TapeAlert-MIB

All MIBs › TapeAlert-MIB

Category: Alarms and Events, Storage

Description: Monitors tape drive TapeAlert status flags, failure conditions, and preventive maintenance alerts.

Start monitoring vendor-neutral, standards-based MIB, any SNMPv3-capable network device (SNMP engine identity/boot/clock status) with a free 30-day trial of IPNetwork Monitor. Import MIBs, browse SNMP OIDs, create custom SNMP monitors, configure alerts, and monitor any SNMP-enabled network device from a single console.

What Is TapeAlert-MIB?

TapeAlert-MIB is a storage-industry standard MIB (based on the SCSI TapeAlert specification) used to expose health and maintenance status from tape drives, autoloaders, and tape libraries accessed via a host bus adapter. It exposes data such as per-device TapeAlert flag counts, HBA identification, and configuration flags controlling automatic cleaning and copying behavior. It is squarely a hardware-status monitoring MIB: it reports drive failure conditions, cleaning-required alerts, and preventive-maintenance warnings that precede tape media or mechanism failure, effectively serving as the SNMP window into SCSI TapeAlert flags normally read via SCSI Log Sense pages. It has no dependency on standard IETF MIBs but mirrors the vendor-neutral SCSI TapeAlert specification maintained by the storage industry (T10/SNIA). It is typically deployed on backup servers or SAN-attached tape libraries so backup administrators can be alerted before a failed drive or dirty head causes a backup job to fail. Engineers can download the TapeAlert-MIB file directly to load it into their MIB browser.

IPNetwork Monitor allows you to monitor SNMP objects defined in TapeAlert-MIB. Use the built-in SNMP Monitoring Browser to explore available variables, view their current values and descriptions, and select the objects you want to monitor. You can then create SNMP monitors, configure thresholds, and receive alerts when monitored values change.

Supported Devices

tape drives
tape autoloaders/libraries
SCSI/Fibre Channel HBAs

Monitoring Examples

An administrator would poll devTable/devInfo entries indexed by devNum to see per-drive identity and status, alongside hbaName and hbaNumber to correlate a drive with its host bus adapter. Rising TapeAlert flag activity together with autoCleanEnable/autoCopyEnable settings that are still disabled would explain a drive throwing repeated 'cleaning needed' conditions during backup windows. numDevices and tapeAlertCapability indicate how many devices are visible and whether TapeAlert support is active on each, useful for verifying every drive in a library is actually reporting.

What Can Be Monitored

per-drive TapeAlert flags
cleaning-required status
auto-clean/auto-copy configuration
HBA identity and number
device count in library
TapeAlert capability support

Imported Objects

From RFC-1212

OBJECT-TYPE

From RFC-1215

TRAP-TYPE

From RFC1155-SMI

enterprises

From RFC1213-MIB

DisplayString

OIDs

OID symbolic	OID numeric	Type	Access	Description
hp	1.3.6.1.4.1.11
nm	1.3.6.1.4.1.11.2
system	1.3.6.1.4.1.11.2.3
netPeripheral	1.3.6.1.4.1.11.2.3.9
netTape	1.3.6.1.4.1.11.2.3.9.7
tapeAlert	1.3.6.1.4.1.11.2.3.9.7.1
NTF tapeAlertTrap1	1.3.6.1.4.1.11.2.3.9.7.1.0.1			The tape drive is having problems reading data. No data has been lost, but there has been a reduction in the performance of the tape.
NTF tapeAlertTrap2	1.3.6.1.4.1.11.2.3.9.7.1.0.2			The tape drive is having problems writing data. No data has been lost, but there has been a reduction in the capacity of the tape.
NTF tapeAlertTrap3	1.3.6.1.4.1.11.2.3.9.7.1.0.3			The operation has stopped because an error has occured while reading or writing data which the drive cannot correct.
NTF tapeAlertTrap4	1.3.6.1.4.1.11.2.3.9.7.1.0.4			Your data is at risk: 1. Copy any data you require from this tape 2. Do not use this tape again 3. Restart the operation with a different tape
NTF tapeAlertTrap5	1.3.6.1.4.1.11.2.3.9.7.1.0.5			The tape is damaged or the drive is faulty. Call the tape drive supplier helpline.
NTF tapeAlertTrap6	1.3.6.1.4.1.11.2.3.9.7.1.0.6			The tape is from a faulty batch or the tape drive is faulty: 1. Use a good tape to test the drive. 2. If the problem persists, call the tape drive supplier helpline.
NTF tapeAlertTrap7	1.3.6.1.4.1.11.2.3.9.7.1.0.7			The tape cartridge has reached the end of its calculated useful life: 1. Copy any data you need to another tape 2. Discard the old tape.
NTF tapeAlertTrap8	1.3.6.1.4.1.11.2.3.9.7.1.0.8			The tape cartridge is not data-grade. Any data you back up to the tape is at risk. Replace the cartridge with a data-grade tape.
NTF tapeAlertTrap9	1.3.6.1.4.1.11.2.3.9.7.1.0.9			You are trying to write to a write-protected cartridge. Remove the write-protection or use another tape.
NTF tapeAlertTrap10	1.3.6.1.4.1.11.2.3.9.7.1.0.10			You cannot eject the cartridge because the tape drive is in use. Wait until the operation is complete before ejecting the cartridge.
NTF tapeAlertTrap11	1.3.6.1.4.1.11.2.3.9.7.1.0.11			The tape in the drive is a cleaning cartridge. If you want to back up or restore, insert a data-grade tape.
NTF tapeAlertTrap12	1.3.6.1.4.1.11.2.3.9.7.1.0.12			You have tried to load a cartridge of a type which is not supported by this drive.
NTF tapeAlertTrap13	1.3.6.1.4.1.11.2.3.9.7.1.0.13			The operation has failed because the tape in the drive has snapped: 1. Discard the old tape. 2. Restart the operation with a different tape.
NTF tapeAlertTrap14	1.3.6.1.4.1.11.2.3.9.7.1.0.14			The operation has failed because the tape in the drive has snapped: 1. Do not attempt to extract the tape cartridge. 2. Call the tape drive supplier helpline.
NTF tapeAlertTrap15	1.3.6.1.4.1.11.2.3.9.7.1.0.15			The memory in the tape cartridge has failed, which reduces performance. Do not use the cartridge for further backup operations.
NTF tapeAlertTrap16	1.3.6.1.4.1.11.2.3.9.7.1.0.16			The operation has failed because the tape cartridge was manually ejected while the tape drive was actively writing or reading.
NTF tapeAlertTrap17	1.3.6.1.4.1.11.2.3.9.7.1.0.17			You have loaded a cartridge of a type that is read-only in this drive. The cartridge will appear as write-protected
NTF tapeAlertTrap18	1.3.6.1.4.1.11.2.3.9.7.1.0.18			The directory on the tape cartridge has been corrupted. File search performance will be degraded.
NTF tapeAlertTrap19	1.3.6.1.4.1.11.2.3.9.7.1.0.19			The tape cartridge is nearing the end of its useful life. It is recommended that you: 1. Use another tape cartridge for your next backup. 2. Store this tape cartridge in a safe place in case you need to restore data from it.
NTF tapeAlertTrap20	1.3.6.1.4.1.11.2.3.9.7.1.0.20			The tape drive needs cleaning: 1. If the operation has stopped, eject the tape and clean the drive 2. If the operation has not stopped, wait for it to finish and then clean the drive. Check the tape drive users manual for device specific cleaning instructions.
NTF tapeAlertTrap21	1.3.6.1.4.1.11.2.3.9.7.1.0.21			The tape drive is due for routine cleaning: 1. Wait for the current operation to finish. 2. Then use a cleaning cartridge. Check the tape drive users manual for device specific cleaning instructions.
NTF tapeAlertTrap22	1.3.6.1.4.1.11.2.3.9.7.1.0.22			The last cleaning cartridge used in the tape drive has worn out: 1. Discard the worn out cleaning cartridge. 2. Wait for the current operation to finish. 3. Then use a new cleaning cartridge.
NTF tapeAlertTrap23	1.3.6.1.4.1.11.2.3.9.7.1.0.23			The last cleaning cartridge used in the tape drive was an invalid type: 1. Do not use this cleaning cartridge in this drive. 2. Wait for the current operation to finish. 3. Then use a valid cleaning cartridge.
NTF tapeAlertTrap29	1.3.6.1.4.1.11.2.3.9.7.1.0.29			Preventive maintenance of the tape drive is required. Check the tape drive users manual for device specific preventive maintenance tasks or call the tape drive supplier helpline.
NTF tapeAlertTrap30	1.3.6.1.4.1.11.2.3.9.7.1.0.30			The tape drive has a hardware fault: 1. Eject the tape or magazine. 2. Reset the drive. 3. Restart the operation.
NTF tapeAlertTrap31	1.3.6.1.4.1.11.2.3.9.7.1.0.31			The tape drive has a hardware fault: 1. Turn the tape drive off and then on again. 2. Restart the operation. 3. If the problem persists, call the tape drive supplier helpline. Check the tape drive users manual for device specific instructions on turning the device power on and off.
NTF tapeAlertTrap32	1.3.6.1.4.1.11.2.3.9.7.1.0.32			The tape drive has a problem with the host interface: 1. Check the cables and cable connections. 2. Restart the operation.
NTF tapeAlertTrap33	1.3.6.1.4.1.11.2.3.9.7.1.0.33			The operation has failed: 1. Eject the tape or magazine. 2. Insert the tape or magazine again. 3. Restart the operation.
NTF tapeAlertTrap34	1.3.6.1.4.1.11.2.3.9.7.1.0.34			The firmware download has failed because you have tried to use the incorrect firmware for this tape drive. Obtain the correct firmware and try again.
NTF tapeAlertTrap35	1.3.6.1.4.1.11.2.3.9.7.1.0.35			Environmental conditions inside the tape drive are exceeding the humidity specifications
NTF tapeAlertTrap36	1.3.6.1.4.1.11.2.3.9.7.1.0.36			Environmental conditions inside the tape drive are exceeding the temperature specifications
NTF tapeAlertTrap37	1.3.6.1.4.1.11.2.3.9.7.1.0.37			The voltage supply to the tape drive exceeds specifications
NTF tapeAlertTrap38	1.3.6.1.4.1.11.2.3.9.7.1.0.38			A hardware failure of the tape drive is predicted. Call the tape drive supplier helpline.
NTF tapeAlertTrap39	1.3.6.1.4.1.11.2.3.9.7.1.0.39			The tape drive may have a hardware fault. Run extended diagnostics to verify and diagnose the problem. Check the tape drive users manual for device specific instructions on running extended diagnostic tests.
NTF tapeAlertTrap40	1.3.6.1.4.1.11.2.3.9.7.1.0.40			The changer mechanism is having difficulty communicating with the tape drive: 1. Turn the autoloader off then on. 2. Restart the operation. 3. If problem persists, call the tape drive supplier helpline.
NTF tapeAlertTrap41	1.3.6.1.4.1.11.2.3.9.7.1.0.41			A tape has been left in the autoloader by a previous hardware fault: 1. Insert an empty magazine to clear the fault. 2. If the fault does not clear, turn the autoloader off and then on again. 3. If the problem persists, call the tape drive supplier helpline.
NTF tapeAlertTrap42	1.3.6.1.4.1.11.2.3.9.7.1.0.42			There is a problem with the autoloader mechanism.
NTF tapeAlertTrap43	1.3.6.1.4.1.11.2.3.9.7.1.0.43			The operation has failed because the autoloader door is open: 1. Clear any obstructions from the autoloader door. 2. Eject the magazine and then insert it again. 3. If the fault does not clear, turn the autoloader off and then on again. 4. If the problem persists, call the tape drive supplier helpline.
NTF tapeAlertTrap44	1.3.6.1.4.1.11.2.3.9.7.1.0.44			The autoloader has a hardware fault: 1. Turn the autoloader off and then on again. 2. Restart the operation. 3. If the problem persists, call the tape drive supplier helpline. Check the autoloader users manual for device specific instructions on turning the device power on and off.
NTF tapeAlertTrap45	1.3.6.1.4.1.11.2.3.9.7.1.0.45			The autoloader cannot operate without the magazine. 1. Insert the magazine into the autoloader 2. Restart the operation.
NTF tapeAlertTrap46	1.3.6.1.4.1.11.2.3.9.7.1.0.46			A hardware failure of the changer mechanism is predicted. Call the tape drive supplier helpline.
NTF tapeAlertTrap256	1.3.6.1.4.1.11.2.3.9.7.1.0.256			The library mechanism is having difficulty communicating with the drive: 1. Turn the library off then on. 2. Restart the operation. 3. If problem persists, call the library supplier helpline.
NTF tapeAlertTrap257	1.3.6.1.4.1.11.2.3.9.7.1.0.257			There is a problem with the library mechanism. If problem persists, call the library supplier helpline.
NTF tapeAlertTrap258	1.3.6.1.4.1.11.2.3.9.7.1.0.258			The library has a hardware fault: 1. Reset the library 2. Restart the operation. Check the library users manual for device specific instructions on resetting the device.
NTF tapeAlertTrap259	1.3.6.1.4.1.11.2.3.9.7.1.0.259			The library has a hardware fault: 1. Turn the library off and then on again. 2. Restart the operation. 3. If the problem persists, call the library supplier helpline. Check the library users manual for device specific instructions on turning the device power on and off.
NTF tapeAlertTrap260	1.3.6.1.4.1.11.2.3.9.7.1.0.260			The library mechanism may have a hardware fault. Run extended diagnostics to verify and diagnose the problem. Check the library users manual for device specific instructions on running extended diagnostic tests.
NTF tapeAlertTrap261	1.3.6.1.4.1.11.2.3.9.7.1.0.261			The library has a problem with the host interface: 1. Check the cables and cable connections. 2. Restart the operation.
NTF tapeAlertTrap262	1.3.6.1.4.1.11.2.3.9.7.1.0.262			A hardware failure of the library is predicted. Call the library supplier helpline.
NTF tapeAlertTrap263	1.3.6.1.4.1.11.2.3.9.7.1.0.263			Preventative maintenance of the library is required. Check the library users manual for device specific preventative maintenance tasks, or call your library supplier helpline.
NTF tapeAlertTrap264	1.3.6.1.4.1.11.2.3.9.7.1.0.264			General environmental conditions inside the library have exceeded the humidity specifications.
NTF tapeAlertTrap265	1.3.6.1.4.1.11.2.3.9.7.1.0.265			General environmental conditions inside the library have exceeded the temperature specifications.e
NTF tapeAlertTrap266	1.3.6.1.4.1.11.2.3.9.7.1.0.266			he voltage supply to the library exceeds specifications. There is a potential problem with the power supply or failure of a redundant power supply
NTF tapeAlertTrap267	1.3.6.1.4.1.11.2.3.9.7.1.0.267			A cartridge has been left in a drive inside the library by a previous hardware fault: 1. Insert an empty magazine to clear the fault. 2. If the fault does not clear, turn the library off and then on again. 3. If the problem persists, call the library supplier helpline.
NTF tapeAlertTrap268	1.3.6.1.4.1.11.2.3.9.7.1.0.268			There is a potential problem with a drive ejecting cartridges short or with the library mechanism picking a cartridge from a slot. 1. No action needs to be taken at this time. 2. If the problem persists, call the library supplier helpline.
NTF tapeAlertTrap269	1.3.6.1.4.1.11.2.3.9.7.1.0.269			There is a potential problem with the library mechanism placing a cartridge into a slot 1. No action needs to be taken at this time. 2. If the problem persists, call the library supplier helpline.
NTF tapeAlertTrap270	1.3.6.1.4.1.11.2.3.9.7.1.0.270			There is a potential problem with a drive or the library mechanism loading cartridges, or an incompatible cartridge.
NTF tapeAlertTrap271	1.3.6.1.4.1.11.2.3.9.7.1.0.271			The operation has failed because the library door is open: 1. Clear any obstructions from the library door. 2. Close the library door. 3. If the problem persists, call the library supplier helpline.
NTF tapeAlertTrap272	1.3.6.1.4.1.11.2.3.9.7.1.0.272			There is a mechanical problem with the library media import/export mailslot.
NTF tapeAlertTrap273	1.3.6.1.4.1.11.2.3.9.7.1.0.273			The library cannot operate without the magazine. 1. Insert the magazine into the library 2. Restart the operation.
NTF tapeAlertTrap274	1.3.6.1.4.1.11.2.3.9.7.1.0.274			Library security has been compromised
NTF tapeAlertTrap275	1.3.6.1.4.1.11.2.3.9.7.1.0.275			The security mode of the library has been changed. The library has either been put into secure mode, or the library has exited the secure mode. This is for information purposes only. No action is required.
NTF tapeAlertTrap276	1.3.6.1.4.1.11.2.3.9.7.1.0.276			The library has been manually turned offline and is unavailable for use.
NTF tapeAlertTrap277	1.3.6.1.4.1.11.2.3.9.7.1.0.277			A drive inside the library has been taken offline. This is for information purposes only. No action is required.
NTF tapeAlertTrap278	1.3.6.1.4.1.11.2.3.9.7.1.0.278			There is a potential problem with the barcode label or the scanner hardware in the library mechanism. 1. No action needs to be taken at this time. 2. If the problem persists, call the library supplier helpline.
NTF tapeAlertTrap279	1.3.6.1.4.1.11.2.3.9.7.1.0.279			The library has detected a inconsistency in its inventory. 1. Redo the library inventory to correct inconsistency. 2. Restart the operation Check the applications users manual or the hardware users manual for specific instructions on redoing the library inventory.
NTF tapeAlertTrap280	1.3.6.1.4.1.11.2.3.9.7.1.0.280			A library operation has been attempted that is invalid at this time.
control	1.3.6.1.4.1.11.2.3.9.7.1.1
INT revMajor	1.3.6.1.4.1.11.2.3.9.7.1.1.1	INTEGER	read-only	The TapeAlert major revision level (left of the decimal). Used for presence checking.
INT revMinor	1.3.6.1.4.1.11.2.3.9.7.1.1.2	INTEGER	read-only	The TapeAlert minor revision level (right of the decimal).
INT trapEnable	1.3.6.1.4.1.11.2.3.9.7.1.1.3	INTEGER	read-write	Indicates whether agent should or should not send TapeAlert traps.
INT autoCleanEnable	1.3.6.1.4.1.11.2.3.9.7.1.1.4	INTEGER	read-write	Indicates whether application should or should not perform an automatic cleaning operation based on TapeAlert cleaning information.
INT autoCopyEnable	1.3.6.1.4.1.11.2.3.9.7.1.1.5	INTEGER	read-write	Indicates whether application should or should not perform an automatic tape copy or tape discard operation based on TapeAlert media information.
INT numDevices	1.3.6.1.4.1.11.2.3.9.7.1.2	INTEGER	read-only	Total number of tape devices attached to server and managed by TapeAlert agent. Zero means no devices present.
devTable	1.3.6.1.4.1.11.2.3.9.7.1.3		not-accessible	A list of tape device information entries. The number of entries is given by the value of numDevices.
devInfo	1.3.6.1.4.1.11.2.3.9.7.1.3.1		not-accessible	A tape device information entry, containing configuration information for a particular tape device.
INT devNum	1.3.6.1.4.1.11.2.3.9.7.1.3.1.1	INTEGER	read-only	A unique index value for each tape device. Its value ranges between 1 and the value of numDevices.
INT tapeAlertCapability	1.3.6.1.4.1.11.2.3.9.7.1.3.1.2	INTEGER	read-only	Indicates whether tape device supports TapeAlert, with zero indicating not supported and one indicating supported
STR hbaName	1.3.6.1.4.1.11.2.3.9.7.1.3.1.3	DisplayString	read-only	Name of SCSI Host Bus Adaptor connected to tape drive, for example Adaptec AHA2740AT.
INT hbaNumber	1.3.6.1.4.1.11.2.3.9.7.1.3.1.4	INTEGER	read-only	The number of SCSI Host Bus Adaptor connected to tape drive, for example 0 is first HBA on the system.
INT hbaChannel	1.3.6.1.4.1.11.2.3.9.7.1.3.1.5	INTEGER	read-only	SCSI Channel number of SCSI Host Bus Adaptor connected to tape drive, for example 0 is first SCSI channel of HBA.
INT driveScsiID	1.3.6.1.4.1.11.2.3.9.7.1.3.1.6	INTEGER	read-only	SCSI ID of Tape Device.
STR driveInquiry	1.3.6.1.4.1.11.2.3.9.7.1.3.1.7	DisplayString	read-only	SCSI Inquiry data of Tape Device, with vendor ID data followed by device ID data.
STR driveFirmware	1.3.6.1.4.1.11.2.3.9.7.1.3.1.8	DisplayString	read-only	Firmware revision of Tape Device.
STR driveType	1.3.6.1.4.1.11.2.3.9.7.1.3.1.9	DisplayString	read-only	Device type of Tape Device, for example DDS1
INT driveCompress	1.3.6.1.4.1.11.2.3.9.7.1.3.1.10	INTEGER	read-only	Indicates whether Tape Device supports hardware compression, with zero indicating not supported and one indicating supported.
STR currentMedia	1.3.6.1.4.1.11.2.3.9.7.1.3.1.11	DisplayString	read-only	Software label of current media loaded in drive
STR driveSerialNum	1.3.6.1.4.1.11.2.3.9.7.1.3.1.12	DisplayString	read-only	Hardware Serial Number of Tape Device, if available
INT numErrors	1.3.6.1.4.1.11.2.3.9.7.1.4	INTEGER	read-only	Total number of TapeAlert error traps logged by TapeAlert agent since agent was initialised. Zero means that no TapeAlert trap events occurred since initialisation.
errorHistoryTable	1.3.6.1.4.1.11.2.3.9.7.1.5		not-accessible	A list of historical error entries for all tape devices on the server. The list should contain an entry for each TapeAlert trap sent since the TapeAlert agent was initialised.
errorHistoryEntry	1.3.6.1.4.1.11.2.3.9.7.1.5.1		not-accessible	An error entry in the errorHistoryTable, containing information on a historic TapeAlert trap sent by the TapeAlert agent
INT errorIndex	1.3.6.1.4.1.11.2.3.9.7.1.5.1.1	INTEGER	read-only	A unique index value for each error entry. Its value ranges between 1 and the value of numErrors.
INT errorHbaNumber	1.3.6.1.4.1.11.2.3.9.7.1.5.1.2	INTEGER	read-only	The number of SCSI Host Bus Adaptor connected to the tape drive that caused this specific TapeAlert error, for example 0 is first HBA on the system.
INT errorHbaChannel	1.3.6.1.4.1.11.2.3.9.7.1.5.1.3	INTEGER	read-only	SCSI channel number of SCSI Host Bus Adaptor connected to the tape drive that caused this specific TapeAlert error, for example 0 is first SCSI channel of HBA.
INT errorDriveScsiID	1.3.6.1.4.1.11.2.3.9.7.1.5.1.4	INTEGER	read-only	SCSI of the tape drive that caused this specific TapeAlert error, for example 0 is first SCSI channel of HBA.
OCT errorDate	1.3.6.1.4.1.11.2.3.9.7.1.5.1.5	OCTET STRING	read-only	Date and time of the error in yyyymmddHHMMSS format: where yyyy year 1980-9999 mm month 01-12 dd day 01-31 HH hour 00-23 MM minute 00-59 SS second 00-60 (use 60 for leap-second) Example 14:35:26 5th Oct 1996 = 19961005143526
INT errorTrapNum	1.3.6.1.4.1.11.2.3.9.7.1.5.1.6	INTEGER	read-only	TapeAlert trap number of the error. For tape drive/autoloader traps, range 1-64. For library device traps, range 256-319 (Library device traps = TapeAlert flag + 255)
STR errorMedia	1.3.6.1.4.1.11.2.3.9.7.1.5.1.7	DisplayString	read-only	Software label of the media that was loaded in the tape drive at the time of the error.

RFC description

SNMP MIB for managing TapeAlert events on tape drives and libraries. Defines objects to monitor and report tape drive conditions, error states, and cartridge alerts as standardized by the TapeAlert specification.

Start monitoring tape drives, tape autoloaders/libraries, SCSI/Fibre Channel HBAs (TapeAlert flag/preventive-maintenance status) with a free 30-day trial of IPNetwork Monitor. Import MIBs, browse SNMP OIDs, create custom SNMP monitors, configure alerts, and monitor any SNMP-enabled network device from a single console.

Download TapeAlert-MIB

What Is TapeAlert-MIB?

Supported Devices

Monitoring Examples

What Can Be Monitored

This MIB depends on

Related MIBs

RFC description