> For the complete documentation index, see [llms.txt](https://docs.vex-nx.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.vex-nx.com/vex-nx-user-guide-1/networks-and-clouds.md).

# Networks and clouds

The OVA ships with **three NICs**. Keep adapter order. Map them on Workstation (VMnets) or ESXi (port groups).

## OVA adapters

| Adapter | OVF network | Workstation (typical) | ESXi (typical)       | Guest NIC | Default cloud mode |
| ------- | ----------- | --------------------- | -------------------- | --------- | ------------------ |
| 1       | Management  | VMnet0 Bridged        | Mgmt / VM Network    | ens160    | **Management**     |
| 2       | Internet    | VMnet8 NAT            | Uplink / internet PG | ens161    | **NAT**            |
| 3       | Lab         | VMnet1 Host-only      | Isolated lab PG      | ens192    | **Bridge**         |

* Prefer **`http://<management-ip>`** (Adapter 1) for the web UI.
* Internet is for lab NAT egress, not usually UI access.
* Do not reorder NICs after import.

Import steps: Install the OVA. Deep ops: cloud-vmware-networks.md.

## Cloud templates in a lab

| Cloud mode     | Meaning                                                                            |
| -------------- | ---------------------------------------------------------------------------------- |
| **NAT**        | Lab peers in `100.64.x.x`; traffic NATs out the uplink (usually Internet / ens161) |
| **Management** | L2 macvlan onto the selected NIC                                                   |
| **Bridge**     | Same L2 attach; default prefers Lab / ens192 for isolated labs                     |

Configure appliance defaults under **Infrastructure -> Cloud <-> VMware adapters**. Override per cloud node in the lab inspector.

## Device management (OOB) ports

Many QEMU appliances expose a dedicated management NIC (`mgmt0`, `fxp0`, `Management0/0`, CSR `GigabitEthernet1`, and so on). VEX-NX marks that canvas port as **Mgmt**, skips it when auto-picking data links, and can auto-link it to an existing **Cloud Management** node so you can SSH/telnet from your PC on the bridged LAN.

1. Add **Cloud Management** to the lab.
2. Add the device (OOB auto-links when the cloud is present), or use **Connect to Management cloud** in the node inspector.
3. Configure an IP on the guest management interface, then connect from your PC.

Do not confuse the **appliance** Management NIC (OVA adapter 1) with the **guest** OOB port - see cloud-vmware-networks.md.

## Appliance Management IP

How to set DHCP or Static for the web UI address (console Keep/Change menu and **Infrastructure -> Management network**): [Management network](/vex-nx-user-guide-1/management-network.md).

Example Static: `192.168.8.50/24`, gateway `192.168.8.1`, DNS `8.8.8.8`. Internet (ens161) stays on DHCP for egress.

## Related

* [Management network](/vex-nx-user-guide-1/management-network.md)
* Install the OVA
* First login
* System requirements
* [Quick reference](/vex-nx-user-guide-1/reference/quick-reference.md)


---

# 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://docs.vex-nx.com/vex-nx-user-guide-1/networks-and-clouds.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.