top of page

Rack & networking field guide for Fusion installs

  • Start on the home page, then dig into drivers and downloads
    Use the Fusion Research home page for the latest movie server, music server, and PA-1 summaries. When you are ready for firmware bundles, control drivers, or dealer-only files, move through the same top navigation you already use on jobsites so nothing gets lost between the rack and the truck stock.
  • Keep discovery clean on the VLAN that carries Fusion traffic
    Put Ovation tools, multicast discovery, and streaming control on a switch that has IGMP snooping and a known querier. If the customer VLAN is busy with cameras or guest Wi-Fi, carve a small integrator-only VLAN for servers, control processors, and PoE switches. Document the subnet, gateway, and helper addresses in your closeout packet so the next tech does not guess which port feeds the rack.
  • Budget PoE headroom before you hang a PA-1 off a crowded edge switch
    Fusion zone hardware that relies on PoE should sit on a switch port with real watts to spare, not on a shared injector daisy chain. Measure cable length, pair count, and switch class so you are not one camera reboot away from a brownout. If you add optional wireless adapters or USB accessories, rerun the math on the same bill of materials so the rack photo matches what commissioning sees.
  • Treat movie servers like thermal loads, not thin clients
    High-bitrate storage and playback need steady intake and exhaust even when the rack looks fine on day one. Leave blank rack units, route low voltage away from hot PCIe zones, and log max temps during soak testing. Pair that with clean power sequencing so spin-up current does not trip a branch breaker while the projector is calibrating.
  • Map physical cable paths before you dress fiber or copper to the rack ears
    Decide early whether HDMI runs stay short with local switching or jump through HDBaseT or fiber extenders. For Ethernet, keep homerun pulls under the derated length for 1 Gbps links and label both ends with the room name and patch panel coordinate. That habit saves hours when you validate 4K HDR paths against the control system macros.
  • Hand the client a one-page network facts sheet tied to Fusion gear
    List reserved DHCP leases or static IPs, forwarded TCP ports such as 9720 for remote Ovation access, and the hostname each driver expects inside Control4, Crestron, or Q-SYS. Add the support URLs you actually use in the field, including music server support, movie server support, and contact and downloads so owners stop searching random forums.
  • When you need a second opinion on a stubborn install
    If discovery still fails after VLAN work, cable swaps, and factory resets, collect switch logs, traceroutes, and a short phone video of front-panel behavior. That package lets Fusion support reproduce the fault quickly and keeps your RMR relationship with the homeowner intact.
bottom of page