From: Joseph Brunner (joe@affirmedsystems.com)
Date: Sun Jun 15 2008 - 08:55:17 ART
The router doing the ping is sending pings from all interfaces, try "ping
224.1.1.1 source S0" on R3 if you don't want to enable multicast on E0.
When you enabled multicast on R3's E0 and you pinged, this time that
interface can join the tree and get the feed.
The DR message simply says it's the DR on the segment, now that pim has
started on R3's E0.
-Joe
-----Original Message-----
From: nobody@groupstudy.com [mailto:nobody@groupstudy.com] On Behalf Of
David Lonnie
Sent: Sunday, June 15, 2008 7:19 AM
To: ccielab@groupstudy.com
Subject: A question about multicast
Hi,folks:
This is a question about multicast.
This is my topology.
R1(e0)--------------(e0)R2(s0)--------------------(s0)R3(e0)---
These interfaces configurated in sparse-dense-mose.
R1:e0 and lo0
R2:e0 and s0
R3:s0
R1 is auto-rp candicate and bsr for group 224.1.1.1
and now i ping 224.1.1.1 on R2, it's OK.
but when i ping the group on R3,it shows timeout.
when i add "ip pim sparse-dense-mode" command to the e0 interface of
R3,there is a log message:
*Mar 2 19:55:46.007: %PIM-5-DRCHG: DR change from neighbor 0.0.0.0 to
150.1.8.1
on interface Ethernet0/0
and then ping the group,it works.
That's why? it seems strange.
can somebody clarify this occurrence for me?
Thanks in advance for your help.
David
This archive was generated by hypermail 2.1.4 : Tue Jul 01 2008 - 06:23:21 ART