Command Line Interface Reference Guide R
Copyright ©2000 – 2004 Adaptec, Inc. All rights reserved. No part of this publication may be reproduced, stored in a retrieval system, or transmitted in any form or by any means, electronic, mechanical, photocopying, recording or otherwise, without the prior written consent of Adaptec, Inc., 691 South Milpitas Blvd., Milpitas, CA 95035. Trademarks Adaptec and the Adaptec logo are trademarks of Adaptec, Inc., which may be registered in some jurisdictions.
Contents 1 Introduction Audience 1-1 Accessing the CLI 1-2 Accessing the CLI from the MS-DOS Prompt 1-2 Accessing the CLI in Windows 1-2 Accessing CLI in Linux and UNIX 1-2 Accessing CLI in NetWare 1-3 Terminology 1-3 Conventions 1-4 Command Syntax 1-5 Class 1-5 Action 1-6 Object 1-6 Switch 1-6 Value 1-6 Parameter 1-7 Blank Space 1-7 Parameter and Switch Value Types 1-7 Boolean 1-7 integer 1-8 string 1-9 scsi_device 1-10 free_space 1-11 container 1-12 Status Information 1-13 The Stat and Task Items 1-13 Th
Contents 2 General Control Commands close 2-2 exit 2-3 help, ? 2-4 history_size 2-5 open 2-6 reset_window 2-8 toggle_more 2-9 3 container Commands container add_level 3-3 container create mirror 3-5 container create mmirror 3-8 container create mstripe 3-12 container create mvolume 3-17 container create raid5 3-21 container create stripe 3-27 container create volume 3-32 container delete 3-37 container extend file_system 3-40 container extend mvolume 3-43 container extend volume 3-47 container list 3-50
Contents container set failover 3-95 container set global_failover 3-97 container set io_delay 3-99 container set label 3-101 container show cache 3-103 container show failover 3-108 container split 3-109 container unlock 3-112 container unmirror 3-114 4 controller Commands controller details 4-2 controller firmware compare 4-6 controller firmware save 4-7 controller firmware update 4-9 controller list 4-10 controller pause_io 4-12 controller rescan 4-14 controller reset_scsi_channel 4-15 controller resu
Contents disk show space 5-26 disk verify 5-29 disk zero 5-31 6 diagnostic Commands diagnostic clear boot_parameters 6-2 diagnostic dump structures 6-3 diagnostic dump text 6-4 diagnostic load_arrays 6-6 diagnostic moderation set count 6-7 diagnostic moderation set timer 6-8 diagnostic moderation show count 6-9 diagnostic moderation show timer 6-10 diagnostic set boot_parameter 6-11 diagnostic show boot_parameter 6-12 diagnostic show history 6-13 7 logfile Commands logfile end 7-2 logfile start 7-3 8
Contents enclosure set power 9-19 enclosure set scsiid 9-21 enclosure set temperature 9-24 enclosure show fan 9-26 enclosure show power 9-29 enclosure show slot 9-32 enclosure show status 9-36 enclosure show temperature 9-41 A Automated Scripts Creating an Automated Script A-1 vii
1 Introduction In this Chapter Audience 1-1 Accessing the CLI 1-2 Terminology 1-3 Conventions 1-4 Command Syntax 1-5 Parameter and Switch Value Types 1-7 Status Information 1-13 The CLI provides a command line alternative to Adaptec Storage Manager. Through the CLI, you perform most of the storage management tasks that you can perform with the Adaptec Storage Manager GUI and, in addition, some tasks not available in Storage Manager.
Introduction Accessing the CLI This section discusses accessing the CLI in various operating systems. Accessing the CLI from the MS-DOS Prompt To access the CLI from the MS-DOS prompt, move to the directory containing the afacli executable and then type afacli, as in the following example: C:\>cd Program Files\Adaptec_SCSI_RAID\AAC C:\Program Files\Adaptec_SCSI_RAID\AAC>afacli Accessing the CLI in Windows This section discusses the various methods for accessing the CLI in Windows.
Introduction Accessing CLI in NetWare To access the CLI from the NetWare server console, type aaccli at the prompt. When the system displays the CLI> prompt, which indicates that you can now use CLI commands. Terminology This section discusses terminology used in this Appendix. Adaptec 2410SA/2810SA Controllers Only In the device ID format C:ID:L: ■ C represents Channel, which is always zero. ■ ID represents Port ID, or Port number, on the SATA RAID controller. This is the only value that is used.
Introduction ■ Stripe, chunk—Contiguous set of data distributed across all the disks in an array. A striped array distributes data evenly across all members in equal-sized sections called stripes. ■ Free or available space—Space on an initialized disk that is not in use. ■ Partition—Contiguous area of a physical drive that makes up some or all of an array.
Introduction To exit subcommand mode, press Enter. (You may have to press Enter more than once to exit subcommand mode.) ■ CLI-unique commands For NetWare systems, the following commands are unique to the CLI in that you use these commands when accessing the CLI from the NetWare server console: ■ ■ open ■ close ■ exit ■ toggle_more Comments—If the first non-blank character on a line in the CLI is an exclamation point (!), the rest of the line will be ignored.
Introduction Action An action specifies an operation to be performed by the CLI, such as open, create, list, exit, or show. An action is a required element, except in subcommand mode. In most cases, actions are preceded by a class and followed by an object, switches, and parameters. Object An object describes what to use in an action. Examples include mirror, volume, mstripe, and drive_letter. Switch A switch is an element applied to a command that allows a variation of the command.
Introduction Parameter Although some commands have optional parameters, parameters are usually mandatory. You must place optional parameters after mandatory parameters at the end of the command. For example, the array remove failover command has one required scsi_device parameter and additional optional scsi_device parameters: array remove failover {array} {scsi_device} [{scsi_device}...]. As with switch values, parameters can be of only one type.
Introduction integer An integer is a positive or negative number that has a value between –263 and (263 – 1). Although the valid range is usually much smaller, all integers have 64 bits of precision and do not contain decimal points. You can specify an integer as a mathematical equation that uses an asterisk (*) to multiply, a plus sign (+) to add, a minus sign (–) to subtract, a slash (/) to divide, and parentheses [( )] to specify order of operations.
Introduction Table 1-2 lists examples of valid integers and their corresponding values: Table 1-2 Integers and Values (in Decimal) Integer Value (in decimal) 219 219 3*4 12 (5+3*24) 192 (5+(3*24)) 77 0x123 291 (12+52h+1010z) 104 100M 104,857,600 2G 2,147,483,648 string You can specify a text string with or without quotation marks. If spaces are needed, however, the string must be specified with quotation marks; otherwise, the CLI interprets spaces as delimiters.
Introduction scsi_device Specifies a SCSI device. SCSI device descriptions have three parts: SCSI channel number, SCSI device ID, and SCSI device logical unit number (LUN). The following syntax defines the scsi_device parameter: ({integer},{integer},{integer}) Each integer corresponds to one component of a SCSI device descriptor or specifier: the first integer is the SCSI channel number, the second integer is the SCSI device ID, and the third integer is the SCSI device LUN.
Introduction Table 1-5 displays valid SCSI device specifiers. The second two examples contain a default LUN number, and the last two examples contain default channel and LUN numbers. You can specify these defaults using the disk set default command (see page 5-11).
Introduction Table 1-6 lists valid free_space specifiers.
Introduction Status Information When invoked from the MS-DOS prompt or the Windows Start button, the CLI displays status information in the title bar of a DOS command prompt window as it executes an asynchronous command. On NetWare, the status information appears in a different window. On UNIX systems, the CLI displays this status information at the bottom of the CLI window.
Introduction Table 1-7 Function Values (Continued) Value Meaning MMR Merge a broken mirror task. The array merge command causes the MMR value to display. MSC array scrub task. The array scrub command causes the MSC value to display. NTF array format task with an NTFS file system specified. The array format command with the /file_system switch set to NTFS causes the NTF value to display. R5R RAID-5 rebuild task. R5S RAID 5 array create task with the scrub method specified.
Introduction Table 1-8 describes the state values that the State item can display. Table 1-8 State Values State Meaning BAD The task failed and is no longer running. DNE The task successfully completed or the task is no longer running (that is, the task is done). RUN The task is running. SUS The task was suspended. Typically, you suspend a task with the task suspend command. UNK The controller reported an unknown status for the task.
2 General Control Commands In this Chapter close 2-2 exit 2-3 help, ? 2-4 history_size 2-5 open 2-6 reset_window 2-8 toggle_more 2-9 The CLI general control commands are discussed in alphabetical order and use the following syntax: command [subcommand] [/switch{=value}] [parameter] 2-1
General Control Commands close To close the currently opened controller when all access is completed, use the close command.
General Control Commands exit To close the currently opened controller and exit the CLI, use the exit command.
General Control Commands help, ? To invoke general or topical Help commands, use the help command or the ? (question mark). Syntax ? [{command}] {command} ? help [/full] [{command}] help [/full} {command subset} Parameters If the command has more subcommands, help lists the subcommands and their functions. If a complete command is used, such as array list, the CLI help displays all possible switches. Switches /full Displays all relevant commands along with the command format and all command switches.
General Control Commands history_size To set the size of the command history buffer, use the history_size command. Command Availability This command is supported only on UNIX. Syntax history_size {buffer_size} Parameters {buffer_size} Specifies the size of the command history buffer. The default size is 200.
General Control Commands open To open a controller, use the open command. The open command prepares a particular controller for access by the CLI. If you specify this command when another controller is open during a particular command session, the CLI closes the currently opened controller and then opens the specified controller. Syntax open [/readonly{=boolean}] [/domain{=string}] {string} Parameters {string} Specifies the computer name and the controller you want to open.
General Control Commands /domain{=string} Specifies the domain (the local domain or a trusted domain) in which the specified computer that contains the controller resides. If you do not specify this switch, the CLI assumes the local domain. This switch is supported on Windows only. Note: You can open controllers for read-write access in any GUI or CLI session only once per controller. Thereafter, any user can open and access the previously opened controller only in read-only mode.
General Control Commands reset_window To reset the window, use the reset_window command. Command Availability This command is supported only on UNIX.
General Control Commands toggle_more To turn on or off the functionality, use the toggle_more command. After you type toggle_more on the NetWare console, the command displays an appropriate message indicating whether the functionality is on or off. Command Availability This command is supported only on NetWare.
3 container Commands In this Chapter container add_level 3-3 container create mirror 3-5 container create mmirror 3-8 container create mstripe 3-12 container create mvolume 3-17 container create raid5 3-21 container create stripe 3-27 container create volume 3-32 container delete 3-37 container extend file_system 3-40 container extend mvolume 3-43 container extend volume 3-47 container list 3-50 container lock 3-59 container move 3-61 container promote 3-63 container readonl
container Commands container remove drive_letter 3-78 container remove failover 3-80 container remove file_system 3-82 container remove global_failover 3-84 container restore RAID5 3-86 container scrub 3-88 container set cache 3-91 container set failover 3-95 container set global_failover 3-97 container set io_delay 3-99 container set label 3-101 container show cache 3-103 container show failover 3-108 container split 3-109 container unlock 3-112 container unmirror 3-114 The
container Commands container add_level To create a multilevel volume set from an existing array by adding a volume set on top of the array, use the container add_level command. The existing array cannot be a multilevel array. The container add_level command enables dynamic expansion of an array and can be executed even while an array is in use. After executing the command, you can use the container extend mvolume command to add more space.
container Commands Use the container list command after using the container add_level command to display information about the multilevel volume set, as in the following example: AAC0>container list Executing: container list Num Total Oth Dr Label Type Size Ctr -- ----- ------ ------ --0 Volume 45MB 63 Stripe 45MB Stripe Scsi Partition Size Usage C:ID:L Offset:Size ------ ------- ------ ------------None 32KB 0:02:0 64.0KB: 15.0MB 0:03:0 64.0KB: 15.0MB 0:04:0 64.0KB: 15.
container Commands container create mirror To create a mirror set from a single-partition volume set and freespace, use the container create mirror command. Any data on the original volume set remains intact during mirror creation and the user sees no interruption in service. If you created a mirror set on a NetWare server, you can run the list devices command on the NetWare console to verify its creation and then create the necessary NetWare disk partitions and volumes.
container Commands Switches /wait{=boolean} Specifies whether to create the mirror set synchronously. If you set this switch to TRUE, the command prompt does not return until the mirror-set creation completes. If you set this switch to FALSE, the mirror-set creation starts asynchronously and the command prompt returns immediately. /io_delay{=integer} Specifies the number of milliseconds the controller waits between the I/Os required to create the mirror set.
container Commands Use the container list command after the container create mirror command completes execution to display information about the mirror set, as in the following example: AAC0>container list Executing: container list Num Total Oth Stripe Scsi Partition Dr Label Type Size Ctr Size Usage C:ID:L Offset:Size -- ----- ------ ------ --- ------ ------- ------ ------------0 Mirror 10MB NTFS 0:02:0 64.0KB: 10.0MB 0:03:0 64.0KB: 10.
container Commands container create mmirror To create a multilevel array of mirror sets from a multilevel array of single-partition volume sets and freespace, use the container create mmirror command. Typically, you use this command after promoting a volume set built from multiple partitions with the container promote command. The container create mmirror command is fully dynamic. If you use this command, users will not see any change or experience any interruption in service.
container Commands {scsi_device} Specifies the ID for the SCSI device whose freespace you want to use to create the multilevel array of mirror sets. The size of this freespace should be greater than or equal to the size of the first underlying volume set. A SCSI ID consists of a SCSI bus number (e.g., 0, 1, 2, 3, etc.), SCSI device ID (0 through 15 inclusive), and SCSI device logical unit number (0 through 7 inclusive).
container Commands Examples Before creating a multilevel array of mirror sets, use the container list command to obtain information about any existing arrays.
container Commands The following list describes the change to the display as the result of creating a multilevel array of mirror sets with the container create mmirror command: ■ The Dr column is blank to indicate that the newly created mirror sets (63 and 62) do not have a drive letter assigned to them. ■ The Type column displays Mirror for arrays 63 and 62 to indicate that the underlying arrays are mirror sets.
container Commands container create mstripe To create a multilevel stripe set from equally sized arrays, use the container create mstripe command. The top level of a multilevel stripe array can only be a stripe set.
container Commands {container}... Specifies the ID number or numbers (0 to 63) of one or more arrays from which you want to create the multilevel stripe set. You can use up to 16 arrays to create a multilevel stripe set. All specified arrays must be the same size as the first container parameter and separated by blank spaces. Switches /stripe_size{=integer} Note: This keyword does not support RAID 50 arrays because RAID 50 arrays support only a stripe size of 64 KB.
container Commands The following example shows how to create a multilevel stripe set from two equally sized arrays, using the default stripe size of 64 KB. In this example, the two equally sized arrays are mirror sets: AAC0>container create mstripe 0 1 Executing: container create mstripe 0 1 container 0 created On UNIX systems, the message displayed after you execute the container create mstripe command includes the root special file associated with the newly created multilevel stripe set.
container Commands ■ The Total Size column displays the total size for the multilevel stripe set. This size is the total of all the underlying arrays. In the example, the total size for array 0 (the multilevel stripe set) is the sum of the two underlying arrays (30 MB). The Total Size column also displays the sizes of all the underlying arrays. In the example, the size of array 63 (15.0 MB) and array 62 (15.0 MB) were specified when the mirror sets were created with the container create mirror command.
container Commands Related Commands container commands: ■ container create mirror (page 3-5) ■ container list (page 3-50) ■ container set label (page 3-101) 3-16
container Commands container create mvolume To create a multilevel volume set, use the container create mvolume command.
container Commands {container}... Specifies the ID (0 to 63) of one or more additional arrays from which you want to create the multilevel volume set. You can use up to 16 arrays. Typically, the additional arrays you specify are the same type as the first array. For example, if the first array is a stripe set then any subsequent arrays are also stripe sets. Switches /label{=string} Specifies a label to be assigned to the newly created multilevel volume set.
container Commands Use the container list command after using the container create mvolume command to display information about the multilevel array of volume sets after you create it, as in the following example: AAC0>container list Executing: container list Num Total Oth Dr Label Type Size Ctr -- ----- ------ ------ --0 Volume 60.0MB 63 Stripe 45MB 62 Stripe 15MB Stripe Scsi Partition Size Usage C:ID:L Offset:Size ------ ------- ------ ------------None 64KB 0:02:0 64.0KB: 15.0MB 0:03:0 64.0KB: 15.
container Commands ■ The Stripe Size column displays the stripe size for each of the arrays that make up the multilevel volume set. You specify the stripe size when you create stripe sets and RAID 5 arrays. In the example, the stripe size is 32 KB. ■ The Usage column displays None to indicate that the newly created multilevel volume set does not have a file system on it. To create an NTFS or FAT file system on an array, use the container format command.
container Commands container create raid5 To create a RAID 5 array, use the container create raid5 command. The RAID 5 array must have a minimum of three disks. When creating the RAID 5 array, you must initialize the array parity by using the scrub method (the /scrub switch). Notes If you created a RAID 5 array you can run the list devices command on the NetWare console to verify its creation and then create the necessary NetWare disk partitions and volumes.
container Commands Switches /cache{=boolean} Specifies whether to enable the array’s raw array cache. You can use this switch only if a native operating system’s file system (for Windows, the NTFS or FAT file system) resides on the array. If you do not want to enable the RAID 5 array’s raw array cache when you create it, you can do so later by using the container set cache command. In fact, the container set cache command gives you more control in setting the NVRAM write-back cache.
container Commands /clear{=boolean} Specifies whether to set up the parity during RAID-5 creation by clearing the entire RAID 5 array. If you specify TRUE, the command sets up the parity during RAID-5 creation by clearing the RAID 5 array. The default is FALSE; the command does not clear the entire RAID 5 array. If you use neither this switch nor the /scrub switch, the command uses the scrub method by default.
container Commands /scrub{=boolean} Specifies whether to set up the parity during RAID-5 creation by scrubbing the RAID 5 array. If you set this switch to TRUE, the command sets up the parity by scrubbing the RAID 5 array. Although the drive is immediately available, it is not parity-protected until the background scrub action completes. This switch defaults to TRUE. If you set this switch to FALSE, the command will set up parity by clearing the RAID 5 array.
container Commands As the command executes, note that the title bar of the MS-DOS window displays the status of the command. For example: Stat:OK!Task:101,Func:R5S Ctr:0,State:RUN 84.6% For further details on status information, see page 1-13. On UNIX systems, the message displayed after you execute the container create raid5 command includes the root special file associated with the newly created RAID 5 array.
container Commands ■ The Usage column displays None to indicate that the newly created RAID 5 array does not have a file system on it.To create an NTFS or FAT file system on an array, use the container format command. ■ The State column displays the state of an array, which in the example shows Unprot to indicate that the RAID 5 array is not yet redundant. This means that the command has not completed the creation of the RAID 5 array.
container Commands container create stripe To create a stripe set from freespace, use the container create stripe command. Notes If you created a stripe set you can run the list devices command on the NetWare console to verify its creation and then create the necessary NetWare disk partitions and volumes. For information on how to create partitions and volumes, see the appropriate NetWare documentation.
container Commands Switches /cache{=boolean} Specifies whether to enable the array’s raw array cache.You can use this switch only if a native operating system’s file system (for Windows, the NTFS or FAT file system) resides on the array. If you do not want to enable the stripe set’s raw array cache when you create it, you can do so later by using the container set cache command. In fact, the container set cache command gives you more control in setting the NVRAM write-back cache.
container Commands /label{=string} Specifies a label to be assigned to the newly created array. You can specify a maximum of sixteen characters for the label. If you do not specify the switch, it defaults to no label. If you do not specify a label, you can do so later by using the container set label command. Note that this label is not the label that displays in Windows Explorer. The label displayed by Windows Explorer comes from the label specified with the container format command.
container Commands Use the container list command after using the container create stripe command to display information about the array, as in the following example: AAC0>container list Executing: container list Num Total Oth Stripe Scsi Partition Dr Label Type Size Ctr Size Usage C:ID:L Offset:Size -- ----- ------ ------ --- ------ ------- ------ ------------0 Stripe 45.0MB 64KB None 0:02:0 64.0KB: 15.0MB 0:03:0 64.0KB: 15.0MB 0:04:0 64.0KB: 15.
container Commands ■ The Partition Offset: Size column displays the partition offset(s) and the size(s) for the disk(s) whose associated freespaces you used to create the array. In this example, the display shows 64.0KB:15MB, 64.0KB:15.0MB, and 64.0KB:15.0MB.
container Commands container create volume To create a volume set from freespace, use the container create volume command. Notes If you created a volume set you can run the list devices command on the NetWare console to verify its creation and then create the necessary NetWare disk partitions and volumes. For information on how to create partitions and volumes, see the appropriate NetWare documentation.
container Commands {scsi_device},{free_space}... Specifies any additional SCSI devices and associated freespaces used to create the volume set. A volume set can have a maximum of 16 partitions (or freespaces, since each freespace becomes a partition). Note that you must explicitly specify the entire ID for any additional SCSI devices (the SCSI channel number, device ID, and device logical unit number). Switches /cache{=boolean} Specifies whether to enable the array’s raw array cache.
container Commands /label{=string} Specifies a label to be assigned to the newly created volume set. You can specify a maximum of sixteen characters for the label. If you do not specify the switch, it defaults to no label. If you do not specify a label, you can do so later by using the container set label command. Note that this label is not the label that displays in Windows Explorer. The label displayed by Windows Explorer comes from the label specified with the container format command.
container Commands Use the container list command after executing the container create volume command to display information about the volume set, as in the following example: AAC0>container list Executing: container list Num Total Oth Stripe Scsi Partition Dr Label Type Size Ctr Size Usage C:ID:L Offset:Size -- ----- ------ ------ --- ------ ------- ------ ------------0 Volume 15.0MB None 0:02:0 64.0KB: 15.
container Commands ■ container list (page 3-50) ■ container promote (page 3-63) ■ container set cache (page 3-91) ■ container set label (page 3-101) disk commands: ■ disk show space (page 5-26) 3-36
container Commands container delete To delete an array from the currently opened controller, use the container delete command. Notes If you are deleting an array on a NetWare system, you must first go to the NetWare console and remove the corresponding volume and partition. For information on how to perform these operations, see the appropriate NetWare documentation.
container Commands /unconditional{=boolean} Specifies whether to delete the array, even if the array has open files on it. If you specify TRUE, the command deletes the array even if it has open files on it. The switch defaults to FALSE (that is, the container delete command does not delete an array that has open files on it). WARNING: Unconditionally deleting an array that is in use can cause a system crash under some circumstances.
container Commands Related Commands container commands: ■ container create mirror (page 3-5) ■ container create mmirror (page 3-8) ■ container create mstripe (page 3-12) ■ container create mvolume (page 3-17) ■ container create raid5 (page 3-21) ■ container create stripe (page 3-27) ■ container create volume (page 3-32) ■ container list (page 3-50) 3-39
container Commands container extend file_system To extend a file system so that it uses all of the space in an array, use the container extend file_system command. This command allows you to extend the NTFS file system. Typically, you use this command after extending an array (by adding a level to it with the container add_level command and, possibly, by extending it with the container extend mvolume command).
container Commands Parameters {container} Specifies the ID number (0 to 63) of the array whose file system you want to extend. Examples Typically, you would use the container extend file_system command after adding a level to an array and, perhaps, after extending a multilevel volume set.
container Commands The following example extends the NTFS file system to make use of the additional arrays: AAC0>container extend file_system 0 Executing: container extend file_system 0 The system has been marked to expand the file system on the next reboot. Reboot the system to get the file system to expand to show the new space. Use the container list command after using the container extend file_system command to display information about the array after you extend a file system.
container Commands container extend mvolume To extend a multilevel volume set by adding one or more arrays to it, use the container extend mvolume command. Any file system on the multilevel volume set remains intact, and can be extended to include the added space. Command and Switch Availability This command is supported on Windows. Syntax container extend mvolume {container_to_extend} {container} [{container}...] Parameters {container_to_extend} Specifies the ID number (0 to 63) of the array to extend.
container Commands Examples Before extending a multilevel volume set, use the container list command to obtain information about any existing arrays. As the following example shows, there is an array 0 (a multilevel volume set) on this controller. In addition, the example shows array 1 and array 2 (both volume sets created with the container create volume command).
container Commands The following list describes the change to the display as the result of extending a multilevel array with the container extend mvolume command: ■ The Num Label column continues to display the ID number (0) of the volume set previously created with the container create volume command and the ID number (63) of the volume set previously created with the container add_level command.
container Commands Related Commands container commands: ■ container add_level (page 3-3) ■ container create mvolume (page 3-17) ■ container create volume (page 3-32) ■ container extend file_system (page 3-40) ■ container list (page 3-50) disk commands: ■ disk remove dead_partitions (page 5-10) 3-46
container Commands container extend volume To extend a volume set by adding freespace to it, use the container extend volume command. The file system on the volume set remains intact and can be extended to include the added space. Command and Switch Availability This command is supported on Windows. Syntax container extend volume {container} [{free_space}] [{free_space}...] Parameters {container} Specifies the ID number (0 to 63) of the array (volume set) to extend.
container Commands Before extending the volume set, you might want to use the disk show space command to display space usage information on the SCSI devices from which you plan to add freespace. The following example extends a volume set by adding freespace from two SCSI devices: AAC0>container extend volume 1 ((2,0,0), 32M) ((2,1,0), 32M) Executing: container extend volume 1 ((CHANNEL=2,ID=0,LUN=0),33,554,432)((CHANNEL=2,ID=1,LUN=0),33,554,432) container 1 expanded.
container Commands ■ The Partition Offset:Size column displays the partition offset(s) and size(s) for the partition(s) associated with the extended volume set. In the example the partition offsets and sizes are 64.0 KB and 32.0 MB. If a partition is dead, the “:” (colon) in the Partition Offset:Size column changes to a “!” (exclamation point). See the disk remove dead_partitions (page 5-10) command for more information on dead partitions.
container Commands container list To display information about one or all arrays on the controller, use the container list command. The display contains such information as the container’s ID number and other useful information. Typically, you use the container list command to obtain specific information about arrays prior to using other arrayrelated commands.
container Commands Examples The following example shows how to list nondetailed information about all arrays on the system: AAC0>container list Executing: container list Num Total Oth Dr Label Type Size Ctr -- ----- ------ ------ --0 Volume 15.0MB 1 Stripe 45.0MB Stripe Size Usage ------ ------None 32KB None Scsi C:ID:L -----0:02:0 0:02:0 0:03:0 0:04:0 Partition Offset:Size ------------64.0KB: 15.0MB 15.0MB: 15.0MB 64.0KB: 15.0MB 64.0KB: 15.
container Commands This column also displays the label assigned to the array when the array was created. If no label was assigned to the array then no label appears in the column.
container Commands The Reconf array type does not appear on UNIX systems. The Total Size Column This column displays the size of the array. You specify this size when creating the array with one of the container createrelated commands. The Stripe Size Column This column displays the stripe size for the array. You specify the stripe size when using the container create mstripe, container create raid5, and container create stripe commands.
container Commands The Scsi C:ID:L Column This column displays the SCSI channel number, the SCSI ID, and the SCSI logical unit number for the SCSI disk or disks on which the array was created. The Partition Offset:Size Column This column displays the offset and size for the underlying partitions. If a partition is dead, the “:” (colon) in the Partition Offset:Size column changes to a “!” (exclamation point). See the disk remove dead_partitions (page 5-10) command for more information on dead partitions.
container Commands The RO Column This column displays the letters RO if the array is read-only. Otherwise, if the array is read-write the column displays a blank space. You can explicitly make an array read-only and read-write with the container readonly and container readwrite commands. Some CLI commands cause an array to temporarily become readonly without the use of the container readonly command. The Lk Column This column displays the letter L if the array is locked.
container Commands Table 3-4 Task Types (Continued) Task Meaning Rebuild A rebuild task is running on the specified array. Typically, the rebuild task runs when the controller is in a rebuild for a redundant array (RAID 5 array, mirror set, or multilevel array of mirror sets). Reconfg An array reconfigure task is running on the specified array. When the array reconfigure task completes, the specified array becomes a different array (for example, from a volume set to a stripe set).
container Commands The Done % Column This column displays a running percentage value that indicates the progress of the currently running task. The display shows the percentage in tenths of a percent increments. The currently running task is complete when the Done % column displays 100%. The Ent Column This column displays the number of elements associated with each array. The maximum is 16 elements.
container Commands The Boot Device Column This column displays a value that indicates whether the array resides on the boot device. An X appears in the column if the array resides on the boot device. Otherwise, if the array does not reside on the boot device, no value appears in the column. The Boot Device column does not appear on UNIX systems. The System Files Column This column displays a value that indicates whether the array resides on the system device.
container Commands container lock ! Caution: Use the container lock command only under the direction of technical support. To lock an array into volatile memory space on the currently opened controller, use the container lock command. When an array is locked into volatile memory space, the container reconfigure command has no effect. A locked array cannot be moved, deleted, made read-only, or used to create a multilevel array.
container Commands Use the container list command (with the /full switch) after using the container lock command to display information about the array you just locked, as in the following example: AAC0>container list /full Executing: container list /full=TRUE Num Total Oth Stripe Scsi Dr Label Type Size Ctr Size Usage C:ID:L -- ----- ------ ------ --- ------ ------- -------F: 0 Volume 10.
container Commands container move To renumber an array, use the container move command. If another array already has the new number, the command returns an error. Notes A controller currently supports 24 visible arrays. A visible array is an array that is visible to the operating system and users. Visible arrays are identified with container IDs 0 through 23. Container IDs 24 through 63 are reserved for hidden arrays.
container Commands Examples Before renumbering an array, use the container list command to obtain information about any existing arrays. As the following example shows, there is an array 0 (a volume set) on this controller: AAC0>container list Executing: container list Num Total Oth Stripe Scsi Partition Dr Label Type Size Ctr Size Usage C:ID:L Offset:Size -- ----- ------ ------ --- ------ ------- ------ ------------F: 0 Volume 20.0MB NTFS 0:02:0 64.0KB: 10.0MB 0:03:0 64.0KB: 10.
container Commands container promote To create a multilevel volume set from a stripe set or volume set, use the container promote command. In this case, the resulting array is an array of single-partition volume sets, each of which has a single partition from the original array. Typically, you use the container promote command as part of a process to provide fault tolerance for existing volume sets.
container Commands As the following example shows, there is an array 0 (a stripe set) on this controller: AAC0>container list Executing: container list Num Total Oth Dr Label Type Size Ctr -- ----- ------ ------ --0 Stripe 45.0MB Stripe Scsi Partition Size Usage C:ID:L Offset:Size ------ ------- ------ ------------32KB None 0:02:0 64.0KB: 15.0MB 0:03:0 64.0KB: 15.0MB 0:04:0 64.0KB: 15.
container Commands ■ The Scsi C:ID:L column displays the SCSI channel number, SCSI device ID, and SCSI logical unit number for the underlying arrays. In the example, array 63 resides on disk 0:02:0, array 62 resides on disk 0:03:0, and array 61 resides on disk 0:04:0. ■ The Partition Offset:Size column displays the offset and size for the underlying arrays’ partitions. In the example, arrays 63, 62, and 61 have 64.0 KB offsets and 15.0 MB sizes.
container Commands container readonly To change an array’s read-write status to read-only status, use the container readonly command. Subsequent modifications to the data on the array are prohibited. To use the container readonly command, the array cannot be in use by any application. Syntax container readonly {container} Parameters {container} Specifies the ID number (0 to 63) of the array to make readonly.
container Commands Use the container list command (with the /full switch) after using the container readonly command to display information about the array you just made read-only, as in the following example: AAC0>container list /full Executing: container list /full=TRUE Num Total Oth Stripe Scsi Dr Label Type Size Ctr Size Usage C:ID:L -- ----- ------ ------ --- ------ ------- -------F: 0 Volume 10.
container Commands container readwrite To change an array’s read-only status to read-write status, use the container readwrite command. Subsequent modifications to the data on the array are allowed. To use the container readwrite command, none of the array’s files can be open. Syntax container readwrite {container} Parameters {container} Specifies the ID number (0 to 63) of the array to make readwrite.
container Commands Note that the example eliminates some items in the container list display so that you can see an example of the RO column. As a result of making an array (in this example, array 0) read-write with the container readwrite command, the RO column displays blank (instead of an RO) to indicate that the specified array is now read-write.
container Commands container reconfigure To change the configuration of an array, use the container reconfigure command. The container reconfigure command allows you to perform the following operations: ■ Transform an array from one type to another type You can transform an array from one type to another type. For example, you can transform a RAID 1 to a RAID 5 array. You specify the appropriate switches that the container reconfigure command provides to transform an array.
container Commands ■ Move partitions to other disks You can move an array’s partitions to other disks by specifying the appropriate switches with a valid partition or partitions. For example, you can move three entries of a RAID 5 array to new disks. You can combine the previously listed operations. Notes Some reconfigure operations result in destination sizes slightly different than what you specified.
container Commands {scsi_device}... Specifies one or more SCSI devices. Typically, you specify one or more SCSI devices when adding more drives to an array or moving an array’s partitions. A SCSI ID consists of a SCSI channel number (for example, 0, 1, 2, 3, etc.), a SCSI device ID (0 through 15 inclusive), and a SCSI device logical unit number (0 through 7 inclusive). For further details, see scsi_device on page 1-10.
container Commands /extend_fs{=boolean} Specifies whether to extend the file system so that it occupies the entire reconfigured array. If you specify TRUE, the command adds no new freespace and extends the file system so that it occupies the entire reconfigured array. (The command extends the file system after completing the reconfigure operation.) If you specify FALSE, the command adds freespace to the reconfigured array and does not extend the file system to occupy the entire reconfigured array.
container Commands /raid5{=boolean} Specifies whether to reconfigure the existing array into a RAID 5 array. If you specify TRUE, the command reconfigures the existing array into a RAID 5 array. If you specify FALSE, the command does not reconfigure the existing array into a RAID 5 array. This switch defaults to FALSE. /raid10{=boolean} Specifies whether to reconfigure the existing array into a RAID 10 array. If you specify TRUE, the command reconfigures the existing array into a RAID 10 array.
container Commands Examples Use the container list command to obtain information about any existing arrays. As the following example shows, there is an array 0 (a mirror set) and an array 1 (a volume set) on this controller: AAC0>container list Executing: container list Num Total Oth Stripe Dr Label Type Size Ctr Size Usage -- ----- ------ ------ --- ------ ------0 Mirror 15.0MB None Tigris E: 1 Volume 15.0MB NTFS Scsi C:ID:L -----1:02:0 1:03:0 1:00:0 Partition Offset:Size ------------64.0KB: 15.0MB 64.
container Commands ■ container extend file_system (page 3-40) ■ container list (page 3-50) 3-76
container Commands container release_cache To release the cache buffers associated with a specific array, use the container release_cache command. When a disk fails or you remove a disk, the cache buffers associated with specific arrays remain locked on the controller. This allows the opportunity for the disk to come back online or gives you the opportunity to replace the disk. In this case the arrays regain the previously locked buffers.
container Commands container remove drive_letter To remove a drive letter, use the container remove drive_letter command. To use the container remove drive_letter command, none of the array’s files can be open. Command Availability This command is supported on Windows. Syntax container remove drive_letter {string} Parameters {string} Specifies the drive letter to remove. The colon (:) after the drive letter is optional.
container Commands As the result of removing a drive letter from an array (in this example, array 0) with the container remove drive_letter command: ■ The Dr column no longer displays the drive letter assigned in a previous use of the container assign drive_letter command. In this example, the letter F no longer appears in the Dr column.
container Commands container remove failover To remove one or more failover disks that were assigned to an array using the container set failover command, use the container remove failover command. Syntax container remove failover {container} {scsi_device} [{scsi_device}...] Parameters {container} Specifies the ID number (0 to 63) of the array whose assigned failover disk(s) you want to remove.
container Commands Use the container show failover command after removing a failover disk from an array’s failover disk list with the container remove failover command to display information about the array’s failover disk list, as in the following example: AAC0>container show failover Executing: container show failover container Scsi C:ID:L --------- ---------------------------------0 0:04:0 As the display shows, SCSI device (0,03,0) is no longer in the failover disk list for array 0.
container Commands container remove file_system To remove the file system from an array, use the container remove file_system command. Use this command when the file system on the array is no longer needed. This command fails if there are open files on the array. Command Availability This command is supported on Windows. Syntax container remove file_system {container} Parameters {container} Specifies the ID number (0 to 63) of the array from which you want to remove the file system.
container Commands The following example removes the file system from array 0: AAC0>container remove file_system 0 Executing: container remove file_system 0 Use the container list command after removing a file system from an array with the container remove file_system command to display information about the container, as in the following example: AAC0>container list Executing: container list Num Total Oth Stripe Scsi Partition Dr Label Type Size Ctr Size Usage C:ID:L Offset:Size -- ----- ------ ------ --
container Commands container remove global_failover To remove one or more failover disks that were assigned to all arrays through the container set global_failover command, use the container remove global_failover command. Syntax container remove global_failover {scsi_device} [{scsi_device}...] Parameters {scsi_device} Specifies the ID for the SCSI device that you want to remove as a failover disk for all arrays.
container Commands Use the container show failover command after removing a failover disk from an array’s failover disk list with the container remove failover command to display information about the array’s failover disk list, as in the following example: AAC0>container show failover Executing: container show failover container Scsi C:ID:L --------- ---------------------------------GLOBAL 1:03:0 0 --- No Devices Assigned --- As the display shows, SCSI device (1,2,0) is no longer in the failover disk lis
container Commands container restore RAID5 To restore a RAID 5 array, use the container restore RAID5 command. Typically, you use this command to restore a RAID 5 array that contains one or more dead partitions. This command does not always succeed; therefore, use it only if all other measures fail. One situation where the command might prove useful is for those situations where you may have inadvertently pulled a drive and then almost immediately put it back.
container Commands Use the container list command after using the container restore RAID5 command to display information about the RAID 5 array: AAC0>container list Executing: container list Num Total Oth Dr Label Type Size Ctr -- ----- ------ ------ --0 RAID-5 30.0MB Stripe Scsi Partition Size Usage C:ID:L Offset:Size ------ ------- ------ ------------64.0KB None 0:02:0 64.0KB: 10.0MB 0:03:0 64.0KB: 10.0MB 0:04:0 64.0KB: 10.0MB 0:05:0 64.0KB: 10.
container Commands container scrub To scrub a redundant array, use the container scrub command. A mirror set, a multilevel array of mirror sets, and a RAID 5 array are examples of redundant arrays. For a mirror set or a multilevel array of mirror sets, this means the command reconstructs the data on both mirror halves (partitions), if found to be different. For RAID 5 arrays, the command recalculates and replaces, if necessary, the parity information.
container Commands /wait{=boolean} Specifies whether the command performs the scrub action synchronously or asynchronously. If you set this switch to TRUE, the command performs the scrub action synchronously, which means the command prompt does not return until the scrub action completes. If you set this switch to FALSE, the command performs the scrub action asynchronously, which means the command prompt returns immediately.
container Commands Related Commands container commands: ■ container create mirror (page 3-5) ■ container create mmirror (page 3-8) ■ container create raid5 (page 3-21) ■ container list (page 3-50) 3-90
container Commands container set cache To set cache parameters for a specific array, use the container set cache command. You can use this command only if a native operating system’s file system (for Windows, NTFS, or FAT) resides on the array. The CLI prevents you from setting cache parameters if the array is involved in a reconfiguration operation. The CLI disables the cache parameters on the array involved in a reconfiguration operation.
container Commands Switches /read_cache_enable{=boolean} Specifies whether to enable the read-ahead cache. If you set this switch to TRUE, the command enables the read-ahead cache for the specified array. This switch should always be enabled to optimize performance, unless your application-which is unlikely--is doing completely random reads. This switch defaults to TRUE. To disable the read-ahead cache for the specified array, set this switch to FALSE.
container Commands Table 3-5 summarizes the values for the /write_cache_enable and /unprotected switches: Table 3-5 Switch Values and Results /write_cache_enable Switch Setting /unprotected Switch Setting FALSE FALSE The NVRAM write-back cache setting for the specified array is disabled. FALSE TRUE Not allowed. An appropriate error message displays. TRUE FALSE The NVRAM write-back cache setting for the specified array is enabled when protected.
container Commands The following example sets cache parameters for array 0 by accepting all of the defaults: AAC0>container set cache 0 Executing: container set cache 0 After setting cache parameters for a specific array, use the container show cache command to display cache parameter information, as in the following example: AAC0>container show cache 0 Executing: container show cache 0 Global container Read Cache Size : 5345280 Global container Write Cache Size : 1970176 Read Cache Status : ENABLED Write
container Commands container set failover To assign an automatic failover disk(s) for a single array, use the container set failover command. If the array was already assigned a failover disk(s), the command adds the specified disk(s) to the array’s list of failover disk(s). Although all array types accept failover assignments, only mirror set and RAID 5 array (redundant) array types use the failover assignment if a disk fails. Syntax container set failover {container} {scsi_device} [{scsi_device}...
container Commands As the following example shows, there is an array 0 (a mirror set) on this controller: AAC0>container list Executing: container list Num Total Oth Stripe Scsi Partition Dr Label Type Size Ctr Size Usage C:ID:L Offset:Size -- ----- ------ ------ --- ------ ------- ------ ------------D: 0 Mirror 10.0MB NTFS 0:02:0 64.0KB: 10.0MB 0:02:0 10.0MB: 10.0MB The following example assigns two SCSI failover disks to array 0.
container Commands container set global_failover To assign an automatic failover disk(s) for all arrays, use the container set global_failover command. If the array was already assigned a failover disk(s), the command adds the specified disk(s) to the array’s list of failover disk(s). Although all array types accept failover assignments, only mirror set and RAID 5 array (redundant) array types use the failover assignment if a disk fails. Syntax container set global_failover {scsi_device} [{scsi_device}...
container Commands The following example assigns two SCSI failover disks to all arrays. If you assign only one SCSI disk as a failover device, ensure that there is sufficient freespace. If you assign more than one SCSI disk as failover devices, you need ensure that only one of these disks has sufficient space. The reason for this is that the failover operation will look for the disk that has enough space.
container Commands container set io_delay To set the I/O delay for an array, use the container set io_delay command. You can specify an I/O delay for the following array-related tasks: ■ Creating a mirror set ■ Creating a multilevel array of mirror sets from a multilevel array of volume sets ■ Scrubbing a redundant array You use this command to change the I/O delay from the one you specified in the command for the previously listed tasks.
container Commands The following example creates a mirror set asynchronously and sets an I/O delay of 20 milliseconds for array 0. You need to perform the create mirror task asynchronously.
container Commands container set label To assign a new label to the specified array or to assign a label to an array that has no label, use the container set label command.
container Commands Examples Before assigning a label to a specific array, use the container list command to obtain information about any existing arrays.
container Commands container show cache To display the current cache parameters associated with a specific array, use the container show cache command. Typically, you use this command after setting cache parameters for a specific array using the container set cache command. Syntax container show cache {container} Parameters {container} Specifies the ID number (0 to 63) of the array whose associated cache parameters you want to display.
container Commands The following list provides a brief description of the items that appear as a result of using the container show cache command: ■ Global array Read Cache Size This item indicates the number of blocks devoted to the read cache. ■ Global array Write Cache Size This item indicates the number of blocks devoted to the write cache. ■ Read Cache Setting This item indicates whether the read cache is set for the array. The value ENABLED indicates the read cache is set for this array.
container Commands ■ Write Cache Status This item indicates the current status of the write cache for the array and, where appropriate, the status of the battery. Table 3-7 displays the values for Write Cache Status: Table 3-7 Values for Write Cache Status Value Meaning Active, not protected The status of the write cache for this array is as follows: ■ Active – The write cache can accept write operations from the array. ■ Not protected – The write cache is forceenabled.
container Commands Table 3-7 Values for Write Cache Status (Continued) Value Meaning Active, not protected, battery reconditioning The status of the write cache for this array is as follows: ■ Active – The write cache can accept write operations from the array. ■ Not protected – The write cache is forceenabled. Thus, the write cache accepts write operations even if write data could be lost due to no battery present or a bad battery on the controller.
container Commands Table 3-7 Values for Write Cache Status (Continued) Value Meaning Inactive, cache disabled The status of the write cache for this array is as follows: ■ Inactive – The write cache cannot accept write operations from the array. ■ Cache disabled – The user disabled the write cache by using the container set cache command and setting the appropriate switches.
container Commands container show failover To display a list of failover disks assigned to an array, use the container show failover command. You assign failover disks to an array with the container set failover command. Syntax container show failover [{container}] Parameters {container} Specifies the ID number (0 to 63) of the array whose assigned failover disk(s) you want to display. If you do not specify this parameter, the command displays all arrays and their assigned failover disk(s).
container Commands container split To split a mirror set or a multilevel array of mirror sets into two separate single-partition volume sets or two multilevel arrays of single-partition volume sets, use the container split command. Once this command completes execution, the two volume sets cannot be merged. Before using this command to split an array, shut down system applications (such as, databases) in order to flush application data to the controller.
container Commands Examples Before splitting a mirror set or a multilevel array of mirror sets, use the container list command to obtain information about any existing arrays.
container Commands ■ The Usage column displays NTFS to indicate that file systems exist on both arrays. You can create an NTFS or FAT file system on an array by using the container format command. ■ The Scsi C:ID:L column displays the SCSI device IDs for the disk on which the split mirror set (now two volume sets) reside. In the example, the SCSI device ID is 0:02:0.
container Commands container unlock ! Caution: Use the container unlock command only under the direction of Technical Support. To unlock an array so it can be moved, deleted, made read-only, and used to create a multilevel array, use the container unlock command. Syntax container unlock {container} Parameters {container} Specifies the ID number (0 to 63) of the array to unlock.
container Commands Use the container list command (with the /full switch) after using the container unlock command to display information about the unlocked array, as in the following example: AAC0>container list /full Executing: container list /full=TRUE Num Total Oth Stripe Scsi Dr Label Type Size Ctr Size Usage C:ID:L -- ----- ------ ------ --- ------ ------- -------F: 0 Volume 10.
container Commands container unmirror To unmirror a mirror set, resulting in a single-partition volume set and freespace, use the container unmirror command. Note that there is no equivalent command for a multilevel array of mirror sets. To unmirror a multilevel array of mirror sets, use this command for each underlying mirror set. Syntax container unmirror {container} Parameters {container} Specifies the ID number (0 to 63) of the mirror set to unmirror.
container Commands The following list describes the changes to the display as a result of using the container unmirror command: ■ The Type column displays Volume, which indicates that the mirror set was created from a Volume set. ■ The State column displays a blank space instead of Normal. The Normal state is displayed only for mirror sets. ■ The Scsi C:ID:L column displays only one SCSI ID. ■ The Partition Offset:Size column displays only one partition offset and size.
4 controller Commands In this Chapter controller details 4-2 controller firmware compare 4-6 controller firmware save 4-7 controller firmware update 4-9 controller list 4-10 controller pause_io 4-12 controller rescan 4-14 controller reset_scsi_channel 4-15 controller resume_io 4-16 controller set automatic_failover 4-17 controller set array_verify 4-19 controller show automatic_failover 4-21 controller show channels 4-22 controller show array_verify 4-25 4-1
controller Commands controller details To display details about the currently opened controller, use the controller details command. These details include the controller type and software revision levels.
controller Commands The Controller type Item The Controller type: item displays the controller type. In the example, the controller type is Adaptec 5400S. The Access Mode Item The Access Mode: item displays the access mode of the controller. The command displays the value READ-WRITE if you opened the controller for read-write operations. Otherwise, it displays READ-ONLY if you opened the controller for read-only operations.
controller Commands The Controller CPU Speed and Controller Memory Items The Controller CPU Speed: item (if available) displays the clock speed (in megahertz) of the CPU that resides on the controller. In the example, the speed is 233 Mhz. The Controller Memory: item displays the total amount of memory on the controller that programs and buffer data can use. In the example, the total memory is 48 MB. The Battery State Item The Battery State: item displays the state of the controller’s battery.
controller Commands Table 4-3 Component Revision Items (Continued) Component Revision Item Meaning Service: Displays the revision level of the network services software. This item displays only if the open controller resides on a remote computer. In the example, the revision level is 2.1-0 (Build #2881). Remote API: Displays the revision level of the API that the network services software uses on the remote computer. This item displays only if the open controller resides on a remote computer.
controller Commands controller firmware compare To compare the contents of each of the flash components on a controller to the corresponding image in a pair of user flash image (UFI) files and indicate whether they match, use the controller firmware compare command. Syntax controller firmware compare [/C[{controller_ID}][{controller_ID}...] [/D{UFI_file_path}] Switches /C{controller_ID} Specifies the controller ID representing the set of controllers on which to perform the firmware comparison.
controller Commands controller firmware save Note: This command is not supported in Linux. To save the contents of a controller’s flash in a pair of user flash image (UFI) files, use the controller firmware save command. The names of the pair of UFI files are based on the controller type and cannot be changed. Syntax controller firmware save [/C[{controller_ID}][{controller_ID}...
controller Commands Related Commands controller commands: ■ controller firmware compare (page 4-6) ■ controller firmware update (page 4-9) 4-8
controller Commands controller firmware update To update a controller’s flash components from the flash image data in a pair of user flash image (UFI) files, use the controller firmware update command. This command can update the flash components on a single controller or multiple controllers. Syntax controller firmware update [/C[{controller_ID}][{controller_ID}...
controller Commands controller list To list all controllers on a specified computer or display specific information about the currently opened controller, use the controller list command. Syntax controller list [/domain{=string}] [{string}] Parameters {string} Specifies the computer name from which you want to display a list of controllers or specific information about the currently opened controller. If you do not specify a computer name, the command displays only the controllers on the local computer.
controller Commands The Adapter Type item displays the controller type. In the example, the controller type is Adaptec 5400S. The Availability Item The Availability item displays the availability of the controller. Table 4-4 lists the values that can display in this item. Table 4-4 Controller Availability Status Controller Availability Meaning Unavailable The controller is not available. Unknown The controller availability is unknown. read only The controller is available for read-only access.
controller Commands controller pause_io To pause all I/O activity on the currently opened controller, use the controller pause_io command. While I/O activity is paused, you can make changes to devices attached to the controller without rebooting. For example, you can add, remove, or change SCSI channel assignments.
controller Commands Notes The controller automatically performs a rescan of the SCSI channel before the I/O is resumed. Using this command when there is a pagefile on an array could cause unexpected behavior. Use of the controller pause_io command is not permitted while an array task is running on the controller. (Use the task list command to display a list of currently running array tasks.
controller Commands controller rescan To rescan the SCSI channels on the currently opened controller and update all underlying structures, use the controller rescan command. The effect of this command is to verify currently connected disks or to recognize new disks added to the channel. This command rescans the disks for the arrays and loads the volatile array and the partition tables from disks again. If nothing on the disks has changed, controller rescan should have no visible effect.
controller Commands controller reset_scsi_channel To reset a specific SCSI channel, use the controller reset_scsi_channel command. Syntax controller reset_scsi_channel {integer} Parameters {integer} Specifies the controller channel (for example, 0, 1, 2, 3, etc.) on which you want to reset this SCSI channel. See the installation guide for your controller to determine the number of channels it actually supports.
controller Commands controller resume_io To rescan the SCSI channels and resume all I/O activity on the currently opened, previously paused controller, use the controller resume_io command. You use this command after pausing the controller with the controller pause_io command.
controller Commands controller set automatic_failover Automatic failover allows you to replace a failed disk with a replacement disk. The controller then automatically assigns the disk you insert as a failover disk without your having to first assign it with the array set failover or array set global_failover command. Note that the automatic failover feature works only with disks that reside in a SAF-TE enclosure management device.
controller Commands Syntax controller set automatic_failover [/failover_enabled{=boolean}] /failover_enabled{=boolean} Specifies whether to turn on or off automatic failover on the specified controller. You must set this switch to TRUE if you want to turn on automatic failover on the specified controller. To turn off automatic failover on the specified controller, set this switch to FALSE. The command defaults to TRUE, which means the command turns on automatic failover on the specified controller.
controller Commands controller set array_verify To enable or disable the array verify operation, use the controller set verify command. This command allows you to enable or disable the array verify operation for all arrays controlled by the specified controller. Syntax controller set array_verify [/verify_enabled{=boolean}] /verify_enabled{=boolean} Specifies whether to turn on or off the array verify feature on the specified controller.
controller Commands Related Commands controller commands: ■ controller show array_verify (page 4-25) 4-20
controller Commands controller show automatic_failover To display the automatic failover status (enabled or disabled) for the specified controller, use the controller show automatic_failover command.
controller Commands controller show channels To show all of the channels on a controller and the associated characteristics of each channel, use the controller show channels command. See the installation guide for your controller to determine the number of channels it actually supports.
controller Commands The Targets and Type Items The Targets item displays the number of SCSI device IDs not including the controller ID, which in the example is 15 for all channels. The Type item displays the SCSI channel type the channel is capable of supporting, which in the example is NoInfo for all channels. The controller show channels command can display the SCSI channel types listed in Table 4-5. Table 4-5 SCSI Channel Types Type Meaning Fast The controller supports SCSI channel type Fast.
controller Commands Related Commands controller commands: ■ controller details (page 4-2) 4-24
controller Commands controller show array_verify To display the array verify status (enabled or disabled) for the specified controller, use the controller show array_verify command. Syntax controller show array_verify Examples Before turning the array verify feature on or off, check its status by using the controller show array_verify command. The following example shows that the controller’s automatic failover is currently enabled.
5 disk Commands In this Chapter disk blink 5-2 disk initialize 5-3 disk list 5-5 disk remove dead_partitions 5-10 disk set default 5-11 disk set smart 5-13 disk show default 5-16 disk show defects 5-17 disk show partition 5-19 disk show smart 5-22 disk show space 5-26 disk verify 5-29 disk zero 5-31 Use the following syntax for disk commands: disk command [object] [/switch{=value}] [parameter] 5-1
disk Commands disk blink To cause a SCSI disk access light to blink (or stop blinking), use the disk blink command. Syntax disk blink [/wait{=boolean}] {scsi_device} {integer} Parameters {scsi_device} Specifies the ID for the SCSI disk you want to blink. A SCSI ID consists of a SCSI channel number (for example, 0, 1, 2, 3, etc.), SCSI device ID (0 through 15 inclusive), and SCSI device logical unit number (0 through 7 inclusive). For further details, see scsi_device on page 1-10.
disk Commands disk initialize To initialize a SCSI disk for use with the currently opened controller, use the disk initialize command. This command writes data structures to the disk so that the controller can use the disk. Syntax disk initialize [/always{=boolean}] [/unconditional{=boolean}]{scsi_device} Parameters {scsi_device} Specifies the ID for the SCSI disk you want to prepare and initialize for controller use. A SCSI ID consists of a SCSI channel number (for example, 0, 1, 2, 3, etc.
disk Commands /unconditional{=boolean} Specifies whether to initialize the disk even if arrays on the disk have open files. If you specify TRUE for this switch, the command initializes the disk even if the disk has open files. The default is FALSE; that is, the disk initialize command does not initialize a disk that has open files on it. WARNING: Unconditionally deleting an array that is in use can cause a system crash under some circumstances.
disk Commands disk list To display a list of the disks available on the currently opened controller, use the disk list command. Syntax disk list [/all{=boolean}] [/full{=boolean)] [{scsi_device}] Parameters {scsi_device} Specifies the ID for a specific SCSI device for which you want to display information. A SCSI device consists of a SCSI channel number (for example, 0, 1, 2, 3, etc.), SCSI device ID (0 through 15 inclusive), and SCSI device logical unit number (0 through 7 inclusive).
disk Commands Examples The following example shows how to display nondetailed information for all of the SCSI disks on the currently opened controller: AAC0>disk list Executing: disk list C:ID:L Device Type Blocks ------ ---------- --------2:00:0 Disk 8887200 2:01:0 Disk 8887200 2:02:0 Disk 8496960 2:03:0 Disk 8887200 Bytes/Block ----------512 512 512 512 Usage Shared Rate ----------- ------ ---Initialized NO 40 Initialized NO 40 Initialized NO 40 Initialized NO 40 The detailed disk list display contain
disk Commands The Device Type Column The Device Type column displays the SCSI device type. The disk list command can display one of the values listed in Table 5-1. Table 5-1 Device Type Values Value Meaning Disk The device type is a SCSI direct access device. Typically, these are disk drives. This value appears in the example. Sequential The device type is a SCSI sequential access device; typically, tape drives. Printer The device type is a SCSI printer device.
disk Commands The Rev Column The Rev column displays the revision number of the SCSI device. The Block Column The Block column displays the number of blocks available on the SCSI device. The Bytes/Block Column The Bytes/Block column displays the number of bytes for each block on the SCSI device. The Usage Column The Usage column displays the usage of the SCSI device. The disk list command can display one of the values listed in Table 5-2.
disk Commands The Rate Column The Rate column displays the negotiated speed of the SCSI device, in megabytes per second.
disk Commands disk remove dead_partitions To remove all dead partitions from a SCSI disk, use the disk remove dead_partitions command. A dead partition is a partition that is no longer used by any array. Typically, you use this command only under specific circumstances. For example, if you remove a disk from a redundant array and then later add the disk to the controller, the partition on the reinserted disk (which was previously part of the redundant array) is no longer useful.
disk Commands disk set default To set the default SCSI ID for use in subsequent CLI commands, use the disk set default command. This command allows you to set defaults for a specific SCSI device’s SCSI device channel number and SCSI device logical unit number. Then, in subsequent commands, you need only specify the SCSI device ID on the command line. Syntax disk set default {scsi_device} Parameters {scsi_device} Specifies the ID for the SCSI device.
disk Commands Related Commands disk commands: ■ disk list (page 5-5) ■ disk show default (page 5-16) 5-12
disk Commands disk set smart To change a device’s S.M.A.R.T. configuration, use the disk set smart command. The acronym S.M.A.R.T. stands for SelfMonitoring, Analysis and Reporting Technology. This technology is an industry standard for hard drives that monitors a variety of disk parameters, such as the rate of read-write errors. In addition, S.M.A.R.T. can send an alert to system administrators about potential problems caused by disk errors.
disk Commands Specifies whether to enable S.M.A.R.T. configurations (enable exception reporting) for all disks on the system. If you specify TRUE for this switch, the command enables S.M.A.R.T. configurations for all disks on the system. The default is FALSE; the disk set smart command does not enable S.M.A.R.T. configurations for all disks on the system. In this case, you would want to specify a SCSI ID to enable S.M.A.R.T. configurations for a specific disk on the system.
disk Commands /mrie={integer} /perf{=boolean} Specifies whether to report exceptions according to the MRIE mode taking into account performance. If you specify TRUE for this switch, the command performs exception reporting as long as performance is not an issue. If performance is an issue, the command does not report exceptions. If you specify FALSE for this switch, exceptions are reported according to the MRIE mode regardless of performance issues.
disk Commands disk show default To display the current default for the SCSI device ID, use the disk show default command. You previously set this default using the disk set default command.
disk Commands disk show defects To show the number of defects and/or the defect list for a specific SCSI disk drive, use the disk show defects command. Syntax disk show defects [/full{=boolean}]{scsi_device} Parameters {scsi_device} Specifies the ID for the SCSI device for which you want to display defect information. A SCSI device consists of a SCSI channel number (for example, 0, 1, 2, 3, etc.), SCSI device ID (0 through 15 inclusive), and SCSI device logical unit number (0 through 7 inclusive).
disk Commands The items in the display are described as follows: ■ Number of PRIMARY defects on drive: This item shows the details regarding any primary disk defects. In the example, there are two defects. ■ Defect 1 at cylinder 12, head 5, sector 59 This item shows where defect 1 occurred. In the example, the defect occurred on head 5 of cylinder 12 located in sector 59. ■ Defect 2 at cylinder 550, head 1, sector 44 This item shows where defect 2 occurred.
disk Commands disk show partition To display a list of partitions on the disks attached to the currently opened controller, use the disk show partition command. Syntax disk show partition Examples The following example shows a sample output from the disk show partition command: AAC0>disk show partition Executing: disk show partition Scsi Partition Array MultiLevel C:ID:L Offset:Size Num Type Num Type R/W ------ ------------- --- ------ --- ------ --0:02:0 64.0KB:20.
disk Commands The Array Num and Array Type Columns The Array Num column displays the ID of the primary array in the partition. In the example, the array ID is 0. The Array Type column displays the type of array in which the partition resides. Table 5-3 lists the possible values that the command can display in the Type column. Table 5-3 Primary Array Values Value Meaning None This partition is not in an array. Mirror This partition is part of a mirror set.
disk Commands The R/W Column The R/W column displays whether the partition is read-only or read-write. Specifically, the column can display the values listed in Table 5-5. Table 5-5 R/W Array Values Value Meaning RO The partition is read-only. RW The partition is read-write.
disk Commands disk show smart To display S.M.A.R.T. configuration information for one or all disks, use the disk show smart command. The acronym S.M.A.R.T. stands for Self-Monitoring, Analysis and Reporting Technology. This technology is an industry standard for hard drives that monitors a variety of disk parameters, such as the rate of read-write errors. In addition, S.M.A.R.T. can send an alert to system administrators about potential problems caused by disk errors.
disk Commands /full{=boolean} Specifies whether to display detailed S.M.A.R.T. configuration information for one or all SCSI disks. If you specify TRUE, the command displays detailed S.M.A.R.T. configuration information. If you specify FALSE, the command does not display detailed S.M.A.R.T. configuration information. This switch defaults to FALSE. /view_changeable{=boolean} Specifies whether to display the configuration information that can be set on a S.M.A.R.T. disk.
disk Commands The C:ID:L Column The C:ID:L column displays the SCSI channel number, the SCSI device ID, and the SCSI device logical unit number for each disk on the currently opened controller. (The display shows only one disk if you specified a particular disk.) In the example, the command displays the SCSI channel number, the SCSI device ID, and the SCSI device logical unit number for the four disks on the open controller.
disk Commands The Log Errors Column The Log Errors column displays the value Y if you enabled log errors or N if you did not enable log errors. You enable log errors by using the disk set smart command’s /logerr switch. If you specified the /view_changeable switch, the command displays an X in this column for those disks on which you can enable log errors. The Interval Timer (secs.) Column The Interval Timer (secs.) column displays the number of seconds specified for the exception reporting interval.
disk Commands disk show space To display space usage information on a SCSI disk, use the disk show space command. Syntax disk show space [/all{=boolean}] [{scsi_device}] Parameters {scsi_device} Specifies the ID for the SCSI device for which you want to display space usage information. A SCSI ID consists of a SCSI channel number (for example, 0, 1, 2, 3, etc.), a SCSI device ID (0 through 15 inclusive), and a SCSI device logical unit number (0 through 7 inclusive).
disk Commands The following example shows space usage information for SCSI disk device (0,2,0): AAC0>disk show space (0,2,0) Executing: disk show space (ID=2) Scsi C:ID:L Usage Size ----------- --------------------0:02:0 Array 64.0KB: 20.0MB 0:02:0 Free 20.0MB: 29.0MB The following sections provide more information on the columns that the disk show space command displays.
disk Commands The Size Column The Size column displays the offset (in bytes) into the SCSI device and the size of the partition or space (in bytes). In the example, the offset and sizes for the first two disks are as follows: ■ For the 0:02:0 disk The offset is 64.0 KB for the partition and 20.0 MB for the unused space. The size is 20.0 MB for the partition and 29.0 MB for the unused space. ■ For the 0:03:0 disk The offset is 64.0 KB and the size is 49.0 MB for the unused space.
disk Commands disk verify To verify all blocks on a SCSI disk device and, optionally, repair any bad blocks, use the disk verify command. Syntax disk verify [/repair{=boolean}] [/wait{=boolean}] {scsi_device} Parameters {scsi_device} Specifies the ID for the SCSI disk device that you want to verify. A SCSI ID consists of a SCSI channel number (for example, 0, 1, 2, 3, etc.), a SCSI device ID (0 through 15 inclusive), and a SCSI logical unit number (0 through 7 inclusive).
disk Commands Examples The following example synchronously verifies and repairs all blocks on disk (0,2,0): AAC0>disk verify /repair=TRUE /wait=TRUE (0,2,0) Executing: disk verify (CHANNEL=0,ID=2,LUN=0) As the command executes, note the title bar of the DOS window displays the status of the command. For example: Stat:OK!Task:100,Func:SCV,State:RUN 97.2% For further details on status information, see page 1-13.
disk Commands disk zero To clear an entire SCSI disk, use the disk zero command. When you clear a disk, all data is erased and cannot be recovered. Command and Switch Availability This command is supported on Windows. Syntax disk zero [/always{=boolean}] [/wait{=boolean}] {scsi_device} Parameters {scsi_device} Specifies the ID for the SCSI disk you want to clear. A SCSI ID consists of a SCSI channel number (for example, 0, 1, 2, 3, etc.
disk Commands /wait{=boolean} Specifies whether to clear the disk synchronously or asynchronously. If you set this switch to TRUE, the command clears the disk synchronously and the command prompt does not return until the clear disk task completes. The default is FALSE; the command clears the disk asynchronously and the command prompt returns immediately. Examples The following example clears SCSI disk (0,2,0). There is data on the disk.
6 diagnostic Commands In this Chapter diagnostic clear boot_parameters 6-2 diagnostic dump structures 6-3 diagnostic dump text 6-4 diagnostic load_arrays 6-6 diagnostic moderation set count 6-7 diagnostic moderation set timer 6-8 diagnostic moderation show count 6-9 diagnostic moderation show timer 6-10 diagnostic set boot_parameter 6-11 diagnostic show boot_parameter 6-12 diagnostic show history 6-13 The diagnostic commands are used to help fix problems that can occur during controll
diagnostic Commands diagnostic clear boot_parameters To clear all boot-time parameters contained in the currently opened controller’s parameters, use the diagnostic clear boot_parameters command. Under normal conditions, no boottime parameters are set. Caution: Use this command only under the direction of ! technical support.
diagnostic Commands diagnostic dump structures To save internal data structures to a file for use by technical support, use the diagnostic dump structures command. Caution: Use this command only under the direction of ! technical support. Syntax diagnostic dump structures Parameters {string} Specifies the name of the file to contain the internal data structures. Use the filename conventions that apply to your operating system.
diagnostic Commands diagnostic dump text To display diagnostic information on the console display for use by technical support during bug reporting, use the diagnostic dump text command. ! Caution: Use this command only under the direction of technical support. Notes Before using this command in DOS, verify that the window is set to scroll data. For details, refer to your DOS documentation.
diagnostic Commands Related Commands diagnostic commands: ■ diagnostic dump structures (page 6-3) 6-5
diagnostic Commands diagnostic load_arrays To load arrays when the system is in maintenance mode, use the diagnostic load_arrays command. This command differs from controller rescan in that it does not rescan the SCSI channel. Caution: Use this command only under the direction of ! technical support. Syntax diagnostic load_arrays Examples The following example allows arrays to be loaded: AAC0>diagnostic load_arrays Executing: diagnostic load_arrays All boot time parameters cleared to default values.
diagnostic Commands diagnostic moderation set count To set the default interrupt count on the controller, use the diagnostic moderation set count command. Caution: Use this command only under the direction of ! technical support. Syntax diagnostic moderation set count {integer} Parameters {integer} Specifies the value (for example, 700) you want to set as the default interrupt count on the controller.
diagnostic Commands diagnostic moderation set timer To set the default interrupt timer on the controller, use the diagnostic moderation set timer command. Caution: Use this command only under the direction of ! technical support. Syntax diagnostic moderation set timer {integer} Parameters {integer} Specifies the value (for example, 10) you want to set as the default interrupt timer on the controller.
diagnostic Commands diagnostic moderation show count To display the number of outstanding I/Os necessary to allow the delay of I/O request responses to the host computer, use the diagnostic moderation show count command. You may have previously specified the default interrupt count (the number of outstanding I/Os) with the diagnostic moderation set count command. Caution: Use this command only under the direction of ! technical support.
diagnostic Commands diagnostic moderation show timer To display the time in 100 microsecond units that the controller batches I/O request responses before issuing an interrupt to the host computer, use the diagnostic moderation show timer command. You may have previously specified the default interrupt timer (the time in 100 microsecond units) with the diagnostic moderation set timer command. Caution: Use this command only under the direction of ! technical support.
diagnostic Commands diagnostic set boot_parameter To set boot-time parameters that a technical support representative might need, use the diagnostic set boot_parameter command. Caution: Use this command only under the direction of ! technical support. Syntax diagnostic set boot_parameter Parameters {string} Specifies the name of the boot-time parameter to be set. If you need to use this command, a technical support representative will tell you the name of the boot-time parameter to use.
diagnostic Commands diagnostic show boot_parameter To display a specific boot-time parameter (if one exists) that a technical support representative might need, use the diagnostic show boot_paramter command. Caution: Use this command only under the direction of ! technical support. Syntax diagnostic show boot_parameter Parameters {string} Specifies the boot-time parameter character string whose associated value you want to display.
diagnostic Commands diagnostic show history To display an internal history log of operations kept in the currently opened controller that a technical support representative might need, use the diagnostic show history command. Syntax diagnostic show history [/old{=boolean}] [/current{=boolean}] Switches /old{=boolean} Specifies whether to display the controller’s operations history log from the previous boot of the operating system.
7 logfile Commands In this Chapter logfile end 7-2 logfile start 7-3 Use the following syntax for logfile commands: logfile command [/switch{=value}] [parameter] 7-1
logfile Commands logfile end To end the logging of all output, use the logfile end command. Syntax logfile end Examples The following example stops logging information to the file aac0log17Nov01.txt (which was previously started with the logfile start command): AAC0> logfile end Executing: logfile end Log file closed.
logfile Commands logfile start To begin the logging of all CLI command line activity to a specified file, use the logfile start command. CLI command line activity includes the associated output the CLI command displays. The CLI continues to log command output until you close the CLI or you explicitly end the logfile with the logfile end command. Syntax logfile start [/append{=boolean}] {string} Parameter {string} Specifies the name of the file to contain CLI command line activity.
logfile Commands Related Commands logfile commands: ■ logfile end (page 7-2) 7-4
8 task Commands In this Chapter task list 8-2 task resume 8-8 task stop 8-10 task suspend 8-12 Use the following syntax for task commands: task command [/switch{=value}] [parameter] 8-1
task Commands task list To display a list of one or all tasks running on the currently opened controller, use the task list command. A task is an operation that occurs only on the controller, asynchronous to all other operations. Clearing a disk, creating a file system, and creating a mirror set are examples of tasks done on the controller. The command displays an appropriate message if there are no tasks running on the controller.
task Commands As the example shows, the typical display shows the following columns of information: ■ TaskId ■ Function ■ Done% ■ Array ■ State ■ Specific1 ■ Specific2 The following sections describe each column that the task list command displays. The Task ID Column The Task ID column displays the ID number associated with a specific task. The controller assigns each task a unique ID number. The Function Column The Function column displays the type of task running on the controller.
task Commands Table 8-1 Task Types (Continued) Task Type Meaning NTFSfmt An array format NTFS file system task is running on the specified array. The format NTFS file system task runs as a result of using the array format command with the / file_system switch set to NTFS. Rebuild A rebuild task is running on the specified array. Typically, the rebuild task runs when the controller is in a rebuild of a redundant array (RAID 5 array, mirror set, or multilevel array of mirror sets).
task Commands Table 8-1 Task Types (Continued) Task Type Meaning Verify A verify with no repair of bad blocks task is running on the specified SCSI disk. When the verify with no repair of bad blocks task completes, the specified SCSI disk’s blocks were verified without repairing any detected defects. The verify with no repair of bad blocks task runs as a result of using the disk verify command without specifying the /repair switch.
task Commands The State Column The State Column displays the state of the task. Table 8-2 describes the state values that the task list command can display. Table 8-2 State Values State Meaning BAD The task failed and is no longer running. DNE The task successfully completed or the task is no longer running (that is, the task is done). RUN The task is running. SUS The task was suspended. Typically, you suspend a task with the task suspend command.
task Commands The Specific2 Column The Specific2 column displays additional information for certain tasks that appear in the Task Id column. Table 8-4 lists the tasks for which the task list command can display additional information. Table 8-4 also describes the additional information that task list can display. Table 8-4 Additional Specific2 Information Task Additional Information Verify. Refers to the verify with Displays the number of bad blocks found that were replaced.
task Commands task resume To resume one or all tasks previously suspended on the currently opened controller, use the task resume command. You suspend tasks with the task suspend command. Syntax task resume [/all{=boolean}] [{integer}] Parameters {integer} Specifies the task ID for the task to resume. Perform a task list /all to display the task IDs for all tasks currently suspended on the open controller before resuming a specific task or all tasks.
task Commands Use the task list command after using the task resume command to display information about the task, as in the following example: AAC0>task list Executing: task list TaskId Function Done% Array ------ -------- ----- --------101 Scrub 24.6% 0 State ----RUN Specific1 --------00000000 Specific2 --------00000000 As a result of using the task resume command, the State column now displays RUN (running on the controller) instead of SUS (suspended on the controller).
task Commands task stop To stop one or all tasks running on the currently opened controller, use the task stop command. Syntax task stop [/all{=boolean}] Parameters {integer} Specifies the task ID for the task to stop. Perform a task list /all to display the task IDs for all tasks currently running on the open controller before stopping a specific task or all tasks. Switches /all{=boolean} Specifies whether to stop all running tasks.
task Commands Use the task list command after using the task stop command to display information about the task, as in the following example: AAC0>task list Executing: task list No tasks currently running on controller.
task Commands task suspend To suspend one or all tasks running on the currently opened controller, use the task suspend command. Syntax task suspend [/all{=boolean}] Parameters {integer} Specifies the task ID for the task to suspend. Perform a task list /all to display the task IDs for all tasks currently running on the open controller before suspending a specific task or all tasks. Switches /all{=boolean} Specifies whether to suspend all running tasks.
task Commands Use the task list command after using the task suspend command to display information about the task, as in the following example: AAC0>task list Executing: task list TaskId Function Done% Array ------ -------- ------ --------101 Scrub 24.6% 0 State Specific1 Specific2 ---- --------- --------SUS 00000000 00000000 As a result of using the task suspend command, the State column now displays SUS (suspended on the controller) instead of RUN (running on the controller).
9 enclosure Commands In this Chapter enclosure activate slot 9-2 enclosure identify slot 9-4 enclosure list 9-6 enclosure prepare slot 9-11 enclosure set alarm 9-13 enclosure set door 9-14 enclosure set fan 9-15 enclosure set interval 9-17 enclosure set power 9-19 enclosure set scsiid 9-21 enclosure set temperature 9-24 enclosure show fan 9-26 enclosure show power 9-29 enclosure show slot 9-32 enclosure show status 9-36 enclosure show temperature 9-41 These enclosure command
enclosure Commands enclosure activate slot To activate a device in a specified slot of the specified SAF-TE enclosure management device, use the enclosure activate slot command. Specifically, this command makes the device that resides in the slot available on the SCSI channel. Syntax enclosure activate slot {enclosure} {slot} Parameters {enclosure} Specifies the ID associated with the enclosure management device on which you want to activate a device.
enclosure Commands The following example shows how to activate a device in slot 0 of enclosure management device 0 using the enclosure activate slot command: AAC0>enclosure activate slot 0 0 Executing: enclosure activate slot 0 0 You may want to use the enclosure show slot command again to see the change in the device slot’s status, as in the following example. Note that the OK ACTIVATE in the status column indicates that the device is activated and working properly.
enclosure Commands enclosure identify slot To identify a slot on a specified SAF-TE enclosure management device, use the enclosure identify slot command. Typically, an enclosure management device indicates to the operator which slot is currently being identified by flashing an adjacent light. Syntax enclosure identify slot {enclosure} {slot} Parameters {enclosure} Specifies the ID associated with the enclosure management device on which you want to identify a slot.
enclosure Commands Related Commands enclosure commands: ■ enclosure activate slot (page 9-2) ■ enclosure list (page 9-6) ■ enclosure prepare slot (page 9-11) ■ enclosure show slot (page 9-32) 9-5
enclosure Commands enclosure list To display the list of components associated with one or all SAF-TE enclosure management devices connected to the controller, use the enclosure list command. Syntax enclosure list [/all{=boolean}] [/full{=boolean}] [{enclosure}] Parameters {enclosure} Specifies the ID associated with the enclosure management device whose associated components you want to display. For this version, the controller supports a maximum of eight enclosure management devices on each bus.
enclosure Commands Examples The following example shows a non-detailed list of components for enclosure management devices 0 and 1: AAC0>enclosure list /all=TRUE Executing: enclosure list /all=TRUE Enclosure Fan Power Slot Sensor Door ScsiId Speaker Standard Diagnostic --------- --- ----- ---- ------ ---- ------ -------- -------- --------0 1 1 5 1 5 0:06:0 No SAF-TE PASSED 1 1 1 5 1 5 1:06:0 No SAF-TE PASSED The non-detailed enclosure list display contains the following columns of information: ■ Enclosur
enclosure Commands The Enclosure Column The Enclosure column displays the ID of a specific enclosure management device. This is the ID that you specify for the enclosure parameter on the command line. In the example, the enclosure list command displays enclosure management device IDs 0 and 1 (because the /all switch was specified). The Fan and Power Columns The Fan column displays the number of fans on the enclosure management device.
enclosure Commands The Door Column The Door column displays the number of doors on the enclosure management device. Typically, enclosure management devices support a maximum of sixteen doors. In the example, enclosure management devices 0 and 1 each have five doors. The ScsiId Column The ScsiId column displays the SCSI channel number (in the example, 0 and 1), the SCSI ID (in the example, 06), and the SCSI logical unit number (in the example, 0) for the enclosure management device.
enclosure Commands Specifically, the column can display the items listed in Table 9-2. Table 9-2 Diagnostic Status Status Meaning PASSED No errors were detected and the diagnostic self-tests were successful. This is the value displayed in the example for both enclosure management devices. FAILED Errors were detected and the diagnostic self-tests were not successful. UNKNOWN The status of the diagnostic self-tests is unknown.
enclosure Commands enclosure prepare slot To indicate to the SAF-TE enclosure management device that it should take the appropriate action to prepare the device in a specific slot for removal or insertion, use the enclosure prepare slot command. This command may perform such operations as shutting off power to the device slot. This allows users to safely remove a disk device from or insert a disk device into the device slot.
enclosure Commands The following example prepares the device in slot 0 on enclosure management device 0 for insertion or removal as a result of using the enclosure prepare slot command: AAC0>enclosure prepare slot 0 0 Executing: enclosure prepare slot 0 0 You may want to use the enclosure show slot command again to see the change in the device slot’s status, as in the following example: AAC0>enclosure show slot Executing: enclosure show slot Enclosure Slot scsiId Insert Status --------- ---- ------ ------
enclosure Commands enclosure set alarm To turn the audible alarm on a specific SAF-TE enclosure management device on or off, use the enclosure set alarm command. Syntax enclosure set alarm [/on{=boolean}] {enclosure} Parameters {enclosure} Specifies the ID associated with the enclosure management device whose audible alarm you want to set. For this version, the controller supports a maximum of eight enclosure management devices on each bus.
enclosure Commands enclosure set door To lock or unlock a specific door on a specific SAF-TE enclosure management device, use the enclosure set door command. Syntax enclosure set door [/lock{=boolean}] {enclosure} {door} Parameters {enclosure} Specifies the ID associated with the enclosure management device on which you want to lock the door. For this version, the controller supports a maximum of eight enclosure management devices on each bus.
enclosure Commands enclosure set fan To set the speed of a specific fan on a specific SAF-TE enclosure management device, use the enclosure set fan command. Syntax enclosure set fan [/off{=boolean}] {enclosure} {fan} [{speed}] Parameters {enclosure} Specifies the ID associated with the enclosure management device on which you want to set the speed of a specific fan. For this version, the controller supports a maximum of eight enclosure management devices on each bus.
enclosure Commands Switches /off{=boolean} Specifies whether to turn off the fan associated with the specified unit number. If you set this switch to TRUE, the command turns off the fan associated with the specified unit number. You must turn on the fan if you want to set its speed. This switch defaults to FALSE, which means the fan remains on and you can set its speed.
enclosure Commands enclosure set interval To set the monitor reporting interval for a specific SAF-TE enclosure management device, use the enclosure set interval command. The monitor reporting interval indicates how often the controller checks the status of the enclosure management device and its associated components. In setting this value, consider the needs of your computing environment. Setting the monitor reporting level to less than ten seconds could cause slower system performance.
enclosure Commands The following example sets the monitor reporting interval for enclosure management devices 0 and 1 to 20 seconds: AAC0>enclosure set interval 20 Executing: enclosure set interval 20 You may want to use the enclosure show status command again to see the change in the power supply’s status, as in the following example: Enclosure --------0 . . .
enclosure Commands enclosure set power To turn the power of a specific power supply on a specific SAF-TE enclosure management device on or off, use the enclosure set power command. Typically, most enclosure management devices turn on their associated power supplies by default after power up.
enclosure Commands Examples Before turning a power supply on or off, you might want to use the enclosure show power command to determine the current setting for the power supply or supplies.
enclosure Commands enclosure set scsiid To set the SCSI device ID for a specific device slot on a specific SAFTE enclosure management device, use the enclosure set scsiid command. As discussed in other chapters, a SCSI ID consists of a SCSI channel number (for example, 0, 1, 2, 3, and so on), SCSI device ID (0 through 15 inclusive), and SCSI device logical unit number (0 through 7 inclusive).
enclosure Commands Examples Before setting a device slot to a specific SCSI ID, you might want to use the enclosure show slot command to determine the current SCSI ID setting for the device slots, as in the following example: AAC0>enclosure show slot Executing: enclosure show slot Enclosure Slot scsiId Insert Status --------- ---- ------ ------- ----------------------------------------0 0 0:00:0 4 OK NOTACTIVATE 0 1 0:01:0 0 OK UNCONFIG ACTIVATE 0 2 0:10:0 0 OK UNCONFIG ACTIVATE 0 3 0:03:0 0 OK UNCONFIG AC
enclosure Commands Related Commands controller commands: ■ controller pause_io (page 4-12) enclosure commands: ■ enclosure list (page 9-6) ■ enclosure show slot (page 9-32) 9-23
enclosure Commands enclosure set temperature To set the temperature threshold on a specific SAF-TE enclosure management device, use the enclosure set temperature command. Typically, an enclosure management device contains individual temperature sensors. With this command, you can set a temperature threshold so that the enclosure management device alerts you if one or more of the temperature sensors exceeds the threshold.
enclosure Commands You may want to use the enclosure show temperature command again to see the change in threshold temperature, as in the following example: AAC0>enclosure show temperature 0 Executing: enclosure show temperature 0 Enclosure Sensor Temperature Threshold Status --------- ------ ----------- --------- -------0 0 70 F 100 NORMAL The Threshold column now displays 100 degrees.
enclosure Commands enclosure show fan To display the status of a specific fan on a specific SAF-TE enclosure management device, use the enclosure show fan command. You can also use this command to display the status of all fans on the enclosure management device or devices. Syntax enclosure show fan [{enclosure}] [{fan}] Parameters {enclosure} Specifies the ID associated with the enclosure management device for which you want to display fan status information.
enclosure Commands As the example shows, the fan status display contains the following columns: ■ Enclosure ■ Fan ■ Status The following sections describe the information that the enclosure show fan command can display in these columns. The Enclosure and Fan Columns The Enclosure column displays the ID associated with the enclosure management device that you specified on the command line.
enclosure Commands Related Commands enclosure commands: ■ enclosure list (page 9-6) ■ enclosure set fan (page 9-15) ■ enclosure show status (page 9-36) 9-28
enclosure Commands enclosure show power To display the status of a specific power supply on a specific SAFTE enclosure management device, use the enclosure show power command. You can also use this command to display the status of all power supplies on the enclosure management device or devices. Syntax enclosure show power [{enclosure}] [{powersupply}] Parameters {enclosure} Specifies the ID associated with the enclosure management device for which you want to display power supply status information.
enclosure Commands As the example shows, the power supply status display contains the following columns: ■ Enclosure ■ Power ■ State ■ Status The following sections describe the information that the enclosure show power command can display in these columns. The Enclosure and Power Columns The Enclosure column displays the ID associated with the enclosure management device that you specified on the command line.
enclosure Commands Table 9-5 State and Status Columns Status State Meaning ON BAD The power supply is on and not working properly. OFF BAD The power supply is off and not working properly. INSTALLED UNKNOWN The power supply is installed and its status is not reportable or unknown. NOT INSTALLED Not Applicable The power supply is not installed. UNKNOWN UNKNOWN The state and status of the power supply is not reportable or unknown.
enclosure Commands enclosure show slot To display the status of a specific device slot on a specific SAF-TE enclosure management device, use the enclosure show slot command. You can also use this command to display the status of all device slots on the enclosure management device or devices. Syntax enclosure show slot [{enclosure}] [{slot}] Parameters {enclosure} Specifies the ID associated with the enclosure management device for which you want to display device slot status information.
enclosure Commands Examples The following example displays the status of all device slots on enclosure management devices 0 and 1: AAC0>enclosure show slot Executing: enclosure show slot Enclosure Slot scsiId Insert Status --------- ---- ------ ------- ----------------------------------0 0 0:00:0 4 OK 0 1 0:01:0 0 UNCONFIG 0 2 0:10:0 0 UNCONFIG 0 3 0:03:0 0 UNCONFIG 0 4 0:04:0 0 UNCONFIG 1 0 1:00:0 0 UNCONFIG 1 1 1:01:0 0 UNCONFIG 1 2 1:10:0 0 UNCONFIG 1 3 1:03:0 0 UNCONFIG 1 4 1:04:0 0 UNCONFIG As the ex
enclosure Commands The scsiId Column The scsiId column displays the SCSI ID associated with the device slot. A SCSI ID consists of a SCSI channel number (for example, 0, 1, 2, 3, etc.), SCSI device ID (0 through 15 inclusive), and SCSI device logical unit number (0 through 7 inclusive). In the example, the enclosure show slot command displays the SCSI IDs for device slots 0 through 4.
enclosure Commands Table 9-6 Status Column Status Meaning UNCONFIG The device that resides in this slot is not currently configured as a member of a device array or as a hot spare. HOTFAILOVER The device that resides in this slot is configured as a hot spare. FAILOVERSTOP The device that resides in this slot was in a rebuild operation, but the rebuild operation terminated abnormally or unsuccessfully. EMPTY No physical device resides in this slot.
enclosure Commands enclosure show status To display the general status of a specific SAF-TE enclosure management device, use the enclosure show status command. You can also use this command to display the general status of all enclosure management devices connected to the controller.
enclosure Commands Examples The following example displays status information for enclosure management devices 0 and 1: AAC0>enclosure show status Executing: enclosure show status Enclosure UpTime D:H:M PowerCycle Interval Door Alarm --------- -------------- ---------- -------- -------- ------0 0:04:25 2 20 UNLOCKED OFF Enclosure Fan Status --------- --- ------------0 0 OK Enclosure Power State Status --------- ----- ------------ ------0 0 UNKNOWN UNKNOWN Enclosure Slot scsiId Insert --------- ---- ------
enclosure Commands The general status of an enclosure management device is encapsulated in the following columns: ■ Enclosure ■ UpTime D:H:M ■ PowerCycle ■ Interval ■ Door ■ Alarm The following sections describe the information that the enclosure show status command can display in these columns. For information about the status displays for fans, power supplies, device slots, and temperature sensors see the Related Commands section.
enclosure Commands The Interval Column The Interval column displays the monitor interval. You can set the monitor interval with the enclosure set interval command. In the example, the monitor interval reporting level for both enclosure management devices is 20 seconds. The Door and Alarm Columns The Door column displays the status of the door lock. The enclosure show status command can display the door lock status values listed in Table 9-7.
enclosure Commands ■ enclosure show power (page 9-29) ■ enclosure show slot (page 9-32) ■ enclosure show temperature (page 9-41) 9-40
enclosure Commands enclosure show temperature To display the temperature status of a specific temperature sensor on a specific SAF-TE enclosure management device, use the enclosure show temperature command. You can also use this command to display the temperature status of all temperature sensors on the enclosure management device or devices.
enclosure Commands As the example shows, the temperature sensor status display contains the following columns: ■ Enclosure ■ Sensor ■ Temperature ■ Threshold ■ Status The following sections describe the information that the enclosure show temperature command can display in these columns. The Enclosure Column The Enclosure column displays the ID associated with the enclosure management device that you specified on the command line.
enclosure Commands The Threshold Column The Threshold column displays the temperature at which an alarm will be sounded if the temperature goes above the threshold. In the example, the temperature threshold is 120 degrees Fahrenheit. You can change the temperature threshold by using the enclosure set temperature command. The Status Column The Status column displays the status of the temperature displayed in the Temperature column.
A Automated Scripts This appendix describes how to write DOS batch files and CLI command scripts to perform the controller details task. You can use the CLI commands alone in CLI command scripts or in combination with DOS commands in DOS batch files. Also, you can invoke CLI command scripts in a DOS batch file. You should already understand how to write DOS batch files and be familiar with Windows-related backup commands.
R Adaptec, Inc. 691 South Milpitas Boulevard Milpitas, CA 95035 USA ©2000 – 2004 Adaptec, Inc. All rights reserved. Adaptec and the Adaptec logo are trademarks of Adaptec, Inc. which may be registered in some jurisdictions. Part Number: 513852-06, Ver.
