How to interpret TapeAlert flag severity codes
TapeAlert flags fall into three categories of severity: Critical, Warning, and Information. Addtional severity codes are under discussion.
| Severity | Code | Definition |
| Critical |
C |
Either a failure has already occurred or a failure is imminent. Corrective action is required. The condition should be logged and/or an operator informed. |
| Warning |
W |
The system may not be operating optimally. Continued operation without corrective action may cause a failure or raise critical TapeAlert flags. The condition should be logged and/or an operator informed. |
| Information |
I |
The condition should be logged and/or the operator informed. No guidance about continued operation without corrective action is given by this standard. |
| Intervention Required |
(proposed) |
If this condition is not corrected, a data loss failure may occur. The condition should be logged and/or an operator informed. |
| Call service |
(proposed) |
Action by service personnel is required. The condition should be logged and service personnel informed. |
TapeAlert SNMP Monitoring
This is the MIB module TapeAlert-MIB from Hewlett Packard. This OID tree represents the compiled SNMP MIB module TapeAlert-MIB and includes only high-level compiled information. For more detail (mib object descriptions, Unit Types, Textual Conventions, Macro-definitions, etc.), please download the raw SNMP ASN.1 mib test file by clicking on the ZIP icon. To query a live agent with SNMP for objects in module TapeAlert-MIB, use OidView Network Management Tools or SNMP MIB Browser. To capture and analyze snmp traps from a live agent with objects loaded from module TapeAlert-MIB, use OidView Trap Manager SNMP Fault Management.
Statistics for
| Objects: 106 | OIDS: 103 | Object Groups: 0 |
| Traps: 66 | Notifications: 0 | Notification Groups: 0 |
| Tables: 2 | Tabulars: 7 | Scalars/Other: 28 |
This file automagically generated by OidView Network and Fault Management Tools and SNMP MIB Browser.
Copyright 2001-2009 ByteSphere Technologies LLC. All rights Reserved.
What does a TapeAlert report look like?
This is what the SANtools software returns as it polls tape drives & autochangers
If you invoke SMARTMON-UX with the -X option, it will poll tapes at the specified polling periods and produce a message such as:
\\.\TAPE0 polled at Sun Aug 18 23:19:21 2002 Status:Passed
If there was a problem, you might see:
\\.\TAPE0 polled at Sun Aug 18 23:26:49 2002 Status:Not Data Grade - The cartridge is not data grade. Data written to it will be at risk.
Note that it is possible that in the event of a TapeAlert, you will get more than one message per polling cycle.
The information is used by permisson from SANtools. The full page is at: http://www.santools.com/smart/unix/manual/tapealertviewer.htm
What is the TapeAlert architecture?
TapeAlert software, such as SMARTMon-UX polls the tape drive, autochanger, or library via the SCSI, FibreChannel or iSCSI interface via SCSI commands and reads the
error and warning flags defined by the Read More…
How does TapeAlert work?
TapeAlert compatible tape drives - such as the DELL PowerVault 110T SDLT drive - are delivered with TapeAlert features as standard. The internal TapeAlert firmware constantly monitors the drive hardware and the media, checking for errors and potential difficulties. Any problems identified are flagged on a new SCSI log page, where 64 bytes have been reserved for use by TapeAlert.
ANSI TapeAlert V3 Specification
The ANSI TapeAlert V3 Spec 12-MAY-1999 is located here. It covers information that programmers and hardware designers need to refer to.



devTable
tapeAlertTrap3
errorHistoryEntry





