With that kind of throughput, you can eliminate the switch, patch cables, and NICs, and NIC drivers from the equation…
This is definitely something with FOG… Maybe FOG Configuration, Maybe the drivers that it’s distributing via the kernel… maybe…
What version of FOG are you using? what SVN version? What’s the model of the computer you’re testing the problematic imaging with? What kernel version are you using for the network booting?
[quote=“Tom Elliott, post: 44712, member: 7271”]Windows 10 currently works. The question should be when Windows 10 is released, how will it work if Secure Boot is required hence requiring a UEFI system?[/quote]
The problem of a mixed environment (undionly.kpxe and ipxe.efi) keeps coming up…
We gotta tackle this for ProxyDHCP using Windows Server…
If I just HAD a UEFI device, I could work on it…
new network equipment anywhere?
new router? Switch? Active and/or Passive Intrusion Detection System?
When was the last time the FOG server was rebooted? Is it virtualized?
Have you done simple stuff yet like re-seat the FOG server’s patch cable? Test the cable? Replace the cable?
Maybe something happened to it’s NIC? When was the FOG server’s last OS update? Maybe try a throughput test using [U][URL=‘http://en.wikipedia.org/wiki/Iperf’]Iperf[/URL][/U] ?
A bad patch cable will make a NIC revert to 100 meg, or even 10 meg if it’s bad enough.
Have you only tested one client, or is this problem throughout your environment?
Do you plan on changing the port’s vlan config every time you want to image?
Or do you have an area setup just for imaging that you’d physically bring the machines to?
That’s a good question, Uncle Frank.
And yes, DHCP should easily handle 50, or 300 simultaneous requests. It’s literally only 5 packets per client, with the 5th being an ARP probe from the client at the end.
[LIST=1]
[]Discovery
[]Offer
[]Request
[]Acknowledgement
[*]Client probes network for it’s new address
[/LIST]
See here:
[url]http://en.wikipedia.org/wiki/Dynamic_Host_Configuration_Protocol[/url]
On a gigabit network, (Just an example from my Win7 workstation), if you monitor the network adapter status, mine is sending 400 to 1,000+ packets every 1 to 3 seconds… Receiving about the same. And that’s with it just sitting here idle…
This just highlights how lightweight DHCP is…
It’s not a router.
It’s a router, switch, DHCP, DNS, Access point Combination device…
and real world organizations with over 10 clients don’t use such limited consumer grade devices within their core network infrastructure. They would use an enterprise level solution (like Cisco Small Business devices, or server 2008, 2012.) that allows configuring 066 and 067.
What I recommend for you is not necessarily what I’d recommend for others.
Maybe you should examine your DHCP server, since it seems to be the problem.
Does it have a fast enough interface? Is the system bogged down with other tasks? Does it have enough RAM for breathing room? Is it on the same LAN, or is it a remote server running through a constricted and traffic heavy WAN pipe?
You really shouldn’t be having any issues with DHCP keeping up… it’s such an incredibly lightweight service…
It could just be your FTP settings/credentials… or even firewall or SELinux…
I like the idea, but it might be easier to pull anonymous data from the FOG database first. Then work on implementing the other stuff, like FOG server # of cores, RAM, etc.
Unless that stuff is super easy to pull… I haven’t looked into it.
Here’s more info on DHCP options: [url]http://www.iana.org/assignments/bootp-dhcp-parameters/bootp-dhcp-parameters.xhtml[/url]
Just for your learning purposes.
I’m not sure what your skill level is but, you did ask how to configure 066 & 067.
Just open a web browser and go to you’re TP-Link’s internally facing interface address.
For you, that would be [B]192.168.1.1[/B]
It should ask for credentials at some point. You can probably Google search the default username/password for that device and find it within a minute or two.
Past that, you just need to look around in there. No two are really laid out the same so you just need to be familiar with the terminology. Look into the DHCP stuff. See if you can configure options 066, or 067. They may not be labeled with numbers.
If you can’t figure it out, it’s probably best to turn off DHCP (just figure out how to turn just DHCP off), then set it up on the FOG server.
You’ll need to know about IP ranges, subnet masks, your DNS server, your gateway…
Just a stab at what those are for you:
Range: 192.168.1.2 - 192.168.1.254
Subnet mask: 255.255.255.0
DNS: 192.168.1.1
Gateway: 192.168.1.1
If that TP-Link device that is currently running DHCP can’t set options 066 & 067, then you might be best to turn off that service (not the device, just the service) and set up DHCP on your FOG server.
Is this FOG setup just for learning? I’m assuming so because of the device that’s handing out DHCP.
If that’s the case, you can simply turn DHCP off for that device, set up FOG /w DHCP for learning purposes, and then turn DHCP on for that device later when you’re done (or continue using FOG’s DHCP).
I think that’s going to be your golden ticket, honestly. Consumer grade DHCP devices usually aren’t up-to-snuff for advanced stuff; hence Consumer Grade.
Might those ‘other’ computers have UEFI based booting?
If so, you’re problems are not over…
We will be here.
What version/revision of FOG?
Can you post your installation log? It’s here: [SIZE=12px] [/SIZE][SIZE=12px]/var/log/foginstall.log[/SIZE]
Maybe doublecheck your /tftpboot permissions?
[CODE]ls -ld /tftpboot[/CODE]
Maybe check your firewall?
[CODE]iptables -L[/CODE]
Also, if you’re not using FOG as a DHCP server, then you must configure options 066 and 067 on your actual DHCP server (this will make your life a whole lot easier). 066 is normally the IP address of the FOG server, 067 is the bootfile name you want to use. Generally, undionly.kpxe will be you’re winner for systems made 6 months ago and greater. For newer systems shipping with win8 and UEFI type bios, you would use ipxe.efi for option 067.
#LetsMakeScripts
[quote=“Eze84d, post: 44611, member: 28734”]I could help a little, because I do not have much knowledge of Debian … I’d have to install … the version for Fedora or Ubuntu Wayne Workman ???[/quote]
For Debian, follow the Ubuntu commands. 
FYI, Ubuntu is a branch off of Debian.
Just as Fedora is a branch off of Red Hat.
MOST Linux distributions (that aren’t Debian or Red Hat) are branches off of Debian or Red Hat.
@[URL=‘http://fogproject.org/forum/members/eze84d.28734/’]Eze84d[/URL], before you ask…
Please post the installation log.
It’s here:
[SIZE=12px]/var/log/foginstall.log[/SIZE]
Also, the others above this post are correct, that is not the end of your installation log.
When you see this:
[CODE]You still need to install/update your database schema.
This can be done by opening a web browser and going to:
http://192.168.0.3/fog/management
Press [Enter] key when database is updated/installed.[/CODE]
That means you should use a web browser and go to this address:
[CODE]http://192.168.0.3/fog/management[/CODE]
and click on the “Update Database” button.
After doing that, then you would press [Enter] for the installer.
After you’ve re-ran the installer, please give us your entire installation log.
We use this log to help troubleshoot problems.
I believe the Thinkcentre M73 uses UEFI booting by default.
Your installation log indicates you’re using FOG for DHCP.
UEFI enabled systems generally use ipxe.efi to boot with.
You can set option 067 to point to ipxe.efi and then try to network boot the Thinkcentre M73.
The settings are in this file: /etc/dhcp/dhcpd.conf
You would change
[CODE]filename “undionly.kpxe”; [/CODE]
to:
[CODE]filename “ipxe.efi”; [/CODE]
Or, you can try to disable UEFI and enable legacy boot, and PXE boot in the BIOS on the Thinkcentre M73.
Let us know how it goes.