Beginning with SBC Core release 7.0, the SBC is configured in legacy license mode by default. The “local” and “network” options for license mode that were supported for SBC SWe in prior releases are being phased out. Options to change license mode through the CLI or EMA are no longer available as of release 7.0. Although some references to local license mode remain in documentation, the CLI, or the EMA UI, local license mode is not supported.
If your SBC SWe deployment was configured to use network license mode in a prior release, the tools to monitor and configure network-mode licensing remain available in release 7.0, but will be phased out in the future. Information needed to maintain network license mode is still provided. Contact your Ribbon Sales Representative for more information and assistance in updating your license.
License Encoded with Fingerprint Capability
- The license is restricted and encoded with the fingerprint capability:
- When the license is generated for a local license deployment, the license is encoded with the fingerprint of the SBC (or SBCs in the case of HA system) and the license is restricted to the SBC that matches the fingerprint.
- When the license is generated for a network license deployment, the license is encoded with the fingerprint of the EMS pair where SLS is running.
For Network Wide Licensing find the Fingerprint through EMS:
- Log on to EMS.
Select Insight GUI → License Manager.
- Copy the Fingerprint.
For Local Licensing find the Fingerprint of the SBC at the CLI:
- Log on to SBC CLI as admin.
Ensure that the SBC is up and running.
Type the following command to get the Fingerprint.
- Copy the Fingerprint and keep it handy.
License floating enables a limited number of licenses to be shared among a number of network devices It is applicable when the SBC is deployed on network wide licensing with a centralized SLS distributing licenses to the SBCs connected to it.
There are two ways to delete a license:
From the xml bundle at CLI or EMA for a local license and legacy licenses.
From the Required License Table, in case of network licensing.
When a license name is deleted from the license required table the SBC returns all tokens of the license back to the SLS.
Any existing sessions that are initiated prior to the license being removed can continue, but new calls will be denied access to the associated licensed functionality.
- In a local or legacy license mode - Once the license is expired, the SBC treats the licensed functionality as disabled system wide. Any existing sessions that are active on expiry continues unimpaired. Traps are raised from the SBC to notify the user when a license is nearing expiration. For more information on Alarms, refer to the Alarms Guide.
- In a network license mode - Once the license is expired, the SLS does not serve expired licenses to the SBC. The EMS raises traps to notify the user when a license is nearing expiration.