xaminmo: (Logo IBM CATE)
[personal profile] xaminmo posting in [community profile] eserver
If you've ended up upgraded to newer AIX, and are SAN boot from SDDPCM, there is hope:
* mksysb -eXpi /dev/rmt0 ## just in case it all blows up
* ## Stop/quiesce what you can, unmount filesystems, vary off volume groups.
* vi /usr/lpp/devices.sddpcm.53/deinstl/devices.sddpcm.53.rte.pre_d
* ## Add "exit 0" as the first line after the shebang.
* ZZ
* installp -ug devices.sddpcm.53
* installp -acXYgd /export/lpp_source/sddpcm devices.fcp.disk.ibm.mpio.rte devices.sddpcm.71.rte
* lspv | grep rootvg | cut -f 1 -d \ | xargs -n1 bosboot -ad
* shutdown -Fr now

This worked for me at 2.6.0.3 on several different systems.

Date: 2016-04-26 07:18 am (UTC)
From: (Anonymous)
Thanks for this Josh,
I've included this in a post installation (-z) script for nimadm alt_disk_migration. The alt_disk migration takes place is a chroot environment and I expected that there would be no real access to disk device drivers from within the chroot. This seems to be true and my environment migrated successfully from AIX 6 and devices.sddpcm.61.rte 2.6.0.3 to AIX 7 and devices.ssdpcm.71.rte 2.6.7.0
I bundled the sddpcm and devices.fcp.disk.ibm.mpio into the post installation script using uuencode because by the time the post installation script runs, the lpp_source has been unmounted.
The script includes a bit of logic (lslpp -Lqc "devices.sddpcm*") to find the current version and decides whether or not to upgrade.
If an upgrade is necessary, the deinstallation script is found using "ls /usr/lpp/devices.sddpcm*/deinstl/*pre_d" and replaced as you describe.
This has helped us towards our goal of '1-click' upgrades.
Regards, Simon

Profile

eserver: (Default)
IBM POWER servers

June 2017

S M T W T F S
    123
45678 910
11121314151617
18192021222324
252627282930 

Most Popular Tags

Page Summary

Style Credit

Expand Cut Tags

No cut tags
Page generated Sep. 25th, 2017 10:25 pm
Powered by Dreamwidth Studios