Legal Disclaimer: The resource assets in this website may include abbreviated and/or legacy terminology for HPE Aruba Networking products. See www.arubanetworks.com for current and complete HPE Aruba Networking product lines and names.
Migrating APs to AOS-10
Prerequisites
Before you migrate an AP to AOS-10, ensure that the following conditions are met:
- Ensure that the AP models to be migrated are supported in AOS-10. For more information on AOS-10 supported platforms, see Supported Devices for AOS-10
- Ensure that the devices are enrolled and have a valid subscription.
- Ensure that the devices can resolve all applicable FQDNs and reach those targets on required ports.
- Ensure that the APs are running in IPv4 or dual stack mode. The native IPv6 on APs is not supported.
- Ensure that the Instant APs (IAP)s are running AOS 8.7.1.0 or later versions for a successful firmware upgrade.
- Ensure that the IAP clusters do not contain any AP models that are not supported by AOS-10.
- For IAP clusters with a mix of AP-615 and AP-635 access points having different factory images, disable the Auto-Join Mode option in the default group and set the firmware to a minimum version supported by all AP models.
- Ensure that the uplink native 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. is not configured on the IAPs.
- Ensure that the associated gateway is running AOS 8.7.1.9, AOS 8.10.0.5, or later versions to convert Campus APs Campus APs are used in private networks where APs connect over private links (LAN, WLAN, WAN or MPLS) and terminate directly on controllers. Campus APs are deployed as part of the indoor campus solution in enterprise office buildings, warehouses, hospitals, universities, and so on. (CAP)s to AOS-10.
-
Ensure that VLAN 3333 is not assigned to clients. The magic VLAN 3333 feature is not available in AOS 10. VLAN 3333 is used only for the guest users which are in logon or logout role when they try to access the Captive Portal A captive portal is a web page that allows the users to authenticate and sign in before connecting to a public-access network. Captive portals are typically used by business centers, airports, hotel lobbies, coffee shops, and other venues that offer free Wi-Fi hotspots for the guest users. page.
- IAP currently does not support migration for the following scenarios: Wi-Fi Wi-Fi is a technology that allows electronic devices to connect to a WLAN network, mainly using the 2.4 GHz and 5 GHz radio bands. Wi-Fi can apply to products that use any 802.11 standard. uplink, cellular uplink, and hierarchy mode.
- The HPE Aruba Networking 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 HPE Aruba Networking Central template.
- The direct migration of APs running AOS/Aruba Instant 6.x to HPE Aruba Networking Wireless Operating System 10 is currently not supported. Instead, migrate the APs running AOS/Aruba Instant 6.x to AOS /Aruba Instant 8.7.1.0 and then follow the steps in this section to migrate the APs running AOS/Aruba Instant 8.7.1.0 to HPE Aruba Networking Wireless Operating System 10.
Migration to AOS-10 involves the following scenarios:
- Converting HPE Aruba Networking Central Managed IAPs to AOS-10
- Converting Locally Managed IAPs to AOS-10
- Converting Campus APs to AOS-10
Converting HPE Aruba Networking Central Managed IAPs to AOS-10
To migrate HPE Aruba Networking Central managed IAPs running AOS 8.7.1.0 or later versions to HPE Aruba Networking Wireless Operating System 10 version, complete the following steps:
- In the WebUI, set the filter to Global.
The dashboard context for the selected filter is displayed.
- Under Maintain, click Organization.
By default, the Network Structure tab is displayed.
- In the Network Structure page, click the Groups tile.
The Groups page is displayed.
- In the Groups table, select an AP group running AOS 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.
- 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.
-
In the Move Devices page, select an HPE Aruba Networking Wireless Operating System 10 destination group from the Destination Group drop-down list.
- 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.
HPE Aruba Networking Central upgrades the APs to HPE Aruba Networking Wireless Operating System 10 version. The APs boots up in AOS-10 mode and reconnects with HPE Aruba Networking Central using the HPE Aruba Networking Wireless Operating System 10 version. HPE Aruba Networking Central performs configuration audit and forwards the HPE Aruba Networking Wireless Operating System 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 Domain Name System. A DNS server functions as a phone book for the intranet and Internet users. It converts human-readable computer host names into IP addresses and IP addresses into host names. It stores several records for a domain name such as an address 'A' record, name server (NS), and mail exchanger (MX) records. The Address 'A' record is the most important record that is stored in a DNS server, because it provides the required IP address for a network peripheral or element., and domain name
- uplink-vlan
- ap1x-peap-user and password
- lacp-mode
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 AOS-10
To migrate locally managed IAPs running AOS 8.7.1.0 or later versions to HPE Aruba Networking Wireless Operating System 10 version, complete the following steps:
- In the WebUI, set the filter to Global.
The dashboard context for the selected filter is displayed.
- Under Maintain, click Organization.
By default, the Network Structure tab is displayed.
- In the Network Structure page, click the Groups tile.
The Groups page is displayed.
- In the Groups table, expand the Unprovisioned devices accordion.
- 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.
-
In the Move Devices page, select an AOS-10 destination group from the Destination Group drop-down list.
- 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.
HPE Aruba Networking Central upgrades the APs to HPE Aruba Networking Wireless Operating System 10 version. The APs boots up in AOS-10 mode and reconnects with HPE Aruba Networking Central using the HPE Aruba Networking Wireless Operating System 10 version. HPE Aruba Networking Central performs configuration audit and forwards the HPE Aruba Networking Wireless Operating System 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 AOS-10
When a Campus AP is migrated to AOS-10, you must ensure that the AP is able to reach the cloud. You can convert a Campus AP running AOS 8.7.1.0 or later versions to HPE Aruba Networking Wireless Operating System 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 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.
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 AOS 8.7.1.0 or later versions to HPE Aruba Networking Wireless Operating System 10 version, complete the following steps:
-
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.
- Pre-validate the Campus APs to the conversion list by executing the ap convert pre-validate specific-aps CLI command.
- 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 HPE Aruba Networking Central Group will be available.
- Download the AOS-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.
- Issue the managed device to initiate upgrade of Campus AP to AOS-10 AP. The managed device obtains the AOS-10 AP image, and notifies the APs to download it. Apart from mesh and Wi-Fi uplink, the remaining uplink parameters are saved in parameter in Campus AP. When the AP boots up with AOS-10 image, the uplink parameters saved before in are read and configured temporarily. This is to ensure that the AP boots up and connects to HPE Aruba Networking Central to access the new configuration successfully. command on the
- Issue the AOS-10 AP. For the parameters that are not supported in AOS-10 AP, the uplink parameters in are cleared when AP makes configuration changes and the current uplink configuration is disabled. Once the Campus AP converts to AOS-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. command to remove the uplink parameters that are supported in
-
Verify the conversion status by executing the show ap convert-status CLI command.
The controller upgrades the APs to AOS-10. The APs boots up in AOS-10 mode and receives provisioning rule to connect to HPE Aruba Networking Central from Activate, and then connect to HPE Aruba Networking Central where the AP is placed in the assigned group. HPE Aruba Networking Central performs configuration audit and forwards the AOS-10 configurations from the new AP group by removing most of the configurations and retaining only the following uplink parameters:
- DHCP Dynamic Host Configuration Protocol. A network protocol that enables a server to automatically assign an IP address to an IP-enabled device from a defined range of numbers configured for a given network. /IPv4
- Static/IPv4
- Dual Eth
- PPPoE Point-to-Point Protocol over Ethernet. PPPoE is a method of connecting to the Internet, typically used with DSL services, where the client connects to the DSL modem.
- AP1X
- Proxy
- LACP Link Aggregation Control Protocol. LACP is used for the collective handling of multiple physical ports that can be seen as a single channel for network traffic purposes.
- Mesh
The HPE Aruba Networking 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 HPE Aruba Networking Central template.
The preferred uplink port is configured using the
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 CLI command.The following is the syntax for configuring the preferred uplink:
Ethernet Ethernet is a network protocol for data transmission over LAN. port and 1 is the fiber port.
, where 0 is theThe following example displays the configuration of Eth01 port as the preferred uplink:
The
CLI command displays the status of preferred uplink configuration:The following table provides a list of various Ethernet uplink parameters in the Campus AP to AOS-10 AP:
command that are configured to migrate
Uplink Type |
Campus AP Parameter |
AOS-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 When PPPoE uplink is not configured, the AP removes the uplink parameters by issuing the command. |
AP1X |
ap1xuser, ap1xpasswd |
ap1xuser, ap1xpasswd When AOS-10 AP boots up, it automatically enables parameter. This is to ensure that AP1X uplink connects to HPE Aruba Networking Central to obtain the required configuration. |
To convert APs using local-flash option, upload the images in flash before executing the following CLI commands:
To convert APs using image servers, execute one of the following CLI commands depending on the mode:
To add specific AP groups or AP names to convert, execute the following CLI commands:
To remove specific AP groups or AP names from list of conversion, execute the following CLI command:
To clear all the APs from the list of conversion, execute the following CLI command:
To abort the conversion of APs, execute the following CLI command: