-
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
-
-
Deploy a NetScaler VPX instance on Microsoft Azure
-
Configuring Multiple IP Addresses for a Standalone NetScaler Instance
-
Configuring an HA Setup with Multiple IP Addresses and NICs by Using PowerShell Commands
-
Configuring Address Pools (IIP) for a NetScaler Gateway Appliance
-
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!
Configure multiple IP addresses for a NetScaler VPX standalone instance
This section explains how to configure a standalone NetScaler VPX instance with multiple IP addresses, in Azure Resource Manager (ARM). The VPX instance can have one or more NIC attached to it, and each NIC can have one or more static or dynamic public and private IP addresses assigned to it. You can assign multiple IP addresses as NSIP, VIP, SNIP, and so on.
For more information, see the Azure documentation Assign multiple IP addresses to virtual machines using the Azure portal.
If you want to use PowerShell commands, see Configuring multiple IP addresses for a NetScaler VPX instance in standalone mode by using PowerShell commands.
Use case
In this use case, a standalone NetScaler VPX appliance is configured with a single NIC that is connected to a virtual network (VNET). The NIC is associated with three IP configurations (ipconfig), each servers a different purpose - as shown in the table.
IPconfig | Assocaited with | Purpose |
---|---|---|
ipconfig1 | Static public IP address; static private IP address | Serves management traffic |
ipconfig2 | Static public IP address; static private address | Serves client-side traffic |
ipconfig3 | Static private IP address | Communicates with back-end servers |
Note
IPConfig-3 is not associated with any public IP address.
Diagram: Topology
Here is the visual representation of the use case.
Note
In a multi-NIC, multi-IP Azure NetScaler VPX deployment, the private IP associated with the primary (first) IPConfig of the primary (first) NIC is automatically added as the management NSIP of the appliance. The remaining private IP addresses associated with IPConfigs need to be added in the VPX instance as a VIP or SNIP by using the “add ns ip” command, according to your requirement.
Before you begin
Before you begin, create a VPX instance by following the steps given at this link:
Configure a NetScaler VPX standalone instance
For this use case, the NSDoc0330VM VPX instance is created.
Procedure to configure multiple IP addresses for a NetScaler VPX instance in standalone mode.
For configuring multiple IP addresses for a NetScaler VPX appliance in standalone mode:
- Add IP addresses to the VM
- Configure NetScaler -owned IP addresses
Step 1: Add IP addresses to the VM
1. In the portal, click More services > type virtual machines in the filter box, and then click Virtual machines.
2. In the Virtual machines blade, click the VM you want to add IP addresses to. Click Network interfaces in the virtual machine blade that appears, and then select the network interface.
In the blade that appears for the NIC you selected, click IP configurations. The existing IP configuration that was assigned when you created the VM, ipconfig1, is displayed. For this use case, make sure the IP addresses associated with ipconfig1 are static. Next, create two more IP configurations: ipconfig2 (VIP) and ipconfig3 (SNIP).
To create additional ipconfigs, create Add.
In the Add IP configuration window, enter a Name, specify allocation method as Static, enter an IP address (192.0.0.5 for this use case), and enable Public IP address.
Note
Before adding a static private IP address, check for IP address availability and make sure the IP address belongs to the same subnet to which the NIC is attached.
Next, click Configure required settings to create a static public IP addresss for ipconfig2.
By default, public IPs are dynamic. To make sure that the VM always uses the same public IP address, create a static Public IP.
In the Create public IP address blade, add a Name, under Assignment click Static. And then click OK.
Note
Even when you set the allocation method to static, you cannot specify the actual IP address assigned to the public IP resource. Instead, it gets allocated from a pool of available IP addresses in the Azure location the resource is created in.
Follow the steps to add one more IP configuration for ipconfig3. Public IP is not mandatory.
Step 2: Configure NetScaler-owned IP addresses
Configure the NetScaler-owned IP addresses by using the GUI or the command “add ns ip.” For more information, see Configuring NetScaler-Owned IP Addresses.
You’ve now configured multiple IP addresses for a NetScaler VPX instance in standalone mode.
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.