AIX

 View Only

 Migrating dual VIOS 2.2.6.65 to 3.1

Jump to  Best Answer
Abhimanyu Gupta's profile image
Abhimanyu Gupta posted Fri September 05, 2025 06:32 AM

I need help in migrating VIOS to 3.1, I have downloaded the iso image for 3.1 and it is in vios

Anas AlSaleh's profile image
Anas AlSaleh posted Sun September 07, 2025 03:35 AM  Best Answer

Hi 

Prerequisites :
1- We take note of several important VIOS configurations items, so that we can compare these before and after the upgrade process. This will allow us to ensure the upgrade has completed as expected.
 
$ lsmap -all
$ lsmap -all -net
 
$ lsmap -all -npiv
# lsdev -Cc adapter
# ifconfig -a
# netstat -nr
# hostname
# lspv
#viosbr -backup -file viosbrdatehostnamer o
 
2- Backup Current VIO Server using viosbr command .
 
 
===============================================================================================================
VIO upgrade on Disk if the the current rootvg is mirros or you can assign new disk from SAN , if the current rootvg is mirror , follow the below
 
*unmirror rootvg 
 
1. Reduce the disk from rootvg and use it for upgrade OS using alt_disk_copy
   # unmirrorvg rootvg hdiskx
   # reducevg rootvg hdiskx
   # chpv -c hdiskx
   # bootlist -m normal -o
   # bosboot -ad /dev/hdiskx
 
============================================================================================================
Below steps to upgrade from 2.2.6 to 3.1.4 - 



- Extract/mount the mksysb.image from ISO image you just download and uploaded to VIOS: 
# loopmount -i /tmp/VIOS.iso -o "-V udfs -o ro" -m /mnt1 

- Copy mksysb file from the mounted image to a different location: 
# cp /mnt1/usr/sys/inst.images/mksysb_image /home/VIO31_mksysb_image - disk in use issue? 
Disk must be cleared -PVID- 
chdev -l hdisk# -a pv=clear 
chpv -c hdisk# 
- Start the upgrade process from the copied mksysb file: 
# viosupgrade -l -i /home/VIO31_mksysb_image -a hdiskx (during the upgrade system will reboot 2 times) 
- You can check the upgrade status using the command below: 
# viosupgrade -l -q 
--Check VIOS level ioslevel 
--instfix -i |grep ML 
--lsppchk -v .. check missing packages 
Alexander Pettitt's profile image
Alexander Pettitt posted Fri September 05, 2025 07:13 AM

With 3.1.4 going End of Fix Support April 30th 2026, I would consider 4.1 instead - See PowerVM VIOS Lifecycle Information

IBM has this page on migrating to 3.1 - https://www.ibm.com/support/pages/upgrading-vios-31

Many sites get help from their VAR to help them with their migration. 

Chris Gibson's profile image
Chris Gibson posted Sun September 07, 2025 07:26 PM

As Alexander stated already, it would make more sense to upgrade your VIOS to 4.1. If you need some training on how to use the viosupgrade tool, please consider attending this course: https://community.ibm.com/community/user/blogs/upendra-rajan/2025/09/03/mastering-virtual-io-server-upgrades-an38g-is-out

Steve Munday's profile image
Steve Munday IBM Champion posted Mon September 15, 2025 04:56 AM

Abhimanya,


Hi, good day to you.


In addition to the comments already posted bear in mind the move from VIOS v2 to VIOS v4 is a 2-stage affair. First you need to complete the v2 to v3 piece and then repeat the process for v3 to v4 (v4.1.1.10 being the current latest).


You might want to also consider how you want to safeguard any existing scripts you may have loaded on the existing VIOS as the VIOSUPGRADE command does NOT, automatically, copy these across.


At a high level you might like to consider:


1. Capture evidence of your existing environment -- search for Blogs by @Jaqui Lynch as she has a wealth of knowledge and experience
2. Decide which (configuration) files, if any, you want to have the VIOSUPGRADE command save (things like /etc/hosts, /etc/resolv.conf, etc., etc.) and create a file containing each file you want "saved" on a separate line -- these "saved files" will be placed in /home/padmin/backup_files
3. Consider saving off (to a .tar on a different system) all/any scripts you may have loaded on the existing VIOS for future restoration as these DO NOT get carried forwards by the VIOSUPGRADE command
4. Complete all the pre-IOS upgrade tasks like unmirroring rootvg
5. Upgrade (VIOSUPGRADE) from v2 to v3
6. As v3 is "just" a temporary position you can proceed with re-running the upgrade (VIOSUPGRADE) from v3 to v4 (4.1.1.10 flash ISO is available)
7. With the upgrade to v4 complete, ensure you apply the latest versions/fixes for

- rpm.rte

- OpenSSL

- OpenSSH

- Python

- Java

8. Restore your "saved" files from /home/padmin/backup_files
9. Restore you "saved" scripts from the .tar you created
10. Apply any final iFixes for VIOS v4
11. Check/configure things like (again @Jaqui Lynch has loads of excellent guidance on this)

- Swap space

- Filesystem sizes

- crontab entries

12. Now you're "on" VIOS v4 you can also run


$ updateios -remove_outdated_filesets
$ updateios -rmlang -preserve xx_YY (where xx_YY might be en_US)


13. Complete any outstanding post-IOS upgrade tasks like re-mirroring rootvg etc.
14. Re-capture the "post environment" evidence so you have a clear "before" and "after" snapshot
15. Re-boot and confirm all is looking good


Hope the above is of some help.


Many thanks, Steve

Related Content