Operating instructions

Chapter 5. Cisco Systems IGESM management and user orientation 69
5.3.10 Scenario 4 (possible alternative)
򐂰 IGESM management using IGESM uplinks
򐂰 IGESM and data traffic in a common VLAN
Figure 5-47 Scenario 4: Physically common management and data networks; IGESM uplinks provide
IGESM management path
See 5.3.5, “Considerations: Using the IGESM uplinks to manage the IGESM” on page 61 for
rules for this scenario.
In scenario 4, the management VLAN is shared by both the blade servers and the IGESM. As
long as the IP subnet on the Management Module (on both ETH0 and ETH1) is different from
the IP subnets being used by the IGESM and the blade servers (and it should be if they are
different VLANs), then this design will work.
If for some reason, a blade server in this design were placed into the same IP subnet as the
Management Module (even though it is in a different VLAN), the blade server will more than
Management
Module
IGESM
Bay 1 - 4
Common Management/Data Network
Flow Name Flow Line VLAN Description
MM traffic X Any VLAN other than Y
IGESM and data traffic Y Any VLAN other than X
Possible Design - Common Network
Management enabled for IGESM uplinks
MM management via MM uplink
IGESM management via IGESM uplink
MM on different VLAN than IGESM
IGESM management and data traffic share a single VLAN
BladeCenter
VLAN X
VLAN Y
802.1Q trunk(s)
or mode access
Mode access
ETH 0
ETH 1
To blade servers
MGMT
Interface
VLAN Y
Must be
different IP
subnets
VLAN Y.
Sw Bay - external
management
over all ports
enabled