A few different things. First of all, are you sure the slow down is because of the connections and? Generally, oper-data connections like these are pretty cheap.   Regarding tracking it, ncs --status (which is what hides behind the command you run) is pretty good for seeing the current state, to see things happening (in particular for configuration sessions) devel.log is good. For a system install you might have to turn that on explicitly in ncs.conf.   If all the connections (or at least, several hundred of them) are from the ResourceManager you might want to file a ticket to get an explanation. ... View more

Okay, so then it is being immediately re-created. Do you actually have over 400 allocation pools that are being monitored or what are the client names that make up the bulk of that list? ... View more

Hi Clay,   You have a setting called ssh-keep-alive (and another called ned-keep-alive). This can be set either on the individual node or under the device or under devices global-settings to apply to all devices. Hopefully that does what you want! ... View more

That the sequence number increases is normal, but if the number of active connection increases without bound you have more of a problem.    If it grows rapdily, it depends on who is responsible for the connection, that software needs to make sure to close their sessions when they are done with them. In this case you list four active connections from the resource manager - which is quite normal.    For development purposes, a package reload will reset most of these for you. ... View more

I am afraid I am not sure, emailing whoever you got it from might be the best idea. Have you made sure to check software.cisco.com and that you do not have an entitlement there? ... View more

If you are Cisco internal, please look at the NSO field portal for assistance.   If you are Cisco external current customer you should have entitlement at software.cisco.com. If you are not yet a customer you should reach out to your account team or partner contact. ... View more

So, that model is decribed in tailf-ncs-services.yang that tailf-ncs-customers.yang you can find in your distribution. It is a way of linking customers to resource facing services and is based on a TMForum standard. It is essentially a way of organizing your data in a structured way.    Here is an example based on  17-mpls-vpn-python. I have a single l3vpn instance named volvo, I can then do:   admin@ncs% set customers customer volvo status active [ok][2019-02-13 14:18:53] admin@ncs% set services customer-service volvovpn customer volvo reference "Contract ABC123" service /vpn/l3vpn[name=volvo] [ok][2019-02-13 14:20:23]   You can then get a summary of the services the customer has: admin@ncs> show customers        CUSTOMER       ID     SERVICE         --------------------- volvo   [ volvovpn ]    [ok][2019-02-13 14:22:59]   ... View more

Hi Johnny   I am slightly uncertain what it is you are looking for. NSO doesn't have an explicit customer concept with dedicated functionality - but it is fairly straight forward to just implement a customer list. ... View more

An XML file is certainly one good way to go. I would guess that most people with a large number of devices wrap their on boarding actions in some kind of script, especially if it is an ongoing concern.   A helpful trick is that you can perform certain operations at all devices at once, so you can do for instance:  request devices fetch-ssh-host-keys to fetch all keys and request devices sync-from to synchronize all of them at once. ... View more