A few additions/corrections:
a) Multiple event-windows can be started (if we're talking about the
tess event-viewer)... on NT.
b) Traps/events do goto a DB on NT, but you can also switch-on the
trapd.log if you want (check a check-box).
c) The NT version has an automatic-restart for daemons (I don't know
about the UNIX version).
d) But... I really miss X-windows, and I hope the web-interface in
the next release helps minimize the need for remote-access.
e) I'll 2nd (or 3rd) the wish that they support Perl instead of TCL.
f) You can comfortably manage 5000 nodes on NT (default polling
settings) on a beefy $2000 workstation/PC... I don't know what
the upper limits are for either though.
From: Chris Cowan [mailto:chris.cowan@2ND-WAVE.COM]
Sent: Saturday, September 11, 1999 10:45 AM
Subject: Re: UNIX vs. NT functionality -- NetView 5.1.2 level
James Shanks wrote:
> This is a moving target but here goes what I know. The size of the
> can support is limited basically by the size of the machine you can have,
> UNIX boxes can be made bigger and more powerful. So generally, NT
> manage smaller networks. But here are some real differences you may want
> need to check out.
> Discovery differences
> seed file processing is different
NT netmon supports spray pinging. Discovery works differently on the
You can also manually force discovery of a subnet on NT.
> nvsniffer has more function on NT
> Ruleset differences
> no ruleset editor on NT
> nvcord runs rulesets only to filter the display
> actions and paging cannot be done from NT ruleset
> in-line actions cannot run windows apps on NT
> Trap processing differences
> no internal TEC adapter on NT
> UNIX TEC adapter does not provide a "secure" version which uses
> trap forwarding is handled by a separate daemon (trapfrwd) on NT
> traps forwarded only by UDP not TCP on NT
> no multiple event windows on NT
> events stored in database on NT so no need for Event History function
> fewer daemons on NT (no pmd, orsd, ovesmd, ovelmd, ovactiond,
> no security function on NT
> NT version does not install Tivoli framework or use it
> NT supports WEBM and Wake-on-Lan
> no gtmd or xxmap support on NT
> web clients are different
> NT GUI has availability info
> NT offers attended MLM function
No capability to control or configure MLMs from NT Manager (No APM or
(Actually, not totally true. You could always configure the MLM from
the MIB Browser)
> More third-party apps are available on UNIX
> Many third-party apps on NT do not integrate with NetView but run
To be honest, some of the third party apps on UNIX are headed in this
direction too. (e.g. CiscoWorks)
- Property lists on NT
- NT has the explorer (which is much easier to use than the maps or even
- Tcl integration (although I personally wish they had uses perl!).
Can be used within properties, nvsniffer, and reporting sections.
> If anyone else cares to contribute to this, I will keep a running list the
> time someone asks. Maybe that way we can construct the document that
> seems to want
Great idea. Thanks.
Well I'm speaking only from 5.1.1 experience, so perhaps some of my
bullets are no longer correct.
BTW, I'm a self admitted UNIX bigot and I wish a few of the newer
features from NT would be integrated into the UNIX version.
On the wishlist:
- A port of Netview 5.1.x on Linux (preferably RH6.0)
- If not that, at least the MLM functionality!!