Home > Articles > Networking

Configuration of Frame Mode MPLS

By David Hucaby and Stephen McQuerry
Jul 28, 2010

📄 Contents

␡

10-1 Configuring Basic MPLS
10-2 MPLS Traffic Engineering
10-3 MPLS Virtual Private Networks (VPN)
References

⎙ Print

< Back Page 2 of 4 Next >

This chapter is from the book 

Cisco Router Configuration Handbook, 2nd Edition

Learn More Buy

10-2 MPLS Traffic Engineering

Service providers can use traffic engineering on MPLS-enabled routers to route a customer's network traffic based on throughput and delay. Traffic engineering (TE) tunnels are created for label switch paths (LSP) using the RSVP. A tunnel interface represents the head of the LSP and is configured with a set of resource requirements (for example, bandwidth requirements, media requirements, and priority):

Topology and resource information is flooded using either IS-IS or OSPF. Traffic engineering extensions are added to the routing process to enable MPLS traffic engineering.
IS-IS routers must be configured to use the new style of IS-IS metric to support new type, length, and value objects (TLV) for traffic engineering. The new TLVs are 22 and 135 and have sub-TLVs that enable you to add properties to a link for purposes of traffic engineering.
The Shortest Path First (SPF) algorithm used by IS-IS and OSPF chooses the tunnel interface before choosing an alternative path over main interfaces.
Multiple tunnels might be configured to load-share traffic.

Configuration

(Required) Allow CEF and LDP as explained in Section 10-1.
(Required) Allow the MPLS traffic engineering feature:
```
(global) mpls traffic-eng tunnels
      
```
Before you can allow interfaces for traffic engineering, you must first allow traffic engineering globally.
(Required) Allow traffic engineering on interfaces:
```
(interface) mpls traffic-eng tunnels
      
```
When you have allowed MPLS traffic engineering globally, you can then allow it on interfaces. Configuring this command causes its resource information to be flooded into the appropriate interior gateway protocol (IGP) link-state database (either IS-IS or OSPF). This command also enables the interface to accept traffic engineering tunnel signaling requests.
(Required when using CAC with RSVP) Allow RSVP on an interface and specify the amount of bandwidth to reserve:
```
(interface) ip rsvp bandwidth [bandwidth]
```
This command enables the resource reservation protocol (RSVP) on the interface. You must enter this command if you use Call Admission Control (CAC) with RSVP. If you do not specify a bandwidth value, a default bandwidth value of 75 percent will be used.
Configure OSPF for MPLS traffic engineering.
1. (Required) Allow traffic engineering for each area:
```
(router) mpls traffic-eng area area-number
            
```
2. (Required) Set the traffic engineering router identifier:
```
(router) mpls traffic-eng router-id interface
            
```
  Unlike OSPF and MPLS router IDs, MPLS traffic engineering will not automatically set a router ID. The router ID will be the IP address on the interface you enter in this command. It is recommended that you use a loopback interface and that it match that of the interface used for the OSPF process router ID. The router ID is flooded to other routers and is used as the tunnel destination IP address.
Configure IS-IS for MPLS traffic engineering.
1. (Required) Allow traffic engineering:
```
(router) mpls traffic-eng {level-1 | level-2}
```
  You can choose to flood traffic engineering into IS-IS level-1 or level-2.
2. (Required) Set the traffic engineering router identifier:
```
(router) mpls traffic-eng router-id interface
            
```
3. (Required) Configure the router to generate and accept new-style TLVs:
```
(router)metric-style wide
            
```
  The original metric used by IS-IS does not support traffic engineering. You must enter this command to support the new type, length, value objects (TLV), and sub-TLVs used for traffic engineering.
  
  NOTE
  
  See RFC 3784, "Intermediate System to Intermediate System (IS-IS) Extensions for Traffic Engineering (TE)," for more on the new TLVs and sub-TLVs used for traffic engineering.
Create a tunnel interface:
```
(global) interface tunnel number
      
```
This command creates a new tunnel interface.
Assign an IP address to the tunnel interface:
```
(interface) ip unnumbered interface
      
```
Tunnel interfaces should be unnumbered because the tunnel interface represents a unidirectional link. It is recommended that you use a loopback interface for the interface value.
Set the tunnel destination IP address:
```
(interface) tunnel destination ip-address
      
```
The tunnel destination IP address should be set to the far-end router's IP address that was configured with the mpls traffic-eng router-id command under the IS-IS or OSPF router process.
Set the tunnel type to MPLS traffic engineering:
```
(interface) tunnel mode mpls traffic-eng
      
```
There are many types of tunnel interfaces (for example, GRE, 6to4, and so on), so you must manually set the interface type.
Configure the bandwidth for the tunnel:
```
(interface) tunnel mpls traffic-eng bandwidth bandwidth
      
```
The range of valid bandwidth values is 1–4294967295.
Configure a dynamic or explicit path option:
```
(interface) tunnel mpls traffic-eng path-option number { dynamic | explicit
{name path-name | identifier path-number}}
```
You can configure the tunnel to be dynamic, meaning the router will rely on the IS-IS or OSPF routing information to determine the best path for the tunnel. You can also manually define the path using the explicit option. If you choose to explicitly map out the tunnel path, you need to enter either a name or identifier to reference the configured path. The steps for configuring an explicit path follow:
1. Configure the explicit path (if applicable).
  - Enter IP explicit path configuration mode:
```
(global) ip explicit-path {name path-name | identifier path-number}
```
    The path-name or path-number should match what you configured with the tunnel mpls traffic-eng path-option command earlier.
  - Enter the IP addresses for each hop:
```
(explicit-path-configuration) next-address [loose | strict] ip-address
                  
```
  Enter the next IP addresses one at a time for the path you want the tunneled traffic to take. The loose and strict keywords are optional. The loose option tells the router that the previous address in the explicit path does not need to be directly connected to the next address. The router is therefore free to determine the path from the previous address to the next. The strict option tells the router that the previous address must be directly connected to the next address.
  
  NOTE
  
  The next IP address can be either the link (interface) IP address of the next-hop router or the MPLS node address (set with the mpls traffic-eng router-id interface router process command). However, for Cisco IOS releases 12.4(24)T and earlier, you cannot use a link address as the first hop followed by node addresses for subsequent hops. You do not have this restriction for releases after 12.4(24).
Allow the IGP (that is, IS-IS or OSPF) to use the tunnel when performing its SPF route calculation:
```
(interface) tunnel mpls traffic-eng autoroute announce
      
```
The only way to forward traffic onto a tunnel is to allow this feature or to configure a static route to the interface.
(Optional) Manually configure the metric used by the SPF calculation:
```
(interface) tunnel mpls traffic-eng autoroute metric absolute metric
      
```
You can allow the IGP to automatically assign the metric for the tunnel or manually configure the metric value using this command.

Example

Figure 10-2 is used for this example. RouterA is configured for MPLS traffic engineering. An explicit tunnel is configured with a backup dynamic tunnel. The tunnel is configured with a metric of 10 and announced to IS-IS so that IS-IS will consider the tunnel when it performs its SPF calculation.

Figure 10-2 MPLS Traffic Engineering Example

hostname RouterA
!
ip cef
mpls ip
mpls ldp router-id 1.1.1.1
mpls traffic-eng tunnels
!
interface fastethernet0/0
 ip address 10.1.1.5 255.255.255.252
 mpls ip
 ip router isis
 mpls traffic-eng tunnels
 ip rsvp bandwidth 512
!
interface loopback 0
 ip address 1.1.1.1 255.255.255.255
 ip router isis
!
router isis
 net 49.0001.0000.0000.0001.00
 is-type level-1
 metric-style wide
 mpls traffic-eng router-id loopback 0
 mpls traffic-eng level-1
!
interface tunnel 0
 ip unnumbered loopback 0
 tunnel destination 4.4.4.4
 tunnel mpls traffic-eng bandwidth 512
 tunnel mode mpls traffic-eng
 tunnel mpls traffic-eng autoroute announce
 tunnel mpls traffic-eng autoroute metric absolute 10
 tunnel mpls traffic-eng path-option 1 explicit name TUNNEL
 tunnel mpls traffic-eng path-option 2 dynamic
!
ip explicit-path name TUNNEL
 next-address 2.2.2.2
 next-address 4.4.4.4

< Back Page 2 of 4 Next >

🔖 Save To Your Account

InformIT Promotional Mailings & Special Offers

I would like to receive exclusive offers and hear about products from InformIT and its family of brands. I can unsubscribe at any time.

Privacy Notice

Overview

Pearson Education, Inc., 221 River Street, Hoboken, New Jersey 07030, (Pearson) presents this site to provide information about products and services that can be purchased through this site.

This privacy notice provides an overview of our commitment to privacy and describes how we collect, protect, use and share personal information collected through this site. Please note that other Pearson websites and online products and services have their own separate privacy policies.

Collection and Use of Information

To conduct business and deliver products and services, Pearson collects and uses personal information in several ways in connection with this site, including:

Questions and Inquiries

For inquiries and questions, we collect the inquiry or question, together with name, contact details (email address, phone number and mailing address) and any other additional information voluntarily submitted to us through a Contact Us form or an email. We use this information to address the inquiry and respond to the question.

Online Store

For orders and purchases placed through our online store on this site, we collect order details, name, institution name and address (if applicable), email address, phone number, shipping and billing addresses, credit/debit card information, shipping options and any instructions. We use this information to complete transactions, fulfill orders, communicate with individuals placing orders or visiting the online store, and for related purposes.

Surveys

Pearson may offer opportunities to provide feedback or participate in surveys, including surveys evaluating Pearson products, services or sites. Participation is voluntary. Pearson collects information requested in the survey questions and uses the information to evaluate, support, maintain and improve products, services or sites, develop new products and services, conduct educational research and for other purposes specified in the survey.

Contests and Drawings

Occasionally, we may sponsor a contest or drawing. Participation is optional. Pearson collects name, contact information and other information specified on the entry form for the contest or drawing to conduct the contest or drawing. Pearson may collect additional personal information from the winners of a contest or drawing in order to award the prize and for tax reporting purposes, as required by law.

Newsletters

If you have elected to receive email newsletters or promotional mailings and special offers but want to unsubscribe, simply email information@informit.com.

Service Announcements

On rare occasions it is necessary to send out a strictly service related announcement. For instance, if our service is temporarily suspended for maintenance we might send users an email. Generally, users may not opt-out of these communications, though they can deactivate their account information. However, these communications are not promotional in nature.

Customer Service

We communicate with users on a regular basis to provide requested services and in regard to issues relating to their account we reply via email or phone in accordance with the users' wishes when a user submits their information through our Contact Us form.

Other Collection and Use of Information

Application and System Logs

Pearson automatically collects log data to help ensure the delivery, availability and security of this site. Log data may include technical information about how a user or visitor connected to this site, such as browser type, type of computer/device, operating system, internet service provider and IP address. We use this information for support purposes and to monitor the health of the site, identify problems, improve service, detect unauthorized access and fraudulent activity, prevent and respond to security incidents and appropriately scale computing resources.

Web Analytics

Pearson may use third party web trend analytical services, including Google Analytics, to collect visitor information, such as IP addresses, browser types, referring pages, pages visited and time spent on a particular site. While these analytical services collect and report information on an anonymous basis, they may use cookies to gather web trend information. The information gathered may enable Pearson (but not the third party web trend services) to link information with application and system log data. Pearson uses this information for system administration and to identify problems, improve service, detect unauthorized access and fraudulent activity, prevent and respond to security incidents, appropriately scale computing resources and otherwise support and deliver this site and its services.

Cookies and Related Technologies

This site uses cookies and similar technologies to personalize content, measure traffic patterns, control security, track use and access of information on this site, and provide interest-based messages and advertising. Users can manage and block the use of cookies through their browser. Disabling or blocking certain cookies may limit the functionality of this site.

Do Not Track

This site currently does not respond to Do Not Track signals.

Security

Pearson uses appropriate physical, administrative and technical security measures to protect personal information from unauthorized access, use and disclosure.

Children

This site is not directed to children under the age of 13.

Marketing

Pearson may send or direct marketing communications to users, provided that

Pearson will not use personal information collected or processed as a K-12 school service provider for the purpose of directed or targeted advertising.
Such marketing is consistent with applicable law and Pearson's legal obligations.
Pearson will not knowingly direct or send marketing communications to an individual who has expressed a preference not to receive marketing.
Where required by applicable law, express or implied consent to marketing exists and has not been withdrawn.

Pearson may provide personal information to a third party service provider on a restricted basis to provide marketing solely on behalf of Pearson or an affiliate or customer for whom Pearson is a service provider. Marketing preferences may be changed at any time.

Correcting/Updating Personal Information

If a user's personally identifiable information changes (such as your postal address or email address), we provide a way to correct or update that user's personal data provided to us. This can be done on the Account page. If a user no longer desires our service and desires to delete his or her account, please contact us at customer-service@informit.com and we will process the deletion of a user's account.

Choice/Opt-out

Users can always make an informed choice as to whether they should proceed with certain services offered by InformIT. If you choose to remove yourself from our mailing list(s) simply visit the following page and uncheck any communication you no longer want to receive: www.informit.com/u.aspx.

Sale of Personal Information

Pearson does not rent or sell personal information in exchange for any payment of money.

While Pearson does not sell personal information, as defined in Nevada law, Nevada residents may email a request for no sale of their personal information to NevadaDesignatedRequest@pearson.com.

Supplemental Privacy Statement for California Residents

California residents should read our Supplemental privacy statement for California residents in conjunction with this Privacy Notice. The Supplemental privacy statement for California residents explains Pearson's commitment to comply with California law and applies to personal information of California residents collected in connection with this site and the Services.

Sharing and Disclosure

Pearson may disclose personal information, as follows:

As required by law.
With the consent of the individual (or their parent, if the individual is a minor)
In response to a subpoena, court order or legal process, to the extent permitted or required by law
To protect the security and safety of individuals, data, assets and systems, consistent with applicable law
In connection the sale, joint venture or other transfer of some or all of its company or assets, subject to the provisions of this Privacy Notice
To investigate or address actual or suspected fraud or other illegal activities
To exercise its legal rights, including enforcement of the Terms of Use for this site or another contract
To affiliated Pearson companies and other companies and organizations who perform work for Pearson and are obligated to protect the privacy of personal information consistent with this Privacy Notice
To a school, organization, company or government agency, where Pearson collects or processes the personal information in a school setting or on behalf of such organization, company or government agency.

Links

This web site contains links to other sites. Please be aware that we are not responsible for the privacy practices of such other sites. We encourage our users to be aware when they leave our site and to read the privacy statements of each and every web site that collects Personal Information. This privacy statement applies solely to information collected by this web site.

Requests and Contact

Please contact us about this Privacy Notice or if you have any requests or questions relating to the privacy of your personal information.

Changes to this Privacy Notice

We may revise this Privacy Notice through an updated posting. We will identify the effective date of the revision in the posting. Often, updates are made to provide greater clarity or to comply with changes in regulatory requirements. If the updates involve material changes to the collection, protection, use or disclosure of Personal Information, Pearson will provide notice of the change through a conspicuous notice on this site or other appropriate way. Continued use of the site after the effective date of a posted revision evidences acceptance. Please contact us if you have questions or concerns about the Privacy Notice or any objection to any revisions.

Last Update: November 17, 2020

Email Address