Real devices
Cisco IOSv and IOSvL2, FortiGate, VPCS and graphical Linux guests, or any virtual disk you import.
NOVA NETWORK LAB
A network lab that runs on your own computer: real router, switch and firewall consoles, labs on a world map linked with real latency, and a datacenter you can walk into.
01 / DESIGN
Draw a topology or arrange the same appliances in racks. Both views share the same devices, ports, power and cables, and every lab keeps its own topology, room and disks.
02 / RUN
Bring your own images: Cisco IOSv and IOSvL2, FortiGate, Linux and VPCS. Each device has its own console: float it, tab it, or open it in its own window.
HQ-R1#show ip ospf neighbor Neighbor ID Pri State Dead Time Address Interface 2.2.2.2 1 FULL/DR 00:00:36 172.16.21.2 Gi0/2 2.2.2.2 1 FULL/DR 00:00:34 172.16.12.2 Gi0/1 HQ-R1#ping 10.2.2.10 Sending 5, 100-byte ICMP Echos to 10.2.2.10, timeout is 2 seconds: !!!!! Success rate is 100 percent (5/5), round-trip min/avg/max = 5/20/69 ms HQ-R1#
03 / CONNECT
Pin every lab to a real place and link labs across the map. Delay, jitter, loss, bandwidth and fibre distance apply to the actual traffic.
04 / DATACENTER
Walk the cold aisle. Racks, power leads, PDUs, patch panels and transceivers are all modelled, and power, heat and airflow are simulated cabinet by cabinet.
05 / FAILOVER
Cut, black-hole or flap any link. BFD notices in 150 ms, OSPF reroutes, and the backup takes the traffic.
06 / OBSERVE
NOVA reads the frames on every link and names what it finds, layer by layer. Follow a label across an MPLS core: pushed, swapped, popped.
07 / AUTOMATE · MCP
NOVA speaks MCP. Claude, Codex or any MCP client can build labs, link sites and work the consoles while you watch.
Claude · Codex · any MCP client connected
nova_api create lab "Branch Slatina" · SL-R1, SL-SW1 nova_api link SL-R1 ↔ HQ-R2 (Bucharest) nova_console SL-R1 show ip ospf neighbornova_api create lab "Branch Craiova" · link to SL-R1, HQ-R1 nova_api test failover SL-R1 ↔ HQ-R2EVERYTHING IN THE BOX
Cisco IOSv and IOSvL2, FortiGate, VPCS and graphical Linux guests, or any virtual disk you import.
Delay, jitter, loss, bandwidth and fibre distance on the actual traffic.
150ms
Cut, black-hole or flap a link; BFD notices and the routing protocols move the traffic.
Racks, power leads, PDUs, patch panels and transceivers, with power, heat and airflow modelled cabinet by cabinet.
Strip the jacket, put the eight conductors in T568B order, crimp, and let the tester find the faults.
Each lab keeps its topology, room, VM settings and private disks.
Capture what crosses a link, see each protocol by name and export a PCAP.
Claude, Codex or any MCP client can build labs, link sites and type in the consoles while you watch.
A topology and a 3D room on the same devices, ports, power and cables.
HQ-R1# show ip route ospf O 10.2.0.0/16 [110/2] via 172.16.12.2
Float them, tab them or open native windows.
RAM, CPU, NICs, disks and boot order while a guest is stopped.
An Ethernet fabric that forwards real frames: a pulled cable is a dead link.
THE FILM
Made entirely in code with three.js, the same engine as NOVA's 3D: no screenshots, no stock footage.