HP OpenVMS System Management Utilities Reference Manual

MONITOR VECTOR

The MONITOR VECTOR command displays the number of 10-millisecond clock ticks per second in which one or more vector consumers have been scheduled on each currently configured vector processor in the system.

Format

MONITOR VECTOR

Command Qualifiers

/qualifier[,...]
One or more qualifiers as described in the Command Qualifier Descriptions section.

Classname Qualifiers

/ALL
Specifies that a table of all available statistics (current, average, minimum, and maximum) is to be included in the display and summary output. For summary output, this qualifier is the default for all classes; otherwise, it is the default for all classes except CLUSTER, MODES, PROCESSES, STATES, SYSTEM, and VECTOR.
/AVERAGE
Specifies that a bar graph of average statistics is to be included in the display and summary outputs.
/CURRENT
Specifies that a bar graph of current statistics is to be included in the display and summary outputs. The /CURRENT qualifier is the default for the CLUSTER, MODES, STATES, SYSTEM, and VECTOR classes.
/MAXIMUM
Specifies that a bar graph of maximum statistics is to be included in the display and summary outputs.
/MINIMUM
Specifies that a bar graph of minimum statistics is to be included in the display and summary outputs.

Description

The MONITOR VECTOR command displays the number of 10-millisecond clock ticks per second in which one or more vector consumers have been scheduled on each currently configured vector processor in the system. Because the operating system schedules vector consumers only on those processors identified as "vector present," the VECTOR class output never displays vector CPU time for those processors that are "vector absent."
Note that, because vector consumers can use either the vector CPU, the scalar CPU, or both components of a vector-present processor, the vector CPU time in the VECTOR class display is not a strict measure of the actual usage of the processor's vector CPU component. Rather, it indicates the time during which a scheduled vector consumer has reserved both vector CPU and scalar CPU components of the vector-present processor for its own exclusive use.
The VECTOR class consists of the data item Vector Scheduled Rate, which is represented by a display of statistics that show the rates of 10-millisecond clock ticks per second during which vector consumers have been scheduled on each vector-present CPU.

Example

MONITOR>  MONITOR VECTOR
 
 



  
    
      

       
  
 
  
                           OpenVMS Monitor Utility 
                          VECTOR PROCESSOR STATISTICS 
              +-----+             on node SAMPLE 
              | CUR |          12-JUN-2003  22:52:42 
              +-----+ 
 Vector Consumers Scheduled          0         25        50        75      100 
                                     + - - - - + - - - - + - - - - + - - - - -+ 
 Vector Present CPU ID  0          13|***** 
 Vector Absent  CPU ID  1            | 
 Vector Absent  CPU ID  2            | 
 Vector Present CPU ID  4          58|********************** 
                                     |         |         |         |          | 
                                     |         |         |         |          | 
                                     |         |         |         |          | 
                                     |         |         |         |          | 
                                     |         |         |         |          | 
                                     |         |         |         |          | 
                                     + - - - - + - - - - + - - - - + - - - - -+

This example shows the VECTOR class display for a multiprocessing system containing two vector-present processors, CPU 0 and CPU 4. Displayed statistics represent rates of 10-millisecond clock ticks per second. For an average of 13 ticks per second over the last collection interval, vector consumers have been scheduled on CPU 0. For an average of 58 ticks per second over the last collection interval, vector consumers have been scheduled on CPU 4.

SET DEFAULT

The SET DEFAULT command sets command qualifier, classname parameter, and classname qualifier defaults for the MONITOR command. Each SET DEFAULT command sets only the command qualifiers you specify, but replaces the entire set of classname parameters and classname qualifiers. All qualifiers and class names are identical to those for the MONITOR command.

Format

SET DEFAULT [/qualifier[,...]] classname[,...] [/qualifier[,...]]

Parameters

classname[,...]
Specifies one or more class names.

Command Qualifiers

/qualifier[,...]
One or more command qualifiers as described in the Command Qualifier Descriptions section.

Classname Qualifiers

/qualifier[,...]
One or more classname qualifiers.

Description

Command and classname qualifiers are identical to those for the MONITOR classname commands.

Example


MONITOR> SET DEFAULT /INTERVAL=10 PAGE/AVERAGE+IO/MAXIMUM /NODE=(LARRY,MOE,CURLEY)

The command in this example selects PAGE and IO as the default classes for the MONITOR command and specifies an interval of 10 seconds for the statistics display. The command specifies that AVERAGE statistics be displayed for the PAGE class, and that MAXIMUM statistics be displayed for the IO class. Finally, the command requests that data be collected on nodes LARRY, MOE, and CURLEY. After establishing these defaults, you can enter the MONITOR command without any qualifiers or parameters to display the requested information.

SHOW DEFAULT

The SHOW DEFAULT command displays the defaults established by the SET DEFAULT command.

Format

SHOW DEFAULT

Parameters

None.

Qualifiers

None.

Description

The SHOW DEFAULT command verifies the defaults you have set with the SET DEFAULT command.

Example

MONITOR> SHOW DEFAULT

/BEGINNING = current time /INTERVAL = 10 /ENDING = indefinite /VIEWING_TIME = 10 /FLUSH_INTERVAL = 300 /NOINPUT /NORECORD /DISPLAY = SYS$OUTPUT:.; /NOSUMMARY /NOFILENAME /NOCOMMENT Classes: PAGE/AVERAGE IO/MAXIMUM Nodes: LARRY MOE CURLEY

The command in this example displays the defaults specified by the previous SET DEFAULT command.

Chapter 17
MSA Utility

This chapter contains information about the MSA utility.

17.1 MSA Utility Usage Summary

The MSA utility is an OpenVMS system management tool for configuring and managing the following controllers:

HP StorageWorks Smart Array Family of Storage Host Bus Adapters (5300 series, 6400 series, P400, P410i, P411, P700, and P800 with Native Command Queuing (NCQ) Firmware)
HP StorageWorks Modular Smart Array Family of Storage Controllers (MSA1000 and MSA1500)
Support for SB40c blade storage and the disk numbering changes

These controllers connect to HP StorageWorks Modular Smart Array storage array systems, and to Integrity servers internal SCSI or SAS drives.

17.1.1 Required Privileges

You must have the following privileges to run the MSA utility:

NETMBX, TMPMBX, SYSPRV, DIAGNOSE, PHY_IO.

To start the MSA utility, enter the following command at the DCL command prompt ($):

$ RUN SYS$SYSTEM:MSA$UTIL

The MSA utility returns the following prompt:

MSA>

At the MSA prompt, you can enter any MSA utility command described in the following sections.

17.1.2 Restrictions

The MSA Utility has the following restrictions:

The MSA_UTIL command SHOW CONNECTIONS is not applicable to or supported on the HP StorageWorks Smart Array Controller.
EXTEND, MIGRATE, and EXPAND commands on Smart Array systems will fail if the controller cache is bad or the cache battery is less than 75%. These commands work on controllers that are designed to support volume expansion by using disk drives for backing up expand data stripe. This is in the absence of battery-backed memory on the controller.
RAID units that have spare disks (RAID 1, RAID 5, and so on) cannot be migrated to RAID 0 or JBOD units.
Multiple-capacity disks can be used by specifying the /SIZE qualifier. The maximum value of size specified with the /SIZE qualifier should be the size available on the disk with the lowest capacity.

17.2 MSA Utility Commands

The following sections describe MSA utility commands and provide examples of their use. Note that some qualifiers are shown as abbreviated in the examples.

ACCEPT UNIT

Changes the state of the unit back to VOLUME_OK when all drives of a previously failed unit are in working order.
This command accepts media exchange on a unit marked as failed.

Note
The ACCEPT UNIT command resets the status of all failed units to VOLUME_OK.

Format

ACCEPT UNIT <#>
where # represents the unit number.

Example


MSA> ACCEPT UNIT 2

ADD UNIT

Creates units (logical storage units that comprise one or more hard drives).

Format

ADD UNIT <unit_n> / <qualifiers> unit_n

Parameters

unit_n
The unit number can range from 0-31.

Note

Any two or a combination of all the following qualifiers cannot be used in conjunction with each other.

Qualifiers

/ADG
Specifies the RAID type for the unit as Advanced Data Guard (ADG).
/CACHE
Determines whether the controller's cache must be used for the UNIT. Caching is ON by default. To disable caching, use a /NOCACHE qualifier with SET UNIT or ADD UNIT commands.
/DISK
Specifies the disk numbers to be used to form the unit. Enclose multiple disks in parentheses. Use the following format:
/DISK=(disk-numbers[,...])
/IDENTIFIER
User-defined identifier for the unit. This identifier is used by OpenVMS to name the device. The value of the identifier n is between 1 and 9999. Use the following format:
/IDENTIFIER= n
Note
The /IDENTIFIER qualifier is not required for Smart Array controllers.

/JBOD
Specifies the RAID type as JBOD. Synonymous with RAID 0.
/PARTITION
Specifies the partition number to be used for a given unit. The first unit that is created on a disk/disk group is automatically assigned the partition number 0. Units that are subsequently created on this disk/disk group must be created with sequential partition numbers. Use the following format:
/PARTITION=(partition_number)
/RAID_LEVEL
Specifies the RAID type of the unit. Supported values for this qualifier are 0 (data striping), 1 (data mirroring), 5 (data stripping with striped parity), 50 (data stripping with parity), and 60 (data stripping with parity).
Use the following format:
/RAID=[(0 | 1 | 5 | 50 | 60)]
/SIZE
Specifies the size of the unit. If the size qualifier is not specified, the size defaults to the maximum capacity of the disks depending on the RAID level, as shown in the following example:
/SIZE=#(GB | MB | KB | %)
/SPARE
Specifies the disk numbers to be used as spare disks. Enclose multiple disks in parentheses. Assigning a spare disk to an unit in a drive group assigns the spare disk to all the configured units in the drive group.
If a unit is created on a disk group to which a spare disk is assigned, then the spare disk is configured to the new unit (if it is not a RAID 0 unit). One spare disk can be assigned to multiple drive groups.
Ensure that the size of the spare disk is equal at least to the size of the smallest drive in the drive group. Use the following format:
/SPARE=(disk_number[,...])
/STRIPE_SIZE
Specifies the stripe size for a given RAID volume. Stripe size must be one of the following values: 8, 16, 32, 64, 128, or 256. Raid 5 and ADG are limited to a maximum 64 KB stripes. RAID 0 and 1 default to 128 KB stripes, and RAID 5 and ADG default to 16 KB stripes. Use the following format:
/STRIPE_SIZE=(stripe_size)
/VERBOSE
Provides logging that can be interpreted by engineering.
restrictions
Any two or a combination of all the following qualifiers cannot be used in conjunction with each other.
/RAID_LEVEL, /JBOD, /ADG
Examples
#1
MSA> ADD UNIT 2
This command creates unit 2.
#2
MSA> ADD UNIT 3/ID=1003/DISK=103/JBOD/PARTITION=0/SIZE=8GB MSA> ADD UNIT 4/ID=1004/DISK=103/JBOD/PARTITION=1/SIZE=10GB MSA> ADD UNIT 5/ID=1005/DISK=103/JBOD/PARTITION=2/SIZE=8GB
These commands create three units on disk 103. Notice that the partition numbers are provided in sequential order on the same disk/disk group.
#3
MSA> ADD UNIT 3/ID=1003/DISK=103/JBOD/PARTITION=0/SIZE=8GB MSA> ADD UNIT 4/ID=1004/DISK=103/JBOD/PARTITION=2/SIZE=10GB
In this command sequence, assume that there is no unit with partition number 1 on this disk, the creation of unit 4 will fail because the unit is assigned the partition number 2 and the assignment is not in sequential order.

#1
MSA> ADD UNIT 2

#2
MSA> ADD UNIT 3/ID=1003/DISK=103/JBOD/PARTITION=0/SIZE=8GB MSA> ADD UNIT 4/ID=1004/DISK=103/JBOD/PARTITION=1/SIZE=10GB MSA> ADD UNIT 5/ID=1005/DISK=103/JBOD/PARTITION=2/SIZE=8GB

#3
MSA> ADD UNIT 3/ID=1003/DISK=103/JBOD/PARTITION=0/SIZE=8GB MSA> ADD UNIT 4/ID=1004/DISK=103/JBOD/PARTITION=2/SIZE=10GB

DELETE UNIT

Delete units from the drive. Regardless, whether the disk is mounted on OpenVMS, you are prompted for confirmation before proceeding to delete the selected unit.
For example, if the disk is mounted on an OpenVMS node, in addition to the prompting for confirmation, you are informed that the disk is mounted.

Note
After a unit is deleted, its unit number remains unused until manually assigned to a new unit.
Unit numbers are not automatically reassigned when a unit is deleted.
If more than one unit has been created on a disk/disk group, only the last created unit can be deleted.
Be sure to maintain a record of the unit numbers and the order in which they are created on a disk/disk group.

Format

DELETE UNIT <unit_n> / <qualifiers> unit_n

Parameters

unit_n
The unit number can range from 0-31.

Qualifiers

/VERBOSE
Provides logging that can be interpreted by engineering.
/NOCONFIRM
Allows the specified unit to be deleted without prompting for confirmation.

Example


MSA> DELETE UNIT 4/NOCONFIRM

In this example, unit 4 is the unit to be deleted. This is the same number that is given to the unit when it was created using the ADD UNIT command. The /NOCONFIRM qualifier deletes unit 4 without prompting for confirmation.

EXIT

Exits the MSA$UTIL program.

FLASH FIRMWARE

Updates the firmware of a given controller. Specify the firmware file name to be used.

Format

FLASH FIRMWARE <firmware-file-name> / <qualifiers> firmware-file-name

Parameters

firmware-file-name

Qualifiers

/VERBOSE
Provides logging that can be interpreted by engineering.

HELP

Describes all currently supported MSA$UTIL commands, their parameters, and their qualifiers. Use the following format, where verb is the specific description.

Format

HELP <verb> verb

Parameters

verb

Example


MSA> Help ADD ADD UNIT ADD UNIT is used to create UNITs (logical storage units comprising one or more hard drives). Format: ADD UNIT <unit_n> <qualifiers> Parameters Qualifiers Examples

This command describes the ADD command and its parameters.

LOCATE

Causes the LEDs of the requested drives to blink. These LEDs are visible from the front of the attached storage enclosures.

Note
If time limit is not included with the LOCATE command, the LEDs blink for 30 seconds. In some cases, the LEDs may remain steady without blinking. Furthermore, the LOCATE command does not work from a STANDBY CONTROLLER.

Format

LOCATE/TIME=xxx <parameters> / <qualifiers> ALL

Parameters

ALL

Causes all drives connected to the MSA storage subsystem to flash.
BOX

The LOCATE BOX command causes the disks connected to the specified box/enclosure number to flash.
BUS bus-number

Causes the disks connected to the specified bus to flash.
CANCEL

Cancels the current locate operation.
DISK disk-number

The LOCATE DISKS command makes the specified drive to flash. Disks are identified by their corresponding SCSI bus and SCSI IDs for all the controllers. For SAS controllers, internally connected disks are numbered based on their bay numbers and externally connected disks are numbered based on a combination of their box number and bay number as "disk_n = box number *100 + bay number".

Note
The disk numbers for the existing disks can be obtained using the SHOW DISKS command.

UNIT unit-number

Causes the disks configured on the specified unit to flash.

Qualifiers

/TIME=time
Specifies the number of seconds the disk's LED should flash. This is an optional qualifier whose default is 30 seconds.
/VERBOSE
Provides logging that can be interpreted by engineering.

Examples

#1
MSA> LOCATE ALL

This command locates all drives attached to the storage enclosure.

#2
MSA> LOCATE BUS 1

This command locates all drives SCSI bus 1.

#3
MSA> LOCATE UNIT 1

This command locates all drives in unit 1.

#4
MSA> LOCATE DISK 102

This command locates drive 102.

#5
MSA> LOCATE BOX 1

This command locates and flashes all the drives in the specified BOX 1.

Contents

Index

HP OpenVMS System Management Utilities Reference Manual

MONITOR VECTOR

Format

Command Qualifiers

/qualifier[,...]

Classname Qualifiers

/ALL

/AVERAGE

/CURRENT

/MAXIMUM

/MINIMUM

Description

Example

SET DEFAULT

Format

Parameters

classname[,...]

Command Qualifiers

/qualifier[,...]

Classname Qualifiers

/qualifier[,...]

Description

Example

SHOW DEFAULT

Format

Parameters

Qualifiers

Description

Example

Chapter 17MSA Utility

17.1 MSA Utility Usage Summary

17.1.1 Required Privileges

17.1.2 Restrictions

17.2 MSA Utility Commands

ACCEPT UNIT

Format

Example

ADD UNIT

Format

Parameters

unit_n

Qualifiers

/ADG

/CACHE

/DISK

/IDENTIFIER

/JBOD

/PARTITION

/RAID_LEVEL

/SIZE

/SPARE

/STRIPE_SIZE

/VERBOSE

restrictions

Examples

DELETE UNIT

Format

Parameters

unit_n

Qualifiers

/VERBOSE

/NOCONFIRM

Example

EXIT

FLASH FIRMWARE

Format

Parameters

firmware-file-name

Qualifiers

/VERBOSE

HELP

Format

Parameters

verb

Example

LOCATE

Format

Parameters

ALL

BOX

Chapter 17
MSA Utility