Dear Arun, you can map a community for that VRF prefixes and set a next hop lsp under a policy in routing option.
this will achive the result. regards On Thu, Nov 15, 2012 at 12:27 PM, Arun Kumar <narain.a...@gmail.com> wrote: > Hi, > > I am testing RSVP-TE in Juniper MX Junos 11.2R3. Is there a way to have a > RSVP-TE between ingress and egress PE and use that RSVP-TE only for one > specific L3 MPLS VPN or L2 Circuit VPN customer and other VPN customers > between the same ingress and egress PE to prefer a IGP/LDP path? > > In case of Cisco, for L3 MPLS VPN the same can be done by changing the bgp > next hop to a new loopback and have a static for the new loopback over the > TE (without using "autoroute announce" option). But in Juniper, once > RSVP-TE is configure the tunnel destination usually loopback 0 (bgp next > hop for all L3 VPN customers) starts learned via inet.3 routing table. So > as soon as RSVP-TE comes up the loopback 0 of egress PE is learned via > RSVP-TE. I want to stop this and have only the new loopback (bgp next hop > for only one L3 VPN/L2 VPN) take RSVP-TE? > > Thanks in advance. > > Arun > _______________________________________________ > juniper-nsp mailing list juniper-nsp@puck.nether.net > https://puck.nether.net/mailman/listinfo/juniper-nsp > _______________________________________________ juniper-nsp mailing list juniper-nsp@puck.nether.net https://puck.nether.net/mailman/listinfo/juniper-nsp