Add scripts/generate_traffic.sh: iperf3 traffic generator DC↔Campus over gold VRF #55

New Issue

Damien · 2026-07-20T15:55:14Z

Damien commented

2026-07-20 15:55:14 +00:00

Problem

network-multitool hosts sit idle unless someone manually pings/iperfs
them. This makes IPFabric ARP/MAC tables, Grafana throughput graphs, and
the weathermap panel look empty/stale by default — every demo currently
needs a manual traffic-generation step first (see troubleshooting done in
chat: hosts missing from IPFabric Inventory → Hosts table until traffic
was generated and a new snapshot taken).

Expected outcome

New scripts/generate_traffic.sh:

Starts iperf3 -s in the background on the DC gold-VRF servers:
dc-server2 (10.34.34.102), dc-server4 (10.78.78.104).
Runs iperf3 -c clients from the paired campus gold-VRF hosts:
campus-host1 (10.60.60.101) → dc-server2, campus-host2
(10.60.70.102) → dc-server4. Exercises the full DC→Core→Campus
stitched EVPN Type-5 path end to end.
Duration passed as a script argument.
Live terminal dashboard: server list + real-time Mbps per client
session, refreshed continuously for the run duration (parse iperf3
-i 1 --json streaming output, no raw log dump).
Cleans up server-side iperf3 -s processes on exit (including
Ctrl-C/duration end).

Document usage in scripts/README.md alongside the existing
generate_weathermap.py entry.

Non-goals

Not touching VLAN 40 (dc-server1/dc-server3, VRF default, no
gateway) — gold VRF only, per stitched end-to-end path in README.
Not adding scheduling/automation — manual invocation only, like
generate_weathermap.py today.

## Problem `network-multitool` hosts sit idle unless someone manually pings/iperfs them. This makes IPFabric ARP/MAC tables, Grafana throughput graphs, and the weathermap panel look empty/stale by default — every demo currently needs a manual traffic-generation step first (see troubleshooting done in chat: hosts missing from IPFabric Inventory → Hosts table until traffic was generated and a new snapshot taken). ## Expected outcome New `scripts/generate_traffic.sh`: - Starts `iperf3 -s` in the background on the DC gold-VRF servers: `dc-server2` (10.34.34.102), `dc-server4` (10.78.78.104). - Runs `iperf3 -c` clients from the paired campus gold-VRF hosts: `campus-host1` (10.60.60.101) → dc-server2, `campus-host2` (10.60.70.102) → dc-server4. Exercises the full DC→Core→Campus stitched EVPN Type-5 path end to end. - Duration passed as a script argument. - Live terminal dashboard: server list + real-time Mbps per client session, refreshed continuously for the run duration (parse iperf3 `-i 1 --json` streaming output, no raw log dump). - Cleans up server-side `iperf3 -s` processes on exit (including Ctrl-C/duration end). Document usage in `scripts/README.md` alongside the existing `generate_weathermap.py` entry. ## Non-goals - Not touching VLAN 40 (`dc-server1`/`dc-server3`, VRF default, no gateway) — gold VRF only, per stitched end-to-end path in README. - Not adding scheduling/automation — manual invocation only, like `generate_weathermap.py` today.

Damien added reference feat/iperf-traffic-generator

2026-07-20 16:07:44 +00:00

Damien referenced this issue from a commit

2026-07-20 16:13:46 +00:00

Add iperf3 traffic generator for DC<->Campus gold VRF path

Damien referenced a pull request that will close this issue

2026-07-20 16:14:09 +00:00

Add iperf3 traffic generator for DC<->Campus gold VRF path #56

Damien closed this issue

2026-07-20 16:15:20 +00:00

Sign in to join this conversation.