Investigate lab traffic with Timeline Use Timeline to see what changed in a lab, replay a failure and follow a packet hop by hop. A repeatable traffic run gives us a steady workload to observe during the investigation. Open an eligible lab you own on Pro or higher, then verify a successful connectivity baseline. In Traffic, choose New profile and name this UDP workload. Choose a source device and interface, then enter the destination address. Set the ports, packet size and rate, then leave the duration blank for a continuous run. Enable the simulated listener, correct any highlighted errors and reopen the saved profile to check it. Start the profile and locate its run card; these are modeled results inside your lab. Read the verdict with the sent and delivered packet and byte totals as the run advances. Show path highlights the current route on the topology, and Hide path clears it. The run timeline marks its start and later changes; select a marker to read the associated detail. Apply a temporary access list that blocks this UDP destination port while permitting other traffic. The run reports Filtered, and its change marker shows when delivery stopped. Select the change to read why traffic was filtered, then verify the access-list match counter in a terminal. Remove the applied access list and verify that the same run returns to Delivered. Stop the run when finished, then confirm its ended state and settled counters. Create a TCP profile using a destination device and interface, and choose megabits per second as its rate unit. Set a short duration to make the run finish automatically; confirm Completed and its delivered volume. Compare No listener and its TCP reset reply with the filtered path, then restore Auto-listener. Reload the page to confirm that saved profiles and finished runs are still available. Open Timeline and use the Live and Replay controls beside the recording picker. The time axis and playhead show where you are in the retained recording. Links, routing, device logs, generator runs and recording events have their own lanes. Expand a lane to see which devices contributed its events. The Traffic histogram shows where packet activity is concentrated. Select a recorded event to see its detail and move the playhead to its time. Search the events by text, such as the access list that blocked delivery. Filter by Family to focus on traffic-generator changes instead of the whole event list. Use the Device filter to narrow the investigation to the device involved in the problem. Severity limits the list to warnings or errors, while alert diamonds also mark drops. Reset filters clears the search and selections so you can see the full event list again. After shutting and restoring the receiving interface, check the Routing events and see what changed. Seek back to the outage to see the cable down after the live lab has recovered. Pause replay to inspect a moment while the live workload continues, or press Play to follow recorded events. Change playback speed to review a longer interval, then return to normal speed for closer inspection. Use arrows for adjacent markers, Home and End for the range, and press L to return Live. Live path highlighting gives way to the recorded view during replay. Return Live to verify the repaired interface, the routing adjacency and successful pings. When filtering by device, read its coverage note to see what Timeline leaves out. Switch to Packets to browse recorded traffic, and search for the ping from the source router. Select a recorded packet to open Packet Journey and see the devices it reached. Step forward or backward through the packet journey to inspect its reconstructed path. A dropped packet appears in Alerts, and Packet Journey shows where it stopped. This lab keeps up to one hour of history, which clears on unload or server restart. Compare the run result, its change markers and the lab Timeline, then verify the live repair. Use packet capture for packet-level detail and stop the generator when you finish.