F-5
Cisco MGX 8850 (PXM1E/PXM45), Cisco MGX 8950, Cisco MGX 8830, and Cisco MGX 8880 Configuration Guide
Release 5.0.10, OL-3845-01 Rev. B0, August 16, 2004
Appendix F MPSM Licensing
MPSM Licensing Information
lists the terminology used for managing feature licenses on the MPSM cards.
Table F-4
Feature LIcense Terminology for MPSM Cards
Term Explanation
Allocated Licenses
To provide a feature or service, a license is acquired by a module from the pool of installed
licenses on the node. An acquired license is referred to as allocated to the module.
Available Licenses
The installed licenses which are not allocated are said to be available in the license pool for
use by modules.
Encrypted Key
A long string of characters generated by the Keycutter application. This string contains all
information about purchased licenses as well as the node to which it can be applied.
Grace Period
Under certain conditions, if a sufficient number of licenses are not available or if licenses are
invalid, the system is allowed for certain period of time to run without impacting service. This
period is called the Grace Period, and by default it is set to 5 days (120 hours).
Note
Within this period, it is responsibility of the system owner to purchase and install the
required number of licenses to avoid service degradation after this period has expired.
Installed Licenses
This refers to the purchased licenses which have been added to the license pool owned by the
node. The installed licenses in the license pool can be used by the service modules plugged into
the MGX node. Licenses are used by the modules on as-needed basis.
License Pool
License Pool is a persistent database of all installed licenses owned by an MGX node. Service
modules are allocated licenses from this pool to provide services and features. Licenses are
added to the pool by installing them on the node using cnflic or movelic CLI commands.
Moving Licenses
When programmed licenses migrate from a module NVRAM into the license pool and become
installed, we refer the process as moving the licenses from a card to the license pool.
Needed Licenses
These are licenses that are required by an entity (such as a service module) to provide desired
services or features. For the entity to operate normally, it must have same number of allocated
licenses as needed licenses.
Programmed Licenses
When the licenses are supplied in the NVRAM of a module, we refer to them as physically
programmed licenses. These licenses cannot be allocated to any module, but they can be
installed in a node by moving them from NVRAM of the module to the license pool owned by
the MGX node.
Registering Licenses
When licenses are moved from the card’s NVRAM to the license pool, the process is also
referred to as registering licenses with the node.
Rekey License
If a licensed shelf database is migrated to another non-native shelf, the licenses become invalid.
To revalidate shelf licenses, Rekeying or Rehosting licenses is necessary. The special license
that achieves this purpose is the Rekey License. Rekey license is the same as RAK.
Transferring Licenses
You can migrate installed licenses from one node’s license pool to another node’s installed
pool of licenses. This process is referred to as transferring licenses.
