[ Bottom of Page | Previous Page | Next Page | Contents | Index | Library Home |
Legal |
Search ]
Installation Guide and Reference
Migration Installation
Migration is the default installation
method to move from AIX 4.2 and later to AIX 5.2.
Note: If you only want to install the next recommended
maintenance level of the operating system, use the SMIT update_all fast path or the install_all_updates command to update
the filesets currently installed. For more information on updating to the
next recommended maintenance level of AIX, see Optional Software Products and Service Updates.
During a migration, the installation process determines
which optional software products are installed on the existing version of
the operating system. Components from previous releases that have been replaced
by new software in AIX 5.2 are installed at the AIX 5.2 level.
Migration attempts to preserve all user configuration, while moving the
operating system to a new level of software. The following steps are taken
to achieve this objective:
- Save configuration files
- Prepare/remove old files
- Restore new files
- Remove unsupported or unnecessary filesets
- Migrate configuration data wherever possible
- Prepare VPD for install
- Update additional filesets
When performing a migration, the following occurs:
- All files in /usr/lib/drivers, /usr/lib/microcode, /usr/lib/methods and /dev are removed from the system, so software support for device drivers
must be reinstalled. Non-device software products and application remain on
the system, and should function correctly if they are among those files described
in Binary Compatibility Between Earlier Versions and AIX 5.2.
- The following software products are removed from the system:
- AIXwindows Interface Composer
- Remote Customer Services
- AIXwindows Development Environment
- Display PostScript functionality from AIXwindows Run-Time
Environment Extensions
- Performance Tools functionality from Extended Commands
- OpenGL and graPHIGS
- Xstation Manager
In most cases, user-configuration files from the previous version of a
product are saved when the new version is installed during a migration installation.
Binary Compatibility Between Earlier Versions and AIX 5.2
After a migration installation, you might notice filesets on the system
in the OBSOLETE state. Obsolete filesets were installed
by earlier versions of the operating system, but they remain on the current
system because the migration only replaced some, but not all, of the files
they contain. These filesets remain necessary for systems running mixed levels
of the operating system.
During a migration installation, the following filesets
are automatically included:
- Base operating system commands
- Base operating system libraries
- Base operating system curses/termcap
- Base operating system networking
- Base operating system directories/files (symlinks)
- Messages
- X11R3
- X11R4
- X11 fonts
All operating system applications based on AIX 4.2 and those intended
for use with POWER family, POWER2, and POWER-based models
run compatibly on AIX 5.2 without recompilation for those same models.
The only exceptions to this statement are applications using the following:
- Unsupported self-loadable kernel extensions
- Certain High-Function Terminal (HFT) control interfaces
- X11R3 input device interfaces
- CIO LAN device driver interface
- SCSI device configuration methods (IHVs)
- nlist subroutine interface
- DCE threads
- Applications compiled using POWER2 or POWER-based compiler
options, but executed on models other than POWER2 or POWER-based models.
Note: Any program that must run in all environments (POWER family, POWER2,
and POWER-based models 601 and higher) must be compiled using the common
mode of the compiler. Programs compiled to exploit POWER2 technology
must be run on POWER2 processors. Existing code need not be recompiled
to run.
A system using AIX 4.2 can operate as a server
system for client machines using AIX 5.2 with the following exceptions:
- Network installation of AIX 5.2 clients
- Service SNA or X.25 to AIX 5.2 clients
- Service HCON to AIX 5.2 clients
- Service CGE extensions of PEX and PEX-PHIGS
- Use of AIX 5.2 client installation formats
Font servers might be required on the AIX 5.2 clients
to reliably handle AIXwindows between server and client.
A system using AIX 5.2 might operate as a server
system for client machines using AIX 4.2 or later versions as long as
the necessary compatibility options are installed. All statements about binary
compatibility apply in this case. AIX 5.2 applications might not execute
reliably on AIX 4.2 systems using remote network mounts of AIX 5.2 file
system.
Migrating to AIX 5.2
Notes:
- The boot logical volume requires 12 MB of contiguous disk space. During
migrations, the inuextendblv command runs to ensure there are contiguous
partitions for hd5. If contiguous partitions are not present,
the inuextendblv command attempts to create them. If the partitions
are not present and the inuextendblv command fails to create them,
the migration is stopped.
- The settings in your bootlist are not migrated. After a migration, the
bootlist is set to the primary boot device.
Use the following steps to migrate your current version of
the operating system to the AIX 5.2 BOS:
Attention: This procedure requires shutting down and reinstalling the base
operating system. Whenever you reinstall any operating system, schedule your
downtime when it least impacts your workload to protect yourself from a possible
loss of data or functionality. Before you perform a migration installation,
ensure you have reliable backups of your data and any customized applications
or volume groups. For instructions on how to create a system backup, refer
to
Creating System Backups.
Step 1. Complete the Prerequisites
Before starting the migration, complete the following prerequisites:
- All requisite hardware, including any external devices (such as tape,
CD, or DVD-ROM drives), must be physically connected. If you need further
information, refer to the hardware documentation that accompanied your system.
- Before migrating your BOS to AIX 5.2, ensure
that the root user has a primary authentication method of SYSTEM. You can check this condition by typing the following command:
# lsuser -a auth1 root
Change the value, if needed, by typing
the following command:
# chuser auth1=SYSTEM root
- Before you begin the installation, other users who have access to your
system must be logged off.
- Verify that your applications runs on AIX 5.2. Also, check if your
applications are binary-compatible with AIX 5.2. If your system is an
application server, verify that there are no licensing issues. Refer to your
application documentation or provider to verify on which levels of AIX your
applications are supported and licensed. You can also check the AIX application
availability guide at the following Web address: http://www-1.ibm.com/servers/aix/products/ibmsw/list/
- Verify that all currently installed software is correctly entered in the
Software Vital Product Database (SWVPD), by using the lppchk command.
To verify that all filesets have all required requisites and are completely
installed, type the following:
# lppchk -v
- Check that your hardware microcode is up-to-date.
- All requisite hardware, including any external devices (such as tape drives
or CD/DVD-ROM drives), must be physically connected and powered on. If you
need further information, refer to the hardware documentation that accompanied
your system.
- Use the errpt command to generate an error report from entries
in the system error log. To display a complete detailed report, type the following:
# errpt -a
- There must be adequate disk space and memory available. AIX 5.2 requires
128 MB of memory and 2.2 GB of physical disk space. For additional release
information, see the AIX 5.2 Release Notes.
- Make a backup copy of your system software and data. For instructions
on how to create a system backup, refer to the Creating
System Backups.
Step 2. Prepare Your System for Installation
Prepare for migrating to the AIX 5.2 BOS by doing the following:
- Insert the AIX Volume 1 CD into the CD-ROM
device.
- Shut down your system. If your machine is currently running, power it
off now by following these steps:
- Log in as the root user.
- Type the following command:
# shutdown -F
- If your system does not automatically power off, place the power switch
in the Off (0) position.
Attention: You must not turn on the system unit
until instructed to do so in Step 3. Boot from Your Installation Media.
- Turn on all attached external devices. These include the
following:
- Terminals
- CD-ROM or DVD-ROM drives
- Tape drives
- Monitors
- External disk drives
Turning on the external devices first is necessary so the system
unit can identify each peripheral device during the startup (boot) process.
Step 3. Boot from Your Installation Media
Notes:
- If you are using an ASCII console that was not defined in your previous
system, complete Step 3. Set Up an ASCII Terminal before proceeding.
The following steps migrate your current version of the operating system
to AIX 5.2:
- Turn the system unit power switch from Off (0) to On (|).
- When the system beeps twice, press F5 on the keyboard (or 5 on
an ASCII terminal). If you have a graphics display, you see the keyboard icon
on the screen when the beeps occur. If you have an ASCII terminal (also called
a tty terminal), you see the word keyboard when the beeps occur.
Note
If your system does not boot using the F5 key (or the 5 key
on an ASCII terminal), refer to your hardware documentation for information
about how to boot your system from an AIX product CD.
The system begins booting from the installation media.
- If your system has an LED display, the three-digit LED should
display c31.
If you have more than one console,
each might display a screen that directs you to press a key to identify your
system console. A different key is specified for each console displaying
this screen. If this screen displays, press the specified key only on the device to be used as the system console. (The system console
is the keyboard and display device used for installation and system administration.)
Press a key on one console only.
A screen displays, asking you to select a language
to be used for installation instructions.
- Select the language you prefer to use for installation instructions.
- When the Welcome to Base Operating System Installation and
Maintenance screen displays, either begin the migration immediately by typing 1 to select Start Install Now with Default Settings, or verify
the installation and system settings by typing 2 to select Change/Show Installation Settings and Install. If you want to change
any settings, follow the procedure in Step 5. Verifying or Changing the Installation Settings.
Notes:
- You should not have to change settings simply to select the migration
installation method. If a previous version of the operating system exists,
the installation method defaults to migration.
- The available installation methods vary, depending on the version of the
operating system that is currently installed (before migration). For information
on the BOS installation methods, refer to Introduction to Base Operating System Installation. For
information on the installation options available for a migration installations,
refer to Installation Options.
- Verify the selections in the Migration Installation Summary screen and
press Enter.
- Confirm the migration installation process in the Migration Confirmation
screen and press Enter to begin the migration installation.
Step 4. Finish the BOS Migration
After prompting for confirmation, the installation
process begins. The Installing Base Operating System screen displays.
As the installation progresses, the numbers increment
in the fields that show percentage complete and elapsed time to indicate the
installation status. After the base run-time environment is installed, status
information displays about other software that is being installed. After the
BOS installation is complete, the system automatically reboots.
After the system has restarted, you are prompted to configure your installation
of the BOS. Go to Configuring the Operating System for information on the configuration
process.
Note: If there is not enough space to migrate
all of the usually migrated software, a collection of software called a Migration
Bundle is available when you install additional software later. You must create
additional disk space on the machine on which you want to install, and then
you can run smit update_all to complete the installation,
during which the Migration Bundle is installed.
If you are not doing the
installation from a graphics console, a Graphics_Startup bundle is created.
Refer to Installing Optional Software Products and Service Updates for more information about installing
software bundles and for information on migrating or installing optional software
products. Maintaining Optional Software Products and Service Updates describes how to remove software from the
system to release disk space.
- For additional release information, see the AIX 5.2 Release
Notes.
- For late-breaking information, which might include information on the
configuration process and installed software, refer to readme files. For information
on how to view readme files, see Viewing Readme Files.
- For information on installing optional software, refer to Installing Optional Software Products and Service Updates.
[ Top of Page | Previous Page | Next Page | Contents | Index | Library Home |
Legal |
Search ]