Universal RAID Utility User's Guide Ver: 2.5 856-127900-112-A 1st Edition Apr 2012 Copyright NEC Corporation 2007-2012.
Trademarks NEC EXPRESSBUILDER is trademarks of NEC Corporation. Microsoft and its logo, Windows, Windows Server, and MS-DOS are registered trademarks of Microsoft Corporation in the United States and other countries. "Linux" is a registered trademark or a trademark in United States or other countries of Linus Torvalds. Red Hat, Red Hat Enterprise Linux, the Shadowman logo and JBoss are registered trademarks of Red Hat, Inc. in the U.S. and other countries.
External Libraries which this product uses This product contains libraries ("External Libraries") provided by the third party suppliers ("Suppliers"). Please assume and agree these libraries' license documents and NOTICE files before using this product. License documents and NOTICE files of "External Libraries" are stored in the following folders.
Introduction This User’s Guide describes RAID System management utility "Universal RAID Utility" the version 2.5. This User's Guide consists of the following four files. User's Guide : This file (uru25eug.pdf) Appendix A : Glossary (uru25euga.pdf) Appendix B : raidcmd Command Reference (uru25eugb.pdf) Appendix C : Logs/Events (uru25eugc.pdf) See "Appendix A : Glossary" for the terms on the Universal RAID Utility and those used in this User’s Guide.
Contents Overview ....................................................................................................................... 9 What is Universal RAID Utility?...................................................................................................... 9 Structure of Universal RAID Utility ............................................................................................... 10 Functional differences from previous version of Universal RAID Utility ..............................
RAID Controller ........................................................................................................................................ 33 Battery .................................................................................................................................................... 34 Disk Array ................................................................................................................................................ 34 SSD Cache Disk Array ................
Physical Devices Available for "Create Logical Drive - Simple Mode"............................................................. 74 Creating Logical Drives by "Create Logical Drive - Simple Mode" ................................................................. 74 Creating Logical Drive Freely ....................................................................................................... 75 Operation Procedure of "Create Logical Drive - Custom Mode" .................................................
Operation when the Logical Drive is offline due to failure of Physical Device .............................................. 116 Monitoring Battery Status ..........................................................................................................117 Monitoring Enclosure Status .......................................................................................................118 Monitoring Various Events of RAID System ......................................................................
Overview This chapter describes the overview of the Universal RAID Utility. What is Universal RAID Utility? The Universal RAID Utility enables RAID Systems in a computer to be managed. The Universal RAID Utility is characterized as follows. 1. Allowing a variety of RAID Systems to be managed Conventionally, a specific management utility must be used for each RAID System. On the other hand, only the Universal RAID Utility can manage more than one RAID System.
Structure of Universal RAID Utility Management PC The Universal RAID Utility consists of the following modules. The module that can be used is different depending on operating system. Windows Server raidsrv service The raidsrv service always operates in the server to manage RAID Systems. Receiving a processing request from the RAID Viewer or raidcmd, the raidsrv service provides proper information on a RAID System or performs an appropriate operation for the RAID System.
Functional differences from previous version of Universal RAID Utility Ver2.4 and Ver2.5 The following features have been enhanced and changed from Universal RAID Utility Ver2.4. 1. Addition of the following operating systems to support Red Hat Enterprise Linux 5.7 Red Hat Enterprise Linux 6.1 Red Hat Enterprise Linux 6.2 VMware ESX 4.0 Update 3 VMware ESX 4.0 Update 4 VMware ESX 4.1 Update 2 2.
after displaying the version of Universal RAID Utility by executing raidcmd without parameters. See “RAID System Configuration” for details. Support of the Logical Drive with the level of RAID 60 Universal RAID Utility Ver2.5 supports the display, operation, deletion of the RAID 60 Logical Drive. Creation of the RAID 60 level Logical Driver is not available. Use the configuration utility of the RAID Controller to create RAID 60 level Logical Drive. 9.
System requirements This chapter describes system requirements of the Universal RAID Utility. Hardware Computers The computers can contain RAID Systems to be managed by the Universal RAID Utility. RAID Systems to be managed by Universal RAID Utility For RAID Systems which can be managed by the Universal RAID Utility, see the documentation attached to the computer in which RAID Systems are installed and that attached to the RAID Controller including the Universal RAID Utility.
Runtime component of Microsoft Visual C++ 2005 SP1 library To use the RAID Viewer, the runtime component of the Microsoft Visual C++ 2005 SP1 library equivalent to Microsoft Security Bulletin MS09-035 is required. Windows Server 2008 R2 and Windows 7 include the runtime component of the Microsoft Visual C++ 2005 SP1 library equivalent to Microsoft Security Bulletin MS09-035.
Others Resources Resource Available Hard Disk Space Windows Linux/VMware ESX 250MB or more ← (not include Microsoft .NET Framework (not include the required packages as Ver2.0, the runtime of Microsoft Visual C++ standard C++ library...etc) 2005 SP1 library) RAM 512MB or more ← TCP ports used by Universal RAID Utility The Universal RAID Utility uses the following three TCP ports.
Setup of Universal RAID Utility This chapter describes installation and uninstallation of the Universal RAID Utility. Installation image Use the setup program of Universal RAID Utility for the installation and the uninstallation. The setup program is contained in the installation image of the Universal RAID Utility. Before the Universal RAID Utility can be installed or uninstalled, you must prepare the installation image. The installation images of Universal RAID Utility are different by operating system.
Installation and Uninstallation This section describes the procedure of installation and uninstallation of Universal RAID Utility. kind Installation Description Install Universal RAID Utility newly, when there is not Universal RAID Utility in the server. Procedure (Windows) 1. Preparing installation (Windows) 2. Installation (Windows) Procedure (Linux) 1. Preparing installation (Linux) 2. Installation (Linux, VMware ESX) Procedure (VMware ESX) Uninstallation 1.
Preparing installation (Windows) RAID Viewer and Log Viewer use Microsoft .NET Framework Versions 2.0 to 3.5 and the runtime component of the Microsoft Visual C++ 2005 SP1 library. Install these components if it does not exist in the computer where the Universal RAID Utility is to be installed. Installation of Microsoft .NET Framework Windows Server 2008 and Windows Server 2008 R2, Windows Vista, Windows 7 include .NET Framework Versions 2.0 to 3.5. Therefore, you do not need to install .
CPU architecture x86/x64 Required component and its vendor [Microsoft Visual C++ 2005 Service Pack 1 Redistributable Package ATL Security Update] http://www.microsoft.com/downloads/details.aspx?familyid=766a6af7-ec73-40ff-b072-911 2bab119c2&displaylang=en Use the vcredist_x86.exe whatever the CPU architecture may be. When you use RAID Viewer of Universal RAID Utility Ver2.
Step 5 Next, the wizard appears as shown in the figure to the right. Click [Install] to start the installation. Step 6 At the completion of the installation, the “InstallShield Wizard Complete” screen appears. Click [Finish]. Step 7 When the installation completes, "Universal RAID Utility" is registered to the program list in the [Change or Remove Programs]. Also, either program or both programs to manage the RAID Controllers shown below will be registered depending on the type of the RAID Controller.
Uninstallation (Windows) The Setup Program uninstalls Universal RAID Utility when there is the same version of Universal RAID Utility in the server. You can start the uninstallation by using the clicking [Delete] on "Universal RAID Utility" program in the list of [Add or Remove Program]. Step 1 Terminate RAID Viewer, Log Viewer, or Event Viewer if it is opened. Stop raidcmd if it activated.
Preparing installation (Linux) You must prepare the following packages for using the Universal RAID Utility. If the following packages do not exist in the computer that installs Universal RAID Utility, you need to install them. Red Hat Enterprise Linux 4.8 or later Red Hat Enterprise Linux 5.4 or later MIRACLE LINUX V4.0 SP 2 or later Asianux Server 3 packages x86 x64 standard C++ library libstdc++ libstdc++ (i386) GCC 3.3.
You can recognize the existence and install these packages by the following procedure (This procedure is example using GCC 3.3.4 Compatibility standard C++ library). Step 1 You can check by rpm command which does GCC 3.3.4 Compatibility standard C++ library exist in the > rpm -q compat-libstdc++-33 1 compat-libstdc++-33-3.2.3-* computer or not. If it has existed in your computer, rpm > command displays the right way (the part of "*" is different by operating system).
Universal RAID Utility does not install the following packages in the VMware ESX environment. Please note that the installation is finished successfully in VMware ESX even after the program does not exist. storelib-a.bb-0. (a.bb is version) Lib_Utils-a.bb-cc.noarch (a.bb-cc is version) NEC ESMPRO Manager Ver5.5 or later versions is required to manage the server where Universal RAID Utility Ver2.5 has been installed. See “Installation of NEC ESMPRO Manager” for details.
Change of Universal RAID Utility Configuration The configuration of Universal RAID Utility must be changed when a RAID Controller is connected or removed. In this case, uninstall existing Universal RAID Utility and then install new Universal RAID Utility.
Starting or Stopping Universal RAID Utility This chapter describes the procedure of starting or stopping each module in the Universal RAID Utility. raidsrv service The raidsrv service is started automatically when your server is booted and stopped automatically when your server is shut down. Without operation of the raidsrv service, the Universal RAID Utility cannot operate normally. Neither makes the raidsrv service be not started nor stop the raidsrv service.
RAID Viewer Use [Start] menu to open the RAID Viewer. Click [Start], and point menu in order to [Programs], [Universal RAID Utility] and [RAID Viewer]. To use the RAID Viewer, you should log on to the computer as a user having the administrator authority. Only users having the administrator authority can execute the RAID Viewer. When you start the RAID Viewer on the server not connected to internet, may wait a few minutes until startup the RAID Viewer.
Log Viewer Use [Start] menu to open the Log Viewer. Click [Start], and point menu in order to [Programs], [Universal RAID Utility], [Log Viewer]. Or select [Tool] menu of the RAID Viewer and click [Log Viewer]. To use the Log Viewer, you should log on to the computer as a user having the administrator authority. Only users having the administrator authority can execute the Log Viewer.
raidcmd raidcmd is command on console as "Command Prompt" in Windows and console (terminal) in Linux and VMware ESX. The raidcmd is executed on a console. Use the raidcmd by the methods described in "Functions of raidcmd". A user having the administrator authority should run the raidcmd. Only users having the administrator authority can execute the raidcmd. In case of the operating system is Linux or VMware ESX, the raidcmd can't start by existing the lock file after aborted it.
Standard and Advanced Modes The RAID Viewer and raidcmd can operate in two RAID System Management Modes, which are Standard Mode and Advanced Modes. The Standard Mode provides the RAID Viewer and raidcmd with standard management functions for RAID Systems. The Advanced Mode provides the RAID Viewer and raidcmd with advanced management and maintenance functions for RAID Systems.
The following message will be displayed when you operate in the Standard Mode with raidcmd. Change the RAID System Management Mode to Advanced Mode. - raidcmd: Invalid RAID System Management Mode. RAID System Management Mode when startup RAID Viewer and raidcmd RAID Viewer RAID Viewer always starts with Standard Mode. You can change the RAID System Management Mode when RAID Viewer starts. See "Changing RAID System Management Mode at Start of RAID Viewer".
Functions of RAID Viewer This chapter describes the functions of the RAID Viewer. Structure of RAID Viewer As shown in the figure below, the RAID Viewer is composed of four parts, or Tree View, Operation View, Menu Bar and Status Bar. Menu Bar Operation View Tree View Status Bar Figure 2 Structure of RAID Viewer Tree View The Tree View shows the configuration of RAID Systems managed by the Universal RAID Utility as a hierarchical structure.
Server The first level node shows the server in which the Universal RAID Utility operates. [Icon] Item Description Indicates the name of server having the RAID System. The server icon indicates the status of all the RAID Systems existing in the server. Icon Meaning Description Server - Normal All RAID Systems in the server operate normally. Problems which RAID Controllers define as failures do not occur.
Battery If the RAID Controller has the Battery, the RAID Controller node has a Battery node. A Battery node and icon shows the status of Battery. [Icon] Battery [] Item Description Indicates the status of the Battery installed in the RAID Controller. Icon Meaning Description Battery - Normal The Battery operates normally. Battery - Warning The RAID Controller detects any problem of the Battery.
An SSD Cache Disk Array icon indicates the status of SSD Cache Disk Array. Icon Meaning Description SSD Cache Disk Array - Normal All the SSD Cache Drives you have created, all the member Physical Devices operate normally. No failures have not been detected by the RAID Controller. SSD Cache Disk Array - Warning One or more Physical Devices in the warning condition exist in the SSD Cache Disk Array.
An SSD Cache Drive icon indicates the status of the SSD Cache Drive. Icon Meaning SSD Cache Drive - Normal SSD Cache Drive - Fatal Description The SSD Cache Drive operates normally. Because Status of all Physical Devices for the SSD Cache Drive is Failed, the SSD Cache Drive is offline and accessing the SSD Cache Drive is disabled. Physical Device The Physical Device node exists in either the Disk Array node or the RAID Controller node.
Assigning Physical Device Number The policy to assign Physical Device Number is changed in Universal RAID Utility Ver2.5. In Universal RAID Utility Ver2.4 and the earlier versions, the number starting from 1 is assigned to each Physical Device in the ascending order of the ID of Physical Devices. From Ver2.5, the policy has been changed that the Physical Device number is assigned based on the enclosure number and slot number, in the format “es”.
Operation View The Operation View indicates the status and results of operations executed in the server after the RAID Viewer is started. Figure 4 Operation View The following operations may appear on the Operation View. For each operation, the target RAID Controller, Logical Drive, or Physical Device, and the status of the operation appear. Initialize Rebuild Consistency Check Operations being executed while the RAID Viewer is started and those started after the RAID Viewer is started are listed.
When progress is frequently updated such as initializing a Logical Drive with extremely small capacity, the progress of [Status] might not be able to be displayed correctly. Correct progress is displayed when [Rescan] in [File] menu is run at such time. Menu Bar The RAID Viewer has four menu items on the Menu Bar, or [File], [Control], [Tool] and [Help]. Figure 5 Menu of RAID Viewer The following describes the menu items.
Functions executable by RAID Controller Menu item Description [Create Logical Drive] Creates a Logical Drive in the selected RAID Controller. [Create Logical Drive] has two modes, [Simple] and [Custom]. In the [Simple] mode, a Logical Drive can be simply created only by selecting a RAID Level and Physical Devices. In the [Custom] mode, a Logical Drive can be created by specifying detailed settings. [Create SSD Cache Drive] Creates an SSD Cache Drive in the selected RAID Controller.
[Tool] menu [Tool] menu includes tools used to manage RAID Systems and items for changing the operation of the RAID Viewer. Menu item Description [Easy Configuration...] Executes Easy Configuration allowing a RAID System to be configured easily. [Log Viewer] Starts the Log Viewer. [Advanced Mode] or [Standard Mode] Alters the RAID System Management Mode. The item varies depending on the RAID System Management Mode. [Advanced Mode] sets the RAID System Management Mode to the Advanced Mode.
Functions of Log Viewer This chapter describes the functions of the Log Viewer. Structure of Log Viewer As shown in the figure below, the Log Viewer is composed of three parts, or Log View, Menu Bar and Status Bar. Menu Bar Log View Status Bar Figure 7 Structure of Log Viewer The Status Bar is used only for changing the size of the Log Viewer window.
Log View The Log View indicates RAID System operation logs logged by the raidsrv service. You can view the following information on the Log View. Item Type Description Logs are classified into three types as follows: Fatal: A log of the type is registered when a fatal error occurs. Warning: A log of the type is registered when a problem occurs which is not fatal but requires your attention.
Menu Bar The Log Viewer has two menu items, or [File] and [Help] on the Menu Bar. Figure 8 Menu of Log Viewer The following describes each menu item. [File] menu [File] menu includes items for updating the display information on the Log Viewer and terminating the Log Viewer. Menu item Description [Refresh] Reads the contents in the RAID Log and updates the Log View to the latest. [Properties...
Functions of raidcmd This chapter describes the functions of the raidcmd. Command Line To use the raidcmd, specify a command and one or more parameters for the command if necessary. > raidcmd command Executing the raidcmd without any command and its parameters indicates the version of the raidcmd and the configuration of the RAID system. Returned Value from raidcmd The returned value of the raidcmd is the result of executing the command.
RAID System Configuration raidcmd displays the RAID System configuration in a tree view, the same as RAID Viewer.. Execute raidcmd without a command to display the RAID System configuration. The version of Universal RAID Utility and the configuration of the current RAID System. > >raidcmd Universal RAID Utility Ver 2.
Referring to Information on RAID System This chapter describes how to see the configurations and status of RAID Systems and the RAID System operation log. Referring to Property of RAID Controller For the information on a RAID Controller, see the property of the RAID Controller. To display the property of RAID Controller by RAID Viewer, click the RAID Controller whose information is to be seen on the Tree View and click [Properties] on the [File] menu.
Item RAID Viewer Premium Feature Item raidcmd Description Premium Feature Indicates the Premium Feature of RAID Controller. Displayed only when Premium Feature is enable. Two possible statuses are as follow: Cache Cade Battery Status Indicates the status of the Battery installed in the RAID Controller. Three possible statuses are as follows: Normal: Indicates that the Battery can be used normally. Warning: Indicates that the Battery cannot be used normally due to some reason.
Referring to Property of Battery For the information on a Battery on RAID Controller, see the property of the Battery by RAID Viewer and, see the property of the RAID Controller by raidcmd. To display the property of Battery by RAID Viewer, click the Battery whose information is to be seen on the Tree View and click [Properties] on the [File] menu. The [General] tab indicates the property of the Battery.
Item RAID Viewer Item raidcmd Description Number RAID Controller #X Logical Drive #Y Indicates the management number (logical address) of the Logical Drive in the Universal RAID Utility. The Universal RAID Utility assigns a number beginning with 1 in correspondence with the value of [ID]. ID ID Indicates the original identification value of the Logical Drive.
Each RAID Controller supports specific RAID Levels and Stripe Sizes. Unsupported items indicate space or do not appear in the list. Each RAID Controller supports specific Cache Modes. Unsupported Cache Modes do not appear. Each RAID Controller supports specific items appearing on the Property tab of the Logical Drive and specific items whose settings can be changed. Unsupported items indicate space or do not appear in the list.
Item RAID Viewer Item raidcmd Description Enclosure Enclosure Indicates the number of Enclosure inserted Physical Device. This value is the original identification value of Enclosure. Enclosure Position Enclosure Position Indicates the location where Enclosure in which Physical Device is inserted is connected.
Item RAID Viewer Power Status Item raidcmd Power Status Description Indicates the Power Status of Physical Device. Three possible conditions are as follows: On : Power Status is active. Power Saving : Power Status is Power Saving. Transitioning : Power Status is transitioning from Power Saving to active. The ID is not displayed in RAID Configuration Utility for N8103-149/150/151/160 RAID Controller.
Referring to Property of Disk Array For the information on a Disk Array, see the property of the Disk Array. To display the property of Disk Array by RAID Viewer, click the Disk Array whose information is to be seen on the Tree View and click [Properties] on the [File] menu. The [General] tab indicates the property of the Disk Array. Use "property" command to see property of a Disk Array by raidcmd.
Checking Execution Status of Operation RAID Viewer and raidcmd allows the checking execution status of operation in the RAID System. To check the execution status of operation by RAID Viewer, use Operation View on RAID Viewer. See "Operation View" for detail. To check the execution status of operation by raidcmd, use "oplist" command. The following operations are displayed by "oplist" command.
Referring to RAID System Operation Log Operations done for RAID Systems and events occurred in the RAID Systems are registered to the RAID Log of the Universal RAID Utility. See "Logging Events to RAID Log" for detail. In case of the operating system is Windows, use Log Viewer to see RAID Log The information saved in the RAID Log at the start of the Log Viewer appears on it. To update the information, click [Refresh] on the [File] menu.
Configuration of RAID System This chapter describes the configuration of a RAID System by using the Universal RAID Utility. The Universal RAID Utility provides a variety of functions depending on purposes. Would like to make Hot Spare as measures against failure of Physical Device. See "Making Hot Spare". Allows Global or Dedicated Hot Spare to be made without errors. Would like to configure RAID System easily due to no expert knowledge of RAID System.
Making Hot Spare The Universal RAID Utility can make a Hot Spare to be replaced with a Physical Device in which a failure occurs. Hot spares can have the following two modes. Mode Description Global (Hot Spare) Available as a Hot Spare of every Disk Array for a single RAID Controller. Dedicated (Hot Spare) Available as a Hot Spare of a specific Disk Array for a single RAID Controller. In either mode, note the following to have a Hot Spare operate normally.
About Dedicated Hot Spare Dedicated Hot Spare is a Hot Spare for the specified Disk Arrays under a single RAID Controller. The Dedicated Hot Spare has the following features: Dedicated Hot Spare is a Hot Spare for specified Disk Arrays. One Dedicated Hot Spare can be a Hot Spare for one or more Disk Arrays. One or more Dedicated Hot Spare can be a Hot Spare for one or more Disk Arrays. Dedicated Hot Spares cannot be created in a Disk Array containing Logical Drives with the RAID Level being RAID 0.
Disk Array #1 Disk Array #2 Dedicated Hot Spare #1 Dedicated Hot Spare #2 Figure 14 Dedicated Hot Spare 3 Ex 4 : In case of the RAID System in Ex2, you can add more Dedicated Hot Spare likely Ex2. If you add the Dedicated Hot Spare to the Disk Arrays #1 and #2, the both Dedicated Hot Spare are the Hot Spare for the Disk Arrays #1 and #2.
raidcmd Step 1 Execute "hotspare" command with –mr option and the following parameters. -c : Number of the RAID Controller containing the Physical Device with which a Hot Spare is made -p : Number of the Physical Device with which a Global Hot Spare is made -mr : Specify "make" to make Global Hot Spare Ex. Create a Global Hot Spare using the Physical Device with RAID Controller:1 and Physical Device number:e252s5.
Step 4 If the Dedicated Hot Spare is created successfully, you can find that the value of [Status] is set to [Hot Spare] and item [Hot Spare Information] appears newly with value [Dedicated (Disk Array #X)]. raidcmd Step 1 Execute "hotspare" command with -mr option and the following parameters.
raidcmd Step 1 Execute "hotspare" command with -mr option and the following parameters. -c : Number of the RAID Controller containing the Physical Device from which the Hot Spare is removed -p : Number of the Physical Device from which the Hot Spare is removed -mr : Specify "remove" to remove Hot Spare Ex. Remove a Hot Spare with RAID Controller number: 1 and Physical Device number: e252s5.
Configuring RAID System Easily The Universal RAID Utility supports the Easy Configuration function allowing configurations such as creating Logical Drive and making a Hot Spare to be provided in the state where unused Physical Devices are connected to RAID Controllers.
Step 4 In step 2/3, specify the number of Physical Devices used by Logical Drives (or the number of Physical Devices used for data storage) and the number of Logical Drives created in the RAID Controller. If Physical Devices of different interface types or device type exist, specify the number of Physical Devices in each type. After the specification, click [Next]. Step 5 Step 3/3 shows the configuration of the RAID System to be configured by the Easy Configuration.
raidcmd Step 1 Connect Physical Devices used for Easy Configuration to the RAID Controller before executing raidcmd if required. Step 2 2 > raidcmd econfig Step 1/3 : Select RAID Controller RAID Controller #1 LSI MegaRAID SAS 9267-8i Execute "econfig" command. RAID Controller [1] :1 Step 3 Specify the conditions on Easy Configuration. In step 1/3, select the RAID Controller to be configured. Enter the RAID Controller number to be configured.
RAID Controller Enabling Easy Configuration to Be Executed Any RAID Controller enabling Easy Configuration to be executed must meet the following conditions. 1. Allowing Dedicated Hot Spares to be made, and 2. Connecting with more than one unused Physical Device. Physical Devices Available for Easy Configuration Only unused Physical Devices are available for Easy Configuration. Unused Physical Devices are those with their [Status] being [Ready].
Physical Devices used for Logical Drives Physical Devices of lower Physical Device Numbers are used preferentially for Logical Drives to be created excluding those for making Hot Spares. Ex. : If Physical Devices 1 - 7 can be used for Easy Configuration and Physical Device 3 is used as a Hot Spare, Logical Drives #1 is created with Physical Devices 1, 2, and4 in the ascending order of Physical Device Numbers and Logical Drives #2 is created with Physical Devices 5, 6, and 7.
Capacity of Logical Drive The capacity of a Logical Drive to be created is defined by the RAID Level and the capacities of Physical Devices used for the Logical Drive. The Easy Configuration uses the entire areas of the Physical Devices to create a Logical Drive. When a single Logical Drive is created by using Physical Devices of different capacities, the smallest capacity is applied among those of the Physical Devices. Ex.
Making Hot Spares by Easy Configuration This section describes the information on Hot Spares to be made by the Easy Configuration. Number of Hot Spares The number of Hot Spares is defined by the number of unused Physical Devices connected to the RAID Controller and the number of Physical Devices used for Logical Drives. The number of Hot Spares results from subtracting [Number of Physical Devices specified for Logical Drives] from [Unused Physical Device count] in step 2/3 of the [Easy Configuration...
Ex.: If Physical Devices 1 - 7 are used in Easy Configuration to create two Logical Drives and a single Hot Spare, the Hot Spare will be the Dedicated Hot Spare for each Logical Drive. Physical Devices 1,2 and 3 Physical Devices 4, 5 and 6 Physical Device 7 Logical Drive #1 Logical Drive #2 Dedicated Hot Spare Figure 20 Making Dedicated Hot Spare in Easy Configuration 1 Ex.
Creating Logical Drive Easily The Universal RAID Utility supports "Create Logical Drive - Simple Mode" in which a Logical Drive can be created only by selecting two selection items according to the guide. "Create Logical Drive - Simple Mode" allows you to create a Logical Drive only by specifying two selection items, or the RAID Level of the Logical Drive and Physical Devices to be used. The benefits of creating a Logical Drive with "Create Logical Drive - Simple Mode" are as follows.
Step 4 In step 2/3, select Physical Devices to be used to create the Logical Drive. If Physical Devices of different types exist in the RAID Controller, click the type to be used on [Type]. Next, check the check boxes of Physical Devices to be used on [Physical Device]. You must select Physical Devices to be used by the number allowing the RAID Level selected in Step 1/3 to be created. After selecting Physical Devices properly, click [Next].
Step 3 Type "yes" to reply to the confirmation message. Then a Logical Drive is created. Step 4 After the Logical Drive is created successfully, the raidcmd terminates normally. The Logical Drive has been created completely. You can check the information on the Logical Drive by using "property" command. However, the Initialize of the Logical Drive having been created may not be completed. The progress of initializing the Logical Drive can be checked by using "oplist" command.
Creating Logical Drive Freely The Universal RAID Utility supports "Create Logical Drive - Custom Mode" in which a Logical Drive can be created as required by specifying the setting items of the Logical Drive closely. "Create Logical Drive - Custom Mode" allows you to create a Logical Drive by specifying the setting items of the Logical Drive closely. It can also be used to create Logical Drives of several RAID Levels or create a Logical Drive by using unused area of Disk Array.
Step 4 If you click [Add] in the [Create Logical Drive (Custom)] dialog box, the [Register Logical Drive] wizard is started. In step 1/3, select the RAID Level of the Logical Drive to be registered. After the selection, click [Next]. Step 5 In step 2/3, the operation varies depending on the RAID Level selected in step 1/3. (1) When RAID 0, RAID 1, RAID 5, or RAID 6 is selected as the RAID Level, select an existing Disk Array or create another Disk Array.
Step 6 In step 3/3, select the setting items of the Logical Drive to be registered. [Capacity] should be a value within the Capacity of the Logical Drive to be created. If the RAID Level of the Logical Drive to be created is RAID 10 or RAID 50, you do not have to enter the value. Select [Stripe Size], [Cache Mode] and [Initialize Mode]. After selecting all the setting items, click [Next]. Step 7 If you click [Next] in step 3/3, then [Completing the "Register Logical Drive" Wizard] will appear.
raidcmd A count of Logical Drive created by raidcmd is 1 at same time. Step 1 Connect Physical Devices used for a Logical Drive to the RAID Controller before executing raidcmd if required. Step 2 Execute "mkldc" command with the following parameters. > raidcmd mkldc -c=1 -p=e252s2,e252s3,e252s4 -rl=5 -cp=20 -ss=64 -cm=auto -im=full raidcmd creates Logical Drive #1.
Creating Logical Drives by "Create Logical Drive - Custom Mode" This section describes the information on Logical Drives to be created by "Create Logical Drive - Custom Mode". RAID Levels The RAID Level of a Logical Drive which can be created by "Create Logical Drive - Custom Mode" should be RAID 0, RAID 1, RAID 5, RAID 6, RAID 10, or RAID 50. Supported RAID Levels vary in RAID Controllers. Unsupported RAID Levels cannot be selected.
Deleting Logical Drive The Universal RAID Utility can delete a Logical Drive becoming unnecessary. The function of deleting a Logical Drive is available only in the Advanced Mode. Before deleting a Logical Drive, check if the Logical Drive contains required data. Deleting a Logical Drive causes all the data saved in the Logical Drive to be lost. You can delete Logical Drive with partitions. You can delete only the Logical Drive that is located at the end of Disk Array.
Using CacheCade The CacheCade is the function to create the SSD Cache Drive using Solid State Drive(S) (SSD). The SSD Cache Drive operates as the Cache of Logical Drive. SSD Cache Drive that improves access performance of the Logical Drive. The function of creating SSD Cache Drive is available when the CacheCade function is enabled. The function of Create and Delete SSD Cache Drive are not available with the RAID Controller of which the CacheCade is disabled or is not supported.
Step 4 Click [Next]. The [Check the contents, and completing the "Create SSD Cache Drive" Wizard] window appears. The window shows the contents of SSD Cache Drive to be created. To create an SSD Cache Drive with the settings displayed, click [Finish]. To change the settings , click [Back]. Click [Finish] to create an SSD Cache Drive and close the wizard. After the wizard closes, see the Tree View to check the contents. Click [Back] to cancel the creation of SSD Cache Drive. raidcmd Step 1 required.
Capacity of SSD Cache Drive The capacity of SSD Cache Drive to be created depends on the capacity of Solid State Drive(s). The SSD Cache Drive is created by using the entire areas of Solid State Drive. When a single Solid State Drive is created by using Solid State Drives with different capacities, the smallest capacity is applied among those of the Solid State Drives. Ex. : [Create SSD Cache Drive] creates the SSD Cache Drive by using Solid State Drives (Physical Devices (SSD) 6, 7).
Deleting SSD Cache Drive The procedure of deleting an SSD Cache a Drive is described below. The function of Delete SSD Cache Drive is available only in the Advanced mode. Make sure that the RAID System management mode is Advanced mode. RAID Viewer Step 1 Start the RAID Viewer. Step 2 Click the SSD Cache Drive to be deleted on the Tree View. Click [Delete SSD Cache Drive] on the [Control] menu. Step 3 Click [yes] on the dialog box shown to the right to delete the SSD Cache Drive.
Maintenance of RAID System This chapter describes the maintenance of a RAID System using the Universal RAID Utility. Providing Patrol Read for Physical Devices The Patrol Read function reads data saved in all Physical Devices in a RAID System entirely to check whether a read error occurs or not regularly in the background. The Patrol Read is effective to find failures including Physical Device medium error early. Be sure to execute Patrol Read for a RAID Controller if it supports the Patrol Read.
Checking Result of Executing Patrol Read You can find the result of executing Patrol Read by checking the RAID Log of the Universal RAID Utility. When detects something problem, Universal RAID Utility records the log in the RAID Log. Setting Patrol Read Priority You can set the priority in which Patrol Read is executed in your server. The procedure of setting the Patrol Read Priority is described below. Changing the priority of Patrol Read is available only in the Advanced Mode.
Checking Logical Drive Consistency The Consistency Check function checks the consistency between the data in the data area of a Logical Drive and the parity. The Universal RAID Utility can start or stop Consistency Check and change the priority in which Consistency Check is executed. The Consistency Check is effective next to Patrol Read to find failures including Physical Device medium error early.
Executing Consistency Check for arbitrary Logical Drive You can register the task to schedule the Consistency Check using the Task Scheduler on Windows or cron on Linux or VMware ESX. After installing Universal RAID Utility, a task to schedule the Consistency Check will be registered that makes it possible to detect failures such as media errors on the RAID Controller which does not support the Patrol Read function.
Executing Consistency Check for all Logical Drives for RAID Controller not supporting Patrol Read To execute Consistency Check for all Logical Drives of a RAID Controller not supporting Patrol Read, use "ccs" command of the raidcmd. Stopping Consistency Check You can stop Consistency Check being executed on the way. The procedure of stopping Consistency Check is described below. RAID Viewer Step 1 Start the RAID Viewer. See [Operation View] while Consistency Check is executed.
Setting Consistency Check Priority You can set the priority at which Consistency Check is executed in the server. The procedure of setting the Consistency Check Priority is described below. Setting Consistency Check Priority are available only in the Advanced Mode. RAID Viewer Step 1 Start the RAID Viewer. Click the RAID Controller on the Tree View. Then click [Properties] on the [File] menu. Step 2 Click the [Options] tab in the [RAID Controller Properties] dialog box.
Initializing Logical Drive The Initialize writes 0s into the entire area of a Logical Drive to erase the data saved in the Logical Drive. Use the function when you want to erase the data saved in a Logical Drive fully. Initialize has two modes listed in the table below. Mode Description Full Writes 0s into the entire area of a Logical Drive to erase the data fully. Quick Writes 0s into some blocks in a Logical Drive. Only erases OS installation and partition management information.
Step 3 After Initialize is started, the progress of the Initialize appears on the Operation View. At the completion of the Initialize, [Status] on the Operation View is changed to [Completed]. raidcmd Step 1 Execute "init" command with -op option and the following parameters.
Setting Initialize Priority You can set the priority at which Initialize is executed in the server. The procedure of setting the Initialize Priority is described below. Setting Initialize Priority are available only in the Advanced Mode. RAID Controllers of some types may not support the setting Initialize Priority. If does not support this function, RAID Viewer and raidcmd do not display this item in the property of RAID Controller and the execution of "optctrl" command of raidcmd fails.
Changing Cache Mode of Logical Drive You can change the cache mode of Logical Drive. The range of change differs depending on the type of the RAID Controller. RAID Controller Changed cache Range of change Onboard RAID Controller (LSI Embedded MegaRAID) Hard Disk Drive All the Logical Drives in a single Disk Array. Option and Internal RAID Controller (N8103-128/G128/134/135) RAID Controller All the Logical Drives in a single RAID Controller.
Rebuilding Physical Device Rebuild means incorporation of a new Physical Device to a Logical Drive after a Physical Device is replaced with the new one due to occurrence of an event such as a failure. In general, the Rebuild is automatically started by a function of the RAID Controller called standby rebuild or hot-swap rebuild. Accordingly, manual Rebuild is not required so often. If required, use the Universal RAID Utility.
raidcmd Step 1 Execute "rebuild" command with -op option and the defined parameters. 1 > raidcmd rebuild -c=1 -p=e252s4 -op=start > > raidcmd oplist RAID Controller #1 PD e252s4 : Rebuild (Running 0%) > 2 -c : Number of the RAID Controller containing the Physical Device for which Rebuild is executed -p : Number of the Physical Device for which Rebuild is executed -op : Specify "start" to start Rebuild Ex.
Checking Result of Executing Rebuild You can find the result of executing Rebuild by checking the Tree View, the property of the Physical Device and the RAID Log of the Universal RAID Utility. If Rebuild succeeds, the icon of the Physical Device subject to the Rebuild changes to [Online] on the Tree View. In addition, the [Status] in the Property tab of the Physical Device is set to [Online]. When detects something problem, Universal RAID Utility records the log in the RAID Log.
Reducing the power consumption of the Physical Device The HDD Power Saving is the function to spin down the Physical Device that is not in use. The HDD Power Saving reduces the power consumption of the System by spinning down the Physical Device. Set the Power Saving in each RAID Controllers. You can see which type of the Physical Device is available for the HDD Power Saving function in the table below.
raidcmd Step 1 Execute "optctrl" command with -psd option and the defined parameters. 2 -c : Number of RAID Controller for which Power Saving Device is set. -psd : Select none or hotspare to change the Power Saving Device. Ex) Changes value of HDD Power Saving (Hot Spare) to "enable" (RAID Controller Number is 1) raidcmd optctrl -c=1 -psd=hotspare Step 2 Checking the execution result by using "property" command. The following parameter of RAID Controller is changed.
raidcmd Step 1 Execute the "optctrl" command with -dst option and the defined parameters. -c : Number of RAID Controller for which Device Standby Time is set. -dst : Select 0.5, 1, 2, 4, or 8 hours to change the Device Standby Time. Ex. Changes the value of Device Standby Time to "2hours" (RAID Controller Number is 1). raidcmd optctrl -c=1 -dst=2 Step 2 The property of the RAID Controller changes after the setting has been changed successfully.
Checking Location of Physical Device The locate function can be used when you want to know the slot to which a specific Physical Device appearing in the RAID Viewer is inserted in the server or enclosure. In actual, locate turns on the DISK lamp on the server or enclosure in which the specified Physical Device is installed. (The DISK lamp blinks depending on the types of the server or enclosures.
Changing Status of Physical Device Forcibly The function of changing status of a Physical Device forcibly can be used when you want to change the Status of a Physical Device to Online or Failed forcibly for a maintenance job or another. The function may not be used in normal operation. The function of changing the status of a Physical Device forcibly is available only in the Advanced Mode. The system may not start if you forcibly change the status of the Physical Device used for the system drive.
raidcmd Step 1 Execute "stspd" command with -st option and the following parameters. -c : Number of the RAID Controller containing the Physical Device with its status set to Online forcibly -p : Number of the Physical Device with its status set to Online forcibly -st : Specify "online" Ex. Make the Physical Device (RAID Controller Number: 1 and Physical Device Number: e252s4) Online forcibly. raidcmd stspd -c=1 -p=e252s4 -st=online Step 2 Displays the Warning message and the confirmation message.
raidcmd Step 1 Execute "stspd" command with -st option and the following parameters. -c : Number of the RAID Controller containing the Physical Device with its status set to Failed forcibly -p : Number of the Physical Device with its status set to Failed forcibly -st : Specify "offline" Ex. Set the Physical Device (RAID Controller number: 1 and Physical Device number: e252s4) to Failed. raidcmd stspd -c=1 -p=e252s4 -st=offline Step 2 Displays the Warning message and the confirmation message.
Refreshing the battery of the RAID Controller The Battery Refreshing is a function to refresh the battery connected to the RAID Controller. The function restores the battery degraded due to charge and discharge. Universal RAID Utility provides the function to manually execute the battery refreshing. The function can be done for each RAID Controller. You can use a Windows task scheduler to do a regular battery refreshing. Some types of RAID Controller do not support Battery Refreshing.
raidcmd Step 1 Execute "refresh" command using the following parameter. -c : Number of RAID Controller for which Battery Refresh is set. > raidcmd refresh -c=2 Refresh the battery. 1 Do you continue ? [yes(y) or no(n)] :yes > 2 Ex) Refresh the battery (RAID Controller number: 2). raidcmd refresh –c=2 Step 2 Execute the "refresh" command to display the confirmation message. Enter [Yes] to execute battery refreshing. Enter [No] to cancel battery refreshing.
Troubleshooting RAID System This chapter describes the troubleshooting of a RAID System done by using the Universal RAID Utility. The Universal RAID Utility provides various measures to monitor occurrences of failures in the RAID System. The figure below shows the image of the troubleshooting function provided by the Universal RAID Utility.
Failure Detection Measures The Universal RAID Utility provides several fault detection measures as shown in Figure 23 Troubleshooting image of RAID System. The measures are described below. Status Display by RAID Viewer The RAID Viewer indicates the status of the RAID System with the icons of components on the Tree View and the [Status] in the Property tab of each component. For details of the icons of components on the Tree View, see "Tree View".
Windows [Example 1] When Logical Drive 2 on RAID Controller 1 is degraded. Item Description Indicates event ID. The four numeric characters after “RU” is an event ID. CTRL:1(ID=0) Indicates RAID Controller number. The example “CTRL:1(ID=0)” indicates the RAID Controller of which the RAID Controller number is 1 and ID is 0. LD:2(ID=1) Indicates Logical Drive number. The example “LD:2(ID=1)” indicates Logical Drive number 2 and ID 1.
Linux and VMware ESX [Example 1] When Logical Drive 1 on RAID Controller 2 is degraded. - Jun 27 18:49:04 localhost raidsrv[27370]: [CTRL:2(ID=1) LD:1(ID=0)] Logical Drive is Degraded. Item Description raidsrv Indicates the process name of Universal RAID Utility Indicates event ID. The four numeric characters after “RU” is event ID. CTRL:2(ID=1) Indicates the RAID Controller number.
raidcmd Step 1 Execute raidcmd without command to check the component where a failure occurs. Step 2 Execute "sbuzzer" command with the following parameter. 2 > raidcmd sbuzzer -c=1 > -c : Number of the RAID Controller for which Buzzer is stopped Ex.
ESMPRO User Group is the name group for the management of NEC ESMPRO Manager (specified it when installed NEC ESMPRO Manager). If you forget the name of group, see the following registry key.
Operation in no failures of Physical Devices If all Physical Devices used by a Logical Drive operates normally (with their [Status] being [Online]), the Logical Drive is in the online status (with its [Status] being [Online]).
Operation when redundancy of Logical Drive degraded or lost due to failure of Physical Device If one or more Physical Devices used by a Logical Drive are failed (with their [Status] being [Failed]) to degraded (one Physical Device of RAID Level 6 is failed) or lost (one Physical Device of RAID Level 1 or 5 is failed, two Physical Devices of RAID Level 6 is failed) the redundancy of the Logical Drive, the Logical Drive is degraded (with its [Status] being [Degraded]).
Operation when failed Physical Device is replaced to recover RAID System Using the RAID System continuously with the redundancy of a Logical Drive remaining degraded may cause the data in the Logical Drive to be lost when another Physical Device is failed further. Recover a Logical Drive of degraded redundancy by Hot Spare or replacement of the failed Physical Device.
Operation when the Logical Drive is offline due to failure of Physical Device If you continue to use the RAID System with lost redundancy of a Logical Drive and another Physical Device is failed further, the redundancy of the Logical Drive is lost completely (two or more Physical Devices of RAID Level 1 or 5 is failed, three or more Physical Devices of RAID Level 6 is failed). The status of a Logical Drive without redundancy is offline (with its [Status] being [Offline]).
Monitoring Battery Status The Universal RAID Utility can monitor Battery status which the RAID Controller detects by the following means. RAID Viewer raidcmd RAID Log Buzzer OS Log Alert Depending on type of RAID Controller The Universal RAID Utility monitors events of the Battery installed in the RAID Controller. The Universal RAID Utility logs detected Battery events in the RAID Log.
Monitoring Enclosure Status The Universal RAID Utility can monitor enclosure status which the RAID Controller detects by the following means. RAID Viewer raidcmd RAID Log Buzzer OS Log Alert Depending on type of RAID Controller The Universal RAID Utility monitors events of the enclosure detected by the RAID Controller. The Universal RAID Utility logs detected enclosure events to the RAID Log.
Tree View of RAID Viewer The status of the node of Physical Device becomes [Warning] when S.M.A.R.T. error is detected. Become [Warning] by existence of [Warning] node. Physical Device which detected S.M.A.R.T. error [Warning] Property of RAID Viewer The [S.M.A.R.T.] of Physical Device Properties becomes [Detected] when S.M.A.R.T. error is detected. Physical Device which detected S.M.A.R.T. error [Detected] Property of raidcmd The [S.M.A.R.T.] of Physical Device Properties becomes [Detected] when S.M.
Management of RAID System using NEC ESMPRO Manager You can browse, monitor, or operate the RAID System that is managed by Universal RAID Utility using NEC ESMPRO Manager after registering the server as the target server to be monitored by NEC ESMPRO Manager. See the instruction of NEC ESMPRO Manager about system requirements and how to use. This chapter describes the point that should be noted when the RAID System is managed by using NEC ESMPRO Manager.
Function that can be used in NEC ESMPRO Manager You can use the following functions ("Usable" is "") with the RAID System Management function. .
Using ExpressUpdate Universal RAID Utility supports ExpressUpdate. This feature enables you to install, update, and uninstall Universal RAID Utility. This can enables you the version management of Universal RAID Utility. For details of the operation environment and procedure of ExpressUpdate, see the manual of ExpressUpdate. Functions supported by ExpressUpdate The functions supported in ExpressUpdate for Universal RAID Utility are installation, update, and uninstallation.
Changing of Settings of Universal RAID Utility This chapter describes how to change the settings of the Universal RAID Utility. Changing TCP port number If the TCP port number using Universal RAID Utility is same one of other application, you can change the TCP port number using Universal RAID Utility. A user having the administrator authority should change the TCP port number. Only users having the administrator authority can change the TCP port number.
Using Linux or VMware ESX as Operating System Step 1 Log in to the computer as a user having the administrator authority. Step 2 Abort the raidcmd if it is used. Step 3 Stop raidsrv service. If the RAID System is managed by NEC ESMPRO Manager Ver. 5.5 or later, raidsrv Agent service and eciService will also be stopped. > /etc/init.d/raidsrv stop Stopping raidsrv services: > > /etc/init.d/raidsrv_agent stop Stopping raidsrv_agent services: > > /etc/init.
Changing RAID System Management Mode at Start of RAID Viewer The RAID Viewer is started in the Standard Mode by default. The setting can be changed so that the RAID Viewer is always started in the Advanced Mode as described below. Step 1 Start the RAID Viewer. Click [Option] on the [Tool] menu. Step 2 Check the [Always start with an Advanced Mode] check box in the [General] tab of the [Option] dialog box.
Notes on Use of Universal RAID Utility This chapter describes the notes on use of the Universal RAID Utility. Operation Environment Use of IPv6 The Universal RAID Utility cannot operate in the IPv6 (Internet Protocol version 6) environment. Use the Universal RAID Utility in the IPv4 environment. To manage a RAID System in the IPv6 environment, use the BIOS utility of the RAID Controller. Support for Solid State Drive (SSD) The RAID Viewer and raidcmd of Universal RAID Utility Ver2.
OS Fatal Error Event The event “OS Fatal Error” is registered if the contiguous memory that is required for Universal RAID Utility operation cannot be reserved on the operating system. It may be caused by the lack of system memory or free space. You must resolve the root cause. After the problem is resolved, check "Updating Information of RAID System” to update the RAID system configuration. If you cannot update the RAID system information, restart the raidsrv service.
RAID Viewer, Log Viewer Verification of Authenticode signature at the startup of the RAID Viewer and Log Viewer RAID Viewer and Log Viewer have an Authenticode signature. When you start the Microsoft .NET Framework Version 2.0 managed application that has an Authenticode signature, .NET Framework Version 2.0 verify the validation of Authenticode signature.
About the start when Runtime component of Microsoft Visual C++ 2005 SP1 library does not exist RAID Viewer fails in the start if it doesn't install Runtime component of Microsoft Visual C++ 2005 SP1 library. 1. When Runtime component of Microsoft Visual C++ 2005 SP1 library does not exist The message dialog to show the occurrence of the problem is displayed, because the DLL of Runtime component of Microsoft Visual C++ 2005 SP1 library cannot be loaded.
