IBM FastSetup version 1.10 Readme Contents 1.0 About IBM FastSetup version 1.10 2.0 Conventions and terminology 3.0 Supported servers 4.0 Supported operating systems 5.0 Other hardware requirements 6.0 Other software requirements 7.0 Known limitations, problems, and workarounds 8.0 Web links 9.0 Notices 9.1 Trademarks 1.0 About IBM FastSetup version 1.10 IBM FastSetup version 1.10 is a wizard that allows you to set up BladeCenter H blade servers, Advanced Management Modules (AMMs), and I/O modules. It also allows you to create and apply saved templates. See the prerequisites checklist linked from the Help for the IBM FastSetup Welcome page for full system requirements. 2.0 Conventions and terminology AMM - Advanced Management Module BNT - Blade Network Technologies CNA - Converged Network Adapter GUI - Graphical User Interface HBA - Host Bus Adapter IMM - Integrated Management Module UEFI - Unified Extensible Firmware Interface UXSP - UpdateXpress System Pack UXSPI - UpdateXpress System Pack Installer 3.0 Supported servers *IBM BladeCenter HS23 (7875, 1929) *IBM BladeCenter HS22 (7870, 1936, 7809, 1911) *IBM BladeCenter HS22V (7871, 1949) *IBM BladeCenter HX5 (7872, 1909, 7873, 1910) *IBM BladeCenter HS23E (8038, 8039) 4.0 Other hardware requirements *x86 or x86 64-bit platform *2 GB RAM or more *10 GB of free disk space for temporary usage *Ethernet adapter 5.0 Supported operating systems *Microsoft Windows XP *Microsoft Windows Vista *Microsoft Windows 7 *Microsoft Windows Server 2003 *Microsoft Windows Server 2003 R2 *Microsoft Windows Server 2003 R2 64-bit *Microsoft Windows Server 2008 *Microsoft Windows Server 2008 64-bit *Microsoft Windows Server 2008 R2 6.0 Other software requirements *Browsers -Microsoft Internet Explorer 6.x, 7.x, 8.x, or 9.x is recommended Note: You can use other Web browsers as well. But to launch IBM FastSetup, the mshta.exe (Microsoft HTML Applications) process is required on your machine. *For firmware acquisition, you must have: -TCP/IP networking -Internet connectivity, directly or through a HTTP proxy server 7.0 Known limitations, problems, and workarounds The following limitations, problems, and workarounds are applicable to IBM FastSetup. No more than four chassis should be used simultaneously per IBM FastSetup instance. IBM recommends using a maximum of four chassis to achieve optimal performance. Use of more than four chassis may impact performance and/or reliability, depending on your configuration. Network bandwidth and load should be taken into consideration if more than four chassis are updated at the same time or multiple IBM FastSetup instances are run at the same time on the same network. Installation completes successfully on some Microsoft Windows operating systems, but there are warnings. No warnings display when installing on a Windows 7 64-bit system. Installing IBM FastSetup on some Windows systems may trigger a message stating: "The installation of IBM FastSetup is finished, but some warnings occurred during the install. Please see the installation log for details." This will not impede the execution of IBM FastSetup. Default boot order is not set when applying UEFI default settings in IBM FastSetup. When only UEFI settings are applied, the boot order is not reset to the defaults. Choosing F1 Setup and Loading Defaults in the UEFI menu on the blade causes the boot order to be reset to the defaults. On the UEFI Settings page in IBM FastSetup, select the option to specify the boot order. IBM FastSetup requires the user to configure a user ID for 0 connections. If the user creates an ID for IBM FastSetup on the AMM for IBM FastSetup, the AMM defaults to 1 connection. IBM FastSetup requires that the user configure it to the maximum number of connections. The value to set for maximum number of connections is 0. Switch module IP address must be configured manually. The user must configure the IP address for a switch module manually through the AMM web interface to ensure that it is in the same subnet as the AMM. The network mask defines the subnet boundaries. For example, if the AMM's IP is on network 9.37.0.0 (subnet mask 255.252.0.0),the switch module must be on the same network 9.37.0.0 (subnet mask 255.252.0.0). IBM FastSetup only restores the first 4 entries in the boot order list back when finished. If the blade has 5 entries in the boot order list before running IBM FastSetup, IBM FastSetup only restores the first 4 entries in the boot order list back when finished. The UEFI Settings page allows the user to perform UEFI and other configuration on blades, which fails to enter maintenance mode (the temporary IP address is not pingable). The UEFI Settings page allows the user to perform UEFI and other configuration on blades, which fails to enter maintenance mode (the temporary IP address is not pingable). The issue will be fixed in the next release. A string variable shows on error detail message box instead of the actual device name. If the user clicks Detail on some error message boxes, a string variable name displays instead of the device name. Microsoft Windows Program Compatibility Assistant pop-up dialog displays when the user exits IBM FastSetup. Microsoft Windows displays a Program Compatibility Assistant pop-up dialog box approximately 10 seconds after closing IBM FastSetup that states, "This program might not have installed correctly. If this program didn't install correctly, try reinstalling using settings that are compatible with this version of Windows." The Windows User Access Control (UAC) in Windows Vista and Windows 7 looks for keywords in the programs that are run, such as "Install", "Setup", and "Launch". If it finds these keywords, it assumes the program is an installation program, even though it really is not. In order for the proxy server connection to work, IBM FastSetup requires the user to use a password for the proxy server on the Network Access page. The user must set a password for the proxy server on the Network Access page. Detailed results are not viewable when UXSP update fails. If an update failure occurred in UXSP update, IBM FastSetup will not show which package has failed on the GUI. The detailed results are located in \IBM_Support\IBMFastSetup\\log\\up_result.xml. Examine the xml file to determine the failing update (double-clicking the xml file will open it in a browser). Use the "Select from a list of all available component firmware levels" option to retry the failing update. The expanded view auto-collapses when adding firmware information on the Device Inventory page. On the Device Inventory page, users must expand the tree table to see the detailed information during the inventory process. But the expanded view auto-collapses each time inventory for a blade is completed. Re-expand the tree view to see the detailed information or keep expanding the tree view to see the detailed information until the inventory process finishes. A scroll bar error occurs in the template view when viewing a predefined template. Move the mouse or click anywhere in the View Template page. The table view will return to normal. If the username and/or password for the BNT switch are not "admin" and "admin", IBM FastSetup reports an error when performing a BNT switch update. IBM FastSetup uses the default user name and password to perform a BNT switch update. The default username and password are "admin" and "admin". Modify the default username and/or password in /scripts\com\ibm\ezconfig\common\constants\R2Configurations.xml IBM FastSetup uses UXSPI 9.20 to perform update functions. Any UXSPI limitations may also apply to IBM FastSetup. IBM FastSetup uses UXSPI to perform update functions. Any UXSPI limitations may also apply to IBM FastSetup. IBM FastSetup does not support installing down level UXSP updates. IBM FastSetup does not support installing down level UXSP updates. Only updates in a UXSP that are newer than those in the system being updated will be installed. Use individual blade updates to downgrade to the needed level. Caution: Downgrading can cause unpredictable results for some firmware. When performing firmware updates, the progress bar stays at 99% for a long time. When performing a firmware update in IBM FastSetup, the progress bar may stay at 99% for a long time. If you are uploading files from the client to the blade, the update takes more time than usual. Installed version of blade server updates should change after the individual flash succeeds. The Install Version column is not updated when the flash succeeds. Some firmware updates may require a reboot of the blade in order to display the version that is installed. The user can also see the correct installed version on the FastSetup Summary Report before exiting the application. IBM FastSetup fails to change the UEFI settings due to an error with the target system's IMM. Message EIZUI7701E is displayed, and the message provides details on the appropriate actions to take. IBM FastSetup requires that the target system's IMM is functioning properly to change its UEFI settings. First, make sure the target system's IMM works normally. If the problem occurs, use the AMM to restart the target system's IMM. Under "Blade Tasks", select "Power/Restart". Select the failing blade and perform the "Restart Blade System Mgt Processor" action. Finally, retry changing the blade's UEFI settings with IBM FastSetup. The QLogic 8Gb Fibre Channel Expansion Card (CIOv) for IBM BladeCenter is not supported in IBM FastSetup. The QLogic 8Gb Fibre Channel Expansion Card (CIOv) is not supported in IBM FastSetup. When performing an inventory in IBM FastSetup, the GUI does not display the device under the blade that has installed the component. Use UXSPI to update the QLogic 8Gb Fibre Channel Expansion Card (CIOv). IBM FastSetup might show 2 "Brocade 10G CNA BootCode Update for IBM System X and BC" lines in the inventory drop-down list for a blade. There is only 1 Brocade adapter in the system. The extra one listed is due to an issue with an update in the IBM Fix Central repository. Select only one adapter and ignore the other if you are updating the adapter. IBM FastSetup may fail to obtain the device inventory for an HS23. IBM FastSetup will not properly perform a device inventory on an HS23 with an AMM firmware level lower than ibm_fw_amm_bpet62o_anyos_noarch. If the AMM firmware level is lower than ibm_fw_amm_bpet62o_anyos_noarch, it must be flashed to that level or a level greater before a device inventory is performed on the HS23. Run IBM FastSetup first to update only the AMM firmware. Then, run IBM FastSetup again to perform the desired tasks, as defined in the steps below: 1. Run IBM FastSetup. 2. Proceed to Task Selection and select Full Setup. 3. Proceed to Device Selection and select only the AMM. 4. Perform updates on the AMM firmware to flash the firmware to a level equal to or greater than ibm_fw_amm_bpet62o_anyos_noarch. 5. Close IBM FastSetup. 6. Restart IBM FastSetup. 7. Run as desired. IBM FastSetup does not support the use of an external FTP server. IBM FastSetup requires that its internal FTP server is used with port 21 to manage blade servers and update I/O modules. Stop any FTP server currently running on the system running IBM FastSetup, or use a port other than 21 for your other FTP server(s). Chassis Inventory and Health requires an available connection to the AMM. The EIZUI0001E error message is displayed on the Chassis Inventory and Health page when all of the connections to the AMM are in use. Verify that the number of AMM connections for the AMM userid being used is set to the maximum value (0 means maximum). IBM FastSetup attempts to use the default userid and password of "USERID/PASSW0RD". If a logon failure occurs for the default userid, then a different userid and password may be specified. Gathering device inventory requires that the target system boots successfully. The EIZUI7108E error message is displayed on IBM FastSetup's Device Inventory page when the target system hangs during the UEFI boot process. Use the AMM to restart the target system. Under Blade Tasks, select "Power/Restart". Select the failing blade and perform the "Restart Blade" action. Note that IBM FastSetup temporarily sets the blade's boot sequence to floppy only. The boot order will be restored when you exit IBM FastSetup. If the blade does not boot UEFI successfully, remove and reinsert the blade in the chassis. Restart the blade again. If the blade boots successfully, back up and go forward again to retry gathering device inventory. "Blade" is displayed on the Chassis Inventory and Health page instead of the blade's actual name and description. If the AMM has not completed discovery of a blade, IBM FastSetup may display "Blade" on the Chassis Inventory and Health page instead of the blade's actual name and description. If you continue, the blade will not be selectable on the Device Selection page. Check the AMM's System Status page, refreshing as needed, until the blade is no longer in the discovering state. Then go back and forward to rediscover the chassis and update the Chassis Inventory and Health page. The UEFI Shell is filtered out at the end of running IBM FastSetup if the UEFI Shell is one of the boot order options set before using F1 to run IBM FastSetup. IBM FastSetup cannot set the UEFI Shell option in the boot order. The user must press F1 to enter the UEFI setting to set UEFI Shell option when starting the blade. On the UEFI Settings page, changing boot order is not offered when using multiple blades. Only setting UEFI defaults is offered. A single boot order cannot be applied to multiple blades in a single operation. Use either of the options below to apply to apply the same boot order to multiple blades: 1. Use the full setup task. Select an individual blade, specify the desired boot order, and apply the boot order. Repeat for each desired blade. 2. Create and apply templates. Create a blade template for a desired blade type (e.g. HS22), specify the desired boot order, apply the boot order, and save the template. Run IBM FastSetup again to create a blade template for the next desired blade. Repeat as needed (up to 4 times since 4 blade types are supported). Run IBM FastSetup again, select a template for each desired blade type, and apply the selected templates to all the desired blades (this requires only one final pass through IBM FastSetup). UEFI dialog does not resize correctly when attempting to reduce page size. This dialog is not resizable because the elements inside may collapse or be invisible. These elements are of fixed width. If a user resizes the panel to a much smaller screen, the "Available Devices" box is cut off, and not all text displays clearly. IBM FastSetup supports some higher-resolution screens. IBM FastSetup pages do not always resize properly. Some IBM FastSetup pages do not resize properly, i.e. the page elements may not display properly if a page is resized to be larger or smaller. On the Device Inventory page, IBM Fastsetup may show a BuildID of "0.0.0.0-0000" for a blade component. A Build ID of "0.0.0.0-0000" means that IBM Fastsetup was unable to match the installed version to an update package in the IBM Fix Central repository. This could be due to a package not from Fix Central being used for the last update of the blade component. It also could be that the package last used is on Fix Central but contains a minor error that prevents it from matching after the update. This is not a critical condition. It indicates the component could use an update. Using IBM Fastsetup to update the component will set it to an installed version that will be matched in subsequent IBM Fastsetup sessions. Selected blade fails to boot into maintenance mode. IBM FastSetup may fail to boot a system into maintenance mode if the selected network port from the Adapter Settings page is not the correct network port connected to the data network. To resolve this issue, validate that the correct network port was selected in the Adapter Settings page. Another possible cause for maintenance mode entry failure is the inability to power cycle the system. Downgrading from IBM FastSetup version 1.10 to 1.0 is not recommended, as it may cause unpredictable results. Templates created with version 1.10 may not be compatible with version 1.0 for the newer hardware supported with version 1.1. Firmware cannot be downgraded for a SAS HDD. If the downgrade firmware level option is selected when performing a SAS HDD firmware update in IBM FastSetup, IBM FastSetup will show success, but the firmware cannot be downgraded. The SAS HDD firmware does not support downgrading. 8.0 Web links The following web links contain relative resources to assist with understanding configuration and troubleshooting of supported hardware. *UpdateXpress http://www-947.ibm.com/support/entry/portal/docdisplay?lndocid=SERV-XPRESS#uxspinstall *BladeCenter Interoperability Guide (BIG) - IBM BladeCenter http://www-947.ibm.com/support/entry/portal/docdisplay?lndocid=MIGR-5073016&brandind=5000020 *Installation and User's Guide - IBM BladeCenter H http://www-947.ibm.com/support/entry/portal/docdisplay?lndocid=MIGR-63306&brandind=5000020 *Advanced Management Module Installation Guide - IBM BladeCenter http://www-947.ibm.com/support/entry/portal/docdisplay?lndocid=MIGR-5073392&brandind=5000020 *Enabling and Configuring BladeCenter Chassis Internal Network (CIN) - IBM BladeCenter http://www-947.ibm.com/support/entry/portal/docdisplay?lndocid=MIGR-5074328&brandind=5000020 *Installation and User's Guide - IBM BladeCenter HS22 (7870, 1936, 1911) http://www-947.ibm.com/support/entry/portal/docdisplay?lndocid=MIGR-5079689&brandind=5000020 *Installation and User's Guide - IBM BladeCenter HS22V http://www-947.ibm.com/support/entry/portal/docdisplay?lndocid=MIGR-5083318&brandind=5000020 *Installation and User's Guide - IBM BladeCenter HS23 http://www-947.ibm.com/support/entry/portal/docdisplay?lndocid=MIGR-5089459&brandind=5000020 *Installation and User's Guide - IBM BladeCenter HS23E http://www-947.ibm.com/support/entry/portal/docdisplay?lndocid=MIGR-5090096&brandind=5000020 *Installation and User's Guide - IBM BladeCenter HX5 http://www-947.ibm.com/support/entry/portal/docdisplay?lndocid=MIGR-5084612&brandind=5000020 *IBM BladeCenter forum http://www.ibm.com/developerworks/forums/forum.jspa?forumID=819 9.0 Notices This information was developed for products and services offered in the U.S.A. IBM may not offer the products, services, or features discussed in this document in other countries. Consult your local IBM representative for information on the products and services currently available in your area. Any reference to an IBM product, program, or service is not intended to state or imply that only that IBM product, program, or service may be used. Any functionally equivalent product, program, or service that does not infringe any IBM intellectual property right may be used instead. However, it is the user's responsibility to evaluate and verify the operation of any non-IBM product, program, or service. IBM may have patents or pending patent applications covering subject matter described in this document. The furnishing of this document does not grant you any license to these patents. You can send license inquiries, in writing, to: IBM Director of Licensing IBM Corporation North Castle Drive Armonk, NY 10504-1785 U.S.A. For license inquiries regarding double-byte (DBCS) information, contact the IBM Intellectual Property Department in your country or send inquiries, in writing, to: IBM World Trade Asia Corporation Licensing 2-31 Roppongi 3-chome, Minato-ku Tokyo 106-0032, Japan The following paragraph does not apply to the United Kingdom or any other country where such provisions are inconsistent with local law: 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 states 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. Any references in this information to non-IBM Web sites are provided for convenience only and do not in any manner serve as an endorsement of those Web sites. The materials at those Web sites are not part of the materials for this IBM product and use of those Web sites is at your own risk. IBM may use or distribute any of the information you supply in any way it believes appropriate without incurring any obligation to you. Licensees of this program who wish to have information about it for the purpose of enabling: (i) the exchange of information between independently created programs and other programs (including this one) and (ii) the mutual use of the information which has been exchanged, should contact: IBM Corporation Software Interoperability Coordinator, Department 49XA 3605 Highway 52 N Rochester, MN 55901 U.S.A. Such information may be available, subject to appropriate terms and conditions, including in some cases, payment of a fee. The licensed program described in this document and all licensed material available for it are provided by IBM under terms of the IBM Customer Agreement, IBM International Program License Agreement or any equivalent agreement between us. Any performance data contained herein was determined in a controlled environment. Therefore, the results obtained in other operating environments may vary significantly. Some measurements may have been made on development-level systems and there is no guarantee that these measurements will be the same on generally available systems. Furthermore, some measurements may have been estimated through extrapolation. Actual results may vary. Users of this document should verify the applicable data for their specific environment. Information concerning non-IBM products was obtained from the suppliers of those products, their published announcements or other publicly available sources. IBM has not tested those products and cannot confirm the accuracy of performance, compatibility or any other claims related to non-IBM products. Questions on the capabilities of non-IBM products should be addressed to the suppliers of those products. All statements regarding IBM's future direction or intent are subject to change or withdrawal without notice, and represent goals and objectives only. This information contains examples of data and reports used in daily business operations. To illustrate them as completely as possible, the examples include the names of individuals, companies, brands, and products. All of these names are fictitious and any similarity to the names and addresses used by an actual business enterprise is entirely coincidental. COPYRIGHT LICENSE: Copyright IBM Corp 2012. All rights reserved. 9.1 Trademarks IBM, the IBM logo, and ibm.com are trademarks or registered trademarks of International Business Machines Corp., registered in many jurisdictions worldwide. Other product and service names might be trademarks of IBM or other companies. A current list of IBM trademarks is available on the Web at "Copyright and trademark information" at www.ibm.com/legal/copytrade.shtml. Microsoft, Windows, Windows NT, and the Windows logo are trademarks of Microsoft Corporation in the United States, other countries, or both. Java(TM) and all Java-based trademarks are trademarks of Sun Microsystems, Inc. in the United States, other countries, or both. Linux is a trademark of Linus Torvalds in the United States, other countries, or both. Intel is a trademark of Intel Corporation in the U.S. and other countries. Other company, product, or service names may be trademarks or service marks of others.