**********************************************************************
* IBM ServeRAID DumpLog and ClearLog version 3.0 Log Capture Utility *
* README.TXT *
* Version 1.0 *
**********************************************************************
CONTENTS
________
1.0 Overview
1.1 Supported operating systems
1.2 Supported ServeRAID Controllers
1.3 Security issues
1.4 Limitations
1.5 Capturing multiple sets of logs
2.0 Change history
3.0 Installation and setup instructions
3.1 Running from a ServeRAID DOS Command Line Diskette
3.2 Running under Windows NT, Windows 2000/2003 and OS/2 Warp
3.3 Running under SCO OpenServer and SCO Unixware
3.4 Running under Linux
4.0 Troubleshooting tips
5.0 Web Site and Support Phone Number
6.0 Trademarks and Notices
7.0 Disclaimer
1.0 Overview
_____________
The purpose of the DUMPLOG file is to quickly capture ServeRAID configuration
and event logs for service or support on your ServeRAID disk subsystem. This
batch/script file uses the ServeRAID command line utility called IPSSEND and
automates a number of useful commands, then compiles the output into a standard
text file that can be used to understand and identify issues
1.1 Supported operating systems
- Most version of DOS
- Microsoft Windows NT 4.0, all versions
- Microsoft Windows 2000, all versions
- Microsoft Windows 2003
- Microsoft WindowsXp
- OS/2 Warp
- SCO OpenServer
- SCO Unixware
- Linux
1.1 Supported ServeRAID Controllers:
- Onboard ServeRAID Controllers
- PC ServeRAID SCSI Controller,
Option p/n70G8489, FRU p/n06H9334
- ServeRAID II Ultra SCSI Controller,
Option p/n76H3584, FRU p/n76H3587
- Netfinity ServeRAID-3H Ultra2 SCSI Controller,
Option p/n01K7207, FRU p/n01K7396
- Netfinity ServeRAID-3HB Ultra2 SCSI Controller,
Option p/n37L6086, FRU p/n01K7396
- Netfinity ServeRAID-3L Ultra2 SCSI Controller,
Option p/n01K7364, FRU p/n01K7352
- Netfinity ServeRAID-4H Ultra160 SCSI Controller,
Option p/n37L6889, FRU p/n37L6892
- Netfinity ServeRAID-4L Ultra160 SCSI Controller,
Option p/n37L6091, FRU p/n09N9540
- Netfinity ServeRAID-4M Ultra160 SCSI Controller,
Option p/n37L6080, FRU p/n37L7258
- Netfinity ServeRAID-4M Ultra160 SCSI Controller (Japan),
Option p/n19K0565, FRU p/n00N9543 (Japan)
- ServeRAID-4Lx Ultra160 SCSI Controller,
Option p/n06P5740, FRU p/n06P5741
- ServeRAID-4Mx Ultra160 SCSI Controller,
Option p/n06P5736, FRU p/n06P5737
- ServeRAID-5i Controller,
Option p/n25P3492, FRU p/n32P0016
- ServeRAID-6M Controller (128MB Cache),
Option p/n32P0033, FRU p/n02R0985
- ServeRAID-6M Controller (256MB Cache),
Option p/n02R0988, FRU p/n TBD
1.3 Security issues
The output files obtained from running DUMPLOG are in standard text format
and are available for viewing. The tool captures the ServeRAID array and
logical disk configuration information including physical information
about attached devices. For organizational purposes, we date and time
stamp the file and query for the name of the system as applicable for the
operating system.
1.4 Limitations
DUMPLOG for DOS, Microsoft Windows NT, Windows 2000 and OS/2 will pull the
ServeRAID logs for 1 adapter at a time. If you have multiple adapters in a
system, a separate command must be run for each adapter.
1.5 Capturing multiple sets of logs
It is very important to capture ServeRAID logs using a naming convention
that can identify the server clearly. The tool supports long filenames for
the operating system that also support long filenames. If IBM Service and
Support determines an action plan for the system, it is very important
that we can identify the system in the environment.
When capturing logs on many adapters and systems, save the logs to a
diskette. The ServeRAID logs are usually 12kb to 20kb in size and you can
easily fit many sets of logs on one diskette.
2.0 Change history
- Dumplog version 3.0 added support for additional IPSSEND commands
first implemented in version 6.10. IPSSEND version 6.10 is required
3.0 Installation and setup instructions
3.1 Running from a ServeRAID DOS Command Line Diskette
1. Download the Command Line diskette for the current version of ServeRAID
or version 6.10, whichever version is higher, from the following URL,
ServeRAID - Software Matrix
http://www-3.ibm.com/pc/support/site.wss/MIGR-495PES.html
2. Create the DOS bootable Command Line diskette per the instructions
3. Copy the DUMPLOG.BAT and CLEARLOG.BAT file to the root of the diskette
4. See command syntax in section 3.2 to run this command under DOS
3.2 Running under Windows NT, Windows 2000/2003 and OS/2 Warp
1. Download the dumplognt4.zip, dumplogw2k_xp.zip, dumplogw2003.zip or
for OS/2 Warp download dumplogos2.zip.
2. Extract the files to the local disk drive or to a floppy diskette for
portability.
3. Open a Command Prompt.
4. Run the DUMPLOG command using the following command syntax:
Command syntax for DOS/Windows NT/2000/2003/OS/2 Warp
Usage is:
DUMPLOG filename [n]
Where:
filename - the name of the log file to be created (this will abort if
the file selected exists)
n - ServeRAID adapter number (optional - defaults to 1)
DUMPLOG COMP_SERVERNAME_SITE_MODEL#_SERIAL#_A1.TXT 1
DUMPLOG COMP_SERVERNAME_SITE_MODEL#_SERIAL#_A2.TXT 2
DUMPLOG COMP_SERVERNAME_SITE_MODEL#_SERIAL#_A3.TXT 3
or
DUMPLOG COMPANY_SITE_86652RY_23A7698_A1.TXT 1
DUMPLOG COMPANY_SITE_86652RY_23A7698_A2.TXT 2
DUMPLOG COMPANY_SITE_86652RY_23A7698_A3.TXT 3
3.3 Running under SCO OpenServer and SCO Unixware
1. Download os_dump.tar (SCO OpenServer) or uw_dump.tar (SCO Unixware)
depending on which NOS you are running.
2. Copy the *.tar file to a sub-directory of your choice (e.g. /tmp).
It is not recommended that you extract the *.tar file to (or run from)
the root directory (/). If you plan to collect ServeRAID logs at other
times, it is recommended to create a separate subdirectory (e.g
/ipsdump) to keep these files.
3. Extract the utilities from the associated *.tar file using the
following command:
tar xvf <tar_filename>
The following files are extracted:
NameÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿSize
clearlog.shÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿ1887
dumplog.shÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿ4658
ipssend (os)ÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿ210995
ipssend (uw)ÿÿÿÿÿÿÿÿÿÿÿÿÿÿ117040
4. Using one of the two methods described below, run the dumplog.sh script
to obtain ServeRAID log information.
a. # sh dumplog.sh
b. # ./dumplog.sh
This utility will prompt you for the model-type and serial number of
the system you are running this on. It is important that you supply the
correct information when sending these logs for analysis. Do not enter
hyphens or spaces when supplying model-type and serial number
information.
5. Using one of the two methods described below, run the clearlog.sh
script to clear the ServeRAID log information.
a. # sh clearlog.sh
b. # ./clearlog.sh
3.4 Running under Linux
1. Download dumplog.tgz the directory of your choice.
2. Uncompress it with the command tar -xzvf dumplog.tgz
3. Change into the newly created ./dumplog directory. You should have the
files ipssend, dumplog.sh and clearlogs.sh in this directory.
4. At root, run the command ./dumplog.sh
5. This utility will prompt you for the model-type and serial number of
the system you are running this on. It is important that you supply the
correct information when sending these logs for analysis. Do not enter
hyphens or spaces when supplying model-type and serial number
information. Send all the *.txt files created to IBM support
6. If instructed, run the command ./clearlogs to erase the ServeRaid logs.
Running this command will delete the logs on every ServeRaid controller
installing in your server.
4.0 Troubleshooting tips
ServeRAID - Mismatched software levels can result in system problems
http://www-3.ibm.com/pc/support/site.wss/MIGR-42022.html
Recovering from single disk failures
http://www-3.ibm.com/pc/support/site.wss/MIGR-40364.html
Recovering from Multiple Defunct Drives:
http://www-3.ibm.com/pc/support/site.wss/MIGR-39144.html
5.0 Web Sites and Support Phone Number
_______________________________________
o You can download new and updated files for the IBM ServeRAID products
from the IBM Support Web site:
http://www.ibm.com/pc/support/
o With the original purchase of an IBM hardware product, you have
access to extensive support coverage. During the IBM hardware
product warranty period, you may call the IBM Personal Computer
HelpCenter (1-800-772-2227 in the U.S.) for hardware product
assistance covered under the terms of the IBM hardware warranty.
6.0 Trademarks and Notices
___________________________
The following terms are trademarks of the IBM Corporation in the
United States or other countries or both:
Active PCI OS/2 Warp
HelpCenter PC Server
IBM Predictive Failure Analysis
Netfinity ServeRAID
Netfinity Manager ServerGuide
OS/2
UNIX is a registered trademark in the United States and other
countries and is licensed exclusively through The Open Group.
Microsoft, Windows, and Windows NT are trademarks or registered
trademarks of Microsoft Corporation.
Java and all Java-based trademarks and logos are trademarks or
registered trademarks of Sun Microsystems, Inc. in the United
States, other countries, or both.
Other company, product, and service names may be trademarks
or service marks of others.
7.0 Disclaimer
_______________
THIS DOCUMENT IS PROVIDED "AS IS" WITHOUT WARRANTY OF ANY KIND.
IBM DISCLAIMS ALL WARRANTIES, WHETHER EXPRESS OR IMPLIED,
INCLUDING WITHOUT LIMITATION, THE IMPLIED WARRANTIES OF FITNESS
FOR A PARTICULAR PURPOSE AND MERCHANTABILITY WITH RESPECT TO THE
INFORMATION IN THIS DOCUMENT. BY FURNISHING THIS DOCUMENT, IBM
GRANTS NO LICENSES TO ANY PATENTS OR COPYRIGHTS.
Note to U.S. Government Users -- Documentation related to
restricted rights -- Use, duplication or disclosure is subject
to restrictions set forth in GSA ADP Schedule Contract with
IBM Corporation.
Download Driver Pack
After your driver has been downloaded, follow these simple steps to install it.
Expand the archive file (if the download file is in zip or rar format).
If the expanded file has an .exe extension, double click it and follow the installation instructions.
Otherwise, open Device Manager by right-clicking the Start menu and selecting Device Manager.
Find the device and model you want to update in the device list.
Double-click on it to open the Properties dialog box.
From the Properties dialog box, select the Driver tab.
Click the Update Driver button, then follow the instructions.
Very important: You must reboot your system to ensure that any driver updates have taken effect.
For more help, visit our Driver Support section for step-by-step videos on how to install drivers for every file type.