●カルドブログのテスト

だれでも書ける みんなで作る カルドセプトのブログのテスト

セプターなのなの。

セプターなのなの、の出張所です。

トップページ » fira » aaa

aaa

File Name: dsa_update_preboot_readme.txt
******************************************************************
| |
| IBM(R) Preboot Dynamic System Analysis (DSA) |
| Version 9.65 |
| |
| (C) Copyright International Business Machines Corporation |
| 2004, 2012. 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 Update embedded DSA Preboot

3.0 Running Dynamic System Analysis

4.0 Using the DSA Main Menu

5.0 Using the DSA Interactive Menu

6.0 Using the DSA Graphical User Interface

7.0 Accessing and viewing DSA output
7.1 Naming convention used for output files and directories
7.2 Exporting HTML files created by DSA

8.0 Sending DSA output to IBM xSeries Service and Support

9.0 Known problems and workarounds

10.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 configuration
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 ESXi EH Information
o GoVault Tape Drive information
o Disk Management information
o MAX5 Memory Expansion Unit

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
o Hard Drive 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:
x3100 M4 (2582)
x3200 M2 (4367, 4368)
x3200 M3 (7327, 7328)
x3250 M2 (7657, 4190, 4191, 4194)
x3250 M3 (4251, 4252, 4261)
x3250 M4 (2583)
x3300 M4 (7382)
x3400 M2 (7836, 7837)
x3400 M3 (7378, 7379)
x3500 M2 (7839)
x3500 M3 (7380)
x3500 M4 (7383)
x3530 M4 (7160)
x3550 M2 (7946, 4198)
x3550 M3 (7944, 4254)
x3550 M4 (7914, 7383)
x3620 M3 (7376)
x3630 M3 (7377)
x3630 M4 (7158, 7519)
x3650 M2 (7947, 4199)
x3650 M3 (7945, 4255, 5454)
x3650 M4 (7915)
x3690 X5 (7147, 7148, 7149, 7192)
x3750 M4 (8722, 8733)
x3755 M3 (7164)
x3850 X5 (7143, 7145, 7146, 7191)
x3950 X5 (7143, 7145, 7146, 7191)
iDataplex dx360 M2 (7321, 7323)
iDataplex dx360 M3 (6391)
iDataplex dx360 M4 (7912, 7913, 7918, 7919)
Smart Analytics System (7949)
HS22 (7870, 1936, 7809, 1911)
HS22V (7871, 1949)
HS23 (7875, 1929)
HS23E (8038, 8039)
HX5 (1909, 1910, 7872, 7873)
Flex System x240 Compute Node (8737, 8738, 7863)
Flex System x220 Compute Node (7906, 2585)
Flex System x440 Compute Node (7917, 2584)

Supported Server Options
o Ethernet adapter
Broadcom 1Gb Ethernet CFFh Expansion Card
Broadcom 10Gb Ethernet CFFh Expansion Card for IBM BladeCenter
Broadcom Netextreme II
Ethernet Expansion Card (CIOv) for IBM BladeCenter
2/4 Port Ethernet Expansion Card (CFFh) for IBM BladeCenter
NetXtreme II 1000 Express Quad port Ethernet Adapter
NetXtreme II 1000 Express Dual Port Ethernet Adapter
Broadcom 10Gb BaseT dual port NIC
Broadcom Dualrunner/ Quad-Runner NetXtreme I
Broadcom 1Gb 4 port Mezz Card Tier 1
Emulex 10GbE vNIC w/ BE3 Chipset
Emulex 2-Port 10Gb Multi-function IO Adapter (CFFh) for IBM BladeCenter (vNIC)
Emulex 10Gb 4 port Mezz card with FCoE/iSCSI key for System X Tier 1
Emulex 2+2 10Gb (CFFh) for IBM BladeCenter (vNIC)
Emulex Dual Port 10GbE SFP+ Embedded Adapter
Emulex Virtual Fabric Adapter II for HS23 iSCSI and FCoE upgrade
IBM NetXtreme II 1000 Express Ethernet Adapter
Intel 10GB SFP+ NIC
Intel X540-T2 Dual Port 10GBase-T Adapter
o Fibre Channel adapter
Emulex 4G FC exp. card
Emulex 4G SFF FC exp.
Emulex 4Gb/s FC PCI Express HBA (lpe11000/lpe11002)
Emulex 4Gb/s FC PCI-X 2.0 HBA (lp11000/lp11002)
Emulex 8Gb FC Single-port HBA for IBM System x
Emulex 8Gb FC Dual-port HBA for IBM System x
Emulex 10Gb/s Fibre Channel over Ethernet Dual Channel Converged Network Adapter
Emulex PCI-e Gen2.0 Dual Port 10Gb NIC
Emulex 2-Port 10Gb Multi-function IO Adapter
Emulex 16Gb FC Single/Dual-port HBA
Emulex 8Gb FC Mezz card
QLogic 4G/8G FC CFF exp. card
QLogic 4G/8G SFF FC exp. card
QLogic 2-Gbps Fibre Channel HBA
QLogic 4G and 8G FC single port HBA
QLogic 4G and 8G FC dual port HBA
QLogic iSCSI PCIe HBA
QLogic iSCSI PCIe dual port HBA
Qlogic 10Gb FCoE Dual Port
Qlogic 10GbE CFFh DC
Qlogic 8Gb FC 2 port mezz card Tie 1 for IBM Flex System
QLogic Dual Port 10GbE SFP+ Embedded Adapter for IBM System x
Qlogic 8200 Dual Port 10GbE SFP+ Adapter
Brocade 4 Gb FC Single-port HBA
Brocade 4 Gb FC Dual-port HBA
Brocade 8Gb FC Single-port HBA
Brocade 8Gb FC Dual-port HBA
Brocade 10Gb Dual-port CNA
Brocade 2-port 10Gb Converged Network Adapter
Brocade 16Gb FC 2 port Mezz Card Tier 2
Brocade 16Gb FC Single/Dual-port HBA
IBM SAS HBA controller
LSI 1068 SAS HBA
o Network adapter
IBM 10 GbE PCIe SR Server Adapter
IBM NetXtreme II 10 GigE Express Fiber SR Adapter
Intel PRO/1000 PT Dual Port Server Adapter (no diagnostic support)
Intel PRO/1000 PT Quad Port Server Adapter (no diagnostic support)
Intel PRO/1000 PF Server Adapter (no diagnostic support)
Intel QuadPort Ethernet Server Adapter (no diagnostic support)
CFFh Intel Ethernet Adapter (no diagnostic support)
Intel 10GB SFP+ NIC
Intel X540-T2 Dual Port 10GBase-T Adapter for IBM System x
Intel x520 Dual Port 10GbE SFP+ Embedded Adapter
o RAID adapter
Adaptec IBM ServeRAID 6i +
Adaptec IBM ServeRAID 7k
Adaptec IBM ServeRAID 7t
Adaptec IBM ServeRAID 8i, 8k, 8k-l and 8s
LSI MR 10is
LSI IR 1078, 1064, 1064e and 1068e
LSI MegaRAID 8480
LSI ServeRAID MR 10i, 10ie, 10is, 10k and 10m
LSI ServeRAID M1015, M5014, M5015 and M5025
LSI ServeRAID M1110, M1115, M5016, M5110, M5110e, M5120 and M5115
LSI ServeRAID H1110, H1135
LSI ServeRAID M1100 Upgrade, M5100 Upgrade
LSI ServeRAID B5015
LSI RAID 0//10 FDE SAS-2 6GB
LSI ServeRAID C105
Shikra, IBM Flex System Storage Mezzanine Expansion (SME)
o Tape drive
IBM DDS5 36/72 SCSI
IBM DDS5 36/72 USB
IBM DDS5 36/72 SATA
IBM DDS6 80/160 USB
IBM LTO2 HH 200/400 SCSI
IBM LTO2 FH 200/400 SCSI
IBM LTO3 HH 400/800 SAS
IBM LTO3 FH 400/800 SCSI
IBM LTO4 HH 400/800 SAS
IBM LTO5 HH 400/800 SAS
IBM VS160 tape drive
IBM GoVault tape drive
IBM RDX 160/320/500 GB External/Internal USB 3.0 Drive
o Daughter card
cKVM Daughter Card for IBM BladeCenter
LSI BR10i, BR10ie, BR10il
o BPE-4
o GPU
nVIDIA Quadro (4000, 5000, 6000, 600)
nVIDIA Tesla (M2090, M2090update, X2090, X2090Update)
nVIDIA “Gemini” Kepler GPU (K10)

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 Manager Logs
—————————————–

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

o ServeRAID 4,5,6,7k
o ServeRAID-7t SATA RAID
o ServeRAID-8i, 8k and 8k-l

2.0 Update embedded DSA Preboot
———————————

It will not affect any device drivers.

2.1 Installing and Setup Instructions for the following system:
x3200 M3 (7327, 7328)
x3250 M3 (4251, 4252, 4261)
x3400 M2 (7836, 7837)
x3400 M3 (7378, 7379)
x3500 M2 (7839)
x3500 M3 (7380)
x3550 M2 (7946, 4198)
x3550 M3 (7944, 4254)
x3620 M3 (7376)
x3630 M3 (7377)
x3650 M2 (7947, 7945, 4199, 7949)
x3650 M3 (7945, 4255, 5454)
x3690 X5 (7148, 7149, 7147, 7192)
x3755 M3 (7164)
x3850 M2 (7141, 7144, 7233, 7234)
x3850 X5 (7143, 7145, 7146, 7191)
x3950 M2 (7141, 7144, 7233, 7234)
x3950 X5 (7143, 7145, 7146, 7191)
iDataplex dx360 M2 (6380, 7321, 7323)
iDataplex dx360 M3 (6391)
HS12(8014, 8028, 1916)
HS22 (7870, 1936, 7809, 1911)
HS22V (7871, 1949)
HX5 (1909, 1910, 7872, 7873)
LS22/LS42 (7901, 7902)

IMPORTANT:

o The recommended firmware update sequence is IMM followed by uEFI followed by
DSA Preboot.

o Due to an Intel errata, if your server is running a 32-bit Linux Operating
System, C-states may need to be disabled while updating uEFI, IMM, or DSA
Preboot through the Linux command line interface. See RETAIN TIP H195678 for
more information. Updates performed through the AMM, Bootable Media Creator,
or the IMM web or CLI interfaces do not have this requirement.

o In Windows 2008, the firewall may be enabled by default. In some
configurations, this could prevent the flash utility from
succeeding. The firewall may need to be disabled if it is
suspected to be preventing the update traffic.

o If you are updating DSA Preboot using VMware, the following
steps should be completed prior to the update to ensure that the
flash utility can connect to the IMM.
1. esxcfg-firewall -o 623,udp,out,USBLan
2. run dsa
3. esxcfg-firewall -c 623,udp,out

The procedure to update the DSA Preboot is as follows:

2.1.1 Using the graphical user interface (Only Available on Windows platform)

o Extraction of the package contents

– Run the DSA Preboot Update by double-clicking the .EXE.

– Choose “Extract to Hard Drive” and click the “Next” button.

– Choose a directory into which the Windows update files will be saved
in the “Save As” dialog.

– The files extracted are all the files that are necessary to perform a
DSA Preboot Update under Windows.

– Click the “Exit” button.

o Run DSA Preboot Update

– Run the DSA Preboot Update by double-clicking the Preboot update binary.

– Choose “Perform Update” and click the “Next” button.

– If the update is meant for the system on which it is running, the
“Next” button will appear. Click the “Next” button to continue.

– Click the “Exit” button.

2.1.2 Using the command line interface
Prerequisites:
On Linux, the Preboot Update package should have the permission to be
executable with the following comand:
chmod u+x

o Extraction of the package contents

– Run the DSA Preboot Update with the following command line:
-x where is the path to which the Linux update files will be
extracted.

o Run DSA Preboot Update

– Run the DSA Preboot Update with the following command line:
-s

2.1.3 The contents of Preboot update packages

o On Windows platform

ibm_fw_dsa_dsyte2w-9.65_windows_32-64.exe package contents:

– This readme file
– The DSA Preboot firmware update file named dsa_dsyte2w_95232_9.upd
– An INF file, named ibm_rndis_server_os.inf and a CAT file, named
device.cat are required by Windows operating systems to detect and
use the IMM’s Ethernet over USB functionality.
– A 32-bit flash utility named iflash.exe
– A 64-bit flash utility named iflash64.exe
– A 32-bit flash utility named wflash.exe
– A 64-bit flash utility named wflash64.exe

o On Linux platform

ibm_fw_dsa_dsyte2w-9.65_linux_32-64.bin package contents:

– This readme file
– DSA Preboot firmware update file named dsa_dsyte2w_95232_9.upd
– A 32-bit flash utility named iflash
– A 64-bit flash utility named iflash64
– A 32-bit flash utility named lflash
– A 64-bit flash utility named lflash64

2.2 Installing and Setup Instructions for the following system:
o x3100 M4 (2582)
o x3250 M4 (2583)
o x3300 M4 (7382)
o x3500 M4 (7383)
o x3530 M4 (7160)
o x3550 M4 (7914)
o x3630 M4 (7158)
o x3650 M4 (7915)
o x3750 M4 (8722, 8733)
o HS23 (7875, 1929)
o HS23E (8038, 8039)
o iDataplex dx360 M4 (7912, 7913, 7918, 7919)
o Flex System x240 Compute Node (8737, 8738, 7863)
o Flex System x220 Compute Node (7906, 2585)
o Flex System x440 Compute Node (7917, 2584)

The procedure to update the DSA Preboot is as follows:

2.2.1 Using the graphical user interface
– Launch UXSPI application and accept the license agreement.
– Click the “Next” button to continue.
– Select the “Update the local machine” checkbox and then click the
“Next” button to continue.
– Select the “Check IBM WebSite” checkbox if Preboot payload is
not downloaded to the local; otherwise select the “Look in the
local directory” checkbox to manually select the location of the
payload.
– Select the “Latest available individual update” checkbox and then
click the “Next” button to continue.
– Select the available item and then click the “Next” button to continue.
– Click the “Next” button till the update complete.

2.2.2 Using the command line interface
– Download the UXSPI binary to the local folder.
– Download UXSPI SEP package and its XML file to the same folder if
there is an available UXSPI SEP package.
– Copy Preboot update payload (the file with suffix .uxz) and its XML file to the local folder.
– Launch UXSPI binary to perform the update as follow:
up -e all -i -s all –latest

NOTE:
If the UXSPI binary and updates are not in the same directory,
then you need to specify the ‘-l’ option, e.g, ‘-l ‘.

2.3 Installing and Setup Instructions for the following systems running
IBM customized ESXi 4.1U1 and later:

x3100 M4 (2582)
x3250 M4 (2583)
x3200M3 (7327, 7328)
x3250M3 (4251, 4252, 4261)
x3400M2 (7836, 7837)
x3400M3 (7378, 7379)
x3500M2 (7839)
x3500M3 (7380)
x3550M2 (7946, 4198)
x3550M3 (7944, 4254)
x3755 M3 (7164)
x3620M3 (7376)
x3630M3 (7377)
x3650M2 (7947, 7945, 7949, 4199)
x3650M3 (7945, 4255, 5454)
x3690X5 (7148, 7149, 7147, 7192)
x3850 X5/3950 X5 (7145, 7146, 7143, 7191)
x3950 M2 (7141, 7144, 7233, 7234)
x3650 M4 (7915)
x3550 M4 (7914)
x3500 M4 (7383)
iDataplex dx360 M2 (6380, 7321,7323)
iDataplex dx360 M3 (6391)
HS12 (8014, 8028, 1916)
HX5 (7872, 1909, 7873, 1910)
HS22 (7870, 1936, 7809, 1911)
HS22V (7871, 1949)
HS23 (7875, 1929)
Flex System x240 Compute Node (8737, 8738, 7863)
Flex System x220 Compute Node (7906, 2585)
x3530 M4 (7160)
x3630 M4 (7158)
x3750 M4 (8722, 8733)
HS23E (8038, 8039)
iDataplex dx360 M4 (7912, 7913, 7918, 7919)
x3300 M4 (7382)
Flex System x440 Compute Node (7917, 2584)
For additional information, please refer to
http://download.boulder.ibm.com/ibmdl/pub/systems/support/system_x_pdf/ibm_utl_uxspi_9.00_anyos_noarch.pdf

2.3.1 Assumptions and prerequisites
– To perform updates for VMware ESXi, you must run UXSPI on a local non-ESXi system
to update a remote ESXi host. Running UXSPI or DSA update packages in the ESXi
local or remote tech support mode console is not supported.
– The system must be running a supported operating system.
– The target system must be reachable on port 5989 through CIM-HTTP.
– For updates from an FTP server, the server must be properly configured.

2.3.2 Scenario tasks
Before running UXSPI to update Preboot DSA, the following conditions must be met:
1. The system must be IMM-based.
2. The Firewall is turned off.
3. SSH is enabled.
– From the command line, use the UXSPI command to update the firmware on the target system using the update option.

To update from a local repository:
update -l local_repository_path -L –vmware-esxi=https://userID:password@vmware_esxi_system_IPaddress:port

To update from an FTP server:
update –vmware-esxi=https://userID:password@vmware_esxi_system_IPaddress:port
–esxi_updatefile=ftp://userid:password@ftp_server_IPaddress/path

For more information on these options, please refer to “ibm_utl_uxspi_9.00_anyos_noarch.pdf”.

– The UpdateXpress System Pack Installer compares the firmware inventory of the target system
to the updates available in the repository or on the FTP server, and applies the recommended updates.

3.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
“5.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 “8.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 “7.0 ACCESSING
AND VIEWING DSA OUTPUT.”

NOTE: 1. ONCE THE STANDALONE MEMORY DIAGNOSTIC GETS ANY ERROR THE STANDALONE
MEMORY DIAGNOSTIC EXITS EXECUTION IMMEDIATELY.

2. THE STANDALONE MEMORY DIAGNOSTIC ONLY PASSES LAST TEST RESULT TO DSA
NO MATTER HOW MANY LOOPS HAVE BEEN RUN.

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

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

5.0 USING THE DSA INTERACTIVE MENU
———————————–

The DSA Interactive menu has the following options:

IBM DSA Interactive.

1 – Data Collection.
2 – Diagnostics.
3 – Features on Demand (FoD).
4 – Copy Collected System Information to Local Media.
5 – Send Collected System Information to IBM Server or Customized FTP server.
Q – 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)
Q – Quit to previous menu.

On entering number “2”

Diagnostics:

1 – Execute Diagnostic Test.
2 – View Diagnostic Results.
Q – Quit to previous menu

NOTE: FOR REMOTE ACCESS VIA SOL (SERIAL OVER LAN), COMMAND LINE INTERFACE IS THE ONLY
INTERFACE SUPPORTED.

6.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 Exit – Quit the utility.

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

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

__

where
o is the machine type and model number of
the server.
o is the serial number of the server.
o is the date that DSA collected information.
o

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.

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

8.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. If it fails,
DSA will try to use Hypertext Transfer Protocol (HTTP).

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 date time
stamp.

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

9.0 KNOWN PROBLEMS AND WORKAROUNDS
———————————–

DSA has the following known problems and workarounds:

o If you have ServeRAID (M1015) SAS/SATA Controller, 46M0831
installed, you will need one of the following:
– uEFI GYE133A or greater for x3200 M3 and x3250 M3
– uEFI Y4E145B or greater for x3400 M2, x3400 M3, x3500 M2 and x3500 M3
– uEFI D6E145C or greater for x3550 M2, x3550 M3, x3650 M2 and x3650 M3

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. See Retain Tip H197557.

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 If you are running DSA 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 DSA is unable to collect RAID information from 8e SAS/SATA HostRAID
controller.

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 dx360 M2, no Ethernet NIC test is available in the diagnostics
list in Preboot DSA.

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 For the HS22V, the slot information of devices and bridges may be blank.

o When user updates the IBM Preboot DSA to DSA Preboot 3.20 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 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 For the System x3200 M3 (7327, 7328) and System x3250 M3 (4251,
4252, 4261), the hyper-threading status for the G6950 2.8G CPU may be
incorrect.

o When the Preboot DSA is booted from a CD/DVD, sometimes the CD/DVD
is not automatically ejected (as expected) after user type “exit” in
the main menu of DSA. In this case, user needs to reboot the server
and manually eject the CD/DVD ROM by pressing the bottom on the front
panel for the optical drive.

o This version of DSA does not support ServeRAID B5015 SSD controller.

o When LSI IR ServeRAID is configured to RAID 1E, DSA might show the
configuration as “10”.

o When disk is configured as RAID, DSA does not report disk error
upon spin speed reduction.

o When running Intel NIC test, there might be some redundant message
shown which is not relevant to the test result.

o On x3850/3950 X5, DSA may report the total physical memory size incorrectly.

o On HS22V (7871,1949), DSA can not detected PCI slot information of
Broadcom 10Gb Ethernet CFFh Expansion Card for IBM BladeCenter and 2/4
Port Ethernet Expansion Card (CFFh) for IBM BladeCenter.

o Serial Number of some devices may be shown incorrectly in Other VPD
table on HS22V (7871,1949).

o The association between PCI Slot and Device might be inaccurate on the following systems:
x3850 X5 (7145, 7146)
x3950 X5 (7145, 7146)
HS22V (7871)
HX5 (7872, 1909)
See Retain Tip H197557.

o Monitor information is not detected on x3755 M3 (7164) sometimes. The frequency is about 10 percents.

o Some error logs for internal use would display in “DSA Error Log”.

o On x3400 M2(7836, 7837) and x3500 M2(7839) SMART Error Logs table is missing
in Drive Health page sometimes.

o The information about Level 1,2,3 Cache Enable is not shown accurately sometimes.

o If there is no data for a particular field, this will be left blank. This
is most often encountered in common tables where we display instances from
multiple data sources.

o For Lynnfield 2.4G X3430 CPU & Clarkdale G6950 2.8G CPU, the
Hyper-Threading status collected is not correct.

o On x3250 M3(4251, 4252, 4261), the firmware and BIOS version of
Emulex 10GbE Virtual Fabric Adapter is missing in Firmware/VPD
page.

o On HX5(7872,1909) multiple node, only Diagnostic VPD for the
primary node is shown in Diagnostic VPD table.

o An unexpected menu may pop up if the user clicks the right mouse
button during the initialization of the GUI. Please wait for the
GUI startup to complete before attempting to use the tool.

o When execute the update tool on a newly installed Windows 2003
system a pop- up window will appear and ask user to reboot the OS,
if user click “OK” system will go reboot, and update procedure
could not complete. In this case, it requires user NOT to click
“OK” untill the update procedure is finished.

o The user can not flash Embedded Preboot on VMware ESX3.5 prior to U4.

o When flashing DSA Preboot using wflash/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 The user must disable x2apic in uEFI setting before launching
Embedded Preboot on IBM x3850 X5 dual node.

o In the event of extended collections times it may be helpful to
disconnect external devices temporarily. This could include
unplugging fibre cables or additional USB devices where information
on these devices is not essential to the data collection. It can not
be determined what the minimum amount of hard disk drives are for
this issue to arise. This is due to the hard disk drives technologies
used by various vendors. The only way to overcome this issue is to
change environment variables as follow and run Portable DSA:
Windows:
set DSA_EXCLUDE=diskmgt,hardwareinfo,tapehdd,smart
Linux:
export DSA_EXCLUDE=libdiskmgt,libhardwareinfo,libtapehdd,libsmart

o Retain Tip H197177 – DSA PREBOOT INCORRECTLY DISPLAYS CHINESE LICENSE AGREEMENT

o Retain Tip H197142 – DSA “VOLUMES/MOUNT POINTS” TABLE “LABEL”…COLUMNS ARE EMPTY

o DSA will not show the correct diagnostic result after running LSI HDD Diagnostic Test
when SW RAID is configured. DSA doesn’t support this configuration currently
due to LSI CIM provider limitation.

o Retain tip H203200 – NVIDIA 2075/2090 GPU FAILS IN DSA PREBOOT DIAGS

o Since DSA 4.00, Preboot DSA embedded uses MCP 6.1 for Romley systems.
Since DSA 4.00, Preboot DSA embedded still uses MCP 5.2 for legacy systems.
Since DSA 4.00, Preboot DSA standalone (CD boot or USB-key boot) uses MCP 6.1 for all systems.

– Preboot DSA (embedded or standalone) using MCP 6.1 doesn’t support the data collection
on QLogic adapter since the QLogic driver 1.01.02.d4 packaged in MCP 5.2 can’t be used in MCP 6.1.

– Software License Agreement (SLA) has traditional Chinese wording issue in MCP 5.2.
This issue is fixed in MCP 6.1 in Preboot DSA 4.00 in 2011. But those systems with
Preboot DSA embedded based on MCP 5.2 still have this issue.

o On x3100 M4 and x3250 M4, the following issues may be found due to the
limitation in IMM:
– The IMM configuration and Environmentals information, such as “IMM configuration”,
“IMM Built-in Self Test”, and “Chassis Event Log”, would be reported as “SP Configurations”,
“BIST Results”, and “SP Logs”.
– The IMM configuration and Environmentals information, such as “IMM configuration”,
“Environmentals”, and “Chassis Event Log”, would not be collected and displayed.

o On x3755 M3, the following issue may be found due to the limitation in iBMC:
– The iBMC configuration and Environmentals information, such as “SP Configurations”,
“Environmentals”, and “SP Logs”, would not be collected and displayed.

o On x3755 M3, the following issue may be found due to the limitation in uEFI:
– The “Slot” information in the table “Devices” in the page “PCI Information” will show
“Onboard” if the corresponding PCI device is option card (not onboard card).
– In the item “Name” in the table “Processor/Core” in the page “Hardware Inventory”,
the number of Node is the same as that of CPU.
(e.g. Node 1 CPU 1, or Node 2 CPU 2, or Node 3 CPU 3)

o On the following systems, PCI devices may miss the corresponding mappings of PCI slots
due to limitations in SMBIOS 2.5 (the previous versions might have the same issue).
– Legacy BIOS systems
– uEFI IMMv1 systems

o Permanent limitation: DSA data collection shows “Unknown” in the item “PartitionSubType” in the table
“Disk Information” in the page “Hardware Inventory” when HDD is in the GUID Partition Table (GPT)
format on uEFI systems.

o For Emulex Options, the Emulex Bios Version information in “Firmware/VPD->BIOS/uEFI”
page and “Emulex->EMXCNA BIOS” page would not be collected and shown due to the
limitation of Emulex Utility.

o Preboot DSA embedded cannot be flashed on VMWare ESX 4.1 on x3755 M3.

o In the HTML outputs collected by Preboot DSA on the following systems with VMWare ESXi key,
no page “VMware ESXi” due to the limitation of MCP6.1.
– Romley systems
– x3755 M3
– x3100 M4
– x3250 M4

o Flashing Preboot DSA between the Preboot DSA levels (like the following examples) with the
different naming conventions on windows or Linux might fail.
– The Preboot DSA level starting with DSYT (e.g. DSYT89O)
– The Preboot DSA level starting with D6YT (e.g. D6YT29A)
– The Preboot DSA level starting with TMYT (e.g. TMYT19A)
– The Preboot DSA level starting with yuoo (e.g. yuoo890)
– The Preboot DSA level starting with y4yt (e.g. y4yt21a)
The user could use the following command of iflash to flash Preboot DSA levels between
the Preboot DSA levels with the different naming conventions successfully.
– iflash64 –package [upd file name] –openoptions 16 –force

o When install the FoD key file(s) on CMM, Switch, or Remote IMM, user must ensure the network
connection not affected by the following elements:
– Http service
– Firewall
– Authorization

o When running FoD key management on Compass Switch, the upgrade sequence (Key installation)
must start from first 32-port to second 32-port, and inverse sequence for the downgrade
(Key uninstallation), or the error message “Firmware Version/Update Issue” may be prompted.

o When using DSA to collect the QLogic inventory, some redundant debug information may be
included in the RAW data due to the limitation of the QLogic utility.

o For the definition of KGU xml do not follow the consistent standard, the emulex FoD will not
be shown in the available FoD list for the system.

o FoD ID for Emulex LAN card Eraptor 49Y4235 will show “N/A” under Emulex command line and
pDSA Emulex page.

o When RAID level 1E is setup using LSI ServeRAID H1110 card, DSA will collect wrong value as
“RAID 10” due to LSI provider limitation. The right value can be fetched using LSI utility
with usage “sas2ircu [controller number] DISPLAY LogicalDevice”

o When user boots up Preboot DSA via SOL, Preboot DSA will hang in CLI mode, but uEFI and
standalone memory test can be loaded normally. This issue only happens on HS23E until
April, 2012.

o For Blade System HS23, in DSA data collection result page for ‘PCI Information’
in ‘Hardware Inventory’ page, the Emulex 1GB port will be shown as a 10GB port
due to Emulex issue.

o IMMv1 embedded Preboot DSA does not support Brocade Tuatara adapter. It is a limitation
because the device driver version 2.3.0.0 in MCP 5.2 does not support this new adapter.

o Some extra pieces of information like the following example (two pieces of information)
are shown in DSA log after the user runs the Brocade Ethernet diagnostic test
Brocade:ExternalEthLoopbackTest.

Brocade:ExternalEthLoopbackTest eth5 Tx frames = 0, Rx frames = 0, OSF frames = 0
05/29/2012 15:18:08
Brocade:ExternalEthLoopbackTest eth5 EthLoopback test run status : Link timeout check
and replace SFP/cable 05/29/2012 15:18:08

o When user is accessing HS23 (7875) or HS23E (8038 or 8039) through telnet remotely,
Preboot DSA cannot be loaded in the SOL session after user selects the option to quit to
Preboot DSA once inside the Memory Test screen.

o The systems with iBMC have the “Hardware Activation Key” installed to enable the function of remote
presence. The information of “Hardware Activation Key” can be captured and shown in DSA (both
Preboot DSA and Portable DSA) outputs (HTML outputs or text outputs). The Blade systems are a sort
of the systems with iBMC, but they are managed by AMM and they do not need the “Hardware Activation
Key”, so the information of “Hardware Activation Key” captured by DSA (both Preboot DSA and Portable
DSA) on the Blade systems is always shown as “Not Installed”.

o DSA will error report some LED’s present status due to IMM’s limitation on some special hardware component.
For the following LEDs:
CPU 2 Board
Fan
PCI
DSA will always report “false” even if the LED exist.

o DSA implemented signature in product build. Please update IMM to 1AOO34V or later before updating pDSA,
or flash failure will occur.

10.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/support/entry/portal/

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-03.ibm.com/systems/management/dsa/

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-03.ibm.com/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/systems/info/x86servers/serverproven/compat/us/

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

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

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

コメントを残す

登録ユーザーのかたはログインしてください [ログイン]

unknown