All, I've been having a great time with all your help in creating an MPLS ring and I've made tons of headway.
My issue now my ring is L2 broken using RSVP at an inconvenient point. I am assuming this break is natural to the creation of an MPLS Ring. Note the MPLS transport works. Just taking a +15ms path. However , I would like it broken at a point where two devices are co-located. Device A and B are co-located Device C and D are geographically separated but have a link between them. Currently I have the following RSVPs A A-B A-D B B-A B-C C C-D (Broken rsvp down) C-B D D-C (Broken rsvp down) D-A Incidentally The C-D link was the last MPLS Core link I turned up. This is displaying it self in my output by not having an RSVP Neighbor (neighbor down hellos sent) between C&D (and therefore sending my traffic inefficiently 3/4 way around the ring instead of the 1/4 hop it could. Last bit of information is that D sees C as a neighbor but is down. C does not even see D as a neighbor at all. I'm wondering how RSVP breaks that link. All the documentation I can find are focused on LSP validation/creation and not on Link Breaks to stop layer 2 loops (is my assumption). If one of my intervening links goes own I would like to correct it and then move the break to the specified point. But the RSVP documentation is rather...limited to only LSPs if I am reading it correctly. Any and all assistance would be much appreciated. Thank you *Levi Pederson* Mankato Networks LLC cell | 612.481.0769 work | 612.787.7392 levipeder...@mankatonetworks.net _______________________________________________ juniper-nsp mailing list juniper-nsp@puck.nether.net https://puck.nether.net/mailman/listinfo/juniper-nsp