-
Getting Started with Citrix NetScaler
-
Deploy a Citrix NetScaler VPX instance
-
Install a NetScaler VPX instance on VMware ESX
-
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)
此内容已经过机器动态翻译。 放弃
このコンテンツは動的に機械翻訳されています。免責事項
이 콘텐츠는 동적으로 기계 번역되었습니다. 책임 부인
Este texto foi traduzido automaticamente. (Aviso legal)
Questo contenuto è stato tradotto dinamicamente con traduzione automatica.(Esclusione di responsabilità))
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.(Aviso legal)
这篇文章已经过机器翻译.放弃
Questo articolo è stato tradotto automaticamente.(Esclusione di responsabilità))
Translation failed!
Install a NetScaler VPX instance on VMware ESX
Before installing NetScaler VPX instances on VMware ESX, make sure that VMware ESX Server is installed on a machine with adequate system resources. To install a NetScaler VPX instance on VMware ESXi , you use VMware vSphere client. The client or tool must be installed on a remote machine that can connect to VMware ESX through the network.
Important
You cannot install standard VMware Tools or upgrade the VMware Tools version available on a NetScaler VPX instance. VMware Tools for a NetScaler VPX instance are delivered as part of the NetScaler software release.
Prerequisites
Before you begin installing a virtual appliance, do the following:
- Install VMware ESX on hardware that meets the minimum requirements.
- Install VMware Client on a management workstation that meets the minimum system requirements.
- Download the NetScaler VPX appliance setup files.
- Label the physical network ports of VMware ESX.
- Obtain VPX license files. For more information about NetScaler VPX instance licenses, see the NetScaler VPX Licensing Guide at http://support.citrix.com/article/ctx131110.
VMware ESX hardware requirements
The following table describes the minimum system requirements for VMware ESX servers running NetScaler VPX ncore virtual appliance.
Table 1. Minimum system requirements for a VMware ESX server running a NetScaler VPX instance
Component | Requirement |
---|---|
- | 2 or more 64-bit x86 CPUs with virtualization assist (Intel-VT) enabled. Note that to run NetScaler VPX instance, hardware support for virtualization must be enabled on the VMware ESX host. Make sure that the BIOS option for virtualization support is not disabled. For more information, see your BIOS documentation. |
RAM | 3 GB |
Disk space | 40 GB of disk space available |
Network | One 1-Gbps NIC; Two 1-Gbps NICs recommended |
For information about installing VMware ESX, see http://www.vmware.com/.
The following table lists the virtual computing resources that the VMware ESX server must provide for each VPX ncore virtual appliance.
Table 2. Minimum virtual computing resources required for running a NetScaler VPX instance
Component | Requirement |
---|---|
Memory | 2 GB |
Virtual CPU (VCPU) | 2 |
Virtual network interfaces | 1. Note that with ESX, you can install a maximum of 10 virtual network interfaces if the VPX hardware is upgraded version to 7 or higher. |
Disk space | 20 GB |
Note that this is in addition to any disk requirements for the hypervisor.
For production use of VPX virtual appliance, the full memory allocation must be reserved. CPU cycles (in MHz) equal to at least the speed of one CPU core of the ESX should also be reserved.
VMware vSphere client system requirements
VMware vSphere is a client application that can run on Windows and Linux operating systems. It cannot run on the same machine as the VMware ESX server. The following table describes the minimum system requirements.
Table 3. Minimum system requirements for VMware vSphere client installation
Component | Requirement |
---|---|
Operating system | For detailed requirements from VMware, search for the “vSphere Compatibility Matrixes” PDF file at http://kb.vmware.com/. |
CPU | 750 megahertz (MHz); 1 gigahertz (GHz) or faster recommended |
RAM | 1 GB; 2 GB recommended |
Network Interface Card (NIC) | 100 Mbps or faster NIC |
OVF Tool 1.0 system requirements
OVF Tool is a client application that can run on Windows and Linux systems. It cannot run on the same machine as the VMware ESX server. The following table describes the minimum system requirements.
Table 4. Minimum system requirements for OVF tool installation
Component | Requirement |
---|---|
Operating system | For detailed requirements from VMware, search for the “OVF Tool User Guide” PDF file at http://kb.vmware.com/. |
CPU | 750 MHz minimum, 1 GHz or faster recommended |
RAM | 1 GB Minimum, 2 GB recommended |
Network Interface Card (NIC) | 100 Mbps or faster NIC |
For information about installing OVF, search for the “OVF Tool User Guide” PDF file at http://kb.vmware.com/.
Downloading the NetScaler VPX setup files
The NetScaler VPX instance setup package for VMware ESX follows the Open Virtual Machine (OVF) format standard. You can download the files from the Citrix website. You need a Citrix account to log on. If you do not have a Citrix account, access the home page at http://www.citrix.com, click the New Users link, and follow the instructions to create a new Citrix account.
Once logged on, navigate the following path from the Citrix home page:
Citrix.com > Downloads > NetScaler > Virtual Appliances.
Copy the following files to a workstation on the same network as the ESX server. Copy all three files into the same folder.
- NSVPX-ESX-<release number>-<build number>-disk1.vmdk (for example, NSVPX-ESX-9.3-39.8-disk1.vmdk)
- NSVPX-ESX-<release number>-<build number>.ovf (for example, NSVPX-ESX-9.3-39.8.ovf)
- NSVPX-ESX-<release number>-<build number>.mf (for example, NSVPX-ESX-9.3-39.8.mf )
Label the physical network ports of VMware ESX
Before installing a VPX virtual appliance, label of all the interfaces that you plan to assign to virtual appliances, in a unique format, for example, NS_NIC_1_1, NS_NIC_1_2, and so on. In large deployments, labeling in a unique format helps in quickly identifying the interfaces that are allocated to the VPX virtual appliance among other interfaces used by other virtual machines, such as Windows and Linux. Such labeling is especially important when different types of virtual machines share the same interfaces.
To label the physical network ports of VMware ESX server, follow these steps:
- Log on to the VMware ESX server by using the vSphere client.
- On the vSphere client, select the Configuration tab, and then click Networking.
- At the top-right corner, click Add Networking.
- In the Add Network Wizard, for Connection Type, select Virtual Machine, and then click Next.
- Scroll through the list of vSwitch physical adapters, and choose the physical port that will map to interface 1/1 on the virtual appliances.
- Enter the label of the interface, for example, NS_NIC_1_1 as the name of the vSwitch that will be associated with interface 1/1 of the virtual appliances.
- Click Next to finish the vSwitch creation. Repeat the procedure, beginning with step 2, to add any additional interfaces to be used by your virtual appliances. Label the interfaces sequentially, in the correct format (for example, NS_NIC_1_2).
Install a NetScaler VPX instance on VMware ESX
After you have installed and configured VMware ESX, you can use the VMware vSphere client to install virtual appliances on the VMware ESX server. The number of virtual appliances that you can install depends on the amount of memory available on the hardware that is running VMware ESX.
To install NetScaler VPX instances on VMware ESX by using VMware vSphere Client, follow these steps:
- Start the VMware vSphere client on your workstation.
- In the IP address / Name text box, type the IP address of the VMware ESX server that you want to connect to.
- In the User Name and Password text boxes, type the administrator credentials, and then click Login.
- On the File menu, click Deploy OVF Template.
- In the Deploy OVF Template dialog box, in Deploy from file, browse to the location at which you saved the NetScaler VPX instance setup files, select the .ovf file, and click Next.
- Map the networks shown in the virtual appliance OVF template to the networks that you configured on the ESX host. Click Nextto start installing a virtual appliance on VMware ESX. When installation is complete, a pop-up window informs you of the successful installation.
- You are now ready to start the NetScaler VPX instance. In the navigation pane, select the NetScaler VPX instance that you have just installed and, from the right-click menu, select Power On. Click the Consoletab to emulate a console port.
- If you want to install another virtual appliance, repeat steps 4 through 6.
Note
By default, the NetScaler VPX instance uses E1000 network interfaces.
After the installation, you can use vSphere client or vSphere Web Client to manage virtual appliances on VMware ESX.
Note
For the VLAN tagging feature to work,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 http://www.vmware.com/pdf/esx3_vlan_wp.pdf.
Share
Share
In this article
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.