02-16-2018 04:55 AM - edited 07-05-2021 08:15 AM
Hello,
as we met the 200 AP limit on one of our vWLCs, we would like to migrate to the large scale image-
Is there a possible migration path?
At the moment we have both controllers running in parallel, but due to bug CSCva69352 it's not possible to easily move the APs to the new controller.
What can we do now?
Best Regards
Stefan
Solved! Go to Solution.
02-25-2018 11:27 PM
Thank's for your answers.
We finally made it via CLI commands on all APs.
Configured new Controller:
capwap ap primary-base <name> <ip-addr>
Enabled CLI:
debug capwap console cli
Cleared and restarted the CAPWAP tunnel:
test capwap erase
test capwap restart
And, I don't know why, but most of the APs needed a Reload.
Before they were still not able to join the new controller (Certificate issue).
But be aware: some APs lost their configuration after the reload.
They came back without Name, Location etc.
So you should create a backup this informations before.
02-16-2018 05:36 AM
Hi,
Which version do you have? I don´t know any specific documentation for vWLC upgrade but if you have both of it already up and running, the next move is migrating APs.
By the way, the fixed release for this Bug is
02-16-2018 05:46 AM - edited 02-16-2018 05:47 AM
We are running on 8.2.166.0 right now.
I'm not sure if it's an good idea to upgrade to such a new version in the productive environment.
The Cisco recommendation still is an 8.0. Version.
02-16-2018 06:31 AM
I agree. However, the 8.5 is the version Cisco says the Bug was fixed.
-If I helped you somehow, please, rate it as useful.-
02-16-2018 02:03 PM
Thanks for this hint.
I've checked the release notes and found another issue:
we have some 1142 connected to this controller.
It seeems 1140 Series is no longer supported on 8.5.
Are there any other suggestions? :-)
02-16-2018 02:19 PM
Yeah, look like keep a older version is what you need.
And probably older AP is causing this migration problem.
I heard about certificate issue when moving between wlc.
Maybe keep the same version?
-If I helped you somehow, please, rate it as useful.-
02-25-2018 11:27 PM
Thank's for your answers.
We finally made it via CLI commands on all APs.
Configured new Controller:
capwap ap primary-base <name> <ip-addr>
Enabled CLI:
debug capwap console cli
Cleared and restarted the CAPWAP tunnel:
test capwap erase
test capwap restart
And, I don't know why, but most of the APs needed a Reload.
Before they were still not able to join the new controller (Certificate issue).
But be aware: some APs lost their configuration after the reload.
They came back without Name, Location etc.
So you should create a backup this informations before.
Discover and save your favorite ideas. Come back to expert answers, step-by-step guides, recent topics, and more.
New here? Get started with these tips. How to use Community New member guide