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).
Parsed from file CISCO-NHRP-EXT-MIB.mib
Module: CISCO-NHRP-EXT-MIB
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).
Parsed from file CISCO-NHRP-EXT-MIB.my.txt
Company: None
Module: CISCO-NHRP-EXT-MIB
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).
cneNotifNextHopPeerDown NOTIFICATION-TYPE OBJECTS { nhrpClientInternetworkAddrType, nhrpClientInternetworkAddr, nhrpClientNbmaAddrType, nhrpClientNbmaAddr, nhrpClientNbmaSubaddr, nhrpCacheNextHopInternetworkAddr, nhrpCacheNbmaAddrType, nhrpCacheNbmaAddr, nhrpCacheNbmaSubaddr, cneNextHopDownReason, cneNHRPException } STATUS current DESCRIPTION "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)." ::= { cneNotifs 6 }
Vendor: Cisco
Module: CISCO-NHRP-EXT-MIB
[Automatically extracted from oidview.com]
cneNotifNextHopPeerDown NOTIFICATION-TYPE OBJECTS { nhrpClientInternetworkAddrType, nhrpClientInternetworkAddr, nhrpClientNbmaAddrType, nhrpClientNbmaAddr, nhrpClientNbmaSubaddr, nhrpCacheNextHopInternetworkAddr, nhrpCacheNbmaAddrType, nhrpCacheNbmaAddr, nhrpCacheNbmaSubaddr, cneNextHopDownReason, cneNHRPException } STATUS current DESCRIPTION "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)." ::= { cneNotifs 6 }
cneNotifNextHopPeerDown NOTIFICATION-TYPE OBJECTS { nhrpClientInternetworkAddrType, nhrpClientInternetworkAddr, nhrpClientNbmaAddrType, nhrpClientNbmaAddr, nhrpClientNbmaSubaddr, nhrpCacheNextHopInternetworkAddr, nhrpCacheNbmaAddrType, nhrpCacheNbmaAddr, nhrpCacheNbmaSubaddr, cneNextHopDownReason, cneNHRPException } STATUS current DESCRIPTION "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)." ::= { cneNotifs 6 }
| OID | Name | Sub children | Sub Nodes Total | Description |
|---|---|---|---|---|
| 1.3.6.1.4.1.9.9.680.0.1 | cneNotifNextHopRegServerUp | 0 | 0 | This notification signifies that the SNMP entity, acting as an agent, has detected that one of its NHRP entities, acting as an NH… |
| 1.3.6.1.4.1.9.9.680.0.2 | cneNotifNextHopRegServerDown | 0 | 0 | This notification signifies that the SNMP entity, acting as an agent, has detected that that one of its NHRP entities, acting as … |
| 1.3.6.1.4.1.9.9.680.0.3 | cneNotifNextHopRegClientUp | 0 | 0 | This notification signifies that the SNMP entity, acting as an agent, has detected that one of its NHRP entities, acting as an NH… |
| 1.3.6.1.4.1.9.9.680.0.4 | cneNotifNextHopRegClientDown | 0 | 0 | This notification signifies that the SNMP entity, acting as an agent, has detected that one of its NHRP entities, acting as an NH… |
| 1.3.6.1.4.1.9.9.680.0.5 | cneNotifNextHopPeerUp | 0 | 0 | This notification signifies that the SNMP entity, acting as an agent, has detected that one of its NHRP entities perceives that i… |
| 1.3.6.1.4.1.9.9.680.0.7 | cneNotifRateLimitExceeded | 0 | 0 | This notification signifies that the SNMP entity, acting in an agent role, has detected that one of its NHRP entities(identified … |