Help us improve your experience.

Let us know what you think.

Do you have time for a two-minute survey?

Chassis Cluster License Requirements

 

To configure and use the Junos OS software features that require a license in chassis cluster setup, you must apply the licenses to each member of a chassis cluster setup. For more information, see the following topics:

Understanding Chassis Cluster Licensing Requirements

There is no separate license required for chassis cluster. However, some Junos OS software features require a license to activate the feature. To configure and use the licensed feature in a chassis cluster setup, you must purchase one license per feature per device and the license needs to be installed on both nodes of the chassis cluster. Both devices (which are going to form a chassis cluster) must have the valid, identical features licenses installed on them. If both devices do not have an identical set of licenses, then after a failover, a particular feature (that is, a feature that is not licensed on both devices) might not work or the configuration might not synchronize in chassis cluster formation. Licensing is usually ordered when the device is purchased, and this information is bound to the chassis serial number. For example, Intrusion Detection and Prevention (IDP) is a licensed feature and the license for this specific feature is tied to the serial number of the device. For information about how to purchase software licenses, contact your Juniper Networks sales representative at https://www.juniper.net/in/en/contact-us/.

For information about how to purchase software licenses, contact your Juniper Networks sales representative at https://www.juniper.net/in/en/contact-us/.

Installing Licenses on the SRX Series Devices in a Chassis Cluster

You can add a license key from a file or a URL, from a terminal, or from the J-Web user interface. Use the filename option to activate a perpetual license directly on the device. Use the url option to send a subscription-based license key entitlement (such as unified threat management [UTM]) to the Juniper Networks licensing server for authorization. If authorized, the server downloads the license to the device and activates it.

Before adding new licenses, complete the following tasks:

  • Purchase the required licenses.

  • Set the chassis cluster node ID and the cluster ID. See Example: Setting the Node ID and Cluster ID for SRX Series Devices in a Chassis Cluster .

  • Ensure that your SRX Series device has a connection to the Internet (if particular feature requires Internet or if (automatic) renewal of license through internet is to be used). For instructions on establishing basic connectivity, see the Getting Started Guide or Quick Start Guide for your device.

To install licenses on the primary node of an SRX Series device in a chassis cluster:

  1. Run the show chassis cluster status command and identify which node is primary for redundancy group 0 on your SRX Series device.
    {primary:node0}
    user@host> show chassis cluster status redundancy-group 0

    Output to this command indicates that node 0 is primary and node 1 is secondary.

  2. From CLI operational mode, enter one of the following CLI commands:
    • To add a license key from a file or a URL, enter the following command, specifying the filename or the URL where the key is located:

    • To add a license key from the terminal, enter the following command:

  3. When prompted, enter the license key, separating multiple license keys with a blank line.

    If the license key you enter is invalid, an error appears in the CLI output when you press Ctrl+d to exit license entry mode.

  4. Verify the installed licenses.

    For more details, see Adding New Licenses (CLI Procedure).

To install licenses on the secondary node of an SRX Series device in a chassis cluster:

  1. Initiate a failover to change node 1 (secondary node) to be the primary node:

    {primary:node0}

    user@host> request chassis cluster failover redundancy-group 0 node 1
    Note

    Initiating a failover to the secondary node is not required if you are installing licenses manually on the device. However, if you are installing the license directly from the Internet, you must initiate a failover.

  2. Repeat the steps described in Step-by-Step Procedure to install licenses on the secondary node.
  3. Reboot the device for licenses to take effect.
Note

You must install the updated license on both nodes of the chassis cluster before the existing license expires.

Note

In a chassis cluster configuration, when one device has a license installed, and the other device does not have the same license installed, an error message is displayed when you try to configure that specific feature as shown in the following example:

[edit security utm feature-profile web-filtering type]
Tip

If you are not using any specific feature or license , you can delete the license from both devices in a chassis cluster. You need to connect to each node separately to delete the licenses. For details, see Example: Deleting a License Key.

Verifying Licenses on an SRX Series Device in a Chassis Cluster

Purpose

You can verify the licenses installed on both the devices in a chassis cluster setup by using the show system license installed command to view license usage.

Action

Licenses details on node 0.

user@host> show system license installed

Licenses details on node 1.

Meaning

Use the fields License version and Features to make sure that licenses installed on both the nodes are identical.