Sun Microsystems, Inc.  Oracle System Handbook - ISO 7.0 May 2018 Internal/Partner Edition
   Home | Current Systems | Former STK Products | EOL Systems | Components | General Info | Search | Feedback

Asset ID: 1-71-1597079.1
Update Date:2015-07-17
Keywords:

Solution Type  Technical Instruction Sure

Solution  1597079.1 :   Sun Storage 2500, 2500-M2, and 6000 Arrays: How to Administer the Access Volume (LUN 31) using Sun Storage Common Array Manager (CAM)  


Related Items
  • Sun Storage 2510 Array
  •  
  • Sun Storage 2540-M2 Array
  •  
  • Sun Storage 2540 Array
  •  
  • Sun Storage Common Array Manager (CAM)
  •  
  • Sun Storage 6130 Array
  •  
  • Sun Storage 6780 Array
  •  
  • Sun Storage 6180 Array
  •  
  • Sun Storage 2530 Array
  •  
  • Sun Storage 2530-M2 Array
  •  
  • Sun Storage 6540 Array
  •  
  • Sun Storage 6140 Array
  •  
  • Sun Storage 6580 Array
  •  
Related Categories
  • PLA-Support>Sun Systems>DISK>Disk Software>SN-DK: CAM
  •  




Applies to:

Sun Storage 6540 Array - Version All Versions and later
Sun Storage 6130 Array - Version All Versions and later
Sun Storage 6780 Array - Version All Versions and later
Sun Storage 6140 Array - Version All Versions and later
Sun Storage 2530 Array - Version Not Applicable and later
Information in this document applies to any platform.

Goal

This document describes the functionality of the Access Volume on Sun Storage 2500, 6000 and 2500-M2 arrays, and how to administer it using Sun Storage Common Array Manager (CAM).

Solution

What is the Access Volume?

The Access Volume is also known as the UTM LUN (Universal Transport Mechanism Logical Unit), or LUN 31. It is a special volume that is used by the host-agent software to communicate management requests and event information between the management station and the storage array. It exists on the array by default and cannot be deleted, created, or accessed for I/O.

When is the Access Volume needed?

The Access Volume is required only for in-band management and is mapped by default to each storage domain as LUN 31. If the array is being managed out-of-band, the Access Volume is not needed and can be removed from view of the OS by deleting the mapping(s) using the management software, for example Sun Storage Common Array Manager (CAM). With new arrays, the mapping of the Access Volume to the default domain is set at the factory.

Can I format, label and use the Access Volume to store data?

No. The Access Volume cannot be modified, deleted, created, or accessed for normal I/O. Because a label cannot be applied, error messages may be logged to /var/adm/messages. For details, refer to <Document 1477987.1> "Corrupt Label, Wrong Magic Number" error seen on LUN 31 devices from Oracle storage arrays.

How can I tell what the Access Volume looks like from the OS?

The Access Volume will be labeled with "SUN UniversalXport" or "Volume Access".

Example from Solaris:

AVAILABLE DISK SELECTIONS:
       0. c0t1d0 <SUN18G cyl 7506 alt 2 hd 19 sec 248>
          /pci@1f,4000/scsi@3/sd@1,0
       1. c1t0d31 <SUN-UniversalXport-0780 cyl 8 alt 2 hd 64 sec 64>
          /pci@1f,4000/SUNW,qlc@2/fp@0,0/ssd@w20330080e523b834,1f
       2. c2t0d31 <SUN-UniversalXport-0780 cyl 8 alt 2 hd 64 sec 64>
          /pci@1f,4000/SUNW,qlc@2,1/fp@0,0/ssd@w20320080e523b834,1f

Example from Windows:

\\.\PHYSICALDRIVE0 [Storage Array fms-lca1, Volume Access, LUN 31, Volume ID <600a0b80002458d20000000000000000>]
\\.\PHYSICALDRIVE1 [Storage Array fms-lca1, Volume Access, LUN 31, Volume ID <600a0b80002fc0740000000000000000>]


I want to switch from out-of-band management to in-band management but my Access Volume is not mapped. How do I get it back?

To map the Access Volume to a host using CAM :

  1. Select the Storage System on the left-hand pane and expand its list of pages.
  2. Click on the "Mappings" page for the array. It will appear in the right-hand pane.
  3. Click the "New" button. A pop-up window will appear.
  4. In the "Volume/Snapshot name contains" field, type "Access" and click "Next".
  5. Check the box next to "Access", choose "31" from the drop-down menu under "LUN", and then click "Next".
  6. Select the host you are using for in-band management and then click "Next".
  7. Finally, review your selections and confirm using the "Finish" button.

If I do not need the Access Volume, how do I delete it?

You cannot delete the Access Volume. You can remove view of the Access Volume from the OS by deleting the mapping from the management software.

To delete the mapping of the Access Volume to a host using CAM:

  1. Select the Storage System on the left-hand pane and expand its list of pages.
  2. Click on the "Mappings" page for the array. It will appear in the right-hand pane.
  3. Find the volume named "Access" in the list of mappings for the host or its associated host group and check the box next to it.
  4. Click the "Delete" button.
Deleting a mapping of the Access Volume to a host group will remove the view of the Access Volume by the OS of all hosts within that host group.

For additional information on in-band management, please refer to the Array Administration Guide for your version of CAM on the Oracle Technology Network's Disk Device Software Documentation page.

Do you still have questions?  You can use My Oracle Support Communities.  Communities put you in touch with industry professionals like yourself.  They are monitored by Oracle support engineers, so you can expect reliable and correct answers.  Ask questions and see what others are asking about in the Disk Storage 2000, 3000, 6000 RAID Arrays & JBODs Community.

 

References

<NOTE:1477987.1> - "Corrupt Label, Wrong Magic Number" error seen on LUN 31 Devices from Oracle Storage Arrays

Attachments
This solution has no attachment
  Copyright © 2018 Oracle, Inc.  All rights reserved.
 Feedback