Fujitsu PRIMERGY RX200 S2 User Manual
  1. Manuals
  2. Brands
  3. Fujitsu Manuals
  4. Server
  5. PRIMERGY RX200 S2
  6. User manual

Fujitsu PRIMERGY RX200 S2 User Manual

Onboard scsi raid
Hide thumbs Also See for PRIMERGY RX200 S2:
Table of Contents

Advertisement

Quick Links

See also: User Manual
Areas Covered
Chapter 1 Features (Product Overview/Note)
This chapter explains the overview of the disk array and features of this product.
Chapter 2 Installation Flow and Note
This chapter explains how to install this product and points to note during installation.
Chapter 3 Installing Global Array Manager (GAM)
This chapter explains how to install Global Array Manager (GAM) to this product when
operating in the Windows Server 2003/Windows 2000/Linux environment.
Chapter 4 How to Use GAM
This chapter provides a description of Global Array Manager.
Chapter 5 Replacing a Hard Disk
This chapter explains maintenance related issues, such as hard disk replacement.
Appendix
This appendix explains supplemental items and error codes concerning this product.
PRIMERGY RX200 S2 Onboard SCSI RAID User's Guide
1

Advertisement

Table of Contents
loading

Related Manuals for Fujitsu PRIMERGY RX200 S2

Summary of Contents for Fujitsu PRIMERGY RX200 S2

  • Page 1 PRIMERGY RX200 S2 Onboard SCSI RAID User’s Guide Areas Covered Chapter 1 Features (Product Overview/Note) This chapter explains the overview of the disk array and features of this product. Chapter 2 Installation Flow and Note This chapter explains how to install this product and points to note during installation.
  • Page 2 Remarks ■ Warning Descriptions Various symbols are used throughout this manual. These are provided to emphasize important points for your safety and that of others. The followings are the symbols and their meanings. Ignoring this symbol could be potentially lethal. WARNING Ignoring this symbol may lead to physical injury and/or damage to the server or CAUTION...
  • Page 3 Linux is a trademark or registered trademark of Linus Torvalds in the USA and other countries. Red Hat and all Red Hat-related trademarks and logos are trademarks or registered trademarks of Red Hat, Inc. in the USA and other countries. All Rights Reserved, Copyright© FUJITSU LIMITED 2005 Screen shot(s) reprinted with permission from Microsoft Corporation.

  • Page 5: Table Of Contents

    Contents Chapter 1 Features (Product Overview/Note) 1.1 Disk Array ........1.2 RAID Level .
  • Page 6 4.5 Viewing Information ....... 4.5.1 Event ..........4.5.2 RAID Controller .
  • Page 7 Chapter 1 Features (Product Overview/ Note) This chapter explains the overview and features of the disk array. 1.1 Disk Array ..........1.2 RAID Level .

  • Page 8: Disk Array

    Disk Array A disk array or Redundant Array of Independent Disks (RAID) is a system that can improve reliability compared to a single hard disk, by using a disk controller and multiple hard disks. Access to each hard disk is controlled by the disk controller, but different control methods are used depending on the RAID level settings.

  • Page 9: Logical Drive

    Logical Drive Logical Drive A logical drive is a logical hard disk space consisting of multiple hard disk drives. It is recognized in the same manner as a single hard disk by the OS. In the following figure, a RAID1 disk array is created using 2 hard disks. It is recognized by the OS as if a single hard disk is connected.

  • Page 10: Rebuilding/Initializing A Logical Drive

    Rebuilding/Initializing a Logical Drive In case of RAID1 logical drives, the same data is always written to 2 hard disks. When 1 hard disk fails, the logical drive continues to operate in "Critical" status (status without redundancy) with the other hard disk. Rebuild is the operation to recover data redundancy by copying data from a hard disk that is running normally after replacing a failed hard disk with a new disk.

  • Page 11: Media Verification

    Media Verification Media Verification is a function to detect/correct media errors of hard disks in advance. For the onboard SCSI controller for this server, media verification is always performed when the logical drive is Online. If the hard disk other than the failed disk has a media error at the time of rebuild, data cannot be restored by performing the rebuild.

  • Page 13: Chapter 2 Installation Flow And Note

    Chapter 2 Installation Flow and Note This chapter explains how to install the OS on a disk array created with the onboard SCSI array controller and points to note during installation. 2.1 Installation Flow ..........2.2 Other Points to Note .

  • Page 14: Installation Flow

    The following shows an overview of how to install the OS. When using Linux on the server which has not bundled the Linux service, refer to the Fujitsu PRIMERGY website (http://primergy.fujitsu.com). When Installing the OS on a Newly Created Disk Array...

  • Page 15: Other Points To Note

    Other Points to Note When connecting a hard disk that was previously used in the disk array configuration to a general SCSI adapter, perform a low level format on the hard disk connected to the SCSI adapter in advance. While the server is turned on, do not remove any hard disks except for when replacing a failed hard disk.
  • Page 17 Chapter 3 Installing Global Array Manager (GAM) This chapter explains how to install Global Array Manager (GAM) software to use an onboard SCSI array controller for this server in a Windows Server 2003, Windows 2000 Server, or Linux environment. 3.1 Overview/ Product Requirements ....... 3.2 Installing Global Array Manager (GAM) .

  • Page 18: Overview/ Product Requirements

    Overview/ Product Requirements This section explains Global Array Manager. 3.1.1 Overview of Global Array Manager Global Array Manager (GAM) is an application that allows you to manage a disk array system connected to a SCSI array controller (RAID controller). • Monitoring function GAM collects information about the status and resource usage of disk arrays and notices them.

  • Page 19: Installing Global Array Manager (Gam)

    Installing Global Array Manager (GAM) This section explains how to install Global Array Manager. Global Array Manager must be installed for safe use of this product. Note the following points when installing or uninstalling Global Array Manager (hereafter referred to as GAM). •...
  • Page 20 Before installing GAM, complete the following preparation: • Check that TCP/IP is installed and working properly. • Check that ServerView is installed and working properly. • Insert the ServerStart CD-ROM provided with the server into the CD-ROM drive. • Exit all applications. Exit all applications before starting installation.
  • Page 21 Select [Global Array Manager Server] and click [Change]. The [Select Sub-components] window appears. Make sure [Program Files] and [SNMP] are checked. If any items other than [Program Files] and [SNMP] are displayed, uncheck them. Click [Continue] after confirmation. The [Select Components] window appears again. Click [Next].
  • Page 22 Confirm the installation location and click [Next]. File copying starts. If the following window appears, GAM has already been installed. Cancel this procedure and install GAM again after uninstalling. Specify the client receiving events from GAM Server. In the text box, enter the computer name on which GAM Client is being installed and click [Next].
  • Page 23 The [Server Event Logging] window appears. Make sure [Enable event logging on the server machine] is checked and click [Next]. This option must be enabled. When the full pathname of the configuration file appears, click [OK]. The [Setup Complete] window appears. Click [Finish] to exit the GAM installation wizard.

  • Page 24: Local Logon Setting On A Domain Controller

    3.2.2 Local Logon Setting on a Domain Controller If Windows Server 2003 or Windows 2000 Server is used as a domain controller, it is necessary to set the local logon rights to the user account with which you log on to GAM. Configure the setting according to the following procedure.

  • Page 25: How To Uninstall Gam

    3.2.3 How to Uninstall GAM Perform the following procedure to uninstall GAM. Uninstalling GAM Client Log on as Administrator. Exit all programs before starting uninstallation. If uninstalling GAM while Event Viewer or Computer Management is running, the uninstallation will fail. Make sure to exit all programs. →...

  • Page 26: Using Gam In A Linux Environment

    Using GAM in a Linux Environment To use this product in a Linux environment, it is necessary to install device drivers and GAM. When using Linux on the server which has not bundled the Linux service, refer to the Fujitsu PRIMERGY website (http://primergy.fujitsu.com).

  • Page 27: Using Gam In A Multiple Server Environment

    Using GAM in a Multiple Server Environment The following figure shows a system configuration in which GAM Client on the other Windows server manages GAM Server. Windows server Windows server Monitor/configure GAM status GAM Client GAM Server GAM Agent Notify GAM event SCSI array controller It is necessary to configure the server receiving GAM events during GAM installation.
  • Page 28 When Storing OS Event Logs on GAM Server Windows server Windows server Monitor/configure GAM status GAM Client GAM Server ServerView OS event log AlarmService Notify GAM event GAM Agent SCSI array controller ServerView must be installed on GAM Server. The OS event logs related to GAM events are stored on GAM Server.
  • Page 29 Chapter 4 How to Use GAM GAM is a basic utility to manage the disk array. Read this chapter carefully before use. 4.1 Overview of GAM ..........4.2 Starting and Exiting GAM .

  • Page 30: Overview Of Gam

    Overview of GAM GAM is used for monitoring, management, maintenance and configuration of the SCSI array controller, as well as hard disks and logical drives connected to it. It is necessary to log on (sign on) to GAM to use GAM functions: user authentication is made using the user accounts registered in the OS.

  • Page 31: Starting And Exiting Gam

    Starting and Exiting GAM This section explains how to start and exit GAM. 4.2.1 Starting To start GAM, click [Start] → [Programs] (or [All Programs] on Windows Server 2003) → and [Mylex Global Array Manager Client]. If a server group or server is already defined, [Global Status View] appears. Guest privileges are used at the time of startup.

  • Page 32: Exiting

    Perform the following procedure to sign on. Enter a user name. • When signing on with User privileges Enter any user name in [Username]. • When signing on with Administrator privileges Enter "gamroot" in [Username]. Enter a password in [Password]. If [Remember password for this session] is checked, uncheck it.

  • Page 33: Window Layout

    Window Layout The following provides a description of windows, buttons, and menu items displayed when using GAM. 4.3.1 Startup Window Layout/Functions When GAM is started, a window consisting of [Global Status View] and [Log Information Viewer] will appear. Menu Bar Tool Bar Controller Selection Box Menu Bar...
  • Page 34 Name Function Remarks Global Status View Displays servers in the currently selected server group. Server Icon Displays the server status. For more details, refer to " Server Icon" ( pg.34). Log Information Viewer Displays an event that occurred. For more details, refer to "...

  • Page 35: Controller View] Window Layout/Functions

    4.3.2 [Controller View] Window Layout/Functions Displaying the [Controller View] window enables you to monitor the status of hard disks/logical drives. To display the [Controller View] window, select [Controller View] from the [View] menu. If the [Sign On] window appears, sign on according to "4.2.2 Signing On (Logging On)" ( pg.31). The following window appears.

  • Page 36: Menu Layout/Functions

    • Logical drive Displays the logical drive number and capacity, RAID level set, and logical drive status. The following shows the logical drive status: Icon Color Status Green Normal (OnLine) Yellow Operating without redundancy (Critical) • Enclosure This function is not supported. Double-clicking the icon of each hard disk/logical drive enables you to display more detailed information.
  • Page 37 [View] Menu Menu Function Global Status View Opens the [Global Status View] window. By default, [Global Status View] is configured to appear at the time of GAM startup. Controller View Displays the [Controller View] window. This window displays information of each device, or displays the status of hard disks or the logical drive connected to the controller selected in the controller selection box.

  • Page 38: Tool Bar Icons

    Menu Function Enclosure Displays the information of SES and SAF-TE Enclosure Information Management. Remarks: The Enclosure Information function is not supported. Hard disk cabinets cannot be monitored using this function. Scan Devices Redetects the hardware connected. Settings Not supported. Do not use this. 4.3.4 Tool Bar Icons Tool bar icons at the top of the [Global Array Manager] window enable you to access frequently used...

  • Page 39: Settings

    Settings This section explains how to set parameters. The following setting items are available: • Server group and server settings • Controller option settings 4.4.1 Server Group and Server Settings The server group setting window automatically opens when GAM Client is started for the first time.

  • Page 40: Viewing Information

    Viewing Information The following information can be viewed using GAM: • Information of an event or error that occurred →"B List of GAM Error Codes"(pg.58) • Array configuration or controller information "4.5.2 RAID Controller" (pg.42) • Hard disk information "4.5.3 Viewing Hard Disk Information" (pg.43) •...
  • Page 41 Log Information Viewer [Log Information Viewer] appears automatically when a SCSI array controller is detected at the time of GAM Client startup. Event histories displayed in [Log Information Viewer] are stored in the GAM2CL.LOG file. When [Log Information Viewer] is displayed manually, select [Log Information Viewer] from the [View] menu.

  • Page 42: Raid Controller

    4.5.2 RAID Controller The [Controller View] window enables you to view the status of the RAID controller and hard disks or logical drives connected. Starting Controller View Double-click the server icon in [Global Status View] to start [Controller View]. If you have not signed on to the server, the [Sign On] window appears.

  • Page 43: Viewing Hard Disk Information

    4.5.3 Viewing Hard Disk Information The [Controller View] window displays details of hard disks connected to channels of the controller. Each drive column indicates the hard disks connected to one controller channel each. Double-clicking a hard disk icon enables you to display the information of a specific hard disk. The following information is displayed.
  • Page 44 • Config. size Hard disk capacity available when connected. • Sector size Sector size. • Status Current status of the hard disk. The hard disk status is as follows: Status Meaning OnLine Online (normal) Dead Dead (failed) Rebuilding Rebuild in progress Critical State of failure being expected •...

  • Page 45: Displaying Logical Drive Information

    4.5.4 Displaying Logical Drive Information Defined logical drives are displayed at the right of the [Controller View] window, each icon representing one logical drive (also called Logical Unit or System Drive). To display information of a specific logical drive, double-click a logical drive icon in the [Controller View] window.

  • Page 46: Displaying Request Sense Data

    The following operations can be performed using buttons. • Locate button Blinks the LEDs on all the hard disks that compose the logical drive and notifies the hard disk positions. • Rebuild button When the logical drive status is "Critical", [Rebuild] is enabled, so that it is possible to perform a rebuild of the logical drive.

  • Page 47: Checking The Progress Of A Rebuild

    4.5.6 Checking the Progress of a Rebuild GAM enables you to check the progress of a rebuild in graph form. Rebuild Status When a rebuild is in progress, it is possible to check its progress by selecting [Rebuild status] from the [View] menu.

  • Page 48: Maintenance Functions

    Maintenance Functions The following is the function that can be executed from GAM at the time of maintenance: • Rebuilding a Critical logical drive (Rebuild) 4.6.1 Rebuild When a failed hard disk is replaced, it is necessary to execute a rebuild manually. To execute a rebuild manually, perform the following procedure.

  • Page 49: Chapter 5 Replacing A Hard Disk

    Chapter 5 Replacing a Hard Disk This chapter explains maintenance related issues, such as hard disk replacement. 5.1 Replacing a Hard Disk ........5.2 Preventive Replacement Procedure of a Hard Disk .

  • Page 50: Replacing A Hard Disk

    Replacing a Hard Disk If a hard disk fails, it must be replaced with a new hard disk as soon as possible. The following explains the procedure for replacing a hard disk. For replacement, use a hard disk of the same model (with the same capacity and speed) as the disk that has failed as a rule.

  • Page 51: Preventive Replacement Procedure Of A Hard Disk

    If restart or shutdown is executed during the rebuild, rebuild resumes at the next launch starting from the position where the process stopped. If the rebuild does not start, scan the device. Preventive Replacement Procedure of a Hard Disk When the failure prediction function of the hard disk (S.M.A.R.T.) reports the "Critical" status of a hard disk, it may fail at a future date.
  • Page 52 Confirm that the following log is displayed in Log Information Viewer of GAM. Event ID : S-12 Description : A physical disk has failed. Pull out the plastic lever 90 degrees towards you, and also pull out the likely-to-fail hard disk unit 1 to 3cm to disconnect it from the SCSI bus.

  • Page 53: Appendix

    Appendix A RAID Level ..........B List of GAM Error Codes .

  • Page 54: Araid Level

    RAID Level The onboard SCSI controller for this server only supports RAID1. RAID0/RAID5/ RAID10 are not supported. RAID 0 (Striping) The process of distributing data across multiple hard disks is known as "striping". For example, when writing nine blocks of data (D0 - D8) with three hard disks, each data block is distributed to the hard disks (see below figure).

  • Page 55: Raid 1 (Mirroring)

    RAID 1 (Mirroring) The process of redundantly writing the same data to another hard disk is known as "mirroring". Thanks to this, even if one of the hard disks fails, the system can continue its operation with the data on the other hard disk. Data redundancy of RAID1 by mirroring enhances the high reliability of the server, but the available capacity is that of one hard disk.

  • Page 56: Raid 5 (Striping + Parity)

    RAID 5 (Striping + Parity) In addition to striping (the process distributing data across multiple hard disks), RAID5 creates parity data for redundancy. Parity data is derived via an algorithm from the original data. For example, when writing six blocks of data (D0 - D5) with three hard disks, each data block and the calculated parity data P (DX, DY) are distributed across the hard disks (see below figure).

  • Page 57: Raid 10 (Mirroring + Striping)

    RAID 10 (Mirroring + Striping) In addition to striping (the process distributing data across multiple hard disks), RAID10 mirrors the data for redundancy. For example, when writing six blocks of data (D0 - D5) with four hard disks, each data block and redundant data are distributed across the hard disks (see below figure). Reliability is enhanced by writing the data across four hard disks, and redundancy is achieved with the redundant data.

  • Page 58: B List Of Gam Error Codes

    Windows Event Viewer as events of the "Fujitsu ServerView Service" source. The device address is logged at the beginning of the event log (part within [ ]). The device address indicates where the event occurred.
  • Page 59 Hexad ecimal Type Log item Description Action notatio (0x01) Infor A physical disk has A hard disk is now in Not required. mati been placed online. Online state. The following is a possible cause: • Rebuilding com- pleted. (0x03) Warn physical disk error •...
  • Page 60 Hexad ecimal Type Log item Description Action notatio (0x0a) Error Rebuild stopped Rebuild terminated Replace the hard disk with error. New abnormally due to a again and re-execute the device failed. bad hard disk for the rebuild process. rebuild. (0x0b) Error Rebuild stopped The source disk of the...
  • Page 61 Hexad ecimal Type Log item Description Action notatio (0x16) Warn Parity error found. A parity error was Replace the SCSI BP or detected. SCSI cable. If there is a Dead hard disk, perform the rebuild process. If multiple hard disks are dead, perform the recovery procedure using the Multi Dead function.
  • Page 62 Hexad ecimal Type Log item Description Action notatio (0x22) Error A physical disk A SCSI bus or hard If a hard disk is dead, failed because SCSI disk failed. replace it. If the error bus reset failed. occurs frequently, even though hard disks are not dead, replace the SCSI cable or SCSI BP.
  • Page 63 Hexad ecimal Type Log item Description Action notatio (0x29) Error A physical disk A hard disk failed. Replace the hard disk and failed because of perform the rebuild busy status or parity process. error. If a Multi Dead occurred, take corrective action using the Multi Dead function.
  • Page 64 Hexad ecimal Type Log item Description Action notatio (0x30) Error A physical disk failed because write Replace the hard disk and operation of the perform the rebuild 'Configuration On process. Disk' failed. A hard disk failed. If a Multi Dead occurred, take corrective action (0x31) Error...
  • Page 65 Hexad ecimal Type Log item Description Action notatio (0x47) Error Mirror Race Writing of write buffer If a hard disk is dead, recovery failed for failed. replace it. If this occurs logical drive. repeatedly, replace the baseboard. (0x48) Error Controller A checksum error in Check the setting in SCSI parameters...
  • Page 66 Hexad ecimal Type Log item Description Action notatio (0x86) Error Logical drive has Due to multiple hard Take corrective action been made offline. disk failures, the logical using the Multi Dead drive is now in Offline function. state. (0x87) Error Logical drive is Due to one of the hard Replace the Dead hard...
  • Page 67 Hexad ecimal Type Log item Description Action notatio (0x94) Infor A logical drive has A new logical drive Not required. mati been found. was detected. The following are possible causes: • The system was restarted. (0x95) Infor A logical drive has A logical drive was Not required.
  • Page 68 Hexad ecimal Type Log item Description Action notatio (0x184) Error Controller is dead. The SCSI array Replace the baseboard. System is controller failed. disconnecting from this controller. (0x185) Warn Controller has been The SCSI array Because the firmware is reset. controller received a implementing a recovery, reset command.
  • Page 69 Hexad ecimal Type Log item Description Action notatio (0x193) Error Installation aborted. The configuration Shut down the server and changed while the check the hard disk system was offline. connections. Check to see whether the appropriate hard disks are installed, and remove inappropriate hard disks.
  • Page 70 Hexad ecimal Type Log item Description Action notatio (0x1ac) Error Mirror Race on The logical drive went Replace the hard disk and critical drive. critical. perform the rebuild process. (0x200) Infor System started.- The server or GAM Not required. mati Server started.
  • Page 71 Hexad ecimal Type Log item Description Action notatio (0x322) Warn Configuration The array configuration Check to see whether the Invalid. information is invalid. hard disk is connected properly. If the above does not resolve the issue, recreate the array and restore the backup data.
  • Page 72 Hexad ecimal Type Log item Description Action notatio (0x3a0) Error Internal Controller An error in the SCSI Replace the baseboard. has encountered array controller was Strong-ARM detected. processor specific error. (0x3b0) Error Internal Controller Backend Hardware Error. (0xfff) Unknown Error. An unknown error was Check the logs detected.
  • Page 73 Issued by • The contents of this manual may be revised without prior notice. • Fujitsu assumes no liability for damages to third party copyrights or other rights arising from the use of any information in this manual. • No part of this manual may be reproduced in any without the prior written...

Table of Contents