- Community Home
- >
- Servers and Operating Systems
- >
- Operating Systems
- >
- Operating System - HP-UX
- >
- Unique identifier for SAN disk but reproducable at...
Categories
Company
Local Language
Forums
Discussions
Forums
- Data Protection and Retention
- Entry Storage Systems
- Legacy
- Midrange and Enterprise Storage
- Storage Networking
- HPE Nimble Storage
Discussions
Forums
Discussions
Discussions
Discussions
Forums
Discussions
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
- BladeSystem Infrastructure and Application Solutions
- Appliance Servers
- Alpha Servers
- BackOffice Products
- Internet Products
- HPE 9000 and HPE e3000 Servers
- Networking
- Netservers
- Secure OS Software for Linux
- Server Management (Insight Manager 7)
- Windows Server 2003
- Operating System - Tru64 Unix
- ProLiant Deployment and Provisioning
- Linux-Based Community / Regional
- Microsoft System Center Integration
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Community
Resources
Forums
Blogs
- Subscribe to RSS Feed
- Mark Topic as New
- Mark Topic as Read
- Float this Topic for Current User
- Bookmark
- Subscribe
- Printer Friendly Page
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
11-16-2009 05:38 AM
11-16-2009 05:38 AM
Is there a unique identifier that I can reference at the HP-UX level on each device? I cannot see the WWN of the LUN using vendor tools (we are a pvlinks setup), is there another way to track the disk by a unique identifier? I need to reimport the disks back to their VGs after the move, with something more definitive than "vgscan".
Share and Enjoy! Ian
PS. Any posting to reference using PowerPath will result in zero points.
Solved! Go to Solution.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
11-16-2009 06:04 AM
11-16-2009 06:04 AM
Re: Unique identifier for SAN disk but reproducable at OS level
Hope this helps!
Regards
Torsten.
__________________________________________________
There are only 10 types of people in the world -
those who understand binary, and those who don't.
__________________________________________________
No support by private messages. Please ask the forum!
If you feel this was helpful please click the KUDOS! thumb below!

- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
11-16-2009 10:11 AM
11-16-2009 10:11 AM
Re: Unique identifier for SAN disk but reproducable at OS level
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
11-16-2009 10:14 AM
11-16-2009 10:14 AM
Re: Unique identifier for SAN disk but reproducable at OS level
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
11-16-2009 11:43 PM
11-16-2009 11:43 PM
Re: Unique identifier for SAN disk but reproducable at OS level
With the device files changing path, the mapfiles are rendered unusable, unless you know of a way around this?
trusting in "vgscan" is a little too risky for me.
Share and Enjoy! Ian
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
11-16-2009 11:49 PM
11-16-2009 11:49 PM
Solution# vgexport -v -s -m /tmp/vgXX.map vgXX
while importing the system identifies the disks using the VGID, you don't need to specify the disk device.
Hope this helps!
Regards
Torsten.
__________________________________________________
There are only 10 types of people in the world -
those who understand binary, and those who don't.
__________________________________________________
No support by private messages. Please ask the forum!
If you feel this was helpful please click the KUDOS! thumb below!

- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
11-17-2009 02:57 AM
11-17-2009 02:57 AM
Re: Unique identifier for SAN disk but reproducable at OS level
If you use vgimport -s, there is no need to list the PVs manually: the system reads the VGID from the map file, then examines every PV it currently sees. All the PVs with the correct VGID are automatically included in the import operation. If the same PV is seen through multiple paths (=multipath LUN), the first discovered path becomes the primary one and all the other paths are listed as alternate paths.
We've been using this trick in multiple storage migrations. It works very well.
Only HP-UX 11.31 can display WWNs directly; read the man page of ioscan if you have 11.31.
There is a free "inq" tool available from EMC:
ftp://ftp.emc.com/pub/elab/inquiry/
Get the newest version: currently it seems to be v7.0.1.0.
(Note: the inq.hpux1100 binary is for 32-bit HP-UX PA-RISC systems, inq.hpux64 is for 64-bit capable PA-RISC systems, inq.HPUXIA64 is for Itaniums.)
Drop it into a suitable location (/usr/local/bin maybe?), set it executable (chmod a+x) and use "inq.
It can list the disks in many ways, either by WWN or even directly by the format used in the configuration of various EMC storage systems.
MK
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
11-18-2009 12:23 AM
11-18-2009 12:23 AM