- Release notes
- All how to articles
- Data governance
- System requirements
- Get started
- Prerequisites for installing Citrix ADM
- Citrix ADM with Citrix XenServer
- Citrix ADM with Microsoft Hyper-V
- Citrix ADM with VMware ESXi
- Citrix ADM with Linux KVM server
- Configure high availability deployment
- Configure disaster recovery for high availability
- Configure on-prem agents for multisite deployment
- Migrate Citrix ADM single-server deployment to a high availability deployment
- Migrate from NetScaler Insight Center to Citrix ADM
- Migrate Command Center configurations to Citrix ADM
- Integrate Citrix ADM with Citrix XenDesktop Director
- Attach an additional disk to Citrix ADM
- Access control
- StyleBook groups
- Importing and synchronizing StyleBooks from GitHub repository
- Use default StyleBooks
- Business application StyleBooks
Create and use custom StyleBooks
- StyleBook to create a load balancing virtual server
- StyleBook to create a basic load balancing configuration
- Create a composite StyleBook
- Use GUI attributes in a custom StyleBook
- Use custom StyleBooks
- Create a StyleBook to upload files to Citrix ADM
- Create a StyleBook to upload SSL certificate and certificate key files to Citrix ADM
- Enable analytics and configure alarms on a virtual server defined in a StyleBook
- Instance roles
- Create a Stylebook to perform non-CRUD operations
- Use API to create configurations from StyleBooks
- Import StyleBooks
- Parameters-default-sources construct
- Helper components
- Optional properties
- Properties-default-sources construct
- Nested components
- Condition construct
- Repeat construct
- Repeat-condition construct
- Nested repeats
- Parameter reference
- Parent reference
- Components reference
- Substitutions reference
- Variable reference
- In-place interpolations
- Built-in functions
- Dependency detection
- Monitor globally distributed sites
- How to create tags and assign to instances
- How to search instances using values of tags and properties
- Manage admin partitions of Citrix ADC instances
- Back up and restore Citrix ADC instances
- Force a failover to the secondary Citrix ADC instance
- Force a secondary Citrix ADC instance to stay secondary
- Create instance groups
- Rediscover multiple Citrix ADC VPX instances
- Poll Citrix ADC instances and entities
- Unmanage an instance
- Trace the route to an instance
- Use events dashboard
- Set event age for events
- Schedule an event filter
- Set repeated email notifications for events
- Suppress events
- Create event rules
- Modify the reported severity of events that occur on Citrix ADC instances
- View events summary
- Display event severities and SNMP trap details
- Export syslog messages
- Suppress syslog messages
- Configure prune settings for instance events
- Use the SSL dashboard
- Set up notifications for SSL certificate expiry
- Update an installed certificate
- Install SSL certificates on a Citrix ADC instance
- Create a Certificate Signing Request (CSR)
- Link and unlink SSL certificates
- Configure an enterprise policy
- Poll SSL certificates from Citrix ADC instances
- Create a configuration job
- Use record-and-play to create configuration jobs
- Use configuration jobs to replicate configuration from one instance to multiple instances
- Use variables in configuration jobs
- Create configuration jobs from corrective commands
- Replicate running and saved configuration from one Citrix ADC instance to another
- Reuse executed configuration jobs
- Schedule jobs created by using built in templates
- Use maintenance jobs to upgrade Citrix ADC SDX instances
- Create configuration jobs for Citrix SD-WAN WO instances
- Use the master configuration template
- Use jobs to upgrade Citrix ADC instances
- Use configuration templates to create audit templates
- Use SCP (put) command in configuration jobs
- Reschedule jobs configured by using built in templates
- Reuse configuration audit templates in configuration jobs
- Import and export configuration templates
- Maintenance jobs
- Configuration audit
- Network functions
- Network reporting
- Instance management
- License requirements
- Logstream overview
- Self-service diagnostics for Analytics
- Web Insight
- HDX Insight
- Gateway Insight
- Security Insight
- SSL Insight
- TCP Insight
- WAN Insight
- View network efficiency
- Compare the data volume used by optimized and unoptimized ABR videos
- View the type of videos streamed and data volume consumed from your network
- Compare optimized and unoptimized play time of ABR videos
- Compare bandwidth consumption of optimized and unoptimized ABR videos
- Compare optimized and unoptimized number of plays of ABR videos
- View peak data rate for a specific time frame
- Secure Web Gateway Analytics
OpenStack - integrating Citrix ADC instances
- Pre-configuration tasks in Citrix ADM and OpenStack
- Configure LBaaS V1 using Horizon
- Configure LBaaS V2 using command line
- Configure layer 7 content switching
- Manual provisioning of Citrix ADC VPX instance on OpenStack
- Provisioning of Citrix ADM VPX instance on OpenStack using StyleBooks
- Citrix ADC VPX check-in and check-out license and pooled license support for OpenStack environment
- Shared VLAN support for admin partitions
- Trial licensing workflow
- Integrate with OpenStack Heat services
- Service package isolation policies
- Flexible policy-based device allotment
- NSX Manager - manual provisioning of Citrix ADC instances
- NSX Manager - auto provisioning of Citrix ADC instances
- Citrix ADC automation using Citrix ADM in Cisco ACI hybrid mode
- Citrix ADC device package in Cisco ACI's cloud orchestrator mode
- OpenStack - integrating Citrix ADC instances
- Licenses for Citrix ADM License server in high availability
Citrix ADC pooled capacity
- Configure Citrix ADC pooled capacity
- Upgrade a perpetual license in ADC VPX to ADC pooled capacity
- Upgrading a Perpetual License in ADC MPX to ADC Pooled Capacity
- Upgrade a perpetual license in ADC SDX to ADC pooled capacity
- Citrix ADC pooled capacity on ADC instances in cluster mode
- Health monitoring
- Expected behaviors when issues arise
- Configure expiry checks for pooled capacity licenses
- Citrix ADC VPX check-in and check-out licensing
- Citrix ADC virtual CPU licensing
- Manage Citrix SD-WAN instances
Manage HAProxy instances
- Add HAProxy instances to Citrix ADM
- HAProxy app dashboard
- Third-party licensing
- Role-based access control for HAProxy instances
- Monitor HAProxy instances
- View the details of frontends configured on HAProxy instances
- View the details of backends configured on HAProxy instances
- View the details of servers configured on HAProxy instances
- View the HAProxy Instances with the highest number of frontends or servers
- Restart an HAProxy instance
- Back up and restore an HAProxy instance
- Edit the HAProxy configuration file
Manage system settings
- Configure system backup settings
- Configure a NTP Server
- Upgrade Citrix ADM
- How to reset the password for Citrix ADM
- Configure syslog purging interval
- Configure system prune settings
- Enable shell access for non-default users
- Recover inaccessible Citrix ADM servers
- Assign a host name to a Citrix ADM server
- Back up and restore your Citrix ADM server in a single-server deployment
- View auditing information
- Configure SSL settings
- Monitor CPU, memory, and disk usage
- Configure system notification settings
- Generate a tech support file
- Diagnose and troubleshoot Citrix ADC instances
- Back Up and restore a Citrix ADM configuration in an HA pair
- Configure a cipher group
- Create SNMP traps, managers, and users
- Configure and view system alarms
- Citrix ADM as an API proxy server
- Hybrid and Multi-cloud Deployments
This content has been machine translated dynamically.
Dieser Inhalt ist eine maschinelle Übersetzung, die dynamisch erstellt wurde. (Haftungsausschluss)
Cet article a été traduit automatiquement de manière dynamique. (Clause de non responsabilité)
Este artículo lo ha traducido una máquina de forma dinámica. (Aviso legal)
This content has been machine translated dynamically.
This content has been machine translated dynamically.
This article has been machine translated.
Dieser Artikel wurde maschinell übersetzt. (Haftungsausschluss)
Ce article a été traduit automatiquement. (Clause de non responsabilité)
Este artículo ha sido traducido automáticamente. (Aviso legal)
이 기사는 기계 번역되었습니다.
Este artigo foi traduzido automaticamente.
The following diagram illustrates the architecture of the autoscaling feature with DNS as the traffic distributor.
The following diagram illustrates the architecture of the autoscaling feature with NLB as the traffic distributor.
Citrix Application Delivery Management is a web-based solution for managing all Citrix ADC deployments that are deployed on-premises or on the cloud. You can use this cloud solution to manage, monitor, and troubleshoot the entire global application delivery infrastructure from a single, unified, and centralized cloud-based console. Citrix Application Delivery Management (ADM) provides all the capabilities required to quickly set up, deploy, and manage application delivery in Citrix ADC deployments and with rich analytics of application health, performance, and security.
The autoscale groups are created in Citrix ADM and the Citrix ADC VPX instances are provisioned from Citrix ADM. The application is then deployed through StyleBooks in Citrix ADM.
NLB or DNS/Route53 is used to distribute traffic across all the nodes in an autoscale group. See Autoscale traffic distribution modes for more information.
The Citrix ADM communicates with the traffic distributor to update the application domain and IP addresses of the load balancing virtual servers that frontend the application.
Autoscale group is a group of Citrix ADC instances that load balance applications as a single entity and trigger autoscaling based on the configured threshold parameter values.
A Citrix ADC cluster is a group of Citrix ADC VPX instances and each instance is called a node. The client traffic is distributed across the nodes to provide high availability, high throughput, and scalability.
- Autoscaling decisions are made at the cluster level and not at the node level.
- Independent clusters are hosted in different availability zones and therefore support for some of the shared state features are limited.
Persistence sessions such as source IP persistence and others except cookie based persistence cannot be shared across clusters. However, all the stateless features like load balancing methods work as expected across the multiple availability zones.
AWS auto scaling group is a collection of EC2 instances that share similar characteristics and are treated as a logical grouping for the purposes of instance scaling and management.
AWS availability zone is an isolated location inside a region. Each region is made up of several availability zones. Each availability zone belongs to a single region.
As you move your application deployment to cloud, autoscaling becomes a part of the infrastructure. As the applications scale-out or scale-in using autoscaling, these changes must be propagated to the client. This propagation is achieved using DNS based or NLB based autoscaling.
NLB based autoscaling
In NLB-based deployment mode, the distribution tier to the cluster nodes is the AWS network load balancer.
In NLB based autoscaling, only one static IP address is offered per availability zone. This is the public IP address that is added to route53 and the backend IP addresses can be private. With this public IP address, any new Citrix ADC instance provisioned during autoscaling operates using private IP addresses and does not require additional public IP addresses.
NLB supports only TCP-based load balancing. If you want to support UDP traffic, you can choose DNS based autoscaling.
DNS based autoscaling
In DNS based autoscaling, DNS acts as the distribution layer to the Citrix ADC cluster nodes. The scaling changes are propagated to the client by updating the domain name corresponding to the application. Currently, the DNS provider is AWS Route53.
In DNS based autoscaling, each Citrix ADC instance requires a public IP address.
The following flowchart illustrates the autoscaling workflow.
The Citrix ADM collects statistics (CPU usage, memory usage, throughput) from the autoscale provisioned clusters at a time interval of one minute.
The statistics are evaluated against the configuration thresholds. Depending on whether the statistics exceed the maximum threshold or are operating below the minimum threshold, scale-out or scale-in is triggered respectively.
If a scale-out is triggered;
- New nodes are provisioned.
- The nodes are attached to the cluster and the configuration is synchronized from the cluster to the new node.
- The nodes are registered with Citrix ADM.
- The new node IP addresses are updated in DNS/NLB.
When the application is deployed, IPset is created on clusters in each availability zone and the domain and the instance IP addresses are registered with DNS/NLB.
- If a scale-in is triggered;
- The IP addresses of the nodes identified for removal are removed.
- The nodes are detached from the cluster, deprovisioned and then deregistered from Citrix ADM.
When the application is removed, the domain and the instance IP addresses are deregistered from DNS/NLB and the IPset is deleted.
Consider that you have created an autoscale group named asg_arn in a single availability zone with the following configuration.
- Threshold parameter – Memory usage
- Minimum limit: 40
- Maximum limit: 85
- Watch time – 3 minutes
- Cooldown period – 10 minutes
- Drain connection timeout – 10 minutes
- TTL timeout – 60 seconds
After the autoscale group is created, statistics are collected from the autoscale group. The autoscale policy also evaluates if any an autoscale event is in progress and if an autoscaling is in progress, waits for that event to complete before collecting the statistics.
Sequence of events:
- T1 and T2: Memory usage exceeds the maximum threshold limit.
- T3 - Memory usage is below the maximum threshold limits.
T6, T5, T4: Memory usage has breached the maximum threshold limit consecutively for three watch time durations.
- A scale-out is triggered.
- Provisioning of nodes occur.
- Cooldown period is in effect.
T7 – T16: Autoscale evaluation is skipped for this availability zone from T7 through T16 as the cool down period is in effect.
- T18, T19, T20 - Memory usage has breached the minimum threshold limit consecutively for three watch time durations.
- Scale-in is triggered.
- Drain connection timeout is in effect.
- IP addresses are relieved from the DNS/NLB.
T21 – T30: Autoscale evaluation is skipped for this availability zone from T21 through T30 as the drain connection timeout is in effect.
- For DNS based autoscaling, TTL is in effect.
- For NLB based autoscaling, deprovisioning of the instances occurs.
- For NLB based autoscaling, evaluation of the statistics starts.
- For DNS based autoscaling, deprovisioning of the instances occurs.
- T33: For DNS based autoscaling, evaluation of the statistics starts.