← Problem Library
Network L4 NETWORK-1504 · 10 min

A BGP session stays established and one prefix set disappears because the standby edge normalized route-map order differently

Peers are healthy, but one standby device applies policy in a different sequence after config normalization.

NetworkFoundation OpsLevel 4Free10 min
Scenario

A prefix set vanishes only after traffic moves to the standby multivendor edge.

What to check first
  • Identify the primary failure signal in the The Peers Kept Smiling at Each Other and the Standby Sorted the Rule Cards in a Different Order Behind the Curtain 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

Compare effective route-map order across active and standby nodes.

Questions worth viewing together
Should I translate commands, logs, or product names?

No. Keep commands, logs, file names, APIs, and product names unchanged, then explain the reasoning in the selected UI language.

What should the answer focus on?

State the root cause, the evidence that supports it, and the safest recovery direction.

Why can the scenario remain in the original language?

The source scenario is treated as an incident artifact. Guidance, checklist, hints, and explanations can be localized around it.