FUJITSU RAID Manager User Guide

FUJITSU Software ServerView Suite ServerView RAID Manager is a software suite that allows you to manage RAID controllers and the devices attached to them. It supports all current variants from the different vendors, including SCSI, SATA, and SAS. ServerView RAID Manager also supports RAID controllers on the mainboard and the expansion boards, and solutions with corresponding implementation. It offers only those administrative options which are actually supported.

PDF

Document

User Guide - English

FUJITSU Software ServerView Suite

ServerView RAID Manager

Edition June 2015

Copyright and trademarks

Delivery subject to availability; right of technical modifications reserved.

All hardware and software names used are trademarks of their respective manufacturers.

1 Basics

..................................................................................................................

1.1 Supported RAID Levels

.................................................................................

1.2 RAID Controller Functions ............................................................................. 5

1.3 Supported Controllers and Devices

..............................................................

2 Login

...................................................................................................................

2.1 Installation .................................................................................................... 8

2.2 Login

..........................................................................................................

2.3 Security Certiﬁcate

.....................................................................................

2.4 System requirements

.................................................................................

2.5 Licenses

.....................................................................................................

3 The User Interface

..........................................................................................

3.1 Elements of the User Interface

...................................................................

3.2 Event Status Indicators and Icons

..............................................................

4 Properties

........................................................................................................

4.1 Displaying and Modifying Properties

..........................................................

5 Actions and Dialogs

........................................................................................

5.1 Executing Actions

.......................................................................................

5.2 Creating Logical Drives

..............................................................................

5.3 Modifying Logical Drives (migrating)

..........................................................

5.4 Processing Hot Spares

................................................................................

5.5 Foreign Conﬁguration

.................................................................................

5.6 Task

............................................................................................................

6 Events

...............................................................................................................

6.1 Displaying Events

.......................................................................................

6.2 Events / SNMP Traps

...................................................................................

6.3 Errors

........................................................................................................

106

7 Help

.................................................................................................................

111

7.1 Help

..........................................................................................................

111

7.2 Online Help

...............................................................................................

111

7.3 amCLI

.......................................................................................................

112

7.4 Frequently Asked Questions - FAQs

..........................................................

121

8 Glossary

..........................................................................................................

123

RAID Management

1 Basics

1.1 Supported RAID Levels

RAID is an acronym ﬁrst deﬁned in 1987 by researchers of the University of California, Berkeley as "Redundant Array of Inexpensive

Disks". This storage technology allows a combination of multiple low-cost disk components into logical units (logical drives). A so called

"RAID level" describes how data is distributed over the various disks of a logical drive. These distribution algorithms determine the balance of increasing data reliability through redundancy and/or increasing performance through parallel input/output transactions.

For marketing reasons the deﬁnition of RAID was later replaced by RAID manufacturers with the term "Redundant Array of

Independent Disks". RAID technology should not be subject to a "low cost" expectation.

RAID is now a collective name for computer data storage schemes that can divide and replicate data among multiple disks.

The diﬀerent RAID levels are named by the word RAID followed by a number, as in RAID-0, RAID-1, etc. A brief description of the best known RAID levels the controllers supported by ServerView RAID can conﬁgure follows:

1.1.1 RAID-0

A RAID-0 is created by distributing (striping) data over two or more disks. Single striping (like that just mentioned) does not generate any redundancy for protecting data, but by distributing the data over multiple drives it provides the best read/write performance of all

RAID types.

1.1.2 RAID-1

A RAID-1 consists of two disks. The data stored on the array is written to both drives. The mirroring of data provides a redundancy which ensures that no data is lost if one drive fails. However, only half the total capacity of the two disks is available because all data is written to both drives.

In comparison with a single drive RAID-1 oﬀers no beneﬁts in terms of write performance, but because the data is distributed over two drives it provides advantages in read performance (and data security).

RAID Management 1

1.1.3 RAID-1E

A RAID-1E consists of at least three drives. Some controllers require a conﬁguration with an even drive count, e.g. MegaRAID SAS.

Individual data blocks are mirrored onto the next disk (replication), and RAID-1E consequently oﬀers better failsafe performance than

RAID-1. However, neither two adjacent nor the ﬁrst and last disks may fail simultaneously.

1.1.4 RAID-5

At least three drives are required to create a RAID-5. As with a RAID-0 the data is distributed over various drives, but in the case of

RAID-5 the capacity of a drive is used to store parity information. The parity information is also distributed over all the drives. The controller generates this parity whenever data is written to the array and distributed over all the drives. If a drive fails, the content of the failed drive can be restored from the data and the parity of the remaining drives.

The use of parity minimizes the capacity costs of redundancy. As only one drive is used to store the parity, two thirds of the total capacity (in a 3 disk conﬁguration) can still be used for data. In the case of arrays with more disks the reduction of the usable total capacity is less. With RAID-5 the write performance is lower because parity data must ﬁrst be generated for each write process. The read performance is good, however, because the requests are distributed over all drives.

2 RAID Management

1.1.5 RAID-6

A RAID-6 requires at least four disks and functions in a similar way to a RAID-5, but can handle the failure of two disks. Some RAID controllers also offer a 3 disk configuration for RAID-6. Parity on 2 disks equals a double mirroring of data. In the case of a RAID-6 two pieces of parity information are calculated instead of one and these are distributed over all drives on a stripe-by-stripe basis. This is why a RAID-6 offers the highest level of security. Write access is a little slower than with RAID-5.

1.1.6 RAID-10

A RAID-10 is a dual-level array which is created by two or more equal-sized arrays of the type RAID-1 being used to produce a

RAID-0. A top-level array (RAID-0) shares the total data load with the second-level array (RAID-1), thus enhancing both the read and the write performance. As second-level arrays are RAID-1s, redundancy is also oﬀered. However, only half the total capacity of the drives used is available in the array.

RAID Management 3

1.1.7 RAID-50

A RAID-50 is a dual-level array which is created by using at least two arrays of the type RAID-5 to form a RAID-0. The top-level array

(RAID-0) shares the data with the second-level array (RAID-5), thus enhancing both the read and the write performance. Since the second-level arrays use RAID-5, the parity provides eﬃcient redundancy.

1.1.8 RAID-60

A RAID-60 is a dual-level array which is created by means of at least two arrays of the type RAID-6 in order to form a RAID-0. The uppermost array (RAID-0) shares the data with the array on the second level (RAID-6), which increases the read and write accesses.

Using RAID-6 on the second level also guarantees a high degree of data security.

4 RAID Management

1.1.9 Single Volume, JBOD

A single volume consists of a single disk. In the actual sense of the word this is not a real RAID type and is thus also referred to as a

"none-RAID". According to the latest deﬁnition of the Storage Networking Industry Association a JBOD (Just a Bunch of Disks) is one of these although the term can sometimes refer to multiple physical disks.

1.1.10 Concatenation

A concatenation is formed by interconnecting two or more disks. In this case the drives can have different capacities and are interconnected from beginning to end. A global volume offers no redundancy and no performance benefits compared to a single drive; it is seen in the system merely as a correspondingly large drive.

1.1.11 RAID Volume

A RAID volume is created by interconnecting two or more arrays of the same type. In contrast to the dual-level arrays described above, arrays in a RAID volume need not have the same capacity but are interconnected (as described above under concatenation).

Note: Sometimes the term "volume" is also used as a synonym for array.

1.2 RAID Controller Functions

In the context of RAID terms are used and functions described which are explained in detail below.

1.2.1 Embedded RAID / Host RAID

"Embedded RAID" means hardware (ASIC) is provided on the RAID controller which relieves the system CPU (host) of RAID controller functions. As a result the server can devote itself to processing its core applications and the overall performance is improved. If this hardware support is not available, the term "host RAID" is used.

1.2.2 Drive Usage

For simplicity's sake the diﬀerent RAID types under Supported RAID Levels all use complete disk drives of the same size. In fact the usable capacity of each drive is limited by the disk drive with the lowest capacity if drives with diﬀerent capacities are used.

If, for example, a RAID-1 is created from a 160-Gbyte and an 80-Gbyte drive, only half the capacity of the larger disk can be used, thus limiting it to 80-Gbyte. Furthermore, a small part is removed from each drive for the so-called RAID Signature.

1.2.3 RAID Signature

RAID controllers use a small segment at the beginning or end of each connected drive to store information on the drives and arrays attached to the controller. This segment is also referred to as RAID Signature and is not available for general use for saving user data.

1.2.4 Migration

Some RAID controllers support the modiﬁcation of existing logical drives through expansion options, migration of one RAID type to another, and modiﬁcation of the stripe size. The migration options depend on the RAID controller used.

Further information is provided under Modifying Logical Drives.

1.2.5 Online Capacity Expansion

Most operating systems of today support Online Capacity Expansion (OCE). OCE means that the additional capacity after a logical drive has been expanded can be used without rebooting the system. Details on the additional storage capacity are provided in the documentation for your operating system.

1.2.6 Cabinets

RAID controllers also support external drive enclosures which use SES or SAF-TE enclosure administration hardware. This extended hardware support enables additional administrative information for the enclosure, e.g. fan speed, temperature and voltage. Such enclosures generally oﬀer further properties, e.g. hot swap.

RAID Management 5

1.2.7 Hot Swap

Either through the use of SATA technology or the above-mentioned drive enclosure RAID controllers support so called hot swap, i.e.

disk drives can be replaced during ongoing operation without the system having to be rebooted.

Note: Hot swapping of hard disks is possible only if a disk was placed Oﬄine beforehand.

1.2.8 Hot Spare

A hot spare is a physical drive which is available in a redundant logical drive as a replacement for a failed disk. If a drive fails the hot spare replaces it and the logical drive is recreated. The data is then reconstructed on this new disk during ongoing operation. Until reconstruction has been completed the access to the data takes a little longer but is possible at any time.

RAID controllers support the following hot spare types:

Global hot spares support every logical drive for which the drive provides suﬃcient storage capacity for backup purposes.

Dedicated hot spares support only logical drives which it has been assigned to back up.

Note: Some RAID controllers automatically assign newly added and unused drives to the global hot spares.

1.2.9 Consistency Check/Make Data Consistent (MDC)

The consistency check operation veriﬁes correctness of the data in logical drives that use RAID levels 1, 5, 6, 10, 50, and 60. (RAID-0 does not provide data redundancy). For example, in a system with parity, checking consistency means computing the data on one disk and comparing the results to the contents of the parity disk.

Make data consistent (MDC) does not only verify the correctness of data but also attempts to correct inconsistent data automatically.

Note: It is recommended that you perform a consistency check at least once a month.

1.2.10 Copyback

The copyback feature allows you to copy data from a source disk of a logical drive to a destination disk that is not a part of the logical drive. Copyback is often used to create or restore a specific physical configuration for an array (for example, a specific arrangement of array members on the device I/O buses). Copyback can be run automatically or manually.

Typically, when a disk fails or is expected to fail, the data is rebuilt on a hot spare. The failed disk is replaced with a new disk. Then the data is copied from the hot spare to the new disk, and the hot spare reverts from a rebuild disk to its original hot spare status. The copyback operation runs as a background activity, and the logical drive is still available online to the host.

Copyback is also initiated when the ﬁrst Self-Monitoring Analysis and Reporting Technology (SMART) error occurs on a disk that is part of a logical drive. The destination disk is a hot spare that qualiﬁes as a rebuild disk. The disk with the SMART error is marked as failed only after the successful completion of the copyback. This avoids putting the array in degraded status.

1.2.11 Background Initialization (BGI)

Background initialization is a consistency check that is forced when you create a virtual drive. This is an automatic operation that starts 5 minutes after you create the virtual drive.

Background initialization is a check for media errors on the disks. It ensures that striped data segments are the same on all disks in a drive group. The default and recommended background initialization rate is 30 percent. Before you change the rebuild rate, you must stop the background initialization or the rate change will not aﬀect the background initialization rate.

1.2.12 Patrol Read

Patrol read involves the review of your system for possible disk errors that could lead to disk failure and then action to correct errors.

The goal is to protect data integrity by detecting disk failure before the failure can damage data. The corrective actions depend on the array conﬁguration and the type of errors.

Patrol read starts only when the controller is idle for a deﬁned period of time and no other background tasks are active, though it can continue to run during heavy I/O processes.

1.2.13 MegaRAID® CacheCade™ Pro 2.0

MegaRAID CacheCade Pro 2.0 read/write software eliminates the need for manually conﬁgured hybrid arrays by intelligently and dynamically managing frequently accessed data and copying it from HDD volumes to a higher performance layer of SSD cache.

Copying the most accessed data (‘hot spot’) to ﬂash cache relieves the primary HDD array from time-consuming transactions which

RAID Management

allows for more efficient hard disk operation, reduced latency, and accelerated read and write speeds. This provides significant improvements to overall system performance – two to twelve times that of HDD–only configurations – for a wide variety of server applications including web, file, online transaction processing (OLTP) database, data mining and other transaction-intensive applications.

1.2.14 MegaRAID® FastPath™

MegaRAID FastPath software is a high-performance IO accelerator for SSD arrays connected to a MegaRAID controller card. This advanced software is an optimized version of MegaRAID technology that can dramatically boost storage subsystem and overall application performance – particularly those that demonstrate high random read/write operation workloads – when deployed with a

6Gb/s MegaRAID SATA+SAS controller connected to SSDs.

Application workloads that will beneﬁt most from MegaRAID FastPath software with SSD volumes are those with small and random IO patterns requiring high transactional throughput, such as OLTP.

1.3 Supported Controllers and Devices

ServerView RAID Manager permits administration of various RAID controllers and the devices attached to them.

1.3.1 Supported Controllers

ServerView RAID Manager supports all current variants from the diﬀerent vendors. This support covers SCSI, SATA, and SAS, as well as

RAID controllers on the mainboard and the expansion boards, and solutions with corresponding implementation and oﬀers only those administrative options which are actually supported.

Most controller functions which are supported are described in this online help. However, as not all controllers always support all functions and new functions may be added through new controllers or driver software updates, it is helpful also to refer to the release information for the controller concerned and the current release status of ServerView RAID Manager.

1.3.2 Supported SCSI Devices

In addition to SCSI hard disk drives SCSI RAID controllers also support tape drives.

1.3.3 Supported Serial ATA Devices

Serial ATA RAID controllers support only SATA hard disk drives.

1.3.4 Supported SAS Devices

Serial Attached SCSI replaces the previous parallel SCSI interface. SAS RAID controllers support both SAS and SATA hard disk drives.

Please take note of the relevant controller release information.

RAID Management 7

2 Login

2.1 Installation

If ServerView RAID Manager is not installed automatically during setup with the ServerView Installation Manager or you would like to use RAID management without the whole ServerView Suite installed on your system you can install ServerView RAID Manager independently.

2.1.1 General

If you have used or installed other programs for RAID management before ServerView RAID Manager is installed, you must uninstall them. Further information on this is provided in the relevant release notices.

Assuming that the current release of ServerView RAID Manager is Version 6.2.0, please perform installation as follows:

Open the console window (Linux/VMware) or Explorer (Windows) and navigate to the directory containing the current ServerView

RAID Manager installation package.

RHEL5-32

RHEL5-64

RHEL6-32

RHEL6-64

RHEL7-64

SLES11-32

SLES11-64

SLES12-64

ServerView_RAID-6.2-0.el5.i386.rpm

ServerView_RAID-6.2-0.el5.x86_64.rpm

ServerView_RAID-6.2-0.el6.i686.rpm

ServerView_RAID-6.2-0.el6.x86_64.rpm

ServerView_RAID-6.2-0.el7.x86_64.rpm

ServerView_RAID-6.2-0.sles11.i586.rpm

ServerView_RAID-6.2-0.sles11.x86_64.rpm

ServerView_RAID-6.2-0.sles12.x86_64.rpm

Windows 32 bit ServerView_RAID.msi

Windows 64 bit ServerView_RAID_x64.msi

For initial installation under Linux RHEL6-64 please enter rpm -ivh ServerView_RAID-6.2-0.el6.x86_64.rpm. An update installation is performed using rpm -Uvh ServerView_RAID-6.2-0.el6.x86_64.rpm. You can also delete the older version beforehand. To do this, enter rpm -e ServerView_RAID. You can then proceed as for initial installation. The procedures are all started by pressing the Enter key.

On a Windows system you start the update/installation by double-clicking on the installation package. Follow the installation instructions which you are oﬀered in the dialog boxes.

During installation on windows system, you can select installation type from the following 3 types:

• Standard

• Complete

• Custom

As for "Standard" and "Complete", components to be installed are identical, that is, every useful component will be automatically selected and installed. With "Custom", you can choose which hardware supports and/or SNMP support to be installed as you want. Since most components are enabled in "Custom" by default, you need to deselect unnecessary items before proceeding your installation process.

Note: When you are going to do upgrade installation, you must follow the same installation type and components you chose when installing previous version.

The Core Editions of Windows Server 2008 and newer provide a command line interface only. To install ServerView RAID Manager on these operating systems use the following command line: msiexec SERVICES=start REBOOT=ReallySuppress ALLUSERS=1 /i

ServerView_RAID.msi /qr. Instead of ServerView_RAID.msi on 32-bit versions use ServerView_RAID_x64.msi on 64-bit versions.

RAID Management

To monitor RAID controllers of VMware ESXi servers you have to conﬁgure some settings after installation of ServerView RAID

Manager (see VMware ESXi below).

If you want to work with the graphical user interface of ServerView RAID Manager and the Java Runtime Environment (JRE) has not yet been installed, it may be necessary to install a current Java Runtime Environment on your client.

To ﬁnd out which combination of web browser and Java plugin can be used read the documentation of your web browser and the information provided by Oracle on java.com.

If there is no Java plugin available for a speciﬁc 64-bit web browser then prepare a 32-bit web browser environment.

Please bear in mind that you are personally responsible for compliance with the license terms.

To communicate with ServerView RAID Manager web browsers use an HTTPS connection (i.e. a secure TLS connection). Therefore

ServerView RAID Manager needs a certificate (X.509 certificate) to authenticate itself at the web browser. During installation a self-signed certificate is created automatically. When connecting to ServerView RAID Manager the browser will issue a certificate error with suggestions how to proceed. To fulfill high-level security requirements typical for enterprise usage this self-signed certificate can be replaced by a certificate that is signed by a trusted Certificate Authority. Use amCLI to import such a certificate.

Example syntax:

amCLI -i <certificate file> <private key file>

To check which version of ServerView RAID Manager is installed you can do the following:

Under Linux the rpm -qa command (entry on the console) outputs a list of all the installed RPM packages. If ServerView RAID

Manager is installed, you are shown the package with the current version, for example ServerView_RAID-6.2-0.

Under Windows you are shown the installation under Start > Settings > Control Panel > Add or Remove Programs.

To delete ServerView RAID Manager installation do the following:

Under Linux you can delete the installation of ServerView RAID Manager by executing the command rpm -e ServerView_RAID.

Under Windows you can delete the installation under Start > Settings > Control Panel > Add or Remove Programs.

The Core Editions of Windows Server 2008 and newer require execution of a command line again. Use wmic product where

name="Fujitsu Software ServerView RAID Manager" call uninstall to delete the installation.

RAID Management 9

2.1.2 VMware ESXi

On the Central Management Station (virtual or physical) with running ServerView RAID Manager use amCLI to add required server connection information for ESXi hypervisors to be managed.

Example syntax:

amCLI -e 21/0 add_server name=<FQDN or Hostname or IP> port=5989 username=root password=<ESXi root password>

This command adds an existing ESXi server to the ServerView RAID Manager conﬁguration. The FQDN or Hostname requires an entry in DNS otherwise use the IP address of the server. The username must be "root" (or any other with these rights) and the password must be the valid password of this user on the ESXi server. This is required ESXi information to connect to the CIMOM using https on port 5989.

Note: Passwords including characters that have a special meaning for the used command line interpreter must be escaped by suitable means (e.g. double quotes).

After adding a server it is recommended to check the conﬁguration and connection with amCLI –e 21/0 verify_server name=<FQDN or

Hostname or IP>. If the result is "Status: OK", conﬁguration and connection status are OK. Otherwise, please check the conﬁguration of the ESXi server.

For changes to the conﬁguration you can use amCLI -e 21/0 modify_server name=<FQDN or Hostname or IP> ... and to delete a server

amCLI -e 21/0 delete_server name=<FQDN or Hostname or IP> with the name which was used by add server. A list of conﬁgured servers can be seen by using the command amCLI -e 21/0 show_server_list. For more syntax details use amCLI -? exec 21/0.

Note: If the CMS is rebooted or shut down no monitoring of ESXi servers takes place.

On the start screen of ESXi you can invoke the menu Customize System. Ensure that the parameter Conﬁgure Lockdown Mode is set to

Disabled.

10 RAID Management

2.1.3 Registering trap information into SNMP manager

ServerView RAID Manager oﬀers its own MIB ﬁle RAID.mib (Windows) or FSC-RAID-MIB.txt (Linux/VMware/Solaris) in which its SNMP

trap information is deﬁned.

If you are planning to use your own SNMP manager to receive SNMP traps from ServerView RAID Manager, it is highly recommended to integrate this ﬁle into the SNMP manager beforehand. That way, traps from ServerView RAID Manager can be processed properly in the SNMP manager. Otherwise, some traps may be displayed as 'Unknown trap'.

You can ﬁnd the ﬁle in the following directory after installing ServerView RAID Manager:

On Windows systems:

C:\Program Files\Fujitsu\ServerView Suite\RAID Manager\bin\RAID.mib

On Linux systems:

/usr/share/snmp/mibs/FSC-RAID-MIB.txt

Note: Registering one of the ﬁles RAID.mib or FSC-RAID-MIB.txt is enough, since they have identical contents.

In case of registering FSC-RAID-MIB.txt into ServerView Operations Manager, it is necessary to rename the ﬁle into RAID.mib in advance. Please observe the letter case of the ﬁle name RAID.mib. ServerView Operations Manager is strictly case-sensitive.

Regarding more details how to register the ﬁle, please refer to your favorite SNMP manager's user guide. If you use ServerView

Operations Manager, please refer to "MIB Integration" of "ServerView Suite ServerView Event Manager" (sv-event-mgr-en.pdf).

Please observe the other ServerView RAID Manager system requirements also.

RAID Management 11

2.2 Login

You log in as follows:

ServerView RAID Manager must be installed on the system to be administered. If this has not been done, please install ServerView

RAID Manager.

Note: Under Windows you ﬁnd or start the local application by clicking on Start > Programs > Fujitsu > ServerView Suite > RAID

Manager > RAID Manager.

If ServerView RAID Manager is already installed on the target system, you can also start the RAID Manager directly via the browser

from an arbitrary client. In the address bar, enter the FQDN (Fully Qualiﬁed Domain Name) followed by TCP port number 3173 (e.g.

https://<FQDN>:3173). Conﬁrm your input using the CR key to get access to the desired system. This works both locally and from a remote system.

Note: If there is an intervening ﬁrewall in the environment, you need to conﬁgure the network settings so that the port used by

ServerView RAID Manager will not be blocked.

Note: When you run ServerView RAID Manager for the first time after installation, you must install a security certificate. Information on doing this is provided under Security Certificate.

If you have not turned on Single Sign On and Role Based Access Control the following login screen is displayed in the browser, after a connection has been successfully set up to the system.

Note: By the Help button at the top right the online help can be opened directly without the user needing to log in.

If required, choose a diﬀerent language in the login screen by selecting the related national ﬂag.

Enter the user name and the password which are to be used to log into this system. Then click on Login to enter ServerView RAID

Manager.

12 RAID Management

For authentication and authorization purposes ServerView RAID Manager uses the interfaces provided by the operating system of the server to be monitored. Users who have been set up with administration rights can perform conﬁguration via ServerView

RAID Manager. Non-privileged users can obtain a read-only view of the RAID conﬁguration on the server as well as get write access rights for ServerView RAID Manager.

To grant certain users without administration rights the possibility to take over conﬁguration tasks or a read-only access, this can be done as follows:

RAID administrators

A user with write access rights for ServerView RAID Manager can be set up by creating a new user group with the name "raidadm" (default) and adding an existing user to this group.

RAID observers

A read-only user can be set up by creating a new user group with the name "raid-usr" (default) and adding an existing user to this group.

To get more ﬂexibility the names for the two user groups described above can be freely deﬁned by editing the properties

Admin group and User group. These properties can be found on the Settings tab of System category. If no group name is given there will be no check for membership in a user group during authentication. The settings are activated immediately.

On Windows the search order for group membership is ﬁxed. First the local user groups of the system are checked, then the global groups in an active directory, and ﬁnally the local groups in an active directory.

On Linux the search order is defined in PAM configuration. On systems with very restrictive access control it may be necessary to configure PAM access by editing /etc/security/access.conf additionally.

All other users even though they can authenticate at the server have no authorization for the ServerView RAID Manager functionality.

The ﬁrst user automatically has read/write authorization. Every subsequent user only has read authorization, but – provided they have appropriate administration rights – can obtain write authorization. The user who had write authorization up to this point is then informed of this.

RAID Management 13

2.2.1 Client / Browser Conﬁguration

Please check and if necessary change the following settings for

Internet Explorer:

Enable an encrypted communication by

Tools > Internet Options > Advanced > Security and enable Use TLS 1.0, Use TLS 1.1, or Use TLS 1.2.

Add zone settings of browser as following:

Select Tools > Internet Options.

Click Security tab, and select Local intranet or Trusted sites.

Click Sites and add the server URL where ServerView RAID Manager is installed (https://<FQDN>).

Click Close.

Click Custom level....

Set ActiveX controls and plug-ins to Enable.

If you use a proxy server for the Internet you must bypass it to enable you to access the server. If you know the IP address of the system that you wish to administer remotely, you might select the following, for example, for

Internet Explorer:

Tools > Internet Options > Connections > LAN/Settings… > Use a proxy server for your LAN/Advanced… and enter the IP address of the system to be administered in the Exceptions area.

Netscape/Firefox:

Edit > Settings > Advanced > Proxy Server > Manual Proxy Server Conﬁguration > No Proxy and enter the IP address of the system to be administered.

Do not use "Back", "Forward", or "Refresh" button of the browser.

There is no working web browser in Core Editions of Windows Server 2008 and newer installations.

To manage RAID controllers, prepare a client as described as follows and in System requirements and use ServerView RAID

Manager on it.

14 RAID Management

2.2.2 Single Sign On and Role Based Access Control

If your server management environment is built around ServerView Operations Manager 5.0 or newer and the Single Sign On infrastructure (CAS - Central Authentication Service) and directory services extensions for Role Based Access Control (RBAC) are conﬁgured you can participate with ServerView RAID Manager.

After the ﬁrst login to ServerView RAID Manager as described above switch to the Settings tab of your system where you can enable

CAS and RBAC.

Edit either the CAS or the LDAP entry to enabled. Both entries are related at the moment so if you turn on CAS the setting for LDAP will be enabled automatically.

After turning on CAS and LDAP do not logout from ServerView RAID Manager until connection to CAS and LDAP is working correct or CAS and LDAP are turned oﬀ again. Otherwise you will not be able to login again.

If CAS and LDAP are mistakenly enabled with incorrect settings it is possible to turn them oﬀ again by using amCLI:

amCLI -s 21/3 CAS disabled

RAID Management 15

If you have enabled CAS and LDAP you see a few properties that have to be adapted to the existing environment. This information is available on the Central Management Station (CMS) where ServerView Operations Manager is installed.

Up to and including version 6.00 of ServerView Operations Manager open the following ﬁle on that system in your favorite editor:

On Windows systems:

<ServerView directory>\jboss\server\serverview\conf\sv-sec-conﬁg.xml

On Linux systems:

/opt/fujitsu/ServerViewSuite/jboss/server/serverview/conf/sv-sec-conﬁg.xml

Starting with version 6.10 of ServerView Operations Manager JBoss 7 is used. Open the following ﬁle on that system in an editor:

On Windows systems:

<ServerView directory>\jboss\standalone\svconf\sv-sec-conﬁg.xml

On Linux systems:

/opt/fujitsu/ServerViewSuite/jboss/standalone/svconf/sv-sec-conﬁg.xml

The XML tags in that ﬁle approximately match the properties in the Settings tab of ServerView RAID Manager. Change the properties accordingly.

CAS:

CAS server

CAS port

CAS base URL

LDAP:

LDAP server

LDAP port

Base DN

User search base

User search ﬁlter

Role DN

Username

Password

...

<cms>

<serverUrl>https://

<system_name>

3170

</serverUrl>

</cms>

<cas>

/cas

</contextRoot>

<uriLogin>/login</uriLogin>

<uriServiceValidate>/serviceValidate</uriServiceValidate>

<uriInsertTgt>/Insert/TGT</uriInsertTgt>

</cas>

</authentication>

<serverUrl>ldaps://

<system_name>

1474

</serverUrl>

dc=fujitsu,dc=com

</baseDN>

ou=users,dc=fujitsu,dc=com

</userSearchBase>

uid=%u

</userSearchFilter>

OU=SVS

</serverViewRDN>

cn=svuser,ou=users,dc=fujitsu,dc=com

</securityPrincipal>

<password>

</securityCredentials>

</ldapServer>

</authorization>

...

The names of the conﬁgured servers must match exactly.

In newer version of ServerView Operations Manager the securityCredentials entry is encrypted. Ask your ServerView

Operations Manager administrator for the password.

To test the connection to CAS you can execute the action "Test CAS connection". To test the connection to the directory service it is best practice to allow an unsecure communication ﬁrst. Enable property "Allow non-secure access" and set port as conﬁgured. Now execute action "Test LDAP connection".

If both tests pass you have to set up the environment for secure connection to the directory service. You need a certificate file from the Central Management Station. This file can be either obtained manually or downloaded from the CMS.

16 RAID Management

The ﬁle containing the certiﬁcate can be found in the following directory on the CMS:

On Windows systems:

<ServerView directory>\svcommon\data\download\pki

On Linux systems:

/opt/fujitsu/ServerViewSuite/svcommon/data/download/pki

To download the ﬁle direct your browser to https://<system_name>:3170/Download/pki/ where you have to login by Central

Authentication Service. Then store the certificate file <system_name>.scs.pem on your local system import it into your system's certificate store.

On Windows systems follow these steps to import the certiﬁcate:

Click Start, click Run, type mmc, and then click OK.

On the File menu, click Add/Remove Snap-in, and then click Add.

In the Add Standalone Snap-in dialog box, click Certiﬁcates, click Add, click Computer account, click Next, and then click Finish.

Click Close, and then click OK.

Expand Certiﬁcates (Local Computer), expand Trusted Root Certiﬁcation Authorities.

Right-click Certiﬁcates, click All Tasks, click Import, and then click Next.

In the File name box, type the file name or browse for your stored certificate file, and then click Next.

Click Finish, and then click OK.

On Linux systems you need to copy the certificate file into the CA certificate directory (often /etc/ssl/certs/) and reindex all certificates with "c_rehash".

RAID Management 17

After successful installation return to ServerView RAID Manager, disable the unsecure access to LDAP, and execute "Test LDAP

connection" again. If CAS and LDAP connection tests were successful ServerView RAID Manager is now prepared to participate in

Single Sign On and Role Based Access Control.

If you logout now the following screen will be displayed:

After clicking the link on the right side of the logout screen the login screen from CAS will be displayed:

RAID Management

2.3 Security Certiﬁcate

If you do not install a security certiﬁcate when ServerView RAID Manager is installed, you can do so the ﬁrst time you start it. Proceed as follows to do this depending on your browser and client.

Open your browser and enter the server name (FQDN) of the system followed by TCP port number 3173 into the address bar (e.g.

https://<FQDN>:3173). Conﬁrm your input using the CR key to get access to the desired system.

2.3.1 Internet Explorer 10

Open the browser Tools > Internet Options and select the Trusted sites zone on the Security tab. Click the Sites button, conﬁrm the URL matches, and click Add then Close. Close the Internet Options dialog with OK. Afterwards refresh the current page.

If the browser issues the message There is a problem with this website's security certiﬁcate, click Continue to this website (not

recommended).

Now a Security Warning dialog will be displayed. Conﬁrm that the URL matches your server name, and click Continue.

The Java Runtime Environment requests you to accept the ServerView RAID Manager applet – either once for the current session or, by enabling the Do not show this again for apps from publisher and location above option beforehand, also for subsequent sessions.

Conﬁrm by clicking on Run. In doing so you agree to an encrypted exchange of data and you are then shown the login screen.

In addition to the address bar of your browser, you will see Certiﬁcate Error. Click on this and then on View Certiﬁcates.

In the next window, Certiﬁcate, click on Install Certiﬁcate.

In the window then displayed, Certiﬁcate Import Wizard, click on Next.

The content of the Certiﬁcate Import Wizard window changes. Choose the Place all certiﬁcates in the following store setting and then click Browse.

10.

The appearing Select Certificate Store window will ask you where to save the certificate. Select the Trusted Root Certification

Authorities store and click OK.

11.

Then you return to the Certiﬁcate Import Wizard window from step 9. Click on Next.

RAID Management 19

12.

The content of the Certiﬁcate Import Wizard window is changed again. Click on Finish.

13.

A Security Warning window is displayed. Conﬁrm this by clicking on Yes.

14.

In the next window of the Certiﬁcate Import Wizard which is displayed click on OK, then dismiss the Certiﬁcate window with OK.

15.

After you have executed the steps described, close all instances of Internet Explorer, and restart your browser as described above under step 1.

2.3.2 Firefox 25

Click the I understand the risks link on the warning page that opens in Firefox when you come to this currently untrusted connection for the ﬁrst time.

Click the Add Exception button to open the Add Security Exception dialog.

On the Add Security Exception window, click on View, then select the Details tab to inspect the certiﬁcate and check the issuer.

Click on Export, then on the Save button. After saving the certiﬁcate to a ﬁle click on Close.

Now you can close the Add Security Exception window by clicking on Cancel.

On the upper left hand side of the Firefox browser window click on the orange tab to open the Options > Options menu.

Go to Advanced > Certificates tab, then click on the View Certificates button to view stored certificates.

Click the Servers tab, then the Import button.

10.

Select the certiﬁcate ﬁle saved in step 5 and click on Open.

11.

Select the imported certiﬁcate, then click on Edit Trust, followed by selecting Trust the authenticity of this certiﬁcate radio button.

12.

Click on Edit CA Trust to select at least the This certiﬁcate can identify websites option setting. Afterwards close this dialog by clicking OK.

13.

Close the Certiﬁcate Manager and then the Options dialog by OK, followed by closing all browser instances.

14.

Open Java Control Panel and select the Enable Java content in the browser on the Security tab.

15.

Click the Manage Certiﬁcates button to get to the Certiﬁcates dialog.

16.

Select the Secure Site certiﬁcate type in the top of the dialog, then click Import on the User tab.

17.

Select the certiﬁcate ﬁle saved in step 5 and click on Open again.

18.

Then click on Close, followed by OK to close all Java Control Panel dialogs.

19.

Finally restart your browser as described above under step 1 and conﬁrm the Java Runtime Environment requests as described above under step 5 of Internet Explorer 10.

20 RAID Management

2.3.3 Chrome 31

Click on the security padlock icon in the address bar of Chrome, then on the Connection tab. Here, you will ﬁnd a Certiﬁcate

information link. Click on it.

In the next window, Certiﬁcate, click on the Details tab, then on the Copy to File button.

Now the Certiﬁcate Export Wizard will be opened, click Next to get to the Export File Format screen.

Choose the DER encoded binary X.509 (.CER) format and click Next.

Click Browse, give the certiﬁcate ﬁle a descriptive name, and then Save it to your computer.

Click Next and Finish to proceed with the certiﬁcate export.

In the next window of the Certiﬁcate Export Wizard which is displayed click on OK, then dismiss the Certiﬁcate window with OK.

Open Chrome Settings, scroll to the bottom, and click the Show advanced settings link.

10.

Under the HTTPS/SSL section, click Manage certiﬁcates.

11.

In the following window click the Import button on the Trusted Root Certiﬁcation Authorities tab.

12.

In the window then displayed, Certiﬁcate Import Wizard, click on Next.

13.

Click Browse and select the certiﬁcate ﬁle saved in the steps before, click Open, then click Next.

14.

The content of the Certiﬁcate Import Wizard window changes and Place all certiﬁcates in the following store with Trusted Root

Certiﬁcation Authorities should be automatically selected, if not, follow step 9 and 10 of Internet Explorer 10 description.

15.

Then execute the steps 11-14 as described above under Internet Explorer 10, followed by closing all Chrome instances.

16.

Finally open Java Control Panel and follow the steps 14-19 as described above under Firefox 25.

If only a red X can be seen at the top left-hand corner of the screen when ServerView RAID Manager is started, this means that installation of the security certiﬁcate took too long. In this case close the browser window and restart ServerView RAID

Manager.

RAID Management 21

2.4 System requirements

2.4.1 Hardware

At least 80 MB of disk space must be available on the server for installation purposes. Depending on the settings for ServerView RAID

Manager, disk space must also be provided for the log ﬁles.

The client must be a PC that oﬀers at least 1 GHz processor and 1 GB RAM.

2.4.2 Software

On some Linux distributions it may be necessary to install additional software packages, e.g. pam, cyrus-sasl, etc.

Prerequisite for RAID management of VMware ESXi is at least ESXi 3.5 Update 2. The ESXi hypervisor only supports MegaRAID SAS controllers for management. It is recommended to run a Linux or Windows based virtual machine on each ESXi system and install

ServerView RAID Manager there.

A Java Runtime Environment (JRE) ≥ 1.5 or higher is required for the GUI.

The operating systems for the servers involved are the Windows, Linux, and VMware versions released by Fujitsu.

In addition to the server operating systems the following operating systems are supported as clients: Windows 7/8/8.1.

The browsers supported are Internet Explorer from version 7, Google Chrome from version 9, and Mozilla-based browsers such as

Netscape or Firefox.

2.4.3 Settings

The networking of the managed server must be conﬁgured so that the IP address of its hostname can be resolved either via DNS or the hosts database.

The hostname (FQDN) of the server must be compliant with the naming conventions deﬁned in RFC 952.

ServerView RAID Manager may only be used on the hardware and software speciﬁcally released for it. Further details can be found in the release information.

22 RAID Management

2.5 Licenses

RSA Data Security, Inc. MD5 Message-Digest Algorithm

This product includes software developed by the OpenSSL Project for use in the OpenSSL Toolkit. (http://www.openssl.org/)

This product includes cryptographic software written by Eric Young ([email protected]).

This product includes software developed by Computing Services at Carnegie Mellon University (http://www.cmu.edu/computing/).

This product includes software developed by the University of California, Berkeley and its contributors.

This product includes software developed by the University of Michigan at Ann Arbor

RAID Management 23

3 The User Interface

3.1 Elements of the User Interface

The ﬁgure below shows the ServerView RAID Manager main window with the typical controls.

Note: Depending on the operating system, browser, monitor, color scheme, and language used there may be diﬀerences between this ﬁgure and the display on your screen.

At the top of the window you will ﬁnd the 1st menu line with the menu items:

File

The menu item enables you to terminate your session and return to the login screen or to ServerView if you started the application there.

Actions

After selection diﬀerent actions will be oﬀered, depending on the object selected.

Language

About this menu item you can adjust another language variant.

Help

By means of the last menu item you can get additional information about ServerView RAID Manager or you can call this

online help.

Possible actions are displayed to you when you right-click on an object in the tree structure.

Below the 1st menu line you will ﬁnd the 2nd menu line. You can use the two arrows to go one step forward or back. The button next to the two arrows enables you to change the write or read access to the objects.

Beneath the two menu lines the window is divided into two halves. In the left-hand half all the objects of a system are displayed in a tree structure. In the right-hand half information on the objects selected in the tree structure are displayed in an object

window.

24 RAID Management

The object window on the right contains (depending on the object selected) one or more tabs:

General

Contains general data on an object (IP address, operating system, etc.) which you cannot change.

Settings

Contains object settings which you can change. When you click on the Edit button a dialog box opens in which you can make the changes.

Layout

Contains an overview with information on the structure of an object.

Background activities

Contains activities that are currently running on an object such as a Patrol Read on an adapter.

At the bottom edge of the user interface you will ﬁnd an event window. This displays the latest events of all the RAID controllers which are managed by ServerView RAID manager. The delimiter bar enables you to enlarge or reduce this window. A double click on an event opens a dialog, with which it is easy to navigate through the events and to catch the whole detailed message at a glance.

An overview of the icons used in the tree structure can be found here.

3.2 Event Status Indicators and Icons

3.2.1 Event Status Indicators

The following status indicators in the event window of the ServerView RAID Manager main window indicate the weight of a reported event.

Information Warning Error

3.2.2 Icons

The following icons represent an object (device) in the tree structure of the ServerView RAID Manager main window. This icons can also contain various combinable ﬂags which display the status or property of an object. An object without an additional indicator is always in the status OK.

3.2.2.1 Table of the object icons

Icon Meaning

Adapter

Icon Meaning

Power supply

BBU

Beeper

CacheCade

CD-ROM/DVD drive

Enclosure

Fan

File log

Hard disk (not used)

Hard disk (used)

Printer

Processor

SAS port

SATA port

Scanner

Scheduler/Hosts

SCSI channel

SSD (not used)

SSD (used)

RAID Management 25

Jukebox

Logical drive

Mail log

Multiplexer

Network device/ESXi server

Optical drive

Plugin

Switch

System

System log

Tape

Task

Temperature sensor

WORM drive

3.2.2.2 Table of the additional indicators

Indicator Example Meaning x character Fan in "critical" status

! character

Overﬂow

Foreign conﬁguration

Power supply in "warning" status

Logical drive where the bad block table has an overﬂow

Hard disk with foreign conﬁguration

Energy-saving state

Plus character (light background)

Plus character (gray background)

Yellow halo

1010 line of characters

Stopwatch

(Combination)

Hard disk in the energy-saving state

Global hot spare

Dedicated hot spare

Hard disk with "ﬂashing" LED status (in order to pinpoint it)

Hard disk is rebuilding

Hard disk is waiting

Logical drive with "warning" status is rebuilding

SSD with foreign conﬁguration and in the

"ﬂashing" and "critical" statuses

26 RAID Management

4 Properties

4.1 Displaying and Modifying Properties

Depending on the entry marked in the tree structure the following is displayed in the object window under the tab

General - the properties of the object in question which cannot be modiﬁed.

Settings - the properties of the object in question which can be modiﬁed. Clicking on the Edit button opens a dialog box in which you can make changes.

To make them easier to ﬁnd, the properties within the categories System, Devices and ServerView RAID Manager are listed in alphabetical order independently of the object.

4.1.1 System

Operating system

Build

Build number of the operating system.

Edition

Edition of the operating system.

Features

Additional features of the operating system.

Processor architecture

Processor architecture

Product

Product name of the operating system.

Service pack

No. of the service pack.

Vendor

Vendor of the operating system.

Version

Version of the operating system.

Role based access control

Allow non-secure access

For test purposes or until a correct certiﬁcate is installed an access without encryption to the directory service can be allowed. This is not recommended for production environments.

Base DN

The base DN (Distinguished Name) is the starting point in the directory hierarchy at which a search will begin, e.g.

"dc=example,dc=com". The search base DN is an element of the search operation that works in conjunction with the search scope to deﬁne the subtree of entries that should be considered when processing the search operation. Only entries at or below the search base DN and within the scope will be considered candidates for matching against the search ﬁlter.

LDAP

By default no RBAC is used by ServerView RAID Manager. Here you can enable RBAC via LDAP.

LDAP non-secure port

If non-secure access is allowed you can modify the used port of your directory service here. The default port is 389

LDAP port

Here you can modify the used (secure) port of your directory service. The default port is 636.

LDAP server

Here you can insert the name or IP address of your directory server.

Password

The directory service requires a password for authentication which can be supplied here.

Role DN

This value is used in addition to the base DN when searching roles, e.g. "ou=svs". If no value is supplied, the subtree search will start from the base DN.

Username

The directory service needs an username for authentication, e.g. "cn=Directory Manager", which can be supplied here.

User search base

The node in the directory under which the users reside, for example "ou=users,dc=example,dc=com"

User search ﬁlter

User search ﬁlter stores the unique search criterion for searching a speciﬁc user, e.g. "uid=%u".

RAID Management 27

Single Sign On

CAS

By default no SSO is used by ServerView RAID Manager and you always get a login screen if you call RAID Manager. Here you can enable SSO via CAS authentication.

CAS base URL

URL under which all CAS services reside (default: /cas).

CAS port

Here you can modify the used port of your CAS server. The default port is 3170.

CAS server

Here you can insert the name or IP address of your CAS server.

System

Admin group

Members of this (optional) user group are granted administration rights.

Fully qualiﬁed domain name

Fully qualiﬁed domain name (FQDN) of the system. It is an unambiguous domain name that speciﬁes the system's position in the DNS tree hierarchy absolutely.

IP address

IP address of the system.

Name

Name of the system.

User group

Members of this (optional) user group are allowed to view RAID conﬁguration information.

4.1.2 Devices

Adapter

Abort MDC on error

Abort a consistency check on detection of the ﬁrst inconsistency.

Activity

Current activity of the RAID controller, e.g. Patrol Read running. Additionally for some activities a progress bar with percents and estimated time remaining will be displayed.

Additional status

If available you can see here some additional information of the current status.

Alarm control

Some RAID controllers have an audible alarm which is triggered by a wide range of conditions. Here you switch the alarm on or oﬀ.

Alarm present

Displays whether the RAID controller has an audible alarm.

Auto ﬂush interval

Here you set the intervals at which the cache is to be emptied.

Auto inconsistency handling

Here you select whether a check is to be started automatically. In the case of redundant systems (e.g. RAID-1, RAID-5,

RAID-10) this action starts a check of the logical drive. The consistency check runs in the background, thus enabling you to continue working with the logical drive.

Auto rebuild

Here you deﬁne whether a rebuild is to be started automatically when an error in the logical drive occurs. This setting generally only makes sense in conjunction with a hot spare.

BGI rate

Here you set the background initialization rate.

BIOS build time

Creation date of the BIOS version.

BIOS continue on error

If enabled a user interaction during boot is only required for critical errors. Otherwise boot will be interrupted for every detected problem.

BIOS status

If disabled logical drives cannot be used to boot from. They are not exposed via BIOS INT 13 from Option ROM.

BIOS version

BIOS version of the controller.

Boot from

This describes whether you boot from logical drive or disk.

Boot ID

Unique number of logical drive or disk to boot from.

Bootloader version

Version number of the bootloader.

28 RAID Management

Bus

Number of the PCI bus to which the controller is connected.

CacheCade write cache capable

Flag whether CacheCade can handle read and write I/O operations or read I/O operations only.

Chipset

Codename of the used integrated circuit (IC).

Chip revision

Hardware version of the chip.

Chip temperature

Chip temperature of the controller.

Cluster active

Active status of the cluster.

Cluster enable

Here you switch the cluster mode of the controller on or oﬀ.

Coercion mode

Here you select whether the disk size can be artiﬁcially rounded up/down by the ﬁrmware to facilitate disk exchange.

Completed Patrol Read iterations

Number of completed Patrol Read iterations.

Consistency check rate

When a logical drive is checked this operation takes place in the background. Here you deﬁne the priority with which the consistency check is performed. The higher the priority, the greater the load placed on the system.

Continuous patrolling

Here you can select that patrol read is running automatically without time interval.

Copyback

Here you enable or disable copyback.

Copyback on SMART error

Here you select whether the controller should attempt to start a copyback process if a SMART error is detected on the disk.

Copyback on SSD SMART error

Here you select whether the controller should attempt to start a copyback process if a SMART error is detected on the SSD.

Copyback rate

Here you deﬁne the priority with which the copyback is to be performed.

Correct media errors during Patrol Read

Here you select whether the controller should attempt to ﬁx any media errors found during Patrol Read.

Correctable errors

Number of corrected controller errors.

Critical temperature (high)

The critical upper limit; the adapter should not operate above this limit.

Current CacheCade size

Currently conﬁgured CacheCade size.

Device

Device number on the PCI bus. Together with the bus number this determines the location of the controller.

Device ID

A device ID is unique number associated by a manufacturer to identify hardware.

Disk write cache

Here you activate or deactivate the disk write cache of the controller or of all disks.

Driver date

Creation date of the driver version.

Driver name

Name of the controller driver.

Driver version

Version of the controller driver.

Driver write cache

For some controllers which have no hardware cache you can activate a software cache here which is implemented in the driver.

Estimated time remaining

The estimate of time remaining to complete an activity.

Estimated lifetime

Extrapolated lifetime of the adapter.

Expose enclosure devices

Here you select whether the ﬁrmware shows or hides attached enclosure management devices to/from the operating system.

External power connected

Is an external power supply connected?

External power requirement

Is an external power supply required?

Firmware build time

Creation date of the ﬁrmware version.

Firmware package version

Firmware package version of the controller; describes ﬁrmware, BIOS, etc. as a package.

RAID Management 29

Firmware version

Firmware version of the controller.

FlashROM size

When a RAID controller has a FlashROM its size is shown here.

Foreign GUID

Unique number of a foreign conﬁguration.

Function

Some PCI modules have more than one function, e.g. 2 SCSI Cores (dual-chip as with the new dual-core processors). Together with the location via the PCI bus and PCI device the relevant function can be addressed unambiguously.

GB boundary

Here you select whether or not values should be rounded down to gigabyte boundaries when logical drives are generated.

This setting also allows a slightly smaller drive to be used for replacement.

Hardware version

Hardware version of the controller.

Hostname

ESXi-Host where this adapter is a part of.

Hot spare/auto rebuild

Here you deﬁne whether new disks are integrated automatically and whether a rebuild is to be started automatically when an error in the logical drive occurs.

Hot spare support

Here you deﬁne whether free disks are integrated automatically for erroneous and failed disks when an error in the logical drive occurs.

Hot swap support

Here you deﬁne whether new disks are found automatically from the controller without a system reboot.

ID of the controller.

Inconsistency handling

Here you deﬁne how the system is to react to controller problems.

Inconsistency handling interval

Here you set the intervals at which a check is to be started automatically.

Init mode

Here you select normal or quick initialization for generating the logical drives.

Initialization Rate

Here you deﬁne the priority with which the initialization is to be performed.

Initiator ID

Depending on the controller type the initiator ID for all of the controller's channels can be changed here. In cluster mode each device and consequently also the controller and its channel must have a unique ID.

Internal adapter number

Internal number of the adapter.

Interrupt

IRQ number assigned for this controller. In case of PCI systems this is determined dynamically.

JBOD mode

If enabled, the operating system can access and manage unconﬁgured disks of the adapter.

Logical

Current number of logical drives which are conﬁgured on this controller and maximum number of logical drives respectively.

Logical drive number for boot

Force controller to boot from a speciﬁc logical drive. If the value is set to -1 the controller uses its default settings.

Manufacture date

Date of manufacture of the adapter.

Max. CacheCade size

Maximum conﬁgurable CacheCade size.

Max. disk count

Number of disks on which a Patrol Read can be started at the same time.

MDC rate

Here you set the priority for a consistency check, including debugging (Make Data Consistent).

MDC schedule continuous scheduling

Here you see if the ﬁrmware starts a MDC immediately after ﬁnishing the previous one.

MDC schedule excluded logical drives

Logical drives that are not checked when the MDC scheduler is activated.

MDC schedule frequency

Here you see the intervals at which the ﬁrmware starts MDC.

MDC schedule mode

The mode with which the ﬁrmware handles MDC.

MDC schedule start time

The start time at which the ﬁrmware starts the next MDC.

Memory size

Size of the memory installed on the controller in Megabytes.

Memory type

Type of the memory installed on the controller.

RAID Management

Migration rate

Here you set the migration rate of the connected logical drives.

Name

Model designation of the controller followed by an unique number. The number is sorted by the PCI location.

Native command queuing

Here you see whether the controller supports native command queueing.

Next execution

Time when next execution (of e.g. Patrol Read) takes place.

Number

Number of channels/ports of the RAID controller.

NVData version

NVRAM version of the controller.

NVRAM size

If a controller has an NVRAM, its size is displayed here.

Oﬄine on error

If enabled a disk that sends too many unexpected sense codes in a speciﬁed time will be set to oﬄine automatically.

Error count

Maximum number of unexpected sense codes that may occur in a speciﬁed time.

Time interval

Time interval to monitor the number of unexpected sense codes.

Oﬄine on SMART error

If enabled a disk encountering a SMART error will be set to oﬄine automatically. If 'Copyback on SMART error' is enabled for the adapter this setting has no eﬀect.

Operating system device name

The device name of an adapter, a disk, or a logical drive in the underlying operating system.

Patrol Read delay

For an automatic Patrol Read here you set the time (in hours) which must elapse between two operations.

Patrol Read mode

Here you can disable a Patrol Read and select manual or automatic mode. In automatic mode the disks are always examined for errors at particular intervals. In manual mode you are oﬀered an action for starting the operation.

In automatic mode a scheduled task for Patrol Read is ignored. If you want to start Patrol Read at an arbitrary time by a task manual mode must be set.

Patrol Read on SSD

Here you specify if Patrol Read should handle SSD's or skip them.

Patrol Read rate

Here you set the Patrol Read rate.

Physical

Current number of devices which are connected to this controller and maximum number of devices respectively.

Power limit

Maximum limit of power a device may draw from a PCIe slot.

Power on hours

Time where power was connected to the device.

Preserved cache logical drive numbers

List of logical drive numbers for which cache data has been preserved.

Product

Product designation of the controller.

Protocol

Channel/port protocol of the controller.

RAID-5 init

Here you select whether or not an automatic initialization for generating RAID-5 drives. It wipes all existing data from the disks and sets up parity.

Rated write endurance

Percentage of write endurance that is already used.

Rebuild policy

Flag whether an automatic rebuild process may use hot spare disks only or suitable available disks additionally.

Rebuild rate

Here you deﬁne the priority with which the rebuild is to be performed.

Remaining reserve space

Remaining space of reserve area in percent.

Redundancy build rate

Here you deﬁne the priority with which the redundancy build is performed.

Reserve space status

Status of reserve area.

Reserve space warning threshold

When the remaining reserve space falls below this threshold the status of the reserve space will change to Warning.

SAS address

Unique device address worldwide.

RAID Management 31

Segment

PCI segments are logical collections of PCI busses. By using multiple PCI segments it is possible for a system to have more than 256 PCI busses.

Serial number

Serial number of the controller.

Series name

Series name of the controller.

Slot

PCI slot where the controller is installed.

Slot power

Amount of power a PCIe slot can provide.

SMART poll interval

Here you deﬁne the poll interval when SMART support is enabled.

SMART support

Most disks provide the option of indicating future problems. Here you enable or disable problem message output.

Spindown conﬁgured disks

Here you enable or disable the spindown of conﬁgured disks for power saving.

Spindown delay

Here you deﬁne how much time must elapse before the spindown initiates.

Spindown delay

Here you deﬁne how long a disk has to be idle before a spindown can occur.

Spindown hot spares

Here you enable or disable the spindown of hot spares for power saving.

Spindown mode

Here you switch the spindown mode of the controller on or oﬀ.

Spindown unconﬁgured disks

Here you enable or disable the spindown of unconﬁgured disks for power saving.

Spinup delay

Here you deﬁne how many seconds must elapse before the next cluster of drives is started up.

Spinup drive count

Number of disks which are started up in parallel during a system reboot. The greater the number of disks that start simultaneously, the greater the power consumption.

Status

Current status of the controller (OK, Warning, Failed).

Subsystem ID

The subsystem ID diﬀerentiate speciﬁc models (such as add-in cards).

Subsystem vendor ID

While the vendor ID is that of the chip manufacturer, the subsystem vendor ID is that of the card manufacturer.

Task rate

Here you deﬁne the priority with which the background actions are performed. The higher the priority, the greater the load placed on the system.

Temperature

Overall temperature of the controller.

Temporary oﬄine

Some RAID controllers can temporarily switch disks oﬄine (and then online again) without the logical drive being aﬀected.

Total data read

Total amount of data (including meta data) read from the device during its past lifetime.

Total data written

Total amount of data (including meta data) written to the device during its past lifetime.

UART present

Serial interface available.

UEFI driver version

Version of driver for the UEFI preboot environment.

Uncorrectable errors

Number of uncorrectable controller errors.

Vendor

Name of the controller's vendor.

Vendor ID

A vendor ID is a unique number assigned by the PCI-SIG hardware (e.g. chip) manufacturer.

Warning temperature (high)

Upper early warning threshold; a higher temperature indicates a thermal problem in the adapter.

Write endurance

Speciﬁed amount of data that can be written to the device during its lifetime.

Write throttling

Various environmental factors can have an influence on handling write I/O operations. E.g. high chip temperatures may trigger the firmware to slow down processing of write I/O operations (partial). Other factors may even force the firmware to completely prevent write I/O operations.

RAID Management

BBU

Additional status

Additional information for describing the BBU status.

Auto learn mode

Methods how to handle the necessity to recalibrate the BBU periodically. This can be done automatically after a defined period, manually when the firmware warns about a required recalibration, or turned off.

Auto learn period

Period between required recalibrations.

Average time to empty

The estimated time until the BBU will be depleted.

Average time to full

If the BBU is charging, the estimated time until it is fully charged.

Capacitance

Current percentage of the capacity of the capacitor.

Current

Current ﬂow at present in ampere.

Cycle count

The number of times the BBU has been recharged.

Design capacity

Design capacity of the BBU in ampere-hours (Ah).

Design voltage

Nominal voltage designed by the manufacturer for the regular working.

Device name

Device name of the BBU.

Intelligent BBU

Indicator that the BBU has an integrated logic.

Learn delay interval

Delay until a recalibration is started after the learn period has expired.

Manufacture date

Date of manufacture of the BBU.

Max. error margin

Percentage of the maximum error count. When this value reaches 100% the BBU will get failed status.

Module version

Version number of the logic module.

Name

Name of the BBU.

Next learn time

Time until the next recalibration will be required.

Recalibration active

The BBU is completely discharged and then recharged.

Recalibration needed

It was recognized that the BBU performance no longer complies with the speciﬁcations. Recalibration is to be used to try to make the BBU "ﬁt" again.

Relative state of charge

Percentage of the BBU's current state of charge.

Remaining capacity

BBU's current remaining capacity.

Serial number

Serial number of the BBU.

Status

Current status of the BBU. If the status is no longer normal this means that a bad BBU can no longer retain the power it has been charged with and loses voltage too quickly. The BBU should be replaced as soon as possible.

Temperature

Current temperature of the BBU. If this rises signiﬁcantly above the normal value during charging this indicates a faulty BBU.

Type

Type designation of the BBU.

Vendor

Vendor of the BBU.

Version

Version number of the BBU.

Voltage

Current voltage of the BBU. If the BBU is just being charged, higher values may be displayed by the charger.

Channel/Port

Max. devices

Maximum number of devices that can be connected to the channel/port.

RAID Management 33

Name

Designation of the SCSI channel or port.

SAS address

For SAS ports the unique address worldwide like FibreChannel.

Status

Here you can enable or disable, i.e. deactivate, the channel.

Termination

Termination of the SCSI channel.

Transfer speed

Maximum transfer rate which this channel/port theoretically supports.

Transfer width

Transfer width of the SCSI channel or port.

Disk

Activity

Current activity of the disk, e.g. consistency check running. Additionally for some activities a progress bar will be displayed.

Additional status

If available you can see here some additional information of the current status.

Block size

Smallest amount of memory a device will read or write.

Completed Patrol Read iterations

Number of completed Patrol Read iterations.

Conﬁgurability

Here you see whether the disk can be used for RAID conﬁguration or not.

Conﬁg. size

Capacity which the disk provides for a conﬁguration independent of the current usage.

Copyback partner device number

Copyback always involves two disks in the process. This is the device number of the other disk.

Copyback partner name

Copyback always involves two disks in the process. This is the name of the other disk.

Current Patrol Read iteration progress

Here you see the current progress of Patrol Read iteration.

Device number

Unique drive number on the port.

Enclosure number

Number of enclosure whereof the disk is connected.

Estimated time remaining

The estimate of time remaining to complete an activity.

Firmware version

Firmware version of the drive.

Foreign conﬁguration

Display whether a foreign configuration is on the disk. A foreign configuration can be imported or deleted by the controller action "Manage foreign configuration..".

Format in percent

Amount of memory – in percent of the total amount – a device provides to the end user.

Formatted size

Size of memory a device provides to the end user.

Guarded logical drives

List of IDs of the logical drives which are guarded by this disk (in its role as hot spare).

Hardware errors

Number of faulty blocks on the disk.

Last shield diagnostics

Time of last completed shield diagnostics operation.

Media errors

Number of faulty blocks on the disk.

Media type

Type of storage media, e.g. HDD (Hard Disk Drive) or SSD (Solid State Disk).

Misc errors

Number of other errors.

Name

Designation of the drive.

Native command queuing

Here you enable or disable native command queuing for the disk.

Operating system device name

Device name of the (logical) disk, set by operating system.

Physical size

Real capacity of the disk.

RAID Management

Port number/Channel number

Unique connection number of the port/channel on the RAID controller.

Power status

Power condition of the device that shows whether the device is active or stopped (spindown).

Product

Product designation of the drive.

Rotational speed

Rotational speed of the disk.

SAS address

Unique device address worldwide.

Serial number

Unique serial number of the drive.

Shield counter

How often the disk fell into shield state and did not fail in the 60 day probationary period.

Slot

Location of the disk in the cabinet.

SMART errors

Number of errors detected by the SMART function.

SMART ﬂagged

SMART problem detected.

Status

Current status of the disk (Available, Operational, Global Hot-Spare, Dedicated Hot-Spare, Failed).

Target ID

Unique drive number on the channel. With SCSI devices this is also the SCSI ID.

Temperature

Temperature of the disk.

Total data written

Total amount of data (including meta data) written to the device during its past lifetime.

Transfer speed

Data transfer speed. This can deviate from the theoretical values for the drive or the options for the controller since, for example in the case of SCSI devices, the transfer rate between the controller and all devices is negotiated.

Transfer width

Data width; depends, among other things, on the bus type and drive.

Type

Disk type.

Usage

The usage by logical drives. Display the respective name, RAID level, and additionally capacity by tooltip.

Vendor

Name of the vendor.

Write cache

Here you activate or deactivate the disk write cache.

Enclosure

Enclosure number

Unique connection number of device in this place the enclosure on the RAID controller.

Hardware version

Hardware version of the enclosure.

Logical ID

The enclosure logical ID uniquely identiﬁes the enclosure.

Name

Model designation of the enclosure.

Product

Product designation of the enclosure.

Serial number

Serial number of the enclosure.

Status

Current status of the enclosure.

Vendor

Name of the vendor.

Alarm, Fan, Power supply, Temperature sensor

Additional status

Additional information for describing the status of alarm module, power supply, or temperature sensor.

Critical temperature (high)

The critical upper limit; the enclosure should not operate above this limit.

RAID Management 35

Critical temperature (low)

The critical lower limit; the enclosure should not operate below this limit.

Fan speed

Current speed of fan (low/medium/high).

Hardware version

Hardware version of the power supply.

Location

The position of of fan or temperature sensor.

Name

Model designation of alarm, fan, power supply, or temperature sensor.

Part number

Part number of the power supply.

Product

Product designation of the power supply.

Serial number

Serial number of the power supply.

Status

Current status of alarm, fan, power supply, temperature sensor.

Temperature

Temperature display.

Warning temperature (high)

Upper early warning threshold; a higher temperature indicates a thermal problem in the enclosure.

Warning temperature (low)

Lower early warning threshold; a lower temperature indicates a thermal problem in the enclosure.

Host , Hosts

Additional status

Additional information for describing the status of the ESXi host.

Comment

Here you can insert a comment about the ESXi host.

Fully qualiﬁed domain name

Fully Qualiﬁed Domain Name (FQDN) of the ESXi host. It is an unambiguous domain name that speciﬁes the system's position in the DNS tree hierarchy absolutely.

Hosts

In this table you can see all ESXi hosts that are managed by ServerView RAID Manager. The table shows the name, FQDN, IP address, and the status.

IP address

IP address of the ESXi host.

Name

Name of the ESXi host, alternatively, if you add an ESXi host to ServerView RAID Manager the FQDN or IP address can also be speciﬁed.

Password

If the ESXi host requires authentication a password can be supplied here.

Port number

Port number of the ESXi host through which a connection is to be established for monitoring. The default port is 5989.

Status

Current status of the ESXi host (OK, Warning, Failed, Initializing, Uninitialized).

Username

If the ESXi host requires authentication a username can be entered here.

Logical drive

Emulate 512e

If enabled, the emulation of 512 byte block size can be turned oﬀ to directly expose 4 KB logical and physical block size.

Access mode

Here you set the access mode which can be used to access the logical drive.

Activity

Current activity of the logical drive, e.g. consistency check running. Additionally for some activities a progress bar will be displayed.

Additional status

If available you can see here some additional information of the current status.

BGI

Here you enable or disable the background initialization rate.

Cache mode

Here you select whether read and write operations are forwarded directly or buﬀered in the cache.

CacheCade number

Number of the CacheCade.

RAID Management

CacheCade type

Flag whether the current CacheCade is conﬁgured to handle read and write I/O operations or read I/O operations only.

Default access mode

Describes how and if the operating system can access the logical drive.

Default cache mode

Here you select the default value for cache mode.

Default read mode

Here you select the default value for read mode.

Default write mode

Here you select the default value for write mode.

Disk cache mode

Status of the disk cache mode.

Estimated time remaining

The estimated remaining time to complete an activity.

Initialization status

Initialization status of the logical drive.

Logical drive number

Number of the logical drive.

Logical size

Net capacity of the logical drive. In contrast to the drive vendors the size shown here is actually available to the operating system.

Name

Name assigned when the logical drive was created.

Number of missing drives

Number of missing disks in the logical drive.

Operating system device name

Device name of the logical drive, set by operating system.

Physical size

Sum total of the storage space used on the disk.

RAID level

RAID level of the logical drive.

Read mode

Here you deﬁne the read mode. The following settings are available:

Read-ahead

No read-ahead

Adaptive

Advance read access to the memory takes place.

No advance read access to the memory takes place.

When most of the last read accesses to successive sectors have taken place the controller switches to Read-ahead. When the read accesses have been distributed it switches back to No read-

ahead.

SSD caching

Flag whether a logical drive can make use of a second level cache (CacheCade).

Status

Current status of the logical drive (Operational, Degraded, Failed).

Stripe size

In the case of logical drives with striping (RAID types 0, 5, 10 and 50) the data is distributed to the associated disks in equally sized sections. The amount of data in each section is the stripe size.

Type

RAID type of the logical drive.

Used capacity

Used capacity of the respective disk in percent.

Write mode

Here you deﬁne the write mode. The following settings are available:

Write-back

Write-through

Adaptive

Adaptive Write-back

The controller sends a signal to the server when the data has been written to the controller's cache.

The controller sends a signal to the server only when the data has been written to the disk.

When this setting is chosen and a charged BBU is connected the same procedure is followed as described under Write-back, otherwise the controller behaves as for Write-through.

This display appears when Adaptive is selected and the controller currently handles the write requests as described under Write-

back. After a BBU failure the controller automatically switches to

Write-through.

RAID Management 37

Adaptive Write-through

Always Write-back

This display appears when Adaptive is selected and the controller currently handles the write requests as described under Write-

through. When a charged BBU is available again the controller automatically switches back to Write-back.

The controller always sends a signal to the server when the data has been written to the controller's cache even though the BBU is not present or currently not functional.

Processor (Expander)

Device number/Target ID

Unique device number/ID of the processor (expander) on the port/channel.

Enclosure number

Number of enclosure whereof the processor (expander) is connected.

Firmware version

Firmware version of the processor (expander).

Hardware version

Hardware version of the processor (expander).

Name

Model designation of the processor (expander).

Part number

Part number of the processor (expander).

Port number/Channel number

Unique connection number of the port/channel on the RAID controller.

Product

Product designation of the processor (expander).

SAS address

Unique device address worldwide.

Serial number

Serial number of the processor (expander).

Status

Current status of the processor (expander).

Type

Type designation of the processor (expander).

Vendor

Name of the vendor.

4.1.3 ServerView RAID Manager

E-mail log

Logging

By default no e-mail events were sent from ServerView RAID Manager. Here you can enable the sending.

Log level

E-mail events are weighted diﬀerently. This option enables you to set a threshold from which the events are sent.

Password

If the outgoing e-mail server requires authentication a password can be supplied here.

Recipient E-mail address

Here you can insert the recipient(s) of the e-mails. Multiple e-mail addresses have to be separated by ';' or ','. A maximum of

1024 characters can be used.

Sender description

Here you can insert a free form text that appears in the e-mail header.

Sender E-mail address

Here you can insert a name that appears in the From: header ﬁeld of the e-mail. Some outgoing e-mail servers require a valid e-mail address as sender.

SMTP port

Here you can modify the used port of your outgoing e-mail server. The default port is 25.

SMTP protocol

With this option you can change properties of the SMTP protocol. When setting the value 'smtp' ServerView RAID starts an unencrypted communication with the SMTP server. If the SMTP server sends the response STARTTLS further communication will be encrypted. When setting the value 'smtps' encryption is negotiated when a connection is established.

SMTP server

Here you can insert the name of your outgoing e-mail server.

Username

If the outgoing e-mail server requires authentication a username or an e-mail account can be supplied here.

38 RAID Management

File log

File name

Here you can modify the name of the save ﬁle for ﬁle events which is used by ServerView RAID Manager.

File size

You can modify the size of the save ﬁle for ﬁle events in steps of one Mbyte. Ten Mbytes is preset.

Logging

By default ﬁle events are written to a ServerView RAID Manager log ﬁle. You can disable this logging here.

Log level

Text ﬁle events are weighted diﬀerently. This option enables you to set a threshold from which the events are logged.

Log method

By default a full save file for file events is assigned a new name and saved so that logging can continue in an empty file

(Rotation method). If you wish you can also choose the Round Robin method. In this case the oldest entries in the full ﬁle are overwritten.

Max. save ﬁles

Here you can restrict the maximum number of save files for file events that are retained when the Rotation method is used. If the upper limit is exceeded the oldest file is deleted.

Text format (additionally)

Here you select whether events are additionally written to a text ﬁle without XML format directives.

Plugin

Name

Name of the plugin.

Poll interval

Here you can deﬁne the intervals at which the plugin queries the controller for changes (default: 2 seconds).

Vendor

Name of the vendor.

Show BBU events

If disabled the status of BBU's is always shown as Normal. Events for BBU's are suppressed.

Show tape events

If disabled events for tapes are suppressed.

Version

Version of the plugin or API.

Scheduler, Task

Conﬁgurability

Here you see whether the task can be modiﬁed or deleted.

Name

Name of task which will be deduced automatically from the related action.

Next execution

Time of the next task execution.

Object

Path and name of the object on which the action will be executed.

Status

Status of task. Between 1 and 4 execution failures Warning will be set. After more than 4 failures the task will be stopped by default and the status will be set to Error. With the action "Reset error counters" the error counter will be reset and the status will be cleared.

ServerView RAID Manager

Backup ﬁle

Here you can modify the name of the ServerView RAID Manager backup file. You can save the current RAID configuration using ServerView RAID Manager action "Write configuration".

Poll interval

Here you can deﬁne the intervals at which ServerView RAID Manager asynchronously updates the various logs (default: 2 seconds).

Status

Functional status of ServerView RAID Manager. The following values are possible: Operational, Initializing, Failed, and

Terminating.

Sense log delay

If an Unexpected sense event was logged a recurring identical event is support for this amount of time.

Status adapters

Consolidated status of all monitored controllers. For sake of simplicity only the following values are displayed: Ok, Warning, and Failed.

RAID Management 39

Status disks

Consolidated status of all monitored disks. For sake of simplicity only the following values are displayed: Ok, Warning, and

Failed.

Status logical drives

Consolidated status of all monitored logical drives. For sake of simplicity only the following values are displayed: Ok, Warning, and Failed.

Status overall

Consolidated status of all monitored objects. For sake of simplicity only the following values are displayed: Ok, Warning, and

Failed.

Version

Version of ServerView RAID Manager.

System log

Logging

By default system events are written to a system ﬁle. You can disable this logging here. Depending on the operating system used you can have the event log displayed and manage it with the corresponding functions. Further information on this is provided in the help system for the operating system.

Log destination

Display where the system log information is written to.

Log level

System events are weighted diﬀerently. With this option you set a threshold from which the events are logged.

40 RAID Management

5 Actions and Dialogs

5.1 Executing Actions

Depending on the controller, disk or logical drive selected different actions can be executed via menu item Actions. The hardware type is also decisive for the functionality offered. For example, "Patrol Read" is not supported by all controllers and is consequently not always offered.

The actions which you can execute with the RAID Manager for particular objects are arranged alphabetically to permit easy reference.

The associated description tells you which object (system, controller, disk, logical drive, etc.) they can be used for.

Please note that some actions are not possible with all controller types.

Add server...

This command calls a dialog to add an existing ESXi server (host) to the ServerView RAID Manager conﬁguration. Thus, the RAID controller of the hypervisor can be monitored and conﬁgured. For more information see VMware ESXi.

Alarm oﬀ

The controller's alarm test is terminated and the alarm signal is deactivated.

Alarm on

An alarm signal is activated for checking the controller.

Attach device

Grant operating system access to a SSD device.

Cancel BGI

Cancels initialization which was automatically started by a controller at low priority in the background.

Cancel consistency check

The consistency check is aborted.

Cancel copyback

The copyback is aborted.

Cancel initialization

Initialization of the logical drive is aborted.

Cancel MDC

The MDC (Make Data Consistent) is aborted.

Cancel Patrol Read

The Patrol Read process is aborted.

Cancel rebuild

The Rebuild process is aborted.

Cancel veriﬁcation

Aborts checking of the disk.

Clear bad block log

The log of defective blocks is deleted.

Clear conﬁguration

The entire conﬁguration (all logical drives, hot spares, etc.) is deleted.

Warning: Please pay attention of the conﬁrmation. If you conﬁrm it is also deleted if you are currently working on it.

Clear foreign conﬁguration

This action deletes the foreign conﬁguration of all disks which the ﬁrmware has recognized as belonging together.

Clear log

The save ﬁle(s) for ﬁle events from ServerView RAID is deleted.

Clear NVRAM log

The log from the controller's NVRAM is deleted.

Create dedicated hot spare

Creates a hot spare. When another disk fails the hot spare is automatically integrated into ongoing operations in place of the defective disk. This permits the data of the defective disk to be restored. A dedicated hot spare protects only a selection of redundant logical drives.

Create global hot spare

Creates a hot spare. When another disk fails the hot spare is automatically integrated into ongoing operations in place of the defective disk. This permits the data of the defective disk to be restored. In contrast to a dedicated hot spare a global hot spare protects all redundant logical drives.

Create logical drive...

This action calls a dialog to create a logical drive. Parts of one or more disks are combined to form a logical ("virtual") drive.

Create RAID volume

Two logical drives of the same type (RAID level) are combined to form a logical drive.

Delete all logical drives

All existing logical drives are deleted.

Delete dedicated hot spare

Deletes a dedicated hot spare.

RAID Management 41

Delete global hot spare

Deletes a global hot spare.

Delete last logical drive

The logical drive created last (i.e. the logical drive with the highest index number) is deleted. It is recommended to back up data on all of the logical drives before deleting them.

Warning: It is also deleted if you are currently working on it.

Delete logical drive

A logical drive is deleted. Note: Due to limitations in ﬁrmware this action is not oﬀered for all MegaRAID and Integrated Mirroring

RAID controllers. With these you can only delete either all logical drives at once or just the last one.

Detach device

Revoke operating system access to a SSD device.

Disable SSD caching

Cancel association between logical drive and SSD cache.

Discard preserved cache

If the controller loses access to one or more logical drives, the controller preserves the data from the logical drive. This preserved cache, is preserved until you import the logical drive or discard the cache. Certain actions, such as creating a new logical drive, cannot be performed if preserved cache exists. Note: If there are any foreign configurations, import the foreign configuration before you discard the preserved cache. Otherwise, you might lose data that belongs to the foreign configuration.

Discharge

Discharges the battery for the emergency power supply (Battery Backup Unit – BBU).

Display bad block log

The defective drive device blocks which the controller found when checking the devices are displayed.

Enable SSD caching

Allow ﬁrmware to use an existing SSD cache as additional caching layer for a logical drive.

Fast charge

The battery for the emergency power supply (Battery Backup Unit – BBU) is charged rapidly.

Flush memory

The data from the controller's cache (internal memory) is written to the disks. The cache is then empty.

Force detach device

Revoke operating system access to a SSD device, even if the device is currently in use.

Force write access

Forces write access when another user either does not want to or cannot transfer it.

Caution: This action should only be performed after you have thoroughly weighed up the pros and cons.

Format device

A disk drive is formatted.

Warning: All data previously stored on the drive is lost. If the disk drive is used in a logical drive the data integrity of the logical drive is also impaired.

Get write access

Takes over write access from another user.

Help

This action calls the help about actions.

Import foreign conﬁguration

This action is used to import the foreign conﬁguration of all disks which the ﬁrmware has recognized as belonging together. After this action has been executed, the logical drives which were built with these disks are available for further processing.

Locate

An enclosure is located. An LED on the enclosure ﬂashes either brieﬂy or until location is aborted. In the case of some controllers the LED is set to remain constantly bright.

Locate

A disk is located. An LED on the disk drive ﬂashes either brieﬂy or until drive location is aborted. In the case of some controllers the LED is set to remain constantly bright.

Locate

A logical drive is located.

Logout

This action is only oﬀered for the system object and terminate your session. You return to the login screen or to ServerView if you started the application there.

Make oﬄine

A disk is switched "oﬄine". The status of the aﬀected logical drive changes to "degraded" or "partially degraded".

Make oﬄine (redundancy)

After creating a backup of the disk on a hot spare it is switched "oﬄine". Then the disk is removed from the conﬁguration and replaced by the previously created backup.

Make online

A drive is placed back in service.

Make ready

A disk which was switched "oﬄine" and is no longer part of a logical drive can no longer be switched "online" but only be made available. Only then can it be included in the conﬁguration again using the Make Online action.

Make ready (clear bad block table)

A disk will be made available and simultaneously a bad block table will be cleared.

Manage foreign conﬁguration...

This action calls a dialog to import or clear foreign conﬁgurations.

RAID Management

Manage host...

This action calls a dialog to change connection information or delete an ESXi host from the ServerView RAID Manager conﬁguration. For more information see VMware ESXi.

Manage hot spare...

This action calls a dialog to create or delete a hot spare.

Manage MegaRAID Advanced Software Options...

This action opens a dialog which allows you to enter one or more keys to activate the corresponding software options. Software options which are already activated will be displayed. Installed test keys can be removed by using this action. For more information see RAID Controller Functions.

Manage task...

This action calls a dialog to create, modify or delete a task.

Mark as missing

Remove a speciﬁc disk from a logical drive.

Migrate logical drive...

This action calls a dialog to modify a logical drive. A logical drive is transferred directly from one RAID type to another.

Recalibration

The battery for the emergency power supply (Battery Backup Unit – BBU) is recalibrated. This action returns the battery to its ideal condition.

Release write access

Releases write access for another user who urgently needs it.

Replace missing disk...

With this action a free disk takes over the tasks of a failed disk.

If a disk in a logical drive fails in the new Avago, SAS/SATA solutions and if this is replaced by a new disk, the latter does not automatically take the place of the disk that has been replaced but must be activated manually. If the logical drive should continue to oﬀer restricted functionality after this action has been completed successfully, the rebuild must be started manually.

Reset error counters

This action automatically deletes the error event log for the disk drive and the error counter is set to zero. Also this action can reset the error counter and clear the status of Tasks.

Resume BGI

The background Initialization process is resumed at the point where it was previously stopped.

Resume consistency check

The consistency check is resumed at the place where it was previously stopped.

Resume copyback

The copyback is resumed at the position where it was previously stopped.

Resume initialization

The interrupted initialization of the logical drive is resumed.

Resume MDC

The MDC (Make Data Consistent) is resumed at the point where it was previously stopped.

Resume migration

Migration of a logical drive is resumed (see Migrate logical drive).

Resume Patrol Read

The Patrol Read process is resumed at the point where it was previously stopped.

Resume rebuild

The Rebuild process is resumed at the point where it was previously stopped.

Scan conﬁguration

All the information collected internally is deleted and then all the data is read in anew from controllers.

Send SNMP test event

If SNMP is enabled and conﬁgured you can send a test trap with this action. Neither RAID Manager nor any other SNMP tool can verify that the trap reaches the destination correctly. You have to check yourself whether the trap reaches the destination properly.

Send test E-mail

If you have enabled and conﬁgured the E-mail log you can send a test E-mail with this action.

Show NVRAM log

The internal log from the controller's NVRAM (non-volatile memory) is displayed. This information is generally required by engineers for maintenance purposes.

Show PHY errors

The SAS phy errors recorded are displayed. This information is generally required by engineers for maintenance purposes.

Show sense log

A table with the last n SCSI items of sense information which occurred are displayed. SCSI sense information is generally present when a SCSI command has failed and the controller or the disk can supply additional information on why this happened.

Start consistency check

In the case of redundant systems (e.g. RAID-1, RAID-5, RAID-10) this action starts a check of the logical drive. The consistency check runs in the background, thus enabling you to continue working with the logical drive. Depending on how the synchronization procedure has been set on the controller any error that is found is skipped or rectiﬁed if possible, or the consistency check is stopped and an error message is displayed.

Note: With some controllers the priority of this process can be changed via the Settings tab. The following rule applies here: The lower the priority, the longer the process, but this enables you to work better.

RAID Management 43

Start copyback...

This action calls a dialog to select a disk to copy data from a logical drive to a new destination disk. For more information see

RAID Controller Functions.

Start device

A disk drive is started, i.e. the disk drive is brought up to its standard speed. With some high-speed disks this can take some time.

As power consumption is higher when the disks start up not all of them should be started up at once.

Start initialization

A logical drive is initialized. Before you write the ﬁrst user data to a logical drive you should initialize this drive.

Note: Some controllers automatically perform initialization when the logical drive is created. This action is not oﬀered for these drives.

Warning: Initialization destroys all user data on the logical drive.

Start MDC

A consistency check takes place and, if it is possible to rectify any inconsistency which is found, this is done automatically (Make

Data Consistent).

Start OCE

If there is free storage space on all disks of an array this can be used to increase the capacity of the logical drive (Online Capacity

Expansion). Afterwards existing ﬁlesystems can be adapted to the new capacity with operating system tools.

Start Patrol Read

A Patrol Read process is started on a disk drive. In this case restricted access is still possible to the drive. Patrol Read examines the drive's interface for errors. If an error is detected which cannot be rectiﬁed automatically, this error is logged. The faulty part of the medium is assigned to the defective blocks. With some controllers the disk is automatically taken out of service if multiple errors are found.

This error check is not supported by every controller, but some controllers provide the option of performing a check automatically at freely selectable intervals.

Start rebuild

In the case of critical logical drives of the type RAID-1, RAID-5 or RAID-10 this action starts rebuilding the logical drive. Generally the failed disk is automatically replaced by a hot spare and a rebuild is subsequently started automatically provided this is set on the controller. The action runs in the background, and as long as no further disk fails it is still possible to work with the logical drive.

Start veriﬁcation

Starts a disk check.

Stop charge

Terminates the battery charging process for the emergency power supply (Battery Backup Unit – BBU).

Stop device

A disk drive is stopped. This action can sometimes make sense before a device is replaced.

Stop location

Drive location is stopped and the LED is switched oﬀ.

Suspend BGI

The background initialization process is stopped.

Suspend consistency check

The consistency check is stopped. This can, for example, be necessary when more throughput capacity needs to be provided at short notice for the logical drives connected to the controller.

Suspend copyback

The copyback is paused.

Suspend initialization

Initialization of the logical drive is interrupted.

Suspend MDC

The MDC (Make Data Consistent) is paused.

Suspend migration

Migration of a logical drive is stopped (see Migrate logical drive).

Suspend Patrol Read

The Patrol Read process is stopped. This can, for example, be necessary when more throughput capacity needs to be provided at short notice.

Suspend rebuild

The Rebuild process is stopped. This can, for example, be necessary when more throughput capacity needs to be provided at short notice for the logical drives connected to the controller.

Set low power threshold

Set a voltage threshold where ﬁrmware will issue warnings that the power is to low.

Test CAS connection

If you have enabled and conﬁgured Single Sign On (SSO) via CAS you can check the connection to the CAS server with this action.

Test LDAP connection

If you have enabled and conﬁgured role based access control (RBAC) via LDAP you can check the connection to the directory server with this action.

Unblock

If an SSD cache drive (CacheCade) fails all associated logical drives are set to blocked (i.e. no access from operating system).

The Unblock action reenables access from the operating system.

RAID Management

Write conﬁguration

Save the current RAID conﬁguration into a XML ﬁle on the server.

Write NVRAM log

Save the current internal controller log into a ﬁle on the server.

Write snapshot

This automatic action produces - contrary to the manual action Write conﬁguration - at least every 10 minutes a snapshot of the current RAID conﬁguration.

RAID Management 45

5.2 Creating Logical Drives

Before you create a logical drive with ServerView RAID Manager, ensure that you are familiar with the Supported RAID Types and also know precisely which RAID level is most suitable for your application.

5.2.1 Create logical drive

Select a controller in the tree structure and start the Create logical drive action (via the pulldown menu of the Actions button or with a right mouse click). A dialog box is opened as in the example below for an Avago controller.

Depending on the controller type and RAID level you can change information and properties in the dialog box to create the logical drive.

In the RAID level input ﬁeld enter the RAID level you wish to create. The default for this ﬁeld is "RAID-0".

46 RAID Management

If a new logical drive requires a stripe size, this is displayed in the ﬁeld of the same name. You can accept the default (64 kilobyte) or select a diﬀerent size.

Under Capacity of the logical drive you have two options for determining the size of the logical drive:

Use maximum capacity (default)

The logical drive is created with maximum capacity.

Use only

If you want to use a diﬀerent value from the default, enable this button and enter the desired size in the two adjacent ﬁelds.

Under General parameters you have further adjustable parameters:

In the Name input ﬁeld you can accept the default name for the new logical drive or specify a new name. This name must be unique on the controller and may be up to 15 characters long (standard ASCII).

With Init mode you can select whether no initialization shall be executed automatically after creation of the logical drive or the initialization is executed fast or normal.

With Cache parameters you have the possibility to modify the cache behavior of the logical drive:

For ease of use you can carry out an optimization on Data protection (default) or on Performance under Cache settings.

If you choose the option Advanced instead you can modify all cache parameters separately. Further information to the various parameters can be found under Displaying and Modifying Properties.

On the left the dialog box contains a tree structure in which you select a hard disk and then make it available using the Add button.

The hard disk that has been added is displayed under Current layout.

Logical drives generally (depending on the controller type and RAID level) consist of more than just one hard disk. You must therefore select and add a suitable number of hard disks. In our example (Avago controller and RAID-1) two hard disks are required. Then you can create the logical drive using the Create button. After you have pressed the Create button you must conﬁrm creation of the logical drive again.

If you quit the dialog box via Cancel, no new logical drive is created.

RAID Management 47

5.2.2 Creating MegaRAID CacheCade Drives

This procedure does not create a user accessible logical drive but a drive that functions as a secondary tier of cache.

On controllers that support MegaRAID CacheCade and have the appropriate license installed select in the Create logical drive dialog a

RAID level with (CacheCade) appendix. Then proceed as with creating a logical drive with SSD's.

After successful completion of the Create logical drive dialog a new object will appear in the tree structure as in the example below:

To grant access to the secondary tier of cache the action Enable SSD caching has to be executed on a logical drive.

48 RAID Management

5.3 Modifying Logical Drives (migrating)

The Migrate Logical Drive action enables you to migrate the RAID type to a diﬀerent type expand the capacity of the logical drive

Note: Most operating systems of today support Online Capacity Expansion (OCE). OCE means that the additional capacity after a logical drive has been expanded can be used without rebooting the system. Details on the additional storage capacity are provided in the documentation for your operating system.

To make a modiﬁcation select a logical drive ( ) in the tree structure and start the Migrate logical drive action (via the pulldown menu of the Actions button or with a right mouse click). A dialog box is opened which contains Parameters and Layout.

Select the new RAID type in the pulldown menu. The migration options here depend on the RAID controller used.

Under Layout you can – if you are oﬀered the option – expand the capacity by selecting hard disks in the tree structure and adding them to the logical drive using the Add button. You activate your modiﬁcations using the Apply button.

After you have pressed the Apply button you must conﬁrm the modiﬁcations again. If you quit one of the dialog boxes using Cancel no changes are made.

The following rules apply for modifying a logical drive:

Select the new RAID type for a migration. If the required type is not supported directly by the controller, you can then only delete the logical drive and create a new one.

The capacity of the new logical drive must be at least the same as that of the current drive. If the capacity or the RAID type of the new logical drive requires a greater overall drive capacity than the current one, the additional capacity must be provided by the physical drives which are not yet used in this logical drive. In this case please select one or more physical drives which have suﬃcient free capacity.

Note: The name of a logical drive can – depending on the controller – be modiﬁed in the properties (Settings tab) of the logical drive.

5.4 Processing Hot Spares

Hot spares are used to protect redundant logical drives. If a disk in a redundant logical drive backed up by a hot spare fails, the hot spare automatically replaces the failed disk.

On some controllers a hot spare can be assigned in order to back up an individual logical drive or all logical drives on the controller.

With other controllers it is automatically possible to use any free disk which is large enough as a backup.

5.4.1 Manage hot spare

This action enables you to add or delete a global or dedicated hot spare.

5.4.1.1 Creating

To create a global or dedicated hot spare please select a free disk ( ) on the left in the tree structure. Start the Manage hot spare action (via the pull-down menu of the Actions button or with a right mouse click).

In the dialog box which is now displayed (see example) please select one or more collections in order to create a dedicated hot spare.

If you do not select a collection, a global hot spare is then created.

RAID Management 49

The static (or revertible) hot spare feature can be used to automatically restore a hot spare and logical drive to their original configuration. This function allows administrators who prefer to keep a hot spare in a specific slot within the enclosure to easily return to the preferred configuration without a manual rebuild. The static hot spare feature reduces or eliminates any administrator maintenance beyond replacement of the failed hard drive.

Note: The controller automatically reverts a hot spare only if the failed disk is replaced with a new disk in the same slot. If the new disk is not placed in the same slot, a manual "Replace missing" operation can be used to revert a previously commissioned hot spare.

Enclosure aﬃnity is used to set the preference for a hot spare to be used to rebuild a physical disk that resides in the same physical enclosure. This does not preclude the hot spare from being provisioned to a second enclosure if there are no other hot spares present.

For example, if there are two enclosures and each enclosure has a hot spare with aﬃnity set, then upon a drive failure the hot spare will be provisioned from the same enclosure as the failed drive.

Note: You can conﬁgure hot spare enclosure aﬃnity only if you are using an external storage enclosure.

After you have clicked on the Create button you must conﬁrm the action once again in another dialog box. Depending on what was selected in the previous dialog box, the drive which was originally unused becomes the hot spare and is ﬂagged as a global ( dedicated ( ) hot spare on the left in the tree structure.

) or

Please note that you can only create a hot spare with RAID types with redundancy (e.g. RAID-1, RAID-5, not RAID-0).

5.4.1.2 Deleting

To delete a hot spare please mark the hot spare (

Manage hot spare action.

) or ( ) which you wish to delete on the left in the tree structure. Start the

The dialog box which is now displayed shows you the conﬁguration with the logical drives which are currently protected.

50 RAID Management

After you have clicked on the Delete button you must conﬁrm the action once again in another dialog box. The assignment is now released and the previous hot spare is ﬂagged as unused ( ) on the left in the tree structure.

When you quit one of the dialog boxes by means of Cancel, no hot spare is created or deleted.

In some controllers the individual actions Create dedicated hot spare, Create global hot spare, Delete dedicated hot spare and Delete

global hot spare are oﬀered as alternatives to the Manage hot spare action described above.

5.4.2 Creating hot spares

With hot spare you can protect either a single logical drive (dedicated hot spare) or all logical drives on the controller (global hot spare). The example below describes how you create a dedicated hot spare.

In the tree structure select an unused drive ( ) which is to function as a standby drive.

Start the Create dedicated hot spare action (via the pulldown menu of the Actions button or with a right mouse click). A dialog box is opened as in the example below.

In the pulldown menu select the required logical drive and create it using the Apply button. After you have pressed the button you must conﬁrm the process once more in another dialog box. The drive that was previously unused is now identiﬁed as a dedicated hot spare ( ) in the tree structure.

5.4.3 Deleting hot spares

This action enables you to delete hot spares which you have created. The example below describes how you delete a dedicated hot spare.

In the tree structure select the dedicated hot spare ( ) that you want to delete.

Start the Delete dedicated hot spare action (via the pulldown menu of the Actions button or with a right mouse click). In the dialog box that appears you must conﬁrm the deletion again. After successful deletion the previously dedicated hot spare is now marked in the tree structure as an unused drive ( ).

RAID Management 51

5.5 Foreign Conﬁguration

The new flexible RAID Management enables disks of logical drives to be switched from one enclosure or adapter to another without the configuration being lost. A disk of this type is identified by a blue exclamation point (

This foreign conﬁguration can be imported or deleted.

), which indicates a foreign conﬁguration.

Conﬁgurations can be imported or deleted from disks only if the disk is already available again.

If this was not done automatically, please perform the function using the Make ready action (by means of the pull-down menu of the

Actions button or by right-clicking on the disk). You can then start the dialog described below using the Manage foreign conﬁguration action.

5.5.1 Manage foreign conﬁguration

This action enables you to import or delete one individual foreign conﬁguration or all foreign conﬁgurations.

In the dialog box (see the example below) use the index to select either one individual foreign configuration or all (merged) for all foreign configurations for processing and confirm your selection using the Import or Clear button.

The Cancel button in one of the dialog boxes shown below enables you to abort the action without any eﬀect on the existing conﬁguration.

5.5.1.1 Import

When you select Import, the future overall conﬁguration is displayed before the actual import operation begins.

When you select an individual foreign conﬁguration, this is examined and imported regardless of the existing conﬁguration.

When you select all (merged), an attempt is made to combine all existing conﬁgurations with the foreign conﬁgurations.

52 RAID Management

The import is performed after you have conﬁrmed this and clicked on the OK button.

5.5.1.2 Clear

When you select Clear, you must conﬁrm the operation once again in another dialog box.

When one individual foreign conﬁguration is selected, it is cleared.

When all (merged) is selected, all foreign conﬁgurations are deleted.

Note: If a disk which still contains an old configuration was replaced during maintenance work, it is also identified by a blue flag on the left of the tree. In this case you must delete the old configuration before you can use the disk again.

RAID Management 53

5.6 Task

In order to maintain the operational reliability of a RAID system, certain actions can be repeated at regular intervals. These include, for example the consistency check of the logical drives, the Patrol Read of the disks or the recalibration of existing BBUs.

When the appropriate object (system, controller, disk, logical drive, BBU) or an existing task object has been selected, the object action Manage task (the dialog described below) can be started via the button pull-down menu Actions or by clicking the right mouse button on the object.

5.6.1 Manage task

This action is used to create, modify or delete a task.

5.6.1.1 Create

If a task does not exist for the selected object and the desired action, you can deﬁne and create a task with the following properties.

Select via Task the action that is to be regularly carried out.

For each respective task an optional Exception behavior can be speciﬁed. You can deselect the default setting to stop after 4 errors.

Furthermore you can change the default behavior that after an error a new attempt to start the task is made after 2 minutes, 1 hour, and 8 hours beyond the regular setting. That way you can arrange the number of attempts skip on error and the next regular start time for the task.

Use Frequency to set the required period (from minute-by-minute to yearly). There are various settings depending on the Frequency selected which are used to deﬁne the action recurrences more exactly.

The Start time valid for the task, i.e. when the action is started for the very ﬁrst time, has a default value now when creating the task.

If the action cannot be started, because e.g. the action is already in use, the option now will not be oﬀered. Additionally a time around

24 hours later than current time will be set as default time. Otherwise, if the problem happens when leaving the dialog a time around 8 hours later will be set automatically. A diﬀerent starting time can be agreed upon by choosing later and with input of a valid date as well as a desired time. When the button Create is pressed, the required action is started either within the next minute or after expiration of a selected later start time.

54 RAID Management

Recurrence is used to select a value of 1 to 100 so that, depending on the choice of Frequency, the action can be repeated within a range of intervals (from 1 minute to 100 years).

A weekly Frequency can also have one or more Weekdays in order to deﬁne the starting point more exactly. If no weekday is selected, the current weekday is automatically set as used in the pre-setting. Furthermore the selected weekdays will be considered by the calculation of the ﬁrst starting point if later is selected.

If a monthly Frequency is selected, a day in the month must also be deﬁned on which the respective action is to be started.

RAID Management 55

The exact day of the month can be set via the selection on day. If a month does not have a corresponding day, e.g. 30th February, the action is started on the next possible day of the following month.

On the other hand, the selection on the is used to select the ﬁrst to last week of the appropriate month plus a weekday to start the action.

Also the rule of the desired day of month will be considered if you decided to use a later starting point.

Annual Frequency allows the selection of an exact starting-day (see above) and also oﬀers one or more months in order to deﬁne the starting point more exactly.

56 RAID Management

If an exact day in the month is deﬁned, but this day is not in available certain months, then the corresponding months are automatically deselected and excluded as a selection option. February 29th is an exception. Such a selection is allowed as this day exists in certain years but not all of them. If necessary, the action is started on the next possible day of the following month, i.e. on

March 1st. If no month is selected, the current month is automatically set as used in the pre-setting.

With the choice of later by the Start time the rule of the desired day of month and also the selected months will be considered by the calculation of the exact starting time.

When the button Create is pressed, the required action is started within the next minute or after another desired start time if later is selected. If thereby the Frequency is set at weekly, monthly or annually, the ﬁrst start time is then in the current week or within a month or year, respectively.

When you quit the dialog by means of the Cancel button, no eﬀect on any existing conﬁguration will occur.

If you want to create a task for Patrol Read you must set Patrol Read mode to manual beforehand. Otherwise the task for

Patrol Read will be ignored.

5.6.1.2 Modify

Via the selection of an existing task object or by selection of an action in the dialog, for which the selected object already has a task deﬁned, you can modify the settings of the task.

The Start time is preset at later when a task is modiﬁed. If this setting is not changed, the next start time is calculated when the OK button is pressed based on the set and, if necessary, any modiﬁed values. If the Frequency is set at weekly, monthly or annually, the next start time is then in the current week or within a month or year, respectively. Only a subsequent date is based on the value set in

Recurrence.

If the Start time is changed to now, the action is started within the next minute after the button OK was pressed. If the action cannot be started, because e.g. the action is already running, the option now will not be oﬀered. Otherwise, if the problem happens when leaving the dialog a time around 8 hours later will be set automatically.

Likewise, the status and the internal task error counter is reset after the button OK has been pressed.

When you quit the dialog via the Cancel button, no changes will occur.

RAID Management 57

5.6.1.3 Delete

The task is deleted when the button Delete is pressed. This does not inﬂuence, interrupt nor terminate any current action triggered by the task.

If you quit the dialog by means of the Cancel button, no eﬀect on any existing conﬁguration will occur.

58 RAID Management

6 Events

6.1 Displaying Events

The event window is located at the lower edge of the user interface. It contains the latest events of all the RAID controllers which are managed by ServerView RAID Manager.

You can use the delimiter bar to enlarge or reduce this window. The width of the columns can be changed by dragging its border in the table header. This is sometimes useful for long event messages. A double click on an event opens a dialog, with which it is easy to navigate through the events and to catch the whole detailed message at a glance.

The following information is available for each event:

The type is additionally presented by an icon which indicates the severity of the event.

Error

Warning

Important Information

Date and time at which the event occurred

The name of the object which reported the event

Event ID

A brief message with a description of the event

ServerView RAID Manager logs all events in a Log ﬁle in plain text. This ﬁle is in XML format and is simple to read out and process.

In addition, all events are sent out as SNMP traps for further processing by ServerView Event Manager or any other management tool that can handle traps (e.g. IBM Tivoli, HP OpenView, etc.). Please refer to the ServerView documentation for further details and

RAID Management 59

conﬁguration options.

By default all events show up in the operating system's logging facility. On Windows based systems entries can be found in Start >

Settings > Control Panel > Administrative Tools > Event Viewer (Application), on Linux systems in /var/log/messages, and on Solaris systems in /var/adm/messages.

Note that the message texts, IDs and error classes of the events are the same as those used in the traps and in ﬁle/system logging. The only diﬀerence is that the four error classes of the traps have been reduced to three error classes for the events

(Informational = Information, Minor = Warning, Major and Critical = Error).

6.2 Events / SNMP Traps

The basis for the ServerView RAID SNMP Agent is the MIB file RAID.mib (Windows) or FSC-RAID-MIB.txt (Linux/VMware/Solaris). All the information and trap types are defined in this file. The traps of the MIB are listed below.

The message texts, IDs and error classes of the traps are the same as those used in the event messages in the interface and in ﬁle/system logging.

If the described recovery actions do not solve the problem please call your local Fujitsu Help Desk.

ID Severity

1 Informational Undeﬁned event

10000 Informational Unknown event

Log Entry Recovery action

If there are errors directly before or after this event, perform the proper recovery action for that error.

2 Informational

Connection to ServerView RAID Manager established

3 Informational Disconnected from ServerView RAID Manager

4 Critical

Unexpected disconnect from ServerView RAID

Manager

5 Informational Test event

If problem persists after reboot, call your local Fujitsu

Helpdesk.

If there are errors directly before or after this event, perform the proper recovery action for that error.

For information only.

10001 Informational Internal event

10002 Minor

Write access of the ServerView RAID Manager revoked by user [..] ([..])

For information only.

10003 Major

10004 Major

10005 Major

BBU temperature out of range

BBU temperature unstable

BBU temperature above threshold

1. Check installation of all air ﬂow channels, closed housing, and unblocked louvers.

2. Check environmental temperature.

3. Check version of RAID controller/iRMC ﬁrmware, and BIOS.

1. Check version of RAID controller/iRMC ﬁrmware, and BIOS.

2. If problem persists replace BBU.

1. Check installation of all air ﬂow channels, closed housing, and unblocked louvers.

2. Check environmental temperature.

3. Check version of RAID controller/iRMC ﬁrmware, and BIOS.

60 RAID Management

10006 Major

10007 Major

10008 Major

10009 Major BBU communication error

10010 Informational BBU reconditioning started

10011 Informational BBU status becomes normal

10012 Informational BBU good

10013 Critical

10014 Major

10015 Minor

10016 Minor

BBU voltage out of range

BBU voltage unstable

BBU voltage below threshold

BBU failed

BBU fast charging failed

BBU charge count exceeded

BBU needs reconditioning

10017 Informational SCSI sense data on disk ([..]) available: [..]

10018 Informational Asynchronous command ﬁnished

10019 Informational Adapter [..] suspended

10020 Informational Adapter [..] resumed

10021 Informational Disk ([..]) marked online

1. Check connection between BBU data/power cable and RAID controller.

2. Check version of RAID controller/iRMC ﬁrmware, and BIOS.

3. If problem persists replace BBU.

1. Check connection between BBU data/power cable and RAID controller.

2. Check version of RAID controller/iRMC ﬁrmware, and BIOS.

3. If problem persists replace BBU.

1. Check connection between BBU data/power cable and RAID controller.

2. Check version of RAID controller/iRMC ﬁrmware, and BIOS.

3. If problem persists replace BBU.

1. Check connection between BBU data/power cable and RAID controller.

2. Check version of RAID controller/iRMC ﬁrmware, and BIOS.

3. If problem persists replace BBU.

Note: Only informational during recalibration process.

1. Check connection between BBU data/power cable and RAID controller.

2. Check version of RAID controller/iRMC ﬁrmware, and BIOS.

3. If problem persists replace BBU.

Note: Do not interrupt the charging process by reboots or shutdowns.

1. Check version of RAID controller/iRMC ﬁrmware, and BIOS.

2. If problem persists replace BBU.

1. Initiate manual recalibration process (e.g. via ServerView RAID

Manager). Note: Do not interrupt the charging process by reboots or shutdowns.

2. If problem persists replace BBU.

Note: By default BBU recalibration is automatically initiated every 30 days.

1. If scheduled BBU recalibration is disabled initiate manual recalibration process (e.g. via ServerView RAID

Manager).

RAID Management 61

10022 Critical Disk ([..]) marked oﬄine

10023 Major Disk ([..]) timed out

10024 Informational Global hot spare created on disk ([..])

10025 Minor Global hot spare deleted on disk ([..])

10026 Informational Dedicated hot spare created on disk ([..])

10027 Minor Dedicated hot spare deleted on disk ([..])

10028 Informational Disk ([..]) marked available

10029 Informational Rebuild on disk ([..]) started

10030 Major Rebuild on disk ([..]) failed

10031 Major Bad block on disk ([..]) LBA [..] detected

10032 Informational New disk ([..]) detected

10033 Minor Disk ([..]) removed

10034 Informational Bad sector log entry on disk ([..]) cleared

10035 Informational Bad sector log on disk ([..]) updated

10036 Major Bad sector on disk ([..]) detected

10037 Major

10038 Major

10040 Major

10041 Major

COD I/O error on disk ([..])

Error on disk ([..]) detected

10039 Informational Channel [..] was reset

Retry I/O on disk ([..])

ECC error on disk ([..])

10042 Informational Write modes changed

10043 Major Media error on disk ([..])

Note: Only informational if aﬀected disk was manually set oﬄine otherwise:

1. If oﬄine disk is member of an array initiate a rebuild to the oﬄine disk.

2. If problem persists replace aﬀected disk.

Note: In general additional error messages should occur. If there are no other actions deﬁned call your local Fujitsu Helpdesk.

For information only.

1. Manually initiate a second rebuild

(e.g. via ServerView RAID Manager).

2. If problem persists replace aﬀected disk.

Replace aﬀected disk.

Note: Only informational if aﬀected disk has been removed otherwise:

1. Unplug aﬀected disk, wait 30 seconds, reinsert it.

2. Replace aﬀected disk.

3. Replace aﬀected backplane or the data cable.

Replace aﬀected disk.

1. Manually initiate a rebuild (e.g. via

ServerView RAID Manager) of aﬀected disk.

2. If problem persists replace aﬀected disk.

Replace aﬀected disk.

If the problem occurs repeatedly replace aﬀected disk.

Replace aﬀected disk.

62 RAID Management

10044 Minor

10045 Minor

10046 Major

10047 Major

SMART warning on disk ([..])

SMART error on disk ([..])

Bad disk inserted in enclosure [..]

Enclosure [..] powered down

Note: Disk reports a prefailure. The aﬀected disk might fail soon.

1. Replace the disk during next maintenance.

Replace aﬀected disk.

If this error message is not a result of a planned power oﬀ of the external storage subsystem:

1. Check the power cable(s).

2. Check the mains voltage.

3. Replace aﬀected power supply(s).

10048 Informational Enclosure [..] powered up

10049 Critical

10050 Major

10051 Critical

10052 Critical

10053 Critical

10054 Critical

10055 Informational Rebuild started on logical drive [..]

10056 Informational Rebuild ﬁnished on logical drive [..]

10057 Major

Fan [..] in enclosure [..] failed

Temperature sensor [..] in enclosure [..] above threshold

Power supply [..] in enclosure [..] failed

3.3V power failed for disk ([..])

5.0V power failed for disk ([..])

12V power failed for disk ([..])

Rebuild failed on logical drive [..]

Replace aﬀected fan within the external storage subsystem.

1. Check installation of all air ﬂow channels, closed housing, and unblocked louvers.

2. Check environmental temperature.

1. Check the power cable.

2. Check the mains voltage.

3. Replace aﬀected power supply.

1. Check whether all cables are correctly connected to the disk backplane connectors.

2. Replace aﬀected disk.

1. Check whether all cables are correctly connected to the disk backplane connectors.

2. Replace aﬀected disk.

1. Check whether all cables are correctly connected to the disk backplane connectors.

2. Replace aﬀected disk.

1. Manually initiate a second rebuild

(e.g. via ServerView RAID Manager).

10058 Minor Rebuild aborted on logical drive [..]

10059 Informational Rebuild suspended on logical drive [..]

10060 Informational Consistency check started on logical drive [..]

Note: Rebuild was probably aborted by user. Attention:

The aﬀected RAID array is still degraded.

1. The rebuild should be started again as soon as possible.

10061 Informational Consistency check ﬁnished on logical drive [..]

RAID Management 63

10062 Major

10063 Minor

10064 Informational

Consistency check failed on logical drive [..]

Consistency check aborted on logical drive [..]

Consistency check suspended on logical drive

[..]

10065 Informational

Consistency check started on uninitialized logical drive [..]

Failure happens only if a disk out of the logical drive failed.

1. Check state of logical drive.

2. If logical drive is not operational, check state of aﬀected disk.

3. Check for additional error messages for aﬀected disk.

Note: Consistency check was probably aborted by user.

1. The consistency check should be started again as soon as possible.

10066 Major

10067 Major

10068 Informational Migration started on logical drive [..]

10069 Informational Migration ﬁnished on logical drive [..]

10070 Major

10071 Minor

10072 Informational Patrol Read started

10073 Informational Patrol Read ﬁnished

10074 Minor

10075 Informational Patrol Read stopped

10076 Informational Patrol Read suspended

10077 Informational Patrol Read resumed

10078 Major

Consistency check ﬁnished with errors on logical drive [..]

Inconsistency detected on logical drive [..] at

LBA [..]

Migration failed on logical drive [..]

Migration aborted on logical drive [..]

Patrol Read aborted

Logical drive [..] degraded

1. Manually initiate second consistency check (MDC).

2. If problem persists backup data from aﬀected logical drive.

3. Delete and recreate aﬀected logical drive.

4. Restore data.

Check if logical drive is initialized. If initialized check the following:

1. Backup your data.

2. Start a consistency check with ﬁx.

3. Compare backup data with data on logical drive.

4. If diﬀerent (data lost), restore last good data.

Note: The logical drive is failed (multi dead).

1. Replace broken drives.

2. Create new conﬁguration and restore last good data.

Note: Migration was probably aborted by user.

For information only.

Note: Patrol read was probably aborted by user.

For information only.

1. Manually initiate a rebuild of aﬀected disk (e.g. via ServerView

RAID Manager).

2. If problem persists replace aﬀected disk.

64 RAID Management

10079 Critical Logical drive [..] failed

10080 Informational Logical drive [..] created

10081 Minor Logical drive [..] deleted

10082 Informational Logical drive [..] operational

10083 Major Logical drive [..]: Error on disk ([..])

Note: Sometimes it is possible to recover without data loss. Further investigation is needed.

For information only.

Replace aﬀected disk.

10084 Major Logical drive [..]: Bad block at LBA [..] detected

1. Try to rewrite data.

2. If problem persists replace aﬀected disk.

10085 Informational Initialization started on logical drive [..]

10086 Informational Initialization ﬁnished on logical drive [..]

10087 Informational BGI started on logical drive [..]

10088 Informational BGI ﬁnished on logical drive [..]

10089 Minor BGI canceled on logical drive [..]

Background initialization

(BGI) resumes automatically after a certain period of time. For information only.

For information only.

10090 Minor Initialization canceled on logical drive [..]

10091 Informational Drive letter changed for logical drive [..]

10092 Informational Hot spare operation on logical drive [..] started

10093 Major

10094 Major

Hot spare operation on logical drive [..] failed

Logical drive [..] forced from failed to degraded

10095 Informational Alarm enabled

1. Unplug aﬀected disk, wait 30 seconds, reinsert it.

2. Replace aﬀected disk.

1. Temporary oﬄine case.

2. Try to rebuild remaining defect drive.

10096 Minor Alarm disabled

10097 Informational Automatic inconsistency handling enabled

10098 Informational Automatic inconsistency handling disabled

10099 Informational Inconsistency handling interval changed

10100 Informational Rebuild rate changed

10101 Informational Patrol Read disabled

10102 Informational Patrol Read set to automatic

10103 Informational Patrol Read set to manual

10104 Informational Patrol Read delay changed

10105 Informational Initialization set to normal

10106 Informational Initialization set to fast

10107 Informational Initiator ID changed

10108 Informational Automatic rebuild enabled

10109 Informational Automatic rebuild disabled

For information only.

RAID Management 65

10110 Informational New device set to automatic

10111 Informational New device set to CtrlM

10112 Informational MDC rate changed

10113 Informational MDC rate changed to [..] percent

10114 Informational BIOS enabled

10115 Informational BIOS disabled

10116 Informational BIOS stop on error enabled

10117 Informational BIOS stop on error disabled

10118 Informational Write cache on all disks enabled

10119 Informational Write cache on all disks disabled

10120 Informational Read-ahead on all disks enabled

10121 Informational Read-ahead on all disks disabled

10122 Informational Automatic resumption enabled

10123 Informational Automatic resumption disabled

10124 Informational Spinup drive count changed (after next reboot)

10125 Informational Spinup delay changed (after next reboot)

10126 Informational Consistency check rate changed

10127 Informational Temporary oﬄine enabled

10128 Informational Temporary oﬄine disabled

10129 Informational SMART enabled

10130 Informational SMART disabled

10131 Informational SMART poll interval changed

10132 Informational Conﬁguration rescanned

10133 Informational Conﬁguration cleared

10134 Informational Activity changed

10135 Informational Channel [..] termination set to wide

10136 Informational Channel [..] termination set to narrow

10137 Informational Channel [..] termination disabled

10138 Informational Channel [..] activated

10139 Minor Channel [..] disabled

10140 Informational Channel [..] set to dedicated

10141 Informational Channel [..] set to shared

10142 Informational Logical drive [..]: Read-ahead enabled

10143 Informational Logical drive [..]: Read-ahead disabled

10144 Informational Logical drive [..]: Adaptive read-ahead enabled

1. Connection issue.

2. Check all of your cabling.

10145 Informational

Logical drive [..]: Write mode set to Writethrough

10146 Informational Logical drive [..]: Write mode set to Write-back

66 RAID Management

10147 Informational Logical drive [..]: I/O mode set to direct

10148 Informational Logical drive [..]: I/O mode set to cached

10149 Informational

Max. transfer speed of disk ([..]) changed (after next reboot)

10150 Informational

Bus width of disk ([..]) changed (after next reboot)

10151 Major

10152 Major

10154 Critical

10157 Minor

BBU voltage problem detected

BBU temperature problem detected

10153 Informational BBU charging

BBU failed

10155 Informational BBU normal

10156 Informational BBU discharging

Disk error ﬁxed

10158 Informational Driver write cache enabled

10159 Informational Driver write cache disabled

10160 Informational Drive sizing (GB boundary) enabled

10161 Informational Drive sizing (GB boundary) disabled

10162 Informational

Hot spare support and automatic rebuild enabled

10163 Informational

Hot spare support and automatic rebuild disabled

10164 Informational Task rate changed

10165 Informational

Inconsistency handling set to consistency check

10166 Informational

Inconsistency handling set to consistency check (abort on ﬁrst inconsistency)

10167 Informational Inconsistency handling set to MDC

10168 Informational Logical drive [..]: Name changed

10169 Informational Logical drive [..]: Cache write mode changed

10170 Major Reboot required

10171 Informational User [..] ([..]) logged in

10172 Informational User [..] ([..]) logged out

10173 Informational Hot spare enabled

1. Check connection between BBU data/power cable and RAID controller.

2. Check version of RAID controller/iRMC ﬁrmware, and BIOS.

3. If problem persists replace BBU.

1. Check installation of all air ﬂow channels, closed housing, and unblocked louvers.

2. Check environmental temperature.

3. Check version of RAID controller/iRMC ﬁrmware, and BIOS.

Note: Only informational during recalibration process.

1. Check connection between BBU data/power cable and RAID controller.

2. Check version of RAID controller/iRMC ﬁrmware, and BIOS.

3. If problem persists replace BBU.

For information only.

RAID Management 67

10174 Informational Hot spare disabled

10175 Informational Hot swap enabled

10176 Informational Hot swap disabled

10177 Informational Write mode set to Write-back

10178 Informational Write mode set to Write-through

10179 Informational Write mode set to Adaptive

10180 Informational BBU charging started

10181 Informational Automatic initialization of RAID-5 enabled

10182 Informational Automatic initialization of RAID-5 disabled

10183 Informational Copyback enabled

10184 Informational Copyback disabled

10185 Informational Initialization set to clear

10186 Informational Veriﬁcation started on disk ([..])

10187 Informational Veriﬁcation ﬁnished on disk ([..])

10188 Informational Logical drive [..]: Cache read mode changed

10189 Informational Logical drive [..]: Cache mode changed

10190 Informational Logical drive [..]: Access mode changed

10191 Informational Logical drive [..]: BGI mode changed

10192 Informational Logical drive [..]: Disk cache mode changed

10193 Informational Firmware initialization started

10194 Informational Firmware version [..]

10195 Major Unable to recover cache data from TBBU

Call your local Fujitsu

Helpdesk.

10196 Informational Cache data recovered from TBBU successfully

10197 Major Cluster down; communication with peer lost

Call your local Fujitsu

Helpdesk.

10198 Informational [..] ownership changed from [..] to [..]

10199 Informational BGI rate changed to [..] percent

10200 Major

10201 Major

Adapter cache discarded due to memory/BBU problems

Unable to recover cache data due to conﬁguration mismatch

10202 Informational Cache data recovered successfully

10203 Major

Adapter cache discarded due to ﬁrmware version incompatibility

Call your local Fujitsu

Helpdesk.

1. Check version of RAID controller/iRMC ﬁrmware, and BIOS.

10204 Critical

10205 Informational Factory defaults restored

10206 Major

Fatal ﬁrmware error: [..]

Flash downloaded image corrupt

1. Disconnect AC and wait 30 seconds before reconnect.

1. Download again.

2. Retry ﬂash.

10207 Major Flash erase error

1. Replace aﬀected RAID controller.

68 RAID Management

10208 Major

10209 Major

10210 Informational Flashing image: [..]

10211 Informational Flash of new ﬁrmware image(s) complete

10212 Major

10213 Major

10214 Minor

10215 Major

10216 Major

Flash timeout during erase

Flash error

Flash programming error

Flash timeout during programming

Flash chip type unknown

Flash command set unknown

Flash veriﬁcation failure

1. Retry ﬂash.

2. Replace aﬀected RAID controller.

1. Retry ﬂash.

2. Replace aﬀected RAID controller.

1. Retry ﬂash.

2. Replace aﬀected RAID controller.

1. Retry ﬂash.

2. Replace aﬀected RAID controller.

1. Retry ﬂash.

2. Replace aﬀected RAID controller.

1. Retry ﬂash.

2. Replace aﬀected RAID controller.

1. Retry ﬂash.

2. Replace aﬀected RAID controller.

10217 Informational Flush rate changed to [..] seconds

10218 Informational Hibernate command received from host

10219 Informational Event log cleared

10220 Informational Event log wrapped

10221 Major

10222 Major

Multi-bit ECC error: ECAR=[..], ELOG=[..], ([..])

If the problem occurs repeatedly replace the RAID controller DIMM module

(cache).

Single-bit ECC error: ECAR=[..], ELOG=[..], ([..])

If the problem occurs repeatedly replace the RAID controller DIMM module

(cache).

10223 Major Not enough adapter memory

1. Replace the RAID controller DIMM module (cache).

2. If problem persists replace RAID controller.

10224 Informational Patrol Read rate changed to [..] percent

10225 Informational Migration rate changed to [..] percent

10226 Informational Shutdown command received from host

10227 Informational Test event: '[..]'

10228 Informational

Time established as [..]; ([..] seconds since power on)

10229 Informational User entered ﬁrmware debugger

10230 Informational

BGI corrected medium error (logical drive [..] at

LBA [..] on disk ([..]) at LBA [..])

10231 Major

BGI ﬁnished with uncorrectable errors on logical drive [..]

Initiate consistency check

(e.g. via ServerView RAID

Manager).

10232 Major

BGI detected uncorrectable multiple medium errors (disk ([..]) at LBA [..] on logical drive [..])

Replace aﬀected disk.

10233 Major BGI failed on logical drive [..]

1. Restart Background initialization

(BGI).

2. Replace aﬀected disk.

RAID Management 69

10234 Informational BGI progress on logical drive [..] is [..]

10235 Informational Logical drive [..]: [..] changed

10236 Informational

MDC corrected medium error (logical drive [..] at LBA [..] on disk ([..]) at LBA [..])

10237 Major

Consistency check found inconsistent parity on logical drive [..] at stripe [..]

1. Start consistency check again.

2. If problem persists backup data from aﬀected logical drive.

3. Delete and recreate aﬀected logical drive.

4. Restore data.

10238 Informational

Consistency check logging disabled on logical drive [..] (too many Inconsistencies)

10239 Informational Consistency check progress on [..] is [..]

10240 Major Initialization failed on logical drive [..]

1. Start initialization again.

10241 Informational Initialization progress on logical drive [..] is [..]

10242 Informational Fast initialization started on logical drive [..]

10243 Informational Full initialization started on logical drive [..]

10244 Informational Logical drive [..]: Property [..] updated

10245 Major

Migration detected uncorrectable multiple medium errors (logical drive [..] at LBA [..] on disk ([..]) at LBA [..])

Replace aﬀected disk.

10246 Informational Migration progress on logical drive [..] is [..]

10247 Informational Migration resumed on logical drive [..]

10248 Major

Resume migration of logical drive [..] failed due to Conﬁguration Mismatch

1. Check the RAID conﬁguration and the event log for additional information.

2. Backup data from aﬀected logical drive.

10249 Informational

State change on logical drive [..] from operational to operational

10250 Minor Clear aborted on disk ([..])

10251 Major Clear failed on disk ([..]) (error [..])

For information only.

1. Check version of RAID controller/iRMC ﬁrmware, and BIOS.

2. Verify that current RAID controller drivers are installed.

3. Disconnect AC and wait 30 seconds before reconnect.

10252 Informational Clear progress on disk ([..]) is [..]

10253 Informational Clear started on disk ([..])

10254 Informational Clear ﬁnished on disk ([..])

10255 Major Error on disk ([..]) (error [..])

10256 Informational Format complete on disk ([..])

10257 Informational Format started on disk ([..])

10258 Major

Hot spare SMART polling failed on disk ([..])

(error [..])

Disk ([..]) is not supported 10259 Major

10260 Informational

Patrol Read corrected medium error on disk

([..]) at LBA [..]

Replace aﬀected disk.

Call your local Fujitsu

Helpdesk.

Install supported disk.

70 RAID Management

10261 Informational Patrol Read progress on disk ([..]) is [..]

10262 Major

Patrol Read found an uncorrectable medium error on disk ([..]) at LBA [..]

10282 Major

10283 Major

10284 Major

10285 Major

SAS topology error: Loop detected

SAS topology error: Unaddressable device

SAS topology error: Multiple ports to the same

SAS address

SAS topology error: Expander error

Replace aﬀected disk.

10263 Minor Predictive failure: Disk ([..])

10264 Major

10265 Minor

Puncturing bad block on disk ([..]) at LBA [..]

Rebuild aborted by user on disk ([..])

10266 Informational Rebuild complete on logical drive [..]

10267 Informational Rebuild complete on disk ([..])

10268 Informational Rebuild progress on disk ([..]) is [..]

10269 Informational Rebuild resumed on disk ([..])

10270 Informational Rebuild automatically started on disk ([..])

10271 Major

Rebuild stopped on disk ([..]) due to loss of cluster ownership

10272 Major

10273 Major

Reassign write operation failed on disk ([..]) at

LBA [..]

Unrecoverable medium error during rebuild on disk ([..]) at LBA [..]

10274 Informational

Corrected medium error during recovery on disk ([..]) at LBA [..]

10275 Major

Unrecoverable medium error during recovery on disk ([..]) at LBA [..]

10276 Informational

Unexpected sense: Disk ([..]), Key/ASC/ASCQ:

[..]: [..]

10277 Informational

State change on disk ([..]) from available to available

10278 Informational

State change by user on disk ([..]) from available to available

Note: Disk reports a prefailure. The aﬀected disk might fail soon.

1. Replace the disk during next maintenance.

Replace aﬀected disk.

For information only.

1. Restart rebuild.

Replace aﬀected disk.

10279 Major Redundant path to disk ([..]) broken

Call your local Fujitsu

Helpdesk.

10280 Informational Redundant path to disk ([..]) restored

10281 Minor

Dedicated hot spare ([..]) no longer useful due to deleted array

For information only.

Check the SAS conﬁguration and cabling.

1. Check the SAS conﬁguration and cabling.

2. If problem persists replace aﬀected backplane.

RAID Management 71

10286 Major

10287 Major

10288 Major

10289 Major

10290 Major

10291 Major

10292 Major

10293 Major

10294 Major

10295 Minor

10296 Minor

10297 Minor

SAS topology error: SMP timeout

SAS topology error: Out of route entries

SAS topology error: Index not found

SAS topology error: SMP function failed

SAS topology error: SMP CRC error

SAS topology error: Multiple subtractive

SAS topology error: Table to table

SAS topology error: Multiple paths

Unable to access disk ([..])

Dedicated hot spare not useful for all arrays

Global hot spare does not cover all arrays

Marking logical drive [..] inconsistent due to active writes at shutdown

10298 Informational BBU present

10299 Informational BBU not present

10300 Informational New BBU detected

10301 Informational BBU has been replaced

10302 Informational BBU temperature is normal

10303 Major

BBU has failed and cannot support data retention

10304 Informational BBU relearn started

10305 Informational BBU relearn in progress

10306 Informational BBU relearn ﬁnished

Check the SAS conﬁguration and cabling.

1. Unplug aﬀected disk, wait 30 seconds, reinsert it.

2. Replace aﬀected disk.

3. Replace aﬀected backplane.

For information only.

Note: The size of the global hot spare is not suﬃcient to secure all arrays.

Initiate consistency check

(e.g. via ServerView RAID

Manager).

If the system does not have a BBU this is for information only. If the system does have a BBU replace the BBU.

If the error message occurs right after replacement of the BBU it can be safely ignored. The situation can occur due to the insuﬃcient

BBU charge.

If the error message occurs during regular operation replace the BBU.

72 RAID Management

10307 Minor BBU relearn timed out

10308 Informational BBU relearn pending: BBU is under charge

10309 Informational BBU relearn postponed

10310 Informational BBU relearn will start in 4 days

10311 Informational BBU relearn will start in 2 days

10312 Informational BBU relearn will start in 1 day

10313 Informational BBU Relearn will start in 5 hours

10314 Minor BBU removed

10315 Informational Enclosure (SES) discovered on [..]

10316 Informational Enclosure (SAF-TE) discovered on [..]

10317 Minor

10318 Informational Enclosure [..] communication restored

10319 Informational Enclosure [..] fan [..] inserted

10320 Minor Enclosure [..] fan [..] removed

10321 Major

10327 Major

10328 Major

10329 Major

Enclosure [..] communication lost

Enclosure [..] I/O module [..] failed

10322 Informational Enclosure [..] I/O module [..] inserted

10323 Major Enclosure [..] I/O module [..] removed

10324 Major

10325 Minor

Enclosure [..] shutdown

Enclosure [..] not supported; too many enclosures connected to port

10326 Major

Enclosure [..] ﬁrmware mismatch (I/O module

[..])

Enclosure [..] sensor [..] bad

Enclosure [..] PHY bad for slot [..]

Enclosure [..] is unstable

10330 Major

10331 Major

Enclosure [..] hardware error

Enclosure [..] not responding

10332 Minor

SAS/SATA mixing not supported in enclosure;

[..] disabled

10333 Informational

Enclosure (SES) hot plug on [..] was detected, but is not supported

10334 Informational Clustering enabled

10335 Informational Clustering disabled

1. Initiate manual recalibration process (e.g. via ServerView RAID

Manager). Note: Do not interrupt the charging process by reboots or shutdowns.

2. If problem persists replace BBU.

For information only.

1. Check data cable(s) to enclosure.

2. Check if enclosure is running.

For information only.

Call your local Fujitsu

Helpdesk.

For information only.

Check your enclosure conﬁguration.

Call your local Fujitsu

Helpdesk.

Call your local Fujitsu

Helpdesk.

Replace aﬀected disk.

Call your local Fujitsu

Helpdesk.

1. Check data cable(s) to enclosure.

2. Check if enclosure is running.

1. Check data cable(s) to enclosure.

2. Check if enclosure is running.

Check your disk conﬁguration within enclosure.

RAID Management 73

10336 Minor Disk ([..]) too small to be used for auto rebuild

Check your disk conﬁguration.

10337 Informational

BBU enabled; changing Write-through logical drives to Write-back

10338 Minor

BBU disabled; changing Write-back logical drives to Write-through

10339 Informational Bad block table on disk ([..]) is 80 percent full

1. Check connection between BBU data/power cable and RAID controller.

2. Check version of RAID controller/iRMC ﬁrmware, and BIOS.

3. If problem persists replace BBU.

10340 Major

10341 Minor

10342 Minor

Bad block table on disk ([..]) is full; unable to log Block [..]

MDC aborted due to ownership loss on logical drive [..]

BGI aborted due to ownership loss on logical drive [..]

BBU/charger problems detected; SOH bad

Replace aﬀected disk.

1. Restart consistency check (MDC).

1. Restart Background initialization

(BGI).

10343 Major

10344 Minor

10345 Major

Single-bit ECC error: ECAR=[..], ELOG=[..],

([..]); warning threshold exceeded

Single-bit ECC error: ECAR=[..], ELOG=[..],

([..]); critical threshold exceeded

Replace the BBU.

If the problem occurs repeatedly replace the RAID controller DIMM module

(cache).

1. Replace the RAID controller DIMM module (cache).

2. If problem persists replace RAID controller.

10346 Major

Single-bit ECC error: ECAR=[..], ELOG=[..],

([..]); further reporting disabled

10347 Minor Enclosure [..] power supply [..] cable removed

10348 Informational Enclosure [..] power supply [..] cable inserted

10349 Informational Enclosure [..] fan [..] returned to normal

Check the enclosure power cable(s).

10350 Informational BBU retention started on previous boot

10351 Informational BBU retention test passed

10352 Major BBU retention test failed

Note: In general additional error messages should occur. If there are no other actions deﬁned call your local Fujitsu Helpdesk.

10353 Informational Retention test started on previous reboot

10354 Informational NVRAM retention test passed

10355 Major NVRAM retention test failed

10356 Informational [..] test ﬁnished [..] passes successfully

Note: In general additional error messages should occur. If there are no other actions deﬁned call your local Fujitsu Helpdesk.

74 RAID Management

10357 Major

10358 Informational Self-check diagnostics ﬁnished

10359 Informational Foreign conﬁguration detected

10360 Informational Foreign conﬁguration imported

10361 Informational Foreign conﬁguration cleared

10362 Minor

10363 Minor

[..] test failed on [..] pass. fail data: errorOﬀset=[..] goodData=[..] badData=[..]

NVRAM is corrupt; reinitializing

NVRAM mismatch occurred

Note: In general additional error messages should occur. If there are no other actions deﬁned call your local Fujitsu Helpdesk.

If the problem occurs repeatedly replace the RAID controller.

10364 Minor SAS wide port [..] lost link on PHY [..]

10365 Informational SAS wide port [..] restored link on PHY [..]

10366 Minor

10367 Minor

SAS port [..], PHY [..] has exceeded the allowed error rate

Bad block reassigned on disk ([..]) from LBA [..] to LBA [..]

10368 Informational Adapter hot plug detected

10369 Informational

Enclosure [..] temperature sensor [..] diﬀerential detected

10370 Informational Disk test cannot start. No qualifying disks found

10371 Informational

Time duration provided by host is not suﬃcient for self-checking

10372 Informational

Disk ([..]) on array [..] row [..] marked as missing

1. Unplug aﬀected disk, wait 30 seconds, reinsert it.

2. Check/replace cable between controller and aﬀected disk.

3. Check version of RAID controller/iRMC ﬁrmware, and BIOS.

4. Replace aﬀected disk.

Note: Disk reports errors.

The aﬀected disk might fail soon.

1. Replace the disk as soon as possible.

If the problem occurs repeatedly replace the disk during next maintenance.

For information only.

10373 Informational Disk ([..]) replaced missing on array [..] row [..]

10374 Informational

Enclosure [..] temperature sensor [..] returned to normal

10375 Informational Enclosure [..] ﬁrmware download in progress

10376 Major Enclosure [..] ﬁrmware download failed

Call your local Fujitsu

Helpdesk.

10377 Minor

10378 Minor

Disk ([..]) is not certiﬁed

Dirty cache data discarded by user

Check the type of your disk.

For information only.

RAID Management 75

10379 Minor

10380 Minor

10381 Minor

Disks missing from conﬁguration at boot

Logical drives missing drives and will go oﬄine at boot: [..]

Logical drives missing at boot: [..]

10382 Minor

Previous conﬁguration completely missing at boot

10383 Informational BBU charging complete

10384 Informational Enclosure [..] fan [..] speed changed

10385 Informational

Dedicated hot spare ([..]) imported as global due to missing arrays

10386 Informational

Disk ([..]) rebuild not possible as SAS/SATA mixing is not supported in an array

10387 Informational

I/O module [..] has been rebooted as part of enclosure ﬁrmware download. It will be unavailable until reboot completes

10388 Minor

10389 Minor

Logical drive [..] partially degraded

BBU requires reconditioning; please initiate a

LEARN cycle

Check your RAID conﬁguration.

Replace aﬀected disk.

10390 Informational Coercion mode changed

10391 Informational BBU automatic learn mode changed

10392 Informational BBU automatic learn period changed

10393 Informational BBU learn delay interval changed

10394 Informational BBU next learn time changed

10395 Informational Max. disk count for Patrol Read changed to [..]

10396 Informational Continuous patrolling enabled

10397 Informational Continuous patrolling disabled

10398 Major MDC ﬁnished with errors on logical drive [..]

1. Manually initiate second consistency check (MDC).

2. If problem persists replace aﬀected disk.

10399 Informational

Logical drive [..] disabled because RAID-5 is not supported by this RAID key

10400 Informational

Logical drive [..] disabled because RAID-6 is not supported by this RAID key

10401 Minor

Logical drive [..] disabled because SAS drives are not supported by this RAID key

Check the disks.

10402 Minor Disks missing

10403 Informational Rebuild rate changed to [..] percent

10404 Informational Consistency check rate changed to [..] percent

Check your RAID conﬁguration.

10405 Informational SMART poll interval changed to [..] s

10406 Informational MDC started on logical drive [..]

76 RAID Management

10407 Informational MDC ﬁnished on logical drive [..]

10408 Major MDC failed on logical drive [..]

10409 Minor MDC aborted on logical drive [..]

10410 Informational MDC suspended on logical drive [..]

10411 Informational MDC started on uninitialized logical drive [..]

10412 Major

10413 Minor

State change on logical drive [..] from operational to degraded

State change on logical drive [..] from operational to partially degraded

10414 Critical

State change on logical drive [..] from operational to failed

10415 Informational

State change on logical drive [..] from degraded to operational

10416 Minor

10417 Minor

State change on logical drive [..] from degraded to degraded

State change on logical drive [..] from degraded to partially degraded

10418 Critical

State change on logical drive [..] from degraded to failed

10419 Informational

State change on logical drive [..] from partially degraded to operational

10420 Minor

10421 Minor

State change on logical drive [..] from partially degraded to degraded

State change on logical drive [..] from partially degraded to partially degraded

10422 Critical

State change on logical drive [..] from partially degraded to failed

10423 Informational

State change on logical drive [..] from failed to operational

10424 Minor

State change on logical drive [..] from failed to degraded

10425 Minor

10426 Critical

State change on logical drive [..] from failed to partially degraded

State change on logical drive [..] from failed to failed

10427 Critical

State change by user on disk ([..]) from available to failed

10428 Informational

State change by user on disk ([..]) from available to hot spare

10429 Informational

State change by user on disk ([..]) from available to rebuilding

10430 Informational

State change by user on disk ([..]) from available to operational

1. Manually initiate second consistency check (MDC).

2. If problem persists replace aﬀected disk.

For information only.

Replace aﬀected disk.

1. Check version of RAID controller/iRMC ﬁrmware, and BIOS.

Call your local Fujitsu

Helpdesk.

For information only.

1. Replace aﬀected disks.

2. The array has to be recreated.

Note: Data loss is probable.

Replace aﬀected disk.

Call your local Fujitsu

Helpdesk.

1. Replace aﬀected disks.

2. The array has to be recreated.

Note: Data loss is probable.

For information only.

Call your local Fujitsu

Helpdesk.

For information only.

RAID Management 77

10431 Informational

State change by user on disk ([..]) from failed to available

10432 Critical

State change by user on disk ([..]) from failed to failed

10433 Informational

State change by user on disk ([..]) from failed to hot spare

10434 Informational

State change by user on disk ([..]) from failed to rebuilding

10435 Informational

State change by user on disk ([..]) from failed to operational

10436 Informational

State change by user on disk ([..]) from hot spare to available

10437 Critical

State change by user on disk ([..]) from hot spare to failed

10438 Informational

State change by user on disk ([..]) from hot spare to hot spare

10439 Informational

State change by user on disk ([..]) from hot spare to rebuilding

10440 Informational

State change by user on disk ([..]) from hot spare to operational

10441 Informational

State change by user on disk ([..]) from rebuilding to available

10442 Critical

10443 Informational

State change by user on disk ([..]) from rebuilding to failed

State change by user on disk ([..]) from rebuilding to hot spare

10444 Informational

State change by user on disk ([..]) from rebuilding to rebuilding

10445 Informational

State change by user on disk ([..]) from rebuilding to operational

10446 Informational

State change by user on disk ([..]) from operational to available

10447 Critical

State change by user on disk ([..]) from operational to failed

10448 Informational

State change by user on disk ([..]) from operational to hot spare

10449 Informational

State change by user on disk ([..]) from operational to rebuilding

10450 Informational

State change by user on disk ([..]) from operational to operational

10451 Critical

State change on disk ([..]) from available to failed

10452 Informational

State change on disk ([..]) from available to hot spare

10453 Informational

State change on disk ([..]) from available to rebuilding

For information only.

Replace aﬀected disk.

78 RAID Management

10454 Informational

State change on disk ([..]) from available to operational

10455 Informational

State change on disk ([..]) from failed to available

10456 Critical State change on disk ([..]) from failed to failed

Call your local Fujitsu

Helpdesk.

10457 Informational

State change on disk ([..]) from failed to hot spare

10458 Informational

State change on disk ([..]) from failed to rebuilding

10459 Informational

State change on disk ([..]) from failed to operational

10460 Informational

State change on disk ([..]) from hot spare to available

10461 Critical

State change on disk ([..]) from hot spare to failed

10462 Informational

State change on disk ([..]) from hot spare to hot spare

10463 Informational

State change on disk ([..]) from hot spare to rebuilding

Replace aﬀected disk.

10464 Informational

State change on disk ([..]) from hot spare to operational

10465 Informational

State change on disk ([..]) from rebuilding to available

10466 Critical

State change on disk ([..]) from rebuilding to failed

1. Manually initiate a second rebuild

(e.g. via ServerView RAID Manager).

2. If problem persists replace aﬀected disk.

10467 Informational

State change on disk ([..]) from rebuilding to hot spare

10468 Informational

State change on disk ([..]) from rebuilding to rebuilding

10469 Informational

State change on disk ([..]) from rebuilding to operational

10470 Informational

State change on disk ([..]) from operational to available

10471 Critical

State change on disk ([..]) from operational to failed

10472 Informational

State change on disk ([..]) from operational to hot spare

10473 Informational

State change on disk ([..]) from operational to rebuilding

10474 Informational

State change on disk ([..]) from operational to operational

10475 Major

MDC detected uncorrectable multiple medium errors (disk ([..]) at LBA [..] on logical drive [..])

Replace aﬀected disk.

RAID Management 79

10476 Major

10477 Major

10478 Informational Disk ([..]) appeared new after reboot

10479 Informational Logical drive [..] appeared new after reboot

10480 Major

10481 Major

10482 Critical

Disk ([..]) missing after reboot

Logical drive [..] missing after reboot

Puncturing of LBAs enabled

Puncturing of LBAs disabled

Enclosure [..] I/O module [..] not installed

Check your RAID conﬁguration.

Call your local Fujitsu

Helpdesk.

Call your local Fujitsu

Helpdesk.

Call your local Fujitsu

Helpdesk.

10483 Informational Package version [..]

10484 Informational

Media veriﬁcation corrected error (logical drive

[..] at LBA [..] on disk ([..]) at LBA [..])

10485 Minor

10486 Minor

State change on disk ([..]) from available to oﬄine

State change by user on disk ([..]) from available to oﬄine

10487 Minor

10488 Minor

State change by user on disk ([..]) from failed to oﬄine

State change by user on disk ([..]) from hot spare to oﬄine

10489 Informational

State change by user on disk ([..]) from oﬄine to available

10490 Critical

State change by user on disk ([..]) from oﬄine to failed

10491 Informational

State change by user on disk ([..]) from oﬄine to hot spare

10492 Minor

State change by user on disk ([..]) from oﬄine to oﬄine

10493 Informational

State change by user on disk ([..]) from oﬄine to operational

For information only.

10494 Informational

State change by user on disk ([..]) from oﬄine to rebuilding

10495 Minor

State change by user on disk ([..]) from operational to oﬄine

10496 Minor

10497 Minor

10498 Minor

For information only.

State change by user on disk ([..]) from rebuilding to oﬄine

For information only.

State change on disk ([..]) from failed to oﬄine For information only.

State change on disk ([..]) from hot spare to oﬄine

1. Manually set the disk to hot spare again (e.g. via ServerView RAID

Manager).

2. If problem persists replace aﬀected disk.

80 RAID Management

10499 Informational

10500 Critical

State change on disk ([..]) from oﬄine to available

State change on disk ([..]) from oﬄine to failed Replace aﬀected disk.

10501 Informational

State change on disk ([..]) from oﬄine to hot spare

10502 Minor State change on disk ([..]) from oﬄine to oﬄine For information only.

10503 Informational

State change on disk ([..]) from oﬄine to operational

10504 Informational

State change on disk ([..]) from oﬄine to rebuilding

10505 Minor

10506 Minor

10508 Major

State change on disk ([..]) from operational to oﬄine

State change on disk ([..]) from rebuilding to oﬄine

10507 Informational Data in cache ﬂushed during power up

Data in cache not ﬂushed during power up

10509 Informational Rebuild resumed on disk ([..])

10510 Informational Automatic rebuild started on logical drive [..]

10511 Informational BGI restarted on logical drive [..]

10512 Major Logical drive [..]: Error on disk [..] [..]

10513 Informational Rebuild on logical drive [..] resumed

Note: Only informational if status change was forced by user otherwise:

1. Replace aﬀected disk.

Note: Only informational if status change was forced by user otherwise:

1. Replace aﬀected disk.

If the problem occurs repeatedly call your local

Fujitsu Helpdesk.

10514 Major

10515 Major

10516 Major

10517 Minor

10518 Major

Consistency check ﬁnished with errors on logical drive [..]: [..]

Error on logical drive [..] detected

Disk ([..]) forced from failed to online

Transfer speed of disk ([..]) changed

SAS port [..] lost link

10519 Informational SAS port [..] restored link

10520 Informational Cache mode changed to Write-back

10521 Informational Cache mode changed to Write-through

Replace aﬀected disk.

1. Manually initiate second consistency check (MDC).

2. If problem persists backup data from aﬀected logical drive.

3. Delete and recreate aﬀected logical drive.

4. Restore data.

1. Check/replace cable between controller and aﬀected disk.

2. If problem persists replace disk.

For information only.

1. Check/replace cable between controller and aﬀected disk.

2. If problem persists replace disk.

1. Unplug aﬀected disk, wait 30 seconds, reinsert it.

2. Check/replace cable between controller and aﬀected disk.

3. Check version of RAID controller/iRMC ﬁrmware, and BIOS.

4. Replace aﬀected disk.

RAID Management 81

10522 Minor

10523 Minor

10524 Minor

Global aﬃnity hot spare ([..]) commissioned in a diﬀerent enclosure

Foreign conﬁguration table overﬂow

Partial foreign conﬁguration imported, disks not imported (device numbers): [..]

10525 Informational Connector [..] is active

Check your RAID conﬁguration.

Call your local Fujitsu

Helpdesk.

Note: Only parts of your conﬁg were imported.

1. Call your local Fujitsu Helpdesk.

10526 Critical

10528 Minor

10529 Major

10530 Major

Adapter missing after reboot

10527 Informational Adapter appeared new after reboot

Rebuild aborted on disk ([..])

Consistency check ﬁnished with [..] correctable errors on logical drive [..]

Consistency check ﬁnished with [..] uncorrectable errors on logical drive [..]

Note: Only informational if controller was removed by user otherwise:

1. Unplug aﬀected controller, wait 30 seconds, reinsert it.

2. If problem persists replace aﬀected controller.

3. If problem persists replace mainboard.

Note: Only informational if rebuild was aborted by user otherwise:

1. Initiate a rebuild again (e.g. via

ServerView RAID Manager).

1. Manually initiate second consistency check (MDC).

2. If problem persists backup data from aﬀected logical drive.

3. Delete and recreate aﬀected logical drive.

4. Restore data.

1. Backup data from aﬀected logical drive.

2. Delete and recreate aﬀected logical drive.

3. Restore data.

10531 Informational

MDC ﬁnished with [..] correctable errors on logical drive [..]

10532 Major

MDC ﬁnished with [..] uncorrectable errors on logical drive [..]

10533 Informational Error counters reset on disk ([..])

10534 Minor

Changed adapter property detected after reboot

10535 Informational Board revision [..]

10536 Minor Command timeout on disk ([..]), CDB:[..]

1. Backup data from aﬀected logical drive.

2. Delete and recreate aﬀected logical drive.

3. Restore data.

Check your adapter properties (e.g. via

ServerView RAID Manager).

Note: Only if problem occurs repeatedly:

1. Check/replace cable between controller and aﬀected disk.

2. If problem persists replace aﬀected disk and/or backplane.

82 RAID Management

10537 Minor

10538 Minor

10539 Major

10540 Major

Disk ([..]) reset (type [..])

Bad block table on logical drive [..] is 80 percent full

Bad block table on logical drive [..] is full; unable to log LBA [..] (on disk ([..]) at LBA [..])

Uncorrectable medium error logged for logical drive [..] at LBA [..] (on disk ([..]) at LBA [..])

Note: Only if problem occurs repeatedly:

1. Check/replace cable between controller and aﬀected disk.

2. If problem persists replace aﬀected disk.

Check for additional error messages for aﬀected disk.

10541 Informational

10542 Minor

Medium error corrected on logical drive [..] at

LBA [..]

Check for additional error messages for aﬀected disk.

Bad block table on disk ([..]) is 100 percent full Replace aﬀected disk.

10543 Minor

10544 Critical

Bad block table on logical drive [..] is 100 percent full

Adapter needs replacement, faulty IOP detected

10545 Informational Copyback started on disk ([..]) from disk ([..])

10546 Informational Copyback aborted on disk ([..]) from disk ([..])

Check for additional error messages for aﬀected disk.

1. Replace aﬀected RAID controller.

10547 Informational Copyback complete on disk ([..]) from disk ([..])

10548 Informational Copyback progress on disk ([..]) is [..]

10549 Informational Copyback resumed on disk ([..])

10550 Informational Copyback automatically started on disk ([..])

10551 Major

10552 Minor

Copyback failed on disk ([..])

Early power oﬀ warning was unsuccessful

Check for additional error messages for aﬀected disk.

Call your local Fujitsu

Helpdesk.

10553 Informational BBU FRU is [..]

10554 Informational Disk ([..]) FRU is [..]

10555 Informational Adapter hardware revision ID [..]

10556 Minor

Foreign conﬁguration metadata needs to be upgraded, may become incompatible

For information only.

10557 Informational BIOS continue on error enabled

10558 Informational BIOS continue on error disabled

10559 Informational

Additional information for failed disk ([..]) ﬁrmware version: [..], serial number [..], ﬁrst use: [..], total running time: [..] days

10560 Informational

If the logical size of logical drive [..] has changed use appropriate operating system tool to reread disk information

10561 Informational Enclosure device exposure changed

10562 Informational Abort consistency check on error changed

10563 Informational Abort MDC on error changed

RAID Management 83

10564 Informational Redundant path restored for disk ([..])

10565 Minor Redundant path broken for disk ([..])

Call your local Fujitsu

Helpdesk.

10566 Informational

Redundant enclosure I/O module [..] inserted for I/O module [..]

10567 Minor

10568 Minor

Redundant enclosure I/O module [..] removed for I/O module [..]

Patrol Read can't be started, all disks are either not online, or are in a logical drive with an active process, or are in an excluded logical drive

10569 Informational

Copyback aborted by user on disk ([..]) from disk ([..])

10570 Major

Copyback aborted on hot spare ([..]) from disk

([..]) as hot spare needed for rebuild

10571 Minor

10572 Major

Copyback aborted on disk ([..]) from disk ([..]) as rebuild required in the array

Cache discarded for logical drive (missing or oﬄine) [..]

10573 Informational Redundancy building started on disk ([..])

10574 Informational Redundancy building ﬁnished on disk ([..])

Call your local Fujitsu

Helpdesk.

For information only.

Call your local Fujitsu

Helpdesk.

Call your local Fujitsu

Helpdesk.

For information only.

10575 Major Redundancy building failed on disk ([..])

Call your local Fujitsu

Helpdesk.

10576 Minor Redundancy building aborted on disk ([..])

10577 Informational Redundancy building suspended on disk ([..])

Call your local Fujitsu

Helpdesk.

10578 Informational

Disk ([..]) power management idle mode enabled

10579 Informational

Disk ([..]) power management idle mode disabled

10580 Informational

Disk ([..]) power management idle condition timer changed

10581 Informational

Disk ([..]) power management standby mode enabled

10582 Informational

Disk ([..]) power management standby mode disabled

10583 Informational

Disk ([..]) power management standby condition timer changed

10584 Informational

Copyback cannot be started as disk ([..]) is too small for disk ([..])

10585 Informational

Copyback cannot be started on disk ([..]) from disk ([..]) as SAS/SATA mixing is not supported in an array

10586 Informational Firmware update started on disk ([..])

10587 Informational Firmware update completed on disk ([..])

84 RAID Management

10588 Minor

10589 Minor

Firmware update timeout on disk ([..])

Firmware update failed on disk ([..])

10590 Informational Adapter properties changed

10591 Informational Patrol Read properties changed

10592 Informational MDC schedule properties changed

10593 Informational BBU properties changed

10594 Informational MDC resumed on logical drive [..]

10595 Informational Spindown mode enabled

10596 Informational Spindown mode disabled

10597 Informational Spindown delay changed to [..] seconds

10598 Informational Spinup delay changed to [..] seconds

10599 Informational Redundancy build rate changed to [..] percent

10600 Informational Copyback rate changed to [..] percent

Call your local Fujitsu

Helpdesk.

Call your local Fujitsu

Helpdesk.

10601 Minor

Periodic BBU relearn is pending. Please initiate manual learn cycle as automatic learn is not enabled

10602 Informational Disk security key created

10603 Informational Disk security key backed up

10604 Informational Disk security key from escrow, veriﬁed

10605 Informational Disk security key changed

10606 Minor

10607 Minor

Disk security key, re-key operation failed

Disk security key is invalid

10608 Informational Disk security key destroyed

Initiate manual learn cycle as automatic learn is not enabled.

Call your local Fujitsu

Helpdesk.

Call your local Fujitsu

Helpdesk.

10609 Minor Disk security key from escrow is invalid

10610 Informational Logical drive [..] is now secured

10611 Minor

10617 Major

Logical drive [..] is partially secured

10612 Informational Disk ([..]) security activated

10613 Informational Disk ([..]) security disabled

10614 Informational Disk ([..]) is reprovisioned

10615 Informational Disk ([..]) security key changed

10616 Major

Security subsystem problems detected for disk

([..])

Adapter cache preserved for missing or oﬄine logical drive [..]

Call your local Fujitsu

Helpdesk.

For information only.

Call your local Fujitsu

Helpdesk.

Check error messages for related logical drive and resolve problems.

RAID Management 85

10618 Major

Adapter cache preserved for missing or oﬄine logical drives

Check error messages for related logical drives and resolve problems.

10619 Informational

Adapter cache discarded by user for logical drives

10620 Informational Adapter cache destaged for logical drive [..]

10621 Minor

10622 Minor

MDC started on an inconsistent logical drive [..] For information only.

Disk security key failure, cannot access secured conﬁguration

Call your local Fujitsu

Helpdesk.

10623 Minor Disk security pass phrase from user is invalid

Call your local Fujitsu

Helpdesk.

10624 Informational

10625 Minor

Complete RAID conﬁguration written to ﬁle '[..]' on the server

Abnormal shutdown sequence detected

10626 Major Internal hardware error

Call your local Fujitsu

Helpdesk.

10627 Major Internal hardware error during POST

Call your local Fujitsu

Helpdesk.

10628 Informational

Bad block table of disk ([..]) threshold exceeded; table is about to overﬂow

10629 Informational Bad block table of disk ([..]) cleared

10630 Critical Disk ([..]) failed due to bad block table overﬂow Replace aﬀected disk.

10631 Critical Disk ([..]) failure detected during POST

10632 Critical Failure detected during POST

Replace aﬀected disk.

Call your local Fujitsu

Helpdesk.

10633 Critical

Multiple failure on disk ([..]) detected, internal info [..]

10634 Informational BGI started due to adapter exchange

10635 Critical

10636 Critical

Disk ([..]) failure detected by Patrol Read

Disk ([..]) failure detected after successfully building redundancy

Replace aﬀected disk.

10637 Critical

Disk ([..]) failure detected after aborting building redundancy

Disk ([..]) failed 10638 Critical

10639 Critical Disk ([..]) failed, internal info [..]

10640 Informational Adapter [..] was exchanged

10641 Informational Firmware upload started

10642 Informational Firmware upload is executing

10643 Informational Save conﬁguration

10644 Informational Arrays [..] created

10645 Informational Arrays [..] deleted

10646 Informational Trace mode changed

Replace aﬀected disk.

86 RAID Management

10647 Informational Panic dump data deleted

10648 Informational Panic forced

10649 Informational Startup script set

10650 Informational EXBIOS parameter changed

10651 Informational Auto oﬄine recovery mode changed

10652 Informational Clock time changed

10653 Informational Factory shipment settings restored

10654 Informational Internal log cleared

10655 Informational NVRAM log cleared

10656 Informational Unique key refreshed

10657 Informational Write check parameter changed

10658 Minor

10659 Informational New ﬁrmware version [..] detected

10660 Minor

10661 Minor

10662 Major

10663 Major

Operation failed

Array [..] without logical drive left

Incorrect calendar parameter detected

Copyback on logical drive [..] aborted due to bad block table overﬂow

Redundant copy on logical drive [..] aborted due to bad block table overﬂow

10664 Informational Bad block table expansion area initialized

10665 Informational

10666 Informational

10667 Minor

10668 Informational

Bad block table expansion area initialization failed

Disk error detected by write data on logical drive [..] during redundant copy

Bad block detected on disk ([..]), [..]

Multiple failure recovery on disk ([..]) successful

10669 Informational Hot spare available

10670 Informational Patrol Read (one cycle) started on disk ([..])

10671 Informational Patrol Read (one cycle) ﬁnished on disk ([..])

10672 Minor Error detected on disk ([..]), [..]

10673 Informational Error recovered on disk ([..]), [..]

10674 Informational

Media error recovered on disk ([..]) by reassigning new block

1. Replace aﬀected RAID controller.

There is an array which has no logical drive. Create a logical drive to use the array.

Check the scheduler settings.

A large number of uncorrectable bad blocks were detected on logical drive.

1. Restore last good data.

A large number of uncorrectable bad blocks were detected on logical drive.

1. Restore last good data.

For information only.

RAID Management 87

10675 Minor

Disk location in logical drive changed from port

[..] to port [..]

10676 Informational Disk increased by cold swap on port [..]

10677 Informational Disk decreased by cold swap on port [..]

10678 Informational Disk exchanged by cold swap on port [..]

10679 Informational SAS interface rate changed on port [..]

10680 Minor Driver error

10681 Informational Copyback started on disk ([..])

10682 Minor Copyback aborted on disk ([..])

10683 Informational Copyback complete on disk ([..])

10684 Minor

10685 Major

Internal hardware error

For information only.

Check the driver version.

For information only.

1. Replace aﬀected RAID controller.

10686 Major

10687 Minor

10688 Critical

Disk ([..]) bad block table overﬂow error

Error with the remote BBU connector cable detected

Multiple failure on disk ([..]) detected during

POST, internal info [..]

A large number of uncorrectable bad blocks were detected on the disk.

1. Restore last good data.

Replace the BBU data/power cable.

1. Replace aﬀected disk.

2. Replace aﬀected backplane or the data cable.

10689 Critical

Disk ([..]) failed due to SAS/SATA interface error rate too high

1. Replace aﬀected disk.

2. Replace aﬀected backplane or the data cable.

10690 Informational

Operation to mark disk ([..]) oﬄine (redundant copy) started

10691 Informational RAID migration registered for logical drive [..]

10692 Informational MDC aborted by user on logical drive [..]

10693 Informational Alarm set

10694 Major

10695 Critical

10696 Minor

10697 Minor

Logical drive [..] degraded due to bad block table overﬂow

A large number of uncorrectable bad blocks were detected on the disk.

1. Restore last good data.

Disk ([..]) failed due to write error detection by driver

Replace aﬀected disk.

Abnormal capacity of disk ([..]) in logical drive detected

Check the array conﬁguration.

Illegal type of disk ([..]) in logical drive detected

Check the array conﬁguration.

10698 Informational

Background recovery of logical drive [..] could not be started due to bad block table overﬂow

10699 Informational New hot spare ([..]) detected

10700 Major

10701 Minor

Internal PCI hardware error

Bad block table was updated by disk ([..])

Replace aﬀected RAID controller.

For information only.

88 RAID Management

10702 Minor

10703 Minor

10704 Minor

10705 Minor

Invalid disk on port [..] during start up detected For information only.

Invalid disk on port [..] during hot swap detected

For information only.

SMART error on disk ([..]) because internal error threshold on adapter is exceeded

Firmware and driver version mismatch

Note: Disk reports a prefailure. The aﬀected disk might fail soon.

1. Replace the disk during next maintenance.

Check the driver and ﬁrmware version.

10706 Informational Reset received

10707 Informational Operation to mark disk ([..]) oﬄine started

10708 Informational Operation to delete arrays [..] started

10709 Informational Operation to delete logical drive [..] started

10710 Informational

Operation to delete global hot spare on disk

([..]) started

10711 Critical

Disk ([..]) failed since it never entered ready state, [..]

Replace aﬀected disk.

10712 Minor

10713 Minor

10714 Minor

10715 Minor

10716 Minor

Internal software interface error (function: [..])

Device open error (device: [..])

Ioctl send error (details: [..])

Insuﬃcient application memory (function: [..])

System API error (code: [..], function/item: [..])

Note: The driver encountered an error.

1. Check the status of the operating system.

2. Reboot your system.

Note: The driver encountered an error.

1. Check the status of the operating system.

2. Reboot your system.

Note: The driver encountered an error.

1. Check the status of the operating system.

2. Reboot your system.

Note: The driver encountered an error.

1. Check the status of the operating system.

2. Reboot your system.

Note: The driver encountered an error.

1. Check the status of the operating system.

2. Reboot your system.

10717 Critical

10718 Critical

Firmware initialization failed

Firmware recovery failed

10719 Informational Ioctl busy

10720 Informational Logical drive number for boot changed to [..]

10721 Informational

Power state change on disk ([..]) from active to stopped

10722 Informational

Power state change on disk ([..]) from stopped to active

1. Replace aﬀected RAID controller.

RAID Management 89

10723 Informational

Enclosure [..] element (SES code [..]) status changed

10724 Informational Firmware upload process ﬁnished

10725 Informational Disk ﬁrmware update process started

10726 Informational Disk ﬁrmware update process ﬁnished

10727 Informational Diﬀerence in time information changed

10728 Informational Factory shipment settings initialized

10729 Minor

BBU requires reconditioning; please initiate recalibration

1. Initiate manual recalibration process (e.g. via ServerView RAID

Manager). Note: Do not interrupt the charging process by reboots or shutdowns.

2. If problem persists replace BBU.

10730 Informational

Disk ([..]) rebuild not possible as HDD/SSD mix is not supported in an array

10731 Informational

Copyback cannot be started on disk ([..]) from disk ([..]), as HDD/SSD mix is not supported in an array

10732 Minor

Task [..] for object [..] cannot be started (error

[..]). The scheduler will try to start the task again later

10733 Informational Task [..] for object [..] was started by scheduler

10734 Major

Task [..] for object [..] cannot be started (error

[..]). The scheduler has disabled the task

Check the error code. Then check the controller settings, scheduler settings and disk/logical drive/BBU status.

10735 Informational Bad block table of logical drive [..] cleared

10736 Major SAS topology error: [..]

Check the error code. Then check the controller settings, scheduler settings and disk/logical drive/BBU status.

1. Unplug aﬀected disk, wait 30 seconds, reinsert it.

2. Replace aﬀected disk.

3. Replace aﬀected backplane or the data cable.

10737 Minor

10738 Minor

BBU required reconditioning; recalibration initiated

Task [..] for object [..] could not be started at the normal execution time because the service or system was down

For information only.

Check the scheduler settings.

10739 Minor

Task [..] for object [..] cannot be started (error

[..]). The task will be set to the next regular execution time

Check the error code. Then check the controller settings, scheduler settings and disk/logical drive/BBU status.

10740 Informational

Cluster of medium errors corrected for logical drive [..] at [..] (on disk [..] at [..])

10741 Informational Host bus rescan requested

10742 Informational

Adapter repurposed and factory defaults restored

90 RAID Management

10743 Informational Disk security key binding updated

10744 Informational

State change on disk ([..]) from available to copyback

10745 Informational

State change on disk ([..]) from available to

JBOD

10746 Informational

State change on disk ([..]) from failed to copyback

10747 Informational State change on disk ([..]) from failed to JBOD

10748 Informational

State change on disk ([..]) from hot spare to copyback

10749 Informational

State change on disk ([..]) from hot spare to

JBOD

10750 Informational

State change on disk ([..]) from rebuilding to copyback

10751 Informational

State change on disk ([..]) from rebuilding to

JBOD

10752 Informational

State change on disk ([..]) from operational to copyback

10753 Informational

State change on disk ([..]) from operational to

JBOD

10754 Informational

State change on disk ([..]) from copyback to available

10755 Critical

10756 Informational

State change on disk ([..]) from copyback to failed

State change on disk ([..]) from copyback to hot spare

Replace aﬀected disk.

10757 Minor

State change on disk ([..]) from copyback to oﬄine

10758 Informational

State change on disk ([..]) from copyback to operational

10759 Informational

State change on disk ([..]) from copyback to rebuilding

10760 Informational

State change on disk ([..]) from copyback to copyback

10761 Informational

State change on disk ([..]) from copyback to

JBOD

For information only.

10762 Informational

State change on disk ([..]) from JBOD to available

10763 Critical State change on disk ([..]) from JBOD to failed Replace aﬀected disk.

10764 Informational

State change on disk ([..]) from JBOD to hot spare

10765 Minor State change on disk ([..]) from JBOD to oﬄine For information only.

10766 Informational

State change on disk ([..]) from JBOD to operational

RAID Management 91

10767 Informational

State change on disk ([..]) from JBOD to rebuilding

10768 Informational

State change on disk ([..]) from JBOD to copyback

10769 Informational State change on disk ([..]) from JBOD to JBOD

10770 Informational

State change by user on disk ([..]) from available to copyback

10771 Informational

State change by user on disk ([..]) from available to JBOD

10772 Informational

State change by user on disk ([..]) from failed to copyback

10773 Informational

State change by user on disk ([..]) from failed to JBOD

10774 Informational

State change by user on disk ([..]) from hot spare to copyback

10775 Informational

State change by user on disk ([..]) from hot spare to JBOD

10776 Informational

State change by user on disk ([..]) from rebuilding to copyback

10777 Informational

State change by user on disk ([..]) from rebuilding to JBOD

10778 Informational

State change by user on disk ([..]) from operational to copyback

10779 Informational

State change by user on disk ([..]) from operational to JBOD

10780 Informational

State change by user on disk ([..]) from copyback to available

10781 Critical

10782 Informational

State change by user on disk ([..]) from copyback to failed

State change by user on disk ([..]) from copyback to hot spare

10783 Minor

State change by user on disk ([..]) from copyback to oﬄine

10784 Informational

State change by user on disk ([..]) from copyback to operational

10785 Informational

State change by user on disk ([..]) from copyback to rebuilding

Replace aﬀected disk.

For information only.

10786 Informational

State change by user on disk ([..]) from copyback to copyback

10787 Informational

State change by user on disk ([..]) from copyback to JBOD

10788 Informational

State change by user on disk ([..]) from JBOD to available

10789 Critical

State change by user on disk ([..]) from JBOD to failed

For information only.

92 RAID Management

10790 Informational

State change by user on disk ([..]) from JBOD to hot spare

10791 Minor

State change by user on disk ([..]) from JBOD to oﬄine

For information only.

10792 Informational

State change by user on disk ([..]) from JBOD to operational

10793 Informational

State change by user on disk ([..]) from JBOD to rebuilding

10794 Informational

State change by user on disk ([..]) from JBOD to copyback

10795 Informational

State change by user on disk ([..]) from JBOD to

JBOD

10796 Informational

State change on disk ([..]) from oﬄine to copyback

10797 Informational

State change by user on disk ([..]) from oﬄine to copyback

10798 Informational State change on disk ([..]) from oﬄine to JBOD

10799 Informational

State change by user on disk ([..]) from oﬄine to JBOD

10800 Informational

Disk security is in external key management mode

10801 Minor

10804 Major

Disk security failed to communicate with external key management system

10802 Informational Disk ([..]) needs key to be [..] [..]

10803 Minor Logical drive [..] secure failed

Controller encountered a fatal error and was reset

10805 Major

Conﬁguration command could not be committed to disk, please retry

10806 Informational COD on disk ([..]) updated as it was stale

10807 Minor

10808 Minor

Power state change failed on disk ([..]) (from active to stopped)

Power state change failed on disk ([..]) (from stopped to active)

10809 Minor Logical drive [..] is not ready

10810 Informational Logical drive [..] is ready

10811 Informational Test E-mail was sent successfully

10812 Minor Adapter has been replaced during reboot

10813 Minor Enclosure [..] power supply [..] removed

10814 Minor Enclosure [..] power supply [..] turned oﬀ

10815 Informational Enclosure [..] power supply [..] inserted

10816 Informational Enclosure [..] power supply [..] turned on

Call your local Fujitsu

Helpdesk.

For information only.

1. Replace aﬀected RAID controller.

Call your local Fujitsu

Helpdesk.

Replace aﬀected disk.

For information only.

RAID Management 93

10817 Minor

10818 Major

Enclosure [..] temperature sensor [..] below warning threshold

Enclosure [..] temperature sensor [..] below error threshold

1. Check environmental temperature.

10819 Minor

10820 Major

Enclosure [..] temperature sensor [..] above warning threshold

Enclosure [..] temperature sensor [..] above error threshold

1. Check installation of all air ﬂow channels, closed housing, and unblocked louvers.

2. Check environmental temperature.

1. Check installation of all air ﬂow channels, closed housing, and unblocked louvers.

2. Check environmental temperature.

10821 Informational

Power state change on disk ([..]) from active to transition

10822 Minor

Power state change failed on disk ([..]) (from active to transition)

10823 Informational

Power state change on disk ([..]) from stopped to transition

10824 Minor

Power state change failed on disk ([..]) (from stopped to transition)

Replace aﬀected disk.

10825 Informational

Power state change on disk ([..]) from transition to active

10826 Minor

Power state change failed on disk ([..]) (from transition to active)

Replace aﬀected disk.

10827 Informational

10828 Minor

Power state change on disk ([..]) from transition to stopped

Power state change failed on disk ([..]) (from transition to stopped)

Replace aﬀected disk.

For information only.

10829 Minor Reset on-board expander

10830 Informational

Enclosure [..] temperature sensor [..] temperature increase detected

10831 Informational

Enclosure [..] temperature sensor [..] temperature drop detected

For information only.

10832 Informational Enclosure [..] fan [..] speed changed to low

10833 Informational Enclosure [..] fan [..] speed changed to medium

10834 Informational Enclosure [..] fan [..] speed changed to high

10835 Informational

Disk ([..]) will be set oﬄine due to SAS/SATA interface error rate too high

10836 Informational Write cache on disk ([..]) enabled

10837 Informational Write cache on disk ([..]) disabled

10838 Informational

Native Command Queuing (NCQ) on disk ([..]) enabled

10839 Informational

Native Command Queuing (NCQ) on disk ([..]) disabled

10840 Informational Automatic rebuild will use hot spares

10841 Informational

Automatic rebuild will use available disks and hot spares

94 RAID Management

10842 Informational Patrol Read rate changed

10843 Informational Migration rate changed

10844 Informational Initialization rate changed

10845 Informational Consistency check resumed on logical drive [..]

10846 Minor

Consistency check rejected on uninitialized logical drive [..]

Initiate manual MDC to initialize the logical drive.

10847 Informational Initialization suspended on logical drive [..]

10848 Informational Initialization resumed on logical drive [..]

10849 Informational

Logical drive [..] is used for CacheCade with capacity [..] MB

10850 Informational Logical drive [..] is using CacheCade [..]

10851 Informational

Logical drive [..] is no longer using CacheCade

[..]

10852 Minor

CacheCade [..] capacity changed and is now [..]

For information only.

10853 Minor

BBU life has degraded and cannot initiate transparent learn cycles

10854 Informational

MegaRAID Advanced Software Options ([..]) key applied

1. Initiate manual relearn cycle.

2. If problem persists replace BBU.

10855 Informational

MegaRAID Advanced Software Options ([..]) key transferred

10856 Informational

MegaRAID Advanced Software Options serial number [..]

10857 Minor

10858 Minor

MegaRAID Advanced Software Options serial number mismatch. Key Vault serial number is

[..]

BBU cannot support data retention for more than [..] hours

Controller serial number does not match with

MegaRAID Advanced

Software Options key. Apply key to appropriate controller.

BBU capacity is decreased and buﬀering of data in controller cache is limited.

To reach full data retention time replace BBU.

10859 Informational Logical drive [..]: [..] changed

10860 Minor

Logical drive [..] cannot transition to maximum power savings

10861 Informational Driver is loaded and operational

10862 Informational Logical drive [..] mirror broken

10863 Informational Logical drive [..] mirror joined

For information only.

10864 Minor Disk ([..]) link [..] failed in SAS wide port

1. Unplug aﬀected disk, wait 30 seconds, reinsert it.

2. Check/replace cable between controller and aﬀected disk.

3. Check version of RAID controller/iRMC ﬁrmware, and BIOS.

4. Replace aﬀected disk.

RAID Management 95

10865 Informational Disk ([..]) link [..] restored in SAS wide port

10866 Informational Memory module FRU is [..]

10867 Minor FBU power pack is sub-optimal

1. Replace FBU.

10868 Minor

Foreign conﬁguration auto-import did not import any drives

Attempt to import a foreign conﬁg failed.

1. Call your local Fujitsu Helpdesk.

10869 Minor

10870 Minor

FBU ﬁrmware update required

CacheCade [..] capacity exceeds maximum allowed size of [..] MB, extra capacity is not used

1. Call your local Fujitsu Helpdesk.

Call your local Fujitsu

Helpdesk.

10871 Minor Logical drive [..] protection information lost

10872 Informational Diagnostics passed for disk ([..])

1. Call your local Fujitsu Helpdesk.

10873 Major Diagnostics failed for disk ([..])

10874 Informational Server power capability diagnostic test started

Replace aﬀected disk.

10875 Informational

Disk cache settings enabled during rebuild for disk ([..])

10876 Informational

Disk cache settings restored after rebuild for disk ([..])

10877 Informational Disk ([..]) commissioned as emergency spare

10878 Minor

Reminder: Potential non-optimal conﬁguration because disk ([..]) is commissioned as emergency spare

10879 Informational BGI suspended on logical drive [..]

10880 Informational BGI resumed on logical drive [..]

10881 Informational Migration suspended on logical drive [..]

10882 Informational Copyback suspended on disk ([..])

10883 Informational Reminder: MDC suspended on logical drive [..]

For information only.

10884 Informational Reminder: BGI suspended on logical drive [..]

10885 Informational

Reminder: Migration suspended on logical drive

[..]

10886 Informational Reminder: Rebuild suspended on disk ([..])

10887 Informational Reminder: Copyback suspended on disk ([..])

10888 Informational Reminder: Patrol Read suspended

10889 Informational Erase aborted on disk ([..])

10890 Major Erase failed on disk ([..]) (error [..])

10891 Informational Erase progress on disk ([..]) is [..]

10892 Informational Erase started on disk ([..])

10893 Informational Erase ﬁnished on disk ([..])

10894 Informational Erase aborted on logical drive [..]

10895 Major Erase failed on logical drive [..]

10896 Informational Erase progress on logical drive [..] is [..]

1. Call your local Fujitsu Helpdesk.

96 RAID Management

10897 Informational Erase started on logical drive [..]

10898 Informational Erase ﬁnished on logical drive [..]

10899 Minor

Potential leakage during erase on logical drive

[..]

10900 Minor

BBU charging was suspended due to high BBU temperature

10901 Informational FBU ﬁrmware update ﬁnished

10902 Minor FBU ﬁrmware update failed

1. Call your local Fujitsu Helpdesk.

Bring system back to normal operating temperature.

1. Call your local Fujitsu Helpdesk.

10903 Critical

Logical drive [..] access blocked as cached data in CacheCade is unavailable

Call your local Fujitsu

Helpdesk.

10904 Informational

CacheCade disassociate started on logical drive

[..]

10905 Informational

CacheCade disassociate ﬁnished on logical drive [..]

10906 Major

CacheCade disassociate failed on logical drive

[..]

10907 Informational

CacheCade disassociate progress on logical drive [..] is [..]

10908 Informational

CacheCade disassociate aborted by user on logical drive [..]

Call your local Fujitsu

Helpdesk.

10909 Minor

Unexpected sense: Disk ([..]), Key/ASC/ASCQ:

[..]: [..]

10910 Critical

Unexpected sense: Disk ([..]), Key/ASC/ASCQ:

[..]: [..]

10911 Informational Rebuild suspended on disk ([..])

10912 Informational Rebuild resumed on disk ([..])

10913 Informational

Link speed changed on SAS port [..] and PHY

[..]

10914 Minor

MegaRAID Advanced Software Options were deactivated for - [..]

10915 Informational Logical drive [..] is now accessible

10916 Informational Logical drive [..] is using CacheCade

For information only.

Call your local Fujitsu

Helpdesk.

10917 Informational Logical drive [..] is no longer using CacheCade

10918 Minor

10919 Minor

Patrol Read aborted on disk ([..])

Transient error detected while communicating with disk ([..])

Note: If there are errors directly before or after this event, perform the proper recovery action for that error.

1. For information only.

Note: Doesn't aﬀect the normal operation of the system, but can lead to degraded performance due to retries.

1. Replace aﬀected disk/backplane/cable at next service.

RAID Management 97

10920 Informational

Additional information for detected disk ([..]) ﬁrmware version: [..], serial number [..]

10921 Informational RAID Manager started

10922 Informational RAID Manager stopped

10923 Informational

State change on disk ([..]) from shielded to available

10924 Minor

10925 Critical

State change on disk ([..]) from shielded to oﬄine

State change on disk ([..]) from shielded to failed

10926 Informational

State change on disk ([..]) from shielded to hot spare

10927 Informational

State change on disk ([..]) from shielded to rebuilding

10928 Informational

State change on disk ([..]) from shielded to operational

10929 Informational

State change on disk ([..]) from shielded to copyback

10930 Informational

State change on disk ([..]) from shielded to

JBOD

Replace aﬀected disk.

10931 Critical

10932 Critical

10933 Critical

10934 Critical

10935 Critical

10936 Critical

10937 Critical

10938 Critical

10939 Critical

State change on disk ([..]) from shielded to shielded

State change on disk ([..]) from available to shielded

State change on disk ([..]) from oﬄine to shielded

State change on disk ([..]) from failed to shielded

State change on disk ([..]) from hot spare to shielded

State change on disk ([..]) from rebuilding to shielded

State change on disk ([..]) from operational to shielded

State change on disk ([..]) from copyback to shielded

State change on disk ([..]) from JBOD to shielded

1. Wait until checking in shielded state is completed.

2. Perform action according to upcoming status.

1. Wait until checking in shielded state is completed.

2. Perform action according to upcoming status.

1. Wait until checking in shielded state is completed.

2. Perform action according to upcoming status.

1. Wait until checking in shielded state is completed.

2. Perform action according to upcoming status.

1. Wait until checking in shielded state is completed.

2. Perform action according to upcoming status.

1. Wait until checking in shielded state is completed.

2. Perform action according to upcoming status.

1. Wait until checking in shielded state is completed.

2. Perform action according to upcoming status.

1. Wait until checking in shielded state is completed.

2. Perform action according to upcoming status.

1. Wait until checking in shielded state is completed.

2. Perform action according to upcoming status.

98 RAID Management

10940 Informational

State change by user on disk ([..]) from shielded to available

10941 Minor

State change by user on disk ([..]) from shielded to oﬄine

10942 Critical

State change by user on disk ([..]) from shielded to failed

10943 Informational

State change by user on disk ([..]) from shielded to hot spare

Replace aﬀected disk.

10944 Informational

State change by user on disk ([..]) from shielded to rebuilding

10945 Informational

State change by user on disk ([..]) from shielded to operational

10946 Informational

State change by user on disk ([..]) from shielded to copyback

10947 Informational

State change by user on disk ([..]) from shielded to JBOD

10948 Critical

State change by user on disk ([..]) from shielded to shielded

10949 Critical

10950 Critical

10951 Critical

10952 Critical

10953 Critical

10954 Critical

10955 Critical

10956 Critical

10957 Critical

10958 Critical

Replace aﬀected disk.

State change by user on disk ([..]) from available to shielded

State change by user on disk ([..]) from oﬄine to shielded

State change by user on disk ([..]) from failed to shielded

State change by user on disk ([..]) from hot spare to shielded

State change by user on disk ([..]) from rebuilding to shielded

State change by user on disk ([..]) from operational to shielded

State change by user on disk ([..]) from copyback to shielded

State change by user on disk ([..]) from JBOD to shielded

Internal error

Incompatible PCI slot bandwidth

1. Wait until checking in shielded state is completed.

2. Perform action according to upcoming status.

1. Wait until checking in shielded state is completed.

2. Perform action according to upcoming status.

1. Wait until checking in shielded state is completed.

2. Perform action according to upcoming status.

1. Wait until checking in shielded state is completed.

2. Perform action according to upcoming status.

1. Wait until checking in shielded state is completed.

2. Perform action according to upcoming status.

1. Wait until checking in shielded state is completed.

2. Perform action according to upcoming status.

1. Wait until checking in shielded state is completed.

2. Perform action according to upcoming status.

1. Wait until checking in shielded state is completed.

2. Perform action according to upcoming status.

If problem persists after reboot, call your local Fujitsu

Helpdesk.

Reinstall adapter in a compatible PCI slot.

RAID Management 99

10959 Major

10960 Major

10961 Major

10962 Critical

10963 Critical

10964 Critical

10965 Critical

10966 Critical

10967 Minor

10968 Minor

10969 Minor

10970 Minor

10971 Minor

10972 Minor

10973 Minor

10974 Minor

10975 Minor

10976 Minor

Write performance reduced

Write operations disabled

Temperature close to error threshold

Temperature above error threshold

Internal voltage out of range

Auxiliary voltage out of range

Flashback error

Non-correctable PCI errors detected

Temperature above warning threshold

Memory is close to wearing out

Non-optimal PCI slot bandwidth

Correctable PCI errors detected

Power loss protection disabled

Write regulation activated due to power constraints of PCI slot

Write regulation activated due to high temperature

Write regulation activated to ensure adapter lifespan

Running in minimal status

PCI power budget alarm

Check additional status property for more information.

Increase cooling or reduce write load.

If problem persists after reboot, call your local Fujitsu

Helpdesk.

If problem persists after reboot, call your local Fujitsu

Helpdesk.

1. Backup data from aﬀected adapter.

2. Replace adapter as soon as possible.

3. Restore data.

If problem persists after reboot, call your local Fujitsu

Helpdesk.

Increase cooling or reduce write load.

Formatting to a smaller size will free up reserve.

Reinstall adapter in an optimal PCI slot.

For information only.

Activate power loss protection.

If this condition persists, switch to a higher powered

PCI slot or attach external power cable.

If this condition persists, increase air ﬂow, lower room temperature or reduce write load.

If this condition persists, reduce write load.

Check additional status property for more information.

Switch to a higher powered

PCI slot or attach external power cable.

100 RAID Management

10977 Minor

10978 Minor

10979 Minor

10980 Informational Adapter normal

10981 Critical

LEB map missing

Update in progress

Reserves depleted

Attach failed

If problem persists after reboot, call your local Fujitsu

Helpdesk.

The adapter will not be usable until formatting is complete.

Formatting to a smaller size will free up reserve.

If problem persists, call your local Fujitsu Helpdesk.

10982 Minor Detach failed

1. Force detach.

2. If problem persists, call your local

Fujitsu Helpdesk.

10983 Informational Attached

10984 Critical Detached

10985 Informational Format of disk ([..]) changed

10986 Informational File log cleared

10987 Informational Disk ([..]) will be set oﬄine due to SMART error

For information only.

10988 Informational

Disk ([..]) will be set oﬄine due to too many unexpected sense events

10989 Minor

Protection information error in cache for logical drive [..] at LBA [..]

10990 Minor Flash downloaded image is not supported

Call your local Fujitsu

Helpdesk.

Call your local Fujitsu

Helpdesk.

10991 Informational BBU mode selected - [..]

10992 Informational

Periodic BBU relearn was missed, and rescheduled to [..]

10993 Informational Adapter reset requested by host

10994 Informational Adapter reset requested by host, completed

10995 Major

10996 Major

10997 Minor

10998 Major

10999 Minor

11000 Major

11001 Critical

L3 cache error has been detected

L2 cache error has been detected

Adapter booted in headless mode with errors

Adapter booted to safe mode due to critical errors

Warning during boot - [..]

Critical error during boot - [..]

Fatal error during boot - [..]

Call your local Fujitsu

Helpdesk.

Call your local Fujitsu

Helpdesk.

Call your local Fujitsu

Helpdesk.

Call your local Fujitsu

Helpdesk.

Call your local Fujitsu

Helpdesk.

Call your local Fujitsu

Helpdesk.

Call your local Fujitsu

Helpdesk.

RAID Management 101

11002 Informational

Peer adapter has joined high availability domain (ID: [..])

11003 Major

Peer adapter has left high availability domain

(ID: [..])

11004 Informational Disk ([..]) is managed by peer adapter

11005 Informational Disk ([..]) is managed by local adapter

11006 Informational Logical drive [..] is managed by peer adapter

11007 Informational Logical drive [..] is managed by local adapter

11008 Minor

11011 Minor

11012 Major

11013 Major

11014 Major

11015 Minor

Logical drive [..] has a conﬂict in high availability domain

11009 Informational Logical drive [..] access is shared

11010 Informational Logical drive [..] access is exclusive

Logical drive [..] is incompatible in the high availability domain

Adapters in the high availability domain are incompatible

Adapter properties are incompatible between local and peer adapters

Firmware versions do not match in the high availability domain

11016 Minor

MegaRAID Advanced Software Options [..] do not match in the high availability domain

11017 Informational High availability cache mirror is online

11018 Major

Peer adapter is incompatible

High availability cache mirror is oﬄine

Call your local Fujitsu

Helpdesk.

Call your local Fujitsu

Helpdesk.

Call your local Fujitsu

Helpdesk.

Call your local Fujitsu

Helpdesk.

Call your local Fujitsu

Helpdesk.

Call your local Fujitsu

Helpdesk.

Call your local Fujitsu

Helpdesk.

Call your local Fujitsu

Helpdesk.

Call your local Fujitsu

Helpdesk.

11019 Critical

11020 Minor

11021 Minor

Logical drive [..] access blocked as cached data from peer adapter is unavailable

FBU power pack is not supported. Please replace the pack

Disk ([..]) temperature ([..] C) is above warning threshold

11022 Major

Disk ([..]) temperature ([..] C) is above critical threshold

11023 Informational Disk ([..]) temperature ([..] C) is normal

11024 Minor Disk ([..]) IOs are being throttled

Call your local Fujitsu

Helpdesk.

Call your local Fujitsu

Helpdesk.

Call your local Fujitsu

Helpdesk.

Call your local Fujitsu

Helpdesk.

Call your local Fujitsu

Helpdesk.

11025 Informational Disk ([..]) IOs are normal (no throttling)

11026 Informational

Disk ([..]) has [..] percent life left. Life left thresholds - warning: [..] percent, critical: [..] percent

102 RAID Management

11027 Minor

11028 Major

11029 Major

11030 Minor

Disk ([..]) life left ([..] percent) is below optimal.

Life left thresholds - warning: [..] percent, critical: [..] percent

Call your local Fujitsu

Helpdesk.

Disk ([..]) life left ([..] percent) is critical. Life left thresholds - warning: [..] percent, critical:

[..] percent

Call your local Fujitsu

Helpdesk.

Disk ([..]) failure, device locked-up

Driver needs to be upgraded [..]

Call your local Fujitsu

Helpdesk.

Call your local Fujitsu

Helpdesk.

11031 Minor

11032 Minor

Direct communication with peer adapter(s) was not established. Please check proper cable connections

Firmware image does not contain signed component

11033 Minor

Authentication failure of the signed ﬁrmware image

11034 Informational Setting logical drive [..] as boot device

11035 Informational Setting disk ([..]) as boot device

11036 Informational The BBU temperature is changed to [..] C

11037 Informational The adapter temperature is changed to [..] C

Call your local Fujitsu

Helpdesk.

Call your local Fujitsu

Helpdesk.

Call your local Fujitsu

Helpdesk.

11038 Major

11039 Minor

11040 Major

FBU capacity is too less to support data backup. Write-back logical drives will be converted to Write-through

FBU data backup capacity has decreased, consider replacement

FBU device failed, cannot support data retention

Call your local Fujitsu

Helpdesk.

Call your local Fujitsu

Helpdesk.

Call your local Fujitsu

Helpdesk.

11041 Informational Boot device reset, setting target ID as invalid

11042 Minor

Write-back Nytro cache size mismatch between the servers. The Nytro cache size was adjusted to [..] GB

11043 Minor

Logical drive [..] is not shared between servers but assigned for caching. Write-back Nytro cache content of the logical drive will be mirrored

Call your local Fujitsu

Helpdesk.

Call your local Fujitsu

Helpdesk.

11044 Informational Power [..] watts usage base IOs throttle started

11045 Informational Power base IOs throttle stopped

11046 Informational Adapter tunable parameter(s) changed

11047 Informational

Adapter operating temperature within normal range, full operation restored

11048 Minor

Temperature threshold exceeded for the adapter. This may indicate inadequate cooling in the system chassis. Adapter has switched to lower performance mode

Call your local Fujitsu

Helpdesk.

RAID Management 103

11049 Minor

11050 Major

Adapter defect or no adapter detected on host

[..]

11051 Informational Connection to host [..] established

11052 Informational

Adapter supports high availability mode, currently functioning with high availability feature set

11053 Informational

Adapter supports high availability mode, currently functioning with single adapter feature set

11054 Major

FBU components mismatch. Write-back logical drives will be converted to write-through

11055 Informational Adapter has entered maintenance mode

11056 Informational Adapter has returned to normal mode

11057 Informational Topology is in [..] mode

11058 Major

11059 Major

Cannot enter [..] mode because [..] logical drive [..] would not be supported

Cannot enter [..] mode because [..] disk ([..]) would not be supported

11060 Informational Connection to host [..] deleted

11061 Informational Connection to host [..] modiﬁed

11062 Informational

BBU relearn requires to change WriteBack logical drives to WriteThrough

11063 Informational Alarm silenced

11064 Informational [..] cache ﬂush started

11065 Informational [..] cache ﬂush ﬁnished

11066 Informational [..] cache ﬂush aborted by user

11067 Informational Adapter personality changed

11068 Informational Conﬁguration automatically created by [..]

11069 Informational Software zone enabled

11070 Informational Software zone disabled

11071 Major

Initialization aborted on logical drive [..] due to adapter reset

11072 Major

Connection to host [..] failed

Peer adapter security key mismatch

Call your local Fujitsu

Helpdesk.

Call your local Fujitsu

Helpdesk.

Call your local Fujitsu

Helpdesk.

Call your local Fujitsu

Helpdesk.

Call your local Fujitsu

Helpdesk.

Call your local Fujitsu

Helpdesk.

Call your local Fujitsu

Helpdesk.

11073 Informational Peer adapter security key match

11074 Informational

Logical drive [..] is now compatible in the high availability domain

11075 Informational Disk ([..]) operation delayed

11076 Informational Logical drive [..] operation delayed

11077 Informational Message: [..]

104 RAID Management

11078 Informational Virtual function map: [..]

11079 Critical

Solution will shut down due to maximum temperature threshold exception. This may indicate inadequate system cooling

Call your local Fujitsu

Helpdesk.

11080 Informational Shutdown chassis command received from host

11081 Informational Restart chassis command received from host

11082 Informational Adapter information changed

11083 Minor

Hidden policy not set for all logical drives in the array

Call your local Fujitsu

Helpdesk.

11084 Minor

Disk ([..]) is not an enterprise class self encrypting disk. Encryption capability of the drive will be disabled

11085 Informational

Adapter ﬁrmware was updated with force option

11086 Informational

Write regulation activated due to power constraints of PCI slot

11087 Informational Unactivated ﬁrmware available

Call your local Fujitsu

Helpdesk.

11088 Minor

11089 Minor

11090 Minor

11091 Minor

11092 Minor

Average write usage of disk ([..]) above speciﬁcation

11093 Informational New adapter detected

11094 Minor

Reliability degraded

Estimated lifetime of disk ([..]) below 60 days

Wear level count of disk ([..]) above threshold

Reserve space of disk ([..]) below threshold

Adapter removed

Call your local Fujitsu

Helpdesk.

1. Backup your data.

2. Replace aﬀected disk as soon as possible.

1. Backup your data.

2. Replace aﬀected disk as soon as possible to avoid malfunction (read only mode).

1. Backup your data.

2. Replace aﬀected disk as soon as possible to avoid malfunction (read only mode).

Decrease amount of write accesses to the disk.

Note: Only informational if adapter was removed by user.

RAID Management 105

6.3 Errors

20025

20026

20027

20028

20029

20030

20031

20032

20033

20034

20008

20009

20010

20011

20012

20013

20014

20015

20016

20017

20018

20019

20020

20021

20022

20023

20024

Error code

20000

20001

Unspeciﬁed error occurred.

No supported hardware found.

20002

20003

20004

20005

20006

20007

Invalid command.

Vendor API call failed.

Invalid property.

Invalid operation.

Invalid parameter.

Memory allocation failed.

Invalid object ID.

Invalid object type.

Property type / value mismatch.

Lock initialization failed.

Vendor API initialization failed.

Event initialization failed.

Meaning

Conﬁguration key/value pair not found.

Library loading failed.

Library symbol not found.

MPX initialization in progress.

Write access denied.

Consistency check not supported with this RAID level.

Logical drive busy.

Consistency check not suspended.

Consistency check not running.

Rebuild not supported with this RAID level.

Logical drive not operational.

Rebuild not running.

Rebuild not suspended.

Could not write, the ﬁle already exists.

Invalid characters in ﬁlename.

Could not open ﬁle.

Can only start in manual mode.

Adapter busy.

No disks found.

Patrol Read start in progress.

Patrol Read not running.

106 RAID Management

20035

20036

20037

20038

20039

20040

20041

20042

20043

20044

20045

20046

20047

20048

20049

20050

20051

20052

20053

20054

20055

20056

20057

20058

20059

20060

20061

20062

20063

20064

20065

20066

20067

20068

20069

20070

20071

20072

Alarm disabled.

Recalibration not needed.

Recalibration not running.

Initialization not running.

No BGI running.

Location running.

Location not running.

Disk not available.

Disk not hot spare.

Disk failed.

Reboot required.

Disk(s) too small.

Not enough disk(s) speciﬁed.

Resulting disk space too small.

No logical drive found.

Disk not online.

Disk not oﬄine.

Logical drive not oﬄine.

Migration not running.

Disk busy.

Veriﬁcation not running.

Parse error.

Conﬁguration mismatch.

Logical drive not degraded.

Disk missing.

Selected Segment/drive not usable for the new logical drive.

All segments of a logical drive must be attached to the same channel/port.

All segments of a logical drive must be attached to the same array.

The maximum logical drive count per channel/port is limited.

The maximum logical drive count is limited.

Not enough disks to create a logical drive.

Too many disks to create a logical drive.

Logical drive not creatable.

Disks too small to create the logical drive.

Estimated segment size is smaller than minimum supported segment size.

Segment is too small for the logical drive.

Add drives for creating a logical drive.

All arrays full.

RAID Management 107

20073

20074

20075

20076

20077

20078

20079

20080

20081

20082

20083

20084

20085

20086

20087

20088

20089

20090

20091

20092

20093

20094

20095

20096

20097

20098

20099

20100

20101

20102

20103

20104

20105

20106

20107

20108

20109

20110

Invalid number of arrays.

No unconﬁgured disks.

All arrays full and/or no unconﬁgured disks.

Invalid number of disks.

No space on disk.

Disk already in use.

Disk not available.

Invalid disks speciﬁed for array.

Invalid span depth.

Invalid arrays for span depth.

Invalid array count.

Invalid array reference.

Invalid size.

Invalid logical drive count.

Target IDs exhausted.

Invalid RAID level.

Invalid hot spare count.

Spanning not possible.

Number of spans exhausted.

Number of drives per span exhausted.

No conﬁguration available.

Speciﬁed size too small.

Maximum number of drives to create the disk reached.

Segment is too large for the logical drive.

Previous span must use its full capacity if further spans need to be created.

Current span will be too large to add the disk.

Other span is too large to add the disk.

The supported stripe size depends on the number of disks used.

This stripe size is too large for the number of disks in the logical drive.

There are segments which can never be used for another logical drive.

Alarm not available.

Patrol Read disabled.

Patrol Read running.

Migration running.

Initialization running.

Consistency check running.

Not enough disks for migration.

Disk cannot guard any logical drive as hot spare.

108 RAID Management

20111

20112

20113

20114

20115

20116

20117

20118

20119

20120

20121

20122

20123

20124

20125

20126

20127

20128

20129

20130

20131

20132

20133

20134

20135

20136

20137

20138

20139

20140

20141

20142

20143

20144

20145

20146

20147

20148

MDC running.

MDC not supported with this RAID level.

MDC not running.

MDC not suspended.

Recalibration running.

Diﬀerent disk types in logical drive not supported.

Diﬀerent disk types in enclosure not supported.

Hotplug of enclosures not supported.

It is not possible to import this foreign conﬁguration, it can be cleared only.

Clear of foreign conﬁguration failed.

Timeout

Diﬀerent disk media types in logical drive not supported.

Disk cannot be used for conﬁguration.

Currently the action can not be performed. It will be tried to start the action later.

The service is shutting down.

Too many instances are already running.

Only stripe sizes above 8K are allowed for this RAID level with 3 disks per span.

Plugin busy.

BBU busy.

Port busy.

Enclosure busy.

Processor busy.

Foreign configuration incomplete. Try different index or clear this configuration.

Disk used by LMD

No hardware with supported ﬁrmware found.

Unexpected error code.

Service not available.

Send / receive failed.

gethostname() failed.

Not implemented.

Action not executed.

Error during processing.

Mailbox unavailable.

Invalid mailbox name.

Bad command sequence.

User not local.

Transaction failed.

Authentication not supported.

RAID Management 109

20149

20150

20151

20152

20153

20154

20155

20156

20157

20158

20159

20160

20161

20162

20163

20164

20165

20166

20167

Encryption required for requested authentication mechanism.

Authentication mechanism is too weak.

A password transition is needed.

TLS not available on server for temporary reason.

TLS not supported by server.

Connection refused.

Bad username or password.

Could not open TLS socket.

Undeﬁned recipient mail.

Need at least one recipient.

No sender.

No message subject.

No more connections to servers supported.

Could not connect to server.

No or invalid response from server.

Logical drive not initialized.

Initialization not suspended.

CacheCade supports SSD's only.

No trial software options found.

110 RAID Management

7 Help

7.1 Help

You can access the help system by clicking on Help on the right of the 1st menu line.

Here you can use Contents and Index to start an independent browser session in which you can view this help online. The menu item

Info about ServerView RAID Manager provides you with version information on the product.

An introcdution to the online help and which options you can use there is contained under Help in the table of contents.

7.2 Online Help

To be able to use the help eﬀectively you should familiarize yourself brieﬂy with the navigation. The online help window consists of four areas: Header, Navigation Bar, Overview and Description Field. The areas contain some functions which are described below.

Header

Navigation Bar

Overview Description Field

7.2.1 Header

The header contains the logo and the application name.

7.2.2 Navigation Bar

These buttons enable you to activate and deactivate the Overview.

This button enables you to open the table of contents for the help.

Individual help topics are selected and pulled down in the table of contents using .

All help topics are opened with and closed with .

The individual help texts in the help topics are displayed by clicking on in the Description Field.

This button enables you to open the glossary for the help.

RAID Management 111

You search for the required keyword by selecting a button or scrolling.

You can activate the search function in the help using this button.

After you have entered the search criterion the relevant search results are displayed in the Description Field.

This button enables you to print out the help text displayed in the Description Field.

These buttons enable you to navigate within the pages called so far.

You use them to page forward or back one page.

This button enables you to quit the online help and close the window.

7.2.3 Overview

The overview contains the table of contents, the glossary or the search function depending on what you selected in the Navigation

Bar.

7.2.4 Description Field

The selected help text is displayed in the description ﬁeld.

You can print out the displayed text using the button.

To print the entire help in manual format you must select the Show Manual as PDF entry in the table of contents, save the ﬁle if required, and then print the text using the print function of a PDF reader.

7.3 amCLI

amCLI is a command line interface to ServerView RAID Manager. It can be used to create, delete or manage RAID arrays or manage

ServerView RAID Manager itself from the command line or from a script.

At the top level, amCLI has the following command options:

-c|--create: create a logical drive

-d|--delete: delete last logical drive

-e|--exec: execute a device-speciﬁc command

-g|--get: get a target's property

-i|--import: import a certiﬁcate

-l|--list: list information

-m|--migrate: migrate a RAID array to another RAID level

-r|--restore: restore the state from a ﬁle

-s|--set: set a target's property to a given value

-w|--write: write the current state to a ﬁle

112 RAID Management

mod

-Z|--zap: zap a target

-?|--help: give a short help

Up to one of these may be speciﬁed, -?being the default.

7.3.1 Addressing scheme

All objects that can be manipulated by this command (the entire ServerView RAID Manager subsystem, adapters, physical drives, and logical drives i.e. RAID arrays) are identified by two numbers separated by a slash (/) character: the first number specifies a module and the second number is a (0-based) index: <mod/idx>. In this documentation, such a pair of numbers is referred to as the address of an object.

Currently, the following module numbers are supported:

Module

ServerView RAID Manager

Avago MegaRAID SAS Adapter, SAS/SAS2/SAS3 IT/IR Adapter, MegaSR

Fujitsu Aries SAS Adapter

Linux Software RAID

Avago MegaRAID SAS Adapter, SAS/SAS2/SAS3 IT/IR Adapter (via CIM)

AMD Chipset RAID

Fusion-io PCIe SSD's

Intel PCIe SSD's

Note that index values need not be consecutive (e.g if 27/5 and 27/7 exist, 27/6 must not necessarily exist, too), are relative to a module (i.e. 26/5 and 27/5 can both exist at the same time) and the numbering continues between adapters, logical and physical drives (i.e. 27/5 and 27/10 can be adapters, 27/6 and 27/7 can be physical drives and 27/8 and 27/9 can be logical drives).

In the following,

SysIdx is an index of the "Server View RAID" module (i.e. mod will be 21),

AdpIdx is an index of an adapter module (i.e. <mod/AdpIdx> must be the address of an adapter),

PDIdx is an index of a physical drive (i.e. <mod/PDIdx> must be the address of a physical drive),

LDIdx is an index of a logical drive (i.e. <mod/LDIdx> must be the address of a logical drive), and idx is not restricted to a speciﬁc object type (i.e. <mod/idx> can be be the address of a module, a logical or a physical drive, as appropriate in the context).

Use amCLI -l to ﬁnd the addresses of objects you wish to use.

7.3.2 Create a logical drive

Before creating a logical drive, you must decide which RAID level to use, what parameters the chosen RAID level requires and what

(physical and/or logical) drives this logical drive should consist of. It is assumed here that you are familiar with the concepts of RAID and the various RAID levels.

7.3.2.1 Synopsis amCLI [-c|--create] <mod/AdpIdx> raid=<raidLevel> parameters <mod/PDIdx>+

7.3.2.2 Parameters

<mod/AdpIdx>: the address of the adapter which will manage the logical drive created,

<raidLevel>: the desired RAID level of the logical drive to be created, (at present, RAID levels 0, 1, 01, 1e, 3, 4, 5, 5e, 5ee, 6,

10, 50, 60, "concat", and "single" are supported, but not all adapters support all RAID levels and some RAID levels are only supported by a single adapter type),

parameters depend upon the raidLevel chosen: span=<spanCount>: number of (sub-)logical drives this logical drive should be combined of, stripe=<stripeSize>: how much data should be stored on a physical drive before continuing on the next physical drive,

<raidFlag>=<flag>: additional settings that can be passed to the adapter during logical drive creation, e.g. write cache mode, readahead mode, ... (e.g. read_mode=adaptive) size=<megabytes>: the size of the resulting logical drive.

<mod/PDIdx>+: a (non-empty) list of addresses of physical and/or logical drives that should be used when creating the new logical drive.

RAID Management 113

Use amCLI --help create <mod/AdpIdx> to ﬁnd out which RAID-levels and parameters the speciﬁed adapter supports.

7.3.2.3 Example

To create a RAID-5 array consisting of physical drives 32/5, 32/6, and 32/7 on the Avago MegaRAID adapter 32/1 with default parameters, the following command could be used:

# amCLI -c 32/1 raid=5 32/5 32/6 32/7

A conﬁrmation is then required to execute this command (the input is treated case-insensitive):

Are you sure to create a new Logical Drive on Adapter '32/1'?

Type YES to confirm _

(Note that, depending on the command interpreter used, it may be possible to pipe a "yes" into this command.)

7.3.2.4 Note

ServerView RAID Manager will allocate an address for the new logical drive. Use amCLI -l to determine the address.

7.3.3 Delete last logical drive

This command deletes the logical drive with the highest logical drive ID on a given adapter (which is usually the logical drive most recently created).

7.3.3.1 Synopsis amCLI [-d|--delete] <mod/AdpIdx>

7.3.3.2 Parameters

<mod/AdpIdx>: the address of the adapter whose most recently created logical drive should be deleted.

7.3.3.3 Example

To delete the logical drive created above immediately after having created it, use

# amCLI -d 32/1

Again, an explicit conﬁrmation is required to execute this command:

Are you sure to delete the last Logical Drive on Adapter '32/1'?

Type YES to confirm _

7.3.4 Execute operation on a device

This command starts execution of a device-speciﬁc command on a given device.

7.3.4.1 Synopsis amCLI [-e|--exec] <mod/idx> <operation> <param>*

7.3.4.2 Parameters

<mod/idx>: the address of the object that should execute the operation,

<operation>: the command to execute, and

<param>*: a (possibly empty) list of arguments required for the given command.

To ﬁnd out which operations are supported by a given object and what additional parameters they require, use amCLI [-?|--help] exec <mod/idx>

7.3.4.3 Examples

# amCLI -? exec 32/26 amCLI v5.7.0

Usage:

-e | --exec <32/PDIdx> locate

114 RAID Management

-e | --exec <32/PDIdx> stop_location

-e | --exec <32/PDIdx> create_global_hot_spare

-e | --exec <32/PDIdx> delete_global_hot_spare

-e | --exec <32/PDIdx> create_dedicated_hot_spare <mod/LDIdx>

-e | --exec <32/PDIdx> delete_dedicated_hot_spare

-e | --exec <32/PDIdx> make_online

-e | --exec <32/PDIdx> make_offline

-e | --exec <32/PDIdx> make_ready

-e | --exec <32/PDIdx> replace_missing_disk <mod/LDIdx>

# amCLI -e 32/26 locate

7.3.5 Get property

This command retrieves the value of a given property of a given object.

7.3.5.1 Synopsis amCLI [-g|--get] <mod/idx> <property>

7.3.5.2 Parameters

<mod/idx>: the address of the object and

<property>: the name of the property to retrieve.

Use amCLI -? get to find out which object classes support which properties in general or amCLI -? get <mod/idx> to find out which properties a specific object supports.

7.3.5.3 Examples

# amCLI -? get 32/2 amCLI v5.7.0

Usage:

-g | --get <32/LDIdx> activity

-g | --get <32/LDIdx> status

-g | --get <32/LDIdx> disk_cache_mode

-g | --get <32/LDIdx> bgi

...

# amCLI -g 32/2 status

Operational

7.3.6 Import a certiﬁcate

This command imports a certiﬁcate.

7.3.6.1 Synopsis amCLI [-i|--import] <certificate file> <private key file>

7.3.6.2 Parameters

<certificate file>: the name of a ﬁle containing a certiﬁcate.

<private key file>: the name of a ﬁle containing the private key.

7.3.6.3 Example

# amCLI -i cert.pem key.pem

7.3.7 List information

This command lists information available about a given object.

7.3.7.1 Synopsis amCLI [-l|--list] [all|struct|<mod/idx>]

RAID Management 115

7.3.7.2 Parameters all lists the structure of the RAID subsystems with some information about each item struct, which is the default, lists the structure of the RAID subsystems without additional information, and

<mod/idx>: the address of the object of which extensive information is required.

7.3.7.3 Example

# amCLI -l struct

21/3: System, 'hostname'

32/1: SAS Adapter 0, 'Avago MegaRAID SAS PCI Express(TM) ROMB (0)'

32/2: Logical Drive 0, 'LogicalDrive_0', RAID-0, 69472MB

32/3: SAS Port 0

32/11: Physical Drive 0, 'SEAGATE ST373454SS (0)', 69472MB

32/4: SAS Port 1

32/12: Physical Drive 1, 'SEAGATE ST336754SS (1)', 34464MB

...

7.3.8 Migrate a logical drive to a new RAID level

This command changes the RAID level of a logical drive, if this is possible in the current conﬁguration and if it is supported by the adapter controlling the logical drive.

7.3.8.1 Synopsis amCLI [-m|--migrate] <mod/LDIdx> [raid=<raidLevel>] parameters <mod/PDIdx>*

7.3.8.2 Parameters

<mod/LDIdx>: the address of the logical drive to migrate,

<raidLevel>: the desired new RAID level, and

<mod/PDIdx>*: a (possibly empty) list of addresses of additional physical drives to use.

parameters are speciﬁc to the desired new RAID level. At present, only the stripeSize can be changed during migration.

To ﬁnd out which RAID levels a given logical drive can be migrated to and whether additional physical drives may be needed, use amCLI -? migrate <mod/LDIdx>

7.3.8.3 Examples

# amCLI -l 32/2

32/2: Logical Drive 0, 'LogicalDrive_0', RAID-0, 69472MB

Parents: 1

Children: -

Containers: 1

Drives: 1 --> ( 32/11 )

Properties:

Unique ID: PCI:Bus=2&Device=14&Function=0&ID=0

Logical Drive Number: 0

Name: LogicalDrive_0, settable

Logical Size: 69472 MB

Physical Size: 69472 MB

RAID Level: RAID-0

...

# amCLI -? migrate 32/2 amCLI v5.7.0

Usage:

-m | --migrate 32/2

[raid=(0|1|5)]

(<PDIdx>)+

This means that logical drive 32/2 (a RAID-0 logical drive) can only be migrated to RAID levels 0, 1 or 5 and it may be possible to include additional physical drives (in this speciﬁc case they would be even required to migrate to RAID levels 1 or 5).

# amCLI -m 32/2 raid=1 32/8

A conﬁrmation is again required:

Are you sure to modify Logical Drive '32/2' on Adapter '32/1'?

116 RAID Management

Type YES to confirm _

7.3.9 Restore state

This command restores the state of the RAID conﬁguration from a ﬁle previously created by amCLI -w.

7.3.9.1 Synopsis amCLI [-r|--restore] <filename>

7.3.9.2 Parameters

<filename>: the name of a ﬁle containing a description of the conﬁguration

7.3.9.3 Example

# amCLI -r OldState

Again, an explicit conﬁrmation is required:

Are you sure to restore the configuration?

Type YES to confirm _

7.3.9.4 Warning

Restoring the state of the adapter managing the system disk may render the system unusable!

7.3.10 Set property

This commands sets the given property of a given object to a given new value.

7.3.10.1 Synopsis amCLI [-s|--set] <mod/idx> <property> <value>

7.3.10.2 Parameters

<mod/idx>: the address of the object,

<property>: the property name, and

<value>: the new property value.

Use amCLI -? set to ﬁnd out which device classes support which properties in general or amCLI -? set <mod/idx> to ﬁnd out which properties a given device supports.

7.3.10.3 Examples

# amCLI -? set 32/2 amCLI v5.7.0

Usage:

-s | --set <32/LDIdx> name <string>

...

# amCLI -g 32/2 name

LogicalDrive_0

# amCLI -s 32/2 name 'OS disk'

# amCLI -g 32/2 name

OS disk

7.3.11 Write state

This command saves the internal state of a speciﬁed object into a given ﬁle or prints it to the standard output.

7.3.11.1 Synopsis amCLI [-w|--write] <mod/SysIdx> [<file>] amCLI [-w|--write] <mod/AdpIdx> [<file>]

RAID Management 117

7.3.11.2 Parameters

<mod/SysIdx>: the system's address (i.e. 21/0),

<mod/AdpIdx>: the address of an adapter,

<file> the name of a ﬁle in which the state will be stored. If no ﬁle name is given, the state is sent to stdout.

7.3.11.3 Example

# amCLI -w 32/1

<SASAdapter UniqueID="PCI:Bus=2&Device=14&Function=0" AdapterNumber="0

...

7.3.12 Zap drive

This command clears an existing conﬁguration of an adapter, e.g. deletes all logical drives, hot spares, etc.

7.3.12.1 Synopsis amCLI [-Z|--zap] [<mod/idx>]

(Note the upper case Z)

7.3.12.2 Parameters

<mod/idx>: the address of an adapter. If no adapter is given, the conﬁgurations on all adapters are cleared.

7.3.12.3 Example

# amCLI -Z 32/17

A conﬁrmation is then required to execute this command (the input is treated case-insensitive):

Are you sure to zap Adapter '32/17'?

Type YES to confirm _

7.3.13 Help

The help command serves two purposes:

To remind the user of the syntax of the various commands and to retrieve command- and object-speciﬁc options.

7.3.13.2 Parameters

Without any additional parameters, amCLI -? will just print out the syntax of all amCLI commands. As -? is the default, typing amCLI will do the same.

Additional parameters can be given to retrieve specific information about parameters of a given command when applied to a given object: create: show which RAID-levels and additional parameters the specified adapter supports (<mod/idx> must be the address of an adapter) get: show which properties can be queried with the amCLI -g command set: show which properties can be modified with the amCLI -s command exec: show information about commands available for the given object migrate: show which RAID-level a given logical drive can be migrated to and which additional parameters may be specified

(<mod/idx> must be the address of a logical disk).

If no device is given, the syntax of the command is shown. If the address of an object is given, speciﬁc information about the execution of the command on that object is shown.

7.3.13.3 Examples

# amCLI -?

118 RAID Management

Exit status

amCLI v5.7.0

Usage:

-c <mod/AdpIdx> raid=<raidLevel> [span=<spanCount>] [stripe=<stripeSize>]

[<raidFlag>=<flag>] [size=<megabytes>] (<mod/PDIdx>)+

--create <mod/AdpIdx> raid=<raidLevel> [span=<spanCount>]

[stripe=<stripeSize>] [<raidFlag>=<flag>] [size=<megabytes>]

(<mod/PDIdx>)+

-d <AdpIdx>

--delete <AdpIdx>

...

# amCLI -? create amCLI v5.7.0

Usage:

-c <mod/AdpIdx> raid=<raidLevel> [span=<spanCount>] [stripe=<stripeSize>]

[<raidFlag>=<flag>] [size=<megabytes>] (<mod/PDIdx>)+

--create <mod/AdpIdx> raid=<raidLevel> [span=<spanCount>]

[stripe=<stripeSize>] [<raidFlag>=<flag>] [size=<megabytes>]

(<mod/PDIdx>)+

# amCLI --help create 32/17 amCLI v5.7.0

Usage:

-c | --create 32/17

raid=(0|1|5|6|10|50|60|1e)

[span=<(RAID-0:1)|

(RAID-1:1)|

(RAID-5:1)|

(RAID-6:1)|

(RAID-10:2..8)|

(RAID-50:2..8)|

(RAID-60:2..8)|

(RAID-1E:1)>]

[stripe=<(RAID-0:(8kb|16kb|32kb|64kb|128kb|256kb|512kb|1mb)|

(RAID-1:(8kb|16kb|32kb|64kb|128kb|256kb|512kb|1mb)|

(RAID-5:(8kb|16kb|32kb|64kb|128kb|256kb|512kb|1mb)|

(RAID-6:(8kb|16kb|32kb|64kb|128kb|256kb|512kb|1mb)|

(RAID-10:(8kb|16kb|32kb|64kb|128kb|256kb|512kb|1mb)|

(RAID-50:(8kb|16kb|32kb|64kb|128kb|256kb|512kb|1mb)|

(RAID-60:(8kb|16kb|32kb|64kb|128kb|256kb|512kb|1mb)|

(RAID-1E:(8kb|16kb|32kb|64kb|128kb|256kb|512kb|1mb)>]

[init_mode=(no_initialization|fast_initialization|normal_initialization)]

[read_mode=(readahead|no_readahead)]

[write_mode=(writeback|always_writeback|writethrough)]

[cache_mode=(cached|direct)]

[disk_cache_mode=(disabled|enabled)]

[cache_settings=(data_protection|performance|advanced)]

[name=<string>]

[size=<megabytes>]

(<PDIdx>)+

7.3.14 Diagnostics

The exit status (or error level) approximates the error conditions deﬁned by ServerView RAID Manager and takes on the following values:

Description

Normal; no errors or warnings detected

Internal error

Invalid syntax

Invalid object

Memory failure

Operation not supported

RAID Management 119

Property not supported

Operation cannot be executed at this time

Communication with Core Service failed

Core Service initialization failed

Core Service database failed

Operation failed

Invalid parameter value

Shutdown in progress

No administration rights granted

Cannot open ﬁle

Cannot read ﬁle

Cannot write ﬁle

Core Service is initializing

120 RAID Management

7.4 Frequently Asked Questions - FAQs

• Does ServerView RAID Manager use a secure connection?

→ Yes, RAID Manager uses an encrypted communication to the browser. The data transfer is secured by encryption protocols

TLS 1.0, TLS 1.1, or TLS 1.2. Which protocol is used depends on the browser and its settings.

• When you start ServerView RAID Manager, only a red X appears in the upper left-hand corner.

→ Close the browser window/the browser and restart ServerView RAID Manager (e.g. by reentering the URL).

• When you start ServerView RAID Manager on Windows XP or Windows Server 2003, the browser window/the browser does not display anything.

→ As reaction on an attack against SHA-1 hash functions the National Institute of Standards and Technology (NIST) recommends the transition from SHA-1 to hash functions of the SHA-2 family (SHA-224, SHA-256, SHA-384, SHA-512).

ServerView RAID Manager uses SHA-256 which is not available under every Windows XP or Windows Server 2003 installation.

A hotﬁx (KB968730) is available from Microsoft.

• The browser suddenly no longer has contact to the server.

→ Check whether the service amService (Windows) or the daemon amDaemon (Linux) is running. If it is not, start it:

Windows: Via Computer Management → Services → ServerView RAID Manager

Linux: Using the "/etc/init.d/aurad start" command

The service check under Linux, for instance, is executed using "ps -ef | grep amDaemon" or "/etc/init.d/aurad status".

• The progress display in the GUI suddenly stops after you have initiated an action.

→ Abort the session and restart ServerView RAID Manager.

• The expected results are not displayed in the log.

→ Check whether logging is enabled in ServerView RAID Manager (see system log property Logging). If this does not help, notify your service engineer.

• A logical drive cannot be deleted.

→ Check whether deletion is prevented by an ongoing activity (e.g. initialization). Interrupt or abort the activity and repeat the delete operation.

• You must or want to use ServerView RAID Manager with JRE 1.4, but the login screen remains dark.

→ Click in the browser window and press the Enter key once after you have loaded and initialized ServerView RAID Manager.

• Which service/daemon is installed in conjunction with ServerView RAID Manager?

→ The following service (daemon for Linux) will be installed:

amService/amDaemon: The central service/daemon of ServerView RAID Manager.

• What web server does ServerView RAID Manager use?

→ The web interface (GUI) is made available via the service/daemon amService/amDaemon, various extension modules being loaded dynamically at runtime. No "classical" web server such as Apache runs. amService/amDaemon uses a reduced HTTP as transport protocol to permit web browsers to work with ServerView RAID Manager.

• How can ServerView RAID Manager port be changed?

→ The 6th line of the <installation directory>\bin\amDPatch.ini ﬁle contains the entry "Port = 3173". You can change the port here. You cannot force a binding. If the port is not accessible from the outside, you must arrange this using the ﬁrewall.

When changing the port please test thoroughly that all other software (e.g. ServerView Agents) that connect to ServerView

RAID is working correctly.

• Is it possible to use IPv6 protocol with ServerView RAID Manager?

→ Yes, ServerView RAID Manager supports IPv4 and IPv6.

• Which authentication methods does ServerView RAID Manager support in E-mail log function?

→ ServerView RAID Manager supports the following SMTP authentication methods:

• CRAM-MD5

• DIGEST-MD5

• LOGIN

• NTLM

• OTP

• PLAIN

• SCRAM

• SRP

• Which SNMP version does ServerView RAID Manager support?

→ ServerView RAID Manager supports SNMP v1 only.

RAID Management 121

• Which settings have to be changed for SNMP on Linux?

→ During installation of ServerView RAID Manager entries are added to /etc/.../snmpd.conf that have to be explicitly activated for the underlying Linux distribution. These entries are marked with SVRA. On SuSE the '#' in the line starting with

"rocommunity" has to be removed, and on RedHat and VMware the '#' in the line starting with "view". Then the SNMP daemon has to be restarted.

All further SNMP settings (community, trapsink, ...) are described in the manual of the distribution.

• User accounts on Windows.

→ When creating an account for ServerView RAID Manager on Windows it is recommended that the option User must change

password at next login should not be checked and Password never expires should be checked. ServerView RAID Manager does not display a warning message when the password is expired.

• No login to Linux ServerView RAID Manager possible although users and groups have been created correctly.

→ Check ﬁle /etc/security/access.conf. Some operating systems have a very restrictive default user access control. To allow

ServerView RAID Manager to be used with the newly created users and groups add lines like the following to the beginning of

/etc/security/access.conf:

+:<user or group name>:LOCAL

• No login to VMware ServerView RAID Manager possible although users and groups have been created correctly.

→ Similar to the previous item VMware vSphere 4.1 has a very restrictive default user access control. To allow ServerView RAID

Manager to be used with the newly created users and groups use vSphere Client as described in ESX Conﬁguration Guide and add administrator role privilege to them.

• No login to ServerView RAID Manager possible although user name and password was entered correctly in Japanese environment.

→ If you use 2 byte characters in the hostname, a login with this URL is not possible. Please change the name of the server to use only standard characters. Standard characters are A-Z, a-z, 0-9, -(hyphen). If this is not possible the IP address of the server can be used alternatively.

122 RAID Management

8 Glossary

Array

A group of several hard disks on which one or more logical drives are contained is called an array.

Array Initialization

See Initialization.

ATA

AT Bus Attachment. Standard parallel interface to IDE hard disk drives which is commonly used in desktop computers and some entrylevel servers. A successor of ATA is SATA (Serial ATA interface).

Automatic Rebuild

Automatic procedure which restores faulty segments on preconﬁgured volumes. If a drive in a SAF-TE enclosure which has no hot spare assigned should fail, a rebuild starts only when the failed drive has been replaced by a new one.

Background Initialization

In the case of background initialization of a drive the redundant logical drive can be accessed while the initialization is running.

BGI

Background Initialization is a type of initialization which is started automatically in the background at low priority by an Avago controller. See also Initialization and Background Initialization.

Bus

See Channel.

Cache

Quickly accessible memory on a controller which serves as a buﬀer for data which is read from or written to devices.

Capacity

Total storage capacity available on a drive; often speciﬁed in megabytes or gigabytes. A distinction is made between physical and logical capacity.

CAS

CAS (Central Authentication Service) is an enterprise single sign-on solution for web services. Single sign-on (SSO) means a better user experience when running a multitude of web services, each with its own means of authentication. With a SSO solution, diﬀerent web services may authenticate to one authoritative source of trust, that the user needs to log in to, instead of requiring the end-user to log in into each separate service.

Channel

Path between a controller and storage devices used for data transfer and control of information. Each channel of a controller is identiﬁed by a number between 0 and the maximum number of channels minus 1. A channel is also referred to as a port or bus.

Concatenation

Connection in sequential order.

Consistency Check

An action in which the controller checks all segments of the logical dive. Depending on the logical drive type various things can be checked and the checks can therefore take diﬀerent lengths of time. RAID-5 checks the data for consistency and parity. RAID-1 checks whether both drives are consistent. See also MDC and Verify.

Create

See Automatic Rebuild.

Dedicated Hot Spare

A physical drive which, when required, takes over the place of a failed physical drive in a specially assigned, fault-tolerant logical drive.

Degraded

A redundant logical drive in which one or more members have failed. The data is still intact, but redundancy has been impaired and is in a worse status. The logical drive and all the data are still available, but a further drive failure leads to the failure of the logical drive and loss of data. A check plus correction can return an impaired logical drive to its optimal status.

Dirty Data

Data which has been written into a cache and has not yet been updated on the actual target volume.

Drive

See Physical and Logical Drive.

RAID Management 123

Enclosure

An enclosure for physical drives which generally contains several power supplies, fans, and temperature sensors. Enclosures are normally outside the computer to which they are connected. Some computers also contain internal enclosures.

Event

Notiﬁcation or warning message when changes occur in the system.

Event Log

Information on controller activities or other events are stored in a ﬁle.

Expand

Assignment of more storage space to a logical drive.

Failed

Status of a non-redundant logical drive with a single drive failure or a redundant logical drive with multiple drive failures. The status generally results in a loss of data as access to the logical drive is no longer possible.

Failed Segment

A segment which is no longer used by a logical drive because it is either logically or physically damaged.

Fast Initialization

The logical drive is available immediately, but has a special internal status. In RAID-5 and RAID-50 the write performance is aﬀected until a check plus correction has been performed on this logical drive.

Fault-tolerant Logical Drives

Logical drives with redundant components (RAID-1, RAID-5, RAID-10, RAID-50).

Format

A process performed by the ﬁrmware in which all data on the hard disk is totally deleted.

Global Hot Spare

Volume which can replace a failed component in the logical drives on the same controller. The available storage capacity must be at least as large as that of the failed component. See also Hot Spare.

Hot Spare

A physical volume available as a replacement if a drive fails. In a redundant logical drive this permits automatic data recovery. The storage capacity available must be at least as large as that of the failed component. See also Automatic Rebuild, Global Hot Spare and

Dedicated Hot Spare.

Hot Swap

Replacement of system components while the system is running.

Initialization

A fault-tolerant logical drive must be initialized before it is used. This operation deletes all blocks on the logical drive. In RAID-5 a parity is then generated on the basis of the current content of the member segments, whereas RAID-1 copies the content of the ﬁrst drive (master) to a second drive (slave). Depending on the RAID type initialization runs in the background at diﬀering speeds. In addition, Fast Initialization is also provided for immediate access to a RAID-5 drive.

Initialized Logical Drive

A logical drive which is ready for read and write operations.

Java

Java is an object-oriented, platform-independent programming language developed by Sun Microsystems. All Java programs run on a wide range of platforms without any adjustments. However, to execute, JAVA programs generally need a special runtime environment, the virtual machine, and only this environment need be adjusted to the various operating systems.

JBOD

JBOD stands for Just a Bunch Of Disks. According to the latest deﬁnition of the Storage Networking Industry Association (SNIA) a single hard disk should be understood here today, whereas earlier it referred to multiple hard disks (also referred to as concatenation).

KByte

Is a unit of information or computer storage, commonly abbreviated as "KiB" and stands for 2

bytes = 1,024 bytes.

LBA

Logical Block Addressing is an addressing method for hard disks. In contrast to other methods the sectors on the hard disk are counted singly, beginning with 0.

LED

A light-emitting diode is an electronic semiconductor which is used, for example, to indicate read or write operations on hard disks.

Often an LED is also used for determining the location of the drives.

124 RAID Management

Locate

An aid in uniquely identifying hard disk which consists of the controller number, the channel or port number, the LUN, and the SCSI-ID.

Logical Drive

A drive which consists of one or more physical drives, mostly hard disks. For the operating system, all the storage volume available constitutes a single drive.

Logical Drive Order

The order in which, at system startup, the server's operating system recognizes individual hard disks and other devices connected to the controller.

LUN

Each SCSI device can contain up to eight subdevices. A LUN is the number of the logical unit - 0 through 7 - which has been assigned to this device. However, generally only one subdevice (LUN 0) exists.

MDC

Make Data Consistent is a consistency check with additional correction. Depending on the drive type various things can be checked and the checks can therefore take diﬀerent lengths of time. RAID-5 checks the data for consistency and parity and optionally corrects parity errors. RAID-1 checks whether both drives are consistent. Either if inconsistencies found it will be try to correct if is possible to ﬁx it. See also Consistency Check and Verify.

Migration

Process of transforming a logical drive from one RAID type to another, changing the strip size, or expanding the size of a logical drive by adding new disks.

Monitoring

The process for ascertaining, displaying, and logging system events.

Notiﬁcation

Aid used by the system for communication relating to events that have occurred.

NVRAM

A non-volatile memory which can retain information even if the power supply is not maintained. This memory is often used on RAID controllers as a memory for the conﬁguration and for error logging.

Oﬄine

The status of a logical or physical drive which can no longer be accessed.

Oﬀset

The distance from the start of a drive to the start of a segment.

Optimal

A logical drive in its normal operating status in which all components are present and fully operational.

Parity

A form of redundancy which is used for checking the user data for errors. Additional data is generated from the user data which is also stored and can be used to reconstruct the original data.

Patrol Read

Patrol Read examines the drive's interface for errors. If an error is detected which cannot be rectiﬁed automatically, this error is logged. The faulty part of the medium is assigned to the defective blocks. With some controllers the disk is automatically taken out of service if multiple errors are found.

Physical Drive

Generally a physical hard disk drive, also known as hard disk for short. This is a randomly accessed, rewritable data storage device.

Port

See Channel.

RAID Signature

From the RAID signature on a hard disk the RAID controller can recognize, among other things, whether the hard disk has already been initialized. In future it is to contain a complete, non-proprietary RAID conﬁguration to make it easier to exchange drives or controllers.

RAID Volume

Two or more logical drives of the same type which need not necessarily have the same capacity are connected in a RAID volume.

RAID-0

A logical drive with one level, consisting of two equal-sized segments on diﬀerent hard disk drives. RAID-0 uses the striping process to distribute the data evenly in equal-sized sections over the drives concerned.

RAID-0/1

See RAID-10.

RAID Management 125

RAID-1

A logical drive with one level, consisting of two equal-sized segments on diﬀerent hard disk drives. Oﬀers redundancy by storing the same data on both hard disks.

RAID-5

A logical drive with one level, consisting of three equal-sized segments on diﬀerent hard disk drives. The capacity of one segment is used for parity data which is distributed over all the drives in equal-sized sections.

RAID-10

A logical drive. Two equal-sized RAID-1s are used to create a RAID-10. RAID-10 thus needs four physical drives.

RAID-50

A logical drive. Two equal-sized RAID-5s are used to create a RAID-50. RAID-50 thus needs six physical drives.

Reconﬁguration

See Migration.

Redundancy

Redundancy is the general term to describe the additional existence of resources which are functionally identical or comparable if these are not normally required when operation is error-free. Here redundancy is used to manage data in a system with the aim of automatically replacing failed components by operational ones. For example, logical drives of the type RAID-5 are redundant because the surviving members can combine to replace the data of a failed component.

Replacement

See Hot Spare.

Role Based Access Control

Role based access control (RBAC) manages access control by deﬁning a set of user roles (security roles). One or more roles are assigned to each user, and one or more user privileges are assigned to each role.

SAF-TE

SCSI Accessed Fault-Tolerant Enclosure.

SAS

Serial Attached SCSI is to replace the current parallel SCSI interface because the Terminators which are typical for SCSI are not required for SAS. SAS takes over the SATA connections. SATA devices can be used on SAS but not vice versa.

SATA

Serial ATA is a successor to ATA which transfers data serially instead of in parallel.

SCSI

Small Computer System Interface is a parallel high-speed communication method which permits data transfer rates of up to 320

Mbytes/s. The current speciﬁcation supports up to 15 devices per channel.

SCSI ID

A unique number (0-15) which is assigned to each device on a SCSI bus.

Second Level Array

A logical drive can consists of more than one level. The logical device of the second level (lower level array in an array with two levels) is never visible for the operating system and can only be used by other logical devices. For example, a RAID-10 array's member in the top level is a RAID-0 array and in the second level two or more RAID-1 arrays.

Segment

Reserved area on a physical hard disk. A segment is always part of a logical drive and cannot be used by more than one logical drive at the same time.

Single Sign-On (SSO)

Single sign-on allows participating applications to share a single sign-on session. Users complete a centrally managed authentication experience once per browser session and while authenticated to CAS can log into multiple applications without again being prompted for credentials and without those applications ever seeing the user's password.

SMART

Self-Monitoring Analysis and Reporting Technology (SMART). This drive function is designed to determine the reliability status of a hard disk drive. If SMART detects a potential problem that could be serious, the user is notiﬁed and receives assistance on how to rectify this problem.

Spare Drive

See Hot Spare.

126 RAID Management

Striping Process

Small, contiguous data areas which are distributed over all hard disks in the logical drive are called stripes. For example, with the striping process RAID-0 distributes the data in equal-sized sections over the drives concerned to expedite access.

Stripe Size

In logical drives using the striping process (RAID Levels 0, 5, 10 and 50) the data is distributed over the member hard disks in equalsized sections. The amount of data in each section is the stripe size.

Temperature Warning Threshold

The temperature threshold deﬁned by the user above which a warning message is issued.

Terminator

In a SCSI bus system both ends of the cable route must be provided with a terminator. There are two types of termination, the passive one using resistors and the active one using an internal voltage source.

Verify

An action in which the controller checks all segments of the hard disks. This determines whether the hard disks are sending back data from the blocks. See also Consistency Check and MDC.

Virtual Drive Order

See Logical Drive Order.

RAID Management 127

I've finished reading the Fujitsu RAID Manager User Guide. I understand its contents, including RAID levels, installation instructions, and the user interface. Ask me anything about managing your RAID system with this software.

Show related prompts

Assistant typing

Assistant is out of keyboard. Please, try again later.

Key features

Supports all current RAID controllers
Provides administrative options for SCSI, SATA, and SAS controllers
Supports RAID controllers on the mainboard and expansion boards
Offers only supported administrative options
Includes support for hot swap, hot spare, and background initialization
Provides a user-friendly interface for managing RAID controllers
Allows you to monitor the status of RAID controllers and devices
Allows you to create, modify, and delete logical drives
Provides a security certificate for authentication
Supports both local and remote administration

Frequently asked questions

ServerView RAID Manager supports RAID levels 0, 1, 1E, 5, 6, 10, 50, and 60. It also supports single volumes and JBODs.

ServerView RAID Manager can be installed independently or as part of the ServerView Installation Manager. The installation process involves downloading the installation package, running the installer, and following the on-screen instructions.

To log in to ServerView RAID Manager, open a web browser and enter the server name (FQDN) of the system followed by TCP port number 3173 in the address bar. You will then be prompted to enter your username and password.

ServerView RAID Manager has specific system requirements, including a supported operating system, a web browser, and a Java Runtime Environment. Refer to the documentation for detailed system requirements.

FUJITSU Software ServerView Suite

ServerView RAID Manager

Copyright and trademarks

Contents

1 Basics

1.1 Supported RAID Levels

1.2 RAID Controller Functions

1.3 Supported Controllers and Devices

2 Login

2.1 Installation

2.2 Login

2.3 Security Certiﬁcate

2.4 System requirements

2.5 Licenses

3 The User Interface

3.1 Elements of the User Interface

3.2 Event Status Indicators and Icons

4 Properties

4.1 Displaying and Modifying Properties

5 Actions and Dialogs

5.1 Executing Actions

5.2 Creating Logical Drives

5.3 Modifying Logical Drives (migrating)

5.4 Processing Hot Spares

5.5 Foreign Conﬁguration

5.6 Task

6 Events

6.1 Displaying Events

6.2 Events / SNMP Traps

6.3 Errors

7 Help

7.1 Help

7.2 Online Help

7.3 amCLI

7.4 Frequently Asked Questions - FAQs

8 Glossary

What RAID levels are supported by ServerView RAID Manager?

How do I install ServerView RAID Manager?

How do I log in to ServerView RAID Manager?

What are the system requirements for ServerView RAID Manager?

Related

Fujitsu ServerView RAID Manager User Guide: AI Chat & PDF Access

FUJITSU Software ServerView RAID Manager User Guide

ServerView V7.3.1 RAID Manager User Guide: AI Chat & PDF Access

FUJITSU ServerView RAID Manager V7.2.4: AI Chat & PDF Access

FUJITSU ServerView RAID Manager Benutzerhandbuch

ServerView RAID Manager Benutzerhandbuch

Fujitsu MegaRAID SATA Embedded User's Guide

Fujitsu RAID Management User Guide

ServerView RAID Manager V7.2.4 : AI Chat & PDF Download

FUJITSU RAID Manager 取扱説明書

ServerView RAID Manager V7.3.1 Benutzerhandbuch : AI-gestützte Q&A & PDF Download

Fujitsu RAID Management User Guide