Guide for Setting Up the Availability Manager to Forward Events to OpenView This guide contains the following sections: Section 1 - Overview and Steps for Installation and Setup Section 2 - Availability Manager OpenView Template Installation Instructions Section 2 contains two sets of instructions, for a Management Server that runs on either a UNIX or a Windows system. 1 Overview and Steps for Installation and Setup This section of the guide covers the steps necessary to configure both the Availability Manager and OpenView Operations (OVO) Server so that Availability Manager events are forwarded to an OVO Server. The Availability Manager Data Analyzer signals events based on data that it collects from OpenVMS systems. If you want, you can configure these events so that the Availability Manager forwards the event to an OVO Server for further processing. In this case, the Data Analyzer uses the OpenView Management Agent to forward the events to the OVO Server. The Availability Manager acts as a proxy server for the OVO Server. As such, the Availability Manager signals events for nodes that do not necessarily have OVO Management Agents installed. Because the Availability Manager acts as a proxy server, the events that are signaled for these nodes appear in the message browser on the OVO Server under the name of the node that is running the Availability Manager. The event data contains the name of the node where the event condition occurs and is displayed in the Node field in the message browser display. The basic steps for installation and setup are as follows: 1. Install and configure the Availability Manager Data Collector on the OpenVMS systems that are to be monitored. See the HP Availability Manager Installation Instructions for instructions on how to do this. 1 2. On the OpenVMS or Windows system where the Availability Manager Data Analyzer is to be run: a. Install and configure the OVO Management Agents to forward events to the OpenView Server. b. Install the Availability Manager Data Analyzer. See the HP Availability Manager Installation Instructions for instructions on how to do this. 3. Install the Availability Manager OVO template/policy on the OVO Server. Depending on the kind of system the OpenView Server is installed on, Section 2.1 or 2.2 explain how to do this. 4. Deploy (in other words, install and update) the template/policy to the Management Agents on the node where the Availability Manager Data Analyzer is to be run. 5. Run the Availability Manager Data Analyzer, and configure it to forward selected events to OpenView. Section 7.7 of the Availability Manager User's Guide explains how to do this. After you perform these steps, the Availability Manager is ready to forward events to OpenView. If there are problems forwarding events to the Management Agents, the Availability Manager posts an OVOERR event along with the Availability Manager or OVO Management Agent error condition. 2 Availability Manager OpenView Template Installation Instructions Sections 2.1 and 2.2 contain instructions for updating the Management Server. The steps to perform these updates differ depending on whether your Management Server runs on a UNIX or a Windows system: Section 2.1 contains instructions for a UNIX system. Section 2.2 contains instructions for a Windows system. 2 2.1 Updating a UNIX Management Server (OVOU) Follow the steps in this section if you plan to view your OpenVMS Availability Manager messages from a UNIX Management Server. To distribute the updates on a UNIX Management Server, follow these steps: 1. Log on to your OVOU server. 2. Copy the OVOU_vmsam.TAR file to the UNIX Management Server into a temporary directory such as /tmp. 3. To make the required updates to the Management Server, perform the following lettered steps: ________________________ Note ________________________ Perform the lettered steps in the following section ONLY ONCE, even if you later add nodes or perform other update tasks. ______________________________________________________ a. To distribute the files on the Management Server, set the directory to the root directory, and untar the file using the following commands: # cd / # tar -xvf OVOU_vmsam.TAR b. Upload the templates so that you can distribute them later to the agent nodes: # opccfgupld -add VMSAMpkg 2.2 Updating a Windows Management Server (OVOW) Perform the following numbered steps if you plan to manage your OpenVMS system from a Windows Management Server. ________________________ Note ________________________ Perform the installation on the "C:" drive of the Windows Management Server. ______________________________________________________ 1. Extract the OVOW_vmsam.ZIP files into the HP OpenView folder: 3 C:\Program files\HP OpenView During the extraction process, do not create subfolders; the extraction into the HP OpenView folder places the files in the correct subfolders. 2. Go to the \HP OpenView\install\OpenVMS folder. Run the Upload_AM_Policy batch file to load the OpenView AM policies on the OVOW console. Load the following Policy on the OVOW console: \Policy management\Policy groups\OpenVMS_policies\AvailMan At this point, you have installed the policies for the OpenVMS Availability Manager. Finally, follow this post-installation step: 3. Go to the \Policy management\Policy groups\OpenVMS_ policies directory, and select the AvailMan template. Then drag and drop the file into \Nodes\your-managed- node-name. This last action associates the policy with the node. Conclusion By completing the steps in either Section 2.1 or 2.2, you have made the OpenView Management Server aware of the Availability Manager. The Availability Manager can now forward Availability Manager events to the OpenView Server. 4