Atlona OmniStream AT-OMNI-111 Deployment Manual

Atlona OmniStream AT-OMNI-111 Deployment Manual

Hide thumbs Also See for OmniStream AT-OMNI-111:

Advertisement

AT-OMNI-111
AT-OMNI-121
AT-OMNI-112
AT-OMNI-122
IT Deployment Guide
AT-OMNI-512
AT-OMNI-232
AT-OMNI-521
Atlona Manuals
OmniStream

Advertisement

Table of Contents
loading
Need help?

Need help?

Do you have a question about the OmniStream AT-OMNI-111 and is the answer not in the manual?

Questions and answers

Summary of Contents for Atlona OmniStream AT-OMNI-111

  • Page 1 IT Deployment Guide AT-OMNI-111 AT-OMNI-121 AT-OMNI-512 Atlona Manuals AT-OMNI-232 AT-OMNI-112 AT-OMNI-122 AT-OMNI-521 OmniStream...
  • Page 2: Version Information

    Version Information Version Release Date Notes 08/17 Initial release 11/17 Added language to cover both OmniStream Pro and R-Type AT-OMNI-XXX...
  • Page 3: Table Of Contents

    Table of Contents Network Topologies Single Logical Switch Advantages Disadvantages Star Advantages Disadvantages Fat Tree Advantages Disadvantages Layer Terminology Per Stream Bandwidth Utilization Scrambling Redundancy (OmniStream Pro Only) Video FEC (OmniStream Pro Only) Audio FEC (OmniStream Pro Only) Data Trunk Bandwidth Utilization Unicast vs Multicast Routing Trunk Port Definition Trunk Uplink...
  • Page 4: Network Topologies

    • Simple. • Easy to manage. • Limited network impact of video traffic. • Inexpensive. • Atlona provided configuration files available for some Cisco SG300 SKUs. Disadvantages • Limited scalability options. • No network redundancy; single point of failure. AT-OMNI-XXX...
  • Page 5: Star

    Network Topologies Star For systems needing more scalability than that offered by a single logical switch, multiple logical switches can be each connected to a single switch for intercommunication. In this topology, the central switch is referred to as a “core”...
  • Page 6: Fat Tree

    Network Topologies Fat Tree Very large network systems often fall into the category of a fat tree topology. Here, access switches are connected to a distribution switch in a manner like a star network. Multiple distribution switches are in turn connected to a core switch.
  • Page 7: Layer Terminology

    Network Topologies Layer Terminology Users often refer to switches as a “layer 2 switch” or a “layer 3 switch”, often insisting that a “layer 3 switch” is necessary for a multicast network to function properly. This statement isn’t always true, but to understand why, the terms “layer 2 switch”...
  • Page 8: Per Stream Bandwidth Utilization

    Per Stream Bandwidth Utilization To effectively plan a network, it is necessary to understand how bandwidth on that network will be utilized. By first understanding how much bandwidth each stream on each switch will utilize, it becomes easy to see how bandwidth across the system will be utilized.
  • Page 9: Video

    For OmniStream R-Type, the total bandwidth utilization for a video stream is 900 Mbps. FEC (OmniStream Pro Only) Forward Error Correction (FEC) has a bandwidth penalty associated with its use. Atlona’s implementation of FEC is per SMPTE 2022-5:2013 and does not require any extra network consideration beyond the bandwidth penalty described here.
  • Page 10: Fec (Omnistream Pro Only)

    OmniStream 232 Dante audio bandwidth utilization can be assumed to be 1.5 Mbps per channel. FEC (OmniStream Pro Only) Atlona’s implementation of FEC is per SMPTE 2022-5:2013 and does not require any extra network consideration beyond the bandwidth penalty described here.
  • Page 11: Trunk Bandwidth Utilization

    Trunk Bandwidth Utilization In star or fat tree topologies, multiple switches are interconnected with trunk links. Trunk links are interconnections between switches which enable higher bandwidth connections between switches. To understand how link bandwidth will be used, you must first understand how the traffic will flow. It is recommended that trunk link bandwidth utilization not exceed 80% of trunk link capacity.
  • Page 12 Trunk Bandwidth Utilization Figure 2 - Unicast mode: encoder and decoder using different switches. “Core” Switch “Access” Switch “Access” Switch AT-OMNI-122 (Decoder) Legend AT -O Data flow AT-OMNI-112 (Encoder) Unused connection For multicast streams, the network will do two things: •...
  • Page 13: Trunk Port Definition

    Trunk Bandwidth Utilization Figure 4 - Multicast mode: encoder and decoder using different switches. Legend Data flow Unused connection “Core” Switch IGMP querier “Access” Switch “Access” Switch DI SP M NI AT -O AT-OMNI-112 (Encoder) AT-OMNI-122 (Decoder) Trunk Port Definition Trunk ports on a switch are simply those ports used to connect to other switches.
  • Page 14 Trunk Bandwidth Utilization Figure 5 - Diagram showing uplink calculation (multicast mode). “Access” Switch “Core” Switch AT-OMNI-112 AT -O IGMP querier (Encoder) “Access” Switch “Access” Switch AT -O AT-OMNI-112 AT -O AT-OMNI-112 (Encoder) (Encoder) AT -O AT-OMNI-112 (Encoder) AT -O AT-OMNI-112 (Encoder) AT-OMNI-XXX...
  • Page 15: Trunk Downlink

    Trunk Bandwidth Utilization Trunk Downlink The trunk downlink bandwidth utilization is the sum of all traffic flowing to the switch in question to the other switch connected to the link. When computing trunk downlink bandwidth utilization, it is best practice to assume worst-case by accounting for the maximum amount of multicast traffic possible, coming from another switch.
  • Page 16: Igmp / Multicast Routing Requirements

    IGMP / Multicast Routing Requirements For networks using unicast only (point to single point), there is no special configuration needed for IGMP/multicast routing. For networks using multicast or a combination of unicast and multicast, IGMP/multicast routing must be properly configured to avoid traffic flooding ports and causing unnecessary outages. Note that based on unit configuration, multiple unicasts/multicasts can be generated from single HDMI sources.
  • Page 17: Handling Of Unregistered Multicasts

    • 224.0.0.232 Multicast DNS (mDNS) The Atlona Management System (AMS) uses mDNS for automatic device discovery. By default, mDNS discovery does not function beyond VLAN/subnet boundaries. Switchport Configuration On switches that support it, any ports connected to OmniStream devices should have the below options configured to enable the port to establish a link quickly upon device connection.
  • Page 18: Poe

    OmniStream device. Other switches (e.g., Cisco SG300) do not try to intelligently allocate power and thus do not require this. The Atlona Management System (AMS) is used for centralized management of OmniStream devices. All UDP ports between AMS and OmniStream must be open and available, as AMS uses WebSockets to communicate with OmniStream.
  • Page 19 • 408.962.0515 • 877.536.3976 © 2017 Atlona Inc. All rights reserved. “Atlona” and the Atlona logo are registered trademarks of Atlona Inc. All other brand names and trademarks or registered trademarks are the property of their respective owners. Pricing, specifications and availability...

Table of Contents