On Wed, Jul 27, 2011 at 5:42 AM, marc abel <marcabel_at_gmail.com> wrote:
> Without seeing your topology I can't say where you would need a static
> mroute, you may not need one at all. Make sure you are running pim on
> both the physical interfaces and all interfaces on their routes back
> to the source(confirm with traceroute). make sure the current HSRP
> active router has a higher pim dr priority than the standby. If your
> primary dies, the secondary should pick up gateway and pim forwarding
> duties at the same time.
>
> Remember mroute doesn't specify the route for traffic. It is a way to
> disable a loop prevention check in multicast. It makes it permissible
> to receive multicast on an interface different than the one it would
> normally route traffic to.
>
correctly said the static mroutes are not like static unicast route.
they dont make forwarding decisions.The multicast forwarding is based on
entries in OIL list .
if u are running any pim falvor that uses sparse mode of opeartion , try
using mtrace command
first from the source DR to RP ,
second from receiver DR to RP
Third from reciver DR to source .
>
> If you can post some topology I can try to help further, otherwise if
> you have the abilty to test you might try the above without a static
> mroute.
>
>
> On Tue, Jul 26, 2011 at 6:10 PM, JB Poplawski <jb.poplawski_at_gmail.com>
> wrote:
> > So do I still set my default m-route 0.0.0.0 to the hsrp address or to
> > one of the physical IPs?
> >
> > What happens with a failover? IE I set it to one physical IP, that
> > box dies, etc.
> >
> > Sorry for the basic questions, Multicast isn't my strong suit.
> >
> > On Tue, Jul 26, 2011 at 6:05 PM, marc abel <marcabel_at_gmail.com> wrote:
> >> Just to be clear I mean your PIM DR.
> >>
> >> ip pim dr-priority 100
> >>
> >> On Tue, Jul 26, 2011 at 6:04 PM, marc abel <marcabel_at_gmail.com> wrote:
> >>> Try setting your DR priority. I ran into a similar issue where my
> >>> secondary HSRP was being elected the DR for the segment since it had a
> >>> higher IP address. Once I set the DR to the primary hsrp switch all
> >>> was well. This should still fail over fine as well.
> >>>
> >>> -Marc
> >>>
> >>> On Tue, Jul 26, 2011 at 5:18 PM, JB Poplawski <jb.poplawski_at_gmail.com>
> wrote:
> >>>> Good afternoon,
> >>>>
> >>>> I'm currently running into a random multicast issue. We have a
> >>>> connection to a vendor sending us multicast feeds. I have static
> >>>> routes to the source ips to their HSRP address for RPF purposes. My
> >>>> host subscribes and I can see (with show ip mroute) the groups show
> >>>> up, but no data. Figuring it was an HSRP issue, I added a static
> >>>> M-Route to one of the physical host IPs and BAM!!! starting receiving
> >>>> traffic.
> >>>>
> >>>>
> http://www.cisco.com/en/US/tech/tk828/technologies_tech_note09186a0080094aab.shtml
> >>>>
> >>>> Where's my goof? I add the static m-route to the HSRP address it
> >>>> stops, re-add to a physical and it works again. My concern is if I
> >>>> add a default static m-route to a physical device and that host dies,
> >>>> I have to hurry quick and change the default m-route.
> >>>>
> >>>> Topology is basically the same as attached cisco document.
> >>>>
> >>>> Any thoughts or creating solutions?
> >>>> JB
> >>>>
> >>>>
> >>>> Blogs and organic groups at http://www.ccie.net
> >>>>
> >>>>
> _______________________________________________________________________
> >>>> Subscription information may be found at:
> >>>> http://www.groupstudy.com/list/CCIELab.html
>
>
> Blogs and organic groups at http://www.ccie.net
>
> _______________________________________________________________________
> Subscription information may be found at:
> http://www.groupstudy.com/list/CCIELab.html
Blogs and organic groups at http://www.ccie.net
Received on Thu Jul 28 2011 - 12:30:39 ART
This archive was generated by hypermail 2.2.0 : Mon Aug 01 2011 - 06:30:06 ART