> 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/faq.md).

# FAQ

![Home - start here for FAQ topics](https://1807546539-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FhgHCHWL3861o2DBW53aA%2Fuploads%2Ffdq0RwLhU4rwIam94Rxy%2Fve20261112v5-home.png?alt=media)

## Do I need vendor images?

For Cisco / Juniper / Fortinet / Palo Alto / similar QEMU labs: **yes**, you supply disks you are entitled to use. FOSS Docker FRR/Alpine starters work without vendor images.

## OVA or USB?

Use **OVA** on VMware. Use **USB bare metal** when you need native KVM for heavy nested guests. Software day-1 is the same.

## Why is nested VT-x required?

QEMU labs need `/dev/kvm`. Inside VMware that means the host must not hold Hyper-V on top of Workstation, and the VM must expose VT-x.

## What do Certified, Verified, and Experimental mean?

Images -> Compatibility shows only these three chips:

* **Certified** - full VEX-NX verification suite passed (boot, wipe, snapshot, clone, export/import, console path, ...). It does **not** mean automated guest login.
* **Verified** - partial / smoke verification; not the full Certified bar.
* **Experimental** - early support; expect tweaks.

List and details: [Catalog and Compatibility](/images/catalog-and-compatibility.md).

## Why does Compatibility still say Experimental for my disk?

Status is per **template**, not per your file. Importing a disk does not upgrade Experimental (or Verified) to Certified.

## FRR Start says image not found

Run `sudo vexnx-seed-docker`. Fix DNS if pulls fail. Current OVA/ISO should include offline tarballs.

## SecureCRT will not open

Install the Console Helper; allow port **8022**; node must be running. HTML5 Terminal always works as fallback.

## Student vs Enterprise

**Student** is free and builtin: core labs, packet capture, running-config and lab bundle import, Assist, and the MCP agent API, capped at 5 concurrent labs / 100 nodes per lab / 1 user with the community template allow-list.

**Enterprise** needs a signed licence file and adds classroom timers, LDAP / SSO / RADIUS, and unlimited labs, nodes, and users. Student already includes the full template catalog. Pro, Academic, Team, and Trial are retired. See [Features](/getting-started/features.md).

## Where is the Admin Guide?

Sidebar -> **Admin Guide** (users, licence, LLM, maintenance, sizing).

## Related

* [Troubleshooting](/getting-started/troubleshooting.md)
* [Quick reference](/getting-started/quick-reference.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/faq.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.