The route exists in the source VRF, but shared services remain unreachable because the target VRF never imports the right route target or policy match.
VRF leak design misses the import policy for a shared services subnet
The route exists in the source VRF, but shared services remain unreachable because the target VRF never imports the right route target or policy match.
Scenario
What to check first
- Identify the primary failure signal in the VRF Isolation 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
Choose the smallest safe recovery action first, then record the prevention work that reduces repeat incidents.
Questions worth viewing together
The source VRF can look perfect while the target import policy still hides the route from the real consumer path.
Similar cases seen in the field