Best Practices for WLC Upgrade
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
07-11-2023 11:24 PM
I am currently upgrading from CT2504 8.1.x to CT3504 8.10.x. To ensure safety, I copied the configuration from CT2504 to CT3504. After that, I updated CT3504 to the latest version before connecting the new WLC to our infrastructure. I also made sure that every AP was associated with the primary WLC and that I changed the IP and hostname in copied configuration to prevent conflicts. To further ensure that the new system works as expected, I will test it with a specific AP before applying the upgrade to all AP's.
what are next I have be aware about?
- Labels:
-
Wireless LAN Controller
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
07-11-2023 11:30 PM - edited 07-11-2023 11:31 PM
- You could , for instance, have a checkup of the CT3504 configuration (before production) using this procedure : https://community.cisco.com/t5/networking-knowledge-base/show-the-complete-configuration-without-breaks-pauses-on-cisco/ta-p/3115114#toc-hId-1039672820
Feed the output into (CORRECTED) : https://cway.cisco.com/wireless-config-analyzer/
M.
-- Each morning when I wake up and look into the mirror I always say ' Why am I so brilliant ? '
When the mirror will then always repond to me with ' The only thing that exceeds your brilliance is your beauty! '
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
07-12-2023 12:51 AM - edited 07-12-2023 02:41 AM
I tried to analysis configuration file but it showing this error *BDBUnknownError* while this config file was was getting from WLC itself and I was able to paste it into new WLC without getting any error for that reason I need to start testing it.
Update: I did the same what showing in that post and it showing same error.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
07-12-2023 05:01 AM
>I tried to analysis configuration file but it showing this error *BDBUnknownError*
You can report that to wcae@cisco.com
(if you want)
M.
-- Each morning when I wake up and look into the mirror I always say ' Why am I so brilliant ? '
When the mirror will then always repond to me with ' The only thing that exceeds your brilliance is your beauty! '
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
07-29-2023 09:17 AM
Just to confirm you should be using the output of "show run-config" with that tool?
Please click Helpful if this post helped you and Select as Solution (drop down menu at top right of this reply) if this answered your query.
------------------------------
TAC recommended codes for AireOS WLC's and TAC recommended codes for 9800 WLC's
Best Practices for AireOS WLC's, Best Practices for 9800 WLC's and Cisco Wireless compatibility matrix
Check your 9800 WLC config with Wireless Config Analyzer using "show tech wireless" output or "config paging disable" then "show run-config" output on AireOS and use Wireless Debug Analyzer to analyze your WLC client debugs
Field Notice: FN63942 APs and WLCs Fail to Create CAPWAP Connections Due to Certificate Expiration
Field Notice: FN72424 Later Versions of WiFi 6 APs Fail to Join WLC - Software Upgrade Required
Field Notice: FN72524 IOS APs stuck in downloading state after 4 Dec 2022 due to Certificate Expired
- Fixed in 8.10.196.0, latest 9800 releases, 8.5.182.12 (8.5.182.13 for 3504) and 8.5.182.109 (IRCM, 8.5.182.111 for 3504)
Field Notice: FN70479 AP Fails to Join or Joins with 1 Radio due to Country Mismatch, RMA needed
How to avoid boot loop due to corrupted image on Wave 2 and Catalyst 11ax Access Points (CSCvx32806)
Field Notice: FN74035 - Wave2 APs DFS May Not Detect Radar After Channel Availability Check Time
Leo's list of bugs affecting 2800/3800/4800/1560 APs
Default AP console baud rate from 17.12.x is 115200 - introduced by CSCwe88390
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
07-11-2023 11:37 PM
I would recommend you that after mirroring your current config, and testing all AP models join, you test with different clients as sometimes new codes introduce new standards, features or even software defects, that could make your existing clients to suffer connectivity issues.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
07-12-2023 12:55 AM - edited 07-12-2023 12:56 AM
for that reason I need to install WLC in our infrastructure without effecting current AP's by associate it with specific AP's to test it due that I need to ask which safest procedure to prevent any issue.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
07-12-2023 01:19 AM
What AP models are currently in service?
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
07-12-2023 01:36 AM - edited 07-12-2023 01:36 AM
We are using 2702E, 2702I, 2802E, and 2802I AP's.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
07-12-2023 03:37 AM
The 2700 will do what is called as a "double-download".
It will download the firmware, reboot, join the controller, download the firmware AGAIN and reboot before joining the controller. The entire process will take around 24 minutes per AP.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
07-12-2023 05:05 AM
The best way to proceed is to manually move some APs to the new WLC without setting its IP address in DHCP Option 43 so to avoid unwanted APs to join ('capwap ap primary-base <wlc_name> <wlc_ip>')
First deploy AP on a physical Lab environment (your home office for example) to prevent devices from connecting there, and after all tests are good you can move a small office there to test production environment for 1-month before moving it to full Prod.
