Citrix ADC pooled capacity 编辑

The Citrix ADC pooled capacity allows you to share bandwidth or instance licenses across different ADC form factors. For virtual CPU subscription based instances, you can share virtual CPU license across instances. Use this pooled capacity for the instances that are in the data center or public clouds. When an instance no longer requires the resources, it checks the allocated capacity back into the common pool. Reuse the released capacity to other ADC instances that need resources.

You can use pooled licensing to maximize the bandwidth utilization by ensuring the necessary bandwidth allocation to an instance and not more than its need. Increase or decrease the bandwidth allocated to an instance at run time without affecting the traffic. With the pooled capacity licenses, you can automate the instance provisioning.

How Citrix ADC pooled capacity licensing works

Citrix ADC pooled capacity has the following components:

• Citrix ADC instances, which can be categorized into:
  • Zero-capacity hardware
  • Standalone VPX instances or CPX instances
• Bandwidth pool
• Instance pool
• Citrix ADM configured as license server

Zero-capacity hardware

When managed through Citrix ADC pooled capacity, MPX and SDX instances are referred to as “zero-capacity hardware” because these instances cannot function until they check resources out of the bandwidth and instance pools. Therefore, these platforms are also referred to as MPX-Z, and SDX-Z appliances.

Zero-capacity hardware requires a platform license to be able to check out bandwidth and an instance license from the common pool. However, you cannot use Citrix ADC pooled capacity to another Citrix ADC hardware instance.

Manage and install platform licenses. You must install a platform license manually, by using the hardware serial number or the license access code. After a platform license is installed, it is locked to the hardware and cannot be shared across Citrix ADC hardware instances on demand. However, you can manually move the platform license to another Citrix ADC hardware instance.

ADC MPX instances running the ADC software release 11.1 build 54.14 or later and ADC SDX instances running 11.1 build 58.13 or later support ADC pooled capacity. For more information, see Table 1. Supported pooled capacity for MPX and SDX instances.

Standalone Citrix ADC VPX instances

Citrix ADC VPX instances running Citrix ADC software release 11.1 Build 54.14 and later on the following hypervisors supports pooled-capacity:

• VMware ESX 6.0

• Citrix Hypervisor

• Linux KVM

Citrix ADC VPX instances running Citrix ADC software release 12.0 Build 51.24 and later on the following hypervisors and cloud platforms supports pooled-capacity

• Microsoft Hyper-V

• AWS

• Microsoft Azure

Note

To enable communication between Citrix ADM and Microsoft Azure or AWS, an IPSEC tunnel has to be configured. For more info, see Add Citrix ADC VPX Instances Deployed in Cloud to Citrix ADM. Unlike zero-capacity hardware, VPX does not require platform license. To process traffic, it must check out bandwidth and an instance license from the pool.

Standalone Citrix ADC CPX instances

Citrix ADC CPX instances deployed on a Docker host support pooled-capacity. Unlike zero-capacity hardware, CPX does not require platform license. To process traffic, it must check out an instance license from the pool.

Bandwidth Pool

The bandwidth pool is the total bandwidth that can be shared by Citrix ADC instances, both physical and virtual. The bandwidth pool comprises separate pools for each software edition (Standard, Enterprise, and Platinum). A given Citrix ADC instance cannot have bandwidth from different pools checked out concurrently. The bandwidth pool from which it can check out bandwidth depends on its software edition for which it is licensed.

Instance pool

The instance pool defines the number of VPX instances or CPX instances that can be managed through Citrix ADC pooled capacity or the number of VPX instances in an SDX-Z instance.

When checked out from the pool, a license unlocks the MPX-Z, SDX-Z, VPX, and CPX instance’s resources, including CPUs/PEs, SSL cores, packets per second, and bandwidth.

Note

The Management Service of an SDX-Z does not consume an instance.

Citrix ADM license server

Citrix ADC pooled capacity uses Citrix ADM software configured as a license server to manage pooled capacity licenses: bandwidth pool licenses and instance pool licenses. You can use Citrix ADM to manage pooled capacity licenses without an ADM license.

When checking out licenses from bandwidth and instance pool, Citrix ADC form factor and hardware model number on a zero-capacity hardware determines

• The minimum bandwidth and the number of instances that a Citrix ADC instance must check out before being functional.

• The maximum bandwidth and the number of instances that a Citrix ADC can check out.

• The minimum bandwidth unit for each bandwidth check-out. Minimum bandwidth unit is the smallest unit of bandwidth that a Citrix ADC has to check out from a pool. Any check-out must be an integer multiple of the minimum bandwidth unit. For example, if the minimum bandwidth unit of a Citrix ADC is 1 Gbps, 100 Gbps can be checked out, but not 200 Mbps or 150.5 Gbps. Minimum bandwidth unit is different from the minimum bandwidth requirement. A Citrix ADC instance can only operate after it is licensed with at least the minimum bandwidth. Once the minimum bandwidth is met, the instance can check out more bandwidth with the minimum bandwidth unit.

Tables 1, 2, and 3 summarize the maximum bandwidth/instances, minimum bandwidth/instances, and minimum bandwidth unit for all supported NetScaler instances. Table 4 summarizes the license requirement for different form factors. For all supported Citrix ADC instances:

Table 1. Supported pooled capacity for MPX and SDX instances

Note

The minimum bandwidth and instances are applicable to SDX instances running the following releases and higher: 11.1 64.x, 12.0 63.x, and 12.1 54.x.

The minimum purchase quantity is different from the minimum system requirement.

Table 2. Supported pooled capacity for CPX instances

Table 3. Supported pooled capacity for VPX instances on hypervisors and cloud services

Note

The minimum purchase quantity is different from the minimum system requirement.

Table 4. License requirement for different form factors