Multicast last reporter 0.0.0.0

Rogerchung · ‎09-07-2004

When I troubleshoot the multicast network, I used the comment "show ip igmp group" on the router which run PIM dense mode. It straingh that the last reporter of the igmp group is 0.0.0.0. What is the menaing of this? pls help

Kevin Dorrell · ‎09-07-2004

This normally happens becuase the reporter does not have an IP address yet. It is probably trying to do a DHCP or a BOOTP or something. What was the address of the group? If we recognise it, we can find out what it was trying to do.

Kevin Dorrell

Luxembourg

Rogerchung · ‎09-07-2004

Why DHCP or BOOTP will join my private multicast group?

Kevin Dorrell · ‎09-07-2004

"show ip igmp group" will show all the multicast groups, not just the private ones. What was the group address? If the group is 224.0.0.12, then that is the DHCP relay / agent address.

Could you post the output of the command please.

Kevin Dorrell

Luxembourg

Rogerchung · ‎09-07-2004

The output of the 'show ip igmp group':

IGMP Connected Group Membership

Group Address Interface Uptime Expires Last Reporter

239.255.255.254 Ethernet0 00:00:03 00:02:56 0.0.0.0

239.255.255.253 Ethernet0 00:00:03 00:02:56 10.138.180.28

239.255.255.250 Ethernet0 00:00:03 00:02:56 10.128.134.45

239.193.12.1 Ethernet0 00:00:03 00:02:56 0.0.0.0

239.194.2.1 Ethernet0 00:00:02 00:02:57 10.128.100.203

230.194.135.221 Ethernet0 00:00:03 00:02:56 0.0.0.0

229.55.150.208 Ethernet0 00:00:03 00:02:58 10.128.99.39

224.0.1.127 Ethernet0 00:00:09 00:02:56 10.128.52.239

224.0.1.40 Ethernet0 19:00:17 never 10.128.251.6

224.0.1.50 Ethernet0 00:00:09 00:02:56 10.128.251.8

224.0.1.60 Ethernet0 00:00:09 00:02:59 10.128.52.102

234.5.1.14 Ethernet0 00:00:03 00:02:58 10.128.60.209

225.0.0.1 Ethernet0 00:00:09 00:02:58 0.0.0.0

225.1.2.3 Ethernet0 00:00:03 00:02:56 10.128.99.46

234.5.2.14 Ethernet0 00:00:03 00:02:56 0.0.0.0

224.0.1.24 Ethernet0 00:00:09 00:02:56 0.0.0.0

Our private multicast group is 234.5.2.14. It shown the last reporter is 0.0.0.0. In addition, is it affect the multicast traffic? We found our client joined 234.5.2.14 abnormal.