IBC2022 IPShowcase: Tips for Media-over-IP Network Design

KojiOyama 44 views 28 slides May 21, 2024
Slide 1
Slide 1 of 28
Slide 1
1
Slide 2
2
Slide 3
3
Slide 4
4
Slide 5
5
Slide 6
6
Slide 7
7
Slide 8
8
Slide 9
9
Slide 10
10
Slide 11
11
Slide 12
12
Slide 13
13
Slide 14
14
Slide 15
15
Slide 16
16
Slide 17
17
Slide 18
18
Slide 19
19
Slide 20
20
Slide 21
21
Slide 22
22
Slide 23
23
Slide 24
24
Slide 25
25
Slide 26
26
Slide 27
27
Slide 28
28

About This Presentation

This presentation provides you the design flow and some common pitfalls when broadcast network engineers consider their Media-over IP (MoIP) network architecture and configure its network switches. In addition to the essential technology such as VLAN, VRF, IGMP, PIM, and OSPF I introduced at the N...


Slide Content

Tips for Media-over-IP Network Design
Koji Oyama, Xcelux Design Inc.
[email protected]

Introduction
Media-over-IP (MoIP) Network Design
Verification and Design Pitfalls
Conclusion
Agenda
10/Sep/2022 © 2022 Xcelux Design Inc. 2

Koji Oyama https://www.linkedin.com/in/koji- oyama/
Technical Consultant, Evangelist, Hardware/Software Engineer
Founder and CEO, Xcelux Design
10+ yrs engineer & 10+ yrs sales/marketing experience
Love New Technology
My mission recently: Increase MoIP network engineers
Xcelux Design, Inc. www.xceluxdesign.com
Technical Consulting Company
Founded in October 2016
Tokyo, Japan San Jose, CA
Targeting area: IP network infrastructure, AI interpretation
Introduction
© 2022 Xcelux Design Inc. 310/Sep/2022

Target Audience :
1.MoIP beginners
a.Broadcast engineers who are NOT familiar with IP network technology
b.IT network engineers who WANT to know what else is necessary to learn for MoIP network design
Recommend to watch my previous presentation at NAB2022 “Essential for MoIP Network Design”
https://youtu.be/dY9NXhGOwgQ
2.Project managers and leaders who want to know what to take care of during developing an
MoIP infrastructure
Goal of the presentation today:
You can get hints for learning these technologies  You can get some keywords today!
30 mins are not enough to learn whole things
All of MoIP tech are based on common network technologies
Tons of network design information are on the internet
 Google it with the keyword you get today!
Goal of this presentation
© 2022 Xcelux Design Inc. 410/Sep/2022

Objective: Deploy enough MoIP network experts worldwide
Strategy: Networking & Education
Invite you to the slack channel ‘MoIP Square’ if you want
E-mail me
Share template files for common network switches
Share issues to find solution
Let’s help each others
SDN controllers will be able to configure all NW switches in the near future, BUT…
If you don’t know fundamental network technologies, you’ll never analyze any issues when
your system doesn’t work as expected
© 2022 Xcelux Design Inc. 5
Objective of My Project
10/Sep/2022

Video, audio, and meta data on IP protocols
Multicast for media + Unicast for control
IPv4 multicast
UDP size specified in SMPTE ST 2110- 10
Receive media data using IGMP when you want
that data
Based on the manner to send data when needed for
network paths that require transmission
IGMP v3 + PIM-SSM
Plus, SSM mapping + IGMP v2
if you have equipment which does not support IGMP v3
Introduction: Media over IP (1)
© 2022 Xcelux Design Inc. 610/Sep/2022
Request
To join
the group
receiver A
Multicast
232.100.10.1232.100.20.3232.100.30.7232.100.40.9
MoIP Network
(media plane)
PIM-SSM
IGMP v3
receiver B
receiver C
(S,G) = (192.168.10.1,
232.100.10.1)
(S,G) = (192.168.10.1,
232.100.10.1)
(S,G) = (192.168.30.7,
232.100.30.7)
L2/L3 NW Switch
L2/L3 NW Switch
L2/L3 NW Switch
L2/L3 NW Switch

JT-NM TR-1001-1:2020
http://www.ipshowcase.org/wp-content/uploads/2019/05/1030- Koji-Oyama-
20190409_IPShowcase-NAB19_M3L-CurrentStatus-ST2110- over-25GbE_v100.pdf
Media Node Requirements
Comply with SMPTE ST 2110 & ST 2059
Implement SMPTE ST 2022- 7:2018
Expose NMOS IS-04/05 entries
Implement AMWA BCP-002-01
Implement AMWA NMOS IS-08
Utilize IPv4 Multicast addressing for streams
Utilize DHCP
Store current operating settings
Store System ID and DHCP-assigned address, and check at re-
start
Support the entire range of multicast addresses from 224.0.2.0
through 239.255.255.255
224.0.0.0/8 : reserved for common protocol
232.0.0.0/8 : use for PIM-SSM
239.0.0.0/8 : some addresses used for specific venders and equipment
Introduction: Media over IP (2)
© 2022 Xcelux Design Inc. 710/Sep/2022

Not only physical but
also logical design is
necessary
Bottom-up design
whileverifyingthe
feasibility of a specific
functionality
w/minimal network
configuration is likely
to result in faster
design / verification
convergence
MoIP Network Design Flow
810/Sep/2022
List up all media and control nodes
Count the number of physical ports
of equipment to be connected
List all media and control sessions
Physical Network Design Logical Network Design
Calculate bandwidth of each ports
Select adequate
network switches
assign IP addresses for
each sessions and multicast groups
Calculate the max bandwidth
of each sessions
Structural Design: abstract to specific
(logical /physical architecture, isolation, fault tolerance)
Check behavior using
actual network with the
minimum configuration
Verification (normal & abnormal sequences)
configure switches
Documentation
Revise / Modify the specification Review
Finish
List all required
functionalities
Allow the
iteration
© 2022 Xcelux Design Inc.

These design and verification process is similar as common software development
process
1.But check physical cabling is correct at first  This is still the basic
2.Estimate more network design and verification time than you thought when planning
Fixing the design with step-wise refinement
Some flexibility are necessary to adjust both senders and receivers at the verification phase
Time can be used efficiently by performing unit tests of NW switches in parallel with node-side
combination tests
3.Know that bottom -up design is better
Agile process is often suitable better than Waterfall for MoIP development
Pursuing a simpler and quicker design & verification iterations than design accuracy, at the beginning phase
4.Accumulate simple verification method & tools when you check a specific functionality
Larger and more complex the system becomes, more debugging time might be necessary at the design
and verification phase
So that you can build full- or semi- automatic testing in the near future by combination such tools
Tips #1: Design and Verification Process
© 2022 Xcelux Design Inc. 910/Sep/2022

Production for Video,
Audio, Inter-comm
Spine-Leaf NW
switches
Non-blocking
ST 2059 PTP
Boundary clock
BMCA
Redundant (ST 2022-7)
Separated media and
control plane
Logically / Physically
MoIP Network Example
© 2022 Xcelux Design Inc. 1010/Sep/2022
Grandmaster Grandmaster
L3 NW Switch L3 NW Switch
L2/L3 NW Switch L2/L3 NW SwitchL2/L3 NW SwitchL2/L3 NW Switch
L2/L3 NW Switch L2/L3 NW Switch
Media Plane
Control Plane
audio
Inter-comm
Inter-comm
Inter-comm
playout
video

The commands to
configure NW switches
differ depending on the
switch vendors and the
installed network OS
Use CLI or GUI to
configure a switch
via ethernet interface
or serial interface
Configure Network Switches
© 2022 Xcelux Design Inc. 1110/Sep/2022

1). VLAN
2). VRF
3). Multicast routing
3-a). PIM
3-b). IGMP
4). OSPF
5). LAG/LACP
6). VRRP
Essential Network Technologies
© 2022 Xcelux Design Inc. 1210/Sep/2022
Checklist
Check how many keywords you’re already familiar with
Watch my video @NAB22 IP Showcase https://youtu.be/dY9NXhGOwgQ

https://en.wikipedia.org/wiki/Virtual_LAN
It is a technology to set virtual groups of devices and operate each as if they were one LAN
It is any broadcast domain that is partitioned and isolated in a network
Use for Media Plane and Control Plane, Layer 2
Port VLAN, Tag VLAN (IEEE802.1Q)
1). VLAN (Virtual Local Area Network)
© 2022 Xcelux Design Inc. 1310/Sep/2022
L2 NW Switch
L2 NW Switch
192.168.200.11
192.168.200.12
192.168.200.13
192.168.200.14
192.168.200.15
192.168.200.16
Segment
= 192.168.200.0/24
L2 NW Switch
L2 NW Switch
192.168.100.1
192.168.100.2
192.168.100.3
192.168.100.4
192.168.100.5
192.168.100.6
Segment = 192.168.100.0/24
trunk
VLAN100
VLAN200
Logically partitioned
and isolated
(Physically resource
shared)
L2 NW Switch
L2 NW Switch
Physically partitioned
and isolated

https://en.wikipedia.org/wiki/Virtual_routing_and_forwarding
It allows you to configure multiple virtual routers in one router.
It allows multiple instances of a routing table to co-exist within the same router at
the same time
Use for Media Plane (and Control Plane), Layer 3
2). VRF (Virtual Routing and Forwarding)
© 2022 Xcelux Design Inc. 1410/Sep/2022
L3 NW Switch
L3 NW Switch
10.1.10.1/16
VLAN110
10.1.20.2/16
VLAN12010.1.30.3/16
VLAN130
10.1.40.4/16
VLAN14010.1.50.5/16
VLAN150
10.1.60.6/16
VLAN160
VLAN100
10.1.0.12/16
10.1.0.21/16
L3 NW Switch
L3 NW Switch
10.2.10.11/16
VLAN210
10.2.20.12/16
VLAN220
10.2.30.13/16
VLAN230
10.2.40.14/16
VLAN24010.2.50.15/16
VLAN250
10.2.60.16/16
VLAN260
VLAN200
10.2.0.12/16
10.2.0.21/16
Physically partitioned
and isolated
VLAN100
L3 NW Switch
VLAN200
L3 NW Switch
Logically partitioned
and isolated

https://en.wikipedia.org/wiki/Multicast_routing
a method of transmitting to all subscribers
registered in a group by one transmission
Use for Media Plane
Multicast protocols: PIM, Multicast BGP, …
3). Multicast routing
© 2022 Xcelux Design Inc. 1510/Sep/2022
Unicast (one- to-one)Broadcast (one-to-all)
Multicast (one-to-many) Anycast
(one-to-one-of-many)

https://en.wikipedia.org/wiki/Protocol_Independent_Multicast
One of multicast routing protocol
PIM does not include its own topology discovery mechanism  Protocol Independent
Use for Media Plane
4 variants: PIM- SM, PIM- DM, Bidir-PIM, PIM-SSM
3-a). Multicast routing:
PIM(Protocol Independent Multicast)
© 2022 Xcelux Design Inc. 1610/Sep/2022

https://en.wikipedia.org/wiki/Internet_Group_Management_Protocol
It is a communications protocol used by hosts (receivers) and adjacent routers on IPv4
networks to establish multicast group memberships
It allows the network to direct multicast transmissions only to hosts that have requested them
Use for Media Plane
3-b). Multicast routing:
IGMP (
Internet Group Management Protocol)
© 2022 Xcelux Design Inc. 1710/Sep/2022
These diagrams are quoted from https://mrncciew.com/2012/12/25/igmp-basics/

https://en.wikipedia.org/wiki/Open_Shortest_Path_First
It is one of routing protocols for IP networks
It gathers link state information from available routers and constructs a topology map of the
network
You don’t need to make a routing table manually, OSFP does automatically
But you have to consider how a routing table changes when one of switches accidentally stops
Use for Media Plane or Control Plane
4). OSPF (Open Shortest Path First)
© 2022 Xcelux Design Inc. 1810/Sep/2022
Media Node
192.168.130.2/24
OSPFOSPF
OSPF
VLAN100
VLAN110 VLAN120 VLAN130
192.168.130.0/24
 192.168.130.254
192.168.130.0/24  192.168.120.253192.168.130.0/24  192.168.110.253

https://en.wikipedia.org/wiki/Link_aggregation
It is the combining (aggregating) of multiple network connections in parallel by
any of several methods
Implementation for Ethernet = LACP
1.Maximum number of bundled ports allowed in the port channel: Valid values are usually from 1 to 8.
2.LACP packets are sent with multicast group MAC address 01:80:C2:00:00:02
3.During LACP detection period
LACP packets are transmitted every second
Keep-alive mechanism for link member: (default: slow = 30s, fast=1s)
4.Selectable load-balancing mode is available in some implementations
5.LACP mode :
Active: Enables LACP unconditionally.
Passive: Enables LACP only when an LACP device is detected. (This is the default stateControl Plane
MLAG: Multi-chassis Link Aggregation Group

https://en.wikipedia.org/wiki/Multi-chassis_link_aggregation_group
It is a type of LAG with constituent ports that terminate on separate chassis
Use for Control Plane
5). LAG (Link Aggregation Group)
/ LACP (
Link Aggregation Control Protocol)
© 2022 Xcelux Design Inc. 1910/Sep/2022
This diagram is quoted from
https://docs.nvidia.com/networking/displa
y/ONYXv381174/MLAG

https://en.wikipedia.org/wiki/Virtual_Router_Redundancy_Protocol
It provides for automatic assignment of available IP routers to participating hosts
Increase the availability and reliability of the network
Use for Control Plane
6). VRRP (Virtual Router Redundancy Protocol)
© 2022 Xcelux Design Inc. 2010/Sep/2022
This diagram is quoted from
https://www.globalknowledge.com/us-en/resources/resource-
library/articles/hot-standby- router-protocol-vs-virtual-router-
redundancy- protocol-what-s-the-difference/#gref

Prepare debugging ports on NW switches connecting to a powerful PC in order
to monitor IP packets I explained with the previous slides 1) to 6)
Learn to use WireShark: https://www.wireshark.org/

Analyze protocols at the packet level  This is the best way to find out what’s happening
PTP Track Hound is also useful to see PTP protocols: https://www.ptptrackhound.com
Experts can build automatic verification scenarios on the PCs with Python etc.
Tips #2: Prepare Debugging & Testing PCs
© 2022 Xcelux Design Inc. 2110/Sep/2022
A monitoring port is
configurable by NW
switch settings
Automatic Testing
Debugging / Monitoring

The unpredicted issues based-on my experience so far:
1.Bandwidth overflow when switching multicast streams dynamically within one
cable at the high load
Caused by short time between IGMP leave and join
2.Unintended network path routed by OSPF in the event of a network switch
failure
Pitfalls: MoIP- specific Issue Examples
© 2022 Xcelux Design Inc. 2210/Sep/2022

Issue: Bandwidth overflow when switching multicast streams dynamically
within one cable at the high load
It is caused by short timing between IGMP leave and join
2 streams of the previous and new streams might be overlapped in a short time
Issue#1:Bandwidth Overflow
© 2022 Xcelux Design Inc. 2310/Sep/2022
1).Issue IGMPv3
Membership Report (Join)
S = IPaddr_2, G=232.2.0.21
3) Multicast routing
4) Multicast
routing
5) Issue IGMPv3 Membership Report (Leave)
S = Ipaddr_2, G=232.2.0.21
6)IssuePIMv2 Prune
S = Ipaddr_2, G=232.2.0.21
7) Multicast unrouting
12) Multicast unrouting
IPaddr_2
IPaddr_1
VRF1
VRF3
Receiver
(Media Node #1)
Sender 1
(Media Node #2)
Sender 2
(Media Node #3)
VRF2
2).Issue PIMv2 Join
S = IPaddr_2
G=232.2.0.21
8).Issue IGMPv3 Membership Report (Join)
S = IPaddr_3, G=232.3.0.31
9).Issue PIMv2 Join
S = IPaddr_3
G=232.3.0.31 10) Multicast routing
11) Multicast routing
It might happen 11) before 12)
IPaddr_3
time
Bandwidth

Workarounds:
1.Design with sufficient timing margin between IGMP leave and join
2.Set the IGMP immediate leave option if NW switch has
3.Design with sufficient margin of bandwidth
Issue#1:Bandwidth Overflow (cont’d)
© 2022 Xcelux Design Inc. 2410/Sep/2022

Issue: Unintended network path routed by OSPF in the event of a
network switch failure
OSPF might find out the shortest route dynamically with unpredicted path at the
designing at abnormal situation
Issue#2:Unintended Network Path
© 2022 Xcelux Design Inc. 2510/Sep/2022
Expected routing
path by OSPF
when VRF2 down
VRF2
VRF8 VRF9
VRF1 VRF3 VRF4 VRF5
VRF6 VRF7
VRF9
Normal routing path by OSPF
Multicast steam to VRF9 Restricted by ssm range
Unpredicted routing
path by OSPF
when VRF2 down
No routing path to VRF9

Workarounds:
1.Set some next-hop information statically in a routing table
The contents which never want to change obviously even in an irregular situation
Issue#2:Unintended Network Path (cont’d)
© 2022 Xcelux Design Inc. 2610/Sep/2022

As more MoIP facilities are developed,
there will be a greater shortage of MoIP network engineers
It takes some time to become an MoIP network experts
To be MoIP experts need more software-engineering skill
Let's communicate more among MoIP engineers
See you again at the NAB show next year
More tips to help you developwouldbeopen
Conclusion
© 2022 Xcelux Design Inc. 2710/Sep/2022

Any Questions?
Koji Oyama, Xcelux Design Inc.
[email protected]
+81-90-1127-2023 / +1- (408) 714- 8808
Thank you!
Feel free to contact me!
The workstyle of MoIP engineers is changing!
Work anywhere in the world!!
This photo shows how I configured NW switches in
Tokyo from the resort island in Thailand
Welcome to the MoIP world!!!