@fsweetser wrote:
I'm in the very early stages of troubleshooting some wireless connectivity complaints, and before I dig in much deeper and open up a support case I wanted to see if I could quickly verify what kind of behavior I should be expected.
I have a pair of local controllers set up as an HA pair. It appears to me that when a user roams from an AP on controller A over to a controller B, no broadcast traffic is explicitly generated by the controllers. This means that the rest of the upstream network still believes that the client is hanging off of controller A, and sends it there, where it goes off into the void. This is in contrast to our old Trapeze network, where a broadcast packet of IP protocol 99 was generated whenever a client jumped controllers, keeping the rest of the network in sync.
Should I be expecting any kind of similar traffic, like a gratuitous ARP, from my Aruba controllers?
thanks!
Did you do a test like your client pinging the default gateway while it is roaming, or another wired device pinging your client while it is roaming from controller to controller to observe application performance?
IP Mobility (layer 3 mobilty) is not in effect, unless you turn it on globally and it is only used when a controller does not have a layer 2 VLAN that the client's initial controller had. If it is not configured, it is not active, even when enabled at the Virtual AP level.
Enabling VLAN mobility allows to target controller to look into its bridge table to assign the VLAN of a client that is roaming to it. If your target controller had a VLAN pool in the VAP and you have Vlan mobility enabled, the controller will assign the VLAN based on the VLAN observed in the target controller's bridge table, instead of a VLAN pool.
Again, you should do an actual test where your client is pinging a wired device when it is roaming to determine if you have an issue or not. Just the client roaming and sending traffic should update the bridge table, due to traffic leaving the controller.