VAXcluster_Console_System____________________________ Installation Guide EK-VXCNE-IN-005 June 1990 This guide describes how to install the VAXcluster Console System software and the fiberoptic and DECconnect hardware. Revision/Update Information: This manual is a revision of the VAXcluster Console System Hardware Installation Guide, order number EK-VXCND-IN-004. Operating System and Version: VMS Version 5.3 Software Version: VCS Version 1.3 digital equipment corporation maynard, massachusetts _____________________________________________________ First Printing, May 1986 Revised, July 1986 Revised, May 1987 Updated, January 1988 Revised, October 1988 Revised, June 1990 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. Restricted Rights: Use, duplication, or disclosure by the U.S. Government is subject to restrictions as set forth in subparagraph (c)(1)(ii) of the Rights in Technical Data and Computer Software clause at DFARS 252.227-7013. © by Digital Equipment Corporation 1986, 1987, 1988, 1990. All Rights Reserved. Printed in U.S.A. The postpaid Reader's Comments forms at the end of this document request your critical evaluation to assist in preparing future documentation. FCC Notice: This equipment generates, uses, and may emit radio frequency energy. The equipment has been type tested and found to comply with the limits for a Class A computing device pursuant to Subpart J of Part 15 of FCC Rules, which are designed to provide reasonable protection against such a commercial environment. Operation of this equipment in a residential area may cause interference, in which case the user, at his own expense, may be required to take measures to correct the interference. The following are trademarks of Digital Equipment Corporation: DEC, DECconnect, DECnet, DECserver, DELNI, HSC, LAT, microVAX, microVAX II, PDP, VAX, VAXcluster, VMS, and the DIGITAL logo. This document was prepared using VAX DOCUMENT, Version 1.2 ________________________________________________________________ Contents About This Guide......................................... vii 1 Hardware Installation 1.1 VCS Hardware Connection Methods and Precautions..................................... 1-1 1.1.1VCS Hardware Direct Connection ............... 1-2 1.1.2VCS Hardware Host Initiated Connection ....... 1-3 1.1.3VCS Hardware Installation Precautions ........ 1-5 1.1.3.1 VAX 8830/8840 Precautions ............... 1-5 1.1.3.2 HSC Precautions ......................... 1-6 1.2 VCS Fiberoptic Components....................... 1-7 1.2.1Fiberoptic Cable Characteristics ............. 1-8 1.2.2Fiberoptic Cable Environmental Requirements .. 1-8 1.2.3Preparing the Host System .................... 1-8 1.2.4Direct Connection Installation ............... 1-12 1.2.5Host Initiated Connection Installation ....... 1-16 iii 1.2.6Fiberoptic Installation at the Serviced Nodes........................................ 1-17 1.2.6.1 Optional Extension Cable Installation ... 1-18 1.2.6.2 Optional DECconnect Cabling Installation............................ 1-21 1.2.6.3 Optional VCS Disable Switch Installation............................ 1-21 1.2.7Fiberoptic Converter Troubleshooting ......... 1-22 1.3 VCS DECconnect Components....................... 1-23 1.3.1Preparing the Host System .................... 1-24 1.3.2Direct Connection Installation ............... 1-27 1.3.3Host Initiated Connection Installation ....... 1-28 1.3.4DECconnect Installation at the Serviced Nodes........................................ 1-28 1.3.5DECconnect Adapter Troubleshooting ........... 1-29 2 Software Installation 2.1 VCS Software Kit Inventory...................... 2-1 2.2 VCS Host System Preparation..................... 2-2 2.2.1Required Software ............................ 2-2 2.2.2Required Disk Space .......................... 2-2 2.2.3User Terminals ............................... 2-3 2.2.4SYSGEN Parameters ............................ 2-3 2.2.5Host Initiated Connection Setup .............. 2-4 2.2.5.1 Setting Up DECserver 200 Ports .......... 2-4 2.2.5.2 Using VCS$LTA.COM to Create LTA Devices................................. 2-6 2.3 Installation Preparation for the VAX 8500/8700/8800 Series Systems................... 2-9 2.3.1VAX 8500/8700/8800 ........................... 2-9 2.3.2VAX 8830/8840 ................................ 2-12 2.3.3Preparation Work Sheets ...................... 2-12 2.4 Installation of the VCS Software on the Host System.......................................... 2-14 2.4.1License Registration ......................... 2-14 2.4.2Installation Procedure ....................... 2-16 iv 2.4.3VCS Installation Log ......................... 2-26 2.5 Site-Specific Modifications to the Installed VCS Environment..................................... 2-30 2.5.1Creating a Configuration File ................ 2-30 2.5.2Console Line Communications Characteristics .. 2-31 2.5.3VCS Logical Names ............................ 2-31 2.5.3.1 Node Name Grouping by Logical Name ...... 2-31 2.5.3.2 VCS Logical Name Definitions ............ 2-33 2.5.4Setting Console Terminal Characteristics ..... 2-37 2.5.5Starting the VCS Software at System Reboot ... 2-37 2.5.5.1 VCS$STARTUP.COM ......................... 2-39 2.5.5.2 VCS Startup Sequence .................... 2-41 2.5.6Stopping the VCS Software at System Shutdown..................................... 2-42 2.6 Starting the VCS Software....................... 2-42 2.7 Final Setup..................................... 2-44 2.7.1VAX 8500/8700/8800 ........................... 2-44 2.7.2VAX 8830/8840 ................................ 2-46 Index Figures 1-15 DECserver 200 Connections........................ 1-16 1-28 DECconnect Adapter and Cable Connections......... 1-27 2-2 VAXconsole PRO380 Communication Line Setup Menu............................................. 2-11 v Tables 2-1 Logical Names.................................... 2-33 vi ________________________________________________________________ About This Guide The VAXcluster Console System allows multiple system management from one location. The VCS software runs on most VMS V5.3 systems. See the VCS Software Product Description (SPD) for a specific description of host systems. Specific installation procedures for the host processors can be found in their respective installation documentation. Intended Audience This guide is intended for Digital Customer Service. Structure of This Document Chapter 1, Hardware Installation, provides installation procedures for the fiberoptic and DECconnect hardware components between the VCS host and serviced systems. Chapter 2, Software Installation, provides the VCS software installation procedures for the host system and a work sheet for recording information about the serviced configuration. vii Conventions The VAXcluster Console System Installation Guide uses the following conventions: _____________________________________________________________ Convention_______Meaning_____________________________________ Italic Words or phrases appearing in italics indicate one of the following: _ Referencing of an associated document _ Emphasis on an important word or concept _ A variable Italic text is also used to indicate titles of manuals. Blue-green ink Blue-green ink indicates information that Bold you must enter from the keyboard or a screen object that you must choose. For online versions, user input is shown in bold. UPPERCASE TEXT Text in uppercase should be typed exactly as shown. lowercase text Text in lowercase is an item supplied by you, such as a file name or a node name. [ ] In format descriptions, brackets ([ ]) enclose an optional item. { } In format descriptions, braces ({ }) indicate that you must choose one item from the enclosed list. viii _____________________________________________________________ Convention_______Meaning_____________________________________ , . . . A comma followed by a horizontal ellipsis indicates that you can supply more than one item separated by commas. In procedures, a key name is shown enclosed to indicate that you press a key on the keyboard. In procedures, a sequence such as indicates that you must hold down the key labeled Ctrl while you press another key or _________________a_pointing_device_button.___________________ ix Associated Documents The following documents are either referred to in this manual or contain additional information pertaining to VCS: DECserver 200 Hardware Installation/Owner's Guide DECconnect System Planning and Configuration Guide DELNI Ethernet Local Network Interconnect Technical Manual H4000 Ethernet Installation Guide Guide to Terminal Server Manager Guide to Setting Up a VMS System Guide to VMS System Security Introduction to VMS System Management Introduction to VMS System Routines VAX 8800/8700/8550/8500 Console User's Guide VAX 8840/8830 Console User's Guide VAXcluster Console System Software Reference Manual VMS DCL Concepts Manual VMS License Management Utility Manual VMS System Manager's Manual Revision History This guide contains both hardware and software installation instructions. Previous versions of this guide were devoted exclusively to the hardware that supports VCS. The software installation information now in Chapter 2 was previously contained in the VAXcluster Console System Software Manual. x 1 ________________________________________________________________ Hardware Installation This chapter describes how to prepare and install fiberoptic and DECconnect interconnection kits between the VAXcluster Console System (VCS) host and serviced systems. Section 1.1 describes the direct connection and host initiated connection methods that can be used in the VCS hardware installation procedures. Also, described are precautionary guidelines to follow when the installation is performed on a VAX 8830/8840 system or a system that contains HSC devices. Section 1.2 describes how to install fiberoptic components on a serviced system. Section 1.3 describes how to install DECconnect components on a serviced system. 1.1 VCS Hardware Connection Methods and Precautions The VCS hardware can be connected by the following: _ The direct connection method described in Section 1.1.1 _ The host initiated connection method described in Section 1.1.2 Hardware Installation 1-1 1.1.1 VCS Hardware Direct Connection A VCS hardware direct connection consists of a host MicroVAX or VAXstation processor, up to 32 nodes serviced by the VCS software, and a fiberoptic (FOC) or DECconnect connection between the VCS host system and each serviced node. An example of a direct connection method is shown in Figure 1-1. 1-2 Hardware Installation 1.1.2 VCS Hardware Host Initiated Connection A VCS hardware host initiated connection consists of a VCS host system connected to an Ethernet network and serviced nodes that are connected by asynchronous fiberoptic or DECconnect hardware to a DECserver 200 terminal server. An example of a VCS host initiated hardware connection is shown in Figure 1-2. The VCS host is connected to an Ethernet network by a DELNI communications device. Figure 1-2 also shows four direct connections. Hardware Installation 1-3 Figure 1-3 shows another example of a VCS host initiated connection. The VCS host is connected to an H4000 Ethernet transceiver. Figure 1-3 also shows four direct connections. 1-4 Hardware Installation 1.1.3 VCS Hardware Installation Precautions Read Section 1.1.3.1 if the serviced system is a VAX 8830/8840 system. Read Section 1.1.3.2 if the serviced system contains HSC devices. 1.1.3.1 VAX 8830/8840 Precautions Connect the VCS host to a VAX 8830/8840 system by the central terminal line of a VAXconsole MicroVAX II. The central terminal line is the 25- pin TTA2: port located on the back of the VAXconsole pedestal system box. See Figure 1-4. For more information about the VAXconsole central terminal line, refer to the VAX 8840/8830 Console User's Guide. WARNING It is unsafe to connect VCS directly to the 9-pin OPA0: local console port of the VAXconsole MicroVAX II. Do not use the DECconnect components in the VCS fiberoptic kit for this purpose. Connect the VCS host system to the VAXconsole 25-pin TTA2: port instead. The following VAXconsole command may only be entered at the OPA0: local console port. { INITIALIZE } { OFF } PS-HW-0> POWER { ON } { STANDBY } { } { STATUS } If the VCS is connected to the OPA0: local console port, the POWER command could accidentally be entered through a remote VCS user interface while an engineer is working on the VAX 8830/8840 system. Hardware Installation 1-5 1.1.3.2 HSC Precautions Powering off the VCS host system or the DECserver causes line disruption similar to the line disruption caused by powering off a console terminal. These disruptions are random electrical signals resembling break signals generated on terminal lines. The inside panel of an HSC cabinet contains a switch with two positions, SECURE and ENABLE. Set this switch to the SECURE position, if currently set to the ENABLE position. CAUTION Powering off the VCS host system before ensuring that the SECURE/ENABLE switch on each HSC cabinet has been set correctly causes HSCs with incorrect switch settings to cease normal processing. 1-6 Hardware Installation 1.2 VCS Fiberoptic Components The VCS fiberoptic hardware consists of fiberoptic cable, fiberoptic converters, and power supplies for the fiberoptic converters. Each end of the cable needs a converter and a #12V DC power source. The following fiberoptic components are used for VCS: _ Fiberoptic cable (BN25J-XX) _ Fiberoptic converter kit (FOCHA-AE/IF), which contains the following components: Note Whether or not all the kit components are to be used depends on the kind of VCS-serviced system present. _ 2 fiberoptic converters (FOCFB-BB) _ 1 H7132 single-tap linear power supply _ 1 VCS disable switch (17-01314-01) _ 1 RS232 extension cable (BC14N) _ 1 9-pin female adapter (H8571-B) _ 1 25-pin male adapter (H8571-C) _ 1 2-foot DECconnect cable (BC16E-02) _ H7133 16-tap switching power supply The H7132 single-tap power supply is used to power the fiberoptic converter at the serviced node. The H7133 16-tap power supply is used to power the fiberoptic converters at the VCS host in a direct connection installa- tion or, at a terminal server (in a host initiated connection installation). One H7133 power supply can provide power to a maximum of 16 fiberoptic converters. One H7133 power supply can provide power to the fiberoptics connected to two DECserver 200 terminal servers if the servers are within eight feet of each other. Hardware Installation 1-7 1.2.1 Fiberoptic Cable Characteristics Fiberoptic cable connects a transmitter at one end and a receiver at the other end. The cable has two thin optical fibers (one to transmit and one to receive) that provide simultaneous bidirectional communication. Each fiberoptic core is reinforced with cladding and enclosed in an inner jacket. The two inner jackets are sealed in a light polyurethane outer jacket. Installing fiberoptic cables is different from installing traditional cables. Be careful not to break the fiberoptic core, but in many cases, normal cable installation techniques are adequate. Figure 1-5 shows basic fiberoptic cable structure. 1.2.2 Fiberoptic Cable Environmental Requirements Fiberoptic cables are made to last longer than coaxial cables. They also require different maintenance. Within reasonable limits, fiberoptic cables are immune from the deteriorating effects of condensation, humidity, and temperature extremes. Fiberoptic cable can withstand a crushing force of 400 lb/in. Basic fiberoptic cable requirements are as follows. _ Fiberoptic cable must not be kinked or crimped. _ Maintain operating temperature within +50°F to +160°F +10°C to +70°C). 1.2.3 Preparing the Host System To unpack and install the MicroVAX or VAXstation to be the VCS host system, follow the accompanying installation and configuration documentation. Include all add-on options such as the DHQ11, DZQ11, or CXY08 serial line interface devices. BA23, BA123, and BA213types of system enclosures are suitable for a VCS direct connection method of installation. Figure 1-6 shows the BA23 type of system enclosure and where to gain access to the device connectors, to which the fiberoptic converters are installed. 1-8 Hardware Installation Hardware Installation 1-9 Figure 1-7 shows the BA123 type of system enclosure and device connector locations. 1-10 Hardware Installation Figure 1-8 shows the BA213 type of system enclosure and device connector locations. Hardware Installation 1-11 1.2.4 Direct Connection Installation If you are performing a direct connection installation to the host VCS MicroVAX or workstation, read the following instructions. If performing a host initiated connection installation, read the instructions in Section 1.2.5. 1 Unpack the fiberoptic converters. 2 Unpack the H7133 16-tap power supply. 3 Peel back the label that covers the power supply voltage switch and check the voltage setting. If necessary, change the switch setting to match the voltage source. See Figure 1-9. CAUTION Damage to the power supply can occur if the voltage switch setting does not match the voltage source. 4 Place the H7133 16-tap power supply on or near the host system. For a BA23 or BA123 MicroVAX enclosure, run the DC power cable through the cable guides at the rear door of the enclosure. CAUTION Connect the DC power cable to the fiberoptic converter BEFORE applying AC power. Otherwise, the power supply can be damaged. 5 Find an AC power source for the H7133 16-tap power supply. Figure 1-10 shows AC power plug types. Note Do not plug the power supply into any AC power source in the VCS host system. 1-12 Hardware Installation Hardware Installation 1-13 6 Make the following connections: a Install each fiberoptic converter on any unused port on the processor bulkhead. For BA23 and BA123 enclosures, see Figure 1-11. For BA213 enclosures, see Figure 1-12. b Connect a DC power cable to each fiberoptic converter. See Figure 1-13. c Plug the power supply AC power cable into the AC power source. The H7133 power supply powers on when plugged into an AC power source. See Figure 1-13. CAUTION To prevent damage, do not bind the installed fiberoptic converters together with cable ties, tape, or any other method. To prevent overheating, the fiberoptic converters need air to circulate around them. Fiberoptic converters installed in a BA23 or BA123 system enclosure can also overheat when cables and converters block the air flow. 1-14 Hardware Installation The back of these system enclosures can be cooled by the following: _ Moving the system enclosure to a cooler area _ Opening or removing the back door Note An installed fiberoptic converter shows no visible indication of a successful connection. Refer to Section 1.2.7 for troubleshooting information. Hardware Installation 1-15 1.2.5 Host Initiated Connection Installation The following instructions describe how to prepare the fiberoptic hardware for a host initiated connection installation to a DECserver 200 terminal server. 1 Install the DECserver 200 terminal server. A DECserver 200 terminal server is shown in Figure 1-14. For installation procedures, use the following documents: _ DECserver 200 Installation/Owner's Guide _ DELNI Ethernet Local Network Interconnect Technical Manual _ H4000 Ethernet Installation Guide 2 Unpack the fiberoptic converters. 3 Unpack the H7133 16-tap power supply. 4 Peel back the label that covers the power supply voltage switch and check the voltage setting. If necessary, change the switch setting to match the voltage source. See Figure 1-9. CAUTION Damage to the power supply can occur if the voltage switch setting does not match the voltage source. 5 Place the H7133 power supply on or near the DECserver 200 terminal server. CAUTION Connect the DC power cable to the fiberoptic converter BEFORE applying AC power. Otherwise, the power supply can be damaged. 6 Find an AC power source for the H7133 16-tap power supply. Figure 1-10 shows AC power plug types. 7 Make the following connections. a Install each fiberoptic converter on any unused port on the DECserver 200 terminal server. See Figure 1-15. 1-16 Hardware Installation b Connect one power supply DC power cable to each fiberoptic converter as shown in Figure 1-13. c Connect the H7133 16-tap power supply AC power cord to the AC power source as shown in Figure 1-13. The H7133 power supply powers on when plugged into the power source. 1.2.6 Fiberoptic Installation at the Serviced Nodes This section describes how to install the fiberoptic hardware on VCS-serviced systems. If a serviced system is a VAX 8830/8840 system, read the precautions in Section 1.1.3.1. If a serviced system is an HSC storage controller, read the precautions in Section 1.1.3.2. For each serviced system, install the H7132 single-tap power supplies and the fiberoptic cables and converters as follows: 1 Plug the fiberoptic converter into the console port of the serviced system. 2 Place the H7132 single-tap power supply conveniently near the serviced system. 3 Connect the DC power cable to the fiberoptic converter. See Figure 1-16. CAUTION BEFORE applying AC power, connect the DC power cable to the fiberoptic converter. Otherwise, the power supply can be damaged. 4 Find an AC power source for the H7132 power supply. Figure 1-10 shows AC power plug types. Note Do not plug the power supply into any AC power source in the serviced system. 5 Plug the power supply AC power cable into the AC power source. See Figure 1-16. The H7132 power supply powers on when plugged into the AC power source. 6 Each fiberoptic cable is labeled with either a transmit strand or receive strand symbol on the connector as shown in Figure 1-17. Each fiberoptic connector jack contains a transmit jack and a receive jack. Each fiberoptic connector jack is labeled with either the transmit or receive symbol as shown in Figure 1-17. Install the fiberoptic cable between the fiberoptic converter at Hardware Installation 1-17 the host or DECserver and the fiberoptic converter at the serviced system. Match the symbols at the converter jacks with the symbols on the cables to connect the cable correctly. When a fiberoptic cable has been installed between the VCS host (or DECserver) and each system to be serviced by VCS, the configuration is ready to test. 1.2.6.1 Optional Extension Cable Installation The optional extension cable enables the fiberoptic converter to be placed away from the serviced node's console port. See Figure 1-18. Use the extension cable when the fiberoptic converter cannot be connected directly to the bulkhead for the following reasons: _ Not enough clearance exists to close the system enclosure door when the fiberoptic converter is installed, as with the VAX 8200 system. _ A ridge near the communications port prevents the fiberoptic converter from being connected directly to the communications port, as with the VAX 8700/8800's VAXconsole PRO380. 1-18 Hardware Installation Hardware Installation 1-19 To connect the VCS host to the VAXconsole PRO380 of a VAX 8700 or 8800 system, connect the extension cable to the COMM 1 port as shown in Figure 1-19. 1-20 Hardware Installation 1.2.6.2 Optional DECconnect Cabling Installation Use the optional DECconnect components provided to connect the fiberoptic converter to MicroVAX and VAXstation systems with the BA23, BA123, and BA213 types of enclosures. For the BA23 and BA123 types of enclosures, use the following optional components from the fiberoptic converter kit, as shown in Figure 1-20: _ 25-pin male adapter (H8571-C) _ 2-foot DECconnect cable (BC16E-02) _ 9-pin female adapter (H8571-B) For the BA213 type of enclosure, use: _ 25-pin male adapter (H8571-C) _ 2-foot DECconnect cable (BC16E-02) 1.2.6.3 Optional VCS Disable Switch Installation Use the optional VCS disable switch to change to a local console terminal at a serviced node should the VCS host fail. Figure 1-21 shows VCS disable switch cabling connections. The VCS disable switch has two settings: VCS and LOCAL. To connect the serviced system's console line to the VCS host, set the switch to the VCS setting. To connect the serviced system's console line to the local terminal, set the switch to the LOCAL setting. Hardware Installation 1-21 Install the VCS disable switch cable by performing the following procedures: 1 Plug the double connector female end into the console port of the serviced system. For a MicroVAX, plug the double connector female end into the H8571-C 25-pin adapter. 2 Plug the fiberoptic converter into the double connector end. 3 Plug the switch connector end into the terminal's communications port. 1.2.7 Fiberoptic Converter Troubleshooting If the fiberoptic converter is not working correctly, do the following: 1 Ensure that #12 voltages are present at each power supply DC output. 2 Ensure that the fiberoptic cable is connected correctly, as shown in Figure 1-17. 3 Replace the fiberoptic converter at the VCS end with a spare. If the spare does not correct the problem, reinstall the original converter and go to the next step. 4 Replace the fiberoptic converter at the serviced system with a spare. If the spare does not correct the problem, reinstall the original converter and go to the next step. 5 Replace the fiberoptic cable with a spare before stringing the new cable. Make sure this corrects the problem by testing the cables. Use the fiberoptic converter from the VCS host system and a terminal or a hand-held terminal (HHT). 1-22 Hardware Installation 1.3 VCS DECconnect Components The VCS DECconnect hardware consists of DECconnect cables and DECconnect adapters. Each cable end is connected to an adapter. The following DECconnect components are used for VCS: _ BC16E-xx DECconnect cable (xx denotes cable length) _ H8575-A 25-pin DECconnect adapter _ H8575-B 9-pin DECconnect adapter Figure 1-22 shows the DECconnect hardware cable and adapters. Hardware Installation 1-23 1.3.1 Preparing the Host System To unpack and install the MicroVAX or VAXstation to be the VCS host system, follow the accompanying installation and configuration documentation. Include all add-on options such as the DHQ11, DZQ11, or CXY08 serial line interface devices. BA23, BA123, and BA213 types of system enclosures are suitable for a VCS direct connection method of installation. Figure 1-23 shows the BA23 type of system enclosure and where to gain access the device connectors, to which the DECconnect adapters are installed. 1-24 Hardware Installation Figure 1-24 shows the BA123 type of system enclosure and device connector locations. Hardware Installation 1-25 Figure 1-25 shows the BA213 type of system enclosure and device connector locations. 1-26 Hardware Installation 1.3.2 Direct Connection Installation If performing a direct connection installation to the host VCS MicroVAX or workstation, read the following instructions. If performing a host initiated connection installation, read the instructions in Section 1.3.3. 1 Unpack the DECconnect adapters and cable. 2 Make the following connections: a Install each DECconnect adapter on any unused port on the processor bulkhead. For BA23 and BA123 enclosures, see Figure 1-26. For BA213 enclosures, see Figure 1-27. b Connect a DECconnect cable to each DECconnect adapter. See Figure 1-28. Hardware Installation 1-27 1.3.3 Host Initiated Connection Installation The following instructions describe how to prepare the DECconnect hardware for host initiated connection instal- lation to a DECserver 200 terminal server. 1 Install the DECserver 200 terminal server. A DECserver 200 terminal server is shown in Figure 1-29. For installation procedures use the following documents: _ DECserver 200 Installation/Owner's Guide _ DELNI Ethernet Local Network Interconnect Technical Manual _ H4000 Ethernet Installation Guide 2 Unpack the DECconnect adapters and cable. 3 Make the following connections: a Install each DECconnect adapter on any unused port on the DECserver 200 terminal server. b Connect one DECconnect cable to each DECconnect adapter as shown in Figure 1-30. See Figure 1-30. 1.3.4 DECconnect Installation at the Serviced Nodes This section describes how to install the DECconnect hardware on VCS-serviced systems. If a serviced system is a VAX 8830/8840 system, read the precautions in Section 1.1.3.1. If a serviced system is an HSC storage controller, read the precautions in Section 1.1.3.2. For each serviced system, install the DECconnect cables and adapters as follows: 1 Plug the DECconnect adapter into the console port of the serviced system. 2 Connect the DECconnect cable to the DECconnect adapter. See Figure 1-31. 1-28 Hardware Installation When a DECconnect cable has been installed between the VCS host (or DECserver) and each system to be serviced by VCS, the configuration is ready to test. 1.3.5 DECconnect Adapter Troubleshooting If the DECconnect adapter is not working correctly, do the following: 1 Ensure that the DECconnect adapter is seated correctly. 2 Ensure that the DECconnect cable ends are connected correctly. 3 Ensure that the baud rates at both ends are the same. 4 Ensure that the software parameters are set correctly. 5 Disconnect the DECconnect adapter from the serviced system and connect the adapter directly into a terminal port. Type some characters. If this does not correct the problem, reinstall the DECconnect adapter to the serviced system and continue to the next step. 6 Replace the DECconnect adapter at the VCS end with a spare. If the spare does not correct the problem, reinstall the original adapter and go to the next step. 7 Replace the DECconnect adapter at the serviced system with a spare. If the spare does not correct the problem, reinstall the original adapter and go to the next step. 8 Replace the DECconnect cable with a spare. Make sure this corrects the problem. Use the DECconnect adapter from the VCS host system and a terminal. Refer to the DECconnect System Planning and Configuration Guide for more troubleshooting information about DECconnect cables and adapters. Hardware Installation 1-29 2 ________________________________________________________________ Software Installation This chapter describes how to prepare for and perform the VCS Version 1.3 software installation on a VCS host system. The installation process is organized in the following manner: _ Section 2.1 describes the contents of the VCS software product kit. _ Section 2.2 describes the installation preparation of the VCS host system. _ Section 2.3 describes the installation preparation for VAX 8500, 8700, or 8800 series systems. _ Section 2.5 describes how to make site specific modifica- tions to the installed VCS software environment. _ Section 2.6 describes how to start up the VCS software _ Section 2.7 describes the final adjustments to make to the VCS serviced systems. 2.1 VCS Software Kit Inventory The VCS software kit consists of the VCS software distribu- tion medium and the VCS Product Authorization Key (PAK). The PAK is a piece of paper containing the VCS software license information that must be entered during the software installation. Software Installation 2-1 2.2 VCS Host System Preparation The VCS software installation requires a minimum of 20 minutes. This time includes reading the installation instructions, performing the actual installation using VMSINSTAL, and creating the site-specific information. If unfamiliar with VMSINSTAL, VMS, LAT, or the configuration of the serviced nodes, allow an additional two hours for reading the referenced documentation and gathering the required information. 2.2.1 Required Software VMS Version 5.3 must already be installed on the system before the VCS software can be installed. Enter the following command to determine what version of VMS is running. $ SHOW SYSTEM The first line of the response indicates the version of VMS. This version of VMS should contain the latest version of VAXTPU, which is included in the UTIL kit of the VAX/VMS full kit. Install the VCS software using VMSINSTAL, the standard VMS installation procedure. If unfamiliar with VMSINSTAL, read the information in the VMS System Manager's Manual. 2.2.2 Required Disk Space Before the VCS software can be installed, a minimum of 7000 free blocks on the system disk is required. Enter the following command to determine the number of free blocks on the system disk: $ SHOW DEVICE SYS$SYSDEVICE: The approximate disk block utilization requirements are: 7000 blocks, maximum peak disk-block utilization 2000 blocks, maximum net disk-block utilization In addition, the VCS software requires a minimum of 1.5 megabytes of disk space, per month, per node in the cluster for the logging function. This space is in addition to the normal disk space requirements of the VCS host system software. This should permit the VCS software to keep log data files for the system consoles managed by the VCS software for up to a month. 2-2 Software Installation 2.2.3 User Terminals The number of terminals needed to use the VCS software effectively depends on the user environment. If the site does not require simultaneous access to the consoles of the various nodes, a single terminal device as the console may be sufficient. However, if competition for access to the consoles is a norm at the site, additional user terminals should be available to the VCS software. Simultaneous access exists when the operations staff and Digital Customer Service engineers need to perform different tasks on different serviced nodes at the same time. Digital Field Service engineers need access to consoles through the VCS software with reasonable proximity to the processors they are working on. Network support greatly increases the flexibility and availability of the VCS software. Any terminal on the network can be used to access the VCS software. 2.2.4 SYSGEN Parameters Modifications to a number of SYSGEN parameters need to be performed for the VCS software to run properly. Place the following entries in the SYS$SYSTEM:MODPARAMS.DAT file to change the parameters. If the following values conflict with currently defined values, add the following entries only if their values are greater than the current values. _ TTY_ALTALARM = 320 _ TTY_ALTYPAHD = 1000 _ PQL_MDIOLM = 64 Add the following entry if using host initiated connection devices for console connections: _ LRPSIZE = 1504 Digital recommends adding the following entries if other software applications coexist with the VCS software product: _ SRPCOUNT = 410 _ IRPCOUNT = 300 _ LRPCOUNT = 25 Software Installation 2-3 Execute SYS$UPDATE:AUTOGEN.COM and reboot the host system to embed these values. Because the system is still in the preparation stage of the VCS software installation, rebooting of the system at this time may not be advisable. A reminder to initiate the AUTOGEN facility is provided at the end of the installation Section 2.6. For more information on the AUTOGEN facility, see the Guide to Setting Up a VMS System. 2.2.5 Host Initiated Connection Setup When setting up host initiated connections, the VCS host system and the DECserver 200 must reside on the same Ethernet. When an Ethernet is comprised of two separate Ethernet segments joined by a LAN Bridge device, the DECserver 200 is supported as a LAT interface device. The host initiated connection extends the logical I/O channels between the VCS host system and the terminal bulkheads located on a DECserver, over the Ethernet medium. The setup involves defining the DECserver port characteristics for host initiated connections and creating LTA devices on the VCS host system which are mapped to those ports. If planning to use host initiated connections, create the LTA devices before running the Configuration Editor. 2.2.5.1 Setting Up DECserver 200 Ports Before you set up the DECserver ports, the DECserver must be connected to the Ethernet and be ready to be loaded from a VAX system. A terminal must also be connected to the DECserver console port 1. Refer to the DECserver 200 Hardware Installation/Owner's Guide for additional information. Use the TSM in place of the local DECserver console terminal if the Terminal Server Manager (TSM) product is installed. Refer to the Guide to Terminal Server Manager for additional information about TSM. Unless aware of the actual characteristics of the DECserver, perform the following steps to initialize the DECserver to a known state. However, if other devices are also being serviced by the DECserver, skip step 1 to avoid resetting their port characteristics. 1 Use the red software reset switch (S1) located on the DECserver control/indicator back panel to restore factory- set characteristics to the DECserver's permanent database. To disconnect the DECserver power, remove the power cord from the back panel. While pressing the red software reset 2-4 Software Installation switch, simultaneously apply the power to the DECserver by reconnecting the power cord. Approximately one minute is required for the DECserver to be reloaded. The software reset switch is shown in Figure 2-1. 2 At the terminal keyboard, press Return twice to connect to the DECserver. The DECserver displays the following message: DECserver 200 Terminal Server V2.0 (BL29) -- LAT V5.1 Please type HELP if you need assistance Enter username> 3 Enter the user name. The DECserver responds with the Local> prompt. 4 Enter the factory-set password SYSTEM to enable the privileges on the DECserver: Local> SET PRIVILEGE Password> Enter the following command to change the factory-set privileged password: Local> DEFINE SERVER PRIVILEGED PASSWORD password 5 Locate the DECserver name by entering the command: Local> SHOW SERVER The second line of the response displays the address, name, and number of the DECserver. The DECserver name is required to define the LTA devices in Section 2.2.5.2. Use the command DEFINE SERVER NAME to change the default DECserver name. Perform the following steps for each DECserver port being used for the VCS host initiated connections: Note If Port 1 is used as a host initiated connection, perform the following steps on Port 1 last. Step 11 requires logging off the port and then repeating the entire procedure. Doing so and not performing the steps on Port 1 last prevents reconnection to Port 1 once disconnected. 6 Define the port name: Local> DEFINE PORT n NAME VCS0n Software Installation 2-5 In the following steps, n is always the DECserver port which can be in the range of 1 to 8. 7 Define the port speed: Local> DEFINE PORT n SPEED baud Baud is baud rate. 8 Define the reverse characteristic: Local> DEFINE PORT n ACCESS REMOTE Local> DEFINE PORT n BREAK REMOTE 9 Disable the AUTOBAUD, AUTOPROMPT, and BROADCAST character- istics: Local> DEFINE PORT n AUTOBAUD DISABLE Local> DEFINE PORT n AUTOPROMPT DISABLE Local> DEFINE PORT n BROADCAST DISABLE 10 Disable the default LAT group 0. Enable a unique LAT group number so that only the VCS host system controls this port: Local> DEFINE PORT n AUTHORIZE GROUP 0 DISABLE Local> DEFINE PORT n AUTHORIZE GROUP group ENABLE The LAT group number is required to define the LTA devices in Section 2.2.5.2. Define the same group number for all the VCS host initiated connection ports of the same DECserver. 11 Activate the port characteristics by logging off the port. Local> LOGOUT PORT n Repeat steps 6 through 11 for each DECserver port. 2.2.5.2 Using VCS$LTA.COM to Create LTA Devices The VCS$LTA.COM procedure invokes the LATCP program, which defines the LTA devices and maps the DECserver ports. The procedure uses the following parameters: @SYS$MANAGER:VCS$LTA.COM device-range server port-range group 2-6 Software Installation This DCL command requires that the following information: device- The numeric range allowed for LTA devices. The range range format is: number1[-number2] where number(1) is the beginning and number(2) is the ending of the range. The range can be in either ascending or descending order. The device numbers must be from 1 to 999. There are no spaces surrounding the hyphen character. The number of devices specified by this range must be equal to the number of ports specified by port-range. The VCS$LTA.COM procedure checks for and notifies of any discrepancies between the two ranges. server The name of the DECserver whose ports are mapped to the specified host initiated connection devices. LATCP enables a DECserver name to be specified before the name is entered into the DECserver's database (see Step 5 in Section 2.2.5.1). Ensure that the specified name is defined in the intended DECserver's database before starting the VCS software. Otherwise, the VCS software fails when trying to establish a connection to the fictitious DECserver. Software Installation 2-7 port-range The numeric range allowed for DECserver ports. The port range format is: number1[-number2] where number(1) is the beginning and number(2) is the ending of the range. The range can be in either ascending or descending order. The port numbers must be from 1 to 8 for a DECserver 200 device, and from 1 to 16 for a DECserver 300 device. Note that there are no spaces surrounding the hyphen character. The number of ports specified by this range must be equal to the number of devices specified by device-range. VCS$LTA.COM checks for and notifies of any discrepancies between the two ranges. group The unique LAT group number, defined for the ports in the DECserver and required for the VCS host system to gain control of those ports. (See Step 10 in Section 2.2.5.1). The following command examples show how to create host initiated connection devices using the VCS$LTA.COM procedure: 1 $ @SYS$MANAGER:VCS$LTA.COM 9 VCSDS0 8 34 Creates a single host initiated connection device LTA9. The device is mapped to the port VCS08 of the DECserver 200 named VCSDS0. The LAT group number 34 is required to gain control of the VCSDS0 port VCS08. 2 $ @SYS$MANAGER:VCS$LTA.COM 13-10 VCSDS1 1-4 29 Creates four host initiated connection devices LTA13, LTA12, LTA11, and LTA10. Next, these devices are mapped to the ports VCS01, VCS02, VCS03, and VCS04 of the DECserver 200 (named VCSDS1) in the specified order. The LAT group number 29 is required to gain control of the VCSDS1 ports VCS01 through VCS04. 2-8 Software Installation 2.3 Installation Preparation for the VAX 8500/8700/8800 Series Systems Note The information in this section is applicable only if you are installing the VCS software to manage a VAX 8500, 8700, or 8800 series system. If you are not doing so, continue reading at Section 2.4. These VAX series systems have either a PRO380 or a MicroVAX II as the console subsystem. This console subsystem is called the VAXconsole. The VAXconsole is a secondary computer that resides outside of the VAX system cabinets. Unlike other VAX systems (for example, VAX 8600) where the VCS software connects directly to the OPA0 port on the back of the system main cabinet, the VCS software is connected to this series of systems through the VAXconsole. 2.3.1 VAX 8500/8700/8800 The VCS software must be connected to one of these systems using the remote port of the VAXconsole PRO380. This port is located on the back of the VAXconsole system box and labeled COMM 1. A number of steps must be performed to set up the remote port on the VAXconsole before communications between the VAXconsole and the VCS host system can be established. For more information about the VAXconsole commands described in the following steps, refer to the VAX 8800/8700/8550/8500 Console User's Guide. Note The following steps are valid only for the PRO380 Console V9.3 software. Digital recommends that the VCS system and the VAXconsole not share the same OPA0 device. Sharing the same console device can cause data flow control problems which can hang the VAXconsole. Use the VCS system to utilize the OPA0 device since its purpose is to consolidate console management. The OPA5 device is normally not enabled by default as an operator terminal during VAX/VMS system startup. Thus, valuable information is not logged by the VCS system during the early stages of VAX/VMS system startup. Enabling the OPA5 device as an operator terminal has the added disadvantage of doubling the I/O load on the VAXconsole system. For this reason Digital does not recommend that the OPA5 device be enabled as an operator terminal for a great length of time. Software Installation 2-9 Perform the following steps at the VAXconsole local terminal keyboard: 1 Log into the system manager's account, SYSTEM. 2 Issue the following commands to connect the OPA5 device: $ MCR SYSGEN SYSGEN> CONNECT CONSOLE/REMOTE SYSGEN> EXIT The above commands should also be added to SYS$STARTUP:SYSTARTUP_ V5.COM for subsequent system reloads to connect the OPA5 device at startup. 3 Log out of the system manager's account. 4 Enter the VAXconsole Console Mode by pressing Ctrl/P. The VAXconsole responds with the >>> prompt. 5 Enter the EXIT command to return the console program from the Micromonitor to the Console Command Language. >>> EXIT 6 Press Main Screen to return to the VAXconsole PRO P/OS Stand-Alone Main Menu. 7 From the Stand-Alone Main Menu select PRO/Communications V3.0. 8 Press Set-Up to display the Communications Menu. 9 Select the Setup menu. 10 Select Setup Communications Line. 11 The Communication Line Setup Menu displays the current setup values. Adjust the values to equal those given in Figure 2-2. 12 Press Exit to accept the new values and return to the Setup Menu. 13 Select Save Setup to save the new values. 14 Select items Clear Comm to activate the new port characteristics, and Reset to reset the remote port. 15 Press Main Screen to return to the VAXconsole PRO P/OS Stand-Alone Main Menu. 2-10 Software Installation Figure 2-2 VAXconsole PRO380 Communication Line Setup Menu Communication Line Setup Menu Receive speed (baud) speed-of-your-choice Transmit speed (baud) Receive Character type 8 bits, no parity Number of stop bits 1 XOFF control Enabled Autoanswer Disabled Remote access Disabled Connection type Hardwired 16 Select CONSOLE/PRODCL to enter the console program. The Console Program takes about 20 seconds to be fully operational. When ready, the VAXconsole responds with the >>> prompt. 17 Enter the following command, which sets the remote port to NO MODEM: >>> DISABLE REMOTE MODEM NO MODEM is required because the connection between the VCS host system and the VAXconsole is a hardwired RS232 line. 18 Enter the following command, which enables the VCS software to communicate with the VAXconsole through the remote port as a user terminal: >>> ENABLE REMOTE USER 19 Enter the following command, which enables the VCS software to communicate with the VAXconsole through the remote port as a console terminal: >>> REMOTE CONSOLE 20 Enter the following command to set the remote VAXconsole port to OPA0: >>> SET REMOTE TERMINAL OPA0 21 Enter the following command to set the VAXconsole local terminal to OPA5: >>> SET TERMINAL OPA5 Software Installation 2-11 22 Enter the following command, which enters the VAXconsole into program I/O mode: >>> SET TERMINAL PROGRAM 23 Login to the system manager's account to verify that the OPA5 device is operational. The VAXconsole remote port has been successfully set up. 2.3.2 VAX 8830/8840 At each of the VAX 8830/8840 series systems, perform the following steps at the VAXconsole local terminal keyboard: 1 Enter the VAXconsole Console Mode by pressing Ctrl/P. The VAXconsole responds with the prompt PS-HW-0>. This is one of the prompts displayed by the VAXconsole, depending on the current console mode. See Chapter 2 of the VAX 8840/8830 Console User's Guide for additional information about the VAXcluster Console Mode. 2 Enter the following command, which enables the VCS host system to communicate with the VAX through the central terminal port. PS-HW-0> ENABLE CENTRAL CONSOLE 3 Enter the following command to place the VAXconsole into program I/O mode: PS-HW-0> SET TERMINAL PROGRAM 2.3.3 Preparation Work Sheets Use the work sheets in Figures 2-3 and 2-4 to record the information to be used by the VCS Configuration Editor. 2-12 Software Installation Software Installation 2-13 2.4 Installation of the VCS Software on the Host System The VCS software installation includes the registration of the product license information and the actual installation of the software. 2.4.1 License Registration License registration is required before the VCS software can be run. The license registration requires response to a series of questions prior to the software installation. Issue the following command to register and load the VCS software license: $ @SYS$UPDATE:VMSLICENSE VMS License Management Utility Options: 1. Register a Product Authorization Key 2. Amend an existing Product Authorization Key 3. Cancel an existing Product Authorization Key 4. List Product Authorization Keys 5. Modify an existing Product Authorization Key 9. Exit this procedure Type '?' at any prompt for a description of the information requested. Enter one of the above choices [1]: Do you have your Product Authorization Key? [YES]: The REGISTER option allows you add a new license to a license database. A Product Authorization Key (PAK) provides the product name and information you need to register the license. You must enter all the information provided by your PAK exactly as specified. PAK ID: Issuer [DEC]: Authorization Number []: AWS-ZK-88582-1 PRODUCT ID: Product Name []: VAXCLUSTER-CONSOLE Producer [DEC]: NUMBER OF UNITS: Number of Units []: 3200 KEY LEVEL: Version []: 1.3 2-14 Software Installation KEY TERMINATION DATE: Key Termination Date []: 30-JUN-1990 RATING: Availability Table Code []: Activity Table Code []: CONSTANT=100 MISCELLANEOUS: Key Options []: Product Token []: Hardware-Id []: Checksum []: 1- INDP-KHJJ-KIFB-COAF License Database File: SYS$COMMON:[SYSEXE]LMF$LICENSE.LDB Issuer: DEC Authorization: AWS-ZK-88582-1 Producer: DEC Product Name: VAXCLUSTER-CONSOLE Units: 3200 Date: Version: 1.3 Termination Date: 30-JUN-1990 Availability: Activity: CONSTANT=100 Options: Token: Hardware ID: Checksum: 1-INDP-KHJJ-KIFB-COAF Is this information correct? [YES]: Registering VAXCLUSTER-CONSOLE license in SYS$COMMON:[SYSEXE]LMF$LICENSE.LDB... Do you want to LOAD this license on this system? [YES]: %LICENSE-I-LOADED, DEC VAXCLUSTER-CONSOLE was successfully loaded with 0 units VMS License Management Utility Options: 1. Register a Product Authorization Key 2. Amend an existing Product Authorization Key 3. Cancel an existing Product Authorization Key 4. List Product Authorization Keys 5. Modify an existing Product Authorization Key 9. Exit this procedure Type '?' at any prompt for a description of the information requested. Enter one of the above choices [1]: 9 $ Software Installation 2-15 2.4.2 Installation Procedure Install the VCS software by performing the following steps: 1 Log in to the system manager's account, SYSTEM. 2 Issue the following command to identify the appropriate local load device for the software kit medium: $ SHOW DEVICE /FULL 2-16 Software Installation 3 Enter the following command to run the VMSINSTAL software: $ @SYS$UPDATE:VMSINSTAL VCS013 device where device is the local load device identified in the previous step. If the VMSINSTAL software detects a system environment that may impede installation, you are asked if you want to continue with the installation. The VCS software installation does not require that DECnet be shut down or that interactive logins be disabled. If you are updating from VCS version 1.2, you do not have to shut it down for this installation. This procedure will shut down the current and restart with the new VCS software once the installation completes successfully. If the VMSINSTAL software detects that DECnet is running or users are logged in, and displays the prompt: * Do you want to continue anyway [NO]? Answer YES. 4 VMSINSTAL asks: * Are you satisfied with the backup of your system disk [YES]? If a backup of the system disk is available that would enable a rebuild of the system disk in case of a drastic failure, answer YES and press Return. 5 VMSINSTAL asks: Please mount the first volume of the set on device. * Are you ready? Load the distribution tape or cartridge labeled VCS013 on the specified load device. Answer YES and press Return when the device is ready for installation. VMSINSTAL responds: %MOUNT-I-MOUNTED, VCS mounted on device 6 VMSINSTAL begins the installation and displays a message similar to the following: The following products will be processed: VCS V1.3 Beginning installation of VCS V1.3 at 12:04 Software Installation 2-17 7 VMSINSTAL restores the first save set and moves the release notes to directory SYS$HELP. %VMSINSTAL-I-RESTORE, Restoring product save set A ... %VMSINSTAL-I-RELMOVED, The product's release notes have been successfully moved to SYS$HELP. 8 VMSINSTAL asks: * Do you want to purge files replaced by this installation [YES]? If the installation is an update of VCS from version 1.2 to 1.3, and you want to purge the older generations of the product files, answer YES and press Return. 9 VMSINSTAL asks: * Do you want to run the IVP after the installation [YES]? If you want to execute the installation verification procedure, answer YES and press Return. 10 VMSINSTAL reminds you, with the following message, that the installation verification procedure can also be run afterward: The VCS Installation Verification Procedure can also be executed manually after the installation by using the command: $ @SYS$TEST:VCS$IVP.COM 11 VMSINSTAL asks: Product license information Product: VAXCLUSTER-CONSOLE Producer: DEC Version: 1.3 Release Date: 11-APR-1990 * Does this product have an authorization key registered and loaded? The product authorization key must be registered and loaded before you can activate the VCS software. If you have done so, answer YES and press Return. Otherwise, VMSINSTAL prompts you to do so: 2-18 Software Installation ********************** W A R N I N G ********************* At the completion of the VCS software installation, you must use the following command: $ @SYS$UPDATE:VMSLICENSE to register and load the VCS product authorization key before starting the software. Software Installation 2-19 12 VMSINSTAL verifies that the system disk contains a minimum of 7000 free blocks for the installation of the product. If not, VMSINSTAL notifies you and terminates the installation procedure with the following message: %VMSINSTAL-E-NOSPACE, VCS requires 7000 blocks for the installation 13 If sufficient disk space is found, VMSINSTAL restores the second save set. %VMSINSTAL-I-RESTORE, Restoring product save set B ... 14 VMSINSTAL asks: In addition to a set of default icons, VCS allows you to design your own icons representing various serviced resources. To extend this collection of default icons, you need to install their icon bitmap DDIF source files. * Do you want to install the default icon bitmaps [YES]? The VCS icon conversion tool uses these files in conjunction with the newly created icon bitmap DDIF source files to produce a new set of icons used by the VCS Configuration Editor and the Central Control Coordinator Interface. These icon bitmap DDIF source files are restored to the directory VCS$ICONS: and take up approximately 106 disk blocks. If you want to install these files, answer YES and press Return. 15 VMSINSTAL notifies you that the following product specific directories are to be created: The following directories are created to contain VCS files: SYS$SPECIFIC:[VCS] SYS$SPECIFIC:[VCS.ENS] SYS$SPECIFIC:[VCS.LOG] SYS$SPECIFIC:[SYSHLP.EXAMPLES.VCS] SYS$SPECIFIC:[SYSHLP.EXAMPLES.VCS.ICONS] SYS$SPECIFIC:[SYSTEST.VCS$IVP] 16 VMSINSTAL begins the next phase of the installation by moving the installed files to their target directories and displaying the following message: 2-20 Software Installation All requested VCS V1.3-000 save sets are restored. %VMSINSTAL-I-MOVEFILES, Files will now be moved to their target directories... 17 VMSINSTAL activates the product startup procedure to install the image files: VAXcluster Console System Startup Procedure Install VCS images... Software Installation 2-21 18 VMSINSTAL creates a template configuration data file and skips steps 19 to 22 if the installation is being performed as an original product installation: A template configuration file is now created to contain only the scan event records. The commands that are to be used to create this template configuration file can be found in the Configuration Editor indirect command file: VCS$EXAMPLES:VCS$CONFIGURATION_TEMPLATE.COM You need to use the Configuration Editor to create additional configuration information describing the serviced nodes before starting VCS. Use the following command to do so: $ VCS EDIT CONFIGURATION 19 VMSINSTAL indicates that conversion of data is to be performed if updating from VCS version 1.2, The VCS 1.2 configuration and scan files require conversion to version 1.3 format. These files along with the VCS security information, defined in the system Rights List database, will be consolidated into a single configuration file in binary format. You must also convert other locally created scan files into the new format. At the prompt, please list these files separated by commas and use wild-card characters in the file names where appropriate. Terminate with a carriage-return if there are no other files to be converted. * Other VCS scan files: Enter a list of file names (use wild-card characters where appropriate) followed by Return. 20 The following VMSINSTAL message explains what happens before the actual conversion is carried out: Before the conversion, a backup copy of the configuration file SYS$MANAGER:VCS$CONFIGURATION.DAT_012 is created for possible fall-back. After a successful conversion, the VCS 1.2 locally created scan files along with the Digital supplied ones will be deleted from the system. The VCS 1.2 security information will also be removed from the Rights List database. * Press Return to begin the conversion 2-22 Software Installation Enter Return to initiate the conversion process. Software Installation 2-23 21 VMSINSTAL creates a backup copy of the older configuration file and begins the conversion: Please wait, it will take approximately 5 minutes to convert the following files: Directory SYS$SYSROOT:[SYSMGR] VCS$SCAN_EVENTS.DAT;1 3 14-FEB-1989 09:12:33.39 VCS$SCAN_HSC50.DAT;1 5 14-FEB-1989 09:12:34.51 VCS$SCAN_HSC70.DAT;1 7 14-FEB-1989 09:12:35.15 VCS$SCAN_KL10.DAT;1 3 14-FEB-1989 09:12:35.70 VCS$SCAN_KS10.DAT;1 3 14-FEB-1989 09:12:36.01 VCS$SCAN_LANBRIDGE.DAT;1 3 14-FEB-1989 09:12:36.50 VCS$SCAN_LPS40.DAT;1 8 14-FEB-1989 09:12:37.29 VCS$SCAN_MICROVAX2000.DAT;1 2 14-FEB-1989 09:12:37.80 VCS$SCAN_MICROVAX3000.DAT;1 2 14-FEB-1989 09:12:38.12 VCS$SCAN_MICROVAXII.DAT;1 3 14-FEB-1989 09:12:38.38 VCS$SCAN_RSTSV9.DAT;1 5 14-FEB-1989 09:12:39.23 VCS$SCAN_TOPS10.DAT;1 3 14-FEB-1989 09:12:39.77 VCS$SCAN_TOPS20.DAT;1 4 14-FEB-1989 09:12:40.05 VCS$SCAN_UNIX.DAT;1 25 14-FEB-1989 09:12:40.57 VCS$SCAN_VAX6200.DAT;1 2 14-FEB-1989 09:12:41.05 VCS$SCAN_VAX750.DAT;1 3 14-FEB-1989 09:12:41.31 VCS$SCAN_VAX780.DAT;1 3 14-FEB-1989 09:12:42.04 VCS$SCAN_VAX8200.DAT;1 2 14-FEB-1989 09:12:42.29 VCS$SCAN_VAX8300.DAT;1 2 14-FEB-1989 09:12:42.52 VCS$SCAN_VAX8500.DAT;1 6 14-FEB-1989 09:12:42.77 VCS$SCAN_VAX8600.DAT;1 7 14-FEB-1989 09:12:43.32 VCS$SCAN_VAX8700.DAT;1 6 14-FEB-1989 09:12:43.59 VCS$SCAN_VAX8800.DAT;1 6 14-FEB-1989 09:12:43.82 VCS$SCAN_VITALINK.DAT;1 3 14-FEB-1989 09:12:44.44 VCS$SCAN_VMSV4.DAT;1 6 14-FEB-1989 09:12:45.10 VCS$SCAN_VMSV5.DAT;1 6 14-FEB-1989 09:12:45.38 22 The following VMSINSTAL message is displayed at comple- tion: All specified files are converted successfully. Deleting the obsolete scan files. 2-24 Software Installation 23 VMSINSTAL creates the template ENS data file: The default event notification system data file is now created to contain a number of pre-defined actions and events. The commands that are to be used to create this data file can be found in the event notification system editor command file: VCS$EXAMPLES:VCS$ENS_TEMPLATE.COM You need to use the event notification system editor to create additional actions and events. Use the following command to do so: $ RUN SYS$SYSTEM:VCS$ENS_EDITOR 24 VMSINSTAL prompts you to issue the following commands, if not already done: Insert the following command into SYS$STARTUP:SYSTARTUP_V5.COM: $ @SYS$STARTUP:VCS$STARTUP SYSTEM and Insert the following command into SYS$MANAGER:SYSHUTDWN.COM: $ VCS SHUTDOWN 25 VMSINSTAL verifies the SYSGEN parameters SCSNODE and SCSSYSTEMID and displays the following prompt: You must define the SYSGEN parameters SCSNODE and SCSSYSTEMID for the VCS host system. The VCS Central Control Coordinator Interface makes use of this information in the creation of subprocesses. Define these parameters as follows: SCSNODE = quoted-node-name SCSSYSTEMID = (1024 * DECnet-node-area) + DECnet-node-number Thus, for node PETER whose DECnet node number is 1.484, its definitions of these parameters are: SCSNODE = "PETER" SCSSYSTEMID = 1508 ! (1024 * 1) + 484 26 The following VMSINSTAL message reminds you of the option to remove the product from the system if you want to: To deinstall the VCS product, execute the following command: $ @SYS$MANAGER:VCS$DEINSTAL.COM Software Installation 2-25 27 If you chose to perform the installation verification procedure earlier, VMSINSTAL performs the procedure at this time and displays the following: **************************************************************** * VCS 1.3 Installation Verification Procedure * **************************************************************** Begin... Complete! 28 The product installation procedure is complete. VMSINSTAL displays a message similar to the following: Installation of VCS V1.3 completed at 12:12 VMSINSTAL procedure done at 12:13 2.4.3 VCS Installation Log This section consists of the following sample log of a VCS software installation: $ @SYS$UPDATE:VMSINSTAL VCS013 MUA0: VAX/VMS Software Product Installation Procedure V5.3 It is 14-MAR-1990 at 11:58. Enter a question mark (?) at any time for help. %VMSINSTAL-W-ACTIVE, The following processes are still active: USER DECW$WM_1 DECW$WM_2 DECW$TE_1 * Do you want to continue anyway [NO]? YES * Are you satisfied with the backup of your system disk [YES]? YES Please mount the first volume of the set on MUA0:. * Are you ready? YES %MOUNT-I-MOUNTED, VCS mounted on _MISVCS$MUA0: The following products will be processed: VCS V1.3 Beginning installation of VCS V1.3 at 12:04 2-26 Software Installation %VMSINSTAL-I-RESTORE, Restoring product save set A ... %VMSINSTAL-I-RELMOVED, The product's release notes have been successfully moved to SYS$HELP. * Do you want to purge files replaced by this installation [YES]? * Do you want to run the IVP after the installation [YES]? The VCS Installation Verification Procedure can also be executed manually after the installation by using the command: $ @SYS$TEST:VCS$IVP.COM Product license information Product: VAXCLUSTER-CONSOLE Producer: DEC Version: 1.3 Release Date: 11-APR-1990 * Does this product have an authorization key registered and loaded? yes %VMSINSTAL-I-RESTORE, Restoring product save set B ... In addition to a set of default icons, VCS allows you to design your own icons representing various serviced resources. To extend this collection of default icons, you need to install their icon bitmap DDIF source files. * Do you want to install the default icon bitmaps [YES]? %VMSINSTAL-I-RESTORE, Restoring product save set C ... Software Installation 2-27 The following directories are created to contain VCS files: SYS$SPECIFIC:[VCS] SYS$SPECIFIC:[VCS.ENS] SYS$SPECIFIC:[VCS.LOG] SYS$SPECIFIC:[SYSHLP.EXAMPLES.VCS] SYS$SPECIFIC:[SYSHLP.EXAMPLES.VCS.ICONS] SYS$SPECIFIC:[SYSTEST.VCS$IVP] %VMSINSTAL-I-SYSDIR, This product creates system directory [VCS.ENS]. 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:[VCS.ENS]/OWNER_UIC=[1,4] /PROTECTION=(S:RWED,O:RWED,G:RE,W) %VMSINSTAL-I-SYSDIR, This product creates system directory [VCS.LOG]. 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:[VCS.LOG]/OWNER_UIC=[1,4] /PROTECTION=(S:RWED,O:RWED,G:RE,W) %VMSINSTAL-I-SYSDIR, This product creates system directory [SYSHLP.EXAMPLES.VCS]. 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:[SYSHLP.EXAMPLES.VCS] /OWNER_UIC=[1,4]/PROTECTION=(S:RWED,O:RWED,G:RE,W) %VMSINSTAL-I-SYSDIR, This product creates system directory [SYSHLP.EXAMPLES.VCS.ICONS]. 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:[SYSHLP.EXAMPLES.VCS.ICONS] /OWNER_UIC=[1,4]/PROTECTION=(S:RWED,O:RWED,G:RE,W) %VMSINSTAL-I-SYSDIR, This product creates system directory [SYSTEST.VCS$IVP]. 2-28 Software Installation 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:[SYSTEST.VCS$IVP]/OWNER_UIC=[1,4] /PROTECTION=(S:RWED,O:RWED,G:RE,W) All requested VCS V1.3-000 save sets are restored. Software Installation 2-29 %VMSINSTAL-I-MOVEFILES, Files will now be moved to their target directories... VAXcluster Console System Startup Procedure Install VCS images... **************************************************************** * VCS 1.3 Installation Verification Procedure * **************************************************************** Begin... Complete! Installation of VCS V1.3 completed at 12:12 VMSINSTAL procedure done at 12:13 $ 2.5 Site-Specific Modifications to the Installed VCS Environment This section describes the site-specific modifications that must be performed after the VCS software has been installed on the VCS host system but before the software can be started. Some of these are modifications that must be made to the VCS software site-specific startup procedure SYS$MANAGER:VCS$SITE_SPECIFIC.COM. If present in the SYS$MANAGER directory, the SYS$MANAGER:VCS$SITE_ SPECIFIC.COM is automatically invoked by the VCS software startup procedure SYS$STARTUP:VCS$STARTUP.COM before the VCS software processes are started. 2.5.1 Creating a Configuration File Use the Configuration Editor to create the VCS Configuration File SYS$MANAGER:VCS$CONFIGURATION.DAT before starting the VCS software. This file describes all of the information necessary for the VCS software to manage and service the nodes in the configuration. Refer to VAXcluster Console System Software Manual for information about what to include in a Configuration File and how to use the Configuration Editor. If you are planning to use host initiated connections, create the LTA devices before running the Configuration Editor. See Section 2.2. 2-30 Software Installation 2.5.2 Console Line Communications Characteristics The default character format for all terminal lines connected to the VCS host system is /NOEIGHTBIT, and is defined by the SYSGEN parameter TTY_DEFCHAR. The VCS software makes use of this terminal characteristic as defined in TTY_ DEFCHAR. If the system manager leaves the default value to be /NOEIGHTBIT, all console lines managed by the VCS software on the host system inherit that characteristic. If installing the VCS software to control a system that requires the character format of its console port to be eight-bit, include the following command in the VCS software site-specific startup SYS$MANAGER:VCS$SITE_SPECIFIC.COM procedure: $ SET TERMINAL device /PERMANENT /EIGHTBIT In this command, device is the terminal port on the VCS host system that is configured for the serviced system requiring eight-bit character format. The default setting for all terminal lines on the VCS host system is /NOPARITY. If you are installing the VCS software to control a system that requires a parity console line, include the following command in the VCS software site- specific startup procedure SYS$MANAGER:VCS$SITE_SPECIFIC.COM: $ SET TERMINAL device /PERMANENT /PARITY 2.5.3 VCS Logical Names The VCS software defines and accepts user-defined logical names. This section describes these logical names and their uses. 2.5.3.1 Node Name Grouping by Logical Name Some VCS software commands can operate on one or more nodes while others can operate on single nodes only. The node names recognized by the VCS software are those names listed in the VCS Configuration File. Any VCS software command that accepts a single node name can also accept a logical name for each node name. Do not use VCS as a logical name. The VCS REVIEW command does not work as expected if VCS is used as a logical name. For example, type the following: $ DEFINE NODE1 PEPPER Software Installation 2-31 The following two commands are synonymous and enable connection to the same system: $ VCS CONNECT NODE1 $ VCS CONNECT PEPPER Any VCS software command that accepts a list of node names also accepts a list of logical names for each node name. One logical name can be used with one node name, several node names, or any combination thereof. For example, assign the following logical names as node names: $ DEFINE NODE1 PEPPER $ DEFINE NODE2 HEART $ DEFINE NODE3 HSC001 $ DEFINE NODE4 HSC002 $ DEFINE VAX NODE1,NODE2 $ DEFINE HSC NODE3,NODE4 $ DEFINE ALL VAX,HSC The following commands are synonymous and can be used to monitor the same four systems - PEPPER, HEART, HSC001, and HSC002: $ VCS MONITOR PEPPER,HEART,HSC001,HSC002 $ VCS MONITOR NODE1,NODE2,NODE3,NODE4 $ VCS MONITOR VAX,HSC $ VCS MONITOR VAX,HSC001,HSC002 $ VCS MONITOR ALL Note that node names can be abbreviated; logical names cannot. The default node name used by the commands VCS ACCESS, VCS COORDINATE, VCS MONITOR, VCS RECORD, and VCS REVIEW is VCS$ALL_NODES, a system-wide logical name that specifies all the nodes in the current VCS software configuration. For more information about these commands, see the VAXcluster Console System Software Manual. The logical names can be defined in any logical name table accessible to the user process. To make logical names available on a system-wide basis, define these logical names at system startup by including the DEFINE/SYSTEM/EXECUTIVE commands in The VCS software site-specific startup procedure. For example, include the commands, that were listed previously in this section: 2-32 Software Installation $ DEFINE/SYSTEM/EXECUTIVE NODE1 PEPPER $ DEFINE/SYSTEM/EXECUTIVE NODE2 HEART $ DEFINE/SYSTEM/EXECUTIVE NODE3 HSC001 $ DEFINE/SYSTEM/EXECUTIVE NODE4 HSC002 $ DEFINE/SYSTEM/EXECUTIVE VAX NODE1,NODE2 $ DEFINE/SYSTEM/EXECUTIVE HSC NODE3,NODE4 $ DEFINE/SYSTEM/EXECUTIVE ALL VAX,HSC 2.5.3.2 VCS Logical Name Definitions The following system-wide logical names are defined by VCS. Their definitions determine the behavior of the various VCS software components. You may re-define some of these logical names in the site-specific procedure SYS$MANAGER:VCS$SITE_ SPECIFIC.COM to tailor your local environment. Table 2-1 Logical Names ________________________________________________________________ VCS$+ The top level directory of the VCS related subdirectories containing various data and log files. VCS$ALL_NODES+ The list of all nodes that are currently in the VCS configuration. VCS$CONFIGURATION+ The VCS configuration file name that is currently active. VCS$DISPLAY+ The list of all DECwindows display servers where the C3 Interface is started up automatically when VCS is activated. VCS$ENS The directory which contains the ENS data, command, and executable image files. VCS$ENS_DATA_FILE+ The ENS data file name that is currently active. ________________________________________________________________ +These logical names are defined by the VCS software components and should not be redefined or the product may behave incorrectly. (continued on next page) Software Installation 2-33 Table 2-1 (Cont.) Logical Names ________________________________________________________________ VCS$ENS_LOG The directory which contains the ENS process output and error log files. VCS$EVENT_LOG_ The initial file allocation quantity in ALLOCATION blocks for the VCS event log file. This logical name defines the default value of the FAB$L_ALQ field in the RMS FAB data structure when the VCS event log file is first created. VCS$EVENT_LOG_ The default extension quantity in blocks EXTENSION for the VCS event log file. This logical name defines the default value of the FAB$L_DEQ field in the RMS FAB data structure when the VCS event log file is first created. Note that a larger extension quantity will help ensure a contiguous file. A contiguous file helps improve the speed of the REVIEW commands. Consider the VCS$EVENT_ LOG_EXTENSION when deciding on the values for the allocation and extension quantities. VCS$EXAMPLES+ The directory which contains the VCS sample source codes and other example files. VCS$GROUP_cluster- The list of all nodes that were defined name+ to belong to the Cluster cluster-name in the VCS configuration file. Cluster-name can be used in any command that requires a list of nodes. VCS$ICONS The directory which contains the DIGITAL supplied icon image DDIF files. ________________________________________________________________ +These logical names are defined by the VCS software components and should not be redefined or the product may behave incorrectly. (continued on next page) 2-34 Software Installation Table 2-1 (Cont.) Logical Names ________________________________________________________________ VCS$LOG+ The directory where the console and event log files are created and maintained by the VCS software. VCS$LOG_ALLOCATION The initial file allocation quantity in blocks for the VCS console log file. This logical name defines the default value of the FAB$L_ALQ field in the RMS FAB data structure when the VCS console log file is first created. VCS$LOG_EXTENSION The default extension quantity in blocks for the VCS console log file. This logical name defines the default value of the FAB$L_DEQ field in the RMS FAB data structure when the VCS console log file is first created. Note that a larger extension quantity will help ensure a contiguous file. A contiguous file helps to improve the speed of the REVIEW commands. Consider this when deciding on the values for the allocation and extension quantities. VCS$MAILBOX+ The inter-process communication mailbox device. VCS$PRIVATE A unique identifier which is used by the VCS software to construct various inter- process communication facility names and devices when two or more nodes are running the VCS software in a VAXcluster environment. ________________________________________________________________ +These logical names are defined by the VCS software components and should not be redefined or the product may behave incorrectly. (continued on next page) Software Installation 2-35 Table 2-1 (Cont.) Logical Names ________________________________________________________________ VCS$PROCESS_C3 If TRUE, the Central Control Coordinator process is started in the VCS startup sequence. The default is TRUE. VCS$PROCESS_ELOG If TRUE, the VCS Event Logger process VCS$ELOG is started in the VCS startup sequence. The default is TRUE. VCS$PROCESS_ENS If TRUE, the VCS Event Notification System processes are started in the VCS startup sequence. The default is TRUE. VCS$PROCESS_SCANNER If TRUE, the Data Scanner process VCS$SCANNER is started in the VCS startup sequence. The default is TRUE. VCS$STANDBY If TRUE, the VCS software will operate in a fail-over mode on an appropriately set up platform configuration. VCS$TERMINAL_DEFAULT The file name containing the customized features for the DECterm windows created ________________________by_the_C3_Interface.____________________ 2-36 Software Installation 2.5.4 Setting Console Terminal Characteristics Specific parameters must be set for all lines that connect to the VCS host system. Execute the following command for each VAX system startup procedure for each serviced node: $ SET TERMINAL OPA0: /PERMANENT /FULLDUP /HOSTSYNC /TTSYNC Check the console line speed setting at each node to ensure that the console line speed matches the VCS host system terminal port speed. If you are installing the VCS software to service a system without VMS, make sure that the system console software provides the same set of characteristics for the console terminal line. The equivalent console terminal characteristics are: /FULLDUP Indicates the mode of operation is full-duplex. /HOSTSYNC Enables a system without VMS to control the flow of data from the VCS software. With this characteristic, the system can stop transmission from the VCS software by generating an XOFF when the input buffer is full. When the system's input buffer is empty, generating an XON resumes transmission by the VCS software. /TTSYNC Enables the system to respond to the flow control requests from the VCS software. With this characteristic the system can stop transmission to the VCS software when an XOFF is received. Transmission from the VCS software resumes when an XON is received. 2.5.5 Starting the VCS Software at System Reboot Add the following command to the SYS$STARTUP:SYSTARTUP_V5.COM to start the VCS software during system reboot: $ @SYS$STARTUP:VCS$STARTUP.COM SYSTEM See Section 2.5.5.1 for the description of VCS$STARTUP.COM. Software Installation 2-37 Do not submit the VCS software startup command procedure VCS$STARTUP.COM in batch mode. The VCS software must allocate the terminal lines in SYSTARTUP_V5.COM before any other process. The following scenario can occur if another process allocates the terminal lines in STARTUP_V5.COM before the VCS software. Noise on an unallocated line can be mistaken for a login request and result in the LOGINOUT process prompting for a user name. This action normally causes a timeout at a terminal. However, a processor at each end of the terminal line can cause an infinite and alternating execution of the VCS host system and serviced system's LOGINOUT process, as shown in the following example: Username: Password: . . . If not using host initiated connection devices, start the VCS software at any point within the SYS$STARTUP:SYSTARTUP_ V5.COM command procedure. If using host initiated connection devices, must create the LTA devices before starting the VCS software. Use the command procedure SYS$MANAGER:VCS$LTA.COM to create the LTA devices. The LTA devices require the LAT software and can only be created after DECnet software is started. Thus, the order of product startup is as follows: 1 DECnet 2 LAT 3 VCS The following sample commands show how the components are started in SYS$STARTUP:SYSTARTUP_V5.COM: . . . $ IF F$SEARCH("SYS$SYSTEM:NETACP.EXE") .NES. "" - THEN @SYS$MANAGER:STARTNET $ @SYS$MANAGER:VCS$LTA 1-8 LAT40 1-8 54 $ @SYS$STARTUP:VCS$STARTUP SYSTEM . . . 2-38 Software Installation 2.5.5.1 VCS$STARTUP.COM The SYS$STARTUP:VCS$STARTUP.COM enables the VCS system manager to start and control detached VCS software processes. This procedure also establishes the environment in which the VCS software operates in. Software Installation 2-39 The procedure has the following parameters: $ @SYS$STARTUP:VCS$STARTUP.COM option priority device where: option is one of the following options: INSTALL indicates that the VCS software images are installed. This option does not start the VCS software. SYSTEM indicates that the VCS software images are installed and then the complete the VCS software startup sequence are performed. This option must be specified in the system startup procedure SYS$STARTUP:SYSTARTUP_V5.COM. or process names: VCS$ELOG indicates that only the Event Logger process is started. VCS$ENS indicates that only the ENS processes are started. VCS$IODL indicates that only the I/O Data Logger process is started. VCS$C3 indicates that only the Central Control Coordinator process are started. VCS$RECORDER indicates that a process is started. Multiple Interface processes may be run, each directing console data to a different output terminal device. VCS$SCANNER indicates that only the Data Scanner process is started. 2-40 Software Installation If option is omitted, that is, specified as " ", the complete VCS software startup sequence begins. This is the recommended option when starting the VCS software interactively. priority represents the VCS software process priority. By default, all the VCS software processes inherit the current priority of the process that executes VCS$STARTUP.COM. If specifying a priority with the SYSTEM option, all VCS software processes inherit that value as their process base priority. device If option is VCS$RECORDER, device represents the VCS Record Interface terminal output device name. If option is VCS$C3, device is optional and represents the DECwindows graphics server display. If device is specified, the C3 Interface is started only on that DECwindows display. 2.5.5.2 VCS Startup Sequence The complete VCS software startup sequence, executed by VCS$STARTUP.COM, is described in the following steps: 1 Define the specific logical names (for example, VCS$EXAMPLES). 2 Execute the site-specific procedure SYS$MANAGER:VCS$SITE_ SPECIFIC.COM to set up the site requirements, if present. 3 Shut down the VCS software, if currently running. 4 Install the VCS software images, if required. 5 The I/O Data Logger process, VCS$IODL, begins. Error messages are written to the file SYS$MANAGER:VCS$IODL_ OUTPUT.LOG. 6 The Data Scanner process, VCS$SCANNER, begins. Error messages are written to the file SYS$MANAGER:VCS$SCANNER_ OUTPUT.LOG. Define the VCS logical name VCS$PROCESS_SCANNER to be FALSE in the SYS$MANAGER:VCS$SITE_SPECIFIC.COM procedure to inhibit the Data Scanner process from being started in the sequence, 7 The Event Logger process, VCS$ELOG, begins. Error messages are written to the file SYS$MANAGER:VCS$ELOG_OUTPUT.LOG. Software Installation 2-41 Define the VCS logical name VCS$PROCESS_ELOG to be FALSE in the SYS$MANAGER:VCS$SITE_SPECIFIC.COM procedure to inhibit the Event Logger process from being started in the sequence. 8 The ENS processes are started. Error messages are written to the file SYS$MANAGER:VCS$ENS_OUTPUT.LOG. To inhibit the ENS processes from being started in the sequence, define the VCS logical name VCS$PROCESS_ENS to be FALSE in the SYS$MANAGER:VCS$SITE_SPECIFIC.COM procedure. 9 The VCS software starts the Central Control Coordinator Interface process, VCS$C3_display If the VCS host system is a VAXstation or a display destination has been defined in the configuration file. Error messages are written to the file SYS$MANAGER:VCS$C3_display_OUTPUT.LOG. Define the VCS logical name, VCS$PROCESS_C3 to be FALSE in the SYS$MANAGER:VCS$SITE_SPECIFIC.COM procedure to inhibit the Central Control Coordinator Interface processes from being started in the sequence. 10 If the parameter device is specified or the logical name VCS$RECORDER_TERMINAL is defined to point to an output terminal. The VCS software starts the Recorder Interface process VCS$REC_device and writes error messages to the file SYS$MANAGER:VCS$REC_device_OUTPUT.LOG. 2.5.6 Stopping the VCS Software at System Shutdown Add the following command to SYS$MANAGER:SYSHUTDWN.COM to terminate communications between the VCS host system and the serviced systems: $ VCS SHUTDOWN Remember to execute the site-specific shutdown procedure when shutting down the VCS host system. 2.6 Starting the VCS Software The VCS software can now be started for the first time. The two ways to start the VCS software are: _ Reboot the system and automatically start the VCS software at system startup. _ Manually start up the VCS software. 2-42 Software Installation If the SYSGEN parameters have been adjusted, as described in Section 2.2.4 or Section 2.5.2, run the AUTOGEN procedure by entering the command: $ @SYS$UPDATE:AUTOGEN SAVPARAMS REBOOT This command automatically generates the new SYSGEN parameters. AUTOGEN automatically reboots the VCS host system. When the system is rebooted, the VCS software is started as a part of the system startup procedure. When the VCS host system completes the system startup, log into the system manager's account, SYSTEM in Section 2.7. To start up the VCS software manually, enter the following command: $ @SYS$STARTUP:VCS$STARTUP.COM SYSTEM Software Installation 2-43 2.7 Final Setup Although the VCS software is operational, additional procedures must be performed before the installation is complete. 2.7.1 VAX 8500/8700/8800 Note Read the information in this section only if installing the VCS software to manage a VAX 8530, 8550, 8700, or 8800 system. For each of these VAX systems, perform the following procedures at the VCS host system: Note The following steps are valid only for the VAXconsole PRO380 Console V9.3 Software. 1 Enter the command: $ VCS CONNECT node-name where node-name is the name of a VAX 8500/8700/8800 series system. Any keystrokes entered are forwarded to the VAXconsole PRO380. 2 Press Return to confirm that the communication path between the VCS host system and the VAXconsole PRO380 has been established successfully. The >>> prompt is displayed. 3 Enter the following command to share the same OPA0 device with the VAXconsole local terminal: >>> SET TERMINAL OPA0 4 Enter the following command to enter the VAXconsole remote port into program I/O mode: >>> SET TERMINAL PROGRAM 5 Press Ctrl/G to return to the VCS host system. Now all of the console functions to control the VAX 8500/8700/8800 series system from a VCS software user interface can be performed with the exception of the following commands. However, the following commands can be entered from the VAXconsole PRO380 terminal keyboard: _ EXIT 2-44 Software Installation { OFF } _ POWER { ON } { STANDBY } { } _ DISABLE PRINTER _ { CONSOLE } _ ENABLE REMOTE { USER } { } Software Installation 2-45 2.7.2 VAX 8830/8840 Note Read the information in this section only if the VCS software has been installed to manage one or more VAX 8830/8840 series systems. For each of these VAX systems, perform the following steps at the VCS host system: 1 Enter the following command: $ VCS CONNECT node-name where node-name is the name of a VAX 8830/8840 series system. Any keystrokes entered are forwarded to the VAXconsole MicroVAX II. 2 Press Return to confirm that the communication path between the VCS host system and the VAXconsole MicroVAX II has been established successfully. The PS-HW-0> prompt is displayed. 3 Enter the following command to share the same OPA0 device with the VAXconsole local terminal: PS-HW-0> SET TERMINAL OPA0 4 Enter the following command to enter the VAXconsole remote port into program I/O mode: PS-HW-0> SET TERMINAL PROGRAM 5 Press Ctrl/G to return to the VCS host system. Now all of the console functions to control the VAX 8830/8840 series system from a VCS software user interface can be performed. However, enter the commands at the VAXconsole MicroVAX II terminal keyboard: _ EXIT { INITIALIZE } { OFF } _ POWER { ON } { STANDBY } { } { STATUS } 2-46 Software Installation ___________________________________________________________ Index A BA23 device connectors, 1-9 AC power plug types, 1-13 (fig), 1-24 (fig) (fig) BA23 system, 1-8, 1-21, 1-24 B C BA123 device connectors, Central terminal line, 1-5 1-10 (fig), 1-25 (fig) Console extension cable BA123 system, 1-8, 1-21, connections, 1-19 (fig) 1-24 BA213 device connectors, D 1-11 (fig), 1-26 (fig) DECconnect adapter BA213 enclosure bulkhead troubleshooting, 1-29 connection, 1-14 (fig), DECconnect adapter and 1-27 (fig) cable connections, 1-27 BA213 system, 1-8, 1-21, (fig), 1-29 (fig) 1-24 DECconnect cable, 1-21 BA23/BA123 enclosure DECconnect cable and bulkhead connection, adapters, 1-23 (fig) 1-14 (fig), 1-27 (fig) DECconnect components, 1-23 Index-1 DECconnect components Fiberoptic converter, 1-7, (Cont.) 1-14, 1-17 adapters, 1-23, 1-27, kit components, 1-21 1-28 troubleshooting, 1-22 cables, 1-23, 1-27, 1-28 Fiberoptic extension cable, installation at serviced 1-18 nodes, 1-28 Final setup, 2-44 DECserver 200 back panel, H 2-5 (fig) DECserver 200 connections, H7132 power supply, 1-7, 1-16 (fig), 1-28 (fig) 1-17 DECserver 200 terminal H7132 power supply server, 1-7, 1-16, 1-16 connections, 1-17 (fig) (fig), 1-28, 1-28 (fig) H7133 power supply, 1-7, port setup, 2-4 1-12, 1-16 Direct connection, 1-2 H7133 power supply DECconnect installation, connections, 1-12 (fig), 1-27 1-15 (fig) fiberoptic installation, H8571-B adapter, 1-21 1-12 H8571-C adapter, 1-21 F Hardware connection methods , 1-1 Fiberoptic cable, 1-17 Hardware installation characteristics, 1-8 precautions, 1-5 environmental HSC precautions, 1-6 requirements, 1-8 VAX 8830/8840 precautions with DECconnect , 1-5 Components, 1-21 Host initiated connection, Fiberoptic cable structure, 1-3, 1-16 1-8 (fig) DECconnect installation, Fiberoptic components, 1-7 1-28 installation at serviced setup, 2-4 nodes, 1-17 with DELNI, 1-3 (fig) Fiberoptic connector jacks, with H4000, 1-4 (fig) 1-17, 1-18 (fig) Host system preparation, 2-2 Index-2 Host system preparation Site-specific modifications (Cont.) (Cont.) DECconnect installation, console terminal 1-24 characteristics fiberoptic installation, settings, 2-37 1-8 to the installed VCS required disk space, 2-2 environment, 2-30 required software, 2-2 VCS logical names, 2-31 SYSGEN parameters, 2-3 definitions, 2-33 user terminals, 2-3 Node name grouping, HSC storage controller, 2-31 1-17, 1-28 VCS software startup, see Hardware installation 2-37 precautions Software installation L installation procedure, 2-16 Logical names, 2-33 (tab) license registration, 2-14 O on host system, 2-14 Optional DECconnect cabling starting the VCS software , 1-21 (fig) , 2-42 VAX 8500/8700/8800 P preparation, 2-9 VCS installation log, Product authorization key, 2-26 2-1 Software kit inventory, 2-1 S SYS$MANAGER:VCS$CONFIGURATION.DAT , 2-30 Site-specific modifications SYS$MANAGER:VCS$SITE_ configuration file SPECIFIC.COM, 2-30 creation, 2-30 SYS$SYSTEM:MODPARAMS.DAT, console line 2-3 communications SYS$UPDATE:AUTOGEN.COM, 2-4 characteristics, 2-31 SYSGEN parameters, 2-3 Index-3 V VAXconsole PRO380 VAX 8200, 1-18 communication line setup VAX 8500/8700/8800 menu, 2-11 (fig) final setup, 2-44 VCS$LTA.COM remote port set, 2-9 LTA device creation, 2-6 VAX 8700/8800, 1-18 VCS$STARTUP.COM, 2-37, 2-39 VAX 8830/8840, 1-17, 1-28 VCS direct connection method, 1-2 (fig) see Hardware installation VCS disable switch, 1-21 precautions VCS disable switch cabling, final setup, 2-46 1-21 (fig) remote port setup, 2-12 VCS software shutdown, 2-42 VAXconsole central terminal VCS startup sequence, 2-41 line, 1-6 (fig) VMSINSTAL, 2-2 VAXconsole PRO380, 1-18 VAXconsole PRO380 COMM 1 W port, 1-20 (fig) Work sheets, 2-12, 2-13 (fig) Index-4