ERICSSON-DISCOVERY-MIB
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
Main OID:
ericssonDiscoveryMIB.1.3.6.1.4.1.193.183.5
23
Objects
Active
Status
5
Dependencies
Imported Objects
Objects
23 total| Object Name |
|---|
ericssonDiscoveryMIBThis 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 MODULE-IDENTITY .1.3.6.1.4.1.193.183.5 |
eriDiscoveryControl OBJECT IDENTIFIER .1.3.6.1.4.1.193.183.5.1 |
eriDiscoveryStatusThis 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...rw EriDiscoveryStateValue .1.3.6.1.4.1.193.183.5.1.1 |
eriDiscoveryObjects OBJECT IDENTIFIER .1.3.6.1.4.1.193.183.5.2 |
eriDiscoveryNodeIdTypeThe type of node ID value to expect in eriDiscoveryNodeIdValuero EriDiscoveryNodeIdTypeType .1.3.6.1.4.1.193.183.5.2.1 |
eriDiscoveryNodeIdValueThe node ID valuero EriDiscoveryIdValueText -- 0..400 oct .1.3.6.1.4.1.193.183.5.2.2 |
eriDiscoverySecCSThe security check sum (SCC) calculated by the NE.ro EriDiscoveryCheckSum -- 32bit (4 oct) .1.3.6.1.4.1.193.183.5.2.3 |
eriDiscoverySecCSVerThe version of the SCC. Only one version is currently supported, represented by the literal '1.0'ro EriDiscoveryText16 -- 0..16 oct .1.3.6.1.4.1.193.183.5.2.4 |
eriDiscoveryNodeIpAddrOam1TypeThe type of address used for O&M address 1 (see RFC 4001)ro InetAddressType (INET-ADDRESS-MIB) .1.3.6.1.4.1.193.183.5.2.5 |
eriDiscoveryNodeIpAddrOam1The first O&M address of the nodero InetAddress (INET-ADDRESS-MIB) .1.3.6.1.4.1.193.183.5.2.6 |
eriDiscoveryOptionalObjects OBJECT IDENTIFIER .1.3.6.1.4.1.193.183.5.3 |
eriDiscoveryNodeIpAddrOam2TypeThe type of address used for O&M address 2, if any (see RFC 4001)ro InetAddressType (INET-ADDRESS-MIB) .1.3.6.1.4.1.193.183.5.3.1 |
eriDiscoveryNodeIpAddrOam2A second or alternative IP O&M address - if anyro InetAddress (INET-ADDRESS-MIB) .1.3.6.1.4.1.193.183.5.3.2 |
eriDiscoveryNotifications OBJECT IDENTIFIER .1.3.6.1.4.1.193.183.5.4 |
eriDiscoveryNotifsPrefix OBJECT IDENTIFIER .1.3.6.1.4.1.193.183.5.4.0 |
eriDiscoveryEventThis 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. NOTIFICATION-TYPE .1.3.6.1.4.1.193.183.5.4.0.1 |
eriDiscoveryMIBCompliances OBJECT IDENTIFIER .1.3.6.1.4.1.193.183.5.5 |
eriDiscoveryMIBComplianceGroups OBJECT IDENTIFIER .1.3.6.1.4.1.193.183.5.5.1 |
eriDiscoveryControlGroupObjects to control the discovery mechanism - mandatory to implement Unknown .1.3.6.1.4.1.193.183.5.5.1.1 |
eriDiscoveryEventContentGroup1Mandatory objects to include in the events Unknown .1.3.6.1.4.1.193.183.5.5.1.2 |
eriDiscoveryEventGroupMandatory events Unknown .1.3.6.1.4.1.193.183.5.5.1.3 |
eriDiscoveryEventOptionalContentGroup1Additional objects to send in the event Unknown .1.3.6.1.4.1.193.183.5.5.1.4 |
ericssonDiscoveryMIBBasicComplianceCompliance descriptions - mandatory groups and optional groups Unknown .1.3.6.1.4.1.193.183.5.5.2 |