BCN-HA-MIB

All MIBs › BCN-HA-MIB

Organization: BlueCat Networks

Last Updated: 2010-12-15

Category: VPN and Security, Vendor: BlueCat Networks

Description: Monitors high-availability (HA) cluster state, failover status, and replication health on BlueCat Networks appliances.

Start monitoring vendor-neutral, standards-based MIB, any SNMPv3-capable network device (SNMP engine identity/boot/clock status) with a free 30-day trial of IPNetwork Monitor. Import MIBs, browse SNMP OIDs, create custom SNMP monitors, configure alerts, and monitor any SNMP-enabled network device from a single console.

What Is BCN-HA-MIB?

BCN-HA-MIB is a vendor-specific SNMP module from BlueCat Networks for monitoring high-availability (HA) clustering, failover state, and replication health on BlueCat DNS/DHCP/IPAM appliances. It exposes the HA service's operational state and replication state, an address table mapping virtual, physical, and peer IP addresses used in the HA pairing, and an alarm severity object with an associated notification for HA-related faults. This is a software/service-status monitoring MIB focused on cluster resilience: bcnHaSerOperState and bcnHaSerReplicationState reveal whether the HA service is active and whether configuration/data replication between HA peers is healthy or has fallen behind/failed, which are critical indicators for detecting a split-brain condition or a failed standby node before it impacts DNS/DHCP service availability. It complements the related BCN-COMMANDSERVER-MIB and other BlueCat appliance MIBs within the same vendor management framework and relies on the standard SNMP NOTIFICATION-TYPE mechanism for bcnHaNotification. Typical deployment context is enterprise/service-provider DNS/DHCP/IPAM infrastructure deployed as HA pairs for high availability. Engineers can download the BCN-HA-MIB file directly to load it into their MIB browser.

IPNetwork Monitor allows you to monitor SNMP objects defined in BCN-HA-MIB. Use the built-in SNMP Monitoring Browser to explore available variables, view their current values and descriptions, and select the objects you want to monitor. You can then create SNMP monitors, configure thresholds, and receive alerts when monitored values change.

Supported Devices

BlueCat Networks DNS/DHCP/IPAM appliance (HA pair)

Monitoring Examples

An administrator would poll bcnHaSerOperState and bcnHaSerReplicationState to confirm both HA peers are active and in sync, and walk bcnHaSerAddressTable/Entry (via bcnHaSerAddrTableIndex) to verify bcnHaSerVirtualAddress, bcnHaSerPhysicalAddress, and bcnHaSerPeerAddress are correctly configured for the pair. A bcnHaSerReplicationState showing a stalled or degraded state would indicate the standby appliance is not receiving current configuration/lease data, risking an outdated failover target. Receiving a bcnHaNotification trap with an elevated bcnHaAlarmSeverity would alert operators to an HA fault requiring investigation before a failover event occurs.

What Can Be Monitored

HA operational state
replication state
virtual/physical/peer address configuration
HA alarm severity/notifications

Imported Objects

From BCN-SMI-MIB

bcnServices

OBJECT-IDENTITY

From BCN-TC-MIB

BcnAlarmSeverity

From INET-ADDRESS-MIB

InetAddress
InetAddressType

From SNMPv2-CONF

MODULE-COMPLIANCE
NOTIFICATION-GROUP
OBJECT-GROUP

From SNMPv2-SMI

MODULE-IDENTITY
NOTIFICATION-TYPE
OBJECT-IDENTITY
OBJECT-TYPE
Unsigned32

From SNMPv2-TC

DisplayString

How to Use in IPNetwork Monitor

Example using bcnHaSerOperState OID:

Select a BlueCat Networks DNS/DHCP/IPAM appliance as the target host to create a monitor — the SNMP service should be up and running on it. Click New Monitor, then check SNMP Custom on the Favorites tab, click Next, and confirm the host. On the next page, click Select... to open the built-in SNMP MIB Browser and type bcnHaSerOperState into the Find box to locate it in the OID tree, then select it and click OK. The operational state of this clustered service — standalone, active, passive standby, stopped, stopping, becoming active, becoming passive, or fault. On the monitor's Main parameters page you can set the target's SNMP port (default 161), credentials, polling interval, and other settings — see the SNMP Monitor help for details. On the State conditions and Alerting tabs, configure when the monitor should change state and trigger an alert; since this is an INTEGER-type OID, Value bounds is the most useful condition here — trigger an alert if the value is 'fault' or 'stopped', or it changes between standalone/active/passive unexpectedly, since which role is correct for this node depends on your clustering configuration and an unplanned change often indicates a failover. Click Finish to create the monitor; you can adjust any parameter later.

OIDs

OID symbolic	OID numeric	Type	Access	Description
bcnHa	1.3.6.1.4.1.13315.3.1.5
bcnHaMIB	1.3.6.1.4.1.13315.3.1.5.1			This module provides status as well as statistical information about the HA service.
bcnHaObjects	1.3.6.1.4.1.13315.3.1.5.2
bcnHaServiceStatus	1.3.6.1.4.1.13315.3.1.5.2.1			General state of the HA Service.
INT bcnHaSerOperStateEx	1.3.6.1.4.1.13315.3.1.5.2.1.1	INTEGER	read-only	Operational state of the Service. The possible states are: standalone(1) The node is not configured to provide clustering services. active(2) The system is operational and the node is providing clustering services. passive(3) The system is operational and the node is active as a passive standby for the cluster. stopped(4) The service is stopped either intentionally (i.e.: the service is not supposed to run on this node) or unintentionally (a problem has occurred). This state might apply to both standalong and clustered nodes. stopping(5) The service is in the process of stopping. Stopping a service might be necessary after a configuration change. becomingActive (6) The node is becoming active, either as a result of a switchover or by initial start. becomingPassive (7) The node is failing over. Another node is taking charge of the services. fault(8) An error has been detected and the state is undefined.
INT bcnHaSerReplicationState	1.3.6.1.4.1.13315.3.1.5.2.1.2	INTEGER	read-only	The current state of the replication. All nodes in a cluster must be in synch in order for HA to work correctly. The nodes might be temporarily out of synch during cluster creation or when one of the nodes has been down for a while.
bcnHaSerAddressTable	1.3.6.1.4.1.13315.3.1.5.2.1.3		not-accessible	This table keeps the information about the network addresses for the clustered nodes. Most of the time this table will contain one or two rows, depending on the type of IPs configured for clustering.
bcnHaSerAddressEntry	1.3.6.1.4.1.13315.3.1.5.2.1.3.1		not-accessible	A logical row in the bcnHaSerAddressTable.
U32 bcnHaSerAddrTableIndex	1.3.6.1.4.1.13315.3.1.5.2.1.3.1.1	Unsigned32	not-accessible	This index will normally be 0 or 1
IPt bcnHaSerVirtualAddressType	1.3.6.1.4.1.13315.3.1.5.2.1.3.1.2	InetAddressType	read-only	The type of address stored in bcnHaSerVirtualAddress.
IP bcnHaSerVirtualAddress	1.3.6.1.4.1.13315.3.1.5.2.1.3.1.3	InetAddress	read-only	The virtual IP address configured for this node. The type of this mib variable is defined in bcnHaSerVirtualAddressType. This address binds to the active node at all times.
IPt bcnHaSerPhysicalAddressType	1.3.6.1.4.1.13315.3.1.5.2.1.3.1.4	InetAddressType	read-only	The type of address stored in bcnHaSerPhysicalAddress.
IP bcnHaSerPhysicalAddress	1.3.6.1.4.1.13315.3.1.5.2.1.3.1.5	InetAddress	read-only	The physical IP address configured for this node. The type of this mib variable is defined in bcnHaSerPhisicalAddressType. This address is not affected by switchover events.
IPt bcnHaSerPeerAddressType	1.3.6.1.4.1.13315.3.1.5.2.1.3.1.6	InetAddressType	read-only	The type of address stored in bcnHaSerPeerAddress.
IP bcnHaSerPeerAddress	1.3.6.1.4.1.13315.3.1.5.2.1.3.1.7	InetAddress	read-only	The physical IP address configured for the peer node. The type of this mib variable is defined in bcnHaSerPeerAddressType. This address is not affected by switchover events.
bcnHaNotification	1.3.6.1.4.1.13315.3.1.5.3
bcnHaNotificationEvents	1.3.6.1.4.1.13315.3.1.5.3.0
NTF bcnHaAlarmNotif	1.3.6.1.4.1.13315.3.1.5.3.0.1			A bcnHaAlarmNotif signifies that the HA service has transitioned state or a particular event has been detected on the service.
bcnHaNotificationData	1.3.6.1.4.1.13315.3.1.5.3.1
BCN bcnHaAlarmSeverity	1.3.6.1.4.1.13315.3.1.5.3.1.1	BcnAlarmSeverity	accessible-for-notify	Severity classification for the alarm.
STR bcnHaAlarmInfo	1.3.6.1.4.1.13315.3.1.5.3.1.2	DisplayString	accessible-for-notify	Descriptive information about the alarm event.
bcnHaConformance	1.3.6.1.4.1.13315.3.1.5.4
bcnHaServiceCompliances	1.3.6.1.4.1.13315.3.1.5.4.1
bcnHaStatusCompliance	1.3.6.1.4.1.13315.3.1.5.4.1.1			Basic conformance
bcnHaServiceGroups	1.3.6.1.4.1.13315.3.1.5.4.2
bcnHaServiceStatusGroup	1.3.6.1.4.1.13315.3.1.5.4.2.1			Status conformance.
bcnHaNotificationEventGroup	1.3.6.1.4.1.13315.3.1.5.4.2.2			Server statistics conformance.
bcnHaNotificationDataGroup	1.3.6.1.4.1.13315.3.1.5.4.2.3			Server statistics conformance.

RFC description

Tracks BlueCat Networks high availability service status and operational state for DNS infrastructure management.

Start monitoring BlueCat Networks DNS/DHCP/IPAM appliances with a free 30-day trial of IPNetwork Monitor. Import MIBs, browse SNMP OIDs, create custom SNMP monitors, configure alerts, and monitor any SNMP-enabled network device from a single console.

Download BCN-HA-MIB