OnAir 3000 Digital Mixing Console
Networking 9-3
Document generated: 10.10.14
SW V6.0
9 NETWORKING
Important! Manageable switches, such as Netgear FSV318 or AT8624, MUST
NEVER BE SWITCHED OFF!
9.1 Introduction
Purpose: This chapter should help designing an appropriate IT network in order to
successfully establish a networked OnAir 3000 system. It is intended for use
by system integrators, customers, service & support.
Definitions and Acronyms:
OnAir 3000 Component Compact SCore, OnAir 3000 main screen, OnAir 3000 channel screen,
DigiMedia (audio editor), event logger, status monitor, central configuration
com puter
OnAir 3000 Network Domain All OnAir 3000 components within the network that are required to ‘see’ each
other
Canonical Name Constant and explicit identification (CNAME)
DNET A proprietary suite of network protocols, based upon X.25
DHCP Dynamic host configuration protocol (dynamical IP address assignment)
DNS Domain name system (resolves canonical names to IP addresses, and vice
versa)
IP Internet protocol
IT Network The customer’s non-OnAir 3000 network infrastructure
LAN Local area network
MAN Metropolitan area network
Malware Malicious software (viruses, worms, trojans, etc.)
TCP/IP Transfer protocol/internet protocol
UDP User datagram protocol
VLAN Virtual LAN
WA N Wide area network
9.2 Network Characteristics and Requirements
In order to choose the appropriate network topology and design, it is important
to understand the fundamentals of the OnAir 3000 system communication
scheme.
9.2.1 Network Layer & Setup
The OnAir 3000 system supports and uses only IP protocols on the network
layer. IP addresses are assigned using DHCP. This can be realized with a
regular IT server (software), or with manageable switches or routers that
implement this feature.
By definition, only one single DHCP server within one network domain can be
active. Redundant DHCP servers may be realized, but this is left to the system
integrator’s or customer’s responsibility. If more than one DHCP server is
used, it must be guaranteed that the OnAir 3000 components always get a
valid IP address being in the range of other OnAir 3000 components within
the OnAir 3000 network domain.
To Next Page
Loading...
Need help?
General
