- MPLS Traffic Engineering--Fast Reroute Link and Node Protection
- MPLS TE Link and Node Protection with RSVP Hellos Support
- MPLS Traffic Engineering (TE) Path Protection
- MPLS Traffic Engineering (TE)--IP Explicit Address Exclusion
- MPLS Traffic Engineering-Autotunnel Primary and Backup
- MPLS Traffic Engineering BFD-triggered Fast Reroute
- MPLS Traffic Engineering Shared Risk Link Groups
- MPLS Traffic Engineering Inter-AS TE
- Finding Feature Information
- Prerequisites for MPLS Traffic Engineering (TE)--IP Explicit Address Exclusion
- Restrictions for MPLS Traffic Engineering (TE)--IP Explicit Address Exclusion
- Information About MPLS Traffic Engineering (TE)--IP Explicit Address Exclusion
- How to Configure MPLS Traffic Engineering (TE)--IP Explicit Address Exclusion
- Configuration Examples for MPLS Traffic Engineering (TE)--IP Explicit Address Exclusion
- Additional References
- Feature Information for MPLS Traffic Engineering (TE)--IP Explicit Address Exclusion
- Glossary
MPLS Traffic Engineering (TE)--IP Explicit Address Exclusion
The MPLS Traffic Engineering (TE)--IP Explicit Address Exclusion feature provides a means to exclude a link or node from the path for Multiprotocol Label Switching (MPLS) TE label switched path (LSP).
The feature is enabled through the ip explicit-path command that allows you to create an IP explicit path and enter a configuration submode for specifying the path. The feature adds to the submode commands the exclude-address command for specifying addresses to exclude from the path.
If the excluded address for an MPLS TE LSP identifies a flooded link, the constraint-based shortest path first (CSPF) routing algorithm does not consider that link when computing paths for the LSP. If the excluded address specifies a flooded MPLS TE router ID, the CSPF routing algorithm does not allow paths for the LSP to traverse the node identified by the router ID.
- Finding Feature Information
- Prerequisites for MPLS Traffic Engineering (TE)--IP Explicit Address Exclusion
- Restrictions for MPLS Traffic Engineering (TE)--IP Explicit Address Exclusion
- Information About MPLS Traffic Engineering (TE)--IP Explicit Address Exclusion
- How to Configure MPLS Traffic Engineering (TE)--IP Explicit Address Exclusion
- Configuration Examples for MPLS Traffic Engineering (TE)--IP Explicit Address Exclusion
- Additional References
- Feature Information for MPLS Traffic Engineering (TE)--IP Explicit Address Exclusion
- Glossary
Finding Feature Information
Your software release may not support all the features documented in this module. For the latest caveats and feature information, see Bug Search Tool and 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 table at the end of this module.
Use Cisco Feature Navigator to find information about platform support and Cisco software image support. To access Cisco Feature Navigator, go to www.cisco.com/go/cfn. An account on Cisco.com is not required.
Prerequisites for MPLS Traffic Engineering (TE)--IP Explicit Address Exclusion
Your network must support the following Cisco IOS features in order to support IP explicit address exclusion:
- MPLS
- IP Cisco Express Forwarding
- Intermediate System-to-Intermediate System (IS-IS) or Open Shortest Path First (OSPF)
Restrictions for MPLS Traffic Engineering (TE)--IP Explicit Address Exclusion
MPLS TE will accept an IP explicit path comprised of either all excluded addresses configured by the exclude-address command or all included addresses configured by the next-addresscommand, but not a combination of both.
Information About MPLS Traffic Engineering (TE)--IP Explicit Address Exclusion
MPLS Traffic Engineering
MPLS is an Internet Engineering Task Force (IETF)-specified framework that provides for the efficient designation, routing, forwarding, and switching of traffic flows through the network.
Traffic engineering (TE) is the process of adjusting bandwidth allocations to ensure that enough is left for high-priority traffic.
In MPLS TE, the upstream router creates a network tunnel for a particular traffic stream, then fixes the bandwidth available for that tunnel.
Cisco Express Forwarding
Cisco Express Forwarding is an advanced, Layer 3 switching technology inside a router. It defines the fastest method by which a Cisco router forwards packets from ingress to egress interfaces. The ip cef command enables Cisco Express Forwarding globally, and the ip route-cache cefcommand enables Cisco Express Forwarding on an interface.
How to Configure MPLS Traffic Engineering (TE)--IP Explicit Address Exclusion
Configuring IP Explicit Address Exclusion
1. enable
2. configure terminal
3. ip explicit-path {name path-name | identifier number} [enable | disable]
4. exclude-address ip-address
5. exit
6. show ip explicit-path
DETAILED STEPS
Configuring an MPLS Traffic Engineering Tunnel
1. enable
2. configure terminal
3. interface tunnel number
4. ip unnumbered loopback0
5. tunnel destination ip-address
6. tunnel mode mpls traffic-eng
7. tunnel mpls traffic-eng bandwidth bandwidth
8. tunnel mpls traffic-eng path-option number {dynamic | explicit {name path-name | ID path-number}} [lockdown]
9. exit
10. exit
11. show mpls traffic eng tunnels
DETAILED STEPS
Command or Action | Purpose | |||
---|---|---|---|---|
Step 1 | enable Example: Router> enable |
Enables privileged EXEC mode.
|
||
Step 2 | configure terminal Example: Router# configure terminal |
Enters global configuration mode. |
||
Step 3 | interface tunnel number Example: Router(config)# interface tunnel11 |
Configures an interface type and enters interface configuration mode. |
||
Step 4 | ip unnumbered loopback0 Example: Router(config-if)# ip unnumbered loopback0 |
Assigns the tunnel interface an IP address.
|
||
Step 5 | tunnel destination ip-address Example: Router(config-if)# tunnel destination 10.11.11.11 |
Specifies the destination for a tunnel.
|
||
Step 6 | tunnel mode mpls traffic-eng Example: Router(config-if)# tunnel mode mpls traffic-eng |
Sets the tunnel encapsulation mode to MPLS traffic engineering. |
||
Step 7 | tunnel mpls traffic-eng bandwidth bandwidth Example: Router(config-if)# tunnel mpls traffic-eng bandwidth 100 |
Configures the bandwidth for the MPLS traffic engineering tunnel. |
||
Step 8 | tunnel mpls traffic-eng path-option number {dynamic | explicit {name path-name | ID path-number}} [lockdown] Example: Router(config-if)# tunnel mpls traffic-eng path-option 2 dynamic |
Configures the tunnel to use a named IP explicit path or a path dynamically calculated from the traffic engineering topology database.
|
||
Step 9 | exit Example: Router(config-if)# exit |
Exits from interface configuration mode. |
||
Step 10 | exit Example: Router(config)# exit |
Exits to privileged EXEC mode. |
||
Step 11 | show mpls traffic eng tunnels Example: Router# show mpls traffic eng tunnels |
Shows information about tunnels, including the current tunnel path if a tunnel is operational.
|
Configuration Examples for MPLS Traffic Engineering (TE)--IP Explicit Address Exclusion
- Configuring IP Explicit Address Exclusion Example
- Configuring an MPLS Traffic Engineering Tunnel Example
Configuring IP Explicit Address Exclusion Example
The following example shows how to configure an MPLS TE tunnel with two path options: a preferred explicit path with an excluded address and a backup dynamic path.
Configure the IP explicit path named OmitR12, which excludes the router with router ID 10.12.12.12:
ip explicit-path name OmitR12 exclude-address 10.12.12.12 Explicit Path name OmitR12: 1: exclude-address 10.12.12.12 exit
To verify the configuration of the explicit path, use the show ip explicit-path command.
show ip explicit-paths name OmitR12 PATH OmitR12 (loose source route, path complete, generation 3) 1: exclude-address 10.12.12.12
![]() Note |
You must know the router IDs for LSRs (nodes) in the network; in this example, that 10.12.12.12 is a router ID. Otherwise, it will not be apparent whether the specified address is the IP address of a link or a router ID. |
Configuring an MPLS Traffic Engineering Tunnel Example
The following example configures Tunnel11 with its two options, where the preferred path option is the IP explicit path OmitR2:
interface tunne l11 ip unnumbered loopback0 tunnel destination 10.11.11.11 tunnel mode mpls traffic-eng tunnel mpls traffic-eng path-option 1 explicit name OmitR12 tunnel mpls traffic-eng path-option 2 dynamic
![]() Note |
There are additional commands for configuring properties for TE tunnels such as bandwidth and priority. For descriptions of those commands, refer to the Cisco IOS IP Switching Services Configuration Guide . |
Additional References
Related Documents
Standards
Standard |
Title |
---|---|
No new or modified standards are supported by this feature, and support for existing standards has not been modified by this feature. |
-- |
MIBs
MIB |
MIBs Link |
---|---|
No new or modified MIBs are supported by this feature, and support for existing MIBs has not been modified by this feature. |
To locate and download MIBs for selected platforms, Cisco software releases, and feature sets, use Cisco MIB Locator found at the following URL: |
RFCs
RFC |
Title |
---|---|
No new or modified RFCs are supported by this feature, and support for existing RFCs has not been modified by this feature. |
-- |
Technical Assistance
Description |
Link |
---|---|
The Cisco Support and Documentation website provides online resources to download documentation, software, and tools. Use these resources to install and configure the software and to troubleshoot and resolve technical issues with Cisco products and technologies. Access to most tools on the Cisco Support and Documentation website requires a Cisco.com user ID and password. |
Feature Information for MPLS Traffic Engineering (TE)--IP Explicit Address Exclusion
The following table provides release information about the feature or features described in this module. This table 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.
Use Cisco Feature Navigator to find information about platform support and Cisco software image support. To access Cisco Feature Navigator, go to www.cisco.com/go/cfn. An account on Cisco.com is not required.
Feature Name |
Releases |
Feature Configuration Information |
---|---|---|
MPLS Traffic Engineering (TE)--IP Explicit Address Exclusion |
12.0(14)ST 12.2(4)T 12.2(4)T2 12.2(14)S 12.0(32)S 12.2(28)SB |
The MPLS Traffic Engineering (TE)--IP Explicit Address Exclusion feature provides a means to exclude a link or node from the path for Multiprotocol Label Switching (MPLS) TE label switched path (LSP). The following command was introduced by this feature: exclude-address. In 12.0(14)ST, this feature was introduced. In 12.2(4)T, this feature was integrated into Release 12.2(4)T. In 12.2(4)T2, this feature was integrated into Release 12.2(4)T2. In 12.2(14)S, this feature was integrated into Release 12.2(14)S. In 12.0(32)S, this feature was integrated into Release 12.0(32)S. In 12.2(28)SB, this feature was integrated into Release 12.2(28)SB. |
Glossary
CEF --Cisco express forwarding. A means for accelerating the forwarding of packets within a router, by storing route lookup information in several data structures instead of in a route cache.
IP explicit path --A list of IP addresses, each representing a node or link in the explicit path.
link --Network communications channel consisting of a circuit or transmission path and all related equipment between a sender and a receiver. Sometimes referred to as a line or a transmission link.
MPLS --Multiprotocol Label Switching. Switching method that forwards IP traffic using a label. This label instructs the routers and the switches in the network where to forward the packets based on preestablished IP routing information.
node --Endpoint of a network connection or a junction common to two or more lines in a network. Nodes can be interconnected by links, and serve as control points in the network.