Searching ALOHA 12.5
Creating a VRRP Active/Passive Cluster
Creating a VRRP Active/Passive Cluster
In an active/passive cluster failover configuration, one or more passive or standby nodes are available to take over for failed nodes.
Note
Be sure you run the VRRP safety check procedure before you configure VRRP.
Configuring the ALOHA Master
Configure the VRRP daemon
Browse the ALOHA WUI.
Open the Services tab.
Scroll down to VRRP service.
-
Click Setup
.
Remove the line
no autostart
if it exists.If a
group
directive exists and the required network interface is not listed, then append it.Otherwise, add a
group
directive followed by the interface name.
The configuration should look like the following:
group eth0 track_svc haproxy track_mgt sshd wui
Click OK.
Click Close. The line corresponding to the VRRP daemon now appears in orange with the flag Need restart.
Click Restart
.
Configure the VRRP instance
Browse the ALOHA WUI.
Open the Services tab.
Scroll down to the network interface you want to configure.
Click Setup
.
-
Add the following parameters to create a new VRRP instance:
vrrp inst default id 110
this ID must be unique and depends on your environment
vrrp inst default garp 30
vrrp inst default prio 101
ALOHA Master priority (Slave will be 100)
vrrp inst default address 10.0.32.20
the Virtual IP
vrrp inst default password aloha
recommended
vrrp inst default no-address
recommended
The configuration should look like the following:
service network eth0 ip address 10.0.32.11/24 ip route default 10.0.32.1 vrrp inst default id 110 vrrp inst default garp 30 vrrp inst default prio 101 vrrp inst default address 10.0.32.20 vrrp inst default password aloha vrrp inst default no-address
Click OK.
Click Close. The line corresponding to the VRRP daemon now appears in orange with the flag Need restart.
Click Restart
.
Configuring the ALOHA Slave
Configure the VRRP daemon
Browse the ALOHA WUI.
Open the Services tab.
Scroll down to VRRP service.
-
Click Setup
.
Remove the line
no autostart
if it exists.If a
group
directive exists and the required network interface is not listed, then append it.Otherwise add a
group
directive followed by the interface name.
The configuration should look like the following:
group eth0 track_svc haproxy track_mgt sshd wui
Click OK.
-
Click Close.
The line corresponding to the VRRP daemon now appears in orange with the flag Need restart.
Click Restart
.
Configure the VRRP instance
Browse the ALOHA WUI.
Open the Services tab.
Scroll down to the network interface you want to configure.
Click Setup
.
-
Add the following parameters to create a new VRRP instance:
vrrp inst default id 110
this ID must be unique and depends on your environment
vrrp inst default garp 30
vrrp inst default prio 101
ALOHA Slave priority (Master is 101)
vrrp inst default address 10.0.32.20
the Virtual IP
vrrp inst default password aloha
recommended
vrrp inst default no-address
recommended
The configuration should look like below:
service network eth0 ip address 10.0.32.11/24 ip route default 10.0.32.1 vrrp inst default id 110 vrrp inst default garp 30 vrrp inst default prio 100 vrrp inst default address 10.0.32.20 vrrp inst default password aloha vrrp inst default no-address
Click OK.
-
Click Close.
The line corresponding to the VRRP daemon now appears in orange with the flag Need restart.
Click Restart
.
Troubleshooting
Detect duplicated IPs
To troubleshoot duplicated IPs, you can use the ARP who-has diagnostic tool.
This tool checks if the MAC address associated with the IP address is the one expected or not:
If yes, the problem may be on an upper layer
If not, the MAC address of the server has the duplicated IP
Capture VRRP packets
You can use the capture diagnostic tool for this purpose.
To capture VRRP traffic, use vrrp
as <filter>
and choose an interface:
tcpdump: listening on eth0, link-type EN10MB (Ethernet), capture size 65535 bytes
14:12:27.936839 00:0c:49:65:47:0e > ... , proto VRRP (112), 10.9.104.253 > 224.0.0.18, ... , vrid 30, prio 35, ... , addrs: ...
14:12:28.250381 00:0c:59:20:c7:f6 > ... , proto VRRP (112), 10.9.104.241 > 224.0.0.18, ... , vrid 166, prio 133, ... , addrs: ...
14:12:28.460930 00:0d:b9:18:b9:74 > ... , proto VRRP (112), 10.9.104.253 > 224.0.0.18, ... , vrid 55, prio 70, ... , addrs: ...
14:12:28.939831 00:0c:49:65:47:0e > ... , proto VRRP (112), 10.9.104.253 > 224.0.0.18, ... , vrid 30, prio 35, ... , addrs: ...
14:12:28.250381 00:0c:59:20:c7:f6 > ... , proto VRRP (112), 10.9.104.241 > 224.0.0.18, ... , vrid 166, prio 133, ... , addrs: ...
5 packets captured
0 packets received by filter
0 packets dropped by kernel
Using the capture diagnostic tool, you can get the following information:
Source MAC and IP address
VRID
VRRP priority