HP Operations Agent for NonStop Installation Guide Part number: 540072-010 Tenth edition: 01/2014
Legal notices Hewlett-Packard makes no warranty of any kind with regard to this manual, including, but not limited to, the implied warranties of merchantability and fitness for a particular purpose. Hewlett-Packard shall not be held liable for errors contained herein or direct, indirect, special, incidental or consequential damages in connection with the furnishing, performance, or use of this material.
Contents Preface Before You Begin ........................................................................................................................................ 8 Audience ................................................................................................................................................... 8 Goals of Documentation .............................................................................................................................. 8 Organization................
6-2-1 6-2-2 6-3 6-3-1 6-4 7 Uninstalling 7-1 7-2 7-3 7-3-1 7-3-2 7-3-3 7-3-4 7-3-5 7-4 Obtaining ovnm_linux.tar.gz File............................................................................................ 77 OVNM Installation ................................................................................................................ 78 Configuring OVNM on Linux .................................................................................................
Figures Figure Figure Figure Figure Figure Figure Figure Figure Figure Figure Figure Figure Figure Figure Figure Figure Figure Figure Figure Figure Figure Figure Figure Figure Figure Figure Figure Figure Figure Figure Figure Figure Figure Figure Figure Figure Figure Figure Figure Figure Figure Figure Figure Figure Figure Figure Figure Figure Figure Figure Figure Figure Figure Figure 2-1 HP OVNM Installation Welcome Screen .....................................................................................
Figure Figure Figure Figure Figure Figure Figure Figure Figure Figure Figure Figure Figure Figure Figure Figure Figure Figure Figure Figure Figure Figure Figure Figure Figure Figure Figure Figure Figure Figure Figure Figure Figure Figure Figure Figure Figure Figure Figure Figure Figure Figure Figure Figure Figure Figure Figure Figure Figure Figure Figure Figure Figure Figure Figure Figure Figure 5-15 Modify User Window ........................................................................................
Figure Figure Figure Figure Figure Figure Figure Figure Figure Figure Figure Figure Figure Figure Figure 7-38 7-39 7-40 7-41 7-42 7-43 7-44 7-45 7-46 7-47 7-48 7-49 7-50 7-51 7-52 Node Bank Window − All Tool Groups Option ............................................................................. 103 Tool Bank Window .................................................................................................................... 104 Choose an Action Drop-down List Box ................................
Preface HP Operations Agent for NonStop (OVNM) is an out-of-the-box solution that provides seamless integration of HP Operations Software (previously known as HP OpenView) with HP NonStop servers. The software is a natural extension of HP Operations and provides you with true end-to-end management of your NonStop environment. Before You Begin Before reading the documentation, you are expected to have a basic understanding of HP Operations environment, as well as the HP NonStop environment.
Organization Sr. 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 HP Operations management server and the HP NonStop managed nodes. Chapter 2 Installing OVNM on Windows Details the OVNM installation procedure on Windows.
Description Media OVNM SNMP Adapter Guide Covers installation and configuration. SNMP Adapter is used when SNMPcompatible management consoles are used. such as HP Operations Network Node Manager, BMC’s PATROL, and IBM’s NetCool PDF OVNM Console Guide Explains the Console interface and provides the instructions on how to use the software effectively.
1 OVNM Installation Overview 1-1 Overview HP Operations Agent for NonStop (OVNM) is an out-of-the-box solution that provides seamless integration of HP Operations Manager with HP NonStop servers. Although HP OVNM is designed to integrate with HP 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.
• 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.
1-1-2 HP Operations Manager Environment OVNM installation on the Operations management server primarily involves the installation of the OVNM SPI Agent, which feeds the NonStop events into the HP 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.
1-2-3 Workstation Environment (Any system where OCC and Console are to be installed) Operating System Windows (XP/Vista/Window 7/2003) Protocol TCP/IP Disk Space 200 MB 1-3 Prerequisites for OVNM Installation 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. a.
2 OVNM Installation on Windows 2-1 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 HPOM workstation.
2. Click the Next button. The License Agreement screen is displayed. Figure 2-2 HP OVNM Installation License Agreement Screen Review the software license agreement and click the Yes button. The Choose Destination Location screen 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.
WARNING! Please be sure you have totally unzipped 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 screen is displayed. Figure 2-4 HP OVNM Installation Setup Type Screen 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.
4. Click the Next button. The Check Setup Information screen is displayed. Figure 2-5 HP OVNM Installation Check Setup Information Screen The current settings, which have been selected so far are displayed. In case you want to change any of the settings, you can do so by going back to the particular screen before you start copying the program files. NOTE: You should check the location of the directory where OVNM is to be installed.
7. Click the Next button. The Setup Complete screen is displayed. Figure 2-7 HP OVNM Installation Setup Completed Screen NOTE: It is recommended that you login with the same User ID used during installation for using OVNM. OVNM Installation on Windows 20 Installing OVNM on Windows Click the Finish button to complete the process. The OVNM installation on a Windows workstation is completed.
2-2 Starting OVNM on Windows Operations Manager To start OVNM Agents on the Windows Operations Manager Management server, click the Start Programs HP OVNM Management Server Tools Start Agents option. Figure 2-8 Starting Agents Using Start Menu The Start Agents option starts the OVNM communication interface on the Windows workstation or Server. If OVNM is installed on an HPOM server the SPI interface is also started.
2-3 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 HPOM Server 3. Upgrading OVNM Agent on the HP NonStop Server 4. Testing upgrade 2-3-1 Upgrading OVNM Components on Windows To upgrade OVNM Components on Windows, perform the following steps. 1. Run the OVNMInstallation.exe file.
4. HP-OVNM Select Features screen is displayed. Select the components that need upgrade, and click the Next button. Figure 2-11 HP-OVNM Select Features Screen 5. If upgrading OVNM on OVO Windows Server the HP-OVNM Installation message box is displayed with the information that the installation is preparing to reinstall NonStop Tools in HPOM. If you have modified the NonStop tools, save them, and then click the OK button to continue. Figure 2-12 HP-OVNM Installation Message Box 6.
7. The Install Shield completes the installation on the workstation and the HP-OVNM Setup Completed screen is displayed. Click the Finish button to complete the procedure. 2-3-2 Upgrading OVNM Components on the HPOM Server Refer to the section Upgrading OVNM on HPOM UNIX for details on how to upgrade OVNM on the HPOM UNIX server. 2-3-3 Upgrading OVNM Agent on the HP NonStop Server To upgrade OVNM Agent on the HP NonStop Server, perform the following steps. 1.
2-3-4 Testing Upgrade Perform the following steps to generate a test EMS event. Once generated, OVNM will process the message. If an Enterprise Manager is used the Manager will display the message. 1. Run Host Management Client using the Start Programs HP 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 HP NonStop Server User ID and password used for this installation. 3.
3 Installing OVNM on HP 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 HP NonStop Server, perform the following steps. 1. Click the Start Programs HP OVNM NonStop Server Tools Host Installation Client to start the installation process.
2. The OVNM Host Installation Client dialog box is displayed. To add a new HP NonStop host, click the New button. Figure 3-2 OVNM Host Installation Client Dialog Box The New OVNM Configuration dialog box is displayed. By default the Host Tab page is displayed.
3. In the Host tab page, specify the information as described in the following table. Table 3-1 NonStop Node Configuration Parameters Parameter Name Managed Host Configuration Name Information Description Additional Information 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).
Table 3-1 NonStop Node Configuration Parameters Other Parameters Parameter Name Description Additional Information OVNMPort Port number for Elink connection with the HP 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 1.1.1.1 and ports 5020/5030 multiple times.
4. Click the Communication tab to configure communication related OVNM parameters. The Communication tab page is displayed. Figure 3-4 New OVNM Configuration – Communication Tab Page 5. In the Communication tab page, specify the information as described in the following table. Table 3-2 Communication Parameters Area Parameter Name Communication • Information Telnet and FTP Information • • • Description Additional Information Show Advanced Options To view and configure advance options.
Table 3-2 Communication Parameters Area Services Available Parameter Name Description • • • Specify the FTP port to be used for the • FTP session with the HP NonStop Host. Use the corresponding Address field to specify the IP address or the DNS name for the FTP session with the HP NonStop Host. There are 3 types of FTP that are supported - standard, SFTP, and SSL. If your NonStop Host is configured to use one of those options, pick the selection that matches your host.
6. 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 screen as well. Figure 3-5 Communication Tab Page – Advanced Communication Information 7. Specify the following information. a.
9. Click the Policies tab to add default OVNM policies to the HP NonStop Server. The Policies tab page is displayed. Figure 3-6 New OVNM Configuration – Policies Tab Page 10. In the Policies tab page, specify the information as described in the following table. Table 3-3 Policies Parameters Area Parameter Name Description Additional Information Policies Add Default Policies Click the Add Default Policies check box • to install the OVNM Object Monitoring policies.
11. Click the Mail tab to configure the E-mail facility on the HP NonStop Server. The Mail tab page is displayed. Figure 3-7 New OVNM Configuration – Mail Tab Page 12. In the Mail tab page, specify the information as described in the following table. Table 3-4 Email Parameters Area Parameter Name Description Additional Information Mail Allow Mail To enable the mail functionality. • • The option is disabled by default. Selecting the check box enables other fields on the tab page.
Table 3-4 Email Parameters Area 13. Parameter Name Description Additional Information Queue Read Interval To specify how often the host application is to pick up queued mails. • • Giveup Interval To specify the duration, in minutes, after • which the host application will stop • trying to send the e-mail and delete it from the queue. Retry Interval 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.
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 HP 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. 14.
16. 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 3-9 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.
Clicking the Plug-Ins tab displays the Plug-Ins tab page. This tab page is optional and is intended for OVNM Plug-In support. Figure 3-10 New OVNM Configuration Dialog Box Plug-Ins Tab Page For information on installing and verifying Telco Plug-in refer to documentation on Telco Plug-in for OVNM. 17. Click the EMS Template tab to configure for EMS template files. The EMS Template tab page is displayed.
18. Click the BASE24 tab to configure BASE24. The BASE24 tab page is displayed.
19. In the BASE24 tab page, specify the information as described in the following table. Table 3-6 BASE24 Parameters 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. Checking this option will allow the addition of BASE24 distributor to the OCC screen and start the processing of BASE24 events. Selecting the option enables other fields in the tab page.
20. Click the Enterprise tab to configure other OVNM options. The Enterprise tab page is displayed. Figure 3-13 New OVNM Configuration – Enterprise Tab Page NOTE: This panel is ONLY to be used when you have OVNM installed with Enterprise Manager like HPOM in a WINDOWS environment. 21. Select the NonStop Event Message Format from the drop-down box. 22.
23. Select the Enterprise Management Server to receive NonStop Events from the drop-down box. This option is enabled only when the Fault Tolerance Enabled check box is selected. Figure 3-14 New OVNM Configuration – MQ Series Tab Page NOTE: This panel is ONLY to be used when you are going to use OVNM to monitor your MQ environment(s). For information on installing and verifying MQ Series Plug-in refer to documentation on MQ Series Plug-in for OVNM. 24.
27. Once you have completed all the configurations, click the Install button in the New OVNM Configuration dialog box to start installing OVNM on the HP NonStop host. Figure 3-15 New OVNM Configuration Dialog Box At this point you can perform any of the following tasks also. a. To revert to the default field values, click the Reset Fields button. b. Use the Cancel button to close the dialog box without saving the information. c.
While configuring, if you have changed the collector in the Log To Collector field of 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 a OVNM Host Installation Client confirmation box is displayed with the information about the status of the installation process.
The OVNM Host Response for Installation dialog box is displayed again with the message that the installation has completed. Figure 3-20 OVNM Host Response for Installation Dialog Box – Installation Complete You can save the session as a text file using the Save button. To close the box after completion of the installation process, click the OK button. This completes the installation process.
4-1 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 OVNM 5.x release introduced the following new features that are not supported on NonStop Servers running OVNM 4.x or earlier versions.
The Upgrade Release option in the OVNM Host Installation Client Upgrade menu allows you to perform a full software release upgrade. Clicking the Upgrade button displays the Upgrade menu. Figure 4-2 Upgrade Release Option in Upgrade Menu Clicking the Upgrade Release option displays the Login to Host dialog box. Figure 4-3 Login to Host Dialog Box Enter the user name and password in the Login to Host dialog box and click the OK button to initiate the upgrade process.
The OVNM Host Response for Upgrade Release dialog box is displayed showing the response of the operations carried on the NonStop Host. Figure 4-4 OVNM Host Response for Upgrade Release Dialog Box During the upgrade process on the NonStop Host the OVNM Host Installation Client confirmation box is displayed. Figure 4-5 OVNM Host Response for Upgrade Release Click the Yes button if you want to run OVNM on the specified Node. This will start OVNM agents on the HP NonStop Server.
Upgrading OVNM on HP NonStop Server The upgrade procedure completes with the status that the release upgrade is successful. Use the Save button to save the response in the form of a text file. To close the dialog box, click on OK button. Figure 4-6 OVNM Host Response for Upgrade Release Dialog Box This completes the upgrade of OVNM on a HP NonStop Server.
5 Installing OVNM on HPOM UNIX 5-1 Introduction This chapter describes how to install HP OVNM for the first time on the HP Operations Manager (HPOM) UNIX Management Server. To upgrade from an earlier OVNM version, refer to section Upgrading OVNM to a Newer Version. Overview of Steps for Installing and Configuring OVNM on OVO (VPO) UNIX Server 1. FTP the appropriated OVNM depot .tar file from the HP OVNM product CD to the UNIX Server. Refer to Obtaining the Appropriate OVNM Depot .tar File. 2.
5-2-2 OVNM Installation Getting Started 1. Logon to the HP 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 OVO (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: /OVNM-HPUX/OVNM-CONF-FILES/var/opt/OV/share/tmp/OpC_appl/ovnm/conf/C/ovnmcfg.
5-3 Configuring OVNM on HPOM UNIX The following procedure is used to configure the HP 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 HPOM 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.
SUN SOLARIS a. Name Resolution Successful: In case the name resolution is successful, the script adds the node to the HPOM 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.
5-4 Configuring the HPOM Environment The following sections describe the configuration of the HPOM environment in HPOM 8 and HPOM9. 5-4-1 Configuring the HPOM8 Environment The OVO/VPO ‘opc’ program will be used to configure the HP NonStop Server templates, and assign HPOM users responsibilities. The NonStop Server icon is added to the OVO Node Bank Group after OVNM installation. Perform the following tasks to configure the HPOM environment.
2. Select the Agents menu in the Actions menu. In the displayed Agents menu, click the Assign Templates option. 3. Installing OVNM on HPOM UNIX Figure 5-2 OVO Node Bank – Actions – Agents - Assign Templates Option The Define Configuration window is displayed. Figure 5-3 Define Configuration Window Click the Add button to add the HP NonStop Server group template. 4. In the OVO Node Bank window, select the Management Server icon with a single mouse click. 5.
6. Click the Open Template Window button in the Add Configuration window. The Message Source Templates window is displayed. Select the Group HP NonStop Server template on the right-hand-side of the window. Figure 5-5 Message Source Templates Window with Group HP NonStop Server Template Selected 7. Move to the Add Configuration window and click the Get Template Selections button to add the Group HP NonStop Server template to the Templates box.
5-4-1-2 Deploy HP NonStop Server Template Group Once the HP NonStop Server templates have been assigned, they have to be distributed to the managed nodes. This can be accomplished using the Install / Update OVO Software and Configuration window. 1. In the OVO Node Bank window, select the Management Server. As an example we have selected SUNMAC. Installing OVNM on HPOM UNIX Figure 5-8 OVO Node Bank Window 2. Select the Install / Update SW & Config menu option in the OVO Node Bank Actions/Agents menu.
3. The Install / Update OVO Software and Configuration window is displayed. Select the Templates and Nodes in list requiring update options. Figure 5-10 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.
5-4-1-3 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. Installing OVNM on HPOM UNIX Figure 5-13 OVO Node Bank - User Bank Option 2. The OVO User Bank window is displayed.
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 5-15 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.
5. Click the Applications button on the Modify User dialog box to assign application to the user. The Applications of User submap is displayed. Installing OVNM on HPOM UNIX Figure 5-17 Applications of User Submap 6. Click the Application Bank option in the Window menu.
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 5-19 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 5-20 Application of User Window with NonStop Tools 9.
5-4-2 Configuring the HPOM9 Environment The OM 9 UNIX Administration UI will be used to configure the HP NonStop Server templates, and assign HPOM9 users responsibilities. The NonStop Server icon is added to the OVO Node Bank Group after OVNM installation. To configure the HPOM9 environment, perform the following steps. • Assign HP NonStop Server Template Group • Deploy HP NonStop Server Template Group • Set User Responsibilities and Applications NOTE: The opc program requires a User ID and Password.
The Node Bank page is displayed.
2. Click the icon. Click the Assign Policies/Policy Groups item in the Actions menu. Figure 5-23 Node Bank Page – Assign Policies/Policy Group Option The Selector dialog box is displayed. Select the HP NonStop Server option.
5-4-2-2 Deploying HP NonStop Server Template Group After you have assigned the HP NonStop Server templates/Policies, you have to distribute these policies/templates to the managed nodes. To distribute theses policies/templates, perform the following steps. 1. In the HPOM Node Bank window, select the Node (BMC062) and click the icon.
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 5-26 Deploy Configuration Dialog Box 3. Click the Ok button to close the dialog box.
5-4-2-3 Assign User Responsibilities and Tools/Applications To assign responsibilities and Tools/applications for a user, perform the following steps. 1. In the HPOM Node Bank window, click the All Users item in the Browse menu.
2. The HPOM 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 5-28 HPOM All Users Window 3. The Selector dialog box is displayed. Click the Tool Bank link and select the NonStop Tools option from the list.
4. Click the Ok button to save your changes. 5. Click the icon, and click the Edit Responsibilities item in the Actions menu.
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 5-31 Edit Responsibilities for User Window 7. Click the Node Group column button to select all the check boxes in the NonStop-Server column.
5-5 Starting OVNM on HPOM 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 -diagnose To generate diagnostic file.
5-6 Testing OVNM and HPOM 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 HPOM 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 HP NonStop Server, which will generate the EMS event. Follow the steps below to execute the Test Message application from the ITO user interface.
The output is displayed in the Test Message Output window. Figure 5-34 Test Message Output Window You can view the HPOM Message Browser and the HPOM 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.
5-7 Upgrading OVNM on HPOM UNIX The following procedure is used to upgrade OVNM on HPOM UNIX. The following OVNM installation files are located in the “OVNM for UNIX” directory of the HP OVNM product CD. Table 5-2 OVNM Installation Files Installation File Version ovnm_hpux-itanium_depot.tar HP-UX Integrity (Itanium) 11i v2 (OM 8.x) ovnm_hpux-risc_depot.tar HP-UX (PA-\RISC) 11iv1,11iv2 ovnm_sol_depot.tar Sun Solaris(32 bit)5.
5-8 Adding Additional NonStop Nodes Once OVNM is initially configured, additional Nodes may be added by executing the following. 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 HP NonStop node that is to be added. For example NODE.domain.com NODE.hp.com Enter the IP Address of the HP NonStop node. 111.111.111.
6 Installing OVNM on Linux Server 6-1 Introduction This chapter describes how to install HP OVNM for the first time on the HP Operations Manager (OML) Linux Management Server. Overview of steps for installing and configuring OVNM on OVO (VPO) Linux Server. 1. FTP the appropriated OVNM depot .tar file from the HP OVNM product CD to the Linux Server. For locating the OVNM linux tar.file, refer to Obtaining OVNM tar File. 2. Install OVNM software. 3. Configure OVNM.
6-2-2 OVNM Installation Getting Started 1. Logon to the HP 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. #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 NOTE: If OM Server being used supports Japanese language support, OVNM configuration file “ovnmcfg.
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.hp.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 HP NonStop node that you want to be displayed in HPOM. \NODE 8. Enter the port for NonStop Alerts on the specified node. The default port is 5030. 5030 9.
6-4 Starting OVNM on HPOMU 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 trace messages to the specified file.
7 Uninstalling OVNM 7-1 Uninstalling OVNM from HPOM UNIX This section covers the procedure to uninstall OVNM components from the HPOM Management Server. To uninstall OVNM from the HPOM 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 HP NonStop Policies, Nodes and Applications from the HPOM Management Server manually.
b. Double-click on HoldingArea. This displays the Layout Group: HoldingArea window with the HP NonStop Nodes. Figure 7-2 Layout Group: HoldingArea Window c. Right-click on a HP NonStop node icon and select the Delete option.
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 7-4 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 HP NonStop nodes.
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 7-6 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.
c. The OVO Question Dialog is displayed. Click the Yes button to continue. Figure 7-8 OVO Question Dialog d. Move to the OVO Node Group Bank window and check that the NonStop Server icon has been successfully removed.
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 7-10 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.
c. The OVO Question Dialog is displayed. Click the Yes button to continue. Figure 7-12 OVO Question Dialog d. Move to the OVO Message Group Bank window and check that the NonStop message group icon has been successfully removed.
Step F: Removing NonStop Applications a. Open the OVO Node Bank window and select the Application Bank option from the Window menu.
b. The OVO Application Bank window is displayed. Right-click the NonStop Tools application icon and select the Delete option. Figure 7-15 OVO Application Bank– NonStop Tools - Delete Option c. The OVO Question Dialog is displayed. Click the Yes button to continue.
d. Move to the OVO Application Bank window and check that the NonStop Tools application group icon has been successfully removed.
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 7-18 OVO Node Bank – Window– Message Source Templates Option b. The Message Source Templates window is displayed. Select HP NonStop Server from the Template Groups list. The templates in the HP 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.
d. In the Message Source Templates window, select HP NonStop Server from the Template Groups list again and click the Delete From All button. Figure 7-21 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.
Step H: Removing OVNM Services To remove OVNM Application services from the HPOM Service Map, use the following command. opcservice –remove ApplicationServices To remove OVNM System services from the HPOM Service Map, use the following command. opcservice –remove SystemServices Step I: Restarting HPOM Restart the HPOM session to check if all the HP NonStop nodes, node groups, message groups, applications and message source templates have been removed successfully.
7-2 Uninstalling OVNM from HP NonStop Server Follow the steps below to delete OVNM components from a HP NonStop Server. 1. Open the OVNM Host Installation Client using StartProgramsHP OVNMNonStop Server ToolsHost 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 7-24 OVNM Host Installation Client – Delete Menu 3.
5. 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 7-26 Login to Host Dialog Box 6. The OVNM Host Response for Deleting Configuration for the selected node is displayed with the information that the node has been deleted successfully.
7-3 Uninstalling OVNM from Linux (Removing NonStop Nodes from HPOM9) 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 HP NonStop Server Policy The following sections describe each in detail. 7-3-1 Removing NonStop Nodes To remove the NonStop Nodes from HPOM9, perform the following steps. 1. Open the OVO Node Bank window.
The HoldingArea window is displayed. Figure 7-29 HoldingArea Window 2. Select the check box corresponding to the HP NonStop Node that you want to delete. Click the icon and click the Delete item in the action menu.
3. The delete message box is displayed. Click the Ok button to delete the selected node. Figure 7-31 Delete Message Box 4. In the HoldingArea window, confirm whether the NonStop Node has been removed or not. 5. Repeat the above step for all the HP NonStop Nodes.
7-3-2 Removing NonStop Node Group To remove the NonStop Node group, perform the following. 1. In the OVO Node Bank window, and click the Browse menu. In the Browse menu, click the All Node Groups item.
2. The All Node Groups window is displayed. Select the NonStop-Server check box and click the Delete item in the Actions menu. Figure 7-33 All Node Groups Window 3. The delete message box is displayed. Click the Ok button to delete the selected node. Figure 7-34 Delete Message Box 4. In the Node Bank window, confirm whether the NonStop Server option is successfully removed or not.
7-3-3 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.
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 7-36 All Messages Groups Window 3. The delete message box is displayed. Click the Ok button to delete the selected node. Figure 7-37 Delete Message Box 4. In the All Message Groups window, confirm whether the NonStop message group option is successfully removed or not.
7-3-4 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.
2. The Tool Bank window is displayed.
3. In the Choose an action drop-down list box, click the Delete item. Figure 7-40 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 HP NonStop Server tools. Figure 7-42 Tool Bank Window − HP NonStop Server Tools Page 6. In the Tool Bank window and confirm whether the NonStop applications are successfully removed or not.
7-3-5 Removing HP NonStop Server Policy To remove the HP Non Stop server policy, perform the following steps. 1. In the HPOM Node Bank window, click the Policy Bank item in the Browse menu.
2. The Policy Bank window is displayed. Click the icon, and then click the Delete item in the Actions menu. Figure 7-44 Policy Bank Window 3. The delete message box is displayed. Click the Ok button to delete the selected node.
4. Similarly, delete all the other OVNM message groups. Figure 7-46 Policy Bank Window − OVNM Message Groups Page 5. In the Tool Bank window, confirm whether the OVNM message groups are successfully removed or not.
7-4 Uninstalling OVNM from Windows Workstation Follow the steps given below to un-install OVNM components from the workstation. NOTE: Before beginning the un-installation, 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 StartProgramsHP OVNMManagement Server ToolsStop Agents.
Step C: Remove All Installed Components The HP OVNM Welcome screen is displayed with the Remove option button selected. Figure 7-49 HP OVNM Welcome Screen Remove Radio Button To continue with the un-installation process, click the Next button. This will display a Confirm Uninstall dialog box asking confirmation for removing the application and its features. Figure 7-50 Confirm Uninstall Confirmation Box Click the Yes button to continue with the un-installation procedure.
Step D: Locked Files Information The Locked Files Information screen is displayed. The screen provides a list of all the locked files. These files will be deleted after system reboot. Figure 7-51 HP-OVNM Locked Files Information Click the Next button. The Uninstall window is displayed. Uninstalling OVNM Figure 7-52 OVNM 5.3 Uninstall Window The uninstall process is completed.
Appendix A: Installation Information 1. User Name The user in whose name OVNM is registered. Example: John Smith 2. Company Name The company in whose name OVNM is registered. Example: ABC Inc. 3. Destination Location The directory on the workstation where OVNM is to be installed 4. Configuration Name Specifies the name of the configuration where OVNM backend is installed. 5. HP NonStop Node Name The Name of the HP NonStop Node where OVNM is to be installed Example: \NODE 6.
15. OVNM Home Terminal Select either a physical hometerm or a process that will be continuously available. Default: $ZHOME 16. OVNM Process Prefix A two character prefix that will be used as the first two characters for all the OVNM processes, making them unique The first character must be a letter, and both characters should be alphanumeric. Example: If you specify the prefix as OV, then the Elink process will be called $OVELK. 17.
28. NSDB Location Location of the NSDB subvolume. This is only needed for the TELCO thresholds. If your site does not use SS7, then it will not be needed. 29. STAT Location Location of the STAT subvolume. This is only needed for the TELCO thresholds. If your site does not use SS7, then this will not be needed. 30. Mach Ini File Location of the MQ Series Mach Ini file Use OSS name for MQ version 5.3 and the Guardian file name for versions of MQ prior to 5.3.
Appendix B: Custom Installation The Custom installation allows you to customize the selection of OVNM components to be installed. This option is recommended for advanced users. Selecting the Custom option displays the Select Features screen. The options available are: • OCC An interactive and user-friendly interface, which is used to define the desired state of a NonStop object in operation.
Appendix C: Sample Installation Session on HPOM HPUX # swinstall -s /var/spool/sw OVNM ======= 06/02/03 15:18:19 PDT BEGIN swinstall SESSION (non-interactive) hpptc50". * Beginning Selection * Target connection succeeded for "hpptc50:/". * Source connection succeeded for "hpptc50:/var/spool/sw". The software item "OVNM" is a bundle (or a product, subproduct or fileset contained within a bundle).
NOTE: More information may be found in the agent logfile (location is hpptc50:/var/adm/sw/swagent.log).
Appendix D: Sample OVNM Configuration on HPOM UNIX This section gives a sample OVNM configuration on HPOM UNIX, under the following conditions: • When the Name resolution for Node is successful • When the Name resolution for Node fails: On HP UX • When the Name resolution for Node fails: On SUN SOLARIS Name Resolution for Node is Successful # ./ovnm_configure.
Name Resolution for Node Fails: On HP UX # ./ovnm_configure.sh OVNM for HP NonStop Server Configuration Please enter the port number (above 5000) for NonStop Alerts reception (default 5030)? 5030 Please enter the fully qualified name of the HP NonStop Node (NODE.domain.com) NODE.hp.com Please enter the IP Address of NODE.hp.com 111.111.111.111 Checking the name resolution. This can take a few minutes. Please be patient.. Name resolution for NODE.hp.com failed.
Name Resolution for Node Fails: On SUN SOLARIS # ./ovnm_configure.sh OVNM for HP NonStop Server Configuration Please enter the port number (above 5000) for NonStop Alerts reception (default 5030)? 5030 # ./ovnm_configure.sh OVNM for HP NonStop Server Configuration Please enter the port number (above 5000) for NonStop Alerts reception (default 5030)? 5030 NODE.hp.com Please enter the IP Address of NODE.hp.com 111.111.111.111 Checking for name resolution. This can take a few minutes. Please be patient...
Appendix E: HP MC/SG Cluster Installation Supplement The information in this topic pertains to installing and configuring OVNM when installed with an HPOM Management Server on a MC/SG (Mission Critical/ServiceGuard) cluster. HPOM installed on a MC/SG Cluster provides high availability in the event the primary Node (running HPOM Management Server) fails. The HPOM Management Server is installed on the shared disk /var/opt/OV/share, which is shared between the two nodes of the MC/SG Cluster.
MC/SG Cluster Package Control Script To configure the Cluster to automatically start and stop OVNM, the package control script, /etc/cmcluster/ov-server/ov-server.cntl, needs to be modified on EACH node of the cluster. The startup and shutdown commands for OVNM are defined in the CUSTOMER DEFINED FUNCTIONS section. function customer_defined_run_cmds { /opt/OV/lbin/ovharg -start ov-server sleep 10 if [ -x /var/opt/OV/share/ovnm/bin/ovnm_start.sh ]; then /var/opt/OV/share/ovnm/bin/ovnm_start.
Appendix F: Manual Operations on HP NonStop Server OVNM provides interactive GUIs, which make the installation, upgrade, starting and stopping of OVNM components easy. In the event you are not able to use the OVNM Workstations GUIs, you can perform the following functions manually.
NOTE: While making changes in the sample InstInfo file make sure that there is a space after the colon on each line. Follow the steps given below to create the InstInfo file on the workstation using the Host Installation Client: 1. Start the Host Installation Client. 2. Click NEW to create a new Instinfo file. 3. Go through the same process you would normally go through using the HIC, but instead of clicking INSTALL, click Add to Workstation.
Applying OVNM Patch Follow the steps given below to apply an OVNM patch. NOTE: The manual patch update should be attempted only when the Upgrade/Apply Patch feature provided with the OVNM Host Installation Client fails. Step A: Copying Installation Files 1. Switch to the directory on the workstation, where the FIXxxxx.FIX file is stored. CD Where, The FIXxxxx.FIX is the patch file. The< File Location> is the path where the FIXxxxx file is located on the workstation. 2.
Manual OVNM Un-Installation You can un-install OVNM from the HP NonStop host using the Delete HP NonStop Host option from the Host Installation Client interface on the workstation. However, if the un-install process fails, then you can un-install OVNM from the HP NonStop host manually. Follow the steps given below to perform a manual un-installation. Switch to the subvolume where OVNM is installed and execute the following command at the TACL prompt to uninstall OVNM from the HP NonStop host.
Appendix G: Sample InstInfo File Product: OVNM WorkSubvol: $SYSTEM.ZOVNM Appendix G Install_Subvolume: $SYSTEM.OVNM TCPIP_process_name: $ZTC0 Home_terminal: $VHS Process_prefix: OV OCC_Port: 5020 OVNM_Port: 5030 License_key: XXXXXXXXXXXXXXXXXXXX Guardian_user: SUPER.
EMON_DIST02_ProcessName: DO2 OCC_DIST01_Collector: $0 OCC_DIST01_Filter: $SYSTEM.OVNM.PASSALL OCC_DIST01_CPU: 0 OCC_DIST01_Priority: 150 OCC_DIST01_Name: SDIST01 OCC_DIST01_ProcessName: DAL OCC_DIST02_Collector: $ZLOG OCC_DIST02_Filter: $SYSTEM.OVNM.
SecondaryTaclPrompt: 1 b24options: 0 closetdf: NO b24linelstobj: NO b24linklstobj: NO b24processlstobj: NO b24stationlstobj: NO b24systemlstobj: NO InstallationDate: AUGUST 2, 2011 2:19:59 LastModifiedTime: AUGUST 2, 2011 2:19:5 The following table lists and explains the various fields available in the Instinfo file. Table 3 INSTINFO Parameters Parameter Description Default Value Product Specify the name of the product as OVNM WorkSubvol Specify the name of the work subvolume.
Table 3 INSTINFO Parameters Parameter Description Default Value NNM To specify if NNM is also installed. Can have a value of Yes or No. Yes specifies that NNM is installed on the workstation. If NNM is not installed, the value is specified as No. Highpin To run the gateway process in Highpin. Can have a value of ON or OFF. ICE_Option To enable the monitoring of the ICE subsystem. Can have a value of Yes or No. FileSys To generate alerts if a file does not exists or when a threshold is violated.
Table 3 INSTINFO Parameters Parameter Description Default Value EMON_DIST01_Collector The first default event source (collector) for OVNM filter. The default is $0. EMON_DIST01_Filter The name of the OVNM filter file being The default is PASSALL filter. used for filter ... You can define maximum three filters. EMON_DIST01_CPU The CPU on which the distributor process The default value is same as specified in will run. PrimaryCpu.
Table 3 INSTINFO Parameters Parameter Description Default Value OCC_DIST02_ProcessName Name of the distributor (DIST02) process. Mail_Option To enable or disable e-mail feature. Can have a value of Yes or No. Email_Trace To configure tracing. Options available are Error, None and Progress. Error is the default value Email_QreadIntervalSec How often the host application is to pick The default value is 30 seconds. up queued mails. Specify a value between 1 – 36000 seconds.
