Netboot and DHCP Issue - Setting up AST Diagnostic Gateway

Question

Netboot and DHCP Issue - Setting up AST Diagnostic Gateway

Hi everyone,

I recently set up a new Mac Mini as a stand-alone server for the Apple Service Toolkit Diagnostic Gateway. Here are the specs of the Mini, if needed by anyone:

Mac OS X 10.6 Server (patched to 10.6.8)

2.66GHz Core 2 Duo

8 GB DDR3 RAM

I have followed Apple's instructions on how to install/configure AST Diagnostic Gateway from the Service Source page to the T. Installation was no problem and everything went smoothly.

In Server Admin, I turned on only NFS and NetBoot services (as per the instructions) and configured NetBoot to work via Ethernet with the AST image as the default. Both services are running. I DO NOT have DHCP turned on on this machine, namely because:

a.) We have a district DHCP server supplying IPs to all our machines, and

b.) The instructions from Apple actually say to avoid running any services on the AST Gateway machine besides NFS and NetBoot.

I gave the server a static IP and reserved it in our DHCP server. I also registered my Gateway Manager with my Apple ID and ASP location, etc. so it can connect to the repositories.

However, when I plug in a remote host on the same network segment (same subnet), it will not netboot. I get the flashing globe for about 20 - 30 seconds and then the system boots normally into the OS. When going into System Preferences > Startup Disk, it does not see the AST server.

If I turn AFP on, I can connect to it that way and view the image files, etc. The permissions are set so that everyone can read the image files.

What am I missing? The only thing I have been able to find so far are these entires in the NetBoot log within Server Admin:

Jul 6 13:06:48 localhost servermgrd[58]: servermgr_dhcp:bootp config:Error:Failed to create default subnet records

Jul 6 11:47:43 localhost configd[32]: bootp_session_transmit: bpf_write(en1) failed: Network is down (50)

It appears that the remote host is not getting a proper DHCP address and therefore cannot see the netboot server..?

Any suggestions or help would be greatly appreciated!

Apple Certified Macintosh Technician, Mac OS X (10.6.7), MacBook Pro 2.4GHz Core 2 Duo, iPhone 3GS

Posted on Jul 6, 2011 11:40 AM

Reply

Answer 1

May 26, 2017 11:37 PM in response to mberardinelli

Hello I see this post is old though has anyone does a MacOS Sierra AST I did just a few minutes ago. And wanted to know do I need to use apple toolkit from reading the article it seems I don't have to but it also stated 10.9 and later in which sierra is later version.

As I will test the AST prior to install, also what is a UUT as I did not see a configure dmg or settings to use for Sierra.

don't I need a certificate to tell AST I'm apple certified or linked to my GSX just wondering even though I logged in to get the software just thought it would need a token or something for extra security.

Finally could I clone my Mac and deploy an image out in my district or will I need to do different setups

Thanks all

Dan Sifu

Reply

Answer 2

Jul 7, 2011 9:30 AM in response to mberardinelli

The NetBoot service does not need to run on a server also running DHCP so you are ok on that front, you will only need AFP if you are going to use diskless NetBoot. Can you however provide more details as to your NetBoot configuration, e.g. what Interfaces have you enabled it to serve on, what archictectures are supported, have you configured any restrictions as to models that can connect, have you configured a filter for MAC addresses, etc.?

The first thing to do is to get things so the NetBoot image does show up in Startup Disks, then worry later about actually trying to NetBoot.

The error you listed of "Jul 6 11:47:43 localhost configd[32]: bootp_session_transmit: bpf_write(en1) failed: Network is down (50)" might be suggesting you have enabled the NetBoot service on a network interface which is not in use. Some models of Mac such as the Mac Pro and XServe have two Ethernet interfaces. Even on the Mac mini you are using the built-in Ethernet and built-in AirPort (WiFi) still count as two interfaces. On the Mac mini normally en0 is the built-in Ethernet and en1 is the AirPort.

Reply

Answer 3

Jul 7, 2011 10:35 AM in response to John Lockwood

Hi there and thanks for the reply!

At the moment I have the NetBoot service serving on built-in Ethernet (which makes that error on en1 all the more strange - I don't even have Airport turned on). In fact, the en0 port is the only one that populates in the list of available interfaces to use.

I have not configured any restrictions or filters or anything. Currently it is set to allow any connected host. I have logging set to High so I can catch anything that happens to come up.

I was just talking with our network admin and he's thinking we'll have to configure our DHCP server with some settings to point the Macs to the image file. (for example, we have some LTSP machines with reserved IPs in a group on the DHCP server that get PXE-boot settings from the group and thus are able to netboot to a terminal server session).

Reply

Answer 4

Aug 1, 2011 8:12 AM in response to mberardinelli

So we figured out that we need to create a group within our DHCP server such that any Mac that is also part of the group will be able to netboot to the AST image.

Does anyone know the root path I need to put in for the AST image? I'm looking through the gateway server and I cannot find a .sparseimage file within the AppleServiceToolkit.nbi folder.

Any ideas?

Reply