| Device | arubacx |
|---|---|
| Provider | libvirt |
| Test suite | evpn |
| Test | Supported | Lab started |
Devices configured |
Validated | Netlab version |
Test date | Device image |
|---|---|---|---|---|---|---|---|
| 01-vxlan-bridging | ✅ | ✅ | ✅ | 25.09 | 2025-08-01 17:14:08 | aruba/cx:10.15 | |
| 02-vxlan-asymmetric-irb | ✅ | ✅ | ✅ | 25.09 | 2025-08-01 17:15:31 | aruba/cx:10.15 | |
| 03-vxlan-symmetric-irb | ✅ | ✅ | ✅ | 25.09 | 2025-08-01 17:17:24 | aruba/cx:10.15 | |
| 04-vxlan-central-routing | ✅ | ✅ | ❌ (more) | 25.09 | 2025-08-01 17:19:35 | aruba/cx:10.15 | |
| Aruba CX core router doing VXLAN-to-VXLAN routing does not interoperate with Linux-based edge switches doing VXLAN-to-VLAN bridging. It does work with Arista cEOS and Cisco Nexu OS devices as edge switches. | |||||||
| 05-vxlan-l3only | ✅ | ✅ | ✅ | 25.09 | 2025-08-01 17:21:05 | aruba/cx:10.15 | |
| 06-vxlan-bridging-vlan-bundle | ✅ | ✅ | ✅ | 25.09 | 2025-08-06 18:15:04 | aruba/cx:10.15 | |
| 10-vxlan-rr | ✅ | ✅ | ✅ | 25.09 | 2025-08-01 17:22:14 | aruba/cx:10.15 | |
| 11-vxlan-ebgp | ✅ | ✅ | ✅ | 25.09 | 2025-08-01 17:23:14 | aruba/cx:10.15 | |
| 12-vxlan-ibgp-ebgp | ✅ | ✅ | ✅ | 25.09 | 2025-08-01 17:24:50 | aruba/cx:10.15 | |
| 13-vxlan-ebgp-allowas | ✅ | ✅ | ✅ | 25.09 | 2025-08-01 17:26:13 | aruba/cx:10.15 | |
| 14-vxlan-ebgp-ebgp | ✅ | ✅ | ✅ | 25.09 | 2025-08-01 17:27:46 | aruba/cx:10.15 | |
| 15-vxlan-ebgp-unnumbered | ❌ | 25.09 | 2025-08-01 17:27:52 | ||||
| 20-vxlan-irb-ospf | ✅ | ✅ | ❌ (more) | 25.09 | 2025-08-01 17:30:29 | aruba/cx:10.15 | |
| Aruba CX does not propagate CPU-generated traffic over VXLAN in IRB scenarios, making it impossible to establish VRF OSPF adjacency across a VXLAN link. | |||||||
| 21-bgp-ce-router | ✅ | ✅ | ✅ | 25.09 | 2025-08-01 17:32:02 | aruba/cx:10.15 | |
| 22-ospf-ce-router | ✅ | ✅ | ✅ | 25.09 | 2025-08-01 17:33:35 | aruba/cx:10.15 | |
| 30-cs-bridging | ❌ | 25.09 | 2025-08-01 17:33:41 | ||||
Notes: