• RE: Very slow registering host and pushing images to Dell Optiplex 7070 ultras.

    @darkxeno First thing you have to keep in mind that the XX70 generation is still very new. The FOG Project relies heavily on the Linux Kernel developers for hardware support. When hardware support is added by the Linux kernel developers the FOG Project devs integrate that kernel into FOS Linux. The Linux kernel developers will always be behind in releasing supporting hardware drivers because hardware vendors and chip manufacturers sometimes release hardware in a closed manner where they release the chips and provide the windows driver.

    But from a wireshark perspective, we can see what is flying down the wire using a witness computer connected to the same subnet, or the FOG server if its on the same subnet as the pxe booting computer. The FOG server is preferable since it would also collect unicast communications between the target computer and the FOG server. If the fog server can be used (i.e. same subnet as target computer) I have a tutorial for that: https://forums.fogproject.org/topic/9673/when-dhcp-pxe-booting-process-goes-bad-and-you-have-no-clue

    If you are using wireshark from a witness computer (i.e. computer plugged into the same subnet as the pxe booting computer) you can (should) use the capture filter of udp port 67 or udp port 68 That will only capture the dhcp/bootp part of the booting process. This is possible since dhcp uses broadcast messages to communicate so all hosts on the subnet will receive these broadcast dhcp messages.

    posted in FOG Problems
  • RE: Xps15 Fail to deploy image - Ipxe / Uefi

    @Schuede said in Xps15 Fail to deploy image - Ipxe / Uefi:

    listen-address=127.0.0.1

    Sebastian, good point I skipped right over that. In this case that command is telling dnsmasq to bind to the loopback interface. So only DHCP DISCOVERS on the loopback interface would get a response. Probably not what the OP wants. While that’s not the issue in the picture it would be the cause of the other issues reported.

    posted in FOG Problems
  • RE: Very slow registering host and pushing images to Dell Optiplex 7070 ultras.

    @Sebastian-Roth said in Very slow registering host and pushing images to Dell Optiplex 7070 ultras.:

    Maybe you have a rough DHCP in your network?

    Just as a comment, I’ve seen organizations that have a primary and secondary dhcp servers setup intentionally, but only one of them has the pxe boot information. But looking at the OPs picture it looks like FOS Linux is unable to get an IP address. At that point the PXE boot information isn’t needed. But it does make me think its a networking (or possibly) a dhcp server issue. We probably can/should trap that error with wireshark so we can see who is saying what to the target computer.

    posted in FOG Problems
  • RE: Very slow registering host and pushing images to Dell Optiplex 7070 ultras.

    @darkxeno Thank you for the feedback.

    @Sebastian-Roth tagging you only so you are aware of the issue with the Dell system disks too.

    posted in FOG Problems
  • RE: FOG image sync with mysql replication - 2 Servers

    @roc1479 Very nice, well done. We’ll have to go over it and test it in the lab, but the configuration is pretty straight forward. Thank you.

    posted in General
  • RE: Very slow registering host and pushing images to Dell Optiplex 7070 ultras.

    @darkxeno Well what’s not clear is if its a network issue or a disk (nvme) issue at the moment. We are seeing newer (select) nvme drives having a slowness issue writing the image to disk. That issue is being discussed in this thread: https://forums.fogproject.org/topic/13777/extremely-slow-deploy-to-nvme-drives/28

    One thing you can test is to go into the global kernel parameters under the fog configuration and add in this kernel parameter
    nvme_core.default_ps_max_latency_us=0 You will see an error with that name during booting, but its a warning, it will set the kernel parameter correctly. The issue is that there is a dot in the parameter name. See if that kernel parameter changes anything with write speed. What it does is keep the nvme drive from using any low power mode during imaging. We are seeing random successes with that.

    We might also want to get you to move to the dev branch of FOG, that will take your FOG version to 1.5.7.55 or later. The developers added a nvme command line tool that we can use to push commands directly to the nvme disk. But lets first see if the kernel parameter masks the issue.

    posted in FOG Problems
  • RE: Very slow registering host and pushing images to Dell Optiplex 7070 ultras.

    @darkxeno said in Very slow registering host and pushing images to Dell Optiplex 7070 ultras.:

    So on the linux side it would be [8086:15BE] While I know that network adapter, that may have been a new model. But I looked in the linux docs and that driver was added in kernel version 4.12.x, you are at 4.19.64 so its been supported for quite a while.

    posted in FOG Problems
  • RE: Very slow registering host and pushing images to Dell Optiplex 7070 ultras.

    @darkxeno First you have to remember I don’t know your network design so I need to ask 20 questions to understand how things are setup. So we’ve already ruled out a spanning tree issue since you’ve used a cheap switch on your bench and the issue is only with the 7070s so far. You are on the latest version of FOG with a moderately new kernel.

    For the 7070s, under windows device manager can you get us the hardware id of that nic? We’ll need both the vendor and hardware IDs. Then I can look into the linux kernel to see if there is a driver for it. If its a realtek nic, I have a test kernel you can try that has an updated nic driver specifically for realtek 8168 series nics.

    posted in FOG Problems
  • RE: Xps15 Fail to deploy image - Ipxe / Uefi

    I guess a couple of questions to start off with.

    1. In regards to dnsmasq, is the fog server on the same IP subnet as your pxe booting computer? If they are on different subnets then you will need to add the fog server’s IP address as the last address in your vlan router’s dhcp-helper/relay service.
    2. What chipset is in that USB NIC? If you don’t know go into the windows device manager and pots here the hardware ID we’ll need the vendor and device IDs.

    While its not as clean of an answer, if you were to manually register that target computer with the fog server. Then schedule a deploy task to that computer, but before you hit the schedule button, tick the debug check box. Now pxe boot the target computer. After a few screens of text on the target computer that you will need to clear with the enter key, you will be dropped to the FOS Linux command prompt. At the FOS Linux command prompt key in lsusb and post the results here (picture). That will give us the codes if FOS Linux sees the network adapter. I guess the output of this command would be handy too ip addr show

    posted in FOG Problems
  • RE: Very slow registering host and pushing images to Dell Optiplex 7070 ultras.

    @darkxeno What version of FOG are you using? What version of the FOS Linux kernel are you using? You can see the kernel version in the fog configuration page. It would be a number like 4.19.64.

    From the picture that is uploaded I see that (potentially) the client is on a different subnet than the fog server?

    Also on the systems that have this issue of not being able to get an IP address, if you place a dumb (read cheap) unmanaged switch between your building switch and the pxe booting computer does it work correctly every time?

    posted in FOG Problems