-
Getting Started with Citrix NetScaler
-
Deploy a Citrix NetScaler VPX instance
-
Install a 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
-
Provisioning the NetScaler Virtual Appliance with SR-IOV, on OpenStack
-
Configuring a NetScaler VPX Instance on KVM to Use OVS DPDK-Based Host Interfaces
-
-
Upgrade and downgrade a NetScaler appliance
-
-
-
-
-
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)
此内容已动态机器翻译。 放弃
このコンテンツは動的に機械翻訳されています。免責事項
This content has been machine translated dynamically.
This content has been machine translated dynamically.
This content has been machine translated dynamically.
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.
这篇文章已经过机器翻译.放弃
Translation failed!
Provision the NetScaler VPX instance by using the virsh program
The virsh program is a command line tool for managing VM Guests. Its functionality is similar to that of Virtual Machine Manager. It enables you to change a VM Guest’s status (start, stop, pause, and so on), to set up new Guests and devices, and to edit existing configurations. The virsh program is also useful for scripting VM Guest management operations.
To provision NetScaler VPX by using the virsh program, follow these steps:
-
Use the tar command to untar the the NetScaler VPX package. The NSVPX-KVM-*_nc.tgz package contains following components:
- The Domain XML file specifying VPX attributes [NSVPX-KVM-*_nc.xml]
- Check sum of NS-VM Disk Image [Checksum.txt]
- NS-VM Disk Image [NSVPX-KVM-*_nc.raw]
Example:
tar -xvzf NSVPX-KVM-10.1-117_nc.tgz NSVPX-KVM-10.1-117_nc.xml NSVPX-KVM-10.1-117_nc.raw checksum.txt
-
Copy the NSVPX-KVM-*_nc.xml XML file to a file named <DomainName>-NSVPX-KVM-*_nc.xml. The <DomainName> is also the name of the virtual machine. Example:
cp NSVPX-KVM-10.1-117_nc.xml NetScaler-VPX-NSVPX-KVM-10.1-117_nc.xml
-
Edit the <DomainName>-NSVPX-KVM-*_nc.xml file to specify the following parameters:
- name— Specify the name.
- mac— Specify the MAC address. Note: The domain name and the MAC address have to be unique.
- sourcefile— Specify the absolute disk-image source path. The file path has to be absolute. You can specify the path of the RAW image file or a QCOW2 image file.
If you want to specify a RAW image file, specify the disk image source path as shown in the following example:
Example: <name>NetScaler-VPX</name> <mac address=’52:54:00:29:74:b3’/> <source file=’/root/NSVPX-KVM-10.1-117_nc.raw’/>
Specify the absolute QCOW2 disk-image source path and define the driver type as qcow2, as shown in the following example:
Example: <name>NetScaler-VPX</name> <mac address=’52:54:00:29:74:b3’/> <driver name =’qemu’ type=’qcow2’/> <source file=’/root/NSVPX-KVM-10.1-117_nc.qcow’/>
-
Edit the <DomainName>-NSVPX-KVM-*_nc.xml file to configure the networking details:
- source dev— specify the interface.
- mode— specify the mode. The default interface is Macvtap Bridge.
Example: Mode: MacVTap Bridge Set target interface as ethx and mode as bridge Model type as virtio
<interface type='direct'> <mac address='52:54:00:29:74:b3'/> <source dev='eth0' mode='bridge'/> <target dev='macvtap0'/> <model type='virtio'/> <alias name='net0'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x03' function='0x0'/> </interface>
Here, eth0 is the physical interface attached to the VM.
-
Define the VM attributes in the <DomainName>-NSVPX-KVM-*_nc.xml file by using the following command: virsh define <DomainName>-NSVPX-KVM-*_nc.xml Example:
virsh define NS-VPX-NSVPX-KVM-10.1-117_nc.xml
-
Start the VM by entering following command: virsh start [<DomainName> <DomainUUID>] Example: virsh start NetScaler-VPX
-
Connect the Guest VM through the console virsh console [<DomainName> <DomainUUID> <DomainID> ] Example: virsh console NetScaler-VPX
Add additional interfaces to NetScaler VPX instance using virsh program
After you have provisioned the NetScaler VPX on KVM, you can add additional interfaces.
To add additional interfaces, follow these steps:
- Shut down the NetScaler VPX instance running on the KVM.
-
Edit the <DomainName>-NSVPX-KVM-*_nc.xml file using the command: virsh edit [<DomainName> <DomainUUID>] - In the <DomainName>-NSVPX-KVM-*_nc.xml file, append the following parameters:
-
For MacVTap
- Interface type— Specify the interface type as ‘direct’.
- Mac address— Specify the Mac address and make sure the MAC address is unique across the interfaces.
- source dev— Specify the interface name.
- mode— Specify the mode; the modes supported are - Bridge, VEPA, Private, and Pass-through
- model type— Specify the model type as virtio
Example:
Mode: MacVTap Pass-through
Set target interface as ethx, Mode as bridge, and model type as virtio
<interface type='direct'> <mac address='52:54:00:29:74:b3'/> <source dev='eth1' mode='passthrough'/> <model type='virtio'/> </interface>
Here eth1 is the physical interface attached to the VM.
-
For Bridge Mode
Note: Make sure that you have configured a Linux bridge in the KVM host, bound the physical interface to the bridge, and put the bridge in the UP state.
- Interface type— Specify the interface type as ‘bridge’.
- Mac address— Specify the Mac address and make sure the MAC address is unique across the interfaces.
- source bridge— Specify the bridge name.
- model type— Specify the model type as virtio
Example: Bridge Mode
<interface type='bridge'> <mac address='52:54:00:2d:43:a4'/> <source bridge='br0'/> <model type='virtio'/> </interface>
-
Share
Share
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.