• Add a Comment
  • Edit
  • More Actions v
  • Quarantine this Entry

Comments (21)

1 barryw commented Permalink

Wow that is seriously cool. <br /> Does this only work with AIX 7.1 or can you migrate from 5.3 to 6.1 using this method too?

2 cggibbo commented Permalink

Sure, you can use this method to migrate a mksysb image from 5.3 to 6.1. Thanks for the comment Barry.

3 fjw999 commented Permalink

Nice article gibbo, tried it out and it works a charm. FW

4 billgncali commented Permalink

Nice, does work from 5.3 tl9 to 7.1? Or do you need to migrate to 6.1?

5 Shazanja commented Permalink

Great article Chris, thanks.

6 cggibbo commented Permalink

Yes, migrating from 5.3 to 7.1 with nimadm will work.

7 bsanjay commented Permalink

cool Solution, Will this work on SAN bootable disk ?

8 cggibbo commented Permalink

I don't see why not, especially if they are booting via a VIO server. However, if you are booting directly from SAN storage, you would probably need to update any MPIO device drivers you may have installed for your particular storage i.e. IBM=SDDPCM, HDS=HDLM, EMS=PowerPath, etc. <div>&nbsp;</div> For example if you migrate from AIX 5.3 to 7.1, and you SAN boot directly from IBM DS8300 storage, then you would need to update SDDPCM to the latest supported version for AIX 7.1 immediately after the AIX migration was completed. <div>&nbsp;</div> HTH. <div>&nbsp;</div> Chris

9 vbaranov commented Permalink

For servers booting up from SAN the only way to upgrade SDDPCM is to uninstall SDDPCM prior to upgrade via pre-migration script and have lpp_source updated with both SDDPCM and host attachment filesets as required. In such case SDDPCM fileset will be uninstalled just before the upgrade and installed back at time of upgrade (on-the-fly). <br /> So, for servers booting up from SAN this way ensures installing the appropriate version of SDDPCM, which is different for 5.3 and 6.1 - as an example).

10 cggibbo commented Permalink

My only additional comment would be to do your homework for your specific MPIO device driver BEFORE you upgrade AIX. Understand what's required and plan for it.

11 acid.plasm@gmail.com commented Permalink

I know that in our environment we forgot to update the sddpcm and now since these are critical machines we are just hoping that nothing goes wrong running an unsupported driver with the updated AIX. <div>&nbsp;</div> Wish we would have known this before. Thanks for the info Chris. <div>&nbsp;</div> Thanks, <br /> http://www.icancompute.ca/aix

12 cggibbo commented Permalink

Thanks for the comment acid.plasma. Unfortunately the SDDPCM guide is pretty clear on what you need to do when upgrading from one version of AIX to another. So I'm sorry you were not aware of this information. <div>&nbsp;</div> I think it is unlikely that you will encounter problems immediately but I would highly recommend that you update to the correct version of SDDPCM for your level of AIX ASAP. <div>&nbsp;</div> I've found the following SDDPCM links very helpful in the past: <div>&nbsp;</div> http://www-01.ibm.com/support/docview.wss?uid=ssg1S4000201 <div>&nbsp;</div> http://www-01.ibm.com/support/docview.wss?uid=ssg1S7001350#AIXSDDPCM <br />

13 CSCCjmclaugh commented Permalink

Good stuff! Chris I do have a question for you. For the volume group in the -j parameter, can there already be filesystems in that VG as long as we have enough space in the VG for the nimadm command to do it's thing?

14 cggibbo commented Permalink

Thanks CSCCjmclaugh. Sure, there's nothing stopping you from using an existing VG, that already contains a file system(s). As a long as there is sufficient free space to house the rootvg of the NIM client(s), you should be fine.

15 RaniSivanandham commented Permalink

Nice Article, NIM master can be AIX6 while migrating mksysb image to 7.1?

Add a Comment Add a Comment