Micromuse. Supporting Products. Probe for HP OpenView IT/Operations

Transcription

1 Micromuse

2 2001 Micromuse Inc., Micromuse Ltd. All rights reserved. No part of this work may be reproduced in any form or by any person without prior written permission of the copyright owner. This document is proprietary and confidential to Micromuse, and is subject to a confidentiality agreement, as well as applicable common and statutory law. Micromuse Disclaimer of Warranty and Statement of Limited Liability Micromuse provides this document as is, without warranty of any kind, either express or implied, including, but not limited to, the implied warranties of merchantability, fitness for a particular purpose or non-infringement. This document may contain technical inaccuracies or typographical errors. Micromuse may make improvements and changes to the programs described in this document or this document at any time without notice. Micromuse assumes no responsibility for the use of the programs or this document except as expressly set forth in the applicable Micromuse agreement(s) and subject to terms and conditions set forth therein. Micromuse does not warrant that the functions contained in the programs will meet your requirements, or that the operation of the programs will be uninterrupted or error-free. Micromuse shall not be liable for any indirect, consequential or incidental damages arising out of the use or the ability to use the programs or this document. Micromuse specifically disclaims any express or implied warranty of fitness for high risk activities. Micromuse programs and this document are not certified for fault tolerance, and are not designed, manufactured or intended for use or resale as on-line control equipment in hazardous environments requiring fail-safe performance, such as in the operation of nuclear facilities, aircraft navigation or communication systems, air traffic control, direct life support machines, or weapons systems ( High Risk Activities ) in which the failure of programs could lead directly to death, personal injury, or severe physical or environmental damage. Compliance with Applicable Laws; Export Control Laws Use of Micromuse programs and documents is governed by all applicable federal, state and local laws. All information therein is subject to U.S. export control laws and may also be subject to the laws of the country where you reside. All Micromuse programs and documents are commercial in nature. Use, duplication or disclosure by the United States Government is subject to the restrictions set forth in DFARS and FAR Trademarks and Acknowledgements Micromuse and Netcool are registered trademarks of Micromuse Ltd. Other Micromuse trademarks include but are not limited to: Netcool/OMNIbus, Netcool/OMNIbus for Voice Networks, Netcool/Reporter, Netcool/Internet Service Monitors, Netcool/NT Service Monitors, Netcool/WAP Service Monitors, Netcool/Fusion, Netcool/Impact, Netcool/Visionary, Netcool/Precision, Netcool/Firewall, Netcool/WebTop, Netcool ObjectServer, Netcool/Software Developers Kit, Micromuse Developers Alliance and Network Slice. Micromuse acknowledges the use of I/O Concepts Inc. X-Direct 3270 terminal emulators and hardware components and documentation in Netcool/Fusion. X-Direct I/O Concepts Inc. X-Direct and Win-Direct are trademarks of I/O Concepts Inc. Netcool/Fusion contains IBM Runtime Environment for AIX, Java Technology Edition Runtime Modules Copyright IBM Corporation All rights reserved. Micromuse acknowledges the use of MySQL in Netcool/Precision. Copyright 1995, 1996 TcX AB & Monty Program KB & Detron HB Stockholm SWEDEN, Helsingfors FINLAND and Uppsala SWEDEN. All rights reserved. Micromuse acknowledges the use of the UCD SNMP Library in Netcool/Precision. Copyright 1989, 1991, 1992 by Carnegie Mellon University. Derivative Work - Copyright 1996, 1998, 1999, 2000 The Regents of the University of California. All rights reserved. Micromuse acknowledges the use of Viador Inc. software and documentation for Netcool/Reporter. Viador is a trademark of Viador Inc. Netcool Visionary, Netcool/Precision and Netcool/Reporter include software developed by the Apache Group for use in the Apache HTTP server project ( Copyright The Apache Group. All rights reserved. Micromuse acknowledges the use of Merant drivers. Copyright MERANT Solutions Inc.,

3 The following product names are trademarks of Tivoli Systems or IBM Corporation: AIX, IBM, OS/2, RISC System/6000, Tivoli Management Environment, and TME10. IBM and NetView/6000 are either trademarks or registered trademarks of IBM Corporation. VTAM is a trademark of IBM Corporation. Omegamon is a trademark of Candle Corporation. Netspy is a trademark of Computer Associates International Inc. The Sun logo, Sun Microsystems, SunOS, Solaris, SunNet Manager, Java are trademarks of Sun Microsystems Inc. SPARC is a registered trademark of SPARC International Inc. Programs bearing the SPARC trademark are based on an architecture developed by Sun Microsystems Inc. SPARCstation is a trademark of SPARC International Inc., licensed exclusively to Sun Microsystems Inc. UNIX is a registered trademark of the X/Open Company Ltd. Sybase is a registered trademark of Sybase Inc. Action Request System and Remedy are registered trademarks of Remedy Corporation. Peregrine System and ServiceCenter are registered trademarks of Peregrine Systems Inc. HP and OpenView are trademarks of Hewlett-Packard Company. Microsoft, Windows, Windows NT are either registered trademarks or trademarks of Microsoft Corporation. FireWall-1 is a registered trademark of Check Point Software Technologies Ltd. Netscape and Netscape Navigator are registered trademarks of Netscape Communications Corporation in the United States and other countries. Netscape's logos and Netscape product and service names are also trademarks of Netscape Communications Corporation, which may be registered in other countries. Micromuse acknowledges the use of Xpm tool kit components. SentinelLM is a trademark of Rainbow Technologies Inc. GLOBEtrotter and FLEXlm are registered trademarks of Globetrotter Software Inc. Red Hat, the Red Hat Shadow Man logo, RPM, Maximum RPM, the RPM logo, Linux Library, PowerTools, Linux Undercover, RHmember, RHmember More, Rough Cuts, Rawhide and all Red Hat-based trademarks and logos are trademarks or registered trademarks of Red Hat Inc. in the United States and other countries. Linux is a registered trademark of Linus Torvalds. Nokia is a registered trademark of Nokia Corporation. WAP Forum and all trademarks, service marks and logos based on these designations (Trademarks) are marks of Wireless Application Protocol Forum Ltd. Micromuse acknowledges the use of InstallAnywhere software in Netcool/WAP Service Monitors. Copyright Zero G Software Inc. Orbix is a registered trademark of IONA Technologies PLC. Orbix 2000 is a trademark of IONA Technologies PLC. All other trademarks, registered trademarks and logos are the property of their respective owners. Micromuse Inc. 139 Townsend Street San Francisco USA CA

4 Document Control Page This document is supplied solely as an electronic copy. To obtain the most recent version, see the Micromuse support site. Before you read this document you should be familiar with the Netcool/OMNIbus Version Product Documentation. Document Details Document Name Release Name Netcool/OMNIbus Version Print Date Current Status Approved Modification History Document Version No. Comments 1.0 Updated for Netcool/OMNIbus Version Release Date

5 Table of Contents... 1 Summary... 2 Data Acquisition... 2 Elements... 4 Fatal Level Messages... 6 Error Level Messages... 6 Contact Information... 9 Page i

6 Page ii

7 The HP OpenView IT/Operations (ITO) is a software application that provides central operations and event management. ITO consists of a central management server, which interacts with intelligent software agents installed on the managed nodes. ITO receives events from log files, SNMP traps, MPE/iX consoles, ITO message interface and monitored objects such as disk space, swap space, and CPU utilization. The ITO message processing is as follows: 1. An event occurs on a managed object and the ITO Agent on that managed node creates a message. 2. The message is compared to filters. Messages matching suppress conditions are suppressed. Other messages are forwarded to the management server or logged locally. 3. Messages matching filters are converted to ITO message format, and forwarded to the management server. If a local action is configured, it will be started. 4. The management server can perform the following processing: Assign the message to another message group (regrouping). Start non-local automatic actions configured for the message on the specified node. Forward the message to external notification interfaces and trouble ticket service. Escalate the message to another management server. 5. The active message is stored in the database. 6. The message is displayed in a Message Browser window. 7. When the message is acknowledged, it is removed from the active browser and placed in the history database. Page 1

8 Summary Probe Target Probe Executable Name HP OpenView IT / Operations Manager nco_p_ito4 nco_p_ito5 Table 1: Summary Probe Supported on HP-UX 10 and HP-UX 11 Properties file $OMNIHOME/probes/arch/ito4.props $OMNIHOME/probes/arch/ito5.props Rules file $OMNIHOME/probes/arch/ito4.rules $OMNIHOME/probes/arch/ito5.rules Requirements OpenView IT/Operations MSI must be enabled in the ITO configuration. Connection Method API Probe Type API License Band C Data Acquisition The acquires event data as it is generated by IT/Operations management server. Once processed, the alert is forwarded to the ObjectServer. Before the can acquire events from the ITO management server, the agents must be configured to send MSI (Message Stream Interface) alerts to the server. To do this you must: configure MSI for each node configure MSI for a particular alarm assign an alarm template to a node update the node configuration Each of these tasks is described in the following sections To Configure MSI for Each Node 1. Select a node by clicking on its icon. 2. Display the pop-up menu for that node by clicking the icon and holding the mouse Page 2

9 3. Select Modify from the pop-up menu. 4. Select Advanced Options and enable output for the message stream interface. 5. From the Node Bank window, select Actions Server Configure. 6. Enable output for the message stream interface. 7. For each node in the Node Bank window: Highlight the agent icon. Select Actions Agents Set Defaults. Select Advanced Options, then enable output for the message stream interface. To Configure MSI for a Particular Alarm 1. Login to IPO as opc_adm. 2. Select Window Message Source Templates. 3. Double-click Defaults in the Template Groups frame. 4. Select a group, for example: HP-UX 10.x. This will display a list of options in the right hand frame. 5. Double-click Logfile SuXXX (10.x HP-UX). This will display a list of conditions. 6. Select one of the conditions and click Modify. 7. Select Advanced Options. 8. Click the Server MSI box. 9. Click the Copy Messages box. 10. Click OK, then close all open windows. To Assign an Alarm Template to a Node 1. Select Window Node Bank. The ITO Node Bank window is displayed. 2. Select Actions Agents Assign Templates. The Define Configuration window is displayed. 3. Click Add. 4. Select the nodes you want to assign the template to. Page 3

10 5. From the Templates frame, click Open Template Window. The Message Source Templates window is opened. 6. Select the template created in the first procedure. 7. In the Add Configuration window, click Get Template Selections. 8. Click OK. 9. In the Define Configuration window, click OK. The new template will be displayed in the list of assigned templates. To Update the Node Configuration 1. From the ITO Node Bank window select Actions Agents Install/Update SW & Config. 2. Click Templates in the Components frame. 3. Click Force Update in the Options frame. 4. Add the nodes to which you want to download the template to the Target Nodes frame. The templates should now be downloaded to the ITO agents, and the probe will start to receive events from the ITO management server. Elements DYNAMIC The only generates dynamic elements as shown in Table 2 on page 4. Element Name $Application $AutoActionAck $AutoActionAnnotate $AutoActionCall $AutoActionNode Element Description The application name used for the event. This element contains 1 if ITO automatically acknowledges the event, otherwise it contains 0. This element contains 1 if the ITO is required to create an annotation for the event that generated the action if the action type is OPC_AUTOMATIC_ACTION or OPC_OPERATOR_INIT_ACTION. The command to issue as an automatic response to the ITO event. The system on which the automatic action should run. Table 2: Dynamic Elements Page 4

11 Element Name $CreationTime $Group $InstructionParameter $InstructionTag $InstructionType $MsgId $MsgLogOnly $MsgSrc $MsgText $MsgType $Node $Notification $Object $OpActionAck $OpActionAnnotate $OpActionCall $OpActionNode $OrigMsgText $ReceiveTime $Severity $TroubleTicket $TroubleTicketAck $Unmatched The time the event was generated. The ITO message group. The parameters used to call the external instruction text interface. The name of the external instruction text interface. This element defines whether the internal ITO instruction text or an external interface is used to display instructions for the event. A unique identifier for the event. This element contains 1 if the event is automatically inserted into the history event table when it is received by ITO, otherwise it contains 0. The source of the event. The event text. The type of ITO message contained within the event. The node name of the server that generated the event. This element contains 1 if ITO forwards the event to the ITO notification interface, otherwise it contains 0. The object name used for the event. This element contains 1 if ITO automatically acknowledges the operatorinitiated event after it has finished successfully, otherwise it contains 0. This element contains 1 if ITO creates start and end annotations for the operator-initiated action, otherwise it contains 0. The command to issue as an operator-initiated response to the ITO event. This element defines the system on which an operator-initiated action should run. The original message text. The time the event was received by ITO. The severity of the event Element Description This element contains 1 if ITO forwards the event to the ITO trouble ticket interface, otherwise it contains 0. This element contains 1 if ITO automatically acknowledges the event when it is sent to the trouble ticket interface successfully, otherwise it contains 0. This element contains 0 if the event was forwarded to ITO because it matched a condition, otherwise it contains 1. Table 2: Dynamic Elements Page 5

12 Fatal Level Messages This section describes the fatal level messages specific to this probe. For information on generic fatal level messages, see Appendix D of the Netcool/OMNIbus Administration Guide. FAILED TO INITIALISE An internal error. FAILED TO PROCESS ARGUMENTS Failed to process the command line arguments. ITO PROBE CAN ONLY BE RUN BY ROOT The probe must be run as root user. SESSION CREATE FAILED - ABORTING An internal error. FAILED TO CONNECT - ABORTING Failed to connect to the ObjectServer. FAILED TO READ RULES - ABORTING FAILED TO INFORM PROCESS AGENT OF STATUS-ABORTING See your system administrator. Error Level Messages This section describes the error messages specific to this probe. For information on generic error messages, see Appendix D of the Netcool/OMNIbus Administration Guide. FAILED TO OPEN ITO MSI STREAM The probe was unable to connect to IT/Operations. Check IT/Operations is available. Page 6

13 OPCID_REGISTER () FAILED OPCDATA_CREATE () FAILED OPCIF_READ () FAILED OPCIF_UNREGISTER () FAILED OPCIF_CLOSE () FAILED Any of the above indicate a problem with IT/Operations communication. Check IT/Operations is available, and check the MSI configuration. FAILED TO INSTALL SIGQUIT HANDLER FAILED TO INSTALL SIGINT HANDLER FAILED TO INSTALL SIGTER HANDLER System errors. Failed to install signal handlers. FAILED TO OPEN ITO MSI STREAM: <ERROR> Failure to open a connection to the MSI interface. <Error> will contain the OpC error string. OPCIF_REGISTER() FAILED: <ERROR> Failure to register for messages from ITO Message Stream Interface. <Error> will contain the OpC error string. OPCDATA_CREATE() FAILED: <ERROR> Failed to allocate and initialize data structures within the OpC API. <Error> will contain the OpC error string. OPCIF_READ() FAILED: <ERROR> Failure to read a message from ITO Message Stream Interface. <Error> will contain the OpC error string. OPCIF_UNREGISTER() FAILED: <ERROR> Failure to unregister for messages from ITO Message Stream Interface. Page 7

14 OPCIF_CLOSE() FAILED: <ERROR> Failure to close the Message Stream Interface. UNABLE TO GET EVENTS Event collection has failed. CREATEANDSET FAILED: $<ELEMENT NAME> An internal error. SESSIONPROCESS FAILED: <INTERNAL ERROR CODE> An internal error. SESSIONSENDALERT FAILED Failure to send alert to the ObjectServer. Page 8

15 Contact Information Technical Support Contact Details USA Europe Telephone Number: Fax Number: World Wide Web: Address: Telephone Number: Fax Number: World Wide Web: Address: Netcool ( ) Customer Support Services, 139 Townsend Street, San Francisco, California (0) (0) Customer Support Services, Disraeli House, 90 Putney Bridge Road, London, SW18 1DA Company Contact Details USA Micromuse Inc (HQ), 139 Townsend Street, San Francisco, CA 94107, USA Phone: Fax: EUROPE Micromuse Ltd., Disraeli House, 90 Putney Bridge Road, London SW18 1DA, United Kingdom Phone: Fax: