[Search for users]
[Overall Top Noters]
[List of all Conferences]
[Download this site]
Title: | DEChub/HUBwatch/PROBEwatch CONFERENCE |
Notice: | Firmware -2, Doc -3, Power -4, HW kits -5, firm load -6&7 |
Moderator: | NETCAD::COLELLA DT |
|
Created: | Wed Nov 13 1991 |
Last Modified: | Fri Jun 06 1997 |
Last Successful Update: | Fri Jun 06 1997 |
Number of topics: | 4455 |
Total number of notes: | 16761 |
1009.0. "DA90 V1.1 and DH900?" by WARABI::CHIUANDREW () Thu May 19 1994 22:05
Hi,
I 've just upgraded DA90 to V2.1.3 which is mounted in DH900. In the
DH900, there are DB90 (V3.1), DS900TM (with an IP address), and 3
BRouter90s (with IP address setup). When we start HUBwatch for OpenVMS
V2.0.1, the DA90 said it is mounted on a 'DH90'. That's why we have
DH90 display instead of DH900. Is it a limitation on DA90 V2.1.3?
So we downgraded the DA90 to V1.1, via the console we specific the
hub type is DH900, then when we re-start HUBwatch for OpenVMS, we can
see the DH900 backplane display. With DA90 V1.1, we can only manage
upto 8 single hubs, but customer have 13 hubs (local and remote),
have someone try to manage DH90 modules via DA90 V2.1.3 in DH900?
DH900 - ROM V1.1.6 and HubManager V2.2.1 (NO IBM and OBM had been setup)
DA90 V1.1.2
DB90 V3.1 (in DH900 and in remote DH90s)
Secondly, in DH900 manual, if it is managed via DA90, then DH900
modules must be configured and used as standalone, does it still apply
for HUBwatch for OpenVMS V3.0?
Thanks and regards,
Andrew Chiu - NIS Sydney
T.R | Title | User | Personal Name | Date | Lines |
---|
1009.1 | Some answers | ROGER::GAUDET | Because the Earth is 2/3 water | Fri May 20 1994 10:54 | 21 |
| Andrew, please read through the DECagent 90 V2.1 release notes. You will find
that most of the things you are seeing are documented there. I will summarize.
V2.2.1 of the DEChub 900 hub manager firmware will not allow the DECagent 90 to
be the hub master. However, if you deny the hub manager an IP address, the
DECagent can manage the devices in the hub through the DECbridge 90. Remote hub
management should work as advertised.
There is a trick you can play to get the DECagent to discover that it is in a
DEChub 900. Install the DECagent in slot 1 through 6. Do not install it in
slot 7 or 8. In this configuration, the DECagent will assume it is in a DEChub
900. Once hub manager V3.0 is available, the DECagent will be able to determine
that it is in a DEChub 900 even if it is installed in slot 7 or 8.
V2.1.3 of the DECagent will allow you to manage up to 16 communities or 64
modules.
The DECagent 90 does not manage any DH900 modules, so yes you must continue to
manage those modules as standalone with HUBwatch V3.0.
...Roger...
|