NWDL Overview

SBC SWe deployments support a domain-based licensing model referred to as network-wide domain licensing (NWDL). In contrast to node-locked licensing, a domain 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 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. NWDL 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 NWDL.

Note

Starting with SBC 9.1, Ribbon does NOT support Network-Wide Domain Licensing (NWDL) on hardware SBC platforms (5000 series/5400/7000). However, Ribbon supports NWDL on the following virtual and cloud platforms:

  • VMware
  • Red Hat Virtualization (RHV)
  • OpenStack (already supported)
  • Amazon Web Services (AWS)

On Openstack, the SBC instance automatically registers with the EMS to pull its configuration when the instance boots up, including when you re-instantiate. For other virtual/cloud platforms, you must manually push the NWDL licenses to the SBC during initial instantiation and subsequent re-instantiations.

NWDL is implemented using license management capabilities within the Insight Element Management System (EMS). The EMS provides the public key used to bind the license to the local domain and is used for associating license data with eligible nodes. The basic steps to implement domain licensing are as follows:

  • Log into the EMS managing the SBC SWe cluster and copy the EMS domain public key.
  • Submit the copied public key, along with the order details, to the self-service licensing portal to generate a license bundle file that incorporates the domain public key.
  • Install the NWDL license bundle on the EMS.
  • From the EMS, add the feature licenses to the SBC cluster configuration. The licenses are added to the OAM which then replicates the configuration (including licenses) to the SBC nodes. 

Refer to the License Management section in EMS documentation for specific procedures to locate and copy the public key, install a license bundle, and associate feature licenses with SBC nodes.

After these preparations are completed on the EMS, enable domain-based licensing on the SBC cluster by configuring the license mode as "domain." Save and activate the configuration. The OAM node for the cluster provides the configuration update to each SBC node in the cluster. The nodes then enable or disable features and set maximum capacity based on the license definition in their configuration.

Important

The NWDL 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 on an active system without an NWDL license bundle installed will result in a service outage. 

Adding License Capacity

In domain licensing mode, you can add to your existing license definition following the same process to load another license bundle file onto the EMS, and using the EMS to assign the additional features licenses to the SBC clusters. The resulting set of licenses features and capacity for the cluster is the aggregate of the existing license and the added license.

Full-Capacity Licensing Option

When configured for NWDL, the SBC supports a "full-capacity" option in which the counts for individual, counted license features are no longer used to limit activity on the SBC. Enabling the full-capacity feature effectively enables feature use up to the capacity of the node. Actual license usage is reported to Ribbon using EMS statistics.

The full-capacity feature requires the SBC-CAPACITY-D license key in the license file. Contact your Ribbon representative for more information on the use of the full-capacity licensing option.

Restricting Licensed Capacity on a Node

The SBC provides a mechanism to restrict the nodes in a cluster to a subset of a domain's licensed capacity, if needed. To define such restrictions, the SBC uses the License Required table (/system/licenseRequired/). Entries in the License Required table are optional when using NWDL and, when present, the entries specify limits on the license capacity allowed for each node. By default no limits are configured; the absence of entries in the License Required table indicates that the node is entitled to use the entire capacity associated with the SBC cluster.

Be aware that if you choose to specify any restrictions then you must configure appropriate limits for all counted features and also include entries in the License Required table for any on/off features you want to enable. If the License Required table contains a limit for any feature, any other features that are not included in the table are treated as having a license count of 0 and are effectively disabled. If you are using the full-capacity licensing option enabled by the SBC-CAPACITY-D license key, then any maxCount values you specify in License Required table entries are ignored.

Configuring NWDL Options

Use the SBC CLI or access the SBC Configuration Manager UI from the EMS to enable domain license mode and optionally specify license capacity limits for the nodes in the cluster. Refer to Modifying SBC Cluster Configuration.

Enabling Domain License Mode

Caution

To avoid a service outage, ensure your NWDL licenses are already installed if you reconfigure an SBC cluster into domain license mode.


By default, SBC license mode is set to nodeLocked. Use the following CLI commands to place the SBC in domain (NWDL) license mode:

Enable Domain License Mode using CLI
% set system licenseMode mode domain
% commit

Or, in the SBC Configuration Manager UI:

  1. Go to All > System > License Mode  The License Mode window opens.
  2. In Mode, select Domain.
  3. Click Save.

Specifying License Capacity restrictions for a Node (Optional)

Use the following CLI command to add entries in the License Required table to specify limits on the license capacity allowed for nodes in the cluster on a per-feature basis. If you specify a limit for any feature, you must include an entry in the licenseRequired table for each feature you want to enable, including features that are not counted (on/off features) or counted features that you do not want to limit. For features that you want to enable but do not need to restrict, it is not necessary to specify the maxCount parameter because its default value is unlimited. 

License Required CLI Syntax
% set system licenseRequired <licensed feature key> maxCount <2-1000000, or "unlimited">
% commit
ParameterDescription
<feature key>

The license key for a licensed feature that you want to enable for the specific node.

 maxCountThe maximum number of uses of the licensed feature allowed for the specified node within what is allowed for the domain. The allowed range is 2–1000000, or "unlimited" (default). For license keys that are not counted (on/off), or for counted features you do not want to limit, it is not necessary to enter a maxCount value.

Or, in the SBC Configuration Manager UI:

  1. Go to Administration > System Administration > License Management > Network License Settings > Required License. The Required License window opens.
  2. Click New Required License. The Create New Required License window opens.
  3. Select a feature from the Feature Name list.
  4. Enter a numeric limit in Max Count
  5. Click Save.

Displaying Domain License Bundle Information

Use the following command to output information on the domain license bundles loaded into the system.

 > 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 SBC
  • bundleName – License bundle name
  • expirationDate – License expiration date
  • featureName – license keys for each licensed feature
  • generationDate – The date the license was generated
  • installDate – The date the license was installed
  • licenseId – License ID
  • lineId – The line ID for the license feature entry
  • purchaseOrderId – The purchase order ID specified when the license was generated
  • usageLimit – Usage limit for the licensed feature