Migrating from 5520 to 9800 WLC
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
09-18-2024 05:51 AM
Migrating a client from 5520 to 9800. I do not have access/visibilty to client's devices. Only have a running config text file from the 5520. Although it can be done, it's a painful process going through the configs. Is there another way, or tool, to have the file translated in to Cat 9800 verbage/config?
- Labels:
-
Wireless LAN Controller
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
09-18-2024 06:17 AM
Personally I would configure the new WLC from scratch. Implementing a new WLC is a good time to look over the configuration, make sure best practice is followed, and enable new features.
But here is a converter: https://cway.cisco.com/wlc-config-converter/
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
09-18-2024 06:33 AM
- Besides the other reply , if you are preparing a 9800 controller with a configuration as intended , then validade it with the CLI command :
show tech wireless
And feed the output from that into : https://cway.cisco.com/wireless-config-analyzer/
Consider this mandatory before use. Ps : use the full command , do not use a simple 'show tech' for this
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
09-18-2024 06:46 AM - edited 09-18-2024 06:47 AM
- As I also recommend starting from scratch please have a look at https://www.ciscolive.com/c/dam/r/ciscolive/global-event/docs/2024/pdf/BRKEWN-2094.pdf
It contains many useful topics and details which are sometimes not used or forgotten :
And don't forget to always use WirelessAnalyzer from my first reply
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
09-18-2024 06:54 AM
- If we talk about the client's AP models , then you must also check compatibilities according to : https://www.cisco.com/c/en/us/td/docs/wireless/compatibility/matrix/compatibility-matrix.html
- For the controller it is best to start with 17.12.3
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
09-18-2024 05:33 PM
That will depend on how complicated the AireOS configuration is. Ours is fairly complicated and when we used the tool, the configuration that came out was "dodgy".
We ended up configuring a controller (one out of six) from scratch and used that as the "base" (or template) for the other five.
I migrated about 2100 APs from AireOS to the 9800 and my total outage time was 4 minutes, 45 seconds.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
03-28-2025 03:01 PM
@Leo Laohoo How were the Aps migration, were you using newer Aps, We are using 1572. Can you share high level plan to reduced the outage times. Thanks
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
03-28-2025 05:18 PM
Migrating from AireOS to IOS-XE, we had 3700 and we had some 2800/3800/4800/1560.
I deliberately did not follow the Cisco-recommended method of migrating the APs because it would mean longer outage time. I came up with a solution which had a 4 minutes & 45 seconds outage time (per AP).
