ication signifies that the number
of available IP addresses for a particular scope
has fallen below the value of
cnrDHCPScopeFreeAddrLowThreshold for that scope.
          
This notification has been replaced by the 
ciscoNetRegFreeAddrLowThreshold notification.

ication signifies that a server has detected
via the failover protocol that its configuration does
not match that of its failover peer, and that reliable 
DHCP operation in the event of a server failure may not
be possible.  The identity of the peer server is given
by the cnrNotifServer or cnrNotifIPv6Server object. The
cnrNotifFailoverPairName object indicates failover
pair name. The cnrNotifFailoverCfgErrType object
indicates failover configuration error type.

ication signifies that the number
of available IP addresses for a particular scope
has fallen below the value of
cnrNotifDHCPScopeFreeAddrLow for that scope. 
          
This notification signals a shortage of addresses.
The shortage will continue until the number of free 
addresses has reached or exceeded the number 
specified by the cnrNotifDHCPScopeFreeAddrHigh object. 
This notification will only be generated when the 
shortages of IP addresses in first encountered.   
          
If the threshold type is scope or subnet, then the value is 
the primary or secondary subnet number, and if the type is  
selection-tag, then the value is the selection tag list.

ication signifies that the shortage of
available IP addresses for a particular scope is over and
generated when the number of free addresses for that scope
reaches or exceed value specified  by the 
cnrNotifDHCPScopeFreeAddrHigh.
          
This notification will only be generated when crossing the
threshold specified by the cnrNotifDHCPScopeFreeAddrHigh 
object indicates the end of IP address shortage.
          
If the threshold type is scope or subnet, then the value is 
the primary or secondary subnet number, and if the type is  
selection-tag, then the value is the selection tag list.

ication signifies that a server is not
responding to updates from the DHCP server.  This 
notification will be generated when this error 
is first encountered and suppressed until the 
the normal reponse from server has been established
as indicated by the ciscoNetRegOtherServerResp.
notification.
          
The identity of the server is given by the cnrNotifServer
or cnrNotifIPv6Server object. The type of the server is
indicated by the cnrNotifRelatedServerType object.

ication signifies that a server is now 
responding to updates from the DHCP server.  This 
notification will be generated when normal operation
is resumed after generation of the 
ciscoNetRegOtherServerNotResp notification.
          
The identity of the server is given by the cnrNotifServer
or cnrNotifIPv6Server object. The type of the server is
indicated by the cnrNotifRelatedServerType 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
ciscoNetRegOtherServerNotResp notifications being sent,
or in a ciscoNetRegOtherServerResp notification NOT
being sent.

ication signifies that communication with a 
HA-DNS (High Availability DNS) server's partner has been 
interrupted. The identity of the HA-DNS partner server is 
given by the cnrNotifServer or cnrNotifIPv6Server object.

ication signifies that communication with a 
HA-DNS server's partner has been restored. The identity 
of the HA-DNS partner server is given by the cnrNotifServer 
or cnrNotifIPv6Server object.

ication indicates that a DNS secondary server 
cannot reach any of its configured masters to obtain 
a zone transfer. Once this situation is encountered 
generation of this notification will be suppressed until
a complete zone transfer has completed as indicated by 
the ciscoNetRegMastersResp notification.
          
The identity of the secondary server is given by 
cnrNotifDnsServerIpAddress or cnrNotifDnsServerIp6Address;
the identity of the master servers is given by the
cnrNotifDnsRemoteServersList; and 
the zone is given by cnrNotifZoneName.

ication indicates that a DNS secondary server 
reached at least one of its configured masters and obtained
a zone transfer. This notification is generated the first 
time sucessful zone transfer completed after a prior request 
for zone transfer failed because master server could not
reached.
          
The identity of the secondary server is given by 
cnrNotifDnsServerIpAddress or cnrNotifDnsServerIp6Address;
the identity of the master servers is given by the
cnrNotifDnsRemoteServersList; and 
the zone is given by cnrNotifZoneName object.

ication indicates that a DNS secondary server was
unable to reach any primaries, and that a zone has expired
because the TTL has passed. 
          
The identity of the DNS secondary server is given by 
cnrNotifDnsServerIpAddress or cnrNotifDnsServerIp6Address;
the identity of the master servers is given by the
cnrNotifDnsRemoteServersList; and  
the zone is given by cnrNotifZoneName object.

ication signifies that the number
of available IP addresses for a particular scope
has risen above the value of
cnrDHCPScopeFreeAddrHighThreshold for that scope.
          
This notification has been replaced by the 
ciscoNetRegFreeAddrHighThreshold notification.

ication indicates that a DNS recursive resolver was
not able to reach any of its configured forwarders. Once this
situation is encountered generation of this notification will 
be suppressed until normal operation is resumed as indicated by 
the ciscoNetRegDnsForwardersResp notification.
          
The identity of the affected DNS resolving server is given by 
cnrNotifDnsServerIpAddress and the identity of the forwarders
is given by the cnrRemoteServersList object.

ication indicates that a DNS recursive resolver was 
able to reach at least one of its configured forwarders and 
indicates start of normal operation. This notification is 
generated the  first time normal operation is established after 
a DNS recursive resolver was not able to reach any of its 
configured forwarders.
          
The identity of the affected DNS resolving server is given by 
cnrNotifDnsServerIpAddress and the identity of the forwarders
is given by the cnrRemoteServersList object.

ication indicates a configuration mismatch between
two HA-DNS partners. The first zone that has a mismatch will
be reported and is denoted by cnrNotifZoneName and the 
server with the configuration error is denoted by 
cnrNotifServer or cnrNotifIPv6Server object.

ication indicates sync operation failure between
failover pair. Failure reason is denoted by cnrNotifSyncError.
cnrNotifFailoverPairName specifies the failover pair name.
cnrNotifMainIPAddress and cnrNotifMainIPv6Address specifies
the main server IPv4 and IPv6 address respectively.
cnrNotifBackupIPAddress and cnrNotifBackupIPv6Address specifies
the backup server IPv4 and IPv6 address respectively.
cnrNotifSyncDirection indicates the direction of sync
operation.

ication signifies that the server
of the specified type has started on the
host from which this notification has been sent.

ication signifies that the server
of the specified type has stopped normally on the
host from which this notification has been sent.

ication indicates that the number of pending
DNS updates has reached its limit.  Successive updates
may be dropped, and DHCP may stop responding to client
requests until this problem has cleared.

ication signifies that a server is not
responding to updates from the DHCP server.  The 
identity of the server is given by the cnrNotifServer
object.  The type of the server is given by the
cnrNotifServerType object.
          
This notification has been replaced by the 
ciscoNetRegOtherServerNotResp notification.

ication signifies that a duplicate IP address
has been detected.  The DHCP server can detect this
condition through the ping-before-offer mechanism.
Alternatively, the client may have sent a DHCPDECLINE 
back to the server; this is assumed to be the result of
the client detecting that the address was in use.  In
either case, the DHCP server marks the IP address as
unavailable for leasing to clients.  The
cnrNotifDupIpAddressDetectedBy object indicates whether
the client or server detected this condition.

ication indicates that the DHCP server on this
host, and a DHCP server on another host, have claimed
ownership for the same IP address.  The
cnrNotifContestedIpAddress object indicates which address
is under contention.  The cnrNotifServer or 
cnrNotifIPv6Server object indicates with which other 
server a conflict was detected. The
cnrNotifFailoverPairName object indicates failover
pair name.

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