When you configure explicit routing rather than hop-by-hop routing for MPLS, the route the LSP takes is defined by the ingress node. The path consists of a series of hops defined by the ingress LSR. Each hop can be a traditional interface, an autonomous system, or an LSP.
MPLS explicit routing configuration tasks include the following sets of tasks:
You can create explicit routing paths manually by configuring an explicit path with a name and a series of addresses (hops) from ingress to egress.
To manually configure explicit routing:
- host1(config)#mpls explicit-path name xyz
- host1(config-expl-path)#
- host1(config-expl-path)#next-address 10.10.9.2
- host1(config)#mpls explicit-path name xyz
![]() |
Note: To prevent a partially configured explicit path from being used, do not enable it until you have finished configuring or modifying the path. |
- host1(config-expl-path)#list 5
After you have defined a configured explicit path, you can configure the path on a tunnel.
To configure explicit routing on a tunnel:
- host1(config)#interface tunnel mpls:1
- host1(config-if)#tunnel mpls path-option 1
explicit name xyz
You can create explicit routing paths dynamically with a routing protocol. IS-IS and OSPF both currently support explicit routing.
To configure dynamic explicit routing:
- host1(config)#interface tunnel mpls:bilbao5
- host1(config-if)#tunnel mpls path-option 2
dynamic isis