CISCO-NHRP-EXT-MIB: View SNMP OID List / Download MIB

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)

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.

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).

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.

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).

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.

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).

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.

This object represents the reason for the NHRP entity to declare a next hop(NHRS or NHRC or NHP) as down.

This object represents the error code associated with the protocol message exchange for the error notification generated.

This table extends nhrpClientStatTable to provide additional statistics related to NHRP clients.

Each entry represents a conceptual row in cneClientStatExtTable table and provides additional statistics related to an NHRP client.

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.

This table extends nhrpServerStatTable to provide additional statistics related to NHRP servers.

Each entry represents a conceptual row in cneServerStatExtTable table and provides additional statistics related to an NHRP server.

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.

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. Bits: 'rateLimitExceeded': 6, 'nextHopRegClientUp': 2, 'nextHopPeerDown': 5, 'nextHopPeerUp': 4, 'nextHopRegClientDown': 3, 'nextHopRegServerUp': 0, 'nextHopRegServerDown': 1.

The compliance statement for the entities that implement the ciscoNhrpExtMIB module.

This group of objects provides information that is applicable to both NHRP clients and servers.

This group of objects provides information specific to NHRP clients.

This group of objects provides information specific to NHRP servers.

This group of objects is required to control the generation of notifications by NHRP agents.

This group of objects defines notifications generated by both NHRP clients and servers.

This group of objects defines notifications generated by NHRP clients.

This group of objects defines notifications generated by NHRP servers.