Avaya APPN User Manual

Download

Page 1

Configuring APPN Services

Router Software Version 10.0

Site Manager Software Version 4.0

Part No. 112908 Rev. A

January 1996

Page 2

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

recommendations in this document are believed to be accurate and reliable, but are presented without express or implied warranty. Users must take full responsibility for their applications of any 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, BCN, BLN, BN, CN, FRE, LN, Optivity, SynOptics, SynOptics Communications, Wellﬂeet and the Wellﬂeet logo are registered trademarks and AN, ANH, ASN, BaySIS, BayStack, BCNX, BLNX, BNX, EZ Internetwork, EZ LAN, FN, PathMan, PhonePlus, PPX, 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 T rademarks

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 University of California. All rights reserved. Redistribution and use in source and binary forms of such portions are permitted, provided that the abov e 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 deri v ed 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).

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, none xclusiv e 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.

4401 Great America Parkway, Santa Clara, CA 95054

8 Federal Street, Billerica, MA 01821

Bay Networks, Inc.

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 Softw are Directiv 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)

4401 Great America Parkway, Santa Clara, CA 95054

8 Federal Street, Billerica, MA 01821

Bay Networks, Inc.

Page 5

About This Guide

Audience ..........................................................................................................................xiii

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

Bay Networks Customer Support ....................................................................................xiv

CompuServe .............................................................................................................xiv

InfoFACTS .................................................................................................................xv

World Wide Web ........................................................................................................ xv

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

Conventions .....................................................................................................................xvi

Ordering Bay Networks Publications ..............................................................................xvii

Acronyms ........................................................................................................................xvii

Chapter 1 Advanced Peer-to-Peer Networking Overview

APPN Networking Overview ...........................................................................................1-2

APPN Node Types ..........................................................................................................1-2

Network Nodes ........................................................................................................1-3

End Nodes ...............................................................................................................1-3

Low-Entry Networking Nodes ..................................................................................1-3

Control Points and Logical Units .....................................................................................1-5

Dependent Logical Unit Requester and Server ..............................................................1-6

lnterfaces, Ports, and Link Stations ................................................................................1-8

Interfaces .................................................................................................................1-9

Ports .........................................................................................................................1-9

Link Stations .............................................................................................................1-9

Connection Networks ...................................................................................................1-10

Intermediate Session Routing ......................................................................................1-12

Packet Segmentation and Reassembly .................................................................1-13

Adaptive Pacing .....................................................................................................1-13

Page 6

High Performance Routing ...........................................................................................1-14

Rapid Transport Protocol .................................................................................1-16

Non-Disruptive Path Switching ........................................................................1-16

End-to-End Error Recovery .............................................................................1-17

End-to-End Flow and Congestion Control .......................................................1-17

Automatic Network Routing ....................................................................................1-18

Fast Packet Switching ......................................................................................1-18

Session Transparency .....................................................................................1-18

Source Routing ................................................................................................1-18

APPN Services .............................................................................................................1-19

Session Services ...................................................................................................1-19

Directory Services ..................................................................................................1-20

Topology and Routing Services .............................................................................1-20

Conﬁguration Services ...........................................................................................1-21

Management Services ...........................................................................................1-21

For More Information about APPN ...............................................................................1-22

Chapter 2 Enabling APPN Services

Using the Parameter Descriptions ..................................................................................2-1

Enabling APPN over LLC2 Interfaces .............................................................................2-2

Enabling APPN over LLC2 Interfaces Using SRB ..........................................................2-7

Enabling APPN Interfaces over SDLC ..........................................................................2-12

Chapter 3 Editing APPN Parameters

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

Accessing APPN Parameters .........................................................................................3-2

Editing APPN Global Parameters ...................................................................................3-3

APPN Global Advanced Parameters ........................................................................3-5

Editing APPN lnterfaces and Ports ...............................................................................3-14

Deleting APPN Interfaces ......................................................................................3-16

Editing APPN Ports ................................................................................................3-17

Deleting APPN Ports ..............................................................................................3-19

Adding Ports to an APPN Interface ........................................................................3-19

Editing APPN Advanced Port Parameters .............................................................3-23

Page 7

Editing APPN Adjacent Link Stations ...........................................................................3-33

Deleting Adjacent Link Stations .............................................................................3-40

Adding Adjacent Link Stations ...............................................................................3-41

Editing Advanced Adjacent Link Station Parameters .............................................3-47

Editing APPN Connection Networks .............................................................................3-55

Adding APPN Connection Networks ......................................................................3-57

Deleting APPN Connection Networks ....................................................................3-58

Editing APPN Connection Network Ports ...............................................................3-59

Adding APPN Connection Network Ports ..............................................................3-60

Deleting APPN Connection Network Ports ............................................................3-61

Editing APPN Advanced Connection Network Parameters ....................................3-61

Editing APPN Directory Entry Parameters ...................................................................3-66

Adding APPN LU Names to Directory Services .....................................................3-69

Deleting APPN Directory Entires ...........................................................................3-72

Appendix A APPN Base and Optional Function Sets

Appendix B APPN Default Settings

Index

vii

Page 8

Page 9

Figures

Figure 1-1. APPN Network with Different Node Types ...............................................1-4

Figure 1-2. CP-CP and LU-LU Sessions ....................................................................1-5

Figure 1-3. DLUR and DLUS in an APPN Network ....................................................1-7

Figure 1-4. Interface, Port, and Link Station Relationship ..........................................1-8

Figure 1-5. Sample APPN Connection Network ......................................................1-11

Figure 1-6. Nonadjacent LU-LU Session through an Intermediate Node .................1-12

Figure 1-7. APPN ISR Routing Functions in SNA Architecture ................................1-13

Figure 1-8. APPN HPR Routing Functions in SNA Architecture ..............................1-15

Figure 1-9. HPR RTP Connection Supporting APPN Sessions ...............................1-16

Figure 1-10. HPR ANR Routing and Packet Handling Operations .............................1-19

Figure 2-1. Source Route Encapsulation Dialogue Box .............................................2-3

Figure 2-2. APPN Local Node Name Conﬁguration Window .....................................2-3

Figure 2-3. APPN/FR Conﬁguration Window .............................................................2-5

Figure 2-4. Adjacent Link Station Dialogue Box .........................................................2-6

Figure 2-5. Source Route Encapsulation Dialogue Box .............................................2-7

Figure 2-6. Source Routing Global Parameters Window ............................................2-8

Figure 2-7. Edit SR Interface Window ......................................................................2-10

Figure 2-8. APPN Virtual Ring Number Conﬁguration Window ................................2-11

Figure 2-9. SDLC Line Parameters Window ............................................................2-13

Figure 2-10. Select Protocols Window .......................................................................2-15

Figure 2-11. APPN Local Node Name Conﬁguration Window ...................................2-16

Figure 2-12. APPN SDLC Address Conﬁguration Window ........................................2-17

Figure 2-13. Adjacent Link Station Dialogue Box .......................................................2-18

Figure 3-1. Conﬁguration Manager Window ...............................................................3-2

Figure 3-2. Edit APPN Global Parameters Window ...................................................3-3

Figure 3-3. Advanced APPN Global Parameters Window ..........................................3-6

Figure 3-4. APPN Interface List Window ..................................................................3-15

Figure 3-5. APPN Port List Window .........................................................................3-17

Page 10

Figure 3-6. APPN/FR Port Conﬁguration Window ....................................................3-20

Figure 3-7. APPN Port Window ................................................................................3-23

Figure 3-8. APPN Adjacent Link Station List Window ..............................................3-33

Figure 3-9. APPN Adjacent Link Station Port Conﬁguration Window .......................3-41

Figure 3-10. APPN Adjacent Link Station Conﬁguration Window ..............................3-42

Figure 3-11. APPN Adjacent Link Station Advanced Conﬁguration Window .............3-48

Figure 3-12. APPN Connection Network List Window ...............................................3-56

Figure 3-13. Connection Network Conﬁguration Window ...........................................3-57

Figure 3-14. APPN Connection Network Port List Window ........................................3-59

Figure 3-15. Connection Network Port Conﬁguration Window ...................................3-60

Figure 3-16. APPN Connection Network Advanced Parameters Window ..................3-62

Figure 3-17. APPN Directory Entry List Window ........................................................3-67

Figure 3-18. Directory Entry Conﬁguration Window ...................................................3-69

Page 11

Tables

Table 3-1. Link Activation Limit Default Values .......................................................3-26

Table A-1. APPN Base Function Sets ...................................................................... A-1

Table A-2. APPN Optional Function Sets ................................................................. A-4

Table B-1. APPN Global and Advanced Global Parameters .................................... B-1

Table B-2. APPN Interface and Port Parameters ..................................................... B-2

Table B-3. APPN Adjacent Link Station Parameters ................................................ B-4

Table B-4. APPN Connection Networks and Port Parameters ................................. B-5

Table B-5. APPN Directory Services Parameters .................................................... B-6

Page 12

Page 13

About This Guide

This guide describes how to customize Bay Networks™ router software for Advanced Peer-to-Peer Networking (APPN) services. Refer to this guide for

• An overview of APPN, as implemented on Bay Networks routers and Site Manager software (see Chapter 1)

• Instructions on enabling APPN services using Site Manager (see Chapter 2)

• Instructions on conﬁguring APPN parameters using Conﬁguration Manager software (see Chapter 3)

• APPN base and optional function sets Bay Networks supports (see Appendix A)

• A list of APPN parameters and their default settings in the Conﬁguration Manager (see Appendix B)

Audience

Written for system and network managers, this guide describes how to conﬁgure the Bay Networks implementation of APPN to suit your environment.

Before Y ou Begin

Before using this guide, you must complete the following procedures:

• Open a conﬁguration ﬁle

• Specify the router hardware, if this is a local-mode conﬁguration ﬁle

• Select the link- or net-module connector on which you are enabling APPN

Refer to

Conﬁguring Routers

for instructions.

xiii

Page 14

Configuring APPN Services

Bay Networks Customer Support

Bay Networks provides live telephone technical support to our distributors, resellers, and service-contracted customers from two U.S. and three international support centers. If you have purchased your Bay Networks product from a distributor or authorized reseller, contact the technical support staff of that distributor or reseller for assistance with installation, conﬁguration, troubleshooting, or integration issues.

Customers also have the option of purchasing direct support from Bay Networks through a variety of service programs. The programs include priority access telephone support, on-site engineering assistance, software subscription, hardware replacement, and other programs designed to protect your investment.

To purchase any of these support programs, including PhonePlus™ for 24-hour telephone technical support, call 1-800-2LANWAN. Outside the U.S. and Canada, call (408) 764-1000. You can also receive information on support programs from your local Bay Networks ﬁeld sales ofﬁce, or purchase Bay Networks support directly from your reseller. Bay Networks provides several methods of receiving support and information on a nonpriority basis through the following automated systems.

CompuServe

xiv

Bay Networks maintains an active forum on CompuServ e. All you need to join us online is a computer, a modem, and a CompuServe account. We also recommend using the CompuServe Information Manager software, available from CompuServe.

The Bay Networks forum contains libraries of technical and product documents designed to help you manage and troubleshoot your Bay Networks products. Software agents and patches are available, and the message boards are monitored by technical staff and can be a source for problem solving and shared experiences.

Customers and resellers holding Bay Networks service contracts can visit the special libraries to acquire advanced levels of support documentation and software.

To open an account and receive a local dial-up number, call CompuServe at 1-800-524-3388 and ask for Representative No. 591.

• In the United Kingdom, call Freephone 0800-289378.

Page 15

• In Germany, call 0130-37-32.

• In Europe (except for the United Kingdom and Germany), call

• Outside the U.S., Canada, and Europe, call (614) 529-1349 and ask for

Once you are online, you can reach our forum by typing the command GO BAYNETWORKS at any ! prompt.

InfoFACTS

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

W orld Wide Web

The World Wide Web (WWW) is a global information system for ﬁle distribution and online document viewing via the Internet. You need a direct connection to the Internet and a Web Browser (such as Mosaic or Netscape).

About This Guide

(44) 272-760681.

Representative No. 591, or consult your listings for an ofﬁce near you.

Bay Networks maintains a WWW Home Page that you can access at http://www.baynetworks.com. One of the menu items on the Home Page is the Customer Support Web Server, which offers technical documents, software agents, and an E-mail capability for communicating with our technical support engineers.

How to Get Help

For additional information or advice, contact the Bay Networks Technical Response Center in your area:

United States 1-800-2LAN-WAN Valbonne, France (33) 92-966-968 Sydney, Australia (61) 2-903-5800 Tokyo, Japan (81) 3-328-005

Page 16

Configuring APPN Services

Conventions

This section describes the conventions used in this guide. angle brackets (< >) Indicate that you choose the text to enter based on the

arrow character (➔) Separates menu and option names in instructions.

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

192.32.10.12

Example: Protocols

<ip_address>

➔

AppleTalk identiﬁes the

, you enter

ping

AppleTalk option in the Protocols menu.

ping

bold text

Indicates text that you need to enter and command

dinfo

names in text. Example: Use the

command.

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

or all of the options.

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:

Bay Networks Trap Monitor Filters

Set

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 show at routes

nets

, you enter either

show at nets

, but not both.

xvi

Page 17

Ordering Bay Networks Publications

To purchase additional copies of this document or other Bay Networks publications, order by part number from Bay Networks Press™ at the following numbers. You may also request a free catalog of Bay Networks Press product publications.

Phone: 1-800-845-9523 FAX - U.S./Canada: 1-800-582-8000 FAX - International: 1-916-939-1010

Acronyms

ANR Automatic Network Routing APPN Advanced Peer-to-Peer Networking COS class of service CP control point DLC data link control DLCI data link connection identiﬁer DLSw data link switching DLUR dependent logical unit requester DLUS dependent logical unit server DS directory services DSPU down stream physical unit EN end node EP entry point FDDI Fiber Distributed Data Interface FQPCID fully qualiﬁed procedure correlation identiﬁer GDS general data stream HPR High Performance Routing IP Internet Protocol ISR intermediate session routing LAN local area network LEN low-entry networking LLC logical link control

About This Guide

xvii

Page 18

Configuring APPN Services

LU logical unit MAC media access control MDS multiple domain support MIB Management Information Base NCP Network Control Program NN network node NNS network node server PCID procedure correlation identiﬁer PU physical unit RSCV route selection control vector RTP Rapid Transport Protocol SAP service access point SATF shared access transport facility SDLC Synchronous Data Link Control SNA Systems Network Architecture SNMP Simple Network Management Protocol SSCP system services control point SRB source routing bridge TG transmission group TPF transmission priority ﬁeld VRN virtual routing node VTAM Virtual T ecommunications Access Method XID exchange identiﬁcation

xviii

Page 19

Chapter 1

Advanced Peer-to-Peer Networking Overview

IBM Advanced Peer-to-Peer Networking (APPN) architecture concepts include

• APPN node types

• Control points and logical units

• Dependent logical unit requester and server

• APPN interfaces, ports, and link stations

• Connection networks

• Intermediate session routing

• High performance routing

• APPN services

Review these concepts if you are responsible for conﬁguring APPN on Bay Networks routers in your network, or if already familiar with APPN concepts, go directly to Chapter 2 for information on starting APPN started on a router.

1-1

Page 20

Configuring APPN Services

APPN Networking Overview

APPN is an architectural extension of IBM Systems Network Architecture (SN A). As participants in an SNA network, APPN nodes use distributed network services for dynamic routing, connection, topology , and directory information, simplifying network deﬁnition and maintenance.

Bay Networks routers participate as APPN network nodes in IBM SNA network environments (with or without the presence of an IBM mainframe computer) and communicate with adjacent network nodes, end nodes, and low-entry networking nodes. APPN runs on all Bay Netw orks router platforms using local and wide area network facilities, as follows:

• LLC2 media, including Ethernet, Token Ring, and Frame Relay

• LLC2 using Source Routing Bridge (SRB) encapsulation formats over Ethernet, FDDI, SMDS, Frame Relay, and Point-to-Point (PPP) protocols

• SDLC links in point-to-point and multipoint conﬁgurations

The Bay Networks APPN implementation complies with Version 2 of the IBM APPN Network Node speciﬁcation, with advanced optional APPN function sets.

APPN Node Types

1-2

APPN supports the following node types:

• Network nodes

• End nodes

• Low-entry networking nodes

Page 21

Network Nodes

Network nodes (NNs) provide routing and networking services to other network nodes and end nodes. These services include locating network resources, calculating routes, and routing sessions. NNs use conﬁgured or dynamic control-point-to-control-point (CP-CP) sessions with adjacent nodes to manage, communicate, and exchange network topology and resource information. Any adjacent node that does not support control point sessions (such as a low-entry networking node) cannot participate in this exchange and must rely on static deﬁnitions. An NN that provides control point services to end nodes is called a network node server (NNS).

End Nodes

End nodes (ENs) have control points that allow them to re gister and share network information (using CP-CP sessions) with the NNS. End nodes provide APPN services to local users and applications and can operate independently in simple network conﬁgurations. In most conﬁgurations, end nodes are application hosts and workstations that register their resources with their network node server.

Advanced Peer-to-Peer Networking Overview

Low-Entry Networking Nodes

Low-entry networking nodes (LENs) are the simplest type of node in an APPN network. LEN nodes communicate with each other as adjacent peers.

LENs do not use control point sessions and cannot exchange resource information with an NN. Therefore, the resource information for LENs is preconﬁgured and supported at the NN. LENs typically include personal computers and workstations.

igure 1-1 illustrates a simple APPN network with the three APPN node types.

1-3

Page 22

Configuring APPN Services

Low-entry networking

node (LEN)

APPN network node

(NN)

AS/400 end node

(EN)

Low-entry networking

node (LEN)

Figure 1-1. APPN Network with Different Node Types

1-4

Page 23

Control Points and Logical Units

APPN uses control points (CPs) to manage nodes and network resources by establishing CP-CP sessions between nodes. All CP-CP sessions use logical unit (LU) 6.2 sessions.

Advanced Peer-to-Peer Networking Overview

During a CP-CP session (F information. Network nodes use CP-CP sessions to keep track of the network topology and directory information. Adjacent end nodes use CP-CP sessions to register resources and to request directory searches from the NNS.

Network node

APPN.A

CP-CP, LU-LU sessions

Figure 1-2. CP-CP and LU-LU Sessions

Network node

igure 1-2), adjacent nodes exchange network

End node

APPN.C

APPN.B

CP-CP, LU-LU sessions

In Figure 1-2, APPN.C registers its local resources with APPN.B, and sends requests to APPN.B for information about the netw ork and its resources. APPN.B functions as an NNS for APPN.C.

APPN.B has CP-CP sessions with both APPN.A and APPN.C. In this example, APPN.A and APPN.B exchange network topology and cooperate in directory searches.

1-5

Page 24

Configuring APPN Services

Dependent Logical Unit Requester and Server

APPN’s Dependent Logical Unit Requester (DLUR) supports LU type 0,1,2,3 and LU6.2 dependent logical units within APPN. In contrast to the base APPN architecture, which uses independent LUs for LU-to-LU sessions, dependent LUs need a mainframe-based system services control point (SSCP) to establish and manage LU-to-LU sessions. DLUR allows these dependent LUs to use APPN networks by encapsulating the SSCP control ﬂows within the APPN LU 6.2 sessions. The APPN network routes the dependent LU-LU data ﬂows.

DLUR works with the dependent LU server (DLUS) component of the virtual telecommunications access method (VTAM) to provide a path for SSCP ﬂows between VTAM and dependent LUs across an arbitrary APPN backbone network. The DLUR node serves as a point of connection for PU2.0 devices (such as 3270-type devices) to attach to an APPN backbone.

The DLUR and DLUS components in an APPN network allow the SSCP and the PU2.0 device to exchange control ﬂows across the APPN backbone. DLUR and DLUS form a tunnel (called a CP-SVR pipe) that allows the SSCP at the DLUS side of the pipe to send SNA control ﬂows to the PU2.0 device at the DLUR side of the pipe. The CP-SVR pipe is a pair of LU6.2 sessions that encapsulate the SSCP control ﬂows.

1-6

igure 1-3 illustrates the DLUR and DLUS components in APPN.

Page 25

Advanced Peer-to-Peer Networking Overview

SSCP sessions

(encapsulated in

CP-SVR pipe

PU2.0

LU-LU sessions

(natively routed by

APPN network)

APPN network node

with DLUR

Figure 1-3. DLUR and DLUS in an APPN Network

Typically, in a large network, multiple DLUS nodes serve many DLUR nodes distributed across the APPN backbone. A DLUR node can establish pipes with several DLUS nodes, although a single PU2.0 de vice can recei v e traf ﬁc from only one of them, because the device is only controlled by a single SSCP.

When the SSCP and the PU2.0 device exchange control ﬂows, BINDs establish the path that the LU-LU session trafﬁc uses through the network. Since the BIND ﬂows independently of the CP-SVR pipe, the LU-LU trafﬁc can take a different path through the network (the DLUS calculates a route using the topology database and class of service [COS] deﬁnitions). Refer to the “APPN Services” section in this chapter for information on the topology database and COS deﬁnitions.

CP-SVR pipe

VTAM

with DLUS

APPN

backbone

VTAM

1-7

Page 26

Configuring APPN Services

lnterfaces, Ports, and Link Stations

APPN conﬁgurations comprise interfaces, ports, and link stations. Figure 1-4 shows how interfaces, ports, and link stations in a simple APPN network relate.

Note:

In this manual, the term

control (DLC

) in IBM publications.

interface

has the same meaning as

data link

APPN.NNA

Interface E51,LLC2,DLC00001

PORT0001

Link Station 1

Link Station 2

Link Station 3

Figure 1-4. Interface, Port, and Link Station Relationship

APPN.ENA

APPN.ENB

APPN.LENC

1-8

Page 27

Interfaces

Ports

Link Stations

Advanced Peer-to-Peer Networking Overview

Interfaces provide data link control (DLC) processes to ensure reliable deliv ery of information between adjacent stations using a speciﬁc data link protocol, such as LLC or SDLC.

Each APPN interface can support one or more ports. A system-assigned DLC number (such as DLC00008) identiﬁes APPN interfaces

on Bay Networks network nodes. For information on adding and enabling APPN interfaces on Bay Networks

network nodes, refer to Chapter 2.

A port provides a unique access point (such as a MAC/SAP address pair) used by the local Bay Networks network node. A port in an APPN network has a DLC process and a set of conﬁgurable parameters.

A link station is a logical connection between adjacent nodes. Link stations use ports to create this connection. Multiple link stations can exist on a single port, and multiple link stations can exist between the same two nodes. You can conﬁgure a link station entry , or APPN creates it dynamically when a remote node initiates a connection.

Note:

The term adjacent link stations to communicate. Within APPN, a link refers to a logical connection between two nodes. The term throughout this manual and has the same meaning as link.

Link stations have a set of conﬁgurable parameters, such as

• Link station name and the name of the adjacent node

• Adjacent link station role: primary, secondary, or negotiable

• Adjacent link station deﬁnitions, such as MAC and SAP addresses

link

often refers to the physical components that enable two

transmission group (TG)

is also used

1-9

Page 28

Configuring APPN Services

Connection Networks

APPN end nodes on a shared access transport facility (SATF), such as a Token Ring network, are directly connected to each other; they can communicate with each other without having to route trafﬁc through an intermediate network node. However, these end nodes still require deﬁnitions to other nodes and the nodes must be accessible over CP-CP sessions. A APPN conﬁgurations by reducing the number of connections that you must conﬁgure between nodes on an SATF.

When two nodes on the same SATF exist on the same connection network, these nodes are unaware that they have a direct connection to each other; the NNS, acting as an APPN virtual routing node (VRN), calculates a route between the tw o end nodes so that they can communicate directly. For the end nodes to communicate with each other over a connection network, the end nodes require a connection to the VRN and a connection to the NNS.

igure 1-5 illustrates a sample connection network. This connection network,

such as that between EN2 and EN3, may use resources at the network node (NN1) to establish sessions with each other.

connection network

(CN) simpliﬁes

1-10

Page 29

Advanced Peer-to-Peer Networking Overview

EN2 EN3

Traffic

SATF

Virtual Routing

Node

NN1 EN4

Figure 1-5. Sample APPN Connection Network

1-11

Page 30

Configuring APPN Services

Intermediate Session Routing

Intermediate session routing (ISR) provides a reliable, connection-oriented, LU-LU session path between nonadjacent APPN nodes. ISR session connectors (SCs) and a session connection manager (SCM) forward sessions through the intermediate network node (F

At session endpoints, the LU, with control point services, establishes a session with a session partner and routes session data back and forth with the partner LU. INTERMEDIATE network nodes do not control the LU endpoints, and LU services cannot be invoked on these nodes. ISR forwards session data to the next node along the session path.

Intermediate

LU-A to LU-C

Session

Network Node B

igure 1-6).

End Node C

LU-C

NNB

Network Node A

LU-a

ISR Services

LU-A to LU-C

Session

Figure 1-6. Nonadjacent LU-LU Session through an Intermediate Node

In Figure 1-6, LU-A and LU-C are nonadjacent session partners. ISR at NNB forwards session data between the nonadjacent nodes, LU-A and LU-C. NNB creates a session connector (SC) for each session passing through it.

igure 1-7 illustrates ISR function placement in the SNA layered architecture.

Routing takes place at the SNA Layer 4, called the Transmission Control layer. Layer 4 performs ﬂow control operations, speciﬁcally segmentation and reassembly, and pacing.

1-12

Page 31

Advanced Peer-to-Peer Networking Overview

APPN

End Node 

Applicaton

6 5 4

3 2



Connection Oriented  Logical Link

Transport Connection

Logical Unit (LU)

APPN

Network Node

6 5 4

LU-LU Session

Application Data

Logical Unit (LU)



Session Connector

Connection Oriented  Logical Link

Transport Connection

APPN

End Node 

Applicaton

Figure 1-7. APPN ISR Routing Functions in SNA Architecture

Packet Segmentation and Reassembly



6 5

Transmission Control

 Flow Control

-Adaptive Pacing

-Segmenting/

Reassembly

T o maximize network performance, ISR sends the lar gest packet size allo wable on each network interface that you conﬁgure for APPN. Intermediate nodes, when necessary , segment and reassemble pack ets of dif ferent packet sizes. The Max R U Size for ISR Sessions parameter sets the maximum packet size for your APPN conﬁguration.

Adaptive Pacing

ISR’s Adaptive Pacing controls data ﬂow and congestion by managing the number of messages the network node receives during a session. To prevent memory consumption, APPN uses “pacing windows” to control the maximum number of incoming messages. During network activity, this pacing window changes dynamically, allowing the receiving node to adjust the rate at which data ﬂows into its buffers.

1-13

Page 32

Configuring APPN Services

To specify the maximum size of the adaptive pacing window, conﬁgure the ISR Receive Pacing Window parameter.

High Performance Routing

APPN’s high performance routing (HPR) increases data routing performance and reliability. HPR allows high-speed forwarding in intermediate nodes at the Data Link Control layer (Layer 2) of SNA, operating much faster than the intermediate session routing (ISR) base component in APPN. HPR consumes fewer network resources (memory and control processor) by

• Minimizing storage and processing activities in intermediate nodes

• Reducing the amount of error recovery on individual lines

• Implementing nondisruptive path switching function that reroutes sessions

around failed links or nodes

HPR uses the Rapid Transport Protocol (RTP) and Automatic Network Routing (ANR). RTP also supports adaptive rate based (ARB) congestion control.

igure 1-8 illustrates HPR in the SNA layered architecture. Routing takes place at

the SNA Data Link Control layer. Layer 2 performs reliable, sequential delivery, selective retransmission, and nondisruptive rerouting using RTP, as described in this section.

1-14

Page 33

Advanced Peer-to-Peer Networking Overview



RTP Endpoint (End Node or 

Network Node) 7

Application Application



ANR Router Node

(Network Node)

RTP Endpoint

(End Node or

Network Node)



6 5

Transport-Oriented LLC

Logical Unit (LU)

Connectionless LLC

6 5

3 2

Session

Logical Unit (LU)

Connectionless (ANR) Routing with Priority 

Figure 1-8. APPN HPR Routing Functions in SNA Architecture

Data-Link Control

 Reliable. 

Sequential Delivery Selective Retransmission Nondisruptive Rerouting

1-15

Page 34

Configuring APPN Services

Rapid T ransport Protocol

RTP is a connection-oriented, full-duplex protocol that supports data in highspeed networks at APPN NN endpoints. HPR uses RTP connections to transport LU-LU and CP-CP trafﬁc. A single RTP connection allows trafﬁc from multiple APPN sessions (requesting the same class of service) to share the same logical “pipe.” This conserves network resources by minimizing the role of intermediate NNs in the path, and by reducing error recovery and ﬂow control operations.

igure 1-9 illustrates an RTP connection supporting multiple sessions between

endpoint nodes over a logical pipe.

NN

Endpoint Node

Figure 1-9. HPR RTP Connection Supporting APPN Sessions

RTP functions include

• Non-disruptive path switching

• End-to-end error recovery

• End-to-end ﬂow and congestion control

Non-Disruptive Path Switching

The HPR non-disruptive path switch dynamically reroutes RTP connections around failed links or nodes. If a path fails, the RTP component at the NN endpoint of the logical link calculates a new path based on the desired class of service and transmission priority (if it exists). RTP performs the switching transparently so that the session is unaware that rerouting is taking place. Non-disruptive path switching forwards and reverses trafﬁc to follow different routes through the network, and also recovers trafﬁc that was lost at the time of failure.

Multiple

Sessions

RTP Connection over Logical Pipe

NN

Intermediate Node



Multiple

Sessions

NN

Endpoint Node

1-16

Page 35

End-to-End Error Recovery

End-to-end error recovery enables APPN NN endpoints to recovery lost trafﬁc. HPR endpoint NNs always perform end-to-end recovery. However, Site Manager allows you to specify base APPN link-le vel error reco very, where error recovery is done on every link, consuming more network resources.

Note: High-speed links generally have low error rates. Therefore, link-level

recovery may not be necessary in the higher speed HPR conﬁgurations.

When link level recovery is turned off and an error is detected, the packet is discarded, resulting in a gap in the stream of bytes over the RTP connection. When the RTP connection endpoint NN detects the gap in the incoming byte stream, it informs the sender to begin retransmitting from the ﬁrst byte after this point in the stream. RTP supports selective retransmission of parts of the byte stream, when the RTP endpoint requests a range of bytes for retransmission.

End-to-End Flow and Congestion Control

Operating at the NN sending and receiving endpoints of an RTP connection, HPR uses a preventative mechanism called adaptive rate-based (ARB) congestion control. ARB monitors, predicts, and regulates the ﬂow of trafﬁc into the network as conditions change. When the network approaches congestion (increased delay, decreased throughput), ARB reduces the input trafﬁc rate so that a recipient endpoint NN can adequately handle the trafﬁc.

Advanced Peer-to-Peer Networking Overview

With multiple RTP connections over a single link, the ARB function regulates the ﬂow of trafﬁc in all connections. This provides fairness to all connections.

With multiple SNA sessions over a single RTP connection, HPR’s adaptive session-level pacing maintains fairness among the sessions. This prevents one session from unfairly consuming network resources, compared to other sessions on the RTP connection.

1-17

Page 36

Configuring APPN Services

Automatic Network Routing

Automatic network routing (ANR) minimizes storage and processing requirements for routing packets through intermediate nodes. ANR functions include

• Fast packet switching

• Session transparency

• Source routing

Fast Packet Switching

ANR operates at the Data Link Control layer of the SNA architecture. Operating at a lower layer than APPN ISR improves packet switching performance in the intermediate nodes. Functions typically performed at the intermediate node, such as link-level recovery, segmentation, ﬂow and congestion control, are performed at the RTP connection endpoints.

Session T ransparency

Intermediate nodes are not aware of the SNA sessions or the RTP connections established across the nodes. This eliminates the need for storing routing tables and consuming resources (memory and buffers) at the intermediate nodes.

Source Routing

1-18

ANR uses a source routing algorithm. ANR carries the routing information in the network header of each packet. For each activated link, an ANR label is dynamically assigned to the packet. As a packet traverses the network, each node strips off the information it uses in the packet header before forwarding it, allowing the next node to easily ﬁnd its routing information at a ﬁxed place in the header. This allo ws faster switching through a node. Additionally, there is no ANR restriction on the number of hops in the network.

igure 1-10 illustrates how ANR routes packets over an APPN HPR network. The

intermediate network node strips the ﬁrst routing label (A1) from the network header before forwarding the packet on the A1 link. C5 represents the endpoint in the last HPR node.

Page 37

Advanced Peer-to-Peer Networking Overview

RTP Connection

A1 C5

Sessions Sessions

Sending Endpoint Node

Figure 1-10. HPR ANR Routing and Packet Handling Operations

APPN Services

The APPN services on the NN include

• Session services

• Directory services

• Topology and routing services

• Conﬁguration services

• Management services

Session Services

NN1

NN2

Intermediate Node



A1 C5 FF Data C5 FF Data

A1 Stripped off at NN2 Before Delivery to NN3

Receiving Endpoint Node

NN3

Session services (SS) generates unique session identiﬁers, activates and deactivates CP-CP sessions to exchange network information, and assists LUs in initiating and activating LU-LU sessions. Session services

• Invokes directory services to locate a partner LU

• Invokes topology and routing services (TRS) to calculate the optimal route

between the origin and destination node

• Informs management services (MS) about newly activated or deactivated

CP-CP sessions

1-19

Page 38

Configuring APPN Services

Directory Services

Directory services (DS) manages the directory database and locates network resources throughout an APPN network. To locate network resources, directory services at each node collects resource information and maintains the information in a local directory database. Through a CP-CP session between an APPN network node and an adjacent APPN end node, the APPN network node registers (by end node request) the APPN end node’s resources in its local directory database.

An APPN network node maintains database entries for

• Local resources (LUs and the CP)

• End node resources within the APPN network node’s domain

• End node or network node resources outside the APPN network node’s

domain (called cross-domain resources)

An APPN end node or low-entry networking node maintains database entries for

• Local resources

• Local resources on adjacent nodes that have peer-to-peer communication

sessions (without the presence of an APPN network node or control point, in the case of a peer-to-peer end node and low-entry networking node)

Topology and Routing Services

T opology and routing services (TRS) resides in e v ery APPN network node and, in lesser form, in every APPN end node and low-entry networking node. In APPN network nodes, TRS collects and exchanges information on other network nodes, and the links between them. For LU-LU sessions, TRS provides the best route between any two LUs. In APPN end nodes and low-entry networking nodes, TRS collects information on links and adjacent nodes.

In APPN network nodes, TRS creates and maintains the class-of-service (COS) database and a copy of the network topology database. The network topology database contains information on APPN network node connections to other network nodes and connection networks. (A connection network is a method of deﬁning an APPN node attachment to a shared-access transport facility, reducing intermediate node routing and deﬁnition requirements.)

1-20

Page 39

In APPN end nodes, TRS creates and maintains the COS database, and maintains the local topology database (also maintained by TRS at the network node). The local topology database contains information on connections involving the local end nodes: end node-to-end node, end node-to-network node, and end node-to-virtual routing node.

For LU-LU sessions, TRS computes the optimal route through an APPN network between the two nodes on which the LUs reside. A route in an APPN network is an ordered sequence of nodes and transmission groups (TGs) that represents a path from an origin to a destination, called a Route Selection Control Vector (RSCV). In APPN end nodes, TRS uses the local database to select possible transmission groups from the end node to an adjacent node. In APPN network nodes, TRS uses the information provided by the two end nodes, together with the information in the network node’s COS and topology database, to select a route.

Conﬁguration Services

Conﬁguration services (CS) manages links to adjacent APPN nodes. The APPN node operator facility (NOF) initializes conﬁguration services through Site Manager.

Advanced Peer-to-Peer Networking Overview

The basic conﬁguration functions are

• Node deﬁnition

• Interfaces

• Ports

• Adjacent link stations

• Connection networks

• Directory services Refer to Chapter 3, “Editing APPN Parameters,” for detailed information on

conﬁguring APPN nodes.

Management Services

Management services (MS) controls and monitors the node’s resources. If an error condition occurs, APPN recei v es or generates ev ent messages about resources and conditions. For information on the APPN ev ent messages, refer to Event Messages

for Routers and BNX Platforms.

1-21

Page 40

Configuring APPN Services

For More Information about APPN

For more information about APPN, IBM SNA, and related subjects, refer to the following IBM publications:

• IBM Systems Network Architecture: LU6.2 Reference: Peer Protocols

(SC31-6808)

• IBM Systems Network Architecture: APPN Architecture Reference

(SC30-3422)

• IBM Systems Network Architecture: Management Services

(SC30-3346)

• IBM APPN Architecture and Product Implementation Tutorial (GG24-3669)

• IBM AS/400 Adv anced Peer-to-Peer Networking

(GG24-3287)

• IBM Systems Network Architecture: Technical Overview

(GC30-3073)

• IBM Systems Network Architecture: Concepts and Products

(GC30-3072)

1-22

• IBM System Network Architecture: Introduction to Sessions between Logical

Units (GC20-1869)

Page 41

Chapter 2

Enabling APPN Services

This chapter describes how to enable APPN services.

• On Logical Link Control 2 (LLC2) media, including Ethernet, Token Ring,

and Frame Relay

• On LLC2 media using Source Routing Bridge (SRB) encapsulation formats

over Ethernet, FDDI, SMDS, Frame Relay, and Point-to-Point (PPP)

• On Synchronous Data Link Control (SDLC) links in point-to-point and

multipoint networks

This chapter assumes that you have read Conﬁguring Routers and that you have

1. Opened a conﬁguration ﬁle

2. Speciﬁed router hardware if this a local mode conﬁguration ﬁle

3. Selected the connector on which you are enabling APPN

Using the Parameter Descriptions

Each APPN parameter description provides information about default settings, valid parameter options, the parameter function, instructions for setting the parameter, and the Management Information Base (MIB) object ID.

The Technician Interface allows you to modify parameters by issuing set and 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.

2-1

Page 42

Configuring APPN Services

Caution: The Technician Interface does not verify that the value you enter for

a parameter is valid. Entering an invalid value can corrupt your conﬁguration.

Enabling APPN over LLC2 Interfaces

When you conﬁgure APPN on LLC2 interf aces, such as Ethernet and Token Ring, the Conﬁguration Manager requests media access control (MAC) and service access point (SAP) addresses. On synchronous interfaces where you are conﬁguring APPN over Frame Relay, the Conﬁguration Manager requests a data link connection identiﬁer (DLCI) address and a SAP address.

To enable APPN on Ethernet, Token Ring, or Bay Networks synchronous interfaces using Frame Relay:

1. Select APPN from the Select Protocols window.

This menu appears after you select either a link or net module connector that requires a WAN circuit. The Conﬁguration Manager automatically selects the LLC2 option.

2-2

2. Click on OK.

For Frame Relay and Ethernet networks, the “Use Source Route Encapsulation?” dialogue box appears (F

3. Click on Cancel if you are conﬁguring standard LLC ov er Ether net, or if

igure 2-1).

you are conﬁguring Frame Relay using the RFC 1490 routing standard.

Page 43

Enabling APPN Services

Figure 2-1. Source Route Encapsulation Dialogue Box

T o conﬁgure Bay Networks SRB o ver Ethernet or Frame Relay using the RFC 1490 bridging standard, click on OK and refer to the next section, “Enabling APPN over LLC2 Interfaces Using SRB,” for information on the additional screens that appear.

The APPN Local Node Name Conﬁguration window appears (F

Figure 2-2. APPN Local Node Name Conﬁguration Window

Specify the Local Node Name parameter, as follows:

igure 2-2).

2-3

Page 44

Configuring APPN Services

Parameter: Local Node Name

Default: None

Options: Any valid name with up to 17 characters in the format

<NETID.CPNAME>; NETID is the global network name with up to 8 characters followed by a period, and CPNAME is the control point name with up to 8 characters

Function: The Local Node Name parameter identiﬁes the unique name of the

network and the Bay Networks router node name.

Instructions: Enter the node name by ﬁrst specifying up to 8 characters in the network

ID name, type a period, then enter a control point name with up to 8 characters. You must use uppercase characters only and the ﬁrst character must be non-numeric. Blank spaces (leading, trailing, and embedded) are not allowed in the node name. For example, NETW ORKA.SYSTEMA is a valid entry for the Local Node Name parameter.

MIB Object ID: 1.3.6.1.4.1.18.3.5.14.1.1.4

5. Click on OK to add the local node name.

For Frame Relay conﬁgurations, the APPN/FR Conﬁguration window appears (F

igure 2-3). If you are conﬁguring standard LLC over Ethernet, the

Conﬁguration Manager displays the APPN Conﬁguration Windo w where you specify a MAC Address instead of the DLCI Address.

2-4

Page 45

Figure 2-3. APPN/FR Conﬁguration Window

Specify the DLCI Address (for Frame Relay only), MAC Address, and

SAP parameters, as follows:

Enabling APPN Services

Parameter: DLCI Address

Default: None

Options: Valid range depends on the Frame Relay address length as follows:

dress Length — Range

2 bytes — 16-1007 3 bytes — 1024-64511 4 bytes — 131072-8257535

Function: The DLCI is the Frame Relay PVC identiﬁcation number. The Frame

Relay network uses the DLCI to direct basic data ﬂow.

Instructions: Enter a decimal number within the valid range.

MIB Object ID: 1.3.6.1.4.1.18.3.5.14.1.3.1.38

2-5

Page 46

Configuring APPN Services

Parameter: SAP (hex)

Default: None

Options: Any unique SAP 2-digit hexadecimal value, usually 04 with APPN.

Function: Speciﬁes a SAP address that lets multiple applications and protocol

entities in a single computer share a MAC address.

Instructions: Enter a 2-digit hexadecimal value.

MIB Object ID: 1.3.6.1.4.1.18.3.5.14.1.3.1.38

Parameter: MAC Address

Default: None

Options: Any unique 48-bit 12-digit hexadecimal MAC-level address

Function: Speciﬁes a unique MAC-level address for this port.

Instructions: Enter a 12-digit hexadecimal MAC-level address in most signiﬁcant bit

(MSB) noncanonical format, regardless of the media.

MIB Object ID: 1.3.6.1.4.1.18.3.5.14.1.3.1.38

7. Click on OK.

The Adjacent Link Station dialogue box appears (F

Figure 2-4. Adjacent Link Station Dialogue Box

2-6

igure 2-4).

Page 47

8. Click on OK to conﬁgure APPN adjacent link station parameters now.

For information on conﬁguring addjacent link stations, go to the section in Chapter 3 entitled “Editing APPN Adjacent Link Stations.”

9. Click on Cancel.

Go to Chapter 3 for information about conﬁguring APPN.

Enabling APPN over LLC2 Interfaces Using SRB

If you are conﬁguring LLC2 interfaces such as Ethernet, FDDI, SMDS, Frame Relay, and PPP, you can use SRB encapsulation formats. For Ethernet (Bay Networks proprietary SRB over Ethernet) and Frame Relay (RFC1490 Bridging Standard), start at the Source Route Encapsulation dialogue box (F proceed as follows:

Enabling APPN Services

igure 2-5) and

Figure 2-5. Source Route Encapsulation Dialogue Box

Click on OK.

The Source Routing Global Parameters window appears (F

igure 2-6).

2-7

Page 48

Configuring APPN Services

Figure 2-6. Source Routing Global Parameters Window

Edit the SR Bridge Internal LAN ID and the SR Bridge ID parameters in

the Source Routing Global Parameters window.

These are mandatory parameters that you must specify before you can proceed.

2-8

Page 49

Enabling APPN Services

Parameter: SR Bridge Internal LAN ID

Default: 0x1

Range: 0x1 to 0x0fff

Function: Speciﬁes this bridge’s internal LAN ID.

Instructions: Assign an internal LAN ID that is unique among all other internal LAN

IDs and ring IDs in the network.

MIB Object ID: 1.3.6.1.4.1.18.3.5.1.1.2.1.4

Parameter: SR Bridge ID

Default: 0x1

Range: 0x1 to 0x0f

Function: Speciﬁes this bridge’s ID and identiﬁes the Bay Networks source routing

bridges in the network.

Instructions: Assign the same value to all Bay Networks source routing bridges in the

network (unless two bridges operate in parallel). The SR bridge ID must be unique among any other third-party bridge IDs in the network.

MIB Object ID: 1.3.6.1.4.1.18.3.5.1.1.2.1.5

For details about conﬁguring the source routing parameters on this window, refer to Conﬁguring Bridging Services.

3. Click on OK.

The Edit SR Interface window appears (F

igure 2-7).

2-9

Page 50

Configuring APPN Services

Figure 2-7. Edit SR Interface Window

Edit the Source Routing Ring Number parameter in the Edit SR

Interface window.

This is the only parameter that you must specify before you can proceed.

2-10

Page 51

Enabling APPN Services

Parameter: Source Routing Ring Number

Default: 0x0

Range: 0x0 to 0x0fff

Function: Identiﬁes the ring number (ring ID) of this source routing circuit.

Instructions: Assign a ring number (ring ID) to this source routing circuit that is unique

among any other ring IDs, group LAN IDs, or internal LAN IDs in the network.

MIB Object ID: 1.3.6.1.4.1.18.3.5.1.1.2.1.6

For details on how to conﬁgure the source routing parameters on this window, refer to Conﬁguring Bridging Services.

5. Click on OK.

The APPN Virtual Ring Number Conﬁguration window appears (F

Figure 2-8. APPN Virtual Ring Number Conﬁguration Window

Edit the Virtual Ring Number parameter, as follows:

igure 2-8).

2-11

Page 52

Configuring APPN Services

Parameter: Virtual Ring Number (hex)

Default: None

Range: 1 to 4095

Function: Speciﬁes the unique SRB ring number to be used by APPN. It must be

unique in the SRB network. This means that the Virtual Ring Number must be different not only from the ring IDs speciﬁed in the SRB conﬁguration, but different also from other Bay Networks routers running APPN on LLC2/SRB media.

Instructions: Specify the unique LLC ring number in the range 1 to 4095.

MIB Object ID: 1.3.6.1.4.1.18.3.5.1.6.2.25

7. Click on OK.

If this is the ﬁrst interface for which you are conﬁguring APPN, the APPN Local Node Name Conﬁguration window appears (F the ﬁrst interface for which you are conﬁguring APPN, the APPN Conﬁguration window for your speciﬁc network appears. Refer to these ﬁgures and the steps that follow them to complete the APPN conﬁguration.

igure 2-2). If this is not

Enabling APPN Interfaces over SDLC

To conﬁgure APPN on synchronous interfaces (COM1, COM2, etc.) using the SDLC protocol:

1. Select SDLC from the WAN protocols window.

The Conﬁguration Manager displays the SDLC Line Parameters window (F

igure 2-9).

2-12

Page 53

Figure 2-9. SDLC Line Parameters Window

Enabling APPN Services

Edit the Clock Source, Internal Clock Speed, Sync Line Coding, Cable

Type, and RTS Enable parameters, as follows:

Parameter: Clock Source

Default: Internal

Options: ExternalInternal

Function: Speciﬁes the origin of the synchronous timing signals. If you set this

parameter to Internal, this router supplies the required timing signals. If you set this parameter to External, an external network device supplies the required timing signals.

Instructions: Set this parameter to either Internal or External, as appropriate for your

network.

MIB Object ID: 1.3.6.1.4.1.18.3.4.5.1.13

2-13

Page 54

Configuring APPN Services

Parameter: Internal Clock Speed

Default: 64 KB

Options: 1200 B2400 B4800 B7200 B9600 B

19200 B 32000 B38400 B56 KB64 KB 125 KB230 KB420 KB 625 KB833 KB

1.25 MB2.5 MB5 MB

Function: Sets the clock speed of an internally supplied clock when Clock Source is

set to Internal.

Instructions: Click on Values and set the clock speed for the internal clock to the

desired data transmission rate across the synchronous line. The Internal Clock Speed parameter is unavailable when Clock Source is

set to External.

MIB Object ID: 1.3.6.1.4.1.18.3.4.5.1.14

Parameter: Sync Line Coding

Default: NRZ

Options: NRZNRZINRZI Mark

Function: Speciﬁes the line coding of the physical synchronous line. You can

change the value of this parameter to match the line coding of a device at the other end of the line.

This parameter is relevant only for the AN and the ASN routers. Other Bay Networks router platforms require NRZ encoding.

NRZ — Indicates Non-Return to Zero encoding. NRZI — Indicates Non-Return to Zero Inverted encoding. NRZI Mark — Indicates Non-Return to Zero Inverted Mark encoding.

Instructions: Select the appropriate value for synchronous line coding.

MIB Object ID: 1.3.6.1.4.1.18.3.4.5.1.88

2-14

Page 55

Enabling APPN Services

Parameter: Cable Type

Default: Null

Options: NullRS232RS422V35X21

Function: Speciﬁes the cable interface to the network.

Instructions: Select the cable interface that you are using to connect to the network.

MIB Object ID: 1.3.6.1.4.1.18.3.4.5.1.83

Parameter: RTS Enable

Default: Disabled

Options: Enabled | Disabled

Function: Controls the toggling of the Request to Send (RTS) signal on the

interface. For manual dial modems (2-wire), you should set this parameter to Enabled. For leased modems (4-wire), the setting should be Disabled.

Instructions: Click on Values and select Enabled or Disabled.

MIB Object ID: 1.3.6.1.4.1.18.3.4.5.1.16

3. Click on OK.

The Select Protocols window appears (F

Figure 2-10. Select Protocols Window

Select APPN and click on OK.

igure 2-10).

2-15

Page 56

Configuring APPN Services

If this is the ﬁrst interface for which you are conﬁguring APPN, the APPN Local Node Name Conﬁguration window appears (F the APPN SDLC Address Conﬁguration window appears (F

Figure 2-11. APPN Local Node Name Conﬁguration Window

Specify the Local Node Name parameter.

igure 2-11). Otherwise,

igure 2-12).

2-16

If this is not the ﬁrst APPN interface on this router, omit this step and go to Step 7.

Page 57

Enabling APPN Services

Parameter: Local Node Name

Default: None

Options: Any valid name with up to 17 characters in the format

<NETID.CPNAME>; NETID is the global network name with up to 8 characters followed by a period, and CPNAME is the control point name with up to 8 characters.

Function: The Local Node Name parameter identiﬁes the unique name of the

network and the Bay Networks router node name.

Instructions: Enter the node name by ﬁrst specifying up to 8 characters in the network

ID name; type a period; and then enter a control point name with up to 8 characters. You must use uppercase characters only and the ﬁrst character must be non-numeric. Blank spaces (leading, trailing, and embedded) are not allowed in the node name. For example, NETW ORKA.SYSTEMA is a valid entry for the Local Node Name parameter.

MIB Object ID: 1.3.6.1.4.1.18.3.5.14.1.1.4

6. Click on OK to add the local node name.

The APPN SDLC Address Conﬁguration window appears (F

Figure 2-12. APPN SDLC Address Conﬁguration Window

Specify the SDLC address for the interface, as follows:

igure 2-12).

2-17

Page 58

Configuring APPN Services

Parameter: SDLC Address (hex)

Default: None

Options: Any unique 2-digit hexadecimal SDLC-level address

Function: Speciﬁes a unique SDLC address for this circuit.

Instructions: Enter a 2-digit hexadecimal address.

MIB Object ID: 1.3.6.1.4.1.18.3.5.14.1.3.1.38

8. Click on OK.

The Adjacent Link Station dialogue box appears (F

Figure 2-13. Adjacent Link Station Dialogue Box

To conﬁgure APPN adjacent link station parameters now, go to the section in Chapter 3 entitled “Editing APPN Adjacent Link Stations.”

9. Click on Cancel.

Go to the beginning of Chapter 3 for information about conﬁguring APPN.

igure 2-13).

2-18

Page 59

Chapter 3

Editing APPN Parameters

Once you successfully enable an APPN interface on the router, you can edit parameters and customize APPN services.

This chapter describes how to use the Conﬁguration Manager to edit the following parameters:

• Global and advanced

• Interface and port

• Adjacent link station

• Connection network

• Directory services The instructions assume you have already added one or more interfaces to a router

conﬁguration ﬁle that you now want to edit for APPN. (Refer to Conﬁguring Routers to learn how to add interfaces to the conﬁguration ﬁle.)

Using the Parameter Descriptions

3-1

Page 60

Configuring APPN Services

Caution: The Technician Interface does not verify that the value you enter for

a parameter is valid. Entering an invalid value can corrupt your conﬁguration.

Accessing APPN Parameters

You can access all APPN operational parameters from the Conﬁguration Manager window (F access this window.)

igure 3-1). (Refer to Conﬁguring Routers for instructions about how to

Figure 3-1. Conﬁguration Manager Window

3-2

Page 61

Editing APPN Global Parameters

To edit APPN global parameters from Conﬁguration Manager window

igure 3-1) and proceed as follows

1. Select Protocols➔APPN➔Global.

Editing APPN Parameters

The Edit APPN Global Parameters window appears (F

2. Edit the parameters you want to change.

igure 3-2).

Use the descriptions that follow as a guide.

3. Click on OK to save your changes and exit the window, or select

Advanced to further customize APPN global parameter settings.

Figure 3-2. Edit APPN Global Parameters Window

3-3

Page 62

Configuring APPN Services

Parameter: APPN Enable/Disable

Default: Enable

Options: Enable | Disable

Function: Globally enables or disables APPN on the router.

Disable – Forces every APPN interface existing on the node into the “down” (inoperative) state.

Enable – Reinitializes every APPN interface existing on the node; each interface maintains the most recent setting of its own Interface Enable/Disable parameter.

Instructions: Select Disable to force every APPN interf ace existing on the node into the

“down” (inoperative) state. Select Enable to globally reinitialize all APPN interfaces conﬁgured on

the node; each interface will maintain the most recent setting of its own Interface Enable/Disable parameter.

MIB Object ID: 1.3.6.1.4.1.18.3.5.14.1.1.2

Parameter: Local Node Name

Default: None

Options: Any valid name with up to 17 characters in the format

<NETID.CPNAME>; NETID is the global network name with up to 8 characters followed by a period, and CPNAME is the control point name with up to 8 characters

Function: The Local Node Name parameter identiﬁes the unique name of the

network and the Bay Networks router node name.

Instructions: Specify up to 8 characters for the network ID name; follow with a period;

then type a control point name with up to 8 characters. You must use uppercase characters only and the ﬁrst character must be non-numeric. Blank spaces (leading, trailing, and embedded) are not allowed in the node name. For example, NETWORKA.SYSTEMA is a valid entry for the Local Node Name parameter.

MIB Object ID: 1.3.6.1.4.1.18.3.5.14.1.1.4

3-4

Page 63

Editing APPN Parameters

Parameter: Local ID Block

Default: None

Options: A valid string of 3 hexadecimal digits

Function: A unique hexadecimal value identiﬁes the APPN product in this NN. The

number is the ﬁrst 3 digits of the node identiﬁcation.

Instructions: Accept the displayed value or enter 3 hexadecimal digits in this ﬁeld.

MIB Object ID: 1.3.6.1.4.1.18.3.5.14.1.1.6

Parameter: Local ID Number

Default: None

Options: A valid string of 5 hexadecimal digits (0 to 9, A,B,C,D,E,F)

Function: Identiﬁes the local APPN network node and is present in APPN alerts and

exchange identiﬁcations (XIDs). These 5 digits are combined with the 3-digit local ID block to form a unique XID node identiﬁcation. The APPN network node and the adjacent node exchange node identiﬁcations when establishing a connection.

Instructions: Enter 5 hexadecimal digits.

MIB Object ID: 1.3.6.1.4.1.18.3.5.14.1.1.7

APPN Global Advanced Parameters

To edit the APPN global advanced parameters from the Edit APPN Global Parameters window (F

1. Click on Advanced.

The Advanced APPN Global Parameters window appears (F window contains general parameters associated with APPN directory services, intermediate session routing, and topology and routing services.

igure 3-2)

igure 3-3). This

3-5

Page 64

Configuring APPN Services

Figure 3-3. Advanced APPN Global Parameters Window

Click on each parameter value that you want to change; then edit the

displayed value.

Use the parameter descriptions that follow as a guide.

3. Click on OK to save your changes and exit the window.

3-6

Page 65

Editing APPN Parameters

Parameter: Route Addition Resistance

Default: 128

Range: 0 to 255

Function: Indicates the relative desirability of using this network node for

intermediate session routing (ISR) when multiple paths exist.

Instructions: Enter a value in the range 0 to 255. The lower the value, the more

desirable the node becomes for ISR.

MIB Object ID: 1.3.6.1.4.1.18.3.5.14.1.1.21

Parameter: Endpoint Session RSCV Storage

Default: Enable

Options: Enable | Disable

Function: When enabled, stores route selection control vector information used by

the network node if it is the endpoint (origin or destination) node in the route. This parameter is useful when you are using the Technician Interface to debug logged APPN events and statistics. Refer to Using Technician Interface Scripts for information on using the show appn command.

When enabled, this parameter consumes additional memory for each endpoint session.

Instructions: Select Enable to enable endpoint session RSCV storage. Select Disable to

disable endpoint session RSCV storage.

MIB Object ID: 1.3.6.1.4.1.18.3.5.14.1.1.29

3-7

Page 66

Configuring APPN Services

Parameter: Max Directory Entries

Default: 0

Options: A value of 0 indicates an unlimited number of entries; otherwise, any

positive numeric value

Function: Speciﬁes the maximum number of entries that APPN stores in the

directory database at the network node. The directory database stores information about network resources and their location in the APPN network.

Instructions: Enter a value large enough for the network being managed, or specify 0

for unlimited entries.

MIB Object ID: 1.3.6.1.4.1.18.3.5.14.1.1.32

Parameter: Max Cached Directory Entries

Default: 100

Options: Any positive numeric value

Function: Speciﬁes the maximum number of cached directory entries that APPN

stores in the local directory database at any one time. The caching can ultimately result in large local directory databases that may include out-of-date resource entries. If the maximum number is reached and if all entries are in use, new entries to be cached will replace the oldest cache entries.

Instructions: Enter a value large enough for the network being managed. Increase the

current value if the oldest valid entries are being replaced on a regular basis.

MIB Object ID: 1.3.6.1.4.1.18.3.5.14.1.1.31

3-8

Page 67

Editing APPN Parameters

Parameter: Network Locate Timeout (in seconds)

Default: 60

Options: Specify 0 to indicate no timeouts

Function: Speciﬁes the length of time (in seconds) before a network search times

out. The network search function locates network resources and controls the ﬂow of search requests and replies throughout the network.

Instructions: Enter a positive time value in seconds. If directory services at the local

network node does not receive a search response at the completion of this timeout value, the search is terminated. When the local network node receives the search response, the search is complete.

MIB Object ID: 1.3.6.1.4.1.18.3.5.14.1.1.33

Parameter: TRS Route Tree Cache Size

Default: 8

Options: Specify any positive numeric value larger than or equal to 8

Function: Speciﬁes the size of the topology and routing services (TRS) tree

database. The tree database allows a network node to cache optimal routes from the local APPN node to other network nodes (tree caching).

Instructions: Enter a positive numeric value larger than or equal to 8, to indicate the

maximum number of routing trees to be stored in the database.

MIB Object ID: 1.3.6.1.4.1.18.3.5.14.1.1.34

Parameter: TRS Route Tree Cache Usage Limit

Default: 8

Options: Any positive numeric value larger than or equal to 1

Function: Speciﬁes the maximum number of times a route tree will be used before

route selection services (RSS) calculates a new route tree for that class of service (COS).

Instructions: Enter any positive numeric value larger than or equal to 1.

MIB Object ID: 1.3.6.1.4.1.18.3.5.14.1.1.35

3-9

Page 68

Configuring APPN Services

Parameter: Max NNs in Topology DB (0 = unlimited)

Default: 0

Options: Any positive number; specify 0 to indicate an unlimited number of

network nodes

Function: Speciﬁes the maximum number of network nodes (routers) in the network

topology database.

Instructions: Specify 0 to include all network nodes.

MIB Object ID: 1.3.6.1.4.1.18.3.5.14.1.1.36

Parameter: Max TGs in Topology DB (0 = unlimited)

Default: 0

Options: Any valid positive number; specify 0 to indicate an unlimited number of

transmission groups (TGs)

Function: Speciﬁes the maximum number of TGs in the network topology database.

A TG represents a single unidirectional connection (or link) to an adjacent link station.

Instructions: Specify 0 to include all TGs.

MIB Object ID: 1.3.6.1.4.1.18.3.5.14.1.1.37

Parameter: Max Number of ISR Sessions

Default: 1000

Options: Any valid positive number greater than or equal to 100

Function: Speciﬁes the maximum number of intermediate session routing (ISR)

sessions that the local network node can support concurrently.

Instructions: This parameter controls the maximum number of ISR sessions. Enter a

value of 100 or greater.

MIB Object ID: 1.3.6.1.4.1.18.3.5.14.1.1.38

3-10

Page 69

Editing APPN Parameters

Parameter: ISR Congestion Threshold

Default: 900

Options: Any positive numeric value less than the Max Number of ISR Sessions

parameter setting

Function: Speciﬁes the maximum number of ISR sessions before the node considers

itself congested, causing it to direct new sessions away. A network node is no longer congested when the number of ISR sessions drops to the setting of the ISR Decongestion Threshold parameter.

Instructions: Enter any positive numeric value less than the setting for the Max Number

of ISR Sessions parameter. In most cases, a value equal to 90% of the Max Number of ISR Sessions parameter is a reasonable value.

MIB Object ID: 1.3.6.1.4.1.18.3.5.14.1.1.39

Parameter: ISR Decongestion Threshold

Default: 800

Options: Any positive numeric value less than the ISR Congestion Threshold

parameter setting

Function: Speciﬁes the number of active ISR sessions that the local network node

must drop to before it is no longer congested. A network node is congested when the number of ISR sessions reaches the ISR congestion threshold.

Instructions: Enter any positive numeric value that is less than the current ISR

Congestion Threshold parameter setting. In most cases, a value equal to 80% of the Max Number of ISR Sessions parameter is a reasonable value.

MIB Object ID: 1.3.6.1.4.1.18.3.5.14.1.1.40

3-11

Page 70

Configuring APPN Services

Parameter: Max RU Size for ISR Sessions

Default: 4096

Range: 256 to 4096, inclusive

Function: Speciﬁes the maximum request unit (RU) size for the segmentation and

reassembly of session and nonsession trafﬁc during the ISR sessions.

Instructions: Enter a positive number in the range 256 to 4096.

MIB Object ID: 1.3.6.1.4.1.18.3.5.14.1.1.41

Parameter: ISR Receive Pacing Window

Default: 7

Range: 1 to 63, inclusive

Function: Speciﬁes the maximum number of messages that the network node can

receive in one windo w during an ISR session. Pacing windo ws control the number of messages to prevent memory consumption.

Instructions: Enter a positive number in the range 1 to 63. Entering higher values may

improve performance, but will consume more memory.

MIB Object ID: 1.3.6.1.4.1.18.3.5.14.1.1.42

Parameter: ISR Session RSCV Storage

Default: Enable

Options: Enable | Disable

Function: Enables or disables the storage of route selection control vectors (RSCVs)

during ISR sessions. This parameter is useful for debugging. When enabled, it consumes additional memory for each ISR session.

The intermediate network node uses RSCV information to obtain the next node and a transmission group (TG) to the node along a route. The maximum number of APPN nodes and TGs a session can traverse is limited to the size of the RSCV.

Instructions: Select Enable to enable ISR session RSCV storage. Select Disable to

disable ISR session RSCV storage.

MIB Object ID: 1.3.6.1.4.1.18.3.5.14.1.1.43

3-12

Page 71

Editing APPN Parameters

Parameter: DLUR Support Enable/Disable

Default: Disable

Options: Enable | Disable

Function: Enables or disables Dependent Logical Unit Requester (DLUR) support

at the network node. DLUR is an APPN component that allows dependent logical units (LU type 0,1,2,3 and dependent LU6.2) within APPN.

Instructions: Click on Values and select Enable to start DLUR at the network node, or

select Disable to stop DLUR at the network node.

MIB Object ID: 1.3.6.1.4.1.18.3.5.14.1.1.45

Parameter: DLUR-DLUS RSCV Storage

Default: Enable

Options: Enable | Disable

Function: Enables or disables the storage of route selection control vectors (RSCVs)

during DLUR/DLUS sessions. This parameter is useful for network monitoring and debugging. When enabled, it will consume additional memory for each DLUR/DLUS session. It is not used if the DLUR Support Enable/Disable parameter is set to Disable.

Instructions: Click on Values and select Enable to enable DLUR-DLUS RSCV storage.

Select Disable to disable DLUR-DLUS RSCV storage.

MIB Object ID: 1.3.6.1.4.1.18.3.5.14.1.1.44

Parameter: HPR Support

Default: Enable

Options: Enable | Disable

Function: Enables HPR on this node.

Instructions: Click on Values and select Enable or Disable.

MIB Object ID: 1.3.6.1.4.1.18.3.5.14.1.1.50

3-13

Page 72

Configuring APPN Services

Parameter: HPR Path Switch Controller Support

Default: Disable

Options: Enable | Disable

Function: Enables this node as an HPR patch switch controller/initiator. This

parameter is available when the HPR Support parameter is set to Enable. Typically, you only set this parameter to Enable if your netw ork node is a

mobile or wireless (satellite communications) partner. The Enable setting prevents unneeded path switch attempts by the non-mobile partner.

Instructions: Click on Values and select Enable or Disable.

MIB Object ID: 1.3.6.1.4.1.18.3.5.14.1.1.51

Editing APPN lnterfaces and Ports

To edit APPN Interface parameters, begin at the Conﬁguration Manager window

efer to Figure 3-1) and proceed as follows:

1. Select Protocols➔APPN➔Interfaces.

3-14

The APPN Interface List window appears (F

2. Edit those parameters you want to change, using the APPN conﬁguration

igure 3-4).

windows that appear.

Page 73

Figure 3-4. APPN Interface List Window

Editing APPN Parameters

Click on Apply to save your changes.

4. Click on Done to exit the window.

To display and enable (or disable) the current port(s) on an interface, add additional ports to the interface, delete ports, or edit advanced port parameters, click on Ports.

Parameter: Interface Enable/Disable

Default: Enable

Options: Enable | Disable

Function: Enables or disables APPN routing on this interface.

Enable – Initializes the selected APPN interface. You can also use the Enable setting to initialize an existing APPN interface that you disabled earlier.

3-15

Page 74

Configuring APPN Services

Disable – Forces the APPN interface into the “down” (inoperative) state.

Instructions: Select Disable to disable APPN routing over this interface.

Select Enable to enable or re-enable APPN routing over this interface.

MIB Object ID: 1.3.6.1.4.1.18.3.5.14.1.2.1.2

Deleting APPN Interfaces

To delete an interface from the APPN Interface List window (refer to Figure 3-4), select the interface, then click on Delete. The system software deletes the interface entry from the APPN conﬁguration.

3-16

Page 75

Editing APPN Ports

The APPN Interface List window (refer to Figure 3-4) allows you to enable or disable APPN ports, add and delete APPN ports on existing interfaces, and edit advanced port parameters. From the APPN Interface List window,

1. Select Ports.

Editing APPN Parameters

The APPN Port List window appears (F

2. Highlight the port you want to modify.

igure 3-5).

The parameter values associated with that interface appear in the parameters window and change dynamically with each port that you select.

3. Click on Apply to save your changes.

Figure 3-5. APPN Port List Window

Click on Done to exit the window.

3-17

Page 76

Configuring APPN Services

Parameter: Port Enable/Disable

Default: Enable

Options: Enable | Disable

Function: Enables or disables APPN routing on this port.

Enable — Initializes the selected APPN port. You can also use the Enable setting to initialize an existing APPN port that you disabled earlier.

Disable — Forces the APPN port into the “down” (inoperative) state.

Instructions: Select Disable to disable APPN routing over this port.

Select Enable to enable or re-enable APPN routing over this port.

MIB Object ID: 1.3.6.1.4.1.18.3.5.14.1.3.1.2

Parameter: Port Address

Default: None

Options: None

Function: Speciﬁes the interface address for this port.

Instructions: This is the MAC address, SDLC address, or DLCI and SAP address that

you speciﬁed when you added the original circuit to the interface. A MA C address starts with the 0x preﬁx and ends with the SAP value.

MIB Object ID: 1.3.6.1.4.1.18.3.5.14.1.3.1.38

3-18

Page 77

Parameter: Local Link Station Role

Default: Negotiable

Options: Negotiable | Primary | Secondary

Function: Speciﬁes the initial role of the local network node when activating

adjacent link stations through this port. Negotiable means that the local network node can be either primary or secondary and the actual role is determined during link activation. A link between the two nodes may require that one link station takes the role of primary link station and one link station takes the role of secondary link station.

Instructions: Click on Values to display the options and select Negotiable, Primary, or

Secondary.

MIB Object ID: 1.3.6.1.4.1.18.3.5.14.1.3.1.8

Deleting APPN Ports

To delete a port from an interface on the APPN Port List window (refer to

Figure 3-5), select the port, then click on Delete. The system software deletes the

entry from the APPN conﬁguration.

Editing APPN Parameters

Adding Ports to an APPN Interface

To add a port to an APPN interface, display the APPN Port List window

igure 3-5) and proceed as follows:

1. Click on Add.

The APPN Port Conﬁguration or the APPN/FR Port Conﬁguration window appears (F

igure 3-6).

3-19

Page 78

Configuring APPN Services

Figure 3-6. APPN/FR Port Conﬁguration Window

Enter values for the Port Name, P ort Number, Port MAC Addr ess or Port

DLCI Address, Port SAP, and Local Link Station Role parameters.

If you are conﬁguring SDLC, the SDLC Address parameter appears instead of the Port MAC Address parameter. If you are conﬁguring Frame Relay on an LLC2 interface, the Port DLCI Address parameter appears.

3. Click on OK to save your entries to the conﬁguration ﬁle.

The APPN Port List window (r

Parameter: Port Name

Default: None

Options: Up to 8 alphanumeric uppercase characters

Function: Speciﬁes the name of the newly added port.

Instructions: Enter up to 8 alphanumeric uppercase characters with no blank spaces

(leading, trailing, or embedded).

MIB Object ID: 1.3.6.1.4.1.18.3.5.14.1.3.1.15

3-20

efer to Figure 3-5) reappears.

Page 79

Editing APPN Parameters

Parameter: Port Number

Default: None

Options: Any unique 3-digit number

Function: Speciﬁes a unique number to identify this port, if more than one port is

conﬁgured on an interface.

Instructions: Enter any 3-digit value.

MIB Object ID: 1.3.6.1.4.1.18.3.5.14.1.3.1.16

Parameter: Port DLCI Address

Default: None

Options: Valid range changes based on the Frame Relay address length as follows:

dress Length — Range

2 bytes — 16-1007 3 bytes — 1024-64511 4 bytes — 131072-8257535

Function: The DLCI is the Frame Relay PVC identiﬁcation number. The Frame

Relay network uses the DLCI to direct basic data ﬂow.

Instructions: Enter a decimal number within the valid range.

MIB Object ID: 1.3.6.1.4.1.18.3.5.14.1.3.1.38

Parameter: Port MAC Address

Default: None

Options: Any unique 48-bit, 12-digit hexadecimal MAC-level address

Function: Speciﬁes a unique MAC-level address, DLCI (for Frame Relay), or SDLC

address.

Instructions: Enter a 12-digit MAC hexadecimal address in MSB non-canonical form

(regardless of the media), a DLCI address, or an SDLC address.

MIB Object ID: 1.3.6.1.4.1.18.3.5.14.1.3.1.38

3-21

Page 80

Configuring APPN Services

Parameter: Port SAP (hex)

Default: None

Options: Any unique SAP 2-digit hexadecimal value, usually 04

Function: Speciﬁes a SAP address that lets multiple applications and protocol

entities in a single computer share a MAC address.

Instructions: Enter a 2-digit hexadecimal value.

MIB Object ID: 1.3.6.1.4.1.18.3.5.14.1.3.1.38

Parameter: SDLC Address (hex)

Default: None

Options: Any unique 2-digit hexadecimal SDLC-level address

Function: Speciﬁes a unique SDLC address for this circuit.

Instructions: Enter a 2-digit hexadecimal address.

MIB Object ID: 1.3.6.1.4.1.18.3.5.14.1.3.1.38

Parameter: Local Link Station Role

Default: Negotiable

Options: Negotiable | Primary | Secondary

Function: Speciﬁes the initial role of the local network node when activating

adjacent link stations through this port. Negotiable means that the local network node can be either primary or

secondary and the actual role is determined during link activation. A link between the two nodes may require one link station to take the role of

primary link station and the other link station to take the role of secondary link station.

Instructions: Click on Values to display the options and select Negotiable, Primary, or

Secondary.

MIB Object ID: 1.3.6.1.4.1.18.3.5.14.1.3.1.8

3-22

Page 81

Editing APPN Advanced Port Parameters

To edit the APPN advanced port parameters, display the APPN Port List window

efer to Figure 3-5) and

1. Click on Advanced.

Editing APPN Parameters

The APPN Port window appears (F

igure 3-7).

Figure 3-7. APPN Port Window

Click on each parameter value that you want to change, then enter a new

value.

3. Click on OK to save your changes and return to the APPN Port List

window (F

igure 3-5).

3-23

Page 82

Configuring APPN Services

Parameter: Max Receive BTU Size

Default: 2057

Range: 256 to 4105

Function: Speciﬁes the maximum Basic Transmission Unit (BTU) size that this

network node can receive. Each link station determines its o wn maximum BTU size based on local node deﬁnitions and exchange identiﬁcation (XID) information received from the interface and the adjacent link station.

Instructions: Enter a number in the range 256 to 4105 that the node can handle.

MIB Object ID: 1.3.6.1.4.1.18.3.5.14.1.3.1.9

Parameter: Max Send BTU Size

Default: 2057

Range: 256 to 4105

Function: Speciﬁes the maximum Basic Transmission Unit (BTU) size that can be

sent over this port. Each link station determines its own maximum send BTU size based on local node deﬁnitions and exchange identiﬁcation (XID) information received from the interface and the adjacent link station.

Instructions: Enter a number in the range 256 to 4105.

MIB Object ID: 1.3.6.1.4.1.18.3.5.14.1.3.1.24

Parameter: Max I-Frame Window

Default: 7

Options: A numeric value not exceeding 127

Function: Speciﬁes the maximum number of information frames (I-frames) that the

local network node can receive before it sends an acknowledgment.

Instructions: Enter a number in the range 1 to 127.

MIB Object ID: 1.3.6.1.4.1.18.3.5.14.1.3.1.10

3-24

Page 83

Editing APPN Parameters

Parameter: Total Link Activation Limits

Default: 256

Range: 0 to 256; see Table 3-1

Function: Speciﬁes the link activation limit for this port. The value is the maximum

number of inbound and outbound link stations that the port will allow in this conﬁguration. The maximum value depends on the setting of the Local Link Station Role parameter and the type of port, as listed in Table 3-1.

Instructions: Specify a value in the range 0 to 256. The value must be greater than or

equal to the combined settings for the Inbound Link Acti v ation Limits and Outbound Link Activation Limits parameters.

MIB Object ID: 1.3.6.1.4.1.18.3.5.14.1.3.1.17

Parameter: Inbound Link Activation Limits

Default: 128

Range: 0 to 256; see Table 3-1

Function: Speciﬁes the inbound link activation limit for this port. The value is the

maximum number of inbound link stations that the port will allow in this conﬁguration.

Instructions: Specify a value in the range 0 to 256. This value plus the current setting

for the Outbound Link Activation Limits parameter must be less than or equal to the current Total Link Activation Limits parameter setting.

MIB Object ID: 1.3.6.1.4.1.18.3.5.14.1.3.1.18

3-25

Page 84

Configuring APPN Services

Parameter: Outbound Link Activation Limits

Default: 128

Range: 0 to 256; see Table 3-1

Function: Speciﬁes the maximum outbound link activation limit for this port. The

value is the maximum number of outbound link stations that the port will allow in this conﬁguration.

Instructions: Specify a value in the range 0 to 255. This value plus the current setting

for the Inbound Link Activation Limits parameter must be less than or equal to the Total Link Activation Limits parameter setting.

MIB Object ID: 1.3.6.1.4.1.18.3.5.14.1.3.1.19

Table 3-1. Link Activation Limit Default Values

Port T ype

Leased Secondary 1 1 0 Leased Negotiable 1 0 0 Leased Primary 256 0 256 SATF any 256(x+y) 128(x) 128(y)

Local Link Station Role

Total Link Activation Limit

Inbound Link Activation Limits

Outbound Link Activation Limits

3-26

Page 85

Editing APPN Parameters

Parameter: Implicit CP Sessions

Default: Yes

Options: Yes | No

Function: Speciﬁes whether CP-to-CP sessions are permitted for dynamic link

stations. Dynamic link stations are link stations that are not deﬁned on this port, but are activated by the adjacent node.

Instructions: Click on Values and select Yes or No.

MIB Object ID: 1.3.6.1.4.1.18.3.5.14.1.3.1.25

Parameter: Implicit Limited Resource

Default: Yes

Options: Yes | No

Function: Speciﬁes whether dynamic link stations on this port should be deﬁned as

limited resources. A limited resource link station deactivates after the number of sessions using the port drops to zero.

Instructions: Click on Values and select Yes or No.

MIB Object ID: 1.3.6.1.4.1.18.3.5.14.1.3.1.26

3-27

Page 86

Configuring APPN Services

Parameter: Implicit Effective Capacity

Default: 16M

Options: 1200

2400 4800 7200 9600 14400 19200 48000 56000 64000 4M 10M 16M Maximum

Function: The Effective Capacity is the highest bit-transmission rate that the TG can

obtain before being considered overloaded. The link bandwidth and maximum load factor determine this value. TGs to dynamic link stations on this port use this value.

Instructions: Click on Values and select a number from the list.

MIB Object ID: 1.3.6.1.4.1.18.3.5.14.1.3.1.27

Parameter: Implicit Connection Cost

Default: 128

Range: 0 to 255, inclusive

Function: Speciﬁes the relative cost (per connect time) of using a TG to dynamic

link stations on this port. A v alue of 0 indicates no cost, and a v alue of 255 indicates maximum cost. The cost per connect time is typically based on the applicable tariffs for the transmission facility this TG uses. An X.25 network, for example, may have a high connection cost for dynamic link stations.

Instructions: Enter a number in the range 0 to 255.

MIB Object ID: 1.3.6.1.4.1.18.3.5.14.1.3.1.28

3-28

Page 87

Editing APPN Parameters

Parameter: Implicit Byte Cost

Default: 128

Range: 0 to 255, inclusive

Function: Speciﬁes the relative cost of transmitting a byte over this TG to a dynamic

link station on this port. A value of 0 indicates no cost, and a value of 255 indicates maximum cost. An X.25 netw ork, for example, may ha v e a high byte cost for dynamic link stations.

Instructions: Enter a number in the range 0 to 255.

MIB Object ID: 1.3.6.1.4.1.18.3.5.14.1.3.1.29

Parameter: Implicit Security

Default: Nonsecure

Options: Nonsecure

Public-Switched Underground Conduit Encrypted Guarded radiation Maximum

Function: Speciﬁes the security level of the TG to the dynamic link stations on this

port.

Instructions: Click on Values and select one of the common deﬁnitions indicated under

Options.

MIB Object ID: 1.3.6.1.4.1.18.3.5.14.1.3.1.30

3-29

Page 88

Configuring APPN Services

Parameter: Implicit Delay

Default: Negligible

Options: Negligible

Terrestrial Packet Long Maximum

Function: Speciﬁes the propagation delay, or the relative amount of time that it tak es

for a signal to travel the length of a TG to dynamic link stations on this port.

Instructions: Click on Values and select a common deﬁnition indicated under Options.

MIB Object ID: 1.3.6.1.4.1.18.3.5.14.1.3.1.31

Parameter: Implicit User-Deﬁned 1

Default: 128

Range: 0 to 255

Function: Speciﬁes the ﬁrst user-deﬁned TG characteristic to a dynamic link station

on this port.

Instructions: Enter a value in the range 0 to 255.

MIB Object ID: 1.3.6.1.4.1.18.3.5.14.1.3.1.32

Parameter: Implicit User-Deﬁned 2

Default: 128

Range: 0 to 255

Function: Speciﬁes the second user-deﬁned TG characteristic to a dynamic link

station on this port.

Instructions: Enter a value in the range 0 to 255.

MIB Object ID: 1.3.6.1.4.1.18.3.5.14.1.3.1.33

3-30

Page 89

Editing APPN Parameters

Parameter: Implicit User-Deﬁned 3

Default: 128

Range: 0 to 255

Function: Speciﬁes the third user-deﬁned TG characteristic to a dynamic link station

on this port.

Instructions: Enter a value in the range 0 to 255.

MIB Object ID: 1.3.6.1.4.1.18.3.5.14.1.3.1.34

Parameter: HPR Implicit LS Support

Default: Enable

Options: Enable | Disable

Function: Enables HPR for implicit link stations on this port. This parameter is

available when the HPR Support parameter is set to Enable.

Instructions: Click on Values and select Enable or Disable.

MIB Object ID: 1.3.6.1.4.1.18.3.5.14.1.3.1.35

Parameter: HPR Link-Level Error Recovery

Default: Disable

Options: Enable | Disable

Function: Enables or disables HPR Link Level Error Recovery on implicit link

stations on this port. This parameter is available when the HPR Support and the HPR Implicit LS Support parameters are set to Enable.

Instructions: Click on Values and select Enable or Disable.

MIB Object ID: 1.3.6.1.4.1.18.3.5.14.1.3.1.36

3-31

Page 90

Configuring APPN Services

Parameter: Implicit Link Deactivation Time

Default: 120

Range: 5 to 255

Function: Speciﬁes the time (in seconds) before implicit link stations on this port

deactivate if it is an HPR limited resource. This parameter is available when the Implicit Limited Resource is set to Yes, and when the HPR Support and the HPR Implicit LS Support parameters are set to Enable.

Instructions: Enter a value in the range 5 to 255, inclusive.

MIB Object ID: 1.3.6.1.4.1.18.3.5.14.1.3.1.37

Parameter: HPR UI SAP

Default: C8

Options: Any 2-digit hexadecimal value

Function: Speciﬁes the local HPR service access point address for unnumbered

information (UI) frames on this port. A UI frame is an LLC frame type on which LLC does not perform link-level error recovery.This parameter is available when HPR Support is set to Enable.

In base APPN/LLC2 conﬁgurations, LLC2 performs link-level recovery by sending information frames (I-frames). If you disable link-level error recovery with the HPR Link-Level Error Recovery parameter, APPN sends the HPR network layer packets as UI frames, since RTP performs the link-level error recovery on an end-to-end basis.

Instructions: Enter any 2-digit hexadecimal value. The 0x preﬁx is optional. For

example, the value C8 uses the 0x preﬁx.

MIB Object ID: 1.3.6.1.4.1.18.3.5.14.1.3.1.39

3-32

Page 91

Editing APPN Adjacent Link Stations

To edit APPN Adjacent Link Station parameters, begin at the Conﬁguration Manager window (r

1. Select Protocols➔APPN➔Adjacent Link Stations.

efer to Figure 3-1) and

Editing APPN Parameters

The APPN Adjacent Link Station List window appears (F

igure 3-8).

Figure 3-8. APPN Adjacent Link Station List Window

Edit those parameters you want to change.

If the window appears without any adjacent link stations in the list, go to the section “Adding Adjacent Link Stations.”

3-33

Page 92

Configuring APPN Services

Click on Apply to save your changes.

4. Click on Done to exit the window.

To edit the advanced adjacent link station parameters, click on Advanced and go to the section “Editing Advanced Adjacent Link Station Parameters.”

Parameter: Enable/Disable

Default: Enable

Options: Enable | Disable

Function: Enables or disables the adjacent link station highlighted in the APPN

Adjacent Link Station List window. Enable — Initializes the selected adjacent link station. You can also use

the Enable setting to initialize an existing adjacent link station port that you disabled earlier.

Disable — Forces the adjacent link station into the “down” (inoperative) state.

Instructions: Click on Values and select Enable or Disable. Select Disable to disable the

adjacent link station. Select Enable to enable or re-enable the adjacent link station.

MIB Object ID: 1.3.6.1.4.1.18.3.5.14.1.4.1.2

Parameter: Port Name

Default: None

Options: Up to 8 alphanumeric uppercase characters

Function: Speciﬁes the name of the port supporting the adjacent link station.

Instructions: Enter up to 8 alphanumeric uppercase characters with no blank spaces

(leading, trailing, or embedded).

MIB Object ID: 1.3.6.1.4.1.18.3.5.14.1.4.1.4

3-34

Page 93

Editing APPN Parameters

Parameter: Adjacent Node Name

Default: None

Options: Any valid name with up to 17 characters in the format <NETID.NAME>;

NETID is the unique network name with up to 8 characters followed by a period, and NAME is the control point name with up to 8 characters

Function: Identiﬁes the name of the network and the adjacent node name.

Instructions: Type to 8 characters for the network ID name, follow with a period, then

type a control point name with up to 8 characters. You must use uppercase characters only and the ﬁrst character must be non-numeric. Blank spaces (leading, trailing, and embedded) are not allowed in the node name. For example, APPNNODE.CPONE is a valid entry for the Adjacent Node Name parameter.

MIB Object ID: 1.3.6.1.4.1.18.3.5.14.1.4.1.6

3-35

Page 94

Configuring APPN Services

Parameter: Adjacent Node Type

Default: LEARN

Options: LEARN

NN EN BACK LEVEL LEN NODE HOST XID 3 HOST XID 0 DSPU XID DSPU NO XID

Function: Speciﬁes the type of adjacent link station node.

Instructions: Click on Values and select an adjacent node type, as indicated under

Options.

LEARN — APPN automatically learns the type of adjacent link station. NN — Network Node EN — End Node BACK LEVEL LEN NODE — Back-level low-entry networking node. HOST XID 3 — Host node that supports XID3 protocols; includes the

network name control vector.

HOST XID 0—Host node that supports XID0 protocols. DSPU XID — Down stream physical unit (DSPU) node that supports

XID3 protocols, but does not include the network name control vector. DSPU NO XID —Down stream physical unit (DSPU) node that does not

support XID protocols. This selection is valid on nonswitched ports and is invalid on negotiable ports.

MIB Object ID: 1.3.6.1.4.1.18.3.5.14.1.4.1.23

3-36

Page 95

Editing APPN Parameters

Parameter: Enable DLUR Support for this LS

Default: Disable

Options: Enable | Disable

Function: Speciﬁes whether the adjacent link station is a PU2.0 node to be serviced

by DLUR.

Instructions: Click on Values and select Enable or Disable.

MIB Object ID: 1.3.6.1.4.1.18.3.5.14.1.4.1.28

Parameter: Primary DLUS Name

Default: None

Options: Any valid name with up to 17 characters in the format <NETID.NAME>,

NETID is the unique network name with up to 8 characters followed by a period, and NAME is the control point name with up to 8 characters

Function: Speciﬁes the fully qualiﬁed name of the DLUS node that will serve the

PU2.0 link station.

Instructions: Type up to 8 characters for the network ID name; follow with a period,

and then type a control point name with up to 8 characters. You must use uppercase characters only and the ﬁrst character must be non-numeric. Blank spaces (leading, trailing, and embedded) are not allowed in the node name. For example, APPNNODE.DLUR is a valid entry for the Primary DLUS Name parameter.

MIB Object ID: 1.3.6.1.4.1.18.3.5.14.1.4.1.30

Parameter: DSPU Name

Default: None

Options: Up to 8 alphanumeric uppercase characters.

Function: Speciﬁes the name of the down stream physical unit (DSPU) supported by

DLUR.

Instructions: Enter up to 8 alphanumeric uppercase characters with no blank spaces

(leading, trailing, or embedded).

MIB Object ID: 1.3.6.1.4.1.18.3.5.14.1.4.1.29

3-37

Page 96

Configuring APPN Services

Parameter: Adjacent Node Block Number

Default: None

Options: None

Function: A unique hexadecimal value that identiﬁes APPN in this adjacent node.

The number is the ﬁrst 3 digits of the node ID.

Instructions: Accept the derived value that displays in this ﬁeld.

MIB Object ID: 1.3.6.1.4.1.18.3.5.14.1.4.1.10

Parameter: Adjacent Node ID Number

Default: None

Options: Optional; if speciﬁed, a valid string of 5 hexadecimal digits (0 to 9,

A,B,C,D,E,F)

Function: Identiﬁes the local APPN adjacent node and is present in APPN alerts and

exchange identiﬁcations (XIDs). These 5 digits are combined with the 3-digit block number to form a unique XID node identiﬁcation for the adjacent node. The APPN network node and the adjacent node exchange node identiﬁcations when establishing a connection.

Instructions: Enter 5 hexadecimal digits.

MIB Object ID: 1.3.6.1.4.1.18.3.5.14.1.4.1.11

3-38

Page 97

Editing APPN Parameters

Parameter: Link Address (hex)

Default: None

Options: None

Function: Speciﬁes the MAC/SAP, DLCI/SAP (for Frame Relay), or SDLC address

that this adjacent link station will use. This ﬁeld displays the address you speciﬁed when you added the adjacent link station. The MAC address starts with the 0x preﬁx and ends with the SAP value.

Instructions: If you choose to specify a new link data address, specify the MAC address

in MSB noncanonical format with the 0x preﬁx, and end the address with the SAP value. For Frame Relay, specify a valid DLCI and SAP value. For SDLC, specify a valid SDLC address.

MIB Object ID: 1.3.6.1.4.1.18.3.5.14.1.4.1.27

Parameter: Max Send BTU Size

Default: 2057

Range: 256 to 4105

Function: Speciﬁes the maximum Basic Transmission Unit (BTU) size that can be

sent over this TG to an adjacent link station. Each link station determines its own maximum send BTU size based on local node deﬁnitions and exchange identiﬁcation (XID) information received from the interf ace and the adjacent link station.

Instructions: Enter a number in the range 256 to 4105.

MIB Object ID: 1.3.6.1.4.1.18.3.5.14.1.4.1.14

3-39

Page 98

Configuring APPN Services

Parameter: Target Pacing Count

Default: 4

Range: 0 to 32767

Function: Speciﬁes the pacing window size for session requests (BINDs) on this TG

to the adjacent link station. APPN uses this value for ﬁxed BIND pacing. Pacing windows control the number of session requests to prevent memory consumption at the adjacent link station.

Instructions: Enter a value in the range 0 to 32767.

MIB Object ID: 1.3.6.1.4.1.18.3.5.14.1.4.1.13

Parameter: HPR Support for this LS

Default: Disable

Options: Enable | Disable

Function: Enables or disables HPR on this link station. This parameter is available

when the HPR Support parameter is set to Enable.

Instructions: Click on Values and select Enable or Disable.

MIB Object ID: 1.3.6.1.4.1.18.3.5.14.1.4.1.32

Deleting Adjacent Link Stations

To delete an adjacent link station from the APPN Adjacent Link Station List window (r The system software deletes the entry from the APPN conﬁguration.

3-40

efer to Figure 3-8), select the adjacent link station and click on Delete.

Page 99

Adding Adjacent Link Stations

To add an adjacent link station to an APPN interface, display the APPN Adjacent Link Station List window (r

1. Click on Add.

The APPN Adjacent Link Station Port Conﬁguration window appears (F

igure 3-9).

Editing APPN Parameters

efer to Figure 3-8) and then

Figure 3-9. APPN Adjacent Link Station Port Conﬁguration Window

Specify the Port Name parameter, as follows:

Parameter: Port Name

Default: None

Options: Up to 8 alphanumeric uppercase characters

Function: Speciﬁes the name of the port supporting the adjacent link station.

Instructions: Enter up to 8 alphanumeric uppercase characters with no blank spaces

(leading, trailing, or embedded).

MIB Object ID: 1.3.6.1.4.1.18.3.5.14.1.4.1.4

3. Click on OK.

The screen displays the APPN Adjacent Link Station Conﬁguration window speciﬁc to your network (F

igure 3-10).

3-41

Page 100

Configuring APPN Services

Figure 3-10. APPN Adjacent Link Station Conﬁguration Window

Edit the following parameters, using the parameter descriptions for

• Adjacent Link Station Name

• Adjacent Node Name

• Address parameters for the speciﬁc network (MAC, SAP, DLCI, SLDC)

• Enable DLUR Support for this LS

• Primary DLUS Name

• DSPU Name

• Adjacent Node ID Number

• Adjacent Node Block Number

3-42

Avaya APPN User Manual

Specifications and Main Features

Frequently Asked Questions

User Manual

Contents

Figures

Tables

About This Guide