-
Getting Started with Citrix NetScaler
-
Deploy a Citrix NetScaler VPX instance
-
Install a Citrix 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
-
-
Deploying NetScaler VPX Instances on AWS
-
Upgrade and downgrade a NetScaler appliance
-
-
-
-
-
-
Overriding Static Proximity Behavior by Configuring Preferred Locations
-
Example of a Complete Parent-Child Configuration Using the Metrics Exchange Protocol
-
Configuring Global Server Load Balancing for DNS Queries with NAPTR records
-
Using the EDNS0 Client Subnet Option for Global Server Load Balancing
-
-
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
-
Use source IP address of the client when connecting to the server
-
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 14: ShareFile wizard for load balancing Citrix ShareFile
-
-
-
-
-
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)
此内容已动态机器翻译。 放弃
このコンテンツは動的に機械翻訳されています。免責事項
This content has been machine translated dynamically.
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.
这篇文章已经过机器翻译.放弃
Translation failed!
Configure a NetScaler VPX instance to use SR-IOV network interfaces
You can use the Virtual Machine Manager to configure a NetScaler VPX instance running on Linux-KVM to use single root I/O virtualization (SR-IOV) network interfaces with Intel 82599 10G NIC and X710 10G and XL710 40G NICs.
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 NICs. The following features not supported.
Limitations for Intel 82599 NICs:
- L2 mode switching
- Admin partitioning (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 alteast 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 X710 10G and XL710 40G NICs:
- L2 mode switching.
- In a cluster, Jumbo Frames are not supported when the XL710 NIC is used as a data interface.
- Interface list re-orders 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 both XL710 and X710 NICs
- Up to 16 Intel XL710/X710 SRIOV or PCI Passthrough interfaces can be supported on a VPX instance.
Note: For IPv6 to work with X710 10G and XL710 40G NICs, you need to enable trust mode on the Virtual Functions (VFs) by typing the following command on the KVM host:
# ip link set <PNIC> <VF> trust on
For 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 about how to complete the corresponding tasks.
Task | 82599 NIC | X710 and XL710 NICs |
---|---|---|
1. Add the NIC to the KVM host. | - | - |
2. Download and install the latest Intel driver. | IXGBE driver | I40E driver |
3. Blacklist 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 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= |
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 are 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 82599 10G NIC.
Figure 2: Enable SR-IOV VFs on the KVM host for X710 10G and XL710 40G NICs.
Figure 3: Make the VFs persistent.
Configure a NetScaler VPX instance to use SR-IOV network interface
To configure NetScaler VPX instance to use SR-IOV network interface by using Virtual Machine Manager, complete these steps:
1. Power off the NetScaler VPX instance.
2. Select the NetScaler VPX instance and then select Open.
1. In the <virtual_machine on KVM> window, select the i icon.
1. Select Add Hardware.
5. In the Add New Virtual Hardware dialog box, do the following:
a. Select PCI Host Device.
b. In the Host Device section, select the VF you have created and click Finish.
Figure 4:VF for 82599 10G NIC
Figure 5: VF for XL710 NIC
6. Repeat Step 4 and 5 to add the VFs that you have created. 7. Power on the NetScaler VPX instance. 8. 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 82599.
Figure 7. Output summary for 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 link set \<interface\_name\> vf \<VF\_id\> spoofchk off*
Where:
- Interface_name – is the interface name.
- VF_id – is the Virtual Function id.
For 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, see Configure Link Aggregation.
Configuring VLAN on the SR-IOV Interface
You can configure VLAN on SR-IOV VFs. For detailed instructions, see Configuring 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.