AV-over-IP Network Design for Yachts

A technical guide to yacht AV-over-IP networks covering multicast, IGMP, QoS, VLANs, PTP, link speeds, switch selection, and acceptance testing.

AV-over-IP puts guest media traffic onto managed network infrastructure. That creates flexibility, but it also turns switch configuration, multicast control, QoS, uplink capacity, clocking, and documentation into guest-service dependencies. Treating AV-over-IP as ordinary office data is one of the fastest ways to create intermittent yacht faults.

The yacht-specific risk is split ownership. The AV integrator may specify the endpoints, the IT provider may manage switches, the ETO/AVIT engineer may own day-to-day fault response, and management may approve budgets. The design record must make those boundaries explicit before several rooms depend on the same media network.

• Endpoint inventory with model, firmware, room, rack, stream type, IP address, switch, port, VLAN, and power source.
• Traffic model showing likely simultaneous sources, receivers, event feeds, exterior zones, and worst-case route counts.
• Switch topology with access ports, uplinks, stacking, link speeds, redundancy, and any bottleneck ports.
• Multicast design: IGMP snooping, IGMP querier location, multicast groups, discovery traffic, and subnet boundaries.
• QoS/DSCP policy for Dante, AES67, Q-LAN, control traffic, video streams, and management traffic.
• Clocking design for networked audio or media systems that rely on PTP or vendor timing.
• Backup plan for switch configs, AV endpoint configs, and known-good firmware versions.

1. Prove topology: Walk the rack and compare labels, switch ports, VLANs, endpoint names, IP addresses, and uplink speeds against the design record.
2. Prove multicast control: Subscribe and unsubscribe receivers while checking switch multicast tables and traffic counters. Flooding should not appear on unrelated ports.
3. Run capacity tests: Operate the maximum expected number of rooms and sources, including event and exterior scenarios. Record bandwidth, packet errors, dropped frames, audio glitches, and endpoint warnings.
4. Test recovery: Reboot selected endpoints and a non-core switch during a controlled window. Record recovery time and whether the user interface returns cleanly.
5. Freeze the baseline: Export switch configs, endpoint configs, screenshots, firmware versions, multicast tables, and test notes as the known-good baseline.

• Switch support: Is the selected switch platform explicitly supported by the AV vendor and acceptable to the IT provider?
• Scale: Can multicast groups, endpoints, uplinks, and forwarding tables handle future rooms and event feeds?
• Operations: Can onboard crew view port errors, multicast groups, endpoint status, and config backups without waiting for a vendor?
• Segmentation: Are guest Wi-Fi, CCTV, owner devices, AV media, and management traffic intentionally separated?
• Warranty: Will vendors support the design if third-party switches, mixed firmware, or shared infrastructure are used?

If AV-over-IP shares switching with IT, CCTV, Wi-Fi, or vessel management systems, document the limits and change-control process. A normal network cleanup can break AV service if multicast, QoS, or discovery rules are changed without awareness.