Filter
Top Products
FRU State HotSwap
LED Status
Healthy
LED Status
Solution
switch through a console cable.
If OpenArchitect is running, and abnormal behavior
is occurring, please see Network Configuration
Problems for information on network issues.
If OpenArchitect cannot be accessed through the
console port, please see Troubleshooting a Failed
OpenArchitect Load.
Table 11.1: Troubleshooting States
Accessing the ShMM
If the Ethernet Switch Blade has not successfully booted, it will not be accessible via a remote
connection. Some of the following procedures will require local access to the switch to examine
the hardware, and possibly a locally attached serial console connection.
Access to the ShMM (either via a remote telnet session or a local console) will also be used to
gather some additional information about the state of the switch and other FRUs in the chassis. If
a remote connection to the ShMM can be established, it is possible to collect some preliminary
troubleshooting data.
Consult your Chassis user’s guide for more information on logging into the Shelf Manager, and
see Verifying Communications Between the ShMM and Switch, below.
Verifying Communications Between the ShMM and Switch
Verify that the communications between the IPMC on the switch and the ShMM have been
established. Try to see if the switch will respond to the following command requests:
GetSensorReading
GedDevID
If the ShMM cannot communicate with the Ethernet Switch Blade, check other devices in the
chassis. if the Ethernet Switch Blade is the only device not responding, replace the switch.
If the ShMM can communicate with the Ethernet Switch Blade, see the Critical Threshold Error
Reported section, below.
Critical Threshold Error Reported
The ShMM may have been configured to remove back-end power from a FRU reporting critical
Ethernet Switch Blade User's Guide release 3.2.2j page 152