Can't WOL & Deploy across subnets
-
Server
- FOG Version: 1.4.4
- OS: Ubuntu 14.4
Client
- Service Version:
- OS: Windows 7
Description
We are able to use all features on the machines that are on the same subnet as our fog server, but once going to our other subnets, WOL and deploying images won’t work. We have registered and all machines and can PXE boot but they get stuck after loading partclone. We’ve tried to enable UDP broadcast forward but the command keeps coming up invalid in our HP switches.
-
THis is what the WOL Broadcast plugin was designed to do.
-
@Tom-Elliott When we try to configure WOL broadcast management we get “ID must be set to edit” error.
-
Is there an error message on the partclone scrone?
Is this multicast or unicast?
-
@Quazz there isn’t any error, it just never starts. It shows the image name that it’s supposed to be deploying, but it won’t load the partitions. This isn’t working with multicast, however, we did try to unicast and it worked. I’m assuming it has something to do with multicast settings…
-
@hvaransky said in Can't WOL & Deploy across subnets:
@Tom-Elliott When we try to configure WOL broadcast management we get “ID must be set to edit” error.
For this, can you post a quick screenshot please? Not a lot of us have worked with the WOL Broadcast plugin, my memory on it is super fuzzy.
@hvaransky said in Can't WOL & Deploy across subnets:
This isn’t working with multicast, however, we did try to unicast and it worked.
So, to make that work you need to configure your router to forward broadcast packets. This can have very nasty side effects though, because it can create broadcast storms on your network. I don’t recommend it.
The best way to do multicasting is to put storage nodes at the remote subnet (another server or even a 2nd NIC or Trunk on your current server). If you put in a 2nd server, the location plugin is needed I believe to make the storage node multicast - and maybe it has to be a master too, can’t remember ( @Tom-Elliott can you explain the ins and outs of multicasting from nodes?). If you add a 2nd NIC, that can be made to work too. A trunk port on your server is more complicated to setup, would require configuring the switch port it’s attached to - to be a trunk port too, and then you’d have to setup virtual adapters on the server’s trunk port per each subnet - it gets a little hairy doing this, I try to avoid it.
-
@Wayne-Workman Here’s the screenshot that we are getting when trying to create the new WOLbroadcast.
We are working on getting a storage node setup on another VLAN now.
-
@Wayne-Workman We tried to use the location plugin and am getting the same error as the WOL plugin.
-
Quick testing on my end and I am also unable to create new entries in location and wolbroadcast plugins (previously never used)
-
https://forums.fogproject.org/topic/10364/issues-after-upgrading-from-1-4-3-to-1-4-4/7
Please update the Plugin file for the one in the post above. You will also need to uninstall and reinstall the plugins that don’t seem to be working.
