HP Operations Agent for NonStop User Guide Part number: 540074-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 Features ..................................................................................................................................................... 8 Before You Begin ........................................................................................................................................ 8 Audience ...................................................................................................................................................
6 Event Delivery Management 6-1 Managing the Connection ..................................................................................................... 53 6-2 Broadcast Mode ................................................................................................................... 54 6-3 Primary/Backup Mode .......................................................................................................... 55 6-4 Mixed Mode ................................................................
Appendix O: Configuration File Parameters Parameters for MAILCONF File ........................................................................................................... 125 Parameters for MONCONF File .......................................................................................................... 126 Appendix P: Threshold Linking Appendix Q: SQL Database feed Appendix R: Support for IPv6 IPv6 Parameters for ELKCONFA & ELKCONFO..............................................................
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 1-1 OVNM Enterprise Management...............................................................................................
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 4-21 OVNM Host Management Client Dialog Box Tools Menu................................................................. 42 4-22 OVNM Host Response for Starting Adapter Portion Dialog 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. OVNM User and Installation Guide provides information about how to install and get started with the product.
Organization Sr. No Chapter Name Description Chapter 1. OVNM Overview Gives a brief overview of the OVNM Product. Chapter 2. OVNM Host Installation Client Gives instructions on how to use the OVNM Host Installation Client. Chapter 3. Default HPOM Tools and Policies Gives information on Operations Manager tools and policies provided with OVNM. Chapter 4. Overview of Host Management Client Gives instructions on how to use the OVNM Host Management Client. Chapter 5.
OVNM Documentation Map HP 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 OVNM product CD-ROM. All manuals are also available in the HP web server directory.
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 HP Operations PDF PDF SMART Plug-In SPI for TELCO PDF SPI for MQ-SERIES PDF SPI for BASE24 PDF About OVNM Online Help This preface describes online documentation for the HP OVNM graphical user interfaces (GUIs).
1 About OVNM 1-1 What is OVNM? HP Operations Agent for NonStop software (formerly called OpenView NonStop Server Management, and still known as OVNM) is designed as an out-of-the-box solution to provide seamless integration for managing an HP NonStop server-only environment or to bring NonStop server data into larger multi-platform management systems. As its name implies, OVNM is designed to work with HP Operations software running on either the Microsoft® Windows® or the UNIX® operating system.
2 OVNM Host Installation Client The OVNM Host Installation Client is a Windows based interactive GUI, which is used to automate the procedures like installation and modifications on the HP NonStop node. This section details the various functionalities of the Host Installation Client. 2-1 Starting Up To start the OVNM Host Installation Client, click the Start Programs HP OVNM NonStop Server Tools Host Installation Client option.
The following fields are displayed in the OVNM Host Installation Client dialog box. • Configuration Name: This field displays the name of the configuration where the OVNM Agent is installed. This is useful when you want to install multiple OVNM backend environments. Refer to Appendix E Installing Multiple Agents on Same NonStop for details.
2-2 Add New HP NonStop Host To add a new NonStop Host, click the New button on the OVNM Host Installation Client dialog box. The New OVNM Configuration dialog box is displayed. Figure 2-4 New OVNM Configuration Dialog Box For details on installing OVNM on a HP NonStop Managed Node, refer to section Installing OVNM on HP NonStop Server of the OVNM Installation Guide.
2-3 Modify HP NonStop Host Information To modify the host information, click the Modify button in the OVNM Host Installation Client dialog box. The Modify OVNM Configuration dialog box is displayed. Figure 2-5 Modify OVNM Configuration Dialog Box Make the necessary changes in the corresponding field(s) and click the Apply button.
For details on synchronizing the host with PC, refer to Tools section of this chapter. Use the Apply To Workstation button to add the modifications on the front-end, without making any changes to the backend. To revert back to the entries before modifications, click the Reset Fields button. NOTE: In case there is a change in the OVNM information, the respective configuration files at the backend will be updated only if the user clicks on the Apply button.
2-4 Upgrade Use the Upgrade button in the OVNM Host Installation Client dialog box to perform a full software release upgrade or apply a patch. Clicking the Upgrade button displays the Upgrade menu. Figure 2-7 OVNM Host Installation Client Dialog Box Upgrade Menu • Upgrade Release: The Upgrade Release option allows you to perform a full software release upgrade. Clicking on this option displays the OVNM Host Installation Client message box with the date when the OVNM product key will expire.
• Apply Patch: This option allows you to upgrade the software with a new patch or fix. Clicking on this option displays the OVNM Host Installation Client message box with the date when the OVNM product key will expire. Clicking the OK button in the message box displays the Apply Patch for Configuration dialog box. Figure 2-9 Apply Patch for Configuration Dialog Box Enter the User ID and Password and select the Upgrade File using the Browse button. Click the Apply button to initiate the process.
2-5 Delete HP NonStop Host Click the Delete button in the OVNM Host Installation Client dialog box to delete an existing host configuration. The Delete menu is displayed. Figure 2-10 OVNM Host Installation Client Dialog Box − Delete Menu You can select any of the following options. • Delete From Workstation This option can be used in case you have manually uninstalled the OVNM agent on the HP NonStop Server and want to remove the configuration from the workstation as well.
• Delete From Both This option can be used to completely remove a configuration from the front-end as well as the backend. The OVNM Host Installation Client confirmation box is displayed. Figure 2-13 OVNM Host Installation Client Confirmation Box Click the Yes button to delete the selected Host configuration, else click the No button. After removing OVNM from the HP NonStop Server, you should also clean up the lines of code that were added to the TACLCSTM file for the User ID that was used to start OVNM.
2-6 View Host Detail To view information about a host, click the View Detail button. This displays the View OVNM Configuration dialog box. Figure 2-14 View OVNM Configuration Dialog Box OVNM Host Installation Client Click the Close button to close the dialog box.
2-7 Import Host Configuration You can import the host configuration(s) from a .cfg file, using the Import button. The OVNM Host Installation Client confirmation box is displayed. Figure 2-15 OVNM Host Installation Client Confirmation Box Click the Yes button to continue with the import process. If you do not want to import, click the No button. Clicking the Yes button displays the Open dialog box. Figure 2-16 Open Dialog Box Select the .
2-8 Export Host Configuration You can export the Node Information, Managed Subsystems and Both to a .cfg file using the Export button. The Export menu is displayed. Figure 2-18 OVNM Host Installation Client Dialog Box Export Menu You can select any of the following options. • Export Node Information: To export only the Node information. • Export Managed Subsystems: To export only the Managed subsystems information. • Export Both: To export Node and Managed subsystems information.
The Save As dialog box is displayed when you click the Yes button. Figure 2-21 Save As Dialog Box In the displayed Save As dialog box, the default file name NodeConfig.cfg is seen in the File name box. To export HP NonStop Host(s) configuration(s) with the default file name, click the Save button or change the file name and then click the Save button. This completes the export procedure. NOTE: The import and export utilities can be used to transfer host configurations from one workstation to another.
2-9 Tools Use the Tools button in the OVNM Host Installation Client dialog box to get token files or to synchronize Host with PC. Clicking the button displays the Tools menu. Figure 2-22 OVNM Host Installation Client Dialog Box Tools Menu • Get Token Files The Get Token button gets enabled once a node is added to the Managed Host list. This button can be used to obtain EMS token files from the selected HP NonStop Host.
Enter the User Name, Password and Token Files Location in the corresponding boxes. If you are using Xypro, you can also enter the Secondary Command and Secondary Password. Both of these fields are optional and even if you enter a Secondary Command, the password is still optional. Depending on the prompt character that is returned as part of the Xypro option, you may need to adjust the Secondary Tacl Prompt value. Then, click the OK button.
Then click the OK button. The OVNM Host Response for Synchronizing Host information with PC dialog box is displayed with the status information for the synchronization with the Host. Figure 2-26 OVNM Host Response for Synchronizing Host information with PC Dialog Box Click the OK button to close the dialog box. To save the information, click the Save button. • Get Pak File The Get Pak Files option is intended to be used when the HP Support staff requires additional files to research a problem.
The OVNM Host Response for Getting Pak File dialog box is displayed giving the status that the created PAK file is being transferred to the workstation. After the binary data transfer is complete, the OVNM Host Installation Client message box is displayed with the information that the PAK file has been successfully retrieved in the C:\Program Files\OVNM\Back End folder. Click the OK button to continue.
The OVNM Host Response for Getting Pak File dialog box is displayed with the information that getting of PAK file from Host is successful. Figure 2-29 OVNM Host Response for Getting Pak File Dialog Box Click the OK button, and then click the Save button, to save your changes.
3 Default Operations Manager (HPOM) Tools & Policies The default Operations Manager tools and policies are used to perform command and control functions for critical events using the HP Operations Management Console along with commands to start and stop OVNM agents. However, OVNM also provides the facility to control the monitoring of events as objects. The OVNM Object Configuration Client (OCC) interface allows the user to configure objects & thresholds for monitoring.
3-1-1 NonStop Operator Tools For details on Operations Manager tools, refer to Operations Manager Tools in the OVNM Event Management Guide. Figure 3-2 Operations Manager Default OVNM NonStop Operator Tools NOTE: To run the tools, select the tool name in the Operations Manager Message Browser and enter the node name on which the command is to be executed.
OVNM provides a set of pre-configured policies, which can be accessed using the Operations Manager interface. You can also create user-defined policies depending on your requirement. The policies are grouped into two categories: • OVNM-Event-Mgmt (OVNM-NonStop-Msgs): Policy pertaining to NonStop messages. • OVNM-Object-Mgmt (OVNM-OvMon-Msgs): Policy pertaining to OVNM monitored objects.
4 Overview of Host Management Client The OVNM Host Management Client is a Windows based interactive GUI, which is used to automate the HP NonStop host management procedures like starting and stopping OVNM agent. 4-1 Starting Up To start the Host Management Client, click Start Programs HP OVNM NonStop Server Tools Host Management Client Menu option. Figure 4-1 Starting Host Management Client The OVNM Host Management Client dialog box is displayed.
You can view the Configuration name, Node Name, IP Address, Installation Date and Version information for the selected Managed Host using the OVNM Host Management Client. The following functions can be performed using the OVNM Host Management Client.
4-2 Start Agent The Start Agent utility starts the OVNM agent on the HP NonStop host. 1. To start the OVNM agent, select the configuration on which the agent is to be started using the Configuration box in the OVNM Host Management Client dialog box, and click the Start Agent button. Figure 4-3 OVNM Host Management Client Dialog Box Start Agent Button 2. The Login to Host dialog box is displayed. Figure 4-4 Login to Host Dialog Box 3.
4-3 Stop Agent The Stop Agent utility stops the OVNM agent on the HP NonStop host. 1. Select the host using the Configuration box in the OVNM Host Management Client dialog box, and click the Stop Agent button. Figure 4-6 OVNM Host Management Client Dialog Box Stop Agent Button 2. The Login to Host dialog box is displayed. Figure 4-7 Login to Host Dialog Box 3. Enter the User Name and Password in the respective boxes in the Login to Host dialog box and click the OK button.
4-4 Status The Status utility enables you to view the status of the OVNM and OCC components on the HP NonStop host. 1. To start the process, select the Configuration name in the OVNM Host Management Client dialog box and click the Status button. Figure 4-9 OVNM Host Management Client Dialog Box Status Button 2. In the displayed Login to Host dialog box, enter the User Name and Password in the respective boxes and click the OK button.
4-5 View Info The View Info utility is used to get information about OVNM and OCC applications on the HP NonStop host. 1. To start the process, select the Configuration in the OVNM Host Management Client dialog box and click the View Info button. Figure 4-12 OVNM Host Management Client Dialog Box View Info Button 2. Specify the User Name and Password in the respective boxes in the displayed Login to Host dialog box and click the OK button.
4-6 Policy Report The Policy Report utility is used to generate a report, which contains information about all the policies/threshold(s) that have been deployed at the NonStop host. 1. To start the process, select the Configuration in the OVNM Host Management Client dialog box and click the Policy Report button. Figure 4-15 OVNM Host Management Client Dialog Box Policy Report Button 2.
3. The OVNM Host Management Client message box is displayed confirming the type of Policy Report to be created. The Policy Report utility allows you to either create a Brief or a Detailed version of policy report. Select the type of report to be created and click the OK button. Figure 4-18 OVNM Host Management Client for Generating Policy Report Confirmation Box 4.
4-7 Tools The Tools utility is used to check the communication between the HP NonStop Node and the Enterprise Management Server. To start the process, select the Configuration in the OVNM Host Management Client dialog box and click the Tools button. The Tools menu is displayed.
4-7-1 Start Enterprise The Start Enterprise option enables you to start the OVNM Adapter portion on the HP NonStop Server. 1. To start the process, select the Configuration in the OVNM Host Management Client dialog box and click the Tools Start Enterprise. 2. The Login to Host dialog box is displayed. Specify the User Name and Password in the respective boxes in the displayed Login to Host dialog box and click the OK button.
4-7-2 Start Monitoring The Start Monitoring option enables you to start the OVNM Client on the HP NonStop Server. 1. To start the process, select the Configuration in the OVNM Host Management Client dialog box and click the Tools Start Monitoring. 2. The Login to Host dialog box is displayed. Specify the User Name and Password in the respective boxes in the displayed Login to Host dialog box and click the OK button.
4-7-4 Stop Monitoring The stop Monitoring tool enables you to stop the OVNM Client on the HP NonStop Server. 1. To start the process, select the Configuration in the OVNM Host Management Client dialog box and click the Tools button. 2. Select the Stop Monitoring option from the displayed Tools menu. 3. The Login to Host dialog box is displayed. Specify the User Name and Password in the respective boxes in the displayed Login to Host dialog box and click the OK button.
4-7-5 Test Message The Test Message utility is used to check the communication between the HP NonStop Node and the Enterprise Management Server. 1. To start the process, select the Configuration in the OVNM Host Management Client dialog box and click the Tools button. 2. Select the Test Message option from the displayed Tools menu. 3. The Login to Host dialog box is displayed. Specify the User Name and Password in the respective boxes in the displayed Login to Host dialog box and click the OK button.
The OVNM Host Management Client message box is displayed with the information that the CLCTINFO and CLCTPAK files are generated and copied to the C:\Program Files\OVNM\Back End folder on the workstation. The file names are prefixed with the selected node’s name. For example, NODECLCTINFO and NODECLCTPAK files will be copied for \NODE. Figure 4-28 OVNM Host Management Client Message Box 5.
4-8 Import Node Configuration The Import Node Configuration utility in the OVNM Host Management Client dialog box helps you to import HP NonStop Host(s) configuration(s) from a file. Figure 4-31 OVNM Host Management Client Dialog Box Import Node Configuration Button 1. Select the Configuration in the OVNM Host Management Client dialog box. 2. Click the Import Node Configuration button to display the OVNM Host Management Client confirmation box.
4-9 Delete Node Configuration The Delete Node Configuration utility removes the selected Managed Host configuration from the workstation. To delete a node configuration, perform the following steps. 1. Select the Configuration to be deleted and click the Delete Node Configuration button Figure 4-33 OVNM Host Management Client Dialog Box Delete Node Configuration Button The OVNM Host Management Client confirmation box is displayed. Figure 4-34 OVNM Host Management Client Confirmation Box 2.
5 Default Operations Manager (HPOM) Applications & Message Templates The default HPOM applications and message templates provided with OVNM are used to perform command & control functions for critical events using the HPOM Management Console along with commands to start and stop OVNM agents. However, OVNM also provides the facility to control the monitoring of events as objects. The OVNM Object Configuration Client (OCC) interface allows the user to configure objects & thresholds for monitoring.
Default Operations Manager (HPOM) Applications & 5-1-1 NonStop Operator Tools Figure 5-2 HPOM Default OVNM NonStop Operator Tools 5-1-2 OVNM Tools Figure 5-3 HPOM Default OVNM Tools NOTE: To run the tools, select the node name and drag and drop it on the tool to be executed in the Application Group submap. For details on HPOM applications, refer to Chapter 4: HPOM Applications in the OVNM Event Management Guide.
5-2 Default OVNM Message Templates A Message template or a policy can be defined as a set of one or more specifications and/or rules that help automate network and service administration, and provide consistent automated administration across a network. After installation, OVNM provides the default message templates that can be used as-is to manage your HP NonStop environment. The templates can be accessed using the HPOM Administrator’s User Interface.
6 Event Delivery Management 6-1 Managing the Connection If the connection between Enterprise Management Server and the HP NonStop Server(s) is lost due to any reason, the event messages generated by the HP NonStop server(s) are not forwarded to the Enterprise Manager Message Browser(s). If the connection is lost between the Enterprise Management Server and OVNM, Store and Forward (SAF) files are used to store the events until the Enterprise Manager services are started.
6-2 Broadcast Mode The broadcast mode is used to send NonStop event messages to multiple Enterprise Management Servers. The figure below shows a monitoring scenario where the HP Operations Manager (HPOM) Servers are configured for Broadcast mode.
Catch-up will only happen if MSGQUEUING is enabled otherwise the messages will be lost because the OVNM will not send any Goback request to the NonStop. The configuration changes on the Enterprise Management server to support broadcast mode require modifying the ovnm_start script. 6-3 Primary/Backup Mode In the Primary/Backup mode, OVNM is configured to send NonStop Events to a pair of Enterprise Management Servers, one as Primary and the other as Backup.
Table 6-1 Primary/Backup Mode for Guaranteed Event Delivery Backup Server Action Enterprise Manager Service OVNM Connection to NonStop Server Enterprise Manager Service OVNM Connection to NonStop Server Up Down Up Down The first Enterprise Manager Server OVNM Agent to register with the NonStop will send a catchup request to recollect the lost messages Up Down Down Up SAF file will be created on Backup Server till the Enterprise Manager services on Backup server are started again Up Down Do
6-4 Mixed Mode From OVNM 4.2 release, the single source feed (SSF) Elink will run in mixed mode. This means that OVNM is configured to broadcast messages to multiple servers AND to Primary/Backup server. OVNM can support one Primary server, one Backup server and unlimited broadcast type servers. Figure 6-3 Mixed Mode If there are a number of adapters or clients, only one of them can be configured as Primary or Backup server. Others can be configured as broadcast servers.
6-5 Communication Process in the OVNM Environment The Elink process is the main communication process in the OVNM environment. The figure below describes the communication process between the HPOM Management Server and the HP NonStop Server(s) as an example.
The Elink configuration file also contains the following parameters. These parameters check the connectivity between the front-end Elink and the NonStop Elink. ALIVECOUNT: The retry count after which the connection is confirmed lost. ALIVEPROBE: The time interval in seconds after which a heartbeat probe is sent. For example, Aliveprobe will probe the NonStop Hosts every X seconds and will declare a host as unavailable if Y consecutive probes are not acknowledged.
7 Troubleshooting OVNM 7-1 General Troubleshooting Outright Installation Failures & Security Access Rights If the installation fails, make sure that the following are true. • Your logon ID has read access to the restored installation files. • Your logon ID has permission to create files in the destination subvolume. • NonStop-Server node group & NonStop message group permissions are set for the right user. Availability of Resources • You have sufficient disk space (60-90 MB).
7-2 Specific Troubleshooting This troubleshooting section has been provided to assist in diagnosing OVNM integration problems with Enterprise Manager Server. The figure illustrates the message flow from the HP NonStop Server to the Enterprise Manager Message Browser.
7-2-1 Messages not Getting Populated on HPOM Event Browser 7-2-1-1 Linux The following steps are intended to assist in diagnosing why NonStop messages are not flowing to the HPOM Message Browser. Check Connectivity between HPOM and NonStop Server To check the connectivity between the HPOM Management server and the NonStop server, run the ovnm_status.sh script. # /opt/OV/ovnm/bin/ovnm_status.
• Edit the Elink.cfg located in the /opt/OV/ovnm/bin directory and modify the SET ELINK TRACE parameter to PROGRESS. A part of the elink.cfg file has been provided for your reference. ######### ELINK Configuration parameters.######## #### Possible values could be #### PROGRESS - For all types of messages #### WARNING - For WARNING messages only #### ERROR - For ERROR messages only #### NONE - For no messages SET ELINK TRACE • PROGRESS Now restart elink trace. # .
OVNM provides the NOCATCHUP facility, which can be used in case the user is not willing to retrieve the events logged during any kind of connection outage. In this case, no catch up request will be sent for the particular node. Follow the steps below to configure the HP NonStop node in Nocatchup file. 1. Access the Nocatchup file available at “C:\Program Files\HP OpenView\bin” location. 2. Add the HP NonStop node name for which NOCATCHUP facility is to be activated using the following syntax.
A Green icon next to the node name in the window indicates that the connection is established with the remote HP NonStop Elink. In case the remote HP NonStop Elink is not up, the icon will be seen in Red. • If connection is Green, verify that the Operations Manager environment is running and that the Operations Manager Console can receive messages other than NonStop Server Events. • From the command prompt, execute the following opcmsg command.
• If connection is red, verify that the OVNM NonStop Server Components are running by obtaining status of OVNM components on the NonStop Server. This can be accomplished using the Status button in the OVNM Host Management Client. Start the Host Management Client using the StartProgramsHP OVNMNonStop Server ToolsHost Management Client option. Figure 7-5 Host Management Client Option From the displayed OVNM Host Management Client window, select the Status button for NonStop Server to be checked.
• If both Elink Ports 5020 and 5030 are red then the Elink session between the Operations Manager Management Server and the NonStop Host has failed. Stop and Start the OVNM Agents on the Operations Manager Server using the Start Agents and Stop Agents options in the StartProgramsHP OVNMManagement Server Tools menu. Figure 7-7 Management Server Tools Menu Check for the HP OVNM SPI Service either by using the ‘net start’ command or from the Services window.
Generate a Test message using the Test Message button in the OVNM Host Management Client while Elink is being traced. If no message is traced, check the NonStop EMS Log $0. If Test message are in the EMS Log, then the problem is with the OVNM components on the NonStop Server. If message are seen in the Elink trace, but are still not seen on the Operations Manager Console, try tracing the OVNM Smart Plug-in process.
Option 3: NOCATCHUP OVNM provides the NOCATCHUP facility, which can be used in case the user is not willing to retrieve the events logged during any kind of connection outage. In this case, no catch up request will be sent for the particular node. Follow the steps below to configure the HP NonStop node in Nocatchup file. 1. Access the Nocatchup file available at “C:\Program Files\HP OpenView\bin” location. 2.
Appendix A: 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 B: Sample InstInfo File Product: OVNM WorkSubvol: $SYSTEM.ZOVNM Appendix B 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:59 Appendix B: Sample InstInfo File 76
• Product Specify the name of the product as OVNM. • WorkSubvol Specify the name of the work subvolume. This field is created when a node is added using the Add to Workstation field in the Host Installation Client. • Install_Subvolume • Appendix B The subvolume where OVNM is to be installed. TCPIP_process_name The name of the TCPIP process that will be used to communicate between the NonStop and the external servers for the OCC, ObjectMap, HPOM, etc.
• MainPriority The priority of the main OVNM process. The default value is 160. • PrimaryCpu Primary CPU of the main OVNM process. The default is 0. • BackupCpu CPU of the main OVNM process. The default is 1. • LogToCollector The collector where all the application events will be logged. Default is $0. • NSDB_Location Location of the NSDB subvolume. (For the Telco interface only) • STAT_Subvolume Location of the STAT subvolume.
• OCC_DIST01_Collector The default event source (collector) for OCC filter. The default is $0. • OCC_DIST01_Filter The name of the OCC filter file being used for filter - ... You can define maximum three filters. The default is ZTFLTRO filter. • OCC_DIST01_CPU • Appendix B CPU on which the distributor (DIST01) process will run. OCC_DIST01_Priority The priority of the distributor process. • OCC_DIST01_Name Name of the distributor.
• MQCONFIG_01 This is the name given to an MQ environment. It is only used within OVNM. There can be up to 20 MQ environments defined. There are five parameters defined for each environment, all ending with a 2-digit number. • MQMACNINIFILE_01 This is the name of the INI file used by the MQ environment. For MQ versions prior to 5.3, it will be a Guardian file. For newer versions of MQ, it will be an OSS file.
Appendix C: OVNM Utilities OVNM provides various utilities, which can be used either through the Host Management Client, or manually by using the TACL macros. The information in this chapter explains the various utilities and how to use them manually. For details on how to run the OVNM utilities through a GUI, refer to the Host Management Client topic.
Elink Process Name $OVELK $DATA05.OVNM.ELINK Master Monitor Process Name $OVMON $DATA05.OVNM.ORMMST Server Monitor Process Name $OVM00 $DATA05.OVNM.ORMCOM Server Monitor Process Name $OVM01 $DATA05.OVNM.ORMCOM List Process Name $OVLST $DATA05.OVNM.LSTCOM Guardian Mail Service Process Name $OVMLS Tacl Gateway Process Name $OVGTA MQ Series Process Name $OVMQL Not being used. Event Correlation Process Name $OVECL $DATA05.OVNM.
CLCTOVNM CLCTOVNM is used to create specific information about the customer's environment, including their database. To run the utility on the HP NonStop server, you need to switch to the volume.subvolume where OVNM is installed. To use the utility, use the following command at the prompt: Run CLCTOVNM $DATA05 OVNM 12> run clctovnm Purge $DATA05.OVNM.CLCTINFO Have you been asked to capture the OVNM Database? y Looking for PAK... Collecting OVNM configuration information... This will take a few minutes....
STATOVNM The STATOVNM TACL utility will show the status of the various OVNM components on the HP NonStop server. To run the utility on the HP NonStop server, you need to switch to the volume.subvolume where OVNM is installed. To use the utility, use the following command at the prompt: Run STATOVNM $DATA05 OVNM 14> run statovnm -------------------------OVNM STATUS UTILITY -------------------------Data extracted from configuration in $DATA05.OVNM.
Email is not configured. OVNM TACL Gateway process ($OVGTA) is up and running. OK MQ Series monitoring is not configured. MQ Series was not activated by customer. OK Event Correlation process ($OVECL) is up and running. OK -----------------------OVNM STATUS UTILITY -----------------------Data extracted from configuration in $DATA05.OVNM.
ALTROVNM The ALTROVNM utility allows clients to change certain attributes within the OVNM environment. To run the utility on the HP NonStop server, you need to switch to the volume.subvolume where OVNM is installed. To use the utility, use the following command at the prompt: Run ALTROVNM $DATA05 OVNM 15> run altrovnm Getting current values... -------------------OVNM ALTER UTILITY -------------------1. Change the OVNM license key : XXXXXXXXXXXXXXXXXXXX 2. Change the Console License key : null^value 3.
or OK to accept these settings : 7 Enter the 2-character process prefix : OV -------------------OVNM ALTER UTILITY -------------------: XXXXXXXXXXXXXXXXXXXX 2. Change the Console License key : null^value 3. Change the TCP IP process name : $ZTC0 4. Change the OCC Port : 7370 5. Change the OVNM Port : 7350 6. Change the Home Terminal : $ITS 7. Change the Process Prefix : OV 8. Change the FileSys Option : NO 9. Change the Page Active Flag : No Appendix C 1. Change the OVNM license key 10.
*WARNING* - Unable to locate Email_Server_IP. Purge $DATA05.OVNM.INSTINFO Creating new parameter files...
ZTPAKIT ZTPAKIT is a tool to PAK specific files and send to product support to troubleshoot a problem. This routine will locate the PAK object file and then execute the necessary PAK commands to create the PAK file. It will also display a message at the end telling them what file was created. If you already know how to use the PAK utility, there is no need to use this TACL routine. NOTE: This routine should be executed ONLY when directed by support.
• The ZTMONCMD command with the following parameters will turn off all monitoring for all PATHWAY thresholds. OVNM will close all of its opens of Pathmon processes until you ACTIVATE the thresholds using this utility again. RUN ZTMONCMD SUSPEND PATHWAY ALL • The ZTMONCMD command with the following parameters will re-activate the monitoring of the specified environments.
This message is generated based on the above action: ---------------------------------------------------------------------------04:10 15SEP09 001,00,750 OVNM : MONITORING FOR MANAGER (PWY:ALL) SUSPENDED DUE TO OPERATOR REQUEST, USER: 050,003, TERM: \NODE1.$ZTN1.#PTSMVZL. ---------------------------------------------------------------------------- -----------------------------------------------------34> run ztmoncmd Using: $OVMON 1. SUSPEND ALL PATHWAY MONITORING 2. ACTIVATE ALL PATHWAY MONITORING 3.
CHECKPWY The CHECKPWY utility is executed during installs to investigate the MAXSPI values in the various PATHWAY systems. If it detects PATHWAY environments with a MAXSPI setting too low, it provides a warning stating the MAXSPI value should be increased. Increasing the value of MAXSPI requires the PATHWAY environment to be bounced, so these needs to be scheduled. This TACL routine can be executed at any time.
ZTCHGSCH The ZTCHGSCH (Change Schedule) Tacl routine is used to verify the updates to the SCHEDULE and HOLIDAY files and then send a command to the application to get the new values loaded. Failure to use this Tacl routine will cause the monitoring programs to use the old data. To run the utility, specify the following command: RUN ZTCHGSCH Edit Schedule; na; e TEXT EDITOR - T9601D20 - (01JUN93) CURRENT FILE IS $DATBT1.OVNM.
Appendix C: OVNM Utilities 94
Appendix D: Batch Utilities for Thresholds OVNM provides the following command line utilities that assist in adding and deleting thresholds from the database: • BATCONF • DELCONF BATCONF The BATCONF or the Batch Configuration utility allows you to add thresholds to the database in a batch mode. This utility always lags behind the features in the Object Configuration Client, so there are some features available in the Object Configuration Client that are not available in BATCONF.
The following commands are supported.
DELCONF The DELCONF or the Delete Configuration utility is used to Delete thresholds from the database. When a configuration record is deleted using the utility, all the corresponding objects and the linked records in the rest of the database are also deleted. To execute the utility, enter the following command: RUN DELCONF / IN ORMCONF / [] [
Appendix E: Installing Multiple Agents on Same NonStop The Configuration Name parameter in the Host Installation Client specifies the name of the configuration where the OVNM Agent is installed. This is useful when you want to install multiple OVNM Agent environments on the same HP NonStop system. However, this can cause problems with Enterprise Management systems.
• f. If you have multiple environments and they consume each other’s events, and one of the environments has a recovery or email associated with that threshold, then both environments could perform the recovery or send the email. The OVNM subvolumes used for multiple environments cannot be duplicated on the same HP NonStop Server. g. The Work subvolumes should be not duplicated across multiple environments.
Appendix F: Sample Session for Adding HP NonStop Nodes This section gives a sample session for adding HP NonStop Nodes, 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_add_nodes.sh OVNM for HP NonStop Server Configuration Please enter the fully qualified name of the HP NonStop Node Name (NODE.domain.com) NODE.
Name Resolution for Node Fails: On HP UX # ./ovnm_add_nodes.sh OVNM for HP NonStop Server Configuration 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 for name resolution. This can take a few minutes. Please be patient... Name resolution for NODE.hp.com failed. Adding the node entry in the hosts file..
Name Resolution for Node Fails: On SUN SOLARIS # ./ovnm_add_nodes.sh OVNM for HP NonStop Server Configuration 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 for name resolution. This can take a few minutes. Please be patient... Name resolution for NODE.hp.com failed. Please specify the name resolution scheme which you are using, from: 1) DNS 2) files 2 Adding the node entry in the hosts file..
Appendix G: Transporting Thresholds OVNM provides tools that assist in migrating common thresholds from one HP NonStop node to another. These tools are: • MOVEDB • ZTEXTRCT • ZTINSERT • AutoRpt (Auto Maintenance Report) • ZTMIGRAT MOVEDB The MOVEDB utility was developed to allow customers to move OVNM database from one location to another without having to re-enter the thresholds. This would be used when multiple HP NonStop nodes need to be configured with the same thresholds.
d. Enter the OVNM license key. Hit for . You should have a separate license key for the remote node. It is possible that if you are evaluating the product, you will use the same key for all nodes. The response to this prompt must be 20 characters. If you want to use the current key for the new system as well, just press the key. Hit for $xxxx. The utility will pick up the TCP/IP process from the OVNM database specified in the first prompt.
ZTEXTRCT / ZTINSERT The ZTEXTRCT and ZTINSERT tools are used together. The advantage of using these tools rather than MOVEDB is that you can leave the OVNM systems running on both the sending node and the receiving node. The first tool, ZTEXTRCT, is used to extract the thresholds from a node. The second tool, ZTINSERT, is used to insert the thresholds into the second node. To run ZTEXTRCT, switch to the OVNM subvolume and run it. For example: 32> volume $oss.ovnm 33> run ztextrct Purge $OSS.OVNM.
Processing EMS;EVENT;EXECUTE-DEFINED-ACTI;TANDEM.258.*; Duplicate skipped Processing EMS;EVENT;EXECUTE-DEFINED-ACTI;TANDEM.258.999; Duplicate skipped Appendix G Processing EXPAND;LINE;NOT STARTED;$*;$* Duplicate skipped Processing EXPAND;PATH;NOT STARTED;$*;$* Duplicate skipped Processing FILESYS;FILE;FILE EXISTS;$SYSTEM.SYSTEM.
Processing TMF;AUDITTRAIL;CANNOT ROLLOVER;*;0 Duplicate skipped Processing TMF;AUDITTRAIL;OVER FLOW IN USE;*;0 Duplicate skipped Processing TMF;TMF;HUNG TRANSACTIONS;*;0 Duplicate skipped Processing TMF;TMF;TMF IS STOPPED;*;0 Duplicate skipped Processing TMF;TRANSACTIONS;TRANSACTION IS HUNG;*;0 Duplicate skipped Processing X25;LINE;NOT STARTED;*;0 Duplicate skipped Processing FILESYS;FILE;PROGID;$VOL.BATCONF.PROGID;0 Duplicate skipped Processing FILESYS;FILE;AUDITED;$VOL.BATCONF.
• Polling intervals match • Scheduled start times match • Scheduled stop times match • Group/subgroups match Appendix G If any of the above has different values in the ORMEXTR file then what is in the database on the receiving side, the threshold will be added. If they all match, the threshold will be skipped.
AutoRpt (Auto Maintenance Report) The AutoRpt program generates a simple report showing what thresholds are defined with auto maintenance. To run AutoRpt, switch to the OVNM subvolume and run it. For example: 3> volume $oss.OVNM 4> run autorpt / in ormconf [, out ] / The program will open the ORMCONF file and produce a report showing all the thresholds that have the auto maintenance option defined. The report will print a ‘section’ for each threshold.
ZTMIGRAT To start using the function, create and edit the CUSTMIGS (Customer Migrations) file. This file will contain a list of nodes and their corresponding locations ($volume.subvolumes). For example: \node1$vol.ovnm \node2$vol2.ovnmx OVNM can be installed on a different subvolume on each node, or on the same subvolume. Once the CUSTMIGS file is created, all you have to do is run it.
Appendix H: Customizing OVNM Configuration Files This section describes the procedures to make custom changes to the OVNM configuration files that are not supported via the OVNM Host Installation Client or the ALTROVNM routine. The Host Installation Client allows you to change parameters like the filters and the collector to be used by OVNM to write the messages. NOTE: Changes to these files should be performed only when you are instructed to do so by the Support Staff.
SAMPCHGS is just a sample, showing how this TACL routine can be coded.
If the OCCCONF file is updated with this command, when you use the Object Configuration Client to turn node monitoring off, ALL EMS thresholds will also be disabled. When you turn node monitoring off, then as the EMS messages are received by the ACC program, it will toss them away. There is no automated method of reprocessing those events while node monitoring has been turned off.
Appendix I: Japanese Character Set Support The system is not configured to support the Japanese Character Set when it is installed, since the default installation is to replace any unprintable character with a period. If you do not want the system to automatically convert unprintable characters, you have to modify a parameter in the OVNMCONF file.
Appendix J: Elink Messages in HPOM This section provides a list of common Elink messages along with explanations. 1. Connection lost with remote Node This alert is generated by OVNM_SPI process. This implies the connection is lost with the specified HP NonStop node. It could be due to OVNM component on the NonStop is brought down or network outage between the front-end OVNM system and NonStop system.
Appendix K: Internal Messages Generated by OVNMSPI Enhancements have been made in the OVNM SPI runtime parameters to perform the following functions related to HPOM events generated by the OVNM SPI process. You You can use the ovnm_spi binary in order to alter the runtime parameters. 1. Enabling/Disabling HPOM Messages You can use the following runtime parameter to enable or disable the HPOM messages generated by OVNM SPI process. -internalmsg By default the parameter is ON. 2.
Table 2 Internal Messages Logged to HPOM by OVNM Message Description Corrupt multi bytes events received. field is invalid Corrupted messages are logged in log file and for each corrupted message, message “Corrupt multi bytes events received. field is invalid” will be logged in log file as well as in HPOM.
Appendix L: EMS Burst Suppression The following methods can be used to suppress duplicate EMS messages from being processed and/or sent to Operations Manager. Collector Level Burst Suppression The first method involves suppressing the duplicate EMS messages at the collector level. You will need to use EMSCCTRL to configure this option. This method eliminates the workload from OVNM to implement burst suppression. Refer to the appropriate HP documentation for more details. 2.
When setting the values for THREADTABLECOUNT and BURSTLINKCOUNT you should always leave plenty of extra room. If either of those tables becomes full, the burst definition feature may not work properly. BURSTCLEANUP-INTERVAL is used to tell OVNM how often to spin through the various tables to delete entries that have expired (are longer than the burst reset time or the “within” time of the burst definition). The default for this parameter is 1 hour (60 minutes). The value you specify here is in MINUTES.
When the “ignore burst” message is generated, it will show you how many events were suppressed since the last time its counter was reset. The counter can be reset after a BurstCleanUp Interval as well, so this count may not include every single EMS message that was suppressed prior to the burst being detected. The Subject will only be reported if a specific subject is involved in the burst. When the burst reset period ends, OVNM will generate event 144 (for process until) or 145 (for ignore until).
Reset This is used to define when the burst should be considered as expired. Once a burst has been detected, no more EMS messages will be processed until after the amount of time defined in this field. The start of the burst will be defined as the EMS generation time of the first EMS message that is part of the burst criteria.
Appendix M: View Detail TACL Routines To modify the information displayed for an Object in the OVNM ObjectMAP, you need to update the following Tacl routines. Also, it is required to reapply the changes once OVNM is upgraded from previous to newer versions. Pass the following parameters to modify the routines: • Threshold Identifier • Object type • Subject • Manager This section provides a list of subsystems mapped with the corresponding TACL routines.
Appendix N: Log Success/Failure of User Defined Command for Recovery This section explains the procedure to write the Tacl routines that will notify OVNM in a way so OVNM can correctly determine if the Tacl execution was successful. A sample Tacl routine called SAMPTACL in OVNM shows the correct way to code a Tacl routine. To test this feature, create Filesys/File thresholds for files with certain key words in their filename and use the following user-defined command: RUN $vol.OVNM.
3. Click the Actions button. This displays the Actions dialog box. Select the User define command option from the Command drop-down menu. Specify the user command in the second Command box. The Subject (%s%) field in the event will contain what is defined in the “Object” field (i.e. the file name $DSMSCM.OVNMTEST.GOODTEST). Figure 9 Actions Dialog Box Select the value as Default in Success and Failure drop down list available under the Log area and click the OK button.
Appendix O: Configuration File Parameters This section contains information about the parameter that you have to add to the mailconf and monconf files for configuration of the OVNM product. Parameters for MAILCONF File Table 4 Parameters for MAILCONF File Parameter Description Default Value SERVER Designates the IP address of the remote mail server SERVERNAME Designates the DNS name of the remote mail server. You must specify SERVER or SERVERNAME, but not both.
Parameters for MONCONF File Table 5 Parameters for MONCONF File Parameter Description/Allowed Value FileSys • • Default Value Yes: Generate alerts if file does not exist OR threshold violated No: Generate alerts ONLY if file exists AND threshold violated SkipEMS • • • Yes: Skip first ems message if normal and using eEvents All: Skip first ems message if normal No: Generate first ems message if normal NO Live • • Yes: Send messages to ObjectStats No: Do not send messages to ObjectStats unless req
Table 5 Parameters for MONCONF File Parameter Description/Allowed Value B24LINELSTOBJ, • B24LINKLSTOBJ, B24STATIONLSTOBJ, B24PROCESSLSTOBJ, and B24SYSTEMLSTOBJ • Default Value YES: Use the LISTOBJECTS command with BASE24 NCP. When set to YES ORM retrieves a list of objects from NCP based on object type and threshold. Example: "LISTOBJECTS STATION *, STOPPED". The list is refreshed as required by polling interval of current object, i.e.
Table 5 Parameters for MONCONF File Parameter Description/Allowed Value Default Value THRESHOLDLINKING Reduces the amount of subsystem I/O needed to service multiple YES thresholds for a given object. Instead of sending a STATUS request per threshold we send only one request, then service all "linked" thresholds for that object from the single response. All thresholds for a given linked object are also assigned to the same ORM monitoring process as well. By default the value is set to YES.
Appendix P: Threshold Linking This section contains information about a parameter that allows you to configure OVNM so it will minimize the number of times it requests information about an object. This option must be manually turned on. The default operation is to continue to work as it did in previous releases. This option is only supported for Base24, Filesys and NetBatch thresholds.
Appendix Q: SQL Database feed A single threshold has been added that allows users to begin testing and evaluating a data feed from OVNM into a SQL database. Currently, the SQL database must be off platform. The SQL database will require the use of the Data Analyzer product in order to use this information. The threshold is the TCPIP/Process/Process Stats threshold. This threshold will never create a violation. It cannot be used to automate actions. It will not be able to generate emails.
Appendix R: Support for IPv6 This section contains information about the parameter that is required when using IPv6. The Front End applications don’t need any changes in configuration to use IPv6. The TCP process should be configured for supporting IPv6 connections. There is a parameter that needs to be included in the ELKCONFA & ELKCONFO files i.e. INET6. The ELKCONFA file would be updated if the Windows applications (OCC, ObjectMap, etc) are going to be using IPv6 IP addresses.
Index alert, 58 alivecount, 59 aliveprobe, 59 ALTROVNM, 86 apply patch, 19 audience, 8 auto-catch-up, 53 B BATCONF, 95 broadcast, 58 Broadcast Mode, 53 BUILDCNF, 111 G Get Pak File, 28 get token files, 26 I import host configuration, 23 import node configuration, 48 INFOOVNM, 81 INSTALL macro, 70 J japanese character set, 114 C L CHGSYS, 103 CLCTINFO, 47 CLCTOVNM, 83 CLCTPAK, 47 collect info, 46 CUSTMIGS, 110 LSTCOM process, 95 D default OVNM applications, 50 DELCONF, 95, 97 delete from both, 21 de
Document Feedback Form We would appreciate your comments on the OVNM User and Installation Guide. After you have read the Guide and used the software, please take a few moments to complete this form and return it to appropriate HP product support service. 1. The organization of the Guide makes it easy to locate topics quickly. Strongly Disagree 1 2. Strongly Agree 2 3 4 The appearance of the pages makes it easy to locate information quickly. Strongly Disagree 1 3.
9. The level of writing in this book is: Too Basic Just Right Too Technical (Please be specific.) Do you have any other suggestions for improvement? Document Feedback Form 10.
