
page 4 – 3
WheatNet-IP BLADE 3
/ Jan 2016
E T H E R N E T N E T W O R K S A N D S W I T C H E S
Unmanaged vs. Managed Switches
An unmanaged Ethernet switch is a low cost WYSIWYG device and has no
configuration software interface. Unmanaged switches do not support IGMP snooping
and will therefore act as repeaters to IP audio multicast packets, effectively flooding all
ports with audio packet traffic. Unmanaged switches are inexpensive, acceptable cost
vs. performance compromise.
Managed switches, on the other hand, allow users to configure the switch hardware
with a software interface of some kind, such as Telnet, Web, Terminal, etc. Primary con‑
figuration features applicable to your Ethernet audio network are the ability to configure
VLAN’s, IGMP management, built in diagnostics, and routing. We highly recommend
the deployment of managed switches throughout the network.
Managed switches fall in to several market niches. Low end managed switches,
or “Smart Switches,” offer some configuration, but may not provide the level of con
‑
figurability required in a medium to large Ethernet audio network. For example, these
switches may forward IGMP host messages and multicast traffic but can not act as the
IGMP router. In medium to large applications at least one switch capable of being the
IGMP Querier is required. Mid-priced managed switches are better suited to the task
and will provide more configuration flexibility.
In larger systems it makes sense to employ a “core and edge” model. This type of
system balances the switching horsepower (cost) according to the throughput requirements
at different physical segments of the network. Lighter bandwidth “edge” segments
can use lower cost switches, while central rack room “core” segments utilize higher
performance devices.
Rules of Thumb
The WheatNet‑IP system will work with a minimum number of devices on an
unmanaged switch. If the system is to include more than six BLADE 3s, two Control
Surfaces, and two PC drivers it is recommended that an IGMP compliant, managed
switch be used.
In large systems, careful attention must be paid to the placement of core and edge
switches.
•
Each I/O (88a, 88d, 88ad) BLADE 3 requires 36.9Mb/s for eight Stereo connections.
•
Each I/O (88a, 88d, 88ad) BLADE 3 Requires 73.7Mb/s for 16 Mono connections.
•
Each Engine (e) requires 147.5Mb/s for 32 unique stereo connection streams.
•
Each E-6 surface requires a 100Mb/s Ethernet connection.
• Each Surface requires an Engine (e) connected to the same GbE switch.
•
Each PC driver requires 19.6Mb/s for eight Stereo outputs.
•
An aggregate of eight BLADE 3s (64 streams) requires roughly 295Mb/s of
bandwidth when each BLADE 3 have eight stereo connections.
The Multicast channels used by the WheatNet-IP System are as follows:
• one per audio source
• one for system announce messages
• one for metering data
• one for Logic messages.
WheatNet-IP BLADE 3
/ Feb 2019
Содержание WheatNet-IP BLADE3
Страница 2: ...Technical Manual Wheatstone Corporation Jan 2016 Audio Over IP Network WheatNet IP BLADE3 ...
Страница 16: ...Quick Start 12 WheatNet IP BLADE 3 Jan 2016 Figure 4 ...
Страница 274: ...page A 48 WheatNet IP BLADE 3 Jan 2016 A P P E N D I C E S Contents Appendix 4 External Controllers A 49 ...
Страница 290: ...page A 61 WheatNet IP BLADE 3 Jan 2016 A P P E N D I C E S Click Next Click Install ...
Страница 336: ...page A 107 WheatNet IP BLADE 3 Jan 2016 A P P E N D I C E S Contents Appendix 9 Introduction to Screen Builder A 108 ...
Страница 338: ...page A 109 WheatNet IP BLADE 3 Jan 2016 A P P E N D I C E S ...
Страница 365: ...WheatNet IP BLADE 3 June 2018 page A 136 A P P E N D I C E S Some Screen Shots of Various Vendors Configuration Screens ...
Страница 366: ...WheatNet IP BLADE 3 June 2018 page A 137 A P P E N D I C E S ...