Canonical Names; Network Routing; Network Bandwidth; Network Topology - Studer OnAir 3000 Operating Instructions Manual

OnAir 3000 Digital Mixing Console
9.2.2

Canonical Names

9.2.3

Network Routing

9.2.4

Network Bandwidth

9.2.5

Network Topology

9-4 Networking
All OnAir 3000 components within a OnAir 3000 network domain should be
part of the same IP subnet (same IP range).
With host software V2.1 and higher, the OnAir 3000 components are allowed
to be placed in the IT network with fixed IP addresses in order to allow easy
FTP access for configuration file management.
If canonical names (CNAMES) are required within the OnAir 3000 network
domain, these names must be resolvable via DNS if OnAir 3000 components
must be able to access them. The system integrator or customer must provide
this DNS server and include its IP address in the DHCP scope definition. As
an example, for time synchronization over the network, the OnAir 3000 can
access the NTP server using either its domain name or its IP address.
OnAir 3000 components with IP addresses in different ranges within a routed
network will not be able to communicate with each other by definition.
If a router is used to route different OnAir 3000 network domains, and if OnAir
3000 components from these OnAir 3000 network domains are required to
interact, it is necessary to forward broadcast or multicast packets. Otherwise,
the components from different domains will not see each other (complete
separation).
Because forwarding broadcasts in a router is not common, it is always better
and easier to connect all OnAir 3000 components within one and the same
network domain using switches.
Only if OnAir 3000 network domains must be completely separated by inten-
tion (i.e., no communication between them), it is reasonable to use different IP
subnets and, if necessary, route between them without broadcast forwarding.
Routers can be used as a controlled path between the OnAir 3000 network
domain and the IT network. They give maximum flexibility whenever net-
work requirements should change. Such implementations vary from case to
case and should be cross-checked with Studer Service & Support.
OnAir 3000 components can be interconnected by using any non-blocking,
manageable, or non-manageable 100 Mbit/s network switch.
Manageable network switches (or routers) are mandatory only in cases where
other networks are 'married' with the OnAir 3000 network domain, or where
the DHCP server must be provided as an integral part.
Any network topology is allowed, as far as it does not generate bottlenecks
within the OnAir 3000 network domain – especially within one studio. Some
well known and proven examples are given in
SW V6.0
chapter 9.4.
Document generated: 10.10.14