Operating instructions

Chapter 7. Cisco Systems IGESM configuration and network integration 147
Step 3.2.3: Configure 802.1Q
trunking toward 6500s and add
allowed VLANs
.
Note that on the line allowing
specific VLANs, there cannot be
any spaces between the numbers
and the commas.
Also note that VLAN 2 is the
native VLAN on these ports by
default.
int port-channel 1
description EtherChannel-To-6500-1
switchport trunk native vlan 2
switchport trunk allowed vlan
2,20,25,30,35,40,45,50
switchport mode trunk
Note that the VLAN numbers might be
wrapped in this document; they should
be on the same line as the command.
int port-channel 2
description EtherChannel-To-6500-3
switchport trunk native vlan 2
switchport trunk allowed vlan
2,20,25,30,35,40,45,50
switchport mode trunk
1. In the top menu bar, click VLAN →
VLAN.
2. Click po1.
3. Click Modify.
4. In the Trunk-Allowed VLAN field,
enter 2,20,25,30,35,40,45,50.
5. Click OK.
6. Click Apply or OK.
7. Repeat the process for po2.
Important: 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 6500
side and result in the aggregation going
down. 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.2.4:
Configure 802.1Q
trunking to BladeServer1 and add
allowed VLANs
.
int g0/1
switchport trunk allowed vlan
2,20,25
Note that the VLAN numbers might be
wrapped in this document; they should
be on the same line as the command.
This allows VLANs 2, 20, and 25 to
reach BladeServer1’s second NIC.
1. In the top menu bar, click VLAN →
VLAN.
2. Click port Gi0/1.
3. Click Modify.
4. In the Trunk-Allowed VLAN field,
enter 2,20,25.
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.2.5:
Configure access links
to BladeServer2 and set access
VLAN
.
int g0/2
switchport mode access
switchport access vlan 20
This places BladeServer2’s second NIC
into VLAN 20.
1. In the top menu bar, 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 20.
6. Click OK.
7. Click Apply or OK.
Description and comments Actions via IOS CLI for CIGEMS2 Actions via CMS for CIGEMS2