\def_style 0 \font font.normal \fg color.black \bg color.transparent
\def_style 1 \font font.bold \fg color.black \bg color.transparent
\def_style 2 \font font.bold \fg color.blue \bg color.transparent \curs curs.magglass
\def_style 3 \font font.bold \fg color.blue \bg color.transparent \curs helpw.curstopic
\def_style 4 \font font.bold \fg color.red \bg color.transparent
\def_style 5 \font font.bold \fg color.blue \bg color.transparent \curs curs.arrowdown
\def_style 7 \font font.bold \fg color.blue \bg color.transparent \curs curs.arrowup

\topic "Home Page" \p\1
HOME PAGE \label "hometop"
\p\p
Fast Find -- \{\5\goto "restricthome" Restrictions\} | \{\5\goto "cqhome" Common Questions\} | \{\5\goto "tshome" Troubleshooting\} | \{\5\goto "ithome" Interface Description\} \0\p\p
\{\3\subtopic "Concept Topics" Concepts\} -- Select this path to view a list of topics that define storage management concepts and explain related hardware/software requirements, associated tasks, and software processes.
\p\p
\{\3\subtopic "Common Task Topics" Common Tasks Available In All Applications\} -- Select this path to view a list of topics for the options available from the tool bar area in every application.
\p\p
\{\3\subtopic "Application Task Topics" Specific Tasks Available In Each Application\} -- Select this path to view a list of topics for the options available in each application. The topics are arranged by application.
\p\p
\{\3\subtopic "Procedure Topics" Procedures\} -- Select this path to view a list of "How to" topics that provide step-by-step details for the various storage management tasks you may want to perform.
\p\p\label "restricthome"
\{\3\subtopic "Restriction/Caution Topics" Restrictions/Cautions\} -- Select this path to view a list of known restrictions organized by task.
\p\p\label "cqhome"
\{\3\subtopic "Common Question Topics" Common Questions\} -- Select this path to view a list of questions organized by concept and task.
\p\p\label "tshome"
\{\3\subtopic "Troubleshooting Topics" Troubleshooting\} -- Select this path to view a list of troubleshooting topics organized by component and tasks.
\p\p\label "ithome"
\{\3\subtopic "Interface Topics" Interface Description\} -- Select this path to view a description of the storage management software's interface screen contents.
\p\p
\1 NOTE:\0 Remember you can select Contents from the top menu to view a list of all topics in help.
\p\p
\{\7\goto "hometop" Top Of Page\}\p

\topic "Concept Topics" \p\1
Concepts \label "concepttop"
\p\p\1
Fast Find -- \{\5\goto "conceptfirmware" Firmware\} | \{\5\goto "concepthostinterface" Host Interface\} | \{\5\goto "concepthost" Host Configurations\} | \{\5\goto "conceptlunassign" LUN Assignment\} | \{\5\goto "conceptnvsram" NVSRAM\} | \{\5\goto "conceptparity" Parity\} | \{\5\goto "conceptperform" Performance\} | \{\5\goto "conceptrecon" Reconstruction\} | \{\5\goto "conceptselect" Selecting Modules\} | \{\5\goto "conceptstat" Statuses\} | \{\5\goto "conceptrt" Related Topics\} \0\p\p
\{\3\subtopic "ASC/ASCQ Error Codes Concept" ASC/ASCQ Error Codes\}
\p\p
\{\3\subtopic "Caching Concept" Caching\}
\p\p
\{\3\subtopic "Changing LUN Parameters Concept" Changing LUN Parameters\}
\p\p
\{\3\subtopic "Component Concept" Component\}
\p\p
\{\3\subtopic "Configuring Concept" Configuring\}
\p\p
\{\3\subtopic "Failure Types Concept" Failure Types\}
\p\p
\{\3\subtopic "Fibre Channel Concept" Fibre Channel\}
\p\p\label "conceptfirmware"
\{\3\subtopic "Firmware Concept" Firmware\}
\p\p\label "concepthostinterface"
\{\3\subtopic "Host Interface Connections Concept" Host Interface Connections\}
\p\p\label "concepthost"
\{\3\subtopic "Host-RAID Module Configuration Types Supported Concept" Host-RAID Module Configuration Types Supported\}
\p\p\label "conceptlunassign"
\{\3\subtopic "LUN Assignment Concept" LUN Assignment\}
\p\p\label "conceptnvsram"
\{\3\subtopic "NVSRAM Concept" NVSRAM\}
\p\p\label "conceptparity"
\{\3\subtopic "Parity Concept" Parity\}
\p\p\label "conceptperform"
\{\3\subtopic "Performance Concept" Performance\}
\p\p\label "conceptrecon"
\{\3\subtopic "Reconstruction Concept" Reconstruction\}
\p\p\label "conceptselect"
\{\3\subtopic "Selecting RAID Modules Concept" Selecting RAID Modules\}
\p\p\label "conceptstat"
\{\3\subtopic "Statuses Concept" Statuses\}
\p\p\1
Related Topics \0\label "conceptrt" \p
\{\3\goto "Common Task Topics" Common Tasks\} \p
\{\3\goto "Procedure Topics" Procedures\} \p
\{\3\goto "Application Task Topics" Specific Tasks Available In Each Application\}
\p\p
\{\7\goto "concepttop" Top Of Page\} \p
\keyword "concept details"
\keyword "details, concept"

\topic "ASC/ASCQ Error Codes Concept" \p\1
ASC/ASCQ Error Codes \label "ascascqtop" 
\p\p
Fast Find -- \{\5\goto "ascascqrt" Related Topics\}
\p\p\1
What Is It \0\p\p
You might see \{\2\bring_popup "ASC/ASCQ Code" ASC/ASCQ\} error codes in the Message Log (Show Details) for hardware messages. These codes are returned by the RAID Module's \{\2\bring_popup "Controller" controllers\} and indicate that a specific problem has occurred. When a hardware problem is detected, you should always follow the recommended Action to Take. Most likely, you will need to use Recovery Guru/Health Check >> Show Procedures in the Recovery Application to resolve the problem. \p\p\1
Associated Tasks \0\p\p
For detailed procedures, see the \{\5\goto "ascascqrt" Related Topics\} below. For a detailed description of the possible ASC/ASCQ codes, select the ASC/ASCQ Error Codes topic.
\p\p
\{\1 o \0\} Viewing hardware messages: Status Application >> Message Log >> Show Details
\p\p
\{\1 o \0\} Selecting ASC/ASCQ message details: Status Application >> Message Log >> List Type
\p\p
\{\1 o \0\} Fixing component failures: Recovery Application >> Recovery Guru/Health Check >> Show Procedure
\p\p\1
Related Topics\0\label "ascascqrt"\p
\{\3\goto "ASC/ASCQ Error Codes" ASC/ASCQ Error Codes\} \p
\{\3\goto "How To List Different Types Of Messages" How To List Different Types Of Messages\} \p
\{\3\goto "How To Use Recovery Guru" How To Use Recovery Guru\} \p
\{\3\goto "Information In Show Details" What Information Appears in Show Details?\}
\p\p
\{\6\goto "ascascqtop" Top Of Page\}\p
\keyword "ASC/ASCQ" \keyword "hardware errors" \keyword "controller error codes" \keyword "code"

\topic "Caching Concept" \p\1
Caching \label "cachetop"
\p\p
Fast Find -- \{\5\goto "cacheat" Associated Tasks\} | \{\5\goto "cachewhat" What Happens\} | \{\5\goto "cachert" Related Topics\}
\p\p\1
What Is It \0\p\p
If the controllers in the module have the minimum performance and cache sizes, certain cache parameters are supported. There are three caching parameters that you can set in the GUI: write caching, write cache mirroring, and cache without batteries. In addition, there are several other advanced caching parameters that you can set using the command line utility, raidutil. Cache performance can be monitored using the Performance Monitor in the Status Application.
\p\p\1
IMPORTANT \0\p
Using caching parameters requires that your \{\2\bring_popup "RAID Module" RAID Module\} have at least one Series 3 or Series 4 controller with a minimum 8 MB \{\2\bring_popup "Processor Memory" processor\} and \{\2\bring_popup "Cache Memory" cache\} memory sizes.
\p\p\1
Associated Tasks \0\label "cacheat"\p\p
For detailed procedures, see the \{\5\goto "cachert" Related Topics\} below.
\p\p
\{\1 o \0\} View or verify cache and processor sizes: Any Application >> RAID Module >> Module Profile >> Controllers
\p\p
\{\1 o \0\} Set or change cache parameters:
\p\p
-- When creating new LUNs: Configuration Application >> RAID Module >> Create LUNs >> Options >> Caching
\p\p
-- For existing LUNs: Maintenance/Tuning Application >> Caching Parameters
\p\p
\{\1 o \0\} View cache parameter settings:
\p\p
-- Any Application >> RAID Module >> Module Profile >> LUNs
\p\p
-- Maintenance/Tuning Application >> Caching Parameters
\p\p
\{\1 o \0\} Monitor cache performance: Status Application >> RAID Module >> Performance Monitor
\p\p\1
NOTE\0: You can use the command line utility, raidutil, to set other advanced caching parameters, such as cache read ahead.
\p\p\1
What Happens \0\label "cachewhat"\p\p
As the Associated Task list describes, the storage management software allows you to set caching parameters both during LUN creation and after. It also displays the current settings for three caching parameters by logical unit (LUN).
\p\p
Keep in mind that some of the parameters are interdependent. Consequently, when you make a change to one parameter, another parameter could also become enabled or disabled.
\p\p\1
Related Topics \0\label "cachert"\p
\{\3\goto "Caching Restrictions" Restrictions/Cautions\} \p
\{\3\goto "How To View/Verify Cache Size" How To View/Verify Cache Memory Size\} \p
\{\3\goto "How To Use Caching Parameters" How To Use Caching Parameters\} \p
\{\3\goto "How To Use Performance Monitor" How To Use Performance Monitor\} \p
\{\3\goto "Caching Troubleshooting" Troubleshooting\} \p
\{\3\goto "Viewing Caching Parameter Settings" Viewing Caching Parameter Settings\} \p
\{\3\goto "Information In Caching Parameters" What Information Appears In Caching Parameters?\}
\p\p
\{\7\goto "cachetop" Top Of Page\} \p
\keyword "caching" \keyword "parameters, caching" \keyword "raidutil utility"

\topic "Changing LUN Parameters Concept" \p\1
Changing LUN Parameters \label "lunparamtop" 
\p\p
Fast Find -- \{\5\goto "lunparamat" Associated Tasks\} | \{\5\goto "lunparamrt" Related Topics\}
\p\p\0
After \{\2\bring_popup "Logical Unit" LUNs\} are created, you can change the various parameters: RAID Level, segment size, caching, etc. However, some of the changes require you to delete the LUN using Delete and then recreate it using Create LUN. See the \{\5\goto "lunparamat" Associated Tasks\} list below for which options to use to change the LUN parameters.
\p\p\1
IMPORTANT\0\p
\{\1 o \0\} Consult the ''Installation and Support Guide'' for your operating system BEFORE deleting and re-creating any logical unit. Some operating systems have special limitations or requirements such as \{\2\bring_popup "Windows NT Delete" Windows NT\}. Additionally, some operating systems require that you reboot your system after making ANY configuration changes so that the operating system can recognize the new configuration.
\p\p
\{\1 o \0\} If you are deleting all the LUNs on a \{\2\bring_popup "RAID Module" RAID Module\} in order to re-create them, backup the data on those LUNs BEFORE deleting them. When re-creating them WAIT for the first LUN to become Optimal before creating others to make sure the operation is completed successfully. \p\p\1
Associated Tasks \label "lunparamat"\0\p\p
For detailed procedures, see the \{\5\goto "lunparamrt" Related Topics\} below.
\p\p
\{\1 o \0\} Changing \{\2\bring_popup "RAID Level" RAID Level\}: Configuration Application >> Modify Group/LUNs >> RAID Level \p\p
\{\1 o \0\} Changing number of drives in an individual LUN: Configuration Application >> Delete, then Configuration >> Create LUN \p\p
\{\1 o \0\} Changing \{\2\bring_popup "Segment Size" segment size\}: Configuration Application >> Modify Group/LUN >> Segment Size \p\p
\{\1 o \0\} Changing \{\2\bring_popup "Configured Drive Group" drive group\} capacity: Configuration Application >> Modify Group/LUN >> Group Capacity \p\p
\{\1 o \0\} Changing caching parameters: Maintenance/Tuning Application >> Caching Parameters \p\p
\{\1 o \0\} Changing LUN Assignment: Maintenance/Tuning Application >> LUN Balancing \p\p
\{\1 o \0\} Changing reconstruction \{\2\bring_popup "Reconstruction Rate" rate\}: \p\p
-- For any LUNs: Maintenance/Tuning Application >> LUN Reconstruction Rate >> Save \p\p
-- For only LUNs undergoing reconstruction: Status Application >> LUN Reconstruction \p\p\1
Related Topics \label "lunparamrt"\0\p
\{\3\goto "Configuring Concept" Configuring RAID Modules\} \p
\{\3\goto "Configuration Questions" Common Questions\} \p
\{\3\goto "Configuration Application" Configuration Application\} \p
\{\3\goto "How To Change The Reconstruction Rate" How To Change The Reconstruction Rate\} \p
\{\3\goto "How To Use Caching Parameters" How To Use Caching Parameters\} \p
\{\3\goto "How To Use Create LUN" How To Use Create LUN\} \p
\{\3\goto "How To Use Delete" How To Use Delete\} \p
\{\3\goto "How To Use LUN Balancing" How To Use LUN Balancing\} \p
\{\3\goto "How To Use Modify Group/LUN" How To Use Modify Group/LUN\} \p
\{\3\goto "Configuration Restrictions" Restrictions/Cautions\} \p
\{\3\goto "Configuration Troubleshooting" Troubleshooting\}
\p\p
\{\7\goto "lunparamtop" Top Of Page\}\p
\keyword "configuration" \keyword "changing LUN parameters" \keyword "parameters, LUN" \keyword "LUN parameters"

\topic "Component Concept" \p\1
Component \label "compcontop" 
\p\p
Fast Find -- \{\5\goto "componentat" Associated Tasks\} | \{\5\goto "componentrt" Related Topics\}
\p\p\1
What Is It \0\p\p
The storage management software monitors the components in the \{\2\bring_popup "RAID Module" RAID Module\} through the controller and reports their operating condition as a status. Component statuses are displayed for controllers, drives, and LUNs. Other hardware components (such as batteries, fans, and power supplies) can be monitored by using Recovery Guru/Health Check (Recovery Application).
\p\p
When a status is NOT Optimal (in its best working state), it indicates that some repair or replacement may be required. If you see a component status other than Optimal for a \{\2\bring_popup "Controller" controller\}, drive, or \{\2\bring_popup "Logical Unit" LUN\}, it is best to use Recovery Guru to diagnose the problem. Recovery Guru determines the failure type and provides the correct procedure for fixing it.
\p\p\1
Associated Tasks \0\label "componentat"\p\p
For detailed procedures, see the \{\5\goto "componentrt" Related Topics\} below.
\p\p
\{\1 o \0\} Diagnosing component failures: Recovery Application >> Recovery Guru/Health Check
\p\p
\{\1 o \0\} Fixing component failures: Recovery Application >> Recovery Guru/Health Check >> Show Procedure
\p\p
\{\1 o \0\} Viewing component statuses: Any Application >> RAID Module >> Module Profile >> Controllers, Drives, or LUNs
\p\p
\{\1 o \0\} Viewing historical information on component problems: Status Application >> Message Log
\p\p\1
Related Topics \0\p\label "componentrt"
\{\3\goto "Component Questions" Common Questions\} \p
\{\3\goto "How To Use Message Log" How To Use Message Log\} \p
\{\3\goto "How To Use Recovery Guru" How To Use Recovery Guru/Health Check\} \p
\{\3\goto "Statuses Concept" Statuses\} \p
\{\3\goto "Updating Component Statuses" Updating Component Statuses\} \p
\{\3\goto "Viewing Component Statuses" Viewing Component Statuses\}
\p\p
\{\7\goto "compcontop" Top Of Page\}\p
\keyword "component details" \keyword "error detection" \keyword "status reporting" \keyword "details, components"

\topic "Configuring Concept" \p\1
Configuring \label "configuringtop" 
\p\p
Fast Find -- \{\5\goto "configuringat" Associated Tasks\} | \{\5\goto "configuringrt" Related Topics\}
\p\p\1
What Is It \0\p\p
When you receive your \{\2\bring_popup "RAID Module" RAID Module\}, there are default \{\2\bring_popup "Logical Unit" logical units\} (LUNs) and \{\2\bring_popup "Configured Drive Group" drive groups\} already configured on it. This default configuration may work for your environment. However, you may want to create a \{\2\bring_popup "Hot Spare" hot spare\} and/or the LUNs may not be set according to your needs (for example, the number of LUNs, \{\2\bring_popup "RAID Level" RAID Level\}, etc.). Use Module Profile and the Configuration main screen to determine what your current configuration is and make changes as needed. \p\p\1
Associated Tasks \label "configuringat"\0\p\p
For detailed procedures, see the \{\5\goto "configuringrt" Related Topics\} below. \p\p
\{\1 o \0\} Creating drive groups/LUNs: Configuration Application >> RAID Module >> Create LUN \p\p
\{\1 o \0\} Creating hot spare drives: Configuration Application >> RAID Module >> Create Hot Spare \p\p
\{\1 o \0\} Changing drive group/LUN parameters: Configuration Application >> RAID Module >> Modify Group/LUN >> (RAID Level, Group Capacity, Segment Size, Defragment) \p\p
\{\1 o \0\} Deleting drive groups/LUNs or hot spare drives: Configuration Application >> RAID Module >> Delete \p\p
\{\1 o \0\} Saving configuration information: Any Application >> RAID Module >> File >> Save Module Profile \p\p
\{\1 o \0\} Changing a controller's mode: Maintenance/Tuning Application >> Controller Mode >> (Swap Active/Passive or Change To Active/Active) \p\p\1
Related Topics \label "configuringrt"\0\p
\{\3\goto "Changing LUN Parameters Concept" Changing Logical Unit Parameters\} \p
\{\3\goto "Configuration Questions" Common Questions\} \p
\{\3\goto "Configuration Application" Configuration Application\} \p
\{\3\goto "How To Use Create Hot Spare" How To Use Create Hot Spare\} \p
\{\3\goto "How To Use Create LUN" How To Use Create LUN\} \p
\{\3\goto "How To Use Delete" How To Use Delete\} \p
\{\3\goto "How To Use Modify Group/LUN" How To Use Modify Group/LUN\} \p
\{\3\goto "Configuration Restrictions" Restrictions/Cautions\} \p
\{\3\goto "Configuration Troubleshooting" Troubleshooting\}
\p\p
\{\7\goto "configuringtop" Top Of Page\}\p
\keyword "configuration" \keyword "module configuration"

\topic "Failure Types Concept" \p\1
Failure Types \label "failtop" 
\p\p
Fast Find -- \{\5\goto "failat" Associated Tasks\} | \{\5\goto "failrt" Related Topics\}
\p\p\1
What Is It \0\p\p
The storage management software monitors the components in the \{\2\bring_popup "RAID Module" RAID Module\} through the \{\2\bring_popup "Controller" controller\} and reports its operating condition as a status. When a status is NOT Optimal (in its best working state), it indicates that some repair or replacement may be required. It is best to use Recovery Guru/Health Check (in the Recovery Application) to diagnose the problem (it presents results as failure types) and to provide the correct procedure for fixing the failure type reported.
\p\p\1
Associated Tasks \label "failat"\0\p\p
For detailed procedures, see the \{\5\goto "failrt" Related Topics\} below.
\p\p
\{\1 o \0\} Diagnosing component failures: Recovery Application >> Recovery Guru/Health Check
\p\p
\{\1 o \0\} Fixing component failures: Recovery Application >> Recovery Guru/Health Check >> Show Procedure
\p\p
\{\1 o \0\} Viewing component statuses: Any Application >> Module Profile >> Controllers, Drives, or LUNs
\p\p\1
NOTE\0: Module Profile is the quickest way to view component statuses from any application. Statuses are also displayed in the following screens: \p\p
-- Recovery Application >> Options >> Manual Recovery >> Controller Pairs, Drives, or Logical Units
\p\p
-- Configuration Application main screen or List/Locate Drives
\p\p
\{\1 o \0\} Viewing historical information on component problems: Status Application >> Message Log
\p\p\1
Related Topics \label "failrt"\0\p
\{\3\goto "Component Concept" Components\} \p
\{\3\goto "How To Use List/Locate Drives" How To Use List/Locate Drives\} \p
\{\3\goto "How To Use Manual Parity Check/Repair" How To Use Manual Parity Check/Repair\} \p
\{\3\goto "How To Use Message Log" How To Use Message Log\} \p
\{\3\goto "How To Use Module Profile" How To Use Module Profile\} \p
\{\3\goto "How To Use Options >> Manual Recovery" How To Use Options >> Manual Recovery\} \p
\{\3\goto "How To Use Recovery Guru" How To Use Recovery Guru/Health Check\} \p
\{\3\goto "Recovery Guru Restrictions" Restrictions/Cautions\} \p
\{\3\goto "Statuses Concept" Statuses\} \p
\{\3\goto "Viewing Component Statuses" Viewing Component Statuses\} \p
\{\3\goto "When To Use Recovery Guru" When Should I Use Recovery Guru/Health Check?\}
\p\p
\{\7\goto "failtop" Top Of Page\}\p
\keyword "failures" \keyword "status reporting" \keyword "error detection"

\topic "Fibre Channel Concept" \p\1
Fibre Channel \label "fibrecontop" 
\p\p
Fast Find -- \{\5\goto "fibreconat" Associated Tasks\} | \{\5\goto "fibreconwhat" What Happens\} | \{\5\goto "fibreconrt" Related Topics\}
\p\p\1
What Is It \0\p\p
A channel-network hybrid using an active, intelligent interconnection scheme (\{\2\bring_popup "Topology"topology\}) to connect devices. \p\p\1
NOTE:\0 Consult the "Installation and Support Guide" specific to your operating system for details on the types of host adapters, drivers, hubs, and connections tested with the storage management software. \p\p\1
Associated Tasks \label "fibreconat"\0\p\p
Viewing fibre channel controller information: Any Application >> RAID Module >> Module Profile >> Controllers \p\p\1
What Happens \label "fibreconwhat"\0\p\p
If a host system is using a fibre channel connection, the storage management software uses either an \{\2\bring_popup "Arbitrated Loop" arbitrated loop\} or \{\2\bring_popup "Point-to-Point" point-to-point\} connection between the host machine and each \{\2\bring_popup "Controller" controller\} in the RAID Modules. Module Profile >> Controllers reports the controller information relative to this host interface connection.
\p\p\1
Related Topics \label "fibreconrt"\0\p
\{\3\goto "Host Interface Connections Concept" Host Interface Connections\} \p
\{\3\goto "Number And Type Of Controllers In A RAID Module" How Many And What Kind Of Controllers Does A RAID Module Have?\} \p
\{\3\goto "How To Use Module Profile" How To Use Module Profile\} \p
\{\3\goto "Can't De-Select The Fibre Channel File" Troubleshooting\} \p
\{\3\subtopic "Viewing Fibre Channel Controller Information" Viewing Fibre Channel Controller Information\}
\p\p
\{\7\goto "fibrecontop" Top Of Page\}\p
\keyword "fibre channel" \keyword "device connection" \keyword "host interface" \keyword "controller type"

\topic "Viewing Fibre Channel Controller Information" \p\1
Viewing Fibre Channel Controller Information \label "viewfibretop" 
\p\p
Fast Find -- \{\5\goto "viewfibrert" Related Topics\} \p\p\0
Module Profile shows information about the \{\2\bring_popup "Controller" controllers\} and host-interface connection associated with a selected \{\2\bring_popup "RAID Module" RAID Module\}. \p\p
1. Select any Application. \p\p
2. Select a RAID Module >> Module Profile. \p\p
3. Under "Detailed Information," select Controllers. \p\p
"Host Interface" indicates whether the controllers have a \{\2\bring_popup "Parallel SCSI" Parallel SCSI\} connection or a \{\2\bring_popup "Fibre Channel" Fibre Channel\} connection. If a RAID Module has fibre channel controllers, you will find additional information about this host interface. \p\p\1
NOTE:\0 For details of the controller information displayed, select the What Additional Details Can I See? topic in the Related Topics list below. \p\p
4. Exit Module Profile when finished. \p\p\1
Related Topics \label "viewfibrert"\0\p
\{\3\goto "Fibre Channel Concept" Fibre Channel\} \p
\{\3\goto "How To Use File >> Save Module Profile" How To Save A Module Profile\} \p
\{\3\goto "How To Use Module Profile" How To Use Module Profile\} \p
\{\3\goto "What Additional Details Can I See?" What Additional Details Can I See?\}
\p\p
\{\7\goto "viewfibretop" Top Of Page\} \p
\keyword "fibre channel" \keyword "controller information" \keyword "details, controller"

\topic "Firmware Concept" \p\1
Firmware \label "firmwaretop" 
\p\p
Fast Find -- \{\5\goto "firmwareat" Associated Tasks\} | \{\5\goto "firmwarert" Related Topics\}
\p\p\1
What Is It \0\p\p
The storage management software requires a minimum version level of controller \{\2\bring_popup "Firmware" firmware\} to ensure fullest functionality. This firmware contains executable codes for operations on the controller. 
\p\p\1
IMPORTANT \0\p
Both controllers in a \{\2\bring_popup "RAID Module" RAID Module\} should have the same version of controller firmware downloaded. You may also need the latest \{\2\bring_popup "NVSRAM File" NVSRAM\} file, which comes from your Customer Services Representative, especially if you are upgrading to a new major firmware release.
\p\p\1
Associated Tasks \label "firmwareat"\0\p\p
For detailed procedures, see the \{\5\goto "firmwarert" Related Topics\} list below.
\p\p
\{\1 o \0\} Upgrading controller firmware: Maintenance/Tuning Application >> Firmware Upgrade
\p\p
\{\1 o \0\} Viewing a RAID Module's controller firmware version: Any Application >> RAID Module >> Module Profile >> Controllers
\p\p\1
Related Topics \label "firmwarert"\0\p
\{\3\goto "Firmware/NVSRAM Questions" Common Questions\} \p
\{\3\goto "How To Use Firmware Upgrade" How To Use Firmware Upgrade\} \p
\{\3\goto "NVSRAM Concept" NVSRAM\} \p
\{\3\goto "Firmware/NVSRAM Restrictions" Restrictions/Cautions\} \p
\{\3\goto "Firmware/NVSRAM Troubleshooting" Troubleshooting\}
\p\p
\{\7\goto "firmwaretop" Top Of Page\}\p
\keyword "firmware" \keyword "controller firmware"

\topic "Host Interface Connections Concept" \p\1
Host Interface Connections \label "hostinterfacetop" 
\p\p
Fast Find -- \{\5\goto "hostinterfacert" Network Version\} | \{\5\goto "hostinterfacert" Related Topics\}
\p\p\0
There are three basic host connection environments for installing and operating the storage management software. For details on the types of host adapters, drivers, hubs, and connections tested with the storage management software, see the "Installation and Support Guide" specific to your operating system. \p\p\1
Fibre Channel\0 -- A host interface that is a channel-network hybrid using an active, intelligent interconnection scheme (\{\2\bring_popup "Topology"topology \}) to connect devices. The storage management software uses the \{\2\bring_popup "Fibre Channel" fibre channel\} connection between the host machine and each \{\2\bring_popup "Controller" controller\} in the RAID Modules. \p\p\1
Parallel SCSI\0 -- A host interface that uses SCSI Cables over SCSI Buses to connect devices. The storage management software uses the \{\2\bring_popup "Parallel SCSI" SCSI\} connection between the host machine and each controller in the RAID Modules. \p\p\1
NOTE\0: Additionally, the storage management software supports three main configurations of host machines connected via SCSI or fibre channel to the RAID Modules: \{\2\bring_popup "Single-Host Configuration" single-host\}, \{\2\bring_popup "Multi-Host Configuration" multi-host\}, or \{\2\bring_popup "Independent Controller Configuration" independent\} controller configurations. Select the Host-RAID Module Configuration Types Supported topic in the \{\5\goto "hostinterfacert" Related Topics\} list below for more information on these configurations. \p\p\1
Network\0 -- A network connection that uses network servers and cables to connect devices. The storage management software uses the network connection between Remote Management Stations (RMS) (where it is installed) and each controller in the RAID Modules to communicate with the controllers. The RAID Modules may also be connected to host machines (via SCSI or Fibre Channel); however, the RMS has no way to talk with the host's system or to monitor its \{\2\bring_popup "I/O Connection" I/O connection\}. \p\p\1
Related Topics \label "hostinterfacert"\0\p
\{\3\goto "Special Considerations For Using The Networked Version" Are There Special Considerations For Using The Networked Version?\} \p
\{\3\goto "Fibre Channel Concept" Fibre Channel\} \p
\{\3\goto "Host-RAID Module Configuration Types Supported Concept" Host-RAID Module Configuration Types Supported\} \p
\{\3\goto "How To Use Module Profile" How To Use Module Profile\}
\p\p
\{\7\goto "hostinterfacetop" Top Of Page\}\p
\keyword "host interface" \keyword "device connection" \keyword "fibre channel" \keyword "SCSI" \keyword "parallel SCSI" \keyword "networked version" \keyword "independent controller configuration" \keyword "single-host configuration" \keyword "multi-host configuration"

\topic "Host-RAID Module Configuration Types Supported Concept" \p\1
Host-RAID Module Configuration Types Supported \label "hosttypetop" 
\p\p
Fast Find -- \{\5\goto "hosttypesingle" Single-Host\} | \{\5\goto "hosttypemulti" Multi-Host\} | \{\5\goto "hosttypeindp" Independent Controllers\} | \{\5\goto "hosttypeat" Associated Tasks\}
 | \{\5\goto "hosttypert" Related Topics\}
\p\p\1
NOTE\0: The Networked version of the storage management software always sees both \{\2\bring_popup "Controller" controllers\} in a dual-controller \{\2\bring_popup "RAID Module" RAID Module\} regardless of which configuration you have. However, the Networked version is able to tell if the RAID Module it is connected to has an \{\2\bring_popup "Independent Controller Configuration" independent\} controller configuration ONLY if you set this option (with Select Module >> Edit). \p\p
The storage management software supports three main configurations of host machines connected by \{\2\bring_popup "Parallel SCSI" Parallel SCSI\} or \{\2\bring_popup "Fibre Channel" Fibre Channel\} to the RAID Modules: \p\p\4
CAUTION \0\p
No configurations or combinations are supported beyond those described in this section. Furthermore, the software's operation cannot be guaranteed to work as intended/described in the operating-system specific "Installation and Support Guide," the "User Guide," or this online help if other configurations are used. Also, not every operating system supports the \{\2\bring_popup "Multi-Host Configuration" multi-host\} configuration. Be sure to consult the restrictions in the operating-system specific "Installation and Support Guide." \p\p\1
Single-Host Configuration \label "hosttypesingle"\0\p\p
The host machine contains two host adapters, with each host adapter connected to one of the controllers in the RAID Module. The storage management software is installed on the host. The two connections are required for maximum \{\2\bring_popup "RDAC Driver" RDAC\} failover support for \{\2\bring_popup "Redundant Controller Pair" redundant\} controllers. \p\p
This is the recommended configuration of the storage management software. It provides the fullest functionality and complete RDAC failover support with dual controllers. \p\p
Although this configuration also supports RAID Modules that have a single-controller or dual controllers on the same I/O data path, you do NOT have complete RDAC protection with either of these configurations. The host adapter and cable become a single-point of failure and any I/O data \{\2\bring_popup "I/O Connection" connection\} failure could result in the operating system hanging. For the greatest level of I/O protection, provide each controller in a RAID Module with its own host adapter in the host system. \p\p\1
Multi-Host Configuration \label "hosttypemulti"\0\p\p
Two host machines are each connected to both of the controllers in a RAID Module. The storage management software is installed on each host \p\p
Both hosts have complete visibility of both controllers, all I/O connections, and all configured \{\2\bring_popup "Configured Drive Group" drive groups\}/LUNs in a RAID Module, plus \{\2\bring_popup "RDAC Driver" RDAC\} failover support for the \{\2\bring_popup "Redundant Controller Pair" redundant\} controllers. However, in this configuration, you must use caution when performing storage management tasks that need exclusive access. When creating and deleting \{\2\bring_popup "Logical Unit" LUNs\}, be sure you have only ONE configuration session open at a time (from only one host) or the operations could fail. \p\p\1
Independent Controller Configuration \label "hosttypeindp"\0\p\p
Two host machines are connected to a dual-controller RAID Module. One host machine is connected to one controller, and the second host machine is connected to the other controller. The storage management software is installed on each host.\p\p
Each host machine sees the controller and the \{\2\bring_popup "Configured Drive Group" drive groups\}/LUNs that it owns as independent of the other (alternate) controller. That is, each host machine acts as if it is connected to a single-controller RAID Module. No RDAC failover support exists for the controllers. \p\p
Because it is possible to open a Configuration Application from both hosts, be sure that you have only ONE configuration session open at a time (from only one host) when creating or deleting \{\2\bring_popup "Logical Unit" LUNs\} or the operation will fail on one of the hosts. \p\p\1
Associated Tasks \0\label "hosttypeat"\p\p
Indicating independent controller configuration: Any Application >> RAID Module >> Select Module >> Edit \p\p\1
Related Topics \label "hosttypert"\0\p
\{\3\goto "Special Considerations For Using The Independent Controller Configuration" Are There Special Considerations For Using The Independent Controller Configuration?\} \p
\{\3\goto "Host Connection Questions" Common Questions\} \p
\{\3\goto "Component Concept" Components\} \p
\{\3\goto "How To Use Select Module" How To Use Select Module\} \p
\{\3\goto "How To Edit Module Information" How To Edit Module Information\} \p
\{\3\goto "Host Connection Restrictions" Restrictions/Cautions\}
\p\p
\{\7\goto "hosttypetop" Top Of Page\}\p
\keyword "host interface" \keyword "device connection" \keyword "fibre channel" \keyword "SCSI" \keyword "parallel SCSI" \keyword "networked version" \keyword "independent controller configuration" \keyword "single-host configuration" \keyword "multi-host configuration" \keyword "module configuration" \keyword "configuration" \keyword "RDAC"

\topic "LUN Assignment Concept" \p\1
LUN Assignment \label "lunassigntop"
\p\p
Fast Find -- \{\5\goto "lunassignat" Associated Tasks\} | \{\5\goto "lunassignrt" Related Topics\}
\p\p\0
\{\2\bring_popup "Configured Drive Group" Drive groups\}/\{\2\bring_popup "Logical Unit" LUNs\} are assigned to a specific \{\2\bring_popup "Active/Active Controller Pair" active/active\} controller in a \{\2\bring_popup "RAID Module" RAID Module\} when they are created. This assignment is either automatic, or specified using the LUN assignment option when creating the LUNs. When automatic, the first drive group created in a session is assigned to controller A, the second is assigned to controller B, and so on. If you frequently create a single drive group per session, therefore, all the drive groups will be assigned to controller A. You can change this assignment after the drive group is created using the LUN Balancing option. \p\p\1
Exceptions \0\p\p
In a RAID Module with an \{\2\bring_popup "Independent Controller Configuration" independent\} controller configuration, each controller owns only the specific drive groups/LUNs created from the host it is connected to. \p\p
In a RAID Module with either a single controller or an \{\2\bring_popup "Active/Passive Controller Pair" active/passive\} controller pair, the active controller owns all of the drive groups/LUNs. \p\p
When one of these exceptions applies, the options for changing LUN assignment are not available (see the Associated Task list). Remember that a controller must be in the \{\2\bring_popup "Active Controller Mode" Active\} mode in order to own drive groups/LUNs. \p\p\1
Associated Tasks \label "lunassignat"\0\p\p
\{\1 o \0\} Changing assignment when creating LUNs: Configuration Application >> Create LUN >> Options >> LUN Assignment \p\p
\{\1 o \0\} Changing assignment after creating LUNs: Maintenance/Tuning Application >> LUN Balancing \p\p
\{\1 o \0\} Changing controller mode to Active: Maintenance/Tuning Application >> Controller Mode >> Change To Active/Active
\p\p\1
Related Topics \label "lunassignrt"\0\p\p
\{\3\goto "LUN Assignment Questions" Common Questions\} \p
\{\3\goto "Number And Type Of Controllers In A RAID Module" How Many And What Kind Of Controllers Does A RAID Module Have?\} \p
\{\3\goto "How To Use LUN Balancing" How To Use LUN Balancing\} \p
\{\3\goto "LUN Assignment Restrictions" Restrictions/Cautions\} \p
\{\3\goto "LUNs Are Marked As Inaccessible" Logical Units Are Marked As Inaccessible\}
\p\p
\{\7\goto "lunassigntop" Top Of Page\}\p
\keyword "LUN assignment" \keyword "controller, LUNs owned" \keyword "assigning LUNs" \keyword "balancing LUNs" \keyword "exceptions, independent controller configuration"

\topic "NVSRAM Concept" \p\1
NVSRAM \label "nvsramtop" 
\p\p
Fast Find -- \{\5\goto "nvsramat" Associated Tasks\} | \{\5\goto "nvsramrt" Related Topics\}
\p\p\1
What Is It? \0\p\p
The \{\2\bring_popup "NVSRAM File" NVSRAM\} file specifies certain default settings for the controller and comes from your Customer Services Representative.
\p\p\1
IMPORTANT \0\p
Any time you are upgrading from one major \{\2\bring_popup "Firmware" firmware\} release to another (for example, from 2.x to 3.x), you may also need a new NVSRAM file. If you do NOT load the NVSRAM file, certain features of the storage management software may not work.
\p\p\1
Associated Tasks \label "nvsramat"\0\p\p
Downloading NVSRAM files: Maintenance/Tuning Application >> Firmware Upgrade
\p\p\1
Related Topics \label "nvsramrt"\0\p
\{\3\goto "Firmware/NVSRAM Questions" Common Questions\} \p
\{\3\goto "Firmware Concept" Firmware\} \p
\{\3\goto "How To Download A New NVSRAM File" How To Download A New NVSRAM File\} \p
\{\3\goto "Firmware/NVSRAM Restrictions" Restrictions/Cautions\} \p
\{\3\goto "Firmware/NVSRAM Troubleshooting" Troubleshooting\}
\p\p
\{\7\goto "nvsramtop" Top Of Page\}\p
\keyword "NVSRAM"

\topic "Parity Concept" \p\1
Parity \label "paritycontop" 
\p\p
Fast Find -- \{\5\goto "parityat" Associated Tasks\} | \{\5\goto "paritywhat" What Happens\} | \{\5\goto "parityrt" Related Topics\}
\p\p\1
What Is It \0\p
Parity is additional information stored along with the data that allows the \{\2\bring_popup "Controller" controller\} to reconstruct lost data on \{\2\bring_popup "RAID Level" RAID Level\} 3 or 5 \{\2\bring_popup "Logical Unit" logical units\} (LUNs) if a drive fails. (RAID Level 1 does not have parity, although it can still be reconstructed.)
\p\p\1
IMPORTANT \0\p
LUNs/\{\2\bring_popup "Configured Drive Group"drive groups\} must be configured as \{\2\bring_popup "RAID 3" RAID 3\} or \{\2\bring_popup "RAID 5" RAID 5\} for parity to be stored. \{\2\bring_popup "RAID 0" RAID 0\} LUNs do NOT have parity and their data cannot be checked and repaired. \{\2\bring_popup "RAID 1" RAID 1\} uses mirrored data, not parity, to provide redundancy. Data in a RAID 1 LUN CAN be checked and repaired.
\p\p\1
Associated Tasks \label "parityat"\0\p\p
For detailed procedures, see the \{\5\goto "parityrt" Related Topics\} list below.
\p\p
\{\1 o \0\} Automatically checking parity: Maintenance/Tuning Application >> RAID Module >> Options >> Auto Parity Settings
\p\p
\{\1 o \0\} Manually checking parity: Recovery Application >> Manual Parity Check/Repair
\p\p
\{\1 o \0\} Viewing parity messages: Status Application >> Message Log
\p\p\1
What Happens \label "paritywhat"\0\p\p
The storage management software automatically performs a parity \{\2\bring_popup "Parity Check/Repair" check/repair\} operation (if enabled) that helps guarantee data integrity of logical units by scanning and repairing any inconsistent \{\2\bring_popup "Parity" parity\}. You can also manually check/repair parity if desired. Either Parity Check/Repair operation performs the following functions:
\p\p
\{\1 o \0\} Scans optimal RAID 1, 3, and 5 LUNs and checks the parity for each block in the LUN. RAID 1 (striping and mirroring) does not have true parity, but parity check compares data on each mirrored pair, block by block.
\p\p
\{\1 o \0\} Repairs any parity inconsistencies during the parity check. On a RAID 1 LUN, the controller changes the data on the mirror disk to make it match the data on the data disk. In RAID 3 or RAID 5 LUNs, the controller changes the parity so that it is consistent with the data.
\p\p\1
Related Topics \label "parityrt"\0\p
\{\3\goto "Parity Questions" Common Questions\} \p
\{\3\goto "How To Use Manual Parity Check/Repair" How To Manually Check Parity\} \p
\{\3\goto "How To Use Options >> Auto Parity Settings" How To Automatically Check Parity\} \p
\{\3\goto "Parity Message Details" Parity Message Details (Message Log)\} \p
\{\3\goto "Parity Restrictions" Restrictions/Cautions\} \p
\{\3\goto "Parity Troubleshooting" Troubleshooting\} \p
\{\3\goto "Viewing Parity Messages" Viewing Parity Messages\}
\p\p
\{\7\goto "paritycontop" Top Of Page\} \p
\keyword "parity" \keyword "mirrored pair drives"

\topic "Performance Concept" \p\1
Performance \label "performcontop" 
\p\p
Fast Find -- \{\5\goto "performconat" Associated Tasks\} | \{\5\goto "performconrt" Related Topics\}
\p\p\1
What Is It \0\p\p
You can assess the performance of your \{\2\bring_popup "RAID Module" RAID Modules\} in three ways: performing an immediate health check of the components, viewing an historical record of events, or monitoring the system's activity to the controllers and LUNs: \p\p\1
\{\1 o \0\} Recovery Guru/Health Check (Recovery Application)\0 -- You can perform an immediate health check of the components for all or selected RAID Modules. If component failures are detected, the storage management diagnoses the problem and provides step-by-step instructions for each failure type detected that you should use to correct the problem. \p\p\1
\{\1 o \0\} Message Log (Status Application)\0 -- The storage management software has a background monitor that automatically polls all RAID Modules and checks for problems/events at a specified \{\2\bring_popup "Checking Interval" interval\} (default is 5 minutes). If any problems or events are detected, the information is written to the default \{\2\bring_popup "Log File" log\} file. This becomes an historical record of past component failures, general status changes, and configuration changes. \p\p\1
\{\1 o \0\} Performance Monitor (Status Application)\0 -- You can monitor the current performance of the system activity on selected \{\2\bring_popup "Controller" controllers\} and \{\2\bring_popup "Logical Unit" LUNs\} for a selected RAID Module while it is in use. This allows you to gather information that may be useful in evaluating system performance and determining possible methods for improvement. \p\p\1
Associated Tasks \label "performconat"\0\p\p
For detailed procedures, see the \{\5\goto "performconrt" Related Topics\} list below. \p\p
\{\1 o \0\} Diagnosing and fixing component failures: Recovery Application >> Recovery Guru/Health Check >> Show Procedure \p\p
\{\1 o \0\} Monitoring system performance: Status Application >> RAID Module >> Performance Monitor \p\p
\{\1 o \0\} Saving data collected by Performance Monitor: With Performance Monitor running, select File >> Save Performance Data \p\p
\{\1 o \0\} Viewing current component status information: Any Application >> RAID Module >> Module Profile >> Detailed Information (Controllers, Drives, or LUNs) \p\p
\{\1 o \0\} Viewing historical information on component problems: Status Application >> Message Log \p\p\1
Related Topics \label "performconrt"\0\p
\{\3\goto "How To Use Message Log" How To Use Message Log\} \p
\{\3\goto "How To Use Module Profile" How To Use Module Profile\} \p
\{\3\goto "How To Use Performance Monitor" How To Use Performance Monitor\} \p
\{\3\goto "How To Use Recovery Guru" How To Use Recovery Guru/Health Check\} \p
\{\3\goto "Statuses Concept" Statuses\}
\p\p
\{\7\goto "performcontop" Top Of Page\}\p
\keyword "Performance Monitor" \keyword "monitoring performance" \keyword "data performance"

\topic "Reconstruction Concept" \p\1
Reconstruction \label "recontop" 
\p\p
Fast Find -- \{\5\goto "reconat" Associated Tasks\} | \{\5\goto "reconwhat" What Happens\} | \{\5\goto "reconrt" Related Topics\}
\p\p\1
What Is It \0\p\p
\{\2\bring_popup "Reconstruction"Reconstruction\} is the process used to restore a \{\2\bring_popup "Degraded Mode" Degraded\} RAID Level 1, 3, or 5 \{\2\bring_popup "Logical Unit" logical unit\} (LUN) to its original state after you replace a failed drive, or restore data to a \{\2\bring_popup "Hot Spare" hot spare\} drive that has taken over for a failed drive in the drive group.
\p\p\1
Associated Tasks \label "reconat"\0\p\p
For detailed procedures, see the \{\5\goto "reconrt" Related Topics\} list below.
\p\p
\{\1 o \0\} Viewing reconstruction progress: Status Application >> LUN Reconstruction \p\p
\{\1 o \0\} Changing the reconstruction rate:
\p\p
-- For any LUNs: Maintenance/Tuning Application >> LUN Reconstruction Rate >> Save
\p\p
-- For LUNs currently undergoing reconstruction: Status Application >> LUN Reconstruction
\p\p
\{\1 o \0\} Starting reconstruction manually: Recovery Application >> Options >> Manual Recovery >> Drives >> Reconstruct
\p\p\1
What Happens \label "reconwhat"\0\p\p
During reconstruction, the \{\2\bring_popup "Controller" controller\} recalculates data on the replaced/hot spare drive by using data and \{\2\bring_popup "Parity" parity\} from the other drives in the LUN. The controller then writes this data to the replaced/hot spare drive.
\p\p
Reconstruction should start automatically when a hot spare drive takes over for a failed drive or when you physically replace a failed drive in a RAID 1, 3, or 5 logical unit. The drive's \{\2\bring_popup "Fault Lights" fault light\} comes on momentarily at the beginning of reconstruction, but then goes off and the drive \{\2\bring_popup "Activity Lights" activity lights\} flash steadily throughout the reconstruction process.
\p\p\1
Related Topics \label "reconrt"\0\p
\{\3\goto "Manually Starting Reconstruction" Common Questions\} \p
\{\3\goto "How To Change The Reconstruction Rate" How To Change The Reconstruction Rate\} \p
\{\3\goto "How To View Reconstruction Progress" How To View Reconstruction Progress\} \p
\{\3\goto "Reconstruction Restrictions" Restrictions/Cautions\} \p
\{\3\goto "Reconstruction Troubleshooting" Troubleshooting\} \p
\{\3\goto "What Are The Rate Settings?" What Are The Reconstruction Rate Settings?\}
\p\p
\{\7\goto "recontop" Top Of Page\}\p
\keyword "reconstruction" \keyword "data recovery" \keyword "activity lights"

\topic "Selecting RAID Modules Concept" \p\1
Selecting RAID Modules \label "smodconcepttop"\p\p
Fast Find -- \{\5\goto "smodconceptrt" Related Topics\}
\0\p\p
You perform all tasks (for example, performing a firmware upgrade or creating logical units) on a \{\2\bring_popup "RAID Module" RAID Module\}. Select a RAID Module BEFORE selecting the option you wish to perform. You select a specific RAID Modules in one of two ways:
\p\p
\{\1 o \0\} Use the Drop-Down List at the far left of the tool bar area just below the top menu options in each application's main screen; OR
\p\p
\{\1 o \0\} Choose the Select Module option (available from any application) for a more detailed list of all RAID Modules. Highlight a module and select OK to make that module the default for performing the application's tasks.
\p\p\1
What Happens \0\p\p
The following are common to all applications, except where noted: \p\p
\{\1 o \0\} Any options or tasks you perform will apply to the RAID Module you select.
\p\p
\{\1 o \0\} Appropriate information for the selected RAID Module is provided in the various options (such as Module Profile).
\p\p
\{\1 o \0\} In the Configuration Application, configuration information for the selected RAID Module is displayed. You can only receive information for one module at a time in this application.
\p\p
\{\1 o \0\} In all applications except Configuration, a screen appears instructing you to select an option.
\p\p
\{\1 o \0\} When you select a RAID Module a second time (when it is currently displayed in the RAID Module selection box), the component statuses are updated. However, you are returned to a blank screen and prompted to select one of the application's tasks.
\p\p\1
Related Topics \0\label "smodconceptrt"\p
\{\3\goto "How To Use Select Module" How To Use Select Module\} \p
\{\3\goto "How To Use Module Profile" How To Use Module Profile\}
\p\p
\{\7\goto "smodconcepttop" Top Of Page\}\p
\keyword "selecting modules" \keyword "module selection" \keyword "screen update" \keyword "update screen" \keyword "update statuses"

\topic "Statuses Concept" \p\1
Statuses \label "statustop" 
\p\p
Fast Find -- \{\5\goto "statusat" Associated Tasks\} | \{\5\goto "statusrt" Related Topics\}
\p\p\1
What Is It \0\p\p
The storage management software monitors the \{\2\bring_popup "RAID Module" RAID Module\} components through the \{\2\bring_popup "Controller" controller\} and reports their statuses. When a component status is NOT Optimal (in its best working state), some repair or replacement of that component may be required. If you see a component status other than Optimal, you should use Recovery Guru/Health Check (in the Recovery Application) to diagnose the problem. Recovery Guru identifies the failure type and provides the correct procedure for fixing it.
\p\p\1
Associated Tasks \label "statusat"\0\p\p
For detailed procedures, see the \{\5\goto "statusrt" Related Topics\} list below.
\p\p
\{\1 o \0\} Diagnosing component failures: Recovery Application >> Recovery Guru/Health Check
\p\p
\{\1 o \0\} Fixing component failures: Recovery Application >> Recovery Guru/Health Check >> Show Procedure
\p\p
\{\1 o \0\} Viewing component statuses: Any Application >> RAID Module >> Module Profile >> Controllers, Drives, or LUNs
\p\p\1
NOTE\0: Module Profile is the quickest way to view component statuses from any application. Statuses are also displayed in the following screens:
\p\p
-- Recovery Application >> Options >> Manual Recovery >> Controller Pairs, Drives, or Logical Units
\p\p
-- Configuration Application main screen or List/Locate Drives
\p\p
\{\1 o \0\} Viewing historical information on component problems: Status Application >> Message Log
\p\p\1
Related Topics \label "statusrt"\0\p
\{\3\goto "Firmware Upgrade Results" Firmware Upgrade Results\} \p
\{\3\goto "How To Use Module Profile" How To Use Module Profile\} \p
\{\3\goto "How To Use Recovery Guru" How To Use Recovery Guru/Health Check\} \p
\{\3\subtopic "Possible Controller Statuses" Possible Controller Statuses\} \p
\{\3\subtopic "Possible Drive Statuses" Possible Drive Statuses\} \p
\{\3\subtopic "Possible LUN Statuses" Possible Logical Unit Statuses\} \p
\{\3\subtopic "Updating Component Statuses" Updating Component Statuses\} \p
\{\3\subtopic "Viewing Component Statuses" Viewing Component Statuses\}
\p\p
\{\7\goto "statustop" Top Of Page\}\p
\keyword "status reporting" \keyword "component details" \keyword "error detection"

\topic "Possible Controller Statuses" \p\1
Possible Controller Statuses \label "ctrlstattop" 
\p\p
Fast Find -- \{\5\goto "ctrlstatrt" Related Topics\}
\p\p\0
In most cases, you should use Recovery Guru/Health Check (Recovery Application) when you have a problem with any \{\2\bring_popup "Controller" controller\} in a RAID Module. The possible controller statuses are: \p\p\1
Dead \0 -- There is a problem on the I/O data connection (interface cable/terminator, network card, controller, or host adapter). Select Recovery Guru/Health Check >> Show Procedure and follow the step-by-step procedure provided to correct the problem. \p\p\1
Inaccessible \0 -- The current host machine cannot access this controller (most likely because the RAID Module has an \{\2\bring_popup "Independent Controller Configuration" independent controller\} configuration). \p\p\1
Offline \0 -- The controller is not receiving/accepting I/O. Either it has been manually placed \{\2\bring_popup "Offline Controller Mode" offline\} or the \{\2\bring_popup "RDAC Driver" driver\} for redundant software support has placed it offline. If you did NOT manually place the controller offline, it may need to be replaced. Select Recovery Guru/Health Check >> Show Procedure and follow the step-by-step procedure provided to correct the problem. \p\p\1
Optimal \0 -- The controller is functioning normally. 
\p\p\1
Related Topics \label "ctrlstatrt"\0\p
\{\3\goto "Number And Type Of Controllers In A RAID Module" How Many And What Kind Of Controllers Does A RAID Module Have?\} \p
\{\3\goto "How To Use Manual Recovery >> Controller Pairs" How To Use Manual Recovery >> Controller Pairs\} \p
\{\3\goto "How To Use Recovery Guru" How To Use Recovery Guru/Health Check\} \p
\{\3\goto "Host-RAID Module Configuration Types Supported Concept" Host-RAID Module Configuration Types Supported\}
\p\p
\{\7\goto "ctrlstattop" Top Of Page\}\p
\keyword "RDAC" \keyword "controller statuses" \keyword "status reporting" \keyword "Inaccessible" \keyword "details, controller"

\topic "Possible Drive Statuses" \p\1
Possible Drive Statuses \label "drvstattop"\p\p
Fast Find -- \{\5\goto "drvstatrt" Related Topics\} \p\p\0
Any status other than Optimal means that the drive is NOT functioning normally. In most cases, you should use Recovery Guru/Health Check when you see a non-Optimal drive status. There are several possible drive statuses: \p\p\1
Failed \0 -- The drive has failed and is no longer functioning. Replace the drive as soon as possible. \p\p\1
Mismatch \0 -- The \{\2\bring_popup "Controller" controller\} has sensed that the drive has some parameters different than expected, such as sector size, \{\2\bring_popup "SCSI Channel" SCSI Channel\}, or \{\2\bring_popup "SCSI ID" ID\}. \p\p\1
Offline \0 -- The drive has been placed Offline because data \{\2\bring_popup "Reconstruction" reconstruction\} failed and a read error occurred for one or more drives in the logical unit (LUN). The affected LUN is \{\2\bring_popup "Dead Mode" Dead\}, and all the drives are probably either Failed or Offline. Use Recovery Guru to diagnose the problem and select Show Procedure for step-by-step instructions to correct it. \p\p\1
Optimal \0 -- The drive is functioning normally. \p\p\1
Replaced \0 -- The drive has been replaced, is being formatted, or is reconstructing. \p\p\1
Spare/In-Use \0 -- The drive is configured as a \{\2\bring_popup "Hot Spare" hot spare\} drive and is currently in use; that is, it is covering for a failed drive in a configured drive group/LUN. (If you are using List/Locate Drives in the Configuration Application to view the hot spare drive group, you see In Use instead.) \p\p\1
Spare-Stdby/Standby \0 -- The drive is configured as a hot spare drive and is currently NOT in use. (If you are using List/Locate Drives in the Configuration Application to view the hot spare drive group, you see Standby instead.) \p\p\1
Unresponsive \0 -- The controller is unable to communicate with the drive. This can occur for \{\2\bring_popup "Unassigned Drive Group" unassigned\} drives or those that are \{\2\bring_popup "Configured Drive Group" configured\} in LUNs. Use Recovery Guru to diagnose the problem and select Show Procedure for step-by-step instructions to correct it. \p\p\1
Wrong Drive \0 -- You placed a new drive in the wrong drive location and the LUN status is Dead. The drive you removed was \{\2\bring_popup "Optimal Mode" Optimal\} and you still have a Failed drive. Applicable only if you have a RAID Module with a controller version earlier than the Series 3. 
\p\p\1
Related Topics \label "drvstatrt"\0\p
\{\3\goto "How To Use Manual Recovery >> Drives" How To Use Manual Recovery >> Drives\} \p
\{\3\goto "How To Use Recovery Guru" How To Use Recovery Guru/Health Check\}
\p\p
\{\7\goto "drvstattop" Top Of Page\}\p
\keyword "drive statuses" \keyword "status reporting" \keyword "details, drive"

\topic "Possible LUN Statuses" \p\1
Possible Logical Unit Statuses \label "lunstattop" 
\p\p
Fast Find -- \{\5\goto "lunstatrt" Related Topics\} \p\p\0
Any status other than \{\2\bring_popup "Optimal Mode" Optimal\} means that the LUN is NOT functioning normally. In most cases, you should use Recovery Guru/Health Check when you see a non-Optimal logical unit (LUN) status. 
\p\p\4
CAUTION \0\p
You should not rely ONLY on LUN status information to determine if a recovery procedure is necessary. For example, if you have \{\2\bring_popup "Hot Spare" hot spares\} configured for a RAID Module and a drive fails, the hot spare takes over for the failed drive, and LUN status remains Optimal. Therefore, any time you see a non-Optimal drive status, select Recovery Guru and follow the step-by-step procedure provided to correct the problem.
\p\p
There are several possible LUN statuses: \p\p\1
Dead \0 -- Two or more drives have failed in the same \{\2\bring_popup "Configured Drive Group" drive group\}, or one or more drives have failed in a \{\2\bring_popup "RAID 0" RAID 0\} drive group. The \{\2\bring_popup "Logical Unit" LUN\} is no longer functioning. Furthermore, all the LUNs in the drive group are Dead also. This is the most serious status a LUN can have and you have probably lost all data on the affected LUNs. \p\p\1
Degraded \0 -- A single drive has failed on a \{\2\bring_popup "RAID Level" RAID Level\} 1, 3, or 5 LUN and the LUN is now functioning in a degraded mode. You can still access your data; however, you should use Recovery Guru to replace the failed drive as soon as possible. \p\p\1
NOTE\0: In a \{\2\bring_popup "RAID 1" RAID 1\} LUN, more than one drive can fail and the LUN remain Degraded, so long as the two drives are NOT in a \{\2\bring_popup "Mirrored Pair Drives" mirrored pair\}. If both drives in a mirrored pair fail, the LUN will have a Dead status. \p\p\1
Formatting \0 -- The LUN is not available because it is being formatted. \p\p\1
Inaccessible \0 -- The LUN is not available because it is part of a drive group owned by the alternate controller in an \{\2\bring_popup "Independent Controller Configuration" independent\} controller RAID Module. It cannot be accessed using this software from the current host. \p\p\1
NOTE\0: If you have moved the RAID Module from another host machine system to one that supports fewer configured LUNs, this status could also indicate that the new host cannot access the LUNs marked Inaccessible. For example, this could occur if a RAID Module was connected to a host system that was able to support 32 configured LUNs, but was moved to a new host system that only supports 8 LUNs. In this case, LUNs 8-31 would be seen as Inaccessible. Consult the "Installation and Support Guide" specific to your operating system (OS) for information on the number of LUNs supported by your host and OS. \p\p\1
Locked \0 -- The LUN is not available because an operation has obtained exclusive access to it (such as LUN creation). Wait for the operation to finish and the status to transition back to Optimal. \p\p\1
Optimal \0 -- The LUN is functioning normally. \p\p\1
Reconstructing \0 -- The controller is currently \{\2\bring_popup "Reconstruction" reconstructing\} one or more drives on the LUN.
\p\p\1
Related Topics\0\label "lunstatrt"\p
\{\3\subtopic "Do Hot Spares Affect LUN Statuses?" Do Hot Spare Drives Affect Logical Unit Statuses?\} \p
\{\3\goto "How To Use Manual Recovery >> LUNs" How To Use Manual Recovery >> Logical Units\} \p
\{\3\goto "How To Use Recovery Guru" How To Use Recovery Guru/Health Check\}
\p\p
\{\7\goto "lunstattop" Top Of Page\}\p
\keyword "LUN statuses" \keyword "status reporting" \keyword "details, LUN" \keyword "independent controller configuration" \keyword "Inaccessible" \keyword "mirrored pair drives"

\topic "Do Hot Spares Affect LUN Statuses?" \p\1
Do Hot Spare Drives Affect Logical Unit Statuses? \label "lunstathstop" 
\p\p
Fast Find -- \{\5\goto "lunstathsrt" Related Topics\}
\p\p\0
If you have \{\2\bring_popup "Hot Spare" hot spares\} configured for a \{\2\bring_popup "RAID Module" RAID Module\}, then the hot spare contains no data and acts as a standby in case a drive fails in a RAID 1, 3, or 5 \{\2\bring_popup "Logical Unit" LUN\}. This does not affect the drive statuses you see, but could affect the LUN status that the software displays. Depending on how many hot spares you have configured, a LUN could remain \{\2\bring_popup "Optimal Mode" Optimal\} and still have several failed drives (each one being covered by a hot spare). \p\p\1
Logical Unit Statuses With Hot Spares \0\p\p
The following LUN status examples are based on having one hot spare configured in a RAID Module. \p\p\1
Optimal \0 -- A single drive has failed in a \{\2\bring_popup "RAID Level" RAID Level\} 1, 3, or 5 logical unit and a hot spare takes over for it. The LUN continues to function normally. Checking drive statuses, you see Failed for the failed drive and Spare for the hot spare drive that is in use. \p\p\1
Degraded \0 -- Could mean one of two things: \p\p
\{\1 o \0\} The hot spare has failed. The LUN now has a single failed drive and is functioning in the \{\2\bring_popup "Degraded Mode" Degraded\} mode. You can still access your data; however, you should replace the failed drives as soon as possible. Checking drive statuses, you see Failed for the original failed drive and Hot Spare Failed for the hot spare drive.
\p\p
\{\1 o \0\} A second drive has failed while a hot spare covers for the first failed drive. The LUN is now functioning in a Degraded mode. You can still access your data; however, you should replace the failed drives as soon as possible. Checking drive statuses, you see Failed for both failed drives and Spare for the hot spare drive that is in use. \p\p\1
Dead \0 -- Two or more drives have failed in addition to the one the hot spare is replacing. The LUN is no longer functioning; furthermore, all of the LUNs in the \{\2\bring_popup "Configured Drive Group" drive group\} are \{\2\bring_popup "Dead Mode" Dead\} also. This is the most serious status a logical unit can have and you will lose data. Checking drive statuses, you see Failed for each failed drive. \p\p\1
Related Topics \label "lunstathsrt"\0\p
\{\3\goto "How Many Hot Spare Drives Can I Configure?" How Many Hot Spare Drives Can I Configure?\} \p
\{\3\goto "How To Use Recovery Guru" How To Use Recovery Guru/Health Check\} \p
\{\3\goto "Possible LUN Statuses" Possible Logical Unit Statuses\}
\p\p
\{\7\goto "lunstathstop" Top Of Page\}\p
\keyword "status reporting" \keyword "hot spare" \keyword "LUN statuses"

\topic "Updating Component Statuses" \p\1
Updating Component Statuses \label "updatestattop" 
\p\p
Fast Find -- \{\5\goto "updatestatrt" Related Topics\}
\p\p\0
If you want to update component statuses quickly, you can re-select the \{\2\bring_popup "RAID Module" RAID Module\} currently displayed in the RAID Module Selection Box. You are returned to a blank screen and prompted to select one of the application's tasks. Also, any time the software detects a configuration change that affects a component's status, you see a "Configuration change detected" message, then the updated status information.
\p\p
The storage management software monitors the components in the RAID Module through the \{\2\bring_popup "Controller" controller\} and reports their operating condition as statuses. This background monitor automatically polls all RAID Modules at a specified \{\2\bring_popup "Checking Interval" interval\} (default is 5 minutes). If any problems or events are detected, the status information is displayed on the screen and written to the default \{\2\bring_popup "Log File" log file\} (Status Application >> Message Log).
\p\p
When a status is NOT Optimal (in its best working state), it indicates that some repair or replacement may be required. If you see a component status other than Optimal for a controller, drive, or \{\2\bring_popup "Logical Unit" LUN\}, it is best to use Recovery Guru/Health Check (in the Recovery Application) to diagnose the problem. Recovery Guru identifies the failure types and provides the correct procedure for fixing it.
\p\p\1
Related Topics \label "updatestatrt"\0\p
\{\3\goto "Component Concept" Component\} \p
\{\3\goto "How To Use Message Log" How To Use Message Log\} \p
\{\3\goto "How To Use Recovery Guru" How To Use Recovery Guru/Health Check\} \p
\{\3\goto "Selecting RAID Modules Concept" Selecting RAID Modules\} \p
\{\3\goto "Statuses Concept" Statuses\}
\p\p
\{\7\goto "updatestattop" Top Of Page\}\p
\keyword "status reporting" \keyword "update statuses" \keyword "component details" \keyword "screen update"

\topic "Viewing Component Statuses" \p\1
Viewing Component Statuses \label "viewstattop" 
\p\p
Fast Find -- \{\5\goto "viewnote" Notes\} | \{\5\goto "viewhist" View Historical\} | \{\5\goto "viewstatrt" Related Topics\}
\p\p\0
The quickest method for viewing component statuses on a selected \{\2\bring_popup "RAID Module" RAID Module\} is to use Module Profile (from any application) and view the component's detailed information.
\p\p
To ensure that the latest problems are diagnosed, it is best to use Recovery Guru/Health Check (in the Recovery Application). Recovery Guru identifies the problem (it presents appropriate failure types) and provides the correct procedure to follow for fixing it.
\p\p
For historical data, use Status Application >> Message Log.
\p\p\1
Viewing Current (Real-Time) Statuses \0\p\p
1. From any application, select a single RAID Module.
\p\p
Remember, the Module Profile option is grayed out if you select All RAID Modules. 
\p\p
2. Select Module Profile >> Controllers, Drives, or LUNs.
\p\p
3. Exit Module Profile when finished.
\p\p\1
Notes \0\label "viewnote"\p\p
\{\1 o \0\} \{\2\bring_popup "Controller" Controller\} statuses are also displayed in the Recovery Application >> RAID Module >> Options >> Manual Recovery >> Controller Pairs. Controller \{\2\bring_popup "Controller Mode" modes\} are displayed in Maintenance/Tuning Application >> Controller Mode.
\p\p
\{\1 o \0\} Drives statuses are also displayed in (a) the Recovery Application >> RAID Module >> Options >> Manual Recovery >> Drives, or (b) the Configuration Application main screen or by selecting List/Locate Drives.
\p\p
\{\1 o \0\} \{\2\bring_popup "Logical Unit" Logical unit\} statuses are also displayed in (a) Recovery Application >> RAID Module >> Options >> Manual Recovery >> Drives or Logical Units, or (b) Configuration Application main screen. \p\p\1
Viewing Historical Component Information \0\label "viewhist"\p\p
The Message Log formats the actual \{\2\bring_popup "Log File" log file\} data to display historical information of the different events for the selected RAID Module. Use Message Log (Status Application) to view specific information for a RAID Module when you have been notified that a component failure has occurred, if either you or Automatic Parity Check/Repair have run a parity \{\2\bring_popup "Parity Check/Repair" check/repair\}, or whenever you are aware of a general status change.
\p\p
This Message Log message can help you identify when (date/time) the event was detected, which RAID Module and controller are affected, and what type of event has occurred, plus any relevant code data.
\p\p\1
Related Topics \label "viewstatrt"\0\p
\{\3\goto "Component Concept" Component\} \p
\{\3\goto "How To Use Message Log" How To Use Message Log\} \p
\{\3\goto "How To Use Module Profile" How To Use Module Profile\} \p
\{\3\goto "How To Use Recovery Guru" How To Use Recovery Guru/Health Check\} \p
\{\3\goto "Statuses Concept" Statuses\}
\p\p
\{\7\goto "viewstattop" Top Of Page\}\p
\keyword "status reporting" \keyword "view statuses" \keyword "component details"

\topic "Common Task Topics" \p\1
Common Tasks Available In All Applications \label"commontop"
\p\p
Fast Find -- \{\5\goto "commonproc" Procedures\} | \{\5\goto "commonrt" Related Topics\}
\p\p\1
Task Summary \0\p\p
The following tasks are available from all applications on the tool bar or from the Options menu:
\p\p\1
\{\1 o \} File >> Save Module Profile \0 -- save profile information to a file ONLY for the selected RAID Module
\p\p\1
\{\1 o \} Select Module \0 -- select or find a specific RAID Module; add or remove RAID Modules; or edit the information (module name and comments) about a RAID Module
\p\p\1
\{\1 o \} Locate Module \0 -- flash the drive activity or drive fault lights (depending on the controller type) to identify the selected RAID Module
\p\p\1
\{\1 o \} Module Profile \0 -- display specific details about the controllers, drives, or LUNs for the selected RAID Module
\p\p\1
Procedures \0\label "commonproc"
\p\p
\{\3\subtopic "How To Use File >> Save Module Profile" How To Save A Module Profile\}
\p\p
\{\3\subtopic "How To Use Locate Module" How To Use Locate Module\}
\p\p
\{\3\subtopic "How To Use Module Profile" How To Use Module Profile\}
\p\p
\{\3\subtopic "How To Use Online Help" How To Use Online Help\}
\p\p
\{\3\subtopic "How To Use Select Module" How To Use Select Module\}
\p\p\1
Related Topics \0\label "commonrt" \p
\{\3\goto "Concept Topics" Concepts\} \p
\{\3\goto "Common Question Topics" Common Questions\} \p
\{\3\goto "Procedure Topics" Procedures\} \p
\{\3\goto "Restriction/Caution Topics" Restrictions/Cautions\} \p
\{\3\goto "Troubleshooting Topics" Troubleshooting\}
\p\p
\{\7\goto "commontop" Top Of Page\} \p
\keyword "common tasks" \keyword "summary of tasks" \keyword "tasks, available in all applications" \keyword "task summary" \keyword "Save Module Profile" \keyword "Select Module" \keyword "Locate Module" \keyword "Module Profile"

\topic "How To Use File >> Save Module Profile" \p\1
How To Save A Module Profile \label "sprofiletop"
\p\p
Fast Find -- \{\5\goto "sprofileimp" Important Notes\} | \{\5\goto "sprofilestep" Procedure\} | \{\5\goto "sprofilert" Related Topics\}
\p\p\1
When To Use \0\p\p
Saving profile information copies the information found in Module Profile and the Configuration Application main screen to a file for your reference. It does not, however, copy configuration information that you could later use to restore your module. Also, it saves information ONLY for the selected RAID Module. You may want to save the profile to a file:
\p\p
\{\1 o \0\} When you want a copy for quick reference
\p\p
\{\1 o \0\} If you want a permanent record
\p\p
\{\1 o \0\} To send information to your Customer Services Representative for troubleshooting
\p\p\1
Important Notes\0\label "sprofileimp"\p\p
It is very important that you save the profile of each RAID Module during initial installation and any time you change your configuration. You can use this information as a reference if you need to perform any recovery or maintenance tasks.
\p\p
If you select All RAID Modules, this option is grayed out.
\p\p
If you select or enter a filename that already exists, selecting OK overwrites the existing data in that file.
\p\p
If you are in Module Profile, the Save Module Profile option is unavailable until you close that screen.
\p\p\1
Procedure \0\label "sprofilestep"\p\p
1. Exit Module Profile (Select OK).
\p\p
2. From the top menu, select File >> Save Module Profile.
\p\p
3. At the Save Module Profile screen, choose either All, Controller Information, Drive Information, LUN Information, or Configuration Information.
\p\p
4. At the second Save Module Profile screen, enter the filename where you want this profile stored.
\p\p
In UNIX systems, you can use the filter to direct the save to a specific directory, filename, and file extension.
\p\p
5. Select OK to save the profile to the selected file.
\p\p\1
NOTE\0: Once you have saved the file, you can print it using the printer utility available on your system.
\p\p\1
Related Topics \0\label "sprofilert"\p
\{\3\goto "How To Use Module Profile" How To Use Module Profile\} \p
\{\3\goto "Module Profile Restrictions" Restrictions/Cautions\} \p
\{\3\goto "Module Profile Troubleshooting" Troubleshooting\}
\p\p
\{\7\goto "sprofiletop" Top Of Page\}\p
\keyword "save" \keyword "File menu" \keyword "module information" \keyword "component details" \keyword "printing"

\topic "How To Use Locate Module" \p\1
How To Use Locate Module \label "lmodtop"
\p\p
Fast Find -- \{\5\goto "lmodproc" Procedure\} | \{\5\goto "lmodrt" Related Topics\}
\p\p\1
Important Notes \0\p\p
\{\1 o \0\} For best results on RAID Modules with Series 3 controllers or earlier, perform this task when no I/O activity is occurring on the selected \{\2\bring_popup "RAID Module" RAID Module\} so that the flashing of the drive \{\2\bring_popup "Activity Lights" activity lights\} can be distinguished from normal I/O activity (Series 4 controllers blink the drive \{\2\bring_popup "Fault Lights" fault lights\} instead of the drive activity lights).
\p\p
\{\1 o \0\} On a RAID Module with Series 3 controllers (or earlier), the activity lights on the drive canisters flash sequentially one-at-a-time until you select Stop. On a RAID Module with Series 4 controllers, the drive fault lights flash instead of the drive activity lights (all the lights flash simultaneously). Some RAID Modules also have a summary activity indicator light that flashes.
\p\p
\{\1 o \0\} Any drives with a status other than Optimal are skipped (that is, the activity or fault light does NOT flash).
\p\p\1
Procedure \0\label "lmodproc"\p\p
1. From any application, select a single RAID Module >> Locate Module.
\p\p
Remember, the Locate Module option is grayed out if you select All RAID Modules.
\p\p
2. From the new window, select Start.
\p\p
The activity or fault lights on the drive canisters flash until you select Stop. You can select Cancel instead without changing any module settings or executing any operation.
\p\p
3. \{\2\bring_popup "Label" Label\} the module for future reference.
\p\p
4. When finished, select Stop.
\p\p\1
NOTE\0: If you want to locate specific drives within a drive group, use the List/Locate Drives option in the Configuration Application.
\p\p\1
Related Topics \label "lmodrt"\p
\{\3\goto "Locate Module Restrictions" Restrictions/Cautions\} \p
\{\3\goto "Locate Module Troubleshooting" Troubleshooting\}
\p\p
\{\7\goto "lmodtop" Top Of Page\} \p
\keyword "modules, locating" \keyword "finding modules" \keyword "Locate Module" \keyword "Module menu" \keyword "activity lights" \keyword "identifying modules" \keyword "lights"

\topic "How To Use Module Profile" \p\1
How To Use Module Profile \label "mprofiletop"
\p\p
Fast Find -- \{\5\goto "mprofilestep" Procedure\} | \{\5\goto "mprofilert" Related Topics\}
\p\p\1
When To Use \0\p\p
Use to find specific details about the components (controllers, drives, or logical units) in the selected RAID Module. This profile can help you identify:
\p\p
\{\1 o \0\} Which logical units are assigned to which controllers in the RAID Module
\p\p
\{\1 o \0\} Manufacturing details about the controller, including its type and firmware version
\p\p
\{\1 o \0\} Specifics about the drives, including location, status, and manufacturing details
\p\p
\{\1 o \0\} Logical unit (LUN) parameter settings 
\p\p\1
Procedure \0\label "mprofilestep"\p\p
1. Select any Application.
\p\p
2. Select RAID Module >> Module Profile.
\p\p
Remember, the Module Profile option is grayed out if you select All RAID Modules.
\p\p
While viewing the module profile, you can select Controllers, Drives, or Logical Units for more detailed information. Also, you can select Cancel without changing any module settings or executing any operation.
\p\p
3. Exit Module Profile when finished.
\p\p
After exiting, you can save the profile to a specific file if desired using File >> Save Module Profile.
\p\p\1
Related Topics \0\label "mprofilert"\0\p
\{\3\goto "How To Use File >> Save Module Profile" How To Save A Module Profile\} \p
\{\3\goto "Module Profile Restrictions" Restrictions/Cautions\} \p
\{\3\goto "Module Profile Troubleshooting" Troubleshooting\} \p
\{\3\subtopic "What Additional Details Can I See?" What Additional Details Can I See?\} \p
\{\3\subtopic "Information In Module Profile" What Information Appears In Module Profile?\}
\p\p
\{\7\goto "mprofiletop" Top Of Page\}\p
\keyword "status reporting" \keyword "Module Profile" \keyword "view module information" \keyword "Module menu"

\topic "What Additional Details Can I See?" \p\1
What Additional Details Can I See? \label "mprofileaddtop"\p\p
Fast Find -- \{\5\goto "mprofilectrl" Controllers\} | \{\5\goto "mprofiledrv" Drives\} | \{\5\goto "mprofilelun" LUNs\} | \{\5\goto "mprofileaddrt" Related Topics\}
\p\p\0
From the Module Profile screen, you can select an option under Detailed Information to view more details for three components: controllers, drives, or logical units.
\p\p\1
CONTROLLER DETAILED INFORMATION \label "mprofilectrl"\p\p
When To Use \0 -- You may want to view this information as a reference if you need to perform any maintenance or troubleshooting procedures. For example, if you want to identify a controller's firmware level, cache size, or would like to know its serial number and date of manufacture.
\p\p\1
Board Name\0: Controller type designation \p\p\1
Board ID\0: Controller model number (3601, 3201, etc.) \p\p\1
Board Serial Number\0: Unique identification for the controller assigned by the manufacturer \p\p\1
Product ID\0: Controller manufacturer's product code \p\p\1
Product Serial Number\0: Usually the same as Board Serial Number \p\p\1
Vendor ID\0: Controller manufacturer's name \p\p\1
Date of Manufacture\0: Date controller was assembled \p\p\1
Product Revision\0: A manufacturer's code giving the revision number of the controller
\p\p\1
Host Interface\0: Displays the type of the controller's connection to the host machine, either \{\2\bring_popup "Parallel SCSI" Parallel SCSI\} or \{\2\bring_popup "Fibre Channel" Fibre Channel\} \p\p\1
For Parallel SCSI host interfaces only -- \p\p
Host-Side ID (dec)\0: The host ID switch \{\2\bring_popup "Host-Side ID" setting\} on the back of the controller identifying the bus connection between the controller and the host. (Not applicable for the Networked version; you see this entry only for controllers with a Parallel SCSI or Fibre Channel host interface). \p\p\1
For Fibre Channel host interfaces only \label "ctrlfibre"\0 --\p\p\1
Topology\0: Type of fibre channel network that the controller is attached to: \{\2\bring_popup "Point-to-Point" Point-to-Point\}, \{\2\bring_popup "Fabric" Fabric\}, \{\2\bring_popup "Arbitrated Loop" Arbitrated Loop\}, or Unknown \p\p\1
Controller ID - NL_Port (hex)\0: The controller's \{\2\bring_popup "Controller ID - NL_Port" ID\}. Its hexadecimal format varies depending on the \{\2\bring_popup "Topology" topology\} \p\p\1
Preferred Address - AL_PA (hex)\0: The \{\2\bring_popup "Hard Address" hard address\} (AL_PA format) that the controller attempts to acquire. Displayed only for controllers attached on Arbitrated Loops. If the hard address is not available, the controller automatically obtains the first address available after the other ports on the loop have obtained their hard addresses.\p\p\1
Preferred Loop ID (dec)\0: The fibre channel \{\2\bring_popup "Loop ID" Loop ID\} in NVSRAM used to determine the \{\2\bring_popup "Preferred Address AL_PA" Preferred Address\} - AL_PA (hard address). Displayed only for controllers attached on Arbitrated Loops. This ID is NOT the AL_PA, but an index into a table of valid AL_PA values. \p\p\1
Host-Side ID (dec)\0: The host ID switch \{\2\bring_popup "Host-Side ID" setting\} on the back of the controller identifying the bus connection between the controller and the host \p\p\1
Worldwide Port Name (hex)\0: An 8-byte hexadecimal value used to uniquely identify the controller \p\p\1
Physical Connection\0: The type of fibre channel connection, either copper or optical \p\p\1
Link Speed (MB/sec)\0: The speed in megabytes per second (MB/sec) of the fibre channel connection
\p\p\1
Firmware Related Details -- \p\p
Boot Level\0: Number indicating the release version of the controller \{\2\bring_popup "Boot Level" bootware\} \p\p\1
Firmware Level\0: Number indicating the release version of the controller \{\2\bring_popup "Firmware Level" appware\} \p\p\1
Fibre Channel Level\0: Number indicating the release version of the fibre channel controller \{\2\bring_popup "Fibre Channel Level" firmware\} \p\p\1
Cache/Processor Size (MB)\0: Amount (in megabytes) of total available \{\2\bring_popup "Cache Memory" cache\} memory and \{\2\bring_popup "Processor Memory" processor\} memory on the controller
\p\p\1
DRIVE DETAILED INFORMATION \0\label "mprofiledrv"\p\p\1
When To Use \0 -- You may want to view this information as a reference if you need to perform any maintenance or troubleshooting procedures. For example, if you want to identify a drive's location or capacity, or would like to know its serial number. \p\p\1
Location\0: Designation indicating the location of the drive in the selected RAID Module corresponding to its \{\2\bring_popup "SCSI Channel" channel\} number and \{\2\bring_popup "SCSI ID" SCSI ID\}, where the channel number is always listed first. Use the location information to match it to a physical drive and to help locate it in the RAID Module. \p\p
For example, this identifier includes the SCSI Channel and SCSI ID unique to the drive; so that, [2,1] indicates the drive is on channel 2 and has a SCSI ID of 1. \p\p\1
Capacity (MB)\0: Amount of storage space on the drive (in megabytes) \p\p\1
Status\0: Operating condition of the drive. For an explanation of the possible statuses, select the Possible Drive Statuses topic in the \{\5\goto "mprofileaddrt" Related Topics\} list below. \p\p\1
Vendor\0: Drive manufacturer's name \p\p\1
Product ID\0: Drive manufacturer's product code \p\p\1
Firmware Version\0: Number indicating the release of drive firmware \p\p\1
Serial Number\0: Drive manufacturer's serial number \p\p\1
Date Code\0: Date of manufacture
\p\p\1
LOGICAL UNIT DETAILED INFORMATION \0\label "mprofilelun"\p\p\1
When To Use \0 -- You may want to view this information as a reference if you need to perform any maintenance or troubleshooting procedures. For example, if you want to see a snapshot of a logical unit's parameters. \p\p\1
LUN\0: Number that identifies the number of the \{\2\bring_popup "Logical Unit" logical unit\} (LUN) \p\p\1
Controller\0: Identifies the controller that owns the logical unit\p\p\1
Capacity (MB)\0: Amount of storage space (in megabytes) \p\p\1
RAID Level\0: Indicates the \{\2\bring_popup "RAID Level" RAID Level\} of the LUN \p\p\1
Segment Size\0: Amount of data (in blocks) the controller writes to a drive before writing data to the next drive \p\p\1
Write Cache\0: Indicates whether the \{\2\bring_popup "Write Caching" write caching\} parameter has been enabled for the LUN \p\p\1
Cache Mirroring\0: Indicates whether the \{\2\bring_popup "Write Cache Mirroring" write cache mirroring\} parameter has been enabled for the LUN \p\p\1
Cache Without Batteries\0: Indicates whether the \{\2\bring_popup "Cache Without Batteries" cache without batteries\} parameter has been enabled for the LUN \p\p\1
Status\0: Operating condition of the LUN. For an explanation of the possible statuses, select the Possible Logical Unit Statuses topic in the \{\5\goto "mprofileaddrt" Related Topics\} list below. \p\p\1
NOTE\0: You might see an asterisk next to the caching parameters column. This indicates that the parameter is enabled, but is currently NOT active. The controller has disabled the parameter for some reason (such as low batteries). If you see this condition, use Message Log (Status Application) to determine the correct action to take.
\p\p\1
Related Topics \0\label "mprofileaddrt"\p
\{\3\goto "Caching Concept" Caching\} \p
\{\3\goto "Fibre Channel Concept" Fibre Channel\} \p
\{\3\goto "Firmware Concept" Firmware\} \p
\{\3\goto "How To Use Message Log" How To Use Message Log\} \p
\{\3\goto "How To Use Module Profile" How To Use Module Profile\} \p
\{\3\goto "Possible Drive Statuses" Possible Drive Statuses\} \p
\{\3\goto "Possible LUN Statuses" Possible LUN Statuses\}
\p\p
\{\7\goto "mprofileaddtop" Top Of Page\}\p
\keyword "details, controller" \keyword "details, LUN" \keyword "details, drive" \keyword "component details" \keyword "host interface" \keyword "networked version" \keyword "version, controller firmware" \keyword "controller information" \keyword "drive information" \keyword "LUN information" \keyword "host-side ID" \keyword "parallel SCSI" \keyword "SCSI" \keyword "fibre channel" \keyword "screen description" \keyword "inactive cache" \keyword "disabled cache" \keyword "cache disabled" \keyword "bootware level" \keyword "appware level" \keyword "fibre channel firmware level" \keyword "cache size" \keyword "processor size" \keyword "drive capacity" \keyword "LUN capacity" \keyword "manufacture date" \keyword "board information" \keyword "product information" \keyword "vendor information" \keyword "drive firmware" \keyword "SCSI ID, see host-side ID items"

\topic "Information In Module Profile" \p\1
What Information Appears In Module Profile? \label "mprotop"
\p\p
Fast Find -- \{\5\goto "mprodrv" Disk Drives\} | \{\5\goto "mproopt" Options\} | \{\5\goto "mprort" Related Topics \}
\p\p\0
Whenever you select Module Profile, you see a summary profile of the selected RAID Module including information on its controllers, disk drives, and logical units (LUNs).
\p\p\1
CONTROLLERS
\p\p
Name\0: Identifies the controllers in the selected RAID Module as A or B and, where applicable, includes a system name/ID. The A and B correspond to the hardware controller IDs.
\p\p\1
Serial Number\0: A unique identification for the controller assigned by the manufacturer.
\p\p\1
Mode\0: Identifies the operating state of the controller. Possible modes are Active, Passive, or Offline. You could also see Inaccessible if the RAID Module has an independent controller configuration.
\p\p\1
Number of LUNs\0: Indicates how many logical units are owned by the particular controller.
\p\p\1
DISK DRIVES \label "mprodrv"
\p\p
Number of Drives\0: Indicates how many drives make up the selected RAID Module.
\p\p\1
OPTIONS \0\label "mproopt"\p\p
\{\1 o \0\} You can also select Controllers, Drives, or Logical Units to view more detailed information on these components.
\p\p
\{\1 o \0\} You can save the profile to a filename and directory of your choice by exiting Module Profile and (from the top menu) selecting File >> Save Module Profile.
\p\p\1
Related Topics \0\label "mprort"\p
\{\3\goto "How To Use File >> Save Module Profile" How To Save A Module Profile\} \p
\{\3\goto "How To Use Module Profile" How To Use Module Profile\} \p
\{\3\goto "What Additional Details Can I See?" What Additional Details Can I See?\}
\p\p
\{\7\goto "mprotop" Top Of Page\}
\keyword "screen description" \keyword "controller name/ID" \keyword "controller serial number" \keyword "module information" \keyword "controller mode" \keyword "mode" \keyword "serial number" \keyword "number of LUNs" \keyword "number of drives" \keyword "LUNs, number of" \keyword "drives, number of" \keyword "Inaccessible" \keyword "Module Profile"

\topic "How To Use Online Help" \p\1
How To Use Online Help \label "helptop"
\p\p
Fast Find -- \{\5\goto "helpnav" Navigating Help\} | \{\5\goto "helpcurs" Cursor Changes\} | \{\5\goto "helprt" Related Topics\}
\p\p\0
Online help has information on features common to all the applications as well as topics that are specific to each application (Configuration, Status, Recovery, and Maintenance/Tuning). You can access ALL of the help topics from any application's Help >> Contents.
\p\p\1
NOTE\0: The Recovery Application has a second help window containing the recovery procedures for each failure type Recovery Guru/Health Check might report. This selection is available from Help >> Recovery Guru Procedures. However, you CANNOT access the rest of the online help topics from this window.
\p\p\1
Navigating In Help \0\label "helpnav"\p\p
The tool bar at the top of the help window allows you to perform the following actions:
\p\p\1
\{\1 o \} File\0\p
-- Print the currently displayed topic to a file or printer.
\p\p
-- Setup your printer (landscape/portrait, margins, etc.).
\p\p
-- Exit Online Help.
\p\p\1
\{\1 o \} Edit \0 -- Copies text to the clipboard so that you can print it. From the top menu, select Edit >> Copy to Clipboard to copy the topic in the window you are viewing.
\p\p\1
\{\1 o \} Home \0 -- Returns you to the Home Page. This screen appears whenever you select Help from the top menu in any application.
\p\p\1
\{\1 o \} Contents \0 -- Displays all the help topics organized by hierarchy and appearance on the Home Page. Press a letter to quickly advance through the list of topics. For example, pressing <M> takes you to the first topic that begins with M. You can also use the <Home> and <End> keys on your keyboard to move through this list.
\p\p\1
\{\1 o \} Index \0 -- Lists key words or phrases in alphabetical order in the top of the Index window. The bottom of the window displays the topics in which the highlighted index term appears. Press a letter to quickly advance through this alphabetical list. To view one of these topics, you can either double-click the topic or simply highlight the topic and select <Go To>.
\p\p\1
\{\1 o \} Back \0 -- Takes you back (one topic at a time) through the topics you have viewed since selecting Help.
\p\p\1
\{\1 o \} History \0 -- Creates a list of all topics you view in the order you have selected them. This feature begins a new list each time you enter Help. To return to one of these topics, either double-click the topic or simply highlight the topic and select <Go To>.
\p\p\1
\{\1 o \} Glossary \0 -- Displays an alphabetical list of terms you can select to view a definition.
\p\p\1
\{\1 o \} Same Level Topics /All Topics \0 -- Displays topics of the same level using the << and >> keys to move forward or backward. You can also select Same Level Topics >> All Topics from the drop-down menu to make the arrow buttons move you through every topic in help.
\p\p\1
\{\1 o \} << and >> \0\p
-- If you are in Same Level Topics, these buttons move you to the previous/next topic within the level you are currently viewing.
\p\p
-- If you are in All Topics, these buttons move you to the previous/next topic across all levels.
\p\p\1
\{\1 o \} Up \0 -- Moves you to the next higher level of topics.
\p\p\1
Understanding Cursor Changes \0\label "helpcurs"\p\p
A change in font color to blue signals one of four types of cursor changes which provide additional information, either by calling up a secondary window, by moving up or down in the topic on screen, or by re-writing the help window with a new topic.
\p\p\1
\{\1 o \} Arrow up\0: click the left mouse button when pointing to this blue word or phrase to move up in the help window to the topic/location indicated; you do NOT leave the topic named at the top of the help screen.
\p\p\1
\{\1 o \} Arrow down\0: click the left mouse button when pointing to this blue word or phrase to move down in the help window to the topic/location indicated; you do NOT leave the topic named at the top of the help screen.
\p\p\1
\{\1 o \} Magnifying glass\0: click the left mouse button when pointing to this blue word or phrase to read text that appears in a new window; click again when finished to close the secondary window. Most of the information in these secondary windows can also be found in the Glossary.
\p\p\1
\{\1 o \} Hand pointing\0: click the left mouse button when pointing to this blue word or phrase for the topic indicated to appear in the help window; the help screen re-writes with the newly selected topic.
\p\p\1
Related Topics \label "helprt"\p
\{\3\goto "Online Help Troubleshooting" Troubleshooting\}
\p\p
\{\7\goto "helptop" Top Of Page\} \p
\keyword "help" \keyword "online help" \keyword "using help"

\topic "How To Use Select Module" \p\1
How To Use Select Module \label "smodtop"
\p\p
Fast Find -- \{\5\goto "smodopt" Options\} | \{\5\goto "smodrt" Related Topics\}
\p\p\1
Procedure \0\p\p
You can select specific \{\2\bring_popup "RAID Module" RAID Modules\} in one of two ways:
\p\p\1
Drop-Down List \0 -- Use the Drop-Down List at the far left of the tool bar area near the top of each application's main screen. This is the quickest selection method if you have only a few modules and are familiar with the module names that will appear in the list.
\p\p\1
Select Module Option \0 -- \p\p
1. From any application, choose Select Module for a more detailed list of all RAID Modules.
\p\p
2. Highlight the module you want and select OK.
\p\p
This module is now selected in the drop-down list and is the default module selected for performing any task options you might choose.
\p\p
If you select the RAID Module currently displayed in the list box a second time, you are returned to the main screen. Additionally, the component statuses are updated.
\p\p\1
Options\0\label "smodopt"\p\p
\{\3\subtopic "How To Add/Remove RAID Modules" How To Add/Remove RAID Modules\} \p\p
\{\3\subtopic "How To Edit Module Information" How To Edit Module Information\} \p\p\1
Related Topics\0\label "smodrt"\p
\{\3\subtopic "Information In Select Module" What Information Appears In Select Module?\} \p
\{\3\goto "Select Module Restrictions" Restrictions/Cautions\} \p
\{\3\goto "Select Module Screen Does/Doesn't Appear" Troubleshooting\}
\p\p
\{\7\goto "smodtop" Top Of Page\} \p
\keyword "selecting modules" \keyword "module selection" \keyword "update screen" \keyword "screen update" \keyword "Select Module" \keyword "Module menu" \keyword "update statuses"

\topic "How To Add/Remove RAID Modules" \p\1
How To Add/Remove RAID Modules \label "addmodtop"
\p\p
Fast Find -- \{\5\goto "addmodstep" Adding\} | \{\5\goto "removemodstep" SCSI/Fibre Host\} | \{\5\goto "removemodnrmstep" Network Host\} | \{\5\goto "addmodrt" Related Topics\}
\p\p
Important Notes \0\p\p
The Add option is available for the Networked version ONLY. 
Check the "Installation and Support Guide" specific to your operating system for the appropriate procedure if you are adding new modules to your system through a \{\2\bring_popup "Parallel SCSI" SCSI\} or \{\2\bring_popup "Fibre Channel" Fibre Channel\} connection.
\p\p
You can only remove one module at a time. The Remove option is grayed out if you select All RAID Modules.
\p\p
If you physically remove RAID Modules from your system, but DO NOT use this Remove option, the storage management software will continue trying to contact the \{\2\bring_popup "Controller" controllers\} in that module. This is especially important in the Networked environment because missing modules could cause the software to have long delays or even system hangs while trying to contact the removed module.
\p\p
If you are operating on a system with SCSI or fibre channel connections and want to remove a RAID Module, be sure you have physically removed it from the system first. Otherwise, the module will be added again when this software detects it.
\p\p\1
Adding RAID Modules \0\label "addmodstep"\p\p
The Select Module >> Add option is available for the Networked version ONLY.
\0\p\p
When you add a new RAID Module to your network, you must follow many of the same procedures you would use when installing this software for the first time. These tasks include setting up the module and controller information for your BOOTP server and your host table, and adding this information to the storage management software's module list. For complete details on these procedures, consult the "Installation and Support Guide" for your networked version.
\p\p
1. Physically connect the RAID Module to your network and to the host machine (via SCSI or fibre channel connection). Consult the appropriate hardware documentation to complete this step.
\p\p
2. Perform the following steps to define the RAID Module and controller information and set up your network. Consult the "Installation and Support Guide" for details on these procedures. \p\p
-- Determine the hardware ethernet address for the controllers.
\p\p
-- Determine unique names for the RAID Module and for its controllers.
\p\p
-- Obtain an IP address for the controllers.
\p\p
-- Edit the BOOTP table to add the new controller information.
\p\p
-- Edit the host (or DNS) table to add the new controller information.
\p\p
3. Turn off power to the RAID Module, then turn it back on again for the new settings in the BOOTP table to take effect.
\p\p
4. Start the storage management software and select any application.
\p\p
The Select Module main screen appears; however, the new module will not be in this list.
\p\p
5. Select Add.
\p\p
6. In the Add screen, enter the controller names for the new RAID Module.
\p\p\1
NOTE\0: Now is also a good time to add information in the Comment field for each RAID Module. You may want to add location details, host-RAID Module \{\2\bring_popup "Configuration Type" configuration\}, machine type, or other unique information to further clarify the module for future identification.
\p\p
7. Click the box next to Independent Controllers if the RAID Module has an independent controller configuration.
\p\p\1
NOTE\0: The Networked version always sees both controllers in a dual-controller RAID Module regardless of which configuration you have. However, the software is able to tell if a RAID Module it is connected to is using \{\2\bring_popup "Independent Controller Configuration" independent controllers\} ONLY if you use this option.
\p\p
8. Select OK when the information is complete.
\p\p
The Add Name screen appears with a default name for this module. For example, if you are adding a tenth RAID Module, the name might be NetModule_010.
\p\p
9. Either accept the default name (select OK) OR define a new name for the module (enter the name up to 16 characters and select OK).
\p\p
If you enter a new name, it could include the host machine name, the module's location, and a unique number for the module. After selecting OK, the Add screen appears again.
\p\p\1
NOTE\0: If you added more than one RAID Module, repeat this procedure (Steps 1-9) for each one.
\p\p
10. When you are finished adding each new module, select Cancel at the final Add screen.
\p\p
11. At the Select Module main screen, verify that the new RAID Module appears in the list.
\p\p\1
NOTE\0: If you receive an error message when adding a new module, use the symping utility to display possible reasons and suggestions for correcting the problem.
\p\p
12. When finished, highlight a module and select OK to go to the application's main screen, OR select Exit if you wish to leave the application.
\p\p\1
NOTE\0: For best results, verify the new RAID Module's configuration is what you need by performing the following steps. Consult the "Installation and Support Guide" for details on these procedures.
\p\p
\{\1 o \0\} From the Recovery Application, select the new RAID Module >> Recovery Guru/Health Check to verify the components are \{\2\bring_popup "Optimal Mode" Optimal\}.
\p\p
\{\1 o \0\} Use the Configuration Application to determine what drive groups/LUNs are configured and how parameters are set.
\p\p
\{\1 o \0\} Determine if any changes are necessary.
\p\p\label "removemodstep"\1
Removing RAID Modules Connected To A Host Via SCSI/Fibre Channel \0\p\p\1
IMPORTANT \0\p
If you leave the RAID Module physically connected while performing this remove procedure, it is possible that the software will scan your devices and re-add the module. Be sure to perform Step 1 first!
\p\p
1. Physically remove the RAID Module from your system. Consult the appropriate hardware documentation to complete this step.
\p\p
2. From any application, choose Select Module.
\p\p
3. Highlight the module you want to remove and select Remove.
\p\p
Remember, the Remove option is grayed out if All RAID Modules is highlighted.
\p\p
4. Select OK to verify that you want to remove this module.
\p\p
5. Exit the Select Module option.
\p\p\1
Removing RAID Modules Connected To A Host Via Network \0\label "removemodnrmstep"\p\p\4
CAUTION \0\p
If you physically remove the RAID Module from your network BEFORE performing this remove procedure, the software will continue to try contacting the module. Missing modules can cause the software to have long delays or even system hangs. Be sure to begin at Step 1!
\p\p
1. From any application, choose Select Module. \p\p
2. Highlight the module you want to remove and select Remove. \p\p
Remember, the Remove option is grayed out if All RAID Modules is highlighted. \p\p
3. Select OK to verify that you want to remove this module. \p\p
4. Exit the Select Module option.
\p\p\1
NOTE\0: If you are permanently removing this module from your network, you should also edit your BOOTP server and host (or DNS) table at this time. \p\p
5. Physically remove the RAID Module from your network. Consult the appropriate hardware documentation to complete this step.
\p\p\1
Related Topics\0\label "addmodrt"\p
\{\3\goto "How To Use Recovery Guru" How To Use Recovery Guru/Health Check\} \p
\{\3\goto "How To Use Select Module" How To Use Select Module\} \p
\{\3\goto "Information In Select Module" What Information Appears In Select Module?\} \p
\{\3\goto "Information In Configuration" What Information Appears In The Configuration Application?\}
\p\p
\{\7\goto "addmodtop" Top Of Page\} \p
\keyword "symping utility" \keyword "networked version" \keyword "independent controller configuration" \keyword "indicating host-module configuration" \keyword "adding modules" \keyword "remove modules" \keyword "modules, adding" \keyword "modules, removing"

\topic "How To Edit Module Information" \p\1
How To Edit Module Information \label "editmodtop"\p\p
Fast Find -- \{\5\goto "editmodrt" Related Topics\}
\p\p\1
Procedure \0\p\p
1. From any application, choose Select Module.
\p\p
2. Highlight the module you want to add or change comments for and select Edit.
\p\p
Remember, the Edit option is grayed out if All RAID Modules is highlighted.
\p\p
3. In the Edit screen, make the following changes as needed: \p\p
-- Change the module name if desired. Remember, there is a 16 character limit. The new name might include the host machine's name, the module's location, and a unique number for the module.
\p\p
-- For RAID Modules using the \{\2\bring_popup "Independent Controller Configuration" independent controller\} configuration, click the box next to Independent Controllers to indicate the RAID Modules are using this configuration.
\p\p\1
NOTE\0: The Networked version always sees both controllers in a dual-controller RAID Module regardless of which configuration you have. However, the software is able to tell if a RAID Module it is connected to is using independent controllers ONLY if you use this option.
\p\p
-- In the Comment field, add information that might help you identify the module. You may want to add location details, host RAID Module \{\2\bring_popup "Configuration Type" configuration type\}, machine type, or other unique information to further clarify the module for future identification.
\p\p
4. Select OK when done.
\p\p
The Select Module main screen now reflects any changes you made.
\p\p
5. Repeat Steps 2-4 until you have added/changed information for each RAID Module you want to change.
\p\p
6. When finished, highlight a module and select OK.
\p\p\1
Related Topics \label "editmodrt"\p
\{\3\goto "How To Use Select Module" How To Use Select Module\} \p
\{\3\goto "Information In Select Module" What Information Appears In Select Module?\}
\p\p
\{\7\goto "editmodtop" Top Of Page\} \p
\keyword "indicating host-module configuration" \keyword "edit module information" \keyword "networked version" \keyword "module information" \keyword "independent controller configuration" \keyword "identifying modules"

\topic "Information In Select Module" \p\1
What Information Appears In Select Module? \label "smodinfotop"
\p\p
Fast Find -- \{\5\goto "remove" Remove\} | \{\5\goto "edit" Edit\} | \{\5\goto "smodinfort" Related Topics\}
\p\p\0
Use the Select Module option to select or view information about a specific RAID Module, to add or remove modules in your system, or to change a module's information (module name, \{\2\bring_popup "Independent Controller Configuration" independent controllers\}, or comments area). This option is available from any application.
\p\p
This screen has the following options:
\p\p\1
Find\0 -- Allows you to quickly locate a RAID Module. It is probably most useful when you have many modules. At the pop-up screen, enter the search term you want to use. Remember that the search item must be contained in one of the fields on this screen.
\p\p\1
Add\0 -- Add is available for the Networked version ONLY. Allows you to add new modules to your system so that this software can access and monitor them.
\p\p\1
NOTE\0: Check the "Installation and Support Guide" specific to your operating system for the appropriate procedure if you are adding new modules to your system through a \{\2\bring_popup "Parallel SCSI" SCSI\} or \{\2\bring_popup "Fibre Channel" Fibre Channel\} connection.
\p\p\1\label "remove"
Remove\0 -- Allows you to remove modules from your system so this software no longer looks for them.
\p\p\1
Important \0\p
\{\1 o \0\} If you physically remove RAID Modules from your system, but DO NOT use this Remove option, the storage management software will continue trying to contact the \{\2\bring_popup "Controller" controllers\} in that module. This is especially important in the Networked environment because missing modules could cause the software to have long delays or even operating system hangs while trying to contact the removed module.
\p\p
\{\1 o \0\} If you are operating on a system with SCSI or fibre channel connections and want to remove a RAID Module, be sure you have physically removed it from the system first. Otherwise, the module will be added to the module list again when this software detects it.
\p\p
\{\1 o \0\} You can only remove one module at a time. This option is grayed out if you select All RAID Modules.
\p\p\1\label "edit"
Edit\0 -- Allows you to add or change information (module name and comments) about a RAID Module that has already been defined. Use the comments area to provide detailed information about the RAID Module to help you identify it, such as location information, independent controllers, etc.
\p\p\1
Important \0\p
You can only edit information for one module at a time. Also, this option is grayed out if you select All RAID Modules.
\p\p\1
Related Topics \0\label "smodinfort"\p
\{\3\goto "How To Use Select Module" How To Use Select Module\}
\p\p
\{\7\goto "smodinfotop" Top Of Page\} \p
\keyword "screen description" \keyword "selecting modules" \keyword "module selection" \keyword "Select Module"

\topic "Application Task Topics" \p\1
Specific Tasks Available In The Applications \0\p\p
\{\3\subtopic "Application Task Summary" Application Task Summary\}
\p\p
\{\3\subtopic "Configuration Application" Configuration Application\}
\p\p
\{\3\subtopic "Status Application" Status Application\}
\p\p
\{\3\subtopic "Recovery Application" Recovery Application\}
\p\p
\{\3\subtopic "Maintenance/Tuning Application" Maintenance/Tuning Application\}
\p\p\1
Related Topics \0\p
\{\3\goto "Concept Topics" Concepts\} \p
\{\3\goto "Common Question Topics" Common Questions\} \p
\{\3\goto "Restriction/Caution Topics" Restrictions/Cautions\} \p
\{\3\goto "Procedure Topics" Procedures\} \p
\{\3\goto "Troubleshooting Topics" Troubleshooting\} \p
\keyword "application tasks"
\keyword "tasks, available by application" \keyword "tasks, Configuration Application" \keyword "tasks, Status Application" \keyword "tasks, Recovery Application" \keyword "tasks, Maintenance/Tuning Application"

\topic "Application Task Summary" \p\1
Application Task Summary \label "apptasktop"
\p\p
Fast Find -- \{\5\goto "applstat" Status\} | \{\5\goto "applrecv" Recovery\} | \{\5\goto "applmt" Maintenance/Tuning\} | \{\5\goto "applrt" Related Topics\}
\p\p\1
CONFIGURATION TASKS \0\p\p
The following tasks are available from the tool bar or from the Options menu for each application as grouped below:
\p\p\1
\{\1 o \} List/Locate Drives \0 -- determine the physical location of drives in a logical unit/drive group, and locate the drives in a drive group when viewing the list of drives
\p\p\1
\{\1 o \} Create LUN \0 -- create new logical units (LUNs) or add LUNs to existing drive groups
\p\p\1
\{\1 o \} Create Hot Spare \0 -- assign drives to act as standbys in case a drive fails in a RAID 1, 3, or 5 logical unit on the RAID Module
\p\p\1
\{\1 o \} Modify Group/LUN \0 -- perform the following tasks on configured drive groups/LUNs: change the drive group's RAID Level, add more capacity (additional drives), change the LUNs' segment size, or restore the drive group's data storage space (defragment)
\p\p\1
\{\1 o \} Delete \0 -- delete logical units to change your drive group/LUN configuration or to change certain LUN parameters. This option always presents a list of LUNs and ask for confirmation before deleting
\p\p\1
\{\1 o \} File >> Reset Configuration \0 -- \4 use only as a last resort;\0 reset the RAID Module's drive groups and logical units back to a default configuration. You lose ALL data on the drive groups/LUNs
\p\p\1
STATUS TASKS \0\label "applstat"
\p\p\1
\{\1 o \} Message Log \0 -- view historical messages for RAID Module events; more options relating to this event log appear under the top menu option, File
\p\p\1
\{\1 o \} LUN Reconstruction \0 -- monitor the status or change the reconstruction rate for LUNs undergoing reconstruction
\p\p\1
\{\1 o \} Performance Monitor \0 -- monitor the current performance of system activity on selected controllers and LUNs for a selected RAID Module while it is in use
\p\p\1
RECOVERY TASKS \0\label "applrecv"
\p\p\1
\{\1 o \} Recovery Guru/Health Check \0 -- check selected RAID Modules for component failures and, if detected, recover from them by following step-by-step instructions
\p\p\1
\{\1 o \} Manual Parity Check/Repair \0 -- manually check and repair \{\2\bring_popup "Parity" parity\} on selected logical units
\p\p\4
CAUTION \0\p
Always select Recovery Guru/Health Check to ensure the problem is correctly diagnosed BEFORE attempting any manual recovery procedure. Incorrectly performing a procedure or performing the wrong procedure could cause equipment damage or data loss. Recovery Guru provides step-by-step procedures to make sure that you are correcting the right problem and will direct you when to use the manual recovery options.
\p\p\1
\{\1 o \} Options >> Manual Recovery >> Controller Pairs \0 -- manually place controllers online or offline when instructed
\p\p\1
\{\1 o \} Options >> Manual Recovery >> Drives \0 -- manually fail, reconstruct, or revive drives when instructed
\p\p\1
\{\1 o \} Options >> Manual Recovery >> Logical Units \0 -- manually format or revive logical units/drive groups when instructed
\p\p\1
MAINTENANCE/TUNING TASKS \0\label "applmt"
\p\p\1
\{\1 o \} LUN Reconstruction Rate \0 -- change the reconstruction rate for LUNs, even those not currently being reconstructed
\p\p\1
\{\1 o \} LUN Balancing \0 -- balance drive groups/logical unit ownership between active/active controller pairs in a module (that is, move drive groups/LUNs assigned to one controller to the other controller)
\p\p\1
\{\1 o \} Controller Mode \0 -- change controller modes for selected RAID Modules. You can change an active/passive controller pair to active/active mode, or you can swap the active and passive controllers
\p\p\1
\{\1 o \} Caching Parameters \0 -- change caching parameters for the configured LUNs on a selected RAID Module; cache parameters include \{\2\bring_popup "Write Caching" write caching\}, \{\2\bring_popup "Write Cache Mirroring" write cache mirroring\}, and \{\2\bring_popup "Cache Without Batteries" cache without batteries\}. You can use the command line utility, raidutil, to change other advanced caching parameters.
\p\p\1
\{\1 o \} Firmware Upgrade \0 -- upgrade controller \{\2\bring_popup "Firmware" firmware\} and \{\2\bring_popup "NVSRAM File" NVSRAM\} for one or all RAID Modules
\p\p\1
\{\1 o \} Options >> Auto Parity Settings \0 -- change the automatic parity check/repair settings, including whether it is enabled or not, the start time of day, day of the week, and whether to automatically repair parity errors found
\p\p\1
Related Topics \0\label "applrt"\p
\{\3\goto "Concept Topics" Concepts\} \p
\{\3\goto "Restriction/Caution Topics" Restrictions/Cautions\} \p
\{\3\goto "Troubleshooting Topics" Troubleshooting\}
\p\p
\{\7\goto "apptasktop" Top Of Page\} \p
\keyword "task summary" \keyword "application tasks" \keyword "raidutil utility" \keyword "summary of tasks" \keyword "Configuration Application" \keyword "Recovery Application" \keyword "Status Application" \keyword "Maintenance/Tuning Application" \keyword "List/Locate Drives" \keyword "Create LUN" \keyword "Create Hot Spare" \keyword "Modify Group/LUN" \keyword "Delete" \keyword "Reset Configuration" \keyword "Message Log" \keyword "Performance Monitor" \keyword "LUN Reconstruction" \keyword "Recovery Guru" \keyword "Manual Parity Check/Repair" \keyword "Manual Recovery options" \keyword "LUN Balancing" \keyword "Controller Mode" \keyword "LUN Reconstruction Rate" \keyword "Firmware Upgrade" \keyword "Caching Parameters" \keyword "automatic parity"

\topic "Configuration Application" \p\1
Configuration Application \label "cfgtop"
\p\p
Fast Find -- \{\5\goto "cfgtaskproc" Procedures\} | \{\5\goto "cfgtaskrt" Related Topics\}
\p\p\1
Configuration Tasks \0\p\p
The following tasks are available from the tool bar or from the Options menu for the Configuration Application:
\p\p\1
\{\1 o \} List/Locate Drives \0 -- determine the physical location of drives in a logical unit/drive group, and locate the drives in a drive group when viewing the list of drives
\p\p\1
\{\1 o \} Create LUN \0 -- create new logical units (LUNs) or add LUNs to existing drive groups
\p\p\1
\{\1 o \} Create Hot Spare \0 -- assign drives to act as standbys in case a drive fails in a RAID 1, 3, or 5 logical unit on the RAID Module
\p\p\1
\{\1 o \} Modify Group/LUN \0 -- perform the following tasks on configured drive groups/LUNs: change the drive group's RAID Level, add more capacity (additional drives), change the LUNs' segment size, or restore the drive group's data storage space (defragment)
\p\p\1
\{\1 o \} Delete \0 -- delete logical units to change your drive group/LUN configuration or to change certain LUN parameters. This option always presents a list of LUNs and ask for confirmation before deleting.
\p\p\1
\{\1 o \} File >> Reset Configuration \0 -- \4 use only as a last resort\0; reset the RAID Module's drive groups and logical units back to a default configuration. You lose ALL data on the drive groups/LUNs.
\p\p\1
Procedures \0\label "cfgtaskproc"
\p\p
\{\3\subtopic "How To Use List/Locate Drives" How To Use List/Locate Drives\} \p\p
\{\3\subtopic "How To Use Create LUN" How To Use Create LUN\} \p\p
\{\3\subtopic "How To Use Create Hot Spare" How To Use Create Hot Spare\} \p\p
\{\3\subtopic "How To Use Modify Group/LUN" How To Use Modify Group/LUN\} \p\p
\{\3\subtopic "How To Use Delete" How To Use Delete\} \p\p
\{\3\subtopic "How To Use File >> Reset Configuration" How To Use File >> Reset Configuration\}
\p\p\1
Related Topics \0\label "cfgtaskrt"\p
\{\3\goto "Changing LUN Parameters Concept" Changing LUN Parameters\} \p
\{\3\goto "Configuring Concept" Configuring\} \p
\{\3\goto "Configuration Questions" Common Questions\} \p
\{\3\goto "Dynamic Display Area" Dynamic Display Area\} \p
\{\3\goto "Configuration Restrictions" Restrictions/Cautions\} \p
\{\3\goto "Configuration Troubleshooting" Troubleshooting\} \p
\{\3\subtopic "Information In Configuration" What Information Appears in Configuration?\}
\p\p
\{\7\goto "cfgtop" Top Of Page\} \p
\keyword "tasks, Configuration Application" \keyword "summary of tasks" \keyword "configuration" \keyword "module configuration" \keyword "task summary" \keyword "List/Locate Drives" \keyword "Create LUN" \keyword "Create Hot Spare" \keyword "Modify Group/LUN" \keyword "Delete" \keyword "Reset Configuration"

\topic "How To Use List/Locate Drives" \p\1
How To Use List/Locate Drives \label "listtop" 
\p\p
Fast Find -- \{\5\goto "listrt" Related Topics\}
\p\p\1
Important Notes \0\p\p
\{\1 o \0\} For best results on RAID Modules with Series 3 controllers or earlier, perform this task when no I/O activity is occurring on the selected \{\2\bring_popup "RAID Module" RAID Module\} so that the flashing of the drive \{\2\bring_popup "Activity Lights" activity lights\} can be distinguished from normal I/O activity (Series 4 controllers blink the drive \{\2\bring_popup "Fault Lights" fault lights\} instead of the drive activity lights).
\p\p
Procedure \0\p\p
1. Select the Configuration Application >> RAID Module. \p\p
2. Highlight the \{\2\bring_popup "Drive Group" drive group\} containing the drives you want to list or locate. \p\p
3. Select List/Locate Drives. \p\p
A list of corresponding drives appears. \p\p
4. Select Locate. In the pop-up window, select Start. \p\p
The lights on the selected drive group \{\2\bring_popup "Flashing Lights" flash\} in a distinctive pattern (depending on the controller type and \{\2\bring_popup "RAID Level" RAID Level\} of the group) to help you physically locate the drives in the RAID Module. In a RAID Module with Series 3 controllers (or earlier), the drive activity lights flash. In a RAID Module with Series 4 controllers, the drive fault lights flash.\p\p
5. Select Stop. \p\p
The activity or fault lights stop flashing and you return to the main List/Locate Drives screen. \p\p\1
Related Topics \label "listrt"\0\p
\{\3\goto "Configuring Concept" Configuring RAID Modules\} \p
\{\3\goto "Configuration Application" Configuration Application\} \p
\{\3\goto "Configuration Restrictions" Restrictions/Cautions\} \p
\{\3\goto "What Are The Different Flashing Patterns?" What Are The Different Flashing Patterns?\}
\p\p
\{\7\goto "listtop" Top Of Page\}\p
\keyword "List/Locate Drives" \keyword "drives, locating" \keyword "finding drives" \keyword "configuration" \keyword "lights" \keyword "flashing lights" \keyword "identifying drives"

\topic "How To Use Create LUN" \p\1
How To Use Create LUN \label "createluntop" 
\p\p
Fast Find -- \{\5\goto "createlunrt" Related Topics\}
\p\p\4
CAUTION \0\p
If you are using the Networked version or a host-RAID Module configuration with more than one host, it is possible to open a Configuration Application and begin Create LUN from more than one host/station. However, you must be sure that you are using only ONE configuration session at a time or the LUN creation will fail for one of the hosts. \p\p\1
Procedure \0\p\p
1. Select the Configuration Application >> RAID Module. \p\p
2. Do one of the following: \p\p
-- For a new logical unit/drive group: highlight the \{\2\bring_popup "Unassigned Drive Group" Unassigned\} drive group in the Module Information area. When you create \{\2\bring_popup "Logical Unit" LUNs\} from the unassigned drive group, you also create a new \{\2\bring_popup "Drive Group" drive group\}. \p\p
-- For a new logical unit on an existing (configured) drive group: highlight an existing drive group with \{\2\bring_popup "Remaining Capacity" remaining\} capacity in the Module Information area. \p\p
3. Select Create LUN. \p\p
4. Do one of the following: \p\p
-- For a new logical unit: select \{\2\bring_popup "RAID Level" RAID Level\}, number of drives, and number of LUNs. \p\p
-- For a new logical unit on an existing drive group: select the number of additional LUNs you want to add to the existing drive group. \p\p
5. Complete the configuration process by doing one of the following: \p\p
-- If you want to create LUNs without changing additional LUN parameters, go to Step 8. \p\p
-- If you want to set additional LUN parameters (for example, \{\2\bring_popup "Segment Size" segment size\}, \{\2\bring_popup "Capacity" capacity\}, or selecting specific drives, etc.), continue with Step 6. \p\p
-- Select Cancel to return to the Configuration main screen without creating any LUNs. \p\p
6. Select Options to view or change any LUN configuration options (LUN capacity, drive selection, caching parameters, segment size, or LUN assignment). \p\p
For detailed information on the options available, select the How To Use Create LUN >> Options topic in the \{\5\goto "createlunrt" Related Topics\} list below. \p\p
7. Make your changes to the Options and select OK when you are done. \p\p
You can switch between options without losing your changes. However, if you make any changes on the main Create LUN screen, all changes in the Options screen are undone. \p\p
8. Select Create. \p\p
9. Select OK at the "Confirm Create" screen. \p\p
The confirmation screen allows you to review the LUNs being created with their number, RAID Level, and capacity. Select Cancel if this information is not correct. After you select Create >> OK, you return to the Configuration main screen, which displays "Formatting" until the operation is completed. \p\p\4
CAUTION \0\p
If you are creating the first drive group/LUN on the module (from all unassigned drives in the module), wait for the LUN to become Optimal before creating LUNs on additional drive groups. Also, you cannot perform any tasks on the new drive group while it is being created. Note that if the logical unit is a RAID 1, 3, or 5 logical unit, it will continue to be formatted in \{\2\bring_popup "Background Formatting" background\} after the LUN status changes to Optimal.\p\p
10. Make the LUNs part of your operating system. \p\p
Your operating system may have additional requirements to complete the configuration process so it can recognize the new LUNs, including adding drives and rebooting the operating system. Refer to the "Installation and Support Guide" specific to your operating system (restrictions and/or troubleshooting sections) and to the appropriate system documentation for specific details. \p\p\1
Related Topics \label "createlunrt"\0\p
\{\3\goto "Configuration Questions" Common Questions\} \p
\{\3\goto "Configuring Concept" Configuring RAID Modules\} \p
\{\3\subtopic "Using Create LUN >> Options" Using Create LUN >> Options\} \p
\{\3\goto "Configuration Restrictions" Restrictions/Cautions\} \p
\{\3\goto "Configuration Troubleshooting" Troubleshooting\}
\p\p
\{\7\goto "createluntop" Top Of Page\}\p
\keyword "configuration" \keyword "Create LUN" \keyword "LUN creation" \keyword "available capacity" \keyword "adding LUNs"

\topic "Using Create LUN >> Options" \p\1
Using Create LUN >> Options \label "optcfgtop" 
\p\p
Fast Find -- \{\5\goto "optcfgcap" Capacity\} | \{\5\goto "optcfgdrv" Drive Selection\} | \{\5\goto "optcfgcache" Caching\} | \{\5\goto "optcfgseg" Segment Size\} | \{\5\goto "optcfgassign" Assignment\} | \{\5\goto "optcfgrt" Related Topics\}
\p\p\0
If you select Options from the main Create LUN screen, you can view or change other LUN parameters. \p\p\1
IMPORTANT \0\p
If you make any changes on the main Create screen AFTER you have made changes in the Options screen, all changes in the Options screen return to the same values as when you first entered the Options screen. \p\p
All options are listed across the top of the screen. Select one to view/change that option (the screen changes to reflect the options you select). \p\p
You can switch between options without losing changes. \p\p
If you change any Options and then select OK, the changes are saved and the Create LUN main screen is displayed again. Therefore, make changes to any options you want before selecting OK. \p\p
If you select Cancel, ALL options settings are canceled and you are returned to the Create LUN main screen. Use Reset if you want to reset the values for a particular option. \p\p
If you select Reset, the settings for the option currently displayed return to the same values they had when you first entered the Options screen. \p\p\1
LUN Capacity \label "optcfgcap"\0\p\p
Allows you to change the default capacities for the LUNs you are creating. \p\p\1
IMPORTANT \0\p
The capacities of the LUNs must not exceed the total \{\2\bring_popup "Remaining Capacity" remaining\} capacity. If they do, the Remaining Group Capacity field indicates the amount exceeded. \p\p
Normally, use all of the \{\2\bring_popup "Available Capacity" available\} capacity. That is, the Remaining Group Capacity should be 0 after making changes to the capacities of the LUNs. \p\p\1
Drive Selection \label "optcfgdrv"\0\p\p
Allows you to change the set of drives used for the \{\2\bring_popup "Drive Group" drive group\} and to view the individual capacity of each drive. It is important to understand drive capacities and locations before making your selections. For further information, select the Restrictions/Cautions topic in the \{\5\goto "optcfgrt" Related Topics\} list below. \p\p\1
Caching Parameters \label "optcfgcache"\0\p\p
Allows you to change \{\2\bring_popup "Write Caching" write caching\}, \{\2\bring_popup "Write Cache Mirroring" write cache mirroring\}, and \{\2\bring_popup "Cache Without Batteries" cache without batteries\} parameters for each LUN you create. \p\p\4
CAUTION \0\p
Selecting Cache Without Batteries allows write caching to continue even without battery backup or if the batteries are completely discharged or not fully charged. Normally, write caching is temporarily turned off if no batteries are detected or until the batteries are charged. However, enabling the cache without batteries parameter overrides the controller's safeguard. Therefore, if you select Cache Without Batteries without an uninterruptible power supply \{\2\bring_popup "UPS (Uninterruptible Power Supply)" (UPS)\} for protection, you could lose data if a power failure occurs. \p\p
This option is grayed out if the controllers in the RAID Module do not support caching. \p\p
There are several conditions (such as low battery power, controller replacement, etc.) under which the \{\2\bring_popup "Controller" controller\} may temporarily turn off the cache settings until the condition is back to normal. In such cases, Module Profile >> LUNs indicates when caching is enabled, but inactive. \p\p
Use Maintenance/Tuning Application >> Caching Parameters if you need to change any caching parameters AFTER creating the logical units. \p\p\1
Segment Size \label "optcfgseg"\0\p\p
Allows you to change the \{\2\bring_popup "Segment Size" segment size\} for each \{\2\bring_popup "Logical Unit" LUN\} you create. Normally, you should use the default segment size shown (the values provided are based on the \{\2\bring_popup "RAID Level" RAID Level\} specified for the \{\2\bring_popup "Drive Group" drive group\}/LUN). \p\p
The segment size can also be changed after LUN creation by using Modify Group/LUN >> Segment Size. \p\p\1
LUN Assignment \label "optcfgassign"\0\p\p
Allows you to change the \{\2\bring_popup "Controller" controller\} that will own the new drive group/LUNs you create. \p\p\1
IMPORTANT \0\p
This option is grayed out if there are NOT two \{\2\bring_popup "Active/Active Controller Pair" active\} controllers in the RAID Module, if you are creating additional LUNs on an existing drive group, or if the module has an \{\2\bring_popup "Independent Controller Configuration" independent\} controller configuration. \p\p
By default, the first drive group created in a session is assigned to controller A, the second is assigned to controller B, and so on (LUNs created on existing drive groups are automatically assigned to the controller that already owns the drive group). Use the Maintenance/Tuning Application >> LUN Balancing if you want to change any drive group/LUN ownership between controllers after creating the drive groups/LUNs. \p\p\1
Related Topics \label "optcfgrt"\0\p
\{\3\goto "Changing LUN Parameters Concept" Changing Logical Unit Parameters\} \p
\{\3\goto "How To Use Create LUN" How To Use Create LUN\} \p
\{\3\goto "How To Use Modify Group/LUN" How To Use Modify Group/LUN\} \p
\{\3\goto "How To Use Module Profile" How To Use Module Profile\} \p
\{\3\goto "LUN Assignment Concept" LUN Assignment\} \p
\{\3\goto "Configuration Restrictions" Restrictions/Cautions\}
\p\p
\{\7\goto "optcfgtop" Top Of Page\}\p
\keyword "configuration" \keyword "assigning LUNs" \keyword "balancing LUNs" \keyword "controller, LUNs owned" \keyword "Create LUN >> Options" \keyword "parameters, LUN" \keyword "LUN assignment" \keyword "segment size" \keyword "capacity" \keyword "LUN capacity" \keyword "caching" \keyword "parameters, caching" \keyword "drive selection" \keyword "selecting drives" \keyword "write caching" \keyword "write cache mirroring" \keyword "cache without batteries" \keyword "LUN Balancing" \keyword "changing settings" \keyword "changing LUN assignment" \keyword "LUN parameters" \keyword "LUN options" \keyword "settings"

\topic "How To Use Create Hot Spare" \p\1
How To Use Create Hot Spare \label "createhottop" 
\p\p
Fast Find -- \{\5\goto "createhotrt" Related Topics\}
\p\p\4
CAUTION \0\p
A \{\2\bring_popup "Hot Spare" hot spare\} cannot cover for a drive with a larger capacity (that is, a 2 GB hot spare cannot replace a 4 GB failed drive). When you create a hot spare, the Configuration Application selects the first available drive unless you specify otherwise. If your \{\2\bring_popup "Unassigned Drive Group" unassigned\} drive group contains drives with different capacities, this may not be one of the larger capacity drives. Therefore, before you create a hot spare drive, use List/Locate Drives to record the capacities and location of the larger capacity drives in the unassigned drive group, and then specify one of those drives to ensure that the hot spare can replace any failed drive in the \{\2\bring_popup "RAID Module" RAID Module\}. \p\p\1
Procedure \0\p\p
1. Select the Configuration Application >> RAID Module. \p\p
2. Highlight the Unassigned drive group from the Module Information area. \p\p
3. Select Create Hot Spare. \p\p
4. Select the number of hot spare drives you want to create. \p\p
The numbers provided in the list are based on the maximum number of hot spares allowed and the number of hot spares that have already been created. Each RAID Module can support as many hot spare drives as there are \{\2\bring_popup "SCSI Channel" SCSI Channels\} (probably either 2 or 5 depending on the model of your RAID Module). \p\p
5. Do one of the following: \p\p
-- If you want the drives automatically selected by the software, select Create. \p\p
-- If you want to select specific drives, select Options. The screen displays two lists: \p\p\1
\{\1 o \0\} Unselected Drives\0 -- Indicates the unassigned drives that are not currently designated to be hot spares. \p\p\1
\{\1 o \0\} Selected Drives\0 -- Indicates the drives that have been automatically selected to be hot spares. The total number is based on the number of drives you specified in the previous screen. \p\p
6. Highlight drives from the Unselected Drives list and/or the Selected Drives list, then select Move. Both lists show the new choices. \p\p
The Move button is grayed out if you specified the maximum number of remaining (unassigned) drives shown in the main Create Hot Spare screen. \p\p\1
NOTE\0: Make sure that the number of drives listed in the Selected Drives list equals the number you specified in the previous screen. If the numbers differ, you cannot continue. \p\p
7. Select OK when finished selecting drives. \p\p
8. Select Create. \p\p
9. At the "Confirm Create Hot Spare Creation" screen, select OK. \p\p
You return to the Configuration main screen. The Module Information area of the screen displays the following: \p\p
\{\1 o \0\} A new hot spare drive group appears if there was not an existing hot spare drive group. \p\p
\{\1 o \0\} The Hot Spare drive group adds the new hot spare if there was an existing hot spare drive group. \p\p
\{\1 o \0\} In either case, the Detailed Information area shows the number of hot spare drives, and information for each hot spare drive (status, \{\2\bring_popup "Location (Drive)" location\}, and capacity in megabytes (MB)). \p\p\1
Related Topics \label "createhotrt"\0\p
\{\3\goto "Configuration Questions" Common Questions\} \p
\{\3\goto "Configuring Concept" Configuring RAID Modules\} \p
\{\3\goto "Configuration Restrictions" Restrictions/Cautions\} \p
\{\3\goto "Configuration Troubleshooting" Troubleshooting\}
\p\p
\{\7\goto "createhottop" Top Of Page\}\p
\keyword "drive group, hot spare" \keyword "configuration" \keyword "hot spare" \keyword "Create Hot Spare" \keyword "selecting drives" \keyword "drive selection" \keyword "adding hot spares"

\topic "How To Use Modify Group/LUN" \p\1
How To Use Modify Group/LUN \p\p\0
The Modify Group/LUN option allows you to perform the following tasks on configured \{\2\bring_popup "Configured Drive Group" drive groups\}/LUNs: change the drive group's \{\2\bring_popup "RAID Level" RAID Level\}, add more capacity (additional drives) to the drive group so that that you can for create new LUNs, change the LUNs' \{\2\bring_popup "Segment Size" segment size\}, or \{\2\bring_popup "Defragment" defragment\} its data storage space. \p\p\1
NOTE\0: You can not perform any of these options if the LUN is still being formatted in \{\2\bring_popup "Background Formatting" background\}. \p\p\1
Options \0\p\p
\{\3\subtopic "Modify RAID Level For A Drive Group" Modify RAID Level For A Drive Group\} \p\p
\{\3\subtopic "Expand Capacity For A Drive Group" Expand Capacity For A Drive Group\} \p\p
\{\3\subtopic "Change Segment Size For LUNs" Change Segment Size For Logical Units\} \p\p
\{\3\subtopic "Defragment A Drive Group" Defragment A Drive Group\}
\p\p\1
Related Topics\0\p
\{\3\goto "Configuration Questions" Common Questions\} \p
\{\3\goto "Configuration Restrictions" Restrictions/Cautions\} \p
\{\3\goto "Configuration Troubleshooting" Troubleshooting\} \p
\keyword "configuration" \keyword "Modify Group/LUN" \keyword "changing LUN parameters" \keyword "parameters, LUN" \keyword "drive group, modifying" \keyword "LUN parameters"

\topic "Modify RAID Level For A Drive Group"\p\1
Modify RAID Level For A Drive Group \label "raidleveltop"\p\p
Fast Find -- \{\5\goto "raidlevelrt" Related Topics\} \p\p\1
NOTE\0: You can not perform this option if any LUN in the drive group is currently being formatted in \{\2\bring_popup "Background Formatting" background\}. \p\p\1
Procedure \0\p\p
1. Select the Configuration Application >> RAID Module. \p\p
2. Highlight the \{\2\bring_popup "Configured Drive Group" drive group\} you want to modify in the Module Information area. \p\p
3. Select Modify Group/LUN >> RAID Level. \p\p
You see a Modify RAID Level screen with the \{\2\bring_popup "RAID Level" RAID Level\} options available for selection. \p\p
4. Select RAID Level. \p\p
Some options are grayed out. For example, on a five-drive LUN, you will be unable to select RAID \{\2\bring_popup "RAID 1" Level 1\} because you must have an even number of drives for \{\2\bring_popup "Mirrored Pair Drives" mirroring\}. \p\p
5. Select OK. \p\p
6. At the confirmation screen, select OK. \p\p
The screen is updated and the status changes to "Modifying" with a percentage complete column. When the process is complete, the status of all the LUNs in the drive group returns to \{\2\bring_popup "Optimal Mode" Optimal\}.
\p\p\1
Related Topics \label "raidlevelrt"\0\p
\{\3\goto "How To Use Modify Group/LUN" How To Use Modify Group/LUN\} \p
\{\3\goto "Configuration Restrictions" Restrictions/Cautions\}
\p\p
\{\7\goto "raidleveltop" Top Of Page\} \p
\keyword "parameters, LUN" \keyword "changing LUN parameters" \keyword "drive group, modifying" \keyword "modifying RAID Level" \keyword "RAID Level" \keyword "changing RAID Level" \keyword "mirrored pair drives" \keyword "LUN parameters"

\topic "Expand Capacity For A Drive Group" \p\1
Expand Capacity For A Drive Group \label "expandtop"\p\p
Fast Find -- \{\5\goto "expandrt" Related Topics\} \p\p\1
IMPORTANT \0\p
This procedure allows you to add drives to a \{\2\bring_popup "Configured Drive Group" drive group\} so that you can create new \{\2\bring_popup "Logical Unit" LUNs\} in the group. It does NOT change the capacity of existing LUNs. You must delete and recreate LUNs to change their capacity. \p\p\1
NOTE\0: You can perform this option only if there are \{\2\bring_popup "Unassigned Drive Group" unassigned\} drives. In addition, you can not perform this option if any LUN in the drive group is currently being formatted in \{\2\bring_popup "Background Formatting" background\}. \p\p\1
Procedure \0\p\p
1. Select the Configuration Application >> RAID Module. \p\p
2. Highlight the drive group you want to modify in the Module Information area. \p\p
3. Select Modify Group/LUN >> Group Capacity. \p\p
You see the Modify Group Capacity screen displaying the current drives in the group and the drives available to be added. \p\p
4. Highlight the drive or drives that you want to add to the drive group. \p\p\1
NOTE\0: If you are performing capacity expansion on a RAID 1 drive group, you must select an even number of drives for \{\2\bring_popup "Mirrored Pair Drives" mirroring\}. \p\p
5. Select OK. \p\p
6. At the confirmation screen, select OK. \p\p
The screen is updated and the status changes to "Modifying" with a percentage complete column. When the process is complete, the status of all the LUNs in the drive group returns to \{\2\bring_popup "Optimal Mode" Optimal\}. The Configuration main screen displays \{\2\bring_popup "Remaining Capacity" remaining\} capacity for this drive group.
\p\p
7. Use the Create LUN option to create new LUNs on the capacity now available in the drive group.
\p\p\1
Related Topics \label "expandrt"\0\p
\{\3\goto "How To Use Create LUN" How To Use Create LUN\} \p
\{\3\goto "How To Use Modify Group/LUN" How To Use Modify Group/LUN\} \p
\{\3\goto "Configuration Restrictions" Restrictions/Cautions\}
\p\p
\{\7\goto "expandtop" Top Of Page\} \p
\keyword "drive group, capacity" \keyword "capacity expansion" \keyword "changing drive group capacity" \keyword "modifying drive group capacity" \keyword "adding capacity" \keyword "adding drives" \keyword "drives, adding" \keyword "Group Capacity" \keyword "mirrored pair drives"

\topic "Change Segment Size For LUNs" \p\1
Change Segment Size For LUNs \label "segsizetop"\p\p
Fast Find -- \{\5\goto "segsizert" Related Topics\} \p\p\1
NOTE\0: You can not perform this option if the selected LUN is currently being formatted in \{\2\bring_popup "Background Formatting" background\}. \p\p\1
Procedure \0\p\p
1. Select the Configuration Application >> RAID Module. \p\p
2. Highlight the \{\2\bring_popup "Configured Drive Group" drive group\} you want to modify in the Module Information area. \p\p
3. Select Modify Group/LUN >> Segment Size. \p\p
4. Select the LUN. \p\p
A screen appears giving you the current \{\2\bring_popup "Segment Size" segment size\} for the selected LUN, and an area with available segment sizes for selection. \p\p
5. Select the desired Segment Size from the pull-down menu. \p\p
6. Select OK. \p\p
7. At the confirmation screen, select OK. \p\p
The screen is updated and the status changes to "Modifying" with a percentage complete column. When the process is complete, the LUN status returns to \{\2\bring_popup "Optimal Mode" Optimal\}.
\p\p\1
Related Topics \label "segsizert"\0\p
\{\3\goto "How To Use Modify Group/LUN" How To Use Modify Group/LUN\} \p
\{\3\goto "Configuration Restrictions" Restrictions/Cautions\}
\p\p
\{\7\goto "segsizetop" Top Of Page\} \p
\keyword "parameters, LUN" \keyword "changing LUN parameters" \keyword "segment size" \keyword "changing segment size" \keyword "LUN segment size" \keyword "LUN parameters"

\topic "Defragment A Drive Group" \p\1
Defragment A Drive Group \label "defragtop"\p\p
Fast Find -- \{\5\goto "defragrt" Related Topics\} \p\p\1
NOTE\0: You can not perform this option if any LUN in the drive group is currently being formatted in \{\2\bring_popup "Background Formatting" background\}. \p\p\1
Procedure \0\p\p
1. Select the Configuration Application >> RAID Module. \p\p
2. Highlight the \{\2\bring_popup "Configured Drive Group" drive group\} you want to defragment in the Module Information area. \p\p
3. Select Modify Group/LUN >> Defragment. \p\p
A Confirm Defragment Drive Group Screen appears, telling you how much space, if any, is available to recover. \p\p
4. If there is space to recover, select OK. \p\p
The data is rewritten into the available space. You see a status of Modifying while this takes place. This may take several minutes. When the process is complete, the status of all the LUNs in the drive group returns to \{\2\bring_popup "Optimal Mode" Optimal\}. \p\p\1
NOTE\0: If there is no space, you get the message, "There is no space to recover in this drive group."
\p\p\1
Related Topics \label "defragrt"\0\p
\{\3\goto "How To Use Modify Group/LUN" How To Use Modify Group/LUN\} \p
\{\3\goto "Configuration Restrictions" Restrictions/Cautions\}
\p\p
\{\7\goto "defragtop" Top Of Page\} \p
\keyword "defragment" \keyword "restore data space" \keyword "space, restore" \keyword "drive group, capacity"

\topic "How To Use Delete" \p\1
How To Use Delete \label "deletetop" 
\p\p
Fast Find -- \{\5\goto "deletewhat" What Happens\} | \{\5\goto "deletert" Related Topics\}
\p\p\0
You can use this option to delete all the \{\2\bring_popup "Logical Unit" logical units\} (LUNs) in a \{\2\bring_popup "Configured Drive Group" drive group\}, individual logical units within a drive group, or Standby \{\2\bring_popup "Hot Spare" hot spare\} drives (if supported). \p\p\4
CAUTION \0\p
Because using the Delete option causes data loss on the affected LUNs, carefully review the information in the Restrictions/Cautions topic in \{\5\goto "deletert" Related Topics\} list below BEFORE using the following procedure. \p\p\1
Procedure \0\p\p
1. Back up the data on ALL the LUNs you want to delete. \p\p
2. Select Configuration Application >> RAID Module. \p\p
3. In the Module Information area, highlight the drive group containing the LUN you want to delete, or highlight the hot spare drive group if you want to delete a hot spare. \p\p\1
NOTE\0: You cannot highlight more than one drive group at the same time. \p\p
4. Select Delete. \p\p
A list of LUNs or hot spare drives is displayed. \p\p\1
NOTE\0: Remember, the delete option is grayed out if you select \{\2\bring_popup "Unassigned Drive Group" unassigned\} drives, hot spare drives currently in use, or a drive group not owned by the current host machine. For more information, select the Restrictions/Cautions topic in the \{\5\goto "deletert" Related Topics\} list below. \p\p
5. Highlight the LUNs or hot spare drive you want to delete, or choose Select All and select Delete again. \p\p
6. Select OK at the "Confirm Delete" screen. \p\p
The confirmation screen asks if you want to delete the selected LUNs and warns that you will lose data on those LUNs. Select Cancel if you do NOT wish to delete the LUNs. \p\p\1
What Happens \label "deletewhat"\0\p\p
After deletion, one of the following is displayed in the Module Information area of the Configuration main screen: \p\p
The drives will return to an \{\2\bring_popup "Unassigned Drive Group" unassigned\} state if you did any of the following: \p\p
\{\1 o \0\} Deleted all of the LUNs in a drive group \p\p
\{\1 o \0\} Deleted the only LUN in a drive group \p\p
\{\1 o \0\} Deleted a hot spare drive \p\p
There will be additional \{\2\bring_popup "Remaining Capacity" remaining\} capacity on the drive group if you deleted some, but not all, of the LUNs in a drive group. \p\p\4
CAUTION \0\p
Your operating system may require that you reboot after making any configuration changes so that the operating system can recognize the new configuration. \p\p
You may want to \{\2\bring_popup "Defragment" defragment\} the drive group if you have deleted some, but not all, of the LUNs in a drive group.
\p\p\1
Related Topics \label "deletert"\0\p
\{\3\goto "Configuration Questions" Common Questions\} \p
\{\3\goto "Configuring Concept" Configuring RAID Modules\} \p
\{\3\goto "Defragment A Drive Group" Defragment A Drive Group\} \p
\{\3\goto "How To Use Create Hot Spare" How To Use Create Hot Spare\} \p
\{\3\goto "How To Use Create LUN" How To Use Create LUN\} \p
\{\3\goto "Configuration Restrictions" Restrictions/Cautions\} \p
\{\3\goto "Configuration Troubleshooting" Troubleshooting\}
\p\p
\{\7\goto "deletetop" Top Of Page\}\p
\keyword "configuration" \keyword "Delete" \keyword "removing LUNs/drive groups" \keyword "removing hot spares" \keyword "exclusive access operations" \keyword "stop I/Os" \keyword "access, exclusive required"

\topic "How To Use File >> Reset Configuration" \p\1
How To Use File >> Reset Configuration \label "resettop" 
\p\p
Fast Find -- \{\5\goto "resetrt" Related Topics\} \p\p\4
Use this option only as a last resort\0 if your configuration is totally inaccessible or if you want to start completely over with your configuration. \p\p\4
CAUTION \0\p
\{\1 o \0\} Because deleting \{\2\bring_popup "Logical Unit" LUNs\} causes data loss, back up data on all the \{\2\bring_popup "Drive Group" drive groups\}/LUNs in the RAID Module. This operation also deletes any filesystems mounted on the LUNs. \p\p
\{\1 o \0\} You must first stop I/O to the affected \{\2\bring_popup "RAID Module" RAID Module\} and should ensure that no other users are on the system. \p\p\1
Procedure \0\p\p
1. Select Configuration Application >> RAID Module. \p\p
2. From the top menu, select File >> Reset Configuration. \p\p
Remember, this option is grayed out if the selected RAID Module has an \{\2\bring_popup "Independent Controller Configuration" independent\} controller configuration. \p\p
3. Select OK to confirm that you want to reset your configuration. \p\p
4. Select OK to confirm again that you want to reset your configuration.\4 This step is your last chance to Cancel! \p\p\0
A default configuration appears in the Configuration main screen. This does not necessarily mean that you have all \{\2\bring_popup "Unassigned Drive Group" unassigned\} drives; you may have a small LUN 0 configured. \p\p
5. Select OK at the reset was successful confirmation screen. \p\p
6. Restart your system. \p\p
7. You will have to redefine all of your LUNs/drive groups using Create LUN. \p\p\1
NOTE\0: Your operating system may have additional requirements to complete the configuration process so that it can recognize the new LUNs. Refer to the "Installation and Support Guide" specific to your operating system (restrictions and/or troubleshooting sections) and to the appropriate system documentation for specific details. \p\p\1
Related Topics \label "resetrt"\0\p
\{\3\goto "Configuration Questions" Common Questions\} \p
\{\3\goto "How To Use Create LUN" How To Use Create LUN\} \p
\{\3\goto "How To Use Delete" How To Use Delete\} \p
\{\3\goto "Configuration Restrictions" Restrictions/Cautions\} \p
\{\3\goto "Configuration Troubleshooting" Troubleshooting\} \p
\{\3\goto "When To Use File >> Reset Configuration" When Should I Use The Reset Configuration Option?\}
\p\p
\{\7\goto "resettop" Top Of Page\}\p
\keyword "configuration" \keyword "Reset Configuration" \keyword "changing configuration" \keyword "File menu" \keyword "stop I/Os" \keyword "exclusive access operations" \keyword "access, exclusive required"

\topic "Information In Configuration" \p\1
What Information Appears In The Configuration Application? \label "cfgwhattop" 
\p\p
Fast Find -- \{\5\goto "cfgwhatmi" Module Information\} | \{\5\goto "cfgwhatdi" Detailed Information\} | \{\5\goto "cfgwhatrm" Right Mouse\} | \{\5\goto "cfgwhatrt" Related Topics\}
\p\p\1
Configuration Application Main Screen \0\p\p
The devices configured on a \{\2\bring_popup "RAID Module" RAID Module\} are identified in the Module Information area on the left side of the screen. You perform all Configuration tasks on a RAID Module and its associated \{\2\bring_popup "Controller" controllers\}, \{\2\bring_popup "Drive Group" drive groups\}, and \{\2\bring_popup "Logical Unit" LUNs\}. \p\p
As you select a device (left-click the mouse) in the list on the left side of the Configuration main screen, detailed information for that device is displayed on the right side of the screen. You can only highlight one device at a time. You cannot select or highlight any item in the Detailed Information area; it is for information only. \p\p
You can right-click the mouse on the drive and LUN devices in the Module Information area to get a menu of options that can be performed on that device. For example, if you select a \{\2\bring_popup "Configured Drive Group" configured\} drive group and right-click the mouse, you will be able to select the following options: List/Locate Drives, Create LUN (if there is available group capacity), Modify Group/LUN, or Delete. You can also select the module specific options: Select Module, Locate Module, and Module Profile. \p\p\1
Module Information Area\label "cfgwhatmi"\0\p\p
The Module Information area on the left-side of the Configuration main screen gives a hierarchical representation of the devices on the RAID Module. At the top is the RAID Module you selected upon entering the Configuration Application. \p\p
When you select the RAID Module, you see the following devices, as applicable: \p\p
\{\1 o \0\} The \{\2\bring_popup "Controller" Controllers\} in the RAID Module, labeled Controller A and Controller B \p
Select a controller and the Detailed Information area on the right side of the screen displays its controller \{\2\bring_popup "Controller Name/ID" name/ID\}, status, and details for each drive group it owns (group number, \{\2\bring_popup "RAID Level" RAID Level\}, capacity in megabytes (MB), number of drives, \{\2\bring_popup "Total Capacity" total\} capacity in MB, \{\2\bring_popup "Remaining Capacity" remaining\} capacity in MB, and details for each LUN (number, controller name/ID, RAID Level, capacity in MB, and status). \p\p
\{\1 o \0\} The Hot Spare drive group (if drives have been assigned as \{\2\bring_popup "Hot Spare" hot spares\}) \p
Select this group and the Detailed Information area on the right side of the screen displays drive \{\2\bring_popup "Location (Drive)" location\}, capacity in megabytes (MB), and status for each hot spare. \p\p
\{\1 o \0\} The \{\2\bring_popup "Unassigned Drive Group" Unassigned\} drive group, which contains the drives that have NOT been configured into logical units (LUN) or hot spares \p
Select this group and the Detailed Information area on the right side of the screen displays drive location, capacity in megabytes (MB), and status for each drive. \p\p
When you select a controller, you see the following devices, as applicable:
 \p\p
\{\1 o \0\} The \{\2\bring_popup "Configured Drive Group" Drive groups\} assigned to the selected controller. Each Group has a unique number as part of its label. \p
Select a Group and the Detailed Information area on the right side of the screen displays group number, RAID Level, capacity in megabytes (MB), number of drives, total capacity in MB, remaining capacity in MB, and details for each LUN (number, controller name/ID, RAID Level, capacity in MB, and status). \p\p
\{\1 o \0\} The Drives that belong to the selected Group. Select this folder to see a list of individual drives by their location. \p
Select a Drive and the Detailed Information area on the right side of the screen displays drive location, capacity in megabytes (MB), and status. You will see a list for the following \{\2\bring_popup "Drive Group" drives\}: Groups, Hot Spares, and Unassigned. \p\p
\{\1 o \0\} The \{\2\bring_popup "Logical Unit" LUN\} that belongs to the selected Group. Each LUN has a unique number as part of its label. \p
Select a LUN and the Detailed Information area on the right side of the screen displays LUN number, controller name/ID (for the controller owning the LUN), RAID Level, capacity in megabytes (MB), and status. \p\p\1
Detailed Information Area \label "cfgwhatdi"\0\p\p
As you highlight a device in the list on the left side of the Configuration main screen, detailed information for that device is displayed on the right side of the screen. You can only highlight one device at a time. You cannot select or highlight any item in the Detailed Information area; it is for information only. \p\p
The amount of information depends on which device you select: \p\p\1
\{\1 o \0\} Group/Ctrl\0 -- Shows an icon for the device and indicates a letter (A or B) for a \{\2\bring_popup "Controller" controller\} and a number (assigned to a \{\2\bring_popup "Configured Drive Group" configured\} drive group) as applicable. Configured drive groups consist of one or more \{\2\bring_popup "Logical Unit" LUNs\}. \p\p\1
\{\1 o \0\} Drives\0 -- Indicates how many drives are in the \{\2\bring_popup "Drive Group" drive group\}. \p\p\1
\{\1 o \0\} Remaining Capacity\0 -- Indicates how much capacity in megabytes (MB) is available on the drive group for configuring LUNs. The capacity reflects any redundancy or \{\2\bring_popup "RAID 1" RAID 1\} mirroring factors. For example, a RAID 1 LUN with 6 drives has half of the capacity of a \{\2\bring_popup "RAID 0" RAID 0\} LUN with 6 drives. \p\p\1
\{\1 o \0\} Total Capacity\0 -- Indicates how much capacity in megabytes (MB) is available on the drive group (the total capacities of all the configured LUNs) for storing data. The capacity reflects any redundancy or RAID 1 \{\2\bring_popup "Mirrored Pair Drives" mirroring\} factors. For example, a drive group with 6 drives containing RAID 1 LUNs has half of the capacity of a drive group containing 6 drives with RAID 0 LUNs. The total capacity for an \{\2\bring_popup "Unassigned Drive Group" unassigned\} drive group shows the entire capacity of the drives and does not reflect any redundancy or mirroring factors. \p\p\1
\{\1 o \0\} LUN\0 -- Indicates the number assigned to the logical unit. \p\p\1
\{\1 o \0\} Name/ID\0 -- Indicates the controller \{\2\bring_popup "Controller Name/ID" name/ID\} that identifies the controllers/LUNs in the selected RAID Module. This name/ID is either system or user defined depending or your operating system. \p\p\1
\{\1 o \0\} RAID Level\0 -- Indicates the \{\2\bring_popup "RAID Level" RAID Level\} of the LUN. This is only applicable for configured drive groups. Each LUN in the same drive group must have the same RAID Level. \p\p\1
\{\1 o \0\} Capacity\0 -- How much capacity in megabytes (MB) is available on the LUN. The capacity reflects any redundancy or RAID 1 mirroring factors. For example, a RAID 1 LUN with 6 drives has half of the capacity of a RAID 0 LUN with 6 drives. \p\p\1
\{\1 o \0\} Status\0 -- Gives the operating condition of the logical unit, controller, or drive. For an explanation of the possible statuses, select the Possible Logical Unit Statuses topic in the \{\5\goto "cfgwhatrt" Related Topics\} list below. \p\p\1
IMPORTANT \0\p
If a status other than Optimal is displayed here, you should use the Recovery Application to select Recovery Guru/Health Check and follow the recommended procedure to identify and correct the problem. \p\p\1
Right-Mouse Functionality \label "cfgwhatrm"\0\p\p
You can right-click the mouse on the devices in the Module Information area to get a menu of options that can be performed on that device. For example, if you select a Group and right-click the mouse, you will be able to select the following options: List/Locate Drives, Create LUN (if there is available group capacity), Modify Group/LUN, or Delete. \p\p\1
Related Topics \label "cfgwhatrt"\0\p
\{\3\goto "Configuration Questions" Common Questions\} \p
\{\3\goto "Configuring Concept" Configuring RAID Modules\} \p
\{\3\goto "How To Use Create LUN" How To Use Create LUN\} \p
\{\3\goto "How To Use Delete" How To Use Delete\} \p
\{\3\goto "Interface Topics" Interface Description\} \p
\{\3\goto "Configuration Restrictions" Restrictions/Cautions\} \p
\{\3\goto "Statuses Concept" Statuses\} \p
\{\3\goto "Configuration Troubleshooting" Troubleshooting\}
\p\p
\{\7\goto "cfgwhattop" Top Of Page\}\p
\keyword "screen description" \keyword "configuration" \keyword "module information" \keyword "view configuration" \keyword "controllers, displayed" \keyword "drive group, displayed" \keyword "LUNs, displayed" \keyword "hot spare" \keyword "drive group, hot spare" \keyword "unassigned drive group" \keyword "drive group, unassigned" \keyword "remaining capacity" \keyword "total capacity" \keyword "capacity" \keyword "RAID Level" \keyword "LUN capacity" \keyword "Configuration Application" \keyword "view drive groups" \keyword "mirrored pair drives"

\topic "Status Application" \p\1
Status Application \label "stattop"
\p\p
Fast Find -- \{\5\goto "stattaskproc" Procedures\} | \{\5\goto "stattaskrt" Related Topics\}
\p\p\1
Status Tasks \0\p\p
The following tasks are available from the tool bar or from the Options menu for the Status Application:
\p\p\1
\{\1 o \} Message Log \0 -- view historical messages for RAID Module events; more options relating to this event log appear under the top menu option, File
\p\p\1
\{\1 o \} LUN Reconstruction \0 -- monitor the status or change reconstruction rate for LUNs undergoing reconstruction
\p\p\1
\{\1 o \} Performance Monitor \0 -- monitor the current performance of the system activity on selected controllers and LUNs for a selected RAID Module while it is in use
\p\p\1
Procedures \0\p\p\label "stattaskproc"
\{\3\subtopic "How To Use Message Log" How To Use Message Log\} \p\p
\{\3\subtopic "How To Change The Reconstruction Rate" How To Change The Reconstruction Rate\} \p\p
\{\3\subtopic "How To View Reconstruction Progress" How To View Reconstruction Progress\} \p\p
\{\3\subtopic "How To Use Performance Monitor" How To Use Performance Monitor\}
\p\p\1
Related Topics \0\label "stattaskrt"\p
\{\3\goto "Dynamic Display Area" Dynamic Display Area\} \p
\{\3\goto "Common Question Topics" Common Questions\} \p
\{\3\goto "Restriction/Caution Topics" Restrictions/Cautions\} \p
\{\3\goto "Troubleshooting Topics" Troubleshooting\} \p
\{\3\goto "Performance Concept" Performance\} \p
\{\3\goto "Reconstruction Concept" Reconstruction\}
\p\p
\{\7\goto "stattop" Top Of Page\} \p
\keyword "tasks, Status Application" \keyword "summary of tasks" \keyword "task summary" \keyword "Status Application" \keyword "Message Log" \keyword "Performance Monitor" \keyword "LUN Reconstruction"

\topic "How To Use Message Log" \p\1
How To Use Message Log \label "msglogtop" 
\p\p
Fast Find -- \{\5\goto "msglogopt" Options\} | \{\5\goto "msglogrt" Related Topics\}
\p\p\1
Procedure \0\p\p
1. Select the Status Application. \p\p\1
NOTE\0: When you first start the Status Application, Message Log is displayed for All RAID Modules on most platforms. In some cases, the Select Module screen may be displayed first. If you want a single RAID Module, select it and re-select Message Log. \p\p
2. To view more detailed information, highlight one or more messages, then select Show Details. \p\p
The information you see depends on the type of message selected under List Types: \{\2\bring_popup "Parity Message Type" parity\}, \{\2\bring_popup "General Message Type" general\}, and \{\2\bring_popup "Hardware Message Type" hardware\}. \p\p
3. To copy detailed message information to the clipboard, from the top menu, select Edit >> Copy To Clipboard. \p\p
This automatically highlights the message's text and copies it to the clipboard. \p\p\1
IMPORTANT \0\p
Before copying additional messages or exiting this program, use an appropriate application to save the clipboard contents into an editor or desired file. \p\p\1
Options \label "msglogopt"\0\p\p
\{\3\subtopic "Copy To Clipboard" Copy To Clipboard\} \p\p
\{\3\subtopic "How To Change Message Log's Settings" How To Change Message Log's Settings\} \p\p
\{\3\subtopic "How To List Different Types Of Messages" How To List Different Types Of Messages\} \p\p
\{\3\subtopic "How To Open A Log File" How To Open An Existing Log File\} \p\p
\{\3\subtopic "How To Refresh Message Log" How To Refresh Message Log\} \p\p
\{\3\subtopic "How To Save The Log As Another File" How To Save The Log As Another File Name\} \p\p
\{\3\subtopic "Selecting Messages" Selecting Messages\} 
\p\p\1
Related Topics \label "msglogrt"\0\p
\{\3\goto "Message Log Questions" Common Questions\} \p
\{\3\goto "How To Use Module Profile" How To Use Module Profile\} \p
\{\3\goto "Message Log Restrictions" Restrictions/Cautions\} \p
\{\3\goto "Message Log Troubleshooting" Troubleshooting\} \p
\{\3\subtopic "Information In Message Log" What Information Appears In Message Log?\} \p
\{\3\subtopic "Information In Show Details" What Information Appears in Message Log's Show Details?\}
\p\p
\{\7\goto "msglogtop" Top Of Page\}\p
\keyword "Message Log" \keyword "view messages" \keyword "historical record" \keyword "past events" \keyword "events, past" \keyword "view events" \keyword "system performance"

\topic "How To Change Message Log's Settings" \p\1
How To Change Message Log's Settings \label "logsettop" 
\p\p
Fast Find -- \{\5\goto "logsetrt" Related Topics\}
\p\p\1
IMPORTANT \0\p
Changing any parameters in Log Settings applies to all RAID Modules even if you have only one RAID Module selected. \p\p\1
Procedure \0\p\p
1. From the top menu, select Options >> Log Settings. \p\p
2. Change one or more of the following: \p\p
--\1 Change the Default Log File\0 -- Enter the new filename you want data logged to. Be sure to enter the correct directory path if different from the current default \{\2\bring_popup "Log File" log\} file. \p\p
--\1 Change the Maximum Message Log Size\0 -- Enter the value you want the default log size to be before you are notified that this \{\2\bring_popup "Maximum Message Log Size" value\} has been exceeded. \p\p
-- \1 Change the Check RAID Modules Every X Minutes \{\2\bring_popup "Checking Interval" interval\}\0 -- Enter the frequency (in minutes) that you want the background monitor to check the RAID Modules. For best results, use the default value or smaller to ensure that you are notified about problems/events as soon as possible after they occur. \p\p
3. Select Save. \p\p\1
Related Topics \label "logsetrt"\0\p
\{\3\goto "Message Log Questions" Common Questions\} \p
\{\3\goto "How To Use Message Log" How To Use Message Log\} \p
\{\3\goto "Message Log Restrictions" Restrictions/Cautions\} \p
\{\3\goto "Message Log Troubleshooting" Troubleshooting\}
\p\p
\{\7\goto "logsettop" Top Of Page\}\p
\keyword "settings" \keyword "checking interval" \keyword "default log" \keyword "log file" \keyword "maximum log size" \keyword "background monitor" \keyword "monitoring modules" \keyword "size, maximum log" \keyword "interval" \keyword "values" \keyword "Options menu" \keyword "Message Log" \keyword "file selection" \keyword "log size" \keyword "changing settings" \keyword "Log Settings"

\topic "How To List Different Types Of Messages" \p\1
How To List Different Types Of Messages \label "mloglisttop" 
\p\p
Fast Find -- \{\5\goto "mloglistrt" Related Topics\}
\p\p\1
Procedure \p\p\0
1. Select Status Application >> Message Log. \p\p
All of the message types appear in the summary information screen (the default setting). \p\p
2. From the summary information screen, select List Type. \p\p
3. Click each box for the types you want to view. Select any of three types of messages or All to view every type. \p\p
You can select any one of three types of messages (\{\2\bring_popup "Parity Message Type"parity\}, \{\2\bring_popup "General Message Type" general\}, and \{\2\bring_popup "Hardware Message Type" hardware\}) or select All to view every message type. Additionally, when you select the All or Hardware message types, you can also specify a particular range of \{\2\bring_popup "ASC/ASCQ Code" ASC/ASCQ\} codes. \p\p
4. Select OK when finished. \p\p
The summary information screen displays the specific message types you selected.
\p\p\1
Related Topics\0\label "mloglistrt"\p
\{\3\goto "Message Log Questions" Common Questions\} \p
\{\3\goto "How To Use Message Log" How To Use Message Log\} \p
\{\3\goto "Message Log Restrictions" Restrictions/Cautions\} \p
\{\3\goto "Message Log Troubleshooting" Troubleshooting\}
\p\p
\{\7\goto "mloglisttop" Top Of Page\}\p
\keyword "List Type" \keyword "ASC/ASCQ" \keyword "message types" \keyword "message selection" \keyword "types of messages" \keyword "general messages" \keyword "parity" \keyword "hardware errors" \keyword "Message Log" \keyword "changing Message Log file"

\topic "How To Open A Log File" \p\1
How To Open An Existing Log File \label "mlogopentop" 
\p\p
Fast Find -- \{\5\goto "mlogopenrt" Related Topics\}
\p\p\1
Procedure \0\p\p
1. From the top menu, select File >> Open Log. \p\p
Remember, you must be in Message Log or this option is grayed out. \p\p
2. Enter/select the filename for the log you want to view in the Selection box. \p\p
On UNIX systems, you can use the \{\2\bring_popup "Filter" filter\} to direct your selection to a specific directory, filename, and file extension. \p\p
3. Select OK. \p\p
The selected log file is displayed in Message Log until you open another log or exit the Status Application. \p\p\1
IMPORTANT \0\p
\{\1 o \0\} If you see the "Log file is corrupted" message, it could mean either that the file is bad or that you have not selected an appropriate log file. \p\p
\{\1 o \0\} Opening another log file does NOT change the default log that the software writes messages to. From the top menu, select Options >> Log Settings to change the default log file. \p\p\1
Related Topics \label "mlogopenrt"\0\p
\{\3\goto "Message Log Questions" Common Questions\} \p
\{\3\goto "How To Change Message Log's Settings" How To Change Message Log's Settings\} \p
\{\3\goto "How To Save The Log As Another File" How To Save The Log As Another File Name\} \p
\{\3\goto "How To Use Message Log" How To Use Message Log\} \p
\{\3\goto "Message Log Restrictions" Restrictions/Cautions\} \p
\{\3\goto "Message Log Troubleshooting" Troubleshooting\}
\p\p
\{\7\goto "mlogopentop" Top Of Page\}\p
\keyword "File menu" \keyword "open" \keyword "log file" \keyword "Message Log" \keyword "file selection"

\topic "How To Refresh Message Log" \p\1
How To Refresh Message Log 
\p\p\1
Procedure \0\p\p
1. From the top menu, select Options >> Refresh All. \p\p
Remember that if you are NOT in Message Log, this option is grayed out. Also, the size of the \{\2\bring_popup "Log File" log\} file can affect the time it takes for refresh to update the screen. \p\p
All of the message types appear in the summary information screen again (the default setting). \p\p\1
Related Topics\0\p
\{\3\goto "Message Log Questions" Common Questions\} \p
\{\3\goto "How To List Different Types Of Messages" How To List Different Types Of Messages\} \p
\{\3\goto "How To Use Message Log" How To Use Message Log\} \p
\{\3\goto "Message Log Restrictions" Restrictions/Cautions\} \p
\{\3\goto "Message Log Troubleshooting" Troubleshooting\} \p
\keyword "Options menu" \keyword "Message Log" \keyword "log file" \keyword "refresh" \keyword "update log" \keyword "screen update"

\topic "How To Save The Log As Another File" \p\1
How To Save The Log As Another File Name \label "mlogsavetop" 
\p\p
Fast Find -- \{\5\goto "mlogsavert" Related Topics\}
\p\p\1
Procedure \0\p\p
1. From the top menu, select File >> Save Log As. \p\p
2. Enter the new name you want to save the log as. \p\p
On UNIX systems, you can use the \{\2\bring_popup "Filter" filter\} to direct your save to a specific directory, filename, and file extension. \p\p
3. Select OK. The log contents are saved to the selected filename. \p\p
4. Select OK at the "save was successful" confirmation screen. This has no effect on the \{\2\bring_popup "Log File" log\} file displayed in Message Log. \p\p\1
IMPORTANT \0\p
\{\1 o \0\} If you select or enter a filename that already exists, selecting OK overwrites the existing data in that file. \p\p
\{\1 o \0\} Saving the log to another file does NOT change the default log that the software writes messages to. From the top menu, select Options >> Log Settings to change the default log file. \p\p\1
Related Topics \label "mlogsavert"\0\p
\{\3\goto "Message Log Questions" Common Questions\} \p
\{\3\goto "How To Change Message Log's Settings" How To Change Message Log's Settings\} \p
\{\3\goto "How To Open A Log File" How To Open An Existing Log File\} \p
\{\3\goto "How To Use Message Log" How To Use Message Log\} \p
\{\3\goto "Message Log Restrictions" Restrictions/Cautions\} \p
\{\3\goto "Message Log Troubleshooting" Troubleshooting\}
\p\p
\{\7\goto "mlogsavetop" Top Of Page\}\p
\keyword "save" \keyword "log file" \keyword "File menu" \keyword "Message Log"

\topic "Information In Message Log" \p\1
What Information Appears In Message Log? \label "mloginfotop" 
\p\p
Fast Find -- \{\5\goto "mloginfobottom" Bottom Screen\} | \{\5\goto "mloginfort" Related Topics\}
\p\p\0
Whenever you select Message Log, you see an historical summary of the \{\2\bring_popup "RAID Module" RAID Module\} problems, parity reports, and general status changes that have been detected. \p\p\1
Items At The Top Of The Summary Information Screen \p\p
Date & Time\0: When the detected event was logged into Message Log. \p\p
\{\1 o \0\} If the event is a component failure detected by the background monitor, this is the time the error was detected, not necessarily when it occurred. The event actually occurred since the last "Check RAID Modules Every X Minutes" \{\2\bring_popup "Checking Interval" interval\} as set in Log Settings. The default setting for this parameter is five minutes. \p\p
\{\1 o \0\} If the message reflects a \{\2\bring_popup "Parity" parity\} event, this is the time the error was detected when parity \{\2\bring_popup "Parity Check/Repair" check/repair\} was run either manually or automatically. \p\p
\{\1 o \0\} If the message indicates a general status change, this is the time the change was detected. You have a history of changes made. \p\p\1
RAID Module\0: The specific module where the event occurred. \p\p\1
Type\0: What type of RAID Module event occurred: \{\2\bring_popup "Parity Message Type" parity\}, \{\2\bring_popup "General Message Type" general\}, and \{\2\bring_popup "Hardware Message Type" hardware\}. \p\p\1
Code\0: The \{\2\bring_popup "ASC/ASCQ Code" ASC/ASCQ\} code for hardware messages when applicable. The code identifies the specific problem that occurred. Select Show Details for the recommended Action to Take. \p\p\1
Controller\0: The affected controller identified by A or B and its system controller \{\2\bring_popup "Controller Name/ID" name/ID\}. \p\p\1
Items At The Bottom Of The Summary Information Screen \label "mloginfobottom"\p\p
Current Log\0: Indicates which log is open for viewing. Normally, this is the default \{\2\bring_popup "Log File" log\} file, unless you open another log file. \p\p\1
Total Messages\0: Indicates the number of messages displayed in the current log file. \p\p\1
Total Selected\0: Indicates the total number of messages that you have selected in the summary information screen. \p\p\1
Related Topics \label "mloginfort"\0\p
\{\3\goto "ASC/ASCQ Error Codes" ASC/ASCQ Error Codes\} \p
\{\3\goto "How To List Different Types Of Messages" How To List Different Types Of Messages\} \p
\{\3\goto "How To Use Message Log" How To Use Message Log\} \p
\{\3\goto "Parity Concept" Parity\} \p
\{\3\goto "Message Log Troubleshooting" Troubleshooting\} \p
\{\3\goto "Information In Show Details" What Information Appears In Message Log's Show Details?\}
\p\p
\{\7\goto "mloginfotop" Top Of Page\}\p
\keyword "error detection" \keyword "ASC/ASCQ" \keyword "Message Log" \keyword "screen description" \keyword "summary of events" \keyword "types of messages" \keyword "current log file open" \keyword "log file"

\topic "Information In Show Details" \p\1
What Information Appears in Message Log's Show Details? \label "infoshowtop" 
\p\p
Fast Find -- \{\5\goto "infoshowscreen" Screen Options\} | \{\5\goto "infoshowopt" Message Options\} | \{\5\goto "infoshowrt" Related Topics\}
\p\p\1
Select Messages In The Summary Information Screen \0\p\p
Double-click a single message or highlight one or more messages, then select Show Details to view more information, such as a description of the event, its probable cause, and the recommended action you should take. All message types have the following information: \p\p\1
Message Type\0: \{\2\bring_popup "Parity Message Type" Parity\}, \{\2\bring_popup "General Message Type" General\}, and \{\2\bring_popup "Hardware Message Type" Hardware\}. \p\p\1
Date\0: The month, day, and year the event details were written to Message Log. \p\p\1
RAID Module\0: The specific \{\2\bring_popup "RAID Module" RAID Module\} affected. \p\p\1
Time\0: The time the event details were written to Message Log. \p\p\1
Controller\0: The \{\2\bring_popup "Controller Name/ID" name/ID\} of the controller assigned to the specified RAID Module. \p\p\1
Screen Options \label "infoshowscreen"\0\p\p
\{\1 o \0\} From the detailed information screen, you can select Copy to Clipboard to copy the contents of a detailed message. Before copying additional items or exiting the Status Application, use an appropriate application to save the clipboard contents into an editor or desired file. \p\p
\{\1 o \0\} Use the Messages Index to track the number of messages you selected in the summary information screen before entering Show Details. For example, if the index reads 1 of 4, then you are viewing the first of four messages that you selected in the summary information screen. \p\p\1
Message Options \label "infoshowopt"\0\p\p
Depending on the type of message you select in the summary information screen, you could see one of the following detailed message formats when you select Show Details: \p\p
\{\3\subtopic "General Message Details" General Message Details\} \p\p
\{\3\subtopic "Hardware Message Details" Hardware Message Details\} \p\p
\{\3\subtopic "Parity Message Details" Parity Message Details\} \p\p
\{\3\subtopic "ASC/ASCQ Error Codes" ASC/ASCQ Error Codes\}
\p\p\1
Related Topics \label "infoshowrt"\0\p
\{\3\goto "How To Use Message Log" How To Use Message Log\} \p
\{\3\goto "Information In Message Log" What Information Appears in Message Log?\}
\p\p
\{\7\goto "infoshowtop" Top Of Page\}\p
\keyword "Show Details" \keyword "details, events" \keyword "error detection" \keyword "Message Log" \keyword "screen description" \keyword "ASC/ASCQ" \keyword "messages, general" \keyword "messages, hardware" \keyword "messages, parity"

\topic "General Message Details" \p\1
General Message Details (Message Log) \0\p\p
If the message type you are viewing in Show Details is \{\2\bring_popup "General Message Type" general\}, you receive the following additional details: \p\p\1
Description\0: Information about what event/problem may have occurred. \p\p\1
Related Topics \0\p
\{\3\goto "Copy To Clipboard" Copy To Clipboard\} \p
\{\3\goto "Selecting Messages" Selecting Messages\} \p
\{\3\goto "Information In Show Details" What Information Appears in Show Details?\} \p
\keyword "general messages" \keyword "messages, general" \keyword "events, general"

\topic "Hardware Message Details" \p\1
Hardware Message Details (Message Log ) \label "hardmsgtop" 
\p\p
Fast Find -- \{\5\goto "hardmsgrt" Related Topics\}
\p\p\0
If the message type you are viewing in Show Details is \{\2\bring_popup "Hardware Message Type" hardware\}, you receive the following details: \p\p\1
Sense Key\0: Sense Keys are sent by the \{\2\bring_popup "Controller" controller\} in the sense data and can be thought of as a summary code for the error. This information may be useful for troubleshooting or to service personnel. \p\p\1
ASC/ASCQ\0: ASC is a SCSI Additional Sense Code and an ASCQ is an ASC Qualifier. \{\2\bring_popup "ASC/ASCQ Code" ASC/ASCQ\} codes are sent by the controller to give further information on the specific event/problem that occurred. This information may be useful for troubleshooting or to service personnel. \p\p\1
Affected Component\0: The specific component where the event/problem occurred. \p\p\1
Affected Tray\0: The tray (controller or \{\2\bring_popup "Drive Tray" drive\}) where the component resides. \p\p\1
Affected Logical Unit\0: The specific \{\2\bring_popup "Logical Unit" LUN\} where the event/problem occurred; given when applicable. \p\p\1
Probable Cause\0: When available, information about why this event/problem may have occurred. \p\p\1
Action To Take\0: The steps you should take to correct the event/problem that occurred. \p\p\1
Related Topics \label "hardmsgrt"\0\p
\{\3\goto "ASC/ASCQ Error Codes" ASC/ASCQ Error Codes\} \p
\{\3\goto "Copy To Clipboard" Copy To Clipboard\} \p
\{\3\goto "Selecting Messages" Selecting Messages\} \p
\{\3\goto "Information In Show Details" What Information Appears in Show Details?\}
\p\p
\{\7\goto "hardmsgtop" Top Of Page\}\p
\keyword "hardware errors" \keyword "messages, hardware" \keyword "events, hardware" \keyword "ASC/ASCQ" \keyword "probable cause" \keyword "action to take" \keyword "cause, probable"

\topic "Parity Message Details" \p\1
Parity Message Details (Message Log) \label "paritymsgtop" 
\p\p
Fast Find -- \{\5\goto "paritymsgrt" Related Topics\}
\p\p\0
If the message type you are viewing in Message Log >> Show Details is \{\2\bring_popup "Parity" parity\}, you receive the following details: \p\p\1
Affected Logical Unit\0: The specific \{\2\bring_popup "Logical Unit" logical unit\} (LUN) where the parity problem occurred. \p\p\1
Block Begin\0: The code for the initial data block on the affected LUN. \p\p\1
Block End\0: The code for the final data block on the affected LUN. The Block Begin and End numbers provide a range that identifies the logical address where the parity inconsistencies were found. \p\p\1
Number of Bad Blocks Repaired\0: The total number of blocks on the logical unit where parity inconsistencies were found and repaired (if repair was selected when the parity check was performed). \p\p\1
IMPORTANT \0\p
Parity check/repair fixes parity, not data. If the parity inconsistencies resulted from corrupted data, the data is still corrupted, but the parity is correct. Therefore, parity inconsistencies might indicate corrupt data. You may be able to use your operating system to verify your data. \p\p\1
Related Topics \label "paritymsgrt"\0\p
\{\3\goto "How To Use Manual Parity Check/Repair" How To Use Manual Parity Check/Repair\} \p
\{\3\goto "Parity Concept" Parity\} \p
\{\3\goto "Viewing Parity Messages" Viewing Parity Messages\} \p
\{\3\goto "Information In Show Details" What Information Appears in Show Details?\}
\p\p
\{\7\goto "paritymsgtop" Top Of Page\}\p
\keyword "blocks, parity" \keyword "parity" \keyword "messages, parity" \keyword "events, parity"

\topic "ASC/ASCQ Error Codes" \p\1
ASC/ASCQ Error Codes (Message Log) \label "asctop"\p\p
Fast Find -- \{\5\goto "ascsense" Sense Keys\} | \{\5\goto "ascfru" FRU Codes\} | \{\5\goto "asccodes" Sense Codes\} | \{\5\goto "ascrt" Related Topics\}
\p\p\0
This document describes the various error codes returned by the RAID Module's \{\2\bring_popup "Controller" controllers\}. On detection of an error condition, the controller returns a status of Check Condition on the command that had the error. The host responds with a Request Sense command. On receipt of the Request Sense, the controller returns sense data, which includes the Sense Key, FRU Code, and ASC/ASCQ information, indicating the reason for the error condition. \p\p\1
IMPORTANT \0\p
You might see \{\2\bring_popup "ASC/ASCQ Code" ASC/ASCQ\} error codes in the Message Log (Show Details) for hardware messages. These codes give further information on the specific error that occurred. When a hardware problem is detected, you should always follow the recommended Action to Take. Most likely, you will need to use Recovery Guru/Health Check >> Show Procedures in the Recovery Application to resolve the problem. \p\p\1
Sense Keys \label "ascsense"\0\p\p
The possible Sense Keys returned by the RAID controller in the sense data are shown below. The Sense Key is returned in byte 2 of the Request Sense data. The Sense Key may be thought of as a summary code for the error. More detailed information about the error is provided by the FRU and ASC/ASCQ codes described in the next sections. 
\p\p
0x00	No Sense \p
The controller has no errors to report at this time.
\p\p
0x01	Recovered Error \p
The controller detected the error, but was able to recover from it.
\p\p
0x02	Not Ready \p
The controller is in the process of finishing initialization, and will not allow hosts access to user data until it is ready.
\p\p
0x03	Media Error \p
A drive attached to the controller detected a media error on itself.
\p\p
0x04	Hardware Error \p
This Sense Key is typically returned by the controller on most unrecoverable errors.
\p\p
0x05	Illegal Request \p
A command was issued to the controller that is not allowed (for example, access to a non-existent logical unit).
\p\p
0x06	Unit Attention \p
The controller is informing the host of an action it took to remedy an exception condition (for example, the controller marked a drive Failed, because the drive could no longer be accessed).
\p\p
0x0B	Aborted Command \p
The controller could not finish the requested operation. However, in the typical scenario, it will have taken some action to ensure that the error condition would not occur again. Therefore, the next time this same command is received, the same error condition should not occur.
\p\p
0x0E	Miscompare \p
A failed Verify operation, or a Verify with Parity Check operation failure will return a Sense Key of Miscompare.
\p\p\1
Field Replaceable Units (FRU) Code Definitions \label "ascfru"\0\p\p
Each time an error is detected, the controller puts the Field Replaceable Unit (FRU) code of the failed component in the sense data (byte 14 in the sense data for the first error and bytes 26-33 for additional errors). To provide meaningful information for troubleshooting, the FRU codes have been grouped. The defined FRU groups are listed below. \p\p\1
FRU Code - Description \0\p
0x01 -- Host Channel Group \p
0x02 -- Controller Drive Interface Group \p
0x03 -- Controller Buffer Group \p
0x04 -- Controller ASIC Group \p
0x05 -- Controller Other Group \p
0x06 -- Subsystem Group \p
0x07 -- Not Used \p
0x08 -- Sub-enclosure Group \p
0x09-0x0F -- Reserved \p
0x10-0xFF -- Drive Groups
\p\p
(0x01)-Host Channel Group \p
This group consists of the host SCSI Bus, its SCSI interface chip, and all initiators and other targets connected to the bus.
\p\p
(0x02)-Controller Drive Interface Group \p
This group consists of the SCSI interface chips on the controller which connect to the drive buses.
\p\p
(0x03)-Controller Buffer Group \p
This group consists of the controller logic used to implement the on-board data buffer.
\p\p
(0x04)-Controller Array ASIC \p
This group consists of the ASICs on the controller associated with the RAID functions.
\p\p
(0x05)-Controller Other Group \p
This group consists of all controller-related hardware not associated with another group.
\p\p
(0x06)-Subsystem Group \p
This group consists of subsystem components that are monitored by the RAID controller, such as power supplies, fans, thermal sensors, and AC power monitors.
\p\p
(0x08)-Sub-Enclosure Group \p
This group consists of the devices such as power supplies, environmental monitor, and other subsystem components in the sub-enclosure.
\p\p
(0x10-0xFF)-Drive Group \p
This group consists of a drive (embedded controller, drive electronics, and Head Disk Assembly), its power supply, and the SCSI cable that connects it to the controller; or supporting sub-enclosure environmental electronics. An FRU code denoting a drive contains the channel number (1-relative) in the upper nibble, and the drive's SCSI ID in the lower nibble. For example, a drive on the third channel, SCSI ID 2 is denoted by an FRU code of 0x32.
\p\p
An FRU code denoting a drive contains the channel number (1-relative) in the upper nibble, and the drive's SCSI ID in the lower nibble. For example, a drive on the third channel, SCSI ID 2 is denoted by an FRU code of 0x32. \p\p\1
Additional Sense Codes And Qualifiers \label "asccodes"\0\p\p
The Additional Sense Code (ASC) and Additional Sense Code Qualifier (ASCQ) values are returned by the RAID controller in the sense data. The ASC and ASCQ provide detailed information about the specific error. \p\p
SCSI-2 defined codes are used whenever possible. Array specific error codes are used when necessary, and are assigned SCSI-2 vendor unique codes 0x80 to 0xFF. \p\p
The most probable Sense Keys (listed below for reference) returned for each error are also listed. Sense Keys of 6 in parentheses indicate that 6 (Unit Attention) would be the nominal Sense Key reported; however, the actual value would be that set in the "Sense Key for Vendor-unique Conditions" field in the User-configurable options of the \{\2\bring_popup "NVSRAM File" NVSRAM\}. \p\p
ASCs and ASCQs are normally returned in bytes 12 and 13 of the sense data. On multiple errors (defined as errors that occurred on the same command, not necessarily as errors that occurred simultaneously), there may be additional ASCs and ASCQs in the ASC/ ASCQ stack, which are bytes 22-25 of the sense data. In most cases, the first error detected is stored in bytes 12 and 13 of the sense data; subsequent errors are stored in the ASC/ ASCQ stack. \p\p
The following list shows all possible ASC/ASCQ/Sense Key combinations returned by the controller. \p\p\1
ASC/ASCQ/Sense Key: 00 00 0 \0\p
No Additional Sense Information \p
The controller has no errors to report for the requesting host and addressed logical unit combination.
\p\p\1
ASC/ASCQ/Sense Key: 04 01 2 \0\p
Logical Unit In Process Of Becoming Ready \p
The controller is executing its initialization functions on the addressed logical unit. This includes drive spin-up and validation of the drive and logical unit configuration information. This error is normally returned on commands following the initial Inquiry command after a power-up/reset.
\p\p\1
ASC/ASCQ/Sense Key: 04 02 2 \0\p
Logical Unit Not Ready, Initializing Command Required \p
The controller is configured to wait for a Start/Stop Unit command before spinning up the drives, but the command has not yet been received.
\p\p\1
ASC/ASCQ/Sense Key: 04 04 2 \0\p
Logical Unit Not Ready, Format In Progress \p
The controller previously received a Format Unit command from an initiator, and is executing that command on this logical unit. Other commands cannot be sent to this logical unit until the Format Unit is completed.
\p\p\1
ASC/ASCQ/Sense Key: 04 81 02 \0\p
Firmware Versions Incompatible \p
The versions of firmware on the redundant controllers are incompatible/inconsistent. This is probably because you replaced a failed controller with a new controller that does not have the same version of firmware. Controllers with an incompatible version of firmware may cause unexpected results. Therefore, you must download new firmware as soon as possible. Use the Recovery Guru/Health Check in the Recovery Application to obtain instructions on how to download firmware to make the versions consistent.
\p\p\1
ASC/ASCQ/Sense Key: 0C 00 4,(6) \0\p
Unrecoverable Write Error \p
If this error is reported during normal operation, the controller has detected an error on a write operation to a drive, but was unable to recover from the error. The drive that failed the write operation is marked Failed.
\p\p
If this error is reported just after a power loss has occurred, it indicates that the controller has detected that its batteries have been discharged. \p\p
\{\1 o \0\} If the power loss was for a reasonably long time, wait for the controller's batteries to be recharged. \p
\{\1 o \0\} If the power loss was for a very short time, the controller's cache holdup battery logic has failed. \p
\{\1 o \0\} If the controller has on-board batteries (such as a 3601 RAID controller), replace the controller. \p
\{\1 o \0\} If the controller has off-board batteries, check the battery hardware to ensure that there is no malfunction.
\p\p\1
ASC/ASCQ/Sense Key: 0C 01 1 \0\p
Write Error Recovered With Auto Reallocation \p
The controller recovered a write operation to a drive. Auto reallocation may or may not have been used, but this is the only standard ASC/ASCQ that tells the initiator that no further actions are required by the driver. The host need not take any action.
\p\p\1
ASC/ASCQ/Sense Key: 0C 80 4,(6) \0\p
Unrecovered Write Error Due To Possible Battery Discharge And Alternate Controller Failure \p
If this error is reported during normal operation, it indicates that the controller had to synchronize and/or purge its cache due to configuration changes (such as logical unit deletion, addition or replacement), or if requested to do so by the host system, and the cache synchronization or purge failed for some reason. The user should restore any data that would have been lost.
\p\p
This error is also reported in the following situations at power-up: \p\p
\{\1 o \0\} The controller noted that it had dirty data in cache, and attempted to flush it to disk, but the flush operation failed. The dirty data will be lost. The user should restore any data that would have been lost.
\p\p
\{\1 o \0\} If the controller had been in write-back caching mode with caching without batteries disabled and mirroring DISABLED: \p
\{\1 -- \0\} The controller has detected that the batteries are either not physically present now, or they are fully discharged. Dirty user data in this controller's cache has been lost and the user must restore the dirty data. \p
(1) If the controller has its own on-board batteries, the user should replace the controller with a good one, or if that is impossible, turn off write-back caching until the controller can be replaced. \p
(2) If the controller has off-board batteries, the user should replace the batteries in the battery pack and ensure that the battery hardware is functioning normally.
\p\p
\{\1 o \0\} If the controllers had been in write-back caching mode with caching without batteries disabled and mirroring ENABLED: \p
\{\1 -- \0\} The controller has detected that its batteries, as well as those of the alternate controller are not functioning. Dirty user data in the cache has been lost and the user must restore the dirty data. The user must replace the  batteries. \p
\{\1 -- \0\} The controller has detected that it was newly swapped into this subsystem, and that it had dirty data in cache. The dirty data cannot be flushed to disk because it has been removed from its original subsystem. The user should ignore the error, since no data loss has occurred on this subsystem. \p
\{\1 -- \0\} The controller has detected that its batteries are not functioning, and it had dirty cached data, and the alternate controller has been replaced by another controller (and therefore the mirrored copy of the cached data has been lost). Dirty user data in this controller's cache may have been lost and the user must restore the dirty data. The user must replace the batteries. If possible, swap-in the original alternate controller, so that the dirty data in that controller's cache may be reclaimed and flushed to disk.
\p\p\1
ASC/ASCQ/Sense Key: 0C 81 4,(6) \0\p
Deferred Unrecoverable Error Due To Memory Failure \p
Recovery from a Data Cache error was unsuccessful. User data may have been lost.
\p\p\1
ASC/ASCQ/Sense Key: 11 00 3 \0\p
Unrecovered Read Error \p
An unrecovered read operation to a drive occurred and the controller has no redundancy to recover the error. The error probably occurred in RAID 0 or Degraded RAID levels 1, 3, or 5.
\p\p\1
ASC/ASCQ/Sense Key: 11 8A 3 \0\p
Miscorrected Data Error - Due To Failed Drive Read \p
A media error has occurred on a read operation during interrupted write processing.
\p\p\1
ASC/ASCQ/Sense Key: 18 02 1 \0\p
Recovered Data - Data Auto Reallocated \p
The controller recovered a read operation to a drive. Auto reallocation may or may not have been used, but this is the only standard ASC/ASCQ that tells the initiator that no further actions are required by the driver. The host need not take any action.
\p\p\1
ASC/ASCQ/Sense Key: 1A 00 5 \0\p
Parameter List Length Error \p
A command was received by the controller that contained a parameter list but the list length in the CDB was less than the length necessary to transfer the data for the command.
\p\p\1
ASC/ASCQ/Sense Key: 20 00 5 \0\p
Invalid Command Operation Code \p
The controller received a command from the initiator that it does not support.
\p\p\1
ASC/ASCQ/Sense Key: 21 00 5 \0\p
Logical Block Address Out Of Range \p
The controller received a command that requested an operation at a logical block address beyond the capacity of the logical unit. This error could be in response to a request with an illegal starting address or a request that started at a valid logical block address and the number of blocks requested extended beyond the logical unit capacity. The user should check the capacity of the logical unit, and retry the command after correcting it.
\p\p\1
ASC/ASCQ/Sense Key: 24 00 5 \0\p
Invalid Field In CDB \p
The controller received a command from the host with an unsupported value in one of the fields in the command block.
\p\p\1
ASC/ASCQ/Sense Key: 25 00 5 \0\p
Logical Unit Not Supported \p
The addressed logical unit is currently not configured. An Add Logical Unit operation to the Logical Array Mode Page must be executed to define and configure the logical unit before it is accessible.
\p\p\1
ASC/ASCQ/Sense Key: 26 00 5 \0\p
Invalid Field In Parameter List \p
The controller received a command with a parameter list that contained an error. This error is typically returned on a Mode Select if: \p\p
\{\1 o \0\} An attempt was made to issue the Mode Select to a non-supported mode page. \p
\{\1 o \0\} An attempt was made to change a changeable mode page field with a Mode Select to an unsupported value. \p
\{\1 o \0\} An attempt was made to reconstruct a drive that is not part of any logical unit. The typical scenario in this case is the deletion of a Degraded logical unit, leaving the Failed drive marked Failed. \p
\{\1 o \0\} A Mode Select was issued to the Logical Array Page (page 2B) for a non-supported action (the "Action To Take" field was not set to a value 0x80-0x88).
\p\p\1
ASC/ASCQ/Sense Key: 28 00 6 \0\p
Not Ready To Ready Transition \p
The controller has completed its initialization operations on the logical unit and it is now ready for access. This Unit Attention is used to notify hosts that the controller is ready to allow access to logical units. This notification is particularly useful if a host has exhausted its retry count soon after reset or power up.
\p\p\1
ASC/ASCQ/Sense Key: 29 00 6 \0\p
Power On, Reset, Or Bus Device Reset Occurred \p
The controller has detected one of the above conditions.
\p\p\1
ASC/ASCQ/Sense Key: 29 04 6 \0\p
Device Internal Reset \p
The controller has reset itself due to an internal error condition. Commands in progress have been lost.
\p\p\1
ASC/ASCQ/Sense Key: 29 81 (6) \0\p
Default Configuration Has Been Created \p
The controller has completed the process of creating a default logical unit. There is now an accessible logical unit that did not exist previously. The host should execute its device scan to find the new logical unit.
\p\p\1
ASC/ASCQ/Sense Key: 29 82 (6) \0\p
Controller Firmware Synchronized \p
The controller firmware was successfully synchronized with the replacement controller.
\p\p\1
ASC/ASCQ/Sense Key: 2A 01 6 \0\p
Mode Parameters Changed \p
The controller received a request from another initiator to change the mode parameters for the addressed logical unit. This Check Condition is to notify the current initiator that the change occurred. This error may also be reported if the Mode Select parameters changed because of a cache synchronization error during the processing of the most recent Mode Select request. The host should execute its device scan to determine the changes on the logical unit.
\p\p\1
ASC/ASCQ/Sense Key: 2A 02 6 \0\p
Log Parameters Changed \p
The controller received a request from another initiator to change the log parameters for the addressed logical unit. This Check Condition notifies the current initiator that the change occurred. The host should be aware that the other host may have cleared log parameters, such as the controller's performance statistics or its AEN log.
\p\p\1
ASC/ASCQ/Sense Key: 2F 00 6 \0\p
Commands Cleared By Another Initiator \p
The controller received a Clear Queue message from another initiator. This Check Condition is to notify the current initiator that the controller cleared the current initiator's commands, if it had any outstanding commands. If the host had outstanding commands, it should retry them.
\p\p\1
ASC/ASCQ/Sense Key: 31 01 1,4 \0\p
Format Command Failed \p
A Format Unit command issued to a drive returned an unrecoverable error. The drive is identified in the FRU code of the sense data. The user should replace the drive.
\p\p\1
ASC/ASCQ/Sense Key: 32 00 4 \0\p
Out Of Alternates \p
A Reassign Blocks command to a drive failed. The drive is identified in the FRU code of the sense data. The user should replace the drive.
\p\p\1
ASC/ASCQ/Sense Key: 3F 01 (6) \0\p
Drive Microcode Changed \p
The controller successfully downloaded new microcode to the specified drive, as requested by the host. This Unit Attention is used to notify the host that the Download Drive Microcode function completed successfully.
\p\p\1
ASC/ASCQ/Sense Key: 3F 80 (6) \0\p
Drive Failed Due To Write Failure \p
The drive failed a write command to it. The user should replace the drive.
\p\p\1
ASC/ASCQ/Sense Key: 3F 82 (6) \0\p
Drive Failed Due To Format/Restore Failure \p
The (previously-failed) drive was marked Failed due to either: \p\p
(1) the drive failing a Format Unit command issued to it, or \p
(2) the reconstruction on the drive failing due to the controller being unable to restore it (for example, an error occurring on another drive required for reconstruction).
\p\p
If the drive was marked Failed prior to reconstruction starting on it, the user should replace it. If the drive was Failed after reconstruction had begun, the drive was marked Failed because the controller could not reconstruct it. The user should format the entire logical unit, and then restore data from the last good tape backup.
\p\p\1
ASC/ASCQ/Sense Key: 3F 83 (6) \0\p
Drive Encountered Error During Reconstruction \p
An error occurred in a read operation on this drive while attempting to reconstruct data for a (different) replaced drive. The replaced drive will be marked Failed, but this drive will not. The user should replace this drive, then format the entire logical unit, and restore data from the last good tape backup.
\p\p\1
ASC/ASCQ/Sense Key: 3F 85 (6) \0\p
Drive Failed Due To No Response \p
The drive failed a Read Capacity or Read command at Start Of Day. The controller was unable to read the array subsystem configuration information stored on it. The user should replace the drive.
\p\p\1
ASC/ASCQ/Sense Key: 3F 86 (6) \0\p
Drive Failed Due To Format Failure \p
The drive failed either a Format Unit command, or a Write operation (issued when a logical unit was formatted). The user should replace the drive.
\p\p\1
ASC/ASCQ/Sense Key: 3F 87 (6) \0\p
Drive User-Failed Via Mode Select \p
The drive was manually failed by the user. The user should replace the drive.
\p\p\1
ASC/ASCQ/Sense Key: 3F 89 (6) \0\p
Wrong Drive Removed/Replaced \p
The user hot-removed a non-Failed drive. If the controller has not marked the drive Failed yet, the user should re-insert the drive as soon as possible. If the drive has been marked Failed, the user should replace it.
\p\p\1
ASC/ASCQ/Sense Key: 3F 8B (6) \0\p
Drive Capacity Less Than Minimum \p
The drive is not large enough to support all the logical units that must be reconstructed on it. The user should replace the drive with a larger capacity drive.
\p\p\1
ASC/ASCQ/Sense Key: 3F 8C (6) \0\p
Drive Has Wrong Block Size \p
The drive's block size does not match that of the other drives in the logical unit. The user should either: \p\p
(1) issue a Mode Select command to the controller directing it to first format, and then reconstruct the drive, or \p
(2) replace this drive with another drive pre-formatted to the block size used by all of the other drives in the logical unit.
\p\p\1
ASC/ASCQ/Sense Key: 3F 8D (6) \0\p
Drive Failed - Controller Storage Failure \p
The controller was unable to access or store internal array subsystem configuration information on the drive. The user should replace the drive.
\p\p\1
ASC/ASCQ/Sense Key: 3F 8E (6) \0\p
Drive Failed - Reconstruction Failure \p
A drive failed due to a reconstruction failure at Start of Day (SOD).
\p\p\1
ASC/ASCQ/Sense Key: 3F 98 (6) \0\p
Drive Marked Offline Due To Internal Recovery Procedure \p
An error has occurred during interrupted write processing causing the LUN to transition to the Dead state. Drives in the drive group that did not experience the read error will transition to the Offline state (0x0B) and log this error.
\p\p\1
ASC/ASCQ/Sense Key: 3F BD (6) \0\p
Drive Has Incorrect Critical Parameters Set \p
The controller was unable to query the drive for its current critical mode page settings, or was unable to change these to the correct setting. Currently, this indicates the Qerr bit is set incorrectly on the drive specified in the FRU field of the Request Sense data.
\p\p\1
ASC/ASCQ/Sense Key: 3F C3 (6) \0\p
Channel Failure \p
The controller failed a channel, and will not access drives on this channel any more. The FRU Group Qualifier (byte 26) in the sense data will indicate the 1-relative channel number of the failed channel. This condition is typically caused by a drive ignoring SCSI protocol on one of the controller's destination channels. The controller typically fails a channel if it issued a reset on a channel, and it continued to see drives ignore the SCSI Bus Reset on this channel.
\p\p\1
ASC/ASCQ/Sense Key: 3F C7 (6) \0\p
Non-Media Component Failure \p\p
(1) A subsystem component other than a drive or controller has failed (for example, fan, power supply, battery), or \p
(2) An over-temperature condition has occurred (some RAID modules contain a temperature sensor). The fans, power supplies, and battery are usually located in the controller module tray. The FRU codes indicate the faulty component. The user should replace the component indicated.
\p\p\1
ASC/ASCQ/Sense Key: 3F C8 (6) \0\p
AC Power Fail \p
The Uninterruptible Power Source (UPS) has indicated that AC power is no longer present and the UPS has switched to standby power. While there is no immediate cause for concern, users should save their work frequently, in case the battery is suddenly depleted.
\p\p\1
ASC/ASCQ/Sense Key: 3F C9 (6) \0\p
Standby Power Depletion Imminent \p
The Uninterruptible Power Source (UPS) has indicated that its standby power source is nearing depletion. The host should take actions to stop I/O activity to the controller. Normally, the controller will change from a write-back caching mode to a write-through mode. The user should not change again to write-back mode until full AC power has been restored.
\p\p\1
ASC/ASCQ/Sense Key: 3F CA (6) \0\p
Standby Power Source Not At Full Capacity \p
The Uninterruptible Power Source (UPS) has indicated that its standby power source is not at full capacity. To prevent loss of data in the event of the failure of AC power, the user should not activate write-back caching mode until full UPS power has been restored.
\p\p\1
ASC/ASCQ/Sense Key: 3F CB (6) \0\p
AC Power Has Been Restored \p
The Uninterruptible Power Source (UPS) has indicated that AC power is now being used to supply power to the controller.
\p\p\1
ASC/ASCQ/Sense Key: 3F D0 (6) \0\p
Write-Back Cache Battery Discharged \p
The controller has detected that its battery is no longer charged. If a power failure were to occur, any dirty user data in cache will be lost. To prevent the loss of any user data, the user should either: \p\p
(1) replace this controller with another, or \p
(2) turn off write-back cache.
\p\p\1
ASC/ASCQ/Sense Key: 3F D1 (6) \0\p
Write-Back Cache Battery Charged \p
The controller has detected that its battery is now fully charged, and will be capable of holding up the cache contents in the event of a power failure. The user may switch to write-back mode, if desired.
\p\p\1
ASC/ASCQ/Sense Key: 3F D8 (6) \0\p
Cache Battery Life Expiration \p
The cache battery has reached the specified expiration age.
\p\p\1
ASC/ASCQ/Sense Key: 3F D9 (6) \0\p
Cache Battery Life Expiration Warning \p
The cache battery is within the specified number of weeks of failing.
\p\p\1
ASC/ASCQ/Sense Key: 3F E0 (6) \0\p
Logical Unit Failure \p
The controller has placed the logical unit in a "Dead" state. User data and/or parity can no longer be maintained to ensure availability. The most likely cause is the failure of a single drive in non-redundant configurations or a second drive in a configuration protected by one drive. The data on the logical unit is no longer accessible.
\p\p\1
ASC/ASCQ Sense Key: 3F EB (6) \0\p
LUN Marked Dead Due To Media Error Failure \p
An error has occurred during interrupted write processing during Start of Day causing the LUN to transition to the Dead state.
\p\p\1
ASC/ASCQ/Sense Key: 40 NN 4,(6) \0\p
Diagnostic Failure On Component NN (0x80 - 0xFF) \p
The controller has detected the failure of an internal controller component. This failure may have been detected during operation as well as during an on-board diagnostic routine. The values of NN supported in this release are listed as follows: \p\p
\{\1 o \0\} 80 - Processor RAM \p
\{\1 o \0\} 81 - RAID buffer \p
\{\1 o \0\} 82 - NVSRAM \p
\{\1 o \0\} 83 - RAID Parity Assist (RPA) chip \p
\{\1 o \0\} 84 - Battery-backed NVSRAM or clock failure \p
\{\1 o \0\} 91 - Diagnostic self test failed non-data transfer components test (most likely controller cache holdup battery discharge)\p
\{\1 o \0\} 92 - Diagnostic self test failed data transfer components test \p
\{\1 o \0\} 93 - Diagnostic self test failed drive Read/Write Buffer data turnaround test \p
\{\1 o \0\} 94 - Diagnostic self test failed drive Inquiry access test \p
\{\1 o \0\} 95 - Diagnostic self test failed drive Read/Write data turnaround test \p
\{\1 o \0\} 96 - Diagnostic self test failed drive self test
\p\p
In a dual controller environment, the user should place this controller offline (hold in reset) (unless the error indicates controller battery failure, in which case the user should wait for the batteries to recharge). In single controller environments, the user should not use this subsystem until the controller has been replaced.
\p\p\1
ASC/ASCQ/Sense Key: 43 00 4 \0\p
Message Error \p
The controller attempted to send a message to the host, but the host responded with a Reject message.
\p\p\1
ASC/ASCQ/Sense Key: 44 00 4,B \0\p
Internal Target Failure \p
The controller has detected a hardware or software condition that does not allow the requested command to be completed. If the Sense Key is 0x04, indicating a Hardware Failure, the controller has detected what it believes is a fatal hardware or software failure and it is unlikely that just a retry of the command would be successful. If the Sense Key is 0x0B, indicating an Aborted Command, the controller has detected what it believes is a temporary software failure that is likely to be recovered if retried.
\p\p\1
ASC/ASCQ/Sense Key: 45 00 4 \0\p
Selection Time-out On A Destination Bus \p
A drive did not respond to selection within a selection time-out period. Possible reasons for this error include drive failure, channel failure, or the possibility of an incomplete hot-swap holding the whole channel in reset.
\p\p\1
ASC/ASCQ/Sense Key: 47 00 1,B \0\p
SCSI Parity Error \p
The controller detected a parity error on the host SCSI Bus or one of the drive SCSI Buses.
\p\p\1
ASC/ASCQ/Sense Key: 48 00 1,B \0\p
Initiator Detected Error Message Received \p
The controller received an Initiator Detected Error Message from the host during the operation.
\p\p\1
ASC/ASCQ/Sense Key: 49 00 B \0\p
Invalid Message Error \p
The controller received a message from the host that is not supported or was out of context when received.
\p\p\1
ASC/ASCQ/Sense Key: 49 80 B \0\p
Drive Reported Reservation Conflict \p
A drive returned a status of Reservation Conflict.
\p\p\1
ASC/ASCQ/Sense Key: 4B 00 1,4 \0\p
Data Phase Error \p
The controller encountered an error while transferring data to/from the initiator or to/from one of the drives.
\p\p\1
ASC/ASCQ/Sense Key: 4E 00 B \0\p
Overlapped Commands Attempted \p
The controller received a tagged command while it had an untagged command pending from the same initiator, or it received an untagged command while it had a tagged commands pending from the same initiator.
\p\p\1
ASC/ASCQ/Sense Key: 5D 80 6 \0\p
PFA Flag Detected \p
A drive has reported that a failure prediction threshold has been exceeded. This indicates that the drive may fail within 24 hours. See Recovery Guru for the recovery procedure.
\p\p\1
ASC/ASCQ/Sense Key: 84 00 4 \0\p
Operation Cannot Be Completed With LUN In Its Current State \p
The requested command or Mode Select operation is not allowed with the logical unit in the state indicated in byte 76 of the sense data. Typically, the controller returns this error if: \p\p
\{\1 o \0\} A Repair Parity, Write And Verify With Parity Check, or Reassign Blocks command was issued to the logical unit, but the logical unit is either in the Degraded or Reconstructing state. \p
\{\1 o \0\} A Test Unit Ready was issued to a Dead logical unit, and the NVSRAM option that directs the controller to return a Good status in this case has not been enabled. \p
\{\1 o \0\} A user data access command (Read or Write) was issued to a Dead logical unit. \p
\{\1 o \0\} The user attempted to replace a logical unit, but the logical unit is currently in the Reconstructing state. \p
\{\1 o \0\} The user attempted to add a logical unit, but the specified logical unit already exists. \p
\{\1 o \0\} The user attempted to check available capacity for logical unit addition, but there is no logical unit existent on the specified set of drives. \p
\{\1 o \0\} The user attempted to delete, modify, replace or format a non-existent logical unit.
\p\p\1
ASC/ASCQ/Sense Key: 84 06 4 \0\p
Logical Unit Awaiting Format \p
A Mode Select has successfully completed to create a logical unit, but the logical unit has not been formatted.
\p\p\1
ASC/ASCQ/Sense Key: 85 01 4 \0\p
Drive I/O Request Aborted \p
I/O issued to failed or missing drive due to recently failed removed drive. This error can occur as a result of I/O in progress at the time of a failed or removed drive.
\p\p\1
ASC/ASCQ/Sense Key: 87 00 4 \0\p
Microcode Download Error \p
The controller detected an error while downloading microcode and storing it in non-volatile memory.
\p\p\1
ASC/ASCQ/Sense Key: 88 0A (6) \0\p
Subsystem Monitor NVSRAM Values Configured Incorrectly \p
The controller detected an error in the configuration of the Subsystem Fault region of the NVSRAM. This error means that the controller either cannot turn on or turn off the desired Fault LEDs.
\p\p\1
ASC/ASCQ/Sense Key: 8A 00 5 \0\p
Illegal Command For Drive Access \p
The initiator attempted to pass a command through to a drive that is not allowed. The command could have been sent in pass-through mode or by attempting to download drive microcode.
\p\p\1
ASC/ASCQ/Sense Key: 8A 01 5 \0\p
Illegal Command For The Current RAID Level \p
The controller received a command that cannot be executed on the logical unit due to its RAID level configuration. Examples are parity verify or repair operations on a RAID 0 logical unit. The user should check the command being attempted, and ensure that it is being issued to a logical unit configured to an appropriate RAID level.
\p\p\1
ASC/ASCQ/Sense Key: 8B 02 B,(6) \0\p
Quiescence Is In Progress Or Has Been Achieved \p
The addressed logical unit has been quiescent. Redundant controller mode changes or logical unit ownership transfers will be, or already are in progress.
\p\p\1
ASC/ASCQ/Sense Key: 8B 03 B \0\p
Quiescence Could Not Be Achieved Within The Quiescence Timeout Period \p
It was not possible to make the requested logical units quiescent within the specified period. The make-quiescent attempt has been aborted, and controller mode changes, or logical unit ownership transfers will not be attempted.
\p\p\1
ASC/ASCQ/Sense Key: 8B 04 5 \0\p
Quiescence Is Not Allowed \p
It is not possible to make the requested logical units quiescent at this time, probably because another initiator has already requested quiescence in anticipation of a redundant controller mode change, or a logical unit ownership transfer.
\p\p\1
ASC/ASCQ/Sense Key: 8E 01 E,(6) \0\p
A Parity/Data Mismatch Was Detected \p
The controller detected inconsistent parity/data during a parity verification.
\p\p\1
ASC/ASCQ/Sense Key: 91 00 5 \0\p
General Mode Select Error \p
An error was encountered while processing a Mode Select command. This error could be returned for the following reasons: \p\p
\{\1 o \0\} An invalid "Action To Take" value was set in the Mode Select page. \p
\{\1 o \0\} An attempt was made to clear all drive and logical unit configurations by issuing a "CLEAR" to the Redundant Controller Mode Page, but the Mode Select was sent to the controller with the lower drive-side SCSI ID. \p
\{\1 o \0\} The controller could not save configuration information to the drives when a logical unit was added or replaced. The user should verify that the drives' hardware is functioning correctly, or replace the drives listed in the FRU code. \p
\{\1 o \0\} The controller could not spin up a drive that the user manually added via the "Add Drive" operation via a Mode Select to the Physical Array Page. The user should verify that the drive's hardware is functioning correctly, or replace the drive. \p
\{\1 o \0\} The controller could not mark a failed drive Optimal, if the user wished to do so via a Mode Select to the Physical Array Page. \p
\{\1 o \0\} The user attempted to mark failed an Optimal drive in an already-Dead LUN. \p
\{\1 o \0\} The user attempted to mark a failed drive as Replaced, but the controller could not access the failed drive. The user should verify that the drive's hardware is functioning correctly, or replace the drive. \p
\{\1 o \0\} The user attempted to mark a failed drive as Replaced in a logical unit that is either Dead or formatting. The user should bring the logical unit to the appropriate state before attempting the operation again. \p
\{\1 o \0\} The user requested the controller to initiate a parity scan on all logical units, but the controller is the Passive controller. The user should retry the operation via the Active controller. \p
\{\1 o \0\} The user requested an operation that caused the controller to synchronize and purge its cache (such as logical unit addition, deletion, or replacement, a transfer of ownership of the logical unit from one controller to another, or a change in the redundant controller mode of operation), but either the synchronize or the purge of the cache failed.
\p\p\1
ASC/ASCQ/Sense Key: 91 03 5 \0\p
Illegal Operation For Current Drive State \p
A drive operation was requested through a Mode Select that cannot be executed due to the state of the drive. This error could be returned for the following reasons: \p\p
\{\1 o \0\} The user attempted to mark a non-existent drive as Optimal, Failed, Non-existent or Replaced, or assign or unassign the non-existent drive as Hot Spare. \p
\{\1 o \0\} The user attempted to operate on a drive on a non-supported channel or SCSI ID. For example, attempting to "Add a Drive" to channel 7 on a 5-channel array controller. \p
\{\1 o \0\} The user attempted to add or replace a logical unit on a drive that is neither in an Optimal (but not Hot Spare) nor Spare state. \p
\{\1 o \0\} The user attempted to reassign blocks on a non-existent drive. \p
\{\1 o \0\} The user attempted to format a logical unit which has missing drives in it. \p
\{\1 o \0\} The user attempted to format a logical unit which exists on a set of drives that have SubLUNs on them. \p
\{\1 o \0\} The user attempted to mark a reconstructing drive (status of Replaced) as Optimal. \p
\{\1 o \0\} The user attempted to mark a non-failed drive as Replaced. \p
\{\1 o \0\} The user attempted to delete a drive, but the drive was not marked unassigned (it belongs to a logical unit).\p
\{\1 o \0\} The user attempted to revive a logical unit that (1) is not currently marked Dead, (2) has missing drives in it, (3) has drives in it that are marked Wrong Drive Replaced, or (4) has multiple drives that are marked Failed, but not all of the failed drives are on the same channel. \p
\{\1 o \0\} The user attempted to download drive firmware to a drive that is not owned by this controller, or the drive is either Non-existent or has been removed. \p
\{\1 o \0\} The user attempted to mark a failed drive as Replaced, but the drive's capacity is too small to support the logical units configured on the drive group. \p
\{\1 o \0\} The user attempted to mark a drive as Replace, Format And Reconstruct that is neither in the Failed or Replaced states.
\p\p\1
ASC/ASCQ/Sense Key: 91 09 5 \0\p
Illegal Operation With Multiple SubLUNs Defined \p
An operation was requested that cannot be executed when multiple SubLUNs are defined on the drive. This error could be returned for the following reasons: \p\p
\{\1 o \0\} The user attempted to add or replace a SubLUN on a drive group which is configured with logical units configured to a different RAID level. \p
\{\1 o \0\} The user attempted to add or replace a SubLUN on a drive group where its drives are not in the same sequence as that for the other SubLUNs. \p
\{\1 o \0\} The user attempted to let one controller take over the ownership of certain SubLUNs, but all SubLUNs on the affected drive group were not transferred.
\p\p\1
ASC/ASCQ/Sense Key: 91 33 5 \0\p
Illegal Operation For Controller State \p
The requested Mode Select operation could not be completed due to the current state of the controller. This error could be returned for the following reasons: \p\p
\{\1 o \0\} The user attempted to fail or unfail the alternate controller, but the current controller is in the Passive mode of operation. \p
\{\1 o \0\} The user attempted to switch from Active-Passive mode of operation to Active-Active mode, but this is a single controller system. \p
\{\1 o \0\} The user attempted to direct this controller to fail the alternate controller, but the alternate controller still owns some of the configured logical units.
\p\p\1
ASC/ASCQ/Sense Key: 91 36 5 \0\p
Command Lock Violation \p
The controller received a Write Buffer Download Microcode, Send Diagnostic, or Mode Select command, but only one such command is allowed at a time and there was another such command active.
\p\p\1
ASC/ASCQ/Sense Key: 91 50 5 \0\p
Illegal Operation For Drive Group State \p
An operation was requested that cannot be executed because of the current state of the drive group (such as a modification operation being performed).
\p\p\1
ASC/ASCQ/Sense Key: 91 51 5 \0\p
Cannot Perform Modification - Insufficient Reserved Capacity \p
A modification operation (RAID level, segment size, capacity expansion, or defragmentation) could not be performed because there is insufficient capacity reserved on each drive for internal configuration purposes. If you want to complete this modification, the only solution is to back up the data on the drive group's LUNs, delete the LUNs, and recreate them with the desired RAID level, number of drives, and segment size.
\p\p\1
NOTE\0: There may be a decrease in drive group capacity when recreating the LUNs (about 38 MB per drive), since this drive group was originally created with pre-2.05 controller firmware and release 3.X controller firmware requires more reserved capacity per drive for internal configuration purposes.
\p\p\1
ASC/ASCQ/Sense Key: 91 53 5 \0\p
Illegal Reconfiguration Request \p
The controller cannot complete the LUN modification operation requested. There is not enough space on the drives to complete the operation. To change the configuration, the user must delete the drives and re-create them.
\p\p\1
ASC/ASCQ/Sense Key: 94 01 5 \0\p
Invalid Request Due To Current LUN Ownership \p
The operation is not allowed because the controller does not own the logical unit. The user should change the logical unit's owner, or attempt the operation from the owning controller.
\p\p\1
ASC/ASCQ/Sense Key: 95 01 4 \0\p
Extended Drive Insertion/Removal Signal \p
The controller has detected that the drive insertion/removal signal is permanently active. The user should ensure that the drives on the affected channel are properly seated.
\p\p\1
ASC/ASCQ/Sense Key: 95 02 (6) \0\p
Controller Removal/Replacement Detected \p
The controller detected the activation of the signal used to indicate that the alternate controller has been removed or replaced.
\p\p\1
ASC/ASCQ/Sense Key: 98 01 (6) \0\p
Multiple Drive Trays With Same ID \p
The controller has determined that there are multiple drive trays with the same ID selected. The user should ensure that each drive tray has a unique ID setting.
\p\p\1
ASC/ASCQ/Sense Key: A0 00 (6) \0\p
Write-Back Cache (With Mirroring) Could Not Be Enabled \p
The user requested the controller to enable write-back cache, but the controller was unable to do so because: \p\p
\{\1 o \0\} A battery was charging after a power cycle. If the RAID Module was power cycled, the user should wait approximately 12 to 15 minutes. The caching should be enabled again. \p\p
\{\1 o \0\} Mirroring was requested, but this controller cannot do so because: \p
(1) its batteries are not operational, and the cache-without-batteries (CWOB) feature is disabled, or \p
(2) its batteries are not present, and the CWOB feature is disabled, or \p
(3) the alternate controller's batteries are either not present or not operational, and the CWOB feature is disabled. The user should replace this controller with another one, or should turn off write-back caching. \p\p
\{\1 o \0\} The controller was mirroring data, and the Force Write Through on Two Minute Warning bit (FWT) is set, and it has now detected a two minute warning from the UPS. It will now transition to write-through mode until full AC power has been restored. The user should not re-enable write-back caching until full AC power is restored. \p\p
\{\1 o \0\} Mirroring was requested, but the alternate controller is not ready to mirror. The user should ensure that the alternate controller is present in the RAID Module and that it is functional. \p\p
\{\1 o \0\} The controller was mirroring data, and now detects that the mirrors are out of synchronization, because: \p
(1) a mirror operation failed, or \p
(2) the alternate controller was removed. \p
The user should ensure that the alternate controller is present in the RAID Module and that it is functional. \p\p\1
ASC/ASCQ/Sense Key: A1 00 (6) \0\p
Write-Back Cache (With Mirroring) Could Not Be Enabled - Cache Size Mismatch \p
The controller will not allow mirroring to be enabled if the alternate controller's cache size is different. The user must ensure that both controllers in the subsystem have the same cache size.
\p\p\1
ASC/ASCQ/Sense Key: A4 00 (6) \0\p
Hot Spare Drive Smaller Than At Least One Drive In The Subsystem \p
A drive designated as Hot Spare does not have the capacity to cover all of the drives in the RAID subsystem. The user should attempt to ensure that the Hot Spare drive has a capacity as large as the largest capacity drive in the RAID subsystem. Note that the Hot Spare drive will still be used to cover any smaller capacity drives.
\p\p\1
ASC/ASCQ/Sense Key: A6 00 (6) \0\p
Recovered Processor Memory Failure \p
The controller has detected and corrected a recoverable error in processor memory.
\p\p\1
ASC/ASCQ/Sense Key: A7 00 (6) \0\p
Recovered Data Buffer Memory Error \p
The controller has detected and corrected a recoverable error in the data buffer memory. Sense bytes 34-36 will contain the count of errors encountered and recovered.
\p\p\1
ASC/ASCQ/Sense Key: C0 00 4,(6) \0\p
The Inter-controller Communications Channel Has Failed \p
The controller has detected the failure of the communications link between the redundant controllers. A switch to Active-Active mode of operation will not be allowed.
\p\p\1
ASC/ASCQ/Sense Key: D0 06 4 \0\p
Drive I/O Time-Out \p
The controller destination I/O timer expired while waiting for a drive command to complete. This error is possible if the drive's power was suddenly turned off, or if there is an extended reset on the channel due to an incomplete drive removal/insertion. The user should check that the drive is still powered up. If there was a drive removal/insertion on this channel a few seconds ago, the user should ensure that the drive is completely seated in the subsystem.
\p\p\1
ASC/ASCQ/Sense Key: D1 0A 4 \0\p
Drive Reported Busy Status \p
A drive returned a Busy status in response to a command.
\p\p\1
ASC/ASCQ/Sense Key: E0 XX 4 \0\p
Destination Channel Error \p
If XX = 00 - 07, it indicates the Sense Key returned by the drive after a Check Condition status. If XX = 10, it indicates that a bus level error occurred. If the same error continues to be returned, the user should replace the drive. \p\p\1
Related Topics \label "ascrt"\0\p
\{\3\goto "Hardware Message Details" Hardware Message Details\} \p
\{\3\goto "How To List Different Types Of Messages" How To List Different Types Of Messages\} \p
\{\3\goto "How To Use Message Log" How To Use Message Log\} \p
\{\3\goto "How To Use Recovery Guru" How To Use Recovery Guru/Health Check\} \p
\{\3\goto "Information In Show Details" What Information Appears in Show Details?\}
\p\p
\{\7\goto "asctop" Top Of Page\}\p
\keyword "action to take" \keyword "cause, probable" \keyword "probable cause" \keyword "ASC/ASCQ" \keyword "error detection" \keyword "hardware errors" \keyword "sense keys" \keyword "sense codes" \keyword "code" \keyword "controller error codes" \keyword "FRU codes"

\topic "Copy To Clipboard" \p\1
Copy To Clipboard \label "copytop" 
\p\p
Fast Find -- \{\5\goto "copyrt" Related Topics\} \p\p\1
Procedure \p\p\0
Using Message Log >> Show Details, you can copy the contents of the detailed message to the clipboard. You need to perform the following steps for EACH detailed message that you want to copy. \p\p
1. From the top menu, select Edit >> Copy to Clipboard. \p\p
This automatically highlights the text of the detailed message and copies it to the clipboard. \p\p
2. Before copying additional items or exiting this program, use an appropriate application to save the clipboard contents to an editor or desired file. \p\p
Use this option to save details into a permanent record or to forward to your Customer Services Representative. \p\p\1
Related Topics \label "copyrt"\0\p
\{\3\goto "How To Use Message Log" How To Use Message Log\} \p
\{\3\goto "Selecting Messages" Selecting Messages\}
\p\p
\{\7\goto "copytop" Top of Page\} \p
\keyword "copy" \keyword "Message Log" \keyword "save" \keyword "Edit menu"

\topic "Selecting Messages" \p\1
Selecting Messages \label "highlighttop" 
\p\p
Fast Find -- \{\5\goto "highlightshow" Show Details\} | \{\5\goto "highlightrt" Related Topics\}
\p\p\1
Summary Information Screen \0\p\p
At this screen, you can select messages for viewing detailed information in Message Log. \p\p\1
Selection Options\0 -- Choose one: \p\p
\{\1 o \0\} To select all messages, select either (1) Edit >> Select All from the top menu, or (2) the Select All button. \p\p
\{\1 o \0\} Single-click to highlight a single message. \p\p\1
NOTE\0: Double-clicking on a single message automatically displays the detailed information screen for that message. \p\p
\{\1 o \0\} Press Shift + click to highlight a series of messages. For example, single-click to highlight the top item in a list, then press Shift + click on the last item in the list to highlight all the items in that list. \p\p
\{\1 o \0\} Press Control + click to highlight messages not in a series. For example, single-click to highlight one item in a list, then press Control + click on another item to highlight it as well. Do this for every item you want to highlight. Pressing Control + click on an already highlighted item deselects it. \p\p\1
Action Options\0 -- To view a message's detailed contents, select either Show Details, or double-click a message. \p\p\1
Show Details Screen \label "highlightshow"\0\p\p
You can select detailed messages and copy them to the clipboard. You must copy each item individually. Also, before copying additional items or exiting this program, use an appropriate application to save the clipboard contents to an editor or desired file. \p\p
For detailed procedures, select Copy To Clipboard in the \{\5\goto "highlightrt" Related Topics\} list below.
\p\p\1
Related Topics \label "highlightrt"\0\p
\{\3\goto "Copy To Clipboard" Copy To Clipboard\} \p
\{\3\goto "How To Save The Log As Another File" How To Save The Log As Another File Name\} \p
\{\3\goto "How To Use Message Log" How To Use Message Log\}
\p\p
\{\7\goto "highlighttop" Top Of Page\}\p
\keyword "selecting messages" \keyword "message selection" \keyword "Edit menu" \keyword "view messages"

\topic "How To Change The Reconstruction Rate" \p\1
How To Change The Reconstruction Rate \label "reconchgtop" 
\p\p
Fast Find -- \{\5\goto "reconchgmt" All LUNs\} | \{\5\goto "reconchgstat" LUNs Reconstructing\} | \{\5\goto "reconchgrt" Related Topics\} \p\p\1
Note\0: Changing the Reconstruction Rate also changes the rate of \{\2\bring_popup "Background Formatting" background\} formatting. \p\p\1
Procedure For Any Logical Unit Whether Or Not Reconstruction Is Occurring \0\label "reconchgmt"\p\p
1. Select the Maintenance/Tuning Application. \p\p
2. Select RAID Module >> LUN Reconstruction Rate. \p\p
Remember, the LUN Reconstruction Rate option is grayed out if you select All RAID Modules. \p\p
3. For each LUN you want to change, change the reconstruction \{\2\bring_popup "Reconstruction Rate" rate\} by moving the Slider bar toward either: \p\p
-- System performance -- to speed system I/O and slow reconstruction, OR \p\p
-- Reconstruction performance -- to speed up the reconstruction rate and slow system I/O. \p\p
4. Select Save for your rate changes to take effect. \p\p\1
Procedure For Logical Units Undergoing Reconstruction \0\label "reconchgstat" \p\p
1. Select the Status Application. \p\p
2. Select RAID Module >> LUN Reconstruction. \p\p
Remember, the LUN Reconstruction option is grayed out if you select All RAID Modules. Also, only the LUNs currently undergoing reconstruction are displayed. If no LUNs are currently reconstructing on the selected RAID Module, select OK in the message box, then select another module or option. \p\p
3. Change the reconstruction \{\2\bring_popup "Reconstruction Rate" rate\} by moving the Slider bar toward either: \p\p
-- System performance -- to speed system I/O and slow reconstruction, OR
\p\p
-- Reconstruction performance -- to speed up the reconstruction rate and slow system I/O. \p\p\1
NOTE\0: You can only change the reconstruction rate for LUNs that are currently reconstructing. If a LUN shows "Waiting to reconstruct," you will be able to change its rate when the reconstruction operation actually begins. \p\p
The rate is automatically set when you move the Slider bar; however, you may notice some delay in the system's response if many or very large LUNs are reconstructing.
\p\p\1
Related Topics\0\label "reconchgrt"\p
\{\3\goto "Reconstruction Concept" Reconstruction\} \p
\{\3\goto "Reconstruction Restrictions" Restrictions/Cautions\} \p
\{\3\goto "Reconstruction Troubleshooting" Troubleshooting\} \p
\{\3\subtopic "What Are The Rate Settings?" What Are The Reconstruction Rate Settings?\}
\p\p
\{\7\goto "reconchgtop" Top Of Page\}\p
\keyword "reconstruction" \keyword "rate" \keyword "LUN Reconstruction" \keyword "LUN Reconstruction Rate" \keyword "changing settings"

\topic "What Are The Rate Settings?" \p\1
What Are The Reconstruction Rate Settings? \label "reconratetop" 
\p\p
Fast Find -- \{\5\goto "reconrateset" Settings\} | \{\5\goto "reconratert" Related Topics\}
\p\p\0
You can change the reconstruction rate to affect how much processing time is allocated for reconstruction and for system performance. The Reconstruction Rate also affects the speed of \{\2\bring_popup "Background Formatting" background\} formatting. Change the reconstruction rate by moving the Slider bar toward either system performance (to speed system I/O and slow reconstruction) or reconstruction performance (to speed reconstruction rate and slow system I/O). \p\p
The reconstruction rate settings each correspond to a different interval, based on the number of blocks reconstructed and the number of seconds delay between reconstruction operations for system I/O operations to take place. The controller reconstructs data (or formats a LUN) one segment at a time. When it has enough reconstructed segments to form a block, it delays for a specific number of seconds. \p\p\1
Settings On The Slider Bar \0\label "reconrateset"\p\p
From left to right, the points on the Slider bar indicate the following reconstruction rates (blocks/seconds delay). Note that each 1024 block = 512 KB. \p\p
\{\1 o \0\} Slow -- 1024 blocks/0.8 second delay \p\p
\{\1 o \0\} Medium slow -- 1024 blocks/0.4 second delay \p\p
\{\1 o \0\} Medium -- 1024 blocks/0.2 second delay \p\p
\{\1 o \0\} Medium fast -- 1024 blocks/0.1 second delay \p\p
\{\1 o \0\} Fast -- reconstruct with no delays
\p\p\1
Related Topics \0\label "reconratert"\p
\{\3\goto "How To Change The Reconstruction Rate" How To Change The Reconstruction Rate\} \p
\{\3\goto "How To View Reconstruction Progress" How To View Reconstruction Progress\} \p
\{\3\goto "Reconstruction Concept" Reconstruction\}
\p\p
\{\7\goto "reconratetop" Top Of Page\}\p
\keyword "reconstruction" \keyword "rate" \keyword "settings"

\topic "How To View Reconstruction Progress" \p\1
How To View Reconstruction Progress \label "reconviewtop"\p\p
Fast Find -- \{\5\goto "reconviewrt" Related Topics\}
\p\p\1
Procedure \0\p\p
1. Select the Status Application. \p\p
2. Select RAID Module >> LUN Reconstruction . \p\p
Remember, the LUN Reconstruction option is grayed out if you select All RAID Modules. Also, only the LUNs undergoing \{\2\bring_popup "Reconstruction" reconstruction\} are displayed. If no LUNs are currently reconstructing on the selected \{\2\bring_popup "RAID Module" RAID Module\}, select OK in the message box, then select another module or option. \p\p
3. View reconstruction progress. \p\p
Each histogram shows the amount of reconstruction accomplished as a percentage. The response time for updating these histograms depends on the number and size of the LUNs undergoing reconstruction and on the \{\2\bring_popup "Reconstruction Rate" rate\} setting for the reconstruction operation. Furthermore, if you exit LUN Reconstruction, any logical units that have completed reconstruction (show 100%) do not appear the next time you select LUN Reconstruction.\p\p
You can not view the progress of \{\2\bring_popup "Background Formatting" background\} formatting with this option.
\p\p\1
Related Topics\0\label "reconviewrt"\p
\{\3\goto "How To Change The Reconstruction Rate" How To Change The Reconstruction Rate\} \p
\{\3\goto "Reconstruction Concept" Reconstruction\} \p
\{\3\goto "Reconstruction Restrictions" Restrictions/Cautions\} \p
\{\3\goto "Reconstruction Troubleshooting" Troubleshooting\} \p
\{\3\goto "What Are The Rate Settings?" What Are The Rate Settings?\}
\p\p
\{\7\goto "reconviewtop" Top Of Page\}\p
\keyword "view reconstruction" \keyword "view progress" \keyword "progress" \keyword "reconstruction"

\topic "How To Use Performance Monitor" \p\1
How To Use Performance Monitor \label "performtop" 
\p\p
Fast Find -- \{\5\goto "performopt" Options\} | \{\5\goto "performrt" Related Topics\}
\p\p\1
Procedure \0\p\p
1. Select the Status Application >> RAID Module. \p\p
2. Select Performance Monitor. \p\p
Remember, this option is grayed out if you select All RAID Modules. \p\p
3. From the Performance Monitor Settings screen, highlight the \{\2\bring_popup "Controller" controllers\} and \{\2\bring_popup "Logical Unit" LUNs\} you want to monitor (or use Select All). \p\p
4. Select the polling \{\2\bring_popup "Polling Interval" interval\} (frequency in seconds) at which you want to monitor performance and select OK. \p\p
5. From the Performance Monitor main screen, select Start to begin monitoring. \p\p
6. When you are finished monitoring, select Stop. \p\p
Selecting Stop is the only direct way to stop monitoring. Selecting another Status Application option or attempting to exit the Status Application prompts a confirmation box asking if the Performance Monitor session should really be stopped. \p\p\1
NOTE\0: Only one \{\2\bring_popup "RAID Module" RAID Module\} can be monitored at a time. However, multiple instances of the Status Application can be opened to view other modules. 
\p\p\1
Options \0\label "performopt"\p\p
\{\3\subtopic "How To Use File >> Save Performance Data" How To Use File >> Save Performance Data\} \p\p\1
Related Topics \label "performrt"\0\p
\{\3\goto "Performance Monitor Questions" Common Questions\} \p
\{\3\subtopic "Interpreting Performance Monitor Data" Interpreting Performance Monitor Data\} \p
\{\3\goto "Performance Monitor Restrictions" Restrictions/Cautions\} \p
\{\3\goto "Performance Monitor Troubleshooting" Troubleshooting\} \p
\{\3\subtopic "Information In Performance Monitor" What Information Appears in Performance Monitor?\} \p
\p\p
\{\7\goto "performtop" Top Of Page\} \p
\keyword "Performance Monitor" \keyword "monitoring performance" \keyword "data performance" \keyword "settings" \keyword "polling interval" \keyword "interval" \keyword "view performance data" \keyword "rate" \keyword "system performance" \keyword "monitoring modules" \keyword "changing settings"

\topic "How To Use File >> Save Performance Data" \p\1
How To Use File >> Save Performance Data (Saving Performance Monitor Data) \label "performsavetop"\p\p
Fast Find -- \{\5\goto "performsavert" Related Topics\} \p\p\1
Procedure \0\p\p
1. Select Status Application >> RAID Module >> Performance Monitor. \p\p
2. Once you have started monitoring a selected \{\2\bring_popup "RAID Module" RAID Module\}, select File >> Save Performance Data. \p\p
If you are in the Status Application, but not currently running Performance Monitor, this option will be grayed out. \p\p
3. Enter the directory and filename where you want to save the data. \p\p
On UNIX systems, you can use the \{\2\bring_popup "Filter" filter\} to direct your save to a specific directory, filename, and file extension. \p\p
4. Select OK. The data is saved to the specified file. \p\p
5. Select OK at the "file successfully saved" confirmation screen. 
\p\p\1
Related Topics \label "performsavert"\0\p
\{\3\goto "Performance Monitor Questions" Common Questions\} \p
\{\3\goto "How To Use Performance Monitor" How To Use Performance Monitor\} \p
\{\3\goto "Interpreting Performance Monitor Data" Interpreting Performance Monitor Data\} \p
\{\3\goto "Performance Monitor Restrictions" Restrictions/Cautions\} \p
\{\3\goto "Performance Monitor Troubleshooting" Troubleshooting\}
\p\p
\{\7\goto "performsavetop" Top Of Page\} \p
\keyword "save" \keyword "Performance Monitor" \keyword "File menu" \keyword "data performance"

\topic "Interpreting Performance Monitor Data" \p\1
Interpreting Performance Monitor Data \label "interprettop" 
\p\p
Fast Find -- \{\5\goto "interpretcache" Cache Hits\} | \{\5\goto "interpretkb" KB/Sec\} | \{\5\goto "interpretio" I/O/Sec\} | \{\5\goto "interpretrt" Related Topics\}
\p\p\0
The following considerations apply in analyzing the data collected by the Performance Monitor (Status Application). \p\p\1
Total I/Os \p\p\0
This field is useful for monitoring the I/O activity to a specific \{\2\bring_popup "Controller" controller\} and a specific \{\2\bring_popup "Logical Unit" LUN\}. This is needed to identify possible I/O "hot spots." It is also useful to be able to identify actual I/O patterns to the individual LUNs and compare those with the expectations based on the application. If a particular LUN has considerably more I/O activity, consider moving the LUN to the other controller in the \{\2\bring_popup "RAID Module" RAID Module\}. If a particular LUN has considerably more I/O activity, consider moving the LUN to another SCSI or system bus. The system administrator should also consider moving the storage set to another array controller or distributing the storage set across multiple modules and LUNs. \p\p\1
Read % \0\p\p
Knowing the read/write ratio of an application gives more insight into the actual application behavior. With redundant RAID Levels 1 and 5, write performance is typically slower than read performance, and \{\2\bring_popup "RAID 5" RAID 5\} is slower than \{\2\bring_popup "RAID 1" RAID 1\}. If a high amount of write activity is occurring, the user might want to consider changing the RAID \{\2\bring_popup "RAID Level" Level\} from RAID 5 to RAID 1. This fact alone may not provide enough information if \{\2\bring_popup "Write Caching" write\} caching is enabled. \p\p\1
Cache Hits % \label "interpretcache"\0\p\p
Indicates the percentage of read operations that were satisfied from the array cache (did not require a disk access). A higher percentage is better. Increasing the amount of installed cache increases the possibility of a cache hit, but there is no guarantee that more cache will improve cache hit percentage. This field can also be used to determine the effectiveness of \{\2\bring_popup "Cache Read Ahead" cache read ahead\} (also known as read request prefetch). By default, the controller does not perform any read prefetching. If Cache Read Ahead is enabled, you can measure the effectiveness by noticing changes in the cache hit percentage. \p\p\1
KB/Sec Rates \label "interpretkb"\p\p\0
The I/O size and the I/O rate determine the transfer rates of the controller. In general, a small host I/O request size results in lower throughput rates (but provides faster I/O rates and shorter response times). With larger host I/O request sizes, higher throughput rates are possible. Wide Ultra SCSI supports sustained data transfer rates of up to 40MB/second with large host I/O sizes. The maximum transfer rates with relatively small I/O sizes, 4096 bytes, is approximately 17 MB/second. \p\p\1
IO/Sec Rates \label "interpretio"\0\p\p
Indicates current and maximum I/O rates. This can be useful in determining if the module is performing up to expectations based on access pattern, I/O size, RAID Level, and number of drives in the module. Sequential access to the module results in higher I/O rates. Higher write I/O rates are experienced with write caching enabled compared to disabled. The higher the cache hit rate, the higher I/O rates will be. \p\p\1
Related Topics \label "interpretrt"\0\p
\{\3\goto "How To Use Performance Monitor" How To Use Performance Monitor\} \p
\{\3\goto "How To Use File >> Save Performance Data" Saving Performance Monitor Data\}
\p\p
\{\7\goto "interprettop" Top Of Page\}\p
\keyword "Performance Monitor" \keyword "data performance" \keyword "details, performance" \keyword "results" \keyword "values"

\topic "Information In Performance Monitor" \p\1
What Information Appears in Performance Monitor? \label "infoperformtop" 
\p\p
Fast Find -- \{\5\goto "infoperform" Main Screen\} | \{\5\goto "infoperformopt" Options\} | \{\5\goto "infoperformrt" Related Topics\}
\p\p\1
SETTINGS SCREEN \0\p\p
This screen allows you to choose the specific \{\2\bring_popup "Controller" controllers\} or \{\2\bring_popup "Logical Unit" LUNs\} you want to monitor, or you may choose Select All to monitor all controllers and LUNs in the selected \{\2\bring_popup "RAID Module" RAID Module\}. \p\p
The polling \{\2\bring_popup "Polling Interval" interval\} area allows you to select the frequency (in seconds) that the Performance Monitor checks the system activity in the module and updates the performance data. \p\p
Once all the selections have been made, choose OK to accept your changes, or Cancel to leave this screen without making any changes. \p\p\1
MAIN SCREEN \label "infoperform"\0\p\p
The dynamic area on the main Status screen displays the Performance Monitor data. The screen is updated at the frequency selected in the Settings screen (polling interval). \p\p
The fields give the following information: \p\p\1
Devices\0: Controller \{\2\bring_popup "Controller Name/ID" name\} listed as Controller A or B; and LUNs listed as LUN 0, LUN 1, etc. The LUNs are listed numerically under the controller that owns them. \p\p\1
Total I/Os\0: The number of total I/Os performed by this device since monitoring was started. When this number exceeds 99,999, it is displayed as 100 K (kilobytes) until the number reaches 9999K, at which time it is displayed as M (megabytes). For amounts less that 100 M, the value is displayed in tenths (for example, 12.3 M). \p\p\1
Read %\0: The percentage of total I/Os that are read operations for this device. Write percentage can be calculated as 100 minus this value. \p\p\1
Cache Hit %\0: The percentage of reads that are fulfilled by data from the cache rather than requiring an actual read from disk. \p\p\1
Current KB/Sec\0: The current KB (kilobytes) per second. Current means the number of KB/second since the last time the polling interval elapsed, causing an update to occur, or since the update button was pressed. \p\p\1
Max KB/Sec\0: The highest value achieved by the current KB/sec column for this polling session (since the Start button was pressed). \p\p\1
Current I/O/Sec\0: The current I/Os per second. Current means the number of I/Os per second since the last time the polling \{\2\bring_popup "Polling Interval" interval\} elapsed, causing an update to occur, or since the update button was pressed. \p\p\1
Max I/O/Sec\0: The highest value achieved by the current IO/sec column for this polling session (since the Start button was last pressed). \p\p
Controller values, displayed in the main screen, represent the totals for all LUNs owned by the controller, not just the LUNs presently selected for monitoring. Module totals, displayed directly below the main screen, represent totals for both controllers in the controller \{\2\bring_popup "Redundant Controller Pair" pair\}, regardless if one, both, or neither are selected for monitoring. \p\p\1
Module Totals\0: This line below the fields shows the statistics for all controllers and LUNs in the selected RAID Module. \p\p\1
OPTIONS \label "infoperformopt"\p\p\1
Start/Stop Button\0 -- Starts or Stops the monitoring of a particular RAID Module. \p\p\1
Update Button\0 -- You can update the screen at any time by selecting Update, regardless of what polling interval you select. \p\p\1
Settings Button\0 -- This takes you back to the Performance Monitor settings screen, where you can change the polling interval. However, you must first select Stop on the Main screen before you select a different controller or LUNs on the settings screen. \p\p
Below the buttons, there is a bar that indicates the time and date you began monitoring, the time and date you stopped monitoring, and calculates how long you spent monitoring a particular RAID Module. \p\p\1
NOTE\0: There is also a status line at the bottom of the screen that provides information about each of the options. Also, when an option is grayed out, the status line provides an indication of why. To receive information about a particular option, move the mouse over the appropriate button. For top menu options, you must click on the option and hold down the left-mouse button. \p\p\1
Related Topics \label "infoperformrt"\0\p\p
\{\3\goto "Performance Concept" Performance\} \p
\{\3\goto "How To Use Performance Monitor" How To Use Performance Monitor\}
\p\p
\{\7\goto "infoperformtop" Top Of Page\}\p
\keyword "Performance Monitor" \keyword "settings" \keyword "total I/Os" \keyword "Read %" \keyword "Cache Hit %" \keyword "KB/sec rates" \keyword "I/O/sec rates" \keyword "rate" \keyword "screen description"

\topic "Recovery Application" \p\1
Recovery Application \label "recvtop"
\p\p
Fast Find -- \{\5\goto "recvtaskproc" Procedures\} | \{\5\goto "recvtaskrt" Related Topics\}
\p\p\1
Recovery Tasks \0\p\p
The following tasks are available from the tool bar or from the Options menu for the Recovery Application:
\p\p\1
\{\1 o \} Recovery Guru/Health Check \0 -- check selected RAID Modules for component failures and, if detected, recover from them by following step-by-step instructions
\p\p\1
\{\1 o \} Manual Parity Check/Repair \0 -- manually check and repair parity on selected logical units
\p\p\4
CAUTION \0\p
Always use Recovery Guru/Health Check to ensure the problem is correctly diagnosed BEFORE attempting any manual recovery procedure. Incorrectly performing a procedure or performing the wrong procedure could cause equipment damage or data loss. Recovery Guru provides step-by-step procedures to make sure that you are correcting the right problem and directs you when to use the manual recovery options.
\p\p\1
\{\1 o \} Options >> Manual Recovery >> Controller Pairs \0 -- manually place controllers online or offline when instructed
\p\p\1
\{\1 o \} Options >> Manual Recovery >> Drives \0 -- manually fail, reconstruct, or revive drives when instructed
\p\p\1
\{\1 o \} Options >> Manual Recovery >> Logical Units \0 -- manually format or revive logical units/drive groups when instructed
\p\p\1
Procedures \0\label "recvtaskproc"\p\p
\{\3\subtopic "How To Use Recovery Guru" How To Use Recovery Guru/Health Check\} \p\p
\{\3\subtopic "How To Use Manual Parity Check/Repair" How To Use Manual Parity Check/Repair \} \p\p
\{\3\subtopic "How To Use Options >> Manual Recovery" How To Use Options >> Manual Recovery\}
\p\p\1
Related Topics \0\label "recvtaskrt"\p
\{\3\goto "Common Question Topics" Common Questions\} \p
\{\3\goto "Restriction/Caution Topics" Restrictions/Cautions\} \p
\{\3\goto "Troubleshooting Topics" Troubleshooting\} \p
\{\3\goto "Parity Concept" Parity\} \p
\{\3\goto "Statuses Concept" Statuses\}
\p\p
\{\7\goto "recvtop" Top Of Page\} \p
\keyword "tasks, Recovery Application" \keyword "summary of tasks" \keyword "task summary" \keyword "Recovery Application" \keyword "Recovery Guru" \keyword "Manual Parity Check/Repair" \keyword "Manual Recovery options"

\topic "How To Use Recovery Guru" \p\1
How To Use Recovery Guru/Health Check \label "gurutop" 
\p\p
Fast Find -- \{\5\goto "gururt" Related Topics\}
\p\p\1
Procedure \0\p\p
1. Select Recovery Application >> RAID Module. \p\p
2. Select Recovery Guru/Health Check. \p\p
3. With the top result highlighted, select Show Procedure and follow the step-by-step instructions provided to correct the problem. \p\p
The Show Procedure option is grayed out if all the modules are diagnosed as \{\2\bring_popup "Optimal Mode" Optimal\}. Also, you cannot highlight any module that shows an Optimal result. \p\p
4. Continue highlighting each result (top-to-bottom) until all problems have been corrected.
\p\p\1
Related Topics \0\label "gururt"\p
\{\3\subtopic "Failure Types Reported By Recovery Guru" Failure Types Reported By Recovery Guru\} \p
\{\3\goto "Recovery Guru Restrictions" Restrictions/Cautions\} \p
\{\3\subtopic "Information In Recovery Guru" What Information Appears In Recovery Guru?\} \p
\{\3\goto "When To Use Recovery Guru" When Should I Use Recovery Guru?\}
\p\p
\{\7\goto "gurutop" Top Of Page\}\p
\keyword "Recovery Guru" \keyword "Health Check, see Recovery Guru items" \keyword "data recovery" \keyword "component recovery" \keyword "error detection" \keyword "details, recovery" \keyword "system performance"

\topic "Failure Types Reported By Recovery Guru" \p\1
Failure Types Reported By Recovery Guru/Health Check \label "failgurutop" 
\p\p
Fast Find -- \{\5\goto "failguruhelp" Help Procedures\} | \{\5\goto "failgururt" Related Topics\}
\p\p\0
When you run Recovery Guru/Health Check on a \{\2\bring_popup "RAID Module" RAID Module\}, it may report one or more failure types in the following areas: modules, controllers, LUNs, drives, other hardware (such as batteries, fans, and power supplies), and \{\2\bring_popup "Independent Controller Configuration" independent\} controller configuration. \p\p
When Recovery Guru diagnoses a failure type, select Show Procedure for step-by-step instructions on correcting the problem. These procedures also provide component-specific status and location information. Start with the top failure in the list, if more than one is listed. It is possible to see a RAID Module listed more than once when it has multiple failures. If this happens, Recovery Guru lists failures in the order (top-to-bottom) that you should fix them. \p\p\1
Recovery Guru Help Procedures \0\label "failguruhelp"\p\p
Even when Recovery Guru reports all modules as Optimal, you can view or print any recovery procedure by selecting Help >> Recovery Guru Procedures from the top menu in the Recovery Application. However, you should use these topics for reference only; they do NOT contain the same component-specific information as the Show Procedure instructions displayed after running Recovery Guru.
\p\p\1
Related Topics \0\label "failgururt"\p
\{\3\goto "Failure Types Concept" Failure Types\} \p
\{\3\goto "How To Use Recovery Guru" How To Use Recovery Guru\} \p
\{\3\goto "Recovery Guru Restrictions" Restrictions/Cautions\}
\p\p
\{\7\goto "failgurutop" Top Of Page\}\p
\keyword "status reporting" \keyword "error detection" \keyword "failures" \keyword "Recovery Guru"

\topic "Information In Recovery Guru" \p\1
What Information Appears In Recovery Guru/Health Check? \label "infogurutop" 
\p\p
Fast Find -- \{\5\goto "infogururt" Related Topics\}
\p\p\0
When you select Recovery Guru, you see whether or not the selected \{\2\bring_popup "RAID Module" RAID Module\} has any failures. \p\p\1
RAID Module\0: Indicates the specific module. \p\p
It is possible to see a RAID Module listed more than once when it has multiple failures. For example, if a RAID Module has both a failed battery and a failed fan, two entries appear for this module: Failed Fan on one line and Failed Battery on another line. \p\p\1
Result\0: Lists the component failure for the particular module. Possible failures appear for modules, controllers, LUNs, drives, subsystem components, and miscellaneous. \p\p\1
Show Procedure\0: Displays a help window with the specific procedure for the failure type highlighted when you select this option. \p\p\1
Related Topics \0\label "infogururt"\p
\{\3\goto "Failure Types Reported By Recovery Guru" Failure Types Reported By Recovery Guru\} \p
\{\3\goto "How To Use Recovery Guru" How To Use Recovery Guru\}
\p\p
\{\7\goto "infogurutop" Top Of Page\}\p
\keyword "results" \keyword "recovery information" \keyword "details, recovery" \keyword "Recovery Guru" \keyword "screen description" \keyword "Show Procedures"

\topic "How To Use Manual Parity Check/Repair" \p\1
How To Use Manual Parity Check/Repair \label "manparitytop" 
\p\p
Fast Find -- \{\5\goto "manparityrt" Related Topics\}
\p\p\1
Procedure \0\p\p
1. Select the Recovery Application >> RAID Module. \p\p
2. Select Manual Parity Check/Repair. \p\p
3. Highlight one or more \{\2\bring_popup "Logical Unit" logical units\} (LUN) in the list with a status of \{\2\bring_popup "Optimal Mode" Optimal\}. \p\p
4. Select Start Parity Check/Repair. \p\p
This option is grayed out if you select one or more LUNs that are either RAID Level 0, or have a LUN status other than Optimal. \p\p
5. The Repair option screen is displayed. Select the repair option you want, either Check With Repair or Check Without Repair. \p\p
If you select Check Without Repair, any parity errors found will be logged, but not repaired. You can then attempt to locate and recover the file affected by the parity error, then run manual parity check again at a later time to repair the parity. \p\p
6. After you have selected the repair option, click OK to start the check. \p\p
7. View the progress of the parity \{\2\bring_popup "Parity Check/Repair" check/repair\} operation. \p\p
A new histogram appears for each selected LUN when its check begins. \p\p
When parity check/repair is completed, one of two confirmation boxes appears: \p\p
\{\1 o \0\} The parity check is completed and no inconsistencies were found. \p\p
\{\1 o \0\} The parity check is completed and inconsistencies were found and repaired (if repair was selected) on specific LUNs. \p\p\1
IMPORTANT \0\p
While parity check/repair is in progress, you cannot perform other Recovery tasks. You can select Cancel at any time during parity check. However, if you stop this operation, your parity has not been completely checked or repaired. \p\p
8. Select OK at the "Parity Complete" confirmation box. \p\p
You return to the logical units list. \p\p\1
Related Topics \0\label "manparityrt"\p
\{\3\goto "Parity Questions" Common Questions\} \p
\{\3\goto "Parity Concept" Parity\} \p
\{\3\goto "Parity Restrictions" Restrictions/Cautions\} \p
\{\3\goto "Parity Troubleshooting" Troubleshooting\}
\p\p
\{\7\goto "manparitytop" Top Of Page\}\p
\keyword "parity" \keyword "progress" \keyword "manual parity" \keyword "check parity" \keyword "repair parity" \keyword "view progress" \keyword "Manual Parity Check/Repair, see parity or manual parity items"

\topic "How To Use Options >> Manual Recovery" \p\1
How To Use Options >> Manual Recovery \label "manrecvtop" 
\p\p
Fast Find -- \{\5\goto "manrecvrt" Related Topics\}
\p\p\4
CAUTION \0\p
Always select Recovery Guru/Health Check to ensure the problem is correctly diagnosed BEFORE attempting any manual recovery procedure. Incorrectly performing a procedure or performing the wrong procedure could cause equipment damage or data loss. Recovery Guru provides step-by-step procedures to make sure that you are correcting the right problem and directs you when to use the manual recovery options. \p\p\1
Options \0\p\p
\{\3\subtopic "How To Use Manual Recovery >> Controller Pairs" How To Use Manual Recovery >> Controller Pairs \} \p\p
\{\3\subtopic "How To Use Manual Recovery >> Drives" How To Use Manual Recovery >> Drives\} \p\p
\{\3\subtopic "How To Use Manual Recovery >> LUNs" How To Use Manual Recovery >> LUNs\}
\p\p\1
Related Topics\0\label "manrecvrt"\p
\{\3\goto "Manual Recovery Questions" Common Questions\} \p
\{\3\goto "How To Use Recovery Guru" How To Use Recovery Guru/Health Check\} \p
\{\3\goto "Manual Recovery Restrictions" Restrictions/Cautions\} \p
\{\3\subtopic "Information In Options >> Manual Recovery" What Information Appears In Options >> Manual Recovery?\}
\p\p
\{\7\goto "manrecvtop" Top Of Page\}\p
\keyword "Options menu" \keyword "Manual Recovery options" \keyword "Options >> Manual Recovery, see Manual Recovery options items"

\topic "How To Use Manual Recovery >> Controller Pairs" \p\1
How To Use Manual Recovery >> Controller Pairs \label "mancrtltop" 
\p\p
Fast Find -- \{\5\goto "placeoff" Placing Offline\} | \{\5\goto "placeon" Placing Online\} | \{\5\goto "manctrlrt" Related Topics\} \p\p\4
CAUTION \0\p
Always select Recovery Guru/Health Check to ensure the problem is correctly diagnosed BEFORE attempting any manual recovery procedure. Incorrectly performing a procedure or performing the wrong procedure could cause equipment damage or data loss. Recovery Guru provides step-by-step procedures to make sure that you are correcting the right problem and directs you when to use the manual recovery options. \p\p\1
Procedure For Placing A Controller Offline \0\label "placeoff"\p\p
1. Select Recovery Application >> RAID Module. \p\p
2. From the top menu, select Options >> Manual Recovery >> Controller Pairs. \p\p
The Manual Recovery option is grayed out if you select All RAID Modules. Furthermore, the Controller Pairs option is grayed out if the RAID Module has only one controller. \p\p
3. Highlight the \{\2\bring_popup "Controller" controller\} you want to Place Offline. \p\p
4. Select Place Offline >> OK. \p\p
The Place Offline option is grayed out if the RAID Module already has one controller with an \{\2\bring_popup "Offline Controller Mode" Offline\} status. You can place only one controller for a module Offline at a time. \p\p\1
IMPORTANT \0\p
If you are using this option to replace the controller, WAIT one minute BEFORE inserting a new controller. \p\p
5. Select OK when the controller list updates the status to Offline. \p\p
You can also visually see the controller is Offline by checking the LED and fault lights on the controller. See the appropriate hardware manual for the location and function of these LEDs. \p\p\1
Procedure For Placing A Controller Online \0\label "placeon"\p\p
1. Select Recovery Application >> RAID Module. \p\p
2. From the top menu, select Options >> Manual Recovery >> Controller Pairs. \p\p
The Manual Recovery option is grayed out if you select All RAID Modules. Furthermore, the Controller Pairs option is grayed out if the RAID Module has only one controller. \p\p
3. Highlight the controller you want to Place Online. \p\p
4. Select Place Online >> OK. \p\p
The Place Online option is grayed out if both controllers in the RAID Module have an Optimal status. There can be only one controller Offline for the selected module. \p\p
5. Select OK when the controller list updates the status to \{\2\bring_popup "Optimal Mode" Optimal\}. \p\p\1
Related Topics \0\label "manctrlrt"\p
\{\3\goto "Manual Recovery Questions" Common Questions\} \p
\{\3\goto "How To Use Options >> Manual Recovery" How To Use Options >> Manual Recovery\} \p
\{\3\goto "How To Use Recovery Guru" How To Use Recovery Guru/Health Check\} \p
\{\3\goto "Possible Controller Statuses" Possible Controller Statuses\} \p
\{\3\goto "Manual Recovery Restrictions" Restrictions/Cautions\}
\p\p
\{\7\goto "mancrtltop" Top Of Page\}\p
\keyword "Options menu" \keyword "controller recovery" \keyword "Place Offline" \keyword "Place Online" \keyword "offline controller" \keyword "online controller" \keyword "Manual Recovery options" \keyword "replacing controller" \keyword "controller replacement" \keyword "stop I/Os"

\topic "How To Use Manual Recovery >> Drives" \p\1
How To Use Manual Recovery >> Drives \label "mandrvtop" 
\p\p
Fast Find -- \{\5\goto "faildrv" Fail\} | \{\5\goto "recondrv" Reconstruct\} | \{\5\goto "revivedrv" Revive\} | \{\5\goto "mandrvrt" Related Topics\} \p\p\4
CAUTION \0\p
Always select Recovery Guru/Health Check to ensure the problem is correctly diagnosed BEFORE attempting any manual recovery procedure. Incorrectly performing a procedure or performing the wrong procedure could cause equipment damage or data loss. Recovery Guru provides step-by-step procedures to make sure that you are correcting the right problem and directs you when to use the manual recovery options. \p\p\1
Procedure For Failing A Drive \label "faildrv"\0\p\p
1. Select Recovery Application >> RAID Module. \p\p
2. From the top menu, select Options >> Manual Recovery >> Drives. \p\p
The Manual Recovery option is grayed out if you select All RAID Modules. \p\p
3. Highlight the drive you want to fail. \p\p
4. Select Fail >> OK. \p\p
The Fail option is grayed out for drives with Failed or Replaced drive statuses or with Reconstructing or Formatting LUN statuses. An hourglass appears until the selected drive is failed, then the drive list shows updated status information. \p\p
5. Use the recommended procedure from Recovery Guru/Health Check >> Show Procedures to replace the drive. \p\p\1
Procedure For Reconstructing A Drive \label "recondrv"\0\p\p
1. Select Recovery Application >> RAID Module. \p\p
2. From the top menu, select Options >> Manual Recovery >> Drives. \p\p
The Manual Recovery option is grayed out if you select All RAID Modules. \p\p
3. Highlight the drive you want to reconstruct. \p\p
4. Select Reconstruct >> OK. \p\p
The Reconstruct option is grayed out for drives in a \{\2\bring_popup "RAID 0" RAID 0\} LUN or with Reconstructing or Formatting LUN statuses. You can only reconstruct drives with Failed or Replaced drive statuses in a RAID 1, 3, or 5 LUN. The drive status changes to Replaced and the LUN status changes to Reconstructing until the \{\2\bring_popup "Reconstruction" reconstruction\} operation is completed. \p\p\1
NOTE\0: You can view the reconstruction progress or change the reconstruction \{\2\bring_popup "Reconstruction Rate" rate\} using Status Application >> LUN Reconstruction. \p\p\1
Procedure For Reviving A Drive \label "revivedrv"\0\p\p
1. Select Recovery Application >> RAID Module. \p\p
2. From the top menu, select Options >> Manual Recovery >> Drives. \p\p
The Manual Recovery option is grayed out if you select All RAID Modules. \p\p
3. Highlight the drive you want to revive. \p\p
4. Select Revive >> OK. \p\p
The Revive option is grayed out for drives that do not have a status of Failed or with Reconstructing or Formatting LUN statuses. An hourglass appears until the revive drive is completed. \p\p
5. Select OK when the drive list updates the drive's status to \{\2\bring_popup "Optimal Mode" Optimal\}. \p\p
6. Select Manual Parity Check/Repair to check \{\2\bring_popup "Parity" parity\} on the revived LUNs in the drive group unless the LUNs on the drives are RAID 0 or the drives are unassigned. \p\p\1
Related Topics \0\label "mandrvrt"\p
\{\3\goto "Manual Recovery Questions" Common Questions\} \p
\{\3\goto "How To Use Manual Parity Check/Repair" How To Use Manual Parity Check/Repair\} \p
\{\3\goto "How To Use Options >> Manual Recovery" How To Use Options >> Manual Recovery\} \p
\{\3\goto "How To Use Recovery Guru" How To Use Recovery Guru/Health Check\} \p
\{\3\goto "How To View Reconstruction Progress" How To View Reconstruction Progress\} \p
\{\3\goto "Possible Drive Statuses" Possible Drive Statuses\} \p
\{\3\goto "Manual Recovery Restrictions" Restrictions/Cautions\}
\p\p
\{\7\goto "mandrvtop" Top Of Page\}\p
\keyword "Options menu" \keyword "reconstruction" \keyword "manual reconstruction" \keyword "data recovery" \keyword "drive recovery" \keyword "Revive drive" \keyword "Fail drive" \keyword "Manual Recovery options"

\topic "How To Use Manual Recovery >> LUNs" \p\1
How To Use Manual Recovery >> LUNs \label "manluntop" 
\p\p
Fast Find -- \{\5\goto "formatlun" Format\} | \{\5\goto "revivelun" Revive\} | \{\5\goto "manlunrt" Related Topics\} \p\p\4
CAUTION \0\p
Always select Recovery Guru/Health Check to ensure the problem is correctly diagnosed BEFORE attempting any manual recovery procedure. Incorrectly performing a procedure or performing the wrong procedure could cause equipment damage or data loss. Recovery Guru provides step-by-step procedures to make sure that you are correcting the right problem and directs you when to use the manual recovery options. \p\p\1
Procedure For Formatting A LUN \label "formatlun"\0\p\p
1. Select Recovery Application >> RAID Module. \p\p
2. From the top menu, select Options >> Manual Recovery >> Logical Units. \p\p
The Manual Recovery option is grayed out if you select All RAID Modules. \p\p
3. Highlight the LUN/drive group you want to format. You see all the \{\2\bring_popup "Logical Unit" LUNs\} for a single \{\2\bring_popup "Configured Drive Group" drive group\} with \{\2\bring_popup "Dead Mode" Dead\} statuses on one line. This procedure affects all LUNs in that drive group. \p\p\4
CAUTION \0\p
Selecting the Format option destroys all data on every LUN in the drive group. Therefore, you lose all data in the drive group and must use a backup copy to restore data after the format is completed. \p\p
4. Select Format >> OK. \p\p
You return to the LUNs list which shows updated LUN status information. The LUNs have a status of Formatting, then \{\2\bring_popup "Optimal Mode" Optimal\}. You can now use the LUN. Note that the LUN may continue to be formatted in \{\2\bring_popup "Background Formatting" background\}. \p\p
5. Restore your data from backup. \p\p\1
Procedure For Reviving A LUN \label "revivelun"\0\p\p
1. Select Recovery Application >> RAID Module. \p\p
2. From the top menu, select Options >> Manual Recovery >> Logical Units. \p\p
The Manual Recovery option is grayed out if you select All RAID Modules. \p\p
3. Highlight the LUN/drive group you want to revive. You see all the \{\2\bring_popup "Logical Unit" LUNs\} for a single \{\2\bring_popup "Configured Drive Group" drive group\} with \{\2\bring_popup "Dead Mode" Dead\} statuses on one line. This procedure affects all LUNs in that drive group. \p\p\4
CAUTION \0\p
Selecting the Revive option may corrupt data on every LUN in the drive group. Therefore, you could lose all data in the drive group and may have to use a backup copy to restore data after the revive is completed. \p\p
4. Select Revive >> OK. One of two information boxes appear: \p\p
-- Reviving the LUN was successful. Select OK. The LUN shows updated status information. \p\p
-- Notification that an error occurred while attempting to perform this procedure. Try the procedure again. If the error persists, run Recovery Guru for the selected RAID Module to diagnose the problem. \p\p
5. Select Manual Parity Check/Repair to check \{\2\bring_popup "Parity" parity\} on the revived LUNs in the drive group. \p\p\1
Related Topics \label "manlunrt"\0\p
\{\3\goto "Manual Recovery Questions" Common Questions\} \p
\{\3\goto "How To Use Manual Parity Check/Repair" How To Use Manual Parity Check/Repair\} \p
\{\3\goto "How To Use Options >> Manual Recovery" How To Use Options >> Manual Recovery\} \p
\{\3\goto "How To Use Recovery Guru" How To Use Recovery Guru/Health Check\} \p
\{\3\goto "How To View Reconstruction Progress" How To View Reconstruction Progress\} \p
\{\3\goto "Possible LUN Statuses" Possible Logical Unit Statuses\} \p
\{\3\goto "Manual Recovery Restrictions" Restrictions/Cautions\}
\p\p
\{\7\goto "manluntop" Top Of Page\}\p
\keyword "Options menu" \keyword "LUN recovery" \keyword "data recovery" \keyword "Format LUN" \keyword "Revive LUN" \keyword "Manual Recovery options" \keyword "exclusive access operations" \keyword "access, exclusive required"

\topic "Information In Options >> Manual Recovery" \p\1
What Information Appears In Options >> Manual Recovery? \label "infomanrecvtop" 
\p\p
Fast Find -- \{\5\goto "ctrlmaninfo" Controllers\} | \{\5\goto "drvmaninfo" Drives\} | \{\5\goto "lunmaninfo" LUNs\} | \{\5\goto "infomanrt" Related Topics\}
\p\p\4
CAUTION \0\p
Always select Recovery Guru/Health Check to ensure the problem is correctly diagnosed BEFORE attempting any manual recovery procedure. Incorrectly performing a procedure or performing the wrong procedure could cause equipment damage or data loss. Recovery Guru provides step-by-step procedures to make sure that you are correcting the right problem and directs you when to use the manual recovery options. \p\p\1
CONTROLLER PAIRS \label "ctrlmaninfo"\0\p\p
Status information is displayed for the \{\2\bring_popup "Controller" controllers\} in the selected \{\2\bring_popup "RAID Module" RAID Module\}. \p\p\1
Controller\0: Identifies one controller per line for the selected RAID Module as A or B and, where applicable, includes a system \{\2\bring_popup "Controller Name/ID" name/ID \}. The A and B correspond to the hardware controller IDs. \p\p\1
Status\0: Operating condition of the controller. For an explanation of possible statuses, select the Possible Controller Statuses topic in the \{\5\goto "infomanrt" Related Topics\} list below. \p\p
For offline or failed controllers, you should select Recovery Guru/Health Check >> Show Procedure and follow the step-by-step instructions provided. \p\p\1
Options\0: Highlight one controller with a status other than \{\2\bring_popup "Optimal Mode" Optimal\} and select the recovery operation you wish to perform: \p\p
\{\1 o \0\} Place a controller \{\2\bring_popup "Offline Controller Mode" Offline\} to stop a selected controller from accepting I/O requests. \p\p
\{\1 o \0\} Place a controller Online to return it to ready-for-operating condition (Optimal status). \p\p\1
DRIVES \label "drvmaninfo"\0\p\p
Status information is displayed for all the drives in the selected \{\2\bring_popup "RAID Module" RAID Module\}. \p\p\1
Location\0: Indicates the location of the drive in the selected RAID Module. \p\p
For example, this identifier includes the \{\2\bring_popup "SCSI Channel" SCSI Channel\} number and \{\2\bring_popup "SCSI ID" SCSI ID\} unique to the drive; for example, [2,1] indicates the drive is on channel 2 and has a SCSI ID of 1. \p\p\1
Drive Status\0: Operating condition of the drive. For an explanation of the possible statuses, select the Possible Drive Statuses topic in the \{\5\goto "infomanrt" Related Topics\} list below. \p\p
For Failed or Offline drives, you should select Recovery Guru/Health Check >> Show Procedure and follow the step-by-step instructions provided. \p\p\1
Logical Units\0: Number that identifies the \{\2\bring_popup "Logical Unit" LUNs\} contained on the drive. The number is repeated for each drive in the \{\2\bring_popup "Configured Drive Group" drive group\}. Therefore, if two different drives show LUN 0, then those two drives contain that LUN/drive group. \p\p\1
RAID Level\0: Indicates the \{\2\bring_popup "RAID Level" RAID Level\} of the LUN on the drive. \p\p\1
Logical Unit Status\0: Operating condition of the affected LUN. For an explanation of the possible statuses, select the Possible Logical Unit Statuses topic in the \{\5\goto "infomanrt" Related Topics\} list below. \p\p
For \{\2\bring_popup "Dead Mode" Dead\} or \{\2\bring_popup "Degraded Mode" Degraded\} LUNs, you should select Recovery Guru/Health Check >> Show Procedure and follow the step-by-step instructions provided. \p\p\1
NOTE\0: When a drive is \{\2\bring_popup "Unassigned Drive Group" unassigned\} (that is, not configured as part of a LUN), you see dashes in every column except location. There is no status, LUN, RAID Level, or LUN status to report. \p\p\1
Options \0: Highlight one or more drives with non-Optimal statuses and select the recovery operation you wish to perform: \p\p
\{\1 o \0\} Fail a drive if you want to replace it before the controller has marked it as failed. \p\p
\{\1 o \0\} Reconstruct a drive if \{\2\bring_popup "Reconstruction" reconstruction\} doesn't start automatically when you replace the drive (normally it does). \p\p
\{\1 o \0\} Revive a drive to recover if you removed the wrong drive, which was \{\2\bring_popup "Optimal Mode" Optimal\} when you removed it. \p\p\1
LOGICAL UNITS \label "lunmaninfo"\0\p\p
Status information is displayed for all the LUNs configured for the \{\2\bring_popup "RAID Module" RAID Module\}. However, if there are no configured LUNs on the module, this screen is blank. \p\p\1
Logical Units\0: Number that identifies the \{\2\bring_popup "Logical Unit" LUNs\} contained on a particular drive group. \p\p\1
Drive Group\0: Number that identifies the \{\2\bring_popup "Configured Drive Group" drive groups\} configured for the selected RAID Module. \p\p\1
RAID Level\0: Indicates the \{\2\bring_popup "RAID Level" RAID Level\} of the LUN. \p\p\1
Logical Unit Status\0: Operating condition of the affected LUNs. For an explanation of the possible statuses, select the Possible Logical Unit Statuses topic in the \{\5\goto "infomanrt" Related Topics\} list below. \p\p 
For \{\2\bring_popup "Dead Mode" Dead\} or \{\2\bring_popup "Degraded Mode" Degraded\} LUNs, you should select Recovery Guru/Health Check >> Show Procedure and follow the step-by-step instructions provided. \p\p\1
Options\0: Highlight one or more logical units with a Dead or Degraded status and select the recovery operation you wish to perform: \p\p
\{\1 o \0\} Format a LUN with a Dead status manually AFTER you have replaced all the failed drives in the drive group. \p\p
\{\1 o \0\} Revive a LUN only when Recovery Guru/Health Check >> Show Procedure instructs you to do so. \p\p\1
Related Topics \0\label "infomanrt"\p
\{\3\goto "Manual Recovery Questions" Common Questions\} \p
\{\3\goto "Component Concept" Components\} \p
\{\3\goto "How To Use Options >> Manual Recovery" How To Use Options >> Manual Recovery\} \p
\{\3\goto "How To Use Recovery Guru" How To Use Recovery Guru/Health Check\} \p
\{\3\goto "Manual Recovery Restrictions" Restrictions/Cautions\} \p
\{\3\goto "Statuses Concept" Statuses\}
\p\p
\{\7\goto "infomanrecvtop" Top Of Page\}\p
\keyword "controller statuses" \keyword "drive statuses" \keyword "LUN statuses" \keyword "Manual Recovery options" \keyword "screen description" \keyword "status reporting"

\topic "Maintenance/Tuning Application" \p\1
Maintenance/Tuning Application \label "mttop"
\p\p
Fast Find -- \{\5\goto "mttaskproc" Procedures\} | \{\5\goto "mttaskrt" Related Topics\}
\p\p\1
Maintenance/Tuning Tasks \0\p\p
The following tasks are available from the tool bar or from the Options menu for the Maintenance/Tuning Application:
\p\p\1
\{\1 o \} LUN Reconstruction Rate \0 -- change the reconstruction rate for LUNs whether undergoing reconstruction or not
\p\p\1
\{\1 o \} LUN Balancing \0 -- balance logical unit/drive group ownership between active/active controller pairs in a module (that is, move LUNs assigned to one controller to its alternate controller in a selected RAID Module)
\p\p\1
\{\1 o \} Controller Mode \0 -- change controller modes for selected RAID Modules; you can change an active/passive controller pair to an active/active mode, or you can swap the active and passive controllers' modes
\p\p\1
\{\1 o \} Caching Parameters \0 -- change caching parameters for the configured LUNs on a selected RAID Module; cache parameters include write caching, write cache mirroring, and cache without batteries. You can use the command line utility, raidutil, to change other advanced caching parameters
\p\p\1
\{\1 o \} Firmware Upgrade \0 -- upgrade controller firmware or an NVSRAM file for one or all RAID Modules
\p\p\1
\{\1 o \} Options >> Auto Parity Settings \0 -- change the automatic parity check/repair settings, including whether it is enabled or not, the start time of day, day of the week, and whether to automatically repair any errors found
\p\p\1
Procedures \0\label "mttaskproc"
\p\p
\{\3\goto "How To Change The Reconstruction Rate" How To Change The Reconstruction Rate\} \p\p
\{\3\subtopic "How To Use LUN Balancing" How To Use LUN Balancing\} \p\p
\{\3\subtopic "How To Use Controller Mode" How To Use Controller Mode\} \p\p
\{\3\subtopic "How To Use Caching Parameters" How To Use Caching Parameters\} \p\p
\{\3\subtopic "How To Use Firmware Upgrade" How To Use Firmware Upgrade\} \p\p
\{\3\subtopic "How To Download A New NVSRAM File" How To Download A New NVSRAM File\} \p\p
\{\3\subtopic "How To Use Options >> Auto Parity Settings" How To Use Options >> Automatic Parity Check/Repair Settings\}
\p\p\1
Related Topics \0\label "mttaskrt"\p
\{\3\goto "Caching Concept" Caching\} \p
\{\3\goto "Common Question Topics" Common Questions\} \p
\{\3\goto "Restriction/Caution Topics" Restrictions/Cautions\} \p
\{\3\goto "Troubleshooting Topics" Troubleshooting\} \p
\{\3\goto "Firmware Concept" Firmware\} \p
\{\3\goto "How To View Reconstruction Progress" How To View Reconstruction Progress\} \p
\{\3\goto "LUN Assignment Concept" LUN Assignment\} \p
\{\3\goto "NVSRAM Concept" NVSRAM\} \p
\{\3\goto "Parity Concept" Parity\} \p
\{\3\goto "Reconstruction Concept" Reconstruction\}
\p\p
\{\7\goto "mttop" Top Of Page\} \p
\keyword "tasks, Maintenance/Tuning Application" \keyword "summary of tasks" \keyword "raidutil utility" \keyword "task summary" \keyword "Maintenance/Tuning Application" \keyword "LUN Balancing" \keyword "Controller Mode" \keyword "LUN Reconstruction Rate" \keyword "Firmware Upgrade" \keyword "Caching Parameters" \keyword "automatic parity"

\topic "How To Use LUN Balancing" \p\1
How To Use LUN Balancing \label "lunbaltop" 
\p\p
Fast Find -- \{\5\goto "lunbalall" On All RAID Modules\} | \{\5\goto "lunbalrt" Related Topics\}
\p\p\1
Procedure For Balancing Logical Units On One RAID Module \label "lunbalone"\0\p\p
1. Select the Maintenance/Tuning Application. \p\p
2. Select a RAID Module >> LUN Balancing. \p\p
Remember, the LUN Balancing option is grayed out if you select a \{\2\bring_popup "RAID Module" RAID Module\} that has only one controller or an \{\2\bring_popup "Active/Passive Controller Pair" active/passive\} controller pair. \p\p
3. Highlight each \{\2\bring_popup "Configured Drive Group" drive group\} you want to assign to the other controller in the pair. \p\p
You can highlight items in both lists. If you want to view the LUN Assignment for the selected RAID Module without making any changes, select Cancel after you are finished viewing. \p\p
4. Select Move (<< / >>). \p\p
The selected drive group/\{\2\bring_popup "Logical Unit" LUNs\} move to the other controller. \p\p
5. Select Save to actually balance the drive group/LUNs (save any new settings). \p\p
An hourglass appears until the save is completed. \p\p\1
Procedure For Balancing Logical Units On All RAID Module \label "lunbalall"\0\p\p
1. Select the Maintenance/Tuning Application. \p\p
2. Select All RAID Modules >> LUN Balancing. \p\p
3. Highlight the modules with \{\2\bring_popup "Active/Active Controller Pair" active/active\} controllers you want to balance. \p\p\1
NOTE\0: You cannot highlight a RAID Module that has an \{\2\bring_popup "Independent Controller Configuration" independent\} controller or single controller configuration. \p\p
4. Select Balance. \p\p
A confirmation box displays a message that the \{\2\bring_popup "Logical Unit" LUNs\} are about to be \{\2\bring_popup "Balanced LUN Distribution" balanced\} for the selected RAID Modules. \p\p
5. Select OK to proceed. \p\p
An hourglass appears until the balancing is completed; then, the list is updated to show the new LUN Assignments for each module you highlighted. \p\p\1
IMPORTANT \0\p
If it appears that no balancing occurred, verify that the LUNs for the selected RAID Modules are NOT all in the same \{\2\bring_popup "Configured Drive Group" drive group\}. For example, assume that a RAID Module has only three LUNs, but they are all in the same drive group. Those LUNs always belong to the same controller because LUNs are balanced on a drive group basis.
\p\p\1
Related Topics \label "lunbalrt"\0\p
\{\3\goto "LUN Assignment Questions" Common Questions\} \p
\{\3\goto "Number And Type Of Controllers In A RAID Module" How Many And What Kind Of Controllers Does A RAID Module Have?\} \p
\{\3\goto "How To Use LUN Balancing" How To Use LUN Balancing\} \p
\{\3\goto "LUN Assignment Concept" LUN Assignment\} \p
\{\3\goto "LUN Assignment Restrictions" Restrictions/Cautions\} \p
\{\3\goto "LUNs Are Marked As Inaccessible" Troubleshooting\} \p
\{\3\subtopic "Information In LUN Balancing" What Information Appears In LUN Balancing?\}
\p\p
\{\7\goto "lunbaltop" Top Of Page\}\p
\keyword "controller, LUNs owned" \keyword "assigning LUNs" \keyword "independent controller configuration" \keyword "LUN Assignment" \keyword "LUN Balancing" \keyword "balancing LUNs" \keyword "exceptions, independent controller configuration" \keyword "changing LUN assignment"

\topic "Information In LUN Balancing" \p\1
What Information Appears In LUN Balancing? \label "infoluntop" 
\p\p
Fast Find -- \{\5\goto "infolunall" All RAID Modules\} | \{\5\goto "infolunrt" Related Topics\}
\p\p\1
IF YOU SELECT ONE RAID MODULE \label "infolunone"\0\p\p
When you select a single \{\2\bring_popup "RAID Module" RAID Module\}, then LUN Balancing, you see two boxes, one for each \{\2\bring_popup "Controller" controller\}. These boxes indicate which \{\2\bring_popup "Configured Drive Group" drive groups\} and \{\2\bring_popup "Logical Unit" LUNs\} are assigned to which controller. \p\p\1
Controller\0: Two boxes each identify one of the controllers for the selected RAID Module as A or B and, where applicable, a system \{\2\bring_popup "Controller Name/ID" name\}. The A and B correspond to the hardware controller IDs. \p\p\1
Drive Group\0: Provides the number of the drive group assigned to that controller. \p\p\1
LUNs\0: Lists all the logical units that belong to the particular drive group. \p\p\1
Group Capacity (MB)\0: Shows the \{\2\bring_popup "Total Capacity" total\} capacity in megabytes (MB) available on the particular drive group. This is NOT the total capacity of the configured LUNs in the drive group unless you configured them to use all of the capacity. \p\p\1
Options \0\p\p
\{\1 o \0\} You can highlight one or more drive groups, select Move (<< / >>) (the LUNs move to the other controller's box), and select Save to actually balance the LUN assignment between controllers. \p\p
\{\1 o \0\} You can view the LUN assignment for the selected RAID Module without making any changes by selecting Cancel. \p\p\1
IF YOU SELECT ALL RAID MODULES \label "infolunall"\0\p\p
When you select All RAID Modules, then LUN Balancing, you see the \{\2\bring_popup "Logical Unit" LUNs\} configured for a particular RAID Module and the \{\2\bring_popup "Controller" controller\} to which they are currently assigned. \p\p\1
RAID Module\0: Provides the number of a particular \{\2\bring_popup "RAID Module" RAID Module\}. \p\p\1
Controller/ Logical Units Owned\0: Lists LUN numbers owned by each controller. You see a number for every LUN configured for a particular RAID Module. \p\p
When no LUNs are assigned to one of the controllers, instead of seeing a LUN, you see a reason why: \p\p
\{\1 o \0\} \{\2\bring_popup "Active Controller Mode" Active\} (No LUNs owned) \p\p
\{\1 o \0\} None (\{\2\bring_popup "Passive Controller Mode"Passive\} Controller) -- only active controllers can have LUNs assigned to them \p\p
\{\1 o \0\} None (\{\2\bring_popup "No Controller Mode"No Controller\}) -- usually means the module has only one controller \p\p
\{\1 o \0\} \{\2\bring_popup "Inaccessible" Inaccessible\} -- indicates the RAID Module has an \{\2\bring_popup "Independent Controller Configuration" independent\} controller configuration \p\p\1
Options \0\p\p
\{\1 o \0\} You can \{\2\bring_popup "Balanced LUN Distribution" balance\} LUNs for All RAID Modules with \{\2\bring_popup "Active/Active Controller Pair" active/active\} controllers by highlighting one or more RAID Modules, then selecting Balance. \p\p
\{\1 o \0\} You can view the \{\2\bring_popup "LUN Assignment" LUN Assignments\} for All RAID Modules without making any changes by selecting Cancel. \p\p\1
Related Topics \label "infolunrt"\0\p
\{\3\goto "LUN Assignment Concept" LUN Assignment\} \p
\{\3\goto "How To Use LUN Balancing" How To Use LUN Balancing\}
\p\p
\{\7\goto "infoluntop" Top Of Page\}\p
\keyword "Inaccessible" \keyword "screen description" \keyword "group capacity" \keyword "capacity" \keyword "drive group, displayed" \keyword "LUNs, displayed" \keyword "controllers, displayed" \keyword "LUN Balancing"

\topic "How To Use Controller Mode" \p\1
How To Use Controller Mode \label "chgswaptop" 
\p\p
Fast Find -- \{\5\goto "chgactive" Change To Active/Active\} | \{\5\goto "swap" Swap Active/Passive\} | \{\5\goto "chgswaprt" Related Topics\}
\p\p\1
IMPORTANT \0\p
If you do not have \{\2\bring_popup "RDAC Driver" RDAC\} protection, you must stop I/O to the \{\2\bring_popup "RAID Module" RAID Module\} before changing a controller's mode. Otherwise, you could hang the system. \p\p\1
Changing To Active/Active Controllers \label "chgactive" \p\p
When To Use\0 -- Use this option to change an \{\2\bring_popup "Active/Passive Controller Pair" active/passive\} controller pair to \{\2\bring_popup "Active/Active Controller Pair" active/active\} to improve I/O performance. \p\p\1
Procedure \p\p\0
1. Select the Maintenance/Tuning Application. \p\p
2. Select RAID Module >> Controller Mode. \p\p
Remember, the Controller Mode option is grayed out if you select a RAID Module that has only one controller, \{\2\bring_popup "Independent Controller Configuration" independent\} controllers, or is already active/active. \p\p
3. Highlight the active/passive controller pair you want to make active/active. \p\p
4. Select Change to Active/Active. \p\p
You see a confirmation box. The option to automatically \{\2\bring_popup "Balanced LUN Distribution" balance\} the LUNs across the newly active/active controllers is selected by default. \p\p
5. Do one of the following: \p\p
-- Leave the automatic LUN Balancing option selected if you want the LUNs for the selected modules to automatically balance. For maximum performance benefits, each controller should own some of the LUNs. \p\p
-- Deselect the automatic LUN Balancing option if you do NOT want the LUN assignment changed. The currently active controller continues to own all the LUNs. \p\p\1
IMPORTANT \0\p
Selecting OK in Step 6 changes the controllers to active/active. This change CANNOT be undone through this interface. You can use the command line \{\2\bring_popup "Command Line Utilities" utility\} rdacutil to return to an active/passive configuration if desired. \p\p
6. Select OK. \p\p
An hourglass appears until the change is completed: \p\p
\{\1 o \0\} If successful, the list is updated to show the new controller \{\2\bring_popup "Controller Mode" mode\} of the selected RAID modules. \p\p
\{\1 o \0\} If a problem occurs, you receive notification. \p\p\1
Swapping Active/Passive Controllers \label "swap"\p\p
When To Use\0 -- Use to switch the controller modes in an active/passive pair (that is, change the active controller to passive and the passive controller to active). You may want to swap an active/passive controller pair: \p\p
\{\1 o \0\} When a Recovery Procedure requires it. \p\p
\{\1 o \0\} If you have multiple RAID Modules, you may want to use this option to swap controller modes so that all your active controllers are not assigned to the same SCSI Bus. \p\p\1
Procedure \0\p\p
1. Select the Maintenance/Tuning Application. \p\p
2. Select RAID Module >> Controller Mode. \p\p
Remember, the Controller Mode option is grayed out if you select a RAID Module that has only one controller, \{\2\bring_popup "Independent Controller Configuration" independent\} controllers, or has an \{\2\bring_popup "Active/Active Controller Pair" active/active\} pair. \p\p
3. Highlight the \{\2\bring_popup "Active/Passive Controller Pair" active/passive\} controller pair you want to swap. \p\p
4. Select Swap Active/Passive. \p\p
The screen displays two possible confirmation boxes: \p\p
\{\1 o \0\} The controller mode is about to change for the selected RAID Module. \p\p
\{\1 o \0\} The selected RAID Module is receiving I/O. You might see this message if you do not have RDAC protection. Select OK. You return to the main Maintenance/Tuning screen. Stop all I/O to this module, then start this procedure again. \p\p
5. Select OK. \p\p
An hourglass appears until the change is completed: \p\p
\{\1 o \0\} If successful, the list is updated to show the new controller \{\2\bring_popup "Controller Mode" mode\} of the selected RAID Modules. \p\p
\{\1 o \0\} If a problem occurs, you receive notification.
\p\p\1
Related Topics\0\label "chgswaprt"\p
\{\3\goto "Controller Mode Restrictions" Restrictions/Cautions\} \p
\{\3\goto "Controller Mode Troubleshooting" Troubleshooting\} \p
\{\3\subtopic "Information In Controller Mode" What Information Appears In Controller Mode?\}
\p\p
\{\7\goto "chgswaptop" Top Of Page\}\p
\keyword "RDAC" \keyword "rdacutil utility" \keyword "Controller Mode" \keyword "changing active/active" \keyword "Swap Active/Passive" \keyword "changing active/passive" \keyword "stop I/Os"

\topic "Information In Controller Mode" \p\1
What Information Appears in Controller Mode? \label "ctrlmodetop" 
\p\p
Fast Find -- \{\5\goto "ctrlmodert" Related Topics\}
\p\p\0
When you select Controller Mode, you see the current \{\2\bring_popup "Controller Mode" modes\} of all controllers in the selected RAID Module. \p\p\1
RAID Module\0: Provides the name of a particular \{\2\bring_popup "RAID Module" RAID Module\}. \p\p\1
Controller A\0: Identifies the mode for one controller of the selected RAID Module. The column heading includes, where applicable, a system \{\2\bring_popup "Controller Name/ID" name/ID\}. The A corresponds to the hardware controller ID. \p\p\1
Controller B\0: Identifies the mode for the second controller of the selected RAID Module. The column heading includes, where applicable, a system name/ID. The B corresponds to the hardware controller ID. \p\p
Possible modes under the two controller columns are \{\2\bring_popup "Active Controller Mode" Active\}, \{\2\bring_popup "Passive Controller Mode" Passive\}, \{\2\bring_popup "Offline Controller Mode" Offline\}, or \{\2\bring_popup "No Controller Mode" No Controller\}. You could also see \{\2\bring_popup "Inaccessible" Inaccessible\} with these statuses if the RAID Module has an \{\2\bring_popup "Independent Controller Configuration" independent\} controller configuration. \p\p\1
Related Topics \label "ctrlmodert"\0\p
\{\3\goto "How To Use Controller Mode" How To Use Controller Mode\}
\p\p
\{\7\goto "ctrlmodetop" Top Of Page\}\p
\keyword "Inaccessible" \keyword "screen description" \keyword "controllers, displayed" \keyword "mode" \keyword "possible controller modes" \keyword "Controller Mode" \keyword "view controller mode"

\topic "How To Use Caching Parameters" \p\1
How To Use Caching Parameters \label "howtocachetop" 
\p\p
Fast Find -- \{\5\goto "enablecache" Enable Parameters\} | \{\5\goto "disablecache" Disable Parameters\} | \{\5\goto "intercache" Interdependencies\} | \{\5\goto "howtocachert" Related Topics\}
\p\p \0
Use this option to set or change caching parameters for LUNs that have already been created. You can set cache parameters when creating LUNs using the Configuration Application (Create LUNs >> Options >> Caching Parameters). Also, you can set other, more advanced, parameters using the command line \{\2\bring_popup "Command Line Utilities" utility\}, raidutil (consult the man page or help text file for more information). \p\p\1
Enabling Cache Parameters \label "enablecache"\0\p\p
1. Select the Maintenance/Tuning Application. \p\p
2. Select a RAID Module >> Caching Parameters. \p\p
Remember, the Caching Parameters option is grayed out if you select All RAID Modules or if both controllers do not have the same or the minimum required \{\2\bring_popup "Cache Memory" cache\} and \{\2\bring_popup "Processor Memory" processor\} size. \p\p
3. Click in the check boxes to enable caching parameters as desired for any or all \{\2\bring_popup "Logical Unit" LUNs\} in the selected RAID Module. \p\p
Any changes you make do NOT take effect until you select Save. Also, if you select a RAID Module with only one controller, \{\2\bring_popup "Write Cache Mirroring" Write Cache Mirroring\} is grayed out. \p\p
Depending on which caching parameter you enable, another caching parameter could also become enabled because of the interdependencies among them. \p\p
4. Select Save. \p\p
An hourglass appears until the settings change. \p\p\1
Disabling Cache Parameters \label "disablecache"\0\p\p
1. Select the Maintenance/Tuning Application. \p\p
2. Select a RAID Module >> Caching Parameters. \p\p
Remember, the Caching Parameters option is grayed out if you select All RAID Modules or if both controllers do not have the same or the minimum required \{\2\bring_popup "Cache Memory" cache\} and \{\2\bring_popup "Processor Memory" processor\} size. \p\p
3. Click in the check boxes to disable caching parameters as desired for any or all \{\2\bring_popup "Logical Unit" LUNs\} on the selected RAID Module. The box is blank when the parameter is off (disabled). \p\p
Any changes you make do NOT take effect until you select Save. \p\p
Depending on which caching parameter you disable, another caching parameter could also become disabled because of the interdependencies among them. \p\p
4. Select Save for the changes you made in Step 3 to take effect. \p\p
An hourglass appears until the settings change. \p\p\1
Interdependencies \label "intercache" \p\p
Enabling: \p\p
Write Caching\0 -- selecting automatically enables write cache mirroring, as long as the module has \{\2\bring_popup "Redundant Controller Pair" redundant\} controllers. You can disable write cache mirroring if you wish without affecting your write caching selection. \p\p\1
Write Cache Mirroring\0 -- selecting automatically enables write caching. Note that if you disable write caching, this caching parameter is also disabled. Also, this option is grayed out if the selected RAID Module does not have redundant controllers. Furthermore, this parameter does not work if a controller fails or if the controllers in the pair do not have the same \{\2\bring_popup "Cache Memory" cache\} size (Use Module Profile >> RAID Module >> Controllers to determine the controllers' cache size). \p\p\1
Cache without Batteries\0 -- selecting automatically enables write caching.
\p\p\4
CAUTION \0\p
Selecting \{\2\bring_popup "Cache Without Batteries" Cache Without Batteries\} allows write caching to continue even without battery backup or if the batteries are completely discharged or not fully charged. Normally, write caching is temporarily turned off if no batteries are detected or until the batteries are charged. However, enabling the Cache Without Batteries parameter overrides the controller's safeguard. Therefore, if you select Cache Without Batteries without an uninterruptible power supply \{\2\bring_popup "UPS (Uninterruptible Power Supply)" (UPS)\} for protection, you could lose data if a power failure occurs. \p\p\1
Disabling: \p\p
Write Caching\0 -- deselecting disables both write cache mirroring and cache without batteries. \p\p\1
Write Cache Mirroring\0 -- deselecting does not affect the other two parameter settings. \p\p\1
Cache Without Batteries\0 -- deselecting does not affect the other two parameter settings. \p\p\1
Related Topics \label "howtocachert"\0\p
\{\3\goto "Caching Concept" Caching\} \p
\{\3\subtopic "How To View/Verify Cache Size" How To View/Verify Cache Memory Size\} \p
\{\3\goto "Caching Restrictions" Restrictions/Cautions\} \p
\{\3\goto "Caching Troubleshooting" Troubleshooting\} \p
\{\3\subtopic "Viewing Caching Parameter Settings" Viewing Caching Parameter Settings\} \p
\{\3\subtopic "Information In Caching Parameters" What Information Appears In Caching Parameters?\}
\p\p
\{\7\goto "howtocachetop" Top Of Page\}\p
\keyword "write caching" \keyword "write cache mirroring" \keyword "cache without batteries" \keyword "Caching Parameters" \keyword "caching" \keyword "parameters, caching" \keyword "raidutil utility" \keyword "interdependencies" \keyword "enable" \keyword "disable" \keyword "changing settings"

\topic "How To View/Verify Cache Size" \p\1
How To View/Verify Cache Memory Size \label "cachesizetop" 
\p\p
Fast Find -- \{\5\goto "cachesizert" Related Topics\}
\p\p\0
If a RAID Module has two \{\2\bring_popup "Active/Active Controller Pair" active/active\} controllers with a minimum of 8 MB of processor and cache memory, you can set three basic caching parameters using the GUI: \{\2\bring_popup "Write Caching" write caching\}, \{\2\bring_popup "Write Cache Mirroring" cache mirroring\}, and \{\2\bring_popup "Cache Without Batteries" cache without batteries \}. \p\p\1
Procedure \0\p\p
1. From any Application, select a RAID Module >> Module Profile. \p\p
2. Select Controllers to obtain more detailed information. \p\p
You see the amount in megabytes (MB) of the total available \{\2\bring_popup "Cache Memory" cache\} and \{\2\bring_popup "Processor Memory" processor\} memories on the controller. \p\p
3. Select OK when you are done reviewing this screen. \p\p
You return to the Module Profile summary information screen. \p\p
4. Select OK to exit Module Profile. \p\p\1
Related Topics \label "cachesizert"\0\p
\{\3\goto "Caching Concept" Caching\} \p
\{\3\goto "Number And Type Of Controllers In A RAID Module" How Many And What Kind Of Controllers Does A RAID Module Have?\} \p
\{\3\goto "How To Use Caching Parameters" How To Use Caching Parameters\}
\p\p
\{\7\goto "cachesizetop" Top Of Page\}\p
\keyword "cache memory" \keyword "processor memory" \keyword "caching" \keyword "size, controller" \keyword "view cache/processor size" \keyword "verify cache/processor size" 

\topic "Viewing Caching Parameter Settings" \p\1
Viewing Caching Parameter Settings \label "viewcachetop" 
\p\p
Fast Find -- \{\5\goto "cachemt" Maintenance/Tuning\} | \{\5\goto "viewcachert" Related Topics\}
\p\p\1
Procedure from Any Application \0\p\p
1. From any Application, select RAID Module >> Module Profile >> LUNs. \p\p
2. Select OK. \p\p\1
NOTE\0: You might see an asterisk next to the caching parameters column. This indicates that the parameter is enabled, but is NOT currently active. The controller has disabled the parameter for some reason (such as low batteries or controller replacement). If you see this condition, use Message Log (Status Application) to determine the correct action to take. \p\p\1
Procedure from Maintenance/Tuning Application \label "cachemt"\0\p\p
1. Select the Maintenance/Tuning Application. \p\p
2. Select a RAID Module >> Caching Parameters. \p\p
This screen displays the settings for the caching parameters on a logical unit basis. For detailed information, select What Information Appears In Caching Parameters? in the \{\5\goto "viewcachert" Related Topics\} list below. \p\p\1
Related Topics \label "viewcachert"\0\p
\{\3\goto "Caching Concept" Caching\} \p
\{\3\goto "How To Use Caching Parameters" How To Use Caching Parameters\} \p
\{\3\goto "Information In Caching Parameters" What Information Appears In Caching Parameters?\}
\p\p
\{\7\goto "viewcachetop" Top Of Page\}\p
\keyword "settings" \keyword "view caching parameters" \keyword "caching" \keyword "parameters, caching" \keyword "cache disabled" \keyword "inactive cache" \keyword "disabled cache"

\topic "Information In Caching Parameters" \p\1
What Information Appears In Caching Parameters? \label "infocachetop" 
\p\p
Fast Find -- \{\5\goto "infocachert" Related Topics\}
\p\p\0
When you select a specific \{\2\bring_popup "RAID Module" RAID Module\}, then Caching Parameters, you see the settings for the caching parameters on a logical-unit basis. \p\p\1
Logical Unit\0: Identifies the number of the \{\2\bring_popup "Logical Unit" logical unit\} (LUN). \p\p\1
Write Caching\0: Check box that allows you to enable/disable the \{\2\bring_popup "Write Caching" write caching\} parameter for a particular LUN. \p\p\1
Write Cache Mirroring\0: Check box that allows you to enable/disable the \{\2\bring_popup "Write Cache Mirroring" write cache mirroring\} parameter for a particular LUN. \p\p\1
IMPORTANT \0\p
Write Cache Mirroring is effective only for modules with \{\2\bring_popup "Redundant Controller Pair" redundant\} controller pairs that have the same size cache. Use Module Profile >> RAID Module >> Controllers to determine if both controllers in the pair have the same size \{\2\bring_popup "Cache Memory" cache\} BEFORE enabling this parameter. \p\p\1
Cache Without Batteries\0: Check box that allows you to enable/disable the \{\2\bring_popup "Cache Without Batteries" cache without batteries\} parameter for a particular LUN. \p\p
Additionally, you see a Caution explaining the considerations for enabling the cache without batteries parameter. \p\p\4
CAUTION \0\p
Selecting Cache Without Batteries allows write caching to continue even without battery backup or if the batteries are completely discharged or not fully charged. Normally, write caching is temporarily turned off if no batteries are detected or until the batteries are charged. However, enabling the Cache Without Batteries parameter overrides the controller's safeguard. Therefore, if you select Cache Without Batteries without an uninterruptible power supply \{\2\bring_popup "UPS (Uninterruptible Power Supply)" (UPS)\} for protection, you could lose data if a power failure occurs. \p\p
You might see an asterisk next to the caching parameters box. This indicates that the parameter is enabled, but is currently NOT active. The controller has disabled the parameter for some reason (such as low batteries or controller replacement). If you see this condition, use Message Log (Status Application) to determine the correct action to take. \p\p\1
Related Topics \label "infocachert"\0\p
\{\3\goto "Caching Concept" Caching\} \p
\{\3\goto "Number And Type Of Controllers In A RAID Module" How Many And What Kind Of Controllers Does A RAID Module Have?\} \p
\{\3\goto "How To Use Caching Parameters" How To Use Caching Parameters\}
\p\p
\{\7\goto "infocachetop" Top Of Page\} \p
\keyword "caching" \keyword "screen description" \keyword "Caching Parameters" \keyword "settings" \keyword "parameters, caching"

\topic "How To Use Firmware Upgrade" \p\1
How To Use Firmware Upgrade \label "upgradefirmtop" 
\p\p
Fast Find -- \{\5\goto "upgradestep" Procedure\} | \{\5\goto "upgradert" Related Topics\}
\p\p\1
Options \0\p\p
You can choose to upgrade controller firmware files on a single \{\2\bring_popup "RAID Module" RAID Module\} or on All RAID Modules at once. \p\p
You can choose to perform the upgrade \{\2\bring_popup "Online Firmware Upgrade" online\} or \{\2\bring_popup "Offline Firmware Upgrade" offline\}. \p\p\1
NOTE:\0 If you also need to upgrade controller NVSRAM, do so before upgrading the controller firmware. \p\p
Procedure \label "upgradestep"\0\p\p
1. Copy the firmware files to the correct \{\2\bring_popup "Subdirectory, Firmware" subdirectory\} in the installation directory. \p\p
2. Select the Maintenance/Tuning Application. \p\p
3. Select RAID Module >> Firmware Upgrade. \p\p
4. Read the Important Notes, and select OK. \p\p
5. Select either: \p\p
-- Online to upgrade firmware while the selected RAID Module receives I/O. \p\p
-- Offline to upgrade firmware when the selected RAID Module is NOT receiving I/O. \p\p
The screen displays "Verifying the controller state" while the software checks the selected RAID Modules for restrictions based on the type of firmware upgrade you selected. If there are no restrictions, you see the \{\2\bring_popup "Compatible Files/Versions Screen" Compatible Files/Versions\} screen. \p\p\1
NOTE\0: If the list in the Compatible Files/Versions area is blank, then the appropriate subdirectory does not contain all of the necessary firmware files. Remember, the initial search is made in a default subdirectory where you installed the storage management software. Select Cancel and repeat Step 1. You may want to review the Restrictions/Cautions topic in the \{\5\goto "upgradert" Related Topics\} list below. \p\p
6. Select the controllers you want to upgrade. \p\p
This is NOT an option if you select ALL RAID Modules, a RAID Module that has only one controller, or the Online method. In these cases, all controllers for the selected RAID Modules will be upgraded. It is strongly recommended that you select both controllers to ensure that they have compatible versions of firmware. \p\p
7. Highlight the firmware version level you want to download. \p\p
The path box is updated to show the filenames associated with the version you \{\2\bring_popup "Selecting Compatible Firmware Files" selected\}. \p\p\1
NOTE\0: It is recommended that the version line you select has both \{\2\bring_popup "Firmware Level" Firmware Level\} and \{\2\bring_popup "Boot Level" Boot Level\} versions specified. You may also see \{\2\bring_popup "Fibre Channel Level" Fibre Channel Level\} (FC). When you highlight a line with FC code, it is downloaded with the appware and bootware files. However, the fibre channel code is ignored unless the module's controllers are fibre channel ready. \p\p\1
NOTE:\0 For firmware levels 3.0 and higher, the fibre channel firmware is contained in the appware file; there is no separate fibre channel firmware file. \p\p
8. Select OK if the correct version level is highlighted. \p\p
You either receive notification that a problem occurred, or you have a final confirmation that the upgrade process is about to begin. \p\p\1
IMPORTANT \0\p
Once you select OK at the "Firmware is about to start" prompt in Step 9, do NOT select any other options or exit the Maintenance/Tuning Application until the upgrade process is complete. You can, however, monitor the upgrade progress. \p\p
9. Select OK and follow the upgrade \{\2\bring_popup "Firmware Upgrade Progress" progress\}. \p\p
When the firmware upgrade is finished, you see a Summary Report indicating whether the upgrade is Successful or Failed. \p\p\1
NOTE\0: If you select All RAID Modules, it is possible that the upgrade was successful for some modules, but not for others. The final confirmation box should indicate which modules were not successful and give an appropriate cause. For more information, select the Possible Download Statuses topic in the \{\5\goto "upgradert" Related Topics\} list below. \p\p
10. Select OK. \p\p
You return to the Maintenance/Tuning main screen. If you have successfully upgraded controller firmware, you are finished with this procedure. 
\p\p\1
Related Topics\0\label "upgradert"\p
\{\3\goto "Firmware/NVSRAM Questions" Common Questions\} \p
\{\3\goto "Fibre Channel Concept" Fibre Channel\} \p
\{\3\goto "Firmware Concept" Firmware\} \p
\{\3\subtopic "Firmware Upgrade Results" Firmware Upgrade Results\} \p
\{\3\goto "How To Download A New NVSRAM File" How To Download A New NVSRAM File\} \p
\{\3\goto "NVSRAM Concept" NVSRAM\} \p
\{\3\goto "Firmware/NVSRAM Restrictions" Restrictions/Cautions\} \p
\{\3\subtopic "Selecting Files In Firmware Upgrade" Selecting Files In Firmware Upgrade\} \p
\{\3\goto "Firmware/NVSRAM Troubleshooting" Troubleshooting\} \p
\{\3\subtopic "Viewing Firmware Upgrade Progress" Viewing A Firmware Upgrade's Progress\}
\p\p
\{\7\goto "upgradefirmtop" Top Of Page\}\p
\keyword "controller firmware" \keyword "firmware" \keyword "upgrading firmware" \keyword "downloading firmware" \keyword "fibre channel" \keyword "offline firmware upgrade" \keyword "online firmware upgrade" \keyword "version, controller firmware" \keyword "Firmware Upgrade"

\topic "Firmware Upgrade Results" \p\1
Firmware Upgrade Results \label "firmresulttop" 
\p\p
Fast Find -- \{\5\goto "firmresultrt" Related Topics\}
\p\p\0
When the \{\2\bring_popup "Firmware" firmware\} upgrade or \{\2\bring_popup "NVSRAM File" NVSRAM\} download is finished, a Summary Report indicates whether or not the upgrade was successful. If you select All RAID Modules, it is possible that the upgrade was successful for some modules, but not for others. If the upgrade was unsuccessful for any modules, the Download Status column in the Summary Report shows "Failed," followed by the probable cause of the failure. \p\p\1
Download Statuses \p\p
Successful\0: Indicates that the firmware upgrade was completed for the RAID Modules and files specified. \p\p\1
Successful: However, all the LUNs are assigned to only one controller\0: Use Controller Mode to determine if the controller pair is \{\2\bring_popup "Active/Active Controller Pair" active/active\} or is \{\2\bring_popup "Active/Passive Controller Pair" active/passive\}. If active/active, use LUN Balancing to assign some of the LUNs to each active controller. If active/passive, use Controller Mode to change to active/active if you want. \p\p\1
Failed\0: Indicates the firmware upgrade was NOT completed for the RAID Modules and files specified. Failed is followed by a reason for the unsuccessful upgrade: \p\p
\{\1 o \0\} The selected module had I/O activity occurring. Stop I/O to that module and try to upgrade the firmware again. \p\p
\{\1 o \0\} At least one of the selected firmware files had bad file contents. Recopy the firmware files to the correct \{\2\bring_popup "Subdirectory, Firmware" subdirectory\} in the installation \{\2\bring_popup "Installation Directory" directory\} (see the "Installation and Support Guide" specific to your operating system for installation directory information). If you see this message a second time, one or more of your files are most likely corrupt. Obtain a new copy of the firmware upgrade files. \p\p
\{\1 o \0\} The Write Buffer Command failed. Try to perform the upgrade again for this module. If it fails a second time, call your Customer Services Representative. \p\p
\{\1 o \0\} The software was unable to reset the controller. Try to upgrade the firmware again. \p\p
\{\1 o \0\} One or more LUNs for the selected module were not Optimal. Use the Recovery Application >> Recovery Guru/Health Check to restore the LUNs to an Optimal status, then try to upgrade the firmware again. \p\p
\{\1 o \0\} Upgrading to the selected firmware version requires that you use the \{\2\bring_popup "Offline Firmware Upgrade" Offline\} method. Try to upgrade the firmware again and this time be sure to select Offline. \p\p
\{\1 o \0\} The current firmware version is unable to upgrade to the files you selected. Most likely, you need to upgrade to an intermediate version of firmware. Try to upgrade to a version earlier than the one you selected. If that upgrade is successful, perform a second upgrade for this latest firmware version. \p\p
\{\1 o \0\} The files you selected are not compatible with the current firmware versions on the selected module's controllers. Most likely, the current directory does not contain ALL the necessary firmware files. Copy the firmware files and the \{\2\bring_popup "fwcompat.def File" fwcompat.def\} file to the correct \{\2\bring_popup "Subdirectory, Firmware" subdirectory\} and try again (see the "Installation and Support Guide" specific to your operating system for installation directory information). Be sure the version you select has both a \{\2\bring_popup "apd File Extension" Firmware\} Level and \{\2\bring_popup "bwd File Extension" Boot\} Level version specified. If the upgrade fails a second time, obtain a new copy of the firmware upgrade files. \p\p
\{\1 o \0\} The software was unable to access the controllers during the upgrade process. Use the Recovery Application >> Recovery Guru/Health Check to determine if the module has a failure. If a failure is indicated, fix it and try to upgrade the firmware again. If Recovery Guru does not indicate a failure, try to upgrade the firmware again. \p\p
\{\1 o \0\} The firmware version selected for upgrading was a pre-2.03 firmware version, which is not supported by the storage management software or the \{\2\bring_popup "Redundant Controller Pair" redundant\} controller configuration. Do NOT try to load this firmware again. \p\p
\{\1 o \0\} The \{\2\bring_popup "Online Firmware Upgrade" online\} upgrade cannot be performed because either the selected module has only one controller or one of the controllers in the pair is not accessible. Use Module Profile >> RAID Module >> Controllers to determine how many controllers the module has. If there is only one controller, try to upgrade the firmware again and be sure to select \{\2\bring_popup "Offline Firmware Upgrade" Offline\}. If you have two controllers, use the Recovery Application >> Recovery Guru/Health Check and follow the recommended Show Procedure to fix the controller problem BEFORE attempting to upgrade the firmware again. \p\p
\{\1 o \0\} The software was unable to bring a controller back to \{\2\bring_popup "Active Controller Mode" active\} mode; furthermore, the firmware upgrade was successful to one of the controllers, so now the controllers do NOT have the same firmware version. Try the procedure again, or try using the \{\2\bring_popup "Offline Firmware Upgrade" Offline\} procedure. Be sure to load the same firmware version on both controllers in the pair. Use Module Profile >> RAID Module >> Controllers to verify what firmware versions are loaded on each controller. \p\p
\{\1 o \0\} An Unknown Failure occurred, probably as a result of some internal software function failure. Use the Status Application >> Message Log for event details. \p\p
Related Topics \label "firmresultrt"\0\p
\{\3\goto "How To Download A New NVSRAM File" How To Download A New NVSRAM File\} \p
\{\3\goto "How To Use Firmware Upgrade" How To Use Firmware Upgrade\}
\p\p
\{\7\goto "firmresulttop" Top Of Page\}\p
\keyword "results" \keyword "NVSRAM" \keyword "firmware" \keyword "upgrade statuses" \keyword "download status" \keyword "failures"

\topic "Selecting Files In Firmware Upgrade" \p\1
Selecting Files In Firmware Upgrade \label "firmselecttop" 
\p\p
Fast Find -- \{\5\goto "firmcompat" Compatible Files\} | \{\5\goto "firmselectrt" Related Topics\}
\p\p\0
When you select a RAID Module, then Firmware Upgrade, and either \{\2\bring_popup "Online Firmware Upgrade" Online\} or \{\2\bring_popup "Offline Firmware Upgrade" Offline\}, the software checks for restrictions based on the type of firmware upgrade you select. If no restrictions are found, a display shows you the current firmware version for the selected RAID Module and a list of version levels that are compatible. \p\p\1
Current Firmware Versions \p\p
RAID Module\0: Provides the identifier for a particular \{\2\bring_popup "RAID Module" RAID Module\}. \p\p\1
Controller\0: Identifies the controllers in the selected RAID Module as A or B and, where applicable, includes a system \{\2\bring_popup "Controller Name/ID" name/ID\}. The A and B correspond to the hardware controller IDs. \p\p\1
Firmware Level\0: Number indicating the release of controller \{\2\bring_popup "Firmware Level" Firmware Level\} firmware. \p\p\1
Boot Level\0: Number indicating the controller type and release version of controller \{\2\bring_popup "Boot Level" Boot Level\}. \p\p\1
Fibre Channel Level\0: Number indicating the controller type and release version of driver for \{\2\bring_popup "Fibre Channel Level" Fibre Channel Level\} firmware. For firmware levels 3.0 and higher, the fibre channel firmware is contained in the appware file; there is no separate fibre channel firmware file. \p\p\1
Compatible Files/Versions \label "firmcompat"\0\p\p
The software displays compatible firmware versions by using the \{\2\bring_popup "fwcompat.def File" fwcompat.def\} file to check the firmware files in the selected directory. Each line shows compatible version level numbers for Firmware Level, Boot Level, and Fibre Channel Level as applicable. When you highlight any line, the Path line is updated to list the filenames for the version you select. \p\p\1
Path\0: The default is the \{\2\bring_popup "Subdirectory, Firmware" subdirectory\} in the installation directory where the fwcompat.def file was copied (see the "Installation and Support Guide" specific to your operating system for installation directory information). \p\p\1
IMPORTANT \0\p
If you copied the firmware files, including the fwcompat.def, to some directory other than the default directory, enter the correct directory on the Path line. \p\p\1
Related Topics \label "firmselectrt"\0\p
\{\3\goto "Fibre Channel Concept" Fibre Channel\} \p
\{\3\goto "How To Use Firmware Upgrade" How To Use Firmware Upgrade\} \p
\{\3\goto "Can't De-Select The Fibre Channel File" Can't De-Select The Fibre Channel Level File\}
\p\p
\{\7\goto "firmselecttop" Top Of Page\}\p
\keyword "firmware" \keyword "controller firmware" \keyword "fibre channel" \keyword "selecting files" \keyword "file selection" \keyword "files, controller firmware" \keyword "fwcompat.def file" \keyword "bootware level" \keyword "appware level" \keyword "fibre channel firmware level"

\topic "Viewing Firmware Upgrade Progress" \p\1
Viewing A Firmware Upgrade's Progress \label "viewfirmtop" 
\p\p
Fast Find -- \{\5\goto "viewfirmrt" Related Topics\}
\p\p\0
Once you select OK at the "Firmware upgrade is about to start" prompt, you can follow the upgrade progress for downloading \{\2\bring_popup "Firmware" firmware\} or \{\2\bring_popup "NVSRAM File" NVSRAM\} files. Remember that you cannot exit the Maintenance/Tuning Application until the operation is completed. \p\p
Watch the histogram for the selected \{\2\bring_popup "RAID Module" RAID Module\}. It indicates the progress (as a percentage) of the download for each file and starts over at 0% for each new file if you have more than one. \p\p
If you have two controllers in a module, the progress bar reaches 50% after the file is downloaded to the first controller. You may notice the bar pauses at 50% before it reaches 100% while the file is downloaded to the second controller. \p\p
If you select All RAID Modules, the module name is updated as each module begins its upgrade process. \p\p\1
Related Topics \label"viewfirmrt"\0\p
\{\3\goto "How To Download A New NVSRAM File" How To Download A New NVSRAM File\} \p
\{\3\goto "How To Use Firmware Upgrade" How To Use Firmware Upgrade\}
\p\p
\{\7\goto "viewfirmtop" Top Of Page\}\p
\keyword "progress" \keyword "view progress" \keyword "firmware" \keyword "NVSRAM" \keyword "controller firmware"

\topic "How To Download A New NVSRAM File" \p\1
How To Download A New NVSRAM File \label "nvsram2top" 
\p\p
Fast Find -- \{\5\goto "nvsram2step" Procedure\} | \{\5\goto "nvsram2rt" Related Topics\}
\p\p\1
Options \0\p\p
You can choose to download a new \{\2\bring_popup "NVSRAM File" NVSRAM\} file on a single \{\2\bring_popup "RAID Module" RAID Module\} or on All RAID Modules at once. \p\p\1
Procedure \0\label "nvsram2step"\p\p\1
IMPORTANT \0\p
This procedure requires that you turn the RAID Module off and then back on. Therefore, you should stop all I/O to the affected module and use the \{\2\bring_popup "Offline Firmware Upgrade" offline\} method to download the NVSRAM file. \p\p
1. Stop all I/O to the affected RAID Module. \p\p
2. Copy the NVSRAM file to the correct \{\2\bring_popup "Subdirectory, Firmware" subdirectory\} in the installation directory.\p\p
3. Select the Maintenance/Tuning Application. \p\p
4. Select RAID Module >> Firmware Upgrade. \p\p
5. Read the Important Notes, and select OK. \p\p
6. Select Offline to download while the selected RAID Module is NOT receiving I/O. \p\p
The screen displays "Verifying the controller state" while the software checks the selected RAID Modules for restrictions based on the type of firmware upgrade you selected. If there are no restrictions, you see the \{\2\bring_popup "Compatible Files/Versions Screen" Compatible Files/Versions\} screen. \p\p
This screen lists the controllers and their current firmware version level for the selected RAID Modules at the top of the screen. \p\p
7. Select the controllers you want to upgrade. \p\p
This is NOT an option if you select ALL RAID Modules, a RAID Module that has only one controller, or the Online method. In these cases, all controllers for the selected RAID Modules will be upgraded. It is strongly recommended that you  select both controllers to ensure that they have compatible NVSRAM versions. \p\p
8. In the Path line, type the complete path name for the NVSRAM file and select OK. \p\p
An Upgrade Restriction screen is displayed, indicating that the software does not recognize the file as a firmware file. \p\p
9. Verify that the NVSRAM file name is correct and select OK. \p\p
After you select OK, you either receive notification that a problem occurred, or you have a final confirmation that the upgrade process is about to begin. \p\p\1
IMPORTANT \0\p
Once you select OK at the "Firmware is about to start" prompt in Step 10, do NOT select any other options or exit the Maintenance/Tuning Application until the upgrade process is complete. You can, however, monitor the upgrade progress. \p\p
10. Select OK and follow the upgrade \{\2\bring_popup "Firmware Upgrade Progress" progress\}. \p\p
When the NVSRAM upgrade is finished, you see a Summary Report indicating whether the upgrade is Successful or Failed. \p\p\1
NOTE\0: If you selected All RAID Modules, it is possible that the upgrade was successful for some modules, but not for others. The Summary Report should indicate which modules were not successful and give an appropriate cause. For more information, select the Firmware Upgrade Statuses topic in the Related Topics list below. \p\p
11. Select OK. \p\p
You return to the main Maintenance/Tuning screen. \p\p
12. If you have successfully downloaded NVSRAM files, at the command line, type: \p\p
nvutil -vf \p\p
This utility checks and corrects any settings on all controllers in your RAID Modules to ensure that certain settings in the NVSRAM are set up correctly for the storage management software. Consult the man pages (UNIX systems) or help.txt files (Windows NT systems) for a description of the nvutil utility. \p\p
13. Turn the RAID Module off and then on again. \p\p\1
Related Topics \label "nvsram2rt"\0\p
\{\3\goto "Firmware/NVSRAM Questions" Common Questions\} \p
\{\3\goto "Firmware Concept" Firmware\} \p
\{\3\goto "Firmware Upgrade Results" Firmware Upgrade Results\} \p
\{\3\goto "How To Use Firmware Upgrade" How To Use Firmware Upgrade\} \p
\{\3\goto "NVSRAM Concept" NVSRAM\} \p
\{\3\goto "Firmware/NVSRAM Restrictions" Restrictions/Cautions\} \p
\{\3\goto "Firmware/NVSRAM Troubleshooting" Troubleshooting\} \p
\{\3\goto "Viewing Firmware Upgrade Progress" Viewing A Firmware Upgrade's Progress\}
\p\p
\{\7\goto "nvsram2top" Top Of Page\}\p
\keyword "NVSRAM" \keyword "nvutil utility" \keyword "upgrading NVSRAM files" \keyword "files, NVSRAM" \keyword "downloading NVSRAM files" \keyword "Firmware Upgrade" \keyword "offline firmware upgrade" \keyword "stop I/Os" \keyword "exclusive access operations" \keyword "access, exclusive required"

\topic "How To Use Options >> Auto Parity Settings" \p\1
How To Use Options >> Auto Parity Settings \label "autoparitytop" 
\p\p
Fast Find -- \{\5\goto "autoparityrt" Related Topics\}
\p\p\0
Use this option to automatically \{\2\bring_popup "Parity Check/Repair" check\} parity at a daily or weekly interval. You can also specify whether you want to automatically repair any errors found. \p\p\1
Procedure \0\p\p
1. Select the Maintenance/Tuning Application. \p\p
2. From the top menu, select Options >> Auto Parity Settings. \p\p
Remember that changing any of these settings affects ALL your RAID Modules. \p\p
3. Do either of the following: \p\p
-- Select the Enable Automatic Parity Check/Repair box if you want parity check/repair to run automatically at the specified start time. \p\p
-- Deselect the Enable Automatic Parity Check/Repair box if you do NOT want this operation to run automatically. \p\p
4. Type in or use the spinner buttons to enter the start time you want automatic parity to begin. \p\p
The time must be in a 24-hour format; therefore, the time you can set ranges from 00 00 (midnight) to 23 59 (11:59 PM). For example, the default setting, two o'clock in the morning is set as 02 00. If you want the check/repair to run at three o'clock in the afternoon, set the boxes to read 15 00. \p\p\1
NOTE\0: For best results, select a time of slow system use for the automatic operation to run so that system performance is not adversely affected while parity is checked and repaired. \p\p
5. Type in or use the spinner buttons to select how often you want automatic parity to run: \p\p
-- To run this check every day at the specified time, select the Daily option. \p\p
-- To run this check once a week, select a specific day, such as Sunday. \p\p
6. Select either the With Repair button (if you want to automatically fix any parity errors found) or the Without Repair button (if you do not want to fix any errors found). \p\p
If you choose not to repair any errors found, the errors will still be logged. You can then use the error information to locate the affected file and attempt to repair it. To fix the parity error, you will have to run parity check again. \p\p
7. Select Save. \p\p\1
NOTE\0: Automatic parity check will not be performed twice in the same day. If it has already run today, and you specify a later time for it to run, it will not run until that time the next day. This does not affect your ability to perform a manual parity check.
\p\p\1
Related Topics \label "autoparityrt"\0\p
\{\3\goto "Parity Questions" Common Questions\} \p
\{\3\goto "How To Use Manual Parity Check/Repair" How To Use Manual Parity Check/Repair\} \p
\{\3\goto "Parity Concept" Parity\} \p
\{\3\goto "Parity Restrictions" Restrictions/Cautions\} \p
\{\3\goto "Parity Troubleshooting" Troubleshooting\} \p
\{\3\subtopic "Viewing Parity Messages" Viewing Parity Messages\}
\p\p
\{\7\goto "autoparitytop" Top Of Page\}\p
\keyword "parity" \keyword "automatic parity" \keyword "check parity" \keyword "repair parity" \keyword "checking interval" \keyword "interval" \keyword "enable" \keyword "disable" \keyword "settings" \keyword "Options menu" \keyword "Options >> Auto Parity Settings, see parity or automatic parity items" \keyword "Auto Parity Settings, see parity or automatic parity items" \keyword "daily parity check" \keyword "weekly parity check" \keyword "changing settings"

\topic "Viewing Parity Messages" \p\1
Viewing Parity Messages \label "viewparitytop" 
\p\p
Fast Find -- \{\5\goto "viewparityopt" Options\} | \{\5\goto "viewparityrt" Related Topics\}
\p\p\1
Procedure \0\p\p
1. Select the Status Application. \p\p
When you first start the Status Application, Message Log is displayed for All RAID Modules on most platforms. In some cases, the Select Module screen may be displayed first. \p\p
2. From the Message Log screen, select List Type. \p\p
A screen is displayed showing the different message types you can view: \{\2\bring_popup "Parity Message Type" parity\}, \{\2\bring_popup "General Message Type" general\}, and \{\2\bring_popup "Hardware Message Type" hardware\}. \p\p
3. Click on the Parity box to view only the parity messages. \p\p
4. Select OK. \p\p
The summary information screen displays only the parity message types for the selected RAID Module. \p\p\1
Options \label "viewparityopt"\0\p\p
\{\1 o \0\} To view more detailed information, highlight one or more messages and select Show Details. \p\p
\{\1 o \0\} To copy detailed message information, from the top menu select Edit >> Copy To Clipboard. This automatically highlights the message's text and copies it to the clipboard. Before copying additional messages or exiting this program, use an appropriate application to save the clipboard contents into an editor or desired file. \p\p\1
Related Topics \label "viewparityrt"\0\p
\{\3\goto "Copy To Clipboard" Copy To Clipboard \} \p
\{\3\goto "How To Use Options >> Auto Parity Settings" How To Use Options >> Auto Parity Settings\} \p
\{\3\goto "Parity Concept" Parity\} \p
\{\3\goto "Parity Message Details" Parity Message Details\} \p
\{\3\goto "Selecting Messages" Selecting Messages\}
\p\p
\{\7\goto "viewparitytop" Top Of Page\}\p
\keyword "parity" \keyword "messages, parity" \keyword "events, parity" \keyword "Message Log"

\topic "Procedure Topics" \p\1
Procedures \label "proceduretop"
\p\p
Fast Find -- \{\5\goto "procctrl" Controller Mode\} | \{\5\goto "procfirm" Firmware/NVSRAM\} | \{\5\goto "prochelp" Help\} | \{\5\goto "proclocate" Locating\} | \{\5\goto "proclun" LUN Assignment\} | \{\5\goto "procmon" Monitoring\} | \{\5\goto "procpar" Parity\} | \{\5\goto "procrm" RAID Modules\} | \{\5\goto "procrecon" Reconstruction\} | \{\5\goto "procrecv" Recovery\} | \{\5\goto "procsave" Saving\} | \{\5\goto "procview" Viewing\} | \{\5\goto "procup" Updating\} | \{\5\goto "procrt" Related Topics\}
\p\p\1
Caching \0\p\p
\{\3\goto "How To Use Caching Parameters" Setting Caching Parameters\} \p
\{\3\goto "Viewing Caching Parameter Settings" Viewing Caching Settings\} \p
\{\3\goto "How To View/Verify Cache Size" Viewing/Verifying Cache Memory Size\}
\p\p\1
Configuration \0\p\p
\{\3\goto "Expand Capacity For A Drive Group" Adding Capacity To A Drive Group\} \p
\{\3\goto "Modify RAID Level For A Drive Group" Changing RAID Level For A Drive Group\} \p
\{\3\goto "Change Segment Size For LUNs" Changing Segment Size For Logical Units\} \p
\{\3\goto "How To Use Create Hot Spare" Creating Hot Spare Drives\} \p
\{\3\goto "How To Use Create LUN" Creating Logical Units\} \p
\{\3\goto "How To Use Delete" Deleting Logical Units Or Hot Spare Drives\} \p
\{\3\goto "How To Use File >> Reset Configuration" Resetting A RAID Module's Configuration\} \p
\{\3\goto "Defragment A Drive Group" Restoring Space On A Drive Group (Defragment)\} \p
\{\3\goto "Using Create LUN >> Options" Setting Options When Creating Logical Units\}
\p\p\1
Controller Mode \0\label "procctrl"\p\p
\{\3\goto "How To Use Controller Mode" Changing Controller Mode\}
\p\p\1
Firmware/NVSRAM \0\label "procfirm"\p\p
\{\3\goto "How To Download A New NVSRAM File" Downloading NVSRAM Files\} \p
\{\3\goto "How To Use Firmware Upgrade" Upgrading Controller Firmware Files\}
\p\p\1
Help \0\label "prochelp"\p\p
\{\3\goto "How To Use Online Help" Using Online Help\}
\p\p\1
Locating \0\label "proclocate"\p\p
\{\3\goto "How To Use Locate Module" Locating A RAID Module\} \p
\{\3\goto "How To Use List/Locate Drives" Viewing And Locating Drives\}
\p\p\1
LUN Assignment \0\label "proclun"\p\p
\{\3\goto "How To Use LUN Balancing" Balancing Logical Units Between Active/Active Controller Pairs\}
\p\p\1
Monitoring \0\label "procmon"\p\p
\{\3\goto "How To Change Message Log's Settings" Changing Message Log's Settings\} \p
\{\3\goto "How To Check For Component Failures" Checking For Component Failures\} \p
\{\3\goto "How To Use Module Profile" Obtaining RAID Module Information (Module Profile)\} \p
\{\3\goto "How To Use Performance Monitor" Monitoring A RAID Module's Performance\} \p
\{\3\goto "Monitoring Performance For More Than One Raid Module" Monitoring Performance For More Than One Raid Module\} \p
\{\3\goto "How To Use Message Log" Viewing Problems Or Events Detected (Message Log)\}
\p\p\1
Parity \0\label "procpar"\p\p
\{\3\goto "How To Use Options >> Auto Parity Settings" Automatically Checking/Repairing Parity\} \p
\{\3\goto "How To Use Manual Parity Check/Repair" Manually Checking/Repairing Parity\}
\p\p\1
RAID Modules \0\label "procrm"\p\p
\{\3\goto "How To Add/Remove RAID Modules" Adding Or Removing A RAID Module\} \p
\{\3\goto "How To Edit Module Information" Editing Information For A RAID Module\} \p
\{\3\goto "How To Use Select Module" Selecting A RAID Module\}
\p\p\1
Reconstruction \0\label "procrecon"\p\p
\{\3\goto "How To Change The Reconstruction Rate" Changing The Reconstruction Rate\} \p
\{\3\goto "Manually Starting Reconstruction" Manually Starting Reconstruction\} \p
\{\3\goto "How To View Reconstruction Progress" Viewing Reconstruction Progress\}
\p\p\1
Recovery \0\label "procrecv"\p\p
\{\3\goto "How To Use Recovery Guru" Detecting And Recovering Component Problems (Recovery Guru/Health Check)\} \p
\{\3\goto "How To Use Manual Recovery >> Controller Pairs" Recovering For Controller Pairs Manually\} \p
\{\3\goto "How To Use Manual Recovery >> Drives" Recovering For Drives Manually\} \p
\{\3\goto "How To Use Manual Recovery >> LUNs" Recovering For Logical Units Manually\}
\p\p\1
Save Information \0\label "procsave"\p\p
\{\3\goto "Copy To Clipboard" Copying Message Log Contents\} \p
\{\3\goto "How To Save The Log As Another File" Saving Message Log As Another File Name\} \p
\{\3\goto "How To Use File >> Save Module Profile" Saving Module Profile Details\} \p
\{\3\goto "How To Use File >> Save Performance Data" Saving Performance Monitor Data\}
\p\p\1
Viewing \0\label "procview"\p\p
\{\3\goto "How To View/Verify Cache Size" Cache Memory Size\} \p
\{\3\goto "Viewing Caching Parameter Settings" Caching Parameter Settings\} \p
\{\3\goto "Viewing Component Statuses" Component Statuses\} \p
\{\3\goto "Viewing Fibre Channel Controller Information" Fibre Channel Controller Information\} \p
\{\3\goto "Viewing Firmware Upgrade Progress" Firmware Upgrade/NVSRAM Download Progress\} \p
\{\3\goto "View LUN Assignments For All RAID Modules" LUN Assignments For All RAID Modules\} \p
\{\3\goto "How To Open A Log File" Message Log Files\} \p
\{\3\goto "How To Use Module Profile" RAID Module Information\} \p
\{\3\goto "How To View Reconstruction Progress" Reconstruction Progress\} \p\{\3\goto "Viewing Parity Messages" Parity Messages\}
\p\p\1
Updating \0\label "procup"\p\p
\{\3\goto "How To Download A New NVSRAM File" Downloading An NVSRAM File\} \p
\{\3\goto "Updating Component Statuses" Updating Component Statuses\} \p
\{\3\goto "How To Use Firmware Upgrade" Upgrading Controller Firmware Files\}
\p\p\1
Related Topics \0\label "procrt"\p
\{\3\goto "Common Question Topics" Common Questions\} \p
\{\3\goto "Concept Topics" Concepts\} \p
\{\3\goto "Restriction/Caution Topics" Restrictions/Cautions\} \p
\{\3\goto "Troubleshooting Topics" Troubleshooting\}
\p\p
\{\7\goto "proceduretop" Top Of Page\} \p
\keyword "details, procedures"

\topic "Restriction/Caution Topics" \p\1
Restrictions/Cautions \label "restricttop"
\p\p
Fast Find -- \{\5\goto "restricthost" Host Connections\} | \{\5\goto "restrictlocmod" Locate Module\} | \{\5\goto "restrictlunassign" LUN Assignment\} | \{\5\goto "restrictmanrecv" Manual Recovery\} | \{\5\goto "restrictmlog" Message Log\} | \{\5\goto "restrictmprofile" Module Profile\} | \{\5\goto "restrictparity" Parity\} | \{\5\goto "restrictperform" Performance Monitor\} | \{\5\goto "restrictrecon" Reconstruction\} | \{\5\goto "restrictrecv" Recovery Guru\} | \{\5\goto "restrictsmod" Select Module\} | \{\5\goto "restrictallrt" Related Topics\} \p\p\1
IMPORTANT \0\p
If you do not find the information you are seeking here, check the "Installation and Support Guide" specific to your operating system for the latest restrictions and troubleshooting information.
\p\p\0
\{\3\subtopic "Caching Restrictions" Caching\}
\p\p
\{\3\subtopic "Configuration Restrictions" Configuration\}
\p\p
\{\3\subtopic "Controller Mode Restrictions" Controller Mode\}
\p\p
\{\3\subtopic "Firmware/NVSRAM Restrictions" Firmware/NVSRAM\}
\p\p\label "restricthost"
\{\3\subtopic "Host Connection Restrictions" Host Connection\}
\p\p\label "restrictlocmod"
\{\3\subtopic "Locate Module Restrictions" Locate Module\}
\p\p\label "restrictlunassign"
\{\3\subtopic "LUN Assignment Restrictions" LUN Assignment\}
\p\p\label "restrictmanrecv"
\{\3\subtopic "Manual Recovery Restrictions" Manual Recovery\}
\p\p\label "restrictmlog"
\{\3\subtopic "Message Log Restrictions" Message Log\}
\p\p\label "restrictmprofile"
\{\3\subtopic "Module Profile Restrictions" Module Profile\}
\p\p\label "restrictparity"
\{\3\subtopic "Parity Restrictions" Parity\}
\p\p\label "restrictperform"
\{\3\subtopic "Performance Monitor Restrictions" Performance Monitor\}
\p\p\label "restrictrecon"
\{\3\subtopic "Reconstruction Restrictions" Reconstruction\}
\p\p\label "restrictrecv"
\{\3\subtopic "Recovery Guru Restrictions" Recovery Guru/Health Check\}
\p\p\label "restrictsmod"
\{\3\subtopic "Select Module Restrictions" Select Module\}
\p\p\1
Related Topics \0\label "restrictallrt"\p
\{\3\goto "Common Question Topics" Common Questions\} \p
\{\3\goto "Concept Topics" Concepts\} \p
\{\3\goto "Procedure Topics" Procedures\} \p
\{\3\goto "Troubleshooting Topics" Troubleshooting\}
\p\p
\{\7\goto "restricttop" Top Of Page\} \p
\keyword "restrictions"
\keyword "cautions"

\topic "Caching Restrictions" \p\1
Caching Restrictions \label "cacherestricttop" 
\p\p
Fast Find -- \{\5\goto "cacherestrictrt" Related Topics\}
\p\p\1
Important Notes \0\p\p
Caching Parameters (Maintenance/Tuning Application) is grayed out if: \p\p
\{\1 o \0\} You select a module that has a \{\2\bring_popup "Controller" controller\} earlier than Series 3. \p\p
\{\1 o \0\} You select All RAID Modules. \p\p
\{\1 o \0\} Both controllers in the RAID Module do not have the same or the minimum required \{\2\bring_popup "Cache Memory" cache\} and \{\2\bring_popup "Processor Memory" processor\} size. \p\p
\{\1 o \0\} You select a RAID Module with only one controller. In this case, \{\2\bring_popup "Write Cache Mirroring" Write Cache Mirroring\} is grayed out. This parameter is only available for modules with \{\2\bring_popup "Redundant Controller Pair" redundant\} controller pairs that have the same size cache. \p\p
If Module Profile >> RAID Module >> LUNs or Maintenance/Tuning Application >> Caching Parameters show an asterisk next to the caching parameters column, it indicates that the parameter is enabled, but is NOT currently active. The controller has disabled the parameter for some reason (such as low batteries or controller replacement). If you see this condition, use Message Log (Status Application) to determine the correct action to take. \p\p\1
Related Topics \label "cacherestrictrt"\0\p
\{\3\goto "Caching Concept" Caching\} \p
\{\3\goto "How To Use Caching Parameters" How To Use Caching Parameters\} \p
\{\3\goto "Restriction/Caution Topics" Restrictions/Cautions\}
\p\p
\{\7\goto "cacherestricttop" Top Of Page\}\p
\keyword "cache disabled" \keyword "disabled cache" \keyword "inactive cache" \keyword "restrictions" \keyword "caching" \keyword "parameters, caching" \keyword "Caching Parameters"

\topic "Configuration Restrictions" \p\1
Configuration Restrictions \label "cfgrestricttop" 
\p\p
Fast Find -- \{\5\goto "cfgrestrictdel" Delete\} | \{\5\goto "cfgrestrictmod" Modify\} | \{\5\goto "cfgrestrictlist" List/Locate\} | \{\5\goto "cfgrestricthot" Hot Spares\} | \{\5\goto "cfgrestrictdrv" Drive Selection\} | \{\5\goto "cfgrestrictrt" Related Topics\} \p\p\0
The following restrictions apply for the Configuration Application's tasks. \p\p\1
Creating LUNs \0\p\p
If you are creating the first \{\2\bring_popup "Configured Drive Group" drive group\}/LUN on the \{\2\bring_popup "RAID Module" RAID Module\} (all drives in the module are \{\2\bring_popup "Unassigned Drive Group" unassigned\}), wait for the new LUN to become Optimal before creating \{\2\bring_popup "Logical Unit" LUNs\} on additional drive groups. Also, you cannot perform any tasks on the new drive group while it is being created. \p\p
To prevent configuration conflicts, you should open only one Configuration screen at a time from any one host machine. You must use caution in a \{\2\bring_popup "Multi-Host Configuration" multi-host\} or \{\2\bring_popup "Independent Controller Configuration" independent\} controller configuration or Networked environment NOT to start a second Configuration screen from another host machine/station, especially when creating or deleting drive groups/LUNs. It is permissible to open multiple instances of the other applications. \p\p\1
Deleting LUNs \label "cfgrestrictdel"\0\p\p
Before deleting any \{\2\bring_popup "Logical Unit" LUNs\}, consult the "Installation and Support Guide" specific to your operating system to see if there are restrictions or troubleshooting information for special requirements (such as deleting partitions, de-assigning drive letters, or unmounting filesystems). \p\p
Deleting all LUNs in a \{\2\bring_popup "Configured Drive Group" drive group\} causes the loss of all data on each LUN in that drive group. Deleting one LUN in the drive group causes data loss on only that one LUN. This operation also deletes any filesystems mounted on the LUNs.\p\p
Because deleting LUNs causes data loss, back up data on all LUNs you are deleting. \p\p
You must first stop I/O to the affected RAID Module and you should ensure that no other users are on the system. \p\p
If you have deleted all the LUNs on a RAID Module and are re-creating new LUNs, WAIT for the first LUN/drive group to become Optimal before creating additional new drive groups to make sure the operation is completed successfully. \p\p
Delete is grayed out for any of the following reasons: \p\p
\{\1 o \0\} You select an \{\2\bring_popup "Unassigned Drive Group" unassigned\} drive group. You cannot delete an unassigned drive group. \p\p
\{\1 o \0\} You select a \{\2\bring_popup "Hot Spare" hot spare\} drive group and all of the hot spares are currently being used. You cannot delete a hot spare drive that is being used. Doing so would delete the data contained on it, and would cause the logical unit to have a \{\2\bring_popup "Degraded Mode" Degraded\} or \{\2\bring_popup "Dead Mode" Dead\} status. \p\p
\{\1 o \0\} You select a configured drive group that is not owned by the controller-host machine you are working from (this can occur if the module has an \{\2\bring_popup "Independent Controller Configuration" independent\} controller configuration). \p\p\1
Modifying Groups/LUNs \label "cfgrestrictmod"\0\p\p
Drive groups/LUNs must be \{\2\bring_popup "Optimal Mode" Optimal\} with no \{\2\bring_popup "Hot Spare" hot spare\} drives in use to use the Modify Group/LUN options. \p\p
You can only use one Modify Group/LUN option at a time. If you attempt to perform more than one process, you will get an error message. \p\p
You can not perform a Modify Group/LUN operation while \{\2\bring_popup "Background Formatting" background\} formatting is taking place on the affected LUN. \p\p\1
Listing/Locating Drives \label "cfgrestrictlist"\0\p\p
If there is a drive status of Failed, Offline, or Unresponsive, go to the Recovery Application and select Recovery Guru/Health Check. \p\p
On \{\2\bring_popup "RAID Module" RAID Modules\} with Series 3 (or earlier) controllers, List/Locate blinks the drive activity lights. For best results on one of these controllers, use Locate when no I/O is occurring so that the flashing of the drive \{\2\bring_popup "Activity Lights" activity lights\} can be distinguished from normal I/O. \p\p
On RAID Modules with Series 4 controllers, List/Locate blinks the drive \{\2\bring_popup "Fault Lights" fault lights\} instead. \p\p\1
Creating Hot Spares \label "cfgrestricthot"\0\p\p
\{\2\bring_popup "Hot Spare" Hot spares\} cannot replace drives with a larger capacity (that is, a 2GB hot spare cannot replace a 4 GB Failed drive). When you create a hot spare, the Configuration Application selects the first available drive unless you specify otherwise. If the \{\2\bring_popup "Unassigned Drive Group" unassigned\} drive group contains drives with different capacities, this drive may not be one of the larger capacity drives. Therefore, BEFORE you create a hot spare drive, use List/Locate Drives to record the capacity and location of the larger capacity drives in the unassigned drive group, and then specify one of those drives to ensure that the hot spare can cover for any failed drive in the \{\2\bring_popup "RAID Module" RAID Module\}. \p\p
It is recommended that you not create all your hot spares on the same drive \{\2\bring_popup "SCSI Channel" channel\}. If the drive channel were to fail, these drives would be unable to cover for the other failed drives in the RAID Module. \p\p\1
Selecting Drives \label "cfgrestrictdrv"\0\p\p
This option is grayed out if you are creating additional \{\2\bring_popup "Logical Unit" LUNs\} on an existing \{\2\bring_popup "Configured Drive Group" drive group\}. \p\p
The Move button is grayed out if you specified the maximum number of remaining (\{\2\bring_popup "Unassigned Drive Group"unassigned\}) drives in the Create main screen. \p\p
If you make any changes, make sure that the number of drives shown in the "Selected Drives" list matches the number of drives you specified in the Create main screen. If you do not, you see an error message and cannot continue until these numbers match. \p\p
For best performance, you should assign drives on as many drive \{\2\bring_popup "SCSI Channel" channels\} as you can. If possible, do not select drives that share the same channel (for example, do not select drives [1,1], [1,2], and [1,3] because they are all on channel 1). However, this is a valid configuration; the only risk is that you would lose access to these drives if the channel fails. \p\p
If your unassigned drive group contains drives with different capacities (such as 2 GB and 4 GB), use Options >> Drive Selection to indicate that you want to use EITHER the smaller capacity drives ONLY or the larger capacity drive ONLY. The Configuration Application bases the \{\2\bring_popup "Available Capacity" available capacity\} of the unassigned drive group (displayed in the Create LUN main screen) on the capacity of the smaller drives. For example, if the unassigned drive group consists of 5 drives (three 2GB drives and two 4 GB drives), the available capacity shown is 10 GB (5 x 2 GB). Furthermore, if you create LUNs using mixed capacity drives, you are using only the smallest capacity available (2GB) and you CANNOT access the additional capacity on the larger drives. \p\p\1
Related Topics \label "cfgrestrictrt"\0\p
\{\3\goto "Configuring Concept" Configuring\} \p
\{\3\goto "How To Use Create Hot Spare" How To Use Create Hot Spare\} \p
\{\3\goto "How To Use Create LUN" How To Use Create LUN\} \p
\{\3\goto "How To Use Delete" How To Use Delete\} \p
\{\3\goto "How To Use File >> Reset Configuration" How To Use File >> Reset Configuration\} \p
 \{\3\goto "Restriction/Caution Topics" Restrictions/Cautions\}
\p\p
\{\7\goto "cfgrestricttop" Top Of Page\}\p
\keyword "restrictions" \keyword "configuration" \keyword "selecting drives" \keyword "drive selection" \keyword "independent controller configuration" \keyword "multi-host configuration" \keyword "networked version" \keyword "Delete" \keyword "Create LUN" \keyword "Modify Group/LUN" \keyword "List/Locate Drives" \keyword "Create Hot Spare" \keyword "stop I/Os"

\topic "Controller Mode Restrictions" \p\1
Controller Mode Restrictions \label "ctrlrestricttop" 
\p\p
Fast Find -- \{\5\goto "ctrlrestrictopt" Options\} | \{\5\goto "ctrlrestrictrt" Related Topics\}
\p\p\1
Important Notes \0\p\p
The Controller Mode option (Maintenance/Tuning Application) is grayed out if you select a RAID Module that does not have an \{\2\bring_popup "Active/Passive Controller Pair" active/passive\} controller pair. Thus, you cannot select a module that has only one controller, \{\2\bring_popup "Independent Controller Configuration" independent\} controllers, or already contains an \{\2\bring_popup "Active/Active Controller Pair" active/active\} controller pair. \p\p
You can, however, select All RAID Modules, then Controller Mode to quickly view the controller \{\2\bring_popup "Controller Mode" modes\} for all your RAID Modules. \p\p
Changing controller pairs to active/active CANNOT BE UNDONE using this interface. Once you have changed to active/active, you cannot go back to active/passive EXCEPT by using the command line \{\2\bring_popup "Command Line Utilities" utility\}, rdacutil. \p\p
If you do not have \{\2\bring_popup "RDAC Driver" RDAC\} protection, you must stop all I/O to the RAID Module BEFORE changing a controller's mode. Otherwise, you could cause the operating system to hang. \p\p\1
Options \label "ctrlrestrictopt"\0\p\p
\{\1 o \0\} You can assign drive groups/LUNs to the active controllers after LUN creation or when changing controller modes by using Maintenance/Tuning Application >> LUN Balancing. \p\p
\{\1 o \0\} To quickly view the controller modes for all your RAID Modules without making any changes, you can select Maintenance/Tuning Application >> All RAID Modules >> Controller Mode. \p\p
\{\1 o \0\} You must use the command line utility, rdacutil, if you want to change an active/active controller pair to active/passive. For example, to change the RAID Module's (named sonne_002) controller pair to active/passive, type: \p\p
rdacutil -m 1 ''sonne_002'' \p\p\1
Related Topics \label "ctrlrestrictrt"\0\p
\{\3\goto "How To Use Controller Mode" How To Use Controller Mode\} \p
\{\3\goto "Restriction/Caution Topics" Restrictions/Cautions\}
\p\p
\{\7\goto "ctrlrestricttop" Top Of Page\}\p
\keyword "Controller Mode" \keyword "rdacutil utility" \keyword "RDAC" \keyword "restrictions" \keyword "independent controller configuration" \keyword "changing active/passive" \keyword "changing active/active" \keyword "Swap Active/Passive" \keyword "stop I/Os"

\topic "Firmware/NVSRAM Restrictions" \p\1
Firmware/NVSRAM Restrictions \label "firmrestricttop" 
\p\p
Fast Find -- \{\5\goto "firmimp" Firmware\} | \{\5\goto "firmnvsram" NVSRAM\} | \{\5\goto "firmrestrictrt" Related Topics\} \p\p\0
The following restrictions apply when using the Firmware Upgrade option (Maintenance/Tuning Application) to download either controller \{\2\bring_popup "Firmware" firmware\} files or \{\2\bring_popup "NVSRAM File" NVSRAM\} files. \p\p\1
GENERAL RESTRICTIONS \p\p
The \{\2\bring_popup "Online Firmware Upgrade" Online\} option: \p\p\0
\{\1 o \0\} Is grayed out if you select a \{\2\bring_popup "RAID Module" RAID Module\} that (1) does NOT have two Series 3 or Series 4 controllers AND you do not have the \{\2\bring_popup "RDAC Driver" driver\} installed for redundant controller support, or (2) has an \{\2\bring_popup "Independent Controller Configuration" independent\} controller configuration. \p\p
\{\1 o \0\} Does not work on a module that has any \{\2\bring_popup "Logical Unit" LUN\} with a status other than Optimal. \p\p\1
The \{\2\bring_popup "Offline Firmware Upgrade" Offline\} option: \p\p\0
\{\1 o \0\} Does not work unless you have stopped I/O to the selected RAID Module. This option is useful if several of your modules have only one controller; you may want to upgrade firmware on only one RAID Module at a time so that you do not have to stop all I/O. \p\p
\{\1 o \0\} Requires exclusive access to the LUNs in the selected RAID Modules; that is, no other operations can be running on the RAID Module. Consult the "Installation and Support Guide" specific to your operating system for details on LUNs with filesystems. \p\p
\{\1 o \0\} Requires that if you are using a UNIX system, you MUST first unmount any filesystems contained on the selected RAID Modules' LUNs, so the storage management software has exclusive access to them. \p\p\1
FIRMWARE RESTRICTIONS/CAUTIONS \label "firmimp"\p\p\4
Cautions \0\p\p
In most cases, you will have to download a new \{\2\bring_popup "NVSRAM File" NVSRAM\} file BEFORE upgrading the controller \{\2\bring_popup "Firmware" firmware\}, especially if you are upgrading from one major firmware release to another (for example, from 2.x to 3.x). You can use the Firmware Upgrade option to download NVSRAM files. \p\p
Remember that both controllers in a \{\2\bring_popup "Redundant Controller Pair" redundant\} pair must have the same version of controller firmware installed. Therefore, it is strongly recommended that you select both controllers to ensure that they have compatible versions of NVSRAM/controller firmware UNLESS you are replacing a failed controller and the replacement controller has an earlier firmware version than the original pair was using. \p\p\1
Important Notes \0\p\p
Controller firmware is different from the drive firmware. You can only use this option to upgrade controller firmware when you receive new firmware upgrade files. If you need to upgrade drive firmware, call your Customer Services Representative. \p\p
If you do not copy the \{\2\bring_popup "fwcompat.def File" fwcompat.def\} file to the correct \{\2\bring_popup "Subdirectory, Firmware" subdirectory\}, the software is unable to check the files for compatibility. Although you can still enter firmware filenames, the software is unable to check the firmware files for compatibility or to provide you with a list of compatible files to select for downloading. \p\p\1
NVSRAM RESTRICTIONS/CAUTIONS \label "firmnvsram"\p\p\4
Cautions \0\p\p
In most cases, you will have to download a new \{\2\bring_popup "NVSRAM File" NVSRAM\} file BEFORE upgrading the controller \{\2\bring_popup "Firmware" firmware\}, especially if you are upgrading from one major firmware release to another (for example, from 2.x to 3.x). You can use the Firmware Upgrade option to download NVSRAM files. \p\p 
Remember that both controllers in a \{\2\bring_popup "Redundant Controller Pair" redundant\} pair must have the same version of controller firmware installed. Therefore, it is strongly recommended that you select both controllers to ensure that they have compatible versions of NVSRAM/controller firmware UNLESS you are replacing a failed controller and the replacement controller has an earlier firmware version than the original pair was using. \p\p\1
Important Notes \0\p\p
If you do not load the NVSRAM file, certain features in this software and in the controller may not work. Also, if you have RAID Modules with a pair of redundant controllers, it is recommended that you download to both controllers at the same time to ensure that both controllers have the same level of NVSRAM and controller firmware files. \p\p
The fibre channel Loop ID in the NVSRAM bit (Byte 3 in the Fibre Channel Interface Parameters Buffer, Write Buffer ID 0xED) is required for fibre channel controllers to be able to determine the \{\2\bring_popup "Preferred Loop ID" Preferred Loop ID\} and \{\2\bring_popup "Controller ID - NL_Port" Controller ID - NL_Port\}. \p\p\1
Related Topics \label "firmrestrictrt"\0\p
\{\3\goto "Firmware Concept" Firmware\} \p
\{\3\goto "How To Download A New NVSRAM File" How To Download A New NVSRAM File\} \p
\{\3\goto "How To Use Firmware Upgrade" How To Use Firmware Upgrade\} \p
\{\3\goto "NVSRAM Concept" NVSRAM\} \p
\{\3\goto "Restriction/Caution Topics" Restrictions/Cautions\}
\p\p
\{\7\goto "firmrestricttop" Top Of Page\}\p
\keyword "RDAC" \keyword "NVSRAM" \keyword "controller firmware" \keyword "firmware" \keyword "restrictions" \keyword "cautions" \keyword "online firmware upgrade" \keyword "offline firmware upgrade" \keyword "independent controller configuration" \keyword "fibre channel" \keyword "fwcompat.def file" \keyword "stop I/Os"

\topic "Host Connection Restrictions" \p\1
Host Connection Restrictions \label "hostrestricttop" 
\p\p
Fast Find -- \{\5\goto "hostrestrictimp" Important Notes\} | \{\5\goto "hostrestrictrt" Related Topics\}
\p\p\4
Cautions \0\p\p
No host-RAID Module configurations or combinations are supported beyond the three described: \{\2\bring_popup "Single-Host Configuration" single-host\}, \{\2\bring_popup "Multi-Host Configuration" multi-host\}, and \{\2\bring_popup "Independent Controller Configuration" independent controller\}. Furthermore, the software's operation cannot be guaranteed to work as intended/described in the operating-system specific "Installation and Support Guide," the "User Guide," or this online help if other configurations are used. Also, not every operating system supports the multi-host configuration. Be sure to consult the restrictions in the operating-system specific "Installation and Support Guide." \p\p
Because it is possible to open a Configuration Application from both hosts in a multi-host or independent controller configuration, be sure that you have only ONE configuration session open at a time (from only one host) when creating or deleting \{\2\bring_popup "Logical Unit" LUNs\} or the operation will fail on one of the hosts. \p\p
\{\2\bring_popup "Drive Group"Drive groups\} /LUNs and their data could be lost if more than one "destructive" operation is launched in a multi-host environment. No other operations should be attempted on the same drive group/LUN if one of these operations is still being completed. Operations requiring exclusive access to the LUNs are: \p\p\1
\{\1 o \0\} Configuration Application\0 -- Delete for LUNs and File >> Reset Configuration \p\p\1
\{\1 o \0\} Recovery Application\0 -- Formatting a LUN with Options >> Manual Recovery >> Logical Units \p\p\1
\{\1 o \0\} Maintenance/Tuning Application\0 -- Firmware Upgrade >> Offline method \p\p\1
Important Notes \0\label "hostrestrictimp"\p\p
The Networked version of the storage management software always sees both \{\2\bring_popup "Controller" controllers\} in a dual-controller \{\2\bring_popup "RAID Module" RAID Module\} regardless of the configurations mentioned here. However, the Networked version is able to show when a RAID Module is using the independent controller configuration ONLY if you set use Select Module >> Edit to indicate independent controllers. \p\p
The \{\2\bring_popup "Single-Host Configuration" single-host\} configuration is the recommended configuration because it provides the fullest functionality and complete \{\2\bring_popup "RDAC Driver" RDAC\} failover support with two \{\2\bring_popup "Redundant Controller Pair" active\} controllers. \p\p
Consult the "Installation and Support Guide" specific to your operating system for special requirements or restrictions that may apply to using RDAC in that environment. For example, you do not have RDAC support in the network connection or if the RAID Module is using the \{\2\bring_popup "Independent Controller Configuration" independent\} controller configuration. \p\p\1
Related Topics \label "hostrestrictrt"\0\p
\{\3\goto "Host Interface Connections Concept" Host Interface Connections\} \p
\{\3\goto "Host-RAID Module Configuration Types Supported Concept" Host-RAID Module Configuration Types Supported\} \p
\{\3\goto "Restriction/Caution Topics" Restrictions/Cautions\}
\p\p
\{\7\goto "hostrestricttop" Top Of Page\}\p
\keyword "RDAC" \keyword "restrictions" \keyword "independent controller configuration" \keyword "multi-host configuration" \keyword "single-host configuration" \keyword "networked version" \keyword "cautions" \keyword "host interface" \keyword "exclusive access operations" \keyword "operations requiring exclusive access"

\topic "Locate Module Restrictions" \p\1
Locate Module Restrictions \p\p
Important Notes \0\p\p
You can locate only one \{\2\bring_popup "RAID Module" RAID Module\} at a time. If you choose All RAID Modules, Locate Module is grayed out and not selectable.
\p\p
Any drives with a status other than Optimal are skipped (that is, the drive \{\2\bring_popup "Activity Lights" activity\} or \{\2\bring_popup "Fault Lights" fault\} lights do not flash).
\p\p
On RAID Modules with Series 3 (or earlier) controllers, Locate blinks the drive activity lights. For best results on one of these controllers, use Locate when no I/O is occurring so that the flashing of the activity lights can be distinguished from normal I/O. \p\p
On RAID Modules with Series 4 controllers, List/Locate blinks the drive fault lights. \p\p
This option is available from any application on the Tool bar or from the Module pull-down menu.
\p\p\1
Related Topics \0\p
\{\3\goto "How To Use Locate Module" How To Use Locate Module\} \p
\{\3\goto "Restriction/Caution Topics" Restrictions/Cautions\} \p
\keyword "Locate Module" \keyword "restrictions" \keyword "finding modules" \keyword "modules, locating" \keyword "activity lights"

\topic "LUN Assignment Restrictions" \p\1
LUN Assignment Restrictions \label "lunrestricttop" 
\p\p
Fast Find -- \{\5\goto "lunrestrictrt" Related Topics\}
\p\p
Important Notes \0\p\p
The LUN Balancing option (Maintenance/Tuning Application) is grayed out if you select a \{\2\bring_popup "RAID Module" RAID Module\} that has one \{\2\bring_popup "Controller" controller\} or an \{\2\bring_popup "Active/Passive Controller Pair" active/passive\} controller pair. You can only balance the LUN \{\2\bring_popup "LUN Assignment" assignment\} for RAID Modules with \{\2\bring_popup "Active/Active Controller Pair" active/active\} controller pairs. \p\p
If you do NOT have \{\2\bring_popup "RDAC Driver" RDAC\} protection, you must stop I/O to the RAID Module BEFORE changing LUN assignment. Otherwise, you could cause the operating system to hang. \p\p
You can select Cancel at any time to close this option without changing any LUN assignments. \p\p
When selecting LUN Balancing for one RAID Module, use Move (<< / >>) to move a highlighted \{\2\bring_popup "Configured Drive Group" drive group\} from one controller to the other controller. However, you do NOT actually balance the LUNs until you select Save. \p\p
If the selected RAID Module has an \{\2\bring_popup "Independent Controller Configuration" independent\} controller configuration, you are able to move drive group/LUNs FROM the \{\2\bring_popup "Inaccessible" Inaccessible\} controller TO the \{\2\bring_popup "Active Controller Mode" Active\} controller. However, you will not be able to give them back. You should NOT use this procedure unless directed by Recovery Guru/Health Check or a Customer Services Representative. \p\p\1
Related Topics \label "lunrestrictrt"\0\p
\{\3\goto "How To Use LUN Balancing" How To Use LUN Balancing\} \p
\{\3\goto "LUN Assignment Concept" LUN Assignment\} \p
\{\3\goto "Restriction/Caution Topics" Restrictions/Cautions\}
\p\p
\{\7\goto "lunrestricttop" Top Of Page\} \p
\keyword "LUN Balancing" \keyword "RDAC" \keyword "restrictions" \keyword "independent controller configuration" \keyword "Inaccessible" \keyword "stop I/Os"

\topic "Manual Recovery Restrictions" \p\1
Manual Recovery Restrictions \label "manrecvrestricttop" 
\p\p
Fast Find -- \{\5\goto "manctrlrestrict" Controllers\} | \{\5\goto "mandrvrestrict" Drives\} | \{\5\goto "manlunrestrict" Logical Units\} | \{\5\goto "manrecvrestrictrt" Related Topics\} \p\p\0
The Manual Recovery options (Recovery Application) are available only from the Options pull-down menu. \p\p\4
Cautions\1 -- All Options \0\p\p
Do NOT use Options >> Manual Recovery unless specifically directed by Recovery Guru/Health Check >> Show Procedure, your software documentation, or a Customer Services Representative. Doing so could result in the loss of data or damage to equipment. \p\p
Always select Recovery Guru/Health Check to ensure the problem is correctly diagnosed BEFORE attempting any manual recovery procedure. Incorrectly performing a procedure or performing the wrong procedure could cause equipment damage or data loss. Recovery Guru provides step-by-step procedures to make sure that you are correcting the right problem and directs you when to use the manual recovery options. \p\p
Do NOT attempt to manually recover from a component failure without understanding the circumstances of the failure. For example, the correct procedure for recovering from a drive failure varies depending on the \{\2\bring_popup "RAID Level" RAID Level\} of the affected \{\2\bring_popup "Logical Unit" LUN\}, the number of drives that failed, and on whether or not a \{\2\bring_popup "Hot Spare" hot spare\} drive is in use. Similarly, the type of \{\2\bring_popup "Controller" controller\} for the affected module could indicate different procedures for the various kinds of drive and controller failures. Therefore, it is best to use Recovery Guru. \p\p
Options >> Manual Recovery is grayed out if you select All RAID Modules. \p\p\1
Controller Pairs \label "manctrlrestrict"\0\p\p
The Controller Pairs option is grayed out if the selected \{\2\bring_popup "RAID Module" RAID Module\} has only one controller. \p\p
The Place Offline option is grayed out if one controller in the RAID Module already has an \{\2\bring_popup "Offline Controller Mode" Offline\} status. You can place only one controller in a module Offline at a time. \p\p
If you are using the Place Offline option to replace the controller, WAIT one minute BEFORE inserting a new controller. \p\p
The Place Online option is grayed out if both controllers in the RAID Module have an \{\2\bring_popup "Optimal Mode" Optimal\} status.\p\p\1
Drives \label "mandrvrestrict"\0\p\p
When a drive is \{\2\bring_popup "Unassigned Drive Group" unassigned\} (that is, not configured as part of a LUN), you see dashes in every column except location. There is no status, LUN, RAID Level, or LUN status to report. \p\p
The Fail option is grayed out for drives with Failed or Replaced drive statuses or with Reconstructing or Formatting LUN statuses. \p\p
The Reconstruct option is grayed out for drives in a \{\2\bring_popup "RAID 0" RAID 0\} LUN or with Reconstructing or Formatting LUN statuses. You can only reconstruct drives with Failed or Replaced drive statuses in a RAID 1, 3, or 5 LUN. \p\p
The Revive option is grayed out for drives with Optimal drive statuses or with Reconstructing or Formatting LUN statuses. \p\p
You should use the Revive option for drives ONLY when you accidentally removed the wrong drive and it was \{\2\bring_popup "Optimal Mode" Optimal\} when you removed it. Never use this procedure if the controller has marked the drive as failed, or if the LUN containing the drive is a RAID Level 0 and has another drive already Failed or in Warning. \p\p\1
LUNs \label "manlunrestrict"\0\p\p
In the case of a \{\2\bring_popup "Dead Mode" Dead\} LUN, you see all the LUNs for the affected drive group on a single line. Thus, highlighting that line selects all those LUNs, and any recovery procedure affects every LUN for the drive group. \p\p
Selecting the Format option destroys all data on every LUN in the drive group. Therefore, you lose all data in the drive group and must use a backup copy to restore data after the format is completed. \p\p
Selecting the Revive option may corrupt data on every LUN in the drive group. Therefore, you could lose all data in the drive group and would have to use a backup copy to restore data after the revive is completed. \p\p\1
Related Topics \label "manrecvrestrictrt"\0\p
\{\3\goto "How To Use Options >> Manual Recovery" How To Use Options >> Manual Recovery\} \p
\{\3\goto "Restriction/Caution Topics" Restrictions/Cautions\}
\p\p
\{\7\goto "manrecvrestricttop" Top Of Page\}\p
\keyword "Options menu" \keyword "Manual Recovery options" \keyword "restrictions" \keyword "cautions" \keyword "Place Offline" \keyword "Place Online" \keyword "Fail drive" \keyword "Revive drive" \keyword "Format LUN" \keyword "Revive LUN" \keyword "reconstruction" \keyword "manual reconstruction"

\topic "Message Log Restrictions" \p\1
Message Log Restrictions \label "mlogrestricttop" 
\p\p
Fast Find -- \{\5\goto "mlogrestrictsla" Save Log\} | \{\5\goto "mlogrestrictra" Refresh All\} | \{\5\goto "mlogrestrictls" Log Settings\} | \{\5\goto "mlogrestrictrt" Related Topics\} \p\p\0
The following restrictions apply for the Message Log (Status Application) and its associated tasks. \p\p\1
General Restrictions \0\p\p
You must be in Message Log or the following options are grayed out: File >> Open Log, File >> Save Log As, Options >> Refresh All. \p\p
When you exit Message Log and return, or when you select Options >> Refresh All, ALL of the message types appear again in the summary information screen (this is the default setting for List Type). \p\p\1
List Type \0\p\p
When using List Types, you must select either All or Hardware before you can select the \{\2\bring_popup "ASC/ASCQ Code" ASC/ASCQ\} box. \p\p\1
Open Log \0\p\p
Using File >> Open Log: \p\p
\{\1 o \0\} If you see the "Log file is corrupted" message, it means that either the file is bad or you have not selected an appropriate log file. \p\p
\{\1 o \0\} Opening another log file does not change the default log that the software writes messages to. From the top menu, select Options >> Log Settings to change the default log file. \p\p\1
Save Log As \label "mlogrestrictsla" \0\p\p
Using File >> Save Log As: \p\p
\{\1 o \0\} If you select or enter a filename that already exists, selecting OK overwrites the existing data in that file. \p\p
\{\1 o \0\} Saving the log to another file does not change the default log that the software writes messages to. From the top menu, select Options >> Log Settings to change the default log file. \p\p\1
Refresh All \label "mlogrestrictra"\0\p\p
The \{\2\bring_popup "Maximum Message Log Size" size\} of the \{\2\bring_popup "Log File" log\} file can affect the time it takes to update the screen when using Options >> Refresh All. \p\p\1
Log Settings \label "mlogrestrictls"\0\p\p
Using Options >> Log Settings: \p\p
\{\1 o \0\} Changing the default \{\2\bring_popup "Log File" log\} does NOT automatically change which log is displayed in Message Log until you exit the Status Application. \p\p
\{\1 o \0\} Although you cannot disable the Maximum Message Log Size option, you can set the size to the maximum value (1000K) to reduce the frequency of notification that the maximum size has been exceeded. \p\p
\{\1 o \0\} Depending on the checking \{\2\bring_popup "Checking Interval" interval\}, it is possible to use Recovery Guru/Health Check (Recovery Application) to find and correct problems before the background monitor detects them. In cases where you have corrected problems BEFORE the background monitor detects them, these events are not detected or written to the Message Log. \p\p\1
Related Topics \label "mlogrestrictrt" \0\p
\{\3\goto "How To Change Message Log's Settings" How To Change Message Log's Settings\} \p
\{\3\goto "How To Refresh Message Log" How To Refresh Message Log\} \p
\{\3\goto "How To List Different Types Of Messages" How To List Different Types Of Messages\} \p
\{\3\goto "How To Open A Log File" How To Open An Existing Log File\} \p
\{\3\goto "How To Save The Log As Another File" How To Save The Log As Another File Name\} \p
\{\3\goto "How To Use Message Log" How To Use Message Log\} \p
\{\3\goto "Restriction/Caution Topics" Restrictions/Cautions\}
\p\p
\{\7\goto "mlogrestricttop" Top Of Page\}\p
\keyword "Message Log" \keyword "restrictions" \keyword "List Type" \keyword "open" \keyword "save" \keyword "refresh" \keyword "log file" \keyword "settings" \keyword "File menu" \keyword "Options menu" \keyword "ASC/ASCQ"

\topic "Module Profile Restrictions" \p\1
Module Profile Restrictions \label "mprofilerestricttop" 
\p\p
Fast Find -- \{\5\goto "mprofilerestrictrt" Related Topics\}
\p\p
Important Notes \0\p\p
The Module Profile option is grayed out if you select All RAID Modules. \p\p
If you are in Module Profile, the File >> Save Module Profile option is unavailable until you close that screen. \p\p
The File >> Save Module Profile option is grayed out if you select All RAID Modules. \p\p
When saving a module profile, if you select or enter a filename that already exists, selecting OK overwrites the existing data in that file. \p\p
It is very important that you save the profile of each RAID Module during initial installation and any time you change your configuration. You can use this information as a reference if you need to perform any recovery or maintenance tasks. \p\p
This option is available from any application on the Tool bar or from the Module pull-down menu.
\p\p\1
Related Topics \0\label "mprofilerestrictrt"\p
\{\3\goto "How To Use Module Profile" How To Use Module Profile\} \p
\{\3\goto "How To Use File >> Save Module Profile" How To Save A Module Profile\} \p
\{\3\goto "Restriction/Caution Topics" Restrictions/Cautions\}
\p\p
\{\7\goto "mprofilerestricttop" Top Of Page\}\p
\keyword "restrictions" \keyword "Module Profile" \keyword "save"

\topic "Parity Restrictions" \p\1
Parity Restrictions \label "parityrestricttop" 
\p\p
Fast Find -- \{\5\goto "parityrestrictrt" Related Topics\}
\p\p\4
Cautions \0\p\p
A \{\2\bring_popup "RAID 0" RAID 0\} LUN does not have \{\2\bring_popup "Parity" parity\} and therefore cannot be checked and repaired. \p\p
A \{\2\bring_popup "RAID 1" RAID 1\} LUN does not have parity, but you can still run parity check on it. In this case, the check compares the data on the mirrored drives. \p\p
You cannot run parity check/repair on RAID 1, 3, or 5 \{\2\bring_popup "Logical Unit" LUNs\} with a status other than Optimal. \p\p
While Manual Parity Check/Repair (Recovery Application) is in progress, you cannot perform other Recovery Application tasks. You can, however, select Cancel at any time during parity check. However, if you stop this operation, your parity has NOT been completely checked or repaired. \p\p\1
Important Notes \0\p\p
Parity \{\2\bring_popup "Parity Check/Repair" check/repair\} fixes parity, not data. If the parity inconsistencies resulted from corrupted data, the data is still corrupted, but the parity is correct. Therefore, parity inconsistencies might indicate corrupt data. You may be able to use your operating system to verify your data. \p\p
Select a time of slow system use for the Automatic Parity Check/Repair (Maintenance/Tuning Application) to run so that system performance is not adversely affected while parity is checked and repaired. \p\p
Remember that changing any of the Options >> Auto Parity Settings (Maintenance/Tuning Application) affects ALL your RAID Modules. \p\p
It is strongly recommended that you enable the automatic option so that parity is checked either daily or once a week (Maintenance/Tuning Application >> Options >> Auto Parity Settings). However, consult the "Installation and Support Guide" specific to your operating system to check for any restrictions that may apply. \p\p\1
Related Topics \label "parityrestrictrt"\0\p
\{\3\goto "How To Use Manual Parity Check/Repair" How To Use Manual Parity Check/Repair\} \p
\{\3\goto "How To Use Options >> Auto Parity Settings" How To Use Options >> Auto Parity Settings\} \p
\{\3\goto "Parity Concept" Parity\} \p
\{\3\goto "Restriction/Caution Topics" Restrictions/Cautions\}
\p\p
\{\7\goto "parityrestricttop" Top Of Page\}\p
\keyword "parity" \keyword "automatic parity" \keyword "manual parity" \keyword "restrictions" \keyword "cautions"

\topic "Performance Monitor Restrictions" \p\1
Performance Monitor Restrictions \p\p\1
Important Notes \0\p\p
Performance Monitor (Status Application) is grayed out if you select All RAID Modules. \p\p
When using File >> Save Performance Data, if you select or enter a filename that already exists, selecting OK overwrites the existing data in that file. \p\p
Opening multiple instances of the Status Application to monitor the performance of different \{\2\bring_popup "RAID Module" RAID Modules\} can cause a performance drain on the system. \p\p
Opening multiple instances of the Status Application to monitor the performance of the same RAID Module will cause one instance to error out. \p\p\1
Related Topics \0\p
\{\3\goto "How To Use File >> Save Performance Data" How To Use File >> Save Performance Data\} \p
\{\3\goto "How To Use Performance Monitor" How To Use Performance Monitor\} \p
\{\3\goto "Performance Concept" Performance\} \p
\{\3\goto "Restriction/Caution Topics" Restrictions/Cautions\} \p
\keyword "restrictions" \keyword "Performance Monitor" \keyword "save"

\topic "Reconstruction Restrictions" \p\1
Reconstruction Restrictions \0\p\p
The LUN Reconstruction (Status Application) and LUN Reconstruction Rate (Maintenance/Tuning Application) options are grayed out if All RAID Modules is selected. \p\p
In Status Application >> LUN Reconstruction, the LUNs that have completed reconstruction show 100%, but disappear if you exit Status. \p\p
If the RAID Module uses the \{\2\bring_popup "Independent Controller Configuration" independent\} controller configuration, you must change the \{\2\bring_popup "Reconstruction Rate" rate\} from the host that owns the LUNs. Do NOT attempt to change the rate for LUNs marked \{\2\bring_popup "Inaccessible" Inaccessible\} or an error message will appear.
\p\p\1
Related Topics \0\p
\{\3\goto "How To Change The Reconstruction Rate" How To Change The Reconstruction Rate\} \p
\{\3\goto "How To View Reconstruction Progress" How To View Reconstruction Progress\} \p
\{\3\goto "Reconstruction Concept" Reconstruction\} \p
\{\3\goto "Restriction/Caution Topics" Restrictions/Cautions\} \p
\keyword "reconstruction" \keyword "LUN Reconstruction" \keyword "LUN Reconstruction Rate" \keyword "restrictions" \keyword "independent controller configuration" \keyword "Inaccessible"

\topic "Recovery Guru Restrictions" \p\1
Recovery Guru/Health Check Restrictions \label "gururestricttop" 
\p\p
Fast Find -- \{\5\goto "gururestrictrt" Related Topics\} \p\p\0
The following restrictions apply when using the Recovery Guru/Health Check option (Recovery Application).
\p\p\1
Important Notes \0\p\p
You cannot highlight a \{\2\bring_popup "RAID Module" RAID Module\} that is Optimal; there are no problems to correct. \p\p
Show Procedures is grayed out if all the selected RAID Modules are \{\2\bring_popup "Optimal Mode" Optimal\}. \p\p
It is possible to see a RAID Module listed more than once when it has multiple failures. For example, if a RAID Module has both a failed battery and a failed fan, two entries appear for this module: Failed Fan on one line and Failed Battery on another line. \p\p
Recovery Guru lists failures in the order (top-to-bottom) that you should fix them. For example, it is best to fix module failures before any drive failures. When you see more than one failure listed in the Result column, select the first item in the list (in most cases it is highlighted already) and follow the step-by-step procedure given to correct the problem. Continue highlighting each result (top-to-bottom) until all problems have been corrected. \p\p
Even when Recovery Guru reports all modules as Optimal, you can view or print any recovery procedure by selecting Help >> Recovery Guru Procedures from the top menu in the Recovery Application. However, you should use these topics for reference only; they do NOT contain the same component-specific information as the Show Procedure instructions display after running Recovery Guru.
\p\p\1
Related Topics \0\label "gururestrictrt"\p
\{\3\goto "How To Use Recovery Guru" How To Use Recovery Guru/Health Check\} \p
\{\3\goto "Restriction/Caution Topics" Restrictions/Cautions\}
\p\p
\{\7\goto "gururestricttop" Top Of Page\}\p
\keyword "restrictions" \keyword "Recovery Guru" \keyword "Show Procedures"

\topic "Select Module Restrictions" \p\1
Select Module Restrictions \label "smodrestricttop" 
\p\p
Fast Find -- \{\5\goto "smodrestrictrt" Related Topics\}
\p\p
Important Notes \0\p\p
The Add option is available in the Networked version ONLY. \p\p
You can only remove one module at a time. The Remove option is grayed out if you select All RAID Modules. \p\p
You can only edit information for one module at a time. The Edit option is grayed out if you select All RAID Modules. \p\p
Use the Add or Edit option to click the box next to Independent Controllers and indicate the RAID Module is using the \{\2\bring_popup "Independent Controller Configuration" independent\} controller configuration. (In the main Select Module screen, the "Indep. Cntrls?" column says Yes.) \p\p
This option is available from any application on the Tool bar or from the Module pull-down menu.
\p\p\1
NOTE\0: The Networked version always sees both controllers in a dual-controller RAID Module regardless of which configuration you have. However, the software indicates that a RAID Module is using independent controllers ONLY if you use this option.
\p\p\1
Related Topics \0\label "smodrestrictrt"\p
\{\3\goto "How To Use Select Module" How To Use Select Module\} \p
\{\3\goto "Restriction/Caution Topics" Restrictions/Cautions\}
\p\p
\{\7\goto "smodrestricttop" Top Of Page\}\p
\keyword "Select Module" \keyword "networked version" \keyword "restrictions" \keyword "adding modules" \keyword "remove modules" \keyword "edit module information" \keyword "modules, adding" \keyword "modules, removing" \keyword "module information"

\topic "Common Question Topics" \p\1
Common Questions \label "cqtop"
\p\p
Fast Find -- \{\5\goto "cqperform" Performance Monitor\} | \{\5\goto "cqrecon" Reconstruction\} | \{\5\goto "cqrecv" Recovery\} | \{\5\goto "cqrt" Related Topics\}
\p\p\0
\{\3\subtopic "Component Questions" Components\}
\p\p
\{\3\subtopic "Configuration Questions" Configuration\}
\p\p
\{\3\subtopic "Firmware/NVSRAM Questions" Firmware/NVSRAM\}
\p\p
\{\3\subtopic "Host Connection Questions" Host Connection\}
\p\p
\{\3\subtopic "LUN Assignment Questions" LUN Assignment\}
\p\p
\{\3\subtopic "Manual Recovery Questions" Manual Recovery\}
\p\p
\{\3\subtopic "Message Log Questions" Message Log\}
\p\p
\{\3\subtopic "Parity Questions" Parity\}
\p\p\label "cqperform"
\{\3\subtopic "Performance Monitor Questions" Performance Monitor\}
\p\p\label "cqrecon"
\{\3\subtopic "Manually Starting Reconstruction" Reconstruction\}
\p\p\label "cqrecv"
\{\3\subtopic "When To Use Recovery Guru" Recovery Guru/Health Check\}
\p\p\1
Related Topics \0\label "cqrt"\p
\{\3\goto "Concept Topics" Concepts\} \p
\{\3\goto "Procedure Topics" Procedures\} \p
\{\3\goto "Restriction/Caution Topics" Restrictions/Cautions\} \p
\{\3\goto "Troubleshooting Topics" Troubleshooting\}
\p\p
\{\7\goto "cqtop" Top Of Page\} \p
\keyword "details, common questions" \keyword "questions"

\topic "Component Questions" \p\1
Component Questions \0\p\p
\{\3\subtopic "How To Check For Component Failures" How Can I Check For Component Failures?\}
\p\p
\{\3\subtopic "Number And Type Of Controllers In A RAID Module" How Many And What Kind Of Controllers Does A RAID Module Have?\}
\p\p
\{\3\subtopic "Why Could The Drive Groups Be Renumbered?" Why Could The Drive Groups Be Renumbered?\}
\p\p\1
Related Topics\0\p
\{\3\goto "Component Concept" Component\} \p
\{\3\goto "Common Question Topics" Common Questions\} \p
\keyword "component details" \keyword "details, components" \keyword "questions"

\topic "How To Check For Component Failures" \p\1
How Can I Check For Component Failures? \0\p\p
There are three easy ways to check for problems on your \{\2\bring_popup "RAID Module" RAID Modules\}: \p\p
\{\1 o \0\} Use Recovery Application >> Recovery Guru/Health Check to perform an immediate check of the selected RAID Module. If component failures are reported, select Show Procedures and follow the step-by-step instructions provided to correct the problem.
\p\p
\{\1 o \0\} Select Status Application >> Message Log if you want to check for any past failures the background \{\2\bring_popup "Checking Interval" monitor\} has detected.
\p\p
\{\1 o \0\} Select Any Application >> RAID Module >> Module Profile >> Controllers, Drives, or LUNs in any application if you would like a quick view of current component statuses.
\p\p\1
Related Topics\0\p
\{\3\goto "Component Questions" Common Questions\} \p
\{\3\goto "How To Use Message Log" How To Use Message Log\} \p
\{\3\goto "How To Use Module Profile" How To Use Module Profile\} \p
\{\3\goto "How To Use Recovery Guru" How To Use Recovery Guru/Health Check\} \p
\keyword "error detection" \keyword "failures" \keyword "status reporting" \keyword "component details" \keyword "details, components" \keyword "Module Profile" \keyword "Recovery Guru" \keyword "Message Log"

\topic "Number And Type Of Controllers In A RAID Module" \p\1
How Many And What Kind Of Controllers Does A RAID Module Have? \label "numberctrltop" 
\p\p
Fast Find -- \{\5\goto "numberctrlrt" Related Topics\}
\p\p\0
Module Profile >> Controller Detailed Information shows information about the \{\2\bring_popup "Controller" controllers\} associated with a selected \{\2\bring_popup "RAID Module" RAID Module\}. For details of the controller information displayed, select the What Additional Details Can I See? topic in the \{\5\goto "numberctrlrt" Related Topics\} list below. \p\p
1. Select Any Application. \p\p
2. Select a RAID Module >> Module Profile. \p\p
3. Under "Detailed Information," select Controllers. \p\p
-- There is a column for each controller (one designated as A and one as B). If one is marked \{\2\bring_popup "Inaccessible" Inaccessible\} the RAID Module is using an \{\2\bring_popup "Independent Controller Configuration" independent\} controller configuration. \p\p
-- The Board Name and Board ID rows provide the controller's type and model information. \p\p
-- The Host Interface row indicates whether the controllers have a \{\2\bring_popup "Parallel SCSI" Parallel SCSI\} connection or a \{\2\bring_popup "Fibre Channel" Fibre Channel\} connection. \p\p
-- The controller's \{\2\bring_popup "Firmware" firmware\} version level is indicated by the \{\2\bring_popup "Boot Level" Boot\} Level, \{\2\bring_popup "Firmware Level" Firmware\} Level, and \{\2\bring_popup "Fibre Channel Level" Fibre Channel\} Level rows. Note that for firmware levels of 3.0 or greater, the fibre channel firmware is included in the Firmware level. \p\p
4. Exit Module Profile (select OK) when finished.
\p\p\1
Related Topics \label "numberctrlrt"\0\p
\{\3\goto "Component Questions" Common Questions\} \p
\{\3\goto "How To Use Module Profile" How To Use Module Profile\} \p
\{\3\goto "What Additional Details Can I See?" What Additional Details Can I See?\}
\p\p
\{\7\goto "numberctrltop" Top Of Page\}\p
\keyword "parallel SCSI" \keyword "SCSI" \keyword "fibre channel" \keyword "controller information" \keyword "controller type" \keyword "Module Profile"

\topic "Why Could The Drive Groups Be Renumbered?" \p\1
Why Could The Drive Groups Be Renumbered? \label "whynumtop"
\p\p
Fast Find -- \{\5\goto "whynumrt" Related Topics\} \0\p\p
The numbering of the \{\2\bring_popup "Configured Drive Group" drive groups\} is based on the specific logical unit numbers associated with each drive group. The drive group numbering starts with the lowest numbered LUN. For example, the drive group containing LUN 0 is always drive group 1. When you delete LUNs and then add new LUNs, the drive group numbers can change to reflect the new logical unit numbers associated with them.
\p\p\1
Example \0\p
Suppose you had two drive groups configured with two \{\2\bring_popup "Logical Unit" LUNs\} each.
\p\p
\{\1 o \0\} Drive group 1 contains LUNs 0 and 1.
\p\p
\{\1 o \0\} Drive group 2 contains LUNs 2 and 3.
\p\p
Now, you delete LUN 1. In this case, the drive groups are not renumbered (drive group 1 now contains only LUN 0).
\p\p
Next, you create a new drive group. The new drive group uses the first available LUN; in this case, LUN 1. The drive groups are renumbered as follows: \p\p
\{\1 o \0\} Drive group 1 contains LUN 0.
\p\p
\{\1 o \} Drive group 2 contains LUN 1.
\p\p
\{\1 o \0\} Drive group 3 contains LUNs 2 and 3.
\p\p\1
Related Topics\0\label "whynumrt"\p
\{\3\goto "Component Questions" Common Questions\} \p
\{\3\goto "Configuration Application" Configuration Application\}
\p\p
\{\7\goto "whynumtop" Top Of Page\} \p
\keyword "drive information" \keyword "drive group, displayed" \keyword "renumbered drive groups"

\topic "Configuration Questions" \p\1
Configuration Questions \label "cfgcqtop"
\p\p
Fast Find -- \{\5\goto "cfgcqrt" Related Topics\} \0\p\p
\{\3\subtopic "Considerations For Two Active Controllers" Any Special Considerations For A Module With Two Active Controllers?\}
\p\p
\{\3\subtopic "Considerations For Deleting LUNs" Any Special Considerations When Deleting LUNs/Drive Groups?\} \p\p
\{\3\subtopic "How LUNs Are Formatted" How LUNs Are Formatted\}
\p\p
\{\3\subtopic "Time It Takes To Create A LUN" How Long Does It Take To Create/Format A LUN?\}
\p\p
\{\3\subtopic "How Many Hot Spare Drives Can I Configure?" How Many Hot Spare Drives Can I Configure?\}
\p\p
\{\3\subtopic "What Are The Different Flashing Patterns?" What Are The Different Flashing Patterns? (List/Locate Drives)\}
\p\p
\{\3\subtopic "What Can I Do While Creating LUNs?" What Can I Do While LUN Create/Format Is Taking Place?\}
\p\p
\{\3\subtopic "When To Change A Module's Configuration" When Should I Change A Module's Configuration?\}
\p\p
\{\3\subtopic "When To Use File >> Reset Configuration" When Should I Use File >> Reset Configuration?\}
\p\p\1
Related Topics\0\label "cfgcqrt"\p
\{\3\goto "Changing LUN Parameters Concept" Changing Logical Unit Parameters\} \p
\{\3\goto "Common Question Topics" Common Questions\} \p
\{\3\goto "Configuring Concept" Configuring\} \p
\{\3\goto "Configuration Application" Configuration Application\} \p
\{\3\goto "Configuration Restrictions" Restrictions/Cautions\} \p
\{\3\goto "Configuration Troubleshooting" Troubleshooting\}
\p\p
\{\7\goto "cfgcqtop" Top Of Page\} \p
\keyword "configuration" \keyword "questions"

\topic "Considerations For Two Active Controllers" \p\1
Any Special Considerations For A RAID Module With Two Active Controllers? \label "twoactivetop" 
\p\p
Fast Find -- \{\5\goto "twoactivert" Related Topics\} \p\p\0
Yes, but only if you want to manually assign the logical units (LUNs) to a specific controller. The software automatically \{\2\bring_popup "Balanced LUN Distribution" assigns\} all logical units (LUNs) on a new drive group to one of the \{\2\bring_popup "Active/Active Controller Pair" active\} controllers during LUN creation. The first drive group created in a session is assigned to controller A, the second drive group is assigned to controller B, the third to controller A again, and so on. If you frequently create one drive group per session, all drive groups will be assigned to controller A. \p\p
Two applications allow you to manually assign LUNs/drive groups to active controllers: \p\p
\{\1 o \0\} If you are creating LUNs, you can use Configuration Application >> Create LUN >> Options >> LUN Assignment to assign the new \{\2\bring_popup "Configured Drive Group" drive group\} and its corresponding \{\2\bring_popup "Logical Unit" LUNs\} to a specific controller. \p\p\1
NOTE\0: If a RAID Module has an \{\2\bring_popup "Independent Controller Configuration" independent\} controller configuration, each controller owns specific drive groups/LUNs. The LUN Assignment option in Create LUN >> Options is grayed out. \p\p
\{\1 o \0\} If the LUNs are already created, you can change their assignment by using Maintenance/Tuning Application >> LUN Balancing.
\p\p\1
Related Topics \label "twoactivert"\0\p
\{\3\goto "Configuration Questions" Common Questions\} \p
\{\3\goto "How To Use Create LUN" How To Use Create LUN\} \p
\{\3\goto "How To Use LUN Balancing" How To Use LUN Balancing\}
\p\p
\{\7\goto "twoactivetop" Top Of Page\}\p
\keyword "active controllers" \keyword "two active controllers" \keyword "controllers, active" \keyword "LUN assignment" \keyword "configuration"

\topic "Considerations For Deleting LUNs" \p\1
Any Special Considerations When Deleting LUNs/Drive Groups? \label "deleteluntop" 
\p\p
Fast Find -- \{\5\goto "deletelunrt" Related Topics\}
\p\p\0
Yes. If you delete all the drive groups/LUNs on a RAID Module, the module consists of all \{\2\bring_popup "Unassigned Drive Group" unassigned\} drives (that is, there are NO existing LUNs configured on the module). When you begin creating/formatting the first drive group with LUN 0, you could run into problems (such as creation failures) if you attempt to create other LUNs on a different (second) drive group before LUN 0 is formatted. \p\p
This restriction applies to both the graphical user interface (GUI) and the command line program, raidutil. \p\p\1
Recommendation\0 -- Wait for LUN creation to finish on the first drive group/LUNs before creating additional drive groups. Also, remember that some operating systems have special considerations regarding adding/deleting LUNs. Consult the "Installation and Support Guide" that is specific to your operating system.
\p\p\1
Related Topics \label "deletelunrt"\0\p
\{\3\goto "Configuration Questions" Common Questions\} \p
\{\3\goto "How To Use Create LUN" How To Use Create LUN\} \p
\{\3\goto "How To Use Delete" How To Use Delete\}
\p\p
\{\7\goto "deleteluntop" Top Of Page\}\p
\keyword "Delete" \keyword "configuration" \keyword "raidutil utility" \keyword "LUN deletion" \keyword "exclusive access operations" \keyword "access, exclusive required" \keyword "stop I/Os"

\topic "How LUNs Are Formatted" \p\1
How LUNs Are Formatted \label "cfgformattop" 
\p\p
Fast Find -- \{\5\goto "cfgformat" Related Topics\}
\p\p\0
Whenever you create a logical unit (LUN) of more than 20 MB, the controller formats (writes zeros to) only the first and last 10 MB of the LUN. It then reports the format operation as completed. The LUN status becomes optimal. At this point, you can begin using the logical unit. You may write data to it, create file systems on it, and so on. \p\p
After the LUN is created, the controller may continue the format operation in \{\2\bring_popup "Background Formatting" background\}, depending on the RAID level of the logical unit: \p\p
\{\1 o \0\} If the LUN is a \{\2\bring_popup "RAID 0" RAID 0\} logical unit, data is written to the unformatted portion of the LUN normally. The controller needs to perform no further actions to format the logical unit. The controller performs no further background formatting. \p\p
\{\1 o \0\} If the LUN is a \{\2\bring_popup "RAID 1" RAID 1\} logical unit, the controller formats the remaining portion of the logical unit in background. Stripe by stripe, the controller rewrites the contents of each mirrored pair so that the contents match. If it needs to write user data in the unformatted portion of the LUN, it writes the data normally (so that the contents of each mirrored pair is the same). \p\p
\{\1 o \0\} If the LUN is a \{\2\bring_popup "RAID 3" RAID 3\} or \{\2\bring_popup "RAID 5" RAID 5\} logical unit, the controller formats the remaining portion of the logical unit in background. One at a time, the controller rewrites the contents of each stripe so that the parity is correct in each stripe. If it needs to write user data in the unformatted portion of the LUN, it writes the data normally (so that the parity in each stripe is correct). \p\p
While the controller is formatting in background, there is a boundary in the LUN. Below the boundary, the mirroring or parity in the logical unit is correct. Above the boundary, the parity or mirroring is not correct. When you perform a \{\2\bring_popup "Parity Check/Repair" parity check\} on the LUN, only the portion of the LUN that is currently formatted (the section below the format boundary) is checked. \p\p
Background formatting is a form of reconstruction, and is affected by the current setting of the \{\2\bring_popup "Reconstruction Rate" reconstruction rate\} parameter. Completing the background format can take a long time (up to 8 hours, depending on the size of the LUN and on how much I/O activity is occurring). \p\p
A LUN being formatted in background has an Optimal status. There is no indication in the storage management software that the format is occurring. While background formatting is occurring, however, you can use the LUN normally. However, you can not perform any Modify LUN operation on the LUN. \p\p\1
Related Topics \label "cfgformat"\0\p
\{\3\goto "Configuration Questions" Common Questions\} \p
\{\3\goto "How To Use Create LUN" How To Use Create LUN\} \p\p
\{\7\goto "cfgformattop" Top Of Page\}\p
\keyword "configuration" \keyword "LUN creation"

\topic "Time It Takes To Create A LUN" \p\1
How Long Does It Take To Create/Format A LUN? \label "cfgtimetop" 
\p\p
Fast Find -- \{\5\goto "cfgtimert" Related Topics\}
\p\p\0
The time it takes to create a \{\2\bring_popup "Logical Unit" logical unit\} (LUN) depends on the \{\2\bring_popup "Capacity" capacity\} of the LUN you are creating. The larger the capacity, the more time it takes. However, you can use the LUN before it is completely formatted. The controller completes the format operation in background. \p\p
Whenever you create a logical unit (LUN) of more than 20 MB, the controller formats (writes zeros to) only the first and last 10 MB of the LUN. It then reports the format operation as completed. The LUN status becomes optimal. At this point, you can begin using the logical unit. You may write data to it, create file systems on it, and so on. \p\p
After the LUN is created, the controller may complete the format operation in \{\2\bring_popup "Background Formatting" background\}, depending on the RAID level of the logical unit: \p\p
\{\1 o \0\} If the LUN is a RAID 0 logical unit, data is written to the unformatted portion of the LUN normally. The controller performs no further background formatting. \p\p
\{\1 o \0\} If the LUN is a RAID 1, 3, or 5 logical unit, the controller formats the remaining portion of the logical unit in background. If it needs to write user data in the unformatted portion of the LUN, it writes the data normally (with mirroring or parity information). \p\p
A LUN being formatted in background has an Optimal status. There is no indication in the storage management software that the format is occurring. While background formatting is occurring, however, you can use the LUN normally. \p\p
While the LUNs are being actively formatted (that is, while the status is Formatting), the information in the Configuration main screen may be incorrect or missing. When the LUN status returns to \{\2\bring_popup "Optimal Mode" Optimal\}, all the screen information will be correct. For more information, select the Screen Information Is Incorrect Or Incomplete topic in the \{\5\goto "cfgtimert" Related Topics\} list below. 
\p\p\1
Related Topics \label "cfgtimert"\0\p
\{\3\goto "Configuration Questions" Common Questions\} \p
\{\3\goto "How LUNs Are Formatted" How LUNs Are Formatted\} \p
\{\3\goto "How To Use Create LUN" How To Use Create LUN\} \p
\{\3\goto "Screen Information Is Incorrect Or Incomplete" Screen Information Is Incorrect Or Incomplete\} \p\p
\{\7\goto "cfgtimetop" Top Of Page\}\p
\keyword "configuration" \keyword "LUN creation" \keyword "time" \keyword "delay"

\topic "How Many Hot Spare Drives Can I Configure?" \p\1
How Many Hot Spare Drives Can I Configure? \label "numhottop" 
\p\p
Fast Find -- \{\5\goto "numhotrt" Related Topics\}
\p\p\0
Each \{\2\bring_popup "RAID Module" RAID Module\} can support as many \{\2\bring_popup "Hot Spare" hot spare\} drives as there are \{\2\bring_popup "SCSI Channel" SCSI Channels\} (probably either 2 or 5, depending on the model of your RAID Module). You can select any drive from the \{\2\bring_popup "Unassigned Drive Group" unassigned\} drive group to be a hot spare. \p\p\4
CAUTION \0\p
\{\1 o \0\} Hot spares cannot replace drives with a larger capacity (that is, a 2 GB hot spare cannot replace a 4 GB failed drive). When you create a hot spare, the Configuration Application always selects the first available drive unless you specify otherwise. If your unassigned drive group contains drives with different capacities, this may not be a drive of largest capacity. Therefore, before you create a hot spare drive, use List/Locate Drives to record the capacities and location of the larger capacity drives in the unassigned drive group, and then specify one of those drives to ensure that the hot spare can cover for any failed drive in the RAID Module. \p\p
\{\1 o \0\} It is NOT recommended that you assign all your hot spares on the same drive channel. If the drive channel were to fail, these drives would be unable to cover for the other failed drives in the RAID Module.
\p\p\1
Related Topics \label"numhotrt"\0\p
\{\3\goto "Configuration Questions" Common Questions\} \p
\{\3\goto "How To Use Create Hot Spare" How To Use Create Hot Spare\}
\p\p
\{\7\goto "numhottop" Top Of Page\}\p
\keyword "hot spare" \keyword "drive group, hot spare" \keyword "configuration" \keyword "module configuration" \keyword "SCSI Channel" \keyword "adding hot spares" \keyword "drives, number of" \keyword "number of drives" \keyword "number of hot spares"

\topic "What Are The Different Flashing Patterns?" \p\1
What Are The Different Flashing Patterns? (List/Locate Drives) \label "flashtop" 
\p\p
Fast Find -- \{\5\goto "flashrt" Related Topics\} \0\p\p
When you select Configuration Application >> List/Locate Drives >> Locate >> Start for a particular \{\2\bring_popup "Drive Group" drive group\}, the drive \{\2\bring_popup "Activity Lights" activity lights\} (on RAID Modules with Series 3 controllers or earlier) or the drive \{\2\bring_popup "Fault Lights" fault lights\} (on RAID Modules with Series 4 controller) on the drives flash until you select Stop. Depending on the type, \{\2\bring_popup "RAID Level" RAID Level\}, and controller type of the selected drive group, the lights either flash sequentially or simultaneously: \p\p
\{\1 o \0\} On RAID Modules with Series 4 controllers, the drive fault lights always blink simultaneously, regardless of RAID level or drive group. \p\p
\{\1 o \0\} \{\2\bring_popup "Unassigned Drive Group" Unassigned\}, \{\2\bring_popup "Hot Spare" Hot Spare\}, or \{\2\bring_popup "RAID 0" RAID 0\} drive groups on Series 3 (or earlier) controllers -- The activity lights on each drive in the drive group flash sequentially one-at-a-time. \p\p
\{\1 o \0\} RAID 1, 3, & 5 drive groups on Series 3 (or earlier) controllers -- The activity lights on all drives in the drive group flash simultaneously. \p\p\1
IMPORTANT \0\p
\{\1 o \0\} If any of the drives in the selected drive group are not Optimal, then none of the drive activity/fault lights will flash. You will see an error message indicating that the operation cannot be performed because one of the drives in the drive group cannot be accessed. \p\p
\{\1 o \0\} If you have a controller version earlier than the Series 3, the drive activity lights do not flash for the unassigned drive group.
\p\p\1
Related Topics \label "flashrt"\0\p
\{\3\goto "Configuration Questions" Common Questions\} \p
\{\3\goto "How To Use List/Locate Drives" How To Use List/Locate Drives\}
\p\p
\{\7\goto "flashtop" Top Of Page\}\p
\keyword "flashing lights" \keyword "List/Locate Drives" \keyword "drives, locating" \keyword "finding drives" \keyword "lights"

\topic "What Can I Do While Creating LUNs?" \1\p
What Can I Do While LUN Create/Format Is Taking Place? \0\p\p
You can perform other Configuration tasks (such as creating logical units on another drive group) or select another application while the \{\2\bring_popup "Logical Unit" logical unit\} (LUN) is being created. However, you cannot select the \{\2\bring_popup "Configured Drive Group" drive group\} that is being created until the status changes to Optimal (although formatting may continue in \{\2\bring_popup "Background Formatting" background\}). \p\p\1
IMPORTANT \0\p
If you have deleted all the LUNs on a \{\2\bring_popup "RAID Module" RAID Module\} and are re-creating new LUNs, wait for LUN creation to finish on the first LUN/drive group before creating additional new drive groups to make sure the operation is completed successfully. 
\p\p\1
Related Topics\0\p
\{\3\goto "Configuration Questions" Common Questions\} \p
\{\3\goto "Screen Information Is Incorrect Or Incomplete" Screen Information Is Incorrect Or Incomplete\} \p \keyword "LUN creation" \keyword "configuration"

\topic "When To Change A Module's Configuration" \1\p
When Should I Change A RAID Module's Configuration? \0\p\p
Normally, when you receive the \{\2\bring_popup "RAID Module" RAID Module\}, there are default \{\2\bring_popup "Logical Unit" logical units\} (LUNs) and \{\2\bring_popup "Configured Drive Group" drive groups\} already configured. This default configuration may work for your environment. However, you may want to create a \{\2\bring_popup "Hot Spare" hot spare\}, or the logical units may not be set according to your needs (for example, the number of LUNs, \{\2\bring_popup "RAID Level" RAID Level\}, etc.). \p\p
Use Module Profile and the Configuration main screen to determine what your current configuration is and make changes as needed. Consult the "Installation and Support Guide" specific to your operating system for information on determining what changes to make.
\p\p\1
Related Topics\0\p
\{\3\goto "Configuration Questions" Common Questions\} \p
\{\3\goto "How To Use Module Profile" How To Use Module Profile\} \p
\keyword "module configuration" \keyword "configuration" \keyword "changing configuration" 

\topic "When To Use File >> Reset Configuration" \p\1
When Should I Use The Reset Configuration Option? \0\p\p
Hopefully never!\4 Use this option ONLY as a last resort\0 if your configuration is totally inaccessible or you want to start over completely. This option allows you to reset the \{\2\bring_popup "Configured Drive Group" drive groups\} and \{\2\bring_popup "Logical Unit" logical units\} on the \{\2\bring_popup "RAID Module" RAID Module\} back to a default configuration based on settings specified in the \{\2\bring_popup "Controller" controller\}.\p\p\4
CAUTION \0\p
You will lose ALL data on the selected RAID Module.
 \p\p\1
Related Topics\0\p
\{\3\goto "Configuration Questions" Common Questions\} \p
\{\3\goto "How To Use File >> Reset Configuration" How To Use File >> Reset Configuration\} \p
\keyword "configuration" \keyword "Reset Configuration" \keyword "File menu" \keyword "changing configuration" \keyword "using Reset Configuration"

\topic "Firmware/NVSRAM Questions" \p\1
Firmware/NVSRAM Questions \0\p\p
\{\3\subtopic "Upgrading Firmware To Only One Controller" Can I Download Firmware Files To Only One Controller?\}
\p\p
\{\3\subtopic "Was The Firmware Upgrade Successful?" How Will I Know If The Firmware Upgrade Was Successful?\}
\p\p
\{\3\subtopic "Firmware Version On A RAID Module's Controllers" What Controller Firmware Version Does A RAID Module's Controllers Have?\}
\p\p
\{\3\subtopic "What Can Be Done During Firmware Upgrade?" What Can I Do While Upgrading Firmware/NVSRAM Files?\}
\p\p
\{\3\subtopic "Files Needed For Firmware Upgrade" What Files Do I Need To Perform A Firmware/NVSRAM Upgrade?\}
\p\p
\{\3\subtopic "What Might Prevent A Firmware Upgrade?" What Restrictions Might Prevent A Firmware Upgrade?\}
\p\p\1
Related Topics\0\p
\{\3\goto "Common Question Topics" Common Questions\} \p
\{\3\goto "Firmware Concept" Firmware\} \p
\{\3\goto "How To Download A New NVSRAM File" How To Download A New NVSRAM File\} \p
\{\3\goto "How To Use Firmware Upgrade" How To Use Firmware Upgrade\} \p
\{\3\goto "NVSRAM Concept" NVSRAM\} \p
\{\3\goto "Firmware/NVSRAM Restrictions" Restrictions/Cautions\} \p
\{\3\goto "Firmware/NVSRAM Troubleshooting" Troubleshooting\} \p
\keyword "NVSRAM" \keyword "controller firmware" \keyword "firmware" \keyword "questions"

\topic "Upgrading Firmware To Only One Controller" \p\1
Can I Download Firmware Files To Only One Controller? \0\p\p
Yes. You have to use the \{\2\bring_popup "Offline Firmware Upgrade" Offline\} method (Maintenance/Tuning Application >> Firmware Upgrade) which requires that you stop all I/O. You will be able to select the \{\2\bring_popup "Controller" controller\} in addition to highlighting the version level you want to download.
\p\p
Remember that both controllers in a \{\2\bring_popup "Redundant Controller Pair" redundant\} pair must have the same version of controller firmware installed. Therefore, it is strongly recommended that you select both controllers to ensure they have compatible versions of firmware UNLESS you are replacing a failed controller that has an earlier firmware version than the original pair was using.
\p\p
For detailed steps on the firmware upgrade operation, select the How To Use Firmware Upgrade topic in the "Related Topics" list below.
\p\p\1
Related Topics\0\p\label "cqonecontrollerrt"
\{\3\goto "Firmware/NVSRAM Questions" Common Questions\} \p
\{\3\goto "Firmware Concept" Firmware\} \p
\{\3\goto "How To Use Firmware Upgrade" How To Use Firmware Upgrade\} \p
\keyword "single controller" \keyword "controller firmware" \keyword "firmware" \keyword "offline firmware upgrade" \keyword "Firmware Upgrade" \keyword "upgrading firmware" \keyword "stop I/Os" \keyword "access, exclusive required"

\topic "Was The Firmware Upgrade Successful?" \p\1
How Will I Know If The Firmware Upgrade Was Successful?
 \label "firmsuccesstop" 
\p\p
Fast Find -- \{\5\goto "cqsuccessrt" Related Topics\}
\p\p\0
After a firmware upgrade is completed, a summary report is displayed indicating whether or not the upgrade was successful.
\p\p\1
NOTE\0: For details on possible download results, select the Firmware Upgrade Results topic in the \{\5\goto "cqsuccessrt" Related Topics\} list below.
\p\p\1
Summary Report for files\0: lists the \{\2\bring_popup "Firmware" files\} used to upgrade the firmware. These are the files loaded in the Path line when you select compatible versions of firmware.
\p\p\1
RAID Module\0: Provides the identifier for a particular RAID Module.
\p\p\1
Download Status\0: Indicates whether the download process was completed successfully. You see either (1) "Successful" or (2) "Failed" with a reason why the upgrade was unsuccessful.
\p\p
If you see "Failed" for any module, you should fix the specified failure and start the download procedure again.
\p\p\1
Related Topics\0\label "cqsuccessrt"\p
\{\3\goto "Firmware/NVSRAM Questions" Common Questions\} \p
\{\3\goto "How To Use Firmware Upgrade" How To Use Firmware Upgrade\} \p
\{\3\goto "Firmware Upgrade Results" Firmware Upgrade Results\}
\p\p
\{\7\goto "firmsuccesstop" Top Of Page\}\p
\keyword "controller firmware" \keyword "firmware" \keyword "results" \keyword "failures" \keyword "download status" \keyword "upgrade statuses" \keyword "Firmware Upgrade" \keyword "view statuses"

\topic "Firmware Version On A RAID Module's Controllers" \p\1
What Controller Firmware Version Does A RAID Module's Controllers Have? \0\p\p
Module Profile shows what version of \{\2\bring_popup "Firmware" firmware\} is installed on the controllers in a selected \{\2\bring_popup "RAID Module" RAID Module\}. Select a single RAID Module. Then, select Module Profile >> Controllers. The firmware versions appear under the \{\2\bring_popup "Boot Level" Boot\} Level, \{\2\bring_popup "Firmware Level" Firmware\} Level, and \{\2\bring_popup "Fibre Channel Level" Fibre Channel\} Level columns. \p\p
Note that for firmware levels of 3.0 or greater, the fibre channel firmware is included in the Firmware Level.
\p\p\1
Related Topics\0\label "cqversionrt"\p
\{\3\goto "Firmware/NVSRAM Questions" Common Questions\} \p
\{\3\goto "Firmware Concept" Firmware\} \p
\{\3\goto "How To Use Module Profile" How To Use Module Profile\} \p
\keyword "controller firmware" \keyword "firmware" \keyword "version, controller firmware" \keyword "fibre channel" \keyword "Module Profile" \keyword "bootware level" \keyword "appware level" \keyword "fibre channel firmware level"

\topic "What Can Be Done During Firmware Upgrade?" \p\1
What Can I Do While Upgrading Firmware/NVSRAM Files? \0\p\p
You cannot do anything besides monitor its progress. You have several opportunities to select Cancel and exit Firmware Upgrade without performing any procedure. However, once you select OK at the "Firmware upgrade is about to start" prompt, you cannot exit the Maintenance/Tuning Application until the upgrade process is complete. This is true both for downloading a new \{\2\bring_popup "NVSRAM File" NVSRAM\} file as well as for upgrading controller \{\2\bring_popup "Firmware" firmware\} files.
\p\p\1
Related Topics\0\label "cqdonert"\p
\{\3\goto "Firmware/NVSRAM Questions" Common Questions\} \p
\{\3\goto "Viewing Firmware Upgrade Progress" Viewing A Firmware Upgrade's Progress\} \p
\keyword "controller firmware" \keyword "firmware" \keyword "NVSRAM" \keyword "view progress" \keyword "progress" \keyword "Firmware Upgrade"

\topic "Files Needed For Firmware Upgrade" \p\1
What Files Do I Need To Perform A Firmware/NVSRAM Upgrade? \label "whatfiletop"
\p\p
Fast Find -- \{\5\goto "nvfile" NVSRAM Files\} | \{\5\goto "firmfilesrt" Related Topics\}
\p\p\0
For detailed information on the Firmware Upgrade procedure, select the How To Download A New NVSRAM File or How To Use Firmware Upgrade topics in the \{\5\goto "firmfilesrt" Related Topics\} list below.
\p\p\1
Controller Firmware Files \p\p\0
When you receive new controller \{\2\bring_popup "Firmware" firmware\} files, copy them to the default subdirectory in the host system's installation directory BEFORE attempting to perform the upgrade procedure. (See the "Installation and Support Guide" specific to your operating system for installation directory information.)
\p\p
With any new controller firmware upgrade, you should receive one to three firmware files: (\{\2\bring_popup "Firmware Level"appware\}, \{\2\bring_popup "Boot Level" bootware\}, and \{\2\bring_popup "Fibre Channel Level" fibreware\}) and the \{\2\bring_popup "fwcompat.def File" fwcompat.def\} file. This last file allows the software to compare the firmware files for compatibility during the upgrade process, providing you with a list of compatible files to select for downloading. Also, the software searches the default \{\2\bring_popup "Subdirectory, Firmware" subdirectory\} in the \{\2\bring_popup "Installation Directory" installation\} directory for these files. \p\p
Note that for firmware levels of 3.0 or greater, the fibreware firmware is included in the Firmware Level.
\p\p\1
IMPORTANT \0\p
If you do not copy the fwcompat.def file to the host system, the software is unable to check the files for compatibility. Although you can still enter firmware filenames, you do NOT have the protection that this compatibility check provides.
\p\p\1
NVSRAM File \label "nvfile"\0\p\p
The \{\2\bring_popup "NVSRAM File" NVSRAM\} file specifies certain default settings for the controller and comes from your Customer Services Representative. You must copy the file to your host system BEFORE downloading. 
\p\p
In most cases, you will have to download a new NVSRAM file BEFORE upgrading controller firmware, especially if you are upgrading from one major firmware release to another (for example, from 2.03 to 2.04). You can use the Firmware Upgrade option to download an NVSRAM file separately, then run\1 nvutil -vf\0 from the command line to check all \{\2\bring_popup "Controller" controllers\} to ensure that certain NVSRAM settings are set up correctly for the storage management software. You then need to select Firmware Upgrade again to upgrade the controller firmware.
\p\p\1
IMPORTANT \0\p
If you do not download the new NVSRAM file (if required), certain features of this software and in the controller may not work. Also, if you have RAID Modules with a pair of \{\2\bring_popup "Redundant Controller Pair" redundant\} controllers, it is recommended that you download to both controllers at the same time to ensure that both controllers have the same level of NVSRAM and firmware files.
\p\p\1
Related Topics\0 \label "firmfilesrt"\p
\{\3\goto "Firmware/NVSRAM Questions" Common Questions\} \p
\{\3\goto "How To Download A New NVSRAM File" How To Download A New NVSRAM File\} \p
\{\3\goto "How To Use Firmware Upgrade" How To Use Firmware Upgrade\}
\p\p
\{\7\goto "whatfiletop" Top Of Page\}\p
\keyword "nvutil utility" \keyword "NVSRAM" \keyword "controller firmware" \keyword "firmware" \keyword "fibre channel" \keyword "fwcompat.def file" \keyword "file selection" \keyword "selecting files" \keyword "Firmware Upgrade"

\topic "What Might Prevent A Firmware Upgrade?" \p\1
What Restrictions Might Prevent A Firmware Upgrade? \label "restrictfirmtop" 
\p\p
Fast Find -- \{\5\goto "restrictfirmrt" Related Topics\}
\p\p\0
After you select the \{\2\bring_popup "Online Firmware Upgrade" Online\} or \{\2\bring_popup "Offline Firmware Upgrade" Offline\} upgrade option, the software determines whether the selected \{\2\bring_popup "RAID Module" RAID Module\} is ready for the type of upgrade you selected. It is possible that the software may find restrictions on performing the upgrade.
\p\p
For example: \p\p
\{\1 o \0\} You cannot perform an offline upgrade on a module that is receiving I/O.
\p\p
\{\1 o \0\} You can only perform an online upgrade on a module that has two functioning Series 3 or Series 4 controllers with the \{\2\bring_popup "RDAC Driver" driver\} installed for \{\2\bring_popup "Redundant Controller Pair" redundant\} controller support. For example, the online option is grayed out if the module has \{\2\bring_popup "Independent Controller Configuration" independent\} controllers. Also, you cannot perform an Online upgrade unless all the \{\2\bring_popup "Logical Unit" LUNs\} in the module are \{\2\bring_popup "Optimal Mode" Optimal\}.
\p\p
If such restrictions are found, you see an Upgrade Restriction box explaining the problem.
\p\p
\{\1 o \0\} If you selected a single RAID Module, you receive an Upgrade Restriction message indicating what problem you should fix before attempting to upgrade the firmware again for that module.
\p\p
\{\1 o \0\} If you selected All RAID Modules, the firmware upgrade continues for each possible module. At the end of the firmware upgrade process, you see a list of which modules were upgraded and which were not. For each module that was not successfully upgraded, you should see a reason why the upgrade did not occur.
\p\p\1
Related Topics\0\label "restrictfirmrt"\p
\{\3\goto "Firmware/NVSRAM Questions" Common Questions\} \p
\{\3\goto "Firmware Upgrade Results" Firmware Upgrade Results\}
\p\p
\{\7\goto "restrictfirmtop" Top Of Page\}\p
\keyword "Firmware Upgrade" \keyword "controller firmware" \keyword "firmware" \keyword "RDAC" \keyword "restrictions" \keyword "upgrade restrictions"

\topic "Host Connection Questions" \p\1
Host Connection Questions \0\p\p
\{\3\subtopic "Special Considerations For Using The Independent Controller Configuration" Are There Special Considerations For Using The Independent Controller Configuration?\}
\p\p
\{\3\subtopic "Special Considerations For Using The Networked Version" Are There Special Considerations For Using The Networked Version?\}
\p\p\1
Related Topics\0\p
\{\3\goto "Common Question Topics" Common Questions\} \p
\{\3\goto "Host Interface Connections Concept" Host Interface Connections\} \p
\{\3\goto "Host-RAID Module Configuration Types Supported Concept" Host-RAID Module Configuration Types Supported\} \p
\keyword "questions" \keyword "host interface" \keyword "device connection"

\topic "Special Considerations For Using The Independent Controller Configuration" \p\1
Are There Special Considerations For Using The Independent Controller Configuration? \label "indepctrltop" 
\p\p
Fast Find -- \{\5\goto "indepctrlrt" Related Topics\} \p\p\0
Yes. If you are using the \{\2\bring_popup "Independent Controller Configuration" independent\} controller configuration, each \{\2\bring_popup "Controller" controller\} in the \{\2\bring_popup "RAID Module" RAID Module\} is controlled by only one host machine. This means that only the software on the host machine connected to the controller can access the \{\2\bring_popup "Configured Drive Group" drive groups\}/LUNs it owns. \p\p
While the storage management software on either host reports the other controller and its drive groups/\{\2\bring_popup "Logical Unit"LUNs\} as \{\2\bring_popup "Inaccessible" Inaccessible\}, the software cannot perform most operations on the alternate controller's drive groups/LUNs. \p\p\1
Unique Considerations\0 -- The following items are unique to this configuration: \p\p
\{\1 o \0\} Both host machines MUST have the same operating system (for example, both UNIX or both Windows NT) and the same storage management software versions installed. \p\p
\{\1 o \0\} It is recommended that both host machines have the same LUNs-per-host adapter capacity (that is, either both are limited to eight LUNs or both can have 16-32 LUNs). This is important so that each controller can handle all configured drive groups/LUNs on the alternate controller, should it be necessary to change controller assignments. \p\p
\{\1 o \0\} Requires a special setting in Select Module main screen (the "Indep. Cntrls?" column says Yes). \p\p
\{\1 o \0\} The controllers in the RAID Module do not have \{\2\bring_popup "RDAC Driver" RDAC\} failover protection. \p\p
\{\1 o \0\} Because it is possible to open a Configuration Application from both hosts, be sure that you have only ONE configuration session open at a time (from only one host) when creating or deleting LUNs or the operation will fail on one of the hosts. \p\p
\{\1 o \0\} Each controller can see all unassigned drives, and hot spares are always available to LUNs of either controller. \p\p
\{\1 o \0\} Recovery Guru/Health Check (Recovery Application) detects \{\2\bring_popup "I/O Connection" I/O connection\} related failures ONLY for the controller that is connected to the host machine running the storage management software. While you might see "Failure on Other Host -- Independent Controllers" as a failure type, you need to run Recovery Guru again from the other host to fully diagnose the problem and obtain the correct recovery procedure. \p\p\1
NOTE\0: The Networked version of the storage management software always sees both controllers in a dual-controller RAID Module regardless of the configuration used. However, the Networked version is able to tell if the RAID Module it is connected to has an independent controller configuration ONLY if you set the option (with Select Module >> Edit). \p\p\1
Related Topics \label "indepctrlrt"\0\p
\{\3\goto "Special Considerations For Using The Networked Version" Are There Special Considerations For Using The Networked Version?\} \p
\{\3\goto "Host Connection Questions" Common Questions\} \p
\{\3\goto "How To Edit Module Information" How To Edit Module Information\}
\p\p
\{\7\goto "indepctrltop" Top Of Page\}\p
\keyword "RDAC" \keyword "independent controller configuration" \keyword "networked version" \keyword "device connection" \keyword "host interface" \keyword "exceptions, independent controller configuration" \keyword "Inaccessible" \keyword "Select Module" \keyword "edit module information" \keyword "indicating host-module configuration"

\topic "Special Considerations For Using The Networked Version" \p\1
Are There Special Considerations For Using The Networked Version? \label "networktop" 
\p\p
Fast Find -- \{\5\goto "networkcfg" Host Configurations\} | \{\5\goto "networkrt" Related Topics\}
\p\p\0
Yes. You should be aware of the following restrictions: \p\p\1
No RDAC Protection \0\p\p
If you have installed the Networked version of this software, you do NOT have \{\2\bring_popup "RDAC Driver" RDAC\} protection over the network connection. This means that there is no way to check for problems along the connection from the host to the \{\2\bring_popup "RAID Module" RAID Module\}. Therefore, you must use extreme caution when you perform tasks that involve a transfer of LUN \{\2\bring_popup "LUN Assignment" ownership\} between \{\2\bring_popup "Redundant Controller Pair" redundant\} controllers to avoid failure of the I/O or the operation. \p\p
It is possible for the RAID Modules to have failover protection installed on the host connected to the modules through the \{\2\bring_popup "I/O Connection" I/O connection\}. Consult the "Installation and Support Guide" specific to the networked version to see whether or not there is an RDAC Driver available for your host machine's operating system. \p\p\1
Host-RAID Module Configurations \label "networkcfg"\p\p\0
If you are using the Networked version of the storage management software, the following restrictions apply to any of the host-RAID Module configurations: \{\2\bring_popup "Single-Host Configuration" single-host\}, \{\2\bring_popup "Multi-Host Configuration" multi-host\}, or \{\2\bring_popup "Independent Controller Configuration" independent\} controllers. \p\p
\{\1 o \0\} This software always sees both controllers in a dual-controller \{\2\bring_popup "RAID Module" RAID Module\} regardless of which configuration you have. However, the Networked version is able to tell if the RAID Module it is connected to has an independent controller configuration only if independent controllers were defined using the Select Module >> Edit option. \p\p
\{\1 o \0\} This software does NOT provide I/O connection failure detection or recovery. However, any problems with a network connection to the controllers or a problem with the controllers themselves are diagnosed by Recovery Guru/Health Check, which provides a step-by-step procedure for correcting these problems. \p\p
\{\1 o \0\} This software does NOT recognize any exclusive access operations that may be performed by other software installed on the host machine (not even another storage management package). Use caution before starting certain operations that need exclusive access. Without it, filesystems are not detected and multiple operations could be launched without logical units being protected. Furthermore, make sure you open only ONE configuration session at a time when creating or deleting \{\2\bring_popup "Logical Unit" LUNs\}. Although it is possible to open a Configuration Application from any networked station, multiple configuration operations will fail for all but ONE station. \p\p\4
CAUTION \0\p
\{\2\bring_popup "Configured Drive Group"Drive groups\}/LUNs and their data could be lost if more than one "destructive" operation is launched. No other operations should be attempted on the same drive group/LUN if one of these operations is still being completed. Operations requiring exclusive access to the LUNs are: \p\p\1
\{\1 o \0\} Configuration Application\0 -- Delete for LUNs and File >> Reset Configuration \p\p\1
\{\1 o \0\} Recovery Application\0 -- Formatting a LUN with Options >> Manual Recovery >> Logical Units \p\p\1
\{\1 o \0\} Maintenance/Tuning Application\0 -- Firmware Upgrade >> Offline method
\p\p\1
Related Topics \label "networkrt"\0\p
\{\3\goto "Special Considerations For Using The Independent Controller Configuration" Are There Special Considerations For Using The Independent Controller Configuration?\} \p
\{\3\goto "Host Connection Questions" Common Questions\}
\p\p
\{\7\goto "networktop" Top Of Page\}\p
\keyword "RDAC" \keyword "independent controller configuration" \keyword "networked version" \keyword "device connection" \keyword "host interface" \keyword "multi-host configuration" \keyword "single-host configuration" \keyword "exclusive access operations" \keyword "operations requiring exclusive access"

\topic "LUN Assignment Questions" \p\1
LUN Assignment Questions \0\p\p
\{\3\goto "Considerations For Two Active Controllers" Any Special Considerations For A RAID Module With Two Active Controllers?\}
\p\p
\{\3\subtopic "View LUN Assignments For All RAID Modules" Can I Quickly View The LUN Assignments For All RAID Modules?\}
\p\p
\{\3\subtopic "Why Wouldn't A Controller Own LUNs?" Why Wouldn't A Controller Own LUNs?\}
\p\p\1
Related Topics\0\p
\{\3\goto "Common Question Topics" Common Questions\} \p
\{\3\goto "LUN Assignment Concept" LUN Assignment\} \p
\{\3\goto "LUN Assignment Restrictions" Restrictions/Cautions\} \p
\{\3\goto "LUNs Are Marked As Inaccessible" Troubleshooting\} \p
\keyword "LUN assignment" \keyword "questions" \keyword "controller, LUNs owned"

\topic "View LUN Assignments For All RAID Modules" \p\1
Can I Quickly View The LUN Assignments For All RAID Modules? \0\p\p
Yes. Select the Maintenance/Tuning Application >> All RAID Modules >> LUN Balancing to view the LUN \{\2\bring_popup "LUN Assignment" Assignments\} for all your \{\2\bring_popup "RAID Module" RAID Modules\}. When finished viewing, select Cancel to close this option without changing any LUN assignments.
\p\p\1
Related Topics\0\p
\{\3\goto "LUN Assignment Questions" Common Questions\} \p
\{\3\goto "How To Use LUN Balancing" How To Use LUN Balancing\} \p
\keyword "view LUN assignment" \keyword "LUN assignment" \keyword "controller, LUNs owned" \keyword "All modules" \keyword "LUN Balancing"

\topic "Why Wouldn't A Controller Own LUNs?" \p\1
Why Wouldn't A Controller Own LUNs? \label "ctrlowntop" 
\p\p
Fast Find -- \{\5\goto "ctrlownrt" Related Topics\}
\p\p\0
When you are in All RAID Modules >> LUN Balancing and you see that no \{\2\bring_popup "Logical Unit" LUNs\} are assigned to a controller, the following reasons could apply: \p\p
\{\1 o \0\} The controller status is None. This usually means that the \{\2\bring_popup "RAID Module" RAID Module\} has only one controller. It is less likely that you would see \{\2\bring_popup "No Controller Mode" No Controller\} as a status. \p\p
\{\1 o \0\} The controller status is \{\2\bring_popup "Passive Controller Mode" Passive\}. In an \{\2\bring_popup "Active/Passive Controller Pair" active/passive\} controller pair, only the active controller owns LUNs. \p\p
\{\1 o \0\} The controller status is \{\2\bring_popup "Active Controller Mode" Active\}; however, it has NOT been assigned any LUNs. \p\p\1
NOTE\0: In an \{\2\bring_popup "Active/Active Controller Pair" active/active\} controller pair, both controllers should own LUNs for best results. \p\p
\{\1 o \0\} The controller status is \{\2\bring_popup "Inaccessible" Inaccessible\}. This means the RAID Module has an \{\2\bring_popup "Independent Controller Configuration" independent\} controller configuration. You must access the Inaccessible controller and its \{\2\bring_popup "Configured Drive Group" drive groups\}/LUNs from the host that is connected to it. \p\p\1
NOTE\0: With independent controllers, each controller owns specific drive groups/LUNs. The storage management software on both hosts has knowledge of the alternate controller and displays all configured drive groups/LUNs. However, the software displays an Inaccessible status for the LUNs owned by the alternate controller.
\p\p\1
Related Topics \label "ctrlownrt"\0\p
\{\3\goto "LUN Assignment Questions" Common Questions\}
\p\p
\{\7\goto "ctrlowntop" Top Of Page\} \p
\keyword "independent controller configuration" \keyword "controller, LUNs owned" \keyword "LUN assignment" \keyword "Inaccessible" \keyword "LUN Balancing"

\topic "Manual Recovery Questions" \p\1
Manual Recovery Questions \0\p\p
\{\3\subtopic "When To Use Revive Drive" When Can I Revive A Drive?\}
\p\p
\{\3\subtopic "When To Use Options >> Manual Recovery" When Should I Use The Manual Recovery Options?\}
\p\p\1
Related Topics\0\p
\{\3\goto "Common Question Topics" Common Questions\} \p
\{\3\goto "How To Use Options >> Manual Recovery" How To Use Options >> Manual Recovery\} \p
\{\3\goto "Manual Recovery Restrictions" Restrictions/Cautions\} \p
\keyword "questions" \keyword "Options menu" \keyword "Manual Recovery options"

\topic "When To Use Revive Drive" \p\1
When Can I Revive A Drive? \label "revivetop"
\p\p
Fast Find -- \{\5\goto "revivert" Related Topics\}
\p\p\4
CAUTION \0\p
Do NOT attempt to use Options >> Manual Recovery >> Drives >> Revive when the \{\2\bring_popup "Controller" controller\} has marked the drive as Failed. Instead, select Recovery Guru/Health Check and follow the instructions provided in Show Procedures.
\p\p\1
When To Use The Revive Option
\p\p\0
You may be able to recover from certain types of drive failures using the Revive procedure if:
\p\p
\{\1 o \0\} You are instructed to by Recovery Guru/Health Check \p\p
\{\1 o \0\} You accidentally failed an \{\2\bring_popup "Optimal Mode" Optimal\} drive in an Optimal \{\2\bring_popup "RAID 0" RAID 0\} LUN (using Options >> Manual Recovery >> Drives >> Fail) and have NOT performed any writes to the LUN in the meantime. In this case, you should use the Revive option. The LUN should return to Optimal and the data is not affected. \p\p
\{\1 o \0\} You accidentally removed or failed an Optimal drive in an Optimal RAID 0 LUN and data was being written to it at the time. The LUN status changes to \{\2\bring_popup "Dead Mode" Dead\}, and the operating system sends you messages indicating the failure. In this case, reinserting and reviving the drive may allow you to recover some of your data. Any files that were not being written when you removed or failed the drive are probably OK. \p\p
\{\1 o \0\} You accidentally failed an \{\2\bring_popup "Optimal Mode" Optimal\} drive in an Optimal RAID 1, 3, or 5 LUN (using Options >> Manual Recovery >> Drives >> Fail) and have NOT performed any writes to the LUN in the meantime. In this case, you should use the Revive option. The LUN should return to Optimal and the data is not affected. However, if you are NOT sure whether any writes have occurred, use the Reconstruct option instead of Revive. \p\p
\{\1 o \0\} You accidentally removed an Optimal drive in a \{\2\bring_popup "Degraded Mode" Degraded\} RAID 1, 3, or 5 LUN and you were writing to it at the time. The LUN status changes to Dead, and the operating system sends you messages indicating the failure. In this case, reviving the drive may allow you to recover some of your data. Any files that were not being written when you removed or failed the drive are probably OK. After the LUN returns to Degraded, you should use Recovery Guru/Health Check >> Show Procedure to restore the LUN to Optimal. \p\p\1
You do NOT need to use the Revive option if: \p\p\0
\{\1 o \0\} You accidentally remove an Optimal drive from an Optimal LUN and the LUN status remains optimal (that is, you were not writing to the LUN at the time you removed it). The drive will automatically be returned to an optimal status after you reinsert it. \p\p
\{\1 o \0\} You accidentally remove an Optimal drive from an Optimal RAID 1, 3, or 5 logical unit and the LUN status changes to Degraded (that is, you were writing to the LUN at the time you removed it). The drive will automatically be reconstructed after you reinsert it.
\p\p\1
Related Topics\0\label "revivert"\p
\{\3\goto "Manual Recovery Questions" Common Questions\} \p
\{\3\goto "How To Use Manual Recovery >> Drives" How To Use Manual Recovery >> Drives\}
\p\p
\{\7\goto "revivetop" Top Of Page\} \p
\keyword "using Revive drive" \keyword "Revive drive" \keyword "drive recovery" \keyword "Manual Recovery options" \keyword "when NOT to revive drives"

\topic "When To Use Options >> Manual Recovery" \p\1
When Should I Use The Manual Recovery Options? \label "manusetop" 
\p\p
Fast Find -- \{\5\goto "ctrlmanuse" Controllers\} | \{\5\goto "drvmanuse" Drives\} | \{\5\goto "lunmanuse" LUNs\} | \{\5\goto "manusert" Related Topics\}
\p\p\4
CAUTION \0\p
Always select Recovery Guru/Health Check BEFORE attempting any manual recovery procedure to ensure the problem is correctly diagnosed. Incorrectly performing a procedure or performing the wrong procedure could cause equipment damage or data loss. Recovery Guru provides step-by-step procedures to make sure that you are correcting the right problem and directs you when to use the manual recovery options.
\p\p\1
Controller Pairs \label "ctrlmanuse"\p\p
\{\1 o \0\} Place Offline \0 -- Place a controller \{\2\bring_popup "Offline Controller Mode" Offline\} to stop a selected controller from accepting I/O requests. If the RAID Module has RDAC failover support, its LUNs are reassigned to the other controller and it stops accepting any I/O. If the RAID Module does not have RDAC failover support, the LUNs are not reassigned, and can no longer be used until the controller is placed back online.
\p\p\1
\{\1 o \0\} Place Online \0 -- Place a controller Online to return it to ready-for-operating condition (\{\2\bring_popup "Optimal Mode"Optimal\} status). For example, if you have placed a controller offline to replace it, you need to place it online before it can function again.
\p\p\1
Drives \label "drvmanuse"\p\p
\{\1 o \0\} Fail \0 -- Fail a drive if you want to replace it before the controller has marked it as failed. It is best to wait and let the controller fail a drive, or for Recovery Guru/Health Check >> Show Procedure to indicate this action is necessary.
\p\p\1
\{\1 o \0\} Reconstruct \0 -- Reconstruct a drive if \{\2\bring_popup "Reconstruction" reconstruction\} doesn't begin automatically. Normally, drive reconstruction begins automatically once you replace a failed drive.
\p\p\1
\{\1 o \0\} Revive \0 -- Revive a drive to recover if you remove a wrong drive that was Optimal. Never use this procedure if the controller has marked the drive as failed. For more information on when to use this option, select the When Can I Revive A Drive? topic in the \{\5\goto "manusert" Related Topics\} list below.
\p\p\1
LUNs \label "lunmanuse"\p\p
\{\1 o \0\} Format \0 -- Format a LUN with a \{\2\bring_popup "Dead Mode" Dead\} status manually AFTER you have replaced all the failed drives in the \{\2\bring_popup "Configured Drive Group" drive group\}. Remember that the format option destroys data on ALL the LUNs in the drive group. You must use a backup copy to restore data after the LUN returns to Optimal.
\p\p\1
\{\1 o \0\} Revive \0 -- Revive a LUN only when Recovery Guru/Health Check >> Show Procedure instructs you to do so. Remember in the case of a Dead LUN, you see all the LUNs in the affected drive group on one line; therefore, the revive procedure affects every LUN in the drive group.
\p\p\1
Related Topics\0\label "manusert"\p
\{\3\goto "Manual Recovery Questions" Common Questions\} \p
\{\3\goto "How To Use Options >> Manual Recovery" How To Use Options >> Manual Recovery\} \p
\{\3\goto "When To Use Revive Drive" When Can I Revive A Drive?\}
\p\p
\{\7\goto "manusetop" Top Of Page\}\p
\keyword "Manual Recovery options" \keyword "using Manual Recovery options" \keyword "Options menu" \keyword "data recovery" \keyword "controller recovery" \keyword "drive recovery" \keyword "LUN recovery" \keyword "Place Offline" \keyword "Place Online" \keyword "Format LUN" \keyword "Revive LUN" \keyword "Revive drive" \keyword "Fail drive" \keyword "reconstruction" \keyword "manual reconstruction" \keyword "RDAC"

\topic "Message Log Questions" \p\1
Message Log Questions \0\p\p
\{\3\subtopic "Changing The Message Log File Displayed" Can I Change The Log File That Message Log Displays?\}
\p\p
\{\3\subtopic "When To Change Message Log's Settings" When Should I Change Message Log's Settings?\}
\p\p
\{\3\subtopic "When To Refresh Message Log" When Should I Refresh Message Log?\}
\p\p
\{\3\subtopic "When To Use Message Log" When Should I Use Message Log?\}
\p\p
\{\3\subtopic "Log Settings Apply To Which Raid Modules?" Will Changing Log Settings Apply To Each Selected RAID Module Or To All RAID Modules?\}
\p\p\1
Related Topics\0\p
\{\3\goto "Common Question Topics" Common Questions\} \p
\{\3\goto "How To Use Message Log" How To Use Message Log\} \p
\{\3\goto "Message Log Restrictions" Restrictions/Cautions\} \p
\{\3\goto "Message Log Troubleshooting" Troubleshooting\} \p
\keyword "Message Log" \keyword "questions"

\topic "Changing The Message Log File Displayed" \p\1
Can I Change The Log File That Message Log Displays? \0\p\p
Yes. Message Log displays the \{\2\bring_popup "Log File" log\} file designated as default (set in Options >> Log Settings) each time you start the Status Application. \p\p
You have two options for changing this display: \p\p
\{\1 o \0\} Change the default log file. From the top menu, select Options >> Log Settings and specify a new log file (including the full path name). \p\p
\{\1 o \0\} Change the display temporarily to view a selected log file. From the top menu select File >> Open Log, and select the file you want to view. This log continues to be displayed until you open another log file or exit the Status Application.
\p\p\1
Related Topics\0\p
\{\3\goto "Message Log Questions" Common Questions\} \p
\{\3\goto "How To Change Message Log's Settings" How To Change Message Log's Settings\} \p
\{\3\goto "How To Open A Log File" How To Open An Existing Log File\} \p
\keyword "changing Message Log file" \keyword "log file" \keyword "Message Log" \keyword "default log"

\topic "When To Change Message Log's Settings" \p\1
When Should I Change Message Log's Settings? \label "defaultlogtop"\p\p
Fast Find -- \{\5\goto "logsize" Log Size\} | \{\5\goto "checkinterval" Checking Interval\} | \{\5\goto "defaultlogrt" Related Topics\}
\p\p\1
The Default Log File \label "defaultlog"\p\p
When To Change It\0 -- \p\p
\{\1 o \0\} If you want the data logged to a different file. \p\p
\{\1 o \0\} To control the size of the \{\2\bring_popup "Log File" log\} file and provide better performance of Message Log's activities. The larger the log becomes, the longer it takes to display Message Log when you select or refresh it. \p\p\1
What Happens\0 -- The software automatically writes future message log data to the file named here. The default path is the \{\2\bring_popup "Installation Directory" installation\} directory and the filename is rmlog.log. When you select Message Log, this file is displayed for All RAID Modules. \p\p\1
Did You Know?\0 -- Changing the default log does NOT automatically change which log is displayed in Message Log until you exit the Status Application. To change the log displayed, from the top menu select File >> Open Log. \p\p\1
Changing The Maximum Message Log Size \label "logsize"\p\p
When To Change It\0 -- Increase this \{\2\bring_popup "Maximum Message Log Size" value\} if you want your maximum message log size to be larger than the default setting of 40K. \p\p\1
What Happens\0 -- The Maximum Message Log Size message is automatically displayed whenever the \{\2\bring_popup "Log File" default\} log file exceeds the value set here. When this happens, the default message log is saved to a new file (rmlog.<hostname>_00X) and the default log file is cleared except for an entry indicating that the contents of the original log have been saved to the new filename. \p\p\1
IMPORTANT \0\p
As the size of the message log increases, you may notice delays when you select Message Log or Options >> Refresh All. Therefore, it is recommended that you use the default value. \p\p\1
Did You Know?\0 -- \p\p
\{\1 o \0\} Although you cannot disable this notification, you can set the size to the maximum value (1000K) to reduce the frequency that the maximum log size is exceeded. \p\p
\{\1 o \0\} The minimum value for this parameter is 1 K. \p\p\label "checkinterval"\1
Changing The "Check RAID Modules Every X Minutes" Interval \p\p
When To Change It\0 -- \1\p\p
\{\1 o \0\} Increase\0 this \{\2\bring_popup "Checking Interval" value\} if you do not want the background monitor to check the RAID Modules as frequently. \p\p\1
\{\1 o \0\} Decrease\0 this value if you want the background monitor to check the RAID Modules more often. \p\p\4
CAUTION \0\p
Setting this value too small could cause the check to affect system I/O performance. Setting this value too large could delay notification of serious problems. \p\p\1
What Happens\0 -- The software automatically polls all RAID Modules and checks for problems/events at the specified interval (default is 5 minutes). If any problems or events are detected, the information is written to the \{\2\bring_popup "Log File" default\} log file, which you can view using Message Log. The log entry shows the date and time that the background monitor detected the problem/event. \p\p\1
Did You Know?\0 - Depending on the length of the checking interval, it is possible to use Recovery Guru/Health Check (Recovery Application) to find and correct problems before the background monitor detects them. In cases where you have corrected problems BEFORE the background monitor detects them, these events are not detected or written to the Message Log.
\p\p\1
Related Topics \label "defaultlogrt"\0\p
\{\3\goto "Message Log Questions" Common Questions\} \p
\{\3\goto "How To Change Message Log's Settings" How To Change Message Log's Settings\}
\p\p
\{\7\goto "defaultlogtop" Top Of Page\} \p
\keyword "settings" \keyword "Message Log" \keyword "default log" \keyword "log file" \keyword "maximum log size" \keyword "size, maximum log" \keyword "log size" \keyword "changing settings" \keyword "checking interval" \keyword "interval" \keyword "values" \keyword "file selection" \keyword "changing Message Log file"

\topic "When To Refresh Message Log" \p\1
When Should I Refresh Message Log? \p\p
What Happens \0\p\p
Message Log is updated with any new messages for events that have occurred since you opened the current log. \p\p
All message types are displayed again (the default setting). For example, if you use List Type to select only hardware messages, but then select Refresh All, all message types are displayed. \p\p\1
When To Use \0\p\p
You may want to use this option if you stay in Message Log any longer than your "Check RAID Modules Every X Minutes" \{\2\bring_popup "Checking Interval" interval\}.
\p\p\1
Related Topics\0\p
\{\3\goto "Message Log Questions" Common Questions\} \p
\{\3\goto "How To Refresh Message Log" How To Refresh Message Log\} \p
\keyword "Message Log" \keyword "refresh" \keyword "using Refresh (Message Log)" \keyword "log file" \keyword "update log" \keyword "screen update"

\topic "When To Use Message Log" \p\1
When Should I Use Message Log? \label "whenmlogtop"\p\p
Fast Find -- \{\5\goto "whenmlogrt" Related Topics\}
\p\p\1
When To Use \0\p\p
Use Message Log (Status Application) to view specific information for a \{\2\bring_popup "RAID Module" RAID Module\}. Use it: \p\p
\{\1 o \0\} When you have been notified that a component failure has occurred. \p\p
\{\1 o \0\} If either you or Automatic Parity Check/Repair has run a parity \{\2\bring_popup "Parity Check/Repair" check/repair\}. \p\p
\{\1 o \0\} Whenever you are aware of a general status change. \p\p
This message can help you identify what type of event has occurred, when the event was detected, what RAID Module and \{\2\bring_popup "Controller" controller\} is affected, plus any relevant code data. \p\p\1
What Happens \0\p\p
The software formats the actual log file data to display historical information containing different events for the selected RAID Module. These events include component failures, general status changes, and \{\2\bring_popup "Parity" parity\} reports. Information for these events is recorded in the message log in different ways: \p\p
\{\1 o \0\} The background monitor checks the RAID Modules. \p\p
\{\1 o \0\} Parity check/repair has run. \p\p
\{\1 o \0\} General status changes occur, such as I/O errors, configuration formats, and component failures.
\p\p\1
Related Topics \label "whenmlogrt"\0\p
\{\3\goto "Message Log Questions" Common Questions\} \p
\{\3\goto "How To Use Message Log" How To Use Message Log\}
\p\p
\{\7\goto "whenmlogtop" Top Of Page\} \p
\keyword "Message Log" \keyword "using Message Log" \keyword "view messages" \keyword "events, past" \keyword "past events" \keyword "historical record" \keyword "view events"

\topic "Log Settings Apply To Which Raid Modules?" \p\1
Will Changing Log Settings Apply To Each Selected RAID Module Or To All RAID Modules? \0\p\p
Changing any parameter in the Log Settings option always applies to ALL RAID Modules, regardless of which RAID Module you may have initially selected. \p\p
To view or change these settings, select the Status Application >> Message Log. From the top menu, select Options >> Log Settings.
\p\p\1
Related Topics \0\p
\{\3\goto "Message Log Questions" Common Questions\} \p
\{\3\goto "How To Change Message Log's Settings" How To Change Message Log's Settings\} \p
\{\3\goto "When To Change Message Log's Settings" When Should I Change Message Log's Settings?\} \p
\keyword "Message Log" \keyword "settings" \keyword "module selection" \keyword "All modules"

\topic "Parity Questions" \p\1
Parity Questions \0\p\p
\{\3\subtopic "Stop Parity Check/Repair When Running" Can I Stop Parity Check/Repair When It Is Running?\}
\p\p
\{\3\subtopic "When Should I Run Parity Check/Repair?" When Should I Run Parity Check/Repair?\}
\p\p\1
Related Topics\0\p
\{\3\goto "Common Question Topics" Common Questions\} \p
\{\3\goto "How To Use Options >> Auto Parity Settings" How To Use Options >> Auto Parity Settings\}
\p
\{\3\goto "How To Use Manual Parity Check/Repair" How To Use Manual Parity Check/Repair\} \p
\{\3\goto "Parity Concept" Parity\} \p
\{\3\goto "Parity Troubleshooting" Troubleshooting\} \p
\keyword "questions" \keyword "parity"

\topic "Stop Parity Check/Repair When Running" \p\1
Can I Stop Parity Check/Repair When It Is Running? \0\p\p
Yes. You can stop Manual Parity Check/Repair (Recovery Application) after starting it. However, stopping this operation means that you have NOT completely checked or repaired the parity for the selected logical units. \p\p
When you see a histogram displaying the progress of parity \{\2\bring_popup "Parity Check/Repair" check/repair\}, you can select Cancel to stop the parity operation at any time.
\p\p\1
Related Topics\0\p
\{\3\goto "Parity Questions" Common Questions\} \p
\keyword "parity" \keyword "check parity" \keyword "repair parity" \keyword "manual parity" \keyword "terminated parity check"

\topic "When Should I Run Parity Check/Repair?" \p\1
When Should I Run Parity Check/Repair? \0\p\p
Running the automatic parity \{\2\bring_popup "Parity Check/Repair" check/repair\} at a set time each day or on a set day of the week can provide early warning that there might be data problems. Enable this option with Maintenance/Tuning Application >> Options >> Auto Parity Settings.
\p\p
You may want to manually run parity check/repair if you notice parity error reports in the Status Application's Message Log. Use the Recovery Application >> Manual Parity Check/ Repair.
\p\p\1
IMPORTANT \0\p
Be sure to use the Manual Parity Check/Repair option when instructed to do so by any Recovery Guru/Health Check procedure.
\p\p\1
Related Topics\0\p
\{\3\goto "Parity Questions" Common Questions\} \p
\{\3\goto "How To Use Options >> Auto Parity Settings" How To Use Options >> Auto Parity Settings\} \p
\{\3\goto "How To Use Manual Parity Check/Repair" How To Use Manual Parity Check/Repair\} \p
\keyword "parity" \keyword "check parity" \keyword "repair parity" \keyword "manual parity" \keyword "automatic parity" \keyword "interval" \keyword "daily parity check" \keyword "weekly parity check"

\topic "Performance Monitor Questions" \p\1
Performance Monitor Questions \0\p\p
\{\3\subtopic "Monitoring Performance For More Than One Raid Module" Can I Monitor Performance For More Than One RAID Module At A Time?\}
\p\p
\{\3\subtopic "Should I Stop Performance Monitor Before Saving Data?" Should I Stop the Performance Monitor Before Saving the Performance Data?\}
\p\p
\{\3\subtopic "When To Save Performance Monitor Data" When Should I Save Performance Monitor Data?\}
\p\p
\{\3\subtopic "When To Use Performance Monitor" When Should I Use Performance Monitor?\}
\p\p
\{\3\subtopic "Why Save Multiple Copies Of Data?" Why Should I Save Multiple Instances of Performance Monitor Data?\}
\p\p\1
Related Topics\0\p
\{\3\goto "Common Question Topics" Common Questions\} \p
\{\3\goto "How To Use File >> Save Performance Data" Saving Performance Monitor Data\} \p
\{\3\goto "How To Use Performance Monitor" How To Use Performance Monitor\} \p
\{\3\goto "Performance Concept" Performance\} \p
\{\3\goto "Performance Monitor Restrictions" Restrictions/Cautions\} \p
\{\3\goto "Performance Monitor Troubleshooting" Troubleshooting\} \p
\keyword "Performance Monitor" \keyword "questions"

\topic "Monitoring Performance For More Than One Raid Module" \p\1
Can I Monitor Performance For More Than One RAID Module At A Time? \0\p\p
Yes. By opening another Status Application, you can monitor the performance of different \{\2\bring_popup "RAID Module" RAID Modules\}. However, use caution when running more than one instance of the Status Application >> Performance Monitor due to slowed Performance rates.
\p\p\1
Related Topics\0\p
\{\3\goto "Performance Monitor Questions" Common Questions\} \p
\{\3\goto "How To Use Performance Monitor" How To Use Performance Monitor\} \p
\{\3\goto "Interpreting Performance Monitor Data" Interpreting Performance Monitor Data\} \p
\keyword "Performance Monitor" \keyword "monitoring performance" \keyword "module selection" \keyword "rate"

\topic "Should I Stop Performance Monitor Before Saving Data?" \p\1
Should I Stop the Performance Monitor Before Saving the Performance Data? \0\p\p
No. When you select File >> Save Performance Data (Status Application), the current data is captured and saved to a file. The Performance monitor is still collecting data. Remember, if you stop monitoring, Performance Monitor is reset. If you want to save the data at different intervals, it is best to leave the Performance Monitor running.
\p\p\1
Related Topics\0\p
\{\3\goto "Performance Monitor Questions" Common Questions\} \p
\{\3\goto "How To Use File >> Save Performance Data" Saving Performance Monitor Data\} \p
\{\3\goto "How To Use Performance Monitor" How To Use Performance Monitor\} \p
\keyword "Performance Monitor" \keyword "data performance" \keyword "save" \keyword "interval"

\topic "When To Save Performance Monitor Data" \p\1
When Should I Save Performance Monitor Data? \0\p\p
Save Performance Monitor (Status Application) data at any time it is collecting data by selecting File >> Save Performance Data from the pull-down menu. You do NOT need to stop the Performance Monitor to save the data. In fact, it is best to allow the Performance Monitor to continue monitoring if you plan to save multiple instances of the data collected at different times.
\p\p\1
Related Topics\0\p
\{\3\goto "Performance Monitor Questions" Common Questions\} \p
\{\3\goto "How To Use File >> Save Performance Data" Saving Performance Monitor Data\} \p
\keyword "using Save Performance Monitor" \keyword "save" \keyword "Performance Monitor"

\topic "When To Use Performance Monitor" \p\1
When Should I Use Performance Monitor? \0\p\p
Use Performance Monitor (Status Application) to obtain information that may be useful in evaluating system performance, and to determine possible methods for improving system performance. \p\p
The Performance Monitor collects data during specified \{\2\bring_popup "Polling Interval" intervals\}. You can determine if the workload is evenly distributed between the \{\2\bring_popup "Controller" controllers\} or \{\2\bring_popup "Logical Unit" LUNs\}, and adjust accordingly.
\p\p\1
Related Topics\0\p
\{\3\goto "Performance Monitor Questions" Common Questions\} \p
\{\3\goto "How To Use Performance Monitor" How To Use Performance Monitor\} \p
\keyword "using Performance Monitor" \keyword "data performance" \keyword "system performance" \keyword "monitoring performance" \keyword "Performance Monitor"

\topic "Why Save Multiple Copies Of Data?" \p\1
Why Should I Save Multiple Instances of Performance Monitor Data? \0\p\p
You might want to save Performance Monitor (Status Application) data at more than one time to use for comparison. Saving data at different times allows you to view the heaviest times of I/O, which controller is receiving more workload, etc.
\p\p\1
Related Topics\0\p
\{\3\goto "Performance Monitor Questions" Common Questions\} \p
\{\3\goto "How To Use File >> Save Performance Data" Saving Performance Monitor Data\} \p
\{\3\goto "Interpreting Performance Monitor Data" Interpreting Performance Monitor Data\} \p
\keyword "copy" \keyword "Performance Monitor" \keyword "data performance" \keyword "save" \keyword "monitoring performance"

\topic "Manually Starting Reconstruction" \p\1
RECONSTRUCTION QUESTIONS \p\p
Can I Manually Start Reconstruction? \p\p\0
Yes. If \{\2\bring_popup "Reconstruction" reconstruction\} does NOT start automatically after you replace a failed drive, you can start the reconstruction operation using the Recovery Application >> Options >> Manual Recovery >> Drives >> Reconstruct. \p\p\1
Remember\0 -- Because drive reconstruction normally begins when you replace a failed drive, it is best to follow the Recovery Guru/Health Check procedure provided, using the Manual Recovery options only when instructed.
\p\p\1
Related Topics \0\p
\{\3\goto "Common Question Topics" Common Questions\} \p
\{\3\goto "How To Use Manual Recovery >> Drives" How To Use Manual Recovery >> Drives\} \p
\{\3\goto "Reconstruction Concept" Reconstruction\} \p
\{\3\goto "Reconstruction Restrictions" Restrictions/Cautions\} \p
\{\3\goto "Reconstruction Troubleshooting" Troubleshooting\} \p
\keyword "reconstruction" \keyword "manual reconstruction" \keyword "data recovery" \keyword "drive recovery" \keyword "Manual Recovery options"

\topic "When To Use Recovery Guru" \p\1
RECOVERY GURU/HEALTH CHECK QUESTIONS \p\p
When Should I Use Recovery Guru/Health Check? \label "whengurutop" 
\p\p
Fast Find -- \{\5\goto "whengururt" Related Topics\}
\p\p\0
Use Recovery Guru/Health Check to check selected \{\2\bring_popup "RAID Module" RAID Modules\} for component failures and to recover from them by following step-by-step instructions (select Show Procedure). \p\p
Use Recovery Guru when: \p\p
\{\1 o \0\} An alarm sounds on your module. \p\p
\{\1 o \0\} Fault lights on any module component are lit. \p\p
\{\1 o \0\} Status Application >> Message Log >> Show Details indicates you should. \p\p
\{\1 o \0\} A non-optimal status is reported for any module component.
\p\p\4
CAUTION \0\p
Always select Recovery Guru to ensure the problem is correctly diagnosed BEFORE attempting any manual recovery procedure. Incorrectly performing a procedure or performing the wrong procedure could cause equipment damage or data loss. Recovery Guru provides step-by-step procedures to make sure that you are correcting the right problem.
\p\p\1
Related Topics\0\label "whengururt"\p
\{\3\goto "Common Question Topics" Common Questions\} \p
\{\3\goto "Failure Types Concept" Failure Types\} \p
\{\3\goto "How To Use Recovery Guru" How To Use Recovery Guru/Health Check\} \p
\{\3\goto "Recovery Guru Restrictions" Restrictions/Cautions\}
\p\p
\{\7\goto "whengurutop" Top Of Page\}\p
\keyword "Recovery Guru" \keyword "using Recovery Guru" \keyword "error detection" \keyword "status reporting" \keyword "component recovery"

\topic "Troubleshooting Topics" \p\1
Troubleshooting \label "troubletop"
\p\p
Fast Find -- \{\5\goto "troublefirm" Firmware/NVSRAM\} | \{\5\goto "troublelocmod" Locate Module\} | \{\5\goto "troublelunassign" LUN Assignment\} | \{\5\goto "troublemlog" Message Log\} | \{\5\goto "troublemprofile" Module Profile\} | \{\5\goto "troublehelp" Help\} | \{\5\goto "troubleparity" Parity\} | \{\5\goto "troubleperform" Performance Monitor\} | \{\5\goto "troublerecon" Reconstruction\} | \{\5\goto "troublesave" Save Module Profile\} | \{\5\goto "troublesmod" Select Module\} | \{\5\goto "troublert" Related Topics\} \p\p\1
IMPORTANT \0\p
If you do not find the information you are seeking here, check the "Installation and Support Guide" specific to your operating system for the latest restrictions and troubleshooting information.
\0\p\p
\{\3\subtopic "Caching Troubleshooting" Caching\}
\p\p
\{\3\subtopic "Configuration Troubleshooting" Configuration\}
\p\p
\{\3\subtopic "Controller Mode Troubleshooting" Controller Mode\}
\p\p
\{\3\goto "Can't De-Select The Fibre Channel File" Fibre Channel\}
\p\p\label "troublefirm"
\{\3\subtopic "Firmware/NVSRAM Troubleshooting" Firmware/NVSRAM\}
\p\p\label "troublelocmod"
\{\3\subtopic "Locate Module Troubleshooting" Locate Module\}
\p\p\label "troublelunassign"
\{\3\subtopic "LUNs Are Marked As Inaccessible" LUN Assignment\}
\p\p\label "troublemlog"
\{\3\subtopic "Message Log Troubleshooting" Message Log\}
\p\p\label "troublemprofile"
\{\3\subtopic "Module Profile Troubleshooting" Module Profile\}
\p\p\label "troublehelp"
\{\3\subtopic "Online Help Troubleshooting" Online Help\}
\p\p\label "troubleparity"
\{\3\subtopic "Parity Troubleshooting" Parity\}
\p\p\label "troubleperform"
\{\3\subtopic "Performance Monitor Troubleshooting" Performance Monitor\}
\p\p\label "troublerecon"
\{\3\subtopic "Reconstruction Troubleshooting" Reconstruction\}
\p\p\label "troublesave"
\{\3\subtopic "Can Save Module Profile Restore My Configuration?" Save Module Profile\}
\p\p\label "troublesmod"
\{\3\subtopic "Select Module Screen Does/Doesn't Appear" Select Module\}
\p\p\1
Related Topics \0\label "troublert"\p
\{\3\goto "Common Question Topics" Common Questions\} \p
\{\3\goto "Concept Topics" Concepts\} \p
\{\3\goto "Procedure Topics" Procedures\} \p
\{\3\goto "Restriction/Caution Topics" Restrictions/Cautions\}
\p\p
\{\7\goto "troubletop" Top Of Page\} \p
\keyword "troubleshooting" \keyword "details, troubleshooting"

\topic "Caching Troubleshooting" \p\1
Caching Troubleshooting \0\p\p
\{\3\subtopic "Asterisk Next To Caching In Parameters Or Module Profile" An Asterisk Appears Next To The Caching Parameters (Caching Parameters And/Or Module Profile LUNs)\}
\p\p
\{\3\subtopic "Can't Select Write Cache Mirroring" Can't Select Write Cache Mirroring\}
\p\p\1
Related Topics\0\p
\{\3\goto "Caching Concept" Caching\} \p
\{\3\goto "How To Use Caching Parameters" How To Use Caching Parameters\} \p
\{\3\goto "Caching Restrictions" Restrictions/Cautions\} \p
\{\3\goto "Troubleshooting Topics" Troubleshooting\} \p
\keyword "troubleshooting" \keyword "caching" \keyword "parameters, caching"

\topic "Asterisk Next To Caching In Parameters Or Module Profile" \p\1
An Asterisk Appears Next To The Caching Parameters (Caching Parameters And/Or Module Profile LUNs)
\p\p
Cause \0 -- You might see an asterisk next to the caching parameters column in either of these screens because the controller has disabled the parameter for some reason (such as low batteries or controller replacement). This means that the parameter is enabled, but currently is not active.
\p\p\1
Action \0 -- If you see this condition, use Message Log (Status Application) to determine the correct action to take.
\p\p\1
Related Topics\0\p
\{\3\goto "How To Use Caching Parameters" How To Use Caching Parameters\} \p
\{\3\goto "Caching Troubleshooting" Troubleshooting\} \p
\keyword "cache disabled" \keyword "inactive cache" \keyword "disabled cache" \keyword "Caching Parameters" \keyword "Module Profile" \keyword "screen description"

\topic "Can't Select Write Cache Mirroring" \p\1
Can't Select Write Cache Mirroring
\p\p
Cause \0 -- This caching parameter is only available if both controllers have the same \{\2\bring_popup "Cache Memory" cache\} and \{\2\bring_popup "Processor Memory" processor\} memory sizes.
\p\p\1
Action \0 -- Use Module Profile >> Controllers to determine if both controllers in the \{\2\bring_popup "Redundant Controller Pair" redundant pair\} have the same cache size before enabling this parameter.
\p\p\1
Related Topics\0\p
\{\3\goto "How To Use Caching Parameters" How To Use Caching Parameters\} \p
\{\3\goto "Caching Troubleshooting" Troubleshooting\} \p
\keyword "caching" \keyword "parameters, caching" \keyword "write cache mirroring" \keyword "disabled cache" \keyword "size, controller" \keyword "cache memory" \keyword "processor memory"

\topic "Configuration Troubleshooting" \p\1
Configuration Troubleshooting \label "cfgtroubletop"
\p\p
Fast Find -- \{\5\goto "troublecfgrt" Related Topics\}
\0\p\p
\{\3\subtopic "Can't Add LUNs To An Existing Drive Group" Can't Add LUNs To An Existing Drive Group\}
\p\p
\{\3\subtopic "Can't Choose/Change A RAID Level" Can't Choose/Change A Particular RAID Level\}
\p\p
\{\3\subtopic "Can't Open The Configuration Application" Can't Open The Configuration Application\}
\p\p
\{\3\subtopic "The Hot Spare Has A Smaller Capacity Message" The Hot Spare You Just Created At Drive Location [x,y] Has A Smaller Capacity Than Some Of The Drives In The Module Message\}
\p\p
\{\3\subtopic "LUN Creation/Format Failed" LUN Creation/Format Failed\}
\p\p
\{\3\subtopic "Remaining Capacity Is Less Than Expected" Remaining Capacity Is Less Than Expected\}
\p\p
\{\3\subtopic "Screen Information Is Incorrect Or Incomplete" Screen Information Is Incorrect Or Incomplete\}
\p\p
\{\3\subtopic "Total And Available Capacity Show Different Values" Total Capacity (Main Screen) and Available Capacity (Create LUN Screen) Show Different Values\}
\p\p\1
Related Topics\0\label "troublecfgrt"\p
\{\3\goto "Changing LUN Parameters Concept" Changing LUN Parameters\} \p
\{\3\goto "Configuration Questions" Common Questions\} \p
\{\3\goto "Configuring Concept" Configuring\} \p
\{\3\goto "Configuration Application" Configuration Application\} \p
\{\3\goto "Configuration Restrictions" Restrictions/Cautions\} \p
\{\3\goto "Troubleshooting Topics" Troubleshooting\}
\p\p
\{\7\goto "cfgtroubletop" Top Of Page\} \p
\keyword "configuration" \keyword "troubleshooting"

\topic "Can't Add LUNs To An Existing Drive Group" \p\1
Can't Add LUNs To An Existing Drive Group \label "cfgnoaddtop" 
\p\p
Fast Find -- \{\5\goto "cfgnoaddrt" Related Topics\}
\p\p\1
Cause\0 -- Either the \{\2\bring_popup "Configured Drive Group" drive group\} does not have any \{\2\bring_popup "Remaining Capacity" remaining\} capacity, or you have created the maximum number of \{\2\bring_popup "Logical Unit" LUNs\} allowed. \p\p\1
Action\0 -- If your existing configuration does not meet your needs, you may have to delete all the LUNs in the drive group that you want to change, then use Create LUN to re-create the LUNs/drive groups you want. Remember, deleting LUNs deletes all data on the LUNs. \p\p
If you have remaining \{\2\bring_popup "Unassigned Drive Group" unassigned\} drives, use Configuration Application >> Modify Group/LUN >> Expand Capacity to add drives to the current drive group. \p\p\1
IMPORTANT \0\p
If you want to change certain parameters, select the Changing Logical Unit Parameters topic in the "Related Topics" list below. \p\p\1
Related Topics \label "cfgnoaddrt"\0\p
\{\3\goto "Changing LUN Parameters Concept" Changing Logical Unit Parameters\} \p
\{\3\goto "Expand Capacity For A Drive Group" Expand Capacity For A Drive Group\} \p
\{\3\goto "How To Use Create LUN" How To Use Create LUN\} \p
\{\3\goto "How To Use Delete" How To Use Delete\} \p
\{\3\goto "Configuration Troubleshooting" Troubleshooting\}
\p\p
\{\7\goto "cfgnoaddtop" Top Of Page\}\p
\keyword "remaining capacity" \keyword "drive group, capacity" \keyword "changing configuration" \keyword "LUN creation" \keyword "LUNs, number of" \keyword "number of LUNs"

\topic "Can't Choose/Change A RAID Level" \p\1
Can't Choose/Change A Particular RAID Level \p\p
Cause\0 -- A grayed out \{\2\bring_popup "RAID Level" RAID Level\} indicates that the current number of drives selected is not a valid number for the particular RAID Level. For example, \{\2\bring_popup "RAID 1" RAID 1\} must always use an even number of drives. \p\p
This option could be grayed out in either the Configuration Application >> Create LUN or Modify Group/LUN >> RAID Level screens. \p\p\1
Action\0 -- Review your RAID Level selection and choose another RAID Level or change the number of drives selected.
\p\p\1
Related Topics\0\p
\{\3\goto "Configuration Troubleshooting" Troubleshooting\} \p
\{\3\goto "How To Use Create LUN" How To Use Create LUN\} \p
\{\3\goto "Modify RAID Level For A Drive Group" Modify RAID Level For A Drive Group\} \p
\keyword "RAID Level" \keyword "changing RAID Level" \keyword "Modify Group/LUN" \keyword "LUN creation" \keyword "changing LUN parameters" \keyword "parameters, LUN" \keyword "drive group, modifying" \keyword "modifying RAID Level" \keyword "LUN parameters"

\topic "Can't Open The Configuration Application" \p\1
Can't Open The Configuration Application \label "cfgnoopentop" 
\p\p
Fast Find -- \{\5\goto "cfgnoopenrt" Related Topics\}
\p\p\1
Cause\0 -- You can only have one Configuration Application open at a time from a single host machine. This prevents any possible configuration conflicts. Although you can have only one Configuration Application open at one time, you can open multiple copies of the other applications. \p\p\4
CAUTION \0\p
If you are using the Networked version and have more than one station configured on your network, you are able to open more than one Configuration session at a time. Also, if the \{\2\bring_popup "RAID Module" RAID Module\} is using a dual-host Configuration, such as \{\2\bring_popup "Multi-Host Configuration" multi-host\} configuration or \{\2\bring_popup "Independent Controller Configuration" independent\} controller configuration, either host machine can open one Configuration session and cannot detect what the other host is doing. \p\p\1
Action\0 -- Be sure that you have ONLY one session open when configuring or deleting LUNs if you are using one of these configurations or the operation will fail for one host.
\p\p\1
Related Topics \label "cfgnoopenrt"\0\p
\{\3\goto "Configuration Application" Configuration Application\} \p
\{\3\goto "Host-RAID Module Configuration Types Supported Concept" Host-RAID Module Configuration Types Supported\} \p
\{\3\goto "Configuration Troubleshooting" Troubleshooting\}
\p\p
\{\7\goto "cfgnoopentop" Top Of Page\}\p
\keyword "open" \keyword "Configuration Application" \keyword "single-host configuration" \keyword "access, exclusive required"

\topic "The Hot Spare Has A Smaller Capacity Message" \p\1
The Hot Spare You Just Created At Drive Location [x,y] Has A Smaller Capacity Than Some Of The Drives In The Module Message \label "hotsmalltop" 
\p\p
Fast Find -- \{\5\goto "hotsmallwhat" Action\} | \{\5\goto "hotsmallselect" Select Larger Drives\} | \{\5\goto "hotsmallrt" Related Topics\}
\p\p
IMPORTANT \0\p
The unassigned drive group must contain a drive of the largest capacity in order for you to create a hot spare that can cover for any failed drive in the RAID Module. \p\p\1
Cause\0 -- \{\2\bring_popup "Hot Spare" Hot spares\} cannot replace drives with a larger capacity (that is a 2 GB hot spare drive cannot replace a 4 GB failed drive). When you create a hot spare, the Configuration Application selects the first available drive unless you specify otherwise. If your \{\2\bring_popup "Unassigned Drive Group" unassigned\} drive group contains drives with different capacities, this may not be one of the larger capacity drives.
\p\p\1
NOTE\0: Remember [x,y] indicates the unique \{\2\bring_popup "Location (Drive)" location\} of the drive in the selected RAID Module. This identifier corresponds to the drive's \{\2\bring_popup "SCSI Channel" SCSI Channel\} number and \{\2\bring_popup "SCSI ID" SCSI ID\}, where the channel number is always listed first. For example, [2,1] corresponds to the drive at location SCSI Channel 2 and SCSI ID 1. \p\p\1
Action\0\label "hotsmallwhat" -- Select Yes to create the hot spare using the smaller capacity drive (it will NOT be able to cover for a larger capacity drive), or select No so the hot spare is not created. \p\p
To avoid seeing this message, select larger capacity drives during the hot spare creation. See the following section for details. \p\p\1
Selecting Larger Capacity Drives \label "hotsmallselect"\0\p\p
1. Before creating hot spares, use List/Locate Drives to determine the size of the drives in the RAID Module, and to record the capacities and location of the larger capacity drives in the unassigned drive group. \p\p
2. In the Configuration main screen, highlight the Unassigned drive group. \p\p
3. Select Create Hot Spare. \p\p
4. Select the number of hot spare drives you want to create, and select Options. \p\p
5. Does the larger capacity drive appear in the Selected Drives list? \p\p
--\1 YES.\0 Select Create. \p\p
--\1 NO.\0 Highlight a larger capacity drive in the Unselected Drives list. Select Move. (Remember, the number of selected drives must match the number of hot spares you selected in Step 4.) Select Create.
\p\p\1
Related Topics \label "hotsmallrt"\0\p
\{\3\goto "How To Use Create Hot Spare" How To Use Create Hot Spare\} \p
\{\3\goto "How To Use List/Locate Drives" How To Use List/Locate Drives\} \p
\{\3\goto "Configuration Restrictions" Restrictions/Cautions\} \p
\{\3\goto "Configuration Troubleshooting" Troubleshooting\}
\p\p
\{\7\goto "hotsmalltop" Top Of Page\}\p
\keyword "hot spare" \keyword "capacity" \keyword "smaller capacity" \keyword "Create Hot Spare" \keyword "drive selection" \keyword "selecting drives" \keyword "message, hot spare" \keyword "error detection"

\topic "LUN Creation/Format Failed" \p\1
LUN Creation/Format Failed \label "cfgfailtop" 
\p\p
Fast Find -- \{\5\goto "cfgfailwhat" Action\} | \{\5\goto "cfgfailrt" Related Topics\}
\p\p\1
Cause\0 -- Once you select Create during the LUN Creation process, the Configuration main screen displays "Formatting" until the operation is completed. However, if this format operation fails, Configuration displays a message that the \{\2\bring_popup "Logical Unit" logical unit\} was not created and a message is written to Message Log in the Status Application. LUN creation can fail for a number of reasons: \p\p
\{\1 o \0\} Most likely, a drive or some other module component has failed. \p\p
\{\1 o \0\} Only one configuration session at a time will be successful if you launch more than one from both hosts with (\{\2\bring_popup "Independent Controller Configuration"independent\} controller or \{\2\bring_popup "Multi-Host Configuration" multi-host\} configurations) or from more than one station (Networked versions). \p\p
\{\1 o \0\} If you begin to create more than two new \{\2\bring_popup "Drive Group" drive groups\} at a time, the subsequent LUN creations will fail. \p\p\1
Action\0\label "cfgfailwhat" -- Depending on which problem has occurred, do the following: \p\p
\{\1 o \0\} If you see this message, determine if a component has failed by using Recovery Guru/Health Check (Recovery Application) and follow the step-by-step procedures provided to correct the problem. \p\p
\{\1 o \0\} When creating or deleting drive groups/LUNs, always use only one host's Configuration Application at a time. \p\p
\{\1 o \0\} Create no more than two new drive groups at a time and wait for them to transition from Formatting to \{\2\bring_popup "Optimal Mode" Optimal\} before creating two more if needed.
\p\p\1
Related Topics \label "cfgfailrt"\0\p
\{\3\goto "How To Use Create LUN" How To Use Create LUN\} \p
\{\3\goto "How To Use Message Log" How To Use Message Log\} \p
\{\3\goto "How To Use Recovery Guru" How To Use Recovery Guru/Health Check\} \p
\{\3\goto "Configuration Troubleshooting" Troubleshooting\}
\p\p
\{\7\goto "cfgfailtop" Top Of Page\}\p
\keyword "format failed" \keyword "failures" \keyword "LUN creation" \keyword "independent controller configuration" \keyword "multi-host configuration" \keyword "networked version" \keyword "exclusive access operations" \keyword "access, exclusive required"

\topic "Remaining Capacity Is Less Than Expected" \p\1
Remaining Capacity Is Less Than Expected \label "cfgremaintop" 
\p\p
Fast Find -- \{\5\goto "cfgremainrt" Related Topics\}
\p\p\1
Cause\0 -- \{\2\bring_popup "Remaining Capacity" Remaining\} capacity reflects the largest contiguous storage space available for creating \{\2\bring_popup "Logical Unit" LUNs\} on a \{\2\bring_popup "Drive Group" drive group\}. Because of this, it is possible for this amount NOT to include the capacity of LUNs deleted from the drive group if the deleted LUNs were non-contiguous or not the largest contiguous amount. \p\p
For example, assume that drive group one has LUNs 0, 1, and 2 configured at 1000 MB capacity each and that this drive group shows 1500 MB remaining capacity in the Module Information area of the Configuration main screen. If you delete LUN 1, the remaining capacity will still show only 1500 MB until you configure that space into additional LUNs on the drive group. Once you use the 1500 MB, the drive group shows remaining capacity of 1000 MB (from the deleted LUN 1). \p\p\1
Action\0 -- It is best to use all the remaining/\{\2\bring_popup "Available Capacity"available\} capacity when creating new drive group/LUNs. However, if you do not and this condition occurs, do one of the following: \p\p
\{\1 o \0\} Select Configuration Application >> Modify Group/LUNs >> Defragment to combine the space left after deletion into one contiguous block of space. \p\p
\{\1 o \0\} Use Configuration Application >> Create LUN to add LUNs to the drive group using all the remaining capacity that shows. Then, you can add more LUNs with the new remaining capacity (from the deleted LUN).
\p\p\1
Related Topics \label "cfgremainrt"\0\p
\{\3\goto "Defragment A Drive Group" Defragment A Drive Group\} \p
\{\3\goto "How To Use Create LUN" How To Use Create LUN\} \p
\{\3\goto "How To Use Delete" How To Use Delete\} \p
\{\3\goto "Configuration Troubleshooting" Troubleshooting\}
\p\p
\{\7\goto "cfgremaintop" Top Of Page\}\p
\keyword "remaining capacity" \keyword "capacity" \keyword "configuration information"

\topic "Screen Information Is Incorrect Or Incomplete" \p\1
Screen Information Is Incorrect Or Incomplete \p\p
Cause\0 -- During LUN creation, you might see LUNs appear and disappear, or capacities seem to change at the Configuration main screen. Also, displays in other screens, such as Module Profile, could have incomplete screen information. \p\p\1
Action\0 -- Wait for the LUNs to become Optimal before continuing with other operations or before creating LUNs on other drives. The information displayed while the LUN is being created may be incorrect or missing. When the last LUN becomes \{\2\bring_popup "Optimal Mode" Optimal\}, all the screen information is correct. Also, re-selecting the \{\2\bring_popup "RAID Module" RAID Module\} updates the information on the screen.
\p\p\1
Related Topics\0\p
\{\3\goto "Configuration Troubleshooting" Troubleshooting\} \p
\keyword "missing information" \keyword "screen description" \keyword "Configuration Application" \keyword "status reporting" \keyword "update statuses" \keyword "configuration information" \keyword "Module Profile"

\topic "Total And Available Capacity Show Different Values" \p\1
Total Capacity (Main Screen) and Available Capacity (Create LUN Screen) Show Different Values \label "cfgdiffcaptop" 
\p\p
Fast Find -- \{\5\goto "cfgdiffcapwhat" Action\} | \{\5\goto "cfgdiffcaprt" Related Topics\}
\p\p\1
Cause\0 -- If your \{\2\bring_popup "Unassigned Drive Group" unassigned\} drive group contains drives with different capacities, such as 2 GB and 4 GB, then the main screen shows the correct \{\2\bring_popup "Total Capacity" total\} capacity (the sum of the available capacity on all the different size drives). However, the \{\2\bring_popup "Available Capacity" available\} capacity of the unassigned drive group (displayed in the Create LUN screen) is based on the capacity of the smaller drives. For example, if the unassigned drive group consists of 5 drives (three 2 GB drives and two 4 GB drives), the total capacity is displayed as 14 GB ((3x2) + (2x4)), but the available capacity is displayed as 10 GB (5x2 GB). \p\p
Furthermore, if you create LUNs using mixed capacity drives, you use only the smallest capacity available (2GB) and you cannot access the additional capacity on the larger drives. \p\p\1
Action\0\label "cfgdiffcapwhat" -- To avoid wasting the additional capacity of the larger drives, select drives of the same capacity when creating logical units: \p\p
1. Select the Configuration Application >> RAID Module. \p\p
2. Highlight the Unassigned drive group. \p\p
3. Select Create LUN and set the desired \{\2\bring_popup "RAID Level" RAID Level\}, number of drives, and number of LUNs. \p\p
4. Select Options >> Drive Selection and choose specific drives that share the same capacity (large or small). \p\p\1
Example\0 -- if you were going to create a three-drive RAID 3, 12 GB LUN and the assigned drive group contains 5 drives (two 2 GB drives and three 4 GB drives), you want to select the larger capacity drives. Once you select the number of drives in the Create LUN main screen, the available capacity is initially reported as 6 GB (instead of 12 GB). However, using Options >> Drive Selection you can select the three 4 GB drives (move them to the Selected Drives box) and the correct available capacity is reported.
\p\p\1
Related Topics \label "cfgdiffcaprt"\0\p
\{\3\goto "How To Use Create LUN" How To Use Create LUN\} \p
\{\3\goto "Configuration Troubleshooting" Troubleshooting\} \p
\{\3\goto "Using Create LUN >> Options" Using Create LUN >> Options\}
\p\p
\{\7\goto "cfgdiffcaptop" Top Of Page\}\p
\keyword "available capacity" \keyword "capacity" \keyword "total capacity" \keyword "configuration information" \keyword "LUN creation" \keyword "Create LUN" \keyword "screen description" \keyword "Configuration Application" \keyword "values" \keyword "drive selection" \keyword "selecting drives"

\topic "Controller Mode Troubleshooting" \p\1
Controller Mode Troubleshooting \0\p\p
\{\3\subtopic "Controller Mode Passive After Replacement" Controller Mode is Passive and It Doesn't Own Any LUNs After Replacing A Failed Controller\}
\p\p
\{\3\subtopic "Can't Change Controller Mode From Active/Active to Active/Passive" Can't Change Controller Mode From Active/Active to Active/Passive\}
\p\p\1
Related Topics \0\p
\{\3\goto "How To Use Controller Mode" How To Use Controller Mode\} \p
\{\3\goto "Controller Mode Restrictions" Restrictions/Cautions\} \p
\{\3\goto "Information In Controller Mode" What Information Appears In Controller Mode?\} \p
\{\3\goto "Troubleshooting Topics" Troubleshooting\} \p
\keyword "troubleshooting" \keyword "mode" \keyword "Controller Mode"

\topic "Controller Mode Passive After Replacement" \p\1
Controller Mode is Passive and It Doesn't Own Any LUNs After Replacing A Failed Controller
\p\p
Cause \0 -- After you use the Recovery Application >> Recovery Guru/Health Check to replace the failed controller and Options >> Manual Recovery >> Controller Pairs to place it back online, the controller could be \{\2\bring_popup "Optimal Mode" Optimal\} but in the \{\2\bring_popup "Passive Controller Mode" Passive\} mode rather than Active.
\p\p\1
Action \0 -- With the newly replaced controller Optimal, use Maintenance/Tuning Application >> Controller Mode >> Change to Active/Active to make the controller Active. You can either \{\2\bring_popup "Balanced LUN Distribution" balance\} the drive groups/LUNs during this mode change, or you can use Maintenance/Tuning Application >> LUN Balancing later to assign specific drive group/LUNs to each Active controller.
\p\p\1
Related Topics \0\p
\{\3\goto "Considerations For Two Active Controllers" Any Special Considerations For A RAID Module With Two Active Controllers?\} \p
\{\3\goto "Controller Mode Troubleshooting" Troubleshooting\} \p
\keyword "passive controller" \keyword "controllers, passive" \keyword "mode" \keyword "controller recovery" \keyword "controller, LUNs owned" \keyword "LUN assignment" \keyword "changing active/active" \keyword "LUN Balancing" \keyword "controller replacement" \keyword "replacing controller"

\topic "Can't Change Controller Mode From Active/Active to Active/Passive" \p\1
Can't Change Controller Mode From Active/Active to Active/Passive
\p\p
Cause \0 -- Once you have an \{\2\bring_popup "Active/Active Controller Pair" active/active\} controller pair, you CANNOT undo this mode change through the graphical user interface (GUI). For best results, always use active/active controllers to improve your I/O performance and so that both controllers can own some of the drive groups/LUNs.
\p\p\1
Action \0 -- You must use the command line \{\2\bring_popup "Command Line Utilities" utility\}, rdacutil, if you want to change an active/active controller pair to \{\2\bring_popup "Active/Passive Controller Pair" active/passive\}. For example, to change the RAID Module's (named sonne_002) controller pair to active/passive, type:
\p\p
rdacutil -m 1 "sonne_002"
\p\p\1
Related Topics \0\p
\{\3\goto "Controller Mode Troubleshooting" Troubleshooting\} \p
\keyword "rdacutil utility" \keyword "mode" \keyword "passive controller" \keyword "controllers, passive" \keyword "Controller Mode" \keyword "active controllers" \keyword "changing active/passive"

\topic "Firmware/NVSRAM Troubleshooting" \p\1
Firmware/NVSRAM Troubleshooting \0\p\p
\{\3\subtopic "Can't De-Select The Fibre Channel File" Can't De-Select The Fibre Channel Level File\}
\p\p
\{\3\subtopic "Firmware File Error Message" Firmware File Error Message\}
\p\p
\{\3\subtopic "Firmware Upgrade Takes A Long Time" Firmware Upgrade Takes A Long Time\}
\p\p
\{\3\subtopic "No Compatible Firmware Files/Versions Are Displayed" No Compatible Firmware Files/Versions Are Displayed\}
\p\p\1
Related Topics\0\p
\{\3\goto "Firmware/NVSRAM Questions" Common Questions\} \p
\{\3\goto "Firmware Concept" Firmware\} \p
\{\3\goto "How To Download A New NVSRAM File" How To Download A New NVSRAM File\} \p
\{\3\goto "How To Use Firmware Upgrade" How To Use Firmware Upgrade\} \p
\{\3\goto "NVSRAM Concept" NVSRAM\} \p
\{\3\goto "Firmware/NVSRAM Restrictions" Restrictions/Cautions\} \p
\{\3\goto "Troubleshooting Topics" Troubleshooting\} \p
\keyword "controller firmware" \keyword "firmware" \keyword "NVSRAM" \keyword "troubleshooting"

\topic "Can't De-Select The Fibre Channel File" \p\1
Can't De-Select The Fibre Channel Level File
\p\p
Cause \0 -- You cannot de-select the \{\2\bring_popup "Fibre Channel Level" fibre channel\} code if it appears in the Compatible Files/Versions screen (under the Fibre Channel Level (FC) column). Fibre channel firmware code, when available, is part of the firmware upgrade package and is displayed in this screen (in the FC column). When you select files that also contain a fibre channel file, the FC file also is downloaded along with the \{\2\bring_popup "Firmware Level" appware\} and \{\2\bring_popup "Boot Level" bootware\} files. However, the fibre channel code is ignored unless the module's controllers are fibre channel ready.
\p\p\1
Action \0 -- It is safe to proceed with a firmware upgrade when you see a fibre channel file.
\p\p\1
Related Topics\0\p
\{\3\goto "Fibre Channel Concept" Fibre Channel\} \p
\{\3\goto "Firmware/NVSRAM Troubleshooting" Firmware/NVSRAM Troubleshooting\} \p
\{\3\goto "Troubleshooting Topics" Troubleshooting\} \p
\keyword "controller firmware" \keyword "firmware" \keyword "fibre channel" \keyword "file selection" \keyword "Firmware Upgrade" \keyword "fibre channel firmware level"

\topic "Firmware File Error Message" \p\1
Firmware File Error Message
\p\p
Cause \0 -- You might see a "Firmware File Error" message after selecting firmware files to download to the controller. This message means that the selected files are not firmware files or are corrupted.
\p\p\1
Action \0 -- Perform one of the following steps:
\p\p
\{\1 o \0\} Select Cancel to exit Firmware Upgrade without performing any procedure. Obtain a new copy of the desired firmware release and begin the firmware upgrade procedure again.
\p\p
\{\1 o \0\} Select OK to return to the "select files for downloading" box again. Try selecting a new file. If that does not work, exit Firmware Upgrade, obtain a new copy of the desired firmware release, and begin this procedure again.
\p\p\1
Related Topics\0\p
\{\3\goto "Firmware/NVSRAM Troubleshooting" Troubleshooting\} \p
\keyword "controller firmware" \keyword "firmware" \keyword "file error" \keyword "error detection" \keyword "Firmware Upgrade" \keyword "results"

\topic "Firmware Upgrade Takes A Long Time" \p\1
Firmware Upgrade Takes A Long Time \p\p\0
If you select the Maintenance/Tuning Application >> All RAID Modules >> Firmware Upgrade, the process takes approximately 2 minutes per module to upgrade two controllers. Therefore, if you select All RAID Modules and you have 8 modules, the upgrade process takes approximately 16 minutes.
\p\p\1
Related Topics\0\p
\{\3\goto "Firmware/NVSRAM Troubleshooting" Troubleshooting\} \p
\{\3\goto "How To Download A New NVSRAM File" How To Download A New NVSRAM File\} \p
\{\3\goto "How To Use Firmware Upgrade" How To Use Firmware Upgrade\} \p
\keyword "time" \keyword "controller firmware" \keyword "firmware" \keyword "Firmware Upgrade" \keyword "delay"

\topic "No Compatible Firmware Files/Versions Are Displayed" \p\1
No Compatible Firmware Files/Versions Are Displayed \label "nofirmtop"
\p\p
Fast Find -- \{\5\goto "nofirmrt" Related Topics\}
\1\p\p
Cause \0 -- If the area under Compatible Files/Versions is blank after you select the Online or Offline method (Maintenance/Tuning Application >> Firmware Upgrade), then the current directory does not contain ALL the necessary firmware files. Remember that the software searches the default \{\2\bring_popup "Subdirectory, Firmware" subdirectory\} in the \{\2\bring_popup "Installation Directory" installation\} installation directory for the firmware files and the \{\2\bring_popup "fwcompat.def File" fwcompat.def\} file. (See the "Installation and Support Guide" specific to your operating system for installation directory information.)
\p\p\1
Action -- \0\p\p
1. Make sure the correct directory is selected. If you copied the files to some directory other than the default directory, enter that directory on the Path line.
\p\p
2. Recopy the firmware files and the fwcompat.def file to the correct subdirectory in the installation directory and try the firmware upgrade process again.
\p\p
It is recommended that the version line you select has both \{\2\bring_popup "Firmware Level" Firmware\} Level and \{\2\bring_popup "Boot Level" Boot\} Level versions specified.
\p\p\1
NOTE\0: You may also see \{\2\bring_popup "Fibre Channel Level" Fibre Channel\} Level (FC). When you highlight a line with FC code, it is downloaded with the appware and bootware files. However, the fibre channel code is ignored unless the module's controllers are fibre channel ready.
\p\p
3. If the upgrade fails a second time, obtain a new copy of the firmware upgrade files.
\p\p\1
Related Topics\0\label "nofirmrt"\p
\{\3\goto "Firmware/NVSRAM Troubleshooting" Troubleshooting\} \p
\{\3\goto "How To Download A New NVSRAM File" How To Download A New NVSRAM File\} \p
\{\3\goto "How To Use Firmware Upgrade" How To Use Firmware Upgrade\}
\p\p
\{\7\goto "nofirmtop" Top Of Page\} \p
\keyword "firmware" \keyword "controller firmware" \keyword "missing files" \keyword "version, controller firmware" \keyword "fwcompat.def file" \keyword "Firmware Upgrade"

\topic "Locate Module Troubleshooting" \p\1
Locate Module Troubleshooting \0\p\p
\{\3\subtopic "Locate Module Takes A Long Time" Locate Module Takes A Long Time\}
\p\p
\{\3\subtopic "Locate Module Doesn't Work" Locate Module Doesn't Work\}
\p\p\1
Related Topics \0\p
\{\3\goto "How To Use Locate Module" How To Use Locate Module\} \p
\{\3\goto "Locate Module Restrictions" Restrictions/Cautions\} \p
\{\3\goto "Troubleshooting Topics" Troubleshooting\} \p
\keyword "Locate Module" \keyword "troubleshooting"

\topic "Locate Module Takes A Long Time" \p\1
Locate Module Takes A Long Time
\p\p
Cause\0 -- If you have heavy I/O or are currently making configuration changes, you might notice a delay when you select Locate Module.
\p\p\1
Action\0 -- For best results, perform this task when no I/O activity is occurring on the selected RAID Module.
\p\p\1
Related Topics \0\p
\{\3\goto "How To Use Locate Module" How To Use Locate Module\} \p
\{\3\goto "Locate Module Troubleshooting" Troubleshooting\} \p
\keyword "Locate Module" \keyword "time" \keyword "activity lights" \keyword "lights" \keyword "delay"

\topic "Locate Module Doesn't Work" \p\1
Locate Module Doesn't Work
\p\p
Cause\0 -- Locate Module may not help you identify a RAID Module under two conditions: \p\p
\{\1 o \0\} If All RAID Modules is selected, this option is grayed out.
\p\p
\{\1 o \0\} If all logical units involved have a \{\2\bring_popup "Dead Mode" Dead\} status, the software cannot flash the lights on the drives. In this case, however, you can check for a fault light on the drive canisters (the light will be on, steady). Also, if the module has a summary activity indicator, it still flashes.
\p\p\1
NOTE\0: Any drives with a status other than Optimal are skipped and their activity lights do not flash.
\p\p\1
Action \0 -- Reselect a single RAID Module and try this option again, or select Recovery Guru/Health Check >> Show Procedures for action to take to correct any component problems.
\p\p\1
Related Topics \0\p
\{\3\goto "How To Use Locate Module" How To Use Locate Module\} \p
\{\3\goto "Locate Module Troubleshooting" Troubleshooting\} \p
\keyword "modules, locating" \keyword "finding modules" \keyword "Locate Module" \keyword "activity lights" \keyword "lights"

\topic "LUNs Are Marked As Inaccessible" \p\1
LUN ASSIGNMENT TROUBLESHOOTING
\p\p
Logical Units Are Marked As Inaccessible \label "luninaccesstop" 
\p\p
Fast Find -- \{\5\goto "luninaccessrt" Related Topics\} \p\p
Cause\0 -- You will see the \{\2\bring_popup "Inaccessible" Inaccessible\} status if the \{\2\bring_popup "RAID Module" RAID Module\} has an \{\2\bring_popup "Independent Controller Configuration" independent\} controller configuration. Neither the controller nor the LUNs marked Inaccessible can be accessed using this software from the host displaying the Inaccessible status. \p\p
\{\1 o \0\} For \{\2\bring_popup "Logical Unit" LUNs\}, this status indicates that the LUN is not available because it is part of a \{\2\bring_popup "Configured Drive Group" drive group\}/LUN owned by the alternate controller. \p\p
\{\1 o \0\} For a \{\2\bring_popup "Controller" controller\}, this status indicates that it is the alternate controller in an independent controller configuration. \p\p\1
Action\0 -- If you need to perform an operation on this drive group/LUN, you need to use the storage management software on the host machine connected to the controller that owns that drive group. \p\p
You can verify a RAID Module is using the independent controller configuration by viewing the Select Module main screen. It will show Yes in the "Indep. Cntrls?" column for that RAID Module.
\p\p\1
Related Topics \label "luninaccessrt"\0\p
\{\3\goto "LUN Assignment Questions" Common Questions\} \p
\{\3\goto "Host-RAID Module Configuration Types Supported Concept" Host-RAID Module Configuration Types Supported\} \p
\{\3\goto "How To Edit Module Information" How To Edit Module Information\} \p
\{\3\goto "How To Use LUN Balancing" How To Use LUN Balancing\} \p
\{\3\goto "LUN Assignment Concept" LUN Assignment\} \p
\{\3\goto "LUN Assignment Restrictions" Restrictions/Cautions\} \p
\{\3\goto "Troubleshooting Topics" Troubleshooting\}
\p\p
\{\7\goto "luninaccesstop" Top Of Page\}\p
\keyword "independent controller configuration" \keyword "Inaccessible" \keyword "LUN balancing" \keyword "controller, LUNs owned"

\topic "Message Log Troubleshooting" \p\1
Message Log Troubleshooting \0\p\p
\{\3\subtopic "Can't Find The Default Log File" Can't Find The Default Log File\}
\p\p
\{\3\subtopic "Default Log Has Exceeded Maximum Size Message" Default Log Has Exceeded The Maximum Size Message\}
\p\p
\{\3\subtopic "Log File Is Corrupted Message" Log File Is Corrupted Message\}
\p\p
\{\3\subtopic "No Match Found Message" No Match Found Message\}
\p\p
\{\3\subtopic "Selection Is Not A File Message" Selection Is Not A File Message\}
\p\p
\{\3\subtopic "Takes A Long Time To Display Or Refresh Message Log" Takes A Long Time To Display Or Refresh Message Log\}
\p\p
\{\3\subtopic "Unexpected Information In Message Log" What If I Do Not See Information I Expect In Message Log?\}
\p\p\1
Related Topics\0\p
\{\3\goto "Message Log Questions" Common Questions\} \p
\{\3\goto "How To Use Message Log" How To Use Message Log\} \p
\{\3\goto "Message Log Restrictions" Restrictions/Cautions\} \p
\{\3\goto "Troubleshooting Topics" Troubleshooting\} \p
\keyword "troubleshooting" \keyword "Message Log"

\topic "Can't Find The Default Log File" \p\1
Can't Find The Default Log File \label "nologtop"
\p\p
Fast Find -- \{\5\goto "nologrt" Related Topics\}
\1\p\p
Cause\0 -- When you select Message Log, the file that appears is the one designated as the \{\2\bring_popup "Log File" default\} log file (as set in Options >> Log Settings). However, you could see a message that the default log file was not found if the file has been deleted but is still entered as the default in Log Settings. \p\p\1
Action\0 -- If you see this message, you are also asked if you want the software to create a log file. \p\p
\{\1 o \0\} If you select OK, an empty log file is created using the default log's filename (rmlog.log). \p\p
\{\1 o \0\} If you select NO, you exit Message Log. Select a different \{\2\bring_popup "RAID Module" RAID Module\} and/or another Status option. \p\p\1
IMPORTANT \0\p
The software creates the default log file again the next time the software writes messages to this file. If you want to rename the default log file, change this parameter using Options >> Log Settings.
\p\p\1
Related Topics \label "nologrt"\0\p
\{\3\goto "How To Change Message Log's Settings" How To Change Message Log's Settings\} \p
\{\3\goto "How To Use Message Log" How To Use Message Log\} \p
\{\3\goto "Message Log Restrictions" Restrictions/Cautions\} \p
\{\3\goto "Message Log Troubleshooting" Troubleshooting\}
\p\p
\{\7\goto "nologtop" Top Of Page\} \p
\keyword "default log" \keyword "log file" \keyword "file selection" \keyword "Message Log" \keyword "settings"

\topic "Default Log Has Exceeded Maximum Size Message" \p\1
Default Log Has Exceeded The Maximum Size Message \label "logsizetop"
\p\p
Fast Find -- \{\5\goto "logsizert" Related Topics\}
\1\p\p
Cause\0 -- The default \{\2\bring_popup "Log File" log\} file has exceeded the specified maximum message log size \{\2\bring_popup "Maximum Message Log Size" value\}. \p\p\1
Action\0 -- The software saves the file as rmlog.<hostname>_001. If this file already exists, you get a message asking if you would like to overwrite the existing file. Selecting No causes the log to be saved to a new file named rmlog.<hostname>_00x, (where x is the next available number; this number is given in the message). When the file is saved, the contents of the current file are deleted, except for an entry indicating that the original log has been saved to the new filename. \p\p\1
Related Topics \label "logsizert"\0\p
\{\3\goto "How To Change Message Log's Settings" How To Change Message Log's Settings\} \p
\{\3\goto "How To Save The Log As Another File" How To Save The Log As Another File Name\} \p
\{\3\goto "Message Log Restrictions" Restrictions/Cautions\} \p
\{\3\goto "Message Log Troubleshooting" Troubleshooting\}
\p\p
\{\7\goto "logsizetop" Top Of Page\} \p
\keyword "Message Log" \keyword "log file" \keyword "default log" \keyword "log size" \keyword "size, maximum log" \keyword "maximum log size" \keyword "file size exceeded" \keyword "message, maximum log size exceeded"

\topic "Log File Is Corrupted Message" \p\1
Log File Is Corrupted Message \p\p
Cause\0 -- If you see the "Log file is corrupted" message, it could mean either that the file is bad or that you have not selected an appropriate log file. \p\p\1
Action\0 -- Try selecting the log file again. 
\p\p\1
Related Topics\0\p
\{\3\goto "How To Open A Log File" How To Open An Existing Log File\} \p
\{\3\goto "Message Log Troubleshooting" Troubleshooting\} \p
\keyword "log file" \keyword "Corrupted File message" \keyword "message, log file corrupted" \keyword "Message Log" \keyword "file corrupted"

\topic "No Match Found Message" \p\1
No Match Found Message \p\p
Cause\0 -- This message can appear in Message Log: \p\p
\{\1 o \0\} Instead of a \{\2\bring_popup "Log File" log\} file being displayed, or \p\p
\{\1 o \0\} For a specific \{\2\bring_popup "RAID Module" RAID Module\} if you select All RAID Modules. \p\p
This message means that the RAID Module no longer exists or is no longer connected to the host system (the software cannot detect it). \p\p\1
Action\0 -- Check to be sure that the selected module is connected. If the RAID Module is one that no longer exists, select another module. 
\p\p\1
Related Topics\0\p
\{\3\goto "How To Use Select Module" How To Use Select Module\} \p
\{\3\goto "Message Log Restrictions" Restrictions/Cautions\} \p
\{\3\goto "Message Log Troubleshooting" Troubleshooting\} \p
\keyword "No Match Found message" \keyword "message, no match found" \keyword "Message Log" \keyword "log file" \keyword "missing files"

\topic "Selection Is Not A File Message" \p\1
Selection Is Not A File Message \p\p
Cause\0 -- This message indicates that the filename you entered is not valid. You might see this message: \p\p
\{\1 o \0\} In any application, when you are saving a module profile (File >> Save Module Profile), \p\p
\{\1 o \0\} In the Status Application >> Message Log, when you are opening a log file or saving the log as another file, or \p\p
\{\1 o \0\} In the Status Application >> Performance Monitor, when you are saving performance data.
\p\p\1
Action\0 -- Try again, using another filename. Also, be sure that you are entering the filename on the Selection line and not the \{\2\bring_popup "Filter" Filter\} line (UNIX).
\p\p\1
Related Topics\0\p
\{\3\goto "How To Open A Log File" How To Open An Existing Log File\} \p
\{\3\goto "How To Save The Log As Another File" Saving The Message Log As Another File Name\} \p
\{\3\goto "How To Use File >> Save Performance Data" Saving Performance Monitor Data\} \p
\{\3\goto "Message Log Restrictions" Restrictions/Cautions\} \p
\{\3\goto "Message Log Troubleshooting" Troubleshooting\} \p
\keyword "message, selection is not a file" \keyword "Selection Is Not A File message" \keyword "file selection" \keyword "selecting files" \keyword "save" \keyword "Message Log" \keyword "Performance Monitor"

\topic "Takes A Long Time To Display Or Refresh Message Log" \p\1
Takes A Long Time To Display Or Refresh Message Log \label "mlogtimetop"
\p\p
Fast Find -- \{\5\goto "mlogtimert" Related Topics\}
\1\p\p
Cause\0 -- Normally, when you select Message Log or Options >> Refresh All (to update the \{\2\bring_popup "Log File" log\}), you should see the display in a few seconds. However, if the log file is very large, you might notice a delay. \p\p\1
NOTE\0: If your default log file is large, you could notice a delay when starting the Status Application because Message Log shows this file for All RAID Modules (the default selection) unless the Select Module screen appears first. \p\p\1
Action\0 -- Reduce the size of the log file or select a new default log file: \p\p
\{\1 o \0\} Change the default log file so that future events are written to this new log. From the top menu, select Options >> Log Settings. \p\p
\{\1 o \0\} Save the log file to another filename. From the top menu, select File >> Save Log As. You must then delete the contents of the current log file to reduce its size. 
\p\p\1
Related Topics \label "mlogtimert"\0\p
\{\3\goto "How To Change Message Log's Settings" How To Change Message Log's Settings\} \p
\{\3\goto "How To Refresh Message Log" How To Refresh Message Log\} \p
\{\3\goto "How To Save The Log As Another File" How To Save The Log As Another File Name\} \p
\{\3\goto "Message Log Restrictions" Restrictions/Cautions\} \p
\{\3\goto "Message Log Troubleshooting" Troubleshooting\}
\p\p
\{\7\goto "mlogtimetop" Top Of Page\} \p
\keyword "Message Log" \keyword "refresh" \keyword "time" \keyword "update screen" \keyword "screen update" \keyword "settings" \keyword "log size" \keyword "delay"

\topic "Unexpected Information In Message Log" \p\1
What If I Do Not See Information I Expect In Message Log? \label "unexpectlogtop"\p\p
Fast Find -- \{\5\goto "nomsg" No Messages\} | \{\5\goto "unexpectlogrt" Related Topics\}
\p\p\1
What Message Log Normally Displays \0\p\p
Any time you leave and return to Message Log, you see: \p\p
\{\1 o \0\} All message types displayed (the default setting is All) \p\p
\{\1 o \0\} The default or most recently selected log file \p\p\1
IMPORTANT \0\p
You can change the log displayed by selecting (from the top menu) File >> Open Log. This new log continues to be displayed until the next time you use Open Log again or exit and re-select Status. Once you exit the Status Application and return, however, the default \{\2\bring_popup "Log File" log\} is displayed again. \p\p\1
What If No Messages Are Displayed? \label "nomsg"\p\p
Cause\0 -- If you do not see any messages displayed in Message Log, most likely your default log file is new or has been cleared recently. It could also mean that there are no messages for the \{\2\bring_popup "Message Types" message\} type you selected (from List Type), or for the RAID Module you selected. \p\p
Normally, no messages in the log indicates that no events have been detected, so nothing has changed, gone wrong, or been corrected. \p\p\1
Action\0 -- If you see this message and feel that an empty log is not possible, \p\p
\{\1 o \0\} Select List Type to be sure that All message types are selected. \p\p
\{\1 o \0\} Try selecting another module or All RAID Modules. \p\p
\{\1 o \0\} Check Current Log File at the bottom of the screen to verify that it matches the log file specified as the default in Log Settings. The default log is the file new messages are written to. \p\p
\{\1 o \0\} From the top menu, select File >> Open Log to view a different log file. \p\p
\{\1 o \0\} If these do not work, you may have other options specific to your operating system. \p\p
\{\3\subtopic "UNIX Options" UNIX Options\}
\p\p
\{\3\subtopic "Windows Options" Windows Options\}
\p\p\1
Related Topics \label "unexpectlogrt"\0\p
\{\3\goto "Message Log Questions" Common Questions\} \p
\{\3\goto "How To List Different Types Of Messages" How To List Different Types Of Messages\} \p
\{\3\goto "How To Use Message Log" How To Use Message Log\} \p
\{\3\goto "Message Log Restrictions" Restrictions/Cautions\} \p
\{\3\goto "Message Log Troubleshooting" Troubleshooting\}
\p\p
\{\7\goto "unexpectlogtop" Top Of Page\} \p
\keyword "log file" \keyword "Message Log" \keyword "unexpected information" \keyword "results" \keyword "missing information" \keyword "screen description" \keyword "no messages" \keyword "empty log" \keyword "current log file open"

\topic "UNIX Options" \p\1
UNIX Options \label "unixtop"
\p\p
Fast Find -- \{\5\goto "unixrt" Related Topics\}
\0\p\p
1. Check file permissions for the log file. Does root have read/write access to the file? \p\p
2. If the file does not exist, does root have read/write/execute access to the directory? \p
Execute access to a directory means the ability to get a directory listing. \p\p
3. Is the arraymon daemon actually running? \p
Type "ps -ef | grep array" to look for the process. \p\p
4. Does the script /etc/raid/bin/rmscript exist and have at least the "putplog $1" line? \p\p
5. Does root have read/execute privileges for /etc/raid/bin/rmscript file? \p\p
6. Does the executable /etc/raid/bin/putplog exist and have execute privileges?
\p\p\1
Related Topics \label "unixrt"\0\p
\{\3\goto "Message Log Troubleshooting" Troubleshooting\} \p
\{\3\goto "Unexpected Information In Message Log" What If I Do Not See Information I Expect In Message Log?\}
\p\p
\{\7\goto "unixtop" Top Of Page\} \p
\keyword "options, UNIX" \keyword "UNIX options" \keyword "Message Log"

\topic "Windows Options" \p\1
Windows Options \0\p\p
1. The user must be logged on as an administrator to run the software and to have access to the log files. \p\p
2. Is the array monitor service running? \p
Check the Control Panel -- Services to make sure that the "Array Monitor" service is started. \p\p
3. Does the file "rmscript.bat" exist in the directory where the software was installed? \p
Does it contain the "putplog %1" line somewhere? \p\p
4. Does the file "putplog.exe" exist in the software's directory? 
\p\p\1
Related Topics\0\p
\{\3\goto "Message Log Troubleshooting" Troubleshooting\} \p
\{\3\goto "Unexpected Information In Message Log" What If I Do Not See Information I Expect In Message Log?\} \p
\keyword "Message Log" \keyword "options, Windows" \keyword "Windows, options"

\topic "Module Profile Troubleshooting" \p\1
Module Profile Troubleshooting \0\p\p
\{\3\goto "Can Save Module Profile Restore My Configuration?" Can I Restore My Configuration With Save Module Profile Information?\}
\p\p
\{\3\subtopic "Controller Board Name Incomplete In Module Profile" Controller Board Name Is Incomplete In Module Profile >> Controllers\}
\p\p\1
Related Topics\0\p
\{\3\goto "How To Use Module Profile" How To Use Module Profile\} \p
\{\3\goto "Module Profile Restrictions" Restrictions/Cautions\} \p
\{\3\goto "Troubleshooting Topics" Troubleshooting\} \p
\keyword "Module Profile" \keyword "troubleshooting"

\topic "Controller Board Name Incomplete In Module Profile" \p\1
Controller Board Name Is Incomplete In Module Profile >> Controllers \0\p\p
The controller board names (both controllers A and B) are limited to 32 characters. If your controller board name is longer, you will see only the first 32 characters displayed in Module Profile.
\p\p\1
Related Topics\0\p
\{\3\goto "How To Use Module Profile" How To Use Module Profile\} \p
\{\3\goto "Module Profile Troubleshooting" Troubleshooting\} \p
\keyword "screen description" \keyword "Module Profile" \keyword "missing information" \keyword "controller information"

\topic "Online Help Troubleshooting" \p\1
Help Troubleshooting \0\p\p
\{\3\subtopic "Print From Help Failed" Top Menu File >> Print Topic Option Failed\}
\p\p
\{\3\subtopic "Can't Access Online Help" Can't Access Online Help\}
\p\p
\{\3\subtopic "Help Files Are Missing Or Corrupted Message" Help Files Are Missing Or Corrupted Message\}
\p\p\1
Related Topics \0\p
\{\3\goto "How To Use Online Help" How To Use Online Help\} \p
\{\3\goto "Troubleshooting Topics" Troubleshooting\} \p
\keyword "help" \keyword "online help" \keyword "using help" \keyword "troubleshooting"

\topic "Print From Help Failed" \p\1
Top Menu File >> Print Topic Option Failed \label "troublehelptop"
\p\p
Fast Find -- \{\5\goto "troublehelprt" Related Topics\}
\1\p\p
Cause\0 -- An Error Window appears. Most likely you do not have a default printer defined or did not provide the full path name for the print file.
\p\p\1
Action\0 -- Do one of the following, depending on whether you selected Send to Printer or Write to File: \p\p\1
If you selected Send to Printer\0: \p\p
1. Select OK in the Error Window.
\p\p
2. Define a default printer (refer to your operating system documentation if needed).
\p\p
3. Re-select Help and try to print again.
\p\p\1
If you selected Write to File\0: \p\p
1. Select OK in the Error Window.
\p\p
2. Re-select File >> Print Topic.
\p\p
3. Specify the full path name (on your local filesystem) for the print file before selecting OK.
\p\p\1
Related Topics \0\label "troublehelprt"\p
\{\3\goto "How To Use Online Help" How To Use Online Help\} \p
\{\3\goto "Online Help Troubleshooting" Troubleshooting\}
\p\p
\{\7\goto "troublehelptop" Top Of Page\} \p
\keyword "printing" \keyword "help" \keyword "online help" \keyword "using help"

\topic "Can't Access Online Help" \p\1
Can't Access Online Help
\p\p
Cause\0 -- You cannot open Help with the current option selected.
\p\p\1
Action\0 -- You have two options: \p\p
\{\1 o \0\} Exit the option you are in, select Help and position the topic you want to refer to in the window. Then, select that option again.
\p\p
\{\1 o \0\} You can select Help from another application because you can access ALL of the help topics from any application's help.
\p\p\1
Related Topics \0\p
\{\3\goto "How To Use Online Help" How To Use Online Help\} \p
\{\3\goto "Online Help Troubleshooting" Troubleshooting\} \p
\keyword "access denied" \keyword "help" \keyword "online help" \keyword "using help" \keyword "missing help" \keyword "No Help message"

\topic "Help Files Are Missing Or Corrupted Message" \p\1
Help Files Are Missing Or Corrupted Message
\p\p
Action\0 -- Check that the correct Help files are installed in the \{\2\bring_popup "Installation Directory" installation directory\} (if needed, open the rmparams file and check the parameter "Help_Files_Directory=" for the name of the subdirectory). You should have two help files: symhelp.txt and glossary.txt. Re-install them if necessary.
\p\p\1
Related Topics \0\p
\{\3\goto "How To Use Online Help" How To Use Online Help\} \p
\{\3\goto "Online Help Troubleshooting" Troubleshooting\} \p
\keyword "help" \keyword "using help" \keyword "online help" \keyword "missing files" \keyword "file corrupted" \keyword "Corrupted File message" \keyword "message, help missing or corrupted" \keyword "rmparams file"

\topic "Parity Troubleshooting" \p\1
Parity Troubleshooting \0\p\p
\{\3\subtopic "Parity Check/Repair Takes A Long Time" Parity Check/Repair Takes A Long Time\}
\p\p
\{\3\subtopic "Manual Parity Check/Repair Terminated Message" Manual Parity Check/Repair Terminated Message\}
\p\p\1
Related Topics\0\p
\{\3\goto "Parity Questions" Common Questions\} \p
\{\3\goto "How To Use Manual Parity Check/Repair" How To Manually Check Parity\} \p
\{\3\goto "How To Use Options >> Auto Parity Settings" How To Automatically Check Parity\} \p
\{\3\goto "Parity Concept" Parity\} \p
\{\3\goto "Parity Restrictions" Restrictions/Cautions\} \p
\{\3\goto "Troubleshooting Topics" Troubleshooting\} \p
\{\3\goto "Viewing Parity Messages" Viewing Parity Messages\} \p
\keyword "parity" \keyword "troubleshooting"

\topic "Parity Check/Repair Takes A Long Time" \p\1
Parity Check/Repair Takes A Long Time \p\p
Cause \0 -- How long parity check/repair takes depends on your I/O load, the number and size of the \{\2\bring_popup "Logical Unit" logical units\} you have selected, the number of parity errors it finds, and on whether it is set to correct those errors. For example, parity check/repair for a 1 GB logical unit takes approximately two minutes. (When you start the manual parity operation, you may notice some performance slow-down for other applications you are running.)
\p\p\1
Action \0 -- Run manual parity on a few logical units at a time, when I/O is not heavy on the selected RAID Module, or with repair turned off.
\p\p\1
NOTE\0: If you are running the automatic parity check/repair operation every day and you notice it taking a long time or overlapping another parity check/repair, you may want to try running the check once a week. Select Maintenance/Tuning Application >> Options >> Auto Parity Settings and choose a specific day of the week.
\p\p\1
Related Topics\0\p
\{\3\goto "Parity Troubleshooting" Troubleshooting\} \p
\{\3\goto "How To Use Options >> Auto Parity Settings" How To Use Options >> Auto Parity Settings\} \p \keyword "parity" \keyword "check parity" \keyword "repair parity" \keyword "automatic parity" \keyword "manual parity" \keyword "time" \keyword "overlapping parity checks" \keyword "daily parity check" \keyword "weekly parity check" \keyword "delay"

\topic "Manual Parity Check/Repair Terminated Message" \p\1
Manual Parity Check/Repair Terminated Message \p\p
Cause \0 -- Remember that the LUNs must be \{\2\bring_popup "Optimal Mode" Optimal\} in order to perform this check. This message indicates that the parity check/repair operation has been aborted. This most likely occurs if the affected LUN has changed to a status other than Optimal.
\p\p\1
Action \0 -- Select Recovery Application >> Recovery Guru/Health Check for the RAID Module. If any component problems are detected, highlight the failure type, select Show Procedures, and use the steps provided to correct the problem. You may want to run the Manual Parity Check/Repair operation again.
\p\p\1
Related Topics\0\p
\{\3\goto "How To Use Manual Parity Check/Repair" How To Manually Check Parity\} \p
\{\3\goto "Parity Troubleshooting" Troubleshooting\} \p
\keyword "parity" \keyword "manual parity" \keyword "terminated parity check"

\topic "Performance Monitor Troubleshooting" \p\1
Performance Monitor Troubleshooting \0\p\p
\{\3\subtopic "Can't Select All Controllers In Performance Monitor" All Of My Controllers Or LUNs Are Not Available For Selection In Performance Monitor\}
\p\p
\{\3\subtopic "The Monitoring Process Has Been Stopped Message" The Monitoring Process Has Been Stopped Message Displays When Using Performance Monitor\}
\p\p
\{\3\goto "Selection Is Not A File Message" Selection Is Not A File Message\}
\p\p\1
Related Topics\0\p
\{\3\goto "Performance Monitor Questions" Common Questions\} \p
\{\3\goto "How To Use Performance Monitor" How To Use Performance Monitor\} \p
\{\3\goto "Performance Concept" Performance\} \p
\{\3\goto "Performance Monitor Restrictions" Restrictions/Cautions\} \p
\{\3\goto "Troubleshooting Topics" Troubleshooting\} \p
\keyword "Performance Monitor" \keyword "troubleshooting"

\topic "Can't Select All Controllers In Performance Monitor" \p\1
All Of My Controllers Or LUNs Are Not Available For Selection In Performance Monitor \p\p
Cause\0 -- If a \{\2\bring_popup "Controller" controller\} or \{\2\bring_popup "Logical Unit" LUN\} is in a \{\2\bring_popup "Dead Mode" Dead\} state before you start Performance Monitor (Status Application), it does not appear in the Select Controllers/LUNs box. \p\p\1
Action\0 -- Use Recovery Guru/Health Check (Recovery Application) to diagnose the problem, then select Show Procedure for step-by-step instructions to correct it. \p\p\1
Related Topics\0\p
\{\3\goto "How To Use Recovery Guru" How To Use Recovery Guru/Health Check\} \p
\{\3\goto "Performance Monitor Troubleshooting" Troubleshooting\} \p
\keyword "Performance Monitor" \keyword "selecting controllers" \keyword "controllers, displayed"

\topic "The Monitoring Process Has Been Stopped Message" \p\1
The Monitoring Process Has Been Stopped Message Is Displayed While When Using Performance Monitor \p\p
Cause\0 -- This message could be displayed for two reasons: \p\p
\{\1 o \0\} Another user has started Performance Monitor (Status Application) on the \{\2\bring_popup "RAID Module" RAID Module\} that you are currently monitoring, or \p\p
\{\1 o \0\} The display capacity of the Performance Monitor has been reached. \p\p\1
Action\0 -- \p\p
\{\1 o \0\} Make sure no other users are using Performance Monitor, and begin the process again. \p\p
\{\1 o \0\} If the display capacity has been reached, you must restart Performance Monitor (you may want to save the data in the current display using File >> Save Performance Data).
\p\p\1
Related Topics\0\p
\{\3\goto "How To Use File >> Save Performance Data" Saving Performance Monitor Data\} \p
\{\3\goto "Performance Monitor Troubleshooting" Troubleshooting\} \p
\keyword "Performance Monitor" \keyword "monitoring data stopped" \keyword "capacity" \keyword "display capacity" \keyword "terminated performance monitoring"

\topic "Reconstruction Troubleshooting" \p\1
Reconstruction Troubleshooting \0\p\p
\{\3\subtopic "Can't Change The Rate For All LUNs" Can't Change The Reconstruction Rate For All LUNs\}
\p\p
\{\3\subtopic "Error Message When Trying To Change The Rate" Error Message Is Displayed When Trying To Change The Reconstruction Rate\}
\p\p
\{\3\subtopic "Reconstruction Takes A Long Time" Reconstruction Takes A Long Time\}
\p\p\1
Related Topics\0\p
\{\3\goto "Manually Starting Reconstruction" Common Questions\} \p
\{\3\goto "How To Change The Reconstruction Rate" How To Change The Reconstruction Rate\} \p
\{\3\goto "How To View Reconstruction Progress" How To View Reconstruction Progress\} \p
\{\3\goto "Reconstruction Concept" Reconstruction\} \p
\{\3\goto "Reconstruction Restrictions" Restrictions/Cautions\} \p
\{\3\goto "Troubleshooting Topics" Troubleshooting\} \p
\keyword "reconstruction" \keyword "troubleshooting"

\topic "Can't Change The Rate For All LUNs" \p\1
Can't Change The Reconstruction Rate For All LUNs
\p\p
Cause \0 -- If you are using the Status Application, you can only change the \{\2\bring_popup "Reconstruction Rate" reconstruction rate\} for logical units (LUN) that are currently reconstructing. If a LUN shows "Waiting to reconstruct," you will be able to change its rate when the reconstruction operation begins.
\p\p\1
Action \0 -- Use LUN Reconstruction Rate in the Maintenance/Tuning Application to change the rate for all logical units, whether they are reconstructing or not.
\p\p\1
Related Topics\0\p
\{\3\goto "How To Change The Reconstruction Rate" How To Change The Reconstruction Rate\} \p
\{\3\goto "Reconstruction Troubleshooting" Troubleshooting\} \p
\keyword "rate" \keyword "reconstruction"

\topic "Error Message When Trying To Change The Rate" \p\1
Error Message Is Displayed When Trying To Change The Reconstruction Rate
\p\p
Cause \0 -- If a RAID Module has an \{\2\bring_popup "Independent Controller Configuration" independent\} controller configuration, do not try to change the \{\2\bring_popup "Reconstruction Rate" reconstruction rate\} for LUNs marked Inaccessible. Although you can move the rate setting, the rate is not changed and error messages will be displayed.
\p\p\1
Action \0 -- Use the storage management software on the host machine connected to the controller that owns the affected LUNs if you want to change their reconstruction rate. You can verify which LUNs a controller owns using Module Profile.
\p\p\1
Related Topics\0\p
\{\3\goto "Host-RAID Module Configuration Types Supported Concept" Host-RAID Module Configuration Types Supported\} \p
\{\3\goto "How To Use Module Profile" How To Use Module Profile\} \p
\{\3\goto "Reconstruction Troubleshooting" Troubleshooting\} \p
\keyword "reconstruction" \keyword "rate" \keyword "settings" \keyword "changing settings" \keyword "Inaccessible" \keyword "independent controller configuration"

\topic "Reconstruction Takes A Long Time" \p\1
Reconstruction Takes A Long Time
\p\p
Cause \0 -- The amount of time that \{\2\bring_popup "Reconstruction" reconstruction\} takes depends on the number and size of the logical units that may be reconstructing and on the rate setting for the reconstruction operation.
\p\p\1
Action \0 -- Consider changing the \{\2\bring_popup "Reconstruction Rate" reconstruction rate\} to better optimize reconstruction. Use LUN Reconstruction in the Status Application to change the rate setting while reconstruction is occurring.
\p\p\1
Related Topics\0\p
\{\3\goto "Reconstruction Troubleshooting" Troubleshooting\} \p
\keyword "reconstruction" \keyword "time" \keyword "delay"

\topic "Can Save Module Profile Restore My Configuration?" \p\1
SAVE MODULE PROFILE TROUBLESHOOTING
\p\p\1
Can Save Module Profile Restore My Configuration? \label "savetrbltop"\p\p
Fast Find -- \{\5\goto "savetrblrt" Related Topics\}
\p\p\0
No. You cannot use this information to automatically restore a \{\2\bring_popup "RAID Module" RAID Module's\} configuration; however, Save Module Profile copies the information found in Module Profile and on the Configuration Application's main screen to a file for your reference. Using this file, you could determine the specifics of a module's configuration. Once you saved the profile, you can print it using the printer utility available on your system. \p\p\1
IMPORTANT \0\p
You should save a module's profile to a file when you first install it and any time you change your configuration. You can use this information if you need to perform any recovery or maintenance tasks. Also, this file is useful when you want a copy for quick reference, if you want a permanent record, or if you want to send information to your Customer Services Representative for troubleshooting. \p\p\1
Related Topics \label "savetrblrt"\0\p
\{\3\goto "How To Use File >> Save Module Profile" How To Use File >> Save Module Profile\} \p
\{\3\goto "Troubleshooting Topics" Troubleshooting\} \p
\{\3\goto "Information In Configuration" What Information Appears In The Configuration Application?\}
\p\p
\{\7\goto "savetrbltop" Top Of Page\} \p
\keyword "troubleshooting" \keyword "save" \keyword "module information" \keyword "configuration"

\topic "Select Module Screen Does/Doesn't Appear" \p\1
SELECT MODULE TROUBLESHOOTING \label "smodtrbltop"
\p\p
Select Module Screen Does/Doesn't Appear 
\p\p
Fast Find -- \{\5\goto "smodtrbl" Action\} | \{\5\goto "smodtrblrt" Related Topics\}
\p\p\1
Cause \0 -- The default setting determining whether the Select Module main screen appears every time you start an application varies according to the operating system version of the storage management software that you are using.
\p\p
You can change this default by editing the \{\2\bring_popup "rmparams File" rmparams\} file and changing the System_DefaultModuleSelect parameter: \p\p
\{\1 o \0\} TRUE means the screen will appear each time.
\p\p
\{\1 o \0\} FALSE means that it will NOT appear automatically.
\p\p\1
Important Notes \0\p\p
Consult the "Installation and Support Guide" for a more information on the rmparams file and a list of the options you might want to consider changing. However, most parameters should NOT be changed and many of the other options should only be changed through the graphical user interface (GUI).
\p\p
Because of the critical nature of the rmparams file, you should copy the rmparams file to a directory other than the \{\2\bring_popup "Installation Directory" installation\} directory before you make changes. If this file becomes corrupted or missing, you can copy the backup rmparams file to the installation directory to resume normal operation. Furthermore, if you make any changes to this file directly or use the options in the GUI that write to this file (such as log settings), always copy the new version of the file to the backup directory.
\p\p\1
Action -- \0\label "smodtrbl"\p\p
1. Change the System_DefaultModuleSelect parameter to the desired default: \p\p
-- TRUE means the screen will appear each time.
\p\p
-- FALSE means that it will NOT appear automatically.
\p\p
2. Save the rmparams file and copy it to the backup directory.
\p\p\1
Related Topics \0\label "smodtrblrt"\p
\{\3\goto "How To Use Select Module" How To Use Select Module\} \p
\{\3\goto "Troubleshooting Topics" Troubleshooting\}
\p\p
\{\7\goto "smodtrbltop" Top Of Page\} \p
\keyword "Select Module" \keyword "troubleshooting" \keyword "rmparams file"

\topic "Interface Topics" \p\1
Interface Description \label "interfacetop"
\p\p
Fast Find -- \{\5\goto "interfacert" Related Topics\}
\p\p\1
Main Screen Description \0\p\p
The main screen contains the following areas: \p\p
\{\3\subtopic "Top Menu Options" Top Menu Options\}
\p\p
\{\3\subtopic "RAID Module Selection/Tool Bar Area" RAID Module Selection And Tool Bar Area\}
\p\p
\{\3\subtopic "Dynamic Display Area" Dynamic Display Area\}
\p\p\1
Notes \0\p\p
\{\1 o \0\} There is also a status line at the bottom of the screen that provides information about each of the options. Also, when an option is grayed out, the status line provides an indication of why. To receive information about a particular option, move the mouse over the appropriate button. For top menu options, you must click on the option and hold down the left-mouse button.
\p\p
\{\1 o \0\} Also, in the Configuration Application's main screen, you can right-click the mouse on the devices in the Module Information area to get a menu of task options available for that device. For example, if you select a \{\2\bring_popup "Configured Drive Group" Group\} and right-click the mouse, you are able to select the following options: List/Locate Drives, Create LUN (if there is available group capacity), Modify Group/LUN, or Delete.
\p\p\1
Related Topics \0\label "interfacert" \p
\{\3\goto "How To Use Select Module" How To Use Select Module\} \p
\{\3\goto "Information In Configuration" What Information Appears In The Configuration Application?\}
\p\p
\{\7\goto "interfacetop" Top Of Page\} \p
\keyword "interface overview"
\keyword "screen description"

\topic "Top Menu Options" \p\1
Top Menu Options \label "menutop"
\p\p
Fast Find -- \{\5\goto "editmenu" Edit\} | \{\5\goto "modmenu" Module\} | \{\5\goto "optmenu" Options\} | \{\5\goto "menurt" Related Topics\}
\p\p\1
FILE TOP MENU SELECTIONS \0\label "filemenu"\p\p
This menu selection is available in all applications; however, the options vary in each.
\p\p\1
All Applications
\p\p\1
\{\1 o \} Save Module Profile \0\p
-- Save profile information to a file ONLY for the selected \{\2\bring_popup "RAID Module" RAID Module\}. Saving profile information copies the information found in Module Profile and the Configuration Application main screen to a file for your reference. It does not, however, copy configuration information that you could later use to restore your module.
\p\p
-- You cannot select this option while viewing Module Profile or if you select All RAID Modules.
\p\p\1
IMPORTANT \0\p
It is very important that you save the profile of each RAID Module during initial installation and any time you change your configuration. You can use this information as a reference if you need to perform any recovery or maintenance tasks.
\p\p\1
\{\1 o \} Exit \0\p
Quit the application you are in and return to the program group or startup screen.
\p\p\1
Configuration Application \label "filecfg"\p\p\1
\{\1 o \} Reset Configuration \0\p
Reset the RAID Module's \{\2\bring_popup "Configured Drive Group" drive groups\} and \{\2\bring_popup "Logical Unit" logical units\} back to a default configuration. Use this option ONLY as a last resort if your configuration is totally inaccessible or you want to start completely over.
\p\p\4
CAUTION \0\p
You will lose ALL data on the selected RAID Module when you reset the configuration.
\p\p\1
Status Application \label "filestat"\p\p\1
\{\1 o \} Open Log\0\p
-- View summary and detailed information for a selected \{\2\bring_popup "Log File" log file\}.
\p\p
-- Only active when you select Message Log.
\p\p
-- This only opens the log for viewing; it does not make this the default log where new incoming events/messages are stored. If you want to change the default log, use Options >> Log Settings.
\p\p\1
\{\1 o \} Save Log As \0\p
-- Save a selected message log to another file.
\p\p
-- Only active when you select Message Log.
\p\p\1
EDIT TOP MENU SELECTIONS \0\label "editmenu"\p\p
This menu selection is available ONLY in the Status Application.
\p\p\1
\{\1 o \} Copy To Clipboard \0\p
-- Copy the contents of a detailed message to the clipboard.
\p\p
-- Active in Message Log when you select Show Details.
\p\p\1
\{\1 o \} Select All \0\p
-- Select all the messages in the summary information screen or highlight the text of a detailed message so that you can copy that information.
\p\p
-- Active when you select Message.
\p\p\1
MODULE TOP MENU SELECTIONS \0\label "modmenu"\p\p
This menu selection is available in all applications.
\p\p\1
\{\1 o \} Select \0\p
Starts the Select Module option. Use this option to select or view information about a specific RAID Module; to add or remove modules in your system; or to change a module's information (module name, \{\2\bring_popup "Independent Controller Configuration" independent controllers\}, or comments area). This option is available from any application.
\p\p\1
\{\1 o \} Locate \0\p
Starts the Locate Module option. Use this option to physically locate and identify a specific RAID Module if you have several modules connected to your system. This option is available from any application.
\p\p\1
\{\1 o \} Profile \0\p
Starts the Module Profile option. Use this option to view specific details about the controllers, drives, or logical units for the selected RAID Module.
\p\p\1
OPTIONS TOP MENU SELECTIONS \0\label "optmenu"\p\p
This menu selection is available in all applications; however, the options vary in each.
\p\p\1
Status Application \0\p\p\1
\{\1 o \} Refresh All \0\p
-- Updates Message Log to show any new messages in the summary information area.
\p\p
-- Only active when you select Message Log.
\p\p
-- Selecting this option updates Message Log to include all message types (the default setting).
\p\p\1
\{\1 o \} Log Settings \0\p
-- You can select this option at all times to affect these Message Log settings.
\p\p
-- Changing any of these parameters affects ALL your RAID Modules.
\p\p
-- Change the default settings for three parameters: \p\p
1. \1 Default Log File \0 -- where incoming events/messages are stored; this is the log that is shown in Message Log when you first select it.
\p\p
2. \1 Maximum Message Log Size \0 -- sets the maximum size that the default log file can be before you receive notification that this \{\2\bring_popup "Maximum Message Log Size" value\} has been exceeded.
\p\p
3. \1 Check RAID Module Every X Minutes \0 -- controls the \{\2\bring_popup "Checking Interval" frequency\} at which the background monitor checks the RAID Modules.
\p\p\1
Recovery Application \p\p\1
\{\1 o \} Manual Recovery \0\p
-- Allows you to manually perform recovery procedures on drives, logical units, or controllers.
\p\p
-- If All RAID Modules is selected, this option is grayed out.
\p\p\1
Maintenance/Tuning Application \p\p\1
\{\1 o \} Auto Parity Settings \0\p
-- Enable or disable the automatic \{\2\bring_popup "Parity Check/Repair" parity\} check/repair operation, change the time at which it runs, and specify whether to automatically repair any errors found.
\p\p
-- You can select this option at all times when you are in the Maintenance/Tuning Application.
\p\p\1
Note\0:	You can also manually perform an immediate parity check/repair using the Recovery Application.
\p\p\1
Related Topics \0\label "menurt"\p
\{\3\goto "Copy To Clipboard" Copy To Clipboard\} \p
\{\3\goto "How To Use Options >> Auto Parity Settings" How To Automatically Check/Repair Parity\} \p
\{\3\goto "How To Change Message Log's Settings" How To Change Message Log's Settings\} \p
\{\3\goto "How To Open A Log File" How To Open An Existing Log File\} \p
\{\3\goto "How To Refresh Message Log" How To Refresh Message Log\} \p
\{\3\goto "How To Save The Log As Another File" How To Save The Log As Another File Name\} \p
\{\3\goto "How To Use File >> Save Module Profile" How To Save A Module Profile\} \p
\{\3\goto "How To Use Locate Module" How To Use Locate Module\} \p
\{\3\goto "How To Use Options >> Manual Recovery" How To Use Options >> Manual Recovery\} \p
\{\3\goto "How To Use Module Profile" How To Use Module Profile\} \p
\{\3\goto "How To Use Select Module" How To Use Select Module\} \p
\{\3\goto "When To Use File >> Reset Configuration" When Should I Use The Reset Configuration Option?\}
\p\p
\{\7\goto "menutop" Top Of Page\} \p
\keyword "menu options" \keyword "File menu" \keyword "Edit menu" \keyword "Options menu" \keyword "Module menu" \keyword "top menu items" \keyword "tasks, available from top menus" \keyword "summary of tasks" \keyword "task summary"

\topic "RAID Module Selection/Tool Bar Area" \p\1
RAID Module Selection And Tool Bar Area \label "tooltop"
\p\p
Fast Find -- \{\5\goto "toolcfg" Configuration\} | \{\5\goto "toolstat" Status\} | \{\5\goto "toolrecv" Recovery\} | \{\5\goto "toolmt" Maintenance/Tuning\} | \{\5\goto "toolrt" Related Topics\}
\p\p\0
This area appears below the top menu options and allows you to perform most of the tasks available in each application. For a complete list of options available, view the Options from the top menu.
\p\p\1
NOTE\0: There is also a status line at the bottom of the screen that provides information about each of the options. Also, when an option is grayed out, the status line provides an indication of why. To receive information about a particular option, move the mouse over the appropriate button. For top menu options, you must click on the option and hold down the left-mouse button.
\p\p\1
Common To All Applications \0\p\p\1
RAID Selection \0 -- The RAID Selection box appears to the left of the tool bar. This area displays the selected RAID Module by name and also provides a drop-down list for selecting another RAID Module.
\p\p\1
Tool Bar \0 -- An icon appears on the tool bar for each of the Module options (Select, Locate, and Profile). For a summary explanation of these, select the Module Top Menu Selections topic in the \{\5\goto "toolrt" Related Topics\} list below.
\p\p\1
Configuration Application \0\label "toolcfg"\p\p
A button appears following the module options on the tool bar for each of the tasks you can perform in Configuration (List/Locate Drives, Create LUN, Create Hot Spare, Modify Group/LUN, Delete). For details on these tasks, select the Configuration Application topic in the \{\5\goto "toolrt" Related Topics\} list below.
\p\p\1
Status Application \0\label "toolstat"\p\p
A button appears following the module options on the tool bar for each of the tasks you can perform in Status (Message Log, LUN Reconstruction, Performance Monitor). For details on these tasks, select the Status Application topic in the \{\5\goto "toolrt" Related Topics\} list below.
\p\p\1
Recovery Application \0\label "toolrecv"\p\p
A button appears following the module options on the tool bar for each of the tasks you can perform in Recovery (Recovery Guru/Health Check and Manual Parity Check/Repair). For details on these tasks, select the Recovery Application topic in the \{\5\goto "toolrt" Related Topics\} list below.
\p\p\1
Maintenance/Tuning Application \0\label "toolmt"\p\p
A button appears following the module options on the tool bar for each of the tasks you can perform in Maintenance/Tuning (LUN Reconstruction Rate, LUN Balancing, Controller Mode, Caching Parameters, and Firmware Upgrade). For details on these tasks, select the Maintenance/Tuning Application topic in the \{\5\goto "toolrt" Related Topics\} list below.
\p\p\1
Related Topics \0\label "toolrt"\p
\{\3\goto "Configuration Application" Configuration Application\} \p
\{\3\goto "Dynamic Display Area" Dynamic Display Area\} \p
\{\3\goto "Interface Topics" Interface Description\} \p
\{\3\goto "Maintenance/Tuning Application" Maintenance/Tuning Application\} \p
\{\3\goto "Top Menu Options" Top Menu Options\} \p
\{\3\goto "Recovery Application" Recovery Application\} \p
\{\3\goto "Status Application" Status Application\}
\p\p
\{\7\goto "tooltop" Top Of Page\} \p
\keyword "module selection" \keyword "selecting modules" \keyword "RAID Modules" \keyword "screen description"

\topic "Dynamic Display Area" \p\1
Dynamic Display Area \label "dynamictop"
\p\p
Fast Find -- \{\5\goto "dynamcfg" Configuration\} | \{\5\goto "dynamhighlight" Highlighting\} | \{\5\goto "dynamrt" Related Topics\}
\p\p\1
Status, Recovery, and Maintenance/Tuning Applications \0\p\p
This main display area appears below the RAID Selection and Tool Bar area for all applications. However, the Configuration Application display differs from the others and is described below.
\p\p
This main viewing area remains blank until you select one of the main task options (from the top menu or the tool bar). When you select a task, this display area is updated dynamically to show information for the selected \{\2\bring_popup "RAID Module" RAID Module\}. This display does not change until you do one of the following:
\p\p
\{\1 o \0\} Select another task option.
\p\p
\{\1 o \0\} Change your RAID Module Selection. When you change RAID Modules, the main viewing area remains blank until you select a task.
\p\p\1
Configuration Application \0\label "dynamcfg"\p\p
The devices configured for a RAID Module are identified in the Module Information area on the left side of the screen. You perform all Configuration tasks on a RAID Module and its associated \{\2\bring_popup "Controller" controllers\}, \{\2\bring_popup "Configured Drive Group" drive group\}, and \{\2\bring_popup "Logical Unit" logical units\}.
\p\p
As you select a device (left-click the mouse) in the list on the left side of the Configuration main screen, detailed information for that device displays on the right side of the screen (the Detailed Information area). You can only highlight one device at a time. You cannot select or highlight any item in the Detailed Information area; it is for information only.
\p\p
You can right-click the mouse on the devices in the Module Information area to get a menu of task options you can perform on that device. For example, if you select a Group and right-click the mouse, you are able to select the following options: List/Locate Drives, Create LUN (if there is available group capacity), Modify Group/LUN, or Delete.
\p\p\1
Highlighting Options \label "dynamhighlight"\0\p\p
Choose one: \p\p
\{\1 o \0\} Single-click to highlight a single item. \p\p
\{\1 o \0\} Press Shift + click to highlight a series of items. For example, single-click to highlight the top item in a list, then press Shift + click on the last item in the list to highlight all the items in that list. \p\p
\{\1 o \0\} Press Control + click to highlight items not in a series. For example, single-click to highlight one item in a list, then press Control + click on another item to highlight it as well. Do this for every item you want to highlight. Pressing Control + click on a highlighted item deselects that item.
\p\p\1
Related Topics \0\label "dynamrt"\p
\{\3\goto "Information In Configuration" What Information Appears In The Configuration Application?\} \p
\{\3\goto "Interface Topics" Interface Description\} \p
\{\3\goto "RAID Module Selection/Tool Bar Area" RAID Module Selection And Tool Bar Area\}
\p\p
\{\7\goto "dynamictop" Top Of Page\} \p
\keyword "screen description" \keyword "dynamic screen display" \keyword "highlighting options" \keyword "selecting messages"

\file glossary.txt

\6 POPUPS HERE\0

\popup "Configuration Type"
\0\p
Configuration Type \p\p
Either single-host, multi-host, or independent controller configurations. See the glossary for definitions of each of these configuration types. \p

\popup "Label"\p\0
When the flashing lights have helped you identify a RAID Module, place a label on it that includes its name for future reference. If using the networked version of this software, you may also want to include the controllers' names and IP addresses. \p

\popup "Balanced LUN Distribution"
\0\p
Balanced LUN Distribution \p\p
The storage management software automatically assigns all logical units on a new drive group to one of the active controllers during LUN creation unless you specifically change its assignment. The LUNs are balanced across active/active controller pairs on a drive-group basis, NOT an individual-LUN basis. The first drive group created in a session is assigned to controller A, the second drive group created in the session is assigned to controller B, the third to controller A again, and so on.\p 

\popup "Hard Address"
\0\p
Hard Address (Fibre Channel) \p\p
If the hard address (Preferred AL_PA) is not available, the controller automatically obtains the first address available after the other ports on the loop have obtained their hard addresses. The following hex values are possible: \p\p
0 -- Undefined \p\p
0x01 -- 0x7E -- Loop Hard Address \p\p
0x7F -- No hard or preferred address (obtain first available address) \p\p
0x80 -- 0xFE - Undefined \p\p
0xFF -- Non-loop access has been specified (the controller will attempt Point-to-Point) \p

\popup "Loop ID"
\0\p
Fibre Channel Loop ID \p\p
Loop IDs are assigned an arbitration priority with (host-side ID) 0 being the lowest and 126 being the highest. This parameter also uses bit 7 to indicate two modes of operation: \p\p
Bit 7 / Bits 6-0 \p\p
-- 0 / 0x00 - 0x7F: Loop ID Base (added to the Host-Side ID); this is the default value \p\p
-- 1 / 0x00 - 0x7D: Loop ID (Host-Side ID ignored) \p\p
-- 1 / 0x7E: No loop operation (initialize as Point-to-Point or Fabric only) \p\p
-- 1 / 0x7F: No Preferred Address \p\p
NOTE: The default value, 0x00, means the default configuration equates the Host-Side ID and the FC Loop ID which allows users to set the Loop ID for up to 16 separate controllers via a physically accessible switch. \p

\popup "Compatible Files/Versions Screen" \p\0
Compatible Files/Versions Screen \p\p
When you select a RAID Module >> Firmware Upgrade >> either Online or Offline, the software checks for restrictions based on the type of firmware upgrade you select. If no restrictions are found, a display shows you the current firmware version for the selected RAID Module and a list of version levels that are compatible. The software uses the fwcompat.def file to generate this list. \p\p
Current Firmware Versions at the top of the screen shows: \p\p
-- RAID Module: the identifier for a particular RAID Module. \p\p
-- Controller: the controllers in the selected RAID Module as A or B and, where applicable, a system name/ID. The A and B correspond to the controller hardware IDs.\p\p
-- Firmware Level: the version of controller firmware (appware) currently loaded. \p\p
-- Boot Level: the version of controller bootware currently loaded. \p\p
-- Fibre Channel Level: number indicating the controller type and release version of drivers for fibre channel firmware. \p

\popup "Selecting Compatible Firmware Files" \p\0
Selecting Compatible Files/Versions \p\p
The software displays compatible firmware versions by using the fwcompat.def file to check the firmware files in the selected directory. Each line shows compatible version level numbers for Firmware Level, Boot Level, and Fibre Channel Level as applicable. When you highlight any line, the Path line is updated to list the filenames for the version you select. \p\p
The Path line shows the default as the subdirectory in the installation directory where the fwcompat.def file was copied (see the "Installation and Support Guide" specific to your operating system for installation directory information). \p\p
IMPORTANT \p
If you copied the firmware files, including the fwcompat.def, to a directory other than the default directory, enter the correct directory on the Path line. \p

\popup "Firmware Upgrade Progress" \p\0
Firmware Upgrade Progress \p\p
A histogram for the selected RAID Module indicates the download progress (as a percentage) for each file and starts over at 0% for each new file if you have more than one. \p\p
If you have two controllers in a module, the progress bar reaches 50% after the file is downloaded to the first controller. You may notice the bar pauses at 50% before it reaches 100% while the file is downloaded to the second controller. \p\p
If you select All RAID Modules, the module name is updated as each module begins its upgrade process. \p

\popup "Flashing Lights" \p\0
For Unassigned, Hot Spare, or RAID 0 drive groups (on Series 3 controllers) -- The activity lights on each drive in the drive group flash sequentially one-at-a-time. \p\p
For Unassigned, Hot Spare, or RAID 0 drive groups (on Series 4 controllers) -- The fault lights on each drive in the drive group flash simultaneously. \p\p
For RAID 1, 3, & 5 drive groups (all controllers) -- The activity or fault lights on all drives in the drive group flash simultaneously. \p


\popup "Windows NT Delete" \0\p
For Windows NT \p
BEFORE deleting LUNs with this software, first use the Disk Administrator utility to delete any partitions and de-assign any drive letters associated with the LUNs you want to delete. If you do NOT use this utility, the remaining disk#'s and filesystems could be renumbered and Disk Administrator may not recognize them. If this occurs, you should see a message that they cannot be found. \p

