SCSI-MIB :: scsiTgtDeviceStatus

MIB Reference — IPNetwork Monitor · Updated September 14, 2026

All MIBsSCSI-MIBscsiTgtDeviceStatus

scsiTgtDeviceStatus

Module: SCSI-MIB

OID (symbolic): SCSI-MIB::scsiTgtDeviceStatus

OID (numeric): 1.3.6.1.2.1.139.2.3.1.1.2

Node type: OBJECT-TYPE

Type: INTEGER

Access: read-only

Description: This object represents the status of this SCSI device, summarizing the state of both the addressable devices (i.e., the logical units) and the non-addressable devices within this SCSI device: - unknown(1): This value is used when the status cannot be determined - available(2): All addressable and non-addressable devices within the SCSI device are fully operational (i.e., no logical units have an abnormal status). - broken(3): The SCSI device is not operational and cannot be made operational without external intervention. - readying(4): One or more logical units within the SCSI device are being initialized and access to the SCSI device is temporarily limited (i.e., one or more of the logical units have a readying status). - abnormal(5): One or more addressable devices within the SCSI device are indicating a status other than available; nevertheless, the SCSI device is operational (i.e., one or more of the logical units have an abnormal status). - nonAddrFailure(6): One or more non-addressable devices within the SCSI device have failed; nevertheless, the SCSI device is operational (i.e., no logical units have an abnormal or readying status).

- nonAddrFailReadying(7): One or more non-addressable devices within the SCSI device have failed; nevertheless, one or more logical units within the SCSI device are being initialized and access to the SCSI device is temporarily limited. - nonAddrFailAbnormal(8): One or more non-addressable devices within the SCSI device have failed and one or more addressable devices within the SCSI device are indicating a status other than available; however, the SCSI device is operational.

What is scsiTgtDeviceStatus?

Summarizes overall health of this SCSI target device across addressable (logical unit) and non-addressable components, with values like available, broken, readying, or abnormal. An admin polling this would treat anything other than 'available' as a signal to check the array further, e.g. 'readying' during a firmware update or 'broken' as a hard failure requiring intervention.

Examples

Walk all instances (SNMPv2c):

snmpwalk -v2c -c public <target> 1.3.6.1.2.1.139.2.3.1.1.2
snmpwalk -v2c -c public <target> SCSI-MIB::scsiTgtDeviceStatus

Get a specific instance (index 1):

snmpget -v2c -c public <target> 1.3.6.1.2.1.139.2.3.1.1.2.1
snmpget -v2c -c public <target> SCSI-MIB::scsiTgtDeviceStatus.1

Start monitoring vendor-neutral, standards-based MIB, storage controller/HBA, SAN/storage array (SCSI-layer identity/status) with a free 30-day trial of IPNetwork Monitor. Create custom SNMP monitor using the SCSI-MIB::scsiTgtDeviceStatus OID value, configure state conditions and alerts, and monitor any vendor-neutral, standards-based MIB, storage controller/HBA, SAN/storage array (SCSI-layer identity/status) from a single console.

OID Breakdown

Upper-level ancestors (6 from the standard OID tree / other modules)
Numeric OIDNameModule
1isoLANART-AGENT
1.3orgAirPair-MIB
1.3.6dodAirPair-MIB
1.3.6.1internetAirPair-MIB
1.3.6.1.2mgmtAXON-MIB
1.3.6.1.2.1mib_2AXON-MIB
Numeric OIDNameModule
1.3.6.1.2.1.139scsiMIBSCSI-MIB
1.3.6.1.2.1.139.2scsiObjectsSCSI-MIB
1.3.6.1.2.1.139.2.3scsiTargetDeviceSCSI-MIB
1.3.6.1.2.1.139.2.3.1scsiTgtDevTableSCSI-MIB
1.3.6.1.2.1.139.2.3.1.1scsiTgtDevEntrySCSI-MIB
1.3.6.1.2.1.139.2.3.1.1.2scsiTgtDeviceStatusSCSI-MIB