Sun Microsystems StorEdge, Troubleshooting Manual

Page: 123 / 168

Appendix B Brocade Communications Systems Switch Troubleshooting 105
1. Discover the Error using Storage Automated Diagnostic Environment Alerts as
shown in
FIGURE B-3
.
Site : Lab Broom
Source : diag229.central.sun.com
Severity : Error (Actionable)
Category : BROCADE DeviceId : brocade:1000006069201efc
EventType: StateChangeEvent.M.port.2
EventCode: 5.26.35
EventTime: 2002/07/11 10:32:33
’port.2’ in BROCADE br-67-167 (ip=172.20.67.167) is now Not-Available (state changed from
’online’ to ’offline’):
INFORMATION:
A port on the switch has logged out of the fabric and gone offline
RECOMMENDED-ACTION:
1. Verify cables, GBICs and connections along Fibre Channel path
2. Check SAN Topology GUI to identify failing segment of the data path
3. Verify correct FC switch configuration
4. Verify port is enabled
----------------------------------------------------------------------
Site : Lab Broom
Source : diag229.central.sun.com
Severity : Error (Actionable)
Category : MESSAGE DeviceId : message:diag229.central.sun.com
EventType: LogEvent.driver.QLC_LOOP_OFFLINE
EventCode: 9.20.315
EventTime: 2002/07/11 10:32:45
Found 1 ’driver.QLC_LOOP_OFFLINE’ errors(s) in logfile: /var/adm/messages on
diag229.central.sun.com (id=80c61254):
INFORMATION:
Found Loop OFFLINE message.
This could indicate that a fiber channel cable has been removed.
This could indicate troubles with a fiber channel loop.
This could also be caused by running the qlctest.
RECOMMENDED-ACTION:
1. Check to see if a fiber channel cable has been removed.
2. Check for fiber channel errors.
3. Check to see if the qlctest was running at time of the failure.
----------------------------------------------------------------------
[continued on next page]