A VIOS fix pack was released on 10 September 2010.
Three points which jumped out from the page of the installation instructions:
- From now on, the VIO Server rootvg requires at least 30 GB. If you're mirroring your rootvg, note that's 30 GB of useable disk. Two LUNs of 15 GB wouldn't suffice, but one of 30 GB would. (Of course, if you're using LUNs you should have redundancy anyway, but if you're on local disk with software mirroring, you need the 30 GB for each disk).
- If you're using the File Backed Media Repositories (and you would have given up reading AIX Down Under long ago if you're not), you need to unload images first. That doesn't mean you remove the ISO images from the Virtual Media Library or the VM Library itself. It's just a matter of not having the images loaded onto the virtual optical devices. Check here for details.
- It is MANDATORY that you use the -install flag when running the updateios command to apply Fix Pack 24. Failure to use the -install flag will leave your VIO server in an unusable state.
Don't say I didn't warn you.
One VIOS at a ttime
If you have a dual VIOS setup with all your redundancy in place (MPIO, SEA failover and active memory sharing paging space) you should be able to do one VIO server at a time and keep your VIO clients up and running. If you've got a single VIO server (e.g. when using IVM instead of an HMC), or redundancy not quite where it should be, you'll have to take the hit of a scheduled outage.
Here's the link to the VIO Server Fix pack:
And even if you're not into reading the READMEs (or is the plural for that "READUS"?), I suggest you do it this time: http://www-01.ibm.com/support/docview.wss?rs=0&uid=isg400000259
I just built a new VIO Server using the installation ISO image which I'd downloaded from IBM Entitled Software Support
. I used NIM referring to this IBM technote
. I installed the VIO Server onto a single SAS disk which I will mirror to another disk later.
I then ran the installation of VIOS 184.108.40.206 Fix Pack 24 which took 1 hour 17 minutes, plus another couple of minutes for the reboot. Before I could do that, the command
Access to run command is not valid.
until I logged out and logged in again, then ran:
and was able to reboot without any issues.
Now it's time to change the padmin .profile for shell history and shell prompt. I'll call on my colleague, Mark Chandler's new aixplode blog
for that. Here's a link to that post on the padmin .profile: http://bit.ly/d7WpQU