LIEBERT-GP-SYSTEM-MIB :: lgpSysState

MIB Reference — IPNetwork Monitor · Updated October 06, 2026

All MIBs › LIEBERT-GP-SYSTEM-MIB › lgpSysState

lgpSysState

Module: LIEBERT-GP-SYSTEM-MIB

OID (symbolic): LIEBERT-GP-SYSTEM-MIB::lgpSysState

OID (numeric): 1.3.6.1.4.1.476.1.42.3.7.2.2

Node type: OBJECT-TYPE

Type: INTEGER

Access: read-only

Description: The operating status for the system. The intent of this data is to provide a high level status of the system.

The possible states are:

normalOperation(1) The system is operating normally with no active warnings or alarms. startUp(2) The system is in a startup state (initializing). Monitoring operations and information may not be fully supported at this time. This state will clear automatically when the system is fully initialized and ready to accept monitoring commands. normalWithWarning(3) The system is operating normally with one or more active warnings. Appropriate personnel should investigate the warning(s) as soon as possible and take appropriate action. normalWithAlarm(4) The system is operating normally with one or more active alarms. Appropriate personnel should investigate the alarm(s) as soon as possible and take appropriate action. abnormalOperation(5) They system is operating abnormally. There is a failure within the system that is unexpected under normal operating conditions. Appropriate personnel should investigate the cause as soon as possible. The normal functioning of the system is likely inhibited.

What is lgpSysState?

This object gives a high-level operating state for the system: normal operation, startup/initializing, normal with warning, normal with alarm, or abnormal operation requiring investigation. Admins use this as the first thing to check for overall system health, since it summarizes whether any active warnings or alarms need attention, or whether the system is in an unexpected failure state. For example, seeing normalWithAlarm(4) tells the admin the system is still running but has one or more active alarms that should be investigated as soon as possible.

Examples

Walk all instances (SNMPv2c):

snmpwalk -v2c -c public <target> 1.3.6.1.4.1.476.1.42.3.7.2.2
snmpwalk -v2c -c public <target> LIEBERT-GP-SYSTEM-MIB::lgpSysState

Get a specific instance (index 1):

snmpget -v2c -c public <target> 1.3.6.1.4.1.476.1.42.3.7.2.2.1
snmpget -v2c -c public <target> LIEBERT-GP-SYSTEM-MIB::lgpSysState.1

SNMPv3 example:

snmpget -v3 -l authPriv -u snmpv3-user -a SHA -A "AuthPassword1" -x AES -X "PrivPassword1" <target> lgpSysState.1

Start monitoring Liebert (Vertiv) GlobalProducts UPS or precision power/environmental control system with a free 30-day trial of IPNetwork Monitor. Create custom SNMP monitor using the LIEBERT-GP-SYSTEM-MIB::lgpSysState OID value, configure state conditions and alerts, and monitor any Liebert (Vertiv) GlobalProducts UPS or precision power/environmental control system 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.7lgpSystemLIEBERT-GP-REGISTRATION-MIB
Numeric OIDNameModule
1.3.6.1.4.1.476.1.42.3.7.2lgpSysStatusLIEBERT-GP-SYSTEM-MIB
1.3.6.1.4.1.476.1.42.3.7.2.2lgpSysStateLIEBERT-GP-SYSTEM-MIB