I observed this behaviour of Aruba OS while setting up a redundant master controller. As per my knowledge, when a device intiate a communication to a VIP , the source IP of reply packet should be the VIP and not the physical interface IP. Correct me if I am wrong.
For eg consider two mobilty controller operating in Master-standby mode.
Controller A--> Physical IP 10.10.10.1
Controller B--> Physical IP 10.10.10.2
Let the VIP be IP 10.10.10.3 floating between the two controllers. I have established a master-redundancy using the above vrrp.
Suppose AP are campus AP trying to contact the controller on the VIP IP 10.10.10.3. I see the reply packets from the controller A(since it is the master) with source IP 10.10.10.1.
Shouldnt the AP get confused. It sent the packet to 10.10.10.3. It receives the reply from 10.10.10.1.
I did a packet pacture in other network (cisco,juniper) to see what is the source IP of reply packet. I see when i ping vip the reply packet has source IP as VIP and not the physical interface IP.
So looks like Aruba is not following the VRRP standard.
Anybody experienced this. Correct me if I am understanding it wrong.