ipsita
October 22, 2026, 9:33am
1
Hi,
We are trying to run the E2E Tests with Aerial L1 (26-1) in loopback mode ( Running cuBB End-to-End — Aerial CUDA-Accelerated RAN ) by connecting the two physical NIC ports of a DGX Spark to the same switch.
Does DGX Spark support running these loopback E2E tests (TestMAC, CuPhyController and RU Emulator on same system)? If yes, could you please guide with the steps to do the same and what each of the following files do?
cubb_scripts/autoconfig/l1_core_config/l1_logical_cores_DU_CG1_RU_LOOPBACK.yaml
testBenches/phase4_test_scripts/physical_cores_du.yaml
testBenches/phase4_test_scripts/physical_cores_ru.yaml
testBenches/phase4_test_scripts/test_config_summary.sh
Is there any minimum number of cores required to run these tests?
Hi @ipsita ,
Welcome to the Forum!
Unfortunately, we haven’t verified the RU emulator on DGX Spark yet.
Thank you.
ipsita
October 26, 2026, 4:59am
3
Hi,
Thanks for your reply…
So, on which platform did you try loopback testing, and could you guide us through the steps?
We have used only GH200 for the loopback connection. Here are the configuration files we have defined.
main/cubb_scripts/autoconfig/l1_core_config
An SDK (Software Development Kit) for building commercial-grade, AI-native, 3GPP, and O-RAN compliant 5G/6G gNB software on NVIDIA-accelerated computing platforms. - NVIDIA/aerial-cuda-accelerated-ran
Please take a look at this README.md for the usage.
# Running Phase-4 Tests
The scripts in `$cuBB_SDK/testBenches/phase4_test_scripts` can be used to run phase-4 tests (also known as cuBB tests).
## Quick Start with Test Configuration Parser
The recommended way to run tests is using the test configuration parser, which automatically generates all required parameters from a test case string.
### Prerequisites
1. **Reserve and log into a pair of lockable systems** (DU and RU nodes)
2. **Ensure codebase is on shared NFS** - All nodes must have access to the same `$cuBB_SDK` directory via shared network filesystem
3. **Configure and verify the PTP roles:**
- These Phase-4 scripts do not install or reconfigure PTP.
- The Aerial host installer defaults to `PTP_ROLE=client`, which configures the node as the PTP slave/timeReceiver for use with an external grandmaster.
- For a direct DU/RU-emulator pair without an external grandmaster, provision the DU as `client` and the RU-emulator host as `master`. Pass the role through the platform-specific `make install` commands in [`cubb_scripts/install/README.md`](../../cubb_scripts/install/README.md).
- Verify that both nodes are PTP synchronized before running the test.
4. **Deploy containers:**
- DU node: Either two containers (DU1 for main operations, DU2 for testMAC) OR one container with two sessions
- RU node: One container (RU)
This file has been truncated. show original