File Name: dsa_preboot_readme.txt
******************************************************************
                                                                
   IBM(R) Preboot Dynamic System Analysis (DSA)                 
   Version 3.02.56 
                                                                
   (C) Copyright International Business Machines Corporation    
       2004, 2009. All rights reserved.                         
                                                                
   US Government Users Restricted Rights -- Use, duplication    
   or disclosure restricted by GSA ADP Schedule Contract with   
   IBM Corp.                                                    
                                                                
   Note: Before using this information and the product it       
         supports, read the general information under           
         "NOTICES" in this document.                            
                                                                
   This readme file is provided only in English. You can        
   obtain the latest version of the readme file from the IBM    
   Support Web site.                                            
                                                                
******************************************************************


CONTENTS
--------    

1.0  Overview
  1.1  Product overview
  1.2  Prerequisites for running Preboot DSA 
  1.3  Compatibility with ServeRAID

2.0  Running Dynamic System Analysis
       
3.0  Using the DSA Main Menu

4.0  Using the DSA Interactive Menu

5.0 Using the DSA Graphical User Interface

6.0  Accessing and viewing DSA output
  6.1  Naming convention used for output files and directories
  6.2  HTML files created by DSA  

7.0  Sending DSA output to IBM xSeries Service and Support

8.0  Known problems and workarounds 

9.0  Support Web sites


1.0  OVERVIEW
-------------

This readme file provides information about IBM Preboot Dynamic System
Analysis (pDSA).


1.1  Product overview 
---------------------

IBM Preboot DSA is a system information collection and analysis tool that is used by IBM xSeries(R) 
Service and Support personnel to aid in the diagnosis of system problems.

DSA collects information about the following aspects of a system:

 o   System configuration
 o   Network interfaces and settings
 o   Hardware inventory, including PCI & USB information
 o   IBM LightPath(TM) status
 o   Service Processor status and configuration
 o   Vital product data, firmware, and basic input/output system
 o   (BIOS) information
 o   Drive Health Information
 o   ServeRAID configuration
 o   LSI RAID & Controller configuration
 o   Scalability/RXE Ports configuraiton
 o   Emulex Fibre Channel configuration
 o   QLogic Fibre Channel & iSCSI Adapter configuration
 o   LSI InternalRaid Adapter configuration
 o   LSI MegaRaid Adpater configuration
 o   Event logs for ServeRAID controllers and service processors
 o   Logs of correctable and uncorrectable error NVRAM 
 o   VMWare 3i EH Information (Athena only)
 o   GoVault Tape Drive information
 o   Disk Management information

DSA can also provide diagnostics for the following system components (if they are installed on the system):

 o  Network, BroadCom NetXtreme II(5703,5708,5709,5714 and 5722 NIC) 
 o  Optical devices (CD-ROM, DVD-ROM)
 o  Tape Drives (SCSI)
 o  Remote Supervisor Adapter
 o  Base Board Management Controller
 o  Memory
 o  CPU
 o  Check-point panel test

Additionally, DSA creates a merged log that includes events from all collected logs.

All collected information can be output as a compressed XML file that can be sent to IBM Service. 
You can customize the FTP to transfer. You can also view the information locally through a generated 
text report file. The generated HTML pages may be copied to removable media and viewed from a web browser.

Server support list:
X206m (8485, 8490) 
X236 (8841)
X260/x3800 (8865, 8866)
X306m (8849, 8491, 1887) 
X336 (8837) 
X336 (1879) 
X346 (8840, 1880) 
X366/x3850 (8863, 8864, 7362, 7365)
X460/x3950 (8872, 8878, 7363, 7366)
X3200 (4362, 4363)
X3200M2(4367, 4368)
X3200M3(7327, 7328)
X3250 (4364, 4365, 4366)
X3250M2(4190, 4191, 4194)
X3250M3(4251, 4252)
X3350 (4192, 4193)
X3400/x3500 (7973, 7974, 7975, 7976, 7977)
X3450(7948, 7949, 4197)
X3455(7940, 7984, 4197, 7941, 7986)
X3400M2(7836, 7837)
X3500M2(7839)
X3550 (7978, 1913)
X3550 M2 (7946, 4198)
X3650 (7979, 1914)
X3650 M2 (7947, 4199)
X3655 (7985, 7943)
X3755 (8877, 7163)
X3850M2 Single node (7141, 7144, 7233, 7234) 
X3950M2 Single node (7141, 7233) 
X3950M2 Dual node (7141, 7233) 
X3950M2 3~4 Node (7141, 7233) 
iDataplex dx320(6388)
iDataplex dx340(7831, 7832, 7834)
iDataplex dx360(7833)
iDataplex dx360M2(6380, 7321, 7322 ) 
Smart Business (9233)
Lotus Foundations Server (9234) 
Z40 (9228)
M40 (6218, 9236)
M50 (9229, 9230)
HS12(8014, 8028, 1916) 
HS20 (8843, 1883)
HS21 (8853, 1885)
HS21 (7995)
HS21 XM(1915)
LS20 (8850)
LS21/LS41 (7971, 7972)
LS22/LS42 (7901, 7902) 
HS22(7870, 1936, 7809) 



1.2  Prerequisites for running Preboot DSA
----------------------------------------------------

Preboot DSA requires:

o   A minimum of 1GB of system memory.
o   A USB interface or an optical drive capable of reading the Bootable media.


1.3  Compatibility with ServeRAID
----------------------------------------- 

Preboot DSA will collect configuration data from the following ServeRAID controllers on
supported server models. However, ServeRAID logs will not be collected.

o  ServeRAID-7t SATA RAID
o  ServeRAID-8i
o  ServeRAID-8k

2.0  RUNNING DYNAMIC SYSTEM ANALYSIS
------------------------------------

Complete the following steps to run Preboot DSA.

For Embedded Preboot DSA:
1. If the server is running, turn off the server and all attached devices. 
2. Turn on all attached devices; then, turn on the server.
3. When the prompt F2 for Dynamic System Analysis (DSA) appears, press F2. 
   If you have set both a power-on password and an administrator password, 
   you must type the administrator password to run the diagnostic programs.
4. A standalone memory diagnostic environment will load.   Select the appropriate 
   tests to run or select exit to DSA to exit the standalone memory diagnostic.
5. From the DSA main screen, select the "gui" or "cmd" options to enter the 
   graphical user interface or the DSA interactive menu respectively.
6. Follow the on screen directions to select the device and tests to launch.


For ISO-based Preboot DSA:
1. Record ISO image to appropriate recordable media.
2. If the server is running, turn off the server and all attached devices. 
3. Turn on all attached devices; then, turn on the server.
4. Boot the machine using the DSA Bootable Edition media.
5. A standalone memory diagnostic environment will load.   Select the appropriate 
   tests to run or select exit to DSA to exit the standalone memory diagnostic.
6. From the DSA main screen, select the "gui" or "cmd" options to enter the 
   graphical user interface or the DSA interactive menu respectively.
7. Follow the on screen directions to select the devices and tests to launch.

   
For more information on using the interactive menu, see 
"4.0 USING THE DSA INTERACTIVE MENU."

DSA collects information into a compressed XML file that can be sent
to IBM Service. For information about sending the file to IBM Service,
see "7.0 SENDING DSA OUTPUT TO IBM XSERIES SERVICE AND SUPPORT." 

DSA also collects information in ASCII text and HTML report files,
For information about viewing the collected data see "6.0 ACCESSING
AND VIEWING DSA OUTPUT."

NOTE:  ONCE THE STANDALONE MEMORY DIAGNOSTIC ENVIRONMENT HAS BEEN EXITED THE
       STANDALONE MEMORY DIAGNOSTIC ENVIRONMENT CANNOT BE RE-ENTERED WITHOUT
       A SYSTEM REBOOT.

3.0  Using the DSA Main Menu
----------------------------

The preboot DSA main menu has the following options:
For Embedded Preboot DSA:
 Commands:
    gui	 - Enter Graphical User Interface (GUI) screen for diagnostic tests and DSA functionality.
    cmd	 - Enter Command Line Interface (CLI) for diagnostic tests and DSA functionality.
    exit     - Quit program.
	         Note: This will eject the CD (if booted from CD) and reboot the system.
    help     - Display this help message.


After the system is booted with the image created by Bootable Media Creator (BoMC),
there are 2 options: CLI and GUI mode. User may choose the mode by using their mouse.
Choosing CLI, user will be led to the interactive menu.
Choosing GUI, user will be led to the Graphic User Interface.


4.0  USING THE DSA INTERACTIVE MENU
-----------------------------------

The DSA Interactive menu has the following options:
   
 IBM DSA Interactive.

   1 - Data Collection.
   2 - Diagnostics.
   3 - Copy Collected System Information to Local Media.
   4 - Send Collected System Information to IBM Server or Customized FTP server.
   5 - Quit and back to main menu.

 Enter Number: 
 
 On entering number "1"

   Data Collection:

   1 - Collect System Information.
   2 - View Collected Results.
         (Note: To exit viewer, type :q or ZZ then press enter)
   3 - Quit to previous menu.

   Again, entering "1" (collect) user is asked "Customize option Y/N?"
   Select "Y" and it shows,

   -x	       Do not create a compressed XML file.
   -v	       Create HTML output files.
   -dumpxml  Write the DSA .xml.gz file after each plugin runs.

   Note: All options must be seperated with a comma (Example: -v,-dumpxml)
   Enter the options and it starts to execute.

   Select "N" and it starts to execute

 On entering number "2"

   Diagnostics:

   1 - Enumerate Available Diagnostic Tests.
   2 - Execute Diagnostic Test.
   3 - Get Diagnostic Extend Results.
   4 - Quit to previous menu

NOTE:	FOR REMOTE ACCESS VIA SOL (SERIAL OVER LAN), COMMAND LINE INTERFACE IS THE ONLY INTERFACE SUPPORTED.
 
5.0 Using the DSA Graphical User Interface
------------------------------------------
 
The following features can be accessed via the GUI:

o System Inventory - Show detailed information about your system.
o Diagnostic - Run diagnostic tests on system components.
o Collect Logs and Transfer- Collect, copy and send the system information to IBM for analysis.
o Help - Display the DSA readme file (Includes open source statements).
o License - Display the DSA license agreement.
o Exit - Quit the utility.

        

6.0  ACCESSING AND VIEWING DSA OUTPUT
------------------------------------- 

When DSA is run, it creates a compressed XML file,
an ASCII text report file, and a set of HTML report files.

The text report file can be viewed from the DSA interactive menu
using the "view" command. To view collected data via the GUI, select 
the System Information button on the main page and choose a category 
of data to view.

The compressed XML and HTML report files can be copied to removable
media for remote viewing using the "copy" command on the DSA main
menu.

Regarding CPU information, the information of physical processors is shown under:
 - Hardware Inventory -> Processor
The information for logical processors is shown under:
 - Hardware Inventory -> Other Devices
NOTE: With hyper-threading turned on there will be more logical processors shown than physical processors.


6.1 Naming convention used for output files and directories
-----------------------------------------------------------

DSA uses the following naming convention for compressed XML files
and for subdirectories and reports that it creates:

<machine_type_model>_<serial_no>_<date>-<time>

where

 o  <machine_type_model> is the machine type and model number of
    the server.
 o  <serial_no> is the serial number of the server.
 o  <date> is the date that DSA collected information.
 o  <time> is the hour, minute, and seconds that DSA was run.

For example, on an xSeries 360 system, Preboot DSA would create a
compressed XML file that has the following name:

86865RZ_23D0600_20041007-191612.xml.gz 

a ASCII text report with the name:

86865RZ_23D0600_20041007-191612.txt

and a subdirectory containing the HTML pages with the name:

86865RZ_23D0600_20041007-191612 

If DSA cannot obtain a valid machine type and model number or
serial number of a system, any resultant output file and
subdirectory will use the string "Unknown" in place of these
values.


6.2 Exporting HTML files created by DSA
---------------------------------------

To view the HTML files that are created by DSA, you must use
Internet Explorer 6.0 SP 1 or later, Mozilla 1.4.0 or greater, or 
Firefox 1.04 or greater  In order to display the DSA data, 30 to 100MB
of available memory is required. The amount of memory required depends
on the size of the logs being viewed.

Each time that you run DSA, DSA creates a subdirectory that contains 
several HTML files, which list the results of the DSA data collection. 
The top-level DSA HTML page is index.html. This Web page is referred 
to as the DSA home page in this readme file. The DSA home page contains
links to the other HTML files that are created by DSA.

To export the DSA HTML report, use the "copy" command to copy the files
to removable media and open the index.html file in your Web
Browser.

The DSA HTML report organizes collected information into various
categories that you can access by clicking a subcategory name
in the left pane of the Web page. For example, to view information
about the hardware inventory on a server, click "Hardware Inventory"
in the Software category in the left pane of the DSA HTML report.


7.0  SENDING DSA OUTPUT TO IBM XSERIES SERVICE AND SUPPORT
----------------------------------------------------------

Use the "transfer" command in the CLI to send the collected data to IBM xSeries
Service and Support. DSA uses File Transfer Protocol (FTP) to
transfer the compressed XML output file to IBM Service.

NOTE:  When the file is first transferred, it is not allowed to be overwritten
until an FTP agent removes it from the server (FTP agent runs approximately every
5 minutes).

If the same file is transferred a second time (before the FTP agent runs), a
connection error is issued.  Alternatively, you could run another collection
which would name the file with an updated datetime stamp.

It is possible that the FTP agent may run immediately after the first collection
allowing another transfer right away. 


8.0  KNOWN PROBLEMS AND WORKAROUNDS
-----------------------------------

DSA has the following known problems and
workarounds:

o  To ensure quality and stability of the DSA code, we have reverted some display functionality 
   of RAID information to what was shown in previous versions of DSA.  This affects RAID display 
   on the following adapters:
      Megaraid 8480
      Serveraid MR10i
      Serveraid MR10is
      Serveraid MR10m
      Serveraid MR10k
      Serveraid M1015
      Serveraid M5014
      Serveraid M5015
   On these adapters, the RAID information is generated from the output of separate command line 
   tools and the format may not match other output in DSA.

o  On systems with PCI Express slots, the type of slot may be listed as 
   "Other". These slots will not be associated with the appropriate PCI 
   device that may be in the PCI Express slot.

o  On systems where the service processor clock does not have the same timezone
   settings as the local system, the merged log may appear to be out of order.
   The entries are sorted correctly but look incorrect because the timezone 
   setting is not displayed.

o  Certain, rare conditions on the SCSI bus may temporarily prevent DSA 
   from collecting sense data from SCSI-attached tape devices.  In the event 
   that this data is not collected on a machine with a SCSI-attached tape 
   device, it is recommended that DSA be run again to collect the data.  
   
o  When DSA collects dates and times that are before 
   January 1, 1970, 00:00:00, or after January 19, 2038, 03:14:07; 
   DSA will report these dates and times as January 1, 1970, 00:00:00.  
   These dates fall outside the valid range for a date in DSA.
   
o  DSA may report the memory speed as "Unknown" in the Memory section 
   of the Hardware Information report.  This is due to issues with SMBIOS 
   support on some systems.
   
o  The ServeRAID report may report the number of Logical Drivers as 1, 
   while ServeRAID Manager reports the number of Logical Drives as 0.  
   This is due to an issue with the tool used by DSA to collect this data.
   
o  DSA is unable to collect firmware information from the Broadcom NX2 (NetXtreme II)
   network adapter due to limitations of the current Broadcom BMAPI interface. 
   
o  DSA is unable to collect firmware information from video adapter (nVidia Quadro) 
   on Blade HC10(Type 7996).

o  For the IBM eServer e325, Preboot DSA will not collect BMC related 
   information such as the BMC firmware level and IPMI logs.  This is due to an
   incompatability with the OpenIPMI driver used by Preboot DSA.

o  For the xSeries 225 and IntelliStation Z10 systems, the PCI Information
   report may  misrepresent which slot a PCI device is in due to an SMBIOS issue.  

o  For the xSeries 226 system, the Firmware/VPD report may erroneously 
   report that there is an RSA card installed.  This is due to an issue 
   with the SMBIOS support.
   
o  Due to a limitation in HS40(8839), DSA can only determine the status 
   of the system error LED.  No other LEDs are available.
   
o  Due to a limitation in x206m and x306m, DSA cannot determine the status of 
   the system LEDs.  No LEDs are available for collection.

o  For the x3550 system, the system fans are physically attached together 
   as pairs, and each pair has a single LightPath LED attached.  The DSA
   LightPath report will display each pair of fans as a single Fan LED.

o  For the IntelliStation A10 system, the Processor section of the Hardware  
   Information report will not display cache information for secondary
   processors.  This is due to an issue with the SMBIOS support.

o  If you are running DSA version 1.00 on a 
   multi-node IBM eServer like the xSeries 460 system, DSA cannot specify
   to which node certain hardware belongs. This is due to limitations of
   either Windows APIs or SMBIOS. The x460 appears to Windows and SMBIOS
   as a single, complete system and not as split up into nodes. Also,
   since LightPath and IPMI logs are only populated by the primary node,
   specific details regarding non-primary nodes will not be collected.
   
o  If the USB Memory Key which you are using does not show up in the list 
   of media copy to, the DSA output may be uploaded directly if the machine 
   is connected to a network, or copied to a floppy for upload later.
  
o  DSA will collect CPLD firmware levels(Super I/O card firmware, PCI-X card
   firmware, CPU card firmware) on systems where there is CPLD inside. The 
   information about the individual CPLD firmware levels versus the CPLD
   package version on the web(i.e. version 1.06) can be obtained in ver_chk.txt
   which is located on each CPLD disk. The 1st column in this file is the SIO
   card CPLD version, the 2nd column is the PCI-X card CPLD version, the 3rd
   column is the CPU card CPLD version and the last column is the overall disk
   version number.

o  GoVault (part number 25R0006) is not recognized as a tape drive in DSA 
   Diagnostics (version 2.02 and prior) and does not appear in the tape drive 
   section of the HTML viewer.  GoVault will appear as a hard disk due to the 
   hardware implementation and device driver.  DSA can still recognize the 
   device, but it will be listed in the disk drive section.   

o  For the HS20 and LS20 systems, the DSA Lightpath report will always show 
   the "System" LED as being "off", even if the associated physical LED is lit. 

o  DSA is unable to collect RAID information from 8e SAS/SATA HostRAID controller.

o  DSA is unable to collect RAID information from 8e SATA HostRAID controller.

o  While flashing Wflash on a new installed windows 2003 R2, a windows pop-up stated" 
	 Do you want to restart your computer now" for each node that being flash, 
   this pop-up window will show-up.  It only happens on a new installed windows.

o  When DSA boots from a USB key, the disk partition size sometime can be incorrect.

o  UpdateXpress section is not available with DSA Preboot.

o  On LS21(7972), no DIMM LED indication in lightpath will be available after a single bit memory error occurs.

o  On HS20, no LSI controller information is collected.

o  On dx360 M2, no ethernet NIC test is available in the diagnostics list in Preboot DSA.

o  On HS12, Preboot DSA can't be updated by UXSPI 3.0.

o  Preboot DSA might not collect PCI slot status information correctly.

o  Remote Supervisor Adapter (RSA) II remote control session is sometimes lost when accessing F2 Diagnostics.
	 The steps of the possible failure is as follows,
	 Login to the RSA II web page address. 
	 Start remote control session. 
	 Reboot the server using Power/Restart link in the web page. If the server is off, power it on using the same link. 
	 Press F2 when prompted during POST to start Diagnostics. 
	 There will be a black screen and then an error messagesaying that the connection is lost. 
	 If the user closes the remote control window and starts anew one. 
	 Note: The user will see that the diagnostics memory test is already taking place, but has no control to the remote session. 
	 When the user presses the ESC key, there is no response at all.
	 
o  on x306m, PCI-e slots are sometimes shown "in use" when actually there is no PCI-e device plugged.
	 When RSA2 is present on PCI slot, it shows no PCI device.

o  Preboot DSA is based on 64bit operating system.
	 Systems must be 64 bit capable.  
   eServer x335 only supports 32 bit and Preboot DSA 3.02 doesn't support it.
   
o  When using the editor function in 'View Collected Results' in the CLI mode, Keystrokes are sometimes
	 misinterpreted. For example, holding the down arrow and nothing happens. 
   Pressing the PgDn key is handled like a 'tab'. 

o  When booting from the image created by BoMC, user can select "Diagnostics" and click "Gui option" to enter gui mode. 
   Select "Diagnostic test" and add NIC items to test. When NIC is triggered with an error(like removing the NIC), 
   "TestLoopBackMAC" test status keeps "Running". The diagnostics only apply to a NIC with stable state (either normal or defective during test).
   
o  When an error occurs to the hard disk during the HDD test, the test might complete with "No Result".
	 The diagnostics only apply to a HDD with stable state (either normal or defective during test).

o  When flashing DSA Preboot using wflash or lflash, if you notice a build mismatch error, please make sure IMM firmware level is 
   minimum 29B. Once you upgrade the IMM firmware to 29B or higher, DSA Preboot will continue to flash without error. 
   
o  Under Hardware Inventory -> Video Controller information, there is no video controller information is collected by the Preboot Edition.

o  On x3400, x3650, x3250, x3850M2, x260, x306m, LS22 and LS42, the PCI slot information might not reflect the real status. It may show "On Board"
   when there is a PCI device plugged in. DSA Installable and Portable Edition can provide accurate information though.

o  LS21/LS41 Lightpath information might only show the first 8 DIMMs and first 2 CPUs LED status.

o  On LS22/LS42, some IPMI events show "Severity: Transition to Critical from less severe."

o  When user updates the IBM Preboot DSA to DSA Preboot 3.0 with the file name starting with "ibm_fw_dsyt", there is no way user can roll 
   back to the version of Preboot DSA before the update.

o  In Preboot DSA environment, the disk partition format information might be inaccurate.

o  When running DSA preboot network interfaces will load in the order they are detected by the the operating system device driver.
   This may result in physical port 1 being labeled eth0 in some cases, but it could also be labeled eth1 or eth2 depending on the quantity of network adapters in the system.
   This is valid for on-board network controllers and added in network controllers.

o  When system is booted to DSA Preboot Edition with ServeRaid (M1015) SAS/SATA controller loaded, there might be no ServeRaid information collected.
 
o  On M40, M50, Z40, BIOS version is not collected.


   
9.0  SUPPORT WEB SITES
----------------------

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

o  IBM support page
   http://www.ibm.com/pc/support/

   This is the IBM Support Web site for IBM hardware and systems-
   management software. For systems-management software support, 
   click "Systems management". 

o  IBM Dynamic System Analysis page
   http://www.ibm.com/servers/eserver/xseries/systems_management/
   dsa.html

   This Web page presents an overview of Dynamic System Analysis
   and links to download the product and readme files.

o  IBM xSeries(R) Systems Management page
   http://www.ibm.com/pc/ww/eserver/xseries/systems_management/
   index.html

   This Web page presents an overview of IBM systems management 
   and IBM Director. Click "IBM Director" for the latest 
   information and documentation. It also contains links to Web 
   pages for IBM Director extensions, including Remote Deployment 
   Manager, Scalable Systems Manager, Virtual Machine Manager,
   Server Plus Pack, and Software Distribution (Premium Edition).

o  IBM ServerProven(R) page
   http://www.ibm.com/pc/us/compat/index.html

   This Web page provides information about IBM hardware
   compatibility with IBM systems-management software. 

o  Electronic Service Agent compliments your DSA tool by providing
   24x7 pro-active monitoring of IBM eServers.

   For more information on Electronic Service Agent go to
   http://www.ibm.com/support/electronic/serviceagent.