ServerGuide Scripting Toolkit Version 1.3.07 Readme

                                                              
  IBM(R) ServerGuide(TM) Scripting Toolkit, Version 1.3.07      
                                                              
  (C) Copyright International Business Machines Corporation     
    2003-2008. 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
     for more information.                                          
                                                              
  o  Check the ServerGuide Scripting Toolkit Web site for the      
     latest version of this readme. See Support Web sites for 
     more information.                                          
                                                             
  Updated 23 January 2008                                      
                                                            

Table of contents

What's new in 1.3.07

Back to TOC

Support for the following hardware:

Support for the following RAID controllers:

Supported hardware and operating systems

Back to TOC

This section lists changes in supported hardware and operating systems and network device driver compatibility since the latest release of the IBM ServerGuide Scripting Toolkit Users Guide. Please consult the Users Guide for a complete list of supported hardware, operating systems, and network device driver compatibility.

Supported Deployment Scenarios

Back to TOC

The ServerGuide Scripting Toolkit supports the following deployment scenarios:

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:

Note: You cannot use this method on any server with both a USB-connected diskette drive and a USB-connected CD-ROM drive.

You can use a DOS-startable CD to deploy Microsoft Windows to all supported servers that have a CD drive.

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.

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 all supported servers except the following:

Note: The xSeries 445, machine type 8870 is supported only when a Remote Supervisor Adapter II-EXA is installed.

Altiris Deployment Solution

You can use the ServerGuide Scripting Toolkit with the Altiris Deployment Solution to deploy Microsoft Windows, Red Hat Enterprise Linux, or SUSE Linux Enterprise Server to all supported servers. The following versions of Altiris Deployment Solution are supported with this version of the ServerGuide Scripting Toolkit:

Notes:

  1. Altiris 6.5 requires SP1 when using Version 1.3.03 or higher of the ServerGuide Scripting Toolkit with RemoteUX.
  2. The ServerGuide Scripting Toolkit does not support WinPE or FreeDOS boot environments with Altiris Deployment Solution for Windows, version 6.5.
  3. The AMD Opteron for IBM BladeCenter models LS21 and LS41, machine types 7971 and 7972 are not supported with Altiris when configured with the Blade Storage and the I/O Expansion Unit.
  4. The System x3755 machine type 8877 and System x3655 machine type 7985 are not supported with Altiris when configured with the ServeRAID 8k or ServeRAID 8k-l.
  5. The Altiris Agent for Windows application provided in Altiris Deployment Solution 6.5 service pack 1 will not install properly on Windows Server 2003 Web Edition.
  6. The Altiris Deployment Solution jobs "Capture CMOS settings" and "Deploy CMOS settings" are not supported on the System x3105 machine type 4347.
  7. Altiris Deployment Solution does not support cloning for VMware ESX Server.

Microsoft Automated Deployment Services (ADS)

You can use the ServerGuide Scripting Toolkit to configure supported RAID adapters and controllers.

Notes:

  1. 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.
  2. Updating ServeRAID firmware using the ServerGuide Scripting Toolkit with ADS was verified on an xSeries 225 (x225), machine type 8647 with a ServeRAID 4H RAID controller.
  3. The IBM System x3455, machine types 7984 and 7986 and IBM System x3755, machine type 8877 are unable to install the Director Agent through Microsoft ADS. All other ADS tasks are unaffected.

Solving ServerGuide Scripting Toolkit Problems

Back to TOC

This section contains updates to information on solving ServerGuide Scripting Toolkit Problems developed since the publication of the IBM ServerGuide Scripting Toolkit Users Guide. Please consult the Users Guide for a full list of known solutions to ServerGuide Scripting Toolkit problems.

IBM BladeCenter HS21 (machine types 8853, 1885) hangs at DHCP for Linux deployments

The IBM BladeCenter HS21 (machine types 8853, 1885) cannot receive an IP address via DHCP when starting a Linux deployment using eth0 as the deployment NIC. To solve this problem, change the value of the variable "DPY_NIC" to eth1 in USRVARS.BAT or in the Altiris deployment job.

Multiple systems: Altiris hangs on "Transferring control to DOS"

This problem affects the following systems:

This is currently a limitation for the System x3655 and System x3755. This problem will be corrected by future BIOS updates.

For the AMD Opteron LS21 and LS41 for BladeCenter, this problem can be corrected by updating the BIOS to BAE122DUS or higher.

IBM Blade Center HS20(8843,1883)loses networking after UpdateXpress System Pack 1.0 update on Windows 2000

The Intel(R) Chipset Software Installation Utility delivered with UXSP 1.0 causesthe networking subsystem to fail. This affects the Altiris UXSP post job, causing the agent to fail to return to the Deployment Server the last message.

To avoid this problem, insert a restart command at the end of the post job script.

Altiris UXSP Job taking an extended period on RHEL3U8 (32-bit)

The Altiris UpdateXpress System Pack Installer job can take up to 25 minutes when executing on RHEL3U8 (32-bit) when run from a samba share.

There is currently no workaround for this problem.

RAID CAPTURE fails and hangs on "Improper syntax for the following parameter."

Using PRAID.exe in capture mode (praid /c ) to capture a configuration on an IBM xSeries 346 containing a ServeRAID 4H controller in the Altiris environment can result in a failure message "Improper syntax for the following parameter" and hanging condition.

To avoid this problem in the Altiris environment, set the RD_ERR2 variable to 'N' in the Altiris job CAPTURE RAID CONFIGURATION.

Network boot disks fail on the IBM BladeCenter H Chassis with the IBM BladeCenter Advanced Management Module

ServerGuide Scripting Toolkit network boot disk scenarios fail on the IBM BladeCenter H chassis with the IBM BladeCenter Advanced Management Module due to inability to connect to the network. To correct this problem, install firmware level build level BPET29F or higher to the Advanced Management Module.

SLES 10 install with xen support hangs during the initial services startup post install

After installation of SLES 10 with XEN support, you may experience what appears to be a hang condition. To work around this problem, log in to the machine using a different console (for example, using Alt+F2).

Altiris Clone/Deploy of Image Fails on SUSE Linux Enterprise Server 10

Altiris RapiDeploy does not support the reiserfs filesystem for capturing and deploying images, causing the job to fail.

To avoid this problem, use -raw parameter for the Capture Linux image job and Deploy Linux image job or install SLES 10 with ext3 filesystem. To get more information about this workaround please check the section "Performing Image Installs" of the Users Guide.

PRAID.EXE errors when configuring System x3800 with ServeRAID-8i

When using PRAID.exe to configure or capture a configuration on a System x3800 containing a ServeRAID-8i controller, you might receive error code 2. This error is caused by an incompatibility between previous versions of the ServeRAID-8i controller firmware and the current version of tools used by PRAID.

To avoid this problem, update the firmware of ServeRAID-8i to 11844 or higher and ensure that the CPLD is 1.06 or higher.

Network deployment of Red Hat Enterprise Linux 5 fails on System x3455 type 7984

When performing network deployment of RHEL 5 to a System x3455 type7984, you might receive the following message:

An error occured during the file system check. Dropping you to a shell; the system will reboot when you leave the shell. Warning -- SELinux is active Disabling security enforcement for system recovery. Run 'sentenforce1' to reenable. Give root password for maintenance (or type control-D to continue):

To correct the problem, reboot the server and continue.

"File not found" error when using the Toolkit Configurator to copy installation files for SLES9 SP3

When using the ServerGuide Scripting Toolkit Configurator to copy operating system installation files for SLES9 SP3, users might encounter errors similiar to these from the Configurator:

Pre-Processing Error - File Not Found: E:\Program Files\Altiris\eXpress\Deployment Server\sgdeploy\os\sles9tim\core\cd1\boot\root Click Finish To Exit... The most common cause of this error is that the files for the base installation of SLES9 were not found in the destination directory. To correct the problem, copy the files for the base installation of SLES9 to the destination directory before copying the installation files for SLES9 SP3.

Performing BIOS updates on x3400 and x3500 using Altiris or ADS

To perform a successful BIOS update to level SPE155A or SPE156A on an x3400 or x3500, you must add 'flashfil.exe' to first line of the 'lcreflsh.bat' file that you have copied into the 'updates\%MachineType%\BIOS' folder.

The correct 'lcreflsh.bat' file should read as follows:

flashfil.exe Phlash16 /x /p /s /exit flashfil.fls

PRAID.EXE errors when configuring System x3550 with no internal drives attached

When using PRAID.exe to configure or capture a configuration on a System x3550 with no internal drives attached, you might receive error code 5. This error is caused by the inability of the configuration tool to determine whether there is a configuration present on the internal drives.

If you want to configure and install to a raid adapter other than the internal adapter, you must disable the internal adapter in the BIOS settings prior to using PRAID.exe.

RAID configuration fails when configuring with ServeRAID-MR10i

When using the RAID configuration tools to configure a ServeRAID-MR10i, you might receive an error code of 1. The most common cause of this error is an incorrect physical connection to the MR10i.

If you receive this error, verify that the SAS cable is connected to the port labeled "0-3" on the MR10i adapter, and that the cable is seated securely.

SLES Installation fails on System 3850 M2

During the Suse Linux Enterprise Server installations on System 3850 M2, you might encounter the following issues:

For the kernel panic issue, this problem has been seen when using a keyboard video mouse (KVM) switch during the SLES installation. To avoid this problem, discontinue use of the KVM until the installation is done.

For the Access Installation Media issue, the kernel parameter maxcpus=1 is needed for installation. Without this parameter, the system will be unable to obtain an IP address via DHCP. To add kernel parameters for the setup phase of the installation please edit USRVARS.BAT and add the following line in the kernel parameter section:

echo maxcpus=1 > %RAMDSK%\usrvars.tmp The kernel parameter maxcpus=1 is not needed post installation. To remove the kernel parameter post installation, edit the file /boot/grub/menu.lst by removing maxcpus=1.

Problems obtaining an IP address after a SLES installation on System 3850 M2

After a Suse Linux Enterprise Server installation, the DHCP server might not assign an IP address. Please refer to ibm.com on instructions on resolving this issue.

Additional Files, Utilities, And Information

Back to TOC

This section contains information that is not documented in the IBM ServerGuide Scripting Toolkit User's Reference.

Electronic Service Agent (ESA)

The Electronic Service Agent is a no-charge software tool that resides on your IBM xSeries? systems to monitor hardware events and transmit system inventory information to IBM. With these functions, this software can proactively monitor, track and capture system inventory and hardware errors. Follow this link to download the IBM xSeries Electronic Service Agent: http://www.ibm.com/support/electronic

Limitations

The following limitations are applicable to this version of the ServerGuide Scripting Toolkit:

Support Web Sites

Back to TOC

The following Web pages provide resources for understanding, using, and troubleshooting IBM deployment and systems-management software:

Notices And Trademarks

Back to TOC

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

ServeRAID

ServerGuide

ServerProven

System x

TotalStorage

xSeries

IBM is a trademark of International Business Machines Corporation in the United States, other countries, or both.

Intel is a trademark or registered trademark of Intel Corporation or its subsidiaries in the United States and other countries.

Linux is a trademark of Linus Torvalds in the united states, other countries, or both.

Microsoft, Windows, and the Windows logo are trademarks of Microsoft Corporation in the United States, other countries, or both.

Other company, product, or service names may be trademarks or service marks of others.