System x ® Education Servicing the ServeRAID M1000...

_________________________________________________________________________________________

System x ® Education

Servicing the ServeRAID M1000 and M5000 Series SAS/SATA II Controllers

October 2009 Study guide

XW5196

Release 1.10

This course is owned and published by the IBM System x/BladeCenter WW Service & Support

Education Team and created by Beth Walker and Henry Artner.

Servicing the ServeRAID M1000 and M5000 Series SAS/SATA II Controllers – Preface

October 2009 2 XW5196r110.pdf

International Business Machines Corporation, 2009 All rights reserved.

IBM System x Service and Support Education

IBM Systems, Department EYGA.

Building 203, Post Office Box 12195,

Research Triangle Park, North Carolina 27709-2195

IBM reserves the right to change specifications or other product information without notice.

This publication could include technical inaccuracies or typographical errors. References

herein to IBM products and services do not imply that IBM intends to make them available in

other countries. IBM provides this publication as is, without warranty of any kind —either

expressed or implied—including the implied warranties of merchantability or fitness for a

particular purpose. Some jurisdictions do not allow disclaimer of expressed or implied

warranties. Therefore, this disclaimer may not apply to you.

Data on competitive products is obtained from publicly obtained information and is subject

to change without notice. Please contact the manufacturer for the most recent information.

The following terms are trademarks or registered trademarks of IBM Corporation in the

United States, other countries or both:

Active Memory, Active PCI, AT, BladeCenter, the e-business logo, EasyServ, Enterprise X-

Architecture, EtherJet, HelpCenter, HelpWare, IBM RXE-100 Remote Expansion Enclosure,

IBM XA-32, IBM XA-64, IntelliStation, LANClient Control Manager, Memory ProteXion,

NetBAY3, Netfinity, Netfinity Manager, Predictive Failure Analysis, RXE Expansion Port,

SecureWay, ServeRAID, ServerProven, ServicePac, SMART Reaction, SMP Expansion

Module, SMP Expansion Port, UM Services, Universal Manageability, Update Connector,

Wake on LAN, XceL4 Server Accelerator Cache, XpandOnDemand scalability.

IBM Corporation Subsidiaries: Lotus, Lotus Notes, Domino, and SmartSuite are trademarks

of Lotus Development Corporation. Tivoli and Planet Tivoli are trademarks of Tivoli

Systems, Inc.

LLC, Adobe, and PostScript are trademarks of Adobe Systems, Inc. Intel Celeron,

LANDesk®, MMX, Pentium II, Pentium III, Pentium 4, SpeedStep, and Xeon are

trademarks or registered trademarks of Intel Corporation. Linux is a trademark of Linus

Torvalds. Microsoft Windows® and Windows NT® are trademarks or registered trademarks

of Microsoft Corporation. Other company, product, and service names may be trademarks or

service marks of others.

For more information,

visit:www.ibm.com/legal/copytrade/phtml



Preface Servicing the ServeRAID M5015 SAS/SATA II Controller This document may not be copied or sold, either in part or in whole, to non-IBM personnel.

Please write your name and address below to personalize your copy.

Issued to

Address

Current release date: October 2009

Current release level: 1.10

The information contained within this publication is current as of the date of the latest

revision and is subject to change at any time without notice.

Please forward all comments and suggestions regarding the course material format and

content to your local IBM System x Service and Support Education country coordinator or

contact.



Table of Contents

Preface...................................................................................................................................... 3

Table of Contents .................................................................................................................... 4

Prerequisites.................................................................................................................. 5

Objectives ..................................................................................................................... 5

Servicing the ServeRAID M1000 and M5000 Series SAS/SATA II Controllers ............. 6

Overview....................................................................................................................... 6

M Series Naming Convention....................................................................................... 7

Warranty ..................................................................................................................... 16

ServeRAID M 1015, M5014 and M5015 Controller Features and Limitations ......... 18

Controller Usage Limitations............................................................................................ 22

Controller Connectors....................................................................................................... 23

Configuration Scenarios.................................................................................................... 25

Installing the M5014 and M5015 Controllers................................................................... 27

Installing the ServeRAID M5000 Series Battery Assembly on the ServeRAID M5015

Controller .................................................................................................................... 30

Storage Management Tools .............................................................................................. 34

MegaRAID Storage Manager(MSM) ......................................................................... 35

WebBIOS Configuration Utility (CU)........................................................................ 36

Starting the WebBIOS CU.......................................................................................... 36

MegaRAID Command Line Tool (CLI) ..................................................................... 38

Troubleshooting and Problem Determination Tools......................................................... 39

Collecting Data ........................................................................................................... 39

Monitoring Controllers ............................................................................................... 42

Selecting Data Encryption Security Options Using WebBIOS .................................. 43

Installing Drivers .............................................................................................................. 46

Installing or Updating the MegaRAID Driver in an Existing Windows System........ 46

Installing the Windows System Driver in a New Windows System .......................... 46

Installing from a Driver Update Diskette.................................................................... 47

Rebuilding a Drive...................................................................................................... 47

Logs and Debugging Techniques...................................................................................... 49

OS Level Debug................................................................................................................ 49

Helpful Links .................................................................................................................... 51

Summary........................................................................................................................... 52



Prerequisites

You should be Server + certified or equivalent before taking this course.

You should also have completed the latest release of the self-paced learning courses:

a) XW2001 - Servicing IBM System x Servers - Part I

b) XW5173 - Unified Extensible Firmware Interface (UEFI) Technology Brief

c) XW2039 - Servicing the IBM® System x3400 M2 (M/T 7836,7837) and x3500 M2

d) XW2038 - Servicing the IBM® System x3550 M2 (M/T 7946) and x3650 M2

Objectives

Upon completion of this course, you will be able to:

1. Provide an overview of the IBM ServeRAID M1000 and M5000 series SAS/SATA II controllers

2. List the features of the ServeRAID M5014 and M5015 controllers

3. Describe how to install the ServeRAID M5014 and M5015 controllers and the

ServeRAID M5000 Series Battery Assembly

4. List the three storage management tools for the ServeRAID M series controllers

5. Perform problem determination and log-gathering activities for the ServeRAID

M Series

6. Install and update drivers for the ServeRAID M Series controllers

Servicing the ServeRAID M1000 and M5000 Series SAS/SATA II Controllers – Overview


Servicing the ServeRAID M1000 and M5000 Series SAS/SATA II Controllers

Overview

The ServeRAID M5014 and M5015 Serial Attached SCSI (SAS)/Serial ATA II (SATA II) controllers are high-performance intelligent PCI Express-to-SAS/SATA II adapters with RAID control capabilities. The ServeRAID M5014 and M5015 controllers provide reliability, high performance, and fault-tolerant disk subsystem management. They are an ideal RAID solution for the storage of workgroup, departmental, and enterprise systems. The controllers offer a cost-effective way to implement RAID in a server. The ServeRAID M1015 Serial Attached SCSI (SAS)/Serial ATA II (SATA II) controller is a low profile high performance value class solution for servers. The ServeRAID M5000 Series Battery Assembly is pre-installed on the ServeRAID M5015 controller to provide battery-protected backup of cached memory. The assembly provides protection of cached data, which allows system builders to protect cached data even during the most catastrophic system failures.

Each port on the ServeRAID M1000 and M5000 controller supports SAS devices and/or SATA II devices using the following:

• SAS Serial SCSI Protocol (SSP), which enables communication with other SAS devices, and SATA II, which enables communication with other SATA II devices

• Serial Management Protocol (SMP), which communicates topology management information directly with an attached SAS expander device

• Serial Tunneling Protocol (STP), which enables communication with a SATA II device through an attached expander

Notes:

• The ServeRAID M5000 Series Battery Assembly is not preinstalled on the ServeRAID M5014 controller but can be installed, if desired.

• SATA II is the only type of SATA supported by these RAID controllers.

• Carefully assess any decision to mix SAS drives and SATA drives within the same virtual drives. Although you can mix drives, IBM strongly discourages the practice. This recommendation applies to both HDDs and SSDs.



M Series Naming Convention

The M series is a new series of ServeRAID adapters with a new naming convention.

Table 1 – Example of Naming Convention for new ServeRAID adapters

Software Classification Generation Connector Feature/Function

M 5 0 1 5 M = LSI MR Stack

1-Value 5 – Enterprise Class

0 - 6 Gb/s 1 – Future use

0 – None 1 – Internal 2 – External 3 – Int and Ext

0-4 Entry Level 5 Base Adapter 6-9 Feature Upgrade

Figure 1 - ServeRAID M5015 Controller Top View




Note: The layout of the M5014 and the M5015 are identical except for the ServeRAID M5000 Series Battery Assembly, which is not shipped standard with the M5014.




The ServeRAID M1015 is a replacement adapter for the ServeRAID BR10i.



Figure 4 - ServeRAID M1015 Close up View



Table 2 - Technical Overview of ServeRAID Controller M1015



Table 3 - Technical Overview of ServeRAID Controllers M5014 and M5015



Supported Servers

The IBM ServeRAID M1015, M5014 and the M5015 adapter cards are both supported on the following IBM System x servers:

• X3400M2

• X3500M2

• X3550M2

• X3650M2

• X3200M3 ServeRAID M1015 only

• X3250M3 ServeRAID M1015 only

Supported Operating Systems

The ServeRAID M1000 and ServeRAID M5000 adapter cards support the following operating systems:

• Microsoft Windows Server 2003, Web Edition • Microsoft Windows Server 2003/2003 R2 • Microsoft Windows Server 2008/2008 R2 • Microsoft Windows Small Business Server 2003/2003 R2 • Red Hat Enterprise Linux 4 • Red Hat Enterprise Linux 5 • SUSE LINUX Enterprise Server 10 • SUSE LINUX Enterprise Server 11

For detailed information on support for specific OS versions, please refer to http://www.redbooks.ibm.com/abstracts/tips0738.html See IBM ServerProven for the latest information about the specific versions and service packs supported: http://ibm.com/servers/eserver/serverproven/compat/us/. Click System x servers, and then click Disk controllers to see the support matrix. Click the check mark that is associated with the System x server in question to see the details of operating system support.



Operating environment The ServeRAID M5015 and ServeRAID M5014 adapter cards are supported in the following environment: Temperature: At 0-1000 m (0-3000 ft): 10 to 35 °C (50 to 95 °F) At 1000-2100m (3000-7000 ft): 10 to 32 °C (50 to 90 °F) Relative humidity: 20% to 80% (non-condensing)



ServeRAID M5000 Series Battery Assembly Specifications

• Battery type: LiON, Li-Poly cell

• Battery operating ambient temperature: 10–40° C

• Humidity (storage and operating): 20% to 80% non-condensing

• Battery storage temperature: Depends on storage time, as follows:

• < 30 days: 0–50° C

• 30–90 days: 0–40° C

• 90 days: 0–30° C

Ship Group:

The ServeRAID M5015 controller ships with the following:

• One ServeRAID M5015 adapter card with full-height bracket • One replaceable low-profile (2U) bracket • One attached ServeRAID M5000 battery (plus battery kit) • Documentation CD • The IBM Important Notices Document

The ServeRAID M5014 controller ships with the following:

• One ServeRAID M 5014 adapter card with full-height bracket • One replaceable low-profile (2U) bracket • The ServeRAID M v1.10 Utility and Documentation CD • The IBM Important Notices Document

The ServeRAID M5000 Series Battery Kit contains the following:

• SR M5000 Battery • Remote Battery Cable Kit • Battery Flyer • Quick Install Guide • Important Notices Flyer



Warranty

This product has a one-year limited warranty. When installed in a System x server, these cards assume your system’s base warranty and any IBM ServicePac upgrade. Batteries are consumables and are therefore not covered under warranty.

This product is a Customer Replaceable Unit (“CRU”). IBM provides replacement CRUs for the customer to install. CRU information and replacement instructions are shipped with the customer's Machine and are available from IBM at any time on the customer's request. CRUs are designated as being either Tier 1 or a Tier 2 CRU. Installation of Tier 1 CRUs is the customer's responsibility. If IBM installs a Tier 1 CRU at the customer's request, the customer is charged for the installation. The customer may install a Tier 2 CRU themselves or request IBM to install it, at no additional charge, under the type of warranty service designated for the customer's Machine. IBM specifies in the materials shipped with a replacement CRU whether a defective CRU must be returned to IBM. When return is required, 1) return instructions and a container are shipped with the replacement CRU, and 2) the customer may be charged for the replacement CRU if IBM does not receive the defective CRU within 15 days of the customer's receipt of the replacement.



Part Numbers

*Part numbers are subject to change without notice. Please consult the IBM Support site for the latest part numbers.

Table 4 - Ordering part numbers

Part Name Part Number IBM ServeRAID M5015 SAS/SATA II Controller 46M0829 IBM ServeRAID M5014 SAS/SATA II Controller 46M0916 IBM ServeRAID M5000 Series Battery Kit 46M0917 IBM ServeRAID M1015 SAS/SATA II Controller 46M0831 IBM ServeRAID M1015 Upgrade Key (Raid 5) 46M0832

Note: Changes are made periodically to the IBM Web site. The actual procedure might vary slightly from what is described in this document.

See IBM ServerProven for the latest information about the specific versions and service packs supported: http://ibm.com/servers/eserver/serverproven/compat/us/. Click System x servers, and then click Disk controllers to see the support matrix. Click the check mark that is associated with the System x server in question to see the details of operating system support.

Servicing the ServeRAID M5015 SAS/SATA II Controllers – Features and Limitations


ServeRAID M 1015, M5014 and M5015 Controller Features and Limitations

• Two (2) x4 internal SAS / SATA ports

• X8 PCI Express Gen 2 host interface

• M5000: RAID Levels 0, 1, 5, 10, 50 (6, 60 Optional)

• M1000: RAID Levels 0, 1, 10, (50 Optional with Upgrade Key)

• Memory

o M5014: 800MHz 40-bit ECC DDR2 SDRAM Memory (256 MB)

o M5015: 800MHz 72-bit ECC DDR2 SDRAM Memory (512 MB)

o M1015: No memory

• M5000: One (1) LSI SAS2108 6Gb/s RAID on Chip processor that controls eight internal SAS/SATA ports through two x4 SAS internal connectors M5000 only

• M1000: One (1) LSI SAS2008 6 Gb/s RAID on Chip processor that controls eight internal SAS/SATA ports through two x4 SAS internal connectors

• Low-profile PCIe Half Length Form Factor

• Encryption Services

o Instant Secure Erase

o Local Key Management

• MegaRAID Management Suite

o MegaRAID Storage Manager

o MegaCLI (command-line interface)

o WebBIOS

• ServeRAID M5000 Series Battery Assembly. The battery assembly, which is preinstalled, provides protection of cached data, which allows system builders to protect cached data even during the most catastrophic system failures. Standard on the M5015, optional part for the M5014

• Drive migration

• Drive roaming

• Media scan

• No reboot necessary after expansion



The M5014 and the M5015 share the same features and functions with two important differences:

1) The M5015 has double the SDRAM memory capacity.

2) The battery comes standard with the M5015 but is optional with the M5014. SAS Features

• Provides eight fully independent PHYs

• Supports 6.0 Gb/s SAS data transfers per PHY

• Supports SSP to enable communication with other SAS devices

• Supports SMP to communicate topology management information

• Provides a serial, point-to-point, enterprise-level storage interface

• Simplifies cabling between devices

• Provides a scalable interface that supports up to 248 devices through the use of expanders

• Supports wide ports consisting of 2, 3, or 4 PHYs within a single quad port

• Supports narrow ports consisting of a single PHY

• Transfers data using SCSI information units

SATA II Features

• Supports SATA II data transfers of 3.0 Gbs/s

• Supports STP data transfers of 3.0 Gbs/s

• Provides a serial, point-to-point storage interface

• Simplifies cabling between devices

• Eliminates the master-slave construction used in parallel ATA

• Allows addressing of multiple SATA II targets through an expander

• Allows multiple initiators to address a single target (in a fail-over configuration) through an expander

6 Gbps SAS 2.0 technology has been introduced to address data off-load bottlenecks in the direct-access storage environment. This new throughput doubles the transfer rate of the previous generation. SAS 2.0 is designed for backward compatibility with 3 Gbps SAS as well as with 3 Gbps SATA hard drives. Regardless of the drive speed, 6 Gbps ServeRAID adapters will deliver significant performance improvements in both read and write applications as compared to their 3 Gbps predecessors.



Solid State Drive Features

The firmware supports Solid State Drives attached to ServeRAID-MR SAS controllers. The features and operations for SSDs are the same as for hard disk drives (HDDs), and these drives are expected to behave like SATA HDDs or SAS HDDs. The major advantages of SSDs include:

• High random read speed (because there is no read-write head to move)

• High performance-to-power ratio, as these drives have very low power consumption compared to HDDs

• Low latency

• High mechanical reliability

• Lower weight and size (for low-capacity SSD drives)

The WebBIOS Configuration Utility and the MegaRAID Storage Manager utility display the SSDs by the type, either SAS or SATA. For example, a SATA SSD drive displays as “SSD (SATA)”. HDDs are identified simply as “SAS” or “SATA”. Note: ServeRAID-MR implements support for only those SATA SSD drives which support ATA-8 ACS compliance. Virtual drives can consist of both SSD devices and HDDs. For a virtual drive that consists of SSDs only, both SAS SSD drives and SATA SSD drives are allowed in that virtual drive. For virtual drives that have both SSDs and HDDs, SAS and SATA HDD drives may be combined with SAS and SATA SSD devices in various combinations. Note: Support for SATA SDD drives applies only to those drives that support ATA-8 ACS compliance.



MegaRAID Features

• Usability

• Extensions to RAID 1

• Revertible Hot Spare

• Unified Extensible Firmware Interface (UEFI ) 2.0 Support

• VMware ESXi Support

• Data Protection & Availability

• Intelligent Battery Backup Unit

• Single Controller Multi-pathing

• SSD Guard

• Performance

• Load Balancing

• SSD Support

Environmentally Friendly

• Dimmer Switch

A Note About UEFI 2.0 Support:

Unified Extensible Firmware Interface (UEFI) 2.0 was developed to do the following:

• Define a clean interface between operating systems and the hardware platform at boot time

• Support an architecture-independent mechanism for initializing add-in cards.

UEFI 2.0 provides ServeRAID M1000 and M5000 customers with expanded platform support. The UEFI 2.0 driver, a boot service device driver, handles block IO requests and SCSI pass-through commands (SPT), and offers the ability to launch pre-boot ServeRAID-MR management applications through a driver configuration protocol (DCP). The UEFI driver also supports driver diagnostic protocol, which allows administrators to access pre-boot diagnostics.



Controller Usage Limitations

The ServeRAID M5015 controller has the following limitations:

• You can connect only one device per SAS PHY unless you use an expander.

• You can use a maximum cable length of six feet (using shorter cables is preferred).

• Cables have to meet the SAS specification.

• The controllers support mixing of drive types on the same backplane but not in the same array.

• Storage Manager will span available hard disks regardless of technology, as long as the technologies and the device drivers support the formatting expected on the virtual drive.

• Refer to the User’s Guide for the ServeRAID M5015 SAS/SATA II Controller

for information about the power requirements and the minimum and the maximum temperature ranges.

Servicing the IBM ServeRAID M5015 SAS/SATA II Controllers –Controller Connectors


Controller Connectors

Figure 1- M5014 and M5015 Controller Jumper and Connector Layout Diagram

Note: JT2 and JT4 are behind the battery assembly when it is installed, but they are still accessible.

Refer to Table 1 on the next page for an explanation of Figure 1 above. Refer to Figure 1 and its corresponding explanation when installing the controller in a system.

Servicing the IBM ServeRAID M5015 SAS/SATA II Controllers –Controller Connectors


Table 1 – Explanation of Controller Connectors

Jumper/Connector Type Description

JT2 (2-pin connector)

SAS Activity LED header Connects to an LED that indicates drive activity.


Battery Backup connector Connects the Battery assembly Unit directly to the ServeRAID M5015 controller.


Global Drive Fault LED header

Connects to an LED that indicates whether a drive is in a fault condition.

JT6 x4 SAS Ports 3–0 Mini SAS 4i connector

Connects the cables from the controller to SAS drives or SATA II drives, or a SAS expander.

JT7 x4 SAS Ports 7–4 Mini SAS 4i

connector

Connects the cables from the controller to SAS drives or SATA II drives, or a SAS expander.

JT8 Modular RAID Key header Reserved for IBM use


Set Factory Defaults connector

Returns the board settings to the defaults set in the factory.

JT10 Test header Reserved for IBM use

JT11(3-pin shielded header)

IPMI-style SMBus (System Management)/I2C header

Provides enclosure management support.

JT12 Individual Drive Fault LED header

for Eight PHYs (0-7)

Indicates drive faults. There is one LED per port. When lit, each LED indicates the corresponding drive has failed or is in the Unconfigured-Bad state.

The LEDs function in a direct attach configuration (there are no SAS expanders). Direct attach is defined as a maximum of one drive connected directly to each port. This header is used for controllers with internal SAS ports.

JT13 Receiver/ Transmitter debugging

Reserved for IBM use

Servicing the IBM ServeRAID M5015 SAS/SATA II Controllers –Configuration Scenarios


Configuration Scenarios

There are three main configuration scenarios for the SAS RAID controllers:

1. Low-end, internal SATA II configurations: In this configuration, use the RAID controller as a high-end SATA II compatible controller that connects up to eight disks either directly or through a port expander. This configuration is mostly for low-end or entry servers. Enclosure management is provided through out-of-band I2C bus. Side bands of both types of internal SAS connectors support the SFF-8485 (SGPIO) interface.

2. Midrange internal SAS configurations: This configuration is similar to the internal SATA II configurations, but with high-end disks. This configuration is more suitable for low-range to midrange servers.

3. High-end external SAS/SATA II configurations: This configuration is for both internal connectivity and external connectivity, using SATA II drives, SAS drives, or both. External enclosure management is supported through in-band, SCSI-enclosed storage. The configuration must support STP and SMP.

Figure 2 shows a direct-connect configuration. The Inter-IC (I2C) interface communicates with peripherals. The external memory bus provides a 32-bit memory bus, parity checking, and chip select signals for pipelined synchronous burst static random access memory (PSBRAM), nonvolatile static random access memory (NVSRAM), and Flash ROM. Figure 2 - SAS Direct-Connect Application Diagram

Servicing the IBM ServeRAID M5015 SAS/SATA II Controllers –Configuration Scenarios


Figure 3 shows an example of a SAS RAID controller configured with an LSISASx12 expander that is connected to SAS disks, SATA II disks, or both. Figure 3 - Example of a SAS RAID Controller Configured with an LSISASx12 Expander

Servicing the IBM ServeRAID M5015 SAS/SATA II Controllers –Installing the M5014 and M5015 Controllers


Installing the M5014 and M5015 Controllers Important Notes: 1) The installation instructions are the same for the M5014 and M5015 types. 2) Read the corresponding Quick Install Guide for the controller before you begin installing any controller.

Note: Record your controller serial number in a safe location for future reference.

The ServeRAID M5000 Series Battery Assembly ships with the controller. Mount the battery assembly directly to the controller using a daughtercard. For more information about the M5015 controller and the battery assembly, refer to the ServeRAID M5015 SAS/SATA Controller User’s Guide on the ServeRAID-M Support CD. Installation Requirements:

• A ServeRAID M5015 SAS/SATA II controller

• A host system with an available PCI Express expansion slot

• The ServeRAID-MR Support CD, containing the drivers and the documentation

• The necessary internal cables

• SAS physical disks or SATA II physical disks (Mechanical or Solid State Devices, SSDs)

To install the controller, perform the following steps:

1) Ensure that all installation requirements listed above are met.

2) Remove the controller from the antistatic bag, making sure you follow precautions to avoid static buildup or damage.

3) Review the controller connector locations as described in the Quick Install

Guide that corresponds with the controller type you are installing.

4) Prepare your computer by unplugging the power cords from the power supplies, disconnecting the computer from the network, and removing the computer cover. Be sure the computer is disconnected from all networks at this time.



5) Install the controller on the motherboard by inserting the controller in a PCI Express slot on the motherboard, as shown in Figure 1. Press down gently but firmly to seat the card correctly in the slot.

6) Secure the controller to the computer chassis with the bracket screw as shown in Figure 1.

Figure 1 – Installing the Controller in a Motherboard

Note: This is a PCI Express x8 card and it can operate in x8 or x16 slots. Some PCI-E slots support only PCI-E graphics cards; if a RAID controller is installed, it will not function.



7. After the controller is installed on the motherboard, configure and install the SAS Devices, SATA II Devices or both.

8. Connect the cables between the controller and the SAS devices, SATA II devices, or both. Refer to the external device documentation to view connector locations for the external devices.

9. Install the computer cover and reconnect the power cords. Turn on the power to the computer, making sure that the power is turned on to the SAS devices and the SATA II devices before or at the same time as the host computer. If the power is turned on to the computer before it is turned on to the devices, the computer might not recognize the devices.

10. During boot, a BIOS message similar to the following displays:

Caution: The battery must charge for at least six hours under normal operating conditions. To protect your data, the firmware changes the Write Policy to write-through until the battery unit is sufficiently charged. When the battery unit is charged, the controller firmware changes the Write Policy to write-back to take advantage of the performance benefits of data caching.

11. Run the WebBIOS Configuration Utility to configure the physical arrays and the logical drives. When the message Press <Ctrl><H> for WebBIOS displays on the screen, press CTRL+H immediately to run the utility.

12. Install the Operating System driver. The ServeRAID-M Support CD includes drivers for the supported operating systems. View the supported operating systems and download the latest drivers for the controller at http://www.ibm.com/support/. For updates, click Downloads and drivers. Access the download center and follow the steps to download the driver.

13. Refer to the ServeRAID-M Device Driver Installation Guide on the CD for details on installing the driver. Be sure to use the latest Service Packs provided by the operating system manufacturer and review the readme file that accompanies the driver.



Installing the ServeRAID M5000 Series Battery Assembly on the ServeRAID M5015 Controller

The battery assembly mounts directly to the ServeRAID M5015 controller using a small board-to-board connector (daughtercard).

Figure 2 displays the bottom view and the top view of the card. (The “top” side is the side that is visible after the battery assembly is installed on the RAID controller.) Note that this unit combines a battery pack with a daughtercard.

Figure 2 –Views of the ServeRAID M5000 Series Battery Assembly

1 - J4 battery pack harness connector

2 - J5 board-to-board connector

3 - J2 connector

4 - Battery pack harness



Perform the following steps to mount the battery assembly directly to the ServeRAID M5015 controller using the daughtercard. (All components are installed on the bottom of the card. The battery is installed on the top. The maximum height of components installed on the battery assembly is 0.125”.)

1. Ground yourself, and remove the battery assembly daughtercard from the package.

2. Insert the battery pack harness into the 5-pin J4 connector on the bottom of the battery assembly.

3. Hold the battery assembly daughtercard so that the battery side is up and the J5 connector lines up with the JT3 battery assembly connector on the controller, as shown in Figure 3.

Figure 3 – Lining up the Connectors

4. Carefully press the battery assembly onto the controller, so that the two connectors are firmly joined.

5. Secure the battery assembly to the controller with the screws and the standoffs in the three screw holes. The standoffs are threaded at both ends and a screw goes into each end.

6. Use the Phillips-head screws that are provided to secure the battery assembly to the controller.



7. Install the controller in the computer in the PCI Express slot, as shown in Figure 1 above.

8. Press down gently, but firmly, to make sure that the controller is properly seated in the slot. The bottom edge of the controller must be flush with the slot.

Caution: Never apply pressure to the battery assembly when you insert the controller. Instead, press down only on the top edge of the controller, as shown in Figure 1 above. Connecting the ServeRAID M5015 SAS/SATA II Controller to Physical Drives This subsection provides step-by-step instructions for connecting the ServeRAID M5014 and M5015 controllers to the SAS physical drives and the SATA II physical drives. Figure 4 demonstrates how to connect the internal SAS cable from the controller to the drives. Follow the steps below to connect the ServeRAID M5015 controller with internal connectors to a physical drive:

1. Plug the connector on the internal cable into the internal connector on the controller.

2. Plug the connector on the other end of the internal cable into the connector on the SAS physical drive or the SATA II physical drive.

3. If you have another physical drive, connect it to another plug on the internal cable.

4. You can connect other devices if the cable has more connectors.



Figure 4 – Connecting the internal SAS cable to the drives

Servicing the IBM ServeRAID M5015 SAS/SATA II Controllers –Storage Management Tools


Storage Management Tools

The user has the choice of three tools to manage storage tasks and monitor activities for the M5014 and M5015 controllers:

1) MegaRAID Storage Manager - MSM

A Powerful management GUI used to complete many advanced storage management operations such as RAID Level Migration, adding HotSpares, etc.

2) WebBIOS Configuration Utility (CU)

A CU used to create and manage RAID configurations on ServeRAID-MR controllers. Unlike the MegaRAID Storage Manager software, the WebBIOS CU resides in the SAS controller BIOS and operates independently of the operating system.

3) Command Line Tool - CLI

A CLI Application for SAS, used to configure, monitor, and maintain Sanford SAS RAID storage adapters and the devices connected to them.

This section describes each of the storage management tools in more detail.



MegaRAID Storage Manager(MSM)

Features MegaRAID Storage Manager (MSM) is a GUI-based application that allows simplified management of numerous storage configuration and virtual disk tasks, including:

• Creating a New Storage Configuration

• Adding Hotspare Disks

• Changing Adjustable Task Rates

• Changing Virtual Disk Properties

• Changing a Virtual Disk Configuration

• Deleting a Virtual Disk

• Saving a Storage Configuration to Disk

• Clearing a Storage Configuration from a Controller

• Adding a Saved Storage Configuration

Hardware and Operating System Requirements

MSM software has the following hardware requirements:

• PC-compatible computer with an IA-32 (32-bit) Intel Architecture processor or an EM64T (64-bit) processor and at least 128 Mbytes of system memory (256 Mbytes recommended)

• Drive with at least 50 Mbytes available free space

MSM software is supported on the following operating systems:

• Microsoft® Windows® 2000, Microsoft Windows Server 2003, and Microsoft Windows Server 2008

• Red Hat® Enterprise Linux™ version 4.0 and version 5.0

• SUSE™ SLES version 9 and version 10, with latest updates and service packs

• Novell® NetWare® 6.5

• SCO™ OpenServer® 6.0.0

• SCO UnixWare™ 7.1.4

• VMWare® ESX 3.0 and ESX 3.5



WebBIOS Configuration Utility (CU)

Features The WebBIOS CU is a web-based utility for configuring and managing RAID volumes. It operates independently of the operating system because the utility resides in the MegaRAID BIOS. It allows the user to perform the following tasks:

• Create physical arrays and logical drives for storage configurations

• Delete virtual disks

• Migrate a storage configuration to a different RAID level

• Detect configuration mismatches

• Import a foreign configuration

• Display adapter, virtual disk, physical drive, and battery backup unit (BBU) properties

• Scan devices connected to the controller

• Initialize virtual disks

• Check configurations for data consistency

• Provides a configuration wizard to guide users through the configuration of logical drives and physical arrays

Starting the WebBIOS CU

Follow these steps to start the WebBIOS CU and access the main screen.

1. When the host computer is booting, hold down the <Ctrl> key and press the <H> key when the following text appears on the screen:

Copyright© LSI Corporation

Press <Ctrl><H> for WebBIOS

The Controller Selection screen appears.

2. If the system has multiple SAS controllers, select a controller.

3. Click Start to continue. The main WebBIOS CU screen appears as shown in Figure 1 on the next page.



Figure 1 – the WebBIOS CU Main Screen

In the right frame, the screen shows the virtual drives configured on the controller, and the drives that are connected to the controller. In addition, the screen indentifies drives that are foreign or missing.

Note: In the list of virtual drives, the drive nodes are sorted based on the order in which you added the drives to the drive group, rather than the physical slot order that displays in the physical trees.

To toggle between the physical view and logical view of the storage devices connected to the controller, click Physical View or Logical View in the menu on the left side of the screen.



MegaRAID Command Line Tool (CLI)

Features The MegaRAID CLI is a simple but useful tool for SAS-RAID related activities. Use the CLI to:.

• Configure MegaRAID SAS RAID storage adapters and attached devices

• Display information about logical drives and physical drives for the adapter and other storage components

• Display ongoing progress for operations on physical drives for the adapter and other storage components

• Change the firmware on the adapters

• Monitor the RAID storage systems

• Create and use scripts with the scriptable CLI tool

• Configure physical disk drives into groups and virtual disks on the controller

• Display configuration information for the controller, physical disk drives, and virtual disks

• Change virtual disk properties on the controller

• Change physical disk drive properties on the controller

• Display controller properties

• Load configuration to the controller from a file

• Save the controller configuration to a file

• Scan, preview, and import foreign configurations

• Set predefined environment variables, such as the number of controllers and virtual disks

• Display firmware event logs

• Display help for how to use the command line options

• Display battery unit properties

• Display enclosure properties

Servicing the IBM ServeRAID M5015 SAS/SATA II Controllers –Troubleshooting and Problem Determination


Troubleshooting and Problem Determination Tools

Collecting Data

Data collection is the primary step in determining the correct service action to perform in order to resolve a client’s issue. Whether the data collected is verbal from the client (“…the front panel LED is blinking…”) or a diagnostic data file from a specialized application, all information collected is useful toward identifying one of the four available Service actions that you can perform. The four actions are:

• Update (firmware, microcode, device drivers, and software)

• Reconfigure (parameter values, cabling, component reseats, system reboots)

• Replace (hardware)

• Escalate to the next service level

Event Monitoring Using MegaRAID Storage Manager

Use the MegaRAID Storage Manager (MSM) software to monitor the status of drives, virtual drives, and other storage devices. MegaRAID Storage Manager software displays the status of controllers, virtual drives, and drives on the workstation or server that you are monitoring. System errors and events are recorded in an event log file and are displayed on the screen. Special device icons appear on the screen to notify you of drive failures and other events that require immediate attention.

Note: You must have administrative privileges in order to use MegaRAID Storage Manager software in either full-access or view-only mode.



The window is composed of three main parts as shown in Figure 1 below:

1. Drive list with physical or logical views 2. Controller Information Window 3. Event Log Messages

You can use MegaRAID Storage Manager to monitor events. There are settings for the delivery of alerts, the severity level of events, exceptions, and email settings. MSM must be set up in Server mode in order to configure alerts and email settings. Figure 1 – MegaRAID Storage Manager Window Overview



Event log messages display in the lower section of the main MSM window as shown in Figure 2. Each message that appears in the event log has a severity level that indicates the importance of the event, as shown in Table 1, a date and timestamp, and a brief description. You can click on an event to display the same information in a window. (For a list of all events, refer to the User’s Guide – ServeRAID-MR

Software, Appendix A, “Events and Messages.”)

Figure 2 – Event Log Messages Section

Table 1 - Event Severity Levels Security Level Meaning Information Informational message. No user action is necessary.

Critical A component has failed, but the system has not lost data.

Warning Some component might be close to a failure point. Fatal A component has failed, and data loss has occurred or will

occur. The Log menu option (as shown in Figure 3) has four options:

1. Save Log: Saves the current log to a .log file. 2. Save Log Text: Saves the current log in .txt format. 3. View Saved Log: Clears the current log information and provides the option to

save the log first. 4. Clear Log: Loads a local .log file.

Figure 3 – Log Menu Option



Monitoring Controllers

The left panel of the MegaRAID Storage Manager window displays either the Physical view or the Logical view of the system and the devices in it, depending on which tab is selected.

The Physical view shows the hierarchy of physical devices in the system. At the top of the hierarchy is the system itself. One or more controllers are installed in the system. The controller label identifies the MegaRAID controller, such as the MegaRAID SAS 8708ELP controller, so that you can easily differentiate between multiple controllers. Each controller has one or more ports. Drives and other devices are attached to the ports.

The Logical view shows the hierarchy of controllers, virtual drives, and drive groups that are defined on the system. (Drives also appear in the Logical view, so you can see which drives are used by each virtual drive.)

When MegaRAID Storage Manager software is running, you can see the status of all controllers in the left panel of the MegaRAID Storage Manager window.

If the controller is operating normally, the controller icon looks like this: .

If the controller has failed, a small red circle appears to the right of the icon.

To display complete controller information, click a controller icon in the left panel of the MegaRAID Storage Manager window, and click the Properties tab in the right panel. The Controller Information window displays as shown in Figure 1 above.



Selecting Data Encryption Security Options Using WebBIOS

The Data Encryption (DE) feature in WebBIOS provides the ability to encrypt data and controller-based key management for the data security solution. This solution provides protection to the data in the event of theft or loss of physical drives. This section describes how to enable, change, or disable the drive security settings, and how to import a foreign configuration. Enabling the Security Key Identifier, Security Key, and Pass Phrase Perform the following steps to enable the encryption settings for the security key identifier, security key, and pass phrase.

1. From the main WebBIOS screen, click Encryption Settings. The Encryption Settings screen appears, as shown in Figure 4.

Figure 4 - Encryption Settings Screen

2. To enable the drive security settings, select the Enable drive security radio button, then click Accept.

The Enable Drive Security – Introduction screen appears. This screen lists the actions you can perform: editing the security key identifier, editing the security key, and adding or changing the pass phrase (optional).

3. Click Next.

The screen used to create a security key identifier appears. The controller provides a default security key.



4. Accept the default security key ID or enter a new security key ID.

5. Click Next.

6. The Enable Drive Security – Enter Security Key screen appears. Enter a new drive security key or click Suggest to fill the new security key. Enter the new drive security key again to confirm.

The security key is case-sensitive. It must be between eight and thirty-two characters and contain at least one number, one lowercase letter, one uppercase letter, and one non-alphanumeric character (e.g. < > @ +). The space character is not permitted.

7. Click Next.

The Enable Drive Security – Enter Pass Phrase screen appears. You have the option to provide a pass phrase for additional security.

8. If you want to use a pass phrase, click the checkbox Use a pass phrase in addition to the security key.

9. Enter a new pass phrase and then enter the new pass phrase again to confirm. The same password rules listed above apply on this screen. Non-US keyboard users must be careful not to enter DBCS characters in the pass phrase field or security key field. Firmware works only with the ASCII character set.

10. Click Accept.

The Confirm Enable Drive Security screen appears.

11. Click Yes on the Confirm Enable Drive Security screen to confirm that you want to enable the drive security settings.

WebBIOS enables the security key ID, security key, and pass phrase (if applicable) that you entered and returns you to the main menu.

Caution: If you forget the security key, you will lose access to your data. Be sure to record your security key information. You might need to enter the security key to perform certain operations.



Upgrading Firmware using MSM and the MegaCLI Utility

To upgrade the controller firmware using MSM, follow these steps:

1) In the left panel of the MegaRAID Storage Manager window, click the icon of the controller you need to upgrade.

2) In the right panel, click the Operations tab, and select Flash Firmware.

3) Click Go.

4) Browse for the .rom update file, and click OK. MegaRAID Storage Manager software displays the version of the existing firmware and the version of the new firmware.

5) When you are prompted to indicate if you want upgrade the firmware, click Yes. The controller is updated with the new firmware code contained in the .rom file.

To upgrade the controller firmware using MegaCLI, use this syntax:

• Megacli –adpfwflash –f sasfw.rom –a0



Installing Drivers

Installing or Updating the MegaRAID Driver in an Existing Windows System

Perform the following steps to install or update the MegaRAID device driver in an existing Windows system:

1. Boot the Windows operating system. The Found New Hardware Wizard starts.

2. Click the Next button and insert the driver diskette in the A drive

3. Click the Search for a Suitable Driver… button, and click Next.

4. Click the Next button. In some cases, a message displays saying that this driver is not digitally signed. This message informs you that a nonsigned driver is being installed. If this message displays, click Continue Anyway.

5. Select Floppy only, and then click the Next button in the Driver Files Search Results windows.

6. Click the Finish button to complete the driver installation, then repeat this process for all adapters on your system.

Installing the Windows System Driver in a New Windows System

Perform the following steps to install the MegaRAID device drive in new Windows system. Windows automatically adds the driver to the registry and copies the driver to the appropriate directory.

1. Start the Windows installation by booting from the Windows CD-ROM. The system BIOS must support booting from a CD-ROM. BIOS settings might require changes to allow CD-ROM booting. See you system documentation.

2. Press F6 when the following displays at the bottom of the screen: ‘Press F6 if you need…’

Note: The user MUST press F6 for the system to recognize the new driver.

3. Select ‘S’ to specify an additional device when the screen displays: ‘Setup could not determine the type of one or more mass storage devices…’ The system prompts for the manufacturer supplied hardware support disk.

Note: If the screen does not display this message after you press F6, then the setup program, did not recognize the F6 command, Reboot the system and return to step 2.

4. Insert the driver diskette containing the Windows device driver and press ENTER.



5. Select the Windows adapter from the menu by using the arrow key to highlight it and pressing ENTER.

6. Press ENTER again to proceed

7. Return to the Windows Setup screen. Windows displays a ‘Welcome to Setup’ window.

8. Press ENTER to continue.

9. Follow the Microsoft Windows Installation procedure by typing ‘C’ to continue.

10. Repeat this process for the adapters on your system.

Installing from a Driver Update Diskette

To install the MegaRAID device driver in a new Red Hat Linux 3.0, 4.0, or 5.0 system from a driver update diskette, create the diskette using the Linux driver image on the Red Hat Linux Installation CD. Perform the following steps:

1. Boot to CD-ROM with Disk 1.

2. Type: linux dd

3. Insert the driver diskette. The utility locates and loads the driver for your device.

4. Press ALT + CTRL + F4 to verify the driver is loaded

5. Follow the Red Hat Linux installation procedure to complete the installation.

Rebuilding a Drive

If a single drive in a RAID 1, RAID 5, RAID 10, or RAID 50 virtual drive fails, the system is protected from data loss. A failed drive must be replaced, and the data on the drive must be rebuilt on a new drive to restore the system to fault tolerance. (You can choose to rebuild the data on the failed drive if the drive is still operational.) If hot spare drives are available, the failed drive is rebuilt automatically without any user intervention.

If a drive has failed, a red circle appears to the right of the drive icon. A small yellow circle appears to the right of the icon of the virtual drive that uses this drive. This indicates that the virtual drive is in a degraded state; the data is still safe, but data could be lost if another drive fails.



Follow these steps to rebuild a drive:

1. Right-click the icon of the failed drive, and select Rebuild.

2. Click Yes when the warning message appears. If the drive is still good, a rebuild will start.

You can monitor the progress of the rebuild in the Group Show Progress window by selecting Group Operations->Show Progress.

If the drive cannot be rebuilt, an error message appears. Continue with the next step.

3. Shut down the system, disconnect the power cord, and open the computer case.

4. Replace the failed drive with a new drive of equal capacity.

5. Close the computer case, reconnect the power cord, and restart the computer.

6. Restart the MegaRAID Storage Manager software.

When the new drive spins up, the drive icon changes back to normal status, and the rebuild process begins automatically.

Making a Drive Offline or Missing If a drive is currently part of a redundant configuration and you want to use it in another configuration, you can use MegaRAID Storage Manager commands to remove the drive from the first configuration. When you do this, all data on that drive is lost.

1. To remove the drive from the configuration without harming the data on the virtual drive, follow these steps:

2. In the left panel of the MegaRAID Storage Manager window, right-click the icon of a drive in a redundant virtual drive.

3. Select Make drive offline from the pop-up menu. The drive status changes to Offline.

4. Right-click the drive icon again, and select Mark physical disk as missing.

5. Select File->Rescan. The drive status changes to Unconfigured Good. At this point, the data on this drive is no longer valid.

6. If necessary, create a hot spare drive for the virtual drive from which you have removed the drive.

Servicing the IBM ServeRAID M5015 SAS/SATA II Controllers –Problem Determination - Logs


Logs and Debugging Techniques

There are several ways of gathering information for problem determination purposes. When directed, pull logs and use all normal troubleshooting procedures as outlined in the PDSG for the system type you are working with.

OS Level Debug

• Information available at the OS layer o Varies greatly from system to system o Debuggers available for different OS o Crash analysis tools available for tier 1 OS

• BSODs and other crash debugs are difficult to infer information from. While useful, they may not provide information directly related or easily tied to the original failure.

• Screen shots or full recording of kernel debug output from various OS failures should be recorded if possible.

• BSODs and other crashes may occur hours after the original failure, depending on symptoms. (for example, “KERNEL_DATA_IN_PAGE_ERROR” BSOD will not occur until the OS tries to do a paging operation. Depending upon system configuration this could be up to several hours after the initial failure).

• Kernel dumps are often useful for post failure analysis (this is extremely helpful in some failures, but with the boot controller failures it is not always available).

System Event Logs

• Windows, Netware, and Linux have event logs: o Windows event logs are viewed via the event viewer under

administrator tools on most flavors of windows o Linux logs are typically in /var/log/messages

• RAID software does not typically log events in the system event logs

• System events may also be useful in correlating times of OS failures with other logs and debugs to show when the OS saw events occurring as well as identifying unique footprints for failures

• Additional debug levels are sometimes available under some OS layers

• Linux can have the amount of debug increased via the logging daemons

• Windows 3rd party utilities can output additional information under some conditions (Storlib debug builds), and are very useful if combined with debug drivers and libraries (dlls)

Servicing the IBM ServeRAID M5015 SAS/SATA II Controllers –Problem Determination - Logs


Application Event Logs

• Many applications have independent debug logs

• Test logs are often very useful

• Applications logs like flash utilities, diagnostics, etc may provide very useful information

HW Debugging

• Card Post

• PMM/EDBA Memory

• Move slots FW logs

• LSI RAID cards come with an auditable buzzer for event notification

• Buzzer tone denotes event of notification

• RAID set has gone to a degraded state FW Debugging

• Captured using either HW or FW interface

• Provide “bird’s view” of FW path to developers

• Proprietary

• Logs may change in the future Firmware Interface

• Trace stored in battery backed RAM

• Trace retrieved using ‘MegaCLI’ utility

• Supported on Windows, Linux and DOS

• Trace can be retained across boots.

• Drains battery

• Does not support 2-way communication

• Can not be used to debug interactively MegaCLI options

• Syntax: o MegaCli -FwTermLog -BBUoff|BBUoffTemp|BBUon|Dsply|Clear -aN|-a0,1,2|-

aALL

• Option –FwTermLog

• Sub-options o BBUoff o BBUoffTemp o BBUon o Dsply o Clear

Servicing the IBM ServeRAID M5015 SAS/SATA II Controllers –Helpful Links


Helpful Links

Publications

• System x RAID products home page http://www.ibm.com/systems/storage/product/systemx/scsi_raid.html

• IBM ServeRAID software matrix http://www.ibm.com/support/docview.wss?uid=psg1SERV-RAID

• IBM System x Configuration and Options Guide http://www.ibm.com/support/docview.wss?uid=psg1SCOD-3ZVQ5W

• QLogic 8Gb FC Single-port and Dual-port HBAs for IBM System x driver download page

http://driverdownloads.qlogic.com/QLogicDriverDownloads_UI/Product_detail.aspx?oemid=376

Download site for the latest operating system drivers http://www.ibm.com/systems/support/.

• General Documentation http://www-947.ibm.com/systems/support/supportsite.wss/docdisplay?lndocid=MIGR-5074106&brandind=5000019

Problem Determination and Troubleshooting

• GLOSSE Pages http://w3.tap.ibm.com/w3ki2/display/GLOSSE/PD_ServeRaid+MR10

Servicing the IBM ServeRAID M5015 SAS/SATA II Controllers – Summary

September 2009 52 Xw5175r100.pdf

Summary

This course has enabled you to:

1. Provide an overview of the IBM ServeRAID M1000 and M5000 series SAS/SATA II controllers

2. List the features of the ServeRAID M5014 and M5015 controllers

3. Describe how to install the ServeRAID M5014 and M5015 controllers and the

ServeRAID M5000 Series Battery Assembly

4. List the three storage management tools for the ServeRAID M series controllers

5. Perform problem determination and log-gathering activities for the ServeRAID

M Series

6. Install and update drivers for the ServeRAID M Series controllers

Servicing the IBM ServeRAID M5015 SAS/SATA II Controllers – Last Page

September 2009 53 Xw5175r100.pdf

Last Page

Date post:	24-Apr-2018
Category:	Documents
Upload:	dinhcong
View:	227 times
Download:	1 times

System x ® Education Servicing the ServeRAID M1000...

Documents