Back to Contents Page
Controller Description
Array Manager Storage Model
Dell PowerVault 660F RAID Controller Configuration Overview
Dell PowerVault 660F RAID Controller Commands and Procedures Summary
Array Group Commands
Disk Group Commands
Virtual Disk Commands
Array Disk Commands
Controller Commands
Subsystem Commands
Enclosure Management Overview and Commands
Controller Battery and Battery Backup Unit (BBU)
This chapter describes how to configure and manage arrays with the Dell PowerVault 660F RAID controller.
The Dell PowerVault 660F RAID controller is a high-performance Fibre Channel host to Fibre Channel disk array controller. The controller provides one Fibre host channel and two Fibre drive channels conforming to Fibre Channel standards. The logical protocol used for both host and disk communications is 100 MB/s Fibre Channel Protocol (FCP) SCSI over fibre. The controller provides Fibre Channel host performance and fault-tolerant RAID disk operations for Fibre Channel disk environments. The controller is an intelligent, caching controller that supports RAID levels 0, 1, 3, 5, and 0+1. The controller allows multiple hosts to access the array of physical disk drives (array disks), which can be configured as one or more virtual storage devices (virtual disks).
The Dell PowerVault 660F RAID controller also provides continuous access to data in the event of a controller failure. This capability comes with a redundant controller system, using two controllers that share access to the same disk array. In the event of a controller failure, controller operations are assumed by the surviving controller through a failover process. The failed controller can then be removed and replaced while the system is online. The new controller resumes processing array operations in a failback process. During failover and failback, write cache coherency is maintained with the array disks.
The controller supports a battery backup unit (BBU) for maintaining memory content in case of an AC power failure. The principal purpose of the BBU is to provide cache fault tolerance during a power glitch; however, the BBU is capable of sustaining memory content for hours at a time, depending on the type and size of the memory. The fault management features are based on the SCSI-3 Enclosure Services (SES) device interface.
The following features are available on the Dell PowerVault 660F RAID controller:
- SCSI Ping It is an operating mode in which virtual disks configured with the write-back caching policy are treated as though they were configured for write-through operation and the cache is flushed. Allows two controllers to operate in an active-active mode without the requirement of a dedicated serial cable.
- Drive Channel Failover Provides support for using both ports of a dual-ported fibre disk drive in an active-inactive topology.
- Cache Coherency Allows server access to a virtual disk (or LUN) through either controller when operating in an active-active mode.
- Enhanced Write Performance Improvements to write performance, specifically small writes to large cache stripe sizes.
- Memory DIMM Support Additional support for memory DIMM sizes 128 MB, 256 MB, and 512 MB.
- Enclosure Management Provides notification of enclosure status changes for fans, power supplies, and temperature through Array Manager.
- Conservative Cache Mode Provides a higher level of data protection after a critical system component has failed. It switches virtual disks with a write-back cache policy to write-through cache policy and flushes their cache.
- Enclosure Alarms Enabling of enclosure alarms based on drive fault conditions.
- Dell PowerVault 660F RAID Arrays Manages one or more Dell PowerVault 660F arrays within a Fibre Channel zone in a Storage Area Network.
- Drive To Enclosure Map Tables The firmware will provide enough array disk information so that each array disk can be mapped to the enclosure in which it resides.
- 32 LUN Support Allows a maximum of 32 virtual disks.
- Real-Time Online Virtual Disk Expansion Allows for the expansion of a current virtual disk or adding a new virtual disk while the system is online.
- 112 Array Disk Support Supports 112 Fibre Channel array disks assembled in a maximum of 8 enclosures containing a maximum of 14 array disks each.
- 16 Disks per Disk Group Allows a maximum of 16 array disks per disk group.
The Dell PowerVault 660F RAID controller supports the following RAID levels:
- Concatenation
- RAID-0
- RAID-1
- RAID-3 and RAID-5
- RAID-0+1
Supported RAID Levels
RAID Level
|
Description
|
# of Drives Min. Max.
|
Fault Tolerant
|
Concatenation | Storing data either on one disk (generally considered a simple volume) or on disk space that spans more than one disk (a spanned volume). | 1 | 16 | No |
0 | Block striping is provided, which yields higher performance than is possible with individual disk drives. No redundancy is provided. | 2 | 16 | No |
1 | Disk drives are paired and mirrored. All data is 100% duplicated on an equivalent disk drive. | 2 | 2 | Yes |
3 and 5 | Data is striped across several physical disk drives. Parity protection is used for data redundancy. | 3 | 16 | Yes |
0+1 | Combination of RAID levels 0 and 1. Data is striped across disks with mirrors of the stripes on adjacent disks. This allows the benefits of RAID 10, but the configuration can have an odd number of disks. | 3 | 16 | Yes |
You can create a maximum of 32 virtual disks on a Dell PowerVault 660F RAID controller.
Conservative Cache mode is a feature of the Dell PowerVault 660F RAID controller. It is an operating mode in which virtual disks configured with the write-back caching policy are treated as though they were configured for write-through operation and the cache is flushed. Conservative Cache mode is entered to provide a higher level of data protection after a critical system component has failed. When the condition forcing Conservative Cache mode is resolved, the cache policies on the system drives are converted back to their original settings.
Conditions that cause Conservative Cache execution are:
- The Enable Conservative Cache controller option is enabled for a redundant controller configuration, and a controller failure has occurred.
- A power supply has failed (not power supply removal or power supply not present).
- An enclosure supporting redundant power (multiple power supply support) is operating on a single power supply.
- An out-of-limit temperature condition exists.
- SES monitoring has failed.
- The Disable Partner command is invoked.
Working with these controllers requires an understanding of the Array Manager storage model, which represents the Array Manager storage objects in an object hierarchy. Each object has a set of attributes and operations associated with it. Attributes describe the properties of the object, and operations allow you to create new objects and modify existing object attributes. See The Array Manager Storage Model section in the Storage Management Concepts chapter for more information about the Array Manager storage model.
Operations that are grayed out in the console are not supported or not available at that time. To view attributes or to perform operations, right-click on a given storage object. A context menu will appear with a list of commands available, including a Properties command.
This section summarizes the steps for configuring the storage attached to redundant Dell PowerVault 660F RAID controllers.
- Determine requirements for disk groups, virtual disks, and hot spares, including the storage capacity and RAID type for each virtual disk. Make sure the requirements for operating system partitions, fault tolerance, and total capacity are considered during this determination. Note that hot spares are used both for recovery from disk failure and for future capacity expansion.
- Identify requirements for future capacity expansion. Note that if a virtual disk is to be expanded in size at a later time, it must be the only virtual disk in its disk group. This consideration will be helpful when determining whether to create one or many virtual disks within a disk group.
- Create required disk groups and virtual disks. Note the following considerations:
- Each disk group's capacity must be consumed by one or more virtual disks before the next disk group can be created.
- Although virtual disks can be added to a disk group at a later time, if the size of a virtual disk is to be expanded later, then the disk group can contain only a single virtual disk.
- A virtual disk's RAID type must be defined at the time of creation.
- Virtual disks must be initialized before they can be accessed by a host computer operating system. Begin initialization of each virtual disk before creating the next disk group and virtual disk to minimize initialization times.
- The RAID types available depend on the number of array disks in the disk group.
- The stripe size for all virtual disks managed by a PowerVault 660F controller is the same. It is determined by the stripe size setting on the first virtual disk created. For the remaining virtual disks, the stripe size setting is grayed out.
- Assign one or more hot spares to enable auto-rebuild in the event of drive failure within a fault-tolerant virtual disk.
- If your PowerVault 660F controller is connected through "direct attach," you must rescan in Windows® 2000 or reboot in Windows NT®. If the PowerVault 660F controller is part of a SAN, you must first assign the virtual disk to a server by using the Dell OpenManage Storage Consolidation software.
- Create and format operating system partitions to complete the configuration. See the Disk Management and Volume Management chapters for details.
The remainder of this chapter provides detailed information on the Dell PowerVault 660F RAID controller commands and procedures and has the following main topics:
An array group contains array disks that are controlled by a particular array controller. An array group is named by the number of the array controller it is associated with. For example, array disks attached to Controller 0 belong to Array Group 0. Because the Dell PowerVault 660F RAID controller can support 112 array disks in a single array group, array disks must be further divided into disk groups with up to 16 disks each. You create virtual disks from a disk group.
You can perform the following operations from the Array Group context menu:
- Create groups of array disks Use the Create Disk Group function to select specific array disks to be configured as a disk group.
- Add global hot spare disks Use the Add Spares function to add global hot spare disks to the selected disk group.
- Delete all information on the controller Use the Reset Configuration function to clear the controller in order to create a fresh configuration.
- View information on a selected array group Use the Array Group Properties command.
To bring up an array group's context menu, right-click the array group object in the tree view.
Use this function to create a disk group from available physical array disks. The disk group of array disks will be used to create virtual disks. The full capacity of the disk group must be used before additional disk groups can be created. You can have up to 16 array disks per disk group. Before you create a disk group, consider the following items:
- The number of disks needed for the RAID levels you want to implement.
- The number of virtual disks to include in the disk group. Note that if the disk group is to be expanded later, it can contain only one virtual disk.
- Right-click on an array group.
- Click on Create Disk Group. The Create Disk Group dialog box appears.
- Select one or more array disks from the Available Array Disks list. Drag the selected disk(s) to the Add Array Disks list or click Add Disk to add to the Add Array Disks list. Continue adding disks as required by your configuration.
- Disks can be removed from the Add Array Disks list by selecting the specific disk and clicking on Remove Disk, or remove all disks from the Add Array Disks list by clicking on Remove All.
- Verify that the Add Array Disks list contains the appropriate disks. Click OK to invoke the changes. (Click Cancel to discontinue the operation.)
Use this function to create a global hot spare disk.
- Right-click on an array disk group.
- Click Add Spares. The Add Spares dialog box appears.
- Select one or more array disks from the Available Array Disks list. Drag the selected disk(s) to the Add Array Disks list or click Add Disk to add to the Add Array Disks list. Continue adding spare disks as required by your configuration.
- Disks can be removed from the Add Array Disks list by selecting the specific disk and clicking on Remove Disk, or remove all disks from the Add Array Disks list by clicking on Remove All.
- Verify that the Add Array Disks list contains the appropriate disks. Click OK to make the changes. (Click Cancel to discontinue the operation.)
Use this function to delete all configuration information on the controller, so you can perform a fresh configuration.
|
CAUTION! Resetting a configuration permanently destroys all data on
the controller and array disks. This operation is not
recoverable.
|
- Right-click on an array disk group.
- Click Reset Configuration. A warning/confirmation dialog box appears warning that all virtual disks and data will be lost. The user is asked to confirm this operation.
- Click Yes to continue. (Click No to exit the function.)
The Properties command for a selected array group displays the following information:
- Name This field displays the array group number, which is equivalent to the controller number.
- Controller This field displays the number of the controller with which this array group is associated. There is one number for the pair of controllers.
- Status This field displays the current status of the array group. Possible values are:
- Online The array group has been configured and is functioning normally.
- Offline The array group has not been configured, or the configuration has just been cleared.
- Failed The array group has failed to operate properly.
- Rebuild The array group has been configured and is in the process of being rebuilt.
 |
Note: If the status value is anything other than Ready, a red X appears
to the left of the status to indicate a situation that requires attention.
|
You can perform the following operations from the Disk Group context menu:
- Create virtual disks Use the Create Virtual Disk Wizard to create virtual disks.
- Apply RAID policies Use the Apply RAID Policy Wizard to apply RAID policies to virtual disks and volumes.
- Customize RAID policies Use the Edit RAID Policy Wizard to create, edit, or delete RAID policies.
- Add capacity to a virtual disk Use the Expand Capacity function to increase the size of the virtual disk.
- Add virtual disks to a disk group Use the Add Virtual Disk function to add virtual disks to the array disk group.
- Delete a disk group Use the Delete Disk Group function to remove a disk group from the array group.
- View information on a selected disk group Use the Disk Group Properties command.
To bring up a disk group's context menu, right-click the disk group object in the tree view.
Creating virtual disks allows you to choose from a variety of RAID configurations to make the best use of your array disk storage. You must create a disk group before creating a virtual disk, because the array disks for a virtual disk are selected from a disk group. See Create Disk Group in this chapter for details.
The Dell PowerVault 660F RAID controller supports the following RAID configurations: concatenation, RAID-0, RAID-1, RAID-3, RAID-5, and RAID-0+1. For more information about RAID configurations, see Choosing RAID Levels in the Storage Management Concepts chapter.
 |
Note: When you create virtual disks, you may want to consider how
virtual disks must be deleted. Because of hardware constraints, virtual
disks must be deleted in reverse order of their creation. In other words,
you must delete the most recently created virtual disk first and
continue to delete in reverse order.
|
- Right-click on a disk group.
- Click on Create Virtual Disk. The Welcome to the Create Virtual Disk Wizard screen appears.
- Read the welcome screen and click Next to continue. (Click Cancel to discontinue the operation.) The Select Virtual Disk Type screen appears.
- Select the Type, Size, Stripe Size, and Write Policy for the virtual disk. Supported virtual disk types or RAID levels are available in the drop-down menu of the Type field.
Supported stripe size values are available in the drop-down menu of the Stripe Size field. The stripe size is selectable only on the first virtual disk created. When you create additional virtual disks, the stripe size setting is grayed out because there can be only one stripe size for all virtual disks on the same Dell PowerVault 660F controller.
The Write Policy toggles between Write Cache Enabled and Write Cache Disabled. When write cache is enabled, the controller returns a completion status to the host as soon as the cache receives the data. The target device receives the data at a more appropriate time. When write cache is disabled, the controller writes data to the target device before returning completion status to the host.
- When the virtual disk attributes are set appropriately, click Next to continue. (Click Back to return to the previous screen. Click Cancel to discontinue the operation.) The Completing the Create Virtual Disk Wizard screen appears.
 |
Note: Initializing the new virtual disk is strongly recommended and
may take approximately one hour to complete, depending on the size
of the virtual disk.
|
- Check the Initialize Disk option if you want to initialize the new virtual disk immediately, and click Finish to create the virtual disk as determined in the previous steps. (Click Back to return to the previous screen. Click Cancel to discontinue the operation.)
 |
Note: If you wish, initialization can be performed later by choosing
Initialize from the Virtual Disk popup menu.
|
If this is the first virtual disk created, a dialog box notifying the user that the controller needs to reset appears. The reset operation may take more than 30 seconds to complete.
- Click OK to continue.
Use this function to apply RAID policies and create virtual disks.
 |
Note: If you use this method, all your virtual disks will be in one disk
group. You will not be able to use the Expand Capacity command to
add disks in the future.
|
- Right-click on a disk group.
- Click Apply RAID Policy. The Welcome to the RAID Policy Wizard screen appears.
- Read the welcome screen and click Next to continue. (Click Cancel to discontinue the operation.) The Select RAID Policy screen appears.
- Use the RAID Policy Browser to select a RAID policy to apply to the array disk group. Check the disk(s) for which this RAID policy is to be applied. Changes can be made to this policy's settings by double-clicking on any of the fields. These changes will be applied "on the fly" without editing or creating a new RAID policy. Click on Revert to default to revert to the existing policy's default settings.
- When the RAID policies are set appropriately, click Next to continue. (Click Back to return to the previous screen. Click Cancel to discontinue the operation.) The Completing the RAID Policy Wizard screen appears.
 |
Note: Initializing the new virtual disk is strongly recommended and
may take approximately one hour to complete, depending on the size
of the virtual disk.
|
- Check the Initialize Disk option if you want to initialize the new virtual disk immediately, and click Finish to create the virtual disk as determined by the RAID policy chosen. (Click Back to return to the previous screen. Click Cancel to discontinue the operation.)
 |
Note: If you wish, initialization can be performed later by choosing
Initialize from the Virtual Disk popup menu.
|
If this is the first virtual disk created, a dialog box notifying the user that the controller needs to reset appears. The reset operation may take more than 30 seconds to complete.
- Click OK to continue.
 |
Note: If your PowerVault 660F controller is connected through direct
attach, you must rescan in Windows 2000 or reboot in Windows NT. If
the PowerVault 660F controller is a part of a SAN, you must first
assign the virtual disk to a server by using the Dell OpenManage
Storage Consolidation software.
|
Use this function to create, edit, or delete RAID policies.
- Right-click on a disk group.
- Click Edit RAID Policy. The RAID Policy Editor screen appears.
- Click New Policy. An empty secondary RAID Policy Editor screen appears.
- Click Add Disk. A disk with empty attribute fields appears on the screen.
- Edit the fields by typing the appropriate information, or double-click in the field for a popup menu of possible settings.
- Add more disks as required for your configuration.
The last disk in the list can be removed from the configuration by clicking Remove Disk.
- Enter a name in the Policy Name field.
- When all settings are correct, click OK to return to the main RAID Policy Editor screen. (Click Cancel to discontinue the operation.)
- Click OK to save the configuration. (Click Cancel to discontinue the operation.)
- Right-click on a disk group.
- Click Edit RAID Policy. The RAID Policy Editor screen appears.
- Select the RAID policy you wish to modify.
- Click Modify Policy. A secondary RAID Policy Editor screen appears showing the attributes of the selected RAID policy.
- Edit the fields by typing the appropriate information, or double-click in the field for a popup menu of possible settings.
- Add or delete disks as required by your configuration.
- When all settings are correct, click OK to return to the main RAID Policy Editor screen. (Click Cancel to discontinue the operation.)
- Click OK to save the configuration. (Click Cancel to discontinue the operation.)
- Right-click on a disk group.
- Click Edit RAID Policy. The RAID Policy Editor screen appears.
- Select the RAID policy you wish to delete.
- Click Delete Policy.
- Click OK to save the configuration. (Click Cancel to discontinue the operation.)
 |
Note: The Expand Capacity command is not available unless the
PowerVault 660F controller is operating with the partner controller
held in reset. Use the Disable Partner command to place the partner
controller in reset before invoking Expand Capacity. This command
can be performed only on disk groups with one virtual disk.
|
Use this function to increase the capacity of an existing disk group while the controller is online. The Expand Capacity command appends the added array disk's capacity to the existing virtual disk specified in the request. In contrast, the Add Virtual Disk command adds a new virtual disk, using the existing array disks.
- Right-click on a disk group containing the virtual disk to be expanded.
- Click on Expand Capacity. The Expand Capacity dialog box appears.
- Select one or more array disks from the Available Array Disks list. Drag the selected disk(s) to the Add Array Disks list or click Add Disk to add to the Add Array Disks list. Continue adding disks until you want to stop or you reach the limit.
Array disks can be removed from the Add Array Disks list by selecting the specific disk and clicking on Remove Disk, or remove all disks from the Add Array Disks list by clicking on Remove All.
- Verify that the Add Array Disks list contains the appropriate disks. Click OK to make the changes. (Click Cancel to discontinue the operation.)
A temporary disk group appears that contains the selected array disks. This disk group remains until the Expand Capacity procedure is completed. When the procedure is finished, the temporary disk group goes away and the selected array disks are displayed under the disk group that contains the virtual disk that has been expanded.
The Expand Capacity process takes approximately 4 to 12 hours to complete, depending on the number of disks involved and their capacity.
- After the Expand Capacity process has completed, you MUST enable the partner controller and reset the controller.
See the Enable Partner and Reset commands.
 |
Note: No rebuilds will take place until after the Expand Capacity
operation is completed and the partner is enabled.
|
- If the virtual disk is on a Windows NT server, you must first reboot to use the free space.
- You are now ready to put a format and a file system on the free space.
Refer to Working with Dynamic Volumes in the Volume Management chapter.
 |
Note: The Add Virtual Disk command is not available unless the
PowerVault 660F controller is operating with the partner controller
held in reset. Use the Disable Partner command to place the partner
controller in reset before invoking Add Virtual Disk.
|
The Add Virtual Disk adds a new virtual disk, using the existing array disks.
- Right-click on a disk group.
- Click on Add Virtual Disk. The Welcome to the Add Virtual Disk Wizard screen appears.
- Read the welcome screen and click Next to continue. (Click Cancel to discontinue the operation.) The Select Virtual Disk Type screen appears.
- Select the Type and Write Policy for the virtual disk.
Supported virtual disk types or RAID levels are available in the drop-down menu of the Type field.
Supported RAID levels are described in the Supported RAID Levels table near the beginning of this chapter.
The Write Policy toggles between Write Cache Enabled and Write Cache Disabled. When write cache is enabled, the controller returns a completion status to the host as soon as the cache receives the data. The target device receives the data at a more appropriate time. When write cache is disabled, the controller writes data to the target device before returning completion status to the host.
- When the virtual disk attributes are set appropriately, click Next to continue. (Click Back to return to the previous screen. Click Cancel to discontinue the operation.) The Select Disk screen appears.
- Select one or more spare disks for this virtual disk by checking the appropriate disk(s).
- When the spare disk or disks are selected, click Next to continue. (Click Back to return to the previous screen. Click Cancel to discontinue the operation.) The Completing the Add Virtual Disk Wizard screen appears.
 |
Note: Initializing the new virtual disk is strongly recommended and
may take approximately one hour to complete, depending on the size
of the virtual disk.
|
- Check the Initialize Disk option if you want to initialize the new virtual disk immediately, and click Finish to create the virtual disk as determined in the previous steps. (Click Back to return to the previous screen. Click Cancel to discontinue the operation.)
 |
Note: If you wish, initialization can be performed later by choosing
Initialize from the Virtual Disk popup menu.
|
- Click OK to continue.
- After the Add Virtual Disk process has completed, you MUST enable the partner controller and reset the controller.
See the Enable Partner and Reset commands.
 |
Note: No rebuilds will take place until after the Add Virtual Disk
operation is completed and the partner is enabled.
|
- If you are using a SAN, see the SAN Administrator's Guide for instructions on how to assign the new virtual disk to a server, using the Dell OpenManage Storage Consolidation software.
Use this function to remove the selected disk group from the array group.
 |
Note: Before you can delete a disk group, you must have deleted the
virtual disks in the disk group.
|
- Right-click on a disk group.
- Click Delete Disk Group. A warning/confirmation dialog box appears notifying the user that the selected disk group will be deleted. The user is asked to confirm this operation.
- Click Yes to continue. (Click No to exit the function.)
 |
Note: After deleting the last disk group, you must reset the
configuration. See Reset Configuration in this chapter.
|
The Properties command for a disk group gives the following information on the selected disk group:
- Group Size This field displays the total size of the disk group. This is the sum of all selected disks' physical sizes configured in this disk group.
- Used Space This field displays the amount of used or configured space.
- Free Space This field displays the amount of free or unused space.
- Minimum Stripe Size This field displays the minimum stripe size supported for this disk group.
- Maximum Stripe Size This field displays the maximum stripe size supported for this disk group.
- Default Stripe Size This field displays the default stripe size. Supported stripe sizes are 4 KB, 8 KB, 16 KB, 32 KB, and 64 KB.
- Status This field displays the current status of the disk group. Possible values are:
- Online The disk group has been configured and is functioning normally.
- Offline The disk group has not been configured or the configuration has just been cleared.
- Failed The disk group has failed to operate properly.
- Rebuild The disk group has been configured and is in the process of being rebuilt.
 |
Note: If the status value is anything other than Ready, a red X appears
to the left of the status to indicate a situation that requires attention.
|
You can perform the following operations from a virtual disk's context menu:
- Change write caching policy Use the Change Policy function to change the write caching policies of your virtual disks.
- Delete a virtual disk Use the Delete Virtual Disk function to delete the virtual disk that was created last.
- Initialize a virtual disk Use the Initialize function to manually initialize the virtual disks.
- Cancel an initialization Use the Cancel Initialize function to cancel an initialization that is in progress.
- Check redundant data information Use the Check Consistency function to verify the integrity of data on the virtual disk.
- Cancel a check consistency Use the Cancel Check Consistency function to cancel a consistency check that is in progress.
- Force a virtual disk online Use the Force Online function to force an offline virtual disk to an online status.
- View information on a selected virtual disk Use the Virtual Disk Properties command.
To bring up a virtual disk's context menu, right-click the virtual disk object in the tree view. For more information why you would want to use virtual disks, see the section Create Virtual Disk in this chapter.
Use this function to change the read and write cache policies of a virtual disk. This setting can be used only when the PowerVault 660F controller is not in Conservative Cache mode.
- Right-click on a virtual disk.
- Click Change Policy. The Write Policy dialog box appears.
Select either Write Cache Enabled or Write Cache Disabled. The Write Policy toggles between Write Cache Enabled and Write Cache Disabled. When write cache is enabled, the controller returns a completion status to the host as soon as the cache receives the data. The target device receives the data at a more appropriate time. When write cache is disabled, the controller writes data to the target device before returning completion status to the host.
- Click OK to make the change. (Click Cancel to discontinue the operation.)
 |
Note: This function is enabled only for the virtual disk that was
created last. Because of hardware constraints, virtual disks must be
deleted in the reverse order of their creation. In other words, you must
delete the most recently created virtual disk first and continue to delete
in reverse order.
|
Use this function to delete the virtual disk that was created last.
- Right-click on the virtual disk that was created last.
- Click Delete. A warning/confirmation dialog box appears warning that all data on the selected virtual disk will be lost. The user is asked to confirm the operation.
|
CAUTION! Deleting a virtual disk permanently deletes all information
contained on that disk.
|
- Click Yes to continue. (Click No to exit the function.) The virtual disk disappears from the left pane and the right pane in the Array Manager console if the array group is selected.
Use this function to manually start initializing a virtual disk.
- Right-click on a virtual disk.
- Click Initialize. A warning/confirmation dialog box appears warning that all current data on the virtual disk will be lost and recommends that the user not perform any disk or volume operations on the corresponding disks while the initialization is in progress.
- Click Yes to continue. (Click No to exit the function.) The initialization progress is indicated in the right pane. The virtual disk status indicates "Initializing" and the progress indicates the percent completed.
Use this function to manually stop an initialization that is in progress.
- Right-click on a virtual disk.
- Click Cancel Initialize. A warning/confirmation dialog box appears asking the user to confirm the operation.
- Click Yes to continue. (Click No to exit the function.)
Use this function to begin a consistency check. A consistency check verifies that mirror or parity information matches the stored data on the redundant arrays (RAID-1, RAID-3, RAID-5, or RAID-0+1). If the parity block information is inconsistent with the data blocks, the controller has the ability to correct the inconsistencies.
- Right-click on a virtual disk.
- Click Check Consistency. A warning/confirmation dialog box appears warning that other disk or volume operations on the corresponding disks not be performed while the consistency check is in progress. The user is asked to confirm this operation.
- Click Yes to continue. (Click No to exit the function.)
Use this function to manually stop a consistency check that is in progress.
- Right-click on a virtual disk.
- Click Cancel Check Consistency. A confirmation dialog box appears asking whether you want to cancel the consistency check.
- Click Yes to continue. (Click No to exit the function.)
Use this function to force an offline virtual disk to online status. This command is needed to recover a failed virtual disk after one or more failed array disks are replaced.
- Right-click on the offline virtual disk.
- Click Force Online. The status change is indicated in the right pane. The virtual disk status indicates a change from offline to online.
The Properties command for a virtual disk gives the following information on the selected virtual disk:
- RAID Level This field displays the RAID level assigned to this virtual disk. Refer to Supported RAID Levels for more information.
- Target ID This field displays the target ID for this virtual disk.
- Cache Policy This field displays the write cache policy assigned to this virtual disk. Refer to Change Policy for more information. This setting is used when the controller is not in Conservative Cache mode.
- LUN This field displays the Logical Unit Number (LUN) assigned to this virtual disk.
- Physical Size This field displays the configured size of the virtual disk.
- Used Array Capacity This field is not applicable at this time and always displays 0.00 MB.
- Cache Line This field is not applicable at this time and is always equal to the Stripe Size.
- Stripe Size This field displays the stripe size assigned to this virtual disk. Refer to Create Virtual Disk for more information.
- Status This field displays the current status of the virtual disk. Possible values are:
- Online The virtual disk has been configured and is functioning normally.
- Offline The virtual disk has not been configured or the configuration has just been cleared.
- Failed The virtual disk has failed to operate properly.
- Rebuild The virtual disk has been configured and is in the process of being rebuilt.
 |
Note: If the status value is anything other than Ready, a red X appears
to the left of the status to indicate a situation that requires attention.
|
Array disks are the physical hard disk drives attached to the controller through the enclosure. The array disks are configured into virtual disks to become members of a disk group. You can perform the following operations from the Array Disk context menu:
- Locate a specific array disk Use the Blink Disk function to blink the LED on the enclosure for the selected array disk.
- Rebuild a failed array disk Use the Rebuild function to return a degraded virtual disk to online status by rebuilding the redundant data on a hot spare or replacement array disk.
- Cancel a rebuild operation Use the Cancel Rebuild function to cancel a rebuild that is in progress.
- Prepare an array disk for removal Use the Prepare to Remove function to spin the array disk down in preparation for removal from the enclosure.
- Define an array disk as a global hot spare disk Use the Make Global Hotspare function to assign a selected array disk to act as a backup hot spare.
- Unassign a hot spare disk Use the Unassign Global Hotspare function to remove the hot spare status from the selected array disk.
- Force an array disk to Offline status Use the Make Offline function to force the selected array disk to offline status.
- View information on a selected disk group Use the Array Disk Properties command.
To bring up an array disk's context menu, right-click the array disk object in the tree view.
Use this function to locate the selected array disk.
- Right-click on an array disk.
- Click Blink Disk. The Locate Disk dialog box appears.
- Click Blink to activate the LED for the selected array disk. The LED on the hard-disk carrier may take 30 seconds to start blinking.
Click Done when finished. The LED may continue blinking for another 30 seconds.
The Rebuild function uses a hot spare to rebuild a degraded virtual disk. You can do only one rebuild at a time.
- Right-click on an array disk.
- Click Rebuild.
A warning/confirmation dialog box appears recommending that you not perform any disk or volume operations on the corresponding disks while the rebuild is in progress, and asking whether you want to rebuild this array disk.
- Click Yes to continue. (Click No to exit the function.)
The status and progress are indicated in the right pane. The array disk status indicates "Rebuilding."
Use this function to manually stop a rebuild that is in progress.
- Right-click on an array disk.
- Click Cancel Rebuild. A confirmation dialog box appears asking whether you want to cancel the array disk rebuild.
Click Yes to continue. (Click No to exit the function.)
This command spins an array disk down to prepare it for removal. Only array disks that have a hardware failure or that have been brought offline can be prepared for removal.
 |
Note: Unused array disks that are not part of a virtual disk and that are
already spun down can be removed at any time.
|
- Right-click on an array disk.
- Click Prepare to Remove.
A confirmation dialog box appears asking whether you want to prepare this array disk for removal.
- Click Yes to continue. (Click No to exit the function.)
The array disk will spin down so that it can be removed.
Use this function to designate the selected array disk as a global hot spare disk.
- Right-click on an array disk.
- Click Make Global Hotspare. The array disk is labeled as a hot spare in the left pane. The information in the right pane is updated to indicate that the array disk status is Ready and the type is Spare Array Disk.
Use this function to unassign the selected array disk as a global hot spare disk.
- Right-click on an array disk.
- Click Unassign Global Hotspare. The type change is indicated in the right pane. The array disk status indicates Ready and the type is Array Disk.
Use this function to force the selected disk to Offline status.
- Right-click on an array disk.
- Click Make Offline. A warning/confirmation dialog box appears warning that loss of data may occur. The user is asked to confirm this operation.
- Click Yes to continue. (Click No to exit the function.) The status change is indicated in the right pane. The array disk status indicates a change from Online to Offline
 |
Note: Forcing an array disk that is part of a disk group offline may
start a rebuild or may fail one or more virtual disks in the disk group.
|
The Properties command for an array disk gives the following information on the selected array disk:
- Vendor This field displays the disk drive manufacturer or vendor name.
- Product This field displays the disk drive product number or model number.
- Revision This field displays the current version of firmware operating on the disk drive.
- Serial # This field displays the disk drive serial number
- Bus Type This field displays the bus type supported by this disk drive. Currently only fibre disk drives are supported.
- Port This field displays the drive port to which this disk drive is attached.
- Target ID This field displays the target ID for the selected disk drive.
- Enclosure ID This field displays the ID of the enclosure where this disk drive is located.
- LUN This field displays the Logical Unit Number (LUN) assigned to this disk drive.
- Free Space This field indicates the amount of unused space available on the disk drive.
- Used Space This field indicates the amount of disk space used or configured.
- Physical Size This field indicates the actual size of the disk drive.
- Largest Contiguous Free Space This field indicates the largest amount of free space and is equal to the amount of free space listed above.
- LUN This field displays the LUN ID for the selected disk drive.
- The Status field indicates the disk drive's current status. The possible values are:
- Online The disk is powered on, part of a configuration, and functioning normally.
- Offline The device has been inserted, powered on into an unconfigured slot, or the configuration has just been cleared. The device is not part of a configuration.
- Failed The device has failed to operate properly.
- Rebuild The device is powered on, part of a configuration, and in the process of being rebuilt.
 |
Note: If the status value is anything other than Ready, a red X appears
to the left of the status to indicate a situation that requires attention.
|
You can perform the following controller operations, which enhance your ability to configure and manage your system:
- Modify controller parameters Use the Controller Options function to customize the Dell PowerVault 660F RAID controller parameters and features to meet the needs of your system.
- Add drive enclosures Use the Add Enclosure option to add drive enclosures while the subsystem is still active.
- Change firmware versions Use the Download function to upgrade the Dell PowerVault 660F RAID controller firmware or the SES Processor firmware when new versions are available.
- Force the partner controller to be held in reset Use the Disable Partner function to hold the partner controller in reset.
- Revive the partner controller held in reset Use the Enable Partner function to return the partner controller to full functionality.
- Perform a warm power cycle of the controllers Use the Reset function to cycle power on the controllers.
- Prepare the controller for shutdown Use the Disable BBU function to prepare the controller for shutdown in order to move to another location.
- Return the controller to normal operation Use the Enable BBU function to return the controller to normal operation.
- Monitor battery functionality on both controllers Use the C0 Battery and C1 Battery menu to manage battery functionality.
- To view the properties of the battery Use the Battery Properties command.
- To view the properties of the controller Use the Controller Properties command.
To bring up a controller's context menu, right-click the controller object in the tree view.
Each Dell PowerVault 660F RAID controller is shipped from the factory with initial settings that have been found to work well in a majority of applications and environments. These settings are listed as the controller options and vary depending on product and user requirements. You can customize controller options and features to meet the needs of your system. The Controller Options dialog box has the following tabs:
You can also revert any settings you make to the default factory options.
Use the revert function to return to the Dell PowerVault 660F Controller factory default values at any time from any controller option page.
- Right-click on a controller.
- Click on Controller Options. The Controller Options multi-tabbed dialog box appears with the Advanced tab open.
- Click Revert. The Revert to Factory Defaults dialog box appears.
- Select either Current Page Only or All Controller Options.
- Current Page Only returns the controller options on this page only to the factory default values.
All Controller Options returns all controller options to the factory default values.
- Click OK to make the changes. (Click Cancel to discontinue the operation.)
- A controller reset is required when making some controller option changes. Controller options requiring a controller reset are indicated with a popup window when the mouse cursor moves over the controller option. A controller reset is recommended after making any changes to the controller configuration. If a dialog box does NOT appear with the warning that a controller reset will occur, refer to the Reset command for controller reset instructions.
- Right-click on a controller.
- Click on Controller Options.
- Click the Advanced tab to continue. The Advanced tab opens.
 |
Note: Checking a specific option activates that option, either enabling
or disabling the option as stated in the dialog box. No check indicates
that the option is not activated.
|
- Make changes to the following Advanced controller options as required by your product and configuration:
- Conservative Cache ModeDefault=Disabled. This function is provided to allow a controller an extra degree of data safety when operating in a degraded state. This function switches write-back caching to write-through operation after a critical system component fails or a degraded state is detected. When the degraded condition is resolved, write-back caching operations resume. Conservative Cache mode is entered automatically when a power supply failure, over-temperature condition, partner controller failure, Expand Capacity operation, or SES failure exists.
- Restrict Reassign to One BlockDefault=Disabled. This function limits reassigning failures to the single failed block. This option is limited to recovered errors and medium errors. If the sense on the error does not indicate one of these errors, then this setting does not apply. When Restrict Reassign to One Block is disabled, all reassigns are allocated to the entire I/O process. A controller reset is required when making changes to this controller option.
- Smart Large Host TransfersDefault=Enabled. This function allows selection of Coalesce (fewer disconnects on large transfers) or As Available (more disconnects) on host data transfers. This function is most effective on SCSI but has some benefit on Fibre Channel systems. The Smart Large Host Transfers function takes effect for transfers larger than the stripe size.
- True Verification Of DataDefault=Disabled. If this option is disabled, the Verify command returns a status without data checking. If this option is enabled, the Verify command checks data before returning a status. Enabling this option compromises performance. A controller reset is required when making changes to this controller option.
- Write Through VerifyDefault=Disabled. This function enables Force Unit Access for reads and writes during error handling. Force Unit Access bypasses the cache and forces all reads and writes directly to or from the disk. A controller reset is required when making changes to this controller option. For some devices, enabling Force Unit Access reduces sequential write performance by up to 86%.
- Enclosure ManagementDefault=Enabled. This function allows the controller to take autonomous actions when a failure occurs. Actions that the Operational Fault Management function monitors and reports include array disk failures, background activity completion status, and enclosure events. This function should remain enabled during normal controller operation. Do not disable this function unless specifically instructed to do so as part of a troubleshooting diagnostic activity (such as upgrading the array disk firmware). The Operational Fault Management function works in conjunction with Automatic Rebuild Management and features in SES certified disk array enclosures to detect the removal of a failed array disk. The Enclosure Management option must be enabled to allow the PowerVault 660F controller to exercise its full array management capabilities.
- Automatic Rebuild ManagementDefault=Enabled. This function allows the controller to take autonomous actions when a failed array disk is replaced or a configured global hot spare disk drive is present. The Automatic Rebuild Management function works in conjunction with Operational Fault Management and features in SES certified disk array enclosures to detect the removal of a failed array disk. The Automatic Rebuild Management function also performs an automatic rebuild after a replacement array disk is installed into a redundant (fault tolerant) array (RAID-1, RAID-3, RAID-5, and RAID-0+1).
- Coalesce Device QueuesDefault=Enabled. This function provides device queuing coalescing optimization. The function enables data traffic coalescing (combining of address adjacent I/Os) on the traffic of each device. This joins the data from adjacent I/Os into a single I/O to improve performance.
- Queue LimitDefault=16. This option specifies the allowed queue depth for tagged commands to all attached array disks. This value is further limited to the array disk's own tag limit. Allowed values are 1 to 230. A setting of 1 is similar to no tags. If using coalescing, set the queue tag limit to 2.
- When the Advanced controller options are set appropriately, click OK to make the changes. (Click Revert to revert controller options to factory default values. Click Cancel to discontinue the operation.)
- Right-click on a controller.
- Click on Controller Options.
- Click the Expert tab to continue. The Expert tab opens.
 |
Note: Checking a specific option activates that option, either enabling
or disabling the option as stated in the dialog box. No check indicates
that the option is not activated.
|
- Make changes to the following Expert controller options as required by your product and configuration:
- On Q Full Give BusyDefault=Disabled. Enabling this option sets the controller to return a Busy status when a Queue Full condition is detected. Disabling this option sets the controller to return a Queue Full status. When a command is received and the controller detects a Queue Full condition, it normally returns Queue Full status. This option is intended to help hosts that are confused by Queue Full. A controller reset is required when making changes to this controller option.
- Disable Busy Status During FailbackDefault=Disabled. The Disable Busy Status During Failback function allows the controller to disregard new requests without returning a Busy status. If enabled, during failback, the surviving controller ignores all new requests and does not return any status. If disabled, the surviving controller returns a Busy status to new commands received from the host during the cache flush operation. A controller reset is required when making changes to this controller option.
- Vendor Unique Test Unit Ready StatusDefault=Disabled. This function enables a vendor unique TUR response sent to an offline LUN. If disabled, a Hard Error status is returned. If enabled, a Not Ready status is returned. A controller reset is required when making changes to this controller option.
- No Pause On Controller Not ReadyDefault=Disabled. This option turns the pause off or on for certain commands when the controller is not ready. Normally, when the controller is starting up, certain commands encounter a pause. This happens only when the controller has not reached Startup Complete. The pause lasts one second. The commands affected are: Prefetch, Read/write, Read/write Extended, Tur, Verify, and Write Verify. A controller reset is required when making changes to this controller option.
- Disable CC For Invalid LUNDefault=Disabled. When enabled, disables Check Condition for an invalid LUN. This affects the handling of the Inquiry command when the referenced LUN is invalid. If enabled, the Inquiry command returns data with the peripheral qualifier indicating that the peripheral device is not connected. If disabled, the Inquiry command will be failed with a check condition of "Illegal Request, LUN Not Supported." A controller reset is required when making changes to this controller option.
- Auto Restore (automatic failback)Default=Enabled. When enabled in a redundant controller system, Auto Restore allows automatic recovery of a partner controller when a replacement is inserted. A controller reset is required when making changes to this controller option.
- Reset PropagationDefault=Disabled. This function allows a port to issue an internal reset without causing a reset event to occur on its attached interface. If enabled, a port that issues an internal reset propagates the reset by causing a reset event to occur on its attached interface. If disabled, a port will not cause a reset event on its attached interface as part of issuing an internal reset.
- Multi-port ResetDefault=Disabled. This function restricts internal resets to ports that have logical devices reserved through that port. If enabled, an internal reset is executed by a port only if a logical device has been reserved through that port. If disabled, internal resets are not qualified by logical device reservations.
- Rebuild RateDefault=50. Change the default Rebuild Rate to less than or equal to 50. A rate of 50 devotes the maximum allowable resources to a drive rebuild or array expansion, allowing the Rebuild or Expand to proceed at its fastest. Lowering the number devotes more resources to I/Os and consequently slows the Rebuild or Expand process.
- When the Expert controller options are set appropriately, click OK to make the changes. (Click Revert to revert controller options to factory default values. Click Cancel to discontinue the operation.)
- Right-click on a controller.
- Click on Controller Options.
- Click the Fibre tab to continue. The Fibre tab opens.
 |
Note: Checking a specific option activates that option, either enabling
or disabling the option as stated in the dialog box. No check indicates
that the option is not activated.
|
- Make changes to the following Fibre controller options as required by your product and configuration:
- Node Name RetentionDefault=Enabled. This option disables/enables a failed controller's node name to be retained through a controller failure. When disabled, each controller shares its node name with its partner controller through failover; however, when failback occurs, the replacement controller uses its own node name. When enabled, each controller shares its node name with its partner controller and those names are used through all phases of failover and failback. A controller reset is required when making changes to this controller option.
- PCI Latency ControlDefault=Short. This function allows adjustment of the Fibre Channel chip's use of the PCI bus. This function controls the amount of data each processor can burst across the primary bus before relinquishing bus ownership to the next device. PCI Latency Control takes effect only when both ports are active and are arbitrating for the bus. PCI Latency Control allows the integrator to tune the controller's operating options for specific applications. Possible settings are Long, Medium, and Short; and these can be selected from the drop-down menu. For maximum throughput, Long is recommended and is equivalent to the time necessary to transfer 1024 bytes; Medium is equivalent to 684 bytes, and Short is equivalent to 512 bytes. A controller reset is required when making changes to this controller option.
- Frame ControlDefault=2KB. This option sets the host Fibre Channel data frame size. Possible settings are 512 bytes, 1 KB or 2 KB; and these can be selected from the drop-down menu. A frame size of 2 KB is recommended since it provides the largest packet transfers and the most throughput. A controller reset is required when making changes to this controller option.
- Set Hard Loop IDsDefault=0 and Enabled. This option allows you to enable or disable use of the controller/host port and, if enabled, to define the hard loop ID. Specifying a hard loop ID means that the same ID will always be requested. The valid range for loop IDs is from 0 to 125. A controller reset is required when making changes to this controller option.
- When the Fibre controller options are set appropriately, click OK to make the changes. (Click Revert to revert controller options to factory default values. Click Cancel to discontinue the operation.)
- A controller reset is required when making some controller option changes. Controller options requiring a controller reset are indicated with a popup window when the mouse cursor moves over the controller option. A controller reset is recommended after making any changes to the controller configuration. If a dialog box does NOT appear warning that a controller reset will occur, refer to the Reset command for the controller reset instructions.
The Add Enclosure command allows users to add device enclosures (one or more) to a configured system while the system continues to operate. After the enclosure or enclosures have been added to the system, the Add Enclosure command initiates the SES monitoring process for the added enclosure(s). The user can configure the additional disk drive capacity without rebooting the system through Array Manager.
- Attach the new enclosure(s) to the system, checking for and resolving any ID conflicts. Refer to the appropriate documentation for enclosure installation.
- Power on the new enclosure(s).
- Wait for all the drives to complete the spin-up process.
- Right-click on a controller.
- Click on Add Enclosure only after all disk drives have completed the spin-up process.
- Perform a rescan.
The Download command allows you to download controller firmware or SES firmware. To use the command, right-click the controller. Then select the Download command from the popup menu that comes up. A submenu appears for selecting either of the two download options. For details, see:
 |
Note: Before downloading firmware, be sure to suspend all I/O to the
PowerVault 660F controller.
|
- Select Controller Firmware.
The Download Firmware dialog box appears. The dialog box provides a standard browser for locating the appropriate firmware image file.
- Click Browse to locate the file and enter the path and filename. Information about the selected file displays.
- Verify that the selected file is correct. If the correct image file is not selected, the command is not executed.
- Click Apply to begin the download process. (Click Cancel to discontinue the operation.)
 |
Note: If operating a redundant controller system, both controllers will
receive the firmware simultaneously.
|
Use this function to upgrade enclosure SES firmware as new versions become available. The Dell PowerVault 660F RAID controller supports pass-through commands used to download new SES firmware to the SES Processor. This mechanism allows a host utility to communicate SCSI commands directly with a device that is visible only to the controller. Array Manager allows the user to download new SES firmware to the SES device. The user will be able to download only to the primary SES device associated with the primary controller. The SES Download wizard guides the user through the process.
- Select SES Firmware.
- Read the welcome screen and click Next to continue. (Click Cancel to discontinue the operation.)
The Select Enclosures screen appears.
- Select the enclosures for which you want to download SES firmware. Click Next to continue. (Click Back to return to the previous screen. Click Cancel to discontinue the operation.)
- Click Browse to locate the file and enter the path and filename. Information about the selected file displays.
- Verify that the selected file is correct. If the correct file is not selected, the command is not executed.
- The Completing the SES Download Wizard screen appears. Click Next to continue. (Click Back to return to the previous screen. Click Cancel to discontinue the operation.)
- Click Finish to continue. (Click Back to return to the previous screen. Click Cancel to discontinue the operation.)
Use this function to hold the partner controller in reset and initiate the failover process. If you are planning to use the Expand Capacity or Add Virtual Disk commands, those commands are not available unless you use this command first to hold the partner controller in reset and transfer control to a single controller. After the Expand Capacity or Add Virtual Disk command is completed, you need to use the Enable Partner command to return to a redundant controller configuration with both controllers operating.
 |
Note: Disabling the partner controller forces all I/O to the subsystem
to go through the surviving controller. Any servers connected to the
Fibre Channel fabric may experience an HBA failover (depending on
the fabric configuration) in order to redirect I/O to the surviving
controller.
|
- Right-click on a controller.
- Click on Disable Partner. This command is invoked immediately; no warning or confirmation screen appears. The partner controller is held in reset. The surviving controller operates as a failed-over redundant controller.
Use this function to return the partner controller to full functionality. Enable the partner controller following an Expand Capacity or Add Virtual Disk operation to return the system to a redundant controller configuration.
 |
Note: Enabling the partner controller allows I/O to be processed by
both controllers. For a SAN environment, manual HBA failovers may
be necessary to have servers use the newly enabled controller.
|
- Right-click on the active controller.
- Click on Enable Partner. This command is invoked immediately; no warning or confirmation screen appears. The failback process begins, and the partner controller resumes full functionality.
Use this function to cycle power on the controllers. After creating a new configuration or making changes to controller options, a controller reset is recommended. The controller reset usually occurs without user intervention; however, occasions may arise when resetting the controllers manually is required.
- Right-click on a controller.
- Click on Reset. A warning/confirmation dialog box appears notifying the user that a controller reset will take 30 seconds or longer. The user is asked to confirm this operation.
- Click Yes to continue. (Click No to exit the function.) A warm power cycle occurs immediately on the controllers.
Use this feature to prepare the controller for removal in order to move it to another location. This procedure forces the controller into Conservative Cache mode, flushes the cache, and disconnects the battery.
- Right-click on a controller.
- Click on Disable BBU. A warning/confirmation dialog box appears notifying the user that the controller will be prepared for removal. The Disable BBU procedure flushes the cache, shifts to Conservative Cache mode (if the Conservative Cache Mode controller option is enabled), and electrically disconnects the BBU. The user is asked to confirm this operation.
- Click Yes to continue. (Click No to exit the function.)
Use this function to return the controller to normal operation.
- Right-click on a controller.
- Click on Enable BBU. A warning/confirmation dialog box appears notifying the user that the controller will return to normal operation. The user is asked to confirm this operation.
- Click Yes to continue. (Click No to exit the function.)
Use these menu items to manage the following battery functions:
- Initiate a battery recondition sequence Use the Recondition function to perform a full battery conditioning cycle.
- Cancel a battery recondition cycle Use the Cancel Recondition function to cancel a recondition that is in progress.
- Initiate a battery fast charge Use the Fast Charge function to perform a fast charge on the battery.
- Cancel a fast charge Use the Cancel Fast Charge function to cancel a fast charge that is in progress.
- Change the battery threshold settings Use the Change Low Threshold function to modify the threshold limits.
A full battery recondition cycle consists of discharging and recharging the battery. The recondition cycle must start with a fully charged battery. If the battery needs charging, use the Fast Charge function. Normally the battery is automatically recharged, but in a new system or a system that has been subjected to a power outage, recharging may be necessary and may take several hours.
The recondition cycle must be initiated manually and must complete without an interruption of power. In addition, the operator must not interrupt the cycle by initiating a fast charge or another recondition cycle. If the cycle is interrupted for any reason, the batteries must be recharged and the recondition process must be restarted.
 |
Note: During the reconditioning, write back cache mode will be
disabled. This may slow normal operations. Therefore, schedule this
operation accordingly.
|
- Right-click on a controller.
- Click on C0 Battery or C1 Battery for the battery associated with the selected controller.
- Click on Recondition. The recondition cycle begins immediately and must not be interrupted.
- Right-click on a controller.
- Click on C0 Battery or C1 Battery for the battery associated with the selected controller.
- Click on Cancel Recondition. The recondition cycle is cancelled immediately.
- Right-click on a controller.
- Click on C0 Battery or C1 Battery for the battery associated with the selected controller.
- Click on Fast Charge. The Fast Charge procedure begins immediately. A fast charge also occurs when the controller is powered on.
- Right-click on a controller.
- Click on C0 Battery or C1 Battery for the battery associated with the selected controller.
- Click on Cancel Fast Charge. The Fast Charge procedure is cancelled immediately.
Use this function to modify the power level used to trigger an alarm when the battery power level drops below the set value.
- Right-click on a controller.
- Click on C0 Battery or C1 Battery for the battery associated with the selected controller.
- Click on Change Low Threshold. The Change BBU Low Threshold dialog box appears. The current value is shown.
- Enter the new value. Click OK to make the changes. (Click Cancel to discontinue the operation.)
This command includes the following battery properties information:
- Battery Type The battery pack type. Currently, NiMH is the only battery pack type supported.
- Hardware Revision Version number for the controller. Version numbers are from 0 to 255. The version number used for the first release is 1 for the controller production release.
- Maximum Power The highest level the battery has been charged, expressed as hours or minutes of charge. This value will change as the battery ages and is reconditioned. The older the battery gets, the less charge it can contain.
- Current Power The current power level of the battery, expressed as hours or minutes of charge. This value will change as the battery is discharged or charged.
- % Charge Level The battery's charge level, where 100% means the battery has been charged up to its maximum level.
- Low Threshold This is a preset or modifiable power level used to trigger an alarm when the battery power level drops below the set value. Refer to Change Low Threshold for information on setting this value.
- Threshold Unit The threshold level is expressed in hours or minutes.
This is an informational field describing the current attribute(s), for example, Fast Charge is not active or Recondition is not active.
This field provides a status icon and information about the current state of the battery. A blue check indicates good status, and a red X indicates a problem or poor status.
- Reconditioning This field monitors the reconditioning status and indicates whether the battery has or has not been reconditioned within 30 discharge/charge cycles.
- Reconditioned This field indicates whether or not the battery has been fully discharged before it was charged up. A new battery indicates Never Reconditioned until it has been fully discharged and then charged by the Recondition procedure.
- Power This field indicates the current power value.
This field displays the current status of the battery. Possible values are:
- Ready The battery is functioning normally.
- Degraded The battery has suffered a failure of a component and is operating in a degraded state.
- Failed The battery has suffered a failure of more than one component and is no longer functioning.
 |
Note: If the status value is anything other than Ready, a red X appears
to the left of the status to indicate a situation that requires attention.
|
This command displays the following categories of properties for the controller:
- Model This field displays the controller number and model that is present in the selected slot.
- Firmware Version This field displays the current version of firmware operating on the controller.
- WWName This field displays the World Wide Name (WWN) for this controller.
- Cache Size This field displays the amount of cache memory available on this controller.
- Memory Size This field displays the amount of memory available on this controller.
- Host Ports This field displays the number of host ports available on this controller.
- Drive Channels This field displays the number of device ports or drive channels available on this controller.
- Logical Drives This field displays the number of logical drives or virtual drives created on this controller.
- Physical Devices This field displays the number of physical devices attached to this controller.
- Fault Tolerant This field indicates whether this controller is operating in a fault tolerant configuration or dual-active controller configuration.
- Yes indicates dual-active controller configuration.
- No indicates either single controller configuration or failed-over dual-active controller configuration.
- Partner Status This field indicates the partner controller's status. Possible values are:
- OK The partner controller is functioning normally.
- Failed The partner controller is no longer functioning, and the surviving controller is operating in a failed-over state.
- OS Controller This field displays the controller's identification number assigned by the operating system. This value is based on the number of peripheral devices recognized by the operating system, including controllers and HBAs.
- Channel This field displays the channel number on which this controller is located.
- Target This field displays the target ID for this controller.
- Name This field displays the port name for this controller.
- Port ID This field displays the port ID for this controller.
- This field displays the current status of the controller. Possible values are:
- Ready The controller is functioning normally.
- Degraded The controller has suffered a failure of a component and is operating in a degraded state.
- Failed The controller has suffered a failure of more than one component and is no longer functioning.
 |
Note: If the status value is anything other than Ready, a red X appears
to the left of the status to indicate a situation that requires attention.
|
The Dell PowerVault 660F RAID controller subsystem consists of physical and logical arrays. The physical arrays include two Dell PowerVault 660F RAID controllers, enclosures, disks, fans, power supplies, and temperature probes. The logical arrays include the virtual disks on the controller(s). The logical arrays are created, monitored, and maintained by Array Manager.
Right-clicking a Dell PowerVault 660F RAID controller subsystem object in the tree view brings up a context menu with subsystem commands. Similarly, right-clicking a physical or logical array object also brings up a context menu.
You can perform the following operations from the Subsystem context menu:
The physical array object context menu allows you to:
The logical array object context menu allows you to:
You can scan for newly created virtual disks from the Dell PowerVault 660F RAID controller subsystem context menu. Use the Rescan function to scan the subsystem for newly created virtual disks, physical disk drives, or enclosures.
- Right-click on a subsystem.
- Click on Rescan. This command is invoked immediately; no warning or confirmation screen appears. The added components appear in the left pane.
The Properties command for the Dell PowerVault 660F RAID controller subsystem provides the name, vendor, and status of the subsystem. Possible values for status are:
- Ready The subsystem is functioning normally.
- Degraded The subsystem has suffered a failure of a component and is operating in a degraded state.
- Failed The subsystem has suffered a failure of more than one component and is no longer functioning.
 |
Note: If the status value is anything other than Ready, a red X appears
to the left of the status to indicate a situation that requires attention.
|
The Physical Array Properties dialog box displays the name, vendor, and status of the physical array. Possible values of the status field are:
- Ready The logical array is functioning normally.
- Degraded The logical array has suffered a failure of a component and is operating in a degraded state.
- Failed The logical array has suffered a failure of more than one component and is no longer functioning.
 |
Note: If the status value is anything other than Ready, a red X appears
to the left of the status to indicate a situation that requires attention.
|
The Logical Array Properties dialog box displays the name and status of the logical array. Possible values of the status field are:
- Ready The logical array is functioning normally.
- Degraded The logical array has suffered a failure of a component and is operating in a degraded state.
- Failed The logical array has suffered a failure of more than one component and is no longer functioning.
 |
Note: If the status value is anything other than Ready, a red X appears
to the left of the status to indicate a situation that requires attention.
|
Dell PowerVault 224F enclosures have enclosure management capability. This section describes how enclosure management works and then details the specific enclosure management commands. The specific topics in the section are:
Array Manager allows you to view all the external Fibre Channel system probes within the same integrated Array Manager console. You are notified of any enclosure status changes while the console is open, and logged events appear in the Events tab as well as in the Windows NT/2000 Event Log.
The Fibre Channel subsystem of Array Manager provides direct support for the display of instrumentation of Fibre Channel enclosures. No other software is required to be installed.
The storage objects associated with enclosures and enclosure management are:
When you expand the PowerVault 660 subsystem storage object in the tree view, you will see one or more controllers attached to the subsystem along with one or more enclosures that are attached to each controller. As shown in the sample screen below, an enclosure has Disks, Fans, Power Supplies and Temperature Probes storage objects associated with it.
In the above screen, the enclosure is identified as "Enclosure 0:1." The zero refers to the number of the controller the enclosure is attached to. The "1" means that it is the first enclosure attached to that controller. If there were a second and a third enclosure attached to Controller 0, they would be called "Enclosure 0:2" and "Enclosure 0:3," respectively. If you right-click an Enclosure storage object, you will get a context menu with enclosure commands. For details, see the section Enclosure Commands in this chapter. Also, when an enclosure is selected in the left-pane tree view, the right-pane panel of the console window lists that enclosure along with its operating status and other properties.
In the tree view, the same Enclosure storage objects with their subordinate objects also appear under a section of the tree that is called "Dell Enclosures," which contains a list of all the enclosures attached to the selected computer you are viewing in the Array Manager console.
The subordinate Enclosure storage objectsDisks, Fans, Power Supplies, and Temperature Probesare described in the sections that follow.
The enclosure's array disks are displayed under the Disks storage object. When the Disks storage object is highlighted in the left-pane tree view, the right-pane panel of the console window lists these disks along with their operating status and other properties. If you right-click the Disks storage object or any of its subordinate disks, the Array Disks context menu will come up. See Array Disk Commands for details on these commands.
The enclosure's fans are displayed under the Fans storage object. When the Fans storage object is highlighted in the left-pane tree view, the right-pane panel of the console window lists the enclosure's fans along with their operating status and other properties. If you right-click the Fans storage object, a context menu comes up with a Fan Properties command.
The power supplies that are installed in the enclosure are displayed under the Power Supplies storage object. When the Power Supplies storage object is highlighted in the left-pane tree view, the right-pane panel of the console window lists the enclosure's power supplies along with their operating status and other properties. If you right-click the Power Supplies storage object, a context menu comes up with a Power Supply Properties command.
The temperature probes that are installed in the enclosure are displayed under the Temperature Probes storage object. When the Temperature Probes storage object is highlighted in the left-pane view, all of the enclosure's temperature probes are displayed along with their operating status and other properties. The categories are Status, Current Value, Minimum Warning Limit, Maximum Warning Limit, Minimum Error Limit, Maximum Error Limit, and Unit of Measurement. The unit of measurement will always be degrees Celsius. If you right-click the Temperature Probes storage object, a context menu comes up with two commands, Temperature Properties and Set Thresholds for Temperature. The Set Thresholds for Temperature command displays the enclosure temperature and the thresholds for critical and warning temperature events. It allows you to set the temperature threshold for warning temperature levels.
This section describes the commands associated with the Enclosure storage object and its subordinate storage objects. Right-clicking a Dell PowerVault 224F RAID enclosure in the tree view brings up a context menu with enclosure commands. Under each enclosure are objects in the tree view for fans, power supplies, and temperature. Right-clicking each of these subordinate objects brings up a context menu as well.
The Enclosure context menu commands are:
The context menu commands for fans, power supplies, and temperature are:
Use this function to enable the alarm when the enclosure exceeds a warning threshold for temperature or battery power; when a disk drive, power supply, fan, or controller fails; and during the controller boot-up process. Once the alarm is enabled, the audible alarm sounds whenever the fault LED lights. To invoke the command, right-click the enclosure and select Alarm Enabled from the context menu that appears.
Use this function to disable the alarm. To invoke the command, right-click the enclosure and select Alarm Disabled from the context menu that appears.
The Asset Settings command brings up a dialog box that allows you to enter or change the asset tag and asset name for the enclosure that contains the controllers. To perform the command:
- Right-click on an enclosure.
- Click on Asset Settings.
The Asset Information dialog box appears with two entry boxes, Asset Tag and Asset Name.
- If the values shown need to be changed, enter a new value for the asset tag and a new asset name.
The asset name for the selected enclosure will be added to the controller name in the object tree; for example, Controller 1 (Enclos53), where "Enclos53" is the asset name for the first enclosure attached to Controller 1. The first enclosure attached to a controller is the enclosure in which the pair of redundant controllers are installed.
 |
Note: The asset tag is limited to 10 characters, and the asset name is
limited to 32 characters.
|
- Click Set to make the changes. Click Cancel to exit the function without accepting the changes.
Use this function to view the following information about the selected enclosure:
- Vendor This field displays the enclosure vendor's name.
- Product This field displays the enclosure product number or model number.
- Revision This field displays the current version of the LS module (or SES processor) firmware.
- Enclosure ID This field displays the enclosure ID number, beginning with 1.
- Asset Tag This field displays the enclosure asset number that is determined by the Asset Settings command.
- Asset Name This field displays the enclosure asset name that is determined by the Asset Settings command.
- Service Tag This field displays the enclosure service tag that is established during manufacturing.
- Status This field displays the current status of the enclosure. Possible values are:
- Ready The enclosure is functioning normally.
- Degraded The enclosure has suffered a failure of a component and is operating in a degraded state.
- Failed The enclosure has suffered a failure off more than one component and is no longer functioning.
 |
Note: If the status value is anything other than Ready, a red X appears
to the left of the status to indicate a situation that requires attention.
|
Use this command to view the following fan properties:
- Vendor This field displays the fan vendor or manufacturer name.
- Product This field displays the fan number.
- Enclosure ID This field indicates the ID number of the enclosure where this fan is located.
- Fan Speed This field displays the current fan speed. Possible values are High, Low, and N/A (meaning the fan speed is not available).
- Controller This field indicates the ID number of the controller with which this fan is associated.
- Status This field displays the current status for the fan. Possible values are:
- Ready The fan is operating normally.
- Degraded The enclosure has suffered a failure of a fan component and is operating in a degraded state.
- Failed The fan has failed to operate properly.
 |
Note: If the status value is anything other than Ready, a red X appears
to the left of the status to indicate a situation that requires attention.
|
Use this command to view the following power supply properties:
- Vendor This field displays the power supply vendor or manufacturer name.
- Product This field displays the power supply number.
- Revision This field is not applicable to the power supply properties.
- Enclosure ID This field indicates the ID number of the enclosure where this power supply is located.
- Status This field displays the current status for the power supply. Possible values are:
- Ready The power supply is operating normally.
- Failed The power supply has failed to operate properly.
 |
Note: If the status value is anything other than Ready, a red X appears
to the left of the status to indicate a situation that requires attention.
|
This command displays the enclosure temperature and the thresholds for critical and warning temperature levels. All values are expressed in degrees Celsius. To perform the command:
- Right-click the temperature object in the tree view.
- Select Set Thresholds for Temperature from the context menu that appears.
A dialog box comes up that displays the following temperature-related information:
- Current Temperature This is the current reading for the selected temperature probe.
- Critical Threshold These values are set by the program and cannot be changed.
High or 55 degrees Celsius: This value is the high critical limit. If this value is exceeded, the system will shut down.
Low or 1 degree Celsius: This value is the low critical limit. If this value is exceeded, the system will shut down.
- Warning Thresholds You can set these thresholds. The warning threshold is a general setting that will apply to all temperature probes in the enclosure.
High: When this value is exceeded, a warning alarm sounds, if the alarm is turned on. The upper limit for the high warning threshold is 35 degrees Celsius.
Low: When this value is exceeded, a warning alarm sounds, if the alarm is turned on. The lower limit is 20 degrees Celsius.
- Make any necessary changes to the Warning Threshold values.
 |
Note: Thresholds are set based on room temperature expectations.
The temperatures reported by the subsystem are actual values. The
subsystem automatically adjusts the entered thresholds to account for
internal temperature limitations.
|
- Click OK to make the changes. Click Cancel to discontinue the operation.
Use this command to view the following temperature-related properties:
 |
Note: All values are expressed in degrees Celsius.
|
- Vendor This field displays the temperature probe vendor or manufacturer name.
- Product This field displays the temperature probe number.
- Enclosure ID This field indicates the ID number of the enclosure where this temperature probe is located.
- Current Temperature This is the current reading for the selected temperature probe.
- Critical Thresholds Thresholds set by the program:
- High or 55 degrees Celsius: This value is the high critical limit. If this value is exceeded, the system will shut down.
- Low or 1 degree Celsius: This value is the low critical limit. If this value is exceeded, the system will shut down.
- High: When this value is exceeded, a warning alarm sounds, if the alarm is turned on.
- Low: When this value is exceeded, a warning alarm sounds, if the alarm is turned on.
- Status This field displays the current status of the temperature probe. Possible values are:
- Ready The temperature probe is functioning normally.
- Degraded The temperature probe has suffered a failure of a component and is operating in a degraded state.
- Failed A temperature probe is not present.
 |
Note: Note: If the status value is anything other than Ready, a red X
appears to the left of the status to indicate a situation that requires
attention.
|
The battery of the Dell PowerVault 660F RAID controller preserves the contents of its nonvolatile cache memory in the event of power loss.
The battery provides a minimum of 72 hours protection for DIMMs up to 64 MB and 48 hours protection for 128 MB DIMMs. However, the duration of protection, or holdover time, depends on the battery's charge level.
The battery is fully discharged when you first install the controller. The controller detects this condition and automatically begins charging the battery. This charging process takes approximately six hours. The controller can be used during this time; however, the battery is unable to meet the specified holdover time until the battery is fully charged. The battery is still able to handle brief power losses during the initial charge cycle.
The battery will need to be reconditioned after six months of service. The reconditioning cycle requires a full discharge and recharge of the battery. It ensures that the battery's capacity is being measured correctly and that the battery's full holdover time is maintained.
A full battery recondition cycle consists of discharging and recharging the battery. The recondition cycle must start with a fully charged battery. Normally the battery is automatically recharged, but in a new system or a system that has been subjected to a power outage, recharging may be necessary and may take several hours.
The recondition cycle must be initiated manually and must complete without an interruption of power. In addition, the operator must not interrupt the cycle by initiating a fast charge or another recondition cycle. If the cycle is interrupted for any reason, the batteries must be recharged and the recondition process must be restarted.
- Right-click on a controller.
- Click C0 Battery or C1 Battery.
- Click Recondition.
The reconditioning cycle takes approximately 8 to 10 hours. During this time, the battery's holdover time is reduced to zero (during discharge) and then restored (during full charge). To ensure that no data is lost from nonvolatile cache memory, the controller automatically disables cache (both read and write) during a reconditioning cycle. When the cache is disabled, performance is degraded for the reconditioning period. Once the reconditioning cycle is complete, the cache is restored to its original settings.
It is highly recommended that battery reconditioning be done during off-peak times.
The Advanced BBU (Battery Backup Unit) on the Dell PowerVault 660F RAID controller maintains memory content during an AC power failure. The principal purpose of the BBU is to provide AC power glitch ride-through; however, the BBU is capable of sustaining memory content for an extended period. Using 512 MB of cache memory, the advanced BBU has been shown to sustain memory content for 68 hours under worst-case conditions and 109 hours under typical operating conditions.
The BBU provides protection to data currently stored in the on-board cache memory during intermittent power loss to the controller. This protection is important when write-back cache is enabled and data is waiting to be flushed to the disk drive. A warm start is required in the presence of a BBU that is supplying power to the cache memory and holding data to be flushed to the disk drive as soon as the system is operational. The data will be lost if the controller is removed and a replacement controller is inserted in the removed controller's location. The BBU guarantees memory retention only when the power loss is the result of AC loss or power supply shutdown, and for as long as the batteries remain viable. Memory retention is not guaranteed if power loss is the result of removing the controller from the system while power is supplied to the system.
The battery pack for the advanced BBU can be removed independent of the BBU circuitry. The controller detects the loss of the battery pack and enters into Conservative Cache mode when the battery pack is removed.
The BBU requires a reconditioning cycle before first time use. This reconditioning process may take several hours and cannot be interrupted. Refer to the topic Recondition in this chapter for detailed instructions on performing a BBU recondition.
Back to Contents Page