Standard view Table view

CISCO-NETWORK-REGISTRAR-MIB

        MIB for Cisco Network Registrar (CNR).
Source file
CISCO-NETWORK-REGISTRAR-MIB
Last revised
Identity
ciscoNetworkRegistrarMIB
Base OID
1.3.6.1.4.1.9.9.120
Imported Objects
CISCO-SMI ciscoMgmt
INET-ADDRESS-MIB InetAddressIPv6
SNMP-FRAMEWORK-MIB SnmpAdminString
SNMPv2-CONF MODULE-COMPLIANCE NOTIFICATION-GROUP OBJECT-GROUP
SNMPv2-SMI Gauge32 IpAddress MODULE-IDENTITY NOTIFICATION-TYPE OBJECT-TYPE Unsigned32
SNMPv2-TC DisplayString TEXTUAL-CONVENTION TruthValue
Net-SNMP examples using the cisco MIB directory Show commands

These commands use the standard Observium installation path and load the selected MIB variant before the RFC and Net-SNMP directories.

Translate the module identity
/usr/bin/snmptranslate -Pud -Ir -On -m 'CISCO-NETWORK-REGISTRAR-MIB' -M '/opt/observium/mibs/cisco:/opt/observium/mibs/rfc:/opt/observium/mibs/net-snmp' 'CISCO-NETWORK-REGISTRAR-MIB::ciscoNetworkRegistrarMIB'
Walk the MIB subtree
/usr/bin/snmpbulkwalk -v2c -c '<community>' -Pud -Ir -OQUs -m 'CISCO-NETWORK-REGISTRAR-MIB' -M '/opt/observium/mibs/cisco:/opt/observium/mibs/rfc:/opt/observium/mibs/net-snmp' 'udp:<hostname>:161' 'CISCO-NETWORK-REGISTRAR-MIB::ciscoNetworkRegistrarMIB'
How SNMP, Net-SNMP, MIB paths, and variants work
Objects (67)
ciscoNetworkRegistrarMIB
.1.3.6.1.4.1.9.9.120
ciscoNetworkRegistrarMIBObjects
.1.3.6.1.4.1.9.9.120.1
cnrDHCP
.1.3.6.1.4.1.9.9.120.1.1
cnrDHCPScopeTable deprecated
.1.3.6.1.4.1.9.9.120.1.1.1
cnrDHCPScopeEntry deprecated
cnrDHCPScopeName
 .1.3.6.1.4.1.9.9.120.1.1.1.1
cnrDHCPScopeName deprecated
OctetString
 .1.3.6.1.4.1.9.9.120.1.1.1.1.1
cnrDHCPScopeFreeAddrLowThreshold deprecated
SNMPv2-SMIUnsigned32
 .1.3.6.1.4.1.9.9.120.1.1.1.1.2
cnrDHCPScopeFreeAddrHighThreshold deprecated
SNMPv2-SMIUnsigned32
 .1.3.6.1.4.1.9.9.120.1.1.1.1.3
cnrDHCPScopeFreeAddrValue deprecated
SNMPv2-SMIUnsigned32
 .1.3.6.1.4.1.9.9.120.1.1.1.1.4
cnrDHCPScopeFreeAddrUnits deprecated
Enumeration
 .1.3.6.1.4.1.9.9.120.1.1.1.1.5
cnrNotifObjects
.1.3.6.1.4.1.9.9.120.1.2
cnrNotifDupIpAddress
SNMPv2-SMIIpAddress
 .1.3.6.1.4.1.9.9.120.1.2.1
cnrNotifDHCPThresholdType
Enumeration
 .1.3.6.1.4.1.9.9.120.1.2.10
cnrNotifDHCPThresholdValue
OctetString
 .1.3.6.1.4.1.9.9.120.1.2.11
cnrNotifDHCPScopeName
OctetString
 .1.3.6.1.4.1.9.9.120.1.2.12
cnrNotifPrimarySubnetNumber
SNMPv2-TCDisplayString
 .1.3.6.1.4.1.9.9.120.1.2.13
cnrNotifRelatedServerType
Enumeration
 .1.3.6.1.4.1.9.9.120.1.2.14
cnrNotifDnsServerIpAddress
SNMPv2-SMIIpAddress
 .1.3.6.1.4.1.9.9.120.1.2.15
cnrNotifZoneName
SNMPv2-TCDisplayString
 .1.3.6.1.4.1.9.9.120.1.2.16
cnrNotifDnsRemoteServersList
OctetString
 .1.3.6.1.4.1.9.9.120.1.2.17
cnrNotifIPv6Server
INET-ADDRESS-MIBInetAddressIPv6
 .1.3.6.1.4.1.9.9.120.1.2.18
cnrNotifFailoverPairName
OctetString
 .1.3.6.1.4.1.9.9.120.1.2.19
cnrNotifMACAddress
CnrPhysAddress
 .1.3.6.1.4.1.9.9.120.1.2.2
cnrNotifFailoverCfgErrType
Enumeration
 .1.3.6.1.4.1.9.9.120.1.2.20
cnrNotifDnsServerIp6Address
INET-ADDRESS-MIBInetAddressIPv6
 .1.3.6.1.4.1.9.9.120.1.2.21
cnrNotifMainIPAddress
SNMPv2-SMIIpAddress
 .1.3.6.1.4.1.9.9.120.1.2.22
cnrNotifMainIPv6Address
INET-ADDRESS-MIBInetAddressIPv6
 .1.3.6.1.4.1.9.9.120.1.2.23
cnrNotifBackupIPAddress
SNMPv2-SMIIpAddress
 .1.3.6.1.4.1.9.9.120.1.2.24
cnrNotifBackupIPv6Address
INET-ADDRESS-MIBInetAddressIPv6
 .1.3.6.1.4.1.9.9.120.1.2.25
cnrNotifSyncDirection
Enumeration
 .1.3.6.1.4.1.9.9.120.1.2.26
cnrNotifSyncError
OctetString
 .1.3.6.1.4.1.9.9.120.1.2.27
cnrNotifServer
SNMPv2-SMIIpAddress
 .1.3.6.1.4.1.9.9.120.1.2.3
cnrNotifServerType
Enumeration
 .1.3.6.1.4.1.9.9.120.1.2.4
cnrNotifDupIpAddressDetectedBy
Enumeration
 .1.3.6.1.4.1.9.9.120.1.2.5
cnrNotifContestedIpAddress
SNMPv2-SMIIpAddress
 .1.3.6.1.4.1.9.9.120.1.2.6
cnrNotifDHCPScopeFreeAddrLow
percentageSNMPv2-SMIUnsigned32
 .1.3.6.1.4.1.9.9.120.1.2.7
cnrNotifDHCPScopeFreeAddrHigh
percentageSNMPv2-SMIUnsigned32
 .1.3.6.1.4.1.9.9.120.1.2.8
cnrNotifDHCPScopeFreeAddrValue
IP addressesSNMPv2-SMIGauge32
 .1.3.6.1.4.1.9.9.120.1.2.9
cnrNotifCfgObjects
.1.3.6.1.4.1.9.9.120.1.3
cnrEnableFreeAddressLow deprecated r/w
SNMPv2-TCTruthValue
 .1.3.6.1.4.1.9.9.120.1.3.1
cnrEnableFailoverConfigMismatch r/w
SNMPv2-TCTruthValue
 .1.3.6.1.4.1.9.9.120.1.3.10
cnrEnableFreeAddrLow r/w
SNMPv2-TCTruthValue
 .1.3.6.1.4.1.9.9.120.1.3.11
cnrEnableFreeAddrHigh r/w
SNMPv2-TCTruthValue
 .1.3.6.1.4.1.9.9.120.1.3.12
cnrEnableOtherServerNotResp r/w
SNMPv2-TCTruthValue
 .1.3.6.1.4.1.9.9.120.1.3.13
cnrEnableOtherServerResp r/w
SNMPv2-TCTruthValue
 .1.3.6.1.4.1.9.9.120.1.3.14
cnrEnableHaDnsPartnerDown r/w
SNMPv2-TCTruthValue
 .1.3.6.1.4.1.9.9.120.1.3.15
cnrEnableHaDnsPartnerUp r/w
SNMPv2-TCTruthValue
 .1.3.6.1.4.1.9.9.120.1.3.16
cnrEnableMastersNotResp r/w
SNMPv2-TCTruthValue
 .1.3.6.1.4.1.9.9.120.1.3.17
cnrEnableMastersResp r/w
SNMPv2-TCTruthValue
 .1.3.6.1.4.1.9.9.120.1.3.18
cnrEnableSecondaryZoneExpired r/w
SNMPv2-TCTruthValue
 .1.3.6.1.4.1.9.9.120.1.3.19
cnrEnableFreeAddressHigh deprecated r/w
SNMPv2-TCTruthValue
 .1.3.6.1.4.1.9.9.120.1.3.2
cnrEnableDnsForwardersNotResp r/w
SNMPv2-TCTruthValue
 .1.3.6.1.4.1.9.9.120.1.3.20
cnrEnableDnsForwardersResp r/w
SNMPv2-TCTruthValue
 .1.3.6.1.4.1.9.9.120.1.3.21
cnrEnableHaDnsConfigErr r/w
SNMPv2-TCTruthValue
 .1.3.6.1.4.1.9.9.120.1.3.22
cnrEnableFailoverSyncFailure r/w
SNMPv2-TCTruthValue
 .1.3.6.1.4.1.9.9.120.1.3.23
cnrEnableServerStart r/w
SNMPv2-TCTruthValue
 .1.3.6.1.4.1.9.9.120.1.3.3
cnrEnableServerStop r/w
SNMPv2-TCTruthValue
 .1.3.6.1.4.1.9.9.120.1.3.4
cnrEnableDNSQueueTooBig r/w
SNMPv2-TCTruthValue
 .1.3.6.1.4.1.9.9.120.1.3.5
cnrEnableOtherServerNotResponding deprecated r/w
SNMPv2-TCTruthValue
 .1.3.6.1.4.1.9.9.120.1.3.6
cnrEnableDuplicateAddress r/w
SNMPv2-TCTruthValue
 .1.3.6.1.4.1.9.9.120.1.3.7
cnrEnableAddressConflict r/w
SNMPv2-TCTruthValue
 .1.3.6.1.4.1.9.9.120.1.3.8
cnrEnableOtherServerResponding deprecated r/w
SNMPv2-TCTruthValue
 .1.3.6.1.4.1.9.9.120.1.3.9
ciscoNetRegMIBNotificationPrefix
.1.3.6.1.4.1.9.9.120.2
ciscoNetRegMIBNotifications
.1.3.6.1.4.1.9.9.120.2.0
ciscoNetworkRegistrarMIBConformance
.1.3.6.1.4.1.9.9.120.3
ciscoNetworkRegistrarMIBCompliances
.1.3.6.1.4.1.9.9.120.3.1
ciscoNetworkRegistrarMIBGroups
.1.3.6.1.4.1.9.9.120.3.2
Dependencies (6) 6 direct Show tree and compile order Hide dependency details

Each imported module is resolved in the importing module's source directory first, then through the normal default-variant rules.

Dependency tree
Dependency-first compile order
  1. SNMPv2-SMIrfc
  2. CISCO-SMIcisco
  3. SNMPv2-TCrfc
  4. INET-ADDRESS-MIBrfc
  5. SNMPv2-CONFrfc
  6. SNMP-FRAMEWORK-MIBrfc
  7. CISCO-NETWORK-REGISTRAR-MIBciscoselected
Type Definitions (1)
CnrPhysAddress
OctetString range: 2..18
Conformance Groups (7)
ciscoNetworkRegistrarDHCPScopeObjectsGroup deprecated
cnrDHCPScopeFreeAddrLowThreshold cnrDHCPScopeFreeAddrHighThreshold cnrDHCPScopeFreeAddrValue cnrDHCPScopeFreeAddrUnits
Network Registrar MIB objects used in DHCP scopes.
 .1.3.6.1.4.1.9.9.120.3.2.1
ciscoNetworkRegistrarNotifObjectsGroup deprecated
cnrNotifDupIpAddress cnrNotifMACAddress cnrNotifDupIpAddressDetectedBy cnrNotifServer cnrNotifServerType cnrNotifContestedIpAddress
Network Registrar MIB objects used in notifications.
 .1.3.6.1.4.1.9.9.120.3.2.2
ciscoNetworkRegistrarNotifCfgObjectsGroup deprecated
cnrEnableFreeAddressLow cnrEnableFreeAddressHigh cnrEnableServerStart cnrEnableServerStop cnrEnableDNSQueueTooBig cnrEnableOtherServerNotResponding cnrEnableDuplicateAddress cnrEnableAddressConflict cnrEnableOtherServerResponding cnrEnableFailoverConfigMismatch
Network Registrar MIB objects used to enable/disable
notifications.
 .1.3.6.1.4.1.9.9.120.3.2.3
ciscoNetworkRegistrarNotificationsGroup deprecated
ciscoNetRegFreeAddressLow ciscoNetRegFreeAddressHigh ciscoNetRegServerStart ciscoNetRegServerStop ciscoNetRegDNSQueueTooBig ciscoNetRegOtherServerNotResponding ciscoNetRegDuplicateAddress ciscoNetRegAddressConflict ciscoNetRegOtherServerResponding ciscoNetRegFailoverConfigMismatch
Notifications which are implemented by the
Cisco Network Registrar agent.
 .1.3.6.1.4.1.9.9.120.3.2.4
ciscoNetRegistrarNotifInfoGroup
cnrNotifDupIpAddress cnrNotifMACAddress cnrNotifServer cnrNotifServerType cnrNotifDupIpAddressDetectedBy cnrNotifContestedIpAddress cnrNotifDHCPScopeFreeAddrLow cnrNotifDHCPScopeFreeAddrHigh cnrNotifDHCPScopeFreeAddrValue cnrNotifDHCPThresholdType cnrNotifDHCPThresholdValue cnrNotifDHCPScopeName cnrNotifPrimarySubnetNumber cnrNotifRelatedServerType cnrNotifDnsServerIpAddress cnrNotifZoneName cnrNotifDnsRemoteServersList cnrNotifIPv6Server cnrNotifFailoverPairName cnrNotifFailoverCfgErrType cnrNotifDnsServerIp6Address cnrNotifMainIPAddress cnrNotifMainIPv6Address cnrNotifBackupIPAddress cnrNotifBackupIPv6Address cnrNotifSyncDirection cnrNotifSyncError
The objects in this group are used provide information
to be included in notifications.
 .1.3.6.1.4.1.9.9.120.3.2.5
ciscoNetRegistrarNotEnableGroup
cnrEnableServerStart cnrEnableServerStop cnrEnableDNSQueueTooBig cnrEnableDuplicateAddress cnrEnableAddressConflict cnrEnableFailoverConfigMismatch cnrEnableFreeAddrLow cnrEnableFreeAddrHigh cnrEnableOtherServerNotResp cnrEnableOtherServerResp cnrEnableHaDnsPartnerDown cnrEnableHaDnsPartnerUp cnrEnableMastersNotResp cnrEnableMastersResp cnrEnableSecondaryZoneExpired cnrEnableDnsForwardersNotResp cnrEnableDnsForwardersResp cnrEnableHaDnsConfigErr cnrEnableFailoverSyncFailure
The objects in this group are used to control the generations
of notifications.
 .1.3.6.1.4.1.9.9.120.3.2.6
ciscoNetRegistrarNotificatGroup
ciscoNetRegServerStart ciscoNetRegServerStop ciscoNetRegDNSQueueTooBig ciscoNetRegFreeAddrLowThreshold ciscoNetRegFreeAddrHighThreshold ciscoNetRegAddressConflict ciscoNetRegDuplicateAddress ciscoNetRegOtherServerNotResp ciscoNetRegOtherServerResp ciscoNetRegFailoverConfigMismatch ciscoNetRegHaDnsPartnerDown ciscoNetRegHaDnsPartnerUp ciscoNetRegMastersNotResp ciscoNetRegMastersResp ciscoNetRegSecondaryZonesExpired ciscoNetRegDnsForwardersNotResp ciscoNetRegDnsForwardersResp ciscoNetRegHaDnsConfigErr ciscoNetRegFailoverSyncFailure
Notifications which are implemented by the
Cisco Network Registrar.
 .1.3.6.1.4.1.9.9.120.3.2.7
Compliance Statements (2)

OID .1.3.6.1.4.1.9.9.120.3.1.1
The compliance statement for entities which implement
the Cisco Network Registrar MIB
Required groups
mandatory ciscoNetworkRegistrarDHCPScopeObjectsGroup
mandatory ciscoNetworkRegistrarNotifObjectsGroup
optional ciscoNetworkRegistrarNotifCfgObjectsGroup Optional configuration objects for notifications.
Object refinements
ObjectAccessSyntaxDescription
cnrEnableFreeAddressLow readonly
Write access is not required.
cnrEnableFreeAddressHigh readonly
Write access is not required.
cnrEnableServerStart readonly
Write access is not required.
cnrEnableServerStop readonly
Write access is not required.
cnrEnableDNSQueueTooBig readonly
Write access is not required.
cnrEnableOtherServerNotResponding readonly
Write access is not required.
cnrEnableDuplicateAddress readonly
Write access is not required.
cnrEnableAddressConflict readonly
Write access is not required.
cnrEnableOtherServerResponding readonly
Write access is not required.
cnrEnableFailoverConfigMismatch readonly
Write access is not required.

OID .1.3.6.1.4.1.9.9.120.3.1.2
The compliance statement for entities which implement
the Cisco Network Registrar MIB
Required groups
mandatory ciscoNetRegistrarNotifInfoGroup
mandatory ciscoNetRegistrarNotEnableGroup
mandatory ciscoNetRegistrarNotificatGroup
Object refinements
ObjectAccessSyntaxDescription
cnrEnableServerStart readonly
Write access is not required.
cnrEnableServerStop readonly
Write access is not required.
cnrEnableDNSQueueTooBig readonly
Write access is not required.
cnrEnableDuplicateAddress readonly
Write access is not required.
cnrEnableAddressConflict readonly
Write access is not required.
cnrEnableFailoverConfigMismatch readonly
Write access is not required.
cnrEnableFreeAddrLow readonly
Write access is not required.
cnrEnableFreeAddrHigh readonly
Write access is not required.
cnrEnableOtherServerNotResp readonly
Write access is not required.
cnrEnableOtherServerResp readonly
Write access is not required.
cnrEnableHaDnsPartnerDown readonly
Write access is not required.
cnrEnableHaDnsPartnerUp readonly
Write access is not required.
cnrEnableMastersNotResp readonly
Write access is not required.
cnrEnableMastersResp readonly
Write access is not required.
cnrEnableSecondaryZoneExpired readonly
Write access is not required.
cnrEnableDnsForwardersNotResp readonly
Write access is not required.
cnrEnableDnsForwardersResp readonly
Write access is not required.
cnrEnableHaDnsConfigErr readonly
Write access is not required.
cnrEnableFailoverSyncFailure readonly
Write access is not required.
Notifications / Traps (23)
NameOIDDescription
ciscoNetRegFreeAddressLow deprecated
cnrDHCPScopeFreeAddrLowThreshold cnrDHCPScopeFreeAddrValue cnrDHCPScopeFreeAddrUnits
.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.
ciscoNetRegFailoverConfigMismatch
cnrNotifServer cnrNotifIPv6Server cnrNotifFailoverPairName cnrNotifFailoverCfgErrType
.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 or cnrNotifIPv6Server object. The
cnrNotifFailoverPairName object indicates failover
pair name. The cnrNotifFailoverCfgErrType object
indicates failover configuration error type.
ciscoNetRegFreeAddrLowThreshold
cnrNotifDHCPScopeFreeAddrLow cnrNotifDHCPScopeFreeAddrValue cnrNotifDHCPScopeName cnrNotifPrimarySubnetNumber cnrNotifDHCPThresholdType cnrNotifDHCPThresholdValue
.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.
ciscoNetRegFreeAddrHighThreshold
cnrNotifDHCPScopeFreeAddrHigh cnrNotifDHCPScopeFreeAddrValue cnrNotifDHCPScopeName cnrNotifPrimarySubnetNumber cnrNotifDHCPThresholdType cnrNotifDHCPThresholdValue
.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.
ciscoNetRegOtherServerNotResp
cnrNotifServer cnrNotifRelatedServerType cnrNotifIPv6Server
.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
or cnrNotifIPv6Server object. The type of the server is
indicated by the cnrNotifRelatedServerType object.
ciscoNetRegOtherServerResp
cnrNotifServer cnrNotifRelatedServerType cnrNotifIPv6Server
.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
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.
ciscoNetRegHaDnsPartnerDown
cnrNotifServer cnrNotifIPv6Server
.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 or cnrNotifIPv6Server object.
ciscoNetRegHaDnsPartnerUp
cnrNotifServer cnrNotifIPv6Server
.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
or cnrNotifIPv6Server object.
ciscoNetRegMastersNotResp
cnrNotifDnsServerIpAddress cnrNotifDnsServerIp6Address cnrNotifZoneName cnrNotifDnsRemoteServersList
.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 or cnrNotifDnsServerIp6Address;
the identity of the master servers is given by the
cnrNotifDnsRemoteServersList; and
the zone is given by cnrNotifZoneName.
ciscoNetRegMastersResp
cnrNotifDnsServerIpAddress cnrNotifDnsServerIp6Address cnrNotifZoneName cnrNotifDnsRemoteServersList
.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 or cnrNotifDnsServerIp6Address;
the identity of the master servers is given by the
cnrNotifDnsRemoteServersList; and
the zone is given by cnrNotifZoneName object.
ciscoNetRegSecondaryZonesExpired
cnrNotifDnsServerIpAddress cnrNotifDnsServerIp6Address cnrNotifZoneName cnrNotifDnsRemoteServersList
.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 or cnrNotifDnsServerIp6Address;
the identity of the master servers is given by the
cnrNotifDnsRemoteServersList; and
the zone is given by cnrNotifZoneName object.
ciscoNetRegFreeAddressHigh deprecated
cnrDHCPScopeFreeAddrHighThreshold cnrDHCPScopeFreeAddrValue cnrDHCPScopeFreeAddrUnits
.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.
ciscoNetRegDnsForwardersNotResp deprecated
cnrNotifDnsServerIpAddress cnrNotifDnsRemoteServersList
.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.
ciscoNetRegDnsForwardersResp deprecated
cnrNotifDnsServerIpAddress cnrNotifDnsRemoteServersList
.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.
ciscoNetRegHaDnsConfigErr
cnrNotifServer cnrNotifZoneName cnrNotifIPv6Server
.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 or cnrNotifIPv6Server object.
ciscoNetRegFailoverSyncFailure
cnrNotifFailoverPairName cnrNotifMainIPAddress cnrNotifMainIPv6Address cnrNotifBackupIPAddress cnrNotifBackupIPv6Address cnrNotifSyncDirection cnrNotifSyncError
.1.3.6.1.4.1.9.9.120.2.0.23
This notification 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.
ciscoNetRegServerStart
cnrNotifServerType
.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.
ciscoNetRegServerStop
cnrNotifServerType
.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.
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.
ciscoNetRegOtherServerNotResponding deprecated
cnrNotifServer cnrNotifServerType
.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.
ciscoNetRegDuplicateAddress
cnrNotifDupIpAddress cnrNotifMACAddress cnrNotifDupIpAddressDetectedBy
.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.
ciscoNetRegAddressConflict
cnrNotifContestedIpAddress cnrNotifServer cnrNotifIPv6Server cnrNotifFailoverPairName
.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 or
cnrNotifIPv6Server object indicates with which other
server a conflict was detected. The
cnrNotifFailoverPairName object indicates failover
pair name.
ciscoNetRegOtherServerResponding deprecated
cnrNotifServer cnrNotifServerType
.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.