Northbound Node 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
The Northbound Node presents hi Sources and Destinations to one external control system as a Pro-Bel SW-P-08 matrix. Configure the Node in hi and then configure the external system to connect to it.
Create one Northbound Node for each external system.
Caution
The Northbound Node needs the hiDock license, and each active Northbound session counts against hiLink. Confirm both before you commission the interface.
Before You Begin
-
Use Node admin and open Inventory > Nodes. See Manage Nodes.
-
Confirm the license and minimum hi version in Required Configuration.
-
Confirm the network access and the listener port in Network Requirements.
-
Know which Sources and Destinations the external system may control. Only Ports that have Tags assigned appear in the Port Picker.
-
Know the Matrix and Level values that the external system uses.
Configure Northbound Node
Use this configuration to let an external control system route mapped hi Sources and Destinations.
Device Configuration
-
In the external control system, define a Pro-Bel SW-P-08 matrix that matches the Matrix and Level values and the assigned slots of the Northbound Node. Use the vendor documentation of the external system.
-
Enter the address of the hi server and the listener port of the Northbound Node as the target of the SW-P-08 connection.
hi Configuration
-
Create the Northbound Node in Inventory. Create one Node for each external system.
-
Set the listener port of the Node, from
31000to31999. Set Matrix and Level in the SWP08 Protocol Properties. The values are zero-based, from0to15. -
In the Labels group, select the hi Label that hi reports for each label length of 4, 8, 12, and 16 characters.
-
Optional: turn Force Extended Message On Broadcast on to always broadcast Crosspoint changes with extended messages, and set Force send crosspoint changed message as the external system requires.
-
Open Matrix Assignment, append the input and output slots, and assign Ports and Port Containers to them. Do not assign the reserved slots. See Reserved Source Slots.
-
Save the Node and wait for it to initialize.
Settings Summary
|
Setting |
Device Side |
hi Side |
|---|---|---|
|
Address and port |
The address of the hi server and the listener port |
The listener port of the Node
|
|
Matrix |
The matrix number
|
Matrix |
|
Level |
The level number
|
Level |
|
Matrix size |
The inputs and outputs of the defined matrix |
The assigned input and output slots |
Common Checks
|
Symptom |
Check |
|---|---|
|
The external system cannot connect. |
Confirm the listener port, and confirm that the network and firewall allow it. |
|
An external route has no effect. |
Confirm that the Source and the Destination are assigned in Matrix Assignment. hi exposes only assigned Ports. |
Verify the Configuration
Connect the external system and query the labels of the matrix. Confirm that they match the labels that hi reports for the selected label lengths. Then issue a Crosspoint Connect command for a mapped Source and Destination, and confirm that the route and the update appear in hi and in the external system. Use a test Destination that is safe to switch.
Related Pages
-
Northbound Interface for label mapping, reserved slots, and supported messages.