Add_workflow_for_techpubs | ||||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
|
Panel | ||||
---|---|---|---|---|
In this section:
|
Info | ||
---|---|---|
| ||
Related articles: |
SBC Core Portfolio deployments (SBC 5400, SBC 7000, SBC SWe, and SBC CNe) support a domain locked licensing model (DL). In contrast to node-locked licensing, a domain locked license is tied to an administrative domain rather than the hardware ID for a specific host server or the UUID for a specific node instance. A domain locked license is bound to the domain through public/private key-pairing and it defines the features and capacity allowed for all nodes within the domain. DL provides flexibility in cloud environments where the number and placement of nodes sometimes varies. Contact your Ribbon representative for more information on available licensing options and to complete the ordering process that is required prior to implementing DL.
DL is implemented using license management capabilities within the
Spacevars | ||
---|---|---|
|
Spacevars | ||
---|---|---|
|
Spacevars | ||
---|---|---|
|
Spacevars | ||
---|---|---|
|
Spacevars | ||
---|---|---|
|
Spacevars | ||
---|---|---|
|
Spacevars | ||
---|---|---|
|
Refer to License Management in the
Spacevars | ||
---|---|---|
|
After these preparations are completed on
Spacevars | ||
---|---|---|
|
Info | ||||
---|---|---|---|---|
| ||||
The DL license bundle must be added to the SBC cluster configuration before or at the same time you change the license mode to "domain." Changing license mode to domain locked on an active system without a DL license bundle installed will result in a service outage. |
Info | ||||
---|---|---|---|---|
| ||||
|
Info | ||||
---|---|---|---|---|
| ||||
The in-use column does not increment for the active sessions if the license type is ON/OFF. |
Domain Locked Licensing infrastructure supplies critical services for a successful subscription deployment:
• Centralized subscription licensing management
• Recognition of licensed product(s) feature(s) successful delivery
• Accounting for licensed product(s) feature(s) successful delivery through supplementary quotes for events such as domain locked license growth
Domain Locked Licensing Infrastructure is uniquely suited to address shared licensing commercial offers such as True Forward Subscription, Network Wide Domain Locked Licensing, and Multiyear Domain Locked Licensing deployments:
A domain locked license agreement requires customers to deploy and operate the Domain Locked Licensing infrastructure per product specifications for successful subscription-related product consumption.
Initial Deployment
The following figure presents the sequence of actions that flow from the signing of a domain locked license to the point where end nodes are ready to begin delivering services.
The Domain Locked Licensing network topology comprises three major network actors:
• End nodes (for example, SBC, PSX, WebRTC Gateway), where domain locked license product features are delivered;
• RAMP (Ribbon Application Management Platform) where centralized domain locked license-related license management is undertaken, along with aggregation of licensed product feature delivery reports and submission;
• RAP (Ribbon Audit Portal) that reconciles licensed product feature delivery reports for domain locked license accounting and action.
In domain locked licensing mode, you can add to your existing license definition following the same process to load another license bundle file onto
Spacevars | ||
---|---|---|
|
Spacevars | ||
---|---|---|
|
Use the SBC CLI or access the SBC Configuration Manager UI from
Spacevars | ||
---|---|---|
|
Note | ||
---|---|---|
| ||
To avoid a service outage, ensure your DL licenses are already installed if you reconfigure an SBC cluster into domain locked license mode. |
By default, SBC license mode is set to nodeLocked
. Use the following CLI commands to place the SBC in domain locked (DL) license mode:
Code Block | ||
---|---|---|
| ||
% set system licenseMode mode domain % commit |
Or, in the SBC Configuration Manager UI:
Use the following command to output information on the domain locked license bundles loaded into the system.
Code Block | ||
---|---|---|
| ||
> show table system licenseDomainBundleInfo |
Or, in the SBC Configuration Manager UI:
Go to All > System > License Domain Bundle Info The License Domain Bundle Info window opens.
The following license information is output:
activeLicenseMode
– The licensing mode currently in use by the SBCbundleName
– License bundle nameexpirationDate
– License expiration datefeatureName
– license keys for each licensed featuregenerationDate
– The date the license was generatedinstallDate
– The date the license was installedlicenseId
– License IDlineId
– The line ID for the license feature entrypurchaseOrderId
– The purchase order ID specified when the license was generatedusageLimit
– Usage limit for the licensed featureInfo | ||
---|---|---|
| ||
This functionality is not supported on the MRFP. |
The SBC Core products include the capability to shut off calls when there is no License Manager refresh in the last 90 days. The DL architecture requires the user to have the node/instance register with the license manager to report the usage, and then refresh the registration periodically. If the SBC instance is not successfully registered with the license manager in 90 days, the SBC stops processing calls after sending warning alarms to the user.
Info |
---|
The SBC Core registers with the License Manager once per day, independent of the registration status. |
Feature behavior:
Action | Conditions | Result |
---|---|---|
The SBC runs with the licenseMode set to domain |
| The SBC attempts to register with the License Manager |
The SBC sends a registration request to the License Manager |
| The registration is considered as successful. |
The SBC sends a registration request to the License Manager |
|
|
The SBC sends a registration request to the License Manager |
|
|
The SBC fails to register with the License Manager for 90 days | All license counts are set to 0 | |
The License Manager returns a response field called lastCollectionTime (In addition to the registration status) (This represents the previous time the License Manager detected at least one license was consumed – either a counted license was consumed while making a call, or an on/off license is present) |
| The License Manager rejects the registration after 90 days |
The lastCollectionTime in the LicenseManager response is older than one day | The start of the grace period is not updated, even if the registration is successful | |
A licensed feature, REG-GRACE-D, is added (This is a counted license) |
NOTE: On a 1-to-1 system, the GRACE period remaining is identical on both systems. | |
All DL licenses on the SBC Core expire (Example: trial license scenario) | The SBC will not attempt to register with the License Manager. When new DL licenses are installed, the 90 day grace period will restart. | |
An action command is added to test the License Manager settings or to trigger a new License Manager registration after a previous registration request failed. | This provides an opportunity for the operator to rectify the condition on the License Manager that caused a registration to fail, and to retry the request. | |
The installed count for any DL-counted license is greater than 0 | A count of 999999 is available for that license (except for REG-GRACE-D feature) NOTE: If all the license bundles containing a particular feature expire, the count for that feature reaches 0 and the calls requiring that feature do not succeed. The licenseRequired table is no longer supported to limit the license count. |
The SBC Core identifies the
server addresses running the License Manager Micro Service through the following methods: Spacevars 0 model3
Spacevars | ||
---|---|---|
|
Spacevars | ||
---|---|---|
|
Spacevars | ||
---|---|---|
|
Panel | ||||
---|---|---|---|---|
| ||||
To configure a License Server, refer to:
|