| T.R | Title | User | Personal
Name | Date | Lines |
|---|
| 4319.1 | | NETCAD::MILLBRANDT | answer mam | Fri Mar 28 1997 13:35 | 7 |
| > DEChub 900MS has been updated. Current firmware is running.
Do you mean the hub did upgrade to V5.0, but the Flash Loader
messages are weird, or do you mean the hub didn't upgrade, and
the firmware you refer to is V4.2 or whatever you had been running?
Dotsie
|
| 4319.2 | Firmware upgrade completes | CSC32::R_BUCK | Authenticated and assimilated | Fri Mar 28 1997 15:27 | 15 |
| The upgrade of firmware has completed successfully and the DEChub is
indeed running V5.0 firmware. The Flash Loader utility is confused.
Have a log file that shows the sequence of messages. Recall doing
multiple upgrades and downgrades with various filed test versions of
firmware and never encountered a problem. The firmware and Flash
loader in this case came directly from the clearVISN V1.1a release.
Looking like some bad things happened when the final kit was put
together. This problem, missing help file(s), firmware upgrade DOES
reset the DEChub 900MS to Factory, cannot manage some DECserver and/or
90 series modules... Am working hard to qualify what might be broken
and get the proper elevations done ASAP.
Randall Buck
MCS - Network Support
|
| 4319.3 | More testing... Different results | CSC32::R_BUCK | Authenticated and assimilated | Fri Mar 28 1997 21:35 | 29 |
| Been doing some more testing to try and figure out what the heck is
going on. Looks like the "loop" scenario is specific to doing a V5.0.0
load to a hub that is already running V5.0.0 Other side issues may be
involved with the customer problem, (and my attempts to re-create the
situation).
Have run the following test a couple of times:
DECHub 900MS running V3.1.0
Use Flash Loader to upgrade to V5.0.0
IP setting for hub are cleared by the upgrade
Flash loader can no longer talk to the hub. Eventually times out.
So, the sentence in the version 5.0 firmware release notes: "When you
update your DEChub 900 MultiSwitch to version 5.x from version 3.0 or
higher, all nonvolatile data stored in the Hub Manager is retained."
would seem to be in error. My observation was that all LAN
Interconnect information survived the firmware upgrade, but the IP
setting for the Hub Manager did not.
Currently testing a 4.2.0 --> 5.0.0 upgrade. Hope to have a reasonable
matrix of what happens with different versions when I am done. Good
news is that the "loop" appears to be specific to an operation that
really should not be performed. Bad news is that customers may try
updating a hub remotely when they have no way to get to the console and
will loose managment capability until the IP settings can be restored.
Randall Buck
MCS - Network Support
|
| 4319.4 | | NETCAD::MILLBRANDT | answer mam | Fri Mar 28 1997 22:49 | 21 |
| Interesting.
I was able to duplicate the vanishing IP address on a
V3.1 -> V5.0 upgrade, despite the error log assuring me
that settings were retained. (I wouldn't trust the
LAN Interconnect settings you saw preserved until we
understand more about what went wrong.) Will look into
it more next week.
WORKAROUND: Upgrade from V3.x to any V4.x, then
to V5.x.
The V5.0 -> V5.0 upgrade _does_ retain settings.
You may have some other problem going on (bad LAN
Interconnect left over from earlier upgrade?).
Check error log.
Dotsie
|
| 4319.5 | Also saw it | PTOJJD::DANZAK | | Sat Mar 29 1997 11:09 | 6 |
| I've experienced similar problems upgrading V2-->V4 or V3-->V4.2 etc.
The hub totally looses configuration. In some cases, i.e. V2-->V4 the
hub totally looses all firmware and needs to be reloaded via serial
port. (i.e. sent back to LKG etc.)
|
| 4319.6 | My summary | CSC32::R_BUCK | Authenticated and assimilated | Mon Mar 31 1997 19:08 | 20 |
| Consistent with V3.x --> V5.x loosing IP settings. Just looking at the
console menu etc., I see that V3.x firmware did not have support for
subnet mask. Seem to recall the old V3.x --> V4.x upgrades had
problems in this area also.
LAN Interconnect looks to be ok for all upgrades.
My 2 cents worth; Need to raise a Yellow flag letting customers know
that a V3.x to V5.x upgrade will remove all IP setting. This in turn
makes Flash Loader look like it does not complete.
As for the problem with V5.x --> V5.x, this is really kind of obscure
and in one sense not a real problem. The firmware does get loaded, and
the DEChub 900MS starts running it. Only Flash Loader seems to beleive
it has to send/resend the firmware again. Am trying to capture a
network trace to see if I can figure out what response from the hub
make Flash Loader believe it needs to send the file again.
Randall Buck
MCS - Network Support
|