Asset ID: |
1-71-1007113.1 |
Update Date: | 2010-10-05 |
Keywords: | |
Solution Type
Technical Instruction Sure
Solution
1007113.1
:
Validating Sun StorEdge[TM] 6920 Volume Modification
Related Categories |
- GCS>Sun Microsystems>Storage - Disk>Modular Disk - 6xxx Arrays
|
PreviouslyPublishedAs
209805
DescriptionThe purpose of this document is to provide basic steps for volume
modification for the 6920 array, via the Browser User Interface(BUI) or
sscs Command Line Interface(CLI).
Content will be limited to a basic usage using the CLI or BUI interfaces
for modifying volumes, and provide help with some usage failure scenarios
for this activity. Consider reviewing some of the following documents if you
are looking to perform actions beyond the scope of this document:
Steps to FollowValidating Sun StorEdge[TM] 6920 Volume Modification:
A. Start By Planning
Volume layout planning and considerations should be reviewed by
answering the following questions before modifying your volume:
- Will you be Growing the size of(Expand) your volume?
- Will you be renaming your volume?
- Will you be changing the volume description?
- Will you be altering the snapshot configuration for your volume?
- Will you be altering the mirror configuration for your volume?
After answering these questions please review the contents of the Best Practices for the Sun StorEdge 6920 System, Version 3.0.1, and identify that you are prepared with at least:
- The size of the volume after expanding
- The new name of the volume
- The new description of the volume
- Available capacity in pool for volume being modified
- If you are altering a snapshot, snapshot reserve, or parent volume, reference document <Document: 1007163.1> Validating Sun StorEdge[TM] 6920 Snapshot Modification
- If you are altering the mirror configuration for your volume, reference document <Document: 1002715.1> Validating Sun StorEdge[TM] 6920 Mirror Volume Modification
If all the information above is provided, continue to Step B
B. Validate 6920 Baseline Release
- Click on the Configuration Services or Common Array Manager(3.2.0.38) Link.
- Click on the Version button in the upper right hand corner
- Note the Version: number in the pop-up window, and take the following action.
- If the Version is NOT 3.0.1.26 or 3.2.0.38, ensure that the volume is not mapped. Reference <Document: 1009974.1> Validating Volume State and Details on a Sun StorEdge[TM] 6920 and Sun Alert <Document: 1000791.1>
- If the version is 3.0.1.26 or 3.2.0.38, continue to Step C.
C. Basic Usage of Browser or SSCS Interfaces for Changing the Name and Description
SSCS
The sscs usage for basic volume modification is as follows.
modify [-p|--pool <string>] [-S|--sdomain <string>] [-N|--new-name <string>] [-d|--description <string>] volume <string>
This CLI will change:
- The volume name
- The volume description
NOTE1: The Storage Domain is assumed to be DEFAULT when it is not specified by the -S switch in the usage
BUI
Volume modification for the BUI interface of the 6920 is completed as follows:
- Click on the Configuration Services or Common Array Manager(3.2.0.38) Link.
- Click on the Volume Tab or Volume Menu Tree
- Click on the Volume Name that you wish to modify
- Change the Name and click the Save button, otherwise go to the next step
- Change the Description and click the Save button
- If you are not changing the volume name or description, please continue to Step D.
- If you received a failure notification, continue to Step F.
- If you received a success notification, you have validated that volume modification is complete.
D. Validating Available Pool Capacity
Get the pool name from the volume details for the volume you are expanding. Reference <Document: 1009974.1> Validating Volume State and Details on a Sun StorEdge[TM] 6920.
Get the Unallocated or Available Capacity from the pool details for this pool. Reference document <Document: 1007144.1> Validating Pool State and Details on a Sun StorEdge[TM] 6920
- If the available capacity in the pool does not match your size requirements,
you will need to add more storage to the pool, or remove any unnecessary volumes in this pool.
Reference <Document: 1005385.1> Validating Sun StorEdge[TM] 6920 Volume Deletion
Reference <Document: 1013066.1> Validating Sun StorEdge[TM] 6920 Pool Modification
- If you have enough space, continue to Step E.
E. Extending the Volume
The size specified in either method below is the size that you are extending the volume TO.
SSCS
Usage:
sscs modify -e <string> volume <string>
The size can be referenced in terms of blocks(B), kilobytes(KB), megabytes(MB), gigabytes(GB), or terabytes(TB).
Example:
./sscs modify -e 300MB volume small_vol
This extends the volume small_vol to a size of 300MB.
BUI
- Click on the Configuration Services or Common Array Manager(3.2.0.38) Link.
- Click on the Volume Tab or Volume Menu Tree
- Click on the Volume Name that you wish to modify
- Click on the Extend button.
- In the pop-up window select either the Maximum Capacity, or specify it yourself. And click the OK button.
At this point the Pop-Up window will disappear, and the main browser screen will refresh, and a success or failure message will be displayed in the Volume Details page.
- If you received a failure notification, continue to Step F.
- If you received a success notification, you have validated that volume modification is complete.
F. Creation Failure.
Please review the following table for a failure message and corresponding action. Please follow the action that describes your symptom.
BUI
Message:
An error occurred. Please contact your system administrator
Action:
Please go to Step G.
Message:
Space for the specified snapshot could not be allocated.
Action:
Snapshot reserve space is increased along with the parent volume. Reference ####(snap mod doc)
Message:
The volume name contains invalid characters
Action:
Change the volume name per pop-up directions.
Message:
The requested volume size must be at least 1MB greater than the volume's current size.
Action:
Specify a size that is the volume size plus 1MB or more
Message:
The requested volume size is too small
Action:
The volume size specified is smaller than the original size. Volumes cannot be shrunk.
Message:
The volume size specified is too large for the virtual disks in the storage pool specified.
Action:
Refer to Step D in this document
SSCS
Message:
Name contains illegal characters
Action:
Change the volume Name. Valid Characters are A-Z, a-z, 0-9, -, or _. No Spaces.
Message:
Name too long
Action:
Change the volume name. Volume Names must be less than 16 characters.
Message:
<pool_name>: The resource was not found.
Action:
Make sure the pool exists and the name is correct(sscs list pool)
Message:
The volume size specified is too large for the virtual disks in the storage pool specified.
Action:
Make a smaller volume, or use a pool with a larger space
Message:
<size>: Invalid size format
Action:
Valid Size format is expressed as a positive integer value, followed by b, kb, mb, gb, or tb, indicating units, ie 10gb
Message:
<domain>: The resource was not found.
Action:
Check the spelling of the domain name, and make sure it exists(sscs list sdomain)
Message:
Error: The operation failed.
Action:
Please go to Step G
Message:
Space for the specified snapshot could not be allocated.
Action:
##### Snapshot reserve space is increased along with the parent volume.
Message:
The requested volume size must be at least 1MB greater than the volume's current size.
Action:
Specify a size that is the volume size plus 1MB or more
Message:
The requested volume size is too small
Action:
The volume size specified is smaller than the original size. Volumes cannot be shrunk.
Message:
The volume size specified is too large for the virtual disks in the storage pool specified.
Action:
Refer to Step D in this document
If a message is not listed, or an action above did not work, go to Step G.
G. Data Collection
Please collect the following information:
- Answers to Questions in Step A.
- 6920 Solution Extract, Reference document <Document: 1003756.1> How to collect an extractor from a Sun StorEdge[TM] 6920 (2.x and 3.x)
- The message given by SSCS or BUI(screen capture if possible)
- The command used, if by SSCS
- The input and selections for the new volume wizard in the BUI
- The following sscs output:
sscs list sdomain
sscs list volume <volume name>
sscs list pool
sscs list pool <pool name> (needed for sizing issues)
sscs list vdisk
NOTE 2: Screen captures of the summary page for each object could be used, as well, for BUI related creations.
Once this information is collected, please contact Sun Support
ProductSun StorageTek 6920 System
Sun StorageTek 6920 Maintenance Update 2
Sun StorageTek 6920 Maintenance Update 1
Internal Comments
Validating Sun StorEdge[TM] 6920 Volume Modification
This document contains normalized content and is managed by the the Domain Lead(s) of the respective domains. To notify content owners of a knowledge gap contained in this document, and/or prior to updating this document, please contact the domain engineers that are managing this document via the “Document Feedback” alias(es) listed below:
[email protected]
The Knowledge Work Queue for this article is KNO-STO-MIDRANGE_DISK.
H. Validate command provided
Validate command provided against examples in the Sun StorEdge 6920 System CLI Quick Reference Guide, Release 3.0.
Ensure that options are valid based on the usage available in reference guide.
I.
error occurred
If the customer reports:
An error occurred. Please contact your system administrator
OR
Error: The operation failed.
Validate the services on the Service Processor. Reference document <Document: 1007129.1>
J. Perform health check of array
Reference document <Document: 1005447.1> Sun StorEdge[TM] 6920 Health Checklist
K. Escalate
Provide the following:
- Description of what is not being displayed properly
- Results of Step H.
- Results of Step I.
- Results of Step J.
- Location of everything in Step G
modify, configure, volume, 6920, extend, expand, rename, normalized, Audited
Previously Published As
90307
Change History
Date: 2007-09-28
User Name: 7058
Action: Approved
Comment: Some links in the external section were pointing to sunsolve.central. Corrected those.
No further edits.
OK to publish.
Version: 3
Date: 2007-09-26
User Name: 7058
Action: Accept
Comment:
Version: 0
Date: 2007-09-26
User Name: 70984
Action: Approved
Comment: Reviewed document and all appears to be correct.
Version: 0
Date: 2007-09-26
User Name: 70984
Attachments
This solution has no attachment