All MIBs › LIEBERT-GP-CONDITIONS-MIB › lgpConditionAckReq
lgpConditionAckReq
Module: LIEBERT-GP-CONDITIONS-MIB
OID (symbolic): LIEBERT-GP-CONDITIONS-MIB::lgpConditionAckReq
OID (numeric): 1.3.6.1.4.1.476.1.42.3.2.3.1.19
Node type: OBJECT-TYPE
Type: INTEGER
Access: read-only
Description: This indicates if the corresponding condition does or does not require user acknowledgement. Conditions that require user acknowledgement will have a value of 'required'. Those conditions that do not require user acknowledgement will have a value of 'notRequired' or in some devices the column may not be present at all.
If a condition requires acknowledgement it will remain in the table until both the 'lgpConditionCurrentState' and 'lgpConditionAcknowledged' are 'inactive' and 'acknowledged' respectively (see lgpConditionAcknowledged).
If a condition does not require acknowledgement it will be removed from the table as soon as its 'lgpConditionCurrentState' is 'inactive'.
What is lgpConditionAckReq?
This read-only INTEGER indicates whether the condition in this row requires operator acknowledgement before it can be removed from lgpConditionsTable, taking the value required(1) or notRequired(2) (or the column may be absent entirely for some devices). It tells an admin whether simply letting the underlying issue clear is enough, or whether they must also explicitly acknowledge the row via lgpConditionAcknowledged. For example, a critical hardware fault might be marked required(1) so it stays visible in the table even after it clears, forcing a technician to confirm they've seen it.
Examples
Walk all instances (SNMPv2c):
snmpwalk -v2c -c public <target> 1.3.6.1.4.1.476.1.42.3.2.3.1.19 snmpwalk -v2c -c public <target> LIEBERT-GP-CONDITIONS-MIB::lgpConditionAckReq
Get a specific instance (index 1):
snmpget -v2c -c public <target> 1.3.6.1.4.1.476.1.42.3.2.3.1.19.1 snmpget -v2c -c public <target> LIEBERT-GP-CONDITIONS-MIB::lgpConditionAckReq.1
Start monitoring Vertiv/Liebert power/cooling equipment (any generation, GP conditions) with a free 30-day trial of IPNetwork Monitor. Create custom SNMP monitor using the LIEBERT-GP-CONDITIONS-MIB::lgpConditionAckReq OID value, configure state conditions and alerts, and monitor any Vertiv/Liebert power/cooling equipment (any generation, GP conditions) from a single console.
OID Breakdown
Upper-level ancestors (11 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.476 | emerson | LIEBERT-GP-REGISTRATION-MIB |
| 1.3.6.1.4.1.476.1 | liebertCorp | LIEBERT-GP-REGISTRATION-MIB |
| 1.3.6.1.4.1.476.1.42 | liebertGlobalProducts | LIEBERT-GP-REGISTRATION-MIB |
| 1.3.6.1.4.1.476.1.42.3 | lgpFoundation | LIEBERT-GP-REGISTRATION-MIB |
| 1.3.6.1.4.1.476.1.42.3.2 | lgpConditions | LIEBERT-GP-REGISTRATION-MIB |
| Numeric OID | Name | Module |
|---|---|---|
| 1.3.6.1.4.1.476.1.42.3.2.3 | lgpConditionsTable | LIEBERT-GP-CONDITIONS-MIB |
| 1.3.6.1.4.1.476.1.42.3.2.3.1 | lgpConditionEntry | LIEBERT-GP-CONDITIONS-MIB |
| 1.3.6.1.4.1.476.1.42.3.2.3.1.19 | lgpConditionAckReq | LIEBERT-GP-CONDITIONS-MIB |