> 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

![First lab on the canvas](https://1807546539-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FhgHCHWL3861o2DBW53aA%2Fuploads%2FgVqBBOyQp46RKEfApnz5%2Fve20261112v5-design-canvas.png?alt=media)

## Goal

Build a tiny working lab with FOSS Docker starters (no vendor image required).

## Why start here

Vendor disks need import and licence awareness. FRR and Alpine Guided / blank labs prove that Start, Terminal, and the fabric work on day 1.

## GUI tutorial

### Step 1 - Launch a Guided Lab

![Guided Labs](https://1807546539-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FhgHCHWL3861o2DBW53aA%2Fuploads%2FHSysito7HbpSm923Uhm6%2Fve20261112v5-guided-labs.png?alt=media)

1. Open [Guided Labs](/labs/guided-labs.md) and launch a small FRR or Alpine pack
2. Or Create blank lab and place two Alpine nodes - [Design mode](/labs/design-mode.md)

### Step 2 - Connect and Start

![Connected topology](https://1807546539-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FhgHCHWL3861o2DBW53aA%2Fuploads%2FHYTisRTZfWZw6CJStLCS%2Fve20261112v5-tutorial-connect.png?alt=media)

1. Connect data ports between nodes
2. Switch to **Operate** -> **Start all**

![Operate Start](https://1807546539-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FhgHCHWL3861o2DBW53aA%2Fuploads%2FD5Bizg5UKcvrUTP0jHMy%2Fve20261112v5-tutorial-operate-start.png?alt=media)

### Step 3 - Open console

![Console docked](https://1807546539-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FhgHCHWL3861o2DBW53aA%2Fuploads%2FGA4RJbvlQLsjeXNNnfbT%2Fve20261112v5-tutorial-console-docked.png?alt=media)

1. Select a running node -> **Terminal**
2. Confirm a prompt - full steps in [Operate and consoles](/labs/operate-and-consoles.md)

### Step 4 - Optional Traffic / Capture

* [Traffic Lens](/labs/traffic-lens.md)
* [Packet capture](/labs/packet-capture.md)

## Before you start

Current OVA/ISO builds ship offline seeds for:

* `quay.io/frrouting/frr:10.2.1`
* `alpine:3.20`

Confirm Docker is up on **Home** Host checks. If Start complains the image is missing:

```bash
sudo vexnx-seed-docker
docker images | grep -E 'frr|alpine'
```

If pull fails with DNS errors, set DNS under **Infrastructure -> Management network**, then seed again. Admins can also use Operate -> More -> Seed Docker images.

## Recipe A: Guided Lab (recommended)

1. Labs -> **Guided Labs** -> Show
2. Domain **Foundations** or **Routing**, rank **Bronze**
3. Open **Guide**, then **Use this lab**
4. Operate -> **Start all** -> **Terminal**
5. On FRR: run `vtysh`, then `show version`

## Recipe B: blank two FRR routers

1. Labs -> **Create blank lab** named `frr-pair`
2. Design: add two **frrouting** nodes
3. Connect their data ports
4. Optionally connect each to a **NAT** cloud for outbound access
5. Operate -> Start
6. Terminal on each node -> `vtysh`

Example:

```
show version
configure
router ospf
 exit
end
```

## Recipe C: Alpine ping

1. Drag two **alpine** (or alpine-docker) nodes
2. Connect them
3. Start -> Terminal -> `ping` the peer (addressing depends on your lab IP plan / DHCP)

## Expected result

* Nodes reach **running** without a registry pull (when seeds loaded)
* `vtysh` or shell responds
* Home Launch Budget shows capacity in use

## Next skills

* Visualize, Present, and Preview before a bigger Start
* Import images for Cisco / Arista
* [Generate Lab](/labs/generate-lab.md) when you have real `show run` text

## If it fails

* Docker off -> Home Host checks / wait for install
* Nested virt / KVM for later QEMU labs -> System requirements
* See Troubleshooting


---

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