[j-nsp] PIM SM RP issue

[Nilesh Khambal]

On M10is acting as RP, do you a route similar to this in the kernel and
cfeb?

R.R.R.R.S.S.S.S.103.a.b.c.d/104 ---> pd-x/y/z

To check this in the RE kernel you need to do "show route forwarding-table"
and in the cfeb "show route ip"

R.R.R.R is the address configured as RP and S.S.S.S is the address
configured on Source DR.

Some of the possibilities to look for the issue are

- show multicast route group <group> extensive
   See if pd interface is showing up as incoming interface for any multicast
   stream.
- Route back to the source DR IP address (Cisco is this case) is missing on
  the RP. Register stops are not making it back to source DR

In addition, the command suggested by Stacy are also good.

Thanks,
Nilesh.






On 12/15/10 8:35 AM, "Philip Palanchi" <palanchi at rutgers.edu> wrote:

> We're seeing what seems to be an interoperability problem when we configure
> PIM Sparse-mode Rendezvous Point on either m10i or mx240 and the PIM source
> registration messages are coming from cisco routers where the cfeb's, fpc's
> and dpc's go to 100% cpu utilization all the time. The box stops responding to
> snmp management, but multicast seems to work ok.
> 
> It seems to be that the pd interface on the RP isn't de-capsulating the
> register messages. JTAC said the pe interface on the encapsulating routers
> needs a tunnel services PIC but our edge routers are all cisco.  Any
> suggestions?
> 
> Thanks,
> Phil
> 
> _______________________________________________
> juniper-nsp mailing list juniper-nsp at puck.nether.net
> https://puck.nether.net/mailman/listinfo/juniper-nsp