All things related to multicast

["Alexander Hsia" <>]

Your request #71 was updated by alex.hsia:

I'm trying to troubleshoot a multicast problem on our campus.

Has anyone seen behavior similar to the following:

I had a couple of hosts on our campus join the multicast beacon
group.  After stopping the beacon on one host (140.172.6.2) I
still see it in a joined state.  A clear of the mroute on my RP
causes a join to come from my upstream MSDP peer (the Abilene
DNVR router) with the state as follows:

brdwy-rtr#sh ip mroute 233.2.171.1 140.172.6.2
IP Multicast Routing Table
Flags: D - Dense, S - Sparse, C - Connected, L - Local, P -
Pruned
       R - RP-bit set, F - Register flag, T - SPT-bit set, J -
Join SPT
       M - MSDP created entry, X - Proxy Join Timer Running
       A - Candidate for MSDP Advertisement
Outgoing interface flags: H - Hardware switched
Timers: Uptime/Expires
Interface state: Interface, Next-Hop or VCD, State/Mode

(140.172.6.2, 233.2.171.1), 00:02:02/00:01:27, flags: CT
  Incoming interface: ATM0/0.6, RPF nbr 0.0.0.0, Registering
  Outgoing interface list:
    ATM0/0.254, Forward/Sparse-Dense, 00:02:02/00:00:57

Abilene states that it's a misconfiguration of one of the
connector networks.  Is there a way that Abilene can prevent
JOINS for addresses that aren't within that connector's AS?