Firewall; Vlans; Malware - Studer OnAir 3000 Operating Instructions Manual

OnAir 3000 Digital Mixing Console
9.2.10

Firewall

9.2.11

VLANs

9.2.12

Malware

9-6 Networking
However, as soon as any unpredictable network traffic is generated from non-
OnAir 3000 components, proper operation and full performance of the OnAir
3000 system cannot be guaranteed. Therefore, mixed mode should only be
chosen if reduced reliability can be tolerated – which, of course, should only
be the case for non-on-air installations, such as production sites.
A firewall between the IT network and the OnAir 3000 network domain is
not necessary but can be implemented if desired. Keep in mind that a firewall
will limit certain functionalities that can not be worked around (e.g. software
update to OnAir 3000 components from the IT network, or even file sharing
between the networks).
VLAN tagging is not supported by the OnAir 3000 components. This means
that only so called port-based (non-tagged) VLANs are possible. Untagged
VLANs, by definition, are completely separated from each other. A network
switch port can thus only belong to a single, untagged VLAN. A set of 'n'
ports belonging to such a VLAN can be compared with a physical Ethernet
switch with 'n' network ports.
The OnAir 3000 network domain must be free of any malware. Even if mal-
ware does not affect the OnAir 3000 components, undesired network traffic
could be generated and reduce the performance as a consequence.
SW V6.0 Document generated: 10.10.14