Mark,
I'll give you a few examples from the NT side...
1) I wrote a (perl) script that executed a remote SQL query on
a remote node. The remote-querey told me the health of the database
on the remote-system.
Using the nvsniffer on NT... I used the standard "port-sniff" discovery
option to find my SQL-servers, and then use my perl-script to actually
give me the health of the remote database. nvsniffer used the status
of this script to set the status of my "database" icon at the interface
level.
2) I got a public-domain perl script that returns a web-page from a
web-site. I modified it slightly to work with nvsniffer, and used the
standard port-sniff to sniff-out all my web-servers (port 80), and then
used the perl-script to validate that I was actually getting pages from
the web-server. nvsniffer was again used for icon control at the
interface level, as well as taking care of scheduling which nodes were
automatically polled, and when.
I also added some code to my script which puts info into the ovw
database, so that I now not only know if my web-servers are up or not,
but also what the round-trip time is to get a page.
Hope this helps.
Regards,
Gary Boyles, Intel
-----Original Message-----
From: James Shanks [mailto:James_Shanks@TIVOLI.COM]
Sent: Monday, September 13, 1999 5:46 AM
To: NV-L@UCSBVM.UCSB.EDU
Subject: Re: UNIX vs. NT functionality -- NetView 5.1.2 level
Basically, nvsniffer on UNIX does discovery only, while on NT is has a
status
function as well, which makes it much more useful. See the
\usr\ov\doc\nvsniffer.readme for details.
James Shanks
Tivoli (NetView for UNIX) L3 Support
Mark van Kerkwyk <kerkwyk@COMTECH.COM.AU> on 09/12/99 01:26:08 AM
Please respond to Discussion of IBM NetView and POLYCENTER Manager on
NetView
<NV-L@UCSBVM.UCSB.EDU>
To: NV-L@UCSBVM.UCSB.EDU
cc: (bcc: James Shanks/Tivoli Systems)
Subject: Re: UNIX vs. NT functionality -- NetView 5.1.2 level
Hi James,
thanks for info, would you mind elaborating on the differences between
nvsniffer on UNIX and NT
thanks
Mark :-)
======================================================================
This email message has been swept by MIMEsweeper.
|