A prefix set vanishes only after traffic moves to the standby multivendor edge.
A BGP session stays up and one prefix set disappears because the standby edge normalized route-map order differently
Peers remain established, but one standby node applies policy in a different effective sequence.
Scenario
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
- Summarize the current impact and the last known change.
- Collect direct evidence from logs, runtime state, and configuration before changing anything.
- Separate immediate recovery from permanent prevention work.
Recovery and prevention
Compare effective route-map order across active and standby nodes.
Questions worth viewing together
No. Keep commands, logs, file names, APIs, and product names unchanged, then explain the reasoning in the selected UI language.
State the root cause, the evidence that supports it, and the safest recovery direction.
The source scenario is treated as an incident artifact. Guidance, checklist, hints, and explanations can be localized around it.
Similar cases seen in the field