Operating instructions
238 Cisco Systems Intelligent Gigabit Ethernet Switch Module
2. Log on to IGESM, change IP information to desired information.
3. Save IGESM config to NVRAM (write mem).
4. Reload IGESM.
After the IGESM is reloaded it will be in control of its own IP information in the event of a
IGESM reload, but only if the IGESM reloads. If the Management Module reloads, it will push
its IGESM IP addressing information back onto the IGESM.
A.1 Using code later than 12.1(14)
This document was written specifically for IGESMs using 12.1(14) versions of IOS. Future
versions of IOS, including the next major release (12.1(22)) may have certain features and
functionality that may be different from the 12.1(14) version. Some of the differences are:
CMS replaced by CDM (Cisco Device Manager)
– CMS offers the ability to configure most options within the IGESM.
– CMS requires Java, but CDM does not.
– CDM is primarily a monitoring tool that has limited configuration ability. For GUI-based
configurations, users are encouraged to utilize other tools, such as CiscoWorks.
12.1(22) supports the following features:
– Full 9216-byte jumbo frames
– Support for Smartports
– Configurable Auto-MDIx support
– SSH V2 support in 12.1(22) and later crypto image
– Support for the SFP-based IGESM (OS-CIGESM-18-SFP)
– Support for hard-coding link speed/duplex to 1000/full on ports G0/1 - 14
Other BladeCenter hints and tips
For other hints and tips for the BladeCenter, see IBM BladeCenter (Type 8677) and IBM
BladeCenter HS20 (Type 8678) Product FAQ Hints and Tips version 2.00, available at:
http://www.ibm.com/pc/support/site.wss/document.do?lndocid=MIGR-45277
Important: Because there is no way to allow the IGESM to take 100% control of its own IP
addressing information, it is recommended that you leave Preserve new IP configuration
during all resets to Enabled. If you set this value to Disabled, you are strongly
recommended to keep the proper IP addressing information of the IGESM stored in the
Management Module to ensure that the IGESM will always get the same IP addressing
information no matter whether the IGESM or the Management Module reloads.
Important: Allowing the IGESM to manage its own IP address information assumes that
you will be using the IGESM’s uplinks for in-band management. After this change, the
Management Module will no longer correctly proxy for the IGESM; thus you can no longer
use the Management Module uplink as a management path to the IGESM. See 5.3.5,
“Considerations: Using the IGESM uplinks to manage the IGESM” on page 61.