All MIBs › CISCO-NETWORK-REGISTRAR-MIB
Organization: Cisco Systems, Inc.
Last Updated: 2005-03-03
Category: Cisco Devices, IP and Core Protocols
Description: Manages Cisco Network Registrar DHCP and DNS services including scope, lease, and zone statistics.
Start monitoring vendor-neutral, standards-based MIB, any SNMPv3-capable network device (SNMP engine identity/boot/clock status) with a free 30-day trial of IPNetwork Monitor. Import MIBs, browse SNMP OIDs, create custom SNMP monitors, configure alerts, and monitor any SNMP-enabled network device from a single console.
What Is CISCO-NETWORK-REGISTRAR-MIB?
CISCO-NETWORK-REGISTRAR-MIB is a Cisco-specific module for Cisco Network Registrar (CNR), a DHCP and DNS server product, exposing address-scope utilization data and duplicate-IP-address detection notifications. It provides data categories covering DHCP scope configuration and free-address thresholds/levels, plus fault notifications for duplicate address conflicts. It supports monitoring the software/service status of the DNS/DHCP server application — scope free-address levels (cnrDHCPScopeFreeAddrValue against low/high thresholds) reveal address-pool exhaustion risk, while cnrNotifDupIpAddress traps flag a specific host/MAC in conflict, both of which are service-affecting conditions for network address management. As an application-layer MIB it depends on the underlying CNR DHCP/DNS engine rather than standard hardware MIBs, and is generally used alongside general host/OS monitoring of the CNR server itself. It is typically deployed on servers running Cisco Network Registrar for enterprise or service-provider DHCP/DNS management. Administrators of Cisco Network Registrar deployments search for this MIB specifically to monitor DHCP/DNS server health and duplicate-address detection through SNMP rather than the product's own web console.
IPNetwork Monitor allows you to monitor SNMP objects defined in CISCO-NETWORK-REGISTRAR-MIB. Use the built-in SNMP Monitoring Browser to explore available variables, view their current values and descriptions, and select the objects you want to monitor. You can then create SNMP monitors, configure thresholds, and receive alerts when monitored values change.
Supported Devices
- Cisco Network Registrar (CNR) DHCP/DNS servers
Monitoring Examples
An administrator would poll cnrDHCPScopeTable/cnrDHCPScopeEntry for cnrDHCPScopeName and cnrDHCPScopeFreeAddrValue, comparing it against cnrDHCPScopeFreeAddrLowThreshold and cnrDHCPScopeFreeAddrHighThreshold to detect a scope approaching address exhaustion before clients start failing to obtain leases. A cnrNotifDupIpAddress trap carrying cnrNotifMACAddress and cnrNotifDupIpAddressDetectedBy identifies which server detected a duplicate IP conflict and the offending MAC address, letting an admin quickly locate the misconfigured host. cnrNotifServer and cnrNotifServerType identify which CNR server instance and role raised the notification.
What Can Be Monitored
- DHCP scope free-address level vs thresholds
- scope name and configuration
- duplicate IP address detection events
- offending MAC address on conflict
- reporting server identity/type
This MIB depends on
Related MIBs
Imported Objects
From CISCO-SMI
| ciscoMgmt | OBJECT-IDENTITY |
From SNMPv2-CONF
| MODULE-COMPLIANCE | |
| NOTIFICATION-GROUP | |
| OBJECT-GROUP |
From SNMPv2-SMI
| Gauge32 | |
| IpAddress | |
| MODULE-IDENTITY | |
| NOTIFICATION-TYPE | |
| OBJECT-TYPE | |
| Unsigned32 |
From SNMPv2-TC
| DisplayString | |
| TEXTUAL-CONVENTION | |
| TruthValue |
OIDs
| OID symbolic | OID numeric | Type | Access | Description |
|---|---|---|---|---|
| ciscoNetworkRegistrarMIB | 1.3.6.1.4.1.9.9.120 | MIB for Cisco Network Registrar (CNR). | ||
| ciscoNetworkRegistrarMIBObjects | 1.3.6.1.4.1.9.9.120.1 | |||
| cnrDHCP | 1.3.6.1.4.1.9.9.120.1.1 | |||
| cnrDHCPScopeTable | 1.3.6.1.4.1.9.9.120.1.1.1 | not-accessible | The table listing characteristics of all scopes. Entries in this table correspond to scopes, which are added and deleted via the CNR GUI or CLI. | |
| cnrDHCPScopeEntry | 1.3.6.1.4.1.9.9.120.1.1.1.1 | not-accessible | An entry in the cnrDHCPScopeTable. | |
| STR cnrDHCPScopeName | 1.3.6.1.4.1.9.9.120.1.1.1.1.1 | DisplayString | not-accessible | The name of the scope, which uniquely identifies an entry in the cnrDHCPScopeTable. |
| U32 cnrDHCPScopeFreeAddrLowThreshold | 1.3.6.1.4.1.9.9.120.1.1.1.1.2 | Unsigned32 | accessible-for-notify | The 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. |
| U32 cnrDHCPScopeFreeAddrHighThreshold | 1.3.6.1.4.1.9.9.120.1.1.1.1.3 | Unsigned32 | accessible-for-notify | The 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. |
| U32 cnrDHCPScopeFreeAddrValue | 1.3.6.1.4.1.9.9.120.1.1.1.1.4 | Unsigned32 | accessible-for-notify | The 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. |
| INT cnrDHCPScopeFreeAddrUnits | 1.3.6.1.4.1.9.9.120.1.1.1.1.5 | INTEGER | accessible-for-notify | The units associated with the value of cnrDHCPScopeFreeAddrValue. |
| cnrNotifObjects | 1.3.6.1.4.1.9.9.120.1.2 | |||
| IP cnrNotifDupIpAddress | 1.3.6.1.4.1.9.9.120.1.2.1 | IpAddress | accessible-for-notify | The IP address which was found to be a duplicate. |
| ADR cnrNotifMACAddress | 1.3.6.1.4.1.9.9.120.1.2.2 | CnrPhysAddress | accessible-for-notify | The offending MAC address which caused a duplicate IP address to be detected. |
| IP cnrNotifServer | 1.3.6.1.4.1.9.9.120.1.2.3 | IpAddress | accessible-for-notify | The IP Address of a server with which CNR is attempting to communicate. |
| INT cnrNotifServerType | 1.3.6.1.4.1.9.9.120.1.2.4 | INTEGER | accessible-for-notify | The type of server. |
| INT cnrNotifDupIpAddressDetectedBy | 1.3.6.1.4.1.9.9.120.1.2.5 | INTEGER | accessible-for-notify | For a ciscoNetRegDuplicateAddress notification, this object indicates whether the client or server detected the condition. |
| IP cnrNotifContestedIpAddress | 1.3.6.1.4.1.9.9.120.1.2.6 | IpAddress | accessible-for-notify | The IP address for which ownership is claimed by two or more DHCP servers. |
| U32 cnrNotifDHCPScopeFreeAddrLow | 1.3.6.1.4.1.9.9.120.1.2.7 | Unsigned32 | accessible-for-notify | This 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. |
| U32 cnrNotifDHCPScopeFreeAddrHigh | 1.3.6.1.4.1.9.9.120.1.2.8 | Unsigned32 | accessible-for-notify | This 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. |
| G32 cnrNotifDHCPScopeFreeAddrValue | 1.3.6.1.4.1.9.9.120.1.2.9 | Gauge32 | accessible-for-notify | The number of IP addresses which are available within the scope specified by the cnrDHCPScope object. |
| INT cnrNotifDHCPThresholdType | 1.3.6.1.4.1.9.9.120.1.2.10 | INTEGER | accessible-for-notify | The 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. |
| STR cnrNotifDHCPThresholdValue | 1.3.6.1.4.1.9.9.120.1.2.11 | DisplayString | accessible-for-notify | The 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. |
| STR cnrNotifDHCPScopeName | 1.3.6.1.4.1.9.9.120.1.2.12 | DisplayString | accessible-for-notify | The name of the DHCP scope. |
| STR cnrNotifPrimarySubnetNumber | 1.3.6.1.4.1.9.9.120.1.2.13 | DisplayString | accessible-for-notify | The primary subnet number of the network interface of which the scope is part. |
| INT cnrNotifRelatedServerType | 1.3.6.1.4.1.9.9.120.1.2.14 | INTEGER | accessible-for-notify | The type of related server. |
| IP cnrNotifDnsServerIpAddress | 1.3.6.1.4.1.9.9.120.1.2.15 | IpAddress | accessible-for-notify | The IP address of the DNS server. |
| STR cnrNotifZoneName | 1.3.6.1.4.1.9.9.120.1.2.16 | DisplayString | accessible-for-notify | The name of the zone. |
| STR cnrNotifDnsRemoteServersList | 1.3.6.1.4.1.9.9.120.1.2.17 | DisplayString | accessible-for-notify | Comma-separated list of remote server IP addresses. |
| cnrNotifCfgObjects | 1.3.6.1.4.1.9.9.120.1.3 | |||
| T/F cnrEnableFreeAddressLow | 1.3.6.1.4.1.9.9.120.1.3.1 | TruthValue | read-write | Indicates whether the ciscoNetRegFreeAddressLow notification should be generated for this entity. |
| T/F cnrEnableFreeAddressHigh | 1.3.6.1.4.1.9.9.120.1.3.2 | TruthValue | read-write | Indicates whether the ciscoNetRegFreeAddressHigh notification should be generated for this entity. |
| T/F cnrEnableServerStart | 1.3.6.1.4.1.9.9.120.1.3.3 | TruthValue | read-write | Indicates whether the ciscoNetRegServerStart notification should be generated for this entity. |
| T/F cnrEnableServerStop | 1.3.6.1.4.1.9.9.120.1.3.4 | TruthValue | read-write | Indicates whether the ciscoNetRegServerStop notification should be generated for this entity. |
| T/F cnrEnableDNSQueueTooBig | 1.3.6.1.4.1.9.9.120.1.3.5 | TruthValue | read-write | Indicates whether the ciscoNetRegDNSQueueTooBig notification should be generated for this entity. |
| T/F cnrEnableOtherServerNotResponding | 1.3.6.1.4.1.9.9.120.1.3.6 | TruthValue | read-write | Indicates whether the ciscoNetRegOtherServerNotResponding notification should be generated for this entity. |
| T/F cnrEnableDuplicateAddress | 1.3.6.1.4.1.9.9.120.1.3.7 | TruthValue | read-write | Indicates whether the ciscoNetRegDuplicateAddress notification should be generated for this entity. |
| T/F cnrEnableAddressConflict | 1.3.6.1.4.1.9.9.120.1.3.8 | TruthValue | read-write | Indicates whether the ciscoNetRegAddressConflict notification should be generated for this entity. |
| T/F cnrEnableOtherServerResponding | 1.3.6.1.4.1.9.9.120.1.3.9 | TruthValue | read-write | Indicates whether the ciscoNetRegOtherServerResponding notification should be generated for this entity. |
| T/F cnrEnableFailoverConfigMismatch | 1.3.6.1.4.1.9.9.120.1.3.10 | TruthValue | read-write | Indicates whether the ciscoNetRegFailoverConfigMismatch notification should be generated for this entity. |
| T/F cnrEnableFreeAddrLow | 1.3.6.1.4.1.9.9.120.1.3.11 | TruthValue | read-write | Indicates whether the ciscoNetRegFreeAddrLowThreshold notification should be generated for this entity. |
| T/F cnrEnableFreeAddrHigh | 1.3.6.1.4.1.9.9.120.1.3.12 | TruthValue | read-write | Indicates whether the ciscoNetRegFreeAddrHighThreshold notification should be generated for this entity. |
| T/F cnrEnableOtherServerNotResp | 1.3.6.1.4.1.9.9.120.1.3.13 | TruthValue | read-write | Indicates whether the ciscoNetRegOtherServerNotResp notification should be generated for this entity. |
| T/F cnrEnableOtherServerResp | 1.3.6.1.4.1.9.9.120.1.3.14 | TruthValue | read-write | Indicates whether the ciscoNetRegOtherServerResp notification should be generated for this entity. |
| T/F cnrEnableHaDnsPartnerDown | 1.3.6.1.4.1.9.9.120.1.3.15 | TruthValue | read-write | Indicates whether the ciscoNetRegHaDnsPartnerDown notification should be generated for this entity. |
| T/F cnrEnableHaDnsPartnerUp | 1.3.6.1.4.1.9.9.120.1.3.16 | TruthValue | read-write | Indicates whether the ciscoNetRegHaDnsPartnerUp notification should be generated for this entity. |
| T/F cnrEnableMastersNotResp | 1.3.6.1.4.1.9.9.120.1.3.17 | TruthValue | read-write | Indicates whether the ciscoNetRegMastersNotResp notification should be generated for this entity. |
| T/F cnrEnableMastersResp | 1.3.6.1.4.1.9.9.120.1.3.18 | TruthValue | read-write | Indicates whether the ciscoNetRegMastersResp notification should be generated for this entity. |
| T/F cnrEnableSecondaryZoneExpired | 1.3.6.1.4.1.9.9.120.1.3.19 | TruthValue | read-write | Indicates whether the ciscoNetRegSecondaryZonesExpired notification should be generated for this entity. |
| T/F cnrEnableDnsForwardersNotResp | 1.3.6.1.4.1.9.9.120.1.3.20 | TruthValue | read-write | Indicates whether the ciscoNetRegDnsForwardersNotResp notification should be generated for this entity. |
| T/F cnrEnableDnsForwardersResp | 1.3.6.1.4.1.9.9.120.1.3.21 | TruthValue | read-write | Indicates whether the ciscoNetRegDnsForwardersResp notification should be generated for this entity. |
| T/F cnrEnableHaDnsConfigErr | 1.3.6.1.4.1.9.9.120.1.3.22 | TruthValue | read-write | Indicates whether the ciscoNetRegHaDnsConfigErr notification should be generated for this entity. |
| ciscoNetRegMIBNotificationPrefix | 1.3.6.1.4.1.9.9.120.2 | |||
| ciscoNetRegMIBNotifications | 1.3.6.1.4.1.9.9.120.2.0 | |||
| NTF ciscoNetRegFreeAddressLow | 1.3.6.1.4.1.9.9.120.2.0.1 | This 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. | ||
| NTF ciscoNetRegFreeAddressHigh | 1.3.6.1.4.1.9.9.120.2.0.2 | This 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. | ||
| NTF ciscoNetRegServerStart | 1.3.6.1.4.1.9.9.120.2.0.3 | This notification signifies that the server of the specified type has started on the host from which this notification has been sent. | ||
| NTF ciscoNetRegServerStop | 1.3.6.1.4.1.9.9.120.2.0.4 | This notification signifies that the server of the specified type has stopped normally on the host from which this notification has been sent. | ||
| NTF ciscoNetRegDNSQueueTooBig | 1.3.6.1.4.1.9.9.120.2.0.5 | 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. | ||
| NTF ciscoNetRegOtherServerNotResponding | 1.3.6.1.4.1.9.9.120.2.0.6 | 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 server is given by the cnrNotifServerType object. This notification has been replaced by the ciscoNetRegOtherServerNotResp notification. | ||
| NTF ciscoNetRegDuplicateAddress | 1.3.6.1.4.1.9.9.120.2.0.7 | 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 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. | ||
| NTF ciscoNetRegAddressConflict | 1.3.6.1.4.1.9.9.120.2.0.8 | 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 object indicates which address is under contention. The cnrNotifServer object indicates with which other server a conflict was detected. | ||
| NTF ciscoNetRegOtherServerResponding | 1.3.6.1.4.1.9.9.120.2.0.9 | 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. | ||
| NTF ciscoNetRegFailoverConfigMismatch | 1.3.6.1.4.1.9.9.120.2.0.10 | 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 in the event of a server failure may not be possible. The identity of the peer server is given by the cnrNotifServer object. | ||
| NTF ciscoNetRegFreeAddrLowThreshold | 1.3.6.1.4.1.9.9.120.2.0.11 | This 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. | ||
| NTF ciscoNetRegFreeAddrHighThreshold | 1.3.6.1.4.1.9.9.120.2.0.12 | 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 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. | ||
| NTF ciscoNetRegOtherServerNotResp | 1.3.6.1.4.1.9.9.120.2.0.13 | 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 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. | ||
| NTF ciscoNetRegOtherServerResp | 1.3.6.1.4.1.9.9.120.2.0.14 | 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 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. | ||
| NTF ciscoNetRegHaDnsPartnerDown | 1.3.6.1.4.1.9.9.120.2.0.15 | 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 by the cnrNotifServer object. | ||
| NTF ciscoNetRegHaDnsPartnerUp | 1.3.6.1.4.1.9.9.120.2.0.16 | 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 object. | ||
| NTF ciscoNetRegMastersNotResp | 1.3.6.1.4.1.9.9.120.2.0.17 | 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 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. | ||
| NTF ciscoNetRegMastersResp | 1.3.6.1.4.1.9.9.120.2.0.18 | 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 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. | ||
| NTF ciscoNetRegSecondaryZonesExpired | 1.3.6.1.4.1.9.9.120.2.0.19 | 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 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. | ||
| NTF ciscoNetRegDnsForwardersNotResp | 1.3.6.1.4.1.9.9.120.2.0.20 | 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 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. | ||
| NTF ciscoNetRegDnsForwardersResp | 1.3.6.1.4.1.9.9.120.2.0.21 | 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 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. | ||
| NTF ciscoNetRegHaDnsConfigErr | 1.3.6.1.4.1.9.9.120.2.0.22 | 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 server with the configuration error is denoted by cnrNotifServer object. | ||
| ciscoNetworkRegistrarMIBConformance | 1.3.6.1.4.1.9.9.120.3 | |||
| ciscoNetworkRegistrarMIBCompliances | 1.3.6.1.4.1.9.9.120.3.1 | |||
| ciscoNetworkRegistrarMIBCompliance | 1.3.6.1.4.1.9.9.120.3.1.1 | The compliance statement for entities which implement the Cisco Network Registrar MIB | ||
| ciscoNetworkRegistrarMIBCompRev1 | 1.3.6.1.4.1.9.9.120.3.1.2 | The compliance statement for entities which implement the Cisco Network Registrar MIB | ||
| ciscoNetworkRegistrarMIBGroups | 1.3.6.1.4.1.9.9.120.3.2 | |||
| ciscoNetworkRegistrarDHCPScopeObjectsGroup | 1.3.6.1.4.1.9.9.120.3.2.1 | Network Registrar MIB objects used in DHCP scopes. | ||
| ciscoNetworkRegistrarNotifObjectsGroup | 1.3.6.1.4.1.9.9.120.3.2.2 | Network Registrar MIB objects used in notifications. | ||
| ciscoNetworkRegistrarNotifCfgObjectsGroup | 1.3.6.1.4.1.9.9.120.3.2.3 | Network Registrar MIB objects used to enable/disable notifications. | ||
| ciscoNetworkRegistrarNotificationsGroup | 1.3.6.1.4.1.9.9.120.3.2.4 | Notifications which are implemented by the Cisco Network Registrar agent. | ||
| ciscoNetRegistrarNotifInfoGroup | 1.3.6.1.4.1.9.9.120.3.2.5 | The objects in this group are used provide information to be included in notifications. | ||
| ciscoNetRegistrarNotEnableGroup | 1.3.6.1.4.1.9.9.120.3.2.6 | The objects in this group are used to control the generations of notifications. | ||
| ciscoNetRegistrarNotificatGroup | 1.3.6.1.4.1.9.9.120.3.2.7 | Notifications which are implemented by the Cisco Network Registrar. |
RFC description
Monitors Cisco Network Registrar (CNR) DNS/DHCP server status and generates notifications for critical events.
Start monitoring Cisco Network Registrar (CNR) DHCP/DNS servers with a free 30-day trial of IPNetwork Monitor. Import MIBs, browse SNMP OIDs, create custom SNMP monitors, configure alerts, and monitor any SNMP-enabled network device from a single console.