> 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/images/catalog-and-compatibility.md).

# Catalog and Compatibility

![Templates catalog](https://1807546539-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FhgHCHWL3861o2DBW53aA%2Fuploads%2FyqxRD2OcGT8oe2QYxRs3%2Fve20261112v5-images-templates.png?alt=media)

## Goal

Read Images -> Catalog / Compatibility correctly, and know what **Certified** means on VEX-NX.

## Where this lives

Sidebar **Images**, then tabs:

| Tab               | Role                                          |
| ----------------- | --------------------------------------------- |
| **Library**       | Disks already registered on this appliance    |
| **Catalog**       | Templates you can place on a lab canvas       |
| **Compatibility** | Support status chips for those templates      |
| **Import**        | Convert & add, upload ready disk, bulk import |

## Compatibility vocabulary

| Status                       | Meaning                                                                                                                                                                                           |
| ---------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| **Certified**                | Honest verification passed on VEX-NX for this template: Start, live terminal (serial / VNC / Docker shell as appropriate), guest config path (or documented N/A), then Stop / Wipe / Start retest |
| **Verified**                 | Partial smoke (for example first boot). Prefer Certified for class when both exist                                                                                                                |
| **Experimental**             | Early or incomplete path - try it, expect tweaks                                                                                                                                                  |
| **Unsupported** / quarantine | Not recommended; often failed validation or blocked import                                                                                                                                        |

Empty status is treated as Experimental in compatibility rows. Always trust the **live chips on your appliance** after an update - do not rely on a printed list from an older guide.

## What Certified does and does not prove

**Does prove:** the platform path for that template on VEX-NX (boot, console path, day-0 / ScriptPad where applicable, wipe retest).

**Does not prove:** every vendor image build, interactive GUI workflows beyond the verified console path, or full protocol labs you design yourself. You still supply legally obtained disks and day-0 credentials.

## Recipe: check a platform before class

1. Open **Images -> Compatibility** (or Catalog)
2. Search the template id (example: `cisco-iosv`)
3. Confirm **Certified** (or accept Verified / Experimental risk)
4. Import your disk under **Import** and bind it in **Library**
5. Run **Validate** in a small lab, then Start once before promising the class

## FOSS Docker starters

FRR / Alpine Docker templates are intended for teaching. Current OVA/ISO media seed offline tarballs; if Start fails on pull, run `sudo vexnx-seed-docker` and check DNS.

## Related

* [Supported images](/images/supported-images.md)
* Import images
* Lab default credentials
* [Operate and consoles](/labs/operate-and-consoles.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/images/catalog-and-compatibility.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.