HPE GreenLake Administration
- Community Home
- >
- Servers and Operating Systems
- >
- Operating Systems
- >
- Operating System - HP-UX
- >
- Move OS/Boot disks from one nPar/server to Another...
Operating System - HP-UX
1834142
Members
2133
Online
110064
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
06-20-2005 05:35 AM
06-20-2005 05:35 AM
We've a requirement to move nPars/servers around as the need arises. Due to certain limitations of simply of re-igniting from backup (Net or Tape), we usually simply move the OS disks around (and just do the vg00 fix/lvlnboot stuff - which in itself sometimes offer some problems ..).
However our device instances are always incremented.. i.e. say on the old server my HBAs are td0 and td1, on the new environment, the HBAs will be seen as td2 and td3. The fix that I've always employed is to simply remove /etc/ioconfig and /stand/ioconfig - but I suspect this may not be the correct way and there must be another way.. which I am asking - how do you guys do it?
However our device instances are always incremented.. i.e. say on the old server my HBAs are td0 and td1, on the new environment, the HBAs will be seen as td2 and td3. The fix that I've always employed is to simply remove /etc/ioconfig and /stand/ioconfig - but I suspect this may not be the correct way and there must be another way.. which I am asking - how do you guys do it?
Hakuna Matata.
Solved! Go to Solution.
3 REPLIES 3
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
06-20-2005 06:46 AM
06-20-2005 06:46 AM
Solution
0) ioscan -f | grep -e "INTERFACE" \
-e "DEVICE" | grep -v -i "target" | \
awk '{printf("%-20.20s %-12.12s %3d\n, $3,$1,($2 + 0))}' | sort > /myfile
1) Use vi (or the text editor of choice) and change the "ext_bus" as needed/desired.
2) mv /stand/ioconfig /stand/ioconfig.SAV
mv /etc/ioconfig /etc/ioconfig.SAV
shutdown -ry 0
Because the ioconfig files are missing, you will get an ioinitrc prompt.
At the ioinitrc prompt type "/sbin/ioinit -c"
to rebuild the files.
3) Now apply your changes.
/sbin/ioinit -f /myfile -r
You can ignore warnings "Input is identical to kernel" but not errors "instance number 4 already exists for class"
The -r ioinit option causes the system to reboot immediately.
If you like this same procedure can also be used to reorder lan instances.
-e "DEVICE" | grep -v -i "target" | \
awk '{printf("%-20.20s %-12.12s %3d\n, $3,$1,($2 + 0))}' | sort > /myfile
1) Use vi (or the text editor of choice) and change the "ext_bus" as needed/desired.
2) mv /stand/ioconfig /stand/ioconfig.SAV
mv /etc/ioconfig /etc/ioconfig.SAV
shutdown -ry 0
Because the ioconfig files are missing, you will get an ioinitrc prompt.
At the ioinitrc prompt type "/sbin/ioinit -c"
to rebuild the files.
3) Now apply your changes.
/sbin/ioinit -f /myfile -r
You can ignore warnings "Input is identical to kernel" but not errors "instance number 4 already exists for class"
The -r ioinit option causes the system to reboot immediately.
If you like this same procedure can also be used to reorder lan instances.
If it ain't broke, I can fix that.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
06-21-2005 06:55 AM
06-21-2005 06:55 AM
Re: Move OS/Boot disks from one nPar/server to Another - Procedure and How to Reorder Bus instances
A. Clay - what if I do not do step 0? A number of times in the past - I do not do step 0 and the effect after 2 reboots is that all my device instances now start from 0 (lan and scsi/fc hbas..).
Hakuna Matata.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
06-21-2005 01:17 PM
06-21-2005 01:17 PM
Re: Move OS/Boot disks from one nPar/server to Another - Procedure and How to Reorder Bus instances
Step 0 gives you the text file that you edit. If will list all the interfaces (SCSI and lan) as they currently are. You then edit it to reflect your desired changes.
If it ain't broke, I can fix that.
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