Tek-Tips is the largest IT community on the Internet today!

Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!

  • Congratulations dencom on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

Multicast

Status
Not open for further replies.

zinkann

ISP
Jan 8, 2008
167
US
My cisco 4506 goes nuts every time i turn multicast on. Unfortunately most of my inherited network is on vlan 1, which i'm slowly segmenting. When ever we need to use a multicast application i have to turn multicast on for vlan 1 (ip pim sparse-mode) When i enable it my cpu stays around 80-100%. When i run a show ip mroute counters there are about 50 routes in it. I guess my question is what can i do about this. I'm sure there are a few different applications that use it but there are all kinds of MC IP's. If i ping one of the IP's, it replays back from a network printer, a proximity panel. is this even reliable method of tracking down the multicast addresses?

Does this look normal? I'm still trying to figure multicast out.



Admin_4506#sh ip mroute count
IP Multicast Statistics
50 routes using 28422 bytes of memory
39 groups, 0.28 average sources per group
Forwarding Counts: Pkt Count/Pkts per second/Avg Pkt Size/Kilobits per second
Other counts: Total/RPF failed/Other drops(OIF-null, rate-limit etc)

Group: 224.68.200.0, Source count: 1, Packets forwarded: 0, Packets received: 0
Source: 192.168.250.135/32, Forwarding: 0/0/0/0, Other: 0/0/0

Group: 239.192.79.0, Source count: 0, Packets forwarded: 0, Packets received: 0

Group: 239.192.79.1, Source count: 0, Packets forwarded: 0, Packets received: 0

Group: 234.21.81.1, Source count: 0, Packets forwarded: 0, Packets received: 0

Group: 239.192.79.2, Source count: 0, Packets forwarded: 0, Packets received: 0

Group: 239.192.79.3, Source count: 0, Packets forwarded: 0, Packets received: 0

Group: 224.7.7.7, Source count: 1, Packets forwarded: 0, Packets received: 719
Source: 192.168.1.211/32, Forwarding: 0/-1/0/0, Other: 719/0/719

Group: 229.111.112.12, Source count: 0, Packets forwarded: 0, Packets received: 0

Group: 224.0.1.22, Source count: 0, Packets forwarded: 0, Packets received: 0

Group: 224.0.1.24, Source count: 0, Packets forwarded: 0, Packets received: 0

Group: 239.192.79.32, Source count: 0, Packets forwarded: 0, Packets received: 0

Group: 239.192.79.33, Source count: 0, Packets forwarded: 0, Packets received: 0

Group: 239.192.79.34, Source count: 0, Packets forwarded: 0, Packets received: 0

Group: 239.192.79.35, Source count: 0, Packets forwarded: 0, Packets received: 0

Group: 239.192.79.36, Source count: 0, Packets forwarded: 0, Packets received: 0

Group: 239.192.79.37, Source count: 0, Packets forwarded: 0, Packets received: 0

Group: 224.0.1.40, Source count: 0, Packets forwarded: 0, Packets received: 0

Group: 224.0.1.60, Source count: 0, Packets forwarded: 0, Packets received: 0

Group: 235.80.68.83, Source count: 0, Packets forwarded: 0, Packets received: 0

Group: 224.0.1.84, Source count: 0, Packets forwarded: 0, Packets received: 0

Group: 239.192.78.192, Source count: 0, Packets forwarded: 0, Packets received: 0

Group: 239.192.78.193, Source count: 0, Packets forwarded: 0, Packets received: 0

Group: 239.192.78.194, Source count: 0, Packets forwarded: 0, Packets received: 0

Group: 232.255.255.200, Source count: 0, Packets forwarded: 0, Packets received: 0

Group: 229.55.150.208, Source count: 7, Packets forwarded: 7, Packets received: 93
Source: 10.0.1.30/32, Forwarding: 0/0/0/0, Other: 26/0/26
Source: 10.0.1.35/32, Forwarding: 0/0/0/0, Other: 27/0/27
Source: 10.0.3.157/32, Forwarding: 0/-1/0/0, Other: 31/0/31
Source: 10.0.34.112/32, Forwarding: 0/0/0/0, Other: 1/1/0
Source: 10.0.34.133/32, Forwarding: 0/0/0/0, Other: 1/1/0
Source: 192.168.250.135/32, Forwarding: 7/0/513/0, Other: 7/0/0
Source: 192.168.250.139/32, Forwarding: 0/0/0/0, Other: 0/0/0

Group: 239.192.78.224, Source count: 0, Packets forwarded: 0, Packets received: 0

Group: 239.192.78.225, Source count: 0, Packets forwarded: 0, Packets received: 0

Group: 239.192.78.226, Source count: 0, Packets forwarded: 0, Packets received: 0

Group: 239.192.78.227, Source count: 0, Packets forwarded: 0, Packets received: 0

Group: 239.192.78.228, Source count: 0, Packets forwarded: 0, Packets received: 0

Group: 239.192.78.229, Source count: 0, Packets forwarded: 0, Packets received: 0

Group: 239.192.78.230, Source count: 0, Packets forwarded: 0, Packets received: 0

Group: 239.192.78.231, Source count: 0, Packets forwarded: 0, Packets received: 0

Group: 239.192.78.232, Source count: 0, Packets forwarded: 0, Packets received: 0

Group: 239.255.255.250, Source count: 2, Packets forwarded: 880, Packets received: 880
Source: 10.0.0.253/32, Forwarding: 10/0/308/0, Other: 10/0/0
Source: 192.168.0.1/32, Forwarding: 870/1/327/2, Other: 870/0/0

Group: 239.255.255.253, Source count: 0, Packets forwarded: 0, Packets received: 0

Group: 239.255.255.254, Source count: 0, Packets forwarded: 0, Packets received: 0

Group: 227.255.255.254, Source count: 0, Packets forwarded: 0, Packets received: 0

Group: 230.255.255.255, Source count: 0, Packets forwarded: 0, Packets received: 0

CCNA, Network+
 
You've got a list of the source devices in a previous post (show ip igmp group). The biggest culprit appears to be 10.0.2.111


MCSE CCNA CCDA
 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top