When a BDDS processes an operation, such as releasing an IP address through DHCP or performing a DNS update operation from another primary DNS server, BDDS sends a notification file to Address Manager where it is processed by BAM and reflected in the database. If the BAM server can't process the notification file immediately, the notification file is stored on BAM until BAM can process the update. However, accumulation of these notification files consumes disk space on BAM and can cause the DNS/DHCP Server to go further out of sync with BAM, resulting in incorrect information being presented on BAM.
Monitoring notification processing using SNMP
When monitoring notification file processing on BAM using SNMP, BlueCat recommends polling the following SNMP Objects.
Each BlueCat-specific BAM MIB (management information base) OID (object identifier) begins with the following prefix of network management object identifiers:
.1.3.6.1.4.1.13315 That represent
iso.org.dod.internet.private.enterprise.bluecatnetworks.
| SNMP Object | OID | Access | Description |
|---|---|---|---|
| .backlogSize | .100.210.1.9.5 | Notification backlog size container | |
| .NotificationDistributionTable | .100.210.1.9.5.1 | Information about the notification backlog size. The objects returns a table that contains notifications in the backlog including the count, the IP address of the source DNS/DHCP Server, the type of notification, the category of the notification, and the state of the notification. | |
| .distributionTableEntry | .100.210.1.9.5.1.1 | Not-accessible | Information about notification entry container Attention: The SNMP service must be configured to use SNMP
version v2c or v3 to receive information from this
OID.
|
| .count | .100.210.1.9.5.1.1.1 | Read-only | Number of notifications Attention: The SNMP service
must be configured to use SNMP version v2c or v3 to receive
information from this OID.
|
| .bddsServerID | .100.210.1.9.5.1.1.2 | Not-accessible | Server ID of the source DNS/DHCP Server Attention: The SNMP service must be configured to use SNMP
version v2c or v3 to receive information from this
OID.
|
| .serviceType | .100.210.1.9.5.1.1.3 | Not-accessible | Type of notification. The type can be one of the following:
Attention: The SNMP service must be configured to
use SNMP version v2c or v3 to receive information from this
OID.
|
| .serviceAction | .100.210.1.9.5.1.1.4 | Not-accessible | Category of the notification type. The category can be the
following based on the notification type: DNS
DHCP
Attention: The SNMP service must be
configured to use SNMP version v2c or v3 to receive information
from this OID.
|
| .state | .100.210.1.9.5.1.1.5 | Not-accessible | State of the notification. The state can be one of the
following:
Attention: The SNMP service must be configured to
use SNMP version v2c or v3 to receive information from this
OID.
|
| .fileSystemFootprint | .100.210.1.9.5.2.0 | Read-only | Total size of the notification backlog (in kilobytes) Attention: The SNMP service must be configured to use SNMP
version v2c or v3 to receive information from this
OID.
|
| .notificationServiceStartTime | .100.210.1.9.6.0 | Read-only | Start time of the notification service Attention: The
SNMP service must be configured to use SNMP version v2c or v3 to
receive information from this OID.
|