Upgrading to VIOS 184.108.40.206 - tips from my experience & some SSP commands
nagger 100000MRSJ Comments (4) Visits (15000)
Having just done this and getting questions on it from customers, I thought I should share a few notes:
1) The process is nicely documented and you need to follow the instructions. I recommend using the Release Notes as a check list as missing out a stop causes the next bit for complain or fail. Fortunately, the recovery is just doing the bit I missed.
2) Read the Release notes - even better print them out and cross them off as you go:
3) I thought the 220.127.116.11 to 18.104.22.168 update would be small (like a bug fix) but I download the files from FixCentral 8+ GB of files. That is roughly the size of the initial install, so quite a lot has been changed and it is lots of packages. Even a tiny one line update means a whole new package which can be a few BM in size.
4) For 22.214.171.124 there is a section in the Release Notes where you can run a "sum check" of the downloaded files to double check the download is complete using the file ck_sum.bff. I tried to follow the instructions but it completes the check with 722 errors. Now the good news, the errors seem to be an error!! Hopefully your milage will vary and you will not see this. They look like this:
CKSUM Failure on /mnt
What you are looking for is errors without the wacko 40 byte hexidecimal filenames that are not files which arepart of the update. The ones like the above can be ignored. Real errors will have typical VIOS/AIX package names. The script seems to be picking up extra data from the Sum Check file.
5) In about half the cases I found the final part of the updateios command hangs in about half the cases. I stops with the follwoing message:
installp: * * * A T T E N T I O N ! ! !
One of these I left overnight and it would not finish and the ps output showed it was repwaning a new process every second of so. As this is normally the very last thing that is output and the VIOS reported in another window that it was now VIOS 2.2.2 I Control-C-ed the updateios command and rebooted. It all worked fine.
6) Another "pet hate" of mine is that the Release Notes don't remind us to check for further fixes. Currently there are three fixes and reading the notes on them they all sound very important so make sure you download and install them.
You do this with the same updateios command (pointing to a different device for the fixes content). You can add all three fixes in one go and reboot. Also note you don't need to remove old fixes before the VIOS 126.96.36.199 update - those are sorted out automatically.
7) For VIOS that are part of a Shared Storage Pool - Find the link in the Release Note specifially for SSP
The VIOS 188.8.131.52 to 184.108.40.206.2 upgrade is not a major upgrade. Major upgrades mean you have to upgrade all the VIO Servers in turn and only the last VIOS upgrade actually does the upgrade to the cluster and adds the new features. You don't need to monitor and check for this 220.127.116.11 upgrade but I thought I would document the command here so I can find it next time :-) It is a very useful command for a summary of the Shared Storage Pool custer but if you don't try the -verbose flag you miss lots of useful information:
cluster -status -clustername galaxy -verbose -field node_name node_upgrade_status
Node Name: diam
Or if you want to see all the avaibale information
cluster -status -clustername galaxy -verbose
Then you get the following for each SSP cluster node
Node Name: purp
Another usful SSP commands to remember to remove your VIOS from the SSP cluster and add it again:
clstartstop -stop -n CLUSTER -m VIOSHOSTNAME clstartstop -start -n CLUSTER -m VIOSHOSTNAME
8) It was taking me about 5 minutes per VIOS of actual work but the the elpased time was well over an hour, so I was doing many of them concurrently. You will have to reboot the VIOS twice. So with
If I find out more later
I am worried that these problems are all down to me rushing the job or forgtting to do something in the right order.
Cheers, Nigel Griffiths