File Name: readme.txt IBM Netfinity 5000 Diagnostics Flash Update Diskettes readme.txt Version 3.03 System 8659 CONTENTS --------- 1.0 Overview 2.0 Change History 3.0 Installation and Setup Instructions 4.0 Configuration Information 5.0 Unattended Mode 6.0 Web Sites and Support Phone Number 7.0 Trademarks and Notices 8.0 Disclaimer 1.0 Overview -------------- 1.1 Overview about this code The diagnostics on the IBM Netfinity 5000 are located in the ROM. In order to update the version of diagnostics in ROM, two flash diskettes are required labeled "IBM Netfinity 5000 Diagnostics Flash Update Diskette 1 of 2" and "IBM Netfinity 5000 Diagnostics Flash Update Diskette 2 of 2". 1.2 Limitations N/A 1.3 Enhancements N/A 1.4 Level of Recommendations and Prerequisites for the Update N/A 1.5 Dependencies N/A 2.0 Change History -------------------- 2.1 Netfinity 5000 Diagnostics Flash Update Diskettes 3.02 to 3.03 - eflash changes 2.2 Netfinity 5000 Diagnostics Flash Update Diskettes 3.01 to 3.02 - Fixed a bug where running "Normal Tests" or "Quick Tests" remotely would cause the remote connection to be dropped 2.3 Netfinity 5000 Diagnostics Flash Update Diskettes 3.00 to 3.01 - Setup Replication Diagnostic Flash Utility changes 2.4 Netfinity 5000 Diagnostics Flash Update Diskettes 2.03 to 3.00 - Enhanced adapter support in the Ethernet diagnostic - Changed LED test to test all LEDs at once - Added tape drive support for NS20 and TR4 to SCSI tape drive diagnostic - Added system error log option to Hardware Info - Added ServeRAID diagnostic 2.5 Netfinity 5000 Diagnostics Flash Update Diskettes 2.02 to 2.03 - Renamed Alt. CPU test to Application Processor test - Fixed a bug where a USB keyboard was not usable after running the cache test 2.6 Netfinity 5000 Diagnostics Flash Update Diskettes 2.01 to 2.02 - Added the BIOS Timer test back into the Systemboard test category. This had been removed due to a bug in version 2.01 2.7 Netfinity 5000 Diagnostics Flash Update Diskettes 2.00 to 2.01 - Fixed date rollback problem described in previous item - Fixed a flashing problem that occurred when flashing a Netfiniity 5000 with a video/keyboard/mouse switch box attached. The flash would fail after inserting the second flash diskette with the error message: "Image File Checksum Invalid The diagnostic image is damaged Try again with another copy of the diskette." 2.8 Netfinity 5000 Diagnostics Flash Update Diskettes 1.01 to 2.00 - Added SCSI Tape Drive diagnostic - Added External Loopback and FIFO Buffers tests to Serial Ports diagnostic - Shortened timeout in Service Processor diagnostic so system will not appear to be hung when certain hardware faults are encountered - Removed hang in flash utility which would occur when the user aborted the flash utility after receiving the warning dialog that they were flashing the same version of diagnostics that was presently in the system - Date Rollback Problem with 2.00: If the cache test is run, either stand alone or as part of Quicks Test or Normal Tests, and diagnostics are left running across midnight the date may not roll forward and the time will be corrupted. Please check that the date and time are correct after rebooting under these circumstances. 2.9 Netfinity 5000 Diagnostics Flash Update Diskettes 1.00 to 1.01 - Warnings added to tell the user when saving files to diskette that they must use non-preformatted diskettes. Namely the user should use diskettes which they have formatted themselves using a recent version of DOS or windows. - Labels and documentation modified to clarify the functionality of "Real-time logging". - Fixed problem in which system date would not roll forward when running tests across midnight. - Diagnostic flash diskettes are called out and #1 and #2 instead of #2 and #3. - Removed Japanese from flash diskette list of supported languages - Fixed a problem in which LEDs which are on when the LED test is aborted by the user (by pressing 'escape') would remain on. Now they will be turned off before the test aborts. - The Service Processor Reset Test has been removed from the Quick Test since Quick Test is meant to be run remotely and this test will abort the remote connection (since the remote connection is made through the service processor). 2.10 Netfinity 5000 Diagnostics Flash Update Diskettes 1.00 - Initial Release 3.0 Installation and Setup Instructions *Note: If installing from an update package, see additional instructions, in Appendix A. ----------------------------------------- 3.1 Step by step instructions for this code update - Insert the "IBM Netfinity 5000 Diagnostics Flash Update Diskette 1 of 2" into drive A. - Start up or restart your IBM Netfinity 5000 server. - The system will boot from the diskette and present a window which allows you the option to flash various options. Choose "2 - Update Diagnostic". - After loading the image from the diskette the system will prompt you to enter the second flash diskette which is labeled "IBM Netfinity 5000 Diagnostics Flash Update Diskette 2 of 2" and hit enter. - After the images are loaded from diskette the system will ask you to wait while the images are flashed into ROM. When this is complete you will be prompted to remove the diskette and hit enter to restart the system. 3.2 Other N/A 4.0 Configuration Information ------------------------------- N/A 5.0 Unattended Mode --------------------- 5.1 Steps for unattended mode - Boot to DOS - Copy flash2.exe and all *.us* files from "IBM Netfinity 5000 Diagnostics Flash Update Diskette 1 of 2" and "IBM Netfinity 5000 Diagnostics Flash Update Diskette 2 of 2" to the same directory on some media capable of storing 2MB of data - From the directory just copied to, run "flash2.exe /u /d" 6.0 WEB Sites and Support Phone Number ---------------------------------------- 6.1 IBM Support Web Site: http://www.pc.ibm.com/support 6.2 IBM Marketing Netfinity Web Site: http://www.pc.ibm.com/netfinity 6.3 If you have any questions about this update, or problems applying the update go to the following Help Center World Telephone Numbers URL: http://www.pc.ibm.com/qtechinfo/YAST-3P2QLY.html. 7.0 Trademarks and Notices ---------------------------- N/A 8.0 Disclaimer ---------------- 8.1 THIS DOCUMENT IS PROVIDED "AS IS" WITHOUT WARRANTY OF ANY KIND. IBM DISCLAIMS ALL WARRANTIES, WHETHER EXPRESS OR IMPLIED, INCLUDING WITHOUT LIMITATION, THE IMPLIED WARRANTIES OF FITNESS FOR A PARTICULAR PURPOSE AND MERCHANTABILITY WITH RESPECT TO THE INFORMATION IN THIS DOCUMENT. BY FURNISHING THIS DOCUMENT, IBM GRANTS NO LICENSES TO ANY PATENTS OR COPYRIGHTS. 8.2 Note to Government Users Note to U.S. Government Users -- Documentation related to restricted rights -- Use, duplication or disclosure is subject to restrictions set forth in GSA ADP Schedule Contract with IBM Corporation. Appendix A: Package Specific Installation Instruction This update is packaged as a self-extracting Package for the web (PFW). To unpack, this update requires that your TEMP environment variable be set to a path with read/write access. You must be logged in as an administrator. The command-line syntax for Package-For-The-Web Firmware update package is: Package.exe [-s] [-a [-s] | [-r] | [-c] | [-x directory] | [-xd] | [-w] | [-?] ] [-s] This initial -s tells the Package-For-The-Web software to install silently and will not prompt if files need to be over-written in the %temp% directory. [-a] Tells the Package-For-The-Web software to pass all subsequent commands to the install package (i.e. the update). [-s] The second -s option indicates to run the update silently and unattended. For firmware updates the update is scheduled to run on the next reboot. An immediate reboot can be forced with the -r option. [-r] Schedule the update (can be used with or without the -s option, either way it has the same meaning) and reboot immediately. [-c] Cancel any scheduled firmware update and record results of this operation in the log file. Only one firmware packages can be scheduled at one time, if a firmware update needs to be applied instead of the currently scheduled firmware update package, the user needs to cancel the current (run with the -c option on any firmware package) package and subsequently run the applicable firmware package. [-x directory] Use with firmware updates to extract the update to directory named directory. Since the Package-For-The-Web extracts itself to subdirectory in the %TEMP% directory, a relative directory will be relative to that location. Normally the user will want to specify an absolute directory. [-xd] Use with firmware updates to extract floppy diskette(s). The floppy diskette(s) can subsequently be used to boot and apply the update in the customary "apply update from floppy diskette" fashion. This option is not available for all firmware updates, such as Tape Drive and Hard Disk updates. [-w] The PowerQuest Virtual Boot Environment requires 2 free sectors on the first track before it can schedule a firmware update. Use this option only if scheduling an update failed because 2 free sectors were not found in the first track. This option will wipe or clear the non boot and the non partition information sectors on the first track. These sectors are normally not used. Before clearing the sectors a copy of the complete first track is saved in the %temp% directory from which the update runs. [-?] Display information about the command line switches. Only the apply-update-silently (-s) option is necessarily unattended, that is the other command line options such as display help (-?) may require the user to "hit any key" to continue. If Windows packages are run without any command line options, a GUI is displayed. This GUI offers all the options available at the command line, except that the -w option is not available.