Seagate ST39103LC Guida Utente Scaricare il pdf (Pagina 63)

Chapter 5. Diagnosing Errors 53

Errors for other spd devices, representing the same physical I/O

path that was interrupted by the pulled cable, will be reported, as

shown in Figure 5-4, “Additional Messages for the Same Pulled

Cable”.

Figure 5-4 Additional Messages for the Same Pulled Cable

Even when an spd device is idle, a SCSI Test Unit Ready

command is sent periodically to the device to confirm that it is

functioning. A failure of this test is reported in the syslog.log file

as illustrated in Figure 5-4, “Additional Messages for the Same

Pulled Cable”.

Failover Error Reporting

/var/adm/syslog/syslog.log records failover events as

well..

Figure 5-5 The Failover Event

The event in Figure 5-5, “The Failover Event” records that I/O for

the device spd0 will be redirected from path 0 (c6t0d0) to path

1 (c7t0d0), the alternate path. The output from setsp -a (Figure

5-6, “setsp -a Output after the Failed Path Is Detected”) now

Jun 30 14:58:28 n4000 vmunix: ALERT: fcT1 (1, 735458, 0/5/0/0) Fibre

Channel Driver received an interrupt indicating a Link Failure. The Frame

Manager Status Register is 0x980010D0.

Jun 30 14:58:31 n4000 vmunix: spd2: path 0 error

Jun 30 14:58:36 n4000 vmunix: ALERT: fcT1 (1, 712251, 0/5/0/0) Fibre

Channel Driver received an interrupt indicating a Link Failure. The Frame

Manager Status Register is 0x980010D0.

Jun 30 14:58:40 n4000 vmunix: spd1: path 0 error

Jun 29 13:53:44 n4000 vmunix: spd0: path failover from 0 to 1.

1 2 ... 58 59 60 61 62 63 64 65 66 67 68

Nessun commento

Seagate ST39103LC Guida Utente Pagina 63