- MPLS Traffic Engineering and Enhancements
- MPLS Traffic Engineering-Configurable Path Calculation Metric for Tunnels
- MPLS Traffic Engineering-Scalability Enhancements
- MPLS Traffic Engineering-LSP Attributes
- 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 Class-based Tunnel Selection
- MPLS Traffic Engineering Interarea Tunnels
- MPLS Traffic Engineering-Automatic Bandwidth Adjustment for TE Tunnels
- MPLS Traffic Engineering Tunnel Source
- Finding Feature Information
- Prerequisites for MPLS Traffic Engineering--Verbatim Path Support
- Restrictions for MPLS Traffic Engineering--Verbatim Path Support
- Information About MPLS Traffic Engineering--Verbatim Path Support
- How to Configure MPLS Traffic Engineering--Verbatim Path Support
- Configuration Example for MPLS Traffic Engineering: Verbatim Path Support
- Additional References
- Feature Information for MPLS Traffic Engineering: Verbatim Path Support
- Glossary
MPLS Traffic Engineering: Verbatim Path Support
The MPLS Traffic Engineering: Verbatim Path Support feature allows network nodes to support Resource Reservation Protocol (RSVP) extensions without supporting Interior Gateway Protocol (IGP) extensions for traffic engineering ( TE), thereby bypassing the topology database verification process.
- Finding Feature Information
- Prerequisites for MPLS Traffic Engineering--Verbatim Path Support
- Restrictions for MPLS Traffic Engineering--Verbatim Path Support
- Information About MPLS Traffic Engineering--Verbatim Path Support
- How to Configure MPLS Traffic Engineering--Verbatim Path Support
- Configuration Example for MPLS Traffic Engineering: Verbatim Path Support
- Additional References
- Feature Information for MPLS Traffic Engineering: Verbatim Path Support
- Glossary
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 Table at the end of this document.
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--Verbatim Path Support
Restrictions for MPLS Traffic Engineering--Verbatim Path Support
Information About MPLS Traffic Engineering--Verbatim Path Support
MPLS TE LSPs usually require that all the nodes in the network are TE aware, meaning they have IGP extensions to TE in place. However, some network administrators want the ability to build TE LSPs to traverse nodes that do not support IGP extensions to TE, but that do support RSVP extensions to TE.
Verbatim LSPs are helpful when all or some of the intermediate nodes in a network do not support IGP extensions for TE.
When this feature is enabled, the IP explicit path is not checked against the TE topology database. Because the TE topology database is not verified, a Path message with IP explicit path information is routed using the shortest path first (SPF) algorithm for IP routing.
How to Configure MPLS Traffic Engineering--Verbatim Path Support
- Configuring MPLS Traffic Engineering--Verbatim Path Support
- Verifying Verbatim LSPs for MPLS TE Tunnels
Configuring MPLS Traffic Engineering--Verbatim Path Support
DETAILED STEPS
Verifying Verbatim LSPs for MPLS TE Tunnels
DETAILED STEPS
Command or Action | Purpose | |
---|---|---|
|
Example: Router> enable |
Enables privileged EXEC mode. |
|
Example: Router# show mpls traffic-eng tunnels tunnel1 |
Displays information about tunnels including those configured with an explicit path option using verbatim. |
|
Example: Router# disable |
(Optional) Exits to user EXEC mode. |
Configuration Example for MPLS Traffic Engineering: Verbatim Path Support
Configuring MPLS Traffic Engineering: Verbatim Path Support
The following example shows a tunnel that has been configured with an explicit path option using verbatim:
interface tunnel 1 ip unnumbered loopback 1 tunnel destination 10.10.100.100 tunnel mode mpls traffic-eng tunnel mpls traffic-eng bandwidth 1000 tunnel mpls traffic-eng autoroute announce tunnel mpls traffic-eng priority 1 1 tunnel mpls traffic-eng path-option 1 explicit name path1 verbatim
Additional References
Related Documents
Related Topic |
Document Title |
---|---|
MPLS Label Distribution Protocol |
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 IOS 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 release. |
-- |
Technical Assistance
Description |
Link |
---|---|
The Cisco Support website provides extensive online resources, including documentation and tools for troubleshooting and resolving technical issues with Cisco products and technologies. To receive security and technical information about your products, you can subscribe to various services, such as the Product Alert Tool (accessed from Field Notices), the Cisco Technical Services Newsletter, and Really Simple Syndication (RSS) Feeds. Access to most tools on the Cisco Support website requires a Cisco.com user ID and password. |
Feature Information for MPLS Traffic Engineering: Verbatim Path Support
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.
Table 1 | Feature Information for MPLS Traffic Engineering: Verbatim Path Support |
Feature Name |
Releases |
Feature Information |
---|---|---|
MPLS Traffic Engineering: Verbatim Path Support |
12.0(26)S 12.2(33)SRA 12.2(33)SXH 12.4(20)T |
The MPLS Traffic Engineering: Verbatim Path Support feature allows network nodes to support Resource Reservation Protocol (RSVP) extensions without supporting Interior Gateway Protocol (IGP) extensions for traffic engineering ( TE), thereby bypassing the topology database verification process. In 12.0(26)S, this feature was introduced. This feature was integrated into Cisco IOS Release 12.2(33)SRA. This feature was integrated into Cisco IOS Release 12.2(33)SXH. This feature was integrated into Cisco IOS Release 12.4(20)T. The following commands were introduced or modified: show mpls traffic-eng tunnels, tunnel mpls traffic-eng path option. |
Glossary
Fast Reroute --Procedures that enable temporary routing around a failed link or node while a new label-switched path (LSP) is being established at the head end.
headend --The router that originates and maintains a given label-switched path (LSP) . This is the first router in the LSP's path.
IGP --Interior Gateway Protocol. Internet protocol used to exchange routing information within an autonomous system. Examples of common Internet IGPs include Interior Gateway Routing Protocol (IGRP), Open Shortest Path First (OSPF), and Routing Information protocol (RIP).
LSP --label-switched path. A configured connection between two routers, in which label switching is used to carry the packets. The purpose of an LSP is to carry data packets.
LSR --label switching router. A device that forwards Multiprotocol Label Switching (MPLS) packets based on the value of a fixed-length label encapsulated in each packet.
merge point --The backup tunnel's tail.
MPLS --Multiprotocol Label Switching. A method for forwarding packets (frames) through a network. It enables routers at the edge of a network to apply labels to packets (frames). ATM switches or existing routers in the network core can switch packets according to the labels with minimal lookup overhead.
PLR --point of local repair. The head-end of the backup tunnel.
RSVP --Resource Reservation Protocol. A protocol that supports the reservation of resources across an IP network. Applications running on IP end systems can use RSVP to indicate to other nodes the nature (bandwidth, jitter, maximum burst, and so on) of the packet streams they want to receive.
SPF --shortest path first. Routing algorithm that iterates on length of path to determine a shortest-path spanning tree. Commonly used in link-state routing algorithms. Sometimes called Dijkstra's algorithm.
tailend --The router upon which an label-switched path (LSP) is terminated. This is the last router in the LSP's path.
traffic engineering --The techniques and processes used to cause routed traffic to travel through the network on a path other than the one that would have been chosen if standard routing methods had been used.
tunnel --A secure communications path between two peers, such as routers.
Cisco and the Cisco logo are trademarks or registered trademarks of Cisco and/or its affiliates in the U.S. and other countries. To view a list of Cisco trademarks, go to this URL: www.cisco.com/go/trademarks. Third-party trademarks mentioned are the property of their respective owners. The use of the word partner does not imply a partnership relationship between Cisco and any other company. (1110R)
Any Internet Protocol (IP) addresses and phone numbers used in this document are not intended to be actual addresses and phone numbers. Any examples, command display output, network topology diagrams, and other figures included in the document are shown for illustrative purposes only. Any use of actual IP addresses or phone numbers in illustrative content is unintentional and coincidental.