http://www-933.ibm.com/eserver/support/fixes/fixcentral
These Release Notes support AIX® Version 7.1.
http://publib.boulder.ibm.com/infocenter/aix/v7r1/index.jsp?topic=/com.ibm.aix.ntl/releasenotes_kickoff.htm
https://www-01.ibm.com/marketing/iwm/iwm/web/pickUrxNew.do?source=aixbp
These tips might contain information that are critical for successful installation of this
software.http://www-03.ibm.com/software/sla/sladb.nsf
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.
http://www-933.ibm.com/eserver/support/fixes/fixcentral
https://www.ibm.com/systems/support/myview/subscription/css.wss/folders?methodName=listMyFolders
https://www-01.ibm.com/marketing/iwm/iwm/web/pickUrxNew.do?source=aixbp
Review the following information to determine the minimum and recommended system requirements needed to run AIX Version 7.1.
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.
prtconf | grep 'Processor Type'
lscfg -vl cd*
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.
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 |
http:/www14.software.ibm.com/webapp/set2/firmware/gjsn
printenv real-base
The
following is a sample display: -------------- Partition: common -------- Signature: 0x70 ---------------
real-base 2000000 c00000
setenv real-base c00000
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.
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.
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.
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.
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. |
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).
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 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 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.
AIX Version 7.1 creates a 512 MB paging space (in the /dev/hd6 directory) for all new and complete overwrite installations.
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 AIX 7.1 | |
---|---|
Location | Allocated (Used) |
/ | 196 MB (184 MB) |
/usr | 2044 MB (1862 MB) |
/var | 424 MB (299 MB) |
/tmp | 128 MB (2 MB) |
/admin | 128 MB (1 MB) |
/opt | 352 MB (184 MB) |
/var/adm/ras/livedump | 256 MB (1 MB) |
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.
SAS RAID controllers and Fibre Channel controllers support attached arrays and disks with capacities which exceed 2 TB. The maximum supported capacity (beyond 2 TB) 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.
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.
https://www-01.ibm.com/marketing/iwm/iwm/web/pickUrxNew.do?source=aixbp
If AIX 7.1 is installed on your system, you can use the update media or the base media to update to AIX 7 with Technology Level 7100-01. To verify the level, run the oslevel -r command. To perform the update, run the smitty update_all command.
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 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.
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.
AIX Version 7.1 includes the IBM Systems Director Common Agent 6.2.1. 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.
/opt/ibm/director/agent/runtime/agent/bin/endpoint.sh stop
stopsrc -s cas_agent
startsrc -s cas_agent
/opt/ibm/director/agent/runtime/agent/bin/endpoint.sh start
platform_agent:2:once:/usr/bin/startsrc -s platform_agent >/dev/null 2>&1
cimservices:2:once:/usr/bin/startsrc -s cimsys >/dev/null 2>&1
stopsrc -s cas_agent
/opt/ibm/director/agent/runtime/nonstop/bin/installnonstop.sh -uninstallservice
/opt/ibm/director/bin/diruninstall
installp -u cas.agent
installp -u tivoli.tivguid
installp -u sysmgt.cim.smisproviders*
installp -u sysmgt.cim.providers*
installp -u sysmgt.cimserver.pegasus
For more information about IBM Systems Director 6.2, see the IBM Systems Director V6.2 Web page.
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.
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).
^./
# 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
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.
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 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.
The instructions for installing AIX using the media device to install a partition with an HMC have been changed to:
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
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
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
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
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.
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:
uname -a
nim -o change -a cupid+<cupid> <client>
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.
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.
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.
/mount_point/installp/ppc
/mount_point/RPMS/ppc
/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.
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.
When you migrate from AIX 5.3 or 6.1 to AIX 7.1, you can avoid the risk of down-leveling fixes previously installed on your AIX 5.3/6.1 system by migrating to the latest available Technology Level of AIX 7.1. If you are using a NIM lpp_source created with a prior level base media and later levels of updates added, you should initially create the lpp_source with the base media at the same release date or later than the level of AIX 5.3/6.1 that you are migrating from. The last 4 digits of the output of the oslevel -s command represent the year and week of the service pack currently installed (YYWW).
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.
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.
The dsm.core ships a /etc/ibm/sysmgt/dsm/overrides/dsm.properties file which allows user to overrides SSH configuration. If this file was modified, the file will need to be backed up manually before an update or a migration, as it will be overwritten.
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.
dt:2:wait:/etc/rc.dt
kdm:2:once:/opt/freeware/kde/bin/kdm
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.
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.
lslpp -l pmtoolkit
lslpp: 0504-132 fileset pmtoolkit not installed
you
can safely install the bos.pmapi file set. Fileset Level State Description
----------------------------------------------------------------------------
Path: /usr/lib/objrepos
pmtoolkit 1.3.1.6 COMMITTED Performance Monitor Toolkit
1.3.1
complete
the following steps: installp -u pmtoolkit
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.
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.
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.
To convert DS4000 disks from FCPARRAY to MPIO, do the following:
set controller [a] HostNVSRAMBYTE [0x06,0x27] = 0x8;
set controller [b] HostNVSRAMBYTE [0x06,0x27] = 0x8;
When the script completes, exit the Storage Manager.
lsdev –Cc disk | grep DS4K
lscfg –vl hdiskX
# 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)........
Machine type-model | Array disk | Storage server |
---|---|---|
1722-600 | DS4300 | FAStT 600 |
1742-900 | DS4500 | FAStT 900 |
1814 | DS4700 and DS4200 | |
1815 | DS4800 |
# ‘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.
# 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
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
To convert the DS4000 driver from MPIO to FCPARRAY, do the following:
set controller [a] HostNVSRAMBYTE [0x06,0x27] = 0;
set controller [b] HostNVSRAMBYTE [0x06,0x27] = 0;
When the script completes, exit the Storage Manager.
lsdev –Cc disk | grep DS4K
lscfg –vl hdiskX
# 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)........
Machine type-model | Array disk | Storage server |
---|---|---|
1722-600 | DS4300 | FAStT 600 |
1742-900 | DS4500 | FAStT 900 |
1814 | DS4700 and DS4200 | |
1815 | DS4800 |
# ‘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.
# 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
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
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.
chdev -l fcsX -ainit_link=pt2pt –P
bosboot -aD
cfgmgr
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.
This section lists restrictions and limitations applying to AIX Version 7.1.
swvpdmgr -p DirectorCommonAgent
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.
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 (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).
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.
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.
Due to the security concern, the public community name configured in snmpdv3 agent configuration file /etc/snmpdv3.conf will be disabled from AIX 6100-07 and AIX 7100-01 release. The AIX snmpdv3 agent will not respond to any request on behalf of the public community name.
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 tunable have been removed from the ODM and are managed by the ioo command.
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.
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.
Messages from the xterm application are not displayed in locale-specific languages.
The AIX Information Center is provided on the Web at http://publib.boulder.ibm.com/infocenter/aix/v7r1/index.jsp. 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.
chwebconfig -b <browser location>
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 P91209, 5799-GWG, with feature 5897 to get the certified version of AIX Version 7.1.
Administrators should refer to this section before going to the Security topic in the AIX 7.1 Information Center. Unless otherwise stated, the information in the security topic supersedes any other document that refers to this topic.
AIX Version 7.1 delivers support for offerings based on Power Systems servers.
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.
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.
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.
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.
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.
lsdev -l <device>
mkwpar -D devname=hdisk3 -n mywpar1
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.
lsdev -x -l hdisk1
A message
similar to the following is displayed: hdisk1 Exported 01-08-02 MPIO Other DS4K Array Disk
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.
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 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.
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 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.
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.
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 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.
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.
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.
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
dscrctl -q
dscrctl [-n] [-b] -s <dscr_value>
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.
Examples
# dscrctl -n -s 13
# dscrctl -q
Current DSCR settings:
number_of_streams = 16
platform_default_pd = 0x5 (DPFD_DEEP)
os_default_pd = 0xd (DSCR_SSE | DPFD_DEEP)
#
/etc/inittab
devices.usbif.08025002
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.
cfgmgr -l usb0
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.
The Cluster Aware function is part of the AIX operating system. Using Cluster Aware AIX (CAA) you can create a cluster of AIX nodes and build a highly available solution for a data center.
Migration is not supported for AIX 6 with 6100-07 or for AIX 7 with 7100-01. To upgrade from AIX 6.1 with 6100-06 of Cluster Aware AIX (CAA) or from AIX 7 with 7100-00 of CAA to AIX 6 with 6100-07 or to AIX 7 with 7100-01, first remove the cluster, and then install AIX 6 with 6100-07 or install AIX 7 with 7100-01 on all nodes that will be included in the new cluster.
CAA no longer uses an embedded IBM solidDB® database. The bos.cluster.solid fileset still exists, but it is now obsolete. The solid and solidhac daemons are no longer used by CAA.
CAA commands no longer support forced cleanup options.
chcluster -f
clusterconf -f, -s, -u
rmcluster -f
The clctrl command can be used for tuning the cluster subsystem. Only tune the cluster subsystem at the direction of IBM customer support.
The CAA infrastructure now provides limited support for some disks that are managed by vender disk drivers. No disk events are available for these disks, but they can be configured into a cluster as a repository or as shared disks. See the documentation for the clustering product that you are using, such as IBM PowerHA SystemMirror for AIX, for a complete list of vendor disk devices that are supported for your environment.
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 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.
For information about licensing LWI v7.1, see the Program-unique Terms section of the AIX license information documentation.
See the Supported languages and locales topic for information on server side support for new unicode locales.