This and all subsequent DECserver models used the Local Area Transport (LAT) protocol which was/is also supported by many DEC operating systems including VMS, RSX-11, RSTS/E and Ultrix (an implementation of UNIX).
Through the use of a simple command, users could establish a logical connection, called a session, to any local service node that implemented the LAT protocol.
The DECserver 200 also provided the capability to connect host systems that did not support the LAT protocol, Digital personal computers, and dial-out modems directly to ports on the server.
The /DL version delivers these data leads through a single connector (similar to Centronics printer connection).
[1] The DECserver 500 series server provided a convenient method to connect logically up to 128 Digital asynchronous terminals to one or more service nodes (hosts) on an Ethernet.
The DECserver 500 series server also allowed for ULTRIX host-initiated connections to asynchronous printers.
The 500 series differed from other DECservers in that the configuration was not stored in nonvolatile storage locally on the server itself, but rather downline loaded from a file on a MOP host.
Configuration changes which needed to remain permanently had to be changed locally on the DECserver and also updated on the MOP host using the OpenVMS Terminal Server Configurator utility (SYS$COMMON:[DECSERVER]DS5CFG on VMS or /usr/lib/dnet/tsc on Ultrix) so that it would return the next reboot.
The 500 and 550 models are based on the PDP-11/53 chipset with 512 kb or 1.5 mb of on-board ram and can be reverted to a full PDP-11/53 system with a PROM swap and console port re-wire.
Also supported were remote-node and remote control applications as well as accounting event logging and audit trails.
The ports were used to connect asynchronous devices including terminals, printers, modems, or PCs to an Ethernet local area network (LAN).
The original units ran DECserver 700 software and were configured with 1 MB of operational memory.
The original units ran DECserver 700 software and were configured with 1 MB of operational memory.
It connects devices (such as printers, terminals, PCs, and modems) to local area networks (LANs).
The DECserver 708 can download the software image from the network or from the Flash RAM option if installed.
It offers RADIUS, Kerberos, RSA SecurID, PAP, CHAP, and CBCP or standard dial-back.
The following are the filenames used for the firmware files that get downloaded by various DECserver terminal servers when they boot up and initialize: These filenames are specified in a network request from the terminal server at boot time, to initiate a MOP download of the firmware.
The DECserver device's hardware address must be specified in the DECnet node database in order for the firmware file to be loaded.
The firmware's filename is not specified in the DECnet database, it is found in a network request from the terminal server.
If the firmware file does not exist in the MOM$SYSTEM directory at the time of a load request, the terminal server will not complete its boot process, and an error message will be displayed on the OpenVMS operator's console (and written to SYS$MANAGER:OPERATOR.LOG) and this message will give the name of the missing file.