| > How about V4.0 or later? Any plans at all in this regard?
Probably not. It's a question of preventing overlapping functions.
HUBwatch is supposed to be the network management interface for the
DEChubs, GIGAswitch, and other NIPG products.
POLYCENTER NetView is supposed to be the enterprise network management
framework, which you use to control and map your whole network.
Frankly, it's hard enough for us to keep up with the products we need to
support and the applications specific to those products.
soapbox time: Once upon a time in a company many years ago there were
many groups who did pretty much the same kinds of things
in competetion with each other. There were several groups
making big computers, several groups making workstations,
and two groups making bridges and repeaters. Lo, Wall
Street and its customers looked at this company and said
"We don't like you anymore." So, the king and queen of
this company told all their princes and princesses to cut
the duplication or find work in another realm.
Moral: We don't want to compete with NetView.
But don't quote me on that. :-)
Tom Hood
HUBwatch
|
|
Our value added with HUBwatch is offering users an easier way to
manage DEChubs, not in creating a better mapping algorithm. Thus
our strategy is to launch HUBwatch from the leading network
management platforms, such as NetView, OpenView, etc.
You should begin seeing this capability of HUBwatch with V3.1.
We hope to support several platforms before the end of 1994.
jack
|