nv-l

Re: NV 5.1 "nvsniffer" config.

1998-09-29 08:34:55
Subject: Re: NV 5.1 "nvsniffer" config.
From: Scott_Donohoo AT TIVOLI DOT COM
To: nv-l AT lists.tivoli DOT com
Date: Tue, 29 Sep 1998 08:34:55 -0400
Joe,

The NetView for Unix 5.1 version of nvsniffer is not that dynamic. It
detects TCP services on nodes in your database, creates fields in the
objects for the nodes that respond (such as isFTP=True), then creates
collections of nodes based on those fields.

There is no periodic checking of the services or status icons created to
represent the service. If you discover a new node that you want included or
start a new service you want detected, you will need to run nvsniffer
again.

Scott Donohoo
Tivoli Customer Support Team (NetView for Unix)




"Prokott, Joe" <Joe.Prokott AT WESTGROUP DOT COM> on 09/28/98 05:27:00 PM

Please respond to Discussion of IBM NetView and POLYCENTER Manager on
      NetView et alia <NV-L AT UCSBVM.UCSB DOT EDU>

To:   NV-L AT UCSBVM.UCSB DOT EDU
cc:    (bcc: Scott Donohoo/Tivoli Systems)
Subject:  NV 5.1 "nvsniffer" config.





Does the new NV 5.1 "nvsniffer" functionality periodically status check the
specific TCP ports and display their status via a symbol color change in
the
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 just
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: joe.prokott AT westgroup DOT com

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