Cisco Network Function Virtualization Infrastructure Software Configuration Guide, Release 26.2 and Later

PDF

Cisco Network Function Virtualization Infrastructure Software Configuration Guide, Release 26.2 and Later

Action commands

Want to summarize with AI?

Log in

Lists action commands that help you release, sync, and trust Cisco NFVIS licenses.


Use action commands that can help you release, sync and trust Cisco NFVIS licences.

This command reference includes action commands for managing Cisco NFVIS licenses:

  • license smart release: Use this command to send a "License Usage 0" message to CSSM. This action prompts the CSSM to release the license entitlement associated with your Cisco UCS C Rack servers. If the device continues to operate with Cisco NFVIS after the license release, a usage report, also known as RUM, is sent to CSSM after a predetermined time interval. This report will indicate the actual number of license units consumed, which will then be reserved again on CSSM. Following a license release, a notification and system logging warning is issued, urging you to cease using Cisco NFVIS as the license has been released. You receive this notification every 8 hours during the 24 hours after a license release. If you continue to use Cisco NFVIS beyond this 24-hour period, a RUM report will be generated reflecting the appropriate number of license units consumed by Cisco NFVIS. This report is sent to the Licensing server based on the set periodic interval, after which the licensing server will reserve the correct number of license units for the device again.

  • license smart sync: Report a license usage to CSSM using this action command.

  • license smart trust: Initiate the establishment of trust between the device and the CSSM. This action can prove beneficial in various scenarios, including but not limited to these:

    1. If you delete the product instance from CSSM but wish to continue with Cisco NFVIS Licensing.

    2. If you transfer your licenses from one Virtual Account to another.

    3. If there is an asynchrony between the licensing state on CSSM and on the device.

    4. If the licensing certificates on the device reach their expiry date.