Complete VIO/Fix Pack upgrade with screen shots :

NOTE: If its dual VIO, 1^st  day do it on vio1 ( alt_disk, migration) , 2^nd day on VIO1 ( fixpack),3^rd day On VIO2 ( alt_disk, migration ) , 4^th day on VIO2 ( fixpack, fix client issues ) , on VIO2 ( remove alt_disk, set bootlist for 2 hdisks and remirror) and (make sure all the pv’s are in active at the client side before do it on VIO1 on last day) after on same day VIO1 ( remove alt_disk and remirror ). At last set the bootlist for both the hdisks ( hdisk0 and hdisk6) and fix the clients pv missing.

For every day (after rebooting) do disk missing activity on client servers.

NIM SERVER CONFIGURATION:

Take backup of /etc/hosts file before making changes on it:

$ cp –p /etc/hosts /home/ujmodhuk/hosts_bkup

Add hostname & IP address:

$ vi /etc/hosts

Check the connectivity: (add viohostname and ip address of it)

ping fsgwvio15

NIM commands:  

smitty nim_mkmac

--------- host name

--------- Kernel to use for Network Boot [mp]

smitty nim_bosinst

---------- Select a TARGET for the operation

---------- Select the installation TYPE

rte - Install from installation images

---------- ACCEPT new license agreements? [yes]

---------- Initiate reboot and installation now? [no]

#lsnim –l <hostname> [verify to see nim configuration before migration and after migration]

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

Before shutdown need to verify the bootlist all the time.

$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

NOTE : After alt_disk completion do reboot ( on particular VIO )

To see port number:

See ifconfig –a; and lscfg –vl <interface_name> ;

Eg: lscfg –vl ent2;

Step 5:$Shutdown –restart (go to Migration steps and boot from SMS mode )

II. MIGRATION STEPS

Log into HMC and select appropriate server and do the following:

Reboot the server to be migrated using shutdown –restart command :

 After rebooting, we have to press 1 to get the SMS (System Management Services) Menu.

Select option 2 - Setup Remote IPL (Initial Program Load)

Select appropriate port no.

 Select option 1: IP Parameters.

Put appropriate ips

Client ip : vios id

Sever ip : nim server ip

Gateway ip : nim server ip

Back to main menu pressing M key then Select Option 5 : Select Boot Options

Select Option 1 : Select Install/Boot Device

Select Option 6 : Network

Select Option 1 : Ethernet

Select Option 2: Normal Mode Boot.

 Select Option 1 : Yes

You will get this screenshot, and server now checks the connectivity to NIM server.

Type 1 and hit Enter.

Type 1 and hit Enter.

Type 1 and hit Enter.

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 )

III. 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 )

Sri:sri:impdocs:script for rootvg disk missing

IV.  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 (i.e. ws181,ws182.. etc ) 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 : 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