CISCO-NHRP-EXT-MIB

File: CISCO-NHRP-EXT-MIB.mib (30556 bytes)

Imported modules

SNMPv2-SMI SNMPv2-CONF NHRP-MIB
SNMPv2-TC IF-MIB CISCO-SMI

Imported symbols

MODULE-IDENTITY OBJECT-TYPE NOTIFICATION-TYPE
Counter32 MODULE-COMPLIANCE NOTIFICATION-GROUP
OBJECT-GROUP nhrpClientRegUniqueness nhrpClientNhsInternetworkAddr
nhrpClientNhsInternetworkAddrType nhrpClientNhsNbmaAddrType nhrpClientNhsNbmaAddr
nhrpClientNhsNbmaSubaddr nhrpClientIndex nhrpClientInternetworkAddrType
nhrpClientInternetworkAddr nhrpClientNbmaAddrType nhrpClientNbmaAddr
nhrpClientNbmaSubaddr nhrpClientHoldTime nhrpClientNhsInUse
nhrpServerNhcPrefixLength nhrpServerNhcInternetworkAddrType nhrpServerNhcInternetworkAddr
nhrpServerNhcNbmaAddrType nhrpServerNhcNbmaAddr nhrpServerNhcNbmaSubaddr
nhrpServerIndex nhrpServerInternetworkAddrType nhrpServerInternetworkAddr
nhrpServerNbmaAddrType nhrpServerNbmaAddr nhrpServerNbmaSubaddr
nhrpServerNhcInUse nhrpServerCacheUniqueness nhrpClientStatEntry
nhrpServerStatEntry nhrpCacheNextHopInternetworkAddr nhrpCacheNbmaAddrType
nhrpCacheNbmaAddr nhrpCacheNbmaSubaddr nhrpCacheType
TEXTUAL-CONVENTION ifIndex ifName
ciscoMgmt

Defined Types

CiscoNhrpErrorCode  
This textual convention is used to indicate the error code associated with failures as part of NHRP protocol messages exchanged in an NBMA network. The values of the enumeration have been chosen to match the values returned as error codes in an NHRP packet. The enumeration can take the following values. -- This indicates that the responder couldn't process an -- extension in the NHRP packet. unrecogExtension(1) Unrecognized extension -- This indicates that an NHRP packet is being forwarded -- in a loop. loopDetected(3) NHRP loop detected -- This indicates that the NHS has refused the NHRP -- Registration/Resolution Request attempt for -- administrative reasons. adminProhibited(4) Administrative reasons -- This indicates that the NHS can't serve a station due to -- lack of resources. insufficientResources(5) Insufficient resources -- This indicates that the protocol address of interest is -- not reachable. addressUnreachable(6) Protocol address unreachable -- This indicates that a generic packet processing error has -- occurred(e.g.failed checksum, invalid protocol type, etc). protocolError(7) Protocol Error -- This indicates that the SDU size of the NHRP packet -- exceeds the MTU size of the NBMA network. sduSizeExceeded(8) NHRP SDU size exceeded -- This indicates that an extension in a packet is -- inappropriate for that packet type. invalidExtension(9) Inappropriate packet type -- This indicates that a client received an NHRP resolution -- reply for a request which it didn't make. invalidResReply(10) Invalid NHRP resolution reply received -- This indicates that a received packet failed an -- authentication test. authFailure(11) Authentication failure -- This indicates that there were absolutely no -- internetworking layer address to NBMA address bindings -- found in the responding NHS's cache. noAddressBinding(12) No address binding present -- This indicates that there were one or more -- internetworking layer address to NBMA address bindings -- found in the responding NHS's cache but none of them had -- the uniqueness bit set. bindingNotUnique(13) Address binding not unique -- This indicates that the client tried to register a -- protocol address to NBMA address binding with the -- uniqueness bit on and the protocol address already exists -- in the NHS's cache(with the uniqueness bit set). uniqueInternetworkAddrRegd(14) Protocol address(with uniqueness bit set) already in cache -- This indicates that the hop count of an NHRP packet has -- been exceeded. hopCountExceeded(15) Hop count exceeded -- This indicates an error that doesn't fall into one of the -- above categories. other(256) Other errors
TEXTUAL-CONVENTION    
  INTEGER unrecogExtension(1), loopDetected(3), adminProhibited(4), insufficientResources(5), addressUnreachable(6), protocolError(7), sduSizeExceeded(8), invalidExtension(9), invalidResReply(10), authFailure(11), noAddressBinding(12), bindingNotUnique(13), uniqueInternetworkAddrRegd(14), hopCountExceeded(15), other(256)  

CiscoNextHopDownReasonCode  
This textual convention is used to indicate the reason code for a next hop(NHRS or NHRC or NHP) going down, as perceived by another NHRP entity. It can take the following values. -- This indicates administrative reasons such as manual -- deletion of address binding information. administrative(1) Administrative reasons -- This indicates that an NHRC's attempt to register with -- an NHRS has failed. The reason for this failure can be -- retrieved from cneNHRPException object. registrationFailure(2) NHRC's attempt to register failed -- This indicates that an attempt to resolve(or to get -- resolved) a destination address failed. The reason for -- this failure can be retrieved from cneNHRPException -- object. resolutionFailure(3) Address resolution failed -- This indicates that the address binding information was -- deleted as a consequence of a receipt of a purge request. purgeReceived(4) Received a purge request from the peer -- This indicates that the address binding information -- expired normally. normalExpiry(5) Address binding information expired normally -- This indicates that the status of the next hop being down -- was learnt from an external entity. external(6) Learnt from an external entity -- This indicates that the reason for declaring the next hop -- down is not one of the above. other(7) Other reasons
TEXTUAL-CONVENTION    
  INTEGER administrative(1), registrationFailure(2), resolutionFailure(3), purgeReceived(4), normalExpiry(5), external(6), other(7)  

CneClientStatExtEntry  
SEQUENCE    
  cneClientStatRedirectRx Counter32

CneServerStatExtEntry  
SEQUENCE    
  cneServerStatRedirectTx Counter32

Defined Values

ciscoNhrpExtMIB 1.3.6.1.4.1.9.9.680
This MIB module is an extension of the NHRP MIB module as defined in RFC 2677. It defines notifications associated with critical events in the Next Hop Resolution Protocol, NHRP, as defined in RFC 2332. This module also contains information about Cisco proprietary enhancements to the protocol. Glossary of terms used in this MIB: NBMA Non-Broadcast Multi-Access NHRP Next Hop Resolution Protocol Internetwork layer The media-independent layer(IP in case of TCP/IP networks) Subnetwork layer The media-dependent layer underlying the internetwork layer, including the NBMA technology NHC Next Hop Client - An entity which initiates NHRP requests of various types to obtain access to NHRP service. NHS Next Hop Server - An entity providing the NHRP service within the NBMA cloud. NHRC Next Hop Registration Client - An entity which initiates NHRP registration requests. NHRS Next Hop Registration Server - An entity for which an NHRP registration request is destined. NHP Next Hop Peer - Any two NHRP entities in an NBMA network which are not related by an NHRS-NHRC relationship(either of them has not registered with the other) are NHPs to each other. Client Unless explicitly stated or obvious from context, a client refers to an NHC Server Unless explicitly stated or obvious from context, a server refers to an NHS Station A station refers to a host or router which contains an NHRP entity(NHC/NHS) NHRC and NHRS are relevant to a client server model based on registrations alone, in which NHRC is a client and NHRS is a server. In case the use of any term is not clear from context or not explicitly stated, they mean the same as in RFC 2332 and RFC 2677. REFERENCE: [1] RFC 2332 - NBMA Next Hop Resolution Protocol (NHRP) [2] RFC 2677 - Definitions of Managed Objects for the NBMA Next Hop Resolution Protocol (NHRP)
MODULE-IDENTITY    

cneNotifs 1.3.6.1.4.1.9.9.680.0
OBJECT IDENTIFIER    

cneObjects 1.3.6.1.4.1.9.9.680.1
OBJECT IDENTIFIER    

cneConform 1.3.6.1.4.1.9.9.680.2
OBJECT IDENTIFIER    

cneGeneralObjects 1.3.6.1.4.1.9.9.680.1.1
OBJECT IDENTIFIER    

cneClientObjects 1.3.6.1.4.1.9.9.680.1.2
OBJECT IDENTIFIER    

cneServerObjects 1.3.6.1.4.1.9.9.680.1.3
OBJECT IDENTIFIER    

cneNotificationControlObjects 1.3.6.1.4.1.9.9.680.1.4
OBJECT IDENTIFIER    

cneNextHopDownReason 1.3.6.1.4.1.9.9.680.1.1.1
This object represents the reason for the NHRP entity to declare a next hop(NHRS or NHRC or NHP) as down.
OBJECT-TYPE    
  CiscoNextHopDownReasonCode  

cneNHRPException 1.3.6.1.4.1.9.9.680.1.1.2
This object represents the error code associated with the protocol message exchange for the error notification generated.
OBJECT-TYPE    
  CiscoNhrpErrorCode  

cneClientStatExtTable 1.3.6.1.4.1.9.9.680.1.2.1
This table extends nhrpClientStatTable to provide additional statistics related to NHRP clients.
OBJECT-TYPE    
  SEQUENCE OF  
    CneClientStatExtEntry

cneClientStatExtEntry 1.3.6.1.4.1.9.9.680.1.2.1.1
Each entry represents a conceptual row in cneClientStatExtTable table and provides additional statistics related to an NHRP client.
OBJECT-TYPE    
  CneClientStatExtEntry  

cneClientStatRedirectRx 1.3.6.1.4.1.9.9.680.1.2.1.1.1
This object represents the number of NHRP Redirects received by the client. Discontinuities in the value of this counter can occur at re-initialization of the management system, at NHRP Client re-initialization and at other times as indicated by the value of nhrpClientStatDiscontinuityTime.
OBJECT-TYPE    
  Counter32  

cneServerStatExtTable 1.3.6.1.4.1.9.9.680.1.3.1
This table extends nhrpServerStatTable to provide additional statistics related to NHRP servers.
OBJECT-TYPE    
  SEQUENCE OF  
    CneServerStatExtEntry

cneServerStatExtEntry 1.3.6.1.4.1.9.9.680.1.3.1.1
Each entry represents a conceptual row in cneServerStatExtTable table and provides additional statistics related to an NHRP server.
OBJECT-TYPE    
  CneServerStatExtEntry  

cneServerStatRedirectTx 1.3.6.1.4.1.9.9.680.1.3.1.1.1
This object represents the number of NHRP Redirects sent by the server. Discontinuities in the value of this counter can occur at re-initialization of the management system, at NHRP Client re-initialization and at other times as indicated by the value of nhrpServerStatDiscontinuityTime.
OBJECT-TYPE    
  Counter32  

cneNotifEnable 0.1.2.3.6.1.3.6.1.4.1.9.9.680.1.4.1
This object is used to control the generation of notifications defined in this MIB. The bits when set to 1 or 0 respectively enable or disable the corresponding notification. The mapping between the bits and the notifications are as follows. nextHopRegServerUp(0): This bit enables/disables the cneNotifNextHopRegServerUp notification. nextHopRegServerDown(1): This bit enables/disables the cneNotifNextHopRegServerDown notification. nextHopRegClientUp(2): This bit enables/disables the cneNotifNextHopRegClientUp notification. nextHopRegClientDown(3): This bit enables/disables the cneNotifNextHopRegClientDown notification. nextHopPeerUp(4): This bit enables/disables the cneNotifNextHopPeerUp notification. nextHopPeerDown(5): This bit enables/disables the cneNotifNextHopPeerDown notification. rateLimitExceeded(6): This bit enables/disables the cneNotifRateLimitExceeded notification.
OBJECT-TYPE    
  BITS nextHopRegServerUp(0), nextHopRegServerDown(1), nextHopRegClientUp(2), nextHopRegClientDown(3), nextHopPeerUp(4), nextHopPeerDown(5), rateLimitExceeded(6)  

cneNotifNextHopRegServerUp 1.3.6.1.4.1.9.9.680.0.1
This notification signifies that the SNMP entity, acting as an agent, has detected that one of its NHRP entities, acting as an NHRC, has successfully registered with an NHRS to which it was not already registered.
NOTIFICATION-TYPE    

cneNotifNextHopRegServerDown 1.3.6.1.4.1.9.9.680.0.2
This notification signifies that the SNMP entity, acting as an agent, has detected that that one of its NHRP entities, acting as a NHRC, has detected(by repeated registration retries or learnt from some other source(e.g. from a lower layer protocol)) that the NHRS it was registered to, or was trying to register to, is operationally down(from the NHRC's perspective). This notification doesn't indicate that the concerned NHRP server is down or unreachable or not even that it is unable to provide (other)NHRP services. It just indicates that the NHRC couldn't register successfully with the NHRS. This notification will be be sent only once for a down event i.e. two consecutive cneNotifNextHopRegServerDown notifications (for the same NHRS) must always be interspersed by a cneNotifNextHopRegServerUp notification(for the same NHRS).
NOTIFICATION-TYPE    

cneNotifNextHopRegClientUp 1.3.6.1.4.1.9.9.680.0.3
This notification signifies that the SNMP entity, acting as an agent, has detected that one of its NHRP entities, acting as an NHRS perceives that an NHRP entity(an NHRC), which was not already registered, has just now successfully registered.
NOTIFICATION-TYPE    

cneNotifNextHopRegClientDown 1.3.6.1.4.1.9.9.680.0.4
This notification signifies that the SNMP entity, acting as an agent, has detected that one of its NHRP entities, acting as an NHRS perceives that an NHRP entity, acting as an NHRC, is no more registered or failed to register. This notification will be be sent only once for a down event i.e. two consecutive cneNotifNextHopRegClientDown notifications (for the same NHRC) must always be interspersed by a cneNotifNextHopRegclientUp notification(for the same NHRC).
NOTIFICATION-TYPE    

cneNotifNextHopPeerUp 1.3.6.1.4.1.9.9.680.0.5
This notification signifies that the SNMP entity, acting as an agent, has detected that one of its NHRP entities perceives that it has learnt the protocol-to-NBMA address binding information for an NBMA next hop(which it didn't have). An NHRP entity might learn the same address binding information for a next hop peer as part of multiple address resolutions; this notification should be sent only when it first learns this address binding information.
NOTIFICATION-TYPE    

cneNotifNextHopPeerDown 1.3.6.1.4.1.9.9.680.0.6
This notification signifies that the SNMP entity, acting as an agent, has detected that one of its NHRP entities perceives that it has lost the protocol-to-NBMA address binding information for an NBMA next hop(which it earlier had). An NHRP entity might maintain multiple cache entries, with the same address binding information, for the same next hop peer (corresponding to different destinations reachable via this next hop peer); This notification will be be sent only when the address binding information is lost meaning only when all such entries are deleted. This notification will be be sent only once for a 'down' event i.e. two consecutive cneNotifNextHopPeerDown notifications (for the same NHP) must always be interspersed by a cneNotifNextHopUp notification(for the same NHP).
NOTIFICATION-TYPE    

cneNotifRateLimitExceeded 1.3.6.1.4.1.9.9.680.0.7
This notification signifies that the SNMP entity, acting in an agent role, has detected that one of its NHRP entities(identified by the ifIndex) has been very frequently reaching the threshold on the rate of NHRP protocol messages exchanged in an NBMA network. It is left to each individual implementation to determine the threshold frequency of this event(threshold being reached on the rate of NHRP protocol messages exchanged) which should result in a notification. The ifIndex object in this notification represents the use of a generic ifIndex which reflects a specific NBMA subnetwork related interface as determined by an implementation.
NOTIFICATION-TYPE    

cneCompliances 1.3.6.1.4.1.9.9.680.2.1
OBJECT IDENTIFIER    

cneGroups 1.3.6.1.4.1.9.9.680.2.2
OBJECT IDENTIFIER    

cneCompliance 1.3.6.1.4.1.9.9.680.2.1.1
The compliance statement for the entities that implement the ciscoNhrpExtMIB module.
MODULE-COMPLIANCE    

cneGeneralGroup 1.3.6.1.4.1.9.9.680.2.2.1
This group of objects provides information that is applicable to both NHRP clients and servers.
OBJECT-GROUP    

cneClientGroup 1.3.6.1.4.1.9.9.680.2.2.2
This group of objects provides information specific to NHRP clients.
OBJECT-GROUP    

cneServerGroup 1.3.6.1.4.1.9.9.680.2.2.3
This group of objects provides information specific to NHRP servers.
OBJECT-GROUP    

cneNotificationControlGroup 1.3.6.1.4.1.9.9.680.2.2.4
This group of objects is required to control the generation of notifications by NHRP agents.
OBJECT-GROUP    

cneGeneralNotificationGroup 1.3.6.1.4.1.9.9.680.2.2.5
This group of objects defines notifications generated by both NHRP clients and servers.
NOTIFICATION-GROUP    

cneClientNotificationGroup 1.3.6.1.4.1.9.9.680.2.2.6
This group of objects defines notifications generated by NHRP clients.
NOTIFICATION-GROUP    

cneServerNotificationGroup 1.3.6.1.4.1.9.9.680.2.2.7
This group of objects defines notifications generated by NHRP servers.
NOTIFICATION-GROUP