TapeAlert Code: 0x27, Type: Warning, Flag: DIAGNOSTICS REQ.

[Stumpr2]

This is from the media logs report:
TapeAlert Code: 0x27, Type: Warning, Flag: DIAGNOSTICS REQ., from drive STK9940B_0113_3 (index 3), Media Id E00860

What is this warning about a diagnostic request?
How can I find out more about what set the flag?
It happens on different drives and also different tapes.
I am going to create the bptm debug log and set verbosity.
Also I will start ltid with -v
Any idease on what I should be looking for?

NetBackup 6.0 MP3 w/SSO
Solaris 10 master server/EMM server

SL8500 silo
build_versionFRS_3.02b (4.17.91)

Stk9940b drives
1.35.409/4.06

[DavidParker]

Media Manager Guide for 6.0 has a listing of TapeAlert Codes ...
Page 333+

The entry for 0x27 looks like it's just a warning message:
TapeAlert Code: 0x27
Default Action: None
Error Type: Warning - WRN
Error Message: DIAGNOSTICS REQ.

Did you get any events or notices on the library itself?

Found a C program someone wrote:
http://csourcesearch.net/package/mtxl/1.4.8/mtx-1.2.16rel/tapeinfo.c
They have an entry for each of the TA Codes and left 0x27 blank; I would think that that would indicate that that error isn't necessarily critical.

[zippy]

Bob,

Refer to page 335 http://backups.lbl.gov/backups/documentation/SysAdmin/6.0/MediaMgr_AdminGuide_Unix.pdf

the tape drive choked on tape number E00860, the tape isnt bad its the tape drive that had an error. I would replace it, wouldnt even mess with it.

JD

[Chia_Tan_Beng]

> What is this warning about a diagnostic request?
> How can I find out more about what set the flag?
> It happens on different drives and also different
> tapes.
> I am going to create the bptm debug log and set
> verbosity.
> Also I will start ltid with -v
> Any idease on what I should be looking for?
>

Its one of those TapeAlert warning message/flag set by the drive, in this case its asking for attention for further diagnostics. I'm not sure about STK's 9940 drive but I believe STK should have the diagnostic tape for it had would contain more extensive diagnostic that provide more results. I would escalate to STK as it happened on different drive with different media (if its the newly installed library).