Onboard NetQ

The NVIDIA NetQ server must be onboarded before you can use topology validation, auto-correction, and other NetQ telemetry operations in Bridge. Topology discovery must also be complete so Bridge has an accurate view of your physical network before validation or auto-correction can run. This is an optional step if NetQ functionality is not required.

Prerequisites

• Topology discovery — Physical infrastructure topology must be discovered in Bridge.
• NetQ server — A NetQ server must be deployed and reachable from Bridge with valid credentials and a channel webhook URL.

Onboard the NetQ Server

1. In the sidebar, click Telemetry.
2. Click Onboard NetQ.

3. Enable SaaS, then enter the following details:

   Parameter	Value / Source
   NetQ Service IP	NetQ server eth0 IP address (for example, 192.168.200.250)
   NetQ Username	NetQ login username
   NetQ Password	NetQ login password
   Channel Webhook	https://<public-ip-or-domain>:<https-netq-service-external-port>/api/v1/messaging/events (for example, https://worker11.air.nvidia.com:21421/api/v1/messaging/events)

4. Click Onboard NetQ to complete the process.

Verify Onboarding

1. The onboarded NetQ server appears on the Telemetry page.

2. After onboarding, Bridge automatically creates the amcop channel on the NetQ node.

Verify the Notification Channel

1. SSH into the NetQ server from the management node using the default credentials nvidia/nvidia (username/password).

   ssh nvidia@<netq-hostname>

   note

   On first login, you may be prompted to reset the password.

2. Verify the automatic creation of the amcop channel:

   netq show notification channel

Next Steps

• Topology Validation — Verify that infrastructure is discovered correctly by comparing the Bridge-discovered topology with the .dot or .json file used to create the NVIDIA DSX AIR simulation.