Operating instructions

Chapter 5. Cisco Systems IGESM management and user orientation 75
See 5.3.4, “Considerations: Using the Management Module uplink to manage the IGESM” on
page 59 for basic rules for this scenario. Keep in mind that this violates some of those rules as
explained below, but is still functional for evaluation purposes.
As noted earlier, this scenario might prove useful for evaluating the IGESM on a single VLAN
test network. But because it shares the same VLAN for all traffic, it is not advised for use in
production environments.
Two important facts about this design:
򐂰 Management over the IGESM uplinks
must be disabled to prevent the IGESM and
Management Module from competing for management of the IGESM IP address (ARP
war for who controls the IGESM’s IP address). Only the Management Module should
provide the management path to the IGESM in this environment.
򐂰 The IP subnet used by the Management Module and the IGESM must be the same.
The defaults for the IGESM have the management VLAN interface as VLAN 1, with ports
going to the blade servers and uplinks tending to default to VLAN 2 (depending on the
configurations on the other sides of the links).
One approach that is encountered frequently in test environments places all traffic on
VLAN 1. While placing all traffic on a single VLAN (especially VLAN 1) defies best practices, it
may be suitable for limited test environments. If this sort of test environment were so desired,
it would first be necessary to create the new management VLAN for the IGESM, then change
the IGESM’s management interface to the newly created VLAN, and then place the blade
server and uplink facing ports on VLAN 1.
The following procedures are for setting up a test environment that uses VLAN 1 for all user
and management traffic, and VLAN 4000 as the IGESM internal VLAN to connect over to the
Management Module.
VLAN 4000 was chosen only for illustration purposes.
Summary of steps to configure scenario 7
1. Change the IGESM’s management interface VLAN.
2. Change the IGESM’s uplink facing ports.
3. Change the IGESM’s blade server facing ports.
Changing the IGESM’s management interface VLAN
To change the VLAN used by the IGESM to carry traffic over ports g0/15 and g0/16, the first
step is to create the new VLAN. For this example, it should be one
not assigned for any other
use within this IGESM. After the VLAN is created, you must create a new management
interface that uses the new VLAN. When the new interface is created, performing no
shutdown on the new interface will move the IP address of the IGESM over to this new
interface and automatically change the management VLAN on the links on g0/15 and 16 (the
native VLAN) to this new VLAN.
Syntactically, changing the IGESM’s management VLAN looks as follows:
conf t
Places IGESM into configuration mode.
vlan 4000
Creates the new VLAN to be used for management.
For this example we have used VLAN 4000.
This is just an example. Whichever VLAN you
choose, it must not be used for any other purpose within this IGESM (restriction of this
specific scenario).