Imagine Communications LRC Plus 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
An Imagine router controller that serves LRC Plus connects to hi as one router Node. hi reads the Sources, Destinations, channels, names, and Crosspoints from the logical database of the router, so you do not enter a matrix size.
|
Configuration |
What hi Sees |
Use When |
|---|---|---|
|
LRC Plus Router |
The logical Sources and Destinations with their channels, names, and Crosspoints. |
hi must route an Imagine routing system through LRC Plus. |
|
LRC Plus Router with Port Containers |
The same Ports, plus one Port Container for each logical Source and Destination. |
Operators must route a logical Source or Destination with all its channels as one item. |
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.
-
Record the LRC Plus controller address and Port.
-
Use RouterMAPPER or the Magellan CCS Navigator to read the logical database.
-
LRC Plus has no authentication in hi. Anyone who can reach the Port can route. Keep the controller on a routing-control network.
Configure LRC Plus Router
Device Configuration
-
Record the LRC Plus Port of the controller. A Magellan SDNO controller serves its whole database over LRC Plus on Port
52117by default, which matches the hi default, and over LRC on Port52116. Confirm that the Port is reachable from hi. -
Confirm that the logical database defines the Sources, Destinations, and channels (levels) that hi must use. LRC Plus addresses the names and IDs of this logical database. Edit it in RouterMAPPER or the Magellan CCS Navigator.
-
To present hi with a subset of the database or with different names and IDs, create a translation on a Magellan SDNO controller:
-
In Database Foundry, select Translator Editor, and then select New.
-
Select the type Level Mapping or Cross Level Regrouping. For Level Mapping, select Map Levels, and then select All Levels one to one mapping so that hi receives every level.
-
On the Destinations and Sources tabs, add the Destinations and Sources for hi, and select Translate. Set Target Protocol Name and the Target Protocol Identifier Index, which is the LRC ID, where required.
-
On the Resources tab, select New Router Port, enter the TCP Port for the translation, and add the Port to the translation. Each Port carries one translation, and a translation database is available only on the router Port assigned to it.
-
Save the translation and publish the database.
-
-
For other controllers, record the LRC Plus endpoint and confirm that it is reachable from hi. Enter that Port in hi; the template default is
52117. -
Send the database configuration to the routing system before you create the Node in hi.
hi Configuration
-
Add the LRC Plus Compatible Router integration (manufacturer Imagine Communications) in Inventory.
-
Enter the controller address and the Port. hi defaults to
52117. -
Create the Node. hi connects and reports its progress while it reads the names, the channels, and the Crosspoints, and then shows
Initialization complete.
Configure LRC Plus Router with Port Containers
Device Configuration
-
Complete the device configuration in Configure LRC Plus Router.
hi Configuration
-
Create the Node as in Configure LRC Plus Router.
-
Open the Node and set Follow changes to
Yesin the Options group. This setting is available only after the Node is created, and its default isNo. -
Wait for hi to synchronize again. hi creates one Port Container for each logical Source and Destination from its channels, and removes Port Containers whose Source or Destination the router no longer reports.
Settings Summary
|
Setting |
Device Side |
hi Side |
|---|---|---|
|
Control Port |
LRC Plus Port
|
Port
|
|
Sources
|
Logical database |
Read from the router |
|
Port Containers |
Logical Sources and Destinations |
Follow changes
|
Common Checks
|
Symptom |
Check |
|---|---|
|
The Node does not connect. |
Confirm the Port that the controller uses for LRC Plus, and confirm that it is reachable from hi. |
|
Synchronization fails, or the levels differ from the router. |
Confirm that hi connects to the router Port that carries the active database or translation, and that this database defines the expected levels. |
|
Names or channels are missing. |
Confirm that the logical database defines them and that the configuration was sent to the routing system. |
|
Some Crosspoints are missing after synchronization. |
hi continues with the Crosspoints that arrive within its wait time. Confirm that the Crosspoints are valid on the router, then synchronize again. |
|
No Port Containers appear. |
Confirm that Follow changes is |
|
The Node synchronizes again without an operator action. |
The router reported a change to its logical database. hi reloads the levels, the names, and the Crosspoints. |
Verify the Configuration
Compare the Source names, the Destination names, the channels, and several Crosspoints with the controller. Route a noncritical Destination from hi, and confirm that the change returns to hi. When Follow changes is Yes, confirm that a Port Container exists for each logical Source and Destination.