Operating instructions

66 Cisco Systems Intelligent Gigabit Ethernet Switch Module
See 5.3.4, “Considerations: Using the Management Module uplink to manage the IGESM” on
page 59 for rules for this scenario.
As noted in scenario 1, this is one of 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 the
External management over all ports setting to Disabled in the Management Module advanced
management section for each IGESM).
The choice of the management interface VLAN on the IGESM is important, as it must not be
set to any VLAN that will be used to carry traffic to or from any blade server.
The VLAN setting on the upstream switch that is connected to the Management Module’s
uplink port can also be any VLAN not used by a blade server in this chassis. However, setting
it to the same VLAN as the management VLAN on the IGESM helps to avoid confusion. (See
Scenario 7 for an exception to this rule.)
As with scenario 1, the IP address used by the IGESM must be in the same IP subnet as that
being used by the Management Module for this configuration to operate correctly.
One important difference between Scenario 1 and Scenario 2: Because the upstream
network is a common infrastructure in this scenario, it relies on VLAN isolation to achieve
separation of traffic types. This requires that VLAN X must be blocked from traveling over the
uplink between the IGESM and its upstream switch. Failure to block this may result in
intermittent connectivity issues when attempting to manage the IGESM.