Citrix ADC pooled capacity
Citrix ADC pooled capacity is a licensing framework that comprises a common bandwidth and instance pool that is hosted on and served by Citrix ADM. From this common pool, each Citrix ADC instance in your data center, regardless of platform or form factor, checks out one instance license and only as much bandwidth as it needs. The license file and, consequently, the bandwidth are not bound to the instance. When the instance no longer requires these resources, it checks them back in to the common pool, making the resources available to other instances that need them.
This licensing framework maximizes bandwidth utilization by ensuring that instances are not allocated bandwidth in excess of their requirement. The ability of Citrix ADC instances to check licenses and bandwidth in and out of a common pool also enables you to automate instance provisioning.
You can increase or decrease the bandwidth allocated to an instance at run time without impacting traffic. You can also transfer Citrix ADC licenses in the pool from one instance to another.
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 ADC license server
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. Accordingly, these platforms are also referred to as MPX-Z, and SDX-Z appliances.
Zero-capacity hardware require 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
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.
Currently, the following zero-capacity hardware, running the Citrix ADC software release 11.1 Build 54.14 or later, support Citrix ADC pooled capacity:
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 XenServer
- 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
- Amazon AWS
- Microsoft Azure
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 supports 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.
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.
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.
The Management Service of an SDX-Z does not consume an instance.
Citrix ADC license server
Citrix ADC license server is a component in Citrix Application Delivery Management (ADM). Citrix ADC pooled capacity uses Citrix ADC 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 a MAS 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 instance 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 minimum bandwidth unit of a Citrix ADC is 1Gbps, 100Gbps can be checked out, but not 200Mbps or 150.5Gbps. 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 additional bandwidth with minimum bandwidth unit.
The following table summarizes the Maximum bandwidth/instances, minimum bandwidth/instances and minimum bandwidth unit for all supported Citrix ADC instances.
For Citrix ADC MPX/SDX/CPX
|Maximum bandwidth (Gbps)||Minimum bandwidth (Gbps)||Minimum instances||Maximum instances||Minimum bandwidth unit|
|MPX 8900Z||33||5||NA||NA||1 Gbps|
|MPX-15000Z series||100||20||NA||NA||1 Gbps|
|SDX-14000Z series||100||20||5||25||1 Gbps|
|SDX 15000Z-50G||100||20||5||25||1 Gbps|
|SDX 26000Z-100G||200||100||20||115||1 Gbps|
For Citrix ADC VPX on Hypervisors and Cloud services
|Hypervisor/Cloud Service||Maximum bandwidth (Gbps)||Minimum bandwidth (Mbps)||Minimum instances||Maximum instances||Minimum bandwidth unit|
|Citrix XenServer||40 Gbps||10 Mbps||1||1||10 Mbps|
|VMware ESXI||100 Gbps||10 Mbps||1||1||10 Mbps|
|Linux KVM||100 Gbps||10 Mbps||1||1||10 Mbps|
|Microsoft Hyper-V||3 Gbps||10 Mbps||1||1||10 Mbps|
|AWS||5 Gbps||10 Mbps||1||1||10 Mbps|
|Azure||3 Gbps||10 Mbps||1||1||10 Mbps|
The following table summarizes the license requirement for different form factors.
|Zero Capacity Hardware Purchase||Bandwidth & Edition Subscription||Instance Subscription|
|MPX||License required||License required|
|SDX||License required||License required||License required|
|VPX||License required||License required|