> For the complete documentation index, see [llms.txt](https://prosbcdocs.telcobridges.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://prosbcdocs.telcobridges.com/initial-installation/1.-instructions-by-platform/virtual-self-hosted-installation/virtual-vmware/launching-an-instance-of-vmware-vsphere.md).

# Launching an Instance of VMware vSphere 8

Deploy a ProSBC instance on VMware vSphere 8 using the vSphere Client: the Deploy OVF Template wizard, the virtual machine settings ProSBC needs, and first access to the web portal.

These instructions cover **vCenter Server 8** using the vSphere Client. For a standalone ESXi host, see [Deploying ProSBC on VMware](/initial-installation/1.-instructions-by-platform/virtual-self-hosted-installation/virtual-vmware/deploying-prosbc-on-vmware.md).

## Before you begin

You need:

* Access to the vSphere Client on vCenter Server 8, with rights to create a virtual machine
* The ProSBC `.ova` file
* Your ProSBC **product key** — the configuration wizard asks for it once the SBC is up
* A destination datastore and the port groups the SBC will use

The image, your product key and your license all come from the [TelcoBridges Customer Dashboard](https://dashboard.telcobridges.com/dashboard).

Size the virtual machine from the table on [Virtual - VMware](/initial-installation/1.-instructions-by-platform/virtual-self-hosted-installation/virtual-vmware.md#requirements).

{% hint style="info" %}
**Plan your network adapters before you start.** This walkthrough uses two: one for management (`mgmt0`) and one for SIP and RTP traffic. A 1+1 HA pair needs two more (`ctrl0`/`ctrl1`); transcoding need one more (`trans`).
{% endhint %}

{% hint style="warning" %}
**Adapter type is fixed when an adapter is added.** The OVA ships with **E1000** — the slowest of the types, but universally supported. The Adapter Type field cannot be edited afterwards: changing it means removing the adapter and adding a new one, which assigns a **new MAC address**, and ProSBC identifies its interfaces by MAC. On a modern guest OS type the dropdown may not offer plain `E1000` at all, in which case **VMXNET3** is the supported choice — ProSBC supports E1000 and VMXNET3 only.

**Decide before you deploy.** Check the [ProSBC Requirements Matrix](/initial-installation/1.-instructions-by-platform/prosbc-requirements-matrix.md) against your session count, and see [Adding Network Interfaces in VMware](/initial-installation/1.-instructions-by-platform/virtual-self-hosted-installation/virtual-vmware/adding-network-interfaces-in-vmware.md).
{% endhint %}

## Deploy the OVF template

### Start the wizard

Log in to the vSphere Client at `https://<vcenter-fqdn>/ui`.

![](https://3811773442-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FiK3TemJSDhHz3xNMOvvk%2Fuploads%2FhtNuPHDpdiX888Oqydkf%2F01_login_vsphere8.png?alt=media\&token=13b957c1-57f1-4446-952b-471ff927aa57)

In the vSphere Client, right-click the target — a cluster, host, datacenter or VM folder — and select **Deploy OVF Template**. The same item is available under **ACTIONS**.

The numbered headings below match the step rail down the left of the wizard. The rail starts short and grows once the OVA has been read.

![](https://3811773442-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FiK3TemJSDhHz3xNMOvvk%2Fuploads%2FbA0vnki0W2tyklJKjmSG%2F03_deploy_ovf_menu_vsphere8.png?alt=media\&token=4cc8deda-af7c-4e48-9f77-88e09b64432c)

### 1. Select an OVF template

Choose **Local file**, click **UPLOAD FILES** and select the ProSBC `.ova`. Click **NEXT**.

![](https://3811773442-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FiK3TemJSDhHz3xNMOvvk%2Fuploads%2F3d6NamGWTVO4BHWI8rxg%2F04_select_ovf_vsphere8.png?alt=media\&token=5c6fab97-8ea8-4c07-b8e0-7fde76cea004)

{% hint style="info" %}
A **URL** may be used instead if the OVA is reachable over HTTP from vCenter itself. Note that vCenter performs the download, not your workstation, so vCenter must be able to resolve and reach that address.
{% endhint %}

### 2. Select a name and folder

Enter a name for the virtual machine and choose its location. Click **NEXT**.

![](https://3811773442-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FiK3TemJSDhHz3xNMOvvk%2Fuploads%2FuUIkTnL8wmBlLAx6zhM0%2F05_name_folder_vsphere8.png?alt=media\&token=ef1a33e9-c938-425f-98da-a5a0c0fff5cb)

### 3. Select a compute resource

Select the host or cluster that will run the virtual machine. Wait for **Compatibility checks succeeded**, then click **NEXT**.

Leave **Automatically power on deployed VM** cleared — the virtual machine settings in the next section must be applied before first boot.

![](https://3811773442-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FiK3TemJSDhHz3xNMOvvk%2Fuploads%2F648wb2R9TMD8t7tkOPC3%2F06_compute_resource_vsphere8.png?alt=media\&token=c23fa110-bc92-4d41-aea5-81235d9e36c5)

### 4. Review details

Confirm the template details, then click **NEXT**.

![](https://3811773442-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FiK3TemJSDhHz3xNMOvvk%2Fuploads%2FqmQut4i8P5CyXxKGM8JM%2F07_review_details_vsphere8.png?alt=media\&token=140f1c65-4ae4-4c63-8703-b09a35380462)

{% hint style="info" %}
This page warns that "the OVF package contains advanced configuration options, which might pose a security risk", and lists entries such as `pciBridge*` and an `nvram` file. This is expected: those are the PCI bridge settings the ProSBC image requires. Click **NEXT** to accept them.

**Publisher** shows "No certificate present" because the OVA is not signed.
{% endhint %}

This page also shows the deployed size both ways — for example 3.1 GB thin provisioned against 40.0 GB thick provisioned — which is useful when choosing the disk format on the next page.

### 5. Select storage

Select the datastore. Under **Select virtual disk format**, choose **Thick Provision Lazy Zeroed**. Click **NEXT**.

![](https://3811773442-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FiK3TemJSDhHz3xNMOvvk%2Fuploads%2F528seqqLJEa3HYzB8miJ%2F10_select_storage_vsphere8.png?alt=media\&token=3a48a94e-7c28-4ee2-9f9b-f1d3c3b654c7)

{% hint style="info" %}
On a **vSAN** datastore this control reads "As defined in the VM storage policy" and the thin and thick options are not offered. On vSAN, disk provisioning is set by the storage policy rather than per-disk.
{% endhint %}

### 6. Select networks

Map each source network to a destination port group. **At least one adapter must connect to the management network from which the web portal will be reached.**

![](https://3811773442-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FiK3TemJSDhHz3xNMOvvk%2Fuploads%2FAqUOOKugQm9K6QwKHdD9%2F11_select_networks_vsphere8.png?alt=media\&token=68df1958-62f9-438b-82e1-be92ed30695e)

{% hint style="warning" %}
**Note the MAC address of each adapter before you continue.** You will need them twice: once when the configuration wizard asks you to assign interfaces to the SBC, and again to verify the result after first boot.

The management and traffic roles are **assigned during the configuration wizard, matched by MAC address** — they are not inherited from the order the adapters appear in. Assign them the wrong way round and the management interface ends up on your traffic network, which on many networks has no DHCP and no route in: the install completes successfully and then cannot be reached.
{% endhint %}

### 7. Ready to complete

Review the summary and click **FINISH**. Wait for the deployment task to finish before touching the virtual machine.

![](https://3811773442-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FiK3TemJSDhHz3xNMOvvk%2Fuploads%2FRFa7hYrt8JJgD1fbrBKt%2F13_ready_to_complete_vsphere8.png?alt=media\&token=92d0b35d-ab1d-472f-8325-d96aab1f4529)

## Configure the virtual machine

Apply these settings **before the first power-on**. They are what allow ProSBC to process media without jitter, and several of them cannot take effect on a running virtual machine.

Right-click the new virtual machine and select **Edit Settings**.

Make every change below in one visit and click **OK** once, at the end. Clicking **OK** after a single section closes the dialog and you will have to reopen it.

![](https://3811773442-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FiK3TemJSDhHz3xNMOvvk%2Fuploads%2FyC3d5Dd6jjwzqOiz2ix3%2F15_edit_settings_menu.png?alt=media\&token=a2d95e29-21d6-4ce0-b8cd-2787acdadee9)

### Network adapters

Confirm each adapter is on the intended port group and that **Connect At Power On** is selected.

![](https://3811773442-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FiK3TemJSDhHz3xNMOvvk%2Fuploads%2F2qOpYocKAvFjYzQHpqdI%2F16_network_adapters_vsphere8.png?alt=media\&token=6e585391-f0c0-4472-b9fc-b62989d3f3da)

{% hint style="info" %}
**Shares**, **Reservation** and **Limit** may appear greyed out on the network adapters. That is because Network I/O Control is not enabled on the distributed switch. ProSBC does not require these settings — the ones that matter are CPU, memory, disk and latency sensitivity, below.
{% endhint %}

### CPU

Expand **CPU** and set:

* **CPU** — the vCPU count for your session count, from the sizing table on [Virtual - VMware](/initial-installation/1.-instructions-by-platform/virtual-self-hosted-installation/virtual-vmware.md#requirements)
* **Shares** — High
* **Reservation** — see the calculation below
* **Limit** — Unlimited

Set the vCPU count first. The reservation is calculated from it, so changing the vCPU count later means recalculating the reservation.

![](https://3811773442-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FiK3TemJSDhHz3xNMOvvk%2Fuploads%2F7csL6Lbt3aXS02S89iey%2F17_cpu.png?alt=media\&token=5ee39c65-5e85-4ed1-91b0-9b91425e4a41)

**Calculating the reservation.** Take the host's total CPU capacity in MHz, divide by its number of **physical cores**, then multiply by the number of vCPUs assigned to this virtual machine.

Find the host's figures on **Host → Summary**: Sockets, Cores per Socket, and total CPU capacity. Physical cores = Sockets × Cores per Socket.

![](https://3811773442-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FiK3TemJSDhHz3xNMOvvk%2Fuploads%2FZf9ulaIFtz7N2ozNAL3d%2F23_host_summary.png?alt=media\&token=78bea4d9-6af8-4f69-9fc6-8bdc7360ed65)

{% hint style="warning" %}
**Use physical cores, not Logical Processors.** With hyperthreading enabled, Logical Processors is double the core count. Dividing by it gives half the correct figure and under-reserves by half.

**And do not simply take the largest value the Reservation dropdown offers.** That dropdown shows the unreserved capacity available in the parent cluster or resource pool, which can be many times what this virtual machine is able to use. Reserving more than its vCPUs can consume will prevent the machine from powering on.
{% endhint %}

### Memory

Expand **Memory** and select **Reserve all guest memory (All locked)**.

![](https://3811773442-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FiK3TemJSDhHz3xNMOvvk%2Fuploads%2FJSGHASQ6sHKhHMycu8MN%2F19_memory.png?alt=media\&token=c11c30a9-fd5d-4e0c-af2d-16feb009e0e0)

### Hard disk

Expand **Hard disk 1** and set **Shares** to High.

![](https://3811773442-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FiK3TemJSDhHz3xNMOvvk%2Fuploads%2FCKO1ZBIDv6ofbGaH4uAQ%2F20_hard_disk.png?alt=media\&token=c1983e90-9720-4e26-8fd6-474790a195eb)

{% hint style="info" %}
On a **vSAN** datastore there is no Shares field on the disk — disk shares and IOPS limits are governed by the storage policy instead. If the field is not present, there is nothing to set here.
{% endhint %}

### Latency sensitivity

Select the **VM Options** tab, expand **Advanced**, and set **Latency Sensitivity** to **High**. Click **OK**.

{% hint style="warning" %}
Latency Sensitivity requires the full memory reservation above to take effect. Set the memory reservation first.

This setting is what grants the virtual machine exclusive access to physical CPUs. It is also the prerequisite for ProSBC's own **Dedicated CPU** option to be worth enabling — isolating cores inside the guest while the hypervisor can still deschedule the virtual machine gives you the cost without the benefit.
{% endhint %}

## Power on and find the management address

Select the virtual machine and choose **ACTIONS → Power → Power On**.

![](https://3811773442-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FiK3TemJSDhHz3xNMOvvk%2Fuploads%2FLew3zOVQMKHKsGDdDBno%2F22_power_on.png?alt=media\&token=e36c5b11-76b0-4630-baaf-4ec88bdb2112)

Open the console and log in as `root`. The default password is `root`.

All detected interfaces have DHCP enabled by default. List them with:

```
# ip addr
```

![](https://3811773442-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FiK3TemJSDhHz3xNMOvvk%2Fuploads%2FYe2Xgwp7otsXo853jgqu%2F27_console_ip_addr.png?alt=media\&token=0b584852-a199-4963-af4b-cfd0066e575d)

{% hint style="info" %}
**Before a configuration is activated, the interfaces appear under their kernel names — `ens32`, `ens33` and so on.** Once a configuration is active, ProSBC renames them to `mgmt0`, `voip0` (and `ctrl0`/`ctrl1` where applicable), keeping the original names as altnames. If you are looking for `mgmt0` and cannot find it, you are simply early in the process.

Match interfaces to virtual adapters by MAC address.
{% endhint %}

To assign a static management address instead, use [tbchangeip](/initial-installation/2.-initial-configuration/initial-setup/sbc-management-ip-configuration.md). It applies to the management interface only.

The address is also shown on the virtual machine's **Summary** tab under **IP Addresses**.

## Access the web portal

Browse to the management address on port **12358**, for example `http://192.168.101.70:12358`. The SBC Configuration Wizard opens.

![](https://3811773442-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FiK3TemJSDhHz3xNMOvvk%2Fuploads%2FLHSKvpLo0SLjcNJ9HUXa%2F29_portal_wizard.png?alt=media\&token=d4437837-cbac-4ed7-9700-59758b71f43a)

The wizard asks for your **product key**. Continue with [SBC Initial Configuration](/initial-installation/2.-initial-configuration/initial-setup.md).

{% hint style="info" %}
The traffic interfaces are configured in the web portal under **Hosts → IP Interfaces**, not in the operating system. Do not attempt to change the IP interfaces manually from the Operating system.
{% endhint %}

## Next steps

* [Adding Network Interfaces in VMware](/initial-installation/1.-instructions-by-platform/virtual-self-hosted-installation/virtual-vmware/adding-network-interfaces-in-vmware.md) — for HA control ports, transcoding ports, and additional VLANs
* [Configuring Passtrough interfaces on VMware](/initial-installation/1.-instructions-by-platform/virtual-self-hosted-installation/virtual-vmware/configuring-passtrough-interfaces-on-vmware.md) — SR-IOV and passthrough for higher session counts
* [ProSBC Requirements Matrix](/initial-installation/1.-instructions-by-platform/prosbc-requirements-matrix.md) — measured session capacity by networking mode


---

# 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 dynamically by asking a question.

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

```
GET https://prosbcdocs.telcobridges.com/initial-installation/1.-instructions-by-platform/virtual-self-hosted-installation/virtual-vmware/launching-an-instance-of-vmware-vsphere.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.