Users Guide

In the system tree, go to Chassis OverviewServer Overview and click NetworkVLAN.
The VLAN Tag Settings page is displayed. VLAN tags are chassis properties. They remain with the chassis even when a
component is removed.
2. In the CMC section, enable VLAN for CMC, set the priority and assign the ID. For more information about the fields, see the
CMC Online Help.
3. Click Apply. The VLAN tag settings are saved.
You can also access this page from the Chassis OverviewServersSetupVLAN subtab.
Configuring Virtual LAN Tag Properties for CMC Using RACADM
1. Enable the VLAN capabilities of the external chassis management network:
racadm config -g cfgLanNetworking -o
cfgNicVLanEnable 1
2. Specify the VLAN ID for the external chassis management network:
racadm config -g cfgLanNetworking -o cfgNicVlanID <VLAN id>
The valid values for <VLAN id> are 1– 4000 and 4021– 4094. Default is 1.
For example:
racadm config -g cfgLanNetworking -o cfgNicVlanID
1
3. Then, specify the VLAN priority for the external chassis management network:
racadm config -g cfgLanNetworking -o
cfgNicVLanPriority <VLAN priority>
The valid values for <VLAN priority> are 0–7. Default is 0.
For example:
racadm config -g cfgLanNetworking -o
cfgNicVLanPriority 7
You can also specify both the VLAN ID and the VLAN priority with a single command:
racadm setniccfg -v <VLAN id> <VLAN priority>
For example:
racadm setniccfg -v 1 7
4. To remove the CMC VLAN, disable the VLAN capabilities of the external chassis management network:
racadm config -g cfgLanNetworking -o
cfgNicVLanEnable 0
You can also remove the CMC VLAN using the following command:
racadm setniccfg -v
Federal Information Processing Standards
The agencies and contractors of the Federal government of the United States use Federal Information Processing Standards
(FIPS), a computer security standard, which is related to all applications that have communicative interfaces. The 140–2 comprises
of four levels — Level 1, Level 2, Level 3, and Level 4. The FIPS 140–2 series stipulate that all communicative interfaces must have
the following security properties:
authentication
confidentiality
message integrity
non-repudiation
availability
access control
If any of the properties depend on cryptographic algorithms, then FIPS must approve these algorithms.
75