PBXserver Software Installation Guide Version 2.1 digital equipment france, annecy ________________________ 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 ©1989 by Digital Equipment France All Rights Reserved. __________ The following are trademarks of Digital Equipment Corpora- tion: DEC EduSystem VAX DEC/CMS IAS VAXcluster DEC/MMS MASSBUS VMS DECnet MicroVAX VT DECsystem-10 PDP DECSYSTEM-20 PDT DECUS RSTS DECwriter RSX DIBOL UNIBUS DIGITAL This document was prepared using VAX DOCUMENT, Version 1.1 Contents________________________________________________________ Preface________________________________________________________v Chapter_1__Software_Installation_and_Configuration______________ 1.1 Scope.................................................1-1 1.2 Installing the PBXserver Software.....................1-1 1.2.1 Software Files..............................1-2 1.2.2 Prerequisite Software.......................1-2 1.2.2.1 VMS Tailoring.........................1-2 1.2.2.2 Micro VMS Tailoring...................1-3 1.2.3 Prerequisite Hardware.......................1-3 1.2.4 VMS License Management Facility.............1-3 1.2.5 The VMSINSTAL Procedure.....................1-3 1.2.5.1 Conventions...........................1-4 1.2.5.2 Accessing the On-line Release Notes.................................1-4 1.2.5.3 Running the Installation Verification Procedure (IVP).......................1-4 1.2.5.4 Preparing to Run VMSINSTAL............1-5 1.2.5.5 Running VMSINSTAL.....................1-5 1.3 Configuring and Verifying the PBXserver...............1-9 1.3.1 The Configuration Procedure................1-10 1.3.1.1 Preparing to run the configuration procedure............................1-10 1.3.1.2 Configuring in a VAXcluster environment..........................1-11 1.3.1.3 Running the configuration procedure............................1-12 1.4 Starting the PBXserver...............................1-18 iii Appendix_A__Installation_and_Configuration_Examples_____________ A.1 Introduction..........................................A-1 A.2 VMS V4.7 Installation Example.........................A-1 A.3 VMS V5.0 Installation Example.........................A-4 A.4 Configuration Example.................................A-7 Index___________________________________________________________ iv Preface_________________________________________________________ This guide describes how to install the PBXserver software onto a VAX host computer and how to set up the PBXserver. Graphics Conventions The following conventions are used throughout this manual: UPPERCASE indicates the characters that make up a command word. Brackets [ ] indicate the characters you may omit from a command word. Braces { } indicate that you must choose one of the enclosed options. Related Publications PBXserver Manuals PBXserver Software Installation and Operations Guide, AA- JZ80B-TE PBXserver User's Reference Card, AA-JZ79B-TE v PBXserver Hardware Installation and Maintenance Guide, EK- PBXHI-MM-001 PBXserver Maintenance Card, EK-PBXSR-MC-001 PBXserver Technical Description, EK-PBXSV-TD-001 MicroVAX II Manuals MicroVAX II System Maintenance Guide, AZ-GM3AA-MN MicroVAX II System Owner's Manual, AZ-FE05A-TN MicroVAX II System Technical Manual, AZ-FE06-TN VMS Manuals Guide to Networking on VAX/VMS, AA-Y512B-TE Revision Information This guide has been updated so that it covers Version 2.1 of the PBXserver software. Version 2.1 of the PBXserver software has same functionality as Version 2.0. Version 2.1 is a maintenance release of the PBXserver software. vi Chapter__1______________________________________________________ Software Installation and Configuration 1.1 Scope This chapter describes the steps you must follow to install the PBXserver software onto an Ethernet load host, using the VMSINSTAL procedure. It also describes the steps you must follow to configure a PBXserver. When a PBXserver is configured, information about it is added to the load host's DECnet database. This information enables the PBXserver software to be down-line loaded to the PBXserver from the load host, simply by powering-up the PBXserver. 1.2 Installing the PBXserver Software You must install the PBXserver software onto at least one host node on the Ethernet network, using the VMSINSTAL procedure. A node that has the software installed on it is called a "load host". A load host can be a single VMS or MicroVMS system but must be located on the same Ethernet as the PBXserver. It is advisable to install the software on more than one host node so that other nodes can act as a load host if a failure occurs. Note Special considerations must be taken into account if you plan to install the PBXserver software on a load host which belongs to a VAXcluster with a common system disk. Refer to Section 1.3.1.2 for details of these considerations. Software Installation and Configuration 1-1 1.2.1 Software Files The PBXserver software consists of the following files: o KITINSTAL.COM o PBXSERVER$021.RELEASE_NOTES (Release Notes for this version of the software) o PBXSERVER$IVP.COM o PBXSERVER$SYSTEM.SYS o PBXSERVER$CONFIG.COM o PBXSERVER$PRIVUSER.COM Refer to the Software Product Description (SPD 29.23.02) for a list of the distribution media of these files. 1.2.2 Prerequisite Software The System Support Addendum (SSA 29.23.02-A) lists all the required software. 1.2.2.1 VMS Tailoring For VMS V5.0 - V5.2 systems, the following VMS classes are required for full functionality of this layered product: o VMS Required Saveset o Utilities o Networking support For more information on VMS classes and tailoring, refer to the VMS Operating System Software Product Description (SPD 25.01.xx) 1-2 Software Installation and Configuration 1.2.2.2 Micro VMS Tailoring For MicroVMS V4.6, V4.7 systems, the following VMS classes are required for full functionality of this layered product: o VMS Required Saveset o Utilities o Networking support 1.2.3 Prerequisite Hardware The System Support Addendum (SSA 29.23.02-A) lists all the required hardware. Note that the hardware on which the PBXserver software runs is DELIX-AB. 1.2.4 VMS License Management Facility The VMS License Management Facility is available with Version 5.0 of the VMS operating system. If you are installing the PBXserver software on a VMS V5.0 system, you must register your software license. The license registration information you need is contained in the Product Authorization Key (PAK) that is shipped with the PBXserver software. The PAK is a paper certificate that contains information about the license you must obtain to run a particular piece of software. 1.2.5 The VMSINSTAL Procedure The VMSINSTAL procedure is an automated procedure. It creates a directory called SYS$SYSROOT:[PBXSERVER] on the load host, copies files from the distribution media into this directory, optionally prints a copy of the release notes and enables you to run an installation verification procedure. VMSINSTAL takes about 10 minutes to complete. Software Installation and Configuration 1-3 1.2.5.1 Conventions VMSINSTAL is an interactive procedure. It displays a series of queries preceded by an asterisk (*). After the query, default responses may appear in brackets ([ ]). At the end of the display line, a colon (:) or a question mark (?) appears. Type your response immediately after the colon or question mark, then press the key. If you choose the default reply in brackets, just press after the colon or question mark. If you enter a question mark (?) as a response, VMSINSTAL provides explanatory text about the query and then repeats the query. Refer to the VAX/VMS or MicroVMS documentation for a complete description of VMSINSTAL. 1.2.5.2 Accessing the On-line Release Notes The PBXserver software provides on-line release notes. If you specify OPTIONS N when you invoke VMSINSTAL, the installation procedure asks you if you want to display or print the release notes. You should review the release notes to find out if there have been any changes to the installation procedures. After the PBXserver software has been installed, the release notes are located in the file SYS$HELP:PBXSERVER$020.RELEASE_ NOTES. 1.2.5.3 Running the Installation Verification Procedure (IVP) During the installation of the PBXserver software, VMSINSTAL asks you if you want to run the Installation Verification Procedure (IVP) as part of the installation. If you respond YES, VMSINSTAL runs the IVP. The IVP verifies that the software has been installed correctly. It is recommended that you do run it. 1-4 Software Installation and Configuration After the PBXserver software has been installed, you can run the IVP independently to verify that the software is available on your system. You might also want to run the IVP after a system failure to ensure that users can access the PBXserver software. The IVP command file is SYS$TEST:PBXSERVER$IVP.COM You execute it with the DCL command: @SYS$TEST:PBXSERVER$IVP 1.2.5.4 Preparing to Run VMSINSTAL Before running VMSINSTAL, determine which host nodes you are going to use as load hosts. Each load host must have the prerequsite software installed and have 1200 blocks of free disk space available. Section 1.2.2 lists the prerequiste software products. 1.2.5.5 Running VMSINSTAL To run VMSINSTAL, place the PBXserver software distribution medium in the appropriate device drive of the load host and log into the system manager's account. Once you have entered the system manager's account, invoke VMSINSTAL by entering: $ SET DEFAULT SYS$UPDATE $ @VMSINSTAL VMSINSTAL displays a title, the date and time, and then continues with the following questions: %VMSINSTAL-W-DECNET, Your DECnet network is up and running. * Do you want to continue anyway [NO]? This warning message only appears if DECnet is running. Answer YES to proceed with the installation. * Are you satisfied with the backup of your system disk [YES]? Software Installation and Configuration 1-5 Enter YES or take appropriate action. * Where will the distribution volumes be mounted: Enter the device identification; for example, CSA0: or MUA0:. Enter the products to be processed from the first distribu- tion volume set. * Products: Enter PBXSERVERnnn, where nnn is the version of the server software shown on your distribution kit. This identifies the PBXserver Terminal Server software product. The following products will be processed: PBXSERVER V2.1 Beginning installation of PBXSERVER V2.1 at time %VMSINSTAL-I-RESTORE, Restoring product saveset A... * Do you want to run the IVP after the installation [YES]? Enter YES or press if you want to run the PBXSERVER$IVP.COM file at the end of the installation. KITINSTAL places the IVP file in the SYS$SYSROOT:[SYSTEST] directory. * Do you want to purge files replaced by this installation [YES]? Enter YES or press if you want to purge files. If you are running your installation procedure on a system running VMS V5.0 or later, and a DECnet license has not been registered, the installation procedure will display the following warning: 1-6 Software Installation and Configuration No DECnet license was registered for this computer. DECnet is a prerequisite for down-line loading this product. This installation procedure will be allowed to complete normally. Note, however, that a suitable DECnet license should be registered before you attempt to run this product. Please refer to the VMS License Management Utility Manual for additional information on licensing. If you are running your installation procedure on a system running VMS V5.0 or later, you will be asked to confirm your PBXserver license registration: Product: PBXSERVER Producer: DEC Version: 2.1 Release Date: 01-FEB-1989 * Does this product have an authorization key registered and loaded? Then the installation procedure displays the following message: There will be no further questions asked during the installation. The installation will continue for approximately 3 to 15 minutes depending on your system type. and continues with the following displays: %VMSINSTAL-I-SYSDIR, This product creates system directory [PBXSERVER] %VMSINSTAL-I-RESTORE, Restoring product saveset B... PBXSERVER-I-INSTALDONE, PBXSERVER V2.1 installation is completed Software Installation and Configuration 1-7 If you are running on a VMS V5.0 or later system, and no DECnet license was registered for your computer, the installation reminds you to do it before using this software: After exiting from VMSINSTAL: o Register your DECnet software license in the VMS/LMF database. If you are running on a VMS V5.0 or later system, and no license was registered for the PBXserver software, the installation reminds you to do it before using this software: o Register your PBXserver software license in the VMS/LMF database. Then it displays: o Configure your PBXserver unit into your host's database. To do this, execute a command procedure called PBXSERVER$CONFIG.COM. This command procedure is in the SYS$SYSROOT:[PBXSERVER] directory. If you have already executed this procedure from previous installations, you only need to configure any additional units. All previously defined units will still be configured. Then it displays: o Verify your PBXserver unit. To do this, execute the command procedure called PBXSERVER$CONFIG.COM, which you have already executed to configure your PBXserver unit. During verification, the link between your host and the PBXserver unit is tested, the PBXserver privileged command SIMULATE is issued to execute internal test of the PBXserver unit. %VMSINSTAL-I-MOVEFILES, Files will now be moved to their target directories... 1-8 Software Installation and Configuration Starting installation verification procedure for PBXSERVER V2.1 Successful creation of SYS$SYSROOT:[PBXSERVER] directory Successful installation of SYS$SYSROOT:[PBXSERVER]PBXSERVER$SYSTEM.SYS Successful installation of SYS$SYSROOT:[PBXSERVER]PBXSERVER$CONFIG.COM Successful installation of SYS$SYSROOT:[SYSTEST]PBXSERVER$IVP.COM Successful installation of SYS$SYSROOT:[PBXSERVER]PBXSERVER$PRIVUSER.COM Successful installation of SYS$SYSROOT:[SYSHLP]PBXSERVER$020.RELEASE_NOTES Installation Verification Procedure for PBXSERVER V2.1 has succeeded. PBXSERVER V2.1 successfully installed. Installation of PBXSERVER V2.1 completed at time Press CTRL/Z to exit from the installation procedure. VMSINSTAL displays: VMSINSTAL procedure done at time Your PBXserver software installation is now complete. 1.3 Configuring and Verifying the PBXserver The installation media you received includes the PBXSERVER$CONFIG.COM configuration procedure for config- uring the PBXserver into a load host's database. This proce- dure also enables you to verify the PBXserver unit. The load host must have DECnet Phase IV and LAT system running. You must run this configuration procedure separately from the installation procedure. Software Installation and Configuration 1-9 1.3.1 The Configuration Procedure The configuration procedure, PBXSERVER$CONFIG.COM, is a menu-driven procedure. It creates or updates the PBXserver units database PBXSERVER$CONFIG.DAT, and updates both permanent and volatile DECnet databases. It is copied to the SYS$SYSROOT:[PBXSERVER] directory during the installation phase. It enables you to: o Configure or add a new PBXserver to the load host's DECnet database. This configuration information identifies the PBXserver on the Ethernet and specifies the down-line load database. o Modify the database if you are swapping an existing PBXserver unit for a new unit. This is necessary as each PBXserver unit has its own unique Ethernet address. o Delete PBXservers from the database if, for example, you are reconfiguring the network or wish to assign this PBXserver to another load host. o Restore your local down-line load database for the PBXserver in cases where you load your DECnet database from a central database on a remote node. o List PBXservers already configured in the database. o Verify a PBXserver already configured in the database. 1.3.1.1 Preparing to run the configuration procedure Before running the configuration procedure make sure that: 1. The PBXserver software has been installed on the load host on which you are going to run the configuration procedure. 2. DECnet is running on your load host. 3. The LAT system is running and the link to the PBXserver is operational if you intend to use the VERIFY option. 1-10 Software Installation and Configuration 4. You know the unique DECnet node name and DECnet address of the PBXserver. Use the NCP SHOW NODE node_name or NCP SHOW KNOWN NODES command to determine if your node name is unique. 5. You know the Ethernet address of the PBXserver unit. This is the unique address associated with the Ethernet controller device that connects the PBXserver to the network. The address is recorded on the back panel of the PBXserver unit and on the PBXserver terminal server identification card. 6. You know the DECnet service circuit-ID over which the loading is to take place (example: QNA-0) for that PBXserver. Note The procedure will attempt to set the circuit to SERVICE ENABLED in the DECnet volatile database. Since it involves turning the circuit OFF and then back ON, it may disrupt other established DECnet communications. The procedure will always give you the option of preventing it from doing this. 1.3.1.2 Configuring in a VAXcluster environment The PBXSERVER$CONFIG.COM configuration procedure will execute any DECnet configuration commands that are necessary to set up the load host's DECnet database and the PBXserver's own database, PBXSERVER$CONFIG.DAT. The DECnet database contains the DECnet service circuit-ID (for example, QNA-0) over which the loading is to take place for each PBXserver. Before attempting to configure your PBXserver units, check the communications hardware configurations within your cluster. If these are not identical on every node, you should make sure that your DECnet node's database, located Software Installation and Configuration 1-11 in the SYS$SYSTEM:NETNODE_REMOTE.DAT, is NOT shared among the cluster. Failing to do so may result in a DECnet service circuit assigned to a PBXserver unit that does not match the loading node's hardware. The configuration procedure will create its own database file PBXSERVER$CONFIG.DAT in a cluster-common directory on your target disk only if the DECnet file SYS$SYSTEM:NETNODE_ REMOTE.DAT already resides in a common directory. Otherwise, the PBXSERVER$CONFIG.DAT will be created in a node-specific directory on your target disk. This ensures that the DECnet database and PBXSERVER$CONFIG.DAT file reflect the same information. Each time the procedure needs to create PBXSERVER$CONFIG.DAT, it issues a message to tell you where the file is created: The database file: PBXSERVER$CONFIG.DAT could not be found, a new file will be created for you. The database file: PBXSERVER$CONFIG.DAT is created in the node-specific directory SYS$SPECIFIC:[PBXSERVER]. Refer to the VMS networking reference manual, Permanent Database Consideration in VAXclusters, for additionnal information about sharing DECnet files in a cluster environment. 1.3.1.3 Running the configuration procedure To run the PBXSERVER$CONFIG.COM configuration procedure interactively, log into the system account on your load host (or any account with OPER, SYSPRV and CMKRNL privileges), and enter the following commands: $ SET DEFAULT SYS$SYSROOT:[PBXserver] $ @PBXSERVER$CONFIG 1-12 Software Installation and Configuration The configuration procedure contains a RESTORE option which you can call by including the RESTORE parameter in the command line. $ @PBXSERVER$CONFIG RESTORE This option will allow systems using central databases to re-configure PBXservers at system boot time. It exits automatically when it has successfully completed. Once invoked, PBXSERVER$CONFIG displays the following text: You must assign a unique DECnet node name and DECnet address for each PBXserver you are going to configure. If, at any time, you specify a node name or address that has already been defined on the network, you lose the previous configuration in favor of the new PBXserver you specify. Press to start, or to exit... Then, if you press , PBXSERVER$CONFIG displays the main menu, as follows: PBXserver Configuration Procedure Menu of options 1 - List known PBXserver units 2 - Add a PBXserver unit 3 - Modify an existing PBXserver unit 4 - Delete an existing PBXserver unit 5 - Restore existing PBXserver units 6 - Verify an existing PBXserver unit CTRL/Z - Exit from this procedure Your selection? Software Installation and Configuration 1-13 Enter the number of the menu item you require and press or press / to exit. Type your responses to further questions immediately after the question mark and press . If you enter a question mark as a response, PBXSERVER$CONFIG provides explanatory text about the query and then repeats the query. SELECTION 1 - List known PBXservers Select this menu item to list known PBXservers in the database. The PBXservers are listed under the following headings: DECnet DECnet Service Address Node name Circuit Ethernet Address ------- --------- ------- ----------------- SELECTION 2 - Add a PBXserver Select this menu item when you are configuring a new PBXserver. DECnet node name for unit? Specify the DECnet node name for your PBXserver unit. Enter a name of 1 to 6 alphanumeric characters, the first one being alphabetic. DECnet address for unit? Specify the DECnet address for your PBXserver. Enter a number in the form aa.nnnn where aa is the area number in the range from 1 to 63 and nnnn is the node number in the range from 1 to 1023. If you are referencing a node within your area, you may omit the area number and the period separator. When referencing a node in a single area network, you must always omit the area number and period. 1-14 Software Installation and Configuration DECnet Service Circuit-ID [QNA-0]? Specify the DECnet service circuit identifier for the PBXserver being added. The circuit-ID between brackets is the default value for the question. PBXserver Ethernet address for this unit? Specify the Ethernet address of your PBXserver. This address is the Ethernet address specified on the back of the hardware unit. Enter the address as six groups of two hexadecimal numbers, with hyphens separating the groups (for example, 08-00-01-00-AB-CD). If you get any error messages now, the new unit will not be added. However, an entry may appear in the directory and you should delete this entry. SELECTION 3 - Modify an existing PBXserver Select this menu item to modify the database if, for example, you are replacing one PBXserver hardware unit with another and wish to keep the same name. As each unit has its own unique Ethernet address, the database needs to be modified to reflect this change. All the questions are asked with a default provided except for the address questions. The DECnet address question is omitted and the Ethernet address question is asked without a default. What is the DECnet node name you want to modify? PBXserver at Ethernet address "address" is being modified. Enter the new Ethernet address, and any other changes characteristics. Specify the DECnet node name of the unit you want to modify. DECnet node name for unit [AEO000]? Software Installation and Configuration 1-15 Specify the new DECnet node name for your PBXserver unit. Enter a name of 1 to 6 alphanumeric characters, the first one being alphabetic, or keep the current node name displayed between brackets as the default value. DECnet Service Circuit-ID [QNA-0]? Specify the DECnet service circuit identifier for the PBXserver being added. The circuit-ID between brackets is the default and current value for this PBXserver. What is the new Ethernet address? Specify the Ethernet address of your new PBXserver. This address is the Ethernet address specified on the back of the hardware unit. Enter a number as six groups of two hexadecimal numbers, with hyphens separating the groups (for example, 08-00-01-00-AB-CD). SELECTION 4 - Delete an existing PBXserver Select this menu item to remove PBXservers from the database if, for example, you are reconfiguring the network or wish to assign the PBXserver to another load host. DECnet node name for unit? Specify the DECnet node name of the unit you wish to remove. Press / if you want to return to the main menu. Successful removal of the unit is indicated by an NCP response. 1-16 Software Installation and Configuration SELECTION 5 - Restore existing PBXservers Select this menu item to restore the volatile database using your local database for the PBXserver units. The following messages are displayed during the process. Restoring existing PBXservers from local database... Local database successfully restored. SELECTION 6 - Verify an existing PBXserver Select this menu item to verify a PBXserver unit. In order to perform the verification, the connection between the PBXserver and the host through Ethernet must be up and running. In addition, the LAT system must also be up and running on your node. Finally, you should allow the procedure to set the service circuit to ENABLED to allow the PBXserver unit to be properly down-line loaded. The following message is then displayed: DECnet node name for unit? Specify the DECnet node name of the unit you wish to verify. Press / if you want to return to the main menu. Then, the procedure: 1. Verifies that the selected unit is defined in the local database. 2. Restores the volatile database for this unit you have specified. 3. Performs a remote loop test, using NCP to test the communication path between the host and the unit. 4. Triggers the unit to down-line load the PBXserver software. 5. Enters the PBXserver privileged interface and waits for the connection to the unit to be completed. Software Installation and Configuration 1-17 6. Issues a SHOW SERVER command to see if a service is up or starting. If a service is up or starting, it issues a SIMULATE INTERNAL command to invoke the internal loop test. The message generated by the PBXserver is displayed. 1.4 Starting the PBXserver To start the PBXserver, you simply switch it on. The PBXserver automatically performs an initialization sequence, which includes loading the firmware from the host computer and running the self-test program. Note Before a new version is installed, it is mandatory to issue the INIT RESET command. This will reset the PBXserver's characteristics to the default values. It is then necessary to update them with your own with the appropriate privileged commands. 1-18 Software Installation and Configuration Appendix__A_____________________________________________________ Installation and Configuration Examples A.1 Introduction This appendix gives you two examples of installing the PBXsever VAX/VMS software using the VMSINSTAL procedure and an example of configuring the PBXserver. A.2 VMS V4.7 Installation Example $ @SYS$UPDATE:VMSINSTAL PBXSERVER MS: OPTIONS N VAX/VMS Software Product Installation Procedure V4.7 It is 7-MAY-1989 at 16:26. Enter a question mark (?) at any time for help. %VMSINSTAL-W-DECNET, Your DECnet network is up and running. * Do you want to continue anyway [NO]? YES * Are you satisfied with the backup of your system disk [YES]? Y Please mount the first volume of the set on MS:. * Are you ready? YES %MOUNT-I-MOUNTED, PBXSER mounted on _LODNOD$MSA0: The following products will be processed: PBXSERVER V2.1 Beginning installation of PBXSERVER V2.1 at 16:27 %VMSINSTAL-I-RESTORE, Restoring product saveset A... Release Notes Options: Installation and Configuration Examples A-1 1. Display release notes 2. Print release notes 3. Both 1 and 2 * Select option [3]: 2 * Queue name [SYS$PRINT]: Job PBXSERVER$021 (queue LP$PRINT, entry 1536) pending * Do you want to continue the installation [N]? YES %VMSINSTAL-I-RELMOVED, The products release notes have been successfully moved to SYS$HELP. * Do you want to run the IVP after the installation [YES]? * Do you want to purge files replaced by this installation [YES]? There will be no further questions asked during the installation. The installation will continue for approximately 3 to 15 minutes depending on your system type. %VMSINSTAL-I-SYSDIR, This product creates system directory [PBXSERVER]. If you intend to execute this layered product on other nodes in your VAXcluster, and you have the appropriate software license, you must prepare the system-specific roots on the other nodes by issuing the following command on each node (using a suitably privileged account): $ CREATE /DIRECTORY SYS$SPECIFIC:[PBXSERVER] /PROTECTION=(S:RWED,O:RWED) %VMSINSTAL-I-RESTORE, Restoring product saveset B... %PBXSERVER-I-INSTALDONE, PBXSERVER V2.1 installation is completed. After exiting from VMSINSTAL: A-2 Installation and Configuration Examples o Configure your PBXserver unit into your host's database. To do this, execute a command procedure called PBXSERVER$CONFIG.COM. This command procedure is in the SYS$SYSROOT:[PBXSERVER] directory. If you have already executed this procedure from previous installations, you only need to configure any additional units. All previously defined units will still be configured. o Verify your PBXserver unit. To do this, execute the command procedure called PBXSERVER$CONFIG.COM, which you have already executed to configure your PBXserver unit. During verification, the link between your host and the PBXserver unit is tested, the PBXserver privileged command SIMULATE is issued to execute internal test of the PBXserver unit. %VMSINSTAL-I-MOVEFILES, Files will now be moved to their target directories... Starting Installation Verification Procedure for PBXSERVER V2.1. Successful creation of SYS$SYSROOT:[PBXSERVER] directory Successful installation of SYS$SYSROOT:[PBXSERVER]PBXSERVER$SYSTEM.SYS Successful installation of SYS$SYSROOT:[PBXSERVER]PBXSERVER$CONFIG.COM Successful installation of SYS$SYSROOT:[PBXSERVER]PBXSERVER$PRIVUSER.COM Successful installation of SYS$SYSROOT:[SYSTEST]PBXSERVER$IVP.COM Successful installation of SYS$SYSROOT:[SYSHLP]PBXSERVER$021.RELEASE_NOTES Installation Verification Procedure for PBXSERVER V2.1 has succeeded. Installation and Configuration Examples A-3 PBXSERVER V2.1 successfully installed. Installation of PBXSERVER V2.1 completed at 16:28 VMSINSTAL procedure done at 16:28 A.3 VMS V5.0 Installation Example $ @SYS$UPDATE:VMSINSTAL PBXSERVER MU: OPTIONS N VAX/VMS Software Product Installation Procedure V5.0-2 It is 7-MAY-1989 at 16:50. Enter a question mark (?) at any time for help. %VMSINSTAL-W-DECNET, Your DECnet network is up and running. * Do you want to continue anyway [NO]? YES * Are you satisfied with the backup of your system disk [YES]? Y Please mount the first volume of the set on MU:. * Are you ready? YES %MOUNT-I-MOUNTED, PBXSER mounted on _LODNOD$MUA0: The following products will be processed: PBXSERVER V2.1 Beginning installation of PBXSERVER V2.1 at 16:53 %VMSINSTAL-I-RESTORE, Restoring product saveset A ... 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]: 2 * Queue name [SYS$PRINT]: A-4 Installation and Configuration Examples Job PBXSERVER$021 (queue LP$PRINT, entry 1536) pending * Do you want to continue the installation [N]? YES %VMSINSTAL-I-RELMOVED , The product's release notes have been successfully moved to SYS$HELP. * Do you want to run the IVP after the installation [YES]? * Do you want to purge files replaced by this installation [YES]? Product: PBXSERVER Producer: DEC Version: 2.1 Release Date: 01-MAY-1989 * Does this product have an authorization key registered and loaded? YES There will be no further questions asked during the installation. The installation will continue for approximately 3 to 15 minutes depending on your system type. %VMSINSTAL-I-SYSDIR, This product creates system directory [PBXSERVER]. If you intend to execute this layered product on other nodes in your VAXcluster, and you have the appropriate software license, you must prepare the system-specific roots on the other nodes by issuing the following command on each node (using a suitably privileged account): $ CREATE /DIRECTORY SYS$SPECIFIC:[PBXSERVER] /PROTECTION=(S:RWED,O:RWED) %VMSINSTAL-I-RESTORE, Restoring product saveset B ... %PBXSERVER-I-INSTALDONE, PBXSERVER V2.1 installation is completed. After exiting from VMSINSTAL: Installation and Configuration Examples A-5 o Configure your PBXserver unit into your host's database. To do this, execute a command procedure called PBXSERVER$CONFIG.COM. This command procedure is in the SYS$SYSROOT:[PBXSERVER] directory. If you have already executed this procedure from previous installations, you only need to configure any additional units. All previously defined units will still be configured. o Verify your PBXserver unit. To do this, execute the command procedure called PBXSERVER$CONFIG.COM, which you have already executed to configure your PBXserver unit. During verification, the link between your host and the PBXserver unit is tested, the PBXserver privileged command SIMULATE is issued to execute internal test of the PBXserver unit. %VMSINSTAL-I-MOVEFILES, Files will now be moved to their target directories... Starting Installation Verification Procedure for PBXSERVER V2.1. Successful creation of SYS$SYSROOT:[PBXSERVER] directory Successful installation of SYS$SYSROOT:[PBXSERVER]PBXSERVER$SYSTEM.SYS Successful installation of SYS$SYSROOT:[PBXSERVER]PBXSERVER$CONFIG.COM Successful installation of SYS$SYSROOT:[PBXSERVER]PBXSERVER$PRIVUSER.COM Successful installation of SYS$SYSROOT:[SYSTEST]PBXSERVER$IVP.COM Successful installation of SYS$SYSROOT:[SYSHLP]PBXSERVER$021.RELEASE_NOTES Installation Verification Procedure for PBXSERVER V2.1 has succeeded. A-6 Installation and Configuration Examples PBXSERVER V2.1 successfully installed. Installation of PBXSERVER V2.1 completed at 16:57 VMSINSTAL procedure done at 16:58 A.4 Configuration Example $ @SYS$SYSROOT:[PBXSERVER]PBXSERVER$CONFIG You must assign a unique DECnet node name and DECnet address for each PBXserver you are going to configure. If, at any time, you specify a node name or address that has already been defined on the network, you lose the previous configuration in favor of the new PBXserver you specify. Press to start, or to exit.. PBXserver unit Configuration Procedure Menu of options. 1 - List known PBXserver units 2 - Add a PBXserver unit 3 - Modify an existing PBXserver unit 4 - Delete an existing PBXserver unit 5 - Restore existing PBXserver units 6 - Verify an existing PBXserver unit CTRL/Z - Exit from this procedure Your selection? 2 Type a ? at any time for help on a question. Type CTRL/Z for any question to return to menu without verifying the unit. DECnet node name unit? PBX001 DECnet address for unit? 10.100 DECnet Service Circuit-ID [QNA-0]? PBXserver unit Ethernet address for this unit? 11-22-33-44-55-66 Installation and Configuration Examples A-7 If you get an error message now, the new unit won't be added, and you should delete it from the directory. PBXserver unit Configuration Procedure Menu of options. 1 - List known PBXserver units 2 - Add a PBXserver unit 3 - Modify an existing PBXserver unit 4 - Delete an existing PBXserver unit 5 - Restore existing PBXserver units 6 - Verify an existing PBXserver unit CTRL/Z - Exit from this procedure Your selection? 1 DECnet DECnet Service Address Node name Circuit Ethernet address ------- --------- ------- ----------------- 10.100 PBX001 QNA-0 11-22-33-44-55-66 Total of 1 PBXserver unit(s) defined. ------------------------------------- (Press RETURN for menu) PBXserver unit Configuration Procedure Menu of options. 1 - List known PBXserver units 2 - Add a PBXserver unit 3 - Modify an existing PBXserver unit 4 - Delete an existing PBXserver unit 5 - Restore existing PBXserver units 6 - Verify an existing PBXserver unit CTRL/Z - Exit from this procedure Your selection? 6 A-8 Installation and Configuration Examples Type a ? at any time for help on a question. Type CTRL/Z for any question to return to menu without verifying the unit. DECnet node name unit? PBX001 PBXserver unit at Ethernet address 11-22-33-44-55-66 is being verified. Test if LAT protocol is active Service Name : LODNOD Test of the communication link, between your host and the PBXserver unit to verify, in progress. The PBXserver software is being down-loaded Connecting to PBX001 SHOW SERVER privileged command is issued to be sure that service is up or starting. PBXserver V2.1 Microcode V2.6 ROM V1.0 LAT V5.1 Rev 0 Installation and Configuration Examples A-9 Current Permanent Manufact Name : PBX001 PBX001 PBXSERVER Number : 00 00 00 Location : Host Maximum : 30 30 4 User Maximum : 30 30 30 Group Codes : Groups 63-0 : 00000000-00000001 ...00001 ...00001 Groups 127-64 : 00000000-00000000 ...00000 ...00000 Groups 191-128 : 00000000-00000000 ...00000 ...00000 Groups 255-192 : 00000000-00000000 ...00000 ...00000 Inactivity Timer : 0 0 0 PBX Addr (1-17) : 81 81 0 PBX Addr (18-24) : Printer channels : 2 2 2 Queue limit : 10 10 10 Term session limit : 4 4 4 Global session limit : 120 120 120 Physical Address : 11-22-33-44-55-66 Up Time : 0 0:0:37 System Status : Service Up Internal PBXserver unit loop test, using the privileged user command SIMULATE, in progress. %PBXSERVER-I-EOSIMU, Simulate completed, no errors PBXserver unit Configuration Procedure Menu of options. 1 - List known PBXserver units 2 - Add a PBXserver unit 3 - Modify an existing PBXserver unit 4 - Delete an existing PBXserver unit 5 - Restore existing PBXserver units 6 - Verify an existing PBXserver unit CTRL/Z - Exit from this procedure Your selection? CTRL/Z A-10 Installation and Configuration Examples Index ________________________________________________________________ A______________________________ Address I______________________________ Ethernet, 1-10 Installation PBXserver software, 1-1 C______________________________ Configuration S______________________________ PBXserver software, 1-9 Software Distribution E______________________________ files, 1-2 Ethernet Starting Address, 1-10 PBXserver, 1-18 H V______________________________ _______________________________ Host, 1-1 VMSINSTAL Conventions, 1-4 Operation, 1-5 Index-1