> 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/operate-and-consoles.md).

# Operate and consoles

**Operate** is for lifecycle and consoles: Start, Stop, Wipe, and the Terminal workspace.

## Start, Stop, Wipe

| Action                         | Effect                                                                       |
| ------------------------------ | ---------------------------------------------------------------------------- |
| **Start all** / Start selected | Boot QEMU or Docker nodes                                                    |
| **Stop**                       | Graceful shutdown                                                            |
| **Wipe**                       | Stop and clear runtime overlay; lab startup configs in the definition remain |

Wipe after nested-virt fixes, image changes, or stuck containers.

Capacity warnings may appear if the VM is undersized - raise resources or stop other labs.

## Open the Terminal workspace

1. Switch to **Operate**.
2. Click **Terminal** on the toolbar to show the workspace (empty until you open sessions).
3. **More -> Open all in Terminal** attaches every running node that has a console.
4. Or right-click a running node -> **Terminal...** / Connect actions.

You can also open a console in a separate browser tab when the node exposes a URL.

### Dock, float, maximize (Terminal only)

These controls apply to the **Terminal** workspace (consoles), not to **VEX-NX Assist**.

* In **Focus**, the terminal often **docks** beside the topology. Use **Float** to overlay the canvas.
* Outside Focus, the terminal floats by default; use **Dock** when available in Focus Studio.
* **Maximize** expands a floating terminal.

Assist has its own Dock / Rail / Hide controls - see [Using Assist](/assist/using-assist.md).

Chrome (tabs, Glass, Colors, Hide) stays clickable even when panes are translucent.

## Glass vs Click through

These two controls are easy to confuse:

| Control           | What it does                                                                                                                                                        |
| ----------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| **Glass**         | Makes the terminal **background translucent** so you can see topology under it. Text stays readable; you still click inside the panes.                              |
| **Click through** | Only while Glass is on. Terminal **panes ignore mouse clicks** so you can pan/select the canvas underneath. Title bar and Glass / Click through buttons still work. |

Opacity also has a slider under **Colors** (appearance). Glass is a quick toggle to a translucent preset; turn Glass off for a solid background again.

## Broadcast

With several text consoles open, the broadcast bar can send the same keystrokes to selected sessions. Use it for parallel lab setup; double-check which tabs are selected before you paste destructive commands.

## Console types

| Type          | Typical use                                               |
| ------------- | --------------------------------------------------------- |
| Serial / text | IOS, EOS, Junos CLI, Linux shell                          |
| VNC           | Graphical guests                                          |
| Docker        | Container shell - on FRR, run `vtysh` for the routing CLI |

Template **primary** console is the default Connect action. QEMU still starts both serial and VNC; when both are available, **Terminal...** also offers **Open serial** and **Open VNC**.

## Console troubleshooting (short)

| Symptom                    | Try                                                 |
| -------------------------- | --------------------------------------------------- |
| Blank Docker console       | Wipe + Start; confirm image present; reopen         |
| IOSv stuck on "Booting..." | Nested KVM on; Wipe; wait (TCG is slow without KVM) |
| CDP but no ping            | Wipe both peers; check MACs / fabric                |

More detail: [Troubleshooting](/reference/troubleshooting.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/operate-and-consoles.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.