WEBVTT 00:00:00.050 --> 00:00:09.550 This tour follows a lab from its first devices to routing, troubleshooting, saved versions, and server design. 00:00:13.600 --> 00:00:22.600 Create a blank lab and give it a name that makes its purpose easy to recognize. 00:00:35.200 --> 00:00:43.200 Open Add device, choose a router, and select a Cisco model from the catalogue. 00:00:55.950 --> 00:01:04.450 Repeat the same workflow with a Juniper router to build a lab with different vendors. 00:01:19.300 --> 00:01:29.800 Add a Linux server to this lab as well; we will use it for the Server Builder example later. 00:01:39.200 --> 00:01:47.700 Open the device terminal to inspect its software version. 00:01:49.250 --> 00:01:59.200 For the Assistant example, start a separate blank lab so the requested four-router topology is easy to follow. 00:02:01.550 --> 00:02:12.550 Ask the Assistant to build four Cisco routers, connect them in a line, and configure OSPF with reachable loopback addresses. 00:02:14.000 --> 00:02:22.950 The Assistant adds and configures the devices through nuLAB, and you can follow its progress here. 00:02:27.200 --> 00:02:36.900 Check the completed topology before moving on: four routers, three links, and the intended interface addresses. 00:02:45.100 --> 00:02:55.100 In the terminal, inspect the OSPF neighbors and routes to confirm that the routers have formed their adjacencies. 00:02:56.100 --> 00:03:05.100 Ping the far router to verify end-to-end connectivity rather than relying only on the topology drawing. 00:03:07.800 --> 00:03:16.550 Configs brings the device configurations into one view, with separate running and saved startup configurations. 00:03:21.800 --> 00:03:28.800 Search the configurations to find the routing settings you want to inspect. 00:03:32.400 --> 00:03:43.900 Events provides a timeline of changes in the lab, with filters to help you focus on the relevant devices and activity. 00:03:50.800 --> 00:04:00.300 To inspect traffic, open Captures and create a named capture on the cable you want to observe. 00:04:00.400 --> 00:04:08.400 Check the capture point and buffer options, then start the capture before generating traffic. 00:04:17.250 --> 00:04:26.750 Return to the router terminal and send a ping across the lab while the capture is running. 00:04:35.850 --> 00:04:44.850 Stop the capture, filter for ICMP, and select a packet to inspect its details and bytes. 00:04:46.500 --> 00:04:56.000 These frames come from the simulated lab traffic, and you can export the capture for later analysis. 00:05:00.850 --> 00:05:09.250 Info organizes the current device state, including interfaces, routes, and routing protocol information. 00:05:12.800 --> 00:05:22.300 Expand the relevant device and use the search and state filters to narrow the information on screen. 00:05:42.350 --> 00:05:51.850 Insights can generate a structured explanation of this lab, helping you review its topology, reachability, and findings. 00:05:52.950 --> 00:06:02.950 Read the explanation alongside the actual configurations and packet results, and verify any suggested changes before applying them. 00:06:06.400 --> 00:06:16.300 Save the working lab as a named version so you have a clear point to return to later. 00:06:18.250 --> 00:06:26.750 The version history keeps saved points together and provides controls for reviewing and restoring them. 00:06:28.400 --> 00:06:37.400 Collaboration brings together access to clone the lab and the review of proposed changes from collaborators. 00:06:37.450 --> 00:06:45.950 Choose access deliberately, and review a collaborator’s proposed changes before merging them into your lab. 00:06:46.150 --> 00:06:55.150 Return to the manual-build lab for the Server Builder example, keeping the four-router OSPF lab separate. 00:07:02.600 --> 00:07:11.100 Server Builder is an Enterprise feature for composing a Linux server design from reusable components. 00:07:14.600 --> 00:07:22.600 Create a design, add a supported component, and review its settings in the editor. 00:07:28.000 --> 00:07:36.500 Save the design, then review the available Linux targets before applying it to a server. 00:07:37.050 --> 00:07:48.150 You have now seen the main lab workflow, from manual and assisted creation to verification, troubleshooting, collaboration, and server design.