Migration is the default installation method to move from AIX 3.2 or any version of AIX Version 4 of the operating system to AIX 5.1.
Note: If you only want to install the next maintenance level of the operating system, see Chapter 4, Optional Software Products and Service Updates, or use the smit update_all SMIT fast path to update the filesets currently installed.
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.1 are installed at the AIX 5.1 level.
When migrating from AIX 3.2, the following occurs:
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.
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:
All operating system applications based on AIX 3.2 and those intended for use with POWER family, POWER2, and POWER-based models run compatibly on AIX 5.1 without recompilation for those same models. The only exceptions to this statement are applications using:
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.
Applications created on a system using AIX 5.1 might not function reliably on a system using AIX Version 3. Applications must have been created using the operating system's shared libraries for these statements to apply.
A system using AIX 3.2 can operate as a server system for client machines using AIX 5.1 with the following exceptions:
Font servers might be required on the AIX 5.1 clients to reliably handle AIXwindows between server and client.
A system using AIX 5.1 might operate as a server system for client machines using AIX 3.2 or later versions as long as the necessary compatibility options are installed. All statements about binary compatibility apply in this case. AIX 5.1 applications might not execute reliably on AIX Version 3 systems using remote network mounts of AIX 5.1 file system.
Use the following steps to migrate your current version of the operating system to the AIX 5.1 BOS:
Before starting the migration, complete the following prerequisites:
lsuser -a auth1 root
Change the value, if needed, by typing the following command:
chuser auth1=SYSTEM root
Prepare for migrating to the AIX 5.1 BOS by doing the following:
Attention: You must not turn on the system unit until instructed to do so in Step 3. Booting from Your Installation Media.
Turning on the external devices first is necessary so the system unit can identify each peripheral device during the startup (boot) process.
Note: If you are using an ASCII console that was not defined in your previous system, complete Step 3. Setting Up with an ASCII Terminal before proceeding.
The following steps migrate your current version of the operating system to AIX 5.1.
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.
- 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).
- If you only want to install the next maintenance level of AIX, see Installing Optional Software Products and Service Updates. You can also use the following SMIT fast path to update existing filesets:
After prompting for confirmation, the installation process begins. If the system key is present and is not already in the Normal position, turn the system key to the Normal position when you are prompted with the following message:
Turn the system key to the NORMAL position.
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 Chapter 3, 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 will be 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 will be 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 free up disk space.
Consider the following when you are migrating network software:
Configuration files are saved in
/lpp/save.config/etc. The file from the previous
release is named filename.old, and the shipped file is named
filename.new. For example, when
/etc/rc.tcpip is migrated:
|/etc/rc.tcpip||is upgraded and your configuration information is saved.|
|/lpp/save.config/etc/rc.tcpip.old||is the original rc.tcpip file (with your configuration changes).|
|/lpp/save.config/etc/rc.tcpip.new||is the version shipped with AIX 5.1 (without your configuration changes).|
The following files are migrated:
All the previously defined services are retained. The AIX 5.1 /etc/services file contains all the defined services from the Request for Comment (RFC) and Internet Engineering Task Force (IETF) standards document. Where a conflict exists between a service you have previously defined and a globally defined service (from an RFC), your service is retained and the official one is commented out.
In most cases, your TCP/IP configuration migrates successfully. If you have made substantial changes to any of the following files, check that everything you changed still works correctly after migration is complete.
The /etc/rc.nfs and /var/yp/Makefile files are not migrated. The old files are saved in /lpp/save.config/etc/rc.nfs and /lpp/save.config/var/yp/Makefile. You must configure your Network Information Service (NIS) domain name before an NIS client will work.
For NIS servers, the NIS databases are unchanged. You must reconfigure the NIS domain and restore any changes you previously made to rc.nfs and the Makefile because rc.nfs and Makefile are replaced. The old files are saved in /lpp/save.config with their corresponding path names. The user and group information is retained because the passwd and group files are not changed in a migration installation.