Note that both Barracuda WAF Control Centers in HA must be the same model and on the same firmware.
Scenario 1. Replace the Secondary Instance in a High Availability Environment
Remove the secondary instance from the AWS Classic Load Balancer.
- Disjoin the secondary instance from the cluster. Perform the following steps to disjoin:
- On the Secondary instance, go to the ADVANCED > High Availability page.
- Click the Delete icon available on the Clustered Systems table.
Once the new instance is installed, perform the following steps:
Go to the ADVANCED > High Availability page and configure all attributes in the exact same manner as those on the primary instance. The Cluster Shared Secret must match.
- In the Clustered Systems section, enter the system IP address of the primary instance and click Join Cluster.
- Add the new instance to the AWS Classic Load Balancer.
Scenario 2. Replace the Primary instance in a High Availability Environment
Remove the primary instance from the AWS Classic Load Balancer.
- Disjoin the primary instance from the cluster. Perform the following steps to disjoin:
- On the primary instance, go to the ADVANCED > High Availability page.
- Click the Delete icon available on the Clustered Systems table.
Once the new instance is installed, perform the following steps:
Go to the ADVANCED > High Availability page and configure all attributes in the exact same manner as those on the peer instance. The Cluster Shared Secret must match.
- In the Clustered Systems section, enter the system IP address of the peer instance and click Join Cluster.
- Add the new instance to the AWS Classic Load Balancer.