Network Configuration
Firewalls and Network Security Software
Omnia Enterprise 9s has been tested and verified to run without issues when using a properly configured instance of Windows Defender Firewall. However, some third-party antivirus and network security software can cause delays in audio packets, which can, in turn, result in audible artifacts ranging from clicks and pops to momentary dropouts to a complete absence of audio on AoIP streams. The same is true for any enterprise software that probes the ports of network switches and the devices attached to them. We strongly encourage working in partnership with your Network Administrator to develop the best practices for your plant to balance the unique requirements of real-time AoIP traffic and network security.
Control Network
Once the network interface for the control network has been set up with the appropriate IP address, subnet, and gateway, no further action is needed in order to connect to Omnia Enterprise 9s via NfRemote. See the section on Installing NfRemote for details on both installation and configuration.
AoIP Network
Once the network interface for the AoIP network has been set up with the appropriate IP address, subnet, and gateway, the configuration can be done either by running the Omnia Enterprise 9s app (located in the shortcuts folder) or by connecting via NfRemote.
Livewire IP Addresses
Navigate to Common > System > Livewire. For a single AoIP network, enter the IP address of the AoIP network interface in the Livewire IP field (A). Use the Livewire IP2 field (B) to enter a second address for dual-network applications; please see the section on SMPTE 2022-7 Redundancy below.
SMPTE 2022-7 Redundancy
Omnia Enterprise 9s supports stream redundancy per SMPTE 2022-7 (Seamless Protection Switching). Two IP addresses (one for each AoIP network interface) must be entered as described above. Omnia Enterprise 9s accepts PTP master clock over both AoIP networks and will synchronize to the better clock, and switch to the other network in case of PTP clock or network failure.
Note: Setup and configuration require connecting locally via the Omnia Enterprise 9s App in the "Shortcuts" folder.
Each Station must be individually configured. Using Station 1 as an example, navigate to the Station 1 > Overview > Livewire menu, choose the desired output (FM, FM Pre-Final, or HD), then enter the multicast addresses of the desired output streams in a comma-separated format with no additional spaces in the Channel field
Address Display Type
Audio sources and destinations can be displayed in one of two ways in the Audio Display Type dropdown (F):
AES67 - Displays I/O entries as multicast addresses
Livewire - Displays I/O entries as Livewire channel numbers
Clock Mode
The Clock Mode dropdown (D) offers two supported clock modes:
PTP Clock - Used for AES67/SMPTE 2110 installations
PTP Clock Domain (E)
The AES67 standard recommends a PTP clock domain of 0
The SMPTE 2110-30 standard recommends a clock domain of 127
Be sure to check with your network administrator as your network may use a different domain
Livewire Clock - Used for Axia installations
The Sync Status (C) will be displayed once the clock is set up properly, including sync lock, announce interval, clock priorities, clock class, clock master IP address, and the MAC address of the grandmaster clock.
HTTP Access
In order for any network device - including automation control, Ember+ control, and SNMP management - to access the Omnia Enterprise 9s server, the remote device's IP address must be entered into the Enterprise 9s HTTP whitelist. Navigate to the Common menu, then to the HTTP Access (A) menu, and then enter the address(es) into the IP field (B) in the format shown in Figure 2 below or the UI.
The HTTP server uses port 7380. The information and resources available from the HTTP server include all of the items shown in Figure 2 below.
Important: It is always advisable to add the IP address of the technical manager's PC to this list. If the Omnia Enterprise 9s password is lost, the only way to recover it is through a PC that has access to the built-in HTTP server. Otherwise, the entire Omnia Enterprise 9s system must be deleted and rebuilt.
Ember+ Control
As a data provider, Omnia 9s Enterprise supports control commands through Ember+ and listens on port 9000 of any network interface. A whitelist of addresses is used to limit the servers that connect.
SNMP
Omnia Enterprise 9s supports SNMP versions V1 and V2c. The MIB file is available by downloading it from the HTTP server (see "HTTP Access" above).
Last updated
