• Also, the storage nodes don’t need to be anything fancy (I’ve said this before?)

    An old dual-core with a gigabit interface will get the job done in an acceptable amount of time.

    Here, in my environment, FOG is virtualized on one of our servers, and can blast an image out to 1 client in 8 minutes (almost 50GB image, uncompressed). We can image 29 systems with that particular image in 29 minutes using multicast (I blame a bad patch cable somewhere).


  • [quote=“jamesb, post: 42509, member: 27742”]So I’m basically going to need to set up a storage node for each vlan we have in order for multicast to work in all of our buildings?[/quote]

    Yeah, basically.

    It might sound scary, but it’s not tough to do, and is documented.

    If you have vlans that are assigned the same gateway (the router interface), then you only need one storage node for those Vlans.

    Basically, you would need one node in each broadcast domain. That’s if you want it all centralized, with one almighty controlling FOG server for them all.

    Before going to that extent though, I’d try getting multicast to work within the broadcast domain that the FOG server is in. You have to do that first to confirm you’re network equipment is configured properly, and that FOG is configured properly.


  • So I’m basically going to need to set up a storage node for each vlan we have in order for multicast to work in all of our buildings?


  • FOG server has 172.28.2.21/24
    Client has 172.52.8.54/24

    The problem is that they are within different broadcast domains.
    Broadcast traffic does not traverse broadcast domains (routers don’t pass broadcast packets).

    The network portion of the FOG server/node’s IP address must match the network portion of the Client’s IP address. So, that particular FOG server can only image clients with an address beginning in 172.28.2

    Try it on a client that is within the same broadcast domain.
    Later, once you can get that going, you can work towards setting up FOG storage nodes with the Location snapin.


  • Our core switches are 4510’s and our stacked switches are 3750’s. All switches are Cisco Catalyst switches. Topographically they are spread throughout our small town in each of the school buildings. We are using Vlans. The FOG config is 172.28.2.21 255.255.255.0; Default route is 172.28.2.1; DNS 172.28.2.12. I’m testing this on an Optiplex 755 for right now. DHCP is set up on our network. The client is getting an IP of 172.52.8.54


  • Can you explain your network environment’s setup?

    Switch model?
    Where is the router (topographically)?
    Are you using Vlans?
    What’s the FOG server’s network interface configuration(s)? (include subnet mask, gateway, DNS, IP address)
    Where’s the client you’re testing with?
    Are you using DHCP?
    Can you tell us what IP address the client is getting/assigned?

    Just covering the bases at this point.


  • After following the instructions for Cisco switches at : [url]http://www.fogproject.org/wiki/index.php/Cisco_Multi_Cast[/url] multi-casting still isn’t working for us. We have the ip pim sparce-dense-mode on the vlans that I’m using to test multicast with and I still have the same problem of the client machine not communicating with the host for a multicast session. Is there some other settings that needs to be applied that aren’t part of the wiki?


  • Well now that I’m able to tackle this again I followed the wiki for multicast issues and it is pointing to the issue being in our switches. I’ll have to start looking their.


  • In Fedora, there are some systemctl commands to check the status of various services. There’s probably something equivalent in Ubuntu.

    If you look at this:

    [url]http://fogproject.org/wiki/index.php/FOG_(r2922)Configuration_on_Fedora_21_Workstation_inside_Windows_Server_2012_Hyper-V_using_ProxyDHCP#FOG_Server_Troubleshooting_Help.28Fedora_21.2C_r2922_.26_up.29[/url]

    It’ll give examples of those commands in Fedora.
    It’s basically to check and see what’s running, what’s not, what has errors…

    It’s a place to start.


  • No, I left everything as the default except for the wait time which I changed to 5 minutes.


  • In that particular revision, it’s possible to change the multicast address & port used. Did you do that, by chance? (just a stab at helping)


  • Sorry it took so long to reply. Other projects got in the way of me testing this. I have tried doing this and it didn’t work. All of the PC’s hit the partclone screen and just sit there. They never actually start the progress bar no matter how long I wait.

  • Senior Developer

    I don’t think those errors are in any way related to your issues.

    Most likely, you’re running ubuntu (based on the error messages you’re seeing) and the service started before the network was actually available. This means the service started up, but then the database (mysql) died, but the process that was running for the multicast manager service failed.

    The fix:
    [code]sudo service FOGMulticastManager stop
    sudo service FOGImageReplicator stop
    sudo service FOGScheduler stop
    sudo service FOGMulticastManager start
    sudo service FOGImageReplicator start
    sudo service FOGScheduler start[/code]

323
Online

8.5k
Users

15.3k
Topics

143.4k
Posts