Page 1 of 1

Forcing SDP Path

Posted: 03 Sep 2014 20:43
by mayesch
Evening everyone,

I have several lsp based vpls/epipe services that are taking a non-optimal path to get to their destination, and this is creating additional latency for the users on this path.

I am trying to see if there is a way to force a LSP/SDP path in a different direction for specific vpls/epipe services. It's only specific services that I'm concerned with. Not all services using these SDP/LSP's need to be redirected.

Any thoughts on how one would go about accomplishing this?

Thanks
Chuck

Re: Forcing SDP Path

Posted: 05 Sep 2014 03:05
by zeips
Hi,

First you need to define new mpls path for your service(whatever epipe or vpls). So you can configure mpls path "X" with exact hops that you would like your service to travel trough, so that it s no colliding with the paths of other services. Then you configure new lsp "Y" and add the new path "X" to it. Next step is to configure new SDP "Z" where you specify lsp that your service is going to use which is lsp "Y". Now all you have to do is go to the service context which you want to take a new path and "bind" newly configured SDP "Z" to the service. The far side of the service needs to be reconfigured as well for the service to be operational.

I think this is the fastest way. However with this simple solution remember about 2 things, first that you have defined strict hops for your path if one of those hops goes down your path goes down, your service goes down(u can add secondary path without strict hops) and second if your other lsp-s change paths so that they are equal for your manualy defined path then again the latancy can occur.

There are some more advanced ways of assuring the different path to be taken by different services but requires configuration on all routers in the network and they are advanced.