Luminex Network Intelligence
Entertainment-first switching and network management: sane multicast defaults, recallable profiles, and hardware built for the road.
What it is
Luminex Network Intelligence builds the GigaCore family of managed Ethernet switches together with Araneo, its network management and monitoring software. The design premise is that a show network is not an office network, so a GigaCore arrives with the behavior an entertainment network needs already enabled: multicast handling appropriate to sACN, loop protection, and PoE on the models that carry it. Configuration is organized around Groups rather than raw VLAN tables, and around Profiles, which are saved configurations that can be recalled on the unit itself, so a switch can be repurposed between rigs without a laptop. The line spans rack and stagebox form factors, copper and fiber uplinks, and models with locking connectors and redundant power. Araneo adds discovery, topology, traffic visibility and alerting across a fleet.
How we work with it
We specify GigaCore where the network gets handed to a crew that will not have a network engineer on site every day. Commissioning starts from the traffic rather than the hardware: universe counts, sender and receiver behavior, where multicast has to be contained, what runs on fiber, what needs PoE, and what happens when a link or a supply is lost. Groups get drawn to match the real data domains, not a departmental org chart. Profiles are built and labeled for every configuration the rig will legitimately need, then handled so a recall is a decision rather than an accident. We write the port map and the recall procedure in plain language for the people who will actually run it, prove failover by pulling links instead of trusting a drawing, and leave Araneo pointed at the fleet so configuration drift stays visible.
Defaults are set for entertainment multicast, so the out-of-box state is closer to correct than a generic switch.
Groups and Profiles let a crew repurpose a switch from the unit itself without editing VLAN tables.
Rack and stagebox form factors, with locking connectors and redundant power on part of the range.
Araneo gives fleet-wide topology and traffic visibility, which shortens fault-finding under show pressure.
Right when
- Show crew will operate the network day to day, and it has to be recoverable without a network engineer on call.
- The rig reconfigures between looks, rooms or cities and needs repeatable saved states instead of ad hoc edits.
- Physical conditions are part of the spec: touring, repeated load-ins, connector retention and power redundancy actually matter.
Look elsewhere when
- You need enterprise Layer 3 and enterprise security posture: dynamic routing, granular ACLs, 802.1X, integration into a corporate NAC or an existing monitoring stack. GigaCore is deliberately narrow, and a mainstream enterprise switch will do that work better, cheaper, and with an in-house team that already knows it. Buying GigaCore here means paying a premium for ergonomics you then configure around.
- It is a fixed install with in-house IT who will own it, and budget is the binding constraint. The premium on this line buys front-panel recall and touring hardware for a crew that does not exist on that site. Put the money into port count, fiber and spares instead, and spend the difference on someone competent to configure and document it.
Does using GigaCore mean we can stop thinking about multicast?
No. It means the common failure modes are less likely on day one, not that the design is done. Universe counts, where multicast is contained, which device acts as querier when other switches are present, and what a receiver does when it loses a source are still design decisions. The defaults buy you margin for error; they do not replace a traffic plan you can explain and test.
Can we mix GigaCore with switches from other vendors?
Yes, and most real networks do, because house infrastructure rarely matches the touring package. The care is at the boundary. Multicast behavior, spanning tree roles and VLAN tagging all have to be agreed across the seam rather than assumed, and whichever device wins querier election has to be the one you chose. Test the joined network, not each half in isolation.