Migrate VIO server to vio2.1_FP22.

1 Introduction This document describes how to migrate the vio server (VIOS) from version 1.X to version VIO2.1_FP22.1. Before the migration, you must migrate the SDD or SDDPCM package. For VIOS version 1.X, the SDD package is devices.sdd.53.rte and the SDDPCM package is devices.sddpcm.53.rte. For VIOS version 2.X, the SDD package is devices.sdd.61.rte and the SDDPCM package is devices.sddpcm.61.rte. 2 Scope These procedures apply if all the following statements are valid for your configuration: Migrating VIOS from version 1.X to version 2.X. SDD (1.6.2.0 or later) or SDDPCM (any version) is installed and configured on VIOS. Virtual target devices (VTD) are configured and backed with SDD or SDDPCM devices. These procedures enable you to perform the following tasks: Preserve the mappings between the virtual target devices and the backing devices so you do not need to destroy and recreate the mappings. Keep the VIO Clients up during the VIOS migration if you have a dual VIOS and there are redundant paths to your VIO Clients. Your dual VIOS can be booting from internal disk or SAN boot disk. 3 3.1

Preparation before migration

The VIO backup is available on the NIM server # mount n580l04:/export/mksysb /mnt

3.2

Backup the Virtual I/O Server with the following command

From padmin prompt: # backupios -file /mnt/<vio_ ame>_iosversion_date_mksysb mksysb or eg: # backupios -file /mnt/n580vio3_1300_04Feb10_mksysb mksysb

3.3

Backup the vio configuration

All physical devices, virtual devices, mapping between the virtual target devices and the backing devices) # mount 10.32.74.17:/souph /mnt cd /mnt/products/vio2.1 ./vio_conf_backup.sh

3.4

On the virtual I/O client, systembackup is available

Example: # ls -ltr /beheer/log/backup/mksysblog/ -rw-r----- 1 root system 2286 Feb 7 03:25 mksysb.2010.02.07 -rw-r----- 1 root system 2285 Feb 14 03:24 mksysb.2010.02.14 # cat /beheer/log/backup/mksysblog/mksysb.2010.02.14

3.5

On the virtual I/O client, check for hardware and software errors.
# errpt # cat /var/adm/syslog

3.6

On the virtual I/O client, check for stale PPs, and the quorum must be off. # lsvg rootvg

3.7

On the virtual I/O client, check for missing disks.

Check that both disks of any mirrored volume group are available in the system and the mirroring is properly synchronized. # lsvg p vg_name (rootvg,appsvg,etc)

3.8

On the virtual I/O client, all file systems must be mirrored

# lsvg l vg_name (rootvg,appsvg,datavg..,all existing vgs on the server)

3.9

On the virtual I/O client, check for missing and failed paths, all paths must be enabled and redundant, except hdisk0 and hdisk1.
# lspath

3.10 On the virtual I/O client, check for disk and diskhcheck_interval. Paths for disks with hcheck_interval=0 will not be automatically recoverd after rebooting the vio server, and you have to enable it manually after reboting vio server. for i in `lspv | awk ' { print $1}'` do echo $i lsattr -El $i | grep hcheck_interval done Enable PATH: Example: # chpath -l hdisk10 -p vscsi0 -s enable 3.11 On the virtual I/O client, change the primary and secondary dump
# sysdumpdev -Pp /dev/sysdumpnull -s /dev/sysdumpnull

. Migrate SDDPCM on the vio server

a. Run oem_setup_env to become root. b. Create the directory /usr/sys/inst.images/Migrate_SDDPCM,
copy file PCM2PCM_OS_SAN_04202009.tar located in /souph/products/vio2.1 on NIM server n580l04 to the directory /usr/sys/inst.images/Migrate_SDDPCM ( use scp). # cd /usr/sys/inst.images/Migrate_SDDPCM
# scp n580l04:/souph/products/vio2.1/PCM2PCM_OS_SAN_04202009.tar .

c. Untar PCM2PCM_OS_SAN_*.tar into the

/usr/sys/inst.images/Migrate_SDDPCM directory and change the permissions of the script files to allow execution. d. Copy the SDDPCM fileset, devices.sddpcm.61.rte, for the new VIOS level into the same directory. If you want to migrate to a SDDPCM PTF level, copy both the base package, devices.sddpcm.61.rte, and the PTF package, devices.sddpcm.61.*.bff, for the new VIOS level into the same directory. If you also want to upgrade the SDDPCM Host Attachment, devices.fcp.disk.ibm.mpio.rte, copy a newer SDDPCM Host Attachment into the same directory. e. Run migratePCMbeforeOSmigrate.sh. It will automatically: i. Put all the virtual target devices in Defined state ii. Unmount file systems and deactivate the volume groups that are created with SDDPCM devices. iii. Remove all the SDDPCM devices. iv. Stop the SDDPCM server. v. Uninstall the SDDPCM for VIOS 1.X package, devices.sddpcm.53.rte. vi. Install the newer SDDPCM Host Attachment package on the same directory. vii. Install SDDPCM for the VIOS 2.X package, devices.sddpcm.61.rte.Important: Do not reboot the VIOS. f. After the script is successfully run, run lslpp l devices.sddpcm.61.rte command to check if SDDPCM for the VIOS 2.X package, devices.sddpcm.61.rte, is successfully installed. 5

. Prepare the NIM server for install.

Setup a Putty session to the n580l04 NIM Server. # /beheer/bin/nim/Migrate_to_Vio21.sh -n <vioserver_ name> -b VIO21FP22 (VIO21FP22 is the migration build for vioserver 2.1.1.0 ) !! Make sure that the lpar vio server is in Open Firmware state, otherwise the script will wait for the lpar to shutdown.!! After the lpar has been shutdown the following will happen:

 <Node name> will be created in de NIM object definitions (If <node name> does not yet exist in the NIM object definitions. Correct NIM resources will be allocated to <node name> BOS install will be enabled The script will enter a loop that will repeatedly query the installation progress with the lsnim command. This loop can be interrupted with the ctrl-c key combination. This will have no effect on the installation progress. The putty session may also be terminated without affecting the installation progress. The installation will continue and be completed unattended. 5.1

Set up a virtual console session to the client partition

mkvterm -m <managed system name> -p <vio_partition name> Note: If you have difficulty with your putty session, log on first to the HMC as hscroot user and then issue the command. If the message A terminal session is already open for this partition appears, then execute the following command and try again: rmvterm -m <server name> --id <vio_server partition id> 5.2

Start the migration

Return to the HMC session that was setup in section 5.1 In the SMS Main menu Select 2: Setup remote IPL Select NIC adapter: 1 Select IP parameters and enter the appropriate ip-addresses as determined in section Error: Reference source not found Return to earlier window (esc key) and select 3 ping test Select 1: Execute ping test (takes about 60 seconds) Enter any key if ping is a success
Now use the M key to go to the Main Menu

Select Select Select Select Select

5: Select Boot Options 1: Select Install/Boot Device 6: Network device: 1 2: Normal Mode Boot

Select 1: Yes, to exit SMS

Now Bootp: wait 60 seconds for Spanning Tree After this a Packet Count starts Installation starts The system will reboot and continue to install several times. Wait for the full installation to complete.

Note: In case pings fails or the BOS install fails to start, there is a problem with IP network connectivity. This may have many root causes: the ipadresses you entered are wrong you chose the wrong Ethernet adapter (if the lpar has more than 1 adapter) Ethernet adapter settings are wrong (make shure the adapter is set to standard Ethernet and NOT IEEE 803.x) The NIM server is in error. (follow NIM troubleshoot procedures to resolve possible problems). Ignore the following errors during the installation

6 . Checking the VIO server migration When the vio server comes back, make sure that the vio server is migrated and all virtual target devices are back in Available state # lppchk -v

# ioslevel 2.1.0.0 # lsmap -all SVSA Physloc Client Partition ID --------------- ------------------------------------------------------------vhost0 U9113.550.10BE8DD-V1-C11 0x00000003 VTD Status LUN Backing device Physloc 7 lpar1vg0 Available 0x8100000000000000 lpar1_rootvg

. Update vio server to VIO2.1.2.10-FP-22.1

Login to vio server Oem_setup_env to become root Mount the remote directory onto the Virtual I/O Server. # mount n580l04:/souph/ /mnt Switch to padmin user #exit Commit previous updates, by running the updateios command # updateios -commit Apply the update by running the updateios command. # updateios -accept -dev /mnt/vio2.1.2.10-FP-22.1 Verify that update was successful by checking results of the updateios command and running the ioslevel command. It should indicate the ioslevel is now 2.1.2.10-FP-22.1 Check the update log
installp: * * * A T T E N T I O N ! ! ! Software changes processed during this session require this system and any of its diskless/dataless clients to be rebooted in order for the changes to be made effective. install_all_updates: Checking for recommended maintenance level 6100-04. install_all_updates: Executing /usr/bin/oslevel -rf, Result = 6100-04

install_all_updates: Verification completed. install_all_updates: Log file is /var/adm/ras/install_all_updates.log

install_all_updates: Result = SUCCESS

To load all changes, reboot the VIOS as User

padmin # shutdown restart

Filesets of Sys_Director:n580l04:/export/lpp_source/vio2.1 -rwxrwxrwx -rwxrwxrwx -rwxrwxrwx -rwxrwxrwx -rwxrwxrwx -rwxrwxrwx -rwxrwxrwx 1 1 1 1 1 1 1 root root root root root root root system system system system system system system 29208576 Nov 12 07:09 DirectorCommonAgent 17254400 Nov 12 07:09 DirectorPlatformAgent 2106368 Nov 12 07:10 sysmgt.cim.smisproviders 2811904 Nov 12 07:10 sysmgt.cim.providers 90175488 Nov 12 07:10 cas.agent 1494016 Nov 12 07:10 tivoli.tivguid 21659648 Nov 12 07:10 sysmgt.cimserver.pegasus

Run this command: /var/opt/tivoli/ep/runtime/agent/toolkit/bin/configure.sh -unmanaged -port 9610 -jport 9614 -nport 9615 -force check this fileset clic.rte is installed: /souph/products/vio2.1

8. Update vio server to VIO2.1.2.13-FP-22.1-sp02 Login to vio server Oem_setup_env to become root Mount the remote directory onto the Virtual I/O

Server. # mount 10.32.74.17:/souph/ /mnt Switch to padmin user #exit Commit previous updates, by running the updateios command # updateios -commit Apply the update by running the updateios command. # updateios -accept -dev /mnt/vio2.1.2.13-FP-22.1-sp02 Verify that update was successful by checking results of the updateios command and running the

ioslevel command. It should indicate the ioslevel is now 2.1.2.10-FP-22.1 On the vio client, enable the Failed or Missing paths AFTER REBOOT, enable all paths for disk with hcheck_interval=0 ( see step 3.10) for i in `lspath |grep -i failed|awk '{print $2}'` do chpath -l $i -s enable -p vscsi1 done On the I/O client, activate rootvg

# varyonvg rootvg On the VIO server:

echo "export ENV=/home/padmin/.ksh" >>/home/padmin/.profile

. Migrate the Second vio server

Repeate step 3.6,3.7,3.8,3.7,7,8,3.10 for the vio client Repeate steps 3.1,3.2,3.3,4,5,5.1,6,9 for the second vio server

.On the virtual I/O client, change the primary and secondary dump
# sysdumpdev -Pp /dev/hd7 -s /dev/hd7x

device