# ArubaCX Delays BGP Policy Update Advertisements

DevFeed: [ArubaCX Delays BGP Policy Update Advertisements](<https://devfeed.tech/articles/arubacx-decides-when-you-re-done-changing-a-bgp-routing-policy-11223.md>)

Original publisher: [Read original article](<https://blog.ipspace.net/2025/08/aruba-bgp-route-map/>)

Published: 2025-08-22T06:16:00Z

Content type: opinion

Language: en

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

Topics: [BGP](<https://devfeed.tech/topics/bgp.md>), [Routing (disambiguation)](<https://devfeed.tech/topics/routing.md>), [configuration](<https://devfeed.tech/topics/configuration.md>), [networking](<https://devfeed.tech/topics/networking.md>)

Tags: [bgp](<https://devfeed.tech/tags/bgp.md>), [configuration](<https://devfeed.tech/tags/configuration.md>), [netlab](<https://devfeed.tech/tags/netlab.md>), [routing](<https://devfeed.tech/tags/routing.md>), [validation](<https://devfeed.tech/tags/validation.md>)

## AI overview

The article investigates why an ArubaCX BGP policy validation test failed. It reports that ArubaCX initially advertised prefixes without MED and resent them with MED about twelve seconds later, requiring a longer validation wait.

## Source excerpt

When I was cleaning the "set BGP MED" integration test, I decided that once a BGP prefix is in the BGP table of the BGP peer, there's no need for a further wait before checking its MED value. After all: We configure an outbound routing policy to change MED; We execute do clear bgp * soft out at the end of most BGP policy configuration templates1 The device under test should thus immediately (re)send the expected BGP prefix with the target MED. That approach failed miserably with ArubaCX; it was time to investigate the details. Read more ...