How do I manually generate and deploy a license key?
Pre-requisite
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 |