DIGITAL_ Network Process Failover (NPF) Installation Guide Part Number: AA-RF2AA-TE September 1998 September 1998 September 1998 Product Version: DIGITAL Network Process Failover V1.0 Operating System and Version: DIGITAL UNIX 4.0D This guide describes how to install DIGITAL Network Process Failover software product kit on the DIGITAL UNIX operating system. Digital Equipment Corporation Digital Equipment Corporation Digital Equipment Corporation Maynard, Massachusetts Maynard, Massachusetts Maynard, Massachusetts c Digital Equipment Corporation 1998. All c Digital Equipment Corporation 1998. All c Digital Equipment Corporation 1998. All rights reserved. rights reserved. rights reserved. Digital Equipment Corporation makes no representations that the use of its products in the manner described in this publication will not infringe on existing or future patents, nor do the descriptions contained in this publication imply the granting of licenses to make, use, or sell equipment or software in accordance with the description. Possession, use, or copying of the software described in this publication is authorized only pursuant to a valid written license from DIGITAL or an authorized sublicensor. The following are trademarks of Digital Equipment Corporation: ALL-IN-1, Alpha AXP, AlphaGeneration, AlphaServer, AltaVista, ATMworks, AXP, Bookreader, CDA, DDIS, DEC, DEC Ada, DEC Fortran, DEC FUSE, DECnet, DECstation, DECsystem, DECterm, DECUS, DECwindows, DTIF, Massbus, MicroVAX, OpenVMS, POLYCENTER, Q-bus, StorageWorks, TruCluster, ULTRIX, ULTRIX Mail Connection, ULTRIX Worksystem Software, UNIBUS, VAX, VAXstation, VMS, XUI, and the DIGITAL logo. UNIX is a registered trademark in the United States and other countries, licensed exclusively through X/Open Company, Ltd. Prestoserve is a trademark of Legato Systems, Inc.; the trademark and software are licensed to Digital Equipment Corporation by Legato Systems, Inc. All other trademarks and registered trademarks are the property of their respective holders. c Copyright Alcatel CIT, 1998. All Rights Reserved. Possession, use, duplication or dissemination of the software and media is authorized only pursuant to a valid written license from Alcatel CIT. DIGITAL conducts its business in a manner that conserves the environment and protects the safety and health of its employees, customers, and the community. Contents Contents Contents About This Document About This Document About This Document Purpose .........................................i Audience ........................................i Organization ....................................i Related Documents .............................iii Reader's Comments .............................iii Location of Online Documentation ...............vi Conventions ...................................vii 1. Introduction 1. Introduction 1. Introduction 1.1. Introduction to DIGITAL Network Process Failover.........................................1-1 1.1.1. The Network Process Failover Platform ..1-2 1.1.2. Pilot and Non-Pilot Stations ...........1-2 1.2. Installation Procedure Overview.............1-3 2. Planning Your Installation 2. Planning Your Installation 2. Planning Your Installation 2.1. Planning Decisions..........................2-1 2.1.1. Pilot Stations .........................2-1 2.1.2. DIGITAL NPF Subsets ....................2-3 2.1.3. Disk Space Requirements ................2-5 2.1.4. DIGITAL UNIX Dependencies ..............2-6 2.2. License Information.........................2-9 2.3. Installation Media.........................2-10 2.4. General Restrictions and Considerations....2-11 3. Pre 3. Pre 3. Pre- - -Installation Tasks Installation Tasks Installation Tasks 3.1. Preinstallation Overview....................3-1 3.2. Prerequisites...............................3-2 3.2.1. Pre-installation Tasks Table ...........3-2 3.3. Install the DIGITAL UNIX Operating System ...3-3 3.4. Configuring Basic Network Services ..........3-5 3.5. Registering a DIGITAL Network Process Failover License ..........................................3-5 3.6. DIGITAL UNIX Patches ........................3-6 3.7. Logical Storage Manager and AdvFS Setup 3-6 ..... 3.8. TruCluster ASE Configuration ................3-8 3.8.1. Initializing a blank ASE database 3-9 ....... 3.8.2. Configuring Network Interfaces.........3-10 3.8.3. Adding an ASE Service for NPF..........3-19 4. Full Installation 4. Full Installation 4. Full Installation 4.1. Installation Overview .......................4-1 4.2. Installing DIGITAL Network Process Failover 4-1 . 4.3. Installation Media ..........................4-3 4.4. Installation Steps ..........................4-4 4.5. /etc/routes file ...........................4-17 4.6. /etc/fstab file ............................4-17 4.7. RIS Installation ...........................4-19 4.8. Installation Errors ........................4-19 Contents 5. Base Installation 5. Base Installation 5. Base Installation 5.1. Non-Pilot Overview..........................5-1 5.2. Installation Media..........................5-2 5.3. Installation Steps..........................5-4 5.4. RIS Installation............................5-9 5.5. Installation Errors........................5-10 6. RIS Installation 6. RIS Installation 6. RIS Installation 6.1. Installing Network Process Failover for RIS 6-1 . Appendix A Appendix A Appendix A Appendix B Appendix B Appendix B Glossary Glossary Glossary Index Index Index Contents About This Document About This Document About This Document Purpose Purpose Purpose The DIGITAL Network Process Failover Installation Guide describes how to install the DIGITAL Network Process Failover Software Product kit. It guides you through the process of planning your installation, completing the required preinstallation tasks and installing the NPF software. Audience Audience Audience This document is for system administrators who will install, configure, and administer the DIGITAL Network Process Failover Software. The instructions in this document assume that you are experienced in maintaining your hardware, operating system, and network. Organization Organization Organization This document is organized as follows: Provides an overview of the Chapter installation process 1 Provides details of how to plan Chapter your installation 2 Chapter Provides step step - by - 3 instructions for preinstallation tasks Chapter Describes how to install NPF for 4 a Pilot Station Chapter Describes how to install a Non- Pilot Station 5 Chapter Describes how to install NPF on 6 a RIS server for distribution Summarizes system file changes Appendi associated with the DIGITAL x A Network Process Failover installation Appendi Provides a detailed listing of x B NPF files contained in each subset ii ii ii About This Document Related Documents Related Documents Related Documents Consult the following DIGITAL Network Process Failover manuals for further information regarding configuration, administration and programming: . DIGITAL Network Process Failover - Release Notes DIGITAL Network Process Failover - . Configuration Guide DIGITAL Network Process Failover Manager . - Administrator Guide DIGITAL Network Process Failover - . Programmer's Guide DIGITAL Network Process Failover - . Reference Manual In addition, you should have available the following manuals from the DIGITAL UNIX documentation set: Installation Guide . Release Notes . . System Administration Network Administration . . TruCluster Administration Guide Reader's Comments Reader's Comments Reader's Comments DIGITAL welcomes your comments on this and other NPF manuals. You can send your comments in any of the following ways: About This Document iii iii iii . Fax: + 33 (0) 4 50 64 01 39 Attn: DIGITAL NPF Engineering Team, AEO . Tel.: + 33 (0) 4 50 09 41 11 . E-mail: npf_team@digital.com iv iv iv About This Document . Mail Address: DIGITAL NPF Engineering Team DIGITAL Equipment France Parc des Glaisins - BP 439 74944 Annecy-le-Vieux cedex France A Reader's Comment form is located on your system in the following location: /usr/doc/readers_comment.txt Please include the following information with your comments: . The full title of the book and its order number The section numbers and page numbers of . the information on which you are commenting The version of DIGITAL NPF you are using . . The version of DIGITAL UNIX you are using . The type of processor running the DIGITAL UNIX software Please address technical questions to your local system vendor or to the appropriate DIGITAL technical support office. Information provided with the software media explains how to send problem reports to DIGITAL. About This Document v v v Location of Online Documentation Location of Online Documentation Location of Online Documentation Each book in the DIGITAL Network Process Failover documentation set is shipped as a set of Adobe Postscript_ files (PS) in the /.../npf100/doc/ps directory on the corresponding Layered Products CD-ROM. You can use the showps program to display these books. vi vi vi About This Document To access the DIGITAL Network Process Failover documentation from the viewer, click on the Open icon in the showps main window and enter the following file location in the Open Location text entry field: mountpoint / /npf100/doc/ps/booktitle.ps Conventions Conventions Conventions The following typographical conventions are used in this manual: Symbol Symbol Symbol Description Description Description A number sign represents the # superuser prompt. Boldface type in interactive cat cat cat % examples indicates typed user input. Italic (slanted) type indicates File values, placeholders, and function argument names . A vertical ellipsis indicates . that a portion of an example that would normally appear is . not shown (1) A cross cat reference to a reference - page includes the appropriate section number in parentheses. For example, cat(1) indicates that you can find information on the cat command in Section 1 of the reference pages. NPF Abbreviation for DIGITAL Network Process Failover. About This Document vii vii vii 1. 1. 1. Introduction Introduction Introduction Welcome to the DIGITAL Network Process Failover Installation Guide. This chapter contains the following information: . Introduction to DIGITAL NPF . Installation Procedure Overview The following chapters describe how to plan your installation, prepare for installation and install the software. Detailed information about configuring, administering and programming NPF is included in the other documentation accompanying DIGITAL NPF. 1. 1. 1.1. 1. 1. Introduction to DIGITAL Network Process Introduction to DIGITAL Network Process Introduction to DIGITAL Network Process Failover Failover Failover DIGITAL NPF allows you to build high- availability applications with real-time switch-over capabilities. While ASE and similar clustering technology provides hardware level failover protection, NPF offers process-level failover protection for your applications. DIGITAL NPF is an extensible architecture that offers programmers the basic services required for the provision of reliable services to applications. The NPF API can be used to build applications that leverage this functionality. 1. 1. 1.1. 1. 1. The Network Process Failover The Network Process Failover The Network Process Failover 1. 1. 1. Platform Platform Platform Each DIGITAL NPF platform consists of at least two Pilot stations and up to two non-Pilot stations. The active Pilot station controls and administers the platform, while the standby Pilot station can take over in case of failure. Figure Figure Figure Typical NPF Platform Typical NPF Platform Typical NPF Platform 1 1 1 1 1 1- - - ASE PILOT PILOT NPF (Active) (Standby NPF NPF NPF NON- NON- PILOT PILOT 1. 1. 1. 1. 1. 1. Pilot and Non-Pilot Stations Pilot and Non-Pilot Stations Pilot and Non-Pilot Stations 2. 2. 2. Each member station within the platform must have the DIGITAL NPF Core Middleware installed. This mandatory subset includes the following components: . NPF Operating System Extensions (NOS) . Data Manager (DM) . Communications Services (CS) . UNIX Middleware Administrator (XMA) While these core NPF components are installed on every station in the platform, there is a need for platform level management features to be present on some stations to configure and administer 1-2 1-2 1-2Introduction the platform. Pilot stations are stations that include an additional global management software component. There is one active Pilot station and one standby Pilot station, which communicate with the local NPF agent on each station. - - - 1 1 1 Figure Figure Figure Pilot and Non-Pilot Stations Pilot and Non-Pilot Stations Pilot and Non-Pilot Stations 2 2 2 Non-Pilot Pilot XMA User Application NPF Mgr.User Ap CS DM NPF Core NPF Core NOS DIGITAL UNIX DIGITAL UNIX The Platform-level manager can be the NPF Configuration component supplied as part of the DIGITAL NPF kit, third party provided or custom-developed. Further information on the NPF Architecture is provided in the NPF Programmer's Guide. Installation Procedure Overview Installation Procedure Overview Installation Procedure Overview 2. 2. 2. 1. 1. 1. The rest of this guide describes the installation procedure for DIGITAL NPF. Installing DIGITAL NPF involves the following steps: Task Task Task See See See Planning your Chapter 2 installation Completing Chapter 3 Preinstallation tasks Software Chapter 4 installation for PILOT Stations Software Chapter 5 installation for Introduction 1-3 1-3 1-3 Task Task Task See See See non-Pilot Stations Software Chapter 6 installation on RIS Server 1-4 1-4 1-4Introduction 2. 2. 2. Planning Your Installation Planning Your Installation Planning Your Installation This chapter describes how to plan for your DIGITAL NPF installation. It includes the following topics: . Planning Decisions . DIGITAL NPF Subsets . Disk Space Requirements . DIGITAL UNIX dependencies . License Information . Installation Media 2. 2. 2.1. 1. 1. Planning Decisions Planning Decisions Planning Decisions Before you begin installing NPF, there are a number of important decisions to be made which will affect your installation preparations. Key decisions include: . deciding on pilot and non-pilot stations . understanding the subsets available . identifying all minimum requirements . determining installation methodology (CD or RIS) 2. 2. 2.1. 1. 1.1. 1. 1. Pilot Stations Pilot Stations Pilot Stations The first decision is to identify which two stations will be designated as the pilot stations. It is not necessary at this point to decide which will be the active pilot station and which will be the standby pilot station. Pilot stations have additional dependencies that require the installation and configuration of the software listed below. Note Note Note This chapter assumes you will be using the supplied DIGITAL Configuration Manager. If you are not, then you will have to install your own platform-level management component and configure your stations as non-pilot stations. The following table lists prerequisites depending on station type: - - - 2 2 2 Table Table Table Software Prerequisites Software Prerequisites Software Prerequisites 1 1 1 DIGITAL PILOT DIGITAL PILOT DIGITAL PILOT Other Other Other STATIONS STATIONS STATIONS Stations Stations Stations1 1 1 DIGITAL M M UNIX 4.0D2 NFS M O ASE M O LSM M O AdvFS M O M=Mandatory, O = Optional 1 Includes non-pilot stations and pilot stations not using DIGITAL NPF Manager 2 See the NPF Release Notes for the latest information about DIGITAL UNIX 4.0D 2-2 2-2 2-2Planning Your Installation 2. 2. 2. DIGITAL NPF Subsets DIGITAL NPF Subsets DIGITAL NPF Subsets 1. 1. 1.2. 2. 2. In order to facilitate customized installations, DIGITAL NPF software is supplied in several subsets. Table 2-2 below lists the DIGITAL Network Process Failover subsets that are available for installation. Planning Your Installation 2-3 2-3 2-3 During the installation procedure you will be asked to choose which subsets you wish to install. This listing is included here to help you plan your installation requirements. The actual installation procedure is described in more detail in Chapters 4 and 5. Table Table Table NPF Subsets NPF Subsets NPF Subsets - - -2 2 2 2 2 2 Subset Name Subset Name Subset Name Descriptio Descriptio Descriptio Mandato Mandato Mandato Contents Contents Contents n n n ry/ ry/ ry/ Optiona Optiona Optiona l l l NPFBASE100 DIGITAL Base M Network components Process , shared Failover libraries, Core and Middleware daemons; start up - scripts NPFCONF100 DIGITAL Platform O - Network level Process Configurat Failover ion and Configurat Management ion components Environmen t NPFDEV100 DIGITAL .h files O Network and Process libraries Failover for Developmen applicatio t n Environmen developmen t t NPFUNMAN100 DIGITAL Reference O Network manual Process Failover Unsupporte man man man d pages 2-4 2-4 2-4Planning Your Installation Subset Name Subset Name Subset Name Descriptio Descriptio Descriptio Mandato Mandato Mandato Contents Contents Contents n n n ry/ ry/ ry/ Optiona Optiona Optiona l l l NPFEXAMPLES100 Programmin Example O g examples code NPFUNSUPPORTED1 Unsupporte Monitoring O 00 d tools utilities 2. 2. 2. Disk Space Requirements Disk Space Requirements Disk Space Requirements 3. 3. 3. 1. 1. 1. Depending on the subsets you choose to install, the amount of disk space required will vary. Please note that the installation will be aborted if insufficient disk space is available for the chosen options. The following table details the approximate disk space requirements, in megabytes (MB), for each Version 1.0 DIGITAL Network Process Failover subset in the root ( , and /usr ), / file systems. /var Table Table Table Disk Space Requirements Disk Space Requirements Disk Space Requirements - - -3 3 3 2 2 2 Subset Subset Subset Root Root Root /va /va /va /usr /usr /usr Totals Totals Totals (/) (/) (/) r r r (MB) (MB) (MB) (MB) (MB) (MB) (MB) (MB) (MB) (MB (MB (MB ) ) ) NPFBASE100 0.2 1.2 4.4 5.8 5.8 5.8 NPFCONF100 - 5.0 - 5.0 5.0 5.0 NPFDEV100 - 0.7 0.1 0.8 0.8 0.8 NPFUNMAN100 - 0.1 - 0.1 0.1 0.1 NPFEXAMPLES100 - 0.1 - 0.1 0.1 0.1 NPFUNSUPPORTED100 - 0.2 0.2 0.2 0.2 - Totals Totals Totals 0.2 0.2 0.2 1.3 1.3 1.3 10.5 10.5 10.5 12.0 12.0 12.0 Note Note Note These requirements are for DIGITAL NPF installation only. Remember to ensure that you have sufficient space for your applications and data. Planning Your Installation 2-5 2-5 2-5 2. 2. 2.1. 1. 1. DIGITAL UNIX DIGITAL UNIX DIGITAL UNIX 4. 4. 4. Dependencies Dependencies Dependencies DIGITAL NPF is designed to run on the DIGITAL UNIX platform. Table 2-4 describes the DIGITAL Network Process Failover product dependencies on DIGITAL UNIX and layered product subsets. Subsets listed as are mandatory; these M subsets must be installed on a system in order to install DIGITAL Network Process Failover product. Subsets listed as O are optional; the "Comment" column describes why you might choose to load one or more of these subsets. See the DIGITAL UNIX Installation Guide for more information on these subsets and their dependencies. Note Note Note Refer to the DIGITAL NPF Release Notes for details about the Patch level required. 2-6 2-6 2-6Planning Your Installation Table Table Table 2 2 2 4 4 4 DIGITAL UNIX Dependencies DIGITAL UNIX Dependencies DIGITAL UNIX Dependencies - - - Subset Subset Subset Descripti Descripti Descripti Requir Requir Requir Comment Comment Comment on on on ed/ ed/ ed/ Option Option Option al al al OSFBASE Base M - System OSFBIN Standard M - Kernel Objects OSFBINCOM Kernel M - Header and Common Files OSFHWBIN Hardware M - Kernel Modules OSFHWBINCOM Hardware M - Kernel Header and Common Files OSFCLINET Basic M - Networkin g Services OSFCMPLRS Compiler M - Back End OSFNFS NFSR M - Utilities OSFATMBASE ATM O Required if Commands Asynchronous Transfer Mode (ATM) hardware is detected during the installation process. OSFATMBIN ATM O Required if ATM Kernel hardware is Modules detected during the installation process. Planning Your Installation 2-7 2-7 2-7 Subset Subset Subset Descripti Descripti Descripti Requir Requir Requir Comment Comment Comment on on on ed/ ed/ ed/ Option Option Option al al al OSFATMBINCOM ATM O Used for kernel Kernel software Header development. and Common Files OSFATMBINOBJEC ATM O Used for kernel T Kernel software Object development. OSFDCMT Documenta O Required by tion DIGITAL Network Preparati Process Failover on Tools Reference Pages subset NPFUNMAN ( ). OSFMANxxx Reference O Some DIGITAL Pages Network Process subsets Failover (base reference pages system) refer to the DIGITAL UNIX operating system reference pages. OSFLSMBASE Logical O Required if Storage setting up ASE Manager services that (LSM) use LSM. OSFLSMBINCOM Logical O Required if Storage setting up ASE Manager services that Kernel use LSM. Header and Common Files OSFLSMBIN LSM O Required if Kernel setting up ASE Modules services that use LSM. 2-8 2-8 2-8Planning Your Installation Subset Subset Subset Descripti Descripti Descripti Requir Requir Requir Comment Comment Comment on on on ed/ ed/ ed/ Option Option Option al al al OSFLSMX11 Logical O Required to Storage launch the LSM Manager graphical user GUI interface (GUI) from the Cluster Monitor. OSFADVFS POLYCTR M Required for the AdvFS POLYCENTER Advanced File System (AdvFS). OSFADVFSBIN POLYCTR M Required for AdvFS AdvFS. Kernel Objects OSFRIS Remote O Required to use Installat a cluster member ion as a RIS server. Service OSFINET Additiona O Required to use l a cluster member Networkin as a RIS server. g Services License Information License Information License Information 2. 2. 2. 2. 2. 2. DIGITAL NPF is licensed separately from DIGITAL UNIX and TruCluster. The DIGITAL Network Process Failover product is available with the following licenses: . DIGITAL Network Process Failover Run- Time License . DIGITAL Network Process Failover Development License You must decide on, and acquire, the number of each type of license you require. Contact your DIGITAL representative for more information. Planning Your Installation 2-9 2-9 2-9 Note Note Note You load and register only one DIGITAL Network Process Failover product license on each station. The preinstallation procedures in Chapter 3 Preinstallation Tasks describe how to load a license product authorization key (PAK). 3. 3. 3. 2. 2. 2. Installation Media Installation Media Installation Media While DIGITAL NPF is supplied on CD-ROM, it can also be installed using a DIGITAL UNIX Remote Installation Service (RIS). Full details about how to install NPF on a RIS server are in Chapter 6. Information about how to perform a Full Installation and Base Installation once your RIS server is configured are included in Section 4.6 and Section 5.4 respectively. 2-10 2-10 2-10 Planning Your Installation 2. 2. 2.4. 4. 4. General Restrictions and Considerations General Restrictions and Considerations General Restrictions and Considerations Note the following general installation restrictions and considerations: . Do not install the product into a dataless environment. It is recommended that you have at least . 128 MB of memory available on each member system.3 . You must have superuser (root) privileges for the systems on which you will install the software. You should back-up all systems before . beginning the installation process. DIGITAL Network Process Failover 3 operates in real-time. Consequently, application processes and data are locked in memory. Planning Your Installation 2-11 2-11 2-11 3. 3. 3. Pre Pre Pre- - -Installation Tasks Installation Tasks Installation Tasks This chapter describes the tasks that you must perform before loading the DIGITAL Network Process Failover subsets. It includes the following topics: . Preinstallation Overview . Prerequisites . Preinstallation Tasks Table . License Requirements . LSM and AdvFS Setup . ASE Configuration 3. 3. 3.1. 1. 1. Preinstallation Overview Preinstallation Overview Preinstallation Overview Based on the decisions you made in Chapter 2, this chapter details the preinstallation tasks you must perform to prepare your system for NPF installation. When you have completed the relevant tasks from this chapter, you will be ready to install NPF to your chosen configuration. Important Important Important This chapter assumes you have completed the planning phase outlined in Chapter 2 and are ready to ensure all prerequisites identified are in place. 3. 3. 3.2. 2. 2. Prerequisites Prerequisites Prerequisites To complete the preinstallation tasks, you should have the following to hand: . DIGITAL Network Process Failover Product Release Notes . DIGITAL Network Process Failover Product Configuration Guide . A valid DIGITAL Network Process Failover product authorization key (PAK) . DIGITAL UNIX Installation Guide . DIGITAL UNIX Release Notes . DIGITAL UNIX System Administration . DIGITAL UNIX Network Administration . TruCluster products Installation Guide (if you are planning to perform a full Network Process Failover installation with administration and configuration utilities provided by DIGITAL). 2. 2. 2. 3. 3. 3. 1. 1. 1. installation Tasks Table installation Tasks Table installation Tasks Table - - - Pre Pre Pre Table 3-1 summarizes the preinstallation tasks. It lists the tasks in order, shows the DIGITAL Network Process Failover product to which each task applies, and provides pointers to necessary information. 3 3 3 Table Table Table Preinstallation Tasks Preinstallation Tasks Preinstallation Tasks 1 1 1 - - - Task Task Task See See See Read the DIGITAL DIGITAL Network Network Process Process Failover Failover Release Release Notes. Notes. 3-2 3-2 3-2 Preinstallation Tasks Task Task Task See See See Plan the platform Chapter 2 configuration (with or without DIGITAL pilot systems). Backup the system. DIGITAL UNIX System Administration manual Install the DIGITAL DIGITAL UNIX UNIX Installation operating system. Guide Configure basic DIGITAL UNIX network services. Network Administration manual Decide Pilot Chapter 2 stations Setup LSM See Below Setup AdvFS See Below Install TruCluster TruCluster ASE, if applicable. Installation and See Guide Below Install the DIGITAL UNIX Install the DIGITAL UNIX Install the DIGITAL UNIX 3. 3. 3. 3. 3. 3. Operating System Operating System Operating System If you have not already installed DIGITAL UNIX on your stations, please read the following section carefully. Before starting the installation procedures described in the DIGITAL UNIX Installation Guide, read the following list and incorporate these tasks into the installation: Load all mandatory and any required . optional subsets. If you are installing the DIGITAL UNIX . operating system on a system in an ASE, a disk that is connected to the shared SCSI bus might be listed in the root disk installation menu. Do not install the operating system on a disk that is connected to the shared bus because the Preinstallation Tasks 3-3 3-3 3-3 data on the disk could be overwritten. DIGITAL recommends that the disks containing the standard system-level file systems (such as root, swap, /usr, ) reside on private, nonshared /var and buses. Note Note Note If you are planning to install all the Network Process Failover subsets including the optional configuration and administration subset you must first perform the TruCluster ASE installation as described in the TruCluster Installation Guide and Section 3.8 of this chapter. 3-4 3-4 3-4 Preinstallation Tasks 3. 3. 3.4. 4. 4. Configuring Basic Network Services Configuring Basic Network Services Configuring Basic Network Services Using the information in the DIGITAL UNIX Network Administration manual, set up your network and configure basic network services such as the Berkeley Internet Name Domain (BIND) service and the Network Information Service (NIS). Registering a DIGITAL Network Process Registering a DIGITAL Network Process Registering a DIGITAL Network Process 5. 5. 5. 3. 3. 3. Failover License Failover License Failover License Before you install a DIGITAL Network Process Failover product, you must use its Product Authorization Key (PAK) to register a product license. A PAK is included in your product kit. If you do not have a PAK, contact your DIGITAL Customer Services representative. As shown in the following table, there are two types of DIGITAL Network Process Failover PAKs: 2 2 2 - - - 3 3 3 Table Table Table License PAKs License PAKs License PAKs Product Product Product PAK PAK PAK DIGITAL Network Process NPF-DEV Failover Development Software DIGITAL Network Process NPF-BASE Failover Run-Time Software For information on installing a PAK, see the DIGITAL UNIX Software License Management manual, lmf(8), and lmfsetup(8). Note Note Note You must register the appropriate PAK before installing a DIGITAL Network Process Failover product; if no PAK is registered, the installation procedure displays the following Preinstallation Tasks 3-5 3-5 3-5 message: There is no active DIGITAL Network Process Failover license installed. In order to install a DIGITAL Network Process Failover product you must first install the appropriate LMF PAK (NPF-BASE or NPF-DEV). DIGITAL UNIX Patches DIGITAL UNIX Patches DIGITAL UNIX Patches 6. 6. 6. 3. 3. 3. DIGITAL NPF V1.0 requires DIGITAL UNIX 4.0D. Chapter 2 detailed the basic UNIX components required for NPF installation. The required Base Level Patch is specified in the accompanying release notes. Note Note Note You must install the specified patch level for NPF to function properly. Logical Storage Manager Logical Storage Manager Logical Storage Manager 7. 7. 7. 3. 3. 3. and AdvFS Setup and AdvFS Setup and AdvFS Setup If you are installing NPF on a PILOT station, you must also setup and configure Logical Storage Manager (LSM) and AdvFS. The script below illustrates the configuration of LSM. Note Note Note LSM is licensed separately from NPF. Consult your DIGITAL UNIX documentation for more details about LSM licensing. # disklabel -z rz9 # disklabel -z rz17 # disklabel -rw rz9 RZ1CB-CA # disklabel -rw rz17 RZ1CB-CA 3-6 3-6 3-6 Preinstallation Tasks # voldisksetup -i rz9 privlrn=128 nconfig=2 nlog=2 # voldisksetup -i rz17 privlrn=128 nconfig=2 nlog=2 # voldg init npf_dg rz9=rz9 # voldg -g npf_dg adddisk rz17=rz17 # volmake -g npf_dg sd rz9-logs dm_name=rz9 offset=0 len=2 # volmake -g npf_dg sd rz9-datas dm_name=rz9 offset=2 len=8379934 # volmake -g npf_dg sd rz17-logs dm_name=rz17 offset=0 len=2 # volmake -g npf_dg sd rz17-datas dm_name=rz17 offset=2 len=8379934 # volmake -g npf_dg plex p101 # volmake -g npf_dg plex p102 # volsd -g npf_dg aslog p101 rz9-logs # volsd -g npf_dg aslog p102 rz17-logs # volsd -g npf_dg assoc p101 rz9-datas # volsd -g npf_dg assoc p102 rz17-datas # volmake -U fsgen -g npf_dg vol vol01 read_pol=SELECT user=root group=daemon mode= 0644 log_type=BLKNO len=8379934 # volplex -g npf_dg att vol01 p101 # volplex -g npf_dg att vol01 p102 # volume -g npf_dg -o bg,verbose start vol01 Preinstallation Tasks 3-7 3-7 3-7 fsgen/volume: Volume vo101 started # mkfdmn -o /dev/vol/npf_dg/vol01 npf_dmn # mkfset npf_dmn npf_fset 3. 3. 3.8. 8. 8. TruCluster ASE TruCluster ASE TruCluster ASE Configuration Configuration Configuration The DIGITAL NPF Manager uses DIGITAL TruCluster Available Server (ASE) to create an NFS service that stores the configuration data for the platform. Therefore, if you intend to install the DIGITAL NPF Manager on your PILOT stations, you must make three configuration changes for ASE: 1. Initializing a blank ASE database (if required) 2. Configure ASE Network interfaces for the PILOT stations 3. Add an ASE service for NPF Note: Note: Note: ASE is licensed separately from NPF. For more details, refer to the DIGITAL TruCluster documentation or contact your DIGITAL Representative. 3-8 3-8 3-8 Preinstallation Tasks 3. 3. 3. Initializing a blank ASE database Initializing a blank ASE database Initializing a blank ASE database 8. 8. 8.1. 1. 1. If you do not already use an ASE database, you must first initialize a new ASE database. Run the following script: . # /sbin/rc3.d/S14asemember stop # /sbin/rc3.d/S14asemember stop # /sbin/rc3.d/S14asemember stop Stopping ASE ... Shutting down the ASE agent (/usr/sbin/aseagent) Shutting down the ASE logger (/usr/sbin/aselogger) Deinitializing the ASE Availability Manager # rcmgr set ASELOGGER 1 # asesetup -i An old ASE database file has been found. Do you want to use this (y/n): n n n Removing the local disk copy of the ASE database (services and members) ... Initializing a new ASE V1.5 database ... # /sbin/rc3.d/S14asemember start Starting ASE ... Initializing the ASE Availability Manager ASE logger started (/usr/sbin/aselogger) ASE agent started (/usr/sbin/aseagent) Preinstallation Tasks 3-9 3-9 3-9 ASE member started 3. 3. 3.8. 8. 8.2. 2. 2. Configuring Network Interfaces Configuring Network Interfaces Configuring Network Interfaces The following example shows how to create the two interfaces required for each pilot station. . Start the ASE Manager and enter the names of the two pilot stations when prompted. # asemgr asemgr asemgr Enter a comma-separated list of all hostnames you want as ASE servers. Enter Members: PILOT_A,PILOT_B PILOT_A,PILOT_B PILOT_A,PILOT_B You will be asked to confirm your entry: Member List: PILOT_A,PILOT_B Is this correct (y/n) [y]: y y y You now need to enter the second interface for each PILOT station: Would you like to define any other network interfaces to PILOT_A for ASE use (y/n)? [n]: y y y Enter interface names for member 'PILOT_A' Interface name (return to exit): STATION_A STATION_A STATION_A Checking to see if STATION_A is a valid host... Interface name (return to exit): 3-10 3-10 3-10 Preinstallation Tasks Would you like to define any other network interfaces to PILOT_B for ASE use (y/n)? [n]: y y y Enter interface names for member 'PILOT_B' Interface name (return to exit): STATION_B STATION_B STATION_B Checking to see if STATION_B is a valid host... Interface name (return to exit): Preinstallation Tasks3-11 3-11 3-11 ASE will display your entries for your confirmation: ASE Network Configuration Member Interface Member Monit Name Name Net or ________ _________ ______ _____ ___ _____ ____ __ PILOT_A PILOT_A Primar Yes y PILOT_A STATION_A Backup Yes PILOT_B PILOT_B Primar Yes y PILOT_B STATION_B Backup Yes END[Press space to continue, q to quit, h for help] Is this configuration correct (y|n)? y y y [y]: When you confirm your entries, the ASE Main Menu will be displayed. You now need to continue ASE configuration by modifying the primary network monitoring option. TruCluster Available Server (ASE) ASE Main Menu a) Managing the ASE --> m) Managing ASE Services --> s) Obtaining ASE Status --> x) Exit ?) Help Enter your choice: a a a Managing the ASE a) Add a member d) Delete a member n) Modify the network configuration 3-12 3-12 3-12 Preinstallation Tasks m) Display the status of the members C) Display the configuration of the ASE database l) Set the logging level e) Edit the error alert script t) Test the error alert script ) Enable ASE V1.5 functionality q) Quit (back to the Main Menu) x) Exit ?) Help Enter your choice [q]: n n n . You now need to specify the monitoring option for these interfaces. By default, all interfaces are monitored. You should turn off monitoring on the primary interface. ASE Network Modify Menu a) Add network interfaces d) Delete network interfaces s) Show the current configuration p) Specify the primary ASE member network b) Specify a backup ASE member network i) Specify an ASE member network to be ignored m) Specify network interfaces to be monitored q) Quit without making changes x) Exit (save changes) Enter your choice [x]: m m m ASE Member Menu Choose a member to modify: Preinstallation Tasks3-13 3-13 3-13 0) PILOT_A 1) PILOT_B q) Quit without making changes Enter your choice [q]: 0 0 0 Network Interfaces for Member 'PILOT_A' Choose all of the network interfaces to be monitored: 0) PILOT_A 10.2.2.144 (monitored) 1) STATION_A 10.1.1.144 (monitored) q) Quit (back to previous menu) n) Do not monitor any interfaces Enter your choices (comma or space separated) [q]: 0 0 0 PILOT_A 10.2.2.144 (monitored) Is the above choice correct (y|n)? [y]: y y y 3-14 3-14 3-14 Preinstallation Tasks ASE Network Modify Menu a) Add network interfaces d) Delete network interfaces s) Show the current configuration p) Specify the primary ASE member network b) Specify a backup ASE member network i) Specify an ASE member network to be ignored m) Specify network interfaces to be monitored q) Quit without making changes x) Exit (save changes) Enter your choice [x]: m m m ASE Member Menu Choose a member to modify: 0) PILOT_A 1) PILOT_B q) Quit without making changes Enter your choice [q]: 1 1 1 Network Interfaces for Member 'PILOT_B' Choose all of the network interfaces to be monitored: 0) PILOT_B 10.2.2.145 (monitored) 1) STATION_B 10.1.1.145 (monitored) q) Quit (back to previous menu) n) Do not monitor any interfaces Preinstallation Tasks3-15 3-15 3-15 Enter your choices (comma or space separated) [q]: 0 0 0 PILOT_B 10.2.2.145 (monitored) Is the above choice correct (y|n)? [y]: y y y 3-16 3-16 3-16 Preinstallation Tasks ASE Network Modify Menu a) Add network interfaces d) Delete network interfaces s) Show the current configuration p) Specify the primary ASE member network b) Specify a backup ASE member network i) Specify an ASE member network to be ignored m) Specify network interfaces to be monitored q) Quit without making changes x) Exit (save changes) Enter your choice [x]: x x x ASE will now display your configuration including both interfaces to each station and the monitoring settings: ASE Network Configuration Interface Member Monit Member Name Name or Net ________ _________ _____ ______ _____ ___ __ ____ PILOT_A PILOT_A No Primar y STATION_A PILOT_A Yes Backup PILOT_B PILOT_B No Primar y PILOT_B STATION_B Yes Backup END[Press space to continue, q to quit, h for help] Is this configuration correct (y|n)? y y y [y]: Managing the ASE Preinstallation Tasks3-17 3-17 3-17 a) Add a member d) Delete a member n) Modify the network configuration m) Display the status of the members C) Display the configuration of the ASE database l) Set the logging level e) Edit the error alert script t) Test the error alert script ) Enable ASE V1.5 functionality q) Quit (back to the Main Menu) x) Exit ?) Help Enter your choice [q]: x x x 3-18 3-18 3-18 Preinstallation Tasks 3. 3. 3. Adding an ASE Service for NPF Adding an ASE Service for NPF Adding an ASE Service for NPF 8. 8. 8.3. 3. 3. The following example illustrates how to add a new service using ASE. Follow this example, substituting your own details as required. Log in as superuser 1. Run the ASE Manager by entering the 2. following command: # asemgr Add your ASE service as described in the 3. example below: TruCluster Available Server (ASE) ASE Main Menu a) Managing the ASE ---> m) Managing ASE Services ---> s) Obtaining ASE Status ---> x) Exit ?) Help Enter your choice: m m m Managing ASE Services c) Service Configuration ---> r) Relocate a Service on) Set a service on line off) Set a service off line res) Restart a service s) Display the status of a service a) Advanced Utilities ---> q) Quit (back to Main Menu) x) Exit ?) Help Enter your choice [q]: c c c Preinstallation Tasks3-19 3-19 3-19 Service Configuration a) Add a new service m) Modify a service o) Modify a service without interrupting its availability d) Delete a service s) Display the status of a service c) Display the configuration of a service q) Quit (back to Main Menu) x) Exit ?) Help Enter your choice [q]: a a a Adding a service Select the type of service: 1) NFS service 2) Disk service 3) User-defined service 4) Tape service q) Quit without adding a service x) Exit ?) Help Enter your choice [1]: 1 1 1 You are now adding a new NFS service to ASE. An NFS service consists of an IP host name and disk configuration that are 3-20 3-20 3-20 Preinstallation Tasks failed over together. The disk configuration can include UFS file systems, AdvFS filesets or LSM volumes. NFS Service Name The name of an NFS service is a unique IP host name that has been set up for this service. This host name must exist in the local hosts database on all ASE members. Enter the NFS service name ('q' to npfmgr npfmgr npfmgr quit): Checking to see if npfmgr is a valid host... Specifying Disk Information Enter one or more UFS device special files, AdvFS filesets, or LSM volumes to define the disk storage for this service. For example: UFS device special file: /dev/rz3c AdvFS fileset: domain1#set1 LSM volume: /dev/vol/dg1/vol01 To end entering disk information, press the 'Return' key at the prompt. Enter a device special file, an AdvFS fileset, or an LSM volume as storage for this service (press 'Return' to end): npf_dmn#npf_fset npf_dmn#npf_fset npf_dmn#npf_fset AdvFS domain 'npf_dmn' has the following volume(s): /dev/vol/npf_dg/vol01 Preinstallation Tasks3-21 3-21 3-21 Is this correct (y/n) [y]: y y y Following is a list of device(s) and pubpath(s) for disk group npf_dg: DEVICE PUBPATH /dev/rz17g rz17 rz9 /dev/rz9g Is this correct (y/n) [y]: y y y Enter a directory pathname(s) to be NFS exported from the storage area "npf_dmn#npf_set". Press 'Return' when done. Directory pathname: /npfmgr /npfmgr /npfmgr Note: Note: Note: be the same name as entered ____ must This for the NFS Service Name above. Enter a host name, NIS netgroup, or IP address for the NFS exports list. (Press 'Return' for all hosts): [Return] [Return] [Return] Directory Pathname: [Return] [Return] [Return] AdvFS Fileset Read-Write Access and Quota Management Mount 'npf_dmn#npf_fset' fileset with read-write or read-only access ? 1) Read-write 2) Read-only Enter your choice [1]: [Return] [Return] [Return] You may enable user, and group fileset quotas on this file system by specifying 3-22 3-22 3-22 Preinstallation Tasks the full pathnames for the quota files. Quota files must reside within the fileset. Enter 'none' to disable quotas. Note: Note: Note: It is important that you enter none to both these prompts: User quota file path [var/ase/mnt/npfmgr/npfmgr/quota.user]: none none none Group quota file path [var/ase/mnt/npfmgr/npfmgr/quota.group]: none none none AdvFS Mount Options Modification Enter a comma-separated list of any mount options you want to use for the 'npf_dmn#npf_fset' fileset (in addition to the defaults listed in the mount.8 reference page). If none are specified, only the default mount options are used. Enter options (Return for none): [Return] [Return] [Return] Preinstallation Tasks3-23 3-23 3-23 Specifying Disk Information Enter one or more UFS device special file names, AdvFS filesets, or LSM volumes to define the disk storage for this service: For example: UFS device special file: /dev/rz3c AdvFS fileset: domain1#set1 LSM volume: /dev/vol/dg1/vol01 To end entering disk information, press the 'Return' key at the prompt. Enter a device special file, an AdvFS fileset, or an LSM volume as storage for this service (press 'Return' to end): You must now set up the scripts for the service you are configuring: Modifying user-defined scripts for 'npfmgr': 1) Start action 2) Stop action 3) Add action 4) Delete action x) Exit - done with changes Enter your choice [x]: 1 1 1 3-24 3-24 3-24 Preinstallation Tasks Modifying the start action script for 'npfmgr': a) Add a start action script ) Edit the start action script ) Modify the start action script arguments [] ) Modify the start action script timeout [60] ) Remove the start action script x) Exit - done with changes Enter your choice [x]: a a a Enter the full pathname of your start action script or "default" for the default script (x to exit): /usr/opt/NPF100/sbin/npf_ase_action /usr/opt/NPF100/sbin/npf_ase_action /usr/opt/NPF100/sbin/npf_ase_action Enter the argument list for the start action script (x to exit, NONE for none) [npfmgr]: start start start Enter the timeout in seconds for the start action script [60]: 300 300 300 Modifying the start action script for 'npfmgr': f) Replace the start action script e ) Edit the start action script g ) Modify the start action script arguments [start] t ) Modify the start action script timeout [300] r ) Remove the start action script Preinstallation Tasks3-25 3-25 3-25 x) Exit - done with changes Enter your choice [x]: 3-26 3-26 3-26 Preinstallation Tasks Modifying user-defined scripts for 'npfmgr': 1) Start action 2) Stop action 3) Add action 4) Delete action x) Exit - done with changes Enter your choice [x]: 2 2 2 Modifying the stop action script for 'npfmgr': a) Add a stop action script ) Edit the stop action script ) Modify the stop action script arguments [] ) Modify the stop action script timeout [300] ) Remove the stop action script x) Exit - done with changes Enter your choice [x]: a a a Enter the full pathname of your stop action script or "default" for the default script (x to exit): /usr/opt/NPF100/sbin/npf_ase_action /usr/opt/NPF100/sbin/npf_ase_action /usr/opt/NPF100/sbin/npf_ase_action Enter the argument list for the stop action script (x to exit, NONE for none) [npfmgr]: stop stop stop Enter the timeout in seconds for the stop action script [60]: 300 300 300 Preinstallation Tasks3-27 3-27 3-27 3-28 3-28 3-28 Preinstallation Tasks Modifying the stop action script for 'npfmgr': f) Replace the stop action script e) Edit the stop action script g) Modify the stop action script arguments [stop] t) Modify the stop action script timeout [300] r) Remove the stop action script x) Exit - done with changes Enter your choice [x]: Modifying user-defined scripts for 'npfmgr': 1) Start action 2) Stop action 3) Add action 4) Delete action x) Exit - done with changes Enter your choice [x]: Selecting an Automatic Service Placement (ASP) Policy Select the policy you want ASE to use when choosing a member to run this service: b) Balance Service Distribution f) Favor Members Preinstallation Tasks3-29 3-29 3-29 r) Restrict to Favored Members ?) Help Enter your choice [b]: f f f 3-30 3-30 3-30 Preinstallation Tasks Selecting an Automatic Service Placement (ASP) Policy Select the favored member(s) IN ORDER for service 'npfmgr': 1) PILOT_A 2) PILOT_B q) No favored members ?) Help Enter a comma-separated list [q]: 1 1 1 Selecting an Automatic Service Placement (ASP) Policy Do you want ASE to relocate this service to a more highly favored member if once becomes available while this service is running (y/n/?): n n n Enter 'y' to add Service 'npfmgr' (y/n): y y y Adding service... Starting service... Service npfmgr successfully added... Service Configuration a) Add a new service m) Modify a service o) Modify a service without interrupting its availability d) Delete a service s) Display the status of a service Preinstallation Tasks3-31 3-31 3-31 c) Display the configuration of a service q) Quit (back to Managing ASE Services) x) Exit ?) Help Enter your choice [q]: x x x # 3-32 3-32 3-32 Preinstallation Tasks Your ASE configuration is now ready to proceed with NPF installation. Note: Note: Note: Before you begin any software installation, DIGITAL recommends that you perform a full backup of your current system. Preinstallation Tasks3-33 3-33 3-33 4. 4. 4. Full Installation Full Installation Full Installation This chapter describes how to install your DIGITAL Network Process Failover software on a Pilot Station. It includes the following topics: . Installation Overview . Installing NPF . Installation Errors 4. 4. 4.1. 1. 1. Installation Overview Installation Overview Installation Overview This chapter describes a full installation of a Pilot station, including all DIGITAL management and configuration tools. While it is possible to use the NPF core middleware without the DIGITAL management software, this chapter describes the recommended approach. For details of how to install NPF as a non-Pilot station or a Pilot station that doesn't use DIGITAL's configuration software, refer to Chapter 5. 4. 4. 4.2. 2. 2. Installing DIGITAL Network Process Installing DIGITAL Network Process Installing DIGITAL Network Process Failover Failover Failover Once you have planned your installation and ensured that you have completed all the relevant preinstallation tasks, you are ready to install NPF. Note Note Note Before proceeding, you should review the preinstallation tasks in Chapter 3. 4-2 4-2 4-2Full Installation DIGITAL NPF V1.0 is installed using the DIGITAL UNIX setld installation utility. This allows you to choose the subsets of the software you require and ensures that the software is installed properly. It also allows for automated uninstall of DIGITAL NPF should this be necessary at a later date. 3. 3. 3. Installation Media Installation Media Installation Media 4. 4. 4. DIGITAL NPF is supplied on CD-ROM. The following description assumes you are installing the product from CD. However, you can also install NPF using Remote Installation Services over a DIGITAL UNIX network. Special considerations for this type of installation are described in Section 4.6. Note: Note: Note: If you have previously installed DIGITAL NPF without using setld, you will receive the following message when you run setld: setld has detected a previous manual installation of DIGITAL NPF. Before setld can continue, you must delete the following files: /./sbin/init.d/npf /./usr/bin/npf_init /./usr/bin/pldm /usr/nectar/...../pldm /./usr/bin/sldm /usr/nectar/...../sldm /./usr/bin/xma /./usr/shlib/libga.so /./usr/shlib/libga_common.so /./usr/shlib/libcoreinit.so /usr/nectar/...../libcoreinit.so /var/subsys/cs_server.mod /var/subsys/cs_tcp.mod /var/subsys/noss.mod Full Installation 4-3 4-3 4-3 /var/subsys/ntrp.mod /./usr/bin/npf_newconf /./usr/bin/npf_runscenario /./usr/bin/npf_runsci /./usr/bin/npf_setsci /./usr/bin/npf_stat /./usr/bin/npf_stopsci /./usr/bin/npf_switchsci /./usr/bin/npf_unlocksci /./usr/bin/npfmgrd /usr/nectar/...../pilot.bul When you have deleted these files, run setld again to install NPF. You must remove the listed files manually before continuing. Installation Steps Installation Steps Installation Steps 4. 4. 4. 4. 4. 4. This section outlines how to install the software: 1. Mount the media on the appropriate CD- ROM drive. 2. Log in as superuser. 3. Change your directory to the root (/) directory. 4. Mount the CD-ROM on the /mnt directory. For example if your CD-ROM drive is rz4, enter the following command: # mount -r /dev/rz4c /mnt mount -r /dev/rz4c /mnt mount -r /dev/rz4c /mnt 5. Enter the setld -l command and specify the CD-ROM mount point and the directory where the NPF software is located. For example: # setld -l /mnt/npf100/kit setld -l /mnt/npf100/kit setld -l /mnt/npf100/kit The setld utility prompts you through the rest of the installation as illustrated 4-4 4-4 4-4Full Installation below. The first part of installation is the selection of the subsets you wish to install: Working....Thu Jul 16 14:05:31 GMT+0100 1998 *** Enter subset selections *** The following subsets are mandatory and will be installed automatically unless you choose to exit without installing any subsets: *DIGITAL Network Process Failover Base Component V1.0 The subsets listed below are optional: There may be more optional subsets than can be presented on a single screen. If this is the case, you can choose subsets screen by screen or all at once on the last screen. All of the choices you make will be collected for your confirmation before any subsets are installed. 1) Digital Network Process Failover Configuration V1.0 2) Digital Network Process Failover Development V1.0 --- MORE TO FOLLOW --- Enter your choices or press RETURN to display the next screen. Choices (for example, 1 2 4-6): 3) Digital Network Process Failover Examples V1.0 4) Digital Network Process Failover Unsupported Reference Pages V1.0 5) Digital Network Process Failover Full Installation 4-5 4-5 4-5 Unsupported V1.0 Or you may choose one of the following options: 6) ALL mandatory and all optional subsets 7) MANDATORY subsets only 8) CANCEL selections and redisplay menus 9) EXIT without installing any subsets Enter your choices or press RETURN to redisplay menus. Choices (for example, 1 2 4-6): 6 You are installing the following mandatory subsets: DIGITAL Network Process Failover Base V1.0 You are installing the following optional subsets: DIGITAL Network Process Failover Configuration V1.0 DIGITAL Network Process Failover Development V1.0 DIGITAL Network Process Failover Examples V1.0 DIGITAL Network Process Failover Unsupported V1.0 DIGITAL Network Process Failover Unsupported Ref. Pages V1.0 Is this correct? (y/n): y y y Setld will now check for sufficient disk space before loading each subset. If there 4-6 4-6 4-6Full Installation is insufficient disk space, you will be prompted to delete unnecessary files. Checking file system space required to install selected subsets: File system space checked OK. 6 subset(s) will be installed. Loading 1 of 6 subset(s).... Copyright (c) Digital Equipment Corporation, 1998. All Rights Reserved. The software contained on this media is proprietary to and embodies the confidential technology of Digital Equipment Corporation. Possession, use, duplication or dissemination of the software and media is authorized only pursuant to a valid written license from Digital Equipment Corporation. Restricted Rights: Use, duplication, or disclosure by the U.S. Government is subject to restrictions as set forth in Subparagraph (c)(1)(ii) of DFARS 252.227-7013, or in FAR 52.227-19, as applicable. Copyright (c) Alcatel CIT, 1998. All Rights Reserved. Possession, use, duplication or dissemination of the software and media is authorized only pursuant to a valid written license from Alcatel CIT. Installing NPFBASE100 and running the Installation Verification Procedure (IVP) takes approximately 5 to 20 minutes, depending on your type of media and your system configuration. Full Installation 4-7 4-7 4-7 Digital Network Process Failover Base V1.0 Copying from Verifying Loading 2 of 6 subset(s).... Copyright (c) Digital Equipment Corporation, 1998. All Rights Reserved. The software contained on this media is proprietary to and embodies the confidential technology of Digital Equipment Corporation. Possession, use, duplication or dissemination of the software and media is authorized only pursuant to a valid written license from Digital Equipment Corporation. Restricted Rights: Use, duplication, or disclosure by the U.S. Government is subject to restrictions as set forth in Subparagraph (c)(1)(ii) of DFARS 252.227-7013, or in FAR 52.227-19, as applicable. Copyright (c) Alcatel CIT, 1998. All Rights Reserved. Possession, use, duplication or dissemination of the software and media is authorized only pursuant to a valid written license from Alcatel CIT. Installing NPFCONF100 and running the Installation Verification Procedure (IVP) takes approximately 5 to 20 minutes, depending on your type of media and your system configuration. Digital Network Process Failover Configuration V1.0 Copying from Verifying 4-8 4-8 4-8Full Installation Loading 3 of 6 subset(s).... Copyright (c) Digital Equipment Corporation, 1998. All Rights Reserved. The software contained on this media is proprietary to and embodies the confidential technology of Digital Equipment Corporation. Possession, use, duplication or dissemination of the software and media is authorized only pursuant to a valid written license from Digital Equipment Corporation. Restricted Rights: Use, duplication, or disclosure by the U.S. Government is subject to restrictions as set forth in Subparagraph (c)(1)(ii) of DFARS 252.227-7013, or in FAR 52.227-19, as applicable. Copyright (c) Alcatel CIT, 1998. All Rights Reserved. Possession, use, duplication or dissemination of the software and media is authorized only pursuant to a valid written license from Alcatel CIT. Installing NPFDEV100 and running the Installation Verification Procedure (IVP) takes approximately 5 to 20 minutes, depending on your type of media and your system configuration. Digital Network Process Failover Development V1.0 Copying from Verifying Loading 4 of 6 subset(s).... Copyright (c) Digital Equipment Corporation, 1998. All Rights Reserved. Full Installation 4-9 4-9 4-9 The software contained on this media is proprietary to and embodies the confidential technology of Digital Equipment Corporation. Possession, use, duplication or dissemination of the software and media is authorized only pursuant to a valid written license from Digital Equipment Corporation. Restricted Rights: Use, duplication, or disclosure by the U.S. Government is subject to restrictions as set forth in Subparagraph (c)(1)(ii) of DFARS 252.227-7013, or in FAR 52.227-19, as applicable. Copyright (c) Alcatel CIT, 1998. All Rights Reserved. Possession, use, duplication or dissemination of the software and media is authorized only pursuant to a valid written license from Alcatel CIT. Installing NPFEXAMPLES100 and running the Installation Verification Procedure (IVP) takes approximately 5 to 20 minutes, depending on your type of media and your system configuration. Digital Network Process Failover Examples V1.0 ng from Copyi Verifying Loading 5 of 6 subset(s).... Copyright (c) Digital Equipment Corporation, 1998. All Rights Reserved. The software contained on this media is proprietary to and embodies the confidential technology of Digital Equipment Corporation. Possession, use, duplication or dissemination of the software and media is authorized only 4-10 4-10 4-10 Full Installation pursuant to a valid written license from Digital Equipment Corporation. Restricted Rights: Use, duplication, or disclosure by the U.S. Government is subject to restrictions as set forth in Subparagraph (c)(1)(ii) of DFARS 252.227-7013, or in FAR 52.227-19, as applicable. Copyright (c) Alcatel CIT, 1998. All Rights Reserved. Possession, use, duplication or dissemination of the software and media is authorized only pursuant to a valid written license from Alcatel CIT. Installing NPFUNMAN100 and running the Installation Verification Procedure (IVP) takes approximately 5 to 20 minutes, depending on your type of media and your system configuration. Digital Network Process Failover Unsupported Reference Pages V1.0 Copying from Verifying Loading 6 of 6 subset(s).... Copyright (c) Digital Equipment Corporation, 1998. All Rights Reserved. The software contained on this media is proprietary to and embodies the confidential technology of Digital Equipment Corporation. Possession, use, duplication or dissemination of the software and media is authorized only pursuant to a valid written license from Digital Equipment Corporation. Full Installation4-11 4-11 4-11 Restricted Rights: Use, duplication, or disclosure by the U.S. Government is subject to restrictions as set forth in Subparagraph (c)(1)(ii) of DFARS 252.227-7013, or in FAR 52.227-19, as applicable. Copyright (c) Alcatel CIT, 1998. All Rights Reserved. Possession, use, duplication or dissemination of the software and media is authorized only pursuant to a valid written license from Alcatel CIT. 4-12 4-12 4-12 Full Installation Installing NPFUNSUPPORTED100 and running the Installation Verification Procedure (IVP) takes approximately 5 to 20 minutes, depending on your type of media and your system configuration. Digital Network Process Failover Unsupported V1.0 Copying from Verifying 6 of 6 subset(s) installed successfully. When the selected subsets have been loaded, setld will create the required links for each component: Creating Links for "Digital Network Process Failover Base V1.0" (NPFBASE100). This could take a while. Please be patient. Configuring "Digital Network Process Failover Base V1.0" (NPFBASE100) Configuration of the NPF Base Component includes the need to make changes to certain system files. You can choose to make these changes now, or at a later time. You must make these changes before you can use NPF. If you choose not to make these changes now, setld will display instructions for finishing configuration later. Do you want to complete configuration now (y/n) ? [y]: This procedure adds entries to the following files: /etc/rc.config, /etc/sysconfigtab, /etc/cfgmgr.auth, /etc/services, /etc/syslog.conf and if needed, /etc/hosts. Full Installation4-13 4-13 4-13 Original files are saved using preNPF100 as name extension. NPF ASE service name (IP alias) [npfmgr]: Debug mode (y/n) [n] : /var/opt/NPF100/cfg/trace.xma created /var/opt/NPF100/cfg/trace.dm created /etc/rc.config modified /etc/sysconfigtab modified /etc/cfgmgr.auth modified /etc/services modified /etc/syslog.conf modified * * * * Restarting syslog daemon * * * * In order to use "DIGITAL Network Process Failover Base V1.0", you will need to set up an access to an NFS filesystem that shares data for DM in /var/npf/data. The remote filesystem should be based on AdvFS. Do you want this procedure to start "DIGITAL Network Process Failover Base V1.0" now (y/n) ? [y] : n n n You can start "DIGITAL Network Process Failover Base V1.0" later by running the following command: # /sbin/rc3.d/s80npf start or by rebooting your system. The next step in the installation is to create the links for the Configuration Component. As with the configuration of the Base Component, you can choose to complete this step at a later time, but 4-14 4-14 4-14 Full Installation you must complete it before you can use NPF. Creating links for "DIGITAL Network Process Failover Configuration V1.0" (NPFCONF100) Do you want to complete configuration now (y/n) ? [y]: Setld continues to display instructions that you need to complete before you can use NPF. Further details about using the pilot configuration file can be found in the NPF Configuration Manual. Before using "DIGITAL Network Process Failover Configuration V1.0", you have to modify the PILOT configuration file (pilot.bul) for tsap and hostname in the CREATE STA definition object. This file is located in /var/npf/cfg directory. In order to use "DIGITAL Network Process Failover Configuration V1.0", you will need to setup an NFS filesystem service that shares the data for the configuration mib (npf_mib.dat) and for the pilot configuration file (pilot.bul). These files are located in the /var/npf/data and /var/npf/cfg directories respectively. The remote filesystem should be based on AdvFS. Setld will now prompt you about the ASE configuration. Refer to Chapter 3 for more details about setting up an ASE service for use with NPF. To set up an NFS filesystem service, you can use DIGITAL TruCluster software or any other similar software. Full Installation4-15 4-15 4-15 When the Configuration component has been installed, you can choose to start it now or later. Do you want this procedure to start "DIGITAL Network Process Failover Configuration V1.0" now [y/n] ? [n] : You can start "DIGITAL Network Process Failover Configuration V1.0" later by running the following command : # /usr/opt/NPF100/sbin/npf_ase_script start The installation process will now continue by creating links for the remaining NPF components. Creating links for "DIGITAL Network Process Failover Development V1.0" (NPFDEV100). This could take a while. Please be patient. Configuring "DIGITAL Network Process Failover Development V1.0" (NPFDEV100) Creating links for "DIGITAL Network Process Failover Examples V1.0" (NPFEXAMPLES100). This could take a while. Please be patient. Configuring "DIGITAL Network Process Failover Examples V1.0" (NPFEXAMPLES100) Creating links for "DIGITAL Network Process Failover Unsupported Reference Pages V1.0" (NPFUNMAN100). This could take a while. Please be patient. Working....Thu Jul 16 14:08:50 GMT+0100 1998 4-16 4-16 4-16 Full Installation Configuring "DIGITAL Network Process Failover Unsupported Reference Pages V1.0" (NPFUNMAN100) Creating links for "DIGITAL Network Process Failover Unsupported V1.0" (NPFUNSUPPORTED100). This could take a while. Please be patient. Configuring "DIGITAL Network Process Failover Unsupported V1.0" (NPFUNSUPPORTED100) /etc/routes file /etc/routes file /etc/routes file 5. 5. 5. 4. 4. 4. The following entries must be added to the /etc/routes file on each Pilot Station: PILOT_A PILOT_A PILOT_B PILOT_B STATION_A STATION_A STATION_B STATION_B /etc/fstab file /etc/fstab file /etc/fstab file 6. 6. 6. 4. 4. 4. The following two entries must be added to the /etc/fstab file on each Pilot Station: /npfmgr@npfmgr /npfmgr nfs nfsv3,proplist,proto=udp,rw,hard,bg,i ntr 0 0 /npfmgr/npf@npfmgr /var/opt/NPF100/share nfs nfsv3,proplist,proto=udp,rw,hard,bg,i ntr 0 0 You must also create special directories after modifying the /etc/fstab file on each Pilot Station. Full Installation4-17 4-17 4-17 # mkdir /npfmgr mkdir /npfmgr mkdir /npfmgr mount /npfmgr mount /npfmgr mount /npfmgr # # mkdir /npfmgr/npf mkdir /npfmgr/npf mkdir /npfmgr/npf mount /var/opt/NPF100/share mount /var/opt/NPF100/share mount /var/opt/NPF100/share # # mkdir /var/opt/NPF100/share/data mkdir /var/opt/NPF100/share/data mkdir /var/opt/NPF100/share/data # mkdir /var/opt/NPF100/share/cfg mkdir /var/opt/NPF100/share/cfg mkdir /var/opt/NPF100/share/cfg 4-18 4-18 4-18 Full Installation 4. 4. 4.7. 7. 7. RIS Installation RIS Installation RIS Installation This section describes the special considerations required when installing NPF using RIS. See also Section and 2.3 Chapter 6. . If your site has a RIS server, contact the server's administrator to see if you should perform a RIS installation. . If you are the RIS administrator, follow the instructions in Chapter 6. Check network connection for RIS . Installations. You need a connection to a RIS server . via the LAN if you plan to perform a Remote Installation Services installation. Performing a full installation from a . RIS server is the same as described above, except that the setld command should include the name of the RIS server where the NPF kit is available. For example: # setld -l bcv05x09 setld -l bcv05x09 setld -l bcv05x09 4. 4. 4. Installation Errors Installation Errors Installation Errors 8. 8. 8. If you encounter errors during installation, refer to the setld reference page for an explanation of the error and suggested actions. If you want to retry the installation, first use the setld -d command to delete the previous installation attempt. Full Installation4-19 4-19 4-19 5. 5. 5. Base Installation Base Installation Base Installation This chapter describes how to install DIGITAL NPF on a Non-Pilot4 station. It includes the following topics: . Non-Pilot Overview . Installation Instructions 5. 5. 5.1. 1. 1. Non-Pilot Overview Non-Pilot Overview Non-Pilot Overview A non-pilot station is a member of a NPF platform that is not involved in the administration of the platform. Note: Note: Note: Before proceeding, you should review the preinstallation tasks in Chapter 3. DIGITAL NPF V1.0 is installed using the DIGITAL UNIX setld installation utility. This allows you to choose the subsets of 4 The instructions in this chapter also apply to users wishing to install a PILOT station without DIGITAL's supplied configuration software. In this case, you must also install your own platform-level configuration software, written to the DIGITAL NPF API as described in the accompanying Programmer's Guide and Reference Manual. the software you require and ensures that the software is installed properly. 5. 5. 5.2. 2. 2. Installation Media Installation Media Installation Media DIGITAL NPF is supplied on CD-ROM. The following description assumes you are installing the product from CD. However, you can also install NPF using Remote Installation Services over a DIGITAL UNIX network. Special considerations for this type of installation are described in Section . 5.4 Note: Note: Note: If you have previously installed DIGITAL NPF without using setld, you will receive the following message when you run setld: setld has detected a previous manual installation of DIGITAL NPF. Before setld can continue, you must delete the following files: /./sbin/init.d/npf /./usr/bin/npf_init /./usr/bin/pldm /usr/nectar/...../pldm /./usr/bin/sldm /usr/nectar/...../sldm /./usr/bin/xma /./usr/shlib/libga.so /./usr/shlib/libga_common.so /./usr/shlib/libcoreinit.so /usr/nectar/...../libcoreinit.so /var/subsys/cs_server.mod /var/subsys/cs_tcp.mod /var/subsys/noss.mod /var/subsys/ntrp.mod /./usr/bin/npf_newconf /./usr/bin/npf_runscenario /./usr/bin/npf_runsci /./usr/bin/npf_setsci 5- 5- 5- Base Installation 2 2 2 /./usr/bin/npf_stat /./usr/bin/npf_stopsci /./usr/bin/npf_switchsci /./usr/bin/npf_unlocksci /./usr/bin/npfmgrd /usr/nectar/...../pilot.bul When you have deleted these files, run setld again to install NPF. You must remove the listed files manually before continuing. Base Installation 5-3 5-3 5-3 5. 5. 5. Installation Steps Installation Steps Installation Steps 3. 3. 3. 1. Mount the media on the appropriate CD- ROM drive. 2. Log in as superuser. 3. Change your directory to the root (/) directory. 4. Mount the CD-ROM on the /mnt directory. For example if your CD-ROM drive is rz4, enter the following command: # mount -r /dev/rz4c /mnt mount -r /dev/rz4c /mnt mount -r /dev/rz4c /mnt 5. Enter the setld -l command and specify the CD-ROM mount point and the directory where the NPF software is located. For example: setld -l /mnt/npf100/kit setld -l /mnt/npf100/kit setld -l /mnt/npf100/kit # The setld utility prompts you through the rest of the installation as illustrated below. The first part of installation is the selection of the subsets you wish to install. The following example shows the installation of only the base components of DIGITAL NPF as this is what is necessary to set up a non-pilot station. You can select other optional subsets as required. Working....Thu Jul 16 14:05:31 GMT+0100 1998 *** Enter subset selections *** The following subsets are mandatory and will be installed automatically unless you choose to exit without installing any subsets: 5- 5- 5- Base Installation 4 4 4 *DIGITAL Network Process Failover Base V1.0 The subsets listed below are optional: There may be more optional subsets than can be presented on a single screen. If this is the case, you can choose subsets screen by screen or all at once on the last screen. All of the choices you make will be collected for your confirmation before any subsets are installed. 1) DIGITAL Network Process Failover Configuration V1.0 2) DIGITAL Network Process Failover Development V1.0 --- MORE TO FOLLOW --- Enter your choices or press RETURN to display the next screen. Choices (for example, 1 2 4-6): 3) DIGITAL Network Process Failover Examples V1.0 4) DIGITAL Network Process Failover Unsupported V1.0 5) DIGITAL Network Process Failover Unsupported Ref. Pages V1.0 Or you may choose one of the following options: 6) ALL mandatory and all optional subsets 7) MANDATORY subsets only 8) CANCEL selections and redisplay menus 9) EXIT without installing any subsets. Enter your choices or press return to redisplay menus. Base Installation 5-5 5-5 5-5 Choices (for example 1 2 4-6): 7 7 7 Enter your selection(s). They will be displayed for your confirmation: You are installing the following mandatory subsets: DIGITAL Network Process Failover Base V1.0 Is this correct? (y/n): y y y Setld will now check for sufficient disk space before loading the subset(s). If there is insufficient disk space, you will be prompted to delete unnecessary files. Checking file system space required to install selected subsets: File system space checked OK. 1 subset(s) will be installed. Loading 1 of 1 subset(s).... Copyright (c) Digital Equipment Corporation, 1998. All Rights Reserved. The software contained on this media is proprietary to and embodies the confidential technology of Digital Equipment Corporation. Possession, use, duplication or dissemination of the software and media is authorized only pursuant to a valid written license from Digital Equipment Corporation. Restricted Rights: Use, duplication, or disclosure by the U.S. Government is subject to restrictions as set forth in Subparagraph (c)(1)(ii) of DFARS 252.227-7013, or in FAR 52.227-19, as applicable. 5- 5- 5- Base Installation 6 6 6 Copyright (c) Alcatel CIT, 1998. All Rights Reserved. Possession, use, duplication or dissemination of the software and media is authorized only pursuant to a valid written license from Alcatel CIT. Installing NPFBASE100 and running the Installation Verification Procedure (IVP) takes approximately 5 to 20 minutes, depending on your type of media and your system configuration. Digital Network Process Failover Base V1.0 Copying from Verifying 1 of 1 subset(s) installed successfully. When the selected subset has been loaded, setld will create the required links for the base component: Creating Links for "Digital Network Process Failover Base V1.0" (NPFBASE100). This could take a while. Please be patient. Configuring "Digital Network Process Failover Base V1.0" (NPFBASE100) Configuration of the NPF Base Component includes the need to make changes to certain system files. You can choose to make these changes now, or at a later time. You must make these changes before you can use NPF. If you choose not to make these changes now, setld will display instructions for finishing configuration later. Do you want to complete configuration now (y/n) ? [y]: Base Installation 5-7 5-7 5-7 This procedure adds entries to the following files: /etc/rc.config, /etc/sysconfigtab, /etc/cfgmgr.auth, /etc/services, /etc/syslog.conf and if needed, /etc/hosts. Original files are saved using preNPF100 as name extension. /var/opt/NPF100/cfg/trace.xma created /var/opt/NPF100/cfg/trace.dm created /etc/rc.config modified /etc/sysconfigtab modified /etc/cfgmgr.auth modified /etc/services modified /etc/syslog.conf modified * * * * Restarting syslog daemon * * * * In order to use "DIGITAL Network Process Failover Base V1.0", you will need to set up an access to an NFS filesystem that shares data for DM in var/npf/data. The remote filesystem should be based on AdvFS. Do you want this procedure to start "DIGITAL Network Process Failover Base V1.0" now (y/n) ? [y] : You can start "DIGITAL Network Process Failover Base V1.0" later by running the following command: # /sbin/rc3.d/s80npf start or by rebooting your system. 5- 5- 5- Base Installation 8 8 8 5. 5. 5.4. 4. 4. RIS Installation RIS Installation RIS Installation This section describes the special considerations required when installing NPF using RIS. If your site has a RIS server, contact . the server's administrator to see if you should perform a RIS installation. If you are the RIS administrator, refer . to Chapter 6 for details of installing DIGITAL NPF on a RIS server for distribution. Check network connection for RIS . Installations. You need a connection to a RIS server . via the LAN if you plan to perform a Remote Installation Services installation. Base Installation 5-9 5-9 5-9 . The installation procedure from a RIS server is the same as described above except that the setld command should include the name of the RIS server where the NPF kit is available. For example: # setld -l bcv05x09 setld -l bcv05x09 setld -l bcv05x09 Installation Errors Installation Errors Installation Errors 5. 5. 5.5. 5. 5. If you encounter errors during installation, refer to the setld reference page for an explanation of the error and suggested actions. If you want to retry the installation, first use the setld -d command to delete the previous installation attempt. 5- 5- 5- Base Installation 10 10 10 6. 6. 6. RIS Installation RIS Installation RIS Installation This chapter describes how to set up NPF for distribution using a Remote Installation Services (RIS) server. It contains the following topic: . Installing NPF on a RIS Server Information about how to perform a Full Installation and Base Installation once your RIS server is configured are included in Section 4.6 and Section 5.4 respectively. 6. 6. 6.1. 1. 1. Installing Network Process Failover for Installing Network Process Failover for Installing Network Process Failover for RIS RIS RIS The following section describes the NPF installation procedure for a RIS Server. Once this installation has been completed, you can install NPF on various stations from this central RIS Server. . Log in as superuser and enter the RIS command. root@bcv05x09 1 > ris root@bcv05x09 1 > ris root@bcv05x09 1 > ris Checking accessibility of RIS areas.... done . From the RIS Utility Menu, choose to Install Software Products. *** RIS Utility Main Menu *** a) ADD a client d) DELETE software products i) INSTALL software products l) LIST registered clients m) MODIFY a client r) REMOVE a client s) SHOW software products in remote installation environments x) EXIT Enter your choice: i i i . Assuming you have previously configured the RIS Server, choose to add software to an existing area. RIS Software Installation Menu: 1) Install software into a new area 2) Add software into an existing area 3) Return to previous menu Enter your choice: 2 2 2 You have chosen to add a product to an existing environment. The existing environment is /var/adm/ris/ris0.alpha. . You must now enter the location of the NPF kit that you wish to add to this RIS server. Enter the device special file name or the path of the directory where the software is located (for example, /mnt/ALPHA/BASE): /cdrom/npf100/kit /cdrom/npf100/kit /cdrom/npf100/kit . Extract the software from the CD. Choose one of the following options: 6-2 6-2 6-2RIS Installation 1) Extract software from /cdrom/npf100/kit 2) Create symbolic link to /cdrom/npf100/kit Enter your choice: 1 1 1 *** Enter subset selections *** The following subsets are mandatory and will be extracted automatically unless you choose to exit without extracting any subsets: * Digital Network Process Failover Base V1.0 The subsets listed below are optional: There may be more optional subsets than can be presented on a single screen. If this is the case, you can choose subsets screen by screen or all at once on the last screen. All of the choices you make will be collected for your confirmation before any subsets are extracted. 1) Digital Network Process Failover Configuration V1.0 2) Digital Network Process Failover Development V1.0 --- MORE TO FOLLOW --- Enter your choices or press RETURN to display the next screen. Choices (for example, 1 2 4-6): 3) Digital Network Process Failover Examples V1.0 4) Digital Network Process Failover Unsupported Reference Pages V1.0 RIS Installation 6-3 6-3 6-3 5) Digital Network Process Failover Unsupported V1.0 Or you may choose one of the following options: 6) ALL mandatory and all optional subsets 7) MANDATORY subsets only 8) CANCEL selections and redisplay menus 9) EXIT without extracting any subsets Enter your choices or press RETURN to redisplay menus. . Choose to add all NPF subsets to the RIS server. Clients can decide later what type of NPF installation they require. Choices (for example, 1 2 4-6): 6 6 6 You are extracting the following mandatory subsets: Digital Network Process Failover Base V1.0 You are extracting the following optional subsets: Digital Network Process Failover Configuration V1.0 Digital Network Process Failover Development V1.0 Digital Network Process Failover Examples V1.0 Digital Network Process Failover Unsupported Reference Pages V1.0 Digital Network Process Failover Unsupported V1.0 Is this correct? (y/n): y y y 6-4 6-4 6-4RIS Installation Checking file system space required to extract selected subsets: File system space checked OK. Extracting NPFBASE100... Extracting NPFCONF100... Extracting NPFDEV100... Extracting NPFEXAMPLES100... Extracting NPFUNMAN100... Extracting NPFUNSUPPORTED100... Media extraction complete. When the NPF software has been extracted . to the RIS server, you must now use the RIS Utility to modify the client(s) to make NPF available. *** RIS Utility Main Menu *** a) ADD a client d) DELETE software products i) INSTALL software products l) LIST registered clients m) MODIFY a client r) REMOVE a client s) SHOW software products in remote installation environments x) EXIT Enter your choice: m m m The following clients are available to modify: bcv05x0b.vz.cit.alcatel.fr Enter the client processor's hostname or press RETURN to quit: bcv05x0b.vz.cit.alcatel.fr bcv05x0b.vz.cit.alcatel.fr bcv05x0b.vz.cit.alcatel.fr The existing environment is /var/adm/ris/ris0.alpha. RIS Installation 6-5 6-5 6-5 6-6 6-6 6-6RIS Installation Client bcv05x0b.vz.cit.alcatel.fr currently can install the following products from /var/adm/ris/ris0.alpha: 'DIGITAL UNIX V4.0D Operating System ( Rev 878 )' 'Advanced File System Advanced Utilities ' 'DIGITAL UNIX TruCluster(TM) Software V1.5 ' 'Alternative Development Environment Tools for DIGITAL UNIX' 'DECevent ' 'Performance Manager for Digital UNIX ' Select one or more products for the client to install from /var/adm/ris/ris0.alpha: Product Description 'DIGITAL UNIX V4.0D Operating System 1 ( Rev 878 )' 'Advanced File System Advanced 2 Utilities ' 'DIGITAL UNIX TruCluster(TM) Software 3 V1.5 ' 4 'Alternative Development Environment Tools for DIGITAL UNIX' 5 'DECevent ' 6 'Performance Manager for Digital UNIX ' 7 'Digital Network Process Failover V1.0 ' Add NPF to the list of software . available for the client to install. RIS Installation 6-7 6-7 6-7 Enter one or more choices as a space- separated list (for example, 1 2 3) or "all" for all products [all]: 7 7 7 You chose the following products: 7 'Digital Network Process Failover V1.0 ' Is that correct? (y/n) [y]: Network type: 1) Ethernet or FDDI 2) Token Ring Enter your choice [1]: Client bcv05x0b.vz.cit.alcatel.fr has been modified. *** RIS Utility Main Menu *** a) ADD a client d) DELETE software products i) INSTALL software products l) LIST registered clients m) MODIFY a client r) REMOVE a client s) SHOW software products in remote installation environments x) EXIT Enter your choice: x x x . Your RIS Installation is now complete and available to the specified 6-8 6-8 6-8RIS Installation client(s). Follow the instructions in Chapters 4 and 5 for installation. RIS Installation 9 9 9 Appendix A Appendix A Appendix A The following files are created or modified as a result of installing DIGITAL Network Process Failover: File Name File Name File Name File Content File Content File Content /etc/hosts The IP address and interface name associated with the primary network interface. /etc/rc.config See the DIGITAL Network Process Failover Software Products Administration manual for a complete list of DIGITAL Network Process Failover rc.config variables. /etc/sysconfigt See the DIGITAL Network Process ab Failover Software Products Administration manual for a complete list of DIGITAL Network Process Failover sysconfigtab variables. NAME /sys/ /vmuni A new kernel is built and placed x in /sys/ /vmunix, where NAME NAME is the name of the configuration file specified during installation. /etc/services See the DIGITAL UNIX Network Administrator's Guide. /etc/syslog.con See the DIGITAL UNIX System f Administration Guide. /etc/cfgmgr.aut See the DIGITAL UNIX System h Administration Guide. Configuration Management server authorization database. /var/opt/NPF100 Configuration Files for DM and XMA /cfg/trace.xma subsystems to enable tracing. /var/opt/NPF100 /cfg/trace.dm 2 2 2 RIS Installation Appendix B Appendix B Appendix B This appendix provides a complete listing of all the files supplied with DIGITAL NPF Release 1.0. NPFBASE100 -------------------- ./opt/NPF100/etc/sysconfigtab.cs_server ./opt/NPF100/etc/sysconfigtab.cs_tcp ./opt/NPF100/etc/sysconfigtab.noss ./opt/NPF100/etc/sysconfigtab.ntrp ./opt/NPF100/sbin/init.d/npf ./usr/opt/NPF100/bin/npf_init ./usr/opt/NPF100/bin/npfagent ./usr/opt/NPF100/bin/pldm ./usr/opt/NPF100/bin/sldm ./usr/opt/NPF100/bin/xma ./usr/opt/NPF100/gcis/README.TXT ./usr/opt/NPF100/gcis/gcis_app_api.h ./usr/opt/NPF100/gcis/libgcis_api.so ./usr/opt/NPF100/gcis/makefile ./usr/opt/NPF100/gcis/test_gcis ./usr/opt/NPF100/gcis/test_gcis.c ./usr/opt/NPF100/gcis/test_gcis.h ./usr/opt/NPF100/gcis/test_gcis.o ./usr/opt/NPF100/shlib/libga.so ./usr/opt/NPF100/shlib/libga_common.so ./var/opt/NPF100/libconf/makefile ./var/opt/NPF100/shlib/libcoreinit.so ./var/opt/NPF100/subsys/cs_server.mod ./var/opt/NPF100/subsys/cs_tcp.mod ./var/opt/NPF100/subsys/noss.mod ./var/opt/NPF100/subsys/ntrp.mod Appendix B- - -2 2 2 NPFCONF100 -------------------- ./usr/opt/NPF100/bin/npf_newconf ./usr/opt/NPF100/bin/npf_runscenario ./usr/opt/NPF100/bin/npf_runsci ./usr/opt/NPF100/bin/npf_setsci ./usr/opt/NPF100/bin/npf_stat ./usr/opt/NPF100/bin/npf_stopsci ./usr/opt/NPF100/bin/npf_switchsci ./usr/opt/NPF100/bin/npf_unlocksci ./usr/opt/NPF100/bin/npfmgrd ./usr/opt/NPF100/cfg/pilot.bul ./usr/opt/NPF100/sbin/fuser ./usr/opt/NPF100/sbin/npf_ase_action ./usr/opt/NPF100/sbin/npf_ase_script NPFDEV100 -------------------- ./usr/opt/NPF100/include/ga_conf.h ./usr/opt/NPF100/include/ga_error.h ./usr/opt/NPF100/include/ga_obj.h ./usr/opt/NPF100/include/ncb.h ./usr/opt/NPF100/include/ncs.h ./usr/opt/NPF100/include/ncs_adm.h ./usr/opt/NPF100/include/ncs_init.h ./usr/opt/NPF100/include/ndm.h ./usr/opt/NPF100/include/ndm_adm.h ./usr/opt/NPF100/include/ndm_init.h ./usr/opt/NPF100/include/ndmp_init.h ./usr/opt/NPF100/include/nec_core.h ./usr/opt/NPF100/include/nec_init.h ./usr/opt/NPF100/include/nec_initconf.h ./usr/opt/NPF100/include/necs_core.h ./usr/opt/NPF100/include/nos.h ./usr/opt/NPF100/include/nos_init.h ./usr/opt/NPF100/include/nxa.h ./usr/opt/NPF100/include/nxa_adm.h ./usr/opt/NPF100/include/nxa_init.h Appendix B-3 3 3 ./usr/opt/NPF100/lib/ncb.o ./usr/opt/NPF100/lib/ncbs.o ./usr/opt/NPF100/lib/ncbsys.o ./usr/opt/NPF100/lib/ncs.o ./usr/opt/NPF100/lib/ncs_ini_lib.o ./usr/opt/NPF100/lib/ncss.o ./usr/opt/NPF100/lib/ncss_core.o ./usr/opt/NPF100/lib/ncss_tcp.o ./usr/opt/NPF100/lib/ndm.o ./usr/opt/NPF100/lib/ndm_vchg_new.a ./usr/opt/NPF100/lib/ndm_vchg_old.a ./usr/opt/NPF100/lib/ndms.a ./usr/opt/NPF100/lib/ndms_core.a ./usr/opt/NPF100/lib/ndms_pmd.a ./usr/opt/NPF100/lib/necdlist.o ./usr/opt/NPF100/lib/neclist.o ./usr/opt/NPF100/lib/necpool.o ./usr/opt/NPF100/lib/nmts_core.a ./usr/opt/NPF100/lib/nos.o ./usr/opt/NPF100/lib/noss.o ./usr/opt/NPF100/lib/noss_core.o ./usr/opt/NPF100/lib/nossys.o ./usr/opt/NPF100/lib/nostime.a ./usr/opt/NPF100/lib/nostime.o ./usr/opt/NPF100/lib/nxa.o ./usr/opt/NPF100/lib/nxacrt0.o ./usr/opt/NPF100/lib/nxas.o ./var/opt/NPF100/libconf/include/nec_core_ init.h ./var/opt/NPF100/libconf/ncs_init.c ./var/opt/NPF100/libconf/ndm_conf.c ./var/opt/NPF100/libconf/ndm_init.c ./var/opt/NPF100/libconf/ndmp_conf.c ./var/opt/NPF100/libconf/ndmp_init.c ./var/opt/NPF100/libconf/nec_init.c ./var/opt/NPF100/libconf/nec_initconf.c ./var/opt/NPF100/libconf/nos_init.c ./var/opt/NPF100/libconf/nxa_conf.c ./var/opt/NPF100/libconf/nxa_init.c Appendix B- - -4 4 4 NPFEXAMPLES100 -------------------- ./usr/opt/NPF100/examples/src/Makefile ./usr/opt/NPF100/examples/src/include/esiz e.c ./usr/opt/NPF100/examples/src/include/nmox .h ./usr/opt/NPF100/examples/src/provider.c ./usr/opt/NPF100/examples/src/requester.c ./usr/opt/NPF100/examples/src/sr_provider. c ./usr/opt/NPF100/examples/src/sr_requester .c NPFUNMAN100 -------------------- ./usr/opt/NPF100/share/man/man3/ncb_alloc. 3.gz ./usr/opt/NPF100/share/man/man3/ncb_data.3 .gz ./usr/opt/NPF100/share/man/man3/ncb_delete head.3.gz ./usr/opt/NPF100/share/man/man3/ncb_free.3 .gz ./usr/opt/NPF100/share/man/man3/ncb_intro. 3.gz ./usr/opt/NPF100/share/man/man3/ncb_list.3 .gz ./usr/opt/NPF100/share/man/man3/ncb_read.3 .gz ./usr/opt/NPF100/share/man/man3/ncb_readfr ee.3.gz ./usr/opt/NPF100/share/man/man3/ncb_rseek. 3.gz ./usr/opt/NPF100/share/man/man3/ncb_size.3 .gz ./usr/opt/NPF100/share/man/man3/ncb_writeh Appendix B-5 5 5 ead.3.gz ./usr/opt/NPF100/share/man/man3/ncb_writet ail.3.gz ./usr/opt/NPF100/share/man/man3/ncs_answer indic.3.gz ./usr/opt/NPF100/share/man/man3/ncs_data.3 .gz ./usr/opt/NPF100/share/man/man3/ncs_dtgbro adcast.3.gz ./usr/opt/NPF100/share/man/man3/ncs_dtgdel egate.3.gz ./usr/opt/NPF100/share/man/man3/ncs_dtgind ic.3.gz ./usr/opt/NPF100/share/man/man3/ncs_dtgsen d.3.gz ./usr/opt/NPF100/share/man/man3/ncs_fapsup off.3.gz ./usr/opt/NPF100/share/man/man3/ncs_fapsup on.3.gz ./usr/opt/NPF100/share/man/man3/ncs_getfap .3.gz ./usr/opt/NPF100/share/man/man3/ncs_getifa p.3.gz ./usr/opt/NPF100/share/man/man3/ncs_intro. 3.gz ./usr/opt/NPF100/share/man/man3/ncs_list.3 .gz ./usr/opt/NPF100/share/man/man3/ncs_ltsapg et.3.gz ./usr/opt/NPF100/share/man/man3/ncs_msgrec eive.3.gz ./usr/opt/NPF100/share/man/man3/ncs_port_c ong_rep.3.gz ./usr/opt/NPF100/share/man/man3/ncs_port_d rop_rep.3.gz ./usr/opt/NPF100/share/man/man3/ncs_port_e ndofcong_rep.3.gz ./usr/opt/NPF100/share/man/man3/ncs_port_e ndofrecov_rep.3.gz ./usr/opt/NPF100/share/man/man3/ncs_port_e quip_rep.3.gz ./usr/opt/NPF100/share/man/man3/ncs_porteq uip.3.gz ./usr/opt/NPF100/share/man/man3/ncs_qstabo rt.3.gz ./usr/opt/NPF100/share/man/man3/ncs_qstans Appendix B 6 6 6 - - - wer.3.gz ./usr/opt/NPF100/share/man/man3/ncs_qstdel egate.3.gz ./usr/opt/NPF100/share/man/man3/ncs_qstind ic.3.gz ./usr/opt/NPF100/share/man/man3/ncs_qstref use.3.gz ./usr/opt/NPF100/share/man/man3/ncs_qstsen da.3.gz ./usr/opt/NPF100/share/man/man3/ncs_qstsen db.3.gz ./usr/opt/NPF100/share/man/man3/ncs_sesabo rt.3.gz ./usr/opt/NPF100/share/man/man3/ncs_sesabo rtindic.3.gz ./usr/opt/NPF100/share/man/man3/ncs_sesclo se.3.gz ./usr/opt/NPF100/share/man/man3/ncs_sesclo seconfirm.3.gz ./usr/opt/NPF100/share/man/man3/ncs_sesclo seindic.3.gz ./usr/opt/NPF100/share/man/man3/ncs_sesclo seresp.3.gz ./usr/opt/NPF100/share/man/man3/ncs_sescon gendindic.3.gz ./usr/opt/NPF100/share/man/man3/ncs_sesdat aindic.3.gz ./usr/opt/NPF100/share/man/man3/ncs_sesdat asend.3.gz ./usr/opt/NPF100/share/man/man3/ncs_sesdat axconfirm.3.gz ./usr/opt/NPF100/share/man/man3/ncs_sesdat axindic.3.gz ./usr/opt/NPF100/share/man/man3/ncs_sesdat axsend.3.gz ./usr/opt/NPF100/share/man/man3/ncs_sesdel egate.3.gz ./usr/opt/NPF100/share/man/man3/ncs_sesinh ibit.3.gz ./usr/opt/NPF100/share/man/man3/ncs_sesope na.3.gz ./usr/opt/NPF100/share/man/man3/ncs_sesope nb.3.gz ./usr/opt/NPF100/share/man/man3/ncs_sesope nconfirm.3.gz ./usr/opt/NPF100/share/man/man3/ncs_sesope Appendix B-7 7 7 nindic.3.gz ./usr/opt/NPF100/share/man/man3/ncs_sesope nresp.3.gz ./usr/opt/NPF100/share/man/man3/ncs_sesrec over.3.gz ./usr/opt/NPF100/share/man/man3/ncs_sesrec overend.3.gz ./usr/opt/NPF100/share/man/man3/ncs_sesref use.3.gz ./usr/opt/NPF100/share/man/man3/ncs_sesrei nitindic.3.gz ./usr/opt/NPF100/share/man/man3/ncs_supind ic.3.gz ./usr/opt/NPF100/share/man/man3/ncs_tsapq_ alarm.3.gz ./usr/opt/NPF100/share/man/man3/ncs_tsapq_ cong.3.gz ./usr/opt/NPF100/share/man/man3/ncs_tsapq_ econg.3.gz ./usr/opt/NPF100/share/man/man3/ncs_xpcxco nfirmindic.3.gz ./usr/opt/NPF100/share/man/man3/ncs_xpcxin dic.3.gz ./usr/opt/NPF100/share/man/man3/ncs_xpdisc indic.3.gz ./usr/opt/NPF100/share/man/man3/ncs_xperri ndic.3.gz ./usr/opt/NPF100/share/man/man3/ndm_1_intr o.3.gz ./usr/opt/NPF100/share/man/man3/ndm_2_data .3.gz ./usr/opt/NPF100/share/man/man3/ndm_3_list .3.gz ./usr/opt/NPF100/share/man/man3/ndm_bkp_cl ose.3.gz ./usr/opt/NPF100/share/man/man3/ndm_bkp_cr eate.3.gz ./usr/opt/NPF100/share/man/man3/ndm_bkp_op en.3.gz ./usr/opt/NPF100/share/man/man3/ndm_bkp_re ad.3.gz ./usr/opt/NPF100/share/man/man3/ndm_bkp_wr ite.3.gz ./usr/opt/NPF100/share/man/man3/ndm_dbacku p.3.gz ./usr/opt/NPF100/share/man/man3/ndm_dlock. Appendix B 8 8 8 - - - 3.gz ./usr/opt/NPF100/share/man/man3/ndm_ralloc p.3.gz ./usr/opt/NPF100/share/man/man3/ndm_ralloc v.3.gz ./usr/opt/NPF100/share/man/man3/ndm_rcheck point.3.gz ./usr/opt/NPF100/share/man/man3/ndm_rdeall oc.3.gz ./usr/opt/NPF100/share/man/man3/ndm_rreadp .3.gz ./usr/opt/NPF100/share/man/man3/ndm_rreadv .3.gz ./usr/opt/NPF100/share/man/man3/ndm_rwrite p.3.gz ./usr/opt/NPF100/share/man/man3/ndm_rwrite v.3.gz ./usr/opt/NPF100/share/man/man3/ndm_trclos e.3.gz ./usr/opt/NPF100/share/man/man3/ndm_trgrem ove.3.gz ./usr/opt/NPF100/share/man/man3/ndm_trgset .3.gz ./usr/opt/NPF100/share/man/man3/ndm_trgtrs et.3.gz ./usr/opt/NPF100/share/man/man3/ndm_tropen .3.gz ./usr/opt/NPF100/share/man/man3/nos_data.3 .gz ./usr/opt/NPF100/share/man/man3/nos_intro. 3.gz ./usr/opt/NPF100/share/man/man3/nos_list.3 .gz ./usr/opt/NPF100/share/man/man3/nos_qassig n.3.gz ./usr/opt/NPF100/share/man/man3/nos_qcreat e.3.gz ./usr/opt/NPF100/share/man/man3/nos_qsend. 3.gz ./usr/opt/NPF100/share/man/man3/nxa_errcou nt.3.gz ./usr/opt/NPF100/share/man/man3/nxa_initen d.3.gz ./usr/opt/NPF100/share/man/man3/nxa_intro. 3.gz ./usr/opt/NPF100/share/man/man3/nxa_list.3 Appendix B-9 9 9 .gz ./usr/opt/NPF100/share/man/man3/nxa_wdogse t.3.gz NPFUNSUPPORTED100 -------------------- ./usr/opt/NPF100/bin/cmwobs Appendix B- - -10 10 10 Glossary Glossary Glossary The following terms are used in the DIGITAL Network Process Failover Documentation: active pilot station active pilot station active pilot station An active pilot station controls and administers the NPF platform. AdvFS AdvFS AdvFS Advanced File System ASE ASE ASE DIGITAL TruCluster Available Server ASP ASP ASP Automatic Service Placement ATM ATM ATM Asynchronous Transfer Mode BIND BIND BIND Berkeley Internet Name Domain LSM LSM LSM Logical Storage Manager NIS NIS NIS Network Information Service non-pilot station non-pilot station non-pilot station A non-pilot station is a member of a NPF platform, but is not involved in the administration of the platform. NPF-BASE NPF-BASE NPF-BASE The PAK needed for the DIGITAL Network Process Failover Run-Time Software. NPF-DEV NPF-DEV NPF-DEV The PAK needed for the DIGITAL Network Process Failover Development Software. PAK PAK PAK Product Authorization Key pilot station pilot station pilot station A pilot station is a member of a NPF platform and is involved in the administration of the platform. It includes an additional global management software component. RIS RIS RIS Remote Installation Service setld setld setld The DIGITAL UNIX installation utility that allows you to choose the subsets of the software you require and ensures that the software is installed properly. standby pilot station standby pilot station standby pilot station A standby pilot station can take over from the active pilot station in case of failure. Glossary-2 2 2 Index Index Index Disk Space A A A Requirements 2-3 2-3 2-3 AdvFS 3-5 3-5 3-5 Errors 4-13 4-13 4-13 5-7 5-7 5-7 ; ; 3-3 3-3 3-3 ASE 3-6 3-6 3-6 Files created or modified (Appendix C C C 1 1 1 A) Configuring General Basic Network Restrictions and Services 3-4 3-4 3-4 Considerations 2- 2- 2- Network Interfaces 8 8 8; 3-22 3-22 3-22 for TruCluster ASE Installation 3-7 3-7 3-7 Procedure Overview NPF Base Component 1-3 1-3 1-3 ; 4-9 4-9 4-9 5-5 5-5 5-5 License Information 2-7 2-7 2-7 D D D Planning Decisions DIGITAL NPF Subsets 2- 2- 2- 2-1 2-1 2-1 3-3 3-3 3-3 ; 2 2 2 Pre-installation DIGITAL UNIX prerequisites 3-2 3-2 3-2 dependencies 2-4 2-4 2-4 Pre-installation installing 3-3 3-3 3-3 tasks 3-2 3-2 3-2 patches 3-5 3-5 3-5 Using RIS 4- 4- 4- ; 2-7 2-7 2-7 Disk Space 13 13 13; 5-6 5-6 5-6 Requirements 2-3 2-3 2-3 Installation Media 2- 2- 2- ; 5-1 5-1 5-1 7 7 7 ; 4-2 4-2 4-2 I I I Installation Steps Installation Base Installation Creating links for 5-3 5-3 5-3 the Configuration Full Installation Component 4-10 4-10 4-10 4-3 4-3 4-3 DIGITAL NPF Subsets 2-2 2-2 2-2; 3-3 3-3 3-3 L L L Licensing license types 2-7 2-7 2-7 installation Registering your planning 2-1 2-1 2-1 PAK 3-4 3-4 3-4 Pre-installation Logical Storage prerequisites 3-2 3-2 3-2 Manager tasks 3-2 3-2 3-2 3-5 3-5 3-5 setup Product Authorization LSM Setup See Logical Key PAK See Storage Manager R R R N N N RIS Network Process Using RIS to Failover Platform install DIGITAL overview 1-1 1-1 1-1 2-7 2-7 2-7 NPF ; 5-6 5-6 5-6 4-13 4-13 4-13; non-pilot stations overview 1-1 1-1 1-1 T T T TruCluster ASE P P P Adding a Service PAK 3-4 3-4 3-4 for NPF 3-13 3-13 3-13 registering 3-4 3-4 3-4 Configuring Pilot station 3-5 3-5 3-5 Network Interfaces overview 1-2 1-2 1-2 3-7 3-7 3-7 Pilot stations 3-6 3-6 3-6 installation 3-6 3-6 3-6 Index-2 2 2