Imagine Communications Magellan SDN Orchestrator (SDNO) 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

Magellan SDNO uses two control surfaces. The SDNO REST API supplies Source, Destination, level, and channel metadata. LRC Plus performs the Crosspoint routing. Configure both endpoints for one Node.

Configuration	What hi Sees	Use When
SDNO with LRC Plus	SDNO names and level and channel assignments, with LRC Plus Crosspoint state and routing.	hi must route an Imagine system that an SDNO orchestrates.

Caution

The SDNO REST interface returns the published database. Edits that are not published do not appear in hi.

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 in Network Requirements. The default Ports are 52117 for LRC Plus and 80 for the SDNO REST API.

Configure SDNO with LRC Plus

Device Configuration

Confirm that the SDNO REST interface is reachable on Port 80. SDNO 2.9.8 and later serve the REST interface on Port 80.
Record the LRC Plus Port. SDNO serves its whole database over LRC Plus on Port 52117 by default, which matches the hi default, and over LRC on Port 52116. A translation database from the SDNO Translator Editor is available only on the router Port assigned to that translation.
In SDNO, publish the active database before you commission hi.
Use an SDNO version with REST API 1.5 or later. hi reads the levels of the active database through an endpoint that is available from API 1.5. API 1.6 adds the filter for generated breakaway Sources.

hi Configuration

Add the Magellan SDN Orchestrator (SDNO) integration in Inventory.
Enter the LRC Plus address and Port, then the SDNO REST address and Port. If the SDNO REST address stays at the default address, hi does not use SDNO. Allow outbound TCP from hi to the LRC Plus endpoint and outbound HTTP from hi to the SDNO REST endpoint. No callback to hi is used.
Create the Node.
To update Port Containers automatically when the device changes, open the Node and set Follow changes to Yes in the Options group.

Settings Summary

Setting	Device Side	hi Side
Router control	LRC Plus endpoint default Port `52117`	LRC Plus Port
Metadata	SDNO REST endpoint default Port `80`	SDNO REST Port
Database	Published SDNO database	Names and level assignments in hi

Common Checks

Symptom	Check
The Node shows Device not available.	Confirm the SDNO REST address and Port, and confirm that the database is published. If SDNO is configured and unreachable, the Node does not initialize.
Names load and routing fails.	Confirm that the LRC Plus Port is reachable.

Verify the Configuration

Confirm that routing state loads through LRC Plus and that SDNO metadata is available. Compare several Crosspoints, then test a route on a noncritical Destination. If synchronization fails, identify the unavailable surface and verify its endpoint and the active database.