SDI Failsafe IP Routing: Inside the UTAH-400 Series 2 Router

SDI Failsafe IP Routing: Inside the UTAH-400 Series 2 Router A pure-IP routing core has no inherent fallback. When the ST 2110 network degrades, when the PTP grandmaster drops offline, or when an NMOS controller loses its session state, every signal path in that core is at risk simultaneously. The failure domain covers an entire facility.

Understanding how the UTAH-400 Series 2 addresses this requires looking at hybrid SDI/IP routing architecture from the failure mode outward - starting with the specific conditions a pure-IP core cannot survive, and then examining how an embedded SDI crosspoint changes the calculus.

Quick Links

The Failure Modes a Pure-IP Core Cannot Absorb

What Embedded Gateway Actually Means in the UTAH-400

How the SDI Crosspoint Stays Live When the IP Network Fails

PTP Grandmaster Loss: The Timing Failure Pure-IP Systems Cannot Absorb

Control Plane Failure and Single-Interface Management

What This Means for IT Directors

FAQ

The Failure Modes a Pure-IP Core Cannot Absorb

Broadcast IP infrastructure fails in ways that have no clean IT parallel. Three failure modes, in particular, expose the architectural gap in pure-IP routing designs:

Network Fabric Congestion or Partition ST 2110 uncompressed video flows are multicast streams with strict bandwidth and latency requirements. A single 1080i 59.94 ST 2110-20 video flow (including protocol overhead) consumes approximately 1.5 Gbps. At scale, a 1056 1056 router equivalent represents thousands of simultaneous flows traversing a managed Ethernet fabric. If that fabric experiences congestion, a spanning-tree reconvergence event, or a VLAN misconfiguration, signal loss is immediate and facility-wide. There's simply no SDI wire holding the path open.

PTP Grandmaster Loss SMPTE ST 2110 timing depends on IEEE 1588 Precision Time Protocol (PTP). Every media node in the system - senders, receivers, encoders - locks to a PTP grandmaster clock to maintain sample-accurate synchronization across the IP network. If the grandmaster fails, and no boundary clock or secondary grandmaster assumes the role quickly enough, receivers begin dropping audio and video samples.

In a facility still running analog Black Burst references on legacy equipment, those two timing domains are entirely separate. A PTP failure does not protect SDI-connected devices, and vice-versa.

Control Plane Isolation NMOS IS-05 connection management depends on an active, reachable registry and controller. If the controller loses network access to a device - due to a switch failure, a software crash, or a misconfigured ACL - that device cannot be re-routed until connectivity is restored. The crosspoint state is frozen. Planned changes, emergency re-routes, and manual override attempts all depend on the same network path that just failed.

What Embedded Gateway Actually Means in the UTAH-400

The UTAH-400 Series 2 does not treat SDI and IP as parallel systems managed by separate hardware. PassThrough Cards, installed directly within the router frame, perform ST 2110 encapsulation and de-encapsulation inside the routing fabric itself. No external gateway hardware sits between the SDI crosspoint and the IP network.

This architecture has a specific consequence: the SDI crosspoint remains fully operational as its own independent routing layer. IP flows pass through the PassThrough cards and are presented to the control system alongside SDI signals, but the SDI crosspoint does not depend on the IP network to function. The two layers share a control interface without sharing a failure domain.

In a conventional hybrid design, gateways live outside the router frame, connected by patch cables or fiber. A gateway failure removes a block of signals from both the SDI and IP layers. In the UTAH-400 Gateway Router, the gateway is the router; if the IP network goes down, the SDI path through that same card continues to route.

How the SDI Crosspoint Stays Live When the IP Network Fails When an ST 2110 network failure occurs, the UTAH-400's SDI failsafe path engages without requiring a control system command. The SDI crosspoint is not dependent on IP network state; it holds whatever crosspoint configuration was last committed and continues passing signal on the SDI layer.

A pure-IP system has one routing layer. When that layer fails, every path fails. The UTAH-400 maintains two routing layers within one chassis, and the SDI layer has no dependency on the health of the IP layer to stay live.

SDI routing architecture in the UTAH-400 scales from 72 72 through 1056 1056, so the SDI failsafe path is not a reduced-capacity emergency mode. It is the full routing matrix, available at full scale, independent of IP network state.

PTP Grandmaster Loss: The Timing Failure Pure-IP Systems Cannot Absorb PTP grandmaster redundancy is standard practice, but redundancy schemes have their own failure conditions: split-brain scenarios where two grandmasters both claim priority, boundary clock misconfiguration that allows PTP traffic to loop, or a failover delay long enough to cause receivers to unlock before the backup grandmaster asserts.

The UTAH-400 manages ST 2110 timing through PTP while simultaneously supporting analog Black Burst references for legacy SDI equipment in the same facility. These timing domains run independently within the system. A PTP failure that disrupts ST 2110 flows does not touch the SDI layer's timing reference; Black Burst-locked SDI signals continue routing normally on the SDI crosspoint.

For facilities in phased migration - where some equipment has moved to ST 2110 and some remains on SDI - this timing independence is the condition that makes coexistence viable, without a separate SDI routing infrastructure running in parallel. The UTAH-400 handles both timing domains within one frame, from one control surface. For operators evaluating the

LINK:	https://utahscientific.com/sdi-failsafe-ip-routing-inside-the-utah-400...
	See more stories from utah

More from Utah Scientfic