Operating instructions

74 Cisco Systems Intelligent Gigabit Ethernet Switch Module
5.3.13 Scenario 7 (possible evaluation test environment)
򐂰 IGESM management using Management Module uplinks
򐂰 Management Module and data traffic all in common VLAN
򐂰 IGESM on internally different VLAN, but shares Management Module uplink VLAN for
management
Figure 5-52 Scenario 7: Test Environment only; Management Module uplinks to provide IGESM
management path
Note: This configuration has a known caveat: If the blade server facing ports (g0/1-14) are
trunked, then the IGESM’s management VLAN Y must be blocked from these trunk ports.
Failure to block VLAN Y on the blade server facing ports may result in failed ping requests
from a blade server to the IGESM’s IP address, as well as an intermittent failure to Telnet
from a blade server to the IGESM. However, if the blade server facing ports are set for
Access (and for a different VLAN than Y), this caveat does not apply.
Management
Module
IGESM
Bay 1 - 4
Common Management/Data Network
Flow Name Flow Line VLAN Description
All traffic X All traffic on a single VLAN
IGESM mgmt traffic X via Y IGESM mgmt traffic will flow out MM on VLAN X
Possible IGESM Evaluation Design - Common Network
Management disabled for IGESM uplinks
MM management via MM uplink
IGESM management via MM uplink
MM, IGESM, and data traffic all on a single VLAN
Not recommended in a production environment
BladeCenter
VLAN X VLAN X
802.1Q trunk(s) or
mode access
Mode access
ETH 0
ETH 1
To blade servers
MGMT
Interface
VLAN Y
VLAN X
Sw Bay - external
management
over all ports
disabled
Must be same IP
subnet
If trunk - must
block VLAN Y