\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.italic \fg color.black \bg color.transparent

\topic "Home Page"
\0\p\1
HOME PAGE\0
\p\p\1
Common Features For All Applications\0
\p\p
\{\3\subtopic "Using Online Help" Using Online Help\} 
\p\p
\{\3\subtopic "Tasks For All Applications" Task Summary\}
\p\p
\{\3\subtopic "Screen Description" Main Screen Description\}
\p\p
\{\3\subtopic "Using Select Module" Select Module\}
\p\p
\{\3\subtopic "Using Locate Module" Locate Module\}
\p\p
\{\3\subtopic "Using Module Profile" Module Profile\}
\p\p
\{\3\subtopic "Troubleshooting For All Applications" Troubleshooting/Common Questions\}
\p\p
\{\3\subtopic "Types Of Hardware Configurations" Types Of Host-RAID Module Configurations Supported\}
\p\p\1
Specific Application Details\0
\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

\topic "Using Online Help"
\0\p\1
Using Online Help\0
\p\p
This 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).
\p\p
Select help from the top menu or from the dynamic interface area when available. Some screens pop up to overlay the original application window, and you cannot select help in that application AFTER selecting these options:
\p\p
\{\1 o \0\} Select Module
\p\p
\{\1 o \0\} Locate Module
\p\p
\{\1 o \0\} Module Profile
\p\p
\{\1 o \0\} Save Module Profile
\p\p
\{\1 o \0\} Most notification windows
\p\p
\{\1 o \0\} In the \1 Status Application\0, the following Message Log options: Open Log, Save Log File As, Log Settings, and List Type.
\p\p
\{\1 o \0\} In the \1 Configuration Application\0, the task windows: List/Locate Drives, Create LUN, Create Hot Spare, and Delete.
\p\p
Fortunately, it is still possible to obtain help by selecting Help from another application because you can access ALL of the help topics from any application's help. \p

\topic "Tasks For All Applications"
\0\p\1
TASKS FOR ALL APPLICATIONS\0
\p\p\1
File >> Save Module Profile\0 -- save profile information to a file ONLY for the selected \{\2\bring_popup "RAID Module" RAID Module\} 
\p\p\1
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
Locate Module\0 -- flash the summary and drive activity lights to identify the selected RAID Module
\p\p\1
Module Profile\0 -- display specific details about the \{\2\bring_popup "Controller" controllers\}, \{\2\bring_popup "Drive Group" drives\}, or \{\2\bring_popup "Logical Unit" logical units\} for the selected RAID Module
\p\p\1
CONFIGURATION TASKS
\p\p
List/Locate Drives\0 -- determine the physical location of drives that comprise a logical unit/drive group, and locate the drives in a drive group when viewing the list of drives
\p\p\1
Create LUN\0 -- create new logical units (LUNs) or add LUNs to existing drive groups
\p\p\1
Create Hot Spare\0 -- designate drives to act as \{\2\bring_popup "Hot Spare" standbys\} in case any drive fails in a RAID 1, 3, or 5 logical unit on the RAID Module
\p\p\1
Delete\0 -- delete logical units to change your drive group/LUN configuration or to change certain LUN parameters. This option will always present a list of LUNs and ask for confirmation before deleting
\p\p\1
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
\p\p\1
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
Health Check\0 -- immediately verify the status of module and data path components
\p\p\1
LUN Reconstruction\0 -- monitor the status or change reconstruction \{\2\bring_popup "Reconstruction Rate" rate\} for LUNs undergoing \{\2\bring_popup "Reconstruction" reconstruction\}
\p\p\1
RECOVERY TASKS\0
\p\p\1
Recovery Guru\0 -- check selected RAID Modules for component failures and, if detected, recover from them by following step-by-step instructions
\p\p\1
Manual Parity Check/Repair\0 -- manually check and repair \{\2\bring_popup "Parity" parity\} on selected logical units
\p\p\4
CAUTION\0\p
It is best to use Recovery Guru BEFORE performing any Manual Recovery tasks. Only use a manual recovery procedure when directed by your software documentation or a Customer Services Representative. To do otherwise could result in the loss of data.
\p\p\1
Options >> Manual Recovery >> Drives\0 -- manually fail, reconstruct, or revive drives when instructed
\p\p\1
Options >> Manual Recovery >> Logical Units\0 -- manually format or revive logical units/drive groups when instructed
\p\p\1
Options >> Manual Recovery >> Controller Pairs\0 -- manually place controllers online or \{\2\bring_popup "Offline Controller Mode" offline\} when instructed
\p\p\1
MAINTENANCE/TUNING TASKS\0
\p\p\1
Options >> Auto Parity Settings\0 -- change the automatic \{\2\bring_popup "Parity Check/Repair" parity check/repair\} settings, including whether it is enabled or not and the start time of day
\p\p\1
LUN Reconstruction Rate\0 -- change the \{\2\bring_popup "Reconstruction Rate" reconstruction rate\} for LUNs whether undergoing reconstruction or not
\p\p\1
LUN Balancing\0 -- balance logical unit/drive group \{\2\bring_popup "LUN Assignment" ownership\} between \{\2\bring_popup "Active/Active Controller Pair" 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
Controller Mode\0 -- change controllers' \{\2\bring_popup "Controller Mode" modes\} for selected RAID Modules; you can change an \{\2\bring_popup "Active/Passive Controller Pair" active/passive\} controller pair to an active/active mode, or you can swap the active and passive controllers' modes
\p\p\1
Caching Parameters\0 -- change \{\2\bring_popup "Cache Memory" caching\} parameters for the configured LUNs on a selected RAID Module; 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
Firmware Upgrade\0 -- upgrade controller \{\2\bring_popup "Firmware" firmware\} or an \{\2\bring_popup "NVSRAM File" NVSRAM\} file for one or all RAID Modules
\p\p\1
Related Topics\0\p
\{\3\goto "Configuration Task Summary" Configuration Task Summary\} \p
\{\3\goto "Maintenance/Tuning Task Summary" Maintenance/Tuning Task Summary\} \p
\{\3\goto "Recovery Task Summary" Recovery Task Summary\} \p
\{\3\goto "Status Task Summary" Status Task Summary\} \p
\{\3\goto "Top Menu Options" Top Menu Options\} \p

\topic "Screen Description"
\0\p\1
Main Screen Description\0
\p\p
The main screen is comprised of the following areas:
\p\p
\{\3\subtopic "Top Menu Options" Top Menu Options\}
\p\p
\{\3\subtopic "Module Information Area" Module Information Area\}
\p\p
\{\3\subtopic "Dynamic Display Area" Dynamic Display Area\} in the Status, Recovery, and Maintenance/Tuning Applications
\p\p
\{\3\subtopic "Drive Groups Area" Drive Groups Area\} in the Configuration Application
\p\p
\{\3\subtopic "Logical Unit Information Area" Logical Unit (LUN) Information Area\} in the Configuration Application
\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. 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
\keyword "description, main screen"
\keyword "screen description"

\topic "Top Menu Options"
\0\p\1
TOP MENU OPTIONS\0
\p\p
\{\3\subtopic "File Menu" File Menu\}
\p\p
\{\3\subtopic "Edit Menu" Edit Menu\}
\p\p
\{\3\subtopic "Options Menu" Options Menu\}
\p\p\1
Related Topics\0\p
\{\3\goto "Screen Description" Main Screen Description\} \p

\topic "File Menu"
\0\p\1
File Top Menu Selections
\p\p
ALL APPLICATIONS
\p\p
Save Module Profile\0
\p\p
\{\1 o \0\} Save profile information to a file ONLY for the selected RAID Module. Saving profile information copies the information found in Module Profile and the main Configuration Application 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
\{\1 o \0\} 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
Exit\0
\p\p
Quit the application you are in and return to the \{\2\bring_popup "Program Group" program group\}.
\p\p\1
CONFIGURATION
\p\p\1
Reset Configuration\0\p
Reset the RAID Module's \{\2\bring_popup "Drive Group" drive groups\} and \{\2\bring_popup "Logical Unit" logical units\} back to a \keyword "default configuration" default configuration. Only use this option as a last resort if your configuration is totally inaccessible or you want to start completely over. \keyword "reset configuration"
\p\p\4
CAUTION\0\p
You will lose ALL data on the selected RAID Module when you select Options >> Reset Configuration.
\p\p\1
STATUS 
\p\p
Open Log\0
\p\p
\{\1 o \0\} View summary and detailed information for a selected log file.
\p\p
\{\1 o \0\} Only active when you select Message Log.
\p\p
\{\1 o \0\} 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
Save Log As\0
\p\p
\{\1 o \0\} Save a selected message log to another file.
\p\p
\{\1 o \0\} Only active when you select Message Log. \p
\p\p\1
Related Topics\0\p
\{\3\goto "Open An Existing Log File" Open An Existing Message Log File\} \p
\{\3\goto "Save The Log As Another File" Save A Message Log To Another File\} \p
\{\3\goto "Save A Module Profile" Save A Module Profile\} \p
\{\3\goto "Top Menu Options" Top Menu Options\} \p
\{\3\goto "When Should I Use Reset Configuration?" When Should I Use Reset Configuration?\}
\keyword "file menu"
\keyword "profile, modules"
\keyword "file, save"
\keyword "file, open"
\keyword "saving files"
\keyword "opening files"

\topic "Edit Menu"
\0\p\1
Edit Top Menu Selections \p
(Status Application Only)
\p\p
Copy To Clipboard\0
\p\p
\{\1 o \0\} Copy the contents of a detailed message to the clipboard.
\p\p
\{\1 o \0\} Active in either Message Log or Health Check when you select Show Details.
\p\p\1
Select All\0
\p\p
\{\1 o \0\} 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
\{\1 o \0\} Active when you select either Message Log or Health Check.
\p\p\1
Related Topics\0\p
\{\3\goto "Copy To Clipboard" Copy To Clipboard\} \p
\{\3\goto "Selecting Messages Or Exceptions" Selecting Messages Or Exceptions\} \p
\{\3\goto "Top Menu Options" Top Menu Options\} \p
\keyword "edit menu"
\keyword "copying contents"

\topic "Options Menu"
\0\p\1
Options Top Menu Selections
\p\p
STATUS
\p\p
Refresh All\0
\p\p
\{\1 o \0\} Updates Message Log to show any new messages in the summary information area.
\p\p
\{\1 o \0\} Only active when you select Message Log.
\p\p
\{\1 o \0\} Selecting this option updates Message Log to include all message types (the default setting).
\p\p\1
Log Settings\0
\p\p
\{\1 o \0\} You can select this option at all times.
\p\p
\{\1 o \0\} Changing any of these parameters affects ALL your RAID Modules.
\p\p
\{\1 o \0\} 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 Log size before notification\0 -- sets the maximum size that the default log file can be before you receive notification that this value has been reached
\p\p
3.\1 Check RAID Module every x minutes\0 -- controls the frequency at which the background monitor checks the RAID Modules
\p\p\1
RECOVERY
\p\p
Manual Recovery\0\p
\{\1 o \0\} Allows you to manually perform recovery procedures on drives, logical units, or controllers.
\p\p
\{\1 o \0\} If All RAID Modules is selected, this option is grayed out.
\p\p\1
MAINTENANCE/TUNING
\p\p
Auto Parity Settings\0\p
\{\1 o \0\} Enable or disable the automatic parity check/repair operation, or change the daily time at which it starts.
\p\p
\{\1 o \0\} 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\p
\{\3\goto "Change Log Settings" Change Message Log Settings\} \p
\{\3\goto "Refresh Message Log" Refresh Message Log\} \p
\{\3\goto "Top Menu Options" Top Menu Options\} \p
\{\3\goto "Using Manual Recovery" Using Manual Recovery\} \p
\{\3\goto "Using Auto Parity Settings" Using Options >> Auto Parity Settings\} \p
\keyword "parity, manual"
\keyword "options menu"
\keyword "Refresh All"
\keyword "log settings"

\topic "Module Information Area"
\0\p\1
Module Information Area\0
\p\p
This area appears below the top menu options and allows you to perform the following tasks:
\p\p\1
Select A RAID Module\0\p
You perform all tasks (for example, performing a Health Check or creating logical units) on a \{\2\bring_popup "RAID Module" RAID Module\}. Select a RAID Module BEFORE selecting an option you wish to perform. You can easily select specific RAID Modules for performing storage management operations in either of two ways: \p
\{\1 o \0\} Use the\1 Drop-Down List\0 located at the far left of the Module Information area in each application's main screen. This is the quickest selection method if you are familiar with the module names that will appear in the list. \p\1 OR \0\p
\{\1 o \0\} Choose\1 Select Module\0 for a more detailed list of all RAID Modules. Highlight the module you want and select OK. This module is now the default RAID Module.
\p\p
You also use\1 Select Module\0 to find RAID Modules quickly, to add or remove them from the storage management software, or to edit the information (module name and comments) about a RAID Module.
\keyword "selecting RAID Modules"
\p\p
If you re-select the RAID Module that is currently displayed in the list box, you are returned to the main screen. Additionally, the component statuses have been updated at this time. \keyword "selecting RAID Modules"
\p\p\1
Locate A RAID Module\0\p
Select a \keyword "RAID Module" RAID Module, then Locate Module to physically identify its location. The activity lights on the drive canisters flash sequentially one-at-a-time until you select Stop. Some RAID Modules also have a \keyword "summary activity indicator" summary activity indicator light that also flashes. For best results, use this option when there is no I/O activity occurring. Also, once you have identified the RAID Module, place a label on it that includes its name for future reference. \keyword "Locate Module"
\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
View A Profile Of A RAID Module\0\p
Select a RAID Module, then Module Profile to determine the physical and logical make-up of the selected RAID Module. This option indicates how many \{\2\bring_popup "Controller" controllers\} and drives are in the RAID Module. It also shows you the \{\2\bring_popup "Logical Unit" logical unit\} (LUN) configuration with each LUN's parameters. \keyword "viewing a module profile"
\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 if you need to perform any recovery or maintenance tasks. From the top menu, select File >> Save Module Profile. 
\p\p\1
NOTE\0: When you select either Locate Module or Module Profile, another window overlays the display area without changing any information in the dynamic display area. In this additional window, you may exit without changing any module settings or executing any operation.
\p\p\1
Related Topics\0\p
\{\3\goto "Dynamic Display Area" Dynamic Display Area\} \p
\{\3\goto "Screen Description" Main Screen Description\} \p
\{\3\goto "Save A Module Profile" Save A Module Profile\} \p
\{\3\goto "Using Select Module" Using Select Module\} \p
\{\3\goto "Using Locate Module" Using Locate Module\} \p
\{\3\goto "Using Module Profile" Using Module Profile\} \p

\topic "Dynamic Display Area"
\0\p\1
Dynamic Display Area \p
(Status, Recovery, and Maintenance/Tuning Applications)\0
\p\p
This main display area appears below the Module Information area for all applications EXCEPT Configuration. To the left, you see the main tasks (option buttons) you can perform, such as Message Log, Recovery Guru, LUN Reconstruction Rate, etc. When you select one of these options, the main display area to the right updates dynamically to show information for the selected RAID Module. This display does not change until you do one of the following:
\p\p
\{\1 o \0\} Select another of these options.
\p\p
\{\1 o \0\} Change your \{\2\bring_popup "RAID Module" RAID Module\} Selection. The main viewing area remains blank until you select one of these options.
\p\p\1
Related Topics\0\p
\{\3\goto "Screen Description" Main Screen Description\} \p
\{\3\goto "Module Information Area" Module Information Area\} \p
\keyword "screen description"
\keyword "changing options"
\keyword "display area"

\topic "Drive Groups Area"
\0\p\1
Drive Groups Area \p
(Configuration Application Only)\0
\p\p
The \keyword "drive group" drive groups are identified in the Drive Groups area on the left side of the screen. You perform all Configuration tasks on a RAID Module and its associated drive groups. The Drive Groups area has the following column headings:
\p\p\1
Group\0\p
Identifies the type of drive group. There are three types of drive groups: \p
\{\1 o \0\} An \keyword "unassigned drives" unassigned drive group is a set of drives that has not been configured into \{\2\bring_popup "Logical Unit" logical units\} (LUN) or hot spares.
\p\p
\{\1 o \0\} A \keyword "hot spare" hot spare drive group indicates the drives that have been assigned as \{\2\bring_popup "Hot Spare" hot spares\}.
\p\p
\{\1 o \0\} A configured drive group (designated with a number (e.g. 1, 2, 3, etc.)) indicates a set of drives that has one or more LUNs configured on it with the same RAID Level.
\p\p\1
NOTE\0: As you highlight a drive group in the list on the left side of the main Configuration screen, the corresponding LUNs are highlighted in the Logical Unit (LUN) Information area on the right side of the screen. You can only highlight one drive group at a time. You cannot select or highlight any item in the logical unit information list; it is for information only.
\p\p\1
Number Of LUNs\0\p
Indicates how many LUNs are currently configured on the drive group. This is only applicable for configured drive groups. \keyword "number of LUNs"
\p\p\1
RAID Level\0\p
Indicates the \{\2\bring_popup "RAID Level" RAID Level\} of the logical unit. This is only applicable for configured drive groups. Each LUN in the same drive group must have the same RAID Level. \keyword "RAID Level"
\p\p\1
Drives\0\p
Indicates how many drives comprise the drive group.
\p\p\1
Total Capacity\0\p
Indicates how much capacity (in megabytes) is available on the drive group. The capacity reflects any redundancy or \{\2\bring_popup "RAID 1" RAID 1\} mirroring factors. For example, a drive group comprised of RAID 1 logical units has half of the capacity of one with \{\2\bring_popup "RAID 0" RAID 0\} logical units. The \keyword "total capacity" total capacity for an unassigned drive group shows the entire capacity of the drives and does not reflect any redundancy or mirroring factors.
\p\p\1
Remaining Capacity\0\p
Indicates how much capacity (in megabytes) is still available for configuring LUNs on the drive group. The capacity reflects any redundancy or RAID 1 mirroring factors (except for an unassigned drive group). \keyword "remaining capacity"
\p\p\1
Related Topics\0\p
\{\3\goto "Logical Unit Information Area" Logical Unit (LUN) Information Area\} \p
\{\3\goto "Screen Description" Main Screen Description\} \p
\{\3\goto "Module Information Area" Module Information Area\} \p
\{\3\goto "Top Menu Options" Top Menu Options\} \p
\keyword "viewing drive groups"

\topic "Logical Unit Information Area"
\0\p\1
Logical Unit (LUN) Information Area \p
(Configuration Application Only)\0
\p\p
The configured logical units are identified in the Logical Unit (LUN) Information area on the right side of the screen. The Logical Unit (LUN) Information area has the following column headings:
\p\p\1
NOTE\0: As you highlight a drive group in the list on the left side of the main Configuration screen, the corresponding logical units are highlighted in the Logical Unit (LUN) Information area. You can only highlight one drive group at a time.
\p\p\1
LUN\0\p
Indicates the number assigned to the logical unit.
\p\p\1
Group\0\p
Indicates the number assigned to a configured drive group, consisting of one or more logical units.
\p\p\1
Device Name\0\p
Indicates a system-designated \{\2\bring_popup "Device Name" name\} that identifies the controllers/LUNs in the selected RAID Module.
\p\p\1
RAID Level\0\p
Indicates the \{\2\bring_popup "RAID Level" RAID Level\} of the LUN.
\p\p\1
Capacity\0\p
Indicates how much capacity (in megabytes) is available on the LUN. The capacity reflects any redundancy or \{\2\bring_popup "RAID 1" RAID 1\} mirroring factors. For example, a RAID 1 LUN has half of the capacity of a \{\2\bring_popup "RAID 0" RAID 0\} LUN.
\p\p\1
Status\0\p
Gives the operating condition of the logical unit. For an explanation of the possible statuses, select the "Possible Logical Unit Statuses" topic in the list below. \p
For Dead or Degraded LUNs, you should use the \keyword "Status Application" Status Application to select Health Check and follow the recommended Action To Take in the detailed information screen.
\p\p\1
Related Topics\0\p
\{\3\goto "Drive Groups Area" Drive Groups Area\} \p
\{\3\goto "Screen Description" Main Screen Description\} \p
\{\3\goto "Module Information Area" Module Information Area\} \p
\{\3\goto "Possible LUN Statuses" Possible Logical Unit Statuses\} \p
\{\3\goto "Top Menu Options" Top Menu Options\} \p
\keyword "viewing logical units"

\topic "Using Select Module"
\0\p\1
Using Select Module
\p\p
When To Use\0\p
Use to select or view information about a specific \{\2\bring_popup "RAID Module" RAID Module\}; to add or remove modules in your system, or to change a module's information (module name or comments). 
\p\p\1
Options\0\p
This screen has the following options:
\p\p
\{\1 o \0\}\1 Find\0 -- use this option to help you quickly locate a RAID Module. It will probably be most useful when you have many modules.
\p\p
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 o \0\}\1 Add\0 -- (available for the Networked version ONLY) use this option to add new modules to your system so that this software can access and monitor it. 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 SCSI connection.
\p\p
\{\1 o \0\}\1 Remove\0 -- use this option to remove modules from your system. You can only remove one module at a time. This option will be grayed out if you selected All RAID Modules.
\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 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
\{\1 o \0\} If you are operating on a system with SCSI 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 on the SCSI Bus.
\p\p
\{\1 o \0\}\1 Edit\0 -- use this option to add or change information (module name and comments) about a RAID Module that has already been defined. You can only edit information for one module at a time and this option will be grayed out if you selected All RAID Modules. Use the comments area to provide detailed information about the RAID Module to help you identify it, such as location information. \p
\keyword "modules, locating"
\keyword "modules, selecting"
\keyword "adding RAID Modules"
\keyword "removing RAID Modules"
\keyword "selecting RAID Modules"
\keyword "modules, adding"
\keyword "modules, removing"

\topic "Using Locate Module"
\0\p\1
Using Locate Module\0
\p\p\1
When To Use\0\p
Use to physically locate and identify a specific \{\2\bring_popup "RAID Module" RAID Module\} if you have several RAID Modules connected to your system.
\p\p
See Related Topics at the bottom of this screen for additional information on this option.
\p\p\1
What Happens\0\p
The \{\2\bring_popup "Activity Lights" activity lights\} on the drive canisters flash sequentially one-at-a-time until you select Stop. Some RAID Modules also have a summary activity indicator light that also flashes.
\p\p\1
IMPORTANT\0\p
\{\1 o \0\} If All RAID Modules is selected, this option is grayed out.
\p\p
\{\1 o \0\} Any drives with a status other than Optimal are skipped (that is, the activity light does not flash).
\p\p
\{\1 o \0\} If you have a controller version earlier than the Series 3, this option does not work on a module with no configured logical units (that is, all \{\2\bring_popup "Unassigned Drive Group" unassigned drives\}).
\p\p\1
For Best Results\0\p
\{\1 o \0\} Select Locate Module when there is no I/O activity on the selected RAID Module.
\p\p
\{\1 o \0\} When the flashing lights have helped you identify a RAID Module, place a label on that module that includes its name for future reference.
\p\p\1
Related Topics\0\p
\{\3\goto "Using List/Locate Drives" Using List/Locate Drives\} \p
\{\3\goto "Why Are Some Options Grayed Out?" Why Are Some Options Grayed Out?\} \p
\{\3\goto "Why Did Locate Module Take A Long Time?" Why Did Locate Module Take A Long Time?\} \p
\{\3\goto "Why Doesn't Locate Module Work?" Why Doesn't Locate Module Work?\} \p
\keyword "identifying modules"
\keyword "drive activity lights"
\keyword "activity lights"
\keyword "labeling modules"
\keyword "modules, locating"
\keyword "Locate Module"

\topic "Using Module Profile"
\0\p\1
Using Module Profile\0
\p\p\1
When To Use\0\p
Use to find specific details about the controllers, drives, or logical units for the selected RAID Module. This profile can help you identify: \p
\{\1 o \0\} Which \{\2\bring_popup "Logical Unit" logical units\} are assigned to the controllers in the RAID Module
\p\p
\{\1 o \0\} Manufacturing details about the \{\2\bring_popup "Controller" controller\}, including its type and \{\2\bring_popup "Firmware" firmware\} version
\p\p
\{\1 o \0\} Specifics about the drives, including location, status, and manufacturing details
\p\p
\{\1 o \0\} Logical unit \{\2\bring_popup "LUN" (LUN)\} parameter settings
\p\p
See Related Topics at the bottom of this screen for additional information on this option.
\p\p\1
What Happens\0\p
Displays information about the components (controllers, drives, and logical units) in the selected \{\2\bring_popup "RAID Module" RAID Module\}.
\p\p\1
IMPORTANT\0\p
If All RAID Modules is selected, this option is grayed out.
\p\p\1
Options\0\p
\{\1 o \0\} While viewing the module profile, you can select Controllers, Drives, or Logical Units for more detailed information.
\p\p
\{\1 o \0\} After exiting Module Profile, you can save the profile to a specific file if desired: \p
1. Exit Module Profile (select OK).
\p\p
2. From the top menu bar, select File >> Save Module Profile.
\p\p\1
Related Topics\0\p
\{\3\subtopic "Save A Module Profile" Save A Module Profile\} \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
\{\3\goto "Why Are Some Options Grayed Out?" Why Are Some Options Grayed Out?\} \p
\keyword "profile, controllers"
\keyword "profile, drives"
\keyword "details, module"
\keyword "profile, logical units"
\keyword "Module Profile"
\keyword "profile, modules"
\keyword "component details"
\keyword "manufacturing details"
\keyword "drive details"
\keyword "logical unit details"
\keyword "controller details"
\keyword "viewing profile"

\topic "Information In Module Profile"
\0\p\1
What Information Appears In Module Profile?\0
\p\p
Whenever you select \keyword "Module Profile" Module Profile, you see a summary profile of the selected RAID Module including information on its controllers, disk drives, and logical units (LUN).
\p\p
See Related Topics at the bottom of this screen for additional information on this option.
\p\p\1
Controllers\0
\p\p\1
Name\0: Identifies the controllers in the selected RAID Module by an A or B designation and, where applicable, includes a system \{\2\bring_popup "Device Name" device name\}. The A and B are relative names to simplify identification of the controllers.
\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 \{\2\bring_popup "Active Controller Mode" Active\}, \{\2\bring_popup "Passive Controller Mode" Passive\}, or \{\2\bring_popup "Offline Controller Mode" Offline\}. You could also see (Inaccessible) with these statuses if the RAID Module has an \{\2\bring_popup "Independent Controller Configuration" 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\0
\p\p\1
Number of Drives =\0 Indicates how many drives make up the selected RAID Module.
\p\p\1
Options\0\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\p
\{\3\goto "Save A Module Profile" Save A Module Profile\} \p
\{\3\goto "Using Module Profile" Using Module Profile\} \p
\{\3\goto "What Additional Details Can I See?" What Additional Details Can I See?\} \p
\{\3\goto "What Does The Device Name Mean?" What Does The Device Name Mean?\} \p
\keyword "controller name"
\keyword "serial number, controller"
\keyword "controller mode"

\topic "What Additional Details Can I See?"
\0\p\1
What Additional Details Can I See?\0
\p\p
From the initial Module Profile screen, you can view more detailed information for three components:
\p\p
\{\3\subtopic "Controller Detailed Information" Controller Detailed Information\}
\p\p
\{\3\subtopic "Drive Detailed Information" Drive Detailed Information\}
\p\p
\{\3\subtopic "LUN Detailed Information" Logical Unit Detailed Information\}
\p\p\1
Related Topics\0\p
\{\3\goto "Save A Module Profile" Save A Module Profile\} \p
\{\3\goto "Using Module Profile" Using Module Profile\} \p
\keyword "Module Profile"
\keyword "profile, modules"

\topic "Controller Detailed Information"
\0\p\1
Controller Detailed Information\0
\p\p\1
When To Use\0\p
You may want to view this information as a reference if you need to perform any maintenance or troubleshooting procedures. For example, 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\1
Board ID\0: Controller model number (3601, 3201, etc.) \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\1
Product Serial Number\0: Usually the same as Board Serial Number \p\1
Vendor ID\0: Controller manufacturer's name \p\1
Date of Manufacture\0: Date controller was assembled
\p\p\1
SCSI ID\0: Address assigned to the controller for its connection to the bus (Not applicable for the Networked version)
\p\p\1
Boot Level\0: Number indicating the release version of controller \{\2\bring_popup "Bootware" bootware\}
\p\p\1
Firmware Level\0: Number indicating the release version of controller \{\2\bring_popup "Firmware" appware\}
\p\p\1
Fibre Channel Level\0: Number indicating the release version of fibre-channel controller 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
Related Topics\0\p
\{\3\goto "Save A Module Profile" Save A Module Profile\} \p
\{\3\goto "What Additional Details Can I See?" What Additional Details Can I See?\} \p
\keyword "board information"
\keyword "serial number, board"
\keyword "product information"
\keyword "serial number, product"
\keyword "firmware level"
\keyword "SCSI ID"
\keyword "cache size"
\keyword "vendor ID"
\keyword "bootware level"
\keyword "manufacture date"
\keyword "controller details"
\keyword "capacity, cache"

\topic "Drive Detailed Information"
\0\p\1
Drive Detailed Information\0
\p\p\1
When To Use\0\p
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 channel number and SCSI ID where the channel number is always listed first. Use the location information to match it to a unique drive and to help locate it in the RAID Module.
\p\p
For example, this identifier includes the \{\2\bring_popup "SCSI Channel" SCSI Channel\} and \{\2\bring_popup "SCSI ID" 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 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
Related Topics\0\p
\{\3\goto "Possible Drive Statuses" Possible Drive Statuses\} \p
\{\3\goto "Save A Module Profile" Save A Module Profile\} \p
\{\3\goto "What Additional Details Can I See?" What Additional Details Can I See?\} \p
\keyword "drive details"
\keyword "profile, drives"
\keyword "drive location"
\keyword "capacity, drives"
\keyword "drive capacity"
\keyword "drive firmware"
\keyword "product ID"
\keyword "drive status"
\keyword "status, drives"
\keyword "serial number, drive"
\keyword "date code"
\keyword "vendor ID"

\topic "LUN Detailed Information"
\0\p\1
Logical Unit Detailed Information\0
\p\p\1
When To Use\0\p
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 controllers in the selected RAID Module by a system \{\2\bring_popup "Device Name" device name\}. \keyword "device name"
\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. \keyword "RAID Level"
\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\} option has been enabled for a particular LUN.
\p\p\1
Write Cache Mirroring\0: Indicates whether the \{\2\bring_popup "Write Cache Mirroring" write cache mirroring\} option has been enabled for a particular LUN.
\p\p\1
Cache Without Batteries\0: Indicates whether the \{\2\bring_popup "Cache Without Batteries" cache without batteries\} option has been enabled for a particular LUN.
\p\p\1
Status\0: Operating condition of the logical unit. For an explanation of the possible statuses, select the "Possible Logical Unit Statuses" topic in the 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\p
\{\3\goto "Possible LUN Statuses" Possible Logical Unit Statuses\} \p
\{\3\goto "Save A Module Profile" Save A Module Profile\} \p
\{\3\goto "What Additional Details Can I See?" What Additional Details Can I See?\} \p
\{\3\goto "What Does The Device Name Mean?" What Does The Device Name Mean?\} \p
\keyword "profile, logical units"
\keyword "capacity, logical units"
\keyword "logical unit capacity"
\keyword "segment size"
\keyword "write caching"
\keyword "write cache mirroring"
\keyword "cache without batteries"
\keyword "logical unit status"
\keyword "status, logical units"
\keyword "LUN number"

\topic "Save A Module Profile"
\0\p\1
Save A Module Profile \0
\p\p\1
When To Use\0\p
Saving profile information copies the information found in Module Profile and the main Configuration Application screen to a file for your reference. It does not, however, copy configuration information that you could later use to restore your module. Also, this 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\0\p
\{\1 o \0\} 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 o \0\} If All RAID Modules is selected, this option is grayed out.
\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\} If you are in \keyword "Save Module Profile" Module Profile, the Save Module Profile option is unavailable until you close that screen.
\p\p\1
Steps To Save A Module Profile\0\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 \{\2\bring_popup "Configuration Information" Configuration Information \}.
\p\p
4. At the second Save Module Profile screen, enter the filename where you want this profile stored. At this screen in UNIX systems, you can use the \{\2\bring_popup "Filter" 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\p
\{\3\goto "Using Module Profile" Using Module Profile\} \p
\keyword "profile, modules"
\keyword "profile, saving"
\keyword "filter"

\popup "Configuration Information" 
\0\p
The drive group/LUN information found in the main Configuration Application screen. \p

\topic "Troubleshooting For All Applications"
\0\p\1
Troubleshooting/Common Questions For All Applications\0
\p\p\1
General Questions\0\p
\{\3\subtopic "Are There Different Screen Displays?" Are There Different Screen Displays?\}
\p\p
\{\3\subtopic "Considerations For The Networked Version" Are There Special Considerations For The Networked Version?\}
\p\p
\{\3\subtopic "Considerations For Independent Controllers" Are There Special Considerations For Using The Independent Controllers Configuration?\}
\p\p
\{\3\subtopic "Can I Update Component Statuses On Screen?" Can I Update Component Statuses On Screen?\}
\p\p
\{\3\subtopic "How Can I Check For Component Failures?" How Can I Check For Component Failures?\}
\p\p
\{\3\subtopic "About A RAID Module's Controllers" How Can I Tell How Many And What Kind Of Controllers A RAID Module Has?\}
\p\p
\{\3\subtopic "What Does The Device Name Mean?" What Does The Device Name Mean?\}
\p\p
\{\3\subtopic "The ''Optimal (Health Check Not Done)'' Message Displays" What If Recovery Guru Or Health Check Displays The ''Optimal (Health Check Not Done)'' Message?\}
\p\p
\{\3\subtopic "The ''Selection Is Not A File'' Message Displays" What If The ''Selection Is Not A File'' Message Displays?\}
\p\p
\{\3\subtopic "The ''Threshold Level Reached'' Message Displays" What If The ''Threshold Level Reached'' Message Displays?\}
\p\p
\{\3\subtopic "What Is A Drive Group?" What Is A Drive Group?\}
\p\p
\{\3\subtopic "What Is A Logical Unit?" What Is A Logical Unit?\}
\p\p
\{\3\subtopic "What Is A RAID Module?" What Is A RAID Module?\}
\p\p
\{\3\subtopic "What Is Parity?" What Is Parity?\}
\p\p
\{\3\subtopic "What Is RDAC?" What Is RDAC?\}
\p\p
\{\3\subtopic "What Is Reconstruction?" What Is Reconstruction?\}
\p\p
\{\3\subtopic "What Is SNMP?" What Is SNMP?\}
\p\p
\{\3\subtopic "Why Are Some Options Grayed Out?" Why Are Some Options Grayed Out?\}
\p\p
\{\3\subtopic "Why Aren't LUNs Visible On Screen?" Why Would Logical Units Not Be Visible On The Screen?\}
\p\p\1
Locate Module\0\p
\{\3\subtopic "Why Did Locate Module Take A Long Time?" Why Did Locate Module Take A Long Time?\}
\p\p
\{\3\subtopic "Why Doesn't Locate Module Work?" Why Doesn't Locate Module Work?\}
\p\p\1
Save Module Profile\0\p
\{\3\subtopic "Can Save Module Profile Restore My Configuration?" Can I Use Save Module Profile Information To Restore My Configuration?\}

\topic "Are There Different Screen Displays?"
\0\p\1
Are There Different Screen Displays?\0
\p\p
The Status screen displays information in two ways, depending on which options you select.
\p\p
1. When you select the top menu options, Locate Module, or Module Profile, another window overlays the screen without changing any information in the main viewing area. In this additional window, you may select Cancel any time to exit without changing any module settings or executing any operation.
\p\p
2. When you select one of the three options to the left of the main viewing area, the screen dynamically updates to display the selected option's information. This display does not change until you do one of the following: \p
\{\1 o \0\} Select another of these three options (Message Log, Health Check, or LUN Reconstruction).
\p\p
\{\1 o \0\} Change your RAID Module selection. The main viewing area remains blank until you select one of these three options.
\p\p
\{\1 o \0\} Exit Status. The next time you enter Status, the default display is the first RAID Module with Message Log selected. \p
\keyword "screen description"
\keyword "changing options"

\topic "Considerations For The Networked Version"
\0\p\1
Are There Special Considerations For The Networked Version?\0
\p\p
Yes. You should be aware of the following restrictions:
\p\p\1
No RDAC Protection\0\p
If you have installed the Networked version of this software, you will NOT have \{\2\bring_popup "RDAC Driver" RDAC\} protection over the network connection. This means that there is no way to check for and handle I/Os. Therefore, you must use extreme caution when you perform tasks that involve a transfer of LUN ownership between \{\2\bring_popup "Redundant Controller Pair" redundant controllers\} to avoid failure of the I/Os or the operation.
\p\p\1
Host-RAID Module Configurations\0\p
If you are using the Networked version of this 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
NOTE\0: The Networked version of the storage management software always sees both controllers in a dual-controller RAID Module regardless of which configuration you have. However, the Networked version will be able to tell if the RAID Module it is connected to has an independent controller configuration if independent controllers was selected using the Select Module option.
\p\p
\{\1 o \0\} Your RAID Modules do not have RDAC failover protection unless there is SCSI-based failover protection installed on the host connected to the modules through the SCSI Bus.
\p\p
\{\1 o \0\} This software does not provide SCSI-related data path failure detection or recovery. However, any problems with a network connection to the controllers or a problem with the controllers themselves are shown as a data path failure. Recovery Guru provides assistance for these problems.
\p\p
\{\1 o \0\} This software has no way to recognize any exclusive access operations that may be performed by other software installed on the host machine (not even another storage management package). This requires you to use caution before starting certain operations that need exclusive access because without it filesystems are not detected and multiple operations could be launched without logical units being protected. Furthermore, because it is possible to open a Configuration Application from any networked station, be sure that you have only one configuration session open at a time when creating or deleting LUNs or the operation will fail for all but one station.
\p\p\4
CAUTION\0\p
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 Delete for LUNs and File >> Reset Configuration (Configuration); fixing Multiple Drive Failures with Recovery Guru and formatting a LUN with Options >> Manual Recovery >> Logical Units (Recovery); and Firmware Upgrade >> Offline method (Maintenance/Tuning).
\p\p\1
Related Topics\0\p
\{\3\goto "Considerations For Independent Controllers" Are There Special Considerations For Using The Independent Controllers Configuration?\} \p
\{\3\goto "Types Of Hardware Configurations" Types Of Host-RAID Module Configurations Supported\} \p
\keyword "RDAC, no protection"
\keyword "Networked version"

\topic "Considerations For Independent Controllers"
\0\p\1
Are There Special Considerations For Using The Independent Controllers Configuration?\0
\p\p
Yes. If you are using the \{\2\bring_popup "Independent Controller Configuration" independent controllers\}, each \{\2\bring_popup "Controller" controller\} in the RAID Module is controlled by only one host machine. This means that only the software on the host machine connected to the controller can control the \{\2\bring_popup "Drive Group" drive groups\}/\{\2\bring_popup "Logical Unit" logical units\} it owns.
\p\p
While the storage management software on either host will report the other controller and its drive groups/LUNs as Inaccessible, the software cannot perform most operations on the alternate controller's drive groups/LUNs.
\p\p\1
IMPORTANT\0\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 LUNs or the operation will fail from one of the hosts.
\p\p
The following items are unique to this configuration: \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\} We recommend 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 for failed-controller situations so that each controller can take over and display all configured drive groups/LUNs for the alternate controller.
\p\p
\{\1 o \0\} Requires a special setting in\1 Select Module\0 (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\} The storage management software reports the alternate controller and its drive group/LUNs as "Inaccessible."
\p\p
\{\1 o \0\}\1 Health Check\0 (Status Application) and\1 Recovery Guru\0 (Recovery Application) detect data path-related failures ONLY for the controller that is connected to the host machine running the storage management software. For example, if host one has a controller (data path) failure, host one reports the failure, but host two will NOT report a data path failure using its Health Check or Recovery Guru. Also, these applications detect drive-related failures only for configured drive groups/LUNs that are owned by the controller (connected to the host machine running the storage management software) or for any unassigned or hot spare (Spare-Stdby) drive.
\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 (under the Select Module option) will be able to tell if the RAID Module it is connected to is in an independent controller configuration.
\p\p\1
Related Topics\0\p
\{\3\goto "Types Of Hardware Configurations" Types Of Host-RAID Module Configurations Supported\} \p
\{\3\goto "Using Select Module" Using Select Module\} \p
\keyword "independent controller configuration"
\keyword "configuration, hardware"
\keyword "host-RAID Module configurations"

\topic "Can I Update Component Statuses On Screen?"
\0\p\1
Can I Update Component Statuses On Screen?\0
\p\p
Yes. If you want to update component statuses quickly, you can re-select the \{\2\bring_popup "RAID Module" RAID Module\} that is currently displayed in the RAID Module list 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. \p
\keyword "status change"
\keyword "updating component statuses"
\keyword "selecting RAID Modules"

\topic "How Can I Check For Component Failures?"
\0\p\1
How Can I Check For Component Failures?\0
\p\p
There are three easy ways to check for problems on your RAID Modules:
\p\p
\{\1 o \0\} Use either Recovery Guru (in the Recovery Application) or Health Check (in the Status Application) to perform an immediate check of the selected \{\2\bring_popup "RAID Module" RAID Module\}.
\p\p\1
NOTE\0: If you have component failures, Recovery Guru provides step-by-step instructions for fixing the failure.
\p\p
\{\1 o \0\} Select Message Log (in the Status Application) if you want to check for any past failures the background monitor has detected.
\p\p
\{\1 o \0\} Select Module Profile in any application if you would like a quick reference. \p
\keyword "component errors"
\keyword "checking modules"
\keyword "Status Application"
\keyword "Recovery Guru"
\keyword "failures"
\keyword "Health Check"
\keyword "Module Profile"

\topic "About A RAID Module's Controllers"
\0\p\1
How Can I Tell How Many And What Kind Of Controllers A RAID Module Has?\0
\p\p
Module Profile shows you how many and what kind of controllers a selected RAID Module has.
\p\p
1. Select a RAID Module, then Module Profile. Check the columns for Controller A and Controller B to determine if you have a single controller or a pair of controllers.
\p\p\1
NOTE\0: You can also use the Maintenance/Tuning Application to view \{\2\bring_popup "Controller Mode" controller modes\} for all your RAID Modules at once.
\p\p
2. Select Controllers under Detailed Information. \p
\{\1 o \0\} Check the Board Name to determine the kind of controller (ADP-93, Series 3, etc.).
\p\p
\{\1 o \0\} Check the Board ID to determine the model of controller (for example, 3601, 3201, etc.).
\p\p
3. Exit Module Profile (select OK) when finished. \p
\keyword "controller number"
\keyword "controller type"
\keyword "Module Profile"
\keyword "Maintenance/Tuning Application"

\topic "What Does The Device Name Mean?"
\0\p\1
What Does The Device Name Mean?\0
\p\p
The software uses the device name as an address to access the controllers in a RAID Module. These addresses are determined by the location of the RAID Module hardware and can vary according to the operating system you are using.
\p\p
For example, most UNIX operating systems use a cXtXdXsX scheme, the Windows NT operating system uses a driveX scheme, and the Networked version uses an eight character scheme you defined during installation.
\p\p\1
Related Topics\0\p
\{\3\subtopic "UNIX Device Names" UNIX Device Names\} \p
\{\3\subtopic "Windows NT Device Names" Windows NT Device Names\} \p
\{\3\subtopic "Networked Version Device Names" Networked Version Device Names\} \p
\keyword "device name"
\keyword "SCSI ID"

\topic "UNIX Device Names"
\0\p\1
UNIX Device Names\0
\p\p
UNIX uses device addresses to refer to \{\2\bring_popup "Logical Unit" logical units\}. Most UNIX addresses indicate the SCSI Host controller, \{\2\bring_popup "SCSI ID" SCSI ID\} number of the controller, logical unit number (LUN), and the slice number. However, not all UNIX systems include the slice number, such as HP-UX.
\p\p
\{\2\insert_image "rm6res.SolDevNameIcon"\}
\p\p\1
Related Topics\0\p
\{\3\goto "What Does The Device Name Mean?" What Does The Device Name Mean?\} \p
\keyword "UNIX device name"

\topic "Windows NT Device Names"
\0\p\1
Windows NT Device Names\0
\p\p
Windows NT uses device addresses to gain access to each RAID Module's controllers. Each Windows NT address represents the maximum number of \{\2\bring_popup "Logical Unit" logical units\} that any one controller could own which it limits to eight. Therefore, a device name for one controller refers to a POSSIBLE group of up to eight LUNs or Drive#. Used with the controller designation A or B, the Drive# is the first number for the eight "potential" logical units that could be assigned to that controller. For example, Controller A (Drive0) means that LUNs zero through seven are the eight LUNs that could be assigned to this controller. 
\p\p\1
IMPORTANT\0\p
\{\1 o \0\} These addresses do NOT match the disk# used in the Disk Administrator utility which represent configured logical units and corresponding filesystems.
\p\p
\{\1 o \0\} These addresses ONLY refer to a range of eight LUNs per controller and do NOT necessarily represent a configured LUN. For example, if you have a RAID Module with two controllers, each controller's device address spans a range of eight numbers. However, there is still a Windows NT limit of eight LUNs for that module (thus, these two controllers can only have a TOTAL of eight LUNs between them).
\p\p
Additionally, the order that device addresses are assigned to a controller depends (in descending order) on the port, path, and SCSI ID of the controller. The controller with the lowest port will have the first eight drive# (0-7) assigned to it. For example, assume RAID Module 1 has only one controller. RAID Module 2 has two active controllers on different ports. The device addresses are assigned to these controllers in groups of eight; so that, the logical units are assigned as follows:
\p\p
\{\1 o \0\} RAID Module 1, controller A (port 0, path 1, SCSI ID 3) has Drive8 through Drive15.
\p\p
\{\1 o \0\} RAID Module 2, controller A (port 0, path 1, SCSI ID 2) has Drive0 through Drive7.
\p\p
\{\1 o \0\} RAID Module 2, controller B (port 1, path 0, SCSI ID 1) has Drive16 through Drive23.
\p\p\1
Related Topics\0\p
\{\3\goto "What Does The Device Name Mean?" What Does The Device Name Mean?\} \p
\keyword "Windows NT device name"

\topic "Networked Version Device Names"
\0\p\1
Networked Version Device Names\0
\p\p
The Networked version of the software uses device names to gain access to each controller in the RAID Modules connected to the network. You create these names as part of the software's installation procedure.
\p\p
You need to provide unique names for each controller. See the "Installation And Support Guide" for the Networked version for specific details.
\p\p\1
Related Topics\0\p
\{\3\goto "What Does The Device Name Mean?" What Does The Device Name Mean?\} \p
\keyword "Networked device name"
\keyword "device name"

\topic "The ''Optimal (Health Check Not Done)'' Message Displays"
\0\p\1 
What If Recovery Guru Or Health Check Displays The "Optimal (Health Check Not Done)'' Message?\0
\p\p
This message most likely indicates that the controller was unable to communicate with the selected \{\2\bring_popup "RAID Module" RAID Module\}. Most likely all the \{\2\bring_popup "Logical Unit" LUNs\} are busy because some operation has them locked under exclusive access. For example, if you had no LUNs configured on your RAID Module and are currently creating the first LUN, you could see this Failure Type if you run Recovery Guru (in the Recovery Application) or Health Check (in the Status Application) before the LUN's format is complete.
\p\p
Select a different RAID Module, or wait for any operation that requires exclusive access to complete before performing another operation on the same RAID Module. \p
\keyword "Recovery Guru"
\keyword "Health Check"
\keyword "Module Profile"
\keyword "optimal (health check not done)"

\topic "The ''Selection Is Not A File'' Message Displays"
\0\p\1
What If The ''Selection Is Not A File'' Message Displays?\0
\p\p
You might see this message when you are opening a \{\2\bring_popup "Log File" log file\}, saving the log as another file, or saving a module profile. This message indicates that the filename you entered is not valid. Try again using another filename. Also, be sure that you are entering your selection on the Selection line and not the \{\2\bring_popup "Filter" Filter\} line. \p
\keyword "messages, selection is not a file"
\keyword "filter"
\keyword "messages, selection is not a file"

\topic "The ''Threshold Level Reached'' Message Displays"
\0\p\1
What If The ''Threshold Level Reached'' Message Displays?\0
\p\p
Controlling the size of the log file provides better performance of Message Log's activities. Therefore, if you see this message when you start the Status Application, you should take one of the following actions:
\p\p
\{\1 o \0\} Change the default \{\2\bring_popup "Log File" log file\} so that any future events are written to a new log. From the top menu, select Options >> Log Settings.
\p\p
\{\1 o \0\} Increase the \{\2\bring_popup "Log Size Before Notification" log size before notification\} value so that the log size is larger before you are notified again. From the top menu, select Options >> Log Settings.
\p\p
\{\1 o \0\} Save the log file to another filename. You must then delete the contents of the current default log to reduce its size. From the top menu, select File >> Save Log As.
\p\p\1
IMPORTANT\0\p
If you save the default log to a different filename because the log is getting too large, then you need to delete the contents of the log as soon as possible after saving it to another log file. You can use a standard editor to delete the contents. For example, if rmlog.log is the current default log, it continues to have messages written to it. Thus, if you do not delete the contents, it continues to be too large and you continue to receive the "Threshold Level Reached" message every time you select an application. \p
\keyword "threshold level reached"
\keyword "log size before notification"
\keyword "messages, threshold level reached"
\keyword "defaults"

\topic "What Is A Drive Group?"
\0\p\1
What Is A Drive Group?\0
\p\p
A drive group is a physical set of drives in the \{\2\bring_popup "RAID Module" RAID Module\}. The drive groups are defined during configuration. You perform all configuration tasks (for example, LUN creation/deletion, and hot spare creation) on a RAID Module and its associated drive groups.
\p\p
There are three types of drive groups: \p
\{\1 o \0\} An unassigned drive group has not been configured into \{\2\bring_popup "Logical Unit" logical units\} or hot spares. This drive group is displayed only in the Drive Groups area of the Configuration Application's main screen.
\p\p
\{\1 o \0\} A \{\2\bring_popup "Hot Spare" hot spare\} drive group has been assigned as hot spares. This drive group is displayed only in the Drive Groups area of the Configuration Application's main screen.
\p\p
\{\1 o \0\} A configured drive group has been configured into one or more logical units with the same \{\2\bring_popup "RAID Level" RAID Level\}. Each configured drive group is designated with a number (e.g. 1, 2, 3, etc.). These drive groups are displayed by number in all applications.
\p\p\1
Related Topics\0\p
\{\3\goto "What Is A Hot Spare?" What Is A Hot Spare?\} \p
\keyword "unassigned drives"
\keyword "Configuration Application"
\keyword "drive group"
\keyword "hot spare"

\topic "What Is A Logical Unit?"
\0\p\1
What Is A Logical Unit?\0
\p\p
A logical unit (LUN) is the basic structure you create on the RAID Modules to retrieve and store your data. A LUN spans one or more drives and is configured into either \{\2\bring_popup "RAID Level" RAID Level\} 0, 1, 3, or 5. More than one LUN may reside within a \{\2\bring_popup "Configured Drive Group" drive group\}, and all LUNs in the same drive group share the same physical drives and RAID Level.
\p\p
Each LUN is seen by the operating system as ONE drive. If you create only one LUN on a drive group, the terms "logical unit" and "drive group" are synonymous. However, their designated number may be different. For example, drive group 2 may contain only one LUN but its number could be LUN 3. \p
\keyword "logical units, defined"

\topic "What Is A RAID Module?"
\0\p\1
What Is A RAID Module?\0
\p\p
A RAID Module is defined as a set of drives, a set of controllers (single active, \{\2\bring_popup "Active/Passive Controller Pair" active/passive\}, or \{\2\bring_popup "Active/Active Controller Pair" active/active\}), and applicable power supplies/fans. A RAID Module is what you select to perform the various RAID tasks (such as, configuring, obtaining status, recovering, etc.).
\p\p
For example, a single unit with 20 drives and two controllers would be considered one RAID Module. However, if you have a rack-mount module, each unit contained in the cabinet is considered a RAID Module. Therefore, a cabinet containing three rack-mount units would be listed as three RAID Modules.
\p\p
By default, RAID Module numbers are assigned in the order in which the system detects them (SCSI versions), or the order in which you define them (Networked versions). The default name displayed is derived from the name of the host machine where the storage management software is installed. For example, you see <hostname>_001, <hostname>_002, etc.
\p\p
The controllers in the module have unique device names, but these vary depending on the operating system version of this software you are using. Consult the "Installation And Support Guide" specific to your operating system (especially for Networked versions of this software which require some preliminary setup tasks for the RAID Modules to be recognized and numbered). \p
\keyword "RAID Module"

\topic "What Is Parity?"
\0\p\1
What Is Parity?\0
\p\p
Parity \keyword "parity defined" is additional information stored along with the data that allows the controller to \keyword "reconstruction" reconstruct lost data on \{\2\bring_popup "RAID Level" RAID Level\} 1, 3, or 5 \{\2\bring_popup "Logical Unit" logical units\} if a drive fails.
\p\p
The storage management software performs an Automatic Parity Check/Repair operation (if enabled) that helps guarantee the data integrity of the logical unit by scanning and repairing any damaged parity. You can also perform a Manual Parity Check/Repair if desired. Parity Check/Repair performs the following functions:
\p\p
\{\1 o \0\} Scans optimal RAID 1, 3, and 5 logical units and checks the parity for each block in the logical unit. \{\2\bring_popup "RAID 1" RAID 1\} (striping and mirroring) does not have true parity, but parity check compares data on each mirrored pair, block by block. \keyword "mirrored pair"
\p\p
\{\1 o \0\} Repairs any parity inconsistencies found during the parity check. On a RAID 1 logical unit, the controller changes the data on the mirror disk to make it match the data on the data disk. On RAID 3 or 5 logical units, the controller changes the parity so that it is consistent with the data.
\p\p\4
CAUTION\0\p
\{\2\bring_popup "RAID 0" RAID Level 0\} does not have parity and, therefore, cannot be checked and repaired. Additionally, you cannot run parity check/repair on RAID 1, 3, or 5 logical units with a status other than Optimal. 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. Parity inconsistencies might indicate corrupt data. You may be able to use your operating system to verify your data.
\p\p\1
Related Topics\0\p
\{\3\goto "Using Manual Parity Check/Repair" Using Manual Parity Check/Repair\} \p
\{\3\goto "Using Auto Parity Settings" Using Auto Parity Settings\} \p

\topic "What Is RDAC?"
\0\p\1
What Is RDAC?\0
\p\p\4
CAUTION\0\p
Consult the "Installation And Support Guide" specific to your operating system for special requirements or restrictions that may apply to using RDAC. For example, you do not have RDAC support over the network connection or if the RAID Module is using the \{\2\bring_popup "Independent Controller Configuration" independent controller configuration\}.
\p\p
The Redundant Disk Array Controller (RDAC) Driver is part of the storage management software package. For RAID Modules with \{\2\bring_popup "Redundant Controller Pair" redundant controllers\}, this host-based driver manages the I/O data path. If a component fails on the data path (interface cable/terminator, controller, host adapter, etc.) that causes the host to lose communication with a controller, the driver automatically reroutes all I/O operations to the other controller.
\p\p\1
Related Topics\0\p
\{\3\subtopic "RDAC For HP-UX Using HP-PB Host Adapters" RDAC Protection For HP-UX 10.20 Using HP-PB Host Adapters\} \p
\{\3\subtopic "RDAC For HP-UX Using HSC Host Adapters" RDAC Protection For HP-UX 10.20 Using HSC Host Adapters\} \p
\{\3\subtopic "RDAC Protection For Solaris" RDAC Protection For Solaris\} \p
\{\3\subtopic "RDAC Protection For Windows NT" RDAC Protection For Windows NT\} \p
\{\3\goto "Considerations For Independent Controllers" Are There Special Considerations For Using The Independent Controllers Configuration?\} \p
\{\3\goto "Considerations For The Networked Version" Are There Special Considerations For The Networked Version?\} \p
\keyword "redundant controller support"
\keyword "RDAC"
 
\topic "RDAC For HP-UX Using HP-PB Host Adapters"
\0\p\1
RDAC Protection For HP-UX 10.20 Using HP-PB Host Adapters\0
\p\p
RDAC for HP-UX 10.20 is part of the storage management software package and is built into the disk driver (spt310) with the HP-PB Host Adapters. Special nodes for all existing logical units are created automatically during the installation process to ensure RDAC protection. Consult the "Installation And Support Guide" for your operating system for specific information.
\p\p\1
Example Of RDAC's Data Path Redundancy\0\p
The figure below illustrates how RDAC provides data path management with a redundant controller pair when the host generates a request for I/O to Controller A, but Controller A fails. Use the following Legend to follow the I/O data path shown in the figure.
\p\p\1
Legend\0\p
1. I/O request fails.
\p\p
2. Failed I/O goes back to SCSI RDAC Driver.
\p\p
3. SCSI RDAC Driver performs failover and transfers logical units to the alternate controller (Controller B).
\p\p
4. SCSI RDAC Driver re-sends I/O request back down to Controller B where it is serviced. (The host application is unaware of the transactions that have taken place to complete the I/O.)
\p\p
\{\2\insert_image "rm6res.rdac3"\}
\p\p\1
Related Topics\0\p
\{\3\goto "What Is RDAC?" What Is RDAC?\} \p
\keyword "RDAC illustrated"
\keyword "RDAC for HP-UX and HP-PB"

\topic "RDAC For HP-UX Using HSC Host Adapters"
\0\p\1
RDAC Protection For HP-UX 10.20 Using HSC Host Adapters\0
\p\p
RDAC for HP-UX 10.20 using the HSC Host Adapters has a separate RDAC Driver and an associated resolution daemon as part of the storage management software package. Special nodes for all existing logical units are created automatically during the installation process to ensure RDAC protection, and additional nodes are added any time the system is restarted and new modules have been added. When mounting filesystems on logical units, you MUST use the special device node created by the RDAC Driver to ensure RDAC protection. Consult the "Installation And Support Guide" for your operating system for specific information.
\p\p\1
Example Of RDAC's Data Path Redundancy\0\p
The figure below illustrates how RDAC provides data path management with a redundant controller pair. Normally, the host application generates a request for I/O which goes through just the SCSI Driver to get to the controllers/drives. With RDAC installed, though, the RDAC Driver and resolution daemon are added for transparent failover. This does not affect performance. As the figure shows, the host generates a request for I/O to Controller A, but Controller A fails. Use the following Legend to follow the I/O data path shown in the figure.
\p\p\1
Legend \0\p
1. I/O request fails.
\p\p
2. Failed I/O goes back to RDAC Driver.
\p\p
3. RDAC Driver asks resolution daemon for assistance.
\p\p
4. Resolution daemon performs failover through SCSI Driver and transfers logical units to the alternate controller (Controller B).
\p\p
5. Resolution daemon tells RDAC Driver the new path is ready and RDAC Driver re-sends I/O request back down to Controller B where it is serviced. (The host application is unaware of the transactions that have taken place to complete the I/O.)
\p\p
\{\2\insert_image "rm6res.rdac1"\}
\p\p\1
Related Topics\0\p
\{\3\goto "What Is RDAC?" What Is RDAC?\} \p
\keyword "RDAC illustrated"
\keyword "RDAC for HP-UX and HSC"

\topic "RDAC Protection For Solaris"
\0\p\1
RDAC Protection For Solaris\0
\p\p
RDAC for Solaris has an associated resolution daemon as part of the storage management software package. When mounting filesystems on logical units, you can use either the Solaris standard device node ctXdXsX or the special device node created by the RDAC Driver. \1 Either device node offers RDAC protection.
\p\p
Special RDAC Nodes\0\p
The special nodes were created automatically during the installation process, and additional nodes are added any time the system is restarted and new modules have been added. Consult the "Installation And Support Guide" for your operating system for specific information.
\p\p\1
Example Of RDAC's Data Path Redundancy\0\p
The figure below illustrates how RDAC provides data path management with a redundant controller pair. Normally, the host application generates a request for I/O which goes through just the SCSI Driver to get to the controllers/drives. With RDAC installed, though, the RDAC Driver and resolution daemon are added for transparent failover. This does not affect performance. As the figure shows, the host generates a request for I/O to Controller A, but Controller A fails. Use the following Legend to follow the I/O data path shown in the figure.
\p\p\1
Legend\0\p
1. I/O request fails.
\p\p
2. Failed I/O goes back to RDAC Driver.
\p\p
3. RDAC Driver asks resolution daemon for assistance.
\p\p
4. Resolution daemon performs failover through SCSI Driver and transfers logical units to the alternate controller (Controller B).
\p\p
5. Resolution daemon tells RDAC Driver the new path is ready and RDAC Driver re-sends I/O request back down to Controller B where it is serviced. (The host application is unaware of the transactions that have taken place to complete the I/O.)
\p\p
\{\2\insert_image "rm6res.rdac1"\}
\p\p\1
Related Topics\0\p
\{\3\goto "What Is RDAC?" What Is RDAC?\} \p
\keyword "RDAC illustrated"
\keyword "RDAC for Solaris"
 
\topic "RDAC Protection For Windows NT"
\0\p\1
RDAC Protection For Windows NT\0
\p\p
RDAC for Windows NT is part of the storage management software package and is built into the array class driver (symarray.sys).
\p\p\1
Example Of RDAC's Data Path Redundancy\0\p
The figure below illustrates how RDAC provides data path management with a redundant controller pair when the host generates a request for I/O to Controller A, but Controller A fails. Use the following Legend to follow the I/O data path shown in the figure.
\p\p\1
Legend\0\p
1. I/O request fails.
\p\p
2. Failed I/O goes back to RDAC Array Class Driver.
\p\p
3. RDAC Array Class Driver performs failover and transfers logical units to the alternate controller (Controller B).
\p\p
4. RDAC Array Class Driver re-sends I/O request back down to Controller B where it is serviced. (The host application is unaware of the transactions that have taken place to complete the I/O.)
\p\p
\{\2\insert_image "rm6res.rdac2"\}
\p\p\1
Related Topics\0\p
\{\3\goto "What Is RDAC?" What Is RDAC?\} \p
\keyword "RDAC illustrated"
\keyword "RDAC for Windows NT"

\topic "What Is Reconstruction?"
\0\p\1
What Is Reconstruction?\0
\p\p
\{\2\bring_popup "Reconstruction" Reconstruction\} is the process used to restore a \{\2\bring_popup "Degraded Mode" degraded\} RAID 1, 3, or 5 logical unit to its original state after you replace a single, failed drive.
\p\p\1
When Does Reconstruction Start?\0\p
Reconstruction should start automatically when you physically replace a single \keyword "failed drive" failed drive in a RAID 1, 3, or 5 logical unit. Note that the drive's fault light comes on momentarily at the beginning of reconstruction, but then goes off and the drive activity lights flash steadily throughout the \keyword "reconstruction" reconstruction process. 
\p\p\1
How Does Reconstruction Work?\0\p
During reconstruction, the \{\2\bring_popup "Controller" controller\} recalculates data on the replaced drive by using data and \{\2\bring_popup "Parity" parity\} from the other drives in the logical unit. The controller then writes this data to this replaced drive. \p

\topic "What Is SNMP?"
\0\p\1
What Is SNMP?\0
\p\p
The Simple Network Management Protocol (SNMP) notification is an option that you may enable when installing this software. It allows this software to send remote notification of RAID events to designated network management machines using SNMP \{\2\bring_popup "Trap" traps\}. See the ''Installation And Support Guide'' for your operating system for details on enabling this notification option. \p
\keyword "SNMP, defined"
\keyword "error notification options"
\keyword "remote notification"

\topic "Why Are Some Options Grayed Out?"
\0\p\1
Why Are Some Options Grayed Out?\0
\p\p
If you select All RAID Modules, you cannot select some options, such as \keyword "Locate Module" Locate Module, \keyword "Module Profile" Module Profile, \keyword "Save Module Profile" Save Module Profile, and \keyword "LUN Reconstruction" LUN Reconstruction. If these buttons are grayed out, change your \keyword "RAID Module" RAID Module selection to a specific \{\2\bring_popup "RAID Module" RAID Module\}.
\p\p
Similarly, some menu options are not active unless you have selected a specific option. For example, Open Log, Save Log As, and Refresh All, from the File top menu, are grayed out if you are not in \keyword "Message Log" Message Log. Also, Copy to Clipboard, from the Edit top menu, is grayed out unless you are in the detailed information screen of Message Log or \keyword "Health Check" Health Check. \p
\keyword "menu options"

\topic "Why Aren't LUNs Visible On Screen?"
\0\p\1
Why Would Logical Units Not Be Visible On The Screen?\0
\p\p
Any time a long operation (such as formatting, firmware upgrade, parity check/repair, etc.) is being performed on \{\2\bring_popup "Logical Unit" logical units\}, these logical units do not appear on screen EXCEPT in the application where the operation was initiated. These logical units are locked out of the other applications so that no other operations can be performed on them until the current operation is complete. For example, if you started a format in the Recovery Application, these logical units show a "Formatting" status in Recovery, but do not display in any other application. \p
\keyword "missing logical units"

\topic "Why Did Locate Module Take A Long Time?"
\0\p\1
Why Did Locate Module Take A Long Time?\0
\p\p
If you have heavy I/O or are currently making configuration changes, you might notice a delay when you select Locate Module. \p
\keyword "Locate Module"

\topic "Why Doesn't Locate Module Work?"
\0\p\1
Why Doesn't Locate Module Work?\0
\p\p
Locate Module \keyword "Locate Module" may not help you identify a RAID Module under three 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, then the software cannot flash the activity lights on the drives. In this case, however, the summary activity indicator still flashes and you can check for a fault light on the drive canisters.
\p\p
\{\1 o \0\} If you have a controller version earlier than the Series 3 and the selected RAID Module has no configured logical units (that is, all \{\2\bring_popup "Unassigned Drive Group" unassigned \} drives), then the software is unable to communicate with these drives and cannot flash their activity lights. \p

\topic "Can Save Module Profile Restore My Configuration?"
\0\p\1
Can I Use Save Module Profile Information To Restore My Configuration?\0
\p\p
You cannot use this information to automatically restore your module's configuration; however, Save Module Profile information copies the information found in Module Profile and the main Configuration Application 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 to send information to your Customer Services Representative for troubleshooting. \p
\keyword "Save Module Profile"
\keyword "module information"
\keyword "print profile"

\topic "Types Of Hardware Configurations"
\0\p\1
Types Of Host-RAID Module Configurations Supported\0
\p\p
The storage management software supports three main configurations of host machines connected by SCSI Buses to the \{\2\bring_popup "RAID Module" 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 multi-host configuration. Be sure to consult the restrictions in the operating-system specific "Installation And Support Guide."
\p\p
\{\1 o \0\}\1 Single-host configuration\0 -- One host machine is connected by two SCSI Buses to each controller in a RAID Module. The two SCSI Buses are required for maximum \{\2\bring_popup "RDAC Driver" RDAC\} failover support for \{\2\bring_popup "Redundant Controller Pair" redundant controllers\}.
\p\p\1
NOTE\0: This is the recommended configuration with the storage management software installed on the host for fullest functionality and complete RDAC failover support with dual controllers.
\p\p\1
IMPORTANT\0\p
Although this configuration also supports RAID Modules that have a single-controller or dual controllers on the same SCSI Bus, you do NOT have complete RDAC data path protection with either of these configurations. The host adapter and cable become a single-point of failure and any data path 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 SCSI connection (SCSI Bus and host adapter) in the host system.
\p\p
\{\1 o \0\}\1 Multi-host configuration\0 -- Two host machines are each connected by two SCSI Buses to both of the controllers in a RAID Module. With this storage management software installed on each host machine, both hosts have complete visibility of both controllers, all data paths, and all configured \{\2\bring_popup "Drive Group" drive groups\}/\{\2\bring_popup "Logical Unit" logical units\} in a RAID Module, plus RDAC failover support for the redundant controllers. However, in this configuration, you must use caution when performing storage management tasks that need exclusive access. Especially when creating and deleting 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 o \0\}\1 Independent controller configuration\0 -- Two host machines are connected to a dual-controller RAID Module. One host machine is connected by a SCSI Bus to one controller, and a second host machine is connected by another SCSI Bus to the other controller. Each host machine and its storage management software see the controller and the 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\1
IMPORTANT\0\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 LUNs or the operation will fail from one of the hosts.
\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 configurations mentioned above. However, the Networked version (under the Select Module option) will be able to tell if the RAID Module it is connected to is in an independent controller configuration.
\p\p\1
IMPORTANT\0\p
Be sure to consult the "Installation And Support Guide" specific to your operating system for details if you are using the Independent Controller configuration. For more details on any of these configurations consult this software's "User Guide."
\p\p\1
Related Topics\0\p
\{\3\goto "Considerations For Independent Controllers" Are There Special Considerations For Using The Independent Controllers Configuration?\} \p
\{\3\goto "What Is A Drive Group?" What Is A Drive Group?\} \p
\{\3\goto "What Is A Logical Unit?" What Is A Logical Unit?\}
\{\3\goto "What Is A RAID Module?" What Is A RAID Module?\} \p
\{\3\goto "What Is RDAC?" What Is RDAC?\} \p
\keyword "independent controller configuration"
\keyword "multi-host configuration"
\keyword "single-host configuration"
\keyword "host-RAID Module configurations"
\keyword "configuration, hardware"

\topic "Configuration Application"
\0\p\1
Configuration Application\0
\p\p
\{\3\subtopic "Configuration Task Summary" Task Summary\}
\p\p
\{\3\subtopic "Using List/Locate Drives" List/Locate Drives\}
\p\p
\{\3\subtopic "Using Create LUN" Create LUN\}
\p\p
\{\3\subtopic "Configuration -- Quick And Easy" Learning By Example -- Quick And Easy Configuration\}
\p\p
\{\3\subtopic "Configuration -- Custom" Learning By Example -- Custom Configuration\}
\p\p
\{\3\subtopic "Changing LUN Parameters" Changing Logical Unit Parameters\}
\p\p
\{\3\subtopic "Using Create Hot Spare" Create Hot Spare\}
\p\p
\{\3\subtopic "Using Delete" Delete\}
\p\p
\{\3\subtopic "Troubleshooting For Configuration" Troubleshooting/Common Questions\} 
\p\p\1
Related Topics\0\p
\{\3\goto "Tasks For All Applications" Task Summary\} \p
\{\3\goto "Troubleshooting For All Applications" Troubleshooting/Common Questions For All Applications\} \p

\topic "Configuration Task Summary"
\0\p\1
CONFIGURATION TASK SUMMARY\0
\p\p
\{\2\bring_popup "List/Locate Drive Tasks" Viewing A List of Drives\}
\p\p
\{\2\bring_popup "Locate Drive Tasks" Locating Drives\}
\p\p
\{\2\bring_popup "Create LUN Tasks" Creating Logical Units/Drive Groups\}
\p\p
\{\2\bring_popup "Add LUN Tasks" Adding Logical Units To An Existing Drive Group\}
\p\p
\{\2\bring_popup "Create Hot Spare Tasks" Creating Hot Spares\}
\p\p
\{\2\bring_popup "Delete Tasks" Deleting Logical Units/Hot Spares\}
\p\p
\{\2\bring_popup "Change LUN Parameters Tasks" Changing Logical Unit Parameters\} 
\p\p\1
Related Topics\0\p
\{\3\goto "Configuration Application" Configuration Application\} \p
\{\3\goto "Tasks For All Applications" Task Summary For All Applications\}

\popup "List/Locate Drive Tasks"
\0\p
Highlight a drive group, then select List/Locate Drives to determine the physical location of the drives that comprise a logical unit/drive group. Also, the list of drives displays location, capacity, and status information.
\p\p
If you select a RAID 1 drive group, the mirrored-pair drives are indicated by a number appearing in front of the drive location information. (For example, (1) appears in front of the first mirrored pair, (2) appears in front of the second mirrored pair. etc.) \p
\keyword "List/Locate Drives"
\keyword "drives, list"

\popup "Locate Drive Tasks"
\0\p
Using List/Locate Drives, select Locate to flash the activity lights on the appropriate drives in the drive group. \p
\keyword "locating drives"
\keyword "List/Locate Drives"

\popup "Create LUN Tasks"
\0\p
Select Create LUN to create new logical units (LUN) from the unassigned drive group, or to add LUNs to an existing drive group that has remaining capacity. \p
\keyword "Create LUN"
\keyword "adding logical units"
\keyword "logical units, adding"
\keyword "logical units, creating"

\popup "Add LUN Tasks"
\0\p
Highlight a drive group with remaining capacity in the Drive Groups area of the main Configuration screen. Then select Create LUN to configuration the new logical unit. \p

\popup "Create Hot Spare Tasks"
\0\p
Highlight the unassigned drive group to create hot spares. These drives act as standbys in case any drive fails in a RAID 1, 3, or 5 logical unit on the RAID Module. \p
\keyword "Create Hot Spare"
\keyword "hot spare"
\keyword "adding hot spares"

\popup "Delete Tasks"
\0\p
Highlight the drive group/hot spare, select Delete, then select the LUNs you want to delete from the list. Options include deleting all of the logical units (LUN) in a drive group, individual LUNs within a drive group, or standby hot spares (if supported).
\p\p
When you select Delete, you may still Cancel without actually deleting any logical units or hot spares. \p
\keyword "Delete"
\keyword "logical units, deleting"
\keyword "hot spare"

\popup "Change LUN Parameters Tasks"
\0\p
Changing most logical unit (LUN) parameters require you to delete the LUN using Delete and then to recreate it using Create LUN. \p
\keyword "changing logical unit parameters"
\keyword "parameters, logical unit"
\keyword "logical unit parameters"

\topic "Using List/Locate Drives"
\0\p\1
Using List/Locate Drives\0
\p\p\1
When To Use\0\p
Use to view a list of drives that comprise a logical unit/\{\2\bring_popup "Drive Group" drive group\} (unassigned, hot spare, or configured). You must highlight a drive group before selecting this option.
\p\p
You can also locate the drives in the drive group when you are viewing the list of drives. Select Locate >> Start to flash the \keyword "drive activity lights" \{\2\bring_popup "Activity Lights" activity lights\} on the appropriate drives in the drive group.
\p\p
One of the best times to use this option is right after you have installed your RAID Module so that you can determine the initial logical unit/drive group configuration and the associated physical drives.
\p\p\1
What Happens\0\p
A list of drives displays for the drive group you highlighted from the main Configuration screen. This list includes location, capacity, and status information for each drive. 
\p\p\1
Did You Know?\0\p
\{\1 o \0\} The drive location corresponds to a specific drive in the RAID Module, and indicates the \{\2\bring_popup "SCSI Channel" SCSI Channel\} number and \{\2\bring_popup "SCSI ID" SCSI ID\} for that drive (in that order). For example, [2,1] corresponds to a drive at location SCSI Channel 2 and SCSI ID 1. Use the location information to match it to a unique drive to help locate it in the RAID Module.
\p\p
\{\1 o \0\} If there is a drive status of Failed, Offline, Unresponsive, or Warning go to the \keyword "Recovery Application" Recovery Application and select Recovery Guru.
\p\p
\{\1 o \0\} If you select the \{\2\bring_popup "Hot Spare" hot spare\} drive group, the list shows the hot spares and a status of In Use or Standby. \p\1
In Use\0 -- the hot spare is currently being used as a replacement for a failed drive. The location of the drive being covered by this hot spare is indicated in brackets. \p\1
Standby\0 -- the hot spare is ready for use in case a drive fails.
\p\p
\{\1 o \0\} If you select a \{\2\bring_popup "RAID 1" RAID 1\} drive group, the mirrored-pair drives are indicated by a number appearing in front of the drive location information. (For example, (1) appears in front of the first mirrored pair, (2) appears in front of the second mirrored pair. etc.)
\p\p\1
For Best Results\0\p
Use Locate when no I/Os are occurring so that the flashing of the activity lights can be distinguished from normal I/O.
\p\p\1
Related Topics\0\p
\{\3\subtopic "What Are The Different Flashing Patterns?" What Are The Different Flashing Patterns?\} \p
\{\3\goto "Using Locate Module" Using Locate Module\} \p
\keyword "List/Locate Drives"
\keyword "drives, locating"
\keyword "identifying drives"

\topic "What Are The Different Flashing Patterns?"
\0\p\1
What Are The Different Flashing Patterns?\0
\p\p
When you select \keyword "List/Locate Drives" List/Locate Drives >> Locate >> Start for a particular \{\2\bring_popup "Drive Group" drive group\}, the \keyword "activity lights" \{\2\bring_popup "Activity Lights" activity lights\} on the drives flash until you select Stop. Depending on the type and \{\2\bring_popup "RAID Level" RAID Level\} of the selected drive group, the activity lights either flash sequentially or simultaneously: 
\p\p
\{\1 o \0\} Unassigned, Hot Spare, or RAID 0 drive groups -- 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 -- 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 drives' activity lights will flash. You should 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\0\p
\{\3\goto "Using List/Locate Drives" Using List/Locate Drives\} \p

\topic "Using Create LUN"
\0\p\1
Using Create LUN
\p\p\4
CAUTION\0\p
If you are using the networked version of the storage management software or a dual-host-RAID Module configuration (such as \{\2\bring_popup "Multi-Host Configuration" multi-host\} or \{\2\bring_popup "Independent Controller Configuration" independent controller\}),  it is possible to open a Configuration Application and begin Create LUN from more than one host/station. However, you must be sure that are using only one configuration session at a time or the LUN creation will fail for one of the hosts/stations.
\p\p\1
When To Use\0\p
Use to: \p
\{\1 o \0\} Create new \{\2\bring_popup "Logical Unit" logical units\} (LUN) from the \{\2\bring_popup "Unassigned Drive Group" unassigned drive group\}. \keyword "Create LUN"
\p\p\1
NOTE\0: When you create LUNs from the unassigned drive group, you also create a corresponding \{\2\bring_popup "Configured Drive Group" drive group\}.
\p\p
\{\1 o \0\} Add LUNs to an existing drive group that has remaining capacity. You cannot change the RAID Level and number of drives because any LUNs on a specific drive group must use the same RAID Level and the same set of drives. \keyword "adding logical units"
\p\p\1
NOTE\0: If you need to change any logical unit parameters (for example, RAID Level, segment size, etc.) after the logical units have been created, select the "Changing Logical Unit Parameters" topic in the list below.
\p\p
See Related Topics at the bottom of this screen for additional information on Create LUN.
\p\p\1
What Happens\0\p
Displays the main Create LUN screen. At this screen, you can specify the following parameters: \p
\{\1 o \0\}\1 RAID Level\0 -- can only specify if you are creating from unassigned drives.
\p\p
\{\1 o \0\}\1 Number of drives\0 -- can only specify if you are creating from unassigned drives.
\p\p
\{\1 o \0\}\1 Number of logical units\0 -- depends on the \keyword "maximum, logical units" maximum LUNs allowed on your operating system and the number of LUNs already created.
\p\p\1
NOTE\0: The Available Capacity field changes depending on the \{\2\bring_popup "RAID Level" RAID Level\} and number of drives you select and reflects the actual capacity that is available for use. Remember that all RAID Levels (except RAID 0) use part of the drives' capacity for redundancy. \keyword "available capacity"
\p\p
After you have specified the three parameters (RAID Level, drives, and LUNs), you can select: \p
\{\1 o \0\}\1 Options\0 -- to view or customize the other LUN parameters (such as LUN capacities, drive selection, caching parameters, etc.). \keyword "logical unit options"
\p\p
\{\1 o \0\}\1 Create\0 -- to create/format the logical units.
\p\p\1
IMPORTANT\0\p
\{\1 o \0\} If all of the drives in the unassigned drive group are failed, the Create LUN button is grayed out.
\p\p
\{\1 o \0\} If a \keyword "RAID Level" RAID Level is grayed out, it means that the current number of drives selected is not a valid number for the particular RAID Level. For example, RAID 1 must always use an even number of drives.
\p\p
\{\1 o \0\} Some operating systems require that you reboot your system after making ANY configuration changes so that the operating system can recognize the new configuration. Consult the "Installation And Support Guide" for your operating system for specific information.
\p\p
\{\1 o \0\} If you make any changes on the main Create screen AFTER you have made changes in Options, all changes in Options are undone. For example, if you changed the segment size of a logical unit from 16 to 32 but then changed the number of LUNs in the main Create screen, the segment size would return back to 16 (blocks).
\p\p
\{\1 o \0\} If you have deleted all the LUNs on a RAID Module and are re-creating new LUNs, WAIT for the format to finish on the first LUN/drive group before creating additional new drive groups to make sure the operation completes successfully. Consult the troubleshooting section of the "User Guide" for more information on deleting ALL drive groups/LUNs.
\p\p
\{\1 o \0\} If your unassigned drive group contains drives with different capacities (such as 2 GB or 4 GB), be sure to use Options >> Drive Selection to indicate that you want to use EITHER the smaller capacity drives ONLY or the larger capacity drives ONLY. With mixed capacity drives in the unassigned drive group, the Configuration Application initially bases the available capacity of this drive group (displayed in the main Create LUN screen) on the capacity of the smaller drives. For example if the unassigned drive group consisted of 5 drives (three 2 GB drives and two 4 GB drives), then the available capacity shown would be 10 GB (5 x 2 GB). Furthermore, if you create LUNs using mixed capacity drives, you are using only the smallest capacity available (2 GB) and you CANNOT access the additional capacity on the larger drives.
\p\p\1
Did You Know?\0\p
\{\1 o \0\} Normally, when creating logical units, you should use all of the available capacity.
\p\p
\{\1 o \0\} When you create new logical units (LUN) from the unassigned drive group, a new configured drive group is designated that contains the LUNs you specify. The drive group is assigned a number and is indicated in the Drive Groups area of the main Configuration screen and used in all other applications.
\p\p\1
Related Topics\0\p
\{\3\goto "Considerations For Different Drive Capacities" Any Special Considerations For A Module With Different Drive Capacities?\} \p
\{\3\goto "Changing LUN Parameters" Changing Logical Unit Parameters\} \p
\{\3\goto "Configuration -- Custom" Learning By Example -- Custom Configuration\} \p
\{\3\goto "Configuration -- Quick And Easy" Learning By Example -- Quick And Easy Configuration\} \p
\{\3\subtopic "Selecting The Create Button" Selecting The Create Button\} \p
\{\3\subtopic "Selecting The Options Button" Selecting The Options Button\} \p
\{\3\subtopic "Specifying Number Of Drives" Specifying Number Of Drives\} \p
\{\3\subtopic "Specifying Number Of LUNs" Specifying Number Of LUNs\} \p
\{\3\subtopic "Specifying RAID Level" Specifying RAID Level\} \p
\keyword "logical units, creating"
\keyword "logical units, adding"
\keyword "missing logical units"
\keyword "formatting logical units"

\topic "Selecting The Create Button"
\0\p\1
Selecting The Create Button\0
\p\p
If you select Create WITHOUT making changes in Options (such as LUN capacity, segment size, etc.), the following occurs: \p
\{\1 o \0\} The \{\2\bring_popup "RAID Level" RAID Level\}, number of drives, and number of logical units (LUN) you specified are used to create equal-sized LUNs based on the available capacity and default Options settings.
\p\p
\{\1 o \0\} If you specified 1 LUN, then 1 LUN is created using the entire available capacity.
\p\p
\{\1 o \0\} If you are creating new logical units from the unassigned drive group, a new configured drive group appears containing the logical units you specify. The drive group is assigned the next available number and is indicated in the Drive Groups area of the main Configuration screen.
\p\p
If you select Create AFTER making changes in Options, the following occurs: \p
\{\1 o \0\} The LUNs are created based on the options you changed (for example, LUN capacity, segment size, etc.) and the RAID Level, number of drives, and number of LUNs specified.
\p\p
Once you select Create, you see a confirmation screen before returning to the main Configuration screen. The LUN creation/formatting occurs in the background so that you can perform other Configuration tasks (such as creating logical units on another drive group) or select another application (such as Status or Maintenance/Tuning) while the LUN is being created.
\p\p\1
Related Topics\0\p
\{\3\goto "How The Options Screen Works" How The Options Screen Works\} \p
\{\3\goto "Selecting The Options Button" Selecting The Options Button\} \p
\{\3\goto "Using Create LUN" Using Create LUN\} \p
\keyword "beginning a logical unit format"
\keyword "formatting logical units"

\topic "Selecting The Options Button"
\0\p\1
Selecting The Options Button\0
\p\p
If you select Options from the main Create screen, you can view or change these other logical unit (LUN) parameters:
\p\p
\{\3\subtopic "LUN Capacity Option" LUN Capacity\}
\p\p
\{\3\subtopic "Drive Selection Option" Drive Selection\}
\p\p
\{\3\subtopic "Caching Parameters Option" Caching Parameters\}
\p\p
\{\3\subtopic "Segment Size Option" Segment Size\}
\p\p
\{\3\subtopic "LUN Assignment Option" LUN Assignment\}
\p\p\1
Related Topics\0\p
\{\3\subtopic "How The Options Screen Works" How The Options Screen Works\} \p
\{\3\goto "Selecting The Create Button" Selecting The Create Button\} \p
\{\3\goto "Using Create LUN" Using Create LUN\} \p
\keyword "logical units, options"
\keyword "changing logical unit parameters"
\keyword "Options screen"

\topic "LUN Capacity Option"
\0\p\1
LUN Capacity Option\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 remaining capacity. If they do, the Remaining Group Capacity field indicates the amount exceeded.
\p\p\1
Did You Know?\0\p
Normally, use all of the available capacity. That is, the Remaining Group Capacity should be 0 after making changes to the capacities of the LUNs.
\p\p\1
Related Topics\0\p
\{\3\goto "How The Options Screen Works" How The Options Screen Works\} \p
\{\3\goto "Selecting The Options Button" Selecting The Options Button\} \p
\{\3\goto "Using Create LUN" Using Create LUN\} \p
\keyword "capacity, logical units"
\keyword "logical unit capacity"
\keyword "remaining group capacity"
\keyword "drive group, capacity"
\keyword "capacity, drive groups"
\keyword "logical unit parameters"
\keyword "changing LUN capacity"

\topic "Drive Selection Option"
\0\p\1
Drive Selection Option\0
\p\p
Allows you to change the set of drives used for the \{\2\bring_popup "Configured Drive Group" drive group\} and to view the individual capacity of each drive.
\p\p\1
IMPORTANT\0\p
\{\1 o \0\} This option is grayed out if you are creating additional LUNs on an existing drive group.
\p\p
\{\1 o \0\} The Move button is grayed out if you specified the maximum number of remaining (unassigned) drives in the main Create screen.
\p\p
\{\1 o \0\} 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 main Create screen. If you do not, you see an error message and cannot continue until these numbers match.
\p\p
\{\1 o \0\} For best performance, you should specify drives over as many drive 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 these 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 drive channel fails.
\p\p
\{\1 o \0\} If your unassigned drive group contains drives with different capacities (such as 2 GB or 4 GB), use Options >> Drive Selection to indicate that you want to use EITHER the smaller capacity drives ONLY or the larger capacity drives ONLY. With mixed capacity drives in the unassigned drive group, the Configuration Application initially bases the available capacity of this drive group (displayed in the main Create LUN screen) on the capacity of the smaller drives. For example, if the unassigned drive group consisted of 5 drives (three 2 GB drives and two 4 GB drives), then the available capacity shown would be 10 GB (5 x 2 GB). Furthermore, if you create LUNs using mixed capacity drives, you are using only the smallest capacity available (2 GB) and you CANNOT access the additional capacity on the larger drives.
\p\p\1
Did You Know?\0\p
\{\1 o \0\} Normally, you should use the default drives shown.
\p\p
\{\1 o \0\} You can highlight drives in both the Unselected and Selected lists and then select Move.
\p\p
\{\1 o \0\} If you are configuring a \{\2\bring_popup "RAID 1" RAID 1\} drive group, the mirrored-pair drives are indicated by a number appearing in front of the drive location information. (For example, (1) appears in front of the first mirrored pair, (2) appears in front of the second mirrored pair. etc.)
\p\p\1
Related Topics\0\p
\{\3\goto "Considerations For Different Drive Capacities" Any Special Considerations For A Module With Different Drive Capacities?\} \p
\{\3\goto "How The Options Screen Works" How The Options Screen Works\} \p
\{\3\goto "Selecting The Options Button" Selecting The Options Button\} \p
\{\3\goto "Using Create LUN" Using Create LUN\} \p
\keyword "selecting drives"
\keyword "drives, specifying selection"
\keyword "logical unit parameters"

\topic "Caching Parameters Option"
\0\p\1
Caching Parameters Option\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 logical unit you create.
\p\p\4
CAUTION\0\p
\{\1 o \0\} Selecting Cache Without Batteries allows write caching to continue even without battery backup or if the batteries are discharged completely or not fully charged. Normally, write caching is temporarily turned off if no batteries are detected or until the batteries are charged. However, enabling this 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 o \0\} Selecting 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 >> Controllers to determine if both controllers in the pair have the same size cache BEFORE enabling this parameter.
\p\p\1
IMPORTANT\0\p
This option is grayed out if the controllers in the RAID Module do not support caching.
\p\p\1
Did You Know?\0\p
\{\1 o \0\} There are several conditions (such as low battery power, etc.) where the controller may temporarily turn off the cache settings until the condition is back to normal unless you have enabled the cache without batteries option. In such cases, Module Profile >> LUNs indicates when caching is enabled, but inactive.
\p\p
\{\1 o \0\} Use the \keyword "Maintenance/Tuning Application" Maintenance/Tuning Application if you need to change any caching parameters after creating the logical units.
\p\p\1
Related Topics\0\p
\{\3\goto "How The Options Screen Works" How The Options Screen Works\} \p
\{\3\goto "Selecting The Options Button" Selecting The Options Button\} \p
\{\3\goto "Using Create LUN" Using Create LUN\} \p
\{\3\goto "What Is Cache Memory?" What Is Cache Memory?\} \p
\keyword "setting cache parameters"
\keyword "caching parameters"
\keyword "write caching"
\keyword "write cache mirroring"
\keyword "cache without batteries"
\keyword "logical unit parameters"
\keyword "changing caching parameters"

\topic "Segment Size Option"
\0\p\1
Segment Size Option\0
\p\p
Allows you to change the \{\2\bring_popup "Segment Size" segment size\} for each logical unit (LUN) you create. Normally, you should use the \keyword "segment size parameter" default segment size shown (the values provided are based on the \{\2\bring_popup "RAID Level" RAID Level\} specified for the drive group/LUNs).
\p\p\1
Related Topics\0\p
\{\3\goto "How The Options Screen Works" How The Options Screen Works\} \p
\{\3\goto "Selecting The Options Button" Selecting The Options Button\} \p
\{\3\goto "Using Create LUN" Using Create LUN\} \p
\keyword "changing segment size"
\keyword "logical unit parameters"

\topic "LUN Assignment Option"
\0\p\1
LUN Assignment Option\0
\p\p
Allows you to change which controller owns the new drive group/ \{\2\bring_popup "Logical Unit" LUN\} you create.
\p\p\1
IMPORTANT\0\p
\{\1 o \0\} 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\1
Did You Know?\0\p
\{\1 o \0\} The display shows you which controller owns the current drive groups/LUNs.
\p\p
\{\1 o \0\} Normally, you should use the default controller selected under the Assign Group To Controller area.
\p\p
\{\1 o \0\} The capacity shown is the \keyword "total capacity" total capacity available on the drive group. It is not the total capacity of the LUNs configured on the drive group unless the LUNs have used all of the capacity. \keyword "drive group, capacity"
\p\p
\{\1 o \0\} The only reason to change the default is to be sure that a particular controller owns a specific drive group/LUNs.
\p\p
\{\1 o \0\} Unless you use this option or if the RAID Module has an independent controller configuration, the LUNs are balanced across active controller pairs on a drive-group basis. The odd-numbered drive groups are assigned to one active controller and the even-numbered drive groups are assigned to the other active controller.
\p\p
\{\1 o \0\} Use the \keyword "Maintenance/Tuning Application" Maintenance/Tuning Application if you want to change any LUN ownership between controllers after creating the logical units.
\p\p\1
Related Topics\0\p
\{\3\goto "How The Options Screen Works" How The Options Screen Works\} \p
\{\3\goto "Selecting The Options Button" Selecting The Options Button\} \p
\{\3\goto "Using Create LUN" Using Create LUN\} \p
\keyword "capacity, drive groups"
\keyword "assigning logical units"
\keyword "balancing logical units"
\keyword "LUN Assignment"
\keyword "logical unit parameters"
\keyword "changing LUN Assignment"

\topic "How The Options Screen Works"
\0\p\1
How The Options Screen Works\0
\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 \keyword "Options screen" Options screen return to the same values as when you first entered the Options screen.
\p\p\1
Changing Options\0\p
\{\1 o \0\} All options are listed across the top of the screen. Select one to view/change that option. The area below the options changes to reflect the option you selected.
\p\p
\{\1 o \0\} You can switch between options without losing changes.
\p\p
\{\1 o \0\} If you change any option settings and then select OK, the changes are saved and the main Create screen displays again. Therefore, make changes to any options you want before selecting OK.
\p\p
\{\1 o \0\} If you select Cancel, ALL option settings are canceled and you are returned to the main Create screen. Use Reset if you want to reset the values for a particular option.
\p\p
\{\1 o \0\} 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
Related Topics\0\p
\{\3\goto "LUN Capacity Option" LUN Capacity\} \p
\{\3\goto "Drive Selection Option" Drive Selection\} \p
\{\3\goto "Caching Parameters Option" Caching Parameters\} \p
\{\3\goto "Segment Size Option" Segment Size\} \p
\{\3\goto "LUN Assignment Option" LUN Assignment\} \p
\{\3\goto "Selecting The Options Button" Selecting The Options Button\} \p
\{\3\goto "Using Create LUN" Using Create LUN\} \p
\keyword "changing logical unit parameters"
\keyword "Create LUN"

\topic "Specifying Number Of Drives"
\0\p\1
Specifying Number Of Drives\0
\p\p\1
When To Use\0\p
Use to indicate how many drives you want in the \{\2\bring_popup "Configured Drive Group" drive group\}/logical units (LUN) you are going to create.
\p\p\1
What Happens\0\p
The Available Capacity \keyword "available capacity" field changes depending on the \{\2\bring_popup "RAID Level" RAID Level\} and number of drives you select and reflects the actual capacity that is available for use. Remember that all RAID Levels (except RAID 0) use part of the drives' capacity for redundancy.
\p\p\1
IMPORTANT\0\p
\{\1 o \0\} The number of drives provided in the drive list could be less than the number shown in the \{\2\bring_popup "Unassigned Drive Group" unassigned drive group\}. There are two main reasons: \p
(1) Your operating system and/or RAID Module's controller has limitations on how many drives can comprise a single drive group; therefore, the list only shows the maximum allowed. \keyword "logical units, limitations"
\p\p
(2) Any drives that have failed in the unassigned drive group are not available for configuration and are not listed.
\p\p
\{\1 o \0\} If you select a certain number of drives and a \keyword "RAID Level" RAID Level is grayed out, the current number of drives selected is not a valid number for that RAID Level. For example, RAID 1 must always use an even number of drives.
\p\p
\{\1 o \0\} If you are creating additional logical units on an existing drive group, you cannot change the number of drives. Any logical units on a specific drive group must use the same RAID Level and the same set of drives. \keyword "changing number of drives"
\p\p\1
Related Topics\0\p
\{\3\goto "Changing LUN Parameters" Changing Logical Unit Parameters\} \p
\{\3\goto "Using Create LUN" Using Create LUN\} \p
\keyword "drives, specifying number"
\keyword "logical unit parameters"

\topic "Specifying Number Of LUNs"
\0\p\1
Specifying Number Of LUNs\0
\p\p\1
When To Use\0\p
Use to indicate how many \{\2\bring_popup "Logical Unit" logical units\} (LUN) you want to create either on a new drive group or on an existing \{\2\bring_popup "Configured Drive Group" drive group\} if it has remaining capacity.
\p\p\1
IMPORTANT\0\p
There is a limit on how many LUNs you can create. This limit depends on the following factors: \p
\{\1 o \0\} The maximum LUNs allowed by the operating system (installed on the host machine connected to your RAID Modules via SCSI cable).
\p\p
\{\1 o \0\} The number of LUNs you have already created.
\p\p
\{\1 o \0\} The number of LUNs that the controllers in the RAID Module can own.
\p\p\1
Related Topics\0\p
\{\3\goto "Using Create LUN" Using Create LUN\} \p
\keyword "logical units, limitations"
\keyword "maximum, logical units"
\keyword "logical units, specifying number"
\keyword "changing number of logical units"
\keyword "logical unit parameters"

\topic "Specifying RAID Level"
\0\p\1
Specifying RAID Level\0
\p\p\1
When To Use\0\p
Use to indicate what \{\2\bring_popup "RAID Level" RAID Level\} you want for the drive group/logical units (LUN) you are going to create.
\p\p\1
What Happens\0\p
The Available Capacity \keyword "available capacity" field changes depending on the \keyword "RAID Level" RAID Level and number of drives you select and reflects the actual capacity that is available for use. Remember that all RAID Levels (except RAID 0) use part of the drives' capacity for redundancy.
\p\p\1
IMPORTANT\0\p
\{\1 o \0\} If a RAID Level is grayed out, it means that the current number of drives selected is not a valid number for the selected RAID Level. For example, RAID 1 must always use an even number of drives.
\p\p
\{\1 o \0\} A RAID Module can support multiple RAID Levels, but each LUN configured on the same drive group must use the same RAID Level.
\p\p
\{\1 o \0\} If you are creating additional LUNs on an existing drive group, you cannot change the RAID Level. Any LUNs on a specific drive group must use the same RAID Level and the same set of drives.
\p\p\1
Did You Know?\0\p
\{\1 o \0\} When you select the different RAID Levels, a brief description of the particular RAID Level displays. Use this description to determine which RAID Level to use.
\p\p
\{\1 o \0\} If you want to change the RAID Level of an existing drive group, see the "Changing Logical Unit Parameters" topic in the list below.
\p\p\1
Related Topics\0\p
\{\3\goto "Changing LUN Parameters" Changing Logical Unit Parameters\} \p
\{\3\goto "Using Create LUN" Using Create LUN\} \p
\keyword "logical unit parameters"
\keyword "changing RAID Level"
\keyword "logical units, specifying RAID Level"

\topic "Configuration -- Quick And Easy"
\0\p\1
Learning By Example -- Quick And Easy Configuration\0
\p\p
The following scenario provides an example of a user creating a \{\2\bring_popup "Logical Unit" logical unit\}/drive group as quickly and easily as possible.
\p\p\1
Objective\0\p
The user wants to create a new RAID 5 drive group containing 5 drives and 4 logical units (LUN) on a RAID Module named sonne2.
\p\p\1
Assumptions\0\p
\{\1 o \0\} User has already started the Configuration Application. The main Configuration screen is displayed.
\p\p
\{\1 o \0\} There are three RAID Modules; the first module on the SCSI Bus or in your defined list is currently displayed. (For example, sonne_001.)
\p\p
\{\1 o \0\} The RAID Module sonne2 has an \{\2\bring_popup "Unassigned Drive Group" unassigned drive group\} consisting of 10, one-gigabyte drives (that is, 10,000 MB of total capacity).
\p\p\1
8 Easy Steps For The User\0\p
1. Selects the RAID Module sonne2. \p
The current configuration for sonne2 displays.
\p\p
2. Highlights the unassigned drive group in the Drive Groups area. \p
The total capacity shows 10,000 MB.
\p\p
3. Selects Create LUN. \p
The main Create screen displays (RAID 5, 10 drives, and 1 LUN are the default selections).
\p\p
4. Selects 5 in the Number Of Drives field. \p
The Available Capacity field changes to 4000 MB based on 5 drives and RAID 5 (that is, 5 drives x 1000 MB - 1000 MB (for data redundancy) = 4000 MB).
\p\p
5. Selects 4 in the Number Of LUNs To Create field.
\p\p
6. Before selecting Create, the user selects Options to view the settings for the other LUN parameters (this is an optional step). After quickly looking at the defaults (such as individual LUN capacity, drive selection, caching parameters, etc.), the user keeps the defaults and selects Cancel.
\p\p
7. Selects Create. \p
A confirmation screen displays.
\p\p
8. Confirms that 4 LUNs of 1000 MB each will be created and selects OK. \p
The main Configuration screen displays again and shows that a new RAID 5 drive group (consisting of 5 drives and 4, 1000 MB LUNs) is being created/formatted.
\p\p\1
NOTE\0: Your operating system may have additional \{\2\bring_popup "OPSYS Requirements" requirements\} to complete the configuration process so that the operating system can recognize the new logical units. Consult the "Installation And Support Guide" for your operating system and the appropriate system documentation for specific details.
\p\p\1
Related Topics\0\p
\{\3\goto "Configuration -- Custom" Learning By Example -- Custom Configuration\} \p
\{\3\goto "Using Create LUN" Using Create LUN\} \p
\keyword "configuration, quick example"
\keyword "quick configuration"

\popup "OPSYS Requirements" 
\0\p
Operating System Requirements \p
Most require that you add new LUNs to your operating system (see your system documentation for details on adding a drive). Remember, each logical unit (not a drive group) is seen by the operating system as ONE drive.
\p\p
Windows NT requires that you reboot your system after making ANY configuration changes (see the "Installation And Support Guide" for your operating system for details). \p

\topic "Configuration -- Custom"
\0\p\1
Learning By Example -- Custom Configuration\0
\p\p
The following scenario provides an example of a user creating a new \{\2\bring_popup "Logical Unit" logical unit\}/drive group and changing some of the more advanced default logical unit (LUN) options.
\p\p\1
Objective\0\p
The user wants to create a new RAID 3 drive group containing 5 drives and 4 logical units (LUN) on a RAID Module named sonne2.
\p\p\1
Assumptions\0\p
\{\1 o \0\} User has already started the Configuration Application. The main Configuration screen is displayed.
\p\p
\{\1 o \0\} There are three RAID Modules; the first module on the SCSI Bus or in your defined list is currently displayed. (For example, sonne_001.)
\p\p
\{\1 o \0\} The RAID Module sonne2 has an \{\2\bring_popup "Unassigned Drive Group" unassigned drive group\} consisting of 10, one-gigabyte drives (that is, 10,000 MB of total capacity).
\p\p
\{\1 o \0\} User does not want the LUNs to have equal capacities.
\p\p
\{\1 o \0\} User wants the first two LUNs to have write caching and write mirroring enabled.
\p\p
\{\1 o \0\} User does not care which of the 10 drives are used for the new drive group.
\p\p\1
11 Easy Steps For The User\0\p
1. Selects the RAID Module sonne2. \p
The current configuration for sonne2 displays.
\p\p
2. Highlights the unassigned drive group in the Drive Groups area. \p
The total capacity shows 10,000 MB.
\p\p
3. Selects Create LUN. \p
The main Create screen displays (RAID 5, 10 drives, and 1 LUN are the default selections).
\p\p
4. Selects 3 in the RAID Level selection area. \p
The RAID Level description changes from RAID 5 to RAID 3. The Available Capacity field changes to 9000 MB based on 10 drives (the default) and RAID 3 (that is, 10 drives x 1000 MB - 1000 MB (for data redundancy) = 9000 MB).
\p\p
5. Selects 5 in the Number Of Drives field. \p
The Available Capacity field changes again to 4000 MB based on 5 drives and RAID 3 (that is, 5 drives x 1000 MB - 1000 MB (for data redundancy) = 4000 MB).
\p\p
6. Selects 4 in the Number Of LUNs To Create field.
\p\p
7. Selects Options. \p
The Options screen displays the default LUN capacity settings (the default is 1000 MB for each LUN).
\p\p
8. Changes the LUN capacities and then selects Caching Parameters. \p
The caching parameter options display for each LUN that will be created.
\p\p
9. Selects write caching and write mirroring for the first two LUNs. Then, selects OK because the other default options (such as drive selection) do not need to be changed. \p
The main Create screen displays again.
\p\p
10. Selects Create. \p
A confirmation screen displays.
\p\p
11. Confirms that 4 LUNs with the capacities specified will be created and selects OK. The main Configuration screen displays again and shows that a new RAID 3 drive group (consisting of 5 drives and 4 LUNs) is being created/formatted.
\p\p\1
NOTE\0: Your operating system may have additional \{\2\bring_popup "OPSYS Requirements" requirements\} to complete the configuration process so that the operating system can recognize the new logical units. Consult the "Installation And Support Guide" for your operating system and the appropriate system documentation for specific details.
\p\p\1
Related Topics\0\p
\{\3\goto "Configuration -- Quick And Easy" Learning By Example -- Quick And Easy Configuration\} \p
\{\3\goto "Using Create LUN" Using Create LUN\} \p
\keyword "configuration, custom example"
\keyword "custom configuration"
\keyword "changing logical unit parameters"

\topic "Changing LUN Parameters"
\0\p\1
Changing Logical Unit Parameters\0
\p\p\1
When To Use\0\p
After the LUNs are created, you can change the various parameters of the logical units (RAID Level, segment size, caching, etc.). However, most of the changes require you to delete the LUN using \keyword "Delete" Delete and then recreate it using \keyword "Create LUN" Create LUN. The following list indicates each LUN parameter, whether changing it destroys data, and what option you use to change it.
\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, and when re-creating them WAIT for the format to finish on the first LUN/drive group before creating others to make sure the operation completes successfully. Consult the troubleshooting section of the "User Guide" for more information.
\p\p\1
LUN Parameter List
\p\p\1
Parameter\0: \{\2\bring_popup "RAID Level" RAID Level\} or Number Of Drives \p\1
Destroys Data When Changed?\0: Yes, on all LUNs in the drive group\p\1
How To Change\0:\p
1. From the top menu, select File >> Save Module Profile to save all of the Module Profile information for the RAID Module you want to change. You can use this information as a reference when you are creating new LUNs.
\p\p
2. Back up the data on ALL the LUNs you want to delete.
\p\p
3. Use Delete to delete all of the LUNs in the drive group. This also deletes the drive group and the drives are returned to the unassigned drive group.
\p\p
4. Use Create LUN to recreate the LUNs from the unassigned drive group.
\p\p\1
Parameter\0: \{\2\bring_popup "Segment Size" Segment Size\} or Individual LUN Capacity\p\1
Destroys Data When Changed?\0: Yes, only on the LUN you are changing. \p\1
How To Change\0: \p
1. From the top menu, select File >> Save Module Profile to save all of the Module Profile information for the RAID Module you want to change. You can use this information as a reference when you are creating new LUNs.
\p\p
2. Back up the data on ALL the LUNs you want to delete.
\p\p
3. Use Delete to delete the individual LUN in the drive group. If there is more than one LUN on the drive group, then deleting an individual LUN gives remaining capacity for the existing drive group. However, if there is only one LUN on the drive group, the drive group is also deleted and the drives are returned to the unassigned drive group.
\p\p
4. Use Create LUN to recreate the LUN on the existing drive group or the unassigned drive group.
\p\p\1
Parameter\0: Caching Parameters or LUN Assignment\p\1
Destroys Data When Changed?\0: No\p\1
How To Change\0: Use Caching Parameters or LUN Balancing in the \keyword "Maintenance/Tuning Application" Maintenance/Tuning Application.
\p\p\1
Parameter\0: \{\2\bring_popup "Reconstruction Rate" Reconstruction Rate\}\p\1
Destroys Data When Changed?\0: No\p\1
How To Change\0: Use LUN Reconstruction Rate in the Maintenance/Tuning Application.
\p\p\1
Related Topics\0\p
\{\3\goto "Selecting The Options Button" Selecting The Options Button\} \p
\{\3\goto "Using Create LUN" Using Create LUN\} \p
\keyword "changing logical unit parameters"

\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

\topic "Using Create Hot Spare"
\0\p\1
Using Create Hot Spare\0
\p\p\1
When To Use\0\p
Use to create \{\2\bring_popup "Hot Spare" hot spares\} from unassigned drives. These drives contain no data and act as standbys in case any drive fails in a RAID 1, 3, or 5 logical unit on the \{\2\bring_popup "RAID Module" RAID Module\}.
\p\p\4
CAUTION\0\p
Hot spares cannot cover for drives with a larger capacity (that is, a 2 GB hot spare cannot stand in for a 4 GB failed drive). If the unassigned drive group contains drives with different capacities, the Configuration Application selects the first available drive when you select this option, which may NOT have the largest capacity. 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 to ensure that the hot spare can cover for any failed drive in the RAID Module.
\p\p\1
What Happens\0\p
If a drive fails, the hot spare drive \keyword "hot spare" automatically takes over for the failed drive until you replace it. Once you replace the failed drive, the hot spare automatically returns to a Standby status after reconstruction (copy-back) is complete. A hot spare is NOT dedicated to a specific drive group or logical unit; instead, it can be used for any failed drive in the RAID Module with the same or smaller capacity. If a drive fails, the hot spare automatically takes over for the failed drive until you replace it.
\p\p
You can determine the status of the hot spare by highlighting the hot spare drive group in the main Configuration screen and selecting \keyword "List/Locate Drives" List/Locate Drives. For an explanation of possible drive statuses and any recommended action to take, select the "Possible Drive Statuses" topic in the list below.
\p\p
After you create a hot spare, the Drive Groups area of the main Configuration screen displays the following: \p
\{\1 o \0\} A new hot spare drive group displays if there was not an existing hot spare drive group.
\p\p
\{\1 o \0\} The Drives column increases to add the new hot spare if there was an existing hot spare drive group.
\p\p\1
IMPORTANT\0\p
This option is grayed out if all of the drives in the \{\2\bring_popup "Unassigned Drive Group" unassigned drive group\} are failed, or if you do not highlight the unassigned drive group. You can only create new or additional hot spares from the unassigned drive group. \keyword "Create Hot Spare"
\p\p\1
Did You Know?\0\p
\{\1 o \0\} Once you replace the failed drive, the hot spare automatically returns to a Spare-Stdby status after reconstruction (copy-back) has completed on the replacement drive.
\p\p
\{\1 o \0\} The number of hot spare drives you can select is 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 SCSI Channels (probably either 2 or 5, depending on the model of your module). 
\p\p\1
Related Topics\0\p
\{\3\subtopic "Choosing Specific Hot Spare Drives" Choosing Specific Hot Spare Drives\} \p
\{\3\goto "How Many Hot Spares Can I Configure?" How Many Hot Spares Can I Configure?\} \p
\{\3\goto "Possible Drive Statuses" Possible Drive Statuses\} \p
\{\3\subtopic "Specifying Number Of Hot Spare Drives" Specifying Number Of Hot Spare Drives\} \p
\keyword "adding hot spares"
\keyword "creating hot spares"

\topic "Specifying Number Of Hot Spare Drives"
\0\p\1
Specifying Number Of Hot Spare Drives\0
\p\p
When you select \keyword "Create Hot Spare" Create Hot Spare, a screen displays that allows you to specify how many hot spares you want to create.
\p\p\1
IMPORTANT\0\p
If you select Create without making any changes in Options, then a hot spare is created using the default drive specified in Options.
\p\p\1
Selection Options\0\p
\{\1 o \0\} Specify how many hot spares you want to create. 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 module).
\p\p
\{\1 o \0\} Select Options to indicate the specific drives to be used as hot spares and/or to view the drives that have been automatically selected.
\p\p
\{\1 o \0\} Select Create once you are ready to create the hot spare.
\p\p\1
Related Topics\0\p
\{\3\goto "Choosing Specific Hot Spare Drives" Choosing Specific Hot Spare Drives\} \p
\{\3\goto "How Many Hot Spares Can I Configure?" How Many Hot Spares Can I Configure?\} \p
\{\3\goto "Using Create Hot Spare" Using Create Hot Spare\} \p
\keyword "maximum, hot spares"
\keyword "hot spare, specifying number"

\topic "Choosing Specific Hot Spare Drives"
\0\p\1
Choosing Specific Hot Spare Drives\0
\p\p
When you select \keyword "Create Hot Spare" Create Hot Spare >> Options, this screen displays two lists: \p
\{\1 o\0\} \1 Unselected Drives\0 -- indicates the unassigned drives that are not currently designated to be hot spares.
\p\p
\{\1 o\0\} \1 Selected Drives\0 -- indicates the drives that have been automatically designated to be hot spares. The total number is based on the number of drives you specified in the previous screen.
\p\p\1
IMPORTANT\0\p
\{\1 o \0\} The Move button is grayed out if the number you selected in the previous screen equals all of the remaining (unassigned) drives.
\p\p
\{\1 o \0\} Make sure that the number of drives listed in the Selected Drives list equals the number you specified in the previous screen. If it does not, you cannot continue with creating the hot spares.
\p\p\1
Selection Options\0\p \keyword "selecting items"
Choose one: \p \keyword "highlighting multiple items"
\{\1 o \0\} Single-click to highlight a single drive.
\p\p
\{\1 o \0\} Press Shift + click to highlight drives in a series.
\p\p
\{\1 o \0\} Press Control + click to highlight drives not in a series.
\p\p
1. Highlight drives from the Unselected Drives list and/or Selected Drives list.
\p\p
2. Select Move. Both lists are updated to show the new choices.
\p\p\1
Related Topics\0\p
\{\3\goto "Specifying Number Of Hot Spare Drives" Specifying Number Of Hot Spare Drives\} \p
\{\3\goto "Using Create Hot Spare" Using Create Hot Spare\} \p
\keyword "selecting hot spare drives"
\keyword "hot spare, specifying drives"

\topic "Using Delete"
\0\p\1
Using Delete\0
\p\p\4
CAUTION\0\p
\{\1 o \0\} Consult the "Installation And Support Guide" for your operating system BEFORE deleting any logical unit. Some operating systems have special limitations or requirements such as \{\2\bring_popup "Windows NT Delete" Windows NT\}.
\p\p
\{\1 o \0\} Deleting one or more logical units causes the loss of ALL data on the selected logical units. However, you may still Cancel after selecting \keyword "Delete" Delete without actually deleting any logical units or hot spares. \keyword "how to delete"
\p\p
\{\1 o \0\} Because deleting LUNs causes data loss, back up data on ALL the LUNs in any drive group you are deleting.
\p\p
\{\1 o \0\} If you do not have RDAC protection (such as, with the Networked version of this software), you must first stop I/Os to the affected RAID Module and you should ensure that no other users are on the system.
\p\p
\{\1 o \0\} If you are using the networked version of the storage management software or a dual-host-RAID Module configuration (such as \{\2\bring_popup "Multi-Host Configuration" multi-host\} or \{\2\bring_popup "Independent Controller Configuration" independent controller\}),  it is possible to open a Configuration Application and begin Delete from more than one host/station. However, you must be sure that are using only one configuration session at a time or the drive group/LUN you delete could be in use and cause problems for one of the hosts/stations.
\p\p\1
When To Use\0\p
Use to delete all of the \{\2\bring_popup "Logical Unit" logical units\} (LUN) in a \{\2\bring_popup "Configured Drive Group" drive group\}, individual LUNs within a drive group, or standby \{\2\bring_popup "Hot Spare" hot spare\} drives (if supported). \keyword "logical units, deleting"
\p\p
You delete ALL logical units or the only logical unit in a drive group if you want to: \p
\{\1 o \0\} Change the RAID Level or number of drives of that drive group. You delete the logical units and then use Create LUN to recreate them. \keyword "changing logical unit parameters"
\p\p
\{\1 o \0\} Free up capacity. \keyword "freeing capacity"
\p\p
You delete INDIVIDUAL logical units in a drive group if you want to: \p
\{\1 o \0\} Change the segment size or capacity of an individual LUN. You delete the individual logical unit and then use \keyword "Create LUN" Create LUN to recreate them.
\p\p
\{\1 o \0\} Free up capacity.
\p\p
You delete a Spare-Stdby hot spare drive if you want to return it to an unassigned status and make it available for LUN creation. \keyword "hot spare, deleting"
\p\p\1
IMPORTANT\0\p
If you have deleted all the LUNs on a RAID Module and are re-creating new LUNs, WAIT for the format to finish on the first LUN/drive group before creating additional new drive groups to make sure the operation completes successfully. Consult the troubleshooting section of the "User Guide" for more information.
\p\p\1
What Happens\0\p
After selecting Delete, a list of LUNs for the drive group you highlighted appears. You can select any or all of these LUNs to delete.
\p\p
After deleting LUNs or hot spares, the Drive Groups area of the main Configuration screen displays one of the following: \p
\{\1 o \0\} The drives return to the unassigned drive group if you \p
(1) deleted all of the LUNs in a drive group, \p
(2) deleted the only LUN in the drive group, or \p
(3) deleted a hot spare.
\p\p
\{\1 o \0\} There is additional remaining capacity on the drive group if you deleted some, but not all, of the LUNs in a drive group.
\p\p\1
IMPORTANT\0\p
\{\1 o \0\} If you select an \{\2\bring_popup "Unassigned Drive Group" unassigned drive group\}, this option is grayed out. You cannot delete an unassigned drive group.
\p\p
\{\1 o \0\} If you select a hot spare drive group and all of the hot spares are currently being used, this option is grayed out. You cannot delete a hot spare that is being used. Doing so would delete the data it contains which would cause a logical unit to go to a \{\2\bring_popup "Degraded Mode" Degraded\} or \{\2\bring_popup "Dead Mode" Dead\} status.
\p\p
\{\1 o \0\} If you select a RAID Module that has an \{\2\bring_popup "Independent Controller Configuration" independent controller configuration\}), each controller owns a specific drive group/LUN. This option is grayed out if you select a configured drive group that is NOT owned by the controller-host machine you are working from.
\p\p\1
Selection Options\0\p \keyword "selecting items"
Choose one: \p \keyword "highlighting multiple items"
\{\1 o \0\} Choose Select All to highlight all items in the list.
\p\p
\{\1 o \0\} Single-click to highlight a single item.
\p\p
\{\1 o \0\} Press Shift + click to highlight items in a series.
\p\p
\{\1 o \0\} Press Control + click to highlight items not in a series.
\p\p\1
Related Topics\0\p
\{\3\goto "Types Of Hardware Configurations" Types Of Host-RAID Module Configurations Supported\} \p
\{\3\goto "Using Create LUN" Using Create LUN\} \p

\topic "Troubleshooting For Configuration"
\0\p\1
Troubleshooting/Common Questions
\p\p
NOTE:\0 For more general problems/questions that could apply in any application, consult the "Troubleshooting/Common Questions" topic on the Home Page.
\p\p\1
General Questions\0\p
\{\3\subtopic "Considerations With Two Active Controllers" Any Special Considerations For A Module With Two Active Controllers?\}
\p\p
\{\3\subtopic "Open Only One Configuration Application" How Many Configuration Applications Can I Have Open At Once?\}
\p\p
\{\3\subtopic "How Many Hot Spares Can I Configure?" How Many Hot Spares Can I Configure?\}
\p\p
\{\3\subtopic "What Is A Hot Spare?" What Is A Hot Spare?\}
\p\p
\{\3\subtopic "When Should I Use Reset Configuration?" When Should I Use Reset Configuration?\}
\p\p
\{\3\subtopic "Drive Groups Could Be Renumbered" Why Could The Drive Groups Be Renumbered?\}
\p\p\1
Logical Unit Creation\0\p
\{\3\subtopic "Considerations For Different Drive Capacities" Any Special Considerations For A Module With Different Drive Capacities?\}
\p\p
\{\3\goto "Determining Controller's Memory Size" How Can I Tell What Size Memory The Controllers In A RAID Module Have?\}
\p\p
\{\3\subtopic "Time To Create/Format A LUN" How Long Will It Take To Create/Format A Logical Unit?\}
\p\p
\{\3\subtopic "What Can Be Done During LUN Create/Format?" What Else Can I Do While A Logical Unit Is Being Created/Formatted?\}
\p\p
\{\3\subtopic "If A LUN Format Fails Before Creating A LUN" What If A Format Process Fails Before A LUN Is Created?\}
\p\p
\{\3\subtopic "What Is Cache Memory?" What Is Cache Memory?\}
\p\p
\{\3\subtopic "What Is The Difference Between Capacities?" What Is The Difference Between Capacities: Total, Remaining, And Available?\}
\p\p
\{\3\subtopic "After Creating A LUN" What Should I Do After Creating A Logical Unit?\}
\p\p
\{\3\subtopic "Can't Choose/Change The RAID Level" Why Can't I Choose/Change A Particular RAID Level?\}
\p\p
\{\3\subtopic "Why Change The Logical Unit Configuration?" Why Would I Want To Change The Logical Unit Configuration?\}
\p\p\1
Related Topics\0\p
\{\3\goto "Configuration Application" Configuration Application\} \p
\{\3\goto "Troubleshooting For All Applications" Troubleshooting/Common Questions For All Applications\} \p

\topic "Considerations With Two Active Controllers"
\0\p\1
Any Special Considerations For A Module With Two Active Controllers?\0
\p\p
Only if you want to manually assign/balance the \{\2\bring_popup "Logical Unit" logical units\} (LUN). The software automatically \keyword "logical units, assigning" assigns all logical units (LUN) on a new \{\2\bring_popup "Configured Drive Group" drive group\} to one of the active controllers during LUN creation. The LUNs are balanced across active controller pairs on a drive-group basis not an individual-LUN basis. The odd-numbered drive groups are assigned to one active controller and the even-numbered drive groups are assigned to the other active controller.
\p\p
There are two applications where you can manually assign/balance the LUNs: \p
\{\1 o \0\} During LUN creation, you can use \keyword "Create LUN" Create LUN >> Options >> LUN Assignment if you want to indicate which controller to assign the new drive group and corresponding LUNs.
\p\p
\{\1 o \0\} After LUN creation, you can balance the LUNs by using LUN Balancing in the \keyword "Maintenance/Tuning Application" Maintenance/Tuning Application.
\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 is grayed out.
\keyword "assigning logical units"
\keyword "balancing logical units"
\keyword "active controllers"
\keyword "Options screen"

\topic "Open Only One Configuration Application"
\0\p\1
How Many Configuration Applications Can I Have Open At Once?\0
\p\p
Only one at a time from a single host machine. This prevents any possible configuration conflicts. Although you can only open one Configuration Application 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 you have more than one station configured on your network, it is possible to open more than one Configuration session at a time. Also, if the RAID Module is using a dual-host configuration (such as \{\2\bring_popup "Multi-Host Configuration" multi-host\} or \{\2\bring_popup "Independent Controller Configuration" independent controller\}), either host machine can open one Configuration session and cannot detect what the other host is doing. Therefore, in these cases, be sure that you only have one session open when configuring or deleting LUNs or the operation will fail for one host. \p
\keyword "opening Configuration"

\topic "How Many Hot Spares Can I Configure?" 
\0\p\1
How Many Hot Spares Can I Configure?\0
\p\p
Each RAID Module can support as many \{\2\bring_popup "Hot Spare" hot spare\} drives as there are 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 cover for drives with a larger capacity (that is, a 2 GB hot spare drive cannot stand in for a 4 GB failed drive). 
\p\p
\{\1 o \0\} We do not recommend placing all your hot spares on the same drive channel. If the drive channel were to fail, these drives would be unable to cover for other failed drives in the RAID Module.
\p\p\1
Related Topics\0\p
\{\3\goto "Considerations For Different Drive Capacities" Any Special Considerations For Different Drive Capacities?\} \p
\{\3\goto "What Is A Hot Spare?" What Is A Hot Spare?\} \p
\keyword "hot spare"
\keyword "number of hot spares"

\topic "What Is A Hot Spare?"
\0\p\1
What Is A Hot Spare?\0
\p\p
A hot spare is a drive containing no data that acts as a standby in case a drive fails in a RAID 1, 3, or 5 logical unit.
\p\p
The hot spare drive adds another level of redundancy to your RAID Module. If a drive (of the same or smaller capacity) fails, the hot spare automatically takes over for the failed drive until you replace it. Once you replace the failed drive, the hot spare automatically returns to a Spare-Stdby status after \{\2\bring_popup "Reconstruction" reconstruction\} (copy-back) completes on the new replacement drive.
\p\p
A hot spare is NOT dedicated to a specific drive group or logical unit but instead can be used for any failed drive in the RAID Module with the same or smaller capacity. 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 module).
\p\p
You can determine the status of the hot spares by highlighting the hot spare drive group in the main Configuration screen and selecting \keyword "List/Locate Drives" List/Locate Drives or by selecting Module Profile >> Drives. For an explanation of the hot spare drive statuses, select the "Possible Drive Statuses" topic listed below.
\p\p\1
Related Topics\0\p
\{\3\goto "Do Hot Spares Affect LUN Statuses?" How Do Hot Spares Affect Logical Unit Statuses?\} \p
\{\3\goto "Possible Drive Statuses" Possible Drive Statuses\} \p
\keyword "hot spare limits"
\keyword "limitations, number of hot spares"

\topic "When Should I Use Reset Configuration?"
\0\p\1
When Should I Use Reset Configuration?\0
\p\p
Hopefully never! Only use this option as a last resort if your configuration is totally inaccessible or you want to start completely over.
\p\p
This option allows you to reset the \{\2\bring_popup "Drive Group" drive groups\} and \{\2\bring_popup "Logical Unit" logical units\} on the RAID Module back to a default configuration based on settings specified in the controller.
\p\p\4
CAUTION\0\p
You will lose ALL data on the selected RAID Module. If you do not have RDAC protection, you must first stop I/Os to the affected RAID Module and you should ensure no other users are on the system.
\p\p\1
NOTE\0: This option is grayed out if the selected RAID Module has an \{\2\bring_popup "Independent Controller Configuration" independent controller configuration\}.
\p
\keyword "reset configuration"
\keyword "file menu"

\topic "Drive Groups Could Be Renumbered"
\0\p\1
Why Could The Drive Groups Be Renumbered?\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 would always be 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" logical units\} each. \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 contains only LUN 0 now).
\p\p
Next, you create a new drive group. The new drive group uses the first available LUN; in this case, LUN 1. Therefore, the drive groups are renumbered as follows: \p
\{\1 o \0\} Drive group 1 contains LUN 0.
\p\p
\{\1 o \0\} Drive group 2 contains LUN 1.
\p\p
\{\1 o \0\} Drive group 3 contains LUNs 2 and 3. \p
\keyword "numbering drive groups"
\keyword "drive group, renumbering"

\topic "Considerations For Different Drive Capacities"
\0\p\1
Any Special Considerations For A Module With Different Drive Capacities?\0
\p\p
You should be aware if a RAID Module has drives with different capacities when you are creating \{\2\bring_popup "Logical Unit" logical units\} or \{\2\bring_popup "Hot Spare" hot spares\}.
\p\p\1
Creating Logical Units\0\p
If your \{\2\bring_popup "Unassigned Drive Group" unassigned drive group\} contains drives with different capacities (such as 2 GB and 4 GB), then Configuration detects and displays the unassigned drive group's capacity based on the capacity of the smaller drives (displayed as the total capacity in the main Configuration screen, and as available capacity in the main Create LUN screen). For example, if the unassigned drive group consisted of 5 drives (three 2 GB drives and two 4 GB drives), then the total/available capacity shown would be 10 GB (5 x 2 GB). Furthermore, if you create LUNs using mixed capacity drives, you CANNOT access the additional capacity on the larger drives.
\p\p
To avoid wasting the additional capacity of the larger capacity drives when creating logical units, select drives of the same capacity:
\p\p
1. Highlight the unassigned drive group.
\p\p
2. Select Create LUN and set the desired RAID Level, number of drives, and number of LUNs.
\p\p
3. Select Options >> Drive Selection and choose specific drives that share the same capacity (large or small).
\p\p
For example, if you are creating a three-drive, RAID 0, 12 GB LUN and the unassigned drive group contains 5 drives (two are 2 GB and three are 4 GB), you will want to select the larger capacity drives. Once you select the number of drives in the main Create LUN screen, the available capacity will initially be 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 will be reported.
\p\p\1
Creating Hot Spares\0\p
Hot Spares cannot cover for drives with a larger capacity (that is, a 2 GB hot spare drive cannot stand in for a 4 GB failed drive). If your unassigned drive group contains drives with different capacities, then the Configuration Application selects the first available drive, which may NOT have the largest capacity. To ensure that you select a drive with the largest capacity, use the following procedure.
\p\p\1
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 drive in the RAID Module.
\p\p
1. Before creating hot spares, use List/Locate Drives to determine the size of the drives on the RAID Module, and to record the capacities and location of the larger-capacity drives in the unassigned drive group.
\p\p\1
NOTE\0: Remember [x,y] indicates the unique location of the drive in the selected RAID Module. This identifier corresponds to the drive's SCSI Channel number and 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
2. In the main Configuration screen, highlight the Unassigned drive group.
\p\p
3. Select Create Hot Spare.
\p\p
4. Select the number of hot spares you want to create, and select Options.
\p\p
5. Does a larger-capacity drive appear in the Selected Drives list? \p
\{\1 o \0\} Yes. Select Create. \p
\{\1 o \0\} No. Highlight a larger-capacity drive in the Unselected Drives list. Select Move. Select Create.
\p\p\1
Related Topics\0\p
\{\3\goto "What Is The Difference Between Capacities?" What Is The Difference Between Capacities: Total, Remaining, And Available?\} \p
\keyword "drives, different capacity"
\keyword "creating logical units"
\keyword "hot spare, specifying drives"

\topic "Time To Create/Format A LUN"
\0\p\1
How Long Will It Take To Create/Format A Logical Unit?\0
\p\p
The time it takes to create \{\2\bring_popup "Logical Unit" logical unit\} (LUN) depends on the capacity of the LUN you specified (the larger the capacity, the more time it takes). The software creates the LUN in the background so that you can perform other Configuration tasks or use another application (such as Status, etc.). The main Configuration screen displays "Formatting" until the operation is complete. \p
\keyword "format failure"
\keyword "logical units, failing to format/create"
\keyword "time, Create LUN"

\topic "What Can Be Done During LUN Create/Format?"
\0\p\1
What Else Can I Do While A Logical Unit Is Being Created/Formatted?\0
\p\p
You can perform other Configuration tasks (such as creating \{\2\bring_popup "Logical Unit" logical units\} on another drive group) or select another application while the logical unit (LUN) is being created because the creation/format occurs in the background. However, you cannot select the drive group/LUNs that is being created until the format has completed.
\p\p\1
IMPORTANT\0\p
If you have deleted all the LUNs on a RAID Module and are re-creating new LUNs, WAIT for the format to finish on the first LUN/drive group before creating additional new drive groups to make sure the operation completes successfully. Consult the "User Guide" for more information. \p
\keyword "format failure"
\keyword "logical units, failing to format/create"

\topic "If A LUN Format Fails Before Creating A LUN"
\0\p\1
What If A Format Process Fails Before A LUN Is Created?\0
\p\p
Once you select "Create" during the LUN Creation process, the main Configuration screen displays "Formatting" until the operation is complete. However, if this format operation fails, Configuration displays a message that the logical unit failed to create and a message is written to Message Log in the Status Application. Most likely, the LUN failed to create because a drive or some module component has failed. If you see this message, you should use the \keyword "Status Application" Status Application to select Health Check and follow the recommended Action To Take in the detailed information screen. \p
\keyword "format failure"
\keyword "logical units, failing to format/create"

\topic "What Is Cache Memory?"
\0\p\1
What Is Cache Memory?\0
\p\p
Cache memory is an area on the \{\2\bring_popup "Controller" controller\} used for intermediate storage of read and write data. By using cache, you can increase system performance because the data for a read or write operation from the host may already be in the cache from a previous operation (thus the need to access the drive itself is eliminated), or the write operation is completed once it is written to the cache. Module Profile >> Controller shows the available cache size per controller in the RAID Module.
\p\p
When you create a logical unit, you can specify various caching parameters for the LUNs (Create LUN >> Options >> Caching). If you need to change any caching parameters after LUN creation, use the Maintenance/Tuning Application (Caching Parameters).
\p\p\1
NOTE\0: You can also use the command line utility, raidutil, for setting these and other more advanced caching parameters. \p
\keyword "cache memory"
\keyword "Maintenance/Tuning Application"

\topic "What Is The Difference Between Capacities?"
\0\p\1
What Is The Difference Between Capacities: Total, Remaining, And Available?\0
\p\p\1
Total Capacity\0\p
Shown in the main Configuration screen. This value indicates how much capacity (in megabytes) is available on the drive group. The capacity reflects any redundancy or \{\2\bring_popup "RAID 1" RAID 1\} mirroring factors. For example, a drive group comprised of RAID 1 \{\2\bring_popup "Logical Unit" logical units\} has half of the capacity of one with \{\2\bring_popup "RAID 0" RAID 0\} logical units. The total capacity for an \{\2\bring_popup "Unassigned Drive Group" unassigned drive group\} does not reflect any redundancy or mirroring factors.
\p\p\1
Remaining Capacity\0\p
Shown in the main Configuration screen. This value indicates how much capacity (in megabytes) is still available for configuring LUNs on the drive group. The capacity reflects any redundancy or RAID 1 mirroring factors (except for an unassigned drive group).
\p\p\1
Available Capacity\0\p
Shown in the main Create screen after you select Create LUN. This value indicates the actual capacity that is available for use and changes depending on the \{\2\bring_popup "RAID Level" RAID Level\} and number of drives you select. Remember that all RAID Levels (except RAID 0) use part of the drive group's capacity for redundancy. 
\p\p\1
IMPORTANT\0\p
If your unassigned drive group contains drives with different capacities (such as 2 GB or 4 GB), be sure to use Options >> Drive Selection to indicate that you want to use EITHER the smaller capacity drives ONLY or the larger capacity drives ONLY. With mixed capacity drives in the unassigned drive group, the Configuration Application initially bases the available capacity of this drive group (displayed in the main Create LUN screen) on the capacity of the smaller drives. For example if the unassigned drive group consisted of 5 drives (three 2 GB drives and two 4 GB drives), then the available capacity shown would be 10 GB (5 x 2 GB). Furthermore, if you create LUNs using mixed capacity drives, you are using only the smallest capacity available (2 GB) and you CANNOT access the additional capacity on the larger drives.
\p\p\1
Related Topics\0\p
\{\3\goto "Considerations For Different Drive Capacities" Any Special Considerations For A Module With Different Drive Capacities?\} \p
\keyword "capacity, defined"
\keyword "total capacity"
\keyword "remaining capacity"
\keyword "available capacity"
\keyword "RAID Level"

\topic "After Creating A LUN"
\0\p\1
What Should I Do After Creating A Logical Unit?\0
\p\p
Once you create \{\2\bring_popup "Logical Unit" logical units\} (LUN) using the Configuration Application, you have to make them part of the operating system. These procedures differ depending on the operating system you are using (see your system documentation for details on adding a drive). Remember, each logical unit (not a drive group) is seen by the operating system as ONE drive.
\p\p
Additionally, some operating systems (such as Windows NT) require that you reboot your system after making ANY configuration changes so that the operating system can recognize the new configuration (see the "Installation And Support Guide" for your operating system for details). \p
\keyword "after creating logical units"
\keyword "logical units, after creation"
\keyword "reboot"

\topic "Can't Choose/Change The RAID Level"
\0\p\1
Why Can't I Choose/Change A Particular RAID Level?\0
\p\p
If a \keyword "RAID Level" RAID Level is grayed out, it means 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

\topic "Why Change The Logical Unit Configuration?"
\0\p\1
Why Would I Want To Change The Logical Unit Configuration?\0
\p\p
Normally, when you receive the RAID Module, there are default logical units (LUN) and 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\} and/or the logical units may not be set up according to your needs (for example, number of LUNs, RAID Level, etc.). \p
\keyword "default configuration"

\topic "Status Application"
\0\p\1
Status Application\0
\p\p
\{\3\subtopic "Status Task Summary" Task Summary\}
\p\p
\{\3\subtopic "Using Message Log" Message Log\}
\p\p
\{\3\subtopic "Using Health Check" Health Check\}
\p\p
\{\3\subtopic "Using LUN Reconstruction" LUN Reconstruction\}
\p\p
\{\3\subtopic "ASC/ASCQ Error Codes" ASC/ASCQ Error Codes\}
\p\p
\{\3\subtopic "Troubleshooting For Status" Troubleshooting/Common Questions\}
\p\p\1
Related Topics\0\p
\{\3\goto "Tasks For All Applications" Task Summary\} \p
\{\3\goto "Troubleshooting For All Applications" Troubleshooting/Common Questions For All Applications\} \p

\topic "Status Task Summary"
\0\p\1
STATUS TASK SUMMARY\0
\p\p
\{\2\bring_popup "Open Log Tasks" Opening A Message Log\}
\p\p
\{\2\bring_popup "Save Log As Tasks" Saving A Message Log To Another File\}
\p\p
\{\2\bring_popup "Copy To Clipboard Tasks" Copying Detailed Messages\}
\p\p
\{\2\bring_popup "Select All Tasks" Selecting All Messages\}
\p\p
\{\2\bring_popup "Log Settings Tasks" Changing Message Log's Default Settings\}
\p\p
\{\2\bring_popup "Refresh All Tasks" Updating Message Log\}
\p\p
\{\2\bring_popup "Message Log Tasks" Viewing A Message Log\}
\p\p
\{\2\bring_popup "List Type Tasks" Selecting Types of Messages To Display\}
\p\p
\{\2\bring_popup "Health Check Tasks" Performing A Health Check\}
\p\p
\{\2\bring_popup "LUN Reconstruction Tasks" Viewing LUN Reconstruction Status\}
\p\p
\{\2\bring_popup "Reconstruction Rate Tasks" Changing The Reconstruction Rate\}
\p\p\1
Related Topics\0\p
\{\3\goto "Status Application" Status Application\} \p
\{\3\goto "Tasks For All Applications" Task Summary For All Applications\}

\popup "Open Log Tasks"
\0\p
Select Message Log, then from the top menu select File >> Open Log to view information for a selected log file. \p
\keyword "open log"

\popup "Save Log As Tasks"
\0\p
Select Message Log, then from the top menu select File >> Save Log As to save information in a selected log file to another log file. \p
\keyword "save log"

\popup "Copy To Clipboard Tasks"
\0\p
Using either Message Log or Health Check, and from the top menu, select Edit >> Copy To Clipboard to save the contents of a detailed message to a clipboard. \p
\keyword "copying contents"

\popup "Select All Tasks"
\0\p
Using either Message Log or Health Check, and from the top menu, select Edit >> Select All to highlight all the messages in the summary information screen. This option also highlights the text of a detailed message. \p
\keyword "selecting messages"

\popup "Refresh All Tasks"
\0\p
Using Message Log, from the top menu, select Options >> Refresh All to update Message Log to show any new messages for all message types in a selected log file. \p
\keyword "refresh log"
\keyword "update message log"

\popup "Log Settings Tasks"
\0\p
From the top menu, select Options >> Log Settings to change Message Log's default settings for log file, log size before notification, or check RAID Module every x minutes. \p
\keyword "log settings"
\keyword "log file, default"

\popup "Message Log Tasks"
\0\p
Select Message Log to display historical information for a single or all RAID Modules, including component failures, general status changes, and parity reports. \p
\keyword "Message Log"
\keyword "viewing messages"

\popup "List Type Tasks"
\0\p
Using Message Log, select List Type to change the \keyword "message types" message types displayed. Message types are parity, general, and hardware.
\p
\keyword "List Type"
\keyword "changing message type"

\popup "Health Check Tasks"
\0\p
Select Health Check to immediately check a single or all RAID Modules for failures on the I/O data path, controllers, drives, logical units, and other components. \p
\keyword "Health Check"
\keyword "checking modules"

\popup "LUN Reconstruction Tasks"
\0\p
Select a RAID Module, then LUN Reconstruction to display reconstruction progress for logical units undergoing reconstruction on that module. \p
\keyword "viewing reconstruction progress"
\keyword "reconstruction progress"

\popup "Reconstruction Rate Tasks"
\0\p
Select a RAID Module, then LUN Reconstruction to change the reconstruction rate for logical units undergoing reconstruction. \p
\keyword "changing reconstruction rate"
\keyword "reconstruction rate"

\topic "Using Message Log"
\0\p\1
Using Message Log\0
\p\p\1
When To Use\0\p
Use 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 has run a \keyword "parity check/repair" parity check/repair, or whenever you are aware of a general status change.
\p\p
This message can help you identify when (date/time) the event was detected, what RAID Module and \{\2\bring_popup "Controller" controller\} are affected, and what type of event has occurred, plus any relevant code data.
\p\p
See Related Topics at the bottom of this screen for additional information on this option.
\p\p\1
What Happens\0\p
Formats the actual log file data to display historical information containing different events for the selected \{\2\bring_popup "RAID Module" RAID Module\}. These events include component \keyword "failures" 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
\{\1 o \0\} The background monitor checks the RAID Modules.
\p\p
\{\1 o \0\} \{\2\bring_popup "Parity Check/Repair" 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
Options\0\p
While you are in \keyword "Message Log" Message Log, you can show more details for the messages you select and can change what types of \{\2\bring_popup "Message Types" messages\} are displayed.
\p\p
You can also use the top menu bar to: \p
\{\1 o \0\} Select File and either open another \keyword "log file, opening" log file or save the current log file to another filename.
\p\p
\{\1 o \0\} Select Options and either Refresh All to update the display or Log Settings to change Message Log parameters (default \{\2\bring_popup "Log File" log file\}, \{\2\bring_popup "Log Size Before Notification" log size before notification\}, and \{\2\bring_popup "Checking Interval" check RAID Module every x minutes\}).
\p\p\1
Related Topics\0\p
\{\3\subtopic "Change Log Settings" Change Log Settings\} \p
\{\3\subtopic "Copy To Clipboard" Copy To Clipboard\} \p
\{\3\subtopic "Listing Different Types Of Messages" Listing Different Types Of Messages\} \p
\{\3\subtopic "Open An Existing Log File" Open An Existing Log File\} \p
\{\3\subtopic "Refresh Message Log" Refresh Message Log\} \p
\{\3\subtopic "Save The Log As Another File" Save The Log As Another File\} \p
\{\3\subtopic "Selecting Messages Or Exceptions" Selecting Messages Or Exceptions\} \p
\{\3\goto "Unexpected Information In Message Log" What If I Do Not See The Information I Expected In Message Log?\} \p
\{\3\goto "Message Log Can't Find The Default Log File" What If Message Log Cannot Find The Default Log File?\} \p
\{\3\goto "The ''No Match Found'' Message Displays" What If The ''No Match Found'' Message Displays?\} \p
\{\3\subtopic "Information In Message Log" What Information Appears In Message Log?\} \p
\{\3\subtopic "Information In Show Details" What Information Appears In Show Details?\} \p
\keyword "component errors" 
\keyword "monitor, background"
\keyword "error messages"
\keyword "configuration changes"
\keyword "viewing messages"

\topic "Information In Message Log"
\0\p\1
What Information Appears In Message Log?\0
\p\p
Whenever you select Message Log, you see an historical summary of the \keyword "RAID Module" RAID Module problems, parity reports, and general status changes that have been detected.
\p\p
See Related Topics at the bottom of this screen for additional information on this option.
\p\p\1
Date & Time\0\p
When the detected event was logged into Message Log. \p
\{\1 o \0\} If the event is a component failure detected by the background monitor, it indicates that the error 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 parity event, it indicates that detection and repair occurred the last time that parity was run either manually or through Automatic Parity Check/Repair.
\p\p
\{\1 o \0\} If the message indicates a general status change, you have a history of changes made.
\p\p\1
RAID Module\0\p
The specific module where the event occurred.
\p\p\1
Type\0\p
What type of RAID Module event occurred: \{\2\bring_popup "Parity Message Type" Parity\}, \{\2\bring_popup "General Message Type" General\}, or \{\2\bring_popup "Hardware Message Type" Hardware\}.
\p\p\1
Code\0\p
The \{\2\bring_popup "ASC/ASCQ Code" ASC/ASCQ\} code for hardware messages when applicable. The code indicates that a specific problem has occurred. Select Show Details for the recommended Action to Take. \keyword "ASC/ASCQ"
\p\p\1
Controller\0\p
The affected controller identified by A or B and its system \{\2\bring_popup "Device Name" device name\}.
\p\p\1
Items At The Bottom Of The Summary Information Screen\0\p
\{\1 o \0\}\1 Current Log\0 -- Indicates what log is open for viewing. Normally, this is the default log file, unless you open another log file.
\p\p
\{\1 o \0\}\1 Total Messages\0 -- Indicates the number of messages displayed in the current log file.
\p\p
\{\1 o \0\}\1 Total Selected\0 -- Indicates the total number of messages that you have selected or highlighted in the summary information screen.
\p\p\1
Related Topics\0\p
\{\3\goto "ASC/ASCQ Error Codes" ASC/ASCQ Error Codes\} \p
\{\3\goto "Listing Different Types Of Messages" Listing Different Types Of Messages\} \p
\{\3\goto "Selecting Messages Or Exceptions" Selecting Messages Or Exceptions\} \p
\{\3\goto "Using Message Log" Using Message Log\} \p
\{\3\goto "What Does The Device Name Mean?" What Does The Device Name Mean?\} \p
\{\3\goto "Unexpected Information In Message Log" What If I Do Not See The Information I Expected In Message Log?\} \p
\{\3\goto "Message Log Can't Find The Default Log File" What If Message Log Cannot Find The Default Log File?\} \p
\{\3\goto "The ''No Match Found'' Message Displays" What If The ''No Match Found'' Message Displays?\} \p
\{\3\goto "Information In Show Details" What Information Appears In Show Details?\} \p
\keyword "device name"
\keyword "defaults"
\keyword "message types"
\keyword "check RAID Modules every x minutes"
\keyword "failures"
\keyword "error detection"

\topic "Information In Show Details"
\0\p\1
What Information Appears In Show Details?\0
\p\p
See Related Topics at the bottom of this screen for additional information on this option.
\p\p\1
Select Messages In The Summary Information Screen\0\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\}, or \{\2\bring_popup "Hardware Message Type" Hardware\}.
\p\p\1
Date\0: The month, day, and year the event details were written to \keyword "Message Log" Message Log.
\p\p\1
RAID Module\0: The specific 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 "Device Name" device name\} of the controller assigned to the specified RAID Module.
\p\p\1
Options\0\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 highlighted 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 Types\0\p
Depending on the type of message you select in the summary information screen, you could see one of three detailed message formats when you select Show Details:
\p\p
\{\3\subtopic "Parity Message Details" Parity Message Details\}
\p\p
\{\3\subtopic "General Message Details" General Message Details\}
\p\p
\{\3\subtopic "Hardware Message Details" Hardware Message Details\}
\p\p\1
Related Topics\0\p
\{\3\goto "ASC/ASCQ Error Codes" ASC/ASCQ Error Codes\} \p
\{\3\goto "Using Message Log" Using Message Log\} \p
\{\3\goto "What Does The Device Name Mean?" What Does The Device Name Mean?\} \p
\keyword "show details"
\keyword "message index"
\keyword "details, error messages"
\keyword "message details"
\keyword "copy to clipboard"
\keyword "selecting messages"
\keyword "message types"
\keyword "device name"
\keyword "date/time"

\topic "Parity Message Details"
\0\p\1
Parity Message Details\0
\p\p
If the message type you are viewing in Show Details is \{\2\bring_popup "Parity Message Type" parity\}, you receive the following details:
\p\p\1
Affected Logical Unit\0: The specific \{\2\bring_popup "Logical Unit" logical unit\} where the \keyword "parity messages" parity problem occurred.
\p\p\1
Block Begin\0: The code for the initial data block on the affected logical unit.
\p\p\1
Block End\0: The code for the final data block on the affected logical unit. The Block Begin and End numbers provide a range that identifies the logical address where the parity inconsistencies were found and repaired.
\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.
\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\0\p
\{\3\goto "Copy To Clipboard" Copy To Clipboard\} \p
\{\3\goto "Selecting Messages Or Exceptions" Selecting Messages Or Exceptions\} \p
\{\3\goto "Information In Show Details" What Information Appears In Show Details?\} \p
\{\3\goto "What Is Parity?" What Is Parity?\} \p
\keyword "blocks"
\keyword "logical block address"
\keyword "message types"

\topic "General Message Details"
\0\p\1
General Message Details\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 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 Or Exceptions" Selecting Messages Or Exceptions\} \p
\{\3\goto "Information In Show Details" What Information Appears In Show Details?\} \p
\keyword "message types"

\topic "Hardware Message Details"
\0\p\1
Hardware Message Details\0
\p\p
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
ASC/ASCQ\0: ASC is a SCSI Additional Sense Code and an ASCQ is an ASC Qualifier. \keyword "ASC/ASCQ" ASC/ASCQ codes are sent by the controller to provide further information about the 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 Logical Unit\0: The specific \{\2\bring_popup "Logical Unit" logical unit\} 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\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 Or Exceptions" Selecting Messages Or Exceptions\} \p
\{\3\goto "Information In Show Details" What Information Appears In Show Details?\} \p
\keyword "message types"

\topic "Listing Different Types Of Messages"
\0\p\1
Listing Different Types Of Messages\0
\p\p\1
Options\0\p
In the summary information screen of \keyword "Message Log" Message Log, you can view information for a specific RAID Module or select any 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\}. Additionally, when you select the Hardware message type, you can also specify a particular range of \{\2\bring_popup "ASC/ASCQ Code" ASC/ASCQ\} codes.
\p\p\1
Steps To List Different Types Of Messages\0\p
To change the types of messages displayed,
\p\p
1. Select \keyword "List Type" List Type, and click each box for the types you want to view.
\p\p\1
OR\0
\p\p
2. Change your RAID Module selection.
\p\p\1
Did You Know?\0\p
\{\1 o \0\} When you exit Message Log and return, all of the message types appear again in the summary information screen (this is the default setting).
\p\p
\{\1 o \0\} You must select either All or Hardware before you can select the ASC/ASCQ box.
\p\p\1
Related Topics\0\p
\{\3\goto "Using Message Log" Using Message Log\} \p
\{\3\goto "What Is Parity?" What Is Parity?\} \p
\keyword "hardware errors"
\keyword "ASC/ASCQ"
\keyword "general errors"
\keyword "parity errors"
\keyword "message types"
\keyword "defaults"	
		 
\topic "Open An Existing Log File"
\0\p\1
Open An Existing Log File\0
\p\p\1
Steps To Open A Log File\0\p
1. From the top menu, select File >> Open Log.
\p\p
\{\1 o \0\} Enter the name of the log you want to open, OR
\p\p
\{\1 o \0\} 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
2. Select OK. The selected log file displays in Message Log until you open another log or exit the Status Application.
\p\p\1
IMPORTANT\0\p
\{\1 o \0\} If you are not in Message Log, this option is grayed out.
\p\p
\{\1 o \0\} If you see the "Log file is corrupted" message, it could mean 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
Related Topics\0\p
\{\3\goto "Change Log Settings" Change Log Settings\} \p
\{\3\goto "Save The Log As Another File" Save The Log As Another File\} \p
\{\3\goto "Using Message Log" Using Message Log\} \p
\{\3\goto "The ''Selection Is Not A File'' Message Displays" What If The ''Selection Is Not A File'' Message Displays?\} \p
\keyword "file menu"
\keyword "log file, viewing"
\keyword "file, open"
\keyword "open log"
\keyword "filter"

\topic "Save The Log As Another File"
\0\p\1
Save The Log As Another File\0
\p\p\1
When To Use\0\p
You may want to save the log to another file when:
\p\p
\{\1 o \0\} The log file is getting too large.
\p\p
\{\1 o \0\} The log has exceeded the log size before notification \{\2\bring_popup "Threshold Values" value\}.
\p\p
\{\1 o \0\} You want to capture a specific time frame for analysis.
\p\p\1
IMPORTANT\0\p
\{\1 o \0\} If you are not in Message Log, this option is grayed out.
\p\p
\{\1 o \0\} If you save the log to a different filename because the log is getting too large, then you need to delete the contents of the log as soon as possible after saving it to another log file. You can use a standard editor to delete the contents. For example, if rmlog.log is the current default log, it continues to have messages written to it. Thus, if you do not delete the contents, it continues to be too large.
\p\p\1
Steps To Save A Log As Another File\0\p
1. From the top menu, select File >> Save Log As, and
\p\p
\{\1 o \0\} Enter the new name you want to save the log as, OR
\p\p
\{\1 o \0\} 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
2. Select OK. The log contents are saved to the selected filename. 
\p\p
3. Select OK at the "save was successful" confirmation screen. This has no effect on the log 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\0\p
\{\3\goto "Change Log Settings" Change Log Settings\} \p
\{\3\goto "Open An Existing Log File" Open An Existing Log File\} \p
\{\3\goto "Using Message Log" Using Message Log\} \p
\{\3\goto "The ''Selection Is Not A File'' Message Displays" What If The ''Selection Is Not A File'' Message Displays?\} \p
\keyword "file menu"
\keyword "save log"
\keyword "log file, saving"
\keyword "file, save"
\keyword "threshold level reached"
\keyword "messages, threshold level reached"
\keyword "log size"
\keyword "filter"

\topic "Refresh Message Log"
\0\p\1
Refresh Message Log\0
\p\p
From the top menu, select Options >> Refresh All \keyword "Refresh All" to update Message Log with any new messages for events that have occurred since you opened the current log. 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
IMPORTANT\0\p
If you are not in Message Log, this option is grayed out.
\p\p\1
Did You Know?\0\p
\{\1 o \0\} If you exit Message Log, it automatically updates when you re-select it.
\p\p
\{\1 o \0\} When you select Options >> Refresh All, the message log \keyword "defaults" defaults back to showing all message types. 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 o \0\} The size of the log file can affect the time it takes for refresh to update the screen.
\p\p\1
Related Topics:\0\p
\{\3\goto "Using Message Log" Using Message Log\} \p
\keyword "update message log"
\keyword "options menu"
\keyword "refresh log"
\keyword "check RAID Modules every x minutes"

\topic "Change Log Settings"
\0\p\1
Change Log Settings\0
\p\p
You can change default settings for three log parameters by selecting Options >> Log Settings from the top menu.
\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
Log Settings Parameters\0
\p\p
\{\3\subtopic "Changing The Default Log File" Changing The Default Log File\}
\p\p
\{\3\subtopic "Changing The Log Size Before Notification" Changing The Log Size Before Notification\}
\p\p
\{\3\subtopic "Changing The Checking Interval" Changing The ''Check RAID Modules every x minutes'' Interval\}
\p\p\1
Related Topics\0\p
\{\3\goto "Using Message Log" Using Message Log\} \p
\keyword "options menu"
\keyword "defaults"
\keyword "log settings"

\topic "Changing The Default Log File"
\0\p\1
Changing The Default Log File\0
\p\p\1
When To Use\0\p
\{\1 o \0\} If you want the data logged into a different file.
\p\p
\{\1 o \0\} As one of the actions you can take if the "Threshold Level Reached" message displays.
\p\p
\{\1 o \0\} To control the size of the 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\p
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
Steps To Change The Default Log File\0\p
1. From the top menu, select Options >> Log Settings.
\p\p
2. Enter the new filename you want data logged to. Be sure to enter the correct directory path if different from the current default log file.
\p\p
3. Select Save.
\p\p\1
Did You Know?\0\p
\{\1 o \0\} Any changes you make apply to all RAID Modules.
\p\p
\{\1 o \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
Related Topics\0\p
\{\3\goto "Change Log Settings" Change Log Settings\} \p
\{\3\goto "Message Log Can't Find The Default Log File" What If Message Log Cannot Find The Default Log File?\} \p
\keyword "log file, default"
\keyword "options menu"

\topic "Changing The Log Size Before Notification"
\0\p\1
Changing The Log Size Before Notification\0
\p\p\1
When To Use\0\p
Increase this \{\2\bring_popup "Threshold Values" value\} if you want your \keyword "log size before notification" log size before notification to be larger than the default setting of 40K. This does NOT set the actual size that the log can become; instead, it increases the size the log can reach before "Threshold Level Reached" message appears.
\p\p\1
What Happens\0\p
The "Threshold Level Reached" message automatically displays whenever the default \{\2\bring_popup "Log File" log file\} exceeds the value set here.
\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, we recommend that you use the default value.
\p\p\1
Steps To Change The Log Size Before Notfication\0\p
1. From the top menu, select Options >> Log Settings.
\p\p
2. Enter the value you want the new log size to be before you are notified that the value has been reached.
\p\p
3. Select Save.
\p\p\1
Did You Know?\0\p
\{\1 o \0\} Any changes you make apply to all RAID Modules.
\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 of notification.
\p\p
\{\1 o \0\} The minimum value for this parameter is 1 K.
\p\p\1
Related Topics\0\p
\{\3\goto "Change Log Settings" Change Log Settings\} \p
\keyword "log settings"
\keyword "threshold level reached"
\keyword "messages, threshold level reached"
\keyword "defaults"

\popup "Threshold Values"
\0\p
Default -- 40K
\p\p
Minimum -- 1K
\p\p
Maximum -- 1000K
\p\p
IMPORTANT \p
As the size of the message log increases, you may notice delays when you select Message Log or Options >> Refresh All. Therefore, we recommend that you use the default value. \p

\topic "Changing The Checking Interval"
\0\p\1
Changing The ''Check RAID Modules every x minutes'' Interval\0
\p\p\1
When To Use\0\p
\{\1 o \0\} Increase this \{\2\bring_popup "Checking Values" value\} if you do not want the background monitor to check the RAID Modules as frequently.
\p\p
\{\1 o \0\} Decrease this value if you want the background monitor to check the RAID Modules more often.
\p\p\4
CAUTION\0\p
\{\1 o \0\} Setting this value too small could cause the check to affect system I/O performance.
\p\p
\{\1 o \0\} Setting this value too large could delay notification of serious problems.
\p\p\1
What Happens\0\p
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 default \{\2\bring_popup "Log File" log file\} which you can view using Message Log. The log entry shows the date and time that the background \keyword "monitor, background" monitor detected the problem/event.
\p\p\1
Steps To Change The "Check RAID Modules every x minutes" Interval\0\p
1. From the top menu, select Options >> Log Settings.
\p\p
2. Enter the frequency (in minutes) that you want the background monitor to check the RAID Modules.
\p\p
3. Select Save.
\p\p\1
For Best Results\0\p
Use the default value or smaller to ensure that you are notified about problems/events as close as possible to when they occur.
\p\p\1
Did You Know?\0\p
\{\1 o \0\} Any changes you make apply to all RAID Modules.
\p\p
\{\1 o \0\} Using \keyword "Health Check" Health Check, it is possible for you to find and correct problems before the background monitor detects them. This is especially true if you change the "check RAID Modules every x minutes" interval to a time larger than the default setting (5 minutes). In cases where you have corrected problems before the background monitor detects them, these events are not detected or written to \keyword "Message Log" Message Log.
\p\p\1
Related Topics\0\p
\{\3\goto "Change Log Settings" Change Log Settings\} \p
\keyword "defaults"
\keyword "error detection"
\keyword "failures"
\keyword "check RAID Modules every x minutes"
\keyword "log settings"

\popup "Checking Values"
\0\p
Default -- 5 minutes
\p\p
Minimum -- 1 minute
\p\p
Maximum -- 59 minutes
\p\p\4
CAUTION\0\p
Setting this value too small could cause the check to affect system I/O performance. Also, setting this value too large could delay notification of serious problems. \p

\topic "Selecting Messages Or Exceptions"
\0\p\1
Selecting Messages Or Exceptions\0
\p\p\1
Summary Information Screen\0\p
At this screen, you can select messages/exceptions for viewing detailed information in either \keyword "Message Log" Message Log or \keyword "Health Check" Health Check.
\p\p\1
Selection Options:\0 Choose one:
\p\p
\{\1 o \0\} To highlight all messages/exceptions, select either (1) from the top menu Edit >> Select All, or (2) choose 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/exception.
\p\p
\{\1 o \0\} Press Shift + click to highlight a series of messages/exceptions. 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/exceptions 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.
\p\p\1
Action Options:\0 Select either:
\p\p
\{\1 o \0\} Show Details
\p\p
\{\1 o \0\} Double-click a message to show its detailed contents
\p\p\1
Show Details Screen\0\p
You can select detailed messages/exceptions and copy them to the clipboard. Perform the following steps for each item that you want to copy.
\p\p
1. From the top menu, select Edit >> Copy to Clipboard. This automatically highlights the text of the detailed message/exception 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 into an editor or desired file.
\p\p\1
Related Topics\0\p
\{\3\goto "Copy To Clipboard" Copy to Clipboard\} \p
\{\3\goto "Save The Log As Another File" Save The Log As Another File\} \p
\{\3\goto "Using Health Check" Using Health Check\} \p
\{\3\goto "Using Message Log" Using Message Log\} \p
\keyword "edit menu"
\keyword "copy to clipboard"
\keyword "selecting messages"
\keyword "selecting exceptions"
\keyword "message details"
\keyword "exception details"
\keyword "show details"

\topic "Copy To Clipboard"
\0\p\1
Copy To Clipboard\0
\p\p\1
When To Use\0\p
Use in either \keyword "Message Log" Message Log or \keyword "Health Check" Health Check when you have selected Show Details. Use to save details into a permanent record or to forward to your Customer Services Representative.
\p\p\1
Steps To Copy Detailed Messages\0\p
You need to perform the following steps for each detailed message/exception that you want to copy.
\p\p
1. From the top menu, select Edit >> Copy to Clipboard. This automatically highlights the text of the detailed message/exception 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 in an editor or desired file.
\p\p\1
Related Topics\0\p
\{\3\goto "Selecting Messages Or Exceptions" Selecting Messages Or Exceptions\} \p
\{\3\goto "Using Health Check" Using Health Check\} \p
\{\3\goto "Using Message Log" Using Message Log\} \p
\keyword "show details"
\keyword "message details"
\keyword "edit menu"
\keyword "copy to clipboard"

\topic "Using Health Check"
\0\p\1
Using Health Check\0
\p\p\1
When To Use\0\p
Use when you want to immediately check for failures on \{\2\bring_popup "I/O Data Path" I/O data path\}, drives, \{\2\bring_popup "Logical Unit" logical units\}, and other components.
\p\p
See Related Topics at the bottom of this screen for additional information on this option.
\p\p\1
What Happens\0\p
The software performs an immediate check of the selected \{\2\bring_popup "RAID Module" RAID Module\} and displays a summary of results.
\p\p\1
IMPORTANT\0\p
Only when Health Check detects exceptions can you select items for more detailed information. Show Details and Select All are grayed out for items with an Optimal status.
\p\p\1
Options\0\p
While viewing Health Check's results, you can select all or some modules that have non-optimal statuses to: \p
\{\1 o \0\} View more detailed information.
\p\p
\{\1 o \0\} Copy detailed information to the clipboard.
\p\p\1
Related Topics\0\p
\{\3\goto "Copy To Clipboard" Copy To Clipboard\} \p
\{\3\goto "Selecting Messages Or Exceptions" Selecting Messages Or Exceptions\} \p
\{\3\subtopic "Action For Modules With Exceptions Detected" What Action Do I Take For Modules With Exceptions Detected?\} \p
\{\3\subtopic "What Statuses Appear In Health Check?" What Statuses Can Appear In Health Check?\} \p
\{\3\goto "Why Did Health Check Take A Long Time?" Why Did Health Check Take A Long Time?\} \p
\keyword "error detection"
\keyword "system check"
\keyword "component errors"
\keyword "Health Check"
\keyword "checking modules"

\topic "What Statuses Appear In Health Check?"
\0\p\1
What Statuses Can Appear In Health Check?\0
\p\p
When you select Health Check, "Checking" displays until the check is completed; then, the results of the check for the selected \{\2\bring_popup "RAID Module" RAID Module\} display.
\p\p
See Related Topics at the bottom of this screen for additional information on this option.
\p\p\1
Health Statuses \p
IMPORTANT\0\p
The most commonly reported statuses that may appear as a result of performing a Health Check are shown below. There may be other statuses possible depending on the type of RAID Module system you have. Consult the "Installation And Support Guide" specific to your operating system for details. Any results other than Optimal are noted as exceptions detected.
\p\p\1
Exceptions Detected\0: In the event a status other than Optimal appears, you should highlight the non-optimal exceptions, select Show Details, and follow the recommended Action To Take.
\p\p\1
Channel Failure\0: Indicates that all the drives on the same drive channel have Failed and/or are Unresponsive. Depending on how the logical units (LUNs) have been configured across the drives, the status of the LUNs may be Dead, Degraded, or Optimal (if hot spare drives are in use).
\p\p\1
Data Path Failure:\0 Indicates some component along the \{\2\bring_popup "I/O Data Path" data path\} has failed. For example, the interface cable/terminator, network card, host adapter, or controller could have failed.
\p\p\1
IMPORTANT\0\p
If you do NOT have RDAC protection (such as with the Networked version of this software), this failure type may not be displayed for every condition. Therefore, verify that the interface cable/terminator or network connections are not removed or damaged before proceeding with any controller-related recovery procedure. \keyword "data path failure"
\p\p\keyword "path failure" \1
Drive Failure:\0 Indicates that a single drive has failed in the same \{\2\bring_popup "Configured Drive Group" drive group\}.
\p\p\keyword "drive failure" \1
Failed/Warning Drive:\0 Indicates that at least one drive has failed and one drive has been put in warning. Applicable only if you have a RAID Module with a controller version earlier than the Series 3.
\p\p\keyword "failed drive" \1
Hot Spare Failure:\0 Indicates that a \{\2\bring_popup "Hot Spare" hot spare\} drive has failed while being used in a logical unit.
\p\p\keyword "hot spare" \1
Module Component Failure:\0 Indicates that some component (power supply or fan) has failed.
\p\p\keyword "module failure" \1
Multiple Drive Failure:\0 Indicates that more than one drive has failed in the same drive group.
\p\p\keyword "multiple drive failure" \1
Multiple Offline/Failed Drives\0: Indicates that the controller has placed one or more drives Offline because data reconstruction failed and a read error occurred for one or more failed drives in the logical unit.
\p\p\keyword "offline drive failure" \1
Multiple Unresponsive Drives\0: Indicates that multiple drives in the selected RAID Module are no longer accessible to the controller. If the drives receive any I/O, the controller will fail them. \keyword "multiple unresponsive drives"
\p\p\1
Optimal:\0 No problem is indicated for the RAID Modules checked. All components are functioning normally.
\p\p\keyword "optimal" \1
Unit Failure:\0 Indicates a Dead logical unit needs to be manually formatted, so the LUN can be restored to Optimal status. This means that the failed drives have already been replaced, but Recovery Guru or Health Check was run again before Options >> Manual Recovery >> Logical Units >> Format was performed.
\p\p
Also, applicable only if you have a RAID Module with controller version earlier than the Series 3, indicates an interrupted format where either power was lost or the controller caused a reset in the middle of a create or format procedure. It results in a Dead logical unit status, but with Optimal drive statuses.
\p\p\keyword "unit failure" \1
Unresponsive Drive\0: Indicates that a drive in the selected RAID Module is no longer accessible. If the drive receives any I/O, the controller will fail it. \keyword "unresponsive drive"
\p\p\1
Warning Drive:\0 At least one drive has been placed in warning, but there are no failed drives. Applicable only if you have a RAID Module with a controller version earlier than the Series 3.
\p\p\keyword "warning drive" \1
Related Topics\0\p
\{\3\goto "Copy To Clipboard" Copy To Clipboard\} \p
\{\3\goto "Selecting Messages Or Exceptions" Selecting Messages Or Exceptions\} \p
\{\3\goto "Using Health Check" Using Health Check\} \p
\{\3\goto "Action For Modules With Exceptions Detected" What Action Do I Take For Modules With Exceptions Detected?\} \p
\{\3\goto "What Is A Hot Spare?" What Is A Hot Spare?\} \p
\{\3\goto "Can't Select Items From Health Check" Why Can't I Select Items From Health Check's Summary Screen?\} \p
\keyword "failures"
\keyword "exception details"
\keyword "component errors"
\keyword "module status"
\keyword "status, modules"

\topic "Action For Modules With Exceptions Detected"
\0\p\1
What Action Do I Take For Modules With Exceptions Detected?\0
\p\p\1
Selecting Exceptions In The Summary Information Screen\0\p
Double-click on a single exception or highlight one or more exceptions, then select Show Details to view detailed information, such as the affected component and logical unit, RAID Level and LUN Status when applicable, the probable cause of the problem, and the recommended action you should take.
\p\p\1
RAID Module\0: The specific RAID Module affected. \keyword "RAID Module"
\p\p\1
Affected Component\0: The specific component where the event/problem occurred.
\p\p\1
Affected Logical Unit\0: The specific \{\2\bring_popup "Logical Unit" logical unit\} where the event/problem occurred; given when applicable.
\p\p\1
RAID Level\0: Indicates the \{\2\bring_popup "RAID Level" RAID Level\} of the affected logical unit; given when applicable.
\p\p\1
Logical Unit Status\0: Operating condition of the affected logical unit; given when applicable. For an explanation of the possible statuses, select the "Possible Logical Unit Statuses" topic in the list below. \p
For Dead or Degraded LUNs, you should follow the recommended Action To Take in the detailed information screen.
\p\p\1
IMPORTANT\0\p
Whenever indicated in Action To Take, you should use the Recovery Application as soon as possible to correct the problem before more serious errors occur or you lose data. \keyword "Recovery Application"
\p\p\1
Options\0\p
\{\1 o \0\} In the detailed information screen, you can select Copy to Clipboard to save the contents of the detailed exception.
\p\p
\{\1 o \0\} Use the Exception Index to track the number of exceptions you highlighted in the summary information screen before selecting Show Details. For example, if the index reads 1 of 4, then you are viewing the first of four exceptions that you selected in the summary information screen.
\p\p\1
Did You Know?\0\p
It is possible to detect and correct problems using \keyword "Health Check" Health Check before the background monitor detects them. This is especially true if you change the \keyword "check RAID Modules every x minutes" "check RAID Modules every x minutes" interval to a time larger than the default setting (5 minutes). In cases where you have corrected problems before the background monitor detects them, these events are not detected or written to \keyword "Message Log" Message Log.
\p\p\1
Related Topics\0\p
\{\3\goto "Copy To Clipboard" Copy To Clipboard\} \p
\{\3\goto "Possible LUN Statuses" Possible Logical Unit Statuses\} \p
\{\3\goto "Selecting Messages Or Exceptions" Selecting Messages Or Exceptions\} \p
\{\3\goto "Using Health Check" Using Health Check\} \p
\keyword "status, modules"
\keyword "module status"
\keyword "exception details"
\keyword "exception index"
\keyword "show details"
\keyword "defaults"
\keyword "RAID Level"
\keyword "status, logical units"
\keyword "logical unit status"

\topic "Using LUN Reconstruction"
\0\p\1
Using LUN Reconstruction\0
\p\p\1
When To Use\0\p
Use to view \keyword "reconstruction progress" reconstruction progress or to change the \{\2\bring_popup "Reconstruction Rate" reconstruction rate\} for logical units undergoing reconstruction for a selected RAID Module.
\p\p
See Related Topics at the bottom of this screen for additional information on this option.
\p\p\1
What Happens\0\p
The software displays histograms indicating the \{\2\bring_popup "Reconstruction Progress" progress\} of any \{\2\bring_popup "Logical Unit" logical units\} undergoing \{\2\bring_popup "Reconstruction" reconstruction\} for the selected \{\2\bring_popup "RAID Module" RAID Module\}. Also, a Slider bar shows the current reconstruction \{\2\bring_popup "Points" rate setting\} for those logical units.
\p\p\1
IMPORTANT\0\p
\{\1 o \0\} If All RAID Modules is selected, this option is grayed out.
\p\p
\{\1 o \0\} You can change the reconstruction rate even when logical units are undergoing reconstruction. However, with this option, you can only change the rate for logical units that are reconstructing or awaiting reconstruction. To change the reconstruction rate for all logical units, whether they are reconstructing or not, use the Maintenance/Tuning Application. \keyword "Maintenance/Tuning Application"
\p\p\1
Did You Know?\0\p
\{\1 o \0\} If you exit \keyword "LUN Reconstruction" LUN Reconstruction, any logical units that have completed their reconstruction (that is, they show 100%) do not appear the next time you select it.
\p\p
\{\1 o \0\} If no logical units are currently reconstructing for the selected RAID Module, you see the message ''No LUNs Are Reconstructing.'' Select OK to exit LUN Reconstruction, then select a different RAID Module and/or another Status option.
\p\p\1
Related Topics\0\p
\{\3\subtopic "Change The Reconstruction Rate" Change The Reconstruction Rate\} \p
\{\3\goto "What Is Reconstruction?" What Is Reconstruction?\} \p
\{\3\goto "Why Are Some Options Grayed Out?" Why Are Some Options Grayed Out?\} \p
\{\3\goto "Why Did Reconstruction Take A Long Time?" Why Did Reconstruction Take A Long Time?\} \p
\keyword "reconstruction rate"
\keyword "viewing reconstruction progress"
\keyword "progress, reconstruction"

\popup "Reconstruction Progress"
\0\p
Histograms appear for each logical unit when it begins reconstruction. These graphics show the amount of reconstruction accomplished as a percentage. The response time for updating these histograms depends on the number and size of the logical units undergoing reconstruction and the rate setting for the reconstruction operation. \p

\popup "Points"
\0\p
Rate Settings \p
From left to right, the points on the Slider bar set the reconstruction rate as follows:
\p\p
(Setting = number of blocks reconstructed / seconds delay between reconstruction operations for system I/O operations to take place)
\p\p
For example, the 256/0.8 setting means that each time 256 blocks are reconstructed, reconstruction pauses for an 0.8 second interval so that system I/O can take place.
\p\p
Slow = 256 / 0.8
\p\p
Slow Medium = 256 / 0.4
\p\p
Medium = 512 / 0.4
\p\p
Medium Fast = 512 / 0.2
\p\p
Fast = 1024 / 0.1 \p

\topic "Change The Reconstruction Rate"
\0\p\1
Change The Reconstruction Rate\0
\p\p
To view the reconstruction progress for logical units undergoing reconstruction, use the Status Application. To change the reconstruction rate for all logical units, whether they are reconstructing or not, use the Maintenance/Tuning Application.
\p\p\1
Options\0\p
There are distinct \{\2\bring_popup "Points" points\} along the Slider bar that allow you to set the rate to optimize either \{\2\bring_popup "Reconstruction" reconstruction\} or system performance.
\p\p\1
Steps To Change The Reconstruction Rate\0\p\1
NOTE\0: In the Status Application's LUN Reconstruction option, when you move the Slider bar, you may notice some delay in the system's response if many or very large \{\2\bring_popup "Logical Unit" logical units\} are reconstructing. However, the rate automatically changes when you move the Slider bar. In the Maintenance/Tuning Application's LUN Reconstruction Rate option, changes do not take effect until you select Save.
\p\p
1. Select either LUN Reconstruction (Status Application) for LUNs currently reconstructing or LUN Reconstruction Rate (Maintenance/Tuning Application) for access to all LUNs.
\p\p
2. Move the Slider bar toward either: \p
\{\1 o \0\}\1 System performance\0 -- to speed up system I/O and slow reconstruction.
\p\p
\{\1 o \0\}\1 Reconstruction\0 -- to speed up the \keyword "reconstruction rate" reconstruction rate and slow system I/O.
\p\p
3. In the LUN Reconstruction Rate (Maintenance/Tuning Application), select Save for the rate changes to take effect.
\p\p\1
Related Topics\0\p
\{\3\goto "Using LUN Reconstruction" Using LUN Reconstruction\} \p
\{\3\goto "Using LUN Reconstruction Rate" Using LUN Reconstruction Rate\} \p
\{\3\goto "What Is Reconstruction?" What Is Reconstruction?\} \p
\keyword "LUN Reconstruction Rate"
\keyword "LUN Reconstruction"
\keyword "changing reconstruction rate"
\keyword "Maintenance/Tuning Application"
\keyword "Status Application"

\topic "ASC/ASCQ Error Codes"
\0\p\1
ASC/ASCQ Error Codes\0
\p\p
This document describes the various error codes returned by the Series 3 RAID controllers. On detection of an error condition, the controller will return a status of Check Condition on the command that had the error. The host should respond with a Request Sense command. On receipt of the Request Sense, the controller will return 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 \keyword "Message Log" Message Log (Show Details) when applicable for hardware messages. These codes 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 to resolve the problem.
\p\p\1
Sense Keys\0\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\0\p
Each time an error is detected, the controller will put 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 would be 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 would be denoted by an FRU code of 0x32.
\p\p\1
Additional Sense Codes And Qualifiers\0\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 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 completes.
\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 will be 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
\{\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
\{\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 have 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 controllers' 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 controller's batteries. If possible, the user should 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: 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: 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 and 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
\{\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: 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 will be 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 Re-assign Blocks command to a drive failed. The drive will be 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
(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 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
(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 field 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. The channel failure condition is reset by the controller once it undergoes a reset.
\p\p\1
ASC/ASCQ/Sense Key: 3F C7 (6)\0\p
Non-Media Component Failure \p
The controller has detected the failure of a subsystem component other than a disk, channel, or controller. The FRU codes will 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
(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\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
\{\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: 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 will return this error if: \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/Os 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: 87 08 4\0\p
Microcode Download Error \p
Incompatible board type for the code downloaded.
\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 (6),B\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 (6),E\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
\{\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 drive 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
\{\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
\{\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
\{\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: 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: 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
\{\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 subsystem and that it is functional.
\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. \p
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 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 subsystem and that it is functional.
\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
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: 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
\keyword "ASC/ASCQ"
\keyword "hardware errors"
\keyword "error messages"

\topic "Troubleshooting For Status"
\0\p\1
Troubleshooting/Common Questions
\p\p 
NOTE:\0 For more general problems/questions that could apply in any application, consult the "Troubleshooting/Common Questions" topic on the Home Page.
\p\p\1
Message Log\0\p
\{\3\subtopic "Unexpected Information In Message Log" What If I Do Not See The Information I Expected In Message Log?\}
\p\p
\{\3\subtopic "Message Log Can't Find The Default Log File" What If Message Log Cannot Find The Default Log File?\}
\p\p
\{\3\subtopic "The ''No Match Found'' Message Displays" What If The ''No Match Found'' Message Displays?\}
\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
Health Check\0\p
\{\3\goto "The ''Optimal (Health Check Not Done)'' Message Displays" What If Health Check Displays The ''Optimal (Health Check Not Done)'' Message?\}
\p\p
\{\3\subtopic "Can't Select Items From Health Check" Why Can't I Select Items From Health Check's Summary Screen?\}
\p\p
\{\3\subtopic "Why Did Health Check Take A Long Time?" Why Did Health Check Take A Long Time?\}
\p\p\1
LUN Reconstruction \0\p
\{\3\subtopic "Why Did Reconstruction Take A Long Time?" Why Did Reconstruction Take A Long Time?\}
\p\p\1
Related Topics\0\p
\{\3\goto "Status Application" Status Application\} \p
\{\3\goto "Troubleshooting For All Applications" Troubleshooting/Common Questions For All Applications\} \p

\topic "Unexpected Information In Message Log"
\0\p\1
What If I Do Not See The Information I Expected In Message Log?\0
\p\p\1
What Message Log Normally Displays\0\p
Any time you leave and return to \keyword "Message Log" Message Log, you see \p
\{\1 o \0\} All message types displayed (the default setting is All)
\p\p
\{\1 o \0\} The default or most recently selected \{\2\bring_popup "Log File" log file\}
\p\p\1
IMPORTANT\0\p
You can change the log that is displayed by selecting (from the top menu) File >> Open Log. This new log continues to display until the next time you use Open Log again or exit and re-select Status. For example, if you open status.log, and select other Status options, such as Locate Module, this log continues to display when you return to Message Log. Once you exit the Status Application and return, however, the default log displays again.
\p\p\1
What If No Messages Are Displayed?\0\p
If you do not see any messages displayed in Message Log, then 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 \keyword "List Type" 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. If you see this message and feel that an empty log is not possible, \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\1
Related Topics\0\p
\{\3\subtopic "UNIX Options" UNIX Options\} \p
\{\3\subtopic "Windows NT Options" Windows NT Options\} \p
\keyword "defaults"
\keyword "message types"

\topic "UNIX Options"
\0\p\1
UNIX Options\0
\p\p
1. Check file permissions of 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? Execute access to a directory means the ability to get a directory listing.
\p\p
3. Is the arraymon daemon actually running? 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
\keyword "UNIX options"
\keyword "options, UNIX"

\topic "Windows NT Options"
\0\p\1
Windows NT 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? 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? Does it contain the ''putplog %1'' line somewhere?
\p\p
4. Does the file ''putplog.exe'' exist in the software's directory? \p
\keyword "Windows NT options"
\keyword "options, Windows NT"

\topic "Message Log Can't Find The Default Log File"
\0\p\1
What If Message Log Cannot Find The Default Log File?\0
\p\p
When you select Message Log, the file that appears is the one designated as the default (as set in Options >> Log Settings). However, it is possible that you could see a message that the default log file was not found. This would be possible, if the default log file has been deleted, but is still entered as the default in Log Settings.
\p\p
If you see this message, you also are asked if you want the software to create a log file. \p
\{\1 o \0\} If you select OK, an empty log file is created using the default log's filename.
\p\p
\{\1 o \0\} If you select NO, you exit Message Log. Select a different 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

\topic "The ''No Match Found'' Message Displays"
\0\p\1
What If The ''No Match Found'' Message Displays?\0
\p\p
This message can appear in \keyword "Message Log" Message Log, \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 RAID Module if you selected All RAID Modules.
\p\p
This message means that the \{\2\bring_popup "RAID Module" RAID Module\} no longer exists or is no longer connected to the host system (the software cannot detect it). Check to be sure that the selected module is connected. If the RAID Module is one that no longer exists, try selecting another module. \p
\keyword "messages, no match found"

\topic "Log Settings Apply To Which RAID Modules?"
\0\p\1
Will Changing Log Settings Apply To Each Selected RAID Module Or To All RAID Modules?\0
\p\p
Changing any parameter in Options >> Log Settings always applies to all RAID Modules, regardless of which \{\2\bring_popup "RAID Module" RAID Module\} you may have initially selected. From the top menu, select Options, then Log Settings. \p
\keyword "log settings"
\keyword "options menu"

\topic "Can't Select Items From Health Check"
\0\p\1
Why Can't I Select Items From Health Check's Summary Screen?\0
\p\p
Only when \keyword "Health Check" Health Check detects exceptions can you select items for more detailed information. The Show Details and Select All options are grayed out for items with an Optimal status. \p
\keyword "summary information screen"

\topic "Why Did Health Check Take A Long Time?"
\0\p\1
Why Did Health Check Take A Long Time?\0
\p\p
Normally you see the results from selecting Health Check in a few seconds. However, if you have selected All RAID Modules or there are I/O operations running, you might notice a delay. \keyword "Health Check"
\p\p
There could be instances where some status change affects the \{\2\bring_popup "Controller" controller's\} ability to provide a result in Health Check. While such occurrences are rare, if you experience long delays in performing Health Check, you might try checking one RAID Module at a time. \p

\topic "Why Did Reconstruction Take A Long Time?"
\0\p\1
Why Did Reconstruction Take A Long Time?\0
\p\p
The amount of time that 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. If the reconstruction process takes too long, consider changing the reconstruction rate to better optimize reconstruction. Use LUN Reconstruction to change the rate setting while reconstruction is occurring. \p
\keyword "reconstruction time"
\keyword "time, reconstruction"

\topic "Recovery Application"
\0\p\1
Recovery Application\0
\p\p
\{\3\subtopic "Recovery Task Summary" Task Summary\}
\p\p
\{\3\subtopic "Using Recovery Guru" Recovery Guru\}
\p\p
\{\3\subtopic "Using Manual Parity Check/Repair" Manual Parity Check/Repair\}
\p\p
\{\3\subtopic "Using Manual Recovery" Manual Recovery\}
\p\p
\{\3\subtopic "Troubleshooting For Recovery" Troubleshooting/Common Questions\}
\p\p\1
Related Topics\0\p
\{\3\goto "Tasks For All Applications" Task Summary\} \p
\{\3\goto "Troubleshooting For All Applications" Troubleshooting/Common Questions For All Applications\} \p

\topic "Recovery Task Summary"
\0\p\1
RECOVERY TASK SUMMARY\0
\p\p
\{\2\bring_popup "Recovery Guru Tasks" Fixing A Failure Using Recovery Guru\}
\p\p
\{\2\bring_popup "Manual Recovery Tasks" Manually Performing Recovery Procedures\}
\p\p
\{\2\bring_popup "Fail Drive Tasks" Failing A Drive Manually\}
\p\p
\{\2\bring_popup "Reconstruct Drive Tasks" Starting Drive Reconstruction Manually\}
\p\p
\{\2\bring_popup "Revive Drive Tasks" Reviving A Drive Manually\}
\p\p
\{\2\bring_popup "Format Logical Unit Tasks" Formatting A Logical Unit Manually\}
\p\p
\{\2\bring_popup "Revive Logical Unit Tasks" Reviving A Logical Unit Manually\}
\p\p
\{\2\bring_popup "Controller Pairs Tasks" Placing A Controller Offline/Online Manually\}
\p\p
\{\2\bring_popup "Manual Parity Check/Repair Tasks" Checking Parity Manually\}
\p\p\1
Related Topics\0\p
\{\3\goto "Recovery Application" Recovery Application\} \p
\{\3\goto "Tasks For All Applications" Task Summary For All Applications\}

\popup "Recovery Guru Tasks"
\p
IMPORTANT: Any time you suspect a component failure, select Recovery Guru BEFORE attempting any manual recovery procedure.
\p\p
Select one or All RAID Modules, then Recovery Guru. Then, highlight the first failure type (non-Optimal) and select Fix. Follow the instructions provided very carefully in the order they are given. \p
\keyword "Recovery Guru"
\keyword "fixing failures"

\popup "Manual Recovery Tasks"
\p
From the top menu, select Options >> Manual Recovery, then either Drives, Logical Units, or Controller Pairs to perform specific recovery options manually.
\p\p
NOTE: However, it is best to use Recovery Guru first. \p
\keyword "Manual Recovery"

\popup "Fail Drive Tasks"
\p
From the top menu, select Options >> Manual Recovery >> Drives, and use the Fail option to manually fail a drive.
\p\p
IMPORTANT: However, it is best to wait and let the controller fail a drive, then use Recovery Guru to replace the drive. \p
\keyword "failing drives"
\keyword "Manual Recovery -- Drives"

\popup "Reconstruct Drive Tasks"
\p
From the top menu, select Options >> Manual Recovery >> Drives, and use the Reconstruct option to manually begin reconstruction on a drive. Normally, drive reconstruction begins automatically once you replace a failed drive. \p
\keyword "reconstructing drives"
\keyword "drive reconstruction"
\keyword "Manual Recovery -- Drives"

\popup "Revive Drive Tasks"
\p
From the top menu, select Options >> Manual Recovery >> Drives, and use the Revive option to manually revive a drive if you accidentally removed the wrong drive and it was Optimal.
\p\p
IMPORTANT: Never use this procedure if the controller has marked the drive as failed. Instead, use Recovery Guru to diagnose and correct the problem. \p
\keyword "reviving drives"
\keyword "Manual Recovery -- Drives"

\popup "Format Logical Unit Tasks"
\p
From the top menu, select Options >> Manual Recovery >> Logical Units, and use the Format option to \keyword "reformat" reformat a Dead logical unit after you have replaced the failed drives in the drive group. This procedure applies to every LUN in the affected drive group.
\p\p
IMPORTANT: It is best to use Recovery Guru to fix Dead or Degraded logical units. \p
\keyword "formatting a logical unit"
\keyword "Manual Recovery -- Logical Units"

\popup "Revive Logical Unit Tasks"
\p
From the top menu, select Options >> Manual Recovery >> Logical Units, and use the Revive option to revive a logical unit.
\p\p
IMPORTANT: You should not use this procedure unless recommended by Recovery Guru. \p
\keyword "reviving logical units"
\keyword "Manual Recovery -- Logical Units"

\popup "Controller Pairs Tasks"
\p
From the top menu, select Options >> Manual Recovery >> Controller Pairs to stop a selected controller from accepting I/O requests by placing a controller offline, or to return a controller to operating condition by placing it online after placing it offline or after replacing it.
\p\p
NOTE: It is best, however, to use Recovery Guru to replace a controller. \p
\keyword "Manual Recovery -- Controller Pairs"
\keyword "offline"
\keyword "online"

\popup "Manual Parity Check/Repair Tasks"
\p
Select Manual Parity Check/Repair for a single or all RAID Modules and highlight any logical units that have Optimal statuses and are NOT RAID 0. Then, select Start Manual Parity Check/Repair to begin the parity operation. \p
\keyword "Manual Parity Check/Repair"
\keyword "checking parity"

\topic "Using Recovery Guru"
\0\p\1
Using Recovery Guru\0
\p\p\1
When To Use\0\p
Use to check selected \{\2\bring_popup "RAID Module" RAID Modules\} for failures and then recover from them by following step-by-step instructions.
\p\p\4
CAUTION\0\p
Always select \keyword "Recovery Guru" Recovery Guru BEFORE attempting any manual recovery procedure because Recovery Guru's diagnosis takes into account your module's configuration (that is, the relationship between RAID Level and drive groups). Therefore, its recommended recovery procedure will take you through every step and check to make sure you are correcting the right problem and not, for example, replacing drives or controllers just because they show a Failed status.
\p\p
See Related Topics at the bottom of this screen for additional information on this option.
\p\p\1
What Happens\0\p
Performs an immediate check \keyword "checking modules" of the selected RAID Module and displays the status for each module. Each failure detected for a module appears on a single line. Recovery Guru provides step-by-step instructions to fix failures.
\p\p\1
IMPORTANT\0\p
\{\1 o \0\} The Fix option is grayed out if all the selected modules have Optimal statuses.
\p\p
\{\1 o \0\} You cannot highlight any module with an Optimal status (that is, with no failures) or that has already been fixed (that is, unless a No appears in the Fixed? column).
\p\p\1
Options\0\p
Select one of the failures listed, then Fix, and follow the \keyword "step-by-step recovery" step-by-step instructions given to recover from that failure.
\p\p\1
For Best Results\0\p
When you see more than one failure listed, select the first item in the list. In such cases, Recovery Guru lists failures in the order (top to bottom) that you should fix them. For example, it is best to fix a controller failure before any drive failures.
\p\p\1
Related Topics\0\p
\{\3\goto "How Can I Check For Component Failures?" How Can I Check For Component Failures?\} \p
\{\3\subtopic "Fixing A Failure" Fixing A Failure\} \p
\{\3\subtopic "Possible Failures Shown In Recovery Guru" Possible Failures Shown In Recovery Guru\} \p
\{\3\subtopic "Information In Recovery Guru" What Information Appears In Recovery Guru?\} \p
\{\3\goto "Why Are Some Options Grayed Out?" Why Are Some Options Grayed Out?\} \p
\keyword "fixing failures"
\keyword "module, failures"

\topic "Information In Recovery Guru"
\0\p\1
What Information Appears In Recovery Guru?\0
\p\p
When you select \keyword "Recovery Guru" Recovery Guru, you see whether or not the selected RAID Module has any failures, and whether or not a failure has been fixed.
\p\p
See Related Topics at the bottom of this screen for additional information on this option.
\p\p\1
RAID Module\0: Indicates the specific module. \p
It is possible to see a \keyword "RAID Module" RAID Module listed more than once when it has multiple failures. For example, if RAID Module 1 has both a failed drive and a failed fan, two entries appear for this module: Drive Failure on one line and Module Component Failure on another line. Also, you see two Drive Failure entries on separate lines when failed drives exist on more than one \{\2\bring_popup "Configured Drive Group" drive group\}.
\p\p\1
Failure\0: Lists the component failure for the particular module. Possible \keyword "failure type" failures appear for drives/logical units, data path (interface cables/terminators, network cards, controllers, or host adapters), other component failures (fan/power supply), and logical unit create/formats that fail.
\p\p\1
Fixed?\0: Indicates whether or not you have fixed that failure. \p
\{\1 o \0\} The column appears blank if the RAID Module is Optimal (that is, there are no failures). \keyword "failure fixed?"
\p\p
\{\1 o \0\} No in the column means that the failure has not been fixed. Highlight this module and select Fix to follow the step-by-step instructions for fixing this failure.
\p\p
\{\1 o \0\} Yes in the column means that you selected Fix and performed the step-by-step instructions. The next time you select Recovery Guru, any items that had Yes should appear as Optimal and this column is blank.
\p\p\1
Related Topics\0\p
\{\3\goto "Fixing A Failure" Fixing A Failure\} \p
\{\3\goto "Possible Failures Shown In Recovery Guru" Possible Failures Shown In Recovery Guru\} \p
\{\3\goto "Using Recovery Guru" Using Recovery Guru\} \p

\topic "Fixing A Failure"
\0\p\1
Fixing A Failure\0
\p\p\1
IMPORTANT\0\p
\{\1 o \0\} When you use \keyword "Recovery Guru" Recovery Guru, follow the instructions very carefully and perform all the steps in the order they are presented. To not do so could lead to unexpected results and you may not correct the failure. \keyword "step-by-step recovery"
\p\p
\{\1 o \0\} You can only select one failure at a time to perform a recovery procedure. Also, you can only fix modules that have a failure. You cannot highlight any module with an Optimal status.
\p\p\1
For Best Results\0\p
When you see more than one failure listed, select the first item in the list. In such cases, Recovery Guru lists failures in the order (top to bottom) that you should fix them.
\p\p\1
Steps To Fix A Failure\0\p
1. Select one or all RAID Modules, then Recovery Guru.
\p\p
2. Highlight one failure and either \p \keyword "fixing failures"
\{\1 o \0\} Select Fix.
\p\p
\{\1 o \0\} Double-click on the item.
\p\p
3. Follow the step-by-step instructions you see on screen very carefully. When you complete the recovery procedure, notice that the Fixed? column in the main screen says Yes.
\p\p\1
IMPORTANT\0\p
\{\1 o \0\} Do not select OK at any time unless you have completed all the steps as instructed. Be sure to replace any failed item when instructed. Once an item is marked as fixed (Yes), you cannot re-select it until the next time you select Recovery Guru and it reports a failure on the module again.
\p\p
\{\1 o \0\} When recovering from a Module Component Failure (fan or power supply), wait ten minutes before re-selecting Recovery Guru. Otherwise, the software continues to report the condition as a failure during this time.
\p\p
\{\1 o \0\} Select Cancel, when offered, if you want to stop the recovery procedure. However, you are NOT correcting the failure.
\p\p
4. Select one: \p
\{\1 o \0\} Repeat these steps starting at Step 2 for each additional failure.
\p\p
\{\1 o \0\} Use Manual Parity Check/Repair to check parity when recommended.
\p\p
\{\1 o \0\} Use the Status Application to view reconstruction progress when recommended. \keyword "Status Application"
\p\p\1
Related Topics\0\p
\{\3\goto "Using Recovery Guru" Using Recovery Guru\} \p
\keyword "Fix option"

\topic "Possible Failures Shown In Recovery Guru"
\0\p\1
Possible Failures Shown In Recovery Guru\0
\p\p\1
IMPORTANT\0\p
The most commonly reported failure types are shown below. There may be other statuses possible depending on the type of RAID Module system you have. Consult the "Installation And Support Guide" specific to your operating system for details.
\p\p\1
Drives\0\p
The correct procedure for recovering from a drive failure varies depending on the \{\2\bring_popup "RAID Level" RAID Level\} of the affected logical units and the number of drives failed within one \{\2\bring_popup "Configured Drive Group" drive group\}.
\p\p\1
Drive Failure\0: One drive in a drive group has failed. A single RAID Module could show this failure on more than one line, as long as the failed drives belong to different drive groups. \keyword "drive failure"
\p\p\1
Hot Spare Failure\0: A \{\2\bring_popup "Hot Spare" hot spare\} drive has failed while being used by a logical unit on the RAID Module. \keyword "hot spare"
\p\p\1
Multiple Drive Failure\0: More than one drive in the same drive group has failed on a RAID Module. \keyword "multiple drive failure"
\p\p\1
Multiple Offline/Failed Drives\0: One or more drives has been placed Offline because data reconstruction failed and a read error occurred for one or more Failed drives in the logical unit.
\p\p\keyword "offline drive failure" \1
Multiple Unresponsive Drives\0: The controller is unable to communicate with multiple drives in the selected RAID Module. \keyword "multiple unresponsive drives"
\p\p\1
Unresponsive Drive\0: The controller is unable to communicate with a drive in the selected RAID Module. \keyword "unresponsive drive"
\p\p\1
IMPORTANT\0\p
In case of either unresponsive-drive failure type, the drive status in Module Profile >> Drives and in Options >> Manual Recovery >> Drives is most likely Unresponsive. If the drive receives any I/O, the controller will fail it. Also, you may want to determine which drive is Unresponsive, then if you want to manually fail it, use Options >> Manual Recovery >> Drives.
\p\p\1
Warning Drive\0: At least one drive has been placed in Warning for the RAID Module. Applicable only if your module has a controller version earlier than the Series 3. Refer to your software documentation for the correct recovery procedure to follow. \keyword "warning drive"
\p\p\1
Other Failures \p
Channel Failure\0: All the drives on the same drive channel have Failed and/or are Unresponsive. Depending on how the logical units (LUNs) have been configured across these drives, the status of the LUNs may be Dead, Degraded, or Optimal (if hot spare drives are in use).
\p\p\1
Data Path Failure\0: A controller is not receiving/accepting I/O. For Networked versions, this means the controller is not responding to the storage management software.
\p\p
This failure could be the result of a problem with the interface cable/terminator, network card, controller, or the host adapter. The correct procedure for recovering from a data path failure varies depending on where the failure occurred. For example, the correct procedure for recovering from a controller failure depends on how many and what type of controllers the affected module has.
\p\p\1
IMPORTANT\0\p
If you do NOT have RDAC protection (such as with the Networked version of this software), this failure type may not be displayed for every condition. Therefore, verify that the interface cable/terminator or network connections are not removed or damaged before proceeding with any controller-related recovery procedure. \keyword "data path failure"
\p\p\1
Module Component Failure\0: Either single or multiple fans or power supplies have failed. \keyword "module component failure"
\p\p\1
IMPORTANT\0\p
When recovering from a Module Component Failure, wait ten minutes before re-selecting Recovery Guru. Otherwise, this condition may continue to be reported as a failure. \keyword "fan failure"
\p\p\1
Unit Failure\0: A Dead logical unit needs to be manually formatted, so the LUN can be restored to Optimal status. This means that the failed drives have already been replaced, but Recovery Guru or Health Check was run again before Options >> Manual Recovery >> Logical Units >> Format was performed.
\p\p
Also, applicable only if your module has a controller version earlier than the Series 3, a logical unit \keyword "create fail" create or format operation has failed because either power was lost or the controller caused a reset. It results in a Dead logical unit status, but with Optimal drive statuses. \keyword "unit failure"
\p\p\1
Related Topics\0\p
\{\3\goto "Using Recovery Guru" Using Recovery Guru\} \p
\{\3\goto "Information In Recovery Guru" What Information Appears In Recovery Guru?\} \p
\{\3\goto "What Is A Hot Spare?" What Is A Hot Spare?\} \p
\keyword "power supply failure"
\keyword "controller failure"
\keyword "Recovery Guru"
\keyword "host adapter"
\keyword "format fail"

\topic "Using Manual Parity Check/Repair"
\0\p\1
Using Manual Parity Check/Repair\0
\p\p\1
When To Use\0\p
Use to manually check and repair \{\2\bring_popup "Parity" parity\} on selected \{\2\bring_popup "Logical Unit" logical units\}. Because an automatic parity check/repair runs daily, checking parity manually is only necessary when some recovery procedure has been performed that could result in parity inconsistencies. For example, you may want to check parity after performing most Manual Recovery procedures.
\p\p
See Related Topics at the bottom of this screen for additional information on this option.
\p\p\1
What Happens\0\p
Displays a list of logical units for the selected RAID Module and allows you to run \{\2\bring_popup "Parity Check/Repair" parity check/repair\} on one or more logical units with Optimal statuses. Also, once you start the parity check/repair operation, a histogram shows the percentage of progress for each selected logical unit. \keyword "progress, parity"
\p\p\1
IMPORTANT\0\p
The Start Parity Check/Repair option is grayed out if you select one or more logical units (LUN) that (1) are RAID Level 0 or (2) have a LUN status other than Optimal.
\p\p\1
Options\0\p
\{\1 o \0\} Highlight each logical unit that you want to check/repair parity on, and start the operation.
\p\p
\{\1 o \0\} View the progress of parity check/repair for each LUN selected.
\p\p\1
Related Topics\0\p
\{\3\goto "Stop Parity Check/Repair When Running" Can I Stop Parity Check/Repair When It Is Running?\} \p
\{\3\goto "Another Way To Run Parity Check/Repair" Is There Another Way To Run Parity Check/Repair Besides Manually?\} \p
\{\3\subtopic "Highlighting Items In A List" Highlighting Items In A List\} \p
\{\3\subtopic "Starting Manual Parity Check/Repair" Starting Manual Parity Check/Repair\} \p
\{\3\subtopic "What Does Manual Parity Check/Repair Do?" What Does Manual Parity Check/Repair Do?\} \p
\{\3\subtopic "Information In Manual Parity Check/Repair" What Information Appears In Manual Parity Check/Repair?\} \p
\{\3\goto "What Is Parity?" What Is Parity?\} \p
\{\3\goto "Why Are Some Options Grayed Out?" Why Are Some Options Grayed Out?\} \p
\keyword "Manual Parity Check/Repair"
\keyword "checking logical units"
\keyword "checking modules"
\keyword "module, parity"
\keyword "parity check/repair"
\keyword "checking parity"

\topic "Information In Manual Parity Check/Repair"
\0\p\1
What Information Appears In Manual Parity Check/Repair?\0
\p\p
When you select Manual Parity Check/Repair, information displays for all the logical units on the selected RAID Module. You can select one or more logical units with an Optimal status to run the \{\2\bring_popup "Parity Check/Repair" parity\} operation.
\p\p
See Related Topics at the bottom of this screen for additional information on this option.
\p\p\1
RAID Module\0: The specific module containing the logical unit. It is possible to see a \keyword "RAID Module" RAID Module listed more than once.
\p\p\1
Logical Units\0: Number that identifies the logical units configured for a particular RAID Module. Each line shows only one \{\2\bring_popup "LUN" LUN\}. \keyword "LUN Number"
\p\p\1
RAID Level\0: Indicates the \{\2\bring_popup "RAID Level" RAID Level\} of the logical unit. \keyword "RAID Level"
\p\p\1
Logical Unit Status\0: Operating condition of the affected logical units. For an explanation of the possible statuses, select the "Possible Logical Unit Statuses" topic in the list below. \p \keyword "logical unit status"
For Dead or Degraded LUNs, you should select Recovery Guru and follow the step-by-step instructions provided. \keyword "status, logical units"
\p\p\1
Parity Check/Repair Progress\0: A histogram appears for a logical unit when it begins parity check/repair. This graphic shows the amount of parity check/repair accomplished as a percentage, and starts over from 0% as each new LUN begins parity check. The response time for updating this histogram depends on the number and size of the logical units undergoing parity check/repair. \keyword "progress, parity"
\p\p\1
IMPORTANT\0\p
You cannot perform other Recovery Application operations until parity check/repair is completed for all selected logical units unless you cancel the operation.
\p\p\1
Related Topics\0\p
\{\3\goto "Possible LUN Statuses" Possible Logical Unit Statuses\} \p
\{\3\goto "Using Manual Parity Check/Repair" Using Manual Parity Check/Repair\} \p
\{\3\goto "What Is Parity?" What Is Parity?\} \p
\{\3\goto "Parity Check/Repair Takes A Long Time" Why Would Parity Check/Repair Take A Long Time?\} \p

\topic "Starting Manual Parity Check/Repair"
\0\p\1
Starting Manual Parity Check/Repair\0
\p\p\4
CAUTION\0\p
\{\2\bring_popup "RAID 0" RAID Level 0\} does not have parity and, therefore, cannot be checked and repaired. Additionally, you cannot run parity check/repair on RAID 1, 3, or 5 logical units with a status other than Optimal. 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. Parity inconsistencies might indicate corrupt data. You may be able to use your operating system to verify your data. 
\p\p\1
IMPORTANT\0\p
You cannot perform other Recovery Application operations until parity check/repair is completed for all selected logical units unless you cancel the operation.
\p\p\1
Steps To Begin Manual Parity Check/Repair\0\p
1. Select \keyword "Manual Parity Check/Repair" Manual Parity Check/Repair.
\p\p
2. Highlight one or more logical units (LUN) in the list with a status of Optimal.
\p\p\1
IMPORTANT\0\p
The Start Parity Check/Repair option is grayed out if you select one or more LUNs that (1) are RAID Level 0 or (2) have a LUN status other than Optimal.
\p\p
3. Select Start Parity Check/Repair.
\p\p
4. View the progress of the parity check/repair operation. A new histogram appears for each selected LUN when its check begins. \keyword "progress, parity"
\p\p\1
IMPORTANT\0\p
You can select Cancel at any time parity is occurring. However, if you stop this operation, your parity has not been completely checked or repaired.
\p\p
5. When parity check/repair is complete, one of two confirmation boxes appears: \p
\{\1 o \0\} Parity is complete and no inconsistencies were found. \keyword "inconsistencies, parity"
\p\p
\{\1 o \0\} Parity is complete and inconsistencies were found and repaired on specific LUNs.
\p\p
6. Select OK to return to the logical units list.
\p\p\1
Related Topics\0\p
\{\3\goto "Highlighting Items In A List" Highlighting Items In A List\} \p
\{\3\goto "What Does Manual Parity Check/Repair Do?" What Does Manual Parity Check/Repair Do?\} \p
\{\3\goto "Using Manual Parity Check/Repair" Using Manual Parity Check/Repair\} \p
\{\3\goto "Parity Check/Repair Takes A Long Time" Why Would Parity Check/Repair Take A Long Time?\} \p
\keyword "starting parity check"
\keyword "how to start parity check"

\topic "What Does Manual Parity Check/Repair Do?"
\0\p\1
What Does Manual Parity Check/Repair Do?\0
\p\p
When you highlight logical units (LUN) and select Start Parity Check/Repair, the selected RAID 1, 3, or 5 LUNs are scanned for parity inconsistencies. This operation only applies to selected LUNs with an Optimal status. 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.
\p\p
When the parity operation finishes, you see whether or not inconsistencies were found and repaired for each LUN. Also, if inconsistencies were found and repaired, a parity-event entry is logged in the Message Log \keyword "Status Application" (Status Application).
\p\p\1
IMPORTANT\0\p
\{\1 o \0\} Start Parity Check/Repair is grayed out if you select one or more logical units that (1) are RAID Level 0 or (2) have a LUN status other than Optimal.
\p\p
\{\1 o \0\} You cannot perform other Recovery Application operations until parity check/repair is completed for all selected logical units unless you cancel the operation.
\p\p
\{\1 o \0\} We strongly recommend you leave the Automatic Parity Check/Repair option enabled in the \keyword "Maintenance/Tuning Application" Maintenance/Tuning Application (Options >> Auto Parity Settings). With this option enabled, parity on your logical units can be checked and repaired daily. \keyword "parity, automatic operation"
\p\p
\{\1 o \0\} Parity inconsistencies might indicate corrupt data. You may be able to use your operating system to verify your data.
\p\p\1
Related Topics\0\p
\{\3\goto "Using Manual Parity Check/Repair" Using Manual Parity Check/Repair\} \p

\topic "Highlighting Items In A List"
\0\p\1
Highlighting Items In A List\0
\p\p
You can select multiple items to perform an action for certain options:
\p\p
\1 In Recovery\0\p
\{\1 o \0\} Manual Parity Check/Repair \keyword "Manual Parity Check/Repair"
\p\p
\{\1 o \0\} Manual Recovery >> Drives \keyword "Manual Recovery"
\p\p
\{\1 o \0\} Manual Recovery >> Logical Units.
\p\p\1
In Maintenance/Tuning\0\p
\{\1 o \0\} LUN Balancing \keyword "LUN Balancing"
\p\p
\{\1 o \0\} Controller Mode \keyword "Controller Mode"
\p\p\1
Selection Options\0\p
Choose one: \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.
\p\p\1
Related Topics\0\p
\{\3\goto "Manual Recovery For Drives" Manual Recovery For Drives\} \p
\{\3\goto "Manual Recovery For LUNs" Manual Recovery For Logical Units\} \p
\{\3\goto "Using Controller Mode" Using Controller Mode\} \p
\{\3\goto "Using LUN Balancing" Using LUN Balancing\} \p
\{\3\goto "Using Manual Parity Check/Repair" Using Manual Parity Check/Repair\} \p
\keyword "selecting items"

\topic "Using Manual Recovery"
\0\p\1
Using Manual Recovery\0
\p\p\1
When To Use\0\p
Use to perform recovery steps manually for drives, logical units, and controller pairs. In most cases, however, you should select \keyword "Recovery Guru" Recovery Guru and follow the step-by-step instructions provided there.
\p\p\4
CAUTION\0\p
\{\1 o \0\} Do not use Manual Recovery unless specifically directed by your software documentation or a Customer Services Representative. To do so could result in the loss of data.
\p\p
\{\1 o \0\} 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 logical unit and the number of drives in one \{\2\bring_popup "Configured Drive Group" drive group\} that have failed. Similarly, the type of 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
See Related Topics at the bottom of this screen for additional information on this option.
\p\p\1
What Happens\0\p
Displays information about the module's component status based on which option you select: drives, logical units, or controller pairs.
\p\p\1
IMPORTANT\p\0
\{\1 o \0\} If All RAID Modules is selected, this option is grayed out.
\p\p
\{\1 o \0\} Controller Pairs \keyword "controller pairs" is grayed out if the selected RAID Module has only one controller.
\p\p\1
Options\0\p
\{\1 o \0\} When you select Drives, you have options for failing, reconstructing, or reviving drives.
\p\p
\{\1 o \0\} When you select Logical Units, you have options for formatting or reviving logical units.
\p\p
\{\1 o \0\} When you select Controller Pairs, you have options for placing controllers offline or online.
\p\p\1
Related Topics\0\p
\{\3\goto "About A RAID Module's Controllers" How Can I Tell How Many And What Kind Of Controllers A RAID Module Has?\} \p
\{\3\subtopic "Manual Recovery For Controller Pairs" Manual Recovery For Controller Pairs\} \p
\{\3\subtopic "Manual Recovery For Drives" Manual Recovery For Drives\} \p
\{\3\subtopic "Manual Recovery For LUNs" Manual Recovery For Logical Units\} \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\goto "Using Recovery Guru" Using Recovery Guru\} \p
\{\3\goto "Why Are Some Options Grayed Out?" Why Are Some Options Grayed Out?\} \p
\keyword "data loss"

\topic "Manual Recovery For Drives"
\0\p\1
Manual Recovery For Drives
\p\p\4
CAUTION\0\p
\{\1 o \0\} Do not use Manual Recovery unless specifically directed by your software documentation or a Customer Services Representative. To do so could result in the loss of data.
\p\p
\{\1 o \0\} Do not attempt to manually recover from a drive failure without understanding the circumstances of the failure. The correct procedure varies depending on the RAID Level of the affected logical unit and the number of drives in one drive group that have failed. Therefore, it is best to use Recovery Guru.
\p\p\1
IMPORTANT\0\p
If All RAID Modules is selected, Options on the top menu is grayed out.
\p\p\1
What Information Appears\0\p
Status information for all the drives in the selected RAID Module displays. \keyword "options menu"
\p\p\1
Location\0: Designation indicating the \keyword "drive location" location of the drive in the selected RAID Module. There is also a label on the drive with the corresponding location identifier. \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; so that, [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 list below. \p
For Failed, Offline, or Warning drives, you should select Recovery Guru and follow the step-by-step instructions provided. \keyword "drive status"
\p\p\1
Logical Units\0: Number that identifies the logical units contained on the drive. The number repeats 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 comprise that LUN/drive group. \keyword "LUN Number"
\p\p\1
RAID Level\0: Indicates the \{\2\bring_popup "RAID Level" RAID Level\} of the logical unit containing the drive. \keyword "RAID Level"
\p\p\1
Logical Unit Status\0: Operating condition of the affected logical unit. For an explanation of the possible statuses, select the "Possible Logical Unit Statuses" topic in the list below. \p
For Dead or Degraded LUNs, you should select Recovery Guru and follow the step-by-step instructions provided. \keyword "logical unit status"
\p\p\1
Did You Know?\0\p
When a drive is \{\2\bring_popup "Unassigned Drive Group" unassigned\} (that is, not configured as part of a logical unit), you see dashes in every column except location. There is no status, LUN, RAID Level, or logical unit status to report.
\p\p\1
Options\0\p
Highlight one or more drives with non-Optimal statuses and select the recovery operation you wish to perform:
\p\p
\{\3\subtopic "Failing A Drive" Failing A Drive\}
\p\p
\{\3\subtopic "Reconstructing A Drive" Reconstructing A Drive\}
\p\p
\{\3\subtopic "Reviving A Drive" Reviving A Drive\}
\p\p\1
Related Topics\0\p
\{\3\goto "Possible Drive Statuses" Possible Drive Statuses\} \p
\{\3\goto "Possible LUN Statuses" Possible Logical Unit Statuses\} \p
\{\3\goto "Highlighting Items In A List" Highlighting Items In A List\} \p
\{\3\goto "Using Manual Recovery" Using Manual Recovery\} \p
\keyword "status, drives"
\keyword "status, logical units"
\keyword "failing drives"
\keyword "reconstructing drives"
\keyword "reviving drives"
\keyword "unassigned drives"
\keyword "Manual Recovery -- Drives"

\topic "Failing A Drive"
\0\p\1
Failing A Drive\0
\p\p
You cannot fail drives that have a status of Replaced or that contain logical units that are currently reconstructing or formatting. It is best to wait and let the controller fail a drive; however, you may want to use this option if you want to replace a drive for some reason before the controller has failed it. For example, if Recovery Guru is unable to complete a Health Check because a drive is Unresponsive, use Options >> Manual Recovery >> Drives to determine which drive is Unresponsive, then this option to fail and replace it.
\p\p\4
CAUTION\p\0
\{\1 o \0\} Do not use Manual Recovery unless specifically directed by your software documentation or a Customer Services Representative. To do so could result in the loss of data.
\p\p
\{\1 o \0\} Do not attempt to manually recover from a drive failure without understanding the circumstances of the failure. The correct procedure varies depending on the RAID Level of the affected logical unit and the number of drives in one drive group that have failed. Therefore, it is best to use Recovery Guru.
\p\p\1
Steps To Fail A Drive\0\p
1. From the top menu, select Options >> Manual Recovery >> Drives. \keyword "Manual Recovery -- Drives"
\p\p
2. Highlight the drives you want to fail.
\p\p\1
IMPORTANT\0\p
The Fail option is grayed out if you highlight any drive that has a drive status of Replaced or a logical unit status of Formatting or Reconstructing.
\p\p
3. Select Fail, then OK. An hourglass appears until the fail drive is completed, then the drive list shows updated status information.
\p\p
4. Use Recovery Guru to replace the drive.
\p\p\1
Related Topics\0\p
\{\3\goto "Manual Recovery For Drives" Manual Recovery For Drives\} \p
\{\3\goto "Highlighting Items In A List" Highlighting Items In A List\} \p
\keyword "how to fail drives"
\keyword "failing drives"

\topic "Reconstructing A Drive"
\0\p\1
Reconstructing A Drive\0
\p\p
You can only reconstruct drives with Failed or Replaced drive statuses in a RAID Level 1, 3, or 5 logical unit. Normally, drive \{\2\bring_popup "Reconstruction" reconstruction\} begins automatically once you replace a failed drive. However, if it does not begin automatically, you may need to use this option.
\p\p\4
CAUTION\0\p
\{\1 o \0\} Do not use Manual Recovery unless specifically directed by your software documentation or a Customer Services Representative. To do so could result in the loss of data.
\p\p
\{\1 o \0\} Do not attempt to manually reconstruct a drive without following the correct procedure given in your software documentation. In most cases, drive reconstruction begins automatically once you replace a failed drive. Therefore, it is best to use Recovery Guru.
\p\p\1
Steps To Start Drive Reconstruction\0\p
1. From the top menu, select Options >> Manual Recovery >> Drives. \keyword "Manual Recovery -- Drives"
\p\p
2. Highlight the drives you want to reconstruct.
\p\p\1
IMPORTANT\0\p
The Reconstruct option is grayed out if you highlight any drive that (1) contains a RAID Level 0 logical unit or (2) has a drive status other than Failed or Replaced.
\p\p
3. Select Reconstruct, then OK. The drive status changes to Replaced and the logical unit status changes to Reconstructing until reconstruction is complete. You can view reconstruction progress using the \keyword "Status Application" Status Application.
\p\p\1
Related Topics\0\p
\{\3\goto "Manual Recovery For Drives" Manual Recovery For Drives\} \p
\{\3\goto "Highlighting Items In A List" Highlighting Items In A List\} \p
\{\3\goto "What Is Reconstruction?" What Is Reconstruction?\} \p
\keyword "how to start drive reconstruction"
\keyword "starting reconstruction"
\keyword "reconstructing drives"
\keyword "drive reconstruction"

\topic "Reviving A Drive"
\0\p\1
Reviving A Drive\0
\p\p
You can only \keyword "reviving drives" revive drives with Failed drive statuses and the affected logical units cannot be formatting or reconstructing. Use this procedure only if you accidentally removed the \keyword "wrong drive" wrong drive and it was Optimal. Never use this procedure if the controller has marked the drive as failed.
\p\p\4
CAUTION\0\p
\{\1 o \0\} Do not use Manual Recovery unless specifically directed by your software documentation or a Customer Services Representative. To do so could result in the loss of data.
\p\p
\{\1 o \0\} Do not attempt to manually revive a drive without understanding the circumstances of the drive failure. Use this procedure only if you are certain than no data has been written to the drive. For example, you mistakenly removed or failed a drive with an Optimal status and have now returned the optimal drive to its correct location. Therefore, it is best to use Recovery Guru.
\p\p\1
Steps To Revive A Drive\0\p
1. From the top menu, select Options >> Manual Recovery >> Drives. \keyword "Manual Recovery -- Drives"
\p\p
2. Highlight the drives you want to revive.
\p\p\1
IMPORTANT\0\p
The Revive option is grayed out if you highlight any drive that has a drive status other than Failed or Warning.
\p\p
3. Select Revive, then OK.
\p\p
4. When the revive is finished, select OK. The drive list shows updated status information. You should manually check parity on the LUNs that the revived drives contain.
\p\p\1
Related Topics\0\p
\{\3\goto "Manual Recovery For Drives" Manual Recovery For Drives\} \p
\{\3\goto "Highlighting Items In A List" Highlighting Items In A List\} \p
\{\3\subtopic "When Can I Revive A Drive?" When Can I Revive A Drive?\} \p
\keyword "how to revive drives"

\topic "When Can I Revive A Drive?"
\0\p\1
When Can I Revive A Drive?\0
\p\p\4
CAUTION\0\p
Do NOT attempt to use the Revive option: \p
\{\1 o \0\} When the controller has marked the drive as Failed. (Instead, follow the instructions in Recovery Guru.)
\p\p
\{\1 o \0\} If the logical unit containing the drive is a RAID Level 0 and has another drive already Failed or in Warning.
\p\p\1
Using Revive\0\p
You may be able to recover from certain types of drive failures using the Revive Drive procedure:
\p\p
\{\1 o \0\} If the drive you removed was Optimal before removing it and the logical unit (LUN) containing the drive was Optimal. \p
For example, you removed an optimal drive from a functioning RAID 0 LUN, or you removed an optimal drive from an optimal RAID 1, 3, or 5 LUN.
\p\p
\{\1 o \0\} If you removed the \keyword "wrong drive" wrong drive. After you return the drive to its original location and use Revive, that drive returns to Optimal, but the original failed drive is still Failed. \p
For example, you removed an optimal drive from a \{\2\bring_popup "Degraded Mode" degraded\} RAID 1, 3, or 5 LUN.
\p\p
\{\1 o \0\} If you accidentally fail an Optimal drive in a functioning LUN or Degraded RAID 1, 3, or 5 LUN. \p
For example, you failed an optimal drive in a functioning RAID 0 LUN, or you failed an optimal drive from an optimal or degraded RAID 1, 3, or 5 LUN.
\p\p\1
Related Topics\0\p
\{\3\goto "Reviving A Drive" Reviving A Drive\} \p
\keyword "when to revive drives"
\keyword "reviving drives"
\keyword "when not to revive drives"

\topic "Possible Drive Statuses"
\0\p\1
Possible Drive Statuses\0
\p\p
In most cases, you should use Recovery Guru when you see a Failed, Offline, or Warning drive status. Any status other than Optimal means that the drive is not functioning normally. There are several possible \keyword "drive status" drive statuses:
\p\p\1
Failed\0: The drive has failed and is no longer functioning. Use Recovery Guru to replace the drive as soon as possible. \keyword "failed drive"
\p\p\1
Mismatch\0: The controller has sensed that the drive has some parameters different than expected, such as sector size, SCSI Channel, or ID. \keyword "mismatch drives"
\p\p\1
Offline\0: The drive has been placed Offline because data reconstruction failed and a read error occurred for one or more drives in the logical unit. The affected logical unit is \{\2\bring_popup "Dead Mode" Dead\}, and all the drives are probably either Failed or Offline. Use Recovery Guru to correct the problem.
\p\p\1
Optimal\0: The drive is functioning normally. \keyword "optimal"
\p\p\1
Replaced\0: The drive has been replaced, is being formatted, or is reconstructing. \keyword "replaced"
\p\p\1
Unresponsive\0: The controller is unable to communicate with the drive. You only see this status using List/Locate Drives in the Configuration Application, Module Profile >> Drives in all applications, and Options >> Manual Recovery >> Drives in this application. If you have an Unresponsive drive, you may want to determine which drive is affected. Then, if you want to manually fail it, use Options >> Manual Recovery >> Drives. \keyword "unresponsive"
\p\p\1
Spare\0: The drive is configured as a 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 \keyword "in use drive" In Use instead.) \keyword "spare drive"
\p\p\1
Spare-Stdby\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 \keyword "standby drive" instead.) \keyword "spare-stdby drive"
\p\p\1
Warning\0: The drive has been placed in Warning and could fail at any time. Applicable only if you have a RAID Module with a controller version earlier than the Series 3. \keyword "warning drive"
\p\p\1
Wrong Drive\0: You placed a new drive in the wrong drive location and the logical unit status is \{\2\bring_popup "Dead Mode" Dead\}. The drive you removed was 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. \keyword "wrong drive"
\p\p\1
Related Topics\0\p
\{\3\goto "About A RAID Module's Controllers" How Can I Tell How Many And What Kind Of Controllers A RAID Module Has?\} \p
\{\3\goto "Manual Recovery For Drives" Manual Recovery For Drives\} \p
\{\3\goto "What Is A Hot Spare?" What Is A Hot Spare?\} \p
\keyword "status, drives"

\topic "Manual Recovery For LUNs"
\0\p\1
Manual Recovery For Logical Units\0
\p\p\4
CAUTION\0\p
\{\1 o \0\} Do not use Manual Recovery unless specifically directed by your software documentation or a Customer Services Representative. To do so could result in the loss of data.
\p\p
\{\1 o \0\} Do not attempt to manually recover logical units without understanding the circumstances of the Degraded or Dead status. The correct procedure varies depending on the RAID Level of the affected logical unit and the number of drives in one drive group that have failed. Therefore, it is best to use Recovery Guru.
\p\p\1
IMPORTANT\0\p
\{\1 o \0\} If you have selected All RAID Modules, Options on the top menu is grayed out.
\p\p
\{\1 o \0\} In the case of a \{\2\bring_popup "Dead Mode" Dead\} LUN, you see all the LUNs for the affected \{\2\bring_popup "Configured Drive Group" 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\1
What Information Appears\0\p
Status information for all the \keyword "logical unit status" logical units (LUN) configured for the selected RAID Module displays. However, if there are no configured logical units on the module, this screen is blank. \keyword "options menu"
\p\p\1
Logical Units\0: Number that identifies the \{\2\bring_popup "Logical Unit" logical units\} contained on a particular drive group. \keyword "LUN Number"
\p\p\1
Drive Group\0: Number that identifies the drive groups configured for the selected RAID Module. \keyword "drive group"
\p\p\1
RAID Level\0: Indicates the \{\2\bring_popup "RAID Level" RAID Level\} of the LUN. \keyword "RAID Level"
\p\p\1
Logical Unit Status\0: Operating condition of the affected logical units. For an explanation of the possible statuses, select the "Possible Logical Unit Statuses" topic in the list below. \p
For Dead or Degraded LUNs, you should select Recovery Guru and follow the step-by-step instructions provided. \keyword "status, logical units"
\p\p\1
Options\0\p
Highlight one or more logical units with a Dead or Degraded status and select the recovery operation you wish to perform:
\p\p
\{\3\subtopic "Formatting A LUN" Formatting A Logical Unit\}
\p\p
\{\3\subtopic "Reviving A LUN" Reviving A Logical Unit\}
\p\p\1
Related Topics\0\p
\{\3\goto "Possible LUN Statuses" Possible Logical Unit Statuses\} \p
\{\3\goto "Highlighting Items In A List" Highlighting Items In A List\} \p
\{\3\goto "Using Manual Recovery" Using Manual Recovery\} \p
\keyword "formatting a logical unit"
\keyword "reviving logical units"
\keyword "Manual Recovery -- Logical Units"

\topic "Formatting A LUN"
\0\p\1
Formatting A Logical Unit\0
\p\p
Use this procedure to reformat a \{\2\bring_popup "Dead Mode" Dead\} logical unit after you have replaced all the failed drives in the drive group.
\p\p\4
CAUTION\0\p
\{\1 o \0\} Do not use Manual Recovery unless specifically directed by your software documentation or a Customer Services Representative. To do so could result in the loss of data.
\p\p
\{\1 o \0\} Do not attempt to manually format a logical unit (LUN) without first correcting any failures. The correct procedure varies depending on the RAID Level of the affected logical unit and the number of drives in one drive group that have failed. Therefore, it is best to use Recovery Guru.
\p\p\1
Steps To Format A Logical Unit\p\4
CAUTION\0\p
Selecting the Format option destroys all data on every logical unit (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 completes.
\p\p
1. From the top menu, select Options >> Manual Recovery >> Logical Units. \keyword "Manual Recovery -- Logical Units"
\p\p
2. Highlight the logical units/drive group you want to format. You see all the LUNs for a single drive group with Dead statuses on one line.
\p\p
3. Select Format, then OK. You return to the logical units list which shows updated logical unit status information. The LUNs have a status of Formatting, then Optimal when the format completes.
\p\p\1
Related Topics\0\p
\{\3\goto "Manual Recovery For LUNs" Manual Recovery For Logical Units\} \p
\{\3\goto "Possible LUN Statuses" Possible Logical Unit Statuses\} \p
\{\3\goto "Highlighting Items In A List" Highlighting Items In A List\} \p
\keyword "formatting a logical unit"
\keyword "how to format logical units"
\keyword "data loss"
\keyword "reformat"

\topic "Reviving A LUN"
\0\p\1
Reviving A Logical Unit\0
\p\p
Use this procedure only when \keyword "Recovery Guru" Recovery Guru instructs you to do so.
\p\p\4
CAUTION\0\p
\{\1 o \0\} Do not use Manual Recovery unless specifically directed by your software documentation or a Customer Services Representative. To do so could result in the loss of data.
\p\p
\{\1 o \0\} Do not attempt to manually revive a logical unit (LUN) without understanding the nature of the Dead status. Use this procedure only when recommended by Recovery Guru. Therefore, it is best to use Recovery Guru.
\p\p\1
IMPORTANT\0\p
In the case of a 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\1
Steps To Revive A Logical Unit\p\4
CAUTION\0\p
Selecting the Revive option may corrupt the data on every logical unit (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 completes.
\p\p
1. From the top menu, select Options >> Manual Recovery >> Logical Units. \keyword "Manual Recovery -- Logical Units"
\p\p
2. Highlight the logical units/drive group you want to revive.
\p\p
3. Select Revive, then OK. One of two information boxes appear: \p
\{\1 o \0\} Reviving the LUN was successful. Select OK. The logical unit list shows updated status information. You should manually check parity on the LUNs that the revived drive group contained.
\p\p
\{\1 o \0\} Notification that an error occurred while attempting to perform this procedure. Try the procedure again.
\p\p\1
Related Topics\0\p
\{\3\goto "Manual Recovery For LUNs" Manual Recovery For Logical Units\} \p
\{\3\goto "Possible LUN Statuses" Possible Logical Unit Statuses\} \p
\{\3\goto "Highlighting Items In A List" Highlighting Items In A List\} \p
\keyword "reviving logical units"
\keyword "how to revive logical units"
\keyword "parity check/repair"

\topic "Possible LUN Statuses"
\0\p\1
Possible Logical Unit Statuses\0
\p\p
In most cases, you should use Recovery Guru when you see a Degraded or Dead logical unit status.
\p\p\4
CAUTION\0\p
You should not rely ONLY on logical unit (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 affects the LUN status that is displayed. Therefore, any time you see a drive status other than Optimal or Replaced, select Recovery Guru and follow the step-by-step instructions provided.
\p\p
There are several possible \keyword "logical unit status" logical unit statuses:
\p\p\1
Dead\0: Two or more drives have failed in the same drive group, or one or more drives have failed in a RAID 0 drive group. The logical unit (LUN) is no longer functioning. Furthermore, all the LUNs in the \{\2\bring_popup "Configured Drive Group" drive group\} are Dead also. This is the most serious status a logical unit can have and you will lose data \keyword "data loss" unless the LUN status changed from Degraded because you replaced the wrong drive accidentally. \keyword "dead"
\p\p\1
Degraded\0: A single drive has failed on a \{\2\bring_popup "RAID Level" RAID Level\} 1, 3, or 5 logical unit 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. \keyword "degraded"
\p\p\1
NOTE\0: In a \{\2\bring_popup "RAID 1" RAID 1\} logical unit, more than one drive can fail and, as long as they are NOT in a mirrored pair, the logical unit remains in the degraded mode.
\p\p\1
Formatting\0: The logical unit is not available because it is being formatted. \keyword "formatting"
\p\p\1
Inaccessible\0: The logical unit 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
Locked\0: The logical unit is not available because an operation has obtained exclusive access to it (such as LUN creation). \keyword "locked status"
\p\p\1
Optimal\0: The logical unit is functioning normally. \keyword "optimal"
\p\p\1
Reconstructing\0: The controller is currently reconstructing one or more drives on the logical unit. \keyword "reconstructing"
\p\p\1
Related Topics\0\p
\{\3\goto "About A RAID Module's Controllers" How Can I Tell How Many And What Kind Of Controllers A RAID Module Has?\} \p
\{\3\goto "Do Hot Spares Affect LUN Statuses?" How Do Hot Spares Affect Logical Unit Statuses?\} \p
\{\3\goto "Manual Recovery For Drives" Manual Recovery For Drives\} \p
\{\3\goto "Manual Recovery For LUNs" Manual Recovery For Logical Units\} \p
\{\3\goto "Information In Manual Parity Check/Repair" What Information Appears In Manual Parity Check/Repair?\} \p
\keyword "status, logical units"

\topic "Manual Recovery For Controller Pairs"
\0\p\1
Manual Recovery For Controller Pairs
\p\p\4
CAUTION\0\p
\{\1 o \0\} Do not use Manual Recovery unless specifically directed by your software documentation or a Customer Services Representative. To do so could result in the loss of data.
\p\p
\{\1 o \0\} Do not attempt to manually recover controller failures without understanding the circumstances of the controller failure. Also, do not attempt to replace a controller without following the proper hardware documentation. Therefore, it is best to use Recovery Guru.
\p\p\1
IMPORTANT\0\p
\{\1 o \0\} This option is grayed out if All RAID Modules is selected or if the selected RAID Module has only one controller.
\p\p
\{\1 o \0\} You cannot perform an option on more than one controller at a time.
\p\p\1
What Information Appears\0\p
Status information for the controllers on the selected RAID Module displays. \keyword "options menu"
\p\p\1
Controller\0: Identifies one \{\2\bring_popup "Controller" controller\} per line for the selected RAID Module by an A or B designation and, where applicable, includes a system \{\2\bring_popup "Device Name" device name\}. The A and B are relative names to simplify identification of the controllers.
\p\p\1
Status\0: Operating condition of the controller. For an explanation of possible statuses, select the "Possible Controller Statuses" topic in the list below. \p
For Dead controllers, you should select Recovery Guru and follow the step-by-step instructions provided. \keyword "controller status"
\p\p\1
Options\0\p
Highlight one controller with a status other than Optimal and select the recovery operation you wish to perform:
\p\p
\{\3\subtopic "Placing A Controller Offline" Placing A Controller Offline\}
\p\p
\{\3\subtopic "Placing A Controller Online" Placing A Controller Online\}
\p\p\1
Related Topics\0\p
\{\3\goto "Possible Controller Statuses" Possible Controller Statuses\} \p
\{\3\goto "Using Manual Recovery" Using Manual Recovery\} \p
\keyword "Manual Recovery -- Controller Pairs"

\topic "Placing A Controller Offline"
\0\p\1
Placing A Controller Offline\0
\p\p
Use this option to stop a selected controller from accepting I/O requests. For example, to replace a controller, you want it first to be \{\2\bring_popup "Offline Controller Mode" offline\}. When you place a controller offline, its logical units are reassigned to the other \keyword "redundant controllers" redundant controller and it stops accepting any I/O. \keyword "logical unit assignment"
\p\p\4
CAUTION\0\p
\{\1 o \0\} Do not use Manual Recovery unless specifically directed by your software documentation or a Customer Services Representative. To do so could result in the loss of data.
\p\p
\{\1 o \0\} Do not attempt to manually place a controller offline without following the proper hardware and software documentation for replacing a controller. Therefore, it is best to use Recovery Guru.
\p\p\1
Steps To Place A Controller Offline \p
IMPORTANT\0\p
If the selected RAID Module has only one controller or one controller is already offline, this option is grayed out. You can place only one controller for a module offline at a time.
\p\p
1. From the top menu, select Options >> Manual Recovery >> Controller Pairs. \keyword "Manual Recovery -- Controller Pairs"
\p\p
2. Highlight the controller you want to place Offline.
\p\p
3. Select Place Offline, then OK.
\p\p\1
IMPORTANT\0\p
If you are using this option to replace the controller, wait one minute before inserting a new controller. \keyword "replacing controller"
\p\p
4. Select OK when the controller list updates the controller's status to Offline. You can also visually see the controller is Offline by checking the LED and fault lights on the controller. (See your hardware manual for the location and function of these LEDs.)
\p\p\1
Related Topics\0\p
\{\3\goto "Manual Recovery For Controller Pairs" Manual Recovery For Controller Pairs\} \p
\keyword "offline"
\keyword "controller, offline"

\topic "Placing A Controller Online"
\0\p\1
Placing A Controller Online\0
\p\p
Use this option to place a controller online; that is return it to ready-for-operating condition. For example, if you have placed a controller offline to replace it, you need to place it online before it can function for the selected RAID Module.
\p\p\4
CAUTION\0\p
\{\1 o \0\} Do not use Manual Recovery unless specifically directed by your software documentation or a Customer Services Representative. To do so could result in the loss of data.
\p\p
\{\1 o \0\} Do not attempt to manually place a controller online without following the proper hardware and software documentation for replacing a controller. Therefore, it is best to use Recovery Guru.
\p\p\1
Steps To Place A Controller Online\p\1
IMPORTANT\0\p
If the selected RAID Module has only one controller or there is NOT a controller with an Offline status, this option is grayed out. Also, there can be only one controller offline for the selected RAID Module.
\p\p
1. From the top menu, select Options >> Manual Recovery >> Controller Pairs. \keyword "Manual Recovery -- Controller Pairs"
\p\p
2. Highlight the controller with the Offline status to place it Online.
\p\p
3. Select Place Online, then OK.
\p\p
4. Select OK again when the controller list updates the controller's status to Optimal.
\p\p\1
Related Topics\0\p
\{\3\goto "Manual Recovery For Controller Pairs" Manual Recovery For Controller Pairs\} \p
\keyword "online"
\keyword "controller, online"

\topic "Possible Controller Statuses"
\0\p\1
Possible Controller Statuses\0
\p\p
In most cases, you should use Recovery Guru when you have a problem with any controller or see a data path failure. The possible controller statuses are:
\p\p\1
Optimal\0: The controller is functioning normally. \keyword "optimal"
\p\p\1
Dead\0: There is a problem on the data path (interface cable/terminator, network card, controller, or host adapter). Use Recovery Guru to diagnose and correct the problem as soon as possible. \keyword "dead"
\p\p\1
Offline\0: The controller is not receiving/accepting I/O data. Either it has been manually placed offline or the \{\2\bring_popup "RDAC Driver" driver\} for \{\2\bring_popup "Redundant Controller Pair" 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 and follow the step-by-step instructions provided. \keyword "offline"
\p\p\1
NOTE\0: You could also see (Inaccessible) with these statuses if the RAID Module has an \{\2\bring_popup "Independent Controller Configuration" independent controller\} configuration. \p
\p\p\1
Related Topics\0\p
\{\3\goto "Manual Recovery For Controller Pairs" Manual Recovery For Controller Pairs\} \p
\keyword "controller status"
\keyword "status, controllers"

\topic "Troubleshooting For Recovery"
\0\p\1
Troubleshooting/Common Questions
\p\p
NOTE:\0 For more general problems/questions that could apply in any application, consult the "Troubleshooting/Common Questions" topic on the Home Page.
\p\p\1
General\0\p
\{\3\subtopic "Do Hot Spares Affect LUN Statuses?" How Do Hot Spares Affect Logical Unit Statuses?\}
\p\p\1
Recovery Guru\0\p
\{\3\goto "How Can I Check For Component Failures?" How Can I Check For Component Failures?\}
\p\p
\{\3\goto "The ''Optimal (Health Check Not Done)'' Message Displays" What If Recovery Guru Displays The ''Optimal (Health Check Not Done)'' Message?\}
\p\p\1
Manual Parity Check/Repair\0\p
\{\3\subtopic "Stop Parity Check/Repair When Running" Can I Stop Parity Check/Repair When It Is Running?\}
\p\p
\{\3\subtopic "Another Way To Run Parity Check/Repair" Is There Another Way To Run Parity Check/Repair Besides Manually?\}
\p\p
\{\3\subtopic "Parity Check/Repair Takes A Long Time" Why Would Parity Check/Repair Take A Long Time?\}
\p\p\1
Related Topics\0\p
\{\3\goto "Recovery Application" Recovery Application\} \p
\{\3\goto "Troubleshooting For All Applications" Troubleshooting/Common Questions For All Applications\} \p

\topic "Do Hot Spares Affect LUN Statuses?"
\0\p\1
How Do Hot Spares Affect Logical Unit Statuses?\0
\p\p
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 logical unit until you replace it. This does not affect the drive statuses you see, but does affect the logical unit status that the software displays. Depending on how many hot spares you have configured, a \{\2\bring_popup "Logical Unit" logical unit\} could remain 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
The following logical unit (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 RAID 1, 3, or 5 logical unit and a hot spare takes over for it. The LUN continues to function normally. Checking the drive's status, 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 two things: \p
\{\1 o \0\} The hot spare has failed. The LUN now has a single failed drive and is functioning in the degraded mode. You can still access your data; however, you should replace the failed drives as soon as possible. Checking the drives' 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 the drives' 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 covering. The LUN is no longer functioning; furthermore, all the LUNs in the \{\2\bring_popup "Configured Drive Group" drive group\} are Dead also. This is the most serious status a logical unit can have and you will lose data. Checking the drives' statuses, you see Failed for each failed drive.
\p\p\1
Related Topics\0\p
\{\3\goto "How Many Hot Spares Can I Configure?" How Many Hot Spares Can I Configure?\} \p
\keyword "hot spare"
\keyword "logical unit status and hot spares"

\topic "Stop Parity Check/Repair When Running"
\0\p\1
Can I Stop Parity Check/Repair When It Is Running?\0
\p\p
Yes. When you see a histogram displaying the progress of \{\2\bring_popup "Parity Check/Repair" parity check/repair\}, you may select Cancel to stop the parity operation at any time. However, stopping this operation means that you have not completely checked or repaired the parity for the selected logical units.
\p
\keyword "parity check/repair"
\keyword "stopping parity check"

\topic "Another Way To Run Parity Check/Repair"
\0\p\1
Is There Another Way To Run Parity Check/Repair Besides Manually?\0
\p\p
Yes. In addition to running parity check/repair manually, you can also enable an Automatic Parity Check/Repair to run at a specific time every day. In the \keyword "Maintenance/Tuning Application" Maintenance/Tuning Application, from the top menu, select Options >> Auto Parity Settings to enable/disable this automatic parity option or to change the time of day you want it to run.
\p\p
The default settings are (1) Auto Parity enabled and (2) 2:00 am in the morning is the start time. \p
\keyword "parity, automatic operation"

\topic "Parity Check/Repair Takes A Long Time"
\0\p\1
Why Would Parity Check/Repair Take A Long Time?\0
\p\p
When you start the manual parity operation, you may notice some performance slow-down for other applications you are running. How long parity check/repair takes depends on your I/O load, and the number and size of the logical units you have selected. For example, parity check/repair for a 1 GB logical unit takes approximately two minutes. \p
\keyword "parity check/repair"
\keyword "time, manual parity"

\topic "Maintenance/Tuning Application"
\0\p\1
Maintenance/Tuning Application\0
\p\p
\{\3\subtopic "Maintenance/Tuning Task Summary" Task Summary\}
\p\p
\{\3\subtopic "Using LUN Reconstruction Rate" LUN Reconstruction Rate\}
\p\p
\{\3\subtopic "Using LUN Balancing" LUN Balancing\}
\p\p
\{\3\subtopic "Using Controller Mode" Controller Mode\}
\p\p
\{\3\subtopic "Using Caching Parameters" Caching Parameters\}
\p\p
\{\3\subtopic "Using Firmware Upgrade" Firmware Upgrade\}
\p\p
\{\3\subtopic "Using Auto Parity Settings" Using Options >> Auto Parity Settings\}
\p\p
\{\3\subtopic "Troubleshooting For Maintenance/Tuning" Troubleshooting/Common Questions\}
\p\p\1
Related Topics\0\p
\{\3\goto "Tasks For All Applications" Task Summary\} \p
\{\3\goto "Troubleshooting For All Applications" Troubleshooting/Common Questions For All Applications\} \p

\topic "Maintenance/Tuning Task Summary"
\0\p\1
MAINTENANCE/TUNING TASK SUMMARY\0
\p\p
\{\2\bring_popup "Auto Parity Tasks" Changing Automatic Parity Check/Repair Settings\}
\p\p
\{\2\bring_popup "LUN Reconstruction Rate Tasks" Changing The Reconstruction Rate\}
\p\p
\{\2\bring_popup "LUN Balancing Tasks" Balancing LUN Ownership Between Controllers\}
\p\p
\{\2\bring_popup "Change Active/Active Tasks" Changing To Active/Active Controllers\}
\p\p
\{\2\bring_popup "Swap Active/Passive Tasks" Swapping Active And Passive Controllers\}
\p\p
\{\2\bring_popup "Caching Parameters Tasks" Setting Caching Parameters\}
\p\p
\{\2\bring_popup "Firmware Upgrade Tasks" Upgrading Controller Firmware\}
\p\p\1
Related Topics\0\p
\{\3\goto "Maintenance/Tuning Application" Maintenance/Tuning Application\} \p
\{\3\goto "Tasks For All Applications" Task Summary For All Applications\}

\popup "Auto Parity Tasks"
\0\p
From the top menu, select Options >> Auto Parity Settings to enable or disable, or to change the time that automatic parity check/repair starts. \p
\keyword "changing parity settings"
\keyword "parity check/repair"

\popup "LUN Reconstruction Rate Tasks"
\0\p
Select a RAID Module, then LUN Reconstruction Rate to change the reconstruction rate for logical units whether or not they are undergoing reconstruction. \p
\keyword "changing reconstruction rate"
\keyword "reconstruction rate"

\popup "LUN Balancing Tasks"
\0\p
Select LUN Balancing to balance the logical unit ownership between active/active controller pairs for a single or all RAID Modules. \p
\keyword "balancing logical units"
\keyword "assigning logical units"

\popup "Change Active/Active Tasks"
\0\p
Select Controller Mode to make active/passive controller pairs active/active for a single or all RAID Modules. The selected modules cannot have only one controller or a controller pair that is already active/active. \p
\keyword "Controller Mode"
\keyword "changing controller modes"
\keyword "active/active controller pairs"

\popup "Swap Active/Passive Tasks"
\0\p
Select Controller Mode to switch the controller modes in active/passive controller pairs for a single or all RAID Modules. That is, change the active controller to ''passive,'' and the passive controller to ''active.'' The selected modules cannot have only one controller or an active/active controller pair. \p
\keyword "Controller Mode"
\keyword "swapping controller modes"
\keyword "active/passive controller pairs"

\popup "Caching Parameters Tasks"
\0\p
Select a RAID Module, then Caching Parameters to display the settings for three caching parameters, which you can enable or disable for logical units in the selected modules:
\p\p
write caching \p
write cache mirroring \p
cache without batteries
\p\p
NOTE: You can use the command line utility, raidutil, to change other advanced caching parameters. \p
\keyword "setting, caching parameters"

\popup "Firmware Upgrade Tasks"
\0\p
Select Firmware Upgrade to perform a controller firmware upgrade for a single or all RAID Modules, or to download a new NVSRAM file which comes from your Customer Services Representative. \p
\keyword "upgrading controller firmware"

\topic "Using LUN Reconstruction Rate"
\0\p\1
Using LUN Reconstruction Rate\0
\p\p\1
When To Use\0\p
Use to change the \{\2\bring_popup "Reconstruction Rate" reconstruction rate\} for the logical units on the selected RAID Module.
\p\p
See Related Topics at the bottom of this screen for additional information on this option.
\p\p\1
What Happens\0\p
Slider bars show the current reconstruction \{\2\bring_popup "Points" rate setting\} for each \{\2\bring_popup "Logical Unit" logical unit\} on the selected \{\2\bring_popup "RAID Module" RAID Module\}.
\p\p\1
IMPORTANT\0\p
\{\1 o \0\} If All RAID Modules is selected, this option is grayed out.
\p\p
\{\1 o \0\} You can change the \keyword "reconstruction rate" reconstruction rate even when logical units are undergoing reconstruction. To view the reconstruction progress for logical units currently reconstructing, use the \keyword "Status Application" Status Application.
\p\p\1
Related Topics\0\p
\{\3\goto "Change The Reconstruction Rate" Change The Reconstruction Rate\} \p
\{\3\goto "What Is Reconstruction?" What Is Reconstruction?\} \p
\{\3\goto "Why Are Some Options Grayed Out?" Why Are Some Options Grayed Out?\} \p
\{\3\goto "Why Did Reconstruction Take A Long Time?" Why Did Reconstruction Take A Long Time?\} \p
\keyword "LUN Reconstruction Rate"

\topic "Using LUN Balancing"
\0\p\1
Using LUN Balancing\0
\p\p\1
When To Use\0\p
Use to balance \{\2\bring_popup "Logical Unit" logical unit\} (LUN) ownership \keyword "LUN Assignment" between \{\2\bring_popup "Active/Active Controller Pair" active/active\} controller pairs in a selected RAID Module.
\p\p
See Related Topics at the bottom of this screen for additional information on this option.
\p\p\1
What Happens\0\p
The software displays the logical units configured for a particular \{\2\bring_popup "Configured Drive Group" drive group\} and shows which controller owns them. The display you see depends on whether you have selected All RAID Modules or a single RAID Module. 
\p\p\1
IMPORTANT\0\p
\{\1 o \0\} This option is grayed out if you select a RAID Module that has only one controller or an \{\2\bring_popup "Active/Passive Controller Pair" active/passive\} controller pair. You can, however, select All RAID Modules, then \keyword "LUN Balancing" LUN Balancing to quickly view the \{\2\bring_popup "LUN Assignment" LUN Assignments\} for all your RAID Modules at once, regardless of the number of controllers or their modes.
\p\p
\{\1 o \0\} If you do not have RDAC protection, you must stop I/Os to the RAID Module BEFORE changing LUN ownership. Otherwise, you could cause the operating system to hang. \keyword "mode, controller"
\p\p\1
Related Topics\0\p
\{\3\subtopic "View LUN Assignments For All RAID Modules" Can I Quickly View The LUN Assignments For All RAID Modules?\} \p
\{\3\subtopic "Balancing LUNs For All RAID Modules" Balancing LUNs Between Controllers For All RAID Modules\} \p
\{\3\subtopic "Balancing LUNs On One RAID Module" Balancing LUNs Between Controllers On One RAID Module\} \p
\{\3\goto "See ''No Controller'' As A Controller Mode" What If I See ''No Controller'' As A Controller Mode?\} \p
\{\3\subtopic "Information For All RAID Modules" What Information Appears In LUN Balancing For All RAID Modules?\} \p
\{\3\subtopic "Information For A Single RAID Module" What Information Appears In LUN Balancing For A Single RAID Module?\} \p
\{\3\goto "Why Are Some Options Grayed Out?" Why Are Some Options Grayed Out?\} \p
\keyword "balancing logical units"
\keyword "assigning logical units"

\topic "Information For All RAID Modules"
\0\p\1
What Information Appears In LUN Balancing For All RAID Modules?\0
\p\p
When you select All RAID Modules, then \keyword "LUN Balancing" LUN Balancing, you see the logical units configured for a particular module and the \{\2\bring_popup "Controller" controller\} to which they are assigned.
\p\p\1
RAID Module\0: Provides the number of a particular RAID Module.
\p\p\1
Controller/ Logical Units Owned\0: Lists logical unit numbers owned by each \keyword "controller, LUNs owned" controller. You see a number for every logical unit configured for a particular RAID Module.
\p\p\1
IMPORTANT\0\p
When no logical units (LUN) are assigned to one of the controllers, instead of a LUN, you see a reason why no LUNs are assigned to that controller: \p
\{\1 o \0\}\1 None\0 (Passive controller)
\p\p
\{\1 o \0\}\1 None\0 \{\2\bring_popup "No Controller" (No controller)\} -- usually means the module has only one controller
 \p\p
\{\1 o \0\}\1 Active\0 (No LUNs assigned)
\p\p\1
Options\0\p
\{\1 o \0\} You can balance LUNs for all RAID Modules with active/active controllers by highlighting one or more modules, then selecting Balance. The odd numbered drive groups are automatically assigned to one active controller and the even numbered drive groups are assigned to the other active controller.
\p\p
\{\1 o \0\} You can view the \keyword "LUN Assignment" LUN Assignments for All RAID Modules without making any changes by selecting Cancel when finished.
\p\p\1
IMPORTANT\0\p
You can only balance the LUN ownership for RAID Modules with \{\2\bring_popup "Active/Active Controller Pair" active/active\} controller pairs. You cannot perform any balancing on modules with only one controller or an \{\2\bring_popup "Active/Passive Controller Pair" active/passive\} controller pair.
\p\p\1
Related Topics\0\p
\{\3\goto "Highlighting Items In A List" Highlighting Items In A List\} \p
\{\3\goto "About A RAID Module's Controllers" How Can I Tell How Many And What Kind Of Controllers A RAID Module Has?\} \p
\{\3\goto "Using LUN Balancing" Using LUN Balancing\} \p
\{\3\goto "Information For A Single RAID Module" What Information Appears In LUN Balancing For A Single RAID Module?\} \p
\keyword "assigning logical units"
\keyword "no controller message"
\keyword "messages, no controller"

\topic "Information For A Single RAID Module"
\0\p\1
What Information Appears In LUN Balancing For A Single RAID Module?\0
\p\p
When you select a single RAID Module, then \keyword "LUN Balancing" LUN Balancing, you see two boxes, one for each controller. These boxes indicate which drive groups and logical units are assigned to which controller.
\p\p\1
Controller\0: Two boxes each identify one of the \keyword "controller name" controllers for the selected RAID Module by an A or B designation and, where applicable, a system \{\2\bring_popup "Device Name" device name\}. The A and B are relative names to simplify identification of the controllers. \keyword "device name"
\p\p\1
Drive Group\0: Provides the number of the \keyword "drive group number" \{\2\bring_popup "Configured Drive Group" drive group\} assigned to that controller.
\p\p\1
LUNs\0: Lists all the \keyword "LUN Assignment" logical units that belong to the particular drive group. \keyword "LUN Number"
\p\p\1
Group Capacity (MB)\0: Shows the total capacity (in megabytes) 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
IMPORTANT\0\p
This option is grayed out if you select a RAID Module that has one controller or an active/passive controller pair.
\p\p\1
Options\0\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 ownership 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 when you are finished.
\p\p\1
Related Topics\0\p
\{\3\goto "Highlighting Items In A List" Highlighting Items In A List\} \p
\{\3\goto "Using LUN Balancing" Using LUN Balancing\} \p
\{\3\goto "What Does The Device Name Mean?" What Does The Device Name Mean?\} \p
\{\3\goto "Information For All RAID Modules" What Information Appears In LUN Balancing For All RAID Modules?\} \p
\keyword "capacity, drive groups"
\keyword "drive group capacity"
\keyword "controller, LUNs owned"
\keyword "assigning logical units"

\topic "View LUN Assignments For All RAID Modules"
\0\p\1
Can I Quickly View The LUN Assignments For All RAID Modules?\0
\p\p
Yes. Select All RAID Modules, then \keyword "LUN Balancing" LUN Balancing to view the \{\2\bring_popup "LUN Assignment" LUN Assignments\} for all your modules. When finished viewing, select Cancel to close this option without changing any \keyword "LUN Assignment" LUN Assignments.
\p\p\1
Related Topics\0\p
\{\3\goto "Using LUN Balancing" Using LUN Balancing\} \p

\topic "Balancing LUNs For All RAID Modules"
\0\p\1
Balancing LUNs Between Controllers For All RAID Modules\0
\p\p
If you select ALL RAID Modules, then \keyword "LUN Balancing" LUN Balancing, you see all modules with their controllers displayed. You can highlight any modules with \{\2\bring_popup "Active/Active Controller Pair" active/active\} controller pairs, and the odd numbered drive groups are automatically assigned to one active controller while the even numbered drive groups are assigned to the other active controller.
\p\p\1
IMPORTANT\0\p
\{\1 o \0\} You cannot highlight any RAID Modules that do not have active/active controller pairs. Thus, you cannot balance LUNs for any module that has only one controller or an \{\2\bring_popup "Active/Passive Controller Pair" active/passive\} controller pair.
\p\p
\{\1 o \0\} If you do not have RDAC protection, you must stop I/Os to the RAID Module BEFORE changing LUN ownership. Otherwise, you could cause the operating system to hang. \keyword "mode, controller"
\p\p\1
Steps For Balancing LUNs From An All RAID Modules List\0\p
1. Select All RAID Modules, then LUN Balancing.
\p\p
2. Highlight each module you want to balance its LUNs.
\p\p
3. Select Balance. You see a confirmation box that the LUNs are about to be balanced for the selected RAID Modules.
\p\p
4. In the confirmation box, select OK to proceed. An hourglass displays until the balancing is complete. Then, the LUN Balancing list updates to show the new LUN Assignments for each module you highlighted.
\p\p\1
NOTE\0: If it appears that no balancing occurred, verify that the logical units for the selected module are NOT all in the same drive group. For example, assume that RAID Module 1 has only three LUNs, but they are all in the same drive group. Those LUNs always belong to the same controller because LUNs are assigned on a \{\2\bring_popup "Configured Drive Group" drive-group\} basis.
\p\p\1
Related Topics\0\p
\{\3\goto "Balancing LUNs On One RAID Module" Balancing LUNs Between Controllers On One RAID Module\} \p
\{\3\goto "Highlighting Items In A List" Highlighting Items In A List\} \p
\{\3\goto "About A RAID Module's Controllers" How Can I Tell How Many And What Kind Of Controllers A RAID Module Has?\} \p
\{\3\goto "Using LUN Balancing" Using LUN Balancing\} \p
\keyword "LUN Assignment"
\keyword "assigning logical units"
\keyword "how to change LUN Assignment"

\topic "Balancing LUNs On One RAID Module"
\0\p\1
Balancing LUNs Between Controllers On One RAID Module \0
\p\p
You may wish to manually balance the LUNs and their \{\2\bring_popup "Configured Drive Group" drive groups\} on a single RAID Module. You have this option for any RAID Module with an active/active controller pair.
\p\p\1
IMPORTANT\0\p
\{\1 o \0\} The \keyword "LUN Balancing" LUN Balancing option is grayed out if you select a RAID Module that does not have an \{\2\bring_popup "Active/Active Controller Pair" active/active\} controller pair. Thus, you cannot select LUN Balancing for a module that has only one controller or an \{\2\bring_popup "Active/Passive Controller Pair" active/passive\} controller pair.
\p\p
\{\1 o \0\} If you do not have RDAC protection, you must stop I/Os to the RAID Module BEFORE changing LUN ownership. Otherwise, you could cause the operating system to hang. \keyword "mode, controller"
\p\p
\{\1 o \0\} You can select Cancel at any time to close this option without changing any LUN Assignments.
\p\p
\{\1 o \0\} Using Move (<< / >>), you can move the drive group to the other controller; however, you do not actually balance the LUNs until you select Save.
\p\p\1
Steps For Balancing LUNs On One RAID Module\0\p
1. Select a RAID Module, then LUN Balancing.
\p\p
2. Highlight each drive group (LUN) you want to assign to the other controller in the pair. You can highlight items in both lists.
\p\p
3. Select Move (<< / >>). The selected drive group moves to the other controller.
\p\p
4. Select Save to actually balance the LUNs (save new settings). An hourglass displays until the save is complete.
\p\p\1
Related Topics\0\p
\{\3\goto "Balancing LUNs For All RAID Modules" Balancing LUNs Between Controllers For All RAID Modules\} \p
\{\3\goto "Highlighting Items In A List" Highlighting Items In A List\} \p
\{\3\goto "About A RAID Module's Controllers" How Can I Tell How Many And What Kind Of Controllers A RAID Module Has?\} \p
\{\3\goto "Using LUN Balancing" Using LUN Balancing\} \p
\keyword "LUN Assignment"
\keyword "assigning logical units"
\keyword "how to change LUN Assignment"

\topic "Using Controller Mode"
\0\p\1
Using Controller Mode\0
\p\p\1
When To Use\0\p
Use to change the controllers' modes for a selected RAID Module. You can change an \{\2\bring_popup "Active/Passive Controller Pair" active/passive\} controller pair to active/active or you can swap the active and passive controllers' modes (that is, change the active controller to "passive," and the passive controller to "active").
\p\p
See Related Topics at the bottom of this screen for additional information on this option.
\p\p\1
What Happens\0\p
Displays the controllers with their respective \{\2\bring_popup "Device Name" device name\} and mode for the selected RAID Module.
\p\p\1
IMPORTANT\0\p
\{\1 o \0\} This option is grayed out if you select a RAID Module that does not have an active/passive controller pair. Thus, you cannot select a module that has only one controller or an \{\2\bring_popup "Active/Active Controller Pair" active/active\} controller pair.
\p\p
\{\1 o \0\} You can, however, select All RAID Modules, then Controller Mode to quickly view the \{\2\bring_popup "Controller Mode" controller modes\} for all your RAID Modules.
\p\p
\{\1 o \0\} Changing controller pairs to active/active cannot be undone; that is, once changed, you cannot return the controller to an active/passive pair.
\p\p
\{\1 o \0\} If you do not have RDAC protection, you must stop I/Os to the RAID Module BEFORE changing a controller's mode. Otherwise, you could cause the operating system to hang. \keyword "mode, controller"
\p\p\1
Related Topics\0\p
\{\3\subtopic "View Controller Modes For All RAID Modules" Can I Quickly View The Controller Modes For All RAID Modules?\} \p
\{\3\subtopic "Changing To Active/Active Controller Pairs" Changing To Active/Active Controller Pairs\} \p
\{\3\goto "Highlighting Items In A List" Highlighting Items In A List\} \p
\{\3\goto "About A RAID Module's Controllers" How Can I Tell How Many And What Kind Of Controllers A RAID Module Has?\} \p
\{\3\subtopic "Swapping Active/Passive Controller Pairs" Swapping Active/Passive Controller Pairs\} \p
\{\3\goto "See ''No Controller'' As A Controller Mode" What If I See ''No Controller'' As A Controller Mode?\} \p
\{\3\subtopic "Information In Controller Mode" What Information Appears In Controller Mode?\} \p
\{\3\goto "Why Are Some Options Grayed Out?" Why Are Some Options Grayed Out?\} \p
\keyword "device name"
\keyword "Controller Mode"

\topic "Information In Controller Mode"
\0\p\1
What Information Appears In Controller Mode?\0
\p\p
When you select \keyword "Controller Mode" Controller Mode, you see the current modes of every controller for the selected RAID Module.
\p\p\1
RAID Module\0: Provides the number of a particular \keyword "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 "Device Name" device name\}. The A is a relative name to simplify identification of the controllers. \keyword "device name"
\p\p\1
Controller B\0: Identifies the \keyword "mode, controller" mode for the second controller of the selected RAID Module. The column heading includes, where applicable, a system device name. The B is a relative name to simplify identification of the controllers.
\p\p\1
Mode\0: Indicates the operating state of the controller. 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" No Controller\}. You could also see (Inaccessible) with these statuses if the RAID Module has an \{\2\bring_popup "Independent Controller Configuration" independent controller\} configuration.
\p\p\1
Options\0\p
\{\1 o \0\} You can select Change To Active/Active to make \{\2\bring_popup "Active/Passive Controller Pair" active/passive\} controller pairs active/active.
\p\p
\{\1 o \0\} You can select Swap Active/Passive to switch the controller modes in an active/passive pair (that is, change the active controller to "passive," and the passive controller to "active").
\p\p\1
IMPORTANT\0\p
\{\1 o \0\} The Change To Active/Active and Swap Active/Passive options are grayed out if you select a module that has only one controller or an \{\2\bring_popup "Active/Active Controller Pair" active/active\} controller pair. For example, if you select All RAID Modules, then Controller Mode, and then highlight a module that does not have an active/passive controller pair, you cannot select these options.
\p\p
\{\1 o \0\} Changing from active/passive 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 utility rdacutil.
\p\p\1
Related Topics\0\p
\{\3\goto "Using Controller Mode" Using Controller Mode\} \p
\{\3\goto "What Does The Device Name Mean?" What Does The Device Name Mean?\} \p
\{\3\goto "See ''No Controller'' As A Controller Mode" What If I See ''No Controller'' As A Controller Mode?\} \p

\topic "View Controller Modes For All RAID Modules"
\0\p\1
Can I Quickly View The Controller Mode For All RAID Modules?\0
\p\p
Yes. Select All RAID Modules, then \keyword "Controller Mode" Controller Mode. When you are finished viewing the \{\2\bring_popup "Controller Mode" controller modes\}, select Cancel to exit this option without making any changes.
\p\p\1
Related Topics\0\p
\{\3\goto "Using Controller Mode" Using Controller Mode\} \p
\{\3\goto "See ''No Controller'' As A Controller Mode" What If I See ''No Controller'' As A Controller Mode?\} \p

\topic "Changing To Active/Active Controller Pairs"
\0\p\1
Changing To Active/Active Controller Pairs\0
\p\p
Changing an active/passive controller pair to \{\2\bring_popup "Active/Active Controller Pair" active/active\} improves your I/O performance. Note however, that you cannot change an active/active controller pair back to an active/passive pair.
\p\p\1
IMPORTANT\0\p
\{\1 o \0\} The Change To Active/Active option is grayed out for any RAID Module you select that has only one controller or an active/active controller pair.
\p\p
\{\1 o \0\} If you do not have RDAC protection, you must stop I/Os to the RAID Module BEFORE changing a controller's mode. Otherwise, you could cause the operating system to hang. \keyword "mode, controller"
\p\p\1
Steps For Changing To Active/Active Controller Pairs\0\p
1. Select one RAID Module or All RAID Modules, then Controller Mode.
\p\p
2. Highlight the active/passive controller pair you want to make active/active.
\p\p
3. Select Change To Active/Active. You see a confirmation box that the controller mode is about to change for the selected RAID Module. The option to automatically balance the LUNs across the newly active/active controllers is selected by default.
\p\p
4. In the confirmation box, \p
\{\1 o \0\} Leave the automatic LUN balancing option selected if you want the LUNs for the selected module to automatically \{\2\bring_popup "LUN Assignment" balance\} (the odd numbered drive groups are assigned to one active controller and the even numbered drive groups are assigned to the other active controller). For maximum performance benefits, each controller must own some of the LUNs. \keyword "LUN Assignment"
\p\p
\{\1 o \0\} Unselect the automatic LUN balancing option if you do not want the LUN assignment changed. Thus, the currently active controller continues to own all of the LUNs. You can assign some of the LUNs to the other active controller later using LUN Balancing.
\p\p\4
CAUTION\0\p
When you select OK in Step 5,\1 THIS CHANGE CANNOT BE UNDONE through this interface\0 (that is, once changed to active/active, you cannot change back to active/passive EXCEPT by using the command line utility rdacutil).
\p\p
5. Select OK. An hourglass displays until the change is complete. \p
\{\1 o \0\} If successful, the list updates to show the new controller mode of the selected RAID Module.
\p\p
\{\1 o \0\} You receive notification if a problem occurs.
\p\p\1
Related Topics\0\p
\{\3\goto "Balancing LUNs On One RAID Module" Balancing LUNs Between Controllers On One RAID Module\} \p
\{\3\goto "Highlighting Items In A List" Highlighting Items In A List\} \p
\{\3\goto "Using Controller Mode" Using Controller Mode\} \p
\keyword "changing to active/active"
\keyword "active/active controller pairs"
\keyword "how to change to active/active"

\topic "Swapping Active/Passive Controller Pairs"
\0\p\1
Swapping Active/Passive Controller Pairs\0
\p\p
You may want to swap an \{\2\bring_popup "Active/Passive Controller Pair" active/passive\} controller pair: \p
\{\1 o \0\} When a Recovery procedure requires it.
\p\p
\{\1 o \0\} When 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
IMPORTANT\0\p
\{\1 o \0\} 
The Swap Active/Passive option is grayed out if you select any RAID Module that has only one controller or an active/active controller pair.
\p\p
\{\1 o \0\} If you do not have RDAC protection, you must stop I/Os to the RAID Module BEFORE changing a controller's mode. Otherwise, you could cause the operating system to hang. \keyword "mode, controller"
\p\p\1
Steps For Swapping Active/Passive Controller Modes\0\p
1. Select one RAID Module or All RAID Modules, then Controller Mode.
\p\p
2. Highlight the active/passive controller pair you want to swap.
\p\p
3. Select Swap Active/Passive. You see one of two possible confirmation boxes. \p
\{\1 o \0\} The selected RAID Module is receiving I/O. You might see this message if the \{\2\bring_popup "RDAC Driver" driver\} for redundant controller support is not installed. Select OK to return to the Controller Mode screen without performing the swap procedure. Then, STOP all I/O to this module before repeating these Steps.
\p\p
\{\1 o \0\} The controller mode is about to change for the selected RAID Module. Select OK to proceed. An hourglass displays until the change is complete. Then, the list updates to show the swapped controller modes for the selected RAID Module.
\p\p\1
Related Topics\0\p
\{\3\goto "Highlighting Items In A List" Highlighting Items In A List\} \p
\{\3\goto "Using Controller Mode" Using Controller Mode\} \p
\keyword "swapping controller modes"
\keyword "active/passive controller pairs"
\keyword "how to change active/passive controller pairs"

\topic "Using Caching Parameters"
\0\p\1
Using Caching Parameters\0
\p\p\1
When To Use\0\p
Use to view or modify three caching parameters for a selected RAID Module: \{\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\}.
\p\p
See Related Topics at the bottom of this screen for additional information on this option.
\p\p\1
What Happens\0\p
The software displays the settings for these caching parameters.
\p\p\1
IMPORTANT\0\p
\{\1 o \0\} If All RAID Modules is selected, this option is grayed out.
\p\p
\{\1 o \0\} If both controllers in the RAID Module do NOT have the same or the minimum required \{\2\bring_popup "Processor Memory" processor\} and \{\2\bring_popup "Cache Memory" cache\} size, this option is grayed out.
\p\p
\{\1 o \0\} If you select a RAID Module with only one controller, 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. Use Module Profile >> Controllers to determine if both controllers in the pair have the same size cache BEFORE enabling this parameter.
\p\p
\{\1 o \0\} Any changes you make do NOT take effect until you select Save.
\p\p
\{\1 o \0\} You can use the command line utility, raidutil, to change other advanced caching parameters.
\p\p
\{\1 o \0\} Module Profile >> LUNs indicates whether or not the caching parameters are enabled (write cache, write cache mirroring, and cache without batteries). Also, 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\p
\{\3\subtopic "Enabling And Disabling Caching Parameters" Enabling And Disabling Caching Parameters\} \p
\{\3\goto "About A RAID Module's Controllers" How Can I Tell How Many And What Kind Of Controllers A RAID Module Has?\} \p
\{\3\goto "Determining Controller's Memory Size" How Can I Tell What Size Memory The Controllers In A RAID Module Have?\} \p
\{\3\subtopic "Information In Caching Parameters" What Information Appears In Caching Parameters?\} \p
\{\3\goto "What Is Cache Memory?" What Is Cache Memory?\} \p
\{\3\goto "Why Are Some Options Grayed Out?" Why Are Some Options Grayed Out?\} \p
\keyword "Caching Parameters"
\keyword "parameters, caching"

\topic "Information In Caching Parameters"
\0\p\1
What Information Appears In Caching Parameters?\0
\p\p
When you select a specific RAID Module, then \keyword "Caching Parameters" 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\} \keyword "LUN Number" (LUN).
\p\p\1
Write Caching\0: Check box that allows you to enable/disable the \{\2\bring_popup "Write Caching" write caching\} option 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\} option for a particular LUN. This option is grayed out if the selected RAID Module does not have \{\2\bring_popup "Redundant Controller Pair" redundant controllers\}.
\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 >> Controllers to determine if both controllers in the pair have the same size 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\} option 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 discharged completely or not fully charged. Normally, write caching is temporarily turned off if no batteries are detected or until the batteries are charged. However, enabling this 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
IMPORTANT\0\p
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\p
\{\3\goto "Enabling And Disabling Caching Parameters" Enabling And Disabling Caching Parameters\} \p
\{\3\goto "About A RAID Module's Controllers" How Can I Tell How Many And What Kind Of Controllers A RAID Module Has?\} \p
\{\3\goto "Using Caching Parameters" Using Caching Parameters\} \p
\keyword "write caching"
\keyword "write cache mirroring"
\keyword "cache without batteries"

\topic "Enabling And Disabling Caching Parameters"
\0\p\1
Enabling And Disabling Caching Parameters\0
\p\p
Depending on which caching parameters you may enable/disable, another parameter could also become enabled/disabled because of the interdependencies among them.
\p\p\1
IMPORTANT\0\p
Any changes you make do NOT take effect until you select Save.
\p\p\1
Enabling Caching Parameters\0\p
\{\1 o \0\}\1 Write caching\0 -- selecting automatically enables write cache mirroring too, 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 o \0\}\1 Write cache mirroring\0 -- selecting automatically enables write caching too. 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 cache size (use Module Profile >> Controllers to determine the controllers' cache size).
\p\p
\{\1 o \0\}\1 Cache without batteries\0 -- selecting automatically enables write caching too.
\p\p\4
CAUTION\0\p
Selecting Cache Without Batteries allows write caching to continue even without battery backup or if the batteries are discharged completely or not fully charged. Normally, write caching is temporarily turned off if no batteries are detected or until the batteries are charged. However, enabling this 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 Caching Parameters\0\p
\{\1 o \0\}\1 Write caching\0 -- deselecting disables both write cache mirroring and cache without batteries.
\p\p
\{\1 o \0\}\1 Write cache mirroring\0 -- deselecting does not affect the other two parameter's settings.
\p\p
\{\1 o \0\}\1 Cache without batteries\0 -- deselecting does not affect the other two parameter's settings.
\p\p\1
Steps To Save Caching Parameters Settings\0\p
1. Select one RAID Module, then Caching Parameters.
\p\p\1
IMPORTANT\0\p
This option is grayed out if you select All RAID Modules, or if both controllers in the RAID Module do NOT have the same or the minimum required \{\2\bring_popup "Processor Memory" processor\} and \{\2\bring_popup "Cache Memory" cache\} size. 
\p\p
2. Click in the check boxes to enable/disable parameters as desired for any or all logical units on the selected RAID Module. Remember the interdependencies the settings may share.
\p\p
3. Select Save to change the parameters as you set them in Step 2. An hourglass appears until the settings change.
\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\p
\{\3\goto "About A RAID Module's Controllers" How Can I Tell How Many And What Kind Of Controllers A RAID Module Has?\} \p
\{\3\goto "Using Caching Parameters" Using Caching Parameters\} \p
\{\3\goto "Information In Caching Parameters" What Information Appears In Caching Parameters?\} \p
\keyword "turning off caching"
\keyword "Caching Parameters"
\keyword "caching interdependencies"
\keyword "saving caching parameters"
\keyword "setting, caching parameters"

\topic "Using Firmware Upgrade"
\0\p\1
Using Firmware Upgrade\0
\p\p\1
When To Use\0\p
Use to upgrade \keyword "controller firmware" controller \{\2\bring_popup "Firmware" firmware\} for one or all RAID Modules, or to download a new \{\2\bring_popup "NVSRAM File" NVSRAM file\} which comes from your Customer Services Representative.
\p\p
See Related Topics at the bottom of this screen for additional information on this option.
\p\p\1
What Happens\0\p
Allows you to choose whether you want to perform upgrades \{\2\bring_popup "Online Firmware Upgrade" online\} or \{\2\bring_popup "Offline Firmware Upgrade" offline\}, then presents a series of information/selection windows to perform the upgrade procedure.
\p\p\4
CAUTION\0\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). If you do not, certain features of this software and in the controller may not work. Also, if you have RAID Modules with a pair of redundant controllers, we recommend 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\1
IMPORTANT\0\p
\{\1 o \0\} Once you select OK at the "Firmware is about to start" prompt, you cannot exit the Maintenance/Tuning Application until the upgrade process is complete.
\p\p
\{\1 o \0\} The Online option is grayed out if you select a RAID Module that does NOT have two functioning Series 3 controllers and the \{\2\bring_popup "RDAC Driver" driver\} installed for \{\2\bring_popup "Redundant Controller Pair" redundant controller\} support. For example, this 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 logical units in the module are Optimal.
\p\p
\{\1 o \0\} The Offline option does not work unless you have stopped I/O to the selected RAID Module.
\p\p
\{\1 o \0\} Controller firmware is different from drive firmware. Only use this option to upgrade controller firmware. If you need to upgrade drive firmware, call your Customer Services Representative.
\p\p\1
Related Topics\0\p
\{\3\goto "Upgrading Firmware To Only One Controller" Can I Upgrade Controller Firmware To Only One Controller?\} \p
\{\3\subtopic "Downloading New Firmware Files" Downloading New Controller Firmware Files\} \p
\{\3\subtopic "Downloading New NVSRAM Files" Downloading New NVSRAM Files\} \p
\{\3\goto "Firmware Version For A RAID Module's Controllers" How Can I Find Out What Firmware Version A RAID Module's Controllers Have?\} \p
\{\3\goto "About A RAID Module's Controllers" How Can I Tell How Many And What Kind Of Controllers A RAID Module Has?\} \p
\{\3\subtopic "What Can Be Done During Firmware Upgrade?" What Can I Do While The Upgrade Is Taking Place?\} \p
\{\3\goto "Firmware Upgrade Takes A Long Time" Why Would Upgrading Firmware Take A Long Time?\} \p
\keyword "Firmware Upgrade"
\keyword "NVSRAM files"
\keyword "online"
\keyword "offline"

\topic "What Can Be Done During Firmware Upgrade?"
\0\p\1
What Can I Do While The Upgrade Is Taking Place?\0
\p\p
Nothing else besides monitor its progress. You have several opportunities to select Cancel and exit \keyword "Firmware Upgrade" Firmware Upgrade without performing any procedure. However, once you select OK at the "Firmware is about to start" prompt, you cannot exit the Maintenance/Tuning Application until the upgrade process is complete.
\p\p\1
Related Topics\0\p
\{\3\goto "Downloading New Firmware Files" Downloading New Controller Firmware Files\} \p

\topic "Downloading New Firmware Files"
\0\p\1
Downloading New Controller Firmware Files
\p\p\1
Options\0\p
\{\1 o \0\} You can choose to upgrade firmware on a single RAID Module or on all RAID Modules at once.
\p\p
\{\1 o \0\} You can choose to \keyword "performing an upgrade" perform the upgrade\{\2\bring_popup "Online Firmware Upgrade" online\} or \{\2\bring_popup "Offline Firmware Upgrade" offline\}.
\p\p\4
CAUTION\0\p
\{\1 o \0\} In most cases, you will have to download a new \{\2\bring_popup "NVSRAM File" 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). If you do not, certain features of this software and in the controller may not work. Select the "Downloading New NVSRAM Files" topic in the list below for the procedure to follow.
\p\p
\{\1 o \0\} You must stop all I/O to the selected RAID Modules before selecting the offline procedure. If the selected RAID Modules are receiving I/O, you cannot perform the offline upgrade until you stop the I/O. 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
IMPORTANT\0\p
\{\1 o \0\} The Online upgrade option is grayed out if you do not have two functioning Series 3 controllers and the \{\2\bring_popup "RDAC Driver" driver\} installed for redundant controller support. For example, this 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 logical units in the module are Optimal.
\p\p
\{\1 o \0\} Before you begin the upgrade procedure, make sure you have copied the \keyword "files, firmware upgrade" firmware files and the \keyword "fwcompat.def" fwcompat.def file to the correct subdirectory in the \{\2\bring_popup "Installation Directory" installation directory\} on your host system (see the "Installation And Support Guide" specific to your operating system for installation directory information). Without fwcompat.def, 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
Steps For Performing A Firmware Upgrade\0\p
1. Select the RAID Module you want to upgrade controller firmware on, then Firmware Upgrade. You could also choose All RAID Modules. \keyword "how to upgrade firmware"
\p\p
2. Read the "Before You Begin" Important notes, then select OK. A screen displays for you to select the online or offline procedure.
\p\p\1
IMPORTANT\0\p
In a UNIX-system environment, if you are selecting the Offline upgrade in Step 3, you MUST first unmount any filesystems contained on the selected module's logical units so that the software has exclusive access to all the LUNs.
\p\p
3. Select either: \p
\{\1 o \0\} Online to upgrade firmware while the selected RAID Module receives I/O. \keyword "online"
\p\p
\{\1 o \0\} Offline to upgrade firmware when the selected RAID Module is not receiving I/O. \keyword "offline"
\p\p
After selecting Online or Offline, you see a confirmation box, "Verifying the controller state." The selected RAID Modules are being checked for restrictions based on the type of firmware upgrade you selected. If no restrictions are found, you see what the current firmware version is for the selected RAID Module. Also, you see a list of version levels that are compatible. These files are found by using the \{\2\bring_popup "fwcompat.def" fwcompat.def\} file to check the selected directory.
\p\p
4. Select the controllers you want to download the firmware files to. You must download to both controllers if you selected the Online method. If you are performing an Offline download and you selected only one RAID Module in Step 1 that has a redundant controller pair, select one or both controllers. We strongly recommend selecting both controllers to ensure that they have compatible versions of firmware.
\p\p
5. Highlight the version line you want to download for the upgrade process. The path box is updated to show the filenames associated with the version you selected.
\p\p\1
NOTE\0: Fibre channel firmware code, when available, is part of the firmware upgrade package and displays in this Compatible Files/Versions screen (in the Fibre Channel Level (FC) column). When you select a package with FC code for downloading, it also downloads along with the appware and bootware files. However, the fibre channel code is ignored unless the module's controllers are fibre channel ready.
\p\p
6. Select OK if the correct version level is highlighted. Either you receive notification if some problem occurs, or you have a final confirmation that the upgrade process is about to begin.
\p\p\1
IMPORTANT\0\p
Once you select OK in Step 7, do NOT select any other options or exit the Maintenance/Tuning Application until the upgrade process is complete. You can, however, monitor the upgrade's progress.
\p\p
7. Select OK to begin the upgrade procedure.
\p\p
8. Follow the \keyword "progress, firmware upgrade" firmware upgrade progress. \p
A histogram for the selected RAID Module indicates the progress of downloading for each file. This graphic shows the amount of progress as a percentage and starts over at 0% for each file if you have more than one. 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. If you selected All RAID Modules, the module number updates as each module begins its download process.
\p\p
9. When the upgrade is finished, you see a confirmation box indicating whether or not the upgrade was successful. Select OK.
\p\p\1
IMPORTANT\0\p
If you selected 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.
\p\p\1
Related Topics\0\p
\{\3\subtopic "Following Firmware Upgrade Progress" Can I Follow The Progress For A Firmware Upgrade?\} \p
\{\3\goto "Downloading New NVSRAM Files" Downloading New NVSRAM Files\} \p
\{\3\goto "About A RAID Module's Controllers" How Can I Tell How Many And What Kind Of Controllers A RAID Module Has?\} \p
\{\3\goto "Was The Firmware Upgrade Successful?" How Will I Know If The Upgrade Was Successful?\} \p
\{\3\subtopic "Selecting Firmware Files For Downloading" Selecting Firmware Files For Downloading\} \p
\{\3\goto "What Can Be Done During Firmware Upgrade?" What Can I Do While The Upgrade Is Taking Place?\} \p
\{\3\goto "Files Needed To Perform A Firmware Upgrade" What Files Do I Need To Perform A Firmware Upgrade?\} \p
\{\3\goto "No Firmware Files/Versions Are Displayed" What If I Don't See Any Firmware Files/Versions Displayed?\} \p
\{\3\subtopic "The ''Firmware File Error'' Message Displays" What If I See The ''Firmware File Error'' Message?\} \p
\{\3\goto "Restrictions Might Prevent A Firmware Upgrade" What Restrictions Might Prevent A Firmware Upgrade?\} \p
\{\3\goto "Why Do I See Fibre Channel Firmware Code?" Why Do I See Fibre Channel Firmware Code In The Compatible Files/Versions List?\} \p
\{\3\goto "Using Firmware Upgrade" Using Firmware Upgrade\} \p

\popup "fwcompat.def" 
\0\p
Before you begin a firmware upgrade, make sure you have copied the firmware files to the correct subdirectory in the \{\2\bring_popup "Installation Directory" installation directory\} on your host system, including the fwcompat.def file (see the "Installation And Support Guide" specific to your operating system for installation directory information). This file allows the software to compare the firmware files for compatibility during the upgrade process, and to provide you with a list of version levels that are compatible to select for downloading.
\p\p
Without fwcompat.def, the software is unable to check the firmware files for compatibility. Although you can still enter firmware filenames, you do NOT have the protection that this compatibility check provides. \p

\topic "Following Firmware Upgrade Progress"
\0\p\1
Can I Follow The Progress For A Firmware Upgrade?\0
\p\p
Yes. The progress display occurs for both \{\2\bring_popup "NVSRAM File" NVSRAM file\} downloads and \{\2\bring_popup "Firmware" controller firmware\} upgrades. Once you select OK at the "Firmware is about to start" prompt, a histogram for the selected RAID Module indicates the \keyword "progress, firmware upgrade" progress of downloading for each file. This graphic shows the amount of progress as a percentage and starts over at 0% for each file if you have more than one. 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. If you selected All RAID Modules, the module number updates as each module begins its download process.
\p\p
Once you select OK at this prompt, you cannot exit the Maintenance/Tuning Application until the upgrade process is complete. After the upgrade is finished, you can confirm that it was successful by viewing the firmware version information in Module Profile's Controller details. Select the upgraded RAID Module, then \keyword "Module Profile" Module Profile >> Controllers under Detailed Information.
\p\p\1
Related Topics\0\p
\{\3\goto "Downloading New Firmware Files" Downloading New Controller Firmware Files\} \p
\{\3\goto "Firmware Version For A RAID Module's Controllers" How Can I Find Out What Firmware Version A RAID Module's Controllers Have?\} \p
\{\3\goto "Using Module Profile" Using Module Profile\} \p
\keyword "version, firmware"
\keyword "confirm firmware upgrade"

\topic "Selecting Firmware Files For Downloading"
\0\p\1
Selecting Firmware Files For Downloading\0
\p\p
When you select a RAID Module, then \keyword "Firmware Upgrade" Firmware Upgrade, and either Online or Offline, the software checks for restrictions based on the type of firmware upgrade you selected. If no restrictions are found, a display shows you the current \keyword "version, firmware" firmware version for the selected RAID Module and a list of version levels that are compatible.
\p\p\1
Current Firmware Versions \p
RAID Module\0: Provides the number of a particular \keyword "RAID Module" RAID Module.
\p\p\1
Controller\0: Identifies the controllers in the selected RAID Module by an A or B designation and, where applicable, includes a system \{\2\bring_popup "Device Name" device name\}. The A and B are relative names to simplify identification of the controllers. \keyword "device name"
\p\p\1
Firmware Level\0: Number indicating the release of controller firmware. \keyword "firmware level"
\p\p\1
Boot Level\0: Number indicating the controller type and release version of controller \{\2\bring_popup "Bootware" bootware\}. \keyword "bootware level"
\p\p\1
Fibre Channel Level\0: Number indicating the controller type and release version of driver for fibre channel firmware. \keyword "fibre channel level"
\p\p\1
Compatible Files/Versions\0\p
The software displays compatible firmware versions by using the \keyword "fwcompat.def" 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 updates to list the filenames for the version you selected.
\p\p\1
Path\0: The default is the subdirectory in the \{\2\bring_popup "Installation Directory" 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\0\p
\{\3\goto "Downloading New Firmware Files" Downloading New Controller Firmware Files\} \p
\{\3\goto "What Does The Device Name Mean?" What Does The Device Name Mean?\} \p
\{\3\goto "Why Do I See Fibre Channel Firmware Code?" Why Do I See Fibre Channel Firmware Code In The Compatible Files/Versions List?\} \p
\keyword "files, firmware upgrade"
\keyword "defaults"

\topic "The ''Firmware File Error'' Message Displays"
\0\p\1
What If I See The ''Firmware File Error" Message?\0
\p\p
You might see a "Firmware File Error" message after selecting files for downloading the firmware. This message means that the selected files are not firmware files or are corrupted.
\p\p
Perform one of the following steps: \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 "Downloading New Firmware Files" Downloading New Controller Firmware Files\} \p
\keyword "Firmware Upgrade"
\keyword "messages, firmware"

\topic "Downloading New NVSRAM Files"
\0\p\1
Downloading New NVSRAM Files\0
\p\p\1
Options\0\p
\{\1 o \0\} You can choose to download a new \{\2\bring_popup "NVSRAM File" NVSRAM file\} to a single RAID Module or on all RAID Modules at once.
\p\p
\{\1 o \0\} You can choose to perform the download \{\2\bring_popup "Online Firmware Upgrade" online\} or \{\2\bring_popup "Offline Firmware Upgrade" offline\}. 
\p\p\4
CAUTION\0\p
\{\1 o \0\} In most cases, you 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). If you do not, certain features of this software and in the controller may not work.
\p\p 
\{\1 o \0\} You must stop all I/O to the selected RAID Modules before selecting the offline procedure. If the selected RAID Modules are receiving I/O, you cannot perform the Offline upgrade until you stop the I/O. If several of your modules have only one controller, you may want to download an NVSRAM file on only one RAID Module at a time so that you do not have to stop all I/O.
\p\p\1
IMPORTANT\0\p
\{\1 o \0\} The Online upgrade option is grayed out if you do not have two functioning Series 3 controllers and the \{\2\bring_popup "RDAC Driver" driver\} installed for redundant controller support. For example, this 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 logical units in the module are Optimal.
\p\p
\{\1 o \0\} Before you begin the upgrade procedure, make sure you have received the appropriate NVSRAM files from your Customer Services Representative for downloading. You must copy the file to your host system before downloading. However, do NOT copy them to the same directory as your firmware files in order to bypass the compatibility check performed by fwcompat.def on the NVSRAM files. This file does not recognize NVSRAM files and returns a no compatible files found message. (See the "Installation And Support Guide" specific to your operating system for installation directory information.)
\p\p\1
Steps For Downloading NVSRAM Files\0\p
1. Select the RAID Module you want to download to, then Firmware Upgrade. You could also choose All RAID Modules. \keyword "how to upgrade firmware"
\p\p
2. Read the "Before You Begin" Important Notes, and select OK. A screen displays for you to select the online or offline procedure.
\p\p\1
IMPORTANT\0\p
In a UNIX-system environment, if you are selecting the Offline upgrade in Step 3, you MUST first unmount any filesystems contained on the selected module's logical units so that the software has exclusive access to all the LUNs. Consult the "Installation And Support Guide" for your operating system for specific procedures to follow.
\p\p
3. Select either: \p
\{\1 o \0\} Online to download the files while the selected RAID Module receives I/O. \keyword "online"
\p\p
\{\1 o \0\} Offline to download the files when the selected RAID Module is not receiving I/O. \keyword "offline"
\p\p
After selecting Online or Offline, you see a confirmation box, "Verifying the controller state." The selected RAID Modules are being checked for restrictions based on the type of firmware upgrade you selected. If no restrictions are found, you see what the current firmware version is for the selected RAID Module.
\p\p
4. Select the controllers you want to download an NVSRAM file to. You must download to both controllers if you selected the Online method. If you are performing an Offline download and you selected only one RAID Module in Step 1 that has a redundant controller pair, select one or both controllers. We strongly recommend selecting both controllers to ensure that they have compatible NVSRAM versions.
\p\p\1
IMPORTANT\0\p
Once you select OK in Step 5, do NOT select any other options or exit the Maintenance/Tuning Application until the download process is complete. You can, however, monitor the download progress.
\p\p
5. In the Path box, type the path information for the NVSRAM file you want to download, then select OK to begin the download procedure.
\p\p
6. Follow the \keyword "progress, NVSRAM download" download progress. \p
A histogram for the selected RAID Module indicates the progress of downloading the NVSRAM file. This graphic shows the amount of progress as a percentage and starts over at 0% for each file if you have more than one. 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. If you selected All RAID Modules, the module number updates as each module begins its download process.
\p\p
7. When the NVSRAM download is finished, you see a confirmation box indicating whether or not the download was successful. Select OK.
\p\p\1
IMPORTANT\0\p
If you selected All RAID Modules, it is possible that the download 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.
\p\p
8. If you have successfully downloaded the NVSRAM file, at the command line, type: \1 nvutil -vf\0.\p
This utility checks and corrects any settings on all controllers to ensure that certain settings in the NVSRAM are correct for this software. Consult the "Installation And Support Guide" specific to your operating system for a description of the nvutil utility.
\p\p\1
Related Topics\0\p
\{\3\goto "Following Firmware Upgrade Progress" Can I Follow The Progress For A Firmware Upgrade?\} \p
\{\3\goto "Was The Firmware Upgrade Successful?" How Will I Know If The Upgrade Was Successful?\} \p
\{\3\goto "Files Needed To Perform A Firmware Upgrade" What Files Do I Need To Perform A Firmware Upgrade?\} \p
\{\3\goto "Restrictions Might Prevent A Firmware Upgrade" What Restrictions Might Prevent A Firmware Upgrade?\} \p
\{\3\goto "Using Firmware Upgrade" Using Firmware Upgrade\} \p

\topic "Using Auto Parity Settings"
\0\p\1
Using Options >> Auto Parity Settings\0
\p\p\1
When To Use\0\p
Use to change the Automatic Parity Check/Repair (auto parity) settings. \keyword "Auto Parity Settings"
\p\p
See Related Topics at the bottom of this screen for additional information on this option.
\p\p\1
What Happens\0\p
Allows you to enable/disable auto parity or change its start time. The default settings are (1) enabled auto parity and (2) run at 2:00 am in the morning.
\p\p\1
IMPORTANT\0\p
\{\1 o \0\} Changing any of these settings affects all RAID Modules.
\p\p
\{\1 o \0\} To run a one-time \{\2\bring_popup "Parity Check/Repair" parity check/repair\} manually, use the Manual Parity Check/Repair in \keyword "Recovery Application" the Recovery Application.
\p\p\1
Related Topics\0\p
\{\3\subtopic "Steps To Change The Auto Parity Settings" Steps To Change The Auto Parity Settings\} \p
\{\3\subtopic "What Does Automatic Parity Check/Repair Do?" What Does Automatic Parity Check/Repair Do?\} \p
\{\3\goto "What Is Parity?" What Is Parity?\} \p
\keyword "options menu"
\keyword "parity, settings"

\topic "Steps To Change The Auto Parity Settings"
\0\p\1
Steps To Change The Auto Parity Settings\0
\p\p
1. From the top menu, select Options >> Auto Parity Settings. \keyword "options menu"
\p\p
2. Specify enable or disable: \p
\{\1 o \0\} Select the Enable Automatic Parity Check/Repair box if you want auto parity to run at the specified start time. We strongly recommend leaving this option enabled so that any \{\2\bring_popup "Parity" parity\} corruption can be found and repaired as soon as possible.
\p\p
\{\1 o \0\} Deselect this box if you do not want this operation to run. \keyword "turning off parity"
\p\p
3. Type in or use the spinner boxes to enter the start time you want auto parity to begin each day. \keyword "setting, parity"
\p\p\1
IMPORTANT\0\p
Select a time of low system use for the Automatic Parity Check/Repair to run so that the system performance is not significantly affected while parity is checked and repaired during this operation.
\p\p\1
NOTE\0: The time must be in a 24-hour format; therefore, the time you can set for 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 wanted to set the time to run at three o'clock in the afternoon, set the boxes to read 15 00. \keyword "time, auto parity"
\p\p
4. When finished changing these settings, select Save to keep the changes you have made.
\p\p\1
Related Topics\0\p
\{\3\goto "Using Auto Parity Settings" Using Options >> Auto Parity Settings\} \p
\keyword "how to change parity settings"

\topic "What Does Automatic Parity Check/Repair Do?"
\0\p\1
What Does Automatic Parity Check/Repair Do?\0
\p\p
Enabling Automatic Parity Check/Repair (auto parity) allows this operation to run at the time specified (the default is 2:00 AM). Thus, once a day, auto parity scans the non-degraded logical units on all your RAID Modules for parity inconsistencies. If it finds any inconsistencies, auto parity repairs them and notifies you. Notification includes a parity-event entry in the Message Log \keyword "Status Application" (Status Application), a message to your console and to email. Also, if you have installed SNMP, a message goes to the designated network manager's station.
\p\p\1
IMPORTANT\0\p
We strongly recommend enabling this option, so that parity on your logical units can be checked and repaired as soon as possible.
\p\p\1
Did You Know?\0\p
You can run parity check/repair manually by using Manual Parity Check/Repair in the \keyword "Recovery Application" Recovery Application.
\p\p\1
Related Topics\0\p
\{\3\goto "Using Auto Parity Settings" Using Options >> Auto Parity Settings\} \p
\{\3\goto "What Is Parity?" What Is Parity?\} \p
\keyword "Auto Parity Settings"
\keyword "defaults"
\keyword "parity check/repair"
\keyword "messages, parity"

\topic "Troubleshooting For Maintenance/Tuning"
\0\p\1
Troubleshooting/Common Questions
\p\p
NOTE:\0 For more general problems/questions that could apply in any application, consult the "Troubleshooting/Common Questions" topic on the Home Page.
\p\p\1
General\0\p
\{\3\subtopic "See ''No Controller'' As A Controller Mode" What If I See ''No Controller'' As A Controller Mode?\}
\p\p\1
LUN Reconstruction Rate\0\p
\{\3\goto "Why Did Reconstruction Take A Long Time?" Why Did Reconstruction Take A Long Time?\}
\p\p\1
Caching Parameters\0\p
\{\3\subtopic "Determining Controller's Memory Size" How Can I Tell What Size Memory The Controllers In A RAID Module Have?\}
\p\p
\{\3\goto "What Is Cache Memory?" What Is Cache Memory?\}
\p\p\1
Firmware Upgrade\0\p
\{\3\subtopic "Upgrading Firmware To Only One Controller" Can I Upgrade Controller Firmware To Only One Controller?\}
\p\p
\{\3\subtopic "Firmware Version For A RAID Module's Controllers" How Can I Find Out What Firmware Version A RAID Module's Controllers Have?\}
\p\p
\{\3\subtopic "Was The Firmware Upgrade Successful?" How Will I Know If The Upgrade Was Successful?\}
\p\p
\{\3\subtopic "Files Needed To Perform A Firmware Upgrade" What Files Do I Need To Perform A Firmware Upgrade?\}
\p\p
\{\3\subtopic "No Firmware Files/Versions Are Displayed" What If I Don't See Any Firmware Files/Versions Displayed?\}
\p\p
\{\3\subtopic "Restrictions Might Prevent A Firmware Upgrade" What Restrictions Might Prevent A Firmware Upgrade?\}
\p\p
\{\3\subtopic "Why Do I See Fibre Channel Firmware Code?" Why Do I See Fibre Channel Firmware Code In The Compatible Files/Versions List?\}
\p\p
\{\3\subtopic "Firmware Upgrade Takes A Long Time" Why Would Upgrading Firmware Take A Long Time?\}
\p\p\1
Related Topics\0\p
\{\3\goto "Maintenance/Tuning Application" Maintenance/Tuning Application\} \p
\{\3\goto "Troubleshooting For All Applications" Troubleshooting/Common Questions For All Applications\} \p

\topic "See ''No Controller'' As A Controller Mode"
\0\p\1
What If I See ''No Controller'' As A Controller Mode?\0
\p\p
You might see this message instead of a mode in either LUN Balancing or Controller Mode. It usually means that the selected RAID Module has only one \{\2\bring_popup "Controller" controller\}. However, it could also indicate that the controller is no longer detected, which could mean that there is a bad cable connection or that the controller is \{\2\bring_popup "Offline Controller Mode" offline\}. \p
\keyword "no controller message"
\keyword "messages, no controller"
\keyword "LUN Balancing"
\keyword "Controller Mode"
\keyword "offline"

\topic "Determining Controller's Memory Size"
\0\p\1
How Can I Tell What Size Memory The Controllers In A RAID Module Have?\0
\p\p
Module Profile shows you detailed information about the controllers in a selected RAID Module, including the size for \{\2\bring_popup "Cache Memory" cache\} and \{\2\bring_popup "Processor Memory" processor\} memories.
\p\p
1. Select a RAID Module, then Module Profile >> Controllers.
\p\p
2. Check the Cache/Processor Size row to determine the size of memory (in megabytes) for the controllers.
\p\p
3. Exit Module Profile (select OK) when finished. \p

\topic "Upgrading Firmware To Only One Controller"
\0\p\1
Can I Upgrade Controller Firmware To Only One Controller?\0
\p\p
Yes. Select a single RAID Module that has a pair of \{\2\bring_popup "Redundant Controller Pair" redundant controllers\}, then select Firmware Upgrade >> Offline method. (Remember that you must stop I/Os to the selected RAID Module when using the offline method.) Next, select the controller on which you want to upgrade firmware in addition to highlighting the version level you want to download.
\p\p\4
CAUTION\0\p
In most cases, you will have to download a new \{\2\bring_popup "NVSRAM File" 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). If you do not, certain features of this software and in the controller may not work.
\p\p
Remember that both controllers in a redundant pair must have the same version of controller firmware installed. Therefore, we strongly recommend selecting 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\1
Related Topics\0\p
\{\3\goto "Downloading New NVSRAM Files" Downloading New NVSRAM Files\} \p
\{\3\goto "Using Firmware Upgrade" Using Firmware Upgrade\} \p
\keyword "upgrading firmware to only one controller"
\keyword "controllers, upgrading firmware to one"
\keyword "NVSRAM files"

\topic "Firmware Version For A RAID Module's Controllers"
\0\p\1
How Can I Find Out What Firmware Version A RAID Module's Controllers Have?\0
\p\p
Module Profile \keyword "Module Profile" shows what version of \{\2\bring_popup "Firmware" firmware\} is installed for any module's controllers.
\p\p
1. Select a RAID Module, then Module Profile.
\p\p
2. Under Detailed Information, select Controllers, and look at the Firmware Level column.
\p\p
3. Exit Module Profile (select OK) when finished. \p
\keyword "firmware level"
\keyword "version, firmware"

\topic "Was The Firmware Upgrade Successful?"
\0\p\1
How Will I Know If The Upgrade Was Successful?\0
\p\p
After a firmware upgrade is completed, you see the new version levels for each RAID Module and the \keyword "download status" download status for each file.
\p\p\1
Summary Report\0 for files: lists the files used to upgrade the firmware. These are the files loaded in the Path line when you selected compatible versions of firmware.
\p\p\1
RAID Module\0: Provides the number of a particular \keyword "RAID Module" RAID Module.
\p\p\1
Download Status\0: Indicates whether the download process was completed successfully. Either you see (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\p
\{\3\subtopic "Possible Download Statuses" Possible Download Statuses\} \p
\keyword "device name"
\keyword "Firmware Upgrade"
\keyword "confirm firmware upgrade"

\topic "Possible Download Statuses"
\0\p\1
Possible Download Statuses\0
\p\p
When the firmware upgrade is finished, a confirmation screen indicates whether or not the upgrade was successful. If you selected 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 on the final confirmation screen shows "Failed" followed by the probable cause why.
\p\p\1
Download Statuses \p
Successful\0: Indicates that the firmware upgrade was completed for the RAID Modules and files specified.
\p\p\1
Successful\0 - However, all the LUNs are assigned to only one controller. Use Controller Mode to determine if the controller pair is active/active or 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
\{\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 subdirectory in the \{\2\bring_popup "Installation Directory" installation 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 SCSI Command Write Buffer 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 logical units for the selected module were not Optimal. Use Recovery Guru in the Recovery Application 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" fwcompat.def\} file to the correct 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 Firmware Level and 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 Recovery Guru in the Recovery Application 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 selected firmware files are not compatible with the module's controller type. For example, the module's controller may be an ADP-93, but the firmware version is for the Series 3. Use Module Profile >> Controllers to determine the controller type and model and obtain the correct firmware version files.
\p\p
\{\1 o \0\} The 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 >> 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 Offline. If you have two controllers, use the Status Application to select Health Check and follow the recommended Action To Take to fix the controller problem BEFORE attempting to upgrade the firmware again.
\p\p
\{\1 o \0\} The online upgrade cannot be performed for ADP-93 controllers. Try to upgrade the firmware again and this time be sure to select Offline.
\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 Offline procedure. Be sure to load same version on both controllers in the pair. Use Module Profile >> 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 engine function failure. Use the Status Application to select Message Log for event details.
\p\p
\{\1 o \0\} NVSRAM downloads could fail if you selected All RAID Modules and had copied the NVSRAM files to the same directory as the firmware files (see the "Installation And Support Guide" specific to your operating system for installation directory information). This causes the fwcompat.def file to check for compatibility on the NVSRAM files; however, it does not recognize NVSRAM files and returns a no compatible files found message. \p
\keyword "download status"
\keyword "Firmware Upgrade"

\topic "Files Needed To Perform A Firmware Upgrade"
\0\p\1
What Files Do I Need To Perform A Firmware Upgrade?\0
\p\p\1
Controller Firmware Files\0\p
When you receive new \keyword "firmware files" \{\2\bring_popup "Firmware" firmware\} upgrade files, copy them to your host system before attempting to perform the upgrade procedure. With any new controller firmware upgrade, you should receive one to three firmware files and the \keyword "fwcompat.def" 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 \keyword "defaults" default subdirectory in the \{\2\bring_popup "Installation Directory" installation directory\} for these files. (See the "Installation And Support Guide" specific to your operating system for installation directory information.)
\p\p\1
IMPORTANT\0\p
If you do not copy 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 Files\0\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. However, do NOT copy them to the same directory as your firmware files in order to bypass the compatibility check performed by fwcompat.def on the NVSRAM files. This file does not recognize NVSRAM files and returns a no compatible files found message. (See the "Installation And Support Guide" specific to your operating system for installation directory information.)
\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 controllers and ensure that certain NVSRAM settings are set-up correctly for the storage management software. You 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\}, we recommend 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\p
\{\3\goto "Downloading New Firmware Files" Downloading New Controller Firmware Files\} \p
\{\3\goto "Downloading New NVSRAM Files" Downloading New NVSRAM Files\} \p
\keyword "files, firmware upgrade"
\keyword "compatibility check"
\keyword "NVSRAM files"
\keyword "files, NVSRAM download"

\topic "No Firmware Files/Versions Are Displayed"
\0\p\1
What If I Don't See Any Firmware Files/Versions Displayed?\0
\p\p
If the area under Compatible Files/Versions is blank after you select files for downloading firmware, then the current directory does not contain ALL the necessary firmware files. Remember that the software searches the default subdirectory in the \{\2\bring_popup "Installation Directory" installation directory\} for the firmware files and the \keyword "fwcompat.def" \{\2\bring_popup "fwcompat.def" fwcompat.def\} file. (See the "Installation And Support Guide" specific to your operating system for installation directory information.)
\p\p\1
Actions To Take\0\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
3. We recommend that the version line you select has both \{\2\bring_popup "Firmware" Firmware\} Level and \{\2\bring_popup "Bootware" Boot\} Level versions specified.
\p\p
4. If the upgrade fails a second time, obtain a new copy of the firmware upgrade files. \p
\keyword "defaults"
\keyword "firmware directory"
\keyword "bootware level"

\topic "Restrictions Might Prevent A Firmware Upgrade"
\0\p\1
What Restrictions Might Prevent A Firmware Upgrade?\0
\p\p
After you select the Online or Offline upgrade option, the software determines whether the selected RAID Module is ready for the type of upgrade you selected. It is possible that the software may find restrictions for performing the upgrade.
\p\p
For example, \p
\{\1 o \0\} You cannot perform an offline upgrade with 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 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" logical units\} in the module are 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 unsuccessfully upgraded, you should see a reason why the upgrade did not occur. \p
\keyword "Firmware Upgrade"
\keyword "upgrading controller firmware"
\keyword "restrictions, firmware upgrade"
\keyword "messages, firmware"

\topic "Why Do I See Fibre Channel Firmware Code?"
\0\p\1
"Why Do I See Fibre Channel Firmware Code In The Compatible Files/Versions List?\0
\p\p
It is safe to proceed with a firmware upgrade when you see a fibre channel file 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 displays in this screen (in the (FC) column). When you select files that contain a fibre channel file too, the FC file also is downloaded along with the appware and bootware files. However, the fibre channel code is ignored unless the module's controllers are fibre channel ready. \p
\keyword "Fibre channel and firmware upgrade"
\keyword "Firmware Upgrade"

\topic "Firmware Upgrade Takes A Long Time"
\0\p\1
Why Would Upgrading Firmware Take A Long Time?\0
\p\p
If you select All RAID Modules, then \keyword "Firmware Upgrade" 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
\keyword "time, upgrading firmware"
\keyword "upgrade time"

\file glossary.txt