Rules for repairing xHA - BlueCat Address Manager - 9.0.0

Address Manager Administration Guide

prodname
BlueCat Address Manager
version_custom
9.0.0

Rules and guidelines for using the xHA repair function in Address Manager.

You must have the same DNS/DHCP Server software version on both the Active node and the replacement node.

If the Active node is running DNS/DHCP Server software v9.0.0, and the replacement node is running DNS/DHCP Server v8.3.0, the replacement node will be automatically upgraded to match the software version running on the Active node. This will allow the xHA repair to complete successfully. Automatic upgrade of the software on the replacement node is not supported if the Active node is running DNS/DHCP Server v8.2.0 or earlier.
Note: xHA repair with VLAN interfaces
  • If the Active node is running DNS/DHCP Server v9.0.0 and configured with VLAN interfaces, the replacement node must also be running software version 9.0.0 and the Primary IPv4 address must be configured on the same services interface as the disconnected/failed node. That is, the same physical interface (eth0/bond0) or virtual interface (eth0.xxx). In addition, the Primary IPv4 address of the replacement node must be the same as that of the disconnected/failed node.
  • If you are running xHA with VLAN and Dedicated Management, you must also enable Dedicated Management and configure the Management interface (eth2) on the Passive node prior to repairing xHA.

The following table describes the general xHA repair rules depending on the installed software versions.

General xHA repair rules (VLAN interfaces not configured)
Active Node software version Replacement Node software version Expected behavior
DNS/DHCP Server v9.0.0 DNS/DHCP Server v9.0.0 Repair completes successfully.
DNS/DHCP Server v9.0.0 DNS/DHCP Server v8.3.2/v8.3.1/v8.3.0/v8.2.0 Address Manager automatically upgrades the software on the replacement node to match the Active node, then xHA repair completes successfully.
DNS/DHCP Server v8.3.2 DNS/DHCP Server v8.3.2 Repair completes successfully.
DNS/DHCP Server v8.3.2 DNS/DHCP Server v8.3.1/v8.3.0/v8.2.0 Address Manager automatically upgrades the software on the replacement node to match the Active node, then xHA repair completes successfully.
DNS/DHCP Server v8.3.1 DNS/DHCP Server v8.3.1 Repair completes successfully.
DNS/DHCP Server v8.3.1 DNS/DHCP Server Server v8.3.0/v8.2.0 Address Manager automatically upgrades the software on the replacement node to match the Active node, then xHA repair completes successfully.
DNS/DHCP Server v8.3.0 DNS/DHCP Server v8.3.0 Repair completes successfully.
DNS/DHCP Server v9.0.0/v8.3.2/v8.3.1/v8.3.0/v8.2.0 DNS/DHCP Server v8.1.1 Repair fails. You must manually upgrade the software on the replacement node to match the software version of the Active node and run xHA repair again.

The following tables describes the xHA repair rules if VLAN interfaces are configured on an xHA pair.

xHA Repair rules with VLAN interfaces and/or Dedicated Management
Active node software version Replacement node software version Expected behavior
DNS/DHCP Server v9.0.0 (configured with VLAN interfaces and/or Dedicated Management) DNS/DHCP Server v9.0.0 (Primary IPv4 address must be the same as that of the disconnected/failed node and must be configured on the same services and management interfaces as the disconnected node, either eth0, bond0, eth0.xxx and eth2) Repair completes successfully.
Note: You must have the same DNS/DHCP Server software version on both the Active node and the replacement node. If Dedicated Management is enabled on the Active Node it must also be enabled on the replacement node.
DNS/DHCP Server v9.0.0 (configured with VLAN interfaces and/or Dedicated Management) DNS/DHCP Server v9.0.0 (not configured with VLAN interfaces or Dedicated Management) Repair fails. You must configure the Replacement node with at least one identical VLAN sub-interface on a physical interface (eth0/bond0) and the same Primary IPv4 address as the Active node (and enable Dedicate Management if it is enabled on the Active node), then run xHA repair again.
DNS/DHCP Server v9.0.0 (configured with VLAN interfaces and/or Dedicated Management) DNS/DHCP Server v8.3.2/v8.3.1/v8.3.0/v8.2.0 (Primary IPv4 address must be the same as that of the disconnected/failed node and must be configured on the same services and management interfaces as the disconnected node, either eth0, bond0, eth0.xxx and eth2) Address Manager automatically upgrades the software on the replacement node to match the Active node, then xHA repair completes successfully.
Note: You must have the same DNS/DHCP Server software version on both the Active node and the replacement node. If Dedicated Management is enabled on the Active Node it must also be enabled on the replacement node.
DNS/DHCP Server v9.0.0 (configured with VLAN interfaces and/or Dedicated Management) DNS/DHCP Server v8.1.1 Repair fails. VLAN interfaces are only supported on software version 8.3.0 or later. You must manually upgrade the software on the replacement node to match the software on the Active node, configure at least one identical VLAN sub-interface on a physical interface (eth0/bond0) and the same Primary IPv4 address as the Active node, then run xHA repair again.
Note: If Dedicated Management is enabled on the Active node it must also be enabled on the replacement node.
DNS/DHCP Server v9.0.0 (configured with Dedicated Management - eth2) DNS/DHCP Server v8.2.0 (IPv4 addresses on Service interface—eth0|bond0—and the Management interface—eth2—must be the same as that of the disconnected/failed node) Address Manager automatically upgrades the software on the replacement node to match the Active node, then xHA repair completes successfully.