Configure a Citrix ADC VPX instance to use VMXNET3 network interface
After you have installed and configured the Citrix ADC VPX instance on the VMware ESX, you can use the VMware vSphere web client to configure the virtual appliance to use VMXNET3 network interfaces.
To configure Citrix ADC VPX instances to use VMXNET3 network interfaces by using the VMware vSphere Web Client:
- In the vSphere Web Client, select Hosts and Clusters.
1. Upgrade the Compatibility setting of the Citrix ADC VPX instance to ESX, as follows:
1. Power off the Citrix ADC VPX instance.
1. Right-click the Citrix ADC VPX instance and select Compatibility > Upgrade VM Compatibility.
- In the Configure VM Compatibility dialog box, select ESXi 5.5 and later from the Compatible with drop-down list and click OK.
3. Right-click on the Citrix ADC VPX instance and click Edit Settings.
4. In the <virtual_appliance> - Edit Settings dialog box, click the CPU section.
5. In the CPU section, update the following:
- Number of CPUs
- Number of Sockets
- Reservations
- Limit
- Shares
Set the values as follows:
1. In the CPU drop-down list, select the number of CPUs to assign to the virtual appliance.
1. In the Cores per Socket drop-down list, select the number of sockets.
1. (Optional) In the CPU Hot Plug field, select or unselect the Enable CPU Hot Add checkbox.
Note: Citrix recommends accepting the default (disabled).
1. In the Reservation drop-down list, select the number that is shown as the maximum value.
1. In the Limit drop-down list, select the number that is shown as the maximum value.
1. In the Shares drop-down lists, select Custom and the number that is shown as the maximum value.
6. In the Memory section, update the following:
- Size of RAM
- Reservations
- Limit
- Shares
Set the values as follows:
1. In the RAM drop-down list, select the size of the RAM. It should be number of vCPUs x 2 GB. For example, if the number of vCPUs is 4, the RAM should be 4 x 2 GB = 8 GB.
Note: For an Advanced or Premium edition of the Citrix ADC VPX appliance, make sure that you allocate 4 GB of RAM to each vCPU. For example, if the number of vCPU is 4 then RAM = 4 x 4 GB = 16 GB.
b. In the Reservation drop-down list, enter the value for the memory reservation, and select the Reserve all guest memory (All locked) checkbox. The memory reservation should be the number of vCPUs x 2 GB. For example, if the number of vCPUs is 4, the memory reservation should be 4 x 2 GB = 8 GB.
Note: For an Advanced or Premium edition of the Citrix ADC VPX appliance, make sure that you allocate 4 GB of RAM to each vCPU. For example, if the number of vCPU is 4 then RAM = 4 x 4 GB = 16 GB.
c. In the Limit drop-down list, select the number that is shown as the maximum value.
d. In the Shares drop-down lists, select Custom and the number that is shown as the maximum value.
7. Add a VMXNET3 network interface. From the New device drop-down list, select Network and click Add.
8. In the New Network section, from the drop-down list, select the network interface, and do the following:
a. In the Adapter Type drop-down list, select VMXNET3.
Important
The default E1000 network interface and VMXNET3 cannot coexist, make sure that you remove the E1000 network interface and use VMXNET3 (0/1) as the management interface.
9. Click OK.
10. Power on the Citrix ADC VPX instance.
11. Once the Citrix ADC VPX instance powers on, you can use the following command to verify the configuration:
> show interface summary
The output should show all the interfaces that you configured:
> show interface summary
--------------------------------------------------------------------------------
Interface MTU MAC Suffix
--------------------------------------------------------------------------------
1 0/1 1500 00:0c:29:89:1d:0e NetScaler Vir...rface, VMXNET3
2 1/1 9000 00:0c:29:89:1d:18 NetScaler Vir...rface, VMXNET3
3 1/2 9000 00:0c:29:89:1d:22 NetScaler Vir...rface, VMXNET3
4 LO/1 9000 00:0c:29:89:1d:0e Netscaler Loopback interface
Note
After you add a VMXNET3 interface and restart the Citrix ADC VPX appliance, the VMWare ESX hypervisor might change the order in which the NIC is presented to the VPX appliance. So, network adapter 1 might not always remain 0/1, resulting in loss of management connectivity to the VPX appliance. To avoid this issue, change the virtual network of the network adapter accordingly.
This is a VMWare ESX hypervisor limitation.