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-1540471.1
Update Date:2014-12-09
Keywords:

Solution Type  Technical Instruction Sure

Solution  1540471.1 :   Pillar Axiom: How to set up, identify and mount clones on a Solaris 10 server  


Related Items
  • Pillar Axiom 600 Storage System
  •  
  • Pillar Axiom 500 Storage System
  •  
Related Categories
  • PLA-Support>Sun Systems>DISK>Axiom>SN-DK: Ax600
  •  




Created from <SR 3-6948703531>

Applies to:

Pillar Axiom 600 Storage System - Version Not Applicable to Not Applicable [Release N/A]
Pillar Axiom 500 Storage System - Version Not Applicable to Not Applicable [Release N/A]
Information in this document applies to any platform.

Goal

This method explains the steps that are needed with AxiomCli in order to identify and mount a clone on a Solaris 10 Server
The commands below are for Axioms in R5 only.
 

Solution

The Axiom does not have constant LUN Serial Numbers for clones: each time you create a new clone, a new LUN Serial Number is used resulting in the /dev/dsk/ path changing for every new clone.

Other vendors such as EMC have a different Clone or Snapshot creation method where the LUN Serial Number is static and the clone can be stopped/refreshed this makes the system administator able to just set up the clone in the vfstab. The Axiom does not have this functionality (yet)


The Axiomcli software and documentation are available on the Axiom Storage System web interface. Please check details via a web browser on address http://<AXIOMIP>.

The lines below are guidelines. The AxiomCli has many more options and functionality to fine tune the clone creation and managment.

 

Legent for below procedure:

AXIOMIP : Axiom Storage System Public IP address

AXIOMACCOUNT : Axiom Storage System User with administrator privileges

AXIOMPASSWORD : Password of Axiom Storage System User

CLONENAME : Name of the Clone LUN

LUNSOURCE : Name of the Source LUN sued to create Clone LUN

LUNNUMBER :  LUN Number reported for Clone LUN after clone creation

MOUNTPOINT : mount point given by user on Solaris hosts

HOST : Hostname using the Clone LUN

LUID: LUN ID will be used for mounting the Clone LUN

 

Method to mount clones:

 

1- Login Axiom CLI
axiomcli login AXIOMIP -u AXIOMACCOUNT -p AXIOMPASSWD

2- Create Clone LUN of the Source LUN
axiomcli clone_lun -add -name CLONENAME -source /LUNSOURCE

3- Create mapping for newly created Clone LUN
axiomcli hostmap -add -lun /CLONENAME -lunNumber LUNNUMBER -host /HOST

4- Refresh device table on Solaris host
devfsadm -c disks

5- Grab LUN ID needed to mount newly created LUN
LUID=`axiomcli clone_lun -list -details -clonelun /CLONENAME -o xml | grep "SerialNumber" | cut -d ">" -f 2 | cut -c 1-16`

6- Mount new Clone LUN via using new LUID
mount /dev/dsk/c2t${LUID}d0s2 MOUNTPOINT

!!! NOTE: Controller number on your system may be different. Please check details via "cfgadm -al" command. !!!

7- Logout Axiom CLI
axiomcli logout

 


Method to unmount and delete:


1- Login Axiom CLI
axiomcli login AXIOMIP -u AXIOMACCOUNT -p AXIOMPASSWD

2- Unmount previously mounted Clone LUN
umount MOUNTPOINT

3- Delete mapping of old Clone LUN on Axiom
axiomcli hostmap -delete -lun /CLONENAME -host /HOSTMAPPING

4- Delete old CLone LUN on Axiom
axiomcli clone_lun -delete -clonelun /CLONENAME

5- Logout Axiom CLI
axiomcli logout

 


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