Cisco Support Community
cancel
Showing results for 
Search instead for 
Did you mean: 
Announcements

Welcome to Cisco Support Community. We would love to have your feedback.

For an introduction to the new site, click here. If you'd prefer to explore, try our test area to get started. And see here for current known issues.

New Member

3850 MC to 5760 MC migration planning

Last summer we deployed 15 3850's as mobility controllers in various buildings throughout our campus. We now have additional funds to purchase a 5760 high availability pair. I am trying to plan the best way to migrate the access points from the standalone closet 3850 controllers to a centralized 5760, with the 3850's acting as mobility agents. This is the sequence I have come up with so far - 1. create a dns entry with CISCO-CAPWAP-CONTROLLER resolving to the address of the new 5760 so the access points can find the new mobility controller. 2. add sufficent licenses to the 5760 to move the existing 3850's AP populations. 3. reconfigure the 3850's as mobility agents. Is there something I am overlooking? When I change the role of the 3850's from MC to MA, will the attached AP's reboot and find the 5760? Or will changing the role of the 3850 require a reboot that will take care of the AP's rebooting and discovering the new 5760? We also have Prime 2.0, is there a way any of this can be automated with templates? We also have a 5508 still in service with roughly 50 1142 ap's attached to it. We bought the 3850's along with new 2602's, and have been running two parallel wireless networks. Should we retire the 5508 or upgrade the code and leave it in service as an additional mobility controller? Please ask question if more information is needed to respond.

2 ACCEPTED SOLUTIONS

Accepted Solutions
VIP Purple

HiFew suggestions1. Even if

Hi

Few suggestions

1. Even if you change MC functionality from 3850 to 5760 still CAWPAP tunnel terminate on MA. So no point changing DNS entry or DHCP option 43 as AP CAPWAP will never go back & terminate on 5760(as long as AP connect to MA). In CA deployment MC is required for holding licence, RRM, mobility,etc (not to terminate CAPWAP)

 

2. I would suggest bring 5760 online with necessary configuration (dynamic interfaces, SSIDs, etc) and configure the mobility with 3850. Then take one 3850 at a time & change its role to MA & pointing to 5760 as MC. 3850 should be reloaed when change the role. So your AP will re-register to 3850, but licence hold on 5760 this time. Below post may give some guidance

http://mrncciew.com/2013/12/12/getting-started-with-5760/

http://mrncciew.com/2013/12/14/3850ma-with-5760mc/

 

3. Regarding 5508, upgrade it to 7.6.110.0 (only supported version which could enable "New Mobility") & enable "new mobility" feature. Then configure it a a mobility controller peering with 5760. That will give the advantage of client roaming between your CUWN & CA deployment setup.

 

4. If you want to retire 5508 & move 1142 to 5760, then you need to pointing APs to 5760 as WLC (assuming 1142s are not connected to 3850MAs and they are connected to legacy switches)

 

HTH

Rasika

*** Pls rate all useful responses ****

VIP Purple

From the AP registration

From the AP registration point of view, AP does not need to know about MC. Its only known MA (as directly connected) and then MA has information where is MC (to get the licence for AP registration).

All AP CAPWAP communication is betwen MA & AP (nothing beyond MA)

Here is a link to very good presentation on this CA architecture, Please go through it, you will learn a lot from this

BRKARC-2665 - Converged Access Architecture, Design and Deployment (2014 Melbourne)

Hope that clear you query

Rasika

*** Pls rate all useful responses ***

3 REPLIES
VIP Purple

HiFew suggestions1. Even if

Hi

Few suggestions

1. Even if you change MC functionality from 3850 to 5760 still CAWPAP tunnel terminate on MA. So no point changing DNS entry or DHCP option 43 as AP CAPWAP will never go back & terminate on 5760(as long as AP connect to MA). In CA deployment MC is required for holding licence, RRM, mobility,etc (not to terminate CAPWAP)

 

2. I would suggest bring 5760 online with necessary configuration (dynamic interfaces, SSIDs, etc) and configure the mobility with 3850. Then take one 3850 at a time & change its role to MA & pointing to 5760 as MC. 3850 should be reloaed when change the role. So your AP will re-register to 3850, but licence hold on 5760 this time. Below post may give some guidance

http://mrncciew.com/2013/12/12/getting-started-with-5760/

http://mrncciew.com/2013/12/14/3850ma-with-5760mc/

 

3. Regarding 5508, upgrade it to 7.6.110.0 (only supported version which could enable "New Mobility") & enable "new mobility" feature. Then configure it a a mobility controller peering with 5760. That will give the advantage of client roaming between your CUWN & CA deployment setup.

 

4. If you want to retire 5508 & move 1142 to 5760, then you need to pointing APs to 5760 as WLC (assuming 1142s are not connected to 3850MAs and they are connected to legacy switches)

 

HTH

Rasika

*** Pls rate all useful responses ****

New Member

Thank you for such a detailed

Thank you for such a detailed, clear response!  I just have one more question - it sounds like the mobility controller is referenced on the mobility agent and that is how the ap's find the new MC, is that correct?  There is someplace to define the MC on the MA, so that even if the AP's are on a different subnet from the controller, (they shouldn't be, but just in case) they will still find the new MC because the MA has that information?

 

 

VIP Purple

From the AP registration

From the AP registration point of view, AP does not need to know about MC. Its only known MA (as directly connected) and then MA has information where is MC (to get the licence for AP registration).

All AP CAPWAP communication is betwen MA & AP (nothing beyond MA)

Here is a link to very good presentation on this CA architecture, Please go through it, you will learn a lot from this

BRKARC-2665 - Converged Access Architecture, Design and Deployment (2014 Melbourne)

Hope that clear you query

Rasika

*** Pls rate all useful responses ***

76
Views
0
Helpful
3
Replies