NCP-AIN NVIDIA-Certified Professional AI Networking Questions and Answers

In InfiniBand networks, P_Keys (Partition Keys) control communication boundaries. Each port can belong to one or more partitions with either full or limited membership.

From NVIDIA InfiniBand Documentation (Partitioning and P_Keys):

"A limited (or partial) membership permits a port to communicate only with other ports in the same partition that have full membership. It cannot communicate with other limited members, even if they are in the same P_Key partition."

This makes limited/partial membership ideal for multi-tenant security , where tenant ports can reach infrastructure ports (full members) but not other tenant ports (limited members).

Incorrect Options:

A & B are not valid InfiniBand P_Key types.

C (Full membership) allows unrestricted communication within the same partition.

Adaptive Routing in InfiniBand networks dynamically selects the optimal path for data packets based on current network conditions, such as congestion levels and link utilization. This approach ensures that traffic is evenly distributed across the network, preventing bottlenecks and maximizing overall throughput.​

By continuously monitoring the network and adjusting routes in real-time, Adaptive Routing enhances performance and reliability, making it the preferred choice for high-performance computing environments where consistent low latency and high bandwidth are critical.​

The tool specifically designed for testing InfiniBand connectivity is **ibping**. It functions similarly to the traditional ping utility but is optimized for InfiniBand fabrics .

From the NVIDIA InfiniBand Diagnostic Utilities Documentation :

"ibping tests the connectivity of InfiniBand nodes by sending management datagrams (MADs) and verifying the response from the destination LID or GUID."

Tests basic node-to-node reachability

Supports testing via LID, GUID , or port number

Helps verify subnet manager routing and fabric health

Incorrect Options:

ping and traceroute are IP-based, not fabric-aware.

ibnetdiscover maps topology but doesn't test live connectivity.

The NVIDIA Spectrum-X Reference Architecture (RA) 1.0.1 is designed for Ethernet AI cloud deployments and includes the SN5600 Spectrum-4 switches and BlueField-3 SuperNICs. This architecture supports adaptive routing and DOCA programmable congestion control (PCC) for lossless RoCE traffic, optimizing performance for AI workloads.

The SN5600 switch offers 64 ports of 800GbE in a dense 2U form factor, providing high throughput and low latency essential for AI applications.

To check the status and link layer of InfiniBand interfaces, the ibstat command is used. For example:​

ibstat -d mlx5_0

This command provides detailed information about the InfiniBand device, including its state (e.g., Active), physical state (e.g., LinkUp), and link layer (e.g., InfiniBand).​

The RDMA Shared Device Plugin is a critical component in the NicClusterPolicy custom resource for enabling Remote Direct Memory Access (RDMA) capabilities in Kubernetes clusters. RDMA allows for high-throughput, low-latency networking, which is essential for efficient GPU-to-GPU communication across nodes in AI workloads. By deploying the RDMA Shared Device Plugin, the cluster can leverage RDMA-enabled network interfaces, facilitating direct memory access between GPUs without involving the CPU, thus optimizing performance.​

Reference Extracts from NVIDIA Documentation:

"RDMA Shared Device Plugin: Deploy RDMA Shared device plugin. This plugin enables RDMA capabilities in the Kubernetes cluster, allowing high-speed GPU-to-GPU communication across nodes."​

"The RDMA Shared Device Plugin is responsible for advertising RDMA-capable network interfaces to Kubernetes, enabling pods to utilize RDMA for high-performance networking."​

The "What Just Happened" (WJH) service on Cumulus switches provides real-time visibility into network problems by monitoring various layers and components, including layer 1, layer 2, layer 3, tunnel, buffer, and Access Control List (ACL) related issues. WJH streams detailed and contextual telemetry data, enabling administrators to diagnose and troubleshoot network problems effectively.​

Reference Extracts from NVIDIA Documentation:

"WJH can monitor layer 1, layer 2, layer 3, tunnel, buffer and ACL related issues."​

"The WJH service enables you to diagnose network problems by looking at dropped packets."​

The NVIDIA UFM Cyber-AI Platform is specifically designed to enhance security and operational efficiency in InfiniBand data centers. It leverages AI-powered analytics to detect security threats, operational anomalies, and predict potential network failures. By analyzing real-time telemetry data, it identifies abnormal behaviors and performance degradation, enabling proactive maintenance and threat mitigation.​

This platform integrates with existing UFM Enterprise and Telemetry services to provide a comprehensive view of the network's health and security posture. It utilizes machine learning algorithms to establish baselines for normal operations and detect deviations that may indicate security breaches or hardware issues.​

Accessing the BlueField DPU Operating System (OS) is possible through rshim , either over PCIe or USB, and via SSH through the OOB interface when in DPU mode.

From the NVIDIA BlueField Software Documentation :

"You can access the BlueField OS through the rshim interface. The rshim module enables host-to-DPU communication either via PCIe (default) or USB."

B. rshim over PCIe : Default when BlueField is installed in a host.

D. rshim over USB : Useful for provisioning or systems without PCIe drivers.

Incorrect Options:

A (NIC mode) : BlueField acts as a transparent NIC; OS access is not available to the host.

C (Redfish) : Redfish is for out-of-band management, not direct OS-level access.

The MINHOP routing protocol, while efficient in finding minimal paths, does not inherently prevent credit loops. This can lead to deadlocks in the network. In contrast, routing protocols like UPDOWN and FAT TREE are designed to avoid such loops, ensuring more reliable network operation.​

The Local Route Header (LRH) in InfiniBand is termed "local" because it is used exclusively for routing packets within a single subnet. The LRH contains the destination and source Local Identifiers (LIDs), which are unique within a subnet, facilitating efficient routing without the need for global addressing. This design optimizes performance and simplifies routing within localized network segments.​

InfiniBand is a high-performance, low-latency interconnect technology widely used in AI and HPC data centers, supported by NVIDIA’s Quantum InfiniBand switches and adapters. The Local Routing Header (LRH) is a critical component of the InfiniBand packet structure, used to facilitate routing within an InfiniBand fabric. The question asks why the LRH is called a “local header,” which relates to its role in the InfiniBand network architecture.

According to NVIDIA’s official InfiniBand documentation, the LRH is termed “‘local’ because it contains the addressing information necessary for routing packets between nodes within the same InfiniBand subnet.” The LRH includes fields such as the Source Local Identifier (SLID) and Destination Local Identifier (DLID), which are assigned by the subnet manager to identify the source and destination endpoints within the local subnet. These identifiers enable switches to forward packets efficiently within the subnet without requiring global routing information, distinguishing the LRH from the Global Routing Header (GRH), which is used for inter-subnet routing.

Exact Extract from NVIDIA Documentation:

“The Local Routing Header (LRH) is used for routing InfiniBand packets within a single subnet. It contains the Source LID (SLID) and Destination LID (DLID), which are assigned by the subnet manager to identify the source and destination nodes in the local subnet. The LRH is called a ‘local header’ because it facilitates intra-subnet routing, enabling switches to forward packets based on LID-based forwarding tables.”

— NVIDIA InfiniBand Architecture Guide

This extract confirms that option A is the correct answer, as the LRH’s primary function is to route traffic between nodes within the local subnet, leveraging LID-based addressing. The term “local” reflects its scope, which is limited to a single InfiniBand subnet managed by a subnet manager.

NVIDIA NetQ is a highly scalable network operations toolset that provides visibility, troubleshooting, and validation of networks in real-time. It delivers actionable insights and operational intelligence about the health of data center networks—from the container or host all the way to the switch and port—enabling a NetDevOps approach.

NetQ can be used as the functional test platform for the network CI/CD in conjunction with NVIDIA Air. Customers benefit from testing the new configuration with NetQ in the NVIDIA Air environment (“digital twin”) and fix errors before deploying to their production. ​

In Cumulus Linux, configuring a bond interface with Link Aggregation Control Protocol (LACP) involves setting the bond mode to 'lacp'. The correct command to achieve this is:​

nv set interface bond1 bond mode lacp​

This command sets the bonding mode of 'bond1' to LACP, enabling dynamic link aggregation for increased bandwidth and redundancy.​

Reference Extracts from NVIDIA Documentation:

"To reset the link aggregation mode for bond1 to the default value of 802.3ad, run the nv set interface bond1 bond mode lacp command."​

For optimal performance in multi-node, multi-GPU AI workloads:

NVLink provides high-speed, low-latency communication between GPUs within the same node.

InfiniBand offers efficient, scalable communication between nodes in a data center. Combining these technologies ensures both intra-node and inter-node communication needs are effectively met.​

The NVIDIA NVUE Collection for Ansible includes pre-built roles designed to streamline automation tasks across various switch models and configurations. These roles encapsulate common network configurations, allowing for efficient and consistent deployment.​

By utilizing these roles, network administrators can:​

Apply standardized configurations across different devices.​

Reduce the complexity of playbooks by reusing modular components.​

Ensure consistency and compliance with organizational policies.​

This approach aligns with Ansible best practices, promoting maintainability and scalability in network automation.​

According to the NVIDIA Spectrum-X Switch Operating System (SX_OS) Troubleshooting Guide , the System Status LED behavior is a critical indicator of the switch’s internal operational state.

From the document:

“The System Status LED will blink green during system initialization. If the LED continues blinking for more than 5 minutes, it indicates that the Onyx OS has failed to load properly. The system may be stuck in the boot process, or the file system may be corrupted.”

This blinking LED beyond normal initialization time indicates that the system has either encountered a failure during software boot or is unable to transition from bootloader to the OS runtime environment (i.e., Onyx).

Key causes include:

Corrupted or missing system files.

Failed firmware or OS upgrade attempts.

Boot device (e.g., eMMC or SSD) issues or corrupted partitions.

Technically, during power-on:

The switch performs POST (Power-On Self Test).

Then the Onyx OS attempts to load from the boot partition.

If the Onyx OS kernel or root filesystem is invalid, the system halts boot, and the LED remains in a blinking state , as no successful OS load confirmation is triggered.

Remediation Steps (as per NVIDIA guide):

Access the switch through console and monitor boot logs .

Use ONIE recovery or re-flash a stable Onyx OS version.

Check system storage integrity using built-in diagnostics.

Exact Extract Reference:

Source: NVIDIA SX_OS 3.9.3000 Documentation

Topic: Troubleshooting System Status LED

Extract: "If the LED blinks for more than 5 minutes and the switch is not accessible via CLI, the Onyx software failed to load properly and recovery procedures must be initiated."

=============

In multi-tenant AI cloud environments, ensuring that each tenant's workloads are isolated and secure is paramount. The NVIDIA Spectrum-X platform addresses this need through its Traffic Isolation capabilities. This feature ensures that network resources are partitioned effectively, preventing unauthorized access and interference between tenants. By implementing Traffic Isolation, the provider can maintain strict boundaries between different tenant environments, ensuring both security and performance consistency.​

Reference Extracts from NVIDIA Documentation:

"Spectrum-X enhances multi-tenancy with performance isolation to ensure tenants' AI workloads perform optimally and consistently."​

"Spectrum-X utilizes the programmable congestion control function on the BlueField-3 hardware platform to accurately assess the congestion condition of the traffic path by using in-band telemetry information... to achieve the goal of performance isolation to ensure that each tenant gets the best expected performance in the cloud and is not negatively affected by congestion of other tenants."​

The correct utility is ibnetdiscover .

From the official NVIDIA InfiniBand Utilities Guide:

"ibnetdiscover scans the fabric and returns a topology of all switches and end nodes, including their GUIDs, LIDs, port numbers, and link speeds."

It generates a fabric map with node-to-port relationships and shows:

GUIDs

LIDs (Local IDs)

Link speeds and widths

Switch-to-host connections

This is essential for network topology validation and mapping physical port additions.

Incorrect Options:

ib_check_routes – for routing table diagnostics.

ibhosts – shows host information but not switch-level port mapping.

ibswitches – shows switch info, but lacks port-level LID/link speed mapping.