Home / artificial-intelligence-machine-learning / NVIDIA-Certified Professional: AI Networking (NCP-AIN) / Cheat Sheet
NVIDIA-Certified Professional: AI Networking (NCP-AIN)

NCP-AIN Cheat Sheet

NCP-AIN Tests Lossless AI Fabrics End to End — Not Generic Data Center Switching

A professional exam for engineers who run Spectrum-X Ethernet and InfiniBand fabrics for GPU clusters. Stop thinking in VLANs and ECMP; think in rails, subnet managers, congestion control and which tool sees which layer.

Check Your Readiness →
Among the harder certs
Avg: Not published by NVIDIA
Pass: 750 / 1000
Most candidates understand NVIDIA-Certified Professional: AI Networking (NCP-AIN) concepts — and still fail. This exam tests how you apply knowledge under pressure.

NCP-AIN Domain Map (MAY26 study guide)

Spectrum-X and InfiniBand carry equal 30% weight, so you need both fabrics cold. Items show NVUE snippets, nv show or UFM output, or a symptom, and the distractors are real tools working at the wrong layer. NVIDIA says lab exercises are being added from November 1, so recheck the format.

  1. 01
    NVIDIA Spectrum Networking (30%) — RoCE QoS with ECN and PFC, adaptive routing, BGP-EVPN tenancy, NVIDIA Air, WJH, NetQ, DOCA and SuperNIC setup
  2. 02
    NVIDIA InfiniBand Networking (30%) — subnet manager and HA, PKeys, SL-to-VL QoS, adaptive routing, UFM monitoring
  3. 03
    Troubleshooting Tools (20%) — ibstat, iblinkinfo, ibdiagnet, ibping, perftest, cl-resource-query, nvidia-smi topo
  4. 04
    Automation and Configuration (10%) — NVUE pending/applied/saved states, templates, Ansible nvidia.nvue playbooks
  5. 05
    AI Data Center Design and Optimization (5%) — AI factory planes, scalable units, rail-optimized topologies, NVLink vs. scale-out
  6. 06
    Kubernetes Integration (5%) — Network Operator, NicClusterPolicy, Multus, RDMA and SR-IOV device plugins

Wrong instinct vs correct approach

Some leaf uplinks are saturated while others sit idle during an all-reduce on a Spectrum-X fabric
✕ Wrong instinct

Tune the ECMP hash to spread AI flows better

✓ Correct approach

A few large synchronized flows collide under any hash. Enable per-packet adaptive routing on the switches with SuperNIC reordering on the hosts; both sides are required, and the slowest flow sets step time.

An engineer needs to know exactly why specific packets were dropped on a Spectrum switch
✕ Wrong instinct

Read interface discard counters on each port

✓ Correct approach

Counters only give totals. What Just Happened reports each drop with reason, port and flow, across L1, L2, router, tunnel, ACL and buffer groups. Only buffer drops indicate congestion; an ACL reason points to policy instead.

ibping to a remote host's LID fails while ibstat on both hosts shows Active ports
✕ Wrong instinct

Conclude the remote host is unreachable on the fabric

✓ Correct approach

ibping needs a responder: run ibping -S on the target first. Likewise ib_write_bw and ib_write_lat need a server side, and bandwidth tests never answer latency questions.

Two tenants share a Spectrum-X EVPN fabric and must never reach each other
✕ Wrong instinct

Put both tenants in one VRF on separate VLANs

✓ Correct approach

A shared VRF shares a routing table, so tenants can route to each other. Give each tenant its own VRF and L3 VNI; type 5 routes carry tenant prefixes and type 2 carries MAC and host entries.

Pods on a Kubernetes cluster need dedicated RDMA interfaces on an InfiniBand fabric
✕ Wrong instinct

Deploy the RDMA shared device plugin through the GPU Operator

✓ Correct approach

The Network Operator, configured by NicClusterPolicy, deploys the stack. SR-IOV virtual functions give per-pod isolation, Multus adds the secondary network, and IPoIBNetwork fits InfiniBand. The GPU Operator only adds GPUDirect RDMA peer memory.

Know these cold

  • ▸ NVLink and NVSwitch are scale-up; InfiniBand or Spectrum-X Ethernet carry scale-out traffic between servers
  • ▸ A rail is the same NIC index across all servers on one leaf, not one server
  • ▸ NCCL PXN relays over NVLink to the destination rail, avoiding cross-rail spine hops
  • ▸ GPUDirect RDMA moves GPU-to-GPU over the network; GPUDirect Storage moves storage-to-GPU data
  • ▸ ECN is proactive and end to end; PFC is a reactive backstop; adaptive routing avoids hot links
  • ▸ InfiniBand is natively lossless with credit-based flow control; never look for PFC there
  • ▸ SL is carried in the packet; SL2VL tables map it per link; VL15 is reserved for management
  • ▸ Scope ladder — bstat local port, iblinkinfo link width and speed, ibdiagnet whole-fabric scan
  • ▸ WJH explains drops, NetQ tracks changes and validates, Air simulates config, not ASIC throughput
  • ▸ nvidia-smi topo -m — IX is the best GPU-NIC path; SYS crosses the CPU socket

Can you answer these without checking your notes?

In this scenario: "Some leaf uplinks are saturated while others sit idle during an all-reduce on a Spectrum-X fabric" — what should you do first?
A few large synchronized flows collide under any hash. Enable per-packet adaptive routing on the switches with SuperNIC reordering on the hosts; both sides are required, and the slowest flow sets step time.
In this scenario: "An engineer needs to know exactly why specific packets were dropped on a Spectrum switch" — what should you do first?
Counters only give totals. What Just Happened reports each drop with reason, port and flow, across L1, L2, router, tunnel, ACL and buffer groups. Only buffer drops indicate congestion; an ACL reason points to policy instead.
In this scenario: "ibping to a remote host's LID fails while ibstat on both hosts shows Active ports" — what should you do first?
ibping needs a responder: run ibping -S on the target first. Likewise ib_write_bw and ib_write_lat need a server side, and bandwidth tests never answer latency questions.

Common Exam Mistakes — What candidates get wrong

Treating PFC as the main congestion control on RoCE fabrics

PFC only pauses a priority; heavy pausing spreads congestion and causes head-of-line blocking. ECN marking plus SuperNIC congestion control handles sustained load, with PFC as the backstop. Many pause frames and few ECN marks means ECN thresholds need tuning.

Replacing cables when InfiniBand ports show LinkUp but stay in Initialize

LinkUp proves the physical layer works. Initialize means no subnet manager has assigned LIDs and routes. Start or fix the SM; for HA run standby SMs, since only one master per subnet is elected by highest priority, then lowest GUID.

Expecting two limited PKey members to communicate with each other

The PKey high bit marks full membership. Full-to-full and full-to-limited traffic is allowed; limited-to-limited is blocked. The default partition is 0x7fff. In Kubernetes, ib-kubernetes applies PKeys to pods because namespaces do nothing on the fabric.

Assuming nv set changes forwarding or that apply always persists

NVUE stages nv set and nv unset in a pending revision until nv config apply runs. Persistence to /etc/nvue.d/startup.yaml is automatic only with auto save on, the default from Cumulus Linux 5.9; otherwise nv config save is required.

Picking DPU mode as the per-GPU east-west adapter

In Spectrum-X the SuperNIC, typically one per GPU, owns east-west congestion control and packet reordering for adaptive routing. BlueField-3 in DPU mode sits on the north-south path for security, storage and infrastructure offload.

Resources to help you pass NVIDIA AI Networking Professional on your first attempt

NCP-AIN rewards picking the right fabric tool at the right layer. Check your Spectrum-X and InfiniBand readiness.