loggerDump Event Log

Overview

There are many events recorded in the loggerDump section of a supportDump.log. This section will not cover all of them and will be improved over time. Some important events of interest are:

Host HBA Connections
Fibre Channel Error Events
Host Initiated Target Resets
Host Initiated Aborts
Device Check Condition Sense Data Responses with or without ASQ/ASCQ Codes

To find this section of a support dump, search for "loggerDump". Here are examples of each item mentioned above. If you see events like these that have no clear explanation, you should escalate the case.

Host HBA Connections:

These are part of normal operation during a host, library, or blade reboot, but are unexpected during normal operation or backups.

2009-10-22 11:38:56 0045   80 NOTICE: Host with WWN 20fd0060:6951d129 connected
2009-10-22 11:38:56 0046   80 NOTICE: Host with WWN 210000e0:8b0fbf71 connected
2009-10-22 11:38:57 0047   80 NOTICE: Host with WWN 10000000:c93b4d1e connected
2009-10-22 11:39:19 0048   80 NOTICE: Host with WWN 210000e0:8b1191e4 connected

Fibre Channel Error Events:

(SRR, CRC, Xfer, Adv.Accl): These could indicate serious problems and should be escalated. Could be ecosystem or within the library.

2009-03-18 21:31:54 73335 014 FCAL 1: SRR Received on oxid a1 tag e flags 45000204!

2009-03-18 21:31:54 73349 014 FCAL 1: Received FC Frame CRC Error

2010-07-14 17:57:32 3318 41 FCAL 2: Xfer Error: initId=132, rxId=0x3c28, flags=0xa1e0, status=0x0002, scsiStatus=0x0000, xferLen=0, residual=0, codeLoc=4

2009-07-10 18:33:00 0095 14 FCAL 4: Adv.Accl.Host Err: 2
2009-07-10 19:01:28 0096 111 Health Check 1: 2 New Transfer Errors Detected on FCAL 1

Host Initiated Target Resets:

Ecosystem or response to hardware problems, escalate.

2006-05-10 11:04:45 1517 14 FCAL 2: Target Reset X_ID 2138/1e INIT 07h
2006-05-10 22:28:59 1539 14 FCAL 2: Target Reset X_ID 2300/2a INIT 09h

2006-08-25 09:44:29 4300   14 FCAL 1: TGT RST: 5 trgts rst by WWN 10000000:c93aed7d
2006-08-25 10:09:59 4319   14 FCAL 1: TGT RST: 5 trgts rst by WWN 10000000:c93aed7d
2006-08-25 10:12:49 4337   14 FCAL 1: TGT RST: 5 trgts rst by WWN 10000000:c93aed7d

Host Initiated Aborts:

These are a problem and should be escalated. Could be ecosystem or HBA response to a hardware issue.

2009-03-16 07:13:48 12100 014 FCAL 1: ABT:C(d)S(ffadcdc)oid(194),i=25,rp=1fffa6e0
2009-03-16 07:13:48 12101 014 FCAL 2: ABT:C(18)S(ff9592c)oid(4c),i=1d,rp=1ffed9e0
2009-03-16 07:13:48 12102 014 FCAL 3: Doorbell: Manufacturing is whoInit. CtrlId =
2009-03-16 07:13:48 12103 014 Debug 0: lnksrvresAB:ind=1d,p=2,sid=1f600,rct=84660000
2009-03-16 07:13:48 12104 014 Debug 0: AT: Tag dh in TDEV 3:0:0 sts 0h
2009-03-16 07:13:48 12105 014 Debug 0: lnksrvresAB:ind=25,p=1,sid=17100,rct=84650000

Device Check Condition Sense Data Responses with or without ASQ/ASCQ Codes.

These are informational and could be normal. Communication timeouts are bad, for example, but "Medium not present" and "Blank Check " are normal. Information about sense data can be found in the library and drive SCSI reference manuals.

2005-12-19 00:10:33 0278    8 FCAL 3: SCSI Sense Data for tgt=0, lun=0:
        70 00 04 00 00 00 00 0a 00 00 00 00 08 01 00 00 00 00
Hardware Error: LU Communication Time-Out
2005-12-19 00:10:33 0279   14 Debug 0: fcinEntry: LU Comm Failure: k/c/q=04/08/01

2006-08-25 10:18:44 4356 8 FCAL 6: SCSI Sense Data for tgt=0, lun=0:
70 00 02 00 00 00 00 1c 00 00 00 00 3a 00 30 00 10 13 00 00 00 00 20 20 20 20 20 20 20 00 00 00
Not Ready: Medium Not Present

2006-08-24 23:11:26 0387 8 FCAL 3: SCSI Sense Data for tgt=0, lun=0:
f0 00 08 00 01 00 00 1c 00 00 00 00 00 05 30 00 64 02 00 00 00 00 20 20 20 20 20 20 20 21 00 10
Blank Check: End-Of-Data Detected

What's Next?

Drives and Media >