Config multicast

[george1421]

You really need to get a cisco network admin involved with this. But I can see you do have an mrouter setup and you are doing igmp snooping so you have the elements in place. So you are /do use some multicasting today.

Just looking at your configuration, I might assume that you need to do something with 1/0/12 since that is the source of your multicast traffic. You will also need do igmp snooping on the vlans for the servers and the pc network. The snooping tells the switch where a subscriber is for the multicast channel. I’m a bit out of my skill set with this, other than I know you need to speak with the networking group to get this sorted out.

I don’t see any acl lists that would limit the PCs from communicating with the FOG server.

Is it also safe to assume that unicast deployments work as intended?

[Erik Rafael]

Unicast and multicast only works in vlan 901,

[george1421]

@Erik-Rafael ok then that gives us new information. Lets see if we can get unicasts working first. From vlan 902 can you ping the fog server? When you pxe boot the client…

Wait, just looked at your OP again. You have two network adapters in your FOG server, one on each vlan. This is not a currently supported configuration. At the very least you can only multicast from a single network interface. What is happening the FOG server is getting traffic on one interface and sending it out another interface.

With your setup do you need to capture and deploy to both vlans?

[Sebastian Roth]

@Erik-Rafael said:

Mounting file system Failed
Could not mount images folder (/bin/fog.upload)

This error has nothing to do with multicast which is deploy/download!! Seams like the client cannot connect to the FOG server NFS share. So I guess it’s firewall rules somewhere on the way. Make sure NFS is allowed between the VLANs and see if upload and unicast download is working then.

[Erik Rafael]

• I could only ping to 172.19.2.250,
• I changed trunk to static on port gi1/0/12 where is connected fog, changed my fogserver /etc/networks/vlans, I changed 066 boot server (past 172.19.2.250) to (172.19.1.250) and now can ping to 172.19.1.250, its ok?

My new Config
auto eth0
iface eth0 inet static
address 172.19.1.250
netmask 255.255.255.0
network 172.19.1.0
broadcast 172.19.1.255
gateway 172.19.1.254
# dns-* options are implemented by the resolvconf package, if installed
dns-nameservers 172.19.1.2 172.19.1.4

#auto eth0.901
#iface eth0.901 inet static
#. address 172.19.1.250
#. netmask 255.255.255.0
#. network 172.19.1.0
#. gateway 172.19.1.10
#. dns-nameservers 172.19.1.2 172.19.1.4
#. dns-search ciis.xxx.edu
#. vlan-raw-device eth0
#.
#auto eth0.902
#iface eth0.902 inet static
#. address 172.19.2.250
#. netmask 255.255.255.0
#. vlan-raw-device eth0
#.
#auto eth0.903
#iface eth0.903 inet static
#. address 172.19.3.250
#. netmask 255.255.255.0
#. vlan-raw-device eth0
#.
#auto eth0.904
#iface eth0.904 inet static
#. address 172.19.4.250
#. netmask 255.255.255.0
#. vlan-raw-device eth0
#.
#auto eth0.905
#iface eth0.905 inet static

[george1421]

@Sebastian-Roth Unless I’m reading the situation wrong, the OP has a single fog server with a network interface on each vlan. The fog ipxe default.ipxe file has a hard coded IP address in it. AFAIK, FOG is not designed to support deploying to multiple network interfaces. On its basic level the fog server will receive a pxe boot request on its primary network interface, but it will attempt to reply on the interface that is directly attached to the vlan. The device will start initiating communication to one IP fog IP address and the fog server will reply on a second IP address and the client will ignore the traffic because its from an unsolicited host.

[Erik Rafael]

I reinstall fog with the new configuration and reboot, unicast works on all vlans but multicast does not work in any vlan (before work in vlan 901).

I changed trunk to static on port gi1/0/12 where is connected fog, changed my fogserver /etc/networks/vlans.

auto eth0
iface eth0 inet static
address 172.19.1.250
netmask 255.255.255.0
network 172.19.1.0
broadcast 172.19.1.255
gateway 172.19.1.254

dns-* options are implemented by the resolvconf package, if installed

dns-nameservers 172.19.1.2 172.19.1.4

[Wayne Workman]

@george1421 I don’t think it’s hard coded, the script is dynamically generated I think… but - I think he would need a storage group and master node for EACH interface.

All of them can live in the same /images directory, I think, but you just would need each one to be a master for multicast to work properly. Each node would have an interface and IP for each interface.

You can set an image in FOG Trunk to be associated with many storage groups. The replicator will check and see that the files are the same across all groups (because it is THE same file), and therefore won’t do any replicating.

Just an idea…

[george1421]

This post is deleted!

[george1421]

@Erik-Rafael Ok now that unitcast works all on all vlans (this is an accomplishment in itself). Now for the multicasting. You need to enable the mrouter and igmp snooping on the link to the fog server (i think, we need a network admin here). Once that is turned on, then multicasting should work on your 901 vlan. (This is where my knowledge gets weak) if the mrouter is setup correctly it should find the subscribers on the other vlans and then broadcast the multicast traffic to that vlan.

[Wayne Workman]

@george1421 /tftpboot/default.ipxe just points to the server where the boot.php web file is hosted.

the boot.php file dynamically generates a configuration for every host that queries it.

Also - apologies for editing your post. I’m half here today.