Dell OpenManage(TM) Array Manager 2.0 Readme
This readme file contains updated information for your Dell
OpenManage(TM) Array Manager User's Guide and any other technical
documentation included with this product.
Always see the Dell World Wide Web site at http://www.dell.com
for the most current information.
The following sections contain updated requirements and open issues
for the Dell OpenManage Array Manager 2.0 software.
=======================================================================
Notes, Notices, Cautions, and Warnings
=======================================================================
Throughout this guide, blocks of text may be used to draw your attention.
These blocks are notes, cautions, and warnings, and they are used as
follows:
NOTE: A NOTE indicates important information that helps you make better
use of your computer system.
NOTICE: A NOTICE indicates either potential damage to hardware or loss
of data and tells you how to avoid the problem.
CAUTION: A CAUTION indicates either potential damage to hardware or loss
of data and tells you how to avoid the problem.
WARNING: A WARNING indicates the potential for bodily harm and tells you
how to avoid the problem.
Some warnings may appear in alternate formats and may be unaccompanied by
an icon. In such cases, the specific presentation of the warning is
mandated by regulatory authority.
==================================================================
Dell OpenManage Array Manager 2.0
==================================================================
--------
Contents
--------
I. System Requirements
II. Warnings
III. CD Directory Structure
IV. Required Driver/Firmware Revisions
V. Compatibility Issues
VI. Known Issues
VII. Winsock 2 on Novell(R) NetWare(R) Version 4.2 With Support Pack 8
VIII. Viewing Traps With Hewlett Packard OpenView Network Node Manager
Special Edition
----------------------
I. SYSTEM REQUIREMENTS
----------------------
GENERAL REQUIREMENTS:
* 64 (megabytes) MB of (random-access memory) RAM
* Dell(TM) PowerEdge(TM) Expandable RAID Controller (PERC)
PERC 2
PERC 2/Single Channel (SC)
PERC 2/Dual Channel (DC)
PERC 2/Single Integrated (SI)
PERC 3/Single Integrated (SI)
and/or
PERC 3/Dual Integrated (DI)
* Simple Network Management Protocol (SNMP) services for SNMP support
(optional)
MICROSOFT WINDOWS NT SPECIFIC REQUIREMENTS:
* 40 MB of free hard drive space
* Microsoft(R) Windows NT(R) Version 4.0 With Service Pack 5 or later
* Transmission control protocol/Internet protocol (TCP/IP) connection on
the console and server when attempting remote node management
* Microsoft Internet Explorer Version 4.0 or later for online
help and the browser plug-in (optional)
* Microsoft Management Console (MMC) Version 1.1 or later for
snap-in support (optional)
* Dell Hardware Instrumentation Package (HIP) Version 3.5.2 or later
for enclosure management (optional)
NETWARE SPECIFIC REQUIREMENTS:
* 15 MB of free hard-disk drive space
* Novell(R) NetWare(R) Version 4.2 With Support Pack 8 or later.
WinSock 2 support needs to be enabled after install of Support Pack 8.
See section VII.
* Novell NetWare Version 5.0 With Support Pack 4 or later
* Novell NetWare Version 5.1
* Novell NetWare Client Version 4.6 or later
* TCP/IP required for connection to management console
* Long filename support
------------
II. WARNINGS
------------
* Microsoft Windows(R) 2000 is not supported at this time.
* Dell PowerEdge 2200, 4200, and 6100 servers are not supported by this
software.
* Clustered PERCs are not supported by this software.
* Array Manager 1.0 console cannot manage a 1.5 or 2.0 managed node.
* When importing a foreign disk that contains a dynamic volume created
previously by Array Manager, YOU MUST IMPORT ALL OF THE DISKS AT THE
SAME TIME. Failure to do so will result in DATA LOSS.
* NEVER remove a hard-disk 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
hotspares during reconfiguration of a virtual disk (Transform Type,
Add Member). While this reconstruction is in progress, NEVER remove
the hotspare array disks that are part of the reconstruction.
* As a general rule, you should be logged into the local machine with
Administrator access rights when launching the "Array Manager Console."
---------------------------
III. CD DIRECTORY STRUCTURE
---------------------------
\DOCUMENTATION - Contains the Array Manager documentation.
\DRIVERS\NT40\PERC - Contains PERC drivers for Windows NT.
\DRIVERS\NT40\PERC2 1.1 - Contains PERC 2 1.1 drivers for Windows NT.
\DRIVERS\NT40\PERC2 2.1 - Contains PERC 2 2.1 drivers for Windows NT.
\DRIVERS\NT40\PERC2SC - Contains PERC 2/SC drivers for Windows NT.
\DRIVERS\NT40\PERC2DC - Contains PERC 2/DC drivers for Windows NT.
\DRIVERS\NT40\PERC2SI - Contains PERC 2/Si drivers for Windows NT.
\DRIVERS\NT40\PERC3SI - Contains PERC 3/Si drivers for Windows NT.
\DRIVERS\NT40\PERC3DI - Contains PERC 3/Di drivers for Windows NT.
\DRIVERS\NETWARE\PERC - Contains PERC drivers for Netware.
\DRIVERS\NETWARE\PERC2 - Contains PERC 2 drivers for Netware.
\DRIVERS\NETWARE\PERC2SC - Contains PERC 2/SC drivers for NetWare.
\DRIVERS\NETWARE\PERC2DC - Contains PERC 2/DC drivers for NetWare.
\DRIVERS\NETWARE\PERC2SI - Contains PERC 2/Si drivers for NetWare.
\DRIVERS\NETWARE\PERC3SI - Contains PERC 3/Si drivers for NetWare.
\DRIVERS\NETWARE\PERC3DI - Contains PERC 3/Di drivers for NetWare.
\FIRMWARE\PERC - Contains PERC firmware.
\FIRMWARE\PERC2 1.1 - Contains PERC 2 1.1 firmware.
\FIRMWARE\PERC2 2.1 - Contains PERC 2 2.1 firmware.
\FIRMWARE\PERC2SC - Contains PERC 2/SC firmware.
\FIRMWARE\PERC2DC - Contains PERC 2/DC firmware.
\FIRMWARE\PERC2SI - Contains PERC 2/Si firmware.
\FIRMWARE\PERC3SI - Contains PERC 3/Si firmware.
\FIRMWARE\PERC3DI - Contains PERC 3/Di firmware.
\SETUP - Contains the Array Manager setup files.
\UPDATE - Contains the HTML Help Viewer update package.
--------------------------------------
IV. REQUIRED DRIVER/FIRMWARE REVISIONS
--------------------------------------
* PERC
- Windows NT Driver: 2.32
- NetWare Driver: 2.06
- Firmware: U.81
* PERC 2/SC
- Windows NT Driver: 2.32
- NetWare Driver: 2.06
- Firmware: 3.13
* PERC 2/DC
- Windows NT Driver: 2.32
- NetWare Driver: 2.06
- Firmware: 1.01
* PERC 2
- Windows NT Driver: 1935
- NetWare Driver: Not Supported
- Firmware: 1963
* PERC 2
- Windows NT Driver: 2938
- NetWare Driver: 2938
- Firmware: 2939
* PERC 2/Si
- Windows NT Driver: 2874
- NetWare Driver: 2874
- Firmware: 2874
* PERC 3/Si
- Windows NT Driver: 2900
- NetWare Driver: 2896
- Firmware: 2906
* PERC 3/Di
- Windows NT Driver: 2905
- NetWare Driver: 2881
- Firmware: 2907
-----------------------
V. COMPATIBILITY ISSUES
-----------------------
* Compatibility Issues With the Flexible Array Storage Tool (FAST) on
Windows NT:
Both Array Manager and FAST can be installed on the same Windows NT
server. However, only one program at a time can be used to actively
configure PERC 2, PERC 2/Si, PERC 3/Si, or PERC 3/Di controllers. The
interface supports two different access rights: read-only and
read-write.
To maintain the integrity of the storage device configuration, the
interface grants read-write access to one application only and
read-only access to others. When Array Manager is launched, it first
attempts read-write access. If read-write access is denied, Array
Manager grants read-only access to the controller. When Array Manager
is launched in read-only mode, you can view storage devices and
storage device properties, but you cannot configure controllers or
devices on them.
If you want to launch Array Manager in read-write access mode, make
sure FAST is not running.
NOTE: If FAST is launched while the Array Manager Disk Management
Service is stopped, FAST is given read-write access to any
controllers it opens. You must first close FAST and restart the
Disk Management Service (from the Array Manager Service Manager)
to manage PERC 2, PERC 2/Si, PERC 3/Si, or PERC 3/Di controllers with
Array Manager. The same notes apply to the command-line interface
(CLI) for the PERC 2, 2/Si, 3/Si, and 3/Di controllers.
* Compatibility Issues With the FAST on NetWare:
Array Manager and FAST may have problems if they are installed on the
same NetWare server. FAST will install all of its files to the
system directory on the NetWare server, so they will always be loaded
before Array Manager's files. Array Manager and FAST use some of the
same files, so if the files in the system folder are older than the
ones that come on the Array Manager CD, Array Manager will not work
properly and possibly not at all. Install detects this and forces
you to disable the conflicting files before continuing the install.
Disabling actually renames the extensions of "fsamutex.nlm" and
"partapi.nlm" to ".bak," so if you want to revert this at a later
time, all you need to do is change the extensions back to ".nlm."
* 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, PERC 2/SC, and PERC 2/DC controllers. To maintain the
integrity of the storage device configuration, simultaneous use of
Array Manager and PERC Console is not supported. Dell strongly
recommends that Array Manager and PERC Console not be used at the
same time on the same server.
* Compatibility Issues With Disk Administrator:
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 Service:
If you do not want the Array Manager service to start automatically
each time you boot your machine:
1. Select "Start"-->"Settings"-->"Control Panel"
2. Double-click "Services."
3. Select "Disk Management Service."
4. Click "Startup..."
5. For Startup Type, select "Manual."
The Disk Management Service automatically starts any time the
console is opened and can also be started from Service Manager.
NOTICE: If the Disk Management Service is not started, you will not
receive any alerts or warnings in the case of failure.
----------------
VI. KNOWN ISSUES
----------------
* 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.
* Multiple simultaneous operations on NetWare causes strange/slow
console behavior.
Problem: Controllers on a NetWare server that are performing
multiple simultaneous operations may cause the remote
console to appear "frozen".
Solution: The console will return to normal operation when the
operations are complete.
RECOMMENDATION: Do not perform more than 2 simultaneous controller
operations on a NetWare server.
* NetWare server abends when performing Add Member or Transform Type
functions with PERC, PERC 2/SC, or PERC 2/DC RAID controllers.
Problem : When 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.
* Backward Compatibility With Array Manager 1.x
Problem 1: When an Array Manager 1.0 managed node is managed from a
2.0 console, events may not show up correctly.
Solution: Upgrade the managed node to 2.0.
Problem 2: The "RAID Policy" wizard will not open on a 1.x managed
node.
Solution: Upgrade the managed node to 2.0.
* Microsoft HTML Help Viewer
Problem: "Help Viewer" fails to load online help or the tabs
do not operate as expected.
Solution 1: Run the "hhupd.exe" from the \Help Update folder on the
Microsoft HTML Help Viewer CD.
Solution 2: Delete the "hh.dat" file from your Windows folder.
* 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 "Default Protocols" tab.
Remove all of the protocols EXCEPT "Connection-oriented
TCP/IP."
NOTICE: If other applications reside on a server requiring 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.
* PercRAID.Log Events in the Windows NT Event Log
Problem: PERC Console (a legacy Dell RAID configuration utility)
installs a service called "PercRAID," that monitors the
status of PERC, PERC 2/SC, and PERC 2/DC RAID controllers.
When unassigning a hotspare 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.
* Enclosure Management may not be available after installing the
HIP agent from the Dell OpenManage Applications CD.
Problem: After installing the HIP agent from the Dell
OpenManage Applications CD, the "Dell Enclosures"
group does not appear in the left pane of the Array
Manager console.
Solution 1: The HIP agent was installed after Array Manager was
installed. Open the Array Manager Service Manager
and check the box labeled "Enclosure Management."
The "Dell Enclosures" group will be in the left pane.
Solution 2: When installing the HIP agent, you did not select
the "Adaptec CIO" option. See the Dell HIP OpenView NNM
SE documentation for details.
Solution 3: ASPI was never installed on your system or is not working
properly. Run "aspi32.exe," which is located on the Dell
OpenManage Applications CD.
Solution 4: There is a problem with the PERC 2/DC driver that prevents
enclosure management on channel 1.
There is no solution for this at this time.
* NetWare Version 4.2 is missing various NetWare Loadable Modules
(NLMs) required by Array Manager.
Problem: When attempting to start Array Manager on NetWare Version
4.2, the console may report that a number of NLMs are not
loaded (such as "cdbe.nlm," "ws2_32.nlm," etc).
Solution: Array Manager requires the WinSock 2 update on NetWare
Version 4.2 servers. This update is available from the
Novell website at www.novell.com\download\index.html. See
section VII for instructions on how to enable WinSock 2
support after installing Support Pack 8.
* 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: None at this time. You must 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.
* 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 and the drive letter will be available
again.
* Opening a second window from the Array Manager browser plug-in causes
multiple problems.
Problem: After choosing "File"-->"New Window," several error messages
appear and the Array Manager plug-in loses functionality
and/or features.
Solution: Do not open multiple windows when using the Array Manager
plug-in.
* Volume created from a RAID policy does not display label.
Problem: The volume created from applying a RAID policy (only the last
volume of a multiple volume set) does not have a label upon
completion of the RAID policy.
Solution: After completion of the RAID policy, manually refresh the
console.
------------------------------------------------------------------
VII. WinSock 2 on Novell NetWare Version 4.2 With Support Pack 8
------------------------------------------------------------------
After installing Support Pack 8, manually copy the files in
the extracted SP8 directory (nw4sp8\tools\coredump)
to somewhere in the server's search path, e.g. sys:\system (Novell
documentation recommends copying to c:\nwserver on boot partition).
------------------------------------------------------------------
VIII. Viewing Traps With HP OpenView NNM Special Edition
------------------------------------------------------------------
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:
1. Load the Dell Array Manager MIB "arymgr.mib;" when prompted to
"Load a TRAP-TYPE/NOTIFICATION-TYPE macro," select "Cancel."
2. Run the 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."
------------------------------------------------------------------
Trademarks used in this text: Dell, Dell OpenManage, and PowerEdge
are trademarks of Dell Computer Corporation; Microsoft, Windows, and
Windows NT are registered trademarks of Microsoft Corporation;
Novell and NetWare are registered trademarks of Novell, Inc;
Adobe is a trademark of Adobe Systems Incorporated, which may be
registered in certain jurisdictions. OpenView is a trademark of the
Hewlett-Packard Company. Other trademarks and trade names may be
used in this document to refer to either the entities claiming the
marks and names or their products. Dell Computer Corporation disclaims
any proprietary interest in trademarks and trade names other than its
own.
June 2000
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.