All things related to multicast

[Amel Caldwell <>]

Has anyone else noticed an usually large amount of traffic from a beacon
client?  It looks like 209.245.19.27 is sourcing almost 300 packets per
second.

We noticed because we have been trying to track down some high CPU problems on
our campus it this seems to be part of the problem?  THe hwole problem is that
our core Foundry switches has PIM SM snooping enabled, but multicast traffic
is leaking where it shouldn't be anyway and is hitting some old Cisco Cat5505s
who have to process switch the traffic and they can't keep up.

Here is a partial snapshot of mroute count soon after clearing stats:

  Source: 204.121.50.18/32, Forwarding: 274/9/89/6, Other: 3/0/0
  Source: 205.253.57.122/32, Forwarding: 275/9/98/7, Other: 3/0/0
  Source: 206.220.241.245/32, Forwarding: 273/9/91/6, Other: 3/0/0
  Source: 209.245.19.27/32, Forwarding: 8583/284/80/176, Other: 57/0/0
  Source: 210.25.130.54/32, Forwarding: 270/9/90/6, Other: 3/0/0
  Source: 210.25.133.16/32, Forwarding: 268/9/94/6, Other: 3/0/0


For the time being I had to shut down my beacon clients, but I can't be sure
that someone else on campus won't start them up.  Does anyone know who to
contact regarding this host or what the problem may be with their client?

Amel