Operating instructions

Chapter 7. Cisco Systems IGESM configuration and network integration 167
Step 3: Configuring Cisco Systems IGESMs
This section steps through the sequence of actions required to configure the Cisco Systems
IGESMs for this example. It is broken into two major sections, one for configuring the Cisco
Systems IGESM in bay 1 and one for configuring the Cisco Systems IGESM in bay 2.
The following assumptions have been made for both Cisco Systems IGESM configurations in
this example:
򐂰 The user is already logged on to the Cisco Systems IGESM, and the switch is in enable
mode (or logged on to CMS and using the GUI therein).
򐂰 Commands are being performed in the sequence shown.
򐂰 The Cisco Systems IGESM is starting from a base configuration per the example shown in
“Cisco Systems IGESM base configurations” on page 108.
򐂰 The operating systems in use on the blade servers are Windows 2000. This is important,
because which port is considered “first” and which port is considered “second” on a blade
server has several dependences, not the least of which is the operating system in use. For
an explanation of the blade servers connection names and how they are derived, see
Appendix A, “Hints and tips” on page 227.
򐂰 On BladeServer1, both ports will be using trunking (but not load balancing) through the
Broadcom BASP software. The first port will be configured for VLANs 10 and 15, the
second port will be configured for VLANs 20 and 25.
򐂰 On BladeServer2, both ports will be simple access links and will be placed on VLANs 10
and 20, respectively, through port settings on the Cisco Systems IGESMs.
򐂰 On BladeServer3, both ports will be teamed through the Broadcom BASP software to
appear as a single logical link to the OS, using access VLAN 30 as configured at the Cisco
Systems IGESM’s ports to this server.
򐂰 On BladeServer4, both ports will be teamed through the Broadcom BASP software to
appear as a single logical link to the OS and use 802.1Q trunking to support VLANs 35,
40, 45, and 50.
Step 3.1: Configuring the first Cisco Systems IGESM (CIGESM1)
Figure 7-16 shows the step-by-step instructions used to configure CIGESM1, showing both
CLI and CMS commands.
Step 2.4: Save config to
NVRAM
.
Note: Failure to save your
configuration will result in
possible network down
conditions if the switch is
restarted prior to the save (all
changes since last save will
be lost).
copy running-config startup-config copy running-config startup-config
Description and comments On the 6500-1 On the 6500-3
Important: The current version of CMS supported on the Cisco Systems IGESM has a
limitation in its ability to completely control VLANs being placed on a given trunk: It always
includes VLAN 1 and 1001-1005, even if you do not set them as allowed. Due to this
limitation, its use might not be appropriate for production configuration when trying to
control VLANs allowed on a given trunk.