Deployment: New Cluster Settings Parent topic

A new HA cluster is created through the Deployment Wizard interface. When a new HA cluster is created, the management system configures the HA Agent with the desired policy settings and stores it on the parent member. Parent members are the only units that can be actively configured. A child member receives regular updates from the parent member to stay synchronized with the latest configuration and policy information.
  • Note
    Note
    Only IPv4 HA Cluster IP addresses are supported. IPv6 HA Cluster IP addresses are not supported.

About the HA (or Heartbeat) Interface

Active and passive IWSVAs are connected directly though the HA or "Heartbeat" interface. The interface, labeled H in the interface status graphic, has two functions:
  • Active and passive virtual appliances send a package per second to notify each other they are up and running.
  • The interface is used in the synchronization process.
To create a new cluster:
  1. Click the Transparent Bridge Mode - High Availability option on the Deployment Mode page.
  2. Click the New Cluster option.
  3. Click Next.
  4. Set the Cluster Settings, which include:
    1. Type a cluster name.
    2. Type an (optional) cluster description.
    3. Type the Cluster IP address.
    4. Select Enable or Disable from the Weighted Priority Election drop-down list.
      • If enabled, the HA pair launches an election to choose the maximum-weighted machine.
      • If disabled, the HA pair only launches an election when the current active (primary) machine is not available.
      Note
      Note
      The HA mode displays as Active/Passive and the Deployment mode always shows Bridge to indicate Transparent Bridge Mode - High Availability.
    5. Using the information in the Interface Status section, select the HA Interface from the drop-down list (eth0, eth1, eth2, eth3, etc.) Active and passive IWSVAs are connected directly though the HA or "Heartbeat" interface. The interface, labeled H in the interface status graphic, has two functions:
      • Active and passive virtual appliances send a package per second to notify each other they are up and running.
      • The interface is used in the synchronization process.
    6. Enter the Weight value. (Default 128)
      • The member with the higher weighting has higher priority and becomes the parent member.
  5. Click Next.
  6. Set up the Network Interface to continue the deployment.