 |
Use the checklist below to step through the process of installing an IBM® BladeCenter® or System x™ model that is attached to an IBM i using iSCSI host bus adapters (iSCSI HBAs). You might want to print this page so that you can check off the tasks as you complete them.
Note: This checklist is for i5/OS i 5.4. For IBM i 6.1, see the iSCSI-attached integrated server installation road map in the IBM i 6.1 Information Center.
Last updated: 11 February 2008
| |
|
| |
Several preliminary tasks need to be performed to prepare yourself
and the IBM i environment before planning for and installing a specific iSCSI attached server.
These tasks can take a considerable amount of time to complete,
so you should normally perform the steps in this Prerequisites section
well before planning for and installing a specific iSCSI attached server.
- Follow the process described on this web page
The planning and installation process described on this web page
overrides information in the product documentation,
so it is important to closely follow the process described on this web page.
The order of the tasks listed in the following sections is also important, so
please resist the temptation to perform hardware installation or IBM i configuration tasks
until you get to the step below that instructs you to do those tasks.
Attention: The iSCSI planning and installation processes are significantly different than they were with the
Integrated xSeries Server (IXS) or Integrated xSeries Adapter (IXA) technologies.
- Ensure that you have access to required documentation
Many of the steps on this web page link to other required documents and are written
assuming that you have access to the Internet.
However, in some environments you might not have access to the Internet.
For example, some customer datacenters do not have a connection to the Internet.
If you will not have access to the Internet while performing all of the steps on this web page,
then you should gather the required documents ahead of time
so that you have them on-hand when you need to reference them.
The following list contains the key documents that you will need:
You should save these PDFs to your PC so that you can view them from your PC during the appropriate steps below.
Alternatively, you could print them and use the hardcopy printouts during the appropriate steps below.
In addition to the documents listed above, there are several key web pages
that you may want to download or print for reference:
Note: The above PDFs and web pages might change over time, so if you have previously saved or printed them,
please verify that you have the latest versions.
Finally, you should have on-hand the BladeCenter or System x hardware setup documents.
These documents are normally included in hardcopy form with your BladeCenter or System x model.
The actual document titles and contents will depend on your BladeCenter or System x hardware.
- Review iSCSI concepts
The
 BladeCenter or
System x iSCSI Installation Overview
Flash animation provides an overview of the iSCSI attached server installation process. It also provides a conceptual overview of the various hardware and software components and shows how they work together in the IBM i iSCSI solution.
The following diagram shows the basic iSCSI concept, where an
iSCSI target (IBM i) is connected to an
iSCSI initiator (BladeCenter blade or System x server) using an Ethernet network:
The following diagram shows the network connections between a System i i5/OS partition
and a hosted iSCSI attached BladeCenter blade or System x model:
The following diagram shows the IBM i configuration objects for the BladeCenter blade or System x model:
For more information, see the Concepts
section of the Windows environment on iSeries topic in the IBM i 5.4 Information Center
if you are not already familiar with the above diagrams and how BladeCenter blade and System x models are
integrated with the IBM i platform using iSCSI HBAs.
The Concepts topics referenced below
describe the above diagrams and many other topics related to iSCSI in more detail.
As you are reading the concepts information, note that the following functions are not currently supported:
- Microsoft® Cluster Service (MSCS) on iSCSI attached servers.
- Secure Sockets Layer (SSL) security for the service processor connection.
- IP Security (IPSec) on the iSCSI network.
- Routers on the iSCSI network.
For the iSCSI attached server planning and installation,
the highlighted concepts topics below are most important.
Read all of the concepts topics to gain a better understanding of additional server integration functions
and how the iSCSI technology compares to the IXS and IXA technologies.
As you are reading the concepts information, stay focused on the Concepts topics for now.
Other information center topics are referenced as needed later in the process described on this web page.
After reviewing the following Concepts topics,
return to this web page to continue with the planning and installation process:
___
Integrated server overview
___
Advantages
___
Terminology
___
Hardware concepts
___
Considerations
___
Performance
___
Networking concepts
___
Software concepts
___
High availability concepts
___
Security concepts
- Review iSCSI terminology cross-reference
Depending on the context, different terms are sometimes used to refer to similar items in this installation process.
The table below provides a cross-reference of key terms that have equivalent terms that might also be used:
| Hosted system |
BladeCenter blade or System x model |
| Host system |
IBM i |
| Network server description |
NWSD
(i5/OS object type *NWSD) |
| Network server host adapter |
NWSH
(i5/OS type *DEVD, subtype *NWSH) |
| Remote system configuration |
RMTSYS NWSCFG
(i5/OS type *NWSCFG, subtype *RMTSYS) |
| Service processor configuration |
SRVPRC NWSCFG
(i5/OS type *NWSCFG, subtype *SRVPRC) |
| Connection security configuration |
CNNSEC NWSCFG
(i5/OS type *NWSCFG, subtype *CNNSEC) |
SCSI Local adapter (MAC) address
(in remote system configuration) |
iSCSI
(on the iSCSI HBA label) |
LAN Local adapter (MAC) address
(in remote system configuration) |
TOE (TCP/IP offload engine)
(on the iSCSI HBA label) |
| iSCSI initiator system |
BladeCenter blade or System x model |
| iSCSI target system |
IBM i logical partition on a Power server |
| Initiator iSCSI HBA |
iSCSI HBA in an BladeCenter blade or System x model |
| Target iSCSI HBA |
iSCSI HBA in a IBM i |
For more information on many of these terms as well as other terms related to this product, see
Terminology (Windows environment on iSeries > Concepts > Terminology).
- Load required i5/OS products and firmware
Several i5/OS products are required when attaching BladeCenter or System x models with iSCSI HBAs. If this is the first iSCSI attached server being installed in the IBM i logical partition, you should verify that any required products are installed and install them now, if necessary.
IBM Director server must be installed on each IBM i logical partition that will be used to host iSCSI attached servers. This IBM Director server on IBM i instance is in addition to any IBM Director servers you might use for other distributed systems management tasks in your environment. Be sure to check the additional i5/OS products that are required by IBM Director, and install them if necessary.
Note that Windows Server 2003, VMware ESX Server 3 or SUSE Linux Enterprise Server 9 is a required product, but you will install it later as directed in the Operating system installation section.
For Windows, VMware ESX and Linux servers: Install the products listed in the
Software requirements (English version) topic
(Windows environment on iSeries > Install and configure > Software requirements).
Be sure to follow the links for installing IBM Director. If you will be installing VMware ESX or Linux on the integrated server, then in addition to the products listed in the Software Requirements topic above, also install product 5722-LSV IBM i5/OS Integration for Linux on xSeries.
The minimum server firmware required for the #5783 PCI-X iSCSI HBA Copper and #5784 PCI-X iSCSI HBA Fiber adapters are:
- For Model 520 Power5+ (Processor Features 8325, 8327, and 8330) the server firmware level must be 240_219 or later.
- For all other supported models and other 520 processor features,
the server firmware level must be the later of either 235_185 or the specific FW level
required for your model/processor (which can be found at
http://www-912.ibm.com/e_dir/eServerPrereq.nsf).
- Note: You can display the processor feature number of your Power server using the following IBM i command:
DSPSYSVAL QPRCFEAT
- Load latest required fixes (each time servers are installed)
IBM i PTFs are required when attaching BladeCenter or System x models with iSCSI HBAs.
Attention: Additional iSCSI-related fixes are released from time to time.
If it has been a while since you originally installed the required fixes, you should
perform this step again so that you have the latest fixes loaded.
Load the cumulative PTF package and individual PTFs that are listed on the
IBM i PTFs web page.
- Install iSeries Navigator on a PC
Use the iSeries Navigator GUI to perform i5/OS iSCSI configuration tasks, whenever possible.
iSeries Navigator is part of iSeries Access for Windows.
Attention: Use of iSeries Navigator is optional.
Almost all of the tasks that the GUI supports have CL command equivilants,
so you can use CL commands if you prefer to do so.
However, the CL command prompter has permanent restrictions that adversely affect prompting of some commands,
so the GUI is considerably easier to use for some tasks. See the
CRTNWSCFG and CHGNWSCFG Prompting Problems When defining more than one remote interface
troubleshooting topic for more information.
To install iSeries Navigator, perform the steps in the
Installing iSeries Navigator topic
(Connecting to iSeries > iSeries Navigator > Getting to know iSeries Navigator > Installing iSeries Navigator).
When installing iSeries Access, be sure to do either a Full install or do a Custom install
and select the following minimum set of iSeries Navigator components:
- Configuration and Service
- Network
- Integrated Server Administration
You should also install the latest iSeries Access service pack.
- Prepare i5/OS for use with integrated servers
Some general setup in IBM i should be performed before installing iSCSI attached servers.
For Windows servers: Perform the steps in the
Prepare for the installation of integrated Windows servers (English version) topic
(Windows environment on iSeries > Install and configure >
Prepare for the installation of integrated Windows servers).
Note: Unlike the IXS and IXA products, which primarily used memory in the IBM i machine pool,
the IBM i iSCSI HBA solution uses a combination of memory in the IBM i machine,
base and optional private memory pools.
Refer to the
System i Performance Capabilities Reference (1.6MB) for details.
See Chapter 17, Integrated BladeCenter® and System x™ Performance.
Under some workloads, iSCSI virtual disk I/O operations may adverseley
impact other IBM i applications that share the *BASE memory pool.
You can solve this by setting up a private memory pool for iSCSI to use.
See the iSCSI virtual I/O private memory pool subsection in Chapter 17 of the
System i Performance Capabilities Reference.
- Obtain server operating system install media
For Windows servers: Obtain Windows Server 2003 media that includes Service Pack 1.
iSCSI attached Windows servers require Windows install media (CD, DVD or IFS directory) with Service Pack 1 or later integrated with the base Microsoft® Windows Server™ 2003 installation image. If you have previously obtained the required install media, you can skip the remainder of this step.
Otherwise, obtain the required install media. 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.
For VMware ESX servers: Obtain VMware ESX Server 3.0.1 or 3.0.2 media.
Also obtain install media for the guest operating systems that you plan to run on the virtual machines that are hosted by the ESX server. For more information on supported guest operating systems, see the VMware Infrastructure 3 Documentation page.
If you have previously obtained the required install media, you can skip the remainder of this step. Otherwise, obtain the required install media.
For Linux servers: Obtain SUSE LINUX Enterprise Server 9 for AMD64 & Intel EM64T media. The base media (no service packs) and Service Pack 3 or later is required.
iSCSI attached Linux servers require 64-bit x86 version of SLES 9 install media (CD or DVD). If you have previously obtained the required install media, you can skip the remainder of this step. Otherwise, obtain the required install media.
|
| |
|
| |
Before starting the hardware installation, you should perform the following steps to
ensure that you have the necessary hardware and firmware updates on hand
and plan the hardware and networking configuration.
Before performing the steps below, you should be familiar with key concepts for iSCSI attached servers,
such as how the various hardware, software and networking pieces relate to each other in the iSCSI environment.
If necessary, refer to the
Review iSCSI concepts information in the
Prerequisites section before continuing.
- Obtain BladeCenter or System x hardware
If you have previously obtained BladeCenter blade or System x hardware
that is supported for use with the operating system you plan to install with this iSCSI solution, you can skip the remainder of this step.
Otherwise, review the
BladeCenter and System x models supported with iSCSI web page
to help you determine the BladeCenter blade or System x hardware you will use or to verify that the hardware you plan to use is supported with the operating system you plan to install.
Be sure to read the
Notes
that apply to the BladeCenter or System x model that you are using.
If necessary, obtain any BladeCenter or System x hardware that is required for your configuration.
- Obtain iSCSI host bus adapter hardware
Note: This step corresponds to slide 5 in the
BladeCenter or
System x iSCSI Installation Overview animation.
If you have previously obtained iSCSI host bus adapter (iSCSI HBA) hardware
that is supported for use with this iSCSI solution, you can skip the remainder of this step.
Otherwise, review the
iSCSI host bus adapter (iSCSI HBA) web page
to see the iSCSI HBAs that are supported and various configuration limits.
If necessary, obtain any iSCSI HBAs that are required for your configuration.
- Obtain Ethernet switches and cables
Note: This step corresponds to slide 6 in the
BladeCenter or
System x iSCSI Installation Overview animation.
If you have previously obtained the Ethernet switch hardware and associated cables
that are required for this iSCSI solution, you can skip the remainder of this step.
Otherwise, review the
Ethernet switches for iSCSI web page
to help you determine the Ethernet switches and Ethernet cables that you will need.
If necessary, obtain any Ethernet switches and Ethernet cables that are required for your configuration.
- Obtain firmware updates and drivers for your hardware
In the Hardware installation section later on, you will need to
install firmware updates for the hardware that you obtained in the previous steps.
To save time in the Install the BladeCenter or System x hardware, including iSCSI HBAs step later on,
you can optionally download the firmware updates ahead of time.
However, if you want to wait until the Install the BladeCenter or System x hardware, including iSCSI HBAs
step to download the firmware updates, you can skip the remainder of this step now.
For download instructions, see either the
Download BladeCenter or blade server firmware or
Download xSeries firmware section of the
iSCSI Host Bus Adapter for IBM BladeCenter or xSeries document (1.1MB).
Important note: The BladeCenter and System x initiator iSCSI HBAs must use exactly the level of BIOS and firmware specified in IBM i documentation and available for download via the Download iSCSI HBA firmware links referenced in Note 1 on the BladeCenter and System x models supported with iSCSI web page, even if a newer level is present in the initiator iSCSI HBA as shipped from the manufacturer. Only downloadable ISO images obtained from the above web page are supported. Any downloads from any other web sites are considered unsupported BIOS and firmware versions. Once the server installation is completed, future iSCSI HBA BIOS and firmware updates are released and can be installed via the IBM i PTF process. After the IBM i PTF containing the iSCSI HBA BIOS and firmware is loaded and applied to IBM i, install the BIOS and firmware in each integrated BladeCenter blade or System x server by following the service pack installation procedure described in the Installing IBM i integration service packs section of the Service packs web page.
Do not perform the hardware setup or update the firmware yet.
Wait until instructed to do those tasks in the Hardware installation step later on.
Also, in the Install additional device drivers step later on, you will need to
install device drivers for your hardware.
When you download the firmware updates as directed above,
you can usually use the same web site to download the latest device drivers for your system as well.
In particular, you should download drivers for:
The actual device drivers that you should download will vary based on the hardware
that is installed in your system and some of these may not apply to you.
Use the documentation that came with your system to determine what hardware
and optional adapters are installed in your system and what drivers are appropriate for them.
Also, a device driver that you need might not be listed on the web page where you downloaded the firmware updates as directed above.
If this is the case, refer to the documentation for that hardware for information on how to get the latest device driver.
- Plan the iSCSI network
Note: This step corresponds to slide 7 in the
BladeCenter or
System x iSCSI Installation Overview animation.
It is important to do thorough planning of your iSCSI environment before
starting to install and configure the hardware and software.
The planning information in this step will help you produce some worksheets to document
the key information that you will need in the later steps.
Fill out the iSCSI Network Planning Worksheets in the
iSCSI Network Planning Guide for IBM i 5.4 (300 KB) to plan for the installation.
The iSCSI Network Planning Worksheets should be filled out
before installing the hardware and installing the server from IBM i.
Configuration information in the hardware/firmware and in
i5/OS must be coordinated in order for the installation to succeed.
|
| |
|
| |
|
The steps in this section address:
- Installing the hardware that is required to run the server.
- Downloading and updating the BladeCenter or System x model firmware.
- Configuring the BladeCenter or System x BIOS, service processor and iSCSI HBA settings.
- Attaching all the cables that are needed.
Important: The IBM i iSCSI HBA and the PCI-X versions of the System x iSCSI HBA cards look identical,
but they have different firmware and function, so they are not interchangeable.
If you get them mixed up and use an iSCSI HBA in the wrong system, it will not work.
If you are not sure which system type a particular iSCSI HBA is for,
look for the following CCIN values on the tail stock of the iSCSI HBA card:
- 1986 (copper) or 1987 (fiber) for a System x iSCSI HBA.
- 573B (copper) or 573C (fiber) for a IBM i iSCSI HBA.
Before performing the steps below, you should already have the
iSCSI Network Planning Worksheets filled out.
If necessary, go back to the
Plan the iSCSI network section and fill out the worksheets before continuing.
- Install the IBM i iSCSI HBAs
Note: This step corresponds to slide 8 in the
BladeCenter or
System x iSCSI Installation Overview animation.
If new IBM i iSCSI HBAs need to be installed, perform the steps in the
PCI adapter topic (in the
System p5 and i5, eServer™ p5 and i5 and OpenPower™
PCI adapters document) to install the iSCSI HBAs in your Power server.
If your IBM i is partitioned,
make sure that the newly installed iSCSI HBAs are assigned to the IBM i logical partition
that will host the BladeCenter or System x models.
- Install the BladeCenter or System x hardware, including iSCSI HBAs
Note: This step corresponds to slides 8-10 in the
BladeCenter or
System x iSCSI Installation Overview animation.
Perform the steps in the Prepare your system section of the
iSCSI Host Bus Adapter for IBM BladeCenter or xSeries document (1.1MB) to
prepare your BladeCenter or System x model, update the firmware and configure the system.
This includes installing the iSCSI HBAs and updating the iSCSI HBA firmware.
Be sure to use the BladeCenter or System x service processor configuration information
from the iSCSI Network Planning Worksheets.
Do not hook up the cables or power on the server
until instructed to do so in the iSCSI Host Bus Adapter for IBM BladeCenter or xSeries document.
If you run into problems, see the
Troubleshooting web page.
- Configure the BladeCenter or System x iSCSI HBAs
Note: This step corresponds to slide 11 in the
BladeCenter or
System x iSCSI Installation Overview animation.
Perform the steps in the Configure iSCSI HBA section of the
iSCSI Host Bus Adapter for IBM BladeCenter or xSeries document (1.1MB) to
configure the iSCSI HBAs in your BladeCenter blade or System x model.
Important note: The BladeCenter and System x initiator iSCSI HBAs must use exactly the level of BIOS and firmware specified in IBM i documentation and available for download via the Download iSCSI HBA firmware links referenced in Note 1 on the BladeCenter and System x models supported with iSCSI web page, even if a newer level is present in the initiator iSCSI HBA as shipped from the manufacturer.
Be sure to use the BladeCenter or System x iSCSI HBA configuration information
from the iSCSI Network Planning Worksheets.
Do not hook up the cables or power on the server
until instructed to do so in the iSCSI Host Bus Adapter for IBM BladeCenter or xSeries document.
If you run into problems, see the
Troubleshooting web page.
- Cable the network
Note: This step corresponds to slide 12 in the
BladeCenter or
System x iSCSI Installation Overview animation.
Attach all of the cables as described in the Cable the network section of the
iSCSI Host Bus Adapter for IBM BladeCenter or xSeries document (1.1MB).
|
| |
|
| |
|
Before starting the operating system installation, you should perform the following
steps to prepare i5/OS for the install.
Before performing the steps below, you should already have installed the hardware, updated the firmware,
configured the BladeCenter blade or System x model and attached all the cables.
If necessary, go back to the
Hardware installation section and complete those tasks before continuing.
- Create an NWSH object for each new IBM i iSCSI HBA
Note: This step corresponds to slide 14 in the
BladeCenter or
System x iSCSI Installation Overview animation.
For each new IBM i iSCSI HBA that was installed above:
- Determine the IBM i hardware resource name that was assigned to the
newly installed iSCSI HBA.
Find the Network Server Host Adapter resource with
physical location values that match the location of the newly installed iSCSI HBA.
Use either of the following methods.
- iSeries Navigator:
- Expand Configuration and Service > Hardware > Communications.
- Display the Properties of each resource with the description Network Server Host Adapter.
- On the Physical Location tab of the property sheet,
look at the Frame ID and Card position values.
- IBM i command line:
- Run the following command to display a list of the communications resources:
WRKHDWRSC *CMN
- Use option 7=Display resource detail on each resource with the description Network Server Host Adapter.
- Examine the Location: entry to determine the frame ID and card position values.
For more information, see the
Work with Hardware Resources (WRKHDWRSC) command documentation.
Next, record the Network Server Host Adapter resource name (usually of the form "LINxx")
in item NH3 of the i5/OS Network Server Host Adapter Object Worksheet
(iSCSI Network Planning Guide > iSCSI Network Planning Worksheets >
i5/OS Network Server Host Adapter Object Worksheet).
- Create an i5/OS network server host adapter (NWSH) object.
Using the information you recorded on the i5/OS Network Server Host Adapter Object Worksheet
(iSCSI Network Planning Guide > iSCSI Network Planning Worksheets >
i5/OS Network Server Host Adapter Object Worksheet),
create the NWSH object using either of the following methods.
You can accept the default values for any items that are not listed in the worksheet.
- iSeries Navigator:
Perform the steps in the
Create a network server host adapter object topic
(Windows environment on iSeries > Administer connections to iSCSI attached servers >
Work with iSCSI configuration objects > Manage network server host adapters >
Create a network server host adapter object).
- IBM i command line:
- Type
CRTDEVNWSH and press F4 to display the command prompt screen.
- Fill in the command parameters and press Enter to run the command.
For more information, see the
Create Device Desc (NWSH) (CRTDEVNWSH) command documentation.
- Start the NWSH for each IBM i iSCSI HBA that the server will use
Start any NWSHs that will be used by the server so that they are available during the operating system installation.
Use either of the following methods:
- iSeries Navigator:
Perform the steps in the
Start a network server host adapter (English version) topic
(Windows environment on iSeries > Administer connections to iSCSI attached servers >
Work with iSCSI configuration objects > Manage network server host adapters >
Start a network server host adapter).
- IBM i command line:
Run the following command (where nwshname is your NWSH name):
VRYCFG CFGOBJ(nwshname) CFGTYPE(*DEV) STATUS(*ON)
For more information, see the
Vary Configuration (VRYCFG) command documentation.
After starting the NWSH, the NWSH status should be ACTIVE.
If you run into problems, see the
Troubleshooting web page.
- Ensure that the IBM Director server on IBM i is started
Perform the steps in the
Verify that IBM Director Server is installed and running (English version) topic
(Windows environment on iSeries > Administer connections to iSCSI attached servers > Remote server discovery and management > Verify that IBM Director Server is installed and running).
If the IBM Director server is not started, use either of the following methods to start it:
- iSeries Navigator:
- Open Network > Servers > User-Defined.
- Right-click IBM DIRECTOR and select Start.
- IBM i command line:
- Run the following command to start the IBM Director server:
STRTCPSVR SERVER(*DIRECTOR)
- For more information, see the
Start TCP/IP Server (STRTCPSVR) command documentation.
If the IBM Director server fails to start, see the IBM Director Fails to Start article in the Software Knowledge Base. If you run into other problems, see the Troubleshooting web page.
- Create a service processor configuration object
Note: This step corresponds to slide 15 in the
BladeCenter or
System x iSCSI Installation Overview animation.
If the i5/OS Service Processor Configuration Object Worksheet
(iSCSI Network Planning Guide > iSCSI Network Planning Worksheets >
i5/OS Service Processor Configuration Object Worksheet)
indicates that a new service processor configuration object needs to be created,
use the information from the worksheet to create it now using either of the following methods.
You can accept the default values for any items that are not listed in the worksheet.
- iSeries Navigator:
Perform the steps in the
Create a service processor configuration object (English version) topic
(Windows environment on iSeries > Administer connections to iSCSI attached servers >
Work with iSCSI configuration objects > Manage service processor network server configurations >
Create a service processor configuration object).
- IBM i command line:
- Type
CRTNWSCFG TYPE(*SRVPRC) and press F4 to display the command prompt screen.
- Press Enter once to display more parameters.
- Fill in the command parameters and press Enter again to run the command.
For more information, see the
Create NWS Configuration (CRTNWSCFG) command documentation.
Note: Creating this object now (rather than by using the install command later on) simplifies the install command inputs
and allows some validation of the object to be performed prior to its use during the install command.
This will make the operating system installation go smoother later on.
- Synchronize the service processor configuration
Both the service processor configuration and the BladeCenter or System x service processor
must contain the same user and password information so that IBM i can connect
to the service processor during the operating system installation.
Attention: On the iSeries Navigator panel and the IBM i command referenced below,
there are options to either initialize (*INIT) or synchronize (*SYNC)
the IBM i service processor configuration.
The initialize option is only needed when using SSL,
which is not currently supported, so you should use the synchronize option.
Using the service processor user and password from the
BladeCenter or System x Service Processor Worksheet
(iSCSI Network Planning Guide > iSCSI Network Planning Worksheets >
BladeCenter or System x Service Processor Worksheet),
synchronize the user and password from the BladeCenter or System x service processor
to the IBM i service processor configuration now using either of the following methods.
Note that the service processor user and password values are case sensitive.
- iSeries Navigator:
- Perform the steps in the
Initialize a service processor topic
(Windows environment on iSeries > Administer connections to iSCSI attached servers >
Work with iSCSI configuration objects > Manage service processor network server configurations >
Initialize a service processor) and use the Synchronize certificate from service processor option.
- Wait a few minutes.
- If the synchronize operation failed, a pop-up window with the IBM i job log messages is shown,
which indicates what the failure was.
- If a pop-up window is not shown within a few minutes, then the synchronize operation succeeded.
- IBM i command line:
- Type
INZNWSCFG and press F4 to display the command prompt screen.
- Type your service processor configuration name.
- Type
*SYNC for the processing option.
- Type the service processor user name and password.
- Press Enter to run the command.
For more information, see the
Initialize NWS Configuration (INZNWSCFG) command documentation.
The above synchronize operation will verify that:
- The correct service processor user and password are stored in the service processor configuration.
- The connection to the remote system service processor is physically cabled and configured properly.
If you run into problems, see the
Troubleshooting web page.
- Create a remote system configuration object
Note: This step corresponds to slide 16 in the
BladeCenter or
System x iSCSI Installation Overview animation.
If the i5/OS Remote System Configuration Object Worksheet
(iSCSI Network Planning Guide > iSCSI Network Planning Worksheets >
i5/OS Remote System Configuration Object Worksheet)
indicates that a new remote system configuration object needs to be created,
use the information from the worksheet to create it now using either of the following methods.
Note that you can accept the default values for any items that are not listed in the worksheet.
Also note that the CHAP name and CHAP secret values are case sensitive.
Note: Creating this object now (rather than by using the install command later on) simplifies the install command inputs
and allows some validation of the object to be performed prior to its use during the install command.
This will make the operating system installation go smoother later on.
If you created a new remote system configuration above and you specified the option to generate a CHAP secret,
display the generated CHAP secret now using either of the following methods:
- iSeries Navigator:
- Perform the steps in the
Display remote system configuration properties topic
(Windows environment on iSeries > Administer connections to iSCSI attached servers >
Work with iSCSI configuration objects > Manage remote system network server configurations >
Display remote system configuration properties).
- Click on the CHAP Authentication tab.
- IBM i command line:
Run the following command, where rmtsys is your remote system configuration name:
DSPNWSCFG NWSCFG(rmtsys) OPTION(*RMTSYS)
For more information, see the
Display NWS Configuration (DSPNWSCFG) command documentation.
Record the generated CHAP secret in item RS9
of the i5/OS Remote System Configuration Object Worksheet
(iSCSI Network Planning Guide > iSCSI Network Planning Worksheets >
i5/OS Remote System Configuration Object Worksheet).
Next, using the generated CHAP secret that was determined above,
perform the procedure described in the Change CHAP secret section of the
iSCSI Host Bus Adapter for IBM BladeCenter or xSeries document (1.1MB).
This will set the CHAP secret for the BladeCenter blade or System x iSCSI HBAs
to match the value in the remote system configuration.
- Verify the remote system connection and that the remote system is powered off or offline
Displaying the remote system status will verify that the connection to the remote system is working
and that the remote system is in a powered off or offline state (depending on which method is used below) before starting the operating system installation.
Display the remote system status for the remote system configuration that was created earlier
using either of the following methods:
- iSeries Navigator:
- Perform the steps in the
Display remote system status topic
(Windows environment on iSeries > Administer connections to iSCSI attached servers >
Work with iSCSI configuration objects > Manage remote system network server configurations >
Display remote system status).
- Verify that the remote system status is Powered off.
- IBM i command line:
- Run the following command:
WRKNWSCFG TYPE(*RMTSYS)
- Type 8=Work with status next to your remote system configuration name and press Enter.
- Verify that the remote system status is Offline.
For more information, see the
Create NWS Configuration (CRTNWSCFG) command documentation.
Note that a "not found" error when displaying the remote system status as directed above
could mean that IBM Director has not completed its system discovery process yet.
If this is the case, IBM Director should complete its system discovery process within a few minutes,
so try displaying the remote system status again. If you continue to get a "not found" error
or get some other error, see the
Troubleshooting web page.
If the remote system is not in a Powered off (Offline) state, power it off now before continuing.
If installing a blade, just the blade should be powered off, not the BladeCenter chassis.
- Create a connection security configuration object
Note: This step corresponds to slide 17 in the
BladeCenter or
System x iSCSI Installation Overview animation.
If the i5/OS Connection Security Configuration Object Worksheet
(iSCSI Network Planning Guide > iSCSI Network Planning Worksheets >
i5/OS Connection Security Configuration Object Worksheet)
indicates that a new connection security configuration object needs to be created,
use the information from the worksheet to create it now using either of the following methods.
You can accept the default values for any items that are not listed in the worksheet.
- iSeries Navigator:
Perform the steps in the
Create a connection security configuration object (English version) topic
(Windows environment on iSeries > Administer connections to iSCSI attached servers >
Work with iSCSI configuration objects > Manage connection security network server configurations >
Create a connection security configuration object).
- IBM i command line:
- Type
CRTNWSCFG TYPE(*CNNSEC) and press F4 to display the command prompt screen.
- Fill in the command parameters and press Enter to run the command.
For more information, see the
Create NWS Configuration (CRTNWSCFG) command documentation.
|
| |
|
| |
The steps in this section address preparing for and installing the operating system on the server:
- Plan for the server operating system installation
Note: This step corresponds to slide 18 in the
BladeCenter or
System x iSCSI Installation Overview animation.
For Windows servers, do the following:
To plan for the values that are used on the IBM i Install Windows Server (INSWNTSVR) command,
you can use either of these methods (read the Notes below before performing this step):
- Run the
Windows server installation advisor (English version)
(Windows environment on iSeries > Install and configure >
Plan for the installation of Windows > Windows server installation advisor).
The advisor provides an interactive web-based interface for determining the key INSWNTSVR parameter values.
Be sure to:
- Print off the Planning work sheet that is generated by the advisor.
- Copy the INSWNTSVR command string that is generated by the advisor and paste it to a file and save it.
The INSWNTSVR command string is used in a later step so that you
do not need to re-type all of the INSWNTSVR command parameters when you install Windows.
- Return here to continue with the following steps.
Do not run the INSWNTSVR command yet. It will be run in the next step.
- Print the
Installation worksheet for i5/OS parameters
(Windows environment on iSeries > Install and configure >
Plan for the installation of Windows > Installation worksheet for i5/OS parameters)
and fill it in. Then return here to continue with the following steps.
This worksheet provides information similar to what is produced by the Windows server installation advisor.
When using this worksheet, you will need to type in all of the parameter values on the INSWNTSVR command later.
For VMware ESX and Linux servers: Review the notes below then continue with the Start the installation from the IBM i console step.
Notes for both Windows (INSWNTSVR) and VMware ESX and Linux (INSLNXSVR) install command planning:
- Specify to use an existing service processor configuration.
Use the name from item SP1 in the i5/OS Service Processor Configuration Object Worksheet
(iSCSI Network Planning Guide > iSCSI Network Planning Worksheets >
i5/OS Service Processor Configuration Object Worksheet).
- Specify none for the service processor security initialization method,
since the service processor configuration was already synchronized in an earlier step.
- Specify to use an existing remote system configuration.
Use the name from item RS1 in the i5/OS Remote System Configuration Object Worksheet
(iSCSI Network Planning Guide > iSCSI Network Planning Worksheets >
i5/OS Remote System Configuration Object Worksheet).
- Windows servers only: Specify to use the full install type.
The basic (ServerGuide™) install type is not currently supported.
- Windows servers only: For the Windows source directory, use the IBM i optical device or IFS directory
that corresponds to the Windows install media that you obtained in the
Obtain server operating system install media step above.
- Windows servers only: 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.
- Specify to use an existing connection security configuration.
Use the name from item CS1 in the i5/OS Connection Security Configuration Object Worksheet
(iSCSI Network Planning Guide > iSCSI Network Planning Worksheets >
i5/OS Connection Security Configuration Object Worksheet).
- For both the storage path and the point to point virtual Ethernet LAN, use the network server host adapter name
from item NH1 in the i5/OS Network Server Host Adapter Object Worksheet
(iSCSI Network Planning Guide > iSCSI Network Planning Worksheets >
i5/OS Network Server Host Adapter Object Worksheet).
- Start the installation from the IBM i console
Note: This step corresponds to slides 19-22 in the
BladeCenter or
System x iSCSI Installation Overview animation.
When installing Windows on the iSCSI attached server,
you need the information produced by either of the planning methods in the
Plan for the server operating system installation step above:
- The Planning work sheet and the INSWNTSVR command string
that were generated by the Windows server installation advisor.
- The INSWNTSVR Installation worksheet for i5/OS parameters that you filled out.
When installing VMware ESX or Linux on the iSCSI attached server, just continue with the remainder of this step.
Attention: If you are installing on a blade in a BladeCenter,
you must assign the BladeCenter KVM and media tray
to the blade that you are installing to before running the INSWNTSVR or INSLNXSVR command.
Perform the steps in the appropriate topic below:
Note that the INSWNTSVR or INSLNXSVR command creates the network server description (NWSD) configuration object and the system drive for the server. The NWSD is then started (varied on) to boot the server and install the server operating system.
If you run into problems, see the
Troubleshooting web page.
- Continue the installation from the integrated server console
When the IBM i configuration is complete and the server OS installation starts on
the integrated server, the IBM i install command will prompt you to go to the server console to
complete the server OS installation process.
For Windows servers: Perform the steps in the
Continue the installation from the integrated Windows server console topic
(Windows environment on iSeries > Install and configure >
Install Windows 2000 Server or Windows Server 2003 >
Continue the installation from the integrated Windows server console).
For VMware ESX servers: Perform the steps in the Completing a VMware ESX installation on the integrated server topic in the VMware ESX Server on iSCSI attached integrated servers for IBM i 5.4 document.
For Linux servers: Perform the steps in the
Completing a SLES 9 SP3 (or later) install on iSCSI attached BladeCenter or xSeries topic
(Linux on an integrated xSeries solution > Completing the installation from the Linux console >
Completing a SLES 9 SP3 (or later) install on iSCSI attached BladeCenter or xSeries).
If you run into problems, see the
Troubleshooting web page.
|
| |
|
| |
After the server operating system is installed, perform the following tasks:
- Complete the server installation
Perform a few tasks to verify that the server is correctly installed and ready.
For Windows servers: Perform the steps in the
Complete the server installation topic
(Windows environment on iSeries > Install and configure >
Install Windows 2000 Server or Windows Server 2003 > Complete the server installation).
For VMware ESX servers: Perform the steps in the Running the post install utility topic in the | |
Windows environment on iSeries