A Route Does Not Appear on the Destination

Diagnosis

Scenario

An operator applies a routing action from the Control Panel.

Observed Behavior

The Destination does not display the intended connected Source, or the Control Panel reports a routing error.

Possible Causes

The route can be blocked or superseded by a Destination lock, authorization, incompatible Ports, an unavailable integration path, or configured automation. The symptom alone does not establish which condition applies.

Prerequisites

Operator checks require Control Panel access and Tag access to both Ports.
Node, Topology, Rule, or external-control changes require the administrator responsible for that configuration.
Keep the displayed error and current Source and Destination names available. Do not repeat a live route until its impact is understood.

Resolution

Operator: Record the Source, Destination, Preset, Take Mode, and complete displayed error.
If the connection is queued in Take mode, follow A Selected Source Has Not Been Routed.
If the Destination is locked, follow A Destination Lock Prevents Routing. If a Port is absent, follow An Expected Port Is Missing.
If both Ports are visible, confirm that they are compatible in the active Preset. Review the relevant Node states and use Inspect a Signal Path to inspect the configured path.
If a Node is offline, follow A Node Remains Offline or Unreachable.
If the route applies and then changes again, ask the responsible administrator to review Rules or external control systems that can change the same Destination.
Administrator: Review a remaining path or configuration mismatch using the relevant task and integration pages. Repeat the route only after the conflicting condition is understood and the live change can proceed.

Displayed Compatibility Warnings

These warnings identify a mismatch in the selected Ports. Review the selection before attempting another live route. They do not establish an integration or infrastructure failure.

Displayed warning	What to check
Baseband and IP ports cannot be routed together	Check the media of the selected Ports and select a compatible Source and Destination for this routing action.
Please select ports with the same Format Type. followed by the Source and Destination types	Compare the displayed Format Types and select matching Ports. Matching Essence Layers alone does not resolve a Format Type mismatch.
Please select baseband ports from the same node.	Check which configured Node owns each selected Baseband Port. Ask the responsible administrator to review a required path between different Nodes.
Please select IP ports from different devices	Review the devices that own the selected Ports and the configured routing path. This warning applies when the current configuration does not allow same-device routing; it does not mean that all same-device IP routing is unsupported.

Verify the Result

Confirm that the Destination displays the intended Source and that the downstream monitored result matches the intended Signal Path.

See Make Your First Route and Control Panel.

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.