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-75-1008470.1
Update Date:2009-04-21
Keywords:

Solution Type  Troubleshooting Sure

Solution  1008470.1 :   Validating Sun StorEdge[TM] 6920 Mirrored Volume State and Details  


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

PreviouslyPublishedAs
211571


Description
This document provides the basic steps to review mirrored volume state, configuration, and settings information using the Browser or SSCS user interfaces. Use this document if:
  • Mirrored Volumes are not listed in the UI
  • Mirrored Volumes are missing information
  • Syntax/Usage is needed to get volume state/details

For basic administrative tasks on the Sun StorEdge[TM] 6920 System, please reference



Steps to Follow
Validating Sun StorEdge[TM] 6920 Mirrored Volume State and Details:

A. Validate Mirrored Volume Summary

The basic usage for listing all of the volumes can be gotten by:

sscs

sscs list -S storage_domain volume

This will display:

  • Volume Name
  • Storage Domain Name
  • Volume Type(Single, Mirrored, Snapshot, Replicated)

Note that only volumes that are part of the storage domain specified will be listed. If no domain option is specified, the domain DEFAULT is assumed.

BUI

  1. Click Common Array Manager or Configuration Service link
  2. Click Logical Storage
  3. Click Volumes

This will display:

  • Volume Name
  • Storage Domain Name
  • State(Mapping State)
  • Condition(Volume State)
  • Volume Type(Single, Mirrored, Snapshot, Replicated)
  • Raw Capacity(Volume Size)
  • Volume WWN

For a more detailed view of a volume of type Mirror continue to Step B.. For other volume types, return to the table in Step 2 of <Document: 1009915.1> Troubleshooting Sun StorEdge[TM] 6920 Configuration Problems

If a volume cannot be seen, or has a condition other than OK go to Step D.

B. Validating Volume Details

This step details collection for Volumes that are of the type, Mirror

SSCS

sscs list -S storage_domain volume volume_name

Note that only volumes that are part of the storage domain specified will be listed. If no domain option is specified, the domain DEFAULT is assumed.

This will display the following field information:

  • Volume Name
  • Description
  • Creation Date
  • WWN
  • Storage Domain
  • Size
  • State
  • Condition (Volume State)
  • Resilver Priority
  • Isolation Policy
  • Mirror Logs Storage Pools
  • Snapshot Policy
  • Snapshot Pool(blank if none)
  • Space Allocated For(states No Snapshots if none)
  • Expected Write Activity
  • Snapshot Reserve Size(reports 0 if no snapshots)
  • Snapshot Reserve Percent Full(reports 0 if no snapshots)
  • Associated with Component(states No Snapshot Component Configured if none)
  • Snapshots
  • Component Volumes(Volumes that make up the mirror)
  • Associations(List of initiators to which the volume is mapped)

BUI

  1. Click Common Array Manager or Configuration Service link
  2. Click Logical Storage
  3. Click Volumes
  4. Click on a Volume Name with type Mirrored

This will display:
Details:

  • Volume Name
  • Description
  • Resilver Priority
  • Isolation Policy
  • State(Mapping State)
  • Condition(Volume State)
  • Storage Domain
  • Capacity
  • WWN
  • Mirror Logs Storage Pools(Storage pools in which the mirror logs reside)

Mirror

  • Name(Component Name)
  • State(Component Mapping State)
  • Condition(Component State)
  • Storage Pool(Storage pool for Component)
  • % Resilvered(Percentage of the component that has been resilvered)
  • Raw Capacity

Snapshot Reserve

  • Storage Pool(reports No Snapshot Reserve Space Allocated if none)
  • Size
  • Space Allocated For(states No Snapshots if none)
  • Expected Write Activity
  • Use(reports Not Apllicable if none)
  • Volume / Snapshot Policy:
  • Associated with Component(states No Mirror Component Selected if none)
  • In a table it will list the number and link you to a summary page for the following items under the Additional Details Section: Mapped Initiators, Replication Sets, Snapshots, and Virtual Disks. For details on any of these, please see Step 2 of document <Document: 1009915.1> Troubleshooting Sun StorEdge[TM] 6920 Configuration Problems.

Consider the following actions:

  • If you are concerned about the size displayed continue to Step C
  • If you are missing information in the detailed information go to Step D
  • If an initiator listed has a mapping state of Failed or Failure go to Step D
  • If the Condition field lists a state of Degraded, Don't Instantiate , Error, Error Detected, Lost Communication, Mirror Logs Degraded, Non-Recoverable Error, Supporting Entity in Error, or Unknown go to Alarm Doc
  • If the Condition field lists a state of Contains Split Volumes, Split Component, or Split Volume go to <Document: 1002715.1> 
  • If the Condition field is anything other then what's listed above go to Step D
  • If the Volume details are correct, you have validated the Volume Details, return to Step 2 of <Document: 1009915.1>  Troubleshooting Sun StorEdge[TM] 6920 Configuration Problems

C. Validating Size

The volume size should be as you listed during volume creation, however it
will be shown as follows:

  • If created in Units of Blocks or Kilobytes(KB), and less than 1 Gigabyte(GB), the size will be displayed in units of Megabytes(MB), rounded to the thousandths decimal place in the BUI, and the ten thousandths place in sscs.
  • If created in Units of Blocks, KB, or MB, and greater than 1 GB, the size will be displayed in units of GB, rounded to the thousandths decimal place in the BUI, and the ten thousandths place in sscs.
  • If created in Units of Blocks, KB, MB, or GB, and greater than 1 Terabyte(TB), the size will be displayed in units of TB, rounded to the thousandths decimal place in the BUI, and the ten thousandths place in sscs.

Example:

Volume created as 18000 blocks, will show up as 17.578 MB in the BUI, and 17.5781 MB in sscs.

If the Volume Size is missing, or incorrect, go to Step D
If the Volume Size is correct, you have validated the Volume Details, return
to Step 2 of <Document: 1009915.1> Troubleshooting Sun StorEdge[TM] 6920 Configuration Problems

D. Data Collection for Missing or Incorrect Volume Information

Please Collect the following information:

  • 6920 Solution Extract
  • sscs list output showing volume detail(or lack)
  • Screen capture of BUI screen showing volume detail(or lack)

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

[email protected]

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



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 <Document: 1005447.1> 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


and escalate to the next level of support.


6920, volume, details, sscs, BUI, size, list, mirror, audited
Previously Published As
90353

Change History
Date: 2007-09-27
User Name: 7058
Action: Approved
Comment: OK to publish. Roger did checks.
Version: 5
Date: 2007-09-27
User Name: 7058
Action: Reassign
Comment: Permission from roger to publish this. Timing is OK to publish now.
Version: 0
Date: 2007-09-27
User Name: 97961
Action: Add Comment
Comment: Waiting for some docs at top of resolution path to be published. Actions taken thus far:


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