Product Documentation

Limitations and Usage Guidelines

May 13, 2014
  • The clustering feature is not supported for VPX.
  • For HA to work as expected, associate a dedicated NATing device to management Interface or associate EIP to NSIP. For more information on NAT, in the AWS documentation, see NAT Instances.
  • Data traffic and management traffic should be segregated by using ENIs belonging to different subnets.
  • Only the NSIP address should be present on the management ENI.
  • If a NAT instance is used for security instead of assigning an EIP to the NSIP, appropriate VPC level routing changes are required. For instructions on making VPC level routing changes, in the AWS documentation, see "Scenario 2: VPC with Public and Private Subnets."
  • A VPX instance can be moved from one EC2 instance type to another (for example, from m3.large to an m3.xlarge).
  • For storage options for VPX on AWS, Citrix recommends EBS, because it is durable and the data is available even after it is detached from instance.
  • Dynamic addition of ENIs to VPX is not supported. You have to restart the VPX instance to apply the update. Citrix recommends you to stop the standalone or HA instance, attach the new ENI, and then restart the instance.
  • You can assign multiple IP addresses to an ENI. The maximum number of IP addresses per ENI is determined by the EC2 instance type, see EC2 Support for ENIs and IP Addresses.
  • Citrix recommends that you avoid using the enable and disable interface commands on NetScaler VPX interfaces.
  • Due to Amazon AWS limitations, these features are not supported:
    • IPV6
    • Gratuitous ARP(GARP)
    • L2 mode
    • Tagged VLAN
    • Dynamic Routing
    • Virtual MAC (VMAC)