Hi Experts , I want to start migrating our AIX 6.1 to AIX 7.1 . I am planning to use alt_disk_migration . Chris gibson has awesome documentation in the internet. However I am running into an issue with EMC odm filesets . So my current OS is AIX 6.1. and I have this :
lslpp -l | grep EMC
EMC.CLARiiON.aix.rte 5.3.0.9 COMMITTED EMC CLARiiON AIX Support
EMC.CLARiiON.fcp.rte 5.3.0.9 COMMITTED EMC CLARiiON FCP Support
-------------
But if I migrate to AIX 7.1 these are not compatible, because bos.rte will be 7.1. ( i tested trying to install those on a clean AIX 7.1 and failed)
For AIX 7.1 we need the EMC.CLARION.AIX.rte 6.0.0.2 or something. So Now I have dilemma here . I can't install those before migration because we are still in AIX 6.1 . But I can't migrate to AIX 7.1 with EMC.CLARiiON.aix.rte 5.3.0.9 , because it is not good with AIX 7.1. See the problem I have here. I was thinking uninstall those before migration , then I feel like this is too risky for production environment. Any body has any idea, all the help will be appreciated very highly !
I don't think you really need your disks during the migration After you made alt_rootvg, you can wake it up and remove the filesets. After booting in new AIX you install the new versions.
Waking up alt_rootvg: alt_rootvg_op -W -d hdiskX
Removing filesets in alt_rootvg: INUCLIENTS=1 chroot /alt_inst /usr/sbin/installp -u 'EMC.CLARiiON.*'
Putting alt_rootvg back to sleep: alt_rootvg_op -S -t -d hdiskX
Of course, if your rootvg doesn't reside on EMC storage using NPIV or dedicated FC.
Thanks agent.kgb.
You can't wake the altinst_rootvg in this situation . This will only work if it is a TL upgrade. otherwise
alt_rootvg_op -W -d hdiskX
will give you some sort of error , saying can't wake up the vg because current version is lower than alt_rootvg , something like that. I am thinking doing some sort of post install script . keep you posted
The other thing, of course, is to ask EMC for their advice.
Also, IBM support should have some ideas. I would hope that the binary compatibility between AIX 6.1 and AIX 7.1 would let you at least install/migrate AIX and reboot.
If I read/understood you correctly - it is sad that EMC will not permit you to update their drivers on AIX 6.1 (or on the alt_install).
And, thanks for your willingness to keep us current on your progress!
Thanks for everyone for trying to help .So i did test migration with NIMADM , After migration i upgraded EMC odm , now it looks like below (not sure why it is showing two of same fileset) . so far it works, this server has only two LUNs, (test server) no application or anything running on the server. I will know more when I do that on the real server, hope everything runs okay . I need to figure it out how to put that in the lpp_source . EMC is such a pain , one image file came with Symmetrixc, clariion, CELERRA together, i need to separate those install only CLARiiON . I need to figure it out how to add that only in the lpp_source , smit installp take care of that easily, not in this case, or maybe I am just dumb .
lslpp -l | grep EMC
EMC.CLARiiON.aix.rte 6.0.0.2 COMMITTED EMC CLARiiON AIX Support
EMC.CLARiiON.fcp.rte 6.0.0.2 COMMITTED EMC CLARiiON FCP Support
EMC.INVISTA.aix.rte 6.0.0.2 COMMITTED EMC INVISTA AIX Support
EMC.INVISTA.fcp.rte 6.0.0.2 COMMITTED EMC INVISTA FCP Support
EMC.XtremIO.fcp.rte 5.3.0.9 COMMITTED EMC XtremIO FCP Support
EMCpower.MgmtComponent 5.7.2.0 COMMITTED PowerPath Management
EMCpower.base 5.7.2.0 COMMITTED PowerPath Base Driver and
EMCpower.migration_enabler
EMCpower.mpx 5.7.2.0 COMMITTED PowerPath Multi_Pathing
EMC.CLARiiON.aix.rte 6.0.0.2 COMMITTED EMC CLARiiON AIX Support
EMC.CLARiiON.fcp.rte 6.0.0.2 COMMITTED EMC CLARiiON FCP Support
EMC.INVISTA.aix.rte 6.0.0.2 COMMITTED EMC INVISTA AIX Support
EMC.INVISTA.fcp.rte 6.0.0.2 COMMITTED EMC INVISTA FCP Support
# oslevel -s
6100-08-03-1339
# lslpp -L EMC\*
Fileset Level State Type Description (Uninstaller)
----------------------------------------------------------------------------
EMC.CLARiiON.aix.rte 5.3.0.8 C F EMC CLARiiON AIX Support
Software
EMC.CLARiiON.fcp.rte 5.3.0.8 C F EMC CLARiiON FCP Support
Software
# lsdev -Cc disk | grep Virtual
hdisk0 Available Virtual SCSI Disk Drive
hdisk9 Available Virtual SCSI Disk Drive
# getconf DISK_SIZE /dev/hdisk0
40960
# getconf DISK_SIZE /dev/hdisk9
40960
# lsvg -p rootvg
rootvg:
PV_NAME PV STATE TOTAL PPs FREE PPs FREE DISTRIBUTION
hdisk0 active 639 583 127..100..100..128..128
NIM:
# lsnim -t mksysb | grep test
test_mksysb resources mksysb
# lsnim -l test_mksysb | grep location
location = /export/mksysb/test.mksysb
# cp /export/mksysb/test.mksysb /export/mksysb/test.mksysb.bak
# nim -Fo remove test_mksysb
# nim -o define -t mksysb -a server=master -a location=/export/mksysb/test.mksysb -a mk_image=yes -a source=test -a mksysb_flags="Xipa" test_mksysb
+---------------------------------------------------------------------+
System Backup Image Space Information
(Sizes are displayed in 1024-byte blocks.)
+---------------------------------------------------------------------+
Required = 1117817 (1092 MB) Available = 385141436 (376115 MB)
Expanding /tmp.
Filesystem size changed to 262144
Creating information file (/image.data) for rootvg.
Creating list of files to back up
Backing up 26830 files........
26830 of 26830 files backed up (100%)
0512-038 savevg: Backup Completed Successfully.
# nimadm -T test_mksysb -O /export/mksysb/test_upgraded -s spot_71_03_05 -l lpp_71_03_05 -j vg1 -Y
... a lot of output ...
# ls -l /export/mksysb/*test*
-rw-r----- 1 nobody nobody 1124710400 Nov 11 11:05 test.mksysb
-rw-r--r-- 1 root system 943564800 Nov 11 11:58 test_upgraded
Copy new mksysb to the NIM client
Test server:
# nimclient -o cust -a lpp_source=lpp_71_03_05 -a filesets='bos.alt_disk_install'
# alt_disk_mksysb -m /tmp/test_upgraded -d hdisk9 -B
... a lot of output ...
lspv | grep -E '^hdisk(0|9)'
hdisk0 00f91ab70e53153d rootvg active
hdisk9 00cba4a7f647aa36 altinst_rootvg
# bootlist -m normal -o
hdisk0 blv=hd5 pathid=0
hdisk0 blv=hd5 pathid=1
# bootlist -m normal hdisk9
# reboot -q
After reboot:
# oslevel -s
7100-03-05-1524
# lslpp -L EMC\*
Fileset Level State Type Description (Uninstaller)
----------------------------------------------------------------------------
EMC.CLARiiON.aix.rte 5.3.0.8 C F EMC CLARiiON AIX Support
Software
EMC.CLARiiON.fcp.rte 5.3.0.8 C F EMC CLARiiON FCP Support
Software
# mount -o soft nfs_server:/share /mnt
# cd /mnt/EMC/ODM/6.0.0.5
# update_all -Y -d .
....
Installation Summary
--------------------
Name Level Part Event Result
-------------------------------------------------------------------------------
EMC.CLARiiON.aix.rte 6.0.0.5 USR APPLY SUCCESS
EMC.CLARiiON.fcp.rte 6.0.0.5 USR APPLY SUCCESS
* * * A T T E N T I O N * * *
System boot image has been updated. You must reboot the system
after install_all_updates completes to properly integrate the updates.
install_all_updates: Checking for recommended maintenance level 7100-03.
install_all_updates: Executing /usr/bin/oslevel -rf, Result = 7100-03
install_all_updates: Verification completed.
install_all_updates: Log file is /var/adm/ras/install_all_updates.log
install_all_updates: Result = SUCCESS
# lslpp -L EMC\*
Fileset Level State Type Description (Uninstaller)
----------------------------------------------------------------------------
EMC.CLARiiON.aix.rte 6.0.0.5 C F EMC CLARiiON AIX Support
Software
EMC.CLARiiON.fcp.rte 6.0.0.5 C F EMC CLARiiON FCP Support
Software
reboot and ready. But if you've read the whole output, you seen that I've used lpp_source for the update. I don't have EMC ODM filesets in the lpp_source, but it is not so difficult to do. If they were there, they were updated together with the base OS.
something like:
nim# nim -o update -a source=/directory/where/new/EMC/ODM/resides -a packages=all lpp_71_03_05
then you don't even need to update them manually and to reboot the server again.
Wow ! agent.kgb you rock, I will try that and let you know. How did you get all these output? , looks like your environment is same like ours. You truly are helpful person
After you made alt_rootvg, you can wake it up and remove the filesets. After booting in new AIX you install the new versions.