Network Testing (Load Test)
Network Testing drives synthetic signalling load at a live core so you can measure how it behaves under stress. It is powered by the RAN Simulator: virtual eNodeBs and UEs that exercise the full radio→core path (S1AP/NAS, GTP-U, IMS) rather than a single interface.
The Network Testing group in the sidebar collects the RAN Simulator load-test tools:
| Sub-tab | What it does |
|---|---|
| RAN Load Test | Recent load-test jobs — attaches, data sessions and IMS registrations run against the core, with their results and a downloadable pcap. |
| Scenario Schedules | Define recurring scenario runs (e.g. an hourly attach batch), run one now, and browse the run history. Results are exported to Prometheus for alerting. |
| RAN Simulator | Stand up virtual eNodeBs/gNodeBs and UEs and drive them directly. |
| RAN Radio | Multi-RAT radio control (5G NR / 2G GERAN / 3G UTRAN). |
| RANsimware — IMS | IMS registration and VoLTE load across the simulated fleet. |
All of these are documented in depth in RAN Simulator.
Pointing a run at a core
When you turn up a cell, OmniWeb offers a dropdown of the core nodes it can dial — every MME, AMF and STP it finds across your site inventories — so you point the run at the right core (mme_ip / amf_ip / stp_ip) instead of typing an IP. With no inventory configured, the field falls back to free text.
Typical use
- Open RAN Simulator, turn up an eNodeB/gNodeB and point it at the core to test.
- Attach a batch of UEs and run a scenario (attach, data, IMS register, VoLTE, or an outage scenario).
- Watch the results and, for signalling detail, download the run's pcap.
- For routine coverage, save the scenario as a Scenario Schedule so it runs on an interval and exports pass/fail to Prometheus.
Related
- RAN Simulator: virtual eNodeBs/UEs for functional and load testing across the whole radio→core path.
- Grafana Dashboards & Statistics: scenario pass/fail and timing are exported to Prometheus; use Grafana for the full picture during a test.