How is IPv6 L3 mobility concept implemented in Aruba ?

Aruba Employee
Aruba Employee

This article applies to Aruba Mobility Controllers running ArubaOS version


ArubaOS supports IPv6 L3 Mobility functionality. The existing L3 mobility solution has been enhanced to support dual stacked (IPv4 and IPv6) and pure IPv6 mobile clients. This allows wireless clients to retain their IPv4/IPv6 addresses on a wireless roam across different VLAN’s within a controller and between controllers. 

The IPv6 L3 mobility concept on Aruba controller is aided by the following enhancements :

  • L2 GRE tunnels between controllers in mobility group once they boots up

  • Router Advertisement Proxy which proxies Router Advertisements (RAs) 

The Controller consume RA from upstream routers and maintain a repository of prefix information and both the solicited RAs and the unsolicited periodic RAs will be converted to L2 unicast and sent to the wireless clients.

  • MLD proxy to support mobility for IPv6 multicast traffic

Multicast mobility ensures a client gets an uninterrupted multicast stream while roaming with support for MLD versions v1 and v2.

  • HA discovery on station association

The HA discovery on association parameter is turned on by default and is not configurable.

Functional Description





  • IPv6/Ipv4  client joins the controller first time HA discovery will be triggered automatically to validate if any of the controller in the mobility group already own this client. 

  • A new bridge entry will be created for the client as it is a fresh association. 

  • Once client send a RS packet, controller will buffer the RA response from router and client will get a unicast RA response from controller. 

  • After client successfully roam to the neighbor controller, HA discovery will be triggered and first controller will claim the ownership of the client. 

  • As the tunnels are already up all the traffic from the particular client tunneled through the HA including DHCP. Authentication packets will be only exception for this. 

  • An additional bridge entry will be created for the client after roaming. 



Version history
Revision #:
1 of 1
Last update:
‎07-01-2014 04:35 AM
Updated by:
Labels (1)