Avaya MPLS User Manual
Configuring MPLS Services
BayRS Version 13.20
Site Manager Software Version 7.20
BCC Version 4.20
Part No. 305754-A Rev 00
March 1999
Bay Networ ks, Inc.
4401 Great America Parkway
Santa Clara, CA 95054
Copyright © 1999 Bay Networks, Inc.
All rights reserved. Printed in the USA. March 1999.
The information in this document is subject to change without notice. The statements, configurations, technical data,
and recommendations in this document are believed to be accurate and reliable, but are presented without express or
implied warranty. Users must take full responsibility fo r th eir a pplic a tio ns of any products specified in this document.
The information in this document is proprietary to Bay Networks, Inc.
The software described in this document is furnished under a license agreement and may only be used in accordance
with the terms of that licen se. A summary of the Software License is included in this document.
Trademarks
BCN, BLN, BN, FRE, and Bay Networks are registered trademarks and BayRS, BCC, and System 5000 are
trademarks of Bay Networks, Inc.
All other trademarks and registered trademarks are t he property of their respective owners.
Restricted Rights Legend
Use, duplication, or disclosure by the United States Government is subject to restrictions as set forth in subparagraph
(c)(1)(ii) of the Rights in Technical Data and Computer So ftware clause at DFARS 252.227-7013.
Notwithstanding any other license agreement that may pertain to, or accompany the delivery of, this computer
software, the rights of the United States Government regarding its use, reproduction, and disclosure are as set forth in
the Commercial Computer Software-Restricted Rights cl ause at FAR 52.227-19.
Statement of Conditions
In the interest of improving internal design, operational function, and/or reliability, Bay Networks, Inc. reserves the
right to make changes to the pr oducts described in this document without notice.
Bay Networks, Inc. does not assume any liability that may occur du e to the use or application of the product(s) or
circuit layout(s) described herein.
Portions of the code in this software product may be Copyright © 1988, Regents of the University of California. All
rights reserved. Redistribution and use in source and binary forms of such portions are permitted, provided th at the
above copyright notice and this paragraph are duplicated in all such forms and that any documentation, advertising
materials, and other materials related to such distribution and use acknowledge that su ch portions of the software were
developed by the University of California, Berkeley. The name of the University may not be used to endorse or
promote products derived from such portions of the software without specific prior written permission.
SUCH PORTIONS OF THE SOFTWARE ARE PROVIDED “AS IS” AND WITHOUT ANY EXPRESS OR
IMPLIED WARRANTIES, INCLUDING, WITHOUT LIMITATION, THE IMPLIED WARRANTIES OF
MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE.
In addition, the program and information contained herein are licensed only pursuant to a license agreement that
contains restrictions on use and disclosure (that may incorporate by reference certain limitations and notices imposed
by third parties).
ii
305754-A Rev 00
Bay Networks, Inc. Software License Agreement
NOTICE: Please carefully read this license agre ement before copying or using the accompanying software or
installing the hardware unit with pre-enabled software (each of which is referred to as “Software” in this Agreement).
BY COPYING OR USING THE SOFTWARE, YOU ACCEPT ALL OF THE TERMS AND CONDITIONS OF
THIS LICENSE AGREEMENT. THE TERMS EXPRESSED IN THIS AGREEMENT ARE THE ONLY TERMS
UNDER WHICH BAY NETWORKS WILL PERMIT YOU TO USE THE SOFTWARE. If you do not accept these
terms and conditions, return the product, unused and in the original shipping container, within 30 days of purchase to
obtain a credit for the full purchase price.
1. License Grant. Bay Networks, Inc. (“Bay Networks”) grants the end user of the Software (“Licensee”) a personal,
nonexclusive, nontransferable license: a) to use the Software either on a single computer or, if applicable, on a single
authorized device identified by host ID, for which it was originally acquired; b) to copy the Software solely for backup
purposes in support of authorized use of the Software; and c) to use and copy the associated user manual solely i n
support of authorized use of the Software by Licensee. This license applies to the Software only and does not extend
to Bay Networks Agent software or other Bay Networks software pro ducts. Bay Networks Agent software or other
Bay Networks software products are licensed for use under the terms of the applicable Bay Networks, Inc. Software
License Agreement that accomp anies such software and upon payment by the end user of the applicable license fees
for such software.
2. Restrictions on use; reservation of rights. The Software and user manuals are protected under copyright laws.
Bay Networks and/or it s licensors retain all title and ownership in both the Software and user manuals, including any
revisions made by Bay Networks or its licensors. The copyright notice must be reproduced and included with any
copy of any portion of the Software or user manuals. Licensee may not modify, translate, decompile, disassemble, use
for any competitiv e analysis, re v erse engineer , distrib ute, or create deriv ati ve works from the Softwa re or user manuals
or any copy, in whole or in part. Except as expressly provided in thi s Agreement, Licensee may not copy or transfer
the Software or user manuals, in whole or in part. The Soft ware and user manuals embody Bay Networks’ and its
licensors’ confidential and proprietary intellectual property. Licensee shall not sublicense, assign, or otherwise
disclose to any third party the Software, or any information about the operation, design, performance, or
implementation of the Software and user manuals that is confidential to Bay Networks and its licensors; however,
Licensee may grant permission to its consultants, subcontractors, a nd agents to use the Softw are at Licensee’s facility ,
provided they have agreed to use the Software only in accordance with the terms of this license.
3. Limited warranty. Bay Netw o r ks wa r ra nts ea c h item of So ft ware, as delivered by Bay Networks and properly
installed and operated on Bay Networks hardware or other equipment it is originally licensed for, to function
substantially as described in its accompanying user m anual during its warranty period , which begins on the date
Software is first shipped to Licensee. If an y item of S oftware f ails to so function d uring its w arranty period, as the sole
remedy Bay Networks will at its discretion provide a suitable fix, patch, or workaround for the problem that may be
included in a future Software release. Bay Network s fur ther w arra nts to Licen see that the medi a on which the
Software is provided will be free from defec ts in materials and wo rkman ship under no rmal use for a peri od of 90 da ys
from the date Software is first shipped to Licensee. Bay Networks will replace defective media at no cha rge if it is
returned to Bay Netw orks during the warran ty perio d alon g with proof of the date of shipment . This war ranty do es not
apply if the media has been dam aged as a resul t of acci dent, misuse , or ab use. The Licen see assumes all re sponsibilit y
for selection of the Software to achieve Licensee’s intended results and for the installation, use, and results obtained
from the Software. Bay Networks does not warrant a) that the functions contained in the software will meet the
Licensee’ s requireme nts, b) that the Software will operate in the hardware or software combinations tha t the L icens ee
may select, c) that the operation of the Softw a re will be uninterru pte d or error free, or d) that all defec ts in the
operation of the Software will be corrected. Bay Networks is not obligated to remedy any Software defect that cannot
be reproduced with the latest Software release. These warranties do not apply to the So ftw are if i t has been (i) altered,
except by Bay Networks or in accordance with its instructions; (ii) used in conjunction with another vendor’s product,
resulting in the defect; or (iii) damaged by improper environment, abuse, misuse, accident, or negligence. THE
FOREGOING WARRANTIES AND LIMITATIONS ARE EXCLUSIVE REMEDIES AND ARE IN LIEU OF ALL
OTHER WARRANTIES EXPRESS OR IMPLIED, INCLUDING W ITHOUT LIMITATION ANY WARRANTY OF
MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE. Licensee is responsible for the security of
305754-A Rev 00
iii
its own data and information and for maintaining adequate procedures apart from the Software to reconstruct los t or
altered files, data, or programs.
4. Limitation of liability. IN NO EVENT WILL BAY NETWORKS OR ITS LICENSORS BE LIABLE FOR ANY
COST OF SUBSTITUTE PROCUREMENT; SPECIAL, INDIRECT, INCIDENTAL, OR CONSEQUENTIAL
DAMAGES; OR ANY DAMAGES RESULTING FROM INACCURATE OR LOST DATA OR LOSS OF USE OR
PROFITS ARISING OUT OF OR IN CONNECTION WITH THE PERFORMANCE OF THE SOFTWARE, EVEN
IF BAY NETWORKS HAS BEEN ADVISED OF THE POSSIBILITY OF SUCH DAMAGES. IN NO EVENT
SHALL THE LIABILITY OF BAY NETWORKS RELATING TO THE SOFTWARE OR THIS AGREEMENT
EXCEED THE PRICE PAID TO BAY NETWORKS FOR THE SOFTWARE LICENSE.
5. Government Licensees. This provision applies to a ll Softwa re and docum entation acquired d irectly or i ndirectly by
or on behalf of the United States Government. The Software and documentation are commercial products, licensed on
the open market at market prices, and were developed entirely at private expense and without th e use of any U.S.
Government funds. The license to the U.S. Government is granted only with restricted rights, and use, duplication, or
disclosure by the U.S. Government is subject to the restrictions set forth in subparagraph (c)(1) of the Commercial
Computer Software––Restricte d Rig hts cla u se o f FAR 52.227-19 and the limita tio ns set o ut in this license for civilian
agencies, and subparagraph (c)(1)(ii) of the Rights in Technical Data and Computer Software clause of DFARS
252.227-7013, for agencies of t he Department of Defense or their successors, whichever is applicable.
6. Use of Software in the European Community. This provision applies to all Software acquired for use within the
European Community. If Licensee uses the Software within a country in the European Community, the Software
Directive enacted by the Council of European Communities Directive dated 14 Ma y, 1991, will apply to the
examination of th e Software to facilitate interoperability. Licensee agrees to notify Ba y Networks of any such
intended examination of the Software and may procure support and assistance from Bay Networks.
7. Term and termination. This license is effective until terminated; however, all of the restrictions with respect to
Bay Networks’ copyright in the Software and user manuals will cease being effective at the date of expiration of the
Bay Networks copyright; those restrictions relating to use and disclosure of Bay Networks’ confidential information
shall continue in effect. Licensee may terminate this license at any time. The license will automatically terminate if
Licensee fails to comply with any of the terms and conditions of the license. Upon termination for any reason,
Licensee will immediately destroy or return to Bay Networks the Software, user manuals, and all copies. Bay
Networks is not liable to Licensee for damages in any form solely by reason of the termination of this license.
8. Export and Re-export. Licensee agrees not to export, directly or indirectly, t he S oft ware or re lated technical data
or information without first obtaining any required export licenses or other governmental approvals. Without limiting
the foregoing, Licensee, on behalf of itself and its subsidiaries and affiliates, agrees that it will not, without first
obtaining all export licenses and approvals required by the U.S. Government: (i) export, re-export, transfer, or divert
any such Software or technical data, or any direct product thereof, to any country to which such exports or re-exports
are restricte d or em b argoed under United States ex po r t con t rol laws and re gulations, or to any national or resident of
such restricted or embargoed countries; or (ii) provide the Software or related technical data or information to any
military end user or for any military end use, including the design, development, or production of any chemical,
nuclear, or biological weapons.
9. General. If any provision of this Agreement is held to be invalid or unenf orceable by a court of competent
jurisdiction, the remainder of the provisions of this Agreement shall remain in full force and effect. This Agreement
will be governed by the laws of the state of California.
Should you have any questions concerning this Agreement, contact Bay Networks, Inc., 4401 Great America Parkway,
P.O. Box 58185, Santa Clara, California 95054-8185.
LICENSEE ACKNOWLEDGES THAT LICENSEE HAS READ THIS AGREEMENT, UNDERSTANDS IT, AND
AGREES TO BE BOUND BY ITS TERMS AND CONDITIONS. LICENSEE FURTHER AGREES THAT THIS
AGREEMENT IS THE ENTIRE AND EXCLUSIVE AGREEMENT BETWEEN BAY NETWORKS AND
LICENSEE, WHICH SUPERSEDES ALL PRIOR ORAL AND WRITTEN AGREEMENTS AND
COMMUNICATIONS BETWEEN THE PARTIES PERTAINING TO THE SUBJECT MATTER OF THIS
AGREEMENT. NO DIFFERENT OR ADDITIONAL TERMS WILL BE ENFORCEABLE AGAINST B AY
NETWORKS UNLESS BAY NETWORKS GIVES ITS EXPRESS WRITTEN CONSENT, INCLUDING AN
EXPRESS WAIVER OF THE TERMS OF THIS AGREEMENT.
iv
305754-A Rev 00
Contents
Preface
Before You Begin .............................................................................................................. xi
Text Conventions ..............................................................................................................xii
Acronyms ........................... .......................... .......................... ......................... .................xiv
Bay Networks Technical Publications .............................................................................. xv
How to Get Help .............................................................................................................. xv
Chapter 1
Understanding MPLS
MPLS General Information .............................................................................................1-2
MPLS System Overview .................................................................................................1-3
Label Distribution Entity ...........................................................................................1-4
MPLS Label Management ........................................................................................1-4
Forwarding ...............................................................................................................1-4
The MPLS Network ........................................................................................................1-5
Label Switching Router ............................................................................................1-6
Label Edge Router ...................................................................................................1-6
Supported Protocols .......................................................................................................1-7
For More Information ......................................................................................................1-7
Where to Go Next ...........................................................................................................1-7
Chapter 2
Starting MPLS
Creating an ATM Circuit ..................................................................................................2-2
Adding an LDP Session Record ...............................................................................2-2
Adding Protocols to an LDP Session Record .................................................................2-4
Adding Protocols to the LDP Session ......................................................................2-4
Adding Protocols to an Existing Record ...................................................................2-5
Adding IP Adjacent Hosts ...............................................................................................2-6
Defining IP Static Routes for LDP ...................................................................................2-8
305754-A Rev 00
v
Enabling MLM .................................................................................................................2-9
Configuring TCP ...........................................................................................................2-10
Enabling TCP .........................................................................................................2-10
Increasing the TCP Window Size ....................................................................2-11
Where to Go Next .........................................................................................................2-11
Chapter 3
Customizing the MPLS Configuration
Customizing LDP Parameters ........................................................................................3-2
Disabling and Reenabling LDP .......................... ...... ....... ...... ...... ....... ...... ....... ...... ...3-2
Changing the Local IP Address ................................................................................3-3
Specifying a Local TCP Port ....................................................................................3-4
Specifying a Remote IP Address .............................................................................3-5
Specifying a Remote TCP Port ................................................................................3-6
Specifying the Routes Configuration Mode ..............................................................3-7
Specifying a Hold Time ............................................................................................3-8
Specifying a Protocol for MPLS Route Configuration ...............................................3-9
Enabling and Disabling Aggregation ......................................................................3-10
Disabling and Reenabling MLM Administrative Status .................................................3-11
Customizing Default VC Parameters ............................................................................3-12
Disabling and Reenabling Default VC Admin Status ..............................................3-12
Specifying the Default VCL VPI Number ................................................................3-13
Specifying the Default VCL VCI Number ...............................................................3-14
Specifying the Default VC VPI Range ....................................................................3-15
Specifying the Default VC VCI Minimum Range ....................................................3-16
Specifying the Default VC VCI Maximum Range ...................................................3-17
Modifying Default VC Traffic Parameters ................................................................3-18
Setting the Default VC Transmit PCR ..............................................................3-18
Setting the Default VC Transmit SCR ..............................................................3-19
Setting the Default VC Transmit MBS ..............................................................3-20
Setting the Default VC Receive PCR ...............................................................3-22
Setting the Default VC Receive SCR ...............................................................3-22
Setting the Default VC Receive MBS ..............................................................3-24
Modifying the Default VC Maximum AAL CPCS SDU Size ....................................3-25
Setting the Transmit SDU Size ........................................................................3-25
Setting the Receive SDU Size .........................................................................3-26
vi
305754-A Rev 00
Specifying the AAL Encapsulation Type .................................................................3-27
Specifying the Default VC Transmit QOS Class .....................................................3-28
Specifying the Default VC Receive QOS Class .....................................................3-28
Specifying the Default VC AAL Type ......................................................................3-28
Specifying the Default VC Congestion Indication ...................................................3-28
Enabling and Disabling the Default VC Cell Loss Priority ......................................3-28
Enabling and Disabling Default VC Transmit Tagging ............................................3-28
Enabling and Disabling Default VC Receive Tagging .............................................3-28
Customizing LDP Static Route Parameters ..................................................................3-29
Enabling and Disabling Static Routes ....................................................................3-29
Specifying a Destination Route Prefix ....................................................................3-30
Specifying a Route Mask .......................................................................................3-31
Deleting MPLS from the Interface .................................................................................3-32
Where to Go Next .........................................................................................................3-33
Appendix A
Site Manager Parameters
Accessing MPLS Parameters ........................................................................................ A-1
LDP Parameters ............................................................................................................ A-2
MLM Parameter ............................................................................................................. A-6
Static Route Parameters ................................................................................................ A-7
Default VC Parameters .................................................................................................. A-8
305754-A Rev 00
vii
Figures
Figure 1-1. The MPLS System ...................................................................................1-3
Figure 1-2. Sample MPLS Network ............................................................................1-5
123456 Rev. A
ix
This guide describes Multiprotocol Label Switching (MPLS) and what you do to
start and customize MPLS services on a Bay Networks
To configure MPLS, you must use Site Manager.
Before You Begin
Before using this guide, you must complete the following procedures. For a new
router:
®
router.
Preface
• Install the router (see the installation guide that came with the router).
• Connect the router to the network and create a pilot configuration file (see
Quick-Starting Routers)
Make sure that you are running the latest version of Bay Networks BayRS
.
™
and
Site Manager software. For information about upgrading BayRS and Site
Manager, see the upgrading guide for your version of BayRS.
305754-A Rev 00
xi
Configuring MPLS Services
Text Conventions
This guide uses the following text conventions:
angle brackets (< >) Indicate that you choose the text to enter based on the
description inside the brackets. Do not type the
brackets when entering the command.
Example: If the command syntax is:
bold text
<ip_address>
ping
ping 192.32.10.12
Indicates text that you need to enter and command
, you enter:
names and options.
Example: Enter
show ip {alerts | routes
Example: Use the
dinfo
command.
}
braces ({}) Indicate required elements in syntax descriptions
where there is more than one option. You must choose
only one of the options. D o not type the braces when
entering the command.
Example: If the command syntax is:
}
show ip {alerts | routes
show ip alerts or show ip routes
, you must enter either:
.
brackets ([ ]) Indicate optional elements in syntax descriptions. Do
not type the brackets when entering the command.
Example: If the command syntax is:
]
show ip interfaces [-alerts
show ip interfaces
or
, you can enter either:
show ip interfaces -alerts
.
xii
305754-A Rev 00
Preface
ellipsis points (. . . ) Indicate that you repeat the last element of the
command as needed.
Example: If the command syntax is:
ethernet/2/1 [<parameter> <value>] . . .
ethernet/2/1
and as many parameter-value pairs as
, you enter
needed.
italic text Indicates file and directory names, new terms, book
titles, and variables in command syntax descriptions.
Where a variable is two or more words, the words are
connected by an underscore.
Example: If the command syntax is:
show at <valid_route>
valid_route
is one variable and you substitute one value
for it.
screen text Indicates system output, for example, prompts and
system messages.
Example:
Set Bay Networks Trap Monitor Filters
separator ( > ) Shows menu paths.
Example: Protocols > IP iden tifi es the IP optio n on the
Protocols menu.
vertical line (
) Separates choices for command keywords and
|
arguments. Enter only one of the choices. Do not type
the vertical line when entering the command.
Example: If the command syntax is:
305754-A Rev 00
show ip {alerts | routes}
show ip alerts
show ip routes
or
, you enter either:
, but not both.
xiii
Configuring MPLS Services
Acronyms
AAL ATM adap tation layer
ATM asynchronous transfer mode
B-ISDN Broadband Integrated Services Digital Network
CPCS common part convergence sublayer
DLCI data link connection identifier
FIB forwarding information base
IETF Interne t Engineering Task Force
IP Internet Protocol
IPX Internetwork Packet Exchange
LDP Label Distribution Protocol
LER label edge router
LSR label-switching router
MAC media access control
xiv
MBS maximum burst size
MCR minimum cell rate
MIB management inform ation base
MLM MPLS label management
MPLS Multiprotocol Label Switching
OSPF Open Shortest Path First
PCR peak cell rate
PVC permanent virtual circuit
RIP Routing Information Protocol
SCR sustainable cell rate
SDU service data unit
SNAP Subnetwork Access Protocol
SVC switched virtual circuit
UNI user-to-network interface
305754-A Rev 00
VC virtual circuit
VCI virtual channel identifier
VCL virtual channel link
VPI virtual path identifier
Bay Networks T echnical Publications
You can now print Bay Networks technical manuals and release notes free,
directly from t he Inte rnet. Go to
Bay Networks product for which you need documentation. Then locate the
specific category and model or version for your hardware or software product.
Using Adobe Acrobat Reade r, you can open the manuals an d rel ease n otes, sea rch
for the sections you need, and print them on most standard printers. You can
download Acrobat Reader free from the Adobe Systems Web site,
www.adobe.com
You can purchase Bay Networks documentation sets, CDs, and selected technical
publications through the Bay Networks Collateral Catalog. The catalog is located
on the World Wide Web at
into sections arranged alphabetically:
.
support.baynetwork s.com/library /tpubs/
support.baynetworks.com/catalog.html
Preface
. Find the
and is divided
• The “CD ROMs” section lists available CDs.
• The “Guides/Books” section lists books on technical topics.
• The “Technical Manuals” section lists available printed documentation sets.
Make a note of the part numbers and prices of the items that you want to order.
Use the “Marketing Coll ateral Catalog description” link to place an order and to
print the order form.
How to Get Help
For product assista nce, support contract s, information about educational servic es,
and the telephone numbers of o ur glob al supp ort of f ices, g o to the foll owing URL :
http://www.baynetworks.com/corporate/ contac ts/
In the United States and Canada, you can dial 800-2LANWAN for assistance.
305754-A Rev 00
xv
Chapter 1
Understanding MPLS
This chapter desc ribes th e conce pts un derlyi ng MPLS and, where a ppropr iate, th e
specific ways Bay Networks implements these concepts on its routers. It contains
the following information:
Topic Page
MPLS General Information 1-2
The MPLS Network 1-5
Supported Proto cols 1-7
For More Information 1-7
Where to Go Next 1-8
305754-A Rev 00
1-1
Configuring MPLS Services
MPLS General Information
Multiprotocol Label Switching (MPLS) is an emerging Internet Engineering T ask
Force (IETF) sta ndard that i s currentl y in draft fo rm. Its pr imary goal is to provi de
a standardized solution that supersedes existing proprietary solutions for
integrating label-swapping and forwarding with network layer routing. MPLS
works in an environment where traditional network layer routing protocols (for
example, OSPF and BGP) are used to maintain the routing topology and
forwarding in formation base (FIB) for each router.
In connectionless networks (those using connectionless network layer protocols),
as a packet travels from one hop to another, each router must determine where to
forward the packet based on the individual packet header. This decision process
can be broken down into two major tasks: classi fying a set of packets as part of a
forwarding equivalence class (FEC) and mapping each FEC to a next hop.
By classifying a set of packets as part of an FEC, the router uses the same
forwarding criteria for each packet. All packets that belong to a particular FEC
and that trav el from a particular node follow the same path. This group of packets
is called a “stream .” A packet stream is a group of packets that follows the same
path to a destination. I n a con v ention al IP netw ork, each ro uter hop e xamines ea ch
packet to determine its destination.
1-2
Using MPLS, the examination of the packet is done only once. The first router
assigns a label that defines the specific packet stream. Each intervening router
then forward s packets ba sed on the fixed-length labels. Labels reside in the label
information base (LIB), which contains both inbound and outbound labels
associated with inbound and outbound interfaces.
Looking up a label is faster than interpreting the destination of an individual
packet and routing data based on that destination. By assigning labels to packets
or packet streams, the transmission speed of your network increases.
305754-A Rev 00
MPLS System Overview
The Bay Networks MPLS implementation consists of three major components:
• Label distribution entity
• MPLS label management (MLM) entity
• Forwarding enti ty
Understanding MPLS
Other
interfaces
Figure 1-1
OSPF/RIP
IP
Forwarding
illustrates the basic MPLS system architec tur e.
Routing
table
LDP
MLM
Driver
Key
MIB
External
component
MPLS
component
Data path
Control path
Figure 1-1. The MPLS System
305754-A Rev 00
ATM0058A
1-3
Configuring MPLS Services
Label Distribution Entity
The label dis tribution entity is essentially the implementation of the Label
Distribution Protocol (LDP). LDP is the set of proc edures and mess ages by which
label-switching routers (LSRs) establish label-switched paths (LSPs) through a
network. LDP establishes these paths by mapping network layer routing
information directly to data link layer switched paths.
LDP associates a packet stream with a speci fi c LSP and assigns the LSP a specif ic
label. The label infor mation is distributed betwe en the LSRs and LERs to
maintain stream mapping information.
MPLS Label Management
The MPLS label management (MLM) entity communicates with LDP. It is
responsible for:
• Establishing the de fault VC
• Responding to requests from LDP (for example, requests for a label and
establishing VC communications)
Forwarding
1-4
• Communicating with the ATM driver to set up and tear down VCs
The forwarding entity encapsulates and decapsulates the data that it sends and
receives over the MPLS interface.
Outbound data is delivered to the encapsulation process by the higher layers and
delivered to the lower-level driver for transmission to the MPLS network.
Inbound data is received from the MPLS network by the lower-level driver and
delivered to the decapsulation process, wher e it is stripped of layer 2 protocol
headers. The decapsulation process then passes the inbound data to higher layers
for further processi ng.
305754-A Rev 00
The MPLS Network
The MPLS network (Figure 1-2) consists of two major components:
• Label switching router (LSR)
• Label edge router (LER)
Understanding MPLS
100BASE-T
10BASE-T
LER
MPLS network
LER
100BASE-T
LSR
LER
LSR
LSR
100BASE-T
LER
Key
Label-switching router (LSR)
Label edge router (LER)
Virtual connection
10BASE-T
100BASE-T
Figure 1-2. Sample MPLS Network
305754-A Rev 00
ATM0057A
1-5
Configuring MPLS Services
Label Switching Router
A label-switching router (LSR) is a router that contains all label-sw itching
interfaces. The LSR controls MPLS forwarding in the MPLS network. An LSR
performs table lookup on received packets and, based on the packet label,
forwards the packet or packet stream to the specified outgoing inter f ace. The LSR
swaps the labels of the packet headers before transmitting the packets to the
MPLS network.
Note:
An ATM LSR currently consis ts of an ATM switc hing de vice that w orks
with a UNIX UltraSPARC workstation running Solaris and LDP. For
information about how to configure an ATM LSR, refer to the documentation
provided with your switching device.
Label Edge Router
A label edge router (LER) is an LSR that resides between the IP and MPLS
networks. This router performs two generalized functions:
• It receives non-MPLS traffic, labels that traffic, and forwards it to another
label-switching interface.
1-6
• It receives labeled MPLS traffic, strips the label from the packets, and
forwards the traffic over a non-MPLS interface.
Note:
This guide describes how to configure the LER. For information about
how to start M PLS on the router, see Chapter 2, “Starting MPLS.” For
information about how to customize the ATM router interface for MPLS, see
Chapter 3, “Customizing the MPLS Configuration.”
305754-A Rev 00
Supported Protocols
MPLS supports the following protocols:
•IP
•RIP
• BGP
• OSPF
For More Information
For more inform ation about MPLS, refer to the following documents:
Black, D. Building Switche d N etworks: Mu ltilayer Switching, Qos, IP Multicast,
Network Policy, and Service-Level Agreements. Reaqding, MA.: Addison-Wesley,
1999.
“LDP Specification,” Andersson, Doolan, Feldman, Fredette, Thomas, Internet
Draft <draft-ietf-mpls-ldp-01.txt>. August, 1998.
Understanding MPLS
305754-A Rev 00
“Multiprotocol Label Switching Architecture,” Callon, Rosen, Viswanathan,
Internet Draft <draft-ietf-mpls-arch-02.txt>. July, 1998.
1-7
Configuring MPLS Services
Where to Go Next
Use the following table to determine where to go next.
If you want to Go to
Learn about ATM concepts.
Start MPLS. Chapter 2
Change default settings for MPLS parameters. Chapter 3
Change default settings for ATM interface
parameters.
Change default settings for ATM signaling
parameters.
Change default settings for ATM PVC service record
and PVC parameters.
Change default settings for classical IP service
record parameters.
Change default settings for LAN emulation client
service record parameters.
Change default settings for Multi-Protocol Over ATM
server parameters.
Change default settings for the ATM router
redundancy parameter.
Obtain information about Site Manager parameters. Appendix A
Monitor ATM using the BCC show commands.
Configure NHRP for MPOA services.
Configuring ATM
Services
Configuring ATM
Services
Configuring ATM
Services
Configuring ATM
Services
Configuring ATM
Services
Configuring ATM
Services
Configuring MPOA
Services
Configuring ATM
Services
Configuring ATM
Services
Configuring MPOA
Services
1-8
305754-A Rev 00
Chapter 2
Starting MPLS
This chapter describes how to create a basic MPLS configuration by specifying
values for required parameters only and accepting default values for all other
parameters.
You can confi gure MP LS using Si te Manage r. For instruction s on ho w t o star t and
use Site Manager, see Configuring and Managing Routers wit h Site Manager.
For overview information about MPLS, see Chapter 1, “Understanding MPLS.”
You start MPLS on a router using Site Manager by:
Topic Page
Creating an ATM Circuit 2-2
Adding Protocols to an LDP Session Record 2-4
Adding IP Adjacent Hosts 2-6
Defining IP Static Routes for LDP 2-8
Enabling MLM 2-9
Enabling TCP 2-10
Where to Go Next 2-12
305754-A Rev 00
2-1
Configuring MPLS Services
Creating an ATM Circuit
MPLS operates only over an ATM circuit. You must create an ATM circ uit before
you can configure MPLS.
To create an ATM circuit, complete the following tasks:
You do this System responds
Site Manager Procedure
1. In the Configuration Manager window,
click on an ATM link module interface
(
).
ATM1
2. Click on OK to accept the default circuit
name.
3. Go to the following section, “Adding an
LDP Session Record,” or go to step 4 to
exit this procedure.
4. Click on
. You return to the Configuration Manager
Done
Adding an LDP Session Record
After you create an ATM circuit over which MPLS can operate, you must add an
LDP session record t o that circ uit . F or infor mati on about crea ting an ATM ci rcuit ,
see “Creating an ATM Circuit
Note:
This release supports only one LDP session record per ATM interface.
The Add Circuit window opens.
The Select Connection Type window
opens.
window.
” on page 2-2.
2-2
305754-A Rev 00
Starting MPLS
To add an LDP session record, complete the following tasks:
Site Manager Procedure
You do this System responds
1. In the Configuration Manager window,
click on an ATM link module interface
(
).
ATM1
2. Click on OK to accept the default circuit
name.
3. Click on
4. Click on
5. Click on
6. Set the following parameters:
• Local IP Address
• Remote IP Address
Click on
descriptions beginning on page A-3.
7. Click on OK. The Default VC Record Parameters
8. Click on OK. The Select Protocols window opens.
9. Go to the following section, “Adding
Protocols to the LDP Session,” or go to
step 10 to exit this procedure.
10. Click on
11. Click on
12. Click on
13. Click on
. The Edit MPLS Connector win do w opens .
MPLS
. The LDP Session Records List window
LDP
. The LDP Session Record Parameters
Add
Help
or see the parameter
. You return to the LDP Session Records
Cancel
. You return to the Edit MPLS Connector
Done
. You return to the Select Connection Type
Done
. You return to the Configuration Manager
Done
The Add Circuit window opens.
The Select Connection Type window
opens.
opens.
window opens.
window opens.
List window.
window.
window.
window.
305754-A Rev 00
2-3
Configuring MPLS Services
Adding Protocols to an LDP Session Record
You can either add protocols immediately after you create an LDP session, or you
can add protocols to an existing LDP session at any time.
Adding Protocols to the LDP Session
To add protocols to an LDP session record, complete the following tasks:
Site Manager Procedure
You do this System responds
1. In the Select Protocols window, click on IP. A check mark appears in the box for IP.
2. Click on any IP routing protocol that you
want to add.
3. Click on OK. The IP Configuration window opens.
4. Set the following parameters:
• IP Address
• Subnet Mask
Click on
RIP, and OSPF Ser vices
5. Click on OK. For each additional protocol that you
Help
or see
Configuring IP, ARP,
for details.
A check mark app ears in the bo x for each
additional protocol that you select.
The IP address should ma tch the loc al IP
address that you configured for the LDP
session.
selected, the Configuration Manager
displays a protocol-specific window
prompting you for required information.
2-4
6. Click on
7. Click on
8. Click on
Click on
the appropriate protocol-specific guide.
After completing all required protocol
configuration, you return to the LDP
Session Records List wind ow.
. You return to the Edit MPLS Connector
Done
window.
. You return to the Select Connection Type
Done
window.
. You return to the Configuration Manager
Done
window.
for any parameter, or see
Help
305754-A Rev 00
Loading...