Configure HA a/p on Thunder1040

jsanabria

Good afternoon,

I'm new in the forum. I have 2 Thunder1040-F devices with firmware 5.2.1-p3, build 70, we want to configure HA in active/passive mode, what would be the procedure to do it. and that the synchronization is done automatically from the primary to the secondary

Thank you

mdunn

Welcome! There are two pieces to configure which work hand in hand to accomplish your goals:

1. VRRP - this provides HA data plane redundancy
2. VCS - this provides automatic config sync between the devices

I have attached the guides for both of these, but they're also available on the A10 Support Portal. VRRP is configured first followed by VCS. I have also attached a couple example configs for how the final config will look. Be sure to check the configuration steps on the VCS guide.

adc-1.txt

adc-2.txt

VRRP-A_High_Availability.pdf

ACOS_Virtual_Chassis_Systems.pdf

jsanabria

Good night.

Thank you for your support, I have a concern, after having configured the interfaces, the static route, hostname, I must configure the vrrp as mentioned in the commands you sent me:

vrrp-a common

 device-id 1

 set-id 1

 enable

!

device-context 1

 vcs enable

!

device-context 2

 vcs enable

!

vcs device 1

 priority 140

 interfaces management

 enable

!

vcs device 2

 priority 100

 interfaces management

 enable

vrrp-a vrid 0

 device-context 1

  blade-parameters

   priority 150

 device-context 2

  blade-parameters

   priority 140

!

vrrp-a interface ethernet 1/4

!

vrrp-a interface ethernet 2/4

!

vrrp-a preferred-session-sync-port ethernet 1/4

!

vrrp-a preferred-session-sync-port ethernet 2/4

but in the document something called floating IP appears, it is mandatory to configure that parameter? if so how should I configure it because I don't understand that concept well

Thanks

mdunn

The floating IP's are configured under the VRRP VRID. Here is an example:

vrrp-a vrid 0 
  floating-ip 10.1.1.100 
  floating-ip 10.2.1.116 
  floating-ip 10.3.1.84 
  device-context 1
    blade-parameters
      priority 150
  device-context 2
    blade-parameters
      priority 140

Floating IP's are not required, but they can be useful for failover depending on your network routing configuration. The Active device in VRRP will advertise the floating IP's, and they can be used as next hop in routes.

jsanabria

Hello,

Thank you for the support you have given me, for some reason the configurations are not synchronizing between the 2 devices, I created a new server on one device but it was not replicated, what parameters should you review for this.

Thanks

mdunn

Sounds like VCS may not be communicating or running properly. You can check the status of VCS from the CLI with "show vcs summary". Here's an example of a functional VCS output. Did you perform a "vcs reload" after configuring vcs?

dunn-adc-2-Standby-vMaster[2/2]#sho vcs summary


VCS Chassis:
   VCS Enabled:                               Yes
   Chassis ID:                                2
   Unicast Election port:                     41217
   Multicast IP:                              224.0.0.210
   Multicast Port:                            41217
   Version:                                   5.2.1-P7.b160
   Current Discover mode:                     Multicast


Members(* means local device):
 ID  State       Priority IP:Port                                       Location
-------------------------------------------------------------------------------
 1   vBlade      140      10.22.10.56:41216                             Remote
 2   vMaster(*)  100      10.22.10.55:41216                             Local
Total: 2
dunn-adc-2-Standby-vMaster[2/2]#