Error trying to perform a multicast deployment


  • My Server is a CentOS 7 with FOG updated to version 1.5.9.114 where we have already displayed images for more than 1 year, but we had not tried using MULTICAST. Setting are as follow:
    ad2637d9-4cdf-4953-9811-89e782be0a59-imagen.png
    883cd9cc-7760-460d-b354-fbc18f9e590b-imagen.png

    The images are stored on the local server /images and a Sinology NAS.

    We schedule a multicast session for 100 clients and 0 timeouts.
    5c5f179f-754a-4b0e-94d7-91a52292d66f-imagen.png
    systemctl status FOGMulticastManager → Active (running)

    We start a PC for deployment and join it to the active Multicast session, a task is automatically created for that client in the active tasks view.
    c2427b6d-6fa9-4cf0-92e3-c9da3f52a6cb-imagen.png
    a3c880a8-21a4-43c8-bc66-880cb2bc8a5d-imagen.png

    On the PC screen, a PartClone, Starting Restore box and the image to be displayed appear on a blue background, and the cursor is blinking, but no progress bar or other information appears.

    On the Server, the logs file /opt/fog/lof/multicast.log appears repeatedly:

    “Interface not ready, waiting for it to come up: 10.137.102.150”

    Where is my mistake.

    Thanks in advance.

  • Moderator

    @fgutvar multicasting is very much dependent on your infrastructure. Multicast packets are normally blocked crossing your vlan routers this is by design. For multicasting across subnets there is typically a multicast router in place. This can be the same or different than your vlan router. The processing of unicast and multicast routing are different. Some standard IP routers have an igmp proxy service that will run. It functions much like a dhcp-relay or dhcp-helper service does, but the igmp proxy listens for multicast traffic and not dhcp traffic.


  • @fgutvar Yes the server is in a WMWARE VCenter deployed in a C class and the clients e.g. 10.137.109.xxx.
    I guess that this should be a VLAN or switch filtering problem. I’ll try a lab for 2 clients in the 10.137.102.xxx to corroborate this suspicion.

    Thanks.

  • Moderator

    @fgutvar Are the client machines in a different subnet than your FOG server (10.137.102.150) is?


  • @george1421 I had images stored in my server at 10.137.102.150 and in a NAS 10.137.102.248. This multicast session is started with a image stored on the server.

    I don’t know exactly the param value that are you asking me for in the (.fogsettings).

    ipadress=‘10.137.102.150’
    hostname=‘gaptffog1’

    Thanks in advance.


  • This post is deleted!
  • Moderator

    @fgutvar The fog multicast only will run from a full FOG server with the files locally. FOG does not support multcasting from a storage node (FOG or NAS). Is 10.137.102.150 your FOG server or NAS IP address?

    When you configured FOG did you define the proper network device name to be used for imaging. You can review the hidden file /opt/fog/.fogsettings to see the options you selected.

333
Online

9.1k
Users

15.7k
Topics

145.8k
Posts