DOCSLIB.ORG

Local Area Transport (LAT) Specification Part No

Total Page：16

File Type：pdf, Size：1020Kb

Download full-text PDF Read full-text
Local Area Transport (LAT) Specification Part No Local Area Transport (LAT) Specification Part No. AA-NL26A-TE A simple, efficient, transparent model for exchanging data between terminals c=r.· nected to terminal servers and host operating system processes is described. Tr.e model Is termed Local Area Transport (LAn. LAT Is carefully tailored to take ac­ vantage of the environment offered by Local Area Networks. such as the Ethernet data link, but maintains much of the simplicity of traditional methods of connec~ing terminals and hosts. Digital Equipment CorporatlonIProprietary and Confidential The information in this document is subject to change without notice and should not be construed as a commitment by Digital Equipment Corporation. DigitaJ Equipment Corporation assumes no responsibility for any errors that may appear in this document. June 1989 Copyright C1989 Digital Equipment Corporation All rights reserved. The following are trademarks of DIGITAL Equipment Corporation: DEC ~T RT pECmate MASSBUS ULTRIX DECnet PDP UNIBUS DECUS P/OS VAX DECWiiter Profe.sional VAXcluater DmOL Rainbow VMS !amDDma- RSTS VT DN,. RSX Work Processor This Inanuat was P§dUcec(!!i Networks and Communications Publicati~ ii f Thit document was prepared using VAX DOCUMENT, Version 1.1 Contents Preface 1 Introduction 1.1 Terminology . 1-5 2 Architecture Overview 2.1 Introduction ................................................ 2-1 2.2 SLOT LAYER - USER INTERFACE ............................. 2-5 2.2.1 Connecting to the Host Service .............................. 2-6 2.2.2 Connecting to the Terminal Server Service ..................... 2-7 2.3 VIRTUAL CIRCUIT LAYER ................................... 2-9 2.4 Product Considerations ...................................... 2-11 2.4.1 Host .................................... _./ ............•...... 2-11 2.4.2 Ternlinal Server ............................................ :' .. ·2-12 3 Naming and Translation 3.1 Naming Conventions .................... ~ ............•<i ••••.•• 3-1 3.1.1 Service Name Translation Process ......................... ;"'-.~ 3-1 3.1.2 Translation Process On A Source Node ....................... 3-4 3.1.3 Translation Process On A Destination Node .................... 3-5 3.2 Service Advertising Mechanisms ............................... 3~6 3.2.. 1 Host Advertising .......................................... 3-6 3.2.2 Terminal Server Advertising ................................. 3-8 3.3 Specification of Nanles ....................................... 3-9 3.4 Specification of Text ......................................... 3-11 III 4 Circuit and Session Layers 4.1 Architectural Model .......................................... 4-1 4.1.1 Slot Data ................................................. 4-1 4.1.2 Asynlnletry ............................................... 4-1 4.1.3 Virtual Circuit Service ...................................... 4-2 4.1.3.1 Virtual Circuit State .................................... 4-2 4.1.3.2 Architecturally Controlled Names and Variables ............. 4-4 4.1.3.3 Message Types ....................................... 4-11 4.1.3.4 Cirtual Circuit State Variables ........................... 4-12 4.1.3.5 Response Requested Flag and Balanced Mode .............. 4-13 4.1.3.6 Message Mapping Onto State Diagram ................... 4-13 4.1.4 User Connection Management And Data Flow ................ 4-19 4.1.4.1 Service Classes ..................................... .. 4-19 4.1.4.2 Host Session Management .............................. 4-19 4.1.4.3 Multiplexing Over A Virtual Circuit ...................... 4-20 4.1.4.4 Slot Ordering Within Messages .......................... 4-20 4.1.4.5 Slot State Variables .................................... 4-20 4.1.4.6 Ternlinal Server Slot Mapping Onto State Diagranl ......... 4-22 4.1.4.7 Terminal Server Slot State Table ......................... 4-23 4.1.4.8 Host Slot Mapping Onto State Diagram ................... 4-24 4.1.4.9 Host Slot State Table ................................... 4-25 4.2 Layer Illterfaces ............................................ 4-26 4.2.1 Data Types .............................................. 4-27 4.2.2 User/Slot Layer Interface ................................... 4-28 4.2.2.1 Summary Of Functions ................................. 4-28 4.2.2.2 Description Of Functions ............................... 4-29 4.2.3 Slot/Virtual Circuit Layer Interface ........................... 4-32 4.2.3.1 Summary Of Functions ................................. 4-32 4.2.3.2 Description Of Functions ............................... 4-33 4.3 Axioms And Algorithms ..., ........ '.......................... 4-35 4.3.1 Virtual Circuit Layer ....................................... 4-37 4.3.1.1 Circuit Starter (Terminal Server Only) ..................... 4-37 4.3.1.2 Data_Volunteered ...................................... 4-37 4.3.1.3 Credits Returned ...................................... 4-38 4.3.1.4 Orcuit Ender ......................................... 4-38 4.3.1.5 Message Receiver ...................................... 4-38 4.3.1.6 Message Transnlitter ................................... 4-40 4.3.1.7 Circuit Tinler Policy .................................... 4-42 4.3.1.8 Buffering ............................................. 4-42 iv 4.3.2 Slot Layer ............................................... 4-43 4.3.2.1 Host Systenl Management .............................. 4-43 4.3.2.2 Terminal Server System Management ..................... 4-43 4.3.2~3 Session Starter (Tenninal Server) ........................ 4-44 4.3.2.4 Session Starter (Host) .................................. 4-44 4.3.2.5 Slot Deolultiplexer ..................................... 4-44 4.3.2.6 Slot Multiplexer ....................................... 4-45 4.3.2.7 Sessioll Ellder ......................................... 4-47 4.3.2.8 Flow Control ......................................... 4-47 4.3.2.9 Protocol Versions And ECO Control ...................... 4-48 4.3.3 Otl,er Processes .......................................... 4-49 4.3.3.1 Keep-Alive Process .................................... 4-49 4.3.3.2 Progress Process ...................................... 4-49 4.4 Message Forolats ........................................... 4-50 4.4.1 Virtual Circuit Message Header ............................. 4-51 4.4.1.1 Start Message Format .................................. 4-52 4.4.1.2 Run Message Forolat ................................... 4-55 4.4.1.3 Stop Message Fonnat .................................. 4-62 5 Connection Solicitation 5.1 Architectural Model .......................................... 5-1 5.1.1 Service Sharing ......•.................................... 5-2 5.1.1.1 Queue Coordination .................................... 5-4 5.1.1.2 Queue Access . .. 5-5 5.1.1.3 Queue Structure ........................................ 5-6 5.1.1.4 Queue Operations ...................................... 5-7 5.1.1.5 Concatenating The Status Entries ........................ 5-12 5.1.1.6 Retranslnission And TiIne-out Policies .................... 5-12 5.1.2 Connection Initiation ...................... , ............... 5-13 5.1.2.1 Solicitation Process Message Flow ........................ 5-14 5.1.2.2 Solicitation process state-tables .......................... 5-24 5.1.2.3 Name And Inforolation Field Presentation ................. 5-30 5.2 Message Formats ........................................... 5-31 5.2.1 Command Message ....................................... 5-32 5.2.2 Status Message ...................................... ',..... 5-36 v A Service Class 1 - Interactive And Application Terminals. A.l Local Area Directory Service .................................. A-l A.2 Service Access Control ...................................... A-2 A.3 Advertising Services Through Multicast Message ................. A-6 A.3.1 Host .................................................... A-6 A.3.1.l Initialization .......................................... A-6 A.3.1.2 Host Group Codes ..................................... A-7 A.3.1.3 Host Node Nanles ..................................... A-7 A.3.l.4 Multiple-Node Service Ratings. .. A-7 A.3.l.S Steady-State Operation ................................. A-7 A.3.1.6 System Shutdown .. .. A-8 A.3.2 Ternlillal Server .......................................... A-8 A.3.2.l Initialization .......................................... A-8 A.3.2.2 Building The Circuit Nanle Database ...................... A-9 A.4 Advertising Thr.ough Solicitation and Response Messages ........ A-11 A.4.l A Node Operating In Slave Mode .......................... A-12 A.4.2 A Node Operating In Master Mode ......................... A-13 A.4.3 Response Information Message Policy. .. A-14 A.S Service Class 1 Messages ................................... A -15 A.S.l Service Announcenlent Message ...................... .. A-1S A.S.2 Solicit Infornlation Message . .. A-19 A.S.3 Response Infornlation Message ............................ A-22 A.6 Service Class 1 Slot Format Extensions ........................ A-28 A.6.1 Start Slot Status Field .................................... A-29 A.6.2 Attention Slot Status Field ................................ A-31 A.6.3 Data_b Slot Extension .................................... A-33 A.6.3.1 Infornlation Exchange Using Data_b Slots ................ A-33 A.6.3.2 Data_b Slot Fornlat ................................... A-34 A.6.3.3 Guidelines And Reconlnlendations For Data_b Slot ProcessingA-38 B Compatibility and Implementation B.l Implementation Issues. .. B-1 B.l.l Possible
Load more

Recommended publications
  • Digital Technical Journal, Number 3, September 1986: Networking
    Netwo;king Products Digital TechnicalJournal Digital Equipment Corporation Number 3 September I 986 Contents 8 Foreword William R. Johnson, Jr. New Products 10 Digital Network Architecture Overview Anthony G. Lauck, David R. Oran, and Radia J. Perlman 2 5 PerformanceAn alysis andModeling of Digital's Networking Architecture Raj Jain and William R. Hawe 35 The DECnetjSNA Gateway Product-A Case Study in Cross Vendor Networking John P:.. �orency, David Poner, Richard P. Pitkin, and David R. Oran ._ 54 The Extended Local Area Network Architecture and LANBridge 100 William R. Hawe, Mark F. Kempf, and Alan). Kirby 7 3 Terminal Servers on Ethernet Local Area Networks Bruce E. Mann, Colin Strutt, and Mark F. Kempf 88 The DECnet-VAXProduct -A n IntegratedAp proach to Networking Paul R. Beck and James A. Krycka 100 The DECnet-ULTRIXSoftware John Forecast, James L. Jackson, and Jeffrey A. Schriesheim 108 The DECnet-DOS System Peter 0. Mierswa, David). Mitton, and Ma�ha L. Spence 117 The Evolution of Network Management Products Nancy R. La Pelle, Mark). Seger, and Mark W. Sylor 129 The NMCCjDECnet Monitor Design Mark W. Sylor 1 Editor's Introduction The paper by Bill Hawe, Mark Kempf, and AI Kirby reports how studies of potential new broad­ band products led to the development of the Extended LAN Architecture. The design of the LANBridge 100, the first product incorporating that architecture, is described, along with the trade-offs made to achieve high performance. The speed of communication between terminals and systems depends on how they are connected. Bruce Mann, Colin Strutt, and Mark Kempf explain how they developed the LAT protocol to connect terminals to hosts on an Ethernet.
    [Show full text]
  • Networks· Communications
    - Networks· Communications, ;--___...........................................e e_e __ • • • • • • • • • • • • • • • • • • • • • • • • • • • • . ... • • • • • • • • • ~---- Local Area Transport (LAT) Architecture i Network Manager's Guide " wore~D~DD~D Local Area Transport (LAT) Arch itectu re Network Manager's Guide Order No. AA-OJ 188-TK July 1985 The Local Area Transport (LA T) Architecture Network Manager's Guide is intended for network managers and system managers. It contains information about the LAT architecture. This guide also in­ cludes information for configuring and managing LAT networks. SUPERSESSION/UPDATE INFORMATION: This is a revised manual. AA-DJ18B-TK First Printing, July 1985 The information in this document is subject to change without notice and should not be construed as a commitment by Digital Equipment Corporation. Digital Equipment Corpora­ tion assumes no responsibility for any errors that may appear in this document. The software described in this document is furnished under a license and may only be used or copied in accordance with the terms of such license. No responsibility is assumed for the use or reliability of software on equipment that is not supplied by Digital or its affiliated companies. Copyright © 1985 by Digital .Equipment Corporation The postage-prepaid Reader's Comments form on the last page of this document requests the user's critical evaluation to assist us in preparing future documentation. The following are trademarks of Digital Equipment Corporation: DEC MASSBUS RT DECmate PDP UNIBUS DECnet P/OS VAX DECUS Professional VAXcluster DECwriter Rainbow VMS DIBOL RSTS VT ~D~DDmD RSX Work Processor Ethernet is a trademark of Xerox Corporation. This manual was produced by Networks and Communications Publications.
    [Show full text]
  • Software Product Description and Quickspecs
    VSI OpenVMS Alpha Version 8.4-2L2 Operating System DO-DVASPQ-01A Software Product Description and QuickSpecs PRODUCT NAME: VSI OpenVMS Alpha Version 8.4-2L2 DO-DVASPQ-01A This SPD and QuickSpecs describes the VSI OpenVMS Alpha Performance Release Operating System software, Version 8.4-2L2 (hereafter referred to as VSI OpenVMS Alpha V8.4-2L2). DESCRIPTION OpenVMS is a general purpose, multiuser operating system that runs in both production and development environments. VSI OpenVMS Alpha Version 8.4-2L2 is the latest release of the OpenVMS Alpha computing environment by VMS Software, Inc (VSI). VSI OpenVMS Alpha V8.4-2L2 is compiled to take advantage of architectural features such as byte and word memory reference instructions, and floating-point improvements, which are available only in HPE AlphaServer EV6 or later processors. This optimized release improves performance by taking advantage of faster hardware-based instructions that were previously emulated in software. NOTE: VSI OpenVMS Alpha V8.4-2L2 does not work on, and is not supported on, HPE AlphaServer pre-EV6 systems. OpenVMS Alpha supports HPE’s AlphaServer series computers. OpenVMS software supports industry standards, facilitating application portability and interoperability. OpenVMS provides symmetric multiprocessing (SMP) support for multiprocessing systems. The OpenVMS operating system can be tuned to perform well in a wide variety of environments. This includes combinations of compute-intensive, I/O-intensive, client/server, real-time, and other environments. Actual system performance depends on the type of computer, available physical memory, and the number and type of active disk and tape drives. The OpenVMS operating system has well-integrated networking, distributed computing, client/server, windowing, multi-processing, and authentication capabilities.
    [Show full text]
  • Muxserver 380 Hardware Installation Manual Order Number EK-DSRZD-IM-002
    MUXserver 380 Hardware Installation Manual Order Number EK-DSRZD-IM-002 2nd Edition Second Edition - February 1992 The information in this document is subject to change without notice and should not be construed as a commitment by Digital Equipment Corporation (Australia) Pty. Limited. Digital Equipment Corporation (Australia) Pty. Limited assumes no responsibility for any errors that may appear in this document. The software described in this document is furnished under a license and may be used or copied only in accordance with the terms of such license. No responsibility is assumed for the use or reliability of software on equipment that is not supplied by Digital Equipment Corporation (Australia) Pty. Limited or its affiliated companies. Copyright ©1992 by Digital Equipment Corporation (Australia) Pty. Limited. All Rights Reserved. Printed in Australia. The postpaid READER’S COMMENTS form on the last page of this document requests the user’s critical evaluation to assist in preparing future documentation. The following are trademarks of Digital Equipment Corporation: DEC DIBOL UNIBUS DEC/CMS EduSystem UWS DEC/MMS IAS VAX DECnet MASSBUS VAXcluster DECstation PDP VMS DECsystem–10 PDT VT DECSYSTEM–20 RSTS DECUS RSX DECwriter ULTRIX dt Contents Preface viii Chapter 1 Introduction 1.1 Overview of the MUXserver 380 Network . ................................1–1 1.2 Typical MUXserver 380 Network Configuration ...............................1–2 1.3 The MUXserver 380 . .................................................1–3 1.4 Connecting the MUXserver 380 . ........................................1–6 1.5 Installation Overview . ................................................1–10 1.6 Items Required for MUXserver 380 Installation .............................1–11 1.7 Service Options ......................................................1–12 1.7.1 Digital On-Site Service .
    [Show full text]
  • Decserver 90M Installation Guide
    DECserver 90M Installation Guide Part Number: IG-DSRVH-00 April 2002 This document describes how to install and troubleshoot the DECserver 90M. Revision/Update Information: This is a new document. Digital Networks makes no representations that the use of its products in the manner described in this publication will not infringe on existing or future patent rights, nor do the descriptions contained in this publication imply the granting of licenses to make, use, or sell equipment or software in accordance with the description. Possession, use, or copying of the software described in this publication is authorized only pursuant to a valid written license from Digital Networks or an authorized sublicensor. Copyright © 2001 DNPG, LLC (“Digital Networks”). All rights reserved. Digital Networks 486 Amherst St. Nashua , NH 03063-1224 Web site: www.digitalnetworks.net Digital Networks is the tradename of DNPG, LLC, and is not affiliated with Compaq Computer Corporation. DIGITAL, the Digital Logo and DEC are used under license from Compaq Computer Corporation. clearVISN, Multistack, MultiSwitch, and ThinWire are trademarks of Cabletron Systems, Inc. All other trademarks and registered trademarks are the property of their respective holders. NOTICES FCC Notice — Class A Computing Device: This equipment has been tested and found to comply with the limits for a Class A digital device, pursuant to part 15 of the FCC Rules. These limits are designed to provide reasonable protection against harmful interference when the equipment is operated in a commercial environment. This equipment generates, uses, and can radiate radio frequency energy and, if not installed and used in accordance with the instruction manual, may cause harmful interference to radio communications.
    [Show full text]
  • ETS4P4 Terminal Server
    ETS4P4 Terminal Server Installation Guide Thank you for purchasing this Lantronix ETS Ethernet Terminal Server. As the newest addition to our successful Ethernet terminal server family, the ETS uses software for multiprotocol Ethernet connections that has over 5 years of real-world feedback and de- velopment behind it. Lantronix is constantly improving the capabilities of our prod- ucts, and we encourage you to take advantage of new features through our FREE software upgrades (available via ftp over the Internet or BBS.) Our Flash ROM products, including this ETS, provide the sim- plest means for upgrades and installation. I hope you find this manual easy to use, and thorough in its explanation of the power- ful features you can now access on your network. Brad Freeburg President Contents 1 Introduction Overview...........................................................................1-1 Configuration ................................................1-1 Software ..........................................................1-2 About the Manuals ..........................................................1-2 2 Installation Overview...........................................................................2-1 ETS Components..............................................................2-1 Installation ........................................................................2-2 Selecting a Location for the ETS ..................2-2 Connecting to the Ethernet...........................2-2 Connecting a Terminal..................................2-3
    [Show full text]
  • Openvms Cluster Load Balancing
    OpenVMS Cluster Load Balancing Presented by Paul Williams www.parsec.com | 888-4-PARSEC To Download this Presentation, please visit: http://www.parsec.com/public/ClusterLoadBalancing.pdf To E-mail Paul [email protected] www.parsec.com | 888-4-PARSEC Outline • Load Balancing Mechanisms • Batch and Print Queues • TCP/IP • DECnet • Local Area Transport (LAT) • Host Based Volume Shadowing • MSCP Server • Lock Manager • Questions and Answers Evaluating Load Balancing Mechanisms What happens when? •A new request is made •A node fails •Resources are exhausted on a node •A node is returned to service Load Balancing Goals •Never direct a request to a non- functional node •Direct requests to the node which can provide the best level of service •Direct requests to other nodes prior to scheduled downtime •Make failover and recovery transparent to user Load Balancing Mechanisms •Failover - All requests go to a single node while it is up •Round Robin - Balanced based only on number of requests serviced •Load Based - Balances requests based on ability of serving nodes to handle the work OpenVMS Queue Manager • Maintains all queues, forms and characteristics • Manages all jobs in each queue • Must run on one node in a VMScluster • Default is any node • Failover is automatic and transparent to users $ start /queue /manager /on=(class2,class3,*) $ show queue /manager /full Master file: STAFF_DISK:[COMMON]QMAN$MASTER.DAT; Queue manager SYS$QUEUE_MANAGER, running, on CLASS2:: /ON=(CLASS2,CLASS3,*) Database location: STAFF_DISK:[COMMON] Generic Batch Queues
    [Show full text]
  • Configuring Asynchronous Lines and Interfaces
    Configuring Asynchronous Lines and Interfaces This chapter describes how to configure asynchronous line features in the following main sections: • How to Configure Asynchronous Interfaces and Lines • How to Configure Other Asynchronous Line and Interface Features • Configuration Examples for Asynchronous Interfaces and Lines Perform these tasks, as required, for your particular network. To identify the hardware platform or software image information associated with a feature, use the Feature Navigator on Cisco.com to search for information about the feature or refer to the software release notes for a specific release. For more information, see the “Identifying Supported Platforms” section in the “Using Cisco IOS Software” chapter. For a complete description of the commands in this chapter, refer to the Cisco IOS Dial Technologies Command Reference. To locate documentation of other commands that appear in this chapter, use the command reference master index or search online. How to Configure Asynchronous Interfaces and Lines To configure an asynchronous interface, perform the tasks described in the following sections as required: • Configuring a Typical Asynchronous Interface (As required) • Creating a Group Asynchronous Interface (As required) • Configuring Asynchronous Rotary Line Queueing (As required) • Configuring Autoselect (As required) Configuring a Typical Asynchronous Interface To configure an asynchronous interface, use the following commands beginning in global configuration mode: Americas Headquarters: Cisco Systems, Inc., 170 West Tasman Drive, San Jose, CA 95134-1706 USA Configuring Asynchronous Lines and Interfaces How to Configure Asynchronous Interfaces and Lines Command Purpose Step 1 Router(config)# interface async number Brings up a single asynchronous interface and enters interface configuration mode. Step 2 Router(config-if)# description description Provides a description for the interface.
    [Show full text]
  • SSH Terminal-Line Access
    SSH Terminal-Line Access The SSH Terminal-Line Access feature provides users secure access to tty (text telephone) lines. tty allows the hearing- and speech-impaired to communicate by using a telephone to type messages. • Finding Feature Information, page 1 • Prerequisites for SSH Terminal-Line Access, page 1 • Restrictions for SSH Terminal-Line Access, page 2 • Information About SSH Terminal-Line Access, page 2 • How to Configure SSH Terminal-Line Access, page 3 • Configuration Examples for SSH Terminal-Line Access, page 5 • Additional References, page 6 • Feature Information for SSH Terminal-Line Access, page 7 Finding Feature Information Your software release may not support all the features documented in this module. For the latest caveats and feature information, see Bug Search Tool and the release notes for your platform and software release. To find information about the features documented in this module, and to see a list of the releases in which each feature is supported, see the feature information table at the end of this module. Use Cisco Feature Navigator to find information about platform support and Cisco software image support. To access Cisco Feature Navigator, go to www.cisco.com/go/cfn. An account on Cisco.com is not required. Prerequisites for SSH Terminal-Line Access Download the required image to your router. The secure shell (SSH) server requires the router to have an IPSec (Data Encryption Standard (DES) or 3DES) encryption software image from Cisco IOS Release 12.1(1)T or a later release. The SSH client requires the router to have an IPSec (DES or 3DES) encryption software image from Cisco IOS Release 12.1(3)T or a later release.
    [Show full text]
  • Console Port
    DIGITAL NetRider Network Access Server Management Part Number: AA-PW5VE-TE June 1997 Revision/Update Information: This is a revised document. Software and Version: DECserver Network Access Software, Version 2.2 © Digital Equipment Corporation 1997. All rights reserved. Digital Equipment Corporation makes no representations that the use of its products in the manner described in this document will not infringe on existing or future patent rights, nor do the descriptions contained in this document imply the granting of licenses to make, use, or sell equipment or software in accordance with the description. Possession, use, or copying of this software and media is authorized only pursuant to a valid written license from DIGITAL or an authorized sublicensor. The following are trademarks of Digital Equipment Corporation: DDCMP, DEC, DECmcc, DECnet, DECserver, DECsystem, DECwindows, DIGITAL, DNA, LAT, NetRider, OpenVMS, ThinWire, ULTRIX, VAX, VAXstation, VMS, VMScluster, VT100, VT220,VT320, VT330, and the DIGITAL logo. The following are third-party trademarks: AppleTalk and Macintosh are registered trademarks of Apple Computer, Inc. HP and Hewlett-Packard are registered trademarks of Hewlett Packard Company. IBM is a registered trademark of International Business Machines Corporation. Kerberos is a trademark of the Massachusetts Institute of Technology. Microsoft, MS-DOS, and Windows 95 are registered trademarks, and Windows NT is a trademark of Microsoft Corporation. NetBIOS is a trademark of Micro Computer Systems, Inc. Novell and NetWare are registered trademarks of Novell, Inc. OS/2 is a registered trademark of International Business Machines Corporation. OSF/1 is a registered trademark of Open Software Foundation, Inc. PostScript is a registered trademark of Adobe Systems, Inc.
    [Show full text]
  • Single-Port Terminal Server Model 2120
    Device Servers Single-Port Terminal Server Model 2120 The Patton Model 2120 Single Port Terminal Server brings RS-232 serial devices onto the LAN using the flexibility of Ethernet and TCP/IP protocols. Control and Monitor Serial Devices thernet continues to be the most com- user-defined IP address and port. Once con- Control and monitor your RS-232 asynchronous mon office networking infrastructure. nected to the remote host, data is passed terminals and devices over the local area network ENow, Ethernet is making its way from transparently end-to-end. The built-in DHCP the office to the shop floor. Traditional RS- Client allows the Model 2120 to dynamically Supports a Wide Range of Data Rates 232 environments require the use of multi- obtain an IP address and a subnet mask from User-selectable async data port serial cards, expensive cables, and the a master server. With SLIP and PPP connec- rates up to 115.2 kbps personnel to manage multiple systems. tions, remote users can Patton’s Model 2120 Single Port Terminal access the network and it Connects Directly to the LAN Server provides a quick, simple, and cost will appear as if they were 802.3 10Base-T LAN connection effective solution for connecting traditional locally connected. via RJ-45 connects to any hub/switch RS-232 terminals and devices to the LAN. Why go to the expense and hassle of installing Special Rates Available Standard TCP/IP Protocols Supported The Model 2120 enables you to bring all sys- Call for Details TCP, UDP, IP, ICMP, TELNET, ARP, DHCP, tems and equipment together onto one local outdated multi-port serial FTP, SLIP, PPP, DNS, WINS, and PAP area network.
    [Show full text]
  • Decserver 90M
    DECserver 90M Owner’s Manual Part Number : EK-DSRVH-OM. A01 CAUTION The DECserver 90M is not intended for use with telecommunications net- works or with Integrated Services Digital Network (ISDN) devices. ACHTUNG Der DECserver 90M darf nicht als Teil eines Fernmeldenetzwerks oder zusammen mit ISDN1 –Geräten betrieben werden. (1Integrated Services Digital Network) ATTENTION Le DECserver 90M n’a pas été conçu pour fonctionner avec des réseaux de télécommunication ou des modules ISDN (Integrated Services Digital Network). A VISO El DECserver 90M no ha sido diseñado para su uso con redes IMPORTANTE de telecomunicaciones ni dispositivos de Red Digital Servicios Integrados (ISDN). DECserver 90M Owner’s Manual Part Number : EK-DSRVH-OM. A01 ________________________________________________________________ The information in this document is subject to change without notice and should not be construed as a commitment by Digital Equipment Corporation. Digital Equipment Corporation assumes no responsi- bility for any errors that may appear in this document. The software described in this document is furnished under a license and may only be used or copied in accordance with the terms of such license. No responsibility is assumed for the use or reliability of software on equipment that is not supplied by Digital or its affiliated companies. Restricted Rights: Use, duplication, or disclosure by the U.S. Government is subject to restrictions as set forth in subparagraph (c) (1) (ii) of the Rights in Technical Data and Computer Software clause at DFARS 252.227–7013. Copyright 1993 by Digital Equipment Corporation All Rights Reserved FCC NOTICE – The equipment described in this manual generates, uses and may emit radio frequency energy.
    [Show full text]