[Search for users]
[Overall Top Noters]
[List of all Conferences]
[Download this site]
Title: | HSZ40 Product Conference |
|
Moderator: | SSDEVO::EDMONDS |
|
Created: | Mon Apr 11 1994 |
Last Modified: | Fri Jun 06 1997 |
Last Successful Update: | Fri Jun 06 1997 |
Number of topics: | 902 |
Total number of notes: | 3319 |
886.0. "Upgr. V2.7->V3.1 & SAVE_CONFIGURATION?" by UTRTSC::VISSER () Mon May 26 1997 16:09
Upgrading dual redundant HSZ40's, where SAVE_CONFIGURATION is used,
from HSOF V2.7Z to V3.0Z has been NOT free of any risk (as we
experienced) and strict steps had to be performed to make it a
success.
These steps were described in the HSZ40 HSOF V3.0Z release Notes.
HSZ40 HSOF V3.1Z Release Notes have a straight-forward procedure
(only step 12. should NOT say "repeat all previous steps for the 2nd
controller" but "repeat steps 5-11 for the 2nd controller").
Q1: Upgrade from HSOF V2.7Z to V3.1Z seems allowed, as suggested on
page 19 of those release notes.
Is it VALID to skip V3.0Z and go from V2.7 to V3.1?
Q2: Does V3.1Z have IMPROVEMENTS, where an upgrade from V2.7Z Dual
Redundant controller WITH SAVE_CONFIGURATION on disks will NOT
cause problems during the upgrade (as may happen during
upgrading to V3.0Z when the proper procedure was not followed)?
Jan Visser.
T.R | Title | User | Personal Name | Date | Lines |
---|
886.1 | | SSDEVO::T_GONZALES | | Tue May 27 1997 10:41 | 2 |
| I think that same procedures and care should be taken when upgrading
to 3.1z also.
|