HPE GreenLake Administration
- Community Home
- >
- Servers and Operating Systems
- >
- Operating Systems
- >
- Operating System - HP-UX
- >
- Ignite client boot problems
Operating System - HP-UX
1837365
Members
3547
Online
110116
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
03-07-2006 01:45 AM
03-07-2006 01:45 AM
Ignite client boot problems
Hi!
I'm trying to use Ignite-server for installing OS, like 11.23 or 11.11.
For regret Ignite use bootpd for booting
the Client mashine for installation and for
this reason the both mashines must be in
the same VLAN. But I have a systems in
different lans: 192.168.24.x; 192.168.1.x
and so on... So is there any experiance in "trunking", where the same port of
switch for Ignite-server become part of
2-3 VLANs.
How I could organize that?
I'm trying to use Ignite-server for installing OS, like 11.23 or 11.11.
For regret Ignite use bootpd for booting
the Client mashine for installation and for
this reason the both mashines must be in
the same VLAN. But I have a systems in
different lans: 192.168.24.x; 192.168.1.x
and so on... So is there any experiance in "trunking", where the same port of
switch for Ignite-server become part of
2-3 VLANs.
How I could organize that?
2 REPLIES 2
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
03-07-2006 01:58 AM
03-07-2006 01:58 AM
Re: Ignite client boot problems
I know some Cisco switches will allow multiple VLANs to be assigned to a port. I'm sure this is a pretty common feature. However, just because you configure the switch to show the server on all the VLANs doesn't necessarily mean you'll be able to boot all of the clients from the server without a boot helper. They still need to be on the same IP subnet to do the bootp stuff. If they are on different IP subnets, requiring a router to communicate, then you still need the boot helper even if they are on the same VLAN.
--
Jeff Traigle
Jeff Traigle
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
03-07-2006 02:02 AM
03-07-2006 02:02 AM
Re: Ignite client boot problems
Shalom Inesa,
Some vlan situations require a boot helper machine to get the needed traffic from client to server.
Last I checked Ignite boots had to also be on the built in NIC, not any add in cards. When possible, I set up a cisco switch and private lan for boots to get around VLAN problems.
SEP
Some vlan situations require a boot helper machine to get the needed traffic from client to server.
Last I checked Ignite boots had to also be on the built in NIC, not any add in cards. When possible, I set up a cisco switch and private lan for boots to get around VLAN problems.
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