Tiered Knowledge Map: SMPTE 2110 Essentials for Junior Engineers

This structured knowledge map outlines the minimum essential knowledge for a junior engineer to function in a broadcast facility using SMPTE ST 2110 (professional media over IP). It is organized in five tiers of ascending expertise, from basic networking fundamentals to full IP deployment case studies. The focus is on practical, results-oriented skills – the things an engineer will actually use day-to-day – with blunt explanations and examples of why each topic matters. The goal is to produce an engineer who can think critically and troubleshoot real problems in an ST 2110 facility, rather than just reciting theory. Audience baseline: You might have set up a Ubiquiti router or PiHole at home, but perhaps lack deeper networking knowledge (e.g. IP subnetting, multicast). This guide will fill those gaps step by step, emphasizing what you must know to work with SMPTE 2110 in live production environments.

Tier 1: Foundational Concepts

At Tier 1, the engineer builds a solid foundation in general networking and computing concepts. These are not specific to broadcast, but without them, an engineer will be lost when dealing with IP-based media. If you don’t understand these basics, nothing in SMPTE 2110 will make sense.

Basic Networking (OSI Layers 1-3 and 7)

OSI Layer 1 – Physical: Understand the physical media and hardware that make up the network:

• Cabling (Copper vs Fiber): Traditional SDI video runs on coaxial cables, but IP media networks rely on Ethernet cabling (often fiber optics for high bandwidth). For example, a 1080p60 uncompressed video stream (~3 Gbps) cannot travel over old 1 Gbps copper; studios now use 10 Gbps or 25 Gbps links, which typically means fiber optic cables and SFP modules, not RJ45 copper. Modern IP broadcast infrastructures “use fiber and IP signals” instead of coax

• smpte.org

• . You should be comfortable handling fiber connectors, SFP transceivers, and knowing the difference between single-mode and multi-mode fiber. (Why it matters: If a camera’s 25 GbE fiber link is dirty or mis-patched, you need to diagnose the physical layer – no amount of software debugging will fix a disconnected cable.)

• Network Interfaces & Switches: Know that devices connect via Ethernet interfaces to network switches. Each device has a MAC address (Layer 2). Switches forward frames based on MAC addresses within a local network (LAN). Basic troubleshooting: verify link lights, check port speeds (e.g. a 1G device on a 10G switch port must negotiate correctly), and ensure the physical link is up.

OSI Layer 2 – Data Link: Learn what a LAN is and how switching works:

• Ethernet and Frames: All IP media streams ultimately ride inside Ethernet frames on a LAN. If multiple devices are on the same Ethernet switch and same VLAN, they can send frames directly to each other using MAC addresses. No IP routing is needed in this case.

• VLANs: Virtual LANs can partition a switch into separate networks. At this stage just grasp that a VLAN ID tags traffic to segregate it. (We’ll use this in Tier 2 to isolate media or control traffic as needed.)

OSI Layer 3 – Network (IPv4): Grasp IP addressing and subnets:

• IP Addresses and Subnets: Every device in an IP network has an address (e.g. 192.168.100.10/24). You must be able to determine if two IPs are in the same subnet or not (e.g. 192.168.100.10/24 can talk directly to 192.168.100.200/24, but not to 192.168.101.5/24 without a router). If you don’t understand subnet masks (like /24), review this now – misconfigured IPs are a frequent cause of “why can’t this receiver see that sender?” in IP systems.

• Routing vs Switching: Know the difference between a router and a switch. A router (Layer 3 device) forwards packets between different IP networks; a switch (Layer 2) forwards frames within the same network. In a 2110 facility, you might have an IP router or Layer3 switch connecting separate subnets (e.g. separating production and corporate networks), and you’ll need to ensure your media devices either share a subnet or have a route between them. (Why it matters: If a camera is on 10.0.1.x and a monitor on 10.0.2.x with no routing, they will not see each other’s streams – a common rookie mistake.)

OSI Layer 7 – Applications: Recognize that above the network, we have application protocols:

• In ST 2110 systems, examples include RTP streams carrying the media (video, audio, etc.) and protocols like NMOS (HTTP/JSON APIs for control – more on that in Tier 3). OSI layers 4-6 (transport/session/presentation) we won’t delve into deeply here, but note that SMPTE 2110 primarily uses UDP at Layer 4 (User Datagram Protocol, for low-latency streaming) rather than TCP. Application-layer understanding means knowing that, for instance, a video stream might be an RTP/UDP flow on a certain UDP port, and a discovery service might be an HTTP REST API on a certain port.

Key Example (Layer Mistake): If someone accidentally plugs a device into the wrong VLAN or switch port, it could be isolated at Layer 2 and never get the multicast stream. A solid foundation in OSI layers helps you systematically check: Is the fiber link up (Layer 1)? Is the device seen in the switch MAC table (Layer 2)? Does it have an IP in the correct range (Layer 3)? This thought process is fundamental.

Computing Basics and System Setup

While networking is the focus, a few general computing skills are assumed:

• Operating Systems & CLI: Be comfortable with using a computer to configure devices – e.g. accessing a switch’s command-line interface or a device’s web interface. Know how to set a static IP on your laptop’s NIC so you can talk to gear on an isolated network. Familiarity with Linux is a plus (many broadcast appliances run on Linux internally).

• Basic Services: Understand what DHCP is (for IP address assignment) and DNS (name resolution), even if in many ST 2110 facilities devices use static IPs or host files. This helps when devices register hostnames or when setting up control systems.

• Security mindset: While not deeply covered here, be aware that media networks are usually tightly controlled – no internet, and often isolated from corporate networks to prevent congestion or malicious traffic. Always double-check before plugging random devices into a media network.

Critical Physical Infrastructure Knowledge

• Sync and Reference Signals: Even at this foundational level, know that professional video systems require synchronization. In analog/SDI systems, this was done with black burst or tri-level sync signals distributed to all devices. In IP systems, as we’ll expand in Tier 3, the equivalent is PTP (Precision Time Protocol). Just remember: nothing works reliably if devices aren’t genlocked or PTP-locked to a common time base.

• Power and Environment: Ensure you consider things like proper powering (UPS for critical gear), cooling, and that fiber cables don’t get bent/damaged. A junior engineer on site might be tasked with running fiber to a new camera – understanding how fragile fiber can be and how to test it (visual inspection, fiber tester) is important operationally.

By the end of Tier 1, you should comfortably speak the language of basic IT networks. For example, you should be able to say, “Camera X can’t ping the production switch – maybe it’s on the wrong subnet or the fiber link is down,” and know how to start checking that. This lays the groundwork for the broadcast-specific layers to come.