   	DECserver 300 	---------------------------     	Software Installation (VMS)                                                               	Order Number: AA-NE45C-TE   	  
 DECserver 300  -------------------------------      Software Installation (VMS)   
 December 1991   M This manual provides the procedure to install the DECserver 300 distribution  P software onto VMS systems, configure these systems as down-line load hosts, and M down-line load the DECserver 300 image.  This manual is intended for the VMS  " system manager or network manager.  : Supersession/Update Information:	This is a revised manual.  ' Operating System and Version:		VMS V5.0   & Software Version:			DECserver 300 V2.1  M This manual applies to Version 2.1 of the DECserver 300 software and Version  O 5.0 of the VMS operating system, and all subsequent maintenance releases up to   the next major product release.                                                	Order Number: AA-NE45C-TE                P The information in this document is subject to change without notice and should K not be construed as a commitment by Digital Equipment Corporation. Digital  O Equipment Corporation assumes no responsibility for any errors that may appear   in this document.   M The software described in this document is furnished under a license and may  D only be used or copied in accordance with the terms of such license.  G No responsibility is assumed for the use or reliability of software on  F equipment that is not supplied by Digital or its affiliated companies.  M Restricted Rights: Use, duplication, or disclosure by the U.S. Government is  N subject to restrictions as set forth in subparagraph (c)(1)(ii) of the Rights E in Technical Data and Computer Software clause at DFARS 252.227-7013.   0 Copyright  1991 by Digital Equipment Corporation All Rights Reserved   I The following are trademarks of Digital Equipment Corporation:  BI, DEC,   DECnet, DECserver,M DELNI, LAT, MicroVAX, ThinWire, ULTRIX, UNIBUS, VAX, VAXcluster, VAXstation,   VMS,   VT220, and the Digital logo.    M IBM is a registered trademark of International Business Machines Corporation. A UNIX is a registered trademark of UNIX System Laboratories, Inc.  J Vitalink is a registered trademark of Vitalink Communications Corporation.                      L  ---------------------------------------------------------------------------L  |This manual was produced by Telecommunications and Networks Publications.|L  ---------------------------------------------------------------------------              				Preface    Intended Audience   L   This document provides a system manager or network manager the procedures H   needed to install the terminal server software on a VMS[TM] load host.  P   The system manager or network manager should be familiar with both DECnet[TM] E   Phase IV network management concepts and the VMS operating system.     Structure of This Document  K   This document consists of one continuous procedure,  which is divided as  
   follows:  %   o	Preparing to install the software      o	Using VMSINSTAL      o	Using DSVCONFIG   "   o	Down-line loading the software     o	Completing the installation   /   o	Installing software on additional VMS hosts      This document also includes:  (   o	What to do if the installation fails  (   o	DECserver[TM] 300 distribution files   								      Conventions Used in This Manual   N   To use this manual effectively, you should be familiar with the conventions    discussed in this section:  3   o	All numbers are decimal unless otherwise noted.   +   o	All Ethernet addresses are hexadecimal.     N   ----------------------------------------------------------------------------     Convention	Meaning  N   ----------------------------------------------------------------------------    I   Special type	This special type indicates system output or user input.   < 		System output is in black type; user input is in red type.  F   UPPERCASE	VMS commands, node names, directory names, and file names  		appear in uppercase letters.  G   italic	Italic type in command syntax indicates variables  for  which  , 		either you or the system supplies a value.  H   [ key ]	Press the specified key.  For example,  means that you should  		press the Return key.   D   Ctrl/X	Hold down the Control key and simultaneously press the key ? 		specified by x.  The server displays this key combination as   		^x. O   -----------------------------------------------------------------------------  	            			Installation Procedure  			---------------------- H The following lists the topics provided in this document to install the - terminal server  software on a VMS load host:   # O	Preparing to install the software    O	Using VMSINSTAL    O	Using DSVCONFIG     O	Down-line loading the software   O	Completing the installation   - O	Installing software on additional VMS hosts   N At the end of this manual is a procedure that describes the steps to be taken O if the installation fails.  The final section of this document provides a list   of the distribution  files.       ! Preparing to Install the Software   N   Perform the following tasks before you install the terminal server software B   on your system (referred to as the load host in this procedure):  ,   1. Check your load host for the following:  M      a.	VMS  V5.0 or any subsequent maintenance release up to the next major   	product release is installed.  +      b. DECnet VAX[TM] Phase IV is running.   O      c.	The Ethernet controller is on the same Ethernet as the terminal server.   :   2. Ensure that the CMKRNL and SYSPRV privileges are set.  M   3. Verify that the load host has 2500 blocks of available disk space (2000  N      after installation), and an additional 2048 blocks for each up-line dump.  6   4. Backup the system before installing the software.  M   5. Mount the software media on an appropriate device drive, unless you are  =      installing from save sets copied from another load host.   J   6. Make a note of  the terminal server DECnet node address, DECnet node O      name (supplied by the network manager), and the Ethernet hardware address  *      (supplied by the hardware installer).  <   Installation requires approximately 5 minutes to complete.   				NOTE  4 		License Management Facility (LMF) is not required.       Using VMSINSTAL   L   Perform the following to install the terminal server software on the load ?   host.  To stop the installation at any time,  press Ctrl/Y.     *   7. Log in to the system manager account.  C   8. Enter the @SYS$UPDATE VMSINSTAL DS3021 your-device-identifier  N      OPTIONS N command to start VMSINSTAL.  Substitute your device identifier I      for your-device-identifier where the distribution medium is mounted.   M   9. If there are any active processes, VMSINSTAL lists them and asks if you  @      want to continue.  Enter YES to continue the installation.   M   10. Press Return if you have backed up your system disk,  and enter YES if  @       you mounted the software media on the appropriate device.     N   ----------------------------------------------------------------------------C   $ @SYS$UPDATE:VMSINSTAL DS3021  your-device-identifier OPTIONS N    6   VAX/VMS Software Product Installation Procedure Vn.n     It is 11-APR-1991 at 14:08. 1   Enter a question mark (?) at any time for help.   @   %VMSINSTAL-W-ACTIVE, The following processes are still active:
   MIKE_VCS   VCS Task 542.1   VCS Task 193.0"   * Do you want to continue anyway   [NO]? YES    ?   * Are you satisfied with the backup of your system disk[YES]?    4   Please mount the first volume of the set on xxxx:.   * Are you ready? Y  /   %MOUNT-I-MOUNTED, DS3 mounted on SYSTEM$xxxx: O   -----------------------------------------------------------------------------      Using VMSINSTAL (cont.)   L   11. Select option 2 (recommended) to print the release notes.   Press the N       Return key to print the release notes on the default printer or specify -       another print queue.                      M       If you select option 1, the release notes scroll on your terminal.  Be  J       aware that the release notes file can contain as many as 30 screens.  ,   12.Enter YES to continue the installation.    N   ----------------------------------------------------------------------------+   The following products will be processed: 
   DS3 V2.1  -   Beginning installation of DS3 V2.1 at 14:08   7   %VMSINSTAL-I-RESTORE, Restoring product save set A...    E   Release notes included with this kit are always copied to SYS$HELP.   #   Additional Release Notes Options:      1.  Display release notes    2.  Print release notes    3.  Both 1 and 2   4.  None of the above      * Select option [2]:     * Queue name [SYS$PRINT]: L   Job DS3020.RELEASE_NOTES (queue SYS$PRINT, entry 314) started on SYS$PRINT    6   * Do you want to continue the installation [NO]? YESP   ----------------------------------------------------------------------------         Using VMSINTAL (cont.)    J   13. Press the Return key to run the Installation Verification Procedure H       (IVP), which is recommended.  The IVP verifies that the DECSERVER K       directory exists, all the files from the distribution kit are in the  G       directory, and the release notes are in the SYS$HELP directory.     N   14. If your system is part of a VAXcluster system, use the CREATE/DIRECTORY J       command on each VAXcluster node after exiting VMSINSTAL so that the M       other nodes can execute the terminal server software.  You can do this  3       after you finish this installation procedure.   N   ----------------------------------------------------------------------------8   * Do you want to run the IVP after installation [YES]?7   %VMSINSTAL-I-RESTORE, Restoring product save set B... J   %VMSINSTAL-I-SYSDIR, This product creates a system directory [DECSERVER]  G   If you intend to execute this layered product on other nodes in your  F   VAXcluster, and you have the appropriate software license, you must F   prepare the system-specific roots on the other nodes by issuing the G   following command on each node (using a suitably privileged account):   -   $ CREATE/DIRECTORY SYS$SPECIFIC:[DECSERVER] &   /PROTECTION=(S:RWED,O:RWED, G:WER,W)   O   -----------------------------------------------------------------------------        Using VMSINSTAL (cont.)   J   15. If you receive one of the following messages, perform the procedure G       described within the message to update the MOM$LOAD logical name.      One possible message:     O   ----------------------------------------------------------------------------- B   Your installation is now complete. After exiting from VMSINSTAL:  E   1. Modify the definition of MOM$LOAD in your system start-up file,  :   SYS$MANAGER:SYSTARTUP_V5.COM, to resemble the following:  ,   $ DEFINE/SYSTEM/EXEC/NAME=NO_ALIAS/NOLOG - 	MOM$LOAD -  	SYS$SYSROOT:[MOM$SYSTEM], - 	SYS$SYSROOT:[DECSERVER]  M   This command ensures that the location of the server image is defined each  J   time the system is rebooted, necessary for successful down-line loading.N   ----------------------------------------------------------------------------       Another possible message:     N   ----------------------------------------------------------------------------B   Your installation is now complete. After exiting from VMSINSTAL:  >   1. Add the following  command to your system start-up file, :   SYS$MANAGER:SYSTARTUP_V5.COM, to resemble the following:  ,   $ DEFINE/SYSTEM/EXEC/NAME=NO_ALIAS/NOLOG - 	MOM$LOAD -  	SYS$SYSROOT:[DECSERVER]  M   This command ensures that the location of the server image is defined each  J   time the system is rebooted, necessary for successful down-line loading.N   ----------------------------------------------------------------------------    K      MOM$LOAD is a logical name that your load host uses to find the image  J      file of any product that must be down-line loaded. For each product, N      MOM$LOAD has an associated equivalent string that specifies the location !      of the product image file.     J      If you do not get either of these messages,  no modifications to the (      system start-up file are necessary.       Using VMSINSTAL (cont.)   2   16. VMSINSTAL is completed. Proceed to step 17.   N   This IVP command procedure is for informational purposes.   You do not need    to run it again at this time.     N   ----------------------------------------------------------------------------H   2. Configure the server into your host's database.  Execute a command D   procedure called DSVCONFIG.COM.  This command procedure is in the O   SYS$ROOT:[DECSERVER] directory.  If you have already executed this procedure  M   from previous installations, you only need to configure  additional units.  8   All previously defined units will still be configured.  M   The Installation Verification Procedure (IVP) for the DECserver 300 can be  H   found in SYS$TEST and may be run at any time by executing the command    procedure DS3$IVP.COM.  O   VMSINSTAL-I-MOVEFILES, Files will now be moved to their target directories...   Q   Beginning installation verification procedure for DECserver 300 V2.1 completed  
   at 14:30  #   VMSINSTAL procedure done at 14:30    $ N   ----------------------------------------------------------------------------     Using DSVCONFIG               L   17. If you are using the optional Terminal Server Manager (TSM) software, L       do not use the DSVCONFIG procedure; instead, refer to Terminal Server G       Manager Installation and Use to configure the load host database.   M   DSVCONFIG checks for data file DSVCONFIG.DAT in SYS$SYSROOT:[DECSERVER] or  H   SYS$COMMON:[DECSERVER] for VAXcluster systems.  It finds one of three 
   situations:   A   o	The file does not exist. The procedure creates DSVCONFIG.DAT.   /   o	The file exists and is formatted correctly.   A   o	The file exists but not in the correct format. The procedure   	reformats the file.  P   Each VAXclusterTM node might have an older version of  DSVCONFIG.DAT. In this N   case, DSVCONFIG copies the terminal server entries from that data file into M   the DSVCONFIG.DAT file on SYS$COMMON:[DECSERVER], and renames the  file in  O   SYS$SPECIFIC so that the DSVCONFIG.DAT file in SYS$COMMON is used thereafter.    				CAUTION   O   Do not execute any DECnet commands that  are part of DSVCONFIG separate from  N   the DSVCONFIG procedure.  Otherwise, DECnet databases could be changed with-@   out changing DSVCONFIG.DAT, causing a synchronization problem.      # Using DSVCONFIG (cont.)               F   18. Set the default to MOM$LOAD and start DSVCONFIG as shown in the J       example.  You might get merging messages if you are on a VAXcluster 
       system.   @   19. Select option 2 to add a new terminal server.                 N   ----------------------------------------------------------------------------   $ SET DEFAULT MOM$LOAD:    $ @DSVCONFIG      L   You must assign a unique DECnet node  name  and  DECnet  node address for    each new DECserver unit.  4   Press <RET> to start, or <CTRL/Z> to exit...              1   DECserver Configuration Procedure Version: Vn.n      Menu of Options    1 - List known DECservers    2 - Add a DECserver     3 - Swap an existing DECserver"   4 - Delete an existing DECserver!   5 - Restore existing DECservers #   CTRL/Z - Exit from this procedure    Your selection? 2 N   ----------------------------------------------------------------------------     Using DSVCONFIG  (cont.)     20. Enter the following:  $       -	DS300 for the DECserver type  $       -	DECnet node name and address  L         DSVCONFIG determines the validity of the node name entered.  If you L         get an error here, choose another node name.  The one you specified          is in use.  (       -	Terminal server Ethernet address  N   21. DSVCONFIG determines the load host service circuit-ID and displays this M       ID as the default.  Press the Return key to select the default service         circuit-ID.   L       DSVCONFIG adds the entry for the new terminal server to the databases K       and sets SERVICE ENABLED on the specified service circuit,  which is  N       necessary for down-line loading.   If you get an error from DECnet whileN       adding a terminal server, use option 4 to remove the entry, correct the        problem, then try again.    N   ----------------------------------------------------------------------------,   Type ? at any time for help on a question.M   Type CTRL/Z for any question to return to the menu without adding the unit.c     DECserver type? DS300o#   DECnet node name for unit? xxxxxxo'   DECnet node address for unit? xx.xxxxi.   Ethernet address of unit? xx-xx-xx-xx-xx-xx   $   DECnet Service Circuit-ID? [UNA-0]  F   If you get an error message now, the new DECserver unit will not be H   completely added, and you should use menu item #4 (Delete an existing =   DECserver) to remove it from the list of known DECservers. tN   ---------------------------------------------------------------------------- m   Using DSVCONFIG  (cont.)  1   22. Press the Return key to continue DSVCONFIG.e  %   23. Press Ctrl/Z to exit DSVCONFIG.o    N   ----------------------------------------------------------------------------"   Please hit <RETURN> to continue.  1   DECserver Configuration Procedure Version: Vn.n      Menu of Optionsl     1 - List known DECserverse   2 - Add a DECserver     3 - Swap an existing DECserver"   4 - Delete an existing DECserver!   5 - Restore existing DECserversd#   CTRL/Z - Exit from this procedure    Your selection?    $ N   ---------------------------------------------------------------------------- u   Down-Line Loading the Software  I   If you are installing a new terminal server,  down-line loading of the .L   software image is done automatically during power up of the hardware.  If M   this is the case, do not  perform steps 24 through 28; instead, proceed to .
   step 29.  N   24. Enter the NCP CONNECT NODE node-name command to connect to the terminal O       server. (Substitute your terminal server DECnet node name for node-name.)sH       If a maintenance password has been defined by the terminal server I       manager, use the following command: CONNECT NODE node-name SERVICE  N       PASSWORD password. (Substitute your terminal server maintenance password       for password.) e  I   25. Press the Return key to get the terminal server prompt.  Enter the iN       log-in password.  ACCESS is the terminal server default log-in password.  <   26. Enter your user name (a string of 1 to 16 characters).  I   27. Use the SET PRIVILEGED command and enter the password. The default -       password is SYSTEM.-  N   28. Use the INITIALIZE command to  down-line load the terminal server image L       to the terminal server.  The qualifier, DELAY xx, causes the terminal G       server to wait xx minutes before initializing.  This permits any  L       existing users time to log off.  You must also wait xx minutes before *       you can continue with the procedure.    N   ----------------------------------------------------------------------------   $ MCR NCP    NCP> CONNECT NODE node-name 0   Console connected (press Ctrl/D when finished)        # ACCESS  (not echoed).   DECserver 300 Terminal Server V2.0 (BLn.n)- 
   LAT V5.1  )   Please type HELP if you need assistance    Enter username>  SWINSTALLER d   Local> SET PRIVILEGED     Password> SYSTEM (not echoed)    Local> INITIALIZE DELAY xxN   ---------------------------------------------------------------------------- s  & Down-Line Loading the Software (cont.)  <   Perform steps 29 through 34 to verify the down-line load.   N   29. Enter the NCP CONNECT NODE node-name command to connect to the terminal E       server.  (Substitute your terminal server DECnet node name for -N       node-name.)  If a maintenance password has been defined by the terminal I       server manager,  use the following command: CONNECT NODE node-name -N       SERVICE PASSWORD password.  (Substitute your terminal server maintenance       password for password.)   I   30. Press the Return key to get the terminal server prompt.  Enter the sN       log-in password.  ACCESS is the terminal server default log-in password.  M   31. Read the identification message to ensure the latest version (Vn.n) of h6       the terminal server image was down-line loaded.   >   32. Enter your user name (any string of 1 to 16 characters).  0   33. Press Ctrl/D to return to the NCP prompt.   5   34. Enter EXIT to return to the VMS system prompt.    P   If this installation is a software upgrade, either you or the network manager 0   can now reload all existing terminal servers.     N   ----------------------------------------------------------------------------   $ MCR NCP    NCP> CONNECT NODE node-name 0   Console connected (press CTRL/D when finished)       # ACCESS  (not echoed)/   DECserver 300 Terminal Server V2.1 (BLn.n) - S
   LAT V5.1  o)   Please type HELP if you need assistanceg   Enter username>  SWINSTALLER g	   Local> n   NCP> exitM   $tN   ----------------------------------------------------------------------------         Completing the Installationi  8   Perform the following if the installation is complete:  J   35. Optionally, you should install the kit on at least two load hosts.  H       Also, you should have one load host for every 10 terminal servers.  L   36. Inform the system manager or network manager that the installation is        complete.o  I   37. Give this document to the person who will be managing the terminal  
       server.p  H Installing Software on Additional VMS Hosts                               O   To install the server distribution software onto an additional VMS load host  B   that is not a member of a VAXcluster system, follow these steps:  J   1. Invoke VMSINSTAL at the original load host, as follows.  (Substitute >      your device drive identifier for your-device-identifier.)  F      $ @VMSINSTAL DS3021  your-device-identifier OPTIONS G SYS$UPDATE:  @      OPTIONS G stores the save sets in the SYS$UPDATE directory.  J   2. Copy the save sets from the original load host to the alternate load K      host's SYS$UPDATE directory. The save sets are DS3nnn.A and DS3nnn.B,  I      where nnn is the version number of the DECserver 300 software.  For e.      example, nnn  equals 021 for version 2.1.  /   3. Run VMSINSTAL on the alternate load  host.    m  $ What To Do If the Installation Fails  2   Perform the following if the installation fails:  M   1. If the down-line load fails, it could be that service on the circuit is lI      disabled.  The following command shows how to check service circuit  E      BNA-0.  Substitute your load host service circuit-ID for BNA-0. V        $ MCR NCP r      NCP> SHOW CIR BNA-0 CHAR     O      a. If the display shows that the service is disabled, enter the following eJ         command to check if there are any users or applications using the          circuit:           NCP> SHOW KNOWN LINKS   L      b. If there are no known links active, enter the following commands to L         enable service circuit BNA-0.  Enabling the circuit disconnects the          active links.   $         NCP> SET CIR BNA-0 STATE OFF*         NCP> SET CIR BNA-0 SERVICE ENABLED#         NCP> SET CIR BNA-0 STATE ON-         NCP> EXITD	         $A  K   2. If your load host has more than one Ethernet controller, be sure that aL      the correct service circuit-ID was used during the DSVCONFIG procedure.N      If you do not know the load host service circuit-ID, use the NCP command D      SHOW ACTIVE CIRCUITS to display active circuit characteristics.        NCP> show active circuit                          5      Active circuit Volatile Summary as of 6-SEP-1991   P      Circuit     State     Loopback      Adjacent                               5                            Name          Routing Node-  9      SVA-0       on                      4.378 (LKGRT3)  -        NCP> exit  L   3. If you still have problems,  refer to DECserver 300 Problem Solving or !      inform your system manager. e   k    DECserver 300 Distribution FilesL ---------------------------------------------------------------------------- File Name				DescriptionL ----------------------------------------------------------------------------  ; SYS$TEST:DS3$IVP.COM			Installation verification procedure.t  J The following files are located in SYS$SYSROOT: or SYS$COMMON:[DECSERVER]:  ) DSVCONFIG.COM				Configuration procedure. 1 DSVCONFIG.DAT				Data file used by DSVCONFIG.COM.2; TSM$DS3_nnn_DEFAULTS.COM		File used by the Terminal Server S 					Manager (TSM) software.  9 DS3_UNIX_SPOOL.C			The sample C program file is used for k 					DECserver 300 spooling. 	  ? DS3_021_CRASH_DISPLAY.COM		Crash dump identification procedure. ( DS3__021_RELEASE_NOTES			Release notes. . SH1601ENG.SYS				DECserver 300 software image.A TSM$DS3_V21_ADD_LOCAL_SERVICE.COM 	File used by the TSM software.AA TSM$DS3_V21_DEDIC_SERV_PRINTER.COM	File used by the TSM software. @ TSM$DS3_V21_DEDIC_SERV_TERM.COM		File used by the TSM software. < TSM$DS3_V21_DSR_DTR_TERM.COM		File used by the TSM software.8 TSM$DS3_V21_GET_CHAR.COM		File used by the TSM software.@ TSM$DS3_V21_HOST_INIT_PRINTER.COM	File used by the TSM software.? TSM$DS3_V21_PC_TERM_OR_SERV.COM		File used by the TSM software. < TSM$DS3_V21_PORT_DEFAULT.COM		File used by the TSM software.  2 CHAR_MIB.TXT				Management Information Base (MIB)  					for user reference.  , RFC_1158.TXT				MIB file for user reference.. RS_232_MIB.TXT				MIB file for user reference.  L ----------------------------------------------------------------------------  