Mac Thread, Netboot Problem Across Switches in Technical; Not sure whether this should be in this forum or the Network forum (chose this one in the end as ...
13th February 2010, 09:58 PM #1
Netboot Problem Across Switches
Not sure whether this should be in this forum or the Network forum (chose this one in the end as it sems specific to the Macs).
Right, we are mainly a PC school with PXE/WDS deployment working fine across switches and VLANs.
Before I go any further I need to say that I know nothing about Macs and the current config was setup by another member of staff who does know about Macs.
For the Apple Macs we use Netboot, which works fine from the core switch (HP Procurve 5412zl) and also from a HP Procurve 2900 plugged into it (also across VLANs on these two switches).
However, Macs plugged into a 3com 4250T, 3com 2824-sfp plus or 3com 4500 don't work.
The PCs connected to these switches PXE boot fine.
There are appropriate ip helper addresses added to the HP 5412zl (which is acting as the router for the network).
Is there something I need to set on the 3coms or does anyone else have a solution?
I know of the NBAS option, but this means changing a setting on each Mac's firmware, which I am reluctant to do - plus I'd rather get it working the "proper" way.
IDG Tech News
12th March 2010, 11:18 PM #2
Ok, we've narrowed this down:
1. an iMac plugged into the switch netboots fine
2. a Mac Pro doesn't UNLESS it is plugged into the core switch (same switch as the Mac Server)
I'm guessing Mac Pros do their "netbooting" differently and, as such, can't handle broadcasts between switches properly if they are not in the default VLAN
Not sure what the solution is - can't imagine having to shift around 30 macs all the way across school to re-image them is going to be practical
13th March 2010, 12:07 AM #3
You need to add the address of the Netboot server as an ip helper for the vlan (you can have multiple).
It doesn't need to be a dhcp server, just needs to see the request so it can send a response back for the remote boot.
Ah, you already have this set for the procurve and it works. If the 3coms don't bundle the remote boot requests along with dhcp traffic like the procurves do then you may be out of luck.
Last edited by DMcCoy; 13th March 2010 at 12:10 AM.
13th March 2010, 12:14 AM #4
Hmm, now read your second post. Working for just the imacs is definately odd. Are the ports tagged or untagged? Does the netboot server show up when picking a startup disk in a machine that is already booted and working?
It wouldn't surprise me if the pros were broken in someway. Something always is with apple.
18th April 2010, 01:38 AM #5
- Rep Power
Richie - get yourself a mac that won't netboot, and open up terminal....type in
sudo bless --netboot --server bsdp://10.10.10.10
Change the IP to your netboot server, now try to netboot.
13th July 2011, 06:10 PM #6
- Rep Power
14th July 2011, 09:32 AM #7
I have found using the IP-helper address command to allow os x to netboot. I have configuration manager/WDS and deploystudio and both work happily together. I have found that you do not need to change any DHCP options for WDS or configuration manager.
14th July 2011, 01:54 PM #8
- Rep Power
By FN-GM in forum Windows Server 2008
Last Post: 19th August 2011, 12:47 PM
By Shorty in forum Wireless Networks
Last Post: 21st November 2008, 03:50 PM
By monkeyx in forum O/S Deployment
Last Post: 11th September 2008, 02:23 AM
By button_ripple in forum Hardware
Last Post: 1st April 2008, 12:11 AM
By tosca925 in forum Wireless Networks
Last Post: 6th February 2007, 10:10 AM
Users Browsing this Thread
There are currently 1 users browsing this thread. (0 members and 1 guests)