BRKSPV-1222-Cisco IP Fabric Arquitectures For Video Production and Broadcast Workflows PDF

BRKSPV-1222
IP Fabric Architectures for

Video Production and
Broadcast workflows
Rahul Parameswaran – Technical Marketing Engineer

Cisco Spark
Questions?
Use Cisco Spark to communicate
with the speaker after the session
How
1. Find this session in the Cisco Live Mobile App
2. Click “Join the Discussion”
3. Install Spark or go directly to the space
4. Enter messages/questions in the space
cs.co/ciscolivebot#BRKSPV-1222
© 2018 Cisco and/or its affiliates. All rights reserved. Cisco Public
Agenda
• The Move to IP
• Cisco’s IP Fabric for Media
• DCNM Media Controller
• Determining the Topology
• Architectures and Customer Deployments
• Conclusion
The Move to IP
The Move to IP
Today, the broadcast industry uses an SDI router and SDI cables to transport
video and audio signals. The SDI cables can carry only a single unidirectional
signal. As a result, a large number of cables, frequently stretched over long
distances, are required, making it difficult and time-consuming to expand or
change an SDI-based infrastructure. Also, with rapid adoption of 4k,VR, SDI
routers are unable to keep up with the industry requirements.
Cisco IP Fabric for Media helps you migrate from an SDI router to an IP-based
infrastructure . In an IP-based infrastructure, a single cable has the
capacity(100G) to carry multiple bidirectional traffic flows and can support different
flow sizes without requiring changes to the physical infrastructure.
BRKSPV-1222 © 2018 Cisco and/or its affiliates. All rights reserved. Cisco Public 6
How does LIVE Broadcast Production Work?
Why NOT SDI?
• Unidirectional Transport
• Stretch wires across long
distance
• Replace wires when
production technology
changes (move from HD to
UHD)
Next Wave of IP Convergence - MEDIA
Enterprises
Decouple Application and Telecoms
Decouple Application and Broadcasters
Decouple Application and
(1990’s)
Policy From Underlying
Infrastructure
(2000’s)
Infrastructure
(Now)
Infrastructure
SDI Complexity – Capex and Opex

Trends
& 4K and 8K Ultra HD
Drivers
Economies of scale with IP and SDN
Capturing New Transitions
• Ready for today’s new formats and data rates

Transition to IP 10110101 1001010110
• Increased bandwidth with Ethernet
from SDI 101010101010
• Deterministic networking
• Move away from specialized, dedicated,

x86 expensive HW
Workloads • Towards general purpose, low cost compute
and storage
• Software Defined Networking (SDN), not

manual
Cloud • Application Policy Driven Infrastructure
Architectures • Treat the platform as reusable pools of
resources
Typical Broadcast Chain Today
HD- HD-
SDI IP SDI IP IP
Remote Studio & Post Primary Secondary Consumer
Production Contribution Production Distribution Distribution Experience
Broadcast Chain of the Future
IP IP IP IP IP
Remote Studio & Post Primary Secondary Consumer
Production Contribution Production Distribution Distribution Experience
Video, audio, metadata, intercom
Multiple signals per cable
Bi-directional signals
What can IP do for Frame format & rate agnostic
you? Live & file based workflows
Phase & Frame alignment
Dynamic infrastructure
New workflow models
Objective: Replace SDI Router with IP Fabric
Control Systems with
Control Panel
Playout
Cameras and
Microphones Monitoring
REST API Systems
Video Server Network

Relay and Clips Video Switcher
Controller
Graphic Multiviewer
Systems
Remote Source Audio Mixer

IP Fabric
Video Router BRKSPV-1222 © 2018 Cisco and/or its affiliates. All rights reserved. Cisco Public 15
How are Video and Audio carried over IP ?
• SMPTE 2022-6 : Encapsulation of SDI over IP (UDP/Multicast)
• AES 67 : Audio over IP and includes a PTP timing profile (UDP/ Unicast or
Multicast)
• TR-04: 2022-6 (For Video ) and AES 67 for Audio
• SMPTE 2110: Video, Audio and Ancillary Data as separate flows
(UDP/Multicast)
Industry Challenges and Requirements
SDI-based Unchanged Operator Workflow

Video Router
Deterministic Network
(Zero Packet Loss, Ultra Low Latency and Minimal Jitter)
Precision Time for Synchronization
IP Network System Availability
Network Security
Cisco Strategy
Open Standards Interoperability Based on COTS HW
Development and Supporting Rich Eco Benefit from Ethernet

Adoption System of Vendors Economies
Active Industry Participation
Joint Task Force on Professional Networked

Streamed Media (JT-NM)
Rich Ecosystem of Broadcast Vendors
and more …..
Cisco COTS Hardware
Nexus 9000 switching platforms

Fixed and Modular Form Factors
Deployment Models
Spine-Leaf CLOS Topology Single Modular Switch
• Scalable – Grow as you need • Familiar SDI router work flow

• Deployment flexibility – Cable management • Less optics – No inter-switch links
• Highly available – Reconfigure paths
Use Cases
Studio (multiple rooms) Sporting Venue OB Van/Truck
Spine-Leaf Spine-Leaf Single Modular Switch
Cisco’s IP Fabric for Media
IP Fabric for Media – Solution Components
Cisco Nexus
9200 Series
9300-EX Series
+
9500 –EX Series
9500 -R Series Cisco Nexus 9000 Series Cisco DCNM software
From Cisco’s Data Center Portfolio
System Architecture
Broadcast Controller Final authority on all policy decisions
and actions
REST PMN SDN API

Abstracts the Network and provides a
flexible API to the higher layers to
Network Control and orchestrate the Network
Controller
REST Robust IP Network built on open and

PUB-SUB events etc. proven technologies
Sources Destinations
IP Fabric
Typical Work Flow
Broadcast Controller
1 Tells sources to send flows

REST PMN SDN API
Flow Orchestration: Permits
2 flows & allocate BW
Network Tells destinations to receive
3 flows
Controller
REST
PUB-SUB events etc.
Destinations
Sources
IGMP join
IP Fabric
Cisco IP Fabric for Media
Response to Industry’s Challenges and Requirement
Non-Blocking Fabric Visibility and Analytics

Low Latency Information Rich Topology
1/10/25/40/100 Gbps Flow Visibility
Flow Statistics
Cisco IPFM
Plug-n-Play HA & Scale
Day 0 Deployment Spine-Leaf Topology
Image and Configuration Updates Flow Migration
Multicast and PTP Scaling
Security Open Standards

Endpoint Admission Control SMPTE 2022-6
Flow Authorization SMPTE 2110
Flow Policing PTP – SMPTE 2059-2, AES67
AMWA Network Control REST API
Data Center Network Manager
Data Center Network Manager
• Flexible network management and automation for Cisco Nexus programmable
fabrics
• Customizable using pre-validated configuration templates for bulk deployments
• Representational state transfer (REST) APIs allow easy integration from Cisco
or third-party managers
• Mature management solution popular with Enterprise and Data Center
customers
• Media Controller built over DCNM adds media specific functionalities over the
existing capabilities DCNM provides that is relevant to Media Industry
• Shipped as an OVA or ISO
http://www.cisco.com/c/en/us/products/cloud-systems-management/prime-data-center-network-manager/index.html
Fabric Provisioning – Day 0
Fabric Provisioning using POAP
• Similar to PXE boot

• Easy-to-use flow with
pre-shipped templates
• Preform day-0
configuration on your
fabric
Fabric Provisioning using POAP – Step 1
DCHP Scope
Specify IP range
Creating configuration from Template
Specify Switch
Serial Number
Image
Specifying Template Parameters
Topology and Host Discovery
Topology Discovery
• DCNM Media Controller automatically discovers the topology when fabric is
brought up using Power on Auto Provisioning
• If Fabric is provisioned via CLI, Switches needs to be manually discovered by
DCNM
Topology Discovery – Adding Switches to DCNM
DCNM GUI : Inventory -> Discover Switches -> LAN Switches
Specify Switch IP and Credentials

Using CDP information DCNM
discovers topology
Topology Discovery – Designate Role
Media Controller -> Topology
Click on a Switch and select its
role and leaf or spine
Choose Topology Layout
Host Discovery - Visibility
Host Discovery
• Host Can be discovered in one of the following ways
• When Host sends an ARP request for its default gateway – the switch
• When Sender Host sends multicast flow
• When a Receiver Host sends an IGMP join
• Manual addition of Host via an API
• Host information can be found on Media Controller -> Host

• Host is populated in the Topology Page providing a visual representation on
where the host is connected
Flow Orchestration
Flow Orchestration
• Media Controller is responsible to set up a flow between source and receivers
• Bandwidth Management algorithm running on the controller provides a
bandwidth guaranteed path for the flow ensuring zero drop multicast transport
• Receivers can request for a flow by sending an IGMP join
• Flows can also be setup using an API
Flow Orchestration - Non Blocking Multicast
DCNM updates Bandwidth
DCNM computes Non Usage thereby aware of Fabric
Blocking Path between Capacity for Future flows
Source and Receiver
Request sent to
DCNM Media
DCNM programs Source Controller
Leaf , Spine and Receiver
in Parallel
Flow Sent from Source to

Receiver
Sender Online.
Sender Registered with Receiver Request for a flow
DCNM
Receiver
Source A
Flow Setup - IGMP
• IGMP join sent by a receiver is sent to DCNM which programs the network by
setting up a path between source and receivers
• IGMP v2 and v3 reports are supported
• Immediate Leave supported – Flow Pruned as soon as receiver sends a leave
• SSM is supported as well
Flow Setup - API
• Flows can be provisioned via API
• Flows can be deleted via API
• The workflow involves broadcast controller requesting for a flow setup by
invoking an API
• Example for invoking an API from bash:
• curl -H "Content-Type: application/json" -k --header "Dcnm-Token":$dcnmtoken -X
POST -d '{"hostId": “10.1.1.1","hostInterface": “Ethernet1/1","multiCastIpAddress":
"231.12.11.120", "sender":"false", "seqNum":"125"}' https://<dcnm-
ip>/rest/pmn/switches/<receiver leaf ip>
Flow and Host Policy - Security
Flow Policy
• Flow Policy is used to specify
flow property – bandwidth and
DSCP marking
• Default Policy applied to flows
that do not have specific policy
applied
• Flow Policy ensures sufficient
bandwidth is provisioned on the
network
• Flow Policy ensure the sender
does not sent traffic at a rate
higher than what is provisioned
using the policy – Excessive Media Controller -> Policies -> Flow Policies
Traffic is policed
Quality of Service
Service Class (Flow/Content) L3 DSCP Queue
PTP Time and Sync* EF Priority
Intercom Audio EF Priority
AES67, 2110 Audio AF41 Priority or Rate
SMPTE 2022-6, 2110 Video AF41 Priority or Rate
2110 Ancillary Data CS5 Rate
Other 0 Best Effort
* On Cisco Switch PTP is treated with highest priority irrespective of its QoS Marking
Host Policy
• Host Policy is used to restrict/allow a
sender to send traffic to certain
multicast groups and a receiver to
subscribe to a certain multicast group
• Default policy can be whitelist or
blacklist
• Sender Host Policy is implemented by
an Ingress Access List programed on
the sender leaf
• Receiver Host Policy is implemented
by applying a IGMP filter on receiver
leaf
Media Controller -> Policies -> Host Policies
Host Policy
Double Click any Host

to view policies applied
to it
Flow Visibility, Bandwidth Tracking, Flow
Alias and Analytics
Flow Visibility
• One of Broadcast Industry biggest concerns moving to IP is losing the ability to
track flow path
• DCNM Media Controller provides end to end flow visibility on a per flow basis
• The flow information can be queried from DCNM GUI or via an API
• Broadcast Controller can obtain the flow information and provided end to end
visibility right from the end point/host NIC
Flow Visibility
Flow Visibility – Link Level
Double Click any link to obtain
bandwidth utilization along with active
flows on a link
A very useful tool to determine what

flows are carried on any given link that
could aid in troubleshooting
Bandwidth Utilization
User can be notified as and when

link bandwidth utilization crosses a
threshold
Link changes color based on utilization
Flow Alias
• Ability to name a flow
• Each Multicast IP can be associated with a Name
• Makes Life easy for the operations team
Flow Analytics
• DCNM maintains a real time per flow rate monitor
• Ability to provide the bit rate of every single flow in the system
• If a flow exceeds rate defined in flow policy the flow is policed and the policed
rate is also displayed
• Flow information is cached for a period of 24 hours*
• Flow information can be exported and stored for offline analysis
* Future release will provide the ability to extend this period
Flow Analytics
Media Controller -> Flow Status
Events and Notification
• Logs every action performed on the fabric
• This includes, but not limited to
• Host Add/Delete
• Flow/Host Polices changes
• Flow Add/Delete
• Bandwidth Utilization
• Insufficient bandwidth
• Flow Migration information during failure
• Link/Switch up/down etc.
• Broadcast Controller/User can subscribe to these notifications via AMQP
• AMQP messages are JSON formatted
https://www.amqp.org/
Determining the Topology – Non
Blocking Design
What Defines the Topology?
• Unlike how SDI routers were defined (example:1024x1024), IP Fabrics are
defined based on type of end points and their port requirements
• Consider the following example
• Gateways ; Ports Required 36x40G
• IP Camera’s ; Ports Required 150x10G
• Audio, Intercomm ; Ports Required 50x1G Copper ports
Deployment Options
Single Switch – No Controller Single Switch – With Controller Spine and Leaf – With Controller
OBVAN OBVAN/Studios Studios
Nexus 9000 Series Switches
36p 40/100G QSFP

Nexus 9236C
Leaf or Spine 48p 10/25G SFP + 6p 40/100G
QSFP
Nexus 93180YC-EX
Leaf Only
72p 40G QSFP
Nexus 9272Q
Leaf or Spine 48p 1/10GT + 6p 40/100G QSFP
Nexus 93108TC-EX
Leaf Only
Up to 288x 100G
Nexus 9500-R 48p 10/25G SFP + 4p 100G/
Spine or as a Single Switch
6p 40G QSFP
Nexus 92160YC-X
Leaf Only
Design : Bandwidth Consideration
Non Blocking CLOS Architecture
Bandwidth from Leaf to each Spine > Bandwidth of senders on that leaf
Bandwidth from Leaf to all Spines (aggregate) > Bandwidth of receivers on that
leaf
Design
• 9236C can be used as a Leaf for 40G Gateways
• Each supports up to 25x40G end point and requires 10x100G uplink
• 93180YC-EX can be used as a Leaf for 10G Camera’s
• Each supports up to 48x10G end points and requires 6x100G uplinks
• 93108YC-EX can be used as a Leaf for 1G Audio/Intercomm
• Each supports up to 48x1/10G T end points with 6x100G uplinks
Number of
End Points Platform/Quantity
Uplinks
Gateways-
9236C/2 20x100G
36x40G
Camers-
93180-EX/4 24x100G
160x10G
Audio and
InterComm- 93108-EX/2 4x100G
70x1G
Network Topology
9508
Spine
6x100G Uplinks
from each 93180
Leaf
10x100G Uplinks 2x100G Uplinks

from each 9236 from each 93108
Leaf Leaf
9236c 9236c 93180 93180 93180 93180 93108 93108

Leaf 1 Leaf 2 Leaf 3 Leaf 4 Leaf 5 Leaf 6 Leaf 7 Leaf 8
LIVE and FILE on Same fabric - QOS
Multicast (LIVE) and Unicast(FILE) in the IPFM Fabric
• Live production traffic is typically multicast, and requires assured forwarding
with minimal latency and zero drop.
• File based workflows are typically TCP, and lower priority compared to live
production flows.
• With QOS prioritization for multicast, IP fabric for media, guaranties that live
production traffic is not affected by file based flow in the fabric.
• Multicast traffic is mapped to a strict priority queue (highest level), where
unicast traffic is placed in a default queue (lowest level).
• If contention between multicast and unicast traffic, multicast traffic always
wins!
QoS in the IPFM – Architecture (Spine and Leaf)
Spine 2
First hop leaf - FHL 1 3 Last hop leaf - LHL
1. On the first hop leaf DCNM marks all multicast traffic coming from a source with a designated DSCP value, and assign it to a queue 7
the strict priority queue
2. / 3. Spines and Last hope leaf require manual QOS configuration with classification for unicast traffic to a default queue, and assigning
multicast traffic to priority queue. PMN templates in the DCNM have this configuration enabled.
Converged Infrastructure
Production, Playout, Control and Media Assets on Same IP Infrastructure
IP Fabric
Cloud
Deployment Architectures
IP Fabric for Media – 2022-6/2110
Network Controller
IP Fabric
End Points
IP Fabric with Redundant Networks
• Two Independent Fabric
• Two Independent Network Controller
• Single Broadcast Controller
• End point connected to both fabrics
Fabric A Fabric B
End Points
Connecting Encoders/Ingest/Playout
Flow Setup via API
Network Controller
IP Fabric
Outside
End Points
Connecting Encoders/Ingest/Playout – LIVE and FILE on
Same fabric
Flow Setup via API
Network Controller
Uncompressed Flows
IP Fabric
Compressed Flows post encoding
Outside
End Points
IP Fabric for Media – Distributed Studios
• Studios spread across buildings/locations
Broadcast Controller • Have Leaf Switches at Each Studio
• Aggregate it to Centrally Located Spine
Network Controller
Master Control Room
IP Fabric
Studio A Studio B Studio C
Multi Site – Remote Leaf • Remote Leaf Suitable when number of end point in Remote Site Small
• Most Traffic is sent to Main Site
Challenges:
• Latency in Control Network between Network Controller and Remote Leaf
• How will Broadcast Controller control end points in Remote Site
• Needs dark fiber (No Service provided or router in between remote leaf and Spine)
• PTP distribution : GM in main site
Main Site Remote Leaf
End Points
End Points
Multi-Site and Connecting to an external
PIM Router
Multi-Site and PIM Border
• Multi-Site and PIM Border is a feature with which the IPFM fabric can interconnect with
another site / external PIM Router
• Uses border-leaf to interconnect with an external site/router
• SSM only. No support for ASM*
• The sites that are interconnected work independently. DCNMs across sites do not
communicate with one another
* Support with ASM will be available in a future release. Refer software release notes
PIM Border
External PIM Network
PIM SSM support
Site A
ExS ExR
Layer 3 ports
Multi-Site and PIM Border
• DCNM GUI depicts border-leaf
and the remote hosts
(senders/receivers)
• Remote Sender : Host IP is that
of sender when sender is remote
and receivers are local
• Remote Receiver: Host IP is that
of next hop(PIM neighbor) when
sender is local and receiver is
remote
Multi-Site and PIM Border – Unicast Routing
• Unicast routing protocol is required across sites
• Unicast reachability to hosts in a remote site must be via the border leaf
OSPF
Multi-Site and PIM Border – Operation
(5) DCNM Programs a path and border leaf sends a PIM (S1B,GB) join to pull the traffic from remote site
(7) DCNM Programs a path and (S1B,GB) is sent to the requesting site
(3) DCNM queries Border Leaf for unicast reachability to S1B

Site B
Site A
(2) Request sent to DCNM
(4) Border Leaf informs DCNM S1B is reachable
(6) Border Leaf informs DCNM a request is made for (S1B,GB)
(8) Traffic forwarded
PIM (S1B,GB) join
Layer 3 ports
S1A S2A R1A R2A S2B S1B R1B R2B
(1) R1A send IGMPv3 join
Requesting for S1B,GB
API Integration with Broadcast
Controller
Broadcast Controllers
Control Plane
Media APIs
DCNM
Media Controller
IPFM
Spine Spine
vDCM
Leaf Leaf Leaf
XP VLI UC GV
NK IP Node
Legacy SDI Layer
© 2018 Cisco and/or its affiliates. All rights reserved. Cisco Public 103
Integration with Broadcast Controller
• IP Fabric for Media is designed to interface with any Broadcast Controller via
Open APIs
• This ensures unchanged operator experience while seamlessly migrating the
solution to IP
• Broadcast Controller/User can execute these API to perform various functions
such as flow setup, topology discovery, flow/host policy modification etc.
• Cisco is actively engaged with the wider industry to facilitate API adoption
• APIs continually evolve based on feedback from industry, partners and
customers.
http://www.cisco.com/c/en/us/td/docs/switches/datacenter/sw/10_1_x/rest_api/Cisco_DCNM_Rest_API_Guide_Release_10_1_x.html
APIs
• Authentication • API’s for Host Policy • API’s for Flow Policy
• Logon Management for Flow Management
data • Flow Policy Add
• Logout • Flow Policy Bulk Import
• Host Policy Add
• Get Flow Policies
• Topology and Inventory • Host Policy Bulk Import • Delete Flow Policies
APIs • Get Host Policies
• Delete Host Policies
• API’s for Host Policy • API’s for Operational

Management for Flow data • Host Management APIs Management
• Create Host
• Host Policy Add • Get Listing of all Active/Current Flows
• Bulk Import Hosts • Get Listing of all Flows that a selected
• Host Policy Bulk Import
• Get Hosts host participates in.
• Get Host Policies
• Delete Hosts • Get Listing of all Flows that a particular
• Delete Host Policies switch participates in
Network Design – Solution Integration
Recommended Setup with Broadcast Controller
• DCNM Media Controller NIC Eth1 (Fabric)- Switches in IP Fabric Communicate via Inband Network
• DCNM Media Controller NIC Eth0 (MGMT)- Broadcast Controller Connected via Control Network
• Broadcast Controller-End Points Communicate over Control Network
Failure Handling
How to Avoid any downtime ?
• Recommend a network design by implementing parallel networks and
connecting end points to both networks (2022-7)
• Any failure on one network will not affect traffic to end points as a copy of the
frame is always available on redundant network
• Failure recovery measure built into DCNM Media controller will ensure traffic
converges post recovery, however it could take a few seconds for
reprogramming of flows on other available paths
• Flows are not moved back to original path once original path recovers. New
flows will use the recovered path.
• DCNM Media Controller will provide list of affected flows caused by any failure.
IP Fabric with Redundant Networks
• Two Independent Fabric
• Two Independent Network Controller
• Single Broadcast Controller
• End point connected to both fabrics
Fabric A Fabric B
End Points
PTP For Media
How do I generate
a stable timing
signal from an
Ethernet port?
Source: an anonymous broadcast engineer
Time and Sync across market segments
Service Providers Industrial Solutions Financing and Trading
Smart Grid Media Science
IEEE 1588-2008 Precision Time Protocol
• Two Way Time Transfer protocol (TWTT)
• Accuracy in a well designed E2E model in the nanosecond range
• Boundary Clocks (BC) and Transparent Clocks (TC) aim correcting delay
variations, in both directions (asymmetry)
Ordinary
Clock
Boundary Transparent Ordinary Clock
grandmaster Clock Clock Leaf Slave
PTP PTP
Reference Recovered
Clock Clock
PTP
PTP profiles for media & broadcast
• AES67 (Audio driven)
• Based on IEEE 1588-2008 default profile /w specific message rates
• Announce: 1 {0,4}
• Sync: -3 {-4,1}
• DelayReq: 0 {-3,Sync +5}*
• Allow all devices to be either Master or Slave
• Multicast messages only
• Default PTP domain: 0 {0-255}
PTP profiles for media & broadcast
• SMPTE 2059 (Video driven)
• Based on a 5 sec fast locking requirement for endpoints /w spec rates
• Announce: -2 {-3,1}
• Sync: -3 {-7,-1}
• DelayReq: 0 {Sync +0, Sync +5}
• Default Slave mode unless can operate as Master
• Additional PTP TLV with media specific information
• Daily Jam Time, Default Frame rate, …
• Supports Multicast, Mixed (Mcast/Ucast) and Unicast modes
• Default PTP domain: 127 {0-127}
NX-OS implementation
• Support for AES67 message rates
• ptp announce interval aes67 <value>
• ptp sync interval aes67 <value>
• ptp delay-request minimum interval aes67 <value>
• Support for SMPTE 2059 message rates (and PTP mgmt TLV)
• ptp announce interval smpte-2059-2 <value>
• ptp sync interval smpte-2059-2 <value>
• ptp delay-request minimum interval smpte-2059-2 <value>
Why use PTP aware network devices?
• PTP performance degradation due to PTP message Jitter/Loss
• Competing with media flows, even if PTP messages are EF marked
• Boundary Clock PTP messages processed independently from IP traffic
• Reduce load on PTP nodes (multicast message processing)
• Boundary Clock will segment network hence reduce number of PTP nodes interacting
directly
• Simplify architecture: Remove ASM/RP for PTP mcast messages
• Boundary Clock handle PTP message processing and forwarding
Non PTP aware network w/ PTP messages in Priority Queue
Master -> DEV_04 -> DEV_03 (Layer 3) -> DEV_04 -> Slave, IMIX Loading, Expedited Forwarding for PTP Traffic, 64 msg/s
50000
50% - 50% - 0%
40000 50% - 50% - 0%
50% - 50% - 0%
30000 25% - 0% - 25%
25% - 0% - 25%
20000 25% - 0% - 25%
10000
ns
-10000
-20000
-30000
-40000
-50000
0 10 20 30 40 50 60
s
SMPTE Journal: Analysis of Precision Time Protocol (PTP) Locking Time – March 2014
Quality of implementation: PTP aware device
Baseline Test DEV03
100
Filtered Offset
Offset
50
ns
-50
-100
0 50 100 150 200 250 300
SMPTE ATC 2014: PTP deployment in large networks
s
Non PTP aware + 6x 3G-SDI (overload 10G)
S2_DEV03_DEV04_DEV05_4.log
Filtered Offset
4000
2000
ns
-2000
-4000
0 50 100 150 200 250 300

SMPTE ATC 2014: PTP deployment in large networks s
PTP aware + 6x3G-SDI 3(overload 10G)
Cascaded BCs with 3 SDI Streams
100
Filtered Offset
50
ns
-50
-100
0 50 100 150 200 250 300
SMPTE ATC 2014: PTP deployment in large networks s
SMPTE PTP Demo at Annual Tech Conference 2016
PTP Network Topology
• PTP aware network with Boundary Clocks
• Limits PTP traffic on each port vs. general multicast traffic & reachability
• Consistent PTP message rates across all devices
• Grandmaster (and candidate GMs):
• Are “normal” PTP endpoints -> Connected to a Leaf
• Using common reference signal (typically GPS)
• Slaves:
• Set all PTP endpoints to Slave only mode, except GMs (obviously)
• Use 1pps output to compare to reference signal from GM (monitoring)
Conclusions
• PTP network design and endpoint target performance must be established
• PTP-aware devices (Boundary Clocks) reduce overall endpoint message load,
jitter/loss
• Endpoints should (ideally) all be configured to Slave only, except those that are
candidate Master
• Early days for PTP media endpoints, many implementations still require
optimisations
PTP and Multi Site
No PTP Extension
• Keep PTP separated between sites

• Ensure the GMs at all sites are synced to GPS
• Signal going from one site to another may need to be re-clocked
Customer Deployment
Use Cases
Studio (multiple rooms) Sporting Venue OB Van/Truck
Spine-Leaf Spine-Leaf Single Modular Switch
Multi Site
HQ Branch
IP Network
Branch
Stadium
OB Van / Production Truck
• Live UHD broadcast from IP-enabled truck • UK Premier League broadcast with BT Sport
• World’s first live 4K UHD broadcast
• Platform: N9508
Live Studio Production
• State-of-the-art IP production studio • Broadcasting live shows everyday

• Expanding to multiple sites
• Platform: N9508
Master Control Room Broadcasters in USA and Brazil
• Most common use case • Broadcasting live sports and TV shows

• Allows resource reuse and improves efficiency
• Platform: N9300 and N9200
Event Live Production and Playout
• Cisco on Cisco Story • Live broadcast at the venue and online

• Internal customer for IPFM • Repeat broadcast online
• Platform: N9300
Playout Multi-Site
• Another common use case • Connect multiple locations via dark fiber
• Platform: N9300 and N9508 • Platform: N9300 and N9508
Conclusion
Answering Industry Challenges and Requirements
Unchanged Operator Integration with Broadcast

SDI-based Workflow Controllers
Video Router
Deterministic Network Non Blocking Network Design

(Zero Packet Loss, Ultra Low with Bandwidth Aware Flow
Latency and Minimal Jitter) Setup
Precision Time for

SMPTE 2059-2, AES67 profile
Synchronization
System Availability Redundant Network (-7)

IP Network
Network Security Flow and Host Policies
Useful Resource
• IP Fabric for Media on Cisco.com
• Design Guide
• DCNM
• Solution Guide
Cisco Spark
Questions?
Use Cisco Spark to communicate
with the speaker after the session
How
1. Find this session in the Cisco Live Mobile App
2. Click “Join the Discussion”
3. Install Spark or go directly to the space
4. Enter messages/questions in the space
cs.co/ciscolivebot#BRKSPV-1222
• Please complete your Online Complete Your Online
Session Evaluations after each
session
Session Evaluation
• Complete 4 Session Evaluations
& the Overall Conference
Evaluation (available from
Thursday) to receive your Cisco
Live T-shirt
• All surveys can be completed via
the Cisco Live Mobile App or the
Communication Stations
Don’t forget: Cisco Live sessions will be available
for viewing on-demand after the event at
www.ciscolive.com/global/on-demand-library/.
Continue Your Education
• Demos in the Cisco campus
• Walk-in Self-Paced Labs
• Tech Circle
• Meet the Engineer 1:1 meetings
• Related sessions
Thank you

BRKSPV-1222-Cisco IP Fabric Arquitectures For Video Production and Broadcast Workflows PDF

Загружено:

Сведения о документе

Оригинальное название

Авторское право

Доступные форматы

Поделиться этим документом

Поделиться или встроить документ

Параметры публикации

Этот документ был вам полезен?

Это неприемлемый материал?

Авторское право:

Доступные форматы

BRKSPV-1222-Cisco IP Fabric Arquitectures For Video Production and Broadcast Workflows PDF

Загружено:

Авторское право:

Доступные форматы

BRKSPV-1222

IP Fabric Architectures for

Rahul Parameswaran – Technical Marketing Engineer

SDI Complexity – Capex and Opex

• Ready for today’s new formats and data rates

• Move away from specialized, dedicated,

• Software Defined Networking (SDN), not

Video Server Network

Remote Source Audio Mixer

SDI-based Unchanged Operator Workflow

Precision Time for Synchronization

IP Network System Availability

Open Standards Interoperability Based on COTS HW

Development and Supporting Rich Eco Benefit from Ethernet

Joint Task Force on Professional Networked

and more …..

Nexus 9000 switching platforms

• Scalable – Grow as you need • Familiar SDI router work flow

Spine-Leaf Spine-Leaf Single Modular Switch

9500 -R Series Cisco Nexus 9000 Series Cisco DCNM software

From Cisco’s Data Center Portfolio

REST PMN SDN API

REST Robust IP Network built on open and

1 Tells sources to send flows

Non-Blocking Fabric Visibility and Analytics

Security Open Standards

• Similar to PXE boot

Specify Switch IP and Credentials

Choose Topology Layout

• Host information can be found on Media Controller -> Host

Flow Sent from Source to

PTP Time and Sync* EF Priority

Intercom Audio EF Priority

AES67, 2110 Audio AF41 Priority or Rate

SMPTE 2022-6, 2110 Video AF41 Priority or Rate

2110 Ancillary Data CS5 Rate

Other 0 Best Effort

Double Click any Host

A very useful tool to determine what

User can be notified as and when

Link changes color based on utilization

* Future release will provide the ability to extend this period

36p 40/100G QSFP

10x100G Uplinks 2x100G Uplinks

9236c 9236c 93180 93180 93180 93180 93108 93108

First hop leaf - FHL 1 3 Last hop leaf - LHL

Flow Setup via API

Flow Setup via API

Studio A Studio B Studio C

Main Site Remote Leaf

External PIM Network

PIM SSM support

(3) DCNM queries Border Leaf for unicast reachability to S1B

(2) Request sent to DCNM

(4) Border Leaf informs DCNM S1B is reachable

(6) Border Leaf informs DCNM a request is made for (S1B,GB)

(8) Traffic forwarded

PIM (S1B,GB) join

Leaf Leaf Leaf

Legacy SDI Layer

• API’s for Host Policy • API’s for Operational

Service Providers Industrial Solutions Financing and Trading

Smart Grid Media Science