Bind other address than management

[cbernard32]

Hello,

I have a setup with a mellanox switch and docker container.
When a start the container, the registry annonce itself with the management IP of the mellanox.
But in the mellanox the management interface is in a separate VRF which is not reachable from others interfaces.
So the devices cannot register because they try to contact the management IP.
How can i change this behaviour ?
The container is reachable from other IP of the mellanox.

Thanks.

[rhastie]

Hi,

Are you running the NMOS registry on the switch? By default the Onyx NOS, operates two separate VRFs. One for Mgmt and one for other interfaces. It appears you are using the Mgmt VRF currently for Docker.

Please sned the output of the following commands and we'll try and help...

show docker
show vrf

[cbernard32]

Hello,

Yes, the registry is running on the mellanox. Yes, two VRF : default and mgmt.
Docker is running on the default vrf, not on the mgmt.
By default, the container is announcing the "host_address" for the registration, which is set to the management IP, so it's not reachable from docker and for the clients, because it's on the other VRF...
I don't have acces to the mellanox for the moment, but tomorrow i'll send you the output of requested commands.

Thanks

[cbernard32]

Hello,

Here are the output:

xxxx [standalone: master] # show docker
Dockers state: enabled
Docker hub VRF: default
Docker log-level: warn

xxxx [standalone: master] # show vrf

VRF Info:
Name: mgmt
RD: -
Description: -
IP routing state: Disabled
IPv6 routing state: Disabled
IP multicast routing state: Disabled
Protocols:
Interfaces:

VRF Info:
Name: default
RD: NA
Description: NA
IP routing state: Disabled
IPv6 routing state: Disabled
IP multicast routing state: Disabled
Protocols:
Interfaces: Eth1/18, Eth1/1, vlan4000

And if i go to the container and exec manualy the following command : /home/nmos-cpp-registry /home/registry.json
root@xxxx:/home# /home/nmos-cpp-registry /home/registry.json
2025-06-18 21:16:59.576: info: 140625562175296: Starting nmos-cpp registry
2025-06-18 21:16:59.579: info: 140625562175296: Process ID: 312
2025-06-18 21:16:59.579: info: 140625562175296: Build settings: cpprestsdk/2.10.19 (listener=asio; client=asio); WebSocket++/0.8.2; Boost 1.83.0; OpenSSL 3.2.1 30 Jan 2024
2025-06-18 21:16:59.579: info: 140625562175296: Initial settings: {"admin_port":8010,"authorization_redirect_port":8010,"host_address":"X.X.X.X","host_addresses":["X.X.X.X","Y.Y.Y.Y","Z.Z.Z.Z],"http_port":8010,"http_trace":false,"jwks_uri_port":8010,"label":"switch-2065f2-registry","logging_level":0,"logging_port":8010,"mdns_port":8010,"node_port":8010,"pri":10,"query_port":8010,"query_ws_port":8011,"registration_expiry_interval":12,"registration_port":8010,"schemas_port":8010,"seed_id":"15145ace-4f13-4a43-8584-15e554768711","settings_port":8010,"system_port":8010}
2025-06-18 21:16:59.579: info: 140625562175296: Configuring nmos-cpp registry with its primary Node API at: http://X.X.X.X:8010/x-nmos/node/v1.3
2025-06-18 21:16:59.579: info: 140625562175296: Configuring nmos-cpp registry with its primary Registration API at: http://X.X.X.X:8010/x-nmos/registration/v1.3
2025-06-18 21:16:59.579: info: 140625562175296: Configuring nmos-cpp registry with its primary Query API at: http://X.X.X.X:8010/x-nmos/query/v1.3

X.X.X.X is the management IP, Y.Y.Y.Y and Z.Z.Z.Z are interfaces in the default VRF.

Hope this help.