304 Troubleshooting the Tape Library
T103
T103 - FC I/O Blade Connection Failure
Description GUI Description: Ethernet communication to an I/O blade has failed.
Explanation: The FC I/O blade has two interfaces to the LCB, internal
Ethernet and CAN, and these interfaces are monitored. This RAS ticket is
generated when the LCB can no longer communicate to the FC I/O blade via
the internal Ethernet connection.
Detection Scenarios LCB cannot ping the FC I/O blade via the internal Ethernet interface.
Root Causes • FC I/O blade removed.
• Ethernet cable from the EM is not plugged into the LCB.
• Ethernet cable from the EM to the LCB is bad.
• FC I/O blade is down.
• Ethernet chip/port on the FC I/O blade is not working correctly. If the FC I/O
blade has completely failed, the RAS ticket will indicate that the CAN
interface is not working either. Both an Ethernet failure and a CAN
communication failure will isolate the problem to the FC I/O blade itself.
• LCB hub is not working correctly.
Service Resolution
Steps
Perform DR063 - Resolve FC I/O Blade Connection Failure
on page 395.
Possible CRUs/FRUs Note: Read and perform all resolution steps before dispatching any parts.
Dispatch the first part listed below for replacement. If this does not solve the
problem, dispatch the second part, and so on, in order. Dispatch only one part
(or set of parts) at a time.
1 Ethernet Cable (customer-supplied)
2 FC I/O Blade
3LCB
To Next Page
Loading...
Need help?
General