Operating instructions

Chapter 5. Cisco Systems IGESM management and user orientation 65
It is not imperative in this environment of physically isolated management and data networks
to block the management VLAN on the IGESM uplinks, but doing so prevents issues if the two
upstream networks are ever physically merged. Note that this Scenario covers physically
isolated networks (different switches and routers for each network). Logically isolated
networks (shared switches and routers isolating data and management traffic with VLANs)
such as shown in Scenario 2
must block the management VLAN from traversing the IGESM
uplinks to ensure correct operation.
Although the upstream networks are physically isolated, it is
imperative that the VLANs used
for blade server communication are different from the VLAN used by the Management Module
and IGESM. Figure 5-51 on page 73 shows why this separation is necessary.
5.3.8 Scenario 2 (recommended)
򐂰 IGESM management using Management Module uplink
򐂰 Common management and data networks
Figure 5-45 Scenario 2: Physically common management and data networks; Management Module
providing path
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
MM and IGESM traffic X Any VLAN not used for data traffic
Recommended Design - Common Networks
Management disabled for IGESM uplinks
MM management via MM uplink
IGESM management via MM uplink
MM and IGESM share the same VLAN on MM uplink
Data traffic uses other VLANs
BladeCenter
MGMT
Interface
VLAN X
VLAN X
VLAN A, B, C...
Mode access
ETH 0
ETH 1
To blade servers
802.1Q trunk(s) or
mode access
VLAN X must be
blocked
Sw Bay - external
management
over all ports
disabled
Must be same IP
subnet