HPE GreenLake Administration
- Community Home
- >
- Servers and Operating Systems
- >
- Operating Systems
- >
- Operating System - HP-UX
- >
- Trouble with bootsys
Operating System - HP-UX
1834470
Members
3020
Online
110067
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
11-21-2005 01:03 AM
11-21-2005 01:03 AM
Trouble with bootsys
Hello,
I need to merge possibly incompatible system SD bundles (see my other recent threads).
That's why I am currently struggling to verify this VPars Ignite image.
Because I have no tape drive attached to this VPar I had to setup an Ignite server.
I did provide a dedicated Ignite LAN by simply connecting the built-in igelan NICs of two VPars' NICs point-to-point.
I then managed to perform a make_net_recovery of the VPar that acts as the Ignite client for which I need to merge the critical system depots.
# tail -3 /var/opt/ignite/clients/0x00127995E58C/recovery/latest/recovery.log>
======= 11/20/05 19:47:24 MET make_net_recovery completed with warnings
I tried all sorts of booting this vpwerra into
an Ignite cold-install screen.
But all methods I tried (execept for the vparboot) autoboot the vpar immediately to a normal runlevel.
Of course I started first from the Ignite server by doing symply (explicitly with the wait switch)
# bootsys -vw
Then I tried from the ignite client
# bootsys -wc
Then I tried a conventional shutdown -r on the ignite client.
During all these attempts I had the MP console open lingering on vpwerra (i.e. ^A)
lurking for the Ignite welcome screen, or some "hit any key" display to get interactive.
Finally I tried the vparboot command.
# vparboot -p vpwerra -I,/opt/ignite/boot/Rel_B.11.11/WINSTALL
vparboot: Booting vpwerra. Please wait...
This finally got me to the ignite installation screen at the MP console.
For now this seems acceptable.
But later I probably would rather like to establish autoinstallation through the bootsys CLI (no fumbling with X or MP console).
What do I need to configure for bootsys to work?
Maybe the AUTO boot string needs to be changed?
# vgdisplay -v vg00|grep PV\ Name
PV Name /dev/dsk/c4t6d0
PV Name /dev/dsk/c6t6d0
# lifcp /dev/rdsk/c4t6d0:AUTO -
hpux /stand/vpmon -a
I need to merge possibly incompatible system SD bundles (see my other recent threads).
That's why I am currently struggling to verify this VPars Ignite image.
Because I have no tape drive attached to this VPar I had to setup an Ignite server.
I did provide a dedicated Ignite LAN by simply connecting the built-in igelan NICs of two VPars' NICs point-to-point.
I then managed to perform a make_net_recovery of the VPar that acts as the Ignite client for which I need to merge the critical system depots.
# tail -3 /var/opt/ignite/clients/0x00127995E58C/recovery/latest/recovery.log>
======= 11/20/05 19:47:24 MET make_net_recovery completed with warnings
I tried all sorts of booting this vpwerra into
an Ignite cold-install screen.
But all methods I tried (execept for the vparboot) autoboot the vpar immediately to a normal runlevel.
Of course I started first from the Ignite server by doing symply (explicitly with the wait switch)
# bootsys -vw
Then I tried from the ignite client
# bootsys -wc
Then I tried a conventional shutdown -r on the ignite client.
During all these attempts I had the MP console open lingering on vpwerra (i.e. ^A)
lurking for the Ignite welcome screen, or some "hit any key" display to get interactive.
Finally I tried the vparboot command.
# vparboot -p vpwerra -I
vparboot: Booting vpwerra. Please wait...
This finally got me to the ignite installation screen at the MP console.
For now this seems acceptable.
But later I probably would rather like to establish autoinstallation through the bootsys CLI (no fumbling with X or MP console).
What do I need to configure for bootsys to work?
Maybe the AUTO boot string needs to be changed?
# vgdisplay -v vg00|grep PV\ Name
PV Name /dev/dsk/c4t6d0
PV Name /dev/dsk/c6t6d0
# lifcp /dev/rdsk/c4t6d0:AUTO -
hpux /stand/vpmon -a
Madness, thy name is system administration
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