# Dual-Stack Common-Services VRF Confuses Aruba CX

DevFeed: [Dual-Stack Common-Services VRF Confuses Aruba CX](<https://devfeed.tech/articles/dual-stack-common-services-vrf-confuses-aruba-cx-11212.md>)

Original publisher: [Read original article](<https://blog.ipspace.net/2025/07/aruba-common-services-dual-stack-confusion/>)

Published: 2025-07-11T06:18:00Z

Content type: article

Language: en

Sources: [ipSpace.net blog](<https://devfeed.tech/sources/ipspace-net-blog.md>)

Topics: [bug](<https://devfeed.tech/topics/bug.md>), [configuration](<https://devfeed.tech/topics/configuration.md>), [Ansible](<https://devfeed.tech/topics/ansible.md>), [Software](<https://devfeed.tech/topics/software.md>)

Tags: [ansible](<https://devfeed.tech/tags/ansible.md>), [bug](<https://devfeed.tech/tags/bug.md>), [ipv6](<https://devfeed.tech/tags/ipv6.md>), [netlab](<https://devfeed.tech/tags/netlab.md>), [pre-release](<https://devfeed.tech/tags/pre-release.md>), [tests](<https://devfeed.tech/tags/tests.md>)

## AI overview

The article reports that ArubaCX fails inter-VRF route leaking between dual-stack VRFs. The issue includes a missing IPv6 export route target, an ineffective error report from the aoscx_config Ansible module, and behavior reproduced on ArubaCX 10.13 and physical devices.

## Source excerpt

As I was running the netlab pre-release integration tests, I noticed that ArubaCX failed the IPv6 Common Services test (it worked before). Here's the gist of what that test does: It creates three VRFs (red, blue, and common) It imports routes from red and blue VRF into the common VRF and routes from the common VRF into the red and blue VRF (the schoolbook example of common services VRF) Just to be on the safe side, it imports red routes into the red VRF and so on. Here's the relevant part of the netlab lab topology: Read more ...