NetView V5.1 nvsniffer will create an icon for each service at
the "Interface" submap level, and then change the color of that
service icon. If you have the propogation set to "propogate
most critical" (not the default) set in the service smart-set, then
you will see the icon change in the top-level service smart-set.
If not... then you won't.
In regard to the event that is sent -- this will be a
"Service Event Normal/Narginal/Critical", and not an Interface event.
You have to remember that when you start this up, that you can
have a "discovery" test, and a "status" test.
To make sure that the status is checked periodically, you should
have started nvsniffer with the following two flags:
-s = check status
-r xx = run check (viat at-job) every xx minutes
I would also suggest that you limit the number of threads
that are running (e.g. -t 2) since this could eat a lot of CPU. I'd also
also be aware of the timeout value (i.e. -T xx).
Gary Boyles, email@example.com
> -----Original Message-----
> From: Prokott, Joe [SMTP:Joe.Prokott@WESTGROUP.COM]
> Sent: Monday, September 28, 1998 2:27 PM
> To: NV-L@UCSBVM.UCSB.EDU
> Subject: NV 5.1 "nvsniffer" config.
> Does the new NV 5.1 "nvsniffer" functionality periodically status check
> specific TCP ports and display their status via a symbol color change in
> NetView maps and generate the appropriate event(s) when the particular TCP
> port is unreachable/reachable? Or does the nvsniffer functionality just
> check for the existence of the TCP port and nothing more (i.e., no ongoing
> status checking)? The man page on nvsniffer seems to indicate that it
> discovers the TCP services, but it does not mention anything about ongoing
> status checking of these services. Thanks,
> Joe Prokott - West Group
> Network Architect
> 610 Opperman Drive
> St. Paul, MN 55123
> Phone: 651-687-4536
> Fax: 651-687-6946
> E-mail: firstname.lastname@example.org