K-Series to S-Series Differences

Fallback Considerations
Map: K-Series to S-Series Differences.
Note: Use our Feedback form to let us know of other fallback considerations that
you would like for us to add to this page.
Fallback procedures help you work with system limitations you might encounter when
installing software or falling back to your previous release version update (RVU).
Source for General Instructions
For general upgrade installation instructions and fallback alerts, see the Gxx.xx
Software Installation and Upgrade Guide for your current G-series RVU and the RVU
you might have to fall back to. This manual also provides a list of software product
revisions (SPRs) that you need to install to fall back from one G-series RVU to a
previous one.
Always Save the Configuration Database
The record format of the system configuration database changes with various RVUs.
To ensure system configuration integrity, always save the current system configuration
database before installing software or making any changes to your system
configuration.
Caution: Do not attempt a fallback without previously studying the in-depth
procedures provided for the RVUs involved. Falling back involves a thorough research
of all the fallback SPRs as well as the versions of your applications and configuration
files.
The following summary of fallback steps provides a general overview on what is
needed to fall back to a previous software RVU.
1 Use the DSM/SCM Target Interface to back out of the revision and install the
fallback SPRs.
2 Start the DSM/SCM client software and monitor the status of the backout
process. (Wait for backout completion before exiting DSM/SCM.)
3 Use the OSM Service Connection or the TSM Service Application to update your
service processor (SP) firmware to the previous firmware version.
(To fall back to either the G03.00 or the G05.00 RVU, use the multiple SP
firmware update to update to the previous version of the SP firmware.)
4 Run ZPHIRNM from the TACL prompt and specify the SYSnn you want to fall
back to.