> 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/labs/first-lab-walkthrough.md).

# First lab walkthrough

Goal: in about fifteen minutes, create a small FOSS lab, start it, open a console, run one command, and stop cleanly.

Assumes you already imported the OVA and [signed in](/getting-started/first-login.md). Docker should be available under **Infrastructure**.

## 1. Confirm the appliance

1. Open **Home**. Health should not look offline.
2. Open **Infrastructure**. Note Docker available (KVM is optional for this FOSS path).

## 2. Create a starter lab

1. Go to **Labs**.
2. Open **Starter templates**. Filter to **Foundations** or **Routing** and **Bronze**, then pick a small FRR or Alpine-based pack (or create a blank lab and drag **frrouting** / **alpine** from the drawer).
3. Open the new lab.

If you used a blank lab:

1. Stay in **Design**.
2. Drag two FRR (or Alpine) nodes onto the canvas.
3. Connect a port on each.
4. Optionally open **Lab guide** if the starter included one.

## 3. Validate once

1. Switch to **Validate**.
2. Run checks. Fix anything about missing images or empty topology before continuing.

## 4. Start nodes

1. Switch to **Operate**.
2. Click **Start all**.
3. Wait until nodes show running (or a clear error). First boot after install may still be pulling images - retry after a minute if needed.

## 4b. Glance at Observe (optional)

1. Switch to **Observe**.
2. Confirm health chips and that filters / Issues list look sane.
3. Switch back to **Operate** for consoles.

## 5. Open Terminal

1. Click **Terminal** so the workspace is visible.
2. **More -> Open all in Terminal** (or Connect from the node context menu).
3. Select an FRR tab. At the shell, run:

```
vtysh
show version
```

On Alpine, `ping` or `ip addr` is enough to prove the session.

Optional: turn on **Glass** so you can still see the canvas; leave **Click through** off while you type.

## 6. Stop

1. **Stop all**.
2. Close or **Hide** the Terminal workspace.

## What you proved

* UI reaches the API
* Docker nodes start
* Consoles attach through the Terminal workspace

## Next steps

* Add a licensed QEMU image via Import images (**Convert & add**) and drop an IOSv (or similar) node.
* Try [Assist](/assist/using-assist.md) with a design question.
* Instructors: [Instructor checklist](/classroom/classroom-for-instructors.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/labs/first-lab-walkthrough.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.