Juniper JUNOSE SOFTWARE FOR E SERIES 11.0.X - BGP AND MPLS CONFIGURATION GUIDE 2009-12-30 Configuration Manual page 330

JUNOSe 11.0.x BGP and MPLS Configuration Guide
When you configure a node as the downstream endpoint of an LSP, you must provide
a stable interface as the router ID for the endpoint. Typically you select a loopback
interface because of its inherent stability. Use the mpls traffic-eng router-id
command to designate the router as traffic engineering capable and to specify the
router ID. For all tunnels that end at this node, set the tunnel destination to the
destination node's traffic-engineering router identifier, because the traffic-engineering
topology database at the tunnel ingress uses that for its path calculation.
You can use the show isis mpls and show isis database commands to display
information about IS-IS traffic engineering:
For OSPF, you can use the show ip ospf database opaque-area command to display
information about traffic-engineering opaque LSAs.
Related Topics
294
Configuring IGPs and MPLS
See JUNOSe IP, IPv6, and IGP Configuration Guide for more information about
enabling IS-IS to support traffic engineering and monitoring IS-IS traffic
engineering
See JUNOSe IP, IPv6, and IGP Configuration Guide for more information about
enabling OSPF to support traffic engineering and monitoring OSPF traffic
engineering
For information about BGP and MPLS, see Configuring BGP-MPLS Applications
on page 373
metric-style narrow
metric-style transition
metric-style wide
mpls spf-use-any-best-path
mpls traffic-eng
mpls traffic-eng area
mpls traffic-eng router-id
show ip ospf database
show isis database
show isis mpls adjacency-log
show isis mpls advertisements
show isis mpls tunnel
tunnel mpls autoroute announce
tunnel mpls autoroute metric