OSPF External routes on directly connected VRF interfaces

[deanwebb]

Good God, we've missed posts from mellowd

If I ever get sued and forced to change the name of the website, I'll change it to mellowd-forums.com.

[icecream-guy]

should probably get that now and forward it here.     
or someone else will grab it...

[mellowd]

Awesome, thanks for confirming. So ruling out vrf-target due to lack of options, say we're manually importing/exporting, what are out options?

I tried to manually tag that rte-type community but its rejected. Morever that's a terrible solution, you'd need to match only Type 1/2/3, manually specify the area etc... is this just a limitation of doing OSPF PE-CE on JunOS?


BTW been reading your articles including that one, thanks for taking the time! Going for JNCIS-SP shortly and your articles (and explanation above!) have always been a great help.

loj001@SP-LAB-PE1# set policy-options community domain-b members rte-type:0.0.0.0:1:0     

[edit]
loj001@SP-LAB-PE1# commit
[edit policy-options community domain-b members]
  'rte-type:0.0.0.0:1:0'
    Unknown extended community type
error: configuration check-out failed

Pretty much. OSPF as PE-CE is one of things needed for lab, but hardly done in real life. This is a job for BGP. It doesn't really break anything, but it's odd to see a route to an internal prefix reached through interface learned through a type 5 :O