# Admin Portal Configuration for On-Prem Connectors

Cloudbrink's Personal SASE enables enterprises to deliver best-in-class quality of experience and security for their end users in the new mobile-first and cloud-native world. Cloudbrink achieves this through three simple components:

1. The Brink Agent is installed on end user devices, with all major platforms supported.
2. Enterprise access points are automatically created via machine learning in close proximity to the end user, enabling Cloudbrink's revolutionary overlay protocol to overcome the most challenging last-mile network conditions, delivering best-in-class, hi fidelity quality of experience for the end-user no matter the network they are connected to.
3. To provide end-to-end security, a Cloudbrink Connector is deployed in the customer's data center or cloud environment, creating a dark tunnel connection from the end user to their applications.

This document covers deploying the Cloudbrink Connector in an on-premises environment.

## Introduction

This document will guide the user to configure a Connector entity on the Cloudbrink admin portal and prepare the prerequisites for deploying the Connector VM on an on-premise datacenter.

## Create a Connector entity on Cloudbrink admin portal

1. Login to Cloudbrink admin portal (<https://admin.cloudbrink.com>) with admin credentials.
2. Navigate to Configure → Resources → Connector section
3. Click on "Add New"

## Cloudbrink Software Defined Mobility

![](https://web-api.textin.com/ocr_image/external/67a3024e43a8287e.jpg)

4. Provide the values for the configuration parameters as described below

·Name: Name of the Connector

·Hosting Environment: Select "Private" for on-premises or appropriate CSP

·Deployment Mode: Non-HA (standalone) or Active-Passive or Active-Active

·Region: Select "Private" for on-premises or appropriate CSP region

·Release: Select latest Ubuntu 22 based Connector release

**·** Num of Arms: Select 1 for one-arm and 2 for two-arm

·OS: Select Ubuntu

·OS-Version: 22.04 or 20.04

**·** DNS Primary IP: The enterprise private DNS server IP. If not available, use generic DNS services (ex: 8.8.8.8)

·User IP Management: Select "Source NAT" to use Connector interface IP as the source IP for all internal traffic. Select "DHCP" if a DHCP server will assign LAN IP to the remote user sessions or "Static IP Pool" if the LAN IP is managed by the Connector itself.

**·** Enterprise Services: Select the list of private IP subnet(s)/Hosts that would be accessible from this Connector

## Cloudbrink Software Defined Mobility

![](https://web-api.textin.com/ocr_image/external/37b0f8a580bd8e88.jpg)

![](https://web-api.textin.com/ocr_image/external/80df2da3cfc94729.jpg)

5. Configure Instances for the Connector by selecting "Configure Instances"

## Cloudbrink Software Defined Mobility

![](https://web-api.textin.com/ocr_image/external/ce7a32525acfa743.jpg)

6. Click "Add New" to create instances under the Connector. Provide below values to the configuration parameters.

·Name: Name for the instance

· Platform: Select amd64

·Hosting Environment: Select the hypervisor platform that is available in the on-premises DC

·IPv4 Address: IP address of the Connector interface

·Gateway Address: Default gateway for the Connector VM

**·** DNS Server: Enterprise private DNS server that Connector can use

**·** IPv6 Address: IPv6 address of the Connector interface

·Gateway Address: IPv6 default gateway

DNS Server: IPv6 DNS server

![](https://web-api.textin.com/ocr_image/external/5cb6c2e653bfb15e.jpg)

## Cloudbrink Software Defined Mobility

![](https://web-api.textin.com/ocr_image/external/1a23aec221c2ef7e.jpg)

7. After providing all the configuration parameters, click "Save and Download"
8. **NOTE**: Download the "Shell" type script if the lab server is a Linux or Mac machine. Download the "Powershell" type script if the lab server is Windows server.

![](https://web-api.textin.com/ocr_image/external/3425f87716cf2cb0.jpg)

9. Run the script from the lab server (Linux or Mac or Windows) from where the vCenter UI will be accessed and from where the Connector VM provisioning or deployment steps will be executed.
10. When the script is run, it will download the Connector VM image and the cloud-init ISO file needed to deploy the Connector VM.
11. Run the steps mentioned in the "CloudbrinkConnectorInstallationVMware" guide to complete the Connector VM deployment.


---

# Agent Instructions: Querying This Documentation

If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://docs.cloudbrink.com/configuration/connector-deployment/admin-portal-configuration-for-on-prem-connectors.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.