How do I manually generate and deploy a license key?

Pre-requisite

  • “Perform automated license key deployment?” is set to true in the network pool key details.

The duration of any license manually generated and deployed is given by the “Manual License Key Duration in Days” of the network pool key details.

Note: Changing the functionality of a network function may require a network function reboot for the new functionality to become active. The CLM does not automatically reboot the network function.

Deployment steps for VSR-I/7x50 SR

Deploying a license key to the VSR-I/7x50 network functions consists of the following steps.

Step

Description

Validate connection

CLM will validate that it can connect to the network function using the UID and CLI credentials.

Check UUID

CLM will validate that all UUIDs of the network function match those as reported by the network function.

If the network function UUID is not filled in, CLM will attempt to connect to the network function and populate the UUID field with the correct value from the network function. Otherwise, you can use CLI to look up the corresponding value on the network function. See the appropriate node documentation.  NOTE: The UUID field corresponds to the Chassis Serial # for 7x50 SR.

Generate license key

CLM generates a unique license key file for the selected network function.

Upload license key to CLR

CLM places the license key file onto the license repository referenced by the network function.

NOTE: For 7x50 SR/XRS network functions, the preferred method of license key storage is local storage on the 7x50 SR/XRS.

Activate license

CLM sets the network function to reference the license key file. For example, for a VSR-I, the BOF is set to reference the location of the license key file on the license repository

Procedure
 
1 

Sign in as a user with read/write access to CLM.

2 

Using the main menu, navigate to Centralized License Manager, Network Functions.

3 

Click on a network function for which you want to deploy a license key and click png4.png (Table row actions), Deploy License Key.

4 

Click DEPLOY.

The deploy license key operation is asynchronous and may take a few minutes depending on your network performance. Clicking png9.png updates the data in the network function grid.

The Deployed Status column of the network function grid indicates that the license key file has been deployed to the license repository. After deploying a license key:

  • If the network function is not marked as Deployed, there will be notifications raised about problems communicating with the referenced license repository.

  • If the network function is marked as Deployed, but there are notifications raised against it, the network function is not configured to use the new license key.

If a deploy operation fails, CLM raises a notification with the step, the CLI command CLM sent, and the CLI response received. You must address the problem indicated in the notification, and then choose the deploy license key operation again.

End of steps