Hi, It's (at least for me) hard to guess without relevant configuration information for your 'core' interfaces and protocols mpls/rsvp/ospf/is-is section.
The reason CSPF information is missing is usually eighter reservation problems (not enough bandwith). Also, if you're using OSPF as igp for example, you'll need to enable 'traffic-engineering' in all nodes. HTH On 2/2/07, Amos Rosenboim <[EMAIL PROTECTED]> wrote: > Hi, > > I'm trying to enable MPLS in a small service provider network. > The network consists of 4 M10i routers, and 1 ERX router. > The ERX is out of the scope for the moment, and first stage was to > configure RSVP and MPLS on the M series routers, and to create a full > mesh of LSP. > The topology is described in the below drawing: > > R1-----3 X E1------R2------Ethernet (VLAN on a GigE interface)------ > R3----------T3------------R4 > > > > All is working well between R4, R3, and R2. > > However, all LSP from R1, except for the one to R2 are down. > The failed LSP at R1 shows: > CSPF failed: no route toward 217.69.0.4[4873 times] > > While: > [EMAIL PROTECTED]> show route 217.69.0.4 > > inet.0: 126 destinations, 131 routes (126 active, 0 holddown, 0 hidden) > + = Active Route, - = Last Active, * = Both > > 217.69.0.4/32 *[OSPF/150] 1d 11:16:33, metric 5, tag 0 > via e1-1/3/0.0 > > via e1-1/3/2.0 > via e1-1/3/4.0 > > inet.3: 108 destinations, 109 routes (108 active, 0 holddown, 0 hidden) > + = Active Route, - = Last Active, * = Both > > 217.69.0.4/32 *[OSPF/150] 1d 10:17:08, metric 5, tag 0 > > via e1-1/3/0.0, label-switched-path To-ATH > > > Also, RSVP is acting very strange over the 3 X E1 lines between R1 > and R2. > First, when we configured all 3 E1 for RSVP, only two neighbors came > up. After few clear RSVP session commands the third neighbor came up. > Then, there are only active RSVP sessions between R1 and R3 and R4, > only with R2. > > Then we disabled RSVP on 2 of the E1 lines and stayed with just one, > but R2 still showed 3 RSVP neighbors. Their idle time increase but > they are staying "up" although RSVP is no longer configured on those > interfaces. > When tracing RSVP on R2 we also get: > > Feb 1 12:05:35.602215 RSVP error, send to DISABLED interface? Hello > New 217.69.0.149->217.69.0.150 Len=8 e1-0/3/2.0 > Feb 1 12:05:59.356492 RSVP recv PathErr 217.69.0.134->217.69.0.133 > Session preempted LSP TO-THESS-FROM-ATH(12/44544) > Feb 1 12:05:59.356646 RSVP PathErr to client PathErr 217.69.0.134- > >217.69.0.133 Len=144 > Feb 1 12:06:10.635236 RSVP error, send to DISABLED interface? Hello > New 217.69.0.145->217.69.0.146 Len=8 e1-0/3/1.0 > Feb 1 12:06:35.617397 RSVP error, send to DISABLED interface? Hello > New 217.69.0.149->217.69.0.150 Len=8 e1-0/3/2.0 > Feb 1 12:07:10.650408 RSVP error, send to DISABLED interface? Hello > New 217.69.0.145->217.69.0.146 Len=8 e1-0/3/1.0 > Feb 1 12:07:35.632545 RSVP error, send to DISABLED interface? Hello > New 217.69.0.149->217.69.0.150 Len=8 e1-0/3/2.0 > Feb 1 12:08:10.665565 RSVP error, send to DISABLED interface? Hello > New 217.69.0.145->217.69.0.146 Len=8 e1-0/3/1.0 > Feb 1 12:08:31.729494 RSVP recv PathErr 217.69.0.134->217.69.0.133 > Session preempted LSP TO-THESS-FROM-ATH(12/44544) > Feb 1 12:08:31.729601 RSVP PathErr to client PathErr 217.69.0.134- > >217.69.0.133 Len=144 > Feb 1 12:08:35.647708 RSVP error, send to DISABLED interface? Hello > New 217.69.0.149->217.69.0.150 Len=8 e1-0/3/2.0 > > > > R2 is running : > Model: m10i > JUNOS Base OS boot [7.5R1.12] > JUNOS Base OS Software Suite [7.5R4.4] > JUNOS Kernel Software Suite [7.5R4.4] > JUNOS Packet Forwarding Engine Support (M7i/M10i) [7.5R4.4] > JUNOS Routing Software Suite [7.5R4.4] > JUNOS Online Documentation [7.5R4.4] > JUNOS Crypto Software Suite [7.5R4.4] > > R1 is running: > Model: m10i > JUNOS Base OS boot [7.5R4.4] > JUNOS Base OS Software Suite [7.5R4.4] > JUNOS Kernel Software Suite [7.5R4.4] > JUNOS Packet Forwarding Engine Support (M7i/M10i) [7.5R4.4] > JUNOS Routing Software Suite [7.5R4.4] > JUNOS Online Documentation [7.5R4.4] > JUNOS Crypto Software Suite [7.5R4.4] > > > > All the documentation i could find refers to the cspf no route error > message of the LSP as there is really no route, however, in this case > it seems that there is a route. > > > I'm suspecting it's either something with the 3 x E1 connection, or > RSVP issue, but I can't really fix it. > > Any help will be welcomed. > > > Amos Rosenboim > CTO > [EMAIL PROTECTED] > > www.oasis-tech.net > > > > _______________________________________________ > juniper-nsp mailing list [email protected] > https://puck.nether.net/mailman/listinfo/juniper-nsp > -- Erdem _______________________________________________ juniper-nsp mailing list [email protected] https://puck.nether.net/mailman/listinfo/juniper-nsp
