Controller Object Commands
www.3ware.com
47
3
Use the
/cx add verify
command to create the verify schedule slots you
want (described above.)
4
Use the
/cx set verify=enable
command to enable the schedule (this
enables all rebuild schedule slots). (For details, see page 49.)
5
Use the
/cx/ux set autoverify=on
command to turn on autoverify for each
unit you want to follow the schedule. (For details, see page 59.)
Note:
If you do not enable autoverify for units or start a verification
manually, your verify schedule will not run, even if it is enabled with the
/cx set verify=enable
command.
Warning:
If all time slots are removed, be sure to also disable the
schedule. Otherwise the applicable background task will never
occur.
/cx add selftest=
ddd:hh
This command adds a new background selftest task to be executed on the day
ddd
(where ddd is Sun, Mon, Tue, Wed, Thu, Fri, and Sat), at hour
hh
(range 0 .. 23). Notice that selftest runs to completion and as such no duration
is provided. A maximum of seven selftest tasks can be scheduled. This
command will fail if no (empty) task slot is available.
Example:
//localhost> /c1 add selftest=Sun:16
adds a selftest background task schedule to be executed on Sundays at 16
hours (4:00 PM).
Setting Up a Selftest Schedule
Setting up a selftest schedule requires several steps, and several different CLI
commands in addition to
/cx add selftest.
To set up the selftest schedule you want to use, follow this process:
1
Use the
/cx show selftest
command to display the current schedule for
selftest tasks. (For details, see page 44.)
2
If any of the scheduled tasks do not match your desired schedule, use
the
/cx del selftest
command to remove them. (For details, see page 48.)
3
Use the
/cx add selftest
command to create the selftest schedule slots you
want (described above.)
4
Use the
/cx set selftest=enable
command to enable the schedule (this
enables all selftest schedule slots). (For details, see page 49.)