Specifications

show ip traffic-engineering
MP-544
Cisco IOS Multiprotocol Label Switching Command Reference
January 2010
• The tunnel headend router’s route to the egress is a connected route.
• The egress is unreachable from the tunnel tailend router.
Devices request metrics via an LDP adjacency. The display output shows detailed metric information.
The metric information includes a metric type (shown as routing_protocol/routing_protocol_subtype)
a
nd a metric value.
The routing protocol is as follows:
• Open Shortest Path First (OSPF)
• Intermediate System to Intermediate System (IS-IS)
• Enhanced Interior Gateway Routing Protocol (EIGRP)
• Connected
• Static
• Other (some other routing protocol)
The routing protocol subtype is specific to each routing protocol.
Examples The following is sample output from the sho
w ip traffic-engineering metrics detail command:
Router# show ip traffic-engineering metrics detail
Metrics requested BY this device
Prefix 43.0.0.1/32
TDP id 2.2.2.2:0, metric: connected/0
type request, flags metric-received, rev 6, refcnt 1
TDP id 4.4.4.4:0, metric: ospf-300/2
type request, flags metric-received, rev 7, refcnt 1
Prefix 44.0.0.0/8
TDP id 18.18.18.18:0, metric: connected/0
type request, flags metric-received, rev 1, refcnt 1
Metrics requested FROM this device
Prefix 36.0.0.0/8
TDP id 18.18.18.18:0, metric: connected/0
type advertise, flags none, rev 1, refcnt 1
Table 68 describes the significant fields shown in the display.
Ta b l e 68 show ip traffic-engineering metrics detail Field Descriptions
Field Description
Prefix Destination network and mask.
TDP id The LDP identifier of the LDP peer device at the other end of the tunnel.
T
he LDP peer device advertises these metrics to this neighbor.
metric The routing protocol and metric within that protocol for the prefix in
qu
estion.
type For metrics being requested by this device, the type is either “request” or
“r
elease.” For metrics being requested from this device, the type is
“advertise.”