Native IPv6 Support

ArubaOS now provides native IPv6 support that allows enterprises to deploy pure IPv6 wireless network with Mobility Masters and managed devices. In a dual-stack deployment, even though both IPv4 and IPv6 addresses are configured on the networking devices, pure IPv6 deployment is not possible since IPv4 addresses are mandatory to communicate with the APs. In a native IPv6 deployment, all the applications and processes running on the managed devices support IPv6 addresses for seamless communication between Mobility Masters and managed devices. Native IPv6 deployment is applicable in the following scenarios between Mobility Masters and managed devices:

  • If both Mobility Master and managed device are configured in pure IPv6 deployment (without configuring IPv4 address), the AP comes up only with a valid IPv6 address on the managed device.
  • If both Mobility Master and managed device are configured in pure IPv6 deployment (with managed devices configured in dual-stack deployment but Mobility Masters configured without IPv4 address), the AP comes up on the managed device either with IPv4 or IPv6 address regardless of the cluster.

Native IPv6 deployment impacts the following components:

The mini setup dialog is not recommended in a native IPv6 deployment.

In a native IPv6 deployment, it takes around 30 minutes to initially bring up the APs running ArubaOS 8.7.1.2 or earlier images. For APs running ArubaOS 8.7.1.3 or later images, it takes around 17 minutes to initially bring up the APs. For information on setting the IP preference for an AP, see the Provisioning AP to Native IPv6 section of the ArubaOS 8.x IPv6 Deployment Guide.

Starting from ArubaOS 8.7.0.0, you can delete the controller IPv4 address at the device and group level while migrating from pure IPv4 or dual-stack deployment to native IPv6 deployment by using the no controller-ip command. The following changes are introduced as part of the no controller-ip command:

  1. You can delete the controller IPv4 address in the following scenarios:
    • When a valid controller IPv6 address is available at the same device or group level.
    • When a single IPv4 address is available on the controller.
  2. You cannot delete the controller IPv4 address when multiple IPv4 addresses are available. Hence, you must ensure that only the controller IPv4 and its interface address are the last remaining IPv4 entities to be deleted during the migration process. Depending on the scenario, one of the following errors is displayed in the CLI Command-Line Interface. A console interface with a command line shell that allows users to execute text input as commands and convert these commands to appropriate functions. when you issue the no controller-ip command:

    Controller IPv4 cannot be removed. Please configure controller-ipv6 on some other valid vlan or the loopback Controller IPv4 cannot be removed. Multiple v4 addresses exist on the controller”

  3. An attempt to delete the controller IPv4 address automatically deletes the last remaining IPv4 addresses on the corresponding VLAN Virtual Local Area Network. In computer networking, a single Layer 2 network may be partitioned to create multiple distinct broadcast domains, which are mutually isolated so that packets can only pass between them through one or more routers; such a domain is referred to as a Virtual Local Area Network, Virtual LAN, or VLAN. or loopback interface by issuing the following commands:
  4. An attempt to delete the last remaining IPv4 addresses is prevented by the validation code and displays the following error message in the CLI Command-Line Interface. A console interface with a command line shell that allows users to execute text input as commands and convert these commands to appropriate functions.:

    Controller IPv4 configured with this address. Execute <no controller-ip> command to auto-delete the interface address.

Supported Applications

ArubaOS supports native IPv6 deployment for the following applications or scenarios:

Important Point to Remember