Migrating APs to ArubaOS 10

You can migrate access points (APs) to ArubaOS 10.3.1.0 or later versions.

Prerequisites

Before you migrate an AP to ArubaOS 10, ensure that the following conditions are met:

Migration to ArubaOS 10 involves the following scenarios:

Converting Aruba Central Managed IAPs to ArubaOS 10

To migrate Aruba Central managed IAPs running ArubaOS 8.7.1.0 or later versions to ArubaOS 10 version, complete the following steps:

  1. In the Aruba Central app, set the filter to Global.

    The dashboard context for the selected filter is displayed.

  2. Under Maintain, click Organization.

    By default, the Network Structure tab is displayed.

  3. In the Network Structure page, click the Groups tile.

    The Groups page is displayed.

  4. In the Groups table, select an AP group running ArubaOS 8.7.1.0 or later versions by expanding the group accordion from the Group Name column. Optionally, the icon allows you to filter an AP group from the Group Name column.
  5. Select the Virtual Controller (VC) and the APs you wish to migrate to the destination group and then click the Move Devices icon.

    The Move Devices page is displayed.

    When you migrate an IAP acting as VC, then the member APs also migrate to the new group.

  6. In the Move Devices page, select an ArubaOS 10 destination group from the Destination Group drop-down list.

  7. Click Move.

    The selected devices are moved to the destination group. These devices will adopt the configuration of the destination group.

    You must ensure that the firmware compliance is enabled in the destination group.

Aruba Central upgrades the APs to ArubaOS 10 version. The APs boots up in ArubaOS 10 mode and reconnects with Aruba Central using the ArubaOS 10 version. Aruba Central performs configuration audit and forwards the ArubaOS 10 configurations from the new AP group by removing most of the configurations and retaining only the following uplink configurations:

This feature is not supported on 320 Series AP models with 256 MB of SDRAM, manufactured between August 2015 and January 2016. These 320 Series AP models have a serial number that begins with DD (for example, DD0003824).

For more information on the various uplink configurations, see AP Uplinks.

Converting Locally Managed IAPs to ArubaOS 10

To migrate locally managed IAPs running ArubaOS 8.7.1.0 or later versions to ArubaOS 10 version, complete the following steps:

  1. In the Aruba Central app, set the filter to Global.

    The dashboard context for the selected filter is displayed.

  2. Under Maintain, click Organization.

    By default, the Network Structure tab is displayed.

  3. In the Network Structure page, click the Groups tile.

    The Groups page is displayed.

  4. In the Groups table, expand the Unprovisioned devices accordion.
  5. Select the cluster and the APs you wish to migrate to the destination group and then click the Move Devices icon.

    The Move Devices page is displayed.

    When you migrate an VC, then the member IAPs also migrate to the new group.

  6. In the Move Devices page, select an ArubaOS 10 destination group from the Destination Group drop-down list.

  7. Click Move.

    The selected devices are moved to the destination group. These devices will adopt the configuration of the destination group.

    You must ensure that the firmware compliance is enabled in the destination group.

Aruba Central upgrades the APs to ArubaOS 10 version. The APs boots up in ArubaOS 10 mode and reconnects with Aruba Central using the ArubaOS 10 version. Aruba Central performs configuration audit and forwards the ArubaOS 10 configurations from the new AP group by removing most of the configurations and retaining only the following uplink configurations:

  • Running configuration parameters:
    • ap1x uplink configuration (ap1x peap, and ap1x tls)
    • proxy server
    • mesh-cluster
    • all configurations in the pppoe-uplink-profile, wired-port-profile, enet0-port-profile, and enet1-port-profile
  • Per-AP env parameters:
    • static IPv4 address, static IPv6 address, netmask, gateway, DNS, and domain name
    • uplink-vlan
    • ap1x-peap-user and password
    • lacp-mode

For more information on the various uplink configurations, see AP Uplinks.

Converting Campus APs to ArubaOS 10

When a Campus AP is migrated to ArubaOS 10, you must ensure that the AP is able to reach the cloud. You can convert a Campus AP running ArubaOS 8.7.1.0 or later versions to ArubaOS 10 version using the ap convert command. You can convert the AP using local-flash or local image server options like ftp, tftp, http, https, or scp by copying the downloaded image from Aruba support to the local ftp/tftp/scp server. From that server, the managed device downloads the image to its ftp or tftp folder and then distributes the ftp or tftp URLs Uniform Resource Locator. URL is a global address used for locating web resources on the Internet. to Campus APs. For more information on ap convert CLI command, see ap convert.

The uplink configuration between the different AP deployment modes must be aligned so that appropriate configuration parameters are chosen. This is to enable the AP to have a working uplink. In particular, the following uplink parameters must be configured for Campus AP migration:

  • Static IP settings of uplink port
  • AP1X settings on Eth01 uplink
  • Cellular uplink parameters

To migrate Campus APs running ArubaOS 8.7.1.0 or later versions to ArubaOS 10 version, complete the following steps:

  1. Add Campus APs to the conversion list either specifying the AP group executing the ap convert add ap-group <group-name> CLI command or the individual Campus APs by executing the ap convert add ap-name <ap-name> CLI command.

  2. Pre-validate the Campus APs to the conversion list by executing the ap convert pre-validate specific-aps CLI command.
  3. Verify the conversion pre-validation status by executing the show ap convert-status CLI command. When the pre-validation is successful, then the Upgrade Status should read Pre Validate Success and the assigned Aruba Central Group will be available.
  4. Download the ArubaOS 10 firmware files for the AP models to be upgraded. The firmware images can either be specified individually by AP type or a TAR file.
  5. Issue the ap convert active all-aps server ftp/http/https/scp/tftp command on the managed device to initiate upgrade of Campus AP to ArubaOS 10 AP. The managed device obtains the ArubaOS 10 AP image, and notifies the APs to download it. Apart from mesh and Wi-Fi uplink, the remaining uplink parameters are saved in ap-env parameter in Campus AP. When the AP boots up with ArubaOS 10 image, the uplink parameters saved before in ap-env are read and configured temporarily. This is to ensure that the AP boots up and connects to Aruba Central to access the new configuration successfully.
  6. Issue the no ap-env command to remove the uplink parameters that are supported in ArubaOS 10 AP. For the parameters that are not supported in ArubaOS 10 AP, the uplink parameters in ap-env are cleared when AP makes configuration changes and the current uplink configuration is disabled. Once the Campus AP converts to ArubaOS 10, there should not be any existing AP configurations but the AP should use Campus AP parameters. Hence, AP should recognize these Campus AP parameters and connect to the cloud. Once the APs are managed by cloud, they are provisioned with new parameters and the older Campus AP parameters are removed.

  7. Verify the conversion status by executing the show ap convert-status CLI command.

The controller upgrades the APs to ArubaOS 10. The APs boots up in ArubaOS 10 mode and receives provisioning rule to connect to Aruba Central from Activate, and then connect to Aruba Central where the AP is placed in the assigned group. Aruba Central performs configuration audit and forwards the ArubaOS 10 configurations from the new AP group by removing most of the configurations and retaining only the following uplink parameters:

The Aruba Central WebUI currently does not support the following per-AP env parameters: uplink-vlan, enet0-bridge, ap1x-peap-user and password, and IPv6 address. To perform migration in these scenarios, you must use Aruba Central template.

The preferred uplink port is configured using the preferred-uplink CLI command. The preferred uplink command is a per-AP setting and can only be configured manually on the AP through the CLI. The preferred uplink configuration can be viewed using the show ap-env CLI command.

The following is the syntax for configuring the preferred uplink:

preferred-uplink <0,1>, where 0 is the Ethernet Ethernet is a network protocol for data transmission over LAN. port and 1 is the fiber port.

The following example displays the configuration of Eth01 port as the preferred uplink:

(host)# preferred-uplink 1

The show ap-env CLI command displays the status of preferred uplink configuration:

(host)# show ap-env Antenna Type: Internal Need usb field:No uap_controller_less:1 preferred_uplink:eth1

The following table provides a list of various Ethernet uplink parameters in the ap-env command that are configured to migrate Campus AP to ArubaOS 10 AP:

Table 1: Uplink Parameters to Migrate Campus AP to ArubaOS 10 AP

Uplink Type

Campus AP Parameter

ArubaOS 10 AP Parameter

Static IP

IPv4 address—ipaddr, netmask, gatewayip, dnsip

IPv6 address—ip6addr, ip6prefix, gatewayip6, dnsip6

IPv4 address—ipaddr, netmask, gatewayip, dnsip

IPv6 address—ip6addr, ip6prefix, gatewayip6, dnsip6

PPPoE

pppoe_user pppoe_passwd pppoe_service_name pppoe_chap_secret

pppoe_user pppoe_passwd pppoe_service_name pppoe_chap_secret

NOTE: When PPPoE uplink is not configured, the AP removes the uplink parameters by issuing the no ap-env command.

AP1X

ap1xuser, ap1xpasswd

ap1xuser, ap1xpasswd

NOTE: When ArubaOS 10 AP boots up, it automatically enables ap1x peap parameter. This is to ensure that AP1X uplink connects to Aruba Central to obtain the required configuration.

To convert APs using local-flash option, upload the images in flash before executing the following CLI commands:

(host) [mynode] #ap convert active specific-aps local-flash <images> (host) [mynode] #ap convert active all-aps local-flash <images>

To convert APs using image servers, execute one of the following CLI commands depending on the mode:

(host) [mynode] #ap convert all-aps server ftp: <ftphost> <user> <images > (host) [mynode] #ap convert specific-aps server ftp: <ftphost> <user> <images> (host) [mynode] #ap convert all-aps server scp: <scphost> <user> <images > (host) [mynode] #ap convert specific-aps server scp: <scphost> <user> <images> (host) [mynode] #ap convert all-aps server tftp: <tftphost> <images > (host) [mynode] #ap convert specific-aps server tftp: <tftphost> <images>

To add specific AP groups or AP names to convert, execute the following CLI commands:

(host) [mynode] #ap convert add ap-group <ap-group> (host) [mynode] #ap convert add ap-name <ap-name>

To remove specific AP groups or AP names from list of conversion, execute the following CLI command:

(host) [mynode] #ap convert delete ap-group <ap-group> (host) [mynode] #ap convert delete ap-name <ap-name>

To clear all the APs from the list of conversion, execute the following CLI command:

(host) [mynode] #ap convert clear-all

To abort the conversion of APs, execute the following CLI command:

(host) [mynode] #ap convert cancel