This notification signifies that a server which had formerly
been in a 'not responding' state is now responding to
updates from the CNR protocol server. The identity of the
server is given by the cnrNotifServer object. The type of
the server is given by the cnrNotifServerType object.
NOTE: One should not rely on recieving this notification
as an indication that all is well with the network.
Several conditions, including restart of the CNR
protocol server, could result in either multiple
ciscoNetRegOtherServerNotResponding notifications being sent,
or in a ciscoNetRegOtherServerResponding notification NOT
being sent.
This notification has been replaced by the
ciscoNetRegOtherServerResp notification.
Parsed from file CISCO-NETWORK-REGISTRAR-MIB.mib
Module: CISCO-NETWORK-REGISTRAR-MIB
This notification signifies that a server which had formerly
been in a 'not responding' state is now responding to
updates from the CNR protocol server. The identity of the
server is given by the cnrNotifServer object. The type of
the server is given by the cnrNotifServerType object.
NOTE: One should not rely on recieving this notification
as an indication that all is well with the network.
Several conditions, including restart of the CNR
protocol server, could result in either multiple
ciscoNetRegOtherServerNotResponding notifications being sent,
or in a ciscoNetRegOtherServerResponding notification NOT
being sent.
This notification has been replaced by the
ciscoNetRegOtherServerResp notification.
Parsed from file CISCO-NETWORK-REGISTRAR-MIB.my.txt
Company: None
Module: CISCO-NETWORK-REGISTRAR-MIB
This notification signifies that a server which had formerly
been in a 'not responding' state is now responding to
updates from the CNR protocol server. The identity of the
server is given by the cnrNotifServer object. The type of
the server is given by the cnrNotifServerType object.
NOTE: One should not rely on recieving this notification
as an indication that all is well with the network.
Several conditions, including restart of the CNR
protocol server, could result in either multiple
ciscoNetRegOtherServerNotResponding notifications being sent,
or in a ciscoNetRegOtherServerResponding notification NOT
being sent.
This notification has been replaced by the
ciscoNetRegOtherServerResp notification.
ciscoNetRegOtherServerResponding NOTIFICATION-TYPE OBJECTS { cnrNotifServer, cnrNotifServerType } STATUS deprecated DESCRIPTION "This notification signifies that a server which had formerly been in a 'not responding' state is now responding to updates from the CNR protocol server. The identity of the server is given by the cnrNotifServer object. The type of the server is given by the cnrNotifServerType object. NOTE: One should not rely on recieving this notification as an indication that all is well with the network. Several conditions, including restart of the CNR protocol server, could result in either multiple ciscoNetRegOtherServerNotResponding notifications being sent, or in a ciscoNetRegOtherServerResponding notification NOT being sent. This notification has been replaced by the ciscoNetRegOtherServerResp notification. " ::= { ciscoNetRegMIBNotifications 9 }
Vendor: Cisco
Module: CISCO-NETWORK-REGISTRAR-MIB
[Automatically extracted from oidview.com]
ciscoNetRegOtherServerResponding NOTIFICATION-TYPE OBJECTS { cnrNotifServer, cnrNotifServerType } STATUS deprecated DESCRIPTION "This notification signifies that a server which had formerly been in a 'not responding' state is now responding to updates from the CNR protocol server. The identity of the server is given by the cnrNotifServer object. The type of the server is given by the cnrNotifServerType object. NOTE: One should not rely on recieving this notification as an indication that all is well with the network. Several conditions, including restart of the CNR protocol server, could result in either multiple ciscoNetRegOtherServerNotResponding notifications being sent, or in a ciscoNetRegOtherServerResponding notification NOT being sent. This notification has been replaced by the ciscoNetRegOtherServerResp notification. " ::= { ciscoNetRegMIBNotifications 9 }
ciscoNetRegOtherServerResponding NOTIFICATION-TYPE OBJECTS { cnrNotifServer, cnrNotifServerType } STATUS deprecated DESCRIPTION "This notification signifies that a server which had formerly been in a 'not responding' state is now responding to updates from the CNR protocol server. The identity of the server is given by the cnrNotifServer object. The type of the server is given by the cnrNotifServerType object. NOTE: One should not rely on recieving this notification as an indication that all is well with the network. Several conditions, including restart of the CNR protocol server, could result in either multiple ciscoNetRegOtherServerNotResponding notifications being sent, or in a ciscoNetRegOtherServerResponding notification NOT being sent. This notification has been replaced by the ciscoNetRegOtherServerResp notification. " ::= { ciscoNetRegMIBNotifications 9 }
| OID | Name | Sub children | Sub Nodes Total | Description |
|---|---|---|---|---|
| 1.3.6.1.4.1.9.9.120.2.0.1 | ciscoNetRegFreeAddressLow | 0 | 0 | This notification signifies that the number of available IP addresses for a particular scope has fallen below the value of cnrDHCP… |
| 1.3.6.1.4.1.9.9.120.2.0.2 | ciscoNetRegFreeAddressHigh | 0 | 0 | This notification signifies that the number of available IP addresses for a particular scope has risen above the value of cnrDHCPS… |
| 1.3.6.1.4.1.9.9.120.2.0.3 | ciscoNetRegServerStart | 0 | 0 | This notification signifies that the server of the specified type has started on the host from which this notification has been s… |
| 1.3.6.1.4.1.9.9.120.2.0.4 | ciscoNetRegServerStop | 0 | 0 | This notification signifies that the server of the specified type has stopped normally on the host from which this notification h… |
| 1.3.6.1.4.1.9.9.120.2.0.5 | ciscoNetRegDNSQueueTooBig | 0 | 0 | This notification indicates that the number of pending DNS updates has reached its limit. Successive updates may be dropped, and… |
| 1.3.6.1.4.1.9.9.120.2.0.6 | ciscoNetRegOtherServerNotResponding | 0 | 0 | This notification signifies that a server is not responding to updates from the DHCP server. The identity of the server is given… |
| 1.3.6.1.4.1.9.9.120.2.0.7 | ciscoNetRegDuplicateAddress | 0 | 0 | This notification signifies that a duplicate IP address has been detected. The DHCP server can detect this condition through the… |
| 1.3.6.1.4.1.9.9.120.2.0.8 | ciscoNetRegAddressConflict | 0 | 0 | This notification indicates that the DHCP server on this host, and a DHCP server on another host, have claimed ownership for the … |
| 1.3.6.1.4.1.9.9.120.2.0.10 | ciscoNetRegFailoverConfigMismatch | 0 | 0 | This notification signifies that a server has detected via the failover protocol that its configuration does not match that of it… |
| 1.3.6.1.4.1.9.9.120.2.0.11 | ciscoNetRegFreeAddrLowThreshold | 0 | 0 | This notification signifies that the number of available IP addresses for a particular scope has fallen below the value of cnrNoti… |
| 1.3.6.1.4.1.9.9.120.2.0.12 | ciscoNetRegFreeAddrHighThreshold | 0 | 0 | ciscoNetRegFreeAddrHighthreshold |
| 1.3.6.1.4.1.9.9.120.2.0.13 | ciscoNetRegOtherServerNotResp | 0 | 0 | This notification signifies that a server is not responding to updates from the DHCP server. This notification will be generated… |
| 1.3.6.1.4.1.9.9.120.2.0.14 | ciscoNetRegOtherServerResp | 0 | 0 | This notification signifies that a server is now responding to updates from the DHCP server. This notification will be generated… |
| 1.3.6.1.4.1.9.9.120.2.0.15 | ciscoNetRegHaDnsPartnerDown | 0 | 0 | This notification signifies that communication with a HA-DNS (High Availability DNS) server's partner has been interrupted. The i… |
| 1.3.6.1.4.1.9.9.120.2.0.16 | ciscoNetRegHaDnsPartnerUp | 0 | 0 | This notification signifies that communication with a HA-DNS server's partner has been restored. The identity of the HA-DNS partn… |
| 1.3.6.1.4.1.9.9.120.2.0.17 | ciscoNetRegMastersNotResp | 0 | 0 | This notification indicates that a DNS secondary server cannot reach any of its configured masters to obtain a zone transfer. Onc… |
| 1.3.6.1.4.1.9.9.120.2.0.18 | ciscoNetRegMastersResp | 0 | 0 | This notification indicates that a DNS secondary server reached at least one of its configured masters and obtained a zone transf… |
| 1.3.6.1.4.1.9.9.120.2.0.19 | ciscoNetRegSecondaryZonesExpired | 0 | 0 | This notification indicates that a DNS secondary server was unable to reach any primaries, and that a zone has expired because th… |
| 1.3.6.1.4.1.9.9.120.2.0.20 | ciscoNetRegDnsForwardersNotResp | 0 | 0 | This notification indicates that a DNS recursive resolver was not able to reach any of its configured forwarders. Once this situa… |
| 1.3.6.1.4.1.9.9.120.2.0.21 | ciscoNetRegDnsForwardersResp | 0 | 0 | This notification indicates that a DNS recursive resolver was able to reach at least one of its configured forwarders and indicat… |
| 1.3.6.1.4.1.9.9.120.2.0.22 | ciscoNetRegHaDnsConfigErr | 0 | 0 | This notification indicates a configuration mismatch between two HA-DNS partners. The first zone that has a mismatch will be repo… |