[j-nsp] PIM SM RP issue

[Stefan Fouant]

> -----Original Message-----
> From: juniper-nsp-bounces at puck.nether.net [mailto:juniper-nsp-
> bounces at puck.nether.net] On Behalf Of Philip Palanchi
> Sent: Wednesday, December 15, 2010 11:36 AM
> To: juniper-nsp
> Subject: [j-nsp] PIM SM RP issue
> 
> 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?

If you recall from Multicast 101, initial communications from the router
connected to the Multicast source are unicast via an encapsulated PIM
Register Start message destined towards the RP.  The only time you need a
tunnel services card is if your Juniper router happens to be either the
router connected to the Multicast source (in which case it would be doing
PIM Encapsulation) or it happens to be the RP (in which case it would be
doing PIM Decapsulation).

This only happens for the first few packets until the native multicast state
is built between the RP and the Sourcing router, in which case the traffic
traverses the normal RP tree via multicast mechanisms.

Since your boxes are the RPs, they would need a PIC capable of handling
tunnel services - this could be a Tunnel Service PIC, an Adaptive Services
PIC, or a Multi-Services PIC.  If you happen to have an M7i or J-Series then
you likely have an integrated ASM module and don't need an additional PIC
for tunneling services.

HTHs. 

Stefan Fouant, CISSP, JNCIEx2
www.shortestpathfirst.net
GPG Key ID: 0xB4C956EC