Operating instructions

204 Cisco Systems Intelligent Gigabit Ethernet Switch Module
8.1 Basic rules and unique symptoms
Before going into detail about troubleshooting, it is important to first discuss certain common
rules and symptoms for this environment. Certain interactions within the BladeCenter
between the IGESM and the Management Module require that certain important rules be
followed. Failure to follow these rules can produce unexpected results when deploying the
BladeCenter containing an IGESM. In this section, we summarize some of these rules and
the consequences of not adhering to them. We also discuss some symptoms that might be
seen and possible solutions for these.
8.1.1 Basic rules
1. Do not attach cables to the IGESM until both sides of the connection are configured.
– Symptoms: No upstream connectivity, upstream network failure from spanning tree
loop.
– Solution: Keep cables disconnected or ports shut down until properly configured on
both sides of the connection. This is an important best practice for any switch-to-switch
connections in a production network, not just between the IGESM and its upstream
connections.
2. Do
not put BladeServers on the VLAN that the IGESM uses for its management VLAN
interface.
– Symptoms: Duplicate IP addresses reported on BladeServers, unstable connectivity to
BladeServers, BladeServers unable to obtain a DHCP address, DHCP server
unexpectedly using up all of its IP addresses. Various unexpected connectivity issues
to BladeServers.
– Solution: Use separate VLANs for data and management. (See 5.3, “In-depth
management path discussions” on page 55 for details.)
3. Make sure the IGESM firmware (IOS) code is upgraded.
– Symptoms: Any unexpected issue or missing features (Trunk Failover, Jumbo frames,
Etherchannel load balancing).
– Solution: Review firmware readme file for latest version of code. Upgrade to latest
release of IOS. To locate the latest code for the IGESM, go to:
http://www.ibm.com/support
Under Support by product, click Personal computing. In the Select a product
pull-down menu, select Servers. In the Family pull-down menu, select BladeCenter.
Wait for the screen to refresh and then click Continue and scroll to find the desired
IGESM code.
4. Decide the IGESM management path (via Management Module or IGESM uplinks) and
configure for it.
– Symptoms: Intermittent or no connectivity to IGESM IP address.
– Solutions: See 5.3, “In-depth management path discussions” on page 55.
8.1.2 Basic symptoms and possible solutions
Table 8-1 on page 205 provides a look at some of the more common symptoms and possible
solutions when deploying a BladeCenter containing IGESMs.