Product Documentation

Installing NetScaler Virtual Appliances on Linux-KVM Platform

Mar 09, 2015

To set up NetScaler VPX for the Linux-KVM platform, you can use the graphical Virtual Machine Manager (Virt-Manager) application. If you prefer the Linux-KVM command line, you can use the virsh program.

The host Linux operating system must be installed on suitable hardware by using virtualization tools such as KVM Module and QEMU. The number of virtual machines (VMs) that can be deployed on the hypervisor depends on the application requirement and the chosen hardware.

After you provision a NetScaler virtual appliance, you can add additional interfaces.

Limitations and Usage Guidelines

General Recommendations

To avoid unpredictable behavior, apply the following recommendations:

  • Do not change the MTU of the vnet interface associated with the NetScaler VM. Shut down the NetScaler VM before modifying any configuration parameters, such as Interface modes or CPU.
  • Do not force a shutdown of the NetScaler VM. That is, do not use the Force off command.
  • Any configurations done on the host Linux might or might not be persistent, depending on your Linux distribution settings. You can choose to make these configurations persistent to ensure consistent behavior across reboots of host Linux operating system.
  • The .raw file has to be unique for each of the NetScaler VPX instance provisioned.

Limitations

A NetScaler VPX setup on the Linux-KVM platform has the following limitations:

  • VLAN tagging is not supported on Netscaler-VPX operating on MacVTap-Bridge, MacVTap-Private, MacVTap-VEPA, or MacVTap-Passthrough interface Mode.
  • L2 mode is not supported on Netscaler VPX running on a Linux-KVM host.
  • Interface parameter configurations, such as speed, duplex, and auto-negotiation are not supported
  • Interface events, such as link UP and DOWN are not supported. Because these events are not reported, the following features are not supported:
    • Static link aggregation
    • Dynamic route advertisement for connected networks
    • Monitored static routes
    • Avoiding split brains in a high availability (HA) setup
    • Partial failure detection in an HA setup
  • LACP is not supported on Netscaler VPX operating in Bridge, MacVTap-Bridge, MacVTap-Private, or MacVTap-VEPA interface mode.
  • Live Migration of the Netscaler VPX running on KVM is not supported.
  • When a VLAN tagged packet destined for a guest VM is received on an Intel IXGBE 10G interface of a KVM host running on Red Hat Enterprise Linux (RHEL) 6.4, the IXGBE driver of this distribution strips the VLAN tag before sending it to the guest VM (in this case, NetScaler VPX). Because of this host behavior, a NetScaler VPX instance running on RHEL6.4 does not receive the intended VLAN tagged packets.