cisco-network-registrar-mib.mib object
Introduction
Most network devices and programs ship with so-called MIB files to describe the parameters and meanings (i.e.: friendly names) which are available for monitoring via SNMP.
ActiveXperts Network Monitor 2025 can import vendor-specific MIB files, so it can be used to monitor specific OID's (Object Identifiers).
This way, you can monitor your devices, computers, etc. by selecting your relevant OID's by name.
ActiveXperts Network Monitor 2025 can import MIB file cisco-network-registrar-mib and use it to monitor vendor specific OID's.
cisco-network-registrar-mib file content
Object view of cisco-network-registrar-mib:
| Scalar Object |
| cnrDHCPScopeEntry |
.1.3.6.1.4.1.9.9.120.1.1.1.1 |
|
An entry in the cnrDHCPScopeTable.
|
| cnrNotifDupIpAddress |
.1.3.6.1.4.1.9.9.120.1.2.1 |
|
The IP address which was found to be a duplicate.
|
| 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.
|
| 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.
|
| cnrNotifServerType |
.1.3.6.1.4.1.9.9.120.1.2.4 |
|
The type of server
|
| 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.
|
| 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.
|
| cnrEnableFreeAddressLow |
.1.3.6.1.4.1.9.9.120.1.3.1 |
|
Indicates whether notifications should be generated
for this entity. The default is disabled (FALSE).
|
| cnrEnableFreeAddressHigh |
.1.3.6.1.4.1.9.9.120.1.3.2 |
|
Indicates whether notifications should be generated
for this entity. The default is disabled (FALSE).
|
| cnrEnableServerStart |
.1.3.6.1.4.1.9.9.120.1.3.3 |
|
Indicates whether notifications should be generated
for this entity. The default is disabled (FALSE).
|
| cnrEnableServerStop |
.1.3.6.1.4.1.9.9.120.1.3.4 |
|
Indicates whether notifications should be generated
for this entity. The default is disabled (FALSE).
|
| cnrEnableDNSQueueTooBig |
.1.3.6.1.4.1.9.9.120.1.3.5 |
|
Indicates whether notifications should be generated
for this entity. The default is disabled (FALSE).
|
| cnrEnableOtherServerNotResponding |
.1.3.6.1.4.1.9.9.120.1.3.6 |
|
Indicates whether notifications should be generated
for this entity. The default is disabled (FALSE).
|
| cnrEnableDuplicateAddress |
.1.3.6.1.4.1.9.9.120.1.3.7 |
|
Indicates whether notifications should be generated
for this entity. The default is disabled (FALSE).
|
| cnrEnableAddressConflict |
.1.3.6.1.4.1.9.9.120.1.3.8 |
|
Indicates whether notifications should be generated
for this entity. The default is disabled (FALSE).
|
| cnrEnableOtherServerResponding |
.1.3.6.1.4.1.9.9.120.1.3.9 |
|
Indicates whether notifications should be generated
for this entity. The default is disabled (FALSE).
|
| cnrEnableFailoverConfigMismatch |
.1.3.6.1.4.1.9.9.120.1.3.10 |
|
Indicates whether notifications should be generated
for this entity. The default is disabled (FALSE).
|
| Tabular Object |
| 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.
|
| 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.
|
| 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.
|
| 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.
|
| cnrDHCPScopeFreeAddrUnits |
.1.3.6.1.4.1.9.9.120.1.1.1.1.5 |
|
The units associated with the value of
cnrDHCPScopeFreeAddrValue.
|
| Table |
| 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.
|
| Trap |
| 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.
|
| 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.
|
| 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.
|
| 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.
|
| 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 |
.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.
|
| 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.
|
| 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.
|
| 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.
|
| 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.
|
| Object Identifier |
| 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 |
| cnrNotifObjects |
.1.3.6.1.4.1.9.9.120.1.2 |
| cnrNotifCfgObjects |
.1.3.6.1.4.1.9.9.120.1.3 |
| 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 |
| Group |
| 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.
|
