configuring-netop-platform

Configure netop-tools platform settings and network use cases for NVIDIA Network Operator deployments.

7|4|Updated Oct 24, 2024
One-click install
npx skills add https://github.com/Mellanox/netop-tools --skill configuring-netop-platform-mellanox
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: configuring-netop-platform
Source: https://github.com/Mellanox/netop-tools/tree/main/skills/configuring-netop-platform
Command: npx skills add https://github.com/Mellanox/netop-tools --skill configuring-netop-platform-mellanox

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Setting up NVIDIA Network Operator networking on Kubernetes requires correctly configuring hardware-specific settings, choosing the right network use case (SR-IOV, InfiniBand, IPoIB, Macvlan, HostDevice), and formatting the error-prone NETOP_NETLIST device list. This Skill guides you through the entire configuration cascade so your global_ops_user.cfg matches your platform and workload. ## Core Features & Use Cases - Platform Config Selection: Copy and customize pre-built configs for DGX (B200, B300, GB200, GB300, H100/H200), Dell PowerEdge, OCI, Lenovo, and SuperMicro platforms. - Use Case Guidance: Choose between sriovnet_rdma, sriovibnet_rdma, hostdev_rdma_sriov, ipoib_rdma_shared_device, and macvlan_rdma_shared_device with correct device formats. - NETOP_NETLIST Formatting: Avoid common mistakes like using PCI BDF addresses for InfiniBand use cases or wrong field counts in device entries. - Feature Flags & Validation: Set OFED_ENABLE, NFD_ENABLE, IPAM_TYPE, and CREATE_CONFIG_ONLY, then generate and review YAML before deploying. - Use Case: You have a DGX GB300 cluster and need SR-IOV InfiniBand RDMA networking. This Skill walks you through copying the DGXGB300 config, selecting sriovibnet_rdma, formatting NETOP_NETLIST with IB interface names, and validating the generated YAML. ## Quick Start Ask the AI to configure netop-tools for a DGX GB300 platform with the sriovibnet_rdma use case and validate the generated network operator YAML.

Frequently Asked Questions about configuring-netop-platform

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I configure netop-tools for my hardware platform?

Copy the pre-built config for your platform from the config/ directory (e.g., config/dgx/global_ops_user.cfg.DGXGB300.bcm) to global_ops_user.cfg, then edit it for your environment. Source NETOP_ROOT_DIR.sh first so all scripts resolve paths correctly.

How do I choose between sriovnet_rdma and sriovibnet_rdma?

Use sriovnet_rdma for SR-IOV Ethernet networks with RoCE, specifying devices by PCI BDF address. Use sriovibnet_rdma for InfiniBand fabrics, specifying devices by IB interface names like ibs0f1.

What is the correct NETOP_NETLIST format for SR-IOV InfiniBand?

For InfiniBand use cases, entries use IB interface names: NETOP_NETLIST=( a,,,ibs0f1 b,,,ibs1f1 ). A common mistake is using PCI BDF addresses, which only apply to Ethernet SR-IOV and HostDevice use cases.

When should I use whereabouts instead of nv-ipam for IPAM?

Set IPAM_TYPE to whereabouts for clusters with fewer than 60 nodes, or use dhcp when an external DHCP server manages addresses. The default nv-ipam suits larger deployments.

Can I generate the network config without deploying it?

Yes. Leave CREATE_CONFIG_ONLY set to 1 and run ./install/ins-network-operator.sh to generate YAML without applying it. Review the output under usecase/${USECASE}/ before setting CREATE_CONFIG_ONLY=0 to deploy.