[Top] [All Lists]

Re: [nv-l] nvsniffer

To: nv-l@lists.us.ibm.com
Subject: Re: [nv-l] nvsniffer
From: James Shanks <jshanks@us.ibm.com>
Date: Mon, 11 Apr 2005 09:03:44 -0400
Delivery-date: Mon, 11 Apr 2005 14:04:24 +0100
Envelope-to: nv-l-archive@lists.skills-1st.co.uk
In-reply-to: <425A72AD.6050204@bellsouth.net>
Reply-to: nv-l@lists.us.ibm.com
Sender: owner-nv-l@lists.us.ibm.com

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

             h.net>                                                     To 
             Sent by:                  nv-l@lists.us.ibm.com               
             owner-nv-l@lists.                                          cc 
                                       Re: [nv-l] nvsniffer                
             04/11/2005 08:50                                              
             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
a service.


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
>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)

<Prev in Thread] Current Thread [Next in Thread>

Archive operated by Skills 1st Ltd

See also: The NetView Web