Aix Technology Level Install
Echnology level update on AIX using smitupdate and altdiskinstall methodAIX Technology level updateLet first Understand AIX oslevel command output before TL update.#oslevel -r7100-047100 is AIX OS version.04 is Technolgy level# oslevel -s7100-7100 is AIX OS version.04 is Technolgy level1720 17 is year 2017 and 20 is week of 2017 year in which SP 04 was released.What exactly AIX Technology update do??In AIX TL update IBM add new features and support for new hardware and also fixing previous bugs which found or exist in current TL version. It’s always good to move to new TL version because of new feature and new hardware support.Let’s see different method for updating TL on AIX.There are multiple method to update AIX TL. By copying AIX TL fileset to local filesystem on AIX LPAR and then use SMITupdateall to update AIX TL. Use altdiskinstall method to do AIX TL update (Recommended method). From NIM server create resources for updating AIX LPAR TL and then initiate TL update from NIM server.4. From NIM server share AIX TL fileset File system to AIX LPAR and then do update using SMIT updateall to update AIX TL.
Use multibos method to AIX TL update.Before updating AIX TL make sure that all required prerequisite are completed.1. Take MKSYSB backup of AIX LPAR. Take configuration backup of AIX LPAR which include df -gt,ifconfig –a and all important configuration file backup.
In case after update admin may require these backup. Also most important note oslevel command output( oslevel –r and oslevel –s).4. Make sure that current OS level is consistent (lppchk -v)and no fileset are missing from current OS.Let see some command which will verify that currently installed AIX TL is stable and AIX admin can proceed for new TL. It’s always recommended that “only proceed for AIX TL update when currently installed TL is stable and all pre-requisite are done.For example if AIX admin want to update AIX TL to TL 07 and after executing below command he found that output message like “ Not all filesets for 6100-06AIXML were found”.
I'm SO confused about the question of whether I can or cannot update an lppsource with a bunch of patches. Someone I know who I think knows a lot about AIX and NIM says I should never do this. But I'm looking at the Redbook 'NIM from A to Z in AIX 5L', which seems to describe exactly how to do it, in section 5.1. And now, I just read APAR IZ03167, which seems to say do NOT do this.
Let me be more specific.I have an lppsource and SPOT that correspond to AIX level 5300. All my servers are running that level right now. I just downloaded all the filesets to upgrade my servers to level 5300.
I have done an upgrade of one of my toy servers from the first mentioned level to the second, using these filesets in a 'smitty updateall'. This seemed to work perfectly.My question is: How do I create an lppsource and SPOT that correspond to the new level, 5300-?The Redbook I mentioned describes in detail how to do a 'smitty nimupdate' on the lppsource, using, apparently, that same set of filesets that I fed into the updateall. Then, it says, create a SPOT from this updated lppsource, and you're done.My friend, who seems to know all about NIM and AIX in general, says to never do this, because Bad Things Will Happen. She says the only reliable way is to order a full CD/DVD set of 5300-, and build the lppsource from that. I think that's what APAR IZ03167 says, too.Can anyone give me a definitive answer?
I hate to have to order a full installable media set every time I want to install a minor upgrade. Is the Redbook wrong, and I really should never try update the lppsource?
My question is: How do I create an lppsource and SPOT that correspond to the new level, 5300-? Answer by example: OverviewWhenever there is a need to update the Technology Level (TL) or Service Pack (SP) in any NIM client, the first thing you need to do is to update your NIM master server. After the NIM master server is updated, you will need to update the lppsource follow by the SPOT. If your NIM environment has a mixture of TL levels, hen in order to have some NIM clients at the original level, you need to keep a copy of the original lppsource and SPOT level. These clients will still need the riginal level of lppsource and SPOT. In the next section, we describe the steps to perform the lppsource update.
In this example, we have an original lppsource nd SPOT level at TL04, and we are creating a new TL05 lppsource and SPOT. Create a new AIX 5L V5.3 5372 lppsource directory, for example, /nimexport/aix53/5300-, and copy the AIX 5L V5.3 5371 lppsource directory into it.log into the ms. Code: Add Software to an lppsourceType or select values in entry fields.Press Enter AFTER making all desired changes.EntryFieldsNote: NIM updates the.toc file in /installp/ppc automatically.Make sure the.toc file in /export/lppsource/lpp-aix5305/installp/ppc is updated.TARGET lppsource LPP-AIX5372SOURCE of Software to Add /nimexport/aix53/5300-SOFTWARE Packages to Add all+-ORINSTALLP BUNDLE containing packages to add +gencopy FlagsDIRECTORY for temporary storage during copying /tmpEXTEND filesystems if space needed? Yes +Process multiple volumes? No +You can also use the command line as follows.
Code: # nim -o update -a packages=all -a source=/dev/cd0 LPP-AIX5305After you have updated the TL05 lppsource, there might be some duplicate updates. You can perform the NIM lppmgr operation to remove them. This operation enables you remove any duplicate software, superseded updates, unnecessary languages, and non-simage software. We recommend that you remove the uplicate software and any superseded updates, but that you do not remove any language software and non-simage filesets unless you are sure that they are not needed for future use. We also recommend that you perform a preview to check what software will be removed before the actual removal.4. Remove any duplicate updates in lppsource resource, as shown in Example 5-3. The following steps are followed when using the SMIT menus.
Code: Eliminate Unnecessary Software Images in an lppsourceType or select values in entry fields.Press Enter AFTER making all desired changes.EntryFieldsTARGET lppsource LPP-AIX5372PREVIEW only? No +REMOVE DUPLICATE software yes +REMOVE SUPERSEDED updates yes +REMOVE LANGUAGE software no +PRESERVE language enUSREMOVE NON-SIMAGES software no +SAVE removed files no +DIRECTORY for storing saved files EXTEND filesystems if space needed? Yes +You can also use the command line as follows. Code: # smitty nimmkresSelect “spot = Shared Product Object Tree - equivalent to /usr file”Define a ResourceType or select values in entry fields.Press Enter AFTER making all desired changes.Entry Fields.
Resource Name SPOT-AIX5372. Resource Type spot. Server of Resource master +. Source of Install Images LPPAIX5372 + (Hit F4 and select:). Location of Resource /nimexport/aix53/spot/EXPAND file systems if space needed? Yes +Comments installp FlagsCOMMIT software updates? No +SAVE replaced files?
Yes +AUTOMATICALLY install requisite software? Yes +OVERWRITE same or newer versions?
No +VERIFY install and check file sizes? No + Note: Run lsnim -l LPP-AIX5372 to check the Rstate and simages.
Rstateshould show Ready for use and simages = yes.CheckAfter the updated lppsource and SPOT are created, you can perform a NIM check operation to check the usability of these resources. When you perform the NIM check operation on the lppsource resource, it rebuilds the table of contents (.toc) file in the lppsource directory and checks whether all the necessary filesets are in the directory to qualify the lppsource for the simage attribute.Check the usability of the lppsource and SPOT as shown in Example 5-5. The following steps are followed when using the SMIT menus. Code: Type or select values in entry fields.Press Enter AFTER making all desired changes.EntryFields.
Resource Name SPOT-AIX5305Build Debug Boot Images? No +Force no +After the lppsource and SPOT resources are updated and ready for use, you can perform software maintenance on NIM clients.
Aix 7.1 Service Packs
Refer to “Client-initiated software maintenance tasks (“pull”)” on page 496 for details. Post updated at 09:52 AM - Previous update was at 09:45 AM -I always make a new SPOT and LPPSOURCE.Copy the old LPPSOURCE to a new directory.
Then update that LPPSOURCE with the new patches.Copy your 5300- to 5300- and then patch 5300.This way you have both versions. You need both versions as long as you have severs at each level.If you update your LPPSOURCE and need to boot a server that has not been updated, you will not be able to boot.
The levels of the filesets must match exactly (from my experience).After every server is updated, and some time has gone by, erase 5300. Your 'answer by example' seems to be a direct quote from the Redbook I mentioned.Your comments at the end seem to say that you have actually done this, more than once, and it works fine. Is this right?However, APAR IZ03167 contains the following, which seems to me to say one shouldn't update your lppsource with patches. Maybe I'm reading it wrong.
What i usually do is create a base install lppsource, a lppsource for stable updates, and a lppsource for latest and greatest updates.This is sound advice. Another take would be to copy the base LPPSOURCE and SPOT resources you want to update (fs-copy will do), create new NIM resources from these copies and update into them. This way you still retain the original resources should you need them.IMHO the most important point in managing a NIM-server is to stay as flexible as possible. If you are able to install any update, base level, fix, etc. Separately your flexibility is greater than otherwise.I hope this helps.bakunin.
Thank you for your replies. Actually, I am more concerned about the SPOT than the lppsource, since I use my NIM server to recover an AIX server if the rootvg were to crap out, and in our annual disaster recovery test. Here's the specific scenario I'm concerned with right now:1. All my servers are running 5.3.0.11. I have an lppsource and a SPOT which exactly match this AIX level.
How To Install Package In Aix
I also take regular mksysb's to the NIM master, so that in a disaster situation, I can recover my NIM master from a mksysb DVD and backups, and then be ready to recover all other AIX servers from mksysb's on the NIM master.2. I want to update them all to the latest 5.3.0.12. This is no big deal, since I have downloaded the required patches, and I can simply do a 'smitty updateall' on each of them, if I want, and not even worry about the NIM.3. After the 5.3.0.12 upgrade is done, I want to still be able to install/recover any AIX server from the NIM master, by using the SPOT and mksysb backup there.QUESTION: How do I best accomplish number (3)?The advice I have from a Known Good AIX Person (KGAP) is that the SPOT must be of a version NO OLDER than the mksysb I want to recover with it. According to the KGAP, I should NOT try to update my SPOT, but should order a full installable version of AIX to match what all my servers are running, and build an lppsource and SPOT from that. This seems terribly slow and inefficient, and I am hoping there's a better way.
I'd hate to have to order a full AIX DVD set every time I upgrade from 5.3.0.n to 5.3.0.(n+1). So, tell me, please: How do you keep your SPOT in sync with all your AIX servers?