Configuration Retained or Migrated

When an AP is loaded with AOS 10 and checks in with Central for the first time, some of the previous configuration is retained on the AP, and a subset of that configuration can be migrated into the configuration for the AP stored in Central. Some of this retained configuration will allow the AP to operate properly on the network. Some settings can cause failures or interruptions.

Potential migration impactful configuration

This is the list of configuration settings, either at the AP or AP Group/Virtual Controller level, that can impact connectivity of the AP to the local network and/or Central when the AOS 8 AP is upgraded to AOS 10.

• DHCP

  • No changes, default configuration.

• Static IP Address

  • Campus: Migrated into the device-level AP configuration in Central.

  • Microbranch: Not supported.

• Native VLAN

  • Native VLAN configuration is not retained on the AP and not migrated to Central. The AP will always assume VID 1 for the native VLAN on the uplink.

• Management VLAN

  • Management VLAN configuration is not retained on the AP and not migrated to Central. The AP will always assume the management interface is VID 1.

• LACP

  • Non-default LACP configuration is retained on the AP and migrated into the device level AP configuration.

• AP1X

  • AP1X configuration is retained on the AP but not migrated into the configuration on Central.

  • Mismatch of configuration can result in AP flapping when synchronized with Central and potentially revert configuration due to loss of connectivity and enact auto-restore.

• HTTP Proxy

  • HTTP proxy configuration is retained on the AP but not migrated into the configuration on Central.

  • Mismatch of configuration can result in AP flapping when synchronized with Central and potentially revert configuration due to loss of connectivity and enact auto-restore.

• PPPoE

  • Nothing is retained or migrated into Central.

• Mesh

  • The existing mesh profile will be retained on the AP for the purpose of allowing reconnection to a mesh network.

Configuration required to maintain or restore connectivity

In some situations the upgrade will cause the AP to operate in a partially functional state, with the local configuration continuing to provide connectivity but the pushed Central configuration causing connectivity interruptions. Automatic restoration of the last configuration state should return the AP to a functional state until the configuration is synchronized once again from Central, resulting in the AP state appearing to flap.

• Static IP Address

  • Microbranch: only DHCP is currently supported for IP assignment. Design the deployment around this requirement.

• Native and Management VLAN

  • Configure the AP and/or network so that an untagged VLAN is provided to the AP for management.

  • Deployments that require bridging of VLANs through the AP must postpone upgrading to AOS 10 or account for the potential VID mismatch between AP and switched networks.

• LACP

  • The default LACP state on the AP in AOS 10 is enabled as “Passive”. Best practice is to use this option and configure “Active” only on the switch ports.

• AP1X

  • Before upgrading the AP and placing the device in a Central group, configure the AP settings within the target Central AP group with the appropriate AP1X settings to maintain operation.

• HTTP Proxy

  • Before upgrading the AP and placing the device in a Central group, configure the AP settings within the target Central AP group with the appropriate HTTP Proxy settings to maintain operation.

• PPPoE

  • The AP must be connected to a network that provides a DHCP IP assignment and can be configured with PPPoE settings for the end installation location.

• Mesh

  • Before upgrading the AP and placing the device in a Central group, configure the AP settings within the target Central AP group with the appropriate mesh settings to maintain operation.