HP NetRAID-4M Flexible Array Storage Tool Command Line Interface User’s Guide HP Part Number 5969-8467 Printed in January 2001
Copyright © Copyright 2001, Hewlett-Packard Company. This document contains proprietary information that is protected by copyright. All rights are reserved. No part of this document may be photocopied, reproduced, or translated to another language without the prior written consent of Hewlett-Packard Company. Hewlett-Packard Company Network Server Division Technical Marketing / MS 45S-LE 10955 Tantau Avenue Cupertino, CA 95014 USA Trademarks SCSISelect and FAST are trademarks of Adaptec, Inc.
Contents Contents 1 Getting Started Audience 1-1 Supported Platforms 1-2 Organization 1-2 Conventions 1-4 Related Documentation 1-4 Notes, Cautions, and Warnings 1-5 2 Introducing the Command Line Interface Accessing the CLI from the MS-DOS Prompt 2-1 Accessing the CLI from the Windows NT and Windows 2000 Start Button 2-2 Accessing the CLI from the Flexible Array Storage Tool Window 2-2 Accessing the CLI from the NetWare Server Console 2-2 Accessing the CLI from the UNIX Prompt 2-3 3 Working with Contr
Command Line Interface User’s Guide Displaying a Controller Name 3-8 Displaying a Controller’s Type 3-8 Displaying a Controller’s Availability 3-9 Displaying a Remote Computer Name 3-9 Displaying a Controller’s Serial Number 3-10 Displaying a Controller’s CPU Type 3-10 Displaying the Number of Channels 3-11 Displaying the Number of Devices per Channel 3-12 Displaying a Controller’s CPU Speed 3-12 Displaying Controller Memory 3-13 Displaying the Controller Firmware Build Number 3-14 Rescanning a Controller
Contents Displaying the Revision Number 4-5 Displaying the Number of Blocks 4-6 Displaying the Bytes per Block 4-6 Displaying Disk Usage 4-6 Displaying Disk Defects 4-7 Initializing a Disk 4-8 Displaying the Initialization State of a Disk 4-9 Initializing a Disk 4-9 Working with a Default SCSI ID 4-9 Displaying the Current Default SCSI Device ID 4-10 Setting a Default SCSI Device ID 4-10 Working with Partitions 4-11 Understanding Partition Attributes 4-11 Verifying a Disk 4-18 Verifying a Disk Without Repa
Command Line Interface User’s Guide Adding a Disk to a Diskset 5-12 Removing a Disk from a Diskset 5-13 Deleting a Diskset 5-15 Assigning Diskset Management 5-16 Attaching a Diskset 5-18 Detaching a Diskset 5-19 Changing a Diskset’s Label 5-20 Changing Ownership of a Diskset 5-21 Taking Ownership of a Diskset 5-22 Forcing Ownership of a Diskset 5-23 Releasing Ownership of a Diskset 5-24 Changing a Diskset’s Sparepool Assignment 5-26 6 Working with Container Attributes Understanding Container Identificati
Contents Understanding Container Usage Attributes 6-24 Displaying a Full Compact Snapshot Container 6-25 Displaying the Resident File System 6-26 Displaying a Multi-partition Container 6-27 Displaying a Container that Resides in a NetWare Environment 6-27 Displaying the UNIX-Opened Container 6-27 Displaying an Unknown File System 6-28 Displaying an Unmapped Container 6-28 Displaying an Unconfigured Container 6-29 Displaying a Valid Container 6-29 Understanding State Attributes 6-30 Understanding Mirror Set
Command Line Interface User’s Guide Working with a Stripe Set 7-6 Understanding the Stripe Set Attributes You Can Specify 7-7 Understanding How to Create a Stripe Set 7-9 Understanding Stripe Set Creation in a NetWare Environment 7-10 Understanding Stripe Set Creation in a UNIX Environment 7-10 Identifying Some Tasks to Perform After Creating a Stripe Set 7-11 Working with a Mirror Set 7-11 Understanding the Mirror Set Attributes You Can Specify 7-11 Understanding How to Create a Mirror Set 7-13 Understand
Contents Working with a Stripe Set of RAID-5 Sets (RAID50) 8-14 Creating Multi-level Volume Sets 8-18 Creating a Volume Set of Stripe Sets 8-18 Creating a Volume Set of Mirror Sets 8-21 Creating a Volume Set of RAID-5 Sets 8-25 Creating a Volume Set of Volume Sets 8-28 Working with Multi-level Container’s of Mirror Sets 8-31 9 Modifying Containers Working with Container Reconfiguration 9-2 Understanding the Container Reconfiguration Attributes You can Specify 9-2 Understanding How to Reconfigure a Contai
Command Line Interface User’s Guide Working with Enabling the Container’s Volatile Readahead Cache 9-20 Working with Enabling the Container’s NVRAM Writeback Cache 9-22 Working with Releasing a Container’s Cache Buffers 9-25 Working with Container Rebuild 9-27 Assigning Spare Disks to a Single Container 9-27 Removing Spare Disks from a Single Container 9-29 Assigning Global Spare Disks 9-30 Removing Global Spare Disks 9-31 Working with File Systems 9-33 Adding a File System 9-33 Extending a File System 9-3
Contents Understanding the Update Snapshot Container Attributes that You Can Specify 10-7 Understanding How to Update a Container Snapshot 10-8 Removing a Snapshot Container 10-9 Understanding the Snapshot Container Remove Attributes that You Can Specify 10-9 Understanding How to Remove a Container Snapshot 10-9 Clearing NVRAM of Unconfigured Snapshot Containers 10-11 Understanding the Controller Free Snapshot Attributes You Can Specify 10-11 Understanding How to Clear NVRAM of Unconfigured Snapshot Contai
Command Line Interface User’s Guide Displaying the Mail Subject Line 12-4 Displaying the Mail Body Line 12-5 Setting the Mail Server 12-5 How to Set the Mail Server 12-6 Setting Mail Message Reporting 12-6 How to Set Mail Message Reporting 12-7 Testing Mail Message Reporting 12-8 How to Test the Mail Server 12-8 Clearing Mail Message Reporting 12-9 How to Clear the Mail Server 12-9 13 Working with Tasks Understanding Task Attributes 13-1 Displaying the Task ID 13-2 Displaying the Task Function 13-3 Displ
Contents Locking Information in the Network Connection Database 14-7 Unlocking Information in the Network Connection Database 14-8 Deleting Information from the Network Connection Database 14-10 15 Working with Scripts Executing a Script 15-1 Executing a Script from the CLI Command Prompt 15-2 Executing a Script from the OS Command Prompt 15-2 Example Scripts 15-6 Example 1 15-6 Example 2 15-7 Example 3 15-8 Index xiii
1 Getting Started Hewlett-Packard™NetRAID-4M®RAID Controller products integrate advanced RAID technology with state-of-the-art controller hardware to deliver leadership performance, data availability, and storage management features. To configure and manage components running on the HP NetRAID4M Controller products (hereinafter referred to as the RAID controller), Hewlett-Packard has developed a special software suite.
Command Line Interface User’s Guide material related to storage management on RAID controllers presented in the Flexible Array Storage Tool User’s Guide. This version of the CLI can operate in the Microsoft Cluster Server (MSCS) software environment.
Getting Started Chapter 5, Working with Disksets, describes how to manage disksets that are part of a clustered system. This includes information on how to create, delete, and modify disksets. Chapter 6, Working with Container Attributes, explains how to use container attributes, which are characteristics of a container that you administer or display using the CLI. This chapter includes information about how to display, and, if appropriate, manipulate the container attributes.
Command Line Interface User’s Guide Conventions The following typographical conventions are used in this user’s guide. bold Used to highlight information depicted in examples (for example, the Type column indicates that a RAID-5 set resides on container 0.) Courier Used to highlight commands in text (for example, the container create mirror command) and examples: HPN0> container list Executing: container list No containers found.
Getting Started ■ Flexible Array Storage Tool User’s Guide The Flexible Array Storage Tool User’s Guide provides information about FAST that you need to configure and manage your RAID subsystem. ■ Flexible Array Storage Tool Command Line Interface Reference Guide The Flexible Array Storage Tool Command Line Interface Reference Guide provides information about the CLI commands that you use to configure and manage your RAID subsystem.
2 Introducing the Command Line Interface You can invoke the CLI by doing the following: ■ Accessing the CLI from the MS-DOS Prompt ■ Accessing the CLI from the Windows NT and Windows 2000 Start Button ■ Accessing the CLI from the Flexible Array Storage Tool Window ■ Accessing the CLI from the NetWare Server Console ■ Accessing the CLI from the UNIX Prompt The following sections describe each access method.
Command Line Interface User’s Guide Note: If you specified the path to the afacli executable program in the System Variables on Windows NT or Windows 2000 (basic disk only), then you do not need to specify the path when running afacli. Otherwise, to run the afacli program, you must change to the directory where the afacli program resides. Accessing the CLI from the Windows NT and Windows 2000 Start Button To access the CLI from the Windows NT or Windows 2000 Start button, follow these steps.
Introducing the Command Line Interface Accessing the CLI from the UNIX Prompt To access the CLI from the UNIX prompt, type hpncli from the command prompt.
3 Working with Controllers This chapter explains how to use the CLI to manage a RAID controller so that you can manage such storage resources as disks, containers, freespace, partitions, and file systems. You use controller CLI commands to display the status of a variety of controller attributes and to perform such controller-related tasks as pausing and resuming I/O, and enabling or disabling automatic spare.
Command Line Interface User’s Guide operations, the CLI displays an appropriate message. In this case, you can open the controller for read-only operations. If you open a controller with read-only access, you can use only the commands that do not change the controller configuration. If you execute a command that is not valid in read-only mode, the CLI displays an appropriate error message. After you open a controller, you are ready to work with the controller attributes.
Working with Controllers The CLI allows you to open a controller in the following modes: ■ Read/write ■ Read-only ■ Snapshot Modes of Opening and Closing a Controller The CLI allows you to open and close a controller on the supported operating system using the following modes: ■ Read/write ■ Read-only ■ Snapshot The following sections describe how to open a controller in these three modes and how to close a controller.
Command Line Interface User’s Guide Opening a Controller in Snapshot Mode A snapshot is an instantaneous read-only copy of a container "snapped" at a precise point in time. Automated backup scripts can take advantage of the snapshot feature. The open command provides a snapshot mode that allows an automated backup script to work even if other users have the CLI open somewhere on the network.
Working with Controllers the domain name for the NetWare system. The Adapter Name column indicates that HPN0 is the name of the controller installed on the computer. The example also indicates the controller’s path, which is \\.\ HPN0> controller list /domain=D1 Executing: controller list /domain=D1 Adapter Name Adapter Type Availability Clustering ------------ ------------ ------------ ---------- \\.
Command Line Interface User’s Guide Table 3-1.
Working with Controllers CLI Operations Related Commands controller CPU speed Display controller details Displaying a Controller’s CPU Speed controller memory Display controller details Displaying Controller Memory Controller Attribute Discussed In... The following sections describe how to display the controller attributes.
Command Line Interface User’s Guide details for the controlling partner.The Cluster Partner Controller 1 Information items show controller details for the peer partner. HPN0> controller details Executing: controller details Clustered Partner Controller 0 Information ------------------------------------------. . . Clustered Partner Controller 1 Information -----------------------------------------. . .
Working with Controllers Type column indicates that HP NetRAID-4M is the controller type (product name) for controller HPN0. HPN0> controller list Executing: controller list Adapter Name Adapter Type Availability Clustering ------------ ------------ ------------ ---------- \\.\HPN0 HP NetRAID-4M read/write No Displaying a Controller’s Availability The availability attribute indicates the access mode of a controller. You can open a controller in snapshot, read/write, or read-only mode.
Command Line Interface User’s Guide Executing: controller details Controller Information ---------------------Remote Computer: SUL9999B Device Name: HPN0 Controller Type: HP NetRAID-4M . . . Controller Hardware: 1.0 Displaying a Controller’s Serial Number The controller serial number attribute indicates the last six hexadecimal characters of the controller serial number. These six characters match the last six characters appearing on the “SN =” sticker located on the controller.
Working with Controllers To display the controller’s CPU type, use the controller details command, as in the following example. In the example, the Controller CPU item indicates that Strong Arm 110 is the CPU type.
Command Line Interface User’s Guide Access Mode: READ-WRITE Controller Serial Number: Last Six Digits = A7F90F Number of Channels: 4 . . . Controller Hardware: 1.0 Displaying the Number of Devices per Channel The device per channel or targets attribute indicates the maximum number of devices, not including the host controller, that can reside on a channel. To display the number of targets on a channel, use the controller details command, as in the following example.
Working with Controllers the Controller CPU Speed item indicates that the controller CPU speed is 233 Mhz. HPN0> controller details Executing: controller details Controller Information ---------------------Device Name: HPN0 Controller Type: HP NetRAID-4M Access Mode: READ-WRITE Controller Serial Number: Last Six Digits = A7F90F Number of Channels: 4 Devices per Channel: 15 Controller CPU: Strong Arm 110 Controller CPU speed: 233 Mhz . . . Controller Hardware: 1.
Command Line Interface User’s Guide Devices per Channel: 15 Controller CPU: Strong Arm 110 Controller CPU Speed: 233 Mhz Controller Memory: 80 Mbytes . . . Controller Hardware: 1.0 Displaying the Controller Firmware Build Number The controller firmware attribute indicates the controller’s firmware build number. To display the controller’s firmware build number, use the controller details command, as in the following example.
Working with Controllers Rescanning a Controller The controller rescan operation scans the controller’s channels and verifies the presence of currently connected devices and newly connected devices. If any disk partition structures have changed, rescanning updates those changes in the controller memory’s container and partition lists. If you add devices to the controller, the rescan enables the controller to use those devices.
Command Line Interface User’s Guide You can set a maximum pause of 150 seconds for all I/O activity on the currently opened controller. Note: A controller cannot be paused if a container task is running on the controller. Note: If you need to pause the system for more than a minute, then network timeouts might occur. However, network timeouts are usually preferable to rebooting.
Working with Controllers Note: The pause_io command is not available in the UNIX environment. To resume a controller’s I/O operations, use the controller resume_io command, as in the following example. The controller resume_io command also rescans the SCSI channels on the controller, verifying currently connected disks and recognizing new disks that have been added to the channels.
Command Line Interface User’s Guide ! Caution: The controller deletes any data on the replacement disk when automatic spare is enabled and you remove the failed disk and insert the replacement disk in the failed disk’s slot. Note: The automatic spare feature works only with disks that reside in a SAF-TE enclosure management device.
Working with Controllers flash image (UFI) files, or to save a controller’s current flash contents to a pair of UFI files. NetRAID-4M controllers use nonvolitile flash to store on-board software, such as BIOS, microprocessor kernel and monitor. When it becomes necessary to update any of those components (for example, to correct a problem or provide a new feature) you must update your controller’s flash components with newer flash images.
Command Line Interface User’s Guide Each NetRAID-4M controller requires a different pair of UFI files, since the flash components and contents vary from one controller type to another. The CLI associates each controller type with a unique pair of UFI filenames, so it can select the correct UFI files from a set of UFI files when updating or verifying a controller. A UFI filename uniquely identifies the associated controller type and is common across all of the volume filenames.
Working with Controllers If the CLI encounters a problem during these integrity checks, it issues an error and does not continue the flash update. Understanding Channel Attributes A channel is a path used for transferring and controlling data between a storage controller and storage devices. SCSI devices present on a controller are identified by a combination of their channel number, SCSI device ID (also known as the target ID), and Logical Unit Number.
Command Line Interface User’s Guide The following sections describe how to display and, if appropriate, manipulate the channel attributes. Displaying a Channel Number The channel number attribute identifies the number of each channel present on a controller. The maximum number of channels is determined by the controller model. Each channel is identified by a channel number from 0 to the controller’s maximum number of channels minus 1.
Working with Controllers Displaying the Maximum Number of Targets on a Channel The targets or devices per channel attribute indicates the maximum number of SCSI devices, not including the host controller, that can reside on a channel. To display the number of targets on a channel, use the controller show channels command, as in the following example. In the example, the Targets column indicates that there can be up to 15 targets on channels 0 and 1.
Command Line Interface User’s Guide Displaying a Channel’s Speed The channel speed attribute indicates the speed at which a channel is operating. If drives other than Ultra-2 are present on the system, the entire channel is limited to UltraWide. To display the speed of a channel, use the controller show channels command, as in the following example. In the example, the Max Usage column indicates a maximum speed of NoInfo for channel 0. NoInfo indicates that this information is not available.
Working with Controllers Table 3-3. Battery Attributes Battery Attribute CLI Operations battery state Display Recondition Related Commands Discussed in... controller details controller battery_recondition Displaying the Condition of a Controller’s Battery Displaying the Condition of a Controller’s Battery To display the condition of the battery, use the controller details command, as in the following example. In the example, the Battery State item indicates that the battery is Ok.
Command Line Interface User’s Guide Reconditioning the Battery To recondition the battery, use the controller battery_recondition command, as in the following example: HPN0> controller battery_recondition Executing: controller battery_recondition Note: On Windows NT and Windows 2000 (basic disk only), if you have enabled the battery_good_finished_recondition e-mail messaging feature, an e-mail message indicating that the battery is fully charged will be sent to a designated recipient.
4 Working with Disks This chapter explains how to use the CLI to manage the disks connected to a RAID controller. In this document, a disk is a randomly accessible, re-writable SCSI data storage device on a SCSI channel. Each disk is a component in a RAID configuration and is connected to a controller by a channel. The CLI enables you to monitor disk characteristics and parameters, prepare a disk for use by a controller, and detect defects.
Command Line Interface User’s Guide Understanding Disk Attributes Disk attributes are the characteristics of a disk that you can administer or display using the CLI. Table 4-1 lists the disk attributes and their related CLI commands. Table 4-1. Disk Attributes Attribute CLI Operations Related Commands Discussed in...
Working with Disks Displaying the SCSI Device ID The SCSI device ID attribute identifies an ID number assigned to each SCSI device attached to a SCSI channel, which you need to perform operations on a disk device. You also use the SCSI device ID to perform some container-related tasks. SCSI devices connected to a controller are identified by their channel number, SCSI device ID, and logical unit number, which are shown as C:ID:L in command output listings.
Command Line Interface User’s Guide connected to the controller, which is Disk for device 2:01:0 and 2:02:0. HPN0> disk list Executing: disk list C:ID:L Device Type Blocks Bytes/Block Usage Shared ------ ------------ --------- ----------- ------------- ---- 2:01:0 Disk 17783240 512 Initialized NO 2:02:0 Disk 17783240 512 Initialized NO See the disk list command in the Command Line Interface Reference Guide for a list of possible device types.
Working with Disks the Vendor ID column indicates that ACME is the name of the vendor for device 2:01:0. (Note that the example eliminates some items in the disk list display to make the example readable on this page.
Command Line Interface User’s Guide 2:01:0 Disk N ACME ST39102LW 0006 Displaying the Number of Blocks The number of blocks attribute indicates the total number of disk blocks available on a device. A block is the unit in which data is stored and retrieved on a fixed-block disk architecture. To display the number of blocks available on the devices connected to a controller, use the disk list command, as in the following example.
Working with Disks controller. To determine the usage of your disks, use the disk list command. Table 4-2 shows the possible disk usage values: Table 4-2. Disk Usage Values. Value Meaning DOS The SCSI device was prepared for use with DOS partitions. Initialized The SCSI device was prepared (initialized) for use with containers. This is the value that appears in the example.
Command Line Interface User’s Guide from the disk show defects command with the /full switch. The example shows the total number of primary defects (5) and the location of each primary defect. The location of defect 1 is at cylinder 229, head 7, sector 203.
Working with Disks Displaying the Initialization State of a Disk To determine if the disks attached to a controller are initialized, use the disk list command, as in the following example. The listing shows that the first three disks are Initialized, and that the fourth disk with a SCSI device ID of 2:04:0 is Not Initialized. Note that the Usage column displays Initialized or Not Initialized. See Displaying Disk Usage on page 4-6 for a description of the other values that can appear in the Usage column.
Command Line Interface User’s Guide convenience, you can simplify the specification of the SCSI device ID. Ordinarily, when specifying a CLI command that requires a SCSI device ID, you must specify a channel number, device ID, and logical unit number; for example, disk list (2,1,0). When you set a default SCSI ID, you can specify just the device ID, for example, disk list 1. The CLI allows you to do the following: ■ Display the current SCSI device ID default ■ Set a default SCSI device ID.
Working with Disks C:ID:L Device Type Blocks ------ ----------- --------- ----------- ---------------- ------ 2:01:0 Disk Bytes/Block Usage 17938986 512 Initialized Shared NO Working with Partitions A partition is a contiguous area of a physical disk that makes up some or all of a container. Partitions are created and managed by the controller as by-products of container creation or rebuild operations.
Command Line Interface User’s Guide Table 4-3. Partition Attributes Attribute CLI Operations Related Commands Discussed in...
Working with Disks Displaying a Partition’s Offset The partition offset attribute indicates the logical distance from the beginning of a disk to the start of a partition. A partition’s offset is determined when you create a container. The CLI allows you to display a partition’s offset. To display the partition offset, use the disk show partition command, as in the following example. The Partition Offset column shows an offset of 64.0KB for SCSI devices (2,1,0) and (2,2,0).
Command Line Interface User’s Guide Scsi Partition C:ID:L Offset:Size Container MultiLevel Num Type Num Type R/W ------ ------------- --- ------ --- ------ --2:01:0 64.0KB: 15.0MB 0 Mirror 0 None RW 2:02:0 64.0KB: 15.0MB 0 Mirror 0 None RW The container list command also displays a partition’s size. See any of the container create examples in Chapter 7, Working With Single-level Containers, for further information on the container list command.
Working with Disks The CLI also lets you renumber (assign another ID to) a container. See Chapter 9, Modifying Containers, for a description of how to renumber a container. Displaying a Container’s Type The container type attribute indicates if a partition resides in a volume set, stripe set, RAID-5 set, etc. To display the type of container in which the partition resides, use the disk show partition command, as in the following example.
Command Line Interface User’s Guide C:ID:L Offset:Size Num Type Num Type R/W ------ ------------- --- ------ --- ------ --2:01:0 64.0KB: 100MB 62 Mirror 0 Stripe RW 2:02:0 64.0KB: 100MB 63 Mirror 0 Stripe RW 2:03:0 64.0KB: 100MB 63 Mirror 0 Stripe RW 2:04:0 64.0KB: 100MB 62 Mirror 0 Stripe RW Displaying a Multilevel Container’s Type The multilevel container type attribute indicates the kind of a multilevel container in which the partition resides.
Working with Disks the R/W column shows that the partitions on SCSI devices (2:01:0) and (2:02:0) are read/write (RW) accessible. HPN0> disk show partition Executing: disk show partition Scsi Partition C:ID:L Offset:Size Container MultiLevel Num Type Num Type R/W ------ ------------- --- ------ --- ------ --2:01:0 64.0KB: 100MB 62 Mirror 0 Stripe RW 2:02:0 64.0KB: 100MB 63 Mirror 0 Stripe RW 2:03:0 64.0KB: 100MB 63 Mirror 0 Stripe RW 2:04:0 64.
Command Line Interface User’s Guide Scsi Partition C:ID:L Offset:Size Container MultiLevel Num Type Num Type R/W ------ ------------- --- ------ --- ------ --2:01:0 64.0KB! 15.0MB 0 Mirror 0 None RW 2:02:0 64.0KB: 15.0MB 0 Mirror 0 None RW The container list command also shows dead partitions. See Displaying and Removing a Dead Partition on page 4-17 for more information on dead partitions.
Working with Disks Blinking a Disk Light The disk blink command causes a disk drive’s activity light to flash or stop flashing. This feature allows you to identify the physical drive that corresponds to a disk displayed by the disk list command. Before executing the disk blink command, use the disk list command to display the SCSI device ID of the disk to be blinked. To blink a disk drive’s activity light, use the disk blink command, as in the following example.
Command Line Interface User’s Guide Understanding S.M.A.R.T. Attributes S.M.A.R.T. attributes are characteristics of the S.M.A.R.T. technology that you can administer or display using the CLI. Table 4-4 lists the S.M.A.R.T. attributes and related CLI commands. Table 4-4. S.M.A.R.T. Attributes CLI Operations Related Commands S.M.A.R.T. capable device Display disk show smart Displaying S.M.A.R.T.
Working with Disks S.M.A.R.T. Attribute CLI Operations Related Commands report count Display disk show smart disk set smart Displaying and Setting the Report Count disk show smart disk set smart Displaying and Clearing the Error Count Set Display error count Set Discussed in... The following sections describe how to display and, if appropriate, set the S.M.A.R.T. attributes. Displaying S.M.A.R.T. Capable Devices The S.M.A.R.T.
Command Line Interface User’s Guide ■ Set the MRIE of your devices To display the MRIE for a device, use the disk show smart command, as in the following example: HPN0> disk show smart Executing: disk show smart Smart Method of Enable Capable Informational Exception Performance Error C:ID:L Device Exceptions(MRIE) Control Enabled Count ------ ------- ---------------- --------- ----------- ------ 2:01:0 Y 0 Y N 0 2:02:0 Y 0 Y N 0 The Method of Informational Exceptions colum
Working with Disks After setting the MRIE value, use the disk show smart command to verify the MRIE setting. Displaying and Enabling the Exception Control Setting The enable exception control attribute indicates whether exception reporting is enabled. Exception reporting is a S.M.A.R.T. feature that reports exceptions according to the Method of Reporting Informational Exceptions (MRIE) method, which is described in Displaying and Enabling the MRIE Performance Setting on page 4-24.
Command Line Interface User’s Guide Displaying and Enabling the Exception Control Setting on page 4-23 for further information. Displaying and Enabling the MRIE Performance Setting The MRIE performance enabled attribute indicates whether to report exceptions according to the MRIE method, taking disk performance into consideration. If you enable this feature, S.M.A.R.T. reports exceptions if disk performance has not degraded; otherwise, exception reporting stops.
Working with Disks Displaying and Enabling Error Logging The log errors attribute indicates whether S.M.A.R.T. exception logging is enabled. The CLI allows you to do the following: ■ Display whether S.M.A.R.T. error logging is enabled ■ Enable S.M.A.R.T. error logging To determine whether S.M.A.R.T. error logging is enabled, use the disk show smart command, as in the following example. Note that the Log Errors column appears only if you specify the /full switch with the disk show smart command.
Command Line Interface User’s Guide Displaying and Setting the Exception Report Interval The interval timer attribute indicates the frequency of S.M.A.R.T. exception reporting for specified disks. The CLI allows you to do the following: ■ Display the S.M.A.R.T. interval timer setting for your disks ■ Set the S.M.A.R.T. interval timer To display the interval timer setting for exception reporting, use the disk show smart command, as in the following example.
Working with Disks After setting the S.M.A.R.T. interval timer, use the disk show smart command to verify the exception interval timer setting. Displaying and Setting the Report Count The report count attribute indicates the number of times that S.M.A.R.T. can report an exception. The CLI allows you to do the following: ■ Display the S.M.A.R.T. report count setting for your disks ■ Set the S.M.A.R.T. report count To display the S.M.A.R.T.
Command Line Interface User’s Guide After setting the report count, use the disk show smart command to verify the report count setting. Displaying and Clearing the Error Count The error count attribute indicates the number of errors that S.M.A.R.T. encountered on a disk. The CLI allows you to do the following: ■ Display the error count ■ Clear the error count To display the number of errors on a disk, use the disk show smart command, as in the following example.
5 Working with Disksets This chapter explains how to use the CLI to manage disksets. A diskset is a logical grouping of disks used on a clustered system. A diskset’s member disks may reside on one or more shared channels, but may not contain disks on non-shared channels. You can think of a diskset as a way to define additional layered storage elements in a RAID controller subsystem. The CLI enables you to create, and delete a diskset as well as determine the owner of a diskset.
Command Line Interface User’s Guide For information about... Turn to... Assigning Diskset Management page 5-16 Attaching a Diskset page 5-18 Detaching a Diskset page 5-19 Changing a Diskset’s Label page 5-20 Changing Ownership of a Diskset page 5-21 Changing a Diskset’s Sparepool Assignment page 5-26 Understanding Diskset Attributes Diskset attributes are the characteristics of a diskset that you can administer or display using the CLI.
Working with Disksets Attribute CLI Operations Related Commands Discussed In...
Command Line Interface User’s Guide Diskset ID column indicates that there is one diskset on the controller. The diskset ID is 0x01be868c1d74a640. Note that the example alters the disk_set list output so that the data can fit on the page. HPN0> disk_set list Executing: disk_set list Diskset ID Creator ID Owner ------------------- ------------------ ------------------ 0x01be868c1d74a640 0xfafaf001007a1c00 \\.
Working with Disksets Displaying the Owner The owner attribute indicates the name of the controller that owns the diskset. When you create a diskset, diskset ownership is assigned by default to the controlling partner. The controller on the owning node is in charge of managing container and partition operations for disks in the diskset. When a disk on a shared channel is not owned by either node in a cluster, you cannot perform container operations on the disk.
Command Line Interface User’s Guide Displaying the Number of Disks in a Diskset The disks attribute indicates the number of disks in a diskset. You specify the number of disks in a diskset when you create a diskset using the disk_set create command. See Creating a Diskset on page 5-11 for information on creating a diskset. You can add disks to a diskset using the disk_set add command. See Adding a Disk to a Diskset on page 5-12 for information on adding disks to a diskset.
Working with Disksets Executing: disk_set list Diskset ID Creator ID Owner ------------------- ------------------ ------------------ 0x01be868c1d74a640 0xfafaf001007a1c00 \\.\HPN0 Disks Attached OS Managed Label Shared Spare ------ -------- ---------- ---------- ------ ----- 1 NO NO Saturn YES YES Displaying if a Diskset is Managed by the MS Cluster Service The OS managed attribute indicates if a diskset is managed by the Microsoft Cluster Service (MSCS).
Command Line Interface User’s Guide to a diskset. See Creating a Diskset on page 5-11 for information on creating a diskset. You use the disk_set changelabel command to change a diskset’s label. See Changing a Diskset’s Label on page 5-20 for information on changing a diskset label. To display a diskset’s label, use the disk_set list command, as in the following example. In the example, the Label column indicates Saturn, which is the diskset label.
Working with Disksets Displaying if a Diskset is a Member of a Spare Pool The spare attribute indicates if a diskset is a member of a spare pool. A spare pool is a collection of disksets that function as spare devices. When creating a diskset, you use the disk_set create command to assign a diskset as a spare diskset. See Creating a Diskset on page 5-11 for information on creating a diskset. You can use the disk_set changespare pool command to change a diskset’s spare pool assignment.
Command Line Interface User’s Guide ------ -------- ---------- ---------- ------ -------- ------1 NO NO Saturn YES YES 5/26/2000-14:30:56 Displaying Members of a Diskset The members attribute indicates the SCSI device ID for all disk drives that reside in a diskset. You specify the disk drives that initially reside in a diskset when you create a diskset using the disk_set create command. See Creating a Diskset on page 5-11 for information on creating a diskset.
Working with Disksets Creating a Diskset You use the disk_set create command to create a diskset. When you create a diskset, you specify the disks that are to comprise the diskset. Only disksets, not individual disks, can be attached to a controller in a cluster environment. See the Flexible Storage Array Tool User’s Guide for information on diskset concepts. Once a diskset has been created, it must be attached to a controller before it can be used.
Command Line Interface User’s Guide After running the disk_set create command to create a diskset, use the disk_set list command to display information about your disksets, as in the following example. In the example, the Diskset ID column indicates that the diskset ID is 0x01be868c1d74a640, the Creator ID column indicates that the creator ID is 0xfafaf001007a1c00, the Owner column indicates that the Owner is \\.\HPN0, and the Label column indicates that Saturn is the diskset label.
Working with Disksets ------ -------- ---------- ---------- ------ 2 NO NO Saturn YES ----NO To add a disk to a diskset, use the disk_set add command, as in the following example. In the example, SCSI device (2,2,0) is added to the diskset having a diskset ID of 0x01be868c1d74a640 and a creator ID of 0xfafaf001007a1c00.
Command Line Interface User’s Guide (2:00:0), (2:01:0), and (2:02:0). Note that the example alters the disk_set list output so that the data can fit on the page. HPN0> disk_set list /members Executing: disk_set list Diskset ID Creator ID Owner ------------------- ------------------ ------------------ 0x01be868c1d74a640 0xfafaf001007a1c00 \\.
Working with Disksets ------------------- ------------------ ------------------ 0x01be868c1d74a640 0xfafaf001007a1c00 \\.\HPN0 Disks Attached OS Managed Label Shared Spare ------ -------- ---------- ---------- ------ ----- 2 NO NO Saturn YES NO Members of the Disk Set: C:ID:L ------2:00:0 2:01:0 Deleting a Diskset You use the disk_set delete command to delete a diskset. The disk_set delete command deletes all disks from a diskset.
Command Line Interface User’s Guide 0x01be868c1d74a640 and whose creator ID is 0xfafaf001007a1c00 is deleted. HPN0>disk_set delete 0x01be868c1d74a640 0xfafaf001007a1c00 Executing: disk_set delete 125,685,775,960,680,000 -361,712,932,956,267,520 After running the disk_set delete command to delete a diskset, use the disk_set list command to display information about your disksets, as in the following example.
Working with Disksets HPN0> disk_set list Executing: disk_set list Diskset ID Creator ID Owner ------------------- ------------------ ------------------ 0x01be868c1d74a640 0xfafaf001007a1c00 \\.\HPN0 Disks Attached OS Managed Label Shared Spare ----- ------ -------- ---------- ---------- ------ 3 NO NO Saturn YES NO To assign MSCS management of a diskset, use the disk_set OSmanaged command with the /false switch, as in the following example.
Command Line Interface User’s Guide Attaching a Diskset Attaching a diskset makes the diskset available for use by the controller and the host operating system. You use the disk_set attach command to attach a diskset to a controller. To attach a diskset, the diskset must be owned by either the controlling or peer partner. Before attaching a diskset, use the disk_set list command to display information about your disksets, as in the following example.
Working with Disksets ------------------- ------------------ ------------------ 0x01be868c1d74a640 0xfafaf001007a1c00 \\.\HPN0 Disks Attached OS Managed Label Shared Spare ------ -------- ---------- ---------- ------ ----- 3 YES NO Saturn YES NO Detaching a Diskset You use the disk_set detach command to detach a diskset from a controller. Detaching a diskset makes the diskset unavailable for use by the controller and the host operating system.
Command Line Interface User’s Guide After running the disk_set detach command to detach a diskset, use the disk_set list command to display information about your disksets, as in the following example. In the example, the Attached column indicates NO, which means that the diskset is detached. Note that the example alters the disk_set list output so that the data can fit on the page.
Working with Disksets To change a diskset’s label, use the disk_set changelabel command, as in the following example. In the example, the command changes the label of the diskset whose diskset ID is 0x01be868c1d74a640 and whose creator ID is 0xfafaf001007a1c00 to Mercury.
Command Line Interface User’s Guide Taking Ownership of a Diskset Taking ownership of a diskset assigns ownership of a diskset to either the controlling or peer partner. Before taking ownership of a diskset, the diskset can be owned by neither the controlling partner nor the peer partner; that is, it can be owned by "unowned." You use the disk_set takeownership command to take ownership of a diskset.
Working with Disksets display information about your disksets, as in the following example. In the example, the Owner column indicates that the controlling partner whose Owner is \\.\HPN0 owns the diskset. Note that the example alters the disk_set list output so that the data can fit on the page. HPN0> disk_set list Executing: disk_set list Diskset ID Creator ID Owner ------------------- ------------------ ------------------ 0x01be868c1d74a640 0xfafaf001007a1c00 \\.
Command Line Interface User’s Guide Disks Attached OS Managed Label Shared Spare ------ -------- ---------- ---------- ------ ----- 3 NO NO Mercury YES NO To force ownership of a diskset, use the disk_set forceownership command, as in the following example. In the example, the command’s /partner switch assigns ownership of the diskset to the peer partner, which has a diskset ID of 0xfafaf001007a1c00 and a creator ID of 0xfafaf001007a1c00.
Working with Disksets Before releasing ownership of a diskset, use the disk_set list command to display information about your disksets, as in the following example. In the example, the Owner column indicates \\BULLDOG\HPN1, which means that the peer partner owns the diskset. Note that the example alters the disk_set list output so that the data can fit on the page.
Command Line Interface User’s Guide Disks Attached OS Managed Label Shared Spare ------ -------- ---------- ---------- ------ ----- 3 NO NO Mercury NO YES Changing a Diskset’s Sparepool Assignment Changing a diskset’s sparepool assignment either assigns a diskset to a sparepool or unassigns a diskset from a sparepool. To change a diskset’s sparepool assignment, the diskset must be owned and attached by either the controlling or peer partner.
Working with Disksets After running the disk_set changespare pool command to change a diskset’s sparepool assignment, use the disk_set list command to display information about your disksets, as in the following example. In the example, the Spare column indicates YES, which means that the diskset is assigned as a sparepool. Note that the example alters the disk_set list output so that the data can fit on the page.
6 Working with Container Attributes A container is a logical disk created from freespace and made up of one or more partitions on one or more physical disks. A container can span multiple physical disks and can be larger than any one of the physical disks. See the Flexible Array Storage Tool User’s Guide for a discussion of container concepts. Before you can work with containers, you must have previously opened the controller.
Command Line Interface User’s Guide For information about… Turn to ... Understanding Container Access Attributes page 6-20 Understanding Container Usage Attributes page 6-24 Understanding State Attributes page 6-30 Understanding Container Cache Attributes page 6-39 Understanding Container Identification Attributes The container identification attributes identify a container.
Working with Container Attributes Table 6-1. Container Identification Attributes Attribute CLI Operations Related Commands Discussed in...
Command Line Interface User’s Guide Attribute CLI Operations container Create number Display Renumber container Create label Display Set container Create type Display Related Commands Discussed in...
Working with Container Attributes Displaying, Assigning, and Removing a Drive Letter (Windows Only) The drive letter attribute identifies the drive letter associated with a container. Drive letters do not automatically get assigned when you create a container. Some operations, for example, adding a file system to a container, require that you assign a drive letter to a container.
Command Line Interface User’s Guide The specification of the drive letter is optional. If you omit the drive letter, the CLI assigns the next available drive letter. Note that Windows Explorer displays the drive letter you assign here in its All Folder’s pane (the left pane). After executing the container assign drive_letter command, use the container list command again to verify that the drive letter was assigned, as in the following example.
Working with Container Attributes column. On UNIX systems, containers are associated with root special files not drive letters. See your UNIX documentation for information on how to mount the container or to create a file system. Displaying and Specifying a Cluster Partner The cluster partner attribute identifies the cluster partner on which a controller resides in a cluster environment. See the Flexible Array Storage Tool User’s Guide for a discussion of cluster concepts.
Command Line Interface User’s Guide Executing: container list Cluster Num Dr Partner Label Type Total Oth Stripe Size Ctr Size Scsi Usage Partition C:ID:L Offset:Size -- ------- ----- ----- ------ --- ------ ------ ------ ----------F: 0 0 Volume 100MB NTFS 0:00:0 64.0KB: 100MB Specifying a Cluster Partner Some CLI commands require that you specify the cluster partner (controlling or peer) on which you want to perform an operation.
Working with Container Attributes Command /cluster_partner switch /partner switch disk_set forceownership x disk_set take ownership x To specify a cluster partner, use a command listed in Table 6-2, as in the following example. In the example, the controller show container_verify command displays the container verify status for the controller on cluster partner 1, the peer partner.
Command Line Interface User’s Guide and the peer partner is indicated with the number 1. For example, container 3 on the peer partner is indicated as (1,3). The CLI allows you to do the following: ■ Display a container’s ID ■ Renumber a container’s ID ■ Specify a cluster partner as part of the container ID Displaying a Container’s ID To display a container’s ID, use the container list command, as in the following example. In the example, the Num Label column indicates that the container ID is 0.
Working with Container Attributes following example, the container offline command takes container 0 on cluster partner 1 (the peer cluster partner) offline. HPN0> container offline (1,0) Executing: container offline 1,0 Displaying and Setting a Container Label The container label attribute identifies the name assigned to a container. Labels do not automatically get assigned when you create a container. Note that this label is not the label that displays in Windows Explorer and Disk Administrator.
Command Line Interface User’s Guide You can also assign a label to a container when you create it using the following commands: ■ container create mstripe ■ container create mvolume ■ container create raid5 ■ container create stripe ■ container create volume See Chapter 7, Working With Single-level Containers, and Chapter 8, Working with Multi-level Containers, for information on using these commands.
Working with Container Attributes Container Type Meaning RAID-5 The container is a RAID-5 set. A RAID-5 set is a single-level container that is similar to a stripe set, except that its data is redundant. Reconf The container was reconfigured. A reconfigured container is a container that was converted from one container type to another. The Reconf container type is not used in UNIX. To display a container’s type, use the container list command, as in the following example.
Command Line Interface User’s Guide Cluster Num Total Dr Partner Label Type Oth Stripe Size Ctr Size Scsi Usage C:ID:L RO State -- -------- ----- ------ ------ --- ------ ------- -------- -- ----0 0+62 Volume 15MB 1 0 1+63 Stripe 45MB 0 32KB None 0:02:0 Snapped None 0:02:0 RO SnpShot 0:03:0 0:04:0 Understanding Container Creation Attributes The container creation attributes indicate when a container was created.
Working with Container Attributes Executing: container list /full=TRUE Cluster Num Dr Partner Label Type Total Oth Stripe Size Ctr Size Scsi Usage Creation C:ID:L Date Time -- ------- ----- ------ ------ --- ------ ------- ------ ------ -----0 0 Volume 100MB None 2:01:0 082099 15:12:23 Displaying a Container’s Creation Time The creation time attribute indicates the hour, minute, and second that you created the container.
Command Line Interface User’s Guide Table 6-5. Container Size Attributes Attributes total size CLI Operations Create Display stripe size Related Commands Discussed in...
Working with Container Attributes Understanding Freespace Freespace is the space on an initialized disk that is not being used by other RAID components. Containers are created from freespace. When a container is deleted, its space is returned to freespace. You specify freespace in terms of a SCSI device ID and, optionally, a size as in the following example. If the size parameter is not specified, the freespace defaults to the size of the first freespace area available on the specified SCSI device.
Command Line Interface User’s Guide To convert freespace to container space, use the container create raid5 command, the container create stripe command, the container create volume command, or the container extend volume command. See Chapter 7, Working With Single-level Containers, for a description of the container create commands. See Chapter 9, Modifying Containers, for a description of the container extend command.
Working with Container Attributes Displaying and Setting a Container’s Total Size The total size attribute indicates the number of bytes in a container. The size of a container is the size of the freespace you specified when you created, reconfigured, or extended the container. To display a container’s total size, use the container list command, as in the following example. In the example, the Total Size column indicates that the size of container 0 is 15MB.
Command Line Interface User’s Guide 0 0 Volume 15MB 0 1 Stripe 45MB 32KB None 2:01:0 64KB: None 2:02:0 64KB: 15MB 15MB 2:03:0 64KB: 15MB 2:04:0 64KB: 15MB You set the stripe size of a container when performing the following operations: ■ Creating a multi-level stripe set (container create mstripe command) ■ Creating a RAID-5 set (container create raid5 command) ■ Creating a stripe set (container create stripe command) ■ Reconfiguring a container (container reconfigure command)
Working with Container Attributes Table 6-6. Container Access Attributes CLI Operations Related Commands Discussed in...
Command Line Interface User’s Guide Cluster Num Dr Partner Label Type Total Oth Stripe Size Ctr Size Scsi Usage C:ID:L RO -- ------- ----- ------ ------ --- ------ ------- ------ -0 0 Volume 100MB None 2:01:0 To set a container’s availability to read-only, use the container readonly command, as in the following example. In the example, container 0 is set to read-only availability.
Working with Container Attributes To set a container’s availability to read/write, use the container readwrite command, as in the following example. In the example, container 0 is set to read/write availability. HPN0> container readwrite 0 Executing: container readwrite 0 After executing the container readonly command, use the container list command again to verify that the container is set to read/write availability.
Command Line Interface User’s Guide To display whether a container is locked, use the container list command with the /full switch, as in the following example. In the example, the Lk column is blank, which indicates that container 0 is not locked. (Note that the example eliminates some items in the container list display to make the example readable on this page.
Working with Container Attributes Table 6-7.
Command Line Interface User’s Guide snapshot container, you can specify whether to use compact mode. Compact mode uses a smaller backing container. The dead snapshot attribute indicates that a compact snapshot (backing) container is 100% full and its file system is no longer accessible. See Chapter 10, Working with Snapshot Containers, for information on how to create a snapshot container. To display whether a compact snapshot container is dead, use the container list command, as in the following example.
Working with Container Attributes Displaying a Multi-partition Container The multi-partition container attribute indicates that a file system resides on a multi-partition container. A multi-partition container is a container that has multiple operating systems or DOS partitions. To display whether a container is a multi-partition container, use the container list command, as in the following example.
Command Line Interface User’s Guide To display whether a container is a UNIX-opened container, use the container list command, as in the following example. In the example, the Usage column indicates Open, which means that the container was mounted or opened by UNIX.
Working with Container Attributes Executing: container list Cluster Num Dr Partner Label Type Total Oth Stripe Size Ctr Size Scsi Usage Partition C:ID:L Offset:Size -- ------- ----- ------ ------ --- ------ ------- ------ ------------0 0 Volume 30MB UnMap’d 2:01:0 64KB: 15MB 2:02:0 64KB: 15MB Tigris Displaying an Unconfigured Container The unconfigured container attribute indicates that a container cannot be configured by the RAID controller software or that a container is offline.
Command Line Interface User’s Guide -- ------- ----- ------ ------ --- ------ ------- ------ ------------0 0 Volume 30MB Valid Tigris 2:01:0 64KB: 15MB 2:02:0 64KB: 15MB Understanding State Attributes A container’s state attribute indicates the current use of a container.
Working with Container Attributes Displaying a Mirror Set Create State The mirror set create state attribute indicates the creation of a mirror set. To display whether a container is in the mirror set create state, use the container list command with the /full switch, as in the following example. In the example, the State column indicates Create, which means that a mirror set create operation is occurring on container 0.
Command Line Interface User’s Guide associated with these attributes, the CLI commands you use to perform these operations, and the section that describes the operation. Table 6-9.
Working with Container Attributes In the example, the State column indicates container 0 is being used as a Copy container in a container reconfiguration operation. (Note that the example eliminates some items in the container list display to make the example readable on this page.
Command Line Interface User’s Guide the example, the State column indicates Raid5, which means that container 0 is being used as a RAID-5 set in a container configuration operation. (Note that the example eliminates some items in the container list display to make the example readable on this page.
Working with Container Attributes To display whether a container is being used as a temporary container in a reconfiguration operation, use the container list command with the /full switch, as in the following example. In the example, the State column indicates Temp, which means that container 61 (a hidden container) is being used as a temporary container in a container configuration operation.
Command Line Interface User’s Guide CLI Operations Related Commands Display container list Displaying the Snapshot Original Container Currently Executing State snapshot backing Display container creation complete container list Displaying the Snapshot Backing Container Creation Complete State Attributes snapshot original container currently executing Discussed in... The following sections describe the snapshot state attributes.
Working with Container Attributes Displaying the Snapshot Backing Container State The snapshot backing container state attribute indicates that a container is the snapshot (backing) container in a currently executing create snapshot operation. To display whether a container is in the snapshot backing container state, use the container list command with the /full switch. Typically, the snapshot backing container state occurs so quickly that it does not appear in the container list command output.
Command Line Interface User’s Guide Num Dr Label Type Total Oth Stripe Size Ctr Size Scsi Usage C:ID:L State -- ----- ------ ------ --- ------ ------- ------ -----F: 0+62 Volume 100MB 1 NTMS 2:01:0 Snapped H: 0+63 Volume 100MB 1 NTMS 2:01:0 SnpShot Understanding RAID-5 Set State Attributes The RAID-5 set state attribute indicates the use of a RAID-5 set during a RAID-5 set creation operation.
Working with Container Attributes Understanding Container Cache Attributes Your RAID controller supports two global cache buffer pools that are available to containers: a volatile read cache and a nonvolatile write cache. Collectively, these global caches are referred to as the raw container cache. A container’s cache attributes indicate information about the cache associated with a specific container.
Command Line Interface User’s Guide Attributes write cache setting CLI Operations Set Release Display write cache status Display Related Commands Discussed in...
Working with Container Attributes Write Cache Status : Inactive, cache disabled Displaying a Container’s Global Container Write Cache Size The global container write cache size attribute indicates the number of blocks dedicated to the write cache for a specific container. To display a container’s global container write cache size, use the container show cache command, as in the following example. In the example, the Global Container Write Cache Size item indicates a size of 63332352 bytes.
Command Line Interface User’s Guide Write Cache Status : Inactive, cache disabled To set a container’s read cache, use the container create stripe command, the container create raid5 command, the container create volume command, or the container set cache command. See Chapter 7, Working With Single-level Containers, for information on the container create commands. See Chapter 9, Modifying Containers, for information on the container set command.
Working with Container Attributes Displaying a Container’s Write Cache Status The write cache status setting attribute indicates the current state of the write cache for the container and, where appropriate, the status of the controller’s battery. To display a container’s write cache status, use the container show cache command, as in the following example. In the example, the Write Cache Status item shows that the write cache status is Inactive, cache disabled.
7 Working With Single-level Containers This chapter explains how to use the CLI to work with and create single-level containers. A single-level container is made up of one or more partitions. The partitions can reside on one or more disks, and can be equal or unequal in size. Before you can work with containers, you must have previously opened the controller. See Opening and Closing a Controller in Chapter 3 for a description of how to open a controller.
Command Line Interface User’s Guide See the Flexible Array Storage Tool User’s Guide for a description of single-level container concepts.
Working With Single-level Containers Specifying Freespace When Creating a Volume Set A volume set’s size is created from freespace. To specify freespace when creating a volume set, use the container create volume command. There must be enough freespace available on your disk or disks to create a container of the desired size. See Understanding Freespace in Chapter 6, Working with Container Attributes, for information on freespace.
Command Line Interface User’s Guide ■ Enables the NVRAM write-back cache setting for the specified volume set if a battery is present and its status is Ok. If you do not use the /cache switch, you can enable the volume set’s raw container cache later with the container set cache command. See Chapter 9, Modifying Containers, for more information on how to enable a volume set’s raw container cache after creating it.
Working With Single-level Containers 2:02:0 Free 64.0KB:8.47GB 2:03:0 Free 64.0KB:8.47GB 2:04:0 Free 64.0KB:8.47GB To create a volume set, use the container create volume command, as in the following example. In the example, the volume set 0 is created on SCSI device (2,01,0) from 100MB (megabytes) of freespace. The container’s raw cache is enabled, and the label Venus is specified.
Command Line Interface User’s Guide Understanding Volume Set Creation in a UNIX Environment On UNIX systems, the message displayed after you execute the container create volume command includes the root special file associated with the newly created volume set. Use the container list command to display the root special file associated with volume set. See Displaying A Root Special File (UNIX Only) for more information on the root special file.
Working With Single-level Containers Understanding the Stripe Set Attributes You Can Specify You use the container create stripe command to create a stripe set. Before creating a stripe set, consider the following stripe set attributes you can specify: ■ freespace ■ stripe size ■ raw container cache ■ container label Specifying Freespace When Creating a Stripe Set A stripe set’s size is created from freespace. To specify freespace when creating a stripe set, use the container create stripe command.
Command Line Interface User’s Guide Stripe Set for further information on the container list command. In the following example, the container create stripe command with the /stripe switch creates a stripe set with a stripe size of 64 KB (kilobytes).
Working With Single-level Containers Specifying a Label for a Stripe Set The container label attribute identifies a name assigned to a container. Note that this label is not the label that displays in Windows Explorer and Disk Administrator. You can specify a container label while creating a stripe set or at a later time using the container set label command. See Displaying and Setting a Container Label in Chapter 6, Working with Container Attributes, for a description of the container set label command.
Command Line Interface User’s Guide HPN0> container create stripe /cache=TRUE /label=Mars ((2,01,0), 100M) Executing: container create stripe /cache=TRUE /label="Mars" ((CHANNEL=2,ID=1,LUN=0),104,857,600 ) Container 0 created After running the container create stripe command, use the container list command to display information about the stripe set, as in the following example. In the example, the Num Label column indicates the container ID 0 and the container label Mars.
Working With Single-level Containers Identifying Some Tasks to Perform After Creating a Stripe Set After you create a stripe set, you can: ■ Add a file system. See Chapter 9, Modifying Containers, for a description of how to add a file system. ■ Assign a drive letter. See Chapter 6, Working with Container Attributes, for a description of how to assign a drive letter.
Command Line Interface User’s Guide Specifying Mirror Disk Capacity The disk used to hold the mirror set must be the same size as the disk that is to be mirrored. To display the amount of space available on your disks, use the disk show space command. Additionally, the freespace on both disks must be equal. In the following example, the disk show space command indicates the amount of disk space available.
Working With Single-level Containers Specifying Synchronous or Asynchronous Mirror Set Creation When you create a mirror set you can optionally specify whether the command prompt returns after the mirror set is created (synchronous command execution) or if the command prompt returns immediately after executing the container create mirror command (asynchronous command execution). The mirror creation operation may require more than a minute to complete.
Command Line Interface User’s Guide After running the container create mirror command, use the container list command to display information about the mirror set, as in the following example. In the example, the Type column indicates that a Mirror set resides on container 0. The Scsi C: ID: L column displays the SCSI device IDs for the two halves of the mirror set.
Working With Single-level Containers ■ Assign a drive letter. See Chapter 6, Working with Container Attributes, for a description of how to assign a drive letter. ■ Split a mirror set. See Chapter 9, Modifying Containers, for a description of how to split a mirror set. ■ Unmirror a mirror set. See Chapter 9, Modifying Containers, for a description of how to unmirror a mirror set.
Command Line Interface User’s Guide ■ container label ■ parity (setting up by scrubbing) ■ synchronous or asynchronous RAID-5 set creation Specifying Freespace When Creating a RAID-5 Set A RAID-5 set’s size is created from freespace. To specify freespace when creating a RAID-5 set, use the container create raid5 command. There must be enough freespace available on your disk or disks to create a container of the desired size.
Working With Single-level Containers Executing: container create raid5 /stripe_size=65,536 ((CHANNEL=2,ID=1,LUN=0), 104,857,600) (CHANNEL=2,ID=2,LUN=0)(CHANNEL=2,ID=3,LUN=0) Container 0 created Enabling a RAID-5 Set’s Raw Container Cache The controller provides two global cache buffer pools available to containers: a volatile read-ahead cache and a non volatile NVRAM write-back cache. Collectively, these global caches are referred to as the raw container cache.
Command Line Interface User’s Guide Container Label in Chapter 6, Working with Container Attributes, for a description of the container set label command. In the following example, the container create raid5 command with the /label switch creates a RAID-5 set with the label Venus.
Working With Single-level Containers In the following example, the container create raid5 command with the /wait switch creates a RAID-5 set and returns the prompt after the RAID-5 set is created.
Command Line Interface User’s Guide RAID-5 set, as in the following example. In the example, the Type column indicates that a RAID-5 set resides on container 0. The Total Size column indicates that the RAID-5 set is 200M in size. The Stripe Size column indicates a stripe size of 64K. The Partition Size column indicates that container 0 occupies 100MB on SCSI devices 2:01:0, 2:02:0, and 2:03:0.
Working With Single-level Containers ■ Add a file system. See Chapter 9, Modifying Containers, for a description of how to add a file system. ■ Assign a drive letter. See Chapter 6, Working with Container Attributes, for a description of how to assign a drive letter.
8 Working with Multi-level Containers This chapter explains how to use the CLI to create multi-level containers. A multi-level container is a combination of one or more single-level containers. Multi-level containers made up of two container types combine the beneficial characteristics of the two types. Before you can work with containers, you must have previously opened the controller. See Opening and Closing a Controller in Chapter 3, for a description of how to open a controller.
Command Line Interface User’s Guide The RAID software supports three types of multi-level containers: ■ Multi-level stripe sets ■ Multi-level volume sets ■ Multi-level mirror sets The minimum size of a container is 10MB. Note: On a Windows 2000(basic disk only) system, a container is usable only if its size is greater than 16 MB; otherwise, the container type must be a dynamic disk. The RAID software also supports snapshots of multi-level containers.
Working with Multi-level Containers ■ Stripe set of mirror set creation in a NetWare environment ■ Stripe set of mirror set creation in a UNIX environment ■ Some tasks to perform after creating a stripe set of mirror sets The following sections discuss each of these topics. Understanding the Stripe Set of Mirror Sets Attributes You can Specify You use the container create mstripe command to create a stripe set of mirror sets.
Command Line Interface User’s Guide while creating a stripe set of mirror sets or at a later time using the container set label command. See Displaying and Setting a Container Label in Chapter 6, Working with Container Attributes, for a description of the container set label command. In the following example, the container create mstripe command with the /label switch creates a stripe set of mirror sets with the label Pluto.
Working with Multi-level Containers After running the container create mstripe command, use the container list command to display information about the stripe set of mirror sets, as in the following example. In the example, the Type column indicates a top-level Stripe set, whose container ID is 0, and two underlying Mirror sets, whose container IDs are 63 and 62. (Container’s 62 and 63 are hidden containers.) These three containers make up the stripe set of mirror sets.
Command Line Interface User’s Guide For information on how to display the NetWare console remotely on the NT client running FAST, see the Flexible Array Storage Tool User’s Guide. Understanding a Stripe Set of Mirror Set Creation in a UNIX Environment On UNIX systems, the message displayed after you execute the container create mstripe command includes the root special file associated with the newly created multi-level stripe set.
Working with Multi-level Containers Understanding the Stripe Set of Volume Set Attributes You can Specify You use the container create mstripe command to create a stripe set of volume sets. Before creating a stripe set of volume sets, consider the following stripe set of volume sets attributes you can specify: ■ stripe size ■ container label Specifying Stripe Size When Creating a Stripe Set of Volume Sets The stripe size attribute indicates the stripe size for a container.
Command Line Interface User’s Guide In the following example, the container create mstripe command with the /label switch creates a stripe set of volume sets with the label Neptune. HPN0> container create mstripe /label=Neptune 0 1 Executing: container create mstripe /label="Neptune" 0 1 Container 0 created Understanding How to Create a Stripe Set of Volume Sets This section provides an example that describes how to create a stripe set of volume sets.
Working with Multi-level Containers These three containers make up the stripe set of volume sets. The Total Size column indicates that the stripe set of volume sets is 200MB (megabytes), which is the total size of the two underlying volume sets. The Stripe Size column indicates that the size of each stripe is 32KB (kilobytes).
Command Line Interface User’s Guide Use the container list command to display the root special file associated with the stripe set of volume sets. See Displaying A Root Special File (UNIX Only) for more information on the root special file. Understanding Some Tasks to Perform After Creating a Stripe Set of Volume Sets ■ Add a file system. See Chapter 9, Modifying Containers, for a description of how to add a file system. ■ Assign a drive letter.
Working with Multi-level Containers data stream switches to the next partition in the stripe. The stripe size can be 8 KB, 16 KB, 32 KB, or 64 KB. You need to determine the stripe size that is most suitable for your environment. Note that you can use the container reconfigure command at a later time to change the stripe size. See the container reconfigure command in Chapter 9, Modifying Containers, for a description of the container reconfigure command.
Command Line Interface User’s Guide sets have been created. See Working with a Stripe Set on page 7-5 in Chapter 7, Working With Single-level Containers, for information on creating a stripe set. Use the container list command to display information about your containers, as in the following example. In the example, the Type column indicates two Stripe sets identified by container IDs 0 and 1.
Working with Multi-level Containers 0 0 0 63 Stripe 400MB 32KB None Stripe 200MB 32KB 2:01:0 64.0KB: 100MB 2:02:0 64.0KB: 100MB 0 62 Stripe 200MB 32KB 2:03:0 64.0KB: 100MB 2:04:0 64.0KB: 100MB Understanding a Stripe Set of Stripe Sets in a NetWare Environment When creating a multilevel container of stripe sets on a NetWare server, you specify the container IDs for the containers from which you want to create the multilevel stripe set.
Command Line Interface User’s Guide ■ Assign a drive letter. See Chapter 6, Working with Container Attributes, for a description of how to assign a drive letter. Working with a Stripe Set of RAID-5 Sets (RAID-50) A stripe set of RAID-5 sets (also known as RAID-50) is a multi-level container made up of a top-level stripe set and two or more underlying RAID-5 sets of equal size. A stripe set of RAID-5 set’s data is redundant.
Working with Multi-level Containers display the stripe size of a stripe set of RAID-5 sets using the container list command. See Understanding How to Create a Stripe Set of RAID-5 Sets for information on the container list command. In the following example, the container create mstripe command with the /stripe switch creates a stripe set of RAID-5 sets with a stripe size of 64 KB (kilobytes).
Command Line Interface User’s Guide Num Dr Label Type Total Oth Stripe Size Ctr Size Scsi Usage Partition C:ID:L Offset:Size -- ----- ------ ------ --- ------ ------- ------ ------------0 RAID-5 100MB NTFS 2:01:0 64.0KB: 50.0MB 2:02:0 64.0KB: 50.0MB 2:03:0 64.0KB: 50.0MB 1 RAID-5 100MB NTFS 2:01:0 50.0KB: 50.0MB 2:02:0 50.0KB: 50.0MB 2:03:0 50.0KB: 50.0MB To create a stripe set of RAID-5 sets, use the container create mstripe command, as in the following example.
Working with Multi-level Containers 2:03:0 64.0KB: 50.0MB 62 RAID-5 100MB 2:01:0 50.0KB: 50.0MB 2:02:0 50.0KB: 50.0MB 2:03:0 50.0KB: 50.0MB Understanding a Stripe Set of RAID-5 Set Creation in a NetWare Environment When creating a multilevel container of stripe sets on a NetWare server, you specify the container IDs for the containers from which you want to create the multilevel stripe set. If NetWare is using any of these containers, an appropriate message displays.
Command Line Interface User’s Guide ■ Assign a drive letter. See Chapter 6, Working with Container Attributes, for a description of how to assign a drive letter. Creating Multi-level Volume Sets A multi-level volume set is a container whose top level container is a volume set.
Working with Multi-level Containers Specifying a Label for a Volume Set of Stripe Sets The container label attribute indicates a name assigned to a container. Note that this label is not the label that displays in Windows Explorer and Disk Administrator. You can specify a label while creating a volume set of stripe sets or at a later time using the container set label command at a later time to specify a label.
Command Line Interface User’s Guide HPN0> container create mvolume 0 1 Executing: container create mvolume 0 1 Container 0 created After running the container create mvolume command, use the container list command to display information about the volume set of stripe sets, as in the following example. In the example, the Type column indicates a top-level Volume set, whose container ID is 0, and two underlying Stripe sets, whose container IDs are 63 and 62. (Containers 63 and 62 are hidden containers.
Working with Multi-level Containers For information on how to display the NetWare console remotely on the NT client running FAST, see the Flexible Array Storage Tool User’s Guide. Understanding a Volume Set of Stripe Set Creation in a UNIX Environment On UNIX systems, the message displayed after you execute the container create mvolume command includes the root special file associated with the newly created multi-level volume set.
Command Line Interface User’s Guide ■ Volume set of mirror set creation in a UNIX environment ■ Some tasks to perform after creating a volume set of mirror sets The following sections discuss each of these topics. Understanding the Volume Set of Mirror Sets Attribute You can Specify You use the container create mvolume command to create a volume set of mirror sets.
Working with Multi-level Containers containers, as in the following example. In the example, the Type column indicates two Mirror sets reside on containers 0 and 1. HPN0> container list Executing: container list Cluster Num Dr Partner Label Type Total Oth Stripe Size Ctr Size Scsi Usage Partition C:ID:L Offset:Size -- ------- ----- ------ ------ --- ------ ------- ------ ------------0 0 Mirror 100MB None 2:01:0 64.0KB: 100MB 2:02:0 64.0KB: 100MB 0 1 Mirror 100MB None 2:03:0 64.
Command Line Interface User’s Guide Understanding a Volume Set of Mirror Sets in a NetWare Environment When creating a multilevel container of volume sets on a NetWare server, you specify the container IDs for the containers from which you want to create the multilevel volume set. If NetWare is using any of these containers, an appropriate message displays. This message indicates that one or more of the containers you specified is in use by NetWare.
Working with Multi-level Containers Creating a Volume Set of RAID-5 Sets A volume set of RAID-5 sets is a multi-level container made up of a top-level volume set and one or more underlying RAID-5 sets. A volume set of RAID-5 set’s data is redundant. Each RAID-5 set is made up of three or more equal-sized partitions on three or more separate disks. See the Flexible Array Storage Tool User’s Guide for a description of volume set of RAID-5 sets and other container concepts.
Command Line Interface User’s Guide In the following example, the container create mvolume command with the /label switch creates a volume set of RAID-5 sets with the label Mercury. HPN0> container create mvolume /label=Mercury 0 1 Executing: container create mvolume /label="Mars" 0 1 Container 0 created Understanding How to Create a Volume Set of RAID-5 Sets This section provides an example that describes how to create a volume set of RAID-5 sets.
Working with Multi-level Containers volume set of RAID-5 sets, as in the following example. In the example, the Type column indicates a top-level Volume set, whose container ID is 0, and two underlying RAID-5 sets, whose container IDs are 63 and 62. (Containers 63 and 62 are hidden containers.) These three containers make up the volume set of RAID-5 sets. The Total Size column indicates that the volume set of RAID-5 sets is 400MB (megabytes), which is the total size of the two underlying RAID-5 sets.
Command Line Interface User’s Guide Understanding a Volume Set of RAID-5 Set Creation in a UNIX Environment On UNIX systems, the message displayed after you execute the container create mvolume command includes the root special file associated with the newly created multi-level volume set. Use the container list command to display the root special file associated with the volume set of RAID-5 sets. See Displaying A Root Special File (UNIX Only) for more information on the root special file.
Working with Multi-level Containers Understanding the Volume Set of Volume Sets Attribute You can Specify You use the container create mvolume command to create a volume set of volume sets. Before creating a volume set of volume sets, consider the following volume set of volume sets attribute you can specify: ■ container label Specifying a Label for a Volume Set of Volume Sets The container label attribute indicates a name assigned to a container.
Command Line Interface User’s Guide -- ------- ----- ------ ------ --- ------ ------- ------ ------------0 0 Volume 100MB None 2:01:0 64.0KB: 100MB 0 1 Volume 200MB None 2:02:0 64.0KB: 200MB To create a volume set of volume sets, use the container create mvolume command, as in the following example. In the example, containers 0 and 1 are used to create a volume set of volume sets.
Working with Multi-level Containers After you create a multilevel volume set on a NetWare server, you must run the list devices command on the NetWare console and then create the necessary NetWare disk partitions and volumes. For information on how to create partitions and volumes, see the appropriate NetWare documentation. For information on how to display the NetWare console remotely on the NT client running FAST, see the Flexible Array Storage Tool User’s Guide.
Command Line Interface User’s Guide command after promoting a volume set that was built from multiple partitions with the container promote command. The container create mmirror command is fully dynamic. If you use this command, users will not see any change or experience any interruption in service. However, performance may be reduced.
Working with Multi-level Containers Specifying Synchronous or Asynchronous Command Execution for a Volume Set of Mirror Sets When you create a volume set of mirror sets, you can optionally specify whether the command prompt returns after the volume set of mirror sets is created (synchronous command execution) or if the command prompt returns immediately after executing the container create mmirror command (asynchronous command execution).
Command Line Interface User’s Guide container 0 (a volume set of volume sets created with the container promote command) is used to create the volume set of mirror sets. The freespace from SCSI devices (2,3,0) and (2,4,0) are used to mirror the underlying volume sets.
Working with Multi-level Containers NetWare console and then create the necessary NetWare disk partitions and volumes. For information on how to create partitions and volumes, see the appropriate NetWare documentation. For information on how to display the NetWare console remotely on the NT client running FAST, see the Flexible Array Storage Tool User’s Guide.
9 Modifying Containers This chapter explains how to use the CLI commands to manipulate and modify containers. Before you can work with containers, you must have previously opened the controller. See Opening and Closing a Controller in Chapter 3, for a description of how to open a controller. In addition, you must have initialized your disk or disks to prepare them for container operations. See Working with Disks in Chapter 4 for a description of how to initialize a disk.
Command Line Interface User’s Guide For information about… Turn to… Extending a Container page 9-40 Taking a Container Offline page 9-44 Deleting a Container page 9-45 Working with Container Reconfiguration The CLI allows you to reconfigure an existing container. See the Flexible Array Storage Tool User’s Guide for a complete discussion of container types and container concepts.
Modifying Containers Reconfiguring a Container’s Type The container type attribute indicates the type of container to which the existing container is to be changed. You can change an existing container into one of the following container types: ■ Mirror set ■ Raid-5 set ■ Raid-10 set ■ Stripe set ■ Volume set In the following example, the container reconfigure command with the /stripe switch reconfigures an existing container to a stripe set.
Command Line Interface User’s Guide ■ Stripe set of mirror sets ■ Stripe set of volume sets ■ Stripe set of stripe sets ■ Stripe set of RAID-5 sets ■ Snapshot container In the following example, the container reconfigure command with the /stripe_size switch changes the existing stripe size of container 1 to 16 KB (kilobytes).
Modifying Containers Specifying Synchronous or Asynchronous Command Execution The wait attribute indicates whether the command prompt returns after a container is reconfigured (synchronous command execution) or if the command prompt returns immediately after executing the container reconfigure command (asynchronous command execution).
Command Line Interface User’s Guide To change a volume set to a stripe set, use the container reconfigure command with the /stripe switch, as in the following example. In the example, the /stripe switch causes the existing volume set on container 0 to be changed to a stripe set. A stripe size is not specified, so the default stripe size of 32K (kilobytes) is used.
Modifying Containers Typically, you use the container promote command as part of a process to provide fault tolerance for existing volume sets. To work with container promotion, you must understand: ■ The container promotion attributes you can specify ■ How to promote a container ■ Container promotion in a UNIX environment The following sections discuss each of these topics. Understanding the Container Promotion Attributes You can Specify You use the container promote command to promote a container.
Command Line Interface User’s Guide container ID is 0, and an underlying Volume set, whose container ID is 63. (Container 63 is a hidden container.) These two containers make up a stripe set of volume sets. HPN0> container list Executing: container list Cluster Num Dr Partner Label Type Total Oth Stripe Size Ctr Size Scsi Usage Partition C:ID:L Offset:Size -- ------- ----- ------ ------ --- ------ ------- ------ ------------0 0 0 63 Stripe 100MB Volume 100MB 32KB None 2:01:0 64.
Modifying Containers Understanding How to Add a Level to a Container This section provides an example that describes how to add a level to a container. Before adding a level to a container, use the container list command to display information about your containers, as in the following example. In the example, the Type column indicates that container 0 is a RAID-5 set.
Command Line Interface User’s Guide Understanding How to Add a Level to a Container in a UNIX Environment The container add level feature is not available in a UNIX environment. Working with Mirror Sets The CLI allows you to perform the following modifications on a mirror set: ■ Split a mirror set ■ Unmirror a mirror set ■ Scrub a mirror set See the Flexible Array Storage Tool User’s Guide for a complete description of mirror sets and other container concepts.
Modifying Containers ■ Assign a drive letter to the split container using the container assign drive_letter command. See Chapter 6, Working with Container Attributes, for a description of how to assign a drive letter. ■ Run the Windows NT or Windows 2000 CHKDSK command with the /F switch. See your Windows NT or Windows 2000 documentation for information on how to use the CHKDSK command.
Command Line Interface User’s Guide Executing: container split 0 Container 1 created After running the container split command to split a mirror set, use the container list command to display information about the containers, as in the following example. In the example, the Type column indicates two volume sets with container labels 0 and 1 that reside on SCSI devices 2:01:0 and 2:02:0.
Modifying Containers The following sections discuss each of these topics. Understanding the Container Unmirroring Attributes You can Specify You use the container unmirror command to unmirror a mirror set. The container unmirror command has no attributes. Understanding How to Unmirror a Container This section provides an example that describes how to unmirror a mirror set.
Command Line Interface User’s Guide Scrubbing a Mirror Set The CLI allows you to scrub a mirror set. Scrubbing a mirror set reconstructs the data on both mirror halves (partitions), if they are found to be different. You use the container scrub command to scrub a mirror set. To work with mirror set scrubbing, you must understand: ■ The mirror set scrubbing attributes that you can specify ■ How to scrub a mirror set The following sections discuss each of these topics.
Modifying Containers Executing: container scrub /no_repair=FALSE 2 Specifying Synchronous or Asynchronous Command Execution The wait attribute indicates whether the command prompt returns after a container is scrubbed (synchronous command execution) or if the command prompt returns immediately after executing the container scrub command (asynchronous command execution).
Command Line Interface User’s Guide that the container consists of partitions on SCSI devices 2:01:0 and 2:02:0. HPN0> container list Executing: container list Cluster Num Dr Partner Label Type Total Oth Stripe Size Ctr Size Scsi Usage Partition C:ID:L Offset:Size -- ------- ----- ------ ------ --- ------ ------- ------ ------------0 0 Mirror 100MB None 2:01:0 64.0KB: 100MB 2:02:0 64.
Modifying Containers Understanding the RAID-5 Set Restore Attributes You can Specify You use the container restore raid5 command to restore a RAID-5 set. The container restore raid5 command has no attributes. Understanding How to Restore a RAID-5 Set This section provides an example that describes how to restore a RAID-5 set. Before restoring a RAID-5 set, use the container list command to display information about your containers, as in the following example.
Command Line Interface User’s Guide 2:02:0 64.0KB: 100MB 2:03:0 64.0KB: 100MB Scrubbing a RAID-5 Set The CLI allows you to scrub a RAID-5 set. Scrubbing a RAID-5 set recalculates and replaces, if necessary, the parity information. You use the container scrub command to scrub a RAID-5 set. To work with scrubbing a RAID-5 set, you must understand: ■ The RAID-5 set scrub attributes that you can specify ■ How to scrub a RAID-5 set The following sections discuss each of these topics.
Modifying Containers HPN0> container scrub /no_repair=FALSE 2 Executing: container scrub /no_repair=FALSE 2 Specifying Synchronous or Asynchronous Command Execution The wait attribute indicates whether the command prompt returns after a container is scrubbed (synchronous command execution) or if the command prompt returns immediately after executing the container scrub command (asynchronous command execution).
Command Line Interface User’s Guide HPN0> container list Executing: container list Cluster Num Dr Partner Label Type Total Oth Stripe Size Ctr Size Scsi Usage Partition C:ID:L Offset:Size -- ------- ----- ------ ------ --- ------ ------- ------ ------------0 0 RAID-5 200MB 32KB None 2:01:0 64.0KB: 100MB 2:02:0 64.0KB: 100MB 2:03:0 64.
Modifying Containers To work with enabling a container’s volatile read-ahead cache, you must understand: ■ The container set cache attributes you can specify ■ How to enable a container’s volatile read-ahead cache The following sections discuss each of these topics. Understanding the Read-ahead Cache Attributes You can Specify You use the container set cache command to enable a container’s volatile read-ahead cache.
Command Line Interface User’s Guide To enable a container’s volatile read-ahead cache, use the container set cache command with the /read_cache_enable switch, as in the following example. In the example, the /read_cache_enable=TRUE switch enables the volatile read-ahead cache on container 0.
Modifying Containers Understanding the NVRAM Write-back Cache Attributes You can Specify You use the container set cache command to enable a container’s NVRAM write-back cache.
Command Line Interface User’s Guide following table summarizes the values for the /unprotected and /write_cache_enable switches: /write_cache_enable Switch Setting /unprotected Switch Setting FALSE FALSE The NVRAM write-back cache setting for the specified container is disabled. FALSE TRUE Not allowed. An appropriate error message displays. TRUE FALSE The NVRAM write-back cache setting for the specified container is enabled when protected.
Modifying Containers column indicates None, which means no file system resides on container 0. HPN0> container list Executing: container list Cluster Num Dr Partner Label Type Total Oth Stripe Size Ctr Size Scsi Usage Partition C:ID:L Offset:Size -- ------- ----- ------ ------ --- ------ ------- ------ ------------0 0 Volume 100MB None 2:01:0 64.
Command Line Interface User’s Guide When a disk fails or you remove a disk, the cache buffers associated with a container remain locked on the controller. This allows the disk to come back online or allows the disk to be replaced. In this case the containers regain the previously locked buffers. You may, however, wish to release the cache buffers to the global buffer pool. To release cache buffers associated with a container to the global buffer pool, use the container release_cache command.
Modifying Containers container show cache command to display information about the cache buffers associated with a container. Understanding Releasing the Cache Buffers Associated with a Container in a UNIX Environment The container release cache feature is not available in a UNIX environment. Working with Container Rebuild A spare disk is a disk that is configured to automatically receive data from a failed partition or disk in a redundant container configuration.
Command Line Interface User’s Guide ■ How to assign spare disks to a single container The following sections discuss each of these topics. Understanding the Assign Spare Disk Attributes You can Specify You use the container set spare command to assign spare disks to a container. The container set spare command has no attributes. Understanding How to Assign Spare Disks to a Single Container This section provides an example that describes how to assign spare disks to a single container.
Modifying Containers 0 2:03:0 Removing Spare Disks from a Single Container The CLI allows you to remove one or more spare disks assigned to a single container. To remove one or more spare disks assigned to a single container, use the container remove spare command. To work with removing spare disks from a single container, you must understand: ■ The remove spare disk attributes you can specify ■ How to remove spare disks from a single container The following sections discuss each of these topics.
Command Line Interface User’s Guide Executing container remove spare 0 (CHANNEL=2,ID=3,LUN=0) After running the container remove spare command to remove one or more spare disks from a single container, use the container show spare command to display information about your spare disks, as in the following example. In the example, the Scsi C:ID:L column indicates No Devices Assigned, which means that no spare disk is assigned to container 0.
Modifying Containers the example, the Type column indicates a Mirror set on container 0 and container 1. HPN0> container list Executing: container list Cluster Num Dr Partner Label Type Total Oth Stripe Size Ctr Size Scsi Usage Partition C:ID:L Offset:Size -- ------- ----- ------ ------ --- ------ ------- ------ ------------0 0 Mirror 100MB None 2:00:0 64.0KB: 100MB 2:01:0 64.0KB: 100MB 0 1 Mirror 100MB None 2:00:0 64.0KB: 100MB 2:01:0 64.
Command Line Interface User’s Guide To work with removing one or more spare disks from all containers managed by a controller, you must understand: ■ The remove global spare disk attributes you can specify ■ How to remove global spare disks The following sections discuss each of these topics. Understanding the Remove Global Spare Disk Attributes You can Specify You use the container remove global_spare command to remove spare disks from one or more containers managed by a controller.
Modifying Containers After running the container remove global_spare command to remove one or more spare disks from all containers managed by a controller, use the container show spare command to display information about your spare disks, as in the following example. In the example, SCSI devices (2,2,0) (2,3,0) no longer appear as global spare disks in the container show spare command output.
Command Line Interface User’s Guide ■ Adding a file system to a container in a UNIX environment The following sections discuss each of these topics. Understanding the File System Attributes You can Specify You use the container format command to add a file system to a container.
Modifying Containers Specifying File System Compression The file system compression attribute indicates whether to compress the NTFS file system that resides on a container. Compression is not supported on an NTFS file system with an allocation size greater than 4 KB. Compression is not supported on a FAT or FAT32 file system because allocation size begins at 8 KB.
Command Line Interface User’s Guide In the following example, the container format command with the /quick switch performs a quick format on the container on drive F.
Modifying Containers After running the container format command to add a file system, use the container list command to display information about the file system, as in the following example. In the example, the Usage column indicates that the NTFS file system resides on container 0.
Command Line Interface User’s Guide Understanding the Extend File System Attributes You can Specify You use the container extend file_system command to extend an NTFS file system on a container. The container extend file_system command has no attributes. Understanding How to Extend a File System on a Container This section provides an example that describes how to extend a file system on a container.
Modifying Containers F: 0 0 Volume 100MB NTFS 2:01:0 64.0KB: 100MB Understanding Extending a File System on a Container in a Unix Environment Using the CLI to extend a file system on a container is not supported in a UNIX Environment. Removing a File System The CLI allows you to remove a file system from a container. You use the container remove file_system command to remove a file system from a container.
Command Line Interface User’s Guide To remove a file system from a container, use the container remove file_system command, as in the following example. In the example, the resident file system (NTFS) is removed from container 0. HPN0> container remove file_system 0 Executing: container remove file_system 0 After running the container remove file_system command to remove a file system from a container, use the container list command to display information about the container, as in the following example.
Modifying Containers To work with extending a volume set, you must understand: ■ The extend volume set attributes you can specify ■ How to extend a volume set ■ Extending a volume set in a UNIX environment Understanding the Extend Volume Set Attributes You can Specify You use the container extend volume command to extend a volume set.
Command Line Interface User’s Guide 0 0 Volume 100MB None 2:01:0 64.0KB: 100MB You may also want to use the disk show space command to display space usage information on the SCSI devices from which you plan to add freespace. To extend the volume set on container 0, use the container extend volume command, as in the following example. In the example, SCSI devices (2,2,0) and (2,3,0), each with 100MB of space, are added to container 0.
Modifying Containers To work with extending a multi-level container of volume sets, you must understand: ■ The extend multi-level container of volume set attributes you can specify ■ How to extend a multi-level container of volume sets Understanding the Extend Multi-level Container of Volume Set Attributes You can Specify You use the container extend mvolume command to extend a multi-level container of volume sets. The container extend mvolume set command has no attributes.
Command Line Interface User’s Guide Container 0 extended. After running the container extend mvolume command, use the container list command to display information about the container, as in the following example. In the example, the Type column indicates that container 0 is a multi-level container of volume sets made up of underlying containers 63, 62, 61, and 60.
Modifying Containers indicates container 0, and the Usage column indicates None (there is no resident file system on the container). HPN0> container list Executing: container list Cluster Num Dr Partner Label Type Total Oth Stripe Size Ctr Size Scsi Usage Partition C:ID:L Offset:Size -- ------- ----- ------ ------ --- ------ ------- ------ ------------0 0 Volume 100MB None 2:01:0 64.0KB: 100MB To take the container offline, use the container offline command, as in the following example.
Command Line Interface User’s Guide Understanding the Container Delete Attributes You Can Specify You use the container delete command to delete a container. Before deleting a container, consider the following attributes you can specify: ■ Always delete container ■ Unconditionally delete container Specifying Always Delete a Container The always attribute indicates whether to delete a container, even if it has a file system.
Modifying Containers Before deleting a container, use the container list command to display information about your containers, as in the following example. In the example, the Num Label column indicates container 0, which is a Volume set. HPN0> container list Executing: container list Cluster Num Dr Partner Label Type Total Oth Stripe Size Ctr Size Scsi Usage Partition C:ID:L Offset:Size -- ------- ----- ------ ------ --- ------ ------- ------ ------------0 0 Volume 100MB None 2:01:0 64.
Command Line Interface User’s Guide configuration, you must first upgrade to NetWare 5.1 Service Pack 1 (or higher), then unload and reload NSS (which forces NSS to reload its configuration information).
10 Working with Snapshot Containers This chapter explains how to use the CLI to create, update, and remove snapshot containers. You can perform snapshot operations only if the snapshot feature is available on your controller. The snapshot feature allows you to create an instantaneous copy of a container at a precise point in time. The snapshot container is immediately available for backup, archiving, or use by application programs.
Command Line Interface User’s Guide Creating a Snapshot Container You can create a snapshot of any type container, except a mirror set. When you make a snapshot of a RAID-5 set, the fault tolerance of the data is preserved. While creating a snapshot container, user and application access to the original container is not interrupted, although the create snapshot operation slightly degrades performance during initial writes to the original container.
Working with Snapshot Containers using a read-only application (for example, a backup utility) with the snapshot. The container create snapshot command provides a /compact switch that allows you to specify a compact snapshot container. In the following example, the container create snapshot command with the /compact switch uses container 0 to create a compact snapshot container, container 1.
Command Line Interface User’s Guide In the following example, the container create snapshot command with the /stripe_size switch uses container 0 to create a snapshot container on container 1 with a stripe size of 64KB. HPN0> container create snapshot /stripe_size=64K 0 1 Executing container create snapshot /stripe_size=65,536 01 Specifying Safe Mode When Creating a Snapshot Container The safe mode attribute indicates that i/o is paused during the creation of a snapshot container.
Working with Snapshot Containers 0 1 Stripe 200MB 32KB None 2:02:0 64.0KB: 100MB 2:03:0 64.0KB: 100MB To create a snapshot container, use the container create snapshot command, as in the following example. In the example, a snapshot container is created from container 0 (a volume set) and stored on container 1 (a stripe set). Note that the /compact switch stores the snapshot container on a compact container, which is smaller than a non-compact container.
Command Line Interface User’s Guide ■ The RO column indicates a blank space for the snapped container, 0+62, and the snapshot container, 1+63, which means that container 0+62 and container 1+63 are read/write accessible. ■ The Oth Ctr column indicates 1 and 0, which are two container IDs that identify the relationship between the two containers (0+62 and 1+63) as a result of the create snapshot operation.
Working with Snapshot Containers Updating a Snapshot Container Updating a snapshot container updates archive information on the snapshot container that is linked to the original container. When an update snapshot container operation is performed, only files that have not changed on the original container since the snapshot was taken are effected. This feature only applies to NTFS and FAT file systems.
Command Line Interface User’s Guide Understanding How to Update a Container Snapshot This section provides an example that describe how to update the archive information between a snapshot container and an original container. Before updating the archive information between a snapshot container and an original container, use the container list command to display information about your containers, as in the following example.
Working with Snapshot Containers Removing a Snapshot Container Removing a snapshot container removes the link between the original container and the snapshot container. When the link is removed the snapshot container reverts to ordinary container space.
Command Line Interface User’s Guide information about your containers, as in the following example. In the example, the State column indicates Snapped for container 0+62, which means that container 0 is the original container on which the snapshot was taken. The State column also indicates SnpShot for container 1+63, which means that container 1 is the snapshot (backing) container.
Working with Snapshot Containers 2:03:0 Clearing NVRAM of Unconfigured Snapshot Containers The CLI allows you to clear NVRAM that is being used for unconfigured snapshot containers. A snapshot container becomes unconfigured when a disk on which a snapshot container resides is removed from a RAID system.
Command Line Interface User’s Guide HPN0> controller show unconfigured_snapshot Executing: controller show unconfigured_snapshots NVRAM is being used for unconfigured snapshots To clear NVRAM that is being used for unconfigured snapshot containers, use the controller free_snapshot command, as in the following example. In the example the controller free_snapshot command clears NVRAM of unconfigured snapshot containers.
11 Working with Diagnostic Commands This chapter explains how to use the CLI to perform diagnostic operations on a controller. Diagnostic information provides technical support personnel with information that may be needed to troubleshoot controller problems. The commands described in this chapter are intended to be used with the assistance of technical support personnel.
Command Line Interface User’s Guide Understanding Diagnostic Attributes Diagnostic attributes are the characteristics of a controller that can be administered for the purpose of isolating potential controller problems. Table 11-1 lists the diagnostic attributes and their related CLI commands. Table 11-1. Diagnostic Attributes Attribute interrupt count CLI Operations set show interrupt response time set show boot parameter clear set show Related Commands Discussed in ...
Working with Diagnostic Commands to 32 and the delay time is set to 10, the controller batches I/O request responses for one millisecond only if there are more than 32 I/O requests outstanding in the one millisecond interval. See Displaying the Interrupt Response Time on page 11-3 for information on displaying the interrupt response time. See Setting the Interrupt Count on page 11-7 for information on how to set the default interrupt count and the delay time.
Command Line Interface User’s Guide Displaying a Boot-time Parameter The boot parameter attribute indicates a specific boot-time parameter for which a technical support person might need information. You only need to display a boot-time parameter if a technical support person requests this information. See Setting a Boot Parameter on page 11-7 for information on how to set boot-time parameters. See Clearing Boot Parameters on page 11-6 for information on how to clear boot-time parameters.
Working with Diagnostic Commands . Partitions:6 . . . Battery Information ------------------. . . *** HISTORY BUFFER FROM LAST RUN *** . . . *** HISTORY BUFFER FROM CURRENT CONTROLLER RUN *** . . . ============== Dump Complete. Displaying Internal History Log A controller’s internal log keeps a history of operations occurring on the controller. The controller keeps a history log since the most recent boot of the operating system, and for the previous boot of the operating system.
Command Line Interface User’s Guide Executing: diagnostic show history /current=TRUE *** HISTORY BUFFER FROM CURRENT CONTROLLER RUN *** . . . ============== Dump Complete. Dumping Data Structures A diagnostic structures dump saves container data structures to a file for use by technical support personnel for troubleshooting. To dump diagnostic structures, use the diagnostic dump structures command, as in the following example.
Working with Diagnostic Commands Setting a Boot Parameter You use the diagnostic set boot_parameter command to set a controller boot-time parameter to a specific value. Under normal conditions, boot-time parameters are not set. You usually set a boottime parameter at the request of a technical support person. Before setting a boot-time parameter, use the diagnostic show boot_parameter command to display information about the desired parameter.
Command Line Interface User’s Guide HPN0> diagnostic moderation set count 100 Executing: diagnostic moderation set Count 100 After running the diagnostic moderation show count command to set the interrupt count, use the diagnostic moderation show count command to display the interrupt count, as in the following example. In the example, the The moderation count is currently set to line indicates that the interrupt count is set to 100 I/O requests.
Working with Diagnostic Commands time is set to 20 milliseconds (that is, 20 milliseconds = 200 x 100 microseconds). HPN0> diagnostic moderation show timer Executing: diagnostic moderation show Timer The moderation timer is currently set to 200. Loading Containers When in maintenance mode, you use the diagnostic load_containers command to load containers and partition tables from the disks into the controller’s memory.
12 Working with Event Notification This chapter explains how to use the CLI to enable, display, test, and disable controller event notification messages. The CLI’s event notification feature sends a designated recipient e-mail messages that describe selected events that occur on a HP NetRAID-4M controller. A designated computer functions as an e-mail server. The computer that functions as the e-mail server must support the Simple Mail Transport Protocol (SMTP).
Command Line Interface User’s Guide Enabling E-Mail Notification Before using the CLI to manage controller e-mail notifications, use the following procedure to ensure that the e-mail notification option in the FAST Management Interface Control dialog box is enabled. 1 Open the FAST control panel applet. The FAST Management Interfaces dialog box appears. 2 Select the E-Mail Notification item in the Management Interfaces section of the FAST Management Interfaces dialog box.
Working with Event Notification CLI Operations Related Commands Discussed in... mail subject line Attribute Display Set mail show message mail set message Displaying the Mail Subject Line mail body line Display mail show message Displaying the Mail Body Line Displaying the Mail Server The mail server name attribute identifies the name of the computer that processes e-mail notification messages for controller events. The e-mail server can be on the local computer or on a remote computer.
Command Line Interface User’s Guide Executing: mail show message Message : AdapterFailure To: : jsmith@companyX.com Subject : sul9999b Body : The controller "%adapter%" sent the following text message.%nl%%text%%nl%Computer : %host%%nl%TIME : %time%%nl%DATE : %date%%nl%%nl% Displaying the Mail To Line The mail to line attribute identifies the recipient of an e-mail notification message.
Working with Event Notification To : jsmith@companyX.com Subject : HP NetRAID-4M controller message Body : The controller "%adapter%" sent the following text message.%nl%%text%%nl%Computer : %host%%nl%TIME : %time%%nl%DATE : %date%%nl%%nl% Displaying the Mail Body Line The mail body line attribute indicates the controller name, time, and date associated with a controller event that sent an e-mail notification message. The CLI software determines the content of a body line according to the event type.
Command Line Interface User’s Guide How to Set the Mail Server This section provides an example that describes how to set the email server that sends e-mail notification messages about controller events. To display the name of the computer on which the current e-mail server is set, use the mail show server command as in the following example. In the example, the Mail Server item indicates that Hercules is the name of the computer on which the e-mail server is set.
Working with Event Notification How to Set Mail Message Reporting This section provides an example that describes how to set e-mail notification message reporting for controller events. To display e-mail message information for all mail message types (and corresponding event types), use the mail show message command with the /all switch, as in the following example.
Command Line Interface User’s Guide message reporting is set for the DriveLetterChange event type and the FileSystemChange event type. HPN0> mail show message /all=TRUE Executing: mail show message /all=TRUE Message : DriverLetterChange To : jsmith@companyX.com Subject : HP NetRAID-4M controller message Body : A drive letter assignment change occurred on container (%container%).
Working with Event Notification To send a test e-mail notification message, use the mail test command, as in the following example. In the example, the mail test command sends an e-mail notification message using the local computer and domain to jsmith@companyX.com. Note that the Subject item and the message This is a test mail message are supplied by the system. HPN0> mail test "jsmith@companyX.com" Executing: mail test "jsmith@companyX.
Command Line Interface User’s Guide Body : A drive letter assignment change occurred on container (%container%).%nl%Controller : "%adapter%"%nl%Computer : %host%%nl%TIME : %time%%nl%DATE : %date%%nl%%nl% To clear e-mail message reporting for all controller event types, use the mail clear message with the /all switch, as in the following example. In the example, the mail clear message command with the /all switch clears all message reporting on the local computer in the local domain.
13 Working with Tasks This chapter explains how to use the CLI to display and manage tasks running on a controller. A task is an operation that runs on a controller. Several CLI commands start a task running on a controller. Once a task is running, the CLI allows you to display, stop, suspend, and resume the task. The following table provides a quick reference to the topics covered in this chapter. For information about... Turn to...
Command Line Interface User’s Guide Table 13-1.
Working with Tasks TaskId Function Done% Container State Specific1 Specific2 ------ -------- ------- --------- ----- --------- --------103 Create 63.5% 00 RUN 00000000 00000000 Displaying the Task Function The task function attribute indicates the type of task running on the controller. See the Command Line Interface Reference Guide for a description of task types. To display the task function of a task running a controller, use the task list command, as in the following example.
Command Line Interface User’s Guide Displaying the Container ID The container ID attribute indicates the identification numbers of the containers associated with a running task. To display the container IDs associated with a task, use the task list command, as in the following example. In the example, the Container column indicates 00, which means that container 00 is associated with task 103.
Working with Tasks is running, and the Specific1 column indicates 00000000, which means that no errors were found. HPN0> task list Executing: task list Controller Tasks TaskId Function Done% Container State Specific1 Specific2 ------ -------- ------- --------- ----- --------- --------104 Verify 63.
Command Line Interface User’s Guide ■ Windows NT and Windows 2000 (basic disk only): the status line appears in the MS DOS prompt title bar ■ NetWare: the status line appears in a separate window ■ UNIX: the status line appears at the bottom of the CLI window See the Command Line Interface Reference Guide for a complete description of all items in the task status line. Starting Tasks All tasks running on a controller are started by a CLI command.
Working with Tasks Controller Tasks TaskId Function Done% Container State Specific1 Specific2 ------ -------- ------- --------- ----- --------- --------No tasks currently running on controller To start a task, use the container create mirror command, as in the following example. In the example, the container create mirror command starts a mirror set create (MCR) task and a container scrub (MSC) task. HPN0> container create mirror 0 (3,0.
Command Line Interface User’s Guide HPN0> task list Executing: task list Controller Tasks TaskId Function Done% Container State Specific1 Specific2 ------ -------- ------- --------- ----- --------- --------106 Scrub 63.5% 00 RUN 00000000 00000000 To stop task 106, use the task stop command, as in the following example. In the example, the task stop command stops the task with the task ID of 106.
Working with Tasks Before suspending a task, use the task list command to display information about all tasks running on a controller, as in the following example. In the example the TaskID column indicates 107, which means that task 107 is running on a controller, and the Done% column indicates 50%, which means that the task is 50% complete.
Command Line Interface User’s Guide Before resuming a task, use the task list command to display information about all tasks running on a controller, as in the following example. In the example, the State column indicates SUS, which means that task 107 has been suspended.
14 Working with Remote Management This chapter explains how to use the CLI to locate and open a controller on another computer. Once you open a controller remotely, you can perform controller, container, and disk operations in the same manner as a controller opened on your local computer. Note: The remote management software provides security features to prevent unauthorized management of controllers from the network.
Command Line Interface User’s Guide For information about... Turn to... Unlocking Information in the Network Connection Database page 14-8 Deleting Information from the Network Connection Database page 14-10 Understanding Remote Management Attributes The remote management attributes are the characteristics of remote management that you can display or administer using the CLI. Table 14-1 lists the remote management attributes and their related CLI commands. Table 14-1.
Working with Remote Management To display whether a computer’s connection information is locked or unlocked in the network connection database, use the remote list command, as in the following example. In the example, the Lock Status column indicates U, which means that the connection record in the network connection database for the \\\TIGERNET\\BULLDOG computer is unlocked.
Command Line Interface User’s Guide Displaying the Remote User Name The remote user name attribute indicates the name of a user who is accessing a controller on a remote computer. To display the names of users accessing a controller on a remote computer, use the remote users command, as in the following example. In the example, the remote users command displays a list of users who are accessing the HPN0 controller on the yeti computer.
Working with Remote Management the remote scan command does not remove the record from the network connection database even if the associated computer is not currently running the FAST RMSA. Before scanning a domain, use the remote list command to display a list of computers that are running the FAST RMSA and have a connection record in the network connection database, as in the following example.
Command Line Interface User’s Guide U \\\TIGERNET\\GOLIATH L \\\TIGERNET\\OAK U \\\TIGERNET\\SUPREME L \\\TIGERNET\\SAMPSON Adding Information to the Remote Connection Database The CLI’s remote add command allows you to add a record with a computer’s connection information to the network connection database. The CLI automatically locks a computer’s connection record that is added to the network connection database with the remote add command.
Working with Remote Management werewolf.go.movies.com using the TCPIP network protocol. The default domain is tigernet. HPN0> remote add werewolf.go.movies.com TCPIP Executing: remote add "werewolf.go.movies.com" "TCPIP" After executing the remote add command, use the remote list command to display a list of computers that have a connection record in the network connection database, as in the following example.
Command Line Interface User’s Guide Lock Status Computer ------------ -------------------------- U \\\TIGERNET\\BULLDOG U \\\TIGERNET\\GOLIATH L \\\TIGERNET\\OAK U \\\TIGERNET\\SUPREME L \\\TIGERNET\\WEREWOLF To lock a computer’s connection record in the network connection database, use the remote lock command, as in the following example. In the example, the remote lock command locks the connection record in the network connection database for the computer BULLDOG.
Working with Remote Management remote scan command to delete the computer’s connection record from the network connection database. Before unlocking a computer’s connection record in the network connection database, use the remote list command to display a list of computers that have a connection record in the network connection database, as in the following example.
Command Line Interface User’s Guide U \\\TIGERNET\\BULLDOG U \\\TIGERNET\\GOLIATH L \\\TIGERNET\\OAK U \\\TIGERNET\\SUPREME L \\\TIGERNET\\WEREWOLF Deleting Information from the Network Connection Database The CLI’s remote delete command allows you to delete a computer’s or NetWare server’s connection record from the network connection database. The remote delete command deletes the connection record even if it is locked.
Working with Remote Management After executing the remote delete command, use the remote list command to display a list of computers that have a connection record in the network connection database, as in the following example. In the example, the entry for \\\TIGERNET\\BULLDOG has been removed from the list, which means that the connection record for the \\\TIGERNET\\BULLDOG computer has been deleted from the network connection database.
15 Working with Scripts This chapter explains how to write and execute automated scripts that can be used to perform a variety of CLI tasks. Scripts enable you to simplify controller management by executing multiple CLI commands or by executing CLI commands in conjunction with operating system commands. The following table provides a quick reference to the topics covered in this chapter. For information about... Turn to...
Command Line Interface User’s Guide The following sections describe how to execute CLI scripts from the afacli and OS command prompts. Executing a Script from the CLI Command Prompt A script that is to be run from the CLI command prompt consists of: ■ A script file. For DOS and NetWare environments, a .afa filename extension is required. In the UNIX environment, a filename extension is not required. ■ One or more CLI commands separated by a carriage return.
Working with Scripts Executing Scripts at the DOS Command Prompt You can execute a CLI script at the DOS command prompt as follows: ■ Enter the script filename with a .bat filename extension at the command prompt and press Enter, as in the following example. C:\> clist.bat The CLI commands in this script file must be entered on a single line and separated by a ";" (semicolon), as in the following example. The script file may contain CLI and DOS commands.
Command Line Interface User’s Guide $ clist.txt The CLI commands in this script file must be entered on a single line and separated by a ":" (colon), as in the following example. The script file may contain CLI and UNIX commands. In the example, the first line of the script is the UNIX ls command. The second line of the script is a series of CLI commands separated by a ":" Note the use of the backslash to make the script file more readable while adhering to the single line restriction.
Working with Scripts Executing Scripts at the NetWare and Windows NT/2000 Command Prompts You can execute a CLI script at the NetWare command prompt as follows. Note that there are three ways to run a NetWare script remotely from Windows NT/Windows 2000 (basic disk only), and one way to run a script from the NetWare console. ■ Enter the script filename at the NetWare console or Windows NT/Windows 2000 (basic disk only) command prompt and press Enter, as in the following example. > clist.
Command Line Interface User’s Guide Example Scripts This section provides example scripts that you may find useful or that you can adapt for your work environment. Example 1 The script in this example is the get configuration script, which is supplied with the controller software in a file named getcfg.hpn. The script comprises all CLI commands that display CLI information. See the Command Line Interface Reference Guide for information on each command. The script produces two output files: cfg.
Working with Scripts enclosure show slot enclosure show temperature enclosure show fan enclosure show power diagnostic moderation show timer diagnostic moderation show count diagnostic dump text diagnostic dump structures cfg.
Command Line Interface User’s Guide container create raid5 /cache /scrub ((0,0,0),30M) (0,1,0) (0,2,0) (0,3,0) (1,0,0) (1,1,0) (1,2,0) (2,1,0) (2,2,0) (2,3,0) (3,1,0) (3,2,0) (3,3,0) container create stripe /cache ((0,0,0),100M) (0,1,0) (0,2,0) (0,3,0) (1,0,0) (1,1,0) (1,2,0) (2,1,0) (2,2,0) (2,3,0) (3,1,0) (3,2,0) (3,3,0) container assign drive_letter 0 R container assign drive_letter 1 S container format /file_system=NTFS /quick/wait R container format /file_system=NTFS /quick/wait S Example 3 The scr
Index A access mode 3-9 activity light, blinking 4-19 adapter name 3-2 adding a file system 9-33 in UNIX 9-37 adding a level to a container how to 9-9 in UNIX 9-10 working with 9-8 assign failover disk attributes 9-28 assign failover disks to a single container how to 9-28 assign global failover disk attributes 9-30 assigning a drive letter to a container 6-5 global failover disks 9-30 attaching a diskset 5-18 attributes allocation size 9-35 assign failover disk 9-28 assign global failover disk 9-30 attache
Command Line Interface User’s Guide container update snapshot wait 10-7 container usage 6-24 controller attribute 3-8 controller cluster environment 3-7 controller CPU speed 3-12 controller CPU type 3-10 controller firmware 3-14 controller memory 3-13 controller name 3-8 controller rescan 3-15 controller serial number 3-10 creation date 6-14 creation time 6-15 creator ID 5-4 dead partition 4-17 device per channel or targets 3-12 device type 4-3 diagnostic 11-2 disk 4-2 disk defect 4-7 disk usage 4-6 disks 5
Index product ID 4-5 quick format 9-35 RAID-5 set 7-15 RAID-5 set restore 9-17 RAID-5 set scrub 9-18 RAID-5 set state 6-38 RAID-5 set unprotected state 6-38 read cache setting 6-41 read/write 4-16, 6-22 read-ahead cache 9-21 read-only 6-21 reconfiguration copy container state 6-32 reconfiguration destination container state 6-33 reconfiguration RAID-5 set state 6-33 reconfiguration source container state 6-34 reconfiguration state 6-31 reconfiguration temporary container state 6-34 remote computer 3-9 remot
Command Line Interface User’s Guide write cache setting 6-42 write cache status setting 6-43 write-back cache 9-23 attributes for stripe set of RAID-5 sets 8-14 automatic failover controller 3-17 B backing container 10-2 bad blocks repairing 4-18 batteries understanding 3-24 battery attributes 3-25 condition 3-25 reconditioning 3-26 state 3-25 blinking a disk light 4-19 blocks number of 4-6 repair bad 4-18 boot parameters clearing 11-6 buffer pools global cache 6-39 C cache attributes 6-39 nonvolitile wri
Index container extend volume 9-40 container move 6-10 container promote 9-6 container readonly 6-22 container readwrite 6-23 container reconfiguration 9-2 container release_cache 9-26 container remove failover 9-29 container remove file_system 9-39 container remove global_failover 9-32 container remove snapshot 10-9 container restore raid5 9-16 container scrub 9-14 container set cache 9-21 container set failover 3-17, 9-27 container set global_failover 3-17, 9-30 container set label 6-11 container show cac
Command Line Interface User’s Guide mail test 12-9 open 3-3 remote add 14-6 remote delete 14-10 remote list 14-3 remote lock 14-7 remote scan 14-4 remote unlock 14-8 remote users 14-4 task list 3-16, 13-2 task resume 13-9 task stop 13-7 task suspend 13-8 comment line 15-2 compact mode snapshot 10-2 compression file system 9-35 container access attributes 6-20 add level attributes 9-8 add_level command 9-8 always delete 9-46 copy 6-32 deleting 9-45 destination 6-33 extending 9-40 failover 9-27 how to delete
Index synchronous and asynchronous command execution 9-36 container ID displaying 6-10 renumbering 6-10 container identification attributes cluster partner 6-7 container label 6-11 container number 6-9 container type 6-12 drive letter 6-5 root special filer 6-6 container label displaying and setting 6-11 container move command 6-10 container number attribute 4-14 container offline attributes 9-44 container promote how to 9-7 container promote command 9-6 container promotion attributes 9-7 in UNIX 9-8 workin
Command Line Interface User’s Guide container update snapshot wait attribute 10-7 container usage attributes multi-partition container 6-27 NetWare environment 6-27 resident file system 6-26 unconfigured container 6-29 UNIX-opened 6-27 valid container 6-29 containers hidden 6-9 loading 11-9 modify 9-1 redundant 3-17 visible 6-9 containersize attributes stripe size 6-19 controller automatic failover 3-17 availability 3-9 closing 3-4, 3-5 opening and closing 3-2 rescan 3-15 controller attributes availability
Index destination container 6-33 diagnostic attributes understanding 11-2 diagnostic commands diagnostic clear boot_parameter 11-6 diagnostic dump structures 11-6 diagnostic dump text 11-4 diagnostic load_containers 11-9 diagnostic moderation set count 11-7 diagnostic moderation set timer 11-8 diagnostic moderation show count 11-3 diagnostic moderation show timer 11-3 diagnostic set boot_parameters 11-7 diagnostic show boot_parameter 11-4 diagnostic show history 11-5 working with 11-1 diangostic data dumpin
Command Line Interface User’s Guide diskset attributes 5-2 attached 5-6 creator ID 5-4 disks 5-6 diskset ID 5-3 failover 5-9 label 5-7 members 5-10 OS managed 5-7 owner 5-5 shared 5-8 diskset commands disk_set add 5-12 disk_set attach 5-18 disk_set changefailover pool 5-26 disk_set changelabel 5-20, 5-21 disk_set create 5-11 disk_set delete 5-15 disk_set detach 5-19 disk_set forceownership 5-23 disk_set list 5-3 disk_set OSmanaged 5-16 disk_set releaseownership 5-24 disk_set remove 5-13 disk_set takeownersh
Index container 9-40 file system 9-4, 9-37 multi-level container of volume sets 9-42 volume set 9-41 F failover controller automatic 3-17 disk 9-27 manual 3-17 pool 5-9 failover disks assigning global 9-30 assigning to a single container 9-27 how to assign global 9-30 how to assign to a single container 9-28 how to remove from single container 9-29 how to remove global 9-32 removing from a single container 9-29 removing global 9-31 fast channel type 3-23 FAST remote management services agent 14-2 fast wide
Command Line Interface User’s Guide mirror set 7-12 i/o wait duration scrubbing a mirror set 9-14 scrubbing a RAID-5 set 9-18 volume set of mirror sets 8-32 initialization state of a disk 4-9 initializing a disk 4-8 internal history log 11-5 interrupt count setting 11-7 interrupt count attribute 11-2 interrupt timer setting 11-8 L label specify for RAID-5 set 7-17 loading containers 11-9 locking information in the network connection database 14-7 logical unit number 4-3 LUN 4-3 M mail body line displaying
Index multi-level containers working with 8-1 multi-level containers of mirror sets working with 8-31 multi-level stripe sets working with 8-2 multi-level volume sets creating 8-18 N NetWare accessing operating system from CLI 2-2 opening and closing a controller from Windows 3-4 network connection database 14-2 deleting information from 14-10 locking information in 14-7 unlocking information in 14-8 no repair when scrubbing a mirror set 9-14 when scrubbing a RAID-5 set 9-18 non-volatile write cache 6-39 n
Command Line Interface User’s Guide how to create 7-19 no repair when scrubbing 9-18 restore attributes 9-17 restoring 9-16 scrub attributes 9-18 scrubbing 9-18 setting parity by scrubbing 7-18 specify freespace 7-16 specify label 7-17 specify stripe size 7-16 state attribute 6-38 synchronous and asynchronous creation 7-18 working with 7-15, 9-16 RAID-5 set attributes container label 7-17 stripe size 7-16 RAID-5 set scrub attributes i/o delay 9-18 no repair 9-18 wait 9-19 RAID-5 set state attributes RAID-5
Index displaying 14-4 remove container drive letter 6-6 failover disk attributes 9-29 file system attributes 9-39 global failover disks attributes 9-32 removing failover disks from a single container 9-29 file system 9-39 file system in UNIX 9-40 global failover disks 9-31 renumbering a container’s ID 6-10 report count display and set 4-27 rescanning a controller 3-15 reset channel 3-24 restoring a RAID-5 set 9-16 how to 9-17 resuming controller I/O 3-15 resuming tasks 13-9 root special file associated with
Command Line Interface User’s Guide creating 10-2 link 10-1 snapshot commands container create snapshot 10-2 container remove snapshot 10-9 container show snapshot 10-6 container update snapshot 10-7 controller free snapshot 10-11 controller show unconfigured_snapshot 10-11 snapshot container backing container 10-2 how to create 10-4 original container 10-1 removing 10-9 safe mode 10-4 stripe size 10-3 unconditionally remove link 10-9 unconfigured snapshot 10-11 update synchronously or asynchronously 10-7 u
Index container label 8-7 stripe size 8-7 stripe set of volume sets attributes 8-7 creating in NetWare 8-9 creating in UNIX 8-9 how to create 8-8 stripe size changing 9-3 displaying and setting 6-19 specify when creating stripe set 7-7 stripe size attribute stripe set of mirror sets 8-3 stripe set of RAID-5 sets 8-14 stripe set of stripe sets 8-10 stripe size attributes stripe size 7-7 suspending tasks 13-8 T taking a container offline 9-44 taking ownership of a diskset 5-22 target ID 4-3 targets 3-12 task
Command Line Interface User’s Guide V verify a disk repair bad blocks 4-18 withoug reparing bad blocks 4-18 verifying a disk 4-18 visible container 6-9 volatile read cache 6-39 volume set create in NetWare environment 7-5 create in UNIX environment 7-6, 7-20 enable raw container cache 7-3 extending 9-40 freespace 7-3 how to create 7-4 how to extend 9-41 specify a label 7-4 working with 7-2 volume set attributes container label 7-4 volume set of mirror sets attributes 8-22 creating 8-21 creating in NetWare
