Testing Network Redundancy with Power Core and STP
A redundant audio path is useful only when programme survives the failure that matters. With Lawo Power Core, proving that means checking the node, switched network, streams, synchronisation and monitoring together. A useful drill ends with measurable evidence, not merely a reassuring green status light.
Spanning Tree Protocol (STP) prevents loops across bridged Ethernet. With redundant Layer 2 paths, it blocks a loop-prone route and reconverges the topology after a link changes. STP does not replace dual IP routing or redundant audio streams, and it cannot repair damaged fibre. Power Core’s dual IP configuration therefore belongs within an end-to-end failover design.
That matters in Australia, where metropolitan studios in Sydney, Melbourne, Brisbane and Perth serve regional outlets through combinations of leased carrier fibre, microwave and satellite links. Commercial networks, the ABC, SBS Radio and community operators work across long distances, limited on-site support and strict uptime expectations. Teams often describe the exercise as a proper fail-safe drill: run it under programme-like load, not just on a bench.
Why failover needs an audible test
Start with the service the audience receives. Packet-loss graphs and switch logs may show that routing recovered, while listeners still hear a gap, duplicated programme or an incorrect feed. Capture the output of both active and standby paths at the Power Core, then compare them with a reference source using millisecond-accurate timestamps.
Processing can also alter what staff hear during a changeover. Lawo’s explanation of acoustic feedback control shows how AutoMix responds in live studio conditions. Record processing states, gain changes and fader positions during the test so that an audible artefact can be traced to the correct layer.
How dual IP and STP work together
Power Core’s dual IP configuration defines primary and secondary IP paths for the node and its audio services. These paths may use separate interfaces, VLANs or routed links, so the commissioning documentation must identify the addresses, ports, streams and routes expected to remain active after a failure. Testing must cover IP reachability and media delivery together; a healthy control connection can conceal a failed audio route.
STP operates below IP and manages the switched Layer 2 topology. It keeps redundant links from creating a forwarding loop, then changes the topology when a preferred path disappears. Classic STP can introduce a noticeable forwarding pause, while RSTP and careful topology design can shorten recovery. Neither mechanism guarantees uninterrupted audio without an established backup stream or suitable endpoint behaviour.
Lawo’s wider product and technology background is available in about Lawo, while the approved Power Core configuration should remain the authority for the installed network design.
Preparing a controlled redundancy test
Use a maintenance window, spare routes and an out-of-band control connection. Document the baseline topology, IP addresses, VLANs, QoS settings, stream subscriptions and synchronisation status before making changes. Run the test with realistic programme levels and metadata while engineers monitor the source, Power Core outputs and downstream receivers.
Verify the physical layer before diagnosing IP behaviour. Check fibre power, optical errors, connector cleanliness, transceiver compatibility and copper link status. Specialist photonics resources such as photonics test tools can support optical measurements, provided they are used according to the installed equipment specifications.
Plan individual failures rather than pulling every connection at once. Suitable scenarios include removing one fibre path, restarting a switch, failing an uplink and restoring a link after convergence. Repeatedly flapping a path can expose unstable recovery, duplicate packets or forwarding loops. Record each action against audio, packet and switch-log timestamps.
Measuring recovery and audio continuity
Define the acceptable audio interruption, recovery time and restoration behaviour before testing. Measure when the first affected packet was lost, when the standby path became usable, when audio returned and whether the restored path remained stable. Retain packet captures, interface counters, gateway logs, alarm records and audio files for later comparison.
Treat network convergence and audio continuity as separate results. An already-established backup stream may keep the receiver supplied while STP changes the physical topology. If the endpoint must create or restore a session, the audio gap will include application recovery time. Any claimed hitless failover should therefore be supported by measurements rather than inferred from a successful route change.
Comparing the expected failure behaviour
A baseline run confirms that the intended primary path carries the programme and that standby resources are healthy. During subsequent tests, compare both the dual-IP outcome with the switch topology’s STP response. A temporary audio interruption may be acceptable, but duplicate programme, traffic instability or inconsistent behaviour across sites is not.
| Failure scenario | Expected dual-IP behaviour | STP or topology check | Evidence to retain |
|---|---|---|---|
| Normal operation | Primary and standby paths remain correctly configured | No unexpected blocking or route changes | Throughput, packet loss, jitter and clock status |
| One link removed | The surviving path becomes usable | Blocked path may unblock as the topology reconverges | Changeover time, audio continuity and interface errors |
| Failed link restored | Traffic returns to its intended state | No loop, duplicate stream or forwarding storm | Duplicate packets, switch load and stability |
| Switch failure | Power Core reaches the surviving route | Topology converges according to the design | Session recovery time, audio gap and alarms |
| Repeated link flapping | Failover remains bounded and repeatable | No oscillation or unstable forwarding | Recovery times, logs and operator interventions |
The standard a redundancy drill should meet
Redundancy is a system behaviour, not a feature that can be confirmed by checking two cables. The drill must demonstrate that the node, network, streams and receivers recover in a predictable order under realistic load.
What the reader should remember is that Power Core’s dual IP configuration and STP work together only when their responsibilities, limitations and recovery times are understood. A credible test proves bounded recovery, acceptable audio continuity, clean restoration and repeatable evidence that the standby system will perform when it matters.
