Since it has an external tape drive, it forced me to do it from V5R3
original install media (CDs). Then later, I used the GO SAVE '21' to
restore the Licensed Pgms, user profiles, config objects, etc... No
partitions.
Lane
-----Original Message-----
From: consult400-bounces@xxxxxxxxxxxx
[mailto:consult400-bounces@xxxxxxxxxxxx] On Behalf Of fwsoftware@xxxxxxx
Sent: Thursday, May 13, 2010 2:54 PM
To: consult400@xxxxxxxxxxxx
Subject: Re: [Consult400] Question about HyperVisor, Service Processor,
trying to move back in O/S level
Lane,
Did you try the install from original IBM cds -or- Go Save (save21)
tapes from V5R3?
How many partitions?
Regards,
Dave
-----Original Message-----
From: Requist, Lane <lrequist@xxxxxxxxxx>
To: consult400@xxxxxxxxxxxx
Sent: Tue, May 11, 2010 1:15 pm
Subject: [Consult400] Question about HyperVisor, Service Processor,
trying to move back in O/S level
Dear colleagues,
I am running on a model 9406-570, which was recently upgraded
rom V5R3 to V5R4, with absolutely no trouble. However, after about 2
onths of being at that O/S level, we were forced into the decision (for
arious reasons) to try to take the machine back to V5R3. I have done
uch 'scratch installs' in the past, simply by doing a Manual IPL from
he 'D' side, and reloading everything from a GO SAVE and/or original
BM media (eg. V5R3 CDs). When I attempted to do so in this case, I got
he results below. Note that this system uses Ops Console (direct) for
he console connection, and has never used HMC to our knowledge.
1) V5R3 LIC was reloaded from original V5R3 install CDs, after
aking option '2' to scratch all disk units.
) Upon taking the option to reload the Operating System, I
mmediately was given the option to add non-configured disk units into
he ASP.
) This ran for a while but finally halted with an error stating
hat it failed to reset a system IOP.
) I proceeded to bypass adding the drives, and continued with
e-loading user profiles, configuration objects, Lic Pgms, etc...
) Upon further attempts to add disk units to the ASP, got hardware
rrors on the units (see below).
) We had to attach a PC to the HMC2 port on the back, in order to
et into the Service Processor interface.
) Now we are unable to do a Manual IPL. Even though we have set
he value to 'Manual' in the Service Processor interface, and even
hough the front LED panel reads '01 M V=F
HMC=0 P
the machine simply will not power up in
anual mode. It always comes directly to the main LOGIN screen, and
herefore I am not able to get into DST. The errors indicate that there
s some kind of mismatch between the O/S level of the machine, and the
/S level of the HyperVisor. Or that the HMC is not giving correct
nformation to the HyperVisor, that sort of thing. When IPLing (and as
f late, all through the day), I am getting numerous hardware errors in
RKPRB and Service Tools on CMB07 and CMB06, but I still don't think it
s hardware. Below you will find some of the errors:
SRC B006 1302
RC B006 1304
RC B006 1308
RC B600 512D
RC B600 5120
RC B600 5275
RC 2844 B935 (message text: "Indicates that PHYP sent the FSP a bad
ize, modifier, or HMC index."
Again, the primary question seems to be: is it possible to do a
scratch install' from V5R4 back to V5R3 on a machine that has
yperVisor on it? I cannot help but thinking that all of the problems
re related to moving the system O/S back to V5R3, but the HyperVisor
nd Service processor are still at V5R4? And, why does the system think
hat I have HMC installed, when I do not?
Any input would be appreciated!
Lane Requist
ane Requist
arris Corporation
800 S. Meridian Blvd., Suite 300
nglewood, CO 80112
requist@xxxxxxxxxx
esk (303)476-4666
ell (303)588-9952
-
his is the Consulting on the iSeries / AS400 (Consult400) mailing list
o post a message email: Consult400@xxxxxxxxxxxx
o subscribe, unsubscribe, or change list options,
isit:
http://lists.midrange.com/mailman/listinfo/consult400
r email: Consult400-request@xxxxxxxxxxxx
efore posting, please take a moment to review the archives
t
http://archive.midrange.com/consult400.
As an Amazon Associate we earn from qualifying purchases.