2
Patching AIX systems - patches are where? How to apply? Software maintenance in AIX is complicated and alien to the uninitiated. These days, major major AIX OS updates are referred to as a "maintenance level" (ML) and revisions to those code drops are referred to as "service packs" (SP). You'll want to determine what level you systems are currently at and the level you wish to upgrade to prior to starting the process. Use the "oslevel" command to display the software level of a system: $ oslevel 6.1.3.0 Here, oslevel is run without args and displays the base software level, v6.1 ML 3 in the example To display the SP level use, $ oslevel -s 6100-03-02-0939 Here, we are at ML 3, SP 2 of AIX 6.1 NOTE: I would recommend reading the latest version of the Services and Support Best Practices doc before going very far as the info given here barely scratches the surface of the subject. As stated in a previous answer, SUMA is the way to go for quickly gathering OS updates, particularly when one is unfamiliar with navigating the IBM support site and/or AIX maintenance practices in general. With that said, SUMA offers a slew of options and features that can definitely confuse a newbie so here is a short usage scenario: 1. determine the software level that you wish to apply to your systems. 2. use SUMA to download the packages 3. perform a test install of the packages 4. download any missing dependencies using Fix Central (linked in a previous comment) or SUMA itself (SUMA's fileset search can be hit or miss, however) 5. Rinse and repeat until the test comes out clean, then install for real Here is a sample SUMA command invocation that would download the updates need to bring a v5.3 system to ML 9: $ suma -x -a RqType=ML -a RqName=5300-09 -a Action=Download

Patch AIX6.1

Embed Size (px)

Citation preview

Page 1: Patch AIX6.1

Patching AIX systems - patches are where? How to apply?Software maintenance in AIX is complicated and alien to the uninitiated. These days, majormajor AIX OS updates are referred to as a "maintenance level" (ML) and revisions to thosecode drops are referred to as "service packs" (SP). You'll want to determine what level yousystems are currently at and the level you wish to upgrade to prior to starting the process. Usethe "oslevel" command to display the software level of a system:

$ oslevel6.1.3.0

Here, oslevel is run without args and displays the basesoftware level, v6.1 ML 3 in the example

To display the SP level use,

$ oslevel -s6100-03-02-0939

Here, we are at ML 3, SP 2 of AIX 6.1

NOTE: I would recommend reading the latest version of theServices and Support Best Practices doc before going very faras the info given here barely scratches the surface of thesubject.

As stated in a previous answer, SUMA is the way to go forquickly gathering OS updates, particularly when one isunfamiliar with navigating the IBM support site and/or AIXmaintenance practices in general. With that said, SUMA offersa slew of options and features that can definitely confuse anewbie so here is a short usage scenario:

1. determine the software level that you wish to apply toyour systems.

2. use SUMA to download the packages3. perform a test install of the packages4. download any missing dependencies using Fix Central

(linked in a previous comment) or SUMA itself (SUMA'sfileset search can be hit or miss, however)

5. Rinse and repeat until the test comes out clean, theninstall for real

Here is a sample SUMA command invocation that would downloadthe updates need to bring a v5.3 system to ML 9:

$ suma -x -a RqType=ML -a RqName=5300-09 -a Action=Download

Page 2: Patch AIX6.1

1. -x: perform the SUMA action now rather than scheduling ajob using SUMA's built-in schedule

2. -a RqType=ML: set the Request Type to ML3. -a RqLevel=5300-09: select ML 09 of the AIX 5.3 release4. -a Action=Download: set the command action to download.

This is the default but it is included here for clarity.

By default, SUMA will download packages to the directory/usr/sys/inst.images/installp/ppc. Unless it is interrupted,SUMA will perform an inutoc command in the download directoryso there is no need to do so following its run.

Once the software is downloaded, it can be installed usingsmitty:

$ smitty update_all

or using the "update_all" command:

$ update_all -d /usr/sys/inst.images/installp/ppc -p

The "-p" in the "update_all" command signifies "pretend" mode. Remove it after the pretendruns cleanly.