   	 DECserver 90TL7 	 _____________________________________________________                   -                  	Software Installation (VMS)                                                                                 # 		        Order Number: AA-PMF4A-TE           DECserver 90TL 6  _____________________________________________________      Software Installation (VMS)      
  January 1992   O  This manual provides the procedure to install the DECserver 90TL distribution  M  software onto VMS systems, configure these systems as down-line load hosts,  O  and down-line load the DECserver 90TL image.  This manual is intended for the  H  person installing DECserver 90TL distribution software on a VMS system.  7  Supersession/Update Information:	This is a new manual.   /  Operating System and Version:	        VMS V5.0   6  Software Version:	                DECserver 90TL V1.0  O  This manual applies to Version 1.0 of the DECserver 90TL software and Version  P  5.0 of the VMS operating system, and all subsequent maintenance releases up to    the next major product release.                                                        # 		        Order Number: AA-PMFA4-TE                             J  The information in this document is subject to change without notice and K  should not be construed as a commitment by Digital Equipment Corporation.  M  Digital Equipment Corporation assumes no responsibility for any errors that    may appear in this document.   N  The software described in this document is furnished under a license and may E  only be used or copied in accordance with the terms of such license.   H  No responsibility is assumed for the use or reliability of software on G  equipment that is not supplied by Digital or its affiliated companies.   N  Restricted Rights: Use, duplication, or disclosure by the U.S. Government is J  subject to restrictions as set forth in subparagraph (c) (1) (ii) of the O  Rights in Technical Data and Computer Software clause at DFARS 252.227-7013.     @              Copyright (C) 1992 by Digital Equipment Corporation/                             All Rights Reserved   J  The following are trademarks of Digital Equipment Corporation:  BI, DEC, K  DECnet, DECserver, DELNI, LAT, MicroVAX, Q-bus, ThinWire, ULTRIX, UNIBUS,  ?  VAX, VAXcluster, VAXstation, VMS, VT220, and the Digital logo.     +  The following are third-party trademarks:    N  IBM is a registered trademark of International Business Machines Corporation.B  UNIX is a registered trademark of UNIX System Laboratories, Inc. K  Vitalink is a registered trademark of Vitalink Communications Corporation.       M    This manual was produced by Telecommunications and Networks Publications.        M  ____________________________________________________________________________ M                                                                       Preface    Intended Audience   P   This document provides a system or network manager with the procedures needed O   to install the Ethernet communication server software on a VMS(TM) load host.   H   The system 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  J   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) 90TL 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.   L   __________________________________________________________________________   Convention	Meaning  L   __________________________________________________________________________  J   Special type  This special type indicates system output or user input.  J                 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.  E   italic	Italic type in command syntax indicates variables for which  :                 either you or the system supplies a value.  A    _____                                                ______    F   | key |	Press the specified key.  For example, |Return|  means that A    _____        you should press the Return key.        ______      D   Ctrl/X	Hold down the Control key and simultaneously press the key M                 specified by X.  The communications server displays this key  "                 combination as ^X.L   __________________________________________________________________________               M  ____________________________________________________________________________ M                                                        Installation Procedure     J   The following lists the topics provided in this document to install the 4   communications 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   The procedure at the end of this manual describes the steps you take if the M   installation fails.  The final section of this document provides a list of     the distribution files.         ! Preparing to Install the Software   K   Perform the following tasks before you install the communications server  K   software 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 communications            server.  ;   2.  Ensure that the CMKRNL and SYSPRV privileges are set.   N   3.  Verify that the load host has 2600 blocks of available disk space (2200 N       after installation) and an additional 2048 blocks for each up-line dump.  7   4.  Backup the system before installing the software.   N   5.  Mount the software media on an appropriate device drive, unless you are >       installing from save sets copied from another load host.  N   6.  Make a note of the communications server DECnet node address and DECnet L       node name, supplied by the network manager, and the Ethernet hardware 2       address, supplied by the hardware installer.  <   Installation requires approximately 5 minutes to complete.   %                                (NOTE)   >             License Management Facility (LMF) is not required.       Using VMSINSTAL   M   Perform the following to install the communications server software on the  A   load host.  To stop the installation at any time, press Ctrl/Y.   +   7.  Log in to the system manager account.   D   8.  Enter the @SYS$UPDATE VMSINSTAL DS9010 your-device-identifier O       OPTIONS N command to start VMSINSTAL.  Substitute your device identifier  J       for your-device-identifier where the distribution medium is mounted.  N   9.  If there are any active processes, VMSINSTAL lists them and asks if you A       want to continue.  Enter YES to continue the installation.    L   10. Press Return if you have backed up your system disk, and enter YES if @       you mounted the software media on the appropriate device.   O   _____________________________________________________________________________   B   $ @SYS$UPDATE:VMSINSTAL DS9010 your-device-identifier OPTIONS N   6   VAX/VMS Software Product Installation Procedure Vn.n     It is 11-JAN-1992 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, DS9 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.       O   _____________________________________________________________________________   +   The following products will be processed:    DS90 V1.0   .   Beginning installation of DS90 V1.0 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 DS9010.RELEASE_NOTES (queue SYS$PRINT, entry 314) started on SYS$PRINT    6   * Do you want to continue the installation [NO]? YESO   _____________________________________________________________________________        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.     O   _____________________________________________________________________________   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]O   _____________________________________________________________________________   >   14. If your system is part of a VAXcluster] system, use the E       CREATE/DIRECTORY command on each VAXcluster node after exiting  N       VMSINSTAL so that the other nodes can execute the communications server N       software.  You can do this after you finish this installation procedure.       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.O   _____________________________________________________________________________          Another possible message:   O   _____________________________________________________________________________   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.O   _____________________________________________________________________________   P   MOM$LOAD is a logical name that your load host uses to find the image file of O   any product that must be down-line loaded. For each product, MOM$LOAD has an  P   associated equivalent string that specifies the location of the product image    file.   M   If you do not get either of these messages, no modifications to the system     start-up file are necessary.       Using VMSINSTAL (cont.)   M   16. VMSINSTAL is completed. Proceed to step 17.   Note that step 18 starts  ;       the DSVCONFIG.COM procedure mentioned in the example.   L   This IVP command procedure described in  the example is for informational ;   purposes.   You do not need to run it again at this time.   O   _____________________________________________________________________________     H   2. Configure the server into your host's database.  Execute a command D   procedure called DSVCONFIG.COM.  This command procedure is in the E   SYS$ROOT:[DECSERVER] directory.  If you have already executed this  D   procedure from previous installations, you only need to configure K   additional units.  All previously defined units will still be configured.   K   The Installation Verification Procedure (IVP) for the DECserver 90TL can  K   be found in SYS$TEST and may be run at any time by executing the command     procedure DS90$IVP.COM.   O   VMSINSTAL-I-MOVEFILES, Files will now be moved to their target directories...   H   Beginning Installation Verification Procedure for DECserver 90TL V1.0    completed at 14:30  #   VMSINSTAL procedure done at 14:30    $ O   _____________________________________________________________________________        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.   K   o The file exists but not in the correct format. The procedure reformats  
     the file.   M   Each VAXcluster node might have an older version of DSVCONFIG.DAT. In this  O   case, DSVCONFIG copies the communications server entries from that data file  I   into the DSVCONFIG.DAT file on SYS$COMMON:[DECSERVER], and renames any  P   versions in SYS$SPECIFIC so that the DSVCONFIG.DAT file in SYS$COMMON is used 
   thereafter.     
 				(CAUTION)  			 B               Do not execute any DECnet commands that are part of @               DSVCONFIG separate from the DSVCONFIG procedure.  C               Otherwise, DECnet databases could be changed without  H               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.   F   19. Select option 2 to add a new communications server.               O   _____________________________________________________________________________      $ SET DEFAULT MOM$LOAD:    $ @DSVCONFIG    M   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 O   _____________________________________________________________________________            Using DSVCONFIG (cont.)      20. Enter the following:  %       -	DS90TL for the DECserver type   $       -	DECnet node name and address  L         DSVCONFIG determines the validity of the node name entered.  If you O         get an error here, choose another node name.  The one you specified is           in use.   .       -	Communications 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._  H       DSVCONFIG adds the entry for the new communications server to the K       databases and sets SERVICE ENABLED on the specified service circuit, fJ       which is necessary for down-line loading.  If you get an error from N       DECnet while adding a communications server, use option 4 to remove the 1       entry, correct the problem, then try again.f  O   _____________________________________________________________________________   ,   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.p     DECserver type? DS90TL#   DECnet node name for unit? xxxxxx '   DECnet node address for unit? xx.xxxx .   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. aO   _____________________________________________________________________________n   m     Using DSVCONFIG (cont.)e  1   22. Press the Return key to continue DSVCONFIG.s  %   23. Press Ctrl/Z to exit DSVCONFIG.nO   _____________________________________________________________________________r  o"   Please hit <RETURN> to continue.  i1   DECserver Configuration Procedure Version: Vn.n   e   Menu of Optionst     1 - List known DECserversi   2 - Add a DECserverR    3 - Swap an existing DECserver"   4 - Delete an existing DECserver!   5 - Restore existing DECservers #   CTRL/Z - Exit from this procedure)                    _________   Your selection? | Ctrl/Z  |u   $                _________O   _____________________________________________________________________________        Down-Line Loading the Software  K   During power up of the hardware, down-line loading of the software image eN   occurs automatically.  If this is the case, do not perform steps 24 through "   28; instead, proceed to step 29.  E   24. Enter the NCP CONNECT NODE node-name command to connect to the  O       communications server. Substitute your communications server DECnet node UM       name for node-name.  If a maintenance password has been defined by the aM       communications server manager, use the following command: CONNECT NODE aK       node-name SERVICE PASSWORD password.  Substitute your communications  0       server maintenance password for password.   K   25. Press the Return key to get the communications server prompt.  Enter  O       the log-in password.  ACCESS is the communications server default log-in s       password.m  >   26. Enter your user name (any string of 1 to 16 characters).  I   27. Use the SET PRIVILEGED command and enter the password. The default         password is SYSTEM.w  F   28. Use the INITIALIZE command to down-line load the communications K       server image to the communications server.  The qualifier, DELAY xx, oP       causes the communications server to wait xx minutes before initializing.  N       This permits any existing users time to log off.  You must also wait xx 9       minutes before you can continue with the procedure.o  O   _____________________________________________________________________________u     $ MCR NCP    NCP> CONNECT NODE node-names0   Console connected (press CTRL/D when finished)    ________v   | Return |    ________      # ACCESS (not echoed)f>   DECserver 90TL Communications Server V1.0 (BLn.n) - LAT V5.1  I   (c) Copyright 1992, Digital Equipment Corporation - All Rights Reserved   )   Please type HELP if you need assistance    Enter username> SWINSTALLER    Local> SET PRIVILEGED     Password> SYSTEM (not echoed)    Local> INITIALIZE DELAY xxO   _____________________________________________________________________________h   e  & Down-Line Loading the Software (cont.)  <   Perform steps 29 through 34 to verify the down-line load.   E   29. Enter the NCP CONNECT NODE node-name command to connect to the aK       communications server.  Substitute your communications server DECnet cN       node name for node-name.  If a maintenance password has been defined by L       the communications server manager, use the following command: CONNECT P       NODE node-name SERVICE PASSWORD password.  Substitute your communications /       server maintenance password for password.u  K   30. Press the Return key to get the communications server prompt.  Enter yO       the log-in password.  ACCESS is the communications server default log-in a       password.l  M   31. Read the identification message to ensure the latest version (Vn.n) of _<       the communications 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. o  P   If this installation is a software upgrade, either you or the network manager 6   can now reload all existing communications servers.   O   _____________________________________________________________________________l     $ MCR NCP    NCP> CONNECT NODE node-name 0   Console connected (press CTRL/D when finished)    ________    | Return |    ________e     # ACCESS (not echoed)   >   DECserver 90TL Communications Server V1.0 (BLn.n) - LAT V5.1  I   (c) Copyright 1992, Digital Equipment Corporation - All Rights Reserved   )   Please type HELP if you need assistancef   Enter username> SWINSTALLER            _________i   Local> | Ctrl/D  |           _________    NCP> exita   $ O   _____________________________________________________________________________        Completing the Installation   8   Perform the following if the installation is complete:  J   35. Optionally, you should install the kit on at least two load hosts.  N       Also, you should have one load host for every 10 communications servers.  M   36. Inform the system or network manager that the installation is complete.   J   37. Give this document and any other software manuals to the person who 1       will be managing the communications server.b  %                                (NOTE)k  D          The installation manual fits in the pocket of the Ethernet 4          communications server documentation binder.  + Installing Software on Additional VMS Hosts   O   To install the server distribution software onto an additional VMS load host dB   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.  G       $ @VMSINSTAL DS9010  your-device-identifier OPTIONS G SYS$UPDATE:e  A       OPTIONS G stores the save sets in the SYS$UPDATE directory.f  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 DS9nnn.A and DS9nnn.B, nJ      where nnn is the version number of the DECserver 90TL software.  For -      example, nnn equals 010 for version 1.0.o  .   3. Run VMSINSTAL on the alternate load host.   i  $ What to Do If the Installation Fails  2   Perform the following if the installation fails:  N   1.  If the down-line load fails, it could be that service on the circuit is J       disabled.  The following command shows how to check service circuit F       BNA-0.  Substitute your load host service circuit-ID for BNA-0.          $ MCR NCP        NCP> SHOW CIR BNA-0 CHAR      P       a. If the display shows that the service is disabled, enter the following K          command to check if there are any users or applications using the /          circuit:t            NCP> SHOW KNOWN LINKS t  M       b. If there are no known links active, enter the following commands to  M          enable service circuit BNA-0.  Enabling the circuit disconnects the            active links. k  %          NCP> SET CIR BNA-0 STATE OFFy+          NCP> SET CIR BNA-0 SERVICE ENABLEDt$          NCP> SET CIR BNA-0 STATE ON          NCP> EXIT
          $  L   2.  If your load host has more than one Ethernet controller, be sure that O       the correct service circuit-ID was used during the DSVCONFIG procedure.  _O       If you do not know the load host service circuit-ID, use the NCP command cE       SHOW ACTIVE CIRCUITS to display active circuit characteristics.          NCP> SHOW ACTIVE CIRCUIT                         6       Active circuit Volatile Summary as of 6-JAN-1992   L       Circuit     State     Loopback      Adjacent                          6                             Name          Routing Node  :       BNA-0       on                      4.378 (LKGRT3)  :       BNA-1       on                                                  NCP> exitn  I   3. If you still have problems, refer to Ethernet Communications Server S4      Problem Solving or inform your system manager.    c  ! DECserver 90TL Distribution Filesn    G  ______________________________________________________________________N  File Name			     Description G  ______________________________________________________________________e  H  SYS$TEST:DS90$IVP.COM              Installation verification procedure.    J The following files are located in SYS$SYSROOT: or SYS$COMMON:[DECSERVER]:    < DSVCONFIG.COM                       Configuration procedure.  D DSVCONFIG.DAT                       Data file used by DSVCONFIG.COM.  K DS9_UNIX_SPOOL.C                    The sample C program file is used for  l=                                     DECserver 90TL spooling. e  H DS9_010_CRASH_DISPLAY.COM           Crash dump identification procedure.  3 DS9_010_RELEASE_NOTES               Release notes. t  B MNENG1.SYS                          DECserver 90TL software image.  M TSM$DS9_V10_ADD_LOCAL_SERVICE.COM   File used by the Terminal Server Manager  3                                     (TSM) software.   B TSM$DS9_V10_DEDIC_SERV_PRINTER.COM  File used by the TSM software.  C TSM$DS9_V10_DEDIC_SERV_TERM.COM     File used by the TSM software. _  B TSM$DS9_V10_DEFAULTS.COM            File used by the TSM software.  B TSM$DS9_V10_DSR_DTR_TERM.COM        File used by the TSM software.  B TSM$DS9_V10_GET_CHAR.COM            File used by the TSM software.  B TSM$DS9_V10_HOST_INIT_PRINTER.COM   File used by the TSM software.  B TSM$DS9_V10_PC_TERM_OR_SERV.COM     File used by the TSM software.  B TSM$DS9_V10_PORT_DEFAULT.COM        File used by the TSM software.      J CHAR-MIB_CONCISE.TXT                Management Information Base (MIB) file7                                     for user reference.   @ CHAR-MIB.TXT                        MIB file for user reference.  @ RFC-1158.TXT                        MIB file for user reference.  @ RS-232-MIB.TXT                      MIB file for user reference.  @ RS-232-MIB_CONCISE.TXT              MIB file for user reference.    