Only the configuration related to load-balancing services is synchronized.

We consider a couple of ALOHA Load-Balancers with the following details:

Name

IP

Description

LB1

10.0.32.11

will be the Master

LB2

10.0.32.12

will be the Slave

Virtual IP

10.0.32.20

Default Gateway

10.0.32.1

Synchronize the service

  1. Browse the ALOHA WUI.

  2. Open the Services tab and scroll down to the bottom of the page.

  3. Click on [advanced mode].

  4. Scroll down to the csyncd service line.

    //cdn.haproxy.com/de/documentation/aloha/8-5/_assets/images/csyncd_service_advanced.png
  5. Click Edit . A text area containing an empty csyncd configuration appears:

    LOCAL_IP=
    REMOTE_IP=
    LOCAL_NODE=
    REMOTE_NODE=
  6. Configure as described below:

    LOCAL_IP

    IP address of currently configured ALOHA node

    REMOTE_IP

    IP address of the second node of the cluster

    LOCAL_NODE

    Unique ID of the current node in the cluster.

    There are no conventions, but we usually configure:

    • 1 for the Master

    • 2 for the Slave

    Example cluster configuration

    LB1 (Master)

    LOCAL_IP=10.0.32.11
    REMOTE_IP=10.0.32.12
    LOCAL_NODE=1
    REMOTE_NODE=2

    LB2 (Slave)

    LOCAL_IP=10.0.32.12
    REMOTE_IP=10.0.32.11
    LOCAL_NODE=2
    REMOTE_NODE=1
  7. Click ok.

  8. Click close.

Note

Before proceeding to the next step, run the procedure above on both members of a cluster.

Set daemon parameters

  1. Browse the ALOHA WUI.

  2. Open the Services tab.

  3. Scroll down to the csyncd service line.

  4. Click Setup setup_icon.

  5. Remove the line no autostart.

  6. Click ok.

  7. Click close.

Note

Before proceeding to the next step, run the procedure above on both members of a cluster.

Configure the key exchange

  1. Browse the ALOHA WUI.

  2. Open the Services tab.

  3. Scroll down to the csyncd service line.

    Warning

    From this point, make sure that you apply each step on both members of the cluster before procedure to the next step.

  4. Click on Stop red.

  5. Ensure the csyncd service is stopped:

    //cdn.haproxy.com/de/documentation/aloha/8-5/_assets/images/service_csyncd_stopped.png
  6. Click on genkey button.

  7. Click on getkey button.

  8. Click on Start.

Test the cluster

  1. Browse the ALOHA LB1.

  2. Open the LB Layer 7 tab.

  3. Click on push button.

    • If no message appears after a few seconds, everything is fine.

    • In case of issue, the following message may display at the bottom of the page:

      //cdn.haproxy.com/de/documentation/aloha/8-5/_assets/images/sync_error_368x18.png

Troubleshooting cluster synchronization

Check if csynd is operational

  1. Browse the ALOHA WUI.

  2. Open the Setup tab.

  3. Look for the Remote Configuration area. The current status table reports the synchronization capability of the cluster:

    • A red LED means synchronization does not work

    • An orange LED or a green LED means synchronization works

If the LED is red, run the tasks below to troubleshoot:

  • Power on both ALOHAs.

  • Check that both ALOHA WUIs listen on the same TCP port and on the same protocol scheme (HTTP or HTTPs).

  • Check that both ALOHAs can ping each other.

  • Check that csyncd service is started on both ALOHAs, i.e. a green LED in the Services tab.

  • Force a csyncd key exchange.