Alternative Multicasting Methods?

[Wayne Workman]

@zacksiga look at this, bear in mind it’s a very rough work in progress: https://wiki.fogproject.org/wiki/index.php/Troubleshoot_Downloading_-_Multicast

[Tom Elliott]

@zacksiga Check that the interface setting for the image’s relevant storage node master is set to the actual interface name of that system. If not, change it and restart the FOGMulticastManager service.

[zacksiga]

Interface setting is set to eth0, which right because there only one network port in the virtual machine and also uni cast images work

[zacksiga]

@Wayne-Workman So I tried your method, and it doesn’t seem to work.

[Wayne Workman]

@zacksiga Tom was on the right path, Fedora 21 and Fedora 22 do not use simple interface names like eth0.

for instance, at home my Fedora 21 Server build uses enp2s0. My Fedora 22 build in my living room uses the same (same model of PC). My Fedora 21 server build at work in Hyper-V however is eth0.

Run this and provide the output please so we can be sure - then we can move forward:

ip link show

[zacksiga]

@Wayne-Workman here the output you requested

[Wayne Workman]

@zacksiga So according to that output, your interface name is ens32

You should set this as the interface name in your storage node settings and then try to multicast again.

[zacksiga]

@Developers, @Tom Elliott, @Wayne-Workman . Funny thing is that when you created a session it only last for 10 sec or so , and disappear, same thing with multicast when you do it with a group, it shows up in active multicast for 10 sec and disappear like it was never multicast session to being with .

[Wayne Workman]

@zacksiga Well, after you set the interface name inside of the storage node settings, you hae to restart the FOGMulticastManager.

Apologies for not including this earlier.

[zacksiga]

@Wayne-Workman Thank you very much that was my the big problem, soon as I changed the interface everything seem to work. Couple of area of concern for the new svn, compare to the last svn

[Wayne Workman]

@zacksiga said:

Couple of area of concern for the new svn, compare to the last svn

?? I don’t see any issues, could you be more specific? thanks for the photos though.

Also - All the props and thanks should go to @Tom-Elliott he knew exactly what the issue was, I was just a milder sounding-board.

[Tom Elliott]

@zacksiga I don’t follow what the problem is.

The “black and blue screen” you see there is because the system can’t use the “vesafb” method.

[zacksiga]

@Wayne-Workman I have another machine that has Ubuntu 12.04 that has multicast issues, for the interface it has eth0 and ip link shows

1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN
link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
2: eth0: <BROADCAST,MULTICAST,SLAVE,UP,LOWER_UP> mtu 1500 qdisc mq master bond0 state UP qlen 1000
link/ether 00:1e:c9:d7:2f:d2 brd ff:ff:ff:ff:ff:ff
3: eth1: <BROADCAST,MULTICAST,SLAVE,UP,LOWER_UP> mtu 1500 qdisc mq master bond0 state UP qlen 1000
link/ether 00:1e:c9:d7:2f:d2 brd ff:ff:ff:ff:ff:ff
4: bond0: <BROADCAST,MULTICAST,MASTER,UP,LOWER_UP> mtu 1500 qdisc noqueue state UP
link/ether 00:1e:c9:d7:2f:d2 brd ff:ff:ff:ff:ff:ff

what are your thoughts, I tried using load balancing feature, but I don’t think its working

[zacksiga]

@Tom-Elliott
The menu used to show up with the fog logo and everything before we update the svn.

[Wayne Workman]

@zacksiga try the bond0 interface.

[Tom Elliott]

@zacksiga This is now fixed. Apparently when I updated one time, the console.h file didn’t transfer over properly. It isn’t even seen on SVN history for whatever reason. I have now fixed this. The background image should display properly as it used to.

[Wayne Workman]

@Tom-Elliott Is the console.h file an actual image? Where is it located?