Dell(TM) OpenManage(TM) Array Manager 3.4 Readme
This readme file contains updated information for your Dell
OpenManage Array Manager User's Guide and any other technical
documentation included with this product.
Always see the Dell support Website at support.dell.com
for the most current information.
The following sections contain updated requirements and open issues
for the Dell OpenManage Array Manager version 3.4 software.
==================================================================
Dell OpenManage Array Manager 3.4
==================================================================
--------
Contents
--------
I. New Features in Array Manager 3.4
II. Installation Requirements for Array Manager 3.4
III. Backward Compatibility
IV. Installing on Windows
V. Installing on NetWare
VI. Remote Installation on Windows Server 2003
VII. Warnings
VIII. Array Manager Directory Structure
IX. Required Driver/Firmware Revisions
X. Compatibility Issues
XI. Fixed Issues
XII. Known Issues
XIII. Changes to the Array Manager Documentation
----------------------------------------------
I. NEW FEATURES IN ARRAY MANAGER 3.4
----------------------------------------------
Array Manager 3.4 provides the following enhancements:
* Support for the Windows Server 2003 64-bit operating system.
This support only includes the following:
-- The PERC 3/QC and PowerVault 660F controllers as well
as 64-bit applications are supported on a Windows Server 2003
64-bit system.
-- All controllers supported by Array Manager are supported
on a Windows Server 2003 32-bit system.
Array Manager does not support Windows disk or volume management
on Windows Server 2003.
* Array Manager has a new Create Virtual Disk wizard which simplifies
creating virtual disks and maximizes efficient usage of disk space.
The new Create Virtual Disk wizard also enables you to implement
channel-redundant virtual disks. You no longer need to use a BIOS
configuration utility to implement channel redundancy.
* Support for NetWare 4.x is no longer provided in Array Manager 3.4.
------------------------------------------------
II. INSTALLATION REQUIREMENTS FOR ARRAY MANAGER
------------------------------------------------
The following sections describe the Array Manager installation
requirements:
General Requirements
Management Console Requirements (Client)
Managed System for Windows Requirements (Server)
Managed System for NetWare Requirements (Server)
Online Help Requirements
** GENERAL REQUIREMENTS **
The following requirements apply to any system running the Array
Manager console (client) or the Array Manager managed system (server):
* 64 megabytes (MB) of RAM.
* Administrator access to the system.
* For information on supported operating systems for the Array Manager
console and managed system, see the following sections:
- Management Console Requirements (Client)
- Managed System for Windows Requirements (Server)
- Managed System for NetWare Requirements (Server)
* Transmission Control Protocol/Internet Protocol (TCP/IP) connection
on the console and server when attempting remote system management.
* Simple Network Management Protocol (SNMP) services are required for
SNMP support. If you do not have SNMP, Array Manager will function
as normal but will not provide SNMP support.
Note: If you intend to web serve Array Manager, Internet Information Services
(including the World Wide Web Server component) must be installed on the
Web server prior to installing Array Manager. If you install Internet
Information Services after installing Array Manager, you will need to
Add/Modify (reinstall) Array Manager before web serving an Array Manager
installation.
Note: Dell provides configuration utilities that enable you to perform
certain RAID management operations using the PERC 2/SC, 2/DC, 3/SC, 3/DCL,
3/DC, 3/QC, 4/SC, 4/DC, 4/Di, 4/IM, CERC ATA100/4ch and PERC 2, 2/Si, 3/Si,
and 3/Di controllers on platforms not currently supported by Array Manager.
These utilities are available at support.dell.com.
** MANAGEMENT CONSOLE REQUIREMENTS (CLIENT) **
The following are minimum requirements for installing the Array Manager
console. The console is the client portion of Array Manager.
* 64 megabytes (MB) of RAM.
* 40 MB of free hard drive space.
* One of the following versions of Windows:
- Microsoft Windows NT(R) Server or Workstation 4.x with service pack 6
or later. Array Manager only supports Windows NT on PERC 4/SC and 4/DC
controllers.
- Windows NT 4 Terminal Server. Array Manager only supports Windows NT on
PERC 4/SC and 4/DC controllers.
- Microsoft Small Business Server.
- Microsoft Windows 2000 Server with service pack 1 or later.
- Microsoft Windows 2000 Advanced Server with service pack 1 or later.
- Microsoft Windows 2000 Professional with service pack 1 or later.
- Microsoft Windows XP.
- Microsoft Windows Server 2003 Enterprise Server.
Note: It is highly recommended that you use the most current service pack.
* Administrator rights.
* Transmission Control Protocol/Internet Protocol (TCP/IP) connection
on the console and server when attempting remote system management.
* Microsoft Management Console (MMC) Version 1.2 or later for snap-in support
on Windows 2000 and Windows Server 2003. MMC snap-in support is an optional
feature on Windows NT.
* (Optional). Novell Client for Windows version 4.6 or later if you intend
to map a drive to NetWare system and copy the Array Manager install media
from the Windows system to the NetWare system.
* (Optional). Microsoft Internet Explorer Version 4.0 or later for
viewing the online help and the browser plug-in.
** MANAGED SYSTEM FOR WINDOWS REQUIREMENTS (SERVER) **
The following are minimum requirements for installing a managed system for
Windows.
* A server running one of the following versions of Windows:
- Windows NT Server 4.x (including enterprise edition) with service
pack 6 or later. Array Manager only supports Windows NT on
PERC 4/SC and 4/DC controllers.
- Windows NT 4 Terminal Server. Array Manager only supports Windows NT on
PERC 4/SC and 4/DC controllers.
- Microsoft Small Business Server.
- Microsoft Windows 2000 Server with service pack 1 or later
- Microsoft Windows 2000 Advanced Server with service pack 1 or later
- Microsoft DataCenter
- Microsoft Windows Server 2003 Enterprise Server
Note: It is highly recommended that you use the most current service pack.
* 64 MB of RAM.
* 15 MB of free hard disk space on the local drive.
* Administrator access to the system.
* Hardware and drivers installed for at least one Dell RAID controller. Drivers
and firmware for supported controllers can be downloaded from the Dell support
site at support.dell.com.
* Fibre Channel Host Bus Adapters and associated device drivers are needed to
manage the Dell PowerVault 660F Fibre Channel RAID array in either a
direct-attach or SAN environment.
* (Optional) TCP/IP installation if this system will be managed over a network.
* (Optional). Simple Network Management Protocol (SNMP) for SNMP trap forwarding by
Array Manager. The SNMP service should be installed prior to installing Array Manager.
* (Optional) Array Manager requires that the Dell OpenManage Server Agent
(OMSA) 4.0.0 or later be installed on the managed system to provide thermal
shutdown (when an enclosure becomes too hot or cold) for the Dell PowerVault
20xS, 21xS, and 22xS SCSI enclosures. If OMSA is not installed, Array Manager can
provide other features of enclosure management, but not thermal shutdown.
Note: The managed system’s RAID controllers must be attached to storage in order to
run Array Manager.
** MANAGED SYSTEM FOR NETWARE REQUIREMENTS (SERVER) **
The following are minimum requirements for installing a managed system for
NetWare.
* 64 megabytes of RAM.
* 15 megabytes of free hard disk space.
* Administrator or supervisor access to the system.
* One of the following versions of Novell NetWare:
- Novell NetWare version 5.1 or later with Support Pack 4 or later.
- Novell NetWare version 6.0 or later with Support Pack 1 or later is
supported in a SCSI environment. (See the Dell PowerVault Systems Storage
Area Network (SAN) documentation for information on SAN support for NetWare.)
* Hardware and drivers installed for at least one Dell RAID controller.
Drivers and firmware for supported controllers can be downloaded from the
Dell support site at support.dell.com.
* Fibre Channel Host Bus Adapters and associated device drivers are needed to
manage the Dell PowerVault 660F Fibre Channel RAID Array in either a
direct-attach or SAN environment. See the Dell PowerVault Systems Storage
Area Network (SAN) documentation for information on supported NetWare
configurations.
* Transmission Control Protocol/Internet Protocol (TCP/IP) required for connection
to the management console.
* Long file name support.
* (Optional). Novell Client for Windows version 4.6 or later installed on a remote
Windows system if you intend copy the Array Manager install media from the Windows
system to the NetWare system by mapping a drive.
* (Optional). Simple Network Management Protocol (SNMP) for SNMP trap forwarding
by Array Manager.
* (Optional) Array Manager requires that the Dell OpenManage Server Agent
(OMSA) 4.0.0 or later be installed on the managed system to provide thermal
shutdown (when an enclosure becomes too hot or cold) for the Dell PowerVault
20xS, 21xS, and 22xS SCSI enclosures. If OMSA is not installed, Array Manager can
provide other features of enclosure management, but not thermal shutdown.
Note: The managed system’s RAID controllers must be attached to storage in order to
run Array Manager.
Note: When installing on NetWare, the Array Manager installation may not recognize
the pedge.ham version 2.06 driver on a PERC 2/SC or PERC 2/DC controller. If the
Array Manager installation displays an error message regarding the 2.06 driver,
update the driver to pedge3.ham version 3.13.
** ONLINE HELP REQUIREMENTS **
Internet Explorer version 4.0 or later is required for launching and viewing
the online help from the Array Manager console.
---------------------------
III. BACKWARD COMPATIBILITY
---------------------------
On a Windows system, Array Manager 2.5 or later can be upgraded to
version 3.4. If you have a version of Array Manager that is
earlier than version 2.5, you should uninstall this version and
perform a fresh install of Array Manager 3.4.
On a NetWare system, you need to uninstall any existing versions of
Array Manager before installing Array Manager 3.4.
An Array Manager 3.4 console can connect to a version
2.5 managed system or later. However, using a version of the console
earlier than 3.4 to connect to a version 3.4 managed system is not
supported.
-------------------------
IV. INSTALLING ON WINDOWS
-------------------------
The Setup program takes you through the process of installing the
Array Manager software. Before proceeding, you should exit all
Microsoft Windows programs and log on with Administrator rights.
Installing from the Dell OpenManage Systems Management CD:
1. Insert the CD. Setup should begin automatically. If not,
start setup by double-clicking on the Setup icon in the root
directory of the CD. (If you are installing Array Manager on
Windows NT, refer to the next section.)
2. Follow the instructions shown in the Setup wizard. You may need
to use Custom Setup to install Array Manager.
3. Reboot the system when finished.
Installing on Windows NT from the Dell OpenManage Systems Management CD:
If you have a PERC 4/SC or 4/DC controller, you can install Array
Manager on Windows NT.
1. Insert the CD.
2. Open the am34 directory which is located in the Dell OpenManage Systems
Management CD’s root directory.
3. Double-click the Setup icon located in the am34 directory to start the
Array Manager setup.
4. Follow the instructions shown in the Setup wizard.
5. Reboot the system when setup is finished.
Installing from the Dell OpenManage Array Manager CD:
1. Insert the CD. Setup should begin automatically. If not,
start setup by double-clicking on the Setup icon in the Setup
directory of the CD.
2. Follow the instructions shown in the Setup wizard.
3. Reboot the system when finished.
NOTE: When installing the managed system component on a Windows 2000
system, the Windows 2000 Plug and Play Manager will activate
after the reboot, indicating that it has discovered new hardware.
You may be required to perform a second reboot if volumes are
present on your system. Otherwise, allow Plug and Play to
register the new driver. (This occurs automatically.)
---------------------------
V. INSTALLING ON NETWARE
---------------------------
You can install the Array Manager managed system on a NetWare server.
You can then connect to the NetWare server from the Array Manager
console.
Use the following steps to install the Array Manager managed system
on the NetWare server using an installation CD.
1) If a version of Array Manager is already installed on the NetWare
system, then uninstall that version before continuing with the install
of Array Manager 3.4.
2) Insert the Array Manager installation CD into the NetWare server’s
CDROM drive.
3) Mount the installation CD as a NetWare volume.
4) Locate the AMINST.NLM and AMINST.IPS files on the Array Manager
installation CD. The AMINST.NLM and AMINST.IPS files may be
located in the NETWARE directory.
If you have the Dell OpenManage Applications CD, then the AMINST.NLM
and AMINST.IPS files are located in the <VolumeName>\NetWare\AM34\NetWare
subdirectory.
If you have the Array Manager installation CD, then the AMINST.NLM and
AMINST.IPS files are located in the NETWARE subdirectory.
5) Start the NetWare configuration utility by entering the following from
the NetWare system console:
nwconfig
6) Select Product Options and then Install product not listed.
7) Specify the full path to the directory containing the AMINST.NLM and
AMINST.IPS files on the Array Manager installation CD. NetWare completes
the installation for you.
Note: Installing Array Manager disables the NetWare QLCSFTE.CDM and DellSEP.CDM
drivers. You should not attempt to manually install these drivers. For more
information, see the "Compatibility Issues" section of this readme file.
-----------------------------------------------
VI. REMOTE INSTALLATION ON WINDOWS SERVER 2003
-----------------------------------------------
Array Manager enables you to perform an unattended or silent installation
on a remote Windows machine. When performing an unattended installation,
you run an install script that contains the steps for the installation.
Array Manager provides different install scripts that contain different
installation scenarios. The script for installing on Windows Server 2003
is named typw2k3.iss. When installing on Windows Server 2003, the typw2k3.iss
script should be used in place of the Typical.iss script described in the
Array Manager online help. For more information on unattended installation,
refer to the "Unattended (Silent) Installation" section of the "Installation
and Upgrades" chapter of the online help.
---------------
VII. WARNINGS
---------------
* The Windows NT Disk Administrator should never be used while
Array Manager is running, particularly if there are tasks running
at the same time on the controller. DATA LOSS CAN OCCUR IF BOTH
APPLICATIONS ARE RUNNING SIMULTANEOUSLY.
* PowerEdge servers earlier than x300 are not supported.
* The (clustered) PERC 3/DCs and the PowerVault 660F fibre channel
controller are the only clustered controllers supported
by this software.
* In a clustered environment, it is recommended that all virtual disks
use the entire capacity of their member array disks. In a situation
where a virtual disk only uses a portion of an array disk, a failed
array disk may not rebuild properly.
* When importing foreign disks that contain a dynamic volume
created previously by Array Manager, YOU MUST IMPORT ALL OF THE
DISKS THAT MAKE UP THE VOLUME AT THE SAME TIME. Failure to do
so will result in DATA LOSS.
* NEVER remove a hard drive from its enclosure while the drive's
individual activity light emitting diode (LED) is blinking. This
action is likely to cause SEVERE DATA LOSS.
* PERCs have a feature called "PowerFail" that uses up to two
assigned hot spares during reconfiguration of a virtual disk
(Transform Type, Add Member). While this reconstruction is in
progress, NEVER remove the hot spare array disks that are part of
the reconstruction.
* As a general rule, you should be logged on to the local computer
system with Administrator access rights when launching the Array
Manager console.
* If you upgrade from Windows NT to Windows 2000, you should uninstall
Array Manager before the upgrade. After the upgrade, reinstall Array
Manager using the Array Manager install media or by downloading Array
Manager from the Dell Website at support.dell.com.
--------------------------------------
VIII. ARRAY MANAGER DIRECTORY STRUCTURE
--------------------------------------
If you are reading this from an Array Manager CD, the following
subdirectories are located in the root directory of CD. These
subdirectories are also the subfolders that make up the ZIP file
downloadable from the support website. If you are reading this
from the Dell OpenManage Applications CD, these folders
are subfolders of /AM34 at the root directory.
\DOCUMENTATION - Contains the Array Manager documentation in
HTML format.
\SETUP - Contains the files used for installation of
Array Manager on a Windows NT or Windows 2000 operating system.
\UPDATE - Contains the HTML Help Viewer update package.
\NETWARE - Contains files used for installing Array Manager on
Netware operating systems.
\MMC - Contains the files used for installing the Microsoft
Management Console (MMC) snap-in on Windows NT. The Array
Manager MMC snap-in enables you to run Array Manager from
the MMC console.
----------------------------------------
IX. REQUIRED DRIVER/FIRMWARE REVISIONS
----------------------------------------
*** PERC RAID Controller Cards ***
These include PERC 2/SC, 2/DC, 3/SC, 3/DC, 3/DCL, 3/QC, 4/SC, 4/DC, 4/Di, 4/IM,
and CERC ATA100/4ch.
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 NT Windows 2000 Windows NetWare
Driver Driver Server Driver
2003
Driver
PERC 2/SC 3.13 2.32 2.68 6.32.2.32 NW 5.x (2.06)
NW 6.x (6.02)
Note: NetWare is not
supported on PowerEdge
x300 systems with a
PERC 2/SC.
PERC 2/SC on a 3.13 4.18 2.68 6.32.2.32 NW 5.x (6.02)
PowerEdge 8450 NW 6.x (6.02)
PERC 2/DC on a 1.06 2.32 2.68 6.32.2.32 NW 5.x (2.06)
PowerEdge x300 NW 6.x (N/A)
PERC 2/DC on a 1.06 4.18 2.68 6.32.2.32 NW 5.x (6.02)
PowerEdge x400 NW 6.x (6.02)
PERC 3/SC 1.78 4.18 5.39 6.32.2.32 NW 5.x (7.01n)
NW 6.x (7.01n)
PERC 3/DC 1.78 4.18 5.39 6.32.2.32 NW 5.x (7.01n)
NW 6.x (7.01n)
PERC 3/DCL 1.78 4.18 5.39 6.32.2.32 NW 5.x (7.01n)
NW 6.x (7.01n)
PERC 3/QC 1.78 4.18 5.39 6.32.2.32 NW 5.x (7.01n)
NW 6.x (7.01n)
PERC 4/SC 3.15 4.18 5.39 6.32.2.32 NW 5.1 (7.01n)
NW 6.x (7.01n)
PERC 4/DC 3.15 4.18 5.39 6.32.2.32 NW 5.1 (7.01n)
NW 6.x (7.01n)
PERC 4/Di on a 2.23 4.18 5.39 6.32.2.32 NW 5.x (7.01n)
PowerEdge 2600 NW 6.x (7.01n)
PERC 4/Di on a 4.00 N/A 5.39 6.32.2.32 NW 5.x (N/A)
PowerEdge 1750 NW 6.x (N/A)
PERC 4/IM on a 1.00.12.00 1.08.06 1.08.06 1.08.18 NW 5.x (N/A)
PowerEdge NW 6.x (N/A)
1655MC
PERC 4/IM 1.1 1.02.09.00 1.08.19 1.08.19 1.08.18 NW 5.x (3.01.00)
NW 6.x (3.01.00)
CERC 6.62 4.18 5.39 6.32.2.32 NW 5.1 (7.01n)
ATA 100/4CH NW 6.x (7.01n)
Note: When installing on NetWare, the Array Manager
installation may not recognize the pedge.ham version 2.06
driver on a PERC 2/SC or PERC 2/DC controller. If the Array
Manager installation displays an error message regarding the
2.06 driver, update the driver to pedge3.ham version
3.13.
Note: PERC is not supported by Array Manager 3.4 on any operating
system. PERC is supported by Array Manager version
2.0 on Windows NT and NetWare.
*** PERC 2 RAID Controller Cards + RAID On Motherboard (ROMB) ***
These include PERC 2, PERC 2/Si, PERC 3/Si, and PERC 3/Di.
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 the PERC 2 controller prior to 2.7.1 are not supported. The
minimum requirement of 2.7.1 applies to all of the PERC 2, PERC 2/Si, PERC 3/Si, and
PERC 3/Di controllers.
Note: Array Manager requires that the system be rebooted before Array Manager can
properly determine whether the system meets the firmware and driver requirements
for the PERC 2, PERC 2/Si, PERC 3/Si, and PERC 3/Di controllers. For this reason,
it is possible to complete an initial installation of Array Manager without being
notified whether your system meets the firmware and driver requirements. If you
install Array Manager and reboot the system, you can view the correct firmware
and driver requirements through the Array Manager Utilities. If you reinstall
or upgrade Array Manager, the install process will notify you of the firmware
and driver requirements.
Controller Firmware Windows NT Windows 2000 Windows NetWare
Driver Driver Server Driver
2003
Driver
PERC 2 3170 4944 4944 4944 NW 5.x (3564)
NW 6.x (3564)
PERC 2/Si 3571 4944 4944 4944 NW 5.x (3564)
NW 6.x (3564)
PERC 3/Si 3571 4944 4944 4944 NW 5.x (3564)
NW 6.x (3564)
PERC 3/Di on a 3170 4944 4944 4944 NW 5.x (3564)
PowerEdge 1650 NW 6.x (3564)
PERC 3/Di on a 3170 4944 4944 4944 NW 5.x (3564)
PowerEdge 2500 NW 6.x (3564)
PERC 3/Di on a 3571 4944 4944 4944 NW 5.x (3564)
PowerEdge 2550 NW 6.x (3564)
PERC 3/Di on a 3170 4944 4944 4944 NW 5.x (3564)
PowerEdge 2650 NW 6.x (3564)
PERC 3/Di on a 3571 4944 4944 4944 NW 5.x (3564)
PowerEdge 4400 NW 6.x (3564)
PERC 3/Di on a 3170 4944 4944 4944 NW 5.x (3564)
PowerEdge 4600 NW 6.x (3564)
*** PowerVault 660F ***
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.
SAN 4.06:
Controller HBA BIOS Windows NT or 2000 Driver
PowerVault 660F QL2100 1.35 QL2100.SYS 7.05.08
PowerVault 660F QL2200 1.45 QL2200.SYS 7.05.08
SAN 5.01:
Controller HBA BIOS Windows NT or 2000 Driver
PowerVault 660F QL2200 1.76 QL2200.SYS 8.00.09.24
SAN 4.06 and 5.01 support Windows NT and Windows 2000.
For the latest information on SAN support for NetWare, see the
Dell PowerVault Systems Storage Area Network (SAN) documentation.
Note: The background initialization feature on PowerVault 660F controllers
is only available when using PowerVault 660F controller firmware
7.7 or later.
*** Ultra SCSI controller Cards ***
These include Ultra SCSI, Ultra2 SCSI, Ultra160 SCSI, Ultra320 SCSI
Firmware for the Ultra SCSI controller cards is provided in the BIOS.
------------------------
X. COMPATIBILITY ISSUES
------------------------
* Applications that query the Array Manager Management Information Base
(MIB) may experience unpredictable behavior when Array Manager is
installed on a system that also has HP OpenView installed.
IT Assistant is an example of an application that may query the Array
Manager MIB. If you install Array Manager on a system that has
HP OpenView installed, IT Assistant may receive erroneous values (such
as null strings) when querying the Array Manager MIB. It is possible
that rebooting the system will resolve these problems.
This compatibility issue with HP OpenView does not affect the receipt
of events in the Array Manager event log or SNMP trap forwarding.
* Compatibility issues with the NetWare 6 QLCSFTE.CDM and DellSEP.CDM
drivers. (Issue 49350)
There is an incompatibility between the QLCSFTE.CDM and DellSEP.CDM
drivers in NetWare 6 and the enclosure management provided by Array
Manager. In NetWare 6, the hardware discovery logic detects the
Qlogic chips within the server and auto installs the QLCSFTE.CDM
and DellSEP.CDM drivers. These drivers interfere with the Array
Manager enclosure management.
To resolve this problem, the Array Manager installation process
comments out the lines for loading the QLCSFTE.CDM and DellSEP.CDM
drivers in the STARTUP.NCF file. You should not remove the
";(Commented out by install...)" designation within the STARTUP.NCF
file or attempt to manually re-install these drivers. If you do
restore the QLCSFTE.CDM and DellSEP.CDM drivers, then the enclosure
management features of Array Manager will not function on NetWare 6.
When you uninstall Array Manager, the QLCSFTE.CDM and DellSEP.CDM
drivers are restored.
* Compatibility Issues With the Flexible Array Storage Tool (FAST):
Due to compatibility issues with FAST, Array Manager cannot be
installed on a system that has FAST installed. If the installation
process detects that FAST is installed on your system, the
installation process will not complete. In this case, the
installation process displays a message indicating that the
installation cannot be completed. When installed, the FAST application
name in the Windows Control Panel is Dell PERC2.
Note that when you install the Dell OpenManage Server Agent, you
may be prompted to also install FAST. FAST should not be installed
since this will conflict with the Array Manager installation.
* Compatibility Issues With the PERC console:
Both Array Manager and the PERC console can be installed on the
same server. However, only one program at a time can be used to
configure PERC 2/SC, PERC 3/SC, PERC 2/DC, PERC 3/DC, PERC 3/DCL,
PERC 3/QC, PERC 4/SC, PERC 4/DC, 4/Di, 4/IM and CERC ATA100/4ch
controllers. To maintain the integrity of the storage device
configuration, simultaneous use of Array Manager and the PERC
console is not supported. Dell strongly recommends that Array
Manager and the PERC console not be used at the same time on the
same server.
Note that when you install the Dell OpenManage Server Agent, you
may be prompted to also install the PERC console. Given the
compatibility problems with the PERC console, you should
consider not installing it.
* Compatibility Issues With the Windows NT Disk Administrator:
The Windows NT Disk Administrator should never be used while
Array Manager is running, particularly if there are tasks running
at the same time on the controller. DATA LOSS CAN OCCUR IF BOTH
APPLICATIONS ARE RUNNING SIMULTANEOUSLY.
* Disabling the Array Manager Disk Management Service:
If you do not want the Array Manager Disk Management service
to start automatically each time you boot your machine, you can
set the service to manual start only.
Use the following steps to change the Array Manager Disk
Management service from automatic start to manual start.
On Windows NT:
1. Select "Start"-->"Settings"-->"Control Panel".
2. Double-click "Services."
3. Select "Disk Management Service."
4. Click "Startup..."
5. For Startup Type, select "Manual."
On Windows 2000:
1. Select "Start"-->"Settings"-->"Control Panel"-->
"Administrative Tools"-->"Services".
2. Select "Services" in the left pane.
3. Double-click "Disk Management Service" in the
right pane.
4. Select the "General" tab.
5. Select "Manual" from the "Startup type" pull-down menu.
6. Click "OK."
NOTICE: If the Array Manager Disk Management Service is not started,
you will not receive any alerts or warnings in the event of a failure.
* Compatibility Issues with the Dell OpenManage Server Agent
When using Array Manager with the Dell OpenManage Server Agent
1.0 through 1.4.x, you may receive duplicate events regarding the
following enclosures:
Dell PowerVault 200S
Dell PowerVault 201S
Dell PowerVault 210S
Dell PowerVault 211S
For this reason, installation of Array Manager disables the Dell
OpenManage Server Agent's enclosure management for versions of the
Server Agent 1.0 through 1.4.x.
------------------
XI. FIXED ISSUES
------------------
* The Add Category function may improperly add or delete items from view.
(Issue 61538)
Problem: When creating objects in the Array Manager tree view (for
example, creating a folder in the tree view to contain virtual disks),
attempts to add or delete a single lower-level object may result in all
lower-level objects being added or deleted.
Solution: Dell has resolved this problem.
* Launching Array Manager from the command line with a device specified
may not work properly. (Issue 62968)
Problem: When launching Array Manager from the command line with a device
parameter specified in the amconsole command syntax, the Array Manager
console may launch with only the Arrays folder expanded showing all
controllers. It does not highlight the device specified.
Solution: Dell has resolved this problem.
* When upgrading a RAID 10 virtual disk to dynamic, Array Manager may
incorrectly display the virtual disk strip size to be 0KB. (Issue 62701)
Problem: After you have upgraded a RAID 10 virtual disk to dynamic,
Array Manager may incorrectly display the virtual disk strip size to be 0KB.
Solution: Dell has resolved this problem.
* Cannot initialize or delete a virtual disk containing a boot partition on
Windows Server 2003. (Issue 39787)
Problem: If you create a virtual disk using array disks that
previously contained a boot partition, you will not be able to
initialize or delete the virtual disk on Windows Server 2003.
Solution: Dell has resolved this problem.
* An offline disk is not visible in Array Manager on a PERC 4/IM
controller. (Issue 62931)
Problem: The PERC 4/IM controller is used to mirror disk drives that
reside internally in the server. If you offline one of these mirrored
disks and reboot the system without returning the disk to online, then
the disk is no longer visible in Array Manager, even after rebooting
the system.
Solution: Dell has resolved this problem.
* The PERC 4/IM controller does not detect SMART alerts. (Issue 61560)
Problem: The PERC 4/IM controller is used to mirror disk drives that
reside internally in the server. The PERC 4/IM controller, however,
may not detect SMART alerts. SMART (Self Monitoring Analysis and
Reporting Technology) alerts inform you that a future failure is
predicted for an array disk.
Solution: Dell has resolved this problem.
* The install fails and displays an error message referring to an
error with "iKernel.exe" at the beginning of the installation.
(Issue 25474)
Problem: This is a problem in the Install Shield installation
engine that occurs when running the installation without
Administrator rights.
Solution: Dell has resolved this problem.
------------------
XII. KNOWN ISSUES
------------------
The following sections describe known problems associated
with Array Manager or the supported controllers. Dell is
in the process of resolving these problems. The sections are
as follows:
General Problems
Problems Associated with the PERC Controllers
Problems Associated with the PowerVault 660F and 650F Controllers
** GENERAL PROBLEMS **
* SMART alert displays after replacing a disk. (Issue 75017)
Problem: If have a hot spare that receives a SMART alert,
you can replace the hot spare. In some cases after replacing
the hot spare with a new disk, the SMART alert will still
display for the new disk.
Solution: Restart the Array Manager service.
* Create Volume and Upgrade Disk buttons are enabled on Windows Server 2003.
(Issue 76425)
Problem: Even though Windows Server 2003 does not support disk or volume
management, the Create Volume and Upgrade Disk buttons are enabled on the
Quick Access Windows.
Solution: Be aware that Windows Server 2003 does not support disk or
volume management. The Create Volume and Upgrade Disk wizards do not
function on Windows Server 2003.
* Remote connection fails on servers with multiple NIC teams. (Issue 76228)
Problem: Certain technologies enable you to group multiple NetWork
Interface Cards (NICs) into groups known as "teams." Array Manager
may not allow you to connect remotely to a server that has multiple
NIC teams.
Solution: Dell is working to resolve this problem.
* Basic disks may disappear under the Disks object in the tree view
when initializing a virtual disk. (Issue 50525)
Problem: If the "Hide unknown disks" option is selected on the
Array Manager Quick Access Window, then the basic disks displayed
under the Disks object in the Array Manager tree view may disappear
when you initialize a virtual disk.
Solution: To resolve this problem do the following:
1. Launch Windows Explorer.
2. Right-click a volume that resides on a basic disk that no longer
displays under the Disks object in Array Manager and select Properties.
* Array Manager installation process does not display the status of
required firmware for a PERC 3/QC controller on Windows Server 2003 (64 bit).
(Issue 29037)
Problem: When installing Array Manager, the installation process
verifies whether you have the firmware and drivers required by the
controllers installed on your system. The installation process
displays the firmware and driver status as either "Passed" or "Failed"
to indicate whether your system meets the requirements. For PERC 3/QC
controllers, the installation process may not be able to determine
whether the requirements have been met on Windows Server 2003 (64 bit).
In this case, the status is displayed as "Undetermined."
Solution: If the installation process displays "Undetermined" as the
status for a PERC 3/QC controller, then you should verify yourself that
the correct firmware and drivers are installed on the system. Refer to
the "Required Driver/Firmware Revisions" section of this readme file
for the required driver and firmware versions.
* DCOM (Distributed Component Object Model) (Issue 19827)
Problem: A large number of DCOM messages appear in the "Event
Viewer" resulting in the following message:
"DCOM was unable to communicate with the computer ...
using any of the configured protocols."
Solution: Run "dcocnfg.exe" and click the "Default Protocols" tab.
Remove all of the protocols EXCEPT "Connection-oriented TCP/IP."
NOTICE: If other applications on a server require that DCOM use
protocols other than TCP/IP, they will no longer function
correctly. If this is the case, the suggested course of action is
to leave the DCOM configuration as it is.
** PROBLEMS ASSOCIATED WITH THE PERC CONTROLLERS **
* Battery fields display "Unknown" in log file. (Issue 66469)
Problem: The PERC 2, 2/Si, 3/Si, and 3/Di controllers
generate a log file to assist in obtaining status and
debugging errors. This log file may display "Unknown" in
the fields relating to battery status.
Solution: Dell is working to resolve this problem.
* Array Manager does not update the Disk View tab at startup on
a PERC 3/DC controller. (ISsue 76523)
Problem: In a cluster configuration on a PERC 3/DC controller,
the Disk View tab on the Array Manager console may not display
updated information after launching Array Manager.
Solution: Perform a Refresh to update the Disk View tab.
* Attempts to split a mirror or unmirror a virtual disk
may fail. (Issue 69787)
Problem: When performing a Split Mirror on a dynamic
virtual disk, you may receive an error message that says
"The Split Mirror failed because the virtual disk is used
as a dynamic disk." Attempts to unmirror the same dynamic
virtual disk may also fail.
Solution: Revert the dynamic virtual disk back to a basic
disk and then unmirror the disk. When completed, you can
make the disk a dynamic disk again.
* Formatting a virtual disk may destroy drive mapping.
(Issue 66471)
Problem: On PERC 2, 2/Si, 3/Si, and 3/Di controllers,
formatting a virtual disk may destroy drive mapping.
For example, during or after the format operation, you
may notice that an operating system disk is offline, disk
objects disappear from the Array Manager tree view, and that
virtual disks are incorrectly mapped to the operating system
disk.
Solution: Reboot the system to restore the correct drive
mapping.
* Create virtual disk may fail on PERC 3/Di controllers.
(Issue 70655)
Problem: If you have already created several virtual disks
on a PERC 3/Di controller, attempts to create additional
virtual disks may fail.
Solution: Reboot the system and then create the additional
virtual disk.
* Attempts to delete a dynamic virtual disk may fail. (Issue 69803)
Problem: On a PERC 3/Di controller, attempts to delete a
dynamic virtual disk may fail.
Solution: Revert the dynamic virtual disk to a basic disk and
then delete it.
* Cannot expand a concatenated virtual disk that fully utilizes
an array disk. (Issue 67588)
Problem: If you have a concatenated virtual disk that uses
the full capacity of one if its array disks, you may not be
able to expand the concatenated virtual disk. This problem
occurs on PERC 2, 2/Si, 3/Si, and 3/Di controllers when the
concatenated virtual disk uses array disks of different sizes.
Solution: Dell is working to resolve this problem.
* Deleting a virtual disk in the BIOS causes incorrect display of
virtual disks in the Array Manager tree view.
Problem: If you delete a virtual disk in the BIOS on a PERC 3/SC,
3/DCL, 3/DC, 3/QC controller, Array Manager may not properly update
the display of virtual disks in the Array Manager tree view.
Specifically, the numbering format for virtual disks in the tree
view may not correspond to the numbering format used in the BIOS.
Solution: Dell is working to resolve this problem.
** PROBLEMS ASSOCIATED WITH THE POWERVAULT 660F AND 650F CONTROLLERS **
* Event message for Add Virtual Disk on a PV660F is not displayed correctly
(Issue 43219)
Problem: When performing an Add Virtual Disk operation, the
Array Manager event log displays event messages indicating that
an Expand Capacity operation has started and completed instead
of an Add Virtual Disk operation.
Solution: Be aware that event messages referring to an Expand
Capacity operation may in fact indicate an Add Virtual Disk
operation.
* Cannot detect when connection is lost to a PowerVault 660F array.
Problem: When the connection is lost to both PowerVault 660F
controllers in an array, Array Manager doesn't give any
indication that it cannot communicate with the Array.
Solution: To determine if Array Manager lost communication with an
array, perform a PV660F Subsystem rescan. If communication is lost,
the PowerVault 660F array will be removed from the console.
------------------------------------------------------------------
Information in this document is subject to change without notice.
(c) 2003 Dell Computer Corporation. (c) 2003 VERITAS Software
Corporation. All rights reserved.
Reproduction in any manner whatsoever without the written
permission of Dell and VERITAS Software Corporation is strictly
forbidden.
Portions copyright (c) 1998 Chris Maunder.
Some cryptographic code in this product is derived from the
SSLeay library, copyright (c) 1995-97 by Eric Young
(eay@cryptsoft.com). All rights reserved.
Trademarks used in this text: Dell, Dell OpenManage, the DELL
logo, PowerEdge, and PowerVault are trademarks of Dell; Microsoft,
Windows, Windows NT, and Windows 2000 are registered trademarks
of Microsoft Corporation; Novell and NetWare are registered
trademarks of Novell, Inc. 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
and VERITAS Software Corporation disclaim any proprietary interest
in trademarks and trade names other than their own.
February, 2003
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.