|
Scott,
NvSniffer is not a sniffer at all. You must read the nvsniffer man page
very carefully to understand it and learn how to configure it. It can ONLY
test TCP ports. It has two modes.
1)
Reads the config file, then tests the devices for the TCP ports, what ever you
told him to test, and then he generates the SmartSets based on those TCP
ports.
2)
Status mode. It only tests the TCP ports for known SmartSets or nodes. If it
detects that TCP port that is closed it will generate the
trap.
What
you need is this:
Decide
what Services you want to monitor and make config file.
Run
NvSniffer in Config mode and make some SmartSets.
Then,
run the NvSniffer in status mode, periodically, using CRONTAB or
AT.
I
think we are a little bit confused here. I think you asked,
originally, for UDP applications? Are you monitoring UDP or
TCP?
If you
monitor UDP, then NvSniffer can't do that because of the nature of UDP. For
that, get something else.
Dejan
Mijailovic
InQuent Technologies.
Listers,
First, thanks to all that replied
to my earlier post. I?m still a
little confused as to what my options are if I decide to use the nvsniffer
?feature?.
Can someone explain to me the
capabilities of the nvsniffer option?
I read the man page and it describes how you can create smartsets that
contain the port information from monitored servers. Does this mean I can configure NetView
to monitor specific TCP ports (ie., 94, 9494, etc?) If so what type of information does
this provide? Is anyone using
this feature? How does this
compare to other sniffer applications?
I?m trying to come up with a plan
to monitor the different TCP ports for the applications (see my earlier
post). I would like to avoid
introducing third party applications if at all possible; however I realize
there are some limitations to what NetView can provide. Other than the man page, the NetView
documentation is vague when it comes to this particular ?feature?.
Thanks in advance for the
responses.
Scott
|