-
- MPLS Traffic Engineering - LSP Attributes
- MPLS Traffic Engineering (TE) - Autotunnel Primary and Backup
- MPLS Traffic Engineering - AutoTunnel Mesh Groups
- MPLS Traffic Engineering - Verbatim Path Support
- MPLS Traffic Engineering - RSVP Hello State Timer
- MPLS Traffic Engineering Forwarding Adjacency
- MPLS Traffic Engineering (TE) - Class-based Tunnel Selection
- MPLS Traffic Engineering - Interarea Tunnels
- MPLS TE - Bundled Interface Support
- MPLS Traffic Engineering�Automatic Bandwidth Adjustment for TE Tunnels
- MPLS Point-to-Multipoint Traffic Engineering
- MPLS Traffic Engineering�Tunnel Source
-
- MPLS Traffic Engineering - Inter-AS TE
- MPLS Traffic Engineering - Shared Risk Link Groups
- MPLS Traffic Engineering (TE) - Autotunnel Primary and Backup
- MPLS Traffic Engineering (TE) - Path Protection
- MPLS Traffic Engineering (TE) - Fast Reroute (FRR) Link and Node Protection
- MPLS TE: Link and Node Protection, with RSVP Hellos Support (with Fast Tunnel Interface Down Detection)
- MPLS Traffic Engineering: BFD-triggered Fast Reroute (FRR)
-
- MPLS MTU Command Changes
- AToM Static Pseudowire Provisioning
- MPLS Pseudowire Status Signaling
- L2VPN Interworking
- L2VPN Pseudowire Redundancy
- L2VPN Pseudowire Switching
- VPLS Autodiscovery: BGP Based
- H-VPLS N-PE Redundancy for QinQ and MPLS Access
- L2VPN Multisegment Pseudowires
- QOS Policy Support on L2VPN ATM PVPs
- L2VPN: Pseudowire Preferential Forwarding
-
- Configuring MPLS Layer 3 VPNs
- MPLS VPN Half-Duplex VRF
- MPLS VPN�Show Running VRF
- MPLS VPN�VRF CLI for IPv4 and IPv6 VPNs
- MPLS VPN--BGP Local Convergence
- MPLS VPN�Route Target Rewrite
- MPLS VPN�Per VRF Label
- MPLS VPN 6VPE per VRF Label
- MPLS Multi-VRF (VRF Lite) Support
- BGP Best External
- BGP PIC Edge for IP and MPLS-VPN
- MPLS VPN - L3VPN over GRE
- Dynamic Layer-3 VPNs with Multipoint GRE Tunnels
- MPLS VPN over mGRE
-
- MPLS LSP Ping/Traceroute for LDP/TE, and LSP Ping for VCCV
- MPLS EM�MPLS LSP Multipath Tree Trace
- Pseudowire Emulation Edge-to-Edge MIBs for Ethernet, Frame Relay, and ATM Services
- MPLS Enhancements to Interfaces MIB
- MPLS Label Distribution Protocol MIB Version 8 Upgrade
- MPLS EM�MPLS LDP MIB - RFC 3815
- MPLS Label Switching Router MIB
- MPLS EM�MPLS LSR MIB - RFC 3813
- MPLS Traffic Engineering MIB
- MPLS Traffic Engineering - Fast Reroute MIB
- MPLS EM - TE MIB RFC 3812
- MPLS VPN�MIB Support
- MPLS EM - MPLS VPN MIB RFC4382 Upgrade
-
- MPLS High Availability: Overview
- MPLS High Availability: Command Changes
- MPLS LDP Graceful Restart
- NSF/SSO - MPLS LDP and LDP Graceful Restart
- NSF/SSO: MPLS VPN
- AToM Graceful Restart
- NSF/SSO�Any Transport over MPLS and AToM Graceful Restart
- NSF/SSO - MPLS TE and RSVP Graceful Restart
- ISSU MPLS Clients
- NSF/SSO/ISSU Support for VPLS
- NSF/SSO and ISSU - MPLS VPN 6VPE and 6PE
- Finding Feature Information
- Contents
- Prerequisites for MPLS Traffic Engineering: Tunnel Source
- Restrictions for MPLS Traffic Engineering: Tunnel Source
- Information About MPLS Traffic Engineering: Tunnel Source
- How to Configure MPLS Traffic Engineering: Tunnel Source
- Configuration Examples for MPLS Traffic Engineering: Tunnel Source
- Additional References
- Feature Information for MPLS Traffic Engineering: Tunnel Source
MPLS Traffic Engineering: Tunnel Source
The Multiprotocol Label Switching (MPLS) Traffic Engineering (TE): Tunnel Source feature allows you to specify the IP address assigned to an interface as the source IP address for control packets. The default behavior is to use the router ID configured in the Interior Gateway Protocol (IGP) using the mpls traffic-eng router-id command.
Finding Feature Information
Your software release may not support all the features documented in this module. For the latest feature information and caveats, see the release notes for your platform and software release. To find information about the features documented in this module, and to see a list of the releases in which each feature is supported, see the "Feature Information for MPLS Traffic Engineering: Tunnel Source" section.
Use Cisco Feature Navigator to find information about platform support and Cisco software image support. To access Cisco Feature Navigator, go to http://www.cisco.com/go/cfn. An account on Cisco.com is not required.
Contents
•Prerequisites for MPLS Traffic Engineering: Tunnel Source
•Restrictions for MPLS Traffic Engineering: Tunnel Source
•Information About MPLS Traffic Engineering: Tunnel Source
•How to Configure MPLS Traffic Engineering: Tunnel Source
•Configuration Examples for MPLS Traffic Engineering: Tunnel Source
•Feature Information for MPLS Traffic Engineering: Tunnel Source
Prerequisites for MPLS Traffic Engineering: Tunnel Source
•You can configure tunnel source only for MPLS-TE tunnels.
•Understand how to configure TE tunnels. See the "Additional References" section.
Restrictions for MPLS Traffic Engineering: Tunnel Source
•The configuration of other types of tunnels are not affected by this feature.
•Configuring a tunnel source affects the control traffic and not the traffic forwarded in the dataplane on this tunnel.
Information About MPLS Traffic Engineering: Tunnel Source
When you configure an MPLS TE tunnel, the address specified in the tunnel source command is used as the source IP address for control traffic to signal the tunnel. The source IP address overrides the default IP address taken from the IGP command mpls traffic-eng router-id.
MPLS Traffic Engineering: Tunnel Source Usage Guidelines
•Specifying a new source for an established tunnel causes the tunnel to be withdrawn and re-established.
•The tunnel source may be configured as an IP address or as an interface. If an interface is specified, it must have an associated IP address.
How to Configure MPLS Traffic Engineering: Tunnel Source
•Configuring MPLS Traffic Engineering: Tunnel Source
Configuring MPLS Traffic Engineering: Tunnel Source
You can configure the tunnel source as an IP address or as an interface. If you configure the tunnel source as an interface, then you should configure an IP address for the interface.
To specify a tunnel source for an MPLS TE tunnel, perform the following steps:
SUMMARY STEPS
1. enable
2. configure terminal
3. interface tunnel number
4. ip unnumbered interface-type interface-number
5. no ip directed-broadcast
6. tunnel source {ip-address | interface-type interface-number}
7. tunnel destination {host-name | ip-address | ipv6-address}
8. tunnel mode mpls traffic-eng
9. tunnel mpls traffic-eng priority setup-priority [hold-priority]
10. tunnel mpls traffic-eng bandwidth bandwidth
11. tunnel mpls traffic-eng affinity affinity-value mask mask-value
12. tunnel mpls traffic-eng path-option number explicit name explicit-path-name
13. tunnel mpls traffic-eng autoroute announce
14. end
15. show ip rsvp sender
DETAILED STEPS
Configuration Examples for MPLS Traffic Engineering: Tunnel Source
•Example: MPLS Traffic Engineering—Tunnel Source, page 5
MPLS Traffic Engineering: Tunnel Source: Example
The output of the show running-config command displays the tunnel source configuration. If the tunnel source command is not configured, the IP address specified in the IGP command mpls traffic-eng router-id is used.
Router# show running-config
Building configuration...
Current configuration: 3969 bytes
!
!
interface Tunnel1
ip unnumbered loopback0
tunnel source loopback1
tunnel mode mpls traffic-eng
tunnel destination 192.168.2.1
tunnel mpls traffic-eng priority 1 1
tunnel mpls traffic-eng bandwidth 5000
tunnel mpls traffic-eng affinity 0x0 mask 0x0
tunnel mpls traffic-eng path-option 1 explicit name BEST-WAY
tunnel mpls traffic-eng autoroute announce
!
!
...
router isis
net 49.0000.0001.0000.0001.00
is-type level-1
metric-style wide
mpls traffic-eng router-id Ethernet4/0/1
mpls traffic-eng level-1
!
The following sample output from the show ip rsvp sender command displays that the source IP address of the loopback interface used for tunnel control traffic:
Router# show ip rsvp sender
To From Pro DPort Sport Prev Hop I/F BPS
192.168.2.1 192.168.42.2 0 1 13 192.168.42.10 Et0/0 SE LOAD 5M
Additional References
Related Documents
|
|
---|---|
Cisco IOS commands |
|
MPLS commands |
|
MPLS TE automatic bandwidth adjustment for TE tunnels configuration tasks |
MPLS Traffic Engineering (TE)—Automatic Bandwidth Adjustment for TE Tunnels module |
MPLS TE - LSP Attributes |
MPLS Traffic Engineering—LSP Attributes module |
MPLS TE: Path Protection |
MIBs
|
|
---|---|
• |
To locate and download MIBs for selected platforms, Cisco software releases, and feature sets, use Cisco MIB Locator found at the following URL: |
Technical Assistance
Feature Information for MPLS Traffic Engineering: Tunnel Source
Table 1 lists the release history for this feature.
Use Cisco Feature Navigator to find information about platform support and software image support. Cisco Feature Navigator enables you to determine which software images support a specific software release, feature set, or platform. To access Cisco Feature Navigator, go to http://www.cisco.com/go/cfn. An account on Cisco.com is not required.

Note Table 1 lists only the software release that introduced support for a given feature in a given software release train. Unless noted otherwise, subsequent releases of that software release train also support that feature.