Configuring The Midpoint Routers - Cisco ASR 920 Series Configuration

Configuring the Midpoint Routers

Command or Action
Step 12
ip ip-address path-option id {dynamic | explicit
{namename | identifierid}
Example:
verbatim
[ ]}
Example:
Router(cfg-te-dest-list)# ip 10.10.10.10
path-option 1 dynamic
Step 13
exit
Example:
Router(cfg-te-dest-list)# exit
Step 14 ip explicit-path {nameword| identifiernumber} [enable
| disable]
Example:
Router(config)# ip explicit-path name path1
enable
Step 15 next-address [loose | strict] ip-address
Example:
Router(cfg-ip-expl-path)# next-address 10.0.0.2
Step 16
end
Example:
Router(cfg-ip-expl-path)# end
Configuring the Midpoint Routers
No special configuration is needed to support the P2MP TE feature on the midpoint routers. The midpoint
routers must have Cisco IOS Release or later release installed. They must be able to support and implement
the P2MP signaling extensions. The MPLS TE configuration of the midpoint routers supports both P2P and
P2MP TE. All multicast traffic is label switched. The midpoint routers do not require IPv4 multicast routing
or PIM.
For information on configuring MPLS TE, see MPLS Traffic Engineering and Enhancements.
MPLS Traffic Engineering Path Calculation and Setup Configuration Guide, Cisco IOS XE Release 3S (Cisco
ASR 920 Series)
24
MPLS Point-to-Multipoint Traffic Engineering
Purpose
Specifies the IP addresses of MPLS point-to-multipoint
traffic engineering tunnel destinations.
• If you use the explicit keyword, you must configure
explicit paths, using the ipexplicit-path command.
• Repeat this step for each destination.
Exits traffic engineering destination list configuration
mode.
Specifies the name of an IP explicit path and enters IP
explicit path configuration mode.
Specifies an explicit path that includes only the addresses
specified or loose explicit paths.
Exits the current configuration mode and returns to
privileged EXEC mode.