ciscoNetRegDNSQueueTooBig
CISCO-NETWORK-REGISTRAR-MIB ·
.1.3.6.1.4.1.9.9.120.2.0.5
Object
notification
This notification 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.
Context
- MIB
- CISCO-NETWORK-REGISTRAR-MIB
- OID
.1.3.6.1.4.1.9.9.120.2.0.5- Type
- notification
- Status
- current
- Parent
- ciscoNetRegMIBNotifications
- Siblings
- 22
Syntax
No syntax metadata recorded.
Values & Constraints
No enumerated values or constraints recorded.
Related Objects
Sibling Objects
| Object | Type | Syntax | OID |
|---|---|---|---|
| ciscoNetRegFreeAddressLow deprecated This notification signifies that the number
of available IP addresses for a particular scope
has fallen below the value of
cnrDHCPScopeFreeAddrLowThreshold for that scope.
… | notification | - | .1.3.6.1.4.1.9.9.120.2.0.1 |
| ciscoNetRegFailoverConfigMismatch This notification 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… | notification | - | .1.3.6.1.4.1.9.9.120.2.0.10 |
| ciscoNetRegFreeAddrLowThreshold This notification signifies that the number
of available IP addresses for a particular scope
has fallen below the value of
cnrNotifDHCPScopeFreeAddrLow for that scope.
… | notification | - | .1.3.6.1.4.1.9.9.120.2.0.11 |
| ciscoNetRegFreeAddrHighThreshold This notification 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 ex… | notification | - | .1.3.6.1.4.1.9.9.120.2.0.12 |
| ciscoNetRegOtherServerNotResp This notification 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 suppre… | notification | - | .1.3.6.1.4.1.9.9.120.2.0.13 |
| ciscoNetRegOtherServerResp This notification signifies that a server is now
responding to updates from the DHCP server. This
notification will be generated when normal operation
is resumed after generati… | notification | - | .1.3.6.1.4.1.9.9.120.2.0.14 |
| ciscoNetRegHaDnsPartnerDown This notification 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 b… | notification | - | .1.3.6.1.4.1.9.9.120.2.0.15 |
| ciscoNetRegHaDnsPartnerUp This notification 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 cnr… | notification | - | .1.3.6.1.4.1.9.9.120.2.0.16 |
| ciscoNetRegMastersNotResp This notification 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 t… | notification | - | .1.3.6.1.4.1.9.9.120.2.0.17 |
| ciscoNetRegMastersResp This notification 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
tim… | notification | - | .1.3.6.1.4.1.9.9.120.2.0.18 |
| ciscoNetRegSecondaryZonesExpired This notification 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 … | notification | - | .1.3.6.1.4.1.9.9.120.2.0.19 |
| ciscoNetRegFreeAddressHigh deprecated This notification signifies that the number
of available IP addresses for a particular scope
has risen above the value of
cnrDHCPScopeFreeAddrHighThreshold for that scope.
… | notification | - | .1.3.6.1.4.1.9.9.120.2.0.2 |
| ciscoNetRegDnsForwardersNotResp deprecated This notification indicates that a DNS recursive resolver was
not able to reach any of its configured forwarders. Once this
situation is encountered generation of this notificatio… | notification | - | .1.3.6.1.4.1.9.9.120.2.0.20 |
| ciscoNetRegDnsForwardersResp deprecated This notification 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 … | notification | - | .1.3.6.1.4.1.9.9.120.2.0.21 |
| ciscoNetRegHaDnsConfigErr This notification 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
s… | notification | - | .1.3.6.1.4.1.9.9.120.2.0.22 |
| ciscoNetRegFailoverSyncFailure This notification indicates sync operation failure between
failover pair. Failure reason is denoted by cnrNotifSyncError.
cnrNotifFailoverPairName specifies the failover pair name… | notification | - | .1.3.6.1.4.1.9.9.120.2.0.23 |
| ciscoNetRegServerStart This notification signifies that the server
of the specified type has started on the
host from which this notification has been sent. | notification | - | .1.3.6.1.4.1.9.9.120.2.0.3 |
| ciscoNetRegServerStop This notification signifies that the server
of the specified type has stopped normally on the
host from which this notification has been sent. | notification | - | .1.3.6.1.4.1.9.9.120.2.0.4 |
| ciscoNetRegOtherServerNotResponding deprecated This notification 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 s… | notification | - | .1.3.6.1.4.1.9.9.120.2.0.6 |
| ciscoNetRegDuplicateAddress This notification signifies that a duplicate IP address
has been detected. The DHCP server can detect this
condition through the ping-before-offer mechanism.
Alternatively, the c… | notification | - | .1.3.6.1.4.1.9.9.120.2.0.7 |
| ciscoNetRegAddressConflict This notification 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 o… | notification | - | .1.3.6.1.4.1.9.9.120.2.0.8 |
| ciscoNetRegOtherServerResponding deprecated 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
serve… | notification | - | .1.3.6.1.4.1.9.9.120.2.0.9 |