> 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/getting-started/networks-and-clouds.md).

# Networks and clouds

![Networks and EXT-MGMT](https://1807546539-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FhgHCHWL3861o2DBW53aA%2Fuploads%2FhUgZTEjv05Fmd5VWAmWe%2Fve20261112v5-networks-page.png?alt=media)

## Goal

Connect lab nodes to Management, Internet (NAT), and isolated Lab fabrics.

## Cloud node types

| Cloud                              | Typical use                                                                                                                                                                                    |
| ---------------------------------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| **Management**                     | Reach the node management VRF / out-of-band style access                                                                                                                                       |
| **NAT**                            | Outbound Internet for updates / licensing inside guests (when uplink exists)                                                                                                                   |
| **Bridge**                         | Attach to a real host NIC or VMware network for external labs                                                                                                                                  |
| **External management (EXT-MGMT)** | Attach labs toward an external management fabric (VLAN trunk and/or routed external). Controller discovery (NDFC/DNAC) is **not** shipping yet - configure connectivity in the product UI only |

Drag a cloud from the template drawer onto the canvas, then connect device ports to cloud ports.

### EXT-MGMT tips (customer-safe)

* Prefer documented UI fields such as VLAN trunk / allowed VLANs / routed external when your edition exposes them
* Do not expect automatic NDFC or DNAC inventory import in this release
* Keep management plane separate from student data links (same idea as CSR Gi1 vs Gi2 - see CSR and multi-NIC interfaces)

## OVA default NICs

Keep this order when importing the OVA:

1. Bridged -> Management (often `ens160`)
2. NAT -> Internet (`ens161`)
3. Host-only -> Lab (`ens192`)

On ESXi, map the three OVF networks to management, uplink, and isolated lab port groups.

## Bare metal

Map clouds to physical NICs under **Infrastructure**. Day-0 addressing was set in the installer; later changes use [Management network](/getting-started/management-network.md).

## Expected result

* Links show in Design
* After Start, Visualize / Traffic Lens can show link activity when the dataplane reports
* Guests that need DHCP on NAT receive addresses when NAT uplink works

## If it fails

* Wrong NIC order on OVA -> fix mapping or re-import
* Bridge cloud with no host uplink -> pick a real NIC in Infrastructure
* Nested VMware without promiscuous / forged transmits on the lab vSwitch -> enable for bridged labs

## Next

* [Management network](/getting-started/management-network.md)
* [Design mode](/labs/design-mode.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 by asking a question.

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

```
GET https://docs.vex-nx.com/getting-started/networks-and-clouds.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.