03 - Alteon ADC Level 1 Lab Manual - High Availability
03 - Alteon ADC Level 1 Lab Manual - High Availability
34.x
Alteon Level 1
Lab Manual
High Availability
Table of Contents
Objectives .................................................................................................................................. 3
Overview .................................................................................................................................... 3
Overview
In this lab you will set up a redundant network for high availability (HA).
The single-switch configuration is enhanced by a second switch to provide High Availability (HA) based on
enhanced configuration on Alteon OS v30.2 (or higher). The legacy-mode high availability (VRRP) is coverd in
Alteon Level 2 training. For more information on HA, refer to Alteon Application Guide.
You'll configure HA for active Alteon (Active = A) and backup Alteon (Backup = B) devices.
High availability is maintained as follows: if the active device fails and no longer passes
traffic, the backup device takes over. This minimizes downtime on a critical network.
Management: Internet
Alteon-A: 10.10.240.11
Alteon-B: 10.10.240.12
Netmask: 255.255.248.0 SSL-VPN
Gateway: 10.10.240.254 Remote
Desktop
External Network Client
Port / If: 1
VLAN: 11
Alteon-A: 192.168.175.11
Alteon-B: 192.168.175.12 10.249.1.0 /24
Netmask: 255.255.255.0 RDP-Network
Gateway 1: 192.168.175.254
Floating IP: 192.168.175.1
MNG 1
2
10.200.1.0 /24
Server Network
WebServer1 WebServer2
10.200.1.100 10.200.1.200
Lab Activities
Here is a summary of the activities you'll perform in this High Availability Lab:
• Verify and configure (active) Alteon A:
o Verify Switching & Configure Routing Basic Setup
o Add interface peer IPs
• Configure (backup) Alteon B:
o Verify Management IP on Device B
o Configure Switching & Routing Minimal Setup
• Configure High Availability on A
o Enable HA Switch Mode
o Select advertisement interfaces
o (Opt) Configure Session Mirroring
o (Opt) Configure Failover Trigger
• Configure Synchronization for A to B
2. Verify the creation of two VLANs on Active Alteon (Device A); add ports.
Verify L2 VLANs
1 11
2 14
GUI:
b. Configuration → Network → Layer 3 → Gateways
c. Double click on gateway 1 to verify.
6. Check configuration.
CLI:
cc
GUI:
Click “Dump”
2. Lengthen Alteon idle timeout to 9999 minutes so the device does not idle out.
Go to Configuration → System → Management Access
7. Set VLAN 11 to port 1 and VLAN 14 to port 2, disable all other VLANs
Go to Configuration → Network → Layer 2 → VLAN
9. Define Layer 3 (L3) IP interfaces. For sync we use the Server Network.
IF ID 2, IP Address 10.200.1.12 /24, VLAN 14 and Peer IP 10.200.1.11
Local Go to Configuration → Network → Layer 3 → IP Interfaces
Apply changes
GUI:
Click “Dump”
a. Use Peer ID = 1
b. Use Peer IP address = 10.200.1.12
IP Address is for the peer Alteon. Only data ports --not management IP -- are valid for sync.
Any interface IP would work BUT of Radware Lab, use the IP address for IF 2 from Backup B.
GUI:
1. Setup Configuration Sync.
For communication set Peer IP 10.200.1.12
Go to Configuration → Network → High Availability → Configuration Sync
a. Select Peers and press + button.
b. Enable Peers
c. Peer ID set 1
d. IP Address 10.200.1.12
e. Submit changes
f. Select Modules to Sync
g. Remove all and add selection for IP Interfaces, Port, Gateways, PIP, Certificates
h. Certifcate and Authentication passphrase we set to radware1 In real world use a stronger
password.
i. Submit, Apply and Save changes
Click Sync button on top. After a couple of seconds check on Alteon-B the interface and default gateway
configuration. Is now interface 1 and 2 as well gw1 available? Config at Alteon-B is applied and saved by
synchronization.
If you like sync config by only applying a new config turn on automatic sync at Modules to Sync menu.
We recommend doing it.
Alteon-A: Configuration → Network → High Availability → Configuration Sync
a. Select Modules to Sync
b. Check Automatic Sync
c. Click Submit and Apply and Save
1 192.168.175.1
2 10.200.1.254
GUI:
GUI:
GUI:
Continuous ping on RDP client fails for 1 or 2 requests and is continued on new master again.
Continuous ping on RDP client fails for 1 or 2 requests and is continued on new master again.
© 2024 Radware Ltd. All rights reserved. The Radware products and solutions mentioned in this document
are protected by trademarks, patents and pending patent applications of Radware in the U.S. and other
countries. For more details, please see: https://www.radware.com/LegalNotice/. All other trademarks and
names are property of their respective owners.