← Problem Library
Network L6 NETWORK-1253 · 19 min

A BGP session stays Established while one route class disappears because local policy still expects communities the upstream stopped sending

Transport is healthy, yet route policy silently stops matching the intended prefixes because the upstream attribute contract changed.

NetworkFoundation OpsLevel 6Free19 min
Scenario

A provider-side change leaves the peering up while one set of business routes vanishes from the local table.

What to check first
  • Identify the primary failure signal in the Established Session, Broken Attribute 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 upstream attribute contract before changing timers or reset behavior.

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

Community-field BGP problem inspired by operator and Cisco Community threads where route classes disappeared after upstream community changes. An Established BGP session proves reachability, not that the route attributes your policy depends on still exist.

What usually causes A BGP session stays Established in production?

Teams often suspect flap damping or soft-reset problems when the upstream simply changed exported communities.

What should you document after resolving A BGP session stays Established?

Community-driven policy is fragile without an explicit and stable upstream contract.