Hi Adam, Thats what I was looking for...hmmm, might need to brush up on the lab skills again, hehe...
Thanks Ciao -----Original Message----- From: Vitkovský Adam [mailto:[email protected]] Sent: Tuesday, April 01, 2014 11:49 AM To: JC Cockburn; [email protected] Subject: RE: [c-nsp] ISIS Distance question Hi JC, > The real life problem is A and B are PE routers and C is the RR. So I > do not have MPLS on the interfaces towards C from A & B. So when the > A-B link fails, it will break the label switched path between them. A > and B have CsC links which should then be preferred.. If you are using separate Control-Plane (RRs that are not part of the MPLS/data-plane) you may set the overload bit on your RRs via the "router isis" cmd: "set-overload-bit". This will assign maximum ISIS metric to all links advertised by the RR -this will assure that RR will never end up on the forwarding path between any two PEs. adam _______________________________________________ cisco-nsp mailing list [email protected] https://puck.nether.net/mailman/listinfo/cisco-nsp archive at http://puck.nether.net/pipermail/cisco-nsp/
