Networking · Episode 72 · 6:05

Create and troubleshoot Traffic Generator runs

Trace a UDP flow, save it as a reusable profile and check delivery in both directions. Compare request filtering, a blocked reply and a TCP port with no listener. Learn how to set a rate and duration, stop a run and find stored results.

English narration and on-screen explanations. Read the narration transcript.

Chapters and transcript times will be ready shortly. You can use the video’s Play control or open the MP4 below.

Chapters
Open MP4 · Download transcript · English captions

Narration transcript

The English narration in this video. Select a time to watch that moment.

  1. Use Traffic Generator to repeat a TCP or UDP workload and see how your lab handles it.

  2. Start with Trace on the topology. Choose a source, a destination and the UDP port to check.

  3. The result shows both directions. Use the direction buttons to inspect the request or reply on the canvas.

  4. Choose Save as profile to open the Traffic editor with the tested endpoints and port already filled in.

  5. Choose a source interface or address. The editor marks the fields if you enter both.

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

  7. Auto-listener supplies a simulated destination listener for testing the network path.

  8. Save the profile. Each start creates a run with its own counters and results.

  9. Delivered means the destination accepted the request. Read the reply summary to see whether traffic came back.

  10. Compare the sent and delivered packet and byte totals as the run advances.

  11. Use Show path to follow the traffic on the topology. Hide path removes the highlight.

  12. Changes to the saved profile apply to later runs. This run keeps the settings it started with.

  13. This access list blocks the request at the receiving interface. The run shows Filtered and identifies the rule.

  14. Select the change marker to see when the request was blocked. The router also shows matches on the deny rule.

  15. Remove the applied filter to restore delivery, then watch the same run change back to Delivered.

  16. When only the reply is blocked, the run shows One way. Requests can arrive even when replies fail.

  17. Stop the run to settle its counters and store the result.

  18. Create a TCP profile using a destination device and interface. This time set the rate in megabits per second.

  19. A finite duration ends the run automatically. Here it completes with a positive delivered total.

  20. Turn off Auto-listener to check whether the destination has its own listener.

  21. The TCP reset confirms the request reached the destination, but there was no listener on that port.

  22. Reload the lab page. The saved profiles and finished run results are still available.

  23. Delete an unused profile when you are done. Its completed run records stay in the lab.

  24. These results describe simulated delivery. Use packet capture when you need to inspect individual headers.

Back to all Networking videos