HP

OpenView Operations (HP OV) is a monitoring software solution designed to help system administrators detect, solve problems occurring in networks, systems, and applications in any enterprise. OV is a flexible solution that can be configured to meet the requirements of any information technology (IT) organization and its users. System administrators can expand the applications of OV by integrating management applications from OV partners or other vendors.

Maximize Network Maximize the availability of network components.  Reduce Downtime Reduce the time lost by end-users as a result of system downtime.  Decrease Workload Reduce unnecessary user actions by automatically solving problems.  Prevent Problems Reduce the number of problems through preventive actions.  Decrease Delays Decrease the time needed to solve problems.  Reduce Costs Reduce the cost of managing the client-server environment.


1)

OpenView Operations (OVO)It deals with the monitoring of system and servers present in an organization which includes the services, memory, disk usage and other things in a system.

2)

Network Node Manager(NNM)It deals with the monitoring of Switches and Routers in an organization i.e. their interfaces.

3)

OpenView Internet Services(OVIS)-

It provides a single integrated view of your Internet and related services by configuring probes which measure availability, response time, and other performance metrics.

contd

4)

OpenView Performance Insight(OVPI)OVPI is a network management system that performs the following functions:

Collect Data
This function identifies the nodes (network devices or systems) in your network, and then obtains data from those nodes by polling them directly.

Process Data
This function converts raw data into rate data i.e. the difference b/w two values over time.

Report Data
This function produces reports from the summarized data.

contd

5) Reporter
HP OpenView Reporter creates Web-based reports from data of targeted systems it "discovers.

6) Service Information Portal (SIP)

This tool is designed for the end users which gives a Web-based report of all the tools of HP OpenView.

OVO concept is based on communication between a management server and managed nodes. Management server processes running on the management server communicate with OVO agent processes running on managed nodes.  The OVO agent processes collect and process events on the managed nodes, then forward information in the form of OVO messages to the management server.  The agent on the management server also serves as the managed node.  A database serves as the central data repository for all messages and configuration data. The database processes run on the management server.
The

The management server performs the central processing functions of OVO.  The entire software package, including the complete current configuration, is stored on the management server.  The management server does the following: Collects Data Collects data from managed nodes. Manages Messages Manages and groups messages.


contd

Manages Actions Calls the selected agent to: Start actions Start local automatic actions on the managed node. Initiate sessions Initiate sessions on managed nodes (for example, open a virtual console). Manages History Controls the history database for messages and performed actions. Forwards Messages Forwards messages to other management servers or to systems where OVO is running. Installs Software Installs OVO agent software on managed nodes.

Managed nodes are computers that are controlled and monitored by OVO. OVO manages these nodes by installing and running agent processes on them. 1) Intercepting Messages After installed and running, the OVO agent software reads logfiles , console messages (MPE/iX), and SNMP traps. If configured properly ,the OVO message interceptor can intercept messages from any application running locally on the managed node. 2) Monitoring Performance Performance values are monitored at configurable intervals, and messages can be generated when performance varies from limits. OVO can also monitor its own processes.


3) Comparing Messages The OVO agent compares all messages with conditions in preconfigured templates, then forwards unexpected or important messages to the management server while ignoring unimportant messages. If so configured, the agent even suppresses duplicate or similar events. 4) Logging Messages All messages can be logged locally on the managed node or written directly into the history database on the management server. 5) Buffering Messages If the management server is not reachable, messages are retained in a storage buffer until the management server can receive them again. 6) Correcting Problems Corrective actions can be started locally on the managed node in response to a message, and can be stopped and restarted, if necessary

7) Configuring Nodes Your OVO environment can be composed of different types of managed Nodes You can also add a range of IP addresses, so all nodes become known when they become part of a specific network or are added manually.

OVO helps you solve problems in your computing environment proactively. These problems can occur anywhere within a heterogeneous distributed environment consisting of network elements, systems, and applications. Registering Problems OVO notifies you when a problem is about to occur, and then provides you with the resources you need to avoid the problem. Likewise, OVO notifies you when a problem has just occurred, and provides you with the resources you need to solve the problem. Solving Problems On the management server, the message is displayed in a browser. The message tells you how severe the problem is, where (that is, on which managed node) the problem occurred, and what triggered the message.

the arrival of the message might trigger an automatic action executed immediately on the managed node. Or the message might trigger another message instructing for a corrective action manually. Documenting Solutions After the action has been completed successfully, the user can annotate the message with a comment, and then move the annotated message into the history database by acknowledging it. Generating Reports you can also generate reports from the database

Notify OVO agents monitor log files and system activity. If an OVO problem occurs, an OVO agent notifies you in one of the following ways: Sends a message to the management server. Changes the colors of node icons, based on the severity of the Problem and displays it in the Message Browser Displays a message and its attributes (for example, time sent, status of actions, and so on). Forwards the message to external notification or trouble ticket services, if they are configured.


Investigate Understand the problem and its cause. In large environments, it is crucial to be able to pinpoint problems quickly. OVO helps you pinpoint trouble in your environment by providing a fast link between the OVO system and the network management view. Solve Initiate a corrective action to solve the problem. OVO provides the following solutions: Automatic Actions As soon as an error message is generated, OVO starts corrective actions automatically. Operator-initiated Actions The received error messages, can start corrective actions manually.


 User Instructions The error messages, can also contain specific problem solving instructions to users depending on the customization. History Logs The history logs (including message annotations) of related problems can be tracked to see the techniques used to solve similar problems or previous occurrences of the same problem. Application Desktop It helps in opening a virtual (or physical) console directly on the affected systems. Then you can begin corrective actions from the Application Desktop itself. Document Close the problem and document the solution, for future reference.

OVO performs the following tasks: Events Notes an event in your environment. Reports Generates a meaningful message, or report, about the event. Actions Responds to the event with an action.  OVO uses messages to communicate . Messages are structured, readable pieces of information about system status, system events, or problem related to a managed node within the system


contd

About Events
An event is a particular fault or incident within the computing environment that occurs on an object. Typically, an event represents either a change in status or a threshold violation.  Events generate messages.  The more events a system generates, the more messages users are likely to receive.


About Messages
Messages are structured chunks of information that are triggered by events.  OVO intercepts events, then creates messages to inform you of those events.


1) Intercepting Messages OVO intercepts messages from a variety of sources, including: Logfiles message information from application and system log files SNMP Events events on the management server and on selected agent platforms MPE/iX Consoles messages sent to the MPE/iX console OVO Messages generate messages by an OVO command or API Monitored Objects threshold levels for monitored objects which when exceeds the configured threshold levels, messages will be generated by OVO

2) Applying Template Conditions to Messages After an event has been identified, OVO applies template conditions, which act like filters, to determine whether to generate a message or to suppress the information about the event. 3)Linking Messages Logically Messages may also be linked logically to one or more messages and automatic actions attached to the correlated output 4)Processing Messages OVO uses messages to perform the following tasks: Communicate information about events. Inform users of status changes within the environment. Trigger corrective actions. contd

About Actions An action is a response to a message. If the event that creates the message is a problem, OVO can start an action to correct the problem. Actions are also used to perform daily tasks, such as starting an application every day on the same nodes. An action can be a shell script, program, command, application start, or any other response required. OVO offers the following types of actions: Automatic actions Automatic actions are preconfigured, message-linked responses to problems. Automatic actions do not require operator interaction. OVO starts these actions as soon as a message is received. Operator-initiated actions Like automatic actions, operator-initiated actions are preconfigured, message-linked responses to problems. These actions are started and stopped by an operator. Applications

Operator-initiated actions Like automatic actions, operator-initiated actions are preconfigured, message-linked responses to problems. These actions are started and stopped by an operator due to following reasons : Manual Operations Preconditions Applications Applications are scripts or programs that have been integrated into OVO. Unlike operator-initiated and automatic actions, which are directly associated with a message and can be started or stopped from the browser windows, applications are tools that are available in the operators Applications folder

The OVO user concept distinguishes real users, such as the OVO administrator and the OVO operators, from user profiles. Types of User Roles The primary user roles of OVO are: OVO Administrator User with unlimited authority. Primarily responsible for installing and configuring the OVO software, and establishing the initial operating policies and procedures. Template Administrator User with limited authority. Allowed to create, modify, and delete templates and monitors only. Operator User with no authority. Uses OVO almost continuously to maintain, manage, monitor, and control systems and objects.

The OVO administrator, opc_adm, has many tasks and responsibilities within the OVO working environment as follows Customizes User Environments Maximizes Operator Efficiency Delegates Responsibility Develops Guidelines Maintains History Solves User Problems Expands OVO

Hardware Requirements
The system you select as the management server must meet the following hardware requirements: HP 9000 servers (PA-RISC 2.0 architecture or higher), with at least one HP-supported X terminal or workstation. Monitor resolution of 1280 x 1024. The monitor does not need to be physically connected to the management-server system. You can use the X-redirection mechanism and run the OVO Motif GUI remotely. Graphics board supporting at least 8-bit color planes. Mouse and Keyboard. Disk space of 5 GB and additional Disk space of 1 GB . 1 GB of RAM and additional RAM of 256 MB 2048 MB of Swap space . CD-ROM drive (optional and can be mounted remotely). contd

Software Requirements Before you install OVO, the following software must be installed on the management server correctly Operating System 1) Windows Server 2003 with Service Pack 2 and above 2) 64-bit Sun Solaris 8,9 and 10 3) Unix 11.0 and above  Oracle Database 9.2 0r 10g depending on OVO versions  Reflection X Version 8.00 or higher, Hummingbird Exceed Version 9.0 on Windows machine for remote desktop if OVO is installed on Solaris or Unix  Kernel parameters and OS patches required for OVO must be installed from OVO installation CD

The OVO agent package comes with the OVO installation CD and is available only after successful installation of OVO on the Management Server  The available agent package is then installed on the systems which are to be monitored through OVO


NNM helps us to meet the demands of rapidly growing network environment in an organization  It is the starting point for implementing a network management solution.  NNM helps you to determine the current state of your networkwhat devices are present, how they are configured, how they are behaving, their performance levels, what is currently going wrong  NNM allows you to monitor thresholds for critical network devices  NNM assists you by collecting historical information


The network needs to be in a well-configured state so that each device can be successfully accessed. Maps out your network for you  Collects critical information about your network and maintains a current log of alarms that you need to know about  Correlates collected information to help you quickly determine the probable cause of problems  Maintains a relational database from which data can be exported Provides easy access to report generation  NNM communicates with the devices on your network through standard network protocols


Consistent IP addressing scheme A list of your network-level IP addresses would help during the initial discovery process so that you can quickly verify that NNM has successfully discovered everything you need  Consistent subnet masks configured If the subnet masks on the management station or configured on your network devices are correct, discovery will be successful  DHCP address ranges identified It is suggested to assign a range of IP addresses to mobile computers when they access your network to prevent disconnection from your network


contd

Consistent name resolution scheme (such as DNS or NIS) If you have name resolution in place prior to NNMs initial discovery process, hostnames are used for map symbol labels, rather than IP addresses. Hostnames generally make the NNM maps and alarm messages more meaningful  SNMP agents configured on each device Know the agents GET- and SET-community names Update the trap-forwarding (trap destination) list to include the NNM management station Know which MIB is being used and obtain a copy of it to load into the NNM management stations MIB database.


The Software and Hardware requirements for NNM installation is same as that in case of OVO installation

OVIS provides a single integrated view of your Internet and related services. It is designed to help organizations predict, isolate, diagnose and troubleshoot problems, manage and report on service level agreements  OVIS uses probes to measure availability, response time, and other performance metrics for Internet and related services Service level violations and Service level agreements are also monitored and reported  OVIS provides a Web-based dashboard to view data about the service levels. The Dashboard is a collection of gauges, graphs OVIS can also generate alarms and make them available to other HP OpenView products.


OVIS

monitors services and protocols (called Service Types) such as

HTTP, FTP, DNS, E-mail and more. OVIS Configuration Manager create/configure probes that checks the use of a service and measure the performance and availability of the service. Probes are then deployed to Windows or UNIX systems from which, they probe the service automatically at set intervals. Measurements from the probes are sent back to the OVIS Management Server where they are stored in a database. Data is consolidated for reporting in the OVIS Dashboard web display.

Hardware Requirements The Windows management server must meet the following hardware requirements: Intel Pentium III, 1 GHz or faster processor Monitor resolution of 800 x 600. Mouse and Keyboard. Disk space of 200 MB. 512 MB of RAM. 50-1000 MB of temporary disk space . CD-ROM drive. contd

Software Requirements The Windows management server must meet the following hardware requirements: Microsoft Windows 2000 Professional/ Server/Advanced Server Service Pack 4 Microsoft IIS 5.0 Web Server OR Microsoft Windows XP Professional with Service Pack 1. Microsoft IIS 5.1 Web Server OR Microsoft Windows Server 2003 Standard and Enterprise editions Microsoft IIS 6.0 Web Server Internet Explorer 5.5 and above . NTFS file system is required . Virtual memory 512 MB or more .

 OVPI is a comprehensive performance management solution that automates the collection and analysis of network data, placing the information into report formats .  With OVPI, the network administrator has the ability to manage service levels, optimize existing resources, accurately plan future growth, and predict network problems before they occur.  OVPI supports the following operating systems: HP-UX, Solaris and Windows

 OVPI Database It is the primary repository for the data that is collected, processed, and reported on by the other OVPI applications. This component configures the database server for OVPI and creates the OVPI schema  OVPI Performance Manager IT provides the engine for storing, processing, and accessing data collected from applications and network devices throughout your network. Data is automatically aggregated and summarized by Performance Manager.  Web Access Server IT acts both a service and an application. It is installed as a service, and the following OVPI client applications are automatically installed with it: Report Builder, Report Viewer, Web Access Server (application server), and Management Console. It provides web based reports. contd

 OVPI Clients The clients provide interface to OVPI. You can install a client on any networked system. The OVPI client applications are: Report Builder : Lets you build and customize reports with multiple tables and graphs based on data from the OVPI database. Report Viewer : Lets you interactively view, modify, save and print reports. Web Access Server: This component contains a web-based application server, also called the Web Access Server. This application lets you view, schedule, generate, and deploy reports. Management Console: Lets you perform administrative tasks using following applications: 1) Database Tuner 2) SNMP Discovery 3) Type Discovery 4) Polling policy Manager contd

Management Server It provides management services, as well as forms that are deployed during report pack installation, to the Management Console application Remote Poller It collects data from nodes in the network and then stores the data on server running the OVPI database .

.


Data collection  Raw data to rate data processing  Rate data to hourly data summarization  Hourly data to daily, monthly, forecasting summarization  Report viewing and building


Hardware Requirements The management server must meet the following hardware requirements: Intel Pentium III, 1 GHz or faster processor Monitor resolution of 800 x 600. Mouse and Keyboard. 1600 MB for Sybase database (HPUX/Solaris/Windows) and 800 MB for Oracle database (HPUX/Solaris/Windows). 1 GB of RAM(Sybase/Oracle on HP-UX) , 4 GB of RAM (Sybase/ Oracle on Solaris) , 2 GB of RAM(Sybase/Oracle on Windows). 50-1000 MB of temporary disk space . CD-ROM drive.

Software Requirements The Windows management server must meet the following hardware requirements: Operating System HPUX 11.11, Solaris 8,9 , Windows 2000 Server with SP4, Windows 2003 (Standard /Enterprise), Windows XP Database -Sybase/Oracle Java 1.4.2_02 software and related Patches Internet Explorer 5.5 and above .

Reporter is made up of a number of programs that work together. These programs complete actions as follows: (1) Discover systems that are running OpenView Performance agents for Windows systems or OpenView Operations (OVO) subagents on your network; (2) Schedule periods of time during which data is collected on those systems or from the OVO database ;and (3) Generate reports that contain the collected data.  Reporter allows you to access reports through an automatically generated Web page that allows you to view information of the systems targeted for reporting


Reporters main window shows the following components Discovery Area Metric Lists Reports Schedule Discovered Systems Customers (customer-segmented reports)

contd

Discovery

Area Before Reporter can access a system, it must be "discovered." Reporter

is designed to discover Windows or UNIX systems through a couple of different methods. After a system is discovered, it is added to the Discovered Systems area of the Reporter hierarchy. Metric Lists It controls what information is gathered from a system into the Reporters database. Reports Available reports are listed in families under the Reports icon. Schedule The Schedule controls when actions occur within Reporter. Discovered Systems It shows systems that have been discovered by the discovery programs. Discovered systems are placed in groups for easier access and reporting. contd

Customers

(customer-segmented reports) This section shows the specific customers and discovered systems associated with the customer.

Hardware Requirements The management server must meet the following hardware requirements: Intel Pentium III, 1 GHz or faster processor Monitor resolution of 800 x 600. Mouse and Keyboard. Disk space of 200 MB. 512 MB of RAM. 50-1000 MB of temporary disk space . CD-ROM drive.

Software Requirements The Windows management server must meet the following hardware requirements: Microsoft Windows 2000 Professional/ Server/Advanced Server Service Pack 4 Microsoft IIS 5.0 Web Server OR Microsoft Windows XP Professional with Service Pack 1. Microsoft IIS 5.1 Web Server OR Microsoft Windows Server 2003 Standard and Enterprise editions Microsoft IIS 6.0 Web Server Internet Explorer 5.5 and above .

SIP

enables you to give each of your customers a personalized view of

the managed environment through the following benefits and features: Gives your customers a personalized view: Customers see only their own network and service management data, while you, the administrator or operator, can see the data of one, many, or all of your customers. Provides information from many sources: 1)OpenView Operations (OVO for UNIX and Windows) and Service Navigator (OVSN) integration 2)Network Node Manager (NNM) integration 3)OpenView Internet Services (OVIS) integration 4)OpenView Performance Manager (OVPM) integration 5)OpenView Performance Insight (OVPI) integration 6)OpenView Reporter integration contd

Provides a secure environment: Security through authentication and authorization. Easy configuration and administration: SIP Configuration Editor for (1) Configuring connections between SIP and management products, and (2) Configuring users, roles and management data filters. SIP Administration Pages for (1) configuring and viewing the customer model, (2) configuring the message board, (3) configuring bookmarks, (4) logging in as another user, and (5) troubleshooting portal problems that may arise. Portal view editing, including reordering of tabs and modules and customizing the modules.

Hardware Requirements The Windows management server must meet the following hardware requirements: Intel Pentium (or AMD) 1 GHz processor-based computer CD-ROM drive (for installation) 512 MB RAM (preferably 1 GB RAM) 250 MB free disk space on one drive (either FAT or NTFS) 512 MB free paging file space

Software Requirements The Windows management server must meet the following hardware requirements: OS version 2000 or 2003. TCP/IP Services installed and configured. Microsoft Internet Information Server (IIS) 5.0 or 6.0. On Windows 2000 Server Microsoft Windows Scripting Host Java 1.4.2 Software Developers Kit (SDK), Java 1.4.2 Runtime Environment (RTE). Netscape Navigator 7.x or later or Internet Explorer 5.5 or later

Hardware Requirements The Unix management server must meet the following hardware requirements: HP 9000 workstation, Series 700 or 800 CD-ROM drive (for installation) 512 MB RAM (preferably 1 GB RAM) 250 MB free disk space on one drive 512 MB swap

Software Requirements The Unix management server must meet the following hardware requirements: HP-UX (versions 11.0 and 11.11), which includes: The Common Desktop Environment (CDE) X Windows and OSF/Motif HP-UX patch PHSS_24303 Java 1.4.2 Software Developers Kit (SDK), Java 1.4.2 Runtime Environment (RTE). Netscape Navigator web browser (version 6.2 or later) with JavaScript and cookies enabled.