.

User's Guide
Microsemi Adaptec RAID Controller Command Line
Utility
Released
October 2017
Revision History
Issue Issue Date Details of Change
3 October Add Linux/Unix LogFiles for PLAYCONFIG and SAVECONFIG commands; add notes to RESCAN and SAVESUPPORTARCHIVE
2017 command sections; add SETCONTROLLERPARAM command; update GETSMARTSTATS command.
2 September Add UARTLOG CONSOLE command; add PPC Linux and pre-boot plugin installation; add static-linked arcconf installation
2016 for Linux x64.
1 April 2016 Add new commands; TASK uninit ALL; new GETCONFIG component properties; Logical Drive, HDD, and Backup System
Status and Error Conditions.

Microsemi Proprietary and Confidential User's Guide Issue 3 2

Contents

Microsemi Adaptec® Product Support.............................................................................................6

Software License Agreement...........................................................................................................7

1 Getting Started with the Command Line Utility.........................................................................10

1.1 Installing the Command Line Utility............................................................................................................10
1.1.1 Downloading the Installation Packages........................................................................................10
1.1.2 Installing on Windows..................................................................................................................11
1.1.3 Installing on Red Hat, Cent OS, SuSE, or Fedora Linux..................................................................11
1.1.4 Installing on Debian or Ubuntu Linux...........................................................................................11
1.1.5 Installing on Solaris.......................................................................................................................11
1.1.6 Installing on FreeBSD....................................................................................................................12
1.1.7 Installing on VMware....................................................................................................................12
1.1.8 Installing on Citrix XenServer........................................................................................................13
1.1.9 Installing on a Guest Operating System........................................................................................13
1.1.9.1 Installing on a Windows Guest OS..................................................................................13
1.1.9.2 Installing on a Linux Guest OS........................................................................................13
1.1.10 Installing on PowerPC.................................................................................................................14
1.2 Starting the Command Line Utility..............................................................................................................14

2 Using the Command Line Utility................................................................................................15

2.1 ARCCONF Commands.................................................................................................................................15
2.2 arcconf atapassword...................................................................................................................................17
2.3 arcconf backupunit.....................................................................................................................................17
2.4 arcconf consistencycheck...........................................................................................................................18
2.5 arcconf copyback........................................................................................................................................18
2.6 arcconf cpld................................................................................................................................................19
2.7 arcconf create.............................................................................................................................................20
2.8 arcconf delete.............................................................................................................................................22
2.9 arcconf driverupdate..................................................................................................................................23
2.10 arcconf errortunable ................................................................................................................................23
2.11 arcconf expanderlist.................................................................................................................................24
2.12 arcconf expanderupgrade.........................................................................................................................24
2.13 arcconf failover.........................................................................................................................................25
2.14 arcconf getconfig......................................................................................................................................26
2.15 arcconf getexception.................................................................................................................................27
2.16 arcconf getlogs..........................................................................................................................................28
2.17 arcconf getperform...................................................................................................................................29
2.18 arcconf getsmartstats...............................................................................................................................30
2.19 arcconf getstatus.......................................................................................................................................30
2.20 arcconf getversion....................................................................................................................................31
2.21 arcconf identify.........................................................................................................................................31
2.22 arcconf imageupdate................................................................................................................................32
2.23 arcconf key................................................................................................................................................33
2.24 arcconf list.................................................................................................................................................33
2.25 arcconf modify..........................................................................................................................................34
2.26 arcconf phyerrorlog..................................................................................................................................35
2.27 arcconf playconfig.....................................................................................................................................36
2.28 arcconf preservecache..............................................................................................................................37

Microsemi Proprietary and Confidential User's Guide Issue 3 3

2.29 arcconf rescan...........................................................................................................................................38
2.30 arcconf resetstatisticscounters.................................................................................................................38
2.31 arcconf romupdate...................................................................................................................................39
2.32 arcconf saveconfig....................................................................................................................................40
2.33 arcconf savesupportarchive......................................................................................................................40
2.34 arcconf seeprom.......................................................................................................................................41
2.35 arcconf setalarm.......................................................................................................................................42
2.36 arcconf setbiosparams..............................................................................................................................42
2.37 arcconf setboot.........................................................................................................................................43
2.38 arcconf setcache.......................................................................................................................................44
2.39 arcconf setconfig.......................................................................................................................................45
2.40 arcconf setcontrollermode.......................................................................................................................46
2.41 arcconf setcontrollerparam......................................................................................................................47
2.42 arcconf setcustommode...........................................................................................................................48
2.43 arcconf setmaxcache................................................................................................................................49
2.44 arcconf setname.......................................................................................................................................50
2.45 arcconf setncq...........................................................................................................................................51
2.46 arcconf setperform...................................................................................................................................51
2.47 arcconf setphy...........................................................................................................................................52
2.48 arcconf setpower......................................................................................................................................52
2.49 arcconf setpriority.....................................................................................................................................54
2.50 arcconf setstate.........................................................................................................................................54
2.51 arcconf setstatsdatacollection..................................................................................................................56
2.52 arcconf setvmcredential...........................................................................................................................56
2.53 arcconf smp..............................................................................................................................................57
2.54 arcconf task...............................................................................................................................................57
2.55 arcconf uninit............................................................................................................................................59
2.56 arcconf verifywrite ...................................................................................................................................59

Appendix A getconfig Output Summary.......................................................................................61

Appendix B Logical Drive, HDD, and Flash Backup System Status and Error Conditions...............70

Microsemi Proprietary and Confidential User's Guide Issue 3 4

Tables
Table 1 • ARCCONF Batch Environments .................................................................................................................15
Table 2 • ARCCONF Commands ...............................................................................................................................15
Table 3 • getconfig output summary .......................................................................................................................61

Microsemi Proprietary and Confidential User's Guide Issue 3 5

Microsemi Adaptec® Product Support
If you have questions about installing or using your Microsemi Adaptec® product, check this document
first—you will find answers to most of your questions. If you need further assistance, use the support
options listed below. To expedite your service, have your computer in front of you.
Note: Please visit our Support site at start.microsemi.com for the most up to date contact
information.

Self Help and Support in English

• Search the Microsemi Support Knowledgebase (ASK) at ask.microsemi.com for articles,
troubleshooting tips, and frequently asked questions for your product.
• For support through email, submit your question at ask.microsemi.com.
• To contact Technical Support, visit our product support site at start.microsemi.com.

Technische Informationen und Support in Deutsch

• Suchen Sie in der Adaptec Support Knowledgebase (ASK) unter ask-de.microsemi.com nach Artikeln,
Tipps zur Fehlerbehebung und häufig gestellten Fragen zu Ihrem Produkt.
• Support per Email erhalten Sie unter ask-de.microsemi.com.
• Um den Technischen Support zu kontaktieren, besuchen Sie uns bitte unter start.microsemi.com
und klicken Sie auf „Support kontaktieren“, für Auswahlmöglichkeiten.

Техническая поддержка и информация на русском языке

• База знаний Microsemi (ASK) на сайте ask-ru.microsemi.com ask-ru.adaptec.com – статьи, советы
по устранению неисправностей и часто задаваемые вопросы о Вашем продукте.
• Для поддержки по электронной почте отправьте Ваш запрос на сайте ask-ru.microsemi.com
• Для обращения в службу Технической Поддержки, пожалуйста, посетите наш web сайт
start.microsemi.com и используйте ссылку "Contact Support".

日本語での技術情報とサポート
• ask.microsemi.co.jp のMicrosemi Support Knowledgebase (ASK)で、お使いの製品の情報 トラブル
シューティングのヒント、よくある質問を検索してください。
• Eメールでのサポートには ask.microsemi.co.jp から質問を送ってください。
• テクニカルサポートへコンタクトするには、弊社ウェブサイトstart.microsemi.comをご覧になり、"Contact
Support“をクリックして下さい。

Microsemi Proprietary and Confidential User's Guide Issue 3 6

Software License Agreement
PLEASE READ CAREFULLY: THE USE OF THIS SOFTWARE IS SUBJECT TO THE SOFTWARE LICENSE TERMS
OF MICROSEMI CORPORATION, AND OTHER LICENSORS WHOSE SOFTWARE MAY BE BUNDLED WITH
THIS PRODUCT.
BY YOUR USE OF THE SOFTWARE INCLUDED WITH THIS PRODUCT YOU AGREE TO THE LICENSE TERMS
REQUIRED BY THE LICENSOR OF THAT SOFTWARE, AS SET FORTH DURING THE INSTALLATION PROCESS.
IF YOU DO NOT AGREE TO THE LICENSE TERMS APPLICABLE TO THE SOFTWARE, YOU MAY RETURN THE
ENTIRE UNUSED PRODUCT FOR A FULL REFUND.
In return for acquiring a license to use the Microsemi software, which may include software from third
party licensors and patches made available by Microsemi (“Software”), and the related documentation,
you agree to the following terms and conditions:
1. License. This Agreement grants you, the Licensee, a license to:
a. Use the Software on a single computer system, which is not intended for use by more than five
(5) users; and:
b. Make one copy of the Software in machine readable form solely for back-up purposes, provided
you reproduce Microsemi's copyright proprietary legends. Notwithstanding the foregoing, the
Software may be used on the home, laptop or other secondary computer of the principal user
of the Software, and an additional copy of the Software may be made to support such use. As
used in this license, the Software is “in use” when it is either loaded into RAM or installed on a
hard disk or other permanent memory device. The Software may be “in use” on only one computer
at any given time. (Different license terms and fees are applicable for networked or multiple user
applications.) As a specific condition of this license, you agree to use the Software in compliance
with all applicable laws, including copyright laws, and that you will not copy, transmit, perform
or distribute any audio or other content using the Software without obtaining all necessary
licenses or permissions from the owner of the content.

2. Restrictions. You may not distribute copies of the Software to others or electronically transfer the
Software from one computer to another over a network. You may not post or otherwise make
available the Software, or any portion thereof, in any form, on the Internet. You may not use the
Software in a computer service business, including in time sharing applications. The Software contains
trade secrets and, in order to protect them, you may not decompile, reverse engineer, disassemble,
or otherwise reduce the Software to a human-perceivable form. YOU MAY NOT MODIFY, ADAPT,
TRANSLATE, RENT, LEASE, LOAN, RESELL FOR PROFIT, DISTRIBUTE, NETWORK OR CREATE DERIVATIVE
WORKS BASED UPON THE SOFTWARE OR ANY PART THEREOF.
3. Ownership of Software. As Licensee, you own the media upon which the software is recorded or
fixed, but Microsemi and its licensors retain title and ownership of the Software recorded on the
original media and all subsequent copies of the Software, regardless of the form or media in which
or on which the original and other copies may exist. This license is not a sale of the Software or any
copy.
4. Confidentiality. You agree to maintain the Software in confidence and that you will not disclose the
Software to any third party without the express written consent of Microsemi. You further agree to
take all reasonable precautions to preclude access of unauthorized persons to the Software.
5. Term. This license is effective until January 1, 2045, unless terminated earlier. You may terminate
the license at any time by destroying the Software (including the related documentation) together
with all copies or modifications in any form. Microsemi will have the right to terminate our license
immediately if you fail to comply with any term or condition of this Agreement. Upon any termination,
including termination by you, you must destroy the Software (including the related documentation),
together with all copies or modifications in any form.

Microsemi Proprietary and Confidential User's Guide Issue 3 7

6. Special Terms Applicable to Databases. Where a database is included with the Software, you
acknowledge that it is licensed only in connection with the use of the Software to perform disc
creation, and that the database and all data derived therefrom must be maintained in confidence
in accordance with the provisions of Section 4. This license does not grant you any rights to distribute
or disclose such database or data.
7. Limited Warranty. Microsemi and its Licensor warrant only that the media upon which the Software
is furnished will be free from defects in material or workmanship under normal use and service for
a period of thirty (30) days from the date of delivery to you. MICROSEMI AND ITS LICENSORS DO
NOT AND CANNOT WARRANT THE PERFORMANCE OR RESULTS YOU MAY OBTAIN BY USING THE
SOFTWARE OR DOCUMENTATION. THE FOREGOING STATES THE SOLE AND EXCLUSIVE REMEDIES
MICROSEMI AND ITS LICENSORS WILL PROVIDE FOR BREACH OF WARRANTY. EXCEPT FOR THE
FOREGOING LIMITED WARRANTY, MICROSEMI AND ITS LICENSORS MAKE NO WARRANTIES,
EXPRESSED OR IMPLIED, INCLUDING, BUT NOT LIMITED, AS TO NON-INFRINGEMENT OF THIRD PARTY
RIGHTS, MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE. Some states do not allow the
exclusion of implied warranties or limitations on how long an implied warranty may last, so the
above limitations may not apply to you. This warranty gives you specific legal rights and you may
also have other rights which vary from state to state.
8. The entire liability of Microsemi and its licensors, and your exclusive remedy for a breach of this
warranty, shall be:
a. The replacement of any media not meeting the above limited warranty which is returned to
Microsemi; or:
b. if Microsemi or its distributor is unable to deliver replacement media which is free from defects
in materials or workmanship, you may terminate this Agreement by returning the Software and
your money will be refunded.

9. Limitation of Liability. IN NO EVENT WILL MICROSEMI OR ITS LICENSORS BE LIABLE TO YOU FOR ANY
INCIDENTAL, CONSEQUENTIAL OR INDIRECT DAMAGES, INCLUDING ANY LOST PROFITS, LOST SAVINGS,
OR LOSS OF DATA, EVEN IF MICROSEMI OR A LICENSOR HAS BEEN ADVISED OF THE POSSIBILITY OF
SUCH DAMAGES, OR FOR ANY CLAIM BY ANY OTHER PARTY. Some states do not allow the exclusion
or limitation of special, incidental, or consequential damages, so the above limitation or exclusion
may not apply to you.
10. Export. You acknowledge that the laws and regulations of the United States and other countries
may restrict the export and re-export of the Software. You agree that you will not export or re-export
the Software or documentation in any form in violation of applicable United States and foreign law.
11. Government Restricted Rights. The Software is subject to restricted rights as follows. If the Software
is acquired under the terms of a GSA contract: use, reproduction or disclosure is subject to the
restrictions set forth in the applicable ADP Schedule contract. If the Software is acquired under the
terms of a DoD or civilian agency contract, use, duplication or disclosure by the Government is subject
to the restrictions of this Agreement in accordance with 48 C.F.R. 12.212 of the Federal Acquisition
Regulations and its successors and 49 C.F.R. 227.7202-1 of the DoD FAR Supplement and its successors.
12. General. You acknowledge that you have read this Agreement, understand it, and that by using the
Software you agree to be bound by its terms and conditions. You further agree that it is the complete
and exclusive statement of the agreement between Microsemi and you, and supersedes any proposal
or prior agreement, oral or written, and any other communication between Microsemi and you
relating to the subject matter of this Agreement. No additional or any different terms will be
enforceable against Microsemi unless Microsemi gives its express consent, including an express
waiver of the terms of this Agreement, in writing signed by an officer of Microsemi. You assume full
responsibility for the use of the Software and agree to use the Software legally and responsibly. This
Agreement shall be governed by California law, except as to copyright matters, which are covered
by Federal law. This Agreement is deemed entered into at Sunnyvale, California by both parties.
Should any provision of this Agreement be declared unenforceable in any jurisdiction, then such

Microsemi Proprietary and Confidential User's Guide Issue 3 8

provision shall be deemed severable from this Agreement and shall not affect the remainder hereof.
All rights in the Software not specifically granted in this Agreement are reserved by Microsemi.
Should you have any questions concerning this license, contact:
Microsemi Corporation
Legal Department
One Enterprise
Aliso Viejo, CA 92656
(949) 380-6100

Microsemi Proprietary and Confidential User's Guide Issue 3 9

Getting Started with the Command Line Utility

1 Getting Started with the Command Line Utility

This chapter explains how your Microsemi® Adaptec® RAID controllers support the use of the ARCCONF
command line utility.
This chapter explains how your Microsemi SmartHBA-SA controller supports the use of the ARCCONF
command line utility.
This utility allows you to:
• Create and delete logical drives
• Display and modify configuration settings
• Copy configurations from one computer to another
• Recover from a failed physical device and rebuild an affected logical drive
• Flash new firmware and BIOS onto the controller
• Enable the controller to check the removal and connection of any disk drives
• Provides access to the status and event logs of a controller
• Isolate problems and determine their causes

1.1 Installing the Command Line Utility

You can install ARCCONF with the Microsemi Adaptec maxView Storage Manager application. If you
prefer to install just the command line utility, without installing the maxView Storage Manager GUI, you
can install just the ARCCONF executable for your operating system.
Follow the instructions in this section to install ARCCONF on the supported operating systems with
maxView Storage Manager. (For more information about maxView Storage Manager, see the maxView
Storage Manager User's Guide.)
Follow the instructions in this section to install ARCCONF on the supported operating systems.
Note: On FreeBSD systems, you must use ARCCONF to perform storage management tasks.
FreeBSD does not support the maxView Storage Manager GUI. For more information, see
Downloading the Installation Packages and Installing on FreeBSD on page 12.
1.1.1 Downloading the Installation Packages
Complete these steps to download the installation package for your operating system(s):
1. Open a browser window, then type start.adaptec.com in the address bar.
2. Select your RAID controller family (Series 7, Series 8, and so on) and controller model.
3. Select Storage Manager Downloads, then select the appropriate installer package from the list; for
instance, maxView Storage Manager for Windows x64 or maxView Storage Manager for Linux.
Note: To install ARCCONF without the GUI, select Adaptec ARCCONF Command Line Utility
from the list of installers. This package includes the ARCCONF executable for Windows, Linux,
Solaris, and FreeBSD. It also includes a statically-linked ARCCONF executable, which allows
you to run the program without any OS library dependencies.

4. Click Download Now and accept the license agreement.

5. When the download completes, extract the contents of the installer archive file to a temporary
location. If the archive includes installers for multiple operating system versions (VMware, for
instance), each installer is stored in a separate folder.
Note: If you are installing maxView Storage Manager and ARCCONF on a different machine ̶
for instance, you downloaded the Linux installer onto a Windows machine ̶ copy the installer
from the download location to a temporary location on the target machine. Use whatever
method you prefer to copy the file: USB flash drive; network transfer; Telnet/SSH; whatever
is most convenient.

Microsemi Proprietary and Confidential User's Guide Issue 3 10

Getting Started with the Command Line Utility

6. Continue with the installation instructions for your operating system.

1.1.2 Installing on Windows

To install ARCCONF on Windows systems:
1. Open Windows Explorer or My Computer, then change to the directory where the Windows setup
program is located (see Downloading the Installation Packages on page 10 for details).
2. Double-click the setup program for your operating system version:
Options Description
Windows 64-bit setup_asm_x64.exe
The Installation wizard opens.
3. Click Next to begin the installation, click I accept..., then click Next.
4. Add the following configuration settings:
a) CIM Server Port: 5988.
b) Web Server Port: 8443.
5. Click OK on the password verification window and on the CIM Server and Web Server port number
verification window.
6. In the Features window, select GUI, Agent, and CLI Tools. Then click Next.
7. Follow the on-screen instructions to complete the installation.

1.1.3 Installing on Red Hat, Cent OS, SuSE, or Fedora Linux

To install ARCCONF on Red Hat, Cent OS, SuSE, or Fedora Linux:
1. In a shell window, change to the directory where the Linux installer package is located (see
Downloading the Installer Package for details).
2. Run the .bin file for your operating system version (where xxxxx=build number):
Options Description
Linux 64-bit ./StorMan-2.02-xxxxx.x86_64.bin
3. When prompted for configuration details, enter the following:
Enter the CIM Server HTTP Port: [default:5988]
When the installation completes a confirmation message is displayed.

1.1.4 Installing on Debian or Ubuntu Linux

To install ARCCONF on Debian or Ubuntu Linux:
1. In a shell window, change to the directory where the Debian or Ubuntu installer package is located
(see Downloading the Installation Packages on page 10 for details).
2. Install the .deb package for your operating system version (where xxxxx=build number):
Options Description
Linux 64-bit dpkg -i StorMan-2.02-xxxxx_amd64.deb
3. Enter the following configuration details:
Enter the CIM Server HTTP Port: [default:5988].
When the installation completes a confirmation message is displayed.

1.1.5 Installing on Solaris

To install ARCCONF on Solaris:
1. On the Solaris machine, change to the directory where the Solaris installer package is located (see
Downloading the Installer Package for details).

Microsemi Proprietary and Confidential User's Guide Issue 3 11

Getting Started with the Command Line Utility

2. Install maxView Storage Manager:

pkgadd -d StorMan.pkg
3. At the prompt to continue, select y, then press Enter.
4. Enter the following configuration details:
Enter your username [default: root].
Enter your operating system password.
Enter the CIM Server HTTP Port: [default:5988].
When the installation completes a confirmation message is displayed.

1.1.6 Installing on FreeBSD

To install ARCCONF on FreeBSD:
1. Copy the arcconf executable from the original download location to your FreeBSD system (see
Downloading the Installer Package for details).
2. Verify that the file has 'execute' privilege.

1.1.7 Installing on VMware

Use the following procedure to install the .vib files for VMware ESXi 5.5 or VMware ESXi 6.0. Perform
the installation from a remote system running a Telnet/SSH client. Use a terminal emulator to access
the ESXi server remotely.
1. Copy the following files from the installer download location to the /tmp directory on your local
ESXi server (see Downloading the Installation Packages on page 10 for details):
• vmware-esx-provider-arcconf.vib
• vmware-esx-provider-arcsmis.vib
The arcconf.vib is for command line communication.
The arcsmis.vib is for remote management communication.
2. Check for existing installation of arcconf.
esxcli software vib list | grep arcconf
3. Remove the existing arcconf package.
esxcli software vib remove -n arcconf
When the package is removed, you receive the message "Reboot Required: false."
4. Check for an existing installation of arc-cim-provider.
esxcli software vib list | grep arc-cim-provider
5. Remove the existing arc-cim-provider package.
esxcli software vib remove -n arc-cim-provider
When the package is removed, you receive the message "Reboot Required: true."
6. Set the installation acceptance level to either PartnerSupported or CommunitySupported:
esxcli software acceptance set –-level=PartnerSupported
7. Install the arcconf package.
esxcli software vib install --no-sig-check -v
/tmp/vmware-esx-provider-arcconf.vib
When the package is installed, you receive the message "Reboot Required: false."
8. Install the arc-cim-provider package.
esxcli software vib install --no-sig-check -v
/tmp/vmware-esx-provider-arc-cim-provider.vib
When the package is installed, you receive the message "Reboot Required: true."
9. Reboot the system.
10. Continue the installation with Installing on a Guest Operating System on page 13.

Microsemi Proprietary and Confidential User's Guide Issue 3 12

Getting Started with the Command Line Utility

1.1.8 Installing on Citrix XenServer

Use the following procedure to install the maxView Storage Manager support package on a Citrix
XenServer host. This package installs and configures all the components necessary to run maxView
Storage Manager and ARCCONF from a XenServer guest operating system.
Note: Before installing the maxView support package on the XenServer host, you must install the
XenServer Integration Suite Supplemental Pack. Do not continue until you complete this task. See
your XenServer installation guide for details.
1. Copy the XenServer module rpm from the installer download location to your XenServer /tmp
directory (see Downloading the Installer Package for details).
2. Install the rpm package for your operating system version (xxxxx=build number).
Options Description
XenServer 64-bit rpm -i StorMan-2.02-xxxxx_amd64.rpm
3. Continue with Installing on a Guest Operating System on page 13.

1.1.9 Installing on a Guest Operating System

This section describes how to install ARCCONF on a VMware or Citrix XenServer guest operating system.
1.1.9.1 Installing on a Windows Guest OS
To install ARCCONF on a Windows Guest OS running on VMware or Citrix XenServer:
1. On the VMware or XenServer guest OS, change to the directory where the Guest OS installer package
is located (see Downloading the Installer Package for details).
2. Double-click the setup program for your operating system:
Options Description
Windows GOS 64- setup_maxview_gos_x64.exe
bit
The Installation wizard opens.
3. Choose the hypervisor type (ESXi Server or XenServer), then click Next.
4. Enter the following configuration details:
a) Host IP Address (ESXi or XenServer host)
b) Web Server Port: 8443
c) ESXi or XenServer Host user name (default: root)
d) ESXi or XenServer Host operating system password/password confirmation
5. Click Next, then click Install.

When the installation is complete you receive a confirmation message.

1.1.9.2 Installing on a Linux Guest OS

To install ARCCONF on a Linux Guest OS running on VMware or Citrix XenServer:
1. On the VMware or XenServer Guest OS, change to the directory where the Linux installer package
is located (see Downloading the Installer Package for details).
2. Run the installer for your operating system version.
Options Description
Linux GOS 64-bit ./Storman-2.02.GOS86_64.bin
3. At the prompt, choose the GOS type. Enter 1 for ESXi, 2 for XenServer:
Select the GOS Type. 1.ESXi Server 2.XenServer:
4. Enter the following configuration details:
Hypervisor IP address

Microsemi Proprietary and Confidential User's Guide Issue 3 13

Getting Started with the Command Line Utility

Hypervisor username [default: root]

Hypervisor password
Event Listener Port [default: 65500]

When the installation is complete you receive a confirmation message.

1.1.10 Installing on PowerPC

• Installing ARCCONF on PowerPC:
• Installing on RHEL PowerPC 64-bit
rpm -i Arcconf-2.02-xxxxx.ppc64le.rpm

• Installing on Ubuntu PowerPC 64-bit

dpkg -i Arcconf-2.02-xxxxx.ppc64el.deb

• Installing on SLES PowerPC 64-bit

rpm -i Arcconf-2.02-xxxxx.ppc64le.rpm

• Installing ARCCONF in Petitboot:

• Extract package arcconf-2.02-xxxxx.tar.xz in the folder of your choice.

Where xxxxx is the installer version.

1.2 Starting the Command Line Utility
1. To start ARCCONF, enter one of the following commands:
Options Description
Windows <install_dir>\arcconf.exe

Linux /usr/<install_dir>/arcconf /<install_dir>/arcconf

Solaris /opt/StorMan/arcconf

FreeBSD /<install_dir>/arcconf

VMware /usr/StorMan/arcconf
VMware ESXi with /usr/RemoteArcconf/arcconf
Remote ARCCONF
XenServer /usr/StorMan/arcconf
where Install_dir is the directory where the utility is installed.
2. To see a list of available commands, type ARCCONF at the prompt. For help with a specific command,
type ARCCONF <command_name> help.

Microsemi Proprietary and Confidential User's Guide Issue 3 14

Using the Command Line Utility

2 Using the Command Line Utility

This chapter explains how to use the command line utility interactively or in batch mode. With interactive
mode, enter commands at the prompt. In batch mode, create scripts and run the script in the appropriate
shell, as described in the table below.
Table 1 • ARCCONF Batch Environments
Environment Batch File Run Script
Windows .bat CMD.EXE
Linux/Unix .sh sh / bash

In either mode, if your command fails, you immediately see an error message of Command failed. Other
script messages that you can get are Command completed successfully, or Command aborted.
The return values for each command are the same:

0x00: SUCCESS

0x01: FAILURE - The requested command failed

0x02: ABORT - The command was aborted because parameters failed

validation

0x03: INVALID_ARGUMENTS - The arguments are incorrect. (Displays COMMAND

help)
To view a list of commands at the command line, type ARCCONF and press Enter.
To access the online help for a specific command, type ARCCONF <command>, then press Enter.

2.1 ARCCONF Commands

The following commands are available in ARCCONF. The commands are described on the following
pages, in alphabetical order.
Table 2 • ARCCONF Commands
atapassword getlogs resetstatisticscounters setncq
backupunit getperform romupdate setperform
consistencycheck getsmartstats saveconfig setphy
copyback getstatus savesupportarchive setpower
cpld getversion seeprom setpriority
create identify setalarm setstate
delete imageupdate setbiosparams setstatsdatacollection
driverupdate key setboot setvmcredential
errortunable list setcache task
expanderlist modify setconfig uninit
expanderupgrade phyerrorlog setcontrollermode verifywrite
failover playconfig setcontrollerparam
getconfig preservecache setcustommode
getexception rescan setmaxcache
setname

Microsemi Proprietary and Confidential User's Guide Issue 3 15

Using the Command Line Utility

Note: In the command syntax descriptions, <> indicates a required parameter and [] indicates an
optional parameter.

Microsemi Proprietary and Confidential User's Guide Issue 3 16

Using the Command Line Utility

2.2 arcconf atapassword

Description
Sets or clears the drive's password for SATA drives. See arcconf task for more information about Secure
Erase.

Syntax
ARCCONF ATAPASSWORD <Controller#> SET <new password> <Channel# ID#> ...
ARCCONF ATAPASSWORD <Controller#> CLEAR <current password> <Channel# ID#> ...

Parameters
new password | current password
New password, current password.
Channel/ID
Lists the space-delimited channel number and device number (ID) pairs for each drive on which to set
or clear the password.

Examples

ARCCONF ATAPASSWORD 1 SET uR8ryx 0 1

ARCCONF ATAPASSWORD 1 CLEAR uR8ryx 0 1

2.3 arcconf backupunit

Description
Resets the hard error flag on the AFM-700 Flash Backup module, and erases the lifetime calculation
records. A hard error disables the backup module permanently, across power cycles, until the hard error
flag is cleared. The error flag is set when any of the following events occur:
• Initialization failure
• Backup failure due to an uncorrectable ECC error
• Backup failure due to a lack of good blocks in the AFM Flash
• Backup failure due to bad meta-data
• Backup failure due to a hardware failure
• Restore failure due to an uncorrectable ECC error
• Restore failure due to a DMA timeout
• Restore failure due to a hardware failure
• AFM Flash erase failure of the meta-data
• AFM Flash erase failure due to a hardware failure
Note: A reboot is necessary for change to take effect.

Syntax
ARCCONF BACKUPUNIT <Controller#> reset

Parameters
Controller#
The controller number.

Microsemi Proprietary and Confidential User's Guide Issue 3 17

Using the Command Line Utility

Examples
ARCCONF BACKUPUNIT 1 reset

2.4 arcconf consistencycheck

Description
Toggles the background consistency check modes of the controller.

Syntax
ARCCONF CONSISTENCYCHECK <Controller#> <on|off|period <DAYS>> [noprompt]
ARCCONF CONSISTENCYCHECK <Controller#> <on [Delay]|off> [noprompt]
ARCCONF CONSISTENCYCHECK <Controller#> PARALLELCOUNT <Count>

Parameters
Controller#
Controller number.
On [Delay] | Off
Turns background consistency check on, with optional 1-30 second delay period. The delay period
sets the controller idle time, after which the consistency check will start. A value of 0 disables the
consistency check (effectively, the same as setting the parameter to Off). If Delay is unspecified, the
consistency check mode is set to HIGH. If Delay is specified, the consistency check mode is set to IDLE,
for specified period.
On | Off
Turns background consistency check on or off. A value of 0 disables the consistency check (effectively,
the same as setting the parameter to Off).
Period <DAYS>
Sets the number of days to complete the background consistency check. The minimum value is 10
days (quick), the maximum is 365 days (slow). Setting the period automatically turns background
consistency check on.
PARALLELCOUNT <Count>
Sets the parallel surface scan count for the controller. A value of 1 disables the consistency check.
Noprompt
Optional parameter that suppresses the confirmation prompt.

Examples
ARCCONF CONSISTENCYCHECK 1 PERIOD 30
ARCCONF CONSISTENCYCHECK 1 ON 20
ARCCONF CONSISTENCYCHECK 1 OFF
ARCCONF CONSISTENCYCHECK 1 PARALLELCOUNT 4

2.5 arcconf copyback

Description
Enables or disables the copyback feature, which attempts to keep drives in the original slot order after
rebuilds.

Microsemi Proprietary and Confidential User's Guide Issue 3 18

Using the Command Line Utility

Syntax
ARCCONF COPYBACK <Controller#> <ON|OFF>

Parameters
Controller#
The controller number
On enables the copyback feature
Off disables the copyback feature

Examples

ARCCONF COPYBACK 1 ON

2.6 arcconf cpld

Description
Updates the CPLD image from flash.

Syntax
ARCCONF CPLD <Controller#> FLASHUPDATE [noprompt] [nologs]
ARCCONF CPLD <Controller#> FORCERELOAD [noprompt] [nologs]

Parameters
Controller#
The controller number.
FLASHUPDATE
Updates the CPLD image from flash.
FORCERELOAD
Forces the CPLD image to reload.
Noprompt
Optional parameter that suppresses confirmation prompt.
Nologs
Optional parameter that suppresses logging of warning/error messages.

Examples

ARCCONF CPLD 1 FLASHUPDATE

Microsemi Proprietary and Confidential User's Guide Issue 3 19

Using the Command Line Utility

2.7 arcconf create

Description
Creates a new logical drive, maxCache Device, or JBOD and, optionally, enables logical drive read caching,
write caching, and maxCache SSD caching. You must provide the channel and device ID of the physical
devices.
On redundant logical drives, ARCCONF performs autosynchronization.
ARCCONF presents JBODs as physical devices, not logical drives.

Syntax
ARCCONF CREATE <Controller#> <LOGICALDRIVE|MAXCACHE> [Options] <Size> <RAID#>
<CHANNEL# DRIVE#> [CHANNEL# DRIVE#] ... [noprompt] [nologs]
ARCCONF CREATE <Controller#> LOGICALDRIVE RVOLUME <LD#> <LD#> [LD#] ...
[noprompt] [nologs]
ARCCONF CREATE <Controller#> JBOD <CHANNEL# DRIVE#> [CHANNEL# DRIVE#] ...
[noprompt] [nologs]
ARCCONF CREATE <Controller#> LOGICALDRIVE [Options] <Size> <RAID#> <CHANNEL#
DRIVE#> [CHANNEL# DRIVE#] ... [noprompt] [nologs]
ARCCONF CREATE <Controller#> LOGICALDRIVE [Options] <Size> <RAID#> ARRAY
<Array#> [noprompt] [nologs]

Syntax
ARCCONF CREATE <Controller#> LOGICALDRIVE [Options] <Size> <RAID#> <CHANNEL#
DRIVE#> [CHANNEL# DRIVE#] ... [noprompt] [nologs]
ARCCONF CREATE <Controller#> LOGICALDRIVE RVOLUME <LD#> <LD#> [LD#] ...
[noprompt] [nologs]
ARCCONF CREATE <Controller#> JBOD <CHANNEL# DRIVE#> [CHANNEL# DRIVE#] ...
[noprompt] [nologs]

Parameters
Controller#
The controller number.
Logical Drive, maxCache
Indicates a logical drive or maxCache Device, with the following options:
• Stripesize <STRIPE>—Allows the logical drive stripe size to be built. Optional parameters for
specifying a stripe size. STRIPE is specified in kilobytes 8, 16, 32, 64, 128, 256, 512 and 1024 are
supported. The default is 256KB.
• Legs <LEG>—Optional parameters for specifying number of legs. Value is an integer.
• LEG—Number of legs for RAID level 50 or 60.
• RAID 50—2-16 legs, 3-32 drives/leg, 128 drives max.
• RAID 60—2-16 legs, 4-16 drives/leg, 128 drives max.
• Name <NAME>—Optional parameter for specifying the alias name of a logical device that is
displayed in the utilities. Value is a string of up to 16 characters.
• Priority <PRIORITY>—Initialization Priority for logical drive to be created. Valid options are: HIGH,
MED, or LOW.
• Method <METHOD>—Initialization method for the logical drive. Valid options include: BUILD,
CLEAR, QUICK, SKIP DEFAULT. Use SKIP for recovery only (to skip the initialization step).
• LDcache—Sets the cache state for the logical drive:
• LON - cache on
• LOFF - cache off

Microsemi Proprietary and Confidential User's Guide Issue 3 20

Using the Command Line Utility

• VerifyWithOS <True | False>—(Windows only) Wait for logical devices to be exposed to Windows
OS:
• True - wait for the logical device to be exposed to the OS
• False - do not wait for the logical device to be exposed to the OS
• Rcache—Sets the logical drive read cache mode:
• RON - read cache on
• ROFF - read cache off
• Wcache—Sets the logical drive write cache mode:
• WT - write-through disabled
• WB - write-back enabled
• WBB - write-back enabled (when protected by battery or flash backup module)

• MaxCacheReadCache—Sets the logical drive SSD read cache mode:

• ION - maxCache on
• IOFF - maxCache off
• MaxCacheWriteCache—Sets the logical drive SSD write cache mode:
• ION - maxCache on
• IOFF - maxCache off
• MaxCacheWritePolicy—Sets the maxCache write cache policy:
• WB - write back enabled. maxCache will store the data on the SSD and write it back to the
hard disks when there is little or no impact on performance. This is the default policy.
• INSTWB - instant write back enabled. In addition to the default policy, maxCache will create
“dirty pages” on-the-fly for full-stripe writes if there is room on the SSD and the number of
dirty pages is below the threshold.
• WT - write through enabled. Similar to instant write back, but full-stripe writes go to both
the cache and hard disk and no dirty pages are created on-the-fly.
This argument is valid only if MaxCacheWriteCache is ION.
Note: For more information about write cache policy, see arcconf setmaxcache on page
49.

Array <Array#>
Array number on which to create the logical drive, with the following options:
• Sectors <sectors> - Sectors per track of the logical device. Valid options are 32 and 63.
• SSDSmartPath <enable | disable> - Enables or disables logical device acceleration. Default is
enabled.
• SSDOverProvisioningOptimization <enable | disable> - Initializes solid state drives that support
the rapid parity initialization feature.
Size
Indicates the size of the logical drive in megabytes. Use MAX to set size to available space. Use MAXMBR
to set the size to 2TB.
RAID#
Indicates the RAID level for the new logical drive: 0, 1, 1E, 10, 5, 5EE, 50, 6, 60, and volume are
supported. For maxCache, 0, 1, 1E, 5 and Simple_Volume are supported. 0, 1, 10 and 5 are supported.
Note: For a complete list of supported RAID levels for your controller, refer to the product
release notes.
Channel# Drive#
Lists the space-delimited channel number and device number pairs for each device to add to the logical
drive or maxCache Device. For maxCache, the devices must be SSDs.
Rvolume
RAID level for a RAID volume logical drive.
LD#
Logical drive numbers for two or more logical drives to be concatenated into the RAID volume. RAID
levels 0, 1, and 5 are supported for RVOLUME members. All RVOLUME members must be the same
RAID level.
Noprompt
No prompt for confirmation

Microsemi Proprietary and Confidential User's Guide Issue 3 21

Using the Command Line Utility

Examples
ARCCONF CREATE 1 LOGICALDRIVE STRIPESIZE 64 MAX 0 1 0 2 0 3 2 NOPROMPT
ARCCONF CREATE 1 JBOD 0 1 NOPROMPT
ARCCONF CREATE 1 LOGICALDRIVE ssdsmartpath enable ssdoverprovisioningoptimization enable
1024 0 ARRAY 0

2.8 arcconf delete

Description
Deletes a logical drive, JBOD, or maxCache logical device or array. All data stored on the logical drive or
JBOD will be lost. Spanned drives cannot be deleted with this function.

Syntax
ARCCONF DELETE <Controller#> LOGICALDRIVE <LD#> <LD#> ...|ALL
[PRESERVEPARTITION] [noprompt] [nologs]
ARCCONF DELETE <Controller#> JBOD <CHANNEL# DRIVE#> [CHANNEL# DRIVE#] ...
[nologs]
ARCCONF DELETE <Controller#> JBOD ALL [noprompt]
ARCCONF DELETE <Controller#> MAXCACHE

Syntax
ARCCONF DELETE <Controller#> LOGICALDRIVE <LD#> <LD#> ...|ALL [noprompt]
[nologs]
ARCCONF DELETE <Controller#> ARRAY <arr#> [noprompt] [nologs]
ARCCONF DELETE <Controller#> ARRAY ALL [noprompt] [nologs]

Syntax
ARCCONF DELETE <Controller#> LOGICALDRIVE <LogicalDrive#> <LD#> <LD#> [noprompt]
ARCCONF DELETE <Controller#> JBOD <CHANNEL# DRIVE#> [CHANNEL# DRIVE#] ...
[noprompt]
ARCCONF DELETE <Controller#> LOGICALDRIVE|JBOD ALL [noprompt]

Parameters
Controller#
Controller# is the controller number
LD#
LogicalDrive# is the number of the logical drive to be deleted.
arr#
arr# is the number of the array to be deleted.
PRESERVEPARTITION
Deletes logical drives without partitions. Applicable ONLY for ALL or multiple LD#.
LogicalDrive|JBOD ALL
Deletes all logical drives or JBODs.
MAXCACHE
Deletes the maxCache Device.
Noprompt
Optional parameter that suppresses alert messages.

Microsemi Proprietary and Confidential User's Guide Issue 3 22

Using the Command Line Utility

Examples
ARCCONF DELETE 1 LOGICALDRIVE 1 2 3
ARCCONF DELETE 1 LOGICALDRIVE 0 1 PRESERVEPARTITION
ARCCONF DELETE 1 JBOD ALL
ARCCONF DELETE 1 ARRAY 0
ARCCONF DELETE 1 ARRAY ALL

2.9 arcconf driverupdate

Description
Updates the Windows device driver for the controller.
Note: This command is available on Windows systems only.

Syntax
ARCCONF DRIVERUPDATE <DirName> [nologs]

Parameters
DirName
Absolute path to directory containing the Windows driver.
Nologs
Optional parameter that suppresses log output.

Examples

ARCCONF DRIVERUPDATE C:\WINDOWSALL

2.10 arcconf errortunable

Description
Sets the tunable error profile for the controller. Contact Microsemi Adaptec Support for more information
about using this command to set up a tunable error profile.

Syntax
ARCCONF ERRORTUNABLE <Controller#> SETPROFILE <Profile#>
ARCCONF ERRORTUNABLE <Controller#> GETPARAMS [Profile#] [SAVE [filename]]
[noprompt]
ARCCONF ERRORTUNABLE <Controller#> CONFIGPARAMS FILE [filename]
ARCCONF ERRORTUNABLE <Controller#> CONFIGPARAMS <Param1> <Value1> [Param2]
[Value2] ...

Parameters
Controller#
Controller number
GETPARAMS
Returns the parameters for the current profile on the controller.
Profile#

Microsemi Proprietary and Confidential User's Guide Issue 3 23

Using the Command Line Utility

Profile number:
1. Aggressive
2. Normal
3. Relaxed
PARAM/VALUE...
A list of param/value pairs:
• MAX_ALLOWED_CRC_ERROR_COUNT
• CRC_ERROR_DURATION_SEC
• MAX_ALLOWED_NOT_READY_COUNT
• MAX_ALLOWED_SEL_TIMEOUT_COUNT
• MAX_ALLOWED_ASYNC_FREEZE_COUNT
• ASYNC_FREEZE_DURATION_SEC
• NEXUS_BUSY_DURATION_SEC
• MAX_IO_TIMEOUT_SEC
• PER_ITERATION_IO_TIMEOUT_SEC
• MAX_RETRY_COUNT
• ALLOW_BBR_ON_WRITE_FAILURE
• MAX_ALLOWED_MEDIUM_ERROR_COUNT
• MEDIUM_ERROR_DURATION_SEC
SAVE and FILE <File name>
Path to tunable parameter definition file. The default filename is ErrorTunableParams.cfg.

Examples
ARCCONF ERRORTUNABLE 1 SETPROFILE 1
ARCCONF ERRORTUNABLE 1 GETPARAMS 2 SAVE C:\abc.cfg
ARCCONF ERRORTUNABLE 1 CONFIGPARAMS FILE C:\abc.cfg
ARCCONF ERRORTUNABLE 1 CONFIGPARAMS CRC_ERROR_DURATION_SEC 10

2.11 arcconf expanderlist

Description
Returns a list of disk drive expanders on a controller.

Syntax
ARCCONF EXPANDERLIST <Controller#>

Parameters
Controller#
Controller number.

Examples

ARCCONF EXPANDERLIST 1

2.12 arcconf expanderupgrade

Description
Allows new firmware to be flashed to an enclosure or expander.

Microsemi Proprietary and Confidential User's Guide Issue 3 24

Using the Command Line Utility

Note: Some controllers do not support this operation.

Syntax:
ARCCONF EXPANDERUPGRADE <Controller#> ENCLOSURE <Connector# Channel# ID#>
[ChunkSize#] <UpgradeType> <Filename> [Mode#] [noprompt]

Parameters
Controller#
Controller number.
Channel#
Channel number of the device to be updated.
ID#
Device number of the device to be updated.
Connector#
Connector number of the device to be updated.
ChunkSize#
Chunk size, in bytes, to be used to update the firmware. Default is 65536 bytes.
Filename
Name of the firmware update file.
UpgradeType
EXPANDER—update the firmware image on the expander or enclosure
MFG—update the manufacturing image (BOOT SEEPROM) on the expander or enclosure
CPLD—update the CPLD image on the expander or enclosure
Note: MFG and CPLD upgrade types are supported on the Microsemi Adaptec AEC-82885T
expander only.

Mode#
The Mode parameter applies to EXPANDER and MFG upgrade types only. Valid values are:
• 02h—download microcode only; requires system reset or power cycle to activate (default)
• 06h—download microcode with offsets and activate
• 07h—download microcode with offsets, save, and activate
• 0Eh—download microcode with offsets and defer activation
• 0Fh—activate deferred microcode
Noprompt
Optional parameter that suppresses alert messages.

Examples

arcconf EXPANDERUPGRADE 1 ENCLOSURE 2 0 0 1024 EXPANDER C:\FirmwareImage.bin 7

arcconf EXPANDERUPGRADE 1 ENCLOSURE 2 0 0 512 MFG C:\FirmwareImage.rom 6
arcconf EXPANDERUPGRADE 1 ENCLOSURE 2 0 0 256 CPLD C:\CPLDImage.bin noprompt

2.13 arcconf failover

Description
Turns automatic failover on and off.

Microsemi Proprietary and Confidential User's Guide Issue 3 25

Using the Command Line Utility

Syntax
ARCCONF FAILOVER <Controller#> <on|off>

Parameters
Controller#
The controller number.
On
Turns the controller failover mode on.
Off
Turns the controller failover mode off.

Examples

ARCCONF FAILOVER 1 ON

2.14 arcconf getconfig

Description
Lists information about controllers, logical devices, physical drives, and flash backup systems, including:
• Controller type, status, World Wide Name (WWN), and mode
• Cache preservation status: enabled/disabled, % of cache pages preserved
• BIOS, boot block, device driver, and firmware versions
• Logical drive and array status, RAID level and size
• Logical drive mount points
• RAID 10 segment and group information
• maxCache status, fetch and flush rate policy, read/write balance, SSD information
• Device type, device ID, presence of PFA
• Physical device state, mount point (for drives with OS partition)
• Enclosure information: fan, power supply, and temperature status
• SGPIO virtual SEP information (virtual enclosure device for SGPIO backplanes)
• Flash backup information (for AFM-700 flash backup module): status, charge level, temperature
readings, max voltage, current, estimated life, errors, and serial number
• Connector/Lane/Phy mapping
Also displays controller BIOS settings if you do not include a device-type keyword.
Note: When displaying adapter information (AD keyword), the Controller Status field is set to Ok
or Not Ok. Its value is set to Not Ok only if:
1. Communication with the controller fails. This occurs when the driver returns an error code
after attempting to send a command to the controller.
2. A logical drive was created with a newer version of arcconf. Update to the latest utilities.
3. The controller mode (RAID/Mixed/HBA) is supported by the hardware, but not the firmware.
Usually, this means that an older version of arcconf is being used against a newer controller.
Update to the latest utilities.

For more information, see getconfig Output Summary on page 61.

Syntax
ARCCONF GETCONFIG <Controller#> [AD|LD [LD#]|PD|MC|AL|CN]

Microsemi Proprietary and Confidential User's Guide Issue 3 26

Using the Command Line Utility

ARCCONF GETCONFIG <Controller#> [AD|PD|AL|CN]

ARCCONF GETCONFIG <Controller#> [AD|LD [LD#]|PD|AL]
ARCCONF GETCONFIG <Controller#> [AR [AR#]|CN]

Parameters
Controller#
Controller number
LD#
Display information about the specified logical device
AR#
Display information about the specified array
AD/PD/AL...
• AD—Adapter information only
• LD—Logical drive information only
• AR—Array information only
• PD—Physical device information only
• MC—maxCache information only
• CN—Connector information only
• AL—All information

Examples
ARCCONF GETCONFIG 1
--------------------------------------------------------
Controller BIOS Setting Information
--------------------------------------------------------
Runtime BIOS : Enabled
Array BBS Support : Enabled
Physical Drives Displayed during POST : Disabled
Backplane Mode : SGPIO
MissingDrvCount :8
...

ARCCONF GETCONFIG 1 LD 0
ARCCONF GETCONFIG 1 CN
ARCCONF GETCONFIG 1 AR 1

2.15 arcconf getexception

Description
Prints the exception (errors/warnings) on the controller.

Syntax
ARCCONF GETEXCEPTION <Controller#> [ AD | LD | PD | AL] [on/off][nologs]

Parameters
Controller#
The controller number.
On/Off
Turns warning exceptions on and off.
AD/LD/PD/AL
• AD—Controller exceptions only
• LD—Logical drive exceptions only

Microsemi Proprietary and Confidential User's Guide Issue 3 27

Using the Command Line Utility

• PD—Physical drive exceptions only

• AL—All exceptions

Examples
ARCCONF GETEXCEPTION 1 PD
ARCCONF GETEXCEPTION 1 AL
ARCCONF GETEXCEPTION 1 off

2.16 arcconf getlogs

Description
Provides access to controller status, event logs, and usage statistics, including:
• A log of device errors that the controller encountered
• A log that records any occurrences of defunct devices
• A log of special events that may have occurred (rebuilds, LDMs, etc.)
• A log of controller usage statistics, including Inter-I/O Read and Write times and I/O Completion
Read and Write times
• A log of cache statistics for one or all logical drives
• A log of supported hardware components on the controller

Syntax
ARCCONF GETLOGS <Controller#> <Type1> [clear|tabular] [nologs]
ARCCONF GETLOGS <Controller#> <Type2> [tabular] [nologs]
ARCCONF GETLOGS <Controller#> <Type3> LOGICALDRIVE [<LD#>|ALL] [tabular]
[nologs]
ARCCONF GETLOGS <Controller#> <Type4> <HardwareType#> [nologs]
ARCCONF GETLOGS <Controller#> DEVICE <clear> <ErrorType#> [<Channel# ID#>|ALL]
[nologs]
ARCCONF GETLOGS <Controller#> <Type1> [clear|tabular] [nologs]
ARCCONF GETLOGS <Controller#> <Type2> [tabular] [nologs]
ARCCONF GETLOGS <Controller#> <Type4> <HardwareType#> [nologs]
ARCCONF GETLOGS <Controller#> DEVICE <clear> <ErrorType#> [<Channel# ID#>|ALL]
[nologs]

Parameters
Controller#
Controller number.
Type1
One of the following:
• DEVICE—device error log
• DEAD—dead (failed) drive log
• EVENT—controller event log
Type2
One of the following:
• STATS—controller statistics data
Type3
One of the following:
• CACHE—cache statistics data for all or a single logical drive
Type4

Microsemi Proprietary and Confidential User's Guide Issue 3 28

Using the Command Line Utility

One of the following:

1. Green Backup
2. Cache Memory
3. NVSRAM
ErrorType
One of the following:
• 1 - Parity Error Counter
• 2 - Link Failure Counter
• 3 - Hardware Error Counter
• 4 - Aborted Commands Counter
• 5 - Medium Error Counter
• 6 - SMART Warning Counter
Clear
Clears the specified log from the controller or a specific error counter for one or all physical drives on
a controller.
Channel/ID
Channel and number of the physical device on the controller.
Tabular
Displays the log or statistics in tabular format.

Examples

ARCCONF GETLOGS 1 EVENT

ARCCONF GETLOGS 1 STATS tabular
ARCCONF GETLOGS 1 DEVICE clear 3 ALL
ARCCONF GETLOGS 1 CACHE LOGICALDRIVE 0

2.17 arcconf getperform

Description
Fetches the parameters that define a logical drive performance mode. Default is the current mode.

Syntax
ARCCONF GETPERFORM <Controller#> [Performance Mode] [Save [Filename]] [Nologs]

Parameters
Controller#
Controller number.
Performance Mode
One of the following:
• 1 - Default/Dynamic mode
• 2 - OLTP/Database
• 3 - Big Block Bypass mode
• 4 - User defined mode
Save
Saves the performance mode parameters in a file.
Filename

Microsemi Proprietary and Confidential User's Guide Issue 3 29

Using the Command Line Utility

Name of the file in which to save the parameters. If not specified, the default filename is
PerformanceMode.cfg.
Nologs
Suppresses creation of logs for this command.

Examples

ARCCONF GETPERFORM 1 2

2.18 arcconf getsmartstats

Description
Displays SMART statistics for the hard drives and Solid State Drives (SSDs) on a controller.
Note: For more information about SMART statistics, see the maxView Storage Manager User's
Guide.

Syntax
ARCCONF GETSMARTSTATS <Controller#> [forcespinup] [Tabular]

Parameters
Controller#
Controller number.
Tabular
Creates output in tabular format.
Force Spin Up
Read SMART statistics from hard drives when SMART poll is disabled on the controller.

Examples

ARCCONF GETSMARTSTATS 1
ARCCONF GETSMARTSTATS 1 TABULAR

2.19 arcconf getstatus

Description
The GETSTATUS function displays the status of any background command that is currently running,
including information about the most recent rebuild, synchronization, logical-drive migration, and
compaction/expansion. The information includes the type of operation, status, logical drive number
and logical drive size (for a logical device), channel ID/device ID (for a physical drive), and percentage
of the operation completed.
Note:
1. GETSTATUS reports currently active operations for ARCCONF commands and commands issued
from maxView Storage Manager.
2. GETSTATUS reports verify, clear, initialize, and secure erase operations on physical devices.
3. GETSTATUS reports the status of controller rescan operations.

Microsemi Proprietary and Confidential User's Guide Issue 3 30

Using the Command Line Utility

4. GETSTATUS only reports active operations. It does not display information if the operation is
completed.

Syntax
ARCCONF GETSTATUS <Controller#> [nologs]

Parameters
Controller#
Controller# is the controller number

Examples

ARCCONF GETSTATUS 1

2.20 arcconf getversion

Description
Lists version information for all controllers or a specific controller's software components, including
information about the BIOS, driver, firmware currently running, and firmware that will run after a reboot.
Note: The firmware version that will run after a reboot is called the “staged” firmware.

Syntax
ARCCONF GETVERSION
ARCCONF GETVERSION <Controller#>

Parameters
Controller#
Controller# is the controller number

Examples

ARCCONF GETVERSION
ARCCONF GETVERSION 1

2.21 arcconf identify

Description
Identifies a physical device, logical device, or maxCache device by blinking its LEDs.

Syntax
ARCCONF IDENTIFY <Controller#> LOGICALDRIVE <LogicalDrive#> [START|STOP]
[nologs]

Microsemi Proprietary and Confidential User's Guide Issue 3 31

Using the Command Line Utility

ARCCONF IDENTIFY <Controller#> DEVICE <Channel# ID#> ... [START|STOP] [nologs]

ARCCONF IDENTIFY <Controller#> MAXCACHE [START|STOP] [nologs]
ARCCONF IDENTIFY <Controller#> LOGICALDRIVE <LogicalDrive#> [TIME <BlinkTime>]
[nologs]
ARCCONF IDENTIFY <Controller#> DEVICE <Channel# ID#> ... [TIME <BlinkTime>]
[nologs]
ARCCONF IDENTIFY <Controller#> ARRAY <Array#> [TIME <BlinkTime>] [nologs]
ARCCONF IDENTIFY <Controller#> ALL [STOP]
ARCCONF IDENTIFY <Controller#> DEVICE <Channel# ID#> [TIME <BlinkTime>] [nologs]
ARCCONF IDENTIFY <Controller#> ALL [STOP]

Parameters
Controller#
Controller number
LogicalDrive#
Number of the logical drive to be identified
Array#
Array number
Channel# ID#
Channel number and ID number for the physical device(s) to be identified
ALL
Blinks all physical devices on the controller for 1 hour or until the STOP command is issued
TIME <BlinkTime>
Time, in seconds, for the LEDs to continue blinking
START
Starts blinking the device until the STOP command is issued
STOP
Stops blinking the device

Examples
ARCCONF IDENTIFY 1 DEVICE 0 0
ARCCONF IDENTIFY 1 DEVICE 0 1 START
ARCCONF IDENTIFY 1 DEVICE 0 1 STOP
ARCCONF IDENTIFY 1 MAXCACHE START
ARCCONF IDENTIFY 1 ARRAY 0 TIME 30
ARCCONF IDENTIFY 1 ALL
ARCCONF IDENTIFY 1 ALL STOP

2.22 arcconf imageupdate

Description
Allows new firmware to be flashed to the hard drive.

Syntax:
ARCCONF IMAGEUPDATE <Controller#> DEVICE <Channel# ID# ChunkSize# Filename>
[Mode#] [BufferID#] [noprompt]

Parameters
Controller#
Controller number.

Microsemi Proprietary and Confidential User's Guide Issue 3 32

Using the Command Line Utility

Channel#
Channel number of the device to be updated.
ID#
Device number of the device to be updated.
ChunkSize#
Chunk size, in bytes, to be used to update the firmware. The minimum chunk size is 32768.
Note: For SATA drives, the chunk size must be a multiple of 512.
Filename
Name of the firmware update file.
Mode#
Firmware update mode. Valid values for physical drives are:
• 3-(SATA) Download with offsets and save image for immediate and future use
• 7-(SAS) Download microcode with offsets, save, and activate
BufferID#
Mandatory for tape drive firmware update.
Noprompt
Optional parameter that suppresses alert messages.

Examples

ARCCONF IMAGEUPDATE 1 DEVICE 0 0 16384 ados.lod 3

2.23 arcconf key

Description
Loads a feature key onto a Microsemi Adaptec controller.

Syntax
ARCCONF KEY <Controller#> SET <Key#>

Parameters
Controller#
The controller number.
Key#
The key number provided by Microsemi.

Examples

ARCCONF KEY 1 SET ABCDEFGHIJKLMNOPQRSTUVWX

2.24 arcconf list

Description
Lists all controllers in the system, or the configuration of a specific controller.

Microsemi Proprietary and Confidential User's Guide Issue 3 33

Using the Command Line Utility

Syntax
ARCCONF LIST [Controller#]

Parameters
Controller#
The controller number.

Examples
ARCCONF LIST
ARCCONF LIST 1

2.25 arcconf modify

Description
Morphs a logical device from one raid level to another (RAID Level Migration). Expands a logical device
from original size to one with larger capacity (Online Capacity Expansion).
Expands, shrinks or moves an array, or moves a logical device to a new array.

Syntax
ARCCONF MODIFY <Controller#> FROM <LogicalDrive#>
TO [Options] <Size> <RAID#> <CHANNEL# ID#> [CHANNEL# ID#] ... [noprompt]
ARCCONF MODIFY <Controller#> ARRAY <Array#> MOVE <Channel# ID#> [Channel# ID#]
... [nologs]
ARCCONF MODIFY <Controller#> ARRAY <Array#> HEAL <Channel# ID#> [Channel# ID#]
... [nologs]
ARCCONF MODIFY <Controller#> LOGICALDRIVE <LD#> MOVEARRAY <Array#> [nologs]
ARCCONF MODIFY <Controller#> LOGICALDRIVE <LD#> NEWARRAY <Channel# ID#>
[Channel# ID#] ... [nologs]

Parameters
Controller#
The controller number
LogicalDrive#
The logical drive number to be modified
Array#
The array ID of the array to be modified
Options
One of the following:
• Stripesize <size>—indicates the stripe size in KB. Options are 8, 16, 32, 64, 128, 256, 512, and
1024. the default is 256KB.
• Init_priority <priority>—is the priority level of the modification. Options are low, med, and high.
• Legs <leg>— is the number of sub-arrays for a RAID level-50 or RAID level 60 array. Possible values
are 2-16 legs and 3-16 drives/leg (to 48 drives maximum).
Size
• Size in MB.
• MAX indicates that you want to use all available space on the disk.
RAID#

Microsemi Proprietary and Confidential User's Guide Issue 3 34

Using the Command Line Utility

RAID level for the logical drive: 0, 1, 10, 5, 6, 50, 60, and simple_volume. 0, 1, 10 and 5 are supported.
Channel# ID#
Channel number and device ID for the device
Note: The CHANNEL# and ID# parameters are the list of devices that will contain the target
modification object. Channel and ID are repeatable parameters. For RAID 1 to Simple Volume
migration, CHANNEL# and ID# parameters are ignored.
MOVE
Moves an array to a new set of physical devices. Number of new physical devices must equal the
number of physical devices in the original array.
HEAL
Replaces failed physical devices in the array with the specified devices
MOVEARRAY
Moves a logical device to an existing array
NEWARRAY
Moves a logical device to a new array created with the specified physical devices
modifyparitygroups
Reconfigures the logical device(s) parity groups based on the final number of physical devices in the
array
noprompt
Suppresses the user prompt

Examples
ARCCONF MODIFY 1 FROM 2 TO 2048 0 0 123 0 124 0 117
ARCCONF MODIFY 1 ARRAY 1 MOVE 0 2 0 3
ARCCONF MODIFY 1 ARRAY 1 HEAL 0 0 0 1
ARCCONF MODIFY 1 LOGICALDRIVE 0 MOVEARRAY 1
ARCCONF MODIFY 1 LOGICALDRIVE 0 NEWARRAY 0 4 0 5

2.26 arcconf phyerrorlog

Description
Displays PHY error logs for physical devices on a controller or expander PHYs.

Syntax
ARCCONF PHYERRORLOG <Controller#> DEVICE <Channel# ID#>
ARCCONF PHYERRORLOG <Controller#> DEVICE ALL
ARCCONF PHYERRORLOG <Controller#> EXPANDER <ExpanderID#> <PHY#>
ARCCONF PHYERRORLOG <Controller#> EXPANDER <ExpanderID#> ALL
ARCCONF PHYERRORLOG <Controller#> DEVICE <Channel# ID#>
ARCCONF PHYERRORLOG <Controller#> DEVICE ALL

Parameters
Controller#
Controller number.
Channel/ID
Channel and number of the physical device on the controller.
ExpanderID#
Expander identifier.
PHY#
PHY identifier.

Microsemi Proprietary and Confidential User's Guide Issue 3 35

Using the Command Line Utility

ALL
Displays PHY error log for all physical devices or expander PHYs.

Examples

ARCCONF PHYERRORLOG 1 DEVICE 0 0

ARCCONF PHYERRORLOG 1 DEVICE ALL
ARCCONF PHYERRORLOG 1 EXPANDER 1 ALL

2.27 arcconf playconfig

Description
Configures a controller using a XML server template file produced by the SAVECONFIG command (see
arcconf saveconfig on page 40). Use this command to deploy the same controller configuration on
multiple servers in your storage space.
Note:
1. The XML server template file (default, saveconfig.xml) is editable. For example, you may need
to change the disk drive capacity, logical drive size, or RAID level.
2. Drives from the same vendor with slightly different capacities (147 GB vs. 150 GB, for instance)
are considered interchangeable. If the interchange results in a change in logical drive capacity,
the drive is scaled, as needed. For example, if the new drives have 4% more capacity due to
vendor or model changes, then all logical drives are increased in size by 4%.
3. Be sure to check the log file to verify that the controller was configured successfully. The exit
codes, shown below, indicate the success or failure of the operation and if the system needs
to be rebooted.

Code Value Meaning

SUCCESS 0 Configuration succeeded, no reboot is required.
FAILURE_GENERAL 1 An error occurred and the configuration could not
be completed.
SUCCESS_REBOOT 2 Configuration succeeded, but a reboot is required.

Syntax
ARCCONF PLAYCONFIG <Config XML File> [LogFile] [FORCE ALL|LOGICALSIZE] [SLOTID]
ARCCONF PLAYCONFIG <Config XML File> [LogFile] [FORCE ALL] [SLOTID]

Parameters
Config XML File
The pathname of the server template file.
LogFile
Sets the pathname of the error log file. By default, the error log is available at
C:\PMCS\Logs\playconfig.log on Windows operating systems and at /var/log/playconfig.log on
Linux/Unix operating systems.
FORCE
Forces deployment of the server even if the controller does not support all features, or the drive
capacity does not match the configuration in the input XML file. Use FORCE ALL to force deployment
of all features; use FORCE LOGICALSIZE to force deployment of just the logical drives.

Microsemi Proprietary and Confidential User's Guide Issue 3 36

Using the Command Line Utility

SLOTID
Apply the configuration based on Slot ID instead of Device ID.

Examples

ARCCONF PLAYCONFIG server1_config.xml playconfig.log FORCE ALL

2.28 arcconf preservecache

Description
Toggles the controller's cache preservation policy; clears the preserved cache for one or more logical
drives; and lists the logical drives with cache preservation enabled.
This command preserves the controller's DDR cache to prevent data loss in the event of a power failure
or unsafe shutdown. "Dirty pages" (data that have not been committed to disk) are restored to the
cache when power is restored and the logical drives on the controller are back online. Once the preserved
cache is restored, the controller flushes the data to disk using its normal scheduling mechanism. You
can clear the preserved dirty cache for one or more logical drives if you expect a failed enclosure or
logical drive to remain offline.
Note: You cannot enable maxCache read and/or write caching on a controller with cache
preservation enabled. The following operations are not permitted on a controller in the Cache
Preserved state:
• Creating a logical drive
• Changing the Performance mode
• Running a consistency check
• Changing the RAID Level of a logical drive
• Forcing a logical drive online or offline
• Changing the cache page size

Syntax
ARCCONF PRESERVECACHE <Controller#> <ENABLE|DISABLE>
ARCCONF PRESERVECACHE <Controller#> CLEAR LOGICALDRIVE <LD#|ALL> [noprompt]
ARCCONF PRESERVECACHE LD [LD#]

Parameters
Controller#
Controller number.
LD#
The logical drive number. Use ALL to clear preserved dirty cache for all logical drives on the controller.
noprompt
No prompt for confirmation.

Examples

ARCCONF PRESERVECACHE 1 ENABLE

ARCCONF PRESERVECACHE 1 CLEAR LOGICALDRIVE ALL
ARCCONF PRESERVECACHE 1 LD 1

Microsemi Proprietary and Confidential User's Guide Issue 3 37

Using the Command Line Utility

2.29 arcconf rescan

Description
Enables the controller to check for the removal of any disk drives in the ready state and to check for
the connection of any new disk drives to the controller. Controller rescan runs in the background,
asynchronously. When rescan is started, a message is displayed stating that the process is running in
the background and may take 10 minutes to complete. Another message is displayed if a rescan is started
while one is already in progress. Rescan status can be obtained with ARCCONF getstatus; see arcconf
getstatus on page 30 for more information.
Note:
When the SMART poll setting is disabled, the rescan will cause physical drives that are in reduced
RPM or powered off states to spin up.

Syntax
ARCCONF RESCAN <Controller#> [nologs]
ARCCONF RESCAN ALL [nologs]

Parameters
Controller#
The controller number
ALL
Rescans all controllers in the system

Examples
ARCCONF RESCAN 1
ARCCONF RESCAN ALL

2.30 arcconf resetstatisticscounters

Description
Resets statistics counters for a controller and the logical and physical devices attached to it. Use this
command to clear the counters and create fresh statistics, including (but not limited to):
• Read/Write Request Count
• Sectors Read/Written/Flushed
• Unaligned Reads/Writes
• Avg/Max Request Latency
• Max Queue Depth
• Max Request Latency
• Avg Dirty Cache Lines
• Avg Free Processor Ram
• Avg Locked Stripes
• Command Count

Microsemi Proprietary and Confidential User's Guide Issue 3 38

Using the Command Line Utility

Syntax
ARCCONF RESETSTATISTICSCOUNTERS <Controller#>

Parameters
Controller#
The controller number

Examples

ARCCONF RESETSTATISTICSCOUNTERS 1

2.31 arcconf romupdate

Description
Allows new firmware and BIOS to be flashed to the controller. A reboot is required for the new firmware
to take effect.
Note:
1. This command is supported on all OSs that support maxView Storage Manager.
2. You can download the .bin .ufi update files from the Support area at www.adaptec.com.
3. You can download the .bin update files at www.pmcs.com/myPMC

Syntax
ARCCONF ROMUPDATE <Controller#> <BaseName> [newversion <build#> [force]]
[noprompt] [nologs]

Parameters
Controller#
The controller number.
BaseName
Absolute path to the controller programmable image update file.
Newversion <build#>
Specifies the version of the firmware build.
Force
An optional parameter used to force a down-level firmware update. Valid only if Newversion parameter
is specified.
Noprompt
An optional parameter that suppresses the confirmation prompt.

Examples
ARCCONF ROMUPDATE 1 /usr/home/AC220001.UFI
ARCCONF ROMUPDATE 1 /usr/home/AC220001.BIN
ARCCONF ROMUPDATE 1 C:\firmwareImage\as483c.bin newversion 12345 force noprompt

Microsemi Proprietary and Confidential User's Guide Issue 3 39

Using the Command Line Utility

2.32 arcconf saveconfig

Description
Note: This command is supported on all OSs that support maxView Storage Manager.
Saves the controller configuration to a XML server template file, including the controller type, operational
settings, physical drive size, logical drive size, RAID level, and more. Use this file with the PLAYCONFIG
command to deploy the same controller configuration to other servers in your storage space; see arcconf
playconfig on page 36 for more information.
Note: Be sure to check the log file to verify that the configuration XML file was created successfully.
The exit codes, shown below, indicate the success or failure of the operation.

Code Value Meaning

SUCCESS 0 Configuration XML generated successfully.
FAILURE_GENERAL 1 An error occurred and the configuration XML could
not be generated.

Syntax
ARCCONF SAVECONFIG [Config XML File] [LogFile]

Parameters
Config XML File
The pathname of the server template file. The default name (if you omit this parameter) is
C:\PMCS\Logs\saveconfig.xml on Windows operating systems and /var/log/saveconfig.xml on Linux/Unix
operating systems.
LogFile
The pathname of the error log file. By default, the error log is available at C:\PMCS\Logs\saveconfig.log
on Windows operating systems and /var/log/saveconfig.xml on Linux/Unix operating systems.

Examples

ARCCONF SAVECONFIG server1_config.xml C:\LOGS\SERVER1.LOG

2.33 arcconf savesupportarchive

Description
Saves configuration and status information to help Adaptec Customer Support diagnose a problem with
your system. Saved information includes device logs, drive logs, event logs, error logs, controller logs,
history logs, basecode logs, and SSD SMART statistics. (For more information about SMART statistics,
see arcconf getsmartstats on page 30.)
By default, the log files are saved in the Support folder in the standard logs directory for your operating
system (/var/log for Linux, the maxView Storage Manager install directory on Windows, and so on).
Note: Unlike the Save Support Archive feature in maxView Storage Manager, this command does
not create a zip (“archive”) file. It simply saves the support files and logs in the Support folder.

Microsemi Proprietary and Confidential User's Guide Issue 3 40

Using the Command Line Utility

Note:
When the SMART poll setting is disabled, Save Support Archive will cause physical drives that are
in reduced RPM or powered off states to spin up.

Syntax
ARCCONF SAVESUPPORTARCHIVE [Path]
[Firmware|GUI|CIM|Arcconf|Storlib|Agent|Basecode]
ARCCONF SAVESUPPORTARCHIVE [Path] [Firmware|Arcconf|Storlib|Basecode]

Parameters
Path
Path to store the log files.
Log type:
One of these log files:
• Firmware: saves Firmware logs
• GUI: saves GUI logs
• CIM: saves CIM logs
• Arcconf: saves Arcconf logs
• Storlib: saves StorLib logs
• Agent: saves Agent logs
• Basecode: saves basecode logs

Examples

ARCCONF SAVESUPPORTARCHIVE
ARCCONF SAVESUPPORTARCHIVE Firmware
ARCCONF SAVESUPPORTARCHIVE /var/log/maxView Storlib

2.34 arcconf seeprom

Description
Updates the SEEPROM on the controller.

Syntax:
ARCCONF SEEPROM <Controller#> UPDATE [noprompt] [nologs]

Parameters
Controller#
Controller number.
Noprompt
Optional parameter that suppresses the confirmation message.
Nologs
Optional parameter that suppresses log output.

Examples

ARCCONF SEEPROM 1 UPDATE

Microsemi Proprietary and Confidential User's Guide Issue 3 41

Using the Command Line Utility

2.35 arcconf setalarm

Description
Sets the state of the controller audible alarm, if present.

Syntax
ARCCONF SETALARM <Controller#> <on|off|silence|test>

Parameters
Controller#
The controller number
On
Enables the alarm
Off
Disables the alarm
Silence
Quiets the currently sounding alarm
Test
Triggers the alarm

Examples

ARCCONF SETALARM 1 TEST

ARCCONF SETALARM 1 SILENCE

2.36 arcconf setbiosparams

Description
Changes select BIOS settings, including:
• Array BBS support (BIOS Boot Specification)
• Runtime BIOS mode
• Drives displayed on POST
• Backplane mode
• Missing drive count
The command sub-functions are mutually exclusive; you can set only one option at a time.

Syntax
ARCCONF SETBIOSPARAMS <Controller#> RUNTIMEBIOS [enable | disable]
ARCCONF SETBIOSPARAMS <Controller#> ARRAYBBSSUPPORT [enable | disable]
ARCCONF SETBIOSPARAMS <Controller#> DISPLAYEDONPOST [enable | disable]
ARCCONF SETBIOSPARAMS <Controller#> BACKPLANEMODE <mode>
ARCCONF SETBIOSPARAMS <Controller#> BIOSHALTONMISSINGDRIVECOUNT <count>
ARCCONF SETBIOSPARAMS <Controller#> POSTPROMPTTIMEOUT <timeout>

Microsemi Proprietary and Confidential User's Guide Issue 3 42

Using the Command Line Utility

Parameters
Controller#
Controller number
Subfunction
Option Description

RUNTIMEBIOS [enable|dis- When enabled, allows the controller to act as a bootable device. When disabled,
able] allows another controller to act as a bootable device. Default is enable.

ARRAYBBSSUPPORT [en- When enabled in systems that support BBS, the controller presents attached
able|disable] bootable devices up to the BIOS for boot device selection. Default is disable.

DISPLAYEDONPOST [en- When enabled, connected disk drives are displayed during system Power On Self
able|disable] Test (POST). Displaying the disk drives adds a few seconds to the overall POST time.
Default is disable.

BACKPLANEMODE <mode> Sets the backplane mode to 0-IBPI, 1-SGPIO, or 3-Disabled. Default is IBPI.

BIOSHALTONMISSINGDRIVE- The number of missing drives during POST. If => "count", halt. Count can have a
COUNT <count> value between 1-255; default is 8.

POSTPROMPTTIMEOUT Changes the F1/F2 POST prompt timeout for the controller during system boot.
<timeout> Timeout can have a value between 1-255.

Examples
ARCCONF SETBIOSPARAMS 1 RUNTIMEBIOS disable
ARCCONF SETBIOSPARAMS 1 BACKPLANEMODE 1
ARCCONF SETBIOSPARAMS 1 BIOSHALTONMISSINGDRIVECOUNT 5
ARCCONF SETBIOSPARAMS 1 ARRAYBBSSUPPORT enable
ARCCONF SETBIOSPARAMS 1 POSTPROMPTTIMECOUNT 10

2.37 arcconf setboot

Description
Sets the controller as a boot device for the system. This command is available only when the controller
is offline.

Syntax
ARCCONF SETBOOT <Controller#> LOGICALDRIVE <LogicalDrive#> [TYPE <Boot Type>]
[nologs]
ARCCONF SETBOOT <Controller#> DEVICE <Channel# ID#> TYPE <Boot Type> [nologs]
ARCCONF SETBOOT <Controller#> ENABLE
ARCCONF SETBOOT <Controller#> DEVICE <Channel# ID#> TYPE <Boot Type> [nologs]
ARCCONF SETBOOT <Controller#> ENABLE

Parameters
Controller#
Controller number
LogicalDrive#
Logical drive number to mark as the boot device
Channel# ID#

Microsemi Proprietary and Confidential User's Guide Issue 3 43

Using the Command Line Utility

Channel and ID of the physical device to mark as the boot device

TYPE <Boot Type>
Boot type of the logical or physical device:
• Primary - Primary boot logical/physical device
• Secondary - Secondary boot logical/physical device
• None - Non-bootable
ENABLE
Sets the controller as a boot controller

Examples
ARCCONF SETBOOT 1 LOGICALDRIVE 0 TYPE primary
ARCCONF SETBOOT 1 DEVICE 0 5 TYPE secondary
ARCCONF SETBOOT 1 ENABLE

2.38 arcconf setcache

Description
Changes the cache mode for a logical drive, or the write cache mode for all drives or a single physical
drive on a controller.

Syntax
ARCCONF SETCACHE <Controller#> LOGICALDRIVE <LogicalDrive#> <logical mode>
[noprompt] [nologs]
ARCCONF SETCACHE <Controller#> DEVICE <Channel> <ID> <physical mode> [nologs]
ARCCONF SETCACHE <Controller#> DEVICEALL <policy> [noprompt] [nologs]
ARCCONF SETCACHE <Controller#> LOGICALDRIVE <LogicalDrive#> <logical mode>
[noprompt] [nologs]
ARCCONF SETCACHE <Controller#> DEVICEALL <policy> [noprompt] [nologs]
ARCCONF SETCACHE <Controller#> CACHERATIO <read#> <write#>
ARCCONF SETCACHE <Controller#> WAITFORCACHEROOM <enable | disable>
ARCCONF SETCACHE <Controller#> NOBATTERYWRITECACHE <enable | disable>

Parameters
Controller#
The controller number
LogicalDrive#
The number of the logical drive whose cache will be altered
Logical mode
Logical drive cache mode:
• RON - read cache on
• ROFF - read cache off
• WT - write through disabled
• WB - write back enabled
• WBB - write back enabled (when protected by battery or flash backup module)
• con - cache enabled
• coff - cache disabled
Channel/ID
Lists the space-delimited channel number and device number pairs for each device.
Physical mode
• WT - write through disabled

Microsemi Proprietary and Confidential User's Guide Issue 3 44

Using the Command Line Utility

• WB - write back enabled

Policy
• Enable - write back for all physical drives
• Disable - write through for all physical drives
• drivespecific - set policy for individual physical drives
CACHERATIO <read#> <write#>
Sets the cache ratio for the controller:
• read# - Read cache percentage
• write# - Write cache percentage
WAITFORCACHEROOM
Wait for room in the read/write cache when full instead of automatically bypassing it in favor of higher
performance. Enabling this feature prevents RAID 1 inconsistencies that occur whenever the host
changes buffer contents during write operations.
• Enable - wait for room in the read/write cache
• Disable - do not wait for room in the read/write cache
NOBATTERYWRITECACHE
Enables write caching when a battery or supercapacitor is not present or fully charged. This setting
applies to all logical drives on the controller; at least one logical drive must exist before usage.
• Enable - enable write caching on controller without fully charged battery or supercapacitor
• Disable - disable write caching on controller without fully charged battery or supercapacitor
Caution: Enabling write caching without a fully charged battery/supercapacitor may cause data
loss in the event of a power failure.

Examples
ARCCONF SETCACHE 1 LOGICALDRIVE 1 RON
ARCCONF SETCACHE 1 DEVICE 0 0 WB
ARCCONF SETCACHE 1 DEVICEALL Enable
ARCCONF SETCACHE 1 CACHERATIO 60 40
ARCCONF SETCACHE 1 WAITFORCACHEROOM enable
ARCCONF SETCACHE 1 NOBATTERYWRITECACHE enable

2.39 arcconf setconfig

Description
Resets the controller configuration. Logical drives are deleted, hard disks are reset to the READY state,
cache contents are lost, and controller settings are reset to default values.

Syntax
ARCCONF SETCONFIG <Controller#> DEFAULT [noprompt]

Parameters
Controller#
The controller number
Default
Restores the controller's default configuration.
Noprompt
No prompt for confirmation.

Microsemi Proprietary and Confidential User's Guide Issue 3 45

Using the Command Line Utility

Examples

ARCCONF SETCONFIG 1 DEFAULT

2.40 arcconf setcontrollermode

Description
Sets the controller operating mode to any of the following:
• RAID: Expose RAW (default)—All RAID functions of the controller are enabled. Attached drives
without Microsemi Adaptec meta-data are surfaced to the host operating system as RAW Pass
Through devices (similar to JBODs on legacy Adaptec controllers).
• Auto Volume Mode—Attached drives without Microsemi Adaptec meta-data, but with an OS
partition, are surfaced to the host operating system as RAW devices, where the RAID layer of the
controller firmware is bypassed when the host issues commands to the device. Attached drives
without Microsemi Adaptec meta-data and without OS partitions, are automatically configured as
Simple Volumes (single drives with Microsemi Adaptec meta-data), with these settings:
• Controller read caching is set to “Enabled” for rotating media.
• Controller write caching is set to “Enabled (write-back) when protected by battery/ZMM” for
rotating media.
• Caching for non-rotating media is disabled.
In Auto Volume Mode, you can create up to a maximum of 128 Simple Volumes; no other RAID
types are supported.
Note: Before you can change to Auto Volume mode, you must delete redundant RAID arrays,
maxCache Devices, and hot spare drives (if any).
Auto-Volume Mode enables DRAM caching on rotating media to help reduce latency and accelerate
performance, especially if combined with a custom performance mode, such as Big Block Bypass
(see arcconf setperform on page 51 for more information).
• HBA Mode—The intent of this mode is to allow the RAID controller to act and be used as a Host
Bus Adapter. All attached drives are surfaced as RAW devices. Changing into HBA mode is allowed
only if there are no drives with Microsemi Adaptec meta-data attached to the controller. Uninitialize
the drives before changing to HBA mode (see arcconf uninit on page 59). Uninitialized drives are
also compatible with any HBA and can be exchanged with drives on the motherboard's SATA
interface.
Note:
1. Before you can change to HBA mode, you must delete existing hot spare drives (if any).
2. In HBA mode, a hot-plugged drive is automatically configured as a RAW device. When a
RAW device is pulled from the system, the controller does not delete internal data
structures associated with the drive. However, the missing RAW device is not remembered
across rescans.
• RAID: Hide RAW—All RAID functions of the controller are enabled, but RAW devices are not exposed
to the operating system.
• Simple Volume Mode—Allows you to create Simple Volumes only, up to a maximum of 128 volumes;
no other RAID types are supported.
Note: Before you can change to Simple Volume mode, you must delete existing RAID arrays,
maxCache Devices, and hot spare drives (if any).
• Smart HBA Mode—RAID volumes and RAW (unconfigured) devices are exposed to the operating
system.

Syntax:
ARCCONF SETCONTROLLERMODE <Controller#> <Controller Mode> [nologs]

Microsemi Proprietary and Confidential User's Guide Issue 3 46

Using the Command Line Utility

Parameters
Controller#
Controller number.
Controller Mode
One of the following values:
• 0 - RAID: Expose RAW
• 1 - Auto Volume Mode
• 2 - HBA Mode
• 3 - RAID: Hide RAW
• 4 - Simple Volume Mode
• 5 - Smart HBA Mode
nologs
Suppresses log output for the command.

Examples

ARCCONF SETCONTROLLERMODE 1 2
ARCCONF SETCONTROLLERMODE 1 0
ARCCONF SETCONTROLLERMODE 1 4
ARCCONF SETCONTROLLERMODE 1 5

2.41 arcconf setcontrollerparam

Description
Changes a parameter of a controller.

Syntax
ARCCONF SETCONTROLLERPARAM <Controller#> SMARTPOLL <Enable | <Disable Raw>>
[nologs] [noprompt]

Parameters
Controller#
The controller number.
SMARTPOLL
Configure SMART poll setting on the controller.
• Disable Raw: Disable SMART poll for RAW physical drives only.
• Enable : Enable SMART poll for RAW physical drives only.

Examples
ARCCONF SETCONTROLLERPARAM 1 SMARTPOLL DISABLE RAW

Microsemi Proprietary and Confidential User's Guide Issue 3 47

Using the Command Line Utility

2.42 arcconf setcustommode

Description
Sets the parameters for a user-defined performance mode. Contact Microsemi Adaptec Support for
more information about using this command to set up a custom performance mode. See also arcconf
setperform on page 51.

Syntax
ARCCONF SETCUSTOMMODE <Controller#> ENABLE <Flag1> [Flag2 ... ] [DISABLE Flag1
Flag2 ...] [PARAMS <Field1 Value1> [Field2 Value2] ..] [nologs]
ARCCONF SETCUSTOMMODE <Controller#> DISABLE <Flag1> [Flag2 ... ] [nologs]
ARCCONF SETCUSTOMMODE <Controller#> PARAMS <Field1 Value1> [Field2 Value2] ..
[nologs]
ARCCONF SETCUSTOMMODE <Controller#> FILE [File name] [nologs]

Parameters
Controller#
Controller number
ENABLE <Flag>, DISABLE <Flag>
A list of flags to enable or disable:
• REPPREFET (CACHE_REPRESSPREFETCHING)
• IOSORT (CACHE_IO_SORTING)
• INSLRU (CACHE_INSERT_LRU)
• DYNSHARE (CACHE_DYNAMIC_SHARING)
• RLOADBYPASS (CACHE_READ_LOAD_BYPASS_VALID)
• WLOADBYPASS (CACHE_WRITE_LOAD_BYPASS_VALID)
• WRITEBYPASS (CACHE_LARGE_WRITE_BYPASS)
• IOCOAL (IO_COALESCING)
PARAMS
A list of field/value pairs:
• MAXDIRTY (CACHE_MAX_DIRTY)
• DMDFLUSHTHR (CACHE_DEMAND_FLUSH_THRESHOLD)
• PAGESIZE (CACHE_PAGE_SIZE)
• RFINACTIVE (CACHE_RESERVED_FOR_INACTIVE)
• ADDWRITES (CACHE_ADDITIONAL_WRITES)
• MINFLUSHSTRIPE (CACHE_MIN_FLUSH_STRIPE)
• BYPASSWRIOSIZE (CACHE_BYPASS_WRITE_IO_SIZE)
• IOLIMSASHDD (IO_LIMIT_SAS_HDD)
• IOLIMSASSSD (IO_LIMIT_SAS_SSD)
• IOLIMSATAHDD (IO_LIMIT_SATA_HDD)
• IOLIMSATASSD (IO_LIMIT_SATA_SSD)
FILE <File name>
Path to parameter definition file. The default parameter file is PerformanceMde.cfg.

Examples
ARCCONF SETCUSTOMMODE 1 ENABLE IOSORT DISABLE INSLRU
ARCCONF SETCUSTOMMODE 1 DISABLE REPPREFET
ARCCONF SETCUSTOMMODE 1 PARAMS PAGESIZE 3
ARCCONF SETCUSTOMMODE 1 FILE C:\Adaptec

Microsemi Proprietary and Confidential User's Guide Issue 3 48

Using the Command Line Utility

2.43 arcconf setmaxcache

Description
Enables/disables maxCache SSD caching for one or more logical drives; updates the maxCache write
cache policy and “dirty page” threshold (data not committed to disk); adds Solid State Drives to the
maxCache pool and removes SSDs from the pool; sets the maxCache read/write balance and cache
fetch/flush rate; clears the maxCache pool.
Note: Before you can enable maxCache SSD caching, you must assign at least one SSD to the
maxCache pool.

Syntax: Read Caching

ARCCONF SETMAXCACHE <Controller#> LOGICALDRIVE <LogicalDrive#> READCACHE
<ENABLE|DISABLE>

Syntax: Write Caching

ARCCONF SETMAXCACHE <Controller#> LOGICALDRIVE <LogicalDrive#> WRITECACHE
<ENABLE|DISABLE> [WRITEPOLICY <policy>]
ARCCONF SETMAXCACHE <Controller#> LOGICALDRIVE ALL WRITECACHE DISABLE
[WRITEPOLICY <policy>]
ARCCONF SETMAXCACHE <Controller#> LOGICALDRIVE <LogicalDrive#> WRITEPOLICY
<policy>
ARCCONF SETMAXCACHE <Controller#> DIRTYPAGETHRESHOLD <dirtyPageThreshold#>
ARCCONF SETMAXCACHE <Controller#> WBCVALID <ENABLE|DISABLE>

General Usage
ARCCONF SETMAXCACHE <Controller#> <ADDTOPOOL|REMOVEFROMPOOL> <Channel# Device#>
ARCCONF SETMAXCACHE <Controller#> RWBALANCE <Read#> <Write#>
ARCCONF SETMAXCACHE <Controller#> FLUSHANDFETCHRATE <FlushAndFetchRate#>
ARCCONF SETMAXCACHE <Controller#> CLEAR

Parameters
Controller#
The controller number.
LogicalDrive#
The number of the logical drive. You can specify one or more logical drives.
Channel#
The channel number for the SSD.
Device#
The device number for the SSD.
Read#/Write#
The read/write ratio for invalidating data on the SSD. When the ratio is reached, the page is removed
from the cache. Values range from 1-10 for each parameter.
FlushAndFetchRate#
The read cache fetch rate from 1 to 1000: 1-50=Low, 51-100=Medium, 101-1000=High. The default is
100.

Microsemi Proprietary and Confidential User's Guide Issue 3 49

Using the Command Line Utility

Note: The lower the rate the longer the page is kept on the SSD before it is flushed from the
cache.
dirtyPageThreshold#
Controls the amount cache space allocated to “dirty” data; that is, data that has not been committed
to disk. The threshold value ranges from 1-100 (percent). Once the percentage of dirty pages crosses
the threshold, the data are flushed to disk.
WBCVALID ENABLE|DISABLE
Enables and disables write caching in non-redundant maxCache. Applies to all logical drives.
Policy
maxCache write cache policy:
• WB - write back enabled. maxCache will store the data on the SSD and write it back to the hard
disks when there is little or no impact on performance. This is the default policy.
• INSTWB - instant write back enabled. In addition to the default policy, maxCache will create dirty
pages on-the-fly for full-stripe writes if there is room on the SSD and the number of dirty pages
is below the threshold.
• WT - write through enabled. Similar to instant write back, but full-stripe writes go to both the
cache and hard disk and no dirty pages are created on-the-fly.
Clear
Clears the maxCache pool.

Examples

ARCCONF SETMAXCACHE 1 LOGICALDRIVE 1 READCACHE ENABLE

ARCCONF SETMAXCACHE 1 LOGICALDRIVE 1 WRITECACHE ENABLE WRITEPOLICY WT
ARCCONF SETMAXCACHE 1 DIRTYPAGETHRESHOLD 50
ARCCONF SETMAXCACHE 1 ADDTOPOOL 0 1
ARCCONF SETMAXCACHE 1 REMOVEFROMPOOL 0 1 0 2
ARCCONF SETMAXCACHE 1 RWBALANCE 4 1
ARCCONF SETMAXCACHE 1 FLUSHANDFETCHRATE 200
ARCCONF SETMAXCACHE 1 CLEAR

2.44 arcconf setname

Description
Renames a logical drive.

Syntax
ARCCONF SETNAME <Controller#> LOGICALDRIVE <LogicalDrive#> <New Name>

Parameters
Controller#
Controller number
LogicalDrive#
The number of the logical drive to be renamed
New Name
The new name of the logical drive

Examples

ARCCONF SETNAME 1 LOGICALDRIVE 1 BACKUP_A

Microsemi Proprietary and Confidential User's Guide Issue 3 50

Using the Command Line Utility

2.45 arcconf setncq

Description
Changes the controller’s Native Command Queuing (NCQ) setting to enabled or disabled. This setting
affects the SATA disk drives on the controller. It takes effect when the SATA drives are restarted.

Syntax
ARCCONF SETNCQ <Controller#> ENABLE|DISABLE

Parameters
Controller#
The controller number

Examples

ARCCONF SETNCQ 1 ENABLE

2.46 arcconf setperform

Description
Changes controller settings based on the application type.

Syntax
ARCCONF SETPERFORM <Controller#> <Performance Mode> [nologs]
ARCCONF SETPERFORM <Controller#> MNPDELAY <Delay> [no logs]
ARCCONF SETPERFORM <Controller#> DPO <Enable | Disable> [no logs]

Parameters
Controller#
The controller number
Performance Mode
Setting Behavior
1 (DYNAMIC/Default) Performance criteria adjusts automatically based on
controller usage, RAID level, and disk drive type.
2 (OLTP/Database) Performance criteria is optimized for transaction-orient-
ed applications such as data entry and retrieval.
3 (Big Block Bypass) DRAM write cache is bypassed based on IO write size;
performance is optimized for serving Web pages and
retrieving data.
4 (User-Defined) User-defined performance mode. See arcconf setcus-
tommode on page 48.

MNPDELAY <Delay>

Microsemi Proprietary and Confidential User's Guide Issue 3 51

Using the Command Line Utility

Sets the monitor and performance delay for the controller, in seconds. Default is 60 minutes (3600
seconds).
DPO
Enables or disables the degraded performance setting for the controller. Default is disabled.

Examples

ARCCONF SETPERFORM 1 2
ARCCONF SETPERFORM 1 3
ARCCONF SETPERFORM 1 MNPDELAY 1800
ARCCONF SETPERFORM 1 DPO enable

2.47 arcconf setphy

Description
Sets the maximum connection speed for SAS devices to 6Gb/s or 12Gb/s.

Syntax
ARCCONF SETPHY <Controller#> MAXSASPHYLINKRATE <MaxSASPhylinkrate#> [noprompt]
[nologs]

Parameters
Controller#
The controller number
MaxSASPhylinkrate#
The Phy link rate. Valid values are 6 and 12 (for 6Gb/s and12Gb/s, respectively).
Noprompt
No prompt for confirmation.

Examples

ARCCONF SETPHY 1 MAXSASPHYLINKRATE 6

ARCCONF SETPHY 1 MAXSASPHYLINKRATE 12

2.48 arcconf setpower

Description
Changes power management settings for disk drives on a controller or logical drive.

Syntax
ARCCONF SETPOWER <Controller#> Stayawake DISABLE | <startime> <endtime> [DAYS] [nologs]
ARCCONF SETPOWER <Controller#> Spinup <internal#> <external#>
ARCCONF SETPOWER <Controller#> LD <LD#> <disable | [slowdown st#] | [poweroff pt#] |
[verify vt#]> [nologs]

ARCCONF SETPOWER <Controller#> POWERMODE <mode>

Microsemi Proprietary and Confidential User's Guide Issue 3 52

Using the Command Line Utility

Parameters
Controller#
The controller number
Stayawake
Sets the stayawake period for the disk drives on the controller. During the stayawake period, the disk
drives always operate at their peak spin rate.
Disable
Is a keyword that disables the stayawake period for the disk drives on a controller.
starttime
Specifies the beginning of the stayawake period, in the form HHMM (24-hour format)
endtime
Specifies the end of the stayawake period, in the form HHMM (24-hour format).
DAYS
Days of the week on which the stayawake period is enabled; default is all days.
Spinup
Sets the spin-up limits for the controller—the maximum number of drives that the controller may spin
up at one time.
internal#
The maximum number of internal drives that the controller may spin up at one time, from 0-20.
external#
The maximum number of external drives (such as the drives in a JBOD) that the controller may spin
up at one time, from 0-20.
LD#
The logical drive number.
Slowdown st#
Sets the disk drive slow-down timer, in minutes. Valid values are 0 (never), 3, 5, 10, 20, 30, 60, 120,
180.
Poweroff pt#
Sets the disk drive power-off timer, in minutes. Valid values are 0 (never), 3, 5, 10, 20, 30, 60, 120,
180.
Verify vt#
Sets the period of inactivity, in hours, after which an inactive drive (a drive that's already powered
down) is restarted to verify its operating condition. Once the check is completed, the drive is powered
down and returns to its inactive state. Valid values are 0 (never), 1, 2, 3, 8, 12, 24.
Note: For the Slowdown, Poweroff, and Verify timers, st# must be less than pt#, and pt# must
be less than vt#. You can set one or more timers, in any order, in a single command. Keep in
mind that the Verify timer, vt#, is specified in hours; the other two timers are specified in minutes.
mode
Sets the power mode for the controller. Valid values are 1, 2, and 3:
• 1: Minimum power - Set static settings to lowest possible values and reduces dynamically based
on workload
• 2: Balanced - Set static settings based on configuration and reduce dynamically based on workload
• 3: Maximum power - Set static settings to highest possible values and do not reduce dynamically

Examples
ARCCONF SETPOWER 1 STAYAWAKE DISABLE
ARCCONF SETPOWER 1 SPINUP 4 4
ARCCONF SETPOWER 1 LD 2 POWEROFF 60
ARCCONF SETPOWER 1 LD 2 SLOWDOWN 20 POWEROFF 60 VERIFY 12
ARCCONF SETPOWER 1 POWERMODE 2

Microsemi Proprietary and Confidential User's Guide Issue 3 53

Using the Command Line Utility

2.49 arcconf setpriority

Description
Changes a task's execution priority or a controller's global background task priority.

Syntax
ARCCONF SETPRIORITY <Controller#> [TASK ID] <New Priority> [current]
ARCCONF SETPRIORITY <Controller#> <REBUILD|EXPAND> <New Priority>

Parameters
Controller#
The controller number
Task ID
Task ID is the number of the task to be changed. Use arcconf getstatus to obtain the task ID.
Omit this parameter to set the controller's global background task priority; that is, the execution
priority for all tasks on the controller.
New Priority
LOW, MEDIUM, or HIGH. For REBUILD only: MEDIUMHIGH (if rapid rebuild priority is supported on
the controller).
Current
Applies a global task priority change to running tasks. By default, a global priority change does not
apply to running tasks.
REBUILD
Sets the controller's rebuild priority.
EXPAND
Sets the controller's capacity expansion (OCE) priority.

Examples

ARCCONF SETPRIORITY 1 <task_id> HIGH

ARCCONF SETPRIORITY 1 LOW CURRENT
ARCCONF SETPRIORITY 1 EXPAND LOW
SETPRIORITY 1 REBUILD MEDIUM

2.50 arcconf setstate

Description
Changes the state of a physical device or logical device from its current state to the designated state.

Syntax
ARCCONF SETSTATE <Controller#> DEVICE <Channel#> <Device#> <State> [MAXCACHE]
[LOGICALDRIVE <LD#>[LD#] ... ] [noprompt]
ARCCONF SETSTATE <Controller#> LOGICALDRIVE <LD#> OPTIMAL [ADVANCED <option>]
[noprompt]
ARCCONF SETSTATE <Controller#> DEVICE <Channel#> <Device#> <State> [ARRAY
<AR#>] [noprompt] [nologs]

Microsemi Proprietary and Confidential User's Guide Issue 3 54

Using the Command Line Utility

ARCCONF SETSTATE <Controller#> LOGICALDRIVE <LD#> OPTIMAL [ADVANCED <option>]

[noprompt]
ARCCONF SETSTATE <Controller#> DEVICE <Channel#> <Device#> <State> [noprompt]

Syntax
ARCCONF SETSTATE <Controller#> DEVICE <Channel#> <Device#> <State> [LOGICALDRIVE
<LD#>[LD#] ... ] [noprompt]
ARCCONF SETSTATE <Controller#> LOGICALDRIVE <LD#> OPTIMAL [ADVANCED <option>]
[noprompt]

Parameters
Controller#
The controller number
Channel#
The channel number for the drive.
Device#
Device number for the device.
LD#
Logical drive number.
AR#
Array number.
State
• HSP—Create a hot spare from a ready drive. Dedicates the HSP to one or more arrays logical
devices.
• RDY—Remove a hot spare designation. Attempts to change a drive from Failed to Ready. To
remove a dedicated HSP from one or more logical devices, use the optional LOGICALDRIVE <LD#>
<LD#> ... parameter.
• DDD—Force a drive offline (to Failed).
• EED—Enable the erased drive.
MAXCACHE
Optional keyword for maxCache devices only. Include if State is HSP or RDY, and the hot spare is for
a maxCache device.
ADVANCED <option>
Optional keyword/option pair. Set option to Nocheck to force a logical drive to the Optimal state
without performing a consistency check.
Caution: Using Advanced options may result in data loss!
Noprompt:
No prompt for confirmation.

Examples
ARCCONF SETSTATE 1 DEVICE 0 0 HSP LOGICALDRIVE 1 2 3
ARCCONF SETSTATE 1 DEVICE 0 0 RDY LOGICALDRIVE 2
ARCCONF SETSTATE 1 LOGICALDRIVE 1 OPTIMAL ADVANCED nocheck
ARCCONF SETSTATE 1 DEVICE 0 0 DDD
ARCCONF SETSTATE 1 DEVICE 0 0 RDY
ARCCONF SETSTATE 1 DEVICE 0 0 HSP ARRAY 0

Microsemi Proprietary and Confidential User's Guide Issue 3 55

Using the Command Line Utility

2.51 arcconf setstatsdatacollection

Description
Enables or disables statistics collection for a controller. To display the statistics, seearcconf getlogs on
page 28 .

Syntax
ARCCONF SETSTATSDATACOLLECTION <Controller#> Enable|Disable

Parameters
Controller#
The controller number
Enable
Turns statistics collection on.
Disable
Turns statistics collection off.

Examples

ARCCONF SETSTATSDATACOLLECTION 1 ENABLE

2.52 arcconf setvmcredential

Description
Resets the Hypervisor login credentials for VMware Guest OSs running Remote ARCCONF.
Note: This command is available for VMware Guest OSs running Remote ARCCONF only.

Syntax
SETVMCREDENTIAL <Esxip> <Esxcimomport> <Esxuserid> <Esxpassword> [noprompt]

Parameters
Esxip
Hypervisor IP address.
Esxcimomport
Hypervisor CiMOM port number.
Esxuserid
Hypervisor user name.
Esxpassword
Hypervisor password.

Microsemi Proprietary and Confidential User's Guide Issue 3 56

Using the Command Line Utility

Examples

ARCCONF SETVMCREDENTIAL 172.18.46.101 5989 root passwd

2.53 arcconf smp

Description
Sends a SAS Management Protocol (SMP) function request to a SMP target device.

Syntax:
ARCCONF SMP <Controller#> Enclosure <Connector# Channel# Device#> Expander
<Expander#> <CommandType1> [ASCII]
ARCCONF SMP <Controller#> Enclosure <Connector# Channel# Device#> Expander
<Expander#> <CommandType2 PHY#> [ASCII]

Parameters
Controller#
Controller number.
Connector# Channel# ID#
Connector ID, Channel ID and Device ID of the enclosure that contains the expander.
Expander#
Expander number on the controller (SMP target device).
PHY#
The PHY Identifier (valid only for for Discover and PHY Error Log Request).
CommandType#
CommandType1:
• RGR - Report General Request
• RMR - Report Manufacturer Request
CommandType2:
• DR - Discover Request
• RPELR - Report PHY Error Log Request
ASCII
Displays the SMP response in ASCII format along with Hex formatted output.

Examples

ARCCONF SMP 1 Enclosure 1 2 0 Expander 0 RGR

ARCCONF SMP 1 Enclosure 1 2 0 Expander 1 DR 0

2.54 arcconf task

Description
Performs a task on a logical drive, physical drive, or maxCache logical device. Uninitializes physical drives
on a controller.

Microsemi Proprietary and Confidential User's Guide Issue 3 57

Using the Command Line Utility

Syntax: General Usage

ARCCONF TASK
TASK START <Controller#> LOGICALDRIVE <LogicalDrive#> <options> [noprompt]
TASK STOP <Controller#> LOGICALDRIVE <LogicalDrive#>
TASK START <Controller#> DEVICE <Channel> <ID> <options> [noprompt]
TASK STOP <Controller#> DEVICE <Channel> <ID>
TASK START <Controller#> DEVICE ALL UNINITIALIZE
ARCCONF TASK
TASK START <Controller#> DEVICE <Channel> <ID> <options> [noprompt]
TASK START <Controller#> DEVICE ALL UNINITIALIZE
TASK STOP <Controller#> DEVICE <Channel> <ID>
ARCCONF TASK START <Controller#> DEVICE ALL UNINITIALIZE

Syntax: maxCache Usage

ARCCONF TASK
TASK START <Controller#> MAXCACHE COHERENCYCHECK [ONCE|ALWAYS]
TASK START <Controller#> MAXCACHE <VERIFY_FIX|VERIFY>
TASK STOP <Controller#> MAXCACHE

Parameters
Controller#
The controller number
LogicalDrive#
Number of the logical drive in which the task is to be performed
Options:
• Logical drive options:
• verify_fix (Verify with fix)—verifies the logical drive redundancy and repairs the drive if bad
data is found.
• verify—verifies the logical drive redundancy without repairing bad data.
• clear—removes all data from the drive.
• Physical device options:
• verify_fix—verifies the disk media and repairs the disk if bad data is found.
• verify—verifies the disk media without repairing bad data.
• clear—removes all data from the drive.
• initialize—returns a drive to the READY state (erases the metadata).
• secureerase [password] [PATTERN <pattern>]—removes all data from the drive in a secure
fashion to prevent any possible recovery of the erased data. (See arcconf atapassword on
page 17 for details about setting the password.) Erase patterns:
• 1 : Zero - Initializes all blocks to zero.
• 2 : Random Zero - Initializes block to random value then zero.
• 3: Random Random Zero - Initializes block to random value, next block to random value,
then zero.
• UNINITIALIZE—When specified with ALL, clears Microsemi Adaptec meta-data and any OS
partitions from all drives on the controller; existing data on the drive is destroyed.

MAXCACHE options:
• coherencycheck—compares valid pages of the maxCache Device with their corresponding logical
drive storage. Once is the default.
• verify_fix (Verify with fix)—verifies the maxCache Device redundancy and repairs the logical drive
if bad data is found.
• verify—verifies the maxCache Device redundancy without repairing bad data.

Microsemi Proprietary and Confidential User's Guide Issue 3 58

Using the Command Line Utility

Examples
ARCCONF TASK START 1 LOGICALDRIVE 1 VERIFY
ARCCONF TASK START 1 DEVICE 0 0 SECUREERASE <password> PATTERN 1
ARCCONF TASK START MAXCACHE COHERENCYCHECK ONCE
ARCCONF TASK STOP 1 DEVICE 0 0
ARCCONF TASK START 1 DEVICE ALL UNINITIALIZE

2.55 arcconf uninit

Description
Uninitializes one or more physical drives. The uninitialize command clears Microsemi Adaptec meta-data
and any OS partitions from a drive; existing data on the drive is destroyed. Drives can uninitialized only
if they are in the Raw or Ready state (that is, not part of any logical drive). A drive in the Raw state has
no Microsemi Adaptec meta-data but may or may not have an OS partition.
Note: Uninitialized drives are compatible with any HBA and can be exchanged with drives on the
motherboard's SATA interface. For more information about uninitialized devices, see arcconf
setcontrollermode on page 46.

Syntax:
ARCCONF UNINIT <Controller#> <Channel# Drive#> [Channel# Drive#] ... [nologs]
ARCCONF UNINIT <Controller#> ALL [nologs]

Parameters
Controller#
Controller number.
Channel#
The channel number of the device to be uninitialized.
Drive#
The drive number of the device to be uninitialized.
ALL
Uninitializes all physical devices on the controller.
nologs
Suppresses log output for the command.

Examples

ARCCONF UNINIT 1 0 12 0 13
ARCCONF UNINIT 1 ALL

2.56 arcconf verifywrite

Description
Enables or disables the verify write feature on the controller.

Syntax
ARCCONF VERIFYWRITE <Controller#> <ENABLE | DISABLE> [nologs]

Microsemi Proprietary and Confidential User's Guide Issue 3 59

Using the Command Line Utility

Parameters
Controller#
The controller number.
ENABLE
Enables verify write feature.
DISABLE
Disables verify write feature.

Examples
ARCCONF VERIFYWRITE 1 ENABLE
ARCCONF VERIFYWRITE 1 DISABLE

Microsemi Proprietary and Confidential User's Guide Issue 3 60

getconfig Output Summary

A getconfig Output Summary

Table 3 • getconfig output summary

getconfig Command Field Description Possible Values/Units
Controller status Overall status of the controller based optimal,failed,passive,removed,Signa-
on its resources. ture error,inaccessible,Down,driver
update required
Controller mode Mode of the controller on which it is RAID(Expose RAW),Auto Volume,
operating. HBA,RAID(Hide RAW),Simple Volume,
SmartHBA
Controller Cache Preservation Data on DRAM of controller can be Enabled, Disabled
preserved.
Channel description Technology type of the channel(s) on SCSI,SATA,SAS,IDE,FIBRE,SATA_ON_
the specified controller. SAS
Controller Model Model number of the controller. n/a
Controller Serial Number Serial number of the controller. n/a
Controller World Wide Name Unique World Wide Name of the n/a
controller.
Controller Alarm The state of the alarm on the con- Not available,Enabled,Disabled,Un-
troller. known
Physical Slot Slot number of this controller n/a
Temperature Current temperature of the con- degree Celsius and degree Fahrenheit
troller
Installed Memory Memory capacity of DRAM installed Memory in MB
on controller .
Global task priority The execution priority for all tasks Low,Medium,High
running on the controller
Performance Mode An application-specific performance Dynamic,OLTP/Database,DataCenter,
mode to improve I/O throughput User Defined
based on the needs of your applica-
tion.
Host Bus type Type of host expansion bus standard Unknown,PCI,PCI-X,PCIE,NA
Host Bus Speed Speed of host expansion bus stan- n/a
dard in MHz
Host bus link width Actual width bits /links depending on n/a
host bus type
Stayawake Period The period during which disk drives n/a
on the controller always operate at
their peak spin rate.
Spinup limit internal drives Maximum number of internal disk n/a
drives (drives in an enclosure) that
the controller may spin-up at the
same time.
Spinup limit external drives Maximum number of external disk n/a
drives (drives in an enclosure) that

Microsemi Proprietary and Confidential User's Guide Issue 3 61

getconfig Output Summary

getconfig Command Field Description Possible Values/Units

the controller may spin-up at the
same time.
Defunct disk drive count Number of dead drives connected to n/a
the controller.
Logical devices/Failed/Degraded The number of logical devices on the n/a
controller,number of failed logicals
and number of degraded logical on
the controller.
NCQ status Lets SATA disk drives arrange com- Enabled, Disabled
mands into the most efficient order
for optimum performance
Statistics data collection mode Whether the statistics collection on Enabled, Disabled
the controller .The stats can be seen
by arcconf getlogs commandis en-
abled or not.
Global Physical Device Write Cache The write cache policy for all physical Enable All, Disable All, Drive Specific
Policy drives on a controller
Monitor Log Severity Level The severity level of monitor logs Emergency,Alert,Critical,Error,Warn-
captured from firmware. ing,Notification,Informational,Debug,
Unknown
Global Max SAS Phy Link Rate The maximum connection speed (or 6GBps,12GBps,Unknown
PHY link rate) for SAS devices on a
controller.
Smart Poll SMART poll setting on the controller. Enabled, Disabled for RAW drives,
Unknown

RAID Properties
Copyback When a logical drive is rebuilt using Enabled,Disabled
a hot spare (see Failed Disk Drive
Protected by a Hot Spare), data from
the failed drive is transferred to the
hot spare
Background consistency check Lets maxView Storage Manager con- Enabled,Disabled
tinually and automatically checks
your logical drives for bad or inconsis-
tent data once they're in use.
Background consistency check period The background consistency check Days
period in days
Automatic Failover Controls the rebuilding of a logical Enabled,Disabled
drive when a failed drive is replaced.
Error Tunable Profile The current error tunable profile Aggressive, Normal, Relaxed, User
Defined
maxCache flush and fetch rate To optimize the read cache perfor- Valid range is 1 to 1000. 1-50 Low, 5
mance of maxCache container 1-100 Medium, 101-1000 High
maxCache Read, Write Balance Fac- The read/write ratio is for invalidat- Valid range is 1 to 10
tor ing data on the SSD. When the ratio
is reached, the page is removed from

Microsemi Proprietary and Confidential User's Guide Issue 3 62

getconfig Output Summary

getconfig Command Field Description Possible Values/Units

the cache. Values range from 1-10
for each parameter.
maxCache Dirty Page Threshold Controls the amount cache space al- Valid range is 1 to 100
located to “dirty” data; that is, B105
. The threshold value ranges from 1-
100 (percent). Once the percentage
of dirty pages crosses the threshold,
the data are flushed to disk.
Controller BIOS Setting Information
Runtime BIOS Allows the controller to act as a Enabled,Disabled
bootable device.
Array BBS Support The controller presents attached Enabled,Disabled
bootable devices up to the BIOS for
boot device selection. This is relevant
for logical arrays.
Physical Drives Displayed during Connected disk drives are displayed Enabled,Disabled
POST during system Power On Self Test
(POST). Displaying the disk drives
adds a few seconds to the overall
POST time.
Backplane Mode Adaptec Series 6 Controllers (except IBPI,SGPIO,N/A ,Unknown
Series 6E/6T): When set to Auto,
controller automatically detects
backplane signal type: I2C or SGPIO.
To set the backplane mode explicitly
select SGPIO, I2C, or Disabled. De-
fault is Auto. Adaptec Series 7, Series
8, and Series 6E/6T Controllers:
When set to Default, controller auto-
matically sets the backplane mode
to IBPI. To set the backplane mode
explicitly, select IBPI, SGPIO, or Dis-
abled. Default is IBPI.
BIOS Halt on Missing Drive Count The number of missing drives during
POST. If => "count", halt. Default is 8
.
Controller Version Information
BIOS Current version of BIOS flashed onto n/a
the controller
Firmware Current version of Firmware flashed n/a
onto the controller
Driver Current version of driver installed on n/a
the system
Boot Flash Firmware version that will run on re- n/a
boot
CPLD(Load version/Flash Version) CPLD version that is loaded and that n/a
is available in flash
SEEPROM(Load Version/Flash Ver- SEEPROM version that is loaded and n/a
sion) that is available in flash

Microsemi Proprietary and Confidential User's Guide Issue 3 63

getconfig Output Summary

getconfig Command Field Description Possible Values/Units

Controller Cache Backup Unit Infor-
mation
Overall Backup Unit Status Status of flash backup unit connected Not Present,Not Ready,Ready,Failed,
to the controller. For more informa- Fatal,Preparing,Health Normal,Health
tion, see Logical Drive, HDD, and Low,Health Dead,Invalid
Flash Backup System Status and Error
Conditions on page 70.
Backup Unit Type Type of back up unit connected to AFM700/700-LP
the controller or on controller
Non-Volatile Storage Status The status of the non volatile storage Not Present,Not Ready,Ready,Failed,
Fatal,Preparing,Health Normal,Health
Low,Health Dead,Invalid
Supercap Status Super cap attached to the backup Not Present,Not Ready,Ready,Failed,
unit. For more information, see Logi- Fatal,Preparing,Health Normal,Health
cal Drive, HDD, and Flash Backup Low,Health Dead,Invalid
System Status and Error Conditions
on page 70.
Current Temperature Temperature of supercap degrees Celsius
Threshold temperature Temperature above which the super- degrees Celsius
cap will become overheated
Life -time Temperature Record- Life-time min/max temperature degrees Celsius
ed(Min/max) recorded
Voltage(Present/Max) Voltage in mV and max voltage in mV Millivolts (mV)
Life-time Max Voltage Recorded Life-time max Voltage of BU system Millivolts (mV)
Current Drawn(Present/Max) Current Drawn in mA present and Millivolts (mV)
max
Health Health level of BU system percentage
Charge level Charge level of BU system percentage
Estimated Life-time Life -time estimate in years and n/a
months
Serial number Super cap serial number n/a
Learn Status Calibration operation run by con- Not Ready,Idle,Pending,"Active,
troller periodically to know status of Scheduled","Active Requested","Ac-
battery tive,Manual",Passed,Failed,not
Ready,Fatal,Unknown
Next Scheduled Learn Cycle Time until next schedule learn cycle Hours
in hours
Present Capacitance Capacitance in Farad Farad
Connector Information
Connector Id Connector number on the controller n/a
Lane Information
Channel ID channel identifier for this lane n/a
Device ID device identifier for this lane n/a

Microsemi Proprietary and Confidential User's Guide Issue 3 64

getconfig Output Summary

getconfig Command Field Description Possible Values/Units

SAS Address SAS address for this lane n/a
PHY Identifier phy identifier for this lane n/a
Lane SAS Phy Information
SAS Address SAS address for this lane SAS Phy n/a
Attached Phy Identifier Attached phy identifier for this lane n/a
sas phy
Attached SAS Address Attached SAS address for the lane sas n/a
phy
Negotiated Link Rate link rate for the lane SAS phy n/a
Logical device information
Logical device number Unique ID of logical drive listed n/a
Logical device name Logical Drive name n/a
Block Size of member drives Block size reported by logical mem- 512 Bytes,4k
ber drives.
RAID level RAID Level on which logical drive has 0,1,1E,5,5E,5EE,00,10,1E0,50,5E0,
been created Spanned Volume,RAID_Volume,Sim-
ple_volume,6 XOR,6 Reed-Solomon,
60 XOR,60 Reed- Solomon
Unique Identifier Unique ID of logical drive n/a
Status of logical device State of logical drive based on health • Optimal
of RAID members of logical device • Impacted
along with running task information • Failed
on the logical. For more information, • Clearing
see Logical Drive, HDD, and Flash • Logical Device Reconfiguring
Backup System Status and Error • Suboptimal, Fault Tolerant
Conditions on page 70. • Suboptimal, Reconfiguring
• Suboptimal, Rebuilding
• Degraded
• Degraded, Reconfiguring
• Degraded, Rebuilding
• Flushing
• Does not exist

Size Size where actual data is striped n/a

across the disk drives
Parity Space Parity size in logical drive calculated n/a
by RAID level specifications.
Stripe-unit size The stripe size is the amount of data n/a
(in KB) written to one disk drive, be-
fore moving to the next disk drive in
the logical device.
Read-cache setting The controller monitors read access Enabled,Disabled
to a logical drive and, if it sees a pat-
tern, pre-loads the cache with data
that seems most likely to be read
next, thereby improving perfor-
mance.

Microsemi Proprietary and Confidential User's Guide Issue 3 65

getconfig Output Summary

getconfig Command Field Description Possible Values/Units

Read-cache status Whether the read cache setting is on On ,Off
or off
Wrie-cache setting Determines when data is stored on Enabled,Disabled
a disk drive and when the controller
communicates with the operating
system.
Write-cache status Whether the write cache is enabled, wt,wb,wbb
disabled or enabled with backup
support
maxCache write cache status whether the maxcache write caching On ,Off
is enabled for logical drives or not
Physical Device information
Device # Drive number n/a
State current state of physical drive based Ready,online,Failed,standby,Hots-
on operations done on it. pare,Rebuilding,Partitioned,Does not
Exist,Unsupported,copying back,
RAW(Pass through),RAW(Smart HBA),
Unknown
Block Size Maximum size of data block on disk 512KB,4K
drives which are RAID members of
logical device
Supported Whether the connected drive is sup- Yes,No
ported by the controller.
Programmed Max Speed The maximum transfer speed support- Basic SCSI,SCSI 2,Fast SCSI 2,Ultra
ed by this drive SCSI,Ultra2 SCSI,Ultra 160,Ultra 320,
SATA 1.5Gb/s,SATA3.0Gb/s,SATA 6.
0Gb/s,SATA12.0Gb/s,SAS 1.5Gb/s,
SAS3.0Gb/s,SAS6.0Gb/s,SAS12.0Gb/
s,SATA on SAS 1.5Gb/s,SATA on SAS3
.0Gb/s,SATA on SAS 6.0Gb/s,SATA on
SAS12.0Gb/s,Unknown
Transfer Speed Negotiated link rate of the device Basic SCSI,SCSI 2,Fast SCSI 2,Ultra
connected SCSI,Ultra2 SCSI,Ultra 160,Ultra 320,
SATA 1.5Gb/s,SATA3.0Gb/s,SATA 6.
0Gb/s,SATA12.0Gb/s,SAS 1.5Gb/s,
SAS3.0Gb/s,SAS6.0Gb/s,SAS12.0Gb/
s,SATA on SAS 1.5Gb/s,SATA on SAS3
.0Gb/s,SATA on SAS 6.0Gb/s,SATA on
SAS12.0Gb/s,Unknown
Reported Channel,Device(T:L) Virtual path/target/lun for device. n/a
Target (T) is the SCSI ID of the device,
and LUN (L) corresponds to the SCSI
LUN number.
Reported Location Location of the connector and device n/a
relative to connector
Vendor Physical device manufacturer name n/a
Model Product model name of physical de- n/a
vice

Microsemi Proprietary and Confidential User's Guide Issue 3 66

getconfig Output Summary

getconfig Command Field Description Possible Values/Units

Firmware Firmware version of the physical de- n/a
vice
Serial number Serial number of physical device. n/a
World wide name Reported world wide name provided n/a
by manufacturer
Reserved Size Reserved capacity of the drive n/a
Used size Used capacity of the drive n/a
Unused size Unused or available capacity of the n/a
drive
Total size Sum of used,unused capacity of the n/a
drive
Write Cache The write cache setting determines Write back,Write through
when data is stored on a disk drive
and when the controller communi-
cates with the operating system.
S.M.A.R.T Self-Monitoring, Analysis, and Report- Yes,No
ing Technology is supported or not
S.M.A.R.T Warnings any SMART warning generated or not Smart event from drive sense data,
e.g. code = 0x0B
Power State The power management options for Full RPM,Powered off,Reduced RPM
a controller affect all logical drives
on that controller.
Supported Power States These are power management states Full RPM,Powered off,Reduced RPM,
supported by different vendor hard Standby
drives
SSD The connected drive is SSD or not Yes,No
Temperature The recent temperature of the drive n/a
in celsius and fahrenheit.
NCQ status Lets SATA disk drives arrange com- Enabled,Disabled
mands into the most efficient order
for optimum performance.NCQ sta-
tus is enabled or not
Device Phy Information
PHY Identifier Phy identifier for this device n/a
SAS Address SAS address for the device n/a
Attached Phy Identifier Attached phy identifier for this device n/a
Attached SAS Address Attached SAS address for this device n/a
Runtime Error Counters
Hardware error count sense key 4 value n/a
Medium error count count of the number of medium er- after drive encounters a medium er-
rors ror, FW will attempt bad block recov-
ery

Microsemi Proprietary and Confidential User's Guide Issue 3 67

getconfig Output Summary

getconfig Command Field Description Possible Values/Units

Parity error count count of the number of parity errors SCSI parity error encountered i.e.
sense code = 47h . This will also con-
sequently abort a command and in-
crement the respective counter.
Link error count count of the number of link errors • SMP Response frame received
with errors e.g. zero frame size,
exceeds max length, missing
EOF, len mismatch with FIS type
• Link timeout while transmitting
frame, IO could not be delivered
to drive
• Encountered open Reject (Bad/
Wrong Destination) i.e. some-
thing is wrong with the topology
• Unable to deliver/issue com-
mand to drive, break received
• LUN reset or I_T nexus reset
• Open zone violation i.e. request-
ed phy is not in the same zone
as initiator or zoning permis-
sions are invalid
• No PHY's in the port or the port
itself is down
• Encountered DMA transmit er-
ror

Aborted command count count of the number of aborted • Disk not accepting commands
commands because format is in progress
• A passthrough command re-
ceived invalid response
• Timeout, receiving OPEN_RE-
JECT(Retry)
• Open error due to IO abort
• A scsi task management com-
mand was issued but the re-
sponse was invalid
• Task management response has
incorrect LUN
• Cannot communicate due to
protocol mismatch
• Unable to successfully open a
connection during the data
phase of a command

Smart warning count count of the number of smart warn- n/a

ings on the device
maxCache information
maxCache device number Always 100 for a maxCache device n/a
maxCache device name name of maxCache container n/a
Block Size of member drives Block size of SSD constituting the 512 Bytes,4k,Unknown
maxCache

Microsemi Proprietary and Confidential User's Guide Issue 3 68

getconfig Output Summary

getconfig Command Field Description Possible Values/Units

maxCache dirty status Does the maxCache contain dirty da- Dirty,Clean
ta that is data that has not been
committed to disk or is it clean
RAID level RAID level of maxcache 0,1,1E,5,5E,5EE,00,10,1E0,50,5E0,
Spanned Volume,RAID_Volume,Sim-
ple_volume,6 XOR,6 Reed-Solomon,
60 XOR,60 Reed- Solomon
Background Coherency Check Chooses to verify the maxCache De- Active Always,Inactive,Unknown
vice without fixing inconsistent or
bad data, or run a coherency check
to compare valid pages of the max-
Cache Device with their correspond-
ing logical drive storage.
Status of maxCache state of maxCache device based on Does not exist,Failed,Optimal,Degrad-
health of RAID members in the max- ed,Logical Device Reconfiguring,"De-
Cache device graded,System","suboptimal,Fault
tolerant","Suboptimal,Reconfigur-
ing","Suboptimal,System","Degraded,
Rebuilding",Flushing,"Suboptimal,
Rebuilding"
Size size of maxCache device in MB n/a
maxCache write cache status maxCache write caching status for On,Protected,Disabled(No Battery
each logical device in your storage Protection),Off(Non redundant max-
space. Cache Device),Off
Protected by Hot-Spare If the maxCache device is protected Yes,No
by hot spare. A hot spare is a SSD
(Solid State Drive) that automatically
replaces any failed drive in a max-
Cache device, and can subsequently
be used to rebuild that maxCache
device.
Failed stripes any bad stripes or bad blocks for a Yes,No
logical

Microsemi Proprietary and Confidential User's Guide Issue 3 69

Logical Drive, HDD, and Flash Backup System Status and Error Conditions

B Logical Drive, HDD, and Flash Backup System Status and Error
Conditions

Logical Drive States

ARCCONF displays the following states for a logical drive.
Optimal • The logical drive is healthy. In case of redundant
Logical Drive types: it has full redundancy
• RAID 1, RAID 1E and RAID10 volumes created using
“quick init” are shown as “optimal” as redundancy
is being established on every write I/O

Impacted • The logical drive has been created. Redundancy

information has not yet been built completely

Failed • More member disks than supported by the redun-

dancy level of the logical drive have failed. Logical
Drive is taken offline

Clearing • Observed when an array is created using method

‘clear’ .The logical drive enters the clearing state
when firmware zeros out first and last 8 blocks of
the container space.

Logical device Reconfiguring • A logical drive that is morphing (eg, raid level migra-
tions / online capacity expansion)

Suboptimal, Fault Tolerant • There are one or more drive failures but the logical
drive is still fault tolerant (ie, single drive failure on
RAID-6 or RAID-60). The logical drive is in steady
state

Suboptimal, Reconfiguring • There are one or more drive failures but the logical
drive is still fault tolerant (ie, single drive failure on
RAID-6 or RAID-60). The logical drive is morphing.

Suboptimal, Rebuilding • There are one or more drive failures but the logical
drive is still fault tolerant (ie. single drive failure on
RAID-6 or RAID-60). The array is recalculating parity.

Degraded • The redundant logical drive has suffered at least

one member disk failure and any more disk failures
would fail the logical drive (ie, two drive failure on
RAID 6 or one drive failure on other RAIDs)

Degraded, Reconfiguring • A degraded logical drive that is morphing

Degraded, Rebuilding • A degraded logical drive where rebuild has started

on any remaining members

Flushing • There is a flushing task on a logical drive

Microsemi Proprietary and Confidential User's Guide Issue 3 70

Logical Drive, HDD, and Flash Backup System Status and Error Conditions

HDD Error Statistics

ARCCONF displays the following HDD error statistics.
Aborted Command Count Types of aborted command instances:
• Timeout receiving OPEN_REJECT(Retry)
• Open error due to IO abort
• SCSI task management command was issued but
the response was invalid
• Task management response has incorrect LUN
• Cannot communicate due to protocol mismatch
• Unable to successfully open a connection during
the data phase of a command

Link Failure count Link failure characterized by the following scenarios:

• SMP Response frame received with errors eg, zero
frame size, exceeds max length, missing EOF, len
mismatch with FIS type
• Link timeout while transmitting frame, I/O could
not be delivered to drive
• Encountered open Reject (Bad/Wrong Destination)
ie, something is wrong with the topology
• Unable to deliver/issue command to drive, break
received
• LUN reset or I_T nexus reset
• Open zone violation ie, requested phy is not in the
same zone as initiator or zoning permissions are
invalid
• No PHYs in the port or the port itself is down
• Encountered DMA transmit error

Medium Error Count • The drive has encountered a medium error and FW
will attempt bad block recovery

Parity Error Count • SCSI parity error encountered i.e. sense code = 47
h. This will also consequently abort a command and
increment the respective counter.

Smart Warning Count • Smart event from drive sense data eg, code = 0x0
B

Flash Backup Status

ARCCONF displays the following status for the Flash Backup system.
General Backup Unit status Preparing:
• The GB unit is preparing the NAND flash for backup.
The supercap can take up to 10 minutes to charge
to 100% from zero charge and report ready status
Ready:
• The backup unit is enabled with the supercap
charged and NAND flash prepared
Not Ready:
• Observed if the supercap is not present or has suf-
fered a fatal error or if the BU temperature has
exceeded allowed maximum

Microsemi Proprietary and Confidential User's Guide Issue 3 71

Logical Drive, HDD, and Flash Backup System Status and Error Conditions

Supercapacitor status Fatal:

• FW could not retrieve green backup information
or configuration due to hardware issues , overvolt-
age, etc
Health Normal / Low / Dead:
• Health parameter indicates overall energy holding
ability of the capacitor and mathematically repre-
sents (supercap capacitance / initial capacitance)
• Health > 90% will be displayed as normal
• Dead status implies that capacitor would need re-
placement
Not Supported:
• FW does not have green backup feature enabled
Not Present:
• The backup unit is not installed

Microsemi Proprietary and Confidential User's Guide Issue 3 72

Microsemi makes no warranty, representation, or guarantee regarding the information contained herein
or the suitability of its products and services for any particular purpose, nor does Microsemi assume any
liability whatsoever arising out of the application or use of any product or circuit. The products sold
hereunder and any other products sold by Microsemi have been subject to limited testing and should not
be used in conjunction with mission-critical equipment or applications. Any performance specifications
Microsemi Corporate Headquarters are believed to be reliable but are not verified, and Buyer must conduct and complete all performance
One Enterprise, Aliso Viejo, and other testing of the products, alone and together with, or installed in, any end-products. Buyer shall
CA 92656 USA not rely on any data and performance specifications or parameters provided by Microsemi. It is the Buyer's
responsibility to independently determine suitability of any products and to test and verify the same. The
information provided by Microsemi hereunder is provided "as is, where is" and with all faults, and the
Within the USA: +1 (800) 713-4113
entire risk associated with such information is entirely with the Buyer. Microsemi does not grant, explicitly
Outside the USA: +1 (949) 380-6100
or implicitly, to any party any patent rights, licenses, or any other IP rights, whether with regard to such
Fax: +1 (949) 215-4996 information itself or anything described by such information. Information provided in this document is
Email: [email protected] proprietary to Microsemi, and Microsemi reserves the right to make any changes to the information in
www.microsemi.com this document or to any products and services at any time without notice.
© 2017 Microsemi Corporation. All rights
reserved. Microsemi and the Microsemi logo
Microsemi Corporation (Nasdaq: MSCC) offers a comprehensive portfolio of semiconductor
are trademarks of Microsemi Corporation. All
other trademarks and service marks are the and system solutions for aerospace & defense, communications, data center and industrial
property of their respective owners. markets. Products include high-performance and radiation-hardened analog mixed-signal
integrated circuits, FPGAs, SoCs and ASICs; power management products; timing and
synchronization devices and precise time solutions, setting the world's standard for time;
voice processing devices; RF solutions; discrete components; enterprise storage and
communication solutions; security technologies and scalable anti-tamper products; Ethernet
solutions; Power-over-Ethernet ICs and midspans; as well as custom design capabilities
and services. Microsemi is headquartered in Aliso Viejo, California, and has approximately
4,800 employees globally. Learn more at www.microsemi.com.
ESC-2160659

Microsemi Proprietary and Confidential User's Guide Issue 3