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-1005606.1
Update Date:2010-08-31
Keywords:

Solution Type  Technical Instruction Sure

Solution  1005606.1 :   Validating Mapping Deletion for Volumes and Initiators for a Sun StorEdge[TM] 6290  


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

PreviouslyPublishedAs
207784


Description
The purpose of this document is to provide basic steps for deleting LUN
mapping for volumes and initiators 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 deleting mappings, 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 Mapping Deletion for Volumes and Initiators for a Sun StorEdge[TM] 6290:

A. Start By Planning

  1. What is the volume you want to unmap?
  2. What is the initiator name you want to unmap?
  3. What is the volume WWN(reference document <Document: 1009974.1>  Validating Volume State and Details on a Sun StorEdge[TM] 6920)?
  4. What is the initiator WWN(reference document <Document: 1011349.1> Validating Initiator State and Details for a Sun StorEdge[TM] 6920)?
  5. Are you currently accessing this device?

B. Stop Access to the device

Unmapping volumes can cause a loss of access, resulting in application failure.
Great care must be taken with answering the questions above.

  1. Validate the Volume WWN and LUN that will be unmapped. Reference document <Document: 1009974.1> Validating Volume State and Details on a Sun StorEdge[TM] 6920
  2. Validate all initiator WWN's that will be unmapped.
  3. Use the initiator and volume data above to identify the device from an OS perspective. Reference document <Document: 1009557.1>  Troubleshooting Fibre Channel Devices from the Solaris[TM] OS
  4. Ensure that this device is not in use by any application(this varies from application to application)
  • If an application is using this device, you must stop it from using the device. This will likely depend on reconfiguration.
  • If no application is using the device, continue to Step C.

C. Un-Map Volume

This allows you to un-map a single volume from many initiators.

SSCS

sscs unmap volume <volume name>

example

sscs unmap volume my-vol

This will delete a volume-to-LUN mapping for the volume my-vol, on all initiators.

BUI

  1. Click Configuration Services or Common Array Manager
  2. Click the Volume tab or menu tree
  3. Click on the Volume Name link
  4. Click the Unmap button
  5. Check next to the Initiator name.
  6. Click Unmap
  7. Click OK to confirm
  • If you received an error, go to Step F.
  • If you were successful go to Step E.

D. Unmap Initiator to Volume

This allows you to unmap a volume from a single initiator.

SSCS

sscs unmap -v <volume> initiator <initiator>

example

sscs unmap -v my-vol initiator my-init

This will delete a volume-to-LUN mapping to the initiator my-init for the volume, my-vol.

BUI

  1. Click Configuration Services or Common Array Manager
  2. Click on Physical Storage
  3. Click on the Initiator tab or menu tree
  4. Click on the Initiator Name link
  5. Click the Unmap button
  6. Check next to the Initiator name.
  7. Click Unmap
  8. Click OK to confirm
  • If you received an error, go to Step F
  • If you were successful go to Step E

E. Validate Mapping

Validate your mappings on the 6920. Reference document <Document: 1008480.1> Validating Mapping Status and Details on a Sun StorEdge[TM] 6920

Use the LUN ID and WWN of the Volume to validate your mappings on Solaris[TM]. Reference document <Document: 1009557.1> Troubleshooting Fibre Channel Devices from the Solaris[TM] OS

F. Failure

BUI

Message:
An error occurred. Please contact your system administrator

Action:
Please go to Step G.

SSCS
Message:
<initiator>: The object was not found.

Action:
Check the name of your initiator. See Step G.

Message:
<domain>: The resource was not found.

Action:
Make sure that the domain is typed correctly, or exists(sscs list sdomain)

Message:
Error: operation failed

Action:
Please go to Step G.

If a message is not listed or the actions did not work, go to Step G.

G. Data Collection

  • Date/Time you attempted to map the volume or initiator
  • 6920 Solution Extract, Reference document <Document: 1003756.1>  How to collect an extractor from a Sun StorEdge[TM] 6920 (2.x and 3.x)
  • Solaris Explorer, Reference document <Document: 1006990.1> Sun[TM] Explorer Implementation Best Practice
  • Windows data, Reference document <Document: 1006603.1> Microsoft Windows? operating system: How to obtain troubleshooting information for storage issues
  • The message given by SSCS or BUI(screen capture if possible)
  • The command used, if by SSCS
  • The input and selections for the new initiator wizard in the BUI
  • The following sscs output:

sscs list volume
sscs list volume <volume>
sscs list initiator
sscs list initiator <initiator>
sscs list sdomain

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:

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



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 E.

  • Results of Step F.

  • Results of Step G.

  • Location of everything in Step D

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

unmap, delete, mappings, map, 6920, volume, initiator, hba, normalized, Audited
Previously Published As
90586

Change History
Date: 2007-09-28
User Name: 7058
Action: Approved
Comment: 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 and updated.
Version: 0
Date: 2007-09-26
User Name: 70984
Action: Add Comment
Comment: This document is "pending the completion of 89105, per normalization".
Corrected line A. 1. to read: What is the volume you want to unmap?
from: 1. What is the volume you want to map?
Corrected line A. 2. to read: What is the initiator name you want to unmap?
from 2. What is the initiator name you want to map?
Corrected line D. to read: Unmap Initiator to Volume
from D. Map Initiator to Volume


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