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).
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 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).
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 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).
cneNotifNextHopRegServerDown NOTIFICATION-TYPE OBJECTS { nhrpClientInternetworkAddrType, nhrpClientInternetworkAddr, nhrpClientNbmaAddrType, nhrpClientNbmaAddr, nhrpClientNbmaSubaddr, nhrpClientNhsInternetworkAddrType, nhrpClientNhsInternetworkAddr, nhrpClientNhsNbmaAddrType, nhrpClientNhsNbmaAddr, nhrpClientNhsNbmaSubaddr, cneNextHopDownReason, cneNHRPException } STATUS current DESCRIPTION "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)." ::= { cneNotifs 2 }
Vendor: Cisco
Module: CISCO-NHRP-EXT-MIB
[Automatically extracted from oidview.com]
cneNotifNextHopRegServerDown NOTIFICATION-TYPE OBJECTS { nhrpClientInternetworkAddrType, nhrpClientInternetworkAddr, nhrpClientNbmaAddrType, nhrpClientNbmaAddr, nhrpClientNbmaSubaddr, nhrpClientNhsInternetworkAddrType, nhrpClientNhsInternetworkAddr, nhrpClientNhsNbmaAddrType, nhrpClientNhsNbmaAddr, nhrpClientNhsNbmaSubaddr, cneNextHopDownReason, cneNHRPException } STATUS current DESCRIPTION "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)." ::= { cneNotifs 2 }
cneNotifNextHopRegServerDown NOTIFICATION-TYPE OBJECTS { nhrpClientInternetworkAddrType, nhrpClientInternetworkAddr, nhrpClientNbmaAddrType, nhrpClientNbmaAddr, nhrpClientNbmaSubaddr, nhrpClientNhsInternetworkAddrType, nhrpClientNhsInternetworkAddr, nhrpClientNhsNbmaAddrType, nhrpClientNhsNbmaAddr, nhrpClientNhsNbmaSubaddr, cneNextHopDownReason, cneNHRPException } STATUS current DESCRIPTION "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)." ::= { cneNotifs 2 }
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.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.6 | cneNotifNextHopPeerDown | 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 … |