Support matrix and usage guidelines

This document lists the different hypervisors and features supported on a NetScaler VPX instance as well as the limitations and usage guidelines that apply.

• Table 1-6 list the different supported hypervisors.
• Table 7 lists the different VPX features and limitations for the different hypervisors supported on a NetScaler VPX instance.
• Table 8 lists the supported web browsers that allow you access the GUI and Dashboard.

Table 1. VPX instance on XenServer

Table 2. VPX instance on VMware ESX server

Table 3. VPX on Microsoft Hyper-V

Table 4. VPX instance on generic KVM

Note: The VPX instance is qualified for hypervisor release versions mentioned in table 1 - 4, and not for patch releases within a version. However, the VPX instance is expected to work seamlessly with patch releases of a supported version. If it does not, log a support case for troubleshooting and debugging.

Table 5. VPX instance on AWS

Table 6. VPX instance on Azure

Table 7. VPX feature matrix

*Clustering support is available on SRIOV for client- and server-facing interfaces and not for the backplane.

**Interface DOWN events are not recorded in NetScaler VPX instances.

For Static LA, traffic might still be sent on the interface whose physical status is DOWN.

For LACP, peer device knows interface DOWN event based on LACP timeout mechanism.

Short timeout: 3 seconds

Long timeout: 90 seconds

For LACP, interfaces should not be shared across VMs.

For Dynamic routing, convergence time depends on the Routing Protocol since link events are not detected.

Monitored static Route functionality fails if monitors are not bound to static routes since Route state depends on the VLAN status. The VLAN status depends on the link status.

Partial failure detection does not happen in high availability if there is link failure. High availability-split brain condition might happen if there is link failure.

***When any link event (disable/enable, reset) is generated from a VPX instance, the physical status of the link does not change. For static LA, any traffic initiated by the peer gets dropped on the instance.

For LACP, peer device knows interface DOWN event based on LACP timeout mechanism.

Short timeout: 3 seconds

Long timeout: 90 seconds

For LACP, interfaces should not be shared across VMs.

• For the VLAN tagging feature to work, do the following:

On the VMware ESX, set the port group’s VLAN ID to 1 - 4095 on the vSwitch of VMware ESX server. For more information about setting a VLAN ID on the vSwitch of VMware ESX server, see pdf.

Table 8. Supported browsers