     	  Software   Product  Description  D  ___________________________________________________________________  D  PRODUCT NAME:  DECserver 700 for VMS[*], ULTRIX,       SPD 38.73.044                 UNIX[R], and MS-DOS[R], Version 1.1c    DESCRIPTION  E  DECserver 700 for VMS, ULTRIX, UNIX, and MS-DOS, Version 1.1c is the $  software release for DECserver 700.  D  The DECserver 700 software provides concurrent Local Area TransportE  (LAT) and Telnet TCP/IP protocol support from a DECserver 700 commu- E  nications server to enable connectivity to host systems that utilize F  LAT or TCP/IP protocols. The TCP/IP protocol suite is used to connectD  to UNIX host systems and other host systems that support the TCP/IP  protocol suite.  F  The DECserver 700 Communications Server is an Ethernet CommunicationsG  Server for Ethernet Local Area Networks (LANs). The DECserver 700 pro- J  vides a convenient method to logically connect up to sixteen asynchronousD  terminals to one or more service nodes (hosts) on an Ethernet. OnceG  the terminal is connected, a user can utilize application programs and H  utilities as though the terminal is directly connected to a host. Thus,D  it may be possible to utilize the DECserver 700 to connect all ter-G  minals to service nodes in place of traditional interfaces, except for   host console terminals.  G  The DECserver 700 is available in two models, the DECserver 700-16 and H  the DECserver 700-08. The DECserver 700-16 provides attachment for six-G  teen asynchronous devices via MJ8 connectors (also referred to as RJ45 D  connectors). The DECserver 700-16 conforms to the DEC423 electricalD  interface standard for local connections, and supports two user se-F  lectable modem signaling options: CTS/RTS/DSR/DTR or RI/DCD/DSRS/DTR.G  DEC423 is a superset of EIA-423-A/CCITT V1.0 with some exceptions, and     ____________________   C  The   terms VMS and OpenVMS refer to the OpenVMS Operating System.   D                                DIGITAL                   August 1997  D                                                          AE-PMSFE-TE       F  supports longer cable runs and higher signaling speeds. The DECserverH  700-08 provides attachment for eight asynchronous devices via DB25 con-E  nectors. Both DECserver 700 models support asynchronous devices with :  interfaces that conform to EIA/TIA-232-3/CCITT V.24/V.28.  D  The DECserver 700 supports connections to wide area networks (WANs)E  via modems. The DECserver 700 also allows for host-initiated connec- E  tions to serial printers. A serial printer can be shared between LAT E  print requests and Telnet requests. Telnet requests cannot be queued F  on the server. A print symbiont on service nodes can initiate connec-D  tions to serial printers connected to DECserver 700 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 may be queued FIFO at the server.   @  Port-to-port connections on the same server are also supported.  E  In addition, the DECserver 700 provides IP end-node routing via SLIP E  (Serial Line Internet Protocol). Up to 16 TCP/IP systems can be con- G  nected to the serial ports of the DECserver 700. These systems can run E  IP applications (such as Telnet, FTP[R], X-Windows, etc.) on the se- E  rial line and communicate with other TCP/IP services on the network.   E  The DECserver 700 supports reverse LAT and Telnet Listener. Both fa- D  cilities are provided to enable a network node, such as a host sys-D  tem, to connect to a DECserver port. This facility could be used toE  support printers, a modem pool for outgoing calls, and connection to I  the asynchronous ports of a system without other network access of other 6  types of devices that have an asynchronous interface.  H  Both reverse LAT and Telnet Listener provide the ability to group phys-F  ical ports into logical groupings. For example, a group of ports con-J  nected to the asynchronous interfaces of the same system could be groupedD  so a connect request would be routed to any of the currently unusedF  ports. A logical grouping can contain any number of ports from one to  all the ports on the server.         #                                   2        E  The DECserver 700 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. Under most I/O loading conditions, a significant performanceE  gain may be realized by using the DECserver 700 versus direct termi- F  nal connections via traditional asynchronous backplane communications  interfaces.  E  The DECserver 700 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:   L  o  Transmission Control Protocol (TCP) is the Internet-standard, transport-E     level protocol that provides the reliable, end-to-end full duplex F     stream service that supports many application protocols (RFC 793).  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-I     fines the Internet datagram as the unit of information that is passed E     across the Internet, and provides the universal addressing scheme J     for hosts and gateways for Internet connectionless, best-effort packetF     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.     #                                   3        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 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).  <     Both Telnet client and server capabilities are provided:  F     -  Telnet client provides the ability to connect to any remote TCPD        port at an Internet address on a local area network or a wideF        area network. Telnet client allows the user to specify a remote>        computer by Internet address as well as by Domain name.  G     -  Telnet server provides the ability to accept connection requests G        from Internet hosts on a LAN or WAN to DECserver 700 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 ListenerD        23 can now be assigned to any terminal server port as well asF        the remote console. Any Telnet Listener (23, 2001-20016) can be)        assigned to be the remote console.         #                                   4        D  o  Internet Domain Name System (DNS) Support - The Domain Name Sys-F     tem provides the translation from system name to Internet address.F     The DECserver 700 will interface to user programs and send queriesG     to 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).  F  o  Simple Network Management Protocol (SNMP) -- The SNMP agent allowsF     the DECserver 700 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 operationE     is fully supported, providing the ability to modify DECserver pa- G     rameters as well as create and delete applicable table entries. The G     terminal server can send unsolicited event alarms to specified SNMP H     management stations via the SNMP TRAP message. Terminal server vari-G     ables accessible via SNMP (RFC 1157), not a MIB, are defined by the E     Internet documents: MIB II (RFC 1213), RS232-like MIB (RFC 1317), !     the Character MIB (RFC 1316).   D  o  Serial Line Internet Protocol (SLIP) - A host computer that sup-H     ports SLIP can use the DECserver 700 serial port as its 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 endE     nodes. Any IP application can then be run over the SLIP link (RFC 
     1055).  D  o  Bootp (RFC 951 and RFC 1084) and tftp (RFC 783) together provideF     a method for downloading the DECserver 700 from any host that sup-I     ports those protocols. Bootp provides a mechanism by which the server G     can identify a host from which it can request a download. Tftp pro- F     vides the data transfer facility used to copy to software from the     load host to the server.  K  The DECserver 700 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 700 provides the ability to communicate with F  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 700 can permit attached devices to maintain screen  #                                   5        F  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.   E  The DECserver 700-8 will support block mode transfers of up to 2,048 E  bytes, and the DECserver 700-16 will support block mode transfers of J  up to 512 bytes, or with a memory (SIM) upgrade to 2 megabytes (or more).J  The DECserver 700-16 will support block mode transfers up to 2,048 bytes.  D  The DECserver 700 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 700. This feature is supported only for LAT 
  connections.   D  Software that runs on the DECserver 700 is downline loaded over theE  network from a Phase IV or V DECnet load host. Software that runs on G  DECserver 700 can also be downloaded from any system that supports the G  Bootp and tftp protocols. Terminal access using the DECserver 700 does G  not require DECnet running in the same service node; LAT uses the Eth- ;  ernet addressing mechanism to transport terminal 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 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 700 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 performanceE  as local terminal connections due to the additional DECnet or Inter-   net protocol overhead.   #                                   6          	  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- D  minal appear physically connected to the service node, and the ter-H  minal user can use standard system utilities and applications supportedG  by that node. Each terminal connected to the server can connect to the D  same or a different service node on the Ethernet. Furthermore, sev-G  eral servers can be used to connect many terminals to one or more ser-   vice nodes.  E  A service node can have one or more LAT services that are offered to F  DECserver 700 users. Services and nodes are identified by name. UsersI  always connect to services, not to nodes; often one of the service names 9  will be the node name. Users of Telnet connect to nodes.   E  In a VAXcluster environment, the DECserver 700 users of LAT see each E  VAXcluster on the Ethernet as a collection of service nodes offering H  a common service. Each cluster node may also offer a service whose nameG  is equivalent to its node name. In this case, a terminal user can con- G  nect either to the cluster service or a service associated with a par- E  ticular cluster node. To connect via Telnet, a user must specify the +  specific cluster node to which to connect.     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-F  vice nodes do not have to be configured in a cluster for load balanc-F  ing to be used. Service nodes with the same names may be running dif-G  ferent operating systems. Using the load balancing process, the server       #                                   7        F  connects to the node with the highest rating for the service desired.D  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 700 allows each user to establish and maintain up to eight E  sessions to one or more service nodes. Only one session per user can E  be active at a time. Through simple switching commands, the user can F  access the different sessions without repeating a login dialogue eachD  time. Some operating systems may impose limits on the number of LAT-  or Telnet sessions that a host will support.       Multiple Session Management  G  The DECserver 700 server allows direct communication with devices that D  support the TD/SMP protocol. This protocol provides the ability forD  the attached device to maintain screen and keyboard context for theD  multiple LAT or Telnet sessions that the DECserver 700 provides. ByD  implementing the ability to directly communicate with this protocolE  to the attached device, the DECserver 700 can now assist in the man-pD  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 Queueso  G  If a terminal user requests a connection to a server and the requested G  service is currently in use, the terminal server users may opt to havevE  the requested connection queued to the remote service. If the user'sl            #                                   8c u     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- H  out (FIFO) until such time as the user's connection request can be com-D  pleted. This feature assists in the fair management of limited net-F  work resources. Once queued for connection, the user also has the op-E  tion to cancel the queue entry and proceed with other sessions. Thist/  feature is supported only for LAT connections.c     Command Line Recall and Editing  E  The DECserver 700 server supports multiple command line entry recall,
  and editing.s      Welcome Identificationr  F  The DECserver 700 server-standard welcome banner, which includes ter-E  minal server type, version number, internal base level, and protocol0F  version number, is issued whenever a user successfully logs in to theE  server. The server will also print a Server-Manager-settable identi-oE  fication string. This can be useful for automatic server identifica-)F  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 700 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 700. When3  operating in this mode, the user is in Local Mode.r  G  In Local Mode, the terminal input is interpreted directly by DECservert/  700 as commands to be performed by the server.o        #                                   9r s  h  H  Additional commands and displays to support the features available withE  the TD/SMP protocol are usable in Local Mode. These commands will beWE  used to enable or disable server recognition of the TD/SMP commands.n  E  Local Mode has three different levels of privilege: privileged, non-AH  privileged, and secure. Privileged mode is provided for the Server Man-F  ager to control the environment of the server and the terminal users.F  Access to this mode is password protected. Nonprivileged commands al-F  low the terminal user to control their service sessions, set the ter-F  minal characteristics and show server information. The Server ManagerF  can set the server to secure mode on a per-terminal basis, which fur-F  ther limits the commands users can enter to only those which directly#  relate to the user's own terminal.a  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-J  lows the Server Manager to enter commands not usually available to serverG  users. These commands set server characteristics, provide control over-E  server port usage, and provide the ability to control the user's ac- )  cess to the server and network services.g  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. OthergE  exceptions, called the forward and backward switch characters, allowsD  the user to switch between sessions without the need to enter localG  mode. The switch characters are disabled by default but may be enabled D  by command. Both CTRL/S and CTRL/Q are usually interpreted locally,9  but flow control using these characters can be disabled.i    Autoconnectionr  E  Autoconnection is a function that automatically connects a user ter-oD  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.  #                                  10g       D  If a dedicated service is specified, the DECserver 700 will attemptE  to connect to that service when a character is typed on the terminaleD  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 messagesfE  are available to the terminal user. Ports with dedicated service cantD  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 700 will attemptE  to connect to that service as with the dedicated service mode of op-eD  eration. However, the terminal user can enter local mode and estab-  lish other sessions.(    Automatic Protocol Selection   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.rJ  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 specified F  in the LAT service field. If the service is not available or unknown,E  the terminal server will then automatically attempt a Telnet connec-e4  tion to the Internet host specified in the command.      Automatic Session Failovert  E  If a service is available on two or more service nodes and a connec-eE  tion to a service fails, the server will attempt to connect the usereE  to another service node offering the same service. The user does notoH  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 LAT 
  connections.p      Groups       #                                  11        D  Every terminal and service node in a LAT network is a member of oneD  or more groups specified by a list of numbers from 0 to 255. GroupsD  allow an easy means of subdividing the network into what appears toD  be many smaller networks. A terminal user is only aware of the ser-6  vices that are offered by nodes in the same group(s).  G  The Server Manager can specify the authorized group(s) in which a ter-uD  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.  G  Groups provide a restrictive view of the network. This restricted vieweF  is mainly for user convenience. Groups apply only to LAT connections.  	  Security   D  The DECserver 700 provides functions that enhance security featuresH  already available in the service nodes. DECserver 700 security includesE  the ability to lock a terminal's keyboard from other users, optional E  login protection, and nonprivileged local mode of operation as a de-   fault.a  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-.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 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.  H  Login passwords can be enabled on a per-server basis by the Server Man-G  ager. If enabled, the terminal user must enter a login password to ac-i  cess server functions.s      #                                  12t r  3  I  DECserver 700 users usually have access to the nonprivileged local mode. G  In this mode, users may only issue commands that affect their own ter-eD  minal environment. The server has a privileged mode for Server Man-,  ager's use. The mode is password protected.    Online HELP Facilityt  F  A full online reference HELP facility is available. The server's HELPE  command provides information on the correct syntax and details aboutrD  each command. In addition, a tutorial HELP feature allows new usersF  to quickly learn the basics of DECserver 700 operation. Tutorial HELPK  may be entered upon logging into the server. HELP is also based on whethery2  the user is secure, nonprivileged, or privileged.    Directory Service  E  Any DECserver 700 user can obtain a directory of LAT services avail- G  able to that user with a SHOW SERVICES command. Services for which theaE  user is not authorized will not be displayed. Services apply only to   LAT connections.       Permanent Characteristics  F  The DECserver 700 maintains permanent characteristics in non-volatileD  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 Configurationn              #                                  13s       E  Characteristics governing the operation of an individual port can bepI  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-fJ  tain characteristics are privileged and may only be changed by the Server	  Manager.o  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.t    Port Access  F  A port on a DECserver 700 may be configured in different ways depend-G  ing on the device attached to the port and its intended use. DECserversF  700-16 provides sixteen MJ8 connectors as the physical interface, andH  they conform to the DEC423 electrical interface standard for local con-E  nections, as well as provide two user selectable model signaling op-pE  tions: CTS/RTS/DSR/DTR or RI/DCD/DSRS/DTR. The DECserver 700-08 pro-iF  vides eight DB25 male connectors as the physical interface. Both DEC-D  server 700 models support asynchronous devices with interfaces thatF  conform to EIA/TIA-232-E/CCITT V.24/V.28 and speeds up to 115.2 Kbps.  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. Additional example: dial-in modem.  I  o  Access Remote - Designed for application-driven devices such as asyn-rD     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. Additional example: dial-out modem.  E  o  Access Dynamic - Designed for devices (such as personal computerswG     or printers with keyboards) which require both Local and Remote ac-f5     cess. Additional example: dial-in/dial-out modem.s      #                                  14  m  y  E  o  Access None - Designed to allow the Server Manager to disable thei     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- F  figured on system startup. The particular server port must be config-F  ured for remote access and set up to match the characteristics of the	  printer.v    Terminal Operationn  E  The DECserver 700 software supports the simultaneous operation of upeD  to 16 asynchronous devices at speeds from 75 bps to 115.2 Kbps. The  software also supports:    o  Data leads only supportt  !  o  Modem control (DS700-08 only)t  5  o  Signal control with Signal Select (DS700-16 only)     o  DSR logout    o  Long Break logout     o  Signal check    o  CTS/RTS flow control    o  DSR/DTR flow control    o  XON/XOFF flow controlp  9  o  Split speed (transmit and receive) terminal operationt  +  o  Modem Fallback Features (DS700-08 only)e  F  o  Block Mode transfers up to 2,048 bytes (DS700-08 and DS700-16 with8     memory upgrade to 2 MB or more). (* See note below.)  +  o  Digital personal computer file transfer   "  o  Automatic line speed detection  #                                  15          o  Data transparency mode  :  o  Ability to pass break character and error notification  ?  o  Ability to assist in multiple session management via TD/SMPl  *  o  RI simulation for DTEs that require it  E  *  NOTE: The DECserver 700-8 will support block mode transfers of upeD     to 2,048 bytes with 1 or more Megabytes of memory. The DECserverL     700-16 will support block mode transfer of up to 512 bytes in 1 Megabyte<     or up to 2,048 bytes with 2 or more Megabytes of memory.    Server Management  E  Several facilities exist for managing and troubleshooting server op-mG  eration. The Server Manager in privileged mode can set up server iden-eF  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-m  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-uD  terface at the server. To diagnose terminal problems, users can ex-G  ecute a command to transmit test data to their terminal, or the Servere,  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 LATD  protocol or internally or externally at the service port. This fea-I  ture is supported only by DECserver 700 service nodes; VMS service nodesg1  do not support this service loopback capability.           #                                  16  n  h  E  The server maintains a variety of statistics and counters. These in-iI  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 andtD  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 modifiedhF  and displayed. IP, ICMP, TCP, IP, UDP, DNS, and SNMP protocol statis-  tics can be displayed.     Remote Server Managementg  G  The DECserver 700 implements the console carrier feature which enableswH  access to the DECserver 700 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-e@  lows centralized server management and remote server diagnosis.  E  The Telnet Remote Console feature is also available as stated above.b      Communicationsm  D  DECserver 700 software is designed to run on DECserver 700 hardwareD  exclusively, which includes an Ethernet interface for connection to  an Ethernet transceiver cable.l  E  The DECserver 700-16 hardware has sixteen MJ8 connectors integral tohF  the box. The DECserver 700-08 hardware has eight DB25 male connectorsF  integral to the box. Each port can be individually configured in var-  ious modes:  !  o  Modem Control (DS700-08 only)   5  o  Signal Control with Signal Select (DS700-16 only)f  #                                  17        F  o  Data leads with DSR logout (if a terminal is powered down the ses-'     sion is automatically disconnected)a  F  o  Data leads with signal check (checks signal status before and dur-     ing a session)    o  DSR/DTR flow control    o  CTS/RTS flow control    o  XON/XOFF flow controlc    o  Long Break logout     o  Modem Fallback Feature  *  o  RI simulation for DTEs that require it    DECserver 700 Operation  D  The DECserver 700 ROM-based firmware provides the necessary mainte-F  nance operation protocols for downline loading DECserver 700 softwareD  from a Phase IV or V DECnet load host over the Ethernet into serverH  memory and bootp and HTP to load from a system that supports those pro-D  tocols also. All self-test diagnostics are in DECserver 700 ROM andF  are executed on power-up prior to downline loading the server. In theG  event of a bugcheck caused by a fatal error, the unit will usually at-rH  tempt to upline dump server memory to a DECnet Phase IV or V load host.F  Following this, the unit will automatically initialize itself and in-  voke a downline load.  ,  DECserver 700 Configuration and Performance  E  The performance of a given server is a function of the expected net-cF  work traffic, the load on hosts to which terminals are connected, andE  resultant processing pursuant to the dedicated function of the unit.c-  Thus performance depends on several factors:r    o  Number of terminalsr  @  o  Number of host systems with active connections to the server  #                                  18c d  c    o  Terminal speeds7    o  Terminal user applications  #  o  Number and size of host buffersa    o  Terminal workloadt    o  LAT circuit timerb  F  The DECserver 700-16 can sustain an aggregate character throughput ofG  215,000 characters per second. The DECserver 700-08 can sustain an ag-sF  gregate character throughput of 120,000 characters per second. In or-G  der to achieve a viable configuration, the user and/or a Digital soft-sE  ware specialist should perform a level of application analysis whichfE  addresses the factors above. The actual maximum data throughput can-PH  not be calculated by multiplying the number of lines by the line speed,D  since many factors already discussed in this section may reduce the  actual throughput.o  $  Restrictions on DECserver 700 Usage  F  While terminal connections using the DECserver 700 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-cD  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:t  F  o  Applications that depend on reading or setting the terminal speed,E     character size, and parity by manipulating system data structuresv  E  o  Applications that depend on an extremely fast response time (typ-s'     ically less than 200 ms) to operateo  F  o  Applications that utilize an alternate terminal driver in the ser-
     vice node     #                                  19s    I  F  o  Applications that expect incoming connections to have fixed device	     names     HARDWARE REQUIREMENTS  D  Processor and/or hardware configurations as specified in the System#  Support Addendum (SSA 38.73.03-x).e    SOFTWARE REQUIREMENTS    For VMS Systems:c    o  VMS Operating System    o  DECnet-VAX    For ULTRIX Systems:    o  ULTRIX Operating Systemi    o  MOP     For MS-DOS Systems:    o  MS-DOS Operating Systemi    o  PATHWORKS for DOSe    For UNIX Systems:  F  The following generic operating systems are supported. Note that com-I  plete support cannot be granted on systems where customization has takencD  place. Also, note that some UNIX implementations, not listed below,5  may operate successfully, but no support is implied.n    o  BOOTP/TFTP     One of the following:e       -  SunOS[TM]       -  OSF[R]/1,       -  IBM[R] AIX[R]  #                                  20e n  u        -  SCO[TM] UNIX System V/386       -  HP[R]-UX   F  Some System V[TM] systems, such as HP-UX and SCO, may not support the  upline dump of server memory.  E  Refer to the System Support Addendum (SSA 38.73.03-x) for availabil-i=  ity and required versions of prerequisite/optional software.l    ORDERING INFORMATIONi    Software License: QL-XA5A9-AA  Software Media: QA-XA5A*-H*$  Software Documentation: QA-XA5AA-GZ'  Software Product Services: QT-XA5A*-**e  G  *  Denotes variant fields. For additional information on available li-gE     censes, services, and media, refer to the appropriate price book.h    SOFTWARE LICENSINGt  E  This software is furnished under the licensing provisions of DigitalpD  Equipment Corporation's Standard Terms and Conditions. For more in-E  formation about Digital's licensing terms and policies, contact yourp  local Digital office.  I  The DECserver 700 software license applies to the DECserver 700 on whichgD  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 ManagementoD  Facility. A Product Authorization Key (PAK) is not required for in-2  stallation or use of this version of the product.            #                                  21c    o    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 Warranty   Addendum of this SPD.    A  [R] Domain is a registered trademark of Apollo Computer, Inc., ai*     subsidiary of Hewlett-Packard Company.  ?  [R] FTP is a registered trademark of Schere Laboratories, Inc.s  =  [R] HP is a registered trademark of Hewlett-Packard Company.   @  [R] IBM, AT, and AIX are registered trademarks of International"     Business Machines Corporation.  B  [R] MS and MS-DOS are registered trademarks of Microsoft Corpora-	     tion.   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.z  @  [TM]System V is a trademark of American Telephone and Telegraph     Company.  F  [TM]The DIGITAL Logo, CI, DEC, DECbridge, DECconnect, DEC EtherWORKS,=     DECmate, DECnet, DECserver, DECstation, DECsystem, DELNI,u@     DEMPR, LA, LAT, LXY, MicroVAX, OpenVMS, PATHWORKS, RX, Thin-A     Wire, TK, ULTRIX, VAX, VAXcluster, VAXft, VAXmate, VAXserver, B     VAXstation, VMS, VT, VT100, VT330, VT340, and VT420 are trade-+     marks of Digital Equipment Corporation.   ;   1997 Digital Equipment Corporation. All rights reserved.i  #                                  22r  y    Systemi  Support	  AddendumD  D  ___________________________________________________________________D  ___________________________________________________________________  D  PRODUCT NAME:  DECserver 700 for VMS[*], ULTRIX,     SSA 38.73.03-A4                 UNIX[R], and MS-DOS[R], Version 1.1c    HARDWARE REQUIREMENTS    VMS Processors     VMS 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 600r  %            VAX 6000 Model 200 Series, %            VAX 6000 Model 300 Series, %            VAX 6000 Model 400 Series,p%            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, VAXB            8530, VAX 8550, VAX 8600, VAX 8650, VAX 8700, VAX 8800,1            VAX 8810, VAX 8820, VAX 8830, VAX 8840o    ____________________s  C  The   terms OpenVMS and VMS refer to the OpenVMS operating system.t    C                                DIGITAL                    June 1997   D                                                          AE-PMSGF-TE e  L                VAX 9000 Model 110,            VAX 9000 Model 210,%            VAX 9000 Model 300 Series, $            VAX 9000 Model 400 Series  %            VAX 10000 Model 600 Seriest              VAXft Model 110,E            VAXft Model 310,a            VAXft Model 410,l            VAXft Model 610,i            VAXft Model 612  "            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 3900i  +  VAXstation:VAXstation II, VAXstation 2000,r$            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         #                                   2  s       %            VAXstation 4000, Model 60,a%            VAXstation 4000, Model 90,s            VAXstation 4000 VLC  (  VAXserver: VAXserver 3100 Model 10/10E,'            VAXserver 3100 Model 20/20E, *            VAXserver 3300, VAXserver 3400,*            VAXserver 3500, VAXserver 3600,*            VAXserver 3602, VAXserver 3800,            VAXserver 3900l  $            VAXserver 4000 Model 200,$            VAXserver 4000 Model 300,#            VAXserver 4000 Model 500,  $            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 630T                          #                                   3v s  g    VMS Processors Not Supported:  &  MicroVAX I, VAXstation I, VAX-11/725,  VAX-11/782, VAXstation 8000    ULTRIX Processors Supported    VAX-Based Processors:  %  VAX:      VAX 6000 Model 200 Series, %            VAX 6000 Model 300 Series,h%            VAX 6000 Model 400 Series,r$            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 8840n              VAX 9000 Model 110,            VAX 9000 Model 210,            VAX 9000 Model 300,            VAX 9000 Model 410,            VAX 9000 Model 420y  -            VAX-11/750, VAX-11/780, VAX-11/785l  &  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,d,            VAXstation 2000, VAXstation 3100,,            VAXstation 3200, VAXstation 3500,          #                                   4  e  n    +            VAXstation 3520, VAXstation 3540   *  VAXserver: VAXserver 100, VAXserver 2000,*            VAXserver 3100, VAXserver 3300,*            VAXserver 3400, VAXserver 3500,*            VAXserver 3600, VAXserver 3602,)            VAXserver 3800, VAXserver 3900s  $            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 520a      RISC-Based Processors:   -  DECstation:DECstation 2100, DECstation 3100,t            DECstation 3100sy  3            Personal DECstation 5000 Model 20/25 HX,i3            Personal DECstation 5000 Model 20/25 MX, 3            Personal DECstation 5000 Model 20/25 TX,i5            Personal DECstation 5000 Model 20/25 PXG+,o:            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,r        #                                   5b t  o    2            DECstation 5000 Model 120/125/133 PXG+,7            DECstation 5000 Model 120/125/133 PXG Turbo, 7            DECstation 5000 Model 120/125/133 PXG Turbo+   (            DECstation 5000 Model 200 CX,(            DECstation 5000 Model 200 HX,(            DECstation 5000 Model 200 MX,(            DECstation 5000 Model 200 PX,(            DECstation 5000 Model 200 TX,)            DECstation 5000 Model 200 PXG,x*            DECstation 5000 Model 200 PXG+,/            DECstation 5000 Model 200 PXG Turbo,m/            DECstation 5000 Model 200 PXG Turbo+t  (            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+s    DECsystem: DECsystem 3100,i#            DECsystem 5000 Model 25,a$            DECsystem 5000 Model 200,$            DECsystem 5000 Model 240,*            DECsystem 5100, DECsystem 5400,*            DECsystem 5500, DECsystem 5810,*            DECsystem 5820, DECsystem 5830,)            DECsystem 5840, DECsystem 5900.      MS-DOS Processors Supported  '  Personal  DECstation 316, 325 with DECn  2  Computer  EtherWORKS Turbo or LC Ethernet adapter  G  Note: Refer to the PATHWORKS for DOS Software Product Description (SPDn
  55.07.xx)  #                                   6n    p    Other Hardware Requirements  G  The DECserver 700 software runs on any of the following packaged hard-d  ware options:  	  DSRVW-**e  E  *  Denotes product variant models. For additional information, referi"     to the appropriate price book.  F  The following DECconnect cables and accessories are available for the  DECserver 700:s    H8584-AA  MP8 to MMJ Adaptere  /  H8585-AB  M58 to DB2J, Low Speed Modem Adaptert  0  H8585-AC  M58 to DA25, High Speed Modem Adapter  2  H8585-AA  MJ8 to DB9, Adapter for PC Interconnect  )  DW29-AA   ThinWire Adapter Module Optiond  G  The DECserver hardware requires both a transceiver drop cable and Eth-gE  ernet connection, H4005 or DELNI, to connect to a Thickwire EthernetnH  physical channel. The DECserver 700 supports both Thickwire and Twisted&  Pair connections integral to the box.    OPTIONAL HARDWARE    Terminals Supported  D  The DECserver 700 software supports the following Digital Equipment2  Corporation terminal devices that have keyboards:     o  LA12, LA34, LA35, LA36, LA38    o  All VTxxx terminalsr  #  Supported Terminal Parameters are:t  .  o  Character size: 7- or 8-bits per character  #                                   7c s  c    o  Parity: Even, Odd, or None  G  The automatic line speed detection (Autobaud) feature is supported for F  either 7-bit characters with even parity, or 8-bit characters with no  parity.  D  The DECserver 700 software also supports Digital Asian terminal de-4  vice variants when accessed from VMS/Hanzi systems.  D  The DECserver 700 software also supports Digital Asian terminal de-7  vice variants when accessed from VMS/Japanese systems.f  D  The DECserver 700 software also supports the following Digital Per-F  sonal Computers (PCs) in both terminal emulation mode and file trans-
  fer mode:    o  VAXmatei    o  DECstation  E  Note: This product will also operate on non-Digital terminal devices D  or personal computers such as terminals supporting VT100- or VT200-G  like characteristics, and personal computers supporting IBM[R] PC, IBM D  PC/XT, and IBM PC/AT[R] characteristics may operate with this prod-  uct.d    Printers Supportedn  G  The DECserver 700 software supports the following Digital asynchronouss)  printers when accessed from VMS systems:e  <  o  All LJ, LA, LQP, LXY, LN0, LG, and DTC printing devices.  F  The DECserver 700 software also supports Digital Asian printer device/  variants when accessed from VMS/Hanzi systems.u  F  The DECserver 700 software also supports Digital Asian printer device2  variants when accessed from VMS/Japanese systems.    #                                   80 o  a    Modems Supportedo  G  Both DECserver 700 models support asynchronous devices with interfacesT/  that conform to EIA/TTA-232-E/CCITT V.24/V.28.   D  Additionally, DECserver 700 models support Digital modems includingG  DF03, DF112, DF124, DF224, DF242, DFM X.29 pad, and DECmodem V32 full-eH  duplex asynchronous modems for either dial-in or dial-out applications.D  However, connections to data switches are NOT WARRANTED but may op-  erate with this product.i  E  Disk Space Requirements (Block Cluster Size= 1): Disk Space Require-C  ments for VMS:u  (  Disk space required for    3,550 blocks  installation:  (  Disk space required for    3,150 blocks  use (permanent):n    $  Disk Space Requirements for ULTRIX:  (  Disk space required        1.581 Kbytes  for installation and   permanent:      Disk Space Requirements for DOS  &  Disk space required for    625 Kbytes  installation:  &  Disk space required for    610 Kbytes  use (permanent):             #                                   9d    o  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.h    CLUSTER ENVIRONMENT  D  This layered product is fully supported when installed on any validG  and licensed VAXcluster* configuration without restrictions. The HARD- G  WARE REQUIREMENTS sections of this product's Software Product Descrip-aF  tion and System Support Addendum detail any special hardware required  by this product.b  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.a    SOFTWARE REQUIREMENTS    For VMS Systems:s  $  o  VMS Operating System V5.0 - V5.5  %  o  DECnet-VAX (Phase IV) V5.0 - V5.5     For ULTRIX Systems:  &  o  ULTRIX Operating System V4.0-V4.2A  4  o  MOP V4.2 (included with ULTRIX Operating System)    For MS-DOS Systems:  3  o  MS-DOS Operating System V3.1, V3.3, V4.01, V5.0n    o  PATHWORKS for DOS V4.1        #                                  10o g  n    For UNIX Systems:  F  The following generic operating systems are supported. Note that com-I  plete support cannot be granted on systems where customization has takenuE  place. Also note that some UNIX implementations not listed below mayt1  operate successfully, but no support is implied.h    o  BOOTP/TFTP       -  SunOS[TM] Release 4.0       -  OSF[R]/1 V1.0       -  IBM AIX[R] Version 3.1.1d  1     -  SCO[TM] UNIX System V/386 Release 3.2 V2.0        -  HP[R]-UX 8.0   F  Some System V[TM] systems, such as HP-UX and SCO, may not support the  up-line dump of server memory.     VMS Tailoring:i  F  For VMS V5.x systems, the following VMS classes are required for full'  functionality of this layered product:c    o  VMS Required Saveset    o  Network SupportF  
  o  Utilities:  D  For more information on VMS classes and tailoring, refer to the VMS>  Operating System Software Product Description (SPD 25.01.xx).    OPTIONAL SOFTWARE     o  Terminal Server Manager V1.6  #                                  11p t  n    GROWTH CONSIDERATIONS  E  The minimum hardware/software requirements for any future version ofnD  this product may be different from the requirements for the current	  version.n    DISTRIBUTION MEDIA   	  For VMS:l"     TK50, 9-track 1600 BPI Magtape    For ULTRIX:"     TK50, 9-track 1600 BPI Magtape    For MS-DOS:     RX33 and RX24   
  For UNIX:     RX23 and QIC-150    ORDERING INFORMATION     Software License: QL-XA5A9-AA  Software Media: QA-XA5A*-H*$  Software Documentation: QA-XA5AA-GZ'  Software Product Services: QT-XA5A*-**3  G  *  Denotes variant fields. For additional information on available li-oE     censes, services, and media, refer to the appropriate price book.-  G  The above information is valid at time of release. Please contact yourf:  local Digital office for the most up-to-date information.  A  [R] Domain is a registered trademark of Apollo Computer, Inc., av*     subsidiary of Hewlett-Packard Company.          #                                  12t e       =  [R] HP is a registered trademark of Hewlett-Packard Company.r  @  [R] IBM, AT, and AIX are registered trademarks of International"     Business Machines Corporation.  B  [R] MS and MS-DOS are registered trademarks of Microsoft Corpora-	     tion.e  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.-  @  [TM]System V is a trademark of American Telephone and Telegraph     Company.  F  [TM]The DIGITAL Logo, CI, DEC, DECbridge, DECconnect, DEC EtherWORKS,=     DECmate, DECnet, DECserver, DECstation, DECsystem, DELNI,r?     DEMPR, LA, LAT, LXY, MicroVAX, PATHWORKS, RX, ThinWire, TK, ?     ULTRIX, VAX, VAXcluster, VAXft, VAXmate, VAXserver, VAXsta- C     tion, VMS, VT, VT100, VT330, VT340, and VT420 are trademarks ofa"     Digital Equipment Corporation.  ;   1997 Digital Equipment Corporation. All rights reserved.                       #                                  13]