For the complete documentation index, see llms.txt. This page is also available as Markdown.

Active - Active: On-Prem Datacenters

Applies to on-premises deployments using ESX, KVM, or Hyper-V virtual platforms.

The Cloudbrink Connector component provides secure zero-trust access to private applications hosted inside customer private networks. Cloudbrink supports access to private networks in a physical on-prem datacenter or a virtual CSP-hosted datacenter such as a VPC/VNET on AWS, Azure, or GCP.

Starting with release 14.3, Cloudbrink supports Connector deployments in Active-Active mode in on-premises environments, in addition to the existing Standalone and Active-Standby modes.

Active-Active mode on on-premises environments is available from the 14.3 release onward.

Points to note

  • Up to 64 Connector instances can be clustered in one logical Active-Active Connector group.

  • When a new Connector instance is added to an existing Active-Active Connector group, new user sessions are loaded onto the new instance until the load is evenly balanced. Existing sessions on the existing instances are not touched.

  • When an existing Connector instance becomes unavailable for any reason, the user sessions on that instance are re-distributed across the remaining available instances.

  • When user sessions are re-distributed, users do not need to re-authenticate to Cloudbrink. The user's authentication session remains intact.

  • Network-level TCP connections are terminated when a user session is re-distributed to another instance. Applications such as SSH or FTP need to be re-established. Web sessions see a short disruption but continue to work after re-distribution.

  • User sessions are distributed across Connector instances based on the session load of each instance.

Use cases

Horizontal scaling

Customers with high-scale requirements can use Active-Active mode to support a large number of users. Customers can start with a limited number of Connector instances and, as the user base grows, add more Connector instances to meet the new scale requirements.

Availability

Active-Active mode can be used to increase availability. When one Connector instance becomes unavailable, the load on that instance is distributed across all remaining available instances. In case of an incident, multiple other instances take over the load without burdening a single standby instance.

Deployment steps

Step 1: Create the Active-Active Connector on the Cloudbrink Admin Portal

  1. Navigate to Admin Portal → Configure → Resources → Connectors → Add.

  2. When adding the new Connector, set Deployment Mode to active-active.

  3. Configure the User IP Management method used to assign datacenter IPs to remote user sessions. In Active-Active mode, three options are supported:

    • DHCPv4: only an IPv4 address is assigned.

    • DHCPv4v6: both IPv4 and IPv6 addresses are assigned.

    • Static IP Pool: the sys-admin manually configures the IP ranges for each Device-User-Group.

  4. When the Static IP Pool method is used, select the list of Device-User-Groups that will use this Connector to access private applications. As part of the Device-User-Group selection, configure a Pool Name and Lease Time for each Device-User-Group.

  5. Configure the remaining parameters (DNS Servers, Enterprise Resources) as usual.

  6. Save the Connector.

For the Static IP Pool method

Step 2: Deploy Connector instances from the hypervisor management console

  1. Provision the Connector VMs on the hypervisor virtual hosts (ESX, KVM, or Hyper-V).

  2. In the cloud-init script, provide the correct input parameters such as IP address, Gateway, and the OTP generated from the Cloudbrink Admin Portal for this Connector.

  3. Once the Connector instance deployment completes successfully on the hypervisor, the Cloudbrink Admin Portal shows the instance in Online status.

Connector list

Instance-level list for each Connector

Step 3: Configure Static IP Pools for Connector instances on the Cloudbrink Admin Portal

  1. Navigate to the Connector instances of the Active-Active Connector by clicking the Name of the Active-Active Connector.

  2. Under each Connector instance, the Pool Names specified at the Connector level are pre-populated.

  3. For each Pool Name, define the IPv4 and IPv6 pools.

Per-instance IP prefix configuration

Step 4: Verify the Connector instance status

All Connector instances must be in Active status. Active status indicates that the Connector is ready to handle user traffic to the private applications.

Last updated