IBM i integration
with BladeCenter and System x

1) Review the System x models supported with IXA page.

Follow any instructions stated in the Notes section for the System x model that you are using.

2) Follow the latest IXA hardware install instructions

Use the latest Integrated xSeries Adapter (IXA) document for IBM® System p5 and i5, eServer™ p5 and i5 and OpenPower™ models (2.3 MB) or pre-eServer i5 models (1.3 MB) to install the IXA in the System x model.

Note: The process for installing an IXA in a System x model is the same for all i5/OS® releases. The above PDF documents contain the most recent IXA install information and covers recently announced System x models that can be attached to the IBM i platform via the IXA.

Also see the IXA Installation Problem Determination Guide (405 KB). Contains a set of problem determination procedures for diagnosing potential problems encountered while installing a new Integrated xSeries Adapter in a System x model and attempting to attach it to your IBM i.

3) Follow these instructions if your System x model is listed below:

4) Route SPCN and RIO/HSL cables to prevent electrical interference.

It is important to route SPCN and HSL cables at least 6 inches away from any AC power cords when attaching System x severs via the IXA. It is also important to route these cables away from other potential sources of electrical interference such as power supplies, florescent lights and uninterruptible power supplies.

5) Load required IBM i PTFs

Several IBM i PTFs are required when attaching System x models via the IXA. See IBM i PTFs.

6) Review Windows Server support information

If you are installing Windows Server on your IXA attached System x model, see Windows on integrated servers for more information.

If you plan to install Windows Server 2003 Service Pack 1 on your IXA attached System x model, see Windows Server 2003 Service Pack 1 for more information.

Note that you can use install media that contains service pack 1 already integrated with the Windows Server 2003 install image. Here are a few of the options available to do this:

• Obtain a Windows Server 2003 R2 CD, which has Service Pack 1 built-in.
   
• Obtain a Windows Server 2003 CD with Service Pack 1 already integrated. This can be obtained through various channels such as Microsoft Developer Network (MSDN®).
   
• Create an integrated install image. To do this, follow the instructions on the Integrating a service pack with Windows Server 2003 web page.

If you you are going to do a "full" (non-ServerGuide) install, then you can also copy the Windows Server install image to an i5/OS Integrated File System (IFS) directory. See Creating a Windows Server install CD image in IFS. The IFS directory is used on the Windows source directory (WNTSRCDIR) parameter when running the INSWNTSVR command.

7) Review Linux support information

If you are installing Linux on your IXA attached System x model, see the Linux on integrated servers page for more information.

8) Install Windows servers using ServerGuide™

It is recommended that you install Windows using the Install Windows Server (INSWNTSVR) command with the install type *BASIC option for your System x models attached with an Integrated xSeries Adapter. The *BASIC install type requires the ServerGuide install program, which is available on CD. ServerGuide will configure hardware specifically for your System x model as well as assist in the installation of the Windows operating system.

Notes:

1. The latest ServerGuide version can be obtained from the following web page: http://www.ibm.com/systems/management/serverguide/sub.html
2. Only ServerGuide version 7.1 or later is supported.
3. When using ServerGuide 7.1 and ServerGuide 7.2, the system drive partition is required to be 16GB or less.

9) Follow the Windows or Linux server installation documentation

For more information on installing Windows or Linux on the IXA, see one of the following:

For Windows servers:

• The Windows installation section in the Information Center for i 6.1, i 5.4 or V5R3.
• If you will install Windows Server 2003 Release 2 (R2), note that R2 licensing uses “per user/per device” terminology, rather than the equivalent “per seat” terminology that was used for base Windows Server 2003 licensing. If you are using “per user/per device” licensing for R2, then you should specify the “per seat” (*PERSEAT) option on the License mode (LICMODE) parameter of the INSWNTSVR command.

For Linux servers:

• For i 5.4: The installation-related sections of the Linux on an integrated xSeries solution topic in the Information Center.
• For V5R3: Chapter 3: Installation and configuration in Redbook Implementing Linux on Integrated xSeries Solutions for iSeries
  Note: The above Redbook does not address installing SUSE® Linux Enterprise Server 9 (SLES 9). If you are installing SLES 9 on an IXA attached System x model, also see the Redbook addendum for SLES 9 installs web page.
  Note: The above Redbook does not address installing Red Had Enterprise Linux 4 (RHEL 4). If you are installing RHEL 4 on an IXA attached System x model, also see the Redbook addendum for RHEL 4 installs web page.
• Note: In i 6.1, installation of Linux on IXA attached servers is not supported.

10) Check if Windows is reporting all of the installed memory

If your server has 4 GB or more of memory installed, but not all of it is being reported by Windows, see FAQ When 4 GB or more of memory is installed, why does Windows report less memory than is actually installed?

11) Keep the IBM i integration code up to date

The IBM i integration code on the Windows or Linux server needs to be updated periodically to provide the latest fixes. In addition, after the Linux operating system is updated using any distrubution update method, the IBM i integration code needs to be refreshed. Fixes are provided via IBM i service pack PTFs that are installed on the server. See the Service packs page for the latest IBM i integration service pack PTFs that are available as well as information on how to install service packs (or refresh the IBM i integration code) on your integrated Windows or Linux server.