| T.R | Title | User | Personal
Name | Date | Lines |
|---|
| 531.1 | It doesn't matter where your device are | SLINK::HOOD | I'd rather be surfing | Tue Nov 30 1993 19:29 | 6 |
| HUBwatch will happily manage any of your brouters anywhere on your IP network.
If you can get to your remote brouters via an IP address, HUBwatch can talk
SNMP to them.
Tom Hood
HUBwatch brouters
|
| 531.2 | | KCBBQ::HELTON | | Wed Dec 01 1993 12:24 | 3 |
| Thanks for the explaination
Gary
|
| 531.3 | | NWD002::KOPEC_ST | Squash:Racketball::Chess:Checkers | Mon Jan 03 1994 17:03 | 3 |
| Does Hubwatch FOR WINDOWS support this today, or only the VMS version?
Thx, Stan
|
| 531.4 | HUBwatch for Windows V2.0 | SLINK::HOOD | I'd rather be surfing | Mon Jan 03 1994 21:17 | 1 |
| HUBwatch for Windows V2.0 supports it.
|
| 531.5 | | NWD002::KOPEC_ST | Squash:Racketball::Chess:Checkers | Tue Jan 04 1994 14:22 | 7 |
| and HW for Windows V2.0 is expected to ship... when?
VTX SPD still lists V1.1 as the current Windows version.
Thx.
PS V2.0 also WILL allow mgt of the DH900 backplane as well I understand.
correct?
|
| 531.6 | HUBwatch windows 2.0 == HUBwatch openvms 2.0 | SLINK::HOOD | I'd rather be surfing | Tue Jan 04 1994 15:44 | 8 |
| If it's in HUBwatch for OpenVMS V2.0, it's in HUBwatch for Windows V2.0,
with some very minor exceptions. Except for the windows interface itself,
HUBwatch for Windows V2.0 is a *port* (ie: same source code) as the OpenVMS
version. So, it will do 900 backplane management, manage the 900 repeater
and terminal server, the brouter, etc.
Tom Hood
HUBwatch developement
|
| 531.7 | Manage Cisco as well? | BEJVC::LEUNGWINGKIN | | Wed Jan 05 1994 01:41 | 10 |
|
Hi,
Since DECbrouter 90 is basically using the same software code as
Cisco, can we take the assumption that we can also use Hubwatch
to manage them? Will there be any difference between Cisco MIB
and our DECbrouter MIB?
Thanks in advance.
|
| 531.8 | It *should* work. | SLINK::HOOD | I'd rather be surfing | Wed Jan 05 1994 13:31 | 20 |
| re: .7 (managing Cisco with HUBwatch)
I haven't tried it, but the DECbrouter MIBs I use in HUBwatch are Cisco MIBs,
so it should work. I'll try to track down a Cisco box today and give it a
try. I'll post the results here.
Be aware that most of the hardcore setup of the brouter is through
the Cisco command language that you have to do thru either a console
connection or by TELNET to the brouter. The HUBwatch GUI screens for
the brouter mainly do monitoring with some control (the MIB allows for
a lot of READs but very few WRITEs). And they will be identical for
both the V2.0 HUBwatch for OpenVMS and HUBwatch for Windows.
In HUBwatch for OpenVMS, you can push a button on the HUBwatch brouter
screen and get a DECterm which will automatically do a TELNET connection
to the brouter. In the Windows version (this is the only difference between
the versions) you have to manually setup a TELNET connection to the brouter
Tom Hood
HUBwatch
|
| 531.9 | But it *doesn't* work. | SLINK::HOOD | I'd rather be surfing | Wed Jan 05 1994 14:38 | 9 |
| It doesn't work. I'll try to add it to version 3.0.
The Cisco IGX returns 1.3.6.1.4.1.9.1.5 for its sysObjectID.
The DECbrouter returns 1.3.6.1.4.1.9.1.3
So, HUBwatch V2.0 says it's unknown.
Sorry. V3.0 of HUBwatch for OpenVMS is due in March.
The Windows version will be a month or two later.
|
| 531.10 | It's now in there. | SLINK::HOOD | I'd rather be surfing | Wed Jan 05 1994 21:59 | 7 |
| HUBwatch for Windows, V2.0, will recognize the Cisco IGS. It will think it
is a DECbrouter 90.
HUBwatch for OpenVMS, V3.0 will have the same ability.
Tom Hood
HUBwatch
|