-
AnswerThis document covers migration preparation information relating to AIX 5.3, and 6.x.In AIX V5, at the first reboot after an install, you will be prompted to view/accept your licenses before you can continue to use your system.Starting in AIX Version 6.1, a separate Software Maintenance Agreement (SWMA) acceptance window displays during installation immediately after the license acceptance window. The response to the SWMA acceptance (accept or decline) is stored on the system, and either response allows the installation to proceed, unlike license acceptance which requires an accept to proceed.NIM masters/servers which are to serve version 5, 6, or 7 resources should be upgraded first. A NIM master/server must be at the same level or later than the software in any resources being served.Any migration will require more space.
If you have no free partitions in the root volume group, or all file systems are near full, it would be a good idea to add another disk to the rootvg. Alternatively you can install a mksysb of the system to a larger disk before running the migration.
See the table below for the required space information for AIX 5, 6, and 7.FilesystemAIX 5AIX 6AIX 7/ (root)76 MB196 MB196 MB/usr1668 MB2834 MB1952 MB/var372 MB480 MB384 MB/tmp128 MB128 MB128 MB/opt364 MB420 MB352 MB/adminN/A128 MB128 MB/var/adm/ras/livedumpN/A256 MB256 MB.Be sure any additional applications you are currently running are supported on the version of AIX you are migrating to, and if they need to be upgraded before, or after the migration. Obtain the latest versions required for running at your new level.For more complete information on your release, it is highly recommended you review the Release Notes.latest version of the media should be used to do the migration. The latest version will always be shipped when you order the media. If you have an older version of the media and would like to obtain the latest version, you can order it at the following web site:assistance is required registering for the site, call Software Delivery(1-800-879-2755 opt2 then opt2 again for the U.S.). They will requirethe machine model and serial number of a machine licensed to run theAIX version you are ordering.
Outside the U.S., contact your local supportcenter.There are things that you can do to speed your migration along and avoid potential problems. While some may and some may not be official requirements to migrate your system, they are recommended and can prevent situations that may cause the system to hang and a restore to be necessary.
Break mirroring on the root volume group before the migration begins.
Lsdev -Cc processor will show the number of physical processors (or virtual processors in a shared processor LPAR.1. Lsdev -Cc processorproc0 Available 00-00 Processorproc2 Available 00-02 ProcessorSMT thread processors are seen with bindprocessor1.
Aix 6 Os X
Bindprocessor -qThe available processors are: 0 1 2 3lparstat -i will show the virtual and logical processors.1. Lparstat -i grep CPUOnline Virtual CPUs: 2Maximum Virtual CPUs: 15Minimum Virtual CPUs: 1Maximum Physical CPUs in system: 2Active Physical CPUs in system: 2Active CPUs in Pool: 2Physical CPU Percentage: 25.00%topas -L shows logical processors,mpstat shows virtual1. Lsattr -El proc0frequency Processor Speed Falsesmtenabled true Processor SMT enabled Falsesmtthreads 2 Processor SMT threads Falsestate enable Processor state Falsetype PowerPCPOWER5 Processor type False1. Lscfg -v grep -i procModel Implementation: Multiple Processor, PCI busproc0 Processorproc2 Processor1. Prtconf pgSystem Model: IBM,9111-520Machine Serial Number: 10EE6FEProcessor Type: PowerPCPOWER5Number Of Processors: 2Processor Clock Speed: 1499 MHzCPU Type: 64-bitKernel Type: 64-bit. Thank you ddup,1. Could you explain how definition of virtual CPUs/cores is done in PowerVM.
For example is it possible to define a one quad core CPU for LPAR if the physical CPU in IBM box is dual core? Or is it possible to define two Dual Core CPUs for LPAR if the total number of physical CPU in IBM box is one Dual Core?I0019m not talking about performance is such scenarios. I just want to understand the logic behind it.2.
Could you comment each line in the following AIX response to lparstat -i grep CPU. Is that responce from AIX running on LPAR?Online Virtual CPUs: 2Maximum Virtual CPUs: 15Minimum Virtual CPUs: 1Maximum Physical CPUs in system: 2Active Physical CPUs in system: 2Active CPUs in Pool: 2Physical CPU Percentage: 25.00%. I'm sorry, not sure what are you asking. If you have 1 16-way core it means you have 16 processors in the same core.
You can't do much with cores actually, it's just the way it's build. So let's just forget about it. The 16 processors you can split either way you want to between your LPARs. With Advanced micro-partitioning enabled you can even split as less as 1/10 of a CPU to a LPAR.
All that is done on HMC level. On the LPAR under AIX (or Linux) you will just see CPUs (processors). If you enable SMT it can present those fractions of those physical processors as a single separate processor to drive utilization up, if an application is multithreaded or it's many of them, either way. If it's a single application that is single threaded - SMT can degrade performance.2. 'capped' means that an LPAR can only consume up to its 'entitled capacity', which is basically, as described in my comment, 'Physical CPU percentage' multiplied by number of 'Online virtual CPUs', expressed in fractions of physical CPUs (an absolute value).'
Uncapped' in contrast means that the above does apply only in contention situations, where 'entitled capacity' acts as a guaranteed share.If 'uncapped', this share can be exceeded when enough resources are available, as needed by the LPAR, but limited by the number of online virtual CPUs (as I said, no more than one physical CPU per virtual CPU).There is an additional configuration value, 'Variable capacity weight', which is used in situations where LPARS exceeding their entitled capacity have to compete for CPU resources. Here, bigger means better.' Capped' and 'uncapped' are settings made in the partition profiles.Back to lparstat -'lparstat -i' shows a static view, basically the maximum (and guaranteed) values as configured in the profile (maybe changed via DLPAR).'
Lparstat' alone or with the interval count parameters shows a dynamic view of actual values, thus reflecting situations where the entitled capacity (uncapped LPARs) is exceeded - '%entc' greater than 100% and 'physc' greater than 'entitled capacity'. To be precise - 'physc' is '%entc' multiplied by 'entitled capacity' divided by 100.Hope I could clarify a bit, but please don't hesitate to ask if I could not.wmp.