ServeRAID mismatched software levels can result in system problems

Symptom

Mismatched ServeRAID software levels can result in system problems. Mismatched version levels are not tested together and may result in stability problems when installed and used together for any significant period of time.

Symptoms might include, but are not limited to:

• Defunct Disk Drives (DDD)
• Erratic performance
• Loss of ServeRAID configuration
• POST error messages
• ServeRAID error messages

[@more@]

Note: This document only pertains to systems that meet the following criteria.

• System running ServeRAID II, 3x, 4x, or 4xx controllers.
• Controller running BIOS/firmware version 4.84 or lower.
  
  Click here to .

Solution

When you update ServeRAID software, you must update all RAID software at the same time and to the same level. This will ensure that all levels of the software are compatible. The ServeRAID software includes:

• Device drivers
• BIOS and firmware code
• Command-line programs
• ServeRAID Manager
• IBM ServeRAID Cluster Solution software

IBM Support also suggests that your ServeRAID software be at the latest level. Each software release contains code updates which may increase your system's performance and reliability.

Click here to download the latest ServeRAID software.

Verifying ServeRAID code levels

Use one of following four methods to verify that you are using matched ServeRAID code levels.

Method 1

Observe the ServeRAID splash screen at boot time. The BIOS version will appear. The driver could then be verified by under the driver property page in Device Manager (select the Driver tab). The driver is made up of three files (based on the controller's chipset):

• PowerPC chip based ServeRAID controllers:
  (ServeRAID, ServeRAID II, ServeRAID 3L, ServeRAID 3H, ServeRAID 3HB, and ServeRAID 4H)
  • ipsraidn.sys
  • ipsperf.sys
  • twintail.sys
    
• Intel SCSI chip based ServeRAID controllers:
  (ServeRAID 4L, ServeRAID 4M, ServeRAID 4LX, ServeRAID 4MX)
  • nfrd960.sys
  • nfrdperf.sys
  • twintail.sys
    

Method 2

Run the command IPSSEND GETCONFIG x (where x is the controller number 1-12 targeted for the command). This could be sent to a file with a simple redirection or the "| more" command could be used to pause the text on the screen. The top portion of the GETCONFIG log will list the BIOS, firmware, bootblock, and driver versions. This command will only provide the device driver version if the specific operating system version is ran and not from version on the DOS diskette. Try the following commands:

Note: Replace x with the controller number 1-12 targeted for the command.

• IPSSEND GETCONFIG x
• IPSSEND GETCONFIG x > FILENAME.TXT
• IPSSEND GETCONFIG x | MORE

Click here for capturing configuration and event logs using DUMPLOG

Method 3

Run ServeRAID Manager from within the installed operating system, and right-click Local system in the left navigation panel and select save printable configuration and event logs from the menu. After the logs are saved, a dialog box will popup displaying the filenames that were saved. The first controller will save logs as Raid1.log. The second controller will save the logs as Raid2.log, etc. These logs are saved in a standard text format viewable with any text editor and can be found in the installation directory of ServeRAID Manager. The default directory in Windows is C:Program FilesRaidMan. Open these files and in the "Configuration summary" and the "Information for controller x" sections will include all the software versions related to this tip. The BIOS and driver versions must match. The firmware and bootblock version may not always match.

Method 4

IBM Support can also verify code levels using the eGatherer tool. Click here to download eGatherer. After running eGatherer, the output can be parsed and reviewed. The data in the ServeRAID, ServeRAID Adapter Configuration, and Device driver listing links should be reviewed. The driver is made up of three files (below) and the version number must match the version number of the BIOS flashed on the ServeRAID controller.

• PowerPC chip based ServeRAID controllers:
  (ServeRAID, ServeRAID II, ServeRAID 3L, ServeRAID 3H, ServeRAID 3HB, and ServeRAID 4H)
  • ipsraidn.sys
  • ipsperf.sys
  • twintail.sys
    
• Intel SCSI chip based ServeRAID controllers:
  (ServeRAID 4L, ServeRAID 4M, ServeRAID 4LX, ServeRAID 4MX)
  • nfrd960.sys
  • nfrdperf.sys
  • twintail.sys

Applicable countries and regions
Worldwide

Back to top

Document id: MIGR-42022
Last modified: 2006-08-31
Copyright © 2008 IBM Corporation

引自: