TeMIP_for_DIGITAL_UNIX_________________________ Installation Guide Order Number: AA-Q9J2E-TE This guide describes how to install TeMIP on Digital Alpha systems running DIGITAL UNIX. Revision/Update Information: V3.1.1. This edition supersedes the V3.1.0 edition Operating System: DIGITAL UNIX Software Version: TeMIP V3.1 _______________________________________________________________ 1997 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 1997. rights reserved. Printed in Europe. AlphaStation, AlphaGeneration and the design mark, DECnet, DECsafe, DECwindows, UNIX, TeMIP and TeMIP Framework are trademarks of Equipment Corporation. SQL*Net and SQL*Plus are registered trademarks of corporation. is a registered trademark of Sun Microsystems, Inc. is a registered trademark of Sun Microsystems, Inc. is a registered trademark of Sun Microsystems, Inc. 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. UNIX V4.0 is a UNIX 95 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-3 Namespace Requirements ........................ 1-4 Distribution Kit .............................. 1-4 Subset Combination Requirements ............... 1-5 Time Required to Install ...................... 1-5 Logging On .................................... 1-6 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 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 Registration for TeMIP................... 1-21 Installation and Recovering from ........................................... 1-22 iii TeMIP From a Previous Version Checking for a Previous Version of TeMIP......... 2-1 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 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-5 AdvFS Configuration ........................... 3-6 Creating a TNS and Database Disk Service ...... 3-6 Database Server Pre-installation .............. 3-7 Database Server Installation .................. 3-7 ORACLE Server Post-installation ............... 3-8 TNS Server Installation ....................... 3-9 TNS Synchronization ........................... 3-9 TNS Server Configuration ...................... 3-9 Add Action Scripts ............................ 3-10 Second Service: TeMIP + Database Client.......... 3-12 LSM configuration ............................. 3-12 AdvFS Configuration ........................... 3-13 Creating a TeMIP Disk Service ................. 3-13 Database Client Configuration or Pre-Configuration.............................. 3-14 Database Configuration or Post-Configuration Tasks.......................................... 3-15 TeMIP Installation ............................ 3-15 Add User acloc ................................ 3-16 Add Users ..................................... 3-16 TeMIP Setup ................................... 3-16 Add Action Scripts ............................ 3-16 TeMIP The Installation Procedure....................... 4-1 Installing from a System Directory ............ 4-2 Installing from a CD-ROM ...................... 4-2 Installing from a RIS Server .................. 4-2 System Setup..................................... 4-2 Installation Verification Procedure.............. 4-2 Release Notes.................................... 4-3 Installation from a CD-ROM....................... 4-4 Installation of Visual TeMIP and IVP............. 4-6 RIS Installation................................. 4-8 The HTML User Documentation...................... 4-11 Installing the CGI Program on an HTTP Server..... 4-13 Installing TeMIP Using the ORACLE Database........................ 5-1 ORACLE Installation ........................... 5-2 ORACLE Configuration .......................... 5-2 Creating the Database ......................... 5-3 Database Access ............................... 5-4 Configuring SQL*Net ........................... 5-4 Checking the ORACLE Installation and Configuration.................................. 5-6 Setting Up Your Namespace........................ 5-7 Checking TCP/IP Reachability .................. 5-7 Configuring Network Time Protocol for TNS Synchronization................................ 5-7 Configuring TNS Server Systems ................ 5-10 Configuring TNS Clerk Systems ................. 5-10 Setting Up Directors After TeMIP Installation.... 5-11 The temip_setup Command ....................... 5-11 Setup Steps ................................... 5-12 Stopping and Starting the TNS Clerk.............. 5-18 Displaying the Result of temip_setup............. 5-19 Changing Setup and Configuration Parameters...... 5-19 Verifying Installations.......................... 5-19 The HTML Documentation IVP....................... 5-20 Listing the TeMIP Program Files Installed........ 5-20 Checklist Installation..................................... A-1 Installation from a CD-ROM....................... A-2 Installation from a RIS Server................... A-2 Single-Service Configuration Example Configuring the Single Service................... B-1 LSM configuration ............................. B-1 AdvFS Configuration ........................... B-2 Creating a TNS and TeMIP Disk Service ......... B-3 Add Users acloc and temip ..................... B-3 TNS Server and TeMIP Installation ............. B-4 TNS Server Configuration ...................... B-4 TeMIP Setup ................................... B-5 TNS Softlink Setup ............................ B-5 Add Action Scripts ............................ B-5 -1 Subset Combinations ........................... 1-5 -2 Disk Space Requirements (Subsets) ............. 1-6 -3 Disk Space Requirements (Installation Directories)................................... 1-7 -4 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 database 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 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 your database, the TNS namespace and your TeMIP directors. 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 of a DECsafe configuration with TNS and TeMIP in a single disk service. Conventions following conventions are used in this guide: __________________________________________________________ Meaning__________________________________________________________ The 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 is a list of the full documentation set. Note book titles preceded by + are not applicable to Sun installations. Manuals TeMIP Introduction (AA-Q9J1D-TE) TeMIP Graphical ASCII Toolkit Overview (AA-QZAUB-TE) Manuals + TeMIP for DIGITAL UNIX Installation Guide (AA-Q9J2E- TE) TeMIP for Sun Solaris Installation Guide (AA-R767A-TE) + TeMIP for DIGITAL UNIX OSI Management Toolkit Installation Guide (AA-QEMQF-TE) TeMIP for Sun Solaris OSI Management Toolkit Installation Guide (AA-R769A-TE) o + TeMIP for DIGITAL UNIX OSI Management Toolkit, OSI Access Module, Run-Time Kit Installation Guide (AA- QEMRF-TE) o TeMIP for Sun Solaris OSI Management Toolkit, OSI Access Module, Run-Time Kit Installation Guide (AA-R76AA-TE) o + TeMIP for DIGITAL UNIX Graphical ASCII Toolkit Installation Guide (AA-QZARB-TE) o TeMIP for Sun Solaris Graphical ASCII Toolkit Installation Guide (AA-R768A-TE) o + DECcmi for DIGITAL UNIX Installation and Configuration Guide (AA-QENTF-TE) o DECcmi for Sun Solaris Installation and Configuration Guide (AA-R76BA-TE) Management Manuals o TeMIP Utilities (AA-Q9JBD-TE) o TeMIP Planning Guide (AA-QXSPB-TE) o TeMIP Director Configuration and Management Guide (AA- QN8NC-TE) o TeMIP Name Service Administration Guide (AA-QXSQB-TE) o TeMIP Customization and Troubleshooting Guide (AA-QXSRB- TE) o TeMIP Framework Security Administration Guide (AA-QD9GD- TE) User Manuals o TeMIP Fault and Trouble Management Alarm Handling User's Guide (AA-Q9J4D-TE) o TeMIP Fault and Trouble Management Trouble Ticketing User's Guide (AA-Q9J8D-TE) o TeMIP Fault and Trouble Management Event Logging User's Guide (AA-Q9J6D-TE) o TeMIP Framework Iconic Map and FCL User's Guide (AA- Q9HMD-TE) o + TeMIP Framework DECnet Phase IV Access Module Use (AA-Q9HAD-TE) o + ++ TeMIP Framework DECnet-Plus Access Module Use (AA- Q9HBD-TE) o TeMIP Framework TCP/IP SNMP Access Module Use (AA-Q9HCD- TE) o TeMIP Framework Script Access Module Use (AA-Q9HDD-TE) ____________________ ++ Formerly known as DECnet/OSI ix TeMIP Framework Circuit Access Module Use (AA-Q9HHD-TE) TeMIP Framework Autoconfiguration Use (AA-Q9HLD-TE) TeMIP Framework Alarms and Notification Services Use (AA-Q9HED-TE) TeMIP Framework Security Operator's Guide (AA-QD9FD-TE) TeMIP OSI Management Toolkit GDMO Browser User's Guide (AA-QDYPF-TE) TeMIP OSI Management Toolkit GDMO Translator User's Guide (AA-QDYNF-TE) TeMIP OSI Management Toolkit, OSI Access Module, User's Guide (AA-QDYMF-TE) TeMIP Graphical ASCII Toolkit Customization Manual (AA- QZASB-TE) TeMIP Graphical ASCII Toolkit Configuration and Troubleshooting Guide (AA-QZATB-TE) DECcmi Operator's Guide (AA-QDYQF-TE) Not applicable to Sun Solaris installations. and Software Reference Manuals TeMIP Framework Management Module Programming (AA-Q9H8D- TE) TeMIP Framework Security Software Reference Manual (AA- QD9ED-TE) TeMIP Framework System Reference Manual Volume 1 (AA- Q9HGD-TE) TeMIP Framework System Reference Manual Volume 2 (AA- PD5LH-TE) Visual TeMIP Reference Guide (AA-QV89C-TE) Visual TeMIP Development Guide (AA-QV8BC-TE) TeMIP Fault and Trouble Management Reference Guide (AA- Q9J3D-TE) TeMIP Fault and Trouble Management OSI System AM, Module Reference Manual (AA-Q9JAD-TE) TeMIP Fault and Trouble Management Alarm Handling FM Module Reference Manual (AA-Q9J5D-TE) TeMIP Fault and Trouble Management Event Log FM Module Reference Manual (AA-Q9J7D-TE) TeMIP Fault and Trouble Management Trouble Ticketing FM Module Reference Manual (AA-Q9J9D-TE) TeMIP Fault and Trouble Management Event Filtering and Correlation FM Module Reference Manual (AA-QK7HC-TE) TeMIP Fault and Trouble Management Event Filtering and Correlation Software Reference Manual (AA-QMWKC-TE) Other Documents of Interest o + DECnet-Plus Planning Guide This describes how to migrate a network from DECnet Phase IV to DECnet-Plus, including configuration guidelines and task planning. o + DIGITAL UNIX Documentation Set This describes how to use and manage the DIGITAL UNIX operating system. o Sun Solaris Documentation Set This describes how to use and manage the Sun Solaris operating system. o + DIGITAL UNIX Guide to Remote Installation Services This describes how to install and maintain your remote installation environment, using the RIS utility. o ORACLE Installation and Configuration Guide This provides installation and configuration information for ORACLE databases and tools. o ORACLE Server Administrator's Guide This describes how to manage ORACLE databases. o ORACLE Server SQL Language Reference Manual This 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 This describes the SQL*Plus program, and gives a detailed description of each command. o ORACLE SQL*Net Administrator's Guide This 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 This 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 This describes how to set up and manage the systems and services in the DECsafe Available Server environment. + Not applicable to Sun Solaris installations. 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.1A. 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 License Registration for TeMIP, Section 1.5 o Aborting Installation and Recovering from Errors, Section 1.6 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 Sharing Software on a Local Area Network document. Preparing to Install TeMIP 1-1 Requirements installation requirements for TeMIP are described in 1.2.1 to Section 1.2.15 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 4.0B, including latest patches. Contact your DIGITAL representative for details. following subsets must be installed: OSFBASE410 Base System software OSFX11410 Basic X Environment software OSFCLINET41* Basic Networking Services 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 OSFCLINET41* subset includes Network Time Protocol for synchronization. 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 CXXBASE570 DEC C++ (cxx) for DIGITAL UNIX o CXXLIB570 DEC C++ static class libraries o CXXV4HDR570 DEC C++ header files for Digital UNIX V4.x o CXXMAN570 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-Plus Network If you want to manage your DECnet-Plus+ network using TeMIP Framework, the following additional subsets are required: o DNABASE4* DECnet-Plus Base Components o DNANETMAN4* DECnet-Plus 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-Plus. TeMIP Version 3.1A requires you to upgrade to DECnet-Plus version V3.2B, provided by the above DNA*4* subsets. See DECnet-Plus V3.2B Release Notes, Chapter 2 (Installation Notes) for some details you should be aware of before installing DECnet-Plus for DIGITAL UNIX software. ______________________________________________________ Database Requirements If you plan to use the Archive function of the TeMIP Alarm Handling or TeMIP Trouble Ticketing applications, you require the ORACLE database installed and running. ________________________ Note ________________________ You do not need to have the database installed or running during the installation of TeMIP. ______________________________________________________ ORACLE Database To use ORACLE with TeMIP, the mandatory ORACLE subsets are as follows: o ORACLE7 Server V7.3.3 o Associated SQL*Plus tool ____________________ + Formerly known as DECnet/OSI. Preparing to Install TeMIP 1-3 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. details of how to reuse an existing namespace with latest version of TNS, see the TeMIP Name Service Guide. 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 can be installed on a Digital Alpha system running UNIX from the Consolidated Distribution CD-ROM the label TeMIP Version 3.1A for DIGITAL UNIX. distribution kit contains the following TeMIP software TFRBASE TeMIP Framework Base System TFRSERVER TeMIP Framework Server TFRPM TeMIP Framework Presentation Modules TFRTK TeMIP Framework Developer Toolkit TFRTFC Visual TeMIP C++ Developer Toolkit TFRTNSCLR TeMIP Name Service Clerk TFRTNSSRV TeMIP Name Service Server TFRREL TeMIP Framework Release Notes TFRDOC TeMIP HTML User Documentation can install some subsets on a system and add others TFRTNSCLRK subset (TeMIP Name Service Clerk) is a subset for the use of the TeMIP Name Service TFRTNSSRV subset (TeMIP Name Service Server) is to configure a TNS server only, together with TFRTNSCLRK subset. ___________________ Important Note: ___________________ Read the Release Notes before starting the installation. They may contain additional information about software requirements and patches. ______________________________________________________ to Install TeMIP For information concerning license registration, refer to Section 1.5. For information concerning the various TeMIP licenses, refer to the section on licensing in the TeMIP Planning Guide. Subset Combination Requirements Table 1-1 shows the subsets required for each type of TeMIP director. The TeMIP director type is determined by the license option chosen for the director, see the TeMIP Planning Guide, and must be specified at the director configuration step of temip_setup during the post- installation setup phase, see Section 5.3.2. Table_1-1_Subset_Combinations______________________________ Director Type:_______TNSCLR__BASE___SERVER_PM_____TK/TFC_TNSSRV_____ Non- R R R R O O distributed Distributed R R R R O O Full Server Distributed R R R -[1] N/A[2] O[3] AM/FM Server Distributed R R -[4] R N/A[2] O[3] Client [1]The_PM_subset_is_definitely_not_installed_on_an_AM/FM___ Server. [2]Development (using the TK subset) cannot be performed on an AM/FM Server. [3]Any TeMIP director or another system can be configured as a TNS server. Usually several TeMIP directors are configured as TNS servers. [4]The SERVER subset is definitely not installed on a Client. ___________________________________________________________ where R = required; O = optional; N/A = not applicable 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. Preparing to Install TeMIP 1-5 On you start the installation, log onto a superuser on the system where you want to install TeMIP. You set the current working directory to the top level (or directory using the following command: cd / 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. Upgrading 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-2. 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-2 Disk Space Requirements (Subsets)__________________________________________________________ subset Disk Space (in KB)__________________________________________________________ TeMIP Framework Base 17160 TeMIP Framework 11040 TeMIP Framework 8350 Modules TeMIP Framework 3750 Toolkit Visual TeMIP C++ 6820 Toolkit TeMIP Name Service 1600 TeMIP Name Service 512 TeMIP Release Notes 10 TeMIP HTML User 20310 __________________________________________________________ 69552__________________________________________________________ to Install TeMIP Table 1-3 shows the disk space requirements in KB for installed TeMIP subsets in directories /usr/mcc, /usr/kits, /usr/tns, /var/mcc and /var/kits. This set of values represents the disk space required for direct installation. Table 1-3 Disk Space Requirements (Installation __________Directories)_____________________________________ subset___________/usr/mcc/usr/kit/usr/tns/var/mcc/var/kits_ TFRBASEV31A 39100 3100 0 12 0 TFRSERVERV31A 11300 13600 0 0 0 TFRPMV31A 7500 10900 0 0 0 TFRTKV31A 7600 1100 500 0 0 TFRTFCV31A 17800 0 0 0 0 TFRTNSCLRKV31A 7 0 3100 0 0 TFRTNSSRVV31A 3 0 550 0 0 TFRRELV31A 1 0 0 0 0 TFRDOCV31A 20310 0 0 0 0 ___________________________________________________________ Total_(KB)_______103630__28600___4450____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 /usr/var/tnscp 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. Preparing to Install TeMIP 1-7 TeMIP Name Service (TNS) data files are stored under /usr/var/tns directory. Setting the UNIX Kernel Parameters for TeMIP of the kernel parameter default values suit a standard configuration, however, specific configurations require modification of some of the values. For all the current value can be displayed using one of following commands; sysconfig -q proc, sysconfig -q vm 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.10 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: 16 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, your kernel as described in the DIGITAL UNIX System document. 1-4 shows the default and recommended values for the parameters as a quick reference. to Install TeMIP Table_1-4_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 16 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 temip account, because this is the default user_id. 2. If you are going to operate in DECsafe ASE, the temip account 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 temip account 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.9. 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 OSFXMIT4xx and OSFMANWOS4xx. The number "4xx" 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 or Sun Solaris 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 or Sun Solaris machine, you may need to add the 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 workstation, you will need to change the number of 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. Registration for TeMIP Before installing TeMIP, you must register your software license and load the Product Authorization Key (PAK) using the DIGITAL UNIX License Management Facility (LMF). The PAK is written proof of the license and contains the information you need to register it. You cannot install TeMIP unless you have first run the LMF procedure. ________________________ Note ________________________ You should only register ONE license. If you register more than one, TeMIP installation will fail. ______________________________________________________ For information about all the available TeMIP licenses, refer to the TeMIP Planning Guide. Register your license and load the PAK as follows: 1. Login to root account 2. Start LMF by entering the following command: # lmf register The LMF utility displays a blank template for registering your license. 3. 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. 4. Load the license by entering the following command: # lmf reset 5. Check that the license is correctly loaded by entering the following command: # lmf list Preparing to Install TeMIP 1-21 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. further details of how to use the License Management refer to the DIGITAL UNIX License Management Reference Manual. Installation and Recovering from Errors abort installation at any time press Ctrl/c. If you the installation, files created up to that point are deleted. the following command to delete a partially installed setld -d an error occurs during the installation, the system an error message. The following list gives reasons for errors that can occur during the The operating system version is incorrect. The prerequisite software version is incorrect. The amount of available disk space is insufficient. a description of error messages generated by these and a description of corrective actions, to the DIGITAL UNIX Documentation on system recovery procedures, and DIGITAL UNIX software to Install TeMIP 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 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 migration involving TNS is given in the TeMIP Name Service Administration Guide. 3. 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 (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 for a Previous Version of TeMIP Before you begin a TeMIP installation, check to see if any subsets from a previous version are present on your system: o If your system is running DIGITAL UNIX V3.2, you may have TeMIP V3.1 or V3.0 subsets. For V3.0, check for: - TeMIP Framework V3.0 (subsets TFRxxxV300xxx) - TeMIP OSI Toolkit V2.0 (subsets NOExxxV200) Upgrading TeMIP From a Previous Version 2-1 - TeMIP Framework ASCII AM V2.0 (subsets TATxxxV200) For V3.1, check for: - TeMIP Framework V3.1 (subsets TFRxxxV310xxx) - TeMIP OSI Toolkit V2.1 (subsets NOExxxV210) - TeMIP Graphical ASCII Toolkit V1.0 (subsets GATxxxV100) 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 Toolkit V1.0A (subsets NOExxxV10A and CMACMV207) - TeMIP OSI Toolkit 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 Toolkit 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. ______________________________________________________ appropriate commands to see if any old subsets are 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 or GAT 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 subset may require some time because it updates 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.) TeMIP From a Previous Version 3 ____________________________________________________________ DECsafe Setup This chapter describes the setup of DECsafe for TeMIP and TNS, with 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 Disk Service, Section 3.2 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 can use in a script to perform ASE tasks. 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 also installed disk service. TNS is also seen as a virtual node with support hosts (the ASE members). Configuration recommended configuration in an ASE environment two ASE services. The main idea is to take of available hardware resources (processing to establish loadsharing. The first service (TNS database server) runs on one system; the second service + database client) runs on another system. The ORACLE configuration is: First machine : service "TNS SERVER + ORACLE SERVER" Second machine: service "TeMIP + ORACLE CLIENT" either of the two systems fails (in the DECsafe sense), service is relocated to the other system, which then TeMIP + database client + TNS + database server. For if the first machine fails, this gives: Setup o Second machine only: service "TNS SERVER + ORACLE SERVER" and service "TeMIP + ORACLE CLIENT" One-Service Configuration An alternative, one-service configuration is described in Appendix B. Constraints on Two-Service Configuration 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 temip (Director user) 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. o The database server data and executables are stored in a directory which must be mounted on the shared disks as follows: /usr/kits/oracle_server o The database client data and executables are stored in a directory which must be mounted on the shared disks as follows: /usr/kits/oracle_client o 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 DECsafe Setup 3-3 If you are also installing the GAT in your DECsafe configuration, you must create the following mount points on the shared disks before performing GAT- specific setup operations: /usr/kits/GATV10 This mount point is used by the GAT software to store data and executables. 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 350: Module Storage Shelf Subsystem. SCSI signal converter (in order to extend the length the SCSI differential bus by 25 meters). dual-port SCSI TURBOchannel controller, set up for SCSI. 1-gigabyte disk (for the first service - TNS and server) 2-gigabyte disk (for the second service - TeMIP and client) 3-2 shows the logical configuration that Digital in a DECsafe environment. following constraints apply: 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. You must install the TNS clerk subset on all DECsafe members. recommends you to configure a TNS read-only server the same LAN, to avoid possible TeMIP problems during relocation of the first service (TNS_DB_SERVICE). Setup 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 server pre-installation 5. ORACLE server installation 6. ORACLE server post-installation 7. TNS server installation 8. TNS synchronization 9. TNS server configuration 10.Second ASE configuration pass: Adding Action Scripts LSM configuration A single disk group is created for the single ASE service that will be configured. ________________________ Note ________________________ The numbers shown are only examples. ______________________________________________________ Physical Disk Initialization Set up the local rootdg disk group on both systems: # volsetup rz1b where rz1b is an example of the name of a free local physical disk. Create the disk partitions on the disks: # disklabel -rw rz19 rz26 # disklabel -rw rz27 rz26 where rz19 and rz27 are the disk names; rz26 is the disk type. Initialize the physical disks as LSM disks: # voldisksetup -i rz19 # voldisksetup -i rz27 Disk Group Create a disk group (dg2) and add disks to it: # voldg init dg2 disk1=rz19 # voldg -g dg2 adddisk disk2=rz27 where dg2 is an example of a disk group name. DECsafe Setup 3-5 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. the following filesets: mkfset dom2 set1 mkfset dom2 set2 mkfset dom2 set3 set1 to set3 are the names of the sets in this a TNS and Database Disk Service the asemgr utility to create the TNS and database disk as follows: service type : disk service service name : TNS_DB_SERVICE (there must be an entry for "TNS_DB_SERVICE" in /etc/hosts on all members (or machines or systems)) Assign an IP address to this service : Y 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 : balanced automatic relocate : no database_name is "oracle". ________________________ 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). Setup o The action scripts will be added after TNS and DATABASE installation. ______________________________________________________ Database Server Pre-installation This step is database-dependent. ORACLE Server Pre-installation Points to note are: o A user "oracle" must be created on both systems prior to the database installation. o The user "oracle" must have the same uid on both systems (greater than 100), and its home directory set to: /usr/kits/oracle o If usr/kits/oracle does not exist, you must create a link from usr/kits/oracle to usr/kits/oracle_ server/oracle to be able to log in as oracle. o You must add "oracle" to the group: dba (database administrator). Update the /etc/services file on both systems by adding: listener 1521/tcp Database Server Installation This step is database-dependent. ORACLE Server Installation The installation can only be done after ASE setup because the appropriate disk mount points are configured on a shared fileset. Install ORACLE in /usr/kits/oracle_server/oracle, as described in Section 5.1.1. All the ORACLE-related files (log files, databases) are located in sub-directories created under /usr/kits/oracle_server/oracle during installation, except for four files located in /etc, namely listener.ora, sqlnet.ora, tnsnames.ora, oratab, and three others located in /usr/bin, namely oraenv, coraenv, dbhome. Edit and configure the files /etc/listener.ora, /etc/tnsnames.ora and /etc/oratab (corresponding ASE service is TNS_DB_SERVICE, database is temip_tt): Edit /etc/listener.ora: DECsafe Setup 3-7 (ADDRESS_LIST= (ADDRESS= (PROTOCOL=IPC) (KEY=temip_tt) ) (ADDRESS= (PROTOCOL=tcp) (HOST=TNS_DB_SERVICE) (PORT=1521) ) ) (SID_LIST= (SID_DESC= (SID_NAME=temip_tt) (ORACLE_HOME=/usr/kits/oracle) ) ) /etc/tnsnames.ora: (DESCRIPTION= (ADDRESS_LIST= (ADDRESS= (PROTOCOL=IPC) (KEY=temip_tt) ) ) (CONNECT_DATA= (SID=temip_tt) ) ) /etc/oratab: Server Post-installation purpose of these tasks is to move the files created the local disks (in /etc and /usr/bin) onto the shared in dedicated sub-directories. The action scripts will the appropriate logical links to make this transparent for ORACLE. the etc_shared subdirectory on the shared disk: mkdir /usr/kits/oracle_server/oracle/etc_shared 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 mv /etc/sqlnet.ora /usr/kits/oracle_server/oracle/etc_shared/sqlnet.ora the usr_bin_shared subdirectory on the shared disk: mkdir /usr/kits/oracle_server/oracle/usr_bin_shared Setup 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 -s /usr/kits/oracle_server/oracle/etc_shared/listener.ora /etc/listener.ora # ln -s /usr/kits/oracle_server/oracle/etc_shared/oratab /etc/oratab # ln -s /usr/kits/oracle_server/oracle/etc_shared/tnsnames.ora /etc/tnsnames.ora # ln -s /usr/kits/oracle_server/oracle/etc_shared/sqlnet.ora /etc/sqlnet.ora # ln -s /usr/kits/oracle_server/oracle/usr_bin_shared/coraenv /usr/bin/coraenv # ln -s /usr/kits/oracle_server/oracle/usr_bin_shared/dbhome /usr/bin/dbhome # ln -s /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 Synchronization Before you can use TNS (as required in the next task), you must synchronize all the ASE members. For details, see Section 5.2.2. TNS Server Configuration To configure your TNS server in a DECsafe environment, perform the following steps: 1. First use the command tns_server_setup. Choose option 3, 4 or 5 according to the type of configuration you have planned. 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. _______________________ Notes: _______________________ 1. 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. DECsafe Setup 3-9 2. Check that your database has been created as described in Section 5.1.3. ______________________________________________________ Relocate the TNS and DB Server disk service to the system where TeMIP is installed (where the TNS server is not installed). On the system where the TNS and DB Server disk service now is, enter the following command: cd / ; /usr/mcc/install/TFRTNSSRV.links This command makes the links from the DIGITAL UNIX standard directories (on the local disk) to the TNS images (on the shared fileset). These softlinks must be created once, during the installation phase, on each member where the TNS server can be relocated. _______________________ Warning _______________________ If you do not create these links you will be unable to run the TNS and DB Server disk service after relocation. ______________________________________________________ Add 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. Setup To add Start and Stop action scripts to the TNS disk service, use the ASE Manager utility (asemgr): arg = "TNS_DB_SERVICE" (service name) timeout = 600 ________________________ Note ________________________ 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 Start the ORACLE server. An example of the start script is available in /usr/kits/TNM310/examples as file: tns_oracle_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 after releasing all pending sessions. o If the ORACLE client installation directory is visible (/usr/kits/oracle_client/oracle), link to the client directory. o Shut down the TNS server o Stop all other processes on the disks used by the disk service (lsof tool). o 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. DECsafe Setup 3-11 example of the stop script is available in as file: tns_oracle_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 client configuration ORACLE client post-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. the disk partitions on the disks: disklabel -rw rz18 rz28 disklabel -rw rz26 rz28 rz18 and rz26 are the disk names; rz28 is the disk the physical disks as LSM disks: voldisksetup -i rz18 voldisksetup -i rz26 Setup 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-13 service type : disk service service name : temip_service (there must be an entry for "TEMIP_SERVICE" in /etc/hosts on all members (or machines or systems)) Assign an IP address to this service : Y 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 temip account) access : read-write ASP Policy : balanced automatic relocate : no database_name is "oracle". ________________________ 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. ______________________________________________________ Client Configuration or Pre-Configuration step is database-dependent. Setup ORACLE Client Configuration Create a soft link from /usr/kits/oracle to /usr/kits/oracle_client/oracle 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 soft links from /etc/tnsnames.ora to /usr/kits/oracle_client/oracle/etc_shared/tnsnames.ora and from /etc/sqlnet.ora to /usr/kits/oracle_client/oracle/etc_ shared/sqlnet.ora to be able to test the client installation. TeMIP Installation TeMIP installation can only be done after ASE setup because TeMIP requires the appropriate disk mount points to be configured on a shared fileset. 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. DECsafe Setup 3-15 User acloc user acloc on the second system if it is not present. the same uid as on the first system. Users users corresponding to the TeMIP operators with the uid on both systems (HOME = /usr/temip_op/user). You relocate the TeMIP before creating TeMIP user accounts the second host. Setup TeMIP installation, all TeMIP images are located in directories and logical links are created in UNIX standard directories to point to these images example /usr/bin for executables and /usr/shlib for libraries). These standard directories are on the disks. In order to install TeMIP on a shared disk, links need to be re-created on the private disks of ASE member (except for the member where the kit was as the links are set up during the installation) the command temip_setup -s "TEMIP_SERVICE", where is the service name. the following steps: On the system where the TeMIP disk service is, run temip_setup with the -v option: temip_setup -v The parameter service_name is the name you gave when creating the TeMIP disk service (see Section 3.4.3). Relocate the TeMIP disk service to the system where the TNS disk service is (where TeMIP is not installed). On the system where the TeMIP service now is, run temip_ setup with the -s option: /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.3. 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. the test phase you can start adding the action See Section 3.3.10 for general guidelines. Setup To add Start and Stop action scripts to the TeMIP disk service, use the ASE Manager utility (asemgr): arg = "TEMIP_SERVICE" (service name) timeout = 600 ________________________ 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 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. An example of the start script is available in /usr/kits/TNM310/examples as file: temip_oracle_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 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-17 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. example of the stop script is available in as file: temip_oracle_stop_ase.sh Setup 4 ____________________________________________________________ Installing TeMIP This chapter describes how to install the Release Notes, HTML documentation, 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 Section 4.1, The Installation Procedure o Section 4.2, System Setup o Section 4.3, Installation Verification Procedure o Section 4.4, Release Notes o Section 4.5, Installation from a CD-ROM o Section 4.6, Installation of Visual TeMIP and IVP o Section 4.7, RIS Installation o Section 4.8, The HTML User Documentation 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 online documentation are on the CD- To install the documentation, see Section 4.8. 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 from a RIS Server install the TeMIP subsets that reside in the distribution area of a remote system, specify name of the RIS server system where the TeMIP subsets located. For example, if you are loading TeMIP subsets a RIS distribution area on the node bigsys, enter the command: setld -l bigsys: Setup setup is not performed during installation. Refer to 5.3 for details of how to use the temip_setup tool set up your system. Verification Procedure the installation of each subset you select, you are if you want to run the IVP for this subset as part the installation procedure or after installation is An example of IVP execution during installation shown in Section 4.6 (for the Visual TeMIP subset). If choose to run the IVP after installation, a message displayed that tells you how to do this. For further refer to Section 5.7. you run the IVP, a log of the output is created for success and failure cases. The log file is placed in directory: name of the log file is: TeMIP 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 for DIGITAL UNIX 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. Install the Release Notes as follows: 1. Mount the media on the distribution device. 2. Start the installation procedure and choose the Release Notes option from the displayed menu. Note that the "revision" shown following the kit level may differ in the installation kit from the examples shown in this chapter. 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 5 rev C) 2) TeMIP Framework Developer Toolkit (level 5 rev C) 3) TeMIP Framework Presentation Modules (level 5 rev C) 4) TeMIP Framework Release Notes (level 5 rev C) 5) TeMIP Framework Server (level 5 rev C) 6) TeMIP Name Service Clerk (level 5 rev C) 7) TeMIP Name Service Server (level 5 rev C) 8) Visual TeMIP C++ Developer Toolkit (level 5 rev C) 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 3. 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 5 rev C) Is this correct? (y/n): y 4. 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. 1 subset(s) will be installed. Loading 1 of 1 subset(s).... Installing TeMIP 4-3 Copyright (c) Digital Equipment Corporation, 1997. 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 Framework Release Notes (level 5 rev C) Copying from . (disk) Verifying Loading 1 of 1 subset(s).... # The Release Notes are installed in the directory: /usr/mcc/release.notes. The names of the files are TFR.txt and TFR.ps regardless of the software version. from a CD-ROM installation procedure installs the TeMIP files from the CD-ROM onto the system disk where you performing the installation. It is assumed that you already installed the Release Notes as described in 4.4. TeMIP as follows: 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 5 rev C) 2) TeMIP Framework Developer Toolkit (level 5 rev C) 3) TeMIP Framework Presentation Modules (level 5 rev C) 4) TeMIP Framework Release Notes (level 5 rev C) 5) TeMIP Framework Server (level 5 rev C) 6) TeMIP Name Service Clerk (level 5 rev C) 7) TeMIP Name Service Server (level 5 rev C) 8) Visual TeMIP C++ Developer Toolkit (level 5 rev C) 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 TeMIP 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 5 rev C) TeMIP Framework Developer Toolkit (level 5 rev C) TeMIP Framework Presentation Modules (level 5 rev C) TeMIP Framework Server (level 5 rev C) TeMIP Name Service Clerk (level 5 rev C) 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. ______________________________________________________ 3. 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. 5 subset(s) will be installed. Loading 1 of 5 subset(s).... ...Software Copyright declaration... Distributed Name Service Clerk for TeMIP (level 5 rev C) Copying from . (disk) Working....Wed Nov 6 11:44:57 MET DST 1997 Verifying Working....Wed Nov 6 11:47:02 MET DST 1997 Loading 2 of 5 subset(s).... ...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 5 rev C) Copying from . (disk) Working....Wed Nov 6 11:50:39 MET DST 1997 Verifying Installing TeMIP 4-5 Loading 3 of 5 subset(s).... ...Software Copyright declaration... ... TeMIP Framework Developer Toolkit (level 5 rev C) Copying from . (disk) Working....Wed Nov 6 11:51:45 MET DST 1997 Verifying Working....Wed Nov 6 11:54:01 MET DST 1997 Loading 4 of 5 subset(s).... ...Software Copyright declaration... ... TeMIP Framework Presentation Modules (level 5 rev C) Copying from . (disk) Working....Wed Nov 6 11:56:03 MET DST 1997 Verifying Working....Wed Nov 6 11:57:43 MET DST 1997 Loading 5 of 5 subset(s).... ...Software Copyright declaration... ... TeMIP Framework Server (level 5 rev C) Copying from . (disk) Working....Wed Nov 6 11:58:45 MET DST 1997 Verifying Working....Wed Nov 6 11:59:51 MET DST 1997 Configuring "TeMIP Framework Base System (level 5 rev C)" (TFRBASEV31A) 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 ] # to Section 5.3 for details of how to complete the and configuration of your system using the temip_ tool. of Visual TeMIP and IVP installation procedure installs the Visual TeMIP files from the CD-ROM onto the system disk where you performing the installation, and runs the IVP for this It is assumed that you have already installed the Notes as described in Section 4.4. TeMIP 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) TeMIP Framework Base System (level 5 rev C) 2) TeMIP Framework Developer Toolkit (level 5 rev C) 3) TeMIP Framework Presentation Modules (level 5 rev C) 4) TeMIP Framework Release Notes (level 5 rev C) 5) TeMIP Framework Server (level 5 rev C) 6) TeMIP Name Service Clerk (level 5 rev C) 7) TeMIP Name Service Server (level 5 rev C) 8) Visual TeMIP C++ Developer Toolkit (level 5 rev C) 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): 8 You are installing the following optional subsets: Visual TeMIP C++ Developer Toolkit (level 5 rev C) Is this correct? (y/n): y Checking file system space required to install selected subsets: File system space checked OK. 1 subset(s) will be installed. Loading 1 of 1 subset(s).... ...Software Copyright declaration... Visual TeMIP C++ Developer Toolkit will use the acloc user account with the following characteristics : acloc user id : 420 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 5 rev C) Copying from . (disk) Working....Wed Nov 6 11:09:05 MET 1997 Verifying 1 of 1 subset(s) installed successfully. Configuring "Visual TeMIP C++ Developer Toolkit (level 5 rev C)" (TFRTFCV31A) Installing TeMIP 4-7 Would you like to run the TFRTFCV31A IVP? (y/n) [y] A TeMIP V31A license has been registered. If any errors appear, please reinstall the product. ************************************************************** Beginning Installation Verification Procedure for Visual TeMIP C++ Developer Toolkit 31A for D-UNIX V4.0 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 31A for Digital UNIX V4.0 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.5. ________________________ 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. ______________________________________________________ install TeMIP, complete the following tasks: Mount the media on the CD-ROM driver. Run the RIS Utility by entering the following command: # ris The RIS Utility Menu is displayed: *** RIS Utility Main Menu *** TeMIP 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 8. 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. Installing TeMIP 4-9 1) TeMIP Framework Base System (level 5 rev C) 2) TeMIP Framework Developer Toolkit (level 5 rev C) 3) TeMIP Framework Presentation Modules (level 5 rev C) 4) TeMIP Framework Release Notes (level 5 rev C) 5) TeMIP Framework Server (level 5 rev C) 6) TeMIP Name Service Clerk (level 5 rev C) 7) TeMIP Name Service Server (level 5 rev C) 8) Visual TeMIP C++ Developer Toolkit (level 5 rev C) 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 5 rev C) 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. 1 subset(s) will be installed. Loading 1 of 1 subset(s).... ...Software Copyright declaration... TeMIP Framework Presentation Modules (level 5 rev C) Copying from . (disk) Working....Wed Apr 12 11:47:31 MET DST 1997 Working....Wed Apr 12 11:49:32 MET DST 1997 Verifying Working....Wed Apr 12 11:50:05 MET DST 1997 ...Software Copyright declaration... TeMIP Framework will use the acloc user account with the following characteristics : acloc user id : 420 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 # Refer to Section 5.3 for details of how to complete the setup and configuration of your system using the temip_ setup tool. HTML User Documentation The user documentation contains complete information on how to use the product. It is supplied in HTML form as a separate kit. You can choose to install this kit on each system or on a single host running an HTTP Server if other systems will have access using an Intranet. At run time, the On-Line Help of the Iconic Map PM and the TeMIP PM use configuration files to map help topics to URLs. In accordance with the URL addressing scheme and depending on the location of the HTML documentation set, the document pointed to by a URL can be either local or remote. Local document example: file:/usr/mcc/temip_doc_html/imfcl/u-tfr_imfcl_prf0015.html Remote document example: http://anyhost.mycompany.com/temip_doc/imfcl/u-tfr_imfcl_prf0015.html Local keyword to URL mapping uses configuration files present on the local system (in the /usr/mcc/mcc_system directory). Remote mapping uses remote services in the form of a CGI program. The main drawback of local keyword mapping is that the configuration files must be duplicated on all systems where the PMs are installed. Remote keyword mapping allows the sharing of configuration files, which makes maintenance and updating easier. To install the user documentation, proceed as follows: 1. Mount the media on the distribution device. 2. Start the installation procedure and choose the User Documentation option from the displayed menu. The following information is displayed: Before installing the TeMIP Framework HTML Documentation, it is recommended (not mandatory) to install the "Netscape Navigator Gold V3.0 (or over)" (OSFNETSCAPE410) subset. the DISPLAY variable must also be defined. This will allow you to run the Installation Verification procedure (IVP). 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 HTML User Documentation (level 5 rev C) 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. Installing TeMIP 4-11 Choices (for example, 1 2 4-6): 1 Enter 1 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 HTML User Documentation (level 5 rev C) 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. 1 subset(s) will be installed. Loading 1 of 1 subset(s).... Copyright (c) Digital Equipment Corporation, 1997. 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 Framework HTML User Documentation (level 5 rev C) Copying from . (disk) Verifying 1 of 1 subset(s) installed successfully. The TeMIP HTML Documentation is now installed on your system : Location : /usr/mcc/temip_doc_html Starting file : start_here.html Configuring "TeMIP Framework HTML Documentation (level 1 rev C)" (TFRDOCV31A) # The HTML user documentation is installed in the directory: /usr/mcc/temip_doc_html. The root HTML file in this directory is start_here.html regardless of the software version. TeMIP the CGI Program on an HTTP Server If you are planning to make the HTML user documentation available on an Intranet, you will need to install the TeMIP Framework Presentation Modules subset containing the CGI program on your HTTP server, and then set up the CGI program to give access to other systems. Proceed as follows: 1. Log on to the system where the HTTP Server resides. 2. Install the TeMIP Framework Presentation Modules subset. (The procedure is as in Section 4.5 but you select number 3 only on the menu.) 3. Copy the TeMIP Help Server CGI program under the HTTP Server CGI programs directory. If necessary, see your HTTP Server documentation on how to install CGI programs. An example of the command is: cp help_server_Dux_v4.0 /usr/ns-home/FastTrack/cgi-bin/help_server 4. Copy the Help System configuration files to the same directory, for example: cp *.conf /usr/ns-home/FastTrack/cgi-bin 5. Edit the configuration files iconic_map_help.conf and temip_pm_help.conf to replace the [TEMIP_DOCUMENT_ROOT] tag with the location of the TeMIP HTML documentation set, for example /temip_doc if the documentation set is installed in the temip_doc subdirectory of the HTTP Server document root directory. 6. On all other systems running the Iconic Map PM and TeMIP PM, modify the PM resource files, mcc_resource.dat and temip_resource.dat, to redirect On-Line Help requests to the Help Server CGI program, for example: The syntax of the help_cgi_url resource must be: bin directory>/?config_file=?keyword=%s 7. To test the linking, start the iconic map on a system other than the HTTP server and choose "Overview" on the Help menu. Chapter 1 of the TeMIP Introduction manual should be displayed. Installing TeMIP 4-13 5 ____________________________________________________________ After Installing TeMIP This chapter tells you how to configure your database (if applicable), 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 Using the ORACLE Database, Section 5.1 o Setting Up Your Namespace, Section 5.2 o Setting Up Directors After TeMIP Installation, Section 5.3 o Stopping and Starting the TNS Clerk, Section 5.4 o Displaying the Result of temip_setup, Section 5.5 o Changing Setup and Configuration Parameters, Section 5.6 o Verifying Installations, Section 5.7 o Listing the TeMIP Files Installed, Section 5.9 the ORACLE Database Section 5.1.1 and Section 5.1.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. After Installing TeMIP 5-1 ________________________ 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 5.1.3). 2. The language used must be the same in ORACLE and in TeMIP, or errors will occur. ______________________________________________________ Configuration use ORACLE, you must configure the environment of the director user account, usually referred to as the account. Required to Run TeMIP run TeMIP, you will need to set the following: ORACLE_HOME to the ORACLE installation location. The ORACLE SQL*Net administration directory to /etc. the TeMIP configuration file (/var/mcc/config/.temip_ ) to contain the following lines: Installing TeMIP . . . ORACLE_HOME=/usr/kits/oracle . . . TNS_ADMIN=/etc . . . For further details of the TeMIP configuration file, see the TeMIP Customization and Troubleshooting Guide. ___________________ Important Note ___________________ If you encounter problems using the ORACLE database, always check that the ORACLE_HOME parameter is correctly set in the TeMIP configuration file. ______________________________________________________ Configuration Required to Run Tools To run tools such as SQL*Net, you will need the same ORACLE configuration parameters as for running TeMIP plus the terminal option, and a path for convenience. You must set the configuration parameters at the DIGITAL UNIX prompt, as follows: setenv ORACLE_HOME /usr/kits/oracle setenv ORACLE_TERM vt100 setenv TNS_ADMIN /etc To append the ORACLE path to your path variable, enter the following at the DIGITAL UNIX prompt): set path = ($ORACLE_HOME/bin $path) ___________________ Important Note ___________________ If you encounter problems using the ORACLE database, always check that the ORACLE_HOME environment variable is correctly set in the temip 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 temip account. The procedure is as follows: 1. Login as root (su - root) o Add the temip 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 After Installing TeMIP 5-3 Login as temip (Director user account) o Check that the ORACLE_HOME parameter is correctly set in your environment using the following command: env | grep ORACLE 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 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 Check that the database has been successfully created and is ready to run using the following command: ps auwx | grep oracle 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. ______________________________________________________ Access only requires that the user temip 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. SQL*Net must now configure SQL*Net as a server or as a client. Installing TeMIP Server Configuration To gain access to TeMIP using SQL*Net, you must complete the following steps: 1. 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) and for SQL*Net. 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/listener.ora.on_server /etc/listener.ora cp /usr/kits/TNM310/examples/tnsnames.ora.on_server /etc/tnsnames.ora cp /usr/kits/TNM310/examples/sqlnet.ora /etc/sqlnet.ora cp /usr/kits/TNM310/examples/oratab /etc/oratab chmod 644 /etc/listener.ora /etc/tnsnames.ora /etc/sqlnet.ora /etc/oratab o Insert the following line in the /etc/services file: listener 1521/tcp 2. 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. 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. They provide the correct configuration for the default databases (temip_tt, temip_ah and mcc_exp) and for SQL*Net: cp /usr/kits/TNM310/examples/tnsnames.ora.on_client /etc/tnsnames.ora cp /usr/kits/TNM310/examples/sqlnet.ora.on_client /etc/sqlnet.ora chmod 777 /etc/tnsnames.ora /etc/sqlnet.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. After Installing TeMIP 5-5 that in the TeMIP configuration file the ORACLE_HOME must be set to the ORACLE_HOME value of the ORACLE server . the ORACLE Installation and Configuration section provides information on how to check the and configuration of your ORACLE database. Check your basic database configuration on the server as follows: o Log in as temip (Director user account) o Enter the following command: sqlplus /@temip_tt If you can connect to the database, your configuration has probably completed successfully. 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 5.1.5 for further details. or o The /etc/listener.ora file does not contain an entry dealing with the database involved. Refer to Section 5.1.5 and the /usr/kits/TNM310/examples/listener.ora.on_server file for further details. 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 5.1.5 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. Installing TeMIP o The temip_start command was not run in the environment where the ORACLE_HOME environment variable was (correctly) set. Refer to Section 5.1.2 for further details. 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.3. ______________________________________________________ If you are configuring a distributed system, you should first check TCP/IP reachability. 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 Configuring Network Time Protocol for TNS Synchronization In a distributed configuration, TNS requires network- synchronized time to ensure that TNS servers generate consistent timestamps. Digital recommends Network Time Protocol (NTP) for this purpose. However, if you have DECnet running (and specifically DECdts (Distributed Time Service)) for other reasons, then you can use DECdts instead and skip this section. NTP is part of the DIGITAL UNIX OSFCLINET4xx subset. You can configure NTP only after this subset is installed. Before configuring NTP on a particular system, you need to do the following: 1. Decide which of your systems will be local NTP servers and which will be NTP clients. 2. 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 After Installing TeMIP 5-7 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. following shows an example ntpsetup session: ntpsetup ******************************************************************** * * * Network Time Protocol (NTP V3) Setup * * * ******************************************************************** NTP has already been installed on this host. 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. Authentication mode ------------------- Authentication mode causes the server to synchronize with peers only if the peer has been correctly authenticated using a trusted key and key identifier. In choosing to enable authentication, you must already know the key number and the key identifier in order to correctly configure each host name and the /etc/ntp.keys file. If you do not know this information, enter 'n' in response to the next question. See the Network Administration manual and ntp.conf(4) for information on authentication. Installing TeMIP Would you like to enable authentication (y/n) [n]? NTP Server/Peer Selection ------------------------- During the selection of servers and peers, you will be asked for a hostname, and for the mode, server or peer, to be associated to each hostname. Press RETURN to terminate the list. Hostname of NTP server/peer [no default]: poupix Mode for poupix (server or peer) (s/p) [s]? Looking up host poupix ... found. Is poupix running ntpd (V1) or xntpd (V2 or V3) (V1/V2/V3) [V3]? Hostname of NTP server/peer [no default]: The list of NTP servers is: server poupix version 3 Enter "r" to REDO the servers list, "e" to EXIT the ntpsetup procedure, or "c" to CONTINUE [no default]: c Created ntp.conf IMPORTANT NOTE -------------- If any of the NTP servers you specified are not in the same IP subnet as your system, 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 or your servers. 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 not monitored very closely by a system manager (such as workstations). Would you like to use the -g option (y/n) [y]? Prevent time getting set backwards, -x ------------------------------------------- The -x option prevents xntpd from correcting time when the offset is negative. This can happen for example if the server(s) have fallen behind for some reason. Would you like to use the -x option (y/n) [n]? After Installing TeMIP 5-9 Configuring your system to run NTP... done. Starting the NTP daemon (xntpd)... kernel timezone variable the current time and date with ntpdate Nov 25 14:14:43 MET 1997 succeeded. Time Service started To monitor NTP, enter "/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 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. TNS Clerk Systems TNS clerk is configured as part of the TeMIP setup (see Section 5.3 below), but some preliminary may be necessary. you are upgrading a system that was a TeMIP director a different namespace (TNS or or MIR) before, you deregister the director from the old namespace before can register it in the new one. To do this, enter: -d that the namespace you are using has the following .temip (containing the TeMIP director information) .MCC_SNMP_BackTranslation (in order to create SNMP entities) .DNA_NodeSynonym (in order to create DNA5 entities) .DNA_BackTranslation.%X49.%X.... (in order to create DNA4 entities) Installing TeMIP 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.2.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. 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. The files involved are as follows (those marked with * are saved by temip_setup before being overwritten): o Dictionary o Configuration file (*) o Dispatch tables file Conditions The temip_setup program first checks that the following conditions apply: o The login must be as super-user. o No TeMIP Framework processes can be running. o The mandatory TeMIP Framework subsets must have been installed. If any of these conditions are violated, temip_setup will abort. After Installing TeMIP 5-11 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: Licenses and Ping step checks the TeMIP licenses and it checks that the system is able to ping itself. The setup procedure abort if the superuser account is not set correctly well 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-Plus Module. If so, the setup procedure create an system entity as a child entity of the MCC entity the local director. you answer "no", the corresponding application will be configured and the tool will ask you if you want use a dictionary without any DECnet-Plus definitions. dictionary without any DECnet-Plus definitions is reduced in size. If you answer "yes", the application will be created and the installed will contain the full TeMIP Framework ________________________ Note ________________________ In a distributed configuration, all dictionaries must be compatible. If you do not plan to use the DECnet- Plus Access Module, you should answer "no" to this question for all your directors. If you plan to use the DECnet-Plus Access Module on any director, you should answer "yes" to this question for all your directors. ______________________________________________________ Installing TeMIP 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 "dtterm -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. Dictionary Installation This is an automatic step that installs the working dictionary, according to information given in Step 2: Basic Configuration. This is done using the following software links: /usr/mcc/mcc_system/mcc_fdictionary.dat /usr/mcc/mcc_system/mcc_fdictionary.bpt /usr/mcc/mcc_system/mcc_fdictionary.log /usr/mcc/mcc_system/en_US.ISO8859-1/mcc_fdictionary.dat /usr/mcc/mcc_system/en_US.ISO8859-1/mcc_fdictionary.bpt /usr/mcc/mcc_system/en_US.ISO8859-1/mcc_fdictionary.log ________________________ Note ________________________ The dictionary installed corresponds to the en_ US.ISO8859-1 (American English) language. Other languages require manual operations. ______________________________________________________ After Installing TeMIP 5-13 a Database step is only executed if the Server subset is This step is automatic and assigns the ORACLE to support the following Function Modules: TeMIP Alarm Handling FM TeMIP Trouble Ticketing FM ___________________ Important Note ___________________ You must remember to set the appropriate values for the database in the TeMIP configuration file, as described in Section 5.1.2. ______________________________________________________ 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.2. ______________________________________________________ all directors, regardless of the namespace selection, is a local MIR database present. Furthermore, on director operating in nondistributed mode with a MIR there is also a so-called TNS datastore, but is local and not distributed, and is not under the of TNS. director operating in nondistributed mode with a TNS makes use of a TNS datastore that is distributed TeMIP is not); the TNS datastore is located on TNS server, and under the control of TNS. A director in distributed mode with a TNS namespace also use of a distributed TNS datastore (TeMIP is also independently); the TNS datastore is located a TNS server under the control of TNS. 5-1 illustrates the data stores seen by TeMIP distributed TNS datastore for a management module will contain the Managing Director attribute and may other data, according to the design choice made for module on splitting data between local and distributed Installing TeMIP 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. Copying the Dispatch Tables File A dispatch tables file containing entries for all TeMIP management modules is delivered with the kit. This step will either install the dispatch tables file delivered with the kit or ask if you wish to overwrite the existing dispatch tables (in case of reinstallation). The installation procedure installs a dispatch tables file with a name having the extension ".delivered". If you have chosen to overwrite the existing dispatch tables file, you need to re-enroll any private management modules after temip_setup 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. For a description of how to check the consistency of dispatch tables on different directors, refer to the TeMIP Director Configuration and Management Guide. For a description After Installing TeMIP 5-15 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. This option is valid if the BASE, PM and SERVER subsets are installed. AM/FM Server 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. 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. director is created according to your choice from the above. the case of a director that is already configured, this displays the current director configuration (using -l) and then asks if you wish to keep the configuration. Installing TeMIP 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. ______________________________________________________ OSI System Selection Depending on choices made in the Basic Configuration step, this step may be run to ask the name of the local OSI system entity. In this case, the OSI system entity will be created and registered. If the OSI system entity is already defined, this step will not be executed. Visual TeMIP Setup If the Visual TeMIP C++ Developer Toolkit (TFC) subset is installed, this step asks you if you want /usr/bin/visual_ temip_setup to be run. If you answer "yes", the visual_temip_setup procedure enrolls the various examples provided with Visual TeMIP and creates the corresponding applications: o visual_temip_example_am : TeMIP Example AM o visual_temip_example_fm : TeMIP Example FM o vt_dev_am : TeMIP Development AM An example of the temip_setup question and the output of visual_temip_setup is provided below: After Installing TeMIP 5-17 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 installation. 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 User Documentation Location step asks if you have the HTML user documentation locally, or if the Iconic Map PM will link to a documentation set. For a remote documentation set, must enter the URL so that the local Iconic Map PM can to this, for example: HTML documentation set type (local/remote) [local]: remote URL of remote documentation root directory: http://limoge.vbe.dec.com/temip Iconic Map PM and the TeMIP PM are delivered with Help System configuration files, which provide a keyword to URL mapping. You can customize this to include new entity classes. For details, see the Customization and Troubleshooting Guide. 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. and Starting the TNS Clerk the TNS clerk is configured during the TeMIP setup it is left running. Should you at a later stage to stop the TNS clerk log in as root and enter: tns_clerk_stop restart the TNS clerk, enter: tns_clerk_start Installing TeMIP 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 - TNSCLR for the TeMIP Name Service Clerk - TNSSRV for the TeMIP Name Service Server ) - REL for the TeMIP Framework Release Notes subset - DOC for the TeMIP Framework HTML documentation and where v represents the major software version and uu represents the software version update. After Installing TeMIP 5-19 HTML Documentation IVP following example shows the HTML IVP: "TeMIP Framework HTML Documentation (level 1 rev D)" (TFRDOCV31A) you like to run the TFRDOCV31A IVP? (y/n) [y] Framework HTML Documentation (level 1 rev C) (TFRDOCV31A) netscape, please wait... netscape window is opened. the subset OSFNETSCAPE410 is not installed, IVP will with the following message: Cannot find netscape tool in current path. Please add path for netscape in your current path and retry the following command : setld -v TFRDOCV31A the DISPLAY variable is not set, IVP will fail with the message: DISPLAY variable is not set. Cannot launch netscape tool. Please set the DISPLAY variable and retry the following command : setld -v TFRDOCV31A the TeMIP Program Files Installed list of the TeMIP program files installed on a system is in the file: view the list, enter the following command at the system 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 kernel parameters correctly. < Choose or create the temip (Director user) 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 ____________________________________________________________ DECsafe Single-Service Configuration Example This appendix describes a single-service DECsafe configuration example. Single Service: TNS + TeMIP TNS and TeMIP are installed on one member system. Upon failure detection, they will automatically be relocated to another member. ________________________ Note ________________________ The TNS Clerk does not need to be installed on all members because it is part of the service. ______________________________________________________ the Single Service 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 unless otherwise indicated. 1. LSM configuration 2. AdvFS configuration 3. First ASE configuration pass: Creating a TNS_TEMIP disk service 4. Add users acloc and temip 5. TNS server and TeMIP installation 6. TNS server configuration 7. TeMIP setup 8. TNS softlink setup (on second system) 9. Second ASE configuration pass: Adding Action Scripts LSM configuration A single disk group is created for the single ASE service that will be configured. ________________________ Note ________________________ The numbers shown are only examples. ______________________________________________________ DECsafe Single-Service Configuration Example B-1 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. the following filesets: mkfset dom2 set1 mkfset dom2 set2 mkfset dom2 set3 mkfset dom2 set4 mkfset dom2 set5 mkfset dom2 set6 mkfset dom2 set7 mkfset dom2 set8 set1 to set8 are the names of the sets in this Single-Service Configuration Example Creating a TNS and TeMIP Disk Service Use the asemgr utility to create the TNS and TeMIP disk service as follows: service type : disk service service name : TNS_TEMIP (there must be an entry for "TNS_TEMIP" in /etc/hosts) Assign an IP address to this service : Y AdvFS set name : dom2#set1 disk mount point : /usr/mcc access : read-write AdvFS set name : dom2#set2 disk mount point : /usr/kits/TNM310 (TemIP constraint on the name) access : read-write AdvFS set name : dom2#set3 disk mount point : /usr/var/mcc (TeMIP constraint on the name) access : read-write AdvFS set name : dom2#set4 disk mount point : /usr/var/kits/temip (TeMIP constraint on the name) access : read-write AdvFS set name : dom2#set5 disk mount point : /usr/temip_homes (used to root the home directories of acloc and temip account) access : read-write AdvFS set name : dom2#set6 disk mount point : /usr/tns (TNS constraint on the name) access : read-write AdvFS set name : dom2#set7 disk mount point : /var/tns (TNS constraint on the name) access : read-write AdvFS set name : dom2#set8 disk mount point : /var/tnscp (TNS constraint on the name) access : read-write ASP Policy : balanced automatic relocate : no ________________________ Notes ________________________ o The name "TNS_TEMIP" for the service is only an example and not a requirement. o The service name "TNS_TEMIP" will be the name of the alias (virtual hostname defined in /etc/hosts). o The mount point /usr/temip_homes is an example of a parent directory name and not a requirement. o The action scripts will be added after TNS and TeMIP installation. ______________________________________________________ Add Users acloc and temip Add users acloc and temip (Director user account) if they are not present (HOME = /usr/temip_homes for both). DECsafe Single-Service Configuration Example B-3 Server and TeMIP Installation and TeMIP installation can only be done after ASE setup they require the appropriate disk mount points to configured on a shared fileset. the required TeMIP subsets and the TNS clerk and subsets from the TeMIP kit, see also Chapter 4. All must be installed on the shared disks. TeMIP installation, all TeMIP images are located in directories and logical links are created in UNIX standard directories to point to these images example /usr/bin for executables and /usr/shlib for libraries). These standard directories are on the disks. In order to install TeMIP on a shared disk, links need to be re-created on the private disks of ASE member (except for the member where the kit was as the links are set up during the installation) the command temip_setup -s "TNS_TEMIP", where TNS_ is the service name, see Section 3.4.9. Server Configuration configure your TNS server in a DECsafe environment, the following steps: First use the command tns_server_setup. Choose option 3, 4 or 5 according to the type of configuration you have planned. 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 TNS_TEMIP and the names of the machines that are ASE members. ________________________ 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_TEMIP, and not the address of a specific host. ______________________________________________________ Answer [NO] to the last question: Do you want this TNS server to be started automatically at boot ? (Y/N) [N] : Also, remove the following files to prevent the TNS clerk from being started automatically at boot time: /sbin/rc3.d/K02tns_clerk /sbin/rc3.d/S93tns_clerk Instead, you start the clerk using the Start script. 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. Relocate the TNS and TeMIP disk service to another system. Single-Service Configuration Example 3. On the system where the disk service now is, enter the following command: cd / ; /usr/mcc/install/TFRTNSSRV.links This command makes the links from the DIGITAL UNIX standard directories (on the local disk) to the TNS images (on the shared fileset). These softlinks must be created once, during the installation phase, on each member where the TNS server can be relocated. _______________________ Warning _______________________ If you do not create these links you will be unable to run the TNS and TeMIP disk service after relocation. ______________________________________________________ TeMIP Setup Perform the following steps: 1. On the system where the TeMIP disk service is, run temip_setup with the -v option: temip_setup -v The parameter service_name is the name you gave when creating the TeMIP disk service (see Section 3.4.3). 2. Relocate the TeMIP disk service on the second system (where TeMIP is not installed). 3. On the system where the TeMIP service now is, run temip_ setup with the -s option: /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). For full details of the TeMIP setup procedure, see Section 5.3. TNS Softlink Setup On the other system (where the service is not installed), run the scripts /usr/mcc/install/TFRTNSCLRK.links and /usr/mcc/install/TFRTNSSRV.links to create the softlinks needed by TNS. Then start TNS manually using the tns_start command. This command starts the clerk and the server. Add Action Scripts When TeMIP is correctly configured on the DECsafe system, Digital recommends you first to relocate the TeMIP service manually and start TeMIP manually to make sure that everything is operational. Do this operation several times as a test. The commands for starting and stopping the service are: DECsafe Single-Service Configuration Example B-5 tns_start temip_start ... temip_stop tns_stop the test phase, you can start adding the action 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 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 and TeMIP service, use the ASE Manager utility (asemgr): = "TNS_TEMIP" (service name) = 600 ________________________ Notes ________________________ o If you want to disable the TNS server from TNS_ TEMIP, you can comment out the corresponding section in the start/stop ASE scripts. ______________________________________________________ Single-Service Configuration Example Start Script The steps in this script are as follows: o Define the 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 the TNS server and clerk. 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. Start Script Contents #!/bin/sh # # PATH=/sbin:/usr/sbin:/usr/bin DIR_SERVER=/usr/kits/oracle_server/oracle DIR_CLIENT=/usr/kits/oracle_client/oracle DIR_ORACLE=/usr/kits/oracle export PATH returnValue=0 ROOT="" MCCUSR_CONFIG="$ROOT/usr/mcc" MCCUSR_TOOLS="$MCCUSR_CONFIG/mmtoolkit/bin" export ROOT MCCUSR_CONFIG MCCUSR_TOOLS # # get the service name from arg list. # if [ $# -gt 0 ]; then svcName=$1 else echo "Usage; $0 svc_name" exit 0 fi # LOGGER=/var/ase/tmp/childLog.$$ rm -f ${LOGGER} DECsafe Single-Service Configuration Example B-7 TNS CLERK AND SERVER STARTUP [ ${returnValue} -eq 0 ]; then dir directory . # start MCC TEMIP applications, begin # Check that temip_config is available if [ -f $MCCUSR_TOOLS/temip_config ]; then # Check that a director is configured $MCCUSR_TOOLS/temip_config -l returnValue=$? nbretry=0 while [ ${returnValue} -ne 0 -a $nbretry -lt 60 ] do sleep 10 nbretry=`expr $nbretry + 1` echo "retry number = $nbretry" $MCCUSR_TOOLS/temip_config -l returnValue=$? done if [ ${returnValue} -eq 0 ]; then # TeMIP start, begin $MCCUSR_TOOLS/temip_start # TeMIP start, end Insert here the start temip applications you want to automaticaly start, for example : manage enable mcc 0 collection_am sink udpip manage create domain xyz ip poller ... Add here the specifics startup of the OSI_ ASCII_AM and of your own MM. fi fi # start MCC TEMIP applications, end Single-Service Configuration Example # # exit with the return value equal to 0 (ok) # exit 0 Stop Script The steps in this script are: o Define TeMIP environment variables. o Obtain the service name from the argument list. o Stop TeMIP processes. o Shut down the TNS server. o Stop all other processes on the disks used by the disk service (lsof tool). o 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. Stop Script Contents #!/bin/sh # # PATH=/sbin:/usr/sbin:/usr/bin DIR_SERVER=/usr/kits/oracle_server/oracle DIR_CLIENT=/usr/kits/oracle_client/oracle DIR_ORACLE=/usr/kits/oracle export PATH returnValue=0 ROOT="" MCCUSR_CONFIG="$ROOT/usr/mcc" MCCUSR_TOOLS="$MCCUSR_CONFIG/mmtoolkit/bin" export ROOT MCCUSR_CONFIG MCCUSR_TOOLS # # get the service name from arg list. # if [ $# -gt 0 ]; then svcName=$1 else echo "Usage; $0 svc_name" exit 0 fi # stop temip process, begin # Check that temip_config is available if [ -f $MCCUSR_TOOLS/temip_config ]; then # Check that a director is running $MCCUSR_TOOLS/temip_config -l returnValue=$? if [ ${returnValue} -eq 0 ]; then DECsafe Single-Service Configuration Example B-9 Insert here the stop temip applications you want to automaticaly stop, for example : manage disable mcc 0 collection_am sink udpip manage disable domain xyz ip poller manage delete domain xyz ip poller ... Add here the specifics stop of the OSI_ ASCII_AM and of your own MM. # TeMIP stop, begin $MCCUSR_TOOLS/temip_stop -k # TeMIP stop, end fi stop temip process, end TNS CLERK AND SERVER STOP stop the tns_server, begin stop the tns_server, end stop all other process on the disks used by the disk service, begin replace in the following line 'temip_ with the name or your AdvFS filedomain | grep 'temip_ | awk '{printf("%s ", $1)}'` -Di -t $setlist` [ -n "${process}" ]; then kill -HUP ${process} stop all other process on the disks used by the disk service, end If anything in the logger cat it to stdout which will then be sent to the syslog daemon.log [ -s "${LOGGER}" ]; then cat ${LOGGER} -f ${LOGGER} Single-Service Configuration Example # # exit with the return value equal to 0 (ok) # exit 0 DECsafe Single-Service Configuration Example B-11 ________________________________________________________ Index _______________________________ installation, 1-22 Database access (ORACLE), 5-4 database, creation (ORACLE), 5-3 account, requirements, 1-3 TeMIP, Database selection, 5-14 DECsafe selection, 5-12 acloc accounts, 1-14 creation, 5-17 ASE documentation, 1-20 deletion, 5-17 ASE installation, 1-20 ASE setup, 1-21 ORACLE client, 3-12 ORACLE server, 3-5 single disk service, B-1______________________ TeMIP server, 3-12 (BOM), TNS server, 3-5 using ASE, 1-20 Device special name, 4-9______________________ Dictionary installation, 5-13 Director Toolkit, type, 1-5 1-3 Directories, 1-6 Director mode, 5-16 1-6, Director name, 5-16 4-6 Director startup, 5-18 Director user account, 1-13 configuration for ORACLE, checklist 5-2 the Director user account selection, 5-13 1-3 Disk service TNS and TeMIP together, B-1 scripts Disk space, 1-6 Dispatch tables file copying, 5-2 5-15 ASE, 1-21 Display resolution checking changing, 1-16 5-4 changing font paths, 1-17 file checking font paths, 1-17 checking system setting, 1-16 user accou checking the hardware, 1-15 X-Server configuration, 1-15 database, Distribution kit, 1-4 Documentation installation of HTML, 4-11 on Intranet, 4-13 Index-1 in HTML, 5-18 L______________________________ License________________________ Management Facility, 1-21 selection, registration, 1-21 List of program files________________________ installed, 5-20 5-20 LMF See License Management problems, Facility 1-18 Logging on, 1-6 ________________________ M _______________________________ requirements, MCC_DNS_SELECTION, 5-14 MCC_NODE_IDP, 5-10 4-11 Menu 5-18 Remote Installation 4-13 Environment, 4-9 access RIS Utility, 4-8 RIS Utility Software file, Installation, 4-9 MIR journaling function, 5-15________________________ N______________________________ the, Namespace for, requirements, 1-4 user Namespace selection, 5-14 CD-ROM, ASE, 1-20 O______________________5-2_____ checking the, 5-6 ORACLE Notes, 4-3 checking the configuration, 4-1 to 4-13 5-6 documentation, 4-11 checking the installation, TeMIP, 4-6 5-6 4-8 client configuration, 3-12 from errors, 1-22 configuration from a CD-ROM, 1-1 for archive directive, RIS, 1-1 5-1 4-2, 5-19 for TeMIP Trouble procedure, 4-1 Ticketing access, 5-1 Verification configuration of director 4-2, 5-19 user account, 5-2 installation, 5-2 server configuration, 3-5 OSI system selection, 5-17 Verification Ownership change, 5-13 P______________________________ Paths to installed files, 1-6________________________ Ping, 5-12 parameter Preparing to install TeMIP, 4-2 1-1 to 1-22 Procedure installation, 4-1 Setup (cont'd) configuration file creation,__________________________ 5-15 from copying dispatch tables file, 1-22 5-15 Notes dictionary installation, 4-4 installed, 4-4 5-13 the, 4-3 director mode, 5-16 Installation MIR journaling, 5-15 modifying resource files, Menu, 5-15 DECwindows namespace selection, 5-14 applications, 1-2 of a new director, 5-11 of DECsafe ASE, 1-21 1-3 of the system, 4-2 space, OSI system selection, 5-17 1-2 overwrites, 5-11 registration, ownership change, 5-13 types, ping, 5-12 V1.1.3, selecting a database, 5-14 1-4 selecting director user system, 1-3 account, 5-13 1-2, 1-4 starting the director, 5-18 combinations, 1-5 system parameter check, 5-18 backup, 1-6 time format selection, 5-14 1-5 Sizing advice, 1-6 Software 1-17 requirements, 1-2 font sizes, 1-18 subsets, 4-4, 4-7 display, changing, 1-16 Software subsets 1-18 choosing the, 4-9 Subset 4-8 combinations for director 4-8 types, 1-5 Menu, 4-8 Subsets, 1-4 Software Installation Synchronization, 5-7 Menu, 4-9 System 4-2 backup, 1-6 SQL*Net, 5-3 setup, 4-2, 5-11 TeMIP, 5-2 System directory, 4-2 System parameter check, 5-18 __________________________ T _______________________________ 1-18 TeMIP kernel parameters test object, 4-3 1-9 upgrade, 1-6 1-9 temip account, 1-13 1-8 temip_setup command, 5-11 1-11 Test Object selection, 5-12 1-12 Time 1-12 synchronization, 5-7 1-12 Time format selection, 5-14 1-10 Time requirements, 1-5 1-10 TNS 1-11 IVP, 5-19 1-11 Toolkit, 1-4 1-10 C++, 1-3 disk space, 1-6, 1-7 creation, 5-17 installing, 4-6 deletion, 5-17 configuration, 5-12 Index-3 Ticketing selection, V______________________________ Visual TeMIP, 1-3, 1-4 deleting V1.0, 2-3________________________ installing, 4-6 1-6 IVP, 4-8, 5-19 setup procedure, 5-17 1-13 X______________________4-12____ X-Server configuration see Display resolution X-Server options, 1-19 X-Server planes, 1-20