HPE GreenLake Administration
- Community Home
- >
- Servers and Operating Systems
- >
- Operating Systems
- >
- Operating System - HP-UX
- >
- Move Vpar from 1 Npar to another
Operating System - HP-UX
1834732
Members
2261
Online
110070
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
Go to solution
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
04-10-2006 01:50 AM
04-10-2006 01:50 AM
We plan on moving an existing vpar from npar1 to npar0 and the existing vpar from npar0 to npar1 (basically a vpar swap between npar's Both vpar's boot from our SAN. I'm in the preliminary stages and know very little about vpar's, so I thought I'd post this for some help/guidance. Anyone have experience with this?
Thanks,
Michelle
Thanks,
Michelle
Solved! Go to Solution.
2 REPLIES 2
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
04-10-2006 02:41 AM
04-10-2006 02:41 AM
Solution
Michelle,
You can do this 2 ways:
(1) w/o SAN rezone (Downtime needed on the nPars to swap cards between nPar0 and nPar1)
(2) w/ SAN rezone (No Downtime on the nPars)
Method 1 & 2 are similar, the only difference is the downtime required for (1) with the swap of the cards whilst method (2) does not.
The following is the procedure:
1. Login to the vPars to be swapped.
2. Get your SAN boot Path:
# lvlnboot -v |grep "Boot Disk"
/dev/dsk/c11t15d5 (0/0/12/1/0/4/0.2.19.0.7.15.5) -- Boot Disk
3. Shutdown the vPar.
4. From another vPar on the same nPar, remove the vPar to be moved:
# vparremove -p vparX
5. If Method 1 - shutdown all remaining vPars/nPars.
6. If Method 2 - no need to shutdown the other vPars, Zone your SAN so vParX and vParY HBAs are swapped.
For each vPar:
7. Login to a running vPar (say vParA) on the same nPar where you want to re-establish the moved vPar
8. Recreate the vPar,
vparcreate -p vparx -a cpu::2 -a cpu:::2:8 -a mem::8912 \
-a io:a.b.c -a io:x.y.z \
-a io:x/y/x/1/0/4/0.2.19.0.7.15.5:BOOT
Where a.b.c or x.y.z are the new locations of your migrated vPar's I.O devices (FC-HBA, LAN, etc..) on its new nPar.
Note that you need to be familiar with determining HW Paths.
Let me know if you need help in this area.
9. Boot your migrated vPar in LVM Maint mode to fix up your vg00 and fix your LAN.
vparA# vparboot -p vparx -o "-lm"
Let me know if you need help in this area as well.
10. vg00 and LAN fixed, reboot multi user...
Done!
You can do this 2 ways:
(1) w/o SAN rezone (Downtime needed on the nPars to swap cards between nPar0 and nPar1)
(2) w/ SAN rezone (No Downtime on the nPars)
Method 1 & 2 are similar, the only difference is the downtime required for (1) with the swap of the cards whilst method (2) does not.
The following is the procedure:
1. Login to the vPars to be swapped.
2. Get your SAN boot Path:
# lvlnboot -v |grep "Boot Disk"
/dev/dsk/c11t15d5 (0/0/12/1/0/4/0.2.19.0.7.15.5) -- Boot Disk
3. Shutdown the vPar.
4. From another vPar on the same nPar, remove the vPar to be moved:
# vparremove -p vparX
5. If Method 1 - shutdown all remaining vPars/nPars.
6. If Method 2 - no need to shutdown the other vPars, Zone your SAN so vParX and vParY HBAs are swapped.
For each vPar:
7. Login to a running vPar (say vParA) on the same nPar where you want to re-establish the moved vPar
8. Recreate the vPar,
vparcreate -p vparx -a cpu::2 -a cpu:::2:8 -a mem::8912 \
-a io:a.b.c -a io:x.y.z \
-a io:x/y/x/1/0/4/0.2.19.0.7.15.5:BOOT
Where a.b.c or x.y.z are the new locations of your migrated vPar's I.O devices (FC-HBA, LAN, etc..) on its new nPar.
Note that you need to be familiar with determining HW Paths.
Let me know if you need help in this area.
9. Boot your migrated vPar in LVM Maint mode to fix up your vg00 and fix your LAN.
vparA# vparboot -p vparx -o "-lm"
Let me know if you need help in this area as well.
10. vg00 and LAN fixed, reboot multi user...
Done!
Hakuna Matata.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
04-18-2006 02:30 AM
04-18-2006 02:30 AM
Re: Move Vpar from 1 Npar to another
I'm in the middle of this now, BUT, I can't seem to boot off of the root disk even though I shared the disk between the 2 systems. Every time I try, I receive a system panic. Any ideas?
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