From: Mark Stephanus Chandra (mark.chandra@gmail.com)
Date: Thu Jul 03 2008 - 03:32:54 ART
I did, with ip nbma-mode, anyway I am using IP PIM Sparse-dense-mode so I
guess it is not necessary to activate nbma-mode feature right ?
Reards
Mark Stephanus Chandra
IT Consultant
From: Jason Madsen [mailto:madsen.jason@gmail.com]
Sent: 03 Juli 2008 12:08
To: Mark Stephanus Chandra
Cc: SAM Meng Wai; ccielab@groupstudy.com
Subject: Re: Multicast Problem
I didn't look at your complete set of config's, but seeing that your
disconnect is across a frame link you may want to try using "ip pim
nbma-mode" (both ends of frame link).
Jason
On Wed, Jul 2, 2008 at 7:03 PM, Mark Stephanus Chandra
<mark.chandra@gmail.com> wrote:
I Have Check it, no problem with rpf.
Just to make it clear, rpf is considered okay if the incoming packet from r1
to sw2 must be go out back with the sam interface right ?
Regards
Mark Stephanus Chandra
IT Consultant
-----Original Message-----
From: SAM Meng Wai [mailto:mwsam@starhub.com]
Sent: 03 Juli 2008 5:38
To: Mark Stephanus Chandra
Subject: RE: Multicast Problem
Hi,
Can you check SW2 for any rpf issue to R1 source IP addresss ?
Rgds
________________________________
From: nobody@groupstudy.com on behalf of Mark Stephanus Chandra
Sent: Thu 7/3/2008 1:47 AM
To: ccielab@groupstudy.com
Subject: Multicast Problem
Hi all,
I have a question About Multicast
Topology :
R1-----FRAME RELAY Point to Point ------R3----ethernet---SW2---ethernet ip
igmp join group 239.23.23.23
R3 is the autorp and the mapping agent.
I can do ping from R3 to the group 239.23.23.23
But I cannot ping it from R1 :
R1#sh 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
(*, 239.23.23.23), 00:01:07/stopped, RP 150.1.3.3, flags: SP
Incoming interface: Serial1/0, RPF nbr 162.1.13.3
Outgoing interface list: Null
(162.1.13.3, 239.23.23.23), 00:01:07/00:01:54, flags: PT
Incoming interface: Serial1/0, RPF nbr 0.0.0.0
Outgoing interface list: Null
(*, 224.0.1.39), 01:43:48/stopped, RP 0.0.0.0, flags: DC
Incoming interface: Null, RPF nbr 0.0.0.0
Outgoing interface list:
Serial1/0, Forward/Sparse-Dense, 01:43:48/00:00:00
(150.1.3.3, 224.0.1.39), 00:02:34/00:00:25, flags: PT
Incoming interface: Serial1/0, RPF nbr 162.1.13.3
Outgoing interface list: Null
(*, 224.0.1.40), 01:44:28/stopped, RP 0.0.0.0, flags: DCL
R1#sh ip pim rp
Group: 239.23.23.23, RP: 150.1.3.3, v2, v1, uptime 01:38:37, expires
00:02:17
R1#ping 239.23.23.23
Type escape sequence to abort.
Sending 1, 100-byte ICMP Echos to 239.23.23.23, timeout is 2 seconds:
.
R1#
R1#mtrace 162.1.13.1 239.23.23.23
Type escape sequence to abort.
Mtrace from 162.1.13.1 to 162.1.13.1 via group 239.23.23.23
From source (?) to destination (?)
Querying full reverse path... * switching to hop-by-hop:
0 162.1.13.1
-1 * * * Timed out receiving responses
Perhaps no local router has a route for source, the receiver is not
a member of the multicast group or the multicast ttl is too low.
Can you guys figure it out why I cannot ping the group address
Mark Stephanus Chandra
IT Consultant
This archive was generated by hypermail 2.1.4 : Mon Aug 04 2008 - 06:11:53 ART