We are deploying HA database cluster on exsi which based on virtual IP concept for failover. if One node fail reserved VIP will be assigned to another node
we have two exsi nodes and two virtual machines on those exsi nodes as master and slave.
db_master = 192.168.60.10 db_slsave = 192.168.60.11 reserved_vip = 192.168.60.12 gateway = 192.168.60.1
each exsi node have two interfaces. NIC teaming configured with IP hash-based routing with the of LAG configured on the switch side ( NO LACP).
LAG configured as a trunk port and I terminate VLANs inside the exsi port groups
All of my database servers are on vlan 60 and those are the only VM on the exsi at the moment
I configured virtual port group and assign vlan 60. and network up and running. I can ping other nodes outside my setup and LAG working fine when I remove one cable.
the issue comes with database failover. For normal scenario VIP 192.168.60.12 assigned to db_master. when I switched off db_master VIP will be assigned to db_slave.
The failover software feature is working perfectly fine but when virtual ip (192.168.60.12) assigned to db_slave I cannot ping it anymore from the gateway.
it seems this is arp issue. but I would like to confirm that exsi IP hash-based routing and lag not playing wrong here by effecting the failover.
moreover, I did not check this with application level but only with ICMP