Peter,
One way to accomplish what I think you are asking for is to use
different BGP next hops for destinations you want to have native IP
switched traffic and those which you want to transport over MPLS LSP (TE
or LDP). Then you are only constructing MPLS LSPs to those next hops you
would like to see label switched to.
R.
We are in the process of enabling traffic engineering with shortcuts for
ISIS on an IP\MPLS based network. As a result of enabling ISIS traffic
engineering with shortcuts, IP traffic will utilize the LSP paths (inet.3)
for the forwarding decision. Is there a configuration feature so the IP
traffic will continue to used inet.0 as we enable the ISIS traffic
engineering feature.
We observed a disruption in our IP traffic when we enabled the traffic
engineering feature possibly due to the fact in the change of the forwarding
path to the LSP.
Regards,
Peter
_______________________________________________
juniper-nsp mailing list [email protected]
https://puck.nether.net/mailman/listinfo/juniper-nsp
_______________________________________________
juniper-nsp mailing list [email protected]
https://puck.nether.net/mailman/listinfo/juniper-nsp
