From: D. J. Jones (meganac@xxxxxxxxx)
Date: Sat Jul 06 2002 - 22:51:49 GMT-3
If you have not done so yet, please pick up Beau Williamson's Developing IP
Multicast Networks book.
There is a very good section on operating multicast over frame relay. In
it, it elaborates on some of the
issues relative to frame relay using a logical ip subnet (LIS) or the use of
physical frame interfaces opposed
to pt-pt subinterfaces. The use of the ip pim nbma-mode command ensures the
next hop information in the
(*,G) and (S,G) outgoing interface list is maintained.
..dj
----- Original Message -----
From: "Joe Higgins" <netsat@optonline.net>
To: <ccielab@groupstudy.com>
Sent: Wednesday, June 26, 2002 2:23 PM
Subject: Re: muticast sparse0dense using frame relay
> Changing the interfaces from r4 to r1 from physical frame to
point-to-point
> frame subinterfaces fixes this problem. I do not know why it fixes the
> problem?
>
> Joe Higgins wrote:
>
> > I have the following problem. I have three routers r4, r1 and r2. All
> > have ip multicasting-routing running. R4 is connected to r1 via frame.
> > serial 1 to serial 1. R1 is connected to r2 via frame, serial 0 to
> > serial 0. All affected interfaces are running ip pim sparse-dense. R2
> > has ip igmp join on its e0 interface for multicast address 224.0.7.7.
> > Ospf is running between al routers
> > R4-s1 <> R1-s1-R1-s0 <> R2-s0
> >
> > Before I enable auto rp on R2 I can ping 224.0.7.7 from r4. After I
> > enable auto rp on r2 I cannot ping 224.0.7.7 from r4. I have configured
> > both announce and discovery on r2. R1 mroute shows the following when
> > it fails.
> >
> > (*, 224.0.1.39), 00:19:43/00:02:59, RP 0.0.0.0, flags: DJC
> > Incoming interface: Null, RPF nbr 0.0.0.0
> > Outgoing interface list:
> > Serial0, Forward/Sparse-Dense, 00:19:43/00:00:00
> > Serial1, Forward/Sparse-Dense, 00:19:43/00:00:00
> >
> > (2.2.2.2, 224.0.1.39), 00:00:43/00:02:16, flags: PCT
> > Incoming interface: Serial0, RPF nbr 1.1.2.2
> > Outgoing interface list:
> > Serial1, Prune/Sparse-Dense, 00:00:43/00:02:22
> >
> > (*, 224.0.1.40), 00:20:25/00:00:00, RP 0.0.0.0, flags: DJCL
> > Incoming interface: Null, RPF nbr 0.0.0.0
> > Outgoing interface list:
> > Serial0, Forward/Sparse-Dense, 00:20:25/00:00:00
> > Serial1, Forward/Sparse-Dense, 00:20:26/00:00:00
> >
> > (2.2.2.2, 224.0.1.40), 00:19:53/00:02:59, flags: CLT
> > Incoming interface: Serial0, RPF nbr 1.1.2.2
> > Outgoing interface list:
> > Serial1, Forward/Sparse-Dense, 00:19:53/00:00:00
> >
> > (*, 224.0.7.7), 00:00:11/00:02:59, RP 2.2.2.2, flags: SP
> > Incoming interface: Serial0, RPF nbr 1.1.2.2
> > Outgoing interface list: Null
> >
> > (1.1.4.4, 224.0.7.7), 00:00:11/00:02:48, flags: PT
> > Incoming interface: Serial1, RPF nbr 1.1.4.4
> > Outgoing interface list: Null
> >
> > On both r1 and r4 a show ip pim rp mapp indicates
> >
> > Group(s) 224.0.0.0/4
> > RP 2.2.2.2 (?), v2v1
> > Info source: 2.2.2.2 (?), via Auto-RP
> > Uptime: 00:34:44, expires: 00:01:59
> >
> > R1 gets the ping but fails to send it to an outgoing interface. I know
> > that there is a problem wt. multicast and frame but what I have read
> > only refers to coming in and out of the same physical interface.
> >
> > Additional facts are as follows. If I make the connection from r4 to r1
> > hdlc, it works. If I put the rp announce and agent on r1, it works. I
> > have spent a couple of days on this and any help would be appreciated.
> > I really hurts not having the search facility working on this site.
> > Thanks in advance.
This archive was generated by hypermail 2.1.4 : Sat Sep 07 2002 - 19:36:21 GMT-3