From bb62d92c92b2ab56f2fc936b3c34a53cc46513c1 Mon Sep 17 00:00:00 2001 From: Benjamin Barthe Date: Thu, 21 May 2026 14:44:25 +0200 Subject: [PATCH] Update NVLink Management instructions Added instructions to enable the manager after applying certificates and specified the ports for NMX-C and NMX-T. --- .../cumulus-netq-51/NVLink-Management/Register-Services.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/content/cumulus-netq-51/NVLink-Management/Register-Services.md b/content/cumulus-netq-51/NVLink-Management/Register-Services.md index 01592a5983..34e70ed9aa 100644 --- a/content/cumulus-netq-51/NVLink-Management/Register-Services.md +++ b/content/cumulus-netq-51/NVLink-Management/Register-Services.md @@ -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 {{}} 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 {{}} 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 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. {{}}