Operating instructions

Chapter 7. Cisco Systems IGESM configuration and network integration 171
Step 3.1.6: Configure access links
to BladeServer2 and set access
VLAN
.
int g0/2
switchport mode access
switchport access vlan 10
This places BladeServer2’s first NIC
into VLAN 10.
1. In the top toolbar, click VLAN
VLAN.
2. Click port Gi0/2.
3. Click Modify.
4. In the Administrative Mode field,
select Static Access.
5. In the Static-Access VLAN field,
enter 10.
6. Click OK.
7. Click Apply or OK.
Step 3.1.7:
Configure access links
to BladeServer3 and set access
VLAN
.
int g0/3
switchport mode access
switchport access vlan 30
This places BladeServer3’s first NIC
into VLAN 30.
1. In the top toolbar, click VLAN
VLAN.
2. Click port Gi0/3.
3. Click Modify.
4. In the Administrative Mode field,
select Static Access.
5. In the Static-Access VLAN field,
enter 30.
6. Click OK.
7. Click Apply or OK.
Step 3.1.8:
Configure 802.1Q
trunking to BladeServer4 and add
allowed VLANs
.
int g0/4
switchport trunk allowed vlan
2,35,40,45,50
end
Note that the VLAN numbers might be
wrapped in this document; they should
be on the same line as the command.
1. In the top toolbar, click VLAN
VLAN.
2. Click port Gi0/4.
3. Click Modify.
4. In the Trunk-Allowed VLAN field,
enter 2,35,40,45,50.
5. Click OK.
6. Click Apply or OK.
Important: As noted in step 3.1.3, a
limitation in the current version of CMS
exists where it will always include
VLANs 1 and 1001 through 1005. This
can cause a mismatch with the setting
on the blade server side and result in
the trunk not working as expected. The
only solution at this time is to go into the
CLI and run the switchport trunk
allowed vlan command with the
desired settings, as shown in the CLI
section for this step.
Step 3.1.9:
Save Cisco Systems
IGESM config to NVRAM
.
Failure to perform this step will
result in all changes to the Cisco
Systems IGESM being lost if the
BladeCenter is powered off or the
Cisco Systems IGESM is
otherwise restarted.
copy running-config startup-config 1. In the top toolbar, click
Administration Save
Configuration.
2. Leave the Source set to Running
Configuration.
3. In Destination, select Startup
Configuration.
4. Click Save.
Description and comments Actions via IOS CLI for CIGEMS1 Actions via CMS for CIGEMS1