Creating an xHA cluster - User Guide - Micetro - 26.1.0

To create an xHA cluster:

1. Navigate to Admin > Service management > Appliances.
2. In the data grid, select one or both appliances you want to be in the cluster.
   • If you select one appliance, this will be the active node in the cluster.
   • If you select two appliances, you can configure which of the servers becomes the active node.
3. Select Action and then select Create xHA cluster in the dropdown.
4. In the dialog, enter the required information for the xHA cluster:
   
   
   • Active node: Select an appliance to be the active node in the cluster.
   • Passive node: Select an appliance to be the passive node in the cluster.
   • For the Service interface:
     • New active node private IP address: A new constant service IP address for the active node. This address will be used as the cluster's virtual IP address. Enter a new IP address that will be private to the active node in this field.
   • For the Management interface:
     • New active node private management IP address: (Only required if dedicated management is enabled on the active node.) A new constant management IP address for the active node. This address will be used as the cluster's virtual management IP address. Enter a new management IP address that will be private to the active node in this field.
   • Ping address: An optional IP address to set as the ping address for the cluster.
   • Enable xHA backbone: Select the checkbox to enable xHA backbone communication, which provides secure and reliable data transfer between the xHA nodes. If you select this option, enter the following information to configure the backbone IP addreses and netmasks for the active and passive nodes:
     • Backbone address on active node
     • Backbone address on passive node
     • Backbone subnet netmask: The numerical netmask of the subnet to which the backbone IP addresses belong

     Make sure the IP addresses of the xHA interfaces (eth1) are on a different subnet than any other interfaces, such as service/management interfaces, or non-routable IPs. If the MDDS appliances 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.

     Note: To avoid split-brain scenarios (where both appliances are active or passive at the same time), the use of xHA backbone communication is mandatory.

   • The xHA cluster's Virtual cluster IP address and Passive node private IP address will be auto-populated.

   • Select Save.

Once you create an xHA cluster, the appliance Type for the cluster members in the data grid changes from MDDS to xHA.