problem deployment multicast



  • Hello,
    On 2 different vlan, pc and server, the multicast session is displayed but is not done.
    On the same vlan, the session does not activate and an error appears : “downloaded WDSNBP…” Windows deployment services : PXE Boot Aborted PXE_M0F : Exiting PXE ROM.
    Selected boot device failed- press any key to reboot the system.

    Thanks for your help.
    Cordially



  • @tom-elliott

    Still me, I just redo a test and here are the multicast logs

    [03-15-18 10:24:37 am] | Task (15) Multi-Cast Task is new!
    [03-15-18 10:24:37 am] | Task (15) /images/SalleC11-01 image file found.
    [03-15-18 10:24:37 am] | Task (15) Multi-Cast Task 2 clients found.
    [03-15-18 10:24:37 am] | Task (15) Multi-Cast Task sending on base port: 54210.
    [03-15-18 10:24:37 am] | Command: /usr/local/sbin/udp-sender --interface eth0 --min-receivers 2 --max-wait 600 --portbase 54210 --full-duplex --ttl 32 --nokbd --nopointopoint --file /images/SalleC11-01/d1p1.img;/usr/local/sbin/udp-sender --interface eth0 --min-receivers 2 --max-wait 10 --portbase 54210 --full-duplex --ttl 32 --nokbd --nopointopoint --file /images/SalleC11-01/d1p2.img;/usr/local/sbin/udp-sender --interface eth0 --min-receivers 2 --max-wait 10 --portbase 54210 --full-duplex --ttl 32 --nokbd --nopointopoint --file /images/SalleC11-01/d1p3.img;/usr/local/sbin/udp-sender --interface eth0 --min-receivers 2 --max-wait 10 --portbase 54210 --full-duplex --ttl 32 --nokbd --nopointopoint --file /images/SalleC11-01/d1p4.img;
    [03-15-18 10:24:37 am] | Task (15) Multi-Cast Task has started!
    [03-15-18 10:24:47 am] | Task (15) Multi-Cast Task is already running with pid: 43102.
    [03-15-18 10:24:57 am] | Task (15) Multi-Cast Task is already running with pid: 43102.
    [03-15-18 10:25:07 am] | Task (15) Multi-Cast Task is already running with pid: 43102.
    [03-15-18 10:25:17 am] | Task (15) Multi-Cast Task is already running with pid: 43102.
    [03-15-18 10:25:27 am] | Task (15) Multi-Cast Task is already running with pid: 43102.
    [03-15-18 10:25:37 am] | Task (15) Multi-Cast Task is already running with pid: 43102.
    [03-15-18 10:25:47 am] | Task (15) Multi-Cast Task is already running with pid: 43102.
    [03-15-18 10:25:57 am] | Task (15) Multi-Cast Task is already running with pid: 43102.
    [03-15-18 10:26:07 am] | Task (15) Multi-Cast Task is already running with pid: 43102.
    [03-15-18 10:26:17 am] | Task (15) Multi-Cast Task is already running with pid: 43102.
    [03-15-18 10:26:27 am] | Task (15) Multi-Cast Task is already running with pid: 43102.



  • @tom-elliott said in problem deployment multicast:

    the read means nothing here. That just means fog can’t ping the machines via hostname, nothing dealing with multicast. Your multicast log appears to indicate there are no tasks.

    I just redo a test
    the ping works well from the server to the clients - I enclose a screenshot of the waiting task as well as a screenshot of the screen waiting for the launch of the multicast

    0_1521103761590_Capture_Multicast.jpg
    0_1521103984433_Attente_Multicast.JPG


  • Senior Developer

    @natlanis the read means nothing here. That just means fog can’t ping the machines via hostname, nothing dealing with multicast. Your multicast log appears to indicate there are no tasks.



  • @tom-elliott said in problem deployment multicast:

    he log you gave appears to be the service startup logs, can you provide the log for multicast? /opt/fog/log/multicast.log

    hi,
    here are the logs
    [03-14-18 9:49:27 pm] * No tasks found!
    [03-14-18 9:49:37 pm] * No tasks found!
    [03-14-18 9:49:47 pm] * No tasks found!
    [03-14-18 9:49:57 pm] * No tasks found!
    [03-14-18 9:50:07 pm] * No tasks found!
    [03-14-18 9:50:17 pm] * No tasks found!
    [03-14-18 9:50:27 pm] * No tasks found!
    [03-14-18 9:50:37 pm] * No tasks found!
    [03-14-18 9:50:47 pm] * No tasks found!
    [03-14-18 9:50:57 pm] * No tasks found!
    [03-14-18 9:51:07 pm] * No tasks found!
    [03-14-18 9:51:17 pm] * No tasks found!
    [03-14-18 9:51:27 pm] * No tasks found!
    [03-14-18 9:51:37 pm] * No tasks found!
    [03-14-18 9:51:47 pm] * No tasks found!
    [03-14-18 9:51:57 pm] * No tasks found!
    [03-14-18 9:52:08 pm] * No tasks found!
    [03-14-18 9:52:18 pm] * No tasks found!
    [03-14-18 9:52:28 pm] * No tasks found!
    [03-14-18 9:52:38 pm] * No tasks found!
    [03-14-18 9:52:48 pm] * No tasks found!
    [03-14-18 9:52:58 pm] * No tasks found!
    [03-14-18 9:53:08 pm] * No tasks found!
    [03-14-18 9:53:18 pm] * No tasks found!

    In FogProject, the PCs appear in red, is it linked?

    0_1521099196142_FogProject.png


  • Senior Developer

    @natlanis the log you gave appears to be the service startup logs, can you provide the log for multicast? /opt/fog/log/multicast.log


  • Moderator

    @natlanis IGMP Snooping is only for the switches. This function the switches will listen for igmp (multicast) subscribe messages from the target computer and then send the traffic to a corresponding igmp offer device. This is done to avoid sending the multicast stream to all network ports. With igmp snooping it improves the efficiency of the network by only sending the multicast stream to the computers that request it and not everyone.

    So that is half of the issue. The other part is your vlan router is not forwarding igmp messages across the subnets. This is typically off by default. Other vlan routers need a help service much like dhcp needs a helper service to listen and forward broadcast messages across the vlans. The dhcp service is called dhcp-relay or dhcp-helper. For IGMP its typically called igmp-proxy. Without that igmp proxy service your multicast signals from the target computers will not make it to the FOG server.

    I did write a tutorial a while ago about using pfsense as the vlan router to forward the igmp messages between the subnets: https://forums.fogproject.org/topic/10117/fog-casting-across-vlans-subnets



  • This logs
    [03-09-18 12:39:09 pm] FOGMulticastManager forked child process (11825).
    [03-09-18 12:39:09 pm] FOGMulticastManager child process (11825) is running.
    [03-09-18 12:39:11 pm] FOGImageReplicator Start
    [03-09-18 12:39:11 pm] FOGImageReplicator forked child process (11861).
    [03-09-18 12:39:11 pm] FOGImageReplicator child process (11861) is running.
    [03-09-18 12:39:13 pm] FOGSnapinReplicator Start
    [03-09-18 12:39:13 pm] FOGSnapinReplicator forked child process (11972).
    [03-09-18 12:39:13 pm] FOGSnapinReplicator child process (11972) is running.
    [03-09-18 12:39:15 pm] FOGTaskScheduler Start
    [03-09-18 12:39:15 pm] FOGTaskScheduler forked child process (12026).
    [03-09-18 12:39:15 pm] FOGTaskScheduler child process (12026) is running.
    [03-09-18 12:39:17 pm] FOGPingHosts Start
    [03-09-18 12:39:17 pm] FOGPingHosts forked child process (12059).
    [03-09-18 12:39:17 pm] FOGPingHosts child process (12059) is running.
    [03-09-18 12:39:19 pm] FOGSnapinHash Start
    [03-09-18 12:39:19 pm] FOGSnapinHash forked child process (12110).
    [03-09-18 12:39:19 pm] FOGSnapinHash child process (12110) is running.
    [03-09-18 12:39:22 pm] FOGImageSize Start
    [03-09-18 12:39:22 pm] FOGImageSize forked child process (12165).
    [03-09-18 12:39:22 pm] FOGImageSize child process (12165) is running



  • Hi,
    Everything is OK now compared to the previous two points, but I still can not do multicast
    When I’m on the same VLAN it works, but if I’m on two different Vlans it does not work anymore - it happens to the multicast session, but it does not start - I enabled IGMP on both vlans (Server + client)


  • Moderator

    You have 2 issues here.

    1. Multicast: If you have a fog server on one vlan and your target computers on a different vlan you must make changes to your vlan router to support multicast routing or you need to install a multicast router (mrouter). Multicasts are not typically forwarded by default on many vlan routers. I would focus on your vlan router to understand why its not forwarding multicast packets.

    2. “downloaded WDSNBP…” Windows deployment services: You have a WDS server configured on this vlan. The WDS server is overriding your pxe boot information on this vlan. Turn off the wds server and your network booting via FOG will work better.


 

395
Online

41.6k
Users

12.1k
Topics

114.2k
Posts