Sun Storage 6920 System
 

GCS>Sun Microsystems>Storage - Disk>Modular Disk - 6xxx Arrays
 

Content will be limited to a basic usage using the CLI or BUI interfaces
for creating 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:

• Best Practices for the Sun StorEdge 6920 System, Version 3.0.1
• Sun StorEdge 6920 System CLI Quick Reference Guide, Release 3.0
•  <Document: 1009915.1>  Troubleshooting Sun StorEdge[TM] 6920 Configuration Problems
• Sun StorEdge 6920 System Administration Guide For the Browser Interface Management Software, Release 3.0

A. Start By Planning

1. What is the volume you want to map?
2. What is the initiator name you want to map?
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)?

B. Map Volume to Initiator

This allows you to map a single volume to many initiators.

SSCS

sscs map -P <readonly|readwrite> -i <initiator> volume <volume>

example

sscs map -P readonly -i my-init volume my-vol

This will create a volume-to-LUN mapping to the initiator, my-init, on the next, lowest, available, LUN number(0-255) for the volume my-vol, and allow read-only permissions.

BUI

1. Click Configuration Services or Common Array Manager
2. Click the Volume tab or menu tree
3. Check the box next to the volume name you wish to map.
4. Click the Map button
5. In the pop-up wizard that appears, check next to the initiators that you want to map to, and set the permissions. If an initiator is not listed, it is not part of the same Storage Domain as the volume in question, and cannot be mapped
6. Click Next, and click Finish on the summary screen.

• If you received an error, go to Step E
• If you were successful go to Step D

C. Map Initiator to Volume

This allows you to map multiple volumes to a single initiator.

SSCS

sscs map -P <readonly|readwrite> -v <volume> initiator <initiator>

example

sscs map -P readonly -v my-vol initiator my-init

This will create a volume-to-LUN mapping to the initiator, my-init, on the next, lowest, available, LUN number(0-255) for the volume my-vol, and allow read-only permissions.

BUI

1. Click Configuration Services or Common Array Manager
2. Click on Physical Storage
3. Click on the Initiator tab or menu tree
4. Check next to the initiator name you wish to map a volume.
5. Click the Map button
6. Check next to the name(s) of the volume(s) you wish to map to this initiator
7. Set the permissions If a volume is not listed, it is not part of the same Storage Domain as the initiator in question, and cannot be mapped
8. Click Finish

• If you received an error, go to Step E
• If you were successful go to Step D

D. 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 OS

E. Failure

BUI

Message:
An error occurred. Please contact your system administrator

Action:
Please go to Step F.

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

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

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

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

F. 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: 1006608.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

G. Validate that services are running properly on the SP

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

H. Validate that the mapping was successful

Reference document <Document: 1004135.1> Sun StorageTek[TM] 6920: Cannot See Volume Mapped to Host on All Paths

I. Perform health check of array

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

J. Escalate

Provide the following:

• Description of what is not being displayed properly


• Results of Step G.


• Results of Step H.


• Results of Step I.


• Location of everything in Step F
  

And escalate to your next level of support.

This solution has no attachment