Views:

Purpose: You can create an HA group from Cloud Edge Cloud Console. An HA group consists of two Cloud Edge gateways. The gateways can be registered or unregistered. A gateway can belong to only one HA Group.

Location: Gateways

  1. Review information about HA Groups as needed.

    HA Groups

  2. Connect an Ethernet cable directly between the heartbeat interfaces for each gateway that will be a member of the HA group.

    For the Cloud Edge 50G2 gateway, you can use only eth2 or eth3 for the heartbeat L3 interface. Moreover, you must use the same interface on each gateway (eth2-to-eth2 or eth3-to-eth3).

  3. In the High Availability Management section, click Create HA Group. The Create HA Group wizard opens.
  4. In the Create HA Group and Choose Operation Mode page, specify the following details:
    Option Description

    HA group name

    Name must be between 1 to 32 characters long and can contain letters, numbers, or the underline symbol.

    Operation mode

    Preset to Active-Passive, which is the only available mode.

    Authentication method

    Select one of the following:

    • None

    • Simple and then enter the password to use for simple authentication

    Enable

    Select one of the following:

    • On

    • Off
  5. Click Next.
  6. In the Configure Primary Gateway page, configure settings for the Cloud Edge gateway that will be the primary gateway in the HA group.
    Option Description

    Primary HA gateway

    Select the gateway from the drop-down list that you want to designate as the HA primary gateway.

    Only gateways that support an HA group configuration are listed.

    Role

    A read-only field set to Primary, which is the role that will be assigned to this gateway.

    Priority

    Enter a priority number for this gateway (1-253). Default is 253.

    The gateway with the higher the priority is active.

    Heartbeat interface

    Select the L3 interface from the drop-down that Cloud Edge uses for communicating with the peer HA gateway.

    For the Cloud Edge 50G2 gateway, only eth2 or eth3 can be selected as the heartbeat interface.
    Heartbeat interface IP / Netmask

    If not already configured, you must enter an IPv4 address and netmask for the heartbeat interface.

    The heartbeat interface's IPv4 address for the primary and secondary gateways must be on the same subnet.

    After adding an interface to an HA pair, you cannot change the primary or secondary gateways for that interface.
  7. Click Next.
  8. In the Configure Secondary Gateway page, configure settings for the Cloud Edge gateway that will be the secondary gateway in the HA group.
    Option Description

    Secondary HA gateway

    Select the gateway from the drop down list that you want to designate as the HA secondary gateway.

    Only gateways that support an HA group configuration are listed.

    Role

    A read-only field set to Secondary, which is the role that will be assigned to this gateway.

    Priority

    Enter a priority number for this gateway (1-253). Default is 100.

    The gateway with the higher the priority is active.

    Heartbeat interface

    The L3 interface is preselected from the drop-down and is the same interface selected for the primary HA gateway.

    Cloud Edge uses the interface for communicating with the peer HA gateway.
    Heartbeat interface IP / Netmask

    If not already configured, you must enter an IPv4 address and netmask for the heartbeat interface. It must be on the same subnet as the heartbeat IP address configured for the primary.
  9. Click Next.
  10. In the Configure Takeover When Failure Occurs page, configure settings for the Cloud Edge HA group when a failure happens and takeover occurs.
    Option Description

    Preemption

    Select one of the following:

    • On (default): Primary gateway will return to active role after it recovers from a previous failure

    • Off: Primary gateway does not automatically resume the active role after recovery from a failure. User must perform manual failover.

    Monitor interface

    Select one or more interfaces to monitor. Cloud Edge monitors only physical interfaces. It is recommended to monitor all physical interfaces with traffic.

    Monitor IP/FQDN

    For each monitor interface, enter up to two IP addresses or FQDNs to use as monitor hosts.

    Takeover triggers

    You must enter values for the following:

    • Heartbeat failure times: Indicates the number of heartbeat failures before the passive gateway takes over from the failed gateway (default is 3, range is 3-6)

    • Ping failure times: Indicates the number of ping failures before the passive gateway takes over from the failed gateway (default is 3, range is 3-6)
  11. In the Configure Virtual Router Redundancy Protocol (VRRP) Group page, add one or more VRRP groups.
    1. Click Add.
    2. Select an interface and enter the virtual IPv4 Address and netmask for the VRRP group.

      You can select either an L3 physical interface or a static L3 VLAN interface, depending on the configuration.

      See HA Group – VRRP Groups configuration requirements.

    3. Save the VRRP group by clicking on the check mark to the right of the IP Address/Mask field.

      You must add and save at least one VRRP group before clicking Next.

      Note:

      You can delete a VRRP group by clicking on the "X" to the right of the VRRP group that you want to delete.

    After clicking Next, the summary page opens.
  12. Review the summary of the HA group settings.
    Note:

    The primary HA gateway is active and the secondary HA gateway is passive when you first create an HA group.

  13. Click Save.
Parent topic: Managing Gateways