Avaya MPOA User Manual
Configuring MPOA and NHRP Services
BayRS Version 13.20
Site Manager Software Version 7.20
BCC Version 4.20
Part No. 305861-A Rev 00
April 1999
Bay Networks, Inc.
4401 Great America Parkway
Santa Clara, CA 95054
Copyright © 1999 Bay Networks, Inc.
All rights reserved. Printed in the USA. April 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 for their app lica tio ns o f any products specif i ed in th is d ocume nt .
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 license. A summary of the Software License is included in this document.
Trademarks
AN, BCN, BLN, BN, and Bay Networks are registered trademarks and Advanced Remote Node, ANH, ARN, ASN,
BayRS, BCC, System 5000, and the Bay Networks logo 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 due 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 that 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
305861-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 products. 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 pr ovided i n t hi 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 Net works 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 charge 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 that th e Licens 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 W ARRANTY OF
MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE. Licensee is responsible for the security of
305861-A Rev 00
iii
its own data and information and for maintaining adequate procedures apart from the Software to reconstruct lost 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 limitations se t 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 May, 1991, will apply to the
examination of the Software to facilitate interoperability. Licensee agrees to notify Bay 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 effecti ve 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, the Software or related 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 export cont rol laws and re gu la tio ns , or to any national or re sident 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. Bo x 58185, Santa Clara, California 9505 4- 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 BAY
NETWORKS UNLESS BAY NETWORKS GIVES ITS EXPRESS WRITTEN CONSENT, INCLUDING AN
EXPRESS WAIVER OF THE TERMS OF THIS AGREEMENT
iv
305861-A Rev 00
Contents
Preface
Before You Begin .............................................................................................................xiii
Text Conventions .............................................................................................................xiv
Acronyms ........................... .......................... .......................... ......................... .................xvi
Bay Networks Technical Publications ............................................................................xviii
How to Get Help ............................................................................................................xviii
Chapter 1
Understanding MPOA and NHRP
ATM General Information ................................................................................................1-1
Multi-Protocol over ATM ..................................................................................................1-2
MPOA Logical Components .....................................................................................1-3
MPOA Basic Elements .............................................................................................1-4
Establishing a Network Cut-Through .... ...... ....................................... ...... ....... ...... ...1-5
NHRP .............................................................................................................................1-7
For More Information ......................................................................................................1-8
Where to Go Next ...........................................................................................................1-9
Chapter 2
Starting MPOA and NHRP Services
Starting Configuration Tools ...........................................................................................2-1
Starting the MPOA Server ..............................................................................................2-2
Creating an MPOA Service Record .........................................................................2-2
Adding an MPOA Server ..........................................................................................2-4
Starting NHRP on an ATM LEC, PVC, or Classical IP Service ......................................2-5
Starting NHRP on an ATM LEC Service ..................................................................2-6
Starting NHRP on an ATM PVC Service ................................................................2-11
Starting NHRP on an ATM Classical IP (RFC 1577 SVC) Service ........................2-14
Where to Go Next .........................................................................................................2-16
305861-A Rev 00
v
Chapter 3
Customizing MPOA Services
Disabling and Reenabling an MPOA Service .................................................................3-2
Setting the MPS Address Generating Mode ...................................................................3-3
Specifying an MPS Control ATM Address ......................................................................3-5
Network Prefix ..........................................................................................................3-5
User Suffix ................................................................................................................3-6
Disabling and Reenabling MPOA Servers ............................. ...... ...... ....... ...... ....... ...... ...3-8
Specifying the MPS Configuration Mode ......................................................................3-10
Specifying a LECS ATM Address .................................................................................3-11
Network Prefix ........................................................................................................3-12
User Suffix ..............................................................................................................3-12
Configuring a Unique Selector Byte for an MPS Address ............................................3-14
Defining MPS Timer Values ..........................................................................................3-16
Setting the Transmission Interval for MPOA Keepalive Packets .............................3-17
Setting the Valid Lifetime for Keepalive Packets .....................................................3-18
Setting the Initial Retry Time ..................................................................................3-19
Setting the Maximum Retry Time ...........................................................................3-21
Setting the Time to Wait for Responses to Resolution Requests ...........................3-22
Setting the Valid Interval for Replies to Resolution Requests ................................3-23
Defining MPS Cache Values ........................................................................................3-25
Setting the Initial Cache Size .................................................................................3-25
Setting the Maximum Cache Size ..........................................................................3-26
Deleting MPOA Servers ...............................................................................................3-28
Deleting an MPOA Service Record ..............................................................................3-29
Where to Go Next .........................................................................................................3-31
Chapter 4
Customizing NHRP Services
Accessing NHRP Client and Server Global Parameters ................................................4-2
Disabling NHRP on an LEC or PVC or Classical IP Service ..........................................4-4
Deleting NHRP from an LEC or PVC or SVC Service ....................................................4-6
Deleting NHRP Globally .................................................................................................4-7
Where to Go Next ...........................................................................................................4-8
vi
305861-A Rev 00
Appendix A
Site Manager Parameters
Accessing ATM Parameters ........................................................................................... A-1
Accessing ATM MPOA Parameters Through a Window Path ................................. A-2
Accessing ATM MPOA and NHRP Parameters Through a Menu Path ................... A-2
MPOA Service Parameters ............................................................................................ A-3
MPOA Server (MPS) Parameters .................................................................................. A-5
MPS Add Parameters .............................................................................................. A-5
MPS Operational Parameters ................................................................................. A-7
NHRP Global Parameters ............................................................................................ A-14
NHRP Interface Parameters ........................................................................................ A-19
Appendix B
BCC Parameters
MPOA Service Record Parameters ............................................................................... B-2
MPS Parameters ........................................................................................................... B-4
MPOA Server Parameters ............................................................................................. B-8
NHRP Global Parameters .............................................................................................. B-9
NHRP Interface Parameter .......................................................................................... B-13
Appendix C
Monitoring MPOA and NHRP Services
Online Help for show Commands .................................................................................. C-2
show mpoa caches ........................................................................................................ C-3
show mpoa caches all .............................................................................................C-3
show mpoa caches egress ......................................................................................C-4
show mpoa caches ingress .....................................................................................C-6
show mpoa server .........................................................................................................C-7
show mpoa server configuration ............................................................................. C-7
show mpoa server stats .......................................................................................... C-9
show nhrp .................................................................................................................... C-12
show nhrp client configuration ............................................................................... C-12
show nhrp client stats ........................................................................................... C-13
show nhrp interfaces ............................................................................................. C-14
show nhrp server configuration .............................................................................C-15
show nhrp server stats ..........................................................................................C-15
305861-A Rev 00
vii
Appendix D
Example Configuration
Configuration Diagram ................................................................................................... D-2
BCC Configuration Sequence .......................................................................................D-4
Appendix E
BCC Configuration Tree
for MPOA and NHRP
Index
viii
305861-A Rev 00
Figures
Figure 1-1. ATM Zero-Hop (Cut-Through) Routing .....................................................1-2
Figure 1-2. MPOA with Cut-Through VC ....................................................................1-6
Figure 2-1. Mapping an MPS to an LEC Service .......................................................2-9
Figure D-1. Example MPOA/NHRP Configuration ..................................................... D-2
Figure E-1. BCC Configuration Tree for MPOA and NHRP ....................................... E-2
305861-A Rev 00
ix
Tables
Table D-1. Example Configuration Summary ........................................................... D-3
305861-A Rev 00
xi
This guide describes Bay Networks implementation of Multi-Protocol over ATM
(MPOA) and Next Hop Resolution Protoc ol (NHRP) servi ces, and what you do to
start and customize these services on a Bay Networks
You can use the Bay Command Console (BCC
these services. Use Site Manager to support any feature not supported by the
BCC.
Before You Begi n
Preface
®
router.
™
) or Site Manager to configure
305861-A Rev 00
Before attempting to perform any of the tasks described in this guide, you must
complete the following procedures. For a new router:
• Install the router (see the installation guide that came with your router).
• Connect the router to the network and create a pilot configuration file (see
Quick-Starting Routers).
In addition, you must configure any ATM servic es ( for example, LAN emulation)
required in Chapter 2.
™
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.
xiii
Configuring MPOA and NHRP Services
Text Conventions
This guide uses the following text conventions:
angle brackets (< >) Indicate that you choose the text to enter based on the
bold text Indicates command names and options and text that
description inside the brackets. Do not type the
brackets when entering the command.
Example: If the command syntax is:
<
ping
ip_address
>, you enter:
ping 192.32.10.12
you need to enter.
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. Unless explicitly instructed to
do so, do not type the braces when entering the
command.
Example: If the command syntax is:
show ip {alerts
routes}, you must enter either:
|
show ip alerts or show ip routes, but not both.
If the command sets a parameter value consisting of
multiple elements, you must type the braces as part of
the command if instructed to do so.
Example:
severity-mask {fault warning info}
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], you can enter either:
show ip interfaces or
show ip interfaces -alerts
.
xiv
305861-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
>] . . . , you enter
[<
ethernet/2/1 and as many parameter-value pairs as
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 ip <
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 Site Manager menu or BCC object navigation
paths.
Example: Protocols > I P ide nti fies the I P opt ion on the
Protocols menu (Site Manager)
Example: box or stac k > ip > osp f id enti f ies th e path to
the ospf object in BCC configuration mode.
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:
show ip {alerts
show ip alerts or
routes}, you enter either:
|
show ip routes, but not both.
305861-A Rev 00
xv
Configuring MPOA and NHRP Services
Acronyms
AAL ATM adaptation layer
AFI authority and format identifier
ARE ATM Routing Engine
ARP Address Resolution Protocol
ATM asynchronous transfer mode
B-ISDN Broadband Integrated Services Digital Network
CSU channel service unit
DCE data communication equipment
DSU data service unit
DTE data terminal equipment
ELAN emulated local area network
IETF Internet Engineering Task Force
ILI Intelligent Link Interface
xvi
ILMI Interim Local Management Interface
IP Internet Protocol
LANE local area network emulation
LE LAN emulat ion
LEC LAN emulation client
LECS LAN emulation configuration server
LER label edge router
LES LAN emulat ion server
LLC Logical Link Control
MAC media access control
MIB management inform ation base
MPC MPOA client
MPLS Multiprotocol Label Switching
MPOA Multi-Protocol over ATM
305861-A Rev 00
Preface
MPS MPOA server
MTU maximum transmission unit
NHRP Next Hop Resolution Protocol
OC-3 Optical Carrier-level 3
OSPF Open Shortest Path First
PDN Public Data Network
PDU protocol data unit
PHY physical [layer]
PMD physical medium dependent
PT payload type
PVC permanent virtual circuit
RIP Routing Information Protocol
SAAL signaling AAL
SAP service access point
305861-A Rev 00
SAR segmentation and reassembly
SMDS Switched Multimegabit Data Service
SNAP Subnetwork Access Protocol
SNMP Simple Network Management Protocol
SONET/SDH Synchronous Optical Network/Synchronous Digital Hierarchy
SPE synchronous payload envelope
SRM System Resource Module
SSCOP Service Specific Connection Oriented Protocol
SSCS service specific convergence sublayer
SVC switched virtual circuit
UNI user-to-network interface
VC virtual circuit
VCC virtual channel connection
VCI virtual channel identifier
VCL virtual channel link
xvii
Configuring MPOA and NHRP Services
VPC virtual path connection
VPI virtual path identifier
WAN wide area network
Bay Networks Technical Publications
You can now print Bay Networks technical manuals and release notes free,
directly from the Internet. Go to support.baynetwork s.com/libr ary/ tpubs/ . Fi nd the
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 Re ader, you can open the manuals and releas e note s, searc h
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 support.baynetworks.com/catalog.html and is divided
into sections arranged alphabetically:
• 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 Collateral Catalog description” link to place an order and to
print the order form.
How to Get Help
For product assi stance, support contracts, information about educational services,
and the telephone numbers of our gl obal supp ort offices, go to the following URL:
http://www.baynetworks.com/corporate/ conta cts/
In the United States and Canada, you can dial 800-2LANWAN for assistance.
xviii
305861-A Rev 00
Chapter 1
Understanding MPOA and NHRP
This chapter descr ibes the c oncepts under lying Multi-pr otocol o ver ATM (MPO A)
and Next-Hop Resolution Protocol (NHRP) and, where appropriate, the specific
ways in which Bay Networks implements MPOA and NHRP functionality on its
routers. It contains the following information:
Topic Page
ATM General Information 1-1
Multi-Protocol ov er ATM 1-2
NHRP 1-7
For More Information 1-8
Where to Go Next 1-9
ATM General Information
Asynchronous transfer mode (ATM) is a connection-oriented, cell-based
technology that relays traffic across a Broadband Integrated Services Digital
Network (B-ISDN). ATM provides a cost-effective way of transmitting voice,
video, and data across a network. For more information about ATM, see
Configuring ATM Services.
305861-A Rev 00
1-1
Configuring MPOA and NHRP Services
Multi-Protocol over ATM
As defined by the ATM Forum, Multi-Protocol over ATM (MPOA) maps routed
and bridged traffic flows to ATM SVCs, thereby removing many performance
limitations imposed by the multihop routing of individual pa ckets. This technique
of mapping identifiable traffic flows to virtual channels creates network
“shortcuts” between source and destination clients, and is generally referred to as
cut-through or zero-hop routing . Figur e 1-1
can communicate efficiently over an independent layer 2 (ATM) virtual channel,
established by means of MPOA and NHRP negotiations.
shows ho w users on LAN 1 or LAN 2
MPOA server 1
(MPS)
MPOA
MPOA client 1
(MPC)
ATM ELAN, PVC
or RFC 1577 SVC
NHRP NHRP
ATM ELAN
Cut-through (zero-hop) route (ATM SVC)
Established through MPOA/NHRP negotiations
MPOA servers
(MPSs)
ATM ELAN, PVC
or RFC 1577 SVC
ATM ELAN
MPOA server
(MPS)
MPOA
MPOA client 2
(MPC)
LAN 2LAN 1
BCC0029A
n
Figure 1-1. ATM Zero-Hop (Cut-Through) Routing
MPOA supports communication between an MPOA client (MPC), typically an
ATM edge device or switch, and its MPOA server (MPS), typically a router.
NHRP supports communication between MPSs.
1-2
305861-A Rev 00
Understanding MPOA and NHRP
Although the connection between any two MPSs can be supported by an ATM
PVC, RFC 1577 SVC (ATM Classical IP), or emulated LAN (ATM LANE), the
connection between any MPC and its MPS must always be supported by an
ELAN, as shown in Figure 1-1 on page 1-2
.
Cut-through routing i s based o n the f act t hat, in most cases , data t ransfe r occur s at
a steady rate of flow. For example, data or file transfer from one legacy Ethernet
LAN to a remote counterpart usually involves multiple frames. A file transfer of
approximately 45 KB requires about 30 Ether net frames, all address ed to the same
destination.
In an MPOA environment, it is possible to:
• Identify, from the address field in the first frame of a data/file transfer, the
recipient of that data or file.
• Establish an SVC to the recipient.
The software then disassembles all 30 or so frames into approximately 900 ATM
cells and transmitts th em to the recipient by way of the virtual channel provided
by the SVC.
Network performa nce i mp roves as the cells follow a predetermined direct path, in
contrast to the hop-by-hop routing of the Ethernet frames. Network performance
improves markedly in the case of steady-stream deterministic data flows, such as
video.
MPOA Logical Components
MPOA operati ons are based on l ogical compone nts, which can be im plemented in
various configurations of hardware and software. MPOA logical components
include the following:
•MPOA clients
An MPOA client (MPC) resides in each ATM edge device (for example, an
ATM switch) served by an MPOA router. BayRS does not provide MPC
functionality. The primary function of the MPC is t o act, in ATM termi nology,
as an ingress or egress point for traffic establishing and subsequently using
network cut-throughs.
305861-A Rev 00
1-3
Configuring MPOA and NHRP Services
The MPC moni tors traffic flows between a local source an d remote
destinations. Wh en traffic volume between a sour ce and a d estin ation exceeds
a preconfigured threshold level (for example x packets to the same network
layer address in y seconds), the MPC attempts to set up an SVC between the
source and destination workstations.
In attempting to set up an SVC, the MPC first looks in a local cache of
network layer-to-ATM address mappings. If the MPC finds the destination
address in its local cac he, it immediately be gins to est ablish the SVC. If it f ails
to locate the destination address in the local cache, it generates an MPOA
address resolution request to an adjacent MPOA server.
• MPOA routers
Each MPOA router that serves MPCs, directly or indirectly, includes a
collection of logical functions that map network layer addresses to ATM
addresses. Each MPO A router maintai ns tables of adjacent network layer (IP),
MAC laye r, and ATM addresses, in addition to s tandar d ro uting tabl es der ived
from a routing protocol (generally OSPF or RIP).
MPOA routers communicate over NHRP to map network layer addresses to
ATM addresses. BayRS provides MPOA router functionality to map IP
addresses to their ATM counterparts.
• MPOA servers
The MPOA server (MPS) is a logical function that mediates between local
MPCs and the MPOA router. It receives MPOA address resolution requests
from MPCs and passes them to the MPOA routing function. The MPOA
router, using NHRP, resolves the address and passes the requested ATM
address back to the MPS. The MPS, in turn, forwards the resolved address to
the requesting MPC. BayR S provides MPOA server func tionality.
MPOA Basic Elements
MPOA services provided by each Bay Networks router depend on the existence
of:
• An ATM emulated LAN (using LANE) between each MPC and its MPS.
• An ATM emulated LAN, ATM Classical IP (RFC 1577 SVC), or an ATM
PVC between any two MPSs. (See Figure 1-1 on page 1-2
• NHRP to resolve ATM and IP source and destination addresses.
• IP to route NHRP packets and other traffic between MPSs.
1-4
.)
305861-A Rev 00
Understanding MPOA and NHRP
For more information about Go to
IP
LANE
NHRP “NHRP” on page 1-7
Establishing a Network Cut-Through
MPOA componen ts and elements fu nction together to establish an SVC bet ween a
source host and a destination host, as follows:
1.
A local MPC monitors traf f ic f lo w and mainta ins a count of pack ets addre ssed
over a specific interval to remote hosts. When the count exceeds a threshold
value, the MPC attempts to establish an SVC to the host.
To establish the virtual connection, the MPC needs the ATM address of the
host.
2.
The MPC first checks a local address resolution cache to map the known
network layer address with an ATM equivalent.
3.
If the cache search fails, the MPC issues an MPOA resolution request to the
local MPS function resident on the adjacent router.
4.
The local MPS hands the resolution request to the MPOA router component.
5.
The MPOA rou ter gener ates an NHRP address resolut ion reque st for t he ATM
address of the destination host. Standard routing protocols move the NHRP
request through the ne twork toward the destination host. Eventually, the
NHRP request reaches the egress router, that is, the router that serves the
target host.
Configuring IP Services
Configuring ATM Services
305861-A Rev 00
6.
The egress router forwards the request to its MPS entity.
7.
The remote MPS provides the ATM address of the destination host to its
NHRP entity.
If the destination host is connected to a legacy LAN, the MPS provides the
ATM address of the router that conn ect s to the legacy LAN. If th e dest ination
host is ATM-attached, the MPS provides the ATM address of the destination
host.
1-5
Configuring MPOA and NHRP Services
8.
The remote MPOA router generates an NHRP address resolution reply
containing the ATM address pr ovi ded b y the MPS. Stan dard ro uting prot ocols
move the NHRP reply through the network to the local MPOA router.
9.
The local MPOA rout er sends the resolved address to the MPS, which then
caches and sends t he r esolved addre ss to the MPC that initiated the reso lut io n
process.
10.
The local MPC caches the address resolution information and establishes an
SVC to the remote MPC, establish ing the netw or k cut-thr ough connection f or
more efficient communication.
ATM MPC
10BASE-T
ATM network
ATM MPS
ELAN 1
ELAN 2
ATM MPC
10BASE-T
Figure 1-2. MPO A with Cut-Through VC
Note again t hat in Figure 1-2, the logical connection between any two MPSs can
be an ATM PVC or RFC 1577 SVC (ATM Classical IP) instead of an ELAN,
depending on your network topology requirements.
1-6
ELAN 3
ELAN 4
ATM MPS
Key
Cut-through VC
Logical connection
NHRP control VC
ATM0055A
305861-A Rev 00
NHRP
Understanding MPOA and NHRP
NHRP is an address resolution protocol described in Internet RFC 2332.
As defined by the RFC, NHRP provides address resolution services by mapping
“internetworking layer addresses to NBMA subnetwork addresses.” As
implemented by Bay Networks, NHRP resolves IP to ATM addresses.
The IETF draft specifies behavior for NHRP clients and NHRP servers.
• The NHRP client (NHC) generates NHRP address resolution requests on
behalf of applications such as a local MPS.
• The NHRP server (NHS) responds to NHRP address resolution requests by
generating NHRP address resolution replies. For this purpose, the NHS
maintains a next-hop cache.
NHRP supports address resolution using seven formatted message types.
• NHRP resolution request
An NHRP resolution request is generated by an NHC and routed through the
ATM topology. Functionally eq uivalent to a stan dard ARP request, it contai ns
the layer 3 and layer 2 address of the originator, the layer 3 address of the
target destination, and a blank field reserved for the layer 2 address of the
target. As implemented by Bay Networks, the NHRP resolution request
contains the IP and ATM addresses of the originator and the IP address of the
target.
305861-A Rev 00
• NHRP resolution reply
An NHRP resolution reply is generated by an NHS in response to an NHRP
resolution request. Like an NHRP resolution request, it is routed through the
ATM topology. It is functionally e qui v alen t to a stan dard ARP response in th at
it replicates the information in the NHRP resolution request and supplies the
requested layer 2 (ATM) address.
• NHRP registration request
An NHRP registration request is generated by an NHC and directed toward
the local NHS. The NHRP registration request is used to register address
mapping data gathered by the NHC with the NHS. The NHS places mapping
data in its next-hop cache.
1-7
Configuring MPOA and NHRP Services
• NHRP registration reply
An NHRP registration reply is generated by an NHS in response to an NHRP
registration request. It provides positive or negative acknowledgment of data
receipt.
• NHRP purge request
An NHRP purge request can be generated by either an NHC or an NHS. It
requests the recipi ent to delete pr evio usly cached informatio n that has become
invalid.
• NHRP purge reply
An NHRP purge reply is generated by either an NHC or an NHS in response
to an NHRP purge request. It provides positive acknowledgment of data
receipt.
• NHRP error indication
An NHRP error indication can be generated by either an NHC or an NHS. It
conveys error status to the sender of an NHRP message.
For More Information
1-8
For more information about MPOA and NHRP, refer to the following documents:
Heinanen, J. Multiprotocol Encapsulation over ATM Adaptation Layer 5.
RFC 1483. Network Working Group. July 1993.
Cole, B., N. Doraswamy, D. Katz, J. Luciani, D. Piscitello. NBMA Next Hop
Resolution Protocol (NHRP). RFC 2332. April 1998.
305861-A Rev 00
Where to Go Next
Use the following table to determine where to go next.
If you want to Go to
Understanding MPOA and NHRP
Learn about ATM and PVCs.
Learn about LAN emulation.
Start MPOA and NHRP services. Chapter 2
Change defa ult settings for MPOA server parameters. Chapter 3
Change default settings for NHRP client or server
parameters.
Obtain information about Site Manager parameters. Appendix A
Obtain information about BCC parameters. Appendix B
Monitor ATM using the BCC show commands. Appendix C
Review an example MPOA/NHRP configuration
sequence.
Review the BCC configuration tree for MPOA and NHRP
services.
Configuring ATM Services
Chapter 4
Appendix D
Appendix E
305861-A Rev 00
1-9
Chapter 2
Starting MPOA and NHRP Services
This chapter describes how to create basic MPOA and NHRP configurations by
specifying v alues for r equired paramet ers only, and by accepting def ault v alues fo r
all other parameters.
This chapter contains the following information:
Topic Page
Starting Configuration Tools 2-1
Starting the MPOA Server 2-2
Starting NHRP on an ATM LEC, PVC, or Classical IP Service 2-5
Where to Go Next 2-16
Starting Configuration Tools
Before configuring MPOA or NHRP services, refer to the following user guides
for instructions on how to start and use the Bay Networks configuration tool of
your choice.
Configuration Tool User Guide
Bay Command Console (BCC)
Site Manager
305861-A Rev 00
Using the Bay Command Console (BCC)
Configuring and Managing Routers with
Site Manager
2-1
Configuring MPOA and NHRP Services
Start ing the MPOA Server
To start the MPOA server, you must perform the following steps:
1.
Start ATM on the router. (See Configuring ATM Services.)
2.
Configure any ATM PVCs, SVCs (Classical IP), and LAN emulation client
(LEC) services that you need for MPOA/NHRP to operate within your
specific network topology. (See Chapter 1 and Configuring ATM Services.)
Be sure to:
• Specify LANE data encapsulation for each LEC that you require.
• Specify LLC-SNAP data encapsulation for each PVC that you require.
• Configure IP and NHRP on each LEC, PVC, and Classical IP (SVC)
service.
3.
Create an MPOA service record.
4.
Add an MPS to the MPOA service record.
5.
Ensure that a LECS has been configured on your network.
6.
Map any LEC services on the router to the desired local MPS.
Creating an MPOA Service Record
To run an MPOA server o v er ATM, you must f i rst cr eate an MPOA service record
on an ATM interface. Then you add one or more MPOA servers (MPSs) to the
MPOA service record.You can use the BCC or Site Manager to accomplish this
using default values for all parameters.
Using the BCC
To create an MPOA service record, navigate to the appropriate ATM interface
prompt and enter:
mpoa-service
2-2
305861-A Rev 00
Loading...