-
Getting Started with Citrix ADC
-
Deploy a Citrix ADC VPX instance
-
Install a Citrix ADC VPX instance on Microsoft Hyper-V servers
-
Install a Citrix ADC VPX instance on Linux-KVM platform
-
Prerequisites for Installing Citrix ADC VPX Virtual Appliances on Linux-KVM Platform
-
Provisioning the Citrix ADC Virtual Appliance by using OpenStack
-
Provisioning the Citrix ADC Virtual Appliance by using the Virtual Machine Manager
-
Configuring Citrix ADC Virtual Appliances to Use SR-IOV Network Interface
-
Configuring Citrix ADC Virtual Appliances to use PCI Passthrough Network Interface
-
Provisioning the Citrix ADC Virtual Appliance by using the virsh Program
-
Provisioning the Citrix ADC Virtual Appliance with SR-IOV, on OpenStack
-
Configuring a Citrix ADC VPX Instance on KVM to Use OVS DPDK-Based Host Interfaces
-
-
Deploy a Citrix ADC VPX instance on Microsoft Azure
-
Network architecture for Citrix ADC VPX instances on Microsoft Azure
-
Configure multiple IP addresses for a Citrix ADC VPX standalone instance
-
Configure a high-availability setup with multiple IP addresses and NICs
-
Configure a high-availability setup with multiple IP addresses and NICs by using PowerShell commands
-
Configure HA-INC nodes by using the Citrix high availability template with Azure ILB
-
Configure address pools (IIP) for a Citrix Gateway appliance
-
-
Upgrade and downgrade a Citrix ADC appliance
-
Solutions for Telecom Service Providers
-
Load Balance Control-Plane Traffic that is based on Diameter, SIP, and SMPP Protocols
-
Provide Subscriber Load Distribution Using GSLB Across Core-Networks of a Telecom Service Provider
-
Authentication, authorization, and auditing application traffic
-
Configuring authentication, authorization, and auditing policies
-
Configuring Authentication, authorization, and auditing with commonly used protocols
-
Use an on-premises Citrix Gateway as the identity provider for Citrix Cloud
-
Troubleshoot authentication issues in Citrix ADC and Citrix Gateway with aaad.debug module
-
-
-
-
-
-
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
-
Retrieve location details from user IP address using geolocation database
-
Use source IP address of the client when connecting to the server
-
Use client source IP address for backend communication in a v4-v6 load balancing configuration
-
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 12: Configure Citrix Virtual Desktops for load balancing
-
Use case 13: Configure Citrix Virtual Apps for load balancing
-
Use case 14: ShareFile wizard for load balancing Citrix ShareFile
-
-
-
-
-
Authentication and authorization
-
-
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 Citrix ADC 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!
Provision the Citrix ADC VPX instance by using the Virtual Machine Manager
The Virtual Machine Manager is a desktop tool for managing VM guests. It enables you to create new VM guests and various types of storage, and manage virtual networks. You can access the graphical console of VM guests with the built-in VNC viewer and view performance statistics, either locally or remotely.
After installing your preferred Linux distribution, with KVM virtualization enabled, you can proceed with provisioning virtual machines.
While using the Virtual Machine Manager to provision a Citrix ADC VPX instance, you have two options:
- Enter the IP address, gateway, and netmask manually
- Assign the IP address, gateway, and netmask automatically (auto-provisioning)
You can use two kinds of images to provision a Citrix ADC VPX instance:
- RAW
- QCOW2
You can convert a Citrix ADC VPX RAW image to a QCOW2 image and provision the Citrix ADC VPX instance. To convert the RAW image to a QCOW2 image, type the following command:
qemu-img convert -O qcow2 original-image.raw image-converted.qcow
For example: qemu-img convert -O qcow2 NSVPX-KVM-11.1-12.5_nc.raw NSVPX-KVM-11.1-12.5_nc.qcow
A typical Citrix ADC VPX deployment on KVM includes the following steps:
- Checking prerequisites for Auto-Provisioning a Citrix ADC VPX Instance
- Provisioning the Citrix ADC VPX Instance by Using a RAW Image
- Provisioning the Citrix ADC VPX Instance by Using a QCOW2 Image
- Adding Additional Interfaces to a VPX Instance by using Virtual Machine Manager
Check prerequisites for auto-provisioning a Citrix ADC VPX instance
Auto-provisioning is an optional feature, and it involves using data from the CDROM drive. If this feature is enabled, you need not enter the management IP address, network mask, and default gateway of the Citrix ADC VPX instance during initial setup. You need to complete the following tasks before you can auto-provision a VPX instance:
- Create a customized Open Virtualization Format (OVF) XML file or userdata file.
- Convert the OVF file into an ISO image by using an online application (for example PowerISO).
- Mount the ISO image on the the KVM host by using any secure copy (SCP)-based tools.
Sample OVF XML file:
Here’s is an example of the contents an OVF XML file, which you can use as a sample to create your file.
<?xml version=”1.0” encoding=”UTF-8” standalone=”no”?>
<Environment xmlns:oe=”http://schemas.dmtf.org/ovf/environment/1"
xmlns:xsi=”http://www.w3.org/2001/XMLSchema-instance"
oe:id=””
xmlns=”http://schemas.dmtf.org/ovf/environment/1"
xmlns:cs=”http://schemas.citrix.com/openstack"\>
<PlatformSection>
<Kind></Kind>
<Version>2016.1</Version>
<Vendor>VPX</Vendor>
<Locale>en</Locale>
</PlatformSection>
<PropertySection>
<Property oe:key=”com.citrix.netscaler.ovf.version” oe:value=”1.0”/>
<Property oe:key=”com.citrix.netscaler.platform” oe:value=”NSVPX”/>
<Property oe:key=”com.citrix.netscaler.orch_env” oe:value=”KVM”/>
<Property oe:key=”com.citrix.netscaler.mgmt.ip” oe:value=”10.1.2.22”/>
<Property oe:key=”com.citrix.netscaler.mgmt.netmask” oe:value=”255.255.255.0”/>
<Property oe:key=”com.citrix.netscaler.mgmt.gateway” oe:value=”10.1.2.1”/>
</PropertySection>
</Environment>
In the OVF XML file above, “PropertySection” is used for NetScaler networking configuration. When you create the file, specify values for the parameters that are highlighted at the end of the example:
- Management IP address
- Netmask
- Gateway
Important
If the OVF file is not properly XML formatted, the VPX instance is assigned the default network configuration, not the values specified in the file.
Provision the Citrix ADC VPX instance by using a RAW image
The Virtual Machine Manager enables you to provision a Citrix ADC VPX instancy by using a RAW image.
To provision a Citrix ADC VPX instance by using the Virtual Machine Manager, follow these steps:
-
Open the Virtual Machine Manager (Application > System Tools > Virtual Machine Manager) and enter the logon credentials in the Authenticate window.
-
Click the icon or right-click localhost (QEMU) to create a new Citrix ADC VPX instance.
-
In the Name text box, enter a name for the new VM (for example, NetScaler-VPX).
-
In the New VM window, under “Choose how you would like to install the operating system,” select Import existing disk image, and then and click Forward.
-
In the Provide the existing storage path field, navigate the path to the image. Choose the OS type as UNIX and Version as FreeBSD 6.x. Then, click Forward.
-
Under Choose Memory and CPU settings select the following settings, and then click Forward:
- Memory (RAM)— 2048 MB
- CPUs— 2
-
Select the Customize configuration before install check box. Optionally, under Advanced options you can you can customize the MAC address. Make sure the Virt Type selected is kvm and the Architecture selected is x86_64. Click Finish.
-
Select a NIC and provide the following configuration:
- Source device— ethX macvtap or Bridge
- Device model— virtio
- Source mode— Bridge
-
Click Apply.
-
If you want to auto-provision the VPX instance, see the section “Enabling Auto-Provisioning by Attaching a CDROM Drive” in this document. Otherwise, click Begin Installation. After you have provisioned the Citrix ADC VPX on KVM, you can add additional interfaces.
Provision the Citrix ADC VPX instance by using a QCOW2 image
Using the Virtual Machine Manager, you can provision the Citrix ADC VPX instance by using a QCOW2 image.
To provision a Citrix ADC VPX instance by using a QCOW2 image, follow these steps:
- Follow step 1 to step 8 in Provision the Citrix ADC VPX instance by using a RAW image.
Note: Ensure that you select qcow2 image in step 5 . - Select Disk 1 and click Advanced options.
- Select qcow2 from the Storage format drop-down list.
4. Click Apply, and then click Begin Installation. After you have provisioned the Citrix ADC VPX on KVM, you can add additional interfaces.
Enable auto-provisioning by attaching a CDROM drive
1. Click Add Hardware > Storage > Device type > CDROM device.
2. Click Manage and selec the correct ISO file that you mounted in the “Prerequisites for Auto-Provisioning a Citrix ADC VPX Instance” section, and click Finish. A new CDROM under Resources on your Citrix ADC VPX instance is created.
3. Power on the VPX instance, and it auto-provisions with the network configuration provided in the OVF file, as shown in the example screen capture.
4. If auto-provision fails, the instance comes up with the default IP address (192.168.100.1). In that case, you need to complete the initial configuration manually. For more information, see Configuring a NetScaler for the First Time.
Add additional interfaces to the Citrix ADC VPX instance by using Virtual Machine Manager
After you have provisioned the NetScaler VPX instance on KVM, you can add additional interfaces.
To add additional interfaces, follow these steps.
-
Shut down the NetScaler VPX instance running on the KVM.
-
Right-click the VPX instance and choose Open from the pop-up menu.
-
Click the icon in the header to view the virtual hardware details.
-
Click Add Hardware. In the Add New Virtual Hardware window, select Network from the navigation menu.
-
In Host Device field, select the physical interface type. The host device type can be either Bridge or MacVTap. In case of MacVTap, four modes possible are VEPA, Bridge, Private and Pass-through.
- For Bridge
-
Host device— Select the “Specify shared device name” option.
-
Provide the Bridge name that is configured in the KVM host.
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.
-
Device model—virtio.
-
Click Finish.
-
- For MacVTap
-
Host device—Select the physical interface from the menu.
-
Device model—virtio.
-
Click Finish. You can view the newly added NIC in the navigation pane.
-
Select the newly added NIC and select the Source mode for this NIC. The available modes are VEPA, Bridge, Private, and Passthrough. For more details on the interface and modes, see Source Interface and Modes.
-
Click Apply.
-
- For Bridge
-
If you want to auto-provision the VPX instance, see the section “Adding a Config Drive to Enable Auto-Provisioning” in this document. Otherwise, power on the VPX instance to complete the initial configuration manually.
Important
Interface parameter configurations such as speed, duplex, and autonegotiation are not supported.
Share
Share
In this article
- Check prerequisites for auto-provisioning a Citrix ADC VPX instance
- Provision the Citrix ADC VPX instance by using a RAW image
- Provision the Citrix ADC VPX instance by using a QCOW2 image
- Enable auto-provisioning by attaching a CDROM drive
- Add additional interfaces to the Citrix ADC VPX instance by using Virtual Machine Manager
This Preview product documentation is Cloud Software Group Confidential.
You agree to hold this documentation confidential pursuant to the terms of your Cloud Software Group 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 Cloud Software Group product purchase decisions.
If you do not agree, select I DO NOT AGREE to exit.