LIEBERT-GP-SYSTEM-MIB

        The MIB module used to specify Liebert Controller OIDs
        
Copyright 2000-2008 Liebert Corporation. All rights reserved.
Reproduction of this document is authorized on the condition
that the forgoing copyright notice is included.
        
This Specification is supplied 'AS IS' and Liebert Corporation
makes no warranty, either express or implied, as to the use,
operation, condition, or performance of the Specification.
    
Source file
LIEBERT-GP-SYSTEM-MIB
Last revised
Identity
liebertSystemModule
Base OID
1.3.6.1.4.1.476.1.42.1.8.1
Imported Objects
LIEBERT-GP-AGENT-MIB lgpAgentConnectedDeviceCount lgpAgentDeviceIndex
LIEBERT-GP-REGISTRATION-MIB lgpSystem liebertSystemModuleReg
RFC1213-MIB sysUpTime
SNMPv2-SMI Integer32 MODULE-IDENTITY (no object page) NOTIFICATION-TYPE (no object page) OBJECT-IDENTITY (no object page) OBJECT-TYPE (no object page) Unsigned32
SNMPv2-TC DisplayString
Net-SNMP examples using the liebert MIB directory Show commands

These commands use the standard Observium installation path and load the selected MIB variant before the RFC and Net-SNMP directories.

Translate the module identity
/usr/bin/snmptranslate -Pud -Ir -On -m 'LIEBERT-GP-SYSTEM-MIB' -M '/opt/observium/mibs/liebert:/opt/observium/mibs/rfc:/opt/observium/mibs/net-snmp' 'LIEBERT-GP-SYSTEM-MIB::liebertSystemModule'
Walk the MIB subtree
/usr/bin/snmpbulkwalk -v2c -c '<community>' -Pud -Ir -OQUs -m 'LIEBERT-GP-SYSTEM-MIB' -M '/opt/observium/mibs/liebert:/opt/observium/mibs/rfc:/opt/observium/mibs/net-snmp' 'udp:<hostname>:161' 'LIEBERT-GP-SYSTEM-MIB::liebertSystemModule'
How SNMP, Net-SNMP, MIB paths, and variants work
Objects (30)
.1.3.6.1.4.1.476.1.42.1.8.1
.1.3.6.1.4.1.476.1.42.3.7.1
.1.3.6.1.4.1.476.1.42.3.7.1.1
.1.3.6.1.4.1.476.1.42.3.7.2
Enumeration
.1.3.6.1.4.1.476.1.42.3.7.2.1
Enumeration
.1.3.6.1.4.1.476.1.42.3.7.2.2
.1.3.6.1.4.1.476.1.42.3.7.3
Enumeration
.1.3.6.1.4.1.476.1.42.3.7.3.1
.1.3.6.1.4.1.476.1.42.3.7.4
.1.3.6.1.4.1.476.1.42.3.7.4.1
Enumeration
.1.3.6.1.4.1.476.1.42.3.7.4.2
.1.3.6.1.4.1.476.1.42.3.7.5
.1.3.6.1.4.1.476.1.42.3.7.5.1
.1.3.6.1.4.1.476.1.42.3.7.6
.1.3.6.1.4.1.476.1.42.3.7.6.1
.1.3.6.1.4.1.476.1.42.3.7.6.2
.1.3.6.1.4.1.476.1.42.3.7.6.3
OctetString
.1.3.6.1.4.1.476.1.42.3.7.7
.1.3.6.1.4.1.476.1.42.3.7.8
.1.3.6.1.4.1.476.1.42.3.7.9
.1.3.6.1.4.1.476.1.42.3.7.9.1
.1.3.6.1.4.1.476.1.42.3.7.9.1.1
.1.3.6.1.4.1.476.1.42.3.7.9.1.1.1
ObjectIdentifier
.1.3.6.1.4.1.476.1.42.3.7.9.1.1.2
OctetString
.1.3.6.1.4.1.476.1.42.3.7.9.1.1.3
OctetString
.1.3.6.1.4.1.476.1.42.3.7.9.1.1.4
.1.3.6.1.4.1.476.1.42.3.7.9.5
.1.3.6.1.4.1.476.1.42.3.7.9.5.5
.1.3.6.1.4.1.476.1.42.3.7.9.5.6
.1.3.6.1.4.1.476.1.42.3.7.9.5.7
Dependencies (9) 5 direct · 4 transitive Show tree and compile order Hide dependency details

Each imported module is resolved in the importing module's source directory first, then through the normal default-variant rules.

Dependency tree
Notifications / Traps (2)
NameOIDDescription
.1.3.6.1.4.1.476.1.42.3.7.8.1
This notification is a generic notification intended for direct user
visibility. The user event description identifies the system
condition that has occurred. This text will be prefixed with either
'Active:', 'Cleared:', or 'Message:' depending on the state of the
event. Note: That a prefix of 'Message:' identifies a stateless event
and as such there will be no corresponding 'Cleared:' trap sent.
.1.3.6.1.4.1.476.1.42.3.7.8.2
The system has returned to a normal operating state. This implies
prior to the generation of this event the system was operating in a
state where one or more alarm or warning conditions were present.
All of those alarms or conditions have now cleared.

NOTE: This notification may be generated after a short delay during a
cold boot of the system -- if no alarms or conditions are present in the
monitored device(s) at that time.