File Name: dsa_portable_readme.

txt
******************************************************************
| |
| IBM(R) Dynamic System Analysis (DSA) Portable Edition, |
| Version 2.20 |
| |
| (C) Copyright International Business Machines Corporation |
| 2004, 2008. 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. |
| |
| Updated 05 Feb 2009 |
******************************************************************
CONTENTS
--------
1.0 Overview
1.1 Product overview
1.2 Prerequisites for systems running Windows
1.3 Compatibility with ServeRAID Manager
1.4 Compatibility with Network Virtual Teaming software
1.5 Compatibility with Service Processors
1.6 Compatibility with Some System

2.0 Running Dynamic System Analysis

3.0 Using DSA command-line options
3.1 Running DSA Diagnostics
4.0 Accessing and viewing DSA output
4.1 Naming convention used for output files and directories
4.2 Viewing a compressed collection file
4.3 HTML files created by DSA
5.0 Sending DSA output to IBM xSeries Service and Support
5.1 Sending DSA output via ftp
5.2 Sending DSA output via HTTPS
6.0 Collecting Remote System info via VMWare ESXi 3i
7.0 Collecting IPMI event of remote system
8.0 Using DSA with UpdateXpress
9.0 Running DSA on WinPE
10.0 Known problems and workarounds
11.0 Support Web sites
12.0 Notices
13.0 Third-party license terms and conditions, notices and
information
13.1 zlib software
13.2 boost software

1.0 OVERVIEW
-------------
This readme file provides information about IBM Dynamic System
Analysis (DSA) Portable Edition, version 2.20.

1.1 Product overview

---------------------
IBM DSA Portable Edition 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 Installed applications, components and hotfixes
o Device drivers and system services
o Network interfaces and settings
o Performance data and details for running processes
o Hardware inventory, including PCI & USB information
o Service Processor status and configuration
o IBM LightPath(TM) status
o Vital product data, firmware, and basic input/output system
(BIOS) information
o Drive Health Information
o ServeRAID configuration
o LSI RAID & Controller configuration
o Event logs for the operating system, applications, security,
ServeRAID controllers, and service processors
Additionally, DSA creates a merged log that includes events from
all collected logs.
Diagnostics information may optionally be collected by DSA.
For more information, see "3.1 Running DSA Diagnostics"
The system information is collected into a compressed XML file
that can be sent to IBM Service. Additionally, you can view the
system information through optionally generated HTML Web pages.
For more information, see "5.0 ACCESSING AND VIEWING DSA OUTPUT."
DSA Portable Edition is not installed on the target system. When
run, DSA Portable Edition expands to a temporary directory, which
is removed after DSA information collection is completed. If you
want to install DSA, use DSA Installable Edition.
DSA Portable Edition is designed to fit on removable media such
as a CD or USB key. The removable media must be supported for use
with the server on which you plan to run DSA Portable Edition.
Server support list:
X206m (8485, 8490)
X226 (8648, SB/8488 )
X236 (8841)
X260/x3800 (8865, 8866)
X306m (8849,8491,1887)
X335 (8676,8830)
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)
X3250 (4364,4365,4366)
x3250M2(4190/4191/4194)
X3350 (4192, 4193)
X3400/x3500 (7973,7974, 7975, 7976,7977)
X3455(7940, 7984, 4197, 7941, 7986)
X3550 (7978,1913)
X3650 (7979,1914)
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 (7321,7322 )
X3550 M2 (7946)
X3650 M2 (7947)
Z20 (6223, 6227)
Z40 (9228)
M30 (6225, 6228)
M40 (6218)
M50 (9229)
HC10 (7996)
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)
Smart Business (9233)
Lotus Foundations Server (9234)

Operation System support list:

[Windows 2008 family]
Windows Server 2008 GA/SP1 (32 and 64bit)
(Including the Windows Core Server installation mode)
Windows Small Business Server 2008 (64 bit)
Windows Essential Business Server 2008 (64-bit)
Windows Hyper-V Server
Windows Vista Business GA/SP1 (32 and 64 bit.)
Windows HPC Server 2008 (64-bit)
[Older Windows family]
Windows Server 2003 GA/SP1 (32 bit and 64 bit)
Windows Server 2003 R2 (32 bit and 64 bit)
Windows Small Business Server 2003 R2
Windows XP GA-SP3 (32 bit and 64 bit)
[SUSE]
SuSE Linux Enterprise Server (SLES) 9.0 GA-SP3 (32 bit and 64 bit)
SuSE Linux Enterprise Server (SLES) 10 GA-SP2 (32 bit and 64 bit)
SuSE Linux Enterprise Server (SLES) 10 with Xen GA-SP2 (32 bit and 64 bit)
SuSE Linux Enterprise Real Time 10 (32bit and 64bit)
[RedHat]
RedHat Enterprise Linux 5 GA-U2 (32 bit and 64 bit)
RedHat Enterprise Linux 5 GA-U2 with Xen (32 bit and 64 bit)
RedHat Enterprise Linux Real Time 5.1 (32bit and 64bit)
RedHat Enterprise Linux 4 GA-U6 (32 bit and 64 bit)
RedHat Enterprise Linux 3 GA-U9 (32 bit and 64 bit)
[VMware]
VMware ESX Server 3.x (Up to 3.5)
VMware 3i (VMware ESXi 3.5 U2 or later)
Note: RHEL3 32bit build is used for use on VMware ESX Server 3.x console.
1.2 Prerequisites for systems running Windows
----------------------------------------------------
DSA requires above 250MB of available memory during the data collection
process. The amount of memory required for this process depends on the
size of the logs being collected from the system.
To view the information that is collected 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.
That it is strongly recommended to have Service processor Drivers installed Prio
r to running DSA.
This Provide IBM with more hardware logs.
BMC: drivers are IPMI device drivers with IPMI mapping layer
RSA 2: IBM Remote Supervisor Adapter II Server Software
See system doc for older systems
In order to collect Emulex HBA information, emulex driver and utility (corekit)
must be installed.
1.3 Compatibility with ServeRAID Manager
-----------------------------------------
DSA Portable Edition 2.20 can collect ServeRAID log information
from ServeRAID Manager 6.10 and later versions.
DSA cannot collect information from the following ServeRAID
controllers unless ServeRAID Manager is installed:
o ServeRAID-7t SATA RAID
o ServeRAID-8i
o ServeRAID-8k

1.4 Compatibility with Network Virtual Teaming software

-----------------------------------------
DSA Portable Edition 2.20 is supported for use with
the following Network Virtual Teaming software:
o Intel(R) PROSet for Wired Connections, version 9.1 or later
o Broadcom Advanced Control Suite, version 7.6.7 or later
1.5 Compatibility with Service Processors
------------------------------------------
Environmental data is available from servers which have an Integrated Management
Module (IMM),
Remote Supervisor Adapter 2 (RSA2) , Remote Supervisor Adapter (RSA) or Integrat
ed System Management
Processor (ISMP) . In all cases appropriate support software must be loaded and
running.

1.6 Compatibility with Some System

------------------------------------------
The following machine types have not been fully verified by IBM test
for complete DSA operation . All major functions have been tested and
confirmed as available.
iDataplex(6388,7831,7832,7834, 7833)and x3450(7948,7949,4197).

2.0 RUNNING DYNAMIC SYSTEM ANALYSIS

------------------------------------
Complete the following steps to run DSA Portable Edition.
Note: The operating-system account that runs DSA Portable Edition
must have local Administrator authority.
1. Click Start; then, click Run. The "Run" window opens.
2. In the Open field, type the path to the DSA Portable Edition
executable file, or click Browse to locate it.
3. (Optional) Type DSA command-line options after the executable file
file name. For more information, see "4.0 USING DSA COMMAND-LINE OPTIONS."
The DSA program files are extracted into temporary disk
space on the server as defined by the TEMP system variable in the
Windows environment. The window that opens shows the progress
of DSA information collection. When DSA is completed, the DSA
program files are deleted from temporary disk space, and the
progress window closes.
If you ran DSA without any options, DSA collects information into
one compressed XML file that can be sent to IBM Service. For
information about where this file is created, see "5.0 ACCESSING
AND VIEWING DSA OUTPUT." For information about sending the file
to IBM Service, see "6.0 Sending DSA output to IBM Service and
Support."

3.0 USING DSA COMMAND-LINE OPTIONS

-----------------------------------
The command-line syntax in this document uses the following
conventions:
o Options are shown delimited with a hyphen (-).
o Options are shown as lowercase, but are not case-sensitive.
o Variables are shown in angle brackets.
DSA has the following command-line options:
collectall.exe [options]
-?, -h Display help for DSA command-line options.
-b Run in batch mode.
-c Create directory specified by -d option.
-d <dir> Place DSA output files in the specified directory rather
than in the default location, which is C:\IBM_Support.
-diags Execute all non-destructive diagnostic tests.
-f Collect the full ISMP log.
-i <file> Read input from <file> rather than collecting data
from the local server.
-ipmilan <userid:password@IP [:port]>
Collect IPMI log via Out-Of-Band mode.
-l Display license and exit.
-t Transfer collected data to IBM Service & Support.
-ux Compare the installed and latest version of firmware levels.
-v Create HTML output files.
-vmwesxi <[userid]:[password]@[IP]:[port]>
Retrieve system information from the remote target system loaded
with VMWare Embedded Hypervisor.
-text Create TEXT output files.
-x Do not create a compressed XML file.
-r <file> Run the CIM difference engine comparing the collected or
specified (via -i) data to this file.
-dumpxml Write the DSA .xml.gz file after each plugin runs.
-upload Upload DSA output to SRSP and ISP by ecc common client C++ API . NO S
UPPORT FOR PPC.
-ibmid Users provides their IBM Identifier. Work with -upload.
Note: All options must be separated with one or more spaces.
For example, to run DSA and generate HTML output files that can be
viewed with a browser, run this command:
ibm_utl_dsa_220p_windows_anycpu.exe -v
To run DSA and create HTML output files in the directory C:\temp\DSA_Output,
run this command:
ibm_utl_dsa_220p_windows_anycpu.exe -v -c -d C:\temp\DSA_Output
3.1 Running DSA Diagnostics
---------------------------
Use the -diags option to execute diagnostics during the DSA collection process.
This option will execute all of the non-destructive diagnostic tests that are
included with DSA.
4.0 ACCESSING AND VIEWING DSA OUTPUT
-------------------------------------
By default, DSA output is created in the \IBM_Support directory of
the hard disk defined by the %SystemDrive% environment variable.
(This is the hard disk on which Windows is installed. It is usually C:\.)
Use the -d option to specify a different output directory.
When DSA is run with no command-line options, it creates only a
compressed XML file in the IBM_Support directory.
When DSA is run with the -v option, it creates a subdirectory that
contains HTML files that you can view with a Web browser.

4.1 Naming convention used for output files and directories

-----------------------------------------------------------
DSA uses the following naming convention for compressed XML files
and for subdirectories 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 a System x3650 system, DSA could create a
a compressed XML file that has the following name:
7979AC1_23D0600_20090320-191612.xml.gz

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.

4.2 Viewing a compressed collection file

----------------------------------------
If you have a compressed XML file that was created by DSA, you can
run DSA again to generate HTML files from that compressed XML
file. Then, you can view the HTML files with a Web browser. To
generate HTML files from a compressed XML file, run the following
command:
ibm_utl_dsa_220p_windows_anycpu.exe -v -x -i <path>\<output_file>.xml.gz
where
o <path> is the path to the compressed XML file that was previously created by
DSA.
o <output_file> is the name of the compressed XML file.
4.3 HTML files created by DSA
-----------------------------
Each time that you run DSA with the -v option, 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 view the DSA home page, open the index.html file in your Web
browser.
The DSA home page 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 applications that are installed on a server, click
"Installed Applications" in the Software category in the left pane
of the DSA home page.

5.0 SENDING DSA OUTPUT TO IBM XSERIES SERVICE AND SUPPORT

----------------------------------------------------------
Customers can specify opting -t or -upload to upload DSA compressed XMl
output file to IBM service.

5.1 Sending DSA output via ftp

-------------------------------
Use the -t option to send the collected data to IBM xSeries
Service and Support (ftp://testcase.boulder.ibm.com/eserver/toibm/xseries/fdr_up
load).
DSA uses File Transfer Protocol (FTP) to transfer the compressed XML
output file to IBM Service.
For example, the following command collects data and sends it to
IBM Service:
<dsa-package> -t
If you already have a compressed XML output file from DSA that you
want to send to IBM Service, run DSA from a command prompt and
use the -i option with the -t option. The -i option requires that
you specify a fully qualified path name to the compressed XML
output file from DSA.
For example, the following command sends the specified output
file to IBM Service:
<dsa-package> -t -i /var/log/IBM_Support/<output file>.xml.gz
where <output_file> is the name of a compressed XML file that was
previously created by DSA. For example, an output file could be
named 86865RZ_23D0600_20041004-190308.xml.gz.
5.2 Sending DSA output via HTTPS
-----------------------------------
Use the -upload option to send inventory to the Electronic Services
web portal for use in proactive support functions such as My Systems
and My Notifications. The data is sent using HTTPS.
Recommend customers to upload DSA output with their IBMid. Customers
can specify -ibmid option with -upload option and input their IBMID
following -ibmid option. If the IBM ID is not provided, the data
will not be accessible via the Electronic Services web portal.
6.0 Collecting Remote System info via VMWare ESXi 3i
-----------------------------------
Use -vmwesxi option to collect remote system info via VMWare ESXi 3i.
The following system support this function:
LS22 with SMART USB key
x3850M2 with Sandisk USB key
HS21XM with uFDM USB
Version of supported VMWare ESXi 3.5 in DSA2.20 is VMware ESXi 3.5 (GA)- Embedde
d Build 71173.
Here are the recommended steps to run the function:
a. Burn VMware ESX Server 3i to USB key.
b. Boot VMware ESX Server on the supported System.
c. Press F2 to enter Configuration
d. Set password
e. Get IP with DHCP or static IP.
If you can't get IP, try to "Restart Management Agents" and then "Restart Manage
ment Network".
f. "Test Management Network"
If all items pass, then you could start running -vmwesxi test case of DSA.
Notification:
If there is firewall locally, please pass it or close it.
In SUSE system, the command should be "w3m [IP]".
In windows or REDHAT system, please open IE or Firefox browser, input [IP] and p
ass firewall.
7.0 Collecting IPMI event of remote system
-----------------------------------
Use -ipmilan option to collect IPMI event of remote system. For example,
<dsa-package> -ipmilan USERID:PASSW0RD@9.125.90.3
Before running the function, configure remote BMC to connect to network..
8.0 Using DSA with UpdateXpress
--------------------------------
Use the -ux option to Compare the installed and latest version of
firmware levels. Internet access is required.
When you do so, DSA compares the device driver and firmware
configurations on the server to those that were extracted from the
eCC Repository.
When the -v option is used to create HTML files, you can view the
results of the comparison from the DSA home page. To do so, click
"UpdateXpress Comparison" in the Analysis category in the left
pane of the DSA home page.
9.0 Running DSA on WinPE
------------------------
DSA portable Version support WinPE.
Please follow these steps to create a new WINPE CD.
a.Select the Windows PE Tools Command Prompt command from the Start | All Progra
ms | Microsoft Windows AIK menu. Or you can click Start, point to All Programs,
point to Windows OPK, and then click Windows PE Tools Command Prompt.
b.At the command prompt, run the Copype.cmd script.
If 32-bit WinPE,
- run Copype.cmd x86 c:\WinPE
If 64-bit WinPE,
- run Copype.cmd amd64 c:\WinPE
where c:\WinPE is the location of the WinPE image being built.
c.Mount the base WinPE image. Run the imagex command.
- imagex /mountrw c:\WinPE\ISO\sources\boot.wim 1 c:\WinPE\mount
d.Create a new registry item named WinPECacheThreshold like belows:
reg load HKLM\_WinPE_SYSTEM c:\WinPE\Mount\windows\system32\config\system
reg add HKLM\_WinPE_SYSTEM\ControlSet001\Services\FBWF /v WinPECacheThreshold /t
REG_DWORD /d 96 /f
reg unload HKLM\_WinPE_SYSTEM
"96" indicates 150MB cache size. You can change the cache size even larger.
e.Add Utilities and DLLs
1)Copy pdh.dll from a corresponding (32/64) Windows Server 2008 installation int
o the c:\WinPE\mount\Windows\system32 (If 64-bit WinPE, also c:\WinPE\mount\Wind
ows\sysWOW64) image subdirectory. Missing pdh.dll will cause the installedapps p
lugin fail to load.
2)Copy RpcNs4.dll from a corresponding (32/64) Windows Server 2008 installation
into the c:\WinPE\mount\Windows\system32 (If 64-bit WinPE, also c:\WinPE\mount\W
indows\sysWOW64) image subdirectory.
3)If you need to see the DSA result in HTML format, you can download and copy a
portable Firefox to c:\winpe\mount\program files\Firefox.
4)If you need to debug DSA, you can download Windbg 6.7 and install it on your l
ocal system. Then, copy the installed Windbg folder to c:\winpe\mount\program fi
les\windbg.
5)peimg /install=*WMI* c:\winpe\mount\Windows
6)peimg /install=*MDAC* c:\winpe\mount\Windows
f.Broadcom Network Support
1)Download Broadcom network driver CD supporting 5709 chip. ( brcm_dd_nic_t3.7.6
-test_anyos_i386.iso from http://onestop.raleigh.ibm.com/OssWeb/UpdateTestAction
.do?id=44056 )
2)The driver CD has two packages, W2K3 for 32-bit Windows and W2K3x64 for 64-bit
Windows. To install the driver,
If 32-bit WinPE,
- run peimg.exe /inf=G:\W2K3\RIS\b06nd.inf c:\winpe\mount\Windows
If 64-bit WinPE,
- run peimg.exe /inf=G:\W2K3x64\RIS\b06nd.inf c:\winpe\mount\Windows
where G: is the CD-ROM drive.
g.RSA Support
1)Download RSA Daemon package. ( ibm_svc_rsa2_hlp416a_winsrvr_i386.exe from http
://www-304.ibm.com/jct01004c/systems/support/supportsite.wss/docdisplay?lndocid=
MIGR-5071025&brandind=5000020 or
ibm_svc_rsa2_hlp915a_winsrvr_x86-64.exe from http://www-304.ibm.com/jct01004c/sy
stems/support/supportsite.wss/docdisplay?lndocid=MIGR-5071027&brandind=5000020 )
2)There are two RSA II packages, one for 32-bit Windows and one for 64-bit Windo
ws. Both of these packages run on WinPE as well as Windows, so choose the one y
ou need according to (32/64) data width. Expand the RSAII Package into c:\winpe
\RSAII subdirectory.
If 32-bit WinPE,
- copy c:\winpe\RSAII\ibmspw.dll to c:\winpe\mount\Windows\system32\ibmspw.dll.
If 64-bit WinPE,
- copy c:\winpe\RSAII\ibmspw.dll to c:\winpe\mount\Windows\system32\ibmspw.dll.
- copy c:\winpe\RSAII\ibmspw32.dll to c:\winpe\mount\Windows\SysWOW64\ibmspw.dll
.
NOTE that ibmspw32.dll is also being renamed in this step.
3)IBMSPREM.exe must be run after WinPE is booted in order for configuration util
ities or other applications to communicate with the RSA II.
- copy c:\winpe\RSAII\IBMSPREM.exe to c:\winpe\mount\program files\RSA.
IBMSPSVC.exe must be run after WinPE is booted.
- copy c:\winpe\RSAII\IBMSPSVC.exe to c:\winpe\mount\program files\RSA.
You can edit a WinPE script (c:\winpe\mount\Windows\System32\startnet.cmd) so IB
MSPREM.exe and IBMSPSVC.exe starts automatically.
wpeinit
cd x:\Program Files\RSA
start /B ibmsprem.exe
start /B ibmspsvc.exe
cd x:\
h.IPMI Support
1)Download OSA IPMI driver package for WinPE. ( osa_dd_ipmi_2.2.1.2_winpe2_32-64
.zip from http://onestop.raleigh.ibm.com/OssWeb/UpdateTestAction.do?id=43454 )
2)Expand the OSA IPMI driver package to c:\winpe\IPMI subdirectory and locate th
e ipmi_install.cmd file. It may be located a subdirectory further down. Go to
that subdirectory and execute the following command:
- ipmi_install c:\winpe /p 1 0xca8 1
You can refer to OSA's readme.txt file for additional information on the remaini
ng arguments, if you like.
i.Enter the following command: peimg /prep c:\WinPE\Mount
Type the word Yes when prompted, and press Enter
j.Enter the following command: copy c:\WinPE\WinPE.wim c:\winpe\ISO\sources\boot
.wim
Press Y when prompted
k.Enter the following command: oscdimg -n -bc:\WinPE\etfsboot.com c:\WinPE\ISO c
:\WinPE\WinPE_Tools.iso
Step 5~8 is optional.Doing that will create a ISO file. Use CD burning software
to create a bootable CD from this ISO file.
Notification: If enough ramdisk is not distributed when creating WIN PE bootable
CD, DSA can not extract and execute normally since no enough free space.
10.0 KNOWN PROBLEMS AND WORKAROUNDS
-----------------------------------
DSA Portable Edition has the following known problems and
workarounds:
o When an adapter is removed from the system that was previously configured
in a network virtual team using the Intel PROSet software package, DSA
 may report that the adapter is still present with a corrupt MAC address.
Disregard the information returned for this adapter.
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 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 On 64-bit Editions of Windows, DSA is unable to collect firmware and ASF
information for Broadcom network controllers. This is due to a limitation
of the current Broadcom BMAPI interface.
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 2.20 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 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 The IPMI device driver must be installed in order to collect IPMI BIST
information.
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 Installable is not supported on WINPE (both 32b and 64b).
o When the user executes DSA with -ux on HC10(7996), there are no BIOS
and BMC firmware comparison result in UpdateXpress section.
o When the user executes DSA with -ux, the ATI video driver comparison result
in UpdateXpress may be downlevel. For example:
Driver ATI2MTAG.SYS, it shows 6.14.10.6744 for the latest version. It should
be 8.24.50.
Please look up on www.ibm.com for latest firmware and driver updates.
o When the user executes DSA with -ux on Windows XP or Windows Vista,
the result in UpdateXpress section may not be available or it might be inaccu
rate.
o When the user executes DSA with -ux on LS20 (8850), the BIOS comparison
result in UpdateXpress section may be downlevel.
For example, it shows the latest version is 1.28 but it should be 1.29.
Also, the ServeRaid driver comparison may be downlevel.
For exampel, it shows the latest version of NFRD960.SYS as 7.10.0.0 but it sh
ould be 7.12.11.
Please look up on www.ibm.com for latest firmware and driver updates.
o When the user executes DSA with -ux on x346 (8840), the result in UpdateXpres
s
for device driver file NFRD960.SYS is 7.10.0.0. But actually it should be
7.12.0.0.
o When the user executes DSA with -ux on HS12(8014/8028/1916), the result in Up
dateXpress
for LSI 1064e SAS controller may be inaccurate. It shows the latest level is
1.26.80 but actually it should be 1.26.84.
o Memory Manufacturer info is missing on HS21(8853/1885)and HS12(8014, 8028,191
6).
o Current State in LED Settings can't report some failure of DIMM in LS21/LS41.
Recommend user to check IPMI event and get the failure DIMM event.
o Both of Window Components and Installed Hotfixes can't be collected in Window
s2008.
o Broadcom Firmware info can't be collected in X3200M2(4367/4368) on Windows 20
08.
o Some SMART Attributes in Drive Health may be missing in iDataplex(7321/7322).

o DSA is unable to retrieve QLogic FC Controller from the HS22 blade. QLogic sc
li
utility can't detect the card on HS22.
o Config LED missing from Lightpath Information in X3650(7979/1914) and X3550(
7978/1913).
o For HS22(7870/1936), iDataplex(7321/7322), X3650 M2(7947), X3550 M2(7946), if
RNDIS driver is
not installed in customer's system, environmental data and chassis event logs
 will not be collected. RNDIS driver can be installed automatically when iMM F
irmware
update in OS. But if customer updates iMM FW by iMM website, RNDIS driver won
't
installed on OS. In this case, customers have to install RNDIS manually, Or S
P
configuration Chassis event log and environment data can't be collected.
o For HS22(7870/1936), iDataplex(7321/7322), X3650 M2(7947), X3550 M2(7946),
virtual disk is created by integrated Management Module.
o Slot of PCI-E/PCI adapters is blank in PCI information Section in
X3400/x3500(7973/7974/7975/7976/7977), X3200M2(4367/4368),
x3250M2(4190/4191/4194), X3350(4192/4193) on Windows2008. The future
BIOS release will fix the issue.
o LSI raid configured as level "1E" will be recognized as level "1"
in DSA data collection.
o UpdateXpress function by specifying -ux when executing DSA is not supported
on the following systems:
x335, x336, Intellistation Z20, Z40, M30, M40, M50, iDataplex dx320, dx340, d
x360.
o Using windows HPC server edition all RSA nodes are not available
on x3950, x3850M2 and x3950M2.
o Using Microsoft Windows2003/Windows2008 Enterprise edition all RSA nodes are
not
available on x3950, x3850M2 and x3950M2. Please refer to Server
Proven for specific OS support per system.
o Using Microsoft WindowsPE all RSA nodes and BMC nodes are not
available on x3950, x3850M2 and x3950M2. Please refer to Server
Proven for specific OS support per system.
o The raw data of MegaRaid Information only can be reviewed in XML/HTML output.

11.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

12.0 NOTICES
-------------
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
e-business logo
eServer
IBM
IntelliStation
ServerProven
xSeries
Microsoft, Windows, and Windows Server are trademarks of Microsoft
Corporation in the United States, other countries, or both.
Intel, Intel logo, Intel Inside, Intel Inside logo, Intel Centrino,
Intel Centrino logo, Celeron, Intel Xeon, Intel SpeedStep, Itanium, and
Pentium are trademarks or registered trademarks of Intel Corporation or its
subsidiaries in the United States and other countries.
Other company, product, or service names may be trademarks or
service marks of others.

13.0 THIRD-PARTY LICENSE TERMS AND CONDITIONS, NOTICES AND

INFORMATION
---------------------------------------------------------
The license agreement for this product refers you to this file for
details concerning terms and conditions applicable to third party
software code included in this product, and for certain notices
and other information IBM must provide to you under its license
to certain software code. The relevant terms and conditions,
notices and other information are provided or referenced below.
Please note that any non-English version of the licenses below is
unofficial and is provided to you for your convenience only. The
English version of the licenses below, provided as part of the
English version of this file, is the official version.
Notwithstanding the terms and conditions of any other agreement
you may have with IBM or any of its related or affiliated entities
(collectively "IBM"), the third party software code identified
below are "Excluded Components" and are subject to the following
terms and conditions:
o the Excluded Components are provided on an "AS IS" basis
o IBM DISCLAIMS ANY AND ALL EXPRESS AND IMPLIED WARRANTIES AND
CONDITIONS WITH RESPECT TO THE EXCLUDED COMPONENTS, INCLUDING,
BUT NOT LIMITED TO, THE WARRANTY OF NON-INFRINGEMENT OR
INTERFERENCE AND THE IMPLIED WARRANTIES AND CONDITIONS OF
MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE
o IBM will not be liable to you or indemnify you for any claims
related to the Excluded Components
o IBM will not be liable for any direct, indirect, incidental,
special, exemplary, punitive or consequential damages with
respect to the Excluded Components.

13.1 zlib software

------------------
ZLIB: The Program includes zlib software, and the following
notice(s) are required by the license under which IBM acquired
this software. (Copyright notices which varied only by the years
of copyright are omitted for brevity.)
Copyright notice:
zlib.h -- interface of the 'zlib' general purpose compression
library version 1.2.1, November 17th, 2003
Copyright (C) 1995-2003 Jean-loup Gailly and Mark Adler
This software is provided 'as-is', without any express or implied
warranty. In no event will the authors be held liable for any
damages arising from the use of this software.
Permission is granted to anyone to use this software for any
purpose, including commercial applications, and to alter it and
redistribute it freely, subject to the following restrictions:
1. The origin of this software must not be misrepresented; you
must not claim that you wrote the original software. If you use
this software in a product, an acknowledgment in the product
documentation would be appreciated but is not required.
2. Altered source versions must be plainly marked as such, and
must not be misrepresented as being the original software.
3. This notice may not be removed or altered from any source
distribution.
Jean-loup Gailly Mark Adler
jloup@gzip.org madler@alumni.caltech.edu

13.2 boost software

-------------------
BOOST: The Program includes Boost software, and the following
notice(s) are required by the license under which IBM acquired
this software. (Copyright notices which varied only by the years
of copyright are omitted for brevity.)
Boost Software License - Version 1.0 - August 17th, 2003
Permission is hereby granted, free of charge, to any person or
organization obtaining a copy of the software and accompanying
documentation covered by this license (the "Software") to use,
reproduce, display, distribute, execute, and transmit the
Software, and to prepare derivative works of the Software, and to
permit third-parties to whom the Software is furnished to do so,
all subject to the following:
The copyright notices in the Software and this entire statement,
including the above license grant, this restriction and the
following disclaimer, must be included in all copies of the
Software, in whole or in part, and all derivative works of the
Software, unless such copies or derivative works are solely in the
form of machine-executable object code generated by a source
language processor.
THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND,
EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES
OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE, TITLE AND
NON-INFRINGEMENT. IN NO EVENT SHALL THE COPYRIGHT HOLDERS OR
ANYONE DISTRIBUTING THE SOFTWARE BE LIABLE FOR ANY DAMAGES OR
OTHER LIABILITY, WHETHER IN CONTRACT, TORT OR OTHERWISE, ARISING
FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR
OTHER DEALINGS IN THE SOFTWARE.
(C) Samuel Krempp 2001, 2003 krempp@crans.ens-cachan.fr
Permission to copy, use, modify, sell and distribute this software
is granted provided this copyright notice appears in all copies.
This software is provided "as is" without express or implied
warranty, and with no claim as to its suitability for any purpose.
(C) Copyright Jeremy Siek 2001.
Copyright (c) 2000 David Abrahams.
Copyright (c) 1994
Hewlett-Packard Company
Permission to use, copy, modify, distribute and sell this software
and its documentation for any purpose is hereby granted without
fee, provided that the above copyright notice appear in all copies
and that both that copyright notice and this permission notice
appear in supporting documentation. Hewlett-Packard Company makes
no representations about the suitability of this software for any
purpose. It is provided "as is" without express or implied
warranty.
Copyright (c) 1996-1998 Silicon Graphics Computer Systems, Inc.
Permission to use, copy, modify, distribute and sell this software
and its documentation for any purpose is hereby granted without
fee, provided that the above copyright notice appear in all copies
and that both that copyright notice and this permission notice
appear in supporting documentation. Silicon Graphics makes no
representations about the suitability of this software for any
purpose. It is provided "as is" without express or implied
warranty.
Copyright (c) 1997 - 1998 Silicon Graphics Computer Systems, Inc.
Copyright (c) Jeremy Siek 2001, Marc Wintermantel 2002
Permission to use, copy, modify, distribute and sell this software
and its documentation for any purpose is hereby granted without
fee, provided that the above copyright notice appear in all copies
and that both that copyright notice and this permission notice
appear in supporting documentation. Silicon Graphics makes no
representations about the suitability of this software for any
purpose. It is provided "as is" without express or implied
warranty.
Copyright (C) 2001-2003 Doug Gregor
Permission to use, copy, modify, distribute and sell this software
and its documentation for any purpose is hereby granted without
fee, provided that the above copyright notice appears in all
copies and that both the copyright notice and this permission
notice appear in supporting documentation. No representations are
made about the suitability of this software for any purpose. It is
provided "as is" without express or implied warranty.
Copyright (c) 2000 Cadenza New Zealand Ltd
Permission to use, copy, modify, distribute and sell this software
and its documentation for any purpose is hereby granted without
fee, provided that the above copyright notice appears in all
copies and that both the copyright notice and this permission
notice appear in supporting documentation. Cadenza New Zealand
Ltd makes no representations about the suitability of this
software for any purpose. It is provided "as is" without express
or implied warranty.
Copyright Jens Maurer 2000
Permission to use, copy, modify, sell, and distribute this
software is hereby granted without fee provided that the above
copyright notice appears in all copies and that both that
copyright notice and this permission notice appear in supporting
documentation,
Jens Maurer makes no representations about the suitability of this
software for any purpose. It is provided "as is" without express
or implied warranty.
Adaptable closures
Phoenix V0.9
Copyright (c) 2001-2002 Joel de Guzman
This software is provided 'as-is', without any express or implied
warranty. In no event will the copyright holder be held liable for
any damages arising from the use of this software.
Permission is granted to anyone to use this software for any
purpose, including commercial applications, and to alter it and
redistribute it freely, subject to the following restrictions:
1. The origin of this software must not be misrepresented; you
must not claim that you wrote the original software. If you
use this software in a product, an acknowledgment in the
product documentation would be appreciated but is not
required.
2. Altered source versions must be plainly marked as such, and
must not be misrepresented as being the original software.
3. This notice may not be removed or altered from any source
distribution.
URL: http://spirit.sourceforge.net/
Copyright Jens Maurer 2000
Copyright Maarten Keijzer 2000
Copyright Herv? Br?nnimann, Guillaume Melquiond, Sylvain Pion
2002 - 2003
Permission to use, copy, modify, sell, and distribute this
software is hereby granted without fee provided that the above
copyright notice appears in all copies and that both that
copyright notice and this permission notice appear in supporting
documentation,
None of the above authors nor Polytechnic University make any
representation about the suitability of this software for any
purpose. It is provided "as is" without express or implied
warranty.
Copyright (C) 2000, 2001 Stephen Cleary
This file can be redistributed and/or modified under the terms
found in "copyright.html". This software and its documentation is
provided "as is" without express or implied warranty, and with no
claim as to its suitability for any purpose.
See http://www.boost.org for updates, documentation, and revision
history.
boost/python/detail/python22_fixed.h
Copyright (c) 2001, 2002 Python Software Foundation; All Rights
Reserved
Copyright (c) 1998-2002 Dr John Maddock
Copyright (c) 2003 Doug Gregor
Permission to use, copy, modify, distribute and sell this software
and its documentation for any purpose is hereby granted without
fee, provided that the above copyright notice appear in all copies
and that both that copyright notice and this permission notice
appear in supporting documentation. Dr John Maddock makes no
representations about the suitability of this software for any
purpose. It is provided "as is" without express or implied
warranty.
Copyright (C) 2001-2003 William E. Kempf
Permission to use, copy, modify, distribute and sell this software
and its documentation for any purpose is hereby granted without
fee, provided that the above copyright notice appear in all copies
and that both that copyright notice and this permission notice
appear in supporting documentation. William E. Kempf makes no
representations about the suitability of this software for any
purpose. It is provided "as is" without express or implied
warranty.
boost/thread/detail/force_cast.hpp
boost/thread/detail/singleton.hpp
Copyright (C) 2001 Mac Murrett
Permission to use, copy, modify, distribute and sell this software
and its documentation for any purpose is hereby granted without
fee, provided that the above copyright notice appear in all copies
and that both that copyright notice and this permission notice
appear in supporting documentation. Mac Murrett makes no
representations about the suitability of this software for any
purpose. It is provided "as is" without express or implied
warranty.