|
|
| |
 IBM i integration with BladeCenter and System x
| | |
Use this web page to plan for and install an IBM® BladeCenter® or System x™ model that is attached to IBM i using an iSCSI network (iSCSI).
Follow the installation road map and use the corresponding checklist for your IBM i version:
Last updated: 10 July 2009
Important updates to the following subset of checklist items in the iSCSI-attached integrated server installation road map topic in the i 6.1 Information Center were made after i 6.1 became available. Make sure to use the online English versions of the topics listed below when working through the associated checklist items.
-
Prerequisites > Load required i5/OS products, firmware, and updates
-
Prepare for the hardware installation > Obtain firmware updates and drivers for your hardware
-
Prepare for the hardware installation > Plan the iSCSI Network
-
Hardware installation > Install the BladeCenter or System x hardware and iSCSI HBAs
-
Prepare for the operating system installation > Create and initialize a service processor configuration object
-
Operating system installation > Review i5/OS memory requirements and plan for a shared data memory pool
-
Operating system installation > Start the installation from the i5/OS console
-
Operating system installation > Continue the installation from the integrated server console
-
After the operating system installation > Complete the server installation
Use the following addendums to the checklist items in the iSCSI-attached integrated server installation road map topic in the i 6.1 Information Center:
-
Use planning worksheets when configuring hardware and software
Use the iSCSI network planning worksheets that are referenced by the checklist when installing an iSCSI attached server. Note that some of the topics referenced by the checklist do not specifically mention to use the values from the planning worksheets. Keep the worksheets in mind when configuring the hardware and software (for example, when creating configuration objects in IBM i) and use the values from the appropriate worksheets as needed.
-
Prerequisites > Obtain integrated server operating system installation media
Note: The i 6.1 checklist refers back to this read me page for this item. Use the information below when directed to do so by the checklist.
Review the Operating systems tested on iSCSI attached servers section of the BladeCenter and System x models supported with iSCSI web page to verify that the operating system you plan to install is supported with the hardware you plan to use. Then obtain the installation media for the operating system. See the appropriate section below for additional considerations.
Microsoft® Windows servers:
iSCSI attached Windows Server 2008 servers require the 64-bit x64 versions of the install media.
iSCSI attached Windows Server 2003 servers require the 32-bit x86 versions of the Windows install media (CD, DVD or IFS directory) with Service Pack 1 or later integrated with the base Windows Server 2003 installation image. Here are a few of the options available:
- 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.
VMware® ESX servers:
Also obtain install media for the guest operating systems that you plan to run on the virtual machines that are hosted by the VMware ESX server. For more information on supported guest operating systems, see the VMware Infrastructure 3 Documentation page.
Linux® servers:
iSCSI attached Linux servers require the 64-bit x86 versions of the install media (CD or DVD).
-
Prepare for the hardware installation >Plan the iSCSI network
In the iSCSI Network Planning Guide, the Selecting IP addresses for the System x or blade iSCSI initiator and Selecting IP addresses for the System i iSCSI HBA sections assume that the iSCSI network is fully connected and any initiator can talk to any target. However, when setting up an iSCSI network with physically disjoint segments, such as a BladeCenter with 2 switches, the initiators and targets on one switch should be on a different subnet than the initiators and targets on the other switch. Therefore, if you are using the suggested IP addressing scheme in the iSCSI Network Planning Guide and have 2 switches, use 192.168.99 for one subnet and 192.168.98 for the other subnet.
-
After the operating system installation > Scale the iSCSI network
Addendums to the documentation for this checklist item:
-
Windows only: Microsoft iSCSI Software Initiator version
Note: The i 6.1 checklist refers back to this read me page for this item. Use the information below when directed to do so by the checklist.
When enabling multi-path I/O for Windows Server 2003, use Microsoft iSCSI Software Initiator version 2.08 or later.
-
When enabling multi-path I/O for Windows Server 2008, use the Microsoft iSCSI Software Initiator version that is included with Windows Server 2008.
-
After the operating system installation > Post install configuration
Note: This is a new checklist item that goes at the end of the checklist in the iSCSI-attached integrated server installation road map topic.
- VMware ESX only: Action is required if you install on a server that uses just a BMC or IMM service processor (a System x without an RSA II or a BladeCenter blade) to prevent an abnormal shutdown of your server. See Note 16 (for servers with BMC) or Note 21 (for servers with IMM) on the BladeCenter and System x models supported with iSCSI page for details.
|
| |
|
|
|
