• Digital Workspaces
          • Digital Workspaces

            Enable desktop & application virtualization, identity management, and secure remote access for work from home (WFH) employees

          • zPortal
          • Controller for desktop and application virtualization via shared hosted desktops and VDI

          • zGateway
          • Secure remote users working from any network on any device to protect corporate data

          • SnapVDI Thin Client (zTC)
          • Thin client endPoint devices for Citrix, Microsoft Hyper-V & WVD and VMware

          • zBrows
          • Provide secure browser-based access to virtualized corporate workspace users

          • zMFA
          • Integrated multi-factor authentication (MFA) for secure user verification on any device

          • zClient
          • Software client for installing on your endpoint devices for connection to zPortal and zGateway

    • Healthcare Solutions
          • Healthcare Solutions

            Remote patient monitoring platform and devices for clinicians and caregivers to remotely monitor the vital signs of their patients

          • ZettaRPM
          • Universal cloud-based remote patient monitoring platform for healthcare organizations

          • B.O.L.T Devices
          • Monitor, track, and improve patients’ health with remote patient monitoring (RPM) devices

    • Data Storage Appliances
          • Data Storage Appliances

            Reliable, high-performance SAN appliances with inclusive snapshots, replication, and  automated data tiering software

          • StorTrends 3500i
          • Extreme-performance SAN with Hybrid and All-Flash configurations to handle even the most demanding workloads

          • StorTrends 3400i
          • Highly reliable HDD-based SAN suited for data retention, backups and low-performance environments

          • StorTrends 3202j
          • Expansion shelf configurable as all-HDD, hybrid, or all-flash to seamlessly add capacity to the StorTrends 3500i or StorTrends 3400i

  • Knowledge Base
  • Company
  • Events
  • Support
  • Contact

How Can We Help?

zGateway Cluster Installation

You are here:
< All Topics

A full zGateway cluster installation requires a 2 node deployment. The installation process steps are as follows:
1. Install primary zGateway Cluster Manager
2. Perform standard pre-boot and bootstrap process of zGateway
3. Start NTP services from zGateway management page
4. Add the same node as zGateway node to the cluster
5. Install zGateway on second host and add it to the Cluster as secondary Cluster Manager
6. Add standby node machine also as zGateway node

INSTALLING PRIMARY ZGATEWAY CLUSTER MANAGER NODE
Prerequisites: zGateway latest ISO, Virtual or physical hosts with minimum 4 GB of RAM and dual core of CPU
Installation steps:

1. Install zGateway using the zGateway ISO on virtual machine or a physical host. Refer to the zGateway install guide on preparing the virtual machine or physical host and zGateway installation steps

2. After the “System Configuration” step in preboot stage, select the installation type as “install first node” under “Clustered zGateway Installation” section

<onegate.IMG>

1. Standalone installation
a. Select this option to install zGateway as a standalone gateway. Cluster options cannot be enabled later on this gateway from management console.
2. Clustered zGateway Installation
Select this option for adding this gateway to a cluster.
a. Install first node
Select this option if you are creating a new cluster and you are configuring this gateway as the first node which will have both LB Node
(Load balancer module, configuration database and HA modules).
b. Join a cluster as backup load balancer
Select this option if you already have a cluster and you are adding this Gateway as backup load balancer
c. Join as a zGateway Server
Select this option if you already have a cluster and you are adding this Gateway as just a zGateway Node.
d. Restore complete configuration from backup file
This works as per the previous version where admin wants to restore The complete config from a backup file. For clusters, this

3. Specify the virtual IP address that will be used for the cluster. This IP address must be an available (free) IP address on the network.
Important: This IP Address cannot be changed from management console currently.

4. Enter the common hostname for the cluster. This hostname does not have to be the public DNS name that will be accessed by end users, but this is an internal hostname of the cluster used for accessing internal services.
Important: This hostname cannot be changed from management console currently.

5. Up on confirming the selection of “install first node”, the installation of primary Cluster Manager will start. After completion of the process, security officer must be created and enrolled as the first security officer.
Please refer to zGateway installation guide for steps to install zGateway client and installing the first security officer.
Tip: Install the client from URL: http://hysecure_IP_address

6. After completion of installation, this host will become the primary Cluster Manager and will host its own physical network IP Address as well as Virtual IP Address after the configuration mentioned below.

CONFIGURING PRIMARY ZGATEWAY CLUSTER MANAGER
After the first security officer user is registered and certificate is installed on administers machine, login as security officer using the zGateway client and open the management console.

Follow these steps on zGateway management console to configure the Primary zGateway Node

1. Create a new HTTP type application with name “ClusterManagement” with Application Server as the virtual IP address and port as 3636. Provide the URL as
http://zgateway_virtual_IP_address:3636

Note: replace zgateway_virtual_IP_address with the virtual IP address of the cluster
provided during installation

Note: This application can be marked hidden in case admin do not want to publish this on
their Launchpad.

<create_app.IMG>

2. Create an application group with name “ClusterAdminApps” with high security user and add
the application to this application group

<app_group.IMG>

3. Create an Access control using Native as the authentication server for High Security Users for the SYSTEM group and assign the newly created high security application group

<access_control.IMG>

4. Logout from zGateway client and login again and open zGateway management console

5. Go to Host Configuration -> Global Settings page and start NTP server.

<global.IMG>

6. Go to High Availability -> Configuration page and start configuring HA.

<config.IMG>

Setting Description Default Value Value Specification
Virtual IP Address The cluster specified during the installation of the first node Provided by the admin Valid IP Address
Network Mask Network Mast of the Virtual IP Selected from the drop down menu Valid Netmask
Primary Load Balancer Server IP The physical IP address of the primary Cluster manager The IP address of this host Valid IP
Backup Load Balancer Server IP The physical IP address of the secondary Cluster Manager The value is bland. It must be entered once the secondary cluster manager is added to the cluster Valid IP or blank entry
Load Balanced Port Number List of ports which will be load balanced by the service 80 and 443 Comma separated list of ports
Device Name The network interface name of the interface on which virtual IP addresses will be assigned First interface of the host Select from drop down menu

7. Add the same host as the VPN Servers by clicking on Add button under VPN Servers section Specify the Server Name for display, IP Address of this host as Server IP Address. Server Weight is used for weight based load balancing when two or more VPN servers (zGateways) will have different hardware sizing. The node with higher weight will receive more connections.

<vpn.IMG>

8. If a secondary zGateway Cluster Manager is to be added to the cluster, the physical IP address of the secondary Cluster Manager host must be updated.

9. The secondary zGateway host (if going to be added immediately) must be added as VPN Server list also.

10. The final configuration shall look like this:

<config2.IMG>

11. Click on “ADVANCED HA CONFIGURATION” and make sure following options are checked

a. Enable check box for “Monitor NIC links for failures”
b. Change the Persistence (Seconds) to 5 seconds/User preference
c. Click on save button to close advanced configuration screen.

12. Click on “Save” to save the configuration

13. Click on “Reload Service” to apply the Cluster modified configuration to cluster

14. Clicking on “Advanced HA Configuration” will show advanced cluster configurations. Follow the section at the end of this document for details on the advanced configuration.

15. The Cluster configuration is completed.

16. Perform other tasks like installing license and or publishing applications, ACLs, etc

17. Move the gateway to “run state” if the secondary zGateway node is not to be configured as the immediate next step.

INSTALLING SECONDARY ZGATEWAY CLUSTER MANAGER
Prerequisites: zGateway latest ISO, Virtual or physical hosts with minimum 4 GB of RAM and dual core of CPU
Installation steps:

1. Install zGateway using the zGateway ISO on a virtual machine or a physical host. Refer to the zGateway install guide on preparing the virtual machine or physical host and zGateway installation steps

2. After the “System Configuration” step in preboot stage, select the installation type as “Join a cluster as backup load balancer” under “Clustered zGateway Installation” section

3. Specify the Virtual IP Address as the virtual IP address of the cluster , specified during installation of the primary Cluster Manager node.

4. Enter the same hostname specified during Cluster Manager node as the common hostname

5. Selecting option “Join a cluster as backup load balancer” will set this appliance as standby load balancer. The next step is synchronization of the settings with the active load balancer. On selecting “continue” button, this zGateway will connect to the IP address specified in the Virtual IP address field and try to get all the settings from the active cluster manager There is no bootstrap step to be performed on this appliance. Imp Note: The IP address of this Node should have been added to the Cluster configuration as standby load balancer and zGateway server for the synchronization to work. See the management console screens in sections below.
Tip: There is no additional configuration required for the secondary Cluster Manager

6. Synchronization of the secondary node will start which may take few minutes and will finish with a success message.

Go to Host Configuration -> Global Settings page and start NTP server

INSTALLING DEDICATED ZGATEWAY NODE
In case a 3rd or more node need to be added to the cluster, these nodes can only run zGateway node.
Prerequisites: zGateway latest ISO, Virtual or physical hosts with minimum 4 GB of RAM and dual core of CPU
Installation steps:

1. Install zGateway using the zGateway ISO on a virtual machine or a physical host. Refer to the zGateway install guide on preparing the virtual machine or physical host and zGateway installation steps

2. After the “System Configuration” step in preboot stage, select the installation type as “Join as zGateway server” under “Clustered zGateway Installation” section

3. Selecting the option “Join as a zGateway Server” will install just the zGateway components on the host and will initiate a configuration synchronization with the active load balancer using the IP address specified as Virtual IP address of the load balancer. After the initial configuration sync is finished, the zGateway will start functioning without requiring any additional configuration. Similarly more no. of zGateway Nodes can be added to an existing cluster.

4. Synchronization of this node will start which may take few minutes and will finish with a success message.

5. Go to Host Configuration -> Global Settings page and start NTP server

LICENSING
zGateway cluster uses a single license applied on the Primary zGateway Cluster Manager node. The Primary Cluster Manager node, shares the same license copy with all other nodes in the cluster. When Primary Cluster Manager node is not available, the Secondary Cluster Manager provides the license information to the other nodes in the cluster.

Was this article helpful?
4.5 out of 5 stars
5 Stars 0%
4 Stars 100%
3 Stars 0%
2 Stars 0%
1 Stars 0%
How can we improve this article?
Table of Contents
Top