Tek-Tips is the largest IT community on the Internet today!
Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!
-
Congratulations Chris Miller on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!
microcode level on an p570 ???
- Thread starter mikri
- Start date
Do you have an hmc?
If so:
Licensed Internal Code ( Navigation Window )
- Licensed Internal Code Updates ( Nav Window )
- Change Internal Code ( other window )
- Select your managed system
- View System Information
This should show the "microcode" on the p570. If you have an HMC, I believe the only way you can update this is through the HMC.
If so:
Licensed Internal Code ( Navigation Window )
- Licensed Internal Code Updates ( Nav Window )
- Change Internal Code ( other window )
- Select your managed system
- View System Information
This should show the "microcode" on the p570. If you have an HMC, I believe the only way you can update this is through the HMC.
- Thread starter
- #3
You can use the lsmcode command.
Example :
# lsmcode
DISPLAY MICROCODE LEVEL 802811
IBM,9117-570
The current permanent system firmware image is SF220_051
The current temporary system firmware image is SF220_051
The system is currently booted from the temporary firmware image.
Use Enter to continue.
Example :
# lsmcode
DISPLAY MICROCODE LEVEL 802811
IBM,9117-570
The current permanent system firmware image is SF220_051
The current temporary system firmware image is SF220_051
The system is currently booted from the temporary firmware image.
Use Enter to continue.
We are trying to update our microcode but we can't do it.
Error message : "The operation failed due to an internal code failure ACT01724"
The update operation is made from the hmc ("licensed internal Code Updates" option).
We are in relation with Ibm for this operation.
Error message : "The operation failed due to an internal code failure ACT01724"
The update operation is made from the hmc ("licensed internal Code Updates" option).
We are in relation with Ibm for this operation.
Funny... I went through the same thing. Did they tell you want the problem was? It took me three days, but finally they found an Internal memo that bailed me out. Support really has sucked this far on p5's. I guess they won't be creating a real fix until Mid March.
To fix this (atleast on my 520s)
1. I had to download the p5 and i5 microcode iso to a pc with a cd burner
2. Run the iso file, which will burn a cd with rpm files on it.
3. Put the cd into the hmc, browse to LIC updates and do a manufactoring equiptment specification upgrade ( instead of Change Internal Code) This will upgrade the SF220_051 to SF222_81.
I was told the problems was upgrade from SF220_51 to any thing higher than SF222_81. According to the rep I worked with, this was the easiest fix. It took about 1.25 hours to do the upgrade.
Just my 2 cents. Treat it as that.
To fix this (atleast on my 520s)
1. I had to download the p5 and i5 microcode iso to a pc with a cd burner
2. Run the iso file, which will burn a cd with rpm files on it.
3. Put the cd into the hmc, browse to LIC updates and do a manufactoring equiptment specification upgrade ( instead of Change Internal Code) This will upgrade the SF220_051 to SF222_81.
I was told the problems was upgrade from SF220_51 to any thing higher than SF222_81. According to the rep I worked with, this was the easiest fix. It took about 1.25 hours to do the upgrade.
Just my 2 cents. Treat it as that.
- Status
Similar threads
- Locked
- Question