NetBootSUS Appliance Setup Problems

[ryanatkisson]

Hey, Everyone! I'm hoping you can help me with my latest issue I'm having. Our Xserve that previously had been hosting our NetBoot volumes has been having more and more frequent hardware failures. As a result, we decided to offload the NetBoot duties to the NetBootSUS Appliance from JAMF.

We loaded the OVA file into our VMware vCenter system, set it up with a static IP and applied the necessary ACL and Firewire rules. Unfortunately, I can't get our Macs to see the server. Using this appliance, will you be able to see the NetBoot volume from the EFI boot screen on Macs?

Is there something simple that I might be missing?

external image link

[gregp]

Is the new IP address different than the old Xserve's and are the Macs not on one of the directly connected subnets?

[Brad_G]

You'll see the device as Faux NetBoot in the Sys Pref Startup Disk pane. That is unless you go in and hack the name (there is a thread on how to do this).

Also try from the Terminal:

sudo bless -netboot -server bsdp://your.ip.here -nextonly

And see if you can boot to it.

As a side note, unless you're only allowing those 3 subnets to boot to this server you could replace all those with just 131.247.0.0 255.255.0.0 (assume you knew that but thought I'd throw it out).

Hope This Helps
Brad

[ernstcs]

Ryan, what type of network hardware do you have? Cisco shop or other? I know that I was working with JAMF for an issue related to how Cisco hardware dealt with passing along the BDSP information. Some network switch brands do things differently.

For example, we got to a point of having a version that allowed us to see the NetBoot when you held option or the N key, but it won't see anything at the Startup Disk screen. As it turns out, the startup screen uses some random ports to get the information from NetBoot, where as the N key boot up process uses static ports. The Apple NetBoot server knew how to handle the requests on random ports. JAMF was going to see if they could get that to work as well.

I'm not sure an updated version of the appliance was pushed out yet with the new DHCPD to at least allow Cisco shops to use the N key.

This may not be the issue of course, but something to be aware of.

[ryanatkisson]

Thanks for all of your prompt replies! It's the first week of the semester and we're chomping at the bit to get our labs imaged!

The IP address is different that the previous xserve and we're attempting to NetBoot across many subnets (as had previously worked with the xserve). I've added the Subnet and Mask range that you recommended 131.247.0.0 255.255.0.0 and NetBoot Status is reporting green.

At this point in time, I don't see anything listed under the Sys Pref Startup Disk pane. I don't believe I've changed anything from Faux NetBoot. I tried running [sudo bless -netboot -server bsdp://your.ip.here -nextonly] from Terminal but I don't believe anything happened.

We have a wide range of network hardware across campus, which further complicates matters. I've had our Network group open up access to all necessary NetBoot ports listed on the apple KB article below.

http://support.apple.com/kb/TS3678

At this point, NetBoot Status is reporting green, but I'm not able to see any available netboot volumes in the EFI boot screen, the sys pref startup disk pane, or when I hold down N at boot time.

[jarednichols]

Troubleshoot. Change one thing. I suggest getting a machine (even temporarily) on the same subnet as your NetSUS appliance and testing it. If that works, then you know it's down to your network and not the appliance itself or the firewall.

[ernstcs]

Depending upon the network hardware then, and the IP address changing, have they updated the helper addresses on the network to point to the new IP for this?

And Jared's troubleshooting tip is spot on to verify the NetBoot is working.

[ryanatkisson]

I'd love to jump on the same subnet with a machine and try to netboot, but we have a rather complicated tiered system here on campus. I'm setting up a time to work with our Network group to try and troubleshoot.

Apart from the ports that Apple lists as necessary, are there any other ports/settings I should look into? The documentation for this net appliance is a bit lacking.

Also, thank you again for all of your help! It's greatly appreciated!

[Brad_G]

Another thing I just thought of....

As Jared said, try to get the NetSUS Appliance and a client on the same subnet so you can narrow what you're troubleshooting. I've spun up several on old hardware under my desk just to test. I know that doesn't fix you're production server but you can show your networking guys a working instance and they may be able to capture packet data that may help them.

The other thing I ran into is that while I could boot my older hardware across subnets to the Appliance for some reason our newest batch of iMacs and Minis will not. The Appliance had to be on the same subnet. A coworker here has been working with Apple regarding some troubles with netboot. So if you have some other clients to test I'd try that. That won't make figuring out the problem any easier but may prove you've got the right ports open etc.

Brad

[jarednichols]

If you've got that complicated of a network setup, you may also want to re-think how you're imaging. Perhaps booting from a USB stick would be easier.

[chriscollins]

If I read correct you are using a different static IP than your old Xserve and booting across subnets. You probably need to have the network group change the IPHelper settings on your networking gear to the new IP of the appliance.

[ryanatkisson]

Thanks for your suggestions, everyone!

I ended up formatting the xserve and installing 10.8 server. It's been working for the most part... still having the occasional issue accessing the server on some subnets.

For tech groups that are having trouble, I've started making bootable flash drives. Can't wait to ditch NetBoot!