-
Getting Started with Citrix NetScaler
-
Deploy a Citrix NetScaler VPX instance
-
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)
此内容已动态机器翻译。 放弃
このコンテンツは動的に機械翻訳されています。免責事項
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!
Scenario
Important
NetScaler VPX instance on Oracle is in Limited Availability. If you’d like to participate, contact your local sales team or request a call at
https://www.citrix.com/products/netscaler-adc/form/inquiry/
.
This scenario illustrates how to deploy a NetScaler VPX standalone instance in Oracle Public Cloud (OPC). The user creates a standalone VPX instance with multiple NICs. The instance, which is configured as a load balancing virtual server, communicates with back-end servers (the server farm). For this configuration, you have to set up the required communication routes between the instance and the back-end servers, and between the instance and the external hosts on the public Internet.
This scenario illustrates how to deploy a NetScaler VPX standalone instance in Oracle Public Cloud (OPC). As a user, create a standalone VPX instance with multiple NICs. The instance, which is configured as a load balancing virtual server, communicates with back-end servers (the server farm). For this configuration, you have to set up the required communication routes:
You create three NICs. Each NIC can be configured with a pair of IP addresses (public and private). The NICs serve the following purposes.
NIC | Purpose | Associated with |
---|---|---|
NIC 1/1 | Serves management traffic (NSIP) | Public IP address and private IP address |
NIC 1/2 | Serves client-side traffic (VIP) | Public IP address and private IP address |
NIC 1/3 | Communicates with back-end servers (SNIP) | Private IP address(Public IP is not mandatory) |
The following public IP addresses are used in this example.
Entity | Public IP address |
---|---|
NSIP | 192.168.30.2 |
VIP | 192.168.10.2 |
SNIP | 192.168.20.2 |
Back-end server1 | 192.168.20.10 |
Back-end server2 | 192.168.20.11 |
Note
Oracle assigns a static public IP address and a dynamic private IP address. For more information on Network Settings, see the Oracle docs site.
To create the required instances and set up the required security rules for this scenario, complete the following tasks:
1. From the Oracle Web Console, click Create Instance and click Private Images.
2. Select the required image and click Review and Create. The Create Instance wizard starts, displaying the default settings.
Note
If you click Create without going through the pages in the wizard, an image with the default settings is created. No SSH keys are associated with it. So make sure you enter the necessary details on each page of the wizard.
While deploying a NetScaler VPX instance on Oracle Public Cloud, an SSH key pair is mandatory. However, the user cannot use the key pair to log on to the VPX instance. The user must use nsroot as the user name and as the password to log on.
3. On the Shape page, select the shape that you want to use. The shape specifies the OCPU and memory resources to be allocated to the instance. Click the arrow next to the Review and Create tab on the upper right corner to go to the Instance page. In this scenario, you create an instance with 1 OCPU.
4. On the Instance page, select or enter the following, and then go to the next page:
- High Availability Policy: Active
Name: \<Instance name\>
- Label: default value
- Description: None
- Tags: None
- SSH Keys: Add the SSH key that you created in the Prerequisites section.
- Custom Attributes: None
5. On the Network page, clear the Shared Network check box and click Configure Interface.
6. In the Configure IP Network Interface window, click Create IP Network to create an IP network for the management IP (NSIP). Add an IP Address Prefix (192.168.30.0/24), a name, and a description. Click Create
7. In the Configure IP Network Interface window, select the IP Network that you’ve just created, add a static IP address, and select an auto-generated public IP address. Make sure the Default Gateway check box is selected.
8. Similary create IP networks for NIC 1/2 and NIC 1/3 as follows.
NIC 1/2
- Name: IPConfig1 (for NIC 1/2)
- IP Address Prefix: 192/168.10.0/24
NIC 1/3
- Name: IPConfig2 (for NIC 1/3)
- IP Address Prefix: 192.168.20.0/24
9. Configure IP Network Interface as follows:
NIC 1/2
- Interface: eth1
- IP Network: IPConfig1
- Static IP Addresses: 192.168.10.2
- Public IP Address: Auto Generated
NIC 1/3
- Interface: eth2
- IP Network: IPConfig2
- Static IP Addresses: 192.168.20.2
Next, click the arrow to go to the Storage page.
Note
For NIC 1/2 and 1/3, do not select the Default Gateway check box.
8. On the Storage page, you can attach existing storage volumes to your instance, if necessary, or create storage volumes and attach them to the instance. In this example, select the default storage.
9. On the Review page, verify the information that you’ve entered, and then click Create.
10. Monitor the status of the instance. When the status is shown as “Running,” the instance is ready. Follow the same steps to create two back-end servers.
11. From the Oracle web console, click IP Network > IP Address Prefix Sets > Create IP Network. Specify the name and the IP Address Prefix Set.
12. Create a security protocol with which to create security rules. You’ll create a security protocol for HTTP.
13. Create a security rule to allow external traffic to access the NetScaler Instance. For this scenario, create a rule to allow HTTP requests from external traffic to the NetScaler instance.
Now you can log on to your instance by using either GUI or SSH and complete the initial configuration. To find the oracle-assigned NetScaler management IP address, in the Oracle web console, click Instances. To the find the NetScaler management IP address pair, click the instance details icon for the instance that you created.
You can use SSH to log on to your instance as an nsroot user, by using the following command:
ssh -i ./<private key> nsroot@<ip address>
When prompted, type the password nsroot.
Next, configure the NetScaler-owned IP addresses and the NetScaler instance as a load balancing virtual server:
- Configure the NetScaler-owned IP addresses by using the NetScaler GUI or the command “add ns ip.” For more information, see https://docs.citrix.com/en-us/netscaler/11-1/networking/ip-addressing/configuring-netscaler-owned-ip-addresses.html
- Configure the NetScaler instance as a load balancing virtual server. For more information, see https://docs.citrix.com/en-us/netscaler/11-1/load-balancing/load-balancing-setup.html .
Example: Here’s a sample LB configuration done by using the NetScaler CLI.
Add nsip 192.168.20.2 255.255.255.0
Add lb vs v1 http 192.168.10.2 80
Add service s[1-2] 192.168.20.[10-11] http 80
Bind lb vs v1 s[1-2]
Add vlan 10
Bind vlan 10 –Ifnum 1/3 –Ipaddress 192.168.20.2 255.255.255.0
The preceding configuration is based on the following assumptions:
Entity | Private IP address |
---|---|
VIP | 192.168.10.2 |
SNIP | 192.168.20.2 |
Back-end server1 | 192.168.20.10 |
Back-end server2 | 192.168.20.11 |
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.