#######################################################################
DELL OPENMANAGE(TM) Storage Management, VERSION 1.0 README
This is the readme file for the Dell OpenManage Server Administrator
enhanced Storage Management Service. For information on the basic and
enhanced Storage Management Service and their relationship to Array
Manager, see the "Title and Description" section of this readme
and the "What’s New for Version 1.9" and the "Storage Management
Service" chapters of the Server Administrator User's Guide.
NOTE: The enhanced Storage Management Service is installed using the
Server Administrator install process. See the Dell OpenManage
Install readme (readme_ins.txt) on the "Systems Management" CD
for the latest installation information and issues specifically
related to Server Administrator.
NOTE: See the Dell OpenManage Array Manager readme (located in the
"am3xx" directory on the "Systems Management" CD) for supplemental
information regarding the basic Storage Management Service and
Array Manager.
Note: Product documentation for the enhanced Storage Management Service
is provided as online help. The online help refers to this service
as "Dell OpenManage Storage Management" and as "Storage Management".
Note: The Server Administrator documentation includes the "User's Guide",
"Messages Reference Guide", "CIM Reference Guide", "Command Line
Interface (CLI) User's Guide", "SNMP Reference Guide", and
"Compatibility Guide". You can access all the documentation from
the product documentation CD or from the Dell Support website at
"support.dell.com".
Always see the Dell support Website at support.dell.com for the most
current information.
#######################################################################
======================================================================
Criticality
======================================================================
2 - Recommended
Note: The enhanced Storage Management Service does not support Novell(R)
NetWare(R) or fibre channel. Disk and volume management are also
not provided by the enhanced Storage Management Service.
All other storage management and configuration features provided
by Array Manager are also provided by the enhanced Storage
Management Service.
In addition, the enhanced Storage Management Service supports
Linux.
======================================================================
Title and Description
======================================================================
This release of Server Administrator provides both a basic and an
enhanced Storage Management Service. The basic Storage Management
Service is the same service as provided with previous releases. Array
Manager is installed with the basic Storage Management Service.
The enhanced Storage Management Service replaces the storage management
and configuration features provided by Array Manager. See the WHAT IS
NEW IN THIS RELEASE? section of this readme for more information.
######################################################################
README TABLE OF CONTENTS
######################################################################
COMPATIBILITY/RECOMMENDED REQUIREMENTS
WARNINGS
WHAT IS NEW IN THIS RELEASE?
COMPARING THE ENHANCED STORAGE MANAGEMENT SERVICE AND ARRAY MANAGER
CONSIDERATIONS WHEN MIGRATING FROM ARRAY MANAGER
WHAT IS FIXED IN THIS RELEASE?
INSTALLING STORAGE MANAGEMENT, VERSION 1.0
KNOWN LIMITATIONS
######################################################################
COMPATIBILITY/RECOMMENDED REQUIREMENTS
######################################################################
The enhanced Storage Management Service is installed using the Server
Administrator install process. For Server Administrator installation
requirements, see the following documentation:
* The Dell OpenManage Install readme (readme_ins.txt) on the "Systems
Management" CD for the latest installation information.
* The "Installing Server Administrator" chapter in the Server
Administrator User's Guide.
======================================================================
COMPATIBILITY WITH ARRAY MANAGER
======================================================================
Installing the new enhanced Storage Management Service replaces any
previous installation of the Array Manager managed system (server
software) that resides on the system. The Array Manager console (client
software) is not replaced.
======================================================================
COMPATIBILITY WITH OTHER RAID STORAGE MANAGEMENT UTILITIES
======================================================================
* PERC Console and FAST Compatibility Issues when Installing Storage
Management
Installing Storage Management on a system that has FAST or the PERC
Console installed is an unsupported configuration. It is recommended
that you uninstall FAST and the PERC Console before installing Storage
Management. In particular, you may find that Storage Management or the
FAST features are disabled at run time when using Storage Management
on a system that also has FAST installed. Storage Management replaces
all storage management features provided by FAST and the PERC Console.
In addition, Storage Management has features not provided by FAST and
the PERC Console.
* Compatibility with Linux Utilities
Installing Storage Management on a Linux system that has other RAID
storage management utilities provided by Dell or other vendors is an
unsupported configuration. It is recommended that you uninstall these
utilities before installing Storage Management. Storage Management
replaces the storage management features provided by these utilities.
Examples of the Dell or vendor-supplied Linux utilities include:
- LinFlash
- DellMgr
- DellMON
- LINLib
- MegaMgr
- MegaMON
Note: See the WARNINGS section of this readme for additional information.
======================================================================
FIRMWARE AND DRIVER REQUIREMENTS FOR THE PERC 2/SC, 2/DC, 3/SC, 3/DC,
3/DCL, 3/QC, 4/SC, 4/DC, 4e/DC, 4/Di, 4/IM, 4e/Si, 4e/Di,
CERC ATA100/4ch, LSI 1020, and LSI 1030 CONTROLLERS
======================================================================
The firmware and drivers listed in the following table refer to the
minimum supported version. Later versions of the firmware and drivers
are also supported. Refer to http://support.dell.com for the most recent
driver and firmware requirements.
Controller Firmware Windows 2000 Windows Redhat Redhat
Driver Server Linux Linux
2003 Driver Driver
Driver 2.1 3.0
PERC 2/SC 3.13 2.68 6.35.2.32 1.18 N/A
PERC 2/DC 1.06 2.68 6.35.2.32 1.18 N/A
PERC 3/SC 197O 5.46 6.41.2.32 2.10.7 2.10.7
PERC 3/DC 197O 5.46 6.41.2.32 2.10.7 2.10.7
PERC 3/DCL 197O 5.46 6.41.2.32 2.10.7 2.10.7
PERC 3/QC 197O 5.46 6.41.2.32 2.10.7 2.10.7
PERC 4/SC 350O 5.46 6.41.2.32 2.10.7 2.10.7
PERC 4/DC 350O 5.46 6.41.2.32 2.10.7 2.10.7
PERC 4e/DC 513P 5.46 6.41.2.32 2.10.7 2.10.7
PERC 4e/Si 513O 5.46 6.41.2.32 2.10.7 2.10.7
PERC 4e/Di 513O 5.46 6.41.2.32 2.10.7 2.10.7
PERC 4/Di on a 2.48 5.46 6.41.2.32 2.10.7 2.10.7
PowerEdge 2600
PERC 4/Di on a 412W 5.46 6.41.2.32 2.10.7 2.10.7
PowerEdge 1750
PERC 4/IM on a 1.00.12.00 1.08.06 1.08.18 Not Not
PowerEdge (1.00.0C.00 Hex) (Native) Applicable Applicable
1655MC
CERC 6.62 5.46 6.41.2.32 2.10.1 Native
ATA 100/4CH
LSI 1020 on a 1.03.04.00 1.08.19 1.08.18 Not Not
PowerEdge (Native) Applicable Applicable
1600SC
LSI 1030 on a 1.01.61.00 1.08.19 1.08.18 Not Not
PowerEdge (Native) Applicable Applicable
2600
LSI 1030 on a 1.01.61.00 1.08.19 1.08.18 Not Not
PowerEdge (Native) Applicable Applicable
1750
======================================================================
FIRMWARE AND DRIVER REQUIREMENTS FOR THE PERC 2, PERC 2/Si, PERC 3/Si,
PERC 3/Di, CERC SATA1.5/6ch, and CERC SATA1.5/2s CONTROLLERS
======================================================================
The firmware and drivers listed in the following table refer to the
minimum supported version. Later versions of the firmware and drivers
are also supported. Refer to http://support.dell.com for the most
recent driver and firmware requirements.
Note: Versions of these controllers (PERC 2, PERC 2/Si, PERC 3/Si,
PERC 3/Di, CERC SATA1.5/6ch, and CERC SATA1.5/2s) prior to 2.8
are not supported.
Note: Storage Management requires that the system be rebooted before
Storage Management can properly determine whether the system
meets the firmware and driver requirements for the PERC 2,
PERC 2/Si, PERC 3/Si, PERC 3/Di, CERC SATA1.5/6ch, and
CERC SATA1.5/2s controllers. For this reason, it is possible
to complete an initial installation of Storage Management
without being notified whether your system meets the firmware
and driver requirements. Refer to this readme and
http://support.dell.com for the most recent driver and firmware
requirements.
Controller Firmware Windows 2000 Windows Linux Linux
Driver Server Driver Driver
2003 2.1 3.0
Driver
PERC 2 2.8.0.6089 2.8.0.6085* 2.8.0.6085* 1.1.4** 1.1.4**
PERC 2/Si 2.8.0.6089 2.8.0.6085* 2.8.0.6085* 1.1.4** 1.1.4**
PERC 3/Si 2.8.0.6089 2.8.0.6085* 2.8.0.6085* 1.1.4** 1.1.4**
PERC 3/Di on a 2.8.0.6089 2.8.0.6085 2.8.0.6085 1.1.4** 1.1.4**
PowerEdge 1650
PERC 3/Di on a 2.8.0.6089 2.8.0.6085* 2.8.0.6085* 1.1.4** 1.1.4**
PowerEdge 2500
PERC 3/Di on a 2.8.0.6089 2.8.0.6085* 2.8.0.6085* 1.1.4** 1.1.4*
PowerEdge 2550
PERC 3/Di on a 2.8.0.6089 2.8.0.6085* 2.8.0.6085* 1.1.4** 1.1.4**
PowerEdge 2650
PERC 3/Di on a 2.8.0.6089 2.8.0.6085* 2.8.0.6085* 1.1.4** 1.1.4**
PowerEdge 4400
PERC 3/Di on a 2.8.0.6089 2.8.0.6085 2.8.0.6085 1.1.4** 1.1.4**
PowerEdge 4600
CERC 2.8.0.7028 2.8.0.7010 2.8.0.7010 1.1.4** 1.1.4**
SATA1.5/6ch
CERC Not 6.00.048 6.00.048 1.1.4** Not
SATA1.5/2s Applicable Applicable
Note: * The 2.8.0.6085 driver install package for the PERC 2, 2/Si,
3/Si, and 3/Di controllers contains the 2.8.0.6076 driver.
For this driver, Storage Management displays 2.8.0.6076
whereas Windows Device Manager displays 2.8.0.6085.
Note: ** The 1.1.4 Linux driver is included in RPM 2302 (Release Package
Manager 2302).
======================================================================
ADAPTEC NON-RAID ULTRA SCSI CONTROLLER CARDS
======================================================================
The Ultra SCSI controller cards (non-RAID SCSI) include Ultra SCSI,
Ultra2 SCSI, Ultra160 SCSI, Ultra320 SCSI.
Support for the Ultra SCSI controller cards is provided in the BIOS.
On Linux, the correct version of the Linux kernel is required in order
for Storage Management to display and manage Adaptec non-RAID SCSI
controllers. If the Linux kernel does not meet the requirements, Storage
Management can be installed but the Adaptec non-RAID SCSI controllers
will not be displayed by Storage Management.
The Linux kernel requirements for the Adaptec non-RAID SCSI controllers
are as follows:
* Linux Advanced Server 2.1 update 3 with the aic7xxx_mod driver enabled
* Linux Advanced Server 3.0 GOLD
======================================================================
PREREQUISITE DRIVERS AND FIRMWARE ON LINUX
======================================================================
On Linux, Storage Management installation is unable to detect whether
the drivers and firmware on the system are at the required level for
installing and using Storage Management. When installing on Linux, you
will be able to complete the installation regardless of whether the
driver and firmware version meets the required level. Even though you
have completed the installation, installing on a system that does not
meet the driver and firmware version requirements is an unsupported
configuration. In particular, you may find that controllers and their
features are not displayed by Storage Management on a system that does
not meet the driver and firmware requirements. At Storage Management
runtime, you can determine whether the system meets the requirements
by checking your application log files for notifications on outdated
firmware versions.
######################################################################
WARNINGS
######################################################################
* As a general rule, you should use only one RAID utility to configure
and manage storage. Installing the enhanced Storage Management
Service on a system that has native RAID utilities or RAID utilities
provided by Dell or other vendors is an unsupported configuration.
* The enhanced Storage Management Service enables you to perform storage
tasks that are data-destructive. The enhanced Storage Management
Service should be used by experienced storage administrators who are
familiar with their storage environment.
######################################################################
WHAT IS NEW IN THIS RELEASE?
######################################################################
This release provides an enhanced Storage Management Service. The
enhanced Storage Management Service provides the same storage management
and configuration functions as Array Manager. Unlike Array Manager,
however, the enhanced Storage Management Service features are accessible
from the Server Administrator graphical and command line interfaces.
Note: Product documentation for the enhanced Storage Management Service
is provided as online help. The online help refers to this service
as "Dell OpenManage Storage Management" and as "Storage Management".
The enhanced Storage Management Service:
* Enables you to view the status of local and remote storage attached to
a monitored system.
* Allows you to perform controller and enclosure functions for all
supported RAID and non-RAID controllers and enclosures from a single
graphical or command line interface without the use of the controller
BIOS utilities.
* Protects your data by configuring data redundancy, assigning hot
spares, or rebuilding failed drives.
* Provides a graphical interface that is wizard-driven with features
for novice and advanced users and a detailed online help.
* Provides a fully-featured and scriptable command line interface.
* Supports SCSI, SATA, and ATA. Does not support Fibre Channel.
NOTE: This release of the enhanced Storage Management Service does not
provide Microsoft(R) Windows volume and disk management or Novell
NetWare support. In addition, fibre channel is not supported.
Note: For more information on the basic and enhanced Storage Management
Service and their relationship to Array Manager, see the "What’s
New for Version 1.9" and the "Storage Management Service" chapters
of the Server Administrator User's Guide.
======================================================================
NEW FEATURES NOT AVAILABLE IN ARRAY MANAGER VERSION 3.5
======================================================================
The following features are available in this release of the enhanced
Storage Management Service and Array Manager Version 3.6, but are not
available in Array Manager Version 3.5:
* Support for global hot spares on the PERC 2, 2/Si, 3/Si, 3/Di, and
CERC SATA1.5/6ch, and CERC SATA1.5/2s controllers.
* Support for the 4e/DC, 4e/Si, 4e/Di, and CERC SATA1.5/2s controllers.
######################################################################
COMPARING THE ENHANCED STORAGE MANAGEMENT SERVICE AND ARRAY MANAGER
######################################################################
The following summarizes notable differences in operating system and
feature support between Array Manager and the enhanced Storage
Management Service:
* Disk and volume management are provided by Array Manager on Windows
2000. Disk and volume management are not provided by the enhanced
Storage Management Service. If you need disk and volume management,
you can use the native disk and volume management utilities provided
by your operating system. On a Windows 2000 system, you have the
option of installing Array Manager which replaces the Windows 2000
disk and volume management.
* Fibre channel support for the Dell PowerVault 660F storage system
is provided by Array Manager, but not by the enhanced Storage
Management Service.
* NetWare support is provided by Array Manager, but not by the enhanced
Storage Management Service.
* Linux support is provided by the enhanced Storage Management Service,
but not by Array Manager.
Note: For a comprehensive comparison of enhanced Storage Management
Service and Array Manager features, see the "What’s New for
Version 1.9" chapter of the Server Administrator User's Guide.
######################################################################
CONSIDERATIONS WHEN MIGRATING FROM ARRAY MANAGER
######################################################################
If you replace an existing Array Manager installation with Storage
Management, the following migration considerations apply:
* Virtual Disk Preservation
You can preserve the virtual disk names when migrating from Array
Manager to Storage Management. To do so, however, you must not
uninstall Array Manager prior to installing Storage Management.
If Array Manager is uninstalled prior to installing Storage Management,
then Storage Management will rename the virtual disks created with
Array Manager. Whether or not Array Manager is uninstalled, Storage
Management will be able to identify and manage the virtual disks
created with Array Manager.
* SNMP Traps
The architecture for handling the SNMP traps and the Management
Information Base (MIB) is different in Storage Management than Array
Manager. You may need to modify applications that have been customized
to receive SNMP traps from Array Manager.
* Event Numbering
The numbering scheme for Storage Management alerts or events is
different than the numbers used for the corresponding Array Manager
events. See the Alert Messages chapter in the Storage Management online
help for more information.
######################################################################
WHAT IS FIXED IN THIS RELEASE?
######################################################################
Fixed issues are not applicable for this release.
######################################################################
INSTALLING STORAGE MANAGEMENT, VERSION 1.0
######################################################################
The enhanced Storage Management Service is installed using the Server
Administrator install process. For Server Administrator installation
requirements, see the following documentation:
* The Dell OpenManage Install readme (readme_ins.txt) on the
"Systems Management" CD for the latest installation information.
* The "Installing Server Administrator" chapter in the Server
Administrator User's Guide.
Note: You cannot reinstall Storage Management on a system that
already has Storage Management installed. If you need to
reinstall Storage Management, you must first uninstall the
existing installation using the Server Administrator uninstall
process. On a Windows system, you can also use Add/Remove
programs to uninstall Storage Management.
Note: Installing Storage Management on a system that does not have a
supported controller or that has a controller that is not attached
to storage is an unsupported configuration.
######################################################################
KNOWN LIMITATIONS
######################################################################
The following sections describe known problems associated with Storage
Management or the supported controllers. Dell is in the process of
resolving these problems.
* Storage Management SNMP traps are not filtered by Server Administrator
Problem: Server Administrator allows you to filter SNMP traps that you
do not wish to receive. To implement SNMP trap filtering, select the
System tree object and then select the Alert Management tab and the
SNMP Traps subtab. The SNMP Traps subtab has options for enabling or
disabling SNMP traps based on severity or the component that generates
the trap. Even when the SNMP traps are disabled, Storage Management
will generate SNMP traps.
Solution: SNMP trap filtering will be provided in a future release of
Storage Management.
* Attempts to reconfigure a virtual disk or perform other operations may
encounter strange behavior and fail.
Problem: When creating a virtual disk on the PERC 2, PERC 2/Si,
PERC 3/Si, PERC 3/Di, CERC SATA1.5/6ch, and CERC SATA1.5/2s controllers,
Storage Management reserves 64KB of disk space on each array disk used
by the virtual disk. The 64KB is reserved for the use of future
operations (such as a reconfigure) that may require this disk space. The
requirement for the 64KB of reserved array disk space may incur problems,
however. For example, a virtual disk created with the controller BIOS or
another utility may not have the 64KB of reserved space. In this case,
the Storage Management Reconfigure Virtual Disk Wizard will be unable to
reconfigure the virtual disk. The Reconfigure Virtual Disk Wizard may also
demonstrate strange behavior, such as an inability to display an array disk
selection or it may display error messages. You may also notice strange
behavior with other virtual disk operations, although a rebuild will work
in most cases.
Solution: As a general rule, it is advisable to use Storage Management
when creating a virtual disk. Dell is working to resolve this problem.
* CLI reports "command successful" when attempts to reconfigure a virtual
disk have failed.
Problem: In some circumstances, attempts to reconfigure a virtual disk
using the command line interface (CLI) may generate a "command successful"
message even though the command has failed due to improper array disk
specification.
Solution: When using the CLI to reconfigure a virtual disk, you must
specify all array disks to be included in the reconfigured virtual disk.
The array disk specification applies to array disks that were in the
original virtual disk and will continue to be in the reconfigured virtual
disk and to any new array disks being added to the reconfigured virtual
disk. The CLI parameters for reconfiguring a virtual disk, including the
array disk specification, are described in the Storage Management online
help.
Dell is working to correct the CLI message in a future release.
* On Linux, Storage Management fails to display an error message when
the export log file function fails due to lack of file system space.
Problem: When exporting a controller log file on a Linux system, no
error message is displayed when the export log file function fails
due to lack of file system space.
Solution: Dell is working to resolve this problem.
* On Linux, attempts to split a mirror that contains the boot drive
may fail.
Problem: On Linux, attempts to split a mirrored virtual disk that
contains the boot drive on a PERC 2, 2/Si, 3/Si, 3/Di, CERC
SATA1.5/6ch, or CERC SATA1.5/2s controller may fail.
Solution: This behavior is a controller limitation on Linux. If it
is necessary to split the mirror, change the boot drive or use
another utility to split the mirror.
* The size of very small virtual disks may be displayed as 0.00 in
certain circumstances.
Problem: The algorithm for calculating the virtual disk size rounds
a value that is less than 0.005 down to 0.00. For this reason, the
size of a virtual disk that is less than 0.005 is displayed as 0.00.
Solution: Dell is working to resolve this problem.
* Using the Go Back To Previous Page button in the Advanced Create
Virtual Disk Wizard may display an error message.
Problem: When attempting to use the Go Back To Previous Page button
in the Advanced Create Virtual Disk Wizard, Storage Management may
fail to display the previous page and instead display an error
message.
Solution: Dell is working to resolve this problem.
* Rebuild menu option is displayed even when the Rebuild function is
not available.
Problem: A Rebuild task is not available for array disks that are
offline. The Rebuild menu option may continue to be displayed,
however.
Solution: Dell is working to resolve this problem.
* An array disk with a small amount of free disk space may not be
usable in a virtual disk.
Problem: Array disks with 0.01 available disk space may not be
displayed as available when creating a virtual disk.
Solution: Dell is working to resolve this problem.
* Failed array disk not identified as missing after a rescan.
Problem: On the PERC 2, PERC 2/Si, PERC 3/Si, PERC 3/Di,
CERC SATA1.5/6ch, and CERC SATA1.5/2s controllers, a controller
rescan only detects the array disks attached to the controller.
If an array disk being used by a virtual disk has failed, it may
not be identified as "missing" from the virtual disk after the
rescan.
Solution: Dell is working to resolve this problem.
* RAID 1 virtual disk may not rebuild onto global hot spare.
Problem: On a PERC 2/DC controller, a RAID 1 virtual disk that
is degraded due to an array disk failure may not automatically
rebuild onto a global hot spare.
Solution: Perform a rebuild on the array disk assigned as a global
hot spare. Dell is working to resolve this problem.
* Reconfiguring virtual disk displays error in Mozilla browser.
Problem: When reconfiguring a virtual disk using the Mozilla
browser, the following error message may display:
"Although this page is encrypted, the information you have
entered is to be sent over an unencrypted connection and could
easily be read by a third party."
Solution: You can disable this error message by changing a Mozilla
browser setting. To disable this error message:
1) Select View --> Preferences.
2) Click Privacy and Security.
3) Click SSL.
4) Uncheck the "Sending form data from an unencrypted page to an
unencrypted page" option.
* Create virtual disk may fail due to lack of free space.
Problem: In Storage Management, virtual disks created on a
PERC 2/SC, 3/SC, 2/DC, 3/DCL, 3/DC, 3/QC, 4/SC, 4/DC, 4e/DC,
4/Di, 4e/Si, 4e/Di, or CERC ATA100/4ch controller cannot be
created from array disks with an aggregate size greater than 2TB.
If you attempt to create a virtual disk that exceeds the 2TB
limit, the create virtual disk operation will fail.
Solution: The 2TB limit is imposed by the controller. You will
need to change your array disk selection in order to avoid this
limitation. This limitation is documented in the Storage
Management online help. Error messages will also document this
limitation in a future release.
* 1TB or larger virtual disks created in BIOS display with a smaller
size in Storage Management.
Problem: Storage Management does not allow you to create a virtual
disk from array disks with an aggregate size greater than 2TB on the
PERC 2/SC, 3/SC, 2/DC, 3/DCL, 3/DC, 3/QC, 4/SC, 4/DC, 4e/DC, 4/Di,
4e/Si, 4e/Di, or CERC ATA100/4ch controllers. If you use the BIOS to
create a virtual disk using array disks that exceed 2TB, then Storage
Management may display the virtual disk as having a smaller size. For
example, if you create a RAID 10 in the BIOS using four 500MB array
disks, the virtual disk size is 1TB whereas the aggregate array disk
size is 2TB. In this case, Storage Management may display the virtual
disk size as less than 1TB.
Solution: Dell is working to resolve this problem.
* On Linux, the size of a virtual disk is limited to 1TB.
Problem: On Linux, the size of a virtual disk is limited
to 1TB. For this reason, when you create a virtual disk on Linux
using the Create Virtual Disk wizard, the wizard limits the virtual
disk size to 1024GB. The controller BIOS is unable to enforce Linux
restrictions and will therefore allow you to create a virtual disk
that exceeds 1TB on Linux. In this case, Storage Management displays
the virtual disk with the size specified in the BIOS.
Solution: When creating virtual disks on Linux using the Create
Virtual Disk wizard, limit your array disk selection to 1024GB or
less to avoid unused (leftover) space on the array disks. When using
the BIOS to create a virtual disk on Linux, limit the virtual disk size
to 1024GB or less.
* Virtual disks created in excess of 16 may not be visible to the
Linux operating system.
Problem: On a Linux system, Storage Management may allow you to
create more than 16 virtual disks on the PERC 2, 2/Si, 3/Si,
3/Di, and CERC SATA1.5/6ch controllers. The controller driver,
however, is only able to communicate the presence of 16 virtual
disks to the Linux operating system. For this reason, virtual
disks created in excess of 16 are not visible to Linux.
Solution: On a Linux system, avoid creating more than 16 virtual
when using a PERC 2, 2/Si, 3/Si, 3/Di, or CERC SATA1.5/6ch controller.
* A virtual disk of minimum size is not visible to Windows Disk
Management.
Problem: If you create a virtual disk using the minimum allowable
size in Storage Management, the virtual disk may not be visible to
Windows Disk Management even after initialization.
Solution: Windows Disk Management is only able to recognize
extremely small virtual disks if they are dynamic. It is generally
advisable to create virtual disks of larger size when using
Storage Management.
* Virtual disk Regenerating status not documented in online help.
Problem: When an array disk in a virtual disk is being rebuilt,
the virtual disk displays Regenerating status. The Regenerating
status is not documented in the Storage Management online help.
Solution: Dell is working to resolve this problem.
* Reconfiguring a concatenated virtual disk to a RAID 1 displays
Resynching state.
Problem: On a PERC 2, 2/Si, 3/Si, 3/Di, or CERC SATA1.5/6ch
controller, a virtual disk that is being reconfigured from
concatenated to RAID 1 displays the Resynching state followed
by the Reconstruct state. In most cases, a virtual disk that is
being reconstructed only displays the Reconstruct state.
Solution: The virtual disk reconfiguration should progress normally
even though the displayed state may change from Resynching to
Reconstruct.
* No error displayed when global hot spare is too small for newly
created virtual disk.
Problem: A hot spare is an unused backup array disk that can be
used to rebuild data from a redundant virtual disk. A global hot
spare is assigned to all redundant virtual disks residing on
the controller. Storage Management does not display an error
message or otherwise prevent you from creating a virtual disk
that is too large to be protected by an existing global hot spare.
Solution: Dell is working to resolve this problem.
* Storage Management does not generate an alert for missing
controller battery.
Problem: Storage Management does not generate an alert or
SNMP trap when a controller battery is missing. In this
situation, the battery state is displayed as Missing.
Solution: Dell is working to resolve this problem.
* There may be a delay in new objects in Storage Management being
reported through SNMP.
Problem: When objects, such as virtual disks are newly created in
Storage Management there may be a delay of up to 5 minutes before
they are reported through SNMP. This includes the creation of a
virtual disk and performing an unmirror or split mirror function
on a RAID-1 concatenated virtual disk on a PERC 2, 2/Si, 3/Si,
3/Di, or CERC SATA1.5/6ch controller.
Note: Deleted objects will be reflected immediately through SNMP.
Solution: This delay can be minimized by forcing a controller rescan.
######################################################################
Information in this document is subject to change without notice.
(C) 2004 Dell Inc. All rights reserved.
Reproduction in any manner whatsoever without the written permission
of Dell Inc. is strictly forbidden.
Trademarks used in this text: "Dell", "PowerEdge", "PowerVault", and
"Dell OpenManage" are trademarks of Dell Inc.; "Microsoft", "Windows",
and "Windows NT" are registered trademarks of Microsoft Corporation;
"Novell" and "NetWare" are registered trademarks of Novell, Inc.;
"Red Hat" is a registered trademark of Red Hat, Inc. "EMC" and
"Navisphere" are registered trademarks of EMC Corporation; "VERITAS"
is a registered trademark and "Backup Exec" is a trademark of VERITAS
Software Corporation.
Other trademarks and trade names may be used in this document to refer
to either the entities claiming the marks and names or their products.
Dell Computer Corporation disclaims any proprietary interest in
trademarks and trade names other than its own.
August, 2004
DELL OPENMANAGE(TM) Storage Management, VERSION 1.0 README
Download Driver Pack
After your driver has been downloaded, follow these simple steps to install it.
Expand the archive file (if the download file is in zip or rar format).
If the expanded file has an .exe extension, double click it and follow the installation instructions.
Otherwise, open Device Manager by right-clicking the Start menu and selecting Device Manager.
Find the device and model you want to update in the device list.
Double-click on it to open the Properties dialog box.
From the Properties dialog box, select the Driver tab.
Click the Update Driver button, then follow the instructions.
Very important: You must reboot your system to ensure that any driver updates have taken effect.
For more help, visit our Driver Support section for step-by-step videos on how to install drivers for every file type.