This session will address how to design an IP network for 2110 transport, with emphasis on how to avoid congestion and hashing collisions, and on how these problems are solved with network protocols and enhancements, or SDN controller orchestrating the network. The world of IP networks can be complicated, full of protocols and choices to make, but what are the right choices and how to be sure everything will work. This session will explain the common issues and challenges for multicast transport in IP networks, and how to ensure that important media flows will reach the destination unaffected. Hashing of IP traffic over available links is another issue, that could affect media flows in the network. This session will propose ideas on how to design multicast networks and what are options in actively managing flows in networks or doing it outside the network using an SDN controller, and how users can benefit from both approaches. Come and see how your ST 2110 signals can be transported in a fast, reliable, and deterministic way.
File Type:
pptx
Categories:
Network Infrastructure
Presenters :
Nemanja Kamenica - Cisco
Year :
2022
dlp_document_download :
Expand your production remotely, or to a public cloud Nemanja Kamenica Technical Marketing Engineer, Cisco Agenda Deployment Scenarios Remote Production Contribution Distribution Hand-off to Public Cloud Importing and Decoding Spine and Leaf deployment Pros: Distributed, scalable Deployment options Monolithic deployment Pros: Simple, centralized Production – Live Studio Production Studio 1 Studio 2 Studio 3 Production Control Room 1 Master Control Production Control Room 2 Production – Live and Postproduction Studio 1 Studio 2 Production Control Room 1 Master Control Production Control Room 2 Playout NAS Encoder Remote production – Remote Leaf For small site with limited amount of end-points Studio 1 – Main Site Studio 2 – Remote Site Cisco Non-Blocking Multicast Fabric Remote production – Remote Leaf For small site with limited amount of end-points Studio 1 – Main Site Studio 2 – Remote Site Cisco Non-Blocking Multicast Fabric Bandwidth Management on all links in network Remote production – Multi-Site Interconnecting two sites to exchange signals Studio 1 – Amsterdam Studio 2 – Brussels Cisco Non-Blocking Multicast Fabric Cisco Non-Blocking Multicast Fabric Remote production – Multi-Site Interconnecting two sites to exchange signals Studio 1 – Amsterdam Studio 2 – Brussels Redundant Dark-Fiber Connection Cisco Non-Blocking Multicast Fabric Cisco Non-Blocking Multicast Fabric Remote production – Multi-Site Interconnecting two sites to exchange signals Studio 1 – Amsterdam Studio 2 – Brussels Redundant Dark-Fiber Connection Cisco Non-Blocking Multicast Fabric Cisco Non-Blocking Multicast Fabric Bandwidth Management on all links in network Bandwidth Management on all links in network Remote production – Multi-Site and PTP Interconnecting two sites to exchange signals Studio 1 – Amsterdam Studio 2 – Brussels Cisco Non-Blocking Multicast Fabric Cisco Non-Blocking Multicast Fabric PTP is required to be traceable between sites PTP is required to be traceable between sites GM GM Remote production – Multi-Site Studio 1 – Amsterdam Cisco Non-Blocking Multicast Fabric Studio 2 – Brussels Cisco Non-Blocking Multicast Fabric Studio 4 – Paris PIM Network Studio 3 – London PIM Network WAN Router Redundant Dark-Fiber Connection WAN network, requires unicast and multicast reachability between sites Remote production – Contribution If stadium and studio have same multicast group used, how to ingest it? Studio 1 – Amsterdam Cisco Non-Blocking Multicast Fabric Johan Cruyff Arena S 4 ,G 1 S 5 ,G 2 S 6 ,G 3 S 1 ,G 1 S 2 ,G 2 S 3 ,G 3 Remote production – Contribution Studio 1 – Amsterdam Cisco Non-Blocking Multicast Fabric Johan Cruyff Arena S 4 ,G 1 S 5 ,G 2 S 6 ,G 3 S 1 ,G 1 S 2 ,G 2 S 3 ,G 3 Use Multicast Network Address Translation (NAT) to change G 1 to G 4 , G 2 to G 5 and G 3 to G 6 NAT enables a device, to translate Source/Designation IP, Layer 4 port of an IP packet to new address Multicast NAT > Translate multicast destination IP Network Address Translation - Multicast Multicast NAT SRC: 192.168.1.10 DST: 239.1.100.10 SRC: 10.1.1.10 DST: 237.1.10.10 IN OUT Remote production – Contribution Studio 1 – Amsterdam Cisco Non-Blocking Multicast Fabric Johan Cruyff Arena S 4 ,G 1 S 5 ,G 2 S 6 ,G 3 S 1 ,G 1 S 2 ,G 2 S 3 ,G 3 Use Multicast Network Address Translation (NAT) to change G 1 to G 4 , G 2 to G 5 and G 3 to G 6 S 4 ,G 4 S 4 ,G 1 S 5 ,G 5 S 5 ,G 2 S 6 ,G 6 S 6 ,G 3 Remote production – Distribution Studio 1 – Amsterdam Cisco Non-Blocking Multicast Fabric S 1 ,G 1 S 2 ,G 2 S 3 ,G 3 Demarcation device to distribute content to third parties Remote production – Distribution Studio 1 – Amsterdam Cisco Non-Blocking Multicast Fabric S 1 ,G 1 S 2 ,G 2 S 3 ,G 3 Demarcation device uses NAT to change G 1 to G 10 , G 2 to G 20 and G 3 to G 30 S 3 ,G 3 S 3 ,G 30 S 2 ,G 2 S 2 ,G 20 S 1 ,G 1 S 1 ,G 10 Hand off to public cloud Studio 1 – Amsterdam Cisco Non-Blocking Multicast Fabric S 1 ,G 1 Transport to Public Cloud might require unicast transport if connected over the Internet, or directly connected Public Cloud 1 Public Cloud 2 Public Cloud 3 NAT enables a device, to translate Source/Designation IP, Layer 4 port of an IP packet to new address Multicast to Unicast NAT > Translate multicast destination IP in to Unicast destination IP NAT – Multicast to Unicast Multicast to Unicast NAT SRC: 192.168.1.10 DST: 239.1.100.10 SRC: 10.1.1.10 DST: 192.168.100.10 IN OUT Hand off to public cloud Studio 1 – Amsterdam Cisco Non-Blocking Multicast Fabric S 1 ,G 1 Multicast to Unicast NAT is performed to translate (S 1 ,G 1 ) in US 1 , UD 1 / UD 2 / UD 3 to allow for routing S 1 ,G 1 US 1 ,UD 1 S 1 ,G 1 US 1 ,UD 2 S 1 ,G 1 US 1 ,UD 3 Public Cloud 1 Public Cloud 2 Public Cloud 3 Decoding Video Internet Studio 1 – Amsterdam Cisco Non-Blocking Multicast Fabric Decoder Decoder US 1 ,UD 1 :UDP Decoding Video Internet Studio 1 – Amsterdam Cisco Non-Blocking Multicast Fabric To distribute traffic to all devices requiring it, unicast traffic can be translated to multicast for efficiency Decoder Decoder US 1 ,UD 1 :UDP NAT enables a device, to translate Source/Designation IP, Layer 4 port of an IP packet to new address Unicast to Multicast NAT > Translate Unicast destination IP into Multicast cast destination IP NAT –Unicast to Multicast Unicast to Multicast NAT SRC: 192.168.1.10 DST: 192.168.100.10 SRC: 192.168.1.10 DST: 239.1.100.10 IN OUT Decoding Video Internet Studio 1 – Amsterdam Cisco Non-Blocking Multicast Fabric S 1 ,G 1 US 1 ,UD 1 Decoder Decoder US 1 ,UD 1 :UDP Unicast to Multicast NAT is performed to translate (US 1 ,UD 1 ) in S 1 , G 1 to allow for efficient distribution IP architecture allows flexibility, so multiple studios can be satisfied with one IP network Interconnecting multiple geographically distant locations is possible with multi-site deployment, over dark fiber or WAN network Importing signals to IP network, or exporting them to 3 rd party is possible with Multicast NAT Exporting signals for post-production in public cloud is possible with Unicast to Multicast NAT Importing unicast signals to IP fabric is allowed with Unicast to Multicast NAT All these deployments can be done with Cisco Nexus 9000 devices, supported with IPFM deployments Conclusion Any Questions?
Downloads:
27