Apstra ConnectorOps RNIC Configurator
Taiala

Apstra ConnectorOps RNIC Configurator

Lolomiina
2025-12-09

Juniper Networks, Inc.
1133 Auala Fou
Sunnyvale, Kalefonia 94089
ISA
408-745-2000
www.juniper.net

Juniper Networks, le logo Juniper Networks, Juniper, ma Junos o fa'ailoga fa'amaufa'ailoga a Juniper Networks, Inc. i le Iunaite Setete ma isi atunu'u. O isi fa'ailoga tau fefa'ataua'iga uma, fa'ailoga tautua, fa'ailoga resitala, po'o fa'ailoga tautua ua resitalaina o mea ia a latou tagata.
E leai se matafaioi a Juniper Networks mo soʻo se mea le saʻo i totonu o lenei pepa. Juniper Networks fa'asaoina le aia tatau e sui ai, suia, fesiita'i, po'o se isi itu e toe teuteu lenei lomiga e aunoa ma se fa'aaliga.
Apstra ConnectorOps RNIC Configurator Guide
Puletaofia © 2025 Juniper Networks, Inc. Ua taofia aia tatau uma.
O fa'amatalaga o lo'o i totonu o lenei pepa o lo'o lata mai e pei o le aso i le itulau autu.

TAUSAGA 2000 FAAALIGA
Juniper Networks hardware and software products is Year 2000 compliant. Junos OS e leai ni fa'agata fa'agata fa'atatau ile tausaga ile tausaga 2038. Peita'i, ole talosaga NTP e iloa e iai ni fa'afitauli ile tausaga 2036.

FA'AI'U FA'A'OA'OGA LAISENE MALIGA
O le Juniper Networks oloa o loʻo avea ma autu o lenei faʻamatalaga faʻapitoa e aofia ai (pe faʻamoemoe mo le faʻaogaina ma) Juniper Networks software. O le fa'aogaina o ia polokalame e fa'atatau i aiaiga ma aiaiga o le Maliega Laisene Tagata Fa'ai'u (“EULA”) fa'asalalau i le. https://support.juniper.net/support/eula/. E ala i le la'uina mai, fa'apipi'i, po'o le fa'aogaina o ia polokalame, e te ioe i aiaiga ma aiaiga o lena EULA.

E uiga i Lenei Taiala

This guide walks you through the setup and deployment of Apstra ConnectorOps RNIC Configurator.
You define QoS and DCQCN settings in Apstra, and ConnectorOps RNIC reads those settings to configure your GPU server RNICs accordingly. The service then generates and pushes vendor-specific configuration scripts to your GPU server RNICs over SSH. ConnectorOps RNIC runs as a service on a VM or host with access to both Apstra and the GPU servers. It continuously monitors selected blueprints for configuration changes and ensures that RDMA traffic is always managed according to the latest Apstra intent.

1 CHAPTER: Introduction

Folasaga

AOTELEGA
ConnectorOps RDMA Network Interface Card (RNIC) Configurator automates host-side RNIC configuration for GPU servers in your fabric.

ConnectorOps RDMA Network Interface Card (RNIC) Configurator is a service designed to automate host-side RDMA NIC configuration for GPU servers in your fabric. The service continuously monitors Apstra blueprints for changes in topology and QoS configuration, such as updates to the Data Center Quantized Congestion Notification (DCQCN) Configlets. If an update event occurs, the service automatically generates scripts that are delivered to GPU servers based on the vendor. This keeps the network interface card Differentiated Services Code Point (DSCP) and Priority-based Flow Control (PFC) settings aligned with the intended fabric policy.

FA'AMATALAGA FESOASOANI
Apstra ConnectorOps Setup Guide

2 CHAPTER: Prerequisites

Mea e mana'omia muamua
Blueprint Prerequisites

• GPU servers connected as “generic systems” in the blueprint
• All interface cabling is mapped in the blueprint
• Configlets assigned to all leaf switches with connected GPU hosts

Apstra ConnectorOps RNIC Configurator Prerequisites

• DCQCN Configlets created in Apstra
• Property Set imported with GPU server SSH credentials
• ConnectorOps RNIC host can access Apstra and GPU servers
• SSH is enabled on all GPU servers
• configure_nic flag set to “enable” for RNIC configuration automation

3 CHAPTER: Deploy ConnectorOps RNIC Configurator and Verify Connectivity

Deploy ConnectorOps RNIC Configurator and Verify Feso'ota'i

AOTELEGA
Use the following steps to deploy ConnectorOps RNIC Configurator and Verify Connectivity

1. Create a directory for the ConnectorOps image.
   mkdir ~/connectorops-rnic
2. Download the latest Apstra ConnectorOps RNIC image onto the VM/host/server.
   Use the following download link under Application Tools: https://support.juniper.net/support/downloads/?p=apstra.
3. Install Docker and Docker Compose.
4. Load the Docker image.
   root@test-vm:~/connectorops-rnic$ docker load -i <connectorops-rnic-image>
5. Create the docker-compose.yml file.
   O le mea lenei o se example Docker Compose. yml file.
   auaunaga:
   connector-ops-rnic:
   image: <image-name>:<tag>
   container_name: connector-ops-rnic
   siosiomaga:
   – AOS_URL=<aos-url>
   – AOS_USER=<aos-username>
   – AOS_PASSWORD=<aos-password>
   – CONFIGURE_NIC=enable
   taulaga:
   – “<host-port>:8080”
   voluma:
   – <path-to-host-directory>:/app/data
   restart: always
6. Start ConnectorOps RNIC Configurator.
   root@test-vm:~/connectorops-rnic$ docker-compose up -d
   The service begins caching blueprint data and monitoring for configuration changes.
7. Access the debugging dashboard to verify the service is active.
   Tatala a web browser and navigate to http://<host-ip>:<8080> (the same port in your docker-compose.yml) to view the dashboard tool.
   E tatau ona e vaʻai:
   • Active blueprints being monitored
   • Cached config-context data
   • Last poll timestamps
   • Any detected configuration changes

4 CHAPTER: Create and Import a Global Property Set

To Create and Import a Global Property Set

AOTELEGA
You must define a Property Set with input information for ConnectorOps to automate configuration generation to the RNICs. ConnectorOps uses this Property Set as the data source for configuration rendering and to establish connectivity between devices.
You must configure a Property Set with the “connectorops_config” prefix. The property set must include the following:

• gpu_host credentials: username/password to access the GPU host or hosts.
• gpu_details: username/password to access the GPUs.

O le mea lenei o se example Property Set. Note that the jump_host details are only required if your topology contains a jump host.

Name connectorops_config
Tulaga taua
{
“jump_host”: “<jump_host_ip>”,
“jump_host_user”: “<username>”,
“jump_host_password”: “<password>”,
“gpu_hosts_user”: “<username>”,
“gpu_hosts_password”: “<password>”,
“gpu_details”: {
“H100-01”: {
“user”: “<username>”,
“password”: “<password>”
},
“H100-0[2-4]”: {
“user”: “<username>”,
“password”: “<password>”
}
}
}

1. Navigate to Design > Property Sets > Create Property Set.
   The Create Property Set window displays.
2. Enter a Name and define a Property Set configuration in Values.
   Make sure to follow the proper naming convention.
3. Kiliki Fausia.
4. From within your Blueprint, navigate to Staged > Catalog > Property Sets > Import Property Set.
   The Import Property Set from Global Catalog window displays.
5. Select the Property Set you created from the dropdown, and click Import Property Set.
   This triggers an event, and ConnectorOps uses the Property Set as input to generate the configuration.

5 CHAPTER: Create and Import a DCQCN Configlet

Create and Import a DCQCN Configlet
For instructions about how to create and import a DCQCN Configlet into your Apstra blueprint, see Enable DCQCN in your AI Fabric.

For more information about DCQCN, see Data Center Quantized Congestion Notification (DCQCN).
O le mea lenei o se example DCQCN Configlet:

class-of-service {
classifiers {
dscp mydscp {
forwarding-class CNP {
loss-priority low code-points 110000;
}
forwarding-class NO-LOSS {
loss-priority low code-points 011010;
}
}
}
drop-profiles {
dp1 {
interpolate {
fill-level [ 55 90 ];
drop-probability [ 0 100 ];
}
}
}
shared-buffer {
ingress {
buffer-partition lossless {
percent 66;
dynamic-threshold 10;
}
buffer-partition lossless-headroom {
percent 24;
}
buffer-partition lossy {
percent 10;
}
}
egress {
buffer-partition lossless {
percent 66;
}
buffer-partition lossy {
percent 10;
}
}
}
dedicated-buffer {
ingress {
percent 15;
}
egress {
percent 30;
}
}
forwarding-classes {
class CNP queue-num 3;
class NO-LOSS queue-num 4 no-loss pfc-priority 3;
}
congestion-notification-profile {
cnp {
pfc-watchdog;
input {
dscp {
code-point 011010 {
pfc;
}
}
}
output {
ieee-802.1 {
code-point 011 {
flow-control-queue 4;
}
}
}
}
}
feso'ota'iga {
et-* {
congestion-notification-profile cnp;
scheduler-map sm1;
unit * {
classifiers {
dscp mydscp;
}
}
}
}
scheduler-maps {
sm1 {
forwarding-class CNP scheduler s2-cnp;
forwarding-class NO-LOSS scheduler s1;
}
}
schedulers {
s1 {
drop-profile-map loss-priority any protocol any drop-profile dp1;
explicit-congestion-notification;
}
s2-cnp {
transmit-rate percent 5;
priority strict-high;
}
}
}

After you import and commit, Apstra includes the DCQCN policies in the config-context for the relevant switches in your fabric. ConnectorOps RNIC Configurator automatically reads these policies and enforces them on all GPU server RNICs.

6 CHAPTER: Troubleshooting

Fa'afitauli
Check the following to help with troubleshooting:

• Ensure that the GPU servers are connected as “generic systems” in the blueprint.
• Verify that all user-inputted Property Sets follow the correct naming conventions and are properly imported into the relevant blueprints.
• Confirm that both Apstra and the GPU servers are reachable from the VM/host/server where ConnectorOps is installed.
• Check that the ConnectorOps RNIC Configurator service is up and running. Review logs for any errors using:

docker logs <container_name_or_id>

To access the debugging tool dashboard, visit http://<host-ip>:<8080>.
You can use the debugging dashboard tool to troubleshoot by checking which blueprints are being polled, when data was last updated, and whether any errors occurred while processing Apstra configuration changes.

Pepa / Punaoa

Juniper NETWORKS Apstra ConnectorOps RNIC Configurator [pdf] Taiala mo Tagata Fa'aoga Apstra ConnectorOps RNIC Configurator, ConnectorOps RNIC Configurator, RNIC Configurator

Fa'asinomaga

• Tusi Taiala