WLC4404 - Getting Multicast Multicast to work

[GeneBeamer]

The story is that we recently upgraded our 4404 controller to the new 7.2.0.230 code. This upgrade was from 4.2.209 code. I would like to make the change to the Multicast setup so that It is multcasted and not unicasted.

So I went into the controller and selected  MULTICAST for AP multicast mode and entered in a multicast ip of 239.255.1.60 ( default choosen in the cisco howto's)

I enabled Multicast globally

I then test the reason for enabling the multicast and it doesnt work. The problem is that the Wireless HP printers setup to use Apples IPRINT are not able to be found. However, when I select the Multicast setting for the APs to be UNICAST the Ipads can find the Printers and print to them.....

What am I doing wrong with this Multicast setting? Do i need to add a Multicast address to the router?

[Stephen Rodriguez]

So the basic difference is, Unicast model sends the multicast packet as a Unicast to all the ap. when you are in multicast mode, one packet is sent.

Now if Unicast mode works, it makes me wonder about the multicast config on the LAN. Do you have pim enabled on the clients, ap, and management vlans? Are you running in sparse or dense mode?

Steve

Sent from Cisco Technical Support iPad App

[GeneBeamer]

Well maybe that is my question... I thought i could just setup a wireless Multicast group on this controller. I did some digging and this is what I got..

   Do I need to choose one of the groups below in order for the multicast / multicast to work on the wireless side?  IP Pim Sparse mode does exist on my vlans.

I had to edit this after further investigation !!

Here is my Multicast config

ip multicast-routing

interface Loopback0

ip address 10.x.y.z 255.255.255.255

ip pim sparse-modeinterface Loopback0
ip address 10.x.y.z 255.255.255.255
ip pim sparse-mode

ip pim rp-address 10.x.y.z

ip pim rp-candidate Loopback0

when i do a sho ip pim rp i get this

Group: 239.255.255.253, RP: 10.x.y.z, next RP-reachable in 00:01:09

Group: 239.255.255.250, RP: 10.x.y.z, next RP-reachable in 00:01:09

Group: 224.10.10.10, RP: 10.x.y.z, next RP-reachable in 00:00:21

Group: 239.24.60.4, RP: 10.x.y.z, next RP-reachable in 00:00:21

Group: 224.0.1.22, RP: 10.x.y.z, next RP-reachable in 00:01:09

Group: 224.0.1.60, RP: 10.x.y.z next RP-reachable in 00:01:09

Group: 224.0.1.35, RP: 10.x.y.z next RP-reachable in 00:01:09

Group: 225.0.0.42, RP: 10.x.y.z next RP-reachable in 00:01:00

Group: 224.0.1.40, RP: 10.x.y.z, next RP-reachable in 00:00:59

Group: 239.24.61.4, RP: 10.x.y.z next RP-reachable in 00:00:03

Group: 239.24.61.6, RP: 10.x.y.z next RP-reachable in 00:00:03

Group: 239.255.255.253, RP: 10.x.y.z next RP-reachable in 00:01:09
Group: 239.255.255.250, RP: 10.x.y.z next RP-reachable in 00:01:09
Group: 224.10.10.10, RP: 10.x.y.z, next RP-reachable in 00:00:21
Group: 239.24.60.4, RP: 10.x.y.z next RP-reachable in 00:00:21
Group: 224.0.1.22, RP: 10.x.y.z next RP-reachable in 00:01:09
Group: 224.0.1.60, RP: 10.x.y.z, next RP-reachable in 00:01:09
Group: 224.0.1.35, RP: 10.x.y.z next RP-reachable in 00:01:09
Group: 225.0.0.42, RP: 10.x.y.z next RP-reachable in 00:01:00
Group: 224.0.1.40, RP: 10.x.y.z next RP-reachable in 00:00:59
Group: 239.24.61.4, RP: 10.x.y.z next RP-reachable in 00:00:03
Group: 239.24.61.6, RP: 10.24.253.1, next RP-reachable in 00:00:03