Configuring IP Address for a vis|ability Deployment
Why IP Addressing Matters
vis|ability is a fully network-driven platform. System Manager, Display Nodes, Capture Clients, encoders, and baseband devices all communicate over IP. A consistent, well-planned addressing scheme ensures stable content routing, predictable troubleshooting, and long-term scalability.
Static vs. DHCP
-
Static Required: System Manager, Display Nodes, Application Server(s), Encoders, IPX cards, Capture Clients (recommended).
-
DHCP Acceptable: Operator desktops, Web Client users, general IT workstations.
-
Changing IPs breaks source mapping, Display Node connectivity, and Link automations — avoid DHCP for anything publishing content or participating in system control.
| Component | IP Requirement | Purpose |
|---|---|---|
| System Manager | Static | Central controller, API, authentication |
| Display Nodes | Static | Routes content to video walls |
| Application/Nexus Server | Static | Web Client, Web Portal, SSO |
| Capture Clients (PCs) | Static preferred | Stable source publishing |
| Encoders (Maevex, SDVoE, NDI, etc.) | Static | Video streaming endpoints |
| IPX / Baseband Cards | Static (each card) | Network-connected capture device |
| Operator Workstations | DHCP or Static | Client use only |
Hardware Encoders and Baseband (IPX) Devices
Hardware Encoders
Includes Maevex 6100/7000, BirdDog NDI, Magewell, AMX, SDVoE, etc.
-
Each device has a management IP and a streaming endpoint.
-
Static IPs prevent source loss and ease troubleshooting.
-
Display Nodes must have route access to each encoder.
Matrox IPX / Baseband Cards
IPX cards function as standalone network devices inside a PC.
-
Each IPX requires its own unique static IP.
-
Devices appear individually in visability.
-
Critical for multi-channel capture PCs.