Multicast just hangs
-
@Sebastian-Roth from a previous post:
Additionally, the output of the command you specified “sudo ps aux|grep udp-sender” is: root 13864 0.0 0.0 115300 1480 ? S Aug30 0:00 sh -c /usr/local/sbin/udp-sender --interface em1 --min-receivers 3 --max-wait 1200 --portbase 56590 --full-duplex --ttl 32 --nokbd --nopointopoint --file /images/BaseImage/d1p1.img;/usr/local/sbin/udp-sender --interface em1 --min-receivers 3 --max-wait 10 --portbase 56590 --full-duplex --ttl 32 --nokbd --nopointopoint --file /images/BaseImage/d1p2.img; root 14393 0.0 0.0 8688 660 ? S Aug30 0:00 /usr/local/sbin/udp-sender --interface em1 --min-receivers 3 --max-wait 10 --portbase 56590 --full-duplex --ttl 32 --nokbd --nopointopoint --file /images/BaseImage/d1p2.img root 31094 0.0 0.0 112708 992 pts/0 S+ 11:39 0:00 grep --color=auto udp-sender
There appears to be some stale multicast tasks running since 30-Aug.
-
@george1421 After a reboot there is no change. The computer is still deploying images via unicast without an issue. I updated the Kernel to the latest version, no change. One question, could I have the interfaces for multicast set wrong? Is there a way to check on the CentOS server what they are really named? Also inside the system can I check this? Just in case the WebUI is reporting it back incorrect?
-
@rogalskij said in Multicast just hangs:
@george1421 One question, could I have the interfaces for multicast set wrong? Is there a way to check on the CentOS server what they are really named?
We have already proved this out via the
ip addr show
what network address / adapters are in play here.Both Sebastian and I recommended to start with just 2 systems on the same switch as the fog server.
-
@rogalskij If your new test with two hosts hangs again, may I ask you to run
ps aux | grep sender
again and post output here. I want to make sure it start with the correct parameters. -
@rogalskij As well I wonder if you’ve gone through our testing guide on multicast?! https://wiki.fogproject.org/wiki/index.php/Troubleshoot_Downloading_-_Multicast#Testing_Multicast
-
@Sebastian-Roth I will be testing again today. My apologies on this taking so long. I will report back.
-
Ok more developments, we found when running the udpcast commands to test, the tests failed. I switched the Poweredge server (where FOG is installed) over to the same Cisco 2960S switch as the target computers and multicast worked perfectly!!! So it seems to be something with my Cisco 6509E core switch. I checked to make sure IGMP snooping was enabled on the core, but other than that I am unsure what to check. Any thoughts?
-
@rogalskij Maybe try setting up the multicast-rendevous with your FOG IP Server? You can use the TCP / IP, or use the Multicast that matches your TCP address.
-
@Tom-Elliott Good thinking, I just attempted that but it seemed to make no difference. My clients still seem to hang on the partclone screen. I did reach out to Cisco to check to see if my 6509E core switch has all the correct settings on it for multicasting. I also made sure the port the server was on is using “port-fast”. It worked like a charm the moment I plugged it into the edge switch. I will do some more testing while I wait for Cisco to answer me back. Sorry for all the back and forth with this, I really do appreciate this product, it’s developers, and the dedicated community behind it.
-
Found the issue! After some research and discussion with Cisco, we had to add “PIM” to the vlan on our core, even though both the server and client are both on the same vlan!
Used the command - ip pim sparse-dense-mode on vlan 1 interface and it started working like a charm! I really appreciate everyone’s assistance here. This will help our institution so very much.