HP Operations Agent for NonStop Event Management Guide for Windows Part number: 540073-005 Fifth Edition: 12/2008
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 ..................................................................................................................................... 6 Audience ................................................................................................................................................ 6 Goals of Documentation ........................................................................................................................... 6 Organization .......................
5-3 5-4 Configuring Actions for NonStop Operator Tools ............................................................................. 43 Applying Tools ............................................................................................................................ 44 6 Browsing Messages 6-1 6-2 6-3 6-4 6-5 6-6 Information Displayed in the Message Browser Window................................................................... 45 Message Attribute Keys .........................................
Figures Figure 1-1 Integration between HP Operations Manager and HP NonStop System ................................................ 9 Figure 1-2 Event Management ...................................................................................................................... 10 Figure 1-3 HP Operations Manager – Message Properties ............................................................................... 11 Figure 2-1 EMS in the System Environment ..................................................
Preface HP Operations Agent for NonStop (OVNM) is an out-of-the-box solution that provides seamless integration of HP Operations Software (formerly 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. The OVNM Event Management Guide gives you information about the event integration between OVNM and supported Enterprise Managers, for example, HP Operations Manager (HPOM).
Organization Sr. No Chapter Name Description Chapter 1. Integrating OVNM with HP Operations Manager Gives a brief overview of OVNM and its integration with OVNM. Also introduces the concepts of Event Messages. Chapter 2. HP NonStop Event Management System (EMS) Gives a brief introduction to the EMS system along with its components and architecture. Chapter 3. Filtering Events Provides information about how to control the message flow through the default and customized filters. Chapter 4.
OVNM Manuals This section provides an overview of the OVNM manuals and their contents. Manual Description Media OVNM Concepts Guide Explains OVNM features, functions, benefits, architecture, and data flow. Describes OVNM agent and server components. PDF OVNM User and Installation Guide Explains how to install, configure and start & stop OVNM components. Also includes OVNM utilities and troubleshooting.
1 Integrating OVNM and HP Operations Manager 1-1 About OVNM OVNM is a natural extension of HP Operations Manager and is fully integrated with the environment. This tight integration gives organizations a cost-efficient, easily configurable, and time-saving way to rapidly and successfully incorporate HP NonStop business applications and management solutions into their service delivery infrastructure.
Figure 2-1 gives an overview of how OVNM integrates HP Operations Manager and a HP NonStop System. It shows that: 1. OVNM is an integrated set of modules with both Event Management and Object Management modules installed on the HP NonStop Server. 2. OVNM accepts messages from HP NonStop Server and forwards them to HP Operations Manager. 3. Action requests that are based on the NonStop messages are passed on to the HP NonStop server through OVNM. 4.
1-5 Event Integration and OVNM Agents OVNM Agents collect HP NonStop event message and package the EMS messages into a defined data structure. These messages are then mapped into the HP Operations Manager environment. These HP NonStop event message are collected and monitored according to predefined rules and filters. The actions performed on the mapped events are then forwarded to the OVNM server components through OVNM agents.
2 HP NonStop Event Management System 2-1 Introduction to EMS The Event Management Service (EMS) is a collection of processes, tools, and interfaces that support the reporting and retrieval of event information.
Figure 3-1 is a simplified diagram of the EMS layer, its components, and their relationships to the subsystem and operations environments. Figure 2-1 EMS in the System Environment 2-1-2 EMS Communications in the DSM Environment EMS uses two types of interfaces to communicate with other components of DSM (for example, ViewPoint) and with processes that use DSM to manage a system or network: EMS Interface This interface manages event reporting in a system or network.
Because the interfaces differ in purpose and use, they also differ in certain key characteristics: • Initiator In the command-response interface, the management application initiates communication with the subsystem. The operator or management application also controls the flow of information, issuing the commands necessary to accomplish the desired task. In the EMS environment, the subsystem initiates communication, at least for reporting an event to EMS.
Basic Capabilities EMS supports many aspects of managing event messages, from generation of a message in the subsystem environment to generation of text for display in the operations environment. This list describes the basic EMS capabilities, in the approximate order in which they would apply to a single event message: • Message building EMS includes several library procedures that HP NonStop subsystems, and subsystems you write use to build event messages.
• Versatility You can use EMS for many types of applications because of the variety of options it provides: • • EMS supports applications that monitor events as they occur, as well as applications that analyze logs of event messages reported in the past. • Distributor processes are provided for communicating event messages to management applications, forwarding event messages from one node to another, and displaying event-message text on printers and other display devices.
2-2 EMS Components and Architecture This section describes the processes, files, and interfaces that together provide the event management capabilities described in Introduction to EMS section. Before working with the process architecture, you must understand more about event messages because they are what EMS exists to manage. 2-2-1 Event Messages Event messages are based on tokens that convey information about events, which are significant occurrences in the subsystem environment.
The exact contents of all messages generated by a subsystem are described in the management programming manual for that subsystem (which is often a separate book with that title). For example, the event messages for Pathway are described in the TS/MP and PATHWAY Management Programming Messages Manual. This manual describes event messages for EMS itself. Special Kind of Messages There are two special categories of events: • Critical events are indicated by assigning the value TRUE to the emphasis token.
Flow of Event Messages Two types of EMS processes manage the flow of event messages from the subsystem environment to the operations environment: Event Message Collectors accept event messages from subsystems and log them. Pre-log filtration (PLF) lets a primary or alternate collector use one or more filters to detect and discard all event bursts with specified attributes or specific unwanted events that would otherwise be sent to the collector’s log file.
Figure 3-3 shows the flow of event messages in a system: 1. Messages originate in the subsystems. 2. The subsystems send the messages to the primary and alternate collector processes. 3. Collectors write passed event messages to the log files. 4. Distributors retrieve selected messages from the log files and send them to processes, printers, terminals, and other destinations in the operations environment.
2-2-3 EMS Message Collectors EMS supports two types of event message collectors. Primary Collector ($0) Each system (or node) has only one primary event message collector, named $0. The primary collector, initiated at system generation, provides a central collection point for all events from all subsystems in a system. $0 uses the $ZOPR process to perform waited operations. $ZOPR is a continuous process that, like $0, exists on every node and is initiated at system generation.
Log File Management The collector writes messages to the log files. The collector writes messages one at a time or writes a number of messages to a buffer then writes that entire message group to the log file. The process of writing a group of messages to a buffer is known as blocking. Blocking significantly increases the speed at which messages are written to the log file.
Consumer, Forwarding, and Printing Distributors In general, you can initiate and terminate consumer, forwarding, and printing distributors as needed. When you initiate a distributor, you can (in some cases, must) provide: • The source of the event messages you want the distributor to process: the current primary or alternate collector log files (on a local or remote node) or a specific log file.
2-2-7 Text Formatting Tools When passed an event message, the EMSTEXT procedure returns text in DSM display format. EMSTEXT performs these steps when it generates text for an event message: 1. If the event message points to a format template or contains a TEXT token: a. EMSTEXT checks first for a template. For many HP NonStop and user-written subsystems, EMSTEXT generates display text from an event message by applying a format template found in a template file installed at system generation.
2-2-8 Definition Files Like all subsystems that support SPI interfaces, EMS has its own DDL (Data Definition Language) file that defines the tokens, values, and data types used in event messages and in command and response messages relating to EMS. The DDL file is called ZEMSDDL, and its language-specific derivative files are called ZEMSTAL, ZEMSTACL, ZEMSCOB, and ZEMSC. These files are of particular importance to EMS because they include definitions for some widely used tokens.
3 Filtering Events 3-1 EMS Filters HP NonStop server can have more then one distributor. Every distributor can use one or more collector and every EMS collector and distributor (except the compatibility distributor) can use one or more filters to determine whether or not to forward specific event messages to their destinations. These filters can select messages in a way that is as detailed and complex as you care to make it.
3-2-1 Create a New Filter 1. Select a HP NonStop node in the console tree. Figure 3-1 HPOM Message Browser with a HP NonStop Node Selected 2. Click on the Message Filter icon on the console toolbar to open the Message Filter dialog box. Filtering Events Figure 3-2 HPOM Message Filter Dialog Box You can also access the Message Filter dialog box using the Apply Message Filter option in the Action/All Tasks menu.
3. Click on the New button to open the Filter Properties dialog box and specify filter properties in the following areas using the respective tabs: a. General b. Time c. Message Source d. Message Properties e. Message CMA Properties Figure 3-3 HP Operations Manager: Filter Properties Dialog Box 4. Click on the General tab of the Filter Properties dialog box to specify general information about a filter. All information is optional. a. Enter a name for the filter in the Name box.
5. Click on the Time tab of the Filter Properties dialog box to filter messages created on a particular date, at a particular time, or during a specified time period. Figure 3-4 HP Operations Manager: Filter Properties Dialog Box Time Tab Page a. Select the All Messages radio button to display messages regardless of the time they were created. b. If you prefer to filter messages created at a specific time, on a specific date, or during a specific interval of time, select Message(s) Received.
6. Click the Message Source tab of the Filter Properties dialog box to filter for messages received from specified message sources such as services and nodes. Only messages from the services and nodes you select will display in the message browser. Figure 3-5 HP Operations Manager: Filter Properties Dialog Box Message Source Tab Page Select one or more services or nodes from the Select Services, Nodes, or NodeGroups tree to display only messages from those nodes or services in the message browser.
7. Click the Message Properties tab of the Filter Properties dialog box to filter on application, object, and message group properties. Only messages with those properties will display in the message browser. Figure 3-6 HP Operations Manager: Filter Properties Dialog Box Message Properties Tab Page a. From the Browser Property dropdown list, select the attribute for which you want to filter. You can select one or more of the available choices.
3-2-2 Edit a Filter 1. Select an item, service, node, or node group from the console tree. 2. Select the Message Filter icon from the console toolbar. This displays the Apply Message Filter dialog box. Figure 3-7 HP Operations Manager: Message Filter Dialog Box 3. From the Message Filters list, select the name of the filter that you want to edit. 4. Click on the Edit button to open the Filter Properties dialog box. 5.
3-2-3 Remove a Filter You Have Applied 1. From within the Message Filter dialog box, select the name of the filter you want to inactivate. 2. Click on the Deactivate button. Figure 3-8 HP Operations Manager: Apply Message Filter Dialog Box Deactivate Button Filtering Events The filter will be unapplied and the filter criteria will no longer be applied to incoming messages.
4 HP Operations Manager Policies 4-1 Introduction 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 policies that can be used as-is to manage your HP NonStop environment. The policy can be accessed using the HP Operations Manager interface.
4-2 Modifying the Default Policy 1. Right-click on the policy and select the All Tasks/Edit option. Figure 4-2 HP Operations Manager: All Tasks/Edit Option 2. Clicking on the Edit option displays the policy editor. 3. Make the required modifications and click on the Save button. After saving the changes, click on the Save and Close button to close the policy editor.
4-3 Creating a New Policy 1. In the console tree, under Policies grouped by type, right-click the type of policy that you want to create. 2. Select the New/Policy option in the displayed right-click menu. Figure 4-4 HP Operations Manager: New/Policy Option 3. The Untitled Policy Editor is displayed, which can be used to set up the new policy Figure 4-5 HP Operations Manager: Untitled Policy Editor 4. Select the File/Save option to save the policy.
4-4 Deploying a Policy 1. Right-click on the policy or policy group, which is to be deployed and select the Deploy On option in the All Tasks menu. Figure 4-6 HP Operations Manager: All Tasks/Deploy On Option 2. The Deploy policies on dialog box is displayed. Select the nodes or node groups to which you want to deploy. Select the Deployment Options using the corresponding check box. Also select the policy status using the Policy status after deployment radio button. 3.
4-5 Configuring Actions for an HP Operations Manager Policy HP Operations Manager Policy can be configured for operator-initiated commands as well as automatic actions that would be triggered for a rule. Follow the steps given below to configure messages and commands for various rules: 1. Double-click on the Policy to be configured for action from the HP Operations Management Console. This displays the policy editor. Figure 4-8 HP Operations Manager: Policy Editor 2.
3. Click on the Actions tab to access the Actions tab page. You can configure event messages and actions for the selected policy rule using this tab page. Figure 4-10 HP Operations Manager: Rule Dialog Box Actions Tab Page 4. Actions commands can be configured in one of two ways using the Automatic command or Operatorinitiated command buttons in the Actions tab page. So the user can configure to either initiate commands automatically when an event is received, or by an Operator as per the requirement.
The following diagram explains the nscmd message flow. Figure 4-12 NSCMD Message Flow Nscmd Basic Parameters -node Remote HP NonStop Node Name (without “\”) -cmd Command String within “ “ (double quotation marks). Command can be either a Guardian or OSS command or Utility. Example: nscmd –node TEST –cmd “DSAP $SUBJECT” nscmd – node TEST –cmd “osh ls -l” Please note that neither –c nor –p options can be used with “osh”.
5-1 Introduction Tools are applications, scripts, and commands to help you perform necessary tasks in your environment, such as launching corrective actions or diagnostic tools. Available tools are contained in tool groups in the Tools folder in the HP Operations Manager console tree. To view tools, select a tools folder to display the tools it contains in the details pane.
5-2-1 NonStop Operator Tools Figure 5-2 HP Operations Manager: OVNM NonStop Operator Tools NOTE: To run the NonStop Operator tools, select the tool name in the HP Operations Manager Message Browser and enter the node name on which the command is to be executed.
Follow the steps given below to configure actions for NonStop Operator Tools: 1. Double-click on the Tool for which the action needs to be configured. This displays the Parameters dialog box. Figure 5-4 HP Operations Manager: Parameters Dialog Box 2. Specify the parameters in the Parameters box. -cmd “” Substitute with the name of the HP NonStop node (without \) to receive command. is the action that would be taken. For example, PEEK /CPU /.
3. Clicking on the Next button displays the Login dialog box. Figure 5-5 HP Operations Manager: Login Dialog Box 4. In the Login dialog box, specify the User Name and Password for the tool on the HP Operations Management Server. 5. Click on the Launch button to launch the tool. A dialog box is displayed, showing the response for the launched tool.
6 Browsing Messages 6-1 Information Displayed in the Message Browser Window The browser headline is a banner across the top of the message browser that labels the columns of information the browser displays. Use the headline to quickly identify these message details. Severity: Color-coded icons give at-a-glance message status. The console displays six levels of message severity. SUIAON: The status column displays attributes for message states.
Table 6-1 Message Attribute Keys Value Flag O Operator-Initiated Command Indicates that an operator-initiated command has been configured for the message and gives the status of the command. The attribute value shows whether a command is: • X: Available • S: Successful • F: Failed • R: Running • N: Not started • D: Discarded • C: Console command N Annotations Indicates if annotations exist for this message. You review the annotations to find procedures that resolved similar problems in the past.
• Acknowledge Send a message for a resolved problem to the acknowledged message browser and remove it from the active message browser view. • Change Severity Change the severity of a selected message. • Map Display a map of a selected service or node. Show the root cause of a problem, services or nodes impacted by the problem, or the relationship of the selected service or node to other services or nodes. • Launch Tool Apply a tool to a selected service or node.
7 Configuring HP Operations Manager Services 7-1 What are Service Models? A service model is a representation of the relationship between components of a service. In HP Operations Manager, service model is a convention for defining the components of a business function and the components that support the business function. The service model defines these objects, their relationships, and the rules that govern their status.
7-3 HP Operations Manager Service Map View of HP NonStop A key feature of HP Operations Manager is the Service Map View. Service Maps enables the visualization of Operations managed components. OVNM provides two sets of Service Map Views for NonStop Servers. These views are installed under the HP Operations Manager’s System Infrastructure and Application folders.
7-4 Infrastructure Service Views and Service IDs There are four Generic Service Map components within the NonStop Server Infrastructure View. The following diagram shows the top level Service Map components. Figure 7-3 HP Operations Manager Infrastructure Service Views • Hardware This Server Map component is intended to indicate some Hardware Event. Currently there are no OVNM Default policies that report to the Hardware Component(s).
7-4-1 Infrastructure Hardware Server Map and Service IDs Figure 7-4 HP Operations Manager Hardware Server Map and Service IDs 7-4-2 Infrastructure Resource Server Map and Service Ids 7-4-3 Infrastructure Network Server Map and Service Ids Figure 7-6 HP Operations Manager Infrastructure Network Server Map and Service IDs Configuring HP Operations Manager Services 51 Configuring HP Operations Manager Services Figure 7-5 HP Operations Manager Infrastructure Resource Server Map and Service IDs
7-5 Application Service Map and Service IDs Within the NonStop Server Application View there are currently six Service Map components installed. Below each Service Map component is the Service ID assigned. Figure 7-7 HP Operations Manager Application Service Map and Service IDs • Process This is a generic component intended to be used to indicate that a NonStop Sever application Process has generated an EMS event or the OVNM monitored Process Object has generated a threshold violation.
Appendix A OVNM Message Mapping in HP Operations Manager Figure A-1 OVNM Message Mapping in HP Operations Manager Table A1 Standard HP Operations Manager Message Variable in the OVNM Message HPOM Message Variable Mapping with OVNM APPLICATION This variable is set to OVNM. OBJECT • NODE This variable is set to the value of the NODE name entry in the elink.cfg file. SERVICE_ID This variable is set to the Service ID that was defined during the object policy in the OCC, otherwise none.
Table A2 Optional HP Operations Manager Message Variable in the OVNM Message HPOM Message Variable Mapping with OVNM NODENAME This variable is set to value of NODE name entry in the elink.cfg file. MANAGER This variable is set to the value of MANGER token in the EMS event message. SUBJECT This variable is set to the value of SUBJECT token in the EMS event message. SSID This variable is set to the SSID of the EMS event message.
Index acknowledge, 47 action events, 18 alternate collectors, 21 annotations, 47 application component, 49 application service IDs, 52 application service map, 52 applying tools, 44 asynchronous pattern, 14 audience, 6 automatic command, 39 automatic or manual actions, 10 B blocking, 22 browser property, 31 browsing messages, 45 burst detection and suppression (BDS), 15 burst filters, 23 C command-response interface, 13 communication pattern, 14 compatibility distributor, 20, 22 compiled filters, 23 compo
pre-log filtration (PLF), 15 primary collector, 12, 16, 21 printing distributor, 20, 22 properties, 47 reliability, 16 removing a filter, 33 resources component, 50 retrieving event information, 12 show report, 47 SPI ADD command, 23 SPI ALTER command, 22 start/stop tools, 42 subsystem environment, 12 subsystem generality, 15 subsystem programmatic interface (SPI), 13 SUIAON, 45 SUPPRESS command parameter, 25 synchronous pattern, 14 S T security, 50 service hierarchy, 48 service models, 48 severity, 45
We would appreciate your comments on the OVNM Event Management Guide for Windows. 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. Guide 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.) 10.
