Use the raid offline command to set a disk drive offline in the switch chassis.

After issuing the command, enter the show chassis diskuse command to verify changes and to view disk status.

disk1 is the drive in Bay 1

disk2 is the drive in Bay 2

This process slows down various internal processes, so we recommend running it on the backup peer in a redundant pair (see redundancy for information on redundant pairs).

The ARX-1500 and ARX-2500 write their metalog data to the RAID, and managed-volume performance is affected if these writes are slowed. Those platforms write all of their metalog data both to the active peer and the backup peer at the same time, so a raid rebuild on the backup peer still affects managed-volume processing on the active peer. For the ARX-1500 and ARX-2500, we recommend performing the rebuild during off hours only. You can use the show metalog usage command to view usage statistics for the metalog driver.

After issuing the command, enter the show chassis diskuse command to verify the change and to view the rebuild progress.

rate (1-99) is the percentage of the systems RAID controller, an internal CPU used for managing access to the internal disks. A higher number ensures a faster rebuild, but slower disk access during the rebuild.

The CLI and the GUI access the internal disks for many operations, as do several processes that create reports. Whenever a raid rebuild occurs, this command determines the division of RAID-controller cycles between these disk-access operations and the RAID-rebuild operation. After issuing the command, enter the show chassis diskuse command to verify changes and to view the rebuild rate.

The RAID subsystem sounds an alarm on disk failure. Use show chassis to find the disk drive that failed. Replace the failed disk as instructed in the ARX®4000 Hardware Installation Guide, the ARX®2000 Hardware Installation Guide, or the instructions that come with the replacement disk.

Use this command to silence the alarm while you replace the drive. Once done, re-enable the alarm with no raid silence.

Use the raid verification-mode command to determine whether or not the RAID verification test runs automatically.

at start every {num days | day-of-week}] (optional) is only available on the ARX-1500 and ARX-2500.

If the verification mode is manual, you can use the raid verification-rate command to determine the CPU cycles used by the verification process. If the verification mode is automatic, the verification rate is set by a system default: on the ARX-1500 and ARX-2500, it runs once at 11PM (see below); on all other chassis types, it runs continuously, every 5 minutes.

Whether or not the verification mode is manual, you can use the raid verify command to run the verification manually.

After issuing the command, you can use the show chassis diskuse command to verify the change.

The ARX-1500 and ARX-2500 write their metalog data to the RAID, and managed-volume performance is affected if these writes are slowed. Constant, automatic RAID verification may have an adverse affect on storage processing for those platforms. For the ARX-1500 and ARX-2500, we recommend using the at option with raid verification-mode automatic, and choose a schedule that runs verifications during slow business hours. If you choose automatic on these platforms, the verification runs daily at 11PM by default.

You can use the show metalog usage command to monitor the internal metalog drivers usage of the RAID.

rate (1-99) is the percentage of the systems RAID-controller resources; the higher the number, the heavier the burden on the RAID controller.

The RAID controller is a separate CPU from the CPUs used for data-plane (network) processing or control-plane processing. This controller is used for the internal disks, and runs when the internal disks are used. The system uses the internal disks for the various copy commands (such as copy ftp) and move commands (such as move ... ftp). This CPU is also required when internal processes write to their log files (see show logs), create reports (see show reports), write packet-capture files (see capture session), collect diagnostic information and put it into a local file, or otherwise write to the internal disks.

You cannot change the default for automatic verification tests. These run continuously on the system; a higher rate would degrade system performance. This command changes the RAID-controller percentage used for manual (user-invoked) verification tests. You can stop the test from running automatically with the raid verification-mode manual command, and then use the raid verify command to manually run the test.

After issuing this command, enter the show chassis diskuse command to verify the change.

This command invokes a verification test for both disks in the RAID. Use the no form of the command, no raid verify, to stop a RAID verification that is currently in progress.

You cannot use this command while another RAID-verify operation is running, and another RAID-verify operation is frequently running when the raid verification-mode command is at its default (automatic). The show chassis diskuse command shows the current mode, manual or automatic. Use raid verification-mode manual to allow manual verification at any time, and guarantee that no RAID-verify process is running in the background. You can also use no raid verify to cancel the current RAID-verify operation, whether it was invoked automatically or manually.

After issuing the command, enter the show chassis diskuse command to view the progress of the test, and its final results. Refer to the Status of the Logical Disk (that is, the full RAID), in the first table of the output. The test takes more than one hour. If the verification fails, you can replace one or both disks as instructed in the ARX®4000 Hardware Installation Guide, the ARX®2000 Hardware Installation Guide, or in the instructions that come with the replacement disk.