Operating instructions

44 Cisco Systems Intelligent Gigabit Ethernet Switch Module
the Cisco Systems IGESM) are on the same IP subnet, the Management Module will still
attempt to proxy for the Cisco Systems IGESMs, which could result in confusion in the
network. We also recommend that you change the management VLAN on the Cisco Systems
IGESM to something other than the default VLAN1, and it will have be in a VLAN that
contains the IP subnet that will be used to access the Cisco Systems IGESM through its
external connections. For example, if the management IP address of the Cisco Systems
IGESM is 10.200.200.X (24-bit mask), the Cisco Systems IGESM management VLAN in use
must be carrying the 10.200.200.X subnetwork traffic into the Routed Production Network.
To change the Cisco Systems IGESM management VLAN:
1. Create the new VLAN on the Cisco Systems IGESM (vlan XX).
2. Create an interface to the new VLAN (interface vlan XX).
3. Perform a no shut on the new VLAN interface.
This new management VLAN must then be added on the uplink connections (switchport
trunk allowed vlan yy,zz,XX...) and into the Routed Production Network. The best way to
change the actual management IP address of the management VLAN interface on the Cisco
Systems IGESM is through the Web interface of the Management Module, even though it is
on a different IP subnet than that being used by the Management Module. Changing the IP
address directly on the Cisco Systems IGESM has certain issues, as noted in Appendix A,
“Hints and tips” on page 227.
See 5.3.5, “Considerations: Using the IGESM uplinks to manage the IGESM” on page 61 for
details about configuring the BladeCenter for in-band management.
Path 4 details
Although we are showing a blade server as being the station accessing the Cisco Systems
IGESM, path 4 really demonstrates that virtually any device on the Routed Production
Network can access the Cisco Systems IGESM through the Routed Production Network.
(The device acting as the Management Workstation would point its Web, Telnet, SNMP, and
other applications directly at the externally available management IP address of the Cisco
Systems IGESM.) Note that in most cases (except scenario 4 on page 69), for a blade server
to connect to the Cisco Systems IGESM it must first pass though the Cisco Systems IGESM,
into the Routed Production Network, and then be routed back onto the subnet containing the
Cisco Systems IGESM’s IP address. This is an important note, because a blade server
should rarely be placed directly on the same IP subnet/VLAN that is used for the
management IP address of the Cisco Systems IGESM. (See Appendix A, “Hints and tips” on
page 227 for the reasons for this isolation.)
Also, as with path 3, for the Cisco Systems IGESM to be accessed through path 4, the
Management Module
advanced management Web page must have the External ports set to
Enabled, and the Management over all ports set to Enabled. If either of these are disabled,
path 4 will not work.
The same IP subnet and management VLAN rules mentioned for path 3 apply for path 4.
See 5.3.5, “Considerations: Using the IGESM uplinks to manage the IGESM” on page 61 for
information about configuring the BladeCenter for in-band management.
Path 5 details
Path 5 makes use of the service port (RJ45 serial console connection) on the faceplate of the
Cisco Systems IGESM. As with path 1B, this path is independent of the Cisco Systems
IGESM management IP address. The use of path 5 is also totally independent of any settings
on the Management Module. This connection can be used in a simple fashion by attaching a
PC with a serial port directly to it (9600, N, 8, and 1, flow control to none), or in a more