Sorry to blast this out but I’m looking for some tricky answers.
How does the vMS solution handle VNF de-licensing? I know we licenses the VNFs (CSR/ASA) via a token provided by NSO and the CSR would then register with smart licensing server at tools.cisco.com.
But when the service chain is deleted, does NSO do a “license smart deregister” before telling ESC to remove the VM?
I’m not only asking to understand vMS, but also the general best practice if I was to use the NSO+ESC Reactive Fast Map via the standard vm-manager package to bring up/down a CSR via a service model.
Or is it handled automagically in if the license step is done as part of a Day1 NSO operation, then would NSO just naturally remove all Day1 before deleting the VM? There are some configuration commands
to enable smart licensing servicesbut the actual “license smart” register and deregister commands are not configuration commands, they are done at the enable prompt.
I have a choice to just add the license info in the day0 config by adding a “do” statement at the bottom, but I’m worried if I delete the VM it will not de-register.
do license smart register idtoken <token here> force
Can someone send sample code or recommendations? Wasn’t ESC going to provide some standard licensing features? If we used an ESC token, would ESC handle this when the VM is killed?
Re: Question on how NSO/vMS handles VNF de-licensing
And realize that deregister works only when everything went smoothly…
Expect it not to work perfectly everytime and might need an occasional manual audit between what is active in VMS vs what is shown in Smart licensing server. There is currently no automatic audit/reconciliation process.