Checkout the LSA documentation that comes with the NSO installation (for example nso_lsa-4.5.pdf). Also check out "deployment_guide.pdf" that comes bundled with the tailf-hcc package (describes the NSO HA framework).
I have read both of those documents which covers how to deploy NSO and how to take advantage of LSA and the deployment model needed when using LSA. What I think is missing is when to use the various deployment options.
Questions I need to answer are:
When are there too many (NSO scale) or too geographically dispersed (timeouts from NSO to devices issue) devices for a single NSO installation (non-LSA) to no longer be effective?
If an LSA based deployment is necessary, how does one handle the situation when the location where the Service Layer NSO HA pair goes offline?
Would it ever be sensible to every split up an NSO HA pair between locations?
All good questions. I know various folks have discussed these but don't think there is a guide as such. The information is available but dispersed. Perhaps we can request the Cisco-AS team to do a "guide" write-up, given that they have done majority of the real-life deployments. Also engineering have done some simulations too.
I've added my thoughts below.
When it comes to scale, the dimensions to consider are:
Memory as all configs are stored in the in-memory CDB
- The number of devices and the average size of the device configuration
- The number of service instances and the average size of the service configuration
- Mark this up to account for metadata (back-pointers, etc). That should give the required memory.
The incoming rate of Move-Add-Change (MAC) requests
- The complexity of service mapping logic for each of the service-types
- Transactional approach or asycn commit-queues
- I've seen some testing done 3+ years back with NETSIMs and commit-queue. With CPUs back then the throughput was around 14 changes per seconds for a VPN like service
- The service types could be split across multiple NSOs (CFS-NODEs) to spread the incoming MACs.
I guess every scenario is so different and one sizing may not work for all. BTW, I've heard the rule-of-thumb of scale-out with LSA with 20k-30k devices per NSO-RFS-instance.
Fredrik Jansson, Principal Engineer & John Mullooly, Distinguished Architect, SalesIn the first half of this lab, we build a k8s deployment of NSO from the ground up. We will start packaging NSO in a docker container, from there we will graduall...
Michael Maddern, Technical Marketing Engineer
This session will demonstrate the use of template-based fastmap in Cisco NSO. It’s easy to underestimate how quickly and simply a new service can be configured based on a synced configuration and templates. R...