HPE Operations Agent for NonStop

Transcription

1 HPE Operations Agent for NonStop Installation Guide Abstract This guide explains how to install, configure, start and stop OVNM components. Part number: Published: January 2016 Edition: 1 2

2

3 Legal and notice information Copyright 2016 Hewlett Packard Enterprise Development LP The information contained herein is subject to change without notice. The only warranties for Hewlett Packard Enterprise products and services are set forth in the express warranty statements accompanying such products and services. Nothing herein should be construed as constituting an additional warranty. Hewlett Packard Enterprise shall not be liable for technical or editorial errors or omissions contained herein. Confidential computer software. Valid license from Hewlett Packard Enterprise required for possession, use, or copying. Consistent with FAR and , Commercial Computer Software, Computer Software Documentation, and Technical Data for Commercial Items are licensed to the U.S. Government under vendor's standard commercial license. Links to third-party websites take you outside the Hewlett Packard Enterprise website. Hewlett Packard Enterprise has no control over and is not responsible for information outside the Hewlett Packard Enterprise website. No part of this documentation may be reproduced or transmitted in any form or by any means without prior written consent of Hewlett Packard Enterprise. The information contained herein is subject to change without notice. Warranties HEWLETT PACKARD ENTERPRISE MAKES NO WARRANTY OF ANY KIND WITH REGARD TO THIS MATERIAL, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE. Hewlett Packard Enterprise shall not be liable for errors contained herein or for incidental or consequential damages in connection with the furnishing, performance, or use of this material. The only warranties for Hewlett Packard Enterprise products and services are set forth in the express warranty statements accompanying such products and services. Nothing herein should be construed as constituting an additional warranty. Hewlett Packard Enterprise shall not be liable for technical or editorial errors or omissions contained herein. Acknowledgments Intel, Itanium, Pentium, Intel Inside, and the Intel Inside logo are trademarks of Intel Corporation in the United States and other countries. Microsoft and Windows are trademarks of the Microsoft group of companies. Adobe and Acrobat are trademarks of Adobe Systems Incorporated. Java and Oracle are registered trademarks of Oracle and/or its affiliates. UNIX is a registered trademark of The Open Group. Revision History Rebranded for Hewlett Packard Enterprise January 2016 i

4 Contents Preface 5 Before You Begin 5 Who Should Read This Guide 5 Goals of Documentation 5 Organization 5 OVNM Documentation Map 6 Electronic Versions of the Manuals 6 OVNM Manuals 6 Additional OVNM-Related Products 7 About OVNM Online Help 7 1 OVNM Installation Overview 8 Overview 8 Microsoft Windows Environment 9 HPE Operations Manager Environment 9 SNMP Adapter 9 HPE NonStop Environment 9 UNIX/LINUX Environment 10 System Requirements 11 HPE NonStop Node 11 HPE OM Management Server 11 Workstation Environment 11 Prerequisites for OVNM Installation 11 2 OVNM Installation on Windows 13 Installing OVNM on Windows 13 Silent Install on Windows 18 Starting OVNM on Windows Operations Manager 19 Upgrading OVNM to a Newer Version 19 Upgrading OVNM Components on Windows 20 Silent Upgrade on Windows 22 Upgrading OVNM Components on the HPE OM Server 22 Upgrading OVNM Agent on the HPE NonStop Server 22 Testing Upgrade 24 3 Installing OVNM on HPE NonStop Server 25 Host Tab Page 26 Communication Tab Page 30 Policies Tab Page 33 Mail Tab Page 34 Distributor Tab Page 36 OCC Tab Page 38 Plug-Ins Tab Page 39 EMS Template Tab Page 40 BASE24 Tab Page 41 Enterprise Tab Page 43 MQ Series Tab Page 44 ii

5 4 Upgrading OVNM on HPE NonStop Server 47 Considerations while Upgrading OVNM 47 Upgrading OVNM 49 5 Installing OVNM on HPE OM UNIX 51 Introduction 51 Installing OVNM on HPE OM UNIX 51 Obtaining the Appropriate OVNM Depot.tar File 51 OVNM Installation 52 Configuring OVNM on HPE OM UNIX 53 Configuring the HPE OM Environment 55 Configuring the HPE OM8 Environment 55 Configuring the HPE OM9 Environment 64 Starting OVNM on HPE OM UNIX 71 Testing OVNM and HPE OM Integration 72 Upgrading OVNM on HPE OM UNIX 74 Adding Additional NonStop Nodes 75 6 Installing OVNM on Linux Server 76 Introduction 76 Installing OVNM on Linux Server 76 Obtaining ovnm_linux.tar.gz File 76 OVNM Installation 76 Configuring OVNM on Linux 77 Configuring the HPE OMU 9 Environment 78 Starting OVNM on HPE OMU 9 Linux 79 Upgrading OVNM on Linux 80 7 Uninstalling OVNM 81 Uninstalling OVNM from HPE OM UNIX 81 Uninstalling OVNM from HPE NonStop Server 93 Uninstalling OVNM from Linux (Removing NonStop Nodes from HPE OM9) 96 Removing NonStop Nodes 96 Removing NonStop Node Group 98 Removing NonStop Message Group 99 Removing NonStop Applications 100 Removing HPE NonStop Server Policy 102 Uninstalling OVNM from Windows Workstation 104 Silent Uninstall from Windows 105 Appendix A: Installation Information 106 Appendix B: Custom Installation 109 Appendix C: Sample Installation Session on HPE OM HPUX 110 Appendix D: Sample OVNM Configuration on HPE OM UNIX 111 Appendix E: HPE MC/SG Cluster Installation Supplement 114 OVNM SPI: Installation Considerations on HPE OM Cluster 114 OVNM SPI Configuration Information 114 MC/SG Cluster Package Control Script 115 iii

6 Appendix F: Manual Operations on HPE NonStop Server 116 Manual OVNM Agent Installation on HPE NonStop Server 116 OVNM Installation / Release Upgrade 117 Manual OVNM Uninstallation 119 Manually Starting OVNM on a HPE NonStop Server 119 Manually Testing Communication 119 Manually Stopping OVNM on a HPE NonStop Server 119 Manually Stopping OVNM on Operations Manager Management Console in Windows 119 Appendix G: Sample InstInfo File 120 iv

7 Preface HPE Operations Agent for NonStop (OVNM) is an out-of-the-box solution that provides seamless integration of HPE Operations Software (previously known as HPE OpenView) with HPE NonStop servers. The software is a natural extension of HPE Operations and provides you with true end-to-end management of your NonStop environment. OVNM User and Installation guide provides information about how to install and get started with the product. Before You Begin Before reading the documentation, you are expected to have a basic understanding of HPE Operations environment, as well as the HPE NonStop environment. Familiarity with the HPE NonStop Distributed Systems Management software, especially the Event Management Service, would be helpful. Who Should Read This Guide This guide is intended for the following two types of users. Administrators, who plan, set up, and maintain OVNM and Operations Manager. Operators, who perform daily tasks using OVNM and Operations Manager. Goals of Documentation Organization After reading this guide, you should know the following information. Installing/Uninstalling OVNM on Windows as well as the HPE NonStop Managed host Working with Host Installation Client Working with Host Management Client Overview of Operations Manager Tools and Policies Troubleshooting OVNM The guide is organized as follows. Chapter No. Chapter Name Description Chapter 1 OVNM Installation Overview Overview of the various procedures involved in installing the OVNM product. Also lists the software and hardware prerequisites for the HPE Operations management server and the HPE NonStop managed nodes. Chapter 2 Installing OVNM on Windows Details the OVNM installation procedure on Windows. Chapter 3 Chapter 4 Chapter 5 Installing OVNM on HPE NonStop Server Upgrading OVNM on HPE NonStop Server Installing OVNM on HPE OM UNIX Gives instructions on how to install OVNM on a HPE NonStop managed server using the Host Installation Client. Explains the procedure to upgrade OVNM on HPE NonStop Server. Gives instructions on how to install and configure OVNM on an HPE OM UNIX server. Chapter 6 Installing OVNM on Linux Server Gives instructions on how to install and configure OVNM on a Linux Server. Chapter 7 Uninstalling OVNM Gives instructions on how to uninstall OVNM. Appendix A Installation Information Installation Information form, which will be helpful during the installation process. 5

8 Appendix B Custom Installation Gives information about how to customize OVNM installation by selecting various components for installation. Appendix C Appendix D Appendix E Appendix F Sample Installation Session on HPE OM HPUX Sample OVNM Configuration on HPE OM UNIX HPE MC/SG Cluster Installation Supplement Manual Operations on HPE NonStop Server Appendix G Sample InstInfo File Provides a sample InstInfo file. Provides a sample installation session on Operations Manager HPUX. Provides a sample OVNM configuration on Operations Manager UNIX. Provides information on how to install and configure OVNM on a MC/SG Cluster. Describes the manual installation, uninstallation, starting and stopping of OVNM components on the HPE NonStop Server. OVNM Documentation Map HPE OVNM provides a set of manuals and online help that help you use the product and understand the concepts underlying the product. This section describes what information is available and where you can find it. Electronic Versions of the Manuals All manuals are available as Adobe Portable Document Format (PDF) files in the documentation directory on the HPE OVNM product CD-ROM. All manuals are also available in the HPE web server directory. For details, contact the appropriate HPE support service. OVNM Manuals This section provides an overview of the OVNM manuals and their contents. Manual Description Media OVNM Concepts Guide Explains OVNM features, functions, benefits, architecture, and data flow. Describes OVNM agent and server components. OVNM Installation Guide Explains how to install, configure and start and stop OVNM components PDF OVNM User Guide OVNM SNMP Adapter Guide OVNM Console Guide OVNM Object Configuration Client Guide Explains how to use the OVNM utilities and troubleshooting procedures for OVNM. Covers installation and configuration. SNMP Adapter is used when SNMP-compatible management consoles are used. such as HPE Operations Network Node Manager, BMC s PATROL, and IBM s NetCool Explains the Console interface and provides the instructions on how to use the software effectively. Explains the Object Configuration Client (OCC) interface and provides the instructions on how to use the software effectively. OVNM Object Reference Guide Lists the various threshold policies in Object Configuration Client (OCC). PDF OVNM ObjectMAP Guide OVNM ObjectStats Guide OVNM Event Management Guide Explains the ObjectMAP interface and provides the instructions on how to use the software effectively. Explains the ObjectStats interface and the instructions on how to use it effectively. Explains the concepts of Event Integration. PDF PDF PDF PDF PDF PDF PDF PDF 6

9 Additional OVNM-Related Products This section provides an overview of the OVNM-related manuals and their contents. Manual Description Media Performance Agent OVNM Performance Agent for HPE Operations PDF PDF SMART Plug-In SPI for MQ-SERIES SPI for BASE24 PDF PDF About OVNM Online Help This preface describes online documentation for the HPE Operations Agent for NonStop (OVNM) graphical user interfaces (GUIs). Manual Description Object Configuration Client ObjectStats Console ObjectMAP Host Installation Client Host Management Client Explains the Object Configuration Client GUI and how to use the interface effectively. Explains the ObjectStats GUI and how to use the interface effectively. Explains the Console GUI and how to use the software effectively. Explains the ObjectMAP GUI and how to use the software effectively. Explains the Host Installation Client GUI and how to use the interface effectively. Explains the Host Management Client GUI and how to use the interface effectively. 7

10 1 OVNM Installation Overview Overview HPE Operations Agent for NonStop (OVNM) is an out-of-the-box solution that provides seamless integration of HPE Operations Manager with HPE NonStop servers. Although HPE OVNM is designed to integrate with HPE Operations for Windows, UNIX, or Linux, it is not required to have Operations Manager installed. The OVNM installation is performed using either Windows workstation or a Windows Server. A Window workstation is used when, OVNM Console is used as the Management Console. HPE Operations Manager is installed on HPUX, or Linux. A Windows Server is used when HPE Operations Manager is installed on a Windows Server. In order to facilitate the integration, OVNM components are installed on the HPE NonStop Server and the HPE Operations Management Server, if available. This section lists and describes the OVNM installation in various environments. The operating systems supported by OVNM and the corresponding package names are listed in the following table. Table 1. Operating Systems supported by OVNM S. No. Operating System Manager Package Name 1 Windows (32/64 bit) Vista/windows 7/ Server2003, 2008 OVNM Console (OMW 9.x) OVNMInstallation.exe 2 HPUX Integrity (Itanium) 11i v3 (B.11.31) OMU 9.x ovnm_hpux_itanium_depot.tar 3 Linux Red Hat Enterprise Linux5.5 (OML 9.x) ovnm_linux.tar.gz NOTE: Support for Solaris and HP UX PA-RISC is discontinued for OVNM 5.3 release onwards. 8

11 Microsoft Windows Environment OVNM installation on the Windows environment primarily installs the following components on the workstation. OVNM Console: Console is a Windows GUI interface program that provides a single interface for managing all aspects of the OVNM environment running on NonStop Servers. Console is intended for NonStop Server Application and System Specialists. By providing basic Console management features found in HPE Operations Manager, the NonStop specialist / Operations staff can use the OVNM product without having any Enterprise Manager software installed (i.e. HPE Operations Manager, Network Node Manager, IBM Netcool etc.) OVNM Host Installation Client: The OVNM Host Installation Client is an interactive GUI, which is used to automate the procedures like installation and modifications on the HPE NonStop managed node. OVNM Host Management Client: The OVNM Host Management Client is an interactive GUI, which is used to automate the HPE NonStop host management procedures like starting and stopping OVNM agents on the HPE NonStop Server. OVNM Object Configuration Client (OCC): The OCC is an interactive and user-friendly interface, which is used to define the desired state of a NonStop object in operation. It allows you to create, modify and delete threshold configurations and perform active monitoring and management of events. OVNM ObjectMAP: ObjectMap is a user-friendly interface, which is used to display the current state of all or a subset of the objects being monitored by OVNM. It allows users to create their own views as well as request additional information about the object. OVNM ObjectStats: ObjectStats is a user-friendly interface, which is used to display statistics regarding the number of objects in each of the violation states (normal, critical, major, minor, warning and unmanaged). It also allows users to request additional information about objects, but only objects that are in violation status. For details on how to install OVNM components on the Windows environment, refer to the installation of OVNM on Windows guide. HPE Operations Manager Environment SNMP Adapter OVNM installation on the Operations management server primarily involves the installation of the OVNM SPI Agent, which feeds the NonStop events into the HPE Operations Message Browser. The extended events allow the escalation of events into the Service View automatically. It provides predefined out-of-the-box policies to correlate auto acknowledgment of events message instructions, operator initiated commands and tools. For details on how to install OVNM components on the Windows environment, refer to the installing OVNM on Windows guide. The supplied SNMP Adapter facilitates policy-based management for HPE NonStop servers for Enterprise Management systems that recognize SNMP Traps. This adapter takes OVNM-generated events from the HPE NonStop server and maps these SNMP events into SNMP-compatible management consoles, such as HPE Operations Network Node Manager, BMC s PATROL, and IBM s NetCool. For installation of the SNMP Adapter, refer to the OVNM SNMP adapter guide. HPE NonStop Environment OVNM installation on the HPE NonStop Managed node involves the installation of OVNM NonStop server components. These components are responsible for the discovery and monitoring of the entire system. The server components are also responsible for collecting the filtered events from various collectors and forwarding them to the HPE Operations Management Server. The installation on the HPE NonStop can be performed through Windows. Refer to the OVNM Host Installation Client section. For details on how to install OVNM agents on the HPE NonStop environment, refer to the Installing OVNM on HPE NonStop Server section. 9

12 UNIX/LINUX Environment OVNM installation on the HPE OM UNIX/LINX management server primarily involves the installation of the OVNM SPI Agent, which feeds the NonStop events into the HPE OM Message Browser. The extended events allow the escalation of events into the Service View automatically. It provides predefined out-of-the-box templates to correlate auto acknowledgment of events, message instructions, operator initiated commands and tools. For details on how to install OVNM Agents on the HPE OM UNIX Management server and Linux Server, refer to Installing OVNM on HPE OM UNIX, and Installing OVNM on LINUX Server sections, respectively. 10

13 System Requirements HPE NonStop Node Operating System Software Requirements Disk Space NonStop Server version, G06.26, H06.05, J06.04, L15.02 or higher NonStop TCP/IP 100 MB (For Installation) 10 MB (Suggested for Databases Files) HPE OM Management Server Any system on which HPE Operations is installed Operating System Software Requirements Disk Space HPUX 11iv1, 11i v2 and 11i v3 HPUX 64-Bit, Windows 32/ 64-Bit, Linux 64-Bit HPE OM 9.0 or Higher 200 MB Workstation Environment Any system where OCC and Console are to be installed Operating System Windows (XP/Vista/Window 7/2003) Protocol Disk Space TCP/IP 200 MB Prerequisites for OVNM Installation Before installing OVNM, ensure that the following tasks have been accomplished. 1. Microsoft Windows (32/64 bit) XP/Vista/Windows7 or Server2003 /2008, is used for installing and configuring OVNM's NonStop Server components. NOTE: You will need administrative rights to install the OVNM FE on Windows. 2. If the NonStop Server(s) are going to be managed by HPE OM (Windows), OVNM should be initially installed on the HPE OM Management Server. 3. If used, the HPE OM Windows Management Server must be able to resolve the HPE NonStop node(s) on which OVNM is to be installed using names. If the network has a DNS server, then the node(s) should have an entry in its records. If there is no DNS for name resolution in the network then the Hosts file on the HPE Operations Manager Server should have an entry for the HPE NonStop nodes. 4. If the NonStop Server(s) are going to be managed by an HPE OM (UNIX/LINUX), OVNM must initially be installed using a Windows Workstation or Server. 11

14 5. Refer to the OVNM SNMP Adapter guide for installations of the SNMP Adapter for Enterprise Managers that rely on SNMP traps to receive NonStop Server Events. 6. For IBM Tivoli, the OVNM Tivoli Adapter needs to be purchased and installed on the Tivoli Management Server. NOTE: The OVNM Tivoli Adapter is an optional product with Marketing ID # HOV08V1/QOV08V1. 7. FTP and Telnet services between the Windows Server (or Workstation) and the HPE NonStop node must be available. Any firewall restrictions will need to be addressed to allow the communication paths. 8. Two additional ports must be available outside the firewall for accessing HPE NonStop managed host. Default ports used by OVNM are 5020 and Guardian Super Group user ID is recommended to perform the installation. For security reasons, it is recommended not to use the SUPER.SUPER ID, but rather a Super Group User ID specifically for OVNM. For example: SUPER.OVNM. To get the most out of OVNM s Multi Node support feature, User IDs used to install OVNM should be the same across all Nodes. This includes both user name (For example: SUPER.OVNM) and the User ID number (Ex ). 10. Product key: If OVNM was not supplied with a Product Key a temporary Key for 60 days will be generated. You will need to purchase the OVNM product after the evaluation period. Contact your local HPE representative for details. 11. For OVNM to monitor Pathway applications, the PATHWAY Parameter MAXSPI should be greater or equal to 3. This enables OVNM to use the SPI interface to obtain Pathway information. 12

15 2 OVNM Installation on Windows Installing OVNM on Windows This section covers the procedure to install OVNM on Windows. To help you with the installation process, it is recommended that you fill out the Installation Information form. Refer to Appendix A: Installation Information, before installing OVNM. NOTE: The user installing OVNM must have Administrator rights/privileges on the HPE OM workstation.before starting the installation, it is recommended that you exit from any other Windows programs that are running. 1. Insert the installation CD in the CD-ROM drive, and run the OVNMInstallation.exe located in the OVNM for Windows directory. The Install Shield prepares the Setup program for use and the HPE-OVNM Welcome page is displayed. WARNING! You must totally unzip the installation package into its own folder and you are running the OVNMInstallation.exe from there NOT from inside the compressed file. Failure to do this will cause problems when installing the backend components. Figure 1. HPE-OVNM Installation Welcome Page 13

16 2. Click the Next button. The License Agreement page is displayed. Figure 2. HPE OVNM Installation License Agreement Page 14

17 3. Review the software license agreement, and click the Yes button. The Choose Destination Location page is displayed. The path of the folder where OVNM files will be installed by default is displayed. NOTE: Configuration files are now placed on the all users folder. This folder is not secured as tightly as the Program Files folder. This will reduce the likelihood that a standard user will not be able to perform some function. If you are upgrading from a previous version, the current files will be moved to the new folder so they will no longer exist in their old location. Figure 3. HPE-OVNM Installation Destination Location Page 15

18 4. Use the Browse button to specify a directory other than the default. To continue, click the Next button. WARNING! You must totally unzip the installation package into its own folder and you are running the OVNMInstallation.exe from there NOT from inside the compressed file. Failure to do this will cause problems when installing the backend components. The Setup Type page is displayed. Figure 4. HPE-OVNM Installation Setup Type Page 5. Select the type of setup required from any of the following options. Typical: This option gives complete functionality of the software. If you select the Typical option, all the OVNM components are selected for installation. This option is recommended for most users. Compact: The installation is recommended for laptop or computers with limited resources. Custom: The installation allows you to customize the selection of OVNM components to be installed. This option is recommended for advanced users. Refer to Appendix B: Custom Installation for details. 16

19 6. Click the Next button. The Check Setup Information page is displayed. Figure 5. HPE-OVNM Installation Check Setup Information Page The current settings, which have been selected, are displayed. In case you want to change any of the settings, you can do so by going back to the particular page before you start copying the program files. NOTE: You should check the location of the directory where OVNM is to be installed. To change the location after installation, you will have to reinstall the software. 7. Click the Next button. The Locked Files Information page is displayed if any of the files were found locked or in use during the modification process. These files will be updated after system reboot. 17

20 8. Click the Next button. The Setup Complete page is displayed. Figure 6. HPE-OVNM Installation Setup Completed Page 9. Click the Finish button to complete the process. The OVNM installation on a Windows workstation is completed. Silent Install on Windows In addition to locking down the PCs, many companies are using tools that will automatically install new versions of software that is allowed on the individual PC. In that regard, customers have asked for a method of installing or upgrading the software that can be executed in a batch mode. For a fresh installation, perform the following steps. 1. Open CMD. 2. Enter D:<path> >OVNMInstallation.exe r f1 D:<path>\setup.iss. This creates the setup.iss file. To execute the silent install, perform the following steps. 1. Open CMD. 2. Enter D:<path>OVNMInstallation.exe s f1 D:<path>\setup.iss. 18

21 Starting OVNM on Windows Operations Manager To start OVNM Agents on the Windows Operations Manager Management server, click the Start Programs HPE OVNM Management Server Tools Start Agents option. The Start Agents option starts the OVNM communication interface on the Windows workstation or Server. If OVNM is installed on an HPE OM server, the SPI interface is also started. For more information about configuring the SPI interface for HPE OM (OVNMCONF file), refer to the OVNM users guide. Upgrading OVNM to a Newer Version Upgrading OVNM from previously installed version to a the newer version involves the upgrading folloiwng components in the below-mentioned order. 1. Upgrading OVNM Components on Windows 2. Upgrading OVNM Components on the HPE OM Server 3. Upgrading OVNM Agent on the HPE NonStop Server 4. Testing upgrade 19

22 Upgrading OVNM Components on Windows To upgrade OVNM Components on Windows, perform the following steps. 1. Run the OVNMInstallation.exe file. The HPE-OVNM message box is displayed. Click the Yes button to continue. 2. The install shelid prompts you to close all the OVNM components running on the workstation. Click the OK button to continue. Figure 7. HPE OVNM Information Box 3. The HPE-OVNM Welcome page is displayed. The Modify option is selected by default. Click the Next button to continue. Figure 8. HPE-OVNM Welcome Page 20

23 4. The HPE-OVNM Select Features page is displayed. Select the components that need upgrade, and click the Next button. Figure 9. HPE-OVNM Select Features Page 5. If upgrading OVNM on HPE OM Windows Server, the HPE-OVNM Installation message box is displayed with the information that the installation is preparing to reinstall NonStop Tools in HPE OM. If you have modified the NonStop tools, save them, and click the OK button. 6. Another HPE-OVNM Installation message box is displayed with the information that the OVNM policies have been registered successfully, which can be deployed using HPE OM. Delete/uninstall the previous policies, and then click the OK button. 21

24 7. The Install Shield completes the installation on the workstation and the HPE-OVNM Setup Completed page is displayed. Click the Finish button. Figure 10. HPE-OVNM Setup Completed Page Silent Upgrade on Windows For Silent upgrade, perform the following steps. To perform an upgrade, perform the following steps. 1. Open CMD. 2. Enter D:<path> >OVNMInstallation.exe r f1 D:<path>\modify.iss. This creates the modify.iss file. To execute the silent upgrade, perform the following steps. 1. Open CMD. 2. Enter D:<path>OVNMInstallation.exe s f1 D:<path>\modify.iss. Upgrading OVNM Components on the HPE OM Server Refer to the Upgrading OVNM on HPE OM UNIX section for details on how to upgrade OVNM on the HPE OM UNIX server. Upgrading OVNM Agent on the HPE NonStop Server To upgrade OVNM Agent on the HPE NonStop Server, perform the following steps. 1. Before upgrading the HPE NonStop Server components, make sure that OVNM is not running on the NonStop Node you are upgrading. You can use the following command. FUP DUP <current OVNM subvol>.*, SAVEOVNM.*, sourcedate. 2. Start the OVNM Host Installation Client and select the node to be upgraded. Click the Upgrade/Upgrade Release button to start the process. You will have to logon using the HPE NonStop Server User ID and password used for this installation. For an upgrade from pre-5.x to 5.x, the Configuration Name will default to <node-name>-<vol.subvolume>. 3. Once the installation is complete, start OVNM on the HPE NonStop Server. 22

25 4. Now, start the OVNM agents on the Management Server. Click Start Programs HPE OVNM Management Server Tools Start Agents option to start the OVNM agents. The Connection established message displayed in the HPE OM Message Browser. 23

26 Testing Upgrade To generate a test EMS event, perform the following steps. Once generated, OVNM will process the message. If an Enterprise Manager is used the Manager will display the message. 1. Run Host Management Client by using the Start Programs HPE OVNM NonStop Server Tools Host Management Client option. 2. Click the Test Message button in the OVNM Host Management Client dialog box and logon using the HPE NonStop Server User ID and password used for this installation. 3. Close the Host Management Client application. 4. Go to Enterprise Management Application or OVNM s Console Application to verify that the message is delivered correctly. **** 999: OVNM: communication test was successful (Event Message Text) **** NOTE: The initial message processed may cause OVNM to initialize the Event Management components. Please wait for up to one minute for the initial messages to be processed. Subsequent events should be processed immediately. 24

27 3 Installing OVNM on HPE NonStop Server To help you with the installation process, it is recommended that you fill the Installation Information form provided in Appendix A: Installation Information. To install OVNM on HPE NonStop Server, perform the following steps. 1. Click the Start Programs HPE OVNM NonStop Server Tools Host Installation Client option to start the installation process. WARNING! For installing OVNM Agent on the NonStop server using the Host Installation client: The user performing the installation must have ftp and telnet privileges on the NonStop host. There should be no firewall on the ports being used for telnet and ftp operations. The installation on the HPE NonStop server can also be performed using the INSTALL macro. 2. The OVNM Host Installation Client dialog box is displayed. To add a HPE NonStop host, click the New button. 3. You can also import an existing configuration by clicking the Import button. Figure 11. OVNM Host Installation Client Dialog Box The New OVNM Configuration dialog box is displayed. By default the Host tab page is displayed. 25

28 Host Tab Page When you click the New button, the Host tab page is displayed by default. Figure 12. New OVNM Configuration Host Tab Page You can import a node configuration by using the Import button. For this, perform the following steps. NOTE: This Import button is available ONLY in case of New installation. It is disabled in case of Modifying configuration. 4. Click the Import button. A confirmation box for importing configuration is displayed. Figure 13. OVNM Configuration Confirmation box a. Click the Yes button to continue. 26

29 b. The Open dialog box is displayed. Browse for the.cfg file, from which you want to import the configuration. Figure 14. Open Dialog Box c. Select the configuration file, and click the Open button. d. All the fields in the OVNM Host Installation Client tab pages are auto-populated as per the details in the configuration file. To manually install a new configuration, perform the following steps. 1. In the Host tab page, specify the information as described in the following table. Table 2. NonStop Node Configuration Parameters Area Parameter Name Description Additional Information Managed Host Information Configuration Name The name of the new host configuration. The name must not duplicate any other configuration name. This field can be used to provide a descriptive name for this particular environment (e.g. DR, QA, or production). Spaces are not allowed, but hyphens and underscores are allowed. Product Key The product license key provided by HPE. You must have a license key in order to install a new node. Node Name The HPE NonStop Node name. The node name must be preceded by the \ sign. Example: \NODE1 Host Address The HPE NonStop Server IP address or DNS name. You cannot have duplicate environment definitions where the IP and Ports all match. In other words, you cannot use IP and ports 5020/5030 multiple times. Example: Example: mytandem.chicago.com User Id The HPE NonStop Server User ID. Example: ov.manager Password TCPIP Process The password corresponding to the HPE NonStop Server User ID specified. The TCPIP process name. The TCPIP Process box displays the value Default: DEFAULT 27

30 Process Prefix Work Subvolume OVNMSubvolume Home Terminal Log To Collector OVNMPort Config Client Port DEFAULT. If the TCPIP Process box is left as is, OVNM tries to get the process name from the host response during the logon process. If OVNM is still not able to find the TCP/IP process name, it prompts the user to provide it manually. A two character prefix that will be used as the first two characters for all the OVNM processes, making them unique. The subvolume where the OVNM installation files will be copied. It is recommended that you use a volume other than $SYSTEM, but it will work if you let it default to $SYSTEM. The subvolume where OVNM will be installed. It is recommended that you use a volume other than $SYSTEM, but it will work if you let it default to $SYSTEM. Select either a physical hometerm or a process that will be continuously available. The collector where the application will log all events. Port number for Elink connection with the HPE NonStop system. This will be used for Console and the Enterprise Management system. You cannot have duplicate environment definitions where the IP and Ports all match. In other words, you cannot use IP and ports 5020/5030 multiple times. Port number for the Object Configuration Client connection. It will also be used with ObjectMap and ObjectStats. You cannot have duplicate environment definitions where the IP and Ports all match. In other words, you cannot use IP and ports 5020/5030 multiple times. The first character must be a letter Both characters must be alphanumeric. Example: OV Default: $SYSTEM.ZOVNM Default: $SYSTEM.OVNM Default: $VHS Default: $0 Default: 5030 Default: 5020 Other Parameters Priority Priority of the main OVNM process. Default: 160 Recommended range: Alive Message Interval The time interval in minutes, after which Host components send an Alive message to the front-end. No message is sent by default (value 0). Default: 0 Recommended range: Primary CPU Primary CPU for the main OVNM process. Default: 0 Recommended range: 0-15 Backup CPU Backup CPU for the main OVNM process. Default: 1 Recommended range: 0-15 Filesys Threshold Option The Filesys Threshold Option check box allows you to configure the generation of alerts for the Filesys/File thresholds. If this check box Is selected, then OVNM will generate an alert if the file you are monitoring has been purged OR the file violated the particular threshold. If this box is NOT checked, then an alert will only be generated when the file exists AND the file violates the threshold. For example: Example Check box is selected: Threshold: Filesys/File threshold set for Percent Full > 80 If the file is purged, an alarm will be generated that will say Current state = critical, Violation if Percent 28

31 Box is NOT checked Threshold: Filesys/File threshold set for Percent Full > 80 If the file is purged, NO alert will be generated. Full > 80, Current: Object does not exist. Check box is NOT selected: Threshold: Filesys/File threshold set for Percent Full > 80 If the file is purged, NO alert will be generated. While configuring, if you have changed the collector in the Log To Collector field of the OVNM tab page in the New OVNM Configuration dialog box back to the default value $0, and the Distributor and OCC tab pages have collectors that are no longer needed, then the OVNM Host Installation Client confirmation box is displayed with the information about the status of the installation process. Figure 15. OVNM Host Installation Client Confirmation Box 2. To review the Distributor and OCC tab pages and make changes, click the Yes button. If the information has been already reviewed, click the No button. 29

32 Communication Tab Page To configure communication related OVNM parameters, perform the following steps. 1. Click the Communication tab. The Communication tab page is displayed. Figure 16. New OVNM Configuration Communication Tab Page 2. In the Communication tab page, specify the information as described in the following table. Table 3. Communication Parameters Area Parameter Name Description Additional Information Communication Information Show Advanced Options To view and configure advance options. Refer to the advanced communication options topic for details. Telnet and FTP Information Telnet Port Telnet Address Type of Telnet Specify the Telnet port to be used for the Telnet session with the HPE NonStop Host. Use the corresponding Address field to specify the IP address or the DNS name for the Telnet session with the HPE NonStop Host. There are 3 types of Telnet that are supported - standard, SSH2, and SSL. If your NonStop Host is configured to use one of those options, pick the selection that matches your host. The default value for this application is standard. This is unsecured Telnet and user IDs and passwords will be passed in the clear because that is the way that protocol works. SSH2 provides greater security when communicating between your PC and the NonStop. SSL is another secure protocol. But, whatever option you choose, it has to match the configuration on your NonStop. Default port: 23 FTP Port FTP Address Type of FTP Specify the FTP port to be used for the FTP session with the HPE NonStop Host. Use the corresponding Address field to specify the IP address or the DNS name for the FTP session with the HPE NonStop Host. There are 3 types of FTP that are supported - standard, SFTP, and SSL. If your NonStop Host is Default port: 21 30

33 Services Available TACL OSS Other Command Prompt configured to use one of those options, pick the selection that matches your host. The default value for this application is standard. This is unsecured FTP. SFTP is normally part of SSH2 and will normally use the same port as the SSH2 port. SFTP provides greater security when communicating between your PC and the NonStop. SSL is another secure protocol. But, whatever option you choose, it has to match the configuration on your NonStop. Selecting the radio button will enable TACL service to be used to logon to the host. Selecting the radio button will enable OSS service to be used to logon to the host. Selecting the radio button will enable you to specify any other service for logging on to the host. To specify a customized command prompt string displayed after logon. The Other field is provided in case you have a different service name for the standard OSS or TACL Logon services. The Host Installation Client only provides support for installation using the standard services; TACL or OSS. If you enter a service, which is neither of TACL or OSS type in the Other box, the installation will not be successful. If you select Other as the service to logon and do not specify the service to be used in the corresponding box, it will be considered a valid entry and a carriage return will be used for the Service name while logging on to the HPE NonStop host. Default: DEFAULT 31

34 3. Click the Show Advanced Options button to access and configure advanced communication parameters. These additional IP addresses and ports will be used if the primary IP and ports fail. In addition, if you use Xypro (or a similar product) and do not have direct access to the user id that is used by OVNM, you can specify the Xypro command (and optional password) on this page as well. Figure 17. Communication Tab Page Advanced Communication Information 4. Specify the following information. a. If you use Xypro (or something similar that requires another logon or special command) you can enter that command and optional password into the Command and Password boxes. If the Secondary Tacl Prompt is not going to be 1, you can also change that so the HIC knows when the login sequence is complete. b. Console and Enterprise Solution Information: Select the various check boxes and specify the corresponding IP Address (or DNS name), TCPIP Process name, and Port number in the fields available for the Console and Enterprise solution. c. OCC, ObjectMap and ObjectStats Information: Select the various check boxes and specify the corresponding IP Address (or DNS name), TCPIP Process name and Port number in the fields available for OCC, ObjectMAP, and ObjectStats. 5. Click the Back button. 32

35 Policies Tab Page To add default OVNM policies to the HPE NonStop Server, perform the following steps. 1. Click the Policies tab. The Policies tab page is displayed. Figure 18. New OVNM Configuration Policies Tab Page 2. In the Policies tab page, specify the information as described in the following table. Table 4. Policies Parameters Area Parameter Name Description Additional Information Policies Add Default Policies Select the Add Default Policies check box to install the OVNM Object Monitoring policies. The policies will be added ONLY if this is an initial install. Default Policies are NOT added during an upgrade. For details on the policies, refer to the object reference guide. Default port: Selected If the check box is NOT selected, all the NonStop Server EMS events logged to the Collectors defined to OVNM will be passed to the Enterprise product. EMS Event Processing Only forward user defined Enterprise Events (eevents) messages This check box allows you to decide if you want every single EMS message sent to the Enterprise Management system or only the EMS messages that correspond to an EMS threshold defined in OCC and you have not selected Disable Events in the Object Configuration Client eevents panel. 33

36 Mail Tab Page To configure the facility on the HPE NonStop Server, perform the following steps. 1. Click the Mail tab. The Mail tab page is displayed. Figure 19. New OVNM Configuration Mail Tab Page 2. Select the Allow Mail check box to enable the fields. 34

37 3. In the displayed fields, specify the information as described in the following table. Table 5. Parameters Area Parameter Name Description Additional Information Mail NonStop IP To specify the IP address of the NonStop Server that will have access to the Server. In many cases, the NonStop IP address is the same as the IP used for the connection between the front-end and the backend. If this IP address is blocked from accessing the Server, specify a different IP address to be used as the NonStop IP. Server IP To specify the IP address of the Server that will receive the for delivery. Port The port number to be used by the Server. Default: 25 Sender ID The sender ID. Sender ID is the ID you want associated as the sender of the s generated by OVNM. Sometimes, the server requires that this ID exist in its address book. In this case, you will have to use an existing ID or create a new one specifically for OVNM. Trace Queue Read Interval Giveup Interval Retry Interval Log Sent Log Fail Log GiveUp The following options are available for configuring the Tracing. Error: To log in case of failure None: No logging Progress: For logging all the messages To specify how often the host application is to pick up queued mails. To specify the duration, in minutes, after which the host application will stop trying to send the and delete it from the queue. To specify the retry interval. The retry interval is the interval after which the application tries to resend the mail if it failed the last time. To specify whether or not you want EMS messages to be generated whenever an is sent. To specify whether or not you want EMS messages to be generated whenever an is not successfully sent. To specify whether or not you want EMS messages to be generated whenever an has not been able to be sent before the GiveUp Interval has been exceeded. The mail trace logfile is <\NODENAME>.<$INSTALLVOL>.OVNM.MA ILLOG. Range: seconds Default: 30 seconds Range: minutes Default: 120 minutes Range: seconds Default: 300 seconds Yes or No Default: No Yes or No Default: No Yes or No Default: No 35

38 Distributor Tab Page To configure HPE NonStop distributors and collectors and filters associated with them, perform the following steps. 1. Click the Distributor tab. The Distributor tab page is displayed. Figure 20. New OVNM Configuration Distributor Tab Page The distributor and its corresponding collectors and filters defined in the Distributor panel is used by the EMON process ($OVEMN). This portion of OVNM is responsible for sending messages to the Enterprise Management System as well as the OVNM Console application. There are two default distributors DIST01 and DIST02. The collectors and filters for DIST01 are $0 and $SYSTEM.OVNM.PASSALL. The PASSALL filter passes all the events generated on the HPE NonStop system. For DIST02, the corresponding collectors and filters are $ZLOG and $SYSTEM.OVNM.ZTSMFLTR. The ZTSMFLTR filter passes all the events for the TANDEM.TSM and TANDEM.SPR subsystems generated on the HPE NonStop system. Additional Distributors and Filters can be configured if you have applications that log to other EMS collectors and you want these messages sent to OVNM s Console and/or your Enterprise Management System. 36

39 2. To add a Distributor, specify the information as described in the following table. Table 6. Adding Distributors Parameters Area Parameter Name Description Additional Information Distributor Distributor(s) Use the Distributor(s) drop-down list to select a distributor to be added. Name Process Name Suffix CPU Priority Collector(s) Filter(s) Specify the name for the distributor selected in the Distributor(s) box. The field is populated with the default name. You can either use the default name or specify a custom name. Specify the process name suffix for the distributor process. The field is populated with the default suffix. You can either use the default suffix or specify a custom one. Use the CPU spin box to specify the CPU on which the distributor process will run. The Priority box can be used to specify the priority of the distributor process. Configure collectors associated with the selected distributor using the Collector(s) box. Configure filters associated with the selected distributor using the Filter(s) box. The option is disabled by default. Selecting the check box enables other fields on the tab page. Distributor names cannot be duplicated within OVNM or within OCC, but they can be duplicated within the two. Process names cannot be duplicated either ways. The distributor name as specified in the Name field can be the same as that for OCC. Hyphens and underscores are acceptable characters. The distributor process name will start with the prefix, which was specified in the OVNM Configuration tab page, followed by the suffix specified in the Process Name Suffix field. The process name suffix for a distributor for OVNM cannot be same as the process name of a distributor for OCC. By default this is the same as the Primary CPU specified for the main OVNM process on the OVNM Configuration tab page. By default the value is 10 less than the priority specified for the main OVNM process on the OVNM tab page. You can specify up to ten collectors for a distributor using comma separators. You can specify up to ten filters for a distributor using comma separators. The default location for the filters is the same as the OVNM Volume.Subvolume. 3. After specifying all the information, click the Add button. After successful addition, the new entry is added to the Distributor list. 4. To modify the information for a distributor, select the Distributor from the list, make the necessary changes and click the Modify button. 5. To delete a distributor, select it in the Distributor list, and click the Delete button. This removes the distributor from the list. WARNING! For proper functioning of OVNM, it is recommended that the default distributors are not deleted. If you use an alternate collector for the Log To Collector in the Host tab page, then another default distributor will automatically be added to the Distributor and the OCC configuration that will consume events from the collector. 37

40 OCC Tab Page 1. Click the OCC tab to configure the distributors and filters to be used by the monitoring portion of OVNM. The OCC tab page is displayed. Figure 21. New OVNM Configuration OCC Tab Page The distributor and its corresponding collectors and filters defined in the OCC Distributors area is used by the OCC process ($OVOCC). This portion of OVNM is responsible for the monitoring of the objects as well as consuming events that are defined as EMS thresholds. There are two default OCC distributors, DIST01 and DIST02. The collectors and filters for DIST01 are $0 and $SYSTEM.OVNM.PASSALL. The PASSALL filter is used by OVNM for event correlation and should not be modified. For DIST02, the corresponding collectors and filters are $ZLOG and $SYSTEM.OVNM.ZTSMFLTR. The ZTSMFLTR passes all the events for the TANDEM.TSM and TANDEM.SPR subsystems generated on the HPE NonStop system. Additional Distributors and Filters can be configured if you have applications that log to other EMS collectors and you want to define EMS thresholds against them. 38

41 Plug-Ins Tab Page 1. Click the Plug-Ins tab. The Plug-Ins tab page is displayed. The information in this tab page is optional and is intended for OVNM Plug-In support. Figure 22. New OVNM Configuration Plug-Ins Tab Page 39

42 EMS Template Tab Page To configure for EMS template files, perform the following steps. 1. Click the EMS Template tab. The EMS Template tab page is displayed. Figure 23. New OVNM Configuration EMS Template Tab Page You can use a standard EMS template file, which is the default option, or use a user-defined EMS template file. 2. The Use Standard EMS Template check box is selected by default. To use a user-defined template, clear the check box. Specify the location of template file in the EMS Template File location in the $<volume>.<subvolume>.<templatefile> format and click the Add button. 3. You can add a maximum of ten template files. The files added will be displayed in the User Defined EMS Template Files list. To remove a file from the list, select the file from the list and click the Delete button. Use the Modify button. 40

43 BASE24 Tab Page To configure BASE24 options for OVNM, perform the following steps. 1. Click the BASE24 tab. The BASE24 tab page is displayed. Figure 24. New OVNM Configuration BASE24 Tab Page 41

44 2. In the BASE24 tab page, specify the information as described in the following table. Table 7. BASE24 Parameters Area Parameter Name Description Additional Information BASE24 BASE24 Monitoring Select the BASE24 Monitoring check box if the BASE24 Plug-In is already installed on the system. Selecting the check box will allow the addition of BASE24 distributor to the OCC page and start the processing of BASE24 events. Selecting the check box enables other fields in the tab page. Deselecting the option will after activating BASE24 monitoring will lead to removal of the BASE24 distributor from the OCC tab page and the processing of the BASE24 events would cease. Close TDF The Close TDF check box is used to specify whether OVNM will open the TDF file to read the process thresholds anytime or only when necessary, that is, when the polling interval expires. To open the TDF file only when necessary, select the Close TDF check box. BASE24 Options Use the BASE24 Options drop-down list to specify the load balancing options. Use only 1 CPU for all objects: To single-thread the BASE24 monitoring through a single connection to the BASE24 environment. This option is selected by default. Distribute objects across all CPUs: To distribute all objects across all CPUs resulting in multiple opens to the BASE24 environment, but better load balancing. ListObjects in 1 CPU, others across all CPUs: To place the objects to be monitored via the ListObject command into a single CPU, but balance the other objects across the available CPUs. It is HIGHLY recommended that you select the use only 1 CPU option. This reduces the concurrent messages that OVNM would send to XPNET if you allow it to spread the objects across CPUs. Use LISTOBJECTS for BASE24 OVNM also provides check boxes for selecting the ListObjects command for monitoring instead of the Status command. Use the check boxes in the Use LISTOBJECTS for BASE24 area to select the BASE24 objects to be monitored via the ListObjects command. In some cases, using ListObjects command is more efficient. It is HIGHLY recommended that you do NOT select any of the Listobjects options. The default method that OVNM uses to communicate with BASE24 has been shown to be more efficient than using ListObjects commands. 42

45 Enterprise Tab Page To configure other OVNM options, perform the following steps. 1. Click the Enterprise tab. The Enterprise tab page is displayed. Figure 25. New OVNM Configuration Enterprise Tab Page NOTE: This panel is ONLY to be used when you have OVNM installed with Enterprise Manager like HPE OM in a WINDOWS environment. 2. Select the NonStop Event Message Format from the drop-down list. 3. Select the Fault Tolerance Enabled check box for guaranteed delivery of NonStop Server events for the following Enterprise management Server Configurations. Single Enterprise Management Server (Configured as Primary): In the event of a connection failure between an OVNM Agent on the HPE NonStop managed server and the Enterprise Management Server, any NonStop events occurring during the connection failure will be resent to the Enterprise Management Server after communication is restored. Events are resent using OVNM s message queuing facility. For details, refer to the OVNM users guide. Dual Enterprise Management Servers (One Primary and other Backup): In this configuration, OVNM sends HPE NonStop events to the Primary Enterprise Management Server. In the event of a connection failure between OVNM on the NonStop Server and the Primary Enterprise Management Server, OVNM will redirect events to the Backup Enterprise Management Server. If connection failure occurs with both the Enterprise Management Servers, any NonStop events occurring during the connection failure will be resent to the Enterprise Management Server after communication is restored. By default, the Fault Tolerance feature is disabled, that means that OVNM is configured to broadcast NonStop events to all available Enterprise Management Servers and will not provide event message queuing. Select the Fault Tolerance Enabled check box to enable the feature. 4. Select the Enterprise Management Server to receive NonStop Events from the drop-down list. This drop-down list is enabled only when the Fault Tolerance Enabled check box is selected. 43

46 MQ Series Tab Page To configure MQ Series Plug-in options for OVNM, perform the following steps. 1. Click the MQ Series tab. The MQ Series tab page is displayed. Figure 26. New OVNM Configuration MQ Series Tab Page 2. This panel is used to define the various MQ environments that are going to be monitored by OVNM. NOTE: This panel is ONLY to be used if you are going to use OVNM to monitor your MQ environment(s). 3. Specify the information in the displayed fields, as described in the following table. Figure 27. MQ Series Parameters Area Parameter Name Description Additional Information MQ Series Config Name Used to provide a very short name to the environment Maximum 8 characters allowed CPU Priority INI Filename Obey Fielname Specify the CPU that you want to use for the monitor program (MQSVR53) for this MQ environment Set the priority of the monitor program (MQSVR53) Specify the INI file that is associated with this particular MQ environment. Specify the name of an Obey file that will be executed by the STRTMQ job prior to running the MQSVR53 program. The PARAMs that get loaded by this Obey file are the PARAMs required by the MQ environment. 4. Once you have entered the necessary data, click the Add button. 5. Repeat that process for each MQ environment you want to monitor. You can add up to 20 configurations. 44

47 6. Once you have completed all the configurations, click the Install button in the New OVNM Configuration dialog box to start installing OVNM on the HPE NonStop host. Figure 28. New OVNM Configuration Dialog Box Perform any of the following steps. a. To revert to the default field values, click the Reset Fields button. b. To close the dialog box without saving the information, click the Cancel button. c. To add the configurations to the workstation, click the Add To Workstation button. In this case, no operation occurs on the HPE NonStop Host. The Add To Workstation button can be used in case you lose the configuration or deleted a node from the workstation without deleting it from the HPE NonStop Host. In that case, just add that configuration once again to the workstation. 7. Click the Install button. This displays multiple confirmation pages depending upon the information given while configuring. If the Volume.Subvolume for some of the filter files is not the same as the OVNM Volume.Subvolume, the OVNM Host Installation Client confirmation box is displayed. Figure 29. OVNM Host Installation Client Confirmation Box 8. Click the OK button. The OVNM Host Response for Installation dialog box displays the information about the status of the installation process. 45

48 After the installation is complete, the OVNM Host Installation Client confirmation box is displayed with the option to start the backend on the specified host. Figure 30. OVNM Host Installation Client Confirmation Box 9. Click the Yes button to start the backend. If you don t want to start the process right now, click the No button. To start the OVNM backend at any later time, click the Start Agent button in the Host Management Client window. The OVNM Host Response for Installation dialog box is displayed again with the message that the installation is completed. Figure 31. OVNM Host Response for Installation Installation Complete 10. Click the Save button. To close the box after completion of the installation process, click the OK button. WARNING! The OVNM Host Installation Client dialog box is displayed again after closing the OVNM Host Response for Installation dialog box. The Operations Manager policies will only be loaded on the Operations Management server when you click the Close button to exit OVNM Host Installation Client. This ONLY happens when you are installing OVNM on the HPE OM server. 46

49 4 Upgrading OVNM on HPE NonStop Server Considerations while Upgrading OVNM It is not mandatory to initially upgrade all NonStop Servers to the latest release. Operation Manager Servers can manage NonStop Servers running either OVNM 4.x or OVNM 5.x Agents. There are, however, new features and functions that are only supported on NonStop Servers running OVNM 5.x Agents. Object Configuration Client The following figure illustrates the Object Configuration Client Interface. Figure 32. OVNM Object Configuration Client Interface OVNM 5.x release introduced the following new features that are not supported on NonStop Servers running OVNM 4.x or earlier versions. Automated Action: In addition to the ability to specify user-written TACL routines to execute, OVNM 5.x provides the ability to use pre-canned recoveries for many of the thresholds. Most of these recoveries will use a SPI interface instead of TACL code to perform the recovery. EMS Burst Suppression: The new EMS burst suppression (part of OCC) cannot be used with an old backend as the code only exists in version 5.x. Add Object to an Existing Threshold: Use of this feature should be limited to 5.x environments only since the structure of the message has changed significantly to support wildcards and manager name data. OCC will not send the request of wildcard objects to the old backend. DNS support: Versions of OVNM prior to 5.x will not support DNS names, so you will still need to use actual IP addresses in the Host Installation Client for those environments. Multiple Backend Environments on a Single HPE NonStop: Multiple OVNM Nonstop Host Agent environments on a single HPE NonStop. New Object Threshold When adding new thresholds, OVNM will not allow you to enter the thresholds that are not supported by the version of the backend that is currently installed on that particular HPE NonStop. If you want to see what the new thresholds are, review the softdocs and/or Release Notes. Limitations while working with thresholds that were added in the previous release and are no longer supported by 5.x. 47

50 The thresholds created with OVNM 4.x that have been deleted in 5.x will show Threshold Name as Unknown in the Threshold pane of the OVNM Object Configuration Client. Modification of thresholds and objects will not be possible, but these can be deleted. 48

51 Upgrading OVNM The Upgrade Release option in the OVNM Host Installation Client Upgrade menu allows you to perform a full software release upgrade. To perform a full software upgrade, perform the following steps. 1. In Host Installation Client, click the Upgrade button. The Upgrade Menu is displayed. Figure 33. Upgrade Release Option in Upgrade Menu 2. Click the Upgrade Release option. The Login to Host dialog box is displayed. Figure 34. Login to Host Dialog Box 3. Enter the User Name and Password in the Login to Host dialog box and click the OK button to initiate the upgrade process. If you use Xypro (or something similar that requires another logon or special command) you can enter that command and optional password into the Secondary Command and Secondary Password boxes. If the Secondary Tacl Prompt is not going to be 1, you can also change that so the HIC knows when the login sequence is complete. 49

52 The OVNM Host Response for Upgrade Release dialog box is displayed showing the response of the operations carried on the NonStop Host. During the upgrade process on the NonStop Host, the OVNM Host Installation Client confirmation box is displayed. Figure 35. OVNM Host Response for Upgrade Release 4. Click the Yes button, if you want to run OVNM on the specified Node. This will start OVNM agents on the HPE NonStop Server. The upgrade procedure completes with the status that the release upgrade is successful. Click the Save button to save the response in the form of a text file. To close the dialog box, click the OK button. Figure 36. OVNM Host Response for Upgrade Release Dialog Box This completes the upgrade of OVNM on a HPE NonStop Server. 50

53 5 Installing OVNM on HPE OM UNIX Introduction This chapter describes how to install HPE OVNM for the first time on the HPE Operations Manager (HPE OM) UNIX Management Server. To upgrade from an earlier OVNM version, refer to the Upgrading OVNM to a Newer Version section. Overview of Steps for Installing and Configuring OVNM on HPE OM UNIX Server 1. FTP the appropriated OVNM depot.tar file from the HPE OVNM product CD to the UNIX Server. Refer to the Obtaining The Appropriate OVNM Depot.Tar File section. 2. Install OVNM software using the swinstall utility (non-interactive). Refer to the Non Interactive Installation section. 3. Configure OVNM. Refer to the Configuring OVNM on HPE OM UNIX section. 4. Deploy the NonStop Server policies on to HPE OM Server and assign the responsibilities to the users for NonStop messages using the HPE OM opc utility. Refer to the Configuring the HPE OM Environment section for details. Installing OVNM on HPE OM UNIX Obtaining the Appropriate OVNM Depot.tar File The following OVNM installation files are located in the HPE OVNM product CD in the OVNM for UNIX directory. Table 8. OVNM Installation Files Installation File ovnm_hpux_itanium_depot.tar ovnm_linux.tar.gz Version HPUX Integrity (*Itanium) 11i v3 (OMU 9.x) Linux Red Hat Enterprise Linux5.5 FTP the appropriate depot tar file from the Windows PC to a temporary location on the UNIX Server. NOTE: The /var/spool/sw directory will be used as the Depot Location in all examples in this Chapter. 51

54 OVNM Installation Getting Started 1. Logon to the HPE Operations Management Server as root user and switch to the directory where the Depot tar file was FTPed. # cd /var/spool/sw 2. Extract the resulting tar file. #tar xvf depot.tar NOTE: If HPE OM (VPO) Server being used supports Japanese language support, OVNM configuration file ovnm-cfg.idx needs to be modified. To configure OVNM for the Japanese environment, edit the section: /OVNM-HPUX/OVNM-CONF-FILES/var/opt/OV/share/tmp/OpC_appl/ovnm/conf/C/ovnm-cfg.idx Locate and change CHARACTER_SET ISO88591 To CHARACTER_SET SJIS 3. Next, register the temporary path as a depot path. # swreg -l depot /var/spool/sw 4. By default the OVNM SPI components are installed in the /opt/ov/ directory. There may be times when a different installation directory is desired, for example when installing OVNM on an HPE UX cluster, the OVNM SPI components should be installed in the OV share directory: /var/opt/ov/share. Refer to Appendix E: HPE MC/SG Cluster Installation Supplement for more information. To change the directory where OVNM is to be installed, execute the following script before performing the installation procedure. # /var/spool/sw/custom_install.sh Non-Interactive Installation Start the non-interactive installation process by using the following command. # swinstall -s <OVNM-DEPOT-LOCATION> OVNM For example, # swinstall -s /var/spool/sw OVNM The installation completes with the display of messages. NOTE: Before continuing, verify that the swinstall completed successfully. Please refer to Appendix C: Sample Installation Session on HPE OM HPUX for sample sessions. 52

55 Configuring OVNM on HPE OM UNIX The following procedure is used to configure the HPE NonStop Nodes the OVNM SPI will be communicating with. It is assumed at this point that the NonStop Nodes being configured already has an OVNM Agent installed. For a sample session, refer to Appendix D: Sample OVNM Configuration on HPE OM UNIX. 1. Change the working directory to /opt/ov/ovnm/bin where the script and binary files have been copied by default, after the installation. # pwd # cd /opt/ov/ovnm/bin 2. Execute the following script to initiate the configuration process. #./ovnm_configure.sh NOTE: Make sure your locale is set to C before running ovnm_configure.sh. 3. Enter the port number (above 5000) for NonStop Alerts reception. The default port is Enter the fully qualified name of the HPE NonStop Node. For example, NODE.domain.com. NODE.HPE.com 5. Enter the IP Address for the specified HPE NonStop node The system checks the name resolution for the specified node and the following message is displayed. Checking the name resolution. This can take a few minutes. Please be patient... The steps for name resolution will be different for HPE UX and SUN SOLARIS. NOTE: Support for Solaris and HP UX PA-RISC is discontinued for OVNM 5.3 release onwards. HPE UX a. Name Resolution Successful: In case the name resolution is successful, the script adds the node to the HPE OM configuration and continues with the process of configuration with the following message. Successfully resolved the nodename. Continuing... b. Name Resolution Failed: In case the name resolution fails, the script checks for the existence of the name resolution method: DNS or Files. If the script finds DNS as the name resolution method, it instructs the user to add an entry in the DNS for the HPE NonStop node and restart the script. Name resolution for NODE.HPE.com failed. Please define an entry for this node in your DNS records and rerun this script. If the script finds Files(hosts) as the name resolution method, it automatically adds the HPE NonStop node to the hosts file and continues with the operation. Name resolution for NODE.HPE.com failed. Adding the node entry in the hosts file.. If the script is unable to find the name resolution method, it will prompt to choose a method of resolution from DNS or Files. If the user chooses DNS the script instructs to add an entry in the DNS for the node and restart the operation. If the user chooses Files the script adds the entry in the hosts file and continues. Name resolution for NODE.HPE.com failed. Not able to determine the method of name resolution used. Please specify the name resolution scheme which you are using, from: 1) DNS 2) files 53

56 SUN SOLARIS NOTE: Support for Solaris and HP UX PA-RISC is discontinued for OVNM 5.3 release onwards. a. Name Resolution Successful: In case the name resolution is successful, the script adds the node to the HPE OM configuration and continues with the process of configuration with the following message. Successfully resolved the nodename. Continuing... b. Name Resolution Failed: In case the name resolution fails, it will prompt to choose a method of resolution from DNS or Files. If the user chooses DNS the script instructs to add an entry in the DNS for the node and restart the operation. If the user chooses Files the script adds the entry in the hosts file and continues. Name resolution for NODE.HPE.com failed. Not able to determine the method of name resolution used. Please specify the name resolution scheme which you are using, from: 1) DNS 2) files 7. Enter the label of the HPE NonStop node that you want to be displayed in HPE OM. \NODE 8. Enter the port for NonStop Alerts on the specified node. The default port is OVNM can be configured to support one or more HPE Operations Management Servers. You can configure OVNM to support a pair of HPE OM Management Servers as primary, backup or broadcast. For details, refer to the OVNM users guide. Specify the HPE OM Management server as Primary, Backup or broadcast server. Enter 1 for primary, 2 for backup and 3 for broadcast. 1 Once the required information is entered correctly the following message is displayed. Adding \NODE node to the NonStop-Server node group bank as IP node Operation successfully completed. Adding \NODE service map and assigning it to opc_adm user... Successfully added service file file: /opt/ov/ovnm/bin/service_file2.xml (SVC10-111) Successfully assigned services to operator opc_adm (SVC10-113) Successfully assigned services to operator opc_adm (SVC10-113) 10. The system confirms if you want to add another node. To configure another node, type Y, otherwise type N. N 11. The system confirms if u want to auto start OVNM at system reboot. To add OVNM at startup, type Y, otherwise type N. Y The will display the following message. Adding OVNM at Startup Added OVNM at system startup successfully. This completes the OVNM configuration portion of the installation. A successful configuration will display the following message. OVNM is successfully configured. Deploy the NonStop Server policies on to OVO Server and assign the responsibilities to the users for NonStop messages. 54

57 Configuring the HPE OM Environment The following section describes the configuration of the HPE OM environment in HPE OM 8 and HPE OM9. NOTE: HPE OM8 support is discontinued OVNM 5.3.x onwards, and you can no longer get extended support. ONLY HPE OM 9 will be supported. Configuring the HPE OM8 Environment The HPE OM opc program will be used to configure the HPE NonStop Server templates, and assign HPE OM users responsibilities. The NonStop Server icon is added to the OVO Node Bank Group after OVNM installation. Perform the following tasks to configure the HPE OM environment. Assign HPE NonStop Server Template Group Deploy HPE NonStop Server Template Group Set User Responsibilities and Applications NOTE: The opc program requires a User ID and Password. Please acquire them from the HPE OM Administrator. Assign HPE NonStop Server Template Group To deploy a template group, perform the following steps. 1. Open the OVO Node Bank window by selecting the Window menu and clicking the Node Bank option. Figure 37. OVO Node Bank Window 55

58 2. Select the Agents submenu in the Actions menu. In the displayed Agents menu, click the Assign Templates option. Figure 38. OVO Node Bank Actions Agents - Assign Templates Option 3. The Define Configuration window is displayed. Figure 39. Define Configuration Window 4. Click the Add button to add the HPE NonStop Server group template. 5. In the OVO Node Bank window, select the Management Server icon with a single mouse click. 6. Clicking the Add button in the Define Configuration window displays the Add Configuration window. Click the Get Map Selections button to add the Management server. The Management server is added to the Nodes/Groups list box. Figure 40. Add Configuration Window 56

59 7. Click the Open Template Window button in the Add Configuration window. The Message Source Templates window is displayed. Select the Group HPE NonStop Server template on the right-hand-side of the window. Figure 41. Message Source Templates Window with Group HPE NonStop Server Template Selected 8. Move to the Add Configuration window and click the Get Template Selections button to add the Group HPE NonStop Server template to the Templates box. Figure 42. Add Configuration Window with the Group HPE NonStop Server Template 9. Close the Add Configuration window by clicking the OK button. To close the Message Source Templates window, click the Close Window option in the Templates menu. 10. The Define Configuration window displays the HPE NonStop Server template. Click the OK button to close the window. Figure 43. Define Configuration Window with the Group HPE NonStop Server Template This completes the procedure for assigning HPE NonStop Server templates. 57

60 Deploy HPE NonStop Server Template Group Once the HPE NonStop Server templates have been assigned, they have to be distributed to the managed nodes. To distribute the managed nodes by using the Install / Update OVO Software and Configuration window, perform the following steps. 1. In the OVO Node Bank window, select the Management Server. As an example we have selected SUNMAC. Figure 44. OVO Node Bank Window 2. Select the Install / Update SW & Config menu option in the OVO Node Bank Actions/Agents menu. Figure 45. OVO Node Bank Actions Agents - Install / Update SW & Config Option 58

61 3. The Install / Update OVO Software and Configuration window is displayed. Select the Templates and Nodes in list requiring update options. Figure 46. Install / Update OVO Software and Configuration Window 4. In the OVO Node Bank window, select the Management Server with a single mouse click. 5. In the Install / Update OVO Software Configuration window, add the Management Server by clicking the Get Map Selections button. Figure 47. Install / Update OVO Software and Configuration Window with the Management Server 6. Click the OK button to close the window. 7. Open the Message Browser window using the Message Browser option in the OVO Node Bank Window menu and check for successful installation messages. Figure 48. Message Browser 59

62 Assign User Responsibilities and Applications This step is very important and if you do not configure responsibilities and applications for a user, the user would not be able to view the NonStop messages and launch NonStop applications. 1. To assign responsibilities and applications for a user, open the OVO Node Bank window and select the User Bank option in the Window menu. Figure 49. OVO Node Bank - User Bank Option 2. The OVO User Bank window is displayed. Right-click opc_adm or any other user you want to set responsibilities and applications for and click the Modify option in the displayed menu. Figure 50. OVO User Bank Modify Option 60

63 3. The Modify User window for the selected user is displayed. Enter the User Name and Password, if required, and click the Responsibilities button. Figure 51. Modify User Window 4. The Responsibilities for Operator window is displayed. Click the NonStop-Server node group column button. This will enable all the check boxes under the NonStop-Server column. Next, click the NonStop message group row button, which will enable all the check boxes for the NonStop Message Group row. Click the Close button. Figure 52. Responsibilities for Operator Window 61

64 5. Click the Applications button on the Modify User dialog box to assign application to the user. The Applications of User submap is displayed. Figure 53. Applications of User Submap 6. Click the Application Bank option in the Window menu. Figure 54. Applications of User Submap Window Application Bank Option 62

65 7. The OVO Application Bank window is displayed. To assign NonStop applications to the user, drag the NonStop Tools icon from the OVO Application Bank window to the Application of User window. Figure 55. Application of User and OVO Application Bank Windows 8. The NonStop Tools icon is added to the Application of User window. NonStop tools have now been assigned to the user. Figure 56. Application of User Window with NonStop Tools 9. Click the OK button in the Modify User window to apply the changes. 63

66 Configuring the HPE OM9 Environment The OM 9 UNIX Administration UI will be used to configure the HPE NonStop Server templates, and assign HPE OM9 users responsibilities. The NonStop Server icon is added to the HPE OM Node Bank Group after OVNM installation. To configure the HPE OM9 environment, perform the following steps. Assign HPE NonStop Server Template Group Deploy HPE NonStop Server Template Group Set User Responsibilities and Applications NOTE: The opc program requires a User ID and Password. Please acquire them from the HPE OM Administrator. Assign HPE NonStop Server Template Group To assign HPE NonStop Server Template Group, perform the following steps. 1. In the OMU window, click the Node Bank link in the Object Banks area. Figure 57. OMU Window 64

67 The Node Bank page is displayed. Figure 58. Node Bank Page 2. Click the icon. Click the Assign Policies/Policy Groups item in the Actions menu. Figure 59. Node Bank Page Assign Policies/Policy Group Option 65

68 3. The Selector dialog box is displayed. Select the HPE NonStop Server option. Figure 60. HPE OM Node Bank Page 66

69 Deploying HPE NonStop Server Template Group After you have assigned the HPE NonStop Server templates/policies, you have to distribute these policies/templates to the managed nodes. To distribute these policies/templates, perform the following steps. 1. In the HPE OM Node Bank window, select the Node (BMC062) and click the icon. Figure 61. OVO Node Bank Actions Menu Deploy Configuration 2. In the Actions menu, click the Deploy Configuration item. The Deploy Configuration dialog box is displayed. Select the following checkboxes. Distribute Policies Distribute Actions Distribute Monitors Distribute Commands Distribute Instrumentation Figure 62. Deploy Configuration Dialog Box 3. Click the Ok button to close the dialog box. 67

70 Assign User Responsibilities and Tools/Applications To assign responsibilities and Tools/applications for a user, perform the following steps. 1. In the HPE OM Node Bank window, click the All Users item in the Browse menu. Figure 63. HPE OM Node Bank Window Browse Menu 2. The HPE OM All Users window is displayed. Select the opc_adm or any other user, for which you want to set responsibilities and tools/application. Click the icon and click the Assign Tools item in the Actions menu. Figure 64. HPE OM All Users Window 68

71 3. The Selector dialog box is displayed. Click the Tool Bank link and select the NonStop Tools option from the list. Figure 65. Selector Dialog Box Tool Bank List 4. Click the Ok button to save your changes. 5. Click the icon, and click the Edit Responsibilities item in the Actions menu. Figure 66. All Users Window Actions Menu 69

72 6. The Edit Responsibilities for User window is displayed. By default the Node Group and Message group does not contains the NonStop Server. Click the Edit View button and select the NonStop-Server Node Group and NonStop Message Group option in the Edit Matrix View dialog box. Click the Ok button. Figure 67. Edit Responsibilities for User Window 7. Click the Node Group column button to select all the check boxes in the NonStop-Server column. Click the Message Group row button to select all the check boxes in the NonStop Message Group row. Figure 68. Edit Responsibilities for User Window Node and Message Groups 8. Click the Save button to save the changes. 70

73 Starting OVNM on HPE OM UNIX After Installing OVNM and configuring the environment, use the following command to start the OVNM Agents on the OVNM UNIX Management Server. # /opt/ov/ovnm/bin/ovnm_start.sh Note the ovnm_start.sh file is used to start the ovnm_spi process. In order to alter the run-time parameters of the OVNM agents, you can use the ovnm_spi binary. #./ovnm_spi help Usage: OVNM_SPI -logfile -trace <filename> trace messages to the specified file. Default file is stderr -diagnose To generate diagnostic file. -node Set incoming node name during OVO message logging -alive <value> How often to check that elink is alive (Default is 180 seconds) -count <value> How many messages to generate if elink is down or hung (Default is 3) -maxgobacknumseconds <value> Maximum no of seconds to go back during message queuing (Default is seconds) -msgqueuing Enables message queuing feature (Default is OFF) -logfilelen <number-of-bytes> Set logfile size (Default is 5MB) -internalmsg <ON OFF> Enables send internal message to OVO feature (Default is ON) -internalmsgseverity < NORMAL WARNING MINOR MAJOR CRITICAL > Set severity of internal messages (Default is CRITICAL) -agent To check if OVO agent is running or not before sending messages to OVO. -catchuptimeout <value> How many seconds to wait for catchup messages. Default is 120 seconds. -ovomonitoringinterval <value> How often to monitor OVO agent/server. Default is 10 seconds. -ovnmmode311 <ON OFF> Enable or disable the OVNM mode 311. Default is OFF. Once the OVNM agents are started, you can follow the procedure listed in the Testing OVNM and HPE OM Integration section to test the integration. In case you need to stop OVNM Agents on the HPE OM Management Server, use the following command. # /opt/ov/ovnm/bin/ovnm_stop.sh 71

74 Testing OVNM and HPE OM Integration The following procedure will generate a test EMS event using the ITO user interface. Once generated, OVNM will process the message and send it to HPE OM and be displayed in the Message Browser. You can send a test message using the Test Message tool. NOTE: The procedure assumes that OVNM is running on the HPE NonStop Server, which will generate the EMS event. To execute the Test Message application from the ITO user interface, perform the following steps. 1. Right-Click the node on which the OVNM-HPE OM integration is to be tested and select the Start/NonStop Tools/ OVNM Tools menu option. 2. In the displayed menu, select the Test Message tool. Figure 69. NonStop Tools Test Message Tool 72

75 The output is displayed in the Test Message Output window. Figure 70. Test Message Output Window You can view the HPE OM Message Browser and the HPE OM Service view for the following message *** 999: OVNM: communication test was successful (Event Message Text) *** You can also perform the above function using the OPC User Interface. Select a node and then drop it over the Test Message tool or just select the node and then double-click the tool. NOTE: The initial message processed will cause OVNM to initialize the Event Management components, so please wait up to 1 minute for the initial messages to be processed. Subsequent events should be processed immediately. 73

76 Upgrading OVNM on HPE OM UNIX The following OVNM installation files are located in the OVNM for UNIX directory of the HPE OVNM product CD. Table 9. OVNM Installation Files Installation File ovnm_hpux-itanium_depot.tar Version HPUX Integrity (Itanium) 11i v2 (OM 8.x) To upgrade OVNM on HPE OM UNIX, perform the following steps. 1. FTP the appropriate depot tar file from the Windows PC to a temporary location on the UNIX Server. 2. Stop OVNM Agents on the HPE OM Management Server, use the following command. 3. # /opt/ov/ovnm/bin/ovnm_stop.shlogon as root user and switch to the directory where the Depot tar file was FTPed. # cd /var/spool/sw 4. Extract the resulting tar file. #tar xvf depot.tar 5. Next, register the temporary path as a depot path. # swreg -l depot /var/spool/sw 6. By default the OVNM SPI components are installed in the /opt/ov/ directory. There may be times when a different installation directory is desired, for example when installing OVNM on an HPE UX cluster, the OVNM SPI components should be installed in the OV share directory: /var/opt/ov/share. Refer to Appendix E: MC/SG Cluster Installation Supplement for more information. To change the directory where OVNM is to be installed, execute the following script before performing the installation procedure. # /var/spool/sw/custom_install.sh Refer to notes in the shell script for details. 7. Use the following command to start the installation process. # swinstall -s <OVNM-DEPOT-LOCATION> OVNM For example: # swinstall -s /var/spool/sw OVNM NOTE: It is recommended to verify that the swinstall completed successfully before continuing. 8. Use the following command to start the OVNM Agents on the OVNM UNIX Management Server. # /opt/ov/ovnm/bin/ovnm_start.sh 9. Execute the./ovnm_configure.sh script file to update policies for existing nodes. 10. To add support for Japanese character set, run setlocale.sh to configure different locale, and re-start OVNM environment 74

77 Adding Additional NonStop Nodes Once OVNM is initially configured, add more Nodes by performing the following steps. 1. Run the following script to start the process. /opt/ov/ovnm/bin/ovnm_add_nodes.sh NOTE: Make sure your locale is set to C before running ovnm_add_nodes.sh. 2. Enter the name of the HPE NonStop node that is to be added. For example NODE.domain.com NODE.HPE.com 3. Enter the IP Address of the HPE NonStop node The system starts checks the name resolution for the specified node and the following message is displayed. Checking the name resolution. This can take a few minutes. Please be patient... The steps for name resolution will be different for HPE UX and SUN SOLARIS. HPE UX a. Name Resolution Successful: In case the name resolution is successful, the script adds the node to the HPE OM configuration and continues with the process of configuration with the following message. Successfully resolved the nodename. Continuing... b. Name Resolution Failed: In case the name resolution fails, the script checks for the existence of the name resolution method: DNS or Files. If the script finds DNS as the name resolution method, it instructs the user to add an entry in the DNS for the HPE NonStop node and restart the script. Name resolution for NODE.HPE.com failed. Please define an entry for this node in your DNS records and rerun this script. If the script finds Files(hosts) as the name resolution method, it automatically adds the HPE NonStop node to the hosts file and continues with the operation. Name resolution for NODE.HPE.com failed. Adding the node entry in the hosts file.. If the script is unable to find the name resolution method, it will prompt to choose a method of resolution from DNS or Files. If the user chooses DNS the script instructs to add an entry in the DNS for the node and restart the operation. If the user chooses Files the script adds the entry in the hosts file and continues. Name resolution for NODE.HPE.com failed. Not able to determine the method of name resolution used. Please specify the name resolution scheme which you are using, from: 1) DNS 2) files 75

78 6 Installing OVNM on Linux Server Introduction This section describes how to install HPE OVNM for the first time on the HPE Operations Manager (OML) Linux Management Server. To install and configure OVNM on HPE OM Linux Server, perform the following steps. 1. FTP the appropriated OVNM depot.tar file from the HPE OVNM product CD to the Linux Server. For locating the OVNM linux tar.file, refer to the Obtaining ovnm_linux.tar.gz File section. 2. Install OVNM software. 3. Configure OVNM. Refer to the Configuring OVNM on LINUX section. 4. Deploy the NonStop Server policies on HPE OM Server and assign the responsibilities to the users for NonStop messages using the HPE OM. For details, refer to the Configuring the HPE OMU 9 Environment section. Installing OVNM on Linux Server Obtaining ovnm_linux.tar.gz File The following OVNM installation file is located in the HPE OVNM product CD in the OVNM for UNIX directory ovnm_linux.tar.gz FTP the tar file from the Windows PC to a temporary location on the Linux Server. NOTE: The /var/spool/sw directory will be used as the Location in all examples in this Chapter. OVNM Installation To install OVNM on Linux Server, perform the following steps. 1. Logon to the HPE Operations Management Server as root user and switch to the directory where the Depot tar file was FTPed. # cd /var/spool/sw 2. Extract the resulting tar file by running the following command. 3. #tar xvzf ovnm_linux.tar.gz # cd /var/spool/sw/ovnm-linux #./install.sh Enter the path where you want to install ovnm, default is /opt/ov/ovnm 4. Do you want to ADD support for japanese character set (Y/N):n Y NOTE: If OM Server being used supports Japanese language support, enter the value as Y, else put N. 76

79 Configuring OVNM on Linux To configure the HPE NonStop Nodes, communicate with the OVNM SPI and perform the following steps. It is assumed at this point that the NonStop Nodes being configured already has an OVNM Agent installed. 1. Change the working directory to /opt/ov/ovnm/bin where the script and binary files have been copied by default, after the installation. # pwd # cd /opt/ov/ovnm/bin 2. Execute the following script to initiate the configuration process. #./ovnm_configure.sh NOTE: Make sure your locale is set to C before running ovnm_configure.sh. 3. Enter the port number (above 5000) for NonStop Alerts reception. The default port is Enter the fully qualified name of the HPE NonStop Node. For example, NODE.domain.com. NODE.HPE.com 5. Enter the IP Address for the specified HPE NonStop node The system checks the name resolution for the specified node and the following message is displayed. Checking the name resolution. This can take a few minutes. Please be patient... For name resolution at Linux server, perform the following steps. a. Name Resolution Successful: In case the name resolution is successful, the script adds the node to the HPE OM configuration and continues with the process of configuration with the following message. Successfully resolved the node name. Continuing... b. Name Resolution Failed: In case the name resolution fails, it will prompt to choose a method of resolution from DNS or Files. If the user chooses DNS the script instructs to add an entry in the DNS for the node and restart the operation. If the user chooses Files the script adds the entry in the hosts file and continues. Name resolution for NODE.HPE.com failed. Not able to determine the method of name resolution used. Please specify the name resolution scheme which you are using, from: 1) DNS 2) files 7. Enter the label of the HPE NonStop node that you want to be displayed in HPE OM. \NODE 8. Enter the port for NonStop Alerts on the specified node. The default port is

80 9. OVNM can be configured to support one or more HPE Operations Management Servers. You can configure OVNM to support a pair of HPE OM Management Servers as primary, backup or broadcast. For details, refer to the OVNM users guide. Specify the HPE OM Management server as Primary, Backup or broadcast server. Enter 1 for primary, 2 for backup and 3 for broadcast. 1 Once the required information is entered correctly the following message is displayed. Adding \NODE node to the NonStop-Server node group bank as IP node Operation successfully completed. Adding \NODE service map and assigning it to opc_adm user... Successfully added service file file: /opt/ov/ovnm/bin/service_file2.xml (SVC10-111) Successfully assigned services to operator opc_adm (SVC10-113) Successfully assigned services to operator opc_adm (SVC10-113) 10. The system confirms if you want to add another node. To configure another node, type Y, otherwise type N. N 11. The system confirms if u want to auto start OVNM at system reboot. To add OVNM at startup, type Y, otherwise type N. Y The will display the following message. Adding OVNM at Startup Added OVNM at system startup successfully. This completes the OVNM configuration portion of the installation. A successful configuration will display the following message. OVNM is successfully configured. Deploy the NonStop Server policies on to OMU Server and assign the responsibilities to the users for NonStop messages. Configuring the HPE OMU 9 Environment The OM 9 UNIX Administration UI will be used to configure the HPE NonStop Server templates, and assign HPE OM9 users responsibilities. The NonStop Server icon is added to the HPE OM Node Bank Group after OVNM installation. To configure the HPE OM9 environment, perform the following steps. Assign HPE NonStop Server Template Group Deploy HPE NonStop Server Template Group Set User Responsibilities and Applications To complete configuration, perform the steps in the Configuring the HPE OM9 Environment section. 78

81 Starting OVNM on HPE OMU 9 Linux After Installing OVNM and configuring the environment, use the following command to start the OVNM Agents on the OVNM Linux Management Server. # /opt/ov/ovnm/bin/ovnm_start.sh Note the ovnm_start.sh file is used to start the ovnm_spi process. In order to alter the run-time parameters of the OVNM agents, you can use the ovnm_spi binary. #./ovnm_spi help Usage: OVNM_SPI -logfile -trace <filename> trace messages to the specified file. Default file is stderr -diagnose To generate diagnostic file. -node Set incoming node name during OVO message logging -alive <value> How often to check that elink is alive (Default is 180 seconds) -count <value> How many messages to generate if elink is down or hung (Default is 3) -maxgobacknumseconds <value> Maximum no of seconds to go back during message queuing (Default is seconds) -msgqueuing Enables message queuing feature (Default is OFF) -logfilelen <number-of-bytes> Set logfile size (Default is 5MB) -internalmsg <ON OFF> Enables send internal message to OVO feature (Default is ON) -internalmsgseverity < NORMAL WARNING MINOR MAJOR CRITICAL > Set severity of internal messages (Default is CRITICAL) -agent To check if OVO agent is running or not before sending messages to OVO. -catchuptimeout <value> How many seconds to wait for catchup messages. Default is 120 seconds. -ovomonitoringinterval <value> How often to monitor OVO agent/server. Default is 10 seconds. -ovnmmode311 <ON OFF> Enable or disable the OVNM mode 311. Default is OFF. To test the integration after starting the OVNM agents, perform the steps in the Testing OVNM and HPE OM Integration section. In case you need to stop OVNM Agents on the HPE OM Management Server, use the following command. # /opt/ov/ovnm/bin/ovnm_stop.sh 79

82 Upgrading OVNM on Linux The following OVNM installation files are located in the OVNM for Linux directory of the HPE OVNM product CD. Table 10. OVNM Installation Files Installation File ovnm_linux.tar.gz Version Linux Red Hat Enterprise Linux5.5 To upgrade OVNM on HPE OM UNIX, perform the following steps. 1. FTP the appropriate depot tar file from the Windows PC to a temporary location on the LINUX Server. 2. Stop OVNM Agents on the HPE OM Management Server, use the following command # /opt/ov/ovnm/bin/ovnm_stop.sh 3. Logon as root user and switch to the directory where the Depot tar file was FTPed using the following command. # cd /var/spool/sw 4. Extract the resulting tar file. #tar xvzf depot.tar.gz 5. To start the installation process, execute the./install.sh script file. 6. Execute the./ovnm_configure.sh script file to update policies for existing nodes. 7. To add support for Japanese character set, run setlocale.sh to configure different locale, and re-start OVNM environment 80

83 7 Uninstalling OVNM Uninstalling OVNM from HPE OM UNIX This section covers the procedure to uninstall OVNM components from the HPE OM Management Server. To uninstall OVNM from the HPE OM UNIX Management Server, you need to first stop the OVNM Agents and then run the ovnm_remove script. After OVNM has been uninstalled successfully, you will have to remove HPE NonStop Policies, Nodes and Applications from the HPE OM Management Server manually. NOTE: Make sure that you are not in the OVNM home directory (/opt/ov/ovnm) while performing the uninstallation. To uninstall OVNM, perform the following steps. Step A: Stopping the OVNM Agents Stop the OVNM agents using the following command. # /opt/ov/ovnm/bin/ovnm_stop.sh This will stop the Elink and OVNM SPI agents, if running, on the machine. Step B: Uninstalling OVNM a. Execute the following script: # /opt/ov/ovnm/bin/ovnm_remove.sh This initiates the uninstall process. b. The process asks you to confirm the uninstallation. Type Y to continue with the uninstallation, to exit, type N. Y The rest of the uninstall session is non-interactive. The uninstallation successfully completes with the following messages. OVNM has been removed successfully. Please remove the NonStop policies, nodes and applications manually. Step C: Removing NonStop Nodes a. Open the OVO Node Bank window. Figure 71. OVO Node Bank Window 81

84 b. Double-click HoldingArea. This displays the Layout Group: HoldingArea window with the HPE NonStop Nodes. Figure 72. Layout Group: HoldingArea Window c. Right-click a HPE NonStop node icon, and select the Delete option. Figure 73. Layout Group: HoldingArea Window Delete Option 82

85 d. OVO Question Dialog is displayed with the warning that the nodes will be deleted from all node hierarchies. Click the Yes button to continue. Figure 74. OVO Question Dialog e. OVO Information and OVO Errors Information are displayed. Click the respective OK buttons to continue. f. Move to the Layout Group: HoldingArea window to check that the NonStop Node has been removed. Repeat step 3-5 for all the HPE NonStop nodes. Figure 75. Layout Group: HoldingArea Window with all the HPE NonStop Nodes Removed 83

86 Step D: Removing NonStop Node Group a. Open the OVO Node Bank window and select the Node Group Bank option from the Window menu. Figure 76. OVO Node Bank Window Node Group Bank Option b. The OVO Node Group Bank window is displayed. Right-click the NonStop-Server icon and select the Delete option. Figure 77. OVO Node Group Bank NonStop-Server - Delete Option 84

87 c. The OVO Question Dialog is displayed. Click the Yes button to continue. Figure 78. OVO Question Dialog d. Move to the OVO Node Group Bank window and check that the NonStop Server icon has been successfully removed. Figure 79. OVO Node Group Bank Window 85

88 Step E: Removing NonStop Message Group a. Open the OVO Node Bank window and select the Message Group Bank option from the Window menu. Figure 80. OVO Node Bank Window Message Group Bank Option b. The OVO Message Group Bank window is displayed. Right-click the NonStop message group icon and select the Delete option. Figure 81. OVO Message Group Bank NonStop - Delete Option 86

89 c. The OVO Question Dialog is displayed. Click the Yes button to continue. Figure 82. OVO Question Dialog d. Move to the OVO Message Group Bank window and check that the NonStop message group icon has been successfully removed. Figure 83. OVO Message Group Bank Window 87

90 Step F: Removing NonStop Applications a. Open the OVO Node Bank window and select the Application Bank option from the Window menu. Figure 84. OVO Node Bank Window Application Bank Option 88

91 b. The OVO Application Bank window is displayed. Right-click the NonStop Tools application icon and select the Delete option. Figure 85. OVO Application Bank NonStop Tools - Delete Option c. The OVO Question Dialog is displayed. Click the Yes button to continue. Figure 86. OVO Question Dialog 89

92 d. Move to the OVO Application Bank window and check that the NonStop Tools application group icon has been successfully removed. Figure 87. OVO Application Bank Window 90

93 Step G: Removing NonStop Message Source Templates a. Open the OVO Node Bank window and select the Message Source Templates option from the Window menu. Figure 88. OVO Node Bank Window Message Source Templates Option b. The Message Source Templates window is displayed. Select HPE NonStop Server from the Template Groups list. The templates in the HPE NonStop Server template group are displayed on the right-hand side of the window. Select the two templates and click the Delete From All button. Figure 89. Message Source Templates Window c. OVO Question Dialog confirmation box is displayed. Click the Yes button to continue. Figure 90. OVO Question Dialog 91

94 d. In the Message Source Templates window, select HPE NonStop Server from the Template Groups list again and click the Delete From All button. Figure 91. Message Source Templates Window e. OVO Question Dialog confirmation box is displayed. Click the Yes button to continue. f. The templates in the Toplevel Template Group are displayed in the Message Source Templates window. Select the OVNM-NonStop-Msgs and OVNM-OvMon-Msgs message templates from the right-hand side of the window and click the Delete From All button. Figure 92. Message Source Templates Window g. OVO Question Dialog confirmation box is displayed again. Click the Yes button to continue. h. The Message Source Templates window is displayed with all the HPE NonStop Message Templates removed. Figure 93. Message Source Templates Window 92

95 Step H: Removing OVNM Services To remove OVNM Application services from the HPE OM Service Map, use the following command. opcservice remove ApplicationServices To remove OVNM System services from the HPE OM Service Map, use the following command. opcservice remove SystemServices Step I: Restarting HPE OM Restart the HPE OM session to check if all the HPE NonStop nodes, node groups, message groups, applications and message source templates have been removed successfully. This completes the procedure to uninstall OVNM from the HPE OM UNIX Management Server. Uninstalling OVNM from HPE NonStop Server To delete OVNM components from a HPE NonStop Server, perform the following steps. 1. Open the OVNM Host Installation Client using Start Programs HPE OVNM NonStop Server Tools Host Installation Client option. 2. In the displayed OVNM Host Installation Client dialog box, select the Managed Host and click the Delete button to access the corresponding menu. Figure 94. OVNM Host Installation Client Delete Menu 3. To delete OVNM components from the HPE NonStop Server, you can use either Delete From Workstation or Delete From Both options. If you use the Delete From Both option, OVNM components from the NonStop server as well as the workstation will be removed. 93

96 Clicking the Delete from Workstation option displays the OVNM Host Installation Client confirmation box. Figure 95. OVNM Host Installation Client Confirmation Box Clicking the Delete from Both option displays the OVNM Host Installation Client confirmation box. Figure 96. OVNM Host Installation Client Confirmation Box 4. Click the Yes button to continue. The Login to Host dialog box is displayed. Enter the User Name and Password in the respective fields and click the OK button to continue. Figure 97. Login to Host Dialog Box 5. The OVNM Host Installation Client confirmation box is displayed. Click the Yes button to update the OVNM Agents Configuration, else click the No button. Figure 98. OVNM Host Installation Client Confirmation Box 94

97 The OVNM Host Response for Deleting Configuration for the selected node is displayed with the information that the node has been deleted successfully. Figure 99. OVNM Host Response for Deleting Configuration Dialog Box 6. You can save the session as a text file using the Save button. To close the box after completion of the process, click the OK button. For the manual uninstallation of OVNM, refer to Appendix F: Manual Operations on HPE NonStop Server. 95

98 Uninstalling OVNM from Linux (Removing NonStop Nodes from HPE OM9) The uninstallation process of OVNM from Linux involves the following. 1. Removing NonStop Nodes 2. Removing NonStop Node Group 3. Removing NonStop Message Group 4. Removing NonStop Applications 5. Remove the HPE NonStop Server Policy The following sections describe each in detail. Removing NonStop Nodes To remove the NonStop Nodes from HPE OM9, perform the following steps. 1. Open the Node Bank window. Click the Holding Area link. Figure 100. Node Bank Window 96

99 The Holding Area window is displayed. Figure 101. HoldingArea Window 2. Select the check box corresponding to the HPE NonStop Node that you want to delete. Click the icon and click the Delete item in the action menu. Figure 102. Action Menu Delete Option 3. The delete message box is displayed. Click the Ok button to delete the selected node. 4. In the HoldingArea window, confirm whether the NonStop Node has been removed or not. 5. Repeat the above step for all the HPE NonStop Nodes. 97

100 Removing NonStop Node Group To remove the NonStop Node group, perform the following. 1. In the Node Bank window, and click the Browse menu. In the Browse menu, click the All Node Groups item. Figure 103. Node Bank Window All Node Groups Option 2. The All Node Groups window is displayed. Select the NonStop-Server check box and click the Delete item in the Actions menu. Figure 104. All Node Groups Window 3. The delete message box is displayed. Click the Ok button to delete the selected node. 4. In the Node Bank window, confirm whether the NonStop Server option is successfully removed or not. 98

101 Removing NonStop Message Group To remove the NonStop Message group, perform the following steps. 1. In the Node Bank window, click the All Message Groups item in the Browse Menu. Figure 105. Node Bank Window All Message Groups Option 2. The All Messages Groups window is displayed. Right-click the NonStop message group option and click the Delete item in the Actions menu. Figure 106. All Messages Groups Window 3. The delete message box is displayed. Click the Ok button to delete the selected node. 4. In the All Message Groups window, confirm whether the NonStop message group option is successfully removed or not. 99

102 Removing NonStop Applications To remove the NonStop Applications, perform the following steps. 1. In the Node Bank window, click the All Tool Groups item in the Browse Menu. Figure 107. Node Bank Window All Tool Groups Option 2. The Tool Bank window is displayed. Select the following check boxes NonStop Tools NonStop Operator Tools OVNM Tools Figure 108. Tool Bank Window 100

103 3. In the Choose an action drop-down list box, click the Delete item. Figure 109. Choose an Action Drop-down List Box 4. The delete message box is displayed. Click the Ok button to delete the selected node. 5. In the Tool Bank window, click the Show All link and delete all the other HPE NonStop Server tools. Figure 110. Tool Bank Window HPE NonStop Server Tools Page 6. In the Tool Bank window and confirm whether the NonStop applications are successfully removed or not. 101

104 Removing HPE NonStop Server Policy To remove the HPE Non Stop server policy, perform the following steps. 1. In the HPE OM Node Bank window, click the Policy Bank item in the Browse menu. Figure 111. HPE OM Node Bank Window Policy Bank Option 2. The Policy Bank window is displayed. Click the icon, and then click the Delete item in the Actions menu. Figure 112. Policy Bank Window 3. The delete message box is displayed. Click the Ok button to delete the selected node. 102

105 4. Similarly, delete all the other OVNM message groups. Figure 113. Policy Bank Window OVNM Message Groups Page 5. In the Tool Bank window, confirm whether the OVNM message groups are successfully removed or not. 103

106 Uninstalling OVNM from Windows Workstation To uninstall OVNM components from the workstation, perform the following steps. NOTE: Before uninstallation, ensure that none of the OVNM components are running. Stop any copies of OCC, ObjectMAP, ObjectStats and/or Console that may be running. Then click Start Programs HPE OVNM Management Server Tools Stop Agents option. 1. Click the Start Programs HPE OVNM Management Server Tools UnInstall option to start the uninstallation process. 2. The HPE OVNM dialog box with the information that all the OVNM components running on the system must be closed. Click the OK button to continue. The HPE OVNM Welcome page is displayed with the Remove option button selected. Figure 114. HPE OVNM Welcome Page Remove Radio Button 3. To continue with the uninstallation process, click the Next button. The Confirm Uninstall message box asking confirmation for removing the application and its features. Figure 115. Confirm Uninstall Message Box 104

107 4. Click the Yes button to continue. The Locked Files Information page is displayed. The page provides a list of all the locked files. These files will be deleted after system reboot. Figure 116. HPE-OVNM Locked Files Information 5. Click the Next button. The Uninstall window is closed, and the uninstall process is completed. Silent Uninstall from Windows For Silent uninstallation, perform the following steps. To uninstall, perform the following steps. 1. Open CMD. 2. Enter D:<path>OVNMInstallation.exe r f1 D:<path>\uninstall.iss. This creates the uninstall.iss file. To execute the silent uninstall, perform the following steps. 3. Open CMD. 4. Enter D:<path>OVNMInstallation.exe s f1 D:<path>\ uninstall.iss. 105