[j-nsp] Multicast, ASM and SSM

[Judd, Michael (Michael)]

Hi Chris,

I have noticed that the output of "show igmp group brief" is listing the SSM sources but not the ASM sources. 

There is also something else I've uncovered which I do not know if it is relevant or not.
In the once freely available JUNOS Enterprise Routing guide (thanks Doug M), page 582, top  of the page, a note indicates that tunnel services hardware is required to perform the register encapsulation/decapsulation functions if PIM sparse mode is being used. The J and M7i's have this capability built-in. The note goes on to say "you can still commit a PIM sparse mode config but things simply won't work".

No PIM rib-groups are being used. 

Here is some other output that might be useful. 
RE0> show multicast rpf 233.3.18.5 (ASM)         
Multicast RPF table: inet.0 , 254 entries

0.0.0.0/0
    Protocol: BGP
    Interface: so-0/0/0.0
    Neighbor: 146.97.40.17

{master}
RE0> show msdp peer 146.97.40.17 
Peer address    Local address   State       Last up/down Peer-Group   SA Count
146.97.40.17    146.97.40.18    Established      12w1d2h external-msd 2480/2550


Thanks 

Regards

Mike


-----Original Message-----
From: Chris Spears [mailto:cspears at eng.oar.net] 
Sent: Wednesday, July 29, 2009 5:29 PM
To: Judd, Michael (Michael)
Cc: juniper-nsp at puck.nether.net
Subject: Re: [j-nsp] Multicast, ASM and SSM

Michael-

   SSM is working, so you've already verified that PIM is configured, as well as IGMP on the LAN.  If it's on the network side, it's most likely a MSDP (or RP) problem.  Some odd IGMP issues on the local switched network could cause a problem, and well as buggy host problems, both of which are harder to diagnose.

   Start at the DR router (the one closest to non-receiving beacon). 
Verify that the RP-mapping is there, and a route to the RP.   Check the 
RP to ensure that MSDP has a source-active for the group (or if the DR 
router is the RP, just check it there).   Verify RPF along the way. 
Also remember that MSDP needs to have inet.2 & interface-routes, just like PIM, so if you created a PIM rib-group, apply it to MSDP as well.

   This of course assumes that because you're using beacons there are several active sources and listeners. Otherwise, always check for active sources and listener interest first.

-Chris


Judd, Michael (Michael) wrote:
> question; I am working on an issue where a multicast beacon receives SSM sources but not ASM sources. Other beacons in the network can see both ASM and SSM. I am wondering what I should check first.
> 
> Thank you
> _______________________________________________
> juniper-nsp mailing list juniper-nsp at puck.nether.net 
> https://puck.nether.net/mailman/listinfo/juniper-nsp

-- 

%%%%%%%%%%%%%%%%%%%%%%%%%%%
Chris Spears, OARnet
Senior Routing Engineer
phone: 614-292-9415
fax: 614-728-8110