ArubaOS not following VRRP standard

[networkninja]

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.

[Victor Fabian]

How are the APs contacting the master controller ?

Dhcp option 43
Aruba- master / dns entry
Static
ADP

[networkninja]

Aruba- master / dns entry

[Victor Fabian]

What is the aruba-master dns entry the 10.1 or the 10.3 ?

[networkninja]

There is one dns entry

VIP-10.10.10.3 ---aruba-master

no entry for others

[Victor Fabian]

DId you just recently made that change ?

I am wondering if when you made the change the AP was already talking to the 10.1 and it would stay that way until it reboots ?

Can you also do a nslookup to make sure the aruba-master is resolving to the 10.3?

Also do a show vrrp and make sure that it is up and running. 

[networkninja]

Initially I had only one controller and it had 10.10.10.3

When i brought second controller I amde 10.10.10.3 as VIP and gave a new IP to both the controller.

This way no DNS changes. ALso I have rebooted all the APs.

DNS entry confirmed to be showing 10.10.10.3 for aruba-master

[Victor Fabian]

If you console into one of the APs can you see what is the IP is getting when it is booting up 

When it is booting up you will see the following : Master is ....<Master IP Address>

[networkninja]

I sniffed the traffic in my network and I know its trying to contact the controller on 10.10.10.3.

The problem is why is the controller replying with 10.10.10.1 source ip instead of 10.10.10.3

[Victor Fabian]

I just doing some reading and it looks like when you sniff you supposed to see the following :

That under the internet protocol drop down you will see as the source address  the actual IP assigned to the controller and then under the Virtual Router Redundancy protocol drop down you will see the VIP .

Is that what your are seeing ?