HPE GreenLake Administration
- Community Home
- >
- Servers and Operating Systems
- >
- Operating Systems
- >
- Operating System - HP-UX
- >
- MAC filtering and booting PXE
Operating System - HP-UX
1833178
Members
2650
Online
110051
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
11-21-2007 08:48 PM
11-21-2007 08:48 PM
Hi!
Here's my problem with PXE in Ignite UX
A client has two Superdomes, and each one have a Ignite server (backing up the other SD's vPars). I have reserved MACs in /etc/opt/ignite/instl_boottab for assigning the right IP to every machine (no DHCP).
The questions are:
1. When trying to boot a vPar by PXE for recovery is the first replying server the one that will boot the machine, isnt it??
2. What happens if it's not the right Ignite server for that Superdome?
Does it checks it's not a registered client for that server, and don't reply to the boot petition?
3. Is there any util for checking Ignite PXE like bootpquery?
PD: If there's anything that you couldn't undestand, please ask for explanation... I almost forgot my english :D
Thanks in advance,
Cristian Casablanca
Here's my problem with PXE in Ignite UX
A client has two Superdomes, and each one have a Ignite server (backing up the other SD's vPars). I have reserved MACs in /etc/opt/ignite/instl_boottab for assigning the right IP to every machine (no DHCP).
The questions are:
1. When trying to boot a vPar by PXE for recovery is the first replying server the one that will boot the machine, isnt it??
2. What happens if it's not the right Ignite server for that Superdome?
Does it checks it's not a registered client for that server, and don't reply to the boot petition?
3. Is there any util for checking Ignite PXE like bootpquery?
PD: If there's anything that you couldn't undestand, please ask for explanation... I almost forgot my english :D
Thanks in advance,
Cristian Casablanca
Solved! Go to Solution.
3 REPLIES 3
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
11-21-2007 10:37 PM
11-21-2007 10:37 PM
Solution
Shalom,
My understanding is that Ignite does not use PXE at all. It interferes with and can be confused by having PXE servers on the same subnet
IF your Ignite server is on the same subnet
boot
intervene
bo lan.ip_of_ignite_server install
# example
bo 192.168.0.10 install
Use the IP address of the boot helper if thats what has been set up.
This methodology should avoid any issues with accidently choosing to boot from some PXE server that can not possibly service Ignite in the first place.
SEP
My understanding is that Ignite does not use PXE at all. It interferes with and can be confused by having PXE servers on the same subnet
IF your Ignite server is on the same subnet
boot
intervene
bo lan.ip_of_ignite_server install
# example
bo 192.168.0.10 install
Use the IP address of the boot helper if thats what has been set up.
This methodology should avoid any issues with accidently choosing to boot from some PXE server that can not possibly service Ignite in the first place.
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
11-22-2007 01:00 AM
11-22-2007 01:00 AM
Re: MAC filtering and booting PXE
I was thinking about booting with
boot lan install
and I was wondering about what server should reply, but with your note, replacing the "lan" with its IP, I think it solves the trouble...
Thanks a lot!!!
Cristian
boot lan install
and I was wondering about what server should reply, but with your note, replacing the "lan" with its IP, I think it solves the trouble...
Thanks a lot!!!
Cristian
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
11-22-2007 01:01 AM
11-22-2007 01:01 AM
Re: MAC filtering and booting PXE
Close the thread due to solved post.
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