Operating instructions

70 Cisco Systems Intelligent Gigabit Ethernet Switch Module
likely have a difficult time connecting to devices on the network. This is because the
Management Module will attempt to proxy for any IP ARP requests (coming up from the blade
server and over to the Management Module via the internal connection), and the blade server
may see a duplicate IP address for itself, or possibly the wrong MAC address for its default
gateway, resulting in failure to complete a connection.
One other possible drawback with this design is the fact that network design best practices
promote separate VLANs for data and management traffic, but we have mixed data and
management traffic on VLAN Y. Based on these concerns, scenario 3 is preferred if using the
IGESM uplinks for management, but scenario 4 might be an alternative if desired.
5.3.11 Scenario 5 (not recommended)
򐂰 IGESM management using IGESM uplinks
򐂰 IGESM and Management Module traffic in common VLAN
Figure 5-48 Scenario 5: Physically common management and data networks; Management Module
uplink and IGESM uplinks provide IGESM management 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
IGESM and MM traffic X Any VLAN not used for data traffic
Poor Design - Common Network
Management enabled for IGESM uplinks
MM management via MM uplink
IGESM management via IGESM uplink
MM and IGESM use the same VLAN on different uplinks
Data traffic uses other VLANs
BladeCenter
MGMT
Interface
VLAN X
VLAN X VLAN A, B, C...
802.1Q
Trunk(s)
Mode Access
ETH 0
ETH 1
To blade servers
Sw Bay - external
management
over all ports
enabled