Operating instructions

Chapter 5. Cisco Systems IGESM management and user orientation 43
essentially on path 2, because the Management Module is now acting simply as a
pass-through from the external Management Network into the Cisco Systems IGESM,
through the Ethernet connection between the Management Module and the Cisco Systems
IGESM. Note that for this path to function, the management IP address on the Cisco Systems
IGESM must be in the same IP subnet that is in use on both the internal and external
Ethernet interfaces of the Management Modules.
See 5.3.4, “Considerations: Using the Management Module uplink to manage the IGESM” on
page 59 for details about configuring the BladeCenter for out-of-band management via the
Management Module.
Path 1B
This is a very specific path (I2C interface) used by the Management Module to communicate
to the Cisco Systems IGESM (and other components of the BladeCenter) for certain tasks. It
is
not part of the normal data path and is used only for very specific instructions from the
Management Module to other components in the BladeCenter, and in the specific case of
path 1B, the Cisco Systems IGESM. From a technical perspective, this path is used during
certain Management Module operations toward the Cisco Systems IGESM, such as setting
the Cisco Systems IGESM IP address or resetting the Cisco Systems IGESM to default
values. For the most part, path 1B includes all of the Cisco Systems IGESM management
tools in the Management Module Web-based interface except the ones involving HTTP,
Telnet, or ping testing to the Cisco Systems IGESM.
Note that path 1B is available regardless
of what the management IP address is set to on the Cisco Systems IGESM.
Path 2 details
Path 2 is from any Management Workstation on the Management Network to the Cisco
Systems IGESM, using the Management Module as a pass-through for this connection. (The
Management Workstation would point its Web, Telnet, SNMP, and other applications directly
at the management IP address of the Cisco Systems IGESM.) In this case, management
traffic between the Cisco Systems IGESM and the Management Workstation travels over the
Management Network, through the Management Module, and on to the internal Ethernet
network between the Management Module and the Cisco Systems IGESM (with the same
return path). As with path 1A, for this path to function, the management IP address on the
Cisco Systems IGESM must be in the same IP subnet that is in use on both the internal and
external Ethernet interfaces of the Management Modules.
See 5.3.4, “Considerations: Using the Management Module uplink to manage the IGESM” on
page 59 for details about configuring the BladeCenter for out-of-band management via the
Management Module.
Path 3 details
Path 3 makes use of a connection between the Management Network and the Routed
Production Network to carry traffic between the Cisco Systems IGESM and the Management
Workstation. (The Management Workstation points its Web, Telnet, SNMP, and other
applications directly at the externally available management IP address of the Cisco Systems
IGESM.) In this case, the Management Module is completely bypassed for Cisco Systems
IGESM management purposes, and the management traffic flows in and out of the Cisco
Systems IGESMs external GigE connections.
For the Cisco Systems IGESM to be accessed through path 3, 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 3 will not work.
In this scenario, the IP address of the Cisco Systems IGESM
must be on a different IP subnet
than the IP address used by the Management Module. If they (the Management Module and