OK ! Thank you, now It's working fine !!! But do you know if is it possible to create a ssl tunnel between mon "server" and clients ?
Jim Trocki a écrit : > On Tue, 11 Sep 2007, Divers wrote: > >> Someone can help me with an example how to configure mon with trap ? >> > > invoke trap.alert from your slave like this: > > alert trap.alert -U mon-username -P trap-password 88.191.36.126 > > > into your auth.cf place this: > > trap section > > a.b.c.d mon-username crypt-trap-password > > or > > hostname mon-username crypt-trap-password > > or > > * mon-username crypt-trap-password > > a "*" in the "hostname" column means allow traps from any host. a "*" > in the > "mon-username" column will tell mon there's no need to authenticate. > if you bypass this authentication, you should at least specify a hostname > or ip address in the "hostname" column so that mon will ignore traps > from any hosts other than the ones listed in auth.cf. > > crypt-trap-password is the crypt(3) form of the password. you can > use the "htpasswd" tool which comes with apache. like this: > > $ htpasswd -n mon-username > New password: > Re-type new password: > xyz:e5zg1O8LmnpC. > > you would insert everything after the ":" into your auth.cf as shown > above. > > mon will automatically pass some parameters needed by the trap.alert via > environment variables, such as the name of the "group" and the service > name. > trap.alert will then do the right stuff to create the trap PDU and send > it to the machine(s) you wish. in the above example it will send the > trap to host 88.191.36.126. > > the recipient host will then try to apply the message to the group and > service name found in the PDU. if either the group or service names in > the > pdu do not match a group and service in the mon.cf, then it will try to > apply it to a group named "default" which has a service named "default". > > i guess that's just about it. i think all of the above is actually > documented > in the man page and in doc/README.traps, except for trap.alert, which > is simple enough that its operation should be self-evident. > > however, there should be documentation on how to operate trap.alert. the > doc/README.traps document is very close to this, but a bit out of date > because > it refers to "remote.alert" rather than trap.alert. i'll update it with > explanations of all the trap.alert options.. > > you may also want to check out the "redistribute alert" option in the > mon man > page. > _______________________________________________ mon mailing list mon@linux.kernel.org http://linux.kernel.org/mailman/listinfo/mon
