Dell(TM) OpenManage(TM) Array Manager 3.3 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.3 software.
==================================================================
Dell OpenManage Array Manager 3.3
==================================================================
--------
Contents
--------
I. New Features in Array Manager 3.3
II. Beta Support on Microsoft Windows Advanced Server Limited Edition
III. Installation Requirements for Array Manager 3.3
IV. Backward Compatibility
V. Installing on Windows
VI. Installing on NetWare
VII. Warnings
VIII. Array Manager Directory Structure
IX. Required Driver/Firmware Revisions
X. Compatibility Issues
XI. Changes to the Documentation
XII. Fixed Issues
XIII. Known Issues
XIV. Viewing Traps With HP OpenView Network Node
Manager (NNM)
----------------------------------------------
I. NEW FEATURES IN ARRAY MANAGER 3.3
----------------------------------------------
Array Manager 3.3 provides the following enhancements:
* Support for the PERC 4/IM controller. The PERC 4/Im controller
enables you to create a virtual disk or integrated mirror from
hard disks. You can use this feature to mirror the data on your
boot drive in order to protect your system from down time and
data loss in the event of a boot drive failure.
* Support for the PERC 4/SC and PERC 4/DC controllers. These
controllers are high-performance intelligent PCI-to-SCSI host
adapters with RAID control capabilities.
* The PERC 2/Si, 3/Si, and 3/Di controllers have new options for
pausing and resuming a consistency check.
* You can now rename a virtual disk on the 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, and 3/Di controllers.
* Events 604 through 607 have been added. These events relate to the
pause and resumption of a consistency check and to splitting and
unmirroring redundant data. These events are documented in the online
help.
---------------------------------------------------------------------
II. BETA SUPPORT ON MICROSOFT WINDOWS ADVANCED SERVER LIMITED EDITION
---------------------------------------------------------------------
Array Manager 3.3 provides beta-level support for the Microsoft Windows
Advanced Server Limited Edition 64-bit operating system. This support
only includes the following:
* Management of the PERC 3/QC and PowerVault 660F controllers.
* Beta-level support for 64-bit applications.
In addition, when running Array Manager on a PowerEdge 7150 that is running
Microsoft Windows Advanced Server Limited Edition, you may experience problems
launching the Array Manager console. To resolve this problem, you should install
an udpate BEFORE installing Array Manager or any application that uses
ActiveX. The update is named Q305175_WxP_SP0_en_IA64.exe and is located on the
Microsoft Windows Advanced Server Limited Edition support CD provided with the
PowerEdge 7150 server.
Array Manager does NOT support Windows disk or volume management on the
Microsoft Windows Advanced Server Limited Edition 64-bit operating
system. Array Manager also does NOT support SNMP on the Microsoft
Windows Advanced Server Limited Edition 64-bit operating system.
Disclaimer: Since Array Manager only provides "beta level" support for
Microsoft Windows Advanced Server Limited Edition, issues may exist when
running Array Manager on the Microsoft Windows Advanced Server Limited
Edition operating system. Array Manager should not be used on Microsoft
Windows Advanced Server Limited Edition in a production environment or
any environment where reliability is necessary.
Note: Be aware that when remotely connecting to a Microsoft Windows
Advanced Server Limited Edition server, your administrator account on
the Microsoft Windows Advanced Server Limited Edition server is required
to have a password.
------------------------------------------------
III. 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.
* 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 5
or later.
- Windows NT 4 Terminal Server.
- Microsoft Small Business Server.
- Microsoft Windows 2000(R) 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.
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. 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 5 or later.
- Windows NT 4 Terminal Server.
- Microsoft Small Business Server.
- Windows 2000 Server with service pack 1 or later
- Windows 2000 Advanced Server with service pack 1 or later
- Microsoft DataCenter.
- Beta support for Microsoft Advanced Server Limited Edition.
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) 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.
** 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 4.2 with Support Pack 9 or later. When Using
NetWare 4.2, Array Manager also requires the Winsock 2 update which is
available from www.novell.com.
- Novell NetWare version 5.1 or later with Support Pack 4 or later.
- Novell NetWare version 6.0 with Support Pack 1 or later.
* 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.00 or later is required for launching and viewing
the online help from the Array Manager console.
---------------------------
IV. BACKWARD COMPATIBILITY
---------------------------
On a Windows system, Array Manager 2.5 or later can be upgraded to
version 3.3. 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.3.
On a NetWare system, you need to uninstall any existing versions of
Array Manager before installing Array Manager 3.3.
An Array Manager 3.3 console can connect to a version
2.5 managed system or later. However, using a version of the console
earlier than 3.3 to connect to a version 3.3 managed system is not
supported.
-------------------------
V. 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.
Use the following steps to install Array Manager on a Windows system.
1) Insert the Dell OpenManage Applications CD or the Array Manager 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) When finished, you can reboot and then begin using Array Manager.
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.)
---------------------------
VI. 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.3.
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\AM33\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:
For NetWare 4.2, enter:
install
For NetWare 5.x and NetWare 6, enter:
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.
---------------
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 /AM33 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.
----------------------------------------
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.
Controller Firmware Windows NT Windows 2000 NetWare
Driver Driver Driver
PERC 2/SC 3.13 2.32 2.68 NW 4.2 (2.06)
NW 5.x (2.06)
NW 6.1 (6.01r)
Note: NetWare is not
supported on PowerEdge
x300 systems with a
PERC 2/SC.
PERC 2/SC on a
PowerEdge 8450 3.13 4.15 2.68 NW 4.2 (3.12)
NW 5.x (6.01r)
NW 6.1 (6.01r)
PERC 2/DC on a
PowerEdge x300 1.06 2.32 2.68 NW 4.2 (2.06)
NW 5.x (2.06)
NW 6.1 (N/A)
PERC 2/DC on a
PowerEdge x400 1.06 4.15 2.68 NW 4.2 (3.12)
NW 5.x (6.01r)
NW 6.1 (6.01r)
PERC 3/SC 1.72 4.15 5.32 NW 4.2 (3.12)
NW 5.x (6.01r)
NW 6.1 (6.01r)
PERC 3/DC 1.72 4.15 5.32 NW 4.2 (3.12)
NW 5.x (6.01r)
NW 6.1 (6.01r)
PERC 3/DCL 1.72 4.15 5.32 NW 4.2 (3.12)
NW 5.x (6.01r)
NW 6.1 (6.01r)
PERC 3/QC 1.72 4.15 5.32 NW 4.2 (3.12)
NW 5.x (6.01r)
NW 6.1 (6.01r)
PERC 4/SC TM12 4.16 5.33 NW 4.2 (N/A)
NW 5.1 (6.01r)
NW 6.1 (6.01r)
PERC 4/DC TM12 4.16 5.33 NW 4.2 (N/A)
NW 5.1 (6.01r)
NW 6.1 (6.01r)
PERC 4/Di 2.01 4.15 5.32 NW 4.2 (N/A)
NW 5.x (6.01r)
NW 6.1 (6.01r)
PERC 4/IM 1.00.06.00 1.08.04 1.08.04 NW 4.2 (N/A)
NW 5.x (1.02.00.00)
NW 6.1 (1.02.00.00)
CERC
ATA 100/4CH 6.61 4.15 5.32 NW 4.2 (N/A)
NW 5.1 (6.01r)
NW 6.1 (6.01r)
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.3 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.
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.
Controller Firmware Windows NT Windows 2000 NetWare
Driver Driver Driver
PERC 2 3170 4944 4944 NW 4.2 (N/A)
NW 5.x (3564)
NW 6.1 (3564)
PERC 2/Si 3571 4944 4944 NW 4.2 (N/A)
NW 5.x (3564)
NW 6.1 (3564)
PERC 3/Si 3571 4944 4944 NW 4.2 (N/A)
NW 5.x (3564)
NW 6.1 (3564)
PERC 3/Di on a
PowerEdge 1650 3170 4944 4944 NW 4.2 (N/A)
NW 5.x (3564)
NW 6.1 (3564)
PERC 3/Di on a
PowerEdge 2500 3170 4944 4944 NW 4.2 (N/A)
NW 5.x (3564)
NW 6.1 (3564)
PERC 3/Di on a
PowerEdge 2550 3571 4944 4944 NW 4.2 (N/A)
NW 5.x (3564)
NW 6.1 (3564)
PERC 3/Di on a
PowerEdge 2650 3170 4944 4944 NW 4.2 (N/A)
NW 5.x (3564)
NW 6.1 (3564)
PERC 3/Di on a
PowerEdge 4400 3571 4944 4944 NW 4.2 (N/A)
NW 5.x (3564)
NW 6.1 (3564)
PERC 3/Di on a
PowerEdge 4600 3170 4944 4944 NW 4.2 (N/A)
NW 5.x (3564)
NW 6.1 (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.
Controller HBA Firmware 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
Note: The background initialization feature on PowerVault 660F controllers
is only available when using PowerVault 660F controller firmware
7.7 or later.
SAN Support for the PowerVault 660F
SAN 4.06 and 5.0 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.
*** Ultra SCSI controller Cards ***
These include Ultra SCSI, Ultra2 SCSI, Ultra160 SCSI, Ultra320 SCSI
Support for the Ultra SCSI controller cards is provided in the BIOS.
*** Required Drivers for the Microsoft Windows Advanced Server Limited Edition ***
Controller Driver for Beta Support
PERC 3/SC 6.26.25.32
PERC 3/DC 6.26.25.32
PERC 3/DCL 6.26.25.32
PERC 3/QC 6.26.25.32
PERC 4/SC 6.25
PERC 4/DC 6.25
PERC 4/Di 6.25.32
PERC 3/Di on a 4944
PowerEdge 2650
------------------------
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. CHANGES TO THE DOCUMENTATION
--------------------------------
The Array Manager online help has a chapter titled "Volume Management."
This chapter discusses dynamic volumes. Please note that dynamic volumes
are only supported on Windows operating systems.
------------------
XII. FIXED ISSUES
------------------
* Create Virtual Disk wizard in Custom Mode contains incorrect
menu option. (Issue 58175)
Problem: On a PERC 2/SC, 2/DC, 3/SC, 3/DCL, 3/DC, 3/QC, 4/SC, 4/DC,
4/Di, 4/IM,or CERC ATA100/4ch controller, you cannot create a RAID 10
virtual disk using array disks that already contain a virtual disk. When
using the Custom Mode of the Create Virtual Disk wizard, the Type
field may display RAID 10 as an option even though you have selected
array disks already containing a virtual disk. In this case, RAID 10
is not a valid option even though it is displayed in the Type field.
Solution: Dell has resolved this problem.
* Enable Alarm option incorrectly displays on PERC 4/Di menu.
(Issue 58008)
Problem: Even though the PERC 4/Di controller does not have an alarm,
if you right click the PERC 4/Di controller object in the Array
Manager tree view, an "Enable Alarm" option is displayed on the popup
menu. If you select the "Enable Alarm" option, you will receive
the following error message:
Failed to enable controller sound.
Solution: Dell has removed the Enable Alarm option from the 4/Di menu.
* EMM firmware updates may not be reflected on all systems in a cluster.
(Issue 45659)
Problem: When using Array Manager to update the EMM firmware on system 1
in a cluster, system 2 may not reflect the updated firmware.
Solution: Dell has resolved this problem.
* A NetWare server abends when performing an "Add Member" or
"Transform Type" function with PERC 2/SC, PERC 3/SC, PERC 2/DC, or
PERC 3/QC RAID controllers.
Problem : Performing either an Add Member or Transform Type
function with a virtual disk that is less than 1 GB in size may
abend the NetWare server containing the virtual disk.
Solution: This function is unstable with virtual disks less than
1 GB for NetWare. Refrain from using these functions with virtual
disks unless they are 1 GB or greater in size.
* May not receive Array Manager SNMP traps from Windows NT 4.0 systems
(Issue 58350)
Problem: If the Windows NT 4.0 application event log is full, then Array
Manager traps may not be forwarded if you are using SNMP to monitor the
Windows NT 4.0 system. In this case, Windows NT 4.0 may or may not display
in the application event log those Array Manager events that are not being
forwarded as SNMP traps due to the application event log being full.
Solution: For an immediate solution, clear the Windows NT 4.0 application
event log. Dell is working to resolve this problem in a future release of
Array Manager.
------------------
XIII. 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 **
* 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 is working to resolve 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: Click on the specified controller to highlight the controller.
Dell is working to resolve 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 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 64.
(Issue 40482)
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 64. 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.
* Cannot initialize or delete a virtual disk containing a boot partition on
Microsoft Windows Advanced Server Limited Edition. (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 Microsoft Windows Advanced
Server Limited Edition.
Solution: Format the array disks included in the virtual disk
with the PERC BIOS Configuration Utility which can be launched
during the BIOS initialization.
* 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: Log in as Administrator and run the installation
again.
* The "Split Mirror" and "Restore Dead Disk Segment" operations are
missing on NetWare.
Problem: The "Split Mirror" and "Restore Dead Disk Segment"
Operations are not available when managing a NetWare server.
Solution: This is working as designed; these options are only
available on Windows NT and Windows 2000.
* 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.
* NetWare 4.2 is missing various NetWare Loadable Modules
(NLMs) required by Array Manager.
Problem: When attempting to start Array Manager on NetWare 4.2,
the console may report that a number of NLMs are not loaded
(such as ws2_32.nlm).
Solution: On NetWare 4.x, Array Manager requires the WinSock 2
update. You can download the Winsock 2 update from the Novell
Website at www.novell.com. To locate the Winsock 2 update on
the Novell website using the website's search function, it
may be useful to search for the string "Array Manager" or
"nw4wsock.exe". The Novell web page contains instructions for
downloading and installing the update.
* Array Manager does not protect a system disk from deletion in
NetWare. (Issue 59447)
Problem: Depending on the RAID controller, there are various
methods to completely remove the RAID configuration from your
controller. The Windows NT version of Array Manager does not allow
you to delete any virtual disk that contains a system volume.
However, the NetWare version of Array Manager does not protect you
from deleting these virtual disks.
Solution: There is no solution to this problem at this time. You
should be very careful when deleting virtual disks or performing an
operation that removes all of the virtual disks from a controller;
make sure you know what data is on any volumes created on them.
* A drive letter is unavailable for use.
Problem: After deleting a basic disk, the drive letter used by that
disk is no longer available.
Solution: Reboot the server to make the drive letter available.
* Performing a virtual disk initialization causes a foreign Windows
NT or Windows 2000 disk to show up under the "Disks" folder.
Problem: Performing an initialization (a destructive operation) on
a virtual disk containing a dynamic disk changes the status of the
dynamic disk to foreign and/or offline. Performing an
initialization on a virtual disk may also create a new Windows NT
or Windows 2000 "missing" disk.
Solution: To reuse a Windows NT or Windows 2000 disk that is set to
foreign or offline, perform either a "Merge Foreign Disk..." or a
"Revert to Basic Disk..." operation. If the disk is set as a
missing disk, you can perform a "Remove Disk" operation to remove
it. As the warning message for virtual disk initialization
indicates, performing a virtual disk initialization destroys the
data on the virtual disk.
* Unable to connect to a NetWare server with the Array Manager
console.
Problem: When trying to connect to a NetWare server by using the
server name with the Array Manager console, a "The Connection Failed"
message appears.
Solution: There can be a variety of reasons for why the connection
between the console and the NetWare managed system fails. To
identify why the connection failed, perform the following steps:
1) Ping the NetWare server from the system running the Array
Manager console. If this fails, then you are experiencing
network problems.
2) Verify that the correct NDS tree, user ID, and password are
correct for the target NetWare server. Also verify that the
user ID has supervisor rights.
3) Verify that the server name is included in some form of DNS
(DNS server, hosts file, and so forth).
4) Verify that the server name does not start with a number.
This can cause problems with DNS.
5) Restart the console if an entry for the NetWare server was
just added to the hosts file.
RECOMMENDATION: You may be able to avoid this connection problem
by using the NetWare server's IP address instead of the server
name when attempting the connection.
** PROBLEMS ASSOCIATED WITH THE PERC CONTROLLERS **
* 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: If you break and then recreate the mirror, the disk will
be displayed in Array Manager. You can break the mirror using the PERC
4/IM BIOS. Dell is working to resolve 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 is working to resolve this problem.
* A "dedicated" hot spare may be assigned to more than one virtual
virtual disk on PERC 2, 2/Si, 3/Si, and 3/Di controllers. (Issue 62041)
Problem: The term "dedicated hot spare" generally implies that a
hot spare is assigned to only one virtual disk. In the case of the
PERC 2, 2/Si, 3/Si, and 3/Di controllers, however, hot spares created
with the "Configure Dedicated Hot Spare" function may also be assigned
to more than one virtual disk. In this case, if the hot spare is rebuilt
because one of the virtual disks failed, then the remaining virtual disks
may no longer be assigned a hot spare.
Solution: When creating hot spares on the PERC 2, 2/Si, 3/Si, and 3/Di
controllers, be aware that Array Manager allows you to assign the same
array disk to more than one virtual disk. Before making an assignment,
you may wish to verify that the array disk is not already assigned as a
hot spare. Dell is working to resolve this problem in a future release.
* Prepare to Remove command requires manual removal of disk on
PERC 4/Di controllers. (Issue 56942)
Problem: When you do a Prepare to Remove command on an array
disk attached to a PERC 4/Di controller, you must do the
following actions before the array disk is redisplayed in the
Array Manager tree view:
1. Manually remove and then replace the array disk.
2. Either do a Rescan or reboot the system.
Doing a Rescan or rebooting the system without first manually
removing and replacing the disk will not cause the disk to
be displayed in the tree view.
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. (Issue 45290)
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.
* PercRAID.Log Events in the Windows NT Event Log
Problem: The PERC console (a legacy Dell RAID configuration
utility) installs a service called PercRAID which monitors the
status of PERC 2/SC and 2/DC RAID controllers. When unassigning
a hot spare from within the Array Manager console, the PercRAID
service logs an event to the system log warning you that a
disk has failed.
Solution: This error message is incorrect; the disk is ready for
use immediately after unassigning it.
* Drive mapping may not work properly on Windows NT and Windows 2000
systems with PERC 3/DC, PERC 3/DCL, PERC 3/QC, PERC 2/DC, PERC 3/SC,
PERC 2/SC, PERC 4/SC, PERC 4/DC, PERC 4/Di, PERC 4/IM, and
CERC ATA100/4ch controllers.
Problem: After creating a virtual disk, the disk may not be visible
in the disk folder until the system is rebooted. After rebooting
the system, the mapping between the newly created disk and the
corresponding Windows NT or Windows 2000 disk may not be displayed
in the Array Manager console.
Solution for Windows NT: After creating a virtual disk and
rebooting the system, do a console rescan by either clicking
the "Rescan" button or selecting "View"--> "Rescan".
Solution for Windows 2000: When using a PERC 2/SC or 2/DC
controller, upgrade your driver to MRAID 35X.SYS version 2.68 or later.
* After creating a virtual disk with a PERC 2/SC, PERC 3/SC, 2/DC, 3/DCL,
3/DC, 3/QC, 4/SC, 4/DC, 4/Di, 4/IM, or CERC ATA100/4ch controller, the
virtual disk does not appear under the Disks storage object.
Problem: If there are no virtual disks configured at boot time on
a PERC 2/SC, 3/SC, 2/DC, 3/DCL, 3/DC, 3/QC, 4/SC, 4/DC, 4/Di, 4/IM, or
CERC ATA100/4ch controller on Windows 2000, the Windows disk driver
may not be loaded.
Solution: Either reboot the system after creating the first
virtual disk or create the first virtual disk in the BIOS. Use the
Ctrl-m key combination to invoke the BIOS utility.
OR
When using a PERC 2/SC or 2/DC controller, upgrade your driver to
MRAID 35X.SYS version 2.68 or later.
** 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: Dell is working to resolve this problem.
* PV660F Enclosure Asset setting are not being saved. (Issue 43987)
Problem: After adding an enclosure to a subsystem and then setting the
Asset Tag a rescan will not show the Asset tag.
Solution: To set Enclosure Asset Tag first do a controller reset and
then change the Asset Tag and they will be saved.
* PV660F Firmware Mismatch appears after a successfule SES download
(Issue 45103)
Problem: After a successful download of SES firmware a warning appears
that the firmware is mismatched.
Solution: Perform a rescan on the PV660F subsystem and the warning
will disappear.
* A Microsoft Disk Removed dialog pops up on a Windows 2000 server
under the following conditions: 1) In a storage area network (SAN)
hardware configuration, you do a console rescan when assigning
virtual disk 0 of a PowerVault 660F array to the server, or 2) You
create virtual disk 0 in a direct-attached hardware configuration.
Problem: When assigning virtual disk 0 (LUN 0) to a Windows 2000
server, a Windows 2000 "Unsafe Removal of Device" message is
displayed for the DELL PV660F PSEUDO SCSI Disk Device.
Solution: Disregard the Windows 2000 message. This is caused by
the Dell PowerVault 660F Pseudo Disk (used to manage the Fibre
Channel array when no virtual disks are assigned) being replaced by
the newly assigned virtual disk. This is normal and has no harmful
effect to your Windows 2000 server.
* After performing a Make Offline and Prepare to Remove operation on
a PowerVault 660F array disk that is part of a disk group
containing redundant virtual disks, performing a Rebuild operation
on the array disk fails. This only happens when hot spares are
not defined.
Problem: After doing a Prepare to Remove operation on an array disk
of a PowerVault 660F array, it cannot be used to rebuild.
Solution: Remove and reinsert the array disk. This automatically
starts a rebuild.
* 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: Dell is investigating this problem. 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.
* HBA to switch cable failure on one server in a SAN fabric causes
Application Transparent Failover to autofail all LUNS that belong to other
servers. (Issue 38505)
Problem: Starting the Array Manager service or doing a rescan when the Qlogic
HBA to switch cable failure occurs on one of the servers in a SAN fabric
causes the Dell OpenManage Application Transparent Failover to autofail all
LUNS on the PowerVault 650F that are assigned to other servers.
Solution: Disable PowerVault 660F management on the server with HBA failure
and enable PowerVault 660F management on another server in the SAN until the
cable failure is resolved
* No objects appear under Physical Array and Logical Array under the
PV660F Subsystem.
Problem: It is possible that the Fibre Channel array might not
discover some of the PowerVault 660F Fibre Channel arrays if any
of the controllers are not fully (re)booted.
Solution: Right-click "PV660F SubSystem" and select "Rescan".
--------------------------------------------------------------
XIV. VIEWING TRAPS WITH HP OpenView NETWORK NODE MANAGER (NNM)
--------------------------------------------------------------
The "arymgr.cfg" and "arymgr.mib" files are in the Management
Information Base (MIB) directory of your installation directory.
To view trap events with strings inserted, perform the following
steps:
1. Load the Dell Array Manager MIB "arymgr.mib" into the HP OpenView
NNM.
2. Select "OK" When prompted to "Load a TRAP-TYPE/NOTIFICATION-TYPE
macro." The system loads all of the trap definitions into HP Openview.
For more information on loading MIBs into HP OpenView, see the
HP OpenView documentation.
------------------------------------------------------------------
Information in this document is subject to change without notice.
(c) 2001 Dell Computer Corporation. (c) 2001 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.
August, 2002
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.