Hello Gents,

First of all, the FOG Project has helped my team achieve what we thought was impossible before and I first want to thank everyone involved in creating and maintaining it.

We currently have FOG ver.1.5.9 setup as the following:

Master Node - Virtual - Main Site - 1
Storage Node with DHCP - Physical - Off-Site Location (Segregated/Silo’d from other sites other than Master Node) - 170
Host to be Imaged - Physical - Approx 10 per site - 1700+

This is actually working perfectly for our use-case in being able to remotely image a host at the click of a button utilizing locations but I did notice something that I wasn’t expecting yesterday when adding a new off-site storage node before segregating it with the ASA.

I noticed (using NHRP) the Storage Node attempting to reach out to seemingly all other Storage Nodes (X.X.X.0/24) and taking up a large number of traffic through tunnels from the router. Once the ASA kicked in and blocked the traffic from getting there, the tunnel issue resolved but now i’m wondering what the intended purpose of this is and how can i turn it off so that there isn’t unnecessary more work from the ASA if we aren’t using this functionality?

Thanks in advance!

** Extra Context of Environment **
Hosts are all connected to FOG Storage Node via same switch and subnet/vlan
That switch then routes to another MAIN Switch at site where it goes through ASA then Router to Main Site where Master Node resides.
Everything is currently working as intended… just curious about this particular function of Storage Nodes attempting to reach each other and how to disable it.

@brian-mainake sounds like he is on the right track. I have run into this before while imaging tablets with an ethernet adapter, although it worked out in my favor since i could mass produce tablets with images without registering each one since it thought each one was already registered due to the adapter.