WEBVTT

1
00:00:03.450 --> 00:00:13.950
Use Timeline to see what changed in a lab, replay a failure and follow a packet hop by hop.

2
00:00:25.850 --> 00:00:33.850
A repeatable traffic run gives us a steady workload to observe during the investigation.

3
00:00:35.400 --> 00:00:44.400
Open an eligible lab you own on Pro or higher, then verify a successful connectivity baseline.

4
00:00:49.600 --> 00:00:55.600
In Traffic, choose New profile and name this UDP workload.

5
00:00:55.750 --> 00:01:02.250
Choose a source device and interface, then enter the destination address.

6
00:01:02.350 --> 00:01:11.350
Set the ports, packet size and rate, then leave the duration blank for a continuous run.

7
00:01:16.150 --> 00:01:25.150
Enable the simulated listener, correct any highlighted errors and reopen the saved profile to check it.

8
00:01:28.900 --> 00:01:37.400
Start the profile and locate its run card; these are modeled results inside your lab.

9
00:01:37.500 --> 00:01:46.500
Read the verdict with the sent and delivered packet and byte totals as the run advances.

10
00:01:53.550 --> 00:02:01.550
Show path highlights the current route on the topology, and Hide path clears it.

11
00:02:06.000 --> 00:02:15.500
The run timeline marks its start and later changes; select a marker to read the associated detail.

12
00:02:43.200 --> 00:02:51.700
Apply a temporary access list that blocks this UDP destination port while permitting other traffic.

13
00:02:55.250 --> 00:03:02.300
The run reports Filtered, and its change marker shows when delivery stopped.

14
00:03:15.500 --> 00:03:25.500
Select the change to read why traffic was filtered, then verify the access-list match counter in a terminal.

15
00:03:43.450 --> 00:03:51.450
Remove the applied access list and verify that the same run returns to Delivered.

16
00:03:55.100 --> 00:04:02.600
Stop the run when finished, then confirm its ended state and settled counters.

17
00:04:09.200 --> 00:04:19.700
Create a TCP profile using a destination device and interface, and choose megabits per second as its rate unit.

18
00:04:37.700 --> 00:04:46.700
Set a short duration to make the run finish automatically; confirm Completed and its delivered volume.

19
00:04:58.550 --> 00:05:07.050
Compare No listener and its TCP reset reply with the filtered path, then restore Auto-listener.

20
00:05:13.900 --> 00:05:21.900
Reload the page to confirm that saved profiles and finished runs are still available.

21
00:05:27.000 --> 00:05:34.500
Open Timeline and use the Live and Replay controls beside the recording picker.

22
00:05:36.350 --> 00:05:43.850
The time axis and playhead show where you are in the retained recording.

23
00:05:43.900 --> 00:05:51.500
Links, routing, device logs, generator runs and recording events have their own lanes.

24
00:05:53.050 --> 00:05:59.050
Expand a lane to see which devices contributed its events.

25
00:06:11.100 --> 00:06:16.600
The Traffic histogram shows where packet activity is concentrated.

26
00:06:18.650 --> 00:06:27.150
Select a recorded event to see its detail and move the playhead to its time.

27
00:06:29.350 --> 00:06:36.850
Search the events by text, such as the access list that blocked delivery.

28
00:06:39.100 --> 00:06:47.100
Filter by Family to focus on traffic-generator changes instead of the whole event list.

29
00:06:47.200 --> 00:06:55.700
Use the Device filter to narrow the investigation to the device involved in the problem.

30
00:06:55.850 --> 00:07:03.850
Severity limits the list to warnings or errors, while alert diamonds also mark drops.

31
00:07:03.950 --> 00:07:12.950
Reset filters clears the search and selections so you can see the full event list again.

32
00:08:07.500 --> 00:08:16.000
After shutting and restoring the receiving interface, check the Routing events and see what changed.

33
00:08:20.350 --> 00:08:29.350
Seek back to the outage to see the cable down after the live lab has recovered.

34
00:08:29.650 --> 00:08:39.650
Pause replay to inspect a moment while the live workload continues, or press Play to follow recorded events.

35
00:08:42.500 --> 00:08:51.500
Change playback speed to review a longer interval, then return to normal speed for closer inspection.

36
00:08:51.600 --> 00:09:01.100
Use arrows for adjacent markers, Home and End for the range, and press L to return Live.

37
00:09:01.200 --> 00:09:07.700
Live path highlighting gives way to the recorded view during replay.

38
00:09:20.650 --> 00:09:28.150
Return Live to verify the repaired interface, the routing adjacency and successful pings.

39
00:09:31.450 --> 00:09:39.450
When filtering by device, read its coverage note to see what Timeline leaves out.

40
00:09:43.900 --> 00:09:52.900
Switch to Packets to browse recorded traffic, and search for the ping from the source router.

41
00:09:54.250 --> 00:10:02.250
Select a recorded packet to open Packet Journey and see the devices it reached.

42
00:10:03.750 --> 00:10:11.250
Step forward or backward through the packet journey to inspect its reconstructed path.

43
00:10:50.150 --> 00:10:57.650
A dropped packet appears in Alerts, and Packet Journey shows where it stopped.

44
00:11:19.300 --> 00:11:28.300
This lab keeps up to one hour of history, which clears on unload or server restart.

45
00:11:28.400 --> 00:11:37.400
Compare the run result, its change markers and the lab Timeline, then verify the live repair.

46
00:11:42.900 --> 00:11:50.400
Use packet capture for packet-level detail and stop the generator when you finish.
