GreenLake Administration
- Community Home
- >
- Servers and Operating Systems
- >
- Operating Systems
- >
- Operating System - HP-UX
- >
- ignite booting
Operating System - HP-UX
1849589
Members
6460
Online
104044
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
Forums
Discussions
back
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
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-03-2003 09:53 AM
04-03-2003 09:53 AM
Hi,
This is for new installation.
I was told ignite client can talk to ignite server only using LAN0.
If I want to use other lan such as 4-PORT lan card , Is it possible? How to do it?
Thanks.
This is for new installation.
I was told ignite client can talk to ignite server only using LAN0.
If I want to use other lan such as 4-PORT lan card , Is it possible? How to do it?
Thanks.
Never quit
Solved! Go to Solution.
3 REPLIES 3
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
04-03-2003 11:40 AM
04-03-2003 11:40 AM
Re: ignite booting
Raj,
That's what the Ignite-UX Administrator's manual says. I haven't tried to do what you propose, but I suspect this limitation is due to the use of bootp. This also requires the Ignite client to be on the same subnet as the server, unless a boot helper us used.
Will the PDC allow you to boot from the 4-port LAN card? If not, I believe that you're stuck with the core LAN interface.
Regards,
Dave
p.s. Maybe somebody with more experience on "current" systems can provide more help. I'm stuck with old Nova-class and 700-series workstations...
That's what the Ignite-UX Administrator's manual says. I haven't tried to do what you propose, but I suspect this limitation is due to the use of bootp. This also requires the Ignite client to be on the same subnet as the server, unless a boot helper us used.
Will the PDC allow you to boot from the 4-port LAN card? If not, I believe that you're stuck with the core LAN interface.
Regards,
Dave
p.s. Maybe somebody with more experience on "current" systems can provide more help. I'm stuck with old Nova-class and 700-series workstations...
Romans 8:28
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
04-03-2003 11:51 AM
04-03-2003 11:51 AM
Solution
You can only boot an ignite client on lan0
After you boot it, you can do the system transfer through your 4 port lan card, thats just Ignite configuration.
Check this on the server:
instl_adm -d
instl_adm -d >/tmp/address.out
vi /tmp/address.out => correct the IP Address
instl_adm -f /tmp/address.out
With this methodology can run the Ignite push or pull after the client boots on via lan0 with any network parameters you want.
Here is my output.
[5001#] instl_adm -d
# instl_adm defaults:
# NOTE: Manual additions between the lines containing "instl_adm defaults"
# and "end instl_adm defaults" will not be preserved.
server="10.1.11.50"
netmask[]="255.255.0.0"
Yes, I've dealt with this issue in real life.
SEP
After you boot it, you can do the system transfer through your 4 port lan card, thats just Ignite configuration.
Check this on the server:
instl_adm -d
instl_adm -d >/tmp/address.out
vi /tmp/address.out => correct the IP Address
instl_adm -f /tmp/address.out
With this methodology can run the Ignite push or pull after the client boots on via lan0 with any network parameters you want.
Here is my output.
[5001#] instl_adm -d
# instl_adm defaults:
# NOTE: Manual additions between the lines containing "instl_adm defaults"
# and "end instl_adm defaults" will not be preserved.
server="10.1.11.50"
netmask[]="255.255.0.0"
Yes, I've dealt with this issue in real life.
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
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
04-03-2003 12:06 PM
04-03-2003 12:06 PM
Re: ignite booting
Thanks, Steve!
That's why you have that nice, shiny crown and I've just got this battered ole painter's cap... :)
Regards,
Dave
That's why you have that nice, shiny crown and I've just got this battered ole painter's cap... :)
Regards,
Dave
Romans 8:28
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 2026 Hewlett Packard Enterprise Development LP