| 1 |
The following requirements/outstanding issues exist for OVMRTG. |
| 2 |
=============================================================== |
| 3 |
|
| 4 |
Installation Version 0.2 |
| 5 |
------------------------ |
| 6 |
|
| 7 |
After installing MRTG and HPOV the following additional customisation |
| 8 |
needs to be done. |
| 9 |
The file $rundir/installov.cmds should be modified to reflect the locations of |
| 10 |
1) the mrtg executables ($rundir) |
| 11 |
2) the web output directory ($webdir) |
| 12 |
3) the name of the cron file within $rundir ($cronfile) |
| 13 |
4) the name of the root HTML file within $webdir ($roothtml). |
| 14 |
5) the name of the HTML rebuild file ($buildhtf) |
| 15 |
6) the company name for display in the HTML ($company) |
| 16 |
7) the directory where the HPOV databases exist {$OV_DB} ($ov_db) |
| 17 |
8) the directory where snmpCol.conf is found {$OV_CONF} ($ov_conf) |
| 18 |
9) Any command line changes to run the perl from within HPOV. May need |
| 19 |
full directory paths to both perl and ovmrtg scripts |
| 20 |
|
| 21 |
NT: |
| 22 |
Suggested defaults for the above items under NT: |
| 23 |
3) mrtgkick.bat |
| 24 |
5) buildht.bat |
| 25 |
7) /OpenView/databases |
| 26 |
8) /OpenView/conf |
| 27 |
|
| 28 |
Then installov should be run from within the mrtg directory to |
| 29 |
update the scripts. |
| 30 |
|
| 31 |
Next the perl script ovupdate should be run to create the new ovmrtgc.csv file |
| 32 |
|
| 33 |
mrtgmenu then needs to be placed into $OV_REGISTRATION/C and be readable |
| 34 |
by the group of users that might need to change mrtg targets. |
| 35 |
You will need to shutdown and restart ovw to see the menu items |
| 36 |
appear under the Misc menu. You do not need to do an ovstop! |
| 37 |
|
| 38 |
The gif files for MRTG banner are located in the common directory |
| 39 |
$webdir for all the HTML's to reference a single copy. |
| 40 |
|
| 41 |
ISSUES |
| 42 |
------ |
| 43 |
|
| 44 |
It is assumed that the HPOV host is also the web server for MRTG |
| 45 |
so that mkdir's can be executed in the WEB directories. |
| 46 |
|
| 47 |
As the target/s are selected from the HPOV screen, it is assumed |
| 48 |
that HPOV already knows what the read community names are for |
| 49 |
these devices. OVMRTG uses this fact to alleviate the need for |
| 50 |
it to know community names. |
| 51 |
|
| 52 |
Little error checking and reporting is currently done. If someone is |
| 53 |
displaying the data collection screen then ovadd and ovdel will |
| 54 |
fail and will NOT report failure to the user. |
| 55 |
|
| 56 |
The SNMP sysName is used to create directories in the web area and is also |
| 57 |
used for most file and web names for that device. As such, the system name |
| 58 |
needs to be unique and set for each device that will be monitored. If it is |
| 59 |
not set for each device then the IP address is used instead. |
| 60 |
Code that translates IP Address to sysname can be setup in ovsysnms |
| 61 |
and in cfgmakerov if desired. All directories, configs html files etc |
| 62 |
are produced for each target by the unique sysname. |
| 63 |
|
| 64 |
At present the data collects into the snmpCollect directory forever. |
| 65 |
I've started to write a cleanup routine that will be able to keep |
| 66 |
only recent history. (see ovcullfile) |
| 67 |
|
| 68 |
ovdel does not destroy the directories that are created for the deleted target |
| 69 |
(a safety measure). If you want to clean them up it is currently a |
| 70 |
manual process. |
| 71 |
|
| 72 |
Access |
| 73 |
------ |
| 74 |
|
| 75 |
$rundir & $webdir files & directories should be rw for the group of people |
| 76 |
that might be changing mrtg targets from within HPOV |
| 77 |
|
| 78 |
$OV_CONF/snmpCol.conf needs to be rw for OVMRTG users |
| 79 |
|
| 80 |
In the mrtg executable directory, the .cfg files are created. |
| 81 |
A file called 'collects' is also created as a work file. |
| 82 |
DO NOT create a file in this directory with this name. |
| 83 |
|
| 84 |
CRON |
| 85 |
---- |
| 86 |
|
| 87 |
cron needs to be setup by the user. Typically a line like this works: |
| 88 |
0,5,10,15,20,25,30,35,40,45,50,55 * * * * /opt/mrtg/run/mrtgc 2>/opt/mrtg/run/log 1>&2 |
| 89 |
The equivalent job should be setup under NT. |
| 90 |
OVMRTG should not care if the host is Unix or NT. |
| 91 |
|
| 92 |
The end of ovadd and ovdel may be customised to perform extra tasks |
| 93 |
by the cron job. |
| 94 |
|
| 95 |
Usage |
| 96 |
----- |
| 97 |
|
| 98 |
Once setup, the user selects the OVMRTG target/s from the OV screen. |
| 99 |
The Misc menu item is then selected, followed by Mrtg Actions and |
| 100 |
then select either the 'Add/Update' or 'Stop collecting' options. |
| 101 |
The third option, Show MRTG Targets, works on Unix systems ONLY at |
| 102 |
present. I only have the UNIX NNM developers kit. This option |
| 103 |
'selects' the current targets on the screen for easy updates. |
| 104 |
|
| 105 |
To understand what happens for an add/update, see the file newrtrov.txt |