Dell(TM) OpenManage(TM) Array Manager 3.1 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 Web site at http://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.1 software.
==================================================================
Dell OpenManage Array Manager 3.1
==================================================================
--------
Contents
--------
I. New Features in Array Manager 3.1
II. Beta Support on Microsoft Windows Advanced Server Limited Edition
III. Installation Requirements for Array Manager 3.1
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. Fixed Issues in Array Manager 3.1
XII. Known Issues
XIII. Viewing Traps With HP OpenView Network Node
Manager Special Edition (NNM SE)
-------------------------------------
I. NEW FEATURES IN ARRAY MANAGER 3.1
-------------------------------------
* Dedicated hot spares are now supported on NetWare.
* Array Manager now supports the PERC 3/SC controller.
* Enclosure management on the PERC 2/SC, 2/DC, 3/SC,
3/DCL, 3/DC, 3/QC and PERC 2, 2/Si, 3/Si, and 3/Di
controllers is now supported by Array Manager for the
following enclosures:
Dell PowerVault 200S
Dell PowerVault 201S
Dell PowerVault 210S
Dell PowerVault 211S
Dell PowerVault 220S
Dell PowerVault 221S
This support is in addition to the enclosure management
support already provided by the PowerVault 660F for the
Dell PowerVault 224F enclosure.
* The Array Manager online help has been enhanced to include
the SCSI and fibre channel events displayed in the Array
Manager event log.
* The utilities previously referred to as the Array Manager
Service Manager have been renamed to the Array Manager
Utilities. The executable for the Array Manager Utilities
is named amutils.exe.
* The PERC 2, 2/Si, 3/Si, and 3/Di controllers now support a
"Prepare to Remove" function which enables you to prepare
a disk so that it can be removed safely.
* The PERC 2/SC, 2/DC, 3/SC, 3/DCL, 3/DC, 3/QC controllers and
the PERC 2, 2/Si, 3/Si, and 3/Di controllers now allow you to
locate the array disks included in a virtual disk by blinking
the light-emitting diodes (LEDs) on the array disks.
---------------------------------------------------------------------
II. BETA SUPPORT ON MICROSOFT WINDOWS ADVANCED SERVER LIMITED EDITION
---------------------------------------------------------------------
Array Manager 3.1 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.
------------------------------------------------
III. INSTALLATION REQUIREMENTS FOR ARRAY MANAGER
------------------------------------------------
The following sections describe the Array Manager installation
requirements:
General Requirements
Management Console Requirements (Client)
Managed Node for Windows Requirements (Server)
Managed Node 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 node (server):
* 64 megabytes (MB) of RAM.
* Administrator access to the system.
* For information on supported operating systems for the Array Manager
console and managed node, see the following sections:
- Management Console Requirements (Client)
- Managed Node for Windows Requirements (Server)
- Managed Node for NetWare Requirements (Server)
* Transmission Control Protocol/Internet Protocol (TCP/IP) connection
on the console and server when attempting remote node 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: 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 and PERC 2, 2/Si, 3/Si, and 3/Di controllers on platforms not
currently supported by Array Manager. These utilities are available at
http://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.
* Microsoft Windows NT® 4.0 with Service Pack 5 or later OR Microsoft
Windows 2000® with Service Pack 1 or later. 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 node 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 NT version 4.6 or later when
installing NetWare remotely from a Windows system.
* (Optional). Microsoft Internet Explorer Version 4.0 or later for
viewing the online help and the browser plug-in.
** MANAGED NODE FOR WINDOWS REQUIREMENTS (SERVER) **
The following are minimum requirements for installing a managed node for
Windows.
* A server running Microsoft Windows NT version 4.0 with Service Pack 5 or
later OR Microsoft Windows 2000 with Service Pack 1 or later. 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 http://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.
* One of the following redundant array of independent disks (RAID) controllers
for array management:
- Dell PowerEdge(TM) Expandable RAID Controller 2 (PERC 2)
- PERC 2/Single Channel (SC)
- PERC 3/Single Channel (SC)
- PERC 2/Dual Channel (DC)
- PERC 2/Single Channel Integrated (Si)
- PERC 3/Single Channel Integrated (Si)
- PERC 3/Dual Channel Integrated (Di)
- PERC 3/Dual Channel (DC)
- PERC 3/Quad Channel (QC)
- PERC 3/Dual Channel Lite (DCL)
- PowerVault(TM) 660F Fibre Channel RAID Controller
* (Optional) TCP/IP installation if this node 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 node to provide thermal
shutdown (when an enclosure becomes too hot or cold) for the Dell PowerVault
20xS and 21xS SCSI enclosures. If OMSA is not installed, Array Manager can
provide other features of enclosure management, but not thermal shutdown.
Note: The managed node’s RAID controllers must be attached to storage in order to
run Array Manager.
** MANAGED NODE FOR NETWARE REQUIREMENTS (SERVER) **
The following are minimum requirements for installing a managed node 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.0 or later with Support Pack 4 or later.
- Novell NetWare version 5.1 with Support Pack 2a or later.
* Novell Client for Windows NT version 4.6 or later, installed on a remote
Microsoft Windows NT or Windows 2000 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 http://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.
* Transmission Control Protocol/Internet Protocol (TCP/IP) required for connection
to the management console.
* Long file name support.
* (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 node to provide thermal
shutdown (when an enclosure becomes too hot or cold) for the Dell PowerVault
20xS and 21xS SCSI enclosures. If OMSA is not installed, Array Manager can
provide other features of enclosure management, but not thermal shutdown.
Note: The managed node’s RAID controllers must be attached to storage in order to
run Array Manager.
** 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
---------------------------
Dell OpenManage Array Manager 2.5 or later can be upgraded to version
3.1. If you have a version of Dell OpenManage Array Manager that is
earlier than version 2.5, you should uninstall this version and
perform a fresh install of Dell OpenManage Array Manager 3.1.
A Dell OpenManage Array Manager 3.1 console can connect to a version
2.5 managed node or later. However, using a version of the console
earlier than 3.1 to connect to a version 3.1 managed node 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 node 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 node 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 node
on the NetWare server using an installation CD.
1) Insert the Array Manager installation CD into the NetWare server’s
CDROM drive.
2) Mount the installation CD as a NetWare volume.
3) Locate the INSTALL.NLM file on the Array Manager installation CD.
If you have the Dell OpenManage Applications CD, then the INSTALL.NLM
file is located in the <VolumeName>\NetWare\DOAM30\INSTALL.NLM
subdirectory.
If you have the Array Manager installation CD, then the INSTALL.NLM file
is located in the NETWARE subdirectory.
4) Load the INSTALL.NLM file.
If you have the Dell OpenManage Applications CD, enter:
LOAD <VolumeName>\NetWare\DOAM30\INSTALL.NLM
where <VolumeName> is the name of the NetWare volume for the
installation CD.
If you have the Array Manager installation CD, enter:
LOAD <VolumeName>\NetWare\INSTALL/NLM
where <VolumeName> is the name of the NetWare volume for the
installation CD.
For information on installing NetWare from a Windows system, see the
Array Manager online help.
------------
VII. WARNINGS
------------
* The Windows NT Disk Administrator should never be used while
Array Manager is running, particularly if there are tasks running
at the same time on the controller. DATA LOSS CAN OCCUR IF BOTH
APPLICATIONS ARE RUNNING SIMULTANEOUSLY.
* PowerEdge servers earlier than x300 are not supported.
* The (clustered) PERC 3/DCs and the PowerVault 660F fibre channel
controller are the only clustered controllers supported
by this software.
* In a clustered environment, it is recommended that all virtual disks
use the entire capacity of their member array disks. In a situation
where a virtual disk only uses a portion of an array disk, a failed
array disk may not rebuild properly.
* When importing foreign disks that contain a dynamic volume
created previously by Array Manager, YOU MUST IMPORT ALL OF THE
DISKS THAT MAKE UP THE VOLUME AT THE SAME TIME. Failure to do
so will result in DATA LOSS.
* NEVER remove a hard drive from its enclosure while the drive's
individual activity light emitting diode (LED) is blinking. This
action is likely to cause SEVERE DATA LOSS.
* PERCs have a feature called "PowerFail" that uses up to two
assigned hot spares during reconfiguration of a virtual disk
(Transform Type, Add Member). While this reconstruction is in
progress, NEVER remove the hot spare array disks that are part of
the reconstruction.
* As a general rule, you should be logged on to the local computer
system with Administrator access rights when launching the Array
Manager console.
* If you upgrade from Windows NT to Windows 2000, you should uninstall
Array Manager before the upgrade. After the upgrade, reinstall Array
Manager using the Array Manager install media or by downloading Array
Manager from the Dell Web site at http://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 web site. If you are reading this
from the Dell OpenManage Applications CD, these folders
are subfolders of /DOAM30 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 2/SC
- Windows NT driver: 4.11
- Windows 2000 driver: 2.68
- NetWare 4.2 driver: 3.11-A
- NetWare 5.x driver: 3.11-A
- Firmware: 3.13
* PERC 3/SC
- Windows NT driver: 4.11
- Windows 2000 driver: 5.23
- NetWare 4.2 driver: 3.11-A
- NetWare 5.x driver: 3.11-A
- Firmware: 1.62
* PERC 2/DC
- Windows NT driver: 4.11
- Windows 2000 driver: 2.68
- NetWare 4.2 driver: 3.11-A
- NetWare 5.x driver: 3.11-A
- Firmware: 1.04
* PERC 3/QC
- Windows NT driver: 4.11
- Windows NT-64 driver: 6.19
- Windows 2000 driver: 5.22
- NetWare 4.2 driver: 3.11-A
- NetWare 5.x driver: 3.11-A
- Firmware: 161j
* PERC 3/DC
- Windows NT driver: 4.11
- Windows 2000 driver: 5.22
- NetWare 4.2 driver: 3.11-A
- NetWare 5.x driver: 3.11-A
- Firmware: 161j
* PERC 3/DCL
- Windows NT Driver: 4.11
- Windows 2000 Driver: 5.22
- NetWare 4.2 driver: 3.11-A
- NetWare 5.x driver: 3.11-A
- Firmware: 161j
* PERC 2 (2.6)
(Versions previous to 2.6 are not supported.)
- Windows NT driver: 4892
- Windows 2000 driver: 4892
- NetWare 4.2 driver: 3499
- NetWare 5.x driver: 3506
- Firmware: 3116
* PERC 2/Si
- Windows NT driver: 4892
- Windows 2000 driver: 4892
- NetWare 4.2 driver: 3499
- NetWare 5.x driver: 3506
- Firmware: 3506
* PERC 3/Si
- Windows NT driver: 4892
- Windows 2000 driver: 4892
- NetWare 4.2 driver: 3499
- NetWare 5.x driver: 3506
- Firmware: 3506
* PERC 3/Di
- Windows NT driver: 4892
- Windows 2000 driver: 4892
- NetWare 4.2 driver: 3499
- NetWare 5.x driver: 3506
- Firmware for a PowerEdge 2500: 3116
- Firmware for a PowerEdge 2550: 3506
- Firmware for a PowerEdge 4400: 3506
- Firmware for a PowerEdge 4500: 3116
* PowerVault 660F
Windows NT or 2000:
- Host bus adapter: QL2100
- Firmware: 1.35
- Windows NT or 2000 driver: QL2100.SYS 7.05.08
OR
- Host bus adapter: QL2200
- Firmware: 1.45
- Windows NT or 2000 driver: QL2200.SYS 7.05.08
NOTES: PERC is not supported by Dell OpenManage Array Manager 3.1
on any operating system. PERC is supported by Array Manager version
2.0 on Windows NT and NetWare.
The PowerVault 660F fibre channel controller is not supported on
any version of the NetWare operating system.
The background initialization feature on PowerVault 660F controllers
is only available when using PowerVault 660F controller firmware
7.7 or later.
------------------------
X. COMPATIBILITY ISSUES
------------------------
* 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, and
PERC 3/QC controllers. To maintain the integrity of the storage
device configuration, simultaneous use of Array Manager and the PERC
console is not supported. Dell strongly recommends that Array
Manager and the PERC console not be used at the same time on the
same server.
Note that when you install the Dell OpenManage Server Agent, you
may be prompted to also install the PERC console. Given the
compatibility problems with the PERC console, you should
consider not installing it.
* Compatibility Issues With the Windows NT Disk Administrator:
The Windows NT Disk Administrator should never be used while
Array Manager is running, particularly if there are tasks running
at the same time on the controller. DATA LOSS CAN OCCUR IF BOTH
APPLICATIONS ARE RUNNING SIMULTANEOUSLY.
* Disabling the Array Manager Disk Management Service:
If you do not want the Array Manager Disk Management service
to start automatically each time you boot your machine, you can
set the service to manual start only.
Use the following steps to change the Array Manager Disk
Management service from automatic start to manual start.
On Windows NT:
1. Select "Start"-->"Settings"-->"Control Panel".
2. Double-click "Services."
3. Select "Disk Management Service."
4. Click "Startup..."
5. For Startup Type, select "Manual."
On Windows 2000:
1. Select "Start"-->"Settings"-->"Control Panel"-->
"Administrative Tools"-->"Services".
2. Select "Services" in the left pane.
3. Double-click "Disk Management Service" in the
right pane.
4. Select the "General" tab.
5. Select "Manual" from the "Startup type" pull-down menu.
6. Click "OK."
NOTICE: If the Array Manager Disk Management Service is not started,
you will not receive any alerts or warnings in the event of a failure.
* Compatibility Issues with the Dell OpenManage Server Agent
When using Array Manager with the Dell OpenManage Server Agent
1.0 through 1.4.x, you may receive duplicate events regarding the
following enclosures:
Dell PowerVault 200S
Dell PowerVault 201S
Dell PowerVault 210S
Dell PowerVault 211S
For this reason, installation of Array Manager disables the Dell
OpenManage Server Agent's enclosure management for versions of the
Server Agent 1.0 through 1.4.x.
------------------------------------
XI. Fixed Issues in Array Manager 3.1
------------------------------------
The following items have been fixed in Array Manager 3.1:
* Virtual disks created on a PERC 2/SC, 3/SC, 2/DC, 3/SC, 3/DCL, 3/DC, or
3/QC controller have a size limit of 1TB (terabytes) on NetWare 4.
(updated: issue 38479)
Problem: A virtual disk that exceeds 1TB is unusable for NetWare
traditional volumes. None of the space can be used if the space
is owned by the traditional NetWare volume management. However,
under NetWare 5, a virtual disk that exceeds 1TB could be used
by the NSS Volume Management to hold NSS volumes. Array Manager
version 3.1 will limit virtual disks to be no greater than 1TB for
NetWare 4 and will allow up to 2TB for NetWare 5 and later.
Any virtual disk created on NetWare 5 that exceeds 1TB
will be unusable unless the storage is assigned to NSS using
nwconfig for NetWare 5. NSS will be the default storage option
in future versions of NetWare.
Solution: Array Manager will automatically limit virtual disks
to a size of 1TB under NetWare 4.x and to a size of 2TB for later
versions of NetWare.
* Virtual disks created on a PERC 2/SC, 3/SC, 2/DC, 3/SC, 3/DCL, 3/DC, or
3/QC controller have an aggregate size limit of 2TB (terabytes)
(Issue 34964)
Problem: Virtual disks created on a PERC 2/SC, 3/SC, 2/DC, 3/DCL, 3/DC,
or 3/QC controller cannot be created from array disks with an
aggregate size greater than 2TB. This is a limitation of the
controller implementation. For example, a user may not select more
than 30 array disks that are 73GB in size, regardless of the size
of the resulting virtual disk. When a user attempts to select
more than 30 disks of this size, a popup message will be displayed
that indicates that the 2TB limit has been reached and to select
a smaller number of array disks.
The 2TB limit is an industry-wide SCSI limitation.
Solution: If you attempt to create a virtual disk that exceeds 2TB,
Array Manager displays a popup message indicating that you should
select a smaller number of array disks.
* Array Manager misreports the virtual disk policy on the
Properties tab under the Disks object in the tree view.
(Issue 32031)
Problem: A virtual disk's read, write and cache policy
do not display correctly on the Properties tab under
the Disks object in the tree view. This only occurs with
PERC 2/SC, PERC 3/SC, PERC 2/DC, PERC 3/QC, PERC 3/DC, and PERC 3/DCL
controllers.
Fix: The Windows Disk properties page has been fixed to
correctly show the cache settings for virtual disks of
these controllers.
Fix: The dialog's text now refers to a "Windows disk."
* The Create Virtual Disk option in the Quick Access window
is enabled even when there are no available array disks.
(Issue 29161)
Problem: The Create Virtual Disk button on the Array Manager
tool bar and Quick Access window is enabled even when there
is no RAID controller in the server.
Fix: The Create Virtual disk button on the tool bar and the
Quick Access window are now disabled when there is no RAID
controller in the server.
* Multiple "Event Log Full" messages are displayed. (Issue 34157)
Problem: When the Array Manager event log exceeds the Event Log
Size, each additional event generates a pop-up dialog on the
server running the Array Manager managed node and the Array
Manager console indicating that the event log is full. The
pop-up dialogs display in the foreground, and need to be
cleared before resuming operations on the Array Manager console.
Fix: When the event log exceeds the Event Log Size, now only one
pop-up dialog is displayed.
* Array Manager may display disks with status set to Offline and type
set to Unknown Disk on Windows NT servers. (Issue 38133)
Problem: Unknown disks continue to be displayed in Array Manager
even after enabling the Hide unknown Windows disks at startup
option on the Quick Access Window
Fix: A "Hide unknown Windows disks at startup" check
box has been added to the Array Manager Quick Access Window. When
this check box is selected, Array Manager does not display offline
disks in the tree view after restarting the Array Manager console.
Note: To verify that the offline disks are associated with either the
PowerVault 650F or 660F, check the vendor property of the disk. If it is
"DGC ....", then it is from the PowerVault 650F. If it is "DELL PV660F...",
then it is from the PowerVault 660F. For Windows NT, you will see offline
disks from the PowerVault 650F that are assigned to other servers in the
SAN.
-----------------
XII. KNOWN ISSUES
-----------------
The following sections describe known problems associated
with Array Manager or the supported controllers. Dell is
in the process of resolving these problems. The sections are
as follows:
General Problems
Problems Associated with the PowerVault 660F and 650F Controllers
Problems Associated with the PERC 2/SC, 2/DC, 3/SC, 3/DCL, 3/DC,
and 3/QC Controllers
Problems Associated with the PERC 2, 2/Si, 3/Si, and 3/Di Controllers
** GENERAL PROBLEMS **
* Array Manager console fails on Windows 2000 with Service Pack 1.
(Issue 40096)
Problem: When launching the Array Manager console on Windows
2000 with Service Pack 1, the console may fail. This problem
only occurs with certain system configurations.
Solution: Upgrade to Windows 2000 Service Pack 2.
* Uninstalling Array Manager on NetWare does not remove the MIB
directory (Issue 37478)
Problem: After uninstalling Array Manager on NetWare, the
Array Manager MIB directory still resides on the NetWare system.
This directory does not contain any files after the uninstall.
Solution: This is being investigated by Dell and will be fixed in
a future release.
* Array Manager inconsistently reports the status of removed
drives. (Issue 40179)
Problem: When you remove a drive, Array Manager indicates that the
drive is no longer available by displaying messages in the event
log and an error symbol in the tree view. Depending on which
controllers you have installed, the message you receive can vary.
For example, the event log message may say "drive removed" or
"drive offline." Array Manager may also display a yellow exclamation
point over the drive object in the tree view to indicate that the
drive is not available.
Solution: Be aware that a removed disk may be identified as either
"offline" or "removed" in the Array Manager event log.
* Array Manager event log does not report the failure of an Enclosure
Management Module on the PowerVault 220S and 221S enclosures.
(Issue 40494)
Problem: Array Manager does not display a message in the
event log or send an SNMP trap when an Enclosure Management Module
(EMM) fails on the PowerVault 220S and 221S enclosures. Array Manager
displays a red X over the enclosure object in the tree view to
indicate the failure.
Solution: Use the red X displayed over the enclosure object in the
tree view to identify an enclosure with a failed component. The
PowerVault 220S and 221S enclosures also display a yellow error light
on the front panel of the enclosure when an EMM or other component
fails. You can use this error light to identify failed
components.
* Cannot initialize 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 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.
* Cannot reactivate an array disk after a virtual disk has failed.
(Issue 38221)
Problem: If a virtual disk fails, an array disk included in the
virtual disk may be identified as a "missing disk" under the Disks
object in the Array Manager tree view. Attempting to reactivate
this missing disk may also fail.
Solution: If a virtual disk fails and one if its member array
disks is identified as missing, you must first restore the virtual
disk before reactivating the array disk.
* The install fails and displays an error message referring to an
error with "iKernel.exe" at the beginning of the installation.
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)
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
Web site at www.novell.com. To locate the Winsock 2 update on
the Novell web site using the web site'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.
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 node 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.
* Wizard menus do not update when the capacity of a virtual disk is
changed on Windows NT. (Issue 31220)
Problem: When you create a virtual disk (for example, a 4GB
virtual disk) and then delete this disk in order to create a new
virtual disk with a different size (for example, 500 MB), the
capacity of the original disk (4 GB) is displayed in the Create
Volume wizard. In this situation, a "format failed" error message
may be displayed.
Solution: Before creating a volume with the Create Volume wizard,
reboot the system to update the Create Volume wizard menus.
** PROBLEMS ASSOCIATED WITH THE POWERVAULT 660F AND 650F CONTROLLERS **
* 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.
* The Fast Charge battery function of the PowerVault 660F controller
object does not seem to work.
Problem: Performing a Fast Charge on a battery for a PowerVault
660F Fibre Channel controller can sometimes take several minutes to
start. Until the Fast Charge starts, the Fast Charge function will
still be selectable.
Solution: After selecting the Fast Charge function on a PowerVault
660F battery, wait 10 minutes and check the Battery Properties of
the controller object. The Attributes section of the property page
should show that the Fast Charge is active.
* Cannot manually enter file name when downloading PowerVault
660F controller firmware.
Problem: When using Array Manager to download PowerVault 660F
controller firmware, you type the file name into the Download
Controller Firmware dialog box. After clicking Apply,
the dialog disappears, and the firmware is not downloaded.
Solution: Dell is investigating this problem. A workaround is
to use the Browse button to select the firmware image file.
* 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.
* Reverting all controller options for the PowerVault 660F controller
causes Queue Limit to be set to zero.
Problem: When reverting all the controller options on the PowerVault
660F controller to the factory settings, the Queue Limit will be set
to 32. After applying the settings, checking this value shows
zero. While the value is set to zero, performing controller resets
may fail.
Solution: After reverting back to the factory settings, open the
Controller Options window again and manually set the Queue Limit to
32. Apply this setting, and the controller will return to the factory
settings.
* The Create Virtual Disk and Create Volume toolbar buttons are not
active when a PowerVault 660F controller is selected. (Issue 33939)
Problem: When the PowerVault 660F controller is selected in the
Array Manager tree view, the Create Virtual Disk and Create Volume
toolbar buttons are dimmed (inactive). This problem also applies
to most of the objects below the PowerVault 660F in the tree view.
Solution: To make the Create Virtual Disk and Create Volume
toolbar buttons active, select an object other than the
PowerVault 660F (and its lower-level objects) in the tree view.
You can also use the Quick Access Window buttons to create a
virtual disk or a volume.
* Cable failure between the Qlogic Host Bus Adapter and the fibre channel
switch that is attached to the slot 0 PowerVault 660F controller side in a
SAN causes Array Manager to become unmanageable. (Issue 38480)
Problem: Failure of the Qlogic HBA to switch cable on the PowerVault 660F's
slot 0 controller side of SAN fabric causes Array Manager to hang or become
unstable.
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.
* 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".
* Alarm options for the enclosure are greyed out (dimmed). (Issue 38510)
Problem: Whenever a rescan is done on the PowerVault 660F subsystem, the
Alarm Enable and Alarm Disable menu options are greyed out (dimmed).
Solution: Launch the Array Manager Service Manager, select the
Windows tab, push the stop button under the service control.
Relaunch the Array manager application. Dell is working to fix this issue.
* The revision for power supplies under PowerVault 660F subsystem is "None".
(Issue 38551)
Problem: The power supplies have a revision of "None" when viewed
from the Properties option.
Solution: Disregard the revision property for power supplies. This
field is not applicable to the power supply properties and is reserved
for future use.
** PROBLEMS ASSOCIATED WITH THE PERC 2/SC, 2/DC, 3/SC, 3/DCL, 3/DC,
and 3/QC CONTROLLERS **
* 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.
* 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, and
PERC 2/SC 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.
* After creating a virtual disk with a PERC 2/SC, PERC 3/SC, 2/DC, 3/DCL, 3/DC
or 3/QC 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 or 3/QC 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.
* Creating a virtual disk may generate an error message when using
a PERC 2/SC, 3/SC, 2/DC, 3/DCL, 3/DC, or 3/QC controller. (Issue 21083)
Problem: Creating a virtual disk may generate the following error
message: PNP provider reported physical disk \<Device>\Harddisk#>
was removed or is temporarily unavailable.
Solution: This error message displays even though an error condition
has not occurred. If this message displays after creating a virtual
disk, it can be ignored.
** PROBLEMS ASSOCIATED WITH THE PERC 2, 2/Si, 3/Si, and 3/Di CONTROLLERS **
* Unable to do Online Volume Expansion without rebooting the system
when using a PERC 2, 2/Si, 3/Si, or 3/Di Controller (Issue 31159)
Problem: After increasing the size of a virtual disk, the system is
unable to recognize the additional disk space.
Solution: Reboot the system after increasing the size of the virtual
disk. After rebooting, the system can recognize the additional disk
space.
---------------------------------------------------------
XIII. VIEWING TRAPS WITH HP OpenView NETWORK NODE MANAGER
SPECIAL EDITION (NNM SE)
---------------------------------------------------------
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. When prompted to "Load a TRAP-TYPE/NOTIFICATION-TYPE macro,"
select "Cancel."
2. Run the following command:
xnmevents-replace arymgr.cfg
3. Stop and start the OpenView NNM services. Under the HP OpenView
folder select "NNM Services-Stop" and then select "NNM Services-
Start."
------------------------------------------------------------------
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.
October, 2001
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.