Fabric Domain vs Fabric Site and DNAC scalability

[norberto.padin]

Hello, I have a customer with 150 branches plus HQ, so, fabric-in-a-box sounds ok for those sites.

The WAN today IPSec based (no SD-WAN at all) and is not meant to be used as an IP Transit.

As per the title of this post, will each branch be a Fabric Domain? 

If this is the case, DNAC scalibility (10 fabric domains, 500 fabric sites) won't be enough and I'll need several DNAC, is that correct?

In order to overcome DNAC limitation, will l need to convert the WAN in an IP Transit?

Thanks in advance!

Nor.

[jedolphi · Accepted solution]

Hello Nor,

*Each branch can be a fabric site in same fabric domain. Probably one fabric domain would be sufficient for your requirements

*For explanation of site and domain see most recent version of BRKCRS-2815 on www.ciscolive.com . At this time most recent version is from San Diego 2019

*One DNA Centre implementation should be sufficient for 150 branches (=150 fabric sites).

*Please review the design best practices document for other DNA Centre scaling data. Number of sites is not the only factor you should consider: https://community.cisco.com/t5/networking-documents/cisco-sda-design-guidance-and-best-practices/ta-p/3865954

*An IPSec WAN can be an SD-Access IP Transit, review following document for explanation of IP Transit:

https://community.cisco.com/t5/networking-documents/cisco-sd-access-for-distributed-campus-with-ip-as-a-transit/ta-p/3837284

*Also review latest version of BRKCRS-2811 on www.ciscolive.com . At this time most recent version is from San Diego 2019

Best regards, Jerome