Hi Mike, also what we do here.
However, that was not that easy, we observed that a discard route imported to another vrf via auto-export on the same box was imported with its next-hop, that is... discard, instead of triggering an additional lookup in the internet table (what we use on some Ericsson/Redback routers in the same MPLS network). We ended up to find a way with some stupidly overcomplicated tricks (next-table route imported from a third vrf only used to contain such next-table routes with vrf-no-advertise, preventing its readvertisement once imported, while taking advantage of that next-table routes are more preferred than discard routes in a Junos RIB, etc...) leaving us with a nicely working but outrageously complicated config (but sometimes I suspect that it's the Junos Signature...). So, I'm rather curious to know the way you implemented that, in fact :) But maybe the routes you import are not discard? regards, Olivier Le 3 févr. 2014 à 23:44, Michael Gehrmann <mgehrm...@macquarietelecom.com> a écrit : > Hi Tobias, > > To put it simply your alternative option 2 would work. We use an Internet > table/vrf to collect CE routes and then import a default from the Internet > table into the CE vrf. To make it easy we add communities to the routes for > easy identification. > > Regards > Mike _______________________________________________ juniper-nsp mailing list juniper-nsp@puck.nether.net https://puck.nether.net/mailman/listinfo/juniper-nsp
