Autonomous to LWAPP Migration

1. Autonomous to LWAPP Migration

2. Upgrading Autonomous Access Points to LWAPP Mode • Basic AP upgrade process: • Use Cisco-provided upgrade tool to load “LWAPP Recovery IOS Image” onto the AP(s) • AP joins a controller, downloads full LWAPP IOS image • LWAPP IOS upgrade is supported on the following platforms: • 1120G series (802.11B/G) • 1200 series, including 1210, 1230 (802.11B/G and/or 2nd generation 802.11A radios—RM21A, RM22A) • 1130AG • 1240AG • BR1310 (only AP mode is supported in LWAPP) • Only layer-3 LWAPP mode is supported • Roll-back to autonomous-mode is supported

3. LWAPP Upgrade Requirements • Ensure the AP’s hardware is supported • The AP is running IOS release 12.3(7)JA, or later • The controller is running 3.1, or later and telnet is enabled • Each AP’s information is input into a text file in the following format: • ap-ip-address,telnet-username,telnet-user-password,enable-password • ap-ip-address,telnet-username,telnet-user-password,enable-password • … (WLC_CLI) >config network telnet enable or In the WLC GUI, Go to: Management | Telnet-SSH and Enable Telnet.

4. Using the LWAPP Upgrade Tool • AP upgrade tool Point the Upgrade Tool to the AP csv text file Ensure the latest IOS LWAPP (JX) image is available via TFTP Telnet must be enabled on a WLC Make sure the time is correctly set APs with static IP addresses will rely on DNS to find WLCs across router hops 1 – 5 APs may be upgraded simultaneously. Their completion status bars are shown here. AP upgrade process status Click for AP MAC and SSC output

5. How Long Does it Take? Measured from the type the “start” button is clicked until the AP upgrades firmware, reloads, and completes the final join to the controller Self-Sign Certificates required for IOS APs which shipped beforeJuly 18, 2005

6. Tips for Running the Upgrade Tool A large site will need half a day just to complete the LWAPP image upgrade – for example the minimum time required for 500 APs is: (500 APs x 10 minutes) / 6 threads = 13.9 hours Using multiple PCs running the Upgrade Tool can speed the process: ((500 APs x 10 minutes) / 6 threads) / 4 PCs = 3.5 hour No, you can’t use VMware to speed up the process – the Upgrade Tool is CPU-bound Use a wired connection for running the Upgrade Tool More bandwidth to speed the TFTPs Upgrading the AP you’re connected to is a bad thing! Don’t mix-and-match AP models during the upgrade

7. Upgrading Autonomous Access Points to LWAPP Mode—Best Practices • Basic upgrade strategy: • Deploy, validate controllers and WCS • Plan an LWAPP discovery strategy so APs can discover controllers • Test the process in a lab or on low-traffic, easy-to-troubleshoot APs to validate the procedure • Do the migration during a change window and allow time for troubleshooting • Save the CSV file(s) with the MAC/Public Key mappings even if you import them to WCS • Migrate APs in logical blocks rather then en masse • Take caveats to co-existence into consideration • Evaluate tolerance for downtime

8. Upgrading Autonomous Access Points to LWAPP Mode—WLSM and WiSM Co-Existence • WLSM and WiSM can co-exist in the same 650x chassis • Minimum software requirements: • Supervisor 720: 12.2(18)SXF2 • WLSM: Version 1.4.1 • WiSM: 3.2.116.x http://www.cisco.com/en/US/partner/products/hw/modules/ps2706/products_configuration_example09186a008073614c.shtml

9. Coexistence Between Autonomous Access Point and Controller-Based Architecture • No seamless roaming between architectures • No coordination between WLSE radio management (RM) and Cisco Unified Architecture RRM • RM and RRM algorithms should account for contention • Each architecture may report other’s APs as rogue • Consider network architectural impact and any necessary changes very carefully • Upgraded APs should be connected to access ports instead of trunk ports • May need to clean-up and harvest old, unnecessary VLANs and IP subnets • Plan out new IP addressing schemes for wireless clients and APs