Product Documentation
ADC
Current Release 13.1 13.0 12.1
View PDF

Deploy a VPX high-availability pair with private IP address on Google Cloud Platform

January 11, 2023
Contributed by:
C S

You can deploy a VPX high-availability pair on GCP using private IP address. The client IP (VIP) must be configured as alias IP address on the primary node. Upon failover, the Client IP address is moved to the secondary node, for the traffic to resume.

For more information on high availability, see高可用性.

Before you start

  • Read the Limitation, Hardware requirements, Points to note mentioned inDeploy a Citrix ADC VPX instance on Google Cloud Platform. This information applies to high availability deployments also.
  • EnableCloud Resource Manager APIfor your GCP project.

  • Allow full access to all Cloud APIs while creating the instances.Full access cloud API

  • Ensure that your GCP service account has the following IAM permissions:

    REQUIRED_INSTANCE_IAM_PERMS = [" compute.forwardingRules.list”, “compute.forwardingRules.setTarget”, “compute.instances.setMetadata”, "compute.instances.get", "compute.instances.list", "compute.instances.updateNetworkInterface", “compute.targetInstances.list”, “compute.targetInstances.use”, "compute.zones.list", ]

  • If you have configured external IP addresses on an interface other than the management interface, ensure that your GCP service account has the following additional IAM permissions:

    REQUIRED_INSTANCE_IAM_PERMS = [ "compute.addresses.use" "compute.instances.addAccessConfig", "compute.instances.deleteAccessConfig", "compute.networks.useExternalIp", "compute.subnetworks.useExternalIp", ]

  • If your VMs do not have internet access, you must enablePrivate Google Accesson the management subnet.Private google access

  • If you have configured GCP forwarding rules on the primary node, read the limitations and requirements mentioned inForwarding rules support for VPX high-availability pair on GCPto update them to new primary on failover.

How to deploy a VPX high availability pair on Google Cloud Platform

Here is a summary of the high availability deployment steps:

  1. Create VPC networks in the same region. For example, Asia-east.
  2. Create two VPX instances (primary and secondary nodes) on the same region. They can be in the same zone or different zones. For example Asia east-1a and Asia east-Ib.
  3. Configure high availability settings on both instances by using the Citrix ADC GUI or ADC CLI commands.

Step 1. Create VPC networks

Create VPC networks based on your requirements. Citrix recommends you to create three VPC networks for associating with management NIC, client NIC, and server NIC.

To create a VPC network, perform these steps:

  1. Log on theGoogle console > Networking > VPC network > Create VPC Network.
  2. Complete the required fields, and clickCreate.

For more information, see theCreate VPC Networkssection inDeploy a Citrix ADC VPX instance on Google Cloud Platform.

Step 2. Create two VPX instances

Create two VPX instances by following the steps given inScenario: deploy a multi-NIC, multi-IP standalone VPX instance.

Important:

Assign a client alias IP address to the primary node. Do not use the internal IP address of the VPX instance to configure the VIP.

To create a client alias IP address, perform these steps:

  1. Navigate to the VM instance and clickEdit.

  2. In theNetwork Interfacewindow, edit the client interface.

  3. In theAlias IP rangefield, enter the client alias IP address.

Client alias IP address

Network interfaces

After the failover, when the old primary becomes the new secondary, the alias IP addresses move from the old primary and is attached to the new primary.

After you have configured the VPX instances, you can configure the Virtual (VIP) and Subnet IP (SNIP) addresses. For more information, seeConfiguring Citrix ADC-owned IP addresses.

Step 3. Configure high availability

After you’ve created the instances on Google Cloud Platform, you can configure high availability by using the Citrix ADC GUI or CLI.

Configure high availability by using the GUI

Step 1. Set up high availability in INC Enabled mode on both the nodes.

On theprimary node, perform the following steps:

  1. Log on to the instance with user namensrootand instance ID of the node from GCP console as the password.
  2. Navigate toConfiguration > System > High Availability > Nodes, and clickAdd.
  3. In theRemote Node IP addressfield, enter the private IP address of the management NIC of the secondary node.
  4. Select theTurn on INC (Independent Network Configuration) mode on self nodecheck box.
  5. ClickCreate.

On thesecondary node, perform the following steps:

  1. Log on to the instance with user namensrootand instance ID of the node from GCP console as the password.
  2. Navigate toConfiguration > System > High Availability > Nodes, and clickAdd.
  3. In theRemote Node IP addressfield, enter the private IP address of the management NIC of the primary node.
  4. Select theTurn on INC (Independent Network Configuration) mode on self nodecheck box.
  5. ClickCreate.

Before you proceed further, ensure that the Synchronization state of the secondary node is shown asSUCCESSin theNodespage.

Secondary-node synchronization state

Note

After the secondary node is synchronized with the primary node, the secondary node has the same log-on credentials as the primary node.

Step 2. Add Virtual IP address and Subnet IP address on both the nodes.

On the primary node, perform the following steps:

  1. Navigate toSystem > Network > IPs > IPv4s, and clickAdd.
  2. To create a client alias IP (VIP) address:
    1. Enter the Alias IP address and netmask configured for the client subnet in the VM instance.
    2. In theIP Typefield, selectVirtual IPfrom the drop-down menu.
    3. ClickCreate.
  3. To create a server IP (SNIP) address:
    1. Enter the internal IP address of the server-facing interface of the primary instance and netmask configured for the server subnet.
    2. In theIP Typefield, selectSubnet IPfrom the drop-down menu.
    3. ClickCreate.

    Create client and server IP address for primary

On the secondary node, perform the following steps:

  1. Navigate toSystem > Network > IPs > IPv4s, and clickAdd.
  2. To create a client alias IP (VIP) address:
    1. Enter the Alias IP address and netmask configured for the client subnet on the primary VM instance.
    2. In theIP Typefield, selectSubnet IPfrom the drop-down menu.
    3. ClickCreate.
  3. To create a server IP (SNIP) address:
    1. Enter the internal IP address of the server-facing interface of the secondary instance and netmask configured for the server subnet.
    2. In theIP Typefield, selectSubnet IPfrom the drop-down menu.
    3. ClickCreate.

    Create client and server IP address for secondary

Step 3. Add a load balancing virtual server on the primary node.

  1. Navigate toConfiguration > Traffic Management > Load Balancing > Virtual Servers > Add.

  2. Add the required values for Name, Protocol, IP Address Type (IP Address), IP Address (primary client alias IP address) and Port, and clickOK.

    LB virtual server client alias

Step 4. Add a service or service group on the primary node.

  1. Navigate toConfiguration > Traffic Management > Load Balancing > Services > Add.
  2. Add the required values for Service Name, IP Address, Protocol and Port, and clickOK.

Step 5. Bind the service or service group to the load balancing virtual server on the primary node.

  1. Navigate toConfiguration > Traffic Management > Load Balancing > Virtual Servers.
  2. Select the load balancing virtual server configured inStep 3, and clickEdit.
  3. In theService and Service Groupstab, clickNo Load Balancing Virtual Server Service Binding.
  4. Select the service configured in theStep 4, and clickBind.

Step 5. Save the configuration.

After a forced failover, the secondary becomes the new primary. The client alias IP (VIP) and the server alias IP (SNIP) from the old primary moves to the new primary.

Configure high availability by using the CLI

Step 1. Set up high availability inINC Enabledmode in both the instances by using the Citrix ADC CLI.

On the primary node, type the following command.

add ha node 1  -inc ENABLED

On the secondary node, type the following command.

add ha node 1  -inc ENABLED

Thesec_iprefers to the internal IP address of the management NIC of the secondary node.

Theprim_iprefers to the internal IP address of the management NIC of the primary node.

Step 2. Add VIP and SNIP on both nodes.

Type the following commands on the primary node:

add ns ip   -type VIP

Note:

Enter the Alias IP address and netmask configured for the client subnet in the VM instance.

add ns ip   -type SNIP

Theprimary_sniprefers to the internal IP address of the server-facing interface of the primary instance.

Type the following commands on the secondary node:

add ns ip   -type VIP

Note

Enter the Alias IP address and netmask configured for the client subnet on the primary VM instance.

add ns ip   -type SNIP

Thesecondary_sniprefers to the internal IP address of the server-facing interface of the secondary instance.

Note:

Enter the IP address and netmask configured for the server subnet in the VM instance.

Step 3. Add a virtual server on the primary node.

Type the following command:

add  vserver

Step 4. Add a service or service group on the primary node.

Type the following command:

add service

Step 5. Bind the service or service group to the load balancing virtual server on the primary node.

Type the following command:

bind  vserver

Note:

To save your configuration, type the commandsave config. Otherwise, the configurations are lost after you restart the instances.

Deploy a VPX high-availability pair with private IP address on Google Cloud Platform
January 11, 2023
Contributed by:
C S
January 11, 2023
Contributed by:
C S

In this article

Site feedback | Privacy and legal terms | Cookie preferences | Consent settings | docs.cloud.com
© 1999-Cloud Software Group, Inc. All rights reserved.