Posts made by cmachado

@Quazz Good catch! Same there too. Only 2 images and both same issue.

[01-08-20 10:36:29 am] # Windows 10 Class: Deleting remote file d1p4.img
[01-08-20 10:36:29 am] # Windows 10 Class: File size mismatch - d1p4.img: 28268901712 != -1795869360
[01-08-20 10:36:29 am] # Windows 10 Class: No need to sync d1p3.img (Link Node)
[01-08-20 10:36:29 am] # Windows 10 Class: No need to sync d1p2.img (Link Node)
[01-08-20 10:36:29 am] # Windows 10 Class: No need to sync d1p1.img (Link Node)
[01-08-20 10:36:28 am] # Windows 10 Class: No need to sync d1.partitions (Link Node)
[01-08-20 10:36:28 am] # Windows 10 Class: No need to sync d1.original.swapuuids (Link Node)
[01-08-20 10:36:28 am] # Windows 10 Class: No need to sync d1.original.fstypes (Link Node)
[01-08-20 10:36:28 am] # Windows 10 Class: No need to sync d1.minimum.partitions (Link Node)
[01-08-20 10:36:28 am] # Windows 10 Class: No need to sync d1.mbr (Link Node)
[01-08-20 10:36:28 am] # Windows 10 Class: No need to sync d1.fixed_size_partitions (Link Node)
[01-08-20 10:36:27 am] | Image Name: Windows 10 Class

So I decided to create a new FOG server from scratch. We have existing nodes at each of the school sites. I uninstalled FOG and installed latest version 1.5.7 FOG storage on each node. Everything is working great. Only issue that I can see is with fogreplicator. Keep getting this error and the replication keeps overwriting img files.

[01-08-20 10:44:45 am] | Sync finished - Resource id #1182
[01-08-20 10:41:38 am] | Sync finished - Resource id #1246
[01-08-20 10:36:35 am] | Started sync for Image Windows 10 Staff - Resource id #1246
[01-08-20 10:36:35 am] | CMD: lftp -e ‘set xfer:log 1; set xfer:log-file /opt/fog/log/fogreplicator.Windows 10 Staff.transfer.Link Node.log;set ftp:list-options -a;set net:max-retries 10;set net:timeout 30; mirror -c --parallel=20 -R --ignore-time -vvv --exclude “.srvprivate” “/images/Windows10Staff” “/images/Windows10Staff”; exit’ -u fogproject,[Protected] 10.4.30.93
[01-08-20 10:36:35 am] # Windows 10 Staff: Deleting remote file d1p4.img
[01-08-20 10:36:35 am] # Windows 10 Staff: File size mismatch - d1p4.img: 13051790429 != 166888541
[01-08-20 10:36:35 am] # Windows 10 Staff: No need to sync d1p3.img (Link Node)
[01-08-20 10:36:35 am] # Windows 10 Staff: No need to sync d1p2.img (Link Node)
[01-08-20 10:36:34 am] # Windows 10 Staff: No need to sync d1p1.img (Link Node)
[01-08-20 10:36:33 am] # Windows 10 Staff: No need to sync d1.partitions (Link Node)
[01-08-20 10:36:33 am] # Windows 10 Staff: No need to sync d1.original.swapuuids (Link Node)
[01-08-20 10:36:33 am] # Windows 10 Staff: No need to sync d1.original.fstypes (Link Node)
[01-08-20 10:36:33 am] # Windows 10 Staff: No need to sync d1.minimum.partitions (Link Node)
[01-08-20 10:36:32 am] # Windows 10 Staff: No need to sync d1.mbr (Link Node)
[01-08-20 10:36:32 am] # Windows 10 Staff: No need to sync d1.fixed_size_partitions (Link Node)
[01-08-20 10:36:31 am] | Image Name: Windows 10 Staff
[01-08-20 10:36:31 am] * Found Image to transfer to 1 node

Image size at Main server and node are exactly the same size 26.32 GiB and transfers in under 10 minutes.

I also increased the IMAGEREPSLEEPTIME to 1800. Is there something I’m missing?

@Sebastian-Roth OK. No problem.

@Sebastian-Roth Looks like we have enough info to solve. I’ll keep you guys posted. Thanks again fellas!

@Sebastian-Roth Wow! Yes it works if in same subnet 164.

@george1421 OK. Got it. File attached.

output.pcap

@george1421 Web UI is good. No issues there. I followed this link to perform the packet capture. https://forums.fogproject.org/topic/9673/when-dhcp-pxe-booting-process-goes-bad-and-you-have-no-clue. I attached 2 Files, Output-7440 (successful), Output-7450 (unsuccessful) both from same subnets.

I’ll find out about the NAC/NAP/802.1x authorization.

output-7440.pcap
output-7450.pcap

@george1421 We are running 1.3.5 and they didn’t modify FOG itself. I’m heavily leaning on the FOG server NOT being the issue because 7450 and 7460 did image properly and we did over a thousand of them. Now, after network changes, even if its the same/different subnet those 2 models no longer image. 7440 works both same/different subnet. Really looking for guidance as to what, outside of FOG, can cause this type of filtering. Allowing one PC model to access http FOG yet not allowing the other.

I have packet captures if needed for further scrutiny.

@george1421 Also, to answer your question, it doesn’t reach iPXE menu. Based on default.ipxe file, perhaps mac is not binding? Is IPV6 also, a possible issue?

#!ipxe
cpuid --ext 29 && set arch x86_64 || set arch i386
params
param mac0 ${net0/mac}
param arch ${arch}
param platform ${platform}
param product ${product}
param manufacturer ${product}
param ipxever ${version}
param filename ${filename}
isset ${net1/mac} && param mac1 ${net1/mac} || goto bootme
isset ${net2/mac} && param mac2 ${net2/mac} || goto bootme
:bootme
chain http://10.20.164.93/fog/service/ipxe/boot.php##params

@george1421 It doesn’t make sense to me either. We don’t have a proxy and we currently don’t have an issue imaging the Dell All-In-One 7440. Even across VLANs. Just the Dell All-In-One 7450 and 7460, which imaged fine during the summer. Thinking its some type of filter by hardware. Maybe Palo Alto setting. Sorry, not an expert in those realms.

Thanks for quick response. Fog server IP is correct. I was able to see the text from a PC in 164. Screenshots below.

We have Dell computers in our district AIO 7440, 7450, 7460. We were able to image all computers during the summer break with no issues. Router/Network staff tightened network security in Oct and suddenly AIO 7450 and 7460 can no longer image. AIO 7440 is still OK. Here is a screenshot of the error message we are getting.

BTW, been using FOG for over a decade. Excellent product! Thanks for your time fellas.