Unit 4

AIX software
installation and maintenance

© Copyright IBM Corporation 2009

Course materials may not be reproduced in whole or in part without the prior written permission of IBM. 5.2
Unit objectives
IBM Power Systems

After completing this unit, you should be able to:

• Define the package definitions and naming conventions
• Understand AIX software levels and states
– Determine the current installed level of the OS and individual filesets

• Identify how software products and updates are installed and

managed on the system
• Recover from broken and inconsistent software states
• How to download fixes using Fix Central and SUMA
• Identify if all the components in the Power and AIX
environment are compatible and supported

© Copyright IBM Corporation 2009

AIX media
IBM Power Systems

AIX AIX AIX AIX

AIX 6.1 Base (DVD or CD)
AIX AIX
+ update CDs
A IX
AIX 6.1 Expansion Pack

AIX AIX 6.1 Infocenter

AIX
AIX Toolbox for Linux

AIX
Mozilla Firefox Browser

© Copyright IBM Corporation 2009

Software packaging definitions
IBM Power Systems

LPP
Base Operating
System Component
bos
Package
Base Networking
package
bos.net
TCP/IP collection
of filesets
bos.net.tcp

bos.net.tcp.server
Fileset
TCP/IP Server fileset
‘the smallest unit’

© Copyright IBM Corporation 2009

Software bundles
IBM Power Systems

• A bundle is a collection of packages and filesets suited for a particular

environment
• There are many predefined system bundles in AIX which include:
– AllDevicesKernels
– Alt_Disk_Install
– openssh_client and openssh_server
• Full list in /usr/sys/inst.data/sys_bundles. Example:

## /usr/sys/inst.data/sys_bundles
/usr/sys/inst.data/sys_bundles ## cat
cat openssh_server.bnd
openssh_server.bnd
## MEDIA="Expansion
MEDIA="Expansion Pack"
Pack"
I:openssl.base
I:openssl.base
I:openssl.man.en_US
I:openssl.man.en_US
I:openssh.base.server
I:openssh.base.server
I:openssh.man.en_US
I:openssh.man.en_US

© Copyright IBM Corporation 2009

AIX software levels
IBM Power Systems

• There are four distinct software levels and management for AIX.
– Base level
– Technology level (TL)
– Service pack (SP)
– Interim fixes

Fix Packs
Interim
Base Technology Service packs
+ fixes
AIX Level level

(Contain APARs)

© Copyright IBM Corporation 2009

What is my AIX version?
IBM Power Systems

• To obtain the AIX level, use the oslevel command.

## oslevel
oslevel -s
-s
6100-02-01-0847
6100-02-01-0847

Service Pack
AIX Level Release date
VRMF for example, 47th week
in 2008
Service Pack

Technology
Level

• To upgrade from one AIX version and release to another, for example,
AIX 5.3 to AIX 6.1, a migration must be performed.
• New TLs or SPs are applied through updates.

© Copyright IBM Corporation 2009

Software installation and maintenance
IBM Power Systems

• All aspects of software installation and maintenance can be

performed from SMIT, the command line, or systems director
console.
• Command line interaction:
– lslpp: lists installed software
– installp: traditional AIX command for installing and maintaining
LPP packages
– rpm: redhat Linux command for installing and maintaining rpm
filesets (part of the AIX Linux affinity introduced in AIX 5L)
– geninstall: a generic installer that installs software of various
package formats: LPP, RPM, and ISMP.

© Copyright IBM Corporation 2009

Software repository
IBM Power Systems

• A location on disk which contains AIX software

– Default image directory is: /usr/sys/inst.images
– AIX filesets require a .toc file
• To copy software, for example from an AIX CD to disk, use the
SMIT facility, copy software to hard disk for future installation (or the
AIX command, bffcreate)
Copy
Copy Software
Software to
to Hard
Hard Disk
Disk for
for Future
Future Installation
Installation
[Entry
[Entry Fields]
Fields]
** INPUT
INPUT device
device // directory
directory for
for software
software /dev/cd0
/dev/cd0
** SOFTWARE package to copy
SOFTWARE package to copy [all]
[all] ++
** DIRECTORY
DIRECTORY for
for storing
storing software
software package
package
[/usr/sys/inst.images]
[/usr/sys/inst.images]
DIRECTORY
DIRECTORY for
for temporary
temporary storage
storage during
during copying
copying [/tmp]
[/tmp]
EXTEND
EXTEND file
file systems
systems if
if space
space needed?
needed? yes
yes ++
Process
Process multiple
multiple volumes?
volumes? yes
yes

© Copyright IBM Corporation 2009

Software states
IBM Power Systems

• The base installation of software is always in a committed

state.
– Committed is a permanent state
• When updates are installed, they can be either applied or
committed.
– Applied software can later be rejected or committed.
6.1.1.1
bos.net.tcp.adt Action: Install & Commit
Committed
6.1.1.1

AIX

6.1.1.1 Saved

6.1.1.1
bos.net.tcp.adt
Action: Apply Committed
6.1.1.2 Reject
6.1.1.2 Applied or
AIX
Commit
6.1.1.2
Committed

© Copyright IBM Corporation 2009

Software listing and versioning
IBM Power Systems

• Software listing is done with the lslpp command.

## lslpp
lslpp -L
-L |grep
|grep bos.net.tcp.server
bos.net.tcp.server
bos.net.tcp.server
bos.net.tcp.server 6.1.1.1
6.1.1.1 CC FF TCP/IP
TCP/IP Server
Server

Version Release Modification Fix

AIX Migration smit update_all
State codes:
State codes:
A -- Applied.
A -- Applied.
B -- Broken.
B -- Broken.
C -- Committed.
C & F are State
C -- Committed.
E -- EFIX Locked. and Type codes.
E -- EFIX Locked.
O -- Obsolete. (partially migrated to newer version)
O -- Obsolete. (partially migrated to newer version)
? -- Inconsistent State...Run lppchk -v.
? -- Inconsistent State...Run lppchk -v.
Type codes:
Type codes:
F -- Installp Fileset
F -- Installp Fileset
P -- Product
P -- Product
C -- Component
C -- Component
T -- Feature
T -- Feature
R -- RPM Package
R -- RPM Package
E -- Interim Fix
E -- Interim Fix

© Copyright IBM Corporation 2009

lslpp, filesets and files
IBM Power Systems

• Switches -f and -w are very useful lslpp flags.

List files in an
LPP fileset.
## lslpp
lslpp -f
-f alex.grumpy.rte
alex.grumpy.rte
Fileset
Fileset File
File
---------------------------------------------------------
---------------------------------------------------------
Path:
Path: /usr/lib/objrepos
/usr/lib/objrepos
alex.grumpy.rte
alex.grumpy.rte 1.0.0.5
1.0.0.5
/usr/local/grumpy/grumpyrecovery
/usr/local/grumpy/grumpyrecovery
/usr/local/grumpy/README
/usr/local/grumpy/README
/usr/local/grumpy/grumpystart
/usr/local/grumpy/grumpystart
/usr/sbin/gfunctions
/usr/sbin/gfunctions
/usr/local/grumpy/grumpycheck
/usr/local/grumpy/grumpycheck
/usr/local/grumpy/grumpystop
/usr/local/grumpy/grumpystop To which
## lslpp
fileset does a
lslpp -w
-w /usr/local/grumpy/grumpystart
/usr/local/grumpy/grumpystart file belong?
File
File Fileset
Fileset Type
Type
-----------------------------------------------------------
-----------------------------------------------------------
/usr/local/grumpy/grumpystart
/usr/local/grumpy/grumpystart alex.grumpy.rte
alex.grumpy.rte File
File

© Copyright IBM Corporation 2009

Installing new software using SMIT
IBM Power Systems

• smit install_all

Install and Update from ALL Available Software

Install and Update from ALL Available Software
Type or select values in entry fields.
Type or select values in entry fields.
Press Enter AFTER making all desired changes.
Press Enter AFTER making all desired changes.
[Entry Fields]
[Entry Fields]
* INPUT device / directory for software .
* INPUT device / directory for software .
* SOFTWARE to install [] +
* SOFTWARE to install [] +
PREVIEW only? (install operation will NOT occur) no +
PREVIEW only? (install operation will NOT occur) no +
COMMIT software updates? yes +
COMMIT software updates? yes +
SAVE replaced files? no +
SAVE replaced files? no +
AUTOMATICALLY install requisite software? yes +
AUTOMATICALLY install requisite software? yes +
EXTEND file systems if space needed? yes +
EXTEND file systems if space needed? yes +
OVERWRITE same or newer versions? no +
OVERWRITE same or newer versions? no +
VERIFY install and check file sizes? no +
VERIFY install and check file sizes? no +
DETAILED output? no +
DETAILED output? no +
Process multiple volumes? yes +
Process multiple volumes? yes +
ACCEPT new license agreements? no +
ACCEPT new license agreements? no +
Preview new LICENSE agreements? no +
Preview new LICENSE agreements? no +

© Copyright IBM Corporation 2009

Installing software using command line, examples
IBM Power Systems

• installp
– a (apply), -c (commit), -p (preview), -g (apply prerequites), -X (expand
filesystems, if needed), -Y (accept license agreements), -d (device or
directory location of software)
## installp
installp -acpgXYd
-acpgXYd .. bos.rte.install
bos.rte.install
## installp
installp -acpgXYd /TL02_SP01
-acpgXYd /TL02_SP01 all
all

• geninstall
– I (use installp flags, as described above), -p (preview), -d (device or
directory location of software)
## geninstall
geninstall -I
-I "-acgXY"
"-acgXY" -p
-p -d
-d .. bos.rte.install
bos.rte.install
## geninstall
geninstall -I "-acgXY" -p -d /TL02_SP01
-I "-acgXY" -p -d /TL02_SP01 all
all

© Copyright IBM Corporation 2009

Red Hat Package Manager filesets
IBM Power Systems

• IBM provides strong Linux affinity within AIX

• Many useful packages for AIX come in RPM format
– Developed by Redhat, now used in many Linux flavors
– Examples (included within the Linux Toolbox for AIX):
• cdrecord
• mkiosfs
• apache Remove
List
package without
• bash packages
dependencies

## rpm
rpm –qa
–qa

## rpm
rpm --nodeps
--nodeps -e
-e cairo-1.0.2-6
cairo-1.0.2-6

## rpm
rpm -i
-i bash-3.2-1.aix.ppc.rpm
bash-3.2-1.aix.ppc.rpm Install
package

© Copyright IBM Corporation 2009

Applying patches to the system
IBM Power Systems

• Ideally, all systems should be at the latest fix pack (TL and SP level).
• IBM recommends installing the complete fix pack.
• System updates can be applied through smit update_all or using
geninstall or installp commands.
Some items
smitty update_all
smitty update_all
removed for
* INPUT device / directory for software /updates
clarity
* INPUT device / directory for software /updates
* SOFTWARE to update _update_all
* SOFTWARE to update _update_all
PREVIEW only? (update operation will NOT occur) yes +
PREVIEW only? (update operation will NOT occur) yes +
COMMIT software updates? no +
COMMIT software updates? no +
SAVE replaced files? yes
SAVE replaced files? yes

• Updates can first be applied, then committed at a later time.

– This enables you to roll back if needed.
– Once software is committed there is no going back without removal and reinstall.

© Copyright IBM Corporation 2009

Applying patches, apply, commit, reject
IBM Power Systems

• installp, example:

# lslpp -L |grep -i cluster |grep pdf

# lslpp -L |grep -i cluster |grep pdf
cluster.doc.en_US.es.pdf 5.4.0.0 C F HAES PDF Documentation
cluster.doc.en_US.es.pdf 5.4.0.0 C F HAES PDF Documentation Apply
# installp -aB -d . cluster.doc.en_US.es.pdf
# installp -aB -d . cluster.doc.en_US.es.pdf Update
(-aB)
# lslpp -L |grep -i cluster |grep pdf
# lslpp -L |grep -i cluster |grep pdf
cluster.doc.en_US.es.pdf 5.4.1.0 A F HAES PDF Documentation
cluster.doc.en_US.es.pdf 5.4.1.0 A F HAES PDF Documentation
Note: “installp –s # will list all Applied software on the system”
Note: “installp –s # will list all Applied software on the system”
Reject
# installp –r cluster.doc.en_US.es.pdf
# installp –r cluster.doc.en_US.es.pdf (-r)
# lslpp -L |grep -i cluster |grep pdf
# lslpp -L |grep -i cluster |grep pdf
cluster.doc.en_US.es.pdf 5.4.0.0 C F HAES PDF Documentation
cluster.doc.en_US.es.pdf 5.4.0.0 C F HAES PDF Documentation

OR ––
OR
Commit all
# installp –c all Applied
# installp –c all
software (-c)
Installation Summary
Installation Summary
--------------------
--------------------
Name Level Part Event Result
Name Level Part Event Result
-------------------------------------------------------------------------------
-------------------------------------------------------------------------------
cluster.doc.en_US.es.pdf 5.4.1.0 USR COMMIT SUCCESS
cluster.doc.en_US.es.pdf 5.4.1.0 USR COMMIT SUCCESS

© Copyright IBM Corporation 2009

Removing installed software
IBM Power Systems

• smit remove
Remove Installed Software
Remove Installed Software
[Entry Fields]
[Entry Fields]
* SOFTWARE name [cluster.es.cspoc.cmds] +
* SOFTWARE name [cluster.es.cspoc.cmds] +
PREVIEW only? (remove operation will NOT occur) yes +
PREVIEW only? (remove operation will NOT occur) yes +
REMOVE dependent software? yes +
REMOVE dependent software? yes +
EXTEND file systems if space needed? no +
EXTEND file systems if space needed? no +
DETAILED output? no +
DETAILED output? no +

• Removing software from the command line

– Remove the firefox web browser
## installp
installp -u
-u Firefox.base.rte
Firefox.base.rte

– (Preview) Remove all X11 software with associated prerequisites

## installp
installp -upg
-upg X11*
X11*

© Copyright IBM Corporation 2009

Fix Central Web site
IBM Power Systems

• To download AIX fixes via the internet, go to:

© Copyright IBM Corporation 2009

Fix Level Recommendation Tool
IBM Power Systems

http://www14.software.ibm.com/webapp/set2/flrt/home
© Copyright IBM Corporation 2009
Unit summary
IBM Power Systems

Having completed this unit, you should be able to:

• Define the package definitions and naming conventions

• Understand AIX software levels and states
– Determine the current installed level of the OS and individual filesets

• Identify how software products and updates are installed and

managed on the system
• Recover from broken and inconsistent software states
• How to download fixes using Fix Central and SUMA
• Identify if all the components in the Power and AIX environment
are compatible and supported

© Copyright IBM Corporation 2009