| T.R | Title | User | Personal
Name | Date | Lines |
|---|
| 80.1 | HUBwatch for Windows and non-DEC equipment | EMDS::SEAVER | LENAC Net Mgnt Mktg 223-4573 | Mon Nov 30 1992 22:27 | 5 |
| HUBwatch for Windows can read any MIB. See
EMDS::MANAGEMENT:WINDOWS_SETUP.TXT and try it yourself. There is a MIB
display secton and MIB walks of the extensions are also possible.
Graphical displays of other devices are NOT supported.
|
| 80.2 | V1.0 has a MIB Browser, but not a Compiler | MEMIT::FORREST | | Wed Dec 16 1992 12:51 | 10 |
|
To add some clarification, HUBwatch for Windows includes a MIB
Browser, but it does not include a MIB Compiler. The difference
is that with only a MIB Browser, you need a paper copy of the
MIB in front of you to make any sense of it. A MIB Compiler would
add the MIB to the database of understood objects.
I'm guessing that Version 2.0, next summer, would have a Compiler.
jack
|
| 80.3 | More questions. | CGOS01::DMARLOWE | dsk dsk dsk (tsk tsk tsk) | Tue Apr 27 1993 15:59 | 7 |
| I didn't figure you'd get any graphics with 3rd party devices but
what could HUBWATCH display of such a device? How much management
could be done this way? What would it look like under WINDOWS?
How would this work with HUBWATCH for VMS?
dave
|
| 80.4 | HUBwatch is an element manager | EMDS::SEAVER | Bill Seaver, HUBwatch Mktg | Thu May 27 1993 23:30 | 17 |
| HUBwatch for VMS and HUBwatch for ULTRIX are element mangers. They are
only designed to manage DEChubs. They do not even have a map function,
thus they currently cannot manage anything other than DEChubs. To do
that you need to layer them on top of a Network Management System (NMS)
such as POLYCENTER. POLYCENTER will manage other devices as an icon
and also will show you SNMP variables associated with other devices.
If the other device is something that POLYCENTER has an element manager
for, you can get even more management. Is you substitute another NMS
for POLYCENTER in the section above, you will obviously get the ability
to launch other element mangers.
As to HUBwatch for Windows, the current version includes a NMS that can
give icons of SNMP devices (in fact anything it can PING) and also SNMP
MIB data (including a MIB walk feature). By December, Windows will be
just like the others (an element manger) but we expect it will be
launchable from HP OpenView and thus will have the option of adding
other element mangers to manage other devices.
|
| 80.5 | MIB Complier for HUBwatch 2.0 ?? | HGOVC::GUPTA | | Fri Jul 23 1993 07:23 | 25 |
| Ref .2:
Will HUBwatch for Windows V2.0 have MIB compiler ? Any latest info ?
One of my customer is asking "What if I decide to buy some third-party
devices in future ? How will I manage them ?"
I have been told that in case MIB compiler is available, we can manage
ANY third party device. IF IT IS TRUE, IS IT SAFE TO TELL THE CUSTOMER
"WITH HUBWATCH FOR WINDOWS V2.0 (DEC 1993 ??), WE WILL MANAGE ANY
THIRD-PARTY DEVICE" ?
What is the current situation with HUBwatch for windows ? Is it safe to
say "Any bridge with RFC 1286 and Repeater with RFC 1368 is manageable
by HUBwatch for Windows V1.0". Any information on bridges/repeaters
which implement these RFCs ? In that case, I can tell these
bridges/repeaters to the customer and sound more convincing (I need to
do a lot of selling to this customer and Network Management can help me
make the sale !!).
Thanks a lot for your attention.
Regards,
Surender
|
| 80.6 | MIB compiler and other features optional with HUBwatch for Windows 2.0 | NAC::FORREST | | Mon Jul 26 1993 19:02 | 32 |
|
> Will HUBwatch for Windows V2.0 have MIB compiler ? Any latest info ?
We plan to move to a model with V2.0 that is similar to the VMS and ULTRIX
model. HUBwatch 2.0 will run standalone or it can be launched from a fully
featured Windows-based NMS. The MIB compiler would come with the optional
NMS.
> I have been told that in case MIB compiler is available, we can manage
> ANY third party device. IF IT IS TRUE, IS IT SAFE TO TELL THE CUSTOMER
> "WITH HUBWATCH FOR WINDOWS V2.0 (DEC 1993 ??), WE WILL MANAGE ANY
> THIRD-PARTY DEVICE" ?
If the customer sufficently understands SNMP and MIBs, he can probably
manage most devices. There are some devices, which expect some objects
to be set simultaneously, and this is not always obvious.
> What is the current situation with HUBwatch for windows ? Is it safe to
> say "Any bridge with RFC 1286 and Repeater with RFC 1368 is manageable
> by HUBwatch for Windows V1.0"
I think it safe to say that HUBwatch for Windows V1.0 includes support for
those MIBs. I can't vouch for interoperability, since we haven't done much
testing.
> Any information on bridges/repeaters which implement these RFCs ?
No, but you might try to find it in one of Ed Mier's reviews in Communications
Week. If I find something, I'll try to post it here.
|