WEBVTT

1
00:00:00.100 --> 00:00:09.600
Use Traffic Generator to repeat a TCP or UDP workload and see how your lab handles it.

2
00:00:11.250 --> 00:00:20.750
Start with Trace on the topology. Choose a source, a destination and the UDP port to check.

3
00:00:24.500 --> 00:00:34.500
The result shows both directions. Use the direction buttons to inspect the request or reply on the canvas.

4
00:00:37.400 --> 00:00:47.400
Choose Save as profile to open the Traffic editor with the tested endpoints and port already filled in.

5
00:00:49.550 --> 00:00:58.050
Choose a source interface or address. The editor marks the fields if you enter both.

6
00:00:58.150 --> 00:01:09.650
Set the packet size and rate. Leave duration empty to run until you stop it or the one-hour limit is reached.

7
00:01:09.750 --> 00:01:16.750
Auto-listener supplies a simulated destination listener for testing the network path.

8
00:01:17.450 --> 00:01:25.450
Save the profile. Each start creates a run with its own counters and results.

9
00:01:27.350 --> 00:01:36.850
Delivered means the destination accepted the request. Read the reply summary to see whether traffic came back.

10
00:01:36.900 --> 00:01:44.400
Compare the sent and delivered packet and byte totals as the run advances.

11
00:01:47.850 --> 00:01:56.350
Use Show path to follow the traffic on the topology. Hide path removes the highlight.

12
00:02:02.950 --> 00:02:12.450
Changes to the saved profile apply to later runs. This run keeps the settings it started with.

13
00:02:30.250 --> 00:02:40.250
This access list blocks the request at the receiving interface. The run shows Filtered and identifies the rule.

14
00:02:53.800 --> 00:03:04.800
Select the change marker to see when the request was blocked. The router also shows matches on the deny rule.

15
00:03:22.700 --> 00:03:31.700
Remove the applied filter to restore delivery, then watch the same run change back to Delivered.

16
00:03:50.200 --> 00:04:00.200
When only the reply is blocked, the run shows One way. Requests can arrive even when replies fail.

17
00:04:04.300 --> 00:04:10.800
Stop the run to settle its counters and store the result.

18
00:04:31.950 --> 00:04:42.450
Create a TCP profile using a destination device and interface. This time set the rate in megabits per second.

19
00:04:56.250 --> 00:05:04.750
A finite duration ends the run automatically. Here it completes with a positive delivered total.

20
00:05:06.000 --> 00:05:13.000
Turn off Auto-listener to check whether the destination has its own listener.

21
00:05:23.550 --> 00:05:33.050
The TCP reset confirms the request reached the destination, but there was no listener on that port.

22
00:05:37.400 --> 00:05:45.400
Reload the lab page. The saved profiles and finished run results are still available.

23
00:05:47.150 --> 00:05:56.150
Delete an unused profile when you are done. Its completed run records stay in the lab.

24
00:05:56.200 --> 00:06:05.150
These results describe simulated delivery. Use packet capture when you need to inspect individual headers.
