Troubleshooting AVB discovery in a mixed Lawo and third-party network
A mixed audio network can appear healthy while discovery fails. Link lights may be active, computers may reach the same IP range, and audio may still remain invisible because AVB relies on precise Layer 2 protocols, clock timing, VLAN behaviour and stream reservation. Lawo equipment also commonly operates with RAVENNA or AES67 workflows, so the first task is confirming that every device is speaking a compatible protocol. Learn more about Automix.
This matters in Australian broadcast environments, where a studio in Sydney may share infrastructure with remote production, a Melbourne facility may have third-party control hardware added over time, or a Perth site may depend on carefully managed links to eastern states. Treat discovery as a sequence of verifiable services rather than a single setting, and the fault becomes easier to localise.
Establish the audio standard first
AVB is an Ethernet-based media transport family built around standards such as IEEE 802.1AS for timing, IEEE 802.1Qat for stream reservation and IEEE 1722 for media transport. RAVENNA and AES67 use different mechanisms, even though they can carry comparable professional audio signals. A Lawo Power Core audio engine should therefore not be assumed to discover an AVB endpoint simply because both devices use gigabit Ethernet.
Check the exact protocol modes supported by each device, including optional cards, firmware versions and licences. Some third-party interfaces advertise AES67, Ravenna, Dante or AVB as separate operating modes. If an endpoint cannot operate in the same discovery and transport ecosystem, use a suitable bridge or redesign the signal path rather than trying to force discovery through unrelated multicast settings.
Record the expected audio direction, sample rate, channel count and clock source. A device configured for 48 kHz may be visible but unusable when the network expects another rate. Likewise, a stream that requires AVB reservation cannot be treated as an ordinary unicast or unmanaged multicast flow.
Check the physical and clocking layers
Begin with the simplest physical checks: link speed, duplex status, fibre transceivers, switch port errors and cable condition. Managed switches should show whether ports are forwarding, blocking or repeatedly renegotiating. For Australian venues and outside-broadcast vehicles, inspect connectors after transport and setup; dust, vibration and patched fibre can create intermittent faults that look like software problems.
AVB discovery depends on timing. Confirm that the grandmaster, boundary clocks and endpoint clock roles are behaving as designed. A network may pass ordinary ping tests while Precision Time Protocol traffic is filtered, delayed or handled incorrectly. Review 802.1AS status at the switch and endpoint, then check whether the devices agree on the active grandmaster and clock domain.
Use a packet capture or specialist diagnostic instrument where possible. Cavendish test equipment can help engineers examine network timing and transport behaviour when switch counters alone are inconclusive. Capture close to the affected endpoint and compare a working port with a failing one, paying attention to timing announcements, link-local discovery and reservation messages.
Isolate discovery and control traffic
AVB discovery is generally local to the Layer 2 domain. Routers, firewalls and many routed VLAN designs do not forward the required discovery frames. A device can respond to an IP address from a laptop while remaining absent from the AVB control view because the relevant multicast or link-local traffic never reaches it.
Temporarily place the Lawo device, third-party endpoint and test computer on one known-good switch or VLAN. Disable unnecessary port isolation, private VLAN features and aggressive multicast filtering during the test. If discovery works in this small network, restore the production topology one element at a time until the blocking feature is identified.
Inspect IGMP snooping and multicast querier settings carefully. These features are useful for managed audio networks, but an incorrect querier arrangement can suppress traffic or leave membership tables stale. Energy-saving Ethernet, storm control and broadcast protection can also interfere with discovery bursts. Keep the audio VLAN separate from office traffic, guest Wi-Fi and general corporate services, particularly in a busy Sydney or Brisbane facility.
Validate subscriptions and stream compatibility
Seeing an endpoint is only the first stage. Confirm that the advertised stream has the expected destination, format, packet timing, sample rate and channel layout. A third-party device may announce a stream using a profile or codec that the Lawo workflow does not accept. Channel labels can also be misleading when a device starts numbering from zero or publishes grouped channels.
Check whether the stream is being reserved successfully. AVB reservation failures often point to unsupported traffic classes, insufficient bandwidth, incompatible switch configuration or a missing SRP function. Look at the sender, every switch in the path and the receiver rather than focusing only on the console or software interface. A single non-compliant hop can prevent an otherwise valid subscription.
For Lawo systems using RAVENNA or AES67, compare the required interoperability profile with the third-party product documentation. A gateway may solve protocol conversion, but it still needs matching clock, multicast, packet-size and channel settings. Software such as Lawo AutoMix can support advanced radio workflows, yet it does not remove the need for a correctly functioning network transport layer; verify the underlying audio stream before diagnosing application behaviour.
Build a repeatable Australian troubleshooting record
Keep a network worksheet for each studio, OB vehicle or performance space. Record switch models, firmware, port assignments, VLAN IDs, clock roles, sample rates and the last known working configuration. This is valuable when a regional site is supported remotely across Australian time zones or when a temporary production system returns from an event in Adelaide, Perth or the Gold Coast.
Use the following sequence to avoid changing several variables at once:
| Check | Healthy result | Likely fault if it fails |
|---|---|---|
| Physical link | Stable negotiated speed with no errors | Cable, optic, port or duplex issue |
| Clock status | Shared grandmaster and locked endpoints | PTP or 802.1AS filtering |
| Discovery | Devices visible in the same local domain | VLAN, multicast or protocol mismatch |
| Reservation | Stream admitted with required bandwidth | SRP, QoS or switch compatibility |
| Subscription | Correct channels and sample rate | Format, profile or routing mismatch |
| Audio | Clean, continuous programme signal | Clock slip, packet loss or endpoint fault |
Save switch logs and packet captures before rebooting equipment. A reboot can clear useful evidence, while a timestamped capture lets engineers compare a failed event with a later working state. In the Australian market, where integrators often support geographically separated stations and mixed legacy estates, consistent records reduce repeated site visits and make vendor escalation far more precise.
The practical takeaway is to prove compatibility first, then verify physical links, timing, local discovery, reservation and stream subscription in that order. A small isolated test network, backed by clear switch and endpoint records, usually reveals whether the fault belongs to AVB itself, the Lawo workflow or an incompatible third-party segment.
