92
ACP Functional Description ACP 10 ACP 50 ACP 70 May 1998 Order Number 2000-900 Document Number 950404-01 Rev E Universal Network Access May 1998

ACP Functional Description Manual.pdf

Embed Size (px)

Citation preview

Page 1: ACP Functional Description Manual.pdf

ACPFunctional Description

����� ����� �����

May 1998Order Number 2000-900

Document Number 950404-01 Rev E

��� ������ ��������� ��

May 1998

Page 2: ACP Functional Description Manual.pdf

Copyright

� TELEMATICS INTERNATIONAL, INC., a member of the ECI Telecom Group, 1998.

All rights reserved. Telematics International, Inc. reserves the right to use or distribute freely anyinformation supplied by readers without incurring obligations.

Any unauthorized use, duplication, or distribution of this document or any part thereof withoutthe prior written consent of Telematics International, Inc. is strictly prohibited.

Printed in the United States of America.

Disclaimer

Telematics International, Inc. reserves the right to improve this document, its contents, and anyproducts described herein at any time without prior notification. The information in thisdocument has been reviewed for accuracy, clarity, and completeness.

Telematics International, Inc. is not responsible for any errors or omissions in this document. Ifyou find any errors or have any comments, please forward them to:

Telematics International, Inc.Information Management & Development Dept.26630 Agoura RoadCalabasas, California 91302–1988U.S.A.

Page 3: ACP Functional Description Manual.pdf

Contents

iiiACP Functional Description, May 1998

Contents

IntroductionACP 10 Platform 3. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . ACP 50 Platform 5. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . ACP 70 Platform 7. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Architecture Highlights 9. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Hardware Characteristics 9. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . ACP System Features 9. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

I/O Connectivity 13. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . ACP 50 Communication Expansion Modules (CEMs) 13. . . . . . . . . . . . . . . . . . ACP 50 Communication Adapter Modules (CAMs) 13. . . . . . . . . . . . . . . . . . . . ACP 70 Optional Modules 14. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . External Interface Converters 14. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . lnternal Interface Converters 14. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Level 1 Support 17. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Interface 17. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Clocking 17. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Speed 17. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Software Architecture 19. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

System Management 21. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Extensive Diagnostic Capabilities 21. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Additional Network Management Options 23. . . . . . . . . . . . . . . . . . . . . . . . . . . .

Automatic Node Protection Switching (ANPS) Support 25. . . . . . . . . . . . Connecting the Nodes 25. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Configuring the Nodes 25. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Failure Scenarios 25. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

X.25 Support 27. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . The Level 2 Frame Interface 27. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . The Level 3 Packet Interface 27. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . General X.25 Features 28. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . X.25 Multipoint Support 31. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

DSP Support 33. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Why Bisync? 33. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . DSP within the X.25 Network 33. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Connection Methods 33. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Monitoring Commands 34. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Trace Functions 34. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Frame Relay Support 35. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . LMI 35. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . DTE and DCE Interfaces 35. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Outbound Congestion Control 36. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Inbound Congestion Control 36. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Page 4: ACP Functional Description Manual.pdf

iv ACP Functional Description, May 1998

Frame Relay Applications 36. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Monitoring Commands 37. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Trace Functions 37. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Asynchronous Support 38. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Device Connectivity Features 38. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Host Connectivity Features 38. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Routing 38. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . X.3 Support 39. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . X.28 Support 40. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . X.29 Support 42. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . X.121 Support 42. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

SNA Support 43. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Why Combine X.25 and SNA? 43. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . ACP TPAD and HPAD Value-added Emulation 43. . . . . . . . . . . . . . . . . . . . . . . Automatic Error Recovery 43. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . PU and LU Switching 43. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3270 SNA Support 44. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3770 SNA Support 44. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5250/5294/5394 SNA Support 44. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Connections to a Host 44. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Enhanced Security 45. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

IP Support 46. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Applications 46. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Standards 48. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Routing Protocols 48. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . ELX Transceivers 48. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Monitoring Commands 48. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . LAN/WAN Interface Connectivity 49. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Statistics 49. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Serial Line Internet Protocol (SLIP) 49. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Point-to-Point (PPP) Protocol 50. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . IP Transporter 50. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . PPP/SLIP/X.25 Gateway 50. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . PAP/CHAP and RADIUS Security 53. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Proxy ARP for IP Addressing 54. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

TPP Support 56. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Why TPP? 56. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . FOP and BOP Protocols 56. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . TPP Module 56. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Connection Methods 57. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Monitoring Commands 57. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Trace Functions 57. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

POS Support 58. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Terminals and Hosts Supported 58. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Connection Types 58. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Programmable Message-Based Switching 58. . . . . . . . . . . . . . . . . . . . . . . . . . . Other Highlights 59. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Example Applications 61. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Page 5: ACP Functional Description Manual.pdf

Contents

vACP Functional Description, May 1998

ISDN BRI Support 63. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . How ISDN Basic Rate Interface (BRI) Works 63. . . . . . . . . . . . . . . . . . . . . . . . . ISDN Specifications 63. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . National ISDN Variations 64. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . ACP ISDN Applications 64. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Internal Modem Support 66. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Modem Sharing 66. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . ACP 50 Internal Modems 66. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Advantages of Internal Modems 66. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Synchronous Dial-out 68. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Asynchronous Dial-out 68. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Dial-in 68. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . ACP Internal Modem Specifications 68. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Functional Characteristics 70. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Personality Module 70. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Nature of Performance Data 70. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Guidelines to Data 70. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Memory, Software, and Hardware Requirements 75. . . . . . . . . . . . . . . . . .

User Responsibilities 77. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . User Setup 77. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Charges, Terms, and Conditions 77. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Comments, Questions, Corrections 77. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Index

Page 6: ACP Functional Description Manual.pdf

vi ACP Functional Description, May 1998

Page 7: ACP Functional Description Manual.pdf

viiACP Functional Description, May 1998

Statement of Corporate Policy & DirectionYear 2000 Millennium Change

POSITION: Telematics International will ensure that all its products conform to theupcoming millennium change. Telematics’ products employ a suite of standard product softwareand, in some cases, software products either custom developed or maintained by Telematics.

PROCESS: We have raised internal awareness by conducting a set of quality checks againstthe products. We have also specified the nature of the necessary tests and have disseminatedthis information to the responsible individuals in all geographic locations that participate inverification activities.

As products pass through their development and maintenance cycles, these specific verificationtests will be conducted to ensure year 1999-to-2000 transition and year 2000 resilience.Required software changes and/or hardware dependencies will be identified and implemented.Similarly, custom software will be verified and modified, if necessary, according to the terms ofspecific customer contracts.

A synopsis of the product tests planned is as follows:

� Output will be year 2000 compliant.

� Products that possess the ability to set clocks will be 2000 compliant.

� Products that need to compute differences between time stamps will be 2000 compliant.

� In products containing a clock, the clock will be able to successfully perform a roll-overfrom December 31, 1999 to January 1, 2000.

� The year 2000 will be treated as a valid leap year.

� Products will function correctly in situations where network components physically residein time zones that span millenniums.

Where Telematics offers third party suppliers’ products as part of our product solution, we willwork with those suppliers to ensure that the time-keeping requirements for the next millenniumare met. Where any other non-Telematics supplied third-party products or customer-generatednon-Telematics software may be interfacing with Telematics products, the customer isresponsible for the year 2000 compliance.

AVAILABILITY: Upon delivery of all newly developed products in 1998, the millenniumrequirement will be already addressed. Upon delivery of revisions (function or maintenance) toexisting products, the millennium issue will be addressed. The goal for all products to bemillennium-compliant is by July 1, 1998.

Customers with products that are either under warranty or are covered under a softwaremaintenance and update contract will receive the millennium-compliant software updates aspart of the normal update process. For others, an upgrade program will be announced.

Page 8: ACP Functional Description Manual.pdf

viii ACP Functional Description, May 1998

Revision HistoryThis Revision History begins with Revision D.

Revision D: Revised certification information; updated ACP data sheet andenvironmental/operational specifications. Updated IP information, including PAP/CHAP andRADIUS server features, plus proxy ARP. Updated POS applications; added asynchronous dial-outmodem application; and added two Voice/Fax Module option information. Added new systemmanagement options and updated Functional Characteristics tables. Added BEST BUY (bestprice) items to ordering forms. Added ACP 50 hex V.28 card and octal modem V.34 card orderinginformation. Moved obsolete product numbers to separate Obsolete section.

Revision E: The following changes were made to the manual:

� Added a Statement of Corporate Policy & Direction for Year 2000 Millennium Changeissues (see page vii).

� Updated ACP 50 product data to include the support of T1/E1 CSU/DSU hardware anddual 48VDC power supplies (see pages 5–6).

� Eliminated all ACP 70 Voice/Fax Option (VFO) information from the manual. (The VFOhas been discontinued.)

� Added information regarding the new T1/E1 CSU/DSU management module that issupported on the ACP 50 by version 4.0 ACP software. (See pages 2 and 20.)

� Added information about Automatic Node Protection Switching (ANPS) — the protectiveswitching feature available to ACP 50 units with 4.0 software. (See page 25.)

� Added descriptions of the available CEMs, CAMs, and optional modules that areavailable for use on the ACP 50 and ACP 70 (see pages 13– 14).

� Updated CEM/CAM table (Table 5) to include V.32 and V.34 modem CEM/CAM modelnumbers and information on the octal DMA III/PS CEM, octal DMA/PS CAM, and T1/E1CSU/DSU CAM (see page 15).

� Added information on new system management options: SNMP Agent, FTP, and TELNETServer (see page 23).

� Updated information regarding supported X.25 packet size (see page 27).

� Added new descriptions/figures of SNMP, FTP, and TELNET to the IP protocol section(see page 46).

� Added information regarding the new OSPF routing capability supported by version 4.0software (see page 48).

� Updated Point of Sale figures and feature descriptions (see pages 58– 61).

� Updated ACP 50 Functional Characteristics Version 1.13 table (Table 15 on page 72) toindicate the correct PU-LU type for SW/AS/SNA/TP/BR software (model number 5Bx9).

� Updated ACP 50 Functional Characteristics Version 2.xx table (Table 16 on page 73) toreflect correct modem async port allowance and to include software p-kit 5P09. Addednew ACP 70 2.xx table (Table 18 on page 74).

� Added new ACP Functional Characteristics Version 4.xx tables (Tables 17 and 19 onpages 73– 74) to show the capabilities of new software versions.

� Updated ACP 50 and 70 Software and Hardware Matrixes (Tables 21 and 22 on page 76)to include Version 4.xx software support information.

� Removed ordering section from this manual. The standard ordering section is nowavailable as a separate document (ACP Order Form – Standard) under model number2002-900 (part number 950493-01).

Page 9: ACP Functional Description Manual.pdf

ACP Functional Description, May 1998 1

Introduction

Telematics ACP (Access Communication Processor)networking products offer a variety of cost-effective ways forusers to access a range of network services. Telematics ACPscan be deployed as customer premises equipment (CPE),central office/concentration equipment within public networks,or as user access and switching equipment within private datanetworks.

Telematics International is also a pioneer in offering highlyreliable, fast products for Point of Sale (POS) transactions as

well as for frame relay, Internet/Intranet, and X.25-basedsystems (see Figure 1).

The ACP platforms available are:ACP10 ACP 50ACP 70

ACP models are available with a variety of protocol andinterface modules to support various access and networkingfunctions.

X.25

INTERNET FRAMERELAY

POS

Universal Network Access

Figure 1. Telematics Product Coverage of Key Network Systems

Designing for the future: Universal Network Access TM

Universal Network Access is designed to offer single-sourceaccess to all user connectivity needs. Universal NetworkAccess offers choice: the ability to choose from a host ofdifferent access protocols and network service options. TheUniversal Network Access platforms include the ACP 10,ACP 50, and ACP 70.

With Universal Network Access, Telematics customers willbe able to connect their remote worksites using any variety ofaccess protocols and network connections.

For access to networks, the ACPs transport a wide range ofprotocols including async, frame relay, X.25, TCP/IP, POS,SNA, BSC, SLIP, and PPP, or, in a “transparent” mode, anybit or byte synchronous protocol.

On the network side, users select the service they require,whether it is basic rate ISDN, frame relay, X.25, IP, PPP, oreven a leased line into a private network.

As user needs change, they are able to change access protocols,network services or both without having to buy another accessdevice. All network service and access protocol changes areavailable from the network manager software.

The flexibility of Universal Network Access allows users tosend LAN data across an IP connection at the same time thatthey are sending async or SNA across X.25. UniversalNetwork Access products combine the functionality of a PAD,FRAD, switch, router concentrator, multiplexer and ISDNterminal adapter, within a single device.

Page 10: ACP Functional Description Manual.pdf

ACP Functional Description, May 19982

■ The Automatic Node Protection Switching (ANPS) mod-ule provides automatic backup of an entire node. This isdone automatically and the network manager is informed ofa failure through an SNMP trap. Async connections areaccomplished by using “Y” cables.

■ The Asynchronous module allows the attachment of asyncstart-stop terminals, host computers, and PCs. In support ofan asynchronous PAD function, it provides data traffic con-centration from a number of async devices to the X.25 net-working module. It implements all the packetassembly/disassembly functions and end-to-end controlsand procedures specified in CCITT recommendations X.3,X.28, X.29, and X.121.

■ The X.25 module provides interconnection and call routingbetween X.25-compliant equipment, such as PADs, X.25host computers, gateways, routers, or other switches withinthe network. Standard functions include packet data switch-ing, concentration, routing, error recovery, and networkflow control. It supports the CCITT X.25 recommendationallowing the connection of different types of X.25 equip-ment and networks.

■ The Frame Relay module provides the interconnectionand routing between all frame relay-compliant equipmentwithin the network, such as FRADs, frame relay host com-puters, routers, and gateways. This module supports theLMI ANSI, ITU, and GO4 (Group of 4) recommendation,allowing connection to different types of frame relay net-works and equipment.

■ The SNA module allows the attachment of SNA/SDLCcluster controllers and host computers to either private orpublic data networks. It provides conversion from SNA toX.25, and vice versa, and can operate in either standardIBM� QLLC protocol mode, compatible with NCP/NPSIsoftware, or in VLU (Virtual Logical Unit) mode. VLUmode allows 3270/5250 devices to operate in a multi-hostenvironment. Host support includes the IBM system 370,S/3x, and AS/400.

■ The DSP module allows the attachment of 3270 BSCEBCDIC controllers. It provides protocol conversion from3270 BSC to X.25 using the de facto DSP packet level pro-tocol. DSP implementation allows 3270 displays and print-er devices to operate in a multi-host environment.

■ The IP module allows the interconnection of EthernetLANs over X.25, frame relay, or IP networks for remoteaccess to LAN services such as E-mail, file transfers, andTELNET sessions. The IP module accomplishes this byfragmenting the Ethernet TCP/IP datagrams into smaller

packets or frames for routing over the network. The IP im-plementation also supports asynchronous SLIP (serial lineIP) and synchronous/asynchronous PPP (point-to-pointprotocol) users over directly connected asynchronous linesor via the PSTN through the internal modem card.

The IP implementation may also include the PPP/SLIP/X.25 gateway for specific personality kits. PPP users havesecurity available through PAP/CHAP and RADIUSservers. Proxy ARP for IP addressing may be used with IP,SLIP, and PPP serial ports.

■ The TPP module transports synchronous byte- and frame-oriented protocol data within an X.25 packet. The TPP im-plementation provides a pass-through function for othersynchronous traffic alongside the SNA, async, X.25, and3270 DSP traffic supported by the specific ACP commu-nication modules.

■ The ISDN (Integrated Services Digital Network) BRI(Basic Rate Interface) module provides the 2B+D ”S/T”interface with 2B (bearer) channels and one D (data) chan-nel. The ISDN implementation supports X.25 packetswitching over the B channels (and D channel in the fu-ture), and supports both incoming and outgoing circuits.

■ The Modem module supports the internal software-drivenmodems. It offers support for a range of modem standards,including V.32bis as well as V.42bis data compression. Theinternal modems support a range of dial-up services includ-ing async, X.25, SLIP, and PPP.

■ The POS module allows the attachment of POS terminalsand host computers to either private or public data net-works. POS supports ISO 8583, VISAI, VISAII, APACS,SPDH, and TINET protocols. POS features include “fastconnect” modems and local protocol spoofing which bothhelp reduce overall transaction response time.

■ The internal T1/E1 CSU/DSU module provides direct con-nection to T1 or E1 services. This eliminates the need topurchase an external CSU/DSU (Channel Service Unit/Data Service Unit). The CSU/DSU is a dual-port deviceand is fully manageable by using the ACP System Manager(SYM) software module. The interface for T1 is a 100 ohmRJ45 connector. The interface for E1 is a 120 ohm RJ45connector. There are three LED indications per port to indi-cate “on line,” “yellow alarm,” and “red/blue” alarm or lossof frame.

ACP products can run certain combinations of the abovemodules concurrently enabling maximum access andnetworking functionality.

Page 11: ACP Functional Description Manual.pdf

ACP Functional Description, May 1998 3

ACP 10 Platform

Highlights

■ Based on Intel 80C188 10 MHz CPU.

■ 6 multi-protocol ports.

■ 1 DMA-driven port at 64 kbps.

■ EPROM- or Flash memory-based operating codecartridges (“personality modules”).

■ 128 KB RAM expandable to 256 KB.

■ Supports X.25, async, SNA, DSP, TPP, and framerelay.

■ Local and remote diagnostics.

■ Centralized management via INF, SmartView, andOMS.

■ Optional V.11 or V.35 external adapters.

■ 110/220V switch-selectable power supply.

■ 75,000 hours – Calculated MTBF (basic unit).

ACP 10 Front Panel

Back Panel with AC Power Supply

Back Panel with DC Power Supply

The ACP 10 is a low-end, self-contained Access Communica-tion Processor that offers the same access and networkingfeatures as the other ACP platforms described in the pages thatfollow.

The base unit houses a personality module, six universalcommunication ports, and non-volatile memory for configura-tion parameters. The ACP 10 is an ideal choice for sites withonly a few devices requiring access to the core network.

The ACP 10 personality module is available in two versions: alow-cost EPROM module, which contains the ACP 10operating code, or a more flexible, flash-based module that is

also able to receive operating code non-intrusively over thenetwork.

Combinations of access protocols are available for eitherpersonality module in code sets (Type 2, Type 3, etc.). Aprotocol enable key on the personality module determines theavailability of access protocols, and an optional memoryenable key expands the memory by 128 Kbytes.

The ACP 10 has six V.24 ports, three of which provide aregulated power feed for a specially designed, optional V.11and V.35 external converter. It is also available with a choice ofpower supplies: 110/220 VAC or 48 VDC.

Page 12: ACP Functional Description Manual.pdf

ACP Functional Description, May 19984

ACP 10 Base Unit, Personality Module, and V.11/V.35 Converter Kit.

EPROM-based Module (Extended)

V.11 or V.35Converter Kit

IEC Power LineConnector or

Base Unit

110V/220V���!���������!�

DDB15–SCable Connectors

PersonalityModule

Flash-based Module

110/220 VAC

48 VDC Terminal Block

OperationalProcessor Type 80C188 10 MHz CPU

Code Storage in bytesRAM in bytes

512K PROM or Flash128K to 256K

Options V.11 /V.35 external adapters48VDC power supply

Protocols Supported X.25, async, SNA, DSP, TPP, andframe relay

ElectricalAC Power

FrequencyPower Dissipation

100V to 130V1.4 Amp max.50/60 Hz ± 2%< 40 BTU/hr

198V to 264V1.3 Amp max.50/60 Hz ± 2%< 40 BTU/hr

DC PowerCurrentFrequencyPower Dissipation

–40 to –58 VDC0.3 Amp DCN\A< 40 BTU/hr

EnvironmentalOperating Temp.

Storage Temp.

Shipping Temp.

&��%!�%��� � ����%!�%��� �����%!�%��� ����!�#� �"����!$

���%!�%���� � ����%!�%��� ������%!�%��� ����!�#� �"����!$

���%!�% �� � ����%!�%���� ������%!�%��� ����!�#� �"����!$

PhysicalHeightWidthDepthWeight (fully configured)

72 mm (2.9” )295 mm (11.5” )235 mm (9.1” )4.5 kg (9.5 lbs)

Safety

UL 478/4 and CSA 22.2 No. 220, or UL 1950 and CSA 22.2 No. 950,respectively, where applicable.IEC 950: 1991EN 60950: 1992EN 41003: 1993

Emissions

EN 55022: 1994, Class AFCC Part 15, Class A

Export Classification

All Telematics products are classified by the U.S. Department ofCommerce Export Administration under Export Commodity ControlNumber (ECCN) 1567A. Any export of these products outside theUnited States requires prior approval from the U.S. Department ofCommerce or another applicable agency of the U.S. Government.

Headquarters

Corporate Headquarters Central European HeadquartersECI Telecom-Telematics ECI Telecom GMBH1201 W. Cypress Creek Road Buropark OberurselFt. Lauderdale, FL 33309 In der Au 27(954) 772-3070 61440 Oberursel, Germany(800) 833-4580 011-49-6171-6209-0FAX (954) 351-4405 FAX 011-49-6171-5405-7

Asian Headquarters Western European HeadquartersECI Telecom (HK), Ltd. ECI Telecom, Ltd.2806 China Resources Bldg. Isis House26 Harbour Road Reading Road, ChinehamWanchai, Hong Kong Basingstoke, Hampshire011-852-2824-4128 RG24 8TW, United KingdomFAX 011-852-2802-4411 011-44-1–256-388-000

FAX 011-44-1-256-388-143

Page 13: ACP Functional Description Manual.pdf

ACP Functional Description, May 1998 5

ACP 50 Platform

Highlights

■ Based on Intel 80486 50 MHz CPU.

■ Supports up to 24 internal V.32bis or V.34 modems.

■ Configurable with up to 48 async ports.

■ Configurable with up to 26 sync ports which may include 2 sync portsat 2Mbps.

■ Configurable with up to 1 Ethernet port.

■ Disk- or PCMCIA-based software upgrades via a network connection.

■ Scaleable using communication expansion modules (CEMs).

■ Modular, easy field upgrades & serviceability.

■ Supports X.25, async, SNA, DSP, POS, TPP, frame relay, IP routing,ISDN, TELNET Client, TELNET Server, FTP server, SNMP, andOSPF.

■ Local and remote diagnostics.

■ Centralized management via INF, SmartView, OMS, or other SNMPmanagers.

■ 92,000 hours – Calculated MTBF (basic unit and components).

■ 100V–264V auto ranging power supply.

■ 27, 48, or dual 48 VDC power supplies.

■ Optional internal T1/E1 CSU/DSU.

■ Redundancy option available when using the ANPS feature of Version4.0 software (together with required hardware).

32-port, 10-link Back Panel

ACP 50 Front Panel

with ELX Port

Stretch Chassis Back Panelwith Three Modem Cards

The ACP 50 provides an open platform with the highestprice/performance ratio of all the ACP products. Its demon-strated success in the market is a result of expanding thecharacter/packet processing power and the number of highspeed links that can be supported in a single ACP node.

The ACP 50 uses the same field-proven software modules asthe other ACP platforms.

The ACP 50 base unit includes the following Field ReplaceableUnits (FRUs) housed in a forced-air cooled metal chassis withan expansion backplane for CEM/CAM FRUs (see figure onnext page):

■ AC Power and Disk Module.

■ Optional 27, 48, or dual 48 VDC Power and Disk Modules.

■ 3.5-inch disk drive (high density).

■ “Personality module” printed circuit board without enablekeys.

■ 486/50 MHz CPU with up to 32 MB of memory and ahigh-performance, 32-bit microprocessor.

The 486 CPU disk controller allows the ACP 50 to support upto 1.44 MB formatted address space on the 3.5-inch disk drive,allowing concurrent execution of an extended set of access andnetworking protocols.

The ACP 50 uses an integrated 50 MHz 486 CPU (25 MHzdouble clock), supporting the following types of high-perfor-mance CEMs:

■ Octal DMA CEM with 8 DMA-assisted universal ports.

■ Octal modem CEM with 8 DMA-assisted universal ports.

■ Hex CEM with 16 async ports.

■ ELX CEM with 2 VHSL links and one 10Base5 Ethernetport, with optional PCMCIA card. (The ELX CEM canconnect to either an ELX or T1/E1 CSU/DSU CAM.)

■ ISDN Basic Rate Interface CEM with 1 VHSL link and 2ISDN S0 RJ45-type 8-way plug interfaces (for Version 1.xxsoftware only).

A fully-populated chassis can support two VHSL links plus upto 24 high-speed universal ports or 48 async ports.

Page 14: ACP Functional Description Manual.pdf

ACP Functional Description, May 19986

ACP 50 FRUs

Communication ExpansionModule (CEM)

ChassisDB-25 CableConnectors

Power and Disk Module

RearPanel

Adapter Module (CAM)ELX/Communication

Backplane

ACP 50/486 Motherboard

ELX/VHSL,BRI/VHSL, or

BRI/VHSL CEMELX/VHSL or

T1/E1 CSU/DSU CAM

Operational Processor Type 80486 at 50 MHz

Code Storage in bytesRAM in bytes

1.44 MB (disk)4 MB

OptionsHex , Octal DMA, ELX, Octal Modem, & ISDN Basic Rate Interface cards; internal T1/E1 CSU/DSUV.11 /V.35 external adapters;27, 48, or dual 48 VDC power supplies

Protocols Supported X.25, async, SNA, DSP, TPP, framerelay, IP, ISDN Basic Rate Interface,PPP, POS, and IP

ElectricalAC Power

FrequencyPower Dissipation

100V to 130V, 2.5 Amp maximum198V to 264V, 1.6 Amp maximum50 Hz/60 Hz ± 2%< 300 BTU/hr

EnvironmentalOperating Temp.

Storage Temp.

Shipping Temp.

��������� � ����������� ������������ �������� ��������

���������� � ����������� ������������� �������� ��������

������� �� � ������������ ������������� �������� ��������

PhysicalHeightWidthDepthWeight (fully configured)

215.9 mm (8.5” )431.8 mm (17” )355.5mm (14” )15.4 kg (34 lbs)

Safety

UL 478/4 and CSA 22.2 No. 220, or UL 1950 and CSA 22.2 No. 950,respectively, where applicable.IEC 950: 1991EN 60950: 1992EN 41003: 1993

Emissions

EN 55022: 1994, Class AFCC Part 15, Class AFCC Part 68 (approved for all components requiring certification).

Export Classification

All Telematics products are classified by the U.S. Department ofCommerce Export Administration under Export Commodity ControlNumber (ECCN) 1567A. Any export of these products outside theUnited States requires prior approval from the U.S. Department ofCommerce or another applicable agency of the U.S. Government.

Headquarters

Corporate Headquarters Central European HeadquartersECI Telecom-Telematics ECI Telecom GMBH1201 W. Cypress Creek Road Buropark OberurselFt. Lauderdale, FL 33309 In der Au 27(954) 772-3070 61440 Oberursel, Germany(800) 833-4580 011-49-6171-6209-0FAX (954) 351-4405 FAX 011-49-6171-5405-7

Asian Headquarters Western European HeadquartersECI Telecom (HK), Ltd. ECI Telecom, Ltd.2806 China Resources Bldg. Isis House26 Harbour Road Reading Road, ChinehamWanchai, Hong Kong Basingstoke, Hampshire011-852-2824-4128 RG24 8TW, United KingdomFAX 011-852-2802-4411 011-44-1–256-388-000

FAX 011-44-1-256-388-143

Page 15: ACP Functional Description Manual.pdf

ACP Functional Description, May 1998 7

ACP 70 Platform

ACP 70 Front Panel

Back Panel with two Quad CCMs

Back Panel with four ISDN BRI Port Modules

Highlights

■ Based on Intel 80486 25 MHz CPU.

■ Integrated Ethernet AUI port.

■ Up to 14 universal sync/async ports at 64kbps andup to 2 ports at 2 Mbps.

■ PCMCIA-based for software configuration upgradesvia network.

■ Scaleable by using optional modules (Quad CCM orISDN BRI port modules).

■ Supports up to 4 ISDN S0 interfaces.

■ Supports X.25, async, SNA, DSP, POS, TPP, framerelay, IP routing, ISDN, TELNET client, TELNETserver, FTP server, SNMP, and OSPF.

■ Local and remote diagnostics.

■ Centralized management via INF, SmartView, OMS,or other SNMP managers.

■ 77,000 hours – Calculated MTBF (basic unit).

■ 100V–250V auto ranging power supply.

The ACP 70 provides the greatest flexibility to support a rangeof access protocols and network services. The ACP 70 comeswith integral Ethernet and high speed synchronous capabilitiesand supports expansion for additional universal ports. The ACP70 uses the same field-proven software as the other ACPplatforms.

The base unit of each ACP 70 includes the following FieldReplaceable Units (FRUs) housed in a forced-air cooled metalchassis:

■ AC Power Module, 110/220V: provides regulated powerfor all logic, and can sustain power interruption of at leasttwo AC cycles.

■ Optional 48VDC Power Module.

■ Quad Combined Communication Module (CCM) support-ing 4 V.24 universal (synchronous/asynchronous) ports atspeeds up to 64 kbps which provide a regulated power feedfor specially designed, optional V.11 and V.35 external con-verters.

■ Single ISDN BRI port module supporting 2B+D channels.

■ Memory modules (SIMMs).

■ CPU motherboard with 4 MB memory, a high-performance32-bit microprocessor, ROM and RAM memory, a 2-busI/O interface, and the following items:

� Four universal (sync/async) V.24 ports with speeds upto 64 kbps, which provide a regulated power feed forspecially designed, optional V.11 and V.35 externalconverters.

� One embedded Ethernet Access Unit Interface (AUI).

� Two VHSL ports supporting a pair of V.series (V.11,V.24, or V.35) interface modules, with a maximumspeed of two ports at 512 kbps, for X.25 or frame relayconnections.

■ “Personality keys” on the motherboard.

■ 2 MB PCMCIA enables additional software storage.

The optional Quad CCMs and ISDN BRI port modules plugdirectly into the ACP 70 motherboard (see figure on nextpage). A screwdriver is all that is required to install thesemodules as upgrades.

Page 16: ACP Functional Description Manual.pdf

ACP Functional Description, May 19988

ACP 70 FRUs

Enable Keys

Memory Modules (SIMMs)

PCMCIA (optional memory for software storage)

Power Module Quad CCMs

OperationalProcessor Type 80486 at 25MHz

Code Storage in bytes

RAM in bytes

2.0 MB Flash (plus optional 2 MB PCMCIA)4 MB

Options Quad V.24, ISDN, and Voice/FaxmodulesV.11 /V.35 external adapters48VDC power supply

Protocols Supported X.25, async, SNA, DSP, TPP, framerelay, IP, ISDN Basic Rate Interface,PPP, and IP

ElectricalAC Power

FrequencyPower Dissipation

100V to 250V0.60 Amp to 0.25 Amp50/60 Hz ± 2%< 222 BTU/hr

EnvironmentalOperating Temp.

Storage Temp.

Shipping Temp.

5� to 45� C (41� to 113� F),20% to 80% Relative Humidity

–20� to 51� C (–4� to 125� F),10% to 95% Relative Humidity

–20� to 60� C (–4� to 140� F),10% to 95% Relative Humidity

PhysicalHeightWidthDepthWeight (fully configured)

86.8 mm(3.4” )415 mm(16.3” )325 mm(12.8” )6 kg (13 lbs)

Safety

UL 478/4 and CSA 22.2 No. 220, or UL 1950 and CSA 22.2 No. 950,respectively, where applicable.IEC 950: 1991EN 60950: 1992EN 41003: 1993

Emissions

EN 55022: 1994, Class AFCC Part 15, Class A

NOTE: Most equipment configurations meet the limits of EN55022 and FCC for Class B digital devices.

Export Classification

All Telematics products are classified by the U.S. Department ofCommerce Export Administration under Export Commodity ControlNumber (ECCN) 1567A. Any export of these products outside theUnited States requires prior approval from the U.S. Department ofCommerce or another applicable agency of the U.S. Government.

Headquarters

Corporate Headquarters Central European HeadquartersECI Telecom-Telematics ECI Telecom GMBH1201 W. Cypress Creek Road Buropark OberurselFt. Lauderdale, FL 33309 In der Au 27(954) 772-3070 61440 Oberursel, Germany(800) 833-4580 011-49-6171-6209-0FAX (954) 351-4405 FAX 011-49-6171-5405-7

Asian Headquarters Western European HeadquartersECI Telecom (HK), Ltd. ECI Telecom, Ltd.2806 China Resources Bldg. Isis House26 Harbour Road Reading Road, ChinehamWanchai, Hong Kong Basingstoke, Hampshire011-852-2824-4128 RG24 8TW, United KingdomFAX 011-852-2802-4411 011-44-1–256-388-000

FAX 011-44-1-256-388-143

Page 17: ACP Functional Description Manual.pdf

ACP Functional Description, May 1998 9

Architecture Highlights

Hardware Characteristics

The three Access Communication Processor platforms offer awide range of hardware features. The ACP platforms are basedon the 188 and 486 microprocessor series. The ACP platformssupport up to:

■ Two 2 Mbps DMA-assisted ports (ACP 70).

■ 24 64 kbps DMA-assisted ports, plus one at 2 MB and oneat 384 kbps (ACP 50).

■ 48 19.2 kbps async ports (ACP 50).

■ 24 115.2 kbps async ports (ACP 50).

■ One 10 Mbps 10BASE5 Ethernet LAN port (ACP 50/ACP70).

■ 4 ISDN BRI S0 ports (ACP 70).

■ 24 V.32bis integral modem ports (ACP 50).

■ 24 V.34 integral modem ports (ACP 50).

■ Non-volatile storage for the operating code and configura-tion database: the 3.5-inch diskette, flash personality mod-ule, or PCMCIA module allow the distribution of operatingcode via the network.

■ Electrical interfaces: RJ11 (ISDN), RJ45 (async), DDB15(sync/async), DB25 (sync/async), and AUI (Ethernet).

■ Physical interfaces: RS530, V.24, V.35, V.11.

■ Field Replaceable Unit-based construction for easy fieldupgrades, wiring, and maintenance.

■ Extensive diagnostic tests to isolate faulty Field Replace-able Units or interconnection problems.

■ Choice of AC or DC power supplies.

ACP System Features

System operation for the ACP platforms is protected by awatchdog timer. This timer protects against lock-ups (causedby program or memory failure) that generate a general systemreset, resulting in an unconditional system restart. These andother restart-causing events, e.g., power failures, are reportedto the Network Management System.

The ACP 10 uses ROM or flash for both start-up and operatingsoftware. It uses RAM for dynamic memory functions, i.e.,stack, data buffers, variable storage, and interrupt vectors.Configuration parameters are stored in battery-backed RAM.The ACP 70 uses ROM for start-up, and flash for operatingsoftware.

In the ACP 50, the boot ROM contains initial hardware start-updiagnostics for all CPU-board logic circuitry. It also containsan IPL program for loading I/O CEM-related diagnostics fromthe system diskette to RAM. Once all diagnostic tests havebeen performed successfully, the operating code andconfiguration on the system diskette are executed.

The ACP 50 and ACP 70 use byte-parity protected RAM fordynamic memory functions, i.e., stack, data buffers, variablestorage, and interrupt vectors.

Refer to Table 1 for a summary of system characteristics, Table2 for certification status, Table 3 for MTBF reliability figures,and Table 4 for physical and environmental specifications.

Table 1. Systems Characteristics

��� �� ��� �� ��� ��

Processor Type ����� ����� �����

Processor Speed � ��, � ��, ��,

Non-volatile Storage — in bytes�� �����

� ���� � �#�(

���� ��!("� ��� �#�(

RAM — in bytes(basic-extended) �� � � ��� � ��� �

Number of chassis I/O Slots - �

First Field Deployment ��%)�'+ ��� �)#+ ��� �&*�$��' ���

Page 18: ACP Functional Description Manual.pdf

ACP Functional Description, May 199810

Table 2. Safety and Emissions Certifications

������������� 1 � �� � ��

�� �

� �� � ��

�� �

� ��

�� �

� �� � ��

�� �

Safety:UL 2

CSA 2

IEC 950: 1991EN 60950: 1992EN 41003: 1993

–�

–7

7

7

––�

Emissions:EN 55022: 1994 3

FCC Part 15 3

FCC Part 68 4

n/a

n/a

n/a

n/a

Network Certification:Pan-European (”CE”mark) approvedOther international approvals held 5

� � � � � � �

Immunity:EN50082–1: 1992EN50082–1: 1997

� � �

� � �

Internal Modems (PSTN, leased line): 6

USAUnited Kingdom (BABT SITS 8201D)

n/an/a

������

������

������

NOTES: 1. The ACP products are marked in conformity with the following European Commission Directives:The Low Voltage Directive (LVD), 73/23/EECThe Electromagnetic Compatibility Directive (EMC), 89/336/EECThe Telecommunications Terminal Equipment Directive (TTE), 91/263/EECThe Conformité Européene Marking Directive (CE Marking), 93/68/EEC

2. UL 478/4 and CSA 22.2 No. 220, or UL 1950 and CSA 22.2 No. 950, respectively, where applicable.3. Class A for ACP 10, ACP 50, and ACP 70 models. (Note that for the ACP 70, most equipment configurations

meet the limits of EN55022 and FCC for Class B digital devices.)4. Approved for all components requiring certification.5. For specific country approvals, consult your Telematics sales representative or the Telematics International

Approvals Group.6. Internal octal modems are certified as complete assemblies only.7. Certification performed on Request for Price Quotation basis, if required.

Page 19: ACP Functional Description Manual.pdf

ACP Functional Description, May 1998 11

Table 3. Estimated Mean Time Between Failure (MTBF) Figures (in thousands of hours)

Component ACP 10 ACP 50 ACP 70

ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ

MTBF for Basic Unit / Basic Unit 48 VDC 75.2 / 106.4 ÁÁÁÁÁÁÁÁÁÁÁÁÁÁ

7474.2 / 165.0 76.8

ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ

MTBF for Power Module (AC / DC) ÁÁÁÁÁÁÁÁÁÁÁÁÁÁ

115.3 / 115.9 ÁÁÁÁÁÁÁÁÁÁÁÁÁÁ

1632.7 / 244.8

ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ

MTBF for Personality Module / Extended 1208.2 / 2437.8 1805.1

MTBF for CPU 161.7 135.0

ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ

MTBF for Octal DMA CAM / DMA II CEM ÁÁÁÁÁÁÁÁÁÁÁÁÁÁ

1756.5 / 214.5

ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ

MTBF for Hex CAM / CEM ÁÁÁÁÁÁÁÁÁÁÁÁÁÁ

2162.2 / 302.0ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ

MTBF for ELX CAM / CEMÁÁÁÁÁÁÁÁÁÁÁÁÁÁ

568.9 / 239.0ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ

MTBF for T1/E1 CSU/DSU CAMÁÁÁÁÁÁÁÁÁÁÁÁÁÁ

454.5ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ

MTBF for BRI CAM / CEMÁÁÁÁÁÁÁÁÁÁÁÁÁÁ

502.6 / 256.0ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁMTBF for Octal Modem CEM

ÁÁÁÁÁÁÁÁÁÁÁÁÁÁ179.1ÁÁÁÁÁÁÁÁÁÁÁÁÁÁ

ÁÁÁÁÁÁÁÁÁÁÁÁÁÁMTBF for Quad I/O Module 457.0ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ

MTBF for Fan Assembly 200.0

ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ

Mean Time to Repair 20 min. ÁÁÁÁÁÁÁÁÁÁÁÁÁÁ

15 min. 45 min.

NOTE: MTBF figures for CAMs and CEMs are for CAMs and CEMs individually. Do not attempt to combine thesefigures in any form to calculate combined CAM/CEM figures. Such combination figures are highly dependenton system configuration and should be obtained through your Telematics representative.

Page 20: ACP Functional Description Manual.pdf

AC

P F

unctional Description, M

ay 1998 12 Table 4. Physical and Environmental Specifications

Description ACP 10 w/48VDC ACP 10 w/48VDC ACP 50 Stretch

PhysicalHeightWidthDepthWeight (fully config.)

72 mm (2.9” )295 mm (11.5” )235 mm (9.1” )4.5 kg (9.5 lbs)

72 mm (2.9” )295 mm (11.5” )235 mm (9.1” )4.5 kg (9.5 lbs)

215.9 mm (8.5” ) 431.8 mm (17” ) 355.5 mm (14” ) 15.4 kg (34 lbs)

ElectricalAC Rating

FrequencyPower Dissipation

100V to 130V, 1.4 Amp maximum198V to 264V, 1.3 Amp maximum50 Hz/60 Hz ± 2%< 40 BTU/hr

DC Power: -40 to -58 VDCCurrent: 0.3 Amp DCN/A< 40 BTU/hr

100V to 130V, 2.5 Amp maximum198V to 264V, 1.6 Amp maximum50 Hz/60 Hz ± 2%< 300 BTU/hr

Environmental *Operating Temp. ***

Storage Temp.

Shipping Temp.

���������� ��������������������� �������� ��������

����������� ������������������������ �������� ��������

������� ��� ������������������������� �������� ��������

���������� ��������������������� �������� ��������

����������� ������������������������ �������� ��������

������� ��� ������������������������� �������� ��������

���������� ����������������������� �������� ��������

����������� ������������������������ �������� ��������

������� ��� ������������������������� �������� ��������

Table 4. Physical and Environmental Specifications (continued)

Description ACP 50 w/27VDC ACP 50 w/48VDC ACP 70 ACP 70 w/48VDC

PhysicalHeightWidthDepthWeight (fully config.)

215.9 mm (8.5” )431.8 mm (17” )355.5 mm (14” )15.4 kg (34 lbs)

215.9 mm (8.5” )431.8 mm (17” )355.5 mm (14” )15.4 kg (34 lbs)

86.8 mm (3.4” )415 mm (16.3” )325 mm (12.8” )6 kg (13 lbs)

86.8 mm (3.4” )415 mm (16.3” )325 mm (12.8” )6 kg (13 lbs)

ElectricalAC Rating

FrequencyPower Dissipation

DC Power: 19 to 30 VDCCurrent: 6 Amp DCN/A< 300 BTU/hr

DC Power: -42 to -57 VDCCurrent: 3 Amp DCN/A< 300 BTU/hr

AC Power: 100V to 250VCurrent: 0.60 Amp to 0.25 Amp50/60 Hz ± 2%< 222 BTU/hr

DC Power: -40 to -70 VDCCurrent: 1.4 Amp maximumN/A< 222 BTU/hr

Environmental*Operating Temp. ***

Storage Temp.

Shipping Temp.

���������� ����������������������� �������� ��������

����������� ������������������������ �������� ��������

������� ��� ������������������������� �������� ��������

���������� ����������������������� �������� ��������

����������� ������������������������ �������� ��������

������� ��� ������������������������� �������� ��������

���������� ����������������������� �������� ��������

����������� ������������������������ �������� ��������

������� ��� ������������������������� �������� ��������

���������� ����������������������� �������� ��������

����������� ������������������������ �������� ��������

������� ��� ������������������������� �������� ��������

* Temperature ranges may be further limited by the type of diskette media used. *** Humidity must be noncondensing.

Page 21: ACP Functional Description Manual.pdf

ACP Functional Description, May 1998 13

I/O Connectivity

The ACP 10 I/O logic is fully-integrated in the base unit,while the ACP 50 allows greater port expansion with a varietyof Communication Expansion Modules (CEMs) andCommunication Adapter Modules (CAMs). The ACP 70contains both fully-integrated I/O logic and expansioncapabilities. Several different optional modules provide theACP 70 with various interface options.

ACP 50 Communication ExpansionModules (CEMs)

Communication Expansion Modules (CEMs) are printedcircuit boards that contain the logic circuitry required for I/Ooperation in the ACP 50. The ACP 50 CEMs, work inconjunction with separate CAMs to allow additional interfaceflexibility to the outside world.

The following types of CEMs are supported by the ACP 50:

� Hex CEM. Provides 16 asynchronous ports that run upto 19.2 kbps. The hex CEM connects to either a V.24 orV.28 hex CAM. The ACP 50 can contain up to three hexCEMs.

� Octal DMA I/II/III CEM. Provides eight DMA-assisteduniversal ports, supporting synchronous speeds up to 64kbps and asynchronous speeds up to 115.2 kbps. A specialversion of octal DMA—the octal DMA III/PS CEM—alsosupports the Automatic Node Protection Switching(ANPS) feature of ACP Version 4.0 software. The ACP 50can contain up to three octal DMA CEMs.

� Octal Modem CEM. Two different version of this CEMare available: V.32 or V.34. Both CEMs contain modemmodule SIMMs to support analog transmission, and eightDMA-assisted synchronous/asynchronous ports. The ACP50 (stretch chassis) can contain up to three octal modemCEMs, supporting up to 24 internal modems.

� ELX/ELX II CEM. The ELX CEM is a daughterboardthat installs directly on the ACP’s main CPU (since itinstalls in the same location as the BRI CEM, only one ofthese CEMs may be used in an ACP). The ELX providesone Ethernet port that is compatible with the IEEE 802.3interface specification for 10Base5 Ethernet LANs. TheELX CEM also provides two VHSL ports that may run atspeeds up to 2 Mbps. The ELX II version of the CEM alsoholds the ACP’s PCMCIA card.

� �� ���� The ISDN BRI CEM is a daughterboard thatinstalls directly on the ACP’s main CPU (since it installs inthe same location as the ELX CEM, only one of theseCEMs may be used in an ACP.) The BRI CEM providestwo S0 interface ports for BRI bearer services, and oneVHSL ports, supporting speeds up to 384 kbps. The VHSLport may have either an RS-530, V.24, or V.35 interface,

determined by the installation of interface modulesinstalled on the BRI CAM. (ISDN BRI operation issupported only by Version 1.xx software.)

Refer to Table 5 on page 15 for additional informationregarding ACP 50 CEMs.

ACP 50 Communication Adapter Modules(CAMs)

The ACP 50 platform uses Communication Adapter Modules(CAMs) to connect external communication cables. Thisapproach allows the ACP to meet different physical/electricalinterface requirements, i.e., DTE or DCE, V.11, V.24, V.35,etc. The CAMs are located behind the backplane and connectdirectly to their corresponding CEMs (see Figure 2).

Communication Expansion Module

ACP 50Backplane

CommunicationAdapter Module

Figure 2. ACP 50 CEM-Backplane-CAM Assembly

The CAMs contain the connectors seen on the rear of theACPs, and depending upon the CAM installed, house differenttypes of connectors with either a DCE or DTE physicalappearance to the attaching device.

Regardless of the DCE or DTE appearance, the actualconnectors are standard RJ11/RS-530, RJ45, and DB25-S“female” connectors. The appearance is selected via the CAMor cable, depending on the connector type. (Refer to Table 5for further information on CAMs and CEMs.)

��� ������� ��� ���� �� CAMs are for connectingACPs to terminals, host computer ports, modems, etc. Forinterfaces, cables should only use the wire pin-outs defined forthat specific interface (V.11, V.11/RS530, V.24, V.35, RJ11,RJ45 types). Cables must be shielded to comply with emissionstandards and must be manufactured using UL and CSAapproved materials.

NOTE: Special DB25-to-Winchester adapter cables areavailable for interfacing to V.35 modems. TheWinchester connector uses 6-32 jack screws. AllACP DB25/DDB15 connectors and cables use 4-40jack screws.

Page 22: ACP Functional Description Manual.pdf

ACP Functional Description, May 1998 14

The following types of CAMs are supported by the ACP 50:

� Hex CAM. The hex CAM is available in both V.24 andV.28 models, each providing 16 asynchronous ports. Thehex CAM is used with the hex CEM. The ACP 50 cancontain up to three hex CAMs.

� Octal DMA CAM. The octal DMA CAM is used withthe octal DMA I, II, or III CEM to provide eightDMA-assisted universal ports. A special version of theoctal DMA CAM—the octal DMA/PS CAM—supportsthe Automatic Node Protection Switching (ANPS) featureof ACP Version 4.0 software. The ACP 50 can contain upto three octal DMA CAMs.

� Octal Modem CAM. This CAM is used with either theV.32 or V.34 octal modem CAM and contains eight RJ11connectors for synchronous/asynchronous modemconnections.

� ELX CAM. The ELX CAM contains one AUI DB15connector for an Ethernet connection, and two DB25connectors for the CAMs two VHSL ports. The VHSLports can be adapted to either RS-530, V.24, or V.35 byinstalling two V.series interface modules into a connectoron the CAM. The ELX CAM is used with the ELX CEM.Only one ELX CAM may be used in the ACP 50. (Sincethe BRI CAM installs in the same location as the ELXCAM, only one of these CAMs may be installed in anACP.)

� BRI CAM. The ISDN BRI CAM contains twoRJ48C-type (8-way) S0 ports to interface to the ISDN.Each interface can carry one or two B-channels at 64 kbpsand one D-channel at 16 kbps. The BRI CAM alsocontains one DB25 VHSL port supporting speeds up to384 kbps. The VHSL port can be adapted to eitherRS-530, V.24, or V.35 by installing a V.series interfacemodules into a connector on the CAM. The BRI CAM isused with the BRI CEM and is supported only by ACPVersion 1.xx software. Only one BRI CAM may be used inthe ACP 50. (Since the BRI CAM installs in the samelocation as the ELX CAM, only one of these CAMs maybe installed in an ACP.)

� T1/E1 CSU/DSU CAM. This CAM contains two RJ45connectors to provide T1 and E1 connections, and containsa DB15 connector for an Ethernet connection. The CAMprovides a mechanism to put a line into loopback mode fortesting from a central office, and also provideswarnings/alarms and collects/relays error statistics. TheCSU/DSU CAM is supported only by an ACP 50 equippedwith a 50/486 Type2 C/D CPU, an ELX II CEM, andVersion 4.0 software.

Refer to Table 5 on page 15 for additional informationregarding ACP 50 CAMs.

ACP 70 Optional Modules

The ACP 70 uses various optional modules to provide it withdifferent interfaces. These modules are described below:

� V.11, V.24, and V.35 Interface Module. Thesemodules are small accessory daughterboards that plug intotwo sockets on the ACP 70’s CPU board. The modulesinstall just behind the DB25 connectors for the ACP 70’stwo VHSL links, giving a V.11, V.24, or V.35 appearanceto the related link.

� Quad Combined Communication Module (CCM).The addition of one or two CCMs allows you to increasethe number of ACP 70 universal V.series ports. Each CCMplugs into the ACP 70’s CPU board and has four femaleDDB15 interface connectors. A CCM can be installed ineither or both of the ACP 70’s upper port areas.

� ISDN BRI Port Module. Up to four of these modulesmay be installed in an ACP 70, with each module usingone S/T port. The port supports two B-channels operatingat 64 kbps and one D-channel operating at 16 kbps. Eachmodule contains one RJ45 connector.

Refer to Table 5 on page 15 for additional informationregarding ACP 70 optional modules.

External Interface Converters

External interface converters are available to change the V.24signaling of the ACP 10, 50, and 70 to V.11/RS-530 or V.35.These converters provide clocking to the V.11 or V.35 devices,thus eliminating costly clock boxes. The converters have a25-pin connector at each end for attachment to the ACP andV.11/V.35 device sides. Connections to V.11 devices withDB15 connectors and V.35 devices with Winchesterconnectors can be achieved with the appropriate cables.

lnternal Interface Converters

Internal interface converters, known as interface modules, areavailable to define the electrical signaling for VHSL ports onthe ACP 50 and ACP 70 (see preceding CEM, CAM, andmodule descriptions). The interface modules are selected at thepoint of purchase. For the ACP 50, the interface modules areavailable for the ELX and BRI CAMs. For the ACP 70, theinterface modules are available for the main CPU board.

Page 23: ACP Functional Description Manual.pdf

ACP Functional Description, May 1998 15

Table 5. ACP Interface Hardware

CEMs CAMsCEM or CAM

Set

Max Speed (kbps)

Product Description Ports Sync Async Model # Interface Model # Model # Notes

ACP 10 (Integrated) 6 64 19.2 — V.24 — — 1, 2, 3, 4, 5ACP 50 Hex 16 — 19.2 5023-001 RJ45 V.24 5067-001 5005-001 6, 7

Hex 16 — 19.2 5023-001 RJ45 V.28 5067-002 5005-002 6, 7, 8

Octal DMA III 8 64 115.2 5019-003 V.24 5029-001 5003-004 2, 4, 5, 9Octal DMA III/PS

8 64 115.2 5019-013 Octal DMA/PS CAM:V.24

5029-011 5003-014 2, 4, 5, 17

ELX II12

10 Mbps2 Mbps2 Mbps

512

————

5020-003AUI:

(V.11/RS530)(V.35)(V.24)

5030-0025030-0035030-004

5017-4005017-5005017-600

10, 13

ELX II12

10 Mbps1.5 Mbps

——

5020-003 T1 CSU/DSU CAM:AUIRJ48

5050-001 5012-001 10, 13, 18

ELX II12

10 Mbps1.5 Mbps

——

5020-003 E1 CSU/DSU CAM:AUIRJ48

5050-002 5012-002 10, 13, 18

Octal modemV.32 8 14.4 57.6 5022-001 RJ11 LL/UK 5016-001 5020-001 11

Octal modemV.32 8 14.4 57.6 5022-001 RJ11 PSTN/US 5016-002 5020-101 11

Octal modemV.32 8 14.4 57.6 5022-001 RJ11 PSTN/UK 5016-003 5020-201 11Octal modemV.32 8 14.4 57.6 5022-001 varies by country 5040-xxx 5120-xxx 11, 12

Octal modemV.34 8 28.8 115.2 5036–004 RJ11 LL/UK 5016-001 5034-001 11

Octal modemV.34 8 28.8 115.2 5036–004 RJ11 PSTN/US 5016-002 5034-101 11

Octal modemV.34 8 28.8 115.2 5036–004 RJ11 PSTN/UK 5016-003 5034-201 11

Octal modemV.34 8 28.8 115.2 5036–004 varies by country 5040-xxx 5037-xxx 11, 12

BRI 21

642 Mbps2 Mbps

512

—5010-002 S0, RJ45:

(V.11)(V.35)(V.24)

5011-0115011-0355011-024

5010-0115010-0355010-024

11, 13, 14

ACP 70 (Integrated) 4 64 57.6 — V.24 — — 15

VHSL (Integrated)

222

2 Mbps2 Mbps2 Mbps

———

—V.11V.24V.35

7710-0117710-0247710-035

15

ELX (Integrated) 1 10 Mbps — — AUI — —

ISDN BRI 1 64 — — S0, RJ45 — 7704-001 16Quad CCM 4 64 57.6 — V.24 — 7703-001 3, 15

Continues...

Page 24: ACP Functional Description Manual.pdf

ACP Functional Description, May 1998 16

NOTES:1. Supports 1 sync port at speeds up to 64 kbps plus 3 others at 19.2 kbps, or 1 at 64 kbps plus 5 at 9.6 kbps, or 1 at 64 kbps plus 5 async

at 19.2 kbps.2. Supports V.54 loopback testing.3 V.11 or V.35 support is provided on up to 3 ports using external converter kits (models 3020-030 and 3020-050).4. V.11 or V.35 support via external converters (models 3020-040 and 3020-060).5. Clock speeds provided are: 1.2, 2.4, 4.8, 9.6, 19.2, 38.4, 56/57.6, 64 kbps. External clocking must be provided for all intermediate

speeds.6. The ACP 50 supports a maximum of three hex CEM/CAMs and two high speed links.7. Supports V.54 Loop 1 testing only.8. The V.28 CAM interface supports a V.28 electrical interface of up to 300 bps. To achieve speeds up to 1200 bps, consult your

Telematics sales representative.9. The Octal DMA II is replaced by the backward-compatible octal DMA III. Octal DMA III offers the 115.2 kbps port speed on the ACP

50/486 only in Version 2.xx or higher software. The ACP 50 supports three octal DMAs IIs with a maximum of 24 sync ports at speeds up to 64 kbps or 24 async ports at speeds up to 57.6 kbps. The ACP 50/486 with octal DMA IIIs support a maximum of 24 sync ports at 64 kbps or 24 async ports at 115.2 kbps.

10. Clock speeds provided are: 64, 128, and 256 kbps. External clocking must be provided for 384 kbps and above (no enable key required).The ACP 50 supports only one ELX or BRI module. The VHSL ports are only used for X.25 and frame relay.

11. The ACP 50 stretch chassis supports a maximum of 3 octal modem cards (24 modem ports). 12. The suffix xxx represents the three digits that specify country. Refer to the ordering section of this manual for model numbers for specific

countries. 13. ACP 50 BRI supports 1 port at 2 Mbps plus 1 port at 384 kbps, or 2 ports at 512 kbps. VHSL speeds are dependent on packet size, link

layer window, and flags between frames. Ports must be application-tested to achieve maximum speed without link layer re-transmissions. With a single VHSL port on the ISDN BRI, the maximum speed for the ACP 50 is 2 Mbps.

14. Requires software version 2.xx or higher for V.24 operation. 15. The ACP 70 V.series ports can be configured for either internal or external clocking, up to the maximum port speeds identified.16. Up to four S0 ports per ACP 70; each S0 port supports 2B+D channels. Depending on BRI module locations, links 1–6 or links 1–10

must operate synchronously.17. The octal DMA III/PS CEM and octal DMA/PS CAM support the Automatic Node Protection Switching (ANPS) feature provided by

Version 4.0 software. Each CEM/CAM supports eight ports at up to 64 kbps sync and 115.2 kbps async.18. The ELX II CEM connected to a T1 CSU/DSU CAM supports a 100 ohm, RJ48 interface. The ELX II CEM connected to an E1

CSU/DSU CAM supports a 120 ohm, RJ45 interface.

Page 25: ACP Functional Description Manual.pdf

ACP Functional Description, May 1998 17

Level 1 Support

Interface

The ACP 10 and ACP 70 universal ports have a V.24 interface.External V.24-to-V.11 or V.24-to-V.35 converter kits can beconnected to the ACP 10 or ACP 70 to interface to V.11/V.35devices.

The ACP 50 provides a V.11, V.35, or RS530 interface,depending on the type of CAM used. The Octal DMA CAMshave a standard V.24 interface, and can use external V.11/V.35converters.

For SNA operation on the ACP 50 platforms, DMA portsconfigured for SDLC operation can operate in NRZ/NRZImode. The ACP 10 supports NRZ/NRZI on all of its ports.

For the ACP 50 and ACP 70, the VHSL CAM is availablewith a V.35, V.24, or V.11/RS530 interface. The ELX CAMprovides an Ethernet AUI port in addition to the above VHSLinterfaces.

Clocking

Each X.25 link interface can be operated using an internal orexternal clock. The internal clock will typically be enabledwhenever the ACP is co-located with other DTEs, eliminatingthe need to use an external clocking device.

While all ACP synchronous ports present a DTE-type physicalinterface, most can be configured to generate a clock signal.The ACP 10/50/70 V.11 and V.35 interfaces must be clockedby attached external devices when connecting to publicnetwork facilities. The V.11 and V.35 converters can, however,clock co-located DTE devices.

Speed

DMA-assisted ports can support X.25 or frame relay operationat a maximum rate of 64 kbps; other sync ports can beoperated at speeds of 1.2 to 19.2 kbps. The ACP 50 and ACP70 support X.25 or frame relay operation up to 2 Mbps. Table 5 on page 15 outlines the maximum supported synchronousspeeds per type of port.

Table 6 summarizes the maximum number of ports possiblefor a specific port speed on each ACP platform.

For a summary of the platforms and related port types, refer toTable 6.

Table 6. Number of Ports per Speed per Platform

Feature ACP 10 ACP 50 ACP 70

Maximum Ports 6 50 14

Maximum SyncPorts 6 26 14

Max 64 kbps SyncPorts 1 26 14

Max 384 kbpsSync Ports — 2 2

Max 512 kbpsSync Ports — 2 2

Max 2 Mbps SyncPorts — 1 2 —

Maximum AsyncPorts 5 48 12

Max 19.2 kbpsAsync Ports 5 48 12

Max 38.4 kbpsAsync Ports — 24 12

Max 57.6 kbpsAsync Ports — 24 12

Max 115.2 kbpsAsync Ports — 24 —

Max ISDN BChannels — 2 8

Max EthernetPorts — 1 1

Max modem Ports — 24 —

Max RAM 256 K 32 MB 4 MB

Code Storage (Banks 1& 2)

512 K PROM512 K Flash

1.44 MB Disk4 MB

PCMCIA

2 MB Flash4 MB

PCMCIA

NOTES:1. Requires octal DMA III and version 2.xxx and later software.2. Dependent on packet size, link layer window, and flags between

frames. Ports must be application-tested to achieve maximumspeed without link layer re-transmissions.

Page 26: ACP Functional Description Manual.pdf

ACP Functional Description, May 1998 18

Table 7. Protocols Available with Port Types/Connectors

ACP 10 1, 2

ACP 50 1, 2 ACP 70 2

Protocol/Interface

V.24(DDB15)

VHSL 1

(DB25)Octal

(DB25)Hex 3

(RJ45) RJ11 4ISDNRJ45

AUI 5

EthernetVHSL 1

(DB25)V.24

(DDB15)ISDNRJ45

AUI 5

Ethernet

SLIP, PPP 8 ■ ■ ■ ■

Async ■ ■ ■ ■ ■

X.25 ■ ■ ■ ■ ■ ■

FrameRelay ■ ■ ■ ■ ■

SNA ■ ■ ■

DSP (3270BSC) ■ ■ ■

TPP ■ ■ ■

IP(Ethernet) ■ ■

POS ■ ■ ■ ■ ■ ■ ■ ■

ISDN BRI ■ 6 ■ 7

NOTES:1. VHSL sync-only ports: ACP 10 link 1; ACP 50 ELX and ISDN CEM/CAM ports; ACP 70 VHSL ports. 2. Sync or async (universal) ports: ACP 10 links 2–6; ACP 50 octal DMA CEM/CAM ports; and ACP 70 links 3–6 and CCM ports. 3. Async-only: ACP 50 hex CEM/CAM ports.4. The RJ11 connector appears on integrated modem modules.5. AUI port on the ACP 50 ELX card; embedded LAN port on ACP 70.6. Located on the BRI CAM. Provides one S0 interface, providing two B channels.7. Provides up to four S0 interfaces, providing 8 B channels.8. PPP is available only on the ACP 70 and on selected IP p-kits on the ACP 50.

Page 27: ACP Functional Description Manual.pdf

ACP Functional Description, May 1998 19

Software Architecture

ACP communication software offers ease of use andversatility:

� Field-proven software—since 1985, operating code writtenin “C” for easy maintenance/customizing.

� Software updates via diskette, flashpak, or downloadedthrough the network from the Network ManagementSystem.

� All options are software-configurable. Dynamic userinterface and routing parameters.

The ACP communication software environment consists ofsoftware modules that support each of the product’s majorfunctions:

� FR (Frame Relay)

� IP (Internet Protocol) including SLIP and PPP

� ISDN BRI (Basic Rate Interface)

� POS (Point of Sale)

� Network Interface (NET) for X.25 operation

� SNA (Host PAD and Terminal PAD) for SNA operation

� DSP (Terminal PAD only) for BSC operation

� TPP (Transparent Protocol Passthrough)

� Asynchronous Interactive Terminal Interface (ITI)

� Modem (MD)

� System Manager (SYM)

� Accounting (ACCT)

� X.25 Trace (TRACE)

� Network Management System (NMS) Interface toSmartView / INF / OMS

� X.25 Trace (TRACE)

This modular approach permits the wide variety of networkconnectivity available to each ACP product while maintainingcommon software. A single ITI module in an ACP, forexample, will support as many asynchronous ports as can beinstalled in a given ACP platform. Similarly, multipleinstances of the NET module can be activated to support X.25operation on as many synchronous ports as required (up to themaximum that can be installed in that platform).

Modular software simplifies system configuration: operationalparameters are grouped by major protocol layers and functionsto focus on one concept at a time, using the same commandsand following the same rules. This scheme also allows you toalter configuration parameters related to one module withoutaffecting the others.

Software modules interact via a software bus (shown inFigure 3) called the network router. A software module itself,the network router is responsible for establishing connectionsand routing data to and from each of the other modules.

� The SYM module implements the local systemmanagement functions. This module allows one toconfigure, monitor, control, and collect system statistics.

� The TRACE module implements the system’s dataanalyzer function, which allows one to examineLAPB/SDLC frames, BSC blocks, X.25 packets, and SNARUs as they exit or arrive through the synchronous ports. Italso allows network operators to remotely view any port’sEIA status.

Figure 3. ACP Software Architecture

Management

Protocol

Media

NMS

DSP FRX.25 ITI SNA TPPIP

ELX ISDNVHSLPORT

SYM TRACE ACCTModules

Modules

Modules MODEM

POS

ANPS

CSU/DSU

Page 28: ACP Functional Description Manual.pdf

ACP Functional Description, May 1998 20

� The NMS module implements the remote systemmanagement functions handling the ACP interface toSmartView, INF, or OMS.

The SYM, TRACE, and NMS modules allow you todynamically change the operating parameters, performdiagnostics, monitor performance, and retrieve statisticsfrom any point on the network using a character-modeterminal or a PC equipped with SmartView, INF, or OMS.

� The ACCT module implements the accounting functionsfor the ITI and NET modules. It produces accountingrecords that can be collected by SmartView NetworkManagement System (NMS). IP accounting through aRadius server is external to the accounting module.

� The Automatic Node Protection Switching (ANPS)module provides automatic backup of an entire node. Thisis done automatically and the network manager is informedof a failure through an SNMP trap. Async connections areaccomplished by using “Y” cables.

� The X.25 (NET) module implements the CCITT X.25standard interface to handle all aspects of the packet andlink level operation. Separate instances of the X.25 moduleare activated to support the X.25 operating mode for eachsynchronous port.

� The DSP module, based on the BSC 3270 Display SystemProtocol, enables IBM 3270 devices to communicate withIBM host computers (equipped with a DSP-compliantsoftware/hardware) through an X.25 packet switchingnetwork. Acting as a Terminal PAD (TPAD), it supportsConnection Request Modes (CRM) 1 through 4.

� The FR module implements a set of DTE and DCEinterface functions to handle the operating environmentrequired by both public and private frame relay networks,as well as native DTE frame relay devices such as bridgesand routers.

� The ITI module implements CCITT standards X.3, X.28,X.29, and X.121 to handle all aspects of asynchronousoperation to and from the attached async devices. The ITImodule is also responsible for voice/fax operation.

� The SNA module implements a set of PU2 and PU4functions to handle the required operating environmentwith both IBM PU2 devices and PU4/5 hosts. The VLUmode supports switching at the LU level while the QLLC

mode limits switching to the PU level. The QLLC mode iscompatible with NPSI environments. Both NRZI and NRZmodes of operation are supported.

� The IP module allows the interconnection of EthernetTCP/IP LANs over X.25 or frame relay networks. Thismodule supports synchronous PPP and asynchronous SLIPand PPP for connections to a LAN. Support forPAP/CHAP/Radius authentication is also available. SeeOrder Forms for IP p-kits which support PPP with IPtransporter (Version 2.xx software).

� The TPP (Transparent Protocol Passthrough) moduleallows a transparent connection between synchronousdevices through an X.25 network. TPP is used in anACP-to-ACP configuration to transport synchronous byte-and frame-oriented protocol data in the “payload” of anX.25 packet. Unlike other protocol systems, such as SNAand BSC, no “spoofing” (i.e., local handshaking) isnecessary. For this reason, there is no requirement forTPAD/HPAD services. This mode of operation isproprietary, and requires that an ACP be located attransmission end points.

� The ISDN BRI (Basic Rate Interface) module configuresthe 2B (bearer of high speed data) channels and a D (datacontrol and signaling) channel.

� The Modem (MD) module sets up the mode of operationand relevant parameters (baud rate, etc.) for each modemport integrated into the ACP.

� The POS module allows the attachment of Point of Saleterminals and host computers to either private or publicdata networks. POS supports ISO 8583, VISAI, VISAII,APACS, SPDH, and TINET protocols. POS featuresinclude “fast connect” modems and local protocol spoofingwhich both help reduce overall transaction response time.

� The internal T1/E1 CSU/DSU module provides directconnection to T1 or E1 services. This eliminates the needto purchase an external CSU/DSU. The CSU/DSU is adual-port device and is fully manageable by using the ACPSystem Manager (SYM) software module. The interfacefor T1 is a 100 ohm RJ45 connector. The interface for E1is a 120 ohm RJ45 connector. There are three LEDindications per port to indicate “on line,” “yellow alarm,”and “red/blue” alarm or loss of frame.

Page 29: ACP Functional Description Manual.pdf

ACP Functional Description, May 1998 21

System Management

The ACP’s resident management facility module is the SystemManager module (SYM). SYM is automatically included withthe ACP applications software and allows local or remote con-trol and management of that node within a network. SYM isaccessed through the ACP service port, and is displayed/usedvia an external terminal.

An authorized user can set up a virtual call to the residentSYM module to configure the operating parameters, performon-line diagnostics, monitor link performance, and retrievestatistics from any point in the network.

All of the configuration parameters can be viewed, altered andsaved on the system diskette (or in non-volatile memory in theACP 10) without affecting the sessions in progress. Residentaccounting, protocol components, and CPU/memory usagemonitors cooperate to provide statistics for each node, port,user, and call. The statistics may be used to monitor the qualityof service and system usage to fine-tune the operation of anACP node.

Many commands are available to help the network administra-tor manage the X.25, SNA, frame relay, and DSP links:

CLOSE Do not accept new calls on that link.

OPEN Cancel a close command.

DOWN Clear or reset all virtual circuits on a givenlink; put the link in disconnect mode.

UP Restart the link.

STAT Report the status of a link.

The network administrator may also clear any virtual circuit onany given link.

To complement the command set, the administrator may acti-vate a very comprehensive trace facility from any point on thenetwork. Each of the following types of trace is available oneach link:

� Trace all logical channels.

� Trace a specific logical channel.

� Trace the channel to be used for the next call.

� Trace all packets.

� Trace call request/accept and unnumbered packets.

� Trace and display the full data packets.

� Trace a specified PU or all PUs.

� Trace a specified LU or all LUs.

� Trace a specified CU or all CUs.

� Trace a specified device or all devices.

� Electronic “breakout box” for displaying the status of anACP port EIA interface.

Extensive Diagnostic Capabilities

The diagnostic functions supported by the ACP include errormessages, V.54 loopback testing, line trace, and performancemonitoring. This allows the network administrator to examinetransmissions from the physical layer through the packet layerquickly and easily (see the sample trace in Figure 4). The loop-back testing can also be invoked remotely to troubleshoot mo-dems, lines, or ACP ports.

*10000*‘traceSmartNet:fac: p(512,512),w(5,5),d(9600,9600) com00:31:43.8 net1.r. 3 RR r000:31:43.8 net1.r. 10 03 0100:31:43.9 net1.r. 3 RR r100:31:43.9 net1.r. 10 03 2100:31:44.0 net1.r. 3 CLR REQ00:31:44.0 net1.r. 10 03 13 00 F500:31:44.0 net1.t. 3 CLR CNF00:31:44.0 net1.r. 10 03 1700:32:19.2 net1.r. 3 CAL REQ00:32:19.2 net1.r. 10 03 0B 55 10 00 01 11 11 14 42 09 09 43 05 05

Figure 4. A Sample Trace

Figure 5 and Figure 6 illustrate external and internal modemusage with ACPs and show how the ACP’s self-generated,CCITT-defined, 511 random test pattern may be used to diag-nose problems. The test pattern can be generated on three dif-ferent loop tests to isolate problems quickly.

Page 30: ACP Functional Description Manual.pdf

ACP Functional Description, May 1998 22

(V.54 Compatible)

MODEM

(V.54 Compatible)

ACP 50

CEMCPU

ACP 50

CEM MODEM

(V.54 Compatible)

CPU

ACP 50

MODEM

(V.54 Compatible)

DTE

(V.54 Compatible)

Sample Network. This is a sampleconnection between the ACP 50 anda DTE.

a) Loop 1. The CCITT loop 1 testis run to check for the integrity ofthe ACP I/O circuitry. In thisexample, it tests the ACP 50’sCEM.

b) Loop 3. If loop 1 passes, theloop3 test is then run to checkthe path to the analog side ofthe local modem.

c) Loop 2. This test checks theintegrity of the whole path—fromthe ACP port to the digital sideof the remote modem.

Loopback Tests

CAM

CAM

MODEM

MODEM DTE

Figure 5. Loopback Tests with External Modems

ACP 50

MODEM

(V.54 Compatible)

ACP 50

CEMCPU

ACP 50

CEMCPU

ACP 50

DTE

(V.54 Compatible)

Sample Network. This is a sampleconnection between the ACP 50 anda DTE.

a) Loop 1. The CCITT loop 1 testis run to check for the integrity ofthe ACP I/O circuitry. In thisexample, it tests the ACP 50’sCEM.

b) Loop 3. If loop 1 passes, theloop3 test is then run to checkthe analog side of the internalmodem.

c) Loop 2. This test checks theintegrity of the whole path—fromthe ACP port to the digital sideof the remote modem.

Loopback Tests

CAM

CAM

MODEM

DTE

Figure 6. Loopback Tests with Modems Integrated into the ACP 50

ACP 50

Page 31: ACP Functional Description Manual.pdf

ACP Functional Description, May 1998 23

Additional Network Management Options

In addition to SYM, ACPs can utilize other network manage-ment methods to control multiple ACPs within a network.These additional methods are as follows:

SNMP Agent. As an interface to a local and remotemanagement system, the ACP SNMP Agent allows you tomanage, monitor, and configure the ACP from an SNMPmanager at your site. Any of several SNMP managers (e.g.,HP OpenView) can be used. SNMP Agent services SNMP V1requests from the SNMP manager, and reports unsolicitedtraps to the SNMP manager for pre-configured ACP alarmconditions. Figure 7 shows an application using SNMP Agentfor remote management.

File Transfer Protocol (FTP). The FTP softwarecomponent supports the upload and download of ACP codeand configuration data from a PC FTP client over an IPnetwork (see Figure 8).

ACP TELNET Server. ACP TELNET Server allowsTELNET clients on a LAN to login and establish a TELNETsession with the ACP System Manager (SYM). Clients canalso trace components to conduct remote management anddiagnostic procedures (see Figure 9 and Figure 10).

Open Management System (OMS). The Open Manage-ment System (OMS) network management option is availableon an HP OpenView host. This software includes an SNMPManager which communicates with one or more SNMPAgents residing in the network.

Figure 7. Application Using SNMP Agent to Manage ACPs

ACP 50

Router

SNMP ManagerWAN

HP OpenView

ACP 70

Figure 8. Application Using FTP

ACP 50

IP/X.25/FR FTP Client

ACP 70FTP Server

FTP Server

ACP 50FTP Server

ACP 70

Page 32: ACP Functional Description Manual.pdf

ACP Functional Description, May 1998 24

Figure 9. Application Using TELNET Server to Manage ACPs

IP TELNET ClientRouter

TELNET ServerACP 70

TELNET ServerACP 70

TELNET ServerACP 70

Figure 10. Application Using TELNET Client to Manage ACPs

IP

TELNETClient

VT-100TELNET Server

ACP 70

TELNET ServerACP 70

TELNET ServerACP 70

TELNET ServerACP 70

Page 33: ACP Functional Description Manual.pdf

ACP Functional Description, May 1998 25

Automatic Node Protection Switching (ANPS) Support

Automatic Node Protection Switching (ANPS) is an optionthat can be used when the availability of the ACP is critical orwhen no on-site service is available. ANPS is implemented byusing two ACP 50s connected in tandem (see Figure 11). TheANPS software automatically detects any failure that occursand switches operation to the standby node. When this switchoccurs, the access channels are switched between the twonodes. The network links are connected to separate and uniqueconnection within the network, and therefore are not switched.ANPS also allows network access to the backup node or to thedown system without interfering with the operation of the on-line node.

The two nodes in an ANPS arrangement are set up to be moni-tored by an SNMP agent, so that a “trap” will be sent out tothe Network Control Center whenever a failure or switchoveroccurs. This will inform the manager of the center that thestatus of the nodes has changed.

Connecting the Nodes

When ACPs are configured for ANPS capability, both nodesare connected to the user interface through the use of “Y”cables. These cables are specially configured to connect to twoseparate ACP 50s and to carry necessary switching signalsfrom one node to the other.

Configuring the Nodes

The two ACP 50s in an ANPS arrangement must be confi-gured identically. This enables the backup node to take over ifthe other system happens to fail. It is the responsibility of the

Network Control Center to ensure that the required configura-tions are downloaded to the two ACP 50 nodes.

Failure Scenarios

The first or lowest-numbered channel is used by the ACP 50sto communicate a “Keep Alive” protocol. By using this proto-col, each of nodes in the ANPS arrangement supervises thestatus of the other node. The failure scenarios that are sup-ported by ANPS are as follows:

� The online node fails.

� The offline node fails.

� The monitor link fails.

� A manual switchover occurs.

The results of each of these scenarios are described in the fol-lowing paragraphs.

The Online Node Fails. If a situation occurs in which theonline node suffers a catastrophic failure, then the offline nodedetects the failure, and within seconds, activates the switchingcontrol and switches all the access ports to itself. When thisoccurs, the effect to the user is momentary loss of the commu-nication session, requiring a new session to be established.

The Offline Node Fails. If the offline node happens to fail,then the online node will detect a lack of activity on the moni-tor link and then send an SNMP trap to the Network ControlCenter, informing the network manager that the offline nodehas failed.

Y-Cable

ACP 50

PSTN

Figure 11. Typical Automatic Node Protection Switching (ANPS) Application

ACP 50

(A)

(B)

V.24

V.24

IPCConnection

IndependentNetwork Connections

IndependentNetwork Connections

IPCCable

Page 34: ACP Functional Description Manual.pdf

ACP Functional Description, May 1998 26

The Monitor Link Fails. An example of this scenario is ifa monitor link cable becomes disconnected on ACP node (A).In this situation, the disconnected cable is detected via loss ofEIA signal on the monitor link port. When this occurs, anSNMP trap is issued to the network manager, indicating thatthe monitor link has failed, and node (A) enters a “lnkerr” state(which is displayed in the protstat software file).

If node (A) was online at the time of the disconnect, then thebackup, offline node (B) will take over operation. This occursdue to the loss of “keep alive” status message from node (A).At the time of this automatic switchover, the now online node(B) sends an SNMP trap to the network manager to indicatethat it is now in service.

At this point, both node (A) and node (B) are both “online.” Inreality though, only node (B) is online; node (A) just thinks itis. This is an alert to the network manager that the monitor linkis down. Once the monitor link is fixed, it will reconfigurenode (A) to a backup position.

A Manual Switchover Occurs. A manual switchoverbetween nodes in an ANPS arrangement is accomplished ei-ther by resetting the online node or by disabling ANPS in theonline system. After either of these actions, the backup nodewill detect that the online node is no longer active and it willswitch over.

Page 35: ACP Functional Description Manual.pdf

ACP Functional Description, May 1998 27

X.25 Support

Each X.25 link can be configured independently from theother links. ACPs allow the user to update most of the linkparameters without resetting the unit.

For example, you can activate or deactivate a link, change itsspeed, and modify facilities or packet level timers withoutaffecting the operation of other links. By assigning differentcharacteristics to the links individually, ACPs can be used tointerconnect X.25 equipment and/or networks of differentvintage.

The following describes the characteristics of the X.25interface as supported by the ACP NET module.

The Level 2 Frame Interface

Procedures

ACP ports configured for X.25 operation support thebit-oriented, LAPB link procedures.

Alternatively, the ACP can use SDLC instead of LAPB forinterconnecting. (See Multipoint Support section on page 31for further information on this subject.)

Addressing

ACP links connected to the PDN will be configured to have alogical DTE appearance. However, any link can be configuredfor a DCE appearance to connect directly to other X.25equipment.

Numbering

The frame level supports both the normal (modulo 8) or theextended (modulo 128) frame sequence numbering. Modulo128 is recommended for optimal satellite or high-speedconnections, and allows the user to operate with a framewindow up to 15.

Parameters and Timers

All the following frame level parameters are supported, andare individually soft configurable on each link:

K: frame level window; 1–15.

N1: maximum number of bits in a receive frame. Supportspacket sizes 128, 256, 512, 1024, 2048, and 4096 (octets).

T1: acknowledgement timer; 1–300 seconds.

T2: Frame Acknowledgement Delay timer; 1–300 seconds.

N2: retransmission counter; 0–255.

T3: link watchdog timer; 0–300 seconds.

ACKTHRESHOLD: a link window threshold for a link-levelacknowledgement.

The Level 3 Packet Interface

Services

Each X.25 port can support concurrent switched andpermanent virtual circuit operation.

Logical Channels

Each X.25 port can be configured to support any range of the4096 logical channel addresses defined by the X.25recommendation. The maximum number of logical channelsthat can be active concurrently on any given ACP vary by thetype of platform and amount of installed memory.

LCN Assignment

For each link, the user may specify the range and number oflogical channels for PVCs or three types of logical channels(incoming, outgoing, and two-way) for SVC operation. Thisallows the user to fine-tune the allocation of each link’sbandwidth.

For private internodal links, e.g., between ACPs, there is noneed to pre-assign LCNs for PVC operation. PVCs can berouted as SVCs to provide alternate routing and contention—afeature typically available only to SVC operation.

NOTE: To route an incoming call through an ACP, a pair oflogical channels—one on each link—is required.

Numbering

The packet level supports both the normal (modulo 8) and theextended (modulo 128) packet sequence numbering. Theextended mode allows individual virtual circuits to use awindow as large as the frame window supported by theunderlying link.

Packet Size

16–4096 octets. The user may configure a default (minimum)and maximum packet size. These parameters are used tobracket the values invoked by call request packets requestingflow control parameter negotiation.

Window Size

1–15. Users may configure a default (minimum) andmaximum window size. These parameters are used to bracketthe values invoked by call request packets requesting flowcontrol parameter negotiation.

Throughput Class

Negotiates incoming calls to a value preconfigured by the user,and will also limit the requested value in outgoing calls to avalue configured by the user.

Page 36: ACP Functional Description Manual.pdf

ACP Functional Description, May 1998 28

Reverse Charge

Any link can be configured for reverse charging acceptance. Itcan accept or reject incoming calls specifying reverse charge.Links used to interconnect X.25 DTEs can be configured tonot forward calls with reverse charging to the DTE.

Fast Select

An ACP NET module can route normal and restrictedfast-select calls. Each link can also be configured to accept orreject incoming fast-select calls.

D-bit

The packet level supports the delivery confirmation D-bit inincoming calls by acknowledging these packets when receivedat their destination.

D-bit Modification

ACPs can be configured such that packets received on a linkcan be considered to have their D-bit set for end-to-endacknowledgement.

Timers

Each link can be configured to support a range of packet leveltimers. In particular, the following timers are configurable bythe user to meet the requirement of the PDN or the packetmode DTE to which it is connected:

� T20, T21, T22, and T23 timers for a link with DTE appear-ance.

� T10, T11, T12, and T13 timers for a link with DCE appear-ance.

� ACKTIMER—A packet-acknowledgement delay timer.This timer is mandatory for satellite links and can also beused to improve the terrestrial links’ efficiency.

� ACKTHRESHOLD—A packet window threshold for re-laying packet level acknowledgement, used to reduce thenumber of acknowledgement packets.

General X.25 Features

The X.25 interface supports these additional features:

� Packet splitting and reconstruction to accommodate differ-ent packet mode destinations.

� Private internodal links protocol to track and clear strandedcalls. Each ACP validates incoming calls to ensure thatthey have not been routed a second time, which wouldindicate a configuration error.

� Private internodal links allow ACPs to establish a new pathfor a PVC if the primary path is unavailable.

� Call request packet called- and calling-address fields maybe modified to achieve compatibility between two inter-connected destinations.

� Call request packets can be validated for an authorizedcalling address.

Network Support

The X.25 networking software has been certified on all majorNorth American public data networks and has been certifiedfor compliance with NET2 (levels 1, 2, and 3) Europeanstandards recognized by 22 European countries.

ACPs are also operating successfully with X.25 equipmentand software of major computer vendors that include AT&T,BULL, CDC, IBM, Honeywell, ICL, NCR, PRIME, andTANDEM.

In order to accommodate the different X.121 and X.25variations of different networks and other manufacturers’equipment, many configurable options have been implementedin the ACP. The user may turn on or off some of theseparameters as the X.25 implementation of his equipment ornetwork evolves.

Following are some of the features and capabilities thathave been incorporated to facilitate the integration ofACPs into deployed networks:

� Each link may be configured to insert, modify, or delete agiven calling address field from outgoing call requestpackets. This gateway function is necessary when inter-connecting an ACP-based private network to a Public DataNetwork.

� For PDNs or equipment that do not support the 1988CCITT recommendation, the packet level can be confi-gured to operate per previous CCITT recommendations.

� ACPs can be configured to generate diagnostic packetsupon certain network errors.

� ACPs can be configured to delete the flow control negoti-ation facility field to accommodate networks that do notsupport this facility.

� ACPs will ignore national X.25 facilities in incoming callpackets.

� ACPs can be configured to accept incoming calls onLCN 0 to accommodate the French TRANSPAC network.

� To accommodate different link-establishment procedures,each link may be independently configured to take the ini-tiative or wait for the other packet mode DTE/DCE to es-tablish the link.

Page 37: ACP Functional Description Manual.pdf

ACP Functional Description, May 1998 29

X.25 Network Service Specifications

As a protocol, X.25 is as applicable to private networks as topublic networks. Because the CCITT X.25 recommendationwas specified as a subscriber-to-network interface, it waswritten from the DCE point of view. Accordingly, the ACPX.25 module was made to fully comply with it when operatingin DTE mode.

The ACP X.25 module also allows users to fully interconnectACPs to form a private network, and to interact with otherpacket mode DTEs.

While the ACP implements most of the networkingfunctions—routing, alternate routing, call redirection, etc.— itdoes not implement Public Data Network functions, such asClosed User Groups and on-line facility registration. Table 8outlines compliance with different facilities and optionsspecified in 1988 for DCE and DTE modes.

Table 8. 1988 Facilities/Options Compliance

Item Facility/Option DTE DCE

1 SVC � �

2 PVC � �

3 Data TransferRNR PacketD-bitQ-bit

4 DTE-originated Cause CodesDCE Cause Codes, 1984

5 Interrupts- 1984 Extensions

6 Datagram Service7 Diagnostic Packet � �

8 On-line Facility Registration9 Extended Packet Seq � �

10 D-bit Modification � �

11 Packet Retransmission � �

12 Incoming Calls Barred � �

13 Outgoing Calls Barred � �

14 1-way Log. Channel Incoming � �

15 1-way Log. Channel Outgoing � �

16 Non-std Default Pkt Size- 1984 Extensions

17 Non-std Default Window Size � �

18 Default Thruput Class Assignment � �

19 Flow Control Negotiation- 1984 Extensions

� �

20 Throughput Class Negotiation � �

21 Closed User Groups- 1984 Extensions- CUG with Outgoing Access- CUG with Incoming Access- Incoming calls barred within CUG- Outgoing calls barred within CUG- CUG Selection- Bilateral CUG- Bilateral CUG w/outgoing access- Bilateral CUG Selection

Table 8. 1988 Facilities/Options Compliance (cont.)

Item Facility/Option DTE DCE

22 Fast Select- 1984 Extensions- Fast Select Acceptance

23 Reverse Charging- Reverse Charging Acceptance

24 Local Charging Prevention

25 Network User Identification �

26 Charging Information � �

27 PSS Call Statistics

28 RPOA Selection � �

29 Hunt Group � �

30 PSS Multiline

31 Call RedirectionCalled Line Address Modification- Call Redirection Notification

32 Transit Delay Selection/Ind. � �

33 DTE Facility Marker � �

34 Calling Address Extension � �

35 Called Address Extension � �

36 Minimum Throughput Class � �

37 End-to-end Transit Delay � �

38 Max unacked frames (K) <= 7Max unacked frames > 7

39 Expedited Data Negotiation � �

40 LAPBLAP

41 Frame sequence numbering(Modulo 8 & Modulo 128)

� �

42 SLP (single link)MLP (multi-link)

� �

43 Max frame size (N1) >=1080<=2080/2088<=8224/8232>8224/8232

44 N2 retransmissions <= 10> 10

45 Timers: T1: 1-15T2: T2<T1T3: T3>T1T4: T4>T3

46 Call deflection selection and subscription

47 TOA/NPI address subscription48 Abbreviated address calling

Page 38: ACP Functional Description Manual.pdf

ACP Functional Description, May 1998 30

ACP Network Router

To enhance the reliability of the network, all addressing androuting decisions are distributed in the ACP node. Smart-View,� the SmartNet ACP Network Management System, isnot involved in call routing. Routing is based on theACP-resident, user-configured network map and routingtables. These tables allow the network administrator to designa network topology that provides the desired level of responsetime, availability, and cost.

The network router allows the user to specify one or morealternate routes to maintain service to users when link failuresoccur. An alternate route is also used when the primary routehas no available logical channels or the final destinationcannot be reached. When all options are exhausted and thedestination is still not reachable, the ACP network will clearthe call.

You may also specify a call-sharing group, consisting of twoor more links. The ACP will then balance the calls among allthe links in the group.

Call Redirecting

Using this X.25-specified feature, ACPs can redirect callswhen the attached called-DTE is busy, out of order/notobtainable, or if the call redirection feature has been set for aspecified address.

When configured with the appropriate reroute information, thecalled ACP will reroute the call to the destination address byusing the best available route. If the first reroute fails toconnect, the next X.121 addresses will be attempted.

Addressing

ACPs allow the routing of calls based on the content of thecalled address field and/or the call-user-data field. For privatenetworks, the called address field is usually adequate.However, when interconnecting a private PDN to the publicPDN, the X.121 subaddress field may not provide thenecessary number of digits to uniquely identify all the privatenetwork destinations. The call-user-data field may then beused as an extension to the called address.

The OSI extended address field may be used alternatively asan extension to the called address field. This allows X.25DTEs to insert additional routing information into the facilityfield of the call packet.

Address Translation

ACPs can be used as a gateway between networks withdifferent X.121 address schemes. ACPs will map either orboth called and calling addresses (using addresses precon-figured by the user) to allow routing within the network.

Network Map

For ease of configuration and network growth, the networkmap concept allows the user to define the whole network intabular form.

The network map includes ACPs, other interconnected X.25equipment, and/or public data network(s). It allows the user toassociate both an X.121 address and call user data with eachdestination.

Routing Table

A single routing table configures an ACP node. When linksare added, a few entries in that table are all that is required—there is no need to define a new routing table for each link.Once the network map is defined, the ACP uses the routingtable to determine the link(s) that can be used to reach a givennetwork destination.

In addition to defining how to reach specific destinations, therouting table is used to assign priorities to the links. Huntgroups are formed by assigning the same priority to two ormore links, while alternate paths are configured by assigningdifferent priorities to links.

Additional control can be configured by routing the sourcecalling address or extended address.

X.25 Dial Out

This feature allows ACPs to automatically establish an X.25connection to another ACP or X.25 packet mode device viathe public switched telephone network (PSTN). The ACPaccomplishes this by using the Hayes�/V.25bis asynchronoushandshake to activate a dial-up connection, and thendisconnects after a specified period of inactivity. The userspecifies the handshake type and speed, timeout delay, howmany times the ACP should attempt to connect to adestination, and the inactivity period that triggers automaticdisconnection of the dial-up connection.

This feature can be used to back up dedicated ACP X.25 links,as shown in Figure 12, or to establish a temporary “overflow”link when the number of virtual channels on the primary linkexceed a predefined number.

In addition, ACPs deployed at sites where traffic does notwarrant a dedicated link use this feature to establish an X.25link on demand. The first X.25 call request packet causes theACP to establish the link; the link subsequently is broughtdown when no activity is detected within the preconfiguredtime.

Page 39: ACP Functional Description Manual.pdf

ACP Functional Description, May 1998 31

X.25 Dial In

This feature allows ACPs with internal modems to automati-cally establish an X.25 connection to another ACP or X.25packet mode device via the public switched telephone network(PSTN).

With internal modems, the ACP can be configured torecognize the mode of operation, can receive a call to activateor dial up a connection, and then disconnect after a specifiedperiod of inactivity.

The user specifies the handshake type and speed, timeoutdelay, how many times the ACP should attempt to connect to adestination, and the inactivity period that triggers automaticdisconnection of the dial-up connection. This feature can beused to back up dedicated ACP X.25 links.

X.25 Multipoint Support

Although the X.25 LAPB specifies point-to-point, full-duplexconnections, users can interconnect ACP nodes using amultidrop topology whenever it offers better cost/performancecharacteristics. When interconnecting ACP nodes in this

manner, one ACP X.25 port assumes a master role, polling allthe ports of other ACPs configured for this mode of operation.

The multipoint connection is totally transparent to all accessprotocols and routing functions supported by the ACP. TheACP modular software architecture allows the networkadministrator to select the link level protocol suitable for thedesired physical connection. While LAPB is used fortraditional point-to-point connections, SDLC is used instead asthe underlying link level for multipoint operations. The X.25packet level fully supports either link levels, providing atransparent physical environment to the terminal operator.

The multipoint support allows you to economically expandyour network by adding ACPs to both ends of an existingSDLC leased line, or by using current multipoint facilities todeploy a switching network. Some of the benefits are:

� Reduced number of leased lines.

� Use of existing multidrop lines to merge async, SNA, BSC,and X.25 traffic.

� One modem per multidropped node, instead of two.

PDN

V.25 bis- or

Terminal A

Link 1

Link 2

X.25 Host

X.25 Dial Out PSTN

Figure 12. X.25 Dial Out and Dial In — Alternate Path Applications

Hayes-compatible

PDN

��������

Link 1

Link 2

X.25 Host

X.25 Dial In with internal modems PSTN

ACP 50

ACP 50

Page 40: ACP Functional Description Manual.pdf

ACP Functional Description, May 1998 32

Figure 13a depicts a standard setup for an X.25 network carry-ing async traffic to a Tandem host, and a parallel SNA networksupporting the SNA traffic to the IBM host.

Figure 13b depicts how these two separate networks can bemerged to carry both SNA and async traffic using ACP multi-protocol capability.

Figure 13c shows how ACP multipoint capability reduces thenumber of modems and synchronous links.

a) Traditional Multidrop Environment at a Two-Host Site

b) X.25 Star Network using ACP Multiprotocol

IBM Host

Figure 13. The ACP Multiprotocol and Multidrop Solutions

FEPModem

SNA ClusterController

SNA ClusterController

SNA ClusterController

TandemHost

AS

SW/AS

AS

Multi-drop S

DLC

Line

Site A

Site B

Site C

Site A

Site B

Site C

X.25

AS

Site DX.25

X.25

IBM Host TandemHost

X.25

Site A

Site B

Site D

Site C

Capability

SNA CC SNA/SW/AS

c) Multidrop Network using ACP Multiprotocol and Multipoint Capability

X.25

Site A

Site B

Site D

Site C

SNA CC SNA/SW/AS

X.25

X.25 X.25

SD

LC Links w

ith X.25 P

acket Level

IBM Host TandemHost

Page 41: ACP Functional Description Manual.pdf

ACP Functional Description, May 1998 33

DSP Support

Why Bisync?

User communities require their networks to comply with net-work conventions that are not vendor-specific, such as theX.25 interface and other protocols that fit in the Open SystemsInterconnection (OSI) network model. The ACP also supportsa vendor-specific 3270 Bisynchronous Communication (BSC)access to allow the user to deploy hybrid networks offering thebest of both worlds. Such networks combine the openness ofX.25 with BSC access, providing the user with a wealth ofapplication software and equipment available from IBM.�

In August, 1981, Telenet, TransCanada Telephone, and Tymnetagreed upon a common end-to-end protocol, the 3270 DisplaySystem Protocol (DSP), that defines how BSC 3270 data ishandled across an X.25 network. In 1983, an update to thisstandard was created, and called Display System Protocol II(DSPII). The ACP’s DSP module conforms to the mandatoryrequirements of the updated specification.

For both 3270 point-to-point and multipoint environments, theuser may use a packet switching network for data transferinstead of leased lines. This capability provides distinct advan-tages to the user:

■ Simplified physical installation because the number of re-quired leased or dial-up lines needed for each cluster con-troller is reduced since they can be replaced with a singleaccess link from the ACP to the PDN.

■ Reduced cost as PDN charges are based on use rather thanconnection time.

■ Increased reliability as the ACP provides multiple, alternateroutes to a host destination.

■ Reduced cost and management overhead by combining3270 BSC traffic with other protocols, such as X.25, SNA,and async.

DSP within the X.25 Network

The DSP module allows up to 64 3270-type control units withattached devices to communicate in a multihost environmentthrough an X.25 network. This mode allows devices attachedto the control unit(s) to establish independent virtual circuits/sessions to the host. In this way, devices on the same controlunit can access different host computers and applications.

ACPs with the DSP module allow the attachment of one ormore 3270-type control units, which in turn attach display ter-minals and printers. Following the BSC protocol, the DSPmodule polls each attached control unit. A control unit trans-mits data to the ACP in the form of 3270 data blocks. The DSPmodule converts the data blocks into X.25 packets, and trans-mits the data through the X.25 packet switching network. Atthe other end, the host DSP process converts the received X.25

packets into 3270 data blocks and forwards them to the hostcomputer applications (see Figure 14).

X.25 X.25

ACP Terminal

Terminals

Control

and Printers

Front EndProcessor w/

BisyncData Blocks

PacketsPackets

PAD (TPAD)

Units3270

Data Blocks

DSP Software

X.25

Bisync Host

FEP

Figure 14. DSP Operation in a PDN

The DSP processing activity is transparent to the user, appear-ing as a direct connection to the host computer. In addition, allpolling and related activity is handled locally and adds noadditional overhead to the network: the ACP’s DSP modulepolls its attached control units, and no polls are passed throughthe network. The user may attach control units to the ACPpoint-to-point (one control unit per bisync port) or multi-dropped (two or more control units per port).

Connection Methods

The DSP module allows the user to take advantage of fourconnection request modes (CRMs).

CRM Type 1, referred to as fixed class, replaces dedicatedline applications. The ACP provides the line number, CU ad-dress, and device address in the call request packet to the hostDSP software. The host DSP software maps the control unitand devices to a fixed location.

CRM Type 2, referred to as specific class, is similar to fixedclass in that it replaces a dedicated application, but the CUaddress and device address in the call request packet can bemapped to a different CU and device by the host DSP soft-ware.

CRM Type 3, referred to as non-specific class, is used in ap-plications where there is a larger number of control units/de-vices contending for a limited number of configured controlunits/devices at the host. The ACP provides the CU and device

Page 42: ACP Functional Description Manual.pdf

ACP Functional Description, May 1998 34

addresses, as well as the application ID in the call request tothe host DSP software.

CRM Type 4, referred to as the associated class, is used toattach printers. This is accomplished by the host DSP softwarereturning a unique four-byte identifier that the ACP uses toconnect the printer.

Connection request modes 1, 2 and 3 are the most commonmethod of attaching 3x7x controllers (e.g., 3174 and 3274) anddevices such as 3178, 3179, 3180, 3191, 3275, 3276, 3277,3278, and 3279.

In addition to the four CRMs, the ACP allows the attacheddevice to take advantage of two call methods: autocall andnormal. When configured for autocall, the ACP automaticallyinitiates calls to the host. Should the host be unreachable, theACP will periodically retry.

With the normal connection method, the user initiates the callby selecting the host application from the Application Selec-tion menu displayed on the terminal screen. Upon selection,the user may then choose a printer from a similar menu. Callsare cleared by the user via menu selection.

Monitoring Commands

The monitoring functions of the DSP module provides a seriesof commands that let the user obtain status information aboutthe ACP, control the general operation of control units anddevices, and troubleshoot the system while it is operating. Theuser invokes monitoring commands by using the ACP’s Sys-tem Manager (SYM) software module. Typical commandsinclude the status command, down command, and up com-mand.

Trace Functions

The DSP module’s trace function collects the 3270 data blocksbeing processed by the DSP module and sends them to theTRACE software module, where they are formatted for review.The Trace function monitors data blocks traveling in bothdirections through the network, that is, toward the host com-puter and toward bisync devices attached to the ACP.

Page 43: ACP Functional Description Manual.pdf

ACP Functional Description, May 1998 35

Frame Relay Support

The ACP 10, 50, or 70 can be equipped with a frame relaysoftware module to provide Frame Relay Access Device(FRAD) functionality when connected to a frame relaynetwork. Deploying ACPs as FRADs allows users to realizethe benefits of frame relay services, such as cost savings andperformance improvements.

ACPs equipped with frame relay also provide frame relayswitching: the transport of async, SNA, and X.25 data viaframe relay network services. This is achieved by firstencapsulating these access protocols using the LAPB X.25protocol, which acts as a transport layer to provide SVCfunctionality through the frame relay network. Since framerelay networks are typically PVCs (Permanent VirtualConnections), this implementation ensures that no connectivityis lost between X.25 and frame relay networks. For example,an async device can communicate with an X.25 host, or anSNA cluster controller can communicate with QLLC hostsusing a frame relay network. Figure 15 illustrates connectivitybetween � 3270-type controllers and IBM host mainframes#1 or #2; between � asynchronous ASCII devices andasynchronous or X.25 hosts; and between � frame relaygateway devices or ELX using RFC 1490.

LMI

The FR module Local Management Interface (LMI) supportsthe ANSI and ITU standards (T1.617 Annex D and CCITTQ.933 Annex A)* and the “GO4” specification authored bythe Group of 4. The LMI implements line monitoring andstatus reporting for frame relay PVCs.

DTE and DCE Interfaces

The ACP frame relay module offers both a DTE interface, toallow connection to public or private frame relay networkservices, and a DCE interface, to allow connection to framerelay-native devices, such as bridges and routers. Bycombining DCE and DTE interfaces in the same ACP, the usercan concentrate several frame relay DTE devices onto one ormore frame relay networks._____________________________________* Available in software Versions 1.10 , 2.04, and later.

Parameters and Timers

All the following frame relay link level parameters are sup-ported, and are individually soft configurable on each link:

Host

3274

CRT

Gateway

IBM

X.25 Host

Async

LAN

LAN

MainFrame

Frame

Frame Frame

Relay

Relay Relay

QLLC

3270/3770ACP 50 ACP 50

Figure 15. ACP Frame Relay Support — Sample Application

FrameRelay

� � �

#2

IBMMain

Frame#1

SDLC

SDLC

ACP 50

ACP 70

FrameRelay

Frame�����

Page 44: ACP Functional Description Manual.pdf

ACP Functional Description, May 1998 36

GO4 ANSI Description

nT1 T391 Polling Interval. Defines how often,in seconds, the ACP sends statusinquiries to the network.

nT2 T392 DCE Timer 2. Defines the maximumnumber of seconds the DCEexpects between DTE polls.

nT3 – DCE Timer 3. Defines the time, inseconds, for the DCE to accept nN4polls.

nN1 N391 Full Status Request Frequency.Defines the number of status inquirymessages it will send to the networkbefore it requests a full statusmessage from the network.

nN2 N392 Threshold Number of Errors.Defines how many errors mustoccur within an nN3 window beforethe link enters an error state.

nN3 N393 Number of LMI Events. Defines thenumber of consecutive LMI eventsrequired to clear the link from anerror state.

nN4 – Maximum Number of Polls. Definesthe maximum number of polls theDCE will accept from the DTE withinthe nT3 window.

Outbound Congestion Control

BECN Reception

Upon reception of a frame with the BECN (Backward ExplicitCongestion Notification) bit set to one, the ACP forwards theframe unchanged, throttles the output rate from Be (excessburst rate) to Bc (committed burst rate), and sets the FECN(Forward Explicit Congestion Notification) bit to one in outgo-ing frames on the same DLCI. If the congestion persists andthe ACP receives N consecutive frames with the BECN bit setto one, the output rate is first reduced to 87.5% of Bc, then to50% of Bc if the congestion still persists.

Congestion Recovery

Congestion recovery occurs when N/2 frames are receivedwith the BECN bit cleared. The output rate is then raised to thenext upper rate (i.e., from 50% of Bc to 87.5% of Bc to Bc thenBe). The FECN bit in the outgoing frames will be cleared onlywhen the output rate is back to Be.

Inbound Congestion Control

FECN Transmission

Upon receipt of a large amount of data on a DLCI bigger thanthe configured receiving buffers threshold, the ACP forwardsthe frames with the FECN bit set to one, and sets the BECNbit to one in the frames returned to the sending device. Howev-er, it does not reduce the data output rate of the outboundDLCI. If the amount of data received overflows the receivingbuffer, the ACP discards frames as follows:

1. Discards the current received frame if the DE (DiscardEligibility) bit is set to one.

2. Discards frames from the buffer with DE bit set to one.

3. Discards the last frame received with or without DE bit setone.

When the ACP’s DCE interface receives data over the BCinput rate, the ACP forwards the frame with the DE bit set toone.

Congestion Recovery

Congestion recovery occurs when the receiving buffer thresh-old is below the configured limit. The ACP will cease settingthe FECN and BECN bits in the forwarded and outgoingframes.

NOTE: The ACP congestion control mechanism —out-bound and inbound—can be disabled via softwareconfiguration.

Frame Relay Applications

FRAD

ACP FRADs (Frame Relay Access Devices) encapsulateX.25, asynchronous, SNA, bit-oriented, and byte-oriented datain frame relay packets for fast transmission to each other overa frame relay backbone network. When equipped with ELXcommunication modules, ACP FRADs are also capable ofrouting IP LAN traffic over a frame relay WAN by using theRFC 1490 standard to encapsulate the IP datagrams. The com-bination of the frame relay component and the feature-richmultiprotocol PAD in the same ACP offers a unique multipro-tocol FRAD Concentrator.

Frame Relay Concentrator

This application provides the end user with the capability toconcentrate multiple frame relay DTE devices, such as routers,bridges and FRADs, to one or more frame relay networks.

Page 45: ACP Functional Description Manual.pdf

ACP Functional Description, May 1998 37

X.25 SVC Over Frame Relay PVC

The unique implementation of frame relay in the ACP plat-form allows the user to take full advantage of X.25 switchingwhile using a frame relay PVC network.

You can assign each X.25 component to either a physical portor to a frame relay DLCI. All X.25 components are intercon-nected through the network router (netmap/netroute), whichmeans that you can switch data from components such as ITI,SNA, TPP, or X.25 to any other X.25 component whether it isusing a physical port or an X.25 frame relay DLCI.

The network router allows the user to specify one or more al-ternate routes to maintain service to users when frame relaylink failures occur. An alternate route is also used when theprimary route has no available logical channels or when thefinal destination cannot be reached.

Figure 16 illustrates how an ACP can support access by sever-al proprietary protocols—here asynchronous, SNA, andX.25—through the frame relay network. Multiple protocolsfrom site D send data to the complementary sites A, B, and Cwhich in turn can send data to site D and to each other via siteD.

The user may also specify a call-sharing group, consisting oftwo or more frame relay links. The ACP will then balance thecalls among all the links in the group.

Because async and SNA protocols are transported over X.25LCNs, both protocols use the above features to retain the ex-tensive PAD functions (e.g., VLU and PU switching) andshare the same DLCI.

Monitoring Commands

The monitoring functions of the frame relay module allow theuser to obtain status information about frame relay PVCs andframe relay interfaces; to enable and disable frame relayPVCs; and to troubleshoot the network while it is operating.

Trace Functions

The trace function of the frame relay module collects data onthe module’s operation. The frame relay module sends tracedata to the ACP’s TRACE software module, which formatsand stores the information for review.

FRDTE

FRDTE

FRDTE

SNA/

X.29/

QLLC/

FRDCEX.25

SNA

X.25

FRDCE

DLCI A

DLCI B

DLCI C

FR ACP

FR ACP

FR ACP

FRDCE

X.25

SDLC

X.25Async

SNA

SNAHost

Host

Host

SITE C

SITE B

SITE A

Frame RelayNetwork

X.25DTE

X.25DTE

X.25DTE

FRDTE

X.25DTE

X.25DTE

X.25DTE

DLCI ADLCI B

DLCI C

FRDCE

ITI

SNA

X.25

Async

SNA

SNA

Figure 16. Multi-protocol ACP and Frame Relay Network

SITE D

A

B

C

Page 46: ACP Functional Description Manual.pdf

ACP Functional Description, May 1998 38

Asynchronous Support

The Interactive Terminal Interface (ITI) module supportsconnections to both asynchronous terminals and host computerasynchronous ports. All features listed here are enabled byconfiguring the ITI-related files in the configuration database.

Device Connectivity FeaturesPhysical Attachment

� Direct attachments via EIA control or 3-wire only.

� Remote attachment via leased line modems or switchedline modems, external or internal.*

� User-definable EIA handshaking to facilitate the attach-ment of terminals, PBXs, POS, etc.

� Up to 100 KB of data buffer memory to optimize block-mode transmissions and high-speed async devices.

� Data rates from 50 bps to 115.2 kbps.*

� Autobaud/autoparity detection from 300 bps to 38.4 kbps.*

� Configurable maximum permissible autobaud speed on aper-port basis.

� Character code support of 5, 6, 7, 8, or 9 data bits.*

� User-selectable number of stop bits (0, 1, or 2).

� Configurable echo mask (sequences).

� MINITEL terminal support.

� Access Control.

� Ports may be classified for public, group, or private access.

� Class of Service password.

� User name and password.

� Additional security provided with an automatic callbackmechanism using dial-up modems.

� NUI support.

� Closed User Group (CUG) support.

� Access Messages.

� Configurable connect banner may display node and accessport identification, time and date notification, and releasenumber of resident operating code.

� Network bulletins may be displayed in Class of Servicemessages.

� Temporary shutdown notices may be dispatched in Out ofService messages.

� Broadcast messages display real time events.

* Platform dependent.

Host Connectivity FeaturesPhysical Attachment

� Dedicated.

� Pulsed ring (not available on ACP 10).

� Constant ring.

� User-definable handshake for universal host attachment.

� Sign-on.

� Host port activates baud rate detection when a call is re-ceived.

� Speed can be made to match the throughput class of incom-ing calls.

� Autocall character strings can be configured.

� Caller can be prompted for a class of service.

� Caller can be prompted for a preferred X.3 profile.

� Access Control.

� Class of Service rotaries may be defined.

� Multiple ACPs configurable as a single async rotary.

� Ports may also be individually selected.

� Closed User Group IDs may be assigned to each port.

� Reverse charges may be accepted.

� Flow control parameter negotiation supported.

Access Messages� Class of Service messages.

� Out of Service messages.

Other Features� Generates a Break signal or a configurable character string

upon receipt of an Interrupt packet.

� Call clearing uses Invitation to Clear procedures to avoiddata loss.

Routing� Supports “off-net” (local) port-to-port switching.

� Incoming call routing to ports/rotaries can be set by ����

��� ���� ���� �� �� ��������� ��� ������ �� �� ���������

� �� ��� ����� � ���� ���� ��

� Incoming data may be copied to another local device or toa remote destination via the copy function. This allows therouting of reports to a shared printer and intra-networkelectronic mail.

Page 47: ACP Functional Description Manual.pdf

ACP Functional Description, May 1998 39

X.3 Support

In addition to conforming to the mandatory 1988 CCITT X.3recommendation, the ITI module supports both mandatory andoptional X.3 values for all 22 parameters, as well as anadditional set of 10 parameters to provide more flexibility.This allows most end-user installations to fully use thecapabilities of packet switching without compromising theoperational procedures already in place.

X.3 (CCITT) Parameters Supported1. PAD recall2. Echo3. Forwarding characters4. Idle timer5. Flow control device6. Service signals7. Break action8. Discard output9. CR padding10. Line folding11. Speed12. Flow control PAD13. LF insertion14. LF padding15. Edit16. Character delete17. Line delete18. Line display19. Editing signals20. Echo mask21. Parity treatment22. Page wait

Extended X.3 Parameters1. Forwarding character 12. Forwarding character 23. Output pending timer4. Interval forwarding timer5. Horizontal TAB padding6. XON to device

7. XOFF to device8. XON to PAD9. XOFF to PAD10. Forwarding on character count

X.3 Mapping

The ITI module allows the terminal operator to select an X.3version for each call to access older generation X.25 networksand different types of X.25-based equipment. For example, aterminal operator calling a host programmed for TELENET-type support would use the X.3 TELENET version rather thanthe extended X.3 version.

The ITI module supports some major X.3 network imple-mentations as well as X.3 profiles of other PAD vendors tofacilitate phasing in the ACP’s extended features.

Profile Support� CCITT profiles 90 and 91.

� 16 additional, configurable, 32-parameter profiles.

� A profile can be preassigned or the terminal operatorprompted for one during sign on.

� Numeric or alphanumeric profile identifiers.

� X.3 profile mapping; for CCITT ’76, ’80, ’84, ’88,TELENET, DATAPAC and TELEPAC networks and otherequipment, such as DYNAPAC and AMDAHL.

� User may review alternative profiles without affecting hisown X.3 parameter settings.

� Automatic storage and recall of X.3 parameter settingsbetween sessions eliminates the need to readjust parame-ters following each session.

Flow Control� In-band flow control as defined by X.3 profile; XON-

XOFF characters are user defined via the extended param-eters.

� Out-of band flow control via user defined secondary EIAsignals. Either DTR or RTS may be used.

� Definable minimum and maximum buffer size and flowcontrol threshold on a per-port basis.

Page 48: ACP Functional Description Manual.pdf

ACP Functional Description, May 1998 40

X.28 Support The ITI module supports all eight X.28 commands as per theCCITT 1988 recommendation. These commands allow theuser to place calls, review and alter X.3 parameters, requeststatus of an X.25 logical connection, etc. In addition, anextended X.28 support allows the user to invoke an additionalset of 19 commands. This extended support enhances thefunctionality of the ACP while providing the user with afriendlier interface.

As in the X.3 implementation, the ITI module allows theterminal operator to select one of the preprogrammed X.28command sets. This enables the operator to have a commoncommand set compatible with equipment already installed andin use.

X.28 (CCITT) Commands Supported� stat

� clr

� par? (parameter list)

� set (parameter:value)

� set? (parameter:value)

� prof (identifier)

� reset

� int

Extended X.28 Command SetCommand Function

c <addr> Place a call to the specified address.

call Retry a previously cleared call withoutrekeying.

copy Establish a secondary virtual circuit to duplicateall incoming data to a second device.

copyclr Clear the copy command.

help Invoke a resident help function.

iclr Send an invitation to clear.

intd Simulate a Break key; for devices without one.

logoff Hang up a modem or exit to idle state.

npar Set parity in network bound data.

rpar Read remote PAD parameters.

rprof Select a remote X.3 profile.

rset Set remote PAD parameters.

rset? Set and read remote PAD parameters.

send Send data to a remote user while in session.

tactt Invoke a resident data generator; for testing theterminal.

tact Invoke a resident echo facility; for testing theconnection.

type Send data to a local device.

X3type Invoke the X.3 emulation and mappingfunction.

X28type Invoke the X.28 emulation and mappingfunction.

X.28 Mapping

The ITI module supports an X.28 mapping function toemulate, within certain limitations, the X.28 command set ofcertain public data networks and other PAD implementations.Emulation for the most commonly used commands is availablefor CCITT ’88, TELENET, DATAPAC, TELEPAC networks,AMDAHL and DYNAPAC PAD equipment.

In addition to the preprogrammed commands, the user mayredefine the syntax of certain X.28 commands.

Call Request Methods

There are four methods of requesting a connection to adestination:

� Long form method.

� Abbreviated (short form) method.

� Direct (Autocall) method.

� PVC (Permanent Virtual Circuit) method.

Long Form Method. The ITI module supports the X.28call request command, commonly referred to as the long formmethod, as it requires the user to specify the destinationaddress, the facilities required for the call; e.g., reversecharging, and possibly a call-user-data-string.

Facilities supported Comments

Packet negotiation Asymmetrical sizes are supported.

Window negotiation Asymmetrical sizes are supported.

Throughput class Asymmetrical class is supported.

Reverse charge May be enforced or on demand.

Closed user group May be enforced or on demand.

Fast select restricted Up to 124 user-specifiable bytes maybe transmitted

Fast select Up to 124 user-specifiable bytes maybe transmitted.

Charging information To request PAD billing information atend of (local) session.

Priority call For the Canadian DATAPAC network.

RPOA From a pre-configured list of carriers.

NUI Network User Identification

Abbreviated Calling Method. In addition to the longform method, the ITI module supports an abbreviated methodof requesting a connection, using preconfigured mnemonics.

� The mnemonics can be up to 10 alphanumeric characterslong.

Page 49: ACP Functional Description Manual.pdf

ACP Functional Description, May 1998 41

� There are two levels of mnemonics: private mnemonics canbe used only by users assigned a certain class of service,while public mnemonics can be used by any user not re-stricted to using abbreviated method of calling.

� Should the preconfigured destinations support subaddress-ing or require different call-user-data content to select ap-plications, the mnemonic addressing method allows theuser to specify these fields when placing a call. This fea-ture relieves the administrator from having to preconfigureeach calling combination—an otherwise tedious andmemory-inefficient exercise.

� Each mnemonic can be configured to invoke a call requestthat includes all the fields of the long-form connect requestcommand.

� The ACP can be configured to automatically send a hostlogon screen upon call establishment.

� The ACP can be configured with up to eight destinationaddresses associated with each mnemonic for automaticcall forwarding. If the primary destination is unreachable,the ACP will automatically attempt to reach other address-es in the list.

Examples:

Mnemonics Possible Use

Inventory To call the “inventory” computer.

Inventory*password Same as above, with a logon passwordin the call-user-data field.

Gateway*12 To call port 12 at destination “gateway.”

Direct Method . The third method is referred to as thedirect or autocall method. Once the user is identified (if accesscontrol is configured), the ACP will automatically place a callto a predefined destination upon completion of the EIAhandshake, or upon detecting data activity.

PVC Method . The fourth method is using PermanentVirtual Circuits (PVCs) in a network. When configured forPVC operation, the connection will be attempted uponcompletion of the local EIA handshake.

User-Defined Commands

The ITI module allows the System Administrator to predefinecommands that can be invoked by the user in command mode.This feature allows commonly used X.28 commands to beinvoked using a mnemonic rather than the cryptic, CCITTcommand style. It may also be used to support a non-Englishlanguage command set, and possibly to mimic othercommands that the user is familiar with on other PADequipment. A mnemonic can also be configured to representmultiple X.28 commands.

Examples:

Possible Mnemonic X.28 Command Invoked

Echo Set 2:1

Echo-off Set 2:0

Edit Set 15:1

Bye Clr

The mnemonic can be configured to represent multiple X.28commands. In the following example, the mnemonic “mail”will set the user X.3 parameters and will cause the ACP toplace a reverse charge call to a destination on the TELENETpacket data network.

Mail Set1:1,2:1,3:2,22:241\R-311021300009

Help Facility

To assist users that sign on to the asynchronous ports, the ITImodule offers an on-line “help” facility.

Help Functions Description

X.3 Lists the parameters by their referencenumber and their function.

X.28 Lists the commands and their functions.

Profiles Lists the different profiles.

Mnemonics Lists both call and command mnemon-ics.

RPOA Lists the carrier names and codes.

Service Signals

The ITI module supports all service signals called for inCCITT ’88. The user may also, via the X.3 parameter 6 (ser-vice signals), invoke the extended mode whereby text messageis printed along side the cause and diagnostic codes in resetand clear service signals.

� In addition to the prescribed service signals, the networkadministrator can define several messages for transmissionto users upon sign-on.

� If necessary, the CCITT-defined X.28 command prompt (*)may be changed to any string of characters.

� A broadcast message may be transmitted at any time to allACP active users.

� The ACP may be configured to transmit a local accountingservice signal to the async device at the conclusion of thecall. The service signal will include the user ID, destina-tion address, time and duration of the call, number of pack-ets, segments and characters transmitted and received,facilities negotiated, etc.

Page 50: ACP Functional Description Manual.pdf

ACP Functional Description, May 1998 42

X.29 Support

The ITI module’s support of X.29 allows remote hostcomputers to read and set the ACP parameters. The ITImodule also supports the reselection message defined inCCITT ’88. The supported messages are:

� Set

� Read

� Set and read

� Parameter indication

� Invitation to clear

� Indication of break

� Error

� Reselection

Host Computer Support

X.29 Conversion. The ACP can be used by attached asyncdevices to generate X.29 messages. For example, an asynchost computer may dynamically disable remote echo forcertain data entry fields (e.g., a logon password). In thisenvironment, the host can be programmed to prefix certainfield prompts with a predefined command that makes the ACPgenerate an appropriate X.29 message to the remote ACP. Inthe above example, this message can cause echo to be disabledat the remote ACP for that particular field.

Automatic Parameters Setting. When the ACP is usedas an async host’s front end, it can be configured to downloada parameter set command to ensure that the calling party’s X.3parameters are compatible with the application being accessedon the host. Downloading of national parameters, including anational marker, is supported.

Invitation to Clear. When used as a host front end, theACP can be configured to clear a connection using theInvitation to Clear method.

X.29 Reselection. This feature allows the ACP to beeffectively used in X.25 networks equipped with applicationrouters or security logon servers. In this environment, typicallyall asynchronous users who log on via the ACP will first bevalidated by the application router or logon server. Uponsuccessful validation, the router/server would instruct the ACPto connect the user to the appropriate network destination viaan X.29 reselection message.

Alternative Host Selection . The ACP can be configuredwith alternate called addresses to be tried in sequence if thecall request to the primary called address fails. The ACP canalso be configured to inform the terminal operator of eachfailure to connect in the alternative host selection process.

Asynchronous Out-dial . The ITI module’s out-dialfeature can significantly reduce long distance calling costs.This feature enables users to access hosts outside theACP-based network with a local call from the nearest ACPPAD via an async modem. The ITI module achieves this byprefacing the X.121 address of the gateway PAD with themodem initialization sequence ATDT.

X.121 Support � The ITI module fully supports recommendation X.121 per

CCITT ’88. In doing so, the ACP allows the user to callany destination accessible via one or more PDNs. All call-ing methods described previously allow the user to call anyaddress up to 15 digits long.

� When originating a call, the ACP can be configured to in-sert the port ID in the calling address field for accountingor identification purposes.

� For incoming calls, the ACP can route calls to any portbased on any number of sub-address digits. This allows theACP to be compatible with networks that support a vari-able sub-addressing field.

Page 51: ACP Functional Description Manual.pdf

ACP Functional Description, May 1998 43

SNA Support

Why Combine X.25 and SNA?

User communities require their networks to comply withnetwork conventions that are not vendor-specific, such as theX.25 interface and other protocols that fit in the Open SystemsInterconnection (OSI) network model. The ACP also supportsa vendor-specific SNA access to allow the user to deployhybrid networks offering the best of both worlds. Suchnetworks combine the openness of X.25 with SNA access,providing the user with a wealth of application software andequipment available from IBM.�

Deploying an ACP-based X.25 network allows the user torealize significant cost savings. Such a network is capable ofsupporting multi-vendor protocols that would otherwiserequire separate, distinct networks.

Depending on the size of the network, ACPs can providerouting, concentration, and access functions. Access to IBMmainframes, mid-range computers, and terminal controllers iscarried out in either native SDLC or X.25 mode.

To operate IBM equipment in X.25 mode without ACPs, theuser may require costly, add-on devices or additionalsoftware—with limited functionality and incremental costs atboth the host and terminal level—only to face performanceissues on the processing equipment.

ACPs offer an optimum solution by providing low-cost accessto SDLC equipment and by assuming the processing burden ofX.25 protocol enveloping, routing, and error checking withoutaltering existing IBM equipment or software code. ACPs alsorelieve the IBM host of switching functions by carrying out theswitching locally at the Logical Unit level, a highly desirablecapability in multi-host environments.

Alternatively, if public networks are not available oreconomical, private networks can be built using ACP units asconventional networking multiplexers. In either case,connections to the IBM system can be X.25, using X.25adapters, or SDLC via standard IBM communication adapters.

Figure 17 on page 44 illustrates connectivity between �

3270-type controllers and IBM host mainframes #1 or #2; �

between 5250-type controllers and IBM System 34, 36, 38 orAS/400 hosts; � between a 3777 and IBM host #1; �

between ASCII devices and X.25 hosts using X.29 protocolsharing the same line facilities; and � between a 3270-typecontroller and IBM host mainframe #3.

ACP TPAD and HPAD Value-addedEmulation

When connecting IBM equipment in their native SDLC mode,ACPs convert SNA to X.25 through an emulation technique.In this mode, PADs are required at both host and terminalends, and are known as Host PADs (HPADs) and TerminalPADs (TPADs). All polling takes place between the ACPacting as the TPAD and the SNA cluster controller. The HPADhandles responses to host polling locally to avoid timeouts andsafeguard the network bandwidth.

In addition to emulating SNA session activation to establishSDLC access with the cluster controller, ACPs emulate theSystem Service Control Point (SSCP) functions to allowindividual LUs to access multiple hosts and applications. Thisbypasses the complex and cumbersome cross-domain SNAsession establishment that would otherwise be required at thehost front end. This device segregation also allows the user toexpand or reconfigure the terminal base without affecting thesetup of host terminal tables.

Group poll which optimizes the performance of the ACP issupported only on the H-pad.

Automatic Error Recovery

Interconnected HPAD and TPAD ACPs will recover from mosterrors occurring in the network. If, for example, an X.25 linkfails, all SNA sessions carried over that link will be cleared,the permanent virtual circuits reset, and the calls re-establishedover an available alternate link and routed to the same PU/LUas before.

When operating in VLU mode, the SNA module also numbersdata packets sequentially to recover from loss or duplicationdue to problems such as a virtual circuit reset or a call clearingand reconnecting. Data is kept at the sending end until thereceiving end acknowledges receiving it. If noacknowledgement is received after a certain number of polls,the call is cleared. If the reconnection fails after a number ofretries, both sides of the connection will go back to the statethey were in before the connection was initially placed.

PU and LU Switching

The SNA module uses QLLC protocol* to route SNA trafficfrom an IBM PU2 to an IBM host over an X.25 link. This

Page 52: ACP Functional Description Manual.pdf

ACP Functional Description, May 1998 44

IBM

PDN

��

IBMMain Frame

Host #1

IBMMain Frame

Host #237x537x5 3274IBM3777

IBM5294/5250

AsyncIBM3274

IBMSYS 34/36/38 PC CRT

Tandem Host

Figure 17. ACP SNA Support—A Sample Application.

X.25 X.25

X.25

SNA3270/3770

5250 SNA

X.25(QLLC)

X.25(DSP)

X.25

NCP NCP/NPSI

� � � �

��

IBMMain Frame

Host #337x5w/DSP

IBM3274

or AS/400

ACP 50

ACP 50

ACP50

mode is referred to as PU switching, as all LUs related to a PUshare the same physical and logical path (i.e., one SVC) to thehost. Up to 64 PUs can be supported by one ACP.

The SNA module can also be configured to allow individualLUs off the same PU to establish independent sessions, amode referred to as LU switching. Each LU essentially usesone X.25 SVC to carry its own session. To use this feature, anACP HPAD is required at the IBM host computer to supportthe necessary protocol from the ACP acting as a TPAD.

3270 SNA Support

ACPs configured as TPADs convert 3270 SNA/SDLC datastreams to CCITT X.25 packets for transmission across a PDNand interface to IBM mainframes. As HPADs, they can also beused as an alternative to IBM’s Network Packet SwitchingInterface (NPSI).

� ��� �� ��� ������ ��� �� ��� ������� ���������� �������

3770 SNA Support

The extended feature “auto connect” provides conversion for3770 SNA/SDLC data streams to CCITT X.25 packets fortransmission across a PDN. This 3770 support can be used inaddition to 5250 and 3270 SNA support.

5250/5294/5394 SNA Support

ACPs configured as TPADs convert 5250 SNA/SDLC datastreams to CCITT X.25 packets for transmission across a PDNand interface to IBM System 34/36/38 and AS/400 hostcomputers. ACPs can simultaneously support IBM5250/5294/5394 cluster controllers. As HPADs, they can alsobe used as an alternative to IBM’s X.25 host adapter.

Connections to a Host

All X.25 call connection features are available to ACP withSNA capability. These features are described earlier in theACP X.25 support section.

Page 53: ACP Functional Description Manual.pdf

ACP Functional Description, May 1998 45

Display Stations

Display stations can connect to a host in three different ways:via menus that contain a directory of application names orphone numbers; automatically to predefined destinations forconvenience or security; or over permanent virtual circuits(PVC). A sample of the fully-configurable host selection menuis shown in Figure 18 below.

BBBBBBBBBBBBBBBBBB BANNER BBBBBBBBBBBBBBBBB

<< Call Clear Message >>

HOST SELECTION MENU

A. HOST1B. SYST/38C. ABCdef

S. SIGNOFFX. EXIT TO HOSTY. PRINTER CONNECTION MENU Z. PRINTER DISCONNECTION MENU

PROMPT _

Figure 18. A Host Connection Menu

Printer Stations

Printer stations may be connected automatically by the host orvia menus displayed at each cluster controller’s “privileged”display station. Autocall connections from the host allow anadditional level of security and automatic batch printing afterworking hours. A sample of the fully-configurable printerconnection menu is shown in Figure 19.

BBBBBBBBBBBBBBBBB BANNER BBBBBBBBBBBBBBB

PRINTER CONNECTION MENU

A. PR555 LU2B. Pclass4 LU5C. 5256class LU10D. 5256class LU9

X. QUIT

PROMPT _

Figure 19. A Printer Connection Menu

Enhanced Security

ACPs offer various security functions to ensure that specificend users only connect to a host using pre-assigned LUs orthat only predetermined hosts are available to them. This is ofparticular importance for host computers that allow dial-inaccess. In addition, selecting “SIGNOFF” from the HostConnection Menu prevents unauthorized use of the network.

Page 54: ACP Functional Description Manual.pdf

ACP Functional Description, May 1998 46

IP Support

The IP module, in conjunction with the ELX CEM/CAM orthe ACP 70 embedded AUI, allows an ACP to function as aTCP/IP router. This, combined with the other ACP-supportedprotocols, eliminates the need for separate networks andseparate hardware.

Available on the ACP 50 and ACP 70, the IP module routes IPdatagrams through X.25 or frame relay networks according tothe routing information contained in the IP headers of thereceived IP datagrams. These datagrams are split into packetsor frames for transmission through the network, andreassembled at the destination ACP into the original datagramwith the appropriate MAC layer and IP addressing intact. Thisprovides a seamless interconnection of LAN users across aWAN. The IP module supports two network links up to2Mbps, and one Ethernet 10Base5 LAN port using 802.3 orEthernet V.2 encoding.

Many large networks are now forced to support separate—anddifferent—network infrastructures for async, SNA, SDLC, andX.25. This, combined with the increasing demand forinternetworked LAN traffic, is making the work of networkdesigners and administrators more difficult than ever before.

Organizations of all sizes are integrating traffic such as async,SNA, X.25, and frame relay on a common WAN to slash costsassociated with operating and maintaining separate networks.Adding IP support to the ACP leverages the available ACPprotocols (SNA, DSP, POS, async, TPP, and FR) to provide anexcellent multiprotocol FRAD or multiprotocol routersolution.

Applications

The following is a list of a few of the most popularapplications that are routed by ELX.

� SNMP. (Simple Network Management Protocol.) TheACP can act as an SNMP agent system, performingnetwork management operations requested by an SNMPmanager at your site. Any of several SNMP managers(e.g., HP OpenView) can be used. SNMP Agent servicesSNMP V1 requests from the SNMP manager, and reportsunsolicited traps to the SNMP manager for pre-configuredACP alarm conditions. Figure 7 on page 23 shows anapplication using SNMP Agent for remote management.

� ��������(Network Terminal Protocol.) TELNETprovides a means for a user to log on to a computer onanother network. Both TELNET Client and TELNETServer are supported.

� TELNET Client—Allows async VT-100 typeterminals to login and establish a TELNET sessionwith a TELNET host server over an IP network. (SeeFigure 20 and Figure 21.)

� TELNET Server—Allows TELNET clients on a LANto login and establish a TELNET session with an X.25host. (See Figure 22 and Figure 23.) TELNET Serveralso allows TELNET clients on a LAN to login andestablish a TELNET session with the ACP SystemManager (SYM), and to trace components to conductremote management and diagnostic procedures (seeFigure 9 and Figure 10 on page 24).

Figure 20. Application Using Remote ACP TELNET Client Support

IPTELNET Server

Async Terminals

ACP 50TELNET Client

ACP 50

PSTN

Page 55: ACP Functional Description Manual.pdf

ACP Functional Description, May 1998 47

Figure 21. Application Using Local Triple-X to ACP TELNET Gateway

IPTELNET Server

ACP 50

Async Terminals

Triple-X PADACP 50

TELNET Gateway

PSTN

Figure 22. Application Using Local ACP Reverse TELNET X.25 Host Server Support

X.25TELNET Client

ACP 50TELNET Server

Host

Figure 23. Application Using Remote ACP Reverse TELNET Async Host Server Support

X.25TELNET Client

ACP 50TELNET Server

Host

Router

Page 56: ACP Functional Description Manual.pdf

ACP Functional Description, May 1998 48

� FTP. (File Transfer Protocol.) Allows the transfer of filesfrom one computer on the network to other computers onthe network. The FTP software component supports theupload and download of ACP code and configuration datafrom a PC FTP client over an IP network (see Figure 8 onpage 23).

� SMTP. (Simple Mail Transfer Protocol.) Allows users tosend mail messages to other mail users on anothernetwork.

� NFS. (Network File System.) A mechanism that allows acomputer to run as a server and make some or all of itsfiles available to remote users.

Figure 24 shows additional examples of applications usingELX/IP operation.

Standards

The IP software module allows ACPs to be fullyinterconnected over a private network, and to interact withother DTE devices supporting the same RFC (Request forComments).

RFC # Description

791 Internet Protocol (IP)

792 Internet Control Message Protocol (ICMP)

826 Ethernet Address Resolution Protocol (ARP)

951,1084 BOOTP Protocol

1042 Standard for transmission of IP datagrams overIEEE 802 networks, using subnetwork access protocol (SNAP).

1055 Transmission of IP datagrams over serial lines(SLIP)

1058 Routing Information Protocol (RIP)

1213 SNMP MiB II statistics

1294,1490

Multiprotocol Interconnect over frame relay (IPover frame relay)

1331 Link Control Protocol (LCP)

1332 Internet Protocol Control Protocol (IPCP)

1356 Multiprotocol Interconnect over X.25 packet network (IP over X.25)

1583 Open Shortest Path First (OSPF)

Routing ProtocolsTo interoperate with other vendors’ LAN-based products, theACP supports the Routing Information Protocol (RIP), whichis the de facto standard used for sending routing informationbetween LAN-equipped nodes in the network. This routinginformation is used to select the best path to the destinationnetwork.

The ACP also supports the Open Shortest Path First (OSPF)routing protocol. OSPF was developed by the InternetEngineering Task Force (IETF) specifically for use in theTCP/IP environment. OSPF is classified as an InteriorGateway Protocol (IGP), meaning that it distributes routinginformation among the routers within an area called anAutonomous System (AS). All routers in the AS run the samerouting protocol, and all maintain an identical database ofrouting information.

ELX Transceivers

Telematics offers third party transceivers to facilitate users ineliminating costly and unwieldy AUI drop cables. Thesetransceivers provide state-of-the-art inexpensive solutions forthin coax (10Base2), unshielded twisted-pair (UTP), shieldedtwisted-pair (STP), and fiber optic LAN Connectivity.

Bandwidth Management

The IP module is always offered with the frame relay module.Together they provide a sophisticated bandwidth managementmechanism for throttling the TCP/IP or other traffic into theframe relay network. The ACP can be configured so that eachof the remote LANs are connected via a separate DLCI. Eachof these DLCIs can have a different “CIR” (CommittedInformation Rate) so that traffic between different destinationLANs and the concentration of other traffic is manageable.

Monitoring Commands

The monitoring function of the IP module allows the networkadministrator or user to obtain a quick status of the networkwith the ping command. Other commands available via thesystem manager (SYM) software module are status command,down command, and up command.

Page 57: ACP Functional Description Manual.pdf

ACP Functional Description, May 1998 49

Frame Relay

or

X.25

X.25

QLLC

3270/3770

Host

Host

Host

Host

3174

3174

3174

ACP 50

ACP 50

Async

3274

AsyncM

ultid

rop

FileServer

LocalUsers

LAN

FileServer

LocalUsers

MailServer

LocalUsers

HostSLIP

SLIP

Modem

Modem

Figure 24. Sample ELX/IP Applications

ACP 50

LAN/WAN Interface Connectivity

The following table lists the LAN/WAN interfaces andconnectivity supported.

Type Description

Supported LANsand LAN Interfaces

Ethernet: AUI/10Base5. Alsosupports 10Base2, 10BaseT,STP/UTP, and fiber via externaltransceivers.

Routed LAN Protocols

IP

RoutingConcurrently

TCP/IP, AS, X.25, SNA, TPP, SLIP,PPP

Frame RelayPerformance

800 frames per second throughput.Assumes system is only routing IPtraffic using RFC 1294 encapsulation.

Routing Capabilities Both static and dynamic routingsupported.

IP Encapsulation IP over Frame Relay RFC 1294 andIP over X.25 RFC 1356.

Packet Performance Packets per second throughput: 500(64 Byte packets using one 256 kbpsX.25 link; RFC 1356; system is onlyrouting IP traffic).

Statistics

The IP module collects statistics on IP, routing, ICMP andEthernet, as described in RFC 1213.

Serial Line Internet Protocol (SLIP)

Mobile IP users, while on the road, can connect to theACP/ELX module via modems and access the resources onthe LANs. The IP module permits a device attached to anasynchronous port of the ACP, either directly or via a modem,to use SLIP to establish a connection to the attached IPnetworks. The IP module conforms to the RFC-1055 for SLIP.

Conforming to RFC-951 and RFC-1084, the BOOTP protocolsupport on the IP module facilitates a device that uses adial-up SLIP connection to the ACP to determine its IPaddress.

Page 58: ACP Functional Description Manual.pdf

ACP Functional Description, May 1998 50

Point-to-Point (PPP) Protocol

Synchronous and/or asynchronous Point-to-Point Protocol,known as PPP, provides an easy and reliable means ofconnecting to TCP/IP based networks (see Figure 25). PPPenables ACPs to communicate with other ACP routers orthird-party routers (that comply with the same RFCs) overwide-area links. Additionally, PPP offers additional benefitsover SLIP for asynchronous dial-up access to the network,such as error detection and authentication.

ACP’s PPP component implements HDLC address/controlfield for error detection and protocol field compression, aswell as TCP header compression, to reduce transmissionoverhead to a minimum. This improves both the throughputand interactive response on typical modem dial-upconnections. In addition, the escape mechanismimplementation allows control characters such as XON/XOFFto be transmitted transparently over the link.

The Link Control Protocol (LCP) is used to automaticallyagree upon the encapsulation format options, handle varyinglimits on sizes of packets, determine when a link is functioningproperly, detect other errors, and terminate the link.

Once the LCP stage is complete, the Internet Protocol Control(IPCP) session begins. IPCP is responsible for configuring,enabling, and disabling the IP protocol modules on both endsof the point-to-point link.

Synchronous PPP is capable of operating across anyDTE/DCE interface (e.g., RS-232, CCITT V.35, and octal

modem). The speeds can be up to 2 Mbps when using theRS-530 and CCITT V.35 links.

IP Transporter

The IP transporter is supported in the IP module through theencapsulation of a wide range of protocols such as X.25, SNA,asynchronous, bisync, third-party bit/byte protocol, SLIP andPPP, over a TCP/IP based wide area network.

The implementation of IP in ACPs (see Figure 26) now offersall the benefits of X.25 while transporting it over a TCP/IPbased backbone network. ACP encapsulates a wide range ofprotocols in X.25 frames which in turn are encapsulated in IPdatagrams for transmission over an IP network. Theconnection between an ACP and the backbone may be viaLAN or PPP synchronous links using RS-232, RS-530, CCITTV.35, or octal modem interfaces. Speeds of the synchronousPPP links may be up to 2 Mbps.

PPP/SLIP/X.25 Gateway

The ACP PPP/SLIP/X.25 gateway provides an alternatemethod for accessing a remote LAN or the Internet with littleor no change to the current X.25 network infrastructure.

The ACP PPP/SLIP/X.25 gateway permits SLIP or PPP usersto dial into their current X.25 network (PAD) and thenestablish a transparent virtual circuit between the PC(PPP/SLIP device) and the ACP gateway (see Figure 27).

ISDN

PC

Async

Third PartyRouter

ACP 50 withinternal dial-up

modem

LAN

PPP

AsyncPPP

SyncPPP

MobileUser

ACP 70

LAN

Dial–upModem

PPP

PPP

Figure 25. PPP Applications

Page 59: ACP Functional Description Manual.pdf

ACP Functional Description, May 1998 51

IP

PC

Async

Cluster

FEP

ACP 50

Controller

ACP 50

AsyncHost

SNA

Figure 26. IP Transporter

...

X.25

Figure 27. PPP/SLIP/X.25 Gateway for Internet/Intranet Access.

��

PPP/SLIP

PAD

...

PPP/SLIP

PAD

X.25

X.25

X.25

X.25

Gateway

Frame Relay

X.25

Ethernet

��

(RFC 1490)

(RFC 1356)

Synchronous PPP

Internet/IntranetACP

PPP/SLIP/X.25

Page 60: ACP Functional Description Manual.pdf

ACP Functional Description, May 1998 52

Dynamic Allocation of IP Address

The ACP overcomes the limited number of available IPaddresses by permitting the network manager to create acommon pool of available IP addresses which are then sharedamong a large number of dial-up PPP/SLIP users. These IPaddresses are then assigned dynamically to the end user duringthe SLIP or PPP connect time and are valid just for thatsession.

Static IP Addresses

The ACP PPP/SLIP architecture allows network managers toassign fixed IP addresses to specific users or for specificpurposes so that a given user always uses the samepre-assigned IP address.

PPP/SLIP/X.25 Gateway Application

The ACP can operate as a PPP/SLIP/X.25 gateway, connectingusers to remote LANs or Internet/Intranet services. This offersan alternative means of access, and it usually requires little orno change to the existing access point(s) in the X.25 networkinfrastructure.

Figure 28 illustrates a gateway application. A PPP or SLIPuser dials into the current X.25 network, and a transparentvirtual circuit is established between the access point (PAD)and the ACP gateway. Optionally, the user can be directlyconnected to the Telematics Access Login Server before thecircuit is established. (For further information on the AccessLogging Server [ALS], contact your Telematics salesrepresentative).

Upon validation and approval for Internet/Intranet Access orremote LAN access, users are automatically connected to theappropriate software module on the selected ACP withPPP/SLIP/X.25 gateway using a switched virtual circuit(SVC). From then on, the SLIP or PPP data from the user’s PCis carried transparently over the X.25 network to the ACP(PPP/SLIP/X.25 gateway). This is referred to as“backhauling.”

The ACP gateway strips off the X.25 and PPP/SLIP headersand forwards the IP datagrams over X.25 (RFC 1356), framerelay (RFC 1294/1490), synchronous PPP, or Ethernet linksdepending upon the destination.

PPP/SLIP/X.25ACP 50

Gateway

X.25

X.25

X.25

X.25

PPP/SLIPUser

PPP/SLIPUser

EthernetLAN

RADIUS#1

RADIUS#2

100.1.1.1

100.1.1.2

100.1.1.100

100.1.1.101

Internet/

PAD

PAD

AccessLoginServer

Intranet

Figure 28. PPP/SLIP/Gateway Application

Page 61: ACP Functional Description Manual.pdf

ACP Functional Description, May 1998 53

PAP/CHAP and RADIUS Security

The following protocols offer security for PPP users (clients)accessing the Internet:

� Password Authentication Protocol (PAP), compliant withRFC1334;

� Challenge Handshake Authentication Protocol (CHAP),compliant with RFC1334;

� Remote Authentication Dial In User Service (RADIUS).(Authentication for SLIP is not supported.)

PAP/CHAP security is a common method of verifying andvalidating PPP clients on servers such as the RADIUS server,which can validate thousands of users by using a centralizeddatabase.

You can configure the ACP to authenticate using either CHAP(the primary, default authentication method) or PAP (thesecondary method). If the ACP is configured to authenticateand the selected servers do not respond, network access isdenied.

Figure 29 and Figure 30 illustrate typical connections betweenthe ACP and the RADIUS server. The RADIUS server is onthe same LAN segment as the ACP. The PPP client may be onthe same network or on another network.

PAP

The Password Authentication Protocol (PAP) uses a two-wayhandshake to establish the identity of a calling PPP clientwhen the link is established. The calling PPP client sends an

ID/password pair repeatedly to the authenticator, untilauthentication is acknowledged or the connection isterminated.

Passwords are sent over the network, and there is no protectionfrom playback or repeated trial-and-error attacks. The callingPPP client controls the frequency and timing of theauthentication requests.

In the ACP implementation, PAP is only used if the callingPPP client does not support CHAP. The ACP implements allfeatures of PAP in conformance with RFC 1334 and includesthe following message types:

� Authenticate-Request (ACP peer)

� Authenticate-ACK and NAK (ACP peer)

CHAP

The Challenge Handshake Authentication Protocol (CHAP)uses a three-way handshake with challenge messages to verifythe identity of the calling PPP client. It does this both when thelink is established and periodically afterward.

CHAP offers protection against playback attack by using anincrementally changing identifier and a variable challengevalue. The use of repeated challenge messages limits the timeof exposure to any single attack. The authenticator controls thefrequency and timing of the challenge messages. This methoddepends on a “secret” known only to the authenticator and thecalling PPP client; the secret is not sent over the link.

The ACP implementation of CHAP conforms to RFC 1334and includes the Challenge and Response, Success and Failuremessage types.

Internet/

PC

ACP 50

RADIUS Server

Router

Async PPP

X.25/Frame Relay/Sync PPP

Figure 29. ACP and PPP Client on Same Network as RADIUS Server

Intranet

Page 62: ACP Functional Description Manual.pdf

ACP Functional Description, May 1998 54

ACP 50

X25Frame RelaySync PPP

X.25 Dial

Internet/

X.25PPP

RADIUS Server

Router

Figure 30. PPP Clients Remote from ACP and RADIUS Server

Intranet

PPP/X.25 Gateway

RADIUS

The Remote Authentication Dial-In User Service (RADIUS)protocol is a draft RFC-based protocol. RADIUS servers areresponsible for receiving user connection requests,authenticating the user, and then returning all configurationinformation needed for the client to deliver services to theuser. The RADIUS server can act as a proxy client to otherkinds of authentication servers.

The ACP operates as a client of RADIUS. The ACP isresponsible for passing user information to designatedRADIUS servers, then acting on the response that is returned(see Figure 29 and Figure 30). The ACP generates and sendsall user connection requests to the RADIUS server. Up to threeserver addresses may be configured.

The ACP implementation of RADIUS includes a subset ofmessages, as defined in Internet Draft Revision 04, which areas follows:

� Access-Request (ACP to RADIUS Server)

� Access-Accept, Reject, and Challenge(Radius Server to ACP)

The following RADIUS options are supported:

� Password, IP address, subnet mask

� Actual service type and protocol type

� Framed user

For a complete listing of RADIUS standard attributes that aresupported and communicated to the ACP, see Table 9. Theattribute number and related value are translated intoinformation used by the ACP to respond to the PPP client andto the RADIUS server. NAS (Network Access Server) refers to

the ACP, which is a client of RADIUS and a server for the PPPclients.

The RADIUS server offers user authentication from a centralserver. The RADIUS server operates on a wide range ofplatforms such as SunOS, Solaris, HP/UX, Alpha OSF/1,Ultrix, AIX, Linux, BSD/OS, SCO, and Unixware. (Telematicsoffers its own RADIUS server, called Enforcer, which operateswithin a Windows� or Windows NT� environment.)

RADIUS Accounting Support. The ACP (NAS) operatesas a client of the RADIUS accounting server. The ACP issuesaccounting commands to the designated RADIUS accountingserver. The RADIUS server listens on UDP port 1646 foraccounting requests from the ACP and returns a receiveindication to the client. The RADIUS accounting server canalso act as a proxy client to other kinds of accounting servers.Up to three server addresses can be configured.

Proxy ARP for IP Addressing

Proxy ARP (Address Resolution Protocol) affects IPaddressing and permits the ACP to use the same subnetworkfor both the ELX interface and PPP ports, without requiringeither RIP or static routing.

Proxy ARP automatically assigns a series of contiguous IPaddresses to the ELX, SLIP, and PPP serial ports so that theELX and PPP interfaces all belong to the same LAN segment(such as 200.1.12 in Figure 31).

At the same time, this permits the flexibility to assign differentsubnet addresses to the ELX interface and PPP port interfaces,as needed.

Page 63: ACP Functional Description Manual.pdf

ACP Functional Description, May 1998 55

Table 9. RADIUS Standard Attributes

Attribute # Description Attribute # Description

ÁÁÁÁÁÁÁÁÁÁ

1 ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ

User Name ÁÁÁÁÁÁÁÁÁÁ

28 ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ

Idle-Timeout

ÁÁÁÁÁÁÁÁÁÁ

2 ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ

User Password ÁÁÁÁÁÁÁÁÁÁ

29 ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ

Termination-Action

ÁÁÁÁÁÁÁÁÁÁ

3 ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ

CHAP Password (Challenge-Response) ÁÁÁÁÁÁÁÁÁÁ

32 ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ

NAS-Identifier

ÁÁÁÁÁÁÁÁÁÁ

4 ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ

NAS-IP-Address ÁÁÁÁÁÁÁÁÁÁ

40 ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ

Acct-Status-Type

ÁÁÁÁÁÁÁÁÁÁ

5 ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ

NAS-Port ÁÁÁÁÁÁÁÁÁÁ

41 ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ

Acct-Delay-Time

ÁÁÁÁÁ6 ÁÁÁÁÁÁÁÁÁÁÁÁÁService-Type ÁÁÁÁÁ42 ÁÁÁÁÁÁÁÁÁÁÁÁÁÁAcct-Input-OctetsÁÁÁÁÁÁÁÁÁÁ7

ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁFramed-Protocol

ÁÁÁÁÁÁÁÁÁÁ43

ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁAcct-Output-OctetsÁÁÁÁÁ

ÁÁÁÁÁ8ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁFramed-IP-Address

ÁÁÁÁÁÁÁÁÁÁ44

ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁAcct-Session-IdÁÁÁÁÁ

ÁÁÁÁÁ9ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ

Framed-IP-NetmaskÁÁÁÁÁÁÁÁÁÁ

45ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ

Acct-AuthenticateÁÁÁÁÁÁÁÁÁÁ

12ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ

Framed-MTUÁÁÁÁÁÁÁÁÁÁ

46ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ

Acct-Session-TimeÁÁÁÁÁÁÁÁÁÁ

22ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ

Framed-RouteÁÁÁÁÁÁÁÁÁÁ

47ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ

Acct-Input-PacketsÁÁÁÁÁÁÁÁÁÁ

24 ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ

State ÁÁÁÁÁÁÁÁÁÁ

48 ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ

Acct-Output-PacketsÁÁÁÁÁÁÁÁÁÁ

25 ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ

Class ÁÁÁÁÁÁÁÁÁÁ

49 ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ

Acct-Terminate-CauseÁÁÁÁÁÁÁÁÁÁ

27 ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ

Session-Timeout ÁÁÁÁÁÁÁÁÁÁ

242 ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ

Data-Filter

Internet/

IP 200.1.1.3

RADIUS Server

Router

PPP

IP 200.1.1.2

IP 200.1.1.1

IP 200.1.1.4

IP 200.1.1.5

IP 200.1.1.100

Intranet

Figure 31. Proxy ARP Application Example

ACP 50

Page 64: ACP Functional Description Manual.pdf

ACP Functional Description, May 1998 56

TPP Support

Why TPP?

Although the ACP family supports de facto standards, such as3270 SNA and 3270 BSC, user communities also require theirnetworks to transport their proprietary traffic. To this end, anACP 10, 50, or 70 can carry Frame and Byte OrientedProtocols in X.25 packets for transport across an X.25network. This results in network saving by reducing extra linecharges.

FOP and BOP Protocols

The ACP TPP implementation supports two types ofsynchronous protocols: Byte Oriented Protocols (BOP) andFrame Oriented Protocols (FOP). All Byte Oriented Protocolsare synchronized using leading sync and sync loss characters,such as ETX, EOT, and ETB (these are referred to astermination characters). All Frame Oriented Protocols areframed with a leading and trailing (7E h) flag character, andmust contain a 16-bit FCS character, which is verified/regenerated at the TPP end points.

TPP Module

The TPP software module is available on the ACP 10, ACP70, and ACP 50 platforms. When the TPP module receivesdata from the FOP/BOP device, it loads it into the payload ofX.25 data packets for transmission through the network. At thedestination ACP, the data is then retrieved from the packets fordelivery to the attached device in the native format.

Figure 32 illustrates how proprietary statmux and 3780 RJEtraffic can be carried through the existing X.25 network toeliminate two dedicated leased lines.

The TPP processing activity is transparent to the users,appearing as a direct connection. Unlike the SNA and DSPmodules, which handle the polling locally via a TPAD/HPADfunctionality; the TPP module has no TPAD/HPADfunctionality and requires an ACP at both ends. All pollingand protocol activity is transmitted through the network. Forthis reason, TPP is best suited for protocols with minimaloverhead, and can only be used to replace point-to-pointleased lines.

Host

Figure 32. ACP TPP Support — A Sample Solution

Statmux

3780RJE

HostX.25

HostStatmux

3780RJE

HostX.25

Traditional Connectivity

X.25

Statmux

Statmux

3780

ACP Solution

Proprietary HDLC-like Protocol

Frame Relayor

X.25

Frame Relayor

X.25

Page 65: ACP Functional Description Manual.pdf

ACP Functional Description, May 1998 57

Connection Methods

There are two methods of establishing a connection betweentwo TPP end points: direct and PVC.

Direct Method

The first method is referred to as direct or autocall. Once theEIA handshake with the DTE has completed, the ACP willautomatically place a call to a predefined X.25 destination.

PVC Method

The second method is the use of a Permanent Virtual Circuit(PVC) in the X.25 network. When configured for PVCoperation, the PVC will be operational upon completion ofEIA handshake.

Monitoring Commands

The monitoring functions of the TPP module provides a seriesof commands, similar to other modules, that provides statusinformation about the connection to the FOP/BOP device. Theuser invokes these monitoring commands by using the ACP’sSystem Manager (SYM) software module. Typical commandsinclude the status command, down command, and upcommand.

Trace Functions

The TPP module’s trace function collects the FOP/BOPframes/data blocks being processed by the TPP module andsends them to the TRACE software module, where they areformatted for review. The Trace function monitors datatraveling to and from attached devices.

Page 66: ACP Functional Description Manual.pdf

ACP Functional Description, May 1998 58

POS Support

The POS software component is designed specifically fortransaction processing applications. Typical applicationsinclude point-of-sale (POS), Electronic Benefits Transferring,ATMs, and Internet commerce. When used with ACPs, POSreduces transaction processing time in environmentscharacterized by high volumes of low-speed, short-durationcalls.

Two ACP platforms support POS:

� ACP 50 for direct, dial, and host gateway applications.

� ACP 70 for direct and host gateway applications.

The ACP 50 was the first product offering from Telematics toaddress the payment transaction market. SmartView is thecompanion network management system designed forsimplifying the highly complicated tasks of networkmanagement and control.

ACPs provide a cost-effective and efficient means tointerconnect POS terminals and controllers withcommunicating host computers.

Basic operating capabilities include the following:

� Both synchronous and asynchronous connections.

� SDLC, VISA, SPDH, APACS, and TINET terminalcommunications protocols; major Wide Area Network(WAN) and Local Area Network (LAN) protocols such asX.25, frame relay, and TCP/IP based protocols.

� Programmable message-based transaction switching forISO 8583, VISAI, and VISAII.

� OmniNAC routing header support.

� Local spoofing which allows transactions to be transportedfrom one protocol to any other protocol, and eliminatesunnecessary overhead across the network.

Terminals and Hosts Supported

The POS terminals that have been tested and certified foroperation on the ACP products are noted in the followingtable.

Terminals Protocols Message Formats

Tranz 3xx, 4xx VISA, TINET,SPDH, APACS

VISAI, VISAII

Omni 3xx, 4xx SDLC, VISA,TINET, SPDH,APACS

ISO 8583VISAI, VISAII

The Tranz terminals use VISA, TINET, SPDH, and APACSprotocols, are asynchronous-only, and use VISAI and VISAII

message formats. The Omni terminals are synchronous orasynchronous, and can use the SDLC protocol with the ISO8583 message format as well as the VISA, TINET, SPDH, andAPACS protocols with the VISAI/VISAII message formats.

The POS hosts that are supported and have been testedinclude, but are not limited to: ASI (Tandem), BASE24(Tandem), CAP (IBM), and the Omnihost (VeriFone).

Connection Types

Link connections between the POS terminals and controllerand an ACP product may use one of four interface types:

� An ACP 50 internal modem on an octal modem CEM.This option saves money and space by using the same setof internal modem ports for either sync or async traffic,and also eliminates the need for numerous externalmodems.

� An external modem attached to an ACP port.

� A dedicated ACP port directly attached to the POSterminal via RS-232 interface.

� Gateway accessed through the X.25 network.

Programmable Message-Based Switching

ACP products support the following message formats:byte-oriented VISAI and VISAII message formats and thebit-oriented ISO 8583 message format.

ACPs are programmable for routing transaction messagesacross the network to different hosts based on the contents ofthe message received, such as source terminal ID and bank IDnumbers. This provides for configuration flexibility, allowingnew users to be added with little or no configuration required.

To illustrate message switching, refer to Figure 33 on the nextpage. As an example application, an authorization transactionis sent over the PSTN to the ACP 50. The transaction can beinitiated from a POS terminal or via an Internet service such astravel reservations, home shopping, or home banking. TheACP 50 negotiates an analog connection and then establishes aVISA, SDLC, PPP, or SLIP connection with the calling device(see part 1 of Figure 33). The protocol to the device isterminated at the ACP 50 and only user information is sentacross the X.25 or frame relay network. When the transactionreaches the gateway device (an ACP 70), the devicedetermines what type of information has been received andthen routes it accordingly. A POS transaction is routed to amerchant host for processing and authorization (see part 2a),while Internet traffic is routed to the Internet (see part 2b). If

Page 67: ACP Functional Description Manual.pdf

ACP Functional Description, May 1998 59

POS Terminals

ACP 50

PSTN

Dial Concentrator

Figure 33. Internet Commerce Application

���

TCP/IP

�������

�������

���

�����

��������

��������

ACP 70Host Gateway

���

Internet user orders an

������������

PPP

SLIP

PPP

��������

SDLC

SDLC

VISA

��

��

Routes Internet trafficto the Internet.

Routes POStransaction to themerchant host forprocessing andauthorization.

X.25

Frame RelayNetwork

or

X.25

Frame RelayNetwork

or

Internet

item using a credit cardtransaction. The webserver then sends the transaction to themerchant host for

authorization.�

The ACP 50 negotiatesan analog connection, thenestablishes a VISA, SDLC,PPP, or SLIP connection withthe device. Next, the protocolis terminated and user information is sent across theX.25 or Frame Relay network.

Receives packet viaTCP/IP, updates the database, and thenprepares informationfor transmission to thebank host.

Retail

Terminates TCP/IP andthen converts the transactionto Legacy X.25 for transmission to the bankhost. A bank host ID numbercan be used to route atransaction to a specific bankhost.

Receives thetransaction and thenupdates thecustomer database.

an Internet user orders an item offered over a web site, then thecredit card transaction used to purchase the item is routed tothe merchant host for authorization (see part 3).

The merchant host receives the transaction (either from a POSdevice or via the Internet) over TCP/IP, updates the customerdatabase, and then prepares information for transmission to theissuing bank of the credit card (the bank host). (See part 4.) Atthis point, the transmission is sent back through the ACP 70,which terminates TCP/IP and then converts the transaction toLegacy X.25 for transmission to the bank host (see part 5).Note that a bank ID number can be included in the transmittedpacket to route the transaction to a specific bank host. Oncethe transaction reaches the bank host, the customer’s databaseis updated and authorization is sent back to the transactioninitiator (the POS terminal or Internet user). (See part 6.)

Other Highlights

Fast Connect. ACP 50 modems can be configured toeliminate many of the delays normally pre-programmed instandard analog modems, such as network billing delay and

standard modem answer tone. This allows the modems to startthe handshake sequence more quickly (see Figure 34).

Automatic Protocol Detection. When a port uses aninternal modem and its basic configuration is for automaticmode operation, the ACP 50 determines the actual connectionmode (synchronous or asynchronous) and then determines thelink protocol for use with SDLC or VISA.

POS follows a series of steps to determine the connectionmode:1. The internal modem goes off-hook and trains with the

calling modem.2. Once the analog connection is established, the modem

component waits to receive synchronous FLAGcharacters from the calling device to determine if it is asynchronous device.

3. If no FLAGs are received within 500 milliseconds, thecall is treated as asynchronous.

POS assumes SDLC protocol for synchronous connections andVISA protocol for asynchronous connections.

Page 68: ACP Functional Description Manual.pdf

ACP Functional Description, May 1998 60

Figure 34. Example of a Fast Connect Transaction

Normal Ring Connect BillingDelay

AnswerTone

StandardModemTraining

X.25Call

Setup

HostEnq

DataTransfer

POSACK

X.25PSTNCall

Teardown

Ring Fast LocalEnq

DataTransfer

POSACK

PSTNCall

TeardownTrain

Sequence

TransactionSequence

FastTransactionSequence

1 2 3 4 5 6 7 8 9 10

1 2 3 4 5 6

10 200

Seconds

Transaction Tracking. The ACP allows the networkmanager to monitor traffic by transaction, rather than bypacket (which may contain information other than transactiondata). The ACP tracks transactions in both directions via INand OUT counters in the system management module. Thismakes it possible to monitor the performance of the systemeither off-line or in real time.

Local Protocol Spoofing. Local protocol spoofingeliminates the handshake with the host, so only transactiondata is exchanged and host overhead is reduced.

When protocol spoofing occurs, the transaction starts soonerbecause the ENQ does not have to come from the actual host.The ACP emulates the host by polling the POS terminal with

an ENQ as soon as the modem connects. With full VISAemulation, the ACP takes on the additional responsibilities ofperforming LRC checking, terminating and generating ACKstoward the POS terminal, and terminating the call when thetransaction is complete. This further reduces X.25 networkoverhead and reduces total transaction time. (See Figure 35.)

TPDU Support. The ACP supports TPDU addressing,making it compatible with TPDU-based transaction networks.The ACP supports TPDU in two ways:

� Switched TPDU—In this mode, the ACP passes thereceived TPDU from the downlink to the uplink.

Figure 35. Local Protocol Spoofing

ACP 50Network Controller

Host

Merchant’sPoint of Sale

Calls Host

TX Transaction

Host Response

Calls Host

ENQ

TX Transaction

ACK

Host Response

ACK

EOT

Disconnect

Page 69: ACP Functional Description Manual.pdf

ACP Functional Description, May 1998 61

� Spoofed TPDU—In this mode, the ACP strips or appendsthe TPDU before sending the transaction to thedownstream device or host.

Application Types . The ACP products process VISAIImessages of application types 1 through 4, to determine theprotocol (authorization or data capture) and the mode (singleor multiple) of the connection to the terminal.

Example Applications

A variety of POS applications that utilize ACP systems areshown in Figure 36 on page 62. This figure is divided intoseven sections (A through G), indicating the various POSapplications that can be used:

� Dial concentrator applications (see section A); up to 24internal modem connections per ACP 50.

� Direct-connect concentrator applications, using multiplePOS terminals and a 1200C or Omni 495 controller (seeSection B); up to 48 async or 24 sync ports on the ACP 50.

� Dial access Internet commerce applications, includingtravel reservations, home shopping, and home banking viaPCs (see section C); up to 24 internal modem connectionson the ACP 50.

� Connection to Internet web sites via X.25 (see section D).

� Host gateway applications (section E); the ACP 70 can beconnected to a TCP/IP client/server application viaEthernet LAN. The gateway reduces the number ofcommunication lines required at the host by providing asingle point gateway access to Legacy X.25 or frame relaybased host applications.

� Connection to an X.25 host (section F).

Figure 36 section A illustrates credit card transactionstraveling from POS terminals through the telephone network(PSTN) to a ACP 50 unit, then across an X.25 or frame relaynetwork to the merchant account host.

Section B shows POS terminals that are directly attached to acontroller. This arrangement is used primarily in grocery storesor shopping malls. The terminals can be connected to either aACP 50 or ACP 70 for accessing a merchant host.

Section C shows dial connections of PCs to a ACP 50 forelectronic commerce applications, such as travel reservations,home shopping, and home banking. The PCs send a messageto the ACP 50 via PPP, and the message is transferred overX.25 or frame relay to a web site (see section D).

When receiving inputs across the access layer (sections A andB shown), the ACP acts as a single access concentrator:receiving transaction messages from multiple terminals, andthen transmitting the messages across an X.25 or frame relaynetwork.

When receiving inputs from the X.25 or frame relay networklayer (section E), the ACP acts as a gateway to multiple hosts:it receives a message, determines its destination host,encapsulates the message for the host protocol, and thentransmits the message to the host.

A message can also be transmitted directly from the X.25 orframe relay network to an X.25 host (see section F).

You can manage the network through the local networkmanager (SYM) or remotely through the centralized networkmanager SmartView (section G). Protocol upgrades can beaccomplished directly through the ACP software.

Page 70: ACP Functional Description Manual.pdf

ACP Functional Description, May 1998 62

POS Terminals

Host Gateway

TCP/IP

C

A

ACP 50

E

Dial Access

PSTN

Dial Concentrator

�������

Omni 390

Omni 330

Omni 330

Sync

Async/Tranz 330

Omni 4xx

�� ��

PPP

ACP 50

ACP 50

Figure 36. Sample POS Applications

�����������

������������

������������

Web Site

X.25

D

G

NetworkManagement

System(SmartView)

��������

F1200C

B

Direct ConnectOmni 495

TINET

SDLC

POS Terminals

ACP 50

Visa

SDLC

Controller

Controller

X.25

Frame RelayNetwork

or

Internet

�����������������

PSTN

Page 71: ACP Functional Description Manual.pdf

ACP Functional Description, May 1998 63

ISDN BRI Support

Integrated Services Digital Network (ISDN) technology is thebasis for high-speed, international computer-to-computercommunications through a simple pair of wires or equivalent(a single, standardized physical connection for voice and datacommunications). ISDN offers complete digital connectivityfrom the subscriber’s location to and throughout the network.

ISDN also offers distinct benefits, including performanceadvantages (higher data speeds and greater distancecapabilities at lower costs); connectivity (the ability to accessmultiple resources from a single terminal); and fasterdevelopment of new services (due to the basic transportsystem put in place).

As a standard interface to the public network, ISDN givescustomers versatility in selecting customer premisesequipment for services. Furthermore, the separate signalingchannel and the rich service capabilities of ISDN technologyprovide customers greater functionality via the public networkover today’s most advanced premises systems, including localarea networks (LANs) and PBXs.

How ISDN Basic Rate Interface (BRI)Works

The twisted pair of copper wires from the Central Officeprovides the basic rate interface (BRI). The BRI is divided intothree channels: two channels are labeled B and the third islabeled D. Each B channel supports a rate of 56/64 kbps. Theoverall BRI rate is 144 kbps. The two B channels are used forvoice and data transmissions (both circuit-switched and/orpacket-switched), while the single D channel is used forsignaling and lower speed packet-switched data. This 2B+Dconfiguration is available to customers over either a 2-wire(U-interface) or a 4-wire (S/T-interface), depending on thecountry deployed and the distance from the Central Office.

The B and D channels are full-duplex bit streams which aretime-division multiplexed into a common stream containingboth user information and signaling/transmitting multiplesignal streams over a single wire.

ISDN Specifications

ISDN is defined in recommendations set forth by theInternational Telecommunications Union (ITU).

Recommendation Describes

Q.920 General principles of LAPD (LinkAccess Procedures on theD-channel): also referred to as theDigital Subscriber Signaling SystemNo. 1 (DSS 1) Data Link Layer.

Q.921 LAPD operating procedures.

Q.930 General principles of user-networksignaling. Together, the four Q.93xprotocols make up the networklayer of the Digital SubscriberSignaling System No. 1 (DSS 1).

Q.931 User-network messages for basiccall control.

Q.932 User-network messages forsupplementary services.

Q.933 Signaling for frame-mode services.

X.31 Procedures for full X.25 LAPB andPLP support on the B-channel, andthe transport of X.25 PLP packets inLAPD frames on the D-channel.

The implementation of ISDN BRI in ACP products adheres tothe following specifications:

Level Protocols

3 Network X.25 X.25 Call Control Q.930/Q.931

2 Datalink I.46X LAPB, LAPD LAPDQ.920/Q.921I.440/I.441

1 Physical I.430 (CCITT)B-Channel D-Channel

For certification details, please refer to Table 2 on page 10 orcontact your Telematics representative regarding a specificcountry.

Page 72: ACP Functional Description Manual.pdf

ACP Functional Description, May 1998 64

National ISDN Variations

The CCITT recommendations released in the 1970’s allowedfor broad interpretations, which have led to a mix ofproprietary systems and equipment that are unable toeffectively communicate with each other. As a result, severalnational or regional standards have evolved. The table belowidentifies the ISDN variations supported in ACP networkingproducts.

Euro-ISDN . In a Memorandum of Understanding (MoU),26 public network operators from 20 European countriesagreed to pursue common ISDN basic (BRI) and primary(PRI) rate interfaces for a common European standard by theend of 1993.

German 1TR6 . Germany has been offering ISDN since1989. As no international standard had been agreed at thattime, the DBP introduced ISDN on the basis of a nationalstandard. Now, Euro-ISDN is paving the way for efficientinternational communications.

Euro-ISDN differs from the existing German national ISDNonly in the D channel protocol used. In the case of the Germannational ISDN, this is the 1TR6 protocol while in the case ofEuro-ISDN, it is the E-DSS1 protocol. DBP introduced theEuropean D channel protocol in most of the ISDN exchangesin the fall of 1992.

NI-1. The U.S. and Canada adopted the National ISDN(NI-1) specifications developed by Bell CommunicationsResearch Inc. (Bellcore). Prior to NI-1, AT&T and NorthernTelecom had unique implementations of ISDN. The differenceprimarily involved ISDN voice capabilities.

VN3 and Euro-Numeris . France is developing thesesignaling standards for its specific requirements.

ACP ISDN Applications

Low Utilization Access. The BRI option can be used toestablish an X.25 link on demand, utilizing one of the Bchannels, via ISDN services. The X.25 link will subsequentlybe brought down when there is no activity for a configurableperiod of time. This option is similar to “dial-out X.25”currently on the ACP.

Leased Link Backup. In locations where ACPs aredeployed, the BRI option can be used to back up dedicatedports on the VHSL or octal DMA links via ISDN. This optionis similar to “dial-out X.25” currently on the ACP.

Bandwidth on Demand. The ISDN option can provideadditional bandwidth during peak periods. When themaximum number of virtual circuits are exceeded, additionaltraffic can be routed over one of the B channels. The link willsubsequently be brought down when there is no additionalbandwidth required.

Call Backup. In Figure 37, the primary route between twonodes is a leased line. A dial-up backup link using BRIchannels through the ISDN provides an alternate routewhenever the primary link fails.

Call Balancing. For call balancing, the ACP can beconfigured to direct a portion of traffic over the leased line,and other traffic through the ISDN, alternating the use of thetwo links call by call.

Dedicated Services . The ISDN option offers dedicatedconnections via ISDN services (see Figure 38). In theseapplications, the ACP will never clear the connection,regardless the traffic load. The ACP will automaticallyattempt link re-initialization ISDN call failure.

LAN traffic over ISDN . This functionality is availablewithin the ACP 70 product which can support ELX and ISDNconcurrently (see Figure 39).

LAN-to-LAN Connection. The switched B channelsprovide dial-up 64 kbps links for internetworking remotelylocated LANs and other data equipment. A LAN-to-LANconnection allows users to access equipment attached to bothLANs, including personal computers, printers, files servers,and gateways. Internetworking LANs through switched ISDNaccess can replace private leased lines underutilized byburst-filled LAN-to-LAN traffic, or reduce the long holdingtimes required by slow speed modems links.

For a summary of ACP-supported ISDN BRI variations andcertifications, refer to Table 2 on page 10.

Page 73: ACP Functional Description Manual.pdf

ACP Functional Description, May 1998 65

ACP 50 ACP 50

BRIBRI

Leased Line

Figure 37. ISDN BRI Channels used for Call-Backup or Call Balancing

ISDN

ACP 50

Figure 38. BRI Channels as the Primary Link

HOST PCP

ACPACPISDN

ACP 50

ACP 70

Figure 39. LAN Traffic over ISDN (for ACP 70 only)

HOST HOST

Ethernet LAN Ethernet LAN

ISDN

ACP 70

Page 74: ACP Functional Description Manual.pdf

ACP Functional Description, May 1998 66

Internal Modem Support

Computer-to-computer data transfer that involves the use oftelephone lines—either the public voice telephone system ordedicated telephone lines—requires the use of a modem. Amodem is needed to translate computer data, which is indigital format, to analog format—a format that can besuccessfully transmitted via the telephone lines.

Each computer-to-computer link involves the use of twomodems, one at each computer to translate data in and out.One computer simply calls the other, the distant computeranswers the call (a process referred to as handshaking), andthen a communication path between the two computers isestablished. With the communication path intact, the modemsthen perform the necessary translations to import data fromone computer to the other.

Modem Sharing

If every computer in an organization has its own dedicatedmodem, this can add up to a significant investment. As aresult, many computer users now share modems in modempool arrangements.

While shared modems help reduce the number of modemsneeded, most modems are separate external devices, oftentaking up considerable space, and often complicated withdifferent maintenance requirements than other networkequipment. While dedicated modems reside next to theirassociated terminals, groups of pooled modems are oftenhoused in large rack-mount devices and may have heavycabling requirements.

ACP 50 Internal Modems

When an ACP system is used, shared external modems are oneoption that can be used. However, as an alternative to externalmodems, the ACP 50 can have built-in 2-wire (internal)modems, thereby eliminating the need for external modems.

The ACP 50 can be equipped with up to three octal modemCEMs, each supporting up to eight high-speed,synchronous/asynchronous modems. The stretch ACP chassiscan support up to three octal modem CEMs, providing theACP with up to 24 modems.

Octal modem CEMs work in conjunction with octal modemCAMs. The CAMs are available in three types: one for leasedline communications (UK); one for PSTN (UK); and one forPSTN (US). These CAMs offer 2-wire leased line

communications and 2-wire public switched telephonenetwork (PSTN) dial-up capabilities. CAMs can be used incombination to provide access to both leased lines and publicswitched telephone networks.

Each octal modem CAM has a DB25 diagnostic port for datascope connection to monitor the individual modem lines, witha chassis-mounted selection dial to move between theindividual modems. Three LEDs per modem line indicatetransmit data (TXD), receive data (RXD), and data carrierdetect (DCD) activity.

Advantages of Internal Modems

Using ACP internal modems instead of external modemspresents the following advantages:

� A large number of modem interfaces and operating speedsare supported (see Table 10).

� Protocol upgrades can be accomplished directly throughthe ACP software, thereby simplifying the upgradeprocedure (see Figure 40).

� An extensive cost savings can be achieved due to: (1) theability to have up to 24 internal modems in a single ACPinstead of 24 external modems; (2) reduced cabling; and(3) reduced rack-mount space requirements.

� ACP internal modems support the standard operatingspeeds that are widely used today. The modems supportboth synchronous and asynchronous, full-duplex operationover 2-wire dial-up (US/UK) or leased (UK) lines.

� A pool of up to 24 multi-speed modem ports (seeFigure 41) can be provided in a single ACP, eliminatingPSTN dedicated rotary dialing requirements.

Table 10. Modem Interfaces and Operating Speeds

Interface Connection Rates (bps)

V.32bis 14400, 12000, 9600, 7200,4800

V.32 9600, 4800

V.22bis 2400V.22 2400V.23 75/1200, 1200/75V.21 0 to 300V.34 28000Bell 212A 1200Bell 103 0 to 300

Page 75: ACP Functional Description Manual.pdf

ACP Functional Description, May 1998 67

Figure 40. ACP Internal Modem Dial-In Applications.

PC

CRT

PSTN

Async

X.25

PPP

SLIP

ACP 50

Modem

X.25

Frame

IP

ISDN

Relaywith internalmodems

Figure 41. ACP Internal Modem Leased-Line Application

X.25/Frame Relay/IP

ACP 50

SNA Cluster

X.25Host

Modem

PC

with internal modems

� The use of one piece of equipment—the ACP 50—formodem and other networking purposes, simplifies networkmanagement. The ACP’s Network Manager onlinediagnostics and EIA monitoring can be applied to modems.Some of the items that can be monitored by the ACPinclude Mean System Error, V.54 loops, and call failurerates.

� Internal ACP modems provide high-speed asynchronous(115.2 bps) and synchronous (28.8 kbps) transmission inconjunction with V.42bis.

� Translation procedures performed by ACP internalmodems are completely transparent to the end user. Userscan dial out to establish outgoing calls over telephone linesas well as receive incoming calls.

� Internal modems support V.42bis data compressionstandards.

� Internal modems support MNP Levels 1–4, which enableerror-free data transmission, and MNP Level 5, whichincorporates Levels 1–4 and compresses data by a factor of4 to 1.

Page 76: ACP Functional Description Manual.pdf

ACP Functional Description, May 1998 68

Synchronous Dial-out

The end user can place an outgoing data call through the ACPto establish a dial-out connection, by using X.25 packet nodedevices or async devices via a PSTN line. The ACP activatesthe dial-up connection and, if there is no activity on the line fora specified period of time, the ACP will disconnect the call.The ACP can be customer-configured for timeout delay, thenumber of destination call attempts, and the inactivity periodpreceding automatic call disconnection. These parameters canbe set to establish a means of back-up for dedicated ACP linksor to establish a temporary “overflow” link when the numberof virtual channels on the primary link exceeds a predefinednumber.

Additionally, ACPs that are deployed at sites where trafficdoes not warrant a dedicated link, can use these parameters toestablish an X.25 link on demand. The first X.25 call requestpacket would cause the ACP to establish the link; the linkwould subsequently be brought down when no activity isdetected within the preconfigured time period.

Because ACP internal modems are controlled by the ACPsoftware, it is not actually required that the modem be Hayescompatible. However, for ease of use, it is possible to use theHayes syntax when configuring dial-out numbers.

Asynchronous Dial-out

Asynchronous dial-out capability enables the ACP 50 to bothreceive and place modem calls without having to preassign thecalling destination. As an example, if a modem call is placedto the ACP, the ACP maintains the number of the callingmodem as part of the data packet. The ACP can thenautomatically call back that modem. This type of arrangementis particularly useful in POS scenarios.

Dial-in

ACPs with internal modems can establish an X.25 connectionwith another ACP or a X.25 packet mode device that isplacing a call via PSTN lines. The ACP internal modems canbe configured to recognize the mode of operation used by theincoming call device, thereby allowing the call to be receivedand a connection to be established. If the incoming call line isinactive for a specified period of time, the ACP can beconfigured to automatically disconnect the call.

ACP Internal Modem Specifications

Details regarding ACP internal modem functionality aresummarized in Tables 11 and 12.

NOTE: Internal modems are not recommended for directattachment to PBXs due to varied ringing voltagesand pulses.

For certification details, refer to Table 2 on page 10 or contactyour Telematics representative.

Table 11. Internal Modem Dial Functionality

General Automatic modem type detection

7, 8, 9, and 10-bit character lengths forasync applications

Auto detection/support of V.42/V.42bis

Auto detection/support of MNP/MNP5

Not CurrentlySupported

Dial-out async, half-duplex operation, FAX,caller ID, call progress tones, pulse dialing

SynchronousDial-out features

Synch channels only, in originate mode

Blind dialing * supported (UK CAM only)

AsynchronousDial-out features

Async channels in originate or standbymode

Dial-in features Async/sync channels, in answer mode

* Refers to dialing without waiting for call progress tones from the PSTN or PBX such as dial tone, busy tone, etc.

Page 77: ACP Functional Description Manual.pdf

ACP Functional Description, May 1998 69

Table 12. General Internal Modem Specifications

Operation Full duplex over 2-wire dial-up(US/UK) or leased line (UK)

Modem Interfaces See Table 10 on page 66.

Error control and data com-pression

V.42bis; MNP Levels 1–4MNP Level 5

Maximum Speed Synchronous up to 28.8 kbps;Async up to 115.2 bps

Fallback speeds 7200, 4800 bps (V.32)1200 bps (V.22bis)

Receive Signal Level Accuracy tolerance of ±1 dB

Frequency Range 300 – 3400 Hz

Receive Level Adjustment Automatic

Receiver Dynamic Range –9 dBm to –40 dBm (14.4k)–40 dBm to –43 dBm (12k)

Receiver Baud Timing +/–0.01% frequency error in re-mote transmit timing source; forV.22bis: ± 0.03% of frequencyerror.

Carrier Recovery ±7 Hz frequency offset

Automatic Gain Control Automatic gain control in allmodes compensates for re-ceive signal level fluctuations.

PSTN Transmit Level (US) –10 dBm ± 1 dBm

LL Transmit Level – 13 dBm + 1 dB

LL Line Impedance 600 ohms with return loss of ≤20 dB over 300 to 3400 Hz

LL Line Type Dry line

Cabling Requirements RJ11 connectors

Approvals PSTN (US): FCC Part 68, DOCLL (UK), PSTN (UK): BABT

Protocols Currently Supported

Synchronous: X.25, PPP, frame relayAsynchronous: X.3, SLIP, PPP

Page 78: ACP Functional Description Manual.pdf

ACP Functional Description, May 1998 70

Functional Characteristics

Personality Module

Each ACP is equipped with a personality module, a plug-inprinted circuit board that houses enable key chips. Thepresence of certain enable keys defines the functionalcharacteristics of that model, e.g., the protocols, features(number of LUs and devices), and memory size supported.

ACP platforms are available with a variety of communicationsoftware modules to support various access and networkingfunctions. Each function, or personality, is identified by a two-or three-letter mnemonic. Table 13 lists each personality, therelated software module in the ACP operating code, and thefunctionality that each provides.

Since ACPs are capable of supporting multiple accessprotocols, personalities are often combined. For example, anACP with three functionalities—SNA PAD, X.25 switch, andasync PAD—is referred to as an SNA/SW/AS ACP.

Table 13. Personality Module Functionality

PersonalityACP Software

Module ACP Functionality

DSP DSP 3270 BSC TPAD

SNA SNA SNA PAD

AS ITI Asynchronous PADSupports Voice/FAX ca-pability

SW X.25 X.25 Switch

TP TPP Transparent Passthrough

FR Frame Relay FRAD/ Concentrator

IP IP LAN Access and Interconnection 1

BR BRI ISDN Basic Rate Interface

MD Modem Internal Modem

POS POS Point-of-sale protocol set

1 Some IP personality kits include the Point-to-Point Protocol (PPP) and IP transporter.

Field upgrades to the functionality of the ACP 50 are achievedby plugging in additional enable keys; for the ACP 10 and 70,the protocol enable key must be upgraded to the appropriatelevel. This allows you to upgrade at a fraction of the cost ofbuying a new ACP.

Refer to ������ 14 through 19� beginning on the next page, forfunctional characteristics and upgrade details. For additionalinformation about software field upgrades, contact yourTelematics sales representative.

Nature of Performance Data

Due to the wealth of features and configuration possibilities,the data in this document can only be estimated, for designguidelines only. Telematics recommends a detailed evaluationof any equipment prior to deployment.

If exact data is required, we recommend that you conductextensive benchmarking at your facility.

Guidelines to Data

Tables 14 through 19 on the following pages indicate thefunctional characteristics of each ACP, using various softwarecombinations. Information contained in these tables is of fourtypes:

� Numbers = data.

� Asterisks (*) = indicate that the number of LCNs isdeemed too low to be practical for a port/memoryconfiguration of this size.

� Hyphens = not applicable.

� TBD or blank = to be determined; data will be supplied ata later date.

It is helpful to review the following paragraphs forassumptions and guidelines concerning the tables.

Connection Type . The values shown for X.25, TPP,PU–LU, CU–DEV, DLCI, and FR are the maximum allowableper ACP. Note that the LU and DEV values shown are themaximum allowable per ACP, not for each PU or CU.

Logical Channels. Results listed in the Logical Channelscolumns were based on a configuration with the followingcharacteristics:

� Assumes billing is disabled, modulo 8 X.25 operation, anddefault settings.

� Assumes all SNA PUs are multidropped on one sync port.

� Elinks field set to equal the number of DLCIs.

� No 3270 BSC CUs or devices.

� Maximum number of SNA PUs and LUs.

� No TPP links enabled.

� Frame relay: 1 FRI, 4 DLCIs.

LCNs. Due to the wealth of features and configurationpossibilities, the number of LCNs available to a given ACPcan only be estimated. If it is critical to know the exact numberof LCNs to be supported by an ACP in a specific environment,

Page 79: ACP Functional Description Manual.pdf

ACP Functional Description, May 1998 71

the ACP will provide the LCN count once it is configured andinitialized.

Min/Max Numbers. The Max/Min figures in the LogicalChannels columns correspond to the Min/Max figures in thePorts columns. Asterisks (*) indicate that the number of LCNsis deemed too low to be practical for a port/memoryconfiguration of this size.

In an X.25 switch, a virtual circuit requires two logicalchannels. SNA QLLC mode requires only one LCN per PUsession; VLU mode requires one LCN per LU session. DSPrequires one LCN per device session.

ITI and TPP require one LCN per session. Minitel supportreduces the number of logical channels by approximately 15.

Table 14. ACP 10 Functional Characteristics – Versions 10.12 and 1.xx

Ports Connection Type Logical Channels Enable Key Levels

ACPPlatform

Personality Kitand Model Number

Min/MaxSync

Min/MaxAsync

MaxTPP

PU–LU CU–DEV

DLCISwitched

DLCIFRAD

Max/Minw/128K Mem

Max/Minw/256K Mem

ProtocolKey

FeatureKey

ÁÁÁÁÁÁÁÁ

ÁÁÁÁÁÁÁÁÁÁ

SW/SNA 12x9ÁÁÁÁÁÁÁÁ

2/6 ÁÁÁÁÁÁ

– ÁÁÁÁÁÁ

– ÁÁÁÁÁÁ

3–32ÁÁÁÁÁÁ

– ÁÁÁÁÁÁ

– ÁÁÁÁÁÁ

– ÁÁÁÁÁÁ

60/*ÁÁÁÁÁÁÁÁ

410/350ÁÁÁÁÁÁÁÁ

9 ÁÁÁÁÁÁ

24

ÁÁÁÁACP 10 ÁÁÁÁÁSW/AS/SNA 13x9ÁÁÁÁ2 ÁÁÁ4 ÁÁÁ– ÁÁÁ3–32ÁÁÁ– ÁÁÁ– ÁÁÁ– ÁÁÁ25ÁÁÁÁ375 ÁÁÁÁ14 ÁÁÁ24ÁÁÁÁÁÁÁÁw/ Type 2

ÁÁÁÁÁÁÁÁÁÁ

ÁÁÁÁÁÁÁÁ5

ÁÁÁÁÁÁ1ÁÁÁÁÁÁ–ÁÁÁÁÁÁ3–32ÁÁÁÁÁÁ–ÁÁÁÁÁÁ–ÁÁÁÁÁÁ–ÁÁÁÁÁÁ*ÁÁÁÁÁÁÁÁ345

ÁÁÁÁÁÁÁÁ14

ÁÁÁÁÁÁ24ÁÁÁÁ

ÁÁÁÁsoftwareÁÁÁÁÁÁÁÁÁÁ

AS 15x9ÁÁÁÁÁÁÁÁ

1ÁÁÁÁÁÁ

5ÁÁÁÁÁÁ

–ÁÁÁÁÁÁ

–ÁÁÁÁÁÁ

–ÁÁÁÁÁÁ

–ÁÁÁÁÁÁ

–ÁÁÁÁÁÁ

100ÁÁÁÁÁÁÁÁ

470ÁÁÁÁÁÁÁÁ

1ÁÁÁÁÁÁ

24

ÁÁÁÁÁÁÁÁ

ÁÁÁÁÁÁÁÁÁÁ

SW/AS 16x9ÁÁÁÁÁÁÁÁ

2 ÁÁÁÁÁÁ

4 ÁÁÁÁÁÁ

– ÁÁÁÁÁÁ

– ÁÁÁÁÁÁ

– ÁÁÁÁÁÁ

– ÁÁÁÁÁÁ

– ÁÁÁÁÁÁ

90ÁÁÁÁÁÁÁÁ

450 ÁÁÁÁÁÁÁÁ

11 ÁÁÁÁÁÁ

24

ÁÁÁÁÁÁÁÁ

ÁÁÁÁÁÁÁÁÁÁ

ÁÁÁÁÁÁÁÁ

5 ÁÁÁÁÁÁ

1 ÁÁÁÁÁÁ

– ÁÁÁÁÁÁ

– ÁÁÁÁÁÁ

– ÁÁÁÁÁÁ

– ÁÁÁÁÁÁ

– ÁÁÁÁÁÁ

55ÁÁÁÁÁÁÁÁ

420 ÁÁÁÁÁÁÁÁ

11 ÁÁÁÁÁÁ

24

ÁÁÁÁÁÁÁÁÁSW 17x9ÁÁÁÁ2/6 ÁÁÁ– ÁÁÁ– ÁÁÁ– ÁÁÁ– ÁÁÁ– ÁÁÁ– ÁÁÁ120/60ÁÁÁÁ470/420ÁÁÁÁ6 ÁÁÁ24ÁÁÁÁÁÁÁÁ

w/Type 3ÁÁÁÁÁÁÁÁÁÁ

SW/AS/TP 1Mx9ÁÁÁÁÁÁÁÁ

2ÁÁÁÁÁÁ

4ÁÁÁÁÁÁ

3ÁÁÁÁÁÁ

–ÁÁÁÁÁÁ

–ÁÁÁÁÁÁ

–ÁÁÁÁÁÁ

–ÁÁÁÁÁÁ

*ÁÁÁÁÁÁÁÁ

424ÁÁÁÁÁÁÁÁ

11ÁÁÁÁÁÁ

24ÁÁÁÁÁÁÁÁ

software ÁÁÁÁÁÁÁÁÁÁ

ÁÁÁÁÁÁÁÁ

5 ÁÁÁÁÁÁ

1 ÁÁÁÁÁÁ

3 ÁÁÁÁÁÁ

– ÁÁÁÁÁÁ

– ÁÁÁÁÁÁ

– ÁÁÁÁÁÁ

– ÁÁÁÁÁÁ

* ÁÁÁÁÁÁÁÁ

395 ÁÁÁÁÁÁÁÁ

11 ÁÁÁÁÁÁ

24

ÁÁÁÁÁÁÁÁ

ÁÁÁÁÁÁÁÁÁÁ

SW/AS/SNA/TP 1Jx9ÁÁÁÁÁÁÁÁ

2 ÁÁÁÁÁÁ

4 ÁÁÁÁÁÁ

3 ÁÁÁÁÁÁ

3–32ÁÁÁÁÁÁ

– ÁÁÁÁÁÁ

– ÁÁÁÁÁÁ

– ÁÁÁÁÁÁ

* ÁÁÁÁÁÁÁÁ

446 ÁÁÁÁÁÁÁÁ

14 ÁÁÁÁÁÁ

24

ÁÁÁÁÁÁÁÁÁ ÁÁÁÁ5 ÁÁÁ1 ÁÁÁ3 ÁÁÁ3–32ÁÁÁ– ÁÁÁ– ÁÁÁ– ÁÁÁ* ÁÁÁÁ405 ÁÁÁÁ14 ÁÁÁ24ÁÁÁÁÁÁÁÁ

w/Type 5ÁÁÁÁÁÁÁÁÁÁ

SW/SNA/DSP 11x9ÁÁÁÁÁÁÁÁ

2/6 –ÁÁÁÁÁÁ

–ÁÁÁÁÁÁ

3–32ÁÁÁÁÁÁ

3–32ÁÁÁÁÁÁ

–ÁÁÁÁÁÁ

–ÁÁÁÁÁÁ

*ÁÁÁÁÁÁÁÁ

150/120ÁÁÁÁÁÁÁÁ

12ÁÁÁÁÁÁ

24ÁÁÁÁÁÁÁÁ

software ÁÁÁÁÁÁÁÁÁÁ

SW/AS/DSP 14x9ÁÁÁÁÁÁÁÁ

2 ÁÁÁÁÁÁ

4 ÁÁÁÁÁÁ

– ÁÁÁÁÁÁ

– ÁÁÁÁÁÁ

3–32 ÁÁÁÁÁÁ

– ÁÁÁÁÁÁ

– ÁÁÁÁÁÁ

* ÁÁÁÁÁÁÁÁ

175 ÁÁÁÁÁÁÁÁ

14 ÁÁÁÁÁÁ

24

ÁÁÁÁÁÁÁÁ

ÁÁÁÁÁÁÁÁÁÁ

ÁÁÁÁÁÁÁÁ

5 ÁÁÁÁÁÁ

1 ÁÁÁÁÁÁ

– ÁÁÁÁÁÁ

– ÁÁÁÁÁÁ

3–32 ÁÁÁÁÁÁ

– ÁÁÁÁÁÁ

– ÁÁÁÁÁÁ

* ÁÁÁÁÁÁÁÁ

170 ÁÁÁÁÁÁÁÁ

14 ÁÁÁÁÁÁ

24

ÁÁÁÁÁÁÁÁÁSW/DSP 18x9ÁÁÁÁ2/6 ÁÁÁ– ÁÁÁ– ÁÁÁ– ÁÁÁ3–32 ÁÁÁ– ÁÁÁ– ÁÁÁ* ÁÁÁÁ200/180ÁÁÁÁ9 ÁÁÁ24ÁÁÁÁÁÁÁÁ

ÁÁÁÁÁÁÁÁÁÁ

SW/AS/SNA/DSP 19x9ÁÁÁÁÁÁÁÁ

2ÁÁÁÁÁÁ

4ÁÁÁÁÁÁ

–ÁÁÁÁÁÁ

3–32ÁÁÁÁÁÁ

3–32ÁÁÁÁÁÁ

–ÁÁÁÁÁÁ

–ÁÁÁÁÁÁ

*ÁÁÁÁÁÁÁÁ

130ÁÁÁÁÁÁÁÁ

17ÁÁÁÁÁÁ

24ÁÁÁÁÁÁÁÁ

ÁÁÁÁÁÁÁÁÁÁ

ÁÁÁÁÁÁÁÁ

5 ÁÁÁÁÁÁ

1 ÁÁÁÁÁÁ

– ÁÁÁÁÁÁ

3–32ÁÁÁÁÁÁ

3–32 ÁÁÁÁÁÁ

– ÁÁÁÁÁÁ

– ÁÁÁÁÁÁ

* ÁÁÁÁÁÁÁÁ

115 ÁÁÁÁÁÁÁÁ

17 ÁÁÁÁÁÁ

24

ÁÁÁÁÁÁÁÁ

w/Type 6 ÁÁÁÁÁÁÁÁÁÁ

SW/AS/DSP/TP 1099ÁÁÁÁÁÁÁÁ

2 ÁÁÁÁÁÁ

4 ÁÁÁÁÁÁ

3 ÁÁÁÁÁÁ

– ÁÁÁÁÁÁ

3–32 ÁÁÁÁÁÁ

– ÁÁÁÁÁÁ

– ÁÁÁÁÁÁ

* ÁÁÁÁÁÁÁÁ

tbd ÁÁÁÁÁÁÁÁ

17 ÁÁÁÁÁÁ

24

ÁÁÁÁÁÁÁÁ

software ÁÁÁÁÁÁÁÁÁÁ

ÁÁÁÁÁÁÁÁ

5 ÁÁÁÁÁÁ

1 ÁÁÁÁÁÁ

3 ÁÁÁÁÁÁ

– ÁÁÁÁÁÁ

3–32 ÁÁÁÁÁÁ

– ÁÁÁÁÁÁ

– ÁÁÁÁÁÁ

* ÁÁÁÁÁÁÁÁ

tbd ÁÁÁÁÁÁÁÁ

17 ÁÁÁÁÁÁ

24ÁÁÁÁÁÁÁÁw/Type 7

ÁÁÁÁÁÁÁÁÁÁSW/AS/SNA/FR 1P99

ÁÁÁÁÁÁÁÁ2

ÁÁÁÁÁÁ4ÁÁÁÁÁÁ–ÁÁÁÁÁÁ3–32ÁÁÁÁÁÁ–ÁÁÁÁÁÁ9ÁÁÁÁÁÁ9ÁÁÁÁÁÁ*ÁÁÁÁÁÁÁÁ323

ÁÁÁÁÁÁÁÁ14

ÁÁÁÁÁÁ24ÁÁÁÁ

ÁÁÁÁsoftwareÁÁÁÁÁÁÁÁÁÁ

ÁÁÁÁÁÁÁÁ

5ÁÁÁÁÁÁ

1ÁÁÁÁÁÁ

–ÁÁÁÁÁÁ

3–32ÁÁÁÁÁÁ

–ÁÁÁÁÁÁ

9ÁÁÁÁÁÁ

9ÁÁÁÁÁÁ

*ÁÁÁÁÁÁÁÁ

293ÁÁÁÁÁÁÁÁ

14ÁÁÁÁÁÁ

24

NOTES: 1. For model numbers with x9 (such as 12x9), x=0 for EPROM memory and x=9 for Flash memory.

2. FRI = 2, for each port configuration.

Page 80: ACP Functional Description Manual.pdf

ACP Functional Description, May 1998 72

Table 15. ACP 50 Functional Characteristics – Version 1.13

Ports Connection Type Logical Channels Enable Key Levels

Personality Kitand Model Number

Min/MaxSync

Min/MaxAsync

MaxTPP

PU–LU CU–DEV

DLCISwitched

DLCIFRAD

Minw/2MB Mem

Minw/4MB Mem

Protocol Feature

ÁÁÁÁÁÁÁSW/AS/SNA/DSP 5909ÁÁÁ8ÁÁÁÁ16/32 ÁÁÁ– ÁÁÁ4–4 ÁÁÁ4–4 ÁÁÁ– ÁÁÁ– ÁÁÁÁ2000 ÁÁÁ2400ÁÁÁÁ17 ÁÁÁ–ÁÁÁÁÁÁÁÁÁÁÁÁÁÁ

ÁÁÁÁÁÁ

8ÁÁÁÁÁÁÁÁ

16/32ÁÁÁÁÁÁ

–ÁÁÁÁÁÁ

24–24ÁÁÁÁÁÁ

8–24ÁÁÁÁÁÁ

–ÁÁÁÁÁÁ

–ÁÁÁÁÁÁÁÁ

2000ÁÁÁÁÁÁ

2400ÁÁÁÁÁÁÁÁ

17ÁÁÁÁÁÁ

6ÁÁÁÁÁÁÁÁÁÁÁÁÁÁ

ÁÁÁÁÁÁ

8ÁÁÁÁÁÁÁÁ

16/32ÁÁÁÁÁÁ

–ÁÁÁÁÁÁ

32–96ÁÁÁÁÁÁ

8–32ÁÁÁÁÁÁ

–ÁÁÁÁÁÁ

–ÁÁÁÁÁÁÁÁ

2000ÁÁÁÁÁÁ

2400ÁÁÁÁÁÁÁÁ

17ÁÁÁÁÁÁ

14

ÁÁÁÁÁÁÁÁÁÁÁÁÁÁ

ÁÁÁÁÁÁ

16ÁÁÁÁÁÁÁÁ

0/16 ÁÁÁÁÁÁ

– ÁÁÁÁÁÁ

4–4 ÁÁÁÁÁÁ

4–4 ÁÁÁÁÁÁ

– ÁÁÁÁÁÁ

– ÁÁÁÁÁÁÁÁ

2000 ÁÁÁÁÁÁ

2400ÁÁÁÁÁÁÁÁ

17 ÁÁÁÁÁÁ

ÁÁÁÁÁÁÁÁÁÁÁÁÁÁ

ÁÁÁÁÁÁ

16ÁÁÁÁÁÁÁÁ

0/16 ÁÁÁÁÁÁ

– ÁÁÁÁÁÁ

24–24ÁÁÁÁÁÁ

8–24ÁÁÁÁÁÁ

– ÁÁÁÁÁÁ

– ÁÁÁÁÁÁÁÁ

2000 ÁÁÁÁÁÁ

2400ÁÁÁÁÁÁÁÁ

17 ÁÁÁÁÁÁ

6

ÁÁÁÁÁÁÁÁÁÁ16ÁÁÁÁ0/16 ÁÁÁ– ÁÁÁ32–96ÁÁÁ8–32ÁÁÁ– ÁÁÁ– ÁÁÁÁ2000 ÁÁÁ2400ÁÁÁÁ17 ÁÁÁ14ÁÁÁÁÁÁÁÁÁÁÁÁÁÁ

ÁÁÁÁÁÁ

24ÁÁÁÁÁÁÁÁ

–ÁÁÁÁÁÁ

–ÁÁÁÁÁÁ

4–4ÁÁÁÁÁÁ

4–4ÁÁÁÁÁÁ

–ÁÁÁÁÁÁ

–ÁÁÁÁÁÁÁÁ

2000ÁÁÁÁÁÁ

2400ÁÁÁÁÁÁÁÁ

17ÁÁÁÁÁÁ

ÁÁÁÁÁÁÁÁÁÁÁÁÁÁ

ÁÁÁÁÁÁ

24ÁÁÁÁÁÁÁÁ

– ÁÁÁÁÁÁ

– ÁÁÁÁÁÁ

24–24ÁÁÁÁÁÁ

8–24ÁÁÁÁÁÁ

– ÁÁÁÁÁÁ

– ÁÁÁÁÁÁÁÁ

2000 ÁÁÁÁÁÁ

2400ÁÁÁÁÁÁÁÁ

17 ÁÁÁÁÁÁ

6

ÁÁÁÁÁÁÁÁÁÁÁÁÁÁ

ÁÁÁÁÁÁ

24ÁÁÁÁÁÁÁÁ

– ÁÁÁÁÁÁ

– ÁÁÁÁÁÁ

32–96ÁÁÁÁÁÁ

8–32ÁÁÁÁÁÁ

– ÁÁÁÁÁÁ

– ÁÁÁÁÁÁÁÁ

2000 ÁÁÁÁÁÁ

2400ÁÁÁÁÁÁÁÁ

17 ÁÁÁÁÁÁ

14

ÁÁÁÁÁÁÁSW/AS/SNA/TP 5J09ÁÁÁ8ÁÁÁÁ16/32 ÁÁÁ24 ÁÁÁ8–8 ÁÁÁ– ÁÁÁ– ÁÁÁ– ÁÁÁÁ2000 ÁÁÁ2400ÁÁÁÁ14 ÁÁÁ–ÁÁÁÁÁÁÁÁÁÁÁÁÁÁ

ÁÁÁÁÁÁ

8ÁÁÁÁÁÁÁÁ

16/32ÁÁÁÁÁÁ

24ÁÁÁÁÁÁ

16–48ÁÁÁÁÁÁ

–ÁÁÁÁÁÁ

–ÁÁÁÁÁÁ

–ÁÁÁÁÁÁÁÁ

2000ÁÁÁÁÁÁ

2400ÁÁÁÁÁÁÁÁ

14ÁÁÁÁÁÁ

6ÁÁÁÁÁÁÁÁÁÁÁÁÁÁ

ÁÁÁÁÁÁ

8ÁÁÁÁÁÁÁÁ

16/32 ÁÁÁÁÁÁ

24 ÁÁÁÁÁÁ

16–192ÁÁÁÁÁÁ

– ÁÁÁÁÁÁ

– ÁÁÁÁÁÁ

– ÁÁÁÁÁÁÁÁ

2000 ÁÁÁÁÁÁ

2400ÁÁÁÁÁÁÁÁ

14 ÁÁÁÁÁÁ

14

ÁÁÁÁÁÁÁÁÁÁÁÁÁÁ

ÁÁÁÁÁÁ

16ÁÁÁÁÁÁÁÁ

0/16 ÁÁÁÁÁÁ

24 ÁÁÁÁÁÁ

8–8 ÁÁÁÁÁÁ

– ÁÁÁÁÁÁ

– ÁÁÁÁÁÁ

– ÁÁÁÁÁÁÁÁ

2000 ÁÁÁÁÁÁ

2400ÁÁÁÁÁÁÁÁ

14 ÁÁÁÁÁÁ

ÁÁÁÁÁÁÁÁÁÁ16ÁÁÁÁ0/16 ÁÁÁ24 ÁÁÁ16–48ÁÁÁ– ÁÁÁ– ÁÁÁ– ÁÁÁÁ2000 ÁÁÁ2400ÁÁÁÁ14 ÁÁÁ6ÁÁÁÁÁÁÁÁÁÁÁÁÁÁ

ÁÁÁÁÁÁ

16ÁÁÁÁÁÁÁÁ

0/16ÁÁÁÁÁÁ

24ÁÁÁÁÁÁ

16–192ÁÁÁÁÁÁ

–ÁÁÁÁÁÁ

–ÁÁÁÁÁÁ

–ÁÁÁÁÁÁÁÁ

2000ÁÁÁÁÁÁ

2400ÁÁÁÁÁÁÁÁ

14ÁÁÁÁÁÁ

14ÁÁÁÁÁÁÁÁÁÁÁÁÁÁ

ÁÁÁÁÁÁ

24ÁÁÁÁÁÁÁÁ

– ÁÁÁÁÁÁ

24 ÁÁÁÁÁÁ

8–8 ÁÁÁÁÁÁ

– ÁÁÁÁÁÁ

– ÁÁÁÁÁÁ

– ÁÁÁÁÁÁÁÁ

2000 ÁÁÁÁÁÁ

2400ÁÁÁÁÁÁÁÁ

14 ÁÁÁÁÁÁ

ÁÁÁÁÁÁÁÁÁÁÁÁÁÁ

ÁÁÁÁÁÁ

24ÁÁÁÁÁÁÁÁ

– ÁÁÁÁÁÁ

24 ÁÁÁÁÁÁ

16–48ÁÁÁÁÁÁ

– ÁÁÁÁÁÁ

– ÁÁÁÁÁÁ

– ÁÁÁÁÁÁÁÁ

2000 ÁÁÁÁÁÁ

2400ÁÁÁÁÁÁÁÁ

14 ÁÁÁÁÁÁ

6

ÁÁÁÁÁÁÁSW/AS/DSP/TP 50A9ÁÁÁ8ÁÁÁÁ16/32 ÁÁÁ24 ÁÁÁ– ÁÁÁ8–8 ÁÁÁ– ÁÁÁ– ÁÁÁÁ2000 ÁÁÁ2400ÁÁÁÁ17 ÁÁÁ–ÁÁÁÁÁÁÁÁÁÁÁÁÁÁ

ÁÁÁÁÁÁ16ÁÁÁÁÁÁÁÁ0/16

ÁÁÁÁÁÁ24ÁÁÁÁÁÁ–ÁÁÁÁÁÁ16–48ÁÁÁÁÁÁ–ÁÁÁÁÁÁ–ÁÁÁÁÁÁÁÁ2000

ÁÁÁÁÁÁ2400ÁÁÁÁÁÁÁÁ17

ÁÁÁÁÁÁ6ÁÁÁÁÁÁÁ

ÁÁÁÁÁÁÁ

ÁÁÁÁÁÁ

24ÁÁÁÁÁÁÁÁ

–ÁÁÁÁÁÁ

24ÁÁÁÁÁÁ

–ÁÁÁÁÁÁ

16–64ÁÁÁÁÁÁ

–ÁÁÁÁÁÁ

–ÁÁÁÁÁÁÁÁ

2000ÁÁÁÁÁÁ

2400ÁÁÁÁÁÁÁÁ

17ÁÁÁÁÁÁ

14

ÁÁÁÁÁÁÁÁÁÁÁÁÁÁ

SW/TP/FR/IP 5E09ÁÁÁÁÁÁ

10/26ÁÁÁÁÁÁÁÁ

– ÁÁÁÁÁÁ

24 ÁÁÁÁÁÁ

– ÁÁÁÁÁÁ

– ÁÁÁÁÁÁ

128 ÁÁÁÁÁÁ

28 ÁÁÁÁÁÁÁÁ

2000 ÁÁÁÁÁÁ

2400ÁÁÁÁÁÁÁÁ

9 ÁÁÁÁÁÁ

ÁÁÁÁÁÁÁÁÁÁÁÁÁÁ

SW/AS/TP/IP 5399ÁÁÁÁÁÁ

10/26ÁÁÁÁÁÁÁÁ

– ÁÁÁÁÁÁ

24 ÁÁÁÁÁÁ

– ÁÁÁÁÁÁ

– ÁÁÁÁÁÁ

128 ÁÁÁÁÁÁ

28 ÁÁÁÁÁÁÁÁ

2000 ÁÁÁÁÁÁ

2400ÁÁÁÁÁÁÁÁ

11 ÁÁÁÁÁÁ

ÁÁÁÁÁÁÁSW/AS/SNA/FR/IP 5G09ÁÁÁ10ÁÁÁÁ16/32 ÁÁÁ– ÁÁÁ8–8 ÁÁÁ– ÁÁÁ128 ÁÁÁ28 ÁÁÁÁ1200 ÁÁÁ1500ÁÁÁÁ14 ÁÁÁ–ÁÁÁÁÁÁÁÁÁÁÁÁÁÁ

ÁÁÁÁÁÁ

10ÁÁÁÁÁÁÁÁ

16/32ÁÁÁÁÁÁ

–ÁÁÁÁÁÁ

8–48ÁÁÁÁÁÁ

–ÁÁÁÁÁÁ

128ÁÁÁÁÁÁ

28ÁÁÁÁÁÁÁÁ

1200ÁÁÁÁÁÁ

1500ÁÁÁÁÁÁÁÁ

14ÁÁÁÁÁÁ

6ÁÁÁÁÁÁÁÁÁÁÁÁÁÁ

ÁÁÁÁÁÁ

10ÁÁÁÁÁÁÁÁ

16/32 ÁÁÁÁÁÁ

– ÁÁÁÁÁÁ

8–64 ÁÁÁÁÁÁ

– ÁÁÁÁÁÁ

128 ÁÁÁÁÁÁ

28 ÁÁÁÁÁÁÁÁ

1200 ÁÁÁÁÁÁ

1500ÁÁÁÁÁÁÁÁ

14 ÁÁÁÁÁÁ

14

ÁÁÁÁÁÁÁÁÁÁÁÁÁÁ

ÁÁÁÁÁÁ

18ÁÁÁÁÁÁÁÁ

0/16 ÁÁÁÁÁÁ

– ÁÁÁÁÁÁ

8–8 ÁÁÁÁÁÁ

– ÁÁÁÁÁÁ

128 ÁÁÁÁÁÁ

28 ÁÁÁÁÁÁÁÁ

1200 ÁÁÁÁÁÁ

1500ÁÁÁÁÁÁÁÁ

14 ÁÁÁÁÁÁ

ÁÁÁÁÁÁÁÁÁÁ18ÁÁÁÁ0/16 ÁÁÁ– ÁÁÁ8–48 ÁÁÁ– ÁÁÁ128 ÁÁÁ28 ÁÁÁÁ1200 ÁÁÁ1500ÁÁÁÁ14 ÁÁÁ6ÁÁÁÁÁÁÁÁÁÁÁÁÁÁ

ÁÁÁÁÁÁ

18ÁÁÁÁÁÁÁÁ

0/16ÁÁÁÁÁÁ

–ÁÁÁÁÁÁ

8–64ÁÁÁÁÁÁ

–ÁÁÁÁÁÁ

128ÁÁÁÁÁÁ

28ÁÁÁÁÁÁÁÁ

1200ÁÁÁÁÁÁ

1500ÁÁÁÁÁÁÁÁ

14ÁÁÁÁÁÁ

14ÁÁÁÁÁÁÁÁÁÁÁÁÁÁ

ÁÁÁÁÁÁ

26ÁÁÁÁÁÁÁÁ

– ÁÁÁÁÁÁ

– ÁÁÁÁÁÁ

8–8 ÁÁÁÁÁÁ

– ÁÁÁÁÁÁ

128 ÁÁÁÁÁÁ

28 ÁÁÁÁÁÁÁÁ

1200 ÁÁÁÁÁÁ

1500ÁÁÁÁÁÁÁÁ

14 ÁÁÁÁÁÁ

ÁÁÁÁÁÁÁÁÁÁÁÁÁÁ

ÁÁÁÁÁÁ

26ÁÁÁÁÁÁÁÁ

– ÁÁÁÁÁÁ

– ÁÁÁÁÁÁ

8–48 ÁÁÁÁÁÁ

– ÁÁÁÁÁÁ

128 ÁÁÁÁÁÁ

28 ÁÁÁÁÁÁÁÁ

1200 ÁÁÁÁÁÁ

1500ÁÁÁÁÁÁÁÁ

14 ÁÁÁÁÁÁ

6

ÁÁÁÁÁÁÁSW/AS/SNA/BR 5Ax9ÁÁÁ8ÁÁÁÁ16/32 ÁÁÁ– ÁÁÁ8–8 ÁÁÁ– ÁÁÁ– ÁÁÁ– ÁÁÁÁ2000 ÁÁÁ2400ÁÁÁÁ14 ÁÁÁ–ÁÁÁÁÁÁÁÁÁÁÁÁÁÁ

ÁÁÁÁÁÁ

8ÁÁÁÁÁÁÁÁ

16/32ÁÁÁÁÁÁ

–ÁÁÁÁÁÁ

16–48ÁÁÁÁÁÁ

–ÁÁÁÁÁÁ

–ÁÁÁÁÁÁ

–ÁÁÁÁÁÁÁÁ

2000ÁÁÁÁÁÁ

2400ÁÁÁÁÁÁÁÁ

14ÁÁÁÁÁÁ

6ÁÁÁÁÁÁÁÁÁÁÁÁÁÁ

ÁÁÁÁÁÁ

8ÁÁÁÁÁÁÁÁ

16/32 ÁÁÁÁÁÁ

– ÁÁÁÁÁÁ

16–192ÁÁÁÁÁÁ

– ÁÁÁÁÁÁ

– ÁÁÁÁÁÁ

– ÁÁÁÁÁÁÁÁ

2000 ÁÁÁÁÁÁ

2400ÁÁÁÁÁÁÁÁ

14 ÁÁÁÁÁÁ

14

ÁÁÁÁÁÁÁÁÁÁÁÁÁÁ

ÁÁÁÁÁÁ

16ÁÁÁÁÁÁÁÁ

0/16 ÁÁÁÁÁÁ

– ÁÁÁÁÁÁ

8–8 ÁÁÁÁÁÁ

– ÁÁÁÁÁÁ

– ÁÁÁÁÁÁ

– ÁÁÁÁÁÁÁÁ

2000 ÁÁÁÁÁÁ

2400ÁÁÁÁÁÁÁÁ

14 ÁÁÁÁÁÁ

ÁÁÁÁÁÁÁÁÁÁ16ÁÁÁÁ0/16 ÁÁÁ– ÁÁÁ16–48ÁÁÁ– ÁÁÁ– ÁÁÁ– ÁÁÁÁ2000 ÁÁÁ2400ÁÁÁÁ14 ÁÁÁ6ÁÁÁÁÁÁÁÁÁÁÁÁÁÁ

ÁÁÁÁÁÁ16ÁÁÁÁÁÁÁÁ0/16

ÁÁÁÁÁÁ–ÁÁÁÁÁÁ16–192ÁÁÁÁÁÁ–ÁÁÁÁÁÁ–ÁÁÁÁÁÁ–ÁÁÁÁÁÁÁÁ2000

ÁÁÁÁÁÁ2400ÁÁÁÁÁÁÁÁ14

ÁÁÁÁÁÁ14ÁÁÁÁÁÁÁ

ÁÁÁÁÁÁÁÁÁÁÁÁÁ

24ÁÁÁÁÁÁÁÁ

–ÁÁÁÁÁÁ

–ÁÁÁÁÁÁ

8–8ÁÁÁÁÁÁ

–ÁÁÁÁÁÁ

–ÁÁÁÁÁÁ

–ÁÁÁÁÁÁÁÁ

2000ÁÁÁÁÁÁ

2400ÁÁÁÁÁÁÁÁ

14ÁÁÁÁÁÁ

ÁÁÁÁÁÁÁÁÁÁÁÁÁÁ

ÁÁÁÁÁÁ

24ÁÁÁÁÁÁÁÁ

– ÁÁÁÁÁÁÁÁÁÁÁÁ

16–48ÁÁÁÁÁÁ

– ÁÁÁÁÁÁ

– ÁÁÁÁÁÁ

– ÁÁÁÁÁÁÁÁ

2000 ÁÁÁÁÁÁ

2400ÁÁÁÁÁÁÁÁ

14 ÁÁÁÁÁÁ

6

ÁÁÁÁÁÁÁÁÁÁÁÁÁÁ

ÁÁÁÁÁÁ

24ÁÁÁÁÁÁÁÁ

– ÁÁÁÁÁÁÁÁÁÁÁÁ

16–192ÁÁÁÁÁÁ

– ÁÁÁÁÁÁ

– ÁÁÁÁÁÁ

– ÁÁÁÁÁÁÁÁ

2000 ÁÁÁÁÁÁ

2400ÁÁÁÁÁÁÁÁ

14 ÁÁÁÁÁÁ

14

ÁÁÁÁÁÁÁSW/AS/SNA/TP/BR 5Bx9ÁÁÁ8ÁÁÁÁ16/32 ÁÁÁ24 ÁÁÁ8–8 ÁÁÁ– ÁÁÁ– ÁÁÁ– ÁÁÁÁ1200 ÁÁÁ1500ÁÁÁÁ17 ÁÁÁ0ÁÁÁÁÁÁÁÁÁÁÁÁÁÁ

ÁÁÁÁÁÁ

8ÁÁÁÁÁÁÁÁ

16/32ÁÁÁÁÁÁ

24ÁÁÁÁÁÁ

8–8ÁÁÁÁÁÁ

–ÁÁÁÁÁÁ

–ÁÁÁÁÁÁ

–ÁÁÁÁÁÁÁÁ

1200ÁÁÁÁÁÁ

1500ÁÁÁÁÁÁÁÁ

17ÁÁÁÁÁÁ

0ÁÁÁÁÁÁÁÁÁÁÁÁÁÁ

ÁÁÁÁÁÁ

8ÁÁÁÁÁÁÁÁ

16/32 ÁÁÁÁÁÁ

24 ÁÁÁÁÁÁ

8–8 ÁÁÁÁÁÁ

– ÁÁÁÁÁÁ

– ÁÁÁÁÁÁ

– ÁÁÁÁÁÁÁÁ

1200 ÁÁÁÁÁÁ

1500ÁÁÁÁÁÁÁÁ

17 ÁÁÁÁÁÁ

0

ÁÁÁÁÁÁÁÁÁÁÁÁÁÁ

ÁÁÁÁÁÁ

16ÁÁÁÁÁÁÁÁ

0/16 ÁÁÁÁÁÁ

24 ÁÁÁÁÁÁ

8–48 ÁÁÁÁÁÁ

– ÁÁÁÁÁÁ

– ÁÁÁÁÁÁ

– ÁÁÁÁÁÁÁÁ

1200 ÁÁÁÁÁÁ

1500ÁÁÁÁÁÁÁÁ

17 ÁÁÁÁÁÁ

6

ÁÁÁÁÁÁÁÁÁÁ16ÁÁÁÁ0/16 ÁÁÁ24 ÁÁÁ8–48 ÁÁÁ– ÁÁÁ– ÁÁÁ– ÁÁÁÁ1200 ÁÁÁ1500ÁÁÁÁ17 ÁÁÁ6ÁÁÁÁÁÁÁÁÁÁÁÁÁÁ

ÁÁÁÁÁÁ

16ÁÁÁÁÁÁÁÁ

0/16ÁÁÁÁÁÁ

24ÁÁÁÁÁÁ

8–48ÁÁÁÁÁÁ

–ÁÁÁÁÁÁ

–ÁÁÁÁÁÁ

–ÁÁÁÁÁÁÁÁ

1200ÁÁÁÁÁÁ

1500ÁÁÁÁÁÁÁÁ

17ÁÁÁÁÁÁ

6ÁÁÁÁÁÁÁÁÁÁÁÁÁÁ

ÁÁÁÁÁÁ

24ÁÁÁÁÁÁÁÁ

– ÁÁÁÁÁÁ

24 ÁÁÁÁÁÁ

16–192ÁÁÁÁÁÁ

– ÁÁÁÁÁÁ

– ÁÁÁÁÁÁ

– ÁÁÁÁÁÁÁÁ

1200 ÁÁÁÁÁÁ

1500ÁÁÁÁÁÁÁÁ

17 ÁÁÁÁÁÁ

14

ÁÁÁÁÁÁÁÁÁÁÁÁÁÁ

ÁÁÁÁÁÁ

24ÁÁÁÁÁÁÁÁ

– ÁÁÁÁÁÁ

24 ÁÁÁÁÁÁ

16–192ÁÁÁÁÁÁ

– ÁÁÁÁÁÁ

– ÁÁÁÁÁÁ

– ÁÁÁÁÁÁÁÁ

1200 ÁÁÁÁÁÁ

1500ÁÁÁÁÁÁÁÁ

17 ÁÁÁÁÁÁ

14

NOTE: Version 1.xx requires a minimum of 2 MB of memory.

Page 81: ACP Functional Description Manual.pdf

ACP Functional Description, May 1998 73

Table 15. ACP 50 Functional Characteristics – Version 1.13 (continued)Ports Connection Type Logical Channels Enable Key Levels

Personality Kitand Model Number

Min/MaxSync

Min/MaxAsync

MaxTPP

PU–LU CU–DEV

DLCISwitched

DLCIFRAD

Minw/2MB Mem

Minw/4MB Mem

ProtocolKey

FeatureKey

ÁÁÁÁÁÁÁÁÁÁÁÁÁÁ

SW/AS/TP/FR/BR 5Cx9ÁÁÁÁÁÁ

8ÁÁÁÁÁÁÁÁ

16/32 ÁÁÁÁÁÁ

24 ÁÁÁÁÁÁ

– ÁÁÁÁÁÁ

– ÁÁÁÁÁÁ

128 ÁÁÁÁÁÁ

28 ÁÁÁÁÁÁÁÁ

1200 ÁÁÁÁÁÁ

1500ÁÁÁÁÁÁÁÁ

17 ÁÁÁÁÁÁ

ÁÁÁÁÁÁÁÁÁÁ16ÁÁÁÁ16 ÁÁÁ24 ÁÁÁ– ÁÁÁ– ÁÁÁ128 ÁÁÁ28 ÁÁÁÁ1200 ÁÁÁ1500ÁÁÁÁ17 ÁÁÁ–ÁÁÁÁÁÁÁÁÁÁÁÁÁÁ

ÁÁÁÁÁÁ

24ÁÁÁÁÁÁÁÁ

–ÁÁÁÁÁÁ

24ÁÁÁÁÁÁ

–ÁÁÁÁÁÁ

–ÁÁÁÁÁÁ

128ÁÁÁÁÁÁ

28ÁÁÁÁÁÁÁÁ

1200ÁÁÁÁÁÁ

1500ÁÁÁÁÁÁÁÁ

17ÁÁÁÁÁÁ

–ÁÁÁÁÁÁÁÁÁÁÁÁÁÁ

SW/AS/SNA/DSP/FR 5R09ÁÁÁÁÁÁ

8ÁÁÁÁÁÁÁÁ

16/32 ÁÁÁÁÁÁ

– ÁÁÁÁÁÁ

4–4 ÁÁÁÁÁÁ

4–4 ÁÁÁÁÁÁ

– ÁÁÁÁÁÁ

– ÁÁÁÁÁÁÁÁ

2000 ÁÁÁÁÁÁ

2400ÁÁÁÁÁÁÁÁ

17 ÁÁÁÁÁÁ

ÁÁÁÁÁÁÁÁÁÁÁÁÁÁ

ÁÁÁÁÁÁ

8ÁÁÁÁÁÁÁÁ

16/32 ÁÁÁÁÁÁ

– ÁÁÁÁÁÁ

24–24ÁÁÁÁÁÁ

8–24ÁÁÁÁÁÁ

– ÁÁÁÁÁÁ

– ÁÁÁÁÁÁÁÁ

2000 ÁÁÁÁÁÁ

2400ÁÁÁÁÁÁÁÁ

17 ÁÁÁÁÁÁ

6

ÁÁÁÁÁÁÁÁÁÁ8ÁÁÁÁ16/32 ÁÁÁ– ÁÁÁ32–96ÁÁÁ8–32ÁÁÁ– ÁÁÁ– ÁÁÁÁ2000 ÁÁÁ2400ÁÁÁÁ17 ÁÁÁ14ÁÁÁÁÁÁÁÁÁÁÁÁÁÁ

ÁÁÁÁÁÁ

16ÁÁÁÁÁÁÁÁ

0/16ÁÁÁÁÁÁ

–ÁÁÁÁÁÁ

4–4ÁÁÁÁÁÁ

4–4ÁÁÁÁÁÁ

–ÁÁÁÁÁÁ

–ÁÁÁÁÁÁÁÁ

2000ÁÁÁÁÁÁ

2400ÁÁÁÁÁÁÁÁ

17ÁÁÁÁÁÁ

–ÁÁÁÁÁÁÁÁÁÁÁÁÁÁ

ÁÁÁÁÁÁ

16ÁÁÁÁÁÁÁÁ

0/16 ÁÁÁÁÁÁ

– ÁÁÁÁÁÁ

24–24ÁÁÁÁÁÁ

8–24ÁÁÁÁÁÁ

– ÁÁÁÁÁÁ

– ÁÁÁÁÁÁÁÁ

2000 ÁÁÁÁÁÁ

2400ÁÁÁÁÁÁÁÁ

17 ÁÁÁÁÁÁ

6

ÁÁÁÁÁÁÁÁÁÁÁÁÁÁ

ÁÁÁÁÁÁ

16ÁÁÁÁÁÁÁÁ

0/16 ÁÁÁÁÁÁ

– ÁÁÁÁÁÁ

32–96ÁÁÁÁÁÁ

8–32ÁÁÁÁÁÁ

– ÁÁÁÁÁÁ

– ÁÁÁÁÁÁÁÁ

2000 ÁÁÁÁÁÁ

2400ÁÁÁÁÁÁÁÁ

17 ÁÁÁÁÁÁ

14

ÁÁÁÁÁÁÁÁÁÁ24ÁÁÁÁ– ÁÁÁ– ÁÁÁ4–4 ÁÁÁ4–4 ÁÁÁ– ÁÁÁ– ÁÁÁÁ2000 ÁÁÁ2400ÁÁÁÁ17 ÁÁÁ–ÁÁÁÁÁÁÁÁÁÁÁÁÁÁ

ÁÁÁÁÁÁ

24ÁÁÁÁÁÁÁÁ

–ÁÁÁÁÁÁ

–ÁÁÁÁÁÁ

24–24ÁÁÁÁÁÁ

8–24ÁÁÁÁÁÁ

–ÁÁÁÁÁÁ

–ÁÁÁÁÁÁÁÁ

2000ÁÁÁÁÁÁ

2400ÁÁÁÁÁÁÁÁ

17ÁÁÁÁÁÁ

6ÁÁÁÁÁÁÁÁÁÁÁÁÁÁ

ÁÁÁÁÁÁ

24ÁÁÁÁÁÁÁÁ

– ÁÁÁÁÁÁ

– ÁÁÁÁÁÁ

32–96ÁÁÁÁÁÁ

8–32ÁÁÁÁÁÁ

– ÁÁÁÁÁÁ

– ÁÁÁÁÁÁÁÁ

2000 ÁÁÁÁÁÁ

2400ÁÁÁÁÁÁÁÁ

17 ÁÁÁÁÁÁ

14

NOTES: 1. 8M = 8 modem ports; 16M = 16 modem ports. You can have hex and octal cards included with the internal modem card, which allows a variety of async and sync port combinations.

2. For model numbers with x9 (such as 5Ax9), x=0 for ISDN NI-1 and x=1 for Euro-ISDN.

3. Version 1.xx requires a minimum of 2 MB of memory.

Table 16. ACP 50 Functional Characteristics – Version 2.xx

Ports Connection Type Logical Channels Enable Key Levels

Personality Kitand Model Number

Min/MaxSync

Min/MaxAsync

MaxTPP

PU–LU CU–DEV

DLCISwitched

DLCIFRAD

Minw/2MB Mem

Minw/4MB Mem

Protocol Feature

ÁÁÁÁÁÁÁSW/AS/FR/IP/MD 5F99ÁÁÁ2ÁÁÁÁ8M/24M ÁÁÁ– ÁÁÁ– ÁÁÁ– ÁÁÁ128 ÁÁÁ2 ÁÁÁÁ1200 ÁÁÁ1500ÁÁÁÁ11 ÁÁÁ–ÁÁÁÁÁÁÁÁÁÁÁÁÁÁ

ÁÁÁÁÁÁ

8ÁÁÁÁÁÁÁÁ

8M/16MÁÁÁÁÁÁ

–ÁÁÁÁÁÁ

–ÁÁÁÁÁÁ

–ÁÁÁÁÁÁ

128ÁÁÁÁÁÁ

8ÁÁÁÁÁÁÁÁ

1200ÁÁÁÁÁÁ

1500ÁÁÁÁÁÁÁÁ

11ÁÁÁÁÁÁ

–ÁÁÁÁÁÁÁÁÁÁÁÁÁÁ

SW/AS/SNA/DSP/TP/FR/IP/ÁÁÁÁÁÁ

2ÁÁÁÁÁÁÁÁ

8M/16M ÁÁÁÁÁÁ

– ÁÁÁÁÁÁ

36–120ÁÁÁÁÁÁ

36–255ÁÁÁÁÁÁ

128 ÁÁÁÁÁÁ

2 ÁÁÁÁÁÁÁÁ

1200 ÁÁÁÁÁÁ

1500ÁÁÁÁÁÁÁÁ

24 ÁÁÁÁÁÁ

14

ÁÁÁÁÁÁÁÁÁÁÁÁÁÁ

MD/POS 5P09ÁÁÁÁÁÁ

8ÁÁÁÁÁÁÁÁ

8M/16M ÁÁÁÁÁÁ

– ÁÁÁÁÁÁ

36–120ÁÁÁÁÁÁ

36–255ÁÁÁÁÁÁ

128 ÁÁÁÁÁÁ

8 ÁÁÁÁÁÁÁÁ

1200 ÁÁÁÁÁÁ

1500ÁÁÁÁÁÁÁÁ

24 ÁÁÁÁÁÁ

14

NOTES: 1. Version 2.xx IP includes PPP, IP Transporter, and PPP/SLIP/X.25 gateway.

2. P-kit 5P09 requires a 50/486 Type2 CPU, 8 MB of memory, and the 8 MB PCMCIA card option.

Table 17. ACP 50 Functional Characteristics – Version 4.xx

Ports Connection Type Logical Channels Enable Key Levels

Personality Kitand Model Number

Min/MaxSync

Min/MaxAsync

MaxTPP

PU–LU CU–DEV

DLCISwitched

DLCIFRAD

Minw/8MB Mem

Minw/16MB Mem

Protocol Feature

ÁÁÁÁÁÁÁÁÁÁÁÁÁÁ

SW/AS/FR/IP/MD 5F99ÁÁÁÁÁÁ

2ÁÁÁÁÁÁÁÁ

8M/24MÁÁÁÁÁÁ

–ÁÁÁÁÁÁ

–ÁÁÁÁÁÁ

–ÁÁÁÁÁÁ

128ÁÁÁÁÁÁ

28ÁÁÁÁÁÁÁÁ

4000ÁÁÁÁÁÁÁÁ

8000ÁÁÁÁÁÁ

11ÁÁÁÁÁÁ

ÁÁÁÁÁÁÁÁÁÁÁÁÁÁ

ÁÁÁÁÁÁ

8ÁÁÁÁÁÁÁÁ

8M/16M ÁÁÁÁÁÁ

– ÁÁÁÁÁÁ

– ÁÁÁÁÁÁ

– ÁÁÁÁÁÁ

128 ÁÁÁÁÁÁ

28 ÁÁÁÁÁÁÁÁ

4000 ÁÁÁÁÁÁÁÁ

8000 ÁÁÁÁÁÁ

11ÁÁÁÁÁÁ

ÁÁÁÁÁÁÁÁÁÁÁÁÁÁ

SW/AS/SNA/FR/IP 5G09ÁÁÁÁÁÁ

10ÁÁÁÁÁÁÁÁ

16/32 ÁÁÁÁÁÁ

– ÁÁÁÁÁÁ

8–8 ÁÁÁÁÁÁ

– ÁÁÁÁÁÁ

128 ÁÁÁÁÁÁ

28 ÁÁÁÁÁÁÁÁ

4000 ÁÁÁÁÁÁÁÁ

8000 ÁÁÁÁÁÁ

14ÁÁÁÁÁÁ

ÁÁÁÁÁÁÁÁÁÁ10ÁÁÁÁ16/32 ÁÁÁ– ÁÁÁ8–48 ÁÁÁ– ÁÁÁ128 ÁÁÁ28 ÁÁÁÁ4000 ÁÁÁÁ8000 ÁÁÁ14ÁÁÁ6ÁÁÁÁÁÁÁÁÁÁÁÁÁÁ

ÁÁÁÁÁÁ

10ÁÁÁÁÁÁÁÁ

16/32ÁÁÁÁÁÁ

–ÁÁÁÁÁÁ

8–64ÁÁÁÁÁÁ

–ÁÁÁÁÁÁ

128ÁÁÁÁÁÁ

28ÁÁÁÁÁÁÁÁ

4000ÁÁÁÁÁÁÁÁ

8000ÁÁÁÁÁÁ

14ÁÁÁÁÁÁ

14ÁÁÁÁÁÁÁÁÁÁÁÁÁÁ

ÁÁÁÁÁÁ

18ÁÁÁÁÁÁÁÁ

0/16 ÁÁÁÁÁÁ

– ÁÁÁÁÁÁ

8–8 ÁÁÁÁÁÁ

– ÁÁÁÁÁÁ

128 ÁÁÁÁÁÁ

28 ÁÁÁÁÁÁÁÁ

4000 ÁÁÁÁÁÁÁÁ

8000 ÁÁÁÁÁÁ

14ÁÁÁÁÁÁ

ÁÁÁÁÁÁÁÁÁÁÁÁÁÁ

ÁÁÁÁÁÁ

18ÁÁÁÁÁÁÁÁ

0/16 ÁÁÁÁÁÁ

– ÁÁÁÁÁÁ

8–48 ÁÁÁÁÁÁ

– ÁÁÁÁÁÁ

128 ÁÁÁÁÁÁ

28 ÁÁÁÁÁÁÁÁ

4000 ÁÁÁÁÁÁÁÁ

8000 ÁÁÁÁÁÁ

14ÁÁÁÁÁÁ

6

ÁÁÁÁÁÁÁÁÁÁ18ÁÁÁÁ0/16 ÁÁÁ– ÁÁÁ8–64 ÁÁÁ– ÁÁÁ128 ÁÁÁ28 ÁÁÁÁ4000 ÁÁÁÁ8000 ÁÁÁ14ÁÁÁ14ÁÁÁÁÁÁÁÁÁÁÁÁÁÁ

ÁÁÁÁÁÁ

26ÁÁÁÁÁÁÁÁ

–ÁÁÁÁÁÁ

–ÁÁÁÁÁÁ

8–8ÁÁÁÁÁÁ

–ÁÁÁÁÁÁ

128ÁÁÁÁÁÁ

28ÁÁÁÁÁÁÁÁ

4000ÁÁÁÁÁÁÁÁ

8000ÁÁÁÁÁÁ

14ÁÁÁÁÁÁ

–ÁÁÁÁÁÁÁÁÁÁÁÁÁÁ

ÁÁÁÁÁÁ

26ÁÁÁÁÁÁÁÁ

– ÁÁÁÁÁÁ

– ÁÁÁÁÁÁ

8–48 ÁÁÁÁÁÁ

– ÁÁÁÁÁÁ

128 ÁÁÁÁÁÁ

28 ÁÁÁÁÁÁÁÁ

4000 ÁÁÁÁÁÁÁÁ

8000 ÁÁÁÁÁÁ

14ÁÁÁÁÁÁ

6

ÁÁÁÁÁÁÁÁÁÁÁÁÁÁ

SW/AS/SNA/DSP/TP/FR/IP/ÁÁÁÁÁÁ

2ÁÁÁÁÁÁÁÁ

16M/48MÁÁÁÁÁÁ

– ÁÁÁÁÁÁ

36–120ÁÁÁÁÁÁ

36–255ÁÁÁÁÁÁ

128 ÁÁÁÁÁÁ

28 ÁÁÁÁÁÁÁÁ

4000 ÁÁÁÁÁÁÁÁ

8000 ÁÁÁÁÁÁ

17ÁÁÁÁÁÁ

14

ÁÁÁÁÁÁÁÁÁÁÁÁÁÁ

MD 5H09ÁÁÁÁÁÁ

8ÁÁÁÁÁÁÁÁ

16M/32MÁÁÁÁÁÁ

– ÁÁÁÁÁÁ

36–120ÁÁÁÁÁÁ

36–255ÁÁÁÁÁÁ

128 ÁÁÁÁÁÁ

28 ÁÁÁÁÁÁÁÁ

4000 ÁÁÁÁÁÁÁÁ

8000 ÁÁÁÁÁÁ

17ÁÁÁÁÁÁ

14

ÁÁÁÁÁÁÁSW/AS/TP/FR/IP 5B99ÁÁÁ2ÁÁÁÁ16M/48MÁÁÁ– ÁÁÁ– ÁÁÁ– ÁÁÁ128 ÁÁÁ28 ÁÁÁÁ4000 ÁÁÁÁ8000 ÁÁÁ17ÁÁÁ14ÁÁÁÁÁÁÁÁÁÁÁÁÁÁ

ÁÁÁÁÁÁ

8ÁÁÁÁÁÁÁÁ

16M/32MÁÁÁÁÁÁ

–ÁÁÁÁÁÁ

–ÁÁÁÁÁÁ

–ÁÁÁÁÁÁ

128ÁÁÁÁÁÁ

28ÁÁÁÁÁÁÁÁ

4000ÁÁÁÁÁÁÁÁ

8000ÁÁÁÁÁÁ

17ÁÁÁÁÁÁ

14

NOTES: 1. Version 4.0 software includes support of PAP/CHAP/RADIUS, T1/E1 CSU/DSU hardware, dual 48VDC power supplies, and the Automatic Node Protection Switching (ANPS) feature. Version 4.0 also supports OSPF routing, TELNET, FTP, and SNMP. Version 4.0 software requires a 50/486 Type2 CPU, a minimum of 8 MB of memory, an ELX II CEM, and the 8 MB PCMCIA card option. If CSU/DSU operation is used, then a 50/486 Type2 C/D CPU is required.

2. With Version 4.1 software, the SNA module of software p-kit 5H09 delivers 48 PUs with enable key 14.

Page 82: ACP Functional Description Manual.pdf

ACP Functional Description, May 1998 74

Table 18. ACP 70 Functional Characteristics – Version 2.xx

Ports Connection Type Logical Channels Enable Key Levels

ACPPlatform

Personality Kitand Model Number

Min/MaxSync

Min/MaxAsync

MaxTPP PU–LU CU–DEV

DLCISwitched

DLCIFRAD

Min (1)

w/8MB MemMin

w/16MB Mem Protocol Feature

ÁÁÁÁw/Type P ÁÁÁÁÁÁSW/AS/SNA/DSP/TP/FR/IP/ÁÁÁÁ6/14 ÁÁÁ– ÁÁ24ÁÁÁ36–255ÁÁÁ4–32ÁÁÁÁ128 ÁÁÁ78 ÁÁÁÁ1200 ÁÁÁÁ1500 ÁÁÁ24 ÁÁÁ14ÁÁÁÁÁÁÁÁ

softwareÁÁÁÁÁÁÁÁÁÁÁÁ

BR/POS (ISDN NI–1) 7P09ÁÁÁÁÁÁÁÁ

6/14ÁÁÁÁÁÁ

–ÁÁÁÁ

24ÁÁÁÁÁÁ

36–255ÁÁÁÁÁÁ

36–255ÁÁÁÁÁÁÁÁ

128ÁÁÁÁÁÁ

78ÁÁÁÁÁÁÁÁ

1200ÁÁÁÁÁÁÁÁ

1500ÁÁÁÁÁÁ

24ÁÁÁÁÁÁ

14ÁÁÁÁÁÁÁÁ

ÁÁÁÁÁÁÁÁÁÁÁÁ

SW/AS/SNA/DSP/TP/FR/IP/ÁÁÁÁÁÁÁÁ

6/14ÁÁÁÁÁÁ

–ÁÁÁÁ

24ÁÁÁÁÁÁ

36–255ÁÁÁÁÁÁ

4–32ÁÁÁÁÁÁÁÁ

128ÁÁÁÁÁÁ

78ÁÁÁÁÁÁÁÁ

1200ÁÁÁÁÁÁÁÁ

1500ÁÁÁÁÁÁ

24ÁÁÁÁÁÁ

14

ÁÁÁÁÁÁÁÁÁÁÁÁ

ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ

BR/POS

(Euro ISDN/1TR6/VN3)

ÁÁÁÁÁÁÁÁÁÁÁÁ

6/14 ÁÁÁÁÁÁÁÁÁ

– ÁÁÁÁÁÁ

24ÁÁÁÁÁÁÁÁÁ

36–255ÁÁÁÁÁÁÁÁÁ

36–255ÁÁÁÁÁÁÁÁÁÁÁÁ

128 ÁÁÁÁÁÁÁÁÁ

78 ÁÁÁÁÁÁÁÁÁÁÁÁ

1200 ÁÁÁÁÁÁÁÁÁÁÁÁ

1500 ÁÁÁÁÁÁÁÁÁ

24 ÁÁÁÁÁÁÁÁÁ

14

ÁÁÁÁÁÁÁÁÁÁ7P19ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁNOTE: These p-kits require a 2 MB PCMCIA card for operational software storage. Telematics recommends the use of 8 MB of memory to ensure future upgradeability.

Table 19. ACP 70 Functional Characteristics – Version 4.xx

Ports Connection Type Logical Channels Enable Key Levels

ACPPlatform

Personality Kitand Model Number

Min/MaxSync

Min/MaxAsync

MaxTPP PU–LU CU–DEV

DLCISwitched

DLCIFRAD

Min (1)

w/8MB MemMin

w/16MB Mem Protocol Feature

ÁÁÁÁw/Type R ÁÁÁÁÁÁSW/SNA/FR/IP 7399ÁÁÁÁ6/14 ÁÁÁ– ÁÁ–ÁÁÁ36–255ÁÁÁ–ÁÁÁÁ128 ÁÁÁ78 ÁÁÁÁ4000 ÁÁÁÁ8000 ÁÁÁ9 ÁÁÁ–ÁÁÁÁÁÁÁÁ

softwareÁÁÁÁÁÁÁÁÁÁÁÁ

ÁÁÁÁÁÁÁÁ

6/14ÁÁÁÁÁÁ

–ÁÁÁÁ

–ÁÁÁÁÁÁ

36–255ÁÁÁÁÁÁ

–ÁÁÁÁÁÁÁÁ

128ÁÁÁÁÁÁ

78ÁÁÁÁÁÁÁÁ

4000ÁÁÁÁÁÁÁÁ

8000ÁÁÁÁÁÁ

9ÁÁÁÁÁÁ

6ÁÁÁÁÁÁÁÁ

w/Type HÁÁÁÁÁÁÁÁÁÁÁÁ

SW/AS/SNA/DSP/TP/IP/FR/ÁÁÁÁÁÁÁÁ

6/14ÁÁÁÁÁÁ

–ÁÁÁÁ

24ÁÁÁÁÁÁ

36–255ÁÁÁÁÁÁ

4–32ÁÁÁÁÁÁÁÁ

128ÁÁÁÁÁÁ

78ÁÁÁÁÁÁÁÁ

4000ÁÁÁÁÁÁÁÁ

8000ÁÁÁÁÁÁ

17ÁÁÁÁÁÁ

14

ÁÁÁÁÁÁÁÁ

software ÁÁÁÁÁÁÁÁÁÁÁÁ

BR (ISDN NI–1) 7H09ÁÁÁÁÁÁÁÁ

6/14 ÁÁÁÁÁÁ

– ÁÁÁÁ

24ÁÁÁÁÁÁ

36–255ÁÁÁÁÁÁ

36–255ÁÁÁÁÁÁÁÁ

128 ÁÁÁÁÁÁ

78 ÁÁÁÁÁÁÁÁ

4000 ÁÁÁÁÁÁÁÁ

8000 ÁÁÁÁÁÁ

17 ÁÁÁÁÁÁ

14

ÁÁÁÁÁÁÁÁ

ÁÁÁÁÁÁÁÁÁÁÁÁ

SW/AS/SNA/DSP/TP/IP/FR/ÁÁÁÁÁÁÁÁ

6/14 ÁÁÁÁÁÁ

– ÁÁÁÁ

24ÁÁÁÁÁÁ

36–255ÁÁÁÁÁÁ

4–32ÁÁÁÁÁÁÁÁ

128 ÁÁÁÁÁÁ

78 ÁÁÁÁÁÁÁÁ

4000 ÁÁÁÁÁÁÁÁ

8000 ÁÁÁÁÁÁ

17 ÁÁÁÁÁÁ

14

ÁÁÁÁÁÁÁÁÁÁBR (Euro ISDN/1TR6/VN3)ÁÁÁÁ6/14 ÁÁÁ– ÁÁ24ÁÁÁ36–255ÁÁÁ36–255ÁÁÁÁ128 ÁÁÁ78 ÁÁÁÁ4000 ÁÁÁÁ8000 ÁÁÁ17 ÁÁÁ14ÁÁÁÁÁÁÁÁ

ÁÁÁÁÁÁÁÁÁÁÁÁ

7H19ÁÁÁÁÁÁÁÁ

ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ

ÁÁÁÁÁÁÁÁÁÁÁÁÁÁ

ÁÁÁÁÁÁÁÁ

ÁÁÁÁÁÁÁÁÁÁÁÁ

NOTE: These p-kits require a 2 MB PCMCIA card for operational software storage. Telematics recommends the use of 8 MB of memory to ensure future upgradeability.

Page 83: ACP Functional Description Manual.pdf

ACP Functional Description, May 1998 75

Memory, Software, and Hardware Requirements

It is important to confirm that you have the memory andhardware required for the ACP platform, protocols, andinterfaces which you have purchased. Tables 20 through 22summarize software release levels, memory requirements, andsupported hardware for each personality kit.

For enable keys required , see the previous section onFunctional Characteristics.

Versions 1.0 and 2.0 are the new software versions after theVersion 10 series. The ELX, frame relay, internal modem, andISDN interfaces require the added power now available

through Versions 1.0 or 2.0 and later software . With the ACP50 and ACP 70 only, Versions 1.0 and 2.0 provide a “protectedmode” which allows the use of more than 1MB of memorywith extensive applications and processes runningsimultaneously.

Designed for future growth, a PCMCIA memory expansionslot is built into the ACP 70 motherboard as well as into theACP 50 ELX II and ISDN CEMs to support increasingsoftware storage requirements.

Table 20. ACP 10 Software and Memory Matrix (a Universal Network Access platform)

Model 2 SoftwareVersion

Software Type 3 Minimum Memory in MB 4

Personality Kit 1 FPK 10 1

SW/SNA/DSP 1199 ■ ❑ 5 .256SW/SNA 1299 ■ ❑ 2 .128

SW/AS/SNA 1399 ■ ❑ 2 .128SW/AS/DSP 1499 ■ ❑ 5 .256AS 1599 ■ ❑ 2 .128

SW/AS 1699 ■ ❑ 2 .128SW 1799 ■ ❑ 2 .128SW/DSP 1899 ■ ❑ 5 .256

SW/AS/SNA/DSP 1999 ■ ❑ 5 .256SW/AS/SNA/TP 1J99 ■ ❑ 3 .256SW/AS/TP 1M99 ■ ❑ 3 .256

SW/AS/SNA/FR * 1P99 ■ ❑ 7 * .256

NOTES: 1. Software modules: AS=asynchronous PAD, DSP=3270 BSC TPAD, FR=Frame Relay, SNA=SNA PAD, SW=X.25 switch, TP=Transparent Passthrough.

2. Model numbers are used to order personality kits. For the ACP 10, the model numbers refer to the FPK flash kit model numbers; the companion EPK EPROM kit model numbers (not included here) have the same usage/requirements as the FPK.

3. The asterisk (*) items are only available on the ACP 10 as FPK models.

4. The minimum memory reflects the memory required by a combination of the personality kit and the hardware.

Legend :■ = Currently available.❑ = Upcoming version releases (which will replace earlier releases).

Page 84: ACP Functional Description Manual.pdf

ACP Functional Description, May 1998 76

Table 21. ACP 50 Software and Hardware Matrix (a Universal Network Access platform)

Hardware SupportedACP 50 CEM/CAMs 3

Personality Kit 1 Model# 2

Octal5003

Hex5005

ELX5017-400/500

BRI5010

Modem5020/5034

SW/AS/DSP/TP 4 50A9 ■ ■ ■

SW/AS/SNA/DSP 4 5909 ■ ■ ■

SW/AS/SNA/TP/BR 4 5B09 ■ ■ ■

SW/AS/TP/FR/BR 4 5C09 ■ ■ ■

SW/AS/SNA/BR 4 5A19 ■ ■ ■

SW/AS/SNA/TP/BR 4 5B19 ■ ■ ■

SW/AS/TP/FR/BR 4 5C19 ■ ■ ■

SW/TP/IP/FR 4 5E09 ■ ■ ■

SW/AS/IP/FR/MD 5 5F99 ■ ■ ■ ■

SW/AS/SNA/IP/FR 5 5G09 ■ ■ ■

SW/AS/SNA/TP 4 5J09 ■ ■ ■

SW/AS/SNA/DSP/FR 4 5R09 ■ ■ ■

SW/AS/TP/IP 4 5399 ■ ■ ■

SW/AS/SNA/DSP/TP/FR/IP/MD 5

5H09 ■ ■ ■ ■

SW/AS/TP/FR/IP 5 5B99 ■ ■ ■

SW/AS/SNA/DSP/TP/FR/IP/MD/POS 6

5P09 ■ ■ ■ ■

NOTES: 1. Software modules: AS=asynchronous PAD, BR=ISDN Basic Rate Interface, DSP=3270 BSC TPAD, FR=Frame Relay, IP=Ethernet LAN connections, MD=internal modem, SNA=SNA PAD, SW=X.25 switch, TP=Transparent Passthrough, POS=Point of Sale.The minimum memory required for Version 1.xx software on the ACP 50 is 2 MB; it reflects the memory required by a combination of the personality kit andthe hardware.

2. Model numbers are used to order personality kits.

3. The model numbers are for CEM/CAM sets only and do not represent all the model number possibilities.

4. The current release of this software p-kit is Version 1.13.

5. Version 4.0 of this p-kit includes V.34 modem support, support of PAP/CHAP/RADIUS, T1/E1 CSU/DSU, dual 48VDC power supplies, Automatic NodeProtection Switching (ANPS), OSPF, TELNET, FTP, and SNMP. Version 4.0 software requires a 50/486 Type2 CPU, a minimum of 8 MB of memory, and the 8MB PCMCIA card option. If CSU/DSU operation is used, then a 50/486 Type2 C/D CPU is required.

6. The 5P09 p-kit is Version 2.xx software.

Legend : ■ = This personality kit uses this hardware.

Table 22. ACP 70 Software and Hardware Matrix (a Universal Network Access platform)

Hardware-Supported ACP Modules

Personality Kit 1 Model # 2 Software Type Minimum Memoryin MB 3

Quad CCM BRI Port

SW/FR/IP 7D09 R 2 ■

SW/AS/SNA/DSP/TP/FR/IP/BR 4 7H09 H 8 + PCMCIA ■ ■

SW/AS/SNA/DSP/TP/FR/IP/BR 4 7H19 H 8+ PCMCIA ■ ■

SW/AS/SNA/FR/IP 4 7399 R 2 ■

SW/AS/SNA/IP/DSP 7499 E 2 ■

SW/AS/SNA/DSP/TP/FR/IP/BR/POS 5

7P09 P 2 ■ ■

SW/AS/SNA/DSP/TP/FR/IP/BR/POS 5

7P19 P 2 ■ ■

NOTES: 1. Software modules: AS=asynchronous PAD, BR=ISDN Basic Rate Interface, DSP=3270 BSC TPAD, FR=Frame Relay, IP=Ethernet LAN connections,SNA=SNA PAD, SW=X.25 switch, TP=Transparent Passthrough.The ACP 70 requires Version 2.xx or higher software.

2. Model numbers are used to order personality kits.3. The minimum memory reflects the memory required by a combination of the personality kit and the hardware.4. Version 4.0 of this p-kit requires a 2 MB PCMCIA card for operational software storage. Telematics recommends the use of 8 MB of memory to ensure future

upgradeability.5. These p-kits are Version 2.xx software.

Legend : ■ = This personality kit uses this hardware.

Page 85: ACP Functional Description Manual.pdf

ACP Functional Description, May 1998 77

User Responsibilities

The following information describes the responsibilities ofusers of ACP products. The user is responsible for:

■ Receipt of the unit at the customer’s receiving dock,unpacking, and installation of the unit.

■ Reading the product manuals prior to operating the unit.

■ Adequate site preparation and planning for the portconfigurations of the unit.

■ Procurement of all communication cables (RS232, RS422,V.35, ...) and 220 volt power cord where applicable.

■ Setup and configuration of the system, including theconnection of cables.

■ Setup and configuration of attached devices (modems,terminals, etc.).

■ Identifying and supplying a suitable ASCII displayterminal or Personal Computer to be used for enteringconfiguration data.

■ Network planning and/or host system configuration toaccommodate the unit.

■ Price quotations, installation, and cost of telephone carrierequipment and service.

■ Determining spare equipment requirements/replacementsunits.

■ Performing customer problem isolation, analysis, andresolution.

■ Verifying that equipment operating with the unit meetscustomer criteria.

User SetupThe unit is designed to be set up by the customer. Physicalsetup instructions are provided in the Installation Manualincluded with each base unit shipped.

Charges, Terms, and Conditions

Contact your sales representative for pricing, availabilitywarranty coverage, and software/hardware maintenanceservices.

Comments, Questions, Corrections

To provide the highest quality information and servicepossible, we welcome your comments, questions, andcorrections regarding this document and any other Telematicspublication.

We invite you to send comments and corrections for the ACPFunctional Description to:

Telematics Publications DepartmentFAX: +1 (818) 880-4726Telematics International, Inc.Calabasas, California, USA

Thank you for your responsiveness and use of our products.

Page 86: ACP Functional Description Manual.pdf

ACP Functional Description, May 1998 78

Page 87: ACP Functional Description Manual.pdf

Index

ACP Functional Description, May 1998 79

IndexA

ACCT support, 20

ACP 10certifications, 10functional characteristics, 71interfaces, 13overview, 3personality kits, 75specifications, 12

ACP 50certifications, 10functional characteristics, 72interfaces, 13overview, 5personality kits, 76specifications, 12

ACP 70certifications, 10functional characteristics, 74interfaces, 13optional modules, 14overview, 7personality kits, 76specifications, 12

ANPS supportdescription, 25summary, 2, 20

Architecturehardware, 9software, 19system features, 9

Asynchronous supportdescription, 38device connectivity features, 38host connectivity features, 38routing, 38summary, 2X.121 support, 42X.28 support, 40X.29 support, 42X.3 support, 39

Automatic Node Protection Switching. See ANPS support

B

BRI CAM (ACP 50), 14

BRI CEM (ACP 50), 13

C

CAMs (ACP 50)definition, 13types, 14

CCM module (ACP 70), 14

CEMs (ACP 50)definition, 13types, 13

Certification/homologation, 10

CHAP security, 53

CSU/DSU CAM (ACP 50), 14

CSU/DSU support, 2, 20

D

DSP supportconnection methods, 33description, 33monitoring commands, 34summary, 2, 20trace functions, 34

E

ELX CAM (ACP 50), 14

ELX/ELX II CEM (ACP 50), 13

F

Frame Relay supportapplications, 36description, 35DTE/DCE interfaces, 35inbound congestion control, 36local management interface (LMI), 35outbound congestion control, 36summary, 2, 20

Frame relay support, applications, 35

FTP, 23, 48

Page 88: ACP Functional Description Manual.pdf

ACP Functional Description, May 199880

H

Hardware, ACPinterface converters, 14interface hardware, 15requirements for personality kits, 75

Hex CAM (ACP 50), 14

Hex CEM (ACP 50), 13

I

Interfaces, ACP, 15

Internal modem supportadvantages, 66applications, 67description, 66dialing in, 68dialing out, 68interfaces, 66modem sharing, 66operating speeds, 66specifications, 68summary, 2, 20

IP supportapplications, 46bandwidth management, 48description, 46ELX transceivers, 48FTP, 23, 48IP transporter, 50LAN/WAN connections, 49monitoring commands, 48NFS, 48PAP/CHAP, 53PPP, 50PPP/SLIP/X.25 gateway, 50proxy ARP, 54RADIUS, 54routing protocols, 48SLIP, 49SMTP, 48SNMP, 23, 46standards, 48statistics, 49summary, 2, 20TELNET, 23, 46

IP Transporter, 50

ISDN BRI port module (ACP 70), 14

ISDN BRI supportapplications, 64description, 63national variations, 64specifications, 63summary, 20

ISDN support, summary, 2

ITI support, summary, 20

L

Level 1 support, 17

M

Modem support. See internal modem support

MTBF figures, 11

N

Network router, definition, 19

NFS, 48

NMS support, 20

O

Octal DMA CAM (ACP 50), 14

Octal DMA I/II/III CEM (ACP 50), 13

Octal modem CAM (ACP 50), 14

Octal modem CEM (ACP 50), 13

Open management system (OMS), 23

OSPF routing protocol, 48

P

PAP security, 53

Personality kits, ACP, 75

Personality module, 70

PlatformsACP 10, 3ACP 50, 5ACP 70, 7

Port types, 18

Page 89: ACP Functional Description Manual.pdf

Index

ACP Functional Description, May 1998 81

POS supportapplications, 61connection types, 58description, 58features, 59summary, 2, 20terminals/hosts supported, 58

PPP protocol, 50

PPP/SLIP/X.25 gateway, 50

Protection switching. See ANPS support

Proxy ARP, 54

R

RADIUS security, 54

Revision history, manual, viii

S

SLIP protocol, 49

SMTP, 48

SNA support3270 support, 443770 support, 445250/5294/5394 support, 44combined X.25/SNA, 43description, 43error recovery, 43host connections, 44PU and LU switching, 43security, 45summary, 2, 20TPAD and HPAD, 43

SNMP, 23, 46

Software, ACPoverview, 19personality kits, 75

Specifications, physical/environmental, 12

SYMdescription, 21summary, 19TELNET client access, 23

System manager interface. See SYM

T

T1/E1 CSU/DSU. See CSU/DSU

TELNET, 23, 46

TPP supportconnection methods, 57description, 56FOP and BOP protocols, 56monitoring commands, 57summary, 2, 20trace functions, 57

Trace support, 19

V

V.11/V.24/V.35 interface modules (ACP 70), 14

X

X.25 supportdescription, 27general features, 28level 2 frame interface, 27level 3 packet interface, 27multipoint support, 31summary, 2, 20

Page 90: ACP Functional Description Manual.pdf

ACP Functional Description, May 199882

Page 91: ACP Functional Description Manual.pdf

ACP Functional Description, May 1998 83

�� ����� �������� ����

American/Corporate Eastern European Central European Western European Asian Headquarters Headquarters Headquarters Headquarters Headquarters

ECI Telecom-Telematics, Inc. ECI Telecom ECI Telecom GMBH ECI Telecom, Ltd. ECI Telecom (HK), Ltd.1201 West Cypress Creek Road 30 Hasivim Street Büropark Oberursel Isis House 2806 China Resources Building

Ft. Lauderdale, FL 33309 Petah Tikva 49133 In der Au 27 Reading Road, Chineham 26 Harbour Road(954) 772-3070 Israel 61440 Oberursel, Germany Basingstoke, Hampshire Wanchai, Hong Kong(800) 883-4580 011-972-3-926-6555 011-49-61-716-2090 RG24 8TW, United Kingdom 011-852-2824-4128

FAX (954) 351-4405 FAX 011-972-3-926-6700 FAX 011-49-61-715-4057 011-44-1-256-388-000 FAX 011-852-2802-4411FAX 011-44-1-256-388-143

�� ����� ���� ��� ������� ����

Spain France NetherlandsBarajas Park Espace Velizy “Le Nungesser” HouttuinIaan 18

San Severo 20 13, Avenue Morane Saulnier P.O. Box 18828042 Madrid 78140 VELIZY 3440 AD Woerden

Spain France Netherlands011-34-1-329-0585 011-33-1-3463-0480 011-31-348-576-611

FAX 011-34-1-329-2220 FAX 001-33-1-3946-2118 FAX 011-31-348-576-700

Singapore U.S. South U.S. West150 Beach Road 1759 N. Collins Blvd. 1534 Plaza Lane, No. 350

#15-08 Gateway West Tower Suite 224 Burlingame, CA 94010Singapore, 189720 Richardson, TX 75080 (650) 344-3999011-65-297-7335 (214) 705-9080 FAX (650) 340-9999

FAX 011-65-299-2716 (214) 437-1750

U.S. East U.S. East620 Herndon Parkway 90 Washington Valley Road

Suite 120 Bedminster, NJ 07921Herndon, VA 20170 (908) 719-8920

(703) 478-0560 FAX (908) 719-8925FAX (703) 478-0143

Page 92: ACP Functional Description Manual.pdf

ACP Functional Description, May 1998 84