Four things I think you should know before you try this:
- The documentation for the update can be found here: http://www-01.ibm.com/support/docview.wss?uid=hpc1vios117f5701
- I updated three of my Virtual I/O Servers to 188.8.131.52 from 184.108.40.206 over the weekend. I started these late on Friday night with the "no reboot" options and they finished about the same time on Sunday afternoon i.e. 48 hours.
- The Release Manager downloads the update directly to the VIOS /opt/VIOS/update/VIOS and sub directory for the release name and this takes over two hours - good if you are not wanting to impact performance but maddening if you are waiting. After the 48 hours it leaves the files on the VIOS so it has permanently used up 3.5 GB of disk space on every VIOS. Being a NFS fan, I can't help thinking that NFS could move the data in a second.
- Also at the moment the Systems Director Release Manager is unaware of the two fixes so you have to manually install them ... at which point I think you might as well manually install the VIOS 220.127.116.11 update in the first place, which takes about 75 minutes over NFS, then a reboot and each fixes take a minute or two plus a reboot.
For your information, we have a:
- VIOS 18.104.22.168 is also known as FP26,
- VIOS new install media from ESS is available,
- There is a Service Pack 1 (SP1)
- FixCentral downloadable update to can FP26 include SP1,
- There are two fixes IV32091 and IV31624 that look to me as very important.
I will update this post when I know this is fixed and re-Tweet via mr_nmon
Any one remember the "Bill stickers will be prosecuted" campaign? It turned out Bill was innocent!
Well it looks like this is a problem with the valid VIOS updateios command that hangs. So System Director is innocent.
It is raised as a bug and being worked on.
I hope this helps you avoid these couple of problems, thanks, Nigel Griffiths