     	  Software   Product  Description  D  ___________________________________________________________________  D  PRODUCT NAME:  DECserver 90 TL Software, Version 1.1c  SPD 38.71.04    DESCRIPTION  F  DECserver 90TL Software, Version 1.1c is an enhanced software release  for the DECserver 90TL.  E  The DECserver 90TL software provides concurrent Local Area Transport D  (LAT) and Telnet TCP/IP protocol support from a DECserver 90TL com-D  munications server to enable connectivity to host systems that uti-H  lize LAT or TCP/IP protocols. The TCP/IP protocol suite is used to con-E  nect to UNIX[R] host systems and other host systems that support the   TCP/IP protocol suite.   G  The DECserver 90TL Communications Server is an Ethernet Communications H  Server for Ethernet Local Area Networks (LANs). The DECserver 90TL pro-I  vides a convenient method to logically connect up to eight digital asyn- E  chronous terminals to one or more service nodes (hosts) on an Ether- D  net. Once the terminal is connected, a user can utilize applicationE  programs and utilities as though the terminal was directly connected D  to a host via a DMF32, DHU11, or DHV11/DHQ11 device, with a few ex-D  ceptions. Thus, it may be possible to utilize the DECserver 90TL toF  connect all terminals to service nodes in place of traditional inter-*  faces, except for host console terminals.  F  In addition, the DECserver 90TL provides IP end-node routing via SLIPH  (Serial Line Internet Protocol). Up to eight TCP/IP systems can be con-D  nected to the serial ports of the DECserver 90TL. These systems canE  run IP applications (such as Telnet, FTP[R], X-Windows, etc.) on the G  serial line and communicate with other TCP/IP services on the network.       D                                DIGITAL                   August 1997  D                                                          AE-PME5E-TE       E  The DECserver 90TL uses MJ8 (similar to RJ45 jacks used in telephone F  jacks) for the attachment of asynchronous devices. The DECserver 90TLD  utilizes the DEC 423-A electrical interface standard for local con-H  nections. DEC 423-A is compatible with the DEC 232-D interface and sup-E  ports DTR/DSR (Data Terminal Ready/Data Set Ready) signals. DEC 423- :  A supports longer cable runs and higher signaling speeds.  G  The DECserver 90TL supports reverse LAT and Telnet Listener. These can H  be used to share the load on asynchronous devices connected to the DEC-G  server 90TL. A group of ports can each be defined as the same service. E  With reverse LAT, if the node from which the service request is ini- G  tiated is properly configured, the service request will be sent to the '  port with the highest capacity rating.   E  The DECserver 90TL also allows for host-initiated connections to se- F  rial printers. A print symbiont on service nodes can initiate connec-E  tions to serial printers connected to DECserver 90TL ports. This al- G  lows the printers to be distributed throughout a facility and accessed E  transparently by service node users. Incoming host-initiated connect +  requests can be queued FIFO at the server.   @  Port-to-port connections on the same server are also supported.  F  The DECserver 90TL implements the LAT protocol for communication withF  service nodes that implement this protocol on the same Ethernet. ThisD  interface has been optimized for high terminal I/O performance overF  an Ethernet, while reducing host CPU cycles required to handle inter-D  rupts. Hence, under most I/O loading conditions, a significant per-E  formance gain can be realized by using the DECserver 90TL versus di- F  rect terminal connections via traditional asynchronous backplane com-  munications interfaces.  F  The DECserver 90TL also implements the TCP/IP protocol suite for com-F  munication with host systems that implement TCP/IP. The TCP/IP imple-H  mentation is based on the University of California's 4.3 Berkeley Soft-F  ware Distribution (BSD). The following TCP/IP protocols are supportedC  and adhere to the Defense Data Network (DDN) Request for Comments:       #                                   2        G  o  Transmission Control Protocol (TCP) is the Internet standard trans- G     port level protocol that provides the reliable, end-to-end full du- K     plex, stream service that supports many application protocols (RFC793).   D  o  Bootstrap Protocol (BOOTP) is the Internet standard protocol forF     downloading software that is on the DECserver 90TL (RFC951); also,D     BOOTP Vendor Information Extensions (RFC1084), the TFTP protocol8     (RFC783), and Bootstrap Loading using TFTP (RFC906).  F  o  User Datagram Protocol (UDP) is an Internet protocol that providesE     datagram service to application programs, allowing an application D     program on one machine to send a datagram to an application pro-D     gram on another machine. UDP is necessary for the Domain[R] NameG     System and the Simple Network Management Protocol (SNMP) (RFC 768).   D  o  Internet Protocol (IP) is an Internet standard protocol that de-D     fines the Internet datagram as the unit of information that getsE     passed across the Internet, and provides the universal addressing D     scheme for hosts and gateways for Internet connection-less, bestD     effort packet delivery services. IP includes ICMP as an integral     part (RFC 791).   H  o  Internet Control Message Protocol (ICMP) is an Internet network pro-E     tocol that specifies error and control messages used with the In-      ternet protocols (RFC 792).   D  o  Packet Internet Groper (PING) tests the reachability of nodes onG     the users' Internet. ICMP echoes requests are sent and replies pro-      cessed.   E  o  Address Resolution Protocol (ARP) is an Internet protocol used to F     perform dynamic address resolution to dynamically map or translateG     an Internet address into the correct physical hardware address (RFC 	     826).   F  o  Telnet is the standard Internet application level protocol for re-F     mote terminal connection service. Telnet is a virtual terminal fa-D     cility that allows a user at one site to establish a TCP connec-F     tion to a remote system. Telnet makes the local terminal appear as  #                                   3        F     a direct extension of the remote system, allowing the user to con-E     duct a session and run application programs as if the user's ter- A     minal were directly connected to the remote system (RFC 854).   <     Both Telnet client and server capabilities are provided:  F     -  Telnet client provides the ability to connect to any remote TCPE        port at an Internet address on a Local Area Network (LAN) or a F        Wide Area Network (WAN). Telnet client allows the user to spec-E        ify a remote computer by Internet address as well as by domain         name.  G     -  Telnet server provides the ability to accept connection requests H        from Internet hosts on a LAN or WAN to DECserver 90TL ports, such:        as printers, host systems, or other serial devices.  D     -  Telnet character and binary profiles are supported for Inter-H        net sessions. Telnet options supported include: status (RFC 859),D        end of record (RFC 885), remote flow control (RFC 1080), echoG        (RFC 857), timing mark (RFC 860), binary (RFC 856), and suppress         go ahead (RFC 858).  E     -  Telnet Remote Console allows a user to establish a remote Tel- G        net connection to the management port on the terminal server and D        manage the server as if locally attached. The Telnet listenerF        23 can now be assigned to any server port as well as the remoteD        console. Any Telnet listener (23, 2001-20016) can be assigned         to be the remote console.  E  o  Internet Domain Name System (DNS) Support. The Domain Name System F     provides the translation from system name to Internet address. TheF     DECserver 90TL will interface to user programs and send queries toD     domain name servers for translating domain names to Internet ad-F     dresses, and Internet addresses to domain names (RFCs 1034, 1035).     o  Subnet Addressing (RFC 950).  D  o  Simple Network Management Protocol (SNMP). The SNMP agent allowsG     the DECserver 90TL to be managed by an SNMP network management sys- D     tem. Retrieving information from the terminal server is possibleD     using the SNMP GET and GET-NEXT requests. The SNMP SET operation  #                                   4        D     is fully supported providing the ability to modify DECserver pa-G     rameters as well as create and delete applicable table entries. The F     server can send unsolicited event alarms to specified SNMP manage-D     ment stations via the SNMP TRAP message. Server variables acces-D     sible via SNMP (RFC 1157) are defined by the Internet documents:H     MIB II (RFC 1213), RS232-like MIB (RFD 1317), the Character MIB (RFC
     1316).  G  o  Serial Line Internet Protocol (SLIP). A host computer that supports D     SLIP can use the DECserver 90TL serial port as it's network con-H     nection. This gives IP end nodes, which have no Ethernet controller,F     access to the network and to other serial-line attached TCP/IP endG     nodes. Any IP application (such as MAIL, X-Windows, NFS[R], Rlogin, =     FTP, etc.) can then be run over the SLIP link (RFC 1055).   D  The DECserver 90TL also implements and supports the Terminal DeviceE  /Session Management Protocol (TD/SMP) to manage multiple sessions at D  the device level. The DECserver 90TL provides the ability to commu-H  nicate with terminals that also implement this protocol (such as VT420,E  VT330+, or VT340+), and to assist in the management of multiple ses- F  sions for these devices. By implementing this protocol, the DECserverF  90TL can permit attached devices to maintain screen and keyboard con-E  text for multiple LAT and/or Telnet sessions, as well as allow these A  devices to run multiple LAT and/or Telnet sessions concurrently.   E  The DECserver 90TL implements the ODL (On Demand Loading) font load- E  ing protocol that allows Asian terminals that implement the ODL pro- F  tocol (such as VT382 or VT282) to communicate with an OpenVMS[*] hostH  via a terminal server. The Asian terminals will be able to request fontE  definitions from an OpenVMS host when connected to a DECserver 90TL. 4  This feature is supported only for LAT connections.  E  Software that runs on the DECserver 90TL is downline loaded over the F  network from a load host using MOP or BOOTP/TFTP. Terminal access us-H  ing the DECserver 90TL does not require DECnet running in the same ser-H  vice node; LAT uses the Ethernet addressing mechanism to transport ter-  minal messages.    ____________________   B  The   terms OpenVMS and VMS refer to the OpenVMS Operating System  #                                   5        G  Features such as login load balancing, multiple terminal sessions, au- G  tomatic failover, and remote printer support are provided and can lead   to greater user productivity.  D  For wide area network communications, terminal users can connect to<  remote hosts via Telnet through a TCP/IP router or gateway.  	  Features     Terminal Connection Management   H  Through the use of a simple command, users can establish a logical con-G  nection, called a session, to any service node that implements the LAT F  or Telnet protocol on the same Ethernet LAN, or to a remote host thatE  implements the TCP/IP protocol suite. This connection makes the ter- E  minal appear as if it were physically connected to the service node, E  and the terminal user can use standard system utilities and applica- D  tions supported by that node. Each terminal connected to the serverE  can connect to the same or a different service node on the Ethernet. F  Furthermore, several servers can be used to connect many terminals to  one or more service nodes.   F  A service node can have one or more services that are offered to DEC-D  server 90TL users. Services and nodes are identified by name. UsersD  always connect to services, not to nodes, although often one of the%  service names will be the node name.   E  In a VAXcluster environment, the DECserver 90TL sees each VAXcluster H  on the Ethernet as a collection of service nodes offering a common ser-F  vice. Each cluster node may also offer a service whose name is equiv-F  alent to its node name. In this case, a terminal user can connect ei-D  ther to the cluster service or a service associated with a particu-!  lar cluster node. Load Balancing   E  When a connection is made to a service, the actual node for the con- E  nection is determined by load balancing. Load balancing is a process F  the server uses when more than one node offers the same service. Ser-G  vice nodes do not have to be configured in a cluster in order for load D  balancing to be used. Service nodes with the same names may be run-D  ning different operating systems. Using the load balancing process,  #                                   6        E  the server connects to the node with the highest rating for the ser- G  vice desired. This rating is based on the current loading on the nodes   that offer the service.  4  This feature is supported only for LAT connections.    Multiple Sessions  D  The DECserver 90TL allows each user to establish and maintain up toG  eight sessions to one or more service nodes, up to a maximum of 64 per K  DECserver 90TL. Only one session per user can be active at a time. Through F  simple switching commands, the user can access the different sessionsE  without repeating a login dialogue each time. Some operating systems F  may impose limits on the number of LAT or Telnet sessions that a host  will support.    Multiple Session Management  H  The DECserver 90TL server allows direct communication with devices thatD  support the TD/SMP protocol. This protocol provides the ability forD  the attached device to maintain screen and keyboard context for theE  multiple LAT or Telnet sessions that the DECserver 90TL provides. By D  implementing the ability to directly communicate with this protocolF  to the attached device, the DECserver 90TL can now assist in the man-D  agement of context of these multiple sessions, as well as allow forH  simultaneous output to multiple LAT or Telnet sessions being maintained  by the device.     Outbound Connection Queues   H  If a terminal user requests a connection to a server, and the requestedE  service is currently in use, the server user may opt to have the re- D  quested connection queued to the remote service. If the user's portF  has been appropriately configured, this feature happens automaticallyD  whenever a connection fails for this reason. The connection requestF  is queued at the service node end and is processed first-in/first-outH  until such time as the user's connection request can be completed. ThisE  feature assists in the fair management of limited network resources. G  Once queued for connection, the user also has the option to cancel the G  queue entry and proceed with other sessions. This feature is supported   #                                   7        E  only for LAT connections. Similar functionality may be available via G  a print filter program on a Telnet host. Command Line Recall and Edit-   ing  F  The DECserver 90TL server supports multiple command line entry recall
  and editing.     Welcome Identification   G  The DECserver 90TL server standard welcome banner, which includes com- G  munications server type, version number, internal base level, and pro- E  tocol version number, is issued whenever a user successfully logs in D  to the server. The server will also print a Server-Manager-settableE  identification string. This can be useful for automatic server iden- G  tification or for small daily messages used for communication with the   server users.    Local Mode and Service Mode  E  For the most part, the environment provided by the DECserver 90TL is G  identical to the environment the user would experience if attached di- E  rectly to the service node. When operating in this mode, the user is D  said to be in Service Mode. Occasionally, such as during connectionD  establishment, the user interacts directly with the DECserver 90TL.8  When operating in this mode, the user is in Local Mode.  G  In Local Mode, the terminal input is interpreted directly by DECserver 0  90TL as commands to be performed by the server.  E  Local Mode has three different levels of privilege: privileged, non- H  privileged, and secure. Privileged mode is provided for the Server Man-I  ager to control the environment of the server and of the terminal users.TF  Access to this mode is password protected. Nonprivileged commands al-F  low the terminal user to control service sessions, set the port char-E  acteristics, and show server information. The Server Manager can set[D  the server to secure mode on a per-port basis, which further limitsG  the commands users can enter to only those that directly relate to theC  user's own port.r    #                                   8s T  D  H  Additional commands and displays to support the features available withE  the TD/SMP protocol are usable in Local Mode. These commands will beoE  used to enable or disable server recognition of the TD/SMP commands.i  F  The Server Manager environment is a logical extension of the user en-G  vironment. The Server Manager is treated as a server user with a priv-hE  ileged status. The Server Manager sets a terminal to this status us-rF  ing a command that requires a password. This privileged status allowsF  the Server Manager to enter commands not normally available to serverG  users. These commands set server characteristics, provide control overeE  server port usage, and provide the ability to control the user's ac-s)  cess to the server and network services.s  H  In Service Mode, the terminal input is passed directly to the connectedD  service node with several exceptions. One exception, called the lo-D  cal switch character, allows the user to enter Local Mode from Ser-G  vice Mode. The BREAK key can also be used for this function. Other ex- G  ceptions, called the forward and backward switch characters, allow thekF  user to switch between sessions without the need to enter local mode.D  The switch characters are disabled by default but can be enabled byF  command. Both CTRL/S and CTRL/Q are normally interpreted locally, but5  flow control using these characters can be disabled.e    Autoconnection   E  Autoconnection is a function that automatically connects a user ter-eD  minal to a service node when connection failures occur or upon userD  login to the server. In conjunction with this function, a dedicated>  or preferred service can be specified for each terminal user.  E  If a dedicated service is specified, the DECserver 90TL will attempteE  to connect to that service when a character is typed on the terminaluD  keyboard or when an existing connection fails. In dedicated serviceF  mode, only one session is available. As this mode is designed to sim-G  ulate a direct terminal connection, no local mode commands or messagestE  are available to the terminal user. Ports with dedicated service canlD  be logged out of the server automatically when the user logs out of  the service node.    #                                   9e o  c  E  If a preferred service is specified, the DECserver 90TL will attemptiE  to connect to that service as with the dedicated service mode of op-mD  eration. However, the terminal user can enter local mode and estab-  lish other sessions.t    Automatic Protocol Selectione  F  It is possible to connect to an Internet host or LAT service automat-D  ically without explicitly identifying the connection as LAT or Tel-E  net. If the port is configured with a value for the default protocolnE  as "ANY," the server will attempt a LAT connection first to the namelD  specified in the LAT service field. If the service is not availableE  or unknown, the server will then automatically attempt a Telnet con- 7  nection to the Internet host specified in the command.e    Automatic Session Failoverm  E  If a service is available on two or more service nodes and a connec-wE  tion to a service fails, the server will attempt to connect the useraE  to another service node offering the same service. The user does not D  have to be connected already to that service node. Furthermore, theE  user's context at the time of failure is not automatically restored,oD  and login to the new service is required. This feature is supported!  only for LAT connections. Groupsc  D  Every terminal and service node in a LAT network is a member of oneH  or more groups, which are specified by a list of numbers from 0 to 255.D  Groups allow an easy means of subdividing the network into what ap-D  pears to be many smaller networks. A terminal user is only aware of=  the services that are offered by nodes in the same group(s).   G  The Server Manager can specify the authorized group(s) in which a ter-iD  minal is a member. The authorized groups define the set of servicesF  that the user is allowed to access. In addition, for those nodes thatF  implement group codes, a user can further limit access to services byD  disabling some of the authorized groups using a nonprivileged groupF  command. The user-settable group codes are a subset of the authorized  groups.    #                                  10     v  G  Groups provide a restrictive view of the network. This restricted viewnF  is mainly for user convenience. Groups apply only to LAT connections.  	  Security   E  The DECserver 90TL provides functions that enhance security featuresID  already available in the service nodes. DECserver 90TL security in-G  cludes the ability to lock a terminal's keyboard from other users, op-oF  tional login protection, and nonprivileged local mode of operation as  a default.t  D  A user can lock the terminal using a lock password. This allows theE  user to leave sessions running at the terminal without fear of secu- D  rity violations. When a terminal is locked, all input from the ter-F  minal is ignored until the lock password is re-entered. The lock fea-,  ture can be disabled by the Server Manager.  H  Each terminal port can be set to operate in a secure mode, which causesF  all commands that relate to other users to be disabled for that port.  F  Login passwords can be enabled on a per-port basis by the Server Man-G  ager. If enabled, the terminal user must enter a login password to ac-   cess server functions.e  E  DECserver 90TL users normally have access to the nonprivileged localiD  mode. In this mode, users may only issue commands that affect theirJ  own terminal environment. The server has a privileged mode for the Server/  Manager's use. The mode is password protected.     Online HELP Facilityh  F  A full online reference HELP facility is available. The server's HELPE  command provides information on the correct syntax and details abouteD  each command. In addition, a tutorial HELP feature allows new usersG  to learn the basics of DECserver 90TL operation quickly. Tutorial HELPv?  can be entered upon logging into the server. Directory Serviceo  E  Any DECserver 90TL user can obtain a directory of services available G  to that user with a SHOW SERVICES command. Services for which the usereD  is not authorized will not be displayed. Services apply only to LAT
  connections.u  #                                  11  e  o    Permanent Characteristics  F  The DECserver 90TL maintains permanent characteristics in nonvolatileD  memory, which is retained even when the power is disconnected. Per-D  manent characteristics are maintained for service and server param-D  eters as well as per-port parameters. Permanent characteristics canE  be reset to factory defaults by pressing the Factory Reset button on2;  the hardware unit while the unit is in power up self test.e  #  Port Characteristics Configuration2  E  Characteristics governing the operation of an individual port can benI  displayed by a nonprivileged terminal user interactively from the user'sdG  terminal. Many of the characteristics may be set by the user, but cer-eJ  tain characteristics are privileged and can only be changed by the Server	  Manager.   D  Port parameters that can be set and displayed include: speed, char-F  acter size, group codes, parity, terminal type, access, autobaud, de-)  fault protocol, and password protection.c    Port Access  G  A port on a DECserver 90TL can be configured in different ways depend-aG  ing on the device attached to the port and its intended use. DECserveriG  90TL uses MJ8 connectors as the physical interface. The DECserver 90TLeH  utilizes DEC 423-A electrical interface standard for local connections,D  which is compatible with the DEC 232-D interface and supports eightF  asynchronous devices operating at speeds up to 57.6 Kbps with DTR/DSR9  (Data Terminal Ready/Data Terminal Set Ready) signaling.   E  Port access is the characteristic that determines how a port can ac-i<  cess or be accessed by interactive users and service nodes.  F  o  Access Local - Designed for interactive terminals. This allows theF     device (typically an interactive terminal) attached to the port to     CONNECT to LAT or Telnet.u      #                                  12e r  o  I  o  Access Remote - Designed for application-driven devices such as asyn- H     chronous printers that are allocated by a service node process. ThisD     allows the implementation of certain shared printers by multiple     service nodes.  E  o  Access Dynamic - Designed for devices (such as personal computersiF     or printers with keyboards) that require both Local and Remote ac-	     cess.t  E  o  Access None - Designed to allow the Server Manager to disable thev     use of a port.  F  With printer support capabilities, the configuration procedure of re-E  mote printers needs to be done once and will be automatically recon-eF  figured on system startup. The particular server port must be config-F  ured for remote access and set up to match the characteristics of theF  printer. The system startup command file must be modified to call theD  two command files provided with the service node software. Finally,E  the command files themselves must be customized to reflect the envi- G  ronment of their node. The server can optionally queue remote connectspF  if these connects cannot be satisfied immediately. This queue manage-D  ment can be enabled for the server by the Server Manager. Note that!  this is a connection queue only.V  J  Improved printer sharing allows a printer port on the server to be shared.  among hosts using LAT and hosts using Telnet.    Terminal Operationw  F  The DECserver 90TL software supports the simultaneous operation of upF  to eight asynchronous devices at speeds from 75 bps to 57.6 Kbps. The  software also supports:    o  Data leads only support     o  DSR logout    o  Signal check    o  Signal control    o  DSR/DTR flow control  #                                  13  n       o  XON/XOFF flow control   9  o  Split speed (transmit and receive) terminal operation   *  o  Block Mode transfers up to 2,048 bytes  "  o  Automatic line speed detection  +  o  Digital personal computer file transfera    o  Data transparency mode  :  o  Ability to pass break character and error notification  ?  o  Ability to assist in multiple session management via TD/SMP     Server Management  E  Several facilities exist for managing and troubleshooting server op-aG  eration. The Server Manager in privileged mode can set up server iden-dF  tification information, change port characteristics, or fine tune theD  operating characteristics of the server. Troubleshooting facilitiesG  include diagnostic tests, a remote console feature, and online statis-e  tics.  I  A privileged user can diagnose Ethernet communications problems by loop-aG  ing messages to an Ethernet host and through the Ethernet hardware in-hD  terface at the server. To diagnose terminal problems, users can ex-G  ecute a command to transmit test data to their terminal, or the Serverm,  Manager can send test data to any terminal.  D  The capability also exists for the Server Manager to test a serviceH  connection by sending data from the initiating port to the service nodeD  and back again. The data is then compared and any discrepancies re-D  ported. At the service node, the data can be looped back by the LATE  protocol, or internally or externally at the service port. This fea- E  ture is supported only by DECserver 90TL service nodes; VAX/VMS ser- <  vice nodes do not support this service loopback capability.    #                                  14t -  t  E  The server maintains a variety of statistics and counters. These in-cI  clude the following: Ethernet data link statistics, LAT protocol statis-eD  tics, and port error statistics. This data can be displayed and ze-G  roed by the Server Manager. Server parameters that can be modified andfD  displayed include the server identification, circuit timer, session  limits, and login limits.  F  Internet statistics are also maintained by the server. Internet char-E  acteristics such as Internet address and subnet mask can be modified F  and displayed. IP, ICMP, TCP, IP, UDP, DNS, and SNMP protocol statis-  tics can be displayed.     Remote Server Managemente  G  The DECserver 90TL implements the console carrier feature that enableseE  access to the DECserver 90TL local mode from either a Telnet host or G  a Phase IV or V DECnet host on the same LAN. With the exception of re- F  mote console port configuration, the entire local mode user interfaceD  is accessible to the remote console carrier user. This includes theD  privileged commands if the user knows the server's privileged pass-F  word. This capability allows centralized server management and remote  server diagnosis.    Communicationsp  F  DECserver 90TL software is designed to run on DECserver 90TL hardwareD  exclusively, which includes an Ethernet interface for connection to  an Ethernet transceiver cable.i  E  The DECserver 90TL hardware has eight MJ8 connectors integral to they@  box. Each port can be individually configured in various modes:    o  Data leads only     o  Signal Control  F  o  Data leads with DSR logout (if a terminal is powered down the ses-'     sion is automatically disconnected)t  F  o  Data leads with signal check (checks signal status before and dur-     ing a session)  #                                  15s l  e    o  DSR/DTR flow control    o  Long Break logouta    DECserver 90TL Operation   E  The DECserver 90TL ROM-based firmware provides the necessary mainte- D  nance operation protocols for downline loading DECserver 90TL soft-F  ware from a TCP/IP host via BOOTP/TFTP or from a Phase IV or V DECnetD  load host over the Ethernet into server memory. All self-test diag-E  nostics are in DECserver 90TL ROM and are executed on power-up prior E  to downline loading the server. In the event of a bugcheck caused byiD  a fatal error, the unit will normally attempt to upline dump serverE  memory to the load host. The upline dump is via either BOOTP/TFTP ormD  via MOP. Following this, the unit will automatically initialize it-!  self and invoke a downline load.h  -  DECserver 90TL Configuration and Performance   D  The process of configuring the DECserver 90TL is based primarily onF  tradeoffs of cost and performance within the realm of satisfying userD  application requirements. Network applications will range from low-G  speed/low-cost to those of relatively high performance (e.g., connect-nG  ing high-speed local terminals to local hosts within a local area net-vG  work). The performance of a given server is a function of the expectedsE  network traffic, the load on hosts to which terminals are connected,rI  and resultant processing pursuant to the dedicated function of the unit.r-  Thus performance depends on several factors:e    o  Number of terminalsi  @  o  Number of host systems with active connections to the server    o  Terminal speeds     o  Terminal user applications  #  o  Number and size of host buffersc    o  Terminal workloada  #                                  16s e  0  D  The DECserver 90TL can sustain an aggregate character throughput of  30K characters per second.i  D  In order to achieve a viable configuration, the user and/or a Digi-D  tal software specialist should perform a level of application anal-H  ysis that addresses the factors above. The actual maximum data through-H  put cannot be calculated by multiplying the number of lines by the lineD  speed, since many factors already discussed in this section may re-  duce the actual throughput.  %  Restrictions on DECserver 90TL Usagep  G  While terminal connections using the DECserver 90TL have been designedtH  to simulate direct terminal connections as much as possible, a few dif-E  ferences necessarily exist because of the nature of the product. Un-eD  der most circumstances, these differences are not noticed by termi-F  nal users or service node application programs. However, applicationsE  that are directly dependent on the following functions may not oper-c!  ate as with a direct connection:r  E  o  Applications that depend on an extremely fast response time (typ-r'     ically less than 200 ms) to operates  F  o  Applications that utilize an alternate terminal driver in the ser-
     vice nodee  F  o  Applications that expect incoming connections to have fixed device	     namesr  &  Use of the DECserver 90TL with Modems  D  The DECserver 90TL provides DSR and DTR signals that can be used toE  control some modems. The control signals required between a communi-rD  cations server and a modem are determined by the modem and, in someF  cases, Telecommunication Utility regulations. To provide satisfactory4  operation, the modem must be configured as follows:  D  o  DSR - The modem must assert DSR when it has connected to an openH     telephone line and the modem is ready to establish an outgoing call.D     The modem must de-assert DSR when it is not connected to an open     telephone line.c  #                                  17r l  o  H  o  DTR - When DTR is asserted by the server, the modem must be put intoD     a state of readiness for receiving an incoming call or the modemD     must be made ready to initiate an outgoing call. When DTR is de-H     asserted, the modem must disconnect from the telephone line and pre-6     vent subsequent connections to the telephone line.  E  Modems that cannot be configured in this way are not compatible withu  the DECserver 90TL.  D  The DECserver 90TL can operate with a modem that is speed bufferingF  only if the modem and server are configured for XON/XOFF flow controlE  and the data is non-binary. For binary data communication with a mo-sD  dem that is speed buffering and is not configured for XON/XOFF flowE  control, a communications server with CTS/RTS flow control is neededd  (such as the DECserver 700).a  D  The modems that have been tested with the DECserver 90TL are speci-6  fied in the System Support Addendum (SSA 38.71.03-x).    HARDWARE REQUIREMENTS  D  Processor and/or hardware configurations as specified in the System#  Support Addendum (SSA 38.71.03-x).o    SOFTWARE REQUIREMENTS    For VMS-Based Systems:d    o  OpenVMS Operating System    o  DECnet-VAX    For ULTRIX-Based Systems:    o  ULTRIX Operating Systemn  /  o  MOP (included with ULTRIX operating system)g    o  DECnet-ULTRIXa    For Non-Digital UNIX Systems:  #                                  18        F  The following generic operating systems are supported. Note that com-D  plete support can not be granted on systems where customization hasE  taken place. Also note that some UNIX implementations not listed be-e9  low may operate successfully, but no support is implied.m  
  o  SunOS[TM]e    o  OSF[R]1s    o  IBM[R] AIX[R]t  !  o  SCO[TM] UNIX System V[TM]/386o    o  HP[R]-UX  E  Some system V systems, such as HP-UX and SCO, may not support an up-p   line dump of the server memory.    For MS-DOS[R]-Based Systems:"    o  MS-DOS Operating Systemc    o  PATHWORKS for DOSm  H  Refer to the System Support Addendum for availability and required ver-J  sions of prerequisite/optional software (SSA 38.71.03-x which is included  in this file).t    ORDERING INFORMATIONm  !  o  Software License: QL-MJPA9-AAmF     (DECserver 90TL TRAD License is included with hardware, not avail-     able separately)    o  Software Kit: QA-MJPA*-H*o8     (DECserver 90TL software and software documentation)  G  *  Denotes variant fields. For additional information on available li-vE     censes, services, and media, refer to the appropriate price book.o    #                                  19          SOFTWARE LICENSINGi  F  This software is furnished only under a license. For more informationF  about Digital's licensing terms and policies, contact your local Dig-
  ital office.e  E  The DECserver 90TL software license applies to the DECserver 90TL onfE  which the server software runs, not to service host node CPUs in ther	  network.n  F  This product does not provide support for the OpenVMS License Manage-E  ment Facility. A Product Authorization Key (PAK) is not required fors4  installation or use of this version of the product.    SOFTWARE PRODUCT SERVICES  F  A variety of service options are available from Digital. For more in-.  formation, contact your local Digital office.    SOFTWARE WARRANTY  H  Warranty for this software product is provided by Digital with the pur-G  chase of a license for the product as defined in the Software Warrantyg  Addendum of this SPD.  A  [R] Domain is a registered trademark of Apollo Computer, Inc., aw*     subsidiary of Hewlett-Packard Company.  ?  [R] FTP is a registered trademark of Schere Laboratories, Inc.   =  [R] HP is a registered trademark of Hewlett-Packard Company.c  @  [R] IBM, AT, and AIX are registered trademarks of International"     Business Machines Corporation.  ?  [R] MS-DOS is a registered trademark of Microsoft Corporation.a  <  [R] NFS is a registered trademark of Sun Microsystems, Inc.    #                                  20r a  s    D  [R] OSF is a registered trademark of Open Software Foundation, Inc.  @  [R] UNIX is a registered trademark of UNIX System Laboratories,     Inc.  6  [TM]SCO is a trademark of Santa Cruz Operations, Inc.  3  [TM]SunOS is a trademark of Sun Microsystems, Inc.d  @  [TM]System V is a trademark of American Telephone and Telegraph     Company.  @  [TM]The DIGITAL Logo, CI, DEC, DECbridge, DECmate, DECnet, DEC->     server, DECstation, DECsystem, DEMPR, EtherWORKS, LA, LAT,@     LXY, MicroVAX, OpenVMS, PATHWORKS, RX, ThinWire, TK, ULTRIX,B     VAX, VAXcluster, VAXft, VAXserver, VAXstation, VMS, VT, VT420,A     VT330, and VT340 are trademarks of Digital Equipment Corpora-e	     tion.   ;   1997 Digital Equipment Corporation. All rights reserved.t                                      #                                  21e  r    Systems  Support	  Addendums  D  ___________________________________________________________________D  ___________________________________________________________________  D  PRODUCT NAME:  DECserver 90TL Software, Version 1.1c SSA 38.71.03-A    HARDWARE REQUIREMENTS    OpenVMS[*] Processors    Processors Supported:    VAX:      VAX 4000 Model 100,            VAX 4000 Model 200,            VAX 4000 Model 300,            VAX 4000 Model 400,            VAX 4000 Model 500,            VAX 4000 Model 600e  %            VAX 6000 Model 200 Series,f%            VAX 6000 Model 300 Series,w%            VAX 6000 Model 400 Series,l%            VAX 6000 Model 500 Series, $            VAX 6000 Model 600 Series  $            VAX 7000 Model 600 Series  (            VAX 8200, VAX 8250, VAX 8300,(            VAX 8350, VAX 8500, VAX 8530,(            VAX 8550, VAX 8600, VAX 8650,(            VAX 8700, VAX 8800, VAX 8810,'            VAX 8820, VAX 8830, VAX 8840e    ____________________.  C  The   terms OpenVMS and VMS refer to the OpenVMS Operating System.n  C                                DIGITAL                    June 1997   D                                                          AE-PME6E-TE s  s                VAX 9000 Model 110,            VAX 9000 Model 210,%            VAX 9000 Model 300 Series,t$            VAX 9000 Model 400 Series  %            VAX 10000 Model 600 Seriese              VAXft Model 110,e            VAXft Model 310,n            VAXft Model 410,r            VAXft Model 610,e            VAXft Model 612  "            VAX-11/730, VAX-11/750,!            VAX-11/780, VAX-11/785p  &  MicroVAX: MicroVAX II, MicroVAX 2000,&            MicroVAX 3100 Model 10/10E,&            MicroVAX 3100 Model 20/20E,"            MicroVAX 3100 Model 30,"            MicroVAX 3100 Model 40,"            MicroVAX 3100 Model 80,"            MicroVAX 3100 Model 90,(            MicroVAX 3300, MicroVAX 3400,(            MicroVAX 3500, MicroVAX 3600,'            MicroVAX 3800, MicroVAX 3900i  +  VAXstation:VAXstation II, VAXstation 2000,u$            VAXstation 3100 Model 30,$            VAXstation 3100 Model 38,$            VAXstation 3100 Model 40,$            VAXstation 3100 Model 48,$            VAXstation 3100 Model 76,,            VAXstation 3200, VAXstation 3500,          #                                   2     e    +            VAXstation 3520, VAXstation 3540i  $            VAXstation 4000 Model 60,$            VAXstation 4000 Model 90,            VAXstation 4000 VLC  (  VAXserver: VAXserver 3100 Model 10/10E,'            VAXserver 3100 Model 20/20E,i:            VAXserver 3300, VAXserver 3400, VAXserver 3500,:            VAXserver 3600, VAXserver 3602, VAXserver 3800,            VAXserver 3900e  $            VAXserver 4000 Model 200,$            VAXserver 4000 Model 300,#            VAXserver 4000 Model 500c  $            VAXserver 6000 Model 210,$            VAXserver 6000 Model 220,$            VAXserver 6000 Model 310,$            VAXserver 6000 Model 320,$            VAXserver 6000 Model 410,$            VAXserver 6000 Model 420,$            VAXserver 6000 Model 510,$            VAXserver 6000 Model 520,$            VAXserver 6000 Model 610,$            VAXserver 6000 Model 620,#            VAXserver 6000 Model 630-                        #                                   3t    t    Processors Not Supported:  &  MicroVAX I, VAXstation I, VAX-11/725,  VAX-11/782, VAXstation 8000    ULTRIX Processors     VAX-Based Processors Supported:  %  VAX:      VAX 6000 Model 200 Series,l%            VAX 6000 Model 300 Series, %            VAX 6000 Model 400 Series,c$            VAX 6000 Model 500 Series  @            VAX 8200, VAX 8250, VAX 8300, VAX 8350, VAX 8500, VAXB            8530, VAX 8550, VAX 8600, VAX 8650, VAX 8700, VAX 8800,1            VAX 8810, VAX 8820, VAX 8830, VAX 8840p  A            VAX 9000 Model 110, VAX 9000 Model 210, VAX 9000 Models=            300, VAX 9000 Model 410 Series, VAX 9000 Model 420   -            VAX-11/750, VAX-11/780, VAX-11/785p  &  MicroVAX: MicroVAX II, MicroVAX 2000,(            MicroVAX 3100, MicroVAX 3300,(            MicroVAX 3400, MicroVAX 3500,(            MicroVAX 3600, MicroVAX 3800,            MicroVAX 3900  -  VAXstation:VAXstation II, VAXstation II/GPX, ,            VAXstation 2000, VAXstation 3100,,            VAXstation 3200, VAXstation 3500,+            VAXstation 3520, VAXstation 3540s  *  VAXserver: VAXserver 100, VAXserver 2000,*            VAXserver 3100, VAXserver 3300,*            VAXserver 3400, VAXserver 3500,      #                                   4     o    *            VAXserver 3600, VAXserver 3602,)            VAXserver 3800, VAXserver 3900e  $            VAXserver 6000 Model 210,$            VAXserver 6000 Model 220,$            VAXserver 6000 Model 310,$            VAXserver 6000 Model 320,$            VAXserver 6000 Model 410,$            VAXserver 6000 Model 420,$            VAXserver 6000 Model 510,#            VAXserver 6000 Model 520i  !  RISC-Based Processors Supported:s  -  DECstation:DECstation 2100, DECstation 3100,i            DECstation 3100se  3            Personal DECstation 5000 Model 20/25 HX,o3            Personal DECstation 5000 Model 20/25 MX,n3            Personal DECstation 5000 Model 20/25 TX,l5            Personal DECstation 5000 Model 20/25 PXG+,a:            Personal DECstation 5000 Model 20/25 PXG Turbo+  0            DECstation 5000 Model 120/125/133 CX,0            DECstation 5000 Model 120/125/133 HX,0            DECstation 5000 Model 120/125/133 MX,0            DECstation 5000 Model 120/125/133 PX,0            DECstation 5000 Model 120/125/133 TX,1            DECstation 5000 Model 120/125/133 PXG,e2            DECstation 5000 Model 120/125/133 PXG+,7            DECstation 5000 Model 120/125/133 PXG Turbo,e7            DECstation 5000 Model 120/125/133 PXG Turbo+t  (            DECstation 5000 Model 200 CX,(            DECstation 5000 Model 200 HX,(            DECstation 5000 Model 200 MX,      #                                   5u t  f    (            DECstation 5000 Model 200 PX,(            DECstation 5000 Model 200 TX,)            DECstation 5000 Model 200 PXG,-*            DECstation 5000 Model 200 PXG+,/            DECstation 5000 Model 200 PXG Turbo,e/            DECstation 5000 Model 200 PXG Turbo+n  (            DECstation 5000 Model 240 HX,(            DECstation 5000 Model 240 MX,(            DECstation 5000 Model 240 TX,*            DECstation 5000 Model 240 PXG+,/            DECstation 5000 Model 240 PXG Turbo+a    DECsystem: DECsystem 3100, #            DECsystem 5000 Model 25,M$            DECsystem 5000 Model 200,$            DECsystem 5000 Model 240,*            DECsystem 5100, DECsystem 5400,*            DECsystem 5500, DECsystem 5810,*            DECsystem 5820, DECsystem 5830,)            DECsystem 5840, DECsystem 5900t     MS-DOS[R] Processors Supported:  F  Personal DECstation 316, 325 with DEC EtherWORKS Turbo or LC Computer  Ethernet adapteri    Other Hardware Required  H  The DECserver 90TL software runs on any of the following packaged hard-  ware options:    o  DSRVE-**  E  *  Denotes product variant models. For additional information, referi"     to the appropriate price book.      #                                   6t t  a  F  The DECserver 90TL supports ThinWire connections integral to the box.E  The DECserver 90TL can be connected to a ThickWire Ethernet using an H  Ethernet transceiver connection, transceiver drop cable, and a repeaterF  (such as a DECMR, DEMPR, or DESPR). In a DEChub90, a DECbridge 90 can"  be used in place of the repeater.    Optional Hardware    Terminals Supported  D  The DECserver 90TL software supports the following Digital terminal  devices that have keyboards:      o  LA12, LA34, LA35, LA36, LA38    o  All VTxxx terminalse  #  Supported Terminal Parameters are:   -  o  Character size: 7 or 8 bits per charactere    o  Parity: Even, Odd, or None  G  The automatic line speed detection (Autobaud) feature is supported forTE  either seven-bit characters with even parity or eight-bit characterse  with no parity.  E  The DECserver 90TL software also supports Digital Asian terminal de-aE  vice variants, including VT282 and VT382, when accessed from OpenVMS E  /Hanzi systems. Please refer to the OpenVMS Operating System SPD forl)  a complete listing of supported devices.o  E  The DECserver 90TL software also supports Digital Asian terminal de-oF  vice variants when accessed from OpenVMS/Japanese systems. Please re-G  fer to the OpenVMS Operating System SPD for a complete listing of sup-   ported devices.  E  The DECserver 90TL software also supports the following Digital Per-dF  sonal Computers (PCs) in both terminal emulation mode and file trans-
  fer mode:    o  Professional 325, 350, 380  #                                   7y g  e  !  o  Rainbow 100A, 100B, 100+, 190-    o  DECmate II    o  DECmate IIIw    o  VAXmater    o  DECstation  D  Note: This product is not warranted to support non-Digital terminalD  devices or personal computers. However, terminals supporting VT100-G  or VT200-like characteristics and personal computers supporting IBM[R]TF  PC, IBM PC/XT, and IBM PC/AT[R] characteristics may operate with this	  product.b    Printers Supported   H  The DECserver 90TL software supports the following Digital asynchronous-  printers when accessed from OpenVMS systems:u  ;  o  All LJ, LA, LQP, LXY, LN0, LG, and DTC printing devices   D  The DECserver 90TL software also supports Digital Asian printer de-E  vice variants when accessed from OpenVMS/Hanzi systems. Please referaH  to the OpenVMS Operating System SPD for a complete listing of supported	  devices.r  D  The DECserver 90TL software also supports Digital Asian printer de-F  vice variants when accessed from OpenVMS/Japanese systems. Please re-G  fer to the OpenVMS Operating System SPD for a complete listing of sup-s  ported devices.    Modems Supportedh  D  The DECserver 90TL provides DSR and DTR signals that can be used toE  control some modems. The control signals required between a communi- D  cations server and a modem are determined by the modem and, in someF  cases, Telecommunication Utility regulations. To provide satisfactory4  operation, the modem must be configured as follows:  D  o  DSR - The modem must assert DSR when it has connected to an openH     telephone line and the modem is ready to establish an outgoing call.  #                                   8n i  r  D     The modem must de-assert DSR when it is not connected to an open     telephone line.h  H  o  DTR - When DTR is asserted by the server, the modem must be put intoD     a state of readiness for receiving an incoming call or the modemD     must be made ready to initiate an outgoing call. When DTR is de-H     asserted, the modem must disconnect from the telephone line and pre-6     vent subsequent connections to the telephone line.  E  Modems that cannot be configured in this way are not compatible withe  the DECserver 90TL.  D  The DECserver 90TL can operate with a modem that is speed bufferingF  only if the modem and server are configured for XON/XOFF flow controlE  and the data is non-binary. For binary data communication with a mo- D  dem that is speed buffering and is not configured for XON/XOFF flowE  control, a communications server with CTS/RTS flow control is needed   (such as the DECserver 700).   E  The following modems have been tested and, when properly configured,h(  are compatible with the DECserver 90TL:    o  DECmodem V32  	  o  DF242g  	  o  DF224c  	  o  DF212d  F  Note: This server is not warranted to support modems other than thoseE  listed. However, modems that support control signaling only with in--E  band signals and/or DSR/DTR can operate with this server for certaint  data communications.n    Disk Space Requirements  <  Disk Space Requirements for OpenVMS (Block Cluster Size=1):    #                                   9l f  e    (  Disk space required for    3,550 blocks  installation:  (  Disk space required for    3,150 blocks  use (permanent):   $  Disk Space Requirements for ULTRIX:  (  Disk space required        1,331 Kbytes  for installation ande  permanent:S  !  Disk Space Requirements for DOS:h  &  Disk space required for    625 Kbytes  installation:  &  Disk space required for    610 Kbytes  use (permanent):   %  Disk Space Requirements for UNIX[R]:E  (  Disk space required        1,731 Kbytes  for installation andd  permanent:m  F  These counts refer to the disk space required on the system disk. TheE  sizes are approximate; actual sizes may vary depending on the user's 9  system environment, configuration, and software options.     CLUSTER ENVIRONMENT  D  This layered product is fully supported when installed on any validG  and licensed VAXcluster* configuration without restrictions. The HARD-iG  WARE REQUIREMENTS sections of this product's Software Product Descrip-tF  tion and System Support Addendum detail any special hardware required  by this product.N    #                                  10m o  a  F  *  V5.x VAXcluster configurations are fully described in the VAXclus-D     ter Software Product Description (29.78.xx) and include CI, Eth-1     ernet, and Mixed Interconnect configurations.     SOFTWARE REQUIREMENTS    For VAX-Based Systems:e  (  o  OpenVMS Operating System V5.0 - V5.5    o  DECnet-VAX V5.0 - V5.5    OpenVMS Tailoring:o  E  For OpenVMS V5.x systems, the following OpenVMS classes are requiredi0  for full functionality of this layered product:    o  OpenVMS Required Saveset    o  Network Support   
  o  UtilitiesT  D  For more information on OpenVMS classes and tailoring, refer to theE  OpenVMS Operating System Software Product Description (SPD 25.01.xx)     For ULTRIX-Based Systems:  (  o  ULTRIX Operating System V4.0 - V4.2A    o  MOP V4.0-V4.2o+     (included with ULTRIX operating system)n    o  DECnet-VAX V5.0 - V5.5    For Non-Digital UNIX Systems:  F  The following generic operating systems are supported. Note that com-D  plete support can not be granted on systems where customization hasE  taken place. Also note that some UNIX implementations not listed be-l9  low may operate successfully, but no support is implied.e    o  SunOS[TM] Release 4.0p  #                                  11t s  e    o  OSF/1[R] V1.0t    o  IBM AIX[R] Version 3.1.1  3  o  SCO[TM] UNIX System V[TM]/386 Release 3.2, V2.0f    o  HP[R]-UX 8.0  E  Some System V systems, such as HP-UX and SCO, may not support an up-i   line dump of the server memory.    For MS-DOS-Based Systems:  ?  For each MS-DOS System acting as a load host or dump receiver:v  3  o  MS-DOS Operating System V3.1, V3.3, V4.01, V5.0     o  PATHWORKS for DOS V4.1    OPTIONAL SOFTWARE  &  o  Terminal Server Manager V1.5 - 1.6    GROWTH CONSIDERATIONS  E  The minimum hardware/software requirements for any future version ofaD  this product may be different from the requirements for the current	  version.o    DISTRIBUTION MEDIAu    For VAX-Based Systems: !     TK50 9-track 1600 BPI Magtaped    For ULTRIX-Based Systems:!     TK50 9-track 1600 BPI Magtapee    For MS-DOS-Based Systems:     RX24 and RX33I  #                                  12k f  t    For UNIX-Based Systems:!     RX23, Tape Cartridge: QIC-150s    ORDERING INFORMATIONf  !  o  Software License: QL-MJPA9-AAiF     (DECserver 90TL Traditional License is included with hardware, not     available separately)s    o  Software Kit: QA-MJPA*-H*a8     (DECserver 90TL software and software documentation)  G  *  Denotes variant fields. For additional information on available li- E     censes, services, and media, refer to the appropriate price book.   G  The above information is valid at time of release. Please contact yourp:  local Digital office for the most up-to-date information.    A  [R] Domain is a registered trademark of Apollo Computer, Inc., as*     subsidiary of Hewlett-Packard Company.  ?  [R] FTP is a registered trademark of Schere Laboratories, Inc.X  =  [R] HP is a registered trademark of Hewlett-Packard Company.,  @  [R] IBM, AT, and AIX are registered trademarks of International"     Business Machines Corporation.  ?  [R] MS-DOS is a registered trademark of Microsoft Corporation.   <  [R] NFS is a registered trademark of Sun Microsystems, Inc.  A  [R] OSF/1 is a registered trademark of Open Software Foundation,_     Inc.  @  [R] UNIX is a registered trademark of UNIX System Laboratories,     Inc.  6  [TM]SCO is a trademark of Santa Cruz Operations, Inc.  3  [TM]SunOS is a trademark of Sun Microsystems, Inc.s  #                                  13     X    @  [TM]System V is a trademark of American Telephone and Telegraph     Company.  @  [TM]The DIGITAL Logo, CI, DEC, DECbridge, DECmate, DECnet, DEC-B     server, DECstation, DECsystem, DEMPR, Digital, EtherWORKS, LA,C     LAT, LXY, MicroVAX, OpenVMS, PATHWORKS, RX, RX33, ThinWire, TK, C     ULTRIX, VAX, VAXcluster, VAXft, VAXmate, VAXserver, VAXstation, A     VMS, VT100, VT420, VT330, and VT340 are trademarks of Digital      Equipment Corporation.  ;   1997 Digital Equipment Corporation. All rights reserved.8                                                        #                                  148