Mark,
Forgive me if this is too blunt, but what kind of an answer are you looking for
from me?
That's a sales question. You want strategy and I am a bug fixer, not a
product manager nor an architect. The short answer
is that that there were two different development groups, one for UNIX and one
for NT. The NT developers never worked on the
UNIX product. And the NT product is not and never has been a simple port from
UNIX. How could it be when the underlying
operating systems are so different? So a lot of the detail differences reflect
what two different development groups thought
were important and what they didn't. Now the two groups, still distinct, are
united under one manager. So code convergence
is happening, but it is slow, because it still reflects those differences. As
I have said many times on this list, if you
have particular concerns about the product direction, about what features need
to go where, then you need to put them in a
note and send it netview@tivoli.com. That's how you influence development. I
have no direct influence myself.
As for which version should a customer choose, I am sure the answer is that he
has to look at the various features and take
his choice. There is no single, best fit.
James Shanks
Tivoli (NetView for UNIX) L3 Support
Mark van Kerkwyk <kerkwyk@COMTECH.COM.AU> on 09/13/99 05:03:31 PM
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 your answer.
I must say that I am a little confused about the NT/UNIX strategy, our
customers put in UNIX builds of Netview because there was more functionality, in
particular, NT having no rules editing capability make it useless and it doesn't
make sense to go and buy a UNIX Netview server just for generating rules and
then have another NT box running the rules.
Is there any reason why NT has more functionality in some cases but still
missing some of the major functions such as full rules editing etc capabilities.
All of my customers really want nvsniffer to do port status checking and are
confused as to why after investing in UNIX hardware etc, they must now put an
extra NT machine to perform the function of port status checking.
For those customers who don't run any rules, I have some who are effectively not
using Netview anymore in their environment and putting in What's Up Gold running
on Windows 95 as it does port status checking, provides % uptime and has a
better alerting mechanism, ann all for under 1K.
Mark
James Shanks <James_Shanks@TIVOLI.COM> on 13/09/99 22:46:25
Please respond to Discussion of IBM NetView and POLYCENTER Manager on NetView
<NV-L@UCSBVM.ucsb.edu>
To: NV-L@UCSBVM.ucsb.edu
cc:
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.
|