If you anticipate having multiple tunnels to share the same configuration, you can reduce your configuration time by using tunnel profiles to configure your tunnels.
In the profile, configure the tunnel endpoint last; anything configured after the tunnel endpoint does not take effect until the tunnel is brought up the next time. You can perform all other tasks in any order.
![]() |
Note: Tunnel profile configuration tasks are relevant only for traffic engineering networks. |
To configure a tunnel profile:
- host1(config)#mpls tunnels profile Lisbon
- host1(config-tunnelprofile)#tunnel mpls autoroute
announce isis
- host1(config-tunnelprofile)#tunnel mpls autoroute
metric absolute 100
- host1(config-tunnelprofile)#tunnel mpls path-option
3 dynamic isis
- host1(config-tunnelprofile)#tunnel mpls bandwidth
1240
- host1(config-tunnelprofile)#tunnel mpls priority
4 4
- host1(config-tunnelprofile)#tunnel mpls affinity
0x1100 mask 0xFFFF
- host1(config-tunnelprofile)#tunnel mpls no-route
retries 100
- host1(config-tunnelprofile)#tunnel mpls no-route
retry-time 45
- host1(config-tunnelprofile)#tunnel mpls retries
250
- host1(config-tunnelprofile)#tunnel mpls retry-time
65
- host1(config-tunnelprofile)#tunnel mpls description
southshore
When an endpoint is dynamically learned from the specified routing protocol, MPLS searches its tunnel profiles for a match. The dynamic tunnel is established using the settings from the first matching profile.