1 krisbash 1.1 // Copyright (c) 2005 DMTF.  All rights reserved.
 2              // <change cr="ArchCR00066.004" type="add">Add UmlPackagePath
 3              // qualifier values to CIM Schema.</change>
 4              // ==================================================================
 5              //  CIM_VLAN 
 6              // ==================================================================
 7                 [Deprecated { "No Value" }, 
 8                  Version ( "2.8.0" ), 
 9                  UMLPackagePath ( "CIM::Network::VLAN" ), 
10                  Description ( 
11                     "An instance of VLAN represents a VLAN within a switch. In a "
12                     "particular switch, there should be an instance of VLAN for "
13                     "every VLAN available. For example, in a switch with port-based "
14                     "VLANs, if there are 16 VLANs to which ports can be assigned "
15                     "(VLAN 1 through VLAN 16), there should be an instance of "
16                     "CIM_VLAN for each of VLAN 1 through VLAN 16. \n"
17                     "\n"
18                     "VLAN inherits Name from ServiceAccessPoint. Use this for the "
19                     "textual name of the VLAN, if there is one. Otherwise, "
20                     "synthesize a textual name, e.g., VLAN 0003. (Consider leading "
21                     "zero fill, as shown, to ensure that if the textual VLAN names "
22 krisbash 1.1        "are extracted and presented by a management applictions, the "
23                     "VLAN names will sort in the expected order.) The numeric part "
24                     "of the name should be at least four digits wide since 802.1Q "
25                     "specifies 4095 VLANs. \n"
26                     "\n"
27                     "It is intended that VLAN be subclassed only if necessary to "
28                     "add attributes. The type of the VLAN can be inferred from the "
29                     "VLANService(s) with which the VLAN is associated in the "
30                     "VLANFor association. \n"
31                     "\n"
32                     "An instance of VLAN may be associated with more than one "
33                     "VLANService. For example, there are switches that support both "
34                     "802.1Q VLANs and the vendor\'s proprietary VLANs. In some such "
35                     "switches, if a broadcast packet is received on a port in an "
36                     "802.1Q VLAN (VLAN 5, for example), it may be be transmitted "
37                     "from a port in a \'proprietary\' VLAN 5. In effect, there is "
38                     "only one VLAN 5, and the type of port only determines the "
39                     "packet format for tagged packets. In the case just described, "
40                     "only one instance of CIM_VLAN should be instantiated for VLAN "
41                     "5, and it should be associated both with the 802.1Q "
42                     "VLANService and the proprietary VLANService. \n"
43 krisbash 1.1        "\n"
44                     "In typical VLAN-aware switches, packets can be assigned to a "
45                     "VLAN based on the port on which they are received (port-based "
46                     "VLANS), based on the source MAC address (MAC-based VLANs), or "
47                     "based on the value of a set of bits in the packet "
48                     "(protocol-based VLANs). If it is desirable to represent the "
49                     "VLAN assignment predicate for some MAC-based VLAN switch, it "
50                     "will be necessary to subclass VLAN. The list of MAC addresses "
51                     "associated with a VLAN might be an attribute of the subclass. "
52                     "If it is desirable to represent the VLAN assignment predicate "
53                     "in a protocol-based VLAN switch, it will also be necessary to "
54                     "subclass VLAN, InboundVLAN, or both. If the predicate applies "
55                     "to all ports in the switch, then only VLAN need be "
56                     "used/instantiated. If the predicate may vary based on the "
57                     "port, then InboundVLAN must be subclassed, and CIM_VLAN might "
58                     "have to be subclassed as well." )]
59              class CIM_VLAN : CIM_ServiceAccessPoint {
60              
61                    [Deprecated { "No Value" }, 
62                     Description ( "VLAN identifying number." )]
63                 uint16 VLANNumber;
64 krisbash 1.1 
65              
66              };