RE: [nv-l] nvsniffer

["Liu, David" <david.liu@eds.com>]

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
entry of

$*.*.*.*.*
^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?

Regards,
David


-----Original Message-----
From: owner-nv-l@lists.us.ibm.com [mailto:owner-nv-l@lists.us.ibm.com]On
Behalf Of James Shanks
Sent: Monday, April 11, 2005 3:04 PM
To: nv-l@lists.us.ibm.com
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.

James Shanks
Level 3 Support  for Tivoli NetView for UNIX and Windows
Tivoli Software / IBM Software Group


                                                                           
             Paul                                                          
             <pstroud@bellsout                                             
             h.net>                                                     To 
             Sent by:                  nv-l@lists.us.ibm.com               
             owner-nv-l@lists.                                          cc 
             us.ibm.com                                                    
                                                                   Subject 
                                       Re: [nv-l] nvsniffer                
             04/11/2005 08:50                                              
             AM                                                            
                                                                           
                                                                           
             Please respond to                                             
                   nv-l                                                    
                                                                           
                                                                           




David,
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
a service.

Paul


Liu, David wrote:

>Dear list,
>
>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
>the following:
>
>1) nvsniffer no need snmp access to the monitoring device (it is
pingable)?!
>
>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)
>
>Regards,
>David
>
>
>