From: Greg Gombas (ggombas@hotmail.com)
Date: Thu Jan 26 2006 - 01:33:57 GMT-3
You are correct but in this case the mroute also causes the router to use
the frame interface as the RPF interface to the RP. Look at my mroute table
before and after the mroute:
Before...
Rack1R3#show ip mroute
IP Multicast Routing Table
Flags: D - Dense, S - Sparse, B - Bidir Group, s - SSM Group, C - Connected,
L - Local, P - Pruned, R - RP-bit set, F - Register flag,
T - SPT-bit set, J - Join SPT, M - MSDP created entry,
X - Proxy Join Timer Running, A - Candidate for MSDP
Advertisement,
U - URD, I - Received Source Specific Host Report,
Z - Multicast Tunnel, z - MDT-data group sender,
Y - Joined MDT-data group, y - Sending to MDT-data group Outgoing
interface flags: H - Hardware switched, A - Assert winner
Timers: Uptime/Expires
Interface state: Interface, Next-Hop or VCD, State/Mode
(*, 228.28.28.28), 01:51:37/00:03:24, RP 150.1.2.2, flags: S
Incoming interface: Null, RPF nbr 0.0.0.0, Mroute
Outgoing interface list:
Serial1/0/0, 132.1.0.1, Forward/Sparse, 00:06:01/00:03:24
(*, 224.0.1.40), 03:19:22/00:02:57, RP 150.1.2.2, flags: SJCL
Incoming interface: Null, RPF nbr 0.0.0.0, Mroute
Outgoing interface list:
FastEthernet1/0, Forward/Sparse, 03:19:15/00:02:57
Serial1/0/0, 132.1.0.1, Forward/Sparse, 00:06:16/00:02:51
Rack1R3#
After...
Rack1R3#show ip mroute
IP Multicast Routing Table
Flags: D - Dense, S - Sparse, B - Bidir Group, s - SSM Group, C - Connected,
L - Local, P - Pruned, R - RP-bit set, F - Register flag,
T - SPT-bit set, J - Join SPT, M - MSDP created entry,
X - Proxy Join Timer Running, A - Candidate for MSDP
Advertisement,
U - URD, I - Received Source Specific Host Report,
Z - Multicast Tunnel, z - MDT-data group sender,
Y - Joined MDT-data group, y - Sending to MDT-data group Outgoing
interface flags: H - Hardware switched, A - Assert winner
Timers: Uptime/Expires
Interface state: Interface, Next-Hop or VCD, State/Mode
(*, 228.28.28.28), 01:55:38/00:03:19, RP 150.1.2.2, flags: S
Incoming interface: Serial1/0/0, RPF nbr 132.1.0.2, Mroute
Outgoing interface list:
Serial1/0/0, 132.1.0.1, Forward/Sparse, 00:10:02/00:03:19
(132.1.6.6, 228.28.28.28), 00:02:34/00:03:28, flags: T
Incoming interface: Serial1/0/0, RPF nbr 132.1.0.2, Mroute
Outgoing interface list:
Serial1/0/0, 132.1.0.1, Forward/Sparse, 00:02:35/00:03:18
(132.1.26.6, 228.28.28.28), 00:02:35/00:03:27, flags: T
Incoming interface: Serial1/0/0, RPF nbr 132.1.0.2, Mroute
Outgoing interface list:
Serial1/0/0, 132.1.0.1, Forward/Sparse, 00:02:35/00:03:18
(*, 224.0.1.40), 03:23:24/00:02:55, RP 150.1.2.2, flags: SJCL
Incoming interface: Serial1/0/0, RPF nbr 132.1.0.2, Mroute
Outgoing interface list:
FastEthernet1/0, Forward/Sparse, 03:23:17/00:01:56
Serial1/0/0, 132.1.0.1, Forward/Sparse, 00:10:18/00:02:54
Rack1R3#
Notice the section:
(*, 228.28.28.28), 01:55:38/00:03:19, RP 150.1.2.2, flags: S
Incoming interface: Serial1/0/0, RPF nbr 132.1.0.2, Mroute
By the way, did you use PIM nbma-mode on R3's frame interface ? I don't
think that was in the solution guide and I needed it to work...
----Original Message Follows----
From: Scott Smith <hioctane@gmail.com>
To: ggombas@hotmail.com
CC: ccielab@groupstudy.com
Subject: Re: IEWB V3 Lab 2 Multicast
Date: Wed, 25 Jan 2006 21:54:15 -0600
Thanks for the reply.
I've actually tried that config and it didn't work for me. The join is
never sent up to R2 (verified with debug). Thus far I've found three
configs that work:
1) Enable PIM on the HDLC link between R2 and R3 (preferred path from R3 to
R2)
2) Place a static route (not mroute) on R3 to force traffic to R2 out
the frame int
3) Advertise R2's loopback into OSPF instead of EIGRP (side effect is
this hoses R6 but the join works <g>)
My understanding of a static mroute is: you're telling the router it
is ok to receive this source on an interface that isn't the same
interface you would use to forward traffic to this source. Right, I
hope?
-Scott
On 1/25/06, ggombas@hotmail.com <ggombas@hotmail.com> wrote:
> Hello Scott,
>
> I had the same issue a few weeks back.
> The solution is to add a 0.0.0.0 0.0.0.0 mroute on R3 pointing to the IP
of R2 frame relay interface and also enable PIM NBNA mode on R3's frame
relay interface.
>
> Here is the relevant config:
>
> R3
> ip multicast-routing
>
> int ser1/0
> ip pim sparse-mode
> ip pim nbma-mode
>
> ip pim rp-address 150.1.2.2
> ip mroute 0.0.0.0 0.0.0.0 132.1.0.2
>
> Although I still don't completely understand why this works Scott Morris
suggested that the mroute allows R3 to send the join out the frame
interface.
>
> _______________________________________________________________________
> Subscription information may be found at:
> http://www.groupstudy.com/list/CCIELab.html
This archive was generated by hypermail 2.1.4 : Wed Feb 01 2006 - 07:45:50 GMT-3