Sun Microsystems, Inc.  Sun System Handbook - ISO 3.4 June 2011 Internal/Partner Edition
   Home | Current Systems | Former STK Products | EOL Systems | Components | General Info | Search | Feedback

Asset ID: 1-71-1005586.1
Update Date:2010-08-27
Keywords:

Solution Type  Technical Instruction Sure

Solution  1005586.1 :   Validating Sun StorEdge[TM] 6920 Mirror Volume Creation  


Related Items
  • Sun Storage 6920 System
  •  
Related Categories
  • GCS>Sun Microsystems>Storage - Disk>Modular Disk - 6xxx Arrays
  •  

PreviouslyPublishedAs
207752


Description
The purpose of this document is to provide basic steps for mirror 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 mirror 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 Follow
Validating Sun StorEdge[TM] 6920 Mirror Volume Creation:

A. Start By Planning

Volume layout planning and considerations should be reviewed by
answering the following questions:

  1. Do you have more than a single Storage Domain? If so which one will be used?
  2. Have you identified a pool to create the volume from?
  3. Will you be creating a new VDisk?
  4. Will you be creating a new Pool?
  5. Will you be creating a new profile for a new pool
  6. Will you be creating the volume as a Mirror with multiple components?
  7. Will you be creating snapshots from this volume?
  8. 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 mirroring, and not snapshotting your volume. Please reference

SSCS

Mirror Volume Creation usage for sscs, can be reviewed in the SSCS Quick Reference Guide. The sscs usage for basic mirror volume creation is as follows.

sscs create -m pool1,pool2 -s <string> volume <volume-name>

or

sscs add -c volume1,volume2 volume <volume-name>

An example:

sscs create -m myfirstpool,mysecondpool -s 100GB volume 100GBvol

This will create a 100 Gigabyte mirrored volume with components from the storage pool myfirstpool, and mysecondpool, which reside in the Storage Domain DEFAULT, using the log pool of myfirstpool. The volume is called 100GBvol.

''Note 1: Mirror creation requires that you specify a pool for each component. Each pool must be called out in comma delimited format, as shown above.

Note 2: The Log Pool defaults to the first pool specified unless the -g switch is used.

or

An example:
sscs modify -M -c myfirstvolume volume mysecondvolume

This will create a mirrored volume with components from the volume myfirstvolume, and mysecondvolume, which reside in the Storage Domain DEFAULT. The volume will be called mysecondvolume. The data on myfirstvolume will be overwritten.

''Note 1: The Storage Domain is assumed to be DEFAULT when it is not specified by the -S switch in the usage.

Note 2: The isolation policy defaults to required if the -i switch isn't used.

Note 3: The Resilver Priority defaults to medium unless the -v switch is used.

BUI

Mirror volume Creation steps for the BUI can be reviewed in Sun StorEdge 6920 System Administration Guide For the Browser Interface Management Software, Release 3.0. The following steps assume that you are mirroring, and not snapshotting your volume. Mirror volume creation for the BUI interface of the 6920 is completed as follows:

  1. Click on the Configuration Services or Common Array Manager(3.2.0.38) Link.
  2. Click on the Volume Tab or Volume Menu Tree
  3. 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.
  4. Complete the Name field for the volume name in the Specify volume Properties screen.
  5. Select a Volume Type of Mirrored Volume
  6. Use the pull down menu to select a Concatenate or Stripe pool for the mirror components.
  7. Click the Next Button. This leaves the Storage Domain at DEFAULT, the description field blank.
  8. Select an Isolation Policy from the radio button in the Select Storage Pool screen.
  9. Select a Storage pool from the radio button, and click Next, in the Select Storage Pool screen.
  10. Select the radio button, and input the volume size, and select the units(blocks, KB, MB, GB, TB) for the Specify Mirror Properties screen.
  11. Select the Resilver Priority from the radio button.
  12. Click the Next button
  13. Leave the Allocate Space for drop down at No Snapshots on the Allocate Snapshot Reserve Space screen, and click Next
  14. Leave the Initiators unchecked in the Select Initiators screen and click next.
  15. The Summary screen will show the volume name, type, capacity, pool, None reserved snapshot space, and None for initiators.
  16. 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 list for a failure message and corresponding action. Please follow the action that describes your symptom.

Browser|
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

Action:
Make a smaller volume, or use a pool with for the virtual disks in the storage a larger space pool specified.

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

Message:
A minimum of 2 mirror pools is required

Action:
Use at least 2 pools with the -m switch

Message:
There are not enough arrays to isolate logs

Action:
Use the -i switch with the optional variable

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 6: 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



Product
Sun 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:

storage-os-disk-mid-domain@sun.com

The Knowledge Work Queue for this article is KNO-STO-MIDRANGE_DISK.



E. Validate that services are running properly on the SP


Reference document <Document: 1007129.1> Validating Services on a Sun StorEdge 6920 Service Processor



F. Perform health check of array


Reference document <Document: 1005447.1>  Sun StorEdge[TM] 6920 Health Checklist



G. Escalate


Provide the following:



  • Description of what is not being displayed properly

  • Results of Step E.

  • Results of Step F.

  • Location of everything in Step D


6920, volume, mirror, creation, sscs, BUI, normalized, audited
Previously Published As
90340

Change History
Date: 2007-09-27
User Name: 95826
Action: Approved
Comment: - verified metadata
- review date ok : 2008-09-26
- checked normalized data
- checked for TM - none added
- checked audience : contract
Publishing
Version: 7
Date: 2007-09-27
User Name: 95826
Action: Add Comment
Comment: 89105 still pending (now on FR / Nita)
Version: 0
Date: 2007-09-27
User Name: 95826
Action: Accept
Comment:
Version: 0
Date: 2007-09-26
User Name: 39181
Action: Approved
Comment: Doc 89105 has been submitted. Sending back for final review.


Attachments
This solution has no attachment
  Copyright © 2011 Sun Microsystems, Inc.  All rights reserved.
 Feedback