Unable to Map a Volume or Snapshot as LUN 31 Using Sun Storage Common Array Manager (CAM) for Sun Storage[TM] 2500 and 6000 Arrays

Asset ID:	1-72-1002786.1
Update Date:	2017-05-12
Keywords:

Solution Type Problem Resolution Sure

Solution 1002786.1 : Unable to Map a Volume or Snapshot as LUN 31 Using Sun Storage Common Array Manager (CAM) for Sun Storage[TM] 2500 and 6000 Arrays

Applies to:

Sun Storage 6130 Array - Version All Versions to All Versions [Release All Releases]
Sun Storage 6180 Array - Version All Versions to All Versions [Release All Releases]
Sun Storage 6580 Array - Version All Versions to All Versions [Release All Releases]
Sun Storage 2530-M2 Array - Version Not Applicable to Not Applicable [Release N/A]
Sun Storage 2540-M2 Array - Version Not Applicable to Not Applicable [Release N/A]
All Platforms

Symptoms

When trying to map a volume or a snapshot to a Host or Hostgroup as LUN 31 on Sun Storage Common Array Manager (CAM) for Sun Storage[TM] 2500 and 6000 Arrays, the following error is reported:

# 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 CAM 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."

Cause

By default, on Sun Storage[TM] 2500 and 6000 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 CAM software with In-band management functionality. For more information about In-band management and Access volume, refer here.

Solution

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.

Note: Access volume can not be unmapped using 'sscs' command.

Attachments

This solution has no attachment