Generic Pro-Bel SW-P-02 Compatible Router

Generic Pro-Bel SW-P-02 Compatible Router

Minimum hi Version: v2.6.1

Overview

This integration provides Crosspoint control and Tally monitoring for routing systems that implement Pro-Bel SW-P-02.

Network Requirements

• Allow outbound TCP from hi to the router controller on Port 2001 by default.

• The control Port is configurable and may differ from the template default.

• No callback or inbound connection to hi is used.

• Keep the plaintext connection on a trusted management network.

Standards Conformance

Operator Workflow

• UI Surface in hi: Routing Matrix and Inventory

• Layers Controlled: One matrix, with the configured signal type

• Routing Semantics: hi exposes the configured Sources, Destinations, and Crosspoints.

• Notes for Operators Familiar with the Vendor's Own Tooling: Use vendor tooling for labels, locks, protection, salvos, and engineering configuration.

Connection Details

Required Configuration

Device-Side Setup

Follow Generic Pro-Bel SW-P-02 Compatible Router Integration Configuration for the device-side and hi-side configuration steps.

Supported Features

Device Coverage

Tested With identifies devices that have been tested with hi. Potentially Compatible (Not Yet Verified) identifies compatibility candidates that use the same protocol or connection method. Device-specific configuration, firmware, and feature support can affect results.

Tested With

• Grass Valley Sirius Series

Potentially Compatible (Not Yet Verified)

• Other routing systems that implement Pro-Bel SW-P-02 and support the routing and state messages listed above.

Known Limitations

• hi addresses up to 1,024 Sources and 1,024 Destinations.

• No encryption or authentication at the protocol level. Keep the control connection on a trusted management network.

• Router controllers differ in which SW-P-02 messages they implement. Confirm interrogate and connect behavior on the router before commissioning.

• Snell SW-P-02 over IP controllers, such as Nucleus 2450, the SC12 and SC13 controllers in Sirius and Halo frames, and Babel Fish, accept up to eight concurrent TCP clients.

• On Snell controllers, protocol Destinations 896 to 1023, which are hi Destinations 897 to 1024, are monitor rows, not main router Destinations. Set Output Count to 896 or less unless monitor rows are intended.

• hi does not read the matrix size from the router. It creates the Sources and Destinations from Input Count and Output Count, and it interrogates each Destination when it connects. Set both counts at creation to match the router.

• hi numbers Sources and Destinations from 1, and it subtracts one when it builds a protocol message. Compare the numbers with that offset when you check routes against the router configuration.

What's Not Supported

• Source and Destination label management; SW-P-02 does not define these operations.

• Lock, protection, and salvo operations.

• Engineering-level configuration (level naming, port labels, redundancy setup) - use the vendor's native router-control tool.

• Firmware updates - use the vendor's native update utility.

• Hardware diagnostics and SFP-level health - surfaced by the device's own management plane, not this integration.

• Level selection. SW-P-02 messages carry no level.

• Extended SW-P-02 commands, such as EXTENDED CONNECT. hi sends only CONNECT and INTERROGATE messages.

• The UDP multicast notifications of Snell SW-P-02 over IP controllers. hi uses the TCP connection only.

Trademarks