All things related to multicast

[Tom Pusateri <>]

I agree. The static entry should be last resort or for permanantly nailing
up membership.

The JTAC should be able to get you up and running but to get started,
look at "show pim join 233.2.171.1 extensive". This will show you the
upstream and downstream pim state. "show multicast rpf x.x.x.x" with a
source address of a known beacon will also indicate if you are pointing
upstream correctly. This could be a simple RPF problem.

Tom

In message 
<>
 you write:
>A call for help...
>
>I'm trying to get multicast "to work" on with a host directly attached to a 
>fast ethernet port on a Juniper M40 running JUNOS 5.6R1.3.  The host is 
>running Windows XP Professional.
>
>I'll just focus on the beacon group, 233.2.171.1.  The host IP is 
>192.88.115.114.
>
>In our "default" configuration, "show multicast route group 233.2.171.1" 
>shows this (S,G) in a pruned state.  If I add static igmp group membership 
>for 233.2.171.1 to the interface, I now see the (S,G) in a forwarding 
>state.  However, our upstream 12008 does not see an mroute entry for the 
>(S,G).  The host does show up on the beacon page as receiving other beacons 
>(but nothing hears it).  The RPF checks are as they should be (some manual 
>configuration was necessary, or at least sufficient).
>
>My first hunch is that MSDP is not announcing the (S,G) from the Juniper to 
>the Cisco.  Does this sound plausible, and, if so, how do I fix it?  And is 
>there some magic configuration piece I'm missing?  I don't like the idea of 
>having to do static configuration.
>
>Thanks,
>
>Michael
>
>+-----------------------------------------------------------------------+
>| Michael H. Lambert, Network Engineer           Phone: +1 412 268-4960 |
>| Pittsburgh Supercomputing Center               FAX:   +1 412 268-8200 |
>| 4400 Fifth Avenue, Pittsburgh, PA  15213       
>
>        |
>+-----------------------------------------------------------------------+
>