This ifix contains new features and fixes which would ease the migration of VIOS from 2.2.6.32 or later to VIOS 3.1.* . IFIX Summary: Following are the list of features/fixes: 1. New force options to enable user to overwrite certain default parameters to proceed with the installation. Following are the usecases of overwriting those parameters: a. Allow user to trigger multiple VIOS upgrade parallely in a SSP Cluster environment b. Enables user to copy the specified files to the respective directories in the newly installed disk(s). c. Enables user to skip VIOS metadata restore configuration after installation process is completed and booted from newly installed disk(s). 2. New option to enable user to do VIOS metadata restore via viosupgrade. 3. New option to Enable user to specify a binary that has to be executed after successful VIOS metadata restore process. 4. New option to support manual reboot after the installation to complete the upgrade process 5. Fix for APAR IJ25453 - VIOSUPGRADE RESTORE UNABLE COMPLETE DUE TO -G FILE COPY FAILURE. Note:All the above features are applicable ,if you are installing the VIOS from VIOS itself ( VIOS-viosupgrade ). If you are installing the VIOS from NIM, only 1.a feature is applicable ( NIM - viosupgrade). viosupgrade File version: 1.58 IFIX Details: ============ IFIX Name: --------- VIOS - viosupgrade: viosupgVIO.200807.epkg.Z NIM - viosupgrade : viosupgNIM.200807.epkg.Z Steps to install the fix for installation of the VIOS from VIOS itself: ----------------------------------------------------------------------- 1. Download epackage " viosupgVIO.200807.epkg.Z" on the VIOS. 2. Run "emgr -e viosupgVIO.200807.epkg.Z" to install the ifix. To uninstall the fix run "emgr -r -L viosupgVIO" Note: No reboot is required. Steps to install the fix for installation of VIOS from NIM: ---------------------------------------------------------- 1. Download epackage "viosupgNIM.200807.epkg.Z" on nim. 2. Run "emgr -e viosupgNIM.200807.epkg.Z" to install the fix. To uninstall the fix run "emgr -r -L viosupgNIM" . Note: No reboot is required. Details of the new options: ========================= VIOS - viosupgrade: =================== Syntax: ------ viosupgrade -l -i image_file -a mksysb_install_disk [-c] [-g filename] [ -F options:... ] [-P post_install_binary ] [-u] <<<<<<<<<<<<<<<<<<<<<<<<<< viosupgrade -l -q viosupgrade -I ISOImage1:ISOImage2 -w directoryPath viosupgrade -o {restore} -A args=argument1... Flags: -l Specifies local Node Installation. -i Specifies image file for the alternate disk installation. -a Specifies alternate disk to install the provided image. -c Specify if the node is part of the cluster. -g Specifies the filename having the list of files to be copied to newly installed rootvg. -q Queries the status of VIOS restore operation after booting the VIOS with newly installed image. -I Specifies ISO image files to create ios_mksysb file. -w Specifies the directory path for creating new ios_mksysb file. -F Enables user to skip certain checks to do force installation. <<<<<<<<<<<<<<<<<<<<<<< Possible options are : skipclusterstate, skiprestore, forcecopy.<<<<<<<<<<<<<<<<<<<<<<< forcecopy is applicable only with -g option.<<<<<<<<<<<<<<<<<<<<<<< -u Specifies that the user needs to do manual reboot to activate the newly installed rootvg. <<<<<<<<<<<<<<<<<<<<<<< -o Specifies the type of non-install operation. Supported types: restore. <<<<<<<<<<<<<<<<<<<<<<< -A Enables user to specify arguments based on non-install operation type. <<<<<<<<<<<<<<<<<<<<<<< -P Enables user to specify postinstall script/binary to be executed post successful restore. <<<<<<<<<<<<<<<<<<<<<<< This option cannot be used with -F skiprestore option. Note : New options are highlighted with "<<<<<" 1. Option : "-F" ================= Description: Enables user to overwrite certain default parameters to proceed with the installation. Options that can be passed to are "skipclusterstate", "skiprestore", "forcecopy". a. "skipclusterstate" ------------------ Description : Enables user to skip the SSP cluster state check , so that the user can trigger viosupgrade installation on multiple VIOS nodes parallelly. This will show a warning message in the viosupgrade output to inform user that we are skipping the clusterstate check. Note: User should ensure that not all the SSP cluster nodes are down at the same time as this might bring the cluster completely down. Example : viosupgrade -l -i /mnt/ios_mksysb_3.1.1.20.img -a hdisk40:hdisk41:hdisk42:hdisk43 -F skipclusterstate -c Sample output: ####################################################################### Welcome to viosupgrade tool. Operation triggered for given node(s). Broadcast message from root@jaguar18.pok.stglabs.ibm.com (pts/0) at 09:49:01 ... WARNING!!! VIOS Upgrade operation is in progress. Kindly Refrain from making any configuration changes... Please wait for completion.. Upgrading from ioslevel '2.2.6.65' to '3.1.2.00'. WARNING: Forcing install with cluster state as 'DEGRADED'. Verifying whether the MPIO software(s) is installed on the VIOS. Verification of the MPIO software(s) is successful. Initiating VIOS configuration backup.. VIOS configuration backup successful. Initiating installation on alternate disk(s).. Installation on alternate disk(s) successful. Copying files to altinst_rootvg. Waking up altinst_rootvg successful. VIOS will be rebooted after '60' seconds to boot from the newly installed disk. Press contrl+c to terminate. VIOS metadata restore (viosbr -restore) will be automatically resumed after the reboot. VIOS may be rebooted once during this restore process. Refrain from making any changes to the VIOS virtual configurations during the restore process. You can verify the restore status using 'viosupgrade -l -q' command and resume your operation after the completion of the restore process. ####################################################################### b. "forcecopy" ----------- Description : Enables user to copy the specified files to the respective directories in the newly installed disk(s). Note: 1. This option is applicable only with -g. 2. -g option without “-F forcecopy” will copy the files to /home/padmin/backup_files folder in newvg. User has to explicitly copy the files to respective directories from there. Example : viosupgrade -l -i /mnt/ios_mksysb_3.1.1.20.img -a hdisk40:hdisk41:hdisk42:hdisk43 -F forcecopy -g /home/padmin/input_files c. "skiprestore" ------------- Description : Enables user to skip VIOS metadata restore configuration after installation process is completed and booted from newly installed disk(s). Note: 1. Details of the backup file will be displayed as part of the viosupgrade installation output. User can use this backupfile path while doing VIOS metadata restore manually. 2. User needs to run the following command manually “viosupgrade -o restore -A args=”” to restore the VIOS metadata. As part of this restore process, VIOS may be rebooted. 3. Alternatively, User can choose to restore using “viosbr -restore “ command. However, User has to manually reboot and re-run the restore process as per the need. Example : viosupgrade -l -i /mnt/ios_mksysb_3.1.1.20.img -a hdisk40:hdisk41:hdisk42:hdisk43 -F skiprestore -c Sample output ####################################################################### Welcome to viosupgrade tool. Operation triggered for given node(s). Broadcast message from root@ferrari10.pok.stglabs.ibm.com (pts/0) at 12:32:10 ... WARNING!!! VIOS Upgrade operation is in progress. Kindly Refrain from making any configuration changes... Please wait for completion.. Upgrading from ioslevel '2.2.6.65' to '3.1.2.00'. WARNING: Forcing install with cluster state as 'DEGRADED'. Verifying whether the MPIO software(s) is installed on the VIOS. Verification of the MPIO software(s) is successful. Initiating VIOS configuration backup.. VIOS configuration backup successful. Initiating installation on alternate disk(s).. Installation on alternate disk(s) successful. Copying files to altinst_rootvg. Waking up altinst_rootvg successful. It is the responsibility of the user to do manual restore using 'viosupgrade -o restore -A args=' after booting from the newly installed disk(s). Backup file is present in the path:'/home/padmin/cfgbackups/ferrari10_7209040.ferrari9_1011cluster.tar.gz' VIOS will be rebooted after '60' seconds to boot from the newly installed disk. Press contrl+c to terminate. ####################################################################### 2. Option: "-o" ============ restore: -------- Description : Specifies VIOS metadata restore through viosupgrade. -A args="" ------------------------------------ Description : This option enables user to do manual restore along with the combination of -o restore. args: User should choose options from “viosbr -restore” command. For more details on the options refer to “viosbr -restore” command usage. Note: 1. User can get backup file information to pass on to the arguments by executing “viosupgrade -l -q” on the new vg. 2. User can verify the status of restore, using “viosupgrade -l -q” command. 3. VIOS may be rebooted during the restore process. 4. At any given point of time, only one instance of viosupgrade restore process is allowed. Example : viosupgrade -o restore -A args="-file /home/padmin/cfgbackups/jaguar18_14942560.tar.gz" Sample output ####################################################################### Welcome to viosupgrade tool. Broadcast message from root@localhost (vty0) at 05:42:27 ... WARNING!!! VIOS Upgrade restore operation is in progress. Kindly Refrain from making any configuration changes... Please wait for completion.. Restore process completed. Please run 'viosupgrade -l -q' to know the status. ####################################################################### 3. Option: -P ========== Description : Enables user to specify a binary that has to be executed after successful VIOS metadata restore process. Note: 1. This is not allowed with -F skiprestore. 2. viosupgrade will execute the post install binary provided as is. It’s the user’s responsibility to ensure that any required checks are performed on the binary prior to viosupgrade execution. Example : viosupgrade -l -i /mnt/2024B_72V_ios_mksysb.img -a hdisk40:hdisk41:hdisk42:hdisk43 -P /home/padmin/post_install.sh 4. Option: "-u" =========== Description : Enables the user to manually reboot the VIOS to activate the newly installed volume group. Example : viosupgrade -l -i /mnt/ios_mksysb_3.1.1.20.img -a hdisk19:hdisk20:hdisk21 -u Sample Output ############################################################################ Welcome to viosupgrade tool. Operation triggered for given node(s). Broadcast message from root@ferrari10.pok.stglabs.ibm.com (pts/0) at 00:59:27 ... WARNING!!! VIOS Upgrade operation is in progress. Kindly Refrain from making any configuration changes... Please wait for completion.. Upgrading from ioslevel '2.2.6.65' to '3.1.1.22'. Verifying whether the MPIO software(s) is installed on the VIOS. Verification of the MPIO software(s) is successful. Initiating VIOS configuration backup.. VIOS configuration backup successful. Initiating installation on alternate disk(s).. Installation on alternate disk(s) successful. Copying files to altinst_rootvg. Waking up altinst_rootvg successful. Bootlist is set to newly installed disk(s). It is the user’s responsibility to ensure VIOS reboot to complete the restore process(Restore triggers automatically as part of next boot). New volume on /mnt/new_mksysb: Cluster size is 51200 bytes (100 blocks). The volume number is 1. The backup date is: Mon Aug 3 09:40:40 CDT 2020 Files are backed up by name. The user is padmin. The number of archived files is 76176. ############################################################################ NIM - viosupgrade: =================== Syntax: ------ viosupgrade -t bosinst -n hostname -m mksysbname -p spotname {-a RootVGCloneDisk: ... | -r RootVGInstallDisk: ...| -s} [-b BackupFileResource] [-c] [-e Resources: ...] [-F options:... ] [-v] <<<<<<<<<<<<<<<<<<<<<<<<<<<<<<< viosupgrade -t altdisk -n hostname -m mksysbname -a RootVGCloneDisk [-b BackupFileResource] [-c] [-e Resources: ...] [-F options:... ][-v] viosupgrade -t {bosinst | altdisk} -f filename [-F options:... ] [-v] viosupgrade -q { [-n hostname | -f filename] } viosupgrade -I ISOImage1:ISOImage2 -w directoryPath -x iosmksysbResourceName [-y spotResourceName] Flags: -t Specifies the type of install. Supported types are: bosinst, altdisk. -n Specifies the target VIOS hostname or IP address to perform VIOS upgrade operation. -m Specifies the MKSYSB resource name. -p Specifies the SPOT resource name. -a Specifies the alternate physical volume. if install type is 'bosinst' then the disk(s) will be used to take backup of current rootvg. For 'altdisk' type installation disk(s) will be used to install the provided image. -r Specifies the new rootvg physical volume to install the provided image. -s Specify to skip cloning of the current rootvg disk(s) to alternate disk(s). -b Specifies VIOS configuration backup file resource name. -c Specify if VIOS is part of the cluster. -e Specifies configuration resource(s) to apply as part of the installation. supported resources are resolv_conf, script, fb_script, file_res, image_data, log. -f Specifies file name which contains the list of nodes. -q Check the status of triggered upgrade operation. -I Specifies ISO image files to create ios_mksysb file. -w Specifies the directory path for creating new ios_mksysb file. -x Specifies new ios_mksysb resource name to be created. -y Specifies new SPOT resource to be created from ios_mksysb resource. -F Enables user to skip certain checks to do force installation. <<<<<<<<<<<<<<<<<<<<<<<<<<<<<<< Possible options are : skipclusterstate. <<<<<<<<<<<<<<<<<<<<<<<<<<<<<<< -v Validates the input data for the given VIO Server(s). Note : New options are highlighted with "<<<<<" 1. Option : "-F" ================= Description: Enables user to overwrite certain default parameters to proceed with the installation. Options that can be passed to are "skipclusterstate", "skiprestore", "forcecopy". a. "skipclusterstate" ------------------ Description : Enables user to skip the SSP cluster state check , so that the user can trigger viosupgrade installation on multiple VIOS nodes parallelly. This will show a warning message in the viosupgrade output to inform user that we are skipping the clusterstate check. Note: User should ensure that not all the SSP cluster nodes are down at the same time as this might bring the cluster completely down. Example : viosupgrade -t bosinst -n ferrari10 -m 2031A_72V_ios_mksysb -p 2031A_72V_ios_spot -r hdisk19:hdisk20:hdisk21 -c -F skipclusterstate Sample Output ######################################################################## Found multiple/matching objects for host 'ferrari10', Please select the correct target VIOS object from below choices: CHOICE VIOS OBJECT NAME HOSTNAME 1 ferrari10 ferrari10.pok.stglabs.ibm.com Choice[1-1]: 1 Welcome to viosupgrade tool. Operation triggered for given node(s). Check log files for more information, Log file for 'ferrari10' is: '/var/adm/ras/ioslogs/ferrari10_10486248_Fri_Aug__7_04:09:10_2020.log'. Please wait for completion.. New volume on /home/padmin/gomathi/mksysb/2031A_72V_ios_mksysb.img: Cluster size is 51200 bytes (100 blocks). The volume number is 1. The backup date is: Tue Jul 28 16:51:26 CDT 2020 Files are backed up by name. The user is . The number of archived files is 80262. Upgrading from ioslevel '2.2.6.65' to '3.1.2.00'. Verifying the disk(s) usage and space availability ... Verification of the disk(s) is successful. ferrari10: WARNING: Forcing install with cluster state as 'DEGRADED'. New volume on /home/padmin/gomathi/mksysb/2031A_72V_ios_mksysb.img: Cluster size is 51200 bytes (100 blocks). The volume number is 1. The backup date is: Tue Jul 28 16:51:26 CDT 2020 Files are backed up by name. The user is . The number of archived files is 80262. Verifying whether the MPIO software(s) is installed on the VIOS. Verification of the MPIO software(s) is successful. Initiating the VIOS configuration backup and installation ... ferrari10: Installation triggered for the node 'ferrari10'. Check the status using 'viosupgrade' command. Installation of VIOS may take 30 minutes or more. Please verify the installation status after the specified time. ----------------------------------- Installation triggered for VIO Servers: ferrari10 ----------------------------------- ########################################################################