You seem to have 2 separate issues here. You should certainly be able
to status poll your box using ping and your seedfile entry looks OK to
do that, except.....
that ^ character to force ping-polling may not be supported if this is a
7.1.2 NetView. I'm not sure when that syntax arrived - someone else on
the list probably knows this.
nvsniffer, by default will not test ports of down boxes so you need to
resolve the status issue first. You can run nvsniffer with the "-o"
flag which means that nvsniffer will also test nodes that have a
critical status, but, as I say, you need to get your status issue
sorted, rather than circumvented.
Liu, David wrote:
James and Paul,
Thanks for your advice. I have found the trap from trapd.conf.
The server I monitored is not snmp accessible, when I ping it, it become
green (UP) and after some time, it become down. My netmon.seed file has the
^10.1.2.3 (this is the IP address of the device)
I also create a log file using the -l option of nvsniffer. The error message
I got is:
WARNING: node object 66534 has a status of Critical; skipping it.
So it does not send event.
What could be the reason?
From: firstname.lastname@example.org [mailto:email@example.com]On
Behalf Of James Shanks
Sent: Monday, April 11, 2005 3:04 PM
Subject: Re: [nv-l] nvsniffer
I might also add that the nvsniffer traps are defined in trapd.conf. From
the definitions, you should at least be able to see the trap number and
some idea of what to expect. If you don't see the definitions in your
current copy of /usr/OV/conf/C/trapd.conf, then it may because you are
running an old copy. In that case you can find them defined in the
installation copy, which is /usr/OV/newconfig/OVSNMP-RUN/trapd.conf.
Level 3 Support for Tivoli NetView for UNIX and Windows
Tivoli Software / IBM Software Group
Sent by: firstname.lastname@example.org
Re: [nv-l] nvsniffer
Please respond to
For NetView to monitor the mail service/server, NetView needs
to be able to make a connection to the service in question(I think
its simply a tcp connection check, but I could be incorrect, someone
please correct me if I am). As for being able to test the nvsniffer
trap, I would think you would be able to simply firewall the connection
between NetView and the target device for the port in question. I usually
try to use the network tools available in lieu of stopping and starting
Liu, David wrote:
Due to some historical reasons, we have some NV7.1.2 running. One of the
customers need to monitor its mail service. I need your advise to confirm
1) nvsniffer no need snmp access to the monitoring device (it is
2) what kind of trap nvsniffer is sending when it finds the (mail) service
is down. How can I test it without stop the service(snmptrap)?
The command I'm using is
/usr/OV/bin/nvsniffer -s -n hostname (the smartset exist)
Tivoli Certified Consultant & Instructor
Skills 1st Limited, 2 Cedar Chase, Taplow, Bucks, SL6 0EU, UK
Tel: +44 (0)1628 782565
Copyright (c) 2005 Jane Curry <email@example.com>. All rights