Monitoring, Maintenance, and Troubleshooting Features
www.3ware.com 13
3ware CLI (Command Line Interface)
The 3ware CLI provides the functionality available in 3DM through a
Command Line Interface. You can view unit status and version information
and perform maintenance functions such as adding or removing drives, and
reconfiguring RAID units online. You also use it to remotely administer
controllers in a system by first logging into the system.
The 3ware CLI is described in 3ware 9000 Series Serial ATA RAID Controller
CLI Guide.
Monitoring, Maintenance, and
Troubleshooting Features
Several 3ware RAID controller features aid in monitoring and
troubleshooting your drives.
•
SMART Monitoring (Self-Monitoring, Analysis and Reporting
Technology) automatically checks a disk drive's health every 24 hours
and reports potential problems. This allows you to take proactive steps to
prevent impending disk crashes. SMART data is checked on all disk
drives (array members, single disks, and hot spares). Monitoring of
SMART thresholds can be turned on and off in 3DM. (For details, see
“Viewing SMART Data About a Drive” on page 176.)
•
Staggered Spinup allows drives that support this feature to be powered-
up into the standby power management state to minimize in-rush current
at power-up and to allow the controller to sequence the spin-up of drives.
Both SATAII OOB and ATA spin-up methods are supported. The standby
power management state is persistent after power-down and power-up.
You can set the number of drives that will spin up at the same time, and
the time between staggers in 3BM (the 3ware BIOS Management utility).
For details, see “Enabling and Setting Up Staggered Spin-up” on
page 124.
•
Verification and Media Scans. The verify task verifies all redundant
units, and checks for media errors on single disks, spares, JBODS and
RAID 0 unit members. If the disk drive is part of a redundant unit, error
locations that are found and are deemed repairable are rewritten with the
redundant data. This forces the drive firmware to reallocate the error
sectors accordingly.
•
Error Correction. Bad sectors can be dynamically repaired through error
correction (Dynamic Sector Repair). Reallocation of blocks will try to be
based intelligently on the location of the block in relation to the stripe.
•
Scheduled Background Tasks. Initialize, rebuild, verify, and self-test
tasks can all be run in the background, at scheduled times. This lets you
To Next Page
Loading...
