-
Getting Started with Citrix ADC
-
Deploy a Citrix ADC VPX instance
-
Optimize Citrix ADC VPX performance on VMware ESX, Linux KVM, and Citrix Hypervisors
-
Apply Citrix ADC VPX configurations at the first boot of the Citrix ADC appliance in cloud
-
Install a Citrix ADC VPX instance on Microsoft Hyper-V servers
-
Install a Citrix ADC VPX instance on Linux-KVM platform
-
Prerequisites for Installing Citrix ADC VPX Virtual Appliances on Linux-KVM Platform
-
Provisioning the Citrix ADC Virtual Appliance by using OpenStack
-
Provisioning the Citrix ADC Virtual Appliance by using the Virtual Machine Manager
-
Configuring Citrix ADC Virtual Appliances to Use SR-IOV Network Interface
-
Configuring Citrix ADC Virtual Appliances to use PCI Passthrough Network Interface
-
Provisioning the Citrix ADC Virtual Appliance by using the virsh Program
-
Provisioning the Citrix ADC Virtual Appliance with SR-IOV, on OpenStack
-
Configuring a Citrix ADC VPX Instance on KVM to Use OVS DPDK-Based Host Interfaces
-
-
Deploy a Citrix ADC VPX instance on AWS
-
Deploy a VPX high-availability pair with elastic IP addresses across different AWS zones
-
Deploy a VPX high-availability pair with private IP addresses across different AWS zones
-
Configure a Citrix ADC VPX instance to use SR-IOV network interface
-
Configure a Citrix ADC VPX instance to use Enhanced Networking with AWS ENA
-
Deploy a Citrix ADC VPX instance on Microsoft Azure
-
Network architecture for Citrix ADC VPX instances on Microsoft Azure
-
Configure multiple IP addresses for a Citrix ADC VPX standalone instance
-
Configure a high-availability setup with multiple IP addresses and NICs
-
Configure a high-availability setup with multiple IP addresses and NICs by using PowerShell commands
-
Configure a Citrix ADC VPX instance to use Azure accelerated networking
-
Configure HA-INC nodes by using the Citrix high availability template with Azure ILB
-
Configure a high-availability setup with Azure external and internal load balancers simultaneously
-
Configure address pools (IIP) for a Citrix Gateway appliance
-
Upgrade and downgrade a Citrix ADC appliance
-
Solutions for Telecom Service Providers
-
Load Balance Control-Plane Traffic that is based on Diameter, SIP, and SMPP Protocols
-
Provide Subscriber Load Distribution Using GSLB Across Core-Networks of a Telecom Service Provider
-
Authentication, authorization, and auditing application traffic
-
Basic components of authentication, authorization, and auditing configuration
-
On-premises Citrix Gateway as an identity provider to Citrix Cloud
-
Authentication, authorization, and auditing configuration for commonly used protocols
-
Troubleshoot authentication and authorization related issues
-
-
-
-
-
-
-
Persistence and persistent connections
-
Advanced load balancing settings
-
Gradually stepping up the load on a new service with virtual server–level slow start
-
Protect applications on protected servers against traffic surges
-
Retrieve location details from user IP address using geolocation database
-
Use source IP address of the client when connecting to the server
-
Use client source IP address for backend communication in a v4-v6 load balancing configuration
-
Set a limit on number of requests per connection to the server
-
Configure automatic state transition based on percentage health of bound services
-
-
Use case 2: Configure rule based persistence based on a name-value pair in a TCP byte stream
-
Use case 3: Configure load balancing in direct server return mode
-
Use case 6: Configure load balancing in DSR mode for IPv6 networks by using the TOS field
-
Use case 7: Configure load balancing in DSR mode by using IP Over IP
-
Use case 10: Load balancing of intrusion detection system servers
-
Use case 11: Isolating network traffic using listen policies
-
Use case 12: Configure Citrix Virtual Desktops for load balancing
-
Use case 13: Configure Citrix Virtual Apps for load balancing
-
Use case 14: ShareFile wizard for load balancing Citrix ShareFile
-
Use case 15: Configure layer 4 load balancing on the Citrix ADC appliance
-
-
-
-
Authentication and authorization for System Users
-
-
Configuring a CloudBridge Connector Tunnel between two Datacenters
-
Configuring CloudBridge Connector between Datacenter and AWS Cloud
-
Configuring a CloudBridge Connector Tunnel Between a Datacenter and Azure Cloud
-
Configuring CloudBridge Connector Tunnel between Datacenter and SoftLayer Enterprise Cloud
-
Configuring a CloudBridge Connector Tunnel Between a Citrix ADC Appliance and Cisco IOS Device
-
CloudBridge Connector Tunnel Diagnostics and Troubleshooting
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)
此内容已经过机器动态翻译。 放弃
このコンテンツは動的に機械翻訳されています。免責事項
이 콘텐츠는 동적으로 기계 번역되었습니다. 책임 부인
Este texto foi traduzido automaticamente. (Aviso legal)
Questo contenuto è stato tradotto dinamicamente con traduzione automatica.(Esclusione di responsabilità))
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.(Aviso legal)
这篇文章已经过机器翻译.放弃
Questo articolo è stato tradotto automaticamente.(Esclusione di responsabilità))
Translation failed!
Configure a Citrix ADC VPX instance to use Azure accelerated networking
Accelerated networking enables the single root I/O virtualization (SR-IOV) virtual function (VF) NIC to a virtual machine, which improves the networking performance. You can use this feature with heavy workloads that need to send or receive data at higher throughput with reliable streaming and lower CPU utilization. When a NIC is enabled with accelerated networking, Azure bundles the NIC’s existing para virtualized (PV) interface with an SR-IOV VF interface. The support of SR-IOV VF interface enables and enhances the throughput of the Citrix ADC VPX instance.
Accelerated networking provides the following benefits:
- Lower latency
- Higher packets per second (pps) performance
- Enhanced throughput
- Reduced jitter
- Decreased CPU utilization
Note
Azure accelerated networking is supported on Citrix ADC VPX instances from release 13.0 build 76.29 onwards.
Prerequisites
- Ensure that your VM size matches the requirements for Azure accelerated networking.
- Stop VMs (individual or in an availability set) before enabling accelerated networking on any NIC.
Limitations
Accelerated networking can be enabled only on some instance types. For more information, see Supported instance types.
NICs supported for accelerated networking
Azure provides Mellanox ConnectX3 and ConnectX4 NICs in the SR-IOV mode for accelerated networking.
When accelerated networking is enabled on a Citrix ADC VPX interface, Azure bundles either ConnectX3 or ConnectX4 interface with the existing PV interface of a Citrix ADC VPX appliance.
For more information about enabling accelerated networking before attaching an interface to a VM, see Create a network interface with accelerated networking.
For more information about enabling accelerated networking on an existing interface on a VM, see Enable existing interfaces on a VM.
How to enable accelerated networking on Citrix ADC VPX instance using the Azure console
You can enable accelerated networking on a specific interface using the Azure console or the Azure PowerShell.
Do the following steps to enable accelerated networking by using Azure availability sets or availability zones.
-
Log in to Azure portal, and navigate to Azure Marketplace.
-
From the Azure Marketplace, search Citrix ADC.
-
Select a non-FIPS Citrix ADC plan along with license, and click Create.
The Create Citrix ADC page appears.
-
In the Basics tab, create a Resource Group. Under the Parameters tab, enter details for the Region, Admin user name, Admin Password, license type (VM SKU), and other fields.
-
Click Next : VM Configurations >.
On the VM Configurations page, perform the following:
- Configure public IP domain name suffix.
- Enable or disable Azure Monitoring Metrics.
- Enable or disable Backend Autoscale.
-
Click Next: Network and Additional settings >.
On the Network and Additional Settings page, create a Boot diagnostics account and configure the network settings.
Under the Accelerated Networking section, you have the option to enable or disable the accelerated networking separately for the Management interface, Client interface, and Server interface.
-
Click Next: Review + create >.
After the validation is successful, review the basic settings, VM configurations, network and additional settings, and click Create. It might take some time for the Azure Resource Group to be created with the required configurations.
-
After the deployment is complete, select the Resource Group to see the configuration details.
-
To verify the Accelerated Networking configurations, select Virtual machine > Networking. The Accelerated Networking status is displayed as Enabled or Disabled for each NIC.
Enable accelerated networking using Azure PowerShell
If you need to enable accelerated networking after the VM creation, you can do so using Azure PowerShell.
Note:
Ensure to stop the VM before you enable Accelerated Networking using Azure PowerShell.
Perform the following steps to enable accelerated networking by using Azure PowerShell.
-
Navigate to Azure portal, click the PowerShell icon on the right-hand top corner.
Note:
If you are in the Bash mode, change to the PowerShell mode.
-
At the command prompt, run the following command:
az network nic update --name <nic-name> --accelerated-networking [true | false] --resource-group <resourcegroup-name> <!--NeedCopy-->
The accelerated networking parameter accepts either of the following values:
- True: Enables accelerated networking on the specified NIC.
- False: Disables accelerated networking on the specified NIC.
To enable accelerated networking on a specific NIC:
az network nic update --name citrix-adc-vpx-nic01-0 --accelerated-networking true --resource-group rsgp1-aan <!--NeedCopy-->
To disable accelerated networking on a specific NIC:
az network nic update --name citrix-adc-vpx-nic01-0 --accelerated-networking false --resource-group rsgp1-aan <!--NeedCopy-->
-
To verify the Accelerated Networking status after the deployment is completed, Navigate to VM > Networking.
In the following example, you can see that Accelerated Networking is Enabled.
In the following example, you can see that Accelerated Networking is Disabled.
To verify accelerated networking on an interface by using FreeBSD Shell of Citrix ADC
You can log in to FreeBSD shell of Citrix ADC, and run the following commands to verify the accelerated networking status.
Example for ConnectX3 NIC:
The following example shows the “ifconfig” command output of the Mellanox ConnectX3 NIC. The “50/n” indicates the VF interfaces of the Mellanox ConnectX3 NICs. 0/1 and 1/1 indicates the PV interfaces of the Citrix ADC VPX instance. You can observe that both PV interface (1/1) and CX3 VF interface (50/1) have the same MAC addresses (00:22:48:1c:99:3e). This indicates that the two interfaces are bundled together.
Example for ConnectX4 NIC:
The following example shows the “ifconfig” command output of the Mellanox ConnectX4 NIC. The “100/n” indicates the VF interfaces of the Mellanox ConnectX4 NICs. 0/1, 1/1, and 1/2 indicates the PV interfaces of Citrix ADC VPX instance. You can observe that both PV interface (1/1) and CX4 VF interface (100/1) have the same MAC addresses (00:0d:3a:9b:f2:1d). This indicates that the two interfaces are bundled together. Similarly, the PV interface (1/2) and CX4 VF interface (100/2) have the same MAC addresses (00:0d:3a:1e:d2:23).
To verify accelerated networking on an interface by using ADC CLI
Example for ConnectX3 NIC:
The following show interface command output indicates that the PV interface 1/1 is bundled with virtual function 50/1, which is an SR-IOV VF NIC. The MAC addresses of both 1/1 and 50/1 NICs are the same. After accelerated networking is enabled, the data of the 1/1 interface is sent through datapath of the 50/1 interface, which is a ConnectX3 interface. You can see that the “show interface” output of PV interface (1/1) points to the VF (50/1). Similarly, the “show interface” output of VF interface (50/1) points to the PV interface (1/1).
Example for ConnectX4 NIC:
The following show interface command output indicates that the PV interface 1/1 is bundled with virtual function 100/1, which is an SR-IOV VF NIC. The MAC addresses of both 1/1 and 100/1 NICs are the same. After accelerated networking is enabled, the data of 1/1 interface is sent through the data path of 100/1 interface, which is a ConnectX4 interface. You can see that the “show interface” output of PV interface (1/1) points to the VF (100/1). Similarly, the “show interface” output of VF interface (100/1) points to the PV interface (1/1).
Points to note in Citrix ADC
- PV interface is considered as the primary or main interface for all the necessary operations. Configurations must be performed on PV interfaces only.
- All the ‘set’ operations on a VF interface are blocked except the following:
- enable interface
- disable interface
- reset interface
- clear stats
Note:
Citrix recommends that you do not perform any operations on the VF interface.
- You can verify the binding of PV interface with VF interface using the
show interface
command.
Configure a VLAN to a PV interface
When a PV interface is bound to a VLAN, the associated accelerated VF interface is also bound to the same VLAN as the PV interface. In this example, the PV interface (1/1) is bound to VLAN (20). The VF interface (100/1) that is bundled with the PV interface (1/1) is also bound to VLAN 20.
Example:
-
Create a VLAN.
add vlan 20 <!--NeedCopy-->
-
Bind a VLAN to the PV interface.
bind vlan 20 –ifnum 1/1 show vlan 1) VLAN ID: 1 Link-local IPv6 addr: fe80::20d:3aff:fe9b:f21d/64 Interfaces : LO/1 2) VLAN ID: 10 VLAN Alias Name: Interfaces : 0/1 100/1 IPs : 10.0.1.29 Mask: 255.255.255.0 3) VLAN ID: 20 VLAN Alias Name: Interfaces : 1/1 100/2 <!--NeedCopy-->
Note
VLAN binding operation is not permitted on an accelerated VF interface.
bind vlan 1 -ifnum 100/1
ERROR: Operation not permitted
<!--NeedCopy-->
Share
Share
In this article
- Prerequisites
- Limitations
- NICs supported for accelerated networking
- How to enable accelerated networking on Citrix ADC VPX instance using the Azure console
- Enable accelerated networking using Azure PowerShell
- To verify accelerated networking on an interface by using FreeBSD Shell of Citrix ADC
- To verify accelerated networking on an interface by using ADC CLI
- Points to note in Citrix ADC
- Configure a VLAN to a PV interface
This Preview product documentation is Citrix Confidential.
You agree to hold this documentation confidential pursuant to the terms of your Citrix Beta/Tech Preview Agreement.
The development, release and timing of any features or functionality described in the Preview documentation remains at our sole discretion and are subject to change without notice or consultation.
The documentation is for informational purposes only and is not a commitment, promise or legal obligation to deliver any material, code or functionality and should not be relied upon in making Citrix product purchase decisions.
If you do not agree, select Do Not Agree to exit.