Cisco ASR 9000 Series Configuration Manual page 215

Implementing MPLS Traffic Engineering
DETAILED STEPS
Command or Action
Step 1
configure
Example:
RP/0/RSP0/CPU0:router# configure
Step 2 interface tunnel-te tunnel-id
Example:
RP/0/RSP0/CPU0:router(config)# interface
tunnel-te 6
Step 3 ipv4 unnumbered type interface-path-id
Example:
RP/0/RSP0/CPU0:router(config-if)# ipv4
unnumbered Loopback0
Step 4 signalled-bandwidth {bandwidth [class-type
ct] | sub-pool bandwidth}
Example:
RP/0/RSP0/CPU0:router(config-if)#
signalled-bandwidth 10 class-type 1
Step 5 autoroute announce
Example:
RP/0/RSP0/CPU0:router(config-if)#
autoroute announce
Step 6 destination ip-address
Example:
RP/0/RSP0/CPU0:router(config-if)#
destination 10.1.1.1
Step 7
policy-class {1 - 7} | {default}
Example:
RP/0/RSP0/CPU0:router(config-if)#
policy-class 1
OL-28381-02
Purpose
Enters global configuration mode.
Configures an MPLS-TE tunnel interface and enables traffic engineering
on a particular interface on the originating node.
Assigns a source address so that forwarding can be performed on the
new tunnel.
Configures the bandwidth required for an MPLS TE tunnel. Because
the default tunnel priority is 7, tunnels use the default TE class map
(namely, class-type 1, priority 7).
Enables messages that notify the neighbor nodes about the routes that
are forwarding.
Assigns a destination address on the new tunnel.
• Destination address is the remote node's MPLS-TE router ID.
• Destination address is the merge point between backup and
protected tunnels.
Configures PBTS to direct traffic into specific TE tunnels or default
class.
Multiple EXP values can be specified as part of a policy-class, separated
by spaces. The EXP values configured to a TE tunnel effectively form
a monolithic policy-class, which should not overlap with other
policy-classes. Once an EXP value is used in a policy-class
configuration, it can only be reused if the subsequent policy-class
Cisco ASR 9000 Series Aggregation Services Router MPLS Configuration Guide, Release 4.3.x
Configuring Policy-based Tunnel Selection
199