Monitoring notification processing - BlueCat Integrity - 26.1.0

Address Manager Administration Guide
ft:locale
en-US
Product name
BlueCat Integrity
Version
26.1.0

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 the metrics services

By default, the Address Manager metrics service is enabled and collects information related to notification processing. You can navigate to the Notification metrics tab within the Dashboards page to view additional information about notification processing.

If you are using the metrics exporter service, you can monitor the following notification metrics using your observability platform:
bc_notification_pna_files
The number of notification files that are queued on Address Manager
bc_notification_pna_files_size_btyes
The total size of notification files on the Address Manager disk
bc_notification_per_second
The total size of notification files on the Address Manager disk
bc_notification_total
The total number of notification files received by Address Manager based on each service type and the status of how the notification was processed. The value has a label service for each service type and status for each status type. The service can be one of the following:
  • DHCPv4
  • DHCPv6
  • DNS
The status can be one of the following:
  • discarded
  • failed
  • received
  • succeeded

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.

Note: The following table is not an exhaustive list of available SNMP MIBs. For more information of all SNMP MIBs available in BAM, refer to Address Manager polled objects .
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:
  • DNS
  • DHCP
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
  • add
  • remove
  • update
DHCP
  • active
  • free
  • backup
  • expired
  • abandoned
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:
  • received
  • succeeded
  • failed
  • discarded
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.