--------------------------------------------------------------------
README.TXT
ICP Storage Manager (ISM)
as of November 19, 2004
--------------------------------------------------------------------
Please review this file for important information about issues
and erratas that were discovered after completion of the standard
product documentation. In the case of conflict between various
parts of the documentation set, this file contains the most
current information.
The following information is available in this file:
I.) Important information - please read before using/installing ISM
1. General Cautions and Notes
1.1 Critical
1.2 Informational
1.3 Concerning this Document
2. Supported Controllers and Firmware Releases
3. Known Limitations
4. Supported Operating Systems
5. Status of Physical Disks and Logical Devices differ between
ISM and icpcon
6. Contact Information
II.) General Information
1. Software Versions and Documentation
1.1 ICP Storage Manager
1.2 Documentation
2. Installation and Setup Notes
2.1 Supported Operating Systems
2.2 System Requirements
2.3 Setup Notes
3. General Cautions and Notes
3.1 General Cautions
3.2 General Notes
4. Array Level-Specific Notes
4.1 RAID 10 Notes
5. Operating System-Specific Issues and Notes
5.1 All
5.2 Windows - All
5.3 Windows 2000
5.4 Linux
--------------------------------------------------------------------
I.) Important information - please read before using/installing ISM
1. General Cautions and Notes
1.1 Critical
- Use icpcon, ICP Storage Manager or ICP RAID Navigator separately!
Do NOT run multiple configuration tools in parallel!
Doing so may cause unpredictable results.
- Do not use/install parallel to Adaptec Storage Manager (ASM).
If Adaptec controllers are used in the same system only use icpcon
and do not install ISM on this system!
Doing so may cause unpredictable results.
- Do not use the aacli tool with RAIDYNE based ICP RAID controllers
(e.g. GDT8500RZ, GDT85x6RZ, GDT8x14RZ, GDT8x24RZ, GDT8x22RZ).
Doing so may cause unpredictable results.
1.2 Informational
- Detailed documentation of the program can be found under help.
Note: not all features may apply to your controller.
- The Host Drives of icpcon are called Logical Devices within ISM
- The array 'Build' process in icpcon is called 'Verifying' in ISM
- Hot Fix drives are called Hot Spare in ISM
- Repair of RAID1 and RAID5 arrays can be done by using the auto
hotplug feature or by adding a Hot Spare drive to the appropriate array.
- After any action taken in ISM it is recommended to manually refresh the
displayed information.
- If a RAID1+"Hot Spare" is being built, the messages "Verify failed..."
followed by "Verify started..." are generated. This is an expected
behaviour related to internal funtions of the controller firmware.
1.3 Concerning this Document
- Unlike the information below, it is NOT possible to migrate from
RAID1 to a striped RAID level (RAID5, RAID0, RAID10) and vice versa.
- Unlike the information below, a browser based version of the
ICP Storage Manager is NOT available.
- Unlike the information below, it is NOT possible to define a single
hard disk for several RAID arrays and logical volumes respectively.
2. Supported Controllers and Firmware Releases
- The following controllers running FW 2.44.00 or higher are supported
with this release of ISM:
GDT8500RZ, GDT8546RZ, GDT8586RZ, GDT8114RZ, GDT8124RZ, GDT8514RZ,
GDT8524RZ+, GDT8524RZ+BBU, GDT8522RZ, GDT8622RZ
3. Known Limitations
- Deleting splitted Host Drives is not possible - use icpcon instead.
- Expand, Migrate and Merge are not possible - use icpcon instead.
- Cluster Functions are not supported - use icpcon instead.
- SNMP notification is not supported - use ICP SNMP subagent instead.
- ISM will not be installed into the same path as the ICP Tools.
- Hotfix Drives of Splitted Host Drives will be assigned to the first
Host Drive number of the splitted parts only.
- ISM allows to create Host Drive with up to max. 2048GB (2TB).
Larger arrays can be created with icpcon.
- Fibre Channel transfer rate is being displayed as SCSI transfer rate.
- If a drive fails during RAID5 build, the build progress counter
shows '0% Verifying' though the build process has been canceled.
- A scheduled RAID5 verification does not start on Windows systems
if the array is connected to controller 2. It works correctly if the
array is connected to controller 1 and/or if only one controller is
installed.
- The drive number of a logical drive can not be changed as known from
icpcon's 'Swap Host Drives' feature.
- ISM only supports blinking of physical drive LEDs when SAFTE processor
is available (i.e. in intelligent hot-plug backplanes). If no SAFTE
device is available on the channel the disk is connected to the blink
function does not work. Use the "F5: Identify Drive" function of
icpcon instead.
- Though it is possible to add a Hot Spare drive to a single volume and
non-redundant arrays (e.g. RAID0), this does not add redundancy features
to these volumes. The Hot Spare disk will NOT be used for these drives.
- SCSI SAFTE devices are listed on Channel 0 with ID 0 if the SAFTE device
can not be addressed correctly by the controller. Always verify the
coordinates of SAFTE devices with icpcon.
4. Supported Operating Systems
- The following OS versions are supported with this release of ISM:
o Windows 2000
o Windows 2003 32-bit only
o SuSE Linux Enterprise Server 9.0 x86
This version of ISM only runs on 32-bit OS versions.
Do NOT install on 64-bit versions.
5. Status of Physical Disks and Logical Devices differ between ISM and icpcon
Drive icpcon state ISM state
------------------------------------------------------------------------------
Single ready optimal
Single fault failed
RAID 0 ready optimal
RAID 0 error failed
RAID 1 build veriyfing (degraded in properties)
RAID 10 build veriyfing (optimal in properties)
RAID 1/10 ready optimal
RAID 1/10 fail degraded
RAID 10 error failed
RAID 4/5 idle verifying (degraded in properties)
RAID 4/5 build verifying (optimal in properties)
RAID 4/5 ready optimal
RAID 4/5 fail degraded
RAID 4/5 rebuild rebuilding
RAID 4/5 error failed
RAID 4/5 idle/patch verifying (failed in properties)
RAID 4/5 ready/patch optimal
RAID 4/5 fail/patch degraded
RAID 4/5 error/patch failed
Expand add disk
RAID 4/5 expand/ready reconfiguring
RAID 4/5 expand/fail reconfiguring (degraded reconfiguring in properties)
RAID 4/5 expand/rebuild reconfiguring (degraded reconfiguring in properties)
Expand use free capacity
RAID 4/5 build verifying
RAID 4/5 idle verifying (degraded in properties)
RAID 4/5 build/patch verifying
6. Contact Information
6.1 ICP sales
Contact ICP sales:
+49-(0)89-45 64 06 21
icp_sales@adaptec.com
6.2 ICP online support
ICP vortex home page:
http://www.icp-vortex.com
ICP products:
english - http://www.icp-vortex.com/english/product/prod_e.htm
deutsch - http://www.icp-vortex.com/german/product/prod_d.htm
ICP support:
english - http://www.icp-vortex.com/english/support/supp_e.htm
deutsch - http://www.icp-vortex.com/german/support/supp_d.htm
====================================================================
II.) General Information
1. Software Versions and Documentation
1.1. ICP Storage Manager Version 2.12.00
1.2. Documentation on this CD
- ICP Storage Manager Online Help
- ICP Storage Manager README.TXT file
--------------------------------------------------------------------
2. Installation and Setup Notes
- The ICP SATA and SCSI RAID Controllers Installation and
User's Guide contains complete installation information for the
controllers and drivers, as well as complete instructions for
all utilities and ICP software.
2.1 Supported Operating Systems
... please note 4. in previous chapter I.)
2.2 System Requirements
o Intel Compatible 500 MHz processor
o 256 MB RAM
o 35 MB hard disk drive space
o 256 color video mode
2.3 Setup Notes
- Do not attempt to install ICP Storage Manager version 2.10.00
on a system that already has ICP Storage Manager version
2.12.00 installed.
- To install ICP Storage Manager on Red Hat Enterprise Linux AS 3,
you must install two packages from the Red Hat installation CD:
o compat-libstdc7.3-2.96.122.i386.rpm
o compat-libstdc-devel-7.3-2.96.122.i386.rpm
NOTE: The version string in the file name may be different
than above; be sure to check the version string on the
Red Hat CD.
For example, type:
rpm --install /mnt/compat-libstdc7.3-2.96.122.i386.rpm
where mnt is the mount point of the CD-ROM drive.
- To run ICP Storage Manager under Red Hat Enterprise Linux
AS 3 Quarterly Update 3 for AMD64, you must add the
'noexec32=off' argument to the boot kernel command line.
Then, restart the system.
- You can configure ICP Storage Manager settings on other
servers exactly as they are configured on one server. To
replicate the ICP Storage Manager tree, notification list,
and security list, do the following:
1. Install ICP Storage Manager on one server.
2. Start ICP Storage Manager. Using the 'Add remote system'
action, define the servers for your tree.
3. Open the Notification Manager. Using the 'Add system'
action, define the notification list.
4. Open the Security Manager. Using the 'Add user' action,
define the security list.
5. Exit ICP Storage Manager.
6. Copy the following files onto a diskette from the directory
where the ICP Storage Manager is installed:
RaidMSys.ser --> to replicate the tree
RaidNLst.ser --> to replicate the notification list
RaidSLst.ser --> to replicate the security list
RaidJob.ser --> to replicate the jobs in the Task Scheduler
7. Install ICP Storage Manager on the other servers.
8. Copy the files from the diskette into the directory where
ICP Storage Manager is installed on the other servers.
- ICP Storage Manager can monitor status information returned
from certain enclosures. If there are any problems, information
such as fan status, power supply status, and temperature status
is collected and reported in the event viewer.
To monitor an enclosure, do the following:
1. Write down the description displayed in the 'Product or
Model Number' field of the enclosure device information panel.
2. Exit ICP Storage Manager.
3. Using a text editor, open the RaidDev.pps file. This file
is in the directory where ICP Storage Manager is
installed.
4. Using the enclosure description from step 1, add a line to
the file. For example, if the description is 3520EX10, add
the following:
3520EX10=true
5. Save and close the file.
6. Restart ICP Storage Manager.
--------------------------------------------------------------------
3. ICP Storage Manager Cautions and Notes
3.1 General Cautions
- While an array is being built or cleared, do not remove and
reinsert any drive from that array. Doing so may cause
unpredictable results for any of the controller's arrays.
- While a drive is being cleared, do not try to include it in a
new array. Doing so may cause unpredictable results.
- Do not move drives containing an array or volume from one
controller to another while the power is on. Doing so could
cause the loss of the array configuration or data, or both.
Instead, power off both affected controllers, move the drives,
and then restart.
- Do not run ICP Storage Manager concurrently with the CLI. Doing
so may cause unpredictable results.
3.2 General Notes
- ICP Storage Manager requires that the following range of ports
be open for remote access: 34571 - 34575.
- You can run ICP Storage Manager from a browser only under
Windows operating systems using Microsoft Internet Explorer 5.5
and later. The standalone GUI is supported under all supported
operating systems.
- To run ICP Storage Manager in a browser, your network's DNS
configuration must have matching forward and reverse lookups.
Point your browser to http://yourcomputername:34572.
- ICP Storage Manager generates log files automatically to
assist in tracking system activity. The log files are
created in the directory where the ICP Storage Manager is
installed.
o RaidEvt.log - Contains the information reported in the
ICP Storage Manager event viewer for all
local and remote systems.
o RaidEvtA.log - Contains the information reported in the
ICP Storage Manager event viewer for the
local system.
o RaidNot.log - Contains the information reported in the
Notification Manager event viewer.
o RaidSec.log - Contains the information reported in the
Security Manager event viewer.
o RaidErr.log - Contains Java messages generated by
ICP Storage Manager.
o RaidErrA.log - Contains Java messages generated by the
ICP Storage Manager agent.
Information written to these files is appended to the existing
files to maintain a history. However, if any of the files reach
a size of 200,000 bytes, the file is copied to a new file with
the extension .OLD and the original (that is, the LOG file) is
deleted and recreated. If a .OLD file already exists, the
existing .OLD file is destroyed.
- The blink LED feature is supported only in SAF-TE enabled
enclosures.
- Performing a Verify and Verify/Fix on an RAID 10 displays the same
message text in the event log, something like, "Build/Verify
started on second level array of array 'Array_0.'" You may see the
message three times for a Verify, but only once for a Verify/Fix.
- Task priority is not retained after rebooting. If you change
a priority to LOW or MEDIUM, and reboot, the controller resets the
priority to the default (HIGH).
- When an array fails, the array name returns to its default name.
- When displaying information on a physical device, the device,
vendor and model information may be displayed incorrectly.
- During array migration from a RAID 1 or RAID 5 to a RAID 0, if
the original array had a spare drive attached, the resulting
RAID 0 retains the spare drive.
- After building or verifying a leg of a second-level array, the
status of the second-level array is displayed as a "Quick
Initialized" array.
- After using a hot spare to successfully rebuild a redundant
array, information about the hot spare drive may not display
as expected. ICP Storage Manager may continue to display
it as a global hot spare.
--------------------------------------------------------------------
4. Array Level-Specific Notes
4.1 RAID 10 Notes
- You cannot change the priority of a RAID-10 verify. Setting
the priority at the start of a verify has no effect. The
priority is still shown as high. Changing the priority of
a running verify on a raid-10 changes the displayed priority
until a rescan is done, then the priority shows as high again.
- Performing a Verify and Verify/Fix on an RAID 10 displays the
same message text in the event log, "Build/Verify started on
second level array of array 'Array_0.'" You may see the message
three times for a Verify, but only once for a Verify/Fix.
- During a migration from a RAID 0 to any redundant array like
RAID 1, 5, or 10, ICP Storage Manager shows the status as
"Degraded Reconfiguring" for a moment, then the status changes
to "Reconfiguring." The "Degraded" status does not appear in the
event log.
--------------------------------------------------------------------
5. Operating System-Specific Issues
5.1 All
- ICP Storage Manager will not start on a system that is using
only 16 colors. ICP Storage Manager supports a minimum of 256
colors. You must switch the video mode from 16 colors to a mode
with at least 256 colors.
- If the ICP Storage Manager console does not repaint correctly,
select the View->Refresh menu item to repaint the screen.
5.2 Windows - All
- To run ICP Storage Manager in a browser, your network's
DNS configuration must have matching forward and reverse
lookups.
- The Java Virtual Machine has a problem with the 256-color
palette. (The ICP Storage Manager display may be distorted
or hard to read.) Set the Display Properties Settings to a
color mode with greater than 256 colors.
- When you shut down Windows, you might see the message
"unexpected shutdown". Windows displays this message if the
ICP Storage Manager Agent fails to exit within 3 seconds.
It has no affect on file I/O or other system operations and can
be ignored.
5.3 Windows 2000
- More event notifications are generated than arrays degraded.
For example, in a configuration with four RAID 5s sharing
three drives, one failed drive causes six notifications--one for
each of the arrays affected, plus two extra for the second array.
5.4 Linux
- When you delete an array, the operating system can no longer see
the last array. WORKAROUND: To allow Linux to see the last array,
restart your system.
- The controller does not support attached CD drives during OS
installation.
- If you cannot connect to a remote ICP Storage Manager
installed on a Linux system, verify that the TCP/IP hosts file
is configured properly.
1. Open the /etc/hosts file.
NOTE: The following is an example:
127.0.0.1 localhost.localdomain localhost matrix
2. If the hostname of the system is identified on the line
with 127.0.0.1, you must create a new host line.
3. Remove the hostname from the 127.0.0.1 line.
NOTE: The following is an example:
127.0.0.1 localhost.localdomain localhost
4. On a new line, type the IP address of the system.
5. Using the Tab key, tab to the second column and enter the
fully qualified hostname.
6. Using the Tab key, tab to the third column and enter the
nickname for the system.
NOTE: The following is an example of a completed line:
1.1.1.1 matrix.localdomain matrix
where 1.1.1.1 is the IP address of the server and
matrix is the hostname of the server.
7. Restart the server for changes to take effect.
- On certain versions of Linux, you may see messages concerning font
conversion errors. Font configuration under X-Windows is a known
JVM problem. It does not affect the proper operation of the
ICP Storage Manager software. To suppress these messages,
add the following line to your .Xdefaults file:
stringConversionWarnings: False
- Some pop-up identification boxes include complete window frames
when running the ICP Storage Manager in bootable-CD mode.
These pop-ups may run off the side of the screen due to the
extra width of the window frame. This is a known problem of the
fvwm window manager on the CD.
- On rare occasions, the online help system may generate a Java
exception. This is due to a known problem in the HTML rendering
section of JFC/Swing.
--------------------------------------------------------------------
(c) 2004 Adaptec, Inc. All Rights Reserved. This software contains the
valuable trade secrets of Adaptec or its licensors. The software is
protected under international copyright laws and treaties. This software
may only be used in accordance with the terms of its accompanying license
agreement. No part of this publication may be reproduced, stored in a
retrieval system, or transmitted in any form or by any means, electronic,
mechanical, photocopying, recording or otherwise, without prior written
consent of Adaptec, Inc., 691 South Milpitas Blvd., Milpitas, CA 95035.
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.