AIX Version 7.1 Release Notes

Contents

AIX Version 7.1 Release Notes

Read this before installation

Note: This software may contain errors that could result in critical business impact. It is highly recommended that you install the latest available fixes prior to using this software. Fixes can be obtained from IBM® System p® support at the following Web site:
http://www-933.ibm.com/eserver/support/fixes/fixcentral

These Release Notes® support AIX® Version 7.1.

The AIX Version 7.1 Release Notes include information that helps you install AIX Version 7.1. To view the most current version of the Release Notes, go to the online Release Notes in the AIX Information Center at the following Web site:
http://publib.boulder.ibm.com/infocenter/aix/v7r1/index.jsp?topic=/com.ibm.aix.ntl/releasenotes_kickoff.htm

Installation tips

The latest installation hints and tips are available from the IBM Subscription Service for UNIX servers at:
http://www14.software.ibm.com/webapp/set2/subscriptions/pqvcmjd
These tips might contain information that are critical for successful installation of this software.

Software License Agreements

There are instances where the Software Licence Agreements (SLA) might not be displayed correctly. In this event, the License Agreements can be viewed in all languages at the following Web site:
http://www-03.ibm.com/software/sla/sladb.nsf

Software Maintenance Agreement

In AIX Version 7.1, a separate Software Maintenance Agreement (SWMA) acceptance window displays during installation immediately after the license acceptance window. The response to the SWMA acceptance (accept or decline) is stored on the system, and either response allows the installation to proceed, unlike license acceptance which requires an accept to proceed.

The SWMA acceptance window is displayed during a New Overwrite or Preservation installation from base CD media.

For base CD media New Overwrite or Preservation installations, if a non-prompted installation is desired, the ACCEPT_SWMA field in the control_flow stanza of the bosinst.data file should be set to yes (to accept the SMWA terms) or no (to decline the SWMA terms). The ACCEPT_SWMA field is set to blank by default.

For NIM installations, if licenses have been accepted either from the choices made when initializing the installation, or using the ACCEPT_LICENSES field in a customized bosinst.data file, then this will constitute SWMA acceptance.

Service

Fixes and problem-solving databases

You can download AIX fixes and search technical databases (including "APARS" and "Tips for AIX administrators"), from the following IBM eServer™ Support Web site:
http://www-933.ibm.com/eserver/support/fixes/fixcentral

Security Advisories

Security subscription services are available at the following My Notifications Web site:
https://www.ibm.com/systems/support/myview/subscription/css.wss/folders?methodName=listMyFolders
After you subscribe to the System p AIX security advisories, you will receive the advisories by email as soon as they are published. You can also view AIX security advisories at the following Web site:
http://www14.software.ibm.com/webapp/set2/subscriptions/pqvcmjd

System requirements

Review the following information to determine the minimum and recommended system requirements needed to run AIX Version 7.1.

Required hardware

Only 64-bit Common Hardware Reference Platform (CHRP) machines running selected PowerPC® 970, POWER4, POWER5, POWER6®, and POWER7® processors that implement the POWER® architecture Platform Requirements (PAPR) are supported.

To see if you have a supported machine, log into the machine as the root user, and run the following command:
prtconf | grep 'Processor Type'
Note: RS64, POWER3, and 604 processors, 32-bit kernel, 32-bit kernel extensions, and 32-bit device drivers are no longer supported.

Firmware

Some AIX systems might not boot from CD-ROM

Some AIX systems might not boot from CD-ROM because of firmware issues. To determine if your system will be affected by this problem, perform the following steps before you migrate or install a running AIX 4.3, AIX 5.1, or AIX 5.2 system:
  1. At the command prompt, type the following:
    lscfg -vl cd*
  2. Examine the data that is returned.

    If Part Number is 04N2964 and ROS Level and ID is less than or equal to 1_04 (for example, 1_02, 1_01, or 1_00), contact your local service representative. Tell your service representative that your system requires the CD-ROM firmware upgrade that is described in RETAIN® TIP H1332.

    If the data returned does not match the data described in the preceding paragraph, your system is not affected by this problem.

Minimum firmware levels required for AIX 7.1

The following table shows minimum system firmware levels required before installing or upgrading your system to AIX 7.1.
Model Number Product Name Minimum Firmware Level
7028-6C4 pSeries® 630 Model 6C4 3R041029
7028-6E4 pSeries 630 Model 6E4 3R041029
7029-6C3 pSeries 615 Model 6C3 3F041029
7029-6E3 pSeries 615 Model 6E3 3F041029
7038-6M2 pSeries 650 Model 6M2 3K041029
7039-651 pSeries 655 Model 651 3J041029
7040-671 pSeries 670 Model 671 3H041029
7040-681 pSeries 690 Model 681 3H041029
9114-275 IntelliStation® POWER Model 275 3F041029
Firmware updates are available at the following Web site:
http:/www14.software.ibm.com/webapp/set2/firmware/gjsn
If you experience problems booting your POWER4 system after updating AIX or firmware, to verify and correct the value of the real-base firmware variable, perform the following steps:
  1. Go to the open firmware prompt when the system is booting by typing 8 when a beep is heard or the banner displays. If applicable, the Hardware Management Console (HMC) can also be used to set to boot to the SMS menu. From the SMS menu, type 0 and go to the open firmware prompt.
  2. At the open firmware prompt, type:
    printenv real-base
    The following is a sample display:
    -------------- Partition: common -------- Signature: 0x70 ---------------
    real-base                2000000             c00000 
    The value following real-base must be c00000. If any value other than c00000 displays, run the following command:
    setenv real-base c00000
  3. After updating the real-base variable, reboot your system using the power switch.

Firmware upgrade required to support an alternate boot device

The requirement of upgrading firmware when installing or booting AIX Version 7.1 in the scenarios described in this section applies only to the systems listed in the table included at the end of this section.

Installation

Some systems might encounter installation problems when you are installing AIX Version 7.1 on a system that is currently installed with a earlier version of AIX or when you are installing an earlier version of AIX on a system currently installed with AIX Version 7.1.

A firmware upgrade is required to support the following installation scenarios:
  1. When an installation device is specified using the SMS menus or the Open Firmware command-line and the specified device is not the first available device in the AIX bootlist.
    Note: SMS menus differ, depending on the system. On some systems, the installation device is specified under the Multiboot menus. On other systems, the installation device is specified under the Select Boot Options menus.
  2. When the F5 key is selected during boot, which is the fast path to install from the CD device, and the CD device is not the first available device in the AIX bootlist.
No firmware upgrade is required if no installation device is specified in the SMS menus or the Open Firmware prompt or if the specified installation device is the first available device in the AIX bootlist.

I/O devices IPL limitation

Because of a firmware memory size limitation, only I/O devices in the first 144 I/O slots assigned to a logical partition or single system image partition can be used as an IPL (boot) source.

You can use the HMC to identify which devices are in the first 144 I/O slots by doing the following:
  1. Select Partition Properties>Hardware>I/O.
  2. Click the Bus column to sort the I/O devices in ascending order.

    The first 144 I/O devices in the sorted list are in the bootable adapter slots.

If you are using a partition or single-system image partition with more than 144 assigned I/O slots, the following scenarios and their results and resolutions are possible.

Table 1. Scenarios for partitions with more than 144 assigned I/O slots
Scenario Result Resolution
Attempting to boot from a device beyond the first 144 I/O slots for installation or diagnostic purposes. The device is not selectable as a boot source from the SMS menus. Use a device in the first 144 I/O slots.
Booting from a device in the first 144 I/O slots, and then attempt to select a target installation device in a slot beyond the first 144 I/O slots. The boot will succeed to the installation menus, but devices beyond the first 144 I/O slots will not be listed as bootable installation targets in the AIX menus. Select a device that is available and marked as bootable.
Using an MPIO configuration where one adapter is in the first 144 I/O slots and another adapter is in a slot beyond the first 144 I/O slots. Both adapters are present at boot time. The boot will succeed to the installation menus, and the device will be listed as bootable in AIX installation menus. The installation will proceed, but it will fail with the bootlist command failure "unable to set bootpath for all paths." Use a device in the first 144 I/O slots for all paths.
Using DLPAR to add an adapter in a slot beyond the first 144 I/O slots, and then attempting to run the alt_disk_install command for the newly added device. The device will not be listed as bootable. Use a device in the first 144 I/O slots.
Using DLPAR to add an adapter in a slot beyond the first 144 I/O slots, and using the bootlist command to add the device as a bootable device (for example, by dynamically adding a redundant path to a current boot device or setting up for a network boot). Then removing the original adapter and rebooting. The bootlist command succeeds, but the boot fails from the specified device, and AIX will not receive control. Use a device in the first 144 I/O slots.
Using DLPAR to add an adapter whose probe order will make it displace a current bootable device, and then rebooting. The boot fails, and AIX will not receive control. Move the boot device to one of the first 144 I/O slots or remove the previously added device.
Selecting a device in a slot beyond the first 144 I/O slots as a dump device for a firmware-assisted dump. The sysdumpdev command does not allow devices in slots beyond the first 144 I/O slots to be selected as firmware-assisted dump storage devices. An error occurs during the firmware-assisted dump configuration, and a traditional AIX dump automatically becomes available. Use a device in the first 144 I/O slots for firmware-assisted dumps.
Using DLPAR to add an adapter whose probe order will make it displace a currently valid firmware-assisted dump target device, and then rebooting after the dump. The firmware-assisted dump process fails during the boot process and displays an error message. The traditional AIX dump still runs to retrieve the dump image. Avoid displacing the selected firmware-assisted dump target device or reconfiguring the sysdumpdev command for the firmware-assisted dump target device selection, and specify a device within the first 144 I/O slots.
Using DLPAR to add an adapter whose probe order will make it displace a currently valid firmware-assisted dump target device, and then rebooting. The sysdumpdev command does not allow devices in slots beyond the first 144 I/O slots to be selected as firmware-assisted dump storage devices. An error occurs during the firmware-assisted dump configuration, and a traditional AIX dump automatically becomes available. Use a device in the first 144 I/O slots for firmware-assisted dumps.

Memory requirements

AIX Version 7.1 minimum current memory requirements vary, based on the configuration.

A general rule for a minimum current memory requirement for AIX 7.1 is 512 MB. A smaller minimum current memory may support a configuration with a very small number of devices or a small maximum memory configuration.

AIX 7.1 requires the minimum current memory requirement to increase as the maximum memory configuration or the number of devices scales upward, or both. Larger maximum memory configurations or additional devices scale up the minimum current memory requirement. If the minimum memory requirement is not increased along with the maximum memory configuration, the partition hangs during the initial program load (IPL).

Host Ethernet Adapter memory requirements

Configurations containing a Host Ethernet Adapter (HEA) require more memory than the 512 MB minimum. Each logical HEA port that is configured requires an additional 102 MB of memory. The minimum memory requirement for configurations with one or more HEA ports configured, where n is the number of HEA ports, is 512MB + n*102MB.

IBM Tivoli Directory Server memory requirements

IBM Tivoli® Directory Server Version 6.1 requires a minimum of 256 MB RAM for the Client and a minimum of 512 MB of RAM (1 GB or more is strongly recommended) for the Server. IBM Tivoli Directory Server (including the Client and the Server) requires about 160 MB of disk space.

IBM Tivoli Directory Server includes the DB2 Universal Database™ for AIX Version 9.1 Restricted Enterprise Server Edition. No previous versions of DB2® databases are supported. If you already have DB2 database installed, you need approximately 45 MB of disk space to create the empty database and start the server. DB2 database requires between 300 MB and 500 MB of disk space. Disk space required for data storage is dependent upon the number and size of database entries.

Your machine must be running on 64-bit hardware.

Your machine must be running a 64-bit kernel.

Paging space requirements

AIX Version 7.1 creates a 512 MB paging space (in the /dev/hd6 directory) for all new and complete overwrite installations.

Disk requirements

AIX Version 7.1 requires a minimum of 5 GB of physical disk space for a default installation that includes all devices, the Graphics bundle, and the System Management Client bundle.

The following measurements provide information about disk usage when you install AIX 7.1.

Disk requirements for AIX Version 7.1
Location Allocated (Used)
/ 196 MB (182 MB)
/usr 1952 MB (1777 MB)
/var 384 MB (267 MB)
/tmp 128 MB (2 MB)
/admin 128 MB (1 MB)
/opt 352 MB (183 MB)
/var/adm/ras/livedump 256 MB (1 MB)
Note:
  1. If the /tmp directory has less than 64 MB, it is increased to 64 MB during a migration installation so that the AIX Version 7.1 boot image is successfully created at the end of the migration.
  2. The boot logical volume is required to be 24 MB with the 610005. The pre-migration script in the usr/lpp/bos directory on your media or in your 7.1 NIM Shared Product Object Tree (SPOT) will check if you have adequate room. During the migration, hd5 will be increased if necessary. The logical partitions must be contiguous and within the first 4 GB of the disk.

You must format the SCSI disk properly before you install AIX on it. The AIX operating system requires the disk to be formatted to a sector size supported by the attached SCSI controller. All AIX SCSI controllers support 512 byte sector SCSI disks. The 522 byte sector SCSI disks are only supported when they are attached to SCSI RAID controllers. If the disk has been formatted for SCSI RAID, but is not attached to a SCSI RAID controller, the disk might not configure. If the disk does configure, it might be unreadable in the AIX environment. In some instances, the certify function and the format function in AIX diagnostics can be used to reformat the disk for the attached SCSI controller.

During a migration installation, if /opt exists only as a directory and has less than 3 MB of data, then a new /dev/hd10opt logical volume and /opt file system are created, and the data that existed in the /opt directory is moved to the new /opt file system.

If there is more than 3 MB of data in the /opt directory, then the new logical volume and file system are not created.

If any existing file system has a mount point in the /opt directory, or a mount point of /opt itself, the new logical volume and file system are not created.

Disk capacity

SAS RAID controllers and Fibre Channel controllers support attached arrays and disks with capacities which exceed 2 TB. The maximum supported capacity (beyond 2TB) is limited by either the attached storage subsystem or the upper level logical storage management.

For additional information about SAS RAID controllers, see the SAS RAID controller for AIX Web page.

For information about AIX capacity limitations for logical storage, see the Limitations for logical storage management Web page.

Installation, migration, upgrade, and configuration information

Installation

This section contains information about installing AIX 7.1 that supplements the information contained in AIX Version 7.1 Installation and migration. The installation guide is available online in the AIX Information Center.

To order these installation guides, contact your point of sale, or in the U.S., call IBM Customer Publication Support at 1-800-879-2755. Give the order number of the book you want to order.

To obtain AIX Version 7.1 installation hints and tips, visit the Subscription Service at the following Web site:
http://www14.software.ibm.com/webapp/set2/subscriptions/pqvcmjd

Installing AIX Version 7.1

The following methods can be used to install AIX Version 7.1:
  • Complete overwrite installation
  • Preservation installation
  • Migration installation
Note: After you install or migrate a system to AIX Version 7.1, you can install a lower level of AIX by restoring a system backup or by performing a new and complete overwrite with base media. Preservation installations from AIX Version 7.1 to a lower level of AIX are not supported.
Notes:
  1. The minimum size of the boot logical volume is 24 MB. If your current boot logical volume is 16 MB or less, the installation process tries to increase it. However, partitions in a boot logical volume must be contiguous, and within the first 4 GB on the disk. If your system does not have free space that meets these requirements, a message will indicate that there is not enough space to expand hd5 (the boot logical volume).
  2. A general rule for a minimum current memory requirement for AIX Version 7.1 is 512 MB.

To install AIX Version 7.1, boot your system from the product media, and follow the instructions in the AIX Version 7.1 Installation and migration in the AIX Information Center.

NIM installations with updated LPP_SOURCE

NIM installations using an LPP_SOURCE directory that contains base images from a prior release and that contains updates to the current release require that you use an image_data resource during operating system installations.

When you use an LPP_SOURCE directory that contains base images from a prior release and updates to the current release, create an image_data resource to use for any operating system installations. The SPOT must be updated with the updates added to the LPP_SOURCE directory, or a new SPOT must be created. In that SPOT, copy the image.template file found at <SPOT_LOCATION>/lpp/bosinst/image.template to a new location outside of the SPOT. Create a new NIM image_data resource that points to that location. Use that NIM image_data resource for all operating system installations.

Certain file systems have grown in size, and the default image.data file used during an operating system installation comes from the bos image in your LPP_SOURCE directory, which is the prior release image.data file.

New installation feature

You can select the edition of the operating system during the base operating system installation. The edition selected defines the signature file that is copied to the /usr/lpp/bos directory. The signature file is used by the IBM License Metric Tool (ILMT) to facilitate the licensing compliance. The selection choices for an operating system edition are express, standard, and enterprise. The default value is express. The edition value can be set during nonprompted NIM installations by using the INSTALL_EDITION field in the control_flow stanza of the bosinst_data NIM resource. The operating system edition can be modified by using the chedition command. Refer to the man pages for more details.

A new file system (/var/adm/ras/livedump) that saves the livedump output is created during base-operating-system installations. You can change the livedump file system attributes by using the optional livedump stanza in a customized bosinst.data file.

IBM Systems Director Common Agent

AIX Version 7.1 includes the IBM Systems Director Common Agent. It is installed as part of the System Management Client Software bundle which is part of the default install options.

When the AIX system is rebooted, the Director agent and the prerequisite processes for it, like the Pegasus CIM server, are automatically enabled. If you do not want to install or enable the Director agent, see the following information for the steps needed to stop, disable, and uninstall the Director agent.

To stop the Director agent, run the following commands:
/opt/ibm/director/agent/runtime/agent/bin/endpoint.sh stop
stopsrc -s platform_agent
To start the Director agent, run the following commands:
startsrc -s platform_agent
/opt/ibm/director/agent/runtime/agent/bin/endpoint.sh start
To permanently disable the Director agent, do the following:
  1. Comment out the following lines in /etc/inittab file:
    platform_agent:2:once:/usr/bin/startsrc -s platform_agent >/dev/null 2>&1
    Note: Comment out the following line only if you do not need the cimserver command to run other applications.
    cimservices:2:once:/usr/bin/startsrc -s cimsys >/dev/null 2>&1
  2. Run the following command:
    /opt/ibm/director/agent/runtime/agent/bin/endpoint.sh stop
  3. Run the following command:
    /opt/ibm/director/agent/runtime/nonstop/bin/installnonstop.sh -uninstallservice
To permanently uninstall the Director agent components and leave the file sets that might be used by other applications, run the following command:
/opt/ibm/director/bin/diruninstall
To uninstall the file sets that remain after you run the diruninstall command (if they are not required for other applications), do the following:
  • To uninstall Tivoli Guid, run the following command:
    installp -u tivoli.tivguid
  • To uninstall SMIS CIM providers, run the following command:
    installp -u sysmgt.cim.smisproviders*
  • To uninstall the remaining CIM providers, run the following command:
    installp -u sysmgt.cim.providers*
  • To uninstall the Pegasus CIM server, run the following command:
    installp -u sysmgt.cimserver.pegasus

For more information about IBM Systems Director 6.1, see the IBM Systems Director V6.1 Web page.

Disk format requirement

You cannot install AIX on an improperly formatted SCSI disk. AIX requires the disk to be formatted to a sector size supported by the attached SCSI controller. All AIX SCSI controllers support 512 byte sector SCSI disks. The 522 byte sector SCSI disks are only supported when they are attached to SCSI RAID controllers. If the disk has been formatted for SCSI RAID, but is not attached to a SCSI RAID controller, the disk might not configure. If the disk does configure, it might be unreadable in the AIX environment. In some instances, the certify function and the format function in AIX diagnostics can be used to reformat the disk for the attached SCSI controller.

Creating a bootable CD or DVD

You might want to create a CD or DVD that can be used to boot and perform maintenance on your system that matches your current level of AIX.

To create a bootable CD or DVD, run the following commands (where cdx is an attached CD or DVD writer). The bosinst.data file must be set for a prompted installation (PROMPT = yes).

Perform the following steps to create a boot-only disc:
  1. Create a file /etc/exclude.rootvg using an editor. For example, vi editor. Add the following line in it.
       ^./
  2. Run the following command.
       # mkcd -e -d /dev/cdx     # Where cdx is an attached cdwriter
         OR
       # mkcd -e -S              # Creates a CD image that can be
                                 # transferred to a system with a cdwriter
Notes:
  • The final mkcd command in the previous example makes an image that can be transferred to another system (AIX or other than AIX) for burning.
  • When a bootable disc is created, the boot image reflects the kernel that is currently running. If the current kernel is the 64-bit kernel, the disc's boot image is also 64-bit, and boots only 64-bit systems. If the current kernel is a 32-bit kernel, the disc's boot image is 32-bit, and it can boot both 32-bit and 64-bit systems.

Using the current kernel

The 32-bit systems cannot boot using a 64-bit kernel. Additionally, some configurations require the system to boot from the 64-bit kernel in order to install the operating system. To ensure that the backup works on the system it came from, the boot image is created to contain the kernel that was running when the backup was created.

Base Operating System installation options

The information in this section supplements the "Installation Options" chapter of the AIX Version 7.1 Installation and migration in the AIX Information Center.

In the Base Operating System installation menus, if there are more than 50 disks on the system, the disks are ordinarily grouped by adapter. However, for some types of disks, the grouping is slightly different:
SCSI disks
Disks may be grouped by adapter or SCSI bus
IBM TotalStorage DS4000®
Disks are grouped by disk array controller (DAC)

In each case, the user can select the adapter, SCSI bus, or DAC by name and see the associated disks. The physical location of the adapter, SCSI bus, or DAC is also displayed.

Installing AIX using the media device to install a partition with an HMC

The instructions for installing AIX using the media device to install a partition with an HMC have been changed to:

  1. Activate the partition, as follows:
    1. Insert the AIX Volume 1 CD or DVD into the media device of the managed system.
    2. Select the checkbox that corresponds to the partition you want installed.
    3. In the Operations menu in the lower window pane, select Activate.
    4. In the Activate window, click Advanced.
    5. For the Boot mode, select SMS.
    6. Click OK. Ensure that the appropriate partition profile is highlighted.
    7. Select the Open a terminal window or console session checkbox, and then click OK.
  2. In the SMS menu on the vterm, do the following:
    1. Press Enter to select 5. Select Boot Options.
      PowerPC Firmware
      Version SF220_001
      SMS 1.5 (c) Copyright IBM Corp. 2000, 2003  All rights reserved.
      -------------------------------------------------------------------------------
      Main Menu
      
      1. Select Language
      2. Setup Remote IPL (Initial Program Load)
      3. Change SCSI Settings
      4. Select Console
      5. Select Boot Options
      
      
      -------------------------------------------------------------------------------
      Navigation Keys:
      
      																X = eXit System Management Services
      -------------------------------------------------------------------------------
      Type the number of the menu item and press Enter or select Navigation Key: 5
    2. Press Enter to select 2. Select Boot Devices.
    3. Press Enter to select 1. Select 1st Boot Device.
    4. Press Enter to select 3. CD/DVD.
    5. Select the media type that corresponds to the media device and press Enter.
    6. Select the device number that corresponds to the media device and press Enter. The media device is now the first device in the Current® Boot Sequence list.
    7. Press the ESC key until you return to the Configure Boot Device Order menu.
    8. Press the x key to exit the SMS menu. Confirm that you want to exit SMS.
  3. Boot from the AIX Volume 1 CD or DVD, as follows:
    1. Select console and press Enter.
    2. Select language for BOS Installation menus, and press Enter to open the Welcome to Base Operating System Installation and Maintenance menu.
    3. Type 2 to select 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
  4. Verify or Change BOS Installation Settings, as follows:
    1. Type 1 in the Choice field to select the System Settings option.
    2. Type 1 for New and Complete Overwrite in the Choice field and press Enter.
      Note: The installation methods available depend on whether your disk has a previous version of AIX installed.
    3. When the Change Disk(s) screen displays, you can change the destination disk for the installation. If the default shown is correct, type 0 in the Choice field and press Enter. To change the destination disk, do the following:
      1. Type the number for each disk you choose in the Choice field and press Enter. Do not press Enter a final time until you have finished selecting all disks. If you must deselect a disk, type its number a second time and press Enter.
      2. When you have finished selecting the disks, type 0 in the Choice field and press Enter. The Installation and Settings screen displays with the selected disks listed under System Settings.
    4. If needed, change the primary language environment. Use the following steps to change the primary language used by this installation to select the language and cultural convention you want to use.
      Note: Changes to the primary language environment do not take effect until after the BOS installation has completed and your system is rebooted.
      1. Type 2 in the Choice field on the Installation and Settings screen to select the Primary Language Environment® Settings option.
      2. Select the appropriate set of cultural convention, language, and keyboard options. Most of the options are a predefined combination, however, you can define your own combination of options.
        • To choose a predefined Primary Language Environment, type that number in the Choice field and press Enter.
        • To configure your own primary language environment, do the following:
          1. Select MORE CHOICES.
          2. Select Create Your Own Combination.
          3. When the Set Primary Cultural Convention screen displays, type the number in the Choice field that corresponds to the cultural convention of your choice and press Enter.
          4. When the Set Primary Language screen displays, type the number in the Choice field that corresponds to your choice for the primary language and press Enter.
          5. When the Set Keyboard screen displays, type the number in the Choice field that corresponds to the keyboard attached to the system and press Enter.
    5. After you have made all of your selections, verify that the selections are correct. Press Enter to confirm your selections and to begin the BOS installation. The system automatically reboots after installation is complete.
  5. Complete the BOS Installation, as follows:
    1. Type vt100 as the terminal type.
                                  Set Terminal Type
      The terminal is not properly initialized.  Please enter a terminal type
      and press Enter.  Some terminal types are not supported in
      non-English languages.
      
           ibm3101          tvi912          vt330
           ibm3151          tvi920          vt340
           ibm3161          tvi925          wyse30
           ibm3162          tvi950          wyse50
           ibm3163          vs100           wyse60
           ibm3164          vt100           wyse100
           ibmpc            vt320           wyse350
           lft              sun
      
                            +-----------------------Messages------------------------
                            | If the next screen is unreadable, press Break (Ctrl-c)
          88  Help ?        | to return to this screen.
          99  Exit          |
                            |
      >>> Choice []: vt100
    2. In the License Agreement menu, select Accept License Agreements.
    3. Select yes to ACCEPT Installed License Agreements.
    4. Press F10 (or Esc+0) to exit the License Agreement menu.
    5. In the Installation Assistant main menu, select Set Date and Time.
                                   Installation Assistant
      
      Move cursor to desired item and press Enter.
      
        Set Date and Time
        Set root Password
        Configure Network Communications
        Install Software Applications
        Using SMIT (information only)
      
      
      F1=Help             F2=Refresh          F3=Cancel           F8=Image
      F9=Shell            F10=Exit            Enter=Do
    6. Set the correct date, time, and time zone. Press the F3 (or Esc+3) key to return to the Installation Assistant main menu.
    7. Select Set root Password. Set a root password for the partition.
    8. Select Configure Network Communications.
    9. Select TCP/IP Startup.
    10. Select from the Available Network Interfaces and press Enter.
    11. Enter the appropriate network information in the Minimum Configuration and Startup menu and press Enter. Use the F3 (or Esc+3) key to return to the Installation Assistant main menu.
    12. Exit the Installation Assistant by pressing F10 (or Esc+0).
    13. The vterm window displays a login prompt.

Secure by Default installation

A DVD installation of AIX 7.1 with the Secure by Default (SbD) option prompts for the Expansion Pack CDs after the base operating system is installed. This step is necessary to install SSH and SSL packages for secure remote system accessibility. If this step is skipped, the system will not be network accessible because SbD erases binaries that use clear text passwords (for example, telnet, and ftp-similar binaries). If the SbD installation option is selected through NIM, the system administrator should ensure that the NIM lpp_source has the openssh and openssl images in place.

Network Installation Management

Network Installation Management (NIM) includes a readme file that is installed with the NIM Master bos.sysmgt.nim.master file set. The path name of the file is /usr/lpp/bos.sysmgt/nim/README. The readme file contains additional information about the AIX Version 7.1 NIM product and includes the following topics:
  • Web-based System Manager NIM May Have Problems Installing SW on Client Machines
  • Restrictions on Customize Operation for RPM Packages
  • Steps Necessary For Adding GNOME -or- KDE Desktop Support

When Live Partition Mobility (LPM) is used to migrate a machine (that is, move a machine from one physical server to another) and the machine is defined as a NIM client, the NIM administrator must update the cupid attribute for the NIM client to reflect the new hardware value after the LPM migration completes. To update the cupid attribute, do the following:

  1. On the NIM client, acquire the new cupid ID by running the following command:
    uname -a
  2. On the NIM master, run the following command:
    nim -o change -a cupid+<cupid> <client>
Note: The OS_install network installer no longer supports the installation of Linux due to the removal of Cluster Systems Management (CSM) support in the AIX operating system.

Installing with an updated LPP_SOURCE

NIM installations using an LPP_SOURCE directory that contains base images from a prior release and that contains updates to the current release require that you use an image_data resource during operating system installations.

When you use an LPP_SOURCE directory that contains base images from a prior release and updates to the current release, create an image_data resource to use for any operating system installations. The SPOT must be updated with the updates added to the LPP_SOURCE directory, or a new SPOT must be created. In that SPOT, copy the image.template file found at <SPOT_LOCATION>/lpp/bosinst/image.template to a new location outside of the SPOT. Create a new NIM image_data resource that points to that location. Use that NIM image_data resource for all operating system installations.

Certain file systems have grown in size, and the default image.data file used during an operating system installation comes from the bos image in your LPP_SOURCE directory, which is the prior release image.data file.

IBM SDK for AIX, Java Technology Edition

IBM software development kit (SDK) for AIX, Java™ Technology Edition is released in JavaV.x file sets, where V represents the version of Java, such as Java6, and x is the individual file set, such as Java5.sdk. To obtain the latest update, complete the following steps:
  1. Go to the developerWorks® website at http://www.ibm.com/developerworks/java/jdk/aix/.
  2. Click Downloads, User Guides, and Service information.
  3. Click Fix Info from the respective Java version column.

IBM Tivoli Directory Server

You must purchase a full-use license through Passport Advantage® for any other use of the IBM Tivoli Directory Server other than authentication and AIX user registry.

The Passport Advantage package includes a White Pages application. The Passport Advantage license entitles you to use and to receive support for the IBM Tivoli Directory Server Proxy server and the White Pages application. You can install and use IBM Tivoli Directory Server only in association with your licensed use of AIX operating system functions.

Other installation information

Installation packaging formats

AIX Version 7.1 supports the following installation-packaging formats:
  • installp, AIX system installation command and packaging format
  • RPM, a Linux installation command and packaging format
  • ISMP, InstallShield Multi-Platform packaging format

With the geninstall command, you can list and install packages from media that contains installation images packaged in any of the listed formats. The geninstall and gencopy commands recognize the non-installp installation formats and either call the appropriate installers or copy the images, respectively.

The AIX Version 7.1 product media contains installp packages and RPM packages that are installed during a BOS installation. The installp packages are located in the following path, where mount_point is the mount point:
/mount_point/installp/ppc
The RPM packages are located in the following path, where mount_point is the mount point:
/mount_point/RPMS/ppc
The ISMP packages are located in the following path, where mount_point is the mount point:
/mount_point/ismp/ppc

The installp, bffcreate, geninstall, gencopy and nim commands recognize this media structure.

For more information about software packaging, see the Software Product Packaging Concepts section in the AIX Version 7.1 Installation and migration in the AIX Information Center.

Troubleshooting problems with installation from mksysb backup

Check that you have sufficient free blocks in the file systems to write temporary files. Check that each file system has at least 500 blocks free when the mksysb backup image is made. The system needs work space in each file system when installing from a mksysb backup image.
Note: Depending on the type of data or files in the file system, you might need additional blocks free. For example, if the file system has a lot of small files, an extra 4 KB is automatically allocated to allow for metadata expansion.

Migration

You can do an operating system migration to AIX 7.1 from any level of AIX version 5 or 6, on a system that supports 7.1 boot. Installing any new level of AIX requires more disk space than previous levels. Read the Disk Requirements in Chapter 2 for the disk requirements for a basic installation and ensure that you have free space in the file systems, or that you have free partitions in the rootvg. Migrating will require slightly more free space than a basic installation.

Maximum size of boot image increased

For AIX Version 7.1, the maximum size of the boot image has changed from the previous value used for AIX 5.2 (and earlier releases) value of 11,984 KB (12 MB minus 16 KB) to 31,984 KB (32 MB minus 16 KB). The size of the boot logical volume has increased from 16 MB to 20 MB.

Replacements for the vmtune and schedtune commands

When you migrate a system from a previous version of AIX to AIX Version 5.2, AIX Version 5.3, AIX Version 6.1, or AIX Version 7.1 it is automatically set to run in compatibility mode (pre520tune mode). Compatibility scripts that replace the vmtune and schedtune commands are included with AIX 5.2, which means that the previous behavior of the tuning commands is preserved to a large extent after a migration.

However, when you migrate to AIX 5.3, the pre520tune compatibility mode applies only to settings that were configured with the no and nfso commands because the vmtune and schedtune commands are no longer included. The compatibility mode is meant to be a temporary help in the migration to the new tuning framework and should normally not be used with releases after AIX 5.2.

xlC runtime software

When you migrate from an AIX 5L™ operating system to an AIX 7.1 operating system, the xlC.aix50.rte file set is replaced by the xlC.aix61.rte file set. If you upgraded the xlC.aix50.rte file set after you installed your system, the migration may replace your upgraded version with a downlevel version. Before you migrate to an AIX 7.1 operating system, save the level of your xlC.aix50.rte file set. After the migration is complete, compare your saved level of the xlC.aix50.rte file set with the xlC.aix61.rte file set. If the changes that you made to your level of the xlC.aix50.rte file set are not in the xlC.aix61.rte file set, upgrade the xlC.aix61.rte file set.

KDE desktop

If the CDE and KDE desktops are both installed on a system migrated from AIX 5.x to AIX Version 7.1, the KDE desktop might not start from the CDE login. To fix this problem, remove the following CDE startup information from the /etc/inittab file:
dt:2:wait:/etc/rc.dt
Note: You must have root user authority to remove this CDE startup information.
Do not delete the following KDE entry from the /etc/inittab file:
kdm:2:once:/opt/freeware/kde/bin/kdm

Thin Servers

If you migrate any previous version of the AIX Common Operating System Image (COSI) and associated AIX Thin Servers to the AIX Version 7.1, it is recommended that you delete any dump device associated with the migrated Thin Servers and re-create the Thin Servers.

Additionally, you must install the devices.tmiscsw.rte file set on the NIM master for the AIX Version 7.1 Thin Server to create a dump device.

pmtoolkit file set

The Performance Monitoring API is contained in the bos.pmapi file set. A beta version of the same code was made available to selected customers, and also through alphaWorks®, under the name pmtoolkit.

When you are migrating from AIX with the beta file set installed, you must uninstall the pmtoolkit file set and reboot the machine before you install the bos.pmapi file set. If you do not, the machine will fail to boot when you attempt to load the pmtoolkit file set's kernel extension.

Verify that the pmtoolkit file set is installed by typing the following at the command line:
lslpp -l pmtoolkit
  • If you get the following output:
    lslpp: 0504-132  fileset pmtoolkit not installed
    you can safely install the bos.pmapi file set.
  • If you get the following output:
      Fileset                      Level  State      Description         
      ----------------------------------------------------------------------------
    Path: /usr/lib/objrepos
      pmtoolkit                  1.3.1.6  COMMITTED  Performance Monitor Toolkit
                                                     1.3.1
    complete the following steps:
    1. Run the following command:
      installp -u pmtoolkit
    2. Reboot the machine. After the machine reboots, you can safely install the bos.pmapi file set.

Kerberos

All of the secure remote commands use the Kerberos Version 5 library and the GSSAPI library provided by IBM Network Authentication Service Version 1.4 that is located on the AIX Version 7.1 Expansion Pack DVD. However, you must install the krb5.client.rte file set that is located on the AIX Version 7.1 Expansion Pack DVD.

If you are migrating to AIX 7.1 with DVD media, and have Kerberos Version 5 installed, the installation scripts will prompt you to install the krb5.client.rte file set from the Expansion Pack. If you are migrating your operating system using NIM resources, add krb5 to your lpp_source. The secure remote commands support Kerberos clients and servers from both Native Kerberos 5 and DCE.

For more information, see "Understanding the Secure Rcmds" in Managing Communications and Networks in the AIX Information Center.

Multipath I/O (MPIO)

In AIX 7.1, the DS4K products are configured as Multipath I/O (MPIO) devices by default.

A DS4K product using the FCPARRAY driver may be migrated to the MPIO driver by using the following instructions, or all DS4K devices may be migrated by uninstalling the devices.fcp.disk.array.rte package and then running the cfgmgr command or rebooting.

The DS3K products are always configured as MPIO devices. There is no FCPARRAY support for these devices. The MPIO support for these devices removes the limitation of connecting only one adapter to each DS3/4K controller port.

Instructions to convert DS4000 disks from FCPARRAY to MPIO

The MPIO driver has been enhanced to support most DS4000 models. The MPIO driver allows more than two paths to be configured to the device, and this simplifies zoning and improves performance. For the DS4000 to operate correctly in an MPIO configuration, the following steps must be performed.

The following AIX releases and minimum service packs can be used to convert DS4000 disks from FCPARRAY to MPIO:
  • AIX 5.2 with the 5200-10 Technology Level and the 5200-10-04 Service Pack
  • AIX 5.3 with the 5300-06 Technology Level and the 5300-06-05 Service Pack
  • AIX 5.3 with the 5300-07 Technology Level and the 5300-07-02 Service Pack
  • AIX 6.1 with the 6100-00 Technology Level and the 6100-00-02 Service Pack
The following DS4000 models are supported by AIX MPIO:
  • 1722-600 = DS4300 = FAStT 600
  • 1742-900 = DS4500 = FAStT 900
  • 1814 = DS4700/DS4200
  • 1815 = DS4800

To convert DS4000 disks from FCPARRAY to MPIO, do the following:

  1. Change the NVSRAM settings on DS4000 storage used in the SAN (or direct attach) by doing the following:
    Note: If this step was previously performed, go to Step 2. However, if DS4000 firmware was updated, this step must be performed again.
    1. From the main Enterprise Management screen, highlight the subsystem you want to change.
    2. From the Tools menu, select Execute Script to open a Script Editor window.
    3. Enter the following:
      set controller [a] HostNVSRAMBYTE [0x06,0x27] = 0x8;
      set controller [b] HostNVSRAMBYTE [0x06,0x27] = 0x8;
    4. From the Tools menu, use the Script Editor to select Verify & Execute.
    5. Wait for the script to complete.
      Attention: Do not cancel the script operation.

      When the script completes, exit the Storage Manager.

  2. Install the MPIO_DS3_4K APAR/iFIX that is appropriate for the AIX release on the server, and then reboot the AIX server.
  3. Determine the DS4000 model or models that you are using on your AIX host by running the following commands, where X is the hdisk number for the DS4000 Array Disk type:
    lsdev –Cc disk | grep DS4K
    lscfg –vl hdiskX
    For example:
    # lsdev -Cc disk
    hdisk2 Available 0C-08-02 DS4K Disk Array Device
    
    # lscfg -vl hdisk2
    hdisk2 U787A.001.DPM0WY4-P1-C5-T1-W200800A0B81326B7L3000000000000 1742-900 (900) Disk Array Device
    
    				Manufacturer................IBM
    				Machine Type and Model......1742-900
    				ROS Level and ID............30393134
    				Serial Number...............
    				Device Specific.(Z0)........0000053245004032
    				Device Specific.(Z1)........
  4. Use the following table and the Machine Type and Model output from Step 3 to determine your DS4000 Array Disk type.
    Table 2. DS4000 Array Disk Cross Reference
    Machine Type-Model Array Disk Storage Server
    1722-600 DS4300 FAStT 600
    1742-900 DS4500 FAStT 900
    1814 DS4700/DS4200  
    1815 DS4800  
  5. Check the AIX systems driver support and state by running the following command:
    # ‘manage_disk_drivers'

    The output from this command displays the DS4000 devices that are supported by MPIO and RDAC, and indicates if they are currently configured for MPIO or RDAC enablement.

    For example:
    # manage_disk_drivers
    	1: DS4300: currently RDAC/fcparray; supported: RDAC/fcparray, MPIO
    	2: DS4500: currently RDAC/fcparray; supported: RDAC/fcparray, MPIO
    	3: DS4700/DS4200: currently RDAC/fcparray; supported: RDAC/fcparray, MPIO
    	4: DS4800: currently RDAC/fcparray; supported: RDAC/fcparray, MPIO
    Note: If the AIX system has more than one type of DS4XXX models attached, run the manage_disk_drivers command for each model type.

    In the example in Step 2 , hdisk2 is a DS4500. In the example in Step 5, DS4500 is currently enabled for RDAC/fcparray.

    To change the driver that manages the DS4000, run the following commands in order, where X in the first command is the number of the array disk stanza from the output of the manage_disk_drivers command. For example: for DS4700, enter # manage_disk_drivers – c 3; for DS4800, enter # manage_disk_drivers – c 4, etc.

    # manage_disk_drivers – c X

    To verify the change, answer Y when prompted.

    # bosboot –a
    # shutdown –Fr
  6. After the server reboots, all of the hdisk devices that were converted will be configured under the MPIO driver. All of the hdisks that are connected to DS4000 should be displayed as MPIO Other DS4K Array Device as indicated by the lsdev –Cc disk output.
  7. To verify that hdisks are mapped to the appropriate LUNs on DS4000, run the mpio_get_config –A command. This command is similar to the fget_config command for the RDAC driver. The mpio_get_config command is for informational purposes only; you cannot change the LUN ownership using this command.

Instructions to convert DS4000 disk driver from MPIO to FCPARRAY

The following AIX releases and minimum service packs can be used to convert the DS4000 driver from MPIO to FCPARRAY:
  • AIX 5.2 with the 5200-10 Technology Level and the 5200-10-04 Service Pack
  • AIX 5.3 with the 5300-06 Technology Level and the 5300-06-05 Service Pack
  • AIX 5.3 with the 5300-07 Technology Level and the 5300-07-02 Service Pack
  • AIX 6.1 with the 6100-00 Technology Level and the 6100-00-02 Service Pack

To convert the DS4000 driver from MPIO to FCPARRAY, do the following:

  1. Install the MPIO_DS3_4K APAR/iFIX that is appropriate for the AIX release on the server.
  2. Change the NVSRAM settings on DS4000 storage used in the SAN (or direct attach) by doing the following:
    Note: If this step was previously performed, go to Step 3. However, if DS4000 firmware was updated, this step must be performed again.
    1. From the main Enterprise Management screen, highlight the subsystem you want to change.
    2. From the Tools menu, select Execute Script to open a Script Editor window.
    3. Enter the following:
      set controller [a] HostNVSRAMBYTE [0x06,0x27] = 0;
      set controller [b] HostNVSRAMBYTE [0x06,0x27] = 0;
    4. From the Tools menu, use the Script Editor to select Verify & Execute.
    5. Wait for the script to complete.
      Attention: Do not cancel the script operation.

      When the script completes, exit the Storage Manager.

  3. To migrate from MPIO to RDAC, there must be no more than two connections between the server and the storage (one per controller). Verify that this requirement is met by verifying that there is a separate zone for each HBA and controller pair. Refer to the RDAC documentation for valid configuration details.
  4. After the installation completes successfully, reboot the system.
  5. Determine the DS4000 model or models that you are using on your AIX host by running the following command where X is the hdisk number for the DS4000 Array Disk type:
    lsdev –Cc disk | grep DS4K
    lscfg –vl hdiskX
    For example:
    # lsdev -Cc disk
    hdisk2 Available 0C-08-02 DS4K Disk Array Device
    
    # lscfg -vl hdisk2
    hdisk2 U787A.001.DPM0WY4-P1-C5-T1-W200800A0B81326B7L3000000000000 1742-900 (900) Disk Array Device
    
    				Manufacturer................IBM
    				Machine Type and Model......1742-900
    				ROS Level and ID............30393134
    				Serial Number...............
    				Device Specific.(Z0)........0000053245004032
    				Device Specific.(Z1)........
  6. Use the following table and the Machine Type and Model output from Step 5 to determine your DS4000 Array Disk type.
    Table 3. DS4000 Array Disk Cross Reference
    Machine Type-Model Array Disk Storage Server
    1722-600 DS4300 FAStT 600
    1742-900 DS4500 FAStT 900
    1814 DS4700/DS4200  
    1815 DS4800  
  7. Check the AIX systems driver support and state by running the following command:
    # ‘manage_disk_drivers'

    The output from this command displays the DS4000 devices that are supported by MPIO and RDAC, and indicates if they are currently configured for MPIO or RDAC enablement.

    For example:
    # manage_disk_drivers
    	1: DS4300: currently RDAC/fcparray; supported: RDAC/fcparray, MPIO
    	2: DS4500: currently RDAC/fcparray; supported: RDAC/fcparray, MPIO
    	3: DS4700/DS4200: currently RDAC/fcparray; supported: RDAC/fcparray, MPIO
    	4: DS4800: currently RDAC/fcparray; supported: RDAC/fcparray, MPIO
    Note: If the AIX system has more than one type of DS4XXX models attached, run the manage_disk_drivers command for each model type.

    In the example in Step 5 , hdisk2 is a DS4500. In the example in Step 7, DS4500 is currently enabled for RDAC/fcparray.

    To change the driver that manages the DS4000, run the following commands in order, where X in the first command is the number of the array disk stanza from the output of the manage_disk_drivers command. For example: for DS4700, you would enter # manage_disk_drivers – c 3; for DS4800, you would enter # manage_disk_drivers – c 4, etc.

    # manage_disk_drivers – c X

    To verify the change, answer Y when prompted

    # bosboot –a
    # shutdown –Fr
  8. After the server reboots, all of the hdisk devices that were converted will be configured under the RDAC driver.

IBM BladeCenter Issues

To ensure that the storage devices are properly configured on the IBM BladeCenter® server, change the init_link setting on the Fibre Channel adapter from arbitrated loop to point to point.

Enter the following commands to change the init_link setting on the Fibre Channel adapter:
chdev -l fcsX -ainit_link=pt2pt –P
bosboot -aD
cfgmgr

IBM Subsystem Device Driver (SDD)

AIX Version 7.1 does not support the IBM Subsystem Device Driver (SDD) for IBM TotalStorage Enterprise Storage Server®, the IBM TotalStorage DS family, and the IBM System Storage® SAN Volume Controller. If you are using SDD, you must transition to Subsystem Device Driver Path Control Module (SDDPCM) or AIX Path Control Module (PCM) for the multipath support on AIX for IBM SAN storage. SDD to SDDPCM migration scripts are available to help you with the transition.

Contact IBM storage technical support to request access to the migration scripts.

For additional information related to the available multipath I/O solutions and supported AIX versions for IBM SAN storage products, see IBM System Storage Interoperation Center (SSIC) at http://www-03.ibm.com/systems/support/storage/config/ssic/displayesssearchwithoutjs.wss?start_over=yes.

Limitations and restrictions

This section lists restrictions and limitations applying to AIX Version 7.1.

Limitation when creating a WPAR on a system with the Director agent installed

The syncwpar command might fail when you create a workload partition (WPAR) on a system with the Director agent installed. To avoid this problem, run the following command before you create the WPAR:
swvpdmgr -p DirectorCommonAgent

console special file limitation

The EIO errors are restricted in some cases when the connection to the console is lost. The EIO errors that result from the console write function are restricted because the streams file is marked when a tty that is connected to a modem is disconnected. All of the writes to the console are redirected to where the console points, and any writes to the file descriptor are returned with EIO errors. These EIO errors continue until a process reopens the console.

clogin command limitation

When you run the clogin command, some programs will not function properly, especially those programs that are in multibyte locales. Use the clogin command only for emergency system maintenance.

Workload Partitions not supported on thin servers

Workload partitions (WPARs) are not supported on thin servers (diskless and dataless systems that are not capable of booting and running without the assistance of servers on a network).

NPIV support of DS4000 storage products

Some models of the DS4000 product family can be configured using the FCPARRAY or MPIO driver:
  • If the device is configured using the MPIO driver, there are no restrictions.
  • If the device is configured using the FCPARRAY driver, then the following restriction applies:
    • If the device has the reservation policy attribute set to any value other than no_reserve, the LPARs that the device is attached to will fail LPAR migration operations.

WPAR parameters must be in English ASCII text

WPAR input parameters must be in English ASCII text. This includes the following WPAR variables:
  • WPAR name
  • WPAR password
  • WPAR paths
  • WPAR application
  • WPAR hostname

Installing applications in a WPAR environment

The WPAR documentation describes how to install applications in a WPAR environment using various applications such as Apache, DB2 and WAS. These examples are not intended to imply that they are the supported versions or configurations of these applications.

System software cannot be directly managed in a non-shared /usr Workload Partition

If a WPAR is configured to have writable, non-shared /usr and /opt filesystems, the AIX system software within that WPAR cannot be directly managed from within the WPAR. Operations that are prevented on system software include apply, commit, deinstall, and reject. If it is necessary to modify system software within a non-shared WPAR, use the /usr/sbin/swvpdmgr -w <fileset_names> command to allow those file sets to be directly managed within the workload partition.

SNMPv3

In AIX Version 7.1, due to the security concern that the "public" community name configured in the /etc/snmpdv3.conf file is able to query a lot of Management Information Base (MIB) information on the system, the default behavior has been changed to restrict the "public" community name to view this information.

AIO has been removed from the ODM

For each Asynchronous I/O (AIO) function there is a Legacy and a POSIX definition. In AIX Version 7.1, both POSIX and Legacy extensions are loaded at boot time. Do not run the mkdev -l [aio0 | posix_aio0] command to load the extension because it will fail on AIX Version 7.1. AIO attributes have been removed from the Object Data Manager (ODM) and can no longer be queried with the lsattr command or changed with the chdev command. All of the tunables have been removed from the ODM and are managed by the ioo command.

Using a USB optical device with VIOS

When you switch USB optical devices away from a Virtual I/O Server platform, then switch them back, the client partitions cannot use the optical devices until you delete the virtual optical devices, as well as the real optical devices. Run the cfgmgr command to make the optical devices available.

Performing an internal or external snapshot of a JFS2 filesystem

The snapshot command fails in the following instances:
  • The snapshot command fails with a Not owner error if you are trying to create an internal snapshot and the filesystem already has an external snapshot and vice versa. In this instance, the fscntl system call returns -1 and the errno parameter has the EPERM value.
  • The snapshot command fails with a Not owner error if trying to create an internal or an external snapshot and the filesystem is HSM enabled. In this instance, the fscntl system call returns -1 and the errno parameter has a EPERM value.
  • The chfs command fails with a A system call received a parameter that is not valid error if trying to enable HSM for a filesystem that has an internal or an external snapshot. In this instance, the finfo system call returns -1 and the errno parameter has a EINVAL value.
  • The snapshot command fails with a No space left on device error when trying to create an internal snapshot and the snapshot limit is exceeded. In this instance, the fscntl system call returns -1 and the errno parameter has a ENOSPC value.

Xterm with locale support limitations

Xterm, the terminal emulator for the X Window System, is enabled for locale support, except for bidirectional locales. This emulator requires IS0 10646-1 encoded fonts to display results. These fixed-width fonts are shipped with AIX CDs. Install the X11.fnt.xorg.misc-misc file set to properly display locale text. The fixed-width fonts are limited to two sizes: default and large.

All Latin languages, Japanese, and Korean languages are supported. The Chinese language is not supported.

Note: Japanese support is provided only for JISX0201 and JISX0208 characters.

Messages from the xterm application are not displayed in locale-specific languages.

InfiniBand EEH limitation

The 4X IB Dual Port DDR Exp CD, CFF/PCIE adapter (feature 8258) does not support full EEH recovery. If you get a bus error (MXIB_EEH_HARDWARE_ERROR in the error log), you might have to manually perform the recovery steps. These steps may include manually reconfiguring the adapter or replacing the adapter. To manually reconfigure the adapter, do the following:
  1. Unconfigure the adapter by using the rmdev command (for example, rmdev -l iba0).
  2. Configure the adapter by using the mkdev command.
Notes:
  1. If the adapter instance is busy (a program or kernel extension has called open on the adapter), you might not be able to unconfigure the adapter. If you cannot unconfigure the adapter, reboot the system.
  2. If the bus error (MXIB_EEH_HARDWARE_ERROR) is present after a successful manual recovery, replace the adapter.

AIX Information Center

The AIX Information Center is provided on the Web at http://publib14.boulder.ibm.com/infocenter/systems/aix. The AIX Information Center can be installed from or be viewed directly from the DVD on any AIX or Microsoft Windows systems that are capable of reading a DVD.

If you require a translated version of the documentation and cannot access the Web site or use a DVD, then you might be able to download a copy of the DVD contents from the "Entitled Software Service" site under the terms of your AIX Software Maintenance Agreement if electronic download is offered in your country.

Information about using the electronic software delivery site is provided by going to the Web site at https://www-05.ibm.com/servers/eserver/ess/ProtectedServlet.wss and clicking Help. The electronic install image is provided in a tar.gz format. After downloading the compressed tar image, decompress, unpack, and run install_aix to start the installation wizard.

Note: It is recommended that you restart your system after the AIX Information Center is installed. On AIX systems, exit the installation wizard after the installation of the documentation for each language. On AIX systems, to set the default browser, type the following command:
chwebconfig -b <browser location>

What's new

Base AIX Security (BAS)/Labeled AIX Security (LAS) EAL4+ updates

This topic serves as a supplement to the AIX Version 7.1 Security and provides information relevant to configuring and using a system according to the requirements for the AIX Version 7.1 BAS/LAS EAL4+ Common Criteria evaluation. Use PRPQ number [add number when available] to get the certified version of AIX Version 7.1

Administrators should refer to this section before going to the AIX Version 7.1 Security Security. Unless otherwise stated, the information in AIX Version 7.1 Security supersedes any other document that refers to this topic.

New and enhanced functionality in AIX Version 7.1

AIX Version 7.1 delivers support for the System p POWER6 and POWER7 based offerings.

Enterprise Storage Management

AIX Version 7.1 includes new improvements to Enterprise Storage Management. These enhancements include:
  • NFS Support for Workload Partitions

    When mounting NFS file systems from within a system, WPAR performs the same as a regular NFS mount (Versions 2, 3, and 4 supported). Statistics (nfsstat) and tunables (nfso) commands from within a WPAR are specific to that WPAR. NFS mounts from within a mobile WPAR are relocated with the WPAR.

  • JFS2 Integrated Snapshots
    In AIX Version 7.1, snapshots are created in the same storage device as the file system. This new feature allows:
    • Ease of management by removing management of separate logical volumes for snapshots. The snapshot resides in the same host storage object as the primary file system. These snapshots are referred to as internal snapshots to contrast with the snapshots in separate logical volumes, which are now referred to as external snapshots.
    • The number of snapshot generations per file system has been increased to 64. This increase provides better support for real world environments where snapshots are taken at weekly, daily and hourly intervals compared to the external snapshot limit of 15.
    • The new integrated snapshot facility provides superior ease of use. Since the snapshot is in the primary file system, earlier versions of files can be accessed by non-privileged users without requiring a separate mount of the snapshot. This new facility also allows NFS client access to snapshot data for exported file systems.
  • Thread support enhancements add support for thread local storage, thread I/O Prioritization, unique thread identifiers to enable the next generation of database technology.
  • PowerHA® asynchronous Global disk mirroring is supported, a key requirement for Disaster Recovery data protection.

WPAR storage devices

System WPARs can import one or more storage devices. Non-rootvg volume groups, logical volumes, and file systems can be created and managed on imported storage devices within the WPAR.

A storage device is deployed to a WPAR in the following phases:
  1. Use the mkwpar or chwpar command to allocate a device to a WPAR.
  2. The device is automatically exported to the WPAR when the WPAR starts.
  3. The device is automatically imported when the WPAR is booted with the cfgmgr command.

After the device is exported to a WPAR, the device state is listed as Defined and it is not available in the Global environment until it is unexported by using either the chwpar command or the stopwpar command.

Supported storage devices

The disk drives that are supported in a WPAR include any FibreChannel disk drive that is supported by AIX 6 and uses the scsidisk device driver with the AIX MPIO (default PCM) multipath software. These include the follwing:
  • IBM System Storage DS3400
  • IBM System Storage DS4200
  • IBM TotalStorage DS4300 (FAStT600)
  • IBM TotalStorage DS4500 (FAStT900)
  • IBM System Storage DS4700
  • IBM System Storage DS4800
  • IBM System Storage DS5100
  • IBM System Storage DS5300
  • IBM XIV® Storage System

The tape drives that are supported in a WPAR are any FibreChannel tape drives that are supported by AIX 6 and use the sctape device driver.

Note: The atape device driver is not supported.

Allocating a device

A device can be allocated to a WPAR when the WPAR is created or it can be added to WPAR in a later operation. For a device to be allocated to a WPAR, it must be in the available state or defined state in the Global environment.

To query the device state, run the following command:
lsdev -l <device>
To create a system WPAR and allocate the hdisk3 storage device, run the following command:
mkwpar -D devname=hdisk3 -n mywpar1
To allocate a storage device to an existing WPAR, run the following command:
chwpar -D devname=hdisk4 mywpar1

When you allocate a storage device to an active WPAR, the device is exported to the WPAR unless it was previously exported. To import the newly allocated device into the WPAR, invoke the cfgmgr command within the WPAR.

The -D flag for the mkwpar and chwpar commands supports a new attribute, devid. The devid attribute can be used if the unique device identifier for the storage device is known. The devid and devname attributes cannot be specified together. The devtype attribute has been updated to accept three additional device types: disk, tape and cdrom.

A storage device can be allocated to more than one WPAR. However, the device can be exported to only one WPAR at a time. The device is exported to the WPAR that starts first. After a device has been exported to a WPAR, the extended state of the device is listed as Exported. To see the extended state of a device, run the following lsdev command with the new -x flag:
lsdev -x -l hdisk1
A message similar to the following is displayed:
hdisk1 Exported 01-08-02 MPIO Other DS4K Array Disk

Deallocating a device

To deallocate a storage device from an existing WPAR, enter the following command.
chwpar -K -D devname=hdisk3 mywpar1

When a storage device is deallocated from an inactive WPAR, the device is removed from the configuration file. When a storage device is deallocated from an active WPAR, the chwpar command attempts to unconfigure the device. If the device is being used, the unconfiguration operation fails and the command to remove the device from the WPAR also fails. When the command is successful, the device in the WPAR changes from the available state to the defined state.

Configuring a device in a WPAR

Each storage device that is configured in the WPAR has an ODM entry in the WPAR. Each storage device also has a virtualized parent device. Configuration of the parent devices and management of the paths to the actual devices are not allowed in the WPAR. The following commands are used to configure and manage the Global environment and the devices in the WPAR:
  • mkdev
  • chdev
  • rmdev
  • lsdev
  • cfgmgr
  • lsattr
  • lspath

Managing file systems for a device

When a device is configured in the WPAR, commands that are used to create and manage volume groups, logical volumes, and file systems operate in the same way as they do in the Global environment. To create and modify volume groups, use the following commands:
  • mkvg
  • importvg
  • extendvg
To create and modify logical volumes, use the following commands:
  • mklv
  • chlv
To create and modify file systems, use the following commands:
  • mkfs
  • chfs

Limitations

The following limitations apply to WPAR storage devices.
  • A storage device can be exported to only one active WPAR.
  • The JFS2 file system must be used for disk storage devices.
  • To use the WPAR storage device feature, the wio.common and wio.fcp packages must be installed.

Security

AIX Version 7.1 includes significant new enhancements to its security features. These enhancements include:
  • Role Based Access Control

    Role Based Access Control (RBAC) is designed to improve security and manageability by allowing administrators to delegate system administrative duties to non-root users. RBAC in AIX has been enhanced to provide very fine granular authorizations that identify the privileged operation that they control. These authorizations can be used to create the required roles necessary and assign those roles to the users required to manage the system.

  • Trusted AIX

    Trusted AIX extends the security capabilities of AIX by supplying integrated multi-level security. Trusted AIX is implemented as an installation option that provides the highest levels of label-based security to meet critical government and private industry security requirements.

  • Encrypting Filesystem

    The IBM Journaled Filesystem Extended (JFS2) provides for greater data security with the addition of a new capability to encrypt the data in a file system. Clients can select from a number of different encryption algorithms. The encrypted data can be based up in encrypted format, reducing the risk of data being compromised if backup media is lost or stolen. The JFS2 encrypting file system can also prevent the compromise of data even to root-level users.

  • Trusted Execution

    Trusted Execution provides an advanced mechanism for checking and maintaining system integrity. A signature (SHA256/RSA) database for important system files is created automatically as part of the regular AIX installation. The Trusted Execution tool can be used to check the integrity of the system against the database. An administrator can define policies such as monitoring the loads of files listed in the database and not allowing execution/loads if hashes do not match.

  • Secure by Default

    The AIX Version 7.1 installation offers a new option, Secure by Default, that installs only the minimal number of services to provide the maximum amount of security. The Secure by Default option works particularly well when used in conjunction with the AIX Security Expert to only enable the system resources required for the system's intended purpose.

  • Digital certificate authentication for RADIUS

    The AIX RADIUS server fully supports the EAP-TLS protocol for implementing digital certificate authentication in wireless networks. This strong mutual authentication protocol is used for securing access to wireless and wired networks.

  • TCP traffic regulation

    TCP Traffic Regulation provides AIX and Virtual I/O Server (VIOS) systems with flexible denial-of-service attack mitigation of TCP sockets. Policies created by a system administrator can be configured to set maximum limitations and control source IP diversity of incoming TCP connections to a network port or a range of ports. The system automatically ensures that resources are shared across multiple remote IP addresses that are attempting to connect through TCP to a port.

  • Version 2.20 of the PKCS #11 standard
    The PKCS #11 subsystem has been implemented using the following components:
    • An API shared object (/usr/lib/pkcs11/ibm_pks11.so) is provided as a generic interface to the device driver in which PKCS #11 support is implemented. This tiered design allows you to use new PKCS #11 devices when they come available without recompiling existing applications.
    • A PKCS #11 device driver that provides the same capabilities to applications as those provided to other kernel components such as EFS or IPSec.
  • Systems Director platform supports IBM Systems Director Console for AIX tasks.
  • Other manageability enhancements include the following:
    • Concurrent kernel updates manageability and coverage improvements.
    • Improved/new function for commands such as fcstat, topasout, and svmon.
    • Common Information Model (CIM) instrumentation for devices.
    • Performance tools enhancements for workload partitions.
    • The nmon functionality has been integrated into the topas infrastructure, including the ability to use nmon analyzer to process topas historical data.
    • Cryptographic framework.
    • Centralized key management for Encrypting file systems stored in LDAP.
    • Trusted Execution centralized policy control in LDAP.
  • The Common Criteria protection profiles are changed. The Controlled Access Protection Profile (CAPP) is replaced by Base AIX Security (BAS) and the Labeled Security Protection Profile (LSPP) is replaced by Labeled AIX Security (LAS).

System management

AIX Version 7.1 includes new improvements to the manageability of the AIX operating system. These enhancements include:
  • NFSv4 support for the Network Installation Manager (NIM)
  • Graphical Installation

    The AIX Graphical Installer provides a simplified, easy-to-use version of the AIX installer. Users are presented with a graphical user interface to start a system installation instead of the existing text-based installation menu. The Graphical installer is limited to users that boot DVD media on a system that does not have an existing operating system on its disks. If the installation code finds a root volume group on a disk, the traditional BOS menus are presented.

  • New graphical systems console, the IBM Systems Director Console for AIX

    The Systems Director Console for AIX provides a responsive Web access to common systems management tools such as the Systems Management Interface Tool (SMIT) and offers integration into the IBM Systems Director.

  • Systems Director platform supports IBM Systems Director Console for AIX tasks.
  • Other manageability enhancements include the following:
    • Concurrent kernel updates manageability and coverage improvements.
    • Improved/new function for commands such as fcstat, topasout, and svmon.
    • Common Information Model (CIM) instrumentation for devices.
    • Performance tools enhancements for workload partitions.
    • The nmon functionality has been integrated into the topas infrastructure, including the ability to use nmon analyzer to process topas historical data.
  • IBM Systems Director Agent is now included as part of AIX Version 7.1 installation media and is installed and enabled by default.
  • AIX Runtime Expert profile-based performance management.
  • Multi-system topas collect and report performance information from multiple separate systems.
  • Performance Management for Power Systems™ agent support with topas.
  • PerformanceAide integrated with topas.
  • Enhanced concurrent maintenance for LVM and NFS.
  • Thin server paging over TCP/IP.
  • Multiple server monitoring with topas.
  • JFS to JFS2 conversion on migration.
  • Secure Shell (SSH) included on the base AIX installation media.

dscrctl Command

Purpose

Allows the system administrator to read the current settings for the hardware streams mechanism and to set a system wide value for the Data Stream Control Register (DSCR). The Data Streams Control Register is privileged. It can be read or written only by the operating system.

For more information on the Data Stream Control facilities, refer to the POWER Instruction Set Architecture V2.05, available from http://www.power.org.

Syntax

To query the characteristics of the hardware streams on the system:
dscrctl -q
To set the operating system default prefetch depth on the system temporarily (that is, for the current session) or permanently (that is, after each reboot):
dscrctl [-n] [-b] -s <dscr_value>
To cancel a permanent setting of the operating system default prefetch depth at boot time:
dscrctl -c

Description

The dscrctl -q subcommand queries and displays the number of hardware streams, and the platform and operating system default prefetch depth. Any user can run this subcommand.

The dscrctl -s subcommand sets the operating system default prefetch depth. It requires root authority to run. This default can be changed either for the current session (-n), at boot time (-b) or both (-n -b).

The dscrctl -c option cancels the setting of the operating system default prefetch depth at boot time. This option removes the dscrctl command from the /etc/inittab file and thus takes effect after the next reboot.

Flags
-q
Query: Display the number of hardware streams supported by the platform and the values of the firmware and operating system default prefetch depth.
-c
Cancel: Cancels a permanent setting of the system default prefetch depth at boot time by removing the dscrctl command from the /.etc/inittab file.
-n
Now: Used in conjunction with the -s flag, changes the runtime value of the operating system default prefetch depth. The change is not persistent across boot.
-b
Boot: Used in conjunction with the -s flag, makes change persistent across boots by adding a dscrctl command to the /etc/inittab file.
-s dscr_value
Set: Defines the value for the new operating system default prefetch depth. The value is treated as a decimal number unless it starts with 0x in which case it is treated as hexadecimal.

Examples

  1. Set the value of the operating system default prefetch depth to 13 for the current session:
    # dscrctl -n -s 13
  2. Display the current settings for the hardware streams mechanism:
    # dscrctl -q
    Current DSCR settings:
    	number_of_streams = 16
    	platform_default_pd = 0x5 (DPFD_DEEP)
    	os_default_pd = 0xd (DSCR_SSE | DPFD_DEEP)
    #
Related information

/etc/inittab

Additional information

USB Blu-ray drive read-only support

AIX Version 7.1 recognizes and configures USB attached Blu-ray drives. This feature is included in the following device package:
devices.usbif.08025002
The capability of the AIX operating system to read Blu-ray media is validated against a sample of industry standard OEM USB Blu-ray drives.
Note: The AIX USB host-controller device driver supports USB 2.0 on AIX Version 5.3 with Technology Level 5300-10, and later, and AIX Version 6.1 with Technology Level 6100-03, and later. The USB 2.0 based Blu-ray devices are supported.

USB Blu-ray drives are configured with logical names, such as cd0 and cd1. The drives present both raw and block special files. For example, the raw special file for cd0 is /dev/rcd0, and the block special file is /dev/cd0.

The read-only capability is provided for the ISO file system (read-only ISO9660), the Universal Disk Format (UDF) file system (version 2.01, or earlier) and standard optical media access commands, such as dd and tar.

AIX does not support the write operation to CD, DVD, or Blu-ray media present in the USB Blu-ray drive. Although the write operation is not prevented (if the drive is write capable), IBM does not provide support for any issues encountered during the write operation.

AIX does not support plug-and-play for USB Blu-ray drives. To make a USB Blu-ray drive available to AIX users, a root user must connect the drive to a system's USB port and run the following command:
cfgmgr -l usb0
After the drive is removed, the drive remains in the available state in the Object Data Manager (ODM) database until the root user runs the following command:
rmdev -l cd<n>

When a drive is in the available state, you can reconnect it to the system, and it can be remounted or reopened. If a drive is disconnected from a system USB port while it is still open to a user, you cannot use that drive until you close and reopen it.

Cluster Aware AIX

Cluster repository

A key element of the cluster configuration is the cluster repository disk. The cluster repository disk is used as a central repository for the cluster configuration data. The cluster repository disk must be accessible from all nodes in the cluster and is a minimum of 10 GB in size and backed by a redundant and highly available storage configuration. The cluster repository disk must be appropriately set up in a RAID configuration to accommodate the requirements of the data center.

A cluster repository disk is a special device for the cluster. The cluster repository disk has special characteristics that do not support the use of LVM commands when acting on the cluster repository disk. AIX LVM commands are single-node administrative commands and are not applicable in a clustered configuration. The cluster repository disk is renamed to a private device name. Due to the special device characteristics required by the cluster repository disk, there is a raw section of the disk and a section of the disk that will contain a special volume group and special logical volumes that are used during cluster operations (bootstrap and run time).

Disaster recovery

When setting up the cluster configuration and designing a disaster recovery plan, the storage fabric must be evaluated to adequately cover the requirements of the data center (redundancy and backup). In case of a total loss of the hardware and storage elements associated with the cluster configuration, the cluster nodes must be completely rebuilt, because any information that was stored in the OS image of the lost node or storage fabric is lost. The inter-relationships of device names and host names are unique, and cannot be restored from an associated backup disk or image.

Cluster naming policy

Care must be taken while naming clusters. Also, consider the reserved name limitations.

You can use only ASCII A - Z, a - z, 0 - 9, - (hyphen), . (period), and _ (underscore). The first character of the cluster name and domain name must not be a hyphen. The maximum length of a cluster name is 63 characters.

Problem determination and troubleshooting

The SNAP command
The clustering subsystem provides a snap script that can be used to aide in the collection of relevant logs and data configurations to assist with problem determination and troubleshooting activities. For more information, see the snap command.
snap caa
The following structure is an example of the data files collected during the snap script execution for Cluster Aware AIX (CAA):
/tmp/ibmsupt
|
'---- caa_snap
     |
     '---- cluster1
     |     |
     |     '---- node1 (canonical hostname thereof)
     |     '---- ...
     |     '---- nodeN
     |
     '---- ...
     |
     '---- clusterN
           |
           '---- node1
           '---- ...
           '---- nodeN
Syslog setup

The clustering subsystem uses the syslog facility to log errors and debug information. For more information, see syslogd daemon.

To set up the syslog for clustering:
  1. Edit /etc/syslog.conf and add the desired log level and file sizes, for example:
    *.info /var/adm/ras/syslog.out 	 rotate size 10m files 10
  2. Refresh the syslog daemon by using the following command:
    refresh –s syslogd
  3. Initiate® the syslog facility by using the touch command on the syslog.out file.

Cluster maintenance mode

The following information only applies to AIX version 7.1.0.0 - 7.1.0.5. If your system is running AIX version 7.1.0.6, or later, the maintcluster command has been replaced with the clctrl command.

Maintenance of the cluster repository disks, logical volumes, and file systems (with names such as private) must not be needed under normal operation. If maintenance is necessary, the maintcluster command might be used to place the cluster in maintenance mode.

The maintcluster command quiesces cluster services and varies off the cluster repository disk on all but one node, which becomes the management node during cluster maintenance. Changes cannot be made to the cluster configuration during cluster maintenance mode.

To set the cluster in maintenance mode, run the following command:
maintcluster ON
To return the cluster to normal operation, run the following command:
maintcluster OFF

Cluster Data Aggregation Tool

AIX Version 7.1 introduces a new reliability, availability, and serviceability (RAS) tool called Cluster Data Aggregation Tool.

The Cluster Data Aggregation Tool provides a single instance to launch RAS debug and monitoring actions, and to collect problem determination data for multiple nodes. The Cluster Data Aggregation Tool environment is made of a central master node and remote nodes. The Cluster Data Aggregation Tool is installed on and executed from the central master node. The central master node hosts the data collection repository, which is a new file system that contains all the collection data from multiple remote nodes. The remote nodes are the nodes where Cluster Data Aggregation Tool data are collected, which are the AIX logical partition (LPAR), VIOS, PowerHA™ pureScale™, and HMC data.

The Cluster Data Aggregation Tool has the following features:
  • Captures problem determination data across multiple nodes.
  • Supports sending the data gathering tool to remote nodes.
  • Provides an extensible plug-in feature that supports new data collection types for a user.
  • Integrates with RBAC to enable a nonroot user to collect Cluster Data Aggregation Tool data.
  • Relies on Secure Shell (SSH) for secure connectivity between nodes.
  • Is controlled by the CLI (command-line interface) and SMIT panel.

The Cluster Data Aggregation Tool is managed by the cdat command that is divided into several subcommands. The subcommands are access, archive, check, collect, delete, discover_nodes, init, list_nodes, list_types, and show.

For more information about the Cluster data Aggregation Tool, see Cluster Data Aggregation Tool User Guide and Reference.

DB2 migration

You can upgrade your DB2 environment with DB2 Version 9.5, DB2 Version 9.1, or DB2 UDB Version 8 copies to DB2 Version 9.7. For more information, see http://publib.boulder.ibm.com/infocenter/db2luw/v9r7/index.jsp?topic=/com.ibm.db2.luw.qb.upgrade.doc/doc/c0023662.html.
Note: The DB2 High Availability feature is not included in the DB2 version 9.7 FP2. The DB2 HA feature is available in the DB2 Version 9.7 from FP3.

Lightweight Infrastructure

The following AIX components rely on and incorporate Lightweight Infrastructure (LWI) v7.1:
  • Electronic Service Agent™ (eSA)
  • IBM Systems Director Console for AIX
  • Common Agent Services (CAS) Agent

For information about licensing LWI v7.1, see the Program-unique Terms section of the AIX license information documentation.