| Boy do you have a mess...
No I don't believe that going directly to 3.1 will work correctly. If it does
it's by accident since this has not been tested here. I have just sent mail
to someone in mfg to check and see what type of module you have. I can't
tell from the serial number but they should be able to tell me.
>> <<< Note 1248.0 by HITEKS::DOTY >>>
>> -< Upgrade 2.0 to 3.1 didn't work. >-
>>
>> Last week I attempted to "upgrade" the firware on an HSJ40 from 2.0J to
>> 3.1J. This was the first f/w update that the customer had received
>> after a long battle to get registered/on contract with the firmware.
>>
>> We took the system down, set nopath, etc. then powered off the
>> controller, switched the f/w and rebooted. Everything looked okay.
>> All units, devices, etc. appeared normal. Enabled both paths okay.
>> Attempted to boot the system. No device found. Vax 7710. Sho device
>> returns no devices found on the CI controller. Put 2.0j back and
>> rebooted system okay. All devices found.
>> POST MORTUM
>> A review of the firmware release notes shows that the HARDWARE
>> requirements are HSJ40-bx and HSJ40-cx.
>> How does one find out what flavor I have without removing the
>> module to check part numbers? Anything in the SHOW
>> This_controller display? Serial number is ZG41605053 if that
>> will give anyone an idea of which controller it is.
>> Should I have done a "rolling" upgrade? ed 2.0 -> 2.5 -> 2.7
>> -> 3.0 -> 3.1 or any veriation?
Rolling upgrade will work but it may be a lot of work. See below
>> If I do have the -ax flavor, what is the highest version of
>> f/w supported? What is the Digital "do the right thing"
>> stand on replacing the the HSJ40 with the later -bx/-cx if
>> necessary?
Highest rev that I know of that supports AX flavors is V2.5. I believe that
there was some sort of upgrade incentive a while back but I don't know what
is currently available. This was especially true with HSZ's.
>> All drives are RZ28-VA with firmware code D41C being reported.
>> Minimum revision per the release notes is 435E. How is this
>> translated? 41C is greater than 435, but what does the
>> D and E on opposite ends mean? I do plan to upgrade the drive
>> F/W anyway.
I believe these are hex numbers and therefore 41C is lower than 435E in
any case it would be better to be at a higher rev level if you can get the
microcode.
>> Any idea why the HSJ40 appeared to see all containers, units,
>> stripesets okay but the system sees no drives at all? CIXCD?
>> Release notes says it's supported.
If you have gone from V2.0 to V3.1 I have a pretty good idea. The layout of
NVMEM has been changed dramatically between V2 and V3. What you could do is
carefully printout all the configuration information you have with V2.0. Then
startup V3.1 and at the CLI prompt type set this initial_configuration. Then
you get the priviledge of typing the configuration back in ;-.]..... This is
assuming you have a BX or CX controller. I don't know what will happen with
an AX controller.
|