 















          MUXserver 100 Remote Terminal
          MUXserver 100 Remote Terminal
          MUXserver 100 Remote Terminal
          Server Software Installation Guide
          Server Software Installation Guide
          Server Software Installation Guide
          (VMS/MicroVMS)
          (VMS/MicroVMS)
          (VMS/MicroVMS)


          Order Number: Order No. AA-JC20AC-TE



          This guide tells you how to install the MUXserver 100
          distribution software onto VMS and MicroVMS systems
          and how to establish these systems as down-line load
          hosts. This guide is intended for the VMS/MicroVMS
          system manager or the network manager.





          Revision/Update Information:
          Revision/Update Information:
          Revision/Update Information:
                                         UPDATE This document
                                        INFORMATION: supersedes
                                        the guide for the
                                        MUXserver 100 V1.2.
                                        OPERATING VMS or MicroVMS
                                        V4.0 SYSTEM and later.
                                        VERSION: VERSION:
                                        MUXserver 100 V2.0



          Digital Equipment Corporation
          Digital Equipment Corporation
          Digital Equipment Corporation

 





          ________________________
          October 1989
          October 1989
          October 1989

          __________
          The information in this document is subject to change
          without notice and should not be construed as a
          commitment by Digital Equipment Corporation. Digital
          Equipment Corporation assumes no responsibility for
          any errors that may appear in this document.
          The software described in this document is furnished
          under a license and may be used or copied only in
          accordance with the terms of such license.

          No responsibility is assumed for the use or
          reliability of software on equipment that is not
          supplied by Digital Equipment Corporation or its
          affiliated companies.
          __________
          Copyright October 1989 by Digital Equipment
          Corporation

          All Rights Reserved.
          Printed in U.S.A.
          __________
          The postpaid READER'S COMMENTS form on the
          last page of this document requests the user's
          critical evaluation to assist in preparing future
          documentation.


          The following are trademarks of Digital Equipment
          Corporation:

          DEC             DIBOL         UNIBUS
          DEC/CMS         EduSystem     VAX
          DEC/MMS         IAS           VAXcluster
          DECnet          MASSBUS       VMS
          DECsystem-10    PDP           VT
          DECSYSTEM-20    PDT
          DECUS           RSTS
                                        DIGITAL
                                        DIGITAL
                                        DIGITAL
          DECwriter       RSX
                                                 [identification]


          This document was prepared using VAX DOCUMENT, Version
          1.1

 





          _______________________________________________________

          Preface
          Preface
          Preface


          This installation guide explains how to:
          o  Install the distribution kit software on a VAX/VMS
             Version 5.0 or later system running Phase IV
             DECnet.

          o  Configure your MUXserver 100 into the DECnet
             database on the down-line load host.

          __________________________________________________________________
           INTENDED AUDIENCE
           INTENDED AUDIENCE
           INTENDED AUDIENCE
          This guide contains information intended for the
          system or network managers responsible for making
          server products available on their Ethernet. System
          managers are responsible for setting up the nodes
          that will down-line load the MUXserver 100 software.
          Network managers are responsible for the Local Area
          Network (LAN).

          System and network managers should be familiar with
          DECnet Phase IV network management concepts.

          __________________________________________________________________
          STRUCTURE OF THIS GUIDE
          STRUCTURE OF THIS GUIDE
          STRUCTURE OF THIS GUIDE


          o  Chapter 1 Introduces the MUXserver 100 Remote
             Terminal Server and summarizes the installation
             and configuration procedures.
          o  Chapter 2 Explains how to prepare for the
             installation and describes the software
             installation process.

          o  Chapter 3 Describes how to install the MUXserver
             100 software.



                                                              vii
                                                              vii
                                                              vii

 

          Preface
          Preface
          Preface




          o  Chapter 4 Describes the post-installation
             procedures.

          o  Chapter 5 Explains how to add the MUXserver 100
             Remote Terminal Server into the load host's DECnet
             database, as well as how to swap, delete, and
             restore MUXserver 100 units.
          o  Appendix A Contains a sample installation procedure

          o  Appendix B Contains sample MUXserver 100
             configurations.

          __________________________________________________________________
          Related Documents
          Related Documents
          Related Documents
          Other MUXserver 100 Remote Terminal Server Documents:


          o  MUXserver 100 Network Reference Manual (EK-DSRZA-
             RM)

             Describes how to set up, manage, monitor, and
             troubleshoot the MUXserver 100 Remote Terminal
             Server.
          o  MUXserver 100 User's Pocket Guide (EK-DSRZA-PG)

             Summarizes the terminal user's environment.
          o  MUXserver 100 Network Installation Manual (EK-
             DSRZA-IN)

             Describes environmental requirements for the
             MUXserver 100 Remote Terminal Server and the
             installation of the hardware unit.
          o  MUXserver 100 Network Identification Card (EK-
             DSRZA-ID)

             Records the serial number and Ethernet address of
             the MUXserver 100 Remote Terminal Server.




          viii
          viii
          viii

 






          _______________________________________________________

   1       INTRODUCING THE MUXserver 100
   1       INTRODUCING THE MUXserver 100
   1       INTRODUCING THE MUXserver 100





          __________________________________________________________________
   1.1     WHAT IS THE MUXserver 100?
   1.1     WHAT IS THE MUXserver 100?
   1.1     WHAT IS THE MUXserver 100?

          The MUXserver 100 is a remote terminal server that
          connects to an Ethernet Local Area Network (LAN). The
          server connects to as many as two DECmux II units.
          Each DECmux II connects as many as eight terminals (or
          other asynchronous interactive port devices) to a LAN,
          allowing each device to communicate with the other
          nodes on that LAN.
          The software that you are about to install is
          comprised of the files in the MUXserver 100
          distribution kit. After you install the distribution
          software, configure the load host's node database for
          all new servers.

          __________________________________________________________________
   1.2     MUXserver 100 CONCEPTS
   1.2     MUXserver 100 CONCEPTS
   1.2     MUXserver 100 CONCEPTS

          The MUXserver 100 gives terminal devices access to all
          of the LAN services.

          ___________________________
   1.2.1   Connections
   1.2.1   Connections
   1.2.1   Connections
          Port devices are to be connected directly to the
          DECmux II and may not be connected using modems. The
          MUXserver 100 and DECmux II also support printers that
          support RS-232-C or asynchronous connections.





                                                              1-1
                                                              1-1
                                                              1-1

 

          INTRODUCING THE MUXserver 100
          INTRODUCING THE MUXserver 100
          INTRODUCING THE MUXserver 100



          ___________________________
   1.2.2   Services
   1.2.2   Services
   1.2.2   Services

          The MUXserver 100 gives terminals access to services
          offered on the LAN. A service is a resource, such
          as a computer. Each MUXserver 100 user can maintain
          up to six simultaneous connections to these various
          services. However, they can actively use only one
          connection at a time.

          ___________________________
   1.2.3   Service Nodes and LAT Protocol
   1.2.3   Service Nodes and LAT Protocol
   1.2.3   Service Nodes and LAT Protocol
          Server users are offered services by service nodes.
          A service node is any node on the LAN that implements
          the Local Area Transport (LAT) protocol. The server,
          in turn, uses the same LAT protocol to connect
          terminals to these services. LAT architecture uses
          Ethernet to make logical connections between terminals
          and service nodes on the same network.

          When connected to a service, a terminal appears to
          be connected directly to the service node. DECnet is
          not necessary for VAX/VMS systems to function as LAT
          service nodes.

          ___________________________
   1.2.4   LAT Software
   1.2.4   LAT Software
   1.2.4   LAT Software

          The LAT software on a VMS installation includes
          the LTDRIVER, which is a port driver in direct
          communication with the system's terminal class
          driver. LTDRIVER implements the protocol necessary
          to communicate with devices connected to the server,
          and is used in place of a local port driver such as
          the DZDRIVER. A LAT Control Program (LATCP) provides
          the command interface to the LTDRIVER. LATCP can be
          used to start and stop the driver, as well as to set
          and to display characteristics of the driver.




          1-2
          1-2
          1-2

 

                                    INTRODUCING THE MUXserver 100
                                    INTRODUCING THE MUXserver 100
                                    INTRODUCING THE MUXserver 100



          __________________________________________________________________
   1.3     PERFORMING THE SOFTWARE INSTALLATION
   1.3     PERFORMING THE SOFTWARE INSTALLATION
   1.3     PERFORMING THE SOFTWARE INSTALLATION

          As software installer, you have two responsibilities:
          1
          1
          1
             Installing the MUXserver 100 distribution software.

          2
          2
          2
             Configuring the load host's node database.

          The purpose of these two activities is to establish
          your VMS system as a load host for one or more
          servers. A load host is a system that contains the
          server image and whose node database has entries for
          specific servers, and, as a result, can down-line load
          the server image to servers on the local Ethernet. In
          addition, a load host performs maintenance activities,
          such as receiving up-line dumps from the server.
          A load host can be a single VMS system, or it can be a
          member node of a VAXcluster. For a VMS system to act
          as a load host, it must be running DECnet Phase IV and
          it must be located on the same Ethernet as the server.

          Load hosts are assigned by the network manager.
          Digital advises that you establish more than one
          system as a load host for each server. Alternate hosts
          free the server from dependence on one particular load
          host. For each server, Digital suggests a minimum of
          two load hosts. Digital also recommends one load host
          for every ten servers on a network.
          In addition to the two tasks just described, you
          have another responsibility. The total software
          installation procedure requires coordination with
          both the hardware installer of a new server and
          the manager of an existing server. For example, the
          software should be installed before the hardware
          is powered up for the first time. Chapter 5 details
          the necessary coordination efforts between you, the
          hardware installer, and the server manager.





                                                              1-3
                                                              1-3
                                                              1-3

 

          INTRODUCING THE MUXserver 100
          INTRODUCING THE MUXserver 100
          INTRODUCING THE MUXserver 100



          ___________________________
   1.3.1   Installing the MUXserver 100 Distribution Software
   1.3.1   Installing the MUXserver 100 Distribution Software
   1.3.1   Installing the MUXserver 100 Distribution Software

          You install the server distribution software onto
          a VMS system with an automated procedure called
          VMSINSTAL. The MUXserver 100 software distribution
          kit includes a procedure file that VMSINSTAL uses to
          do the installation. VMSINSTAL does the following:
          o  Copies the files from the distribution media to the
             load host.

          o  Creates the appropriate directory for these files.
          o  Processing release notes.

          See Chapter 3 for instructions on installing the
          distribution software.

          ___________________________
   1.3.2   Configuring the Load Host's Node Database
   1.3.2   Configuring the Load Host's Node Database
   1.3.2   Configuring the Load Host's Node Database

          Once you have copied the distribution software to
          your VMS system, you must configure its node database
          to support new servers. You configure this database
          with an automated procedure called DSVCONFIG. The
          configuration procedure file is part of the MUXserver
          100 software distribution kit.
          Configuration of the load host's node database
          means defining an entry for each server in a data
          file called DSVCONFIG.DAT. This file is created
          automatically by DSVCONFIG, and it is part of a load
          host's node database.

          Configuration of a new server involves adding an entry
          to this database. The entry identifies the server
          type, its DECnet node name and DECnet node address,
          its service circuit-ID, its Ethernet address, its dump
          file, and the server image.





          1-4
          1-4
          1-4

 

                                    INTRODUCING THE MUXserver 100
                                    INTRODUCING THE MUXserver 100
                                    INTRODUCING THE MUXserver 100




          Configuration encompasses modification or deletion of
          entries for existing servers. With DSVCONFIG you can
          configure the load host's node database in these ways:

          o  Add a new unit.
          o  Swap an old unit with a new one.

          o  Remove a unit.
          o  Restore the previous configuration from the local
             database.

          To configure a server on a VAXcluster, install the
          distribution software onto one member node, and then
          configure the node databases of the members that you
          want to establish as load hosts.
          When you complete the configuration procedure, you
          have established your VMS system as a load host for
          each server that has an entry in the node database.
          See Chapter 5 for instructions on configuring the load
          host's node database to support servers.





















                                                              1-5
                                                              1-5
                                                              1-5

 






          _______________________________________________________

   2       Preparing to Install the MUXserver 100
   2       Preparing to Install the MUXserver 100
   2       Preparing to Install the MUXserver 100




          This chapter discusses the preparations and
          requirements necessary for installing the MUXserver
          100 software.
          This manual applies to Version 2.3 of the MUXserver
          100 software and all subsequent maintenance releases
          up to the next major product release.

          Your bill of materials (BOM) and indented bills report
          (BIL) specify the number and contents of your media.
          Be sure to verify the contents of your kit with this
          information. If your kit is damaged or if you find
          that parts of it are missing, contact your Digital
          representative.
          The MUXserver 100 distribution kit provides online
          release notes. Digital strongly recommends that you
          read the release notes before proceeding with the
          installation. For information on accessing the online
          release notes, see Section 3.1.1

          __________________________________________________________________
   2.1     Required Operating System Components
   2.1     Required Operating System Components
   2.1     Required Operating System Components
          The VMS operating system comes with a variety of
          support options, or classes. Classes include such
          features as networking and RMS journaling. To use the
          MUXserver 100 software, your system should be running
          a version of VMS that includes the following classes:

          o  Base
          o  Network support





                                                              2-1
                                                              2-1
                                                              2-1

 

          Preparing to Install the MUXserver 100
          Preparing to Install the MUXserver 100
          Preparing to Install the MUXserver 100




          For a complete list of the required classes, see the
          Software Support Addendum (SSA), which comes with the
          Software Product Description (SPD).
          __________________________________________________________________

   2.2     Prerequisite Hardware
   2.2     Prerequisite Hardware
   2.2     Prerequisite Hardware
          To use the MUXserver 100 software, you must have a
          MUXserver 100 Remote Terminal Server connected to the
          local Ethernet.

          __________________________________________________________________
   2.3     License Registration
   2.3     License Registration
   2.3     License Registration
          At this time, the MUXserver 100 software does not
          support LMF. The MUXserver 100 does not have a product
          authorization key (PAK) and does not need to be
          registered.

          __________________________________________________________________
   2.4     VAXcluster Considerations
   2.4     VAXcluster Considerations
   2.4     VAXcluster Considerations
          To install the server distribution software onto an
          alternate load host that is a member of a VAXcluster,
          install the software unto one cluster member, and
          then:


          1
          1
          1
             Log into a privileged (system) account on one of
             the other members of the cluster.

          2
          2
          2
             Enter the following commands:

                       $ CREATE/DIRECTORY SYS$SPECIFIC:[DECSERVER]_
                       /PROTECTION=(S:RWED,O:RWED) <RET>

                       ASSIGN/SYSTEM/EXECUTIVE_MODE ' current-search-string', -
                          SYS$SYSROOT:[DECSERVER] MOM$LOAD
                       $ ASSIGN/SYSTEM/EXECUTIVE_MODE SYS$SYSROOT:[MOM$SYSTEM]
                           MOM$SYSTEM

                       $ ASSIGN/SYSTEM/EXECUTIVE_MODE MOM$SYSTEM, MOM$LOAD
                           MOM$SYSTEM_SOFTID

          2-2
          2-2
          2-2

 

                           Preparing to Install the MUXserver 100
                           Preparing to Install the MUXserver 100
                           Preparing to Install the MUXserver 100




          3
          3
          3
             Include the second command from step 2 in the
             node's system start-up procedures.

          __________________________________________________________________
   2.5     Installation Procedure Requirements
   2.5     Installation Procedure Requirements
   2.5     Installation Procedure Requirements

          The following sections discuss various requirements
          for installing the MUXserver 100 software.

          ___________________________
   2.5.1   Time
   2.5.1   Time
   2.5.1   Time
          The installation takes approximately 5 to 15 minutes,
          depending on your type of media and your system
          configuration.

          Installing the MUXserver 100 software and running
          the IVP on a standalone MicroVAX II system takes 10
          minutes.

          ___________________________
   2.5.2   Privileges
   2.5.2   Privileges
   2.5.2   Privileges

          To install the MUXserver 100 software, you must be
          logged in to an account that has SETPRV or at least
          the following privileges:
          o  CMKRNL

          o  WORLD
          o  SYSPRV

          Note that VMSINSTAL turns off BYPASS privilege at the
          start of the installation.









                                                              2-3
                                                              2-3
                                                              2-3

 

          Preparing to Install the MUXserver 100
          Preparing to Install the MUXserver 100
          Preparing to Install the MUXserver 100



          ___________________________
   2.5.3   Disk Space
   2.5.3   Disk Space
   2.5.3   Disk Space

          Installing the MUXserver 100 software requires a
          certain amount of free disk storage space during
          the installation. Once the MUXserver 100 software is
          installed, less storage space is required. Table 2-1
          summarizes the storage requirements:

          Table 2-1 Disk Space Requirements
          Table 2-1 Disk Space Requirements
          Table 2-1 Disk Space Requirements
          _______________________________________________________
                           Blocks During         Blocks After
                           Blocks During         Blocks After
                           Blocks During         Blocks After
          _______________________________________________________
          Kit              Installation          Installation
          Kit              Installation          Installation
          Kit              Installation          Installation
          MUXserver 100    750                   400
          Version 2.3
          _______________________________________________________
          To determine the number of free disk blocks on the
          current system disk, enter the following command at
          the DCL prompt:

               $ SHOW DEVICE SYS$SYSDEVICE





















          2-4
          2-4
          2-4

 

                           Preparing to Install the MUXserver 100
                           Preparing to Install the MUXserver 100
                           Preparing to Install the MUXserver 100



          ___________________________
   2.5.4   VMSINSTAL Requirements
   2.5.4   VMSINSTAL Requirements
   2.5.4   VMSINSTAL Requirements

          When you invoke VMSINSTAL, it checks the following:
          o  Whether you have set your default device and
             directory to SYS$UPDATE

          o  Whether you are logged in to a privileged account
          o  Whether you have adequate quotas for installation

          o  Whether DECnet is running
          o  Whether any users are logged in to the system

          Note that the VMSINSTAL requires that the installation
          account have a minimum of the following quotas:

             ASTLM = 24
             BIOLM = 18
             BYTLM = 18,000
             DIOLM = 18
             ENQLM = 30
             FILLM = 20
          If VMSINSTAL detects any problems during the
          installation, it notifies you and asks if you want
          to continue the installation. In some instances, you
          can enter YES to continue. To stop the installation
          process and correct the situation, enter NO or press
          RETURN. Then correct the problem and restart the
          installation.

          ___________________________

   2.5.5   Backing Up Your System Disk
   2.5.5   Backing Up Your System Disk
   2.5.5   Backing Up Your System Disk
          At the beginning of the installation, VMSINSTAL asks
          if you have backed up your system disk. Digital
          recommends that you do a system disk backup before
          installing any software.





                                                              2-5
                                                              2-5
                                                              2-5

 

          Preparing to Install the MUXserver 100
          Preparing to Install the MUXserver 100
          Preparing to Install the MUXserver 100




          Use the backup procedures that are established at
          your site. For details on performing a system disk
          backup, see the section on the Backup Utility in the
          VMS System Management Subkit.





































          2-6
          2-6
          2-6

 






          _______________________________________________________

   3       Installing The MUXserver 100 Software
   3       Installing The MUXserver 100 Software
   3       Installing The MUXserver 100 Software




          This chapter describes how to install the MUXserver
          100 software. Section 3.2 contains a step-by-step
          description of the installation procedure.
          The last section covers postinstallation
          considerations.

          __________________________________________________________________
   3.1     General Information
   3.1     General Information
   3.1     General Information
          This section includes information about the following
          topics:

          o  Accessing release notes
          o  Determining files and logical names added to your
             system

          o  Running the Installation Verification Procedure
             (IVP),
          o  Aborting the installation.

          ___________________________

   3.1.1   Accessing the Online Release Notes
   3.1.1   Accessing the Online Release Notes
   3.1.1   Accessing the Online Release Notes
          The MUXserver 100 software provides online release
          notes. You must specify OPTIONS N when you invoke
          VMSINSTAL to see the question about online release
          notes. This question comes near the beginning of the
          installation.

          You should review the release notes in case they
          contain any information about last minute changes
          in the installation procedure. If you are starting the
          installation over again and have already reviewed the
          release notes, you do not need to specify OPTIONS N.

                                                              3-1
                                                              3-1
                                                              3-1

 

          Installing The MUXserver 100 Software
          Installing The MUXserver 100 Software
          Installing The MUXserver 100 Software




          Once the MUXserver 100 software has been installed,
          the release notes are located in the following file:

               SYS$HELP:MSVA023.RELEASE_NOTES

          ___________________________
   3.1.2   Determining the Files and Logical Names Added to the
   3.1.2   Determining the Files and Logical Names Added to the
   3.1.2   Determining the Files and Logical Names Added to the
          System
          System
          System

          The MUXserver 100 software installation creates some
          files on your system. The following files will be left
          behind by this installation:
                SYS$TEST:MSVA$IVP.COM
                SYS$HELP:MSVA023.RELEASE_NOTES
                SYS$SYSROOT:[DECSERVER]DSVCONFIG.COM
                SYS$SYSROOT:[DECSERVER]DSVCONFIG.DAT
                SYS$SYSROOT:[DECSERVER]MS1601ENG.SYS
                SYS$SYSROOT:[DECSERVER]MSVA$CONVERT_CONFIG.COM
                SYS$SYSROOT:[DECSERVER]MSVA_020_DEFAULTS.COM

          In addition, system logicals must be defined after
          VMSINSTAL completes. See section 4.1 for the logical
          names and their definitions.

          ___________________________
   3.1.3   Running the Installation Verification Procedure (IVP)
   3.1.3   Running the Installation Verification Procedure (IVP)
   3.1.3   Running the Installation Verification Procedure (IVP)

          The Installation Verification Procedure (IVP) for the
          MUXserver 100 verifies the installation. During the
          installation, you are asked if you want to run the
          IVP as part of the installation. If you respond YES,
          VMSINSTAL runs the IVP. It is recommended that you run
          the IVP to make sure that the MUXserver 100 software
          is installed correctly.
          After the MUXserver 100 software is installed, you can
          run the IVP independently to verify that the software
          is available on your system. You might need to run the
          IVP after a system failure to make sure that users can
          access MUXserver 100.


          3-2
          3-2
          3-2

 

                           Installing The MUXserver 100 Software
                           Installing The MUXserver 100 Software
                           Installing The MUXserver 100 Software




          To run the IVP independently, execute the command file
          MSVA$IVP in the directory SYS$TEST:

               $ @SYS$TEST:MSVA$IVP

          ___________________________
   3.1.4   Aborting the Installation
   3.1.4   Aborting the Installation
   3.1.4   Aborting the Installation

          To abort the installation procedure at any time,
          press CTRL/Y. When you press CTRL/Y, the installation
          procedure deletes all files it has created up to that
          point and exits. You can then start the installation
          again.
          __________________________________________________________________
   3.2     The Installation Procedure
   3.2     The Installation Procedure
   3.2     The Installation Procedure

          The MUXserver 100 installation procedure consists of a
          series of questions and informational messages.

          ___________________________
   3.2.1   Invoking VMSINSTAL
   3.2.1   Invoking VMSINSTAL
   3.2.1   Invoking VMSINSTAL
          To start the installation, invoke the VMSINSTAL
          command procedure from a privileged account, such
          as the SYSTEM account. VMSINSTAL is in the SYS$UPDATE
          directory. You use the following syntax to invoke
          VMSINSTAL:

                           @SYS$UPDATE:VMSINSTAL saveset-name device-name OPTIONS N
          saveset-name
          saveset-name
          saveset-name
          The installation name for the component. For the
          MUXserver 100, use the following installation name:

               MSVA023

          device-name
          device-name
          device-name
          The name of the device on which you plan to mount the
          media. For example, MTA0: is the device name for a
          tape drive. It is not necessary to use the console
          drive for this installation. However, if you do use


                                                              3-3
                                                              3-3
                                                              3-3

 

          Installing The MUXserver 100 Software
          Installing The MUXserver 100 Software
          Installing The MUXserver 100 Software




          the console drive, you should replace any media you
          removed once the installation is complete.

          OPTIONS N
          OPTIONS N
          OPTIONS N
          An optional parameter that indicates you want to see
          the release notes question. If you do not include the
          OPTIONS N parameter, VMSINSTAL does not ask you about
          the release notes. You should review the release notes
          before proceeding with the installation in case they
          contain new information about the installation.
          Note that there are several other options you can
          select when you invoke VMSINSTAL. See the VMS
          documentation on software installation in the VMS
          System Management Subkit for information on these
          options. If you specify more than one option, separate
          the options with commas (OPTIONS A,N).
          The following example invokes VMSINSTAL to install
          MUXserver 100 from tape drive MTA0: and shows the
          system response. This example uses the OPTIONS N
          release note parameter.

               $ @SYS$UPDATE:VMSINSTAL MSVA023 MTA0: OPTIONS N

                     VAX/VMS Software Product Installation Procedure V5.2


               It is 10-SEP-1989 at 13:40.
               Enter a question mark (?) at any time for help.
          If you do not supply either the product name or
          the device name, VMSINSTAL prompts you for this
          information later in the installation procedure.

          ___________________________

   3.2.2   Installation Questions
   3.2.2   Installation Questions
   3.2.2   Installation Questions
          This section discusses the questions that appear
          during the installation. Appendix A contains a sample
          installation procedure showing how the questions can
          be answered.


          3-4
          3-4
          3-4

 

                           Installing The MUXserver 100 Software
                           Installing The MUXserver 100 Software
                           Installing The MUXserver 100 Software




          Each question in the installation is marked with
          an asterisk (*) at the beginning of the line. Some
          questions show the default response in brackets, for
          example [YES]. To use the default response, press the
          RETURN key.

          1
          1
          1
             DECnet status
             VMSINSTAL notifies you if DECnet is running and
             displays a list of all active processes. It then
             asks if you want to continue the installation. If
             you are installing on VMS Version 5.2 or higher,
             VMSINSTAL does not check the DECnet status. You can
             install the MUXserver 100 while DECnet is up and
             running.

                  %VMSINSTAL-W-DECNET, Your DECnet network is up and running.
                     .
                     .
                     .
                  * Do you want to continue anyway [NO]?


          2
          2
          2
             System backup
             VMSINSTAL asks if you are satisfied with your
             system backup. You should always back up your
             system disk before performing an installation.
             If you are satisfied with the backup of your
             system disk, press RETURN. Otherwise, enter NO
             to discontinue the installation. After you back up
             your system disk, you can restart the installation.

                  * Are you satisfied with the backup of your system disk [YES]?

          3
          3
          3
             Mounting the media
             You should now mount the first distribution volume
             on the device you specified when you invoked
             VMSINSTAL. The device name appears in the line
             preceding the question. VMSINSTAL then asks you if
             you are ready to continue with the installation.


                                                              3-5
                                                              3-5
                                                              3-5

 

          Installing The MUXserver 100 Software
          Installing The MUXserver 100 Software
          Installing The MUXserver 100 Software




             If you respond YES to indicate that you are ready,
             VMSINSTAL displays a message that the media
             containing the MUXserver 100 has been mounted on
             the specified device and that the installation has
             begun. For example:

                  Please mount the first volume of the set on MTA0:.
                  * Are you ready? YES
                  %MOUNT-I-MOUNTED, MUXserver 100 MOUNTED ON _$$MTA0:  (NODE 1)
                  The following products will be processed:
                    MUXserver 100 V2.3

                      Beginning installation of MUXserver 100 V2.3 at 20:01

                  %VMSINSTAL-I-RESTORE, Restoring product saveset A...
             If you entered the wrong device name when you
             invoked VMSINSTAL and need to restart the
             installation, enter NO in response to the "Are
             you ready?" question. To abort the installation for
             other reasons, press CTRL/Y.

          4
          4
          4
             Additional media volumes
             If your installation kit contains more than
             one volume, VMSINSTAL prompts you to mount the
             additional volumes and then asks you to indicate
             that you are ready for the installation to proceed.

                  %BACKUP-I-READYREAD, mount volume 2 on _MTA0: for reading

                  Enter "YES" when ready:
          5
          5
          5
             Release Notes

             If you specified OPTIONS N when you started the
             installation, VMSINSTAL asks a release notes
             question. You have five options for handling the
             release notes under VMS Versions 5.0 and 5.1. There
             are only four options under VMS Version 5.2 or
             higher.



          3-6
          3-6
          3-6

 

                           Installing The MUXserver 100 Software
                           Installing The MUXserver 100 Software
                           Installing The MUXserver 100 Software




             For VMS Versions 5.0 and 5.1, you see the following
             display:

                  Release Notes Options:

                   1.  Display release notes
                   2.  Print release notes
                   3.  Both 1 and 2
                   4.  Copy release notes to SYS$HELP
                   5.  Do not display, print or copy release notes

                  * Select option [2]:
             For VMS Version 5.2 or higher the display is as
             follows:

                  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]:

             If you select option 1, VMSINSTAL displays the
             release notes immediately on the console terminal.
             You can terminate the display at any time by
             pressing CTRL/C.
             If you select option 2, VMSINSTAL prompts you for
             the name of the print queue that you want to use:

                  * Queue name [SYS$PRINT]:

             You can press RETURN to send the file to the
             default output print device or you can enter
             another queue name.



                                                              3-7
                                                              3-7
                                                              3-7

 

          Installing The MUXserver 100 Software
          Installing The MUXserver 100 Software
          Installing The MUXserver 100 Software




             If you select option 3, VMSINSTAL displays the
             release notes immediately on the console terminal
             and then prompts you for a queue name for the
             printed version.

             Option 4 under VMS Versions 5.0 and 5.1 causes
             the installation to copy the release notes to the
             help directory. Even if you do not select the VMS
             Version 5.0 or 5.1 option 4, the release notes
             for the MUXserver 100 are copied to the SYS$HELP
             directory. Under VMS V5.2 or higher, release notes
             are always copied to SYS$HELP.
             VMSINSTAL automatically copies the MUXserver 100
             release notes to the the system help directory. The
             file specification is:

                  SYS$HELP:file-spec
             Select option 4 (VMS Version 5.2 or higher)
             or option 5 (VMS Version 5.0 or 5.1) if you
             have already reviewed the release notes and are
             restarting the installation.

          6
          6
          6
             Continuing the installation
             The installation procedure now asks if you want
             to continue the installation. To continue, enter
             YES. Otherwise, press RETURN. In either case, the
             release notes are copied to a file in the SYS$HELP
             directory. For example:

                  * Do you want to continue the installation [N]?: YES
                  %VMSINSTAL-I-RELMOVED, The product's release notes have been
                                                     successfully moved to SYS$HELP.

             The release notes are located in the following
             file:

                  SYS$HELP:MSVA023.RELEASE_NOTES
             Note: The name of the release notes file installed
             Note: The name of the release notes file installed
             Note: The name of the release notes file installed
             by VMSINSTAL consists of the current product name
             by VMSINSTAL consists of the current product name
             by VMSINSTAL consists of the current product name


          3-8
          3-8
          3-8

 

                           Installing The MUXserver 100 Software
                           Installing The MUXserver 100 Software
                           Installing The MUXserver 100 Software




             and version number. Do not delete release notes for
             and version number. Do not delete release notes for
             and version number. Do not delete release notes for
             previous versions of the MUXserver 100 software.
             previous versions of the MUXserver 100 software.
             previous versions of the MUXserver 100 software.

          7
          7
          7
             Choosing to purge files
             You have the option to purge files from previous
             versions of MUXserver 100 that are superseded by
             this installation. Purging is recommended; however,
             if you need to keep files from the previous
             version, enter NO in response to the question.

                  * Do you want to purge files replaced by this installation [YES]?
          8
          8
          8
             Choosing to run the Installation Verification
             Procedure (IVP)

             The installation procedure now asks if you want to
             run the Installation Verification Procedure. The
             IVP for MUXserver 100 checks to be sure that the
             installation is successful. It is recommended that
             you run the IVP.

                  * Do you want to run the IVP after the installation [YES]?

          ___________________________
   3.2.3   Informational Messages
   3.2.3   Informational Messages
   3.2.3   Informational Messages
          At this point, the installation procedure displays a
          number of informational messages that report on the
          progress of the installation. There are no further
          questions. If the installation procedure has been
          successful up to this point, VMSINSTAL moves the new
          or modified files to their target directories, updates
          help files, and updates DCL tables, if necessary. If
          you chose to have files purged, that work is done now.
          The following message is displayed:

               %VMSINSTAL-I-MOVEFILES, files will now be moved to their target
                                                  directories...





                                                              3-9
                                                              3-9
                                                              3-9

 

          Installing The MUXserver 100 Software
          Installing The MUXserver 100 Software
          Installing The MUXserver 100 Software



          ___________________________
   3.2.4   Running the Installation Verification Procedure
   3.2.4   Running the Installation Verification Procedure
   3.2.4   Running the Installation Verification Procedure

          If you chose to run the IVP, VMSINSTAL runs it now.
          When the IVP runs successfully, you see the following
          display:

                  MUXserver 100 V2.3 Installation Succeeded

          ___________________________
   3.2.5   Completing the Installation Procedure
   3.2.5   Completing the Installation Procedure
   3.2.5   Completing the Installation Procedure

          The following messages indicate that the entire
          installation procedure is complete:

                  Installation of MSVA V2.3 completed at 13:40

                  VMSINSTAL procedure done at 13:40
          You can now log out of the privileged account:

               $ LOGOUT
               SYSTEM     logged out at 10-SEP-1989 13:40:50.01
          Note that VMSINSTAL deletes or changes entries in
          the process symbol tables during the installation.
          Therefore, if you are going to continue using the
          system manager's account and you want to restore these
          symbols, you should log out and log in again.



          __________________________________________________________________
   3.3     Error Recovery
   3.3     Error Recovery
   3.3     Error Recovery

          If errors occur during the installation itself or
          when the IVP is running, VMSINSTAL displays failure
          messages. If the installation fails, you see the
          following message:





          3-10
          3-10
          3-10

 

                           Installing The MUXserver 100 Software
                           Installing The MUXserver 100 Software
                           Installing The MUXserver 100 Software




               ****************************************************
               *                                                  *
               *      MUXserver 100 V2.3 Installation Failed      *
               *                                                  *
               ****************************************************

          If the IVP fails, you see these messages:
               The MSVA V3.2 Installation Verification Procedure failed.

               %VMSINSTAL-E-IVPFAIL, The IVP for MSVA V2.3 has failed.
          Errors can occur during the installation if any of the
          following conditions exist:

          o  The operating system version is incorrect.
          o  Files are missing from the kit.

          For descriptions of the error messages generated
          by these conditions, see the VMS documentation on
          system messages, recovery procedures, and VMS software
          installation. If you are notified that any of these
          conditions exist, you should take the appropriate
          action as described in the message. (You might need to
          change a system parameter or increase an authorized
          quota value.) For information on installation
          requirements, see Chapter 2.
















                                                             3-11
                                                             3-11
                                                             3-11

 






          _______________________________________________________

   4       After Installing the MUXserver 100 Software
   4       After Installing the MUXserver 100 Software
   4       After Installing the MUXserver 100 Software




          After installing the MUXserver 100 software, you need
          to perform the following tasks:
          o  Edit the system startup.

          o  Configure your MUXserver 100

          __________________________________________________________________
   4.1     Editing the System Files
   4.1     Editing the System Files
   4.1     Editing the System Files

          The logicals MOM$LOAD, MOM$SYSTEM, and MOM$SYSTEM_
          SOFTID have to be defined on each load host for the
          MUXserver 100. They should be defined as follows:


               $  ASSIGN/SYSTEM/EXECUTIVE_MODE 'current-search-string', -
                     SYS$SYSROOT:[DECSERVER] MOM$LOAD
               $  ASSIGN/SYSTEM/EXECUTIVE_MODE SYS$SYSROOT:[MOM$SYSTEM] MOM$SYSTEM
               $  ASSIGN/SYSTEM/EXECUTIVE_MODE MOM$SYSTEM, MOM$LOAD MOM$SYSTEM_SOFTID
          These logical definitions should be placed in
          the system startup file (SYS$MANAGER:SYSTARTUP_
          V5.COM) or the system network startup command file
          (SYS$MANAGER:STARTNET.COM) so that they will be
          defined with each reboot of the load host or with each
          restart of the network.










                                                              4-1
                                                              4-1
                                                              4-1

 

          After Installing the MUXserver 100 Software
          After Installing the MUXserver 100 Software
          After Installing the MUXserver 100 Software



          __________________________________________________________________
   4.2     VAXcluster Considerations
   4.2     VAXcluster Considerations
   4.2     VAXcluster Considerations

          To install the server distribution software onto an
          alternate load host that is a member of a VAXcluster,
          install the software unto one cluster member, and
          then:
          1
          1
          1
             Log into a privileged (system) account on one of
             the other members of the cluster.

          2
          2
          2
             Enter the following commands:

                       $ CREATE/DIRECTORY SYS$SPECIFIC:[DECSERVER]_
                       /PROTECTION=(S:RWED,O:RWED) <RET>
                       ASSIGN/SYSTEM/EXECUTIVE_MODE ' current-search-string', -
                          SYS$SYSROOT:[DECSERVER] MOM$LOAD

                       $ ASSIGN/SYSTEM/EXECUTIVE_MODE SYS$SYSROOT:[MOM$SYSTEM]
                           MOMSYSTEM
                       $ ASSIGN/SYSTEM/EXECUTIVE_MODE MOM$SYSTEM, MOM$LOAD
                           MOM$SYSTEM_SOFTID

          3
          3
          3
             Include the second command from step 2 in the
             node's system start-up procedures.

          __________________________________________________________________
   4.3     User Account Requirements
   4.3     User Account Requirements
   4.3     User Account Requirements
          To work with the MUXserver 100, user accounts on
          your system must have certain privileges and quotas.
          The next two sections contain information on these
          requirements. The third section discusses how to set
          up user accounts.

          ___________________________

   4.3.1   Privileges
   4.3.1   Privileges
   4.3.1   Privileges
          To use the MUXserver 100, each account must have at
          least the TMPMBX and NETMBX privileges. Use the VMS
          Authorize Utility to determine whether users have the
          privileges they require.


          4-2
          4-2
          4-2

 

                      After Installing the MUXserver 100 Software
                      After Installing the MUXserver 100 Software
                      After Installing the MUXserver 100 Software



          __________________________________________________________________
   4.4     Determining and Reporting Problems
   4.4     Determining and Reporting Problems
   4.4     Determining and Reporting Problems

          If you encounter a problem while using the MUXserver
          100, report it to Digital. Depending on the nature of
          the problem and the type of support you have, you can
          take one of the following actions:
          o  Call Digital if your software contract or warranty
             agreement entitles you to telephone support.

          o  Submit a Software Performance Report (SPR).
          o  Fill out and submit a Reader's Comments form if
             the problem has to do with the the MUXserver 100
             documentation. There are Reader's Comments forms
             at the back of each manual. Use the form from the
             manual in which you found the error. Include the
             section and page number.

          Review the Software Product Description (SPD) and
          Warranty Addendum for an explanation of warranty.
          If you encounter a problem during the warranty
          period, report the problem as indicated above or
          follow alternate instructions provided by Digital for
          reporting SPD nonconformance problems.

          See the release notes for the MUXserver 100 for
          information on how to submit an SPR.















                                                              4-3
                                                              4-3
                                                              4-3

 






          _______________________________________________________

   5       Configuring the Load Host's Node Database
   5       Configuring the Load Host's Node Database
   5       Configuring the Load Host's Node Database




          This chapter describes the procedure you follow to
          configure a load host's node database to support
          specific servers. You must configure this database
          before you can down-line load the server image to any
          server.
          Use DSVCONFIG.COM, an automated, menu-driven
          procedure, to define servers in the load host's node
          database. With DSVCONFIG, you can define, delete, and
          modify entries.

          The installation procedure (see Chapter 3) copies
          this procedure file to the SYS$SYSROOT:[DECSERVER]
          directory for both single systems and for VAXcluster
          member nodes.
          With DSVCONFIG, you can:

          o  List servers that are currently defined in the load
             host's node database.
          o  Add an entry for a new server in the load host's
             node database.

             Adding an entry supplies information that
             identifies the server on the Ethernet.
          o  Swap an existing server for a new one, or redefine
             an existing server's identification in the load
             host's node database.

             Swapping retains the DECnet node address of an
             existing server, replacing its Ethernet address
             with the Ethernet address of a new unit. This
             option also can replace other server identifiers,
             either for a new server or for an existing one.


                                                              5-1
                                                              5-1
                                                              5-1

 

          Configuring the Load Host's Node Database
          Configuring the Load Host's Node Database
          Configuring the Load Host's Node Database




          o  Delete an entry for an existing server from the
             load host's node database.

             Deleting an entry prevents the load host from
             recognizing the server. Thus, it is no longer
             a load host for that server. You can delete a
             database entry when you reconfigure the network
             or assign a server to another load host.
          o  Restore existing servers to your DECnet load
             database.

             Restoring copies server entries from the load
             host's node database to the DECnet load database.
             Restoring is useful when you routinely copy
             your local DECnet database from a central DECnet
             database and that central database does not include
             servers.
          The functions of adding, swapping, and deleting
          entries in the DSVCONFIG.DAT file is what is meant
          by configuration of the load host's node database. In
          addition, the function of restoring reconfigures the
          DECnet load database. In fact, the DSVCONFIG procedure
          operates on two distinct databases:

          1
          1
          1
             The load host's node database. This database
             is also the server database. It contains the
             information you see when you select Option 1, List,
             from the DSVCONFIG menu.
          2
          2
          2
             The DECnet load database. DSVCONFIG operates
             on both the volatile and the permanent DECnet
             databases.

          When you run DSVCONFIG, data is sometimes transferred
          from the load host's node database to the DECnet
          database. It is important that these two databases
          remain synchronized. The DSVCONFIG procedure
          automatically keeps these databases in sync. Even
          though DSVCONFIG includes several NCP commands, do not
          execute these commands directly yourself in order to


          5-2
          5-2
          5-2

 

                        Configuring the Load Host's Node Database
                        Configuring the Load Host's Node Database
                        Configuring the Load Host's Node Database




          configure the load host's node database because NCP
          affects only the DECnet database.

          DSVCONFIG also prepares your node as a load host by
          enabling SERVICE on the service circuit. SERVICE must
          be enabled before a down-line load can occur.
          __________________________________________________________________
   5.1     PREPARING TO RUN THE CONFIGURATION PROCEDURE
   5.1     PREPARING TO RUN THE CONFIGURATION PROCEDURE
   5.1     PREPARING TO RUN THE CONFIGURATION PROCEDURE

          Before beginning the configuration procedure, check
          that:
          1
          1
          1
             DECnet Phase IV is running. For information
             on DECnet Phase IV, see the DECnet-VAX Network
             Management Concepts and Procedures Manual.

          2
          2
          2
             There is a unique DECnet node name and node address
             for each server. To find out the node name and
             the node address and to determine that they are
             unique, ask your network manager or the person
             whose responsibility it is to assign node names and
             node addresses. You can also determine uniqueness
             with the NCP SHOW NODE command.
          3
          3
          3
             You know the Ethernet address of each server.

             This is the unique hardware address of each
             server. The Ethernet address is recorded on the
             control/indicator panel of the MUXserver 100 and
             on the Identification Card for that server that you
             get from the hardware installer.
          4
          4
          4
             The directory SYS$SPECIFIC:[DECSERVER] exists, for
             VAXcluster nodes. If not, create this directory
             now.

          You will need the preceding information to answer
          prompts during DSVCONFIG.






                                                              5-3
                                                              5-3
                                                              5-3

 

          Configuring the Load Host's Node Database
          Configuring the Load Host's Node Database
          Configuring the Load Host's Node Database



          __________________________________________________________________
   5.2     DSVCONFIG CONVENTIONS AND REQUIREMENTS
   5.2     DSVCONFIG CONVENTIONS AND REQUIREMENTS
   5.2     DSVCONFIG CONVENTIONS AND REQUIREMENTS

          DSVCONFIG is an interactive procedure. When you run
          DSVCONFIG, a menu of options is displayed. Enter a
          menu number and press <RET> to activate the option you
          want. After each query, you can get help by pressing
          the question mark (?). When you finish an option, the
          program returns you to the DSVCONFIG menu.
          If you want to exit an option without making any
          changes, enter CTRL/Z. You are returned to the
          DSVCONFIG menu. At the menu level, type CTRL/Z to exit
          DSVCONFIG and return to the $ prompt.

          At the end of the Add, Delete, and Swap options, you
          may get NCP messages (information, confirmations, and
          errors). In the case of error messages, the operation
          may not have been successful. For the meanings of
          these messages, see the VAX/VMS System Messages and
          Recovery Procedures Reference Manual.
          To run DSVCONFIG on a single system, the distribution
          software must already be installed onto that system.
          For a VAXcluster node, the distribution software
          can be installed onto any node of the cluster, not
          necessarily the node where you run the procedure.



          __________________________________________________________________
   5.3     INSTALLATION PROCEDURES
   5.3     INSTALLATION PROCEDURES
   5.3     INSTALLATION PROCEDURES

          The configuration procedure DSVCONFIG.COM, used
          for configuring your load host database, replaces
          MSVACONFIG.COM which was used in releases prior to
          V2.3 of the MUXserver 100 software. The data file
          associated with MSVACONFIG.COM, MSVA$CONFIG.DAT, may
          have to be modified.





          5-4
          5-4
          5-4

 

                        Configuring the Load Host's Node Database
                        Configuring the Load Host's Node Database
                        Configuring the Load Host's Node Database



          __________________________________________________________________
   5.4     IMPLEMENTING DSVCONFIG.COM
   5.4     IMPLEMENTING DSVCONFIG.COM
   5.4     IMPLEMENTING DSVCONFIG.COM

          Log into the system account or any account with OPER
          and SYSPRV privileges. Enter the following commands:

                $ SET DEFAULT SYS$SYSROOT:[DECSERVER] <RET>
                $ @DSVCONFIG <RET>
          DSVCONFIG determines whether DECnet is running and if
          NCP is installed. If DECnet is down or NCP is missing,
          DSVCONFIG prints a warning and halts the procedure.

          If you receive a warning, exit DSVCONFIG and correct
          the problem. Then, run the procedure again, select the
          option that generated the warning, and repeat the last
          entry.
          __________________________________________________________________
   5.5     DATA FILES
   5.5     DATA FILES
   5.5     DATA FILES

          The next thing the procedure checks is the existence
          and format of a data file called DSVCONFIG.DAT. It
          finds one of two situations and continues accordingly:
          o  The directory SYS$SYSROOT:[DECSERVER] already
             has the file DSVCONFIG.DAT if DSVCONFIG.COM was
             previously used to add server entries in this
             load host's node database. The file is formatted
             correctly so the procedure simply continues with
             its next task.

          o  The DSVCONFIG.DAT file does not exist in the
             directory SYS$SYSROOT:[DECSERVER]. The DSVCONFIG
             procedure now creates DSVCONFIG.DAT.
             If DSVCONFIG.DAT has to be created, you see this
             message:

                          The database file, DSVCONFIG.DAT could not be found,
                          a new one will be created for you.





                                                              5-5
                                                              5-5
                                                              5-5

 

          Configuring the Load Host's Node Database
          Configuring the Load Host's Node Database
          Configuring the Load Host's Node Database



          ___________________________
   5.5.1   REFORMATTING MSVA$CONFIG.DAT
   5.5.1   REFORMATTING MSVA$CONFIG.DAT
   5.5.1   REFORMATTING MSVA$CONFIG.DAT

          If you have an existing
          SYS$SYSROOT:[DECSERVER]MSVA$CONFIG.DAT file, you will
          need to reformat it by entering the command:

                        $ @SYS$SYSROOT:[DECSERVER]MSVA$CONVERT_CONFIG.COM
          The MSVA$CONFIG.DAT currently in use will be
          reformatted, and merged with the new DSVCONFIG.DAT
          file.

          Because it is now possible to utilize various Ethernet
          controllers on your VAX systems, the DSVCONFIG
          configuration procedure may prompt you to enter
          the DECnet service circuit-id for the MUXserver
          100 units you will be adding or swapping in the
          configuration. If DSVCONFIG.DAT or MSVA$CONFIG.DAT has
          to be reformatted, or neither exists, you are asked
          for a service circuit-ID:
                   The database file DSVCONFIG.DAT must be reformatted for common server
                   use. Enter the service circuit-ID for all existing DECservers, ? for
                   help or enter CTRL/Z to exit this procedure:

          Specify one service circuit-ID for all existing
          MUXserver 100s. The default service circuit-ID depends
          on the default Ethernet controller type for your
          processor type:

                       o UNA-n for DEUNA or DELUA.
                       o QNA-n for DEQNA.
                       o BNT-n for DEBNT
                       o BNA-n for DEBNA
                       o SVA-n for VAXstation 2000
          Here 'n', is an integer (typically 0 or 1).

          After you specify the service circuit-ID for existing
          MUXserver 100s and press <RET>, you see these two
          messages:



          5-6
          5-6
          5-6

 

                        Configuring the Load Host's Node Database
                        Configuring the Load Host's Node Database
                        Configuring the Load Host's Node Database




                Your DECserver database is being converted, please wait...

                The DECserver database conversion is now complete...
          If DSVCONFIG.DAT already exists with the correct
          format, the procedure continues.

          Once the data file you need exists in the correct
          format, the procedure proceeds by informing you that
          each server must have a unique DECnet node name and
          DECnet node address and then DSVCONFIG asks you either
          to continue or to exit.
          __________________________________________________________________
   5.6     ADDING A MUXserver 100
   5.6     ADDING A MUXserver 100
   5.6     ADDING A MUXserver 100

          Because it is now possible to utilize various Ethernet
          controllers on your VAX systems, the DSVCONFIG
          configuration procedure has been enhanced to prompt
          for the server type and DECnet service circuit-id when
          you wish to configure a new server. Select option 2
          from the main menu and press <RET> to create a new
          entry in the load host's node database for a new
          server. When defining a new entry, you must supply:
                    1.  The server type.
                    2.  A unique DECnet node name for the DECserver.
                    3.  A unique DECnet node address for the DECserver.
                    4.  The Ethernet address of the DECserver.
                    5.  The service circuit-ID.

          Five prompts ask you for this information:

                         DECserver type?
          Specify the type of server you are adding:

                         DS100 to add a DECserver 100.
                         DS200 to add a DECserver 200.
                         DS300 to add a DECserver 300.
                         MS100 to add a MUXserver 100.
                         MS300 to add a MUXserver 300.

                         DECnet node name for unit?

                                                              5-7
                                                              5-7
                                                              5-7

 

          Configuring the Load Host's Node Database
          Configuring the Load Host's Node Database
          Configuring the Load Host's Node Database




          Specify the DECnet node name for the server. This node
          name must begin with a letter and contain from 1 to
          6 alphanumeric characters; the name must be unique to
          your entire DECnet network.

                         DECnet address for unit?
          Specify the DECnet node address for the server. This
          number must be a decimal number from 2 to 1023, unique
          within the network.

          Your DECnet network may be divided into areas. If this
          is the case, find out, from your network manager, your
          area number because this number becomes part of each
          node address. With defined areas, each node address
          takes the form aa.nnnn. Here, aa is a decimal number
          from 2 to 63, the period distinguishes area from node
          address, and nnnn is the node address (for example,
          7.103). If you omit the area, the area of the current
          load host is used as a default.

                         DECserver Ethernet address of this unit?
          Specify the Ethernet address of the server. This
          address is listed on the control/indicator panel
          of the unit and on the Identification Card for that
          server that you get from the hardware installer.
          Enter the Ethernet address as six pairs of hexadecimal
          digits, with hyphens (-) separating the pairs (for
          example, 08-00-01-00-AB-CD is a valid format).

                         DECnet Service Circuit-ID [ ]?

          Specify the service circuit-ID of your Ethernet
          controller type:

                        o UNA-n for DEUNA or DELUA.
                        o QNA-n for DEQNA.

                        o BNT-n for DEBNT
                        o BNA-n for DEBNA


          5-8
          5-8
          5-8

 

                        Configuring the Load Host's Node Database
                        Configuring the Load Host's Node Database
                        Configuring the Load Host's Node Database




                        o SVA-n for VAXstation 2000

          Here, n is an integer (typically 0 or 1).
          Whenever you run this procedure, you may be asked
          to specify the service circuit-ID several times. The
          first time you are asked, the default will be the
          service circuit-ID for the processor type of your VMS
          load host. If you respond by specifying a different
          service circuit-ID, that response becomes the new
          default.

          The possible values are:
                         CPU Type                               Service Circuit-ID

                         VAX-11/780, 782, 785                   UNA-0
                         VAX-11/725, 730                        UNA-0
                         VAX 8600, 8650                         UNA-0
                         VAX 8200, 8300, 8500, 8800             UNA-0 or BNA-0
                         VAX 6000 series                        BNA-0
                         MicroVAX II                            QNA-0
                         MicroVAX 2000                          SVA-0
          If your CPU supports more than one Ethernet
          controller, the service circuit-ID number may be
          something other than zero.

          After you specify the service circuit-ID and press
          <RET>, DSVCONFIG adds the entry for the new server to
          the database and sets SERVICE ENABLED on the circuit
          supporting the Ethernet controller, both of which are
          necessary in order for the load host to down-line load
          the server image to the server.










                                                              5-9
                                                              5-9
                                                              5-9

 

          Configuring the Load Host's Node Database
          Configuring the Load Host's Node Database
          Configuring the Load Host's Node Database




          Note: If you get an error from DECnet while you
          Note: If you get an error from DECnet while you
          Note: If you get an error from DECnet while you
          are adding a server, the entry is added to the
          are adding a server, the entry is added to the
          are adding a server, the entry is added to the
          DSVCONFIG.DAT file (the load host's node database),
          DSVCONFIG.DAT file (the load host's node database),
          DSVCONFIG.DAT file (the load host's node database),
          even though it is not entered in the DECnet load
          even though it is not entered in the DECnet load
          even though it is not entered in the DECnet load
          database. You should immediately use Option 4 to
          database. You should immediately use Option 4 to
          database. You should immediately use Option 4 to
          delete the entry, fix the condition causing the DECnet
          delete the entry, fix the condition causing the DECnet
          delete the entry, fix the condition causing the DECnet
          error, then return to Option 2 to add the server
          error, then return to Option 2 to add the server
          error, then return to Option 2 to add the server
          again. If you specify a node address that is already
          again. If you specify a node address that is already
          again. If you specify a node address that is already
          defined in the server database (the load host's node
          defined in the server database (the load host's node
          defined in the server database (the load host's node
          database), you get a DSVCONFIG error, nothing is
          database), you get a DSVCONFIG error, nothing is
          database), you get a DSVCONFIG error, nothing is
          added, and the Add option is terminated.
          added, and the Add option is terminated.
          added, and the Add option is terminated.

          __________________________________________________________________
   5.7     SWAPPING AN EXISTING MUXserver 100
   5.7     SWAPPING AN EXISTING MUXserver 100
   5.7     SWAPPING AN EXISTING MUXserver 100

          Because of the availability of the DECserver 200, the
          DSVCONFIG configuration procedure has been enhanced
          so you may now use Option 3 (SWAP) to swap between
          DECserver types. For example, you may swap a DECserver
          200 for a DECserver 100. You may also use the swap
          option to simply change the DECnet node name and/or
          DECnet service circuit for the unit.
          Type the number three and press <RET> to swap an
          existing server with a new unit. Swapping retains the
          DECnet node address of the original unit.

          Swapping is useful if an existing unit malfunctions
          and you need to replace it. Swapping is also helpful
          for renaming servers. DSVCONFIG lets you specify all
          of these characteristics for the new unit:
          Characteristic Defaults:

                              DECserver Type:  The type of the old DECserver you
                                               are replacing.

                              DECnet node name:  The name of the old DECserver you
                                                 are replacing.
                              Ethernet address:  There is no default. You must specify
                                                 the Ethernet address of the new unit.


          5-10
          5-10
          5-10

 

                        Configuring the Load Host's Node Database
                        Configuring the Load Host's Node Database
                        Configuring the Load Host's Node Database




                              DECnet service circuit-ID:  The service circuit-ID of the old
                                                          DECserver you are replacing.

          First, you are prompted for the node name:
                              What is the DECnet node name you want to swap?

          Specify the node name of the existing DECserver that
          you want to replace. DSVCONFIG responds by displaying
          the Ethernet address of the old unit and then asks
          four questions:

                    DECserver at Ethernet Address nn-nn-nn-nn-nn-nn is being swapped. Enter
                    the new Ethernet address, and any other changed characteristics.
                              DECserver type [default-type]?

          Type <RET> if you are replacing a DECserver 100 with a
          DECserver 100 or a DECserver 200 with a DECserver 200,
          or a MUXserver 100 with a MUXserver 100. If you are
          changing DECserver types, specify the type of the new
          unit and press <RET>. Valid responses are:

                    DS100 for a new DECserver 100.
                    DS200 for a new DECserver 200.
                    DS300 for a new DECserver 300.
                    MS100 for a new MUXserver 100.
                    MS300 for a new MUXserver 300.
                              DECnet node name for unit [ ]?

          Type <RET> if you want the replacement MUXserver to
          have the same DECnet node name as the old unit. If you
          are changing node names, specify the node name of the
          new unit and press <RET>. A MUXserver 100 DECnet node
          name must begin with a letter and contain from 1 to
          6 alphanumeric characters; the name must be unique to
          your entire DECnet network.
                         DECserver Ethernet address of this unit?





                                                             5-11
                                                             5-11
                                                             5-11

 

          Configuring the Load Host's Node Database
          Configuring the Load Host's Node Database
          Configuring the Load Host's Node Database




          You must specify the Ethernet address of the
          new MUXserver. This address is shown on the
          control/indicator panel of the unit and on the
          Identification Card for that server that you get from
          the hardware installer. Enter the Ethernet address
          as six pairs of hexadecimal digits, with hyphens (-)
          separating the pairs (for example, 08-00-01-00-AB-CD
          is a valid format). Press <RET>.

                         DECnet Service Circuit-ID [default-id]?
          Type <RET> if the replacement MUXserver has the same
          service circuit-ID as the old unit. If the service
          circuits are different, specify the service circuit-ID
          of the new unit and press <RET>. Valid IDs are:

                     o UNA-n for DEUNA or DELUA.
                     o QNA-n for DEQNA.
                     o BNT-n for DEBNT
                     o BNA-n for DEBNA
                     o SVA-n for VAXstation 2000

          Here, n is an integer (typically 0 or 1). Your answer
          is determined by your system. Possible responses are:

                         CPU Type                        Service Circuit-ID
                     VAX-11/780, 782, 785                      UNA-0
                     VAX-11/725, 730                           UNA-0
                     VAX 8600, 8650                            UNA-0
                     VAX 8200, 8300, 8500, 8800                UNA-0 or BNA-0
                     VAX 6000 Series                           BNA-0
                     MicroVAX II                               QNA-0
                     MicroVAX 2000                             SVA-0

          If your CPU supports more than one Ethernet
          controller, the controller number may be something
          other than zero.





          5-12
          5-12
          5-12

 

                        Configuring the Load Host's Node Database
                        Configuring the Load Host's Node Database
                        Configuring the Load Host's Node Database




          After you specify the service circuit-ID and press
          <RET>, DSVCONFIG swaps the characteristics you just
          specified with the old ones for the the server entry
          with the same DECnet node address (this address cannot
          be swapped).
          __________________________________________________________________

   5.8     RESTORING EXISTING MUXserver 100
   5.8     RESTORING EXISTING MUXserver 100
   5.8     RESTORING EXISTING MUXserver 100
          A change has been made in the DSVCONFIG RESTORE
          option to define the MUXserver 100 units in the DECnet
          permanent database as well as the volatile database.
          This change allows the database to be defined on
          system boot-up without having to reload the permanent
          database from a central node system.



























                                                             5-13
                                                             5-13
                                                             5-13

 






          _______________________________________________________

   A       Sample Installation
   A       Sample Installation
   A       Sample Installation




          This appendix contains a sample installation of the
          MUXserver 100 software. This sample was run on a
          system that had no previous version of the MUXserver
          100 software installed.
          The sample installation assumes that DECnet has been
          shut down, that no users are logged on to your system,
          and that OPTIONS N is specified to print the release
          notes. The Installation Verification Procedure (IVP)
          runs at the end of the installation.

          __________________________________________________________________
   A.1     Full Development Kit
   A.1     Full Development Kit
   A.1     Full Development Kit
          This section contains a sample installation for the
          MUXserver 100 full development kit.



               $ @vmsinstal
               VAX/VMS Software Product Installation Procedure V5.2-43V

               It is 30-AUG-1989 at 16:40.
               Enter a question mark (?) at any time for help.
               * Are you satisfied with the backup of your system disk [YES]?
               * Where will the distribution volumes be mounted: mua0:

               Enter the products to be processed from the first distribution volume set.
               * Products: msva023
               * Enter installation options you wish to use (none):
               The following products will be processed:
                 MSVA V2.3
                Beginning installation of MSVA V2.3 at 16:40



                                                              A-1
                                                              A-1
                                                              A-1

 

          Sample Installation
          Sample Installation
          Sample Installation




               %VMSINSTAL-I-RESTORE, Restoring product saveset A ...
               %VMSINSTAL-I-RELMOVED , The product's release notes have been successfully
                        moved to SYS$HELP.

               * Do you wish to install the new software [YES]?
               * Do you want to purge files replaced by this installation [YES]?
               * Do you want to run the IVP after the installation [YES]?

               %VMSINSTAL-I-RESTORE, Restoring product saveset B ...

               Superseded version of DSVCONFIG.COM exists, file copied as
               [DECSERVER]DSVCONFIG.COM_V11
               %VMSINSTAL-I-MOVEFILES, Files will now be moved to their target directories...

                    Beginning installation verification procedure for MUXserver 100 V2.3.

                Successful creation of SYS$SYSROOT:[DECSERVER] directory
                Successful installation of SYS$SYSROOT:[DECSERVER]MS1601ENG.SYS
                Successful installation of SYS$SYSROOT:[DECSERVER]DSVCONFIG.COM
                Successfully located SYS$SYSROOT:[DECSERVER]DSVCONFIG.DAT
                Successful installation of SYS$SYSROOT:[DECSERVER]MSVA_020_DEFAULTS.COM
                MUXserver 100 V2.3 Installation Verified

               Your installation is now complete.  After exiting from VMSINSTAL, read
               the section on the post-installation procedure in your MUXserver 100
               installation guide.  This will explain how to define the necessary
               load host logicals as well as how to configure your MUXserver 100.

                Installation of MSVA V2.3 completed at 16:42












          A-2
          A-2
          A-2

 






          _______________________________________________________

   B       MUXserver Configurations
   B       MUXserver Configurations
   B       MUXserver Configurations





          __________________________________________________________________
   B.1     EXAMPLE OF A CONFIGURATION: STARTING DSVCONFIG.COM
   B.1     EXAMPLE OF A CONFIGURATION: STARTING DSVCONFIG.COM
   B.1     EXAMPLE OF A CONFIGURATION: STARTING DSVCONFIG.COM

          The following example shows the beginning of the
          configuration procedure. (See Chapter 5 for the
          prompts that are displayed if the procedure has to
          create DSVCONFIG.DAT.)

                   $ SET DEFAULT SYS$SYSROOT:[DECSERVER] <RET>
                   $ @DSVCONFIG <RET>
          You must assign a unique DECnet node name and DECnet
          node address for each MUXserver 100 you are going to
          configure. If, at any time, you specify a node name
          or node address that has already been defined on the
          network, you lose the previous configuration in favor
          of the new MUXserver 100 you specify.

          Press <RET> to start, or CTRL/Z to exit... <RET>
          MUXserver Configuration Procedure



                        Menu of Options
                   1 - List known MUXservers
                   2 - Add a MUXserver
                   3 - Swap an existing MUXserver
                   4 - Delete an existing MUXserver
                   5 - Restore existing MUXservers
                   CTRL/Z - Exit from this procedure

                        Your selection?


                                                              B-1
                                                              B-1
                                                              B-1

 

          MUXserver Configurations
          MUXserver Configurations
          MUXserver Configurations






          __________________________________________________________________
   B.2     EXAMPLE OF A CONFIGURATION: LISTING KNOWN MUXserver
   B.2     EXAMPLE OF A CONFIGURATION: LISTING KNOWN MUXserver
   B.2     EXAMPLE OF A CONFIGURATION: LISTING KNOWN MUXserver
          100 UNITS (OPTION 1)
          100 UNITS (OPTION 1)
          100 UNITS (OPTION 1)

          This section and the following ones show how the
          configuration procedure continues for each option.
          With the exception of List, each option ends by
          returning you to the menu automatically

                   Your selection?  1 <RET>
               _______________________________________________________________________________
               DECnet  DECnet Server Service
               Address Name   Type   Circuit Ethernet Address  Load File     Dump File
               _______________________________________________________________________________

               28.1001 TUNA   MS100  UNA-0   08-00-2B-02-24-F1 MS1601ENG.SYS ASDMP24F1.SYS
               28.1005 OYSTER MS100  UNA-1   08-00-2B-04-AA-2B MS1601ENG.SYS ASDMPAA2B.SYS
               Total of 2 MUXservers defined.
               _______________________________________________________________________________



          __________________________________________________________________
   B.3     EXAMPLE OF A CONFIGURATION: ADDING A MUXserver 100
   B.3     EXAMPLE OF A CONFIGURATION: ADDING A MUXserver 100
   B.3     EXAMPLE OF A CONFIGURATION: ADDING A MUXserver 100
          UNIT (OPTION 2)
          UNIT (OPTION 2)
          UNIT (OPTION 2)
          This example adds a new MUXserver 100 named SHRIMP.

                           Your selection? 2 <RET>

                   Type a ? at any time for help on a question.
                   Type CTRL/Z for any question to return to the menu
                   without adding the unit.
                   MUXserver type? MS100 <RET>
                   DECnet node name for unit? SHRIMP <RET>
                   DECnet address for unit? 28.1002 <RET>
                   MUXserver Ethernet address of this unit?
                   08-00-2B-04-AA-2B <RET>
                   DECnet Service Circuit-ID? [UNA-0] <RET>

          B-2
          B-2
          B-2

 

                                         MUXserver Configurations
                                         MUXserver Configurations
                                         MUXserver Configurations




          If you get an error message now, the new unit won't be
          added, and you should delete it from the directory.

          If you use the List option to get a listing of
          servers, you see that SHRIMP appears on the listing
          of entries.


          __________________________________________________________________
   B.4     EXAMPLE OF A CONFIGURATION: SWAPPING AN OLD UNIT FOR A
   B.4     EXAMPLE OF A CONFIGURATION: SWAPPING AN OLD UNIT FOR A
   B.4     EXAMPLE OF A CONFIGURATION: SWAPPING AN OLD UNIT FOR A
          NEW UNIT (OPTION 3)
          NEW UNIT (OPTION 3)
          NEW UNIT (OPTION 3)

          In this example, an existing MUXserver 100 named CONCH
          is swapped for a new MUXserver 100, which is given the
          same DECnet node name. The DECnet node address always
          stays the same with Swap. The new server also has the
          same service circuit-ID as the old server. (Note that
          if you use Swap to change the characteristics of the
          same server, you have to specify the Ethernet address
          even though it will not change.)

                        Your selection? 3 <RET>
                   Type a ? at any time for help on a question.
                   Type CTRL/Z for any question to return to the menu
                   without changing the unit.

                   What is the DECnet node name you want to swap?
                   CONCH <RET>
                   MUXserver at Ethernet address 08-00-2B-02-24-F1 is
                   being swapped.
                   Enter the new Ethernet address, and any other
                   changed characteristics.
                   MUXserver type? [MS100] MS100 <RET>
                   DECnet node name for unit? [CONCH] <RET>
                   MUXserver Ethernet address of this unit?
                   08-00-2B-03-AA-AB <RET>
                   DECnet Service Circuit-ID? [UNA-0] <RET>




                                                              B-3
                                                              B-3
                                                              B-3

 

          MUXserver Configurations
          MUXserver Configurations
          MUXserver Configurations



          __________________________________________________________________
   B.5     EXAMPLE OF A CONFIGURATION: DELETING A MUXserver 100
   B.5     EXAMPLE OF A CONFIGURATION: DELETING A MUXserver 100
   B.5     EXAMPLE OF A CONFIGURATION: DELETING A MUXserver 100
          FROM THE DATABASE (OPTION 4)
          FROM THE DATABASE (OPTION 4)
          FROM THE DATABASE (OPTION 4)

          This example shows the deletion from the load host's
          node database of the existing server with the DECnet
          node name TUNA.

                        Your selection? 4 <RET>
                   Which DECnet node name is to be deleted? (CTRL/Z to
                   return to menu) TUNA <RET>
                   %NCP-I-NMLRSP, listener response - Success
                   Remote node =  28.1001 (TUNA)
                   %NML-I-RECDELET, Database entry deleted

          If you use the List option to get a listing of
          servers, you see that TUNA no longer appears.


          __________________________________________________________________
   B.6     EXAMPLE OF A CONFIGURATION: RESTORING EXISTING
   B.6     EXAMPLE OF A CONFIGURATION: RESTORING EXISTING
   B.6     EXAMPLE OF A CONFIGURATION: RESTORING EXISTING
          MUXserver 100 UNITS TO THE DATABASE (OPTION 5)
          MUXserver 100 UNITS TO THE DATABASE (OPTION 5)
          MUXserver 100 UNITS TO THE DATABASE (OPTION 5)

          This example shows the restoration of the local down-
          line load database.

                        Your selection?  5 <RET>
                   Restoring existing MUXservers from local database...
                   Local database successfully restored.













          B-4
          B-4
          B-4
