Save your work and pull a tech-dump

Fundamentals
Beginner
6 min
3 steps
Cisco IOS-style

Persist the running config to startup, walk session history, and pull a tech-support concat — the three CLI moves you'll do at the end of every change window.

Open this lab in your browser →

Free · no install · no account

Scenario

Two persistence layers exist: - Running config — the live, in-memory configuration. Every command you type lands here immediately. - Startup config — what the box loads on boot. After making changes, you copy running-config startup-config (short: wr m / write memory) to make them survive a reload. Forget this and your "fix" disappears the next time the box reboots. Beyond CLI, netverdict's workspace also offers (without grading here): - ⤓ config in the Inspector side-drawer — downloads <hostname>-running-config.txt. - Save scenario — bundles topology + per-device CLI history into a .netverdict.json you can share or stash. - Export pcap — every frame the sim has captured, opens cleanly in Wireshark.

Topology

1 × router · Cisco IOS-style

R1 — router

What you will do

Persist the running config to startup. Either copy running-config startup-config or the shorter write memory (wr m).
Type show history to see every command this session has issued.
Pull a tech-support dump: show tech-support. It concatenates running-config + ip route + ip int brief + interfaces + arp.

Open this lab in your browser →

Save your work and pull a tech-dump

Scenario

Topology

What you will do

More labs on this topic

This lab in other languages