Filter
Top Products
114 Sun StorEdge 3900 and 6900 Series Troubleshooting Guide • March 2002
t3 ib Comm_Lost Down Y [ Info/Action ] Lost
communication
(InBandwithdiag213
(ip=xxx.20.67.21
3) ( last reboot was
2001-09-27 15:22:00)
Information: InBand.
This event is
established using
luxadm. This
monitoring may not
be activated for a
particular Sun
StorEdge T3+ array.
Recommended action:
1. Verify luxadm via
command line
(luxadm probe,
luxadm display)
2. Verify cables,
GBICs and
connections along
data path.
3. Check the Storage
Automated
Diagnostic
Environment SAN
Topology GUI to
identify the failing
segment of the
data path.
4. Verify the correct
FC switch
configuration, if
applicable.
t3 oob Comm_Lost Down Y [
Info/Action ] Lost
communication
(OutOfBand with
diag213
(ip=xxx.20.67.212)
Probable Cause: This
problem can also be
caused by a very slow
network, or because
the Ethernet
connection to this Sun
StorEdge T3+ array
was lost.
Information:
OutOfBand. This
means that the Sun
StorEdge T3+ array
failed to answer to a
ping or failed to
return its tokens.
Recommended action:
1. Check Ethernet
connectivity to the
affected Sun
StorEdge T3+
array.
2. Verify the Sun
StorEdgeT3+ array
is booted correctly.
3. Verify the correct
TCP/IP settingson
the Sun StorEdge
T3+ array .
4. Increase the http
and/or ping
timeout in
Utilities--
>System--
>System--
>Timeouts. The
current default
timeouts are 10
seconds for ping
and 60 seconds for
http (tokens).
Category Component EventType Sev Action Description Information