T1/T2 Notification Events

The example below shows a typical port failure event

Site

:

Lab 3286 - DSQA1 Broomfield

Source

:

diag.xxxxx.xxx.com

Severity :

Error (Actionable)

Category :

Switch

DeviceId :

switch:100000c0dd00b682

EventType:

StateChangeEvent.M.port.8

EventTime:

01/30/2002 11:17:22

’port.8’ in SWITCH diag209-sw2a (ip=192.168.0.32) is now Not-Available (status-state changed from ’Online’ to ’Offline’):

INFORMATION:

A port on the switch has logged out of the fabric and gone offline

PROBABLE-CAUSE:

1.Verify cables, GBICs and connections along Fibre Channel path

2.Check Storage Automated Diagnostic Environment SAN Topology GUI to identify failing segment of the data path

3.Verify correct FC switch configuration

----------------------------------------------------------------------

Site

:

Lab 3286 - DSQA1 Broomfield

Source

:

diag.xxxxx.xxx.com

Severity :

Warning

Category :

Switch

DeviceId :

switch:100000c0dd00b682

EventType:

LogEvent.MessageLog

EventTime:

01/30/2002 11:17:22

Change in Port Statistics on switch diag209-sw2a (ip=192.168.0.32): Port-8: Received 9746 ’InvalidTxWds’ in 0 mins (value=9805 )

FIGURE 8-1Storage Service Processor Event

Chapter 8 Troubleshooting the Sun StorEdge T3+ Array Devices 103

For Internal Use Only

Page 119
Image 119
Sun Microsystems 3900 Series, 6900 Series manual T1/T2 Notification Events