For more information on storage subsystem logical or physical components and their properties, see the Subsystem Management Window online help.
If you want to...
|
Use this command and parameters...
|
set properties of the storage subsystem
Back to the top
|
Base Command and Required Parameters
|
set storagesubsystem
|
Additional Parameters You Can Use When Setting Storage Subsystem Properties
Back to the top
|
- set storagesubsystem batteryInstallDate = true (battery age is set to 0 days - for 4884, 4774, or 4766 controllers only)
Caution: To set the battery age to 0 days when you replace the controller-specific battery in 2772 storage subsystems, use the set controller [controller spec] batteryInstallDate=true command instead, where
[controller spec] = a or b (a = controller in slot A, and b = controller in slot B)
If you use the set storagesubsystem batteryInstallDate=true command with the 2772 controller battery, you will get an error message.
- cacheBlockSize = any positive integer value (normally 4 or 16.) This value is in KB and is checked against the supported values provided by the controller at run time. If the value entered is not valid, the controller will return a list of appropriate values.
- cacheFlushStart = 0 to 100 (Indicates the point in the cache memory area, in percentage, that cache flushing should start.)
- cacheFlushStop = 0 to 100 (Indicates the point in the cache memory area, in percentage, that cache flushing should stop.)
- mediaScanRate = number indicating the duration (in days) over which to run the media scan. Current range is 1 to 30 days. If you want to disable the media scan, use the term disabled instead of a 1 to 30 value. You must also enable the media scan parameter and optionally, the redundancy check parameter on each individual logical drive on which you want to run the media scan.
- userLabel = any string up to 30 characters. You must enclose the string in double quotes.
- resetConfiguration = true (Configuration on the storage subsystem is reset back to a default configuration. Attention: Use with extreme caution!)
- timeOfDay = true (Synchronizes the clocks on the controllers in the storage subsystem with the management station.)
- clearEventLog = true (all events stored in the event log are deleted. Attention: Use with extreme caution!)
- password = "any double-quoted string up to 30 characters." Note that the password characters are not hidden (masked).
- RLSBaseline = CurrentTime (Sets the Read Link Status baseline to the current time.)
- defaultHostType = "hostTypeIdentifier" (Sets the default host type for the storage subsystem, based on a hostTypeIdentifier. To obtain a list of available hostTypeIdentifiers, use the show storagesubsystem hostTypeTable; command.)
|
Examples
Back to the top
|
Command statement:
set storagesubsystem userLabel="Engineering" cacheFlushStart=85 cacheFlushStop=15;
Execution results:
- The storage subsystem is renamed to "Engineering."
- The cache flush start value is set to 85 percent.
- The cache flush stop value is set to 15 percent.
Command statement:
set storagesubsystem defaultHostType="Linux";
Execution results:
- The storage subsystem default host type is changed to "Linux".
|
|
set properties of a controller
Back to the top
|
Base Command and Required Parameters
|
set controller [controller-spec];
where:
[controller spec] = a or b (a = controller in slot A, and b = controller in slot B)
|
Additional Parameters You Can Use When Setting the Properties of a Controller
Back to the top
|
- mode = active
- availability = online or offline
- batteryInstallDate = true (battery age is set to 0 days - for the controller-specific battery in 2772 controllers only)
Caution: To set the battery age to 0 days when you replace the battery canister in 4884, 4774, or 4766 storage subsystems, use the set storagesubsystem batteryInstallDate=true command instead.
If you use the set controller [controller spec] batteryInstallDate=true command with the battery canisters in a 4774, 4884, or 4766 storage subsystem, you will get an error message.
|
Example
Back to the top
|
Command Statement:
set controller[a] mode=active;
Execution Result:
The controller in slot A is set to the active mode.
|
|
Change NVSRAM settings
Back to the top
|
Base Command and Required Parameters
|
set controller [controller-spec];
where:
[controller spec] = a or b (a = controller in slot A, and b = controller in slot B)
Caution: Using the GlobalNVSRAMByte, HostNVSRAMByte or NVSRAMByte parameters incorrectly could cause your storage subsystem to malfunction. The following procedure is provided as an example and should be used only under the guidance of technical support.
GlobalNVSRAMByte[nvsram-offset] = mask, value;
where[nvsram-offset] = 0 to 0x3F , mask = 0x00 to 0xFF, and value = 0 to 255 (0x00 to 0xFF).
HostNVSRAMByte [host-type, nvsram-offset] = mask, value;
where[host-type] = 0 to 15,[nvsram-offset] = 0 to 0x3F ,mask = 0x00 to 0xFF, and value = 0 to 255 (0x00 to 0xFF).
NVSRAMByte [nvsram-offset] = mask, value
To set specific bits within an NVSRAMByte, use the parameter as follows:
- The mask and value are used to set specific bits in an NVSRAMByte and leave others unchanged. For each bit turned on (set to 1) in the "mask," the corresponding bit in the NVSRAMByte is set to match the value of that bit in "value." For each bit turned off (set to 0) in the mask, the original NVSRAM bit will be unchanged, regardless of the value for that bit.
Caution: The mask is optional, however if a mask is not specified, a mask of 0xff is assumed. That is, all bits in the value are used. If you do not use a mask, be sure that all bits in the value are set correctly. - Use a range of 0 to 0x3F for [nvsram-offset]. Choose a number for "mask" and "value" within a hexadecimal range of 0x00 to 0xFF.
- The binary equivalent of a hexadecimal parameter setting is used to set individual bits within the byte. For example, a hexadecimal setting of 0x80 corresponds to the binary number of 1000 0000.
- Using 0x80 for the mask setting will allow bit 7 in the byte to be modified (because the number in the bit 7 position is 1.) All other bits in the byte will be masked. (The mask values are set to 0.)
- To set the value for bit 7, choose a hexadecimal setting for "value" whose binary equivalent contains the desired value in the bit 7 position. (Any values in other bit positions are ignored, because the bits are masked.)
Notes:
- In this example, the bits are numbered from right to left starting with bit 0.
- If you want the NVSRAM in both controllers in a storage subsystem to match, you must run this command for each controller.
- The NVSRAMByte operation is provided to be backward compatible with older scripts. The operations GlobalNVSRAMByte and HostNVSRAMByte are now the preferred method to set user-configurable NVSRAM options.
|
Examples
Back to the top
|
Command Statement:
set controller[a] HostNVSRAMByte [0x2, 0x13]=0x1;
Execution Results:
- Host-specific NVSRAMByte 0x13 is set to 1 for host type 2 causing any commands received from the specific host while the controller is quiesced to be reported as Not Ready.
- Note: To determine which host will be affected by changing the NVSRAM settings use the show command to view the storage subsystem profile ("show storagesubsystem profile"). The Storage Partition table and NVSRAM Host Type Internal Definitions table will appear. Use the Host-Type Definitions table to relate the host-type index to a host-type label. Then, use the Storage Partition table to see which host types will be affected by the new NVSRAM settings.
- To determine the NVSRAM configuration offset definitions, refer to the Controller Interface Specification.
Command statement:
set controller[a] GlobalNVSRAMByte [0x30]=0x80,0x80;
Execution Result:
NVSRAM Bit 7 of offset 0x30 is set to 1, enabling the Audible Alarm feature.
Caution: Attempting to change a host-specific offset using this global offset will return an error.
|
|
set properties of an array
Back to the top
|
Base Command and Required Parameters
|
set array [array number];
where:
[array number]= the sequence number of the array, enclosed in square braces.
|
Additional Parameters You Can Use When Setting the Properties of an Array
Back to the top
|
owner = a or b
where a = controller in slot A and b = controller in slot B.
|
Example
Back to the top
|
Command statement
set array[3] owner=b;
Execution Result:
Array 3, and its associated components, are now owned by the controller in slot B.
|
|
set properties of a standard logical drive
Back to the top
|
Base Command and Required Parameters
|
set logicalDrive [logicaldrivelabel]
where:
[logicaldrivelabel] = the logical drive user label, enclosed in square braces
Important: If the logical drive label contains more than one word, white space, or any special character(s), then enclose the label in double quotes.
|
Additional Parameters You Can Use When Setting the Properties of a Standard Logical Drive
Back to the top
|
|
Example
Back to the top
|
Command statement:
set logicalDrive["Nova"] writeCacheEnabled=true mirrorEnabled=true;
Execution result:
The write cache and cache mirroring parameters are enabled on the logical drive named Nova.
|
|
set the properties of a FlashCopy logical drive
Back to the top
|
Base command and required parameters
|
set logicalDrive [logicaldrivelabel]
where:
[logicaldrivelabel] = the logical drive user label, enclosed in square braces
Important:
- If the logical drive label contains more than one word, white space, or any special character(s), then enclose the label in double quotes.
- This syntax is identical to that used when setting the properties of a standard logical drive. The controller firmware and script engine logic determines whether the logical drive specified is a standard or FlashCopy logical drive and responds to the command statement accordingly.
|
Additional Parameters You Can Use When Setting the Properties of a FlashCopy Logical Drive
Back to the top
|
- warningThresholdPercent = integer value of the repository full percentage threshold before you receive a warning. If you don't specify a value, 50% is used by default.
- repositoryFullPolicy = failBaseWrites or failFlashCopy. This value specifies the behavior of the controller when the repository logical drive fills up. If you don't specify a value, failFlashCopy is used by default.
- <userLabel> = any string up to 30 characters.
- Important:
- This new user label replaces the previous logical drive label.
- The string cannot contain a new line.
- You must surround the user label string with double quotes.
- Choose a unique user label for the logical drive, or you will receive an error message.
|
Example
Back to the top
|
Command statement:
set logicalDrive ["Nova-S1"] warningThresholdPercent=45;
Execution result:
You will receive a warning when the repository logical drive associated with the FlashCopy logical drive Nova-S1 reaches 45% full (and an error will be logged to the Event Log).
|
|
set performance monitor polling interval and number of samples
Back to the top
|
Base command and required parameters
|
set performanceMonitor interval=<interval> iterations=<iterations>
where:
<interval> = the polling interval, in seconds, for which you want to capture data
and
<iterations> = the number of samples that should be captured
Notes:
- Use this command when using the upload command to upload Performance Monitor statistics to a file. For more information, see Using the upload Command.
- If you use this command in the Script Editor, the polling interval and number of iterations you specify remain in effect until you close the storage management software (end your session). Then, the default polling interval of 10 seconds and one capture iteration goes back into effect.
- If you use the set command on the command line to specify a polling interval and the number of iterations, enter both the set command and the upload command in the same command string, separated by a semicolon and surrounded by quotes.
- Command line example: -c "set performanceMonitor interval=5 iterations=5;upload storagesubsystem file="June10.csv" content=performanceStats;"
|
Example
Back to the top
|
Command statements:
set performanceMonitor interval=5 iterations=5;
upload storagesubsystem file="June10.csv" content=performanceStats;
Execution results:
- Performance data is uploaded from the storage subsystem and placed in a comma-delimited text file, June10.csv, on the storage management station.
- Data for each logical drive, each controller, and a total for both controllers is captured for five different five second intervals and displayed in the file.
|
|
change the role of a primary or secondary logical drive
Back to the top
|
Base Command and Required Parameters
|
set logicalDrive [logicaldrivelabel] role=primary
or
set logicalDrive [logicaldrivelabel] role=secondary
where:
[logicaldrivelabel] = the logical drive user label, enclosed in square braces
and
<role> = primary or secondary
Important:
- If the logical drive label contains more than one word, white space, or any special character(s), then enclose the label in double quotes.
- When you set the logical drive to its new role (whether primary or secondary) the firmware will attempt to change both primary and secondary logical drive roles.
|
Example
Back to the top
|
Command statement:
set logicalDrive [east] role=primary;
or
set logicalDrive [west] role=secondary;
Execution results:
- The secondary logical drive [east] is promoted to primary; the former primary logical drive [west]is demoted to secondary
or
- The primary logical drive[west]is demoted to secondary: the former secondary logical drive [east]is promoted to primary.
|
|
assign or unassign a hot spare drive
Back to the top
|
Base Command and Required Parameters
|
set drive or drives [drive list] hotspare=true or false
where:
[drive list] = enclosureID, slotID of each drive, separated by a space and enclosed in square braces; and
hotspare = true (assign) or false (unassign)
|
Example
Back to the top
|
Command statement:
set drives [1,2 1,3] hotspare=true;
Execution results:
- The unassigned drive at enclosure 1, slot 2 is assigned as a hot spare drive.
- The unassigned drive at enclosure 1, slot 3 is assigned as a hot spare drive.
|
|
fail a drive
Back to the top
|
Base Command and Required Parameters
|
set drive [drive list] operationalState=failed;
where:
[drive list] is the form "X, Y" where X is the enclosure and Y is the slot number of the drive in question.
|
Example
Back to the top
|
Command statement:
set drive [1,2] operationalState=failed;
Execution results:
- This sets the drive in enclosure 1 to slot 2 to Failed status.
- The drive will display in the AMW physical view with a failed icon.
|
|
revive a failed drive
Back to the top
|
Base Command and Required Parameters
|
set drive [drive list] operationalState=optimal;
where:
[drive list] is the form "X, Y" where X is the enclosure and Y is the slot number of the drive in question.
|
Example
Back to the top
|
Command statement:
set drive [1,2] operationalState=optimal;
Execution results:
- This sets the failed drive in enclosure 1 to slot 2 back to optimal status.
- The drive will re-display in the AMW physical view with an optimal icon.
|
|