Cisco Mobility Express Deployment
Introduction
This document outlines the deployment of Cisco Mobility Express, covering prerequisites, network connection, and the conversion of access points between CAPWAP and Mobility Express images.
Prerequisites for Mobility Express Solution Deployment
- Ensure that no other Cisco wireless LAN controllers (appliance or virtual) exist on the same network. Mobility Express controllers cannot interoperate or coexist with other wireless LAN controllers on the same network.
- Identify the first access point to be configured as the master access point. This access point must support the wireless LAN controller functionality.
- A DHCP server must be available on the network to allow access points and clients to obtain IP addresses. For AireOS Release 8.3.102.0 and later, a DHCP server can also be configured on the master access point, primarily for site surveys.
Connecting Mobility Express Capable Access Points to the Network
Depending on the deployment, Mobility Express capable access points can be connected to a switch's access port or a trunk port.
If the access points and WLANs are on the same network, Mobility Express capable access points can be connected to a switch's access port as follows:
Mobility Express management traffic is untagged. If access points and WLANs are on different VLANs, Mobility Express capable access points connect to a switch's trunk port, and traffic for individual WLANs is switched locally on individual VLANs. The following illustrates a deployment using access points and WLANs on different VLANs:
Diagram Description: A network diagram shows an Internet connection leading to a router, which then connects to a switch. The switch has three access points connected to it, labeled 'v10'. Each access point is connected to a user icon representing 'Contractor', 'Guest', and 'Employee'. The diagram indicates 'VLAN 10' associated with the connection to the access points.
Switch Configuration Example:
interface GigabitEthernet1/0/37 description » Connected to Master AP <<<< switchport trunk native vlan 40 switchport trunk allowed vlan 10,20,30,40 switchport mode trunk
Determining the Access Point Image
Cisco Aironet® 1540, 1560, 1815, 1830, 1850, 2800, and 3800 series access points support either the CAPWAP image or the Cisco Mobility Express image, which enables the virtual wireless LAN controller functionality.
To determine the access point's image and functionality, follow these steps:
Procedure
Step 1: Log in to the access point's CLI using a console connection and enter the command AP#show version. Review the complete output of the show version command. The default login credentials are Username: cisco and Password: cisco.
Scenario 1: If the show version output displays 'AP Image Type: MOBILITY EXPRESS IMAGE' and 'AP Configuration: NOT MOBILITY EXPRESS CAPABLE', it means the access point has the Mobility Express image but is configured to run as a CAPWAP access point. To enable the controller functionality, the AP Configuration needs to be changed. Execute the following command in the AP CLI:
AP#ap-type mobility-express
The access point will reboot and then run with controller functionality. Verify the output of show version again to confirm that 'AP Configuration' has been changed to 'MOBILITY EXPRESS CAPABLE'.
Scenario 2: If the show version output displays 'AP Image Type: MOBILITY EXPRESS IMAGE' and 'AP Configuration: MOBILITY EXPRESS CAPABLE', it signifies that the access point has the Mobility Express image and can run with controller functionality. The output will appear as follows:
cisco AIR-AP38021-B-K9 ARMv7 Processor rev 1 (v71) with 1028384/255032K bytes of memory. Processor board ID FCW2034NXAV AP Running Image : 8.4.2.66 Primary Boot Image : 8.4.2.66 Backup Boot Image : 8.4.2.34 AP Image type: MOBILITY EXPRESS IMAGE AP Configuration : MOBILITY EXPRESS CAPABLE 1 Multigigabit Ethernet interfaces 1 Gigabit Ethernet interfaces 2 802.11 Radios Radio Driver version : 9.0.5.5-W8964
Scenario 3: If the show version output does not display the AP image type and AP configuration parameters as highlighted, the AP is running a CAPWAP image. This indicates that the access point needs to be converted to Cisco Mobility Express to run the controller functionality. Refer to the conversion section of this document.
Example output for Scenario 3:
cisco AIR-AP1852E-UXK9 ARMv7 Processor rev 0 (v71) with 997184/525160K bytes of memory. Processor board ID RFDP2BCR021 AP Running Image : 8.2.100.0 Primary Boot Image: 8.2.100.0 Backup Boot Image : 8.1.106.33 AP Image type: MOBILITY EXPRESS IMAGE AP Configuration : MOBILITY EXPRESS CAPABLE 0 Gigabit Ethernet interfaces 0 802.11 Radios Radio FW version : 1401b63d12113073a3C08aa67f0c039c0 NSS FW version : NSS.AK.1.0.c4-02026-E_cust C-1.24160
Scenario 4: If the show version output displays 'AP Image Type: MOBILITY EXPRESS IMAGE' and 'AP Configuration: NOT MOBILITY EXPRESS CAPABLE', it means the access point has the Mobility Express image but is configured to run as a CAPWAP access point. To enable the controller functionality, the AP Configuration needs to be changed. Execute the following command in the AP CLI:
AP#ap-type mobility-express
The access point will reboot and then run with controller functionality. Verify the output of show version again to confirm that 'AP Configuration' has been changed to 'MOBILITY EXPRESS CAPABLE'.
Scenario 5: If the show version output displays 'AP Image Type: MOBILITY EXPRESS IMAGE' and 'AP Configuration: MOBILITY EXPRESS CAPABLE', it signifies that the access point has the Mobility Express image and can run with controller functionality. The output will appear as follows:
cisco AIR-AP38021-B-K9 ARMv7 Processor rev 1 (v71) with 1028384/255032K bytes of memory. Processor board ID FCW2034NXAV AP Running Image : 8.4.2.66 Primary Boot Image : 8.4.2.66 Backup Boot Image : 8.4.2.34 AP Image type: MOBILITY EXPRESS IMAGE AP Configuration : MOBILITY EXPRESS CAPABLE 1 Multigigabit Ethernet interfaces 1 Gigabit Ethernet interfaces 2 802.11 Radios Radio Driver version : 9.0.5.5-W8964
Scenario 6: If the show version output does not display the AP image type and AP configuration parameters as highlighted, the AP is running a CAPWAP image. This indicates that the access point needs to be converted to Cisco Mobility Express to run the controller functionality. Refer to the conversion section of this document.
Example output for Scenario 6:
cisco AIR-AP1852E-UXK9 ARMv7 Processor rev 0 (v71) with 997184/525160K bytes of memory. Processor board ID RFDP2BCR021 AP Running Image : 8.2.100.0 Primary Boot Image: 8.2.100.0 Backup Boot Image : 8.1.106.33 AP Image type: MOBILITY EXPRESS IMAGE AP Configuration : MOBILITY EXPRESS CAPABLE 0 Gigabit Ethernet interfaces 0 802.11 Radios Radio FW version : 1401b63d12113073a3C08aa67f0c039c0 NSS FW version : NSS.AK.1.0.c4-02026-E_cust C-1.24160
Scenario 7: If the show version output displays 'AP Image Type: MOBILITY EXPRESS IMAGE' and 'AP Configuration: NOT MOBILITY EXPRESS CAPABLE', it means the access point has the Mobility Express image but is configured to run as a CAPWAP access point. To enable the controller functionality, the AP Configuration needs to be changed. Execute the following command in the AP CLI:
AP#ap-type mobility-express
The access point will reboot and then run with controller functionality. Verify the output of show version again to confirm that 'AP Configuration' has been changed to 'MOBILITY EXPRESS CAPABLE'.
Scenario 8: If the show version output displays 'AP Image Type: MOBILITY EXPRESS IMAGE' and 'AP Configuration: MOBILITY EXPRESS CAPABLE', it signifies that the access point has the Mobility Express image and can run with controller functionality. The output will appear as follows:
cisco AIR-AP38021-B-K9 ARMv7 Processor rev 1 (v71) with 1028384/255032K bytes of memory. Processor board ID FCW2034NXAV AP Running Image : 8.4.2.66 Primary Boot Image : 8.4.2.66 Backup Boot Image : 8.4.2.34 AP Image type: MOBILITY EXPRESS IMAGE AP Configuration : MOBILITY EXPRESS CAPABLE 1 Multigigabit Ethernet interfaces 1 Gigabit Ethernet interfaces 2 802.11 Radios Radio Driver version : 9.0.5.5-W8964
Scenario 9: If the show version output does not display the AP image type and AP configuration parameters as highlighted, the AP is running a CAPWAP image. This indicates that the access point needs to be converted to Cisco Mobility Express to run the controller functionality. Refer to the conversion section of this document.
Example output for Scenario 9:
cisco AIR-AP1852E-UXK9 ARMv7 Processor rev 0 (v71) with 997184/525160K bytes of memory. Processor board ID RFDP2BCR021 AP Running Image : 8.2.100.0 Primary Boot Image: 8.2.100.0 Backup Boot Image : 8.1.106.33 AP Image type: MOBILITY EXPRESS IMAGE AP Configuration : MOBILITY EXPRESS CAPABLE 0 Gigabit Ethernet interfaces 0 802.11 Radios Radio FW version : 1401b63d12113073a3C08aa67f0c039c0 NSS FW version : NSS.AK.1.0.c4-02026-E_cust C-1.24160
Conversion
Access points running CAPWAP can be converted to Cisco Mobility Express, and vice versa.
Converting Access Points from CAPWAP to Cisco Mobility Express
For Cisco Mobility Express support on 11ac Wave 2 access points, it is important to note that different AireOS releases are used. Before an access point can be converted to Mobility Express, it requires the minimum AireOS CAPWAP image that supports the Cisco Mobility Express functionality of the access point. The minimum AireOS releases for Cisco Mobility Express support are as follows:
| Access Point | Minimum AireOS Release Supporting CAPWAP Image |
|---|---|
| Cisco Aironet® 1540 Series | Release 8.5 and later |
| Cisco Aironet® 1560 Series | Release 8.4 and later |
| Cisco Aironet® 18151 Series | Release 8.4 and later |
| Cisco Aironet® 1815M Series | Release 8.5 and later |
| Cisco Aironet® 1815W Series | Release 8.4 and later |
| Cisco Aironet® 1830 Series | Release 8.1 MR2 and later |
| Cisco Aironet® 1850 Series | Release 8.1 MR2 and later |
| Cisco Aironet® 2800 Series | Release 8.3 and later |
| Cisco Aironet® 3800 Series | Release 8.3 and later |
If the access point's CAPWAP image is older than the minimum AireOS release that supports Cisco Mobility Express, the access point must first join a WLC running the minimum AireOS release or later to upgrade the CAPWAP image. After upgrading the access point's CAPWAP image, you can convert the AP from CAPWAP to Mobility Express.
To convert an access point running CAPWAP to Mobility Express, follow these steps:
Procedure
Step 1: Download the conversion image from Cisco.com to your TFTP server. This is a .tar file. Do not extract this file. The following table shows the Cisco Mobility Express software for Cisco Wireless Release 8.7.102.0:
| Access Point Supported as Master AP | Software to Use for Conversion to Cisco Mobility Express |
|---|---|
| Cisco Aironet® 1540 Series | AIR-AP1540-K9-8-7-102-0.tar |
| Cisco Aironet® 1560 Series | AIR-AP1560-K9-8-7-102-0.tar |
| Cisco Aironet® 18151 Series | AIR-AP1815-K9-8-7-102-0.tar |
| Cisco Aironet® 1815M Series | AIR-AP1815-K9-8-7-102-0.tar |
| Cisco Aironet® 1815W Series | AIR-AP1815-K9-8-7-102-0.tar |
| Cisco Aironet® 1830 Series | AIR-AP1830-K9-8-7-102-0.tar |
| Cisco Aironet® 1850 Series | AIR-AP1850-K9-8-7-102-0.tar |
| Cisco Aironet® 2800 Series | AIR-AP2800-K9-8-7-102-0.tar |
| Cisco Aironet® 3800 Series | AIR-AP3800-K9-8-7-102-0.tar |
Step 2: Log in to the access point.
Step 3: Execute the command AP#show version in the access point's CLI. Determine the AP Image Type and AP Configuration from the show version output. Then proceed with the conversion process.
Case 1: If the AP Image Type is MOBILITY EXPRESS IMAGE and AP Configuration is NOT MOBILITY EXPRESS CAPABLE, enter the following command to change the AP Configuration to MOBILITY EXPRESS CAPABLE:
AP#ap-type mobility-express
Note: Since the AP already has the MOBILITY EXPRESS IMAGE, a new image will not be downloaded. The access point will reboot after executing the command. After rebooting, the AP Configuration will be changed to MOBILITY EXPRESS CAPABLE.
Case 2: If the AP Image Type and AP Configuration are not displayed, it means the AP is running a CAPWAP image. To perform the conversion, execute the following command:
AP#ap-type mobility-express tftp://<TFTP Server IP>/<path to tar file>
Example:
AP#ap-type mobility-express tftp://10.18.22.34/AIR-AP1850-K9-8.7.102.0.tar
Step 4: If this is the first access point in the network, the controller functionality will start, and the CiscoAirProvison SSID will be broadcast.
Image Download Process:
Starting the ME image download... It may take few minutes to finish the download. Image downloaded, writing to flash... do PREDOWNLOAD, part1 is active part sh: CHECK ME: unknown operand Image start 0x40355008 size 0x01dae41a file size 0x01dae7ca Key start 0x42103422 size 0x00000230 Sinature start 0x42103652 size 0x00000180 Verify returns 0 btldr rel is 16 vs 16, does not need update part to upgrade is part2 activate part2, set BOOT to part2 AP primary version: 8.1.105.37 Archive done. Oe as AP needs to boot up with ME image The system is going down Now! sent SIGTERM to all processes sent SIGKILL to all processes Requesting system reboot79] [07/24/2015 18:19:43.0887] Restarting system. [07/24/2015 18:19:43.1257] Going down for restart now
Note: Once the image download is complete, the image will be written to flash, and the access point will reboot. After the AP boots up, the AP Image Type will be MOBILITY EXPRESS IMAGE, and the AP Configuration will be MOBILITY EXPRESS CAPABLE.
Converting Access Points from Cisco Mobility Express to CAPWAP
There are two main reasons for converting an access point running a Mobility Express image to CAPWAP. They are:
- You want to maintain the access points in a Mobility Express deployment, but you do not want the access points to participate in the master election process when the master AP fails over.
- You want to migrate one or more Mobility Express capable access points to an appliance WLC or a vWLC.
If the reason for converting to CAPWAP is the first reason mentioned above, follow these steps:
- Log in to the access point's CLI via console or SSH and access the EXEC mode. If converting the master AP to CAPWAP, access the controller CLI via console connection. To use the AP CLI, enter
apciscochellat the controller prompt and log in to the access point shell. - Execute the
ap#ap-type capwapCLI command. This will change the AP Configuration to NOT MOBILITY EXPRESS, and the access point will not participate in the master election process.
If the reason for converting to CAPWAP is the second reason mentioned above, follow these steps:
- Log in to the access point's CLI via console or SSH and access the EXEC mode.
- Execute the following CLI command:
(Cisco Controller) >config ap unifiedmode <switch name> <switch ip_address>
<switch_name> and <switch_ip_address> are the name and IP address, respectively, of the WLC to which the APs need to be migrated.
Note: With the command above, all access points running with AP Configuration: MOBILITY EXPRESS CAPABLE will be converted to AP Configuration: NOT MOBILITY EXPRESS CAPABLE. After this command is issued, the AP will reboot and search for and join the controller (switch_ip_address).
