Sun Microsystems StorEdge, Troubleshooting Manual

Page: 70 / 168

52 Sun StorEdge SAN 4.0 Release Field Troubleshooting Guide • October 2002
From the messages above, it is apparent that the following events occurred:
■
The
u2ctlr
took control of LUN 0 on
t3b2
■
SSD and SCSI warnings were seen on host
diag226
■
Sun StorEdge Traffic Manager Software has degraded the paths to a device with
WWN 50020f23000003d5
■
One HBA went from CONNECTED to NOT CONNECTED
■
Port 0 on a Sun StorEdge 2 Gb FC switch (ip=172.20.67.84) went offline
... (
continuation
)
----------------------------------------------------------------------
Site : FSDE LAB Broomfield CO
Source : diag226.central.sun.com
Severity : Error (Actionable)
Category : SWITCH2 DeviceId : switch2:100000c0dd00bfda
EventType: StateChangeEvent.M.port.0
EventCode: 12.26.35
EventTime: 2002/09/13 13:06:35
DESCRIPTION: ’port.0’ in SWITCH2 sw-67-84 (ip=172.20.67.84) is now Not-
Available (state changed from ’online’ to ’offline’):
INFORMATION:
A port on the switch2 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 switch2 configuration