hi human interface®
hi human interface®
English
Breadcrumbs

An External Control System Cannot Use the Northbound Node

An External Control System Cannot Use the Northbound Node

Diagnosis

Scenario

An external control system connects to a hi Northbound Node to read labels and route Ports.

Observed Behavior

The external system cannot connect, connects but shows no expected Sources or Destinations, or sends a route that has no effect in hi.

Possible Causes

A connection can fail because of:

  • The listener port.

  • A firewall.

  • Missing hiDock entitlement or hiLink session capacity.

When the connection works but routing does not, possible causes are:

  • Matrix or Level values that differ from the external system's matrix definition.

  • Ports that are not assigned in Matrix Assignment.

Prerequisites

  • Northbound Node checks require Node admin. Network checks require the network administrator. External-system checks require that system's administrator.

  • Agree on a test Destination that is safe to switch.

Resolution

  1. Node admin: Open the Northbound Node and record its listener port, Matrix, and Level.

  2. If the external system cannot connect, ask the network administrator to confirm that the network permits the listener port between the external system and the hi server.

  3. Confirm that the hiDock entitlement and hiLink capacity are available. See the Northbound Node requirements.

  4. If the system connects but Ports are missing or routes have no effect, compare Matrix and Level with the external matrix definition. Confirm that the required Ports are assigned in Matrix Assignment and that no reserved slot is assigned. See Reserved Source Slots.

  5. Save any corrected settings and wait for the Node to initialize. If the Node does not reach an operational state, follow A Node Remains Offline or Unreachable.

Verify the Result

From the external system, query the matrix labels and confirm that they match hi. Route the agreed test Destination and confirm that the change appears in both hi and the external system.

See Northbound Interface.

If the issue persists after these checks, contact Riedel Customer Success. Include the observations from this page, the Serial Number or Installation ID, the hi version, and a Backup and log export. See Customer Support.