 | Copyright © 2009, Juniper Networks, Inc. All rights reserved. Trademark Notice. | |
If you configure the traffic-engineering bgp-igp statement or the traffic-engineering bgp-igp-both-ribs statement, high-priority RSVP and LDP routes can supersede IGP routes in the inet.0 routing table. IGP routes might no longer be redistributed since they are no longer the active routes.
When you configure the mpls-forwarding option at either the [edit logical-systems logical-system-name protocols mpls traffic-engineering] hierarchy level or the [edit protocols mpls traffic-engineering] hierarchy level, RSVP and LDP routes are used for forwarding but are excluded from route selection. These routes are added to both the inet.0 and inet.3 routing tables. The RSVP and LDP routes in the inet.0 routing table are given a low preference when the active route is selected. However, the RSVP and LDP routes in the inet.3 routing table are given a normal preference and are therefore used for selecting forwarding next hops.
When you activate the mpls-forwarding option, routes whose state is ForwardingOnly are preferred for forwarding even if their preference is lower than that of the currently active route. To examine the state of a route, execute a show route detail command.
To configure, include the traffic-engineering mpls-forwarding statement:
-
traffic-engineering mpls-forwarding;
You can include this statement at the following hierarchy levels:
When you configure the mpls-forwarding option, IGP shortcut routes are copied to the inet.0 routing table only.
| Copyright © 2009, Juniper Networks, Inc. All rights reserved. Trademark Notice. | |