The dest prefix needs to resolve over the LSP. IGP short-cuts is an easy way to make that happen and should work for you but I see you tried that already and had some issue. I would suggest trying to understand why igp shortcuts breaks something else.
You can also use a rib-group on the LSP head-end to populate inet3 as needed. -cb On Jan 18, 2013, at 10:11 AM, James Ashton wrote: > All, Just to clarify a few things, > > The destination is not in inet.3. I do not have a direct LSP to the > destination and cannot create one (The destination doesn't support MPLS nor > does it support BGP) > > > > The show route output is: > jashton@cr01-re0> show route xx.xxx.xx.x/24 > > inet.0: 448173 destinations, 3298320 routes (445123 active, 39 holddown, > 465440 hidden) > @ = Routing Use Only, # = Forwarding Use Only > + = Active Route, - = Last Active, * = Both > > xx.xxx.xx.x/24 *[OSPF/150] 1d 12:35:24, metric 20, tag 0 >> to xx.xxx.xx.x via xe-4/2/0.0 > [BGP/170] 01:03:59, localpref 100, from xx.xxx.xx.x > AS path: I >> to xx.xxx.xx.x via xe-5/2/0.0 > [BGP/170] 6d 19:17:07, MED 20, localpref 100, from > xx.xxx.xx.x > AS path: I >> to xx.xxx.xx.x via ae3.0 > [BGP/170] 6d 18:57:09, MED 20, localpref 100, from > xx.xxx.xx.x > AS path: I >> to xx.xxx.xx.x via ae2.0 > [BGP/170] 6d 19:03:11, MED 20, localpref 100, from > xx.xxx.xx.x > AS path: I >> to xx.xxx.xx.x via ae2.0 > [BGP/170] 6d 19:02:45, MED 20, localpref 100, from > xx.xxx.xx.x > AS path: I >> to xx.xxx.xx.x via ae2.0 > [BGP/170] 6d 19:18:02, MED 20, localpref 100, from > xx.xxx.xx.x > AS path: I >> to xx.xxx.xx.x via xe-4/2/0.0 > [BGP/170] 6d 17:40:10, MED 20, localpref 100, from > xx.xxx.xx.x > AS path: I >> to xx.xxx.xx.x via xe-5/2/0.0 > [BGP/170] 2d 13:54:44, MED 20, localpref 100, from > xx.xxx.xx.x > AS path: I >> to xx.xxx.xx.x via ae6.0 > [BGP/170] 6d 19:20:12, MED 20, localpref 100, from > xx.xxx.xx.x > AS path: I >> to xx.xxx.xx.x via xe-4/2/0.0 > [BGP/170] 6d 17:31:28, MED 20, localpref 100, from > xx.xxx.xx.x > AS path: I >> to xx.xxx.xx.x via xe-5/2/0.0 > [BGP/170] 6d 17:40:12, MED 20, localpref 100, from > xx.xxx.xx.x > AS path: I >> to xx.xxx.xx.x via xe-5/2/0.0 > > inet.3: 1232 destinations, 1248 routes (9 active, 0 holddown, 1232 hidden) > > ----- Original Message ----- > From: "Colby Barth" <cba...@juniper.net> > To: "James Ashton" <ja...@gitflorida.com> > Sent: Friday, January 18, 2013 9:31:51 AM > Subject: Re: [j-nsp] Traffic balancing over LSPs > > James- > > Could you possibly send the output of 'show route x.x.x.x/y' for one of the > destinations that you think should resolve over the LSP? > > I suspect that this destinations are not in inet3 for some reason. > > -Colby > > On Jan 18, 2013, at 8:49 AM, Phil Bedard wrote: > >> Is it all one OSPF area or is the CMTS in an area other than 0? If the >> MX480 is an ABR you can restrict the OSPF routes and originate them on >> the MX480 as BGP instead using aggregate statements. >> >> Phil From: James Ashton >> Sent: 1/17/2013 11:07 >> To: juniper-nsp@puck.nether.net >> Subject: [j-nsp] Traffic balancing over LSPs >> I have an interesting situation that has me stumped for the moment. >> >> I have an OSPF speaking device (ARRIS CMTS) hanging off from an EX Switch. >> That switch is uplinked to an MX480 which is part of the network core. >> It has several paths into it from rest of the network. >> From several major traffic centers in the network I have 3 LSPs >> created to the MX480. >> I am running "mpls traffic-engineering mpls-forwarding" throughout the >> network. >> >> As the end users hanging off the CMTS are advertised onto the network >> via OSPF, and I cannot terminate LSPs on the CMTS, the traffic to >> these users is not being forwarded over the LSPs. >> I have tested enabling "ospf traffic-engineering shortcuts" but that >> is breaking several paths in the network to legacy areas with odd >> configs. >> >> My question is basically, how can I get this traffic into these LSPs >> in way that is more manageable at scale than a pile of static routes. >> >> >> I hope the above is clear, I am low on Caffeine at the moment. >> >> Thank you in advance for any help/ideas. >> >> James >> _______________________________________________ >> juniper-nsp mailing list juniper-nsp@puck.nether.net >> https://puck.nether.net/mailman/listinfo/juniper-nsp >> _______________________________________________ >> juniper-nsp mailing list juniper-nsp@puck.nether.net >> https://puck.nether.net/mailman/listinfo/juniper-nsp >> > > > _______________________________________________ juniper-nsp mailing list juniper-nsp@puck.nether.net https://puck.nether.net/mailman/listinfo/juniper-nsp
