Help us improve your experience.

Let us know what you think.

Do you have time for a two-minute survey?

 
 

Add CSO Licenses

Note:

This topic is applicable only to the CSO on-premises version.

To maintain a record of CSO licenses purchased by tenants or operating companies (OpCos), users with the SP Administrator role (or users with the necessary access privileges) can add the CSO license for a tenant or an OpCo from the CSO Licenses page.

To add a CSO license:

  1. In Administration Portal, select Administration > Licenses > CSO Licenses.

    The CSO Licenses page appears.

  2. Click the add (+) icon.

    The Add CSO License page appears.

  3. Complete the configuration according to the guidelines in Table 1.
    Note:

    Fields marked with an asterisk (*) are mandatory.

  4. Click OK.

    You are returned to the CSO Licenses page. A job is triggered to add the license and a confirmation message appears at the top of the page. After the job completes successfully, a confirmation message appears and the page refreshes to display the newly added license SKUs.

Table 1: Fields on the Add CSO License page

Setting

Guideline

Add License

Select whether you are adding the license for a tenant or for an operating company.

Tenant

If you are adding the license for a tenant, select the name of the tenant from the drop-down list.

Operating Company

If you are adding the license for an OpCo, select the name of the OpCo from the drop-down list.

Sales Order

Specify the sales order number; For example, 15563238.

SSRN

Specify the software support reference number (SSRN).

This information is necessary to identify your sales order if you contact Juniper Networks for support.

Start Date

Specify the start date (in MM/DD/YYYY format) from which the license is effective.

License SKUs

Add one or more license SKUs:

  1. Click the add (+) icon.

    A row appears inline in the License SKU List grid.

  2. In the License SKU field, enter the SKU name.

    The SKU format is as follows: S-CSO-Release-Type-License-Type-Device-Class-License-Period, where:

    • S, which indicates that the SKU is for software.

    • CSO, which indicates that the SKU is for CSO.

    • Release-Type, which indicates whether the SKU is for a cloud release (C) or an on-premise release (P).

    • License-Type, which indicates whether the license is standard (S1) or advanced (A1)

    • Device-Class

      • A denotes SRX300, SRX320, SRX340, SRX345, vSRX (2 vCPUs), NFX150 devices

      • B denotes NFX250 (2 vCPUs), SRX550 High Memory Services Gateway (SRX550M), SRX1500, vSRX (5 vCPUs) devices.

      • C denotes NFX250 (8 vCPUs), SRX4100, SRX4200, vSRX (9 or 17 vCPUs) devices.

    • License-Period, which indicates the term for the CSO license (1, 3, or 5 years).

  3. In the Device Quantity field, enter the maximum number of on-premise spoke sites that a tenant is authorized to add. You must enter a non-zero number to proceed.

  4. Click √ (check mark) to save your changes.

    The license SKU is saved and displayed in the grid.

  5. (Optional) Repeat the preceding steps if you want to add more license SKUs.

You can modify a license SKU by selecting the corresponding row and clicking the edit (pencil) icon.

See Pre-Deployment Tasks for CSO SD-WAN and Next-Generation Firewall for the next task.

Related Documentation