Re: [j-nsp] Matching specific OSPF routes in aggregate policy

2013-09-30 Thread Rob Foehl
On Fri, 27 Sep 2013, Phil Fagan wrote: could you use BGP multi-hop and simply peer directly to the MX bypassing the need to redist routes in though your OSPF core? That's basically what I'm considering from the perspective of readvertising into BGP on the ABR... The source is going to be

Re: [j-nsp] Matching specific OSPF routes in aggregate policy

2013-09-30 Thread Phil Fagan
Got it; well let me know if you find either because its a very interesting scenario! Always a fan of the clever solutions :-) On Mon, Sep 30, 2013 at 1:11 PM, Rob Foehl r...@loonybin.net wrote: On Fri, 27 Sep 2013, Phil Fagan wrote: could you use BGP multi-hop and simply peer directly to

Re: [j-nsp] Matching specific OSPF routes in aggregate policy

2013-09-27 Thread Phil Fagan
could you use BGP multi-hop and simply peer directly to the MX bypassing the need to redist routes in though your OSPF core? On Thu, Sep 26, 2013 at 3:51 PM, Rob Foehl r...@loonybin.net wrote: On Thu, 26 Sep 2013, Phil Fagan wrote: Is your aggregate policy already on the MX and is its

Re: [j-nsp] Matching specific OSPF routes in aggregate policy

2013-09-26 Thread Phil Fagan
Is your aggregate policy already on the MX and is its purpose to export into BGP from OSPF? On Wed, Sep 25, 2013 at 2:42 PM, Rob Foehl r...@loonybin.net wrote: Hey folks, Another OSPF issue for the day: I have a somewhat specific need to match a route from a particular OSPF speaker in an

Re: [j-nsp] Matching specific OSPF routes in aggregate policy

2013-09-26 Thread Rob Foehl
On Thu, 26 Sep 2013, Phil Fagan wrote: Is your aggregate policy already on the MX and is its purpose to export into BGP from OSPF? That's the idea... There are disparate contributing routes, and they tend to come and go on a fairly regular basis. Generating like aggregates elsewhere and

[j-nsp] Matching specific OSPF routes in aggregate policy

2013-09-25 Thread Rob Foehl
Hey folks, Another OSPF issue for the day: I have a somewhat specific need to match a route from a particular OSPF speaker in an aggregate policy, and I'm not having much luck coming up with a straightforward way to do so. The route in question is injected via a type 5 LSA from a (dumb)