cancel
Showing results for 
Search instead for 
Did you mean: 
cancel
58
Views
1
Helpful
2
Replies
Highlighted
Cisco Employee

Question on how NSO/vMS handles VNF de-licensing

 

Hi VMs/NSO team(s);

 

 

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 services but 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?

 

Everyone's tags (5)
1 ACCEPTED SOLUTION

Accepted Solutions
Highlighted
Cisco Employee

Re: Question on how NSO/vMS handles VNF de-licensing

 

John

 

In vMS licensing info is added as part of the day 0 conifg.

 

Before deletion of VNF’s in a service chain, reactive fast map on NSO de-registers the license.

 

 

This is a best effort as the de-register is dependent on VNF connectivity to the licensing server.

 

NSO executes de-register RFM and waits for 30 seconds for the de-register process to complete.

 

  • NSO is able to connect to VNF,  then license is removed from the pool on licensing server and VNF’s are deleted.
  • NSO is able to connect to VNF, but de-register fails because of connectivity between VNF and licensing server.

    NSO proceeds with deletion of the VNF but the license will not be removed from the pool.

    NSO logs that de-register fails.

  • NSO is not able to connect to VNF, ESC will recover the VM’s based on recovery method specified.

    License will not be removed from the pool.

  

 

 

CSR config:

 

 

!####_DAY0_LICENSE

 

!

 

license smart enable

 

call-home

 

http-proxy $VR_MANAGEMENT_PROXY port $VR_MANAGEMENT_PROXY_PORT

 

ip http client source-interface GigabitEthernet1

 

do license smart register idtoken $VR_LICENSE_TOKEN

 

do write

 

 

Throughput level is configured as part of day n configuration in vMS else you can add the below command into day 0 as well.

 

 

“Platform hardware throughput level MB xxxx”

 

 

ASA config:

 

 

license smart

 

feature tier standard

 

throughput level 2G

 

!

 

call-home

 

http-proxy licenseproxy port $VFW_MANAGEMENT_PROXY_PORT

 

source-interface mgmt

 

!

 

license smart register idtoken $VFW_LICENSE_TOKEN

 

!

 

!

 

write memory

 

View solution in original post

2 REPLIES 2
Highlighted
Cisco Employee

Re: Question on how NSO/vMS handles VNF de-licensing

 

John

 

In vMS licensing info is added as part of the day 0 conifg.

 

Before deletion of VNF’s in a service chain, reactive fast map on NSO de-registers the license.

 

 

This is a best effort as the de-register is dependent on VNF connectivity to the licensing server.

 

NSO executes de-register RFM and waits for 30 seconds for the de-register process to complete.

 

  • NSO is able to connect to VNF,  then license is removed from the pool on licensing server and VNF’s are deleted.
  • NSO is able to connect to VNF, but de-register fails because of connectivity between VNF and licensing server.

    NSO proceeds with deletion of the VNF but the license will not be removed from the pool.

    NSO logs that de-register fails.

  • NSO is not able to connect to VNF, ESC will recover the VM’s based on recovery method specified.

    License will not be removed from the pool.

  

 

 

CSR config:

 

 

!####_DAY0_LICENSE

 

!

 

license smart enable

 

call-home

 

http-proxy $VR_MANAGEMENT_PROXY port $VR_MANAGEMENT_PROXY_PORT

 

ip http client source-interface GigabitEthernet1

 

do license smart register idtoken $VR_LICENSE_TOKEN

 

do write

 

 

Throughput level is configured as part of day n configuration in vMS else you can add the below command into day 0 as well.

 

 

“Platform hardware throughput level MB xxxx”

 

 

ASA config:

 

 

license smart

 

feature tier standard

 

throughput level 2G

 

!

 

call-home

 

http-proxy licenseproxy port $VFW_MANAGEMENT_PROXY_PORT

 

source-interface mgmt

 

!

 

license smart register idtoken $VFW_LICENSE_TOKEN

 

!

 

!

 

write memory

 

View solution in original post

Highlighted
Cisco Employee

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.

 

 

Content for Community-Ad
Cisco Community July 2020 Spotlight Award Winners
This widget could not be displayed.