VIO FIX PACK UPGRADE :

I. ATL_DISK creation process in VIO:-

Login to HMC and select appropriate VIO servers

$ioslevel

loging as padmin id and follow the bellow steps

$hostname

Oem_setup_env

#host <hostname> -- verify the ip of VIO

step 1: Varify hdisks under rootvg

$ lsvg -pv rootvg

rootvg:

PV_NAME     PV STATE        TOTAL PPs      FREE PPs        FREE DISTRIBUTION

hdisk0            active               319                   11                     00..00..00..00..11

hdisk6            active               319                   27                     00..00..00..00..27

     

Step 2: unmirror the rootvg

             $unmirrorios hdisk6

step 3: remove a hdisk from rootvg

            $reducevg rootvg hdisk6

Take the config of hdisk6 using lscfg –vl hdisk6.

step 4: create alt_disk

            $alt_root_vg -target hdisk6

$bootlist –mode normal -ls or (oem_setup_env ) # bootlist –m normal –o

[ set bootlist to hdisk0 since hdisk6 is cloned ] bosboot –ad /dev/hdisk0

#bootlist –m normal hdisk0 hdisk1

. To apply the updates from a directory on your local hard disk, follow below steps. (fix pack)

The current level of the VIOS must be 2.1.0 or higher

Login to HMC and select appropriate VIO servers

Step 1: Log in to the VIOS as the user padmin.

 Step  2. If you use one or more File Backed Optical Media Repositories, you need to unload media images before you apply the Fix Pack. See details here..

 Step  3. Create a directory on the Virtual I/O Server. ( on /home/padmin/ )

      $cd /home/padmin

      $ mkdir fixpack

      $chown padmin:ibm fixpack

   Step 4. Using ftp, transfer the update file(s) to the directory you created.

$scp –p fixpack (from vio18/sw/fixpack) vio11(current vios server)@ip:/home/padmon/fixpack

Eg: scp fixpack.tar padmin@32.83.114.50:/home/padmin/fixpack

$tar –xvf / home/padmon/fixpack   ( it will untar and create a dir fixpack)

$rm –f <filename.tar>

  Step  5. Commit previous updates by running the updateios command

      $ updateios –commit

  Step  6. Apply the update by running the updateios command ( make sure the path /home/padmin/fix….)

      $updateios -accept -install -dev  /home/padmin/fixpack/fixpack

                  Or

      $ updateios -accept -install -dev

    

   Step 7. If you are upgrading to Fix Pack 24 from VIOS level 2.1.3, run the following command (skip to step 8 if you are upgrading from a prior level of the VIOS): ( not required )

      $ swrole – Padmin

NOTE: Before shutdown make sure all the disks at client side are active only.

  Step 8. To load all changes, reboot the VIOS as user padmin .

      $ shutdown -restart

  Step 9. After the VIOS has rebooted, you are required to accept the license.

      $ license -accept

  Step 10. Verify that the update was successful by checking the results of the updateios command and by running the isolevel command, which should indicate that the ioslevel is now 2.2.0.10-FP-24.

      $ioslevel

NOTE: After this go to client server and fix the issue of disk missing. Do lsvg –p <vgname>; varyonvg <vgname>; syncvg –v <vgname> on both vg’s ( rootvg and uservg )

Remove ATL_DISK and remirror the rootvg in vio:-

step 1: change shell to root

            $oem_setup_env

step 2: remove existing alt_disk

            $alt_disk_install -X

then that will make hdisk6 free again, back to padmin prompt

step 3: back to padmin shell

           $exit

NOTE: Before remirror make sure everything is working fine and check any issues at client side  like disk missing and lscfg –vl <hdisk#> for hdisk0 and alt_disk hdisk i.e hdisk6. Verify the bootlist, bosboot should be in 2 hdisks. If not create it bosboot –ad /dev/hdisk#, hdisk#, set order bootlist –m normal –o hdisk# hdisk#

V. Remirror the rootvg in vio:-

step 4: extend the rootvg

          $extendvg –f rootvg hdisk6

Make sure bootlist,  bootlist –mode normal -ls; or bootlist –m normal –o;set bosboot –ad /dev/hdisk0 and hdisk6

Step5; mirror rootvg

           $mirrorios –f hdisk6   (Note: If we use –defer it prevent it from reboot; $mirrorios –defer hdisk6)

NOTE : mirrorios will reboot the server. Verify bootlist all the time before rebooting.

step 6: needs reboot to setup bootlist by vio.

Again it will reboot… and come up