Avaya ATM DXI User Manual

Download

Page 1

Conﬁguring ATM DXI Services

Router Software Version 11.0 Site Manager Software Version 5.0

Part No. 114057 Rev. A August 1996

Page 2

4401 Great America Parkway 8 Federal Street Santa Clara, CA 95054 Billerica, MA 01821

and recommendations in this document are believed to be accurate and reliable, but are presented without express or implied warranty. Users must tak e full responsibility for their applications of an y products speciﬁed 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 license. A summary of the Software License is included in this document.

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 Software clause at DFARS 252.227-7013.

Notice for All Other Executive Agencies

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 clause at FAR 52.227-19.

Trademarks of Bay Networks, Inc.

ACE, AFN, AN, BCN, BLN, BN, BNX, CN, FN, FRE, GAME, LN, Optivity, PPX, SynOptics, SynOptics Communications, Wellﬂeet and the Wellﬂeet logo are registered trademarks and ANH, ASN, Bay•SIS, BCNX, BLNX, EZ Install, EZ Internetwork, EZ LAN, PathMan, PhonePlus, Quick2Conﬁg, RouterMan, SPEX, Bay Networks, Bay Networks Press, the Bay Networks logo and the SynOptics logo are trademarks of Bay Networks, Inc.

Third-Party Trademarks

All other trademarks and registered trademarks are the property of their respective owners.

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 products 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 are Copyright © 1988, Regents of the Univ ersity 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 such 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 speciﬁc 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 114057 Rev. A

Page 3

Bay Networks Software License

Note: This is Bay Networks basic license document. In the absence of a

software license agreement specifying varying terms, this license -- or the license included with the particular product -- shall govern licensee’s use of Bay Networks software.

This Software License shall govern the licensing of all software provided to licensee by Bay Networks (“Software”). Bay Networks will provide licensee with Software in machine-readable form and related documentation (“Documentation”). The Software provided under this license is proprietary to Bay Networks and to third parties from whom Bay Networks has acquired license rights. Bay Networks will not grant any Software license whatsoev er , either explicitly or implicitly, except by acceptance of an order for either Software or for a Bay Networks product (“Equipment”) that is packaged with Software. Each such license is subject to the following restrictions:

1. Upon delivery of the Software, Bay Networks grants to licensee a personal, nontransferable, nonexclusi ve license to use the Software with the Equipment with which or for which it was originally acquired, including use at any of licensee’s facilities to which the Equipment may be transferred, for the useful life of the Equipment unless earlier terminated by default or cancellation. Use of the Software shall be limited to such Equipment and to such facility. Software which is licensed for use on hardware not offered by Bay Networks is not subject to restricted use on any Equipment, however, unless otherwise speciﬁed on the Documentation, each licensed copy of such Software may only be installed on one hardware item at any time.

2. Licensee may use the Software with backup Equipment only if the Equipment with which or for which it was acquired is inoperative.

3. Licensee may make a single copy of the Software (but not ﬁrmware) for safekeeping (archives) or backup purposes.

4. Licensee may modify Software (but not ﬁrmware), or combine it with other software, subject to the provision that those portions of the resulting software which incorporate Software are subject to the restrictions of this license. Licensee shall not make the resulting software available for use by any third party.

5. Neither title nor ownership to Software passes to licensee.

6. Licensee shall not provide, or otherwise make available, any Software, in whole or in part, in any form, to any third party. Third parties do not include consultants, subcontractors, or agents of licensee who have licensee’s permission to use the Software at licensee’s facility, and who have agreed in writing to use the Software only in accordance with the restrictions of this license.

7. Third-party owners from whom Bay Networks has acquired license rights to software that is incorporated into Bay Networks products shall have the right to enforce the provisions of this license against licensee.

8. Licensee shall not remove or obscure any copyright, patent, trademark, trade secret, or similar intellectual property or restricted rights notice within or afﬁxed to any Software and shall reproduce and afﬁx such notice on any backup copy of Software or copies of software resulting from modiﬁcation or combination performed by licensee as permitted by this license.

114057 Rev. A iii

Page 4

Bay Networks Software License

9. Licensee shall not reverse assemble, reverse compile, or in any way reverse engineer the Software. [Note: For licensees in the European Community, the Software Directi v e dated 14 May 1991 (as may be amended from time to time) shall apply for interoperability purposes. Licensee must notify Bay Networks in writing of any such intended examination of the Software and Bay Networks may provide review and assistance.]

10. Notwithstanding any foregoing terms to the contrary, if licensee licenses the Bay Networks product “Site Manager,” licensee may duplicate and install the Site Manager product as speciﬁed in the Documentation. This right is granted solely as necessary for use of Site Manager on hardware installed with licensee’s network.

11. This license will automatically terminate upon improper handling of Software, such as by disclosure, or Bay Networks may terminate this license by written notice to licensee if licensee fails to comply with any of the material provisions of this license and fails to cure such failure within thirty (30) days after the receipt of written notice from Bay Networks. Upon termination of this license, licensee shall discontinue all use of the Software and return the Software and Documentation, including all copies, to Bay Networks.

12. Licensee’s obligations under this license shall survive expiration or termination of this license.

(continued)

iv 114057 Rev. A

Page 5

Conﬁguring ATM DXI Services About This Guide

Before You Begin .............................................................................................................xiii

Conventions .................................................................................................................... xiv

Acronyms ......................................................................................................................... xv

Ordering Bay Networks Publications ..............................................................................xvi

Technical Support and Online Services

Bay Networks Customer Service ...................................................................................xviii

Bay Networks Information Services ................................................................................ xix

World Wide Web ...................................................................................................... xix

Customer Service FTP ............................................................................................. xix

Support Source CD ................................................................................................... xx

CompuServe .............................................................................................................xx

InfoFACTS ................................................................................................................ xxi

How to Get Help ....................................................................................................... xxi

Chapter 1 Starting ATM DXI

Before You Begin ............................................................................................................1-1

Adding ATM DXI to the Router .......................................................................................1-2

Creating an ATM DXI Circuit ....................................................................................1-2

Enabling Protocols on an ATM DXI Circuit ...............................................................1-2

Adding PVCs to an ATM DXI Circuit ........................................................................1-3

Deleting ATM DXI from the Router .................................................................................1-4

Where to Go Next ...........................................................................................................1-5

Chapter 2 Understanding ATM DXI Concepts

ATM DXI versus ATM ......................................................................................................2-1

114057 Rev. A v

Page 6

ATM DXI Support ............................................................................................................2-2

Multiprotocol Encapsulation .....................................................................................2-3

AAL Sublayer Support ..............................................................................................2-3

ATM DXI Error Checking ..........................................................................................2-4

ATM DXI LMI Support ..............................................................................................2-5

Simulated Multicast Packet Support .........................................................................2-5

ARP and Inverse ARP Support ................................................................................2-6

ATM DXI Implementation Notes .....................................................................................2-6

Conﬁguring Synchronous Lines for ATM DXI ...........................................................2-6

ATM DXI Modes of Operation ..................................................................................2-7

Mode 1A ............................................................................................................2-7

Mode 1B ............................................................................................................2-7

Mode 2 ...............................................................................................................2-7

Mode 2 Proprietary ............................................................................................2-7

Access Modes for ATM DXI Services .......................................................................2-9

Group Access Mode ..........................................................................................2-9

Direct Access Mode .........................................................................................2-10

Hybrid Access Mode ........................................................................................2-11

Using Hybrid Access for Transparent Bridging .......................................................2-12

Using Hybrid Access for Routing ...........................................................................2-13

ATM DXI and Multipath Support .............................................................................2-13

ATM Layers ...................................................................................................................2-15

AAL 3/4 ..................................................................................................................2-16

AAL 5 .....................................................................................................................2-17

Data Transmission ........................................................................................................2-18

For More Information ....................................................................................................2-19

Where to Go Next .........................................................................................................2-20

Chapter 3 ATM DXI Window Basics

Adding or Copying PVCs ................................................................................................3-1

Setting PVCs for Multipath Mode ....................................................................................3-1

Managing Protocols ........................................................................................................3-3

Where to Go Next ...........................................................................................................3-4

vi 114057 Rev. A

Page 7

Chapter 4 Customizing an ATM DXI Interface

Enabling or Disabling the Interface .................................................................................4-1

Entering an Interface Description ...................................................................................4-1

Changing the DXI Mode .................................................................................................4-2

Assigning a Maximum Number of Virtual Circuits ..........................................................4-2

Assigning Data Encapsulation ........................................................................................4-3

Selecting a Multiprotocol Encapsulation Method .....................................................4-3

Selecting a CS PDU Encapsulation Method ............................................................4-4

Enabling or Disabling the Multicast Function ..................................................................4-4

Enabling or Disabling LMI ...............................................................................................4-5

Where to Go Next ...........................................................................................................4-5

Chapter 5 Customizing ATM DXI PVCs

Setting a VPI/VCI Pair ....................................................................................................5-1

Setting a VPI Number ..............................................................................................5-2

Setting a VCI Number ..............................................................................................5-2

Enabling or Disabling a PVC ..........................................................................................5-2

Changing the PVC Access Mode ...................................................................................5-3

Assigning Data Encapsulation ........................................................................................5-3

Selecting a Multiprotocol Encapsulation ..................................................................5-4

Selecting a CS PDU Encapsulation .........................................................................5-4

Enabling or Disabling the Multicast Function ..................................................................5-5

Where to Go Next ...........................................................................................................5-5

Appendix A Site Manager Parameter Descriptions

Virtual Path and Virtual Circuit Parameters ................................................................... A-1

Interface Parameters ..................................................................................................... A-2

PVC Parameters ............................................................................................................ A-5

Where to Go Next ..........................................................................................................A-8

Appendix B Site Manager Default Settings

Where to Go Next ..........................................................................................................B-2

Index

114057 Rev. A vii

Page 8

viii 114057 Rev. A

Page 9

Figures

Figure 2-1. How ATM DXI Works ................................................................................2-2

Figure 2-2. AAL Layer Division between Bridge/Router and DSU/CSU .....................2-4

Figure 2-3. DXI Modes of Operation ..........................................................................2-8

Figure 2-4. Group Access Mode ................................................................................2-9

Figure 2-5. Direct Access Mode ...............................................................................2-10

Figure 2-6. Hybrid Access Mode ..............................................................................2-11

Figure 2-7. Example of a Bridged Network ..............................................................2-13

Figure 2-8. Multipath Network ..................................................................................2-14

Figure 2-9. B-ISDN ATM Protocol Reference Model ................................................2-15

Figure 2-10. ATM Adaptation Layer 3/4 ......................................................................2-16

Figure 2-11. ATM Adaptation Layer 5 .........................................................................2-17

Figure 2-12. ATM Transmission Components ............................................................2-19

114057 Rev. A ix

Page 10

Page 11

Tables

Table 3-1. Locating a Protocol Menu ........................................................................3-3

Table B-1. ATM DXI Interface List Window ...............................................................B-1

Table B-2. ATM DXI Virtual Circuit Window .............................................................. B-1

Table B-3. ATM DXI PVC List Window .....................................................................B-2

114057 Rev. A xi

Page 12

Page 13

About This Guide

This guide offers

• Instructions for starting a default Asynchronous Transfer Mode (ATM) Data Exchange Interface (DXI) conﬁguration on a synchronous interface

Chapter 1)

(

• A general overview of ATM DXI technology and a list of additional resources that describe this technology (

Chapter 2)

• Speciﬁc features of ATM DXI and how we implement them (

• Instructions on how to customize an ATM DXI interface (

• Instructions on how to customize ATM DXI PVCs (

• Descriptions of ATM DXI parameters and how you edit them (

• A list of parameter default settings for ATM DXI and ATM (

Before You Begin

Before using this guide, you must complete the following procedures. For a new router:

• Install the router (refer to the installation manual that came with your router).

• Connect the router to the network and create a pilot conﬁguration ﬁle (refer to

Quick-Starting Routers, Connecting AN and ANH Systems to a Network, or Connecting ASN Routers to a Network).

Make sure that you are running the latest version of Bay Networks Site Manager and router software. For instructions, refer to Upgrading Routers from Version 7–8.00 to Version 11.0.

Chapter 3)

Chapter 4)

Chapter 5)

Appendix A)

Appendix B)

114057 Rev. A xiii

Page 14

Configuring ATM DXI Services

Conventions

angle brackets (< >) Indicate that you choose the text to enter based on the

bold text Indicates text that you need to enter, command names,

brackets ([ ]) Indicate optional elements. You can choose none, one,

ellipsis points Horizontal (. . .) and vertical ellipsis points indicate

description inside the brackets. Do not type the brackets when entering the command. Example: if command syntax is you enter

ping 192.32.10.12

<ip_address>

ping

and buttons in menu paths. Example: Enter

wfsm &

Example: Use the dinfo command. Example: ATM DXI > Interfaces > PVCs identiﬁes the

PVCs button in the window that appears when you select the Interfaces option from the ATM DXI menu.

or all of the options.

)

(

omitted information.

italic text Indicates variable values in command syntax

descriptions, new terms, ﬁle and directory names, and book titles.

quotation marks (“ ”) Indicate the title of a chapter or section within a book.

screen text Indicates data that appears on the screen.

Example:

Set Bay Networks Trap Monitor Filters

separator ( > ) Separates menu and option names in instructions and

internal pin-to-pin wire connections. Example: Protocols > AppleTalk identiﬁes the AppleTalk option in the Protocols menu.

Example: Pin 7 > 19 > 20

vertical line (|) Indicates that you enter only one of the parts of the

command. The vertical line separates choices. Do not type the vertical line when entering the command. Example: If the command syntax is

show at routes | nets, you enter either show at routes or show at nets, but not both.

xiv 114057 Rev. A

Page 15

Acronyms

About This Guide

AAL ATM adaptation layer ALC Adaptation Layer Controller ARP Address Resolution Protocol ATM Asynchronous Transfer Mode B-ISDN Broadband Integrated Services Digital Network CPCS common part convergence sublayer CS convergence sublayer CSU channel service unit DCE data communications equipment DSU data service unit DTE data terminal equipment DXI Data Exchange Interface FRE Fast Routing Engine ILI Intelligent Link Interface ILMI Interim Local Management Interface IP Internet Protocol ITU-T International Telecommunications Union –

Telecommunication Standardization Sector LMI Local Management Interface MAC media access control OSI Open Systems Interconnection OSPF Open Shortest Path First PDU protocol data unit PVC permanent virtual circuit SAP service access point SAR segmentation and reassembly SDU service data unit SMDS switched multimegabit data service SNAP Subnetwork Access Protocol SNMP Simple Network Management Protocol VC virtual circuit VCC virtual channel connection

114057 Rev. A xv

Page 16

Configuring ATM DXI Services

VCI virtual channel identiﬁer VPC virtual path connection VPI virtual path identiﬁer WAN wide area network

Ordering Bay Networks Publications

To purchase additional copies of this document or other Bay Networks publications, order by part number from the Bay Networks Press telephone or fax numbers:

• Telephone 1-800-845-9523

• Fax (United States/Canada) 1-800-582-8000

• Fax (International) 1-916-939-1010 You can also use these numbers to request a free catalog of Bay Networks Press

product publications.

™

at the following

xvi 114057 Rev. A

Page 17

Technical Support and Online Services

To ensure comprehensive network support to our customers and partners worldwide, Bay Networks Customer Service has Technical Response Centers in key locations around the globe:

• Billerica, Massachusetts

• Santa Clara, California

• Sydney, Australia

• Tokyo, Japan

• Valbonne, France The Technical Response Centers are connected via a redundant Frame Relay

Network to a Common Problem Resolution system, enabling them to transmit and share information, and to provide live, around-the-clock support 365 days a year.

Bay Networks Information Services complement the Bay Networks Service program portfolio by giving customers and partners access to the most current technical and support information through a choice of access/retrieval means. These include the World Wide Web, CompuServe, Support Source CD, Customer Support FTP, and InfoFACTS document fax service.

114057 Rev. A xvii

Page 18

Configuring ATM DXI Services

Bay Networks Customer Service

If you purchased your Bay Networks product from a distributor or authorized reseller, contact that distributor’s or reseller’s technical support staff for assistance with installation, conﬁguration, troubleshooting, or integration issues.

Customers can also purchase direct support from Bay Networks through a variety of service programs. As part of our PhonePlus™ program, Bay Networks Service sets the industry standard, with 24-hour, 7-days-a-week telephone support available worldwide at no extra cost. Our complete range of contract and noncontract services also includes equipment staging and integration, installation support, on-site services, and replacement parts delivery -- within approximately 4 hours.

To purchase any of the Bay Networks support programs, or if you have questions on program features, use the following numbers:

Region Telephone Number Fax Number

United States and Canada

1-800-2LANWAN; enter Express Routing Code (ERC) 290 when prompted

(508) 670-8766

(508) 436-8880 (direct) Europe (33) 92-968-300 (33) 92-968-301 Asia/Paciﬁc Region (612) 9927-8800 (612) 9927-8811 Latin America (407) 997-1713 (407) 997-1714

In addition, you can receive information on support programs from your local Bay Networks ﬁeld sales ofﬁce, or purchase Bay Networks support directly from your authorized partner.

xviii 114057 Rev. A

Page 19

Bay Networks Information Services

Bay Networks Information Services provide up-to-date support information as a ﬁrst-line resource for network administration, expansion, and maintenance. This information is available from a variety of sources.

World Wide Web

The Bay Networks Customer Support Web Server offers a diverse library of technical documents, software agents, and other important technical information to Bay Networks customers and partners.

A special beneﬁt for contracted customers and resellers is the ability to access the Web Server to perform Case Management. This feature enables your support staff to interact directly with the network experts in our worldwide Technical Response Centers. A registered contact with a valid Site ID can

• View a listing of support cases and determine the current status of any open case. Case history data includes severity designation, and telephone, e-mail, or other logs associated with the case.

Technical Support and Online Services

• Customize the listing of cases according to a variety of criteria, including date, severity, status, and case ID.

• Log notes to existing open cases.

• Create new cases for rapid, efﬁcient handling of noncritical network situations.

• Communicate directly via e-mail with the speciﬁc technical resources assigned to your case.

The Bay Networks URL is http://www.baynetworks.com. Customer Service is a menu item on that home page.

Customer Service FTP

Accessible via URL ftp://support.baynetworks.com (134.177.3.26), this site combines and organizes support ﬁles and documentation from across the Bay Networks product suite, including switching products from our Centillion™

and Xylogics site lets you quickly locate information on any of your Bay Networks products.

114057 Rev. A xix

business units. Central management and sponsorship of this FTP

Page 20

Configuring ATM DXI Services

Support Source CD

This CD-ROM -- sent quarterly to all contracted customers -- is a complete Bay Networks Service troubleshooting knowledge database with an intelligent text search engine.

The Support Source CD contains extracts from our problem-tracking database; information from the Bay Networks Forum on CompuServe; comprehensive technical documentation, such as Customer Support Bulletins, Release Notes, software patches and ﬁxes; and complete information on all Bay Networks Service programs.

You can run a single version on Macintosh Windows 3.1, Windows 95, Windows NT, DOS, or UNIX computing platforms. A Web links feature enables you to go directly from the CD to various Bay Networks Web pages.

CompuServe

For assistance with noncritical network support issues, Bay Networks Information Services maintain an active forum on CompuServe, a global bulletin-board system. This forum provides ﬁle services, technology conferences, and a message section to get assistance from other users.

The message section is monitored by Bay Networks engineers, who provide assistance wherever possible. Customers and resellers holding Bay Networks service contracts also have access to special libraries for advanced levels of support documentation and software. To take advantage of CompuServe’s recently enhanced menu options, the Bay Networks Forum has been re-engineered to allow links to our Web sites and FTP sites.

We recommend the use of CompuServe Information Manager software to access these Bay Networks Information Services resources. To open an account and receive a local dial-up number in the United States, call CompuServe at 1-800-524-3388. Outside the United States, call 1-614-529-1349, or your nearest CompuServe ofﬁce. Ask for Representative No. 591. When you are on line with your CompuServe account, you can reach us with the command

xx 114057 Rev. A

GO BAYNET.

Page 21

InfoFACTS

InfoFACTS is the Bay Networks free 24-hour fax-on-demand service. This automated system has libraries of technical and product documents designed to help you manage and troubleshoot your Bay Networks products. The system responds to a fax from the caller or to a third party within minutes of being accessed.

To use InfoFACTS in the United States or Canada, call toll-free 1-800-786-3228. Outside North America, toll calls can be made to 1-408-764-1002. In Europe, toll-free numbers are also available for contacting both InfoFACTS and CompuServe. Please check our Web page for the listing in your country.

How to Get Help

Use the following numbers to reach your Bay Networks Technical Response Center:

Technical Response Center Telephone Number Fax Number

Billerica, MA 1-800-2LANWAN (508) 670-8765 Santa Clara, CA 1-800-2LANWAN (408) 764-1188 Valbonne, France (33) 92-968-968 (33) 92-966-998 Sydney, Australia (612) 9927-8800 (612) 9927-8811 Tokyo, Japan (81) 3-5402-0180 (81) 3-5402-0173

Technical Support and Online Services

114057 Rev. A xxi

Page 22

Page 23

This chapter describes how to set up a synchronous interface to run the default ATM DXI conﬁguration.

Before You Begin

Before you can start ATM DXI on your router, you must

1. Open a conﬁguration ﬁle.

2. Specify router hardware (if using a local mode conﬁguration ﬁle).

3. Select the link or net module interface on which you are enabling ATM DXI.

Chapter 1

Starting ATM DXI

If you have questions about how to perform any of these preliminary tasks, refer to Conﬁguring Routers.

The Technician Interface allows you to modify parameters by issuing

commit commands with the MIB object ID. This process is equivalent to

modifying parameters using Site Manager. For more information about using the Technician Interface to access the MIB,

refer to Using Technician Interface Software.

Caution: The Technician Interface does not validate parameter entries.

Entering an invalid value can corrupt your conﬁguration.

114057 Rev. A 1-1

set and

Page 24

Configuring ATM DXI Services

Adding ATM DXI to the Router

Adding ATM DXI on a router requires

Creating an ATM DXI Circuit

Enabling Protocols on an ATM DXI Circuit

Adding PVCs to an ATM DXI Circuit

T o edit the ATM DXI Interface parameters, which deﬁne the A TM interf ace to the physical line, refer to Chapter 4.

Creating an ATM DXI Circuit

To create an ATM DXI circuit on an interface:

1. Select ATM DXI from the WAN Protocols window.

Note: The WAN Protocols window opens after you select a link or net module

connector that requires a WAN protocol.

2. Click on OK.

Site Manager creates the global framework for an ATM DXI circuit.

Enabling Protocols on an ATM DXI Circuit

To enable protocols on the ATM DXI circuit:

1. Select the protocols you want to enable on this circuit from the Select

Protocols window.

2. Click on OK.

For each protocol you select, the Conﬁguration Manager displays a protocol-speciﬁc window prompting you for required information. If you need assistance in responding to any queries, consult the appropriate conﬁguration guide.

When you ﬁnish conﬁguring the protocols, Site Manager displays the Conﬁguration Manager window.

1-2 114057 Rev. A

Page 25

Adding PVCs to an ATM DXI Circuit

You must add at least one PVC to an ATM DXI circuit for it to function. To add a PVC:

1. From the Conﬁguration Manager window , select Pr otocols > ATM DXI >

Interfaces.

The ATM DXI Interface List window opens. The new ATM DXI interface appears highlighted at the top of the window.

Caution: The DXI mode default setting (Mode 1A) deﬁnes speciﬁc virtual

path identiﬁer (VPI) and virtual channel identiﬁer (VCI) ranges for this PVC. Make sure you want to use DXI Mode 1A before continuing. Refer to “Changing the DXI Mode,” in Chapter 4, for more information about modifying the DXI mode setting.

2. Click on the PVCs button.

The ATM DXI PVC List window opens.

3. Click on Add.

Starting ATM DXI

The ATM DXI Virtual Circuit window opens.

4. Supply the following information:

• A VPI (virtual path identiﬁer) number. You must enter a valid VPI

number. The range for the VPI number varies depending on the DXI Mode speciﬁed in the ATM DXI Interface List window. Since we are using the default DXI Mode in this section, enter a value between 0 and 15 for the VPI number.

Site Manager: VPI Number: page A-1

• A VCI (virtual circuit identiﬁer) number. You must enter a valid VCI

number. The range for the VCI number varies depending on the DXI Mode speciﬁed in the ATM DXI Interface List window. Since we are using the default DXI Mode in this section, enter a value between 32 and 63 for the VCI number.

Site Manager: VCI Number: page A-2

114057 Rev. A 1-3

Page 26

Configuring ATM DXI Services

Note: A TM DXI does not allo w duplicate VPI/VCI pairs on the same physical

interface. Howev er , duplicate VPI/VCI pairs can exist as long as the y reside on separate physical interfaces.

5. Click on OK.

Site Manager returns you to the ATM DXI PVC List window. The default mode of the PVC you just added is GROUP ACCESS. If you want to change any of the parameters on the ATM DXI PVC List window, refer to Chapter 5, “Customizing ATM DXI PVCs,” for instructions.

Note: To add another PVC with the default conﬁguration, repeat Steps 3, 4,

and 5. When you ﬁnish adding PVCs, go to Step 6.

6. Click on Done.

Site Manager returns you to the ATM DXI Interface List window.

7. Click on Done.

Site Manager returns you to the Conﬁguration Manager window.

Deleting ATM DXI from the Router

To delete ATM DXI from all interfaces on the router:

1. From the Conﬁguration Manager window , select Pr otocols > ATM DXI >

Delete ATM.

Site Manager asks

Do you REALLY want to delete ATM?

2. Click on OK.

Site Manager deletes ATM DXI from the router and returns to the Conﬁguration Manager window.

Note: Refer to Chapter 5 for instructions on how to delete individual PVCs

from an ATM DXI interface.

1-4 114057 Rev. A

Page 27

Where to Go Next

Use the following table to determine where you want to go next.

For information about Go to

General ATM DXI information Chapter 2 Speciﬁc ATM DXI features and how we implement them Chapter 3 Customizing an ATM DXI interface Chapter4 Customizing ATM DXI PVCs Chapter 5 Site Manager parameter descriptions Appendix A Site Manager defaults Appendix B

Starting ATM DXI

114057 Rev. A 1-5

Page 28

Page 29

This chapter discusses the concepts behind the ATM Data Exchange Interface (DXI) protocol and how we implement this service in Bay Networks routers.

In this chapter, you can

• Read more about ATM DXI and how it works

• Read about the kinds of support that a router running ATM DXI provides

• Review the notes describing how Bay Networks implements special ATM DXI features.

ATM DXI versus ATM

Chapter 2

Understanding ATM DXI Concepts

You can access an ATM network using a synchronous (that is, HSSI, V.35, or RS-449) connection or a direct ATM connection. When using a synchronous connection, you must use ATM DXI.

Unlike an ATM interface that connects directly to an ATM network, a Bay

Networks synchronous link module works with a Fast Routing Engine (FRE FRE-2) to form an Intelligent Link Interface (ILI) pair. This ILI pair uses ATM DXI as a wide area network (WAN) protocol to connect to an ATM data service unit/channel service unit (DSU/CSU). The DSU/CSU then converts these pack ets into uniform 53-byte cells for transmission over the ATM network (

114057 Rev. A 2-1

Figure 2-1).

Page 30

Configuring ATM DXI Services

T1 or T3 T1 or T3

DSU/CSU DSU/CSU

HSSI or V.35/RS-449

Figure 2-1. How ATM DXI Works

ATM DXI Support

A router running ATM DXI provides the following support:

• Routing IP, IPX, XNS, DECnet Phase IV, AppleTalk, and VINES trafﬁc over the ATM network

• MAC-level transparent bridging over the ATM network

ATM

network

RouterRouter

ATM0007A

• Multiprotocol encapsulation functions deﬁned in RFC 1294 and RFC 1483, enabling concurrent bridging and multiprotocol routing support on the same PVC

• A convergence sublayer (CS) function compatible with AAL 3/4 and AAL 5 as deﬁned in Section 1 of the ITU-T (formerly CCITT) B-ISDN Protocol Reference Model (PRM)

• Error checking

• ATM DXI Link Management Interface (LMI), including Simple Network Management Protocol (SNMP) Proxy support -- a proprietary version of the LMI -- available only when using Mode 2 Proprietary DXI encapsulation with a Digital Link DSU/CSU.

• Broadcasting and multicasting support

2-2 114057 Rev. A

Page 31

• Address Resolution Protocol (ARP) and Inverse ARP support

The DSU/CSU supports the following layers:

• Segmentation and Reassembly (SAR) sublayer of the ATM adaptation layer (AAL)

• ATM layer deﬁned in the B-ISDN PRM

• Physical layer interface to the ATM network through DS1 and DS3

Multiprotocol Encapsulation

Multiprotocol encapsulation enables the router to multiplex and demultiplex bridged or routed protocol data units (PDUs).

For transmission, this function adds a header from 2 through 8 octets in length to the PDU to allow decoding. The decoding process determines the proper service access point (SAP).

When receiving packets, this function evaluates the header to determine whether the PDU is a valid routed or bridged packet. If it is valid, this function then strips the header from the packet and passes it to the appropriate SAP for routing or bridging.

Understanding ATM DXI Concepts

AAL Sublayer Support

The CS in the router logically connects to the SAR in the DSU/CSU using a common interface deﬁned by the ATM DXI protocol. The ATM DXI protocol interface transfers PDUs between the CS and the SAR. Figure 2-2 shows the functional division of the AAL sublayers between the router and the DSU/CSU.

114057 Rev. A 2-3

Page 32

Configuring ATM DXI Services

Bridge/Router

Upper

Layer

Protocols

Multiprotocol

Encapsulation

Convergence

Sublayer

ATM DXI

Figure 2-2. AAL Layer Division between Bridge/Router and DSU/CSU

ATM DXI Error Checking

The ATM DXI veriﬁes

• That the VPI/VCI is valid for the PVCs conﬁgured for that ATM circuit.

• The header format that the value of the DXI Mode parameter deﬁnes.

• That the BTag ﬁeld in the CS_PDU header is equal to the ETag ﬁeld in the CS_PDU trailer and ensures that the frame size is valid. If the packet contains an invalid header, the router drops the packet, updates the appropriate MIB statistic, and logs the appropriate event.

DSU/CSU

ATM DXI

SAR

Sublayer

ATM

Layer

Physical

Layer

AAL

ATM0008A

2-4 114057 Rev. A

Page 33

Refer to “ATM DXI Modes of Operation,” later in this chapter for details.

Note: The ETag and BTag ﬁelds verify that the reassembled AAL3/4 common

part convergence sublayer (CPCS) frame is not just two frames concatenated together. If these two ﬁelds do not match, then the frame is most likely the concatenation of two frames.

ATM DXI LMI Support

The router supports a proprietary version of the ATM DXI Local Management Interface (LMI). This proprietary version of the LMI was a precursor to the standardized ATM Forum version.

LMI uses an SNMP-like protocol to query network management statistics maintained on the DSU/CSU MIB. The DSU/CSU may also send asynchronous events in the form of trap messages to the router.

Simulated Multicast Packet Support

ATM DXI supports multicast packets, enabling the router to take advantage of multicast functionality , if it is av ailable from the ATM network. ATM multicasting reserves select network-assigned VPIs/VCIs as multicast addresses. The ATM network maps multiple recipients to a single VPI/VCI and delivers copies of all ATM cells to each member of the address group. As a cell passes through the ATM network, the network manipulates the cell to reveal the actual source to the cell recipient.

Understanding ATM DXI Concepts

If no multicast address is available for the protocol (because the network interf ace has direct PVC access, you have not set up the service yet, or the VPI/VCI has not been entered in the Adjacent Host Table), ATM DXI simulates a broadcast packet by forwarding a copy of the message to each known PVC.

Simulated multicasting is generally used in certain address resolution techniques and for applications that require the delivery of identical information to multiple recipients.

114057 Rev. A 2-5

Page 34

Configuring ATM DXI Services

ARP and Inverse ARP Support

ATM DXI supports the Address Resolution Protocol (ARP), enabling the router to dynamically resolve IP network layer protocol-to-VPI/VCI address mappings. ATM DXI learns the PVC address by detecting the PVC that received the ARP response.

ATM DXI also supports Inverse ARP. However, you can only use Inverse ARP if both the local and remote router support it.

Bay Networks uses proprietary methods for ARP and Inverse ARP. These methods are incompatible with third-party equipment (that is, equipment using the speciﬁcations in RFC 1577).

ATM DXI Implementation Notes

Some special features follow regarding how Bay Networks implements ATM DXI. We recommend that you read this section before attempting to customize your ATM DXI interface or PVCs.

Conﬁguring Synchronous Lines for ATM DXI

If you enable ATM DXI on a circuit, Site Manager automatically sets synchronous line parameters as follows:

Parameter Value

BOFL Disable Promiscuous Enable Service Transparent WAN Protocol ATM DXI

For more information about these parameters, refer to Conﬁguring Line Services.

2-6 114057 Rev. A

Page 35

ATM DXI Modes of Operation

The ATM Forum’s ATM DXI speciﬁcation deﬁnes three modes of operation, each with a different set of operations and data transfer between the data terminal equipment (DTE; that is, the router) and the data communications equipment (DCE; that is, the DSU/CSU). The combination of the router link module and the DSU/CSU provides a User-to-Network Interface (UNI) to the ATM network.

The modes of operation are as follows:

Mode 1A

Using this mode, the DTE encapsulates the DTE service data unit (SDU) into a DXI frame and transmits it to the DCE. This mode operates with AAL 5 only . No AAL 5 functions are performed by the DTE; the DCE performs the AAL 5 and ATM layer functions.

Mode 1B

This mode serves the same purpose as Mode 1A but offers additional support for AAL 3/4 for at least one VPI/VCI.

Understanding ATM DXI Concepts

Mode 2

This mode allows the DTE to perform the AAL 3/4 CPCS encapsulation for the DTE SDU, then puts this PDU into an ATM DXI frame. The DSU/CSU then modiﬁes the frame to support either AAL 3/4 or AAL 5.

The DSU/CSU performs AAL functions based on whether the virtual channel connection is set for AAL 3/4 or AAL 5.

Mode 2 Proprietary

In addition to the three modes described by the ATM Forum, our implementation of the ATM DXI speciﬁcation deﬁnes a fourth mode of operation: Mode 2 Proprietary.

This mode is a proprietary version of Mode 2 used prior to the development of ATM Forum’s standard Mode 2. This version of Mode 2 has some DXI header differences from the standard Mode 2 and it handles only AAL 3/4.

114057 Rev. A 2-7

Page 36

Configuring ATM DXI Services

Note: Use this mode if your conﬁguration uses pre-ATM Forum DXI

DSU/CSU devices (for example, a Digital Link DL3200).

Figure 2-3 illustrates how each mode handles data transfer from the router to the DSU/CSU.

Mode 1A Mode 1B Mode 2/Mode 2 Proprietary

Mode 1A

DSU/CSU DSU/CSUDSU/CSU

AAL 5 AAL 5 AAL 3/4 AAL 5 AAL 3/4

Mode 1B

Figure 2-3. DXI Modes of Operation

To select a mode for your router, conﬁgure the DXI Mode parameter (refer to “Interface Parameters” in Appendix A for details).

Mode 1B

AAL 3/4

Mode 2 Mode 2

AAL 3/4

ATM0009A

2-8 114057 Rev. A

Page 37

Access Modes for ATM DXI Services

You can enable each ATM PVC to function in one of three access modes: group access, direct access,orhybrid access. Within the same ATM physical interface

you can conﬁgure PVCs to use different modes. The following sections describe the access modes.

Group Access Mode

In group access mode, upper-layer protocols treat each ATM network interface as a single access point to the switched network. They use a single network address to send all trafﬁc destined for the switched network to the ATM network interface. Figure 2-4 shows a conceptual drawing of group access mode (the default).

Upper layer protocol

ATM network interface

PVC PVC

Understanding ATM DXI Concepts

Site A

ATM

network

Site B

Site C

Site D

ATM0010A

Figure 2-4. Group Access Mode

Group access supports the following protocols: IP, IPX, XNS, DECnet Phase IV, AppleTalk, VINES, and transparent bridging. Of the three modes, group access uses network addressing most efﬁciently and is the easiest to conﬁgure. Although you need to conﬁgure each PVC manually for group access mode, you need only deﬁne and associate protocols with the ATM network interface. All the group access mode PVCs you conﬁgure for a given ATM interface carry the protocols you select and conﬁgure to run on that interface.

Note: When you conﬁgure group access mode, the PVCs all use the AAL type

that you set for the ATM DXI interface (that is, the value of the CS PDU Encapsulation parameter set in the ATM DXI Interface List window).

114057 Rev. A 2-9

Page 38

Configuring ATM DXI Services

In a bridged environment, use group access only for fully meshed conﬁgurations, or in hub/spoke environments in which the spokes need not communicate. In a nonbridged environment, you can use group access in any conﬁguration that does not require protocols residing on separate PVCs (that is, where all PVCs accept the same protocols).

Group access works best in either fully meshed environments or in nonmeshed environments where systems not directly connected to each other ha v e no need to communicate. There are, however, ways to conﬁgure upper-layer protocols, like IP or IPX, to allow systems in nonmeshed networks to fully communicate. Refer to the appropriate upper-layer protocol documentation for more information.

Direct Access Mode

In direct access mode, upper-layer protocols treat the ATM network as a series of point-to-point connections (Figure 2-5). The upper-layer protocols view each PVC as an individual network interface. You can, therefore, conﬁgure each direct mode PVC individually. This is helpful if you have different network sites using different types of data encapsulation.

Upper layer protocol

PVC

ATM

network

Site A

Site B

Site C

Site D

ATM0011A

Figure 2-5. Direct Access Mode

Direct access supports the following protocols: IP, IPX, XNS, DECnet Phase IV, AppleTalk, VINES, and bridging. If you use direct access mode, you must conﬁgure each PVC manually and assign protocols to run on each PVC. This mode allows you to dedicate a PVC to a particular protocol, but at the expense of some conﬁguration overhead, memory, and address space.

2-10 114057 Rev. A

Page 39

Understanding ATM DXI Concepts

Direct access mode is best suited to small, nonmeshed conﬁgurations, or to conﬁgurations in which protocols must reside on separate PVCs.

Note: Be aware that the maximum number of PVCs you can conﬁgure in

direct access mode varies, depending on the conﬁguration of the router, the number of protocols running on the circuits, and the number of routing entries.

Hybrid Access Mode

Hybrid access mode combines characteristics of group and direct access modes. It works best for nonmeshed network conﬁgurations that use both bridging and routing over a single ATM DXI interface. This mode is also best for spanning tree bridging.

If your network combines bridging and routing over the same interface, you not only need PVCs in group access mode for routing, but you also need bridging to operate over these same PVCs. Since group access mode does not allow for bridging in nonmeshed environments, you must use hybrid access mode. In this mode, a PVC behaves like a direct access PVC for bridging while maintaining group access characteristics for routing protocols (Figure 2-6).

Bridge protocol sees two interfaces to the network

Routing protocol

I = Interface

Bridge

protocol

Routing protocol sees one interface to the network

ATM network interface

Hybrid PVC

Direction of data

SITE A

ATM Network

SITE B

ATM0012A

Figure 2-6. Hybrid Access Mode

114057 Rev. A 2-11

Page 40

Configuring ATM DXI Services

For hybrid access mode, you must conﬁgure all PVCs manually and assign bridging protocols to run on each PVC. Hybrid access supports all protocols that are available for the ATM interface: IP, IPX, XNS, DECnet Phase IV, AppleTalk, VINES, and bridging.

Note: When you select hybrid access mode for a PVC, Site Manager provides

only three protocol options: Bridge, Spanning Tree, and Native Mode LAN (NML). These protocols, as well as the protocols that are on the ATM interface, can run on the PVC.

Before you conﬁgure hybrid access on your router, carefully e valuate the types of routers you are connecting in your network. For example, combining Series 7 routers running in group access bridge mode with Series 7 (or later) routers running in hybrid access mode may cause broadcasting or spanning tree problems. If you plan to conﬁgure such a network, contact the Bay Networks Technical Response Center.

Using Hybrid Access for Transparent Bridging

In Figure 2-7, trafﬁc bridges between Sites A and B. The bridge (Router 1) runs on an ATM DXI interface and its conﬁguration deﬁnes the PVCs as group access mode. In the ﬁgure:

1. The bridge receives data from Site A.

2. If the bridge does not recognize the destination address, it tries to direct trafﬁc through another bridge port.

3. With the PVCs in group access mode, the ATM bridge port views the paths to Site A and Site B as the same.

4. Because the bridge does not send out data on the same bridge port from which it just received it, the bridge does not direct the data to Site B.

5. As a result, in this example, you need to use hybrid access mode.

2-12 114057 Rev. A

Page 41

Understanding ATM DXI Concepts

Site A Site B

Bridge port sees one path to Sites A and B

Router 1

ATM network

Figure 2-7. Example of a Bridged Network

If you deﬁne the PVCs to be in hybrid access mode (refer to Figure 2-6), each PVC acts as a bridge port. This enables the bridge running on the ATM interface to view the trafﬁc from Site A as arriving on a different port than that of Site B. When the bridge sends out data, it now has access to all of its ports, including the port that accesses Site B. Therefore, data from Site A can reach Site B.

Router 2

Router 3

ATM0013A

Using Hybrid Access for Routing

In hybrid access mode, routing protocols view the ATM network interface in terms of group access PVCs, as described in the “

Group Access Mode” section,

earlier in this chapter.

ATM DXI and Multipath Support

Our implementation of ATM DXI provides multipath redundancy. This means, for example, that if there are two physical lines and one line fails, the other takes o ver the task of transmission (redundancy). If both lines are working, the router uses both lines simultaneously (multipath).

114057 Rev. A 2-13

Page 42

Configuring ATM DXI Services

The multipath feature lets you group several lines that back up one another to ensure that information makes it across the network. Figure 2-8 shows a network with two physical links across the ATM network.

Path A

Router

Path B

Figure 2-8. Multipath Network

ATM network

Router

ATM0014A

In this example, when the router receives trafﬁc destined for the network, it alternately chooses Path A or Path B, at random, to transmit the data. The router uses both lines, simultaneously, to balance the load. If one of these connections fails, the router uses the remaining path.

You can conﬁgure multipath for direct access mode PVCs only. The most signiﬁcant part of conﬁguring multipath is how you set a PVC’s VPI/VCI pair. This number identiﬁes each PVC, thereby identifying a path for the router to direct data out to the network.

See “Setting PVCs for Multipath Mode,” in Chapter 3 for instructions on conﬁguring multiple PVCs to run in multipath mode.

Note: If you use multipath mode, packets traveling on the two paths may

arrive at their destination out of sequence. Some protocols do not tolerate packets arriving out of sequence. As a result, you may experience poor performance or failures.

2-14 114057 Rev. A

Page 43

ATM Layers

Understanding ATM DXI Concepts

The B-ISDN protocol reference model, on which ATM is based, consists of four layers. Each layer communicates only with the layer either directly above it or directly below it. Figure 2-9 shows the B-ISDN ATM protocol reference model.

Higher Protocol Layer

Convergence sublayer (CS)

Segmentation and reassembly sublayer (SAR)

ATM Layer

Transmission convergence sublayer

Physical medium dependent sublayer (PMD)

ATM

adaptation

layer

(AAL)

Physical

layer

(PHY)

ATM0003A

Figure 2-9. B-ISDN ATM Protocol Reference Model

The following layers relate directly to how Bay Networks routers support ATM DXI:

• ATM layer

• ATM adaptation layer (AAL)

The ATM layer deﬁnes how two nodes transmit information between them. It is concerned with the format and size of the cells and the contents of the headers. The addresses of the cells are meaningful only to the two adjacent local nodes (that is, usually not to the end nodes).

The ATM adaptation layer (AAL) conv erts higher -layer protocol data into formats that are compatible with the requirements of the ATM layer, enabling ATM to handle different types of information all within the same format.

114057 Rev. A 2-15

Page 44

Configuring ATM DXI Services

The AAL is divided into two sublayers: the convergence sublayer (CS) and the segmentation and reassembly (SAR) sublayer. These two sublayers convert

variable-length messages into 48-byte segments, while ensuring the integrity of the data.

The CCITT (now ITU-T) has deﬁned different types of AALs to handle different kinds of trafﬁc. Bay Networks routers support AAL 3/4 and AAL 5. The next tw o sections describe the AAL process.

AAL 3/4

In the AAL 3/4 process, a convergence sublayer (CS) header and trailer envelop the data from the higher layer protocols, creating a CS protocol data unit (PDU).

AAL 3/4 divides the PDU into 44-octet segments. Each segment is encapsulated with a segmentation and reassembly (SAR) header and trailer, creating a 48-octet SAR PDU. This 48-octet SAR PDU is the payload of the ATM cell (Figure 2-10).

Service class

AAL

ATM Layer

AAL 3/4

Convergence

sublayer

AAL 3/4

SAR

layer

Header

SAR PDU

Header

ATM cell

Service data unit (SDU)

SDU

SAR PDU

Trailer

ATM cell

Trailer

SAR PDU

ATM cell

ATM0004A

Figure 2-10. ATM Adaptation Layer 3/4

2-16 114057 Rev. A

Page 45

AAL 5

Understanding ATM DXI Concepts

In AAL 5, only a trailer attaches to the data from the higher layer protocols to create a CS PDU. AAL 5 divides the PDU into a 48-octet SAR PDU; however, it does not add an SAR header and trailer. This 48-octet SAR PDU becomes the payload of the ATM cell (Figure 2-11).

Service class

AAL 5

Convergence

sublayer

AAL layer

AAL 5

SAR

layer

ATM layer

Note: AAL 5 does not attach an SAR header or trailer to the PDU.

SAR PDU

ATM cell

Figure 2-11. ATM Adaptation Layer 5

Service data unit (SDU)

SDU

SAR PDU

ATM cell

Trailer

SAR PDU

ATM cell

ATM0005A

114057 Rev. A 2-17

Page 46

Configuring ATM DXI Services

Data Transmission

Data transmission (also called cell switching) through the ATM network relies on the establishment of logical connections between ATM entities. ATM is a connection-oriented service. This means that an ATM entity cannot transmit information until it establishes a connection with a receiving entity. These connections consist of virtual channels, virtual paths, and transmission paths.

A virtual channel is a logical connection between two communicating ATM entities. Each virtual channel may carry a different protocol or trafﬁc type. The virtual channel transports cells that have a common identiﬁer. The identiﬁer is called the virtual channel identiﬁer (VCI) and is part of the cell header. You can establish virtual channels permanently or set them up dynamically, allowing the network to adjust itself to the trafﬁc demand.

A virtual path is a set of virtual channels between a common source and destination. The virtual channels in a virtual path logically associate to a common identiﬁer. This identiﬁer is called the virtual path identiﬁer (VPI) and is part of the cell header. You can base cell switching on either the VPI alone, or on a combination of the VPI and VCI.

Virtual paths enable you to separate netw ork transport functions into those related to an individual logical connection (virtual channel) and those related to a group of logical connections (virtual path).

A transmission path is a physical connection that comprises several virtual paths, each virtual path containing several virtual channels. The transmission path may support multiple virtual paths across a single connection to the network.

Figure 2-12 shows the relationships between the virtual channel, the virtual path, and the transmission path.

2-18 114057 Rev. A

Page 47

Transmission path

Understanding ATM DXI Concepts

VP = Virtual path VC = Virtual channel

Figure 2-12. ATM Transmission Components

For More Information

For more information about ATM, refer to the following documents: ATM Forum. ATM Data Exchange Interface Speciﬁcation. Version 1.0. August

1993.

ATM Forum. ATM User-Network Interface Speciﬁcation. Version 3.0. September

1993.

VP VP

ATM0006A

Bellcore Document SR-NWT-001763, Issue 1. Preliminary Report on Broadband ISDN Transfer Protocols. December 1990.

———, FA-NWT-001109. Broadband ISDN Transport Network Elements Framework Generic Criteria. December 1990.

———, FA-NWT-001110. Broadband ISDN Switching System Framework Generic Criteria. December 1990.

Bradley, T., Brown, C., and Malis, A. Multiprotocol Interconnect over Frame Relay. RFC 1294. Network Working Group. January 1992.

De Prycker, M.Async hr onous T ransfer Mode: Solution for Br oadband ISDN. Ellis Horwood Limited, 1991.

114057 Rev. A 2-19

Page 48

Configuring ATM DXI Services

Handel, R. and Huber, M. Integrated Broadband Networks: An Introduction to ATM-Based Networks. Reading, Massachusetts: Addison-Wesley Publishing

Company, 1991. Heinanen, J. Multiprotocol Encapsulation over ATM Adaptation Layer 5.

RFC 1483. Network Working Group. July 1993.

Where to Go Next

Use the following table to determine where you want to go next.

For information about Go to

Starting ATM DXI Chapter 1 General ATM DXI information Speciﬁc ATM DXI features and how we implement them Chapter 3 Customizing an ATM DXI interface Chapter4 Customizing ATM DXI PVCs Chapter 5 Site Manager parameter descriptions Appendix A Site Manager defaults Appendix B

Chapter 2

2-20 114057 Rev. A

Page 49

This chapter provides some guidelines for using Site Manager ATM DXI windows. For more detailed instructions on speciﬁc Site Manager b uttons or menu selections, refer to Using Site Manager Software.

Adding or Copying PVCs

When adding or copying a PVC, keep the following in mind:

• Whether you add or copy a PVC, you can always customize it later.

• When you run PVCs in direct or hybrid access mode, the copy function copies all of the existing PVC-speciﬁc information to the new PVC. However, this function does not copy the protocols that you have selected and conﬁgured for that PVC. You must reselect and reconﬁgure any desired protocols for the newly copied PVC.

Chapter 3

ATM DXI Window Basics

Setting PVCs for Multipath Mode

Setting PVCs in Multipath Mode provides a form of redundancy. For example, if there are two physical lines and one line fails, the other takes over transmission (redundancy). If both lines are working, the router uses both lines simultaneously (multipath).

114057 Rev. A 3-1

Page 50

Configuring ATM DXI Services

The multipath feature lets you group two or more PVCs to ensure that information makes it across the network. When setting PVCs for multipath mode, keep the following in mind:

• The PVCs must have the same VCI and VPI numbers.

• You can only set direct access PVCs to operate in multipath mode.

To set PVCs to use multipath mode:

1. From the Conﬁguration Manager window , select Pr otocols > ATM DXI >

Interfaces.

The ATM DXI Interface List window opens.

2. Click on PVCs.

The ATM DXI PVC List window opens.

3. Select the ﬁrst PVC you want to run in multipath mode.

4. Click on Multipath.

The Multipath Selection window opens. This window shows all PVCs that you can set for multipath mode, along with the PVC you selected.

5. Select a PVC that you want to group with the ﬁrst PVC.

6. Click on Select.

The ATM DXI PVC List window opens.

7. Repeat this procedure until you select all of the PVCs that you want to

run in multipath mode.

3-2 114057 Rev. A

Page 51

Managing Protocols

As long as your interface contains at least one PVC, you can add, delete, or edit bridging/routing protocols. However, which protocol menu you use depends on the access mode of the PVC. use for each access mode.

Table 3-1. Locating a Protocol Menu

PVC Access Mode Circuit Deﬁnition Window ATM DXI PVC List Window

Group ✔ Hybrid ✔ Direct ✔

Use the following path to access the Circuit Deﬁnition window:

Conﬁguration Manager > Sync > Edit Circuit > Group Protocols

Use the following path to access the ATM DXI PVC List window:

ATM DXI Window Basics

Table 3-1 shows the appropriate protocol menu to

Conﬁguration Manager > Protocols > ATM DXI > Interfaces > PVCs > Protocols

For each protocol you add, you must enter any required protocol-speciﬁc information. If you need assistance in responding to any queries, consult the appropriate guide.

Note: Selecting the bridge protocol for a hybrid or direct mode PVC

automatically sets Multiprotocol Encapsulation to Enable.

114057 Rev. A 3-3

Page 52

Configuring ATM DXI Services

Where to Go Next

Use the following table to determine where you want to go next.

For information about Go to

Starting ATM DXI Chapter 1 General ATM DXI information Chapter 2 Customizing an ATM DXI interface Chapter4 Customizing ATM DXI PVCs Chapter 5 Site Manager parameter descriptions Appendix A Site Manager defaults Appendix B

3-4 114057 Rev. A

Page 53

Customizing an ATM DXI Interface

Once you add ATM DXI to your router, you may want to customize the ATM DXI interface for your speciﬁc network conﬁguration.

Note: Y ou must ﬁrst add ATM DXI to the router before you can customize the

ATM DXI interface. For instructions on how to start ATM DXI, or how to add additional ATM DXI interfaces, refer to Chapter 1.

Enabling or Disabling the Interface

By default, you enable the synchronous interface when you start ATM DXI. However, you can enable or disable the interface at any time.

Chapter 4

Site Manager: Enable: page A-2

Entering an Interface Description

Site Manager allows you to enter an alphanumeric description of the interface; the description can contain up to 63 alphanumeric characters or spaces. Though entering a description is optional, this management feature helps you easily identify the interface.

Site Manager: Interface Description: page A-2

114057 Rev. A 4-1

Page 54

Configuring ATM DXI Services

Changing the DXI Mode

The ATM DXI mode indicates the mode of operation for this interface based on the ATM Forum ATM Data Exchange Interface Speciﬁcation. Each mode relates to different functional settings between the router and the DSU/CSU.

Note: The DXI header size is different for Modes 1A and 1B than for Mode 2

and Mode 2 Proprietary. This difference affects the values that you can set for the VPI and VCI. Refer to “Setting a VPI Number” and “Setting a VCI Number” in Chapter 5 for the allowable VPI and VCI settings for each mode.

By default, the ATM DXI interface uses Mode 1A. This mode operates only with AAL 5 encapsulation. Refer to “ATM DXI Modes of Operation” in Chapter 2 for a detailed description of each mode.

Site Manager: DXI Mode: page A-3

Caution: When assigning data encapsulation to an interface, make sure that

the router encapsulation method matches that of the DSU/CSU.

Assigning a Maximum Number of Virtual Circuits

By default, ATM DXI allows for a maximum of 512 permanent virtual circuits on each interface; however, you can specify from 1 through 512 virtual circuits.

Site Manager: Max number of VCs: page A-3

4-2 114057 Rev. A

Page 55

Customizing an ATM DXI Interface

Assigning Data Encapsulation

The ATM DXI interface allows both multiprotocol encapsulation and CS PDU encapsulation.

Multiprotocol encapsulation determines whether the outbound packets on the interface are encapsulated with a Network Layer Protocol ID (NLPID; RFC 1294) or Logical Link Control / Subnetwork Access Protocol (LLC/SNAP; RFC 1483) multiprotocol header. All group or hybrid access mode PVCs on the interf ace use the value you set for this ﬁeld.

CS PDU encapsulation determines whether the outbound packets on the grouped virtual channels use AAL 3/4 CS_PDU encapsulation or AAL 5 CS_PDU encapsulation. All group and hybrid access mode PVCs on the interface use the value you set for this ﬁeld.

Selecting a Multiprotocol Encapsulation Method

You can use one of three multiprotocol encapsulation methods for the ATM DXI interface -- LLC/SNAP, NLPID, or NO MPE.

We recommend that you use the default setting, LLC/SNAP, when selecting a multiprotocol encapsulation method. However, keep the following exceptions in mind:

• If you are running a router software version earlier than Version 8.00, use NLPID for backward compatibility.

• If you specify NO MPE, the router interprets this as virtual channel-based multiplexing, which is not supported for bridging.

Site Manager: Multiprotocol Encapsulation: page A-4

Caution: When assigning data encapsulation to an interface, make sure that

the encapsulation method matches that of the DSU/CSU.

114057 Rev. A 4-3

Page 56

Configuring ATM DXI Services

Selecting a CS PDU Encapsulation Method

You can use one of three CS PDU encapsulation methods at the ATM DXI interface level -- AAL 5 Encapsulation, AAL 3/4 Encapsulation, and No Encapsulation.

Deﬁning the CS PDU encapsulation on the interface level sets the default value for any PVCs you may add. Normally, any new PVCs use the default AAL 5 encapsulation. By setting the CS PDU encapsulation method to AAL 3/4 at the interface level, all new PVCs that you add to the interface automatically use AAL 3/4 encapsulation.

Use No Encapsulation (a proprietary value) if you do not want the interface to use any CS PDU encapsulation.

When selecting a CS PDU encapsulation, choose the encapsulation method that you want most PVCs on the interface to use. You can always change the encapsulation method for individual PVCs after you add them.

Site Manager: CS PDU Encapsulation: page A-4

Caution: When assigning data encapsulation to an interface, make sure that

the encapsulation method matches that of the receiving device on the other end of the ATM network.

Enabling or Disabling the Multicast Function

By default, the ATM DXI interface does not accept multicast packets. However, you can enable the multicast function to accept multicast packets.

Site Manager: Multicast: page A-5

4-4 114057 Rev. A

Page 57

Enabling or Disabling LMI

To assist in obtaining traps and statistical information from the ATM DSU/CSU, Bay Networks includes a proprietary version of Local Management Interface (LMI) with ATM DXI. This LMI is incompatible with the ATM Forum standard LMI, and only operates under the Mode 2 Proprietary DXI mode.

Caution: If you disable LMI, the DSU/CSU cannot report traps to the router

and the router cannot retrieve statistical information from the DSU/CSU.

By default, this function is enabled. If you do not want LMI available for the interface, set the value to Disabled.

Site Manager: LMI Enable: page A-5

Where to Go Next

Use the following table to determine where you want to go next.

Customizing an ATM DXI Interface

For information about Go to

Starting ATM DXI Chapter 1 General ATM DXI information Chapter 2 Speciﬁc ATM DXI features and how we implement them Chapter 3 Customizing ATM DXI PVCs Chapter 5 Site Manager parameter descriptions Appendix A Site Manager defaults Appendix B

114057 Rev. A 4-5

Page 58

Page 59

Once you add PVCs to your router, you may want to customize them for your speciﬁc network conﬁguration.

Note: Y ou must ﬁrst add an ATM DXI interface to the router and add PVCs to

that interface before you can customize any PVCs. For instructions on how to start ATM DXI, how to add ATM DXI interfaces, or how to add PVCs to an ATM DXI interface, refer to Chapter 1.

Setting a VPI/VCI Pair

A virtual path is a set of virtual channels between a common source and destination. The virtual channels within a virtual path logically associate to a common identiﬁer. This identiﬁer is called the virtual path identiﬁer (VPI) and is part of the cell header.

Chapter 5

Customizing ATM DXI PVCs

Note: ATM DXI does not allow duplicate VPI/VCI pairs on the same ATM

physical interface (that is, on the same link module). However, duplicate VPI/VCI pairs can exist on different physical interfaces (that is, on different link modules).

114057 Rev. A 5-1

Page 60

Configuring ATM DXI Services

Setting a VPI Number

The VPI number does not have a default setting. You must enter a valid VPI number for each PVC you create. Depending on the DXI Mode you specify for the interface, the range for the VPI number varies as follows:

• Mode 1A or Mode 1B -- enter a value from 0 through 15.

• Mode 2 or Mode 2 Proprietary -- enter a value from 0 through 255.

Site Manager: VPI Number: page A-1

Setting a VCI Number

The VCI number does not have a default setting. You must enter a valid VCI number for each PVC you create. Depending on the DXI Mode you specify for the interface, the range for the VCI number varies as follows:

• Mode 1A or Mode 1B -- enter a value from 32 through 63.

• Mode 2 or Mode 2 Proprietary -- enter a value from 32 through 65535.

Site Manager: VCI Number: page A-2

Enabling or Disabling a PVC

By default, you enable a PVC when you create it. However, you can enable or disable a speciﬁc PVC at any time.

Site Manager: Enable: page A-2

5-2 114057 Rev. A

Page 61

Changing the PVC Access Mode

You can enable each PVC to function in one of three access modes -- group access, direct access, or hybrid access. The PVC Access Mode indicates how the PVC behaves within the network. You can conﬁgure PVCs to use different modes within the same physical interface.

Note: Refer to “Access Modes for A TM DXI Services” in Chapter 2 for more

information about these three modes.

When customizing each PVC, keep the following in mind:

• Accept the default, group access, if you want the PVC to act as part of a group of PVCs. All group access PVCs on an interface use the same protocols. This means that when you modify a protocol for one group PVC, you are modifying that protocol for all of the group PVCs.

• Set the mode to Hybrid Access if you want the PVC to act as part of a group of PVCs when routing and to act alone when bridging.

• Set the mode to Direct Access if you want the PVC to bridge or route to different networks than do group access or hybrid access PVCs.

Customizing ATM DXI PVCs

Site Manager: Mode: page A-6

Assigning Data Encapsulation

The ATM DXI interface allows both multiprotocol encapsulation and CS PDU encapsulation.

Multiprotocol encapsulation determines whether the outbound packets on the interface are encapsulated with a NLPID (RFC 1490) or LLC/SNAP (RFC 1483) multiprotocol header. All group or hybrid access mode PVCs on the interf ace use the value you set for this ﬁeld.

114057 Rev. A 5-3

Page 62

Configuring ATM DXI Services

Selecting a Multiprotocol Encapsulation

You can use one of three multiprotocol encapsulation methods for each A TM DXI PVC -- LLC/SNAP, NLPID, and NO MPE.

We recommend that you use the default setting, LLC/SNAP, when selecting a multiprotocol encapsulation method. However, keep the following exceptions in mind:

• If you are running a router software version earlier than Version 8.00, use NLPID for backward compatibility.

• If you specify NO MPE, the router interprets this as virual channel-based multiplexing, which is not supported for bridging.

Site Manager: Multiprotocol Encapsulation: page A-6

Caution: When assigning data encapsulation to an interface, make sure that

the encapsulation method matches that of the DSU/CSU.

Selecting a CS PDU Encapsulation

You can use one of three CS PDU encapsulation methods at the ATM DXI PVC level -- AAL 5 Encapsulation, AAL 3/4 Encapsulation, and No Encapsulation.

Normally, any new PVCs use the default AAL 5 encapsulation. Setting the CS PDU encapsulation method to AAL 3/4 at the interface level makes all new PVCs that you add to the interface automatically use AAL 3/4 encapsulation. Deﬁning the CS PDU encapsulation on the PVC level overrides the default value that you set on the interface level.

You can use No Encapsulation (a proprietary value) if you do not want the PVC to use any CS PDU encapsulation.

Site Manager: CS PDU Encapsulation: page A-7

5-4 114057 Rev. A

Page 63

Customizing ATM DXI PVCs

Caution: When assigning data encapsulation to an interface, make sure that

the encapsulation method matches that of the receiving device on the other end of the ATM network.

Enabling or Disabling the Multicast Function

By default, ATM DXI PVCs do not accept multicast packets. However, you can enable the multicast function to accept multicast packets.

Site Manager: Multicast: page A-7

Where to Go Next

Use the following table to determine where you want to go next.

For information about Go to

Starting ATM DXI Chapter 1 General ATM DXI information Chapter 2 Speciﬁc ATM DXI features and how we implement them Chapter 3 Customizing an ATM DXI interface Chapter4 Site Manager parameter descriptions Appendix A Site Manager defaults Appendix B

114057 Rev. A 5-5

Page 64

Page 65

Appendix A

Site Manager Parameter Descriptions

Virtual Path and Virtual Circuit Parameters

Parameter: VPI Number

Path: Conﬁguration Manager > Protocols > ATM DXI > Interfaces

Default: None

Range: 0 through 255

Function: Identiﬁes the virtual path of the PVC.

Instructions: How you set this parameter depends on how you set the DXI Mode parameter in

the ATM DXI Interface List window (refer to DXI Mode later in this chapter). If you select Mode 1A (default) or 1B for the DXI Mode value, enter a v alue from 0 through 15. If you select Mode 2 or Mode 2 Proprietary, enter a value from 0 through 255. Refer to Chapter 5 for more information.

MIB Object ID: 1.3.6.1.4.1.18.3.5.9.5.14.1.3

114057 Rev. A A-1

Page 66

Configuring ATM DXI Services

Parameter: VCI Number

Path: Conﬁguration Manager > Protocols > ATM DXI > Interfaces

Default: None

Range: 32 through 65535

Function: Identiﬁes the virtual channel of the PVC.

Instructions: How you set this parameter depends on how you set the DXI Mode parameter in

the ATM DXI Interface List window (refer to DXI Mode later in this chapter). If you select Mode 1A (default) or 1B for the DXI Mode value, enter a v alue from 32 through 63. If you select Mode 2 or Mode 2 Proprietary, enter a value from 32 through 65535. Refer to Chapter 5 for more information.

MIB Object ID: 1.3.6.1.4.1.18.3.5.9.5.14.1.4

Interface Parameters

Parameter: Enable

Path: Conﬁguration Manager > Protocols > ATM DXI > Interfaces

Default: Enable

Options: Enable

Function: Enables or disables ATM DXI on the selected interface.

Instructions: Set to Disable if you want to disable ATM DXI for the selected interface.

MIB Object ID: 1.3.6.1.4.1.18.3.5.9.5.2.1.2

| Disable

Parameter: Interface Description

Path: Conﬁguration Manager > Protocols > ATM DXI > Interfaces

Default: None

Range: 1 through 63 alphanumeric characters

Function: Describes the selected ATM interface.

Instructions: Enter text to describe the destination or purpose of the interface.

MIB Object ID: 1.3.6.1.4.1.18.3.5.9.5.2.1.7

A-2 114057 Rev. A

Page 67

Site Manager Parameter Descriptions

Parameter: DXI Mode

Path: Conﬁguration Manager > Protocols > ATM DXI > Interfaces

Default: Mode 1A

Options: Mode 1A

Function: Identiﬁes the ATM DXI mode of operation for this interface, based on the ATM

Forum ATM DXI speciﬁcation. Each mode relates to a different set of operations and functionality between the router and DSU/CSU.

Instructions: Enter the desired mode of operation. Refer to “ATM DXI Modes of Operation”

in Chapter 2 for a detailed description of each mode. The DXI header size is different for Modes 1A and 1B than for Mode 2 and

Mode 2 Proprietary. This difference affects the value that you set for the VPI and VCI parameters. For allowable VPI and VCI entries for each mode, refer to “Setting a VPI/VCI Pair” in Chapter 5.

MIB Object ID:

Parameter: Max number of VCs

Path: Conﬁguration Manager > Protocols > ATM DXI > Interfaces

Default: 512

Range: 1 through 512

Function: Speciﬁes the maximum number of virtual channels (VCs) allowed on the

Instructions: Accept the default, 512, or enter a different value between 1 and 512, inclusive.

MIB Object ID: 1.3.6.1.4.1.18.3.5.9.5.2.1.5

1.3.6.1.4.1.18.3.5.9.5.2.1.18

selected interface. This value is for PVCs only.

| Mode 1B | Mode 2 | Mode 2 Proprietary

114057 Rev. A A-3

Page 68

Configuring ATM DXI Services

Parameter: Multiprotocol Encapsulation

Path: Conﬁguration Manager > Protocols > ATM DXI > Interfaces

Default: LLC/SNAP

Options: LLC/SNAP

Function: Determines whether the outbound packets on the selected interface are

encapsulated with a multiprotocol header per RFC 1490 (NLPID) or RFC 1483 (LLC/SNAP). All group or hybrid access mode PVCs conﬁgured for the selected interface use the value you set for this ﬁeld.

Instructions: We recommend selecting LLC/SNAP.

If you are running an ATM DXI version earlier than Version 8.00, select NLPID for backward compatibility.

If you select NO MPE, the router interprets this as virtual channel-based multiplexing, which is not supported for bridging.

MIB Object ID: 1.3.6.1.4.1.18.3.5.9.5.2.1.11

Parameter: CS PDU Encapsulation

Path: Conﬁguration Manager > Protocols > ATM DXI > Interfaces

Default: AAL5 Encapsulation

Options: AAL5 Encapsulation

Function: Determines whether the outbound packets on the grouped virtual channels use

the AAL 3/4 CS_PDU encapsulation or the AAL 5 CS_PDU encapsulation. The encapsulating method is based on the ATM Forum’s ATM DXI speciﬁcation. All group and hybrid access mode PVCs conﬁgured for the selected interface use the value you set for this ﬁeld.

Instructions: Choose either AAL 3/4 or AAL 5 according to the desired encapsulation

method. No Encapsulation is a proprietary value. Select this value when you do not want CS_PDU encapsulation.

MIB Object ID: 1.3.6.1.4.1.18.3.5.9.5.2.1.12

| NLPID | NO MPE

| AAL3/4 Encapsulation | No Encapsulation

A-4 114057 Rev. A

Page 69

Site Manager Parameter Descriptions

Parameter: Multicast

Path: Conﬁguration Manager > Protocols > ATM DXI > Interfaces

Default: Disable

Options: Enable

Function: Indicates whether the selected ATM DXI interface supports multicast packets.

Instructions: Accept the default, Disable, if you do not want the interface to accept multicast

packets. Set to Enable if you want the selected interface to accept multicast packets.

MIB Object ID: 1.3.6.1.4.1.18.3.5.9.5.2.1.13

Parameter: LMI Enable

Path: Conﬁguration Manager > Protocols > ATM DXI > Interfaces

Default: Enable

Options: Enable

Function: Speciﬁes whether our proprietary version of the Local Management Interface

(LMI) is enabled for the selected interface. This LMI is not compatible with the ATM Forum standard LMI, and is only for use with DXI Mode 2 Proprietary.

Instructions: Accept the default, Enable, if you want LMI enabled for the interface. Set to

Disable if you do not want LMI available for the interface.

MIB Object ID: 1.3.6.1.4.1.18.3.5.9.5.2.1.15

| Disable

PVC Parameters

Parameter: Enable

Path: Conﬁguration Manager > Protocols > ATM DXI > Interfaces > PVCs

Default: Enable

Options: Enable

Function: Speciﬁes whether this PVC is enabled for the selected interface.

Instructions: Set to Disable if you do not want this PVC enabled.

MIB Object ID: 1.3.6.1.4.1.18.3.5.9.5.14.1.14

114057 Rev. A A-5

| Disable

Page 70

Configuring ATM DXI Services

Parameter: Mode

Path: Conﬁguration Manager > Protocols > ATM DXI > Interfaces > PVCs

Default: Group Access

Options: Group Access

Function: Speciﬁes the role of the PVC.

Instructions: Accept the default, group access, if you want the PVC to be part of a group of

PVCs. Set to hybrid access if you want the PVC to be part of a group of PVCs for routing, and to direct access for bridging. Set to direct access if you want the PVC to be used for bridging or routing to different networks.

For more information about the three modes, refer to “Access Modes for ATM DXI Services” in Chapter 2.

MIB Object ID: 1.3.6.1.4.1.18.3.5.9.5.14.1.9

Parameter: Multiprotocol Encapsulation

Path: Conﬁguration Manager > Protocols > ATM DXI > Interfaces > PVCs

Default: LLC/SNAP

Options: LLC/SNAP

Function: Determines whether the outbound packets on the selected interface are

encapsulated with a multiprotocol header per RFC 1490 (NLPID) or RFC 1483 (LLC/SNAP). All direct access mode PVCs conﬁgured for the selected interface use the value of this ﬁeld.

Instructions: We recommend selecting LLC/SNAP.

If you are running an ATM DXI version earlier than Version 8.00, select NLPID for backward compatibility.

If you select NO MPE, the router interprets this as virtual channel-based multiplexing, which is not supported for bridging.

MIB Object ID: 1.3.6.1.4.1.18.3.5.9.5.14.1.12

| Hybrid Access | Direct Access

| NLPID | NO MPE

A-6 114057 Rev. A

Page 71

Site Manager Parameter Descriptions

Parameter: CS PDU Encapsulation

Path: Conﬁguration Manager > Protocols > ATM DXI > Interfaces > PVCs

Default: AAL5 Encapsulation

Options: AAL5 Encapsulation

Function: Determines whether the outbound packets on the grouped virtual channels use

the AAL 3/4 CS PDU encapsulation or the AAL 5 CS PDU encapsulation. The encapsulating method is based on the ATM Forum’s ATM DXI speciﬁcation.

Instructions: Choose either AAL 3/4 or AAL 5 according to the desired encapsulation

method. No Encapsulation is a proprietary value. Select this value when you do not want CS PDU encapsulation.

MIB Object ID: 1.3.6.1.4.1.18.3.5.9.5.14.1.13

Parameter: Multicast

Path: Conﬁguration Manager > Protocols > ATM DXI > Interfaces > PVCs

Default: Unicast

Options: Unicast

Function: Indicates whether this PVC is multicast or unicast.

Instructions: Set to unicast or multicast, according to the PVC type.

MIB Object ID: 1.3.6.1.4.1.18.3.5.9.5.14.1.16

| Multicast

| AAL3/4 Encapsulation | No Encapsulation

114057 Rev. A A-7

Page 72

Configuring ATM DXI Services

Where to Go Next

Use the following table to determine where you want to go next.

For information about Go to

Starting ATM DXI Chapter 1 General ATM DXI information Chapter 2 Speciﬁc ATM DXI features and how we implement them Chapter 3 Customizing an ATM DXI interface Chapter4 Customizing ATM DXI PVCs Chapter 5 Site Manager defaults Appendix B

A-8 114057 Rev. A

Page 73

Appendix B

Site Manager Default Settings

This appendix lists the Site Manager default parameter settings for ATM DXI. Use the Conﬁguration Manager to edit these defaults.

Table B-1. ATM DXI Interface List Window

Parameter Default

Enable Enable Interface Description None DXI Mode Mode 1A Max number of VCs 512 Multiprotocol Encapsulation LLC/SNAP CS PDU Encapsulation AAL5 Encapsulation Multicast Disable LMI Enable Enable

Table B-2. ATM DXI Virtual Circuit Window

Parameter Default

VPI Number None VCI Number None

114057 Rev. A B-1

Page 74

Configuring ATM DXI Services

Table B-3. ATM DXI PVC List Window

Parameter Default

Enable Enable Mode Group Access Multiprotocol Encapsulation LLC/SNAP CS PDU Encapsulation AAL5 Encapsulation Multicast Unicast

Where to Go Next

Use the following table to determine where you want to go next.

For information about Go to

B-2 114057 Rev. A

Page 75

AAL Sublayer support, 2-3 access modes

changing, 5-3 direct access, 2-10 function of, 2-9 group access, 2-9 hybrid access, 2-11 to 2-13

Index

ATM DXI

concepts, 2-1 deleting from the router, 1-4 supported features, 2-2 synchronous line parameters set for, 2-6 versus ATM, 2-1

ATM layers, understanding, 2-15 to 2-17

Bay Networks

CompuServe forum, xx Customer Service FTP, xix home page on World Wide Web, xix InfoFACTS service, xxi publications, ordering, xvi support programs, xviii Support Source CD, xx Technical Response Center, xvii, xxi technical support, xvii

cell switching, 2-18 circuit, creating a, 1-2 CompuServe, Bay Networks forum on, xx Convergence Sublayer (CS), described, 2-16 CS PDU Encapsulation

parameter description

ATM DXI Interface List window, A-4 ATM DXI PVC List window, A-7

selecting, 4-4, 5-4

114057 Rev. A Index-1

Page 76

Configuring ATM DXI Services

Customer Service FTP, xix customer support. See getting help

data encapsulation, assigning, 4-3, 5-3 defaults, parameter, B-1 to B-2 direct access mode, 2-10 disabling

interfaces, 4-1 LMI, 4-5 multicast, 4-4 PVCs, 5-2

DXI Mode

changing, 4-2 parameter description, A-3

Avaya ATM DXI User Manual

Contents

Figures

Tables

About This Guide

Before You Begin

Conventions

Acronyms

Ordering Bay Networks Publications

Technical Support and Online Services

Bay Networks Customer Service

Bay Networks Information Services

World Wide Web

Customer Service FTP

Support Source CD

CompuServe

InfoFACTS

How to Get Help

Before You Begin

Adding ATM DXI to the Router

Creating an ATM DXI Circuit

Enabling Protocols on an ATM DXI Circuit

Adding PVCs to an ATM DXI Circuit

Deleting ATM DXI from the Router

Where to Go Next

Where to Go Next

Adding or Copying PVCs

Setting PVCs for Multipath Mode

Managing Protocols

Where to Go Next

Enabling or Disabling the Interface

Entering an Interface Description

Changing the DXI Mode

Assigning a Maximum Number of Virtual Circuits

Assigning Data Encapsulation

Selecting a Multiprotocol Encapsulation Method

Selecting a CS PDU Encapsulation Method

Enabling or Disabling the Multicast Function

Enabling or Disabling LMI

Where to Go Next

Setting a VPI/VCI Pair

Setting a VPI Number

Setting a VCI Number

Enabling or Disabling a PVC

Changing the PVC Access Mode

Assigning Data Encapsulation

Selecting a Multiprotocol Encapsulation

Selecting a CS PDU Encapsulation

Enabling or Disabling the Multicast Function

Where to Go Next

Virtual Path and Virtual Circuit Parameters

Interface Parameters

PVC Parameters

Where to Go Next

Where to Go Next

Index