PSAX-DS2-MIB: View SNMP OID List / Download MIB

VENDOR: LUCENT TECHNOLOGIES


 Home MIB: PSAX-DS2-MIB
Download as:   
SNMPv2-SMI, RFC1155-SMI, RFC-1212, RFC1213-MIB, SNMPv2-TC

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
 lucent 1.3.6.1.4.1.1751
           products 1.3.6.1.4.1.1751.1
               softSwitch 1.3.6.1.4.1.1751.1.1198
                         psaxDeviceServer 1.3.6.1.4.1.1751.1.1198.6
                             psaxDS2 1.3.6.1.4.1.1751.1.1198.6.2
The MIB module for entities implementing the xxxx protocol.
                                 psaxSystem 1.3.6.1.4.1.1751.1.1198.6.2.1
                                     dsInfo 1.3.6.1.4.1.1751.1.1198.6.2.1.1
Device Server information. This value should include the full name and version identification and/or manufacturer information. It is mandatory that this contains only printable ASCII characters
                                     dsProtocolInfo 1.3.6.1.4.1.1751.1.1198.6.2.1.2
Device Server PSAX/SIP stack information. This value should include the full name and version identification and/or manufacturer information of the PSAX/SIP Stack used in the device server implementation. It is mandatory that this contains only printable ASCII characters
                                     logLevel 1.3.6.1.4.1.1751.1.1198.6.2.1.3
Device Server Log Level. A minimum logging level is always set for the device servers, which logs errors and warnings. If still more verbosity is required, that can be done by setting this parameter to a required level. 1. Error 2. Warning 3. Info
                                     succeededCalls 1.3.6.1.4.1.1751.1.1198.6.2.1.4
Total number of calls successfully made since the last uptime of this device server.
                                     activeCalls 1.3.6.1.4.1.1751.1.1198.6.2.1.5
Number of calls which are still progressing at this time by this device server
                                     failedCalls 1.3.6.1.4.1.1751.1.1198.6.2.1.6
Total Number of calls failed since the last uptime of this device server
                                     reloadConfig 1.3.6.1.4.1.1751.1.1198.6.2.1.7
This is to tell the device server to load its configuration again. This is done when some configuration parameters need to be updated in the system
                                     gatewayDelete 1.3.6.1.4.1.1751.1.1198.6.2.1.8
Informs the device server to delete the entry of the gateway from the configuration file
                                     resetLog 1.3.6.1.4.1.1751.1.1198.6.2.1.9
To discard previous log and to start logging afresh resetLog would be used