| T.R | Title | User | Personal
Name | Date | Lines |
|---|
| 2792.1 | Give the hub some time before retrying | MXOC00::CSILVA | | Mon Sep 25 1995 22:12 | 19 |
|
I have seen a lot of times that error.
Normally occurs after a previous failed load.
When you upgrade the hub, the image is holded in a temporary storage
before is completely received by the agent. After that, the image is
verified and finally written to memory replacing the old image
(critical short period when a power fault can corrupt the firmware
resulting in a "brain-dead" hub).
If the download of the image it's interrupted, that temp storage
still holds the received portion of the image expecting the rest,
so, when a new attempt is made you receive that error.
Normally waiting no more than 10 minutes, gives enough to time for
the hub to assume that the load has to be aborted and give room
for a new image to be downloaded.
|
| 2792.2 | Okay now | SSSAXP::LEMONS | And we thank you for your support. | Mon Sep 25 1995 22:44 | 7 |
| Thanks for your thoughts. I waited much more than 10 minutes, and I
still couldn't use HUBloader to load the image. So, I used the OBM
port to reset (option 2) the hub. After that, HUBloader upgrade worked
just fine.
Thanks!
tl
|
| 2792.3 | | NETCAD::DOODY | Michael Doody | Tue Sep 26 1995 09:10 | 11 |
| What you are seeing is that the "landing pad" where images are
temporarily stored during downline load is marked as in use. Normally
the landing pad is freed when the load is complete; however when there
is an error in the loading process the landing pad can sometimes remain
locked. This problem can only be fixed by a Hub reset as you
discovered.
We are improving the way downline loads work in the next major release
(sometime after v4.1). This problem should go away.
-Mike
|
| 2792.4 | | CRONIC::LEMONS | And we thank you for your support. | Wed Sep 27 1995 23:21 | 5 |
| Mike
Thanks for the reply, and the hint of things to come!
tl
|
| 2792.5 | Check community string too... | PTOJJD::DANZAK | Pittsburgher � | Thu Sep 28 1995 07:00 | 3 |
| I think that I've also got that when the community string was wrong....
j
|