Sunday, May 24, 2009

AIX - Installation - Perform a new and complete overwrite BOS installation from CD

AIX - Installation - Perform a new and complete overwrite BOS installation from CD

Step 1. Prepare your system

-There must be adequate disk space and memory available. AIX 5L Version 5.2 and AIX 5L Version 5.3 require 128MB of memory and 2.2GB of physical disk space.

-Make sure your hardware installation is complete, including all external devices.

Step 2. Boot from the AIX product CD

-Insert the AIX Volume 1 CD into the CD-ROM device.

-Make sure all external devices attached to the system, such as CD-ROM drives, tape drives, DVD drives, and terminals, are turned on. Only the CD-ROM drive from which you will install AIX should contain the installation media.

-Power on the system.

-When the system beeps twice, press F5 on the keyboard or 5 on an ASCII terminal. If you have a graphics display, you will see the keyboard icon on the screen when the beeps occur. If you have an ASCII terminal, you will see the word keyboard when the beeps occur.
-Select the system console by pressing F1 or 1 on an ASCII terminal and press Enter.

-Select the English language for the BOS installation menus by typing a 1 in the Choice field. Press Enter to open the Welcome to Base Operating System Installation and Maintenance screen.

-Type 2 to select 2 Change/Show Installation Settings and Install in the Choice field and press Enter.


Welcome to Base Operating System
Installation and Maintenance


Type the number of your choice and press Enter. Choice is
indicated by >>>.

1 Start Install Now with Default Settings

2 Change/Show Installation Settings and Install

3 Start Maintenance Mode for System Recovery

88 Help ?
99 Previous Menu
>>> Choice [1]: 2


Step 3. Set and verify BOS installation settings


-In the Installation and Settings screen, verify that the installation settings are correct by checking the method of installation (new and complete overwrite), the disk or disks you want to install, the primary language environment settings, and the advanced options.

If the default choices are correct, type 0 and press Enter to begin the BOS installation. The system automatically reboots after installation is complete.

-Go to Step 4. Configure the system after installation.

Otherwise, go to sub-step 2.
To change the System Settings, which includes the method of installation and disk where you want to install, type 1 in the Choice field and press Enter.


Installation and Settings


Either type 0 and press Enter to install with current settings,
or type the number of the setting you want to change
and press Enter.


1 System Settings:
Method of Installation..................New and Complete Overwrite
Disk Where You Want to Install..hdisk0


>>> Choice [0]: 1


Type 1 for New and Complete Overwrite in the Choice field and press Enter. The Change Disk(s) Where You Want to Install screen now displays.


Change Disk(s) Where You Want to Install


Type one or more numbers for the disk(s) to be used for
installation and press Enter. To cancel a choice, type the
corresponding number and Press Enter. At least one
bootable disk must be selected. The current choice is
indicated by >>>.

Name Location Code Size(MB) VG Status Bootable

1 hdisk0 04-B0-00-2,0 4296 None Yes
2 hdisk1 04-B0-00-5,0 4296 None Yes
3 hdisk2 04-B0-00-6,0 12288 None Yes

>>> 0 Continue with choices indicated above

66 Disks not known to Base Operating System Installation
77 Display More Disk Information
88 Help ?
99 Previous Menu

>>> Choice [0]:

In the Change Disk(s) Where You Want to Install screen:

-Select hdisk0 by typing a 1 in the Choice field and press Enter. The disk will now be selected as indicated by >>>. To unselect the destination disk, type the number again and press Enter.

-To finish selecting disks, type a 0 in the Choice field and press Enter. The Installation and Settings screen now displays with the selected disks listed under System Settings.

-Change the Primary Language Environment Settings to English (United States). Use the following steps to change the Cultural Convention, Language, and Keyboard to English.

-Type 2 in the Choice field on the Installation and Settings screen to select the Primary Language Environment Settings option.

-Type the number corresponding to English (United States) as the Cultural Convention in the Choice field and press Enter.

-Select the appropriate keyboard and language options.

-Verify that the selections are correct in the Overwrite Installation Summary screen, as follows


Overwrite Installation Summary

Disks: hdisk0
Cultural Convention: en_US
Language: en_US
Keyboard: en_US
64 Bit Kernel Enabled: No
JFS2 File Systems Created: No
Desktop: CDE
Enable System Backups to install any system: Yes

Optional Software being installed:

>>> 1 Continue with Install
88 Help ?
99 Previous Menu

>>> Choice [1]:

-Press Enter to begin the BOS installation. The system automatically reboots after installation is complete


Step 4. Configure the system after installation

-After a new and complete overwrite installation, the Configuration Assistant opens on systems with a graphics display. On systems with an ASCII display, the Installation Assistant opens.

-Select the Accept Licenses option to accept the electronic licenses for the operating system.

-Set the date and time, set the password for the administrator (root user), and configure the network communications (TCP/IP).

Use any other options at this time. You can return to the Configuration Assistant or the Installation Assistant by typing configassist or smitty assist at the command line.

-Select Exit the Configuration Assistant and select Next. Or, press F10 or ESC+0 to exit the Installation Assistant.

-If you are in the Configuration Assistant, select Finish now. Do not start the Configuration Assistant when restarting AIX and select Finish.


At this point, the BOS Installation is complete, and the initial configuration of the system is complete.

Saturday, May 23, 2009

AIX - BOS Installation Methods

AIX - BOS Installation Methods


AIX - Installation - Migration

AIX - Installation - Migration

This method upgrades from earlier versions of the AIX BOS to AIX 6.1 (see the release notes for restrictions). The migration installation method is used to upgrade from an existing version or release of AIX to a later version or release of AIX. A migration installation preserves most file systems, including the root volume group, logical volumes, and system configuration files. It overwrites the /tmp file system.

AIX - Installation - Preservation

AIX - Installation - Preservation

This method replaces an earlier version of the BOS but retains the root volume group, the user-created logical volumes, and the /home file system. The system file systems /usr, /var, /tmp, /opt, and / (root) are overwritten. Product (application) files and configuration data stored in these file systems will be lost. Information stored in other non-system file systems will be preserved.

AIX - Installation - New and Complete Overwrite

AIX - Installation - New and Complete Overwrite

This method installs AIX 6.1 on a new machine or completely overwrites any BOS version that exists on your system.

AIX - Installing the Base Operating System

AIX - Installing the Base Operating System

There are multiple ways to install the AIX® base operating system.

The Base Operating System (BOS) installation program first restores the run-time bos image, then installs the appropriate filesets, depending on your selections. The installation program automatically installs required message filesets, according to the language you choose

If you are reinstalling on an older system, the DVD media can only be used to boot or reinstall on 64-bit systems. To determine if your system is a 32-bit system or a 64-bit system, run the prtconf command with the -c flag.

The following installation methods are available on AIX:

New and Complete Overwrite

Preservation

Migration

Wednesday, May 20, 2009

AIX - Software Management

AIX - Software Management

A fileset is the smallest installable base unit for the AIX operating system (example: bos.perf.pefstat). A package is a group of separately installable filesets that provide a set of related functions (example: bos.perf). A Licensed Program Product (LPP) is a complete software product including all packages associated with that licensed program (example: bos). A bundle is a list of software that can contain filesets, packages, and LPPs that are suited for a particular use (examples: CDE, KDE, GNOME).

Each fileset in a product can be divided into three parts: usr, root, and share. Parceling of a software product is used for diskless and dataless clients. Thus it can be installed on one machine (the server) and then be used remotely by other machines on a network (the clients).
The usr part of a software product can be shared by machines with the same hardware architecture (stored in /usr).

The root part (optional) of a software product cannot be shared by machines. In a client/server environment, these are the files for which there must be a unique copy for each client of a server. Most of the root software is associated with the configuration of the machine or product (stored in the root (/) file tree. The /etc/objrepos directory contains the root part of an installable software product's VPD).
The share part (optional) can be shared among machines, even if they have different hardware architectures.The share part of a product is always packaged in a separately installable package (stored in /usr/share).
The format for a software product level in AIX 5.2 is as follows: versionnumber.releasenumber.modificationlevel.fixlevel


configassist

Displays the Configuration Assistant wizard (graphics display).

install_assist
Starts the Installation Assistant application (ASCII display).

geninstall

A generic software product installer for installp, InstallShield Multi-Platform (ISMP), the Red Hat Package Manager (RPM) installer and Uniform Device Interface (UDI).
geninstall –Ld /dev/cd0 : lists the contents of the CD media.
geninstall -d /tmp/RPM * : installs all RPM packages in the /tmp/RPM directory.
geninstall -d /dev/cd0 R:cdrecord : installs the cdrecord RPM package.

install_wizard

Invokes the Web-based System Manager Install Wizard or the SMIT install menu.
install_wizard -d /dev/cd0 : invokes the Web-based System Manager Install Wizard using an install CD in /dev/cd0.

gencopy

Allows software products of various packaging formats (installp, RPM, ISMP, UDI) to be copied. Wraps to the bffcreate command.
gencopy –Ld /dev/cd0 : lists the contents of the CD media.
gencopy –d /dev/cd0 I:bos.perf R:cdrecord : copies bos.perf and cdrecord images from CD media to the default directory (/usr/sys/inst.images).

installp

Install, update, and perform maintenance tasks on software.
installp -aXYd /dev/cd0 bos.perf : installs (automatically committed) all filesets within bos.perf from /dev/cd0, expands file systems if necessary (-X), and accepts software licenses (-Y).
installp -pad /dev/cd0 X11.Dt : previews installation of X11.Dt from /dev/cd0.
installp -u -V2 X11.Dt : removes fileset X11.Dt with a verbose display of successes, warnings and failures.
installp -ld /dev/cd0 : lists all software products and their separately installable options on /dev/cd0.
installp -cgX all : commits all applied updates and removes the filesets for the previous version.
installp -C : cleans up after a failed installation.

mkinstallp

Creates software packages in installp format.


rpm

Installs, upgrades, queries, and deletes Linux RPM packages and maintains the RPM package database (located in /var/opt/freeware/lib/rpm).
rpm -qa : queries installed RPM packages.
rpm -Uvh * : installs the RPM packages in the current directory.

lslpp

Displays information about installed filesets/fileset updates.
lslpp -l bos.net.nfs.client : displays the maintenance level and state.
lslpp -L all : lists all installed software.
lslpp -L bos.dosutils : check if software installed.
lslpp -f bos.perf : displays the names of all the files of fileset bos.perf.
lslpp -ha : lists installation history of filesets.
lslpp -w /usr/sbin/nfsd : lists the fileset that the file belongs to.
lslpp -E bos.rte : displays the license agreements of the installed filesets.
lslpp -v :shows only the filesets that do not have the required prerequisites or are not completely installed.


inulag

Manages license agreements (front end).
inulag -l : lists all available software license agreements.

epkg

Creates emergency fix (efix) packages that can be installed by the efix manager, emgr.
epkg perf : runs the epkg command in interactive mode and creates efix package perf.

emgr

Starts the emergency fix (efix) manager, which installs, removes, lists, and checks system efixes. The efix manager installs packages created with the epkg command and maintains a database containing efix information. Databases are in the /usr/emgrdata/DBS directory.
emgr -l : lists all efixes on the system.
emgr -X -e perf.040503.epkg.Z : installs efix package perf.040603.epkg.Z and automatically expand file systems if needed.


lppmgr

Manages an existing installp image source.
lppmgr -d /images -u : lists all duplicate and conflicting updates in image source directory /images.
lppmgr -d /images -u -r : removes all duplicate and conflicting updates in image source directory /images.

lppchk

Verifies that files of an installable software product (fileset) match the SWVPD database information for file sizes, checksum values, or symbolic links.
lppchk -v : verifies that all filesets have all required requisites and are completely installed.
lppchk -c X11.Dt : checks that file checksums and sizes of X11.Dt are consistent with SWVPD.
lppchk -l 'bos*' : verifies the symbolic links of all 'bos*' software products.

compare_report

Compares fileset levels to those available and generates a report of filesets needed.
compare_report -s -r /tmp/LatestFixData52 -l : compares the software installed on a system (-s) to the report of available updates (-r) LatestFixData52, available from the support Web site at IBM.

oslevel

Reports the latest installed maintenance level of the system.
oslevel -r : determines the highest recommended maintenance level reached for the current version of AIX.
oslevel -lr 5100-04: lists which fileset updates are missing if after installing ML 04 on 5100-03 the command oslevel -r still shows 5100-03 (so, preferrably no output!).

instfix

Installs filesets associated with keywords or fixes.
instfix -i | grep ML : displays all ML's installed.
instfix -ik "IY39231 IY38794" : checks if fixes IY39231 and IY38794 are installed.
instfix -k IY42424 -d /dev/fd0 : installs fix IY42424 from diskette.

install_all_updates

Updates installed system software to the latest level that is on the media and verifies the current recommended maintenance level.
install_all_updates -d /dev/cd0 : installs all installp updates on /dev/cd0 and verifies the current recommended maintenance level.
install_all_updates -d /images -rc : commit installs all installp updates and installs any installable rpm updates in directory /images.

whence

Displays the absolute path name.
whence nfsd : displays the full path of the nfsd program.

what

Displays identifying information in files.

which_fileset

Displays which fileset owns a command.
The bos.content_list fileset must be installed.
which_fileset topas : displays which fileset owns the topas command.

inutoc

Creates a .toc file.
inutoc : creates the .toc file for the /usr/sys/inst.images directory.

AIX - File Management

AIX - File Management

procfiles

procfiles -n `ls /proc` : lists all the process and files they have open.

find

find / -xdev -type f -mtime -1 -ls | sort +6nr | head -n 20 : lists the top-20 largest files in / that where used within the last 24 hours.

AIX - Hardware Installation and Configuration Management

AIX - Hardware Installation and Configuration Management

Available hardware platforms: MCA-based uni-processor models (rs6k), MCA-based symmetric multiprocessor models (rs6ksmp), ISA-bus models (rspc), PCI-bus models (CHRP). AIX V5.2 is not supported on MCA and PReP architecture hardware. The "AIX Statement of Direction" gives a complete list of unsupported models.

lscfg

Displays configuration, diagnostic and VPD information about the system.
lscfg -vp : Displays the system model, machine serial, processor type, number of processors, processor clock speed, cpu type, total memory size, network information, filesystem information, paging space information, and devices information.
lscfg | grep proc | wc -l : lists the # of processors.


prtconf or lsconf

Displays system configuration information.
prtconf -s : displays the processor clock speed.
prtconf -k : displays the kernel type in use.
prtconf -m : displays memory.

snap

Gathers system configuration information.
snap -a : gathers system configuration information. The output is written to the /tmp/ibmsupt directory.

uname

Displays the name of the current operating system.
uname -a : displays the machine ID and version banner.
uname -x : displays the operating system in use, the host name, the machine ID number of the hardware, the release number of the operating system, the operating system version and the system model name.

mach

Displays the processor architecture of the machine.

getconf

Displays system configuration variable values.
getconf HARDWARE_BITMODE : displays hardware bit mode (64 or 32 bit).
getconf KERNEL_BITMODE : displays kernel bit mode (64 or 32 bit).
getconf DISK_SIZE /dev/hdisk2 : displays disk size in MB.
getconf REAL_MEMORY : displays real memory size in MB.

cfg2html

A system configuration to HTML converter (Open Source)


file


Determines the file type.
file prog : displays user process bit mode of program prog. Returns:
executable (RISC System/6000) or object module not stripped (32 bit program),
or 64-bit XCOFF executable or object module not stripped (64 bit program).
file /unix : the returned link shows which kernel is running: unix_up = 32-bit uniprocessor kernel, unix_mp = 32-bit multiprocesssor kernel, unix_64 = 64-bit multiprocessor kernel.

cfgmgr

Configures devices by running the programs in /etc/methods directory and optionally installs device software.
cfgmgr : runs the Phase 2 configuration rules (second boot phase for normal boot) (same as using the -s flag).
cfgmgr -v : makes devices available that where not powered on when the system started.
cfgmgr -l scsi1 : configures detected devices attached to the scsi1 adapter.
cfgmgr -i /usr/sys/inst.images : installs device software (using the directory /usr/sys/inst.images) automatically during configuration.

chcons

Redirects the system console to device or file, effective next startup.
chcons -a login=enable /dev/tty0 : changes the system console to device /dev/tty0. Use /dev/lft0 for the default LFT display.
chcons /tmp/console.out : redirects the system console to file /tmp/console.out.

lsdisp

Lists the displays and the default display currently available on the system.

chdisp

Changes the display used by the LFT subsystem.
chdisp -p gda1 : changes the default display permanently to gda1.


lsattr

Displays attribute characteristics and possible values of attributes for devices in the system.
lsattr -EHl sys0l sys0 : displays system attributes (realmem ...)
lsattr -EHl proc0 : displays the state, type and frequency of processor proc0.
lsattr -El rmt0 : lists the current attribute values for the tape device rmt0.
lsattr -El tty0 -a speed : lists the current value of the speed attribute for serial port tty0.


lsdev

Displays devices in the system and their characteristics.
Examples:
lsdev -P -H : lists the Predefined (supported) Devices (in the PdDv object class).
lsdev -C -H : lists the Customized (configured/defined) Devices (in the CuDv object class).
lsdev -C -c disk : lists all the PVs (class disk) in the system along with the status and location code.

listdgrp

Displays devices in a device class.
listdgrp disk : list the devices in the disk class.

getdev

Lists devices that match the specified criteria.
getdev type=proc_rspc : lists all devices of type proc_rspc.

getdgrp

Lists device classes that match the specified criteria.
getdgrp : display all device classes.

chdev

Changes a device's characteristics.
chdev -l hdisk2 -a pv=yes : assigns a PVID to hdisk2.


mkdev


Adds a device to the system.
mkdev -l hdisk2 : make the already defined disk device hdisk2 available to use.
mkdev -l hdisk1 -a pv=yes : makes an available disk a PV (assigning a PVID), if it does not already have one.
mkdev -c tty -t tty -s rs232 -p sa0 -w s1 -a login=enable -a term=ibm3151 : adds an ibm3151 RS232 terminal using adapter sa0 port s1 with login enabled.


rmdev

Removes a device from the system.
rmdev -l tty0 -d : removes the tty0 device definition from the CuDv object class (ODM).
rmdev -l hdisk1 : unconfigures PV hdisk1 and changes its state from available to defined (definition is not removed from the CuDv object class (ODM).