---
title: Appendix
slug: _0qA-appendix
createdAt: 2026-07-27T04:11:11.848Z
---

### Licensing

Ivanti Policy Secure(IPS) software includes Ivanti Licensing and Software Download Center @ [https://my.pulsesecure.net,](https://my.pulsesecure.net/) that lets you configure the license server to allow administrators to view all configured systems and move those licenses as needed. Other devices on the network lease licenses from the central license server. For more information, see *License Management Guide*.

Starting with IPS version 5.0, clustering works as follows:

- Clustering does not require a license.
- Place an equal number of licenses on each appliance, when they are joined together to form a cluster, the user licenses add up so that the cluster supports all the licensed users.
- For example, building a 1,000-user cluster is done by bringing together two appliances with 500 user licenses in each of the two units.
- For third-party features, each node in a cluster should have similar license counts.
- The maximum number of concurrent users allowed in a cluster is the sum of all user licenses of all connected nodes.

If your client devices are using IPS prior to release 5.0:

- A license is no longer required to create a cluster. Prior to Release 4.0, to create a multiple node cluster that supports multiple concurrent users, you were required to purchase one ADD-ccccE license for one cluster node, and n-1 CL licenses (one for each of the remaining cluster nodes). For example, to create a 4-node cluster supporting 2000 concurrent users, you needed to purchase one ADD-2000E license and 3 CL licenses.
- CL licenses are no longer necessary but are still supported. When you upgrade to Release 4.0, your existing licenses continue to work. There is no cluster grace period for the node with a CL license installed. When the node with a CL license installed disconnects, the capacity computation is the same as before Release 4.0.
- A 5-day cluster grace period provides license flexibility when a node crashes or loses connectivity with the rest of the cluster.
- We recommend that you distribute your ADD licenses equally across the cluster to avoid losing large number of licenses when a node disconnects from the cluster.

The following table illustrates why we recommend distributing licenses equally across all cluster nodes.

| License Distribution                      | Example                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                         |
| ----------------------------------------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| Example 1: Equal distribution             | Suppose Node A and Node B are part of a cluster, and each node has 500 concurrent user licenses then the maximum number of licenses is 1000.<br />Suppose Node B disconnects from the cluster. Until the clustering grace period ends, the maximum number of licenses on Node A is 500 (from Node A’s original license) + minimum (licenses on Node A (500), licenses on Node B (500)) = 500 + 500 = 1000.<br />After the grace period ends, the maximum number of licenses on Node A reverts to its original license of 500.                                                                                                                                                                                                                                                                                                                                                                                   |
| Example 2: Unequal distribution           | In this example, Node A and Node B are part of a cluster. Node A has 600 ADD licenses and Node B has 400 ADD licenses then the maximum number of licenses is 1000.<br />Suppose Node B disconnects from the cluster. Until the clustering grace period ends, the maximum number of licenses on Node A is 600 (from Node A’s original license) + minimum (licenses on Node A (600), licenses on Node B (400)) = 600 + 400 = 1000. After the grace period ends, the maximum number of licenses on Node A is 600.<br />Suppose Node A disconnects from the cluster. Until the clustering grace period ends, the maximum number of licenses on Node B is 400 (from Node B’s original license) + minimum (licenses on Node A (600), licenses on Node B (400)) =400+400 = 800. After the grace period ends, the maximum number of licenses on Node B is 400.                                                          |
| Example 3. Unequal distribution (extreme) | In this example, Node A and Node B are part of a cluster. Node A has 1000 ADD licenses and Node B has no ADD licenses.<br />Suppose Node B disconnects from the cluster. Until the clustering grace period ends, the maximum number of licenses on Node A is 1000 (from Node A’s original license) + minimum (licenses on Node A (1000), licenses on Node B (0)) = 1000 + 0 = 1000. After the grace period ends, the maximum number of licenses on Node A is 1000.<br />Suppose Node A disconnects from the cluster. Until the clustering grace period ends, the maximum number of licenses on Node B is 0 (from Node B’s original license) + minimum (licenses on Node A (1000), licenses on Node B (0)) =0+0 = 0. After the grace period ends, the maximum number of licenses on Node B is 0.<br />For the scenarios in Examples 2 and 3, we recommend you distribute the licenses equally amongst the nodes. |

### Configuring IPv6 on an Existing IPv4 Active/Passive Cluster

We recommend as a best practice that you configure IPv6 host and network settings on individual nodes before you create a cluster. In some cases, such as routine upgrade, you have already created a cluster configuration and only want to add IPv6 addresses to the existing interface configuration. If so, follow the procedures in this section precisely.

:::hint{type="info"}
You must leave IPv6 disabled until the last step of the procedures shown below.
:::

To modify the internal port configuration for the cluster:

1. Select **System > Network > Internal Port > Settings**.
2. Under **Settings for**, select **Entire cluster**.
3. Complete the configuration for the IPv6 prefix and the IPv6 gateway, but do not enable IPv6.
4. Verify that all the nodes are up and running, are in sync, and are in reachable state. Complete synchronization of the cluster pair might take a few minutes.
5. Under **Settings for**, selec&#x74;**&#x20;Node 1**.
6. Configure the IPv6 address, but do not enable IPv6.
7. Verify both the nodes are up and running and in reachable state.
8. Repeat steps 6-8 for **Node 2**.
9. Select **System > Network > Internal Port > Virtual Ports**.
10. Update the cluster virtual port configuration to add the IPv6 address.
11. Select **System > Network > Internal Port > Settings**.
12. Under **Settings for**, select **Entire cluster**.
13. Select **Enable IPv6**.

To modify the external port configuration for the cluster:

1. Select **System > Network > External Port > Settings.**
2. Under **Settings for**, select **Entire cluster**.
3. Complete the configuration for the IPv6 prefix and the IPv6 gateway, but do not enable IPv6.
4. Verify that all the nodes are up and running, are in sync, and are in reachable state. Complete synchronization of the cluster pair might take a few minutes.
5. Under **Settings for**, select **Node 1**.
6. Configure the IPv6 address, but do not enable IPv6.
7. Verify both the nodes are up and running and in reachable state.
8. Repeat steps 6-8 for Node 2.
9. Select **System > Network > External Port > Virtual Ports**.
10. Update the cluster virtual port configuration to add the IPv6 address.
11. Select **System > Network > External Port > Settings**.
12. Under **Settings for**, select **Entire cluster**.
13. Select **Enable IPv6**.
