SageVue network architecture
This article provides insight into the network communication architecture and behavior of SageVue on an enterprise network. When deployed within a network, SageVue must have access to communicate directly with the Biamp devices it is managing.
Network Architecture Overview
The diagram below provides a simple overview of the SageVue network communication architecture. Consider the following key points regarding this architecture:
- SageVue operates entirely within an enterprise network.
- Internet access is optional. When there is no internet access, Cloud Support and the ability to download firmware libraries will be disabled.
- Users may access the web UI by browsing to the SageVue host machine's network location.
- Automatic Device Discovery runs within the local subnet only.
- SageVue uses direct UDP/TCP mechanisms to communicate with devices.
- Discovery mechanisms can be disabled. Device IP Addresses and Hostnames can be manually configured.
Protocols
SageVue communicates with Tesira and Devio devices using the same protocols as Tesira Software and the Devio SAU. Communication with QtPro devices is over standard HTTPS while Dynasound Devices use SNMP. See the tables below for specifics of the protocols, ports, and multicast addresses used for automatic device discovery.
Discovery and Control Protocol Ports:
SageVue uses the following ports and protocols for device discovery and control:
| Port | Protocol | Usage |
|---|---|---|
| 22 - TCP | Devio Text Protocol (SSH-based) | Communication with Devio devices |
| 80 - TCP | HTTP | Optional, unsecured HTTP for web UI and API (HTTPS is used by default) |
| 161 - UDP | SNMP | Communication with Dynasound devices |
| 443 - TCP | HTTPS |
Web UI, RESTful API, CrowdMics, and optional connection to Biamp.com portal Communicaton with QtPro devices |
| 5353 - UDP | mDNS | Tesira hostname resolution, Devio discovery, CrowdMics ATOM discovery |
| 12003 - UDP | Biamp Discovery | Biamp's proprietary automatic multicast discovery for Tesira |
| 61451 - TCP/UDP | Biamp Communication | Biamp's proprietary unicast control for Tesira |
Hostname resolution via mDNS may be disabled on SageVue and within Tesira devices. Tesira and Devio auto-discovery mechanisms may also be independently disabled. Communication via HTTPS to Biamp.com for Cloud Support and automatic firmware library downloading is optional.
Discovery Multicast Addresses
SageVue uses the following addresses for automatic device discovery and hostname resolution:
| Multicast Address | Usage |
|---|---|
| 224.0.0.251 | Multicast DNS hostname resolution, Devio device discovery and CrowdMics ATOM device discovery |
| 224.0.0.252 | Biamp Tesira device discovery |
Automatic discovery and mDNS may be disabled in the SageVue network settings. 224.0.0.x multicast addresses are defined as local-scope and generally blocked across network routes. Some routers and switches do not register local-scope addresses to IGMP Snooping and will block forwarding. The direct IP address or hostname of devices must be specified under these conditions.
QtPro and Dynasound devices don't support automatic discovery. The direct IP addresses of these devices must be specified in SageVue. Discovery is only attempted on specified IP addresses