Contents

Contents 1

OverTime User Guide 2

Over View: 2

Adding devices to Monitor (10 second tour). 3

Stopping devices from being Monitored (10 second tour). 5

Finding which devices are currently monitored by OverTime (10 second tour). 6

Looking at the results (10 second tour). 7

Adding a Device 11

I/O Collections: 11

User Specified: 12

PingTime User Guide 13

Over View: 13

PingTime Interactive: 13

PingTime Non-Interactive: 14

Initial Set Up: 14

Adding a Collection to PingTime for OpenView 15

OverTime User Guide

 

Over View:

OverTime is an application that brings together the power and convenience of HP OpenView’s data collection facilities and user interface with the graphical trending database facilities of Tobi Oetiker’s RRDTool.

From a menu item within OpenView, OverTime takes a user selected device from the HP OpenView’s map and

  1. Decides what statistical information can be collected from the device to depict utilisation levels
  2. Gathers these details directly from the device.
  3. Configures HP OpenView to collect the information from the device.
  4. Configures RRDTool databases to store the collected statistics.
  5. Updates an HTML page so that the device’s statistics can be viewed.

When the user selects the device on the HTML page via a browser, OverTime

  1. Updates the RRDTool database from the information collected by HP OpenView.
  2. Generates the appropriate graphic images for the statistics gathered for this device.
  3. Generates an HTML page for the web server to display. (The same display can also be generated from the command line so that it may be relocated to different server for later display.)

In addition to the above HP OpenView menu item, 2 other menu items allow you to firstly stop collecting the data and secondly, show you what devices are currently being monitored by OverTime.

OverTime provides routines that, when run regularly

1) update all the RRDTool databases from the HP OpenView collected information and 2) prevents the HP OpenView collected information from growing until all available disk space is consumed.

 

Adding devices to Monitor (10 second tour).

To add a new device to be monitored by OverTime, select the device on the OpenView map. Let us say we want to monitor "TestSwitch1900" in the below map:

Open the "Misc" menu item and then select "OverTime Actions", then select "Add/Update Target/s".

 

A window like the one shown here will appear showing the progress of the addition:

When the addition has completed, the "Restart" button will become active and the messages window will show "OverTime Add/Update Completed".

 

 

Stopping devices from being Monitored (10 second tour).

To stop an OverTime currently monitored device, select the device on the OpenView map:

Open the "Misc" menu item and then select "OverTime Actions". Finally, select "Stop Collecting Target/s":

A window like the one shown above for the addition above will appear showing the progress of the removal.

When the removal has completed, the "Restart" button will become active and the messages window will show "OverTime Stop Completed".

 

 

Finding which devices are currently monitored by OverTime (10 second tour).

To find which device are currently being monitored by OverTime, open the "Misc" menu item and then select "OverTime Actions". Finally, select "Show Current Targets":

OverTime will open as many windows as needed within OpenView to select and display the currently monitored devices. As you can see, two devices are monitored here:

 

 

 

Looking at the results (10 second tour).

From your browser, select the URL for the OpenView server and OverTime’s area.

http://MyOpenView:8880/OverTime/index.html

OR if OverTime is integrated with Report Presenter, http://MyOpenView:8880/OvCgi/nnmReportPresenter.exe and then select OverTime in the pane on the left.

Click on the system name link for the device you wish to view. A page showing the current information for all the items being monitored on that device will appear:

Or, under Report Presenter:

To view historical information for any individual item, simply click on the title or the graph for that item. A page showing the current information as well as various historical views for that item will be show:

To go back to the main menu, click on the link at the bottom of the displayed pages.

 

Adding a Device

Many different statistics can be collected and monitored by OverTime. Types of collections can be categorized by the collection/s that may be in existence when OverTime is run. The following categories will be explained below: I/O, User Specified and PingTime.

I/O Collections:

To collect interface traffic statistics for Input/Output type devices like routers, switches and hubs, simply select the prediscovered device on the OpenView map and then run the Add/Update menu item (found under Misc, OverTime Actions). OverTime tries to find any existing collections for this device. If there are none or if I/O* collections already exist for this device, OverTime then queries the device looking for I/O interfaces that may be operational to add to the list of collections. The interface must be administratively Up, be reporting a non-zero interface speed that is also less than 400Gb and actually be able to be queried for the snmp OIDs ifInOctets and ifOutOctets. If the interface provides the snmp values for ifInErrors and ifOutErrors, then these are also collected. If the device supports CiscoAvgBusy5 this is also included in the list of collections.

OverTime creates the collection entries and signals OpenView to add these to the list of collections performed by OpenView’s snmpCollect.

If there were no previous collections and RRD file for the interface/instance, then the default sample_time value is used for the collection and the creation of the RRD. (If sample_time is not specified in the file overtime.cfg a default of 300 seconds or 5 minutes is used.)
OverTime creates all necessary directories for the new device. A directory in the web server’s area (under OverTime) to hold the graphics created for the device is created.

OverTime creates a directory (under OverTime\data) to hold the RRD files (1 RRD per interface).

OverTime create a master configuration file for the device. This plain text file contains the list of interfaces being monitored, one per line. For I/O collections, each line has four values on it with the first three blanks separating the 4 values and takes the form:
Interface Number; a 0, 1 or 2; a user modifiable threshold and a user modifiable title.

The threshold and title are initially set from values taken from the device (interface speed or 100% for CPU) for threshold and interface name for title.

OverTime updates/creates the master html page (default of index.html) in the web servers OverTime directory. The devices are listed on this page in alphabetical order (case sensitive). The name chosen for the device is its snmp sysName or, if that is blank, an IP address from the device with first preference given to any loopback address discovered on the device.

 

User Specified:

When an Add/Update is run, if OverTime finds non-IO* collections already active, then these collections are setup as for I/O except:

In the master configuration file, a group of lines is added for each collection. I.E. if a collection for and OID called DiskSpaceUsed existed, then a group of lines would be added where the first line indicated that DiskSpaceUsed was being collected. Each subsequent line in the group would relate to an instance of this (lets say a disk drive) and the group would be terminated by a line with nothing on it. When viewed through your browser, this group would appear on the device’s main page as a single graph, with a line for each instance (disk drive).
When Add/Update is run, if both I/O and non-IO collections are already active, then OverTime will setup for both types as explained above.

* I/O Collections are collections on ifInOctets, ifOutOctets, ifInErrors, ifOutErrors, sysUptime and CiscoAvgBusy5.

* non-I/O collections other than those listed as I/O. This includes expressions.

PingTime User Guide

 

Over View:

PingTime is an application that, in concert with OverTime, shows Ping response times from Cisco routers on the network to IP addresses. PingTime works both interactively from a web browser and on a scheduled basis. The PingTime executable should therefore live in the same directory as devdtl and devmst.

PingTime Interactive:

To run PingTime from your browser you will need to enter a URL such as:

For OpenView on Unix

http://host/OvCgi/PingTime?CiscoRouterIP+TestIP1+TestIP2+etc

For OpenView on NT

http://host/OvCgi/PingTime.exe?CiscoRouterIP+TestIP1+TestIP2+etc

where "CiscoRouterIP" is the IP address of the Cisco router to use as the test source.

"TestIP1 TestIP2 etc" is a list of IP addresses to test response times from this router.

In the example below, 10.1.1.12 is the router and the other addresses are the targets to test.

PingTime Non-Interactive:

Initial Set Up:

For PingTime to record the response times, we need to establish some tasks to run on a regular basis (via Cron or At). This task will run every xxx seconds, where xxx is the collection interval. If you want 5 minute samples, then this command file should be set to run every five minutes. The command file is a simple text file that lives in /var/opt/OverTime/cfgs/. The command file’s name is prefixed by a name you can specify from the overtime.cfg file (from $OV_BIN). The default value for the parameter "pt_cmds" is "PingTime-" which means that the command file that will be run would be /opt/OverTime/cfgs/PingTime-300 for a 5 minute collection in Unix and /OverTime/cfgs/PingTime-300.bat on NT. The "300" indicates this command file will be run every 300 seconds (as a convenient reminder). When the first PingTime entry is created, this file will be created, otherwise it is simply updated. If you have set a different "sample_time" in overtime.cfg, then all new PingTimes will be created with this interval. You need to ensure that a suitable Cron/At also runs at this interval and runs the appropriately named PingTime-xxx. This is the once only configuration that you need to perform.

A Unix "cron" entry such as :

0,5,10,15,20,25,30,35,40,45,50,55 * * * * /var/opt/OverTime/cfgs/PingTime-300 > /var/opt/OverTime/logs/PingTime-300.log

would run the collections every 5 minutes and also keep a simple log.

An "at" command such as:

at 23:55 /every:m,t,w,th,f,s,su \OverTime\bin\batch.bat

might be the 11:55pm instance that was set in place by "schedule.bat" that comes with PingTime for NT.

 

 

Adding a Collection to PingTime for OpenView

To add a new collection to PingTime you run the otadd command:

"otadd –pingtime CiscoRouterIP TestIP1 TestIP2 etc". This instructs PingTime to create the appropriate files (as it does with OverTime) and also update the PingTime-xxx command file. The –pingtime tells otadd to create a PingTime configuration. (PingTime expects OpenView will already know the Cisco router’s snmp set community string.) "CiscoRouterIP" is the IP address of the Cisco router to use as the test source.

"TestIP1 TestIP2 etc" is a list of IP addresses to test response times from this router.

If the router does not already appear in the index.html page for OverTime, then this will add it. The PingTime graphs will then appear as if they were additional interfaces, but with stacked histograms depicting the Maximum, Average and Minimum response times, like this: