Operating System - HP-UX
1833163 Members
3749 Online
110051 Solutions
New Discussion

SecurePath, LUN device file

 
Stan_365
Frequent Advisor

SecurePath, LUN device file


We have a production evironment with more than 25 LUNs(the size of most of LUNs is 200GB) belonging to different VGs. And in this weekend we will change from direct link (without SAN Switch) to indirect link (with Switches). We will install the SecurePath software. My problem is: How can we tell which LUNs are for specific VG? What will be the output of "# autopath display"
3 REPLIES 3
Steve Lewis
Honored Contributor

Re: SecurePath, LUN device file

The usual way is to carefully check the hardware path of the LUNs after you have changed round the storage. Use ioscan for this. The left hand end and the right hand of the path end will remain the same, but the bit in the middle will change.

The other way is to get hold of the LVM metadata for each lun and create your own mapping table. This would require two phases for the work. The first phase is the re-vgimport the storage with the SAN switch, but without SecurePath.
Second phase is to install/use SecurePath.

This thread will give you details on how to get the LVM VGID and PVID data that will allow you to create a definitive mapping table.

http://forums1.itrc.hp.com/service/forums/questionanswer.do?threadId=1064953
Tim Nelson
Honored Contributor

Re: SecurePath, LUN device file

As steve mentioned the HBA address and the LUN number will remain the same, the zone and port numbers i.e. 0/0/10/1/0.0.x.y.0.L.U.N, the x and y will change

You should be able to identify the previous to current paths by matching the LUN.
Stan_365
Frequent Advisor

Re: SecurePath, LUN device file

Thanks Steve and Tim.

Have changed it successfully on last Sunday.The device file for a LUN, cXtYdZ, Y & Z are unchanged. So this is the key info for VG import.