Skip to content

Update NVLink Management instructions #3239

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
rachel-netq merged 1 commit into from
May 21, 2026
+2 −2
Merged

Update NVLink Management instructions #3239

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
4 changes: 2 additions & 2 deletions content/cumulus-netq-51/NVLink-Management/Register-Services.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -35,11 +35,11 @@ Files created:
Done.
```

3. Copy the `example-ca.crt` and `example-tls.p12` files to the switch tray. Replace the filenames with the actual names of the files. Use the {{<exlink url="https://docs.nvidia.com/networking/display/nvidianvosusermanualfornvlinkswitchesv25022225/cluster+manager+commands" text="NVOS cluster manager commands">}} to apply the certificates to both NMX-C and NMX-T.
3. Copy the `example-ca.crt` and `example-tls.p12` files to the switch tray. Replace the filenames with the actual names of the files. Use the {{<exlink url="https://docs.nvidia.com/networking/display/nvidianvosusermanualfornvlinkswitchesv25022225/cluster+manager+commands" text="NVOS cluster manager commands">}} to apply the certificates to both NMX-C and NMX-T. Applying the certificates is not enough, be sure to enable the manager using `nv action update cluster apps <app-name> manager` to get the port open for both apps.

## Register Services

Register the services by making a POST request to the `v1/services` endpoint.
Register the services by making a POST request to the `v1/services` endpoint. NMX-c aka the controller is listening on port 9370 while NMX-t aka TELEMETRY is listening on port 9351.

{{<tabs "TabID42" >}}

Expand Down
Loading