Networking Minerva User Guide

Platform Installation

This guide covers deploying the NVIDIA Minerva platform in either the Unified or Hybrid deployment model.

Unified Installation

In a unified deployment, the NVIDIA Minerva stack runs both the platform and collector roles in a single installation. The following ports must be open from unified installations:

Port

Protocol

Purpose

443

TCP

UI and API (HTTPS)

80

TCP

UI and API (HTTP)

4317

TCP

OTLP gRPC (device telemetry)

4318

TCP

OTLP HTTP (device telemetry)

4319

TCP

OTLP gRPC (NMX-T; NVLink ingress)

9091

TCP

Prometheus

57402

TCP

gNMI dial-out (WJH)

514

UDP

Syslog

Swarm ports (2377, 7946, 4789) are bound but have no peers — not firewall-relevant on standalone.

Hybrid Installation

In a hybrid deployment, the NVIDIA Minerva Platform Stack and Collector Stack are deployed separately. The Platform Stack can run either on-premises or in the cloud, while the Collector Stack typically runs on-premises. The Collector Stack sends telemetry data to the Platform Stack over a local network or the internet. Each component is installed independently, with the installation type selected via interactive prompt.

Components:

  • Platform Stack: infra, tsservice, backend, and ui services, deployed on on-premises hosts or in the cloud

  • Collector Stack: collectors and ingestion services deployed on on-premises hosts, configured to reach the Platform Stack

The following ports must be open from the collector to the platform for hybrid installations:

Inbound to Collector nodes (from devices)

Port

Protocol

Purpose

4317

TCP

OTLP gRPC (device telemetry)

4318

TCP

OTLP HTTP (device telemetry)

4319

TCP

OTLP gRPC (NMX-T; NVLink ingress)

9091

TCP

Prometheus

57402

TCP

gNMI dial-out (WJH)

514

UDP

Syslog

Inbound to Platform node (from collectors)

Port

Protocol

Purpose

443

TCP

UI, API, management (HTTPS)

14317

TCP

Data-plane metrics

24317

TCP

Collector health metrics/logs

Next steps: Docker Swarm - Platform

Last updated: