HPE GreenLake Administration
- Community Home
- >
- Servers and Operating Systems
- >
- Operating Systems
- >
- Operating System - HP-UX
- >
- Re: Boot from make_net_recovery image
Operating System - HP-UX
1842046
Members
2016
Online
110185
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
09-17-2007 03:47 AM
09-17-2007 03:47 AM
Boot from make_net_recovery image
How does one boot from the a make_net_recovery image. This is what I have so far,
Main Menu: Enter command or menu > sea lan install
Searching for potential boot device(s) - on Path 0/1/2/0
This may take several minutes.
To discontinue search, press any key (termination may not be immediate).
IODC
Path# Device Path (dec) Device Path (mnem) Device Type Rev
----- ----------------- ------------------ ----------- ----
P0 0/1/2/0 lan.10.228.59.77 LAN Module 4
Main Menu: Enter command or menu > boot lan install
Interact with IPL (Y, N, or Cancel)?> n
Booting...
Boot IO Dependent Code (IODC) revision 4
HARD Booted.
ISL Revision A.00.44 Mar 12, 2003
ISL booting hpux KernelPrompt "Choose an operating system to install that your hardware supports :" 120 1
1. target OS is B.11.23 PA
2. Exit
Choose an operating system to install that your hardware supports :
Problem is that I want to select the ignite backup and not the OS golden image.
Main Menu: Enter command or menu > sea lan install
Searching for potential boot device(s) - on Path 0/1/2/0
This may take several minutes.
To discontinue search, press any key (termination may not be immediate).
IODC
Path# Device Path (dec) Device Path (mnem) Device Type Rev
----- ----------------- ------------------ ----------- ----
P0 0/1/2/0 lan.10.228.59.77 LAN Module 4
Main Menu: Enter command or menu > boot lan install
Interact with IPL (Y, N, or Cancel)?> n
Booting...
Boot IO Dependent Code (IODC) revision 4
HARD Booted.
ISL Revision A.00.44 Mar 12, 2003
ISL booting hpux KernelPrompt "Choose an operating system to install that your hardware supports :" 120 1
1. target OS is B.11.23 PA
2. Exit
Choose an operating system to install that your hardware supports :
Problem is that I want to select the ignite backup and not the OS golden image.
1 REPLY 1
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
09-17-2007 04:05 AM
09-17-2007 04:05 AM
Re: Boot from make_net_recovery image
Shalom,
My general approach would be.
Bo P4
Y to interact question
boot lan.10.228.59.77 install
Then watch the processes on the Ignite server.
You should see some evidence of the attempt in the Ignite logs and some boot processes attempting to assign an IP address.
We need to find the problem before we can fix it.
Have you all the infrastructure in place on the Ignite server to serve up the images? Is the NFS share point for the images permitting access (showmount -e).
Lots of things to check.
Detective work, thats what it is.
I suspect some setup issues exist on the Ignite server. Logs might help. /var/opt/ignite
SEP
My general approach would be.
Bo P4
Y to interact question
boot lan.10.228.59.77 install
Then watch the processes on the Ignite server.
You should see some evidence of the attempt in the Ignite logs and some boot processes attempting to assign an IP address.
We need to find the problem before we can fix it.
Have you all the infrastructure in place on the Ignite server to serve up the images? Is the NFS share point for the images permitting access (showmount -e).
Lots of things to check.
Detective work, thats what it is.
I suspect some setup issues exist on the Ignite server. Logs might help. /var/opt/ignite
SEP
Steven E Protter
Owner of ISN Corporation
http://isnamerica.com
http://hpuxconsulting.com
Sponsor: http://hpux.ws
Twitter: http://twitter.com/hpuxlinux
Founder http://newdatacloud.com
Owner of ISN Corporation
http://isnamerica.com
http://hpuxconsulting.com
Sponsor: http://hpux.ws
Twitter: http://twitter.com/hpuxlinux
Founder http://newdatacloud.com
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