Nevion MRP Compatible Router

Driver Maturity

Production

Recommended for normal production use.

Caution

Compatibility Note: This information is a general guide and may be incomplete, may not match a specific project implementation, and is subject to change as supported products and versions evolve. Confirm the exact implementation and requirements for each project with Riedel and the relevant equipment vendor, then validate the required functions end to end in the target environment before deployment.

Minimum hi Version: v2.3.0

Overview

The Nevion^® MRP Compatible Router integration uses the Modular Routing Protocol (MRP) interface for level discovery, labels, routing, and state. Nevion uses MRP to control its Modular, Sublime, and Compact routers. The protocol is ASCII-based. The connection requires a device login.

Network Requirements

Allow outbound TCP from hi to the MRP endpoint on Port 4381 by default.
No callback or inbound connection to hi is used.
MRP sends the configured login over the plaintext TCP connection. Use a trusted management network.

Standards Conformance

Standard	Conformance	Notes
Nevion Modular Routing Protocol (MRP)	Level Port Crosspoint login and keepalive operations	Vendor protocol no public-standards conformance claimed

Operator Workflow

UI Surface in hi: Routing Matrix and Inventory
Layers Controlled: Levels reported by the MRP endpoint
Routing Semantics: hi exposes the Sources, Destinations, and Crosspoints reported for each level.
Notes for Operators Familiar with the Vendor's Own Tooling: Use vendor tooling for salvos, protection, engineering configuration, and firmware management.

Connection Details

Property	Value
Protocol	Nevion MRP
Transport	TCP
Default Port	4381
Authentication	Username and password configured in hi and sent through the MRP login exchange
Encryption in Transit	The integration does not add transport encryption to the MRP connection
Connection Model	Persistent TCP with ping keep-alive
Required License	hiBase
Traffic Flow	Outbound from hi

Required Configuration

Parameter	Description	Default
Host / IP Address	IP address of the Nevion router	-
Port	TCP port for MRP communication	4381
User	Login user for MRP authentication	admin
Password	Login password for MRP authentication	password
Read labels on startup	Read the names from the router when the Node starts	Yes

Device-Side Setup

Follow Nevion MRP Compatible Router Integration Configuration for the device-side and hi-side configuration steps.

Supported Features

Feature	Access	Exposed Operation and Scope
Level Input and Output Inventory	Read-only	Enumerate routing levels/matrices and read inputs/outputs, labels, and properties.
Crosspoint	Read/write	Execute supported route changes and query current state.
API Login	Write-only session action	Authenticate using the configured credentials.
TCP Keep-alive	Automatic connection maintenance	Maintain the TCP session; this is not an operator control action.

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.

This integration supports the Nevion VikinX range.

Tested With

Nevion VikinX
Nevion VikinX Sublime
Nevion VideoIPath

Supported Product Range

The following VikinX routers use Multicon as their system controller, which exposes the MRP interface. MRP controls logical routing levels rather than chassis surfaces.

Nevion VikinX Modular

Potentially Compatible (Not Yet Verified)

Nevion Flashlink frames exposed through Multicon, where the system exposes the MRP interface.
Other Nevion routing devices that implement the Nevion MRP control surface.

Known Limitations

Credential requirements are defined by the configured Nevion MRP endpoint.
MRP controls logical levels. Levels, virtual tables, salvos, and parameter groups that exist depend on the router or Multicon configuration, and hi exposes the Levels the endpoint reports.
Crosspoint changes, locks, and protects depend on the privileges of the MRP user. A route change fails when the destination is locked, which blocks every user including the one that locked it, when another user has protected it, or when the configured user lacks the required privilege. Only the owner of a lock or protect, a user with a higher access level, or an administrator can release it.
Nevion routers are partitioned into several levels only when Multicon is used. A router without Multicon reports one level that covers the whole router.
hi can clear a Destination (disconnect) only on levels where the router supports disconnect.
Validate levels, labels, login, and routing on the installed router firmware during commissioning.

What's Not Supported

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.
Locking and protecting Destinations, salvos, virtual tables, and alarms. MRP provides them, and hi sends only take and disconnect commands.

Trademarks

Note

Nevion is a trademark of Nevion AS.

RIEDEL Communications is not affiliated with, endorsed by, or officially partnered with Nevion unless explicitly stated.