What do I need to know about NSP licensing?
NSP licensing
Starting with NSP Release 25.4, the Centralized License Manager (CLM) is integrated within each NSP deployment. CLM is still offered as a standalone product to manage NE licenses in deployments without NSP, however as of NSP Release 25.4, the CLM functions have been embedded in NSP and enhanced to handle NSP system licensing. The entitlements of the NSP system license key (which is called the NSP Routing key in NSP CLM) include information about license points and feature packages.
The NSP license key is added after NSP installation. Entitlements within the NSP license key can be added, viewed, and maintained over time from the Centralized License Manager option in the NSP main menu.
You only need one NSP license key for the NSP whether you have a standalone NSP setup, or whether you have an HA or HA/DR setup. However, if you intend to run NSP Simulation in addition to NSP, you require another unique NSP license key for NSP Simulation.
Prior to the NSP license key expiration date, NSP issues daily alarms with increasing severity levels at 180, 90, and 7 days before expiration. NSP raises a minor alarm once every 24 hours starting 180 days prior to expiration, which is replaced by a major alarm issued every 24 hours starting at 90 days before expiration, which in turn is replaced by a critical alarm 7 days before expiration, and thereafter. These alarms can be viewed in the Current Alarms view as well as in Centralized License Manager, Notifications. For more details about specific alarms, see “What does this notification mean?" in the Centralized License Manager User Guide.