On Wed, Jun 9, 2010 at 18:20, Arie Vayner (avayner) <[email protected]> wrote: > In older releases, where this command is not available you can apply a > route-map on the output direction of the BGP session to the RR, match > the RT of the VRF, and set a different next-hop. It would do the same as > above but without the custom made command.
It can be done in the inbound direction, too. Couple of weeks ago I wrote a blog article that tweaks next-hop of the incoming VPNv4 update as a workaround for broken LSP. The same solution can be used to force the traffic via TE tunnel. Here is the link: http://blog.ipexpert.com/2010/05/31/next-hop-in-mpls-vpns/ -- Marko Milivojevic - CCIE #18427 Senior Technical Instructor - IPexpert YES! We include 400 hours of REAL rack time with our Blended Learning Solution! Mailto: [email protected] Telephone: +1.810.326.1444 Fax: +1.810.454.0130 Web: http://www.ipexpert.com/ _______________________________________________ cisco-nsp mailing list [email protected] https://puck.nether.net/mailman/listinfo/cisco-nsp archive at http://puck.nether.net/pipermail/cisco-nsp/
