     	  Software   Product  Description  D  ___________________________________________________________________  H  PRODUCT NAME:  DECserver 300 for VMS[*] and MS-DOS[R], Version 2.2c SPD	  25.J1.05     DESCRIPTION  G  DECserver 300 for VMS and MS-DOS, Version 2.2c software is an enhanced 8  software and maintenance release for the DECserver 300.  D  The DECserver 300 software provides concurrent Local Area TransportE  (LAT) and Telnet TCP/IP protocol support from a DECserver 300 termi- F  nal server to enable connectivity to host systems that utilize LAT orJ  TCP/IP protocols. The TCP/IP protocol suite is used to connect to UNIX[R]E  host systems and other host systems that support the TCP/IP protocol   suite.   G  The DECserver 300 Terminal Server is an Ethernet Communications Server D  for Ethernet Local Area Networks. The DECserver 300 provides a con-G  venient method to logically connect up to sixteen digital asynchronous D  terminals to one or more service nodes (hosts) on an Ethernet. OnceG  the terminal is connected, a user can utilize application programs and F  utilities as though the terminal was directly connected to a host viaD  a DMF32, DHU11, or DHV11/DHQ11 device, with a few exceptions. Thus,D  it may be possible to utilize the DECserver 300 to connect all ter-G  minals to service nodes in place of traditional interfaces, except for G  host console terminals and remote connection via dial-in modems, which   are not supported.   E  The DECserver 300 uses MMJs (Modified Modular Jacks) for the attach- E  ment of asynchronous devices. The MMJ segregates a Data from a Voice D  connection. The DECserver 300 utilizes the EIA 423-A electrical in-E  terface standard for local connections. EIA 423-A is compatible with G  the EIA 232-D interface and supports DTR/DSR (Data Terminal Ready/Data     ____________________   C  The   terms OpenVMS and VMS refer to the OpenVMS operating system.   D                                DIGITAL                   August 1997  D                                                          AE-NE47G-TE       D  Set Ready) signals. EIA 423-A supports longer cable runs and higher  signaling speeds.  E  The DECserver 300 does not support connections to wide area networks D  via modems. However, it does provide the capability for connections  to non-LAT hosts.  D  The DECserver 300 also allows for host-initiated connections to se-F  rial printers. A print symbiont on service nodes can initiate connec-D  tions to serial printers connected to DECserver 300 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 9  requests may be queued first-in/first-out at the server.   @  Port-to-port connections on the same server are also supported.  E  The DECserver 300 implements the LAT protocol for communication with F  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-D  formance gain may be realized by using the DECserver 300 versus di-F  rect terminal connections via traditional asynchronous backplane com-  munications interfaces.  E  The DECserver 300 also implements the TCP/IP protocol suite for com- D  munication with host systems that implement TCP/IP. The TCP/IP pro-F  tocols are 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:   G  o  Transmission Control Protocol (TCP) is the Internet standard trans- G     port level protocol that provides the reliable, end-to-end full du- G     plex, stream service that supports many application protocols. (RFC      793)          #                                   2        F  o  User Datagram Protocol (UDP) is an Internet protocol that providesE     datagram service to application programs, allowing an application E     program on one machine to send a datagram to an applications pro- F     gram on another machine. UDP is necessary for the Domain Name Sys-D     tem 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 translateH     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 asF     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- @     minal was directly connected to the remote system. (RFC 854)  J     Both Telnet client and server capabilities are provided. Telnet clientD     provides the ability to connect to any remote TCP port at an In-D     ternet address on a local area network (LAN) or a wide area net-F     work (WAN). Telnet client allows the user to specify a remote com-8     puter by Internet address as well as by domain name.  #                                   3        D     Telnet server provides the ability to accept connection requestsD     from Internet hosts on a LAN or WAN to DECserver 300 ports, such7     as printers, host systems, or other serial devices.   H     Telnet character and binary profiles are supported for Internet ses-E     sions. Telnet options supported include: status (RFC 859), end of E     record (RFC 885), remote flow control (RFC 1080), echo (RFC 857), G     timing mark (RFC 860), binary (RFC 856), and suppress go ahead (RFC 	     858).   D     Telnet Remote Console allows a user to establish a remote TelnetE     connection to the management port on the terminal server and man- E     age the server as if locally attached. The Telnet listener 23 can E     now be assigned to any terminal server port as well as the remote F     console. Any Telnet listener (23, 2001-2016) can be assigned to be     the remote console.   D  o  Internet Domain Name System (DNS) Support-The Domain Name SystemF     provides the translation from system name to Internet address. TheE     DECserver 300 will interface to user programs and send queries to D     domain name servers for translating domain names to Internet ad-F     dresses, and Internet addresses to domain names. (RFC's 1034,1035)    o  Subnet Addressing (RFC 950)   G  o  Simple Network Management Protocol (SNMP)-The SNMP agent allows the E     DECserver 300 to be managed by an SNMP network management system. E     Retrieving information from the terminal server is possible using F     the SNMP GET and GETNEXT requests. The SNMP SET operation is fullyE     supported providing the ability to modify DECserver parameters as D     well as create and delete applicable table entries. The terminalF     server can send unsolicited event alarms to specified SNMP manage-F     ment stations via the SNMP TRAP message. Terminal server variablesD     accessible via SNMP (RFC 1157) are defined by the Internet docu-D     ments: MIB II (RFC 1213), RS232-Like MIB (RFC 1317), the Charac-     ter MIB (RFC 1316).         #                                   4        G  o  Serial Line Internet Protocol (SLIP)-A host computer which supports E     SLIP can use the DECserver 300 serial port as its network connec- D     tion. This gives IP end nodes which have no Ethernet controller,F     access to the network and to other serial line attached TCP/IP endF     nodes. Any IP application can then be run over the SLIP link. (RFC	     1055)   K  The DECserver 300 also implements and supports the Terminal Device/Session D  Management Protocol (TD/SMP) to manage multiple sessions at the de-G  vice level. The DECserver 300 provides the ability to communicate with E  devices which also implement this protocol and assist in the manage- G  ment of multiple sessions for these devices. By implementing this pro- H  tocol, the DECserver 300 can permit attached devices to maintain screenF  and keyboard context for multiple LAT and/or Telnet sessions, as wellG  as allow these devices to run multiple LAT and/or Telnet sessions con-   currently.   D  The DECserver 300 implements the ODL (On Demand Loading) font load-F  ing protocol which allows Asian terminals that implement the ODL pro-F  tocol to communicate with a VMS host via a terminal server. The AsianH  terminals will be able to request font definitions from a VMS host whenE  connected to a DECserver 300. This feature is supported only for LAT 
  connections.   D  Software that runs on the DECserver 300 is downline loaded over theE  network from a Phase IV or V DECnet load host. Terminal access using F  the DECserver 300 does not require DECnet running in the same serviceE  node; LAT uses the Ethernet addressing mechanism to transport termi-   nal messages.  G  Features such as login load balancing, multiple terminal sessions, au- F  tomatic failover, and remote printer support can lead to greater user  productivity.  D  For wide area network communications, terminal users can connect toE  remote hosts via Telnet through a TCP/IP router or gateway. In addi- F  tion, terminal users can connect to a local service node running DEC-F  net, where they can "SET HOST" to a remote system via the DECnet net-E  work terminal protocol. If this system has the requisite X.25 or SNA   #                                   5        D  3270 access routines, a terminal user could communicate to a remoteD  SNA or X.25 host through the appropriate gateway and this interven-D  ing host. A DECserver 300 terminal user cannot communicate directlyG  to remote hosts through DECnet Routers or X.25/SNA Gateways. Wide area D  network traffic will not provide the same high level of performanceF  as local terminal connections, due to the additional DECnet or Inter-  net protocol overhead.   	  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-G  server 300 users. Services and nodes are identified by name. Users al- G  ways connect to services, not to nodes, although often one of the ser- "  vice names will be the node name.  D  In a VAXcluster environment, the DECserver 300 sees each VAXclusterH  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         #                                   6        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,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  I  The DECserver 300 allows each user to establish and maintain up to eight G  sessions to one or more service nodes, up to a maximum of 128 per DEC- G  server 300. 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 G  may impose limits on the number of LAT or Telnet sessions which a host   will support.    Multiple Session Management  H  The DECserver 300 server allows direct communication with devices whichD  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 which the DECserver 300 provides. By D  implementing the ability to directly communicate with this protocolE  to the attached device, the DECserver 300 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           #                                   7        H  If a terminal user requests a connection to a server, and the requestedF  service is currently in use, the terminal server user may opt to haveE  the connection requested queued to the remote service. If the user's F  port has been appropriately configured, this feature happens automat-G  ically whenever a connection fails for this reason. The connection re- I  quest is queued at the service node end and is processed first-in/first- G  out until such time as the user's connection request can be completed. J  This 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   only for LAT connections.     Command Line Recall and Editing  E  The DECserver 300 server supports multiple command line entry recall 
  and editing.     Welcome Identification   F  The DECserver 300 server standard welcome banner, which includes ter-E  minal server type, version number, internal base-level, and protocol F  version number, is issued whenever a user successfully logs in to theE  server. The server will also print a server manager settable identi- E  fication string. This can be useful for automatic server identifica- G  tion, or for small daily messages used for communication with the ter-   minal server users.    Local Mode and Service Mode  D  For the most part, the environment provided by the DECserver 300 isG  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 connectionH  establishment, the user interacts directly with the DECserver 300. When3  operating in this mode, the user is in Local Mode.   G  In Local Mode, the terminal input is interpreted directly by DECserver /  300 as commands to be performed by the server.     #                                   8        H  Additional commands and displays to support the features available withE  the TD/SMP protocol are usable in Local Mode. These commands will beiE  used to enable or disable server recognition of the TD/SMP commands._  E  Local Mode has three different levels of privilege: privileged, non-cH  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.hF  Access to this mode is password protected. Nonprivileged commands al-E  low terminal users to control their service sessions, set the termi-eE  nal characteristics, and show server information. The Server ManageraF  can set the server to secure mode on a per-terminal basis, which fur-F  ther limits the commands users can enter to commands directly related  to the user's own terminal.  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- E  ileged status. The Server Manager sets a terminal to this status us- D  ing a command which requires a password. This privileged status al-D  lows the Server Manager to enter commands not normally available toF  server users. These commands set server characteristics, provide con-D  trol over server port usage, and provide the ability to control the2  user's access to the server and network services.  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-E  vice Mode. The <BREAK> key may also be used for this function. OtheruE  exceptions, called the forward and backward switch characters, allowCD  the user to switch between sessions without the need to enter localG  mode. The switch characters are disabled by default but may be enabledaD  by command. Both CTRL/S and CTRL/Q are normally interpreted locally9  but flow control using these characters can be disabled.     Autoconnection   E  Autoconnection is a function that automatically connects a user ter- D  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.  #                                   9  a  d  D  If a dedicated service is specified, the DECserver 300 will attemptE  to connect to that service when a character is typed on the terminalnD  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 messagesaE  are available to the terminal user. Ports with dedicated service can D  be automatically logged out of the server when the user logs out of  the service node.  D  If a preferred service is specified, the DECserver 300 will attemptE  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.i    Automatic Protocol Selectione  H  It is possible to automatically connect to an Internet host or LAT ser-E  vice without explicitly identifying the connection as LAT or Telnet.nJ  If the port is configured with a value for the default protocol as "ANY,"E  the server will attempt a LAT connection first to the name specifiedaF  in the LAT service field. If the service is not available or unknown,E  the terminal server will then automatically attempt a Telnet connec- 0  tion to Internet host specified in the command.    Automatic Session Failoverr  E  If a service is available on two or more service nodes and a connec-aE  tion to a service fails, the server will attempt to connect the userrE  to another service node offering the same service. The user does not H  have to be connected to that service node. Furthermore, the user's con-D  text at the time of failure is not automatically restored and loginG  to the new service is required. This feature is supported only for LATs
  connections.t    Groupsi          #                                  10r s  i  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-sD  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 byE  disabling some of the authorized groups using a non-privileged grouprF  command. The user-settable group codes are a subset of the authorized  groups.  G  Groups provide a restrictive view of the network. This restricted viewhF  is mainly for user convenience. Groups apply only to LAT connections.  	  Securityd  E  The DECserver 300 provides functions which enhance security featuresaH  already available in the service nodes. DECserver 300 security includesE  the ability to lock a terminal's keyboard from other users, optionalyE  login protection, and nonprivileged local mode of operation as a de-t  fault.l  D  A user may lock the terminal using a lock password. This allows theE  user to leave sessions running at the terminal without fear of secu-tD  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 may 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-line basis by the server man-G  ager. If enabled, the terminal user must enter a login password to ac-   cess server functions.o      #                                  11c n  l  D  DECserver 300 users normally have access to the nonprivileged localD  mode. In this mode, users may only issue commands that effect theirF  own terminal environment. The server has a privileged mode for server/  manager's use. The mode is password protected.C    Online HELP Facility   F  A full online reference HELP facility is available. The server's HELPE  command provides information on the correct syntax and details aboutlD  each command. In addition, a tutorial HELP feature allows new usersF  to quickly learn the basics of DECserver 300 operation. Tutorial HELP-  may be entered upon logging into the server.o    Directory Service  D  Any DECserver 300 user can obtain a directory of services availableG  to that user with a SHOW SERVICES command. Services for which the user D  is not authorized will not be displayed. Services apply only to LAT
  connections.a    Permanent Characteristics  E  The DECserver 300 maintains permanent characteristics in nonvolatile2D  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 canF  be reset to factory defaults by pressing the software reset button on4  the hardware unit while plugging in the power cord.  #  Port Characteristics Configuration   E  Characteristics governing the operation of an individual port can be I  displayed by a nonprivileged terminal user interactively from the user's G  terminal. Many of the characteristics may be set by the user, but cer- J  tain characteristics are privileged and may only be changed by the Server	  Manager.d  E  Port parameters that can be set and displayed include speed, charac-nD  ter size, group codes, parity, terminal type, access, autobaud, de-)  fault protocol, and password protection.m  #                                  12v    r    Port Access  F  A port on a DECserver 300 may be configured in different ways depend-G  ing on the device attached to the port and its intended use. DECservertF  300 uses MMJs (Modified Modular Jacks) as the physical interface. TheG  DECserver 300 utilizes EIA 423-A electrical interface standard for lo- F  cal connections, which is compatible with the EIA 232-D interface andF  supports sixteen asynchronous devices operating at speeds up to 19.2KD  bps with DTR/DSR (Data Terminal Ready/Data Terminal Set Ready) sig-  naling.  F  Port access is the characteristic which determines how a port may ac-<  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.v  I  o  Access Remote - Designed for application-driven devices such as asyn-cD     chronous printers which are allocated by a service node process.E     This allows the implementation of certain shared printers by mul-t     tiple service nodes.  E  o  Access Dynamic - Designed for devices (such as personal computersuG     or printers with keyboards) which require both Local and Remote ac-n	     cess.A  E  o  Access None - Designed to allow the server manager to disable thee     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-nF  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-eG  ronment of their node. The server can optionally queue remote connectsd    #                                  13n m  a  F  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.d  F  Improved printer sharing allows a printer port on the terminal server=  to be shared between LAT users and ULTRIX or UNIX lpr users.o    Terminal Operationo  E  The DECserver 300 software supports the simultaneous operation of upTD  to sixteen asynchronous devices at speeds from 75 bps to 19.2K bps.  The software also supports:    o  Data leads only support     o  DSR logout    o  Signal check    o  Signal control    o  DSR/DTR flow control    o  XON/XOFF flow controls  9  o  Split speed (transmit and receive) terminal operations  (  o  Block Mode transfers up to 512 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/SMPo    Server Management  E  Several facilities exist for managing and troubleshooting server op-cG  eration. The Server Manager in privileged mode can set up server iden-oF  tification information, change port characteristics, or fine tune theD  operating characteristics of the server. Troubleshooting facilities  #                                  14t    m  G  include diagnostic tests, a remote console feature, and online statis-t  tics.  I  A privileged user can diagnose Ethernet communications problems by loop- G  ing messages to an Ethernet host and through the Ethernet hardware in-eD  terface at the server. To diagnose terminal problems, users can ex-G  ecute a command to transmit test data to their terminal, or the Serverd,  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- G  ture is supported only by DECserver 300 service nodes; VAX/VMS servicei7  nodes do not support this service loopback capability.r  E  The server maintains a variety of statistics and counters. These in-tI  clude the following: Ethernet data link statistics, LAT protocol statis- D  tics, and port error statistics. This data can be displayed and ze-G  roed by the Server Manager. Server parameters that can be modified andiD  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.t    Remote Server Managementa  G  The DECserver 300 implements the console carrier feature which enablesiH  access to the DECserver 300 local mode from a Phase IV or V DECnet hostD  on the same LAN. With the exception of remote console port configu-F  ration, the entire local mode user interface is accessible to the re-D  mote console carrier user. This includes the privileged commands ifE  the user knows the server's privileged password. This capability al-w@  lows centralized server management and remote server diagnosis.  E  The Telnet Remote Console feature is also available as stated above.i  #                                  15l    s    Communications   D  DECserver 300 software is designed to run on DECserver 300 hardwareD  exclusively, which includes an Ethernet interface for connection to  an Ethernet transceiver cable.s  E  The DECserver 300 hardware has sixteen Modified Modular Jacks (MMJs)nF  integral to the box. Each port can be individually configured in var-  ious modes:    o  Data leads onlyt    o  Signal control  F  o  Data leads with DSR logout (if a terminal is powered down the ses-'     sion is automatically disconnected)   F  o  Data leads with signal check (checks signal status before and dur-     ing a session)    o  DSR/DTR flow control    DECserver 300 Operation  D  The DECserver 300 ROM-based firmware provides the necessary mainte-F  nance operation protocols for downline loading DECserver 300 softwareD  from a Phase IV or V DECnet load host over the Ethernet into serverG  memory. All self-test diagnostics are in DECserver 300 ROM and are ex-tF  ecuted on power-up prior to downline loading the server. In the eventF  of a bugcheck caused by a fatal error, the unit will normally attemptG  to upline dump server memory to a DECnet Phase IV or V load host. Fol-iF  lowing this, the unit will automatically initialize itself and invoke  a downline load.T  ,  DECserver 300 Configuration and Performance  J  The process of configuring the DECserver 300 is based primarily on trade-E  offs of cost and performance within the realm of satisfying user ap-sG  plication requirements. Network applications will range from low-speedlD  /low-cost to those of relatively high performance (e.g., connectingH  high-speed local terminals to local hosts within a local area network).  #                                  16, i  i  E  The performance of a given server is a function of the expected net-dF  work traffic, the load on hosts to which terminals are connected, andE  resultant processing pursuant to the dedicated function of the unit.l-  Thus performance depends on several factors:l    o  Number of terminalsi  @  o  Number of host systems with active connections to the server    o  Terminal speedsr    o  Terminal user applications  #  o  Number and size of host buffersi    o  Terminal workloadE  J  The DECserver 300 can sustain an aggregate character throughput of 30,720F  characters per second. This is equivalent to running sixteen ports at  19,200 bps.  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-I  ysis which 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 300 Usage  F  While terminal connections using the DECserver 300 have been designedH  to simulate direct terminal connections as much as possible, a few dif-E  ferences necessarily exist because of the nature of the product. Un-iD  der most circumstances, these differences are not noticed by termi-F  nal users or service node application programs. However, applicationsD  which are directly dependent on the following functions may not op-#  erate as with a direct connection:   F  o  Applications that depend on reading or setting the terminal speed,E     character size, and parity by manipulating system data structuresr  E  o  Applications that depend on an extremely fast response time (typ-c'     ically less than 200 ms) to operatet  #                                  17.    e  F  o  Applications that utilize an alternate terminal driver in the ser-
     vice noder  F  o  Applications that expect incoming connections to have fixed device	     namesr  6  The DECserver 300 does not support the use of modems.    HARDWARE REQUIREMENTS    For VAX Systems:-  E  Processors and/or hardware configurations as specified in the Systems9  Support Addendum (SSA 25.J1.04-x included in this file).v    For MS-DOS Systems:  (  Processors supported (Load Host System)  >  Personal Computer: DECstation, DECpc, or Industry Standard PC    SOFTWARE REQUIREMENTS    For VAX Systems:d    VMS Operating System     DECnet-VAXi    For MS-DOS Systems:    MS-DOS Operating System    PATHWORKS for DOS  F  *  Refer to the System Support Addendum for availability and required@     versions of prerequisite/optional software (SSA 25.J1.04-x).  D  Refer to the following Software Product Description for information*  on other supported DECserver 300 systems:(  DECserver 300 for ULTRIX (SPD 25.J2.xx)  #                                  18     m    ORDERING INFORMATION/    Software Licenses: QL-VTUA9-AA     Software Media: QA-VTUAA-H*  $  Software Documentation: QA-VTUAA-GZ  '  Software Product Services: QT-VTUAA-**t  G  *  Denotes variant fields. For additional information on available li-iE     censes, services, and media, refer to the appropriate price book.t    SOFTWARE LICENSINGc  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.   I  The DECserver 300 software license applies to the DECserver 300 on whichyD  the server software runs, not to service host node CPUs in the net-  work.  E  This product does not provide support for the VMS License ManagementnD  Facility. A Product Authorization Key (PAK) is not required for in-2  stallation 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.                  #                                  19c o  a    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 Warrantye  Addendum of this SPD.  C  [R] AT and IBM are registered trademarks of International Businessh     Machines Corporation.t  ?  [R] MS-DOS is a registered trademark of Microsoft Corporation.   @  [R] UNIX is a registered trademark of UNIX System Laboratories,     Inc.  A  [TM]The DIGITAL Logo, CI, DEC, DECconnect, DECmate, DECnet, DEC- @     server, DECstation, DELNI, DEMPR, Digital, LA, LAT, LXY, Mi-?     croVAX, OpenVMS, RX, ThinWire, TK, ULTRIX, VAX, VAXcluster,tC     VAXft, VAXmate, VAXserver, VAXstation, and VT100 are trademarkse%     of Digital Equipment Corporation.c  ;   1997 Digital Equipment Corporation. All rights reserved.l                                      #                                  20s  i    Systemr  Support	  Addendumb  D  ___________________________________________________________________D  ___________________________________________________________________  H  PRODUCT NAME:  DECserver 300 for VMS[*] and MS-DOS[R], Version 2.2c SSA  25.J1.04-Ap    HARDWARE REQUIREMENTS    Processors Supported               VAXft Model 110,e            VAXft Model 310,s            VAXft Model 410,o            VAXft Model 610,             VAXft Model 612    VAX:      VAX 4000 Model 100,            VAX 4000 Model 200,            VAX 4000 Model 300,            VAX 4000 Model 400,            VAX 4000 Model 500,            VAX 4000 Model 600m  %            VAX 6000 Model 200 Series,p%            VAX 6000 Model 300 Series,a%            VAX 6000 Model 400 Series,z%            VAX 6000 Model 500 Series,t$            VAX 6000 Model 600 Series        ____________________t  C  The   terms OpenVMS and VMS refer to the OpenVMS operating system.y    D                                DIGITAL                   August 1997  D                                                          AE-NE48G-TE o  .    (            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 8840a              VAX 9000 Model 110,            VAX 9000 Model 210,%            VAX 9000 Model 300 Series,i$            VAX 9000 Model 400 Series  "            VAX-11/730, VAX-11/750,!            VAX-11/780, VAX-11/785   &  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 3900   +  VAXstation:VAXstation II, VAXstation 2000,s$            VAXstation 3100 Model 30,$            VAXstation 3100 Model 38,$            VAXstation 3100 Model 40,$            VAXstation 3100 Model 48,$            VAXstation 3100 Model 76,,            VAXstation 3200, VAXstation 3500,+            VAXstation 3520, VAXstation 3540   $            VAXstation 4000 Model 60,        #                                   2c    d    $            VAXstation 4000 Model 90,            VAXstation 4000 VLC  (  VAXserver: VAXserver 3100 Model 10/10E,(            VAXservice 3100 Model 20/20E,:            VAXserver 3300, VAXserver 3400, VAXserver 3500,:            VAXserver 3600, VAXserver 3602, VAXserver 3800,            VAXserver 3900n  $            VAXserver 4000 Model 200,$            VAXserver 4000 Model 300,#            VAXserver 4000 Model 500u  $            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 630C    Personal  DECstation Series,a  Comput-   DECpc Series, or   ers:      Industry Standard PCh    Processors Not Supported   +  MicroVAX I, VAXstation I, VAXstation 8000,r  VAX-11/725, VAX-11/782-  G  The DECserver 300 software runs on any of the following packaged hard-   ware options:      #                                   3t       	  DSRVF-**   H  *  Denotes variant fields. For additional information on available mod--     els, refer to the appropriate price book.o  F  The following DECconnect cables and accessories are available for the  DECserver 300:m  +  BC16E-10  DECconnect office cable with MMPs  /25/50b  ,  H8572     Coupler/Extender, 6-pin MMJ cable  3  H8571-A   Passive adapter, 25-pin DSUB male to MMJr  B  H8571-C   Passive adapter, 25-pin DSUB female to MMJ (unfiltered)  @  H8571-D   Passive adapter, 25-pin DSUB female to MMJ (filtered)  2  H8571-B   Passive adapter, 9-pin DSUB male to MMJ    H8220     Pack of 50 MMJs    H3103     Loopback, 6-pin MMJ  >  BC23P-10  Cable assembly for DECconnect SER and OCC cabs. Un-            shieldedg  C  BC23R-10  Cable assembly for DECconnect SER and OCC cabs. Shielded3  G  The DECserver hardware requires both a transceiver drop cable and Eth-eE  ernet connection, H4005 or DELNI, to connect to a Thickwire EthernetlE  physical channel or a DEMPR/DESPR to connect from a ThinWire segmentpE  to Thickwire Ethernet. The DECserver 300 supports both Thickwire ands*  ThinWire connections integral to the box.    OPTIONAL HARDWARE    Terminals Supported  G  The DECserver 300 software supports the following Digital terminal de-e  vices that have keyboards:      o  LA12, LA34, LA35, LA36, LA38    o  All VTxxx terminalse  #                                   4y a     #  Supported terminal parameters are:e  -  o  Character size: 7 or 8 bits per characterc    o  Parity: Even, Odd, or None  G  The automatic line speed detection (Autobaud) feature is supported foreE  either 7-bit characters with even parity or 8-bit characters with not  parity.  D  The DECserver 300 software also supports Digital Asian terminal de-D  vice variants when accessed from VMS/Hanzi systems. Please refer toE  the VMS/Hanzi Software Product Description for a complete listing ofc  supported devices.t  D  The DECserver 300 software also supports Digital Asian terminal de-D  vice variants when accessed from VMS/Japanese systems. Please referF  to the VMS/Japanese Software Product Description for a complete list-  ing of supported devices.  D  The DECserver 300 software also supports the following Digital Per-F  sonal Computers (PCs) in both terminal emulation mode and file trans-
  fer mode:    o  Professional 325, 350, 380  !  o  Rainbow 100A, 100B, 100+, 190e    o  DECmate II    o  DECmate IIId    o  VAXmatee    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]mF  PC, IBM PC/XT, and IBM PC/AT[R] characteristics may operate with this	  product.     Printers Supportedn  #                                   5s p  t  G  The DECserver 300 software supports the following Digital asynchronouso)  printers when accessed from VMS systems:   ;  o  All LJ, LA, LQP, LXY, LN0, LG, and DTC printing deviceso  F  The DECserver 300 software also supports Digital Asian printer deviceG  variants when accessed from VMS/Hanzi systems. Please refer to the VMS H  /Hanzi Software Product Description for a complete listing of supported	  devices.o  F  The DECserver 300 software also supports Digital Asian printer deviceF  variants when accessed from VMS/Japanese systems. Please refer to theD  VMS/Japanese Software Product Description for a complete listing of  supported devices.e    Modems Supportedt  6  The DECserver 300 does not support the use of modems.  2  Disk Space Requirements (Block Cluster Size = 1):  (  Disk space required for    3,050 blocks  installation:(                             (1.5 Mbytes)  (  Disk space required for    2,750 blocks  use (permanent):e(                             (1.4 Mbytes)  H  These counts refer to the disk space required on the downline load hostF  system disk. The sizes are approximate; actual sizes may vary depend-F  ing on the user's system environment, configuration, and software op-  tions.s              #                                   6n c  u    CLUSTER ENVIRONMENT  D  This layered product is fully supported when installed on any validG  and licensed VAXcluster* configuration without restrictions. The HARD-eG  WARE REQUIREMENTS sections of this product's Software Product Descrip-eF  tion and System Support Addendum detail and special hardware required  by this product.v  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.c    SOFTWARE REQUIREMENTS    For VAX Systems:   !  VMS Operating System V5.0 - V5.5y  "  DECnet-VAX (Phase IV) V5.0 - V5.5    VMS Tailoring:   F  For VMS V5.x systems, the following VMS classes are required for full'  functionality of this layered product:s    o  VMS Required Saveset    o  Network Supports  
  o  Utilitiesu  D  For more information on VMS classes and tailoring, refer to the VMS=  Operating System Software Product Description (SPD 25.01.xx)d    For MS-DOS[R] Systems:a  ?  For each MS-DOS system acting as a load host or dump receiver:u  0  MS-DOS Operating System V3.1, V3.3, V4.01, V5.0    PATHWORKS for DOS V4.1.  #                                   7a d       OPTIONAL SOFTWARE    Terminal Server Manager V1.6e    GROWTH CONSIDERATIONS  E  The minimum hardware/software requirements for any future version ofrD  this product may be different from the requirements for the current	  version.C    DISTRIBUTION MEDIAh    For VAX Systems:t  .  TK50 Streaming Tape, 9-track 1600 BPI Magtape    For MS-DOS Systems:    RX31 and RX24    ORDERING INFORMATIONt    Software License: QL-VTUA9-AA  Software Media: QA-VTUAA-H*$  Software Documentation: QA-VTUAA-GZ'  Software Product Services: QT-VTUAA-**r  G  *  Denotes variant fields. For additional information on available li-iE     censes, services, and media, refer to the appropriate price book.m  F  The above information is valid at time of release. Please contact you:  local Digital office for the most up-to-date information.  C  [R] AT and IBM are registered trademarks of International Businessd     Machines Corporation.   ?  [R] MS-DOS is a registered trademark of Microsoft Corporation.r      #                                   8b s       @  [R] UNIX is a registered trademark of UNIX System Laboratories,     Inc.  A  [TM]The DIGITAL Logo, CI, DEC, DECconnect, DECmate, DECnet, DEC- @     server, DECstation, DELNI, DEMPR, Digital, LA, LAT, LXY, Mi-?     croVAX, OpenVMS, RX, ThinWire, TK, ULTRIX, VAX, VAXcluster, C     VAXft, VAXmate, VAXserver, VAXstation, and VT100 are trademarkse%     of Digital Equipment Corporation.-  ;   1997 Digital Equipment Corporation. All rights reserved.3                                                          #                                   9e                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                          