TeMIP__________________________________________ Installation Guide Order Number: AA-Q9J2D-TE This guide describes how to install TeMIP on Digital Alpha systems running Digital UNIX. Revision/Update Information: V3.1.0. This edition supersedes the V3.0 edition Operating System and Version: Digital UNIX Version 3.2 Software Version: TeMIP Version 3.1 Digital Equipment Corporation Maynard, Massachusetts _______________________________________________________________ 1996 information in this document is subject to change notice and should not be construed as a commitment Digital Equipment Corporation. Equipment Corporation assumes no responsibility for errors that may appear in this document. software described in this document is furnished under license and may be used and copied only in accordance the terms of such license. No responsibility is for the use or reliability of software on equipment is not supplied by Digital Equipment Corporation or affiliated companies. Rights: Use, duplication, or disclosure by the Government is subject to restrictions as set forth in (c)(1)(ii) of the Rights in Technical Data and Software clause at DFARS 252.227-7013. Digital Equipment Corporation 1996. rights reserved. Printed in Europe. AlphaStation, AlphaGeneration and the design mark, DECnet, DECsafe, DECwindows, UNIX, TeMIP and TeMIP Framework are trademarks of Equipment Corporation. and INGRES/Net and are registered trademarks of corporation. SQL*Net and SQL*Plus are registered trademarks of corporation. is a registered trademark in the United States and countries licensed exclusively through X/Open Company is a registered trademark of X/Open Company, Ltd. UNIX V3.2 is an X/Open UNIX 93 branded product. document is available on CD-ROM. document was prepared using VAX DOCUMENT, Version 2.1. _____________________________________________________ Contents .............................................. vii to Install TeMIP of Installation............................ 1-1 Installation from a CD-ROM .................... 1-1 RIS Installation .............................. 1-1 Requirements........................ 1-2 Hardware Requirements ......................... 1-2 Software Requirements ......................... 1-2 Database Requirements ......................... 1-4 Namespace Requirements ........................ 1-4 Distribution Kit .............................. 1-4 Time Required to Install ...................... 1-5 Logging On .................................... 1-5 Backing Up the System Disk .................... 1-6 Upgrading TeMIP ............................... 1-6 Resource Consumption and System Sizing ........ 1-6 Disk Space Requirements and Directories ....... 1-6 Setting the Digital UNIX Kernel Parameters for TeMIP.......................................... 1-8 Director User Account ......................... 1-13 Creating an "acloc" User Account .............. 1-14 X-Server Configuration....................... 1-15 Initial Actions ............................... 1-15 Checking the Hardware Resolution .............. 1-15 Changing the Resolution ....................... 1-16 Checking Which Font is Used ................... 1-17 Changing the Font Path ........................ 1-17 Problems with Font Size and Resolution ........ Some Options of Your X-Server ................. 1-19 Examples ...................................... 1-19 Changing the Number of Planes ................. 1-20 DECsafe ASE................................ 1-20 DECsafe ASE Installation ...................... 1-20 DECsafe ASE Setup ............................. 1-21 the INGRES Database........................ 1-21 INGRES Installation ........................... 1-22 INGRES Tuning ................................. 1-23 INGRES Configuration .......................... 1-23 diruser Account............................. 1-23 Creating the Database....................... 1-24 Database Access............................. 1-24 Configuring INGRES/Net...................... 1-25 Checking the INGRES Installation and Configuration............................... 1-26 the ORACLE Database........................ 1-27 iii ORACLE Installation ........................... 1-28 ORACLE Configuration .......................... 1-28 diruser Account............................. 1-28 Creating the Database....................... 1-29 Database Access............................. 1-30 Configuring SQL*Net......................... 1-30 Checking the ORACLE Installation and Configuration............................... 1-31 License Registration for TeMIP................... 1-32 Aborting Installation and Recovering from Errors........................................... 1-33 TeMIP From a Previous Version Checking For A Previous Version of TeMIP......... 2-2 Upgrading from TeMIP V3.0........................ 2-2 Upgrading from TeMIP V3.0 With Visual TeMIP 1.0 Installed........................................ 2-3 Checking For Third-Party Programs or Management Modules.......................................... 2-3 Deleting Subsets from Previous Visual TeMIP and TeMIP Versions................................... 2-3 Deleting Third-Party or User Programs That Use TeMIP............................................ 2-3 Deleting a Previous Version of the TeMIP ASCII Management Toolkit............................... 2-4 Setup DECsafe ASE Services............................. 3-1 Disk Service..................................... 3-2 Installing TeMIP and TNS in Disk Services ..... 3-2 System, Hardware, and Logical Configurations .. 3-4 First Service: TNS + Database Server............. 3-5 LSM configuration ............................. 3-6 AdvFS Configuration ........................... 3-6 Creating a TNS and Database Disk Service ...... 3-7 Database Server Pre-installation .............. 3-8 Database Server Installation .................. 3-8 ORACLE Server Post-installation ............... 3-11 TNS Server Installation ....................... 3-11 TNS Server Configuration ...................... 3-11 Add Action Scripts ............................ 3-12 Second Service: TeMIP + Database Client.......... 3-14 LSM configuration ............................. 3-14 AdvFS Configuration ........................... 3-15 Creating a TeMIP Disk Service ................. 3-15 Database Client Configuration or Pre-Configuration.............................. 3-17 Database Configuration or Post-Configuration Tasks.......................................... 3-17 TeMIP Installation ............................ 3-19 Add User acloc ................................ 3-19 Add Users ..................................... 3-19 TeMIP Setup ................................... 3-19 Add Action Scripts ............................ 3-20 TeMIP The Installation Procedure....................... 4-1 Installing from a System Directory ............ 4-2 Installing from a CD-ROM ...................... 4-2 Installing the Kit.......................... 4-2 Installing the BookReader Documentation..... 4-2 Installing from a RIS Server .................. 4-3 System Setup..................................... 4-3 Installation Verification Procedure.............. 4-3 Release Notes.................................... 4-3 Installation from a CD-ROM....................... 4-5 Installation of Visual TeMIP and IVP............. 4-7 RIS Installation................................. 4-8 Installing TeMIP Setting Up Your Namespace........................ 5-1 Checking TCP/IP Reachability .................. 5-1 Configuring Network Time Protocol ............. 5-2 Configuring TNS Server Systems ................ 5-4 Configuring TNS Clerk Systems ................. 5-5 Setting Up Directors After TeMIP Installation.... 5-5 The temip_setup Command ....................... 5-5 Setup Steps ................................... 5-6 Stopping and Starting the TNS Clerk.............. 5-13 Displaying the Result of temip_setup............. 5-13 Changing Setup and Configuration Parameters...... 5-13 Verifying Installations.......................... 5-13 Listing the TeMIP Files Installed................ 5-14 Checklist Installation..................................... A-1 Installation from a CD-ROM....................... A-2 Installation from a RIS Server................... A-2 File of INGRES Installation -1 Disk Space Requirements (Subsets) ............. 1-6 -2 Disk Space Requirements (Installation Directories)................................... 1-7 -3 Kernel Parameters - Quick Reference ........... 1-13 v ____________________________________________________________ Preface This guide describes how to install the TeMIP software on a Digital Alpha system running Digital UNIX [R]+. It includes the setup procedures for secured DECsafe configurations of TeMIP with the supported databases INGRES and ORACLE, and information concerning the use of the TeMIP Name Service (TNS) software. Audience This guide is intended for personnel who are responsible for installing TeMIP on a Digital Alpha system running Digital UNIX, for example: o A system manager installing TeMIP directly on the system from a CD-ROM. o A system manager installing TeMIP from the Remote Installation Services (RIS) server area of a remote system. o A RIS manager installing TeMIP onto a RIS server area. It is assumed that the reader has an understanding of the shell concept of Digital UNIX and is familiar with the mounting of peripheral devices. of This Guide The guide is structured as follows: o Chapter 1 describes the requirements for installing the TeMIP software. o Chapter 2 discusses what to do if you are upgrading from a previous version of TeMIP. o Chapter 3 describes different ways to set up TeMIP and the selected database for operation in DECsafe ASE. o Chapter 4 describes the installation of the TeMIP files directly and on RIS server areas. o Chapter 5 describes how to set up the TNS namespace and TeMIP directors, and how to verify all TeMIP installations. o Appendix A provides a checklist of pre-installation requirements. ____________________ + UNIX is a registered trademark in the United States and other countries licensed exclusively through X/Open Company Ltd. vii Appendix B provides an example log of an INGRES database installation. Conventions following conventions are used in this guide: __________________________________________________________ Meaning__________________________________________________________ The Digital UNIX superuser default prompt. x Indicates that you must hold down the key labelled Ctrl while you press another key or a pointing device button. In examples and procedures, a key combination is enclosed in a box. Indicates that you press the Return key to execute a command line. Indicates the first use of a term, and user input in examples. Italic text is used to indicate the following: o The title of a document to which reference is made. o The directory paths and file names in text and examples. o The emphasis on an important word or concept. __________________________________________________________ Documents guide is part of the TeMIP documentation set. The documents in the set are: Manual TeMIP Introduction (AA-Q9J1C-TE) Manuals TeMIP Installation Guide (AA-Q9J2D-TE) TeMIP OSI Management Toolkit Installation Guide (AA- QEMQD-TE) TeMIP OSI Management Toolkit OSI Access Module Run-Time Kit Installation Guide (AA-QEMRD-TE) TeMIP ASCII Management Toolkit, Installation Guide (AA- QFZ4D-TE) DECcmi for Digital UNIX Installation and Configuration Guide (AA-QENTD-TE) Manuals TeMIP Utilities (AA-Q9JBC-TE) TeMIP Planning Guide (AA-QXSPA-TE) o TeMIP Director Configuration and Management Guide (AA- QN8NB-TE) o TeMIP Name Service Administration Guide (AA-QXSQA-TE) o TeMIP Customization and Troubleshooting Guide (AA-QXSRA- TE) o TeMIP ASCII Management Toolkit, Customization Manual (AA-QDXTD-TE) o TeMIP Framework Security Administration Guide (AA-QD9GC- TE) User Manuals o TeMIP Fault and Trouble Management Alarm Handling User's Guide (AA-Q9J4C-TE) o TeMIP Fault and Trouble Management Trouble Ticketing User's Guide (AA-Q9J8C-TE) o TeMIP Fault and Trouble Management Event Logging User's Guide (AA-Q9J6C-TE) o TeMIP Framework Iconic Map and FCL User's Guide (AA- Q9HMC-TE) o TeMIP Framework DECnet Phase IV Access Module Use (AA- Q9HAC-TE) o TeMIP Framework DECnet/OSI Access Module Use (AA-Q9HBC- TE) o TeMIP Framework TCP/IP SNMP Access Module Use (AA-Q9HCC- TE) o TeMIP Framework Script Access Module Use (AA-Q9HDC-TE) o TeMIP Framework Circuit Access Module Use (AA-Q9HHC-TE) o TeMIP Framework Autoconfiguration Use (AA-Q9HLC-TE) o TeMIP Framework Alarms and Notification Services Use (AA-Q9HEC-TE) o TeMIP Framework Security Operator's Guide (AA-QD9FC-TE) o TeMIP OSI Management Toolkit OSI Access Module GDMO Browser User's Guide (AA-QDYPD-TE) o TeMIP OSI Management Toolkit OSI Access Module GDMO Translator User's Guide (AA-QDYND-TE) o TeMIP OSI Management Toolkit OSI Access Module User's Guide (AA-QDYMD-TE) o TeMIP ASCII Management Toolkit, ASCII Access Module User's Guide (AA-QDXRD-TE) o DECcmi for Digital UNIX Operator's Guide (AA-QDYQD-TE) ix and Software Reference Manuals TeMIP Framework Management Module Programming (AA-Q9H8C- TE) TeMIP Framework Security Software Reference Manual (AA- QD9EC-TE) TeMIP Framework System Reference Manual Volume 1 & Volume 2 (AA-Q9HGC-TE) and (AA-PD5LG-TE) Visual TeMIP Reference Guide (AA-QV89B-TE) Visual TeMIP Development Guide (AA-QV8BB-TE) TeMIP Fault and Trouble Management Reference Guide (AA- Q9J3C-TE) TeMIP Fault and Trouble Management OSI System AM Module Reference Manual (AA-Q9JAC-TE) TeMIP Fault and Trouble Management Alarm Handling FM Module Reference Manual (AA-Q9J5C-TE) TeMIP Fault and Trouble Management Event Log FM Module Reference Manual (AA-Q9J7C-TE) TeMIP Fault and Trouble Management Trouble Ticketing FM Module Reference Manual (AA-Q9J9C-TE) TeMIP Fault and Trouble Management Event Filtering and Correlation FM Module Reference Manual (AA-QK7HB-TE) TeMIP Fault and Trouble Management Event Filtering and Correlation Software Reference Manual (AA-QMWKB-TE) TeMIP Framework Notification FM Module Reference Manual (AA-QXT2A-TE) TeMIP Framework Alarm Generator AM Module Reference Manual (AA-QXT3A-TE) TeMIP ASCII Management Toolkit, ASCII AM Module Reference Manual (AA-QDXUD-TE) of Interest following documents contain additional related DECnet/OSI Planning Guide (AA-QBTHC-TE) Describes how to migrate a network from DECnet Phase IV to DECnet/OSI, including configuration guidelines and task planning. Digital UNIX Documentation Set Describes how to use and manage the Digital UNIX operating system. Digital UNIX Guide to Remote Installation Services Describes how to install and maintain your remote installation environment using the RIS utility. INGRES Installation and Operations Guide Describes how to install, configure and maintain an INGRES database. o INGRES Database Administrator's Guide Describes how to manage an INGRES database. o INGRES/SQL Reference Manual Provides a detailed description of how to issue SQL queries and develop applications. Examples of the correct use of SQL statements and INGRES features are also given. o INGRES/Net User's Guide Describes how to install, use and maintain INGRES/Net. o ORACLE Installation and Configuration Guide Provides installation and configuration information for ORACLE databases and tools. o ORACLE Server Administrator's Guide Describes how to manage ORACLE databases. o ORACLE Server SQL Language Reference Manual Gives a complete description of the SQL language used to create, store, modify, retrieve and manage information in an ORACLE database. o ORACLE SQL*Plus User's Guide and Reference Describes the SQL* program and gives a detailed description of each command. o ORACLE SQL*Net Administrator's Guide. Describes how to use ORACLE tools and applications to access, manipulate, share and store data in ORACLE databases residing on remote servers. o DECsafe Available Server Installation Guide. Describes how to install the DECsafe Available Server hardware and software to give access to applications in a network environment. o Guide to the DECsafe Available Server. Describes how to set up and manage the systems and services in the DECsafe Available Server environment. xi 1 ____________________________________________________________ Preparing to Install TeMIP This chapter describes the requirements and preparations for installing TeMIP. The installation procedures described in this guide apply only to TeMIP Version 3.1. Release Notes are provided with the installation kit and Digital strongly recommends that you read these notes before proceeding with the installation. The topics discussed in this chapter include: o Types of Installation, Section 1.1 o Installation Requirements, Section 1.2 o The X-Server Configuration, Section 1.3 o Using DECsafe ASE, Section 1.4 o Using the INGRES Database, Section 1.5 o Using the ORACLE Database, Section 1.6 o License Registration for TeMIP, Section 1.7 o Aborting Installation and Recovering from Errors, Section 1.8 of Installation You can install TeMIP in several different ways using the procedures described in this guide. Installation can be done directly from a CD-ROM or using Remote Installation Services (RIS). The procedure for each type of installation is described in Chapter 4. Installation from a CD-ROM You can install TeMIP directly on your system from a CD- ROM. RIS Installation You can install TeMIP on a RIS server area of a remote system and then install TeMIP on your system from the RIS server. If you intend to install TeMIP on your system in this way, ensure the following: o A TeMIP kit is installed and running on the RIS server. o You know the name of the RIS server. o Your system is registered as a RIS client. For further details of RIS refer to the Digital UNIX Guide to Remote Installation Services. Preparing to Install TeMIP 1-1 Requirements installation requirements for TeMIP are described in 1.2.1 to Section 1.2.14 and a pre-installation is provided in Appendix A. Requirements minimum hardware requirements for the installation of are as follows: can install TeMIP on any Digital Alpha system running UNIX. Requirements software requirements are as follows: Subsets install TeMIP you require the following version of the UNIX operating system running on a Digital Alpha Version 3.2G following subsets must be installed: OSFBASE350 Base System software OSFX11350 Basic X Environment software OSFCLINET35* Basic Networking Services OSFRTDEV35* Realtime Software Development CXXSHRDA307 DEC C++ shared libraries subsets allow you to use TeMIP as follows: In a non-distributed configuration, with a MIR or TNS namespace In a distributed configuration, with a TNS namespace OSFCLINET35* subset includes Network Time Protocol for synchronization if required. Kits for DECsafe you want to ensure high availability by securing your with DECsafe, one of the following additional kits is TruCluster Production Server (TruCluster Software) V1.0 or TruCluster Available Server (DECsafe Available Server) V1.3, in both of which the DECsafe ASE V1.3 equivalent is embedded. ________________________ Note ________________________ TeMIP does not use features of Trucluster Production Server V1.0 other than DECsafe (Memory Channels and so on). ______________________________________________________ to Install TeMIP Optional Subsets for Visual TeMIP If you intend to use the Visual TeMIP C++ Developer Toolkit, the following additional C++ compiler subsets are required: o CXXBASE540 DEC C++ (cxx) for Digital UNIX o CXXLIB540 DEC C++ static class libraries o CXXV3HDR540 DEC C++ header files for Digital UNIX V3.x o CXXMAN540 DEC C++ and class library manual pages BASE, LIB and HDR are mandatory for Visual TeMIP; MAN is optional. Optional Subsets for Managing a DECnet/OSI Network If you want to manage your DECnet network using TeMIP Framework, the following additional subsets are required: o DNABASE323 DECnet/OSI Base Components o DNADLI323 DECnet/OSI Datalink Components o DNANETMAN323 DECnet/OSI Network Management To be able to use this software, you need the DECNET-OSI- END license. ________________________ Note ________________________ Previous versions of TeMIP used version V3.2A of DECnet/OSI. TeMIP Version 3.1 requires you to upgrade to DECnet/OSI version V3.2B, provided by the above DNA*323 subsets. See DECnet/OSI V3.2B Release Notes, Chapter 2 (Installation Notes) for some details you should be aware of before installing DECnet/OSI for Digital UNIX software. ______________________________________________________ Optional Subsets for TNS Dual-Stack Mode If you intend to use your system as a TNS server operating in dual-stack mode, the following DECnet/OSI subsets are required: o DNABASE323 DECnet/OSI Base Components o DNADLI323 DECnet/OSI Datalink Components o DNANETMAN323 DECnet/OSI Network Management o DNADECDNSSRV323 DECnet/OSI DECdns Server o DNATFRDNSSRV32B1 DECnet/OSI DECdns Server for TeMIP ECO 1 To use this software you need the DECNET-OSI-EXT licence. _______________________ Notes: _______________________ 1. TeMIP Version 3.1 requires you to use DECnet/OSI version V3.2B, provided by the above DNA*323 subsets. See DECnet/OSI V3.2B Release Notes, Chapter 2 (Installation Notes) for some details Preparing to Install TeMIP 1-3 you should be aware of before installing DECnet/OSI for Digital UNIX software. 2. You must use the latest TeMIP ECO for the DECnet/OSI DECdns Server (currently the subset DNATFRDNSSRV32B1) ______________________________________________________ Requirements you plan to use the Archive function of the TeMIP Handling or TeMIP Trouble Ticketing applications, require the INGRES or ORACLE databases installed and Database use INGRES with TeMIP, you must have version V6.4/05 You require a base license. You also require installed for UNIX with the TCP/IP protocol if plan to install the database on a remote station. Database use ORACLE with TeMIP, the mandatory ORACLE subsets are follows: ORACLE7 Server V7.3.2 SQL*Plus V3.3 ________________________ Note ________________________ You do not need to have the database installed or running during the installation of TeMIP. ______________________________________________________ Requirements you want to use TeMIP in a distributed configuration will therefore be using a TNS namespace, you need to at least one Digital Alpha system configured as a server. The necessary software subsets are part of the distribution kit. the system that operates as your TNS server will a dedicated system, with only the TNS subsets of TeMIP on it. However, depending on the size of your and your operational constraints, you may to install TNS subsets and other TeMIP subsets on the system. you are migrating from a DNS namespace to a TNS see the TeMIP Name Service Administration Guide a discussion on migration strategies. Kit sure that you have the correct distribution kit and the contents against the Bill of Materials (BOM). any part of the kit is missing, contact your Digital to Install TeMIP TeMIP can be installed on a Digital Alpha system running Digital UNIX from the Consolidated Distribution CD-ROM bearing the label TeMIP Version 3.1 for Digital UNIX. Your distribution kit contains the following TeMIP software subsets: o TFRBASE TeMIP Framework Base System o TFRSERVER TeMIP Framework Server o TFRPM TeMIP Framework Presentation Modules o TFRTK TeMIP Framework Developer Toolkit o TFRTFC Visual TeMIP C++ Developer Toolkit o TFRTNSCLRK TeMIP Name Service Clerk o TFRTNSSRV TeMIP Name Service Server o TFRREL TeMIP Framework Release Notes You can install some subsets on a system and add others later. The TFRTNSCLRK subset (Distributed Name Service Clerk for TeMIP) is a mandatory subset for the use of the TeMIP Name Service (TNS). The TFRTNSSRV subset (Distributed Name Service Server for TeMIP) is required to configure a TNS server only, together with the TFRTNSCLRK subset. ___________________ Important Note: ___________________ Read the Release Notes before starting the installation. They may contain additional information about software requirements and patches. ______________________________________________________ For information concerning license registration, refer to Section 1.7. For information concerning the various TeMIP licenses, refer to the section on licensing in the TeMIP Planning Guide. Time Required to Install Direct installation of TeMIP takes 5 to 15 minutes, depending on the system configuration. The Installation Verification Procedure (IVP) takes 1 to 5 minutes more. Installation from a RIS server should take about the same time as a direct installation, depending on the amount of traffic in the network. Logging On Before you start the installation, log onto a superuser account on the system where you want to install TeMIP. You can set the current working directory to the top level (or root) directory using the following command: # cd / Preparing to Install TeMIP 1-5 Up the System Disk strongly recommends that you back up your complete disk or at least the /var and /usr partitions. of TeMIP involves writing to these partitions. TeMIP you have, or may have, a previous version of TeMIP on your system, you must carry out the checks and procedures before starting the of the new version. See Chapter 2 for details. Resource Consumption and System Sizing advice on disk occupation, swap file size, memory and sizing considerations in general, contact TeMIP Consultancy Group. Disk Space Requirements and Directories different TeMIP software subsets require different of disk space as shown in Table 1-1. The values are approximate and may vary from kit to kit. set of values represents the disk space required if copy the subsets to a directory on your disk before them. 1-1 Disk Space Requirements (Subsets)__________________________________________________________ Subset Disk Space (in KB)__________________________________________________________ TeMIP Framework Base 31872 TeMIP Framework 42016 TeMIP Framework 19680 Modules TeMIP Framework 4200 Toolkit Visual TeMIP C++ 7736 Toolkit TeMIP Name Service 5504 TeMIP Name Service 3416 TeMIP Release Notes 10 __________________________________________________________ 114434__________________________________________________________ 1-2 shows the disk space requirements in KB installed TeMIP subsets in directories /usr/mcc, , /usr/tns, /var/mcc and /var/kits. This set values represents the disk space required for direct to Install TeMIP Table 1-2 Disk Space Requirements (Installation __________Directories)_____________________________________ Subset___________/usr/mcc/usr/kit/usr/tns/var/mcc/var/kits_ TFRBASEV310 50033 2070 0 12 0 TFRSERVERV310 20693 17320 0 0 0 TFRPMV310 8247 11945 0 0 0 TFRTKV310 9212 2275 483 0 0 TFRTFCV310 26144 0 0 0 0 TFRTNSCLRKV310 6 0 3672 0 0 TFRTNSSRVV310 2 0 2330 0 0 TFRRELV310 0 0 0 0 0 ___________________________________________________________ Total_(KB)_______114337__33610___6485____12______0_________ In addition to the space required for subsets, you will need working space for configuration, Alarm Objects, and Telecommunications Trouble Reports (TTRs). The likely requirement is about 500 MB. For "medium sized" Alarm Objects, 100,000 Alarm Objects = about 100 MB of disk space. The installation procedure creates the following directories if they do not already exist: For TeMIP Framework /usr/mcc /var/mcc For TeMIP Fault and Trouble Management /usr/kits/TNM310 /usr/var/kits/temip For TNS /usr/tns /usr/var/tns The TeMIP executable files must be in the /usr/kits/TNM310, /usr/mcc, and /usr/tns directory trees. However, you can mount a separate file system on /usr/kits/TNM310 or /usr/mcc if you want to keep the TeMIP executable files separate from the rest of the /usr file system. The installation procedure creates the TeMIP Management Information Repository (MIR) files in the directory trees /usr/var/kits/temip and /var/mcc, together with the TeMIP data files. The TeMIP Name Service (TNS) data files are stored under the /usr/var/tns directory. It is recommended that you have at least 200 MB of additional disk space available in the /usr/var partition for collecting network data and reports. Preparing to Install TeMIP 1-7 Setting the Digital UNIX Kernel Parameters for TeMIP of the kernel parameter default values suit a Digital UNIX configuration, however, specific may require modification of some of the For all parameters, the current value can be using one of the following commands; sysconfig proc, sysconfig -q vm or sysconfig -q ipc. the kernel parameters are checked by the temip_setup and a warning message is issued if a parameter is the recommended value. parameters can be modified in two different ways: You can change the values in the static configuration file /sys/conf, rebuild the kernel and then reboot the system. You can modify the dynamic configuration file /etc/sysconfigtab and reboot the system, (no kernel rebuild is required). An example sysconfigtab file is as follows: proc: max-proc-per-user = 256 max-threads-per-user = 8172 vm: vm-vpagemax = 32768 ipc: shm-max = 4194304 shm-min = 1 shm-mni = 128 shm-seg = 32 sem-mni = 128 sem-msl = 640 sem-opm = 128 sem-ume = 128 following parameters can be modified: Description: Defines the maximum number of users that can be logged in simultaneously on the system. This value influences the maximum number of files open simultaneously on the system. Default Value: System dependent Recommended Value for TeMIP server: 128 Recommended Value for TeMIP client: 64 Modification: Change maxusers in the static configuration file. to Install TeMIP To display the value of the maxusers parameter, enter: # dbx /vmunix dbx version 3.11.8 Type 'help' for help. main: Source not available warning: Files compiled -g3: parameter values probably wrong (dbx) p maxusers 256 (dbx) quit # maxuprc Description: Defines the maximum number of processes that a user can create. Default Value: 64 Recommended Value for TeMIP server: 256 Recommended Value for TeMIP client: 64 Increase this value if you run many processes at the same time. Modification: Change maxuprc in the static configuration file or the max-proc-per-user entry in the /etc/sysconfigtab file. max-threads-per-user Description: Defines the maximum number of threads that a user can create. Default Value: 256 Recommended Value: 1024 Increase this value if you perform many mcc_calls, for example, if you enable more than 200 alarm rules. Modification: Change the max-threads-per-user entry in the /etc/sysconfigtab file. Preparing to Install TeMIP 1-9 Description: Defines the maximum number of vpages for a user map, or the maximum number of individually protected pages. As a consequence, this parameter also defines the maximum size allowed for a shared memory segment. Default Value: 16384 pages Recommended Value: 32768 bytes Increase this value if you perform many mcc_calls, for example, if you enable more than 200 alarm rules. Modification: Change vpagemax in the static configuration file or the vm-vpagemax entry in the /etc/sysconfigtab file. Description: Defines the maximum size allowed for a shared memory segment. Default Value: 4194304 bytes Recommended Value: 4194304 bytes Increase this value if you define MCC_EVENT_POOL_SIZE greater than 4194304. Modification: Change shmmax in the static configuration file or the shm-max entry in the /etc/sysconfigtab file. Description: Defines the minimum size allowed for a shared memory segment. Default Value: 1 byte Recommended Value: 1 byte Do not increase this value if you use TeMIP Alarm Handling or Event Logging, because the use of these functions requires the creation of small shared memory segments (less than 60 bytes). Modification: Change shmmin in the static configuration file or the shm-min entry in the /etc/sysconfigtab file. to Install TeMIP shmmni Description: Defines the number of shared memory identifiers. Default Value: 128 Recommended Value: 128 Increase this value if you create more than 128 Operation Contexts or Logs. Modification: Change shmmni in the static configuration file or the shm-mni entry in the /etc/sysconfigtab file. shmseg Description: Defines the maximum number of attached shared memory segments per process. Default Value: 32 Recommended Value: 32 Increase this value if you access many TeMIP objects (Operation Contexts or Logs). Modification: Change shmseg in the static configuration file or the shm-seg entry in the /etc/sysconfigtab file. semmni Description: Defines the maximum number of semaphores that can be in use on the system at any one time. Default Value: 16 Recommended Value for TeMIP server: The number of Operation Contexts and Logs active in the system + 20 + the number needed by other applications. Recommended Value for TeMIP client: 16 Increase this value if you create more than semmni Operation Contexts or Logs. Modification: Change semmni in the static configuration file or the sem-mni entry in the /etc/sysconfigtab file. Preparing to Install TeMIP 1-11 Description: Defines the maximum number of semaphores that can be in use by a single process at any one time. Default Value: 25 Recommended Value for TeMIP server: The number of Operation Contexts and Logs active in the system + 20 Recommended Value for TeMIP client: 25 Modification: Change semmsl in the static configuration file or the sem-msl entry in the /etc/sysconfigtab file. Description: Defines the maximum number of operations per semop call. Default Value: 10 Recommended Value: semmni Modification: Change semopm in the static configuration file or the sem-opm entry in the /etc/sysconfigtab file. Description: Defines the maximum number of undo entries per process. Default Value: 10 Recommended Value: semmni Modification: Change semume in the static configuration file or the sem-ume entry of the /etc/sysconfigtab file. setting the shared memory, semaphore and maximum memory consumption process parameters, rebuild kernel as described in the Digital UNIX Guide to File Management. 1-3 shows the default and recommended values for the parameters as a quick reference: to Install TeMIP Table_1-3_Kernel_Parameters_-_Quick_Reference______________ Default Parameter Value Recommended Value: _______________________________Server_____________Client___ maxusers System 128 64 dependent maxuprc 64 256 64 max-threads- 256 1024 1024 per-user vpagemax 16384 32768 32768 shmmax 4194304 4194304 4194304 shmmin 1 1 1 shmmni 128 128 128 shmseg 32 32 32 semmni 16 Number of active 16 OCs and Logs + 20 + number for other apps semmsl 25 Number of active 25 OCs and Logs + 20 semopm 10 semmni semmni semume___________10____________semmni_____________semmni___ Director User Account After installation, during the setup of each TeMIP director, you are asked to choose a name for the Director User Account. This account can have any user_id you want, but it must be a member of the same group as all other users of TeMIP. _______________________ Notes: _______________________ 1. From now on the Director User Account will be referred to as the diruser account. 2. If you are going to operate in DECsafe ASE, the diruser must be the same on the two support hosts providing the disk service. ______________________________________________________ The setup procedure is carried out using the temip_setup utility, which causes a change in ownership of some of the TeMIP files and directories. The the diruser enables multi-user access to individual TeMIP processes. For details of how to use the temip_setup utility to configure your system, refer to Chapter 5. Preparing to Install TeMIP 1-13 Creating an "acloc" User Account installing TeMIP for the first time, you must create user account acloc. This account can have any user_id want, but it must be a member of the same group as all users of TeMIP. For example, if all users of TeMIP to the group users, then the acloc account must also created as a member of the group users. The user acloc be the owner of the directory /var/mcc/acloc. ________________________ Note ________________________ If you are going to operate in DECsafe ASE, the acloc uid must be the same on the two support hosts providing the disk service. ______________________________________________________ details of how to create a user account, refer to the UNIX System Administration documentation. the acloc account as follows: Log on as root Enter the command adduser at the superuser prompt: # adduser You are prompted to enter the following information for the new user: Enter a login name for the new user (for example, john): acloc Enter a UID for (acloc) [413]: Enter a full name for (acloc): TeMIP Administrator Enter a login group for (acloc) [users]: Enter another group that (acloc) should be a member of ( only if none): You are now prompted to enter a parent directory and login shell: Enter a parent directory for (acloc) [/usr/users]: The shells are: /usr/bin/sh /usr/bin/ksh /bin/csh /bin/ksh /usr/bin/csh /bin/sh Enter a login shell for (acloc): /bin/csh Adding new user... Rebuilding the password base... 28 password entries, maximum length 87 You are asked if you want to edit the authentication file entry for the new user: Do you wish to edit the auth. file entry for this user (y/[n])? Creating home directory... You are now prompted to enter a new password: You must enter a new password for (acloc). Changing password for acloc. New password: Retype new password: Finished editing user account for (acloc). to Install TeMIP X-Server Configuration The visual presentation of TeMIP will vary according to the resolution of your hardware, that is, according to the type of monitor and graphics card you are using. ________________________ Note ________________________ This section only applies to systems running Presentation Modules. ______________________________________________________ DECwindows supports two resolution values, 75dpi and 100dpi (dots per inch) and the X-Server provides a separate set of fonts for each value. At start-up, the X-server sets the resolution and selects the fonts according to how these have been defined in your configuration. To obtain the best presentation quality it is important that the font type matches the resolution of the X-Server. As with any "X" application, TeMIP assumes that your X-Server is correctly configured, which in practice is usually the case. As a check you can verify the configuration, and if necessary make changes, by following the steps described in Section 1.3.1 to Section 1.3.8. This will ensure that all your "X" applications display correctly. Initial Actions The first thing you must do is to make sure that your display is properly set. You must set the DISPLAY environment variable and your session manager security. The steps described in this section can be performed remotely (on a machine other than that on which the X- Server is running), but you must make sure that: o Your DISPLAY variable points to the machine where the X-Server you want to test is running o You make any configuration modifications on the machine where the X-Server is running. Checking the Hardware Resolution There are three steps involved in checking the hardware resolution: 1. Check the system-defined hardware resolution in terms of pixels 2. Use the horizontal pixel size to calculate the resolution of your screen in terms of dots/inch 3. Compare your dots/inch calculation against the X-Server dpi setup value. In /usr/bin/X11 there should be a command named xdpyinfo, that provides you with information about the configuration of your X-Server. If this command is not installed on your system, install the subsets OSFXMIT3xx and OSFMANWOS3xx. The number "3xx" indicates the Digital UNIX version being used and may be different on your system. The second subset contains the MANPAGES. Preparing to Install TeMIP 1-15 1. Checking the system-defined resolution: you run /usr/bin/X11/xdpyinfo a number of lines will displayed, one of which will indicate the display in pixels (and millimetres). This could, for be as follows: #0: dimensions: 1024x864 pixels (346x292 millimetres) information to use from this example is the horizontal size (1024), from which you calculate the resolution the screen in terms of dots per inch. 2. Calculate the dpi of your screen: a general rule: When you see 1024x864 pixels, you have a 75dpi hardware When you see 1280x1024 pixels, you have a 100dpi hardware. you prefer to make your own calculation, take a ruler measure the width of your screen in inches, then divide horizontal pixel size by this number. For example, if screen is approximately 13 inches wide: = 75 dpi. (1) 3. Compare dpi calculation with system setup: the output of /usr/bin/X11/xdpyinfo, locate the line gives the X-Server setup value in dpi. This could be follows: 75x75 dots per inch (2) that if you get 78x78, that equates to "75dpi" "98x98" equates to "100dpi" resolution, and on... this example the X-Server configuration is correct the calculated resolution in (1) matches the setup in (2). If the results from (1) and are different, your X-Server is not using the resolution and if you want you can change it. you could leave it as it is and accept a quality display. the Resolution the resolution of your X-Server is wrong and you decide change it, proceed as follows: Log in as root Edit the file /usr/lib/X11/xdm/Xservers or /usr/dt/config/Xservers if you have CDE installed. is a line (the last one) that is similar to the local /usr/bin/X11/X to Install TeMIP where X is the name of the X-Server program. It may be different on your configuration, but the options remain the same. Refer to the MANPAGES if necessary (type man Xserver at the shell prompt). Edit the line by adding the value of your hardware resolution immediately after the X-Server program name (X). Add -dpi XXX, where XXX is the resolution of your hardware (either 75dpi or 100dpi). For example, if you have a 75dpi hardware the last line of /usr/lib/X11/xdm/Xservers or /usr/dt/config/Xservers if you have CDE installed will be as follows: :0 local /usr/bin/X11/X -dpi 75 Checking Which Font is Used To know which font is being used by your X-Server, check the PATH by typing: /usr/bin/X11/xset q (from the same subset as xdpyinfo). You will see a line giving one or more font paths. The following example of what you could find shows two font paths: Font Path: /usr/lib/X11/fonts/decwin/75dpi/,/usr/lib/X11/fonts/private/75dpi/ (PATH 1) (PATH 2) This example shows that the X-Server uses 75dpi fonts, which is correct if your hardware resolution check also gives 75dpi. The last directory of each PATH must match the resolution of your X-Server. If the font path check indicates a difference between the font and the hardware resolution, you need to change the font path specification as described in Section 1.3.5. Alternatively, you could leave it as it is and accept a lower quality display. Changing the Font Path As an example, if your hardware resolution check showed 75dpi, but the font path check produced a line as follows: Font Path: /usr/lib/X11/fonts/decwin/100dpi/,/usr/lib/X11/fonts/private/100dpi/ then this shows that the fonts are incompatible with the hardware resolution and the paths should be changed. You should specify the two 75dpi font paths as shown in Section 1.3.4. To change the font paths proceed as follows: 1. Log in as root 2. Edit the file /usr/lib/X11/xdm/Xservers or /usr/dt/config/Xservers if you have CDE installed. There is a line that is similar to the following: :0 local /usr/bin/X11/X -dpi 75 Preparing to Install TeMIP 1-17 X is the name of the X-Server program. It may be on your configuration, but the options remain the Refer to the MANPAGES if necessary (type man Xserver the shell prompt). the line by adding the font paths PATH1 and PATH2 given in Section 1.3.4, immediately after the X-Server name (X). -fp /usr/lib/X11/fonts/decwin/75dpi/ (PATH1), /usr/lib/X11/fonts/private/75dpi/ (PATH2) last line of /usr/lib/X11/xdm/Xservers or if you have CDE installed should be as follows: local /usr/bin/X11/X -dpi 75 -fp /usr/lib/X11/fonts/decwin/75dpi/, /usr/lib/X11/fonts/private/75dpi/ ________________________ Notes ________________________ Resolution: The use of 75dpi and 100dpi monitors has been successfully tested. For monitors of any other resolution, the 75dpi settings should be used. Dimensions: The minimum screen dimension is 1024x864. ______________________________________________________ with Font Size and Resolution some cases where the font resolution is 75dpi and a with a small screen is used, text and small images be difficult to see. In order to fix this problem it is to modify the following files: /usr/lib/X11/app-defaults/MCCclass /usr/lib/X11/app-defaults/mcc_resource.dat /usr/lib/X11/app-defaults/TeMIP /usr/lib/X11/app-defaults/temip_resource.dat of these files has font description lines, which a number that describes the font size to be used. example: -*-Times-Medium-R-Normal-*-*-60-*-*-*-*-ISO8859-1 ^^ font size is recommended that you edit the files so that the font in each case is set to at least 90, or 100 if you a larger font. ________________________ Notes ________________________ o To edit these files, first copy them to $HOME and then edit the copies. to Install TeMIP o Where the font description lines wrap to the next line in the file, it is important not to insert a newline character at the end of the partial first line, or add spaces at the end of the line prior to the newline character, or change other parts of the font description. Only the font size should be modified. ______________________________________________________ After modifying the files /usr/lib/X11/app- defaults/MCCclass or /usr/lib/X11/app-defaults/mcc_ resource.dat, restart the Iconic Map. After modifying the file /usr/lib/X11/app-defaults/TeMIP, restart TeMIP PM. In either case it is not necessary to restart any other TeMIP Modules. For more information and an example concerning /usr/lib/X11/app-defaults/TeMIP, refer to the TeMIP Customization and Troubleshooting Guide. Some Options of Your X-Server There are several useful options available on your X-Server that you can use to change the default settings. Check in the manpages of your X-Server for details. If your display system is a Digital UNIX V3.2 machine, the following X-server option is recommended. o -terminate, kills and restarts the X-Server each time you log out If your display system is not a Digital UNIX V3.2 machine, you may need to add following options: o -su, Disables the SaveUnders o -bs, Disables the BackingStore Note that you do not lose any functionality if you use these options. Examples The following are two examples of lines in /usr/lib/X11/xdm/Xservers or /usr/dt/config/Xservers if you have CDE installed: Example 1: To correct a 75dpi hardware with the default Font Path correct, but with the wrong resolution add: :0 local /usr/bin/X11/X -dpi 75 -terminate -bs -su Example 2: To correct a 100dpi hardware with the wrong default resolution and Font Path add on the same line: :0 local /usr/bin/X11/X -dpi 100 -fp /usr/lib/X11/fonts/decwin/100dpi/ -bs -su -terminate ________________________ Note ________________________ Reboot your station to make any changes effective. ______________________________________________________ Preparing to Install TeMIP 1-19 the Number of Planes you are going to install the Iconic Map of TeMIP on a AlphaStation, you will need to change the number planes to 8. check the number of planes and correct it if necessary, as follows: Use the command xdpyinfo in /usr/bin/X11 to display the X-Server configuration, see also Section 1.3.2. Following is an example of the relevant part of the output, with the plane parameter indicated: . . . screen #0: dimensions: 1280x1024 pixels (342x274 millimeters) resolution: 95x95 dots per inch depths (1): 8 root window id: 0x2e depth of root window: 8 planes <=== number of colormaps: minimum 1, maximum 1 default colormap: 0x21 default number of colormap cells: 256 preallocated pixels: black 1, white 0 . . . Login as root. Edit /usr/lib/X11/xdm/Xservers or /usr/dt/config/Xservers if you have CDE installed to replace -nice -2 with -vclass PseudoColor. DECsafe ASE Available Server Environment (ASE) is a highly organization of systems and disks that provide availability of data and software to client systems. ________________________ Note ________________________ DECsafe ASE must be installed and configured before installation of TeMIP and your chosen database. This sequence is necessary as installation of both TeMIP and the database requires that appropriate disk mount points are previously configured on a shared fileset. ______________________________________________________ ASE Installation you use DECsafe ASE, then it must be installed on all members of your configuration according to the relevant ASE installation procedure. For more information on DECsafe ASE utilities and procedures mentioned in this refer to the appropriate DECsafe documentation: TruCluster Software Installation and Configuration Guide to Install TeMIP o TruCluster Software Cluster Administration o DECsafe Available Server Installation Guide o Guide to the DECsafe Available Server. Otherwise, request assistance from your system manager. DECsafe ASE Setup DECsafe ASE setup consists of two steps: 1. Creation and configuration of a disk service for installation of the TeMIP and database software. 2. Association of the configuration scripts (DECsafe action scripts). The action scripts are contained in the kit and can be found in the directory /usr/kits/TNM310/examples. For details of DECsafe setup, see Chapter 3. the INGRES Database Section 1.5.1 to Section 1.5.3 describe how to configure the INGRES database for TeMIP Alarm Handling Archive directive and TeMIP Trouble Ticketing access. It is assumed that the INGRES database has been installed according to the relevant INGRES installation procedure. For more information on the INGRES utilities and procedures mentioned in this section, you should refer to the appropriate INGRES documentation: o INGRES Installation and Operations Guide o INGRES Database Administrator's Guide o INGRES/SQL Reference Manual o INGRES/Net User's Guide. Otherwise, request assistance from your system/database manager. ________________________ Notes ________________________ 1. A number of scripts are provided for management of the INGRES database. These scripts are mandatory; you must use them. The scripts are located in /usr/kits/TNM310/examples. Refer to the TeMIP Utilities manual for further information. 2. If you want to install the INGRES database in a DECsafe ASE environment, ensure that DECsafe ASE is installed and configured before installation of the database, see Chapter 3. ______________________________________________________ Preparing to Install TeMIP 1-21 Installation must be installed and initialized using the iibuild INGRES utility, as described in the INGRES and Operations Guide. Refer to Section 1.2.3 a list of INGRES parts and the relevant version numbers must be installed. Appendix B you will find a log of an INGRES Note however, that the procedure may vary according to the version of the tool that is used. ensure that INGRES has been configured correctly on your Log in as ingres (su - ingres) Use the syscheck INGRES utility. the event of any problems, consult your system/database or the INGRES Installation and Operations Guide. ensure that INGRES is running use the Digital UNIX aux | grep ingres similar to the following will be displayed: ingres 791 0.0 0.5 316 120 p3 I 0:00 iislave 1 0 2 0 @@@@@@@@ ingres 753 0.0 1.3 364 332 p3 I 0:00 iigcn II ingres 763 0.0 4.8 3540 1264 p3 S 0:03 dmfrcp II ingres 792 0.0 0.5 316 120 p3 I 0:00 iislave 1 0 2 1 @@@@@@@@ ingres 782 0.0 12.1 6284 3224 p3 I 0:02 iidbms II 4461 ingres 767 0.0 4.6 3532 1216 p3 I 0:00 dmfacp II are two points to note regarding the sample display The iigcc process must be present in the case of INGRES/Net initialization The iislave processes may not be present, but may be started automatically later. INGRES is not configured or running correctly: Log in as ingres (su - ingres) Use the iistartup INGRES utility, (see the INGRES Installation and Operations Guide). to Section 1.5.2 before running this utility. ______________________ Remember ______________________ INGRES/Net must be configured if you plan to access a remote database. ______________________________________________________ to Install TeMIP INGRES Tuning Depending on how you plan to use TeMIP, you may need to modify the number of concurrent sessions allowed. This can be done: o At installation time when using the iibuild utility, by entering the required number of concurrent sessions o When using the iistartup utility, with -init option (- connected_sessions DBMS server option), and answering the question: 'Enter number of concurrent sessions in the installtion' As a general rule you should allow for the archive function: o One session for each "concurrent" Archive directive o One session for an Archive directive in background. As a general rule you should allow for the TeMIP Trouble Ticketing: o One session for each concurrent Trouble Ticketing directive. ________________________ Note ________________________ Remember to take into account any remote sessions running on a client machine. ______________________________________________________ INGRES Configuration The director user account name is known as the diruser account. diruser Account To register the user diruser with INGRES you must: o Log in as ingres o Use the accessdb INGRES utility o Choose user o Enter the diruser when you are asked for the username o Assign all permissions o Do not take into account the default group field. o Save Modify the environment variables in the TeMIP configuration file as follows: o Set II_SYSTEM to the INGRES installation location. o Append INGRES paths to your path. o Set terminal option for INGRES Utilities. For further details of the TeMIP configuration file. see the TeMIP Customization and Troubleshooting Guide. Preparing to Install TeMIP 1-23 of INGRES Environment Variable Settings II_SYSTEM /usr/kits/ingres path = ($II_SYSTEM/ingres/bin $II_ $path) TERM_INGRES vt100i you obtain the following message when running the TeMIP environment variable II_SYSTEM is not set correctly. means that the II_SYSTEM variable has not been set in TeMIP configuration file or diruser account. ___________________ Important Note ___________________ If you encounter problems using the INGRES database, always check that the II_SYSTEM variable is correctly set in the TeMIP configuration file or diruser account. ______________________________________________________ Creating the Database be able to use the TeMIP Alarm Handling Archive or TeMIP Trouble Ticketing, the INGRES database first be created under the diruser account, as a database. It is not mandatory that the database created as private, but it is recommended in order to access by unauthorized users. general procedure is: Login as diruser Type the command: createdb -p ) ( can be up to 24 characters maximum). specifically, the default INGRES database (temip_ah) be used by the Alarm Handling FM Archive directive must created using the command: -p temip_ah the default INGRES database (temip_tt) to be used by TeMIP Trouble Ticketing FM must be created using the -p temip_tt Database Access only requires that the user diruser has access to the Each object in the database is owned by the user and only this user can access them. To preserve consistency, it is recommended that access to users is only granted when absolutely necessary. to Install TeMIP Configuring INGRES/Net On each client machine: o Log in as ingres o Use the INGRES netu utility ________________________ Notes ________________________ 1. The servername is a vnode name representing the machine where the INGRES server is situated. 2. The remote node address can be an alias or the Internet address. ______________________________________________________ Proceed as follows: o Type in the following command: > netu o The following information is displayed: INGRES/NET MANAGEMENT UTILITY -- -- Copyright (c) 1989, 1991 Ingres Corporation Select one of the following: Q - Quiesce INGRES/NET S - Stop INGRES/NET N - Modify Node Entry A - Modify Remote Authorization Entry E - Exit NETU> N o Enter N and press Return to modify a node entry. You are then asked to supply the following information: Modify Node Entry: Enter operation (add, merge, del, show, exit): add Enter Private or Global (P): G Enter the remote v_node name: servername Enter the network software type (tcp_ip): Default value: tcp_ip Enter the remote node address: servername Enter the remote INGRES/NET Server Listen address (II): Default value: II o Enter the options you want and press Return after each entry. You are then requested to select another operation: 1 row(s) added to the Server Registry Select one of the following: Q - Quiesce INGRES/NET S - Stop INGRES/NET N - Modify Node Entry A - Modify Remote Authorization Entry E - Exit NETU> A Preparing to Install TeMIP 1-25 Enter A and press Return to modify a remote authorization entry. You are then asked to supply the following information: Modify Remote Authorization Entry: Enter operation (add, del, show, exit): add Enter Private or Global (P): G Enter the remote v_node name: servername Enter remote User Name: diruser Enter the remote Password: xxxxxx Repeat the remote Password: xxxxxx Enter the options you want and press Return after each entry. You are then requested to select another operation: 1 row(s) added to the Server Registry Select one of the following: Q - Quiesce INGRES/NET S - Stop INGRES/NET N - Modify Node Entry A - Modify Remote Authorization Entry E - Exit NETU> E Enter E and press Return to return to the prompt. > Checking the INGRES Installation and Configuration section provides information on how to check the and configuration of your INGRES database. Check your basic database configuration as follows: o Log in as diruser (su - diruser) o Enter the following command: isql servername::temip_tt If you can connect to the database, your configuration has probably completed successfully. If you receive the following message (using the "trouble_ticketing_fm" as an example): Cannot start application "trouble_ticketing_fm" then check the following: o During temip_setup, you may have chosen not to use the trouble_ticketing_fm or Archive application. If this is the case, rerun temip_setup and select the required applications. o The temip_start command was not run in the environment where the II_SYSTEM environment variable was (correctly) set. Refer to Section 1.5.3.1 for further details. If you receive the following message: You are not a valid ingres user then you must register the Director Username (diruser), default "temip", with INGRES. to Install TeMIP the ORACLE Database Section 1.6.1 and Section 1.6.2 describe how to configure the ORACLE database for TeMIP Alarm Handling Archive directive and TeMIP Trouble Ticketing access. It is assumed that the ORACLE database has been installed according to the relevant ORACLE installation procedure. For more information on the ORACLE utilities and procedures mentioned in these sections, refer to the appropriate ORACLE documentation: o Installation and Configuration Guide o Server Administrator's Guide o Server SQL Language Reference Manual o SQL*Plus User's Guide and Reference o SQL*Net Administrator's Guide. Otherwise, request assistance from your system/database manager. Preparing to Install TeMIP 1-27 ________________________ Notes ________________________ 1. A number of scripts are provided for management of the ORACLE database. These scripts are mandatory; you must use them. The scripts are located in /usr/kits/TNM310/examples. 2. If you want to install the ORACLE database in a DECsafe ASE environment, ensure that you install and configure DECsafe ASE before installation of the database, see Chapter 3. ______________________________________________________ Installation to Section 1.2.3 for the list of ORACLE parts and the version numbers that must be installed. At ORACLE time there are no particular requirements with to TeMIP. However, see the following notes. _______________________ Notes: _______________________ 1. Digital strongly recommends that you use the Install/Upgrade software only option. This is to avoid creation of a database at installation time. It is mandatory to use the scripts provided to create the TeMIP databases (this is explained in more detail in Section 1.6.2.2). 2. The language used nust be the same in ORACLE and in TeMIP, or errors will occur. ______________________________________________________ Configuration director user account name is known as the diruser diruser Account the environment variables in the TeMIP configuration as follows: Set ORACLE_HOME to the ORACLE installation location. Append ORACLE paths to your path. Set terminal option for ORACLE Utilities. further details of the TeMIP configuration file. see TeMIP Customization and Troubleshooting Guide. of ORACLE Environment Variable Settings ORACLE_HOME /usr/kits/oracle path = ($ORACLE_HOME/bin $path) ORACLE_TERM vt100 to Install TeMIP If you obtain the following message when running the TeMIP applications: ORACLE environment variable ORACLE_HOME is not set correctly. this means that the ORACLE_HOME variable has not been set in the TeMIP configuration file or the diruser account. ___________________ Important Note ___________________ If you encounter problems using the ORACLE database, always check that the ORACLE_HOME variable is correctly set in the TeMIP configuration file or the diruser account. ______________________________________________________ Creating the Database To be able to use the TeMIP Alarm Handling Archive directive, or TeMIP Trouble Ticketing, the ORACLE database must first be created under the diruser account. The procedure is as follows: 1. Login as root (su - root) o Add the diruser user name to the dba group in the file /etc/group 2. Login as oracle (su - oracle) o Enter the following command: chmod 777 $ORACLE_HOME/dbs 3. Login as diruser (su - diruser) o Check that the ORACLE_HOME parameter is correctly set in your environment using the following command: env | grep ORACLE 4. Use the script /usr/kits/TNM310/examples/temip_create_ ora to create a TeMIP database (for example, see temip_ tt below). This script contains mandatory requirements for the use of ORACLE with TeMIP, therefore it must be used. However, you can modify it if you think specific ORACLE options are relevant for your personal use. /usr/kits/TNM310/examples/temip_create_ora temip_tt 5. In the event of problems, use the script /usr/kits/TNM310/examples/temip_destroy_ora to delete the database and then recreate it using the script /usr/kits/TNM310/examples/temip_create_ora as shown below: /usr/kits/TNM310/examples/temip_destroy_ora temip_tt /usr/kits/TNM310/examples/temip_create_ora temip_tt 6. Check that the database has been successfully created and is ready to run using the following command: ps auwx | grep oracle Preparing to Install TeMIP 1-29 similar to the following is displayed: 22260 0.0 0.3 10.1M 624K ?? S Aug 23 0:09.18 ora_lgwr_temip_tt 22258 0.0 0.3 10.1M 512K ?? S Aug 23 0:08.21 ora_dbwr_temip_tt 22249 0.0 0.2 10.1M 448K ?? S Aug 23 0:01.58 ora_pmon_temip_tt 22261 0.0 2.3 10.3M 4.3M ?? I Aug 23 0:12.31 ora_smon_temip_tt ________________________ Note ________________________ This script creates a simple ORACLE database in the $ORACLE_HOME/dbs directory. For security and performance reasons, the database should be partitioned onto different disks, depending on your network requirements. If you want to change the database organization or use special ORACLE options, you can modify the script temip_create_ora. ______________________________________________________ Database Access only requires that the user diruser has access to the Each object in the database is owned by the user and only this user can access them. To preserve consistency, it is recommended that access to users is only granted when absolutely neccessary. Configuring SQL*Net must now configure SQL*Net as a server or as a client. Configuration gain access to TeMIP using SQL*Net, you must complete following steps: Login as root (su - root) o Copy the following files from /usr/kits/TNM310/examples. These files provide the correct configuration for the default databases (temip_tt, temip_ah and mcc_exp). It is not mandatory to have an ORACLE user on a client, as the database use is performed on the server. cp /usr/kits/TNM310/examples/tnsnames.ora.on_server /etc/tnsnames.ora cp /usr/kits/TNM310/examples/listener.ora.on_server /etc/listener.ora chmod 644 /etc/tnsnames.ora /etc/listener.ora o Insert the following line in the /etc/services file: listener 1521/tcp Login as oracle (su - oracle) o Modify the ORACLE_HOME fields in the /etc/listener.ora file. Set them to the correct values, which depend on the location of your installation. o Modify the HOST field in the /etc/listener.ora file. Replace madrid by your server name. o Depending on the names of your databases, add entries to the /etc/tnsnames.ora files. to Install TeMIP o Start the listener process using the following command: /usr/kits/TNM310/examples/temip_startnet_ora o If you encounter problems when starting the listener, check that you did not make any syntax errors when you modified the /etc/listener.ora file. Client Configuration If you want to access the created database from a client machine, connect to the client machine and do the following: 1. Login as root (su - root) o Copy the following files from /usr/kits/TNM310/examples. This file provides the correct configuration for the default databases (temip_tt, temip_ah and mcc_exp): cp /usr/kits/TNM310/examples/tnsnames.ora.on_client /etc/tnsnames.ora chown oracle /etc/tnsnames.ora chmod 644 /etc/tnsnames.ora 2. Modify the HOST field in the /etc/tnsnames.ora file. Replace madrid by your server name. 3. Depending on the names of your databases, add entries to the /etc/tnsnames.ora file. Note that in the TeMIP configuration file the ORACLE_HOME value must be set to the ORACLE_HOME value of the server. Checking the ORACLE Installation and Configuration This section provides information on how to check the installation and configuration of your ORACLE database. 1. Check your basic database configuration on the server as follows: o Log in as diruser (su - diruser) o Enter the following command: sqlplus /@temip_tt If you can connect to the database, your configuration has probably completed successfully. 2. If you receive the following message: ERROR: ORA-12203: TNS: unable to connect to destination then one of the following problems may have occured: o The ORACLE listener process has not been started. Use the temip_startnet_ora utility to start it up, refer to Section 1.6.2.4 for further details. or o The /etc/listener.ora file does not contain an entry dealing with the database involved. Refer to Section 1.6.2.4 and the /usr/kits/TNM310/examples/listener.ora.on_server file for further details. Preparing to Install TeMIP 1-31 If you receive the following message: ERROR: ORA-12154: TNS: could not resolve service name then one of the following problems may have occured: o The /etc/tnsnames.ora file does not contain an entry dealing with the database involved. Refer to Section 1.6.2.4 and to the /usr/kits/TNM310/examples/tnsnames.ora.on_server file for further details. or o Perhaps there is a syntax error in the /etc/tnsnames.ora file. If you receive the following message (using "trouble_ ticketing_fm" as an example): Cannot start application "trouble_ticketing_fm" then check the following: o During temip_setup, you may have chosen not to use the Trouble Ticketing FM or the Archive application. If this is the case, rerun temip_setup and select the required applications. o The temip_start command was not run in the environment where the ORACLE_HOME environment variable was (correctly) set. Refer to Section 1.6.2.1 for further details. Registration for TeMIP installing TeMIP, you must register your software and load the Product Authorization Key (PAK) using Digital UNIX License Management Facility (LMF). The is written proof of the license and contains the you need to register it. You cannot install unless you have first run the LMF procedure. information about all the available TeMIP licenses, to the TeMIP Planning Guide. your license and load the PAK as follows: Login to root account Invoke LMF by entering the following command: # lmf register The LMF utility displays a blank template for registering your license. Use vi or another editor to insert the information from the TeMIP PAK into the template. The LMF utility puts you into vi by default. Load the license by entering the following command: # lmf reset Check that the license is correctly loaded by entering the following command: # lmf list to Install TeMIP Using TEMIP-NMS-CS as an example, the following information is displayed: Product Status Users: Total Active TEMIP-NMS-CS active unlimited Digital UNIX active 32 1 When you have finished, exit from the editor. For further details of how to use the License Management Utility, refer to the Digital UNIX License Management Utility Reference Manual. Installation and Recovering from Errors To abort installation at any time press Ctrl/c. If you abort the installation, files created up to that point are not deleted. Use the following command to delete a partially installed subset: # setld -d If an error occurs during the installation, the system displays an error message. The following list gives possible reasons for errors that can occur during the installation: o The operating system version is incorrect. o The prerequisite software version is incorrect. o The amount of available disk space is insufficient. For a description of error messages generated by these conditions and a description of corrective actions, refer to the Digital UNIX Documentation on system messages, recovery procedures, and Digital UNIX software installation. Preparing to Install TeMIP 1-33 2 ____________________________________________________________ Upgrading TeMIP From a Previous Version This chapter explains how to check for subsets from a previous version of TeMIP and for programs that use TeMIP. It describes how to uninstall TeMIP subsets and, for each group of subsets, it states any data migration possibilities. _______________________ Notes: _______________________ 1. You do not need to read this chapter if you are doing a first-time TeMIP installation. 2. Specific advice on the migration of archived Alarms and Trouble Ticketing data (stored in ORACLE or INGRES) is given in the Release Notes. 3. Specific advice on migration involving TNS is given in the TeMIP Name Service Administration Guide. 4. All TeMIP Framework processes must be stopped before TeMIP is installed, and shared memory resources must be removed. To remove shared memory resources, use the temip_stop tool with flag -a (previously temip_reset) or the ipcrm command. Refer to the Digital UNIX System Administration documentation for further details. Also, the TNS clerk must be stopped using tns_clerk_stop before the TNS Clerk subset is installed. ______________________________________________________ The following topics are discussed in this chapter: o Checking For A Previous Version of TeMIP, Section 2.1 o Upgrading from TeMIP V3.0, Section 2.2 o Upgrading from TeMIP V3.0 With Visual TeMIP 1.0 Installed, Section 2.3 o Checking For Third-Party Programs or Management Modules, Section 2.4 o Deleting Subsets from Previous Visual TeMIP and TeMIP Versions, Section 2.5 o Deleting Third-Party or User Programs That Use TeMIP, Section 2.6 o Deleting a Previous Version of the TeMIP ASCII Management Toolkit, Section 2.7 Upgrading TeMIP From a Previous Version 2-1 For A Previous Version of TeMIP you begin a TeMIP installation, check to see if any from a previous version are present on your system: If your system is running Digital UNIX V3.2, check for: - TeMIP Framework V3.0 (subsets TFRxxxV300xxx) - TeMIP OSI AM V2.0 (subsets NOExxxV200) - TeMIP Framework ASCII AM V2.0 (subsets TATxxxV200) If your system is running Digital UNIX V3.0, check for: - TeMIP Framework V2.0A (subsets TFRxxxV20A) - TeMIP NMS V2.0A (subsets TNMxxxV20A) - TeMIP OSI AM V1.0A (subsets NOExxxV10A and CMACMV207) - TeMIP OSI AM V1.0C (subsets NOExxxV10C and CMACMV210) - TeMIP ASCII AM V2.0A (subsets TATxxxV20A) If your system is running Digital UNIX V2.0 or V2.1, check for: - TeMIP Framework V2.0 (subsets TFRxxxV200) - TeMIP NMS V2.0 (subsets TNMxxxV200) - TeMIP OSI AM V1.0 (subsets NOExxx100 or NOExxx104 and CMACMV203) - TeMIP ASCII AM V2.0 (subsets TATxxx200) ________________________ Note ________________________ If you want to upgrade the Digital UNIX operating system, you must delete all the TeMIP subsets first. ______________________________________________________ an appropriate grep command to see if any old subsets present, for example (for TFR subsets): setld -i | grep TFR any subset with the specified product code exists, grep a message listing the subsets, for example (one subset found): installed TeMIP Framework Basic Management System old subsets are found, you must delete them before the new version of TeMIP, see Section 2.5. from TeMIP V3.0 you install TeMIP on a system where TeMIP V3.0 was you must remove the following files to avoid behavior: files are no longer used but can cause problems if exist. TeMIP From a Previous Version from TeMIP V3.0 With Visual TeMIP 1.0 Installed If you install TeMIP on a system where TeMIP V3.0 was installed with Visual TeMIP Version 1.0, you must delete the Visual TeMIP 1.0 subsets before deleting the TeMIP V3.0 subsets. For Third-Party Programs or Management Modules If you have third-party software installed on top of TeMIP, or your own Access Module installed on the system, you must delete them before installing the new version of TeMIP. Such programs are not necessarily setld-compatible so must be deleted manually or according to the third-party deletion procedure as applicable. Subsets from Previous Visual TeMIP and TeMIP To delete subsets from previous Visual TeMIP and TeMIP versions from your system, log in as superuser and enter the setld command with the -d option, where is the name of the TeMIP subset you want to delete: # setld -d [...] The following example deletes the TeMIP V2.0A subsets: # setld -d TNMTTV20A TNMTOV20A TNMELV20A TNMRELV20A TNMBASEV20A Because there are software dependencies between TeMIP subsets and associated products, Digital recommends you to perform deletion in the following order: 1. Third-party or user software running on top of TeMIP 2. Visual TeMIP V1.0 subsets 3. TeMIP ASCII AM subsets 4. TeMIP OSI AM subsets 5. TeMIP NMS subsets (Fault and Trouble Management) 6. TeMIP Framework subsets If you do not follow this deletion order, the setld command will display error messages. The deletion of the TeMIP OSI AM and TeMIP NMS subsets may require some time because they update the TeMIP dictionary. ________________________ Note ________________________ When you delete old TeMIP subsets, the associated TeMIP data is not deleted. ______________________________________________________ Third-Party or User Programs That Use TeMIP The deletion procedure for third-party or user programs depends on how this software was installed. If software was installed using the setld procedure, it should also be possible to delete it using setld with the -d option. Upgrading TeMIP From a Previous Version 2-3 software cannot be deleted using an automatic procedure as setld -d, you must delete it manually, as follows: Find the executables (management modules or other programs). Find out if the software updated the TeMIP dictionary when it was installed. Find out if there is run-time or configuration data that must be deleted to allow the installation and operation of a new version of the software, compatible with TeMIP V3.1. (Some run-time or configuration data may need to be kept for migration to the new version of the software.) a Previous Version of the TeMIP ASCII Management you delete a previous version of the TeMIP ASCII Toolkit, there is no data requiring migration. you delete a Back End subset of a customized kit, you choose to migrate all the data (that is, the complete you delete a Front End subset of a customized kit, you choose to migrate your customized files, which are in the parser directory. _______________________ Warning _______________________ Take care that you do not lose any changes made to toolkit files when you install the new TeMIP ASCII Management Toolkit. ______________________________________________________ the diff command before installing the new TeMIP ASCII Toolkit to check whether customizable toolkit were changed. If changes were made, you will have to these changes again after installing the new version. TeMIP From a Previous Version 3 ____________________________________________________________ DECsafe Setup This chapter describes the setup of DECsafe for TeMIP and TNS, with INGRES or ORACLE. DECsafe provides high availability of data and software to client systems in a distributed configuration. The topics covered are: o DECsafe ASE Services, Section 3.1 o First Service: TNS Server with Database Server, Section 3.3 o Second Service: TeMIP with Database Client, Section 3.4 ________________________ Note ________________________ All strings shown for naming disk groups, logical volumes, domains, sets and so on are purely examples and do not represent constraints on TeMIP. ______________________________________________________ ASE Services To make an application such as TeMIP highly available, it must be configured in an ASE service. DECsafe provides support for three types of ASE service: o NFS service : to provide highly available access to exported disk data. o Disk service : to provide highly available access to a disk-based application (for example, database application). o User-defined service : to provide highly available access to an application that is not disk-based (for example, a login service). When a set of applications is configured in an ASE service, it runs on only one system (ASE member) at a time. When these applications are able to be automatically started and stopped using a set of commands performed in a specific order, the commands are included in a set of action scripts. If the ASE member running a service fails or if a network failure prevents the member from providing the service to clients, DECsafe automatically stops the service on the failing member if it is still active, and starts the service on another member: this is called service relocation. The service is unavailable only for a limited period of time (fail detection time plus ASE overhead time plus application startup time). DECsafe Setup 3-1 Service disk service is defined by: A service name Several disk mount points with read/write access. An Automatic Service Placement (ASP) policy that enables you to control which members are allowed to run a service: Three choices are proposed: o Balanced Service Distribution (the service will run on the member that is running the least number of services). o Favor Members (you can define a list of favor members, if all the members of the list are unavailable, the service will run on the member that is running the least number of services). o Restricted to Favored Members (same as Favor Members, but if all the members of the list are unavailable, ASE will not start the service). Associated with the ASP policy, ASE allows you to choose whether you want the service to be automatically relocated if a "better" member becomes available. User-defined action scripts (Start action, Stop action, Add action, Delete action) with argument and time-out. configure and manage your services, ASE provides you the ASE Manager utility (asemgr). In addition to the menu-driven mode, asemgr also has a command interface that you could use in a script to perform administrative tasks. a service has to be seen as running on the same (IP address) by its clients even after a relocation. this case it is possible to add an ifconfig alias from a host (free IP address) to the current host in the action script. This alias will be removed in the Stop script. the kit used is a TruCluster kit, you can choose to have alias defined automatically by the asemgr utility. In case, you must remove all ifconfig commands from the and Start action scripts. TeMIP and TNS in Disk Services a DECsafe ASE configuration, TeMIP is installed in a service. TeMIP is seen as a virtual node with several hosts (the ASE members). TNS is installed in a disk service. TNS is also seen as a virtual node several support hosts (the ASE members). Setup Two-Service Configuration The recommended configuration in an ASE environment involves two ASE services. The main idea is to take advantage of available hardware resources (processing power) to establish loadsharing. The first service (TNS + database server) runs on one system; the second service (TeMIP + database client) runs on another system. If the database used is Oracle, then the initial configuration is: o First machine : service "TNS SERVER + ORACLE SERVER" o Second machine: service "TeMIP + ORACLE CLIENT" If either of the two systems fails (in the DECsafe sense), its service is relocated to the other system, which then runs TeMIP + database client + TNS + database server. For example, if the database used is Oracle and the first machine fails, this gives: o Second machine only: service "TNS SERVER + ORACLE SERVER" and service "TeMIP + ORACLE CLIENT" Similar behavior occurs if the database used is Ingres and if the second machine fails. Constraints The following constraints apply: o TeMIP data and executables are stored in directories which must be mounted on the shared disks (disk mount points of the disk service): /usr/var/mcc /usr/var/kits /usr/mcc /usr/kits/TNM310 o TNS Server data and executables are stored in directories which must be mounted on the shared disks: /usr/var/tns/server /usr/tns/bin/server o The TNS Clerk subset must be installed on all members. o Digital strongly recommends that the home directories of the acloc and diruser accounts be on the shared disks. Create the following mount point: /usr/temip_homes and root the home directories of these accounts there. o If the TeMIP operators have their home directories on the local disk of each ASE member, then after a TeMIP relocation and a new login on the host now running the TeMIP service, they will not retrieve their private data stocked on the first member (for example, TeMIP Presentation Module customization). For that reason, another mount point is necessary on the shared disks: /usr/temip_op to be used as the parent directory of operators' home directories. DECsafe Setup 3-3 The database server data and executables are stored in a directory which must be mounted on the shared disks, either: /usr/kits/ingres_server or /usr/kits/oracle_server The database client data and executables are stored in a directory which must be mounted on the shared disks, either: /usr/kits/ingres_client or /usr/kits/oracle_client If you are also installing the OSI AM Access Module in your DECsafe configuration, you must create the following mount points on the shared disks before performing OSI AM specific setup operations: /usr/kits/NOE210 If you are also installing the ASCII AM Access Module in your DECsafe configuration, you must create the following mount points on the shared disks before performing ASCII AM specific setup operations: /usr/kits/TAT310 These mount points are used by the OSI AM software to store data and executables. The director must always be seen by its clients as the same host. The ifconfig alias will be used to make an alias between the virtual director host and the current host. The create alias and remove alias operations are in the Start action script and the Stop action script respectively. All the calls coming from the network to the director will be sent to the virtual host. The ifconfig alias only allows an IP alias; DECnet is not supported. ASE runs scripts with superuser rights, without inheriting the PATH and environment variables such as HOME. If you want to use PATH and environment variables, you must specify them in the action script. Hardware, and Logical Configurations uses a disk service based on AdvFS (Advanced File and LSM (Logical Storage Manager). AdvFS is used its log-based recovery features, the capability to filesets to grow freely within a domain, and its back-up feature. LSM is used for disk mirroring, and the ease-of-use it brings to managing volumes make up an AdvFS domain. 3-1 gives an example of a suitable hardware Setup BA 350: Module Storage Shelf Subsystem. DWZZA: SCSI signal converter (in order to extend the length of the SCSI differential bus by 25 meters). PMAZC: dual-port SCSI TURBOchannel controller, set up for FAST SCSI. RZ26: 1-gigabyte disk (for the first service - TNS and database server) RZ28: 2-gigabyte disk (for the second service - TeMIP and database client) Figure 3-2 shows the logical configuration that Digital recommends in a DECsafe environment. Constraints The following constraints apply: o On the ASE member where a service is to run, you must define an alias for it that is equal to the service name, using the ifconfig command. When you start a service on an ASE member, a link is made using the alias from the service name to the local hostname (member). This makes any relocation transparent to clients. The "Director Host" of the TeMIP server defined in "TEMIP_SERVICE" remains "TEMIP_SERVICE" regardless of the hostname (member) where TeMIP is running. Similarly, the "Director Host" of the TNS server defined in "TNS_ DB_SERVICE" remains "TNS_DB_SERVICE" regardless of the hostname (member) where TNS is running. o You must install the TNS clerk subset on all DECsafe members. Recommendation Digital recommends you to configure a TNS read-only server on the same LAN, to avoid possible TeMIP problems during any relocation of the first service (TNS_DB_SERVICE). Service: TNS + Database Server Initially, TNS and the dbserver are installed on the first system (A in Figure 3-2). Upon failure detection, TNS and the dbserver will automatically be relocated to the second system (B in Figure 3-2). Below is an ordered list of the tasks to be performed in order to install and configure the required environment. The tasks must be carried out on the same host, as described in the sections that follow. 1. LSM configuration 2. AdvFS configuration 3. First ASE configuration pass: Creating a TNS_DB_SERVICE disk service 4. ORACLE or INGRES server pre-installation 5. ORACLE or INGRES server installation 6. ORACLE only: Server post-installation DECsafe Setup 3-5 TNS server installation TNS server configuration Second ASE configuration pass: Adding Action Scripts configuration single disk group is created for the single ASE service will be configured. ________________________ Note ________________________ The numbers shown are only examples. ______________________________________________________ Disk Initialization up the local rootdg disk group on both systems: volsetup rz1b rz1b is an example of the name of a free local disk. the disk partitions on the disks: disklabel -rw rz19 rz26 disklabel -rw rz27 rz26 rz19 and rz27 are the disk names; rz26 is the disk the physical disks as LSM disks: voldisksetup -i rz19 voldisksetup -i rz27 Group a disk group (dg2) and add disks to it: voldg init dg2 disk1=rz19 voldg -g dg2 adddisk disk2=rz27 dg2 is an example of a disk group name. a logical volume (vol02 = 1 gigabyte): volassist -g dg2 make vol02 1000m 1 gigabyte is the size of rz19 and rz27 in this a mirror: volassist -g dg2 mirror vol02 Configuration AdvFS configuration involves defining an AdvFS domain a TeMIP domain) and creating filesets. a domain: mkfdmn /dev/vol/dg2/vol02 dom2 dom2 is the name of the domain in this example. Setup Filesets Create the following filesets: # mkfset dom2 set1 # mkfset dom2 set2 # mkfset dom2 set3 where set1 to set3 are the names of the sets in this example. Creating a TNS and Database Disk Service Use the asemgr utility to create the TNS and database disk service as follows: service type : disk service service name : TNS_DB_SERVICE (there must be an entry for "TNS_DB_SERVICE" in /etc/hosts) Assign an IP address to this service : Y (TruCluster only) AdvFS set name : dom2#set1 disk mount point : /usr/kits/_server (used by the database) access : read-write AdvFS set name : dom2#set2 disk mount point : /usr/tns/bin/server (TNS constraint on the name) access : read-write AdvFS set name : dom2#set3 disk mount point : /usr/var/tns/server (TNS constraint on the name) access : read-write ASP Policy : favor member automatic relocate : no where database_name is "ingres" or "oracle" as appropriate. ________________________ Notes ________________________ o The name "TNS_DB_SERVICE" for the service is only an example and not a requirement. o The service name "TNS_DB_SERVICE" will be the name of the alias (virtual hostname defined in /etc/hosts). o The action scripts will be added after TNS and DATABASE installation. o For DECsafe only (not TruCluster), to test the installation manually establish and remove the alias from the service name to the local host name, using the following commands: ifconfig alias ifconfig -alias In this example, the service name is "TNS_DB_ SERVICE". o After the action scripts have been added, the alias will be established and removed automatically. ______________________________________________________ DECsafe Setup 3-7 Server Pre-installation step is database-dependent. Server Pre-installation to note are: A user "oracle" must be created on both systems prior to the database installation. The user "oracle" must have the same uid on both systems, and its home directory set to: /usr/kits/oracle You must create a link from usr/kits/oracle to usr/kits/oracle_server to be able to log in as oracle. You must add "oracle" to the group: dba (database administrator). the /etc/services file on both systems by adding: 1521/tcp Server Pre-installation to note are: A user "ingres" must be created on both system prior to the database installation. The user "ingres" must have the same uid on both system, and its home directory set to: /usr/kits/ingres You must create a link from usr/kits/oracle to usr/kits/oracle_server to be able to log in as oracle. Server Installation step is database-dependent. Server Installation installation can only be done after ASE setup because appropriate disk mount points are configured on a fileset. ORACLE in /usr/kits/oracle_server/oracle, as in Section 1.6.1. All the ORACLE-related files files, databases) are located in sub-directories under /usr/kits/oracle_server/oracle during except for three files located in /etc and others located in /usr/bin. The handling of these six is the purpose of the ORACLE Server Post-installation as described in Section 3.3.6. and configure the files /etc/listener.ora and (corresponding ASE service is TNS_DB_SERVICE, is temip_tt): /etc/listener.ora: Setup LISTENER= (ADDRESS_LIST= (ADDRESS= (PROTOCOL=IPC) (KEY=temip_tt) ) (ADDRESS= (PROTOCOL=tcp) (HOST=TNS_DB_SERVICE) (PORT=1521) ) ) SID_LIST_LISTENER= (SID_LIST= (SID_DESC= (SID_NAME=temip_tt) (ORACLE_HOME=/usr/kits/oracle) ) ) TRACE_LEVEL_LISTENER=OFF TRACE_FILE_LISTENER=listener Edit /etc/tnsnames: temip_tt (DESCRIPTION= (ADDRESS_LIST= (ADDRESS= (PROTOCOL=IPC) (KEY=temip_tt) ) ) (CONNECT_DATA= (SID=temip_tt) ) ) INGRES Server Installation The installation can only be done after ASE setup because the appropriate disk mount points are configured on a shared fileset. Install INGRES in /usr/kits/ingres_server/ingres. All the INGRES-related files (log files, databases) are located in sub-directories created under /usr/kits/ingres_ server/ingres during installation. Run the configuration program netu, so that if the DB client application (TEMIP_SERVICE in this case) is relocated to the server machine, it can still continue to access the database. (TEMIP_SERVICE has to use the v- node name to refer to the node that hosts the database to make access possible.) Below is an example of netu setup: INGRES_ADMIN> netu INGRES/NET MANAGEMENT UTILITY -- -- Copyright (c) 1989, 1991 Ingres Corporation DECsafe Setup 3-9 one of the following: Q - Quiesce INGRES/NET S - Stop INGRES/NET N - Modify Node Entry A - Modify Remote Authorization Entry E - Exit N Modify Node Entry: Enter operation (add, merge, del, show, exit): add Enter Private or Global (P): G Enter the remote v_node name: server (this is an example) Enter the network software type(tcp_ip): Default value: tcp_ip Enter the remote node address: TNS_DB_SERVICE TNS_DB_SERVICE this must be an entry of /etc/hosts, this has to be the name of the ASE service supporting INGRES DBMS as well Enter the remote INGRES/NET Server Listen address(II): Default value: II row(s) added to the Server Registry Modify Node Entry: Enter operation (add, merge, del, show, exit): exit one of the following: Q - Quiesce INGRES/NET S - Stop INGRES/NET N - Modify Node Entry A - Modify Remote Authorization Entry E - Exit A Modify Remote Authorization Entry: Enter operation (add, del, show, exit): add Enter Private or Global (P): G Enter the remote v_node name: server Enter remote User Name: root Enter the remote Password: Repeat the remote Password: row(s) added to the Server Registry Modify Remote Authorization Entry: Enter operation (add, del, show, exit): exit one of the following: Q - Quiesce INGRES/NET S - Stop INGRES/NET N - Modify Node Entry A - Modify Remote Authorization Entry E - Exit exit Setup ORACLE Server Post-installation This step is for ORACLE only. The purpose of these tasks is to move the files created on the local disks (in /etc and /usr/bin) onto the shared disks in dedicated sub-directories. The action scripts will create/remove the appropriate logical links to make this move transparent for ORACLE. Create the etc_shared subdirectory on the shared disk: # mkdir /usr/kits/oracle_server/oracle/etc_shared Move files to the newly created directory: # mv /etc/listener.ora /usr/kits/oracle_server/oracle/etc_shared/listener.ora # mv /etc/oratab /usr/kits/oracle_server/oracle/etc_shared/oratab # mv /etc/tnsnames.ora /usr/kits/oracle_server/oracle/etc_shared/tnsnames.ora Create the usr_bin_shared subdirectory on the shared disk: # mkdir /usr/kits/oracle_server/oracle/usr_bin_shared Move files to the newly created directory: # mv /usr/bin/coraenv /usr/kits/oracle_server/oracle/usr_bin_shared/coraenv # mv /usr/bin/dbhome /usr/kits/oracle_server/oracle/usr_bin_shared/dbhome # mv /usr/bin/oraenv /usr/kits/oracle_server/oracle/usr_bin_shared/oraenv To be able to test the ORACLE installation, you must create the following soft links: # ln /usr/kits/oracle_server/oracle/etc_shared/listener.ora /etc/listener.ora # ln /usr/kits/oracle_server/oracle/etc_shared/oratab /etc/oratab # ln /usr/kits/oracle_server/oracle/etc_shared/tnsnames.ora /etc/tnsnames.ora # ln /usr/kits/oracle_server/oracle/usr_bin_shared/coraenv /usr/bin/coraenv # ln /usr/kits/oracle_server/oracle/usr_bin_shared/dbhome /usr/bin/dbhome # ln /usr/kits/oracle_server/oracle/usr_bin_shared/oraenv /usr/bin/oraenv TNS Server Installation TNS installation can only be done after ASE setup because TNS requires the appropriate disk mount points to be configured on a shared fileset. Install the TNS clerk and server subsets from the TeMIP kit, see also Chapter 4. TNS Server Configuration To configure your TNS server in a DECsafe environment, use the command tns_server_setup. Choose option 3, 4 or 5 according to the type of configuration you have planned. (Option 6, Configure dual-stack TNS server, cannot be used in a DECsafe environment.) Answer [YES] to the question: Do you want to set your TNS server in order to run in a DECsafe ASE configuration (Y/N) [N] : You are then prompted to enter an IP alias name for the DECsafe ASE service dedicated to the TNS server (TNS_ DB_SERVICE) and the names of the machines that are ASE members. If you need further information on how to use the tns_server_setup utility, see the chapter on the configuration tool in the TeMIP Name Service Administration Guide. DECsafe Setup 3-11 ________________________ Note ________________________ The host IP address shown in brackets in the final configuration display of tns_server_setup is the IP address of the alias TNS_DB_SERVICE, and not the address of a specific host. ______________________________________________________ Action Scripts the Start and Stop scripts have been added, they always executed every time the TeMIP service is or stopped. If a script encounters an error and complete, ASE will refuse the relocation or may an abnormal situation. This is the reason why it extremely important to make sure that a Start or Stop is correct before adding it to ASE. following are working guidelines that should be followed when working on ASE Start or Stop Test your scripts manually. They are Shell scripts and can be executed interactively. Create or update the Start and Stop script at the same time, to maintain consistent behavior of the service. This is necessary because ASE will stop and restart the service whenever a script is modified. Start and Stop scripts run under "system" without any environment variables. Therefore, you need to add the database and TeMIP environment variables to the scripts. Keep your own copy of your Start and Stop scripts. You cannot access the scripts that are privately stored by ASE. The Stop script should always "undo" what is done in the Start script. Make sure at the end of the Stop script that all the shared filesets are free and that no process is still using a shared fileset. Otherwise the relocation will fail because ASE will be unable to unmount the disk. add Start and Stop action scripts to the TNS disk use the ASE Manager utility (asemgr): = "TNS_DB_SERVICE" (service name) = 600 ________________________ Notes ________________________ o Start and Stop scripts run under "system" without any environment variables. Therefore, you need to add the database environment variables to the scripts. Setup o If you want to disable the database or TNS server from TNS_DB_SERVICE, you can comment out the corresponding section in the start/stop ASE scripts. ______________________________________________________ Start Script The steps in this script are as follows: o Define database environment variables. o Obtain the service name from the argument list when the script is activated by ASE. o For DECsafe only (not TruCluster), activate the Network login service: a broadcast message is sent over the network (to be used by Address Resolution Protocol, ARP) to update the correspondence table (ARP table). This in turn associates the IP address of the pseudo- host that is named as the service name (as specified in (/etc/hosts) with the Ethernet address of the physical machine to be accessed when trying to reach the pseudo- host. o Start the TNS server. o ORACLE only: Start the ORACLE server. o INGRES only: Start the INGRES server after shutting down the INGRES client if the directory /usr/kits/ingres_ client/ingres is visible. Examples of start scripts are available in /usr/kits/TNM310/examples as files: tns_oracle_server_start_ase.sh tns_ingres_server_start_ase.sh Stop Script The steps in this script are: o Define database environment variables. o Obtain the service name from the argument list. o Stop ORACLE or INGRES after releasing all pending sessions. o ORACLE: If the client installation directory is visible (/usr/kits/oracle_client/oracle), link to the client directory. INGRES: If the client installation directory is visible (/usr/kits/ingres_client/ingres), start the client. This step is useful when the INGRES server needs to be returned to its preferred host, so that the client application running on this node can access the server after it is relocated on the other system. o Shut down the TNS server o Stop all other processes on the disks used by the disk service (lsof tool). DECsafe Setup 3-13 For DECsafe only (not TruCluster), stop the Network login service: send an ARP message cancelling the previous association between the pseudo-hostname (corresponding to the service name) and the Ethernet address of the physical machine executing the Stop script. of stop scripts are available in as files: tns_oracle_server_stop_ase.sh tns_ingres_server_stop_ase.sh Service: TeMIP + Database Client TeMIP and the dbclient are installed on the system (B in Figure 3-2). Upon failure detection, and the dbclient will automatically be relocated to first system (A in Figure 3-2). is an ordered list of the tasks to be performed in to install and configure the required environment. tasks must be carried out on the same host, as in the sections that follow. LSM configuration AdvFS configuration First ASE configuration pass: Creating a TeMIP disk service ORACLE only: client configuration ORACLE: client post-configuration INGRES: client configuration TeMIP installation on second system Add user acloc on first system Add users corresponding to the TeMIP operators TeMIP setup Second ASE configuration pass: Adding Action Scripts configuration single disk group is created for the single ASE service will be configured. ________________________ Note ________________________ The numbers shown are only examples. ______________________________________________________ Disk Initialization up the local rootdg disk group on both systems: volsetup rz1b rz1b is an example of the name of a free local disk. Setup Create the disk partitions on the disks: # disklabel -rw rz18 rz28 # disklabel -rw rz26 rz28 where rz18 and rz26 are the disk names; rz28 is the disk type. Initialize the physical disks as LSM disks: # voldisksetup -i rz18 # voldisksetup -i rz26 Disk Group Create a disk group (dg1) and add disks to it: # voldg init dg1 disk1=rz18 # voldg -g dg1 adddisk disk2=rz26 where dg1 is an example of a disk group name. Create a logical volume (vol01 = 2 gigabytes): # volassist -g dg1 make vol01 2000m where 2 gigabytes is the size of rz18 and rz26 in this example. Create a mirror: # volassist -g dg1 mirror vol01 AdvFS Configuration The AdvFS configuration involves defining an AdvFS domain (not a TeMIP domain) and creating filesets. Domain Create a domain: # mkfdmn /dev/vol/dg1/vol01 dom1 where dom1 is the name of the domain in this example. Filesets Create the following filesets: # mkfset dom1 set1 # mkfset dom1 set2 # mkfset dom1 set3 # mkfset dom1 set4 # mkfset dom1 set5 # mkfset dom1 set6 # mkfset dom1 set7 where set1 to set7 are the names of the sets in this example. Creating a TeMIP Disk Service Use the asemgr utility to create the TeMIP disk service as follows: DECsafe Setup 3-15 service type : disk service service name : temip_service (there must be an entry for "TEMIP_SERVICE" in /etc/hosts) Assign an IP address to this service : Y (Trucluster only) AdvFS set name : dom1#set1 disk mount point : /usr/kits/_client (used by the database) access : read-write AdvFS set name : dom1#set2 disk mount point : /usr/var/mcc (TeMIP constraint on the name) access : read-write AdvFS set name : dom1#set3 disk mount point : /usr/var/kits (TeMIP constraint on the name) access : read-write AdvFS set name : dom1#set4 disk mount point : /usr/mcc (TeMIP constraint on the name) access : read-write AdvFS set name : dom1#set5 disk mount point : /usr/kits/TNM310 (TeMIP constraint on the name) access : read-write AdvFS set name : dom1#set6 disk mount point : /usr/temip_op (used as the parent directory of operators home directories) ADvFS set name: dom1#set7 disk mount point : /usr/temip_homes (used to root the home directories of acloc and diruser account) access : read-write ASP Policy : favor member automatic relocate : no database_name is "ingres" or "oracle" as appropriate. ________________________ Notes ________________________ o The name "TeMIP_SERVICE" for the service is only an example and not a requirement. o The service name "TeMIP_SERVICE" will be the name of the alias (virtual hostname defined in /etc/hosts). o The mount points /usr/temip_op and /usr/temip_homes are examples of parent directory names and not a requirement. o The action scripts will be added after TeMIP installation. o For DECsafe only (not TruCluster), to test the installation, manually establish and remove the alias from the service name to the local host name, using the following commands: ifconfig alias ifconfig -alias In this example, the service name is "TEMIP_ SERVICE". Setup o After the action scripts have been added, the alias will be established and removed automatically. ______________________________________________________ Database Client Configuration or Pre-Configuration This step is database-dependent. ORACLE Client Configuration Create a soft link from /usr/kits/oracle to /usr/kits/oracle_client to be able to log in as oracle. Create a /etc/tnsnames.ora to specify the host of the ORACLE server, for example: temip_tt= (DESCRIPTION= (ADDRESS_LIST= (ADDRESS= (PROTOCOL=tcp) (HOST=TNS_DB_SERVICE) (PORT=1521) ) ) (CONNECT_DATA= (SID=temip_tt) ) ) In this example, the Oracle server is TNS_DB_SERVICE, the first ASE service, and the database is temip_tt. Database Configuration or Post-Configuration Tasks This step is database-dependent. ORACLE Post-Configuration Tasks The purpose of these tasks is to move the file created on the local disks (in /etc) onto the shared disks in a dedicated sub-directory. The action scripts (see Section 3.4.10) will create/remove the appropriate logical link to make this move transparent for ORACLE. Create the etc_shared subdirectory on the shared disk: # mkdir /usr/kits/oracle_client/oracle/etc_shared Move the file to the newly created directory: # mv /etc/tnsnames.ora /usr/kits/oracle_client/oracle/etc_shared/tnsnames.ora You can create a soft link from /etc/tnsnames.ora to /usr/kits/oracle_client/oracle/etc_shared/tnsnames.ora to be able to test the client installation. INGRES Client Configuration Before configuration, the INGRES client installation must be performed on /usr/kits/ingres_client/ingres. In this example, all the ingres related files (log files, databases) are placed in sub-directories created under /usr/kits/ingres_client/ingres during installation. Create a soft link from usr/kits/ingres to usr/kits/ingres. The "netu" configuration program must be run on the client machine. DECsafe Setup 3-17 is an example of netu setup: netu MANAGEMENT UTILITY -- Copyright (c) 1989, 1991 Ingres Corporation one of the following: Q - Quiesce INGRES/NET S - Stop INGRES/NET N - Modify Node Entry A - Modify Remote Authorization Entry E - Exit N Node Entry: Enter operation (add, merge, del, show, exit): add Enter Private or Global (P): G Enter the remote v_node name: server (this is an example) Enter the network software type(tcp_ip): Default value: tcp_ip Enter the remote node address: TNS_DB_SERVICE (name of the ASE service supporting INGRES; must be an entry in /etc/hosts) Enter the remote INGRES/NET Server Listen address(II): Default value: II row(s) added to the Server Registry Node Entry: Enter operation (add, merge, del, show, exit): exit one of the following: Q - Quiesce INGRES/NET S - Stop INGRES/NET N - Modify Node Entry A - Modify Remote Authorization Entry E - Exit A Remote Authorization Entry: Enter operation (add, del, show, exit): add Enter Private or Global (P): G Enter the remote v_node name: server Enter remote User Name: root Enter the remote Password: Repeat the remote Password: row(s) added to the Server Registry Remote Authorization Entry: Enter operation (add, del, show, exit): exit one of the following: Q - Quiesce INGRES/NET S - Stop INGRES/NET N - Modify Node Entry A - Modify Remote Authorization Entry E - Exit exit Setup TeMIP Installation It is only necessary to install TeMIP on one of the two hosts, but the PAK must be installed on both hosts and the kernels rebuilt if necessary. Before installing TeMIP, check that the TeMIP disk service is on-line on the right system. If not, relocate it. Perform TeMIP installation including the TNS Clerk subset, as described in Chapter 4. TeMIP installation can only be done after ASE setup because TeMIP requires the appropriate disk mount points to be configured on a shared fileset. After TeMIP installation, all TeMIP images are located in TeMIP-specific directories and logical links are created in Digital UNIX standard directories to point to these images (for example /usr/bin for executables and /usr/shlib for shared libraries). These standard directories are on the private disks. In order to install TeMIP on a shared disk, the links need to be re-created on the private disks of each ASE member (except for the member where the kit was installed, as the links are set up during the installation) with the command temip_setup -s "TEMIP_SERVICE", where TEMIP_SERVICE is the service name, see Section 3.4.9. Add User acloc Add user acloc on the second system if it is not present. Use the same uid as on the first system. Add Users Add users corresponding to the TeMIP operators with the same uid on both systems (HOME = /usr/temip_op/user). You must relocate the TeMIP before creating TeMIP user accounts on the second host. TeMIP Setup Perform the following steps: 1. On the system where the TeMIP disk service is, define the alias (DECsafe only) and then run temip_setup with the -v option: ifconfig alias (DECsafe only; not TruCluster) temip_setup -v The parameter service_name is the name you gave when creating the TeMIP disk service (see Section 3.4.3). 2. On the same system, for DECsafe only (not TruCluster), remove the alias: ifconfig -alias 3. Relocate the TeMIP disk service on the system where the TNS disk service is (where TeMIP is not installed). 4. On the system where the TeMIP service now is, define the alias (DECsafe only) and then run temip_setup with the -s option: DECsafe Setup 3-19 ifconfig alias (DECsafe only; not TruCluster) /usr/mcc/mmtoolkit/bin/temip_setup -s This command adds the system to the director's Support Hosts list and makes the links from the Digital UNIX standard directories (located on the local disk) to the TeMIP images (located on the shared fileset). full details of the TeMIP setup procedure, see 5.2. Add Action Scripts TeMIP is correctly configured on the two DECsafe Digital recommends you first to relocate the TeMIP manually and start TeMIP manually to make sure that is operational. Do this operation several times a test. ________________________ Note ________________________ During this test phase, you must manually establish and remove the alias to the local host using the ifconfig command. ______________________________________________________ the test phase you can start adding the action See Section 3.3.9 for general guidelines. add Start and Stop action scripts to the TeMIP disk use the ASE Manager utility (asemgr): = "TEMIP_SERVICE" (service name) = 600 Setup ________________________ Note ________________________ Start and Stop scripts run under "system" without any environment variables. Therefore, you need to add the database and TeMIP environment variables to the scripts. ______________________________________________________ Start Script The steps in this script are as follows: o Define the database and TeMIP environment variables. o Obtain the service name from the argument list when the script is activated by ASE. o For DECsafe only (not TruCluster), activate the Network login service: a broadcast message is sent over the network (to be used by Address Resolution Protocol, ARP) to update the correspondence table (ARP table). This in turn associates the IP address of the pseudo- host that is named as the service name (as specified in /etc/hosts) with the Ethernet address of the physical machine to be accessed when trying to reach the pseudo- host. o Start TeMIP processes: There is a loop to wait for the TNS server to become available before starting TeMIP. If you want any application in your configuration to start at TeMIP start time (temip_start), set its automatic startup attribute to true. (For details of automatic startup, see the TeMIP Director Configuration and Management Guide. The same applies to any sinks that you use; enable them at this point so that they are active as soon as TeMIP is started. o ORACLE: Link to the ORACLE client file if there is no server, that is, if the server installation directory /usr/kits/oracle_server/oracle is not visible. INGRES: Start the INGRES client if there is no server, that is, if the server installation directory /usr/kits/ingres_server/ingres is not visible. Examples of start scripts are available in /usr/kits/TNM310/examples as files: temip_oracle_start_ase.sh temip_ingres_start_ase.sh Stop Script The steps in this script are: o Define database and TeMIP environment variables. o Obtain the service name from the argument list. o Stop TeMIP processes. o ORACLE: Delete the ORACLE client link if there is no server, that is, if the server installation directory /usr/kits/oracle_server/oracle is not visible. DECsafe Setup 3-21 INGRES: Shutdown the INGRES client if there is no server, that is, if the server installation directory /usr/kits/ingres_server/ingres is not visible. Stop all other processes on the disks used by the disk service (lsof tool). For DECsafe only (not TruCluster), stop the Network login service: send an ARP message cancelling the previous association between the pseudo-hostname (corresponding to the service name) and the Ethernet address of the physical machine executing the stop script. of stop scripts are available in as files: temip_oracle_stop_ase.sh temip_ingres_stop_ase.sh Setup 4 ____________________________________________________________ Installing TeMIP This chapter describes how to install the Release Notes and TeMIP software subsets directly onto your system, or on a RIS server. The RIS installation procedure assumes that you have created a server environment and are ready to install TeMIP. ________________________ Note ________________________ All TeMIP Framework processes must be stopped before TeMIP is installed, and shared memory resources must be removed. To remove shared memory resources, use the temip_stop tool with flag -a (previously temip_reset) or the ipcrm command. Refer to the Digital UNIX System Administration documentation for further details. Also, the TNS clerk must be stopped using tns_clerk_ stop before the TNS Clerk subset is installed. ______________________________________________________ The topics discussed in this chapter include: o The Installation Procedure, Section 4.1 o System Setup, Section 4.2 o The Installation Verification Procedure, Section 4.3 o Release Notes, Section 4.4 o Installation from a CD-ROM, Section 4.5 o Installation Including Visual TeMIP, Section 4.6 o RIS Installation, Section 4.7 Installation Procedure First log in as root on your Digital UNIX system. The exact commands you need to enter depend on the media you are installing from. In all cases you will have to enter the load command at the superuser prompt to install the TeMIP subsets. You can install TeMIP in the following ways: o From a system Directory o From a CD-ROM o From a RIS server Installing TeMIP 4-1 from a System Directory the following command from the directory in which the are located: setld -l . from a CD-ROM the kit and the BookReader documentation are on the Installing the Kit install the kit perform the following steps: Mount the CD-ROM driver using its device special name. To do this, enter the following command, replacing N with the actual logical unit number of the CD-ROM driver: # mount -r /dev/rzNc /mnt Enter the load command as follows: # setld -l /mnt/kit When installation is complete, if you do not want to install the online documentation, unmount the CD using the following command: # umount /mnt Installing the BookReader Documentation install the BookReader documentation perform the steps: Assuming the CD-ROM is mounted as described in the previous section, change to the Bookreader directory using the following command: cd /mnt/bookreader Copy the whole directory structure to /usr/lib/dxbook using the following command: cp -r * /usr/lib/dxbook This creates the following entries in the directory /usr/lib/dxbook: - A TeMIP bookshelf (library.decw_bookshelf) - A TFRV310 directory containing all the books. Add the following line in the Bookreader library file: SHELF\/usr/lib/dxbook/library.decw_bookshelf In order to allow access to the books from the Iconic Map PM, create a symbolic link in the help directory for each book to the corresponding installed book, by entering: TeMIP ln -s /usr/lib/dxbook/TFR310/tfr_spd_v310.decw_book /usr/mcc/help/en_US.ISO8859-1/TeMIPFrameworkV3SPD.decw_book ln -s /usr/lib/dxbook/TFR310/iconic_fcl_use_v310.decw_book /usr/mcc/help/en_US.ISO8859-1/TFRAndApplicationsUse.decw_book ln -s /usr/lib/dxbook/TFR310/tnm_ahug_pro_v310.decw_book /usr/mcc/help/en_US.ISO8859-1/TNMAlarmHandlingUse.decw_book ln -s /usr/lib/dxbook/TFR310/tnm_elug_pro_v310.decw_book /usr/mcc/help/en_US.ISO8859-1/TNMEventLoggingUse.decw_book ln -s /usr/lib/dxbook/TFR310/tnm_ttug_pro_v310.decw_book /usr/mcc/help/en_US.ISO8859-1/TNMTroubleTicketingUse.decw_book When installation is complete you must unmount the media using the following command: # umount /mnt Installing from a RIS Server To install the TeMIP subsets that reside in the /var/adm/ris distribution area of a remote system, specify the name of the RIS server system where the TeMIP subsets are located. For example, if you are loading TeMIP subsets from a RIS distribution area on the node bigsys, enter the following command: # setld -l bigsys: Setup System setup is not performed during installation. Refer to Section 5.2 for details of how to use the temip_setup tool to set up your system. Verification Procedure During the installation of each subset you select, you are asked if you want to run the IVP for this subset as part of the installation procedure or after installation is complete. An example of running the IVP during installation is shown in Section 4.6 (for the Visual TeMIP subset). If you choose to run the IVP after installation, a message is displayed that tells you how to do this. For further details refer to Section 5.6. When you run the IVP, a log of the output is created for both success and failure cases. The log file is placed in the directory: /var/kits/temip/ivp The name of the log file is: TFRIVP.log Notes The Release Notes contain the latest information about the product, plus any changes to the installation procedure that may have been made too late for inclusion in the TeMIP Installation Guide. Digital strongly recommends you to install and read the Release Notes before continuing with the TeMIP installation. You can read the Release Notes online or print out a hardcopy. Installing TeMIP 4-3 the Release Notes as follows: Mount the media on the distribution device. Start the installation procedure and choose the Release Notes option from the displayed menu. The following information is displayed: 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) TeMIP Framework Base System (level 1 rev D) 2) TeMIP Framework Developer Toolkit (level 1 rev D) 3) TeMIP Framework Presentation Modules (level 1 rev D) 4) TeMIP Framework Release Notes (level 1 rev D) 5) TeMIP Framework Server (level 1 rev D) 6) TeMIP Name Service Clerk (level 1 rev D) 7) TeMIP Name Service Server (level 1 rev D) 8) Visual TeMIP C++ Developer Toolkit (level 1 rev D) Or you may choose one of the following options: 9) ALL of the above 10) CANCEL selections and redisplay menus 11) EXIT without installing any subsets Enter your choices or press RETURN to redisplay menus. Choices (for example, 1 2 4-6): 4 Enter 4 and press Return. The installation procedure displays the subsets you have chosen and asks you to confirm your choice: You are installing the following optional subsets: TeMIP Framework Release Notes (level 1 rev D) Is this correct? (y/n): y If the information is correct, enter y and press Return. Otherwise enter n, press Return and re-enter your choice. The procedure displays: Checking file system space required to install selected subsets: File system space checked OK. Copyright (c) Digital Equipment Corporation, 1996. All Rights Reserved. Unpublished rights reserved under the copyright laws of the United States. 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 LEGEND 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. TeMIP TeMIP Framework Release Notes (level 1 rev D) Copying from . (disk) Verifying # 5. The Release Notes are installed in the directory: /usr/mcc/release.notes. The names of the files are TFR.release_notes and TFR.release_notes.ps regardless of the software version. from a CD-ROM This installation procedure installs the TeMIP files directly from the CD-ROM onto the system disk where you are performing the installation. It is assumed that you have already installed the Release Notes as described in Section 4.4. Install TeMIP as follows: 1. Run the installation procedure and choose the subset options you want to install: 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) TeMIP Framework Base System (level 1 rev D) 2) TeMIP Framework Developer Toolkit (level 1 rev D) 3) TeMIP Framework Presentation Modules (level 1 rev D) 4) TeMIP Framework Release Notes (level 1 rev D) 5) TeMIP Framework Server (level 1 rev D) 6) TeMIP Name Service Clerk (level 1 rev D) 7) TeMIP Name Service Server (level 1 rev D) 8) Visual TeMIP C++ Developer Toolkit (level 1 rev D) Or you may choose one of the following options: 9) ALL of the above 10) CANCEL selections and redisplay menus 11) EXIT without installing any subsets Enter your choices or press Return to redisplay menus. Choices: (for example, 1 2 4-6): 1-3 5 6 2. Enter the number or numbers of your choice, separated by spaces, and press Return. The installation procedure displays the subsets you have chosen and asks you to confirm your choice: You are installing the following optional subsets: TeMIP Framework Base System (level 1 rev D) TeMIP Framework Developer Toolkit (level 1 rev D) TeMIP Framework Presentation Modules (level 1 rev D) TeMIP Framework Server (level 1 rev D) TeMIP Name Service Clerk (level 1 rev D) Installing TeMIP 4-5 Is this correct? (y/n): y ________________________ Note ________________________ This example is typical of a TeMIP server machine in a DECsafe configuration. Installation for the TNS server machine in a DECsafe configuration would require the choice of subsets 6 and 7 only. ______________________________________________________ If the information is correct, enter y and press Return. Otherwise enter n, press Return and re-enter your choice. The procedure displays the following information and asks you if you want to continue: Checking file system space required to install selected subsets: File system space checked OK. ...Software Copyright declaration... Distributed Name Service Clerk for TeMIP (level 1 rev D) Copying from . (disk) Working....Wed Nov 6 11:44:57 MET DST 1996 Verifying Working....Wed Nov 6 11:47:02 MET DST 1996 ...Software Copyright declaration... TeMIP Framework will use the acloc user account with the following characteristics : acloc user id : 413 acloc group : users Note that TeMIP Framework users should belong to the users group in order to use the product. Refer to the TeMIP Installation Guide for more information. TeMIP Framework Base System (level 1 rev D) Copying from . (disk) Working....Wed Nov 6 11:50:39 MET DST 1996 Verifying ...Software Copyright declaration... ... TeMIP Framework Developer Toolkit (level 1 rev D) Copying from . (disk) Working....Wed Nov 6 11:51:45 MET DST 1996 Verifying Working....Wed Nov 6 11:54:01 MET DST 1996 ...Software Copyright declaration... ... TeMIP Framework Presentation Modules (level 1 rev D) Copying from . (disk) Working....Wed Nov 6 11:56:03 MET DST 1996 Verifying Working....Wed Nov 6 11:57:43 MET DST 1996 TeMIP ...Software Copyright declaration... ... TeMIP Framework Server (level 1 rev D) Copying from . (disk) Working....Wed Nov 6 11:58:45 MET DST 1996 Verifying Working....Wed Nov 6 11:59:51 MET DST 1996 Configuring "TeMIP Framework Base System (level 1 rev D)" (TFRBASEV310) WARNING: ======== To be able to run TeMIP Framework, please run /usr/bin/temip_setup tool after the whole installation. If you do not so, you will have problems at run-time, regardless the previous configuration setup during a previous TeMIP Framework installation. [ Press the RETURN key to continue ] # Refer to Section 5.2 for details of how to complete the setup and configuration of your system using the temip_ setup tool. of Visual TeMIP and IVP This installation procedure installs the Visual TeMIP files directly from the CD-ROM onto the system disk where you are performing the installation, and runs the IVP for this subset. It is assumed that you have already installed the Release Notes as described in Section 4.4. Install Visual TeMIP as follows: 1. Run the installation procedure and choose the subset option for Visual TeMIP: # setld -l . 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) Visual TeMIP C++ Developer Toolkit (level 1 rev D) Or you may choose one of the following options: 2) ALL of the above 3) CANCEL selections and redisplay menus 4) EXIT without installing any subsets Enter your choices or press RETURN to redisplay menus. Choices (for example, 1 2 4-6): 1 You are installing the following optional subsets: Visual TeMIP C++ Developer Toolkit (level 1 rev D) Is this correct? (y/n): y Installing TeMIP 4-7 Checking file system space required to install selected subsets: File system space checked OK. ...Software Copyright declaration... Visual TeMIP C++ Developper Toolkit will use the acloc user account with the following characteristics : acloc user id : 413 acloc group : users Note that Visual TeMIP C++ Developer Toolkit users should belong to the users group in order to use the product. Refer to the TeMIP Installation Guide for more information. Visual TeMIP C++ Developer Toolkit (level 1 rev D) Copying from . (disk) Working....Wed Nov 6 11:09:05 MET 1996 Verifying Configuring "Visual TeMIP C++ Developer Toolkit (level 1 rev D)" (TFRTFCV310) Would you like to run the TFRTFCV310 IVP? (y/n) [y] A TeMIP V310 license has been registered. If any errors appear, please reinstall the product. ************************************************************** Beginning Installation Verification Procedure for Visual TeMIP C++ Developer Toolkit 310 for D-UNIX V3.2 Installation Verification Procedure will take between 1 and 2 minutes ************************************************************** ...Software Copyright declaration... Compiling the Dev AM... There will be no more IVP questions ************************************************************** Installation Verification Procedure successfully completed. ************************************************************** Installation Verification Procedure for Visual TeMIP C++ Developer Toolkit 310 for D-UNIX V3.2 complete # Installation can install the TeMIP subsets in an environment by Remote Installation Services using the UNIX RIS Utility. The installation procedure in this section assumes you have installed the Notes first, see Section 4.4. TeMIP ________________________ Note ________________________ For installations from a RIS server, the subset numbers vary from server to server, depending on which products are available in the RIS server area and how many subsets each product has. ______________________________________________________ To install TeMIP, complete the following tasks: 1. Mount the media on the CD-ROM driver. 2. Run the RIS Utility by entering the following command: # ris 3. The RIS Utility Menu is displayed: *** 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 4. Enter i and press Return. The RIS Utility Software Installation Menu is displayed: 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 5. Enter 2 and press Return. If you select option 1, the RIS Utility creates the new area automatically. The Remote Installation Environment Menu is now displayed: You have chosen to add a product to an existing environment. Select the remote installation environment: 1) 'Same output' Enter your choice: 1 6. Enter 1 and press Return. You are now requested to enter the device special name: Enter the device special name or the path of the directory where the software is located, for example, /dev/rmt0h: /dev/rmt0h 7. Enter the device special name and press Return. A message appears asking you to confirm that the CD-ROM is mounted: Please make sure that your installation CD-ROM is mounted. Are you ready (y/n)? y Installing TeMIP 4-9 If the installation CD-ROM is mounted, enter y and press Return. The installation procedure displays the names of the TeMIP subsets and prompts you to choose the subsets you want to install (assuming that TeMIP is the only product available on the RIS server): 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) TeMIP Framework Base System (level 1 rev D) 2) TeMIP Framework Developer Toolkit (level 1 rev D) 3) TeMIP Framework Presentation Modules (level 1 rev D) 4) TeMIP Framework Release Notes (level 1 rev D) 5) TeMIP Framework Server (level 1 rev D) 6) TeMIP Name Service Clerk (level 1 rev D) 7) TeMIP Name Service Server (level 1 rev D) 8) Visual TeMIP C++ Developer Toolkit (level 1 rev D) Or you may choose one of the following options: 9) ALL of the above 10) CANCEL selections and redisplay menus 11) EXIT without installing any subsets Enter your choices or press Return to redisplay menus. Choices: (for example, 1 2 4-6): 3 Enter the number or numbers of your choice, separated by spaces, and press Return. The installation procedure displays the subsets you have chosen and asks you to confirm your choice: You are installing the following optional subsets: TeMIP Framework Presentation Modules (level 1 rev D) Is this correct? (y/n): y If the information is correct, enter y and press Return. Otherwise enter n, press Return and re-enter your choice. The procedure displays the following information and asks you if you want to continue: Checking file system space required to install selected subsets: File system space checked OK. ...Software Copyright declaration... TeMIP Framework Presentation Modules (level 1 rev D) Copying from . (disk) Working....Wed Apr 12 11:47:31 MET DST 1996 Working....Wed Apr 12 11:49:32 MET DST 1996 Verifying Working....Wed Apr 12 11:50:05 MET DST 1996 ...Software Copyright declaration... TeMIP Framework will use the acloc user account with the following characteristics : TeMIP acloc user id : 413 acloc group : users Note that TeMIP Framework users should belong to the users group in order to use the product. Refer to the TeMIP Installation Guide for more information. # Refer to Section 5.2 for details of how to complete the setup and configuration of your system using the temip_ setup tool. Installing TeMIP 4-11 5 ____________________________________________________________ After Installing TeMIP This chapter tells you how to set up your name space after installing the TNS subsets, how to set up TeMIP directors after installation, and how to run the IVP if you did not do so during installation. The topics discussed in this chapter include: o Setting Up Your Namespace, Section 5.1 o Setting Up Directors After TeMIP Installation, Section 5.2 o Stopping and Starting the TNS Clerk, Section 5.3 o Displaying the Result of temip_setup, Section 5.4 o Changing Setup and Configuration Parameters, Section 5.5 o Verifying Installations, Section 5.6 o Listing the TeMIP Files Installed, Section 5.7 Up Your Namespace Before you can finalize the setup of your TeMIP directors, you need to set up your namespace by configuring one or more TNS server systems. ________________________ Note ________________________ If a TNS server system is dedicated, meaning that it will not also be used as a TeMIP director, you do not do the TeMIP director setup described in Section 5.2. ______________________________________________________ If you are configuring a distributed system, you should first check TCP/IP reachability by pinging each system from all other systems. Also, if you decide to use the recommended time synchronization mechanism, Network Time Protocol (NTP), you must configure this before you configure the TNS server systems. Checking TCP/IP Reachability In a distributed TeMIP configuration, all systems must be able to communicate using the TCP/IP protocol, and configured to recognize the host names in the configuration. Use the following command on each system to ping all remote systems, to see if they are reachable: ping After Installing TeMIP 5-1 Network Time Protocol a distributed configuration, TNS requires network- time to ensure that TNS servers generate timestamps. Digital recommends Network Time (NTP) for this purpose. However, if you have running (and specifically DECdts (Distributed Service)) for other reasons, then you can use DECdts and skip this section. is part of the Digital UNIX OSFCLINET3xx subset. You configure NTP only after this subset is installed. configuring NTP on a particular system, you need to the following: Decide which of your systems will be local NTP servers and which will be NTP clients. Determine the system's time source: o For a local NTP server, the time source will be one of the following: - Several Internet NTP servers The Digital NTP documentation recommends you select a minimum of three systems from the list of Internet servers with which to synchronize the time on your local NTP servers. Internet NTP servers are typically highly available systems which have access to a very accurate time source. The systems that you select are called peers. To use an Internet NTP server you will first have to obtain permission from the contact person listed for the Internet server before specifying it as a peer for your local NTP servers. - A local reference clock A local reference clock is (ideally) a lightly loaded and highly available system on your network that keeps good time. See the ntp_manual_setup(7) man page for information on setting up a local reference clock. For an NTP client, the time source is the set of systems that you specify as local NTP servers. All you need to know to configure an NTP client is the IP host name of at least one local NTP server system and whether it is running the ntpd or xntpd daemon. Digital UNIX systems run xntpd. configure a system as an NTP client, run ntpsetup under as follows: Enter: ntpsetup Answer the questions, taking defaults when they are offered. Give the names of your local NTP server(s) when asked to enter the names of the NTP servers for your system. Installing TeMIP The following shows an example ntpsetup session: ajaxio> ntpsetup ******************************************************************** * * * Network Time Protocol (NTP) Setup * * * ******************************************************************** NTP has already been installed on this host. Would you like to change the current NTP configuration (y/n) [no default]? y Default answers are shown in square brackets ([]). To use a default answer, press RETURN. NTP Server Selection ******************** Enter the names of the NTP servers for this system. Press RETURN to terminate the list. Hostname of NTP server [no default]: poupix Looking up host poupix ...found. Is poupix running ntpd or xntpd (n/x) [x] ? Hostname of NTP server [no default]: The list of NTP servers is: poupix (xntpd) Enter "r" to REDO the servers list, "e" to EXIT the ntpsetup procedure, or "c" to CONTINUE [no default]: c IMPORTANT NOTE: If any of the NTP servers you specified are NOT IN YOUR SUBNET, you must run either routed or gated in order to access them. Please see the networking documentation to set up one of these services. [ Press RETURN to continue ] : Xntpd (the NTP daemon) Options ****************************** NOTE: The default answers are RECOMMENDED. Correct large time differences, -g ---------------------------------- If your system time differs from the network time by more than 1000 seconds while xntpd is running, the daemon will suspect that something is very wrong with your system which may be a security threat. It will then log a message to the syslog and exit to allow the system manager to resolve the problem. The -g option allows xntpd to correct large time differences without logging a message or exiting. It should be used by systems which are less sensitive to security threats. Would you like to use the -g option (y/n) [y]? After Installing TeMIP 5-3 Limit syslog messages, -l ------------------------- NTP uses syslog to record status messages once an hour plus several other informative messages. NTP also logs error messages and an initialization message. Would you like to limit NTP to log ONLY error messages and the initialization message (y/n) [n]? your system to run NTP...done. the NTP daemon (xntpd)... kernel timezone variable the current time and date with ntpdate Mar 28 11:29:37 MET 1996 Time Service started monitor NTP, type "/usr/bin/ntpq -p". NTPSETUP Complete ****** the Digital UNIX System and Network Administration, Configuration manual or the Digital UNIX man pages you need further information on NTP configuration. TNS Server Systems is possible to configure a TNS server to use a new or to re-use an existing TNS or DNS It is also possible to configure a TNS in one of two modes: TCP/IP only mode Dual-stack mode (TCP/IP and DECnet), possible only on a machine where DECnet/DNS V3.2B has been configured. dual-stack TNS server is able to service requests from V3.1 (TNS) and TeMIP V3.0 (DNS) systems, but can only an existing DNS clearinghouse. ________________________ Note ________________________ A system can have only one default namespace. If you set up a TNS server on a TeMIP director, remember that you will have to specify the same default namespace to temip_setup as you specify when you configure the TNS server. ______________________________________________________ configure a TNS server, use the tns_server_setup If you need further information on how to use utility, see the chapter on the configuration tool in TeMIP Name Service Administration Guide. Installing TeMIP Configuring TNS Clerk Systems The TNS clerk is configured as part of the TeMIP setup procedure (see Section 5.2 below), but some preliminary steps may be necessary. If you are upgrading a system that was a TeMIP director using a different namespace (DNS or MIR) before, you must deregister the director from the old namespace before you can register it in the new one. To do this, enter: temip_config -d Ensure that the namespace you are using has the following directories: o .temip (containing the TeMIP director information) o .MCC_SNMP_BackTranslation (in order to create SNMP entities) o .DNA_NodeSynonym (in order to create DNA5 entities) o .DNA_BackTranslation.%X49.%X.... (in order to create DNA4 entities) After deregistering a director, you can register it in TNS using temip_setup. You will need to know the name of your default namespace, which must be a namespace into which a TNS server that is reachable from the clerk has been configured (see Section 5.1.3). Up Directors After TeMIP Installation To complete the setup of a system for TeMIP you must use the temip_setup command. The temip_setup Command Use the temip_setup command to set up TeMIP directors after TeMIP installation. This program must be run immediately after product installation in order to set up the initial configuration. It can be rerun at any time subsequently to change the setup parameters. DECsafe Considerations If you have a DECsafe ASE environment, you will need to use the following two temip_setup options: o The -v option, on the system where TeMIP is installed, to specify that the system is to be secured by DECsafe. (You will also need to run temip_setup without the -v option to perform the full setup procedure.) o The -s option, on the second system, to set up the system that is to be a Support host. Examples of how to use these options are given in Chapter 3. Preserving User Definitions The temip_setup command may modify or overwrite some files containing user definitions. To preserve these definitions, save the files under another name before running temip_ setup and re-enter the definitions in the new files after setup. After Installing TeMIP 5-5 files involved are as follows (those marked with * are by temip_setup before being overwritten): Dictionary Configuration file (*) Dispatch tables file temip_setup program first checks that the following apply: The login must be as super-user. No TeMIP Framework processes can be running. The mandatory TeMIP Framework subsets must have been installed. any of these conditions are violated, temip_setup may Steps is composed of several steps. It is not possible run them independently. Each step may ask questions. on the answers given to some questions, later may be omitted, or may produce a different result. setup steps for TeMIP are as follows: PAKs and Ping step checks the PAKs and it checks that the local is able to ping itself. The setup procedure may if the superuser account is not set correctly with defined PATH. Note that /etc/hosts must contain: address fullname of host synonym unitel.vbo.dec.com unitel Configuration step asks if you wish to run one of the following applications: TeMIP Alarm Handling TeMIP Event Logging TeMIP Trouble Ticketing TeMIP Test Object you answer "no", the corresponding applications will not configured. If you answer "yes", they will be created, configuration details (especially the support database will be requested later. step will also ask you configuration questions about use of the DECnet product. step also asks if you wish to run the DECnet/OSI Module. If so, the setup procedure create an system entity as a child entity of the MCC entity the local director. Installing TeMIP If you answer "no", the corresponding application will not be configured and the tool will ask you if you want to use a dictionary without any DECnet/OSI definitions. A dictionary without any DECnet/OSI definitions is significantly reduced in size. If you answer "yes", the dna5_am application will be created and the installed dictionary will contain the full TeMIP Framework definitions. ________________________ Note ________________________ In a distributed configuration, all dictionaries must be compatible. If you do not plan to use the DECnet/OSI Access Module, you should answer "no" to this question for all your directors. If you plan to use the DECnet/OSI Access Module on any director, you should answer "yes" to this question for all your directors. ______________________________________________________ The TeMIP module Collection AM is able to use either TCP/IP or DECnet as transport protocol. This step asks you whether you wish to use DECnet or only TCP/IP as the protocol for this module. If you select DECnet, the Collection AM will be able to use either DECnet or TCP/IP; otherwise it will use only TCP/IP. For you to select DECnet, it must already be installed on the system, regardless of whether you actually use it or not. Selecting the Director User Account All management modules (AMs and FMs) will be implemented each as a single process irrespective of the number of different users requiring services from them. All the management module processes run under the same user-id, called the 'Director User ID'. This step asks you to choose the 'Director User ID', that is, the user account under which all management module processes will run. It must be an existing user account. This user account name will be used in a later step to change the ownership of some files and directories. ________________________ Note ________________________ In general you should avoid selecting root as this creates a situation where any user could create a domain rule with an alarm-fired procedure that executes the command "dxterm -ls" and thereby becomes root. ______________________________________________________ Ownership Change This is an automatic step that changes the ownership and protection of directories for the applications you selected in the Basic Configuration step, based on the Director User account you specified. During this step the ownership of files used by TeMIP Security is also modified. After Installing TeMIP 5-7 Installation is an automatic step that installs the working according to information given in Step 2: Basic is done using the following software links: ________________________ Note ________________________ The dictionary installed corresponds to the en_ US.ISO8859-1 (American English) language. Other languages require manual operations. ______________________________________________________ a Database step is only executed if the Server subset is According to choices made in previous steps, step asks you to choose the database system to be used support the following Function Modules: TeMIP Alarm Handling FM TeMIP Trouble Ticketing FM supported database systems are INGRES and ORACLE. ___________________ Important Note ___________________ When you select ORACLE or INGRES, you must remember to set the appropriate environment variables in the TeMIP configuration file, as described in Section 1.6.2.1 and Section 1.5.3.1 respectively. ______________________________________________________ a Time Format step asks you to choose the input and output time a Namespace step asks you to choose the namespace to be used by Framework. two possible namespaces are TNS and MIR. The result of choice is saved as variable MCC_DNS_SELECTION in the configuration file. ________________________ Note ________________________ If you have a distributed configuration, you must use TNS. The namespace must be fully configured and running before you can run temip_setup and select TNS as described in Section 5.1. ______________________________________________________ Installing TeMIP On all directors, regardless of the namespace selection, there is a local MIR database present. Furthermore, on a director operating in nondistributed mode with a MIR namespace, there is also a so-called TNS datastore, but this is local and not distributed, and is not under the control of TNS. A director operating in nondistributed mode with a TNS namespace makes use of a TNS datastore that is distributed (although TeMIP is not); the TNS datastore is located on a TNS server, and under the control of TNS. A director operating in distributed mode with a TNS namespace also makes use of a distributed TNS datastore (TeMIP is also distributed, independently); the TNS datastore is located on a TNS server under the control of TNS. Figure 5-1 illustrates the data stores seen by TeMIP directors. A distributed TNS datastore for a management module will always contain the Managing Director attribute and may contain other data, according to the design choice made for the module on splitting data between local and distributed storage. Configuration of MIR Journaling Function This step asks you how you want the MIR journaling function to be configured. Leave this function ON if you are in a production environment, so that journaling is operational. With the journaling function, you must run temip_backup to save the MIRs and clear the journal so that the disk does not become full. It will then be possible to recover the TeMIP MIRs up to and including the last transaction, using temip_backup (-recover option). Switch journaling OFF if you will not need to use temip_ backup for recovery purposes, so that less disk space is used. Without journaling, you can still use temip_backup but it will only be possible to restore the MIRs from the last backup in the event of failure; any more recent transactions will be lost. Your answer is saved in the TeMIP configuration file as environment variable MCC_MIR_WRAP_LOG. For more information on journaling and backup operations, see the chapter on TeMIP Backup in the TeMIP Director Configuration and Management Guide. Configuration File Creation This step creates the TeMIP configuration file, /var/mcc/config/.temip_config. This file is used to set the environment for TeMIP at run time. You can modify this file using any editor. If the configuration file already exists, it is saved and a warning message is displayed. Modifying Resource Files This is an automatic step that modifies TeMIP resource files. If the resource files already exist, they are saved and an information message is displayed. After Installing TeMIP 5-9 the Dispatch Tables File dispatch tables file containing entries for all TeMIP is delivered with the kit. step will either install the dispatch tables file with the kit or ask if you wish to overwrite the dispatch tables (in case of reinstallation). installation procedure installs a dispatch tables file a name having the extension ".delivered". If you have to overwrite the existing dispatch tables file, need to re-enroll any private management modules after execution. ________________________ Note ________________________ All dispatch tables files must be compatible in a distributed configuration. If you do not use the standard dispatch tables file provided with the kit, you should ensure that you have the same dispatch tables file on all your directors. Refer to TeMIP Director Configuration and Management Guide for a description of how to check the consistency of dispatch tables on different directors. For a description of how to ensure that the same dispatch tables are used, refer to the description of temip_ propagate in the TeMIP Utilities manual or in the manpages). ______________________________________________________ the Director step is used to select the name and configuration of director. default value of director name is .temip._ _______________________ Warning _______________________ If you change the name of your director, temip_setup will try to delete your local OSI system entity, see also Basic Configuration. ______________________________________________________ are four possible director modes depending on the subsets currently installed on the system: Non-Distributed Choose this mode if you do not have a distributed configuration. This option is valid if the BASE, PM and SERVER subsets are installed. Full Server Choose this mode if you have a distributed configuration and you wish to configure the system to be a Full Server-a director that can send calls to or receive calls from other directors, but that does not run any Presentation Modules. This option is valid if the BASE, PM and SERVER subsets are installed. AM/FM Server Installing TeMIP Choose this mode if you have a distributed configuration and you wish to configure the system to be an AM/FM Server-a director that can send calls to other directors and receive calls from other directors but does not run any Presentation Modules. This option is valid if at least the BASE and SERVER subsets are installed. o Client Choose this mode if you have a distributed configuration and you wish to configure the system to be a distribution client: a director that runs only Presentation Modules and can send calls to other directors, but cannot receive calls from other directors. This option is valid if at least the BASE and PM subsets are installed. The director is created according to your choice from the options above. In the case of a director that is already configured, this step displays the current director configuration (using temip_config -l) and then asks if you wish to keep the current configuration. If you answer "yes", the current director attribute values will be kept, and so will the director (MCC) and Remote Director entity definitions. If you answer "no", you will be asked to choose one of the modes above and the director entity and its Remote Director child entities will be re- created. Application Deletion This is an automatic step, which in the case of director reconfiguration, deletes all the applications created during a previous temip_setup execution. ________________________ Note ________________________ This step is always executed, even if you have chosen to keep your existing director configuration in the previous step. ______________________________________________________ Application Creation This is an automatic step that creates all the applications needed to support the chosen director configuration and the applications selected in the Basic Configuration step. ________________________ Note ________________________ This step is always executed, even if you have chosen to keep your existing director configuration in an earlier step. ______________________________________________________ After Installing TeMIP 5-11 System Selection on choices made in the Basic Configuration step, step may be run to ask the name of the local OSI entity. this case, the OSI system entity will be created and the OSI system entity is already defined, this step will be executed. TeMIP Setup the Visual TeMIP C++ Developer Toolkit (TFC) subset is this step asks you if you want /usr/bin/visual_ to be run. you answer "yes", the visual_temip_setup procedure the various examples provided with Visual TeMIP creates the corresponding applications: visual_temip_example_am : TeMIP Example AM visual_temip_example_fm : TeMIP Example FM vt_dev_am : TeMIP Development AM example of the temip_setup question and the output of is provided below: The Visual TeMIP C++ Developer Toolkit is installed on your system Do you want to run the Visual TeMIP setup : [y] Visual TeMIP Developers Toolkit Configuration full log is in: /var/mcc/install/visual_temip_setup.log.2 Do you want to re-create the links to files created at Visual TeMIP installation time ? Those soft links have been already created during setld install. This step enables you to re-create them in case of file system corruption. Re-create soft links (y/n)? [n]: Enrolling the Visual TeMIP examples Creating the Visual TeMIP example applications the Director step asks if you want TeMIP to be started at the end temip_setup execution. you answer "yes", you will be able to enter TeMIP directly after temip_setup execution. you answer "no", TeMIP will be stopped after temip_ execution. Refer to the descriptions of temip_start temip_stop in the TeMIP Utilities manual or in the Parameter Check is an automatic step that checks if your system are set to acceptable values for TeMIP. Installing TeMIP and Starting the TNS Clerk When the TNS clerk is configured during the TeMIP setup procedure, it is left running. Should you at a later stage want to stop the TNS clerk log in as root and enter: tns_clerk_stop To restart the TNS clerk, enter: tns_clerk_start For more details of TNS, see the TeMIP Name Service Administration Guide. the Result of temip_setup After running temip_setup, you can view a log of the procedure in the file /var/mcc/install/temip_setup.log. You can also enter temip_config -l to see the resulting parameters. These include those resulting from the choices you made and other default values assigned during setup. Setup and Configuration Parameters It is possible to change the setup parameters after the setup phase by rerunning temip_setup or using temip_config. The temip_config utility allows you to change other aspects of your director configuration as well. For details of temip_config, see the TeMIP Director Configuration and Management Guide. Installations If you did not run the IVP during installation, you can still run it before you use TeMIP for the first time, or whenever you detect problems. The IVP first checks that you have registered and loaded your license for TeMIP. You cannot run the IVP if you have not registered and loaded your license. o Start the IVP by entering the following command: # setld -v TFRSubset-NameVvuu where Subset-Name is: - BASE for the TeMIP Framework Base System subset - SERVER for the TeMIP Framework Server subset - PM for the TeMIP Framework Presentation Modules subset - TK for the TeMIP Framework Developer Toolkit subset - TFC for the Visual TeMIP C++ Developer Toolkit subset - TNSCLRK for the TeMIP Name Service Clerk - TNSSRV for the TeMIP Name Service Server ) - REL for the TeMIP Framework Release Notes subset and where v represents the major software version and uu represents the software version update. After Installing TeMIP 5-13 the TeMIP Files Installed list of the TeMIP files installed on a system is in the file: view the list, enter the following command at the UNIX prompt: /usr/.smdb./TFRvuu.inv Installing TeMIP A ____________________________________________________________ Pre-Installation Checklist This appendix summarizes the various operations required before installation of TeMIP. After you have completed each task, use the box at the left of the page to check it off the list. Before starting an installation, verify the following: < Check that the distribution kit is complete. < Ensure that you have a Digital Alpha system with the correct version of the Digital UNIX operating system installed and running. < Ensure that DECsafe is correctly installed and configured. < Back up the system disk. < Stop any TeMIP and TNS processes that are running. < Uninstall any previous version of TeMIP and Visual TeMIP. < Check your memory and swap file requirements. < Ensure that you have sufficient disk space. < Ensure that you set the required Digital UNIX parameters correctly. < Choose or create the diruser account. < Create the acloc account. < Load the distribution media. < Register the licenses for the product. < Read the online Release Notes. Pre-Installation Checklist A-1 from a CD-ROM starting installation from a CD-ROM, do the in addition to the installation checks: Note the device special name of the CD-ROM driver. from a RIS Server starting installation from a RIS server, do the Ensure that TeMIP is available on the RIS server. Determine the name of the RIS server. Ensure that your system is registered as a RIS client. Checklist B ____________________________________________________________ Log File of INGRES Installation This appendix gives an example log file of INGRES installation. ________________________ Note ________________________ Any specific installation will differ in detail from this example. ______________________________________________________ INGRES_ADMIN> iibuild -------------------------- INSTALLING INGRES --------------------------- Checking INGRES installation environment... INGRES installation is setup correctly ----------------------------------------------------------------------- | | | Your INGRES authorization string was supplied along with your | | distribution media. You must enter that value now to enable the | | new system. | | | ----------------------------------------------------------------------- |-------------------------------------------------------------------------- | You will now be prompted for your installation authorization string. | | This string should have accompanied your current release tape. If you | | didn't receive an authorization string or have lost it, contact Ingres | | sales administration. | | | |-------------------------------------------------------------------------- Please enter authorization string at the prompt below. -> xxxxxxxx xxxxxxxx xxxxxxxx xxxxxxxx The authorization string is now xxxxxxxx xxxxxxxx xxxxxxxx xxxxxxxx. ----------------------------------------------------------------------- | | | Ready to configure and startup release version: | | 6.4/05 (axp.osf/02) | | at location | | /usr/kits/ingres/ingres | | | ----------------------------------------------------------------------- Press RETURN to continue: Uncompressing distribution files (takes a few moments) ... All distribution files are already uncompressed. Log File of INGRES Installation B-1 INGRES merged server program, iimerge... 1 ingres ingres 5335456 Dec 22 1994 /usr/kits/ingres/ingres /bin/iimerge links to iimerge... linked to iimerge linked to iimerge linked to iimerge linked to iimerge linked to iimerge linked to iimerge linked to iimerge linked to iimerge linked to iimerge linked to iimerge to iimerge have been created. Executables successfully loaded. ownership and permissions on directories... directories are ok! FILE INSTALLATION COMPLETE ---------------------- the installation identifier, II_INSTALLATION... ----------------------------------------------------------------------- | To differentiate INGRES installations on a machine, INGRES uses a two | letter code chosen by you, called an installation id. Each INGRES | installation on a machine gets its own installation id. | | When choosing the installation id please keep in mind the following: | | 1. Installation id's should be unique across this machine. | EXCEPTION: If you are upgrading from release 5 to release 6, | then make your release 6 installation id the same as your | release 5 installation id. | 2. Installation id's are two letter codes. The first character | is a letter. The second can be a number or a letter. | | ----------------------------------------------------------------------- the installation identifier: II utility files: dayfile, startup, users... ----------------------------------------------------------------------- | There is no users file present. You can either have the installation | created with the default users (ingres, $ingres and root), or you | can use the users file from some other installation. | | You can always add and delete users with the "accessdb" command. | | If you want to use some other users file, enter its path, otherwise | just press RETURN, and INGRES will be set up with the default users. | | ----------------------------------------------------------------------- path of a users file, or press RETURN: File of INGRES Installation Installing new users file with default users... ----------------------------------------------------------------------- | | | The default editor used by the INGRES application tools is | | /bin/ed | | If you wish to use another editor enter the complete path where this | | editor can be found. Otherwise, press RETURN for the default editor. | | | ----------------------------------------------------------------------- Log File of INGRES Installation B-3 the full path name of the editor [/bin/ed]: /usr/ucb/vi CONFIGURING DATA FILE LOCATIONS -------------------- database location, II_DATABASE... ----------------------------------------------------------------------- | Please enter the value of II_DATABASE, the default base directory | at which to locate INGRES Databases. | | ----------------------------------------------------------------------- II_DATABASE location [/usr/kits/ingres]: ----------------------------------------------------------------------- | The location II_DATABASE has been configured successfully at location | | /usr/kits/ingres | | ----------------------------------------------------------------------- checkpoint location, II_CHECKPOINT... ----------------------------------------------------------------------- | Please enter the value of II_CHECKPOINT, the default base directory | at which to locate INGRES Checkpoints. | | ----------------------------------------------------------------------- II_CHECKPOINT location [/usr/kits/ingres]: ----------------------------------------------------------------------- ***WARNING*** | | The database location, II_DATABASE, and the II_CHECKPOINT location | are pointing to the same root directory | | /usr/kits/ingres | | It is strongly recommended that you put checkpoints, journals, | and dump files on a different physical device than the one used | for databases. If your database disk fails you should have access to | the checkpoint and journal files. Otherwise, a disk crash could | result in a total loss of data. | | ----------------------------------------------------------------------- you wish to change the II_CHECKPOINT location (y/n)? n ----------------------------------------------------------------------- | location II_CHECKPOINT has been configured successfully at | | | /usr/kits/ingres | | ----------------------------------------------------------------------- File of INGRES Installation Configuring journal location, II_JOURNAL... ----------------------------------------------------------------------- | | | Please enter the value of II_JOURNAL, the default base directory | | at which to locate INGRES Journals. | | | ----------------------------------------------------------------------- Log File of INGRES Installation B-5 II_JOURNAL location [/usr/kits/ingres]: ----------------------------------------------------------------------- ***WARNING*** | | The database location, II_DATABASE, and the II_JOURNAL location | are pointing to the same root directory | | /usr/kits/ingres | | It is strongly recommended that you put checkpoints, journals, | and dump files on a different physical device than the one used | for databases. If your database disk fails you should have access to | the checkpoint and journal files. Otherwise, a disk crash could | result in a total loss of data. | | ----------------------------------------------------------------------- you wish to change the II_JOURNAL location (y/n)? n ----------------------------------------------------------------------- | The location II_JOURNAL has been configured successfully at location | | /usr/kits/ingres | | ----------------------------------------------------------------------- dump location, II_DUMP... ----------------------------------------------------------------------- | Please enter the value of II_DUMP, the default base directory | at which to locate INGRES Dump files. | | ----------------------------------------------------------------------- II_DUMP location [/usr/kits/ingres]: ----------------------------------------------------------------------- ***WARNING*** | | The database location, II_DATABASE, and the II_DUMP location | are pointing to the same root directory | | /usr/kits/ingres | | It is strongly recommended that you put checkpoints, journals, | and dump files on a different physical device than the one used | for databases. If your database disk fails you should have access to | the checkpoint and journal files. Otherwise, a disk crash could | result in a total loss of data. | | ----------------------------------------------------------------------- you wish to change the II_DUMP location (y/n)? n File of INGRES Installation ----------------------------------------------------------------------- | | | The location II_DUMP has been configured successfully at location | | | | /usr/kits/ingres | | | ----------------------------------------------------------------------- -------------------- LOCATION CONFIGURATION COMPLETE ------------------- Log File of INGRES Installation B-7 ------------------------------------------------------------------------ The following section concerns the loading of the desired character | set for your installation. Once a character set has been defined for | the installation, you cannot modify it. If you are unsure of which | character set to use, exit now and refer to the I & O guide for | further details. | ------------------------------------------------------------------------ RETURN to continue: ------------------------------------------------------------------------ | *** WARNING *** | | Please indicate which of the following character sets you wish to | | use. The character set you choose will be used by all subsequently | | created databases. If you are unsure, do not continue. | ------------------------------------------------------------------------ CHARACTER SETS: ISO88591 | DECMULTI | HPROMAN8 | HEBREW | GREEK | ELOT437 | THAI | ARABIC | ISO88592 | ISO88595 | ISO88599 | you want to continue (y/n)? y desired Character Set [ISO88591]: ISO88591 ------------------------------------------------------------------------ **** WARNING ****** | You have currently chosen the ISO88591 character set. All your | databases will be created according to this character set, and cannot | be changed to use any other character set. If you are unsure of your | choice of character set, exit now, check your I & O guide and run | iibuild at a later time. | ----------------------------------------------------------------------- you sure (y/n)? y CHARACTER SET CHOSEN --------------------------- SERVER CONFIGURATION -------------------------- Transaction Log File... ----------------------------------------------------------------------- | Please enter the value of II_LOG_FILE, the default base directory | at which to locate INGRES Transaction Log File. | | ----------------------------------------------------------------------- II_LOG_FILE location [/usr/kits/ingres]: File of INGRES Installation ----------------------------------------------------------------------- | | | The location II_LOG_FILE has been configured successfully at location | | | | /usr/kits/ingres | | | ----------------------------------------------------------------------- Log File of INGRES Installation B-9 ----------------------------------------------------------------------- | Please enter the size of the transaction log file in Kbytes, or | press RETURN for the default value as shown. The minimum log file | size is 8192 Kbytes. | | ----------------------------------------------------------------------- log file size in Kbytes [8192]: INGRES log file with 8192 Kbytes (8388608 bytes)... Log file created successfully. INGRES locking and logging system ... ----------------------------------------------------------------------- | This procedure creates a customized parameter file | /usr/kits/ingres/ingres/files/rcp.par | which contains values to configure the INGRES locking/logging system. | | Please read the INGRES Installation and Operations Guide Chapter on | Configuration for an explanation of each parameter. | | ----------------------------------------------------------------------- RETURN to continue: ----------------------------------------------------------------------- | Please enter an estimated number of concurrent sessions in this | installation. This number will be used to calculate the logging | and locking parameters. | | When choosing this number please consider the following issues: | | 1. The minimum number of sessions allowed is 2 because there | are some INGRES utilities that require 2 sessions. In | addition, having at least 2 sessions allows you to monitor | the DBMS server while it is being used. | | 2. The maximum number of sessions you can have in an | installation depends on your system resources. Please refer | to the Installation and Operations Guide for information on | system requirements. | | 3. This number should represent the total number of concurrent | users in the installation, not the number of users per | server. | | 4. If you are planning on using INGRES/STAR you should calculate| two sessions for each user session. | | ----------------------------------------------------------------------- number of concurrent sessions in the installation: 24 appropriate parameters for 24 concurrent sessions... File of INGRES Installation Current logging parameters... Maximum number of open databases in logging system: 32 Maximum number of transactions in logging system: 86 Transfer block size for the log file: 8 Number of log buffers in shared memory: 4 Log-full-limit as a percentage of the log file: 95 Force-abort-limit as a percentage of the log file: 80 Percentage of the log file to be used for each consistency point: 25 Number of consistency points taken before invoking archiver: 1 Log File of INGRES Installation B-11 locking parameters... number of locks per transaction: 80 number of locks in the locking system: 5548 of lock lists in locking system: 86 of the locks hash table: 1109 of the resources hash table: 1109 you wish to change the configuration shown above (y/n)? n DBMS server... default DBMS server options are: 24 24 16 32 65536 4 you wish to change the default configuration (y/n)? n ----------------------------------------------------------------------- | These DBMS server options have been saved at: | | /usr/kits/ingres/ingres/files/rundbms.opt | | If you wish to change these options later on you can edit that file. | For more information on DBMS server options refer to the Installation | and Operations Guide. | | ----------------------------------------------------------------------- RETURN to continue: you wish to install INGRES/STAR (y/n)? n you wish to install INGRES/NET (y/n)? y INGRES/NET server(s)... ----------------------------------------------------------------------- | You will now be asked to specify the number of inbound and outbound | NET connections for each INGRES/NET server. | | Due to your system configuration the maximum number of total sessions | for an INGRES/NET server is 2041 sessions. You can choose any number | of inbound and outbound connections as long as the total number of | connections is not greater than 2041. | | Remember that a connected INGRES/NET session is required for each | INGRES/STAR server to remote DBMS server connection. | ----------------------------------------------------------------------- maximum number (>1) of inbound sessions for madrid.vbo.dec.com [1020]: 24 maximum number (>1) of outbound sessions for madrid.vbo.dec.com [1020]: 24 File of INGRES Installation Configuring INGRES/NET servers for the following protocols: TCP_IP DECnet Enter a TCP_IP Port ID (default II)> II_GCC_TCP_IP=II;export II_GCC_TCP_IP Enter a DECnet Port ID (default II)> II_GCC_DECNET=II;export II_GCC_DECNET Log File of INGRES Installation B-13 you want to start another INGRES/NET server (y/n)? n SERVER CONFIGURATION COMPLETE ---------------------- CHECKING SYSTEM RESOURCES ------------------------ Per-process Resource Limits Current Maximum File Size Limits: NONE NONE Resident Set Size Limits: 191496192 191496192 CPU Time Limits: NONE NONE Data Segment Size Limits: 134217728 1073741824 Stack Segment Size Limits: 2097152 33554432 File Descriptors: 4096 Memory Resources size of a shared memory segment should be: 4194304 of the INGRES system segment is: 8192 of the INGRES locking and logging memory segment is: 696320 of the DBMS server segment is: 225376 number of shared memory segments is: 128 of segments being used: 6 of segments required by INGRES: 3 memory resources are ok Resources number of semaphores: 4800 of semaphores per ID: 150 of semaphores being used: 65 of semaphores needed by INGRES: 35 number of semaphore sets: 32 of semaphore sets being used: 14 of semaphore sets needed by INGRES: 2 resources are ok. system is configured correctly to run INGRES. RESOURCE CHECKING COMPLETE ----------------------- 704512 bytes of shared memory... the Transaction Log File... STARTING INGRES SERVERS ------------------------- name server (iigcn) ... INGRES/NET server(s) (iigcc) ... server(s) 2390 now running recovery process (dmfrcp) ... archiver process (dmfacp) ... a DBMS server (iidbms) ... = 2395 INGRES SERVERS RUNNING ------------------------- File of INGRES Installation ----------------------------------------------------------------------- | | | If the system has C2-security, please remember to login as root and | | run "mkvalidpw". This will create the program "ingvalidpw", which is | | used by the dbms server to verify user passwords. | | | ----------------------------------------------------------------------- Press RETURN to continue: ----------------------------------------------------------------------- | The INGRES installation, configuration and startup process is now | | complete. If you want the installation to run at system boot time, | | add a script file to the /sbin/rc3.d. The script file should | | contain the following command. | | | | su ingres -c \ | | "/usr/kits/ingres/ingres/utility/iistartup \ | | /usr/kits/ingres" >/dev/console | | | | The command su ingres ensures that iistartup is executed by the | | ingres user. The name of the script file should begin with "S", | | followed by an integer, followed by "ingres"; for example, | | "S97ingres". To ensure that INGRES is started after the system is | | fully initialized, the integer in the filename should be higher than | | the integers in any existing scripts in the /sbin/rc3.d directory | | whose names begin with the letter "S". | | | | Before users can run INGRES, they must be authorized with "accessdb". | | See the INGRES Installation & Operations Guide for more information | | on this command. | ----------------------------------------------------------------------- Press RETURN to continue: ----------------------------------------------------------------------- | | | To access INGRES each user should do the following: | | | | For C shell users | | setenv II_SYSTEM /usr/kits/ingres | | set path = ($II_SYSTEM/ingres/{bin,utility} $path) | | | | For Bourne shell users: | | II_SYSTEM=/usr/kits/ingres | | PATH=/usr/kits/ingres/ingres/bin: \ | | /usr/kits/ingres/ingres/utility:$PATH | | export PATH | | | ----------------------------------------------------------------------- Press RETURN to continue: ----------------------------------------------------------------------- | | | A transcript of this session with 'iibuild' has been saved at | | | | /usr/kits/ingres/ingres/files/iibuild.log | | | ----------------------------------------------------------------------- Log File of INGRES Installation B-15 INGRES INSTALLATION COMPLETE ---------------------- File of INGRES Installation ________________________________________________________ Index Creating ______________________ an "acloc" user account, installation, 1-33 1-14 the INGRES database, 1-24 database, 1-24 the ORACLE database, 1-29 database, 1-30 account, 1-14 D______________________________ TeMIP, 5-1 to Database access (INGRES), 1-24 selection, access (ORACLE), 1-30 creation, creation (INGRES), 1-24 deletion, creation (ORACLE), 1-29 requirements, 1-4 ______________________ Database selection, 5-8 (BOM), 1-4 DECsafe documentation ORACLE or INGRES client, 4-2 3-14 ORACLE or INGRES server, 3-5 TeMIP server, 3-14______________________ TNS server, 3-5 DECSafe Toolkit, 1-3 acloc accounts, 1-14 1-2 DECsafe ASE 1-3 documentation, 1-20 installation, 1-20 1-6, setup, 1-21 4-7 using, 1-20 Device special name, 4-9 Dictionary installation, 5-8 checklist Directories, 1-6 the software subsets, Director mode, 5-10 Director name, 5-10 1-3 Director startup, 5-12 Director user account, 1-13 scripts (DECsafe ASE), configuration for INGRES, 1-23 ASE, 1-21 configuration for ORACLE, 1-23 1-28 checking the, Director user account selection, 5-7 1-25 diruser account, 1-13 1-28 Disk space, 1-6 checking the, Dispatch tables file copying, 5-10 1-30 Display resolution file creation, changing, 1-16 changing font paths, 1-17 checking font paths, 1-17 Index-1 resolution (cont'd) Installation (cont'd) system setting, types, RIS, 1-1 verification, 4-3, 5-13 Installation procedure, 4-1 the Installation Verification configuration, kit, 1-4 Procedure, 4-3, 5-13 Installing See Installation________________________ selection, 5-6 IVP See Installation Verification Procedure________________________ 5-14 K______________________________ problems, Kernel parameter settings, 1-8 1-18 Kit on CD-ROM, 4-2 ________________________ L__________________________requirements, 1-2 Library (online documentation) for Iconic Map, 4-2 , 4-2 License Management Facility, 1-32________________________ registration, 1-32 Map List of files installed, 5-14 4-2 LMF the configuration, See License Management Facility the installation, Logging on, 1-5 configuration, 3-14 M______________________________ MCC_DNS_SELECTION, 5-8 archive 1-21 MCC_NODE_IDP, 5-4 Menu TeMIP Trouble Ticketing access, 1-21 Remote Installation Environment, 4-9 director 1-23 RIS Utility, 4-9 RIS Utility Software 1-22 Installation, 4-9 configuration, MIR journaling function, 5-9 1-23 configuration, 1-25 N _______________________________ Namespace the, requirements, 1-4 for, Namespace selection, 5-8 user CD-ROM, 4-5 ASE, 1-20 O______________________________ 1-22 Online help links, 4-2 checking the, ORACLE checking the configuration, 1-28 1-31 checking checking the installation, 1-31 Notes, 4 client configuration, 3-14 4-1 configuration TeMIP, for archive directive, 4-8 1-27 from from a CD-ROM, 1-1 RIS server, 4-3 (cont'd) for TeMIP Trouble S______________________________ Ticketing access, 1-27 Screen of director resolution, 1-18 user account, 1-28 Setting kernel parameters 1-28 max-threads-per-user, 1-9 configuration, 3-5 maxuprc, 1-9 selection, 5-12 maxusers, 1-8 change, 5-7 semmni, 1-11 semmsl, 1-12 semopm, 1-12__________________________ semume, 1-12 shmmax, 1-10 Product shmmin, 1-10 to shmmni, 1-11 5-6 shmseg, 1-11 to vpagemax, 1-10 to Setup application creation, 5-11 4-1 application deletion, 5-11 Authorization basic configuration, 5-6 the, configuration file creation, 5-9 copying dispatch tables file,__________________________ 5-10 from dictionary installation, 5-8 1-33 director mode, 5-10 Notes MIR journaling, 5-9 4-5 modifying resource files, installed, 5-9 the, 4-3 namespace selection, 5-8 Installation of a new director, 5-5 Menu, of DECsafe ASE, 1-21 of the system, 4-3 DECwindows applications, 1-2 OSI system selection, 5-12 overwrites, 5-5 1-4 ownership change, 5-7 space, ping, 5-6 1-2 selecting a database, 5-8 1-4 selecting director user registration, account, 5-7 types, starting the director, 5-12 V1.1.3, system parameter check, 5-12 1-4 time format selection, 5-8 system, Sizing advice, 1-6 1-4 Software 1-2, 1 requirements, 1-2 backup, subsets, 4-5, 4-7 1-5 Software subsets choosing the, 4-10 1-17 System font sizes, backup, 1-6 display, setup, 4-3, 5-5 1-18 System directory, 4-2 System parameter check, 5-12 4-8 4-9 Menu, 4-9 Software Installation Menu, 4-9 Index-3 U________________________ _______________________________ Upgrades, 1-6 4-3 User account 1-6 director, 1-13 command, 5-5 Using selection, 5-6 DECsafe ASE, 1-20 directory, 4-2 selection, 5-8 V______________________________ 1-5 Visual TeMIP, 1-3, 1-5 deleting V1.0, 2-3 5-13 installing, 4-7 1-5 IVP, 4-8, 5-13 Management, setup procedure, 5-12 1-3 X _______________________________ 1-6, X-Server configuration 4-7 Ticketing selection, see Display resolution X-Server options, 1-19 X-Server planes, 1-20 of