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-1002786.1
Update Date:2010-09-14
Keywords:

Solution Type  Technical Instruction Sure

Solution  1002786.1 :   Sun StorageTek[TM] 6140/6540 : Unable to Map a Volume or Snapshot as LUN 31 Using Common Array Manager (CAM)  


Related Items
  • Sun Storage 6540 Array
  •  
  • Sun Storage 6140 Array
  •  
Related Categories
  • GCS>Sun Microsystems>Storage - Disk>Modular Disk - 6xxx Arrays
  •  

PreviouslyPublishedAs
203810


Description
When trying to map a volume or a snapshot to a host or hostgroup as LUN 31 on
a Sun StorageTek[TM] 6140 or 6540 array, the following error is reported by
sscs :
# sscs map -a my-6140 -v my-volume -l 31 host my-host
my-host -> my-volume: : The operation cannot complete because the
logical unit number (LUN) is already in use by the Access Volume.
Select another LUN.

Note: Older versions of software might not explicitly mention that
the Access Volume is already mapped to LUN 31, in which case the message
will only say :

"The operation cannot complete because the logical unit number (LUN) is
already in use. Enter a different LUN."

The equivalent error for the same operation in the Common Array Manager 5.1 GUI is :

 "An error occurred during the creation of Mappings. Mapping creation
forvolumevolumeWwn==60:0A:0B:80:00:11:FB:C8:00:00:80:7D:45:DE:8B:4
EvolumeRef==2:0:0:0:0:0:80:7D:45:DE:8B:4E:0:0:0:0:0:0:0:0:array==
60:0A:0B:80:00:11:FB:C8:00:00:00:00:45:92:54:0BvolumeName==my-volume
failed. - The operation cannot be completed because the logical unit
number (LUN) is already in use by the Access Volume. Select another
LUN."

Again, the error message in older versions of the GUI might not explicitly reference the Access Volume.



Steps to Follow
By default, on the ST6140 and ST6540 arrays, LUN 31 is already mapped to a
read-only volume, known as the access volume, for every attached data host.
So, by default, LUN 31 is always unavailable for mapping to a data volume
or snapshot.

The access volume is not a normal data volume. The access volume is a
special volume automatically created by the array. It's purpose is to
allow in-band management of the array, when using array management software
which has in-band management functionality. Currently, the Common Array
Manager software does not have this functionality.

In Common Array Manager 5.1 or higher, the mapping of the access volume as
LUN 31 is reported in the list of host mappings and it's possible to unmap
the access volume, freeing up LUN 31. So, if the access volume is unmapped
from a host or hostgroup, then it becomes possible to map a normal data
volume or snapshot as LUN 31 to that host or hostgroup.



Product
Sun StorageTek 6540 Array
Sun StorageTek 6140 Array

Internal Comments
For internal Sun use only.

Bug ID 6355569 describes the error message format change.


Bug ID 6461123 describes the change in CAM 5.1 which allows unmapping of the

access volume.


Storagetek, 6140, 6540, ST6140, ST6540, LUN, 31, already, in, use, access, volume, sscs, CAM, Common, Array, Manager
Previously Published As
88574

Change History
Date: 2007-02-28
User Name: 7058
Action: Approved
Comment: Format was all screwed up. I think it is repaired. Preview looks OK. I cannot determine why line wrapping was behaving strangely.
Spell ck OK.
Tags OK.
OK to publish.
Version: 3
Date: 2007-02-26
User Name: 7058
Action: Accept
Comment:
Version: 0

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