Operating instructions

Chapter 8. Cisco Systems IGESM troubleshooting 205
Table 8-1 Specific issues and recommendations
Symptoms specific to
BladeCenter
environment and IGESM
Possible cause/solution
Duplicate IP address
reported on IGESM
Cause: IP address changed directly on IGESM rather than via
Management Module.
Solution: Change IP address to desired setting for IGESM on
Management Module and click Save. See Appendix A, “Hints and tips”
on page 227 for more about this issue.
Duplicate IP address
reported on BladeServer
Cause: Server using same VLAN as IGESM management VLAN;
Management Module proxying for all addresses on that VLAN and
confusing server.
Solution: Separate VLANs, use a different VLAN for the IGESM than
for any of the data VLANs going to the servers. (See section 5.3,
“In-depth management path discussions” on page 55.)
Native VLAN mismatch
reported on IGESM
Cause: 1) Multiple IGESMs in a BladeCenter, and at least one of the
IGESMs is on a different management VLAN than other IGESMs in the
same BladeCenter. 2) Upstream trunked and upstream switch using
different native VLAN than IGESM.
Solution: 1) Place all IGESMs in a BladeCenter into the same
management VLAN or turn off CDP on ports g0/15 and g0/16.
2) Be sure that both sides of the external connection agree on a
common native VLAN. (See section 5.3, “In-depth management path
discussions” on page 55.)
Connection problems to
BladeServers
Cause: 1) VLANs not configured to be carried from servers to other
devices. 2) Servers using same VLAN as IGESM management VLAN;
Management Module proxying for all addresses on that VLAN and
confusing server. 3) Certain drivers on BladeServers (for example,
some versions of the Linux tg3 driver) failing to correctly connect to the
IGESM at certain times, leaving the BladeServer facing port on IGESM
as not connected.
Solution: 1) Make sure desired VLAN is being carried from the blade
server to destination. 2) Separate VLANs; do not use any of the data
VLANs going to the servers for the IGESM VLAN. (See section 5.3,
“In-depth management path discussions” on page 55.) 3) Use a
different (working) version of the driver or use the interface command
speed noneg if IGESM code is at 12.1(22)AY1 or higher.
DHCP server uses up all IP
addresses and
BladeServer still cannot
get an address
Cause: Servers using same VLAN as IGESM management VLAN,
Management Module proxying for all addresses on that VLAN and
confusing DHCP server.
Solution: Separate VLANs; do not use any of the data VLANs going to
the servers for the IGESM VLAN. (See section 5.3, “In-depth
management path discussions” on page 55.)
Intermittent or no
connectivity to IGESM
Cause: Management Module set to permit IGESM to manage over all
ports, uplinks from Management Module and uplinks from IGESM
using the same VLAN.
Solution: If enabling management over all ports, Management Module
must use a VLAN other than any carried on the IGESM uplinks. (See
section 5.3, “In-depth management path discussions” on page 55.)
Cannot configure trunk
failover feature
Cause: Running down level IOS.
Solution: Upgrade to 12.1(14)AY4 or higher.