- Community Home
- >
- Servers and Operating Systems
- >
- Operating Systems
- >
- Operating System - HP-UX
- >
- igniting a client in a different subnet
Categories
Company
Local Language
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
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
Community
Resources
Forums
Blogs
- 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-18-2002 05:26 AM
04-18-2002 05:26 AM
Bootsys -w system1:ip-address (where ip-address is the currently configured address of the system.)
Then bootsys pulls the install kernal down from the remote ignite server before booting.
Target system boots with ip-address from initial command.
Wouldn't bootsys have to configure the gateway also in order to find the ignite server?
Solved! Go to Solution.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
04-18-2002 05:52 AM
04-18-2002 05:52 AM
Re: igniting a client in a different subnet
This should help:-
http://forums.itrc.hp.com/cm/QuestionAnswer/1,,0x84fcc6af36b7d5118ff10090279cd0f9,00.html
Paula
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
04-18-2002 06:55 AM
04-18-2002 06:55 AM
Re: igniting a client in a different subnet
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
04-18-2002 07:07 AM
04-18-2002 07:07 AM
Re: igniting a client in a different subnet
Setting up the boot helper:
1) Install Ignite-UX minimum core fonctionality on the helper.
2) On the helper, run the following command:
/opt/ignite/bin/instl_adm -t Ignite-UX_server_IP
3) Verify with :
/opt/ignite/bin/instl_adm -d
4) Specify a temporary IP adress for the helper in file:
/etc/opt/ignite/instl_boottab
Frank.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
04-18-2002 07:20 AM
04-18-2002 07:20 AM
Re: igniting a client in a different subnet
Can I ignite a remote system in a different subnet without a boot helper?
I thought bootsys was the answer. Maybe I'm wrong.
Cheers...
Ian
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
04-18-2002 07:42 AM
04-18-2002 07:42 AM
SolutionSorry, w/o the Ignite server OR the boothelper in the same subnet, you're not going to be able to Ignite that system.
Better break out the CDs or move the server into the Ignite subnet.
Rgds,
Jeff
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
04-18-2002 08:13 AM
04-18-2002 08:13 AM
Re: igniting a client in a different subnet
That wasn't the answer I was hoping for, but a definitive one none the less. Thanks again. I'm off to France and Germany. Bummer!! :-)