IBM Support

The alt_root_vg bundle option does not install new base filesets

White Papers


Abstract

If new software or bundles are introduced in the VIOS fix package being installed, they are ignored by alt_root_vg command.
The update will appear to be complete, even though the new base filesets were not installed.

Content

How alt_root_vg Works
The alt_root_vg command allows you to copy the current VIOS root volume group to an alternative disk and to update the operating system to the next fix pack level, without taking the VIOS down for an extended period and mitigating outage risk.
Cloning the running rootvg, allows you to create a backup copy of the root volume group. This copy can be modified by installing additional updates. One scenario might be to clone a 3.1.0.00 system, and then install updates to bring the cloned rootvg to a higher version, such as 3.1.3.21.  This would update the system while it was still running. Rebooting from the new rootvg would bring the level of the running system to 3.1.3.21. If you face a problem with this level, changing the bootlist back to the 3.1.0.00 disk and rebooting would bring the system back to 3.1.0.00. Other scenarios would include cloning the rootvg and applying individual fixes, rebooting the system and testing those fixes, and rebooting back to the original rootvg if you face a problem.
At the end of the installation, a volume group, altinst_rootvg, is left on the target disks in the varied off state as a placeholder.
After rebooting from the new alternative disk, the former rootvg volume group is displayed in a lspv listing as old_rootvg, and it includes all disks in the original rootvg. This former rootvg volume group is set to not vary-on at reboot.
If a return to the original rootvg is necessary, the bootlist command is used to reboot from the original rootvg.
How to Update VIOS Using alt_root_vg
When using alt_root_vg command to update the VIOS rootvg clone disk, use the "-bundle update_all -location /PATH ..." option to update all the currently installed software to the latest level that is available on the specified /PATH.
IMPORTANT:  The update_all option updates only the currently installed software and does not install new software or bundles as noted in alt_root_vg command:
image-20221117121638-1
Therefore, after booting from the rootvg clone, an "updateios" command needs to be run to install any new software.
NOTE:  Not all VIO Server updates include new base filesets.  There is no track of which VIOS fix packages include new software. Therefore, updateios must be run after updating the VIOS using alt_root_vg command.
The "alt_root_vg -bundle update_all ..." option is designed to only update currently installed software on the rootvg clone disk.
If a new base fileset is included in the update, and it is not a prerequisite of currently installed software, it will be ignored.
There will be no error reported since there was no error related to the ignored fileset.

Running the "updateios -install ..." installs any new base filesets included in the VIOS update.  This command might report no filesets to be installed:
"0 Total to be installed"

It is more common that there might be a few filesets to be installed. If there are, they will be listed on the "0 Total to be installed" entry.  For example:

FILESET STATISTICS
------------------
1111 Selected to be installed, of which:
5 Passed pre-installation verification
1006 Already installed
----
5 Total to be installed

The time needed to install the few filesets will be short compared to the full VIO Server update.
This allows a short maintenance window to be scheduled for the "updateios -install ..." to be run.

Sample Command
 
$ alt_root_vg -bundle update_all -location /home/padmin/update_files -target hdisk1

After alt_root_vg completes and the clone is booted, it will report the new VIOS version. It will look like the VIOS is complete.

A "lppchk -v" will run clean (no output).  No filesets are "broken" or missing prereqs.
# lppchk -v

The only method to know if new base filesets were included in the update is to run the "updateios -install ..." on the cloned rootvg.

1) Boot from the cloned rootvg disk.
2) Run "ioslevel" to confirm the update was applied.  Output should return the new VIOS level.
3) Run "updateios -install ..." to install the new base filesets that might be included in the VIOS fix package installed.
     $ updateios -install -dev /home/padmin/update_files -accept
4) Pay close attention to the output from updateios in item 3) to determine if new software was installed and whether or not another reboot is required.

[{"Type":"MASTER","Line of Business":{"code":"LOB57","label":"Power"},"Business Unit":{"code":"BU058","label":"IBM Infrastructure w\/TPS"},"Product":{"code":"SSPHKW","label":"PowerVM Virtual I\/O Server"},"ARM Category":[{"code":"a8m50000000L0OZAA0","label":"PowerVM VIOS-\u003EVIOS Update-\u003Ealt_root_vg updates"}],"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"3.1.1;3.1.2;3.1.3"}]

Document Information

Modified date:
17 November 2022

UID

isg3T7000733

Page Feedback