WATCH. LEARN. TRY IT.

Video tutorials

See how to use nuLAB, one workflow at a time. Watch every episode without signing in.

Showing 21–30 of 146 videos to explore

2:35

Reset and delete labs deliberately

Labs · Episode 07

Save the device configuration you want to keep, compare saved startup configuration with an unsaved running change, and review Reset Lab. Cancel first, then reset the lab and check that the device returns to its saved configuration. Reset reboots the devices and discards unsaved device configuration. The permanent-deletion section from 1:52 shows the earlier My Labs workflow and is historical. My Labs now moves labs to seven-day Trash; watch the current Trash and restore tutorials linked on this page. The original recording is preserved.

1:43

Connect and reconnect devices

Labs · Episode 09

Use Connection Builder to choose two devices and a free interface at each end. Swap the device selections, then close the builder without making a connection. Create a cable and see that its occupied ports no longer appear in the free-interface lists. Review the disconnection confirmation, cancel to keep the cable, then confirm its removal. Reconnect using a different free port on each device, and reopen the lab to check the saved connection. This walkthrough uses two simulated routers. Cabling alone does not configure device addressing. Configure interface addressing and interface state separately before testing traffic.

2:15

Power cycle and reload a router

Labs · Episode 10

Save a router configuration before restarting it, then make an unsaved description change. Use the topology toolbar to power the selected router off and see that its terminal becomes unavailable. Reopen the lab to check the powered-off state, then power on and verify that startup restores the saved description and interface address. In the terminal, review the reload confirmation, type n to cancel, then run reload again and press Enter to confirm. Check the saved configuration in a fresh terminal. This walkthrough uses one simulated IOSv router; command syntax and boot behavior vary by device.

2:19

Inspect live device state with Info

Labs · Episode 11

Open Info and expand a router to inspect its physical interface addresses, administrative and operational status, and connected routes. Compare the displayed route with real terminal output. Search for an address, use Enter and Shift Enter to navigate matches, and clear the search. Hide and restore an information category, then collapse and expand the device tree. Change the physical and loopback addresses in the native terminal, refresh Info, and verify the new address and route. This walkthrough uses one simulated IOSv router; available information depends on the device and its configured capabilities.

About these tutorials

Training Platform

These tutorials use personal prepared labs, compatible active-member seats and distinct accepted accounts per UTC calendar month. Invitations do not consume monthly seats; removing a member does not refund a monthly seat. Shared Training Platform libraries and billing/grants remain deferred.

Live sharing shows topology and terminal output. Built-in audio and video are unavailable; arrange voice separately. English on-screen explanations. Watching is free; using Training Platform features needs an account and an appropriate plan.

Earlier recordings use the previous School name for the Training Platform.

Labs

Build a topology, connect devices, configure addressing and test connectivity. Arrange the canvas, add notes and zones, then reopen your saved lab. Follow each workflow using chapters and written explanations.

Watching is free. Create a nuLAB account to try the demonstrated workflow.

Marketplace

Find free and credit-priced Marketplace lab packs in the portal Knowledgebase. Check prerequisites, device limits and the displayed price, then install an independent lab copy. Prices and availability vary.

Watching is free. Sign in with an account that supports the selected pack to try the workflow. The free-lab demo spends zero credits; the credit-pack demo uses a labeled 20-credit listing and demo credits, with no payment checkout completed.

Traffic capture

Capture traffic on a cable, inspect packet fields and bytes, filter the display, follow an observed path and export all or displayed frames as PCAP. Frames are reconstructed simulation observations; temporary capture buffers are not preserved by saving a lab.

Watching is free. Using Traffic capture requires a nuLAB account with Pro or above.

Networking

Identify connected neighbors and address mappings, inspect physical ports and test reachability. Follow prepared lab examples using chapters and narration transcripts. A cached address mapping alone does not prove a working link; supported syntax and behavior vary by device.

Watching is free. Create a nuLAB account with a suitable device allowance to try the demonstrated lab workflows.

IoT

Configure sensors, follow MQTT topics and inspect delivery in a prepared lab. This example uses the in-lab QoS 0 client, Sparkplug-JSON messages and a preconfigured secured broker.

Watching is free. Using IoT Operations requires a nuLAB Enterprise account and supported devices.

Account

Read your dashboard summary, create and reopen a lab, then find Knowledgebase, Marketplace and Plan & billing. Device capacity and AI credits are separate; Time spent and Last used describe different parts of your lab activity.

Watching is free. Sign in to your nuLAB account to try the workflow. This recording uses a demonstration environment with purchasing disabled; account values and available options may differ. Signup, purchases and credit top-up are covered separately.

Integrations

Use nuLAB Gateway with an external SSH terminal, save a device change and confirm it in your browser. This macOS example starts with Gateway installed and paired; installation and account approval are prerequisites.

Watching is free. Use the Gateway build for your computer and a supported lab device. Gateway account approval and the device’s own login are separate. Gateway can keep accessing the active lab after the browser closes.