Ubuntu 20.04 Isolated Network issues
-
Hello, I’ve been using fog on and off for years but am having issues with my new install. I believe it sits with the network setup as the PXE boot sometimes takes forever to come up and sometimes the NBP download will just hang.
I’ve disabled the firewall on the ubuntu desktop setup and am using it in an isolated network off a unamanaged 8 port switch. I was able to capture one image and push out a multicast.
But the multicast only completed one computer. Now all of them are sitting at the deployment screen (if I can get to it).Any help would be appreciated. Please let me know what logs are necessary.
-
@inger We really need to break this down into some discrete steps. First lets focus on pxe booting into the iPXE menu,
What is the dhcp server for your imaging network? That dhcp server needs to have ipxe.efi configured for dhcp option 67
Lets hold off discussing multicasting until you have unicast imaging working correcty
-
@george1421 I’ve setup the fog server as the main DHCP/DNS server as its sitting on an isolated network.
It just seems like the hosts are connecting but then timeout on the connection. Sometimes once it gets past the PXE boot. It cant obtain a lease from the fog server.
Update: Network issues still persist but when I do get to the deployment screen it either hangs or the speed is only 3mb/per min
-
@inger Well it sounds like you have a networking issue. Throughput to modern hardware should be in the 6GB/min range according to partclone. When you have intermittent networking issues. Can you limit the scope of your imaging network to a single enterprise switch, fog server, and test target computer. The enterprise switch can be an older one, just not one of the dumb 5 port cheap switches. Those typically don’t have enough processing power to keep up with sustained bandwidth needed for imaging,
-
@george1421 Hi George, thanks for quick reply. I’m not sure if its the switch as I just tried my main rack mount switch. Anything else I can try?
-
@inger Well we really need to isolate just the fog server and target computer on the same network switch. Right now we don’t know where the problem is. It sounds like a network issue. I assume both the fog server and target computer nics are in working order, so we need to look at what is in between. So my recommendation is to start small and see if it works. If yes then start expanding the scope of devices.
At this point I don’t think its the fog server at fault, but something in the infrastructure. I’m not trying to point blame some place other than fog, it just seems like an intermittent network issue.
