File name: readme.txt
******************************************************************
| |
| IBM(R) ServerGuide(TM) Scripting Toolkit, Version 1.1.01 |
| |
| Part number 31R1035 |
| |
| (C) Copyright International Business Machines Corporation |
| 2003, 2004. All rights reserved. |
| |
| US Government Users Restricted Rights -- Use, duplication |
| or disclosure restricted by GSA ADP Schedule Contract with |
| IBM Corp. |
| |
| Notes: |
| o Before using this information and the product it supports, |
| read the general information under "NOTICES AND TRADEMARKS"|
| in this document. |
| o Check the ServerGuide Scripting Toolkit Web site for the |
| latest version of this readme. See "SUPPORT WEB SITES" for |
| more information. |
| |
| Updated 17 November 2004 |
| |
******************************************************************
1.0 Overview
2.0 Change history
2.1 ServerGuide Scripting Toolkit 1.1.01
2.2 ServerGuide Scripting Toolkit 1.1
2.3 ServerGuide Scripting Toolkit 1.0.02
2.4 ServerGuide Scripting Toolkit 1.0.01
2.5 ServerGuide Scripting Toolkit 1.0
3.0 Installation
4.0 Supported servers
4.1 Supported servers that might contain IBM ServeRAID(TM)
controllers
4.2 Supported servers that contain an integrated SCSI
controller with RAID capabilities based on the LSI 1020 or
LSI 1030 chipset
4.3 Supported servers that contain an LSI IDEal RAID controller
4.4 Supported servers that contain an IBM ServeRAID 7e
(Adaptec(R) HostRAID(TM)) controller
4.5 Supported servers that might contain a Fibre Channel
host bus adapter
5.0 Supported deployment scenarios
5.1 DOS-startable CD or DOS-startable diskette and data CD
5.2 DOS-startable diskette and network share
5.3 Remote Supervisor Adapter II or BladeCenter(TM) Management
Module and network share
5.4 Altiris Deployment Solution
5.5 Microsoft(R) Automated Deployment Services (ADS)
6.0 Supported operating systems
6.1 Windows(R) 2000 (Server and Advanced Server)
6.2 Windows Server 2003 (Standard, Enterprise, and Web
Editions)
6.3 Red Hat(R) Linux(R), Version 7.3
6.4 Red Hat Linux, Version 8.0
6.5 Red Hat Enterprise Linux AS, Version 2.1
6.6 Red Hat Enterprise Linux AS, Version 3
7.0 Solving ServerGuide Scripting Toolkit problems
7.1 Error reporting
7.2 Source system hangs during Linux deployment
7.3 Loadlin fails to start Linux installation
7.4 Problems with CD-based scenarios
7.5 Network-based installation on an eServer(R) BladeCenter
HS20, machine type 8832 with an LSI IDEal RAID controller
7.6 Unknown device in Windows Device Manager with xSeries 206,
machine type 8482 or xSeries 306, machine type 8836 and a
Remote Supervisor Adapter II installed
7.7 BladeCenter management module will not boot from ServerGuide
Scripting Toolkit image
7.8 Known BIOS problems
7.9 Fibre device driver installation fails for eServer BladeCenter
blade servers
7.10 Device drivers will not load for 3Com Ethernet adapter
7.11 Red Hat Enterprise Linux AS 3 may hang during USB module
insertion in xSeries 225, machine type 8649
7.12 Problem installing Red Hat Enterprise Linux to a BladeServer
that has control of the media tray
7.13 Problem installing Windows on an xSeries 345 server containing a ServeRAID-5i,
ServeRAID-4Mx, and ServeRAID-6M controller with ServeRAID BIOS 7.10.18
8.0 Additional files, utilities, and information
8.1 Selecting a network interface card (NIC) device driver
during a deployment scenario
8.2 Limitations
9.0 Support Web sites
10.0 Notices and trademarks
1.0 OVERVIEW
-------------
The ServerGuide Scripting Toolkit is a collection of
system-configuration tools and installation scripts that you can
use to deploy operating systems to your IBM eServer or xSeries(R)
server in a repeatable, predictable manner.
Translated versions of the licensing information and license
agreement for ServerGuide Scripting Toolkit are available from
the ServerGuide Scripting Toolkit Web site. See section 9.0,
"Support Web sites," for more information.
2.0 CHANGE HISTORY
-------------------
This section contains information about the ServerGuide Scripting ToolKit change history.
2.1 ServerGuide Scripting Toolkit 1.1.01
--------------------------------------
ServerGuide Scripting Toolkit 1.1.01 includes the following changes:
o Support for the following servers:
- xSeries 336, machine types 8837 and 1879
- xSeries 346, machine types 8840 and 1880
- eServer BladeCenter HS20, machine types 8843 and 1883
o Additional Altiris support:
- Support for Altiris Deployment Solution 6.1 SP1 for Windows
- Additions to Altiris Deployment Solutions for Windows version 6.0 and 6.1:
- New to Hardware Configuration Events:
- Capture RAID configuration
- Deploy RAID configuration
- Added operating system version specific installation events
- New to System Update Events:
- Windows Post-OS updates:
- Run the UpdateXpress RemoteUX utility to update drivers
- Run the UpdateXpress RemoteUX utility to update firmware
- Capture CMOS settings to a binary file
- Deploy CMOS settings from a binary file
- Perform IBM ServeRAID BIOS and firmware updates
- Additions to Altiris Deployment Solutions Linux version 5.6:
- New to Hardware Configuration Events:
- Capture RAID configuration
- Deploy RAID configuration
- Added operating system version-specific installation events
- New to System Update Events:
- Capture CMOS settings to a binary file
- Deploy CMOS settings from a binary file
- Perform IBM ServeRAID BIOS and firmware update
o Updated the ipssend.exe and ipssendl.exe utilities to version 7.10B
to support IBM ServerRAID 7k on the xSeries 346
o A workaround has been provided to prevent a target machine with a Remote
Supervisor Adapter-II from stopping when an operating system is being
cloned using the Altiris Deployment Solution (Windows or Linux). All
cloning jobs that are provided for the Altiris Deployment Solution have
been changed to use "text" mode.
2.2 ServerGuide Scripting Toolkit 1.1
--------------------------------------
ServerGuide Scripting Toolkit 1.1 included the following changes:
o New source tree directory structure to accommodate more
deployment scenarios
o Support for Altiris Deployment Solution for Windows 6.0 and 6.1
o Support for Altiris Deployment Solution for Linux 5.6 SP1
o Enhanced Microsoft ADS support
- Update the system BIOS
- Update the ServeRAID BIOS and Firmware
- Install the Windows Director Agent
o Support for Installing Red Hat Enterprise Linux AS 3.0
o Support for configuring Fibre Channel host bus adapters,
including the following:
- IBM TotalStorage FC2-133 Host Bus Adapter
- IBM HS20 Fibre Channel Expansion Card
- FAStT FC-2 Host Bus Adapter
o Enhanced support for configuring supported RAID controllers
and adapters, including the following:
- IBM ServeRAID 4H
- IBM ServeRAID 4Lx
- IBM ServeRAID 4Mx
- IBM ServeRAID 5i
- IBM ServeRAID 6i
- IBM ServeRAID 6i+
- IBM ServeRAID 6M
- IBM ServeRAID 7e (Adaptec HostRAID) SATA
- IBM ServeRAID 7e (Adaptec HostRAID) SCSI
- IBM ServeRAID 7t
- Integrated SCSI controllers with RAID capabilities based on
the LSI 1020 and LSI 1030 chipsets.
- LSI IDEal RAID controller in an IBM eServer BladeCenter
HS20, machine type 8832
o Updated most utilities to newer versions, for example:
- ipssend.exe is now at version 7.0
- Fixed intermittent hang in savestat.exe
- Added new command line options to clini.exe
o Support for installing Windows with a BladeCenter Management
Module virtual diskette
o Support for installing Director Agent with Windows
o Reworked environment variables to reduce DOS environment space
o Updated "IBM ServerGuide Scripting Toolkit User's Reference"
document
2.3 ServerGuide Scripting Toolkit 1.0.02
-----------------------------------------
ServerGuide Scripting Toolkit 1.0.02 included the following
changes:
o Support for the following servers:
- xSeries 206, machine type 8482
- xSeries 306, machine type 8836
- eServer BladeCenter HS40, machine type 8839
2.4 ServerGuide Scripting Toolkit 1.0.01
-----------------------------------------
ServerGuide Scripting Toolkit 1.0.01 included the following
changes:
o Support for the following servers:
- xSeries 225, machine type 8649
- eServer 325, machine type 8835
o Reduced DOS environment space usage
2.5 ServerGuide Scripting Toolkit 1.0
--------------------------------------
This was the first release of ServerGuide Scripting Toolkit.
3.0 INSTALLATION
-----------------
Instructions for unpacking the ServerGuide Scripting Toolkit files
are provided in the "IBM ServerGuide Scripting Toolkit User's
Reference." This guide is in Portable Document Format (PDF) and
requires Adobe Acrobat Reader to view it.
The source tree directory structure changed with the ServerGuide
Scripting Toolkit 1.1, so you cannot install over an earlier
version. Many environment variables in the usrvars.bat and
netvars.bat files also changed, so you cannot use existing
scripts.
Complete the following steps to upgrade to ServerGuide Scripting
Toolkit 1.1.01 from ServerGuide Scripting Toolkit 1.1:
1. From the installed Scripting Toolkit 1.1, delete the …\sgdeploy\sgtk directory
and all of its contents.
2. Unpack the new ServerGuide Scripting Toolkit 1.1.01 Package for the Web file
to the same location as the previous installation. During the unpacking process,
accept updates to the following files:
o …\sgdeploy\apps\appsdir.txt
o …\sgdeploy\apps\diragent\diragdir.txt
o …\sgdeploy\drvs\drvsdir.txt
o …\sgdeploy\os\osdir.txt
o …\sgdeploy\updates\updsdir.txt
When the package is unpacked,all of the distributed ServerGuide
Scripting Toolkit files are updated. Note that all custom files and
directories created under all of the other ServerGuide Scripting Toolkit directories
are preserved.
3. To update the Scripting Toolkit - Altiris sample jobs, do the following:
a. Rename the current “ServerGuide Toolkit - IBM BladeCenter / xSeries Support”
job set to “ServerGuide Toolkit - IBM BladeCenter / xSeries Support - Save
b. Import the new Scripting Toolkit - Altiris sample jobs binary.
c. Delete the original sample job set when you are done using it.
Complete the following steps to upgrade to ServerGuide Scripting
Toolkit 1.1 from ServerGuide Scripting Toolkit versions, 1.0, 1.0.01 and 1.0.02:
1. Unpack the new ServerGuide Scripting Toolkit 1.1, this will
create the new directory structure. The new Toolkit
directory is already present.
2. Move any operating system files to the new structure:
\stkfiles\os directories to \sgshare\sgdeploy\os
3. Move any update files to the new structure:
\stkfiles\updates directories to \sgshare\sgdeploy\updates
4. Move any ServerGuide device drivers to the new structure:
o \stkfiles\w2000drv\$oem$\$1\drv directories to
\sgshare\sgdeploy\drvs\w2k_drv
o \stkfiles\w2003drv\$oem$\$1\drv directories to
\sgshare\sgdeploy\drvs\w23_drv
Note: Use of old diskette images from ServerGuide Scripting
Toolkit 1.0 (all versions) is not supported with
ServerGuide Scripting Toolkit 1.1. The previous boot
images cannot be used because the directory names and
base directory structures have changed.
4.0 SUPPORTED SERVERS
----------------------
You can use the ServerGuide Scripting Toolkit to deploy
operating systems to the following IBM eServer and xSeries
servers:
o xSeries 205, machine type 8480
o xSeries 206, machine type 8482
o xSeries 225, machine type 8647
o xSeries 225, machine type 8649
o xSeries 235, machine type 8671
o xSeries 255, machine type 8685
o xSeries 305, machine type 8673
o xSeries 306, machine type 8836
o xSeries 335, machine type 8830
o xSeries 335, machine type 8676
o xSeries 336, machine type 8837, 1879
o xSeries 345, machine type 8670
o xSeries 346, machine type 8840, 1880
o xSeries 360, machine type 8686
o xSeries 365, machine type 8861
o xSeries 365, machine type 8862
o xSeries 440, machine type 8687
o xSeries 445, machine type 8870
o eServer 325, machine type 8835
o eServer BladeCenter HS20, machine type 8678
o eServer BladeCenter HS20, machine type 8832
o eServer BladeCenter HS20, machine type 8843, 1883
o eServer BladeCenter HS40, machine type 8839
Notes: o The ServerGuide Scripting Toolkit supports only
standalone xSeries 440, machine type 8687 and
xSeries 445, machine type 8870 servers.
o The device driver set from ServerGuide version 7.2.03
or later (if the newer ServerGuide release supports your
target server) is supported by ServerGuide Scripting
Toolkit version 1.1 or higher.
4.1 Supported servers that might contain IBM ServeRAID
controllers
-------------------------------------------------------
The following servers might contain ServeRAID controllers.
You can use utilities that come with the ServerGuide Scripting
Toolkit to configure ServeRAID controllers as part of the
deployment process.
o xSeries 205, machine type 8480
o xSeries 206, machine type 8482
o xSeries 225, machine type 8647
o xSeries 225, machine type 8649
o xSeries 235, machine type 8671
o xSeries 255, machine type 8685
o xSeries 305, machine type 8673
o xSeries 306, machine type 8836
o xSeries 335, machine type 8830
o xSeries 335, machine type 8676
o xSeries 336, machine type 8837, 1879
o xSeries 345, machine type 8670
o xSeries 346, machine type 8840, 1880
o xSeries 360, machine type 8686
o xSeries 365, machine type 8861
o xSeries 365, machine type 8862
o xSeries 440, machine type 8687
o xSeries 445, machine type 8870
o eServer 325, machine type 8835
4.2 Supported servers that contain an integrated SCSI controller
with RAID capabilities based on the LSI 1020 or LSI 1030
chipset
-----------------------------------------------------------------
The following servers contain an integrated SCSI controller with
RAID capabilities based on the LSI 1020 or LSI 1030 chipset. You
can use the cfg1030 utility that comes with the ServerGuide
Scripting Toolkit to configure these controllers as part of the
deployment process.
o xSeries 225, machine type 8647
o xSeries 225, machine type 8649
o xSeries 235, machine type 8671
o xSeries 335, machine type 8830
o xSeries 335, machine type 8676
o xSeries 336, machine type 8837, 1879
o xSeries 345, machine type 8670
o xSeries 365, machine type 8861
o xSeries 365, machine type 8862
o xSeries 445, machine type 8870
o eServer 325, machine type 8835
o eServer Bladecenter HS20, machine type 8678
o eServer BladeCenter HS20, machine type 8832
o eServer BladeCenter HS20, machine type 8843, 1883
o eServer BladeCenter HS40, machine type 8839
4.3 Supported servers that contain an LSI IDEal RAID controller
----------------------------------------------------------------
The following server contains an LSI IDEal RAID controller. You
can use the hypercfg utility that comes with the ServerGuide
Scripting Toolkit to configure this controller as part of the
deployment process:
o eServer BladeCenter HS20, machine type 8832
4.4 Supported servers that contain an IBM ServeRAID 7e (Adaptec
HostRAID) controller
----------------------------------------------------------------
The following servers contain an IBM ServeRAID 7e (Adaptec
HostRAID) controller. You can use the acuichsv utility to
configure a SATA controller, or the raidsel utility to configure a
SCSI controller, as part of the deployment process.
o xSeries 206, machine type 8482
o xSeries 306, machine type 8836
o xSeries 346, machine type 8840, 1880 (SCSI only)
4.5 Supported servers that might contain a Fibre Channel
host bus adapter
---------------------------------------------------------
The following servers might contain Fibre Channel host bus
adapters. You can use the fibrecfg utility that comes with the
ServerGuide Scripting Toolkit to configure Fibre Channel host bus
adapters as part of the deployment process.
o xSeries 225, machine type 8647
o xSeries 225, machine type 8649
o xSeries 235, machine type 8671
o xSeries 255, machine type 8685
o xSeries 305, machine type 8673
o xSeries 335, machine type 8830
o xSeries 335, machine type 8676
o xSeries 336, machine type 8837, 1879
o xSeries 345, machine type 8670
o xSeries 346, machine type 8840, 1880
o xSeries 360, machine type 8686
o xSeries 365, machine type 8861
o xSeries 365, machine type 8862
o xSeries 440, machine type 8687
o xSeries 445, machine type 8870
o eServer 325, machine type 8835
o eServer BladeCenter HS20, machine type 8678
o eServer BladeCenter HS20, machine type 8832
o eServer BladeCenter HS20, machine type 8843, 1883
o eServer BladeCenter HS40, machine type 8839
5.0 SUPPORTED DEPLOYMENT SCENARIOS
-----------------------------------
The ServerGuide Scripting Toolkit supports the following
deployment scenarios:
o DOS-startable CD or DOS-startable diskette and data CD
o DOS-startable diskette and network share
o Remote Supervisor Adapter II or BladeCenter Management Module
and network share
o Altiris Deployment Solution
o Microsoft Automated Deployment Services (ADS)
5.1 DOS-startable CD or DOS-startable diskette and data CD
-----------------------------------------------------------
You can use a DOS-startable diskette with a data CD to deploy
Microsoft Windows to all supported servers that have both a
diskette drive and a CD drive.
This includes all supported servers except the following:
o eServer BladeCenter HS20, machine type 8678
o eServer BladeCenter HS20, machine type 8832
o eServer BladeCenter HS20, machine type 8843, 1883
o eServer BladeCenter HS40, machine type 8839
You can use a DOS-startable CD to deploy Microsoft Windows to all
supported servers that have a CD drive.
This includes all supported servers except the following:
o eServer BladeCenter HS40, machine type 8839
Notes:
o (eServer BladeCenter HS20, machine type 8832 server) You can
use this deployment scenario to deploy Windows if the target
server has one of the following BIOS code levels installed:
- version 1.01 (part number 23K4695)
- version 1.04 (part number 26K9227)
If BIOS version 1.02 (part number 26K4905) is installed, the
deployment scenario fails.
o (eServer BladeCenter HS20, machine type 8678 server) You can
use this deployment scenario to deploy Windows if the target
server has one of the following BIOS code levels installed:
- version 1.05 (part number 25K9216)
- version 1.07 (part number 26K9217)
If BIOS version 1.06 (part number 26K3278) is installed, the
deployment scenario fails.
5.2 DOS-startable diskette and network share
---------------------------------------------
You can use a DOS-startable diskette with a network share to
deploy Microsoft Windows or Red Hat Linux to all supported servers
that have a diskette drive and access to a network share.
5.3 Remote Supervisor Adapter II or BladeCenter Management Module
and network share
------------------------------------------------------------------
You can use a virtual diskette to deploy Microsoft Windows to all
supported servers that contain a Remote Supervisor Adapter II, or
a BladeCenter Management Module. This includes the following
servers:
o xSeries 205, machine type 8480
o xSeries 206, machine type 8482
o xSeries 225, machine type 8649
o xSeries 235, machine type 8671
o xSeries 255, machine type 8685
o xSeries 305, machine type 8673
o xSeries 306, machine type 8836
o xSeries 336, machine type 8837, 1879
o xSeries 345, machine type 8670
o xSeries 346, machine type 8840, 1880
o xSeries 365, machine type 8861
o xSeries 365, machine type 8862
o xSeries 445, machine type 8870
o eServer BladeCenter HS20, machine type 8678
o eServer BladeCenter HS20, machine type 8832
o eServer BladeCenter HS20, machine type 8843, 1883
o eServer BladeCenter HS40, machine type 8839
Note: The xSeries 445, machine type 8870 is only supported when
a Remote Supervisor Adapter II-EXA is installed.
5.4 Altiris Deployment Solution
--------------------------------
You can use the ServerGuide Scripting Toolkit with the Altiris
Deployment Solution to deploy Microsoft Windows or Red Hat Linux
to all supported servers. The following versions of Altiris
Deployment Solution have been tested and are supported with this
version of the ServerGuide Scripting Toolkit:
o Altiris Deployment Solution for Linux, version 5.6 SP1
o Altiris Deployment Solution for Windows, version 6.0 (See note)
o Altiris Deployment Solution for Windows, version 6.1
o Altiris Deployment Solution for Windows, version 6.1 SP1
Note: The following servers are not supported by the Altiris Deployment
Solution for Windows, version 6.0:
o xSeries 206, machine type 8482
o xSeries 306, machine type 8836
o xSeries 336, machine type 8837, 1879
o xSeries 346, machine type 8840, 1880
o xSeries 440, machine type 8687
o xSeries 445, machine type 8870
o eServer BladeCenter HS20, machine type 8843, 1883
The following versions of Linux are supported for deployment with
the Altiris Deployment Solution:
o Red Hat Enterprise Linux AS 2.1 is supported by all versions of
the Altiris Deployment Solution.
o Red Hat Enterprise Linux AS 3.0 is supported by Linux DS 5.6 SP1,
Windows Deployment Solution 6.1, and Windows Deployment Solution 6.1 SP1
(Windows Deployment Solution 6.0 is not supported with Red Hat
Enterprise Linux AS 3.0).
5.5 Microsoft Automated Deployment Services (ADS)
--------------------------------------------------
You can use the ServerGuide Scripting Toolkit to configure supported RAID
adapters and controllers.
In some cases, performing a memory-intensive DOS-based task such as
updating the server BIOS code or IBM ServeRAID firmware code requires
more conventional memory (RAM) than is available after loading the
Microsoft ADS virtual boot diskette and the IBM ServerGuide Scripted
Toolkit with network connectivity. The following list shows a
representative sampling of server BIOS code updates using the
ServerGuide Scripted Toolkit with ADS that have been tested:
Old New
Model Name BIOS BIOS Status
8480 x205 1.45 1.47 pass
8482 x206 1.19 1.20 pass
8647 x225 1.37 1.40 fail
8670 x345 1.15 1.16 pass
8671 x235 1.12 1.13 pass
8673 x305 1.62 1.62 fail
Updating ServeRAID firmware using ServerGuide Scripting Toolkit
with ADS was verified on an xSeries 225, machine type 8647 with
a ServeRAID 4H RAID controller.
6.0 SUPPORTED OPERATING SYSTEMS
--------------------------------
You can use the ServerGuide Scripting Toolkit to deploy the
following operating systems to supported servers:
o Windows 2000 (Server and Advanced Server)
o Windows Server 2003 (Standard, Enterprise, and Web Editions)
o Red Hat Linux, Version 7.3
o Red Hat Linux, Version 8.0
o Red Hat Enterprise Linux AS, Version 2.1
o Red Hat Enterprise Linux AS, Version 3
You can use the ServerGuide Scripting Toolkit to deploy the
English, French, German, Italian, Spanish, and Swedish language
versions of Microsoft Windows.
6.1 Windows 2000 (Server and Advanced Server)
----------------------------------------------
You can deploy Windows 2000 (Server and Advanced Server) to all
supported servers, except the following:
o eServer 325, machine type 8835
6.2 Windows Server 2003 (Standard, Enterprise, and Web Editions)
-----------------------------------------------------------------
You can deploy Windows Server 2003 (Standard, Enterprise, and Web
Editions) to all supported servers.
Note: The eServer 325, machine type 8835 supports only the 32-bit
version of Windows Server 2003, Enterprise Edition.
6.3 Red Hat Linux, Version 7.3
-------------------------------
You can deploy Red Hat Linux, Version 7.3 to the following
supported servers:
o xSeries 205, machine type 8480*
o xSeries 225, machine type 8647*
o xSeries 225, machine type 8649*
o xSeries 235, machine type 8671*
o xSeries 255, machine type 8685
o xSeries 305, machine type 8673*
o xSeries 335, machine type 8830*
o xSeries 335, machine type 8676*
o xSeries 345, machine type 8670
o xSeries 360, machine type 8686*
o eServer BladeCenter HS20, machine type 8678
The operating system is certified by the vendor for the servers
marked with an asterisk (*). It is not formally supported by
IBM.
6.4 Red Hat Linux, Version 8.0
-------------------------------
You can deploy Red Hat Linux, version 8.0 to the following
supported servers:
o xSeries 205, machine type 8480*
o xSeries 225, machine type 8647*
o xSeries 225, machine type 8649*
o xSeries 235, machine type 8671*
o xSeries 255, machine type 8685*
o xSeries 305, machine type 8673
o xSeries 335, machine type 8676
o xSeries 345, machine type 8670
o xSeries 360, machine type 8686
o eServer Bladecenter HS20, machine type 8678
The operating system is certified by the vendor for the servers
marked with an asterisk (*). It is not formally supported by
IBM.
6.5 Red Hat Enterprise Linux AS, Version 2.1
---------------------------------------------
You can deploy Red Hat Enterprise Linux AS, Version 2.1 to all
supported servers.
6.6 Red Hat Enterprise Linux AS, Version 3
-------------------------------------------
You can deploy Red Hat Enterprise Linux AS, Version 3 to all
supported servers.
7.0 SOLVING SERVERGUIDE SCRIPTING TOOLKIT PROBLEMS
---------------------------------------------------
This section contains information about solving problems
that might occur as you use ServerGuide Scripting Toolkit.
7.1 Error reporting
--------------------
Each DOS batch file (sample scripts) performs a task, calls other
ServerGuide Scripting Toolkit utilities to perform a task, or
calls other batch files to perform a task. The ServerGuide
Scripting Toolkit performs limited error-checking using the return
codes from the utilities that are called. Persistent-state
information is used to communicate errors, which are otherwise
cleared, that are returned from other batch files.
Note: No log files are created by the ServerGuide Scripting
Toolkit to report errors.
When an error is encountered, the batch file currently in-process
stops and displays an error message. If more than one batch file
is in-process, each file will report an error message. You must
correct the problem; then, restart the deployment scenario.
Attention: When you restart a deployment scenario after an error
is encountered, the process always starts from the
beginning. It does not resume from the last task
correctly performed.
7.2 Source system hangs during Linux deployment
------------------------------------------------
When you are deploying Red Hat Enterprise Linux AS, Version 2.1
from a source system running Microsoft Internet Information
Services (IIS), the source system might appear to hang. To solve
this problem, disable the IIS HTTP Keep-Alive feature.
7.3 Loadlin fails to start Linux installation
----------------------------------------------
Loadlin might fail to start the Linux installation if the
parameter file contains more than 256 characters. By default, the
maximum command-line length that can be passed to the kernel is
256 characters. See the Loadlin documentation for information
about changing the Linux kernel command-line length.
7.4 Problems with CD-based scenarios
-------------------------------------
When you create a CD for a deployment scenario, be sure to enable
all DOS 8.3 character file names in the ISO image. Otherwise,
file names that contain characters such as the tilde (~), dollar
sign ($), and number sign (#) might be renamed and cause the
CD-based deployment scenario to fail.
7.5 Network-based installation on an eServer BladeCenter HS20,
machine type 8832 with an LSI IDEal RAID controller
---------------------------------------------------------------
You must use hypercfg version 3.6 when performing a network-based
installation on an eServer BladeCenter HS20, machine type 8832
with an IDE RAID controller.
To obtain the latest version of this utility, go to the IBM
Support Page and search for "LSI Hyper Configuration Utility" for
the eServer BladeCenter HS20, machine type 8832.
Note: You can search specifically for hypercfg version 3.6, by
the part number 26K9152.
7.6 Unknown device in Windows Device Manager with xSeries 206,
machine type 8482 or xSeries 306, machine type 8836 and a
Remote Supervisor Adapter II installed
---------------------------------------------------------------
When an IBM Remote Supervisor Adapter II is installed in either an
xSeries 206, machine type 8482 or xSeries 306, machine type 8836,
the list of devices in the Windows Device Manager might contain an
unknown device. This is expected, and a future Automatic Server
Restart driver will remove this item from the list of devices.
7.7 BladeCenter management module will not boot from ServerGuide
Scripting Toolkit image
-----------------------------------------------------------------
If the BladeCenter management module will not boot the ServerGuide
Scripting Toolkit virtual-floppy diskette image, make sure that
there is no diskette in the diskette drive of the BladeCenter unit.
If there is a diskette in the diskette drive of the BladeCenter
unit, the BladeCenter management module might boot from this
diskette instead of from the ServerGuide Scripting Toolkit
virtual-floppy diskette image.
7.8 Known BIOS problems
------------------------
This section contains information about known BIOS problems
involving the ServerGuide Scripting Toolkit.
7.8.1 eServer xSeries 205 Type 8480, BIOS version 1.47,
build ID JPE147A
--------------------------------------------------------
If the BIOS update loops continuously and does not get past the
update portion of its processing, edit the lcreflsh.bat BIOS file.
o lcreflsh.bat is located in the following directory, if the
ServerGuide Scripting Toolkit was setup using the default
settings:
\sgshare\sgdeploy\updates\8480\BIOS
o Edit the lcreflsh.bat file to remove the /r flag. The revised
file should have the following line:
flash2 /i:flashfil.fls /v /u
Save changes to the file; then, start the Toolkit process.
7.8.2 eServer xSeries 225 Type 8647, BIOS version 1.40,
build ID OPE140A
--------------------------------------------------------
If the "Insufficient memory" message is displayed when flashing
BIOS over a network, the BIOS update did not take place even
though the process appears to have completed successfully.
The update can be performed with BIOS version 1.37 or
build ID OPE137A.
7.8.3 eServer xSeries 225 Type 8649, BIOS version 1.05,
build ID OQE105A
--------------------------------------------------------
If the "Insufficient memory" message is displayed when flashing
BIOS over a network, the BIOS update did not take place even
though the process appears to have completed successfully.
The update can be performed with BIOS version 1.04 or
build ID OQE104A.
7.8.4 eServer 325 Type 8835, BIOS version 1.28, build ID M1E128A
-----------------------------------------------------------------
If the "Cannot flash if Memory Managers (e.g. HIMEM) present"
message is received when flashing BIOS to version 1.28, edit the
lcreflsh.bat BIOS file.
o lcreflsh.bat is located in the following directory, if the
ServerGuide Scripting Toolkit was setup using the default
settings:
\sgshare\sgdeploy\updates\8835\BIOS
o Add the following line to the lcreflsh.bat file:
phlash16.exe /x /p /s /exit flashfil.fls
Save changes to the file; then, start the Toolkit process.
7.8.5 eServer xSeries 445 Type 8870, BIOS version 1.15,
build ID REJT42B
--------------------------------------------------------
The system hangs at the "Starting PC DOS" prompt while it is booting when
a Remote Supervisor Adapter (RSA) II card is installed.
The system functions correctly with BIOS version 1.12 or build ID REJT37A.
7.8.6 eServer xSeries 360 Type 8686, BIOS 1.12, build ID RUKT56A
-----------------------------------------------------------------
Attempting to upgrade from server BIOS code version 1.12
(build ID RUKT56A) using the ServerGuide Scripting Toolkit
integrated with the Altiris Deployment Solution (Windows or Linux)
is not supported.
If updating from server BIOS code version 1.12 using the Altiris
integration, the procedure might hang during the "Erasing"
portion of the system BIOS code update and might damage the system
BIOS code.
If you have already attempted this procedure, it might be possible to
restore your system BIOS from the backup location if it has been
damaged. See the eServer xSeries 360 Type 8686 Hardware Maintenance
Manual for information about restoring BIOS from the backup location.
Updating from other versions of the server BIOS code using this
deployment method, or any other ServerGuide Scripting Toolkit
deployment method, is supported.
7.8.7 eServer xSeries 206 Type 8482, BIOS version 1.20,
build ID KEE120A
--------------------------------------------------------
This server BIOS code update is not supported when it is included
as part of the DOS-startable CD deployment scenario. This update
is supported by all other deployment methods, including the
DOS-startable diskette and data CD.
If you include this server BIOS code update with the DOS-startable
CD scenario, the ServerGuide Scripting Toolkit process might hang
at the "Running system BIOS update ..." prompt.
7.9 Fibre device driver installation fails for eServer BladeCenter
blade servers
-------------------------------------------------------------------
The directory name of the fibre device driver for Windows Server 2003
taken from a ServerGuide CD version 7.2 04 or earlier has nine
characters: file names in DOS are limited to eight characters. The
directory name and references to it must be renamed to meet the DOS
eight-character naming limitation for it to work with the ServerGuide
Scripting Toolkit.
When using the device driver set from ServerGuide version 7.2.04 or
earlier to install Windows Server 2003 onto a fibre device in an eServer
BladeCenter blade server, the following change must be made to the
driver set:
1. Go to the directory that contains the Windows Server 2003 device
driver set.
Note: If the ServerGuide Scripting Toolkit was set up using the
default values, this directory would be:
\sghare\sgdeploy\sgtk\drvs\w23_drv\ql23hs20
2. Rename the directory hs20_2003 to a DOS compliant name
(maximum of eight characters in the name with up to three characters
for the extension), such as: hs20_2K3.
3. Edit the drvinfo.ini file and change the path parameter to match the
directory name used in step 2. For example, hs20_2k3\txtsetup.oem.
7.10 Device drivers will not load for 3Com Ethernet adapter
-----------------------------------------------------------
The 3Com Ethernet device driver available from the 3Com Website is
combined with the Dynamic Access software on a single diskette. The
ServerGuide Toolkit is unable to load the device driver from this
combined image.
The 3Com Ethernet device driver that is available from the IBM Support
Website is packaged separately from the Dynamic Access software. If
the device driver fails to load, download the device driver that is
packaged by itself, without the Dynamic Access software. If you are
unable to download the device driver by itself, delete the DASetup.exe
file from the root of the combined driver diskette prior to scanning
the driver with DScan.
7.11 Red Hat Enterprise Linux AS 3 may hang during USB module
insertion in xSeries 225, machine type 8649
-------------------------------------------------------------
Installation of Red Hat Enterprise Linux AS 3 may hang during USB
module insertion in the xSeries 225, machine type 8649. To prevent
this problem, make the following change to the LOADLIN parameter
file generation section of the INSTOS.BAT file in the
sgdeploy\sgtk\examples\linux directory:
Before change:
echo /dev/ram rw initrd=%IRD_PATH%\%IRD_FILE% >> %RAMDSK%\
LOADLIN.PAR
After change:
echo /dev/ram rw initrd=%IRD_PATH%\%IRD_FILE% nousb >> %RAMDSK%\
LOADLIN.PAR
7.12 Problem installing Red Hat Enterprise Linux to a blade server
that has control of the media tray
------------------------------------------------------------------
There might be a problem installing Red Hat Enterprise Linux to a
BladeServer if the blade server has control of the media tray
(currently has access to the CD and floppy drive).
To solve this problem, move control of the media tray to another
blade server or make the following change to the LOADLIN parameter
file generation section of the INSTOS.BAT file in the
sgdeploy\sgtk\examples\linux directory:
Before change:
echo /dev/ram rw initrd=%IRD_PATH%\%IRD_FILE% >> %RAMDSK%\
LOADLIN.PAR
After change:
echo /dev/ram rw initrd=%IRD_PATH%\%IRD_FILE%
nousbstorage >> %RAMDSK%\LOADLIN.PAR
7.13 Problem installing Windows on an xSeries 345 server containing a ServeRAID-5i,
ServeRAID-4Mx, and ServeRAID-6M controller with ServeRAID BIOS 7.10.18
-----------------------------------------------------------------------------------
The installation might fail during the second boot of the Windows installation program
(after the ServerGuide Scripting Toolkit scripts have been completed) if you configure
these RAID controllers using the Toolkit RAID configuration script files.
To solve this problem, use one of the following workarounds:
o Use the ServeRAID Support CD to configure your ServeRAID controllers instead of using the
ServerGuide Scripting Toolkit RAID configuration scripts as part of the installation process.
o Remove one of the controllers during the deployment process, and configure the adapter manually after the
deployment process is complete.
8.0 ADDITIONAL FILES, UTILITIES, AND INFORMATION
-------------------------------------------------
This section contains information that is not documented in the
"IBM ServerGuide Scripting Toolkit User's Reference."
8.1 Selecting a network interface card (NIC) device driver
during a deployment scenario
-----------------------------------------------------------
If you use one of the following deployment scenarios, you must
select the device driver for the NIC when you start the target
server from the DOS-startable (bootable) diskette:
o Using a DOS-startable diskette and network share
o Using a Remote Supervisor Adapter II and network share
If the target server is an xSeries 440, machine type 8687, be sure
to select "Broadcom NDIS network driver (xSeries 440 only)". If
the target server is an eServer BladeCenter HS20, machine type
8832, be sure to select "Broadcom NDIS network driver (B57)".
If the target server requires a Broadcom device driver and is
neither an xSeries 440, machine type 8687 server nor an eServer
BladeCenter HS20, machine type 8832 server, you can select either
of the two Broadcom device drivers.
8.2 Limitations
----------------
The following limitations are applicable to this version of the
ServerGuide Scripting Toolkit:
o The "altboot /b" command requires the following BIOS versions
and build IDs on the following servers:
- xSeries 225, machine type 8647: BIOS version 1.40
(build ID OPE140A) or later
- xSeries 225, machine type 8649: BIOS version 1.07
(build ID OQE107A) or later
o The emm386.exe expanded memory device driver is not supported
by the ServerGuide Scripting Toolkit. The following utilities
and functions are incompatible with this device driver:
- hwdetect.exe
- savestat.exe
- BIOS code updates
- Firmware code updates
o Linux operating systems are case-sensitive. Make sure that the
case of the file and directory names matches the corresponding
reference in any command sequence that refers to them, such as
command sequences in usrvars.bat and netvars.bat files.
ex. The default installation directory for ServerGuide
Scripting Toolkit files is "sgdeploy", so the TKDIR
variable in usrvars.bat must be set to "sgdeploy" and not
"SGDEPLOY".
o Enabling and then either configuring or installing to the LSI
IDEal RAID devices on the eServer BladeCenter HS40, machine
type 8839 is not supported by the ServerGuide Scripting Toolkit.
o When installing Linux on an xSeries 206, machine type 8482, only
Red Hat Enterprise Linux AS 3 U2 or later is supported.
o The ServerGuide Scripting Toolkit supports the installation of
only IBM Director Agent 4.20 or later.
o The capture and deployment of CMOS settings is not supported on
an eServer 325, machine type 8835.
o When you deploy CMOS settings from a binary file on an
xSeries 365 (8861) using BIOS 1.08 (RDJT28a), the restore boot
order function does not work correctly.
9.0 SUPPORT WEB SITES
----------------------
The following Web pages provide resources for understanding,
using, and troubleshooting IBM deployment and systems-management
software:
o IBM Remote Deployment Manager page
http://www.ibm.com/servers/eserver/xseries/systems_management/
sys_migration/rdm.html
This Web page provides an overview of IBM Remote Deployment
Manager.
o IBM ServerGuide page
http://www.ibm.com/pc/ww/eserver/xseries/serverguide/index.html
This Web page provides an overview of ServerGuide.
o IBM ServerGuide Scripting Toolkit page
http://www.ibm.com/pc/support/site.wss/
document.do?lndocid=MIGR-53564
This Web page provides an overview of the ServerGuide Scripting
Toolkit. You can download the latest version of the ServerGuide
Scripting Toolkit readme.txt file here.
o IBM ServerProven(R) page
http://www.ibm.com/pc/us/compat/index.html
This Web page provides compatibility information about
hardware, software, and middleware.
o IBM Support page
http://www.ibm.com/pc/support/
This is the IBM Support Web site for IBM hardware and
systems-management software.
o IBM Systems Management Software: Download/Electronic Support
page
http://www.ibm.com/pc/us/eserver/xseries/systems_management/
dwnl.html
Use this Web page to download IBM systems-management software,
including the ServerGuide Scripting Toolkit.
o IBM UpdateXpress page
http://www-1.ibm.com/servers/eserver/xseries/
systems_management/sys_migration/xpress.html
This Web page provides an overview of UpdateXpress. It also
contains links to pages from which you can download
UpdateXpress, order an UpdateXpress CD, or purchase a
subscription from a vendor other than IBM.
o IBM xSeries Systems Management page
http://www.ibm.com/pc/ww/eserver/xseries/systems_management/
index.html
This Web page provides an overview of IBM systems-management
software.
10.0 NOTICES AND TRADEMARKS
----------------------------
INTERNATIONAL BUSINESS MACHINES CORPORATION PROVIDES THIS
PUBLICATION "AS IS" WITHOUT WARRANTY OF ANY KIND, EITHER EXPRESS
OR IMPLIED, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES
OF NON-INFRINGEMENT, MERCHANTABILITY OR FITNESS FOR A PARTICULAR
PURPOSE. Some jurisdictions do not allow disclaimer of express or
implied warranties in certain transactions, therefore, this
statement may not apply to you.
This information could include technical inaccuracies or
typographical errors. Changes are periodically made to the
information herein; these changes will be incorporated in new
editions of the publication. IBM may make improvements and/or
changes in the product(s) and/or the program(s) described in this
publication at any time without notice.
The following terms are trademarks of the IBM Corporation in the
United States, other countries, or both:
BladeCenter
eServer
IBM
ServerGuide
ServerProven
ServeRAID
xSeries
Adaptec and HostRAID are trademarks of Adaptec, Incorporated, in
the United States, other countries, or both.
Intel, Intel Inside (logos), MMX and Pentium are trademarks of
Intel Corporation in the United States, other countries, or both.
Linux is a trademark of Linus Torvalds in the united states, other
countries, or both.
Microsoft and Windows are trademarks of Microsoft Corporation in
the United States, other countries, or both.
Red Hat, the Red Hat "Shadow Man" logo, and all Red Hat-based
trademarks and logos are trademarks or registered trademarks of
Red Hat, Inc., in the United States and other countries.
Other company, product, or service names may be trademarks or
service marks of others.
Download Driver Pack
After your driver has been downloaded, follow these simple steps to install it.
Expand the archive file (if the download file is in zip or rar format).
If the expanded file has an .exe extension, double click it and follow the installation instructions.
Otherwise, open Device Manager by right-clicking the Start menu and selecting Device Manager.
Find the device and model you want to update in the device list.
Double-click on it to open the Properties dialog box.
From the Properties dialog box, select the Driver tab.
Click the Update Driver button, then follow the instructions.
Very important: You must reboot your system to ensure that any driver updates have taken effect.
For more help, visit our Driver Support section for step-by-step videos on how to install drivers for every file type.