> 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-nutanix-ahv.md).

# Connector Installation - Nutanix AHV

This document will guide you to create a Cloudbrink Connector (either single or active-standby pair) in AHV. Steps 6 through 16 must be completed twice in order to create two instances for the active-standby pair.

### Prerequisites

* The Connector virtual machine qcow2 disk file should have been provided separately, which can be re-used for any number of Cloudbrink Connectors
* A Cloud-Init script for static IP and one-time Connector Key should also have been provided separately
* Nutanix Prism Element admin account to upload the disk image and create virtual machines

### Connector VM Requirements

* Compute: 4 CPU and 8GB RAM
* Storage: 30 GB Disk
* Networking: Outbound ports 443 (TCP), and 9993-4 (UDP) to Cloudbrink SaaS and Edge IPs

### Connector VM – High Level Instructions

* Upload the provided qcow2 disk file to the AHV Image Service
* Deploy one (non-HA) or two (HA) VMs from the image with the following settings:
  * The above compute resources
  * A cloud-init customization script with desired static IP and Connector Key

\<img>cloudbrink logo\</img> Software Defined Mobility Cloudbrink Connector - AHV | \<page\_number>1\</page\_number>

***

## Connector VM - Detailed Instructions

1. **Expand** the provided tar file via your GUI, or the following CLI command:

   ```
   tar -xzvf connector-v*-kvm.tar.gz
   ```
2. Within **Prism Element**, click the **gear icon** in the upper right corner, and then **Image Configuration** along the left column.

<figure><img src="https://2520794396-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FsONIa4VvrnRrQWBte3ns%2Fuploads%2Fu3gqr3P8QIa6qI9J5TVK%2Fpage_2_image_2.jpeg?alt=media&amp;token=fdf94869-6e0a-407d-86d0-75e56e97fa1c" alt=""><figcaption></figcaption></figure>

3. Click the **+ Upload Image** button within the Image Configuration.
4. Within the **Create Image** window fill out the following fields and then click **Save**: A. **Name**: a friendly name for the Cloudbrink Connector Image B. **Annotation**: (optional) an annotation per business practices C. **Image Type**: DISK D. **Storage Container**: choose per business practices E. **Image Source**: Upload a file F. **Choose File**: connector-v\*.qcow2

<figure><img src="https://2520794396-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FsONIa4VvrnRrQWBte3ns%2Fuploads%2FIuMw4ucexIHpRCW3aCrW%2Fpage_2_image_2.jpeg?alt=media&amp;token=f681144b-056c-4423-8a3b-54aa36956e34" alt=""><figcaption></figcaption></figure>

5. Depending upon network speed, wait several minutes for the image to upload and convert to a usable format. Once complete, verify the image is in an **Active** state.

<figure><img src="https://2520794396-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FsONIa4VvrnRrQWBte3ns%2Fuploads%2FeTaSa6GSDDFW82Yi8IRg%2Fpage_3_image_1.jpeg?alt=media&amp;token=f66f5673-ffcc-4fe8-b30a-7580ef74f32e" alt=""><figcaption></figcaption></figure>

### Image Configuration

Manage the images to be used for creating virtual disks.

* Upload Image

| NAME               | ANNOTATION | TYPE | STATE  | SIZE   |
| ------------------ | ---------- | ---- | ------ | ------ |
| Cloudbrink-Conn... |            | DISK | ACTIVE | 30 GiB |

6. Expand the **main menu dropdown** in the upper left corner, select **VM**, and the click **+ Create VM** in the upper right corner.
7. Within the **Create VM** pop-up, provide a **name** and **description** per business practices.

<figure><img src="https://2520794396-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FsONIa4VvrnRrQWBte3ns%2Fuploads%2FHuuBf8nbeN6h43nuldxR%2Fpage_3_image_2.jpeg?alt=media&amp;token=fc905614-ab0b-40ac-8674-ded54ef11822" alt=""><figcaption></figcaption></figure>

***

8. Within the **Compute Details** section, change the **vCPU(s)** to **4**, and the **Memory** to **8**.

<figure><img src="https://2520794396-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FsONIa4VvrnRrQWBte3ns%2Fuploads%2FQ3FyvVYnBNt1CVvYnYOf%2Fpage_4_image_1.jpeg?alt=media&amp;token=45ac28de-d335-48e6-8f52-106e12d310f2" alt=""><figcaption></figcaption></figure>

8. Click the **+ Add New Disk** button, then fill out the following fields and click **Add**: A. **Type**: DISK B. **Operation**: Clone from Image Service C. **Bus Type**: SCSI D. **Image**: Select the image created in step 4 E. **Index**: Next Available

<figure><img src="https://2520794396-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FsONIa4VvrnRrQWBte3ns%2Fuploads%2FVCFllKBnuIJFUGOefAxa%2Fpage_4_image_2.jpeg?alt=media&amp;token=ecc593f4-3b04-4521-bd02-835912006c64" alt=""><figcaption></figcaption></figure>

***

10. Ensure the **Disks** appear as below, and leave the **Boot Configuration** as default.

<figure><img src="https://2520794396-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FsONIa4VvrnRrQWBte3ns%2Fuploads%2FON0H0LYVRVMWUNNjY1Sa%2Fpage_5_image_1.jpeg?alt=media&amp;token=bcabf3ff-4bb4-4653-a671-22b2c46eceac" alt=""><figcaption></figcaption></figure>

11. Under Network Adapters, click **+ Add New NIC**.
12. Select the appropriate network under the **Network Name** dropdown, leave the **Connected** radio button toggled, and click **Add**.

<figure><img src="https://2520794396-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FsONIa4VvrnRrQWBte3ns%2Fuploads%2FhB6HnQP3HCOmhSKt9rA5%2Fpage_5_image_2.jpeg?alt=media&amp;token=6f87f054-22a5-46bb-96a8-0744c6163f7f" alt=""><figcaption></figcaption></figure>

***

13. Enable the **Custom Script** checkbox, and then select the **Type or Paste Script** radio button.

<figure><img src="https://2520794396-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FsONIa4VvrnRrQWBte3ns%2Fuploads%2Fd6rmsugSBcKmVFpkP6Rj%2Fpage_6_image_1.jpeg?alt=media&amp;token=519bfde3-a0b5-43df-ad75-e35d463585aa" alt=""><figcaption></figcaption></figure>

14. Within the **Type or Paste Script** text box, paste in the Cloud-Init script with the correct **IP address**, **subnet mask**, **default gateway**, and **OTP** values for this Connector.

<figure><img src="https://2520794396-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FsONIa4VvrnRrQWBte3ns%2Fuploads%2FwWOkIFhS7mest0731lZd%2Fpage_6_image_2.jpeg?alt=media&amp;token=e2c6ed7a-54ff-47a5-952e-9cfd4cd57d70" alt=""><figcaption></figcaption></figure>

15. Click **Save**.

16. Select the **Connector VM** from the VM table, and then click **Power on** below the table.

<figure><img src="https://2520794396-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FsONIa4VvrnRrQWBte3ns%2Fuploads%2FnietpwujYBckmzuuhJ5u%2Fpage_7_image_1.jpeg?alt=media&amp;token=f598fcf8-2a29-4419-bd6b-2328dc023fcf" alt=""><figcaption></figcaption></figure>


---

# 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-nutanix-ahv.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.
