PRA-NetworkSetup03-NetworkDesign

NETWORK DESIGN
PRAESENSA Network Setup

Network Design
 Designing an IP network for PRAESENSA can be very easy
 Each PRAESENSA device contains a preconfigured switch
 3rd party switch PRA-ES8P2S is also preconfigured and optimized for PRAESENSA
 Only in case of interfacing to other networks IT knowledge is mandatory

 Refer to the OMNEO network requirements and recommendations guide
This guide explains more in detail which network design aspects to consider.
2 Internal | Building Technologies | BT-CO/MKA1.22 | 2018-06-20

© Robert Bosch GmbH 2018. All rights reserved, also regarding any disposal, exploitation, reproduction, editing, distribution, as well as in the event of applications for industrial property rights.
Network Design
 Network design aspects
 Audio transport and Control is fully OMNEO based
 Audio routing is managed by the System Controller
 Audio master clock (to synchronize audio data) is located in the System Controller
 Internal switches in the PRAESENSA devices have sufficient performance to distribute clocking data
 The system uses a standard Ethernet network 1 Gbps
 100Mbps is allowed for end points but not advised
 Devices are discovered automatically without need for IP address configuration.

Network Design
 Requirements
 The network needs to be “Ethernet only”
‒ i.e. no other networks in between like ADSL, DSL, ISDN or SONET/SDH
 The whole network needs to support Gbit bandwidth or more
‒ 100Mbit is only allowed at the endpoints in the network
‒ Daisy chaining of 100Mb connections is not allowed
‒ Multicast traffic is broadcasted within the subnet and only stopped at a layer 3 router, so not at a switch.

Network Design
 Requirements (>20 multicast channels)
 It is very important that no OMNEO/Dante devices gets
connected behind a port which runs IGMPsnooping. This
will lead to occasional audio mutes because of the
multicast PTP traffic.

Network Design
 Requirements (<20 multicast channels)
 Unfortunately Dante devices which are based upon the
Ultimo chipset (Dante AVIO, Atterotech UNDX2IO, ...)
use 100Mb/s
 If you want to use these 100Mb/s Dante devices you need
to make sure the multicast traffic stays < 20 audio
channels. If you do you can simply connect it like this.

Network Design
 Minimum feature set for switches + routers
 Need to do packet switching in HW
‒ SW switching will introduce to much packet jitter
‒ Take the ‘minimum feature set’ into account as indicated in the next slides
 Make sure QoS is enabled with the right settings
 Make sure jumbo frames are not present on the network
‒ Jumbo frames will increase the packet jitter to and unacceptable level
‒ One jumbo frame can contain up to 9000 bytes which blocks the network too long for other traffic
 Do the math for your bandwidth requirements
‒ Each multicast audio channel will use ~3Mb/s in the whole subnet it is used in
‒ Each unicast audio channel will use ~3Mb/s of the whole network path from the source to the destination.

Network Design
 Minimum feature set
 When the network uses RSTP make sure the topology and settings are right
‒ Hello_Time = 9 seconds
‒ Forwarding_delay = 30 seconds
‒ Max_age = 22 seconds
‒ Not more than 21 devices between the root bridge and any other device
 When unsure involve a network specialist
‒ Make sure you have a detailed network diagram + equipment list available.

Network Design
 For correct configuration needs to be considered
 Which additional type of Audio transport is being used?
‒ Separate OMNEO / Dante / AES67 traffic from other real time audio like CobraNet by using another VLAN
 Device discovery: how to recognize devices and assign an IP address to them
‒ In small networks via mDNS
‒ In large networks (>250 devices) via DHCP server or ARNI (multi-subnet support scheduled for release 1.1)
 Clocking: master clock selection, network performance to distribute clock data
‒ In small networks the preferred clock master is the System Controller
‒ In large networks (>250 devices) an ARNI is installed to act as a preferred master clock
 Domain Name System Service Directory
‒ DNS-SD uses multicast
‒ ARNI can act as DNS-SD gateway (like a phone book).

Network Design
 Power over Ethernet (PoE)
 Powers network devices over a standard Ethernet cable
 Two of the Ethernet ports on the Multifunctional Power Supply (MPS3) do have PoE (IEEE802.3af, 15.4 W)
 Power is supplied for distances up to 100 meters
 PRAESENSA call stations accept PoE standard IEEE802.3af
 Network performance is not affected by PoE.

Network Design
 Power over Ethernet (PoE)
Manufacturer Product Speed Distance Remarks
D-Link DPE-302ge Gb 5*100m
Tycon POE-EXT-GD-HP Gb 3*100m Waterproof

Manual mentions: Gigabit Full rate network throughout
Axis T8129 100Mb 4*100m
Veracity LONGSPAN 100Mb 450-900m Does not need a repeater any 100m

Network Design
 Redundancy (RSTP)
 RSTP (Rapid Spanning Tree) is a common used redundancy protocol for networks
 RSTP allows loops in a network
 Start your design from a star topology perspective

 Define your daisy chain connections carefully
 Define your redundant (loop) connections carefully.

Network Design
 Audio Network Design Aspects
TRANSMITTING Dante
Tx Ch 4 Tx Ch 3 Tx Ch 2 Tx Ch 1 Header
DEVICE Audio Flow
 Every Dante flow can only have 1 transmitting device

 A standard Dante flow can contain multiple channels
 In PRAESENSA the Dante flows only have one channel .
11 Internal | Building Technologies | ST-CO/MKA1.22 | 2018-06-20

Network Design
Transmit
Multicast
RECEIVING
Flows DEVICE
PRAESENSA
RECEIVING
TRANSMITTING Tx Ch 1 Header
DEVICE
DEVICE
RECEIVING
DEVICE
 In PRAESENSA all audio transmitter flows are created in Multicast, distributing one to many
 The audio transmitter flow is created immediately (It doesn’t care about a receiver)
 The system controller will tell receiving devices where to listen (flow & channel).

Network Design
 Enough Bandwidth to carry flows
‒ PRAESENSA uses digital audio 24 bit 48 kHz sampling frequency
‒ Bandwidth of a flow is 2.5 Mbps per single channel flow
‒ sample rate (how many samples per second) {48kHz = 48000 samples/s}
‒ encoding (how many bits per sample) {24 bits}
‒ latency (how many samples per audio channel {32 samples}
‒ number of audio channels {1}
 The 24 bit results in a digital dynamic range of 20*log(2 24)=144dB
 Bandwidth is of 2.5 Mbps per single channel flow
 Audio (play out) latency in PRAESENSA is set to 10 ms.

Network Design
 Identifying required services (mDNS, DHCP, etc.)
 Specifying an optimal infrastructure for predicted bandwidth demands
 Identifying potential “bottlenecks” –designing them out or managing them
 Ensuring a scalable architecture (the network will grow over time)
 Understanding possible future service requirements.

Network Design
 Assure required communication ports are not blocked
Transmitting method Protocol Port

Multicast PTP UDP 319, 320
Multicast mDNS UDP 5353
Multicast Dante UDP 8700-8706,8800
Unicast Dante UDP 4440, 4444, 4455
Multicast Dante UDP 4321
Unicast Dante UDP 14336-14600
Unicast Dante UDP 8751

Network Design
 Quality of Service (QoS)
‒ Prioritizes network traffic based on the ‘type of protocol’ inside each packet
‒ reads Differentiated Services Code Point labels (DSCP) on incoming IP packets
‒ Based on that label decide forwarding behavior (put into a higher or lower priority queue)
‒ Dante packets contain the following DSCP packet priority values:
Priority Usage DSCP Label Hex Decimal Binary

High Time critical PTP CS7 0x38 56 111000
Medium Audio, PTP EF 0x2E 46 101110
Low (reserved) CS1 0x08 8 001000
None Other trafic BestEffort 0x00 0 000000

Network Design

Network Design

Network Design
‒ in a quiet network QoS will not make any difference since it does not happen very often there
need to go to packets to the same switch port
‒ QoS gets important when > 30% network load.


PRA-NetworkSetup03-NetworkDesign

Uploaded by

Document Information

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

PRA-NetworkSetup03-NetworkDesign

Uploaded by

Copyright:

Available Formats

NETWORK DESIGN

PRAESENSA Network Setup

 Only in case of interfacing to other networks IT knowledge is mandatory

2 Internal | Building Technologies | BT-CO/MKA1.22 | 2018-06-20

3 Internal | Building Technologies | BT-CO/MKA1.22 | 2018-06-20

4 Internal | Building Technologies | BT-CO/MKA1.22 | 2018-06-20

4 Internal | Building Technologies | BT-CO/MKA1.22 | 2018-06-20

4 Internal | Building Technologies | BT-CO/MKA1.22 | 2018-06-20

5 Internal | Building Technologies | BT-CO/MKA1.22 | 2018-06-20

6 Internal | Building Technologies | BT-CO/MKA1.22 | 2018-06-20

7 Internal | Building Technologies | BT-CO/MKA1.22 | 2018-06-20

8 Internal | Building Technologies | BT-CO/MKA1.22 | 2018-06-20

Manufacturer Product Speed Distance Remarks

D-Link DPE-302ge Gb 5*100m

Tycon POE-EXT-GD-HP Gb 3*100m Waterproof

Axis T8129 100Mb 4*100m

9 Internal | Building Technologies | BT-CO/MKA1.22 | 2018-06-20

 Start your design from a star topology perspective

10 Internal | Building Technologies | BT-CO/MKA1.22 | 2018-06-20

 Every Dante flow can only have 1 transmitting device

11 Internal | Building Technologies | ST-CO/MKA1.22 | 2018-06-20

12 Internal | Building Technologies | ST-CO/MKA1.22 | 2018-06-20

13 Internal | Building Technologies | ST-CO/MKA1.22 | 2018-06-20

14 Internal | Building Technologies | ST-CO/MKA1.22 | 2018-06-20

Transmitting method Protocol Port

15 Internal | Building Technologies | ST-CO/MKA1.22 | 2018-06-20

Priority Usage DSCP Label Hex Decimal Binary

16 Internal | Building Technologies | ST-CO/MKA1.22 | 2018-06-20

17 Internal | Building Technologies | ST-CO/MKA1.22 | 2018-06-20

18 Internal | Building Technologies | ST-CO/MKA1.22 | 2018-06-20

19 Internal | Building Technologies | ST-CO/MKA1.22 | 2018-06-20

You might also like