Avaya LLC User Manual

Configuring LLC Services

BayRS Version 13.0 0 Site Manager Software Version 7.00

Part No. 303533-A Rev 00 October 1998

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

and recomm endations in this docum ent are believed to be accurate and reliable, but are presented without express or implied warranty. U sers must take full respons ibility for their applications of any products specified in this do cum ent. 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 te rms of that license. A summary of the Soft w are License is include d in this docum ent.

Trademarks

ACE, AFN, AN, BCN, BLN, BN, BNX, CN, FRE, LN, Optivity, PPX, Quick2Config, and Bay Networks are registered tradema rks and Advanced Remote Node, ANH, ARN, ASN, BayRS, BaySecure, BayStack , BayStr eam, BCC, BCNX, BLNX, EZ Install, EZ Internetwork, EZ LAN, FN, IPAutoLearn, PathMan, RouterMan, SN, SPEX, Switch Node, System 5000, and the Bay Netw orks logo are trademarks of Bay Networks, Inc.

Microsoft , MS, MS-DOS, Win32, Windows, and Windows NT ar e registered trade m arks of Micro soft Corporation. All other trademarks and registered trademarks are the property of their respective owners .

Restricted Rights Legend

Use, duplication, or disclosure by the United States Government is subject to restrict ions as set forth in subparagraph (c)(1)(ii) of the Rights in Technical Data and Computer Software clause at DFARS 252.227-7013.

Notwithstanding any other license agreement th at may pertain to, or accompany the delivery of, this computer software, the ri ghts of the Un ited States Gove rnment re garding its use, reproduction, and disclosure are as set forth in the Commercial Computer Software-Restricted Rights clause 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 products described in this document without notice.

Bay Networks, Inc. does not assume an y liability that may occur due to the use or applic ation 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 reserve d. Redistribution and use in source and binary forms of such portions are permitted, provided that the above copyright notice and this paragrap h are duplicated in all su ch forms and th at any docume ntation, adverti sing materials, and other materials related to such distribution and use acknowledge that such portions of the software were deve loped by th e U niversity of California, Berkeley. The nam e 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 IMPLIE D WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE.

In additi on, the program and information contained herein are li censed only pursuant to a license agreement that contains restrictions on use and disclosu re (that may incorporate by refer ence certain limitations and not ices imposed by thir d pa rt ie s).

303533-A Rev 00

Bay Networks, Inc. Software License Agreement

NOTICE: Please carefully read this license agreement before copying or using the accompanying software or instal ling the hardware unit with pre-enabled software (e ach of which is referred to as “Softw are” 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 o riginal shipping container, within 30 days of purchas e to obtain a credit for the full purchase price.

1. License Grant. Bay Networks, Inc. (“Bay Networks”) gra nts the end user of the Software (“Lice nsee”) a personal, nonexcl usive, nontransferable license: a) to use the Software either on a single computer or, if applic able, on a singl e authori zed de vi ce ide ntified by host ID, fo r whi ch it was origi nal ly acq uired ; b) to cop y th e Softw ar e so le ly fo r bac kup purposes in support of authorized us e of the Software; and c) to us e and copy the associated user manual solely in support of authorized use of the Soft w are by Licensee. This li cense applies to the Software only and does not extend to Bay Networks Agent software or other Bay Networks softw are 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 accompanies such software and upon payment by the end user of the applicable licen se fees for such software.

2. Restrictions on use; reservation of rights. The Software and user manuals are protect ed under copyright laws. Bay Networks and/or its licensors retain all title and ownership in both the Sof tware and user manuals, including any revis ions made by Bay Networks or its licensors. The copyright notice must be reproduced and included wi th any copy of any por tion of the Sof tw are or use r manua ls . Licens ee may not modif y, translate, dec ompi le , disas se mble , use for any compe ti ti v e an al ysis, r e v erse e ngi ne er , dis tr ib ute , o r c rea te der i vative work s f ro m the Softw are or u se r man ual s or any copy, in whole or in part. Except as expressly provided in this Agreement, Licensee may not copy or transfer the Softw are or user man uals, in whole or in part. Th e Software and user manuals embody Bay Networks’ and it s licenso rs’ confidential and proprietary intell ectual property. Licensee shall not sublicense, assign , or otherwise disclos e 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 Networ ks and its licensors; however, Licensee m ay grant permission to its consul tants, subcontractors, and agents to use the Software at Licensee’ s facility, provided they have agreed to use the Software only in accordance with the terms of th is license.

3. Limited warranty. Bay Networks warrants each item of Software, as delivered by Bay Network s and properly installed and operated on Bay Networks hardware or other equipment it is originally licensed for, to function substantially as described in i ts accompanying user manual during its warranty period, wh ich begins on the date Softwar e is fi r st shi pped to Licen see . If any it em of Soft war e fai ls to so func ti on du ring i ts warr anty pe ri od, as t he so le remedy Bay Ne tworks will at its discretion provide a suitable fix, pat ch, or workaround for the problem tha t m ay be included in a future Software release. Bay Networks further warrants to Licensee that the media on which the Softwar e is provided will be fr ee from defects in materials and workmanship under normal use for a period of 90 days 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 warranty per iod along with proof of the date of shipmen t. This warran ty does not apply i f the media has been damaged as a result of acci dent, misuse, or abuse. The Licensee assumes all re sponsibility 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 cont ained in the software w ill meet the Licensee ’s requirements, b) that the Software will operate in the har dw are or software combinations that the Licensee may select, c) that th e operation of the Software will be uninterrupted or error free, or d) that all defects in the operati on of the Software wi ll be corrected. Bay Networks is not ob ligated to remedy any Software defect that cannot be repro duced with the latest Software release. Thes e warranties do not apply to the Sof tware if it 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 im proper environm ent, abuse, misuse, accident, or neglige nce. THE FOREGOING WARRANTIES AND LIMITATIONS ARE EXCLUSIVE REMEDIES AND ARE IN LIEU OF ALL OTHER WARRANTIES EXPRESS OR IMPLIED, INCLUDING WITHOUT LIMITATION ANY WARRANTY OF MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE. Licensee is responsible for the security of

303533-A Rev 00

iii

its own data and information and for maint aining adequate procedures apart from the Software to reconstruct lost or altered files, data, or programs.

4. Limitati on of liabili ty. 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 DAT A 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 NETW ORKS FOR THE SOFTWARE LICENSE.

5. Governmen t L i c en s ees. This provisio n applies to all Software and documentation acquired directly or indirectly 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 the use of any U.S. Government funds. The license to the U.S. Government is granted only with restricte d rights, and use, duplication, or disclos ure by the U.S. Gover n m ent is subject to the restrictions set forth in subparagraph (c)(1) of the Commercial Computer So ftware––Restricted Rights clause of FAR 52.227-19 and the limitations set out 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 D e partment of Defense or their suc cessors, whiche ver is applicable.

6. Use of Software in the European Communi ty. This prov ision applies to all Software acquired for use within the European Comm unity. If Lice nsee uses the Software within a countr y in the European Community, the Softwar e Directive enacted by the Counc il of European Communities Directive dated 14 May, 1991, w ill apply to the examination of the Software to facilitate interoperability. License e agrees to notify Bay Networks of any such intended examination of the Software and may procure support and assistance from Bay Networ ks.

7. Term and termination. This license is effective until terminated; however, all of the restrictions with respect to Bay Networks’ copyright in the Software and user manuals will cease being effective at the date of expiration of the Bay Networks copyright; those r estrictions relating to use and disclosure of Bay N etworks’ confidential information shall continue in effect. Licensee may terminate this license at any time. The license will automatically terminate if Licensee fails to co m ply with any of the terms and conditions of the license. Upon terminat ion 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, direct ly or indirectly, the Software or related technical data or information without first obtaining any required export licenses or other governmental approvals. Without limiting the fore going, Licensee, on behalf of itself and its subsidiaries and affiliates, agrees that i t will not, without first obtaining all export licenses and appro vals required by the U.S. Government: (i) export , re-export, transfer, or diver t any such Sof tware or technical data, or any direct product thereof, to any coun try to which such exports or re-exports are rest ricted or embargoed under United States ex port control laws a nd regulations, or to any national or resident of such rest ricted or embargoed countries; or (ii) provide the Software or related technical data or inf ormation to any military end user or for any military end use, including the design, develop ment, or production of any chemical, nuclear, or biological weapons.

9. General. If any provision of this Agreement is held to be invalid or unenforceable 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., 440 1 G reat America Parkway, P.O. Box 58185, Santa Clara, Californi a 95054-8185.

LICENSEE ACKNOW LEDGES THAT LICENSEE HAS READ THIS AGREEMENT, UNDERSTANDS IT, AND AGREES TO BE BOUND BY ITS TERMS AND CONDITIONS. LICENSEE FUR THER 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.

303533-A Rev 00

Preface

Before You Begin .............................................................................................................. xi

Text Conventions .................................... ....................................................................... ...xii

Acronyms ......................................................................................................................... x ii i

Bay Networks Technical Publications ..............................................................................xv

How to Get Help ..............................................................................................................xv

Chapter 1 Logical Link Control Overview

Using LLC2 with SNA and NetBIOS ............................................................................... 1-2

Supported Connections ................................................................................ ..... ....... ......1-2

Frame Relay Support .................................... .. .......... ....... .. .......... ....... ....... .. .......... ....... .1-3

Boundary Network Node (RFC 1490) ......................................................................1-3

Boundary Access Node ...........................................................................................1-4

LLC 8802/802.2 Standards .............................................................................................1-6

LLC Service Classes ......................................................................................................1-6

LLC1 (Connectionless Service) ...............................................................................1-7

LLC2 (Connection-Oriented Serv ice) .......................................................................1-7

LLC Operation Types ...................................................................................................... 1-8

Type 1 Operations .................................................................................................... 1-8

Type 2 Operations .................................................................................................... 1-8

LLC Functionality ............................................................................................................1-9

LLC Protocol Data Unit Formats ...................................................................................1-10

Destination SAP (DSAP) ........................................................................................ 1 -10

Source SAP (SSAP) .............................. .................................................................1-11

SAP Addressing Scheme .......................................................................................1-12

Control Field ........................................................................................................... 1 -13

Control Field Formats .............................................................................................1-14

Info rmat ion Fi e ld ....................... ....................................................................... ......1-18

303533-A Rev 00

For More Information about Logical Link Control ..........................................................1-19

Chapter 2 LLC2 Routed over Frame Relay

Compatibility with RFC 1490 ............................................ .. ..... ..... .. ..... .. ..... ..... ..... .... ..... .2-1

Compatibility with IBM NCP 7.1 and Higher ...................................................................2-1

FRAD-like Functionality ......................................................................... ....... ..... ....... ......2-4

Mapping DLCIs to MAC Addresses ................................................................................2-4

Router Mapping Examples ........................................ .. ....... .......... ....... .. ....... .......... .. ......2-5

Virtual MAC to Frame Relay .....................................................................................2-6

Frame Relay to Virtual MAC .....................................................................................2-7

Physical MAC to Frame Relay ..................................................................................2-8

Frame Relay to Physical MAC ..................................................................................2-9

Frame Relay to Frame Relay ..................................................................................2-10

LLC2 over Frame Relay: Routed ve rsus Bridged .........................................................2-12

For More Information about LLC2 over Frame Relay ...................................................2-13

Chapter 3 Enabling LLC Services

Using the Parameter Descriptions .................................................................................. 3-1

Enabling LLC2 on an Interface .......................................................................................3-2

Enabling LLC2 Services ove r Native Frame Relay .........................................................3-3

For APPN Networks .................................................................................................3-4

For DLSw Networks .................................................................................................3-5

Chapter 4 Editing LLC Parameters

Configuring LLC Parameters ..........................................................................................4-2

Editing LLC2 Global Para meters ....................................................................................4-3

Editing LLC2 Interface Parameters .................................................................................4-4

Editing Frame Relay Mappings .....................................................................................4-13

Deleting an LLC2 Inte rface ........................................................................................... 4 -14

Editing LLC2 Inbound Traffic Filters ..............................................................................4-14

Deleting LLC2 from the Node .................................... ....... .. .......... ....... ....... .. .......... ......4-14

Appendix A LLC2 Default Settings

Index

303533-A Re v 00

Figures

Figure 1-1. Sample Frame Relay Network ................................................................1-5

Figure 1 -2 . The LLC Sublayer in the IEEE 802.x and OSI Models . ............................1-6

Figure 1-3. LLC PDU Structure ................................................................................1-10

Figure 1-4. DSAP Address Field ....................................... .......................................1-11

Figure 1-5. SSAP Address F ield ..............................................................................1-11

Figure 1-6. SAPs for LLC Clie nts .............................................................................1-12

Figure 1-7. LLC PDU Control Field Format ..............................................................1-14

Figure 2-1. Sample Frame Relay Network Using LLC2 .............................................2-3

Figure 2 -2. Frame Relay to Virtual MAC Topology .....................................................2-7

Figure 2-3. Physical MAC to Frame Relay Topology .................................................. 2-8

Figure 2-4. Frame Relay to Physical MAC Topology ................................................2-10

Figure 2-5. Frame Relay-to-Frame Relay Topology ..................................................2-11

Figure 2 -6. RFC 1490 Bridging and Routing Standards for SNA .............................2-12

Figure 3-1. Select Protocols Window (LLC only) ........................................................3-2

Figure 3-2. WAN Protocols Window (Frame Relay) ...................................................3-3

Figure 3-3. Select Protocols Window .........................................................................3-4

Figure 3-4. Source Route Encapsulation Dialog Box .................................................3-4

Figure 3-5. LLC2 Frame Relay Mappings Window .....................................................3-6

Figure 3-6. LLC2 Frame Relay Mapping Add Window ...............................................3-7

Figure 3-7. LLC2 Frame Relay Mappings Window with DLCI Added . ........................3-9

Figure 4-1. Configuration Manager Window .................................................. ....... ..... .4-2

Figure 4 -2. Edit LLC2 Global Parameters Window .....................................................4-3

Figure 4 -3. LLC2 Interface Configuration Window .....................................................4-5

Figure 4 -4. LLC2 Interface Configuration Window (Bottom) .......................................4-5

303533-A Rev 00

vii

Tables

Table 1-1. LLC Command PDUs ........................................... .. ..... .. ..... ..... ..... .... ..... .1-9

Table 1-2. PDU Format and Function .....................................................................1-15

Table 1-3. Control Field Bits and Functions ............................................................1 -15

Table 1-4. Command Names and Definitions ........................................................1-16

Table 2-1. Virtual MAC to Frame Relay Topology .....................................................2-6

Table A-1. LLC2 Global Parameters .................................................................... .....A-1

Table A-2. LLC2 Interface Parameters ....................................................................A-1

303533-A Rev 00

This guide describes Logical Link Control (LLC) services and what you do to start and customize ATM services on a Bay Networ ks® router. By customizing your router for LLC services, you open your network to LAN Network Manager (LNM) servers, Data Link Switc hing (DLSw) services, and Advanced Peer-to- Peer Networking (APPN).

Before You Begin

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

Preface

303533-A Rev 00

• Instal l the router (see the installation guide that came with your router).

• Connect the route r to the net work and create a pilot configur ation file (see

Quick-Starting Routers, Configuring BayStack Remote Access, or Connecti ng ASN Routers to a Network).

™

Make sure tha t you are running the latest version of Bay Networks BayRS Site Manager sof tware. For information about upgrading BayRS and Site Manager, see the upgr ading guide for your version of B ayRS.

and

Configuring LLC Services

Text Conventions

This guide use s the following text conventions:

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

description inside the brackets. Do not type the brackets when entering the command. Example: If the command syntax is:

bold text

<ip_address>

ping ping 192.32.10.12

Indicates text tha t you need to enter and command

, you enter:

names and options. Example: Enter

Example: Use the

show ip {alerts | routes

command.

dinfo

}

braces ({}) Indicate required elements in syntax descriptions

where there is more than one option. You must choose only one of the options. Do not type the braces when entering the command. Example: If the command syntax is:

, you must enter either:

show ip {alerts | routes show ip alerts or show ip routes

}

brackets ([ ]) Indicate optional elements in syntax descriptions. Do

not type the brackets when entering the command. Example: If the command syntax is:

, you can enter either:

show ip interfaces [-alerts show ip interfaces

]

show ip interfaces -alerts

xii

ellipsis points (. . . ) Indicate that you repeat the last element of the

comman d as need ed . Example: If the command syntax is:

ethernet/2/1 ethernet/2/1

parameter> <value>

and as many parameter-value pairs as

] . . .

, you enter

needed.

303533-A Re v 00

Preface

italic text Indicates file and directory names, new terms, book

titles, and variables in command syntax descriptions. Where a variable is two or more words, the words are connected by an underscore. Example: If the command syntax is:

show at

valid_route

valid_route>

is one va riable and you subs titu te one value

for it.

screen text Indicates system output , fo r exa mple, prompts and

system messages. Example:

Set Ba y Netw orks Tr ap Mo nito r Fil ters

separator ( > ) Shows menu paths.

Example: Protocol s > IP identifies the IP option on the Protocols menu.

vertical line (

) Separates choices for command keywords and

arguments. Enter only one of the choices. Do not type the vertical line when entering the command. Example: If the command syntax is:

Acronyms

303533-A Rev 00

, you enter either:

show ip {alerts | rou tes show ip alerts

}

show ip routes

, but not both.

ANSI American National Standards Institute APPN Advanced Peer-to-Peer Networking DLCI data link connection ide ntifier DLSw Data Link Switching DSPU downstream physical unit FDDI Fiber Distributed Data Interface FEP front-end processor FR Frame Relay

xiii

Configuring LLC Services

FRAD Frame Relay Access Device IEEE Institute of Electr ical and Electronic Engineers ISO International Standards Organization LAN Local Area Network LLC Logical Link Control LNM LAN Network Manager LSAP Link Service Access Point LSB least significant bit LSDU Link Service Data Unit MAC Media Access Control MSB most signific ant bit NCP Network Communications Program NetBIOS Network Basic Input-Output S ystem OSI Open Systems Interconnec tion PDU Protocol Data Unit

xiv

RFC Request for Comment SAP Service Access Point SDLC Synchronous Data Link Control SNA Systems Network Architecture SR source rou ting SRB source-route bridging WAN wide area network

303533-A Re v 00

Bay Netwo rks Technical Publicati o ns

You can now print Bay Networks technical manuals and release notes free, directly from the Int ernet. Go to support.bayn etworks.com/libr ary/tpubs/. Fi nd the Bay Networks product for which you need doc umenta tion. Then locate the specific category and model or version for your hardwa re or software product. Using Adobe Acrobat Reader, you can open the manuals and release notes, search 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 technic al publications through the Bay Networks Collateral Catalog. The catalog is located on the World Wide Web at support.baynetworks.c om/catalog. html and is divided into sections arran ged alpha betically:

• The “CD ROMs” section lists available CDs.

• The “Guides/Boo ks” section lists books on technical topi cs.

• The “Technical Manuals” section lists available printed documentation sets.

Preface

Make a note of the part num bers 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 assista nce, support contracts, or information about educational services, go to the following URL:

http://www.baynetworks.com/corporate/contacts/

Or telephone the Bay Networks Technical Solutions Center at: 800-2LANWAN

303533-A Rev 00

Chapter 1

Logical Link Control Overview

LLC is a standard protocol within the CCITT 8802.2 and IEEE 802.x family of LAN standards. Connection-oriented protocols, including IBM Systems Network Architecture (SNA) and NetBIOS, use LLC services. Connection-oriented protocols do not have a network layer address (such as an IP subnet) to route information. Instead, before any information transfer occurs, a devic e on the network sends a “broadcast” or “explore r” frame to locate the session partner. From this broadcast, the network establishes a path for the data tr ans fer.

LLC2 traffic is generally sensitive to excessive network delays, causing problems with SNA and NetBIOS sessions. Data Link Switching (DLSw) and Advanced Peer-to-Peer Networking (APPN) resolve these problems by locally terminating the LLC2 session at the router, and providing a local acknowledgment to SNA/ NetBIOS workstations. The LLC2 subsystem provides these se rvices.

303533-A Rev 00

The Bay Networks implementat ion of the LLC protoc ol consists of LLC Class 1 (LLC1), a connec tion less s ervice , and LLC Clas s 2 (LLC2) , a connect ion-or iented service. The subsystems that require LLC2 services are

• DLSw

• APPN

• LAN Network Manager (LNM) Most other protocols use LLC1, or connect ionless, delivery services. Generally there is no need to change the LLC2 default settings in Site Manager.

However, you can tune the network by changing these default settings. In Site Manager, you should not se lect LLC 2 on an interface without also selecting one of the preceding protocols.

1-1

Configuring LLC Services

Using LLC2 with SNA and NetBIOS

SNA needs a connectio n-ori ented datalink layer for end-to-end pa cket sequ encing and error control. Over wide area networks (WANs), the Synchronous Data Link Control (SDLC) protocol has tr aditionally met this ne ed. However, in a LAN envir onment, front-end pr ocessors (FEPs), controllers, and NetBIOS clie nt/server stations c ommonly use an LLC 2 layer for this purpose . To support communication among these devic es, you can add LLC2 interfaces to a router co nfigur at ion .

SNA de vices and NetBIOS PCs use LLC when they establish sessions thr ough a LAN topology. SNA and NetBIOS need LLC2 connection-oriented circuits to provide higher-layer sequencing and error control in bridged LAN en vir onments. LLC2 works much like SDLC in terms of packet sequencing and acknowledgment. Unlike SDLC, it does not impose unbalanced, primary/secondar y relat ionships be tween communic ating no des. An y LLC station can initiate a peer -to-peer conversation with any other LLC station.

Supported Connections

Y ou configure LLC2 on any interface requiring local t ermination. These inte rf aces include

1-2

• Interfaces configured with APPN

• Interfaces configured with DLSw When you connect ov er an IP backbone in dual -s witch DLSw configurations,

the interface attached to the IP backbone does not use LLC2. When you connect ove r an LLC2 backbone in DLSw singl e-switch configura tions, the interface attached to the backbone uses LLC2.

• Token Ring interfaces running LNM

You can enable LLC2 on any LAN or W AN interface that supports APPN, DLSw , and LNM. These interfaces inc lude

• LAN interfaces

-- Token Ring

-- Ethernet

-- Any other LAN media supporting Sour ce Route Bridge , including FDDI

303533-A Re v 00

Logical Link Control Overview

• WAN interfaces

-- Frame Relay Boundary Network Node (BNN) and Boundary Access

Node (BAN) interfaces

-- Any other WAN media supporting Source Route Bridge (SRB) traffic,

including Point-to- Point (PPP)

Frame Relay Support

Figure 1-1

configuration with multipr otocol traffic to other locations. Bay Networks pro vides two w ays to communicate di rectly wi th an S NA p rocessor

(such as an IBM 3745 or AS/400) over Frame Relay:

• Boundary Network Node (RFC 1490)

• Boundary Access Node

illustrat es the c onnec tion of a host th rough a F rame Re lay netw ork, i n a

Boundary Network Node (RFC 1490)

The Boundary Network Node (BNN) refers to RFC 1490, Routed SNA over Frame Relay. This implementation of LLC2 also complies with the Frame Relay Forum 3 (FRF.3), “Multiple Protocol Encapsulation over Frame Relay Implementation Agreements,” which defines how SNA traffic traverses a Frame Relay network.

BNN allows native SNA traffic (originating from SDLC LAN- or WAN-attached devices) to communicate over public or private Frame Relay networks directly with an SNA processor. Devices can communicate with int ermedia te routing nodes or in a single-switch configuration function as a Frame Relay Access Device (FRAD).

303533-A Rev 00

1-3

Configuring LLC Services

Since BNN does not carry the destination and source MAC addresses in the network packets, the BNN format carries the fewest number of bits per packet and yields low ne twork ov erhead. Therefo re, you must expli citly define the permanent virtual circuit ( PVC) to carry the packet to its destination. You do this with the LLC2 Frame Relay Mapping Table. The mapping table consists of three fields:

• DLCI

• Remote (or Destina tion) MAC

• Local (or Source) MAC

Each entry requires that you spe ci fy the Remote MAC, Local MAC, or both. A packet that matches this entry is then forwarded to the specified DLCI.

Bay Networks routers sel ect BNN when you configure the Frame Relay network without source route encapsula tion.

Boundary Access Node

The Boundary Access Node (BAN) is an IBM router enhancement. B AN refers to the RFC 1490 specification for Bridged SNA over Frame Relay. The associated IBM NCP 7.3 enhancement is called the Boundary Node Identifier (BNI).

1-4

Since BAN carri es the destination and source MA C addr esses in the network packets, this format carries more bits per packet.

Standard BAN use s the Source Route Bridg e frame format with loc al termin ation. Bay Networks routers sel ect BAN when you configure the Frame Relay net work with source route encapsula tion.

303533-A Re v 00

Logical Link Control Overview

Host

Frame Relay

network

Single-switch DLSw

Bay Networks

router

DLSw

TCP/IP

Client

303533-A Rev 00

Client

Figure 1-1. Sample Frame Relay Network

Bay Networks

router

Token Ring

DLS0007A

1-5

Configuring LLC Services

LLC 8802/802.2 Standards

The LLC protocols comply with the CCITT 8802.2 standar d, a nd operate within the IEEE Project 802.x protocol sta ck. Figure 1-2 compares LLC’s location in the

802.x protocol sta ck to its equivalent position in the ISO/OSI model.

ISO/OSI Model

Application

Presentation

Session

IEEE 802 Model

802.1

802..2 (LLC)

MAC

Physical

Figure 1-2. The LLC Sublayer in the IEEE 802.x and OSI Models

You can add an IEEE 802.2-compliant LLC interface to any physical circuit attached directly to a n 8802.x/802.x LAN segment. Each interface services higher-level clients (net wor king protocols and applications) and is serviced by lower -le v el prot ocols (media access contr ol [MA C ] and physical la yers) operating within the router.

LLC Service Classes

Transport

Network

Data Link

Physical

LLC0002A

1-6

The 802.2/LLC recommendations support three service classes:

• Connectionless Unacknowledged (Class 1 or LLC1)

303533-A Re v 00

• Connection-Oriented (Class 2 or LLC2)

• Connectionle ss Acknowledged (Class 3 or LLC3)

Bay Networks LLC does not support the LLC3 service clas s.

Note:

LLC1 (Connectionless Service)

LLC1 is a data gram s ervice that sends and r ecei v es LLC f rames c alle d link s ervic e data units (LSDUs) without requir ing acknowledgment from the peer to assur e delivery.

LLC1 supports all forms of communication (point-to-point, multipoint/mult icast, and broadcast).

This service is appropriate for protocols that provide addressing, routing, recove ry, and sequencing services at a higher layer.

Logical Link Control Overview

LLC2 (Connection-Oriented Service)

LLC2 secures a point-to-point virtual circuit connection between link service access points (LSAPs). The LLC2 protocol

• Responds to a request from a higher-level protocol to open a connection through the datalink laye r

• Notifies a higher-level protocol that a co nne ct ion thr ough the datalink layer has been established succ essfully

• Enables a higher-level protocol to

-- Send or receive LSDUs over an established datalink-layer connection

-- Sequence LSDUs sent over a datalink-layer connection

-- Control the flo w of LSDUs over a datalink-layer connection

The LLC2 service also

• Responds to a reque st from a higher-l evel protocol to reset a connection to its initially connected state

303533-A Rev 00

1-7

Configuring LLC Services

• Responds to a request from a higher-level protocol to close an established connection

• Notifies a higher-level protocol that a co nne ct ion previously established has been closed successfully

Because the connection occurs in the datalink layer rather than in higher layers, LLC2 performs frame sequencing, flow control, and error recovery services for the datalink layer.

LLC Operation Types

LLC supports two operation types:

• Unnumbered, Unacknowledged (Type 1)

• Numbered, Acknowledged (Type 2)

LLC1 supports only Type 1 operations; LLC2 supports both Type 1 and Type 2 operations.

Type 1 Operations

Type 1 operations have the following characteristics:

• LLCs exchan ge protocol data units (PDUs) without establishing a datalink connection.

• The peer does not acknowledge the PDUs it receiv es.

• There are no mechanis ms for PDU sequenci ng, f low control, or error recovery, because higher-level protoco ls perfo rm thes e serv i ce s.

Type 2 Operations

Type 2 operations have the following characteristics:

• The LLC and its peer must e stablis h a da tali nk-lay er vir tual c ircuit/ connecti on prior to any excha nge of data.

• The source and destination are peer LLCs in an asynchronous, balanced datalink connection.

1-8

303533-A Re v 00

+ 56 hidden pages

Avaya LLC User Manual

Configuring LLC Services

Contents

Figures

Tables

Before You Begin

Preface

Text Conventions

Acronyms

Bay Netwo rks Technical Publicati o ns

How to Get Help

Using LLC2 with SNA and NetBIOS

Supported Connections

Frame Relay Support

Boundary Network Node (RFC 1490)

Boundary Access Node

LLC 8802/802.2 Standards

LLC Service Classes

LLC1 (Connectionless Service)

LLC2 (Connection-Oriented Service)

LLC Operation Types

Type 1 Operations

Type 2 Operations