
Viewing system information4–14
LUN (WWID) Controller Number of Paths
---- ----------------------------------- ---------- ---------------
7 600508b4-000139ed-00007000-01050000 A 2
8 600508b4-000139ed-00007000-010b0000 B 2
9 600508b4-000139ed-00007000-01110000 A 2
The following example shows the output from the show array array_number command in a system
where SFS20 storage is used:
sfs> show array 2
Array: P6C8CX7MQPS7X6
Name: -
Array Number: 2
Type: MSA20
Preferred Server: south1
Firmware: 1.92
Total Disks: 12
Free Disks: 0
Disks Per Group: 11
Raid Type: ADG
Spare Disk Count: 1
Cache Status: OK
Battery Status: OK
Connected to HBA/Port Status
-------------- ---------- ----------
south1 scsi-1/2 online
south2 scsi-1/2 failed
Bay/Disk Status Bay/Disk Status Bay/Disk Status Bay/Disk Status
----------------- ----------------- ----------------- -----------------
1: ok 4: ok 7: logging errors 10: ok
2: ok 5: ok 8: ok 11: ok
3: ok 6: ok 9: ok 12: ok
LUN (WWID) Logical Drive
---- ----------------------------------- ----------
25 a1434c77-d6ca0086 ok
24 a1434c71-e6f50085 ok
The Connected to field shows which servers are attached to the array. The status of the connection is also
shown. In this example, the south2 server cannot access array 2, whereas the south1 server is operating
normally. This might suggest that the UltraSCSI cable connecting south2 to the array has failed. If the
south2 server had never been connected to array 2, the entry for the south2 server would be missing
(instead of being displayed with a status of failed).
The connection status values are described in Table 4-5. If a server that is attached to the array is not listed
in the Connected to field, this indicates that the server has not been rebooted since the array was
attached to the server.
Table 4-5 Connection status values
State Description
failed The server cannot access the SFS20 array. Either the power to the array is turned off or
the UltraSCSI cable connecting the server and the SFS20 array is detached. When the
problem is resolved, you must reboot the server to update the status.
io-hanging The SFS20 array cannot be accessed. This often causes an io-hanging status for other
SFS20 arrays that are attached to the same server, even if those arrays are operating
normally. You must reboot the server. When the server reboots, the status of the failed
SFS20 array changes to failed and the status of the other operational arrays attached
to the server changes to online.
online The server can access the SFS20 array. The Cache status and Battery status
fields are only valid if the connection status is online for at least one server.
Commenti su questo manuale