*/etc/preserve.list
List of files to be saved during a preservation
BOS installation
*Preservation installation overwrites /usr/, /tmp, /var & /(root) filesystems. But you can save any of these filesystems by enlisting their names in /etc/preserve.list
*Installation Types/Methods
1)New & Complete Overwrite-
-Create rootvg,
-Create /, /usr, /var
-Create the /home
-Restore BOS
-Install additional filesets
-No Restoration of configuration
-No save configuration
2)Preservation
-Create /, /usr, /var
-Restore BOS
-Install additional filesets
-No Create the /home
-No Create rootvg,
-No Restoration of configuration
-No save configuration
3)Migration
-Restore BOS
-Install additional filesets
-Save configuration
-Restoration of configuration
-No Create /, /usr, /var
-No Create the /home
-No Create rootvg,
*Trusted Computing Base
TCB enforces the information security policies of the system. By installing a system with the TCB option, you enable the trusted path,trusted shell, trusted processes, & system-integrity checking.
Because every device is part of the TCB, every file in the /dev directory is monitored by TCB.
Also TCB automatically monitors over 600 additional files, storing critical information about these files in the /etc/security/sysck.cfg file.
It is recommended to back up this file on removable media, after installing the BOS.
-You can enable TCB only at installation time,
-bos.rte.security fileset for TCB
-TCB can be removed by removing the bos.rte.security fileset from the system.
To check if TCB is enabled on your system, issue
-->/usr/bin/tcbck
[/etc/security/sysck.cfg TCB info of all devices stored in this file,backup it ]
*Alternate disk installation
Allows for system installation on a system while it is up & running . Install /upgrade downtime decreses considerably, & the switch over to the new version can then happen with a simple reboot, with the possibility to roll back to the original situation in case of problems.
Alternate disk installation can be used in two ways
1+Cloning the current running rootvg to alternate disk
In this way you have an online backup availabe, at the cost of one or more physical disks.
2+Installing a mksysb image on another disk
-->alt_disk_copy
Creates copies of rootvg on an alternate set of disks
-->smitty alt_clone
-->alt_disk_mksysb
Installs an existing mksysb on an alternate set of disks.
-->alt_rootvg_op
Performs wake,sleep,&customize operations.
*Check if bos.alt_disk_install.rte installed(needed)
-->lslpp -L bos.alt_disk_install.rte
if not
-->geninstall -d /dev/cd0 bos.alt_disk_install.rte
1st CD of Aix installation.
*Alternate mksysb installation
-->smitty alt_msksysb
*Alternate rootvg cloning
-->smitty alt_clone
Once the process is finished , the system reboots from the alternate disk, either as mksysb or cloned rootvg.
If the new environment has problems, you can easily rollback by changing the bootlist to the original boot list.
*alt_disk_install command does the following
1)Create /image.data file based on current rootvg configuration.
2)Creates an alternate rootvg(altinst_rootvg).
3)Creates logical volumes & file systems with the (alt_inst prefix).
4)Generates a backup file list from the rootvg, & if exclude.list file is given, those files are excluded from the list.
5)Copies files to altinst_rootvg's filesystem.
6)If specified installp command installs updates, fixes, or new filesets into the alternate filesystem.
7)bosboot command creates a boot logical volume on the alternate boot disk.
8)Filesystems are then unmounted ,& the logical volumes & file systems are renamed.
9)By default, the bootlist is set to the new cloned rootvg for the next reboot.
*Cloning an Aix5L system
Benefits of cloning the rootvg to an alternate disk
1)Having an online backup available , as in the case of a disk crash . Keeping an online backup requires an extra disk
2)When applying new maintenance levels or updates to a system. A copy of the rootvg is made to an alternate disk, then the updates are applied to that copy. The system runs uninterrupted during this process. When it is rebooted, the system boots from the newly updated rootvg for testing.
If updates cause problems, the old-rootvg can be retrived by resetting the bootlist & then rebooting.
3)With a mksysb image, you can clone one system image onto multiple target systems.
However the target might not contain the same hardware, devices or adapters, or require the same kernel as the source system. All devices & kernels are automatically installed during a BOS installtion.
As a result, when you create a system backup, the mksysb image contains all the device and kernel support. ex. you can create a system backup from systemA & install SystemA's mksysb image onto SystemB without having to use product media to boot systemB.
-->/var/adm/ras/devinst.log
Bos installation log files.
*To view logs in the /var/adm/ras
-->smit alog_show
*To view the bosinstlog file
i.e. /var/adm/ras/bosinst.log
-->alog -o -f bosinstlog
-->alog -t boot -o | more bootlog
*Installation LED codes
c41- Could not determine the boot type or device
c43- Cannot access the boot/install tape.
c46- Normal installation processing.
c49- Could not create or form the JFS log.
c50- Creating rootvg on target disks.
c51- No paging devices were found.
c52- Changing rootvg on target disks.
c53- Not enough space in the /tmp directory to do a preservation installation.
c57- Failure to restore BOS
c61- Failed to create the boot image.
*Filesets(game)
Smallest installable base unit for the AIX5L os.
A fileset includes all files that constitute a complete product, such as bos.net.uucp, or a separately installabe part of a product , such as bos.net.nfs.client
*Packages
A package is a group of separately installable filesets that provide a set of related functions.
for ex. bos.net is a package.
*License Program Products-lpp-requiers license
[A group of packages together providing a complete product & which requires license.]
A complete software product including all packages associated with that licensed program
ex. BOS is a lpp, Tivoli, os , Legato.
*Bundles- A bundle is a list of software that contain filesets+packages+lpp for a particular (customizable) use,s/w.
Such as providing personal productivity software or software for a client machine in a network environment.
system bundles
-->/usr/sys/inst.data/sys_bundles
USer created bundles
-->/usr/sys/inst.data/usr_bundles
*install the bundle using
-->smit update_all
*PTF
Program Temporary Fix, is an updated filesets or a new fileset that fixes a previous system problem.
-->installp
*APAR
Authorized Program Analysis Report
An APAR is an emergency fix, or interim fix, to a unique problem on the system.
APAR will eventually become PTFs , after testing and verification.
--> instfix
*bos(LPP).net(Package).tcp(fileset)
bos.net.tcp.-(suffix extension .exe/.bat)
*Identifying Software Products
VersionNumber.release.modification level.fixlevel
[VRMF]
5.1.0.0<----s/w product level number
5.1.0.0032<---- s/w product update level
*Fileset Level
V.R.M.F.
Version.Release.Modificatio.Fixlevel
*Understanding Maintenance Levels
Determine the maintenance level
-->oslevel -l 5300-09(level parameter)
list filesets at levels earlier than 5300-09
-->oslevel -g 5300-09
lists filesets at levels greater than the current maintenance level.
-->oslevel -r
current maintenance level of your system.
5300-03 (Recommended Maintenance level three)
[Do not confuse this output with the M in V.R.M.F.]
5300-03
5-version
3-major release
00-modification fix
03-ML/TL technology Level
6100-07-02-1150
07-TL
02-SP
*Installing Software
Software can be installed in one of two states
1)applied
2)Committed
1)applied-State places software on the system & retains the previous version of the software. When an update is in the applied state, the previous version is stored in the /usr/lpp/Package-Name/
This process is useful for deploying or testing new software, where it may be neccessary to go back to the previous version of the software in case of errors.
2)Committed state places software on the system and removes all previous levels of the software from the /usr/lpp/package-name directory.
It is recommended that you install new software in the applied state, rather than the committed state, until the new software has been throughly tested.
You can not go back from committed to applied you have to reinstall the previous software.
-->installp -a s/w name
install s/w in an applied state
-->installp -ac s/w name
install s/w in a committed state
-->installp -avX -d /usr/sys/inst.images bos.net
To install all filesets within the bos.net s/w packages
in /usr/sys/inst.images directory in the applied state,with a checksum check.
+To preview an install of all filesets within the bos.net s/w package in /usr/sys/inst.images directory in the committed state & to check for disk space requirements -Preview only
-->installp -acpX -d /usr/sys/inst.images bos.net
+A record of the installp output can be found in /var/adm/sw/installp.summary
-->cat /var/adm/sw/installp.summary
+Committing applied updates
To commit all updates
-->installp -cgX all/package-name
Running this command will commit all the updates & will remove the filesets of the previous version.
+Rejecting applied updates
To reject all applied updates listed in the ./reject.list
--> installp -rBfX ./reject.list
Running this command will remove all the uncommitted updates listed in ./reject.list & bring the systemm back to the previous maintenance level.
+Removing installed software(Preview of Removing)
To preview a remove of bos.net.ipsec.rte & its dependents, with a verbose display of all successes, warnings , and failures.
Preview of uninstalling a fileset.
-->installp -ugp -V2 bos(LPP).net(Package).ipsec(fileset).rte(extension)
Running this command will give you a list of files that will be removed, but will not actually remove them.
+Cleaning up after failed installations
-->installp -C
This will remove all the files installed in the failed installation.
+Listing all installable software on media
To list the s/w that is on your cd-rom
-->installp -L -d /dev/cd0
*Using SMIT fro s/w maintenance
-->/var/adm/sw/installp.log
SMIT stores a record of s/w installation,removal, and maintenance tasks in this log like the installp command.
-->$HOME/smit.log
SMIT also stores a more detailed record here.
To install software products
-->smitty install_latest
To commit an applied s/w update
-->smitty install_commit
To reject a service update that you have installed
-->smitty install_reject
To remove installed & committed s/w
-->smitty install_remove
A* Maintaning optional s/w (applying updates)
Bringing a system to the latest maintenance level involves 3 steps
1)Listing the maintenance level of the s/w
2)Downloading fixes
3)Displaying and updating installed s/w to the latest level
-->lslpp -L fileset name
installed or not
1)Listing the ML
a)check what maintenance level your fileset are currently on
-->lslpp -l
this will list all the s/w that is installed on your system showing the current maintenance level.
b)To list the individual files that are installed with a particular fileset
-->lslpp -f bos.64bit
to display all files installed with bos.64bit fileset
c)To list the installation and update history of filesets
-->lslpp -h bos.symgt.trace
2)Downloadinf fixes
*SUMA
service update management assistant
3)Displaying & Updating installed s/w to the latest level
Once you hava downloaded all the fixes into the /ptf directory, the next step is to install them and bring your system to the latest maintenance level.
+)Displaying an individual fix(instfix command)
The instfix command allows you to install a fix of set of files without knowing any information other than the AUthorized Program Analysis Report(APAR) number or other unique keywords that identify the fix.
A fix can have a singel fileset or multiple filesets. Fix information is organised in the Table of contents(TOC) on the installation media.
After A fix is installed, fix information is kept on the systems in a fix database.
+To list fixes that are on a CD-ROM in /dev/cd0,
-->instfix -T -d /dev/cd0
+To determine if APARIX75893
-->instfix -ik IX75893
+To examine information about APARIX75893 and what it does
-->instfix -aik IX75893
+To list what maintenance levels have been installed on your system
-->instfix -i |grep ML
+To install APARIY73748 from /dev/cd0
-->instfix -k IY73748 -d /dev/cd0
+Use the SMIT fast path to determine what fixes are installed on your system
-->smitty show_apar_stat
i-fix is installed or not
k-APAR number of keyword to be installed
or -->instfix -iv
+Installing an individual fix by APAR
following steps are useful for installing a fix
1)To install the fixes using SMIT,use the SMIT fast path
-->smitty instfix
-->smitty update_by_fix
The system will update the maintenance level of the fileset you selected and upon completion you will have successfully updated the maintenance level of your s/w.
+Updating all filesets to the latest level.
Following steps update filesets to the latest level
1.To install all new fixes that are available from IBM
-->smitty update_all
This procedure will update your s/w to the latest maintenance level.
2. To view the new maintenance level of your s/w
-->lslpp -l
*Creating installation images on a disk
Installable image files (or installation packages) can be copied to hard disk for use in future installations. These image fixes will be copied from your installation media(tape on diskette)to a directory on the disk,so that they may be installed later using the disk directory as the input device
-->smitty bffcreate
To create installation images on your hard disk,All the images will be copied to your hard disk in the /usr/sys/inst.images/ and the /usr/sys/inst.images/.toc file is updated .
for future installations, enter the /usr/sys/inst.images/ directory in the INPUT device/directory as a installation source.
If for some reasons, your .toc file becomes corrupted you will receive the following error 0503-005 The format of .toc file is invalid
In this case, simply use the
--> inutoc /usr/sys/inst.images/.toc
command to recreate your .toc file.
This method of creating installation images is very helpful. Suppose you are in the middle of installation & you need some pre-requisite files which are on different media, your system will not permit to change the media in the middle of installation, so your installation will fail due absence of requisites.
Thats why it is recommended to copy all required images in directory & then install.
So get all requisites filesets from all different media using
--> smitty bffcreate
in the directory /usr/sys/inst.images.
and then use -->installp or
-->smitty install_latest
to install the s/w
*Service Update Management Assistant
-SUMA-supports scheduled & unattended task based download of APAR,PTF,ML and also supports periodically checking of the availability of specific new fixes & entire maintenance levels. SUMA allows multiple concurrent downloads to optimize performance & has no dependency on any web browser.
*Verifying the integrity of the operating system
+lppchk command is used to verify whether the s/w installed on your system is in consistent state.
Always use lppchk after you install-OS,PTF,APAR,additional s/w
+For every installed s/w there are four classes,
1-lpp-information about installed s/w status description
2-inventory-information about files installed by s/w products.
3-product-installation requirements,pre-requisites
4-history-history of installation, updates of s/w products.
+lppchk command verifies the actual state of s/w, filesizes, checksum values, sysmbolic links
-->lppchk -c package name
check if some files ,links have been deleted.
-->lppchk -v
To verify if all filesets are correctly installed & have all their prerequisites.
+installp installs and updates s/w filesystems
*RPM maintains a database of installed packages & their files. RPM is an archive of files specific to a program and contains the program name, version, description , dependencies & program files.
+AIX 5L product media contains installp packages and RPM packages that are installed during BOS installation
+installp packages are located in
-->/mount_point/installp/ppc
+The RPM packages are located in the following path
-->/mount_point/RPMS/ppc
*If you are using the geninstall command to install RPM packages, use the prefix type to indicate to the geninstall command the type of package that you are installing
I-installp format.
R-RPM format.
-->geninstall -d Media
-->geninstall -L -d media
List installable s/w on device.
No comments:
Post a Comment