Riedel MediorNet IP - FusioN / MuoN 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

hi discovers FusioN and MuoN devices through NMOS. The REST parameter surface is an addition that is off by default.

Configuration	What hi Sees	Use When
NMOS Routing	The NMOS Senders and Receivers of the device in the NMOS routing workflow.	hi must only route the device.
NMOS Routing with Parameter Control	The NMOS resources, and the REST parameter tree of the device in Parameter Control.	hi must also read or change device parameters.

Before You Begin

Use Node admin and open Inventory > Nodes. See Manage Nodes.
Confirm the license and minimum hi version, and the settings, in Required Configuration.
Configure the NMOS Core Integration and its registry first.
Get the device management address, and access to Riedel MNSet or to the device REST API.
Confirm the network access in Network Requirements.

Configure NMOS Routing

Device Configuration

Configure the NMOS registry in Riedel MNSet, or through the device REST API. The REST API resource is /emsfp/node/v1/self/diag/nmos on firmware with NMOS support. GET reads the NMOS settings and registration state, and PUT writes the settings.

Choose how the device finds the registry with registry_mode:
- auto: the device queries DNS for the registry service. It uses DNS-SD by default. Set mdns_mode to true to use mDNS instead.
- manual: the device connects to registry_address, or to registry_address_2 as the secondary registry. Enter each address as IP address and Port.
For auto with unicast DNS-SD, confirm the DNS servers and domain_name. The device uses the DNS servers from DHCP unless manual_dns_server_address through manual_dns_server_address_4 are set.
Keep devices_visible at true for each device channel that must appear in the registry.
Read /emsfp/node/v1/self/diag/nmos again. status reads connected when the device is fully registered, and current_registry shows the registry in use.

hi Configuration

Confirm that the NMOS Core Integration discovers the device. hi creates a Node with the MediorNet IP – FusioN / MuoN template when the device reports a group hint tag and a Riedel interface MAC address in NMOS.
Open the Node. In the Settings group, keep Manage Master Enable, Manage Primary RTP Enable, and Manage Secondary RTP Enable at Yes when hi must manage these states during NMOS routing. Set a setting to No when another system controls that state. These settings are available only after the Node is created, and only while Automatic RTP and Master Enable Management is Yes on the NMOS Core Integration.

Configure NMOS Routing with Parameter Control

Device Configuration

Confirm that the hi server can reach the device REST API at /emsfp/node/v1 on HTTP Port 80. The device serves the API without authentication.

hi Configuration

Complete the NMOS routing configuration.
Open the Node and turn on the Parameter Control capability. It is off by default.
Confirm the device address and the Port of the capability. The default Port is 80.
Save the Node. hi reads the REST parameter tree and shows it in Parameter Control.

Settings Summary

Setting	Device Side	hi Side
NMOS registry	`registry_mode` and `registry_address` in `manual` mode set in MNSet or through `/self/diag/nmos`	Registry of the NMOS Core Integration
REST address	Device management address	Address of the Parameter Control capability
REST Port	HTTP Port `80`	Port default `80`

Common Checks

Symptom	Check
The device does not appear in hi.	Read `/emsfp/node/v1/self/diag/nmos`. `discovering` means the device has not found a valid registry; check `registry_mode`, the registry address, and the DNS settings. `connected` with an unexpected `current_registry` means the device registered with a different registry.
The device appears as a generic NMOS Node.	Confirm that the device reports a group hint tag and its Riedel interface MAC address in NMOS.
No parameters appear in Parameter Control.	Confirm that the Parameter Control capability is on, and that Port `80` on the device is reachable from hi.
The Manage settings are missing on the Node.	Confirm that Automatic RTP and Master Enable Management is `Yes` on the NMOS Core Integration.
A parameter change from hi has no effect.	Confirm that hi marks the parameter writable and that the device accepts the requested value. REST Parameter Values lists examples of the available controls.

Verify the Configuration

Confirm that the Senders and Receivers of the device appear in the NMOS routing workflow, and route a noncritical Receiver. When Parameter Control is on, read several values and compare them with the Riedel FusioN web interface. Then change a noncritical writable value, such as a flow label, and confirm the change in the web interface.

NMOS Core Integration