ERICSSON-DISCOVERY-MIB: View SNMP OID List / Download MIB

VENDOR: ERICSSON AB


 Home MIB: ERICSSON-DISCOVERY-MIB
Download as:   
SNMPv2-CONF, ERICSSON-TOP-MIB, SNMPv2-SMI, INET-ADDRESS-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
 ericssonDiscoveryMIB 1.3.6.1.4.1.193.183.5
This MIB Module is an Ericsson-wide SNMP interface for auto discovery of nodes during an auto integration procedure or after restart. It describes the notification used to send an intial discovery message to a management system, and an optional mechanism for a management system to acknowledge the reception of this message and that the integration process is started. A few alternative (node type specific) variants of the discovery message is expected over time, modeled as optional parts in the message. The agent is expected to repeatedly send the discovery message untill reception has been acknoleged by the management system through the optional mechanism in this MIB or by an other node specific mechanism. See eriDiscoveryStatus for detailes. The frequency at which to send dicovery messages is implementation specific, but must not be more often than one message per minute or more seldom than one message per hour. MIB Product number in GASK: n/nnn nn-CXC nnn nnnn, Rev x
     eriDiscoveryControl 1.3.6.1.4.1.193.183.5.1
         eriDiscoveryStatus 1.3.6.1.4.1.193.183.5.1.1 eridiscoverystatevalue read-write
This object shows if discovery messages are beeing issued from the node or not. A manager may turn off issuing of discovery messages by setting this object to disabled(0). The node may conclude that discovery has succeeded by other means of communication with a manager and will then indicate that by changing this value to disabled(0). If a manager sets this value to enabled(1) the node may choose to resume sending of discovery messages - or it may deny such a request by immediately reseting this value to disabled(0). Open issue: Shall we have this flexibility - or shall we mandate the possibility to re-start the dicovery process? It's good for testing and some error scenarios, but may have security implications and impacts on OSS, so we have to decide...
     eriDiscoveryObjects 1.3.6.1.4.1.193.183.5.2
         eriDiscoveryNodeIdType 1.3.6.1.4.1.193.183.5.2.1 eridiscoverynodeidtypetype no-access
The type of node ID value to expect in eriDiscoveryNodeIdValue
         eriDiscoveryNodeIdValue 1.3.6.1.4.1.193.183.5.2.2 eridiscoveryidvaluetext no-access
The node ID value
         eriDiscoverySecCS 1.3.6.1.4.1.193.183.5.2.3 eridiscoverychecksum no-access
The security check sum (SCC) calculated by the NE.
         eriDiscoverySecCSVer 1.3.6.1.4.1.193.183.5.2.4 eridiscoverytext16 no-access
The version of the SCC. Only one version is currently supported, represented by the literal '1.0'
         eriDiscoveryNodeIpAddrOam1Type 1.3.6.1.4.1.193.183.5.2.5 inetaddresstype no-access
The type of address used for O&M address 1 (see RFC 4001)
         eriDiscoveryNodeIpAddrOam1 1.3.6.1.4.1.193.183.5.2.6 inetaddress no-access
The first O&M address of the node
     eriDiscoveryOptionalObjects 1.3.6.1.4.1.193.183.5.3
         eriDiscoveryNodeIpAddrOam2Type 1.3.6.1.4.1.193.183.5.3.1 inetaddresstype no-access
The type of address used for O&M address 2, if any (see RFC 4001)
         eriDiscoveryNodeIpAddrOam2 1.3.6.1.4.1.193.183.5.3.2 inetaddress no-access
A second or alternative IP O&M address - if any
     eriDiscoveryNotifications 1.3.6.1.4.1.193.183.5.4
         eriDiscoveryNotifsPrefix 1.3.6.1.4.1.193.183.5.4.0
             eriDiscoveryEvent 1.3.6.1.4.1.193.183.5.4.0.1
This is the discovery notification sent from a node supporting auto dicovery and integration regardless of node type and radio standard. It is asumed that some data has been prepared in an OSS to recognise the node by the ID. Future revisions may add attributes to this MIB not used by all node types.
     eriDiscoveryMIBCompliances 1.3.6.1.4.1.193.183.5.5
         eriDiscoveryMIBComplianceGroups 1.3.6.1.4.1.193.183.5.5.1
             eriDiscoveryControlGroup 1.3.6.1.4.1.193.183.5.5.1.1
Objects to control the discovery mechanism - mandatory to implement
             eriDiscoveryEventContentGroup1 1.3.6.1.4.1.193.183.5.5.1.2
Mandatory objects to include in the events
             eriDiscoveryEventGroup 1.3.6.1.4.1.193.183.5.5.1.3
Mandatory events
             eriDiscoveryEventOptionalContentGroup1 1.3.6.1.4.1.193.183.5.5.1.4
Additional objects to send in the event
         ericssonDiscoveryMIBBasicCompliance 1.3.6.1.4.1.193.183.5.5.2
Compliance descriptions - mandatory groups and optional groups