All MIBs › CPQSCSI-MIB › cpqScsiLogDrvFaultTol
cpqScsiLogDrvFaultTol
Module: CPQSCSI-MIB
OID (symbolic): CPQSCSI-MIB::cpqScsiLogDrvFaultTol
OID (numeric): 1.3.6.1.4.1.232.5.2.3.1.1.4
Node type: OBJECT-TYPE
Type: INTEGER
Access: read-only
Description: SCSI Logical Drive Fault Tolerance.
This shows the fault tolerance mode of the logical drive.
The following values are valid for the Logical Drive Fault Tolerance:
other(1) The management agent does not recognize the status. You may need to upgrade your software.
none(2) Fault tolerance is not enabled. If a physical drive reports an error, the data cannot be recovered. This is known as RAID 0.
mirroring(3) For each physical drive, there is a second physical drive containing identical data. If a drive fails, the data can be retrieved from the mirror drive.
dataGuard(4) One of the physical drives is used as a data guard drive and contains the exclusive OR of the data on the remaining drives. If a failure is detected, the data is rebuilt using the data guard information plus information from the other drives.
distribDataGuard(5) Distributed Data Guarding, sometimes referred to as RAID 5, is similar to Data Guarding, but instead of storing the parity information on one drive, the information is distributed across all of the drives. If a failure is detected, the data is rebuilt using the data guard information from all the drives.
enhancedMirroring(6) This is used when there are more than 2 physical disks. Each 'mirrored stripe' is written to a disk and is mirrored to an 'adjacent' disk. This is commonly referred to as RAID 1E. If a failure is detected, the data is rebuilt using the data from the mirrored stripes on the other drives.
What is cpqScsiLogDrvFaultTol?
This read-only INTEGER shows the logical drive's fault tolerance mode, with defined values including none, mirroring, dataGuard, distribDataGuard, and enhancedMirroring, where the description notes none means a failed physical drive's data cannot be recovered. Admins check this before assuming a logical drive can survive a physical drive failure without data loss. For example, an admin discovering a critical logical drive set to none(2) schedules reconfiguring it with mirroring before a physical drive actually fails.
Examples
Walk all instances (SNMPv2c):
snmpwalk -v2c -c public <target> 1.3.6.1.4.1.232.5.2.3.1.1.4 snmpwalk -v2c -c public <target> CPQSCSI-MIB::cpqScsiLogDrvFaultTol
Get a specific instance (index 1):
snmpget -v2c -c public <target> 1.3.6.1.4.1.232.5.2.3.1.1.4.1 snmpget -v2c -c public <target> CPQSCSI-MIB::cpqScsiLogDrvFaultTol.1
SNMPv3 example:
snmpget -v3 -l authPriv -u snmpv3-user -a SHA -A "AuthPassword1" -x AES -X "PrivPassword1" <target> cpqScsiLogDrvFaultTol.1
Start monitoring Compaq (HP) server (SCSI storage controller) with a free 30-day trial of IPNetwork Monitor. Create custom SNMP monitor using the CPQSCSI-MIB::cpqScsiLogDrvFaultTol OID value, configure state conditions and alerts, and monitor any Compaq (HP) server (SCSI storage controller) from a single console.
OID Breakdown
Upper-level ancestors (7 from the standard OID tree / other modules)
| Numeric OID | Name | Module |
|---|---|---|
| 1 | iso | LANART-AGENT |
| 1.3 | org | AirPair-MIB |
| 1.3.6 | dod | AirPair-MIB |
| 1.3.6.1 | internet | AirPair-MIB |
| 1.3.6.1.4 | private | AirPair-MIB |
| 1.3.6.1.4.1 | enterprises | AirPair-MIB |
| 1.3.6.1.4.1.232 | compaq | COMPAQ-ID-REC-MIB |
| Numeric OID | Name | Module |
|---|---|---|
| 1.3.6.1.4.1.232.5 | cpqScsi | CPQSCSI-MIB |
| 1.3.6.1.4.1.232.5.2 | cpqScsiComponent | CPQSCSI-MIB |
| 1.3.6.1.4.1.232.5.2.3 | cpqScsiLogDrv | CPQSCSI-MIB |
| 1.3.6.1.4.1.232.5.2.3.1 | cpqScsiLogDrvTable | CPQSCSI-MIB |
| 1.3.6.1.4.1.232.5.2.3.1.1 | cpqScsiLogDrvEntry | CPQSCSI-MIB |
| 1.3.6.1.4.1.232.5.2.3.1.1.4 | cpqScsiLogDrvFaultTol | CPQSCSI-MIB |