VLAN Configuration & Network Segmentation

If VLANs are in use within your environment, they must be clearly defined, documented, and properly configured prior to vis|ability deployment.

Important Note: vis|ability does not require VLAN segmentation to function. However, in environments where VLANs are implemented, it is critical that all required communication paths between systems are understood and validated ahead of commissioning.

When VLANs are part of the network architecture, they introduce additional considerations for system communication. These must be addressed early to avoid issues during deployment.

At a minimum, the following must be in place:

• VLANs are clearly defined and documented
• All visability-related devices are assigned to the correct VLANs
• Inter-VLAN communication is configured where required
• Firewall rules allow necessary traffic between network segments

All VLAN-related information should be included as part of the network schema.

This should include:

• VLAN ID and name
• Associated subnet
• Devices assigned to each VLAN
• Any relevant routing or segmentation notes

This ensures that both the deployment team and the network administrators have a shared understanding of how systems are segmented and how they are expected to communicate.

vis|ability components must be able to communicate with one another regardless of how they are segmented.

If systems are placed on separate VLANs, routing between those VLANs must be configured and tested.

At a minimum, verify:

• System Manager (ASM) can communicate with all Display Nodes
• Display Nodes can reach all required source systems (streams, encoders, etc.)
• Client devices (Desktop Client) and Sources can access the System Manager server.

If these paths are not available, the system may not function as expected during commissioning.

In segmented environments, required traffic must be explicitly allowed between VLANs.

While specific configurations may vary, ensure that:

• Required TCP/IP communication between systems is not restricted
• Streaming protocols (such as RTSP) are permitted where used
• Web access (HTTP/HTTPS) to the System Manager is available

Failure to allow required traffic between VLANs is one of the most common causes of deployment delays.

Ports and Protocols

If multicast or AV-over-IP streaming is part of the deployment:

• Multicast traffic must be supported across VLANs where required
• IGMP snooping should be enabled on switches
• An IGMP querier should be present

These configurations must be validated prior to commissioning to ensure reliable stream delivery.