| Name | Data Type | Value | Scope | Flavors |
|---|---|---|---|---|
| Description | string | A FilterList is used by network devices to identify routes by aggregating a set of FilterEntries into a unit, called a FilterList. FilterLists can also be used to accept or deny routing updates. A FilterList is weak to the network device (e.g., the ComputerSystem) that contains it. Hence, the ComputerSystem keys are propagated to this class. | None | TRANSLATABLE= true |
| Name | Data Type | Qualifiers | ||||
|---|---|---|---|---|---|---|
| Name | Data Type | Value | Scope | Flavors | ||
| CreationClassName | string | |||||
| Description | string | The type of class that this instance is. | None | TRANSLATABLE= true | ||
| Key | boolean | true | None | OVERRIDABLE= false |
||
| Direction | uint16 | |||||
| Description | string | This defines whether the FilterList is used for input, output, or both input and output filtering. All values are used with respect to the interface for which the FilterList applies. "Not Applicable" (0) is used when there is no direction applicable to the FilterList. "Input" (1) is used when the FilterList applies to packets that are inbound on the related interface. "Output" (2) is used when the FilterList applies to packets that are outbound on the related interface. "Both" (3) is used to indicate that the direction is immaterial, e.g., to filter on a source subnet regardless of whether the flow is inbound or outbound. "Mirrored" (4) is also applicable to both inbound and outbound flow processing, but indicates that the filter criteria are applied asymmetrically to traffic in both directions and, thus, specifies the reversal of source and destination criteria (as opposed to the equality of these criteria as indicated by "Both"). The match conditions in the aggregated FilterEntryBase subclass instances are defined from the perspective of outbound flows and applied to inbound flows as well by reversing the source and destination criteria. So, for example, consider a FilterList with 3 FilterEntries indicating destination port = 80, and source and destination addresses of a and b, respectively. Then, for the outbound direction, the filter entries match as specified and the mirror (for the inbound direction) matches on source port = 80 and source and destination addresses of b and a, respectively. | None | TRANSLATABLE= true | ||
| Values | string | Not Applicable, Input, Output, Both, Mirrored | None | TRANSLATABLE= true | ||
| Name | string | |||||
| Description | string | This is the name of the FilterList. | None | TRANSLATABLE= true | ||
| Key | boolean | true | None | OVERRIDABLE= false |
||
| MaxLen | uint32 | 256 | None | None | ||
| SystemCreationClassName | string | |||||
| Description | string | The scoping ComputerSystem's CreationClassName. | None | TRANSLATABLE= true | ||
| Key | boolean | true | None | OVERRIDABLE= false |
||
| MaxLen | uint32 | 256 | None | None | ||
| Propagated | string | CIM_ComputerSystem.CreationClassName | None | OVERRIDABLE= false |
||
| SystemName | string | |||||
| Description | string | The scoping ComputerSystem's Name. | None | TRANSLATABLE= true | ||
| Key | boolean | true | None | OVERRIDABLE= false |
||
| MaxLen | uint32 | 256 | None | None | ||
| Propagated | string | CIM_ComputerSystem.Name | None | OVERRIDABLE= false |
||
| Name | Data Type | Class Origin |
|---|---|---|
| Caption | string | CIM_ManagedElement |
| Description | string | CIM_ManagedElement |
| InstallDate | datetime | CIM_ManagedSystemElement |
| Status | string | CIM_ManagedSystemElement |