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

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:

  • Between the instance and the back-end servers
  • Between the instance and the external hosts on the public internet.

Figure: A NetScaler LB vServer communicates with two back-end servers

localized image

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
Back-end server1
Back-end server2


Oracle assigns a static public IP address and a dynamic private IP. For more information, see Network Settings.

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.


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.

localized image

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.

localized image

  • Custom Attributes: None

localized image

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 (, a name, and a description. Click Create.

localized image

7. In the Configure IP Network Interface window, select the IP Network that you’ve created. Add a static IP address and select an auto-generated public IP address. Make sure the Default Gateway check box is selected.

localized image

8. Similarly 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:

9.  Configure IP Network Interface as follows:

NIC 1/2

  • Interface: eth1
  • IP Network: IPConfig1
  • Static IP Addresses:
  • Public IP Address: Auto Generated

NIC 1/3

  • Interface: eth2
  • IP Network: IPConfig2
  • Static IP Addresses:

Next, click the arrow to go to the Storage page.


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.

localized image

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.

localized image

12. Create a security protocol with which to create security rules. For this scenario, create a security protocol for HTTP.

localized image

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.

localized image

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 Configuring NetScaler-Owned IP Addresses
  • Configure the NetScaler instance as a load balancing virtual server. For more information, see [Set up basic load balancing.

Example: Here’s a sample LB configuration done by using the NetScaler CLI.

Add nsip

Add lb vs v1 http 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

The preceding configuration is based on the following assumptions:

Entity Private IP address
Back-end server1
Back-end server2