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
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
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
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
配置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
Deploy NetScaler GSLB and domain-based services back-end autoscale with cloud load balancer
Configure address pools (IIP) for a NetScaler Gateway appliance
配置multiple IP addresses for a NetScaler VPX instance in standalone mode by using PowerShell commands
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
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
-
-
-
-
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
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.
这位目录这是maschinelle Ubersetzung, 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 NetScaler VPX instance to use SR-IOV network interfaces
You can configure a NetScaler VPX instance running on Linux-KVM platform using single root I/O virtualization (SR-IOV) with the following NICs:
- Intel 82599 10G
- Intel X710 10G
- Intel XL710 40G
- Intel X722 10G
This section describes how to:
- Configure a NetScaler VPX Instance to Use SR-IOV Network Interface
- Configure Static LA/LACP on the SR-IOV Interface
- Configure VLAN on the SR-IOV Interface
Limitations
Keep the limitations in mind while using Intel 82599, X710, XL710, and X722 NICs. The following features not supported.
Limitations for Intel 82599 NIC:
- L2 mode switching.
- 管理分区ing (shared VLAN mode).
- High availability (active-active mode).
- Jumbo frames.
- IPv6: You can configure only up to 30 unique IPv6 addresses in a VPX instance if you’ve at least one SR-IOV interface.
- VLAN configuration on Hypervisor for SRIOV VF interface through
ip link
command is not supported. - Interface parameter configurations such as speed, duplex, and autonegotiations are not supported.
Limitations for Intel X710 10G, Intel XL710 40G, and Intel X722 10G NICs:
- L2 mode switching.
- 管理分区ing (shared VLAN mode).
- 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.
- Interface name is 40/X for Intel X710 10G, Intel XL710 40G, and Intel X722 10G NICs
- Up to 16 Intel XL710/X710/X722 SRIOV or PCI passthrough interfaces can be supported on a VPX instance.
Note:For Intel X710 10G, Intel XL710 40G, and Intel X722 10G NICs to support IPv6, you need to enable trust mode on the Virtual Functions (VFs) by typing the following command on the KVM host:
# ip link set
trust on Example:
# ip link set ens785f1 vf 0 trust on
Prerequisites
Before you configure a NetScaler VPX instance to use SR-IOV network interfaces, complete the following prerequisite tasks. See the NIC column for details about how to complete the corresponding tasks.
Task | Intel 82599 NIC | Intel X710, XL710, and X722 NICs |
---|---|---|
1. Add the NIC to the KVM host. | - | - |
2. Download and install the latest Intel driver. | IXGBE driver | I40E driver |
3. Block list the driver on the KVM host. | Add the following entry in the /etc/modprobe.d/blacklist.conf file:blacklist ixgbevf . Use IXGBE driver version 4.3.15 (recommended). |
Add the following entry in the /etc/modprobe.d/blacklist.conf file:blacklist i40evf . Use i40e driver version 2.0.26 (recommended). |
4.Enable SR-IOV Virtual Functions (VFs) on the KVM host. In both the commands in the next two columns:number_of_VFs = the number of Virtual VFs that you want to create.device_name = the interface name. |
If you are using earlier version of kernel 3.8, then add the following entry to the /etc/modprobe.d/ixgbe file and restart the KVM host:options ixgbe max_vfs= . If you are using kernel 3.8 version or later, create VFs using the following command:echo . See example in figure 1. |
If you are using earlier version of kernel 3.8, then add the following entry to the /etc/modprobe.d/i40e.conf file and restart the KVM host:options i40e max_vfs= . If you are using kernel 3.8 version or later, create VFs using the following command:echo . See example in figure 2. |
5. Make the VFs persistent by adding the commands that you used to create VFs, to the rc.local file. | See example in figure 3. | See example in figure 3. |
Important
When you create the SR-IOV VFs, ensure that you do not assign MAC addresses to the VFs.
Figure 1: Enable SR-IOV VFs on the KVM host for Intel 82599 10G NIC.
Figure 2:Enable SR-IOV VFs on the KVM host for Intel X710 10G and XL710 40G NICs.
Figure 3:Enable SR-IOV VFs on the KVM host for Intel X722 10G NIC.
Figure 4: Make the VFs persistent.
Configure a NetScaler VPX instance to use SR-IOV network interface
To configure the NetScaler VPX instance to use SR-IOV network interface by using Virtual Machine Manager, complete these steps:
Power off the NetScaler VPX instance.
Select the NetScaler VPX instance and then select Open.
In the
window, select theiicon. SelectAdd Hardware.
In theAdd New Virtual Hardwaredialog box, do the following:
- Select PCI Host Device.
- In the Host Device section, select the VF you have created and click Finish.
Figure 4: VF for Intel 82599 10G NIC
Figure 5: VF for Intel XL710 40G NIC
Figure 6: VF for Intel X722 10G NIC
- Repeat Step 4 and 5 to add the VFs that you have created.
- Power on the NetScaler VPX instance.
After the NetScaler VPX instance powers on, use the following command to verify the configuration:
show interface summary
The output shows all the interfaces that you configured.
Figure 6: output summary for Intel 82599 NIC.
Figure 7. Output summary for Intel X710 and XL710 NICs.
Configure static LA/LACP on the SR-IOV interface
Important
When you are creating the SR-IOV VFs, ensure that you do not assign MAC addresses to the VFs.
To use the SR-IOV VFs in link aggregation mode, disable spoof checking for VFs that you have created. On the KVM host, use the following command to disable spoof checking:
* ip链路群\ \ _name \ > <接口vf \ < vf \ _id \ >热点ofchk off*
Where:
- Interface_name – is the interface name.
- VF_id – is the Virtual Function id.
Example:
After you disable spoof checking for all the VFs that you have created. Restart the NetScaler VPX instance and configure link aggregation. For detailed instructions, seeConfiguring Link Aggregation.
Configuring VLAN on the SR-IOV Interface
You can configure VLAN on SR-IOV VFs. For detailed instructions, seeConfiguring a VLAN.
Important
Ensure that the KVM host does not contain VLAN settings for the VF interface.
Share
Share
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.