RE: IE Vol1 LAB 2 Multicast over Frame Relay Cloud

From: Greg Gombas (ggombas@hotmail.com)
Date: Wed Jan 04 2006 - 16:35:47 GMT-3


Hi Brian,

In my first posting I forgot to mention the additional point to point link
between R2 and R3 which is exchanging EIGRP.
This point-to-point link is the preffered path to the loopback address of
R2.
Unfortunately the task requirement does not allow you to configure PIM on
this point to point link.

It looks like this:

R6 (Source)
     |
     R2-
   / \ \
R1----R3
|
SW1 (Receiver)

Can you tell me why an mroute on R3 pointing to the frame relay interface of
R2 allows this to work?

----Original Message Follows----
From: "Brian McGahan" <bmcgahan@internetworkexpert.com>
To: "Greg Gombas" <ggombas@hotmail.com>,<ccielab@groupstudy.com>
Subject: RE: IE Vol1 LAB 2 Multicast over Frame Relay Cloud
Date: Wed, 4 Jan 2006 12:49:02 -0500

If they are in a full mesh why would R1 see R3 as the next-hop to reach R2?

Brian McGahan, CCIE #8593
bmcgahan@internetworkexpert.com
Internetwork Expert, Inc.
http://www.InternetworkExpert.com
Toll Free: 877-224-8987 x 705
Outside US: 775-826-4344 x 705
24/7 Support: http://forum.internetworkexpert.com
Live Chat: http://www.internetworkexpert.com/chat/

________________________________

From: nobody@groupstudy.com on behalf of Greg Gombas
Sent: Tue 1/3/2006 4:40 PM
To: ccielab@groupstudy.com
Subject: IE Vol1 LAB 2 Multicast over Frame Relay Cloud

Hello,

I was hoping someone help me figure out this scenario.

R6 (Source)
     |
     R2
   / \
R1----R3
|
SW1 (Receiver)

R1, R2 and R3 are connected via a full frame relay mesh.
OSPF is runnig on the frame relay mesh in point-to-multipoint mode.

R2 is acting as RP with static RP configured on all devices.

R1 is showing R3 as next hop to RP.

I am doing debug ip pim on all devices and I can see that R1 is sending the
PIM join message from SW1 to R3 but R3 is not forwarding the join message to
R2.

I did all the debugs I can think of on R3 but there is no indication of an
RPF failure. How can I troubleshoot this?

Thanks,
Greg



This archive was generated by hypermail 2.1.4 : Wed Feb 01 2006 - 07:45:47 GMT-3