LIEBERT-GP-CONDITIONS-MIB :: lgpConditionAcknowledged

MIB Reference — IPNetwork Monitor · Updated September 14, 2026

All MIBsLIEBERT-GP-CONDITIONS-MIBlgpConditionAcknowledged

lgpConditionAcknowledged

Module: LIEBERT-GP-CONDITIONS-MIB

OID (symbolic): LIEBERT-GP-CONDITIONS-MIB::lgpConditionAcknowledged

OID (numeric): 1.3.6.1.4.1.476.1.42.3.2.3.1.18

Node type: OBJECT-TYPE

Type: INTEGER

Access: read-write

Description: This indicates if the condition has been acknowledged. If the value is 'notAcknowledged' then the condition has not been acknowledged. If the value is 'acknowledged' then the condition has been acknowledged. Writing a value of 'acknowledged' to this object acknowledges the condition and the value will be changed to 'acknowledged'.

If the current state of the condition is 'active' (see lgpConditionCurrentState) the condition will, for all devices remain in the table regardless of the state of the 'lgpConditionAcknowledged' object.

If the 'lgpConditionAckReq' is 'notRequired' or this column does not exist for the row then this object has no affect on the duration the condition stays in the lgpConditionsTable.

If the 'lgpConditionAckReq' is 'required' then the condition will remain in the condition table until both the 'lgpConditionCurrentState' is 'inactive' AND 'lgpConditionAcknowledged' is 'acknowledged'.

What is lgpConditionAcknowledged?

This read-write INTEGER shows whether the condition has been acknowledged, taking the value notAcknowledged(1) or acknowledged(2), and an admin can write acknowledged(2) to clear the acknowledgement flag on that row. If the paired lgpConditionAckReq is required, the row stays in lgpConditionsTable until the condition is both inactive and acknowledged; if AckReq is notRequired or absent, this field has no effect on when the row is removed. For example, after resolving a hardware fault an operator might set lgpConditionAcknowledged to acknowledged(2) on that row so it can finally drop out of the table once lgpConditionCurrentState also reads inactive.

Examples

Walk all instances (SNMPv2c):

snmpwalk -v2c -c public <target> 1.3.6.1.4.1.476.1.42.3.2.3.1.18
snmpwalk -v2c -c public <target> LIEBERT-GP-CONDITIONS-MIB::lgpConditionAcknowledged

Get a specific instance (index 1):

snmpget -v2c -c public <target> 1.3.6.1.4.1.476.1.42.3.2.3.1.18.1
snmpget -v2c -c public <target> LIEBERT-GP-CONDITIONS-MIB::lgpConditionAcknowledged.1

Set instance 1 (SNMPv2c):

snmpset -v2c -c private <target> 1.3.6.1.4.1.476.1.42.3.2.3.1.18.1 i <value>

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::lgpConditionAcknowledged 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 OIDNameModule
1isoLANART-AGENT
1.3orgAirPair-MIB
1.3.6dodAirPair-MIB
1.3.6.1internetAirPair-MIB
1.3.6.1.4privateAirPair-MIB
1.3.6.1.4.1enterprisesAirPair-MIB
1.3.6.1.4.1.476emersonLIEBERT-GP-REGISTRATION-MIB
1.3.6.1.4.1.476.1liebertCorpLIEBERT-GP-REGISTRATION-MIB
1.3.6.1.4.1.476.1.42liebertGlobalProductsLIEBERT-GP-REGISTRATION-MIB
1.3.6.1.4.1.476.1.42.3lgpFoundationLIEBERT-GP-REGISTRATION-MIB
1.3.6.1.4.1.476.1.42.3.2lgpConditionsLIEBERT-GP-REGISTRATION-MIB
Numeric OIDNameModule
1.3.6.1.4.1.476.1.42.3.2.3lgpConditionsTableLIEBERT-GP-CONDITIONS-MIB
1.3.6.1.4.1.476.1.42.3.2.3.1lgpConditionEntryLIEBERT-GP-CONDITIONS-MIB
1.3.6.1.4.1.476.1.42.3.2.3.1.18lgpConditionAcknowledgedLIEBERT-GP-CONDITIONS-MIB