Nevion MRP Compatible Router Integration Configuration

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.

Configuration Overview

A Nevion router connects to hi through the Modular Routing Protocol (MRP). MRP controls logical levels, not raw chassis ports. One physical router can be split into several levels, and hi exposes the levels that the router reports. hi reads the matrix size from the router, so the Node needs no input or output counts.

Configuration	What hi Sees	Use When
MRP Routing	The levels, Sources, Destinations, and Crosspoints that the router reports, with the privileges of the configured user. hi can take routes and clear Destinations, to the extent that the user allows. hi does not lock or protect Destinations.	hi must route a Nevion router.

Caution

MRP sends the login over a plaintext TCP connection. Use a trusted management network, and create a dedicated user for hi.

Before You Begin

Use Node admin and open Inventory > Nodes. See Manage Nodes.
Confirm the license and minimum hi version in Required Configuration.
Use Multicon, or the vendor's router configuration tool, to read the level list and to create the user.
Record the MRP endpoint address and Port, and the user name and password that hi uses.
Confirm the network access in Network Requirements. The default MRP port is 4381.

Configure MRP Routing

Device Configuration

Confirm that the router or Multicon server accepts MRP connections on TCP Port 4381.
In Nevion Configurator, create a user for hi. Give the user an access level that can take routes on every level that hi controls. A new MRP connection starts with a default user, and hi logs in with the configured user to obtain its privileges.
Record the level list. MRP numbers inputs and outputs from 0 within each level. Only a Multicon system partitions a router into several levels. Without Multicon, one level covers the whole physical router.
Confirm that the hi server can reach the Port. hi uses MRP over TCP only and does not support serial MRP links.

hi Configuration

Add the Nevion MPR Compatible Router integration in Inventory. hi labels the MRP integration with that name.
Enter the router address and the Port.
Create the Node.
Open the Node, and enter User and Password in the Login group. hi reconnects with the new login. The Node does not initialize if the login fails.
Wait for hi to read the levels, the names, and the Crosspoints.

Settings Summary

Setting	Device Side	hi Side
Control Port	MRP over TCP default `4381`	Port
User	User with routing privileges on the controlled levels	User and Password in the Login group
Levels	Level list of the router	Levels that the router reports
Numbering	Inputs and outputs from `0` within a level	Ports from `1`. MRP input or output `0` is Port `1` in hi.

Common Checks

Symptom	Check
The Node does not connect.	Confirm the address and Port, and confirm that the router accepts MRP connections from the hi server.
The Node connects and the login fails.	Confirm the user name and password in the router.
A level is missing.	Confirm that the level exists on the router. hi shows only the levels that the router reports.
A route fails.	The Destination can be locked, protected by another user, or outside the privileges of the hi user for that level.
A disconnect does not clear the Destination.	hi can clear a Destination only on levels where the router supports disconnect.

Verify the Configuration

Compare the levels, the names, and several Crosspoints with Multicon. Route a noncritical Destination from hi, and confirm that the router shows the new Crosspoint.