HP Operations Agent for NonStop Event Management Guide for UNIX Part number: 540075-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-1 Infrastructure Component(s) ................................................................................................. 43 5-3-2 Application Component(s) ................................................................................................... 44 5-4 Infrastructure Service Views and Service IDs .................................................................................... 44 5-4-1 Infrastructure Hardware Server Map and Service IDs .................................................
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 1-1 Integration between HPOM and HP NonStop System ......................................................................... 9 1-2 Event Management ...........................................................................
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.
Organization Sr. No Chapter Name Description Chapter 1. Integrating OVNM with HPOM Gives a brief overview of OVNM and its integration with OVNM. Chapter 2. HP NonStop Event Management System (EMS) Gives a brief introduction to the EMS system along with its components and architecture. Chapter 3. HPOM Message Templates Provides information about the default OVNM message templates and how to modify, create and deploy templates in the HPOM environment.
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 HPOM 1-1 About OVNM OVNM is a natural extension of HP Operations Manager (HPOM) 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 HPOM 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 2-3 Flow of Event Messages HP NonStop Event Management System 20
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 HP Operations Manager Message Templates 3-1 Introduction 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 HP Operations Manager Administrator’s User Interface.
2. The Message Source Templates window is displayed with a list of the default message templates. Doubleclick on the template that is to be modified. Figure 3-2 Message Source Templates Window 3. The Message and Suppress Conditions window is displayed. Select the condition to be modified and click on the Modify button. This can be used to add a new condition/rule for the template also. In the example below, Disk-Alerts condition is selected for modification.
4. The Condition window is displayed. Use this window to define message- and suppress-conditions to match incoming messages from the HP NonStop Server. You can set up as many message- and suppressconditions for a template as you need. Figure 3-4 Condition Window Use the various fields in the Condition area to define the condition you wish incoming messages to match. HP Operations Manager displays the default settings you supplied for this template in these fields.
Whether action commands for HP NonStop Servers are executed as Automatic or Operator- initiated, the commands are required to use the “nscmd” utility. The “nscmd” utility is supplied with OVNM and executes on the HP Operations Manager Management Server. It then send the command defined in the –cmd option to the NonStop Server identified with the –node option. Since the “nscmd” command executes on the Management Server the Node field in the Command dialog box MUST be set to <$OPC_MGMTSV>.
Figure 4-6 is an example message corresponding to the “DISK Alerts” message template, which was shown in Figure 4-4. Also shown, is the original message from the NonStop, which met the condition, specified in the template. Figure 3-6 Message Details As discussed in this section, you can modify the existing templates as per your requirements. After modifying a given template, click on the OK button in the Message Source Templates window to save and close the window.
3. The Add OVO Interface Messages window is displayed. Specify the information for the new message template and click on the OK button. Figure 3-8 Add OVO Interface Messages 4. The Message Source Templates dialog box is displayed again with the information about the newly added template. Figure 3-9 Message Source Templates Window Once the template is created, you can start adding/modifying the rules, as discussed in the Modifying Default Message Template topic.
3-4 Deploying a Message Template 1. The first step in deploying a message template is to select the HP Operations Manager Management Server in the OVO Node Bank window. Figure 3-10 OVO Node Bank Window 2. Select the Agents option in the Actions menu. In the displayed Agents menu, click on the Assign Templates option.
3. In the displayed Define Configuration dialog box, add the HP NonStop Server group or your newly created/modified group/template. If the group is already added, you need to remove and add it again. Click on the OK button to continue. For information on adding Template group, refer to Assign HP NonStop Server Template Group section in OVNM User and Installation Guide. Figure 3-12 Define Configuration 4. Next, select the Install / Update SW & Config menu option in the OVO Node Bank Actions/Agents menu.
4 HP Operations Manager Applications 4-1 Introduction Applications are scripts and commands to help you perform necessary tasks in your environment, such as launching corrective actions or diagnostic tools. Available applications are contained in Applications groups in the Application Bank. To view these tools, select a tools folder/group to display the tools it contains in the submap.
2. The OVO Application Bank window is displayed. Figure 4-2 OVO Application Bank Window Double-click on the NonStop Tools icon. 3. The NonStop Tools window is displayed with the various categories of OVNM applications. NOTE: The NonStop operator tools are provided as guidelines for operator tasks. These non-destructive command templates can be used to design and develop user-defined tools on your HP Operations Management environment.
4-2-1 NonStop Operator Tools Figure 4-4 OVNM NonStop Operator Tools 4-2-2 OVNM Tools Figure 4-5 OVNM Start/Stop Tools NOTE: To run the tools, select the node and drag and drop it on the tool to be executed in the Application Group submap.
4-3 Configuring/Modifying NonStop Operator Tools Follow the steps given below to configure actions for NonStop Operator Tools: 1. Select the Application Group: NonStop Tools from the OVO Application Bank window and then select Application Group: NonStop Operator Tools. 2. In the Application Group: NonStop Operator Tools window, right-click on the tool to be configured and select the Modify option.
3. The Modify OVO Application: NonStop Server window for the selected tool is displayed. Figure 4-7 Modify OVO Application: NonStop Server Specify the parameters in the dialog box. Specify the command for the call in the Application Call field. -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 /.
4-4 Creating a New Application Follow the instructions below to create a new Application tool. 1. Open the Application Group: NonStop Operator Tools window and select the Application option in the Actions menu. In the displayed Application menu, click on the Add OVO Application option.
2. The Add OVO Application window is displayed. Figure 4-9 Add OVO Application Window Specify the parameters like new Application Name, Label, and Description in the various fields as per the requirements. In the example above, a NonStop application has been created that checks how many FTP server processes exist on the HP NonStop server at the particular instance of this application’s execution. Click on the OK button to save the information and close the window. 3.
4-5 Applying Applications The HP Operations Manager Administrator configures the tools available for an operator. To view the tools, right click on a Node name and select the Start menu option. The list displays the tools/tool groups available. You can execute the tools using either of the following methods: • ITO (JAVA User Interface): Select a node or service, and then apply a tool. • OPC User Interface: Select a node and then drop it over the tool that needs to be executed.
5 Configuring HP Operations Manager Services 5-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.
Configuring HP Operations Manager Services Figure 5-2 Service View Figure 6-2 displays an example of a service view in HP Operations Manager. 5-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 HP Operations managed components. OVNM provides two sets of Service Map Views for NonStop Servers.
5-3-2 Application Component(s) This view represents the Application environment for a NonStop Server, for example, \EXTDEV, and is intended to be used in conjunction with NonStop Server Processes and Middleware components. The following Sections will provide more detail relating to the NonStop Service Map components and is intended to provide NonStop Administrators with Service ID definitions for each OVNM supplied Service Map component.
Figure 5-5 HP Operations Manager Hardware Server Map and Service IDs 5-4-2 Infrastructure Resource Server Map and Service IDs Figure 5-6 HP Operations Manager Infrastructure Resource Server Map and Service IDs 5-4-3 Infrastructure Network Server Map and Service IDs Figure 5-7 HP Operations Manager Infrastructure Network Server Map and Service IDs Configuring HP Operations Manager Services 45 Configuring HP Operations Manager Services 5-4-1 Infrastructure Hardware Server Map and Service IDs
5-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 5-8 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 Filtering Events Using EMS Filters This section provides information about how to control the message flow through EMS filters. Every 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.
Appendix B 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 • • For OVNM generated messages, this variable is set to the threshold object name of the OCC policy e.g. CPU number, disk name, process name etc.
Table A2 Optional HP Operations Manager Message Variable in the OVNM Message 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. CUSTOMER This variable is set to the CUSTOMER value of OCC policy, otherwise none.
Index A action events, 18 add OVO application, 39 add OVO interface messages, 31 alternate collectors, 21 application bank, 34 application component, 44 application service IDs, 46 application service map, 46 applying applications, 41 assign templates, 32 asynchronous pattern, 14 audience, 6 automatic or manual actions, 10 B blocking, 22 burst detection and suppression (BDS), 15 burst filters, 23 C cmd option, 29 command-response interface, 13 communication pattern, 14 compatibility distributor, 19, 22 co
reliability, 16 resources component, 44 retrieving event information, 12 S security, 44 service hierarchy, 42 service models, 42 SPI ADD command, 23 SPI ALTER command, 22 subsystem environment, 12 subsystem generality, 15 subsystem programmatic interface (SPI), 13 SUPPRESS command parameter, 25 synchronous pattern, 14 T text formatting, 15 tokens, 15 U untokenized messages, 16 V Z ZEMSC, 25 ZEMSCOB, 25 ZEMSDDL, 25 ZEMSTACL, 25 ZEMSTAL, 25 ZEMS-TKN-ACTION-ID token, 18 ZEMS-TKN-ACTION-NEEDED token, 18 Z
Document Feedback Form We would appreciate your comments on the OVNM Event Management Guide for UNIX. 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.) Do you have any other suggestions for improvement? Document Feedback Form 10.
