AIX Package and patches installation Tips

AIX - Software Maintenance

AIX - Software Maintenance

In this software Installation we can do following things

1. Fileset installation
2. Applying the Fileset
3. Reject the Installed Fileset
4. Commit the applied Fileset
5. Remove the Committed Fileset
6. Verify the Installed Fileset ( whether properly installed or not)
7. Clear the braked Fileset installation
8. List the Installed Fileset
9. List the Installed Fileset contents ( What are the files available in File Set)
10. To finding the file, Extracted from which Fileset.
11. To find the command file path
12. To view the fileset history
1. Fileset Installation

The Filesets has additional support files for AIX. Suppose we need additional files, we can install it from Base operating system (bos) CD, Bonus software CD, Expansion Software CD, LPP’s (Licensed program product) CD.

NOTE:

If we want to check the AIX Server performance, we need topas command, this topas command is not by default come under AIX OS installation, So that topas file we have to install from some other CD’s.

First we should mount the CDROM drive in server.

When we mount the CDROM, we required mount point like one directory.

So we should create the directory. Eg. /cdmnt (Directory name will be whatever may be)

#mkdir mount point
#mkdir cdmnt

Then u can mount the CDROM drive in cdmnt directory

#mount –v cdrfs –o ro /dev/cd0 /mount point
#mount –v cdrfs –o ro /dev/cd0 /cdmnt

Verify the Cdrom drive mount process.

#mount

The above command will show the cdrom drive mount point i.e. /cdmnt and cdrfs file system.

Then u go to /cdmnt folder

#cd cdmnt
#pwd
cdmnt
#

Now topas file will be under bos.permaget.tool file set. Now we should find the file set in software cd.

To find the file set using command #installp –Ld /dev/cd0 | grep bos.perf*

If the above bos.permaget.tool file set is available in cd, it will show otherwise it won’t show.

If file set is found then we have to install the fileset.

To install the file set using #installp –agxpd /dev/cd0 file set (for preview installation)
i.e. #installp –agxd /dev/cd0 bos.permaget.tool (for installation)

see difference
Options –agxpd for preview

-agxd for installation

When we type the above command, fileset installation will start and topas file extracted from the fileset and it will store to /usr/sbin/topas (super user or administrator commands stored in /usr/sbin)

After that we can use topas performance monitor utility.

#topas

The above command will display the system performance status, like cpu usage, memory usage, io usage (hdisk’s) network usage, paging space usage .


2. Applying Fileset (It is not permanent installation)

This applying Fileset is just file set installation, i.e. When we updating the old fileset to new fileset, by default installation has done in apply state and old fileset configuration is moved to /usr/lpp/package(fileset) path, After commit the fileset this /usr/lpp/package(fileset) will updated . Because if any problems in updated fileset, we can easily reject(remove) the updated fileset, If updated fileset is working properly we can commit the updated fileset, i.e. permanent installation, this case we cannot reject the fileset, but we can uninstall the fileset.

NOTE:

Suppose we are installing fileset for the first time, this first time installation done in commit state, and When we updating the fileset, installation has done in apply state, suppose that updated fileset giving some problem, we can easily reject the updated fileset.





For fileset installation using command installp

Suppose u want to install one fileset bos.rte

Preview (It will show the installation preview – This preview is not required our testing purpose we are using)
#installp –agxpd /dev/cd0 fileset name

#installp –agxpd /dev/cd0 bos.rte (for preview)

Flags:

a - Apply
g – Perquisites (supporting file)
x – Expand the space
p – Preview
d – Specify the device

After preview we can install the Fileset

#installp –agxd /dev/cd0 bos.rte

After Installation, old installed fileset configuration is moved to /usr//lpp/package (fileset), and updated fileset also available in /usr/lpp/package.


3. Reject the Applied Fileset.

After updating the fileset that installed fileset is moved to applied state, suppose that updated filesets are not working properly then we have to remove the updated fileset and pervious filesets are to be configuring to current working condition.

Now we will reject the updated fileset using

#installp –rgp fileset name (For preview)

#installp –rg fileset name

#installp –rg bos.rte.command

The above command is used to remove the updated fileset and automatically previous fileset is moved to working condition.



4. Commit the Applied fileset (It is permanent installation)

After updating the fileset that installed fileset is moved to applied state, suppose applied filesets are working properly, then we have to commit the updated fileset for permanent installation. Otherwise we will remove the updated fileset using reject option.

Now we will commit the updated fileset using

#installp –cgx fileset name

#installp –cgx bos.rte.command

The above command is used to commit the updated fileset.



5. Remove the Committed fileset (It is complete fileset removal not reject)

After commit the fileset, that fileset is moved to permanent installation, we cannot reject, we have to uninstall the fileset only.

Now we will uninstall the committed fileset using:

#installp –ugp Fileset name

#installp –ugp bos.rte.command (For preview)

#installp –ug bos.rte.command (For un installation)

The above command is used to uninstall the committed fileset.



6. Verify the installed fileset (Whether properly installed or not)

After installation we want to verify whether filesets are properly installed are not, using following command

#lppchk –v fileset name

#lppchk –v bos.rte.command

If any problems it will show the error message otherwise no error message, then we will confirm fileset is installed properly.


7. Clear the braked fileset installation:

While installing the filesets, some problem has occurred, i.e. Cd is not reading or space is not available in volume group.

This time half of the fileset only installed in server, so before next installation, we should remove the half installed fileset using

#Installp –C

To clean the brokend fileset installation


8. List the installed fileset

Suppose we want to see what are the filesets available in Server, Using

#lslpp –l

The above command list the all installed fileset

Suppose you want to find particular fileset in server, Using

#lslpp –l | grep Fileset name

The above command is list the specified fileset only, if file set is not available or not installed, it won’t show anything.


9. List the installed fileset content (What are the files available in fileset)

Suppose we want to see bos.rte.command fileset content, using

#lslpp –f fileset name

#lslpp –f bos.rte.command

The above command is display the bos.rte.command file

Basically bos.rte.command fileset has user commands So it will show the /usr/bin/ls,






10. To find the file, which is installed from which fileset.

Using # lslpp –w /usr/bin/ls

The above command shows the bos.rte.command fileset name, because ls command file is extracted from bos.rte.command fileset

#lslpp –w /usr/sbin/savevg

The above shows some other fileset name.

11. To find the command file path:

Using #which ls

The above command is display the given file path i.e. the above command output will be

/usr/bin/ls

Suppose we want to savevg path, using

#which savevg

/usr/sbin/savevg

12. To view the fileset history:

Using #lslpp –h fileset name

#lslpp –h bos.rte.command

The above command output will be full details of fileset.

Fileset version, installed time, date

NOTE:
Whenever we installing the fileset or fix, in that current path should have the .toc (table of content) file. If this file is not available we cannot install any fileset or fix from that current path

If file is not available, we can create the .toc file using command
#inutoc .

The above command is used to create the .toc file