Veritas-bu

[Veritas-bu] NBKMS failed with error status: Invalid KAD length (1220) (there was only 1 google result for this error)

2012-03-07 14:31:59
Subject: [Veritas-bu] NBKMS failed with error status: Invalid KAD length (1220) (there was only 1 google result for this error)
From: "Justin Piszcz" <jpiszcz AT lucidpixels DOT com>
To: <veritas-bu AT mailman.eng.auburn DOT edu>
Date: Wed, 7 Mar 2012 14:31:49 -0500

Hi,

 

Problem

The drive resets itself and goes DOWN.  I’ve had similar problems with IBM LTO-4 tape drives and I had to use a specific F/W for the fiber HBAs (QLogic 2462-CK) so that the tape drives don’t reset themselves, which kills the backups.  Now, using QLogic 2562-CK 8.0gbps HBA with LTO-5 drives, the problem happens again!  Directly connected to IBM LTO-5 (F/W: B6W2) tape drives., when using nbkms, exactly the same (different keys of course) in a different environment, I get the following errors..

 

The one result on Google points to the 6.5.2 documentation updates:

http://www.symantec.com/business/support/resources/sites/BUSINESS/content/live/TECHNICAL_SOLUTION/59000/TECH59310/en_US/302438.pdf

Which states:

EC_KS_invalid_kad_len -1220 -

“Invalid KAD length”

BPTM and the tape drive have requested a Tag /

KAD length combination that is not supported.

 

QLOGIC DETAILS:

Driver Version                    : 8.03.00.10.05.04-k

BIOS Version                      : 2.16

Driver Firmware Version           : 4.04.09 (85)

Flash BIOS Version                : 2.16

Flash FCode Version               : 2.00

Flash EFI Version                 : 2.00

Flash Firmware Version            : 4.04.00

 

QLOGIC DRIVER ERRORS (when backing up using nbkms+LTO-5 encryption)

qla2xxx 0000:15:00.0: LOOP DOWN detected (2 3 0).

qla2xxx 0000:15:00.0: LIP reset occured (f8ef).

qla2xxx 0000:15:00.0: LIP occured (f8ef).

qla2xxx 0000:15:00.0: LOOP UP detected (8 Gbps).

qla2xxx 0000:15:00.0: scsi(0:0:0): Abort command issued -- 1 fc5bd1 2002.

qla2xxx 0000:15:00.0: scsi(0:0:0): Abort command issued -- 1 fc5bb8 2002.

st 0:0:0:0: timing out command, waited 7s

st 0:0:0:0: timing out command, waited 180s

st 0:0:0:0: timing out command, waited 7s

 

Here are the application logs:

1331145746 1 4 16 media-server-name 40583 40255 0 master-server-name bptm NBKMS failed with error status: Invalid KAD length (1220)

1331145746 1 68 4 media-server-name 40583 40255 0 master-server-name nbpem CLIENT master-server-name POLICY BURNIN SCHED Full EXIT STATUS 83 (media open error)

1331145746 1 4 16 media-server-name 40583 40255 0 master-server-name nbpem backup of client master-server-name exited with status 83 (media open error)

1331145748 1 2 16 media-server-name 40603 40256 0 media-server-name bptm FREEZING media id 001231, Encryption unavailable for an ENCR pool

1331145750 1 68 4 media-server-name 40603 40256 0 media-server-name nbpem CLIENT media-server-name POLICY BURNIN SCHED Full EXIT STATUS 83 (media open error)

1331145750 1 4 16 media-server-name 40603 40256 0 media-server-name nbpem backup of client media-server-name exited with status 83 (media open error)

 

On the IBM LTO-5 Fiber Channel (8.0gbps) drive itself (via SL500)

2012-03-07T12:43:03.448, 0.0.0.0.0, 3200, ifm, , error, 3016, 0000, "IfmDriveState::issueCommand(): Drive State Response Bad Result Code = 6406 For Drive ID 2"

 

Justin.

_______________________________________________
Veritas-bu maillist  -  Veritas-bu AT mailman.eng.auburn DOT edu
http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu