TL Upgrades via multibos
John.Wright 270004XKSU Comments (4) Visits (6076)
This is a subject that has been covered extensively elsewhere but I thought I’d share my recent experience as it did vary slightly. Chris Gibson (@cgibbo) put together an excellent Powerpoint presentation (with no terrible slide transitions) which you can find here.
A customer recently asked me “what do you think of multibos?”. I had to admit it was something I didn’t had a great deal of experience in. A quick look through Google and we were ready to try it out on my test environment.
In this scenario I’ll be updating from 7100-00-02-1041 to 7100-01-00-0000.
Preview creation of multibos environment
# multibos -Xsp
Create multibos environment
# multibos -Xs
Connect to multibos environment
# multibos -S
Check version of OS
MULTIBOS># oslevel –s
Disconnect from multibos environment
Mount NFS exported filesets with which to upgrade the new environment
# mount serv
Preview update of multibos environment
# multibos -Xacp -l /mnt
Update multibos environment
# multibos -Xac -l /mnt
But here we encountered a problem:
installp: * * * A T T E N T I O N ! ! !
Log file is /etc
The two words we all hate to see; FAILURE. Research revealed that this could be down to APAR IV03737. Since I was using AIX 7.1, I couldn’t downgrade my version of bos.rte.bosinst. or at least, I didn’t want to. Clearly this was the package we needed to focus on.
The media we were proposing to use to move the multibos environment to 7100-01-00-0000 would contain the latest version of bos.rte.bosinst. Using this, we upgraded bos.rte.bosinst. This reminded me of the Live Upgrade packages in Solaris. If you were upgrading Solaris 9 to Solaris 10, you had to have the Solaris 10 version of the Live Upgrade packages. So to fix this we selected the following files from the lpp source and updated them.
With those packages upgraded. You’ll want to blow away the old multibos and start afresh.
Remove the old multibos environment
# multibos -R
Create multibos environment
# multibos –Xs
Update the new environment whilst you’re travelling from the train station to your house:
# nohup multibos -Xac -l /mnt &
# umount /mnt
# bootlist -m normal -ov
Verify the bootlist and ensure that the BLV is set to the standby BOS (bos_hd5).
Check the correct BLV. Compare the output from bootlist with “Welcome to AIX” banner.
Reboot the system now with the “shutdown –Fr” command. After the reboot, confirm the TL level via “oslevel –r”. Verify which BLV the system booted from with the “bootinfo –v” command.
Multibos LVs and file systems are now open and mounted. The original file systems are renamed with a bos_ prefix but their original LV names are preserved.
If you need to back out of the update and return to the previous TL, all that's required is to boot the previous (“original”) BOS instance. Set the bootlist and verify that the BLV is set to the previous BOS instance (hd5).
# bootlist -m normal hdisk0 blv=hd5 hdisk0 blv=bos_hd5
# bootlist -m normal -o