Ruby LACP configuration for resilient broadcast audio
Configuring Ruby’s redundant network paths with LACP for uninterrupted AoIP depends on more than pairing Ethernet cables. LACP combines compatible ports into one logical link, but dependable operation needs independent failure domains, correct switch configuration and audio-level protection within the Ruby workflow. Programme audio, talkback, monitoring and control should remain available through credible faults.
Australian stations add practical constraints: facilities may sit in Sydney, Melbourne, Brisbane or Perth, regional sites can lack local technical support, and hot summers or lightning can affect infrastructure. A design that looks redundant on a diagram must be commissioned with the real programme mix, network load and environmental risks in mind.
Why LACP fits a broadcast network
Defined by IEEE 802.3ad and its successor 802.1AX, LACP distributes traffic across member ports and reacts when a link fails. A Ruby installation gains capacity for parallel flows and protection when a cable or port is interrupted, alongside control, file transfers and other IP audio streams.
Yet aggregation is not independence. If both members enter the same access switch, its power supply or one upstream fibre can remove the bundle. Stronger resilience uses separate paths, switches and carriers, or a routed alternative with equivalent failover. Record every failure domain before changing a port setting.
Verify platform and switch support
Confirm that the Ruby hardware, software release and interfaces support the design. LACP differs across platforms, so have Lawo or an authorised broadcast integrator validate whether the topology needs ordinary LACP, multi-chassis aggregation or another method. Settle management, clock and audio VLANs before bundling ports.
At the network edge, members need matching speed, duplex, MTU, VLAN membership and QoS treatment. Use compatible administrative states, permit required VLANs on both ends, and verify a unique actor and partner identity for each bundle. A mismatch can look healthy while causing frame loss, multicast faults or reconvergence instability.
Build the aggregation deliberately
Create the aggregation group at both ends, select active LACP where appropriate, and pair each Ruby interface with its network-side member. Both devices must agree on bundle identity, priority and candidate ports. Manual key selection can make testing and replacement predictable.
Label the bundle and individual ports. Field engineers should be able to trace the Ruby side, patch panel, switch and carrier without undocumented diagrams. Record approved configurations for each switch model and keep management access available under the broadcaster’s security policy.
Do not add a second bond merely because a spare port exists. Unsupported switch designs, mismatched requirements or an accidental loop can turn an availability improvement into an outage. Test with representative cabling, particularly on long outdoor runs.
Manage hashing and multicast audio
Hashing decides which member carries a flow. One multicast audio stream may stay on one link while other traffic uses another, so a bundle can provide failover without doubling that stream’s bandwidth. Symmetric hashing helps prevent imbalance; capacity planning should consider flow count as well as link speed.
IP audio also depends on multicast control, IGMP behaviour and switch replication. Check queriers, snooping and multicast boundaries throughout. Verify PTP distribution and QoS priorities because LACP health says nothing about clock quality or congestion. For speech-led workflows, AutoMix voice automation can operate on stable inputs while monitoring exposes network faults.
Where the studio carries redundant IP audio streams, coordinate their switchover timing with LACP reconvergence and console playout buffers. Link aggregation and stream-level redundancy solve different failure modes and should not be treated as substitutes.
Test failures before they reach air
Test through production failures, not status lights. Disconnect one member, cycle its switch, then interrupt the upstream path while a rehearsal programme runs. Observe LACP state, console and network alarms, talkback, automation and the outbound stream to establish what remains available and how quickly services return.
Measure packet loss, jitter, concealed audio, sync status and switch counters. A short interruption may be acceptable if buffering and redundant-stream options mask it, but that must be proven in the installed configuration. Keep results with the acceptance test.
Repeat tests after firmware updates, port replacements or carrier changes. Australian summer heat can trigger thermal alarms, while lightning events or a mains failure may affect a wider site. These risks deserve test cases because they form part of the real path.
Link studios to transmitter infrastructure
At a multi-site station, the aggregation design should continue beyond the Ruby console. Lawo’s overview of Power Core STLs helps trace studio-to-transmitter audio over IP. The same principles apply: identify the last independent route, monitor each hop and ensure the studio bundle does not terminate in a fragile device.
Local sources can remain on the studio LAN while programme feeds use physically diverse transmitter links, with the boundary documented. For Australian community and commercial stations, this separation must serve modest IT teams as well as engineers. Procedures should identify who may change aggregation keys and how to restore a safe baseline.
Sustain the design in Australia
Long-term support in Australia needs procurement and environmental planning. For equipment sourced from Germany, include customs clearance, GST, any biosecurity checks, freight delays and distributor lead times. Holding spare interface modules, approved switches and documented licences can be more useful than extra capacity that cannot be commissioned.
For distributed contributors and temporary productions, a remote contribution service such as Project VISIT can complement the engineered studio path, but should not replace the engineered LACP core. Credentials, internet quality and the fallback for remote-feed loss need separate planning.
Choose a local integrator familiar with broadcast audio and establish support contacts across Australian and European time zones. Perth’s working day offers limited overlap with European engineering hours, so after-hours support should be agreed in advance. A tested spares list, contact plan and configuration archive make resilience operational.
Ruby’s LACP configuration should be judged by service continuity. Both members may show a synchronised state while programme, talkback and control fail under a fault; meaningful evidence is predictable recovery with understood timing and recorded packet behaviour.
Remember that compatible links, independent failure domains and production-load testing together turn LACP into resilient broadcast operation. That discipline gives Australian broadcasters a clear path from isolated cable faults to dependable daily service.
