| 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 |
A customer has 9 DH900s, 7 connected via DB900MX bridges 2 connected
using DC900MX. They upgraded the DB900MX and the DC900MX along with
the DH900MS to to the latest frimware versions. Everything seems to
be working (system from any hub talk to system on any other hub) but
when they try to change community from hubwatch on the hub they
upgraded they get the following error:
Timed out waiting for set response from the hub the set may have
failed.
Is there a compatablity problem if the other hubs are running Hub
watch 3.0 with DC900MX running 1.2.3 that would cause this error.
They are also concerned that if they can't get to the hub with
hubwatch will they be able to use DECNDU to upgrade these hubs.
The only hubs that they can't talk to (get the above error) are
the 2 hubs that have the DC900MX, that is, these 2 hubs are connected
DC900MX, there is no DB900MX in ether of these 2 hubs.
Thanks in advance for any help
Rich Stewart
| T.R | Title | User | Personal Name | Date | Lines |
|---|---|---|---|---|---|
| 1875.1 | any ideas ??? | CSC32::R_STEWART | Rich Stewart - CSC/CS | Wed Jan 18 1995 00:08 | 1 |
| 1875.2 | A couple of ideas, and some questions | ROGER::GAUDET | Because the Earth is 2/3 water | Wed Jan 18 1995 10:45 | 31 |
Rich, I'm not sure I understand at what revisions your customer's devices are at now. You said that they upgraded to the latest firmware on all devices. That should mean the following: DH900MS V3.1.0 DB900MX v1.4.0 DC900MX V2.8.0 If these are not the firmware revisions currently in the devices, then they are not at the latest. That being said, I'm confused about the following: >> Is there a compatablity problem if the other hubs are running Hub >> watch 3.0 with DC900MX running 1.2.3 that would cause this error. What does this mean? As stated above, the latest DC900MX firmware is V2.8.0. Another question; what was the previous firmware revision of the DH900MS? Upgrading to V3.1.0 from V2.2.1 or earlier would result in a factory reset of the DH900MS, causing the previous configuration to be lost (including the community strings being reset to "public"). If the community strings were changed prior to the upgrade and had been entered into the HUBwatch Manage Table window, then you may get this error because HUBwatch will use the old community string to attempt to access the hub. Make sure the community strings in both the HUBwatch Manage Table window and in the Show Current Settings display of the hub setup port are the same. ...Roger... | |||||
| 1875.3 | Yes and Yes | CSC32::R_STEWART | Rich Stewart - CSC/CS | Wed Jan 25 1995 07:32 | 11 |
Well, the answer to the questions were, yes this is a compatibility
problem and yes DECndu+ was able to upgrade the DH900MS's and the
modules in them. I put the answer here just in case someone else
runs into a problem like this.
Thanks for the replies :)
Rich Stewart
| |||||