CISCO-NETWORK-REGISTRAR-MIB
AI MIB Summary
The CISCO-NETWORK-REGISTRAR-MIB facilitates the monitoring and management of the Cisco Network Registrar (CNR) service, specifically tracking DHCP, DNS, and IP address management (IPAM) operational states, lease statistics, and server availability. It provides granular visibility into CNR subsystem performance, including transaction counters, error logs, and configuration integrity for dynamic host configuration and domain name resolution services.
MIB for Cisco Network Registrar (CNR).
Main OID:
ciscoNetworkRegistrarMIB.1.3.6.1.4.1.9.9.120
78
Objects
Active
Status
4
Dependencies
Imported Objects
Objects
78 total| Object Name |
|---|
ciscoNetworkRegistrarMIBMIB for Cisco Network Registrar (CNR). MODULE-IDENTITY .1.3.6.1.4.1.9.9.120 |
ciscoNetworkRegistrarMIBObjects OBJECT IDENTIFIER .1.3.6.1.4.1.9.9.120.1 |
cnrDHCP OBJECT IDENTIFIER .1.3.6.1.4.1.9.9.120.1.1 |
cnrDHCPScopeTableThe table listing characteristics of all scopes.
Entries in this table correspond to scopes, which are
added and deleted via the CNR GUI or CLI.deprecated SEQUENCE OF CnrDHCPScopeEntry .1.3.6.1.4.1.9.9.120.1.1.1 |
cnrDHCPScopeEntryAn entry in the cnrDHCPScopeTable.deprecated CnrDHCPScopeEntry .1.3.6.1.4.1.9.9.120.1.1.1.1 |
cnrDHCPScopeNameThe name of the scope, which uniquely identifies
an entry in the cnrDHCPScopeTable.deprecated DisplayString .1.3.6.1.4.1.9.9.120.1.1.1.1.1 |
cnrDHCPScopeFreeAddrLowThresholdThe low threshold for available free addresses in
this scope. If the value for available free addresses
in this scope becomes equal to or less than this value,
a cnrDHCPScopeFreeAddrLowThreshold event is generated
for this scope. No more cnrDHCPScopeFreeAddrLowThreshold
events will be generated for this scope during this
execution of the DHCP server until the value for available
free addresses has exceeded the value of
cnrDHCPScopeFreeAddrHighThreshold.
This value may be expressed as either an absolute value
or a percentage; the units are specified by the value of
cnrDHCPScopeFreeAddrUnits.rodeprecated Unsigned32 .1.3.6.1.4.1.9.9.120.1.1.1.1.2 |
cnrDHCPScopeFreeAddrHighThresholdThe high threshold for available free addresses in this
scope. If a cnrDHCPScopeFreeAddrLowThreshold event has
been generated for this scope, and the value for available
free addresses has exceeded the value of
cnrDHCPScopeFreeAddrHighThreshold, then a
ciscoNetRegFreeAddressHigh event will be generated. No
more ciscoNetRegFreeAddressHigh events will be generated
for this scope during this execution of the DHCP server
until the value for available free addresses becomes equal
to or less than the value of
cnrDHCPScopeFreeAddrHighThreshold.
This value may be expressed as either an absolute value
or a percentage; the units are specified by the value of
cnrDHCPScopeFreeAddrUnits.rodeprecated Unsigned32 .1.3.6.1.4.1.9.9.120.1.1.1.1.3 |
cnrDHCPScopeFreeAddrValueThe number of IP addresses which are available
within this scope. May be expressed as either
an absolute value or a percentage; the units are
given by the value of cnrDHCPScopeFreeAddrUnits.rodeprecated Unsigned32 .1.3.6.1.4.1.9.9.120.1.1.1.1.4 |
cnrDHCPScopeFreeAddrUnitsThe units associated with the value of
cnrDHCPScopeFreeAddrValue.rodeprecated Enumeration .1.3.6.1.4.1.9.9.120.1.1.1.1.5 |
cnrNotifObjects OBJECT IDENTIFIER .1.3.6.1.4.1.9.9.120.1.2 |
cnrNotifDupIpAddressThe IP address which was found to be a duplicate.ro IpAddress .1.3.6.1.4.1.9.9.120.1.2.1 |
cnrNotifMACAddressThe offending MAC address which caused a duplicate IP
address to be detected.ro CnrPhysAddress .1.3.6.1.4.1.9.9.120.1.2.2 |
cnrNotifServerThe IP Address of a server with which CNR
is attempting to communicate.ro IpAddress .1.3.6.1.4.1.9.9.120.1.2.3 |
cnrNotifServerTypeThe type of server.ro Enumeration .1.3.6.1.4.1.9.9.120.1.2.4 |
cnrNotifDupIpAddressDetectedByFor a ciscoNetRegDuplicateAddress notification, this
object indicates whether the client or server detected
the condition.ro Enumeration .1.3.6.1.4.1.9.9.120.1.2.5 |
cnrNotifContestedIpAddressThe IP address for which ownership is claimed by two or
more DHCP servers.ro IpAddress .1.3.6.1.4.1.9.9.120.1.2.6 |
cnrNotifDHCPScopeFreeAddrLowThis object is used to determine the start of the
address shortage condition. When the number of free
addresses is equal to or less than the value contained
by this object the ciscoNetRegFreeAddrLowThreshold
notification will be generated. The low address condition
will continue until the number of free addresses has reached
or exceeded the number specified by the
cnrNotifDHCPScopeFreeAddrHigh object. The
ciscoNetRegFreeAddrLowThreshold notification will only be
generated when the low address condition is first
encountered.
These thresholds objects and notifications apply to scopes
defined for the DHCP server. The cnrDHCPScope object
indicates to which scope these objects and notifications
are to be applied.ro Unsigned32 UNITS "percentage" .1.3.6.1.4.1.9.9.120.1.2.7 |
cnrNotifDHCPScopeFreeAddrHighThis object is used to determine the end of address shortage.
When the number of free addresses is equal to or greater
than the value contained by this object the
ciscoNetRegFreeAddrHighThreshold notification will be
generated. The ciscoNetRegFreeAddrHighThreshold
notification will only be generated when the first time
the cnrNotifDHCPScopeFreeAddrHigh is exceeded.
These thresholds objects and notifications apply to scopes
defined for the DHCP server. The cnrDHCPScope object
indicates to which scope these objects and notifications
are to be applied.ro Unsigned32 UNITS "percentage" .1.3.6.1.4.1.9.9.120.1.2.8 |
cnrNotifDHCPScopeFreeAddrValueThe number of IP addresses which are available
within the scope specified by the cnrDHCPScope object.ro Gauge32 UNITS "IP addresses" .1.3.6.1.4.1.9.9.120.1.2.9 |
cnrNotifDHCPThresholdTypeThe type of threshold that is causing the notification.
Threshold is configured based on the following types:
Type Threshold Configuration
scope level of single scope
network level of an entire group of scopes sharing
the same primary subnet
selectionTags level of a group of scopes sharing the same
primary subnet and selection tags.ro Enumeration .1.3.6.1.4.1.9.9.120.1.2.10 |
cnrNotifDHCPThresholdValueThe value of the type of threshold that is causing the
notification.
Type Value
-
scope primary or secondary subnet number
network scope's primary or secondary
subnet number
selectionTags selection tag list.ro DisplayString .1.3.6.1.4.1.9.9.120.1.2.11 |
cnrNotifDHCPScopeNameThe name of the DHCP scope.ro DisplayString .1.3.6.1.4.1.9.9.120.1.2.12 |
cnrNotifPrimarySubnetNumberThe primary subnet number of the network interface of which
the scope is part.ro DisplayString (SNMPv2-TC) .1.3.6.1.4.1.9.9.120.1.2.13 |
cnrNotifRelatedServerTypeThe type of related server.ro Enumeration .1.3.6.1.4.1.9.9.120.1.2.14 |
cnrNotifDnsServerIpAddressThe IP address of the DNS server.ro IpAddress .1.3.6.1.4.1.9.9.120.1.2.15 |
cnrNotifZoneNameThe name of the zone.ro DisplayString (SNMPv2-TC) .1.3.6.1.4.1.9.9.120.1.2.16 |
cnrNotifDnsRemoteServersListComma-separated list of remote server IP addresses.ro DisplayString .1.3.6.1.4.1.9.9.120.1.2.17 |
cnrNotifCfgObjects OBJECT IDENTIFIER .1.3.6.1.4.1.9.9.120.1.3 |
cnrEnableFreeAddressLowIndicates whether the ciscoNetRegFreeAddressLow
notification should be generated for this entity.rwdeprecated TruthValue (SNMPv2-TC) .1.3.6.1.4.1.9.9.120.1.3.1 |
cnrEnableFreeAddressHighIndicates whether the ciscoNetRegFreeAddressHigh
notification should be generated for this entity.rwdeprecated TruthValue (SNMPv2-TC) .1.3.6.1.4.1.9.9.120.1.3.2 |
cnrEnableServerStartIndicates whether the ciscoNetRegServerStart notification
should be generated for this entity.rw TruthValue (SNMPv2-TC) .1.3.6.1.4.1.9.9.120.1.3.3 |
cnrEnableServerStopIndicates whether the ciscoNetRegServerStop notification
should be generated for this entity.rw TruthValue (SNMPv2-TC) .1.3.6.1.4.1.9.9.120.1.3.4 |
cnrEnableDNSQueueTooBigIndicates whether the ciscoNetRegDNSQueueTooBig
notification should be generated for this entity.rw TruthValue (SNMPv2-TC) .1.3.6.1.4.1.9.9.120.1.3.5 |
cnrEnableOtherServerNotRespondingIndicates whether the ciscoNetRegOtherServerNotResponding
notification should be generated for this entity.rwdeprecated TruthValue (SNMPv2-TC) .1.3.6.1.4.1.9.9.120.1.3.6 |
cnrEnableDuplicateAddressIndicates whether the ciscoNetRegDuplicateAddress
notification should be generated for this entity.rw TruthValue (SNMPv2-TC) .1.3.6.1.4.1.9.9.120.1.3.7 |
cnrEnableAddressConflictIndicates whether the ciscoNetRegAddressConflict
notification should be generated for this entity.rw TruthValue (SNMPv2-TC) .1.3.6.1.4.1.9.9.120.1.3.8 |
cnrEnableOtherServerRespondingIndicates whether the ciscoNetRegOtherServerResponding
notification should be generated for this entity.rwdeprecated TruthValue (SNMPv2-TC) .1.3.6.1.4.1.9.9.120.1.3.9 |
cnrEnableFailoverConfigMismatchIndicates whether the ciscoNetRegFailoverConfigMismatch
notification should be generated for this entity.rw TruthValue (SNMPv2-TC) .1.3.6.1.4.1.9.9.120.1.3.10 |
cnrEnableFreeAddrLowIndicates whether the ciscoNetRegFreeAddrLowThreshold
notification should be generated for this entity.rw TruthValue (SNMPv2-TC) .1.3.6.1.4.1.9.9.120.1.3.11 |
cnrEnableFreeAddrHighIndicates whether the ciscoNetRegFreeAddrHighThreshold
notification should be generated for this entity.rw TruthValue (SNMPv2-TC) .1.3.6.1.4.1.9.9.120.1.3.12 |
cnrEnableOtherServerNotRespIndicates whether the ciscoNetRegOtherServerNotResp
notification should be generated for this entity.rw TruthValue (SNMPv2-TC) .1.3.6.1.4.1.9.9.120.1.3.13 |
cnrEnableOtherServerRespIndicates whether the ciscoNetRegOtherServerResp
notification should be generated for this entity.rw TruthValue (SNMPv2-TC) .1.3.6.1.4.1.9.9.120.1.3.14 |
cnrEnableHaDnsPartnerDownIndicates whether the ciscoNetRegHaDnsPartnerDown
notification should be generated for this entity.rw TruthValue (SNMPv2-TC) .1.3.6.1.4.1.9.9.120.1.3.15 |
cnrEnableHaDnsPartnerUpIndicates whether the ciscoNetRegHaDnsPartnerUp
notification should be generated for this entity.rw TruthValue (SNMPv2-TC) .1.3.6.1.4.1.9.9.120.1.3.16 |
cnrEnableMastersNotRespIndicates whether the ciscoNetRegMastersNotResp
notification should be generated for this entity.rw TruthValue (SNMPv2-TC) .1.3.6.1.4.1.9.9.120.1.3.17 |
cnrEnableMastersRespIndicates whether the ciscoNetRegMastersResp notification
should be generated for this entity.rw TruthValue (SNMPv2-TC) .1.3.6.1.4.1.9.9.120.1.3.18 |
cnrEnableSecondaryZoneExpiredIndicates whether the ciscoNetRegSecondaryZonesExpired
notification should be generated for this entity.rw TruthValue (SNMPv2-TC) .1.3.6.1.4.1.9.9.120.1.3.19 |
cnrEnableDnsForwardersNotRespIndicates whether the ciscoNetRegDnsForwardersNotResp
notification should be generated for this entity.rw TruthValue (SNMPv2-TC) .1.3.6.1.4.1.9.9.120.1.3.20 |
cnrEnableDnsForwardersRespIndicates whether the ciscoNetRegDnsForwardersResp
notification should be generated for this entity.rw TruthValue (SNMPv2-TC) .1.3.6.1.4.1.9.9.120.1.3.21 |
cnrEnableHaDnsConfigErrIndicates whether the ciscoNetRegHaDnsConfigErr notification
should be generated for this entity.rw TruthValue (SNMPv2-TC) .1.3.6.1.4.1.9.9.120.1.3.22 |
ciscoNetRegMIBNotificationPrefix OBJECT IDENTIFIER .1.3.6.1.4.1.9.9.120.2 |
ciscoNetRegMIBNotifications OBJECT IDENTIFIER .1.3.6.1.4.1.9.9.120.2.0 |
ciscoNetRegFreeAddressLowThis notification 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. NOTIFICATION-TYPE .1.3.6.1.4.1.9.9.120.2.0.1 |
ciscoNetRegFreeAddressHighThis notification 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. NOTIFICATION-TYPE .1.3.6.1.4.1.9.9.120.2.0.2 |
ciscoNetRegServerStartThis notification signifies that the server
of the specified type has started on the
host from which this notification has been sent. NOTIFICATION-TYPE .1.3.6.1.4.1.9.9.120.2.0.3 |
ciscoNetRegServerStopThis notification signifies that the server
of the specified type has stopped normally on the
host from which this notification has been sent. NOTIFICATION-TYPE .1.3.6.1.4.1.9.9.120.2.0.4 |
ciscoNetRegDNSQueueTooBigThis 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. NOTIFICATION-TYPE .1.3.6.1.4.1.9.9.120.2.0.5 |
ciscoNetRegOtherServerNotRespondingThis 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 server is given by the
cnrNotifServerType object.
This notification has been replaced by the
ciscoNetRegOtherServerNotResp notification. NOTIFICATION-TYPE .1.3.6.1.4.1.9.9.120.2.0.6 |
ciscoNetRegDuplicateAddressThis 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 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. NOTIFICATION-TYPE .1.3.6.1.4.1.9.9.120.2.0.7 |
ciscoNetRegAddressConflictThis 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 object indicates which address
is under contention. The cnrNotifServer object indicates
with which other server a conflict was detected. NOTIFICATION-TYPE .1.3.6.1.4.1.9.9.120.2.0.8 |
ciscoNetRegOtherServerRespondingThis 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. NOTIFICATION-TYPE .1.3.6.1.4.1.9.9.120.2.0.9 |
ciscoNetRegFailoverConfigMismatchThis 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 in the event of a server failure may not
be possible. The identity of the peer server is given
by the cnrNotifServer object. NOTIFICATION-TYPE .1.3.6.1.4.1.9.9.120.2.0.10 |
ciscoNetRegFreeAddrLowThresholdThis notification 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. NOTIFICATION-TYPE .1.3.6.1.4.1.9.9.120.2.0.11 |
ciscoNetRegFreeAddrHighThresholdThis 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 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. NOTIFICATION-TYPE .1.3.6.1.4.1.9.9.120.2.0.12 |
ciscoNetRegOtherServerNotRespThis 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 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
object. The type of the server is indicated by the
cnrNotifRelatedServerType object. NOTIFICATION-TYPE .1.3.6.1.4.1.9.9.120.2.0.13 |
ciscoNetRegOtherServerRespThis 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 generation of the
ciscoNetRegOtherServerNotResp notification.
The identity of the server is given by the cnrNotifServer
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. NOTIFICATION-TYPE .1.3.6.1.4.1.9.9.120.2.0.14 |
ciscoNetRegHaDnsPartnerDownThis 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 by the cnrNotifServer object. NOTIFICATION-TYPE .1.3.6.1.4.1.9.9.120.2.0.15 |
ciscoNetRegHaDnsPartnerUpThis 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
object. NOTIFICATION-TYPE .1.3.6.1.4.1.9.9.120.2.0.16 |
ciscoNetRegMastersNotRespThis 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 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; the identity of the master
servers is given by the cnrNotifDnsRemoteServersList; and
the zone is given by cnrNotifZoneName. NOTIFICATION-TYPE .1.3.6.1.4.1.9.9.120.2.0.17 |
ciscoNetRegMastersRespThis 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
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; the identity of the master
servers is given by the cnrNotifDnsRemoteServersList; and
the zone is given by cnrNotifZoneName object. NOTIFICATION-TYPE .1.3.6.1.4.1.9.9.120.2.0.18 |
ciscoNetRegSecondaryZonesExpiredThis 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 DNS secondary server is given by
cnrNotifDnsServerIpAddress; the identity of the master
servers is given by the cnrNotifDnsRemoteServersList; and
the zone is given by cnrNotifZoneName object. NOTIFICATION-TYPE .1.3.6.1.4.1.9.9.120.2.0.19 |
ciscoNetRegDnsForwardersNotRespThis 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 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. NOTIFICATION-TYPE .1.3.6.1.4.1.9.9.120.2.0.20 |
ciscoNetRegDnsForwardersRespThis 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 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. NOTIFICATION-TYPE .1.3.6.1.4.1.9.9.120.2.0.21 |
ciscoNetRegHaDnsConfigErrThis 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
server with the configuration error is denoted by
cnrNotifServer object. NOTIFICATION-TYPE .1.3.6.1.4.1.9.9.120.2.0.22 |
ciscoNetworkRegistrarMIBConformance OBJECT IDENTIFIER .1.3.6.1.4.1.9.9.120.3 |
ciscoNetworkRegistrarMIBCompliances OBJECT IDENTIFIER .1.3.6.1.4.1.9.9.120.3.1 |
ciscoNetworkRegistrarMIBGroups OBJECT IDENTIFIER .1.3.6.1.4.1.9.9.120.3.2 |