######################################################################
DELL OPENMANAGE(TM) Array Manager, VERSION 3.5 README
######################################################################
======================================================================
Criticality
======================================================================
2 - Recommended
======================================================================
Title and Description
======================================================================
Array Manager is designed for system administrators who implement
hardware and software RAID solutions and understand corporate and small
business storage environments.
Array Manager enables you to configure the storage components attached
to your system. These components include RAID and non-RAID controllers
and the channels, enclosures, and disks attached to them. Using Array
Manager, you can implement controller functions without requiring access
to the BIOS.
This readme file contains updated information for Array Manager Version
3.5.
Always see the Dell support Website at support.dell.com for the most
current information.
######################################################################
README TABLE OF CONTENTS
######################################################################
COMPATIBILITY/RECOMMENDED REQUIREMENTS
WARNINGS
WHAT IS NEW IN THIS RELEASE?
WHAT IS FIXED IN THIS RELEASE?
INSTALLING ARRAY MANAGER VERSION 3.5
KNOWN LIMITATIONS
######################################################################
COMPATIBILITY/RECOMMENDED REQUIREMENTS
######################################################################
The following subsections provide compatibility and system requirements
information:
BACKWARD COMPATIBILITY WITH OLDER VERSIONS OF ARRAY MANAGER
COMPATIBILITY WITH THE ASPI 4.7.X DRIVER
OTHER COMPATIBILITY ISSUES
GENERAL SYSTEM REQUIREMENTS
MANAGEMENT CONSOLE REQUIREMENTS (CLIENT)
MANAGED SYSTEM FOR WINDOWS REQUIREMENTS (SERVER)
MANAGED SYSTEM FOR NETWARE REQUIREMENTS (SERVER)
ONLINE HELP REQUIREMENTS
REQUIRED DRIVER/FIRMWARE REVISIONS
REQUIREMENTS FOR AUTOMATIC FIRMWARE AND DRIVER UPDATES
======================================================================
BACKWARD COMPATIBILITY WITH OLDER VERSIONS OF ARRAY MANAGER
======================================================================
On a Windows system, Array Manager 2.5 or later can be upgraded to
version 3.5. 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.5.
On a NetWare system, you need to uninstall any version of Array Manager
previous to 3.5 before installing Array Manager 3.5.
An Array Manager 3.5 console can connect to a version 2.5 managed system
or later. However, using a version of the console earlier than 3.5 to
connect to a version 3.5 managed system is not supported.
======================================================================
COMPATIBILITY WITH THE ASPI 4.7.X DRIVER
======================================================================
Array Manager cannot be installed on a system that has the ASPI 4.7.x
driver installed. If you have the ASPI 4.7.x driver installed on your
system, you need to remove this driver and install the ASPI 4.6 driver.
You can do this by downloading the ASPI 4.6 package from
http://support.dell.com. The ASPI 4.6 package uninstalls the ASPI 4.7.x
driver and installs the ASPI 4.6 driver. Refer to the documentation of
any other applications installed on the system to see if those applications
have known problems with the ASPI 4.6 driver.
======================================================================
OTHER 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.
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.
If you make configuration changes on NetWare 6.5 after installing
Array Manager, the HDETECT utility may reactivate the QLCSFTE.CDM
or the DellSEP.CDM drivers by removing the ";(Commented out by install...)"
designation within the STARTUP.NCF file. Once the QLCSFTE.CDM
and DellSEP.CDM drivers are reactivated, Array Manager is disabled.
The solution to this problem is to reinstall Array Manager. Examples
of configuration changes that will cause this problem are installing
a new RAID or NIC card or installing NWASPI.CDM.
* 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 and Windows Server 2003:
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.
======================================================================
GENERAL SYSTEM 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. Use the Windows server
installation media to install Internet Information Services. 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 supported 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.
- Windows NT 4 Terminal Server.
- Microsoft Small Business Server.
- Microsoft Windows 2000 Server with service pack 3 or later.
- Microsoft Windows 2000 Advanced Server with service pack 3 or later.
- Microsoft Windows 2000 Professional with service pack 3 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.9 or later if you intend
to map a drive to a NetWare system and copy the Array Manager install media
from the Windows system to the NetWare system. The Novell Client is also
required if you wish to use the Array Manager Utilities to modify a
NetWare server configuration.
* (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.
- Windows NT 4 Terminal Server.
- Microsoft Small Business Server.
- Microsoft Windows 2000 Server with service pack 3 or later
- Microsoft Windows 2000 Advanced Server with service pack 3 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) On Windows NT and NetWare, 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 without the
risk of data loss.
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 6 or later.
- Novell NetWare version 6.0 with Support Pack 3 or 6.5 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.)
Note: If you have a NetWare 6.0 system and are planning to install Support
Pack 3, you should install Support Pack 3 before installing Array
Manager.
* 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.9 or later installed on a
remote Windows system if you intend to 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) On Windows NT and NetWare, 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 without the risk of data loss.
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. In addition to
the online help, the Array Manager installation directory includes
documentation in html and PDF format. The total space requirement for
the online help and documentation is 15 MB.
======================================================================
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,
CERC ATA100/4ch, LSI 1020, and LSI 1030.
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.35.2.32 NW 5.1 (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.21 2.68 6.35.2.32 NW 5.1 (6.02)
PowerEdge 8450 NW 6.x (6.02)
PERC 2/DC on a 1.06 2.32 2.68 6.35.2.32 NW 5.1 (2.06)
PowerEdge x300 NW 6.x (N/A)
PERC 2/DC on a 1.06 4.21 2.68 6.35.2.32 NW 5.1 (6.02)
PowerEdge x400 NW 6.x (6.02)
PERC 3/SC 1.96T 4.21 5.46 6.41.2.32 NW 5.1 (7.01v)
NW 6.x (7.01v)
PERC 3/DC 1.96T 4.21 5.46 6.41.2.32 NW 5.1 (7.01v)
NW 6.x (7.01v)
PERC 3/DCL 1.96T 4.21 5.46 6.41.2.32 NW 5.1 (7.01v)
NW 6.x (7.01v)
PERC 3/QC 1.96T 4.21 5.46 6.41.2.32 NW 5.1 (7.01v)
NW 6.x (7.01v)
PERC 4/SC 3.41 4.21 5.46 6.41.2.32 NW 5.1 (7.01v)
NW 6.x (7.01v)
PERC 4/DC 3.41 4.21 5.46 6.41.2.32 NW 5.1 (7.01v)
NW 6.x (7.01v)
PERC 4/Di on a 2.48 4.21 5.46 6.41.2.32 NW 5.1 (7.01v)
PowerEdge 2600 NW 6.x (7.01v)
PERC 4/Di on a 4.12W N/A 5.46 6.41.2.32 NW 5.1 (7.01v)
PowerEdge 1750 NW 6.x (7.01v)
PERC 4/IM on a 1.00.12.00 N/A 1.08.06 1.08.18 NW 5.1 (N/A)
PowerEdge (Native) NW 6.x (N/A)
1655MC
CERC 6.62 4.18 5.46 6.41.2.32 NW 5.1 (7.01v)
ATA 100/4CH NW 6.x (7.01v)
LSI 1020 1.03.04.00 N/A 1.08.19 1.08.18 NW 5.x (N/A)
(Native) NW 6.x (3.03)
LSI 1030 on a 1.01.61.00 1.08.04 1.08.19 1.08.18 NW 5.x (N/A)
PowerEdge (Native) NW 6.x (3.03)
2600
LSI 1030 on a 1.01.61.00 N/A 1.08.19 1.08.18 NW 5.x (N/A)
PowerEdge (Native) NW 6.x (3.03)
1750
Note: When installing on NetWare, the Array Manager installation
may display an abbreviated name for the required NetWare
driver. Only the numerical portion of the driver name may be
displayed. The letter portion of the driver name (if any) may
not be displayed. For example, if the driver name is "123A",
then only the "123" portion of the name may be displayed.
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.5 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, PERC 3/Di, and CERC SATA1.5/6ch.
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.8 are not supported. The
minimum requirement of 2.8 applies to all of the PERC 2, PERC 2/Si, PERC 3/Si,
PERC 3/Di, and CERC SATA1.5/6ch 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, PERC 3/Di, and CERC SATA1.5/6ch 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 6077 6075 6076 6076 NW 5.x (6075)
NW 6.x (6075)
PERC 2/Si 6077 6075 6076 6076 NW 5.x (6075)
NW 6.x (6075)
PERC 3/Si 6077 6075 6076 6076 NW 5.x (6075)
NW 6.x (6075)
PERC 3/Di on a 6077 6075 6076 6076 NW 5.x (6075)
PowerEdge 1650 NW 6.x (6075)
PERC 3/Di on a 6077 6075 6076 6076 NW 5.x (6075)
PowerEdge 2500 NW 6.x (6075)
PERC 3/Di on a 6077 6075 6076 6076 NW 5.x (6075)
PowerEdge 2550 NW 6.x (6075)
PERC 3/Di on a 6077 6075 6076 6076 NW 5.x (6075)
PowerEdge 2650 NW 6.x (6075)
PERC 3/Di on a 6077 6075 6076 6076 NW 5.x (6075)
PowerEdge 4400 NW 6.x (6075)
PERC 3/Di on a 6077 6075 6076 6076 NW 5.x (6075)
PowerEdge 4600 NW 6.x (6075)
CERC 7015 N/A 7010 7010 NW 5.x (7017)
SATA1.5/6ch NW 6.x (7017)
*** 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.
======================================================================
REQUIREMENTS FOR AUTOMATIC FIRMWARE AND DRIVER UPDATES
======================================================================
When installing Array Manager on Windows 2000 or Windows Server 2003,
the installation process may be able to update firmware and drivers that
do not meet the minimum requirements for the current version of Array
Manager. The installation process assesses whether or not the currently
installed firmware and drivers meet the requirements for the current
version of Array Manager. If they do not, the installation process
displays a prompt to confirm automatic update of the required firmware
and drivers.
*** Minimum Firmware and Driver Prerequisites for Automatic Updates ***
In order for an automatic update to be possible, there must be a minimum
prerequisite level of firmware and drivers already on the system. The
following table describes these prerequisite levels.
Note: 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.
Controller Windows 2000 Windows Server 2003
CERC ATA 100/4ch Firmware: None None
Driver: 5.35.2 N/A
PERC 4/DC Firmware: None None
Driver: 5.35.2 N/A
PERC 4/Di Firmware: None None
Driver: 5.35.2 N/A
PERC 4/SC Firmware: None None
Driver: 5.35.2 N/A
PERC 2 Firmware: 2.6 2.6
Driver: 2.6 N/A
PERC 2/Si Firmware: 2.6 2.6
Driver: 2.6 N/A
PERC 3/DC Firmware: 1.57 1.57
Driver: 5.35.2 N/A
PERC 3/DCL Firmware: 1.57 1.57
Driver: 5.35.2 N/A
PERC 3/Di Firmware: 2.6 2.6
Driver: 2.6 N/A
PERC 3/QC Firmware: 1.57 1.57
Driver: 5.35.2 N/A
PERC 3/SC Firmware: 1.63 1.63
Driver: 5.35.2 N/A
PERC 3/Si Firmware: 2.6 2.6
Driver: 2.6 N/A
*** BIOS Prerequisites for Automatic Firmware and Driver Updates ***
On certain systems, a minimum BIOS level is required for automatic
firmware and driver updates. The following table describes these
prerequisite levels. There are no BIOS prerequisites for systems not
listed in the following table.
System Prerequisite BIOS
PowerEdge 1650 A05
PowerEdge 4600 A08
PowerEdge 2550 A06
*** Conditions that Prevent Automatic Firmware and Driver Updates ***
Automatic firmware and driver update during installation is not
possible in the following circumstances:
* The system does not have the minimum prerequisite level of firmware
and drivers required for automatic update. To resolve this situation,
download the current firmware and driver from http://support.dell.com.
* An incompatible firmware or driver version already resides on the system.
For example, the operating system may install native firmware and drivers
that are incompatible or too old to be supported by the Array Manager
automatic update feature. The outcome of this situation depends on how
you are installing Array Manager.
- If you are installing from the Array Manager CD, the incompatible firmware
or driver displays a Warning status. The Array Manager installation can
continue to completion although the automatic firmware update feature is
disabled. To update the firmware and drivers in this situation, download
the current versions from http://support.dell.com.
- If you are installing from the Dell OpenManage Applications CD, then
installation of Array Manager is not possible. In this case, continue with
the installation of the other applications. You can then download and
install the current versions of the firmware and drivers from
http://support.dell.com and then install Array Manager.
* On the PERC 3/SC, 3/DCL, 3/DC, 3/QC, 4/SC, 4/DC, 4/Di, and CERC ATA100/4ch
controllers, firmware and drivers cannot be updated while the controller is
processing the following operations:
- Background initialization
- Consistency check
- Rebuild
- Virtual disk reconfiguration (changing RAID levels or adding new disks to a
virtual disk)
In this situation, you can wait until the controller has completed processing
these operations and then either reinstall Array Manager or download the current
firmware and drivers from http://support.dell.com.
Once Array Manager is installed, you can launch the Array Manager Utilities to verify
which firmware and drivers are installed on the system. Any firmware or driver that
has a Warning status is not supported.
Note: Automatic update of firmware and drivers is not supported on PERC 2/SC, 2/DC,
4/IM, and CERC SATA1.5/6ch controllers.
######################################################################
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.
* You should uninstall Array Manager before upgrading the Windows
operating system. After upgrading Windows, reinstall Array
Manager using the Array Manager install media or by downloading
Array Manager from the Dell Website at support.dell.com.
If you notice changes in the drive letters after uninstalling
Array Manager and then upgrading Windows, refer to the Dell
Knowledge Base item 832097 for information on resolving this situation.
######################################################################
WHAT IS NEW IN THIS RELEASE?
######################################################################
Added or Changed Features:
* Array Manager 3.5 has added support for the CERC SATA1.5/6ch controller.
* In addition to the PERC 3/DC controller, the PERC 4/DC controller
supports clustered configurations in Array Manager 3.5.
* The Array Manager 3.5 installation provides automatic update of firmware
and drivers on supported controllers. These controllers must already
have firmware and drivers installed that meet minimum requirements.
* Background initialization of virtual disks is supported for the PERC
3/SC, 3/DCL, 3/DC, 3/QC, 4/SC, 4/DC, 4/Di, and CERC ATA100/4ch
controllers.
* The export log file function is now supported on additional controllers.
The following controllers support this feature: PERC 2/SC, 2/DC, 3/SC,
3/DCL, 3/DC, 3/QC, 4/SC, 4/DC, 4/Di, PERC 4/IM, CERC ATA100/4ch, PERC 2,
2/Si, 3/Si, 3/Di, and CERC SATA1.5/6ch.
* The status for array disks that have received a SMART alert has changed.
In past releases of Array Manager, the status for a disk with a SMART
alert was "Degraded." In Array Manager 3.5, the status is "Warning."
The Warning status indicates that the disk should be replaced immediately.
The Degraded status could be interpreted to mean that the virtual disk
has lost redundancy, which is incorrect.
Removed Features:
* The Pause I/O pop-up menu command for PERC 2, 2/Si, 3/Si,
and 3/Di controllers has been removed.
* The Format pop-up menu command for array disks has been
removed.
######################################################################
WHAT IS FIXED IN THIS RELEASE?
######################################################################
The following issues are corrected in Array Manager Version 3.5:
* Firmware download may not work on the PERC 2, 2/Si, 3/Si, and 3/Di
controllers on Windows and NetWare. Firmware download may not work on
the Ultra SCSI, Ultra2 SCSI, Ultra160 SCSI, LSI 1020, and LSI 1030
controllers on NetWare.
* Create Volume and Upgrade Disk buttons are enabled on Windows Server 2003.
* Basic disks may disappear under the Disks object in the tree view
when initializing a virtual disk.
* DCOM (Distributed Component Object Model)
* Battery fields display "Unknown" in log file.
* Array Manager does not update the Disk View tab at startup on
a PERC 3/DC controller.
* Attempts to split a mirror or unmirror a virtual disk
may fail.
* Formatting a virtual disk may destroy drive mapping.
* Create virtual disk may fail on PERC 3/Di controllers.
* Attempts to delete a dynamic virtual disk may fail.
* Cannot expand a concatenated virtual disk that fully utilizes
an array disk.
######################################################################
INSTALLING ARRAY MANAGER VERSION 3.5
######################################################################
The following subsections describe Array Manager installation:
INSTALLING ON WINDOWS
INSTALLING ON NETWARE
REMOTE INSTALLATION ON WINDOWS SERVER 2003
ARRAY MANAGER DIRECTORY STRUCTURE
======================================================================
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 am35 directory which is located in the Dell OpenManage Systems
Management CD’s root directory.
3. Double-click the Setup icon located in the am35 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.)
======================================================================
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.
Note: If you have a NetWare 6.0 system and are planning to install
Support Pack 3, you should install Support Pack 3 before installing
Array Manager.
1) If a version of Array Manager previous to 3.5 is already installed on
the NetWare system, then uninstall that version before installing the
current version of Array Manager.
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\AM35\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 "OTHER COMPATIBILITY ISSUES" section of this readme file.
======================================================================
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.
======================================================================
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 /AM35 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.
######################################################################
KNOWN LIMITATIONS
######################################################################
The following sections describe known problems associated with Array
Manager or the supported controllers. Dell is in the process of resolving
these problems.
GENERAL PROBLEMS
PROBLEMS ASSOCIATED WITH THE PERC AND CERC CONTROLLERS
PROBLEMS ASSOCIATED WITH THE POWERVAULT 660F AND 650F CONTROLLERS
======================================================================
GENERAL PROBLEMS
======================================================================
* Drive may continue to receive SMART alerts even after being replaced.
Problem: If you replace a drive in slot 8 or greater that is receiving
SMART alerts, the new drive may continue to receive SMART alerts and
generate events.
Solution: Reboot the system.
* Detaching the enclosure cable during a rebuild causes the
controller to enter an inoperable state.
Problem: If the cable to the enclosure becomes detached while
a rebuild is in progress, the controller enters an inoperable
state and reports the "controller is busy" status.
Solution: The best solution to this problem is to avoid detaching
the enclosure cable during a rebuild. If the cable does become
detached, however, and the controller enters an inoperable state,
reboot the system to resolve this problem.
* Custom Mode of the Extend Volume wizard displays incorrect disk usage.
Problem: When extending a volume using the Custom Mode of the Extend
volume wizard, the amount of space to be used on each disk that is
displayed by the wizard does not match the actual disk usage once the
volume is extended.
Solution: Dell is working to resolve this problem.
* Enabling the PowerVault 660 provider when the PowerVault 660
controller is not present may abend a NetWare 6.5 system.
Problem: If you enable the PowerVault 660 provider on a NetWare 6.5
system when the PowerVault 660 controller is not present and then
attempt to uninstall Array Manager, the NetWare 6.5 system abends.
In this situation, the system may generate the following error
messages:
'Abend on P00:Page Fault Processor Exception (Error code 00000000.
Running Process: VXSVC_ _P 6 Process'
'Abend on P00: Invalid object handle passed to routine kSemaphoreFree.
Running Process: NLSLRUP Register Process'
Solution: Dell is working to resolve this problem.
* Remote connection fails on servers with multiple NIC teams.
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.
* Array Manager installation process does not display the status of
required firmware for a PERC 3/QC controller on Windows Server 2003 (64 bit).
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.
======================================================================
PROBLEMS ASSOCIATED WITH THE PERC AND CERC CONTROLLERS
======================================================================
* Install process prompts for 4.21 driver when using a CERC ATA 100/4ch
controller on Windows NT.
Problem: If you have a CERC ATA 100/4ch controller and are installing
Array Manager on Windows NT, the install process may ask for the 4.21
driver even though the 4.18 driver is the minimum requirement.
Solution: Click Next to continue the installation. The install process
can complete successfully as long as the 4.18 minimum requirement for
Windows NT is met.
* Export Log File command does not work on NetWare with the CERC ATA 100/4ch
controller.
Problem: When using a CERC ATA 100/4ch controller with NetWare, the Export
Log file command may not work.
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
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) 2004 Dell Inc. (c) 2004 VERITAS Software Corporation. All rights
reserved.
Reproduction in any manner whatsoever without the written permission
of Dell Inc. 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 Inc.; "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 Inc. and VERITAS Software Corporation disclaim any proprietary
interest in trademarks and trade names other than their own.
February, 2004
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.