SCSI NIKE (Disk Array) Expert Tool (xstm Online Help)

The Cxx00 Array Expert Tool provides functionality to examine, interrogate, test, configure and manage Cxx00 Array devices. The tool is interactive in nature, and will provide information and/or initiate actions in response to user directives.

CAUTION:

• This tool provides commands which can:
  • Impair access to and/or the functioning of the device.
  • Change configuration and/or characteristics of the device.
  To use this tool safely, you should be trained in and knowledgeable about Cxx00 Array devices.

NOTE:

• Help Catalog version is: A.02.01

SEE ALSO:

• Introduction
• Step-by-Step Instructions
• Troubleshooting Tool-Related Problems
• Interface Method
• Commands

Introduction

The Cxx00 Array Expert Tool provides functionality to examine, interrogate, test and alter Cxx00 Array devices. This functionality is provided through the issuance of SCSI commands to the device.

NOTE:

• The Cxx00 Array Expert Tool is a licensed tool, and thus requires an appropriate license be installed before the tool can be used.

SEE ALSO:

• Step-by-Step Instructions
• Troubleshooting Tool-Related Problems
• Interface Method
• Commands

Step-by-Step Instructions

To run the Cxx00 Array Expert Tool:

1. At the main STM window, select a Cxx00 Array device.

   Only one device can be selected per execution of the Cxx00 Array Expert Tool. To run the tool against multiple Cxx00 Array devices simultaneously:

   • Select a device.
   • Start an instance of this tool.
   • Repeat previous steps for each desired device.

   NOTE: Each SP of a Cxx00 Array has its own hardware path. As such:

   • Each SP is considered a separate device by the host.
   • Each SP is shown as a separate device in the STM device map/listing.
2. Run the Cxx00 Array Expert Tool.

   WARNING: Simultaneous execution of the Cxx00 Array Expert Tool against both SPs of a multi-SP Cxx00 Array is NOT recommended. Command conflict can occur, resulting in severe performance degradation caused by command induced device 'thrashing'.

3. Execute the desired command(s).

   Queries and information are displayed in pop-up windows and/or the main window.

4. Exit the tool by using the Exit command.

SEE ALSO:

• Introduction
• Troubleshooting Tool-Related Problems
• Interface Method
• Commands

Troubleshooting Tool-Related Problems

• A failure, or other problem, with the Cxx00 Array Expert Tool:

  Consult the Failure Log and/or the Test Activity Log, accessible from the STM main window.

• Problem with the device:

  Make sure the device is connected, powered on, and on-line.

• The computer system becomes slow to respond or non-responsive:

  If the selected device is a system (root) disk, some of the Cxx00 Array Expert Tool commands can cause the computer system to become slow or non-responsive.

  You can interrupt, and subsequently stop, the executing command by using the Interrupt command (if it is permissible to interrupt the command). Or you can abort the tool and return to the main window by using the Abort command (if it is permissible to abort the command).

  To reduce the chance of this problem occurring, consider specifying a smaller scope for the command (where applicable). For example, when reading disks or luns, specify a single block or range of blocks to read rather than the entire disk or lun.

• You start a Cxx00 Array Expert Tool command but nothing seems to happen:

  The tool may be waiting for you to respond to a query message. Check carefully for any messages you may have missed, including looking underneath existing windows and checking iconified windows, and respond as needed.

• When you try to access the Cxx00 Array Expert Tool from the main STM interface, you can not run it:

  The Cxx00 Array Expert Tool is a licensed tool, and thus requires a license to operate. Install the license at the main STM window and try to run the tool again.

  It may also be that there is already a tool running against the desired device, either by you or somebody else. Since there can be only one tool running against a device at a time, the currently running tool will have to complete first.

SEE ALSO:

• Introduction
• Step-by-Step Instructions
• Interface Method
• Commands

Menu Bar

Cxx00 Array Expert Tool commands are grouped by category according to functionality. The commands within these categories are accessible through the Menu Bar, and include:

• File:
  • SaveAs: Save tool's main window to a file.
  • Print: Print tool's main window.
  • Exit: Exit the tool.
• Logs:
  • View Unsolicited Log:
    • ViewUnsolicitedLog >Event Codes: All: Display all log entries.
    • ViewUnsolicitedLog >Event Codes: >= 0x800: Display only log entries with event codes >= 0x800.
    • ViewUnsolicitedLog >Event Codes: >= 0x900: Display only log entries with event codes >= 0x900.
    • ViewUnsolicitedLog >Event Codes: >= 0xA00: Display only log entries with event codes >= 0xA00.
  • ClearUnsolicitedLog: Delete Unsolocited Event Log entries.
• Info:
  • Capacity: Display lun and disk capacity information.
  • Inquiry: Display lun and disk inquiry information.
• I/O:
  • ReadDisks: Read disks.
  • ReadLuns: Read luns.
• Tests:
  • TestUnitReady: Test readiness of luns and disks.
  • VerifyDisks: Verify disks.
  • VerifyLuns: Verify luns.
• Utilities:
  • BindLun: Bind disks into a lun.
  • UnbindLuns: Unbind disks of a lun.
  • Lun Configuration:
    • AutoAssign: Set lun Auto Assign state.
    • CacheParms: Set lun cache parameters.
    • DefaultOwnership: Set lun default SP ownership.
    • RebuildTime: Set lun rebuild time.
  • System Configuration:
    • AutoTrespassArray: Set device Auto Trespass state.
    • BBUTestTime: Set BBU test time.
    • DateTime: Set device date and time.
    • HostIFOptions: Set Host Interface Options.
    • SerialNumber: Set device system serial number.
    • SystemCache: Set system cache parameters.
    • SystemMemory: Set system memory parameters.
    • SystemType: Set System Type parameter.
• Lab Use Only:
  • This category contains commands restricted for use by HP development labs only.
• Help:
  • Help>General: Display tool help information.
  • Help"> Version: Display tool version and copyright information.

SEE ALSO:

• Introduction
• Step-by-Step Instructions
• Troubleshooting Tool-Related Problems
• Commands

Commands

The Cxx00 Array Expert Tool supports the following commands:

Abort

Abort tool.

AutoAssign

Set lun Auto Assign state.

AutoTrespassArray

Set device Auto Trespass state.

BindLun

Bind disks into a lun.

BBUTestTime

Set device BBU test time.

CacheParms

Set lun cache parameters.

Capacity

Display lun and disk capacity information.

ClearUnsolicitedLog

Delete Unsolicited Event Log entries.

DateTime

Set device date and time.

DefaultOwnership

Set lun default SP ownership.

ViewUnsolicitedLog >Event Codes: All

Display all Unsolicited Event Log entries.

ViewUnsolicitedLog >Event Codes: >= 0x800

Display only Unsolicited Event Log entries with event codes >= 0x800.

ViewUnsolicitedLog >Event Codes: >= 0x900

Display only Unsolicited Event Log entries with event codes >= 0x900.

ViewUnsolicitedLog >Event Codes: >= 0xA00

Display only Unsolicited Event Log entries with event codes >= 0xA00.

Exit

Exit tool.

Help >General

Display tool help information.

HostIFOptions

Set host interface options.

Inquiry

Display lun and disk inquiry information.

Interrupt

Interrupt command execution.

Print

Print tool's main window.

ReadDisks

Read disks.

ReadLuns">

Read luns.

RebuildTime

Set lun rebuild time.

SaveAs

Save tool's main window to a file.

SerialNumber

Set device system serial number.

SystemCache

Set system cache parameters.

SystemMemory

Set system memory parameters.

SystemType

Set System Type parameter.

TestUnitReady

Test readiness of disks and luns.

UnbindLuns

Unbind disks of a lun.

VerifyDisks

Verify disks.

VerifyLuns

Verify luns.

Help >Version

Display tool version and copyright information.

SEE ALSO:

• Introduction
• Step-by-Step Instructions
• Troubleshooting Tool-Related Problems
• Interface Method
• Command Output Heading

Command Output Heading

The output of Commands, which produce a 'results listing' is preceeded by a heading containing the following information:

Array Date:

The Gregorian calendar date (mm/dd/yy), as reported by the SP. This value can be changed by using the DateTime command.

Array Time:

The time (hh:mm:ss) in '24 hour' format, as reported by the SP. This value can be changed by using the DateTime command.

Array SP:

The ID (A, B), the SCSI ID, and the LOOP ID of the SP, but with the following caveats:

• The SCSI ID is the Fibre Channel 'hard address' if the device is a Fibre Channel device.
• The LOOP ID is valid only if the device is a Fibre Channel device.

SN:

The 'system serial number' of the device. This value can be changed (firmware revision dependent) by using the SerialNumber command.

FW:

The firmware and prom revisions currently running on the SP.

MN:

The model number and model name of the SP.

System Date:

The Gregorian calendar date (mm/dd/yy), as reported by the host system.

System Time:

The time (hh:mm:ss) in '24 hour' format, as reported by the host system.

System Name:

The host system name, as reported by the host system.

The Support Tool Manager may also insert information before and/or after the results listing generated by the command. The inserted information may include:

• The name of the tool (Expert Tool).
• The name of the command which produced the listing (Capacity).
• The name of the device (Cxx00 Array).
• The hardware path to the device (8/0.8.0.255.0.2).
• Other information.

SEE ALSO:

• Commands

Abort

DESCRIPTION:

The Abort command allows you to abort the SCSI NIKE (Disk Array) Expert Tool, halting its execution and returning to the STM main window.

The tool will be requested to abort and the state of the tool execution in the system map will be set to ABORT_PENDING. When the tool actually exits, its state will be set to ABORTED.

NOTE:

• The tool may not immediately respond to the Abort command, as it could be performing an operation that should not, or cannot, be aborted. In such instances, the Abort command will be processed when appropriate to do so.

WARNING:

• Use of this command is NOT ADVISED, as the interruption of operations in progress may leave the device in an invalid state. possibly rendering the device, and data on it, inaccessible.

SEE ALSO:

• Exit
• Interrupt

Auto Assign

DESCRIPTION:

The Auto Assign command allows you to set/change a lun's Auto Assign state.

Access to a lun by an SP generally requires that the SP have current ownership of the lun (current ownership of a lun belongs to the SP to which the lun is currently assigned). A lun's Auto Assign state determines whether or not an SP can automatically attempt assignment of the lun if the SP needs, but does not have, current ownership. Assignment will be attempted if and only if the lun's Auto Assign state is enabled. Assignment can occur if and only if the lun is not currently assigned to (not currently owned by) an active peer SP.

The possible Auto Assign states are:

• Enabled: Auto Assign is enabled.
• Disabled: Auto Assign is disabled.

NOTE:

• Access to luns is Operating System, device firmware and device command dependent (example: SCSI-2 supports only luns 0-7). Inaccessible luns will be excluded from the command's lun selection list(s).
• Auto assignment is a "passive" attempt to obtain current ownership of a lun. Trespassing is a "forced" acquisition of the current ownership of a lun.

SEE ALSO:

• AutoTrespassArray
• DefaultOwnership

Auto Trespass

DESCRIPTION:

The Auto Trespass command allows you to set/change the device's Auto Trespass state.

Access to a lun by an SP generally requires that the SP have current ownership of the lun (current ownership of a lun belongs to the SP to which the lun is currently assigned). The device's Auto Trespass state determines if current ownership (not DefaultOwnership>default ownership) of a lun can be automatically and forcibly transferred (assigned) to the requesting SP.

The possible Auto Trespass states are:

• On: Auto Trespass is enabled.
• Off: Auto Trespass is disabled.

NOTE:

• This command is not supported under all revisions of Cxx00 Array device firmware. In general, firmware revision 8.x or greater is required.
• The device's Auto Trespass state is a single, device-wide setting. As such, it affects ALL luns.

WARNING:

• Changing the Auto Trespass state of the device can have an immediate and significant impact on data accessibility. As such, this command should be used only if the ramifications of doing so are fully understood.

SEE ALSO:

• AutoAssign
• DefaultOwnership
• SystemType

Bind Lun

DESCRIPTION:

The Bind Lun command allows you to bind disks into a logical unit (lun), which is then recognized, and treated, as a single disk unit by the host.

Lun binding requirements (disk count):

Hot Spare:

1 disk module.

Individual Disk:

1 disk module.

RAID-0:

3 to 16 disk modules.

RAID-1:

2 disk modules.

RAID-1/0:

4 to 16 disk modules, in even increments (4, 6, 8, 10, 12, 14, 16).

RAID-3:

5 disk modules.

RAID-5:

3 to 16 disk modules.

Lun binding recommendations:

RAID-1:

Use 2 disk modules on different internal buses (example: A1, B1).

RAID-3:

Use 5 disk modules on different internal buses (example: A1, B1, C1, D1, E1).

RAID-5:

Use 5 disk modules on different internal buses (example: A1, B1, C1, D1, E1).

Lun binding restrictions:

Hot Spare:

Cxx00 Array device database and vault drives may NOT be used for Hot Spare luns. The restricted drives are:

• 10 slot: A0, B0, A1, A2, A3, A4.
• 20 slot: A0, B0, C0, D0, E0, A3.
• 30 slot: A0, B0, C0, D0, E0, A3, A4.

SEE ALSO:

• UnbindLuns

BBU Test Time

DESCRIPTION:

The BBU Test Time command allows you to set/change the BBU (battery backup unit) test time.

The BBU test time is the day and time at which the Cxx00 Array device will perform an automatic self test of the BBU:

• The day is specified by numeric value:
  • 1 == Sunday
  • 2 == Monday
  • 3 == Tuesday
  • 4 == Wednesday
  • 5 == Thursday
  • 6 == Friday
  • 7 == Saturday
• The time is specified by:
  • hour: 0 to 23
  • minute: 0 to 59

NOTE:

• This command is not supported under all revisions of Cxx00 Array device firmware. In general, firmware revision 8.x or greater is required.

SEE ALSO:

• DateTime
• SerialNumber

Cache Parms

DESCRIPTION:

The Cache Parms command allows you to:

• Enable/Disable a lun's read and write cache.
• Set/Change a lun's read and write cache values.

Modifiable cache values include:

Prefetch Type:

• Disabled: No prefetching is allowed on this lun.
• Constant Length: Prefetching is specified in numbers of blocks.
• Variable Length: Prefetching is specified by a multiplier or factor.

Cache Idle Threshold:

The maximum number of I/Os that can be outstanding to a LUN and have the LUN still considered idle. The SP will perform flushes on idle units. The range for this value is 0 to 254.

Cache Idle Delay Time:

The amount of time (in 100ms intervals) that a LUN must be below the idle threshold in order to be considered idle. The range for this value is 0 to 25500.

Cache Write Aside Size:

The smallest write request size, in blocks, that will bypass the cache and go directly to the disks. The range for this value is 16 to 65534.

Prefetch Factor:

This value has two definitions, depending on the prefetch type:

• If set to Constant Length then this value specifies the size of the prefetch data in blocks. The range for this value is 1 to 2048.
• If set to Variable Length then this value specifies the multiplier or factor to be used to calculate the prefetch length. This is set by the equation:

  prefetch-size-in-blocks = read-request-size X prefetch-multiplier

  The multiplier or factor has a range of 1 to 32.

Segment Factor:

The size of the segments into which the system divides all prefetch operations in order to avoid heavy overhead. This value has two definitions, depending on the prefetch type:

• For Constant Length prefetching this value specifies segment size in blocks.
• For Variable Length prefetching this value specifies the multiplier or factor to calculate the size of the segment. This is determined by the equation:

  segment-size-in-blocks = read-request-size X segment-multiplier

  The multiplier or factor has a range of 1 to 32, but may NOT be larger than the Prefetch Factor.

Maximum Prefetch:

The maximum number of blocks to prefetch in response to a read request, but is applicable only for variable length prefetching. For constant length prefetches, all prefetches are of constant length as specified by the prefetch size. The maximum value that may be specified is 2048.

Prefetch Disable Length:

The minimum read request size at which the system will disable prefetching. The range for this value is 1 to 65534.

Prefetch Idle Count Threshold:

The maximum number of I/Os that can be outstanding to the unit with prefetching enabled. When this number is exceeded, the system will disable prefetching. The range for this value is 1 to 100.

NOTE:

• Access to luns is Operating System, device firmware and device command dependent (example: SCSI-2 supports only luns 0-7). Inaccessible luns will be excluded from the command's lun selection list(s).
• To change a lun's read or write cache values, both read and write cache must be disabled (see SystemCache command).

SEE ALSO:

• SystemCache

Capacity

DESCRIPTION:

The Capacity command allows you to display lun and disk capacity information:

• Luns:

  Column

  Information

  Lun

  The lun to which the information pertains.

  VendorID

  The lun's Vendor Identification, as reported by a SCSI Inquiry command to the lun.

  ProductID

  The lun's Product Identification, as reported by a SCSI Inquiry command to the lun.

  User Information

  User information, as reported by the SP:

  Cap (blks)

  The lun's capacity in blocks.

  BSz

  The lun's block size (in bytes).

  GBytes

  The lun's capacity in gigabytes, where a gigabyte equals 1,000,000,000 bytes..

  Lun Information

  Lun information, as reported by a SCSI Read Capacity command to the lun:

  Last Addr

  The lun's last logical block address..

  BSz

  The lun's block size (in bytes)..

  GBytes

  The lun's capacity in gigabytes, where a gigabyte equals 1,000,000,000 bytes..

• Disks:

  Column

  Information

  Dsk

  The disk to which the information pertains.

  VendorID

  The disk's Vendor Identification, as reported by a SCSI Inquiry command to the disk.

  ProductID

  The disk's Product Identification, as reported by a SCSI Inquiry command to the disk.

  User Information

  User information, as reported by the SP:

  Cap (blks)

  The disk's user capacity in blocks.

  BSz

  The disk's user block size (in bytes).

  GBytes

  The disk's user capacity in gigabytes, where a gigabyte equals 1,000,000,000 bytes.

  Disk Information

  Disk information, as reported by a SCSI Read Capacity command to the disk:

  Last Addr

  The disk's last logical block address.

  BSz

  The disk's actual block size (in bytes).

  GBytes

  The disk's actual capacity in gigabytes, where a gigabyte equals 1,000,000,000 bytes.

NOTE:

• Access to luns is Operating System, device firmware and device command dependent (example: SCSI-2 supports only luns 0-7). Inaccessible information will be reported as ? or 0, depending on the information type (character or number).
• READ CAPACITY commands to Hot Spare luns is NOT supported by the Cxx00 Array device. Inaccessible information will be reported as ? or 0, depending on the information type (character or number).
• Access to disks participating in active Hot Spare operations is NOT supported by the Cxx00 Array device. Inaccessible information will be reported as ? or 0, depending on the information type (character or number).

SEE ALSO:

• Command Output Heading
• Inquiry

Clear Unsolicited Log

DESCRIPTION:

The Clear Unsolicited Log command allows you to delete all entries in an SP's Unsolicited Event Log.

WARNING:

• Clearing an SP's Unsolicited Event Log deletes all existing event log information, which may adversely impact 'failure' and/or 'predicitive failure' analysis.

SEE ALSO:

• ViewUnsolicitedLog

Date Time

DESCRIPTION:

The Date Time command allows you to set/change the date and time of the Cxx00 Array device to the date and time of the host system.

NOTE:

• This command is not supported under all revisions of Cxx00 Array device firmware. In general, firmware revision 8.x or greater is required.
• Though the current date and time of the host system will be displayed in the command confirmation request message, the actual date and time used to update the device will be re-determined (from the host system) during update processing. This permits the device's date and time to be syncronized with the host system without regard to any delay between the display of the confirmation message and the actual update.

SEE ALSO:

• BBUTestTime
• SerialNumber

Default Ownership

DESCRIPTION:

The Default Ownership command allows you to set/change a lun's default owning SP.

Access to a lun by an SP generally requires that the SP have current ownership of the lun (current ownership of a lun belongs to the SP to which the lun is currently assigned). Default ownership defines which SP shall be initially given current ownership (assignment) of a lun following a power-up of the Cxx00 Array device or a restart of the SP(s).

NOTE:

• Access to luns is Operating System, device firmware and device command dependent (example: SCSI-2 supports only luns 0-7). Inaccessible luns will be excluded from the command's lun selection list(s).
• Default ownership changes will not take effect until the SP(s) are restarted. This can be done, for example, by using the restart controller(s) command of the firmware update tool or by power cycling the Cxx00 Array device.

SEE ALSO:

• AutoAssign
• AutoTrespassArray

Exit

DESCRIPTION:

The Exit command allows you to exit the Cxx00 Array Expert Tool.

SEE ALSO:

• Abort
• Interrupt

Help

DESCRIPTION:

The Help commands allow you to obtain help related information regarding the SCSI NIKE (Disk Array) Expert Tool:

Command

Function

General

Displays help for the Cxx00 Array Expert Tool (the help system you are currently viewing).

Version

Displays version and copyright information for the Cxx00 Array Expert Tool.

NOTE:

• For information on STM and/or using the help system, use the STM Help command at the main STM user interface.

Host Interface Options

DESCRIPTION:

The Host Interface Options command allows you to affect certain operating characteristics of the Cxx00 Array device's host system. Each of these characteristics is described below.

Host Interface Characteristics:

• Target Initiated Negotiation: If enabled and there is no current agreement outstanding with the initiator, then the target can attempt to initiate Data Transfer Requests (Wide DTR and/or Synchronous DTR) while in the SCSI DATA phase. SCSI commands other than INQUIRY or REQUEST SENSE will return a Check Condition. Default setting is enabled.
• Substitute Busy for Queue Full: If enabled, return a busy (0x08) status instead of a queue full (0x28) status when the SP has exhausted its list of free processor blocks. (Some initiators expect a BUSY status instead of a QUEUE FULL status). Default setting is disabled.
• Mode Page 0x08 Support: If enabled, mode page 0x08 requests will be returned as the Caching Mode Page. If disabled, a mode page 0x08 call will result in an error. Default setting is enabled.
• Recovered Error Log Reporting: If disabled, Check Conditions are only returned for I/O errors encountered during the active execution of that I/O. No events external to the service of the I/O (such as a fan failure during a read to a healthy CRU) will interfere in an I/O's status. Default setting is enabled.
• Allow Non-Mirrored Cache: If enabled and there is no peer SP, then the ability to use single board caching is available. Default setting is disabled.
• Spindle Synchronization: If enabled, flare will attempt spindle synchronization if the drive and flare revision support it. Default setting is disabled.
• Trespass Logging: If disabled, suppresses the messages 0x606 "Unit Shutdown for Trespass" and 0x602 "CRU Enabled" which occur on the SPs when a LUN is trespassed from one SP to the other SP. This suppression is useful in order to prevent the Unsolicited Log from filling up with these messages in environments which perform many Trespass operations (or use Auto-Trespass). Default setting is disabled.

NOTE:

• This command is not supported under all revisions of Cxx00 Array device firmware. In general, firmware revision 9.x or greater is required.
• This tool permits the setting/changing of host interface options to any value supported by the device's firmware. This is consistent with the serial port interface tool commonly referred to as Grid Manager.
• Changes to the following host interface options apply to the storage subsystem and will thus be applied to both SPs even if a "no" is answered to the question to apply changes to both SPs:
  • Allow Non-Mirrored Cache
  • Spindle Synchronization
  • Trespass Logging

SEE ALSO:

• AutoTrespassArray:
• ViewUnsolicitedLog

Inquiry

DESCRIPTION:

The Inquiry command allows you to display lun and disk Inquiry information, as reported by SCSI Inquiry commands to the luns and disks:

• Luns:

  Column

  Information

  Lun

  The lun to which the information pertains.

  VendorID

  The lun's Vendor Identification.

  ProductID

  The lun's Product Identification.

  PRvL

  The lun's Product Revision Level (typically containing the product's firmware revision).

• Disks:

  Column

  Information

  Dsk

  The disk to which the information pertains.

  VendorID

  The disk's Vendor Identification.

  ProductID

  The disk's Product Identification.

  PRvL

  The disk's Product Revision Level (typically containing the product's firmware revision).

NOTE:

• Access to luns is Operating System, device firmware and device command dependent (example: SCSI-2 supports only luns 0-7). Inaccessible information will be reported as ? or 0, depending on the information type (character or number).
• Access to disks participating in active Hot Spare operations is NOT supported by the Cxx00 Array device. Inaccessible information will be reported as ? or 0, depending on the information type (character or number).

SEE ALSO:

• Command Output Heading
• Capacity

Interrupt

DESCRIPTION:

The Interrupt command allows you to request the tool to abort execution of the current command.

NOTE:

• The tool may not immediately respond to the Interrupt command, as it could be performing an operation that should not, or cannot, be interrupted. In such instances, the Interrupt command will be processed when appropriate to do so.

WARNING:

• Use of this command is NOT ADVISED, as the interruption of operations in progress may leave the device in an invalid state. possibly rendering the device, and data on it, inaccessible.

SEE ALSO:

• Abort
• Exit

Print

DESCRIPTION:

The Print command allows you to print the contents of the tool's main window.

SEE ALSO:

• STM help for more specific information on this command.
• SaveAs

Read Disks

DESCRIPTION:

The Read Disks command allows you to read, and optionally display, disk data blocks (sectors).

The following levels of read granularity are supported (subject to restrictions in "NOTE:" below):

ALL disks, ALL blocks:

Read all blocks of all disks.

SELECTED disks, ALL blocks:

Read all blocks of selected disks.

SELECTED disks, SPECIFIED blocks:

Read user specified blocks of user selected disks. This option also supports the displaying of data read, which is presented in both hexidecimal and ascii format.

NOTE:

• Access to disks participating in active Hot Spare operations is NOT supported by the Cxx00 Array device. Inaccessible disks will be excluded from the command's disk selection list(s).
• Proprietary data may exist on disk blocks 0 through 0x9000 (36,864 decimal). As such, reading of these blocks is NOT supported.
• Reading (large amounts of) data can require a considerable amount of time. As a means of providing progress status, a 'heartbeat' message is given approximately every 60 seconds (when appropriate to do so).
• When displaying data read, host system resources, such as file descriptors and disk space, are temporarily consumed. As such:
  • A 'maximum' number of blocks to display is imposed.
  • Indiscriminate use of the display feature is not recommended.

SEE ALSO:

• Command Output Heading
• ReadLuns
• TestUnitReady
• VerifyDisks
• VerifyLuns

Read Luns

DESCRIPTION:

The Read Luns command allows you to read, and optionally display, lun data blocks.

The following levels of read granularity are supported (subject to restrictions in "NOTE:" below):

ALL luns, ALL blocks:

Read all blocks of all luns.

SELECTED luns, ALL blocks:

Read all blocks of selected luns.

SELECTED luns, SPECIFIED blocks:

Read user specified blocks of user selected luns. This option also supports the displaying of data read, which is presented in both hexidecimal and ascii format.

NOTE:

• Access to luns is Operating System, device firmware and device command dependent (example: SCSI-2 supports only luns 0-7). Inaccessible luns will be excluded from the command's lun selection list(s).
• Read access is supported only to fully bound, non Hot Spare luns which are accessible from the current SP. Inaccessible luns will be excluded from the command's lun selection list(s).
• Reading (large amounts of) data can require a considerable amount of time. As a means of providing progress status, a 'heartbeat' message is given approximately every 60 seconds (when appropriate to do so).
• When displaying data read, host system resources, such as file descriptors and disk space, are temporarily consumed. As such:
  • A 'maximum' number of blocks to display is imposed.
  • Indiscriminate use of the display feature is not recommended.

SEE ALSO:

• Command Output Heading
• AutoTrespassArray
• ReadDisks
• TestUnitReady
• VerifyDisks
• VerifyLuns

Rebuild Time

DESCRIPTION:

The Rebuild Time command allows you to set/change the maximum amount of time (in hours) that the Cxx00 Array device should take to rebuild a failed disk a lun.

NOTE:

• Access to luns is Operating System, device firmware and device command dependent (example: SCSI-2 supports only luns 0-7). Inaccessible luns will be excluded from the command's lun selection list(s).
• Valid maximum rebuild time values are 0 to 254 inclusive. The default value is 4.
• The maximum rebuild time is applicable only to luns of the following RAID levels:
  • RAID-1
  • RAID-1/0
  • RAID-3
  • RAID-5

WARNING:

• Changing the maximum rebuild time of a lun may affect system performance. Caution must therefore be used when setting/changing this value.

SEE ALSO:

• AutoAssign

Save As

DESCRIPTION:

The Save As command allows you to save the contents of the tool's main window to a file.

SEE ALSO:

• Print

Serial Number

DESCRIPTION:

The Serial Number command allows you to set/change the Cxx00 Array device's system serial number.

NOTE:

• This command is not supported under all revisions of Cxx00 Array device firmware. In general, firmware revision 9.x or greater is required.
• System serial number values are processed/verified by this tool as follows:
  • Leading and trailing blanks are silently removed.
  • Imbedded blanks are NOT permitted.

WARNING:

• EXTREME CAUTION is urged when changing a Cxx00 Array device's serial number, as the value may be used in some environments (high availability, multi-host, clustered) to uniquely identify the Cxx00 Array device. Non-unique serial numbers within such environments may cause problems, including possible data corruption and/or loss.

SEE ALSO:

• BBUTestTime
• DateTime

System Cache

DESCRIPTION:

The System Cache command allows you to set/change system cache related parameters:

Cache Page Size:

The amount of physical memory, in KBytes, to be used in the read and write caches. Valid values are 2, 4, 8 and 16.

High Watermark:

The percentage of cache dirty pages which, when reached, will cause the SP to begin flushing the cache. The range for this value is 0 to 100, but can NOT be less than the low watermark.

Low Watermark:

The percentage of cache dirty pages which, when reached, will cause the SP to cease flushing the cache. The range for this value is 0 to 100, but can NOT be greater than the high watermark.

Peer Read Cache State:

Enable/Disable Peer SP read cache.

Read Cache State:

Enable/Disable SP read cache.

Statistics Logging State:

Enable/Disable statistics logging.

Write Cache State:

Enable/Disable write cache.

NOTE:

• This command is not supported under all revisions of Cxx00 Array device firmware. In general, firmware revision 8.x or greater is required.
• Cache Page Size may be changed only if both SP's Read and Write caches are disabled.
• High Watermark can not be less than the Low Watermark.

SEE ALSO:

• CacheParms
• SystemMemory

System Memory

DESCRIPTION:

The System Memory command allows you to set/change system memory related parameters:

Total Physical Memory:

This is the total amount of system memory (in megabytes) that each SP has available. This is not software-customizable.

System Buffer Size:

This is the amount of system memory (in megabytes) on each SP that is reserved for the SP's own use, including data buffers. The default value is 4 megabytes.

Note that modifying System Buffer Size will cause both SPs to restart (see "WARNING:" below).

RAID-3 Memory Size:

This is the amount of system memory (in megabytes) that is reserved for use by RAID-3 logical units. This value applies to both SPs if there are two. Free RAID-3 memory is equal to the total RAID-3 memory minus the amount of RAID-3 memory already used in other RAID-3 luns.

System memory must be allocated to Optimized RAID-3 Memory for RAID-3 LUNs before binding them. The minimum amount of Optimized RAID-3 Memory required per RAID-3 LUN is 2 megabytes, although 6 megabytes is recommended for optimal performance.

RAID-3 memory cannot be lowered to less than the total value of RAID-3 memory currently used in RAID-3 LUNs. RAID-3 LUNs bound on either SP use up Optimized RAID-3 Memory from both SPs.

If the value of free Optimized RAID-3 Memory is listed as "UNKNOWN", then the value could not be accurately determined. Commands that depend upon Optimized RAID-3 Memory can still be attempted, though they may fail if an insufficient amount of free RAID-3 memory is available.

Note that modifying Optimized RAID-3 Memory will cause both SPs to restart (see "WARNING:" below).

Write Cache Size:

This is the amount of system memory (in megabytes) that the SP can use for the write cache. This value applies to both SPs if there are two. Legal values are 0 and any value up to the SP physical memory size, with the exception of the value 1.

Read Cache Size:

This is the amount of memory (in megabytes) that the SP can use for its read cache.

NOTE:

• This command is not supported under all revisions of Cxx00 Array device firmware. In general, firmware revision 8.x or greater is required.
• When specifying memory sizes, the combined sizes of Read Cache, Write Cache, RAID-3 Memory (if applicable) and System Buffer Size cannot exceed the SP's physical memory size.
• All caches must be disabled before you can modify either the System Buffer or RAID-3 Memory sizes.
• SP Write Cache size may only be altered if the write cache is disabled (see SystemCache).
• SP Read Cache size may only be altered if read cache is disabled for the SP (see SystemCache).

WARNING:

• Setting an SP System Buffer or Optimized RAID-3 Memory size to a value other than it's current setting will cause the SP(s) to restart... which will interrupt device access AND CAUSE THE LOSS OF ALL CURRENTLY BINDING LUNS!!!

SEE ALSO:

• SystemCache

System Type

DESCRIPTION:

The System Type command allows you to set/change the Cxx00 Array device's System Type, which "controls certain operating characteristics of the array" and is used "when non-standard features are required for specific environments".

Recognized/Supported HP System Types, as of this writing, and their typically perceived effects are:

• 2: Auto trespass enabled.
• A: Auto trespass disabled.

However, setting the System Type has other implications (as noted above and in "WARNING:" below). To set/change just the auto-trespass state, use of the AutoTrespassArray command is recommended.

NOTE:

• This command is not supported under all revisions of Cxx00 Array device firmware. In general, firmware revision 9.x or greater is required.
• Write cache must be disabled before a System Type command is issued. If write cache is not disabled, the command will fail.
• This tool permits the setting/changing of the System Type to any value supported by the device's firmware. This is consistent with the serial port interface tool commonly referred to as Grid Manager.
• System Type values are processed/verified by this tool as follows:
  • Leading and trailing blanks are silently removed.
  • Lower case characters are silently converted to upper case.
  • Valid characters are: 0123456789ABCDEF

WARNING:

• Setting the System Type to a value other than it's current setting will cause the SP(s) to restart... which will interrupt device access AND CAUSE THE LOSS OF ALL CURRENTLY BINDING LUNS!!!

SEE ALSO:

• AutoTrespassArray
• SystemCache

Test Unit Ready

DESCRIPTION:

The Test Unit Ready command allows you to test lun and disk readiness, through the issuance of SCSI TEST UNIT READY commands.

SCSI TEST UNIT READY commands will be attempted for all luns and disks reported by the Cxx00 Array device. However, the SCSI TEST UNIT READY command is not necessarily supported for all lun and disk states. A given command may/will be unsuccessful (firmware revision dependent) when issued to a:

• Lun which is binding (not fully bound).
• Lun which is bound as a Hot Spare.
• Lun which is inaccessible to the SP (example: lun is owned by peer SP and AutoTrespassArray>auto-trespass is off).
• Disk which is bound as a Hot Spare lun and is currently replacing a failed disk.

NOTE:

• Access to luns is Operating System, device firmware and device command dependent (example: SCSI-2 supports only luns 0-7).
• Supported capability of the SCSI TEST UNIT READY command is SP firmware revision dependent. Commands which are unsuccessful under one firmware revision may succeed under another revision.

SEE ALSO:

• Command Output Heading
• AutoTrespassArray
• ReadDisks
• ReadLuns
• VerifyDisks
• VerifyLuns

Verify Disks

DESCRIPTION:

The Verify Disks command allows you to verify data on disks through the issuance of SCSI Verify commands, which requests that the target verify the data written on the medium (typically performed by using checksum information). The data is NOT transferred to the host.

The following levels of verify granularity are supported (subject to restrictions in "NOTE:" below):

ALL disks, ALL blocks:

Verify all blocks of all disks.

SELECTED disks, ALL blocks:

Verify all blocks of selected disks.

SELECTED disks, SPECIFIED blocks:

Verify user specified blocks of user selected disks.

NOTE:

• Access to disks participating in active Hot Spare operations is NOT supported by the Cxx00 Array device. Inaccessible disks will be excluded from the command's disk selection list(s).
• Verifying (large amounts of) data can require a considerable amount of time. As a means of providing progress status, a 'heartbeat' message is given approximately every 60 seconds (when appropriate to do so).

SEE ALSO:

• ReadDisks
• ReadLuns
• TestUnitReady"
• VerifyLuns

Verify Luns

DESCRIPTION:

The Verify Luns command allows you to verify data on luns through the issuance of SCSI Verify commands, which requests that the target verify the data written on the medium (typically performed by using checksum information). The data is NOT transferred to the host.

The following levels of verify granularity are supported (subject to restrictions in "NOTE:" below):

ALL luns, ALL blocks:

Verify all blocks of all luns.

SELECTED luns, ALL blocks:

Verify all blocks of selected luns.

SELECTED luns, SPECIFIED blocks:

Verify user specified blocks of user selected luns.

NOTE:

• Access to luns is Operating System, device firmware and device command dependent (example: SCSI-2 supports only luns 0-7). Inaccessible luns will be excluded from the command's lun selection list(s).
• Verify access is supported only to fully bound, non Hot Spare luns which are accessible from the current SP. Inaccessible luns will be excluded from the command's lun selection list(s).
• Verifying (large amounts of) data can require a considerable amount of time. As a means of providing progress status, a 'heartbeat' message is given approximately every 60 seconds (when appropriate to do so).

SEE ALSO:

• ReadDisks
• ReadLuns
• TestUnitReady
• VerifyDisks

Unbind Luns

DESCRIPTION:

The Unbind Luns command allows you to unbind disks that are currently bound as a logical unit (lun). The logical unit is 'deleted' (ALL DATA IS LOST) and the disks that were part of the lun are then available for subsequent BindLun operations.

To be unbindable, a lun must:

• Be fully bound (not currently binding).
• Be currently owned by the SP through which the unbind is being attempted, UNLESS:
  • The lun is a Hot Spare, or
  • The SP through which the unbind is being attempted is the only functional SP in the device.
• Not be a Hot Spare lun currently replacing a failed disk in another lun.

NOTE:

• Access to luns is Operating System, device firmware and device command dependent (example: SCSI-2 supports only luns 0-7). This can inhibit the discovery of lun ownership, bind type and Hot Spare information, which affects the ability to unbind a lun. When the discovery of such information is inhibited, the lun will be included in the unbind lun selection list even though the information has not been determined. An unbind attempt can then be attempted, but it may be unsuccessful. If this approach were not taken, this tool would not permit an unbind lun attempt for such luns from either SP.

WARNING:

• Unbinding a lun results in LOSS OF ALL DATA on that lun. Be VERY certain that you want to unbind the lun you are unbinding.

SEE ALSO:

• BindLun

View Unsolicited Log

DESCRIPTION:

The View Unsolicited Log commands allow you to view an SP's Unsolicited Event Log.

Unsolicited Event Log entries can include events which are 'normal' (example: BBU self-test) as well as events which are more 'significant' (example: disk failure). Typically, normal events have an event code value which is numerically less than significant events. To aid the user in viewing events which are considered more significant, limited filtering capabilities are supported (see also "NOTE:" below):

Command

Function

Event Codes: All

Display all log entries.

Event Codes: >= 0x800

Display only log entries with event codes >= 0x800.

Event Codes: >= 0x900

Display only log entries with event codes >= 0x900.

Event Codes: >= 0xA00

Display only log entries with event codes >= 0xA00.

Log information is displayed in column format, and includes:

Column

Description

Rec#

The record number of the log entry within the SP's unsolicited event log.

ArryDate

The date on which the log entry was made (if available).

ArryTime

The time at which the log entry was made (if available).

Fru

The field replaceable unit to which the log entry pertains.

Event

The event code of the log entry.

ExSt

The extended status code of the log entry.

Description

A textual description of the log entry.

NOTE:

• Records are displayed in ascending sequence as received from the SP, with older entries displayed before newer entries. If filtering is applied (example: Event Codes: >= 0x900), record numbering will not necessarily be sequential.
• Additional filtering of log entries is possible by saving the log entries to a file and then using available system applications (example: awk, grep, sed).

SEE ALSO:

• Command Output Heading
• ClearUnsolicitedLog

/ Diagnostics HOME