• Recent
    • Unsolved
    • Tags
    • Popular
    • Users
    • Groups
    • Search
    • Register
    • Login

    Error trying to perform a multicast deployment

    Scheduled Pinned Locked Moved
    FOG Problems
    3
    7
    709
    Loading More Posts
    • Oldest to Newest
    • Newest to Oldest
    • Most Votes
    Reply
    • Reply as topic
    Log in to reply
    This topic has been deleted. Only users with topic management privileges can see it.
    • F
      fgutvar
      last edited by

      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.

      george1421G F 2 Replies Last reply Reply Quote 0
      • george1421G
        george1421 Moderator @fgutvar
        last edited by

        @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.

        Please help us build the FOG community with everyone involved. It's not just about coding - way more we need people to test things, update documentation and most importantly work on uniting the community of people enjoying and working on FOG!

        F 2 Replies Last reply Reply Quote 0
        • F
          fgutvar @george1421
          last edited by

          This post is deleted!
          1 Reply Last reply Reply Quote 0
          • F
            fgutvar @george1421
            last edited by

            @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.

            1 Reply Last reply Reply Quote 0
            • S
              Sebastian Roth Moderator
              last edited by

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

              Web GUI issue? Please check apache error (debian/ubuntu: /var/log/apache2/error.log, centos/fedora/rhel: /var/log/httpd/error_log) and php-fpm log (/var/log/php*-fpm.log)

              Please support FOG if you like it: https://wiki.fogproject.org/wiki/index.php/Support_FOG

              1 Reply Last reply Reply Quote 0
              • F
                fgutvar @fgutvar
                last edited by fgutvar

                @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.

                george1421G 1 Reply Last reply Reply Quote 0
                • george1421G
                  george1421 Moderator @fgutvar
                  last edited by

                  @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.

                  Please help us build the FOG community with everyone involved. It's not just about coding - way more we need people to test things, update documentation and most importantly work on uniting the community of people enjoying and working on FOG!

                  1 Reply Last reply Reply Quote 0
                  • 1 / 1
                  • First post
                    Last post

                  153

                  Online

                  12.1k

                  Users

                  17.3k

                  Topics

                  155.4k

                  Posts
                  Copyright © 2012-2024 FOG Project