SCSI-MIB :: scsiLuState

MIB Reference — IPNetwork Monitor · Updated September 14, 2026

All MIBsSCSI-MIBscsiLuState

scsiLuState

Module: SCSI-MIB

OID (symbolic): SCSI-MIB::scsiLuState

OID (numeric): 1.3.6.1.2.1.139.2.4.1.1.9

Node type: OBJECT-TYPE

Type: Bits

Access: read-only

Description: This object represents the state of a logical unit and its meaning according to the bit position: 0 Data lost: Within the logical unit data has been lost. 1 Dynamic reconfiguration in progress: The logical unit is being reconfigured. In this state all data is still protected. 2 Exposed: Within the logical unit data is not protected. In this state all data is still valid; however, loss of data or data availability is unavoidable in the event of a failure. 3 Fractionally exposed: Within the logical unit part of the data is not protected. In this state all data is still valid; however, a failure may cause a loss of data or a loss of data availability. 4 Partially exposed: Within the logical unit one or more underlying storage devices have failed. In this state all data is still protected. 5 Protected rebuild: The logical unit is in the process of a rebuild operation. In this state all data is protected. 6 Protection disabled: Within the logical unit the data

protection method has been disabled. In this state all data is still valid; however, loss of data or data availability is unavoidable in the event of a failure. 7 Rebuild: The data protection method is in the process of rebuilding data. In this state data is not protected. 8 Recalculate: The logical unit is in the process of a recalculate operation. 9 Spare in use: Within the logical unit a storage device in full or part is being used to store data. In this state all data is still protected. 10 Verify in progress: Within the logical unit data is being verified.

What is scsiLuState?

A bitmask detailing exactly what condition an 'abnormal' logical unit is in, such as dataLost, exposed (unprotected data), rebuild in progress, or spareInUse. When scsiLuStatus reports abnormal, an admin checks this field to see, for example, whether a RAID rebuild is underway (rebuild/spareInUse bits) versus outright data loss (dataLost bit).

Examples

Walk all instances (SNMPv2c):

snmpwalk -v2c -c public <target> 1.3.6.1.2.1.139.2.4.1.1.9
snmpwalk -v2c -c public <target> SCSI-MIB::scsiLuState

Get a specific instance (index 1):

snmpget -v2c -c public <target> 1.3.6.1.2.1.139.2.4.1.1.9.1
snmpget -v2c -c public <target> SCSI-MIB::scsiLuState.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::scsiLuState 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.4scsiLogicalUnitSCSI-MIB
1.3.6.1.2.1.139.2.4.1scsiLuTableSCSI-MIB
1.3.6.1.2.1.139.2.4.1.1scsiLuEntrySCSI-MIB
1.3.6.1.2.1.139.2.4.1.1.9scsiLuStateSCSI-MIB