-
Getting Started with NetScaler
-
Deploy a NetScaler VPX instance
-
Optimize NetScaler VPX performance on VMware ESX, Linux KVM, and Citrix Hypervisors
-
Apply NetScaler VPX configurations at the first boot of the NetScaler appliance in cloud
-
Configure simultaneous multithreading for NetScaler VPX on public clouds
-
Install a NetScaler VPX instance on Citrix Hypervisor
-
Configuring NetScaler Virtual Appliances to use Single Root I/O Virtualization (SR-IOV) Network Interfaces
-
-
Install a NetScaler VPX instance on Microsoft Hyper-V servers
-
Install a NetScaler VPX instance on Linux-KVM platform
-
Prerequisites for installing NetScaler VPX virtual appliances on Linux-KVM platform
-
Provisioning the NetScaler virtual appliance by using OpenStack
-
Provisioning the NetScaler virtual appliance by using the Virtual Machine Manager
-
Configuring NetScaler virtual appliances to use SR-IOV network interface
-
Configure a NetScaler VPX on KVM hypervisor to use Intel QAT for SSL acceleration in SR-IOV mode
-
Configuring NetScaler virtual appliances to use PCI Passthrough network interface
-
Provisioning the NetScaler virtual appliance by using the virsh Program
-
Provisioning the NetScaler virtual appliance with SR-IOV on OpenStack
-
Configuring a NetScaler VPX instance on KVM to use OVS DPDK-Based host interfaces
-
-
Deploy a NetScaler 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
-
Protect AWS API Gateway using the NetScaler Web Application Firewall
-
Configure a NetScaler VPX instance to use SR-IOV network interface
-
Configure a NetScaler VPX instance to use Enhanced Networking with AWS ENA
-
Deploy a NetScaler VPX instance on Microsoft Azure
-
Network architecture for NetScaler VPX instances on Microsoft Azure
-
Configure multiple IP addresses for a NetScaler 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
-
Deploy a NetScaler high-availability pair on Azure with ALB in the floating IP-disabled mode
-
Configure a NetScaler VPX instance to use Azure accelerated networking
-
Configure HA-INC nodes by using the NetScaler high availability template with Azure ILB
-
Configure a high-availability setup with Azure external and internal load balancers simultaneously
-
Configure a NetScaler VPX standalone instance on Azure VMware solution
-
Configure a NetScaler VPX high availability setup on Azure VMware solution
-
Configure address pools (IIP) for a NetScaler Gateway appliance
-
Deploy a NetScaler VPX instance on Google Cloud Platform
-
Deploy a VPX high-availability pair on Google Cloud Platform
-
Deploy a VPX high-availability pair with external static IP address on Google Cloud Platform
-
Deploy a single NIC VPX high-availability pair with private IP address on Google Cloud Platform
-
Deploy a VPX high-availability pair with private IP addresses on Google Cloud Platform
-
Install a NetScaler VPX instance on Google Cloud VMware Engine
-
-
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
-
Web Application Firewall protection for VPN virtual servers and authentication virtual servers
-
On-premises NetScaler Gateway as an identity provider to Citrix Cloud
-
Authentication, authorization, and auditing configuration for commonly used protocols
-
Troubleshoot authentication and authorization related issues
-
-
-
-
-
-
Configure DNS resource records
-
Configure NetScaler as a non-validating security aware stub-resolver
-
Jumbo frames support for DNS to handle responses of large sizes
-
Caching of EDNS0 client subnet data when the NetScaler appliance is in proxy mode
-
Use case - configure the automatic DNSSEC key management feature
-
Use Case - configure the automatic DNSSEC key management on GSLB deployment
-
-
-
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 and Desktops for load balancing
-
Use case 14: ShareFile wizard for load balancing Citrix ShareFile
-
Use case 15: Configure layer 4 load balancing on the NetScaler 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 NetScaler 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 VPX instances to use single root I/O virtualization (SR-IOV) network interfaces
After you have installed and configured a NetScaler VPX instance on Citrix Hypervisor, you can configure the virtual appliance to use SR-IOV network interfaces.
The following NICs are supported:
- Intel 82599 10G
- Intel X710 10G
- Intel XL710 40G
Limitations
Citrix Hypervisor does not support some features on SR-IOV interfaces. The limitations with Intel 82599, Intel X710, and Intel XL710 NICs are listed in the following sections.
Limitations for Intel 82599 NIC
Intel 82599 NIC does not support the following features:
- L2 mode switching
- Clustering
- Admin partitioning [Shared VLAN mode]
- High Availability [Active - Active mode]
- Jumbo frames
- IPv6 protocol in Cluster environment
Limitations for Intel X710 10G and Intel XL710 40G NICs
Intel X710 10G and Intel XL710 40G NICs have the following limitations:
- L2 mode switching is not supported.
- Admin partitioning (shared VLAN mode) is not supported.
- In a cluster, Jumbo frames are not supported when the XL710 NIC is used as a data interface.
- Interface list reorders when interfaces are disconnected and reconnected.
- Interface parameter configurations such as speed, duplex, and auto negotiations are not supported.
- For both Intel X710 10G and Intel XL710 40G NICs, the interface comes up as 40/x interface.
- Up to only 16 Intel X710/XL710 SR-IOV interfaces can be supported on a VPX instance.
Note:
For Intel X710 10G and Intel XL710 40G NICs to support IPv6, enable trust mode on the Virtual Functions (VFs) by typing the following command on the Citrix Hypervisor host:
# ip link set <PNIC> <VF> trust on
Example:
# ip link set ens785f1 vf 0 trust on
Prerequisites for Intel 82599 NIC
On the Citrix Hypervisor host, ensure that you:
- Add the Intel 82599 NIC (NIC) to the host.
-
Block list the
ixgbevf
driver by adding the following entry to the /etc/modprobe.d/blacklist.conf file:blacklist ixgbevf
-
Enable SR-IOV Virtual Functions (VFs) by adding the following entry to the /etc/modprobe.d/ixgbe file:
options ixgbe max_vfs=<number_of_VFs>
where <number_VFs> is the number of SR-IOV VFs that you want to create.
- Verify that SR-IOV is enabled in BIOS.
Note:
IXGBE driver version 3.22.3 is recommended.
Assign Intel 82599 SR-IOV VFs to the NetScaler VPX instance by using the Citrix Hypervisor host
To assign an Intel 82599 SR-IOV VFs to NetScaler VPX instance, follow these steps:
-
On the Citrix Hypervisor host, use the following command to assign the SR-IOV VFs to the NetScaler VPX instance:
xe host-call-plugin plugin=iovirt host-uuid=<Xen host UUID> fn=assign_free_vf args:uuid=<NetScaler VM UUID> args:ethdev=<interface name> args:mac=<Mac addr>
Where:
-
<Xen host UUID> is the UUID of the Citrix Hypervisor host.
-
<NetScaler VM UUID> is the UUID of the NetScaler VPX instance.
-
<interface name> is the interface for the SR-IOV VFs.
-
<MAC address > is the MAC address of the SR-IOV VF.
Note
Specify the MAC address that you want use in the args:Mac= parameter, if not specified, the
iovirt
script randomly generates and assigns a MAC address. Also, if you want to use the SR-IOV VFs in Link Aggregation mode, make sure that you specify the MAC address as 00:00:00:00:00:00. -
-
Boot the NetScaler VPX instance.
Unassign Intel 82599 SR-IOV VFs to the NetScaler VPX instance by using the Citrix Hypervisor host
If you have assigned an incorrect SR-IOV VFs or if you want to modify an assigned SR-IOV VFs, you need to unassign and reassign the SR-IOV VFs to the NetScaler VPX instance.
To unassign SR-IOV network interface assigned to a NetScaler VPX instance, follow these steps:
-
On the Citrix Hypervisor host, use the following command to assign the SR-IOV VFs to the NetScaler VPX instance and reboot the NetScaler VPX instance:
xe host-call-plugin plugin=iovirt host-uuid=<Xen_host_UUID> fn=unassign_all args:uuid=<Netscaler_VM_UUID>
Where:
-
<Xen_host_UUID> - The UUID of the Citrix Hypervisor host.
-
<Netscaler_VM_UUID> - The UUID of the NetScaler VPX instance
-
-
Boot the NetScaler VPX instance.
Assign Intel X710/XL710 SR-IOV VFs to the NetScaler VPX instance by using the Citrix Hypervisor host
To assign an Intel X710/XL710 SR-IOV VF to the NetScaler VPX instance, follow these steps:
-
Run the following command on the Citrix Hypervisor host to create a network.
xe network-create name-label=<network-name> <!--NeedCopy-->
Example:
xe network-create name-label=SR-IOV-NIC-18 8ee59b73-7319-6998-cd69-b9fa3e8d7503 <!--NeedCopy-->
-
Determine the PIF Universal Unique Identifier (UUID) of the NIC on which the SR-IOV network is to be configured.
xe pif-list uuid ( RO) : e2874343-f1de-1fa7-8fef-98547c348783 device ( RO): eth18 currently-attached ( RO): true VLAN ( RO): -1 network-uuid ( RO): f865bd85-44dd-b865-ab65-dcd6ae28c16e <!--NeedCopy-->
-
Configure the network as an SR-IOV network. The following command also returns the UUID of the newly created SR-IOV network:
xe network-sriov-create network-uuid=<network-uuid> pif-uuid=<physical-pif-uuid> <!--NeedCopy-->
Example:
xe network-sriov-create network-uuid=8ee59b73-7319-6998-cd69-b9fa3e8d7503 pif-uuid=e2874343-f1de-1fa7-8fef-98547c3487831629b44f-832a-084e-d67d-5d6d314d5e0f <!--NeedCopy-->
To get more information on the SR-IOV network parameters, run the following command:
[root@citrix-XS82-TOPO ~]# xe network-sriov-param-list uuid=1629b44f-832a-084e-d67d-5d6d314d5e0f uuid ( RO): 1629b44f-832a-084e-d67d-5d6d314d5e0f physical-PIF ( RO): e2874343-f1de-1fa7-8fef-98547c348783 logical-PIF ( RO): 85d52771-5814-c62d-45fa-f37b536144ff requires-reboot ( RO): false remaining-capacity ( RO): 32 <!--NeedCopy-->
-
Create a virtual interface (VIF) and attach it to the target VM.
xe vif-create device=0 mac=b2:61:fc:ae:00:1d network-uuid=8ee59b73-7319-6998-cd69-b9fa3e8d7503 vm-uuid=b507e8a6-f5ca-18eb-561d-308218a9dd68 3e1e2e58-b2ad-6dc0-61d4-1d149c9c6466 <!--NeedCopy-->
NOTE: The NIC index number of the VM must start with 0.
Use the following command to find the VM UUID:
[root@citrix-XS82-TOPO ~]# xe vm-list uuid ( RO): b507e8a6-f5ca-18eb-561d-308218a9dd68 name-label ( RW): sai-vpx-1 power-state ( RO): halted <!--NeedCopy-->
Remove Intel X710/XL710 SR-IOV VFs from the NetScaler instance by using the Citrix Hypervisor host
To remove an Intel X710/XL710 SR-IOV VF from a NetScaler VPX instance, follow these steps:
-
Copy the UUID for the VIF that you want to destroy.
-
Run the following command on the Citrix Hypervisor host to destroy the VIF.
xe vif-destroy uuid=<vif-uuid> <!--NeedCopy-->
Example:
[root@citrix-XS82-TOPO ~]# xe vif-destroy uuid=3e1e2e58-b2ad-6dc0-61d4-1d149c9c6466 <!--NeedCopy-->
Configure link aggregation on the SR-IOV interface
To use the SR-IOV virtual functions (VFs) in link aggregation mode, you need to disable spoof checking for virtual functions that you have created.
On the Citrix Hypervisor host, use the following command to disable spoof checking:
ip link set <interface_name> vf <VF_id> spoofchk off
Where:
- <interface_name> is the interface name.
- <VF_id> is the virtual function ID.
After disabling spoof checking for all the virtual function that you have created, restart the NetScaler VPX instance, and configure link aggregation. For instructions, see Configure link aggregation.
Important
While you are assigning the SR-IOV VFs to the NetScaler VPX instance, make sure that you specify MAC address 00:00:00:00:00:00 for the VFs.
Configure VLAN on the SR-IOV interface
You can configure VLAN on the SR-IOV virtual functions. For instructions, see Configuring a VLAN.
Important
Make sure that the Citrix Hypervisor host does not contain VLAN settings for the VF interface.
Share
Share
In this article
- Limitations
- Prerequisites for Intel 82599 NIC
- Assign Intel 82599 SR-IOV VFs to the NetScaler VPX instance by using the Citrix Hypervisor host
- Unassign Intel 82599 SR-IOV VFs to the NetScaler VPX instance by using the Citrix Hypervisor host
- Assign Intel X710/XL710 SR-IOV VFs to the NetScaler VPX instance by using the Citrix Hypervisor host
- Remove Intel X710/XL710 SR-IOV VFs from the NetScaler instance by using the Citrix Hypervisor host
- Configure link aggregation on the SR-IOV interface
- Configure VLAN on the SR-IOV interface
This Preview product documentation is Cloud Software Group Confidential.
You agree to hold this documentation confidential pursuant to the terms of your Cloud Software Group 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 Cloud Software Group product purchase decisions.
If you do not agree, select I DO NOT AGREE to exit.