cancel
Showing results for 
Search instead for 
Did you mean: 
cancel
578
Views
0
Helpful
3
Replies

Migration form co-located BN/CP to dedicated CP and BN

vattanassov
Level 1
Level 1

How to migrate from 2 nodes co-located CP/BN on an SDA site to 2 dedicated CPs and 2 dedicated BNs?

For instance, following the SDA CVD if I start with a small site model for a given site/fabric with CP/BN co-located, how can I later migrate to a medium site model (for the same site/fabric) and split the CP and BN roles for ending up with a 2 nodes CP and 2 nodes BN?

 

3 Replies 3

jedolphi
Cisco Employee
Cisco Employee

Hi, test in the lab first if you can, to make sure your familiar with the outcomes of each action:

  1. Delete one BN+CP
  2. Added dedicated BN (without CP function)
  3. Add dedicated CP
  4. Repeat 1-3 for the other BN+CP

Thanks, that still is my plan, if I need to.

The point here is to receive some guideline from Cisco TME or TAC SE if that has been done before.

Also, is there a good reason for doing it?

According to Scott Hodgdon (@Cisco) more than 95% of all the deployments are with collocated CP/BN and also he said, "there should be no reason NOT to collated these devices (CP/BN) going forward".

Any comment from Cisco TMEs?

Probably the SDA CVD needs some revision and better explanation regarding when to collocate these roles and what benefit gives a dedicated CP.

jedolphi
Cisco Employee
Cisco Employee

Hi @vattanassov, the main reason to separate CP from BN is to facilitate massive endpoint roams/second. Let's say for example you have a Fabric Site with 150K concurrently connected endpoints (the data sheet limit is 100K, but customers can significantly exceed 100K with proper design AND written Cisco BU approval) and most of those endpoints were people/devices/robots that were constantly moving. Each inter-Edge-Node roam will update LISP Control Plane with a new location, which consumes CPU cycles on the CP. Depending on the sustained and max roams/sec it might be necessary to move from co-located BN+CP to dedicated CP. If your Fabric Site is not very roaming-heavy and your BN/CP CPU is not trending high then I don't think there's any compelling reason to make this design change. Best regards, Jerome

Review Cisco Networking for a $25 gift card