Adding or removing the xHA backbone connection - BlueCat Integrity - 26.1.0

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

Configure the xHA backbone on eth1 for data synchronization between nodes in an xHA pair.

If you didn't already configure the xHA backbone connection when adding an DNS/DHCP Server or creating your xHA pair, you can add the xHA backbone connection without needing to break xHA.

Attention: Make sure to configure the IP addresses of the xHA interfaces (eth1) on a different subnet than any other interfaces. This is the recommended best practice for direct xHA backbone connections and connections over switches or wide area networks (WAN), but is not mandatory if you're using a direct connection to the eth1 interface on each DNS/DHCP Server. In addition, if the DNS/DHCP Servers are not connected by a direct ethernet xHA backbone connection, the xHA interfaces should be separated onto a different LAN segment to prevent the xHA interfaces from receiving layer-2 broadcast traffic intended for other interfaces. This can be achieved by separate VLANs for each interface, private networks (for virtual appliances), or separate physical switches. For information and help on running xHA with switches, contact BlueCat Customer Care. For details on creating an xHA pair in Address Manager, refer to Managing xHA.

If you have re-configured your network implementation and want to re-allocate the xHA interface (eth1) on your DNS/DHCP Servers, you can remove the xHA backbone connection from your xHA cluster.

Note: When the xHA backbone connection is disabled, the IP address assigned to the xHA interface (eth1) remains on the node. Viewing the interface details of the respective DNS/DHCP Server nodes allows you to view the xHA backbone IP address and netmask. For details, refer to Viewing xHA status.
Note: You can disable the xHA backbone without breaking xHA.

To add or remove the xHA backbone connection:

  1. Select the Servers tab in the sidebar, then select Servers.
  2. Select the row actions button (⋮) for an xHA pair, then select Edit.
  3. To enable/disable backbone communication: On the xHA backbone tab, set the following parameters:
    • Enable xHA backbone communication—select this checkbox to enable xHA backbone communication. Additional fields appear to configure the backbone IP addresses and netmasks/prefixes for the active and passive nodes. If you previously configured the xHA backbone when adding the DNS/DHCP Server or creating xHA, the IP addresses and netmasks/prefixes for the active and passive nodes will be pre-populated with the existing values. If this is your first time configuring the xHA backbone connection, enter the IP address and netmask/prefix lengths for the active and passive servers.
      Note: If you added an xHA backbone IP address when initially adding your DNS/DHCP Server to Address Manager, that value will be used to populate the fields for the active and passive servers. If desired, you can edit the IP addresses and netmasks/prefixes to overwrite the initial xHA backbone settings.
      Attention: Make sure to configure the IP addresses of the xHA interfaces (eth1) on a different subnet than any other interfaces. This is the recommended best practice for direct xHA backbone connections and connections over switches or wide area networks (WAN), but is not mandatory if you're using a direct connection to the eth1 interface on each DNS/DHCP Server. In addition, if the DNS/DHCP Servers are not connected by a direct ethernet xHA backbone connection, the xHA interfaces should be separated onto a different LAN segment to prevent the xHA interfaces from receiving layer-2 broadcast traffic intended for other interfaces. This can be achieved by separate VLANs for each interface, private networks (for virtual appliances), or separate physical switches. For information and help on running xHA with switches, contact BlueCat Customer Care. For details on creating an xHA pair in Address Manager, refer to Managing xHA.
      Note: When configuring an IPv6 address for the xHA backbone, the prefix must be set between the accepted CIDR range of 64 to 127.
  4. On the Change control tab, add change control comments, if required.
  5. Select Save.