1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
132
133
134
135
136
137
138
139
140
141
142
143
144
145
146
147
148
149
150
151
152
153
154
155
156
157
158
159
160
161
162
163
164
165
166
167
168
|
$Id: INSTALL,v 1.18.2.4 1999/11/15 02:34:03 trockij Exp $
INSTALLATION
------------
Several parts:
1. mon, the server
2. Mon::Client, the Perl library used by some clients.
3. C programs in mon.d
REQUIREMENTS
------------
The "mon" daemon uses Perl 5.n, where n >= 004_04. You really want at
least 5.004_04, which fixes a few memory leaks, and has a Sys::Syslog
which works with Linux. Mon also requires that *.ph be created from the
system header files. Normally this is done manually during Perl
installation by these means:
cd /usr/include
h2ph *.h sys/*.h
However, if you're running Linux you may need to run
cd /usr/include
h2ph *.h sys/*.h asm/*.h
If you try to run mon and Perl complains with the "did you run h2ph?"
message, then chances are this step wasn't done.
You'll need the following modules for the server to function, all of
which are available from your nearest CPAN archive, or the place
where you got mon:
-Time::Period
-Time::HiRes
-Convert::BER
-Mon::*
All of the monitor and alert scripts that are packaged with mon are
actually *optional*. However, this is what you'll need for each special
monitor:
freespace.monitor
The disk space monitor requires the "Filesys::DiskSpace" Perl
module from CPAN.
fping.monitor
Requires the "fping" code, probably available from the same
place that you go this package.
telnet.monitor
This requires the Net::Telnet Perl module, available from
CPAN.
reboot.monitor
asyncreboot.monitor
netappfree.monitor
process.monitor
hpnp.monitor
All use the UCD SNMP 3.3.1 package, along with G.S. Marzot's
Perl module.
ldap.monitor
requires the Net::LDAPapi Perl module, available from CPAN.
dialin.monitor
requires the Perl Expect module, available from CPAN.
dns.monitor
requires the Net::DNS Perl module.
msql-mysql.monitor
requires the MSQL/MySQL DBD module and DBI front-end.
1. INSTALLING THE PERL CLIENT MODULE
------------------------------------
As of 0.38.8, the Perl client module is distributed as a separate
package. It is named "Mon-*.tar.gz". As of 14-Nov-1999, the most
recent distribution is Mon-0.6.tar.gz. Refer to that for installation
instructions.
If you are looking in CPAN for this module, find it in the
modules/by-authors/id/T/TR/TROCKIJ/ directory until it becomes indexed
in the categorized modules directory.
2. MON SERVER INSTALLATION
--------------------------
-Read the man page for "mon" and "moncmd" in the doc/ directory.
cd doc
nroff -man mon.1 | more
-read the "READMEs" in the doc/ directory for some useful
insight on system configuration.
-Be sure you have the required Perl modules, which are listed in this
file.
-Make your own mon.cf file, using the suppled "example.cf" (located
in the etc/ directory) as a template, or the m4-based "example.m4":
cp etc/mon.cf mon.cf
or
cp etc/mon.m4 mon.m4
-Edit the "auth.cf" file. This file controls which users can perform
what command. The default is pretty restrictive (read-only), but that's
only for safety. Currently, "moncmd" and "monshow" are the only clients
which are able to authenticate themselves to the server; "mon.cgi"
does not do authentication yet, and nor does the 2-way pager interface
However, these programs work fine in read-only mode.
-Add the following lines to /etc/services:
mon 2583/tcp # MON
mon 2583/udp # MON traps
-You may want to make a DNS CNAME entry called "monhost" for your
host that will run "mon". You can then set the environment variable
MONHOST to be this host. "moncmd" uses this variable.
-The Perl scripts look for perl in /usr/bin. You might want to change
this. I'd advise keeping a locally-installed copy of Perl if you're
going to monitor network resources and you expect this stuff to work
when some component of the network is down.
-Test it by starting "mon" from the distribution directory. Use these
arguments if you chose the non-m4 config:
./mon -f -c mon.cf -s mon.d -a alert.d
and these arguments for the m4-based config:
./mon -f -M -c mon.m4 -s mon.d -a alert.d
To get see if it's running on your machine:
./clients/moncmd -s localhost list pids
If you get some output, then things are probably OK.
Mon doesn't really need to be installed in any special location. Just
keep it on the local disk of the machine which will be running the server.
3. COMPILING THE C CODE
-----------------------
-cd mon.d
(edit Makefile)
make
make install
cd ..
to build the RPC monitor and the dialin.monitor wrapper. Keep in mind
that if this may fail for some reason (it works under Linux, Solaris,
and AIX), it is not required for the operation of mon itself.
|
