Asset ID: |
1-71-1009979.1 |
Update Date: | 2010-08-26 |
Keywords: | |
Solution Type
Technical Instruction Sure
Solution
1009979.1
:
Validating Sun StorEdge[TM] 6920 Volume Creation
Related Categories |
- GCS>Sun Microsystems>Storage - Disk>Modular Disk - 6xxx Arrays
|
PreviouslyPublishedAs
213667
DescriptionThe purpose of this document is to provide basic steps for volume
creation 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 creating 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 Creation:
A. Start By Planning
Volume layout planning and considerations should be reviewed by
answering the following questions:
- Do you have more than a single Storage Domain? If so which one will be used?
- Have you identified a pool to create the volume from?
- Will you be creating a new VDisk?
- Will you be creating a new Pool?
- Will you be creating a new profile for a new pool
- Will you be creating the volume as a Mirror with multiple components?
- Will you be creating snapshots from this volume?
- Will you be creating the volume from External Storage?
After answering these questions please review the contents of the 6920 Best Practices Guide, and identify that you are prepared with at least:
- The storage domain that the volume will reside
- The pool that the volume will reside
- Whether you will create the volume as a mirror of different components
- Whether you will be creating snapshots of this volume, and how big the reserve will need to be.
- If there are snapshots, which pool will store the snapshot reserve device.
- If you are going to stripe across all vdisks in the pool.
If all the information above is provided, continue to Step B
B. Basic Usage Using Browser or SSCS interfaces
This usage assumes that you are not mirroring, and not snapshotting your volume. Please reference documents <Document: 1011356.1> Validating Sun Storedge[TM] 6920 Snapshot Creation and <Document: 1005586.1> Validating Sun StorEdge[TM] 6920 Mirror Volume Creation instead.
SSCS
The sscs usage for basic volume creation is as follows.
sscs create -p <string> -s <string> [-S|--sdomain <string>] [-t|--stripe-all] [-d|--description <string>] volume <volume-name>
An example:
sscs create -p raid1pool -s 100GB volume 100GBvol
This will create a 100 Gigabyte volume from the storage pool raid1pool, which resides in the Storage Domain DEFAULT, and the volume is called 100GBvol.
NOTE1: The Storage Domain is assumed to be DEFAULT when it is not specified by the -S switch in the usage
BUI
Volume creation 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 Blue New Button. This will open a pop-up window. You will need to have pop-ups enabled to complete this task. If a new window does NOT appear or if an error message appears on the main page, go to Step C.
- Complete the Name field for the volume name in the Specify volume Properties screen.
- Click the Next Button. This leaves the Storage Domain at DEFAULT, the description field blank, and the Volume Type at Single Volume.
- Select a Storage pool from the radio button, and click Next, in the Select Storage Pool screen.
- Select the radio button, and input the volume size, and select the units(blocks, KB, MB, GB, TB) for the Specify the capacity and striping configuration screen.
- Click the Next button
- Leave the Allocate Space for drop down at No Snapshots on the Allocate Snapshot Reserve Space screen, and click Next
- Leave the Initiators unchecked in the Select Initiators screen and click next.
- The Summary screen will show the volume name, type, capacity, pool, None reserved snapshot space, and None for initiators.
- Click the Finish 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 Summary page, and the volume will be listed in this page, sorted alphanumerically.
- If you received a failure notification, continue to Step C.
- If you received a success notification, you have validated that volume creation is complete.
C. 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 D.
Message:
The volume name contains invalid characters
Action:
Change the volume name per pop-up directions
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
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 D
If a message is not listed, or an action above did not work, go to Step D.
D. 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
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
Sun Support
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:
The Knowledge Work Queue for this article is KNO-STO-MIDRANGE_DISK.
storage-os-disk-mid-domain@sun.com
E. 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.
F.
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>
G. Perform health check of array
Reference document < Solution: 202528 > Sun StorEdge[TM] 6920 Health Checklist
H. Escalate
Provide the following:
- Description of what is not being displayed properly
- Results of Step E.
- Results of Step F.
- Results of Step G.
- Location of everything in Step D
6920, volume, creation, sscs, BUI, normalized, add, audited
Previously Published As
90286
Change History
Date: 2007-09-27
User Name: 95826
Action: Approved
Comment: - verified metadata
- changed review date to 2008-09-26
- checked normalized data
- checked for TM - none added
- checked audience : contract
Publishing
Version: 4
Date: 2007-09-27
User Name: 95826
Action: Accept
Comment:
Version: 0
Date: 2007-09-26
User Name: 39181
Action: Approved
Comment: Technical content looks good. Sending to final review.
Version: 0
Date: 2007-09-18
User Name: 88109
Action: Approved
Comment: fixed requested #### and changed the links in the description, as well as changed the internal section.
Attachments
This solution has no attachment