> 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/labs/create-a-lab.md).

# Create a lab

Open **Labs** from the sidebar.

## Four ways to start

### Blank lab

1. Choose **Create blank lab** (wording may vary slightly by build).
2. Give it a clear name.
3. Open the lab - you land on an empty canvas in **Design** mode.

### Starter template

1. Open **Starter templates** (or the equivalent gallery on Labs).
2. Filter by skill domain and complexity rank, then pick a pack:

| Domain           | Examples                        |
| ---------------- | ------------------------------- |
| Switching        | VLAN, STP, LACP, QinQ           |
| Routing          | Static, OSPF, ISIS, BGP         |
| Datacenter       | EVPN, VXLAN, SR/SRv6            |
| Security         | ACL, nftables, IPsec, WireGuard |
| Service provider | MPLS LDP, L3VPN, VPWS, 6PE      |
| Automation       | Ansible, API, Scrapli           |
| Troubleshoot     | Planted-fault labs              |
| Foundations      | Linux bridge / iproute2 intros  |

Ranks: **Bronze**, **Silver**, **Gold**, **Platinum** (complexity - not Cisco exam tracks).

3. Confirm - VEX-NX creates the topology, often with configs and a **lab guide**.

Starters that use FRR/Alpine expect Docker images that seed on first boot (`quay.io/frrouting/frr:10.2.1`, `alpine:3.20`). If Start fails, wait for install to finish or see [Troubleshooting](/vex-nx-user-guide-1/reference/troubleshooting.md).

### From running-config (Pro)

1. Choose **From running-config**.
2. Paste Cisco / Arista / Junos (or supported) configs.
3. Preview the remap, then create the lab.

Community builds do not include this path.

### Import lab bundle (Pro)

1. Choose **Import lab bundle**.
2. Upload a lab export ZIP.
3. Preview, then create.

Community builds do not include this path.

## After the lab opens

You will see:

* Mode switch: **Design · Operate · Observe · Validate · Present**
* Topology canvas
* Template drawer (Design / Operate / Observe) unless you are in Focus
* Toolbar actions that change with the mode

Port labels use **short interface aliases** (`e0/0`, `eth0`, `gi0/0`, ...). In the node inspector: **Refresh aliases from config** or **Reset aliases**.

**Focus** collapses chrome into a thinner bar and can dock Terminal / Guide beside the canvas. Use it when you want more canvas and less chrome.

Next: [Design mode](/vex-nx-user-guide-1/labs/design-mode.md) or skip ahead to [First lab walkthrough](/vex-nx-user-guide-1/labs/first-lab-walkthrough.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/labs/create-a-lab.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.