CISCO-NETWORK-REGISTRAR-MIB

File: CISCO-NETWORK-REGISTRAR-MIB.mib (49658 bytes)

Imported modules

SNMPv2-SMI SNMPv2-CONF SNMPv2-TC
CISCO-SMI

Imported symbols

MODULE-IDENTITY OBJECT-TYPE NOTIFICATION-TYPE
IpAddress Unsigned32 Gauge32
MODULE-COMPLIANCE OBJECT-GROUP NOTIFICATION-GROUP
TEXTUAL-CONVENTION DisplayString TruthValue
ciscoMgmt

Defined Types

CnrPhysAddress  
A Layer 1 address which includes the hardware address space as well as the usual MAC address. This object is encoded in ASCII as ,,
where is the value of the hardware address space field, as used in ARP (i.e, 1 for Ethernet, 6 for token ring...) IANA has a list of registered numbers for this field. is the length of the address, in bytes (not ASCII chars)
is the ASCII hex-encoded address (2 ASCII characters per byte; 12 chars for an Ethernet address.) This encoding is intended to mirror the representation of MAC addresses in DHCP.
TEXTUAL-CONVENTION    
  OCTET STRING Size(1..32)  

CnrDHCPScopeEntry  
SEQUENCE    
  cnrDHCPScopeName DisplayString
  cnrDHCPScopeFreeAddrLowThreshold Unsigned32
  cnrDHCPScopeFreeAddrHighThreshold Unsigned32
  cnrDHCPScopeFreeAddrValue Unsigned32
  cnrDHCPScopeFreeAddrUnits INTEGER

Defined Values

ciscoNetworkRegistrarMIB 1.3.6.1.4.1.9.9.120
MIB for Cisco Network Registrar (CNR).
MODULE-IDENTITY    

ciscoNetworkRegistrarMIBObjects 1.3.6.1.4.1.9.9.120.1
OBJECT IDENTIFIER    

cnrDHCP 1.3.6.1.4.1.9.9.120.1.1
OBJECT IDENTIFIER    

cnrNotifObjects 1.3.6.1.4.1.9.9.120.1.2
OBJECT IDENTIFIER    

cnrNotifCfgObjects 1.3.6.1.4.1.9.9.120.1.3
OBJECT IDENTIFIER    

cnrDHCPScopeTable 1.3.6.1.4.1.9.9.120.1.1.1
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.
Status: deprecated Access: not-accessible
OBJECT-TYPE    
  SEQUENCE OF  
    CnrDHCPScopeEntry

cnrDHCPScopeEntry 1.3.6.1.4.1.9.9.120.1.1.1.1
An entry in the cnrDHCPScopeTable.
Status: deprecated Access: not-accessible
OBJECT-TYPE    
  CnrDHCPScopeEntry  

cnrDHCPScopeName 1.3.6.1.4.1.9.9.120.1.1.1.1.1
The name of the scope, which uniquely identifies an entry in the cnrDHCPScopeTable.
Status: deprecated Access: not-accessible
OBJECT-TYPE    
  DisplayString Size(1..100)  

cnrDHCPScopeFreeAddrLowThreshold 1.3.6.1.4.1.9.9.120.1.1.1.1.2
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.
Status: deprecated Access: accessible-for-notify
OBJECT-TYPE    
  Unsigned32  

cnrDHCPScopeFreeAddrHighThreshold 1.3.6.1.4.1.9.9.120.1.1.1.1.3
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.
Status: deprecated Access: accessible-for-notify
OBJECT-TYPE    
  Unsigned32  

cnrDHCPScopeFreeAddrValue 1.3.6.1.4.1.9.9.120.1.1.1.1.4
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.
Status: deprecated Access: accessible-for-notify
OBJECT-TYPE    
  Unsigned32  

cnrDHCPScopeFreeAddrUnits 1.3.6.1.4.1.9.9.120.1.1.1.1.5
The units associated with the value of cnrDHCPScopeFreeAddrValue.
Status: deprecated Access: accessible-for-notify
OBJECT-TYPE    
  INTEGER value(1), percent(2)  

cnrNotifDupIpAddress 1.3.6.1.4.1.9.9.120.1.2.1
The IP address which was found to be a duplicate.
Status: current Access: accessible-for-notify
OBJECT-TYPE    
  IpAddress  

cnrNotifMACAddress 1.3.6.1.4.1.9.9.120.1.2.2
The offending MAC address which caused a duplicate IP address to be detected.
Status: current Access: accessible-for-notify
OBJECT-TYPE    
  CnrPhysAddress  

cnrNotifServer 1.3.6.1.4.1.9.9.120.1.2.3
The IP Address of a server with which CNR is attempting to communicate.
Status: current Access: accessible-for-notify
OBJECT-TYPE    
  IpAddress  

cnrNotifServerType 1.3.6.1.4.1.9.9.120.1.2.4
The type of server.
Status: current Access: accessible-for-notify
OBJECT-TYPE    
  INTEGER dns(1), dhcp(2), ldap(3), tftp(4), ccm(5)  

cnrNotifDupIpAddressDetectedBy 1.3.6.1.4.1.9.9.120.1.2.5
For a ciscoNetRegDuplicateAddress notification, this object indicates whether the client or server detected the condition.
Status: current Access: accessible-for-notify
OBJECT-TYPE    
  INTEGER dhcpClient(1), dhcpServer(2)  

cnrNotifContestedIpAddress 1.3.6.1.4.1.9.9.120.1.2.6
The IP address for which ownership is claimed by two or more DHCP servers.
Status: current Access: accessible-for-notify
OBJECT-TYPE    
  IpAddress  

cnrNotifDHCPScopeFreeAddrLow 1.3.6.1.4.1.9.9.120.1.2.7
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.
Status: current Access: accessible-for-notify
OBJECT-TYPE    
  Unsigned32  

cnrNotifDHCPScopeFreeAddrHigh 1.3.6.1.4.1.9.9.120.1.2.8
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.
Status: current Access: accessible-for-notify
OBJECT-TYPE    
  Unsigned32  

cnrNotifDHCPScopeFreeAddrValue 1.3.6.1.4.1.9.9.120.1.2.9
The number of IP addresses which are available within the scope specified by the cnrDHCPScope object.
Status: current Access: accessible-for-notify
OBJECT-TYPE    
  Gauge32  

cnrNotifDHCPThresholdType 1.3.6.1.4.1.9.9.120.1.2.10
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.
Status: current Access: accessible-for-notify
OBJECT-TYPE    
  INTEGER scope(1), network(2), selectionTags(3)  

cnrNotifDHCPThresholdValue 1.3.6.1.4.1.9.9.120.1.2.11
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.
Status: current Access: accessible-for-notify
OBJECT-TYPE    
  DisplayString Size(1..100)  

cnrNotifDHCPScopeName 1.3.6.1.4.1.9.9.120.1.2.12
The name of the DHCP scope.
Status: current Access: accessible-for-notify
OBJECT-TYPE    
  DisplayString Size(1..100)  

cnrNotifPrimarySubnetNumber 1.3.6.1.4.1.9.9.120.1.2.13
The primary subnet number of the network interface of which the scope is part.
Status: current Access: accessible-for-notify
OBJECT-TYPE    
  DisplayString  

cnrNotifRelatedServerType 1.3.6.1.4.1.9.9.120.1.2.14
The type of related server.
Status: current Access: accessible-for-notify
OBJECT-TYPE    
  INTEGER dnsPrimary(1), ldap(2), failoverPartner(3)  

cnrNotifDnsServerIpAddress 1.3.6.1.4.1.9.9.120.1.2.15
The IP address of the DNS server.
Status: current Access: accessible-for-notify
OBJECT-TYPE    
  IpAddress  

cnrNotifZoneName 1.3.6.1.4.1.9.9.120.1.2.16
The name of the zone.
Status: current Access: accessible-for-notify
OBJECT-TYPE    
  DisplayString  

cnrNotifDnsRemoteServersList 1.3.6.1.4.1.9.9.120.1.2.17
Comma-separated list of remote server IP addresses.
Status: current Access: accessible-for-notify
OBJECT-TYPE    
  DisplayString Size(0..254)  

cnrEnableFreeAddressLow 1.3.6.1.4.1.9.9.120.1.3.1
Indicates whether the ciscoNetRegFreeAddressLow notification should be generated for this entity.
Status: deprecated Access: read-write
OBJECT-TYPE    
  TruthValue  

cnrEnableFreeAddressHigh 1.3.6.1.4.1.9.9.120.1.3.2
Indicates whether the ciscoNetRegFreeAddressHigh notification should be generated for this entity.
Status: deprecated Access: read-write
OBJECT-TYPE    
  TruthValue  

cnrEnableServerStart 1.3.6.1.4.1.9.9.120.1.3.3
Indicates whether the ciscoNetRegServerStart notification should be generated for this entity.
Status: current Access: read-write
OBJECT-TYPE    
  TruthValue  

cnrEnableServerStop 1.3.6.1.4.1.9.9.120.1.3.4
Indicates whether the ciscoNetRegServerStop notification should be generated for this entity.
Status: current Access: read-write
OBJECT-TYPE    
  TruthValue  

cnrEnableDNSQueueTooBig 1.3.6.1.4.1.9.9.120.1.3.5
Indicates whether the ciscoNetRegDNSQueueTooBig notification should be generated for this entity.
Status: current Access: read-write
OBJECT-TYPE    
  TruthValue  

cnrEnableOtherServerNotResponding 1.3.6.1.4.1.9.9.120.1.3.6
Indicates whether the ciscoNetRegOtherServerNotResponding notification should be generated for this entity.
Status: deprecated Access: read-write
OBJECT-TYPE    
  TruthValue  

cnrEnableDuplicateAddress 1.3.6.1.4.1.9.9.120.1.3.7
Indicates whether the ciscoNetRegDuplicateAddress notification should be generated for this entity.
Status: current Access: read-write
OBJECT-TYPE    
  TruthValue  

cnrEnableAddressConflict 1.3.6.1.4.1.9.9.120.1.3.8
Indicates whether the ciscoNetRegAddressConflict notification should be generated for this entity.
Status: current Access: read-write
OBJECT-TYPE    
  TruthValue  

cnrEnableOtherServerResponding 1.3.6.1.4.1.9.9.120.1.3.9
Indicates whether the ciscoNetRegOtherServerResponding notification should be generated for this entity.
Status: deprecated Access: read-write
OBJECT-TYPE    
  TruthValue  

cnrEnableFailoverConfigMismatch 1.3.6.1.4.1.9.9.120.1.3.10
Indicates whether the ciscoNetRegFailoverConfigMismatch notification should be generated for this entity.
Status: current Access: read-write
OBJECT-TYPE    
  TruthValue  

cnrEnableFreeAddrLow 1.3.6.1.4.1.9.9.120.1.3.11
Indicates whether the ciscoNetRegFreeAddrLowThreshold notification should be generated for this entity.
Status: current Access: read-write
OBJECT-TYPE    
  TruthValue  

cnrEnableFreeAddrHigh 1.3.6.1.4.1.9.9.120.1.3.12
Indicates whether the ciscoNetRegFreeAddrHighThreshold notification should be generated for this entity.
Status: current Access: read-write
OBJECT-TYPE    
  TruthValue  

cnrEnableOtherServerNotResp 1.3.6.1.4.1.9.9.120.1.3.13
Indicates whether the ciscoNetRegOtherServerNotResp notification should be generated for this entity.
Status: current Access: read-write
OBJECT-TYPE    
  TruthValue  

cnrEnableOtherServerResp 1.3.6.1.4.1.9.9.120.1.3.14
Indicates whether the ciscoNetRegOtherServerResp notification should be generated for this entity.
Status: current Access: read-write
OBJECT-TYPE    
  TruthValue  

cnrEnableHaDnsPartnerDown 1.3.6.1.4.1.9.9.120.1.3.15
Indicates whether the ciscoNetRegHaDnsPartnerDown notification should be generated for this entity.
Status: current Access: read-write
OBJECT-TYPE    
  TruthValue  

cnrEnableHaDnsPartnerUp 1.3.6.1.4.1.9.9.120.1.3.16
Indicates whether the ciscoNetRegHaDnsPartnerUp notification should be generated for this entity.
Status: current Access: read-write
OBJECT-TYPE    
  TruthValue  

cnrEnableMastersNotResp 1.3.6.1.4.1.9.9.120.1.3.17
Indicates whether the ciscoNetRegMastersNotResp notification should be generated for this entity.
Status: current Access: read-write
OBJECT-TYPE    
  TruthValue  

cnrEnableMastersResp 1.3.6.1.4.1.9.9.120.1.3.18
Indicates whether the ciscoNetRegMastersResp notification should be generated for this entity.
Status: current Access: read-write
OBJECT-TYPE    
  TruthValue  

cnrEnableSecondaryZoneExpired 1.3.6.1.4.1.9.9.120.1.3.19
Indicates whether the ciscoNetRegSecondaryZonesExpired notification should be generated for this entity.
Status: current Access: read-write
OBJECT-TYPE    
  TruthValue  

cnrEnableDnsForwardersNotResp 1.3.6.1.4.1.9.9.120.1.3.20
Indicates whether the ciscoNetRegDnsForwardersNotResp notification should be generated for this entity.
Status: current Access: read-write
OBJECT-TYPE    
  TruthValue  

cnrEnableDnsForwardersResp 1.3.6.1.4.1.9.9.120.1.3.21
Indicates whether the ciscoNetRegDnsForwardersResp notification should be generated for this entity.
Status: current Access: read-write
OBJECT-TYPE    
  TruthValue  

cnrEnableHaDnsConfigErr 1.3.6.1.4.1.9.9.120.1.3.22
Indicates whether the ciscoNetRegHaDnsConfigErr notification should be generated for this entity.
Status: current Access: read-write
OBJECT-TYPE    
  TruthValue  

ciscoNetRegMIBNotificationPrefix 1.3.6.1.4.1.9.9.120.2
OBJECT IDENTIFIER    

ciscoNetRegMIBNotifications 1.3.6.1.4.1.9.9.120.2.0
OBJECT IDENTIFIER    

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.
Status: deprecated Access: read-write
NOTIFICATION-TYPE    

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.
Status: deprecated Access: read-write
NOTIFICATION-TYPE    

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.
Status: current Access: read-write
NOTIFICATION-TYPE    

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.
Status: current Access: read-write
NOTIFICATION-TYPE    

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.
Status: current Access: read-write
NOTIFICATION-TYPE    

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.
Status: deprecated Access: read-write
NOTIFICATION-TYPE    

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.
Status: current Access: read-write
NOTIFICATION-TYPE    

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.
Status: current Access: read-write
NOTIFICATION-TYPE    

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.
Status: deprecated Access: read-write
NOTIFICATION-TYPE    

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.
Status: current Access: read-write
NOTIFICATION-TYPE    

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.
Status: current Access: read-write
NOTIFICATION-TYPE    

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.
Status: current Access: read-write
NOTIFICATION-TYPE    

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.
Status: current Access: read-write
NOTIFICATION-TYPE    

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.
Status: current Access: read-write
NOTIFICATION-TYPE    

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.
Status: current Access: read-write
NOTIFICATION-TYPE    

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.
Status: current Access: read-write
NOTIFICATION-TYPE    

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.
Status: current Access: read-write
NOTIFICATION-TYPE    

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.
Status: current Access: read-write
NOTIFICATION-TYPE    

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.
Status: current Access: read-write
NOTIFICATION-TYPE    

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.
Status: current Access: read-write
NOTIFICATION-TYPE    

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.
Status: current Access: read-write
NOTIFICATION-TYPE    

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.
Status: current Access: read-write
NOTIFICATION-TYPE    

ciscoNetworkRegistrarMIBConformance 1.3.6.1.4.1.9.9.120.3
OBJECT IDENTIFIER    

ciscoNetworkRegistrarMIBCompliances 1.3.6.1.4.1.9.9.120.3.1
OBJECT IDENTIFIER    

ciscoNetworkRegistrarMIBGroups 1.3.6.1.4.1.9.9.120.3.2
OBJECT IDENTIFIER    

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
Status: deprecated Access: read-only
MODULE-COMPLIANCE    

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
Status: current Access: read-only
MODULE-COMPLIANCE    

ciscoNetworkRegistrarDHCPScopeObjectsGroup 1.3.6.1.4.1.9.9.120.3.2.1
Network Registrar MIB objects used in DHCP scopes.
Status: deprecated Access: read-only
OBJECT-GROUP    

ciscoNetworkRegistrarNotifObjectsGroup 1.3.6.1.4.1.9.9.120.3.2.2
Network Registrar MIB objects used in notifications.
Status: deprecated Access: read-only
OBJECT-GROUP    

ciscoNetworkRegistrarNotifCfgObjectsGroup 1.3.6.1.4.1.9.9.120.3.2.3
Network Registrar MIB objects used to enable/disable notifications.
Status: deprecated Access: read-only
OBJECT-GROUP    

ciscoNetworkRegistrarNotificationsGroup 1.3.6.1.4.1.9.9.120.3.2.4
Notifications which are implemented by the Cisco Network Registrar agent.
Status: deprecated Access: read-only
NOTIFICATION-GROUP    

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.
Status: current Access: read-only
OBJECT-GROUP    

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.
Status: current Access: read-only
OBJECT-GROUP    

ciscoNetRegistrarNotificatGroup 1.3.6.1.4.1.9.9.120.3.2.7
Notifications which are implemented by the Cisco Network Registrar.
Status: current Access: read-only
NOTIFICATION-GROUP