Adaptec AAR-21610SA Reference Manual

Adaptec AAR-21610SA Reference Manual

Command line interface
Hide thumbs Also See for AAR-21610SA:
Table of Contents

Advertisement

Command Line Interface

Reference Guide
R

Advertisement

Table of Contents
loading

Summary of Contents for Adaptec AAR-21610SA

  • Page 1: Command Line Interface

    Command Line Interface Reference Guide...
  • Page 2 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.
  • Page 3: Table Of Contents

    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...
  • Page 4 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 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...
  • Page 5 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 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...
  • Page 6 disk show space 5-26 disk verify 5-29 disk zero 5-31 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...
  • Page 7 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 Automated Scripts Creating an Automated Script A-1...
  • Page 8: Introduction

    Command Syntax Parameter and Switch Value Types Status Information 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.
  • Page 9: Accessing The Cli

    1 Click the Start button and move the mouse cursor to Programs. Click on Programs. 2 Move the mouse cursor to SMBE. The Adaptec program group will display. 3 Move the mouse cursor to the CLI icon. Click on CLI.
  • Page 10: Accessing Cli In Netware

    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.
  • Page 11: Conventions

    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.
  • Page 12: Command Syntax

    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...
  • Page 13: Action

    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.
  • Page 14: Parameter

    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}...].
  • Page 15: Integer

    integer An integer is a positive or negative number that has a value between –2 and (2 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.
  • Page 16: String

    Table 1-2 lists examples of valid integers and their corresponding values: Table 1-2 Integers and Values (in Decimal) Integer (5+3*24) (5+(3*24)) 0x123 (12+52h+1010z) 100M 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;...
  • Page 17: Scsi_Device

    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.
  • Page 18: Free_Space

    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).
  • Page 19: Container

    Table 1-6 lists valid free_space specifiers. Table 1-6 Freespace Specifiers SCSI Channel Number, SCSI Device ID, SCSI Device LUN; Freespace Specifier Use n Amount of Freespace SCSI Device: Channel 1, Device ID 2, LUNdefault; ((1,2),1G) use 1 GB of freespace SCSI Device: Channel default, Device ID 5, LUN default;...
  • Page 20: Status Information

    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.
  • Page 21: The Ctr And State Items

    Table 1-7 Function Values (Continued) Value Meaning Merge a broken mirror task. The array merge command causes the MMR value to display. array scrub task. The array scrub command causes the MSC value to display. 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.
  • Page 22 Table 1-8 describes the state values that the State item can display. State Table 1-8 State Values Meaning The task failed and is no longer running. The task successfully completed or the task is no longer running (that is, the task is done). The task is running.
  • Page 23: General Control Commands

    General Control Commands In this Chapter close exit help, ? history_size open reset_window toggle_more The CLI general control commands are discussed in alphabetical order and use the following syntax: command [subcommand] [/switch{=value}] [parameter]...
  • Page 24 General Control Commands close To close the currently opened controller when all access is completed, use the close command. Syntax close...
  • Page 25 General Control Commands exit To close the currently opened controller and exit the CLI, use the exit command. Syntax exit...
  • Page 26 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.
  • Page 27 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...
  • Page 28: Open

    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.
  • Page 29 /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.
  • Page 30: Reset_Window

    General Control Commands reset_window To reset the window, use the reset_window command. Command Availability This command is supported only on UNIX. Syntax reset_window...
  • Page 31: Toggle_More

    General Control Commands toggle_more To turn on or off the <Press any key to continue> functionality, use the toggle_more command. After you type toggle_more on the NetWare console, the command displays an appropriate message indicating whether the <Press any key to continue> functionality is on or off. Command Availability This command is supported only on NetWare.
  • Page 32: Container Commands

    container Commands In this Chapter container add_level container create mirror container create mmirror container create mstripe container create mvolume container create raid5 container create stripe container create volume container delete container extend file_system container extend mvolume container extend volume container list container lock container move container promote...
  • Page 33 container remove drive_letter container remove failover container remove file_system container remove global_failover container restore RAID5 container scrub container set cache container set failover container set global_failover container set io_delay container set label container show cache container show failover container split container unlock container unmirror The array commands are discussed in alphabetical order and use...
  • Page 34: Container Add_Level

    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.
  • Page 35 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 Total Dr Label Type Size -- ----- ------ ------ --- ------ ------- ------ ------------- Volume 45MB Stripe 45MB The following list describes the change to the display as a result of...
  • Page 36: Container Create Mirror

    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...
  • Page 37 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.
  • Page 38 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 Total Dr Label Type Size -- ----- ------ ------ --- ------ ------- ------ ------------- Mirror 10MB The following list describes the changes to the display as a result of using the container create mirror command:...
  • Page 39: Container Create Mmirror

    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.
  • Page 40 {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).
  • Page 41 Examples Before creating a multilevel array of mirror sets, use the container list command to obtain information about any existing arrays. As the following example shows, array 0 is a volume set that consists of two underlying volume sets created with the container promote command: AAC0>container list Executing: container list...
  • Page 42 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.
  • Page 43: Container Create Mstripe

    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. You can create the following types of multilevel stripe set: Stripe set of mirror sets Stripe set of volume sets Stripe set of stripe sets...
  • Page 44 {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 parameter and separated by blank spaces.
  • Page 45 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...
  • Page 46 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).
  • Page 47 Related Commands container commands: container create mirror container list container set label (page 3-5) (page 3-50) (page 3-101) container Commands 3-16...
  • Page 48: Container Create Mvolume

    container create mvolume To create a multilevel volume set, use the container create mvolume command. You can create the following types of multilevel volume sets: Volume set of stripe sets Volume set of mirror sets Volume set of RAID 5 arrays Volume set of volume sets Notes When creating a multilevel array of volume sets on a NetWare...
  • Page 49 {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.
  • Page 50 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 Total Dr Label Type Size -- ----- ------ ------ --- ------ ------- ------ ------------- Volume 60.0MB...
  • Page 51 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.
  • Page 52: Container Create Raid5

    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...
  • Page 53 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.
  • Page 54 /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.
  • Page 55 /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.
  • Page 56 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 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.
  • Page 57 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.
  • Page 58: Container Create Stripe

    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.
  • Page 59 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.
  • Page 60 /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.
  • Page 61 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 Total Dr Label Type Size -- ----- ------ ------ --- ------ ------- ------ ------------- Stripe 45.0MB The following list describes the items in the display that contain information as the result of creating a array with the container...
  • Page 62 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. Related Commands container commands: container create mstripe container create mvolume container list container set cache...
  • Page 63: Container Create Volume

    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.
  • Page 64 {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).
  • Page 65 /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.
  • Page 66 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 Total Dr Label Type Size -- ----- ------ ------ --- ------ ------- ------ ------------- Volume 15.0MB The following list describes the columns that contain information as the result of creating a volume set with the container create...
  • Page 67 container list container promote container set cache container set label disk commands: disk show space (page 3-50) (page 3-63) (page 3-91) (page 3-101) (page 5-26) container Commands 3-36...
  • Page 68: Container Delete

    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.
  • Page 69 /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).
  • Page 70 Related Commands container commands: container create mirror container create mmirror container create mstripe container create mvolume container create raid5 container create stripe container create volume container list (page 3-5) (page 3-8) (page 3-12) (page 3-17) (page 3-21) (page 3-27) (page 3-32) (page 3-50)
  • Page 71: Container Extend File_System

    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).
  • Page 72 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. Before extending a file system, use the container list command to obtain information about any existing arrays: AAC0>container list...
  • Page 73 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.
  • Page 74: Container Extend Mvolume

    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.
  • Page 75 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).
  • Page 76 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.
  • Page 77 Related Commands container commands: container add_level container create mvolume container create volume container extend file_system container list disk commands: disk remove dead_partitions (page 3-3) (page 3-17) (page 3-32) (page (page 3-50) (page container Commands 3-40) 5-10) 3-46...
  • Page 78: Container Extend Volume

    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.
  • Page 79 Before extending the volume set, you might want to use the command to display space usage information on the show space 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...
  • Page 80 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 “!”...
  • Page 81: Container List

    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 array- related commands.
  • Page 82 Examples The following example shows how to list nondetailed information about all arrays on the system: AAC0>container list Executing: container list Total Dr Label Type Size -- ----- ------ ------ --- ------ ------- ------ ------------- Volume 15.0MB Stripe 45.0MB The detailed container list display contains the previous columns of information plus the following columns: State Task...
  • Page 83 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. You can assign labels with the following commands: container create mstripe container create mvolume container create raid5 container create stripe...
  • Page 84: Related 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 create- related commands. The Stripe Size Column This column displays the stripe size for the array.
  • Page 85 The Scsi :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.
  • Page 86 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.
  • Page 87 Table 3-4 Task Types (Continued) Task Meaning A rebuild task is running on the specified array. Typically, the Rebuild 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).
  • Page 88 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.
  • Page 89 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.
  • Page 90: Container Lock

    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.
  • Page 91 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 Total Dr Label Type Size -- ----- ------ ------ --- ------ ------- -------- F: 0...
  • Page 92: Container Move

    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.
  • Page 93 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 Total Dr Label Type Size -- ----- ------ ------ --- ------ ------- ------ ------------- F: 0...
  • Page 94: Container Promote

    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.
  • Page 95 As the following example shows, there is an array 0 (a stripe set) on this controller: AAC0>container list Executing: container list Total Dr Label Type Size -- ----- ------ ------ --- ------ ------- ------ ------------- Stripe 45.0MB The following example promotes array 0 to a multilevel array: AAC0>container promote 0 Executing: container promote 0 Use the container list command after using the container...
  • Page 96 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.
  • Page 97: Container Readonly

    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.
  • Page 98 Use the container list command (with the /full switch) after using the container readonly information about the array you just made read-only, as in the following example: AAC0>container list /full Executing: container list /full=TRUE Total Dr Label Type Size -- ----- ------ ------ --- ------ ------- -------- F: 0 Volume 10.0MB Note that the example eliminates some items in the container...
  • Page 99: Container Readwrite

    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...
  • Page 100 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.
  • Page 101: Container Reconfigure

    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.
  • Page 102 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.
  • Page 103 {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).
  • Page 104 /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...
  • Page 105 /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.
  • Page 106 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 Total Dr Label Type Size...
  • Page 107 container extend file_system container list (page (page 3-50) container Commands 3-40) 3-76...
  • Page 108: Container Release_Cache

    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.
  • Page 109: Container Remove Drive_Letter

    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.
  • Page 110 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.
  • Page 111: Container Remove Failover

    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.
  • Page 112 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 --------- ----------------------------------...
  • Page 113: Container Remove File_System

    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.
  • Page 114 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...
  • Page 115: Container Remove Global_Failover

    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.
  • Page 116 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 --------- ----------------------------------...
  • Page 117: Container Restore Raid5

    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.
  • Page 118 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 Total Dr Label Type Size -- ----- ------ ------ --- ------ ------- ------ ------------- RAID-5 30.0MB Note that in this case the command successfully restored the RAID 5 array as indicated by the replacement of the exclamation point (“!”) with a colon (“:”).
  • Page 119: Container Scrub

    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.
  • Page 120 /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.
  • Page 121 Related Commands container commands: container create mirror container create mmirror container create raid5 container list page 3-5) (page 3-8) (page 3-21) (page 3-50) container Commands 3-90...
  • Page 122: Container Set Cache

    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.
  • Page 123 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.
  • Page 124 Table 3-5 summarizes the values for the /write_cache_enable and /unprotected switches: Table 3-5 Switch Values and Results /write_cache_enable /unprotected Switch Setting Switch Setting FALSE FALSE FALSE TRUE TRUE FALSE TRUE TRUE Examples Before setting cache parameters for a specific array, use the container list command to obtain information about any existing arrays.
  • Page 125 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...
  • Page 126: Container Set Failover

    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.
  • Page 127 As the following example shows, there is an array 0 (a mirror set) on this controller: AAC0>container list Executing: container list Total Dr Label Type Size -- ----- ------ ------ --- ------ ------- ------ ------------- D: 0 Mirror 10.0MB The following example assigns two SCSI failover disks to array 0. If you assign only one SCSI disk as a failover device, ensure that there is sufficient freespace.
  • Page 128: Container Set Global_Failover

    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.
  • Page 129 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.
  • Page 130: Container Set Io_Delay

    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...
  • Page 131 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. Otherwise, you cannot change the I/O delay: container create mirror /io_delay=20 0 (0,2,0) Executing container create mirror /io_delay=20 0 (CHANNEL=0,ID=2,LUN=0) The following example shows how to change the I/O delay to 40 milliseconds on the currently running create mirror task:...
  • Page 132: Container Set Label

    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. The following commands have a assign a label to the array when you create it: container create mstripe (a multilevel stripe set) container create mvolume (a multilevel volume set) container create raid5 (a RAID 5 array)
  • Page 133 Examples Before assigning a label to a specific 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 with no label assigned to it (as evidenced by no label in the Num Label column): AAC0>container list Executing: container list...
  • Page 134: Container Show Cache

    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}...
  • Page 135 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.
  • Page 136 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 Active, not protected Active, not protected,...
  • Page 137 Table 3-7 Values for Write Cache Status (Continued) Value Active, not protected, battery reconditioning Active, protected Inactive, battery low Inactive, battery not present Inactive, battery reconditioning Meaning The status of the write cache for this array is as follows: Active – The write cache can accept write oper- ations from the array.
  • Page 138 Table 3-7 Values for Write Cache Status (Continued) Value Inactive, cache disabled Inactive, write not supported Related Commands container commands: container list container set cache container show cache Meaning The status of the write cache for this array is as follows: Inactive –...
  • Page 139: Container Show Failover

    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 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.
  • Page 140: Container Split

    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.
  • Page 141 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. As the following example shows, there is one existing array (array 0, a mirror set) on this controller at the time the mirror set is split: AAC0>container list Executing: container list...
  • Page 142 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 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.
  • Page 143: Container Unlock

    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}...
  • Page 144 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 Total Dr Label Type Size -- ----- ------ ------ --- ------ ------- -------- F: 0 Volume 10.0MB Note that the example eliminates some items in the container...
  • Page 145: Container Unmirror

    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.
  • Page 146 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.
  • Page 147 controller Commands In this Chapter controller details controller firmware compare controller firmware save controller firmware update controller list controller pause_io controller rescan controller reset_scsi_channel controller resume_io controller set automatic_failover controller set array_verify controller show automatic_failover controller show channels controller show array_verify 4-10 4-12 4-14...
  • Page 148: Controller Details

    Executing: controller details Controller Information ---------------------- Remote Computer: YETI Device Name: aac0 Controller type: Adaptec 5400S Access Mode: READ-WRITE Controller serial number: Last six digits = 8A277A Number of Channels: 4 Devices per Channel: 15 Controller CPU: Strong Arm 110...
  • Page 149 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.
  • Page 150 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.
  • Page 151 Table 4-3 Component Revision Items (Continued) Component Revision Item Service: Remote API: Miniport Driver: Controller Software: Controller BIOS: Controller Firmware: Controller Hardware: Related Commands General control commands: (page 2-6) open Meaning Displays the revision level of the network services software. This item displays only if the open controller resides on a remote computer.
  • Page 152: Controller Firmware Compare

    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}...]...
  • Page 153: Controller Firmware Save

    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.
  • Page 154 Related Commands controller commands: controller firmware compare controller firmware update controller Commands (page 4-6) (page 4-9)
  • Page 155: Controller Firmware Update

    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}...]...
  • Page 156: Controller List

    Adapter Name Adapter Type ------------ ------------ \\.\AAC0 Adaptec 5400S The following sections provide descriptions of the items in the display. The Adapter Name and Adapter Type Items The Adapter Name item displays the name(s) of all controllers on the local or remote computers. In the example, there is only one controller on the local computer and it is called AAC0.
  • Page 157 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.
  • Page 158: Controller Pause_Io

    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.
  • Page 159 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.
  • Page 160: Controller Rescan

    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.
  • Page 161: Controller Reset_Scsi_Channel

    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.
  • Page 162: Controller Resume_Io

    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. Syntax controller resume_io Examples The following example resumes all I/O activity on the currently...
  • Page 163: Controller Set Automatic_Failover

    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.
  • Page 164 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.
  • Page 165: Controller Set Array_Verify

    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...
  • Page 166 controller Commands Related Commands controller commands: (page controller show array_verify 4-25) 4-20...
  • Page 167: Controller Show Automatic_Failover

    controller show automatic_failover To display the automatic failover status (enabled or disabled) for the specified controller, use the controller show automatic_failover command. Syntax controller show automatic_failover Examples The following example shows that the controller’s automatic failover is currently disabled: AAC0> controller show automatic_failover Executing: controller show automatic_failover Automatic failover DISABLED Related Commands...
  • Page 168: Controller Show Channels

    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. Syntax controller show channels Examples...
  • Page 169 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.
  • Page 170 controller Commands Related Commands controller commands: (page 4-2) controller details 4-24...
  • Page 171: Controller Show Array_Verify

    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.
  • Page 172 disk Commands In this Chapter disk blink disk initialize disk list disk remove dead_partitions disk set default disk set smart disk show default disk show defects disk show partition disk show smart disk show space disk verify disk zero Use the following syntax for disk commands: disk command [object] [/switch{=value}] [parameter] 5-10...
  • Page 173: 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).
  • Page 174: Disk Initialize

    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...
  • Page 175 /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.
  • Page 176: Disk List

    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.
  • Page 177 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...
  • Page 178 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 Device Type Values Value Meaning Disk The device type is a SCSI direct access device. Typically, these are disk drives.
  • Page 179 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.
  • Page 180 The Rate Column The Rate column displays the negotiated speed of the SCSI device, in megabytes per second. Related Commands disk commands: disk initialize disk show partition disk show space (page 5-3) (page 5-19) (page 5-26) disk Commands...
  • Page 181: Disk Remove Dead_Partitions

    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.
  • Page 182: Disk Set Default

    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.
  • Page 183 Related Commands disk commands: (page disk list disk show default 5-5) (page 5-16) disk Commands 5-12...
  • Page 184: Disk Set Smart

    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 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.
  • Page 185 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.
  • Page 186 /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.
  • Page 187: Disk Show Default

    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. Syntax disk show default Examples The following example shows the default for a SCSI device ID that was set in a previous use of the disk set default command: AAC0>disk show default Executing: disk show default...
  • Page 188: Disk Show Defects

    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.
  • Page 189 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.
  • Page 190: Disk Show Partition

    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...
  • Page 191 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.
  • Page 192 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 The partition is read-only. The partition is read-write. disk Commands 5-21...
  • Page 193: Disk Show Smart

    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.
  • Page 194 /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.
  • Page 195 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.
  • Page 196 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.
  • Page 197: Disk Show Space

    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).
  • Page 198 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 ----------- --------- 0:02:0 Array 0:02:0 Free The following sections provide more information on the columns that the disk show space command displays. The Scsi :ID:L Column The Scsi C:ID:L column displays the SCSI channel number, the...
  • Page 199 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.
  • Page 200: Disk Verify

    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.
  • Page 201 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...
  • Page 202: Disk Zero

    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}...
  • Page 203 /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.
  • Page 204: Diagnostic Clear Boot_Parameters

    diagnostic Commands In this Chapter diagnostic clear boot_parameters diagnostic dump structures diagnostic dump text diagnostic load_arrays diagnostic moderation set count diagnostic moderation set timer diagnostic moderation show count diagnostic moderation show timer diagnostic set boot_parameter diagnostic show boot_parameter diagnostic show history The diagnostic commands are used to help fix problems that can occur during controller operation.
  • Page 205: Technical Support

    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 boot- time parameters are set. Caution: Use this command only under the direction of technical support. Syntax diagnostic clear boot_parameters Examples...
  • Page 206: Diagnostic Dump Structures

    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.
  • Page 207: Diagnostic Dump Text

    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.
  • Page 208 diagnostic Commands Related Commands diagnostic commands: (page 6-3) diagnostic dump structures...
  • Page 209: Diagnostic Load_Arrays

    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.
  • Page 210: Diagnostic Moderation Set Count

    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.
  • Page 211: Diagnostic Moderation Set Timer

    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.
  • Page 212: Diagnostic Moderation Show Count

    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.
  • Page 213: Diagnostic Moderation Show Timer

    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.
  • Page 214: Diagnostic Set Boot_Parameter

    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.
  • Page 215 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...
  • Page 216: Diagnostic Show History

    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.
  • Page 217: Logfile Commands

    logfile Commands In this Chapter logfile end logfile start Use the following syntax for logfile commands: logfile command [/switch{=value}] [parameter]...
  • Page 218: Logfile End

    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.
  • Page 219: Logfile Start

    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.
  • Page 220 logfile Commands Related Commands logfile commands: (page 7-2) logfile end...
  • Page 221: Task List

    task Commands In this Chapter task list task resume task stop task suspend Use the following syntax for task commands: task command [/switch{=value}] [parameter] 8-10 8-12...
  • Page 222: 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.
  • Page 223 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.
  • Page 224 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 file_system 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).
  • Page 225 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.
  • Page 226 The State Column The State Column displays the state of the task. the state values that the task list command can display. State Meaning The task failed and is no longer running. The task successfully completed or the task is no longer running (that is, the task is done).
  • Page 227: Task Resume

    The Specific2 Column The Specific2 column displays additional information for certain tasks that appear in the Task Id column. which the task list command can display additional information. Table 8-4 that task list can display. Table 8-4 Additional Specific2 Information Task .
  • Page 228: Task Resume

    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.
  • Page 229 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 ------ -------- ----- --------- Scrub 24.6% 0 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).
  • Page 230: Task Stop

    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.
  • Page 231 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. Related Commands task commands: (page 8-2) task list 8-11...
  • Page 232: Task Suspend

    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.
  • Page 233 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% ------ -------- ------ --------- Scrub 24.6% 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).
  • Page 234 enclosure Commands In this Chapter enclosure activate slot enclosure identify slot enclosure list enclosure prepare slot enclosure set alarm enclosure set door enclosure set fan enclosure set interval enclosure set power enclosure set scsiid enclosure set temperature enclosure show fan enclosure show power enclosure show slot enclosure show status...
  • Page 235: 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...
  • Page 236 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.
  • Page 237: Enclosure Identify Slot

    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...
  • Page 238 Related Commands enclosure commands: enclosure activate slot enclosure list enclosure prepare slot enclosure show slot (page 9-2) (page 9-6) (page 9-11) (page 9-32) enclosure Commands...
  • Page 239: Enclosure List

    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.
  • Page 240 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 Diagnostic --------- --- ----- ---- ------ ---- ------ -------- -------- --------- The non-detailed enclosure list display contains the following columns of information: Enclosure...
  • Page 241 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).
  • Page 242 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...
  • Page 243 Specifically, the column can display the items listed in 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.
  • Page 244: Enclosure Prepare Slot

    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.
  • Page 245 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...
  • Page 246: Enclosure Set Alarm

    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.
  • Page 247: Enclosure Set Door

    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.
  • Page 248: Enclosure Set Fan

    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.
  • Page 249 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.
  • Page 250: Enclosure Set Interval

    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.
  • Page 251 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 UpTime D:H:M --------- -------------- ---------- -------- -------- -------...
  • Page 252: Enclosure Set Power

    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. Syntax enclosure set power [/off{=boolean}] {enclosure} {powersupply}...
  • Page 253 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. As the following example shows, power supply 0 on enclosure management device 1 is off and operational: AAC0>enclosure show power Executing: enclosure show power...
  • Page 254: Enclosure Set Scsiid

    enclosure set scsiid To set the SCSI device ID for a specific device slot on a specific SAF- TE 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).
  • Page 255 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 --------- ---- ------ ------- ----------------------------------------...
  • Page 256 Related Commands controller commands: controller pause_io enclosure commands: enclosure list enclosure show slot (page 4-12) (page 9-6) (page 9-32) enclosure Commands 9-23...
  • Page 257: Enclosure Set Temperature

    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.
  • Page 258 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 --------- ------ ----------- --------- -------- 70 F The Threshold column now displays 100 degrees.
  • Page 259: Enclosure Show Fan

    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...
  • Page 260 As the example shows, the fan status display contains the following columns: Enclosure 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.
  • Page 261 Related Commands enclosure commands: enclosure list enclosure set fan enclosure show status (page 9-6) (page 9-15) (page 9-36) enclosure Commands 9-28...
  • Page 262: Enclosure Show Power

    enclosure show power To display the status of a specific power supply on a specific SAF- TE 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.
  • Page 263 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.
  • Page 264 Table 9-5 State and Status Columns Status State INSTALLED UNKNOWN Not Applicable INSTALLED UNKNOWN UNKNOWN Related Commands enclosure commands: enclosure list enclosure set power Meaning The power supply is on and not working properly. The power supply is off and not working properly.
  • Page 265: Enclosure Show Slot

    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...
  • Page 266 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 --------- ---- ------ ------- ----------------------------------- 0:00:0 0:01:0 0:10:0 0:03:0 0:04:0 1:00:0 1:01:0 1:10:0 1:03:0...
  • Page 267 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).
  • Page 268 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...
  • Page 269: Enclosure Show Status

    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.
  • Page 270 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 --------- -------------- ---------- -------- -------- ------- 0:04:25 Enclosure Fan Status --------- --- ------------- Enclosure Power State --------- ----- ------------ ------- UNKNOWN Enclosure Slot scsiId Insert...
  • Page 271 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 Commands section.
  • Page 272 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.
  • Page 273 enclosure show power enclosure show slot enclosure show temperature enclosure Commands (page 9-29) (page 9-32) (page 9-41) 9-40...
  • Page 274: Enclosure Show Temperature

    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.
  • Page 275 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.
  • Page 276 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.
  • Page 277: Automated Scripts

    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.
  • Page 278 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. AA 03/04...

This manual is also suitable for:

Aar-2410saAar-2810sa

Table of Contents