Hi Darren, I don't think there is a good way of keeping other VPLS and VLLs off a specific LSP, but there are some options.
The LSP metric doesn't work for L2VPN traffic, so it's not useful. To keep other VPLS off the LSP, you could configure all of them to use other LSPs. Obviously this comes with a lot of configuration overhead, and it doesn't currently work for VLL (though soon, hopefully). The only way I know of to do this for VLL (which also works for VPLS), is to set the class of service for every VPLS and VLL. They will never use an LSP with a higher COS than their own configured COS, so by setting the LSP COS appropriately you can probably keep them on the right LSP. Cheers. Mitchell _____ From: Darren O'Connor [mailto:[email protected]] To: [email protected] [mailto:[email protected]] Sent: Wed, 19 Feb 2014 21:43:06 +1100 Subject: [f-nsp] LSP Metrics For a resilient solution recently I've had two firewalls in two DC's connected to two separate VPLS instances. This is through an XMR core running 5.4E I've created a TE LSP that doesn't follow the shorted path unlike the primary LSP. I've then set up the second VPLS to specifically use the second LSP. I only want to use this LSP for this VPLS. I don't want any other traffic using this LSP. I've set the metric for the LSP to 50000, however other VPLS/VLL instances are still using this path. From the config guide it seems that only BGP and IGPs take note of the metric of the LSP. How is it possible to ensure that a VPLS/VLL will only use this LSP if I specifically request it to do so? Thanks Darren http://www.mellowd.co.uk/ccie
_______________________________________________ foundry-nsp mailing list [email protected] http://puck.nether.net/mailman/listinfo/foundry-nsp
