Table of Contents
Advertisement
JunosE 11.3.x IP, IPv6, and IGP Configuration Guide
mpls spf-use-any-best-path
mpls traffic-eng
mpls traffic-eng router-id
Using IS-IS Routes for Multicast RPF Checks
ip route-type
374
metric-style transition command. See "Extensions for Traffic Engineering" on page 325
and "Configuring Global IS-IS Parameters" on page 347 for detailed information about
using the metric-style commands.
Use to enable SPF calculations to consider the IGP (IS-IS) best paths as well as the
MPLS tunnel for forwarding traffic to the MPLS endpoint.
By default, the MPLS tunnel is always selected for traffic to the tunnel endpoint; IGP
paths are not considered. For traffic beyond the endpoint, the tunnel is considered
equally with any other path.
Example
host1(config-router)#mpls spf-use-any-best-path
Use the no version to disable the use of IGP best paths.
See mpls spf-use-any-best-path
Use to enable flooding of MPLS traffic engineering link information into the specified
IS-IS level. Flooding is disabled by default.
Example
host1(config-router)#mpls traffic-eng level-1
Use the no version to disable flooding.
See mpls traffic-eng
Use to specify a very stable interface to be used as a router ID for MPLS traffic
engineering. Typically you specify a loopback interface to provide the greatest stability,
because this is flooded to all nodes. The interface acts as the destination node for
tunnels originating at other nodes.
Example
host1(config-router)#mpls traffic-eng router-id loopback 0
Use the no version to remove the interface as a router ID.
See mpls traffic-eng router-id
You can use the ip route-type command to specify whether IS-IS routes are available
for only unicast forwarding protocols or only multicast reverse-path forwarding (RPF)
checks. Routes available for unicast forwarding appear in the unicast view of the routing
table, whereas routes available for multicast RPF checks appear in the multicast view
of the routing table.
Copyright © 2010, Juniper Networks, Inc.
Advertisement
Table of Contents
