Arcconf Playconfig - Adaptec Command Line Utility User Manual

Raid controller
Hide thumbs Also See for Command Line Utility:
Table of Contents

Advertisement

Channel# is the channel number for the device.
Drive# is the device_ID (device number) for the device.
Noprompt is an optional parameter that overrides the user prompt.
Examples
ARCCONF MODIFY 1 FROM 2 TO 2048 0 0 123 0 124 0 117

arcconf playconfig

Configures a controller using a XML server template file produced by the SAVECONFIG
command (see
multiple servers in your storage space.
Note:
The XML server template file (default, saveconfig.xml) is editable. For example, you may
1
need to change the disk drive capacity, logical drive size, or RAID level.
Drives from the same vendor with slightly different capacities (147GB vs 150GB, for
2
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%.
Be sure to check the log file to verify that the controller was configured successfully. The
3
exit codes, shown below, indicate the success or failure of the operation and if the system
needs to be rebooted.
Code
SUCCESS
FAILURE_GENERAL
SUCCESS_REBOOT
Syntax
ARCCONF PLAYCONFIG <Input XML File> [LogFile] [FORCE ALL|LOGICALSIZE]
Parameters
Input XML File is the pathname of the server template file. The default server template file is
available at C:\PMCS\Logs\saveconfig.xml.
LogFile is the pathname of the error log file. By default, the error log is available at
C:\PMCS\Logs\playconfig.log.
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.
Example
ARCCONF PLAYCONFIG server1_config.xml playconfig.log FORCE ALL
page
24). Use this command to deploy the same controller configuration on
Value
0
1
2
Chapter 2: Using the Command Line Utility
Meaning
Configuration succeeded, no reboot is
required.
An error occurred and the configuration
could not be completed.
Configuration succeeded, but a reboot is
required.
22

Hide quick links:

Advertisement

Table of Contents
loading

Table of Contents