ERICSSON-DISCOVERY-MIB

File: ERICSSON-DISCOVERY-MIB.mib (16173 bytes)

Imported modules

SNMPv2-SMI SNMPv2-TC INET-ADDRESS-MIB
ERICSSON-TOP-MIB SNMPv2-CONF

Imported symbols

MODULE-IDENTITY OBJECT-TYPE NOTIFICATION-TYPE
Integer32 TEXTUAL-CONVENTION InetAddress
InetAddressType ericssonModules OBJECT-GROUP
NOTIFICATION-GROUP MODULE-COMPLIANCE

Defined Types

EriDiscoveryStateValue  
Values for indicating if the node is currently issuing discovery messages or not.
TEXTUAL-CONVENTION    
  INTEGER disabled(0), enabled(1)  

EriDiscoveryNodeIdTypeType  
The Node ID can be identified using several types of ID values. This TC lists the alternative value types.
TEXTUAL-CONVENTION    
  INTEGER unknown(0), serialNumber(1), fdn(2)  

EriDiscoveryText16  
ASCII string data of max length 16 octets.
TEXTUAL-CONVENTION    
  OCTET STRING Size(0..16)  

EriDiscoveryIdValueText  
ASCII string data of max length 400 octets.
TEXTUAL-CONVENTION    
  OCTET STRING Size(0..400)  

EriDiscoveryCheckSum  
32 bit checksum value
TEXTUAL-CONVENTION    
  Integer32  

Defined Values

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
MODULE-IDENTITY    

eriDiscoveryControl 1.3.6.1.4.1.193.183.5.1
OBJECT IDENTIFIER    

eriDiscoveryObjects 1.3.6.1.4.1.193.183.5.2
OBJECT IDENTIFIER    

eriDiscoveryOptionalObjects 1.3.6.1.4.1.193.183.5.3
OBJECT IDENTIFIER    

eriDiscoveryNotifications 1.3.6.1.4.1.193.183.5.4
OBJECT IDENTIFIER    

eriDiscoveryMIBCompliances 1.3.6.1.4.1.193.183.5.5
OBJECT IDENTIFIER    

eriDiscoveryNotifsPrefix 1.3.6.1.4.1.193.183.5.4.0
OBJECT IDENTIFIER    

eriDiscoveryStatus 1.3.6.1.4.1.193.183.5.1.1
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...
Status: current Access: read-write
OBJECT-TYPE    
  EriDiscoveryStateValue  

eriDiscoveryNodeIdType 1.3.6.1.4.1.193.183.5.2.1
The type of node ID value to expect in eriDiscoveryNodeIdValue
Status: current Access: accessible-for-notify
OBJECT-TYPE    
  EriDiscoveryNodeIdTypeType  

eriDiscoveryNodeIdValue 1.3.6.1.4.1.193.183.5.2.2
The node ID value
Status: current Access: accessible-for-notify
OBJECT-TYPE    
  EriDiscoveryIdValueText  

eriDiscoverySecCS 1.3.6.1.4.1.193.183.5.2.3
The security check sum (SCC) calculated by the NE.
Status: current Access: accessible-for-notify
OBJECT-TYPE    
  EriDiscoveryCheckSum  

eriDiscoverySecCSVer 1.3.6.1.4.1.193.183.5.2.4
The version of the SCC. Only one version is currently supported, represented by the literal '1.0'
Status: current Access: accessible-for-notify
OBJECT-TYPE    
  EriDiscoveryText16  

eriDiscoveryNodeIpAddrOam1Type 1.3.6.1.4.1.193.183.5.2.5
The type of address used for O&M address 1 (see RFC 4001)
Status: current Access: accessible-for-notify
OBJECT-TYPE    
  InetAddressType  

eriDiscoveryNodeIpAddrOam1 1.3.6.1.4.1.193.183.5.2.6
The first O&M address of the node
Status: current Access: accessible-for-notify
OBJECT-TYPE    
  InetAddress  

eriDiscoveryNodeIpAddrOam2Type 1.3.6.1.4.1.193.183.5.3.1
The type of address used for O&M address 2, if any (see RFC 4001)
Status: current Access: accessible-for-notify
OBJECT-TYPE    
  InetAddressType  

eriDiscoveryNodeIpAddrOam2 1.3.6.1.4.1.193.183.5.3.2
A second or alternative IP O&M address - if any
Status: current Access: accessible-for-notify
OBJECT-TYPE    
  InetAddress  

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.
Status: current Access: accessible-for-notify
NOTIFICATION-TYPE    

eriDiscoveryMIBComplianceGroups 1.3.6.1.4.1.193.183.5.5.1
OBJECT IDENTIFIER    

eriDiscoveryControlGroup 1.3.6.1.4.1.193.183.5.5.1.1
Objects to control the discovery mechanism - mandatory to implement
Status: current Access: accessible-for-notify
OBJECT-GROUP    

eriDiscoveryEventContentGroup1 1.3.6.1.4.1.193.183.5.5.1.2
Mandatory objects to include in the events
Status: current Access: accessible-for-notify
OBJECT-GROUP    

eriDiscoveryEventGroup 1.3.6.1.4.1.193.183.5.5.1.3
Mandatory events
Status: current Access: accessible-for-notify
NOTIFICATION-GROUP    

eriDiscoveryEventOptionalContentGroup1 1.3.6.1.4.1.193.183.5.5.1.4
Additional objects to send in the event
Status: current Access: accessible-for-notify
OBJECT-GROUP    

ericssonDiscoveryMIBBasicCompliance 1.3.6.1.4.1.193.183.5.5.2
Compliance descriptions - mandatory groups and optional groups
Status: current Access: accessible-for-notify
MODULE-COMPLIANCE