← Problem Library
Network L6 NETWORK-1271 · 17 min

A BGP session stays Established but traffic preference changes because the route-map clause that sets local preference no longer matches after a community contract changed upstream

Routes still arrive, yet the intended preference disappears because the local policy is keyed on a tagging behavior the upstream modified without dropping the session.

NetworkFoundation OpsLevel 6Free17 min
Scenario

A provider-facing BGP session remains healthy while traffic suddenly shifts to another path after an upstream policy change.

What to check first
  • Identify the primary failure signal in the Established BGP, Broken Community Contract scenario.
  • Separate visible symptoms from the underlying technical dependency.
  • Describe the safest recovery path and the follow-up prevention work.
Checking checklist
  1. Summarize the current impact and the last known change.
  2. Collect direct evidence from logs, runtime state, and configuration before changing anything.
  3. Separate immediate recovery from permanent prevention work.
Recovery and prevention

Validate the live attribute contract on received routes before rewriting timers or resetting peers.

Questions worth viewing together
What should you verify first when A BGP session stays Established but traffic preference changes appears?

Community-field network problem inspired by Cisco Community threads where local preference stopped applying after upstream community behavior changed. An Established session proves reachability, not that the communities your policy depends on are still present.

What usually causes A BGP session stays Established but traffic preference changes in production?

Teams often blame path flaps when the real issue is upstream attribute drift through a still-healthy session.

What should you document after resolving A BGP session stays Established but traffic preference changes?

Community-driven policy needs explicit verification whenever upstream routing contracts change.