HPE GreenLake Administration
- Community Home
- >
- Servers and Operating Systems
- >
- Operating Systems
- >
- Operating System - HP-UX
- >
- Contoller and Target number changed on SAN luns
Operating System - HP-UX
1833779
Members
2185
Online
110063
Solutions
Forums
Categories
Company
Local Language
back
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
back
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
Blogs
Information
Community
Resources
Community Language
Language
Forums
Blogs
Topic Options
- 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
07-25-2009 05:22 AM
07-25-2009 05:22 AM
Contoller and Target number changed on SAN luns
We got our storage system upgraded and after rebooting the server all the storage luns got assigned to the server with new controller and target number's. But we don't have map file to import the VG's.
Please let me know the process to update the all VG's with the new controller and target devices.
Thanks in Advance for the help.
Please let me know the process to update the all VG's with the new controller and target devices.
Thanks in Advance for the help.
1 REPLY 1
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
07-25-2009 11:27 AM
07-25-2009 11:27 AM
Re: Contoller and Target number changed on SAN luns
Even though the controller and target numbers are currently not correct in the LVM configuration, you can still export the VGs.
The system does not really need to write anything to the VG to export it; it just removes the data from the /etc/lvmtab file and puts the VGID in the map file... and you want that map file.
You might want to run "rmsf -a" to all the old LUN devices that will now be showing as NO_HW in the ioscan listing.
Then run "ioscan -fnCdisk" and then "insf -Cdisk" to make sure all the new LUN devices are detected.
Then, for each VG:
ll /dev/vg/group
vgexport -v -s -m vg.map vg
mkdir /dev/vg
mknod /dev/vg/group c 64
vgimport -v -s -m vg.map vg
And you're done.
This procedure is for 11.23 and older; for 11.31, you'll need to remember the new agile device names, and the major number of the VG group file may not always be 64 (because of LVM 2.x).
MK
The system does not really need to write anything to the VG to export it; it just removes the data from the /etc/lvmtab file and puts the VGID in the map file... and you want that map file.
You might want to run "rmsf -a" to all the old LUN devices that will now be showing as NO_HW in the ioscan listing.
Then run "ioscan -fnCdisk" and then "insf -Cdisk" to make sure all the new LUN devices are detected.
Then, for each VG:
ll /dev/vg
vgexport -v -s -m vg
mkdir /dev/vg
mknod /dev/vg
vgimport -v -s -m vg
And you're done.
This procedure is for 11.23 and older; for 11.31, you'll need to remember the new agile device names, and the major number of the VG group file may not always be 64 (because of LVM 2.x).
MK
MK
The opinions expressed above are the personal opinions of the authors, not of Hewlett Packard Enterprise. By using this site, you accept the Terms of Use and Rules of Participation.
Company
Events and news
Customer resources
© Copyright 2025 Hewlett Packard Enterprise Development LP