LIEBERT-GP-SYSTEM-MIB: View SNMP OID List / Download MIB

VENDOR: VERTIV


 Home MIB: LIEBERT-GP-SYSTEM-MIB
Download as:   

Download standard MIB format if you are planning to load a MIB file into some system (OS, Zabbix, PRTG ...) or view it with a MIB browser. CSV is more suitable for analyzing and viewing OID' and other MIB objects in excel. JSON and YAML formats are usually used in programing even though some systems can use MIB in YAML format (like Logstash).
Keep in mind that standard MIB files can be successfully loaded by systems and programs only if all the required MIB's from the "Imports" section are already loaded.
The tree-like SNMP object navigator requires no explanations because it is very simple to use. And if you stumbled on this MIB from Google note that you can always go back to the home page if you need to perform another MIB or OID lookup.


Object Name OID Type Access Info
 liebertSystemModule 1.3.6.1.4.1.476.1.42.1.8.1
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.
 lgpSysStatistics 1.3.6.1.4.1.476.1.42.3.7.1
This sub-tree is used to register Liebert System Statistics object identifiers.
     lgpSysStatisticsRunHrs 1.3.6.1.4.1.476.1.42.3.7.1.1 unsigned32 read-only
Accumulated run hours of the system.
 lgpSysStatus 1.3.6.1.4.1.476.1.42.3.7.2
This sub-tree is used to register Liebert System Status object identifiers.
     lgpSysSelfTestResult 1.3.6.1.4.1.476.1.42.3.7.2.1 integer read-only
The outcome of the previous self-test. Enumeration: 'unknown': 1, 'failed': 3, 'inhibited': 6, 'sysFailure': 5, 'passed': 2, 'inProgress': 4.
     lgpSysState 1.3.6.1.4.1.476.1.42.3.7.2.2 integer read-only
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. Enumeration: 'normalWithAlarm': 4, 'startUp': 2, 'abnormalOperation': 5, 'normalWithWarning': 3, 'normalOperation': 1.
 lgpSysSettings 1.3.6.1.4.1.476.1.42.3.7.3
This sub-tree is used to register Liebert System Settings object identifiers.
     lgpSysAudibleAlarm 1.3.6.1.4.1.476.1.42.3.7.3.1 integer read-write
The state of the audible alarm of the device. Enumeration: 'on': 1, 'off': 2.
 lgpSysControl 1.3.6.1.4.1.476.1.42.3.7.4
This sub-tree is used to register Liebert System Control object identifiers.
     lgpSysSelfTest 1.3.6.1.4.1.476.1.42.3.7.4.1 integer32 read-write
Self-Test Command. This command will initiate a system self-test of the system. If already initiated, this command will abort the self-test. This command should be sent with a parameter of 1. This variable doesn't return a value when read.
     lgpSysControlOperationOnOff 1.3.6.1.4.1.476.1.42.3.7.4.2 integer read-write
This object allows control of the system functionality. This will not affect the communications or control of the system, so that once turned off, the system operation can be restored by setting this value to 'on'. Enumeration: 'on': 1, 'off': 2.
 lgpSysTime 1.3.6.1.4.1.476.1.42.3.7.5
This sub-tree is used to register Liebert System Time object identifiers.
     lgpSysTimeEpoch 1.3.6.1.4.1.476.1.42.3.7.5.1 unsigned32 read-write
The present time of the system. This time is represented as the number of seconds since the epoch of 1970-01-01 00:00:00 GMT.
 lgpSysMaintenance 1.3.6.1.4.1.476.1.42.3.7.6
This sub-tree is used to register Liebert System Maintenance object identifiers.
     lgpSysMaintenanceCapacity 1.3.6.1.4.1.476.1.42.3.7.6.1 unsigned32 read-only
The relative percentage of time that has elapsed since the last scheduled maintenance was performed. When this value reaches 100%, the device is due for another scheduled maintenance procedure.
     lgpSysMaintenanceYear 1.3.6.1.4.1.476.1.42.3.7.6.2 unsigned32 read-only
The year in which the next scheduled service is due
     lgpSysMaintenanceMonth 1.3.6.1.4.1.476.1.42.3.7.6.3 unsigned32 read-only
The month in which the next scheduled service is due
 lgpSysEventDescription 1.3.6.1.4.1.476.1.42.3.7.7 displaystring read-only
An ASCII textual description for the event. This object is primarily used in the varbind of some notifications to provide a simple human-readable description.
 lgpSysEventNotifications 1.3.6.1.4.1.476.1.42.3.7.8
This sub-tree is used to register Liebert System Notification object identifiers.
     lgpSysNotification 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.
     lgpSysNormal 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.
 lgpSysDeviceComponentGroup 1.3.6.1.4.1.476.1.42.3.7.9
This sub-tree registers well known device components.
     lgpSysDeviceComponentTable 1.3.6.1.4.1.476.1.42.3.7.9.1 no-access
A list of components of devices identified by their serial number and or model number. This table contains zero, one, or many rows. The NMS cannot create or delete rows from the table. The rows are created by the agent based upon the capabilities of the managed device.
         lgpSysDeviceComponentEntry 1.3.6.1.4.1.476.1.42.3.7.9.1.1 no-access
This entry defines the contents of the columns for the table 'lgpSysDeviceComponentTable'.
             lgpSysDeviceComponentIndex 1.3.6.1.4.1.476.1.42.3.7.9.1.1.1 unsigned32 no-access
This is the index indicating the row in the table 'lgpSysDeviceComponentTable' for a component entry.
             lgpSysDeviceComponentDescr 1.3.6.1.4.1.476.1.42.3.7.9.1.1.2 object identifier read-only
An OID representing a component of the device indicated by the index lgpAgentDeviceIndex.
             lgpSysDeviceComponentSerialNum 1.3.6.1.4.1.476.1.42.3.7.9.1.1.3 displaystring read-only
This is the serial number of the component described by the OID 'lgpSysDeviceComponentDescr'. This data is intended for display / human consumption. Do not use this field for determining programmatic behavior.
             lgpSysDeviceComponentModelNum 1.3.6.1.4.1.476.1.42.3.7.9.1.1.4 displaystring read-only
This is the model identifier of the component described by the OID 'lgpSysDeviceComponentDescr'. This data is intended for display / human consumption. Do not use this field for determining programmatic behavior.
     lgpSysDeviceComponentWellknown 1.3.6.1.4.1.476.1.42.3.7.9.5
This sub-tree registers well known Liebert System Components.
         lgpSysDeviceBatCabinet 1.3.6.1.4.1.476.1.42.3.7.9.5.5
This sub-tree is used to register a battery cabinet component. To determine the cabinet being described in a multi-cabinet system, this point implements an additional two indexes. The first index describes the module the cabinet is located in. The second index describes the cabinet number. In an SMS (Single-Module System) the first index is always 1. Example: lgpSysDeviceComponentCabinet.2.4 'lgpSysDeviceCabinet' = Point is a battery cabinet. '.2' = Cabinet is in the second module. '.4' = Cabinet number 4 in second module
         lgpSysDeviceParallelCabinet 1.3.6.1.4.1.476.1.42.3.7.9.5.6
This sub-tree is used to register a parallel cabinet.
         lgpSysDeviceMaintBypass 1.3.6.1.4.1.476.1.42.3.7.9.5.7
This sub-tree is used to register the maintenance bypass.