For AI agents: a documentation index is available at the root level at /llms.txt and /llms-full.txt. Append /llms.txt to any URL for a page-level index, or .md for the markdown version of any page.
NCP Software Reference GuideNVIDIA Inference Reference ArchitectureNVIDIA Requirements for AI Clouds
NCP Software Reference GuideNVIDIA Inference Reference ArchitectureNVIDIA Requirements for AI Clouds
  • NVIDIA Requirements for AI Clouds
    • Introduction
    • Service Delivery SLAs
    • Compute and Network Provisioning
    • Kubernetes As a Service (KaaS) Requirements
    • Security and Identity Management
    • Breakfix Requirements
    • Telemetry Requirements
    • Storage Requirements
    • Network Transport and Fabric Visibility
    • Transport and Networking Requirements
    • Capacity and Fleet Management
    • Appendix
NVIDIANVIDIA
Developer-friendly docs for your API
Privacy Policy | Your Privacy Choices | Terms of Service | Accessibility | Corporate Policies | Product Security | Contact

Copyright © 2026, NVIDIA Corporation.

LogoLogoDSX Documentation
On this page
  • Transport and Networking requirements
  • Non-Conflicting IP Space Allocation for the DGXC Cluster
  • Connection to NVIDIA CorpIT Network
  • Connection to DGXC Storage
  • Cluster Local Internet Access
NVIDIA Requirements for AI Clouds

Transport and Networking Requirements

||View as Markdown|
Previous

Network Transport and Fabric Visibility

Next

Capacity and Fleet Management

Transport and Networking requirements

Non-Conflicting IP Space Allocation for the DGXC Cluster

Purpose:
Ensure DGXC GPU clusters deployed in NCP can access the NVIDIA DGXC/CorpIT network directly via routing exchange. DGXC Cluster IP address must be non-conflicting with existing NVIDIA private IP space.

Req IDTest Details (Legend)Requirement AreaDescription
NET03addNon-Conflicting IP Space Allocation for the DGXC ClusterBring Your Own IP (BYOIP): NCP shall support the ability for NVIDIA to bring and allocate its own IP private address space for DGXC GPU clusters. Stable IP: NCP shall provide a possibility to create static IP allocations that persist across instance restarts and re-creations. That includes floating IP allocations. DoD space: NCP shall support allocation and use of the 7.0.0.0/8 IPv4 address space for DGXC GPU cluster deployments. This IP space shall be considered equivalent to RFC1918 addresses Routing Support: NCP must support advertising and routing of BYOIP prefixes within the NCP environment and across interconnects (Private Cloud Interconnect, IPSec, etc.)

Connection to NVIDIA CorpIT Network

Purpose:
Provide connection from DGXC GPU clusters within NCP to NVIDIA CorpIT for internal Command & Control and admin access.

Req IDTest Details (Legend)Requirement AreaDescription
NET04INFOConnection to NVIDIA CorpIT NetworkBandwidth: Low bandwidth (Up to 10Gbps). Transport: Private Cloud interconnect + VIF + BGP (preferred for better performance/security). DGXC will establish connectivity to NCP through a mutually agreed Point of Presence (POP) using Private Cloud Interconnect, functionally equivalent to AWS Direct Connect, GCP Dedicated Interconnect, Azure ExpressRoute, and OCI FastConnect. Connectivity will be provisioned with a Virtual Interface (VIF) and routing established via BGP. The interconnect will be used to exchange private IP space (RFC1918, as well as 7.0.0.0/8) between DGXC and NCP.

Corporate network connectivity diagram

Figure: Private Cloud interconnect + VIF + BGP for CorpIT access

Connection to DGXC Storage

Purpose:
Enable high-bandwidth, end to end MACsec-encrypted (fail-closed) access between the DGXC GPU clusters within NCP and NVIDIA DGXC on-premises object storage for large-scale data movement.

Req IDTest Details (Legend)Requirement AreaDescription
NET05INFOConnection to DGXC StorageTransport: Private Cloud interconnect + VIF + BGP (preferred for better performance/security). DGXC will establish connectivity to NCP through a mutually agreed Point of Presence (POP) using Private Cloud Interconnect, functionally equivalent to AWS Direct Connect, GCP Dedicated Interconnect, Azure ExpressRoute, and OCI FastConnect. Connectivity will be provisioned with a Virtual Interface (VIF) and routing established via BGP. The interconnect will be used to exchange private IP space (RFC1918, as well as 7.0.0.0/8) between DGXC and NCP.

Storage connectivity diagram

Cluster Local Internet Access

Purpose:
Provide general Internet access from DGXC GPU clusters within NCP to Internet, including NVIDIA DGXC hosted services on third-party public cloud services.

Req IDTest Details (Legend)Requirement AreaDescription
NET06INFOCluster Local Internet AccessCluster Internet access: Egress NAT IPs should be a static pool dedicated to only Nvidia Cluster/Tenancy/VPC. These persistent IP addresses must be used exclusively for DGXC traffic and shall not be shared with or carry traffic from other NCP tenants. Availability: Must support redundant upstream paths to ensure connectivity under failure.

Internet access diagram
Figure: Public internet for DGXC hosted Services access