Operating instructions

64 Cisco Systems Intelligent Gigabit Ethernet Switch Module
5.3.7 Scenario 1 (recommended)
򐂰 IGESM management using Management Module uplink
򐂰 Physically isolated management and data networks
Figure 5-44 Scenario 1: Physically separate management and data networks; Management Module
providing path
See 5.3.4, “Considerations: Using the Management Module uplink to manage the IGESM” on
page 59
for rules for this scenario.
Scenarios 1 and 2 are the simplest designs to deploy and support because all management
traffic utilizes the Management Module’s uplink port and isolates this traffic from the data
traffic. In this design, you do not manage the IGESM via its own uplink ports, and the feature
for managing the IGESM over its uplink ports
must be disabled by changing to Disabled the
External management over all ports setting in the Management Module advanced
management section for each IGESM.
For this configuration to operate correctly, the IP address used by the IGESM must be in the
same IP subnet as that being used by the Management Module.
Management
Network
Management
Module
IGESM
Bay 1 - 4
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 - Physically Isolated 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...
802.1Q Trunk(s) or
Mode Access
Mode Access
ETH 0
ETH 1
To blade servers
Must be same IP
subnet
VLAN X should be
blocked
Sw Bay - external
management
over all ports
disabled