Chris,
Thanks for the information. This is a good start. I had considered setting this
up in a lab but I suspected that it would not tell me much and I would not be
able to reproduce such a problem. I will post what I find if it would be of any
interest.
Regards
Mike
~~~~~~~~~~~~~~~
Mike Judd
MTS, JNCIS-M
Alcatel-Lucent
1 Robbins Road
Westford, MA 01886
office: 978-952-1516
Technical Support Operations Americas
Toll Free: 1 (866) 582-3688
Direct Dial: 1-613-784-8928
Prompt 1: Remote Technical Support
Prompt 2: Parts Repair or Exchange
Prompt 3: On-Site Technical Support dispatch
Prompt 7: OnLine Customer Support Web Site support
~~~~~~~~~~~~~~~~~
-----Original Message-----
From: Chris Spears [mailto:[email protected]]
Sent: Wednesday, July 29, 2009 5:29 PM
To: Judd, Michael (Michael)
Cc: [email protected]
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 [email protected]
> https://puck.nether.net/mailman/listinfo/juniper-nsp
--
%%%%%%%%%%%%%%%%%%%%%%%%%%%
Chris Spears, OARnet
Senior Routing Engineer
phone: 614-292-9415
fax: 614-728-8110
_______________________________________________
juniper-nsp mailing list [email protected]
https://puck.nether.net/mailman/listinfo/juniper-nsp