Name | Data Type | Value | Scope | Flavors |
---|---|---|---|---|
Association | boolean | true | None | OVERRIDABLE= false |
Description | string | This association makes explicit the operational dependencies of a SwitchPort when operating in a VLAN. If there is an association between a particular SwitchPort and a particular VLAN, then there is the possibility that a packet received by the port will be assigned to the VLAN (or if the packet already has a VLAN tag, that the packet will not be dropped). If there is no such association, then there is no possibility that a packet received by the port will progress through the switch having been assigned to the VLAN in question. | None | TRANSLATABLE= true |
Name | Data Type | Qualifiers | ||||
---|---|---|---|---|---|---|
Name | Data Type | Value | Scope | Flavors | ||
Default | boolean | |||||
Description | string | Default should be true if untagged packets received by the SwitchPort are assigned to the VLAN by default. For 802.1Q-compliant ports, the Default property should be true on the association instance connecting a SwitchPort to the CIM_VLAN corresponding to the port's PVID. Default should never be true if Tagged is true -- it applies only to untagged packets. | None | TRANSLATABLE= true | ||
Tagged | boolean | |||||
Description | string | If true, packets already tagged with this VLAN number will beaccepted when arriving at this port. For example, if there isan InboundVLAN association between port 12 and VLAN 7 forwhich Tagged is true, then if a packet tagged with VLAN 7arrives at port 12, the packet will be accepted into theswitch for further processing. If there is no such association, then the packet will be dropped. If false, it means that any untagged packets arriving at thisport MIGHT be classified into the associated VLAN. If, for aparticular SwitchPort, there is only one instance of theassociation for which Tagged is false, then all incominguntagged packets will be classified into that VLAN. This isthe typical configuration of a non-trunk port in a switchimplementing port-based VLANs. If there is more than one suchassociation instance, then the packet MIGHT be classifiedinto any one of them, based on some criterion other than theidentity of the switch port. For example, in a MAC-based VLAN switch, the decision would be based on the source MAC address. In a protocol-based VLAN switch, the decision would be based on the values of some set of bits in the packet. Note that the MAC address is formatted as twelve hexadecimal digits (e.g., "010203040506"), with each pair representing one of the six octets of the MAC address in "canonical" bit order according to RFC 2469. | None | TRANSLATABLE= true |
Name | Class Origin | Reference Class |
---|---|---|
Antecedent | CIM_InboundVLAN | CIM_VLAN |
Dependent | CIM_InboundVLAN | CIM_SwitchPort |
Name | Class Origin | Reference Class |
---|---|---|
Antecedent | CIM_SAPSAPDependency | CIM_ServiceAccessPoint |
Antecedent | CIM_Dependency | CIM_ManagedElement |
Dependent | CIM_SAPSAPDependency | CIM_ServiceAccessPoint |
Dependent | CIM_Dependency | CIM_ManagedElement |