ERICSSON-DISCOVERY-MIB

All MIBs › ERICSSON-DISCOVERY-MIB

Organization: Ericsson AB

Last Updated: 2016-01-13

Category: Vendor: Ericsson

Description: Manages network element auto-discovery and topology detection for Ericsson telecom and IP networking equipment.

Start monitoring vendor-neutral, standards-based MIB, any SNMPv3-capable network device (SNMP engine identity/boot/clock status) with a free 30-day trial of IPNetwork Monitor. Import MIBs, browse SNMP OIDs, create custom SNMP monitors, configure alerts, and monitor any SNMP-enabled network device from a single console.

What Is ERICSSON-DISCOVERY-MIB?

ERICSSON-DISCOVERY-MIB is an Ericsson AB proprietary MIB (built on ERICSSON-TOP-MIB) implementing an Ericsson-wide auto-discovery notification, sent during auto-integration or after a restart so a management system can discover and integrate a newly powered-on node. Its objects cover discovery status, node-ID type/value, security-context string and version, primary/secondary OAM IP address type/value, and a discovery-event notification, repeated by the agent until the management system acknowledges reception. As a notification MIB it lets a management system automatically discover and begin integrating a newly commissioned Ericsson network element. It is deployed on Ericsson AB network element equipment (auto-discovery/integration). Engineers can download the ERICSSON-DISCOVERY-MIB file directly to load it into their MIB browser.

IPNetwork Monitor allows you to monitor SNMP objects defined in ERICSSON-DISCOVERY-MIB. Use the built-in SNMP Monitoring Browser to explore available variables, view their current values and descriptions, and select the objects you want to monitor. You can then create SNMP monitors, configure thresholds, and receive alerts when monitored values change.

Supported Devices

Ericsson AB network element equipment (auto-discovery/integration)

Monitoring Examples

A management system receives eriDiscoveryEvent and reads eriDiscoveryNodeIpAddrOam1 to begin auto-integrating a newly powered-on Ericsson network element.

What Can Be Monitored

node auto-discovery and integration-acknowledgment status

Imported Objects

From ERICSSON-TOP-MIB

ericssonModules

OBJECT-IDENTITY

From INET-ADDRESS-MIB

InetAddress
InetAddressType

From SNMPv2-CONF

MODULE-COMPLIANCE
NOTIFICATION-GROUP
OBJECT-GROUP

From SNMPv2-SMI

Integer32
MODULE-IDENTITY
NOTIFICATION-TYPE
OBJECT-TYPE

From SNMPv2-TC

TEXTUAL-CONVENTION

OIDs

OID symbolic	OID numeric	Type	Access	Description
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
ERI 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
ERI eriDiscoveryNodeIdType	1.3.6.1.4.1.193.183.5.2.1	EriDiscoveryNodeIdTypeType	accessible-for-notify	The type of node ID value to expect in eriDiscoveryNodeIdValue
STR eriDiscoveryNodeIdValue	1.3.6.1.4.1.193.183.5.2.2	EriDiscoveryIdValueText	accessible-for-notify	The node ID value
ERI eriDiscoverySecCS	1.3.6.1.4.1.193.183.5.2.3	EriDiscoveryCheckSum	accessible-for-notify	The security check sum (SCC) calculated by the NE.
STR eriDiscoverySecCSVer	1.3.6.1.4.1.193.183.5.2.4	EriDiscoveryText16	accessible-for-notify	The version of the SCC. Only one version is currently supported, represented by the literal '1.0'
IPt eriDiscoveryNodeIpAddrOam1Type	1.3.6.1.4.1.193.183.5.2.5	InetAddressType	accessible-for-notify	The type of address used for O&M address 1 (see RFC 4001)
IP eriDiscoveryNodeIpAddrOam1	1.3.6.1.4.1.193.183.5.2.6	InetAddress	accessible-for-notify	The first O&M address of the node
eriDiscoveryOptionalObjects	1.3.6.1.4.1.193.183.5.3
IPt eriDiscoveryNodeIpAddrOam2Type	1.3.6.1.4.1.193.183.5.3.1	InetAddressType	accessible-for-notify	The type of address used for O&M address 2, if any (see RFC 4001)
IP eriDiscoveryNodeIpAddrOam2	1.3.6.1.4.1.193.183.5.3.2	InetAddress	accessible-for-notify	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
NTF 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

RFC description

Provides auto-discovery mechanism for Ericsson nodes during system integration and restart.

Start monitoring Ericsson AB network element (auto-discovery/integration) with a free 30-day trial of IPNetwork Monitor. Import MIBs, browse SNMP OIDs, create custom SNMP monitors, configure alerts, and monitor any SNMP-enabled network device from a single console.

Download ERICSSON-DISCOVERY-MIB

What Is ERICSSON-DISCOVERY-MIB?

Supported Devices

Monitoring Examples

What Can Be Monitored

This MIB depends on

Related MIBs

RFC description