Jump to content United States-English
HP.com Home Products and Services Support and Drivers Solutions How to Buy
» Contact HP
More options
HP.com home
HP-UX 11i Version 1.5 Reference Volume 2, Section 1M: System Administration Commands > a

arraydsp(1M)

» 

Technical documentation

» Feedback
Content starts here

 » Table of Contents

 » Index

NAME

arraydsp — display the status and operating configuration of the disk array.

SYNOPSIS

arraydsp [-l [LUN] | -d | -c | -s | -v | -h | -a] [-V] [-S] [-?] array-id

arraydsp { -r stime etime | -m stime etime [ int] } [-V] [-S] [-?] array-id

arraydsp -i [-V] [-S] [-?]

arraydsp -R [-V] [-?]

DESCRIPTION

arraydsp displays status and configuration information for the disk array identified by array-id. Logical configuration, physical configuration, current status, and performance data can all be displayed using arraydsp. A list of the serial numbers of all the disk arrays recognized by the host can also be displayed.

The array-id used to address the disk array can be the disk array serial number, the character device file name of any LUN on the array (LUN 0 if no LUNs are created), or the alias text string assigned to the disk array.

Options

arraydsp supports the following options:

none

Display general information about the disk array. This includes product and vendor information, array state, and capacity usage.

-a

Display the information presented by the -l,-d,-c, -s,-v and -h options. This is a quick way of displaying all configuration and status information about the disk array. This option will display information for all LUNs.

-c

Display information for each controller installed in the disk array.

-d

Display information for all disks installed in the array.

-h

Display status information about the disk array hardware. This includes controller, power supply, and fan status.

-i

Display the serial number of all disk arrays currently connected to and recognized by the server. Because this option is device-independent, it does not use array-id .

-l [LUN]

Display information for the LUN identified by LUN. If LUN is not specified, display information for all LUNs on the disk array.

-m stime etime [ int ]

Display detailed performance metrics. These are the metrics on which the performance recommendations are based. Performance is analyzed over the period of time beginning at stime and ending at etime. A detailed description of the performance metrics is included later in this manual page.

The int (interval) value controls the resolution of the data display. Each interval increment equals 15 minutes, with a default of 4 (1 hour).

The format for entering time is mmddhhmm[yy]:

mm

Month (01-12)

dd

Day (01-31)

hh

Hour (00-23)

mm

Minute (00-59)

yy

Year (optional)

-r stime etime

Display recommendations for improving disk array performance. The recommendations are based on various performance metrics maintained by the disk array. Performance is analyzed over the period of time beginning at stime and ending at etime. See above for the format for entering time.

-R

Rescan for disk arrays. The host will scan for all supported disk arrays and update the current list. This may be useful if a new disk array has been added but does not yet show up in the array list. It is also useful if the state of the disk array has changed (for example, following a firmware update).

-s

Display general configuration information for the disk array. This includes the configuration settings that control the operation of the entire disk array.

-S

Raw output display. Data is output as a colon-delimited ASCII text string. Raw output format is near the end of this page.

-v

Display virtual information about the disk array. This includes the amount of capacity currently being used for RAID 0/1, and the amount of unallocated capacity.

-V

Verbose mode displays additional command execution, state, and/or status messages.

-?

Display extended usage message. This option overrides all others.

EXTERNAL INFLUENCES

Environment Variables

LC_MESSAGES determines the language in which messages are displayed. The current language settings can be checked with locale(1).

RETURN VALUE

arraydsp returns the following values:

0

Successful completion.

1

An error in execution (I/O, subsystem, security, etc.) occurred.

2

An error in command syntax occurred: for example, an unknown command-line option was passed.

3

Timeout in communication to server. May indicate ARMServer is not running.

DIAGNOSTICS

The following messages can be generated by arraydsp:

Usage: arraydsp [-l [LUN] | -d | -c | -s | -v | -h | -a | -r stime etime | -m stime etime [int]] [-V] [-?] <array-id>

  • An error in command syntax has occurred. Reenter the command with all necessary arguments.

Usage: arraydsp {-i | -R} [-V] [-?]

  • An error in command syntax has occurred. Reenter the command with all necessary arguments.

Usage: arraydsp -r stime etime | -m stime etime [int] array-id

  • The values entered for the performance analysis start and stop times are invalid. The format for entering the time is mmddhhmm[yy].

arraydsp: Arg out of range

  • One of the arguments has exceeded its maximum or minimum size, or is incorrect in form. Check the size and form of each argument.

arraydsp: Unknown argument

  • An invalid argument was specified. Check command usage.

arraydsp: No such file or directory

  • The specified array-id does not exist or does not identify a disk array LUN that is communicating with the system. Verify the correct array-id with ioscan(1M) or arraydsp(1M).

arraydsp: Error in command execution, <Additional Error Info>: <Error Info Decode>

  • The command failed due to a device error, an internal error, or a system error. The Additional Error Info and Error Info Decode fields will hold specifics about the failure and its cause.

arraydsp: Device was just powered-on or reset.

  • The command failed because the disk array has been powered-on or reset. Reissue the command and it should succeed.

EXAMPLES

Display general information about the disk array identified by device file /dev/rdsk/c2t0d0:

arraydsp /dev/rdsk/c2t0d0

Display information for LUN 2 on disk array serial number 00786b5c0000:

arraydsp -l 2 00786b5c0000

Display information for all LUNs on the disk array identified by alias AUTORAID4:

arraydsp -l AUTORAID4

Display information for all disks installed in disk array serial number 00786b5c0000:

arraydsp -d 00786b5c0000

List the serial numbers of all of the disk arrays recognized by the host:

arraydsp -i

Display performance recommendations for disk array serial number 00786b5c0000. Analyze performance for the time period from 8:00 AM to 5:00 PM (1700) on March 15.

arraydsp -r 03150800 03151700 00786b5c0000

Display performance metrics for disk array serial number 00786b5c0000. Analyze performance for the time period from 1200 PM to 6:00 PM (1800) on April 6. Use a display interval of 30 minutes.

arraydsp -m 04061200 04061800 2 00786b5c0000

PERFORMANCE METRICS

The following information describes the various performance metrics returned by the -m option.

Metric

Description

Drive Diff

Values (Typical/Limit): 0-1/>1

Indicates if the disks are properly distributed across the internal SCSI channels. If the disks are not installed properly, one of the SCSI channels may be handling more than its share of activity, reducing performance. Redistributing the disks will solve this problem.

Relocate Blocks

Values (Typical/Limit): 0.008/>0.07

Indicates how much data is being moved between RAID 0/1 and RAID 5. If too much data is being transferred between RAID 0/1 and RAID 5, performance declines.

Working Set

Values (Typical/Limit): 1/>1.1

Indicates the ratio of the write working set to the amount of RAID 0/1 space available. To maintain performance, the amount of RAID 0/1 space should equal or exceed the write working set (a value of 1 or less). A value greater than 1 indicates that the working set is larger than the available RAID 0/1 space. In this case, the disk array must service writes from RAID 5 space, which degrades performance.

Cache Utilization

Values (Typical/Limit): 0.1/0.2

Indicates how efficiently the write cache on the disk array controller is being utilized. If the write cache is consistently full, too many commands begin stacking up in the cache queue, resulting in decreased performance.

Disk Queue

Values (Typical/Limit): 2-4/>=10 (per disk)

Indicates the average number of transactions on all disk drives waiting in the internal disk SCSI queues. Too many commands in the queues decrease performance.

Concurrency

Values (Typical/Limit): >= drive count/< drive count

Indicates the number of internal simultaneous disk accesses the disk array is making. The disk array achieves optimum performance when it is accessing multiple disks at the same time, so some concurrency is desirable. Too low a value indicates that the host is not requesting enough concurrent I/Os to keep the disk array busy.

Cache Queue

Values (Typical/Limit): 0.05/>=0.32

Indicates the number of commands in the cache queue. An excessive number may reflect address conflicts in host I/Os, caused by repeated access to the same block(s) of data.

Host Queue

Values (Typical/Limit): 0/>32

Indicates the number of host commands waiting in the host queue. A problem here typically reflects another bottleneck further along in the controller data path. For example, if the cache queue is full, commands will stack up in the host queue waiting for the cache queue to empty. The counter does not show until 32 commands are in the queue.

Throughput

Values (Typical/Limit): Not Used

Indicates the average number of bytes per second being transferred over the SCSI channel. This metric reflects channel activity, and does not indicate any problems with the disk array.

I/O Rate

Values (Typical/Limit): Not Used

Indicates the average number of I/Os per second being serviced by the disk array. This metric reflects channel activity; it does not indicate problems with the disk array

RAW OUTPUT FORMAT

The contents of the raw output text string for each display option are listed here. Note that the raw output for the -a option comprises the individual strings displayed by the -l,-d,-c, -s,-v and -h options. For clarification when evaluating Boolean expressions, TRUE=1 and FALSE=0.

Option

Raw Output Description

none

D:HP:ProductID:ArraySN:ServerName:ArrayType:

MfgProdCode:PhysCapacity:LUNCapacity:ActiveSpareCapacity:

DiskNonIncludedCapacity:RedundantCapacity:

UnallocatedCapacity:<ArrayState>:<WarnInd>:<Alias>

The leading "D" is literal to identify this as a DEFAULT record. All capacities are in MB.

-c

C:<CntrlrID>:<CompState>:HP:ProductID:Primary:

BkplaneSlot:Address:SerNumber:PairedSerNum:

ControllerType:ProdRev:MfgProdCode:FirmwareRev:<arraySN>

The leading "C" is literal to identify this as a CONTROLLER record. Output will be displayed for each controller installed. If <CompState> is not "Good", information in the remaining fields will be undefined or absent.

-d

The following output is provided for each installed disk:

PD:<SlotID>:<DiskState>:Vendor:ProductID:Capacity: MaxBlkAddr:BlkLen:SerialNum:FwRev:SeqNum:VolSetSerNum:<arraySN>: RecoveryMapsPresent

The leading "PD" is literal to identify this as a PHYSICAL DISK record. The above will be displayed for each disk slot. For disks with a <DiskState> of NOT_PRESENT, the only field that will follow <DiskState> will be <arraySN>. "Capacity" is displayed in MB, rounded up to the nearest MB.

The following output is provided for each missing disk. A disk is missing if it is no longer accessible to the array (due to removal or failure) but is still required to maintain full redundancy. After the data on the missing disk is rebuilt, the disk is no longer required and is not considered missing.

MD:Vendor:ProductID:Capacity:MaxBlkAddr:BlkLen:

SerialNum:DiskIDNum:VolSetSerNum:<arraySN>

The leading "MD" is literal to identify this as a MISSING DISK record. The above will be displayed for each missing disk. "Capacity" is displayed in MB, rounded up to the nearest MB.

-h

One or more "component state records" will be displayed in the following format:

H:HP:ProductID:<CompID>:<nn>:<CntrlrID>:<CompState>:<arraySN>

H:HP:ProductID:<CompID>:<nn>:<CntrlrID>:<BattState>:<arraySN>

H:HP:ProductID:<CompID>:<nn>:<CntrlrID>:<SimmState>:<arraySN>

The leading "H" is literal to identify this as a HARDWARE record. "<CompID>" is the unique ID of the component. The CompIDs are interpreted as follows:

0 = Fans

1 = Power supplies

2 = Controllers

3 = RESERVED

4 = Controller X DRAM

5 = Controller X NVRAM

6 = Controller Y DRAM

7 = Controller Y DRAM

8 = Controller X batteries

9 = Controller Y batteries

Because there may be multiple components of type "<CompID>", the "<nn>" field further identifies the component. "<nn>" will always be 0 for a "<CompID>" = CONTROLLER.

The "<CntrlrID>" identifies the associated controller. If no association exists for this component with a controller, this field will be empty. "<CompState>" and "<BattState>" indicate the state of the component or battery, respectively.

-i

The following single-line output includes a separate field (xxxxxxxxxx) for each disk array identified:

I:xxxxxxxxxx:xxxxxxxxxx

The leading "I" is literal to identify this as an Identify record.

-l

L:HP:ProductID:LunNumber:Present:MaxBlockAddr:

BlockLength:<arraySN>:<Alias>

The leading "L" is literal to identify this as a LUN record. "Present" is a Boolean, TRUE if the LUN is configured, FALSE otherwise. If a LUN is not specified, the above will be displayed for all LUNs.

-m

PM:HP:ProductID:<requestedStime>:

<requestedEtime>:<actualStime>:<actualEtime>:<interval>:<arraySN> :<PerfMetricId>:<nn>:<nn>: ... :<PerfMetricId>:<nn>:<nn>: ... :<PerfMetricId>:<nn>:<nn>: ...

The leading "PM" is literal to identify this as a PERFORMANCE METRIC record.

-r

PR:HP:ProductID:<stime>:<etime>:

<Recommendation1>:<Recommendation2>:...

The leading "PR" is literal to identify this as a PERFORMANCE RECOMMENDATIONS record.

-s

S:HP:ProductID:VolSetPartition:FmtPatternFill:

AutoRebuild:AutoInclude:Parity:SDTR:WDTR:TermPwr:UnitAtn: ActiveSpare:LogFullWarn:WrtCache:RdCache:RebuildPri: CapDepThresh:WrtWrkSetInt:SubsysTypeID: Language:CntXaddr:CntYaddr:Rebuilding:RebuildPercentage: Balancing:Optimizing:<ArrayState>:<WarnInd>:DRR:<ArraySN>: LUNCreateLimit:MaxLUNCreateLimit:SecContOffline:VeryEarlyBusy QueueFullThreshold:MaxQueueFullThreshold: DisableSingleControllerWarning:LockWriteCacheOn: DisableNVRAMonWCEfalse:DisableNVRAMonSingleController: DisableNVRAMonUPSabsent:<ForceUnitAccessResponse>: DisableReadHits:RecoveryInProgress:<RecoveryProgress>: <ResiliencyThreshold>

The leading "S" is literal to identify this as an ARRAY STATE record. "<WarningState>" will be a hexadecimal number representing the "Warning Indications" field returned by the "Check Array State" command, which is described in the "HP XLR1200 Advanced Disk Array SCSI Interface Specification" (5010-3128).

-v

V:HP:ProductID:Raid1Blocks:Raid1BlockSize:<arraySN>

The leading "V" is literal to identify this as a VIRTUAL record.

DEPENDENCIES

ARMServer must be running to execute this command. See ARMServer(1M).

SECURITY CONFIGURATION

This command is modified for all security configurations.

Security Behavior/Restrictions

Use of this command is restricted to authorized users only.

Command Authorizations

This command requires the sysadmin authorization to successfully execute.

Privileges

The command has been modified to support least privilege. The potential privileges possessed by the command and their uses include:

allowdacread

This privilege is raised to provide discretionary read access to the devices.

allowmacread

This privilege is raised to provide mandatory read access to the devices.

filesysops

This privilege is raised to allow the mknod(2) system call to succeed.

AUTHOR

arraydsp was developed by HP.

Printable version
Privacy statement Using this site means you accept its terms Feedback to webmaster
© 1983-2001 Hewlett-Packard Development Company, L.P.