Operating instructions

Chapter 5. Cisco Systems IGESM management and user orientation 67
5.3.9 Scenario 3 (recommended)
򐂰 IGESM management using IGESM uplinks
򐂰 IGESM, Management Module, and data traffic in separate VLANs
Figure 5-46 Scenario 3: Physically common management and data networks; IGESM uplinks to
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.
Scenario 3 is the recommended design when using the IGESM uplinks to manage the
IGESM. In this design, you manage the IGESM via its own uplink ports, and the feature for
managing the IGESM over its uplink ports
must be enabled. (The External management over
all ports setting must be Enabled in the Management Module advanced management section
for each IGESM).
Management
Module
IGESM
Bay 1 - 4
Common Management/Data Network
Flow Name Flow Line VLAN Description
Data traffic A, B, C... Any VLAN other than X or Y
MM traffic X Any VLAN not used for data traffic and not Y
IGESM traffic Y Any VLAN not used for data traffic and not X
Recommended Design - Common Network
Management enabled for IGESM uplinks
MM management via MM uplink
IGESM management via IGESM uplink
MM on different VLAN than IGESM
Data traffic uses other VLANs
BladeCenter
MGMT
Interface
VLAN Y
VLAN YVLAN X VLAN A, B, C...
802.1Q
Trunk(s)
Mode Access
ETH 0
ETH 1
To blade servers
Must be
different IP
subnets
Sw Bay - external
management
over all ports
enabled