Nexus 9000v in EVE-NG for data centre labs
The Nexus 9000v is in the Add Node list of every CloudLabBox workspace, with 9300v and 9500v images. Use it for NX-OS practice: VLANs, vPC, VXLAN EVPN and data centre routing.
Choose a planCheck it in the free demo
- Vendor
- Cisco
- In Add Node
- 54 images
- Templates
nxosv9ktitanium- Newest
nxosv9k-9500v-10.5.2.F
Installed versions
Every Nexus 9000v name in the Add Node image list, exactly as you’ll pick it.
Started in our checksEach links to the tested tip below.
Template nxosv9k
Nexus 9000v
nxosv9k-9500v-10.5.2.Fnxosv9k-9300v-10.5.2.Fnxosv9k-9500v-10.5.1.Fnxosv9k-9300v-10.5.1.Fnxosv9k-9500v-10.4.3.Fnxosv9k-9300v-10.4.3.Fnxosv9k-9500v-10.4.2.Fnxosv9k-9300v-10.4.2.FStarted in our checksnxosv9k-9500v-10.4.1.Fnxosv9k-9300v-10.4.1.Fnxosv9k-9500v-10.3.3.Fnxosv9k-9300v-10.3.3.F
Show 40 older
nxosv9k-9500v-10.3.2.Fnxosv9k-9300v-10.3.2.Fnxosv9k-9500v-10.3.1.Fnxosv9k-9300v-10.3.1.Fnxosv9k-9500-10.2.3.Fnxosv9k-9300-10.2.3.Fnxosv9k-9500-10.2.2.Fnxosv9k-9300-10.2.2.Fnxosv9k-9500-10.2.1.Fnxosv9k-9300-10.2.1.Fnxosv9k-9500-10.1.2nxosv9k-9300-10.1.2nxosv9k-9500-10.1.1nxosv9k-9300-10.1.1nxosv9k-9500v-9.3.10nxosv9k-9300v-9.3.10nxosv9k-9500-9.3.9nxosv9k-9300-9.3.9nxosv9k-9500-9.3.8nxosv9k-9300-9.3.8nxosv9k-9500-9.3.7anxosv9k-9500-9.3.7nxosv9k-9300-9.3.7anxosv9k-9300-9.3.7nxosv9k-9500-9.3.6nxosv9k-9300-9.3.6nxosv9k-9500-9.3.5nxosv9k-9300-9.3.5nxosv9k-9500v-9.3.4.tarnxosv9k-9300-9.3.4nxosv9k-9500v9.3.3nxosv9k-9500-9.3.3nxosv9k-9300-9.3.3nxosv9k-v9.3.1nxosv9k-9.2.2nxosv9k-9.2.1nxosv9k-7.0.3.I7.10nxosv9k-7.0.3.I7.9nxosv9k-7.0.3.I7.8nxosv9k-7.0.3.I5.2
Template titanium
NX-OSv (Titanium)
titanium-final.7.3.0.D1.1titanium-5.1.2
Add it to a lab
In Add Node, choose the template, then the image. The template fills in these settings; change them before you start the node.
| Image | Template | CPU | RAM | Interfaces | Console |
|---|---|---|---|---|---|
| Nexus 9000v | nxosv9k | 4 | 12288 MB | 8 interfaces | telnet |
| NX-OSv (Titanium) | titanium | 1 | 4096 MB | 4 interfaces | telnet |
EVE-NG admits a node by the CPU and RAM set on it, so a running node counts against your plan at these values. The largest of these templates starts nodes at 4 vCPU and 12,288 MB, more than the free demo’s 6 vCPU and 8 GB, so use the demo to find the image and a plan to run it.
A vPC pair with a dual-homed router
Join two Nexus 9000v switches as a vPC pair with a peer link and keepalive, then dual-home an IOSv router to both over one port-channel. You practise vPC roles, consistency checks and what happens when a link fails.
- 2×Nexus 9000v
nxosv9k4 vCPU, 12288 MB each - 1×IOSv
vios1 vCPU, 1024 MB
Added with these defaults, the lab uses 9 vCPU and 25 GB of RAM. The smallest plan that fits is Professional, with 18 vCPU and 32 GB: £7.50 a day, or £2 an hour On-Demand.
Licences are yours to bring
On NX-OS, features such as VXLAN EVPN belong to Cisco's licence tiers. CloudLabBox doesn't provide Cisco licences, so bring your own where your exercise depends on one.
The images run only inside your CloudLabBox workspace; they aren’t available to download.
Guided labs that use Nexus 9000v
Ready-made labs in the Shared folder of every lab workspace, each with a scenario, tasks, checks and the full solution. Here are 8 of the 17 that use it, from 2 courses, counted on 2 November 2026.
Questions about Nexus 9000v
What is Cisco Nexus 9000v?
The Nexus 9000v is a virtual Nexus 9000 switch running NX-OS, for data centre labs: VLANs, vPC, VXLAN EVPN and the NX-OS CLI. The 9300v and 9500v images follow the two hardware families.
What's the difference between the 9300v and 9500v images?
The 9300v emulates a fixed Nexus 9300 switch and the 9500v a modular Nexus 9500 chassis with line cards. Pick the one that matches the platform you're studying; the node tips note that 9500v needs at least 4 vCPUs.
Why do some images have no 9300v or 9500v in the name?
Names such as nxosv9k-9.2.2 and nxosv9k-7.0.3.I7.9 are older single images. Cisco split the Nexus 9000v into 9300v and 9500v from NX-OS 9.3(1).
What is NX-OSv (Titanium)?
It's the older NX-OSv simulator, which runs NX-OS 7 with the Nexus 7000 command set; the newest installed is titanium-final.7.3.0.D1.1. For NX-OS 9 and 10, use the Nexus 9000v.
Cisco: what does Nexus 10.x need to start?
Matching Nexus 10.x images receive UEFI and CPU compatibility corrections automatically. New Cisco Nexus 9000v nodes default to 4 vCPUs and 12 GB RAM. Standard 10.x needs at least 10 GB, and 9500v needs at least 4 vCPUs. Your account quota still applies. nxosv9k-9300v-10.4.2.F reported NX-OS 10.4(2), line card 1 OK and supervisor 27 active, with both diagnostics passing at 2 vCPUs/12 GB. Choose yes at the POAP abort/setup prompt and create a strong admin password, then save the boot configuration before stopping it.
Cisco: how do I recover a Nexus node that stops at loader>?
Interrupting first-time setup can leave Nexus at loader>. Enter dir, find the exact NX-OS .bin filename, then enter boot <exact .bin filename>. Choose yes at the POAP abort/setup prompt and set a strong admin password; choosing skip can leave an invalid empty admin password that prevents configuration saving. After setup, enter configure terminal, set boot nxos bootflash:<exact .bin filename>, enter end, and run copy running-config startup-config. Confirm the save succeeds. Replace the placeholders with your node's filename. This recovery is manual.
Which Nexus 9000v images are installed?
54 images (52 Nexus 9000v, 2 NX-OSv (Titanium)), all listed on this page exactly as Add Node shows them. The newest is nxosv9k-9500v-10.5.2.F.
How much CPU and RAM does a Nexus 9000v node use?
When you add one, the nxosv9k template adds 4 vCPU and 12288 MB of RAM; the titanium template adds 1 vCPU and 4096 MB of RAM. You can change both in Add Node, and your plan counts what each running node is set to.
More images
CloudLabBox is independent of the vendors named on this page. Their names identify the images in the workspace’s Add Node list.