> For the complete documentation index, see [llms.txt](https://docs.cloudbrink.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.cloudbrink.com/configuration/connector-deployment/connector-installation-vmware-esxi.md).

# Connector Installation - VMWare ESXi

This document will guide you to create a Cloudbrink Connector (either single or active-standby pair) in VMware ESXi. Steps 9 through 18 must be completed twice in order to create two instances for the active-standby pair.&#x20;

**Prerequisites**&#x20;

1. VMware vCenter account with privilege to upload disk images and create virtual machines&#x20;
2. Create a Connector on the Cloudbrink Admin Portal, create Connector instance(s) and download the installation\_script for each of these instance(s)&#x20;
3. Run the installation\_script from the endpoint from where vCenter UI will be managed&#x20;
4. By running the installation\_script, you can download the VM files (ex: OVA) and the ISO file needed for the Connector bring-up step.&#x20;
5. Please refer to “Connector Configuration Guide” for details on these steps&#x20;

**Connector VM Requirements (minimum)**

1. Compute: 4 CPU and 8GB RAM&#x20;
2. Storage: 50 GB Disk&#x20;
3. Networking: Outbound ports 443 (TCP), 9090 (TCP) and 9993-4 (UDP) to Cloudbrink SaaS and Edges&#x20;

\
\
**Connector VM – High Level Instructions**

Deploy 1 (non-HA) or 2 (HA) Connector VMs OVA&#x20;

Edit the following settings of the deployed VM(s):&#x20;

&#x20;     Hard disk 1 size: 50 GB&#x20;

&#x20;     Attach CD/DVD drive with provided ISO (*unique* per VM) file&#x20;

Set forged transmits to Accept on the attached vSwitch&#x20;

**Connector VM – Detailed Instructions** <br>

1. Navigate to the Storage section of the vCenter UI, and select an appropriate datastore and  folder to upload the cloud-init ISO files, per business requirements.&#x20;

NOTE: The OVA and ISO files could be downloaded to the laptop from where vCenter UI is being accessed using the script given from the Cloudbrink admin portal&#x20;

2. Click Upload files, and in your OS file window, select the cloud-init ISO files that were downloaded by running the script from the admin portal.&#x20;
3. Utilizing the dropdown Menu at the vCenter UI, select Content Libraries.&#x20;
4. Select (or create) the Content Library of your choice.&#x20;
5. Click Actions and then Import item.&#x20;

![](https://2520794396-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FsONIa4VvrnRrQWBte3ns%2Fuploads%2FsRnThvFy4wvEnbtEpXpj%2Fimage.png?alt=media\&token=956a0988-9466-427b-8ad1-0a2a2ef1ac86)<br>

6. In the pop-up, select the Local file radio button, and then click Upload File. In your OS file window, select the Cloudbrink Connector OVA file.&#x20;

<figure><img src="https://2520794396-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FsONIa4VvrnRrQWBte3ns%2Fuploads%2FhL8tldWvde35FqKC1iqW%2Fimage.png?alt=media&amp;token=83b00f72-b98e-4eec-a119-8834ae5f4103" alt=""><figcaption></figcaption></figure>

7. Within the Source file details section, click the upload button in the 1 associated file miss- ing row, and in your OS window select the Cloudbrink Connector OVA file.&#x20;

<figure><img src="https://2520794396-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FsONIa4VvrnRrQWBte3ns%2Fuploads%2FCNmW5tGVO5eH9z4ME6yq%2Fimage.png?alt=media&amp;token=e2d96f5a-c474-4a97-8df5-a7bbe5f33fe6" alt=""><figcaption></figcaption></figure>

8. Click the Import button in the lower right corner of the pop-up, and wait for the upload task to complete.&#x20;

<figure><img src="https://2520794396-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FsONIa4VvrnRrQWBte3ns%2Fuploads%2FbLrMzk92Jomn4P37yzEt%2Fimage.png?alt=media&amp;token=2fb46713-09d8-4dbf-adb9-001e8e04a134" alt=""><figcaption></figcaption></figure>

9. From within your Content Library, click on the recently uploaded OVA file, then the Actions dropdown, and finally New VM from this Template.&#x20;

<figure><img src="https://2520794396-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FsONIa4VvrnRrQWBte3ns%2Fuploads%2FMZNhrbsJRRTBy9vcmUf6%2Fimage.png?alt=media&amp;token=feee4bc9-71ec-4efa-8d25-24fe10c16ee9" alt=""><figcaption></figcaption></figure>

10. Name and select the appropriate location to deploy the Connector VM, per business requirement, and then click Next.&#x20;
11. Continue through the deployment wizard, selecting appropriate resources per business re- querulents. On the last step, click Finish.&#x20;
12. Once the VM is deployed, navigate to VMs and Templates, select the recently deployed VM, click Actions, and then Edit Settings.&#x20;

<figure><img src="https://2520794396-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FsONIa4VvrnRrQWBte3ns%2Fuploads%2F73OZvA66MYwqOKqun6oG%2Fimage.png?alt=media&amp;token=f775a7e3-76f8-4b16-9afc-4e8797d3e7b9" alt=""><figcaption></figcaption></figure>

13. Ensure the CPU is set to 4, and the Memory to 8 GB.&#x20;
14. Change the VM's Hard disk 1 size to 50 GB.&#x20;
15. Click the Add New Device button, then CD/DVD Drive.&#x20;
16. Change the newly added CD/DVD Drive dropdown to Datastore ISO file, navigate to and  select the uploaded ISO selected in steps 1-2, and click Ok.&#x20;
17. Click to enable the Connect at Power On checkbox in the CD/DVD Drive entry.&#x20;
18. Ensure the Hard disk 1 and the CD/DVD Drive entries appear as in the image below, and then click Ok.&#x20;

<figure><img src="https://2520794396-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FsONIa4VvrnRrQWBte3ns%2Fuploads%2FZzpCYSYltPDKVgH8jwDt%2Fimage.png?alt=media&amp;token=167886cc-14a3-467e-8558-9e792745f935" alt=""><figcaption></figcaption></figure>

19. Navigate to Hosts and Clusters from the vCenter menu and select the host (or cluster) chosen in step 10.&#x20;
20. In the host UI, select the Configure tab, then in the left column under the Networking section select Virtual Switches.&#x20;
21. In the Virtual Switches table, select the virtual switch chosen in step 10, and then click Edit.&#x20;

<figure><img src="https://2520794396-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FsONIa4VvrnRrQWBte3ns%2Fuploads%2FIZ2zm0N8jcwhCmnIGEuL%2Fimage.png?alt=media&amp;token=2a9d8c31-f293-400b-8696-d89d38da56f2" alt=""><figcaption></figcaption></figure>

22. Select Security from the left column and ensure Forged transmits are set to Accept.&#x20;

<figure><img src="https://2520794396-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FsONIa4VvrnRrQWBte3ns%2Fuploads%2F7t4DCQHTfQW437xEEYde%2Fimage.png?alt=media&amp;token=62b20dcb-1a4a-44c9-88e7-7ac9226e701f" alt=""><figcaption></figcaption></figure>

23. Repeat steps 18 through 21 for all vCenter hosts that can host the Connector VMs.&#x20;
24. Navigate back to VMs and Templates, and power on the Connector VM(s).&#x20;


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

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

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.cloudbrink.com/configuration/connector-deployment/connector-installation-vmware-esxi.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

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.
