DGX OS Connectivity Requirements
In a typical operation, DGX OS runs services to support typical usage of the DGX system.
Some of these services require network communication. The table below describes the port, protocol, direction, and communication purpose for the services. DGX administrators should consider their site-specific access needs and allow or disallow communication with the services as necessary.
In-Band Management, Storage, and Compute Networks
The following table provides information about the in-band management, storage, and compute networks.
Port (Protocol) |
Direction |
Use |
|---|---|---|
22 (TCP) |
Inbound |
SSH |
53 (UDP) |
Outbound |
DNS |
80 (TCP) |
Outbound |
HTTP, package updates |
111 (TCP) |
Inbound/Outbound |
RPCBIND, required by NFS |
273 (TCP) |
NVIDIA System Management Management |
|
443 (TCP) |
Outbound |
For internet (HTTP/HTTPS) connection to NVIDIA GPU Cloud. If port 443 is proxied through a corporate firewall, then WebSocket protocol traffic must be supported |
1883 (TCP) |
Mosquitto Database (used by NVIDIA System Management) |
Out-of-Band Management
The following table provides information about out-of-band management for your DGX system.
Port (Protocol) |
Direction |
Use |
|---|---|---|
443 (TCP) |
Inbound |
For BMC web services, remote console services, and CD-media service. If port 443 is proxied through a corporate firewall, then WebSocket protocol traffic must be supported. |
623 (UDP) |
Inbound |
IPMI |