Go CCIE Go!! - A Cisco Certified Internetwork Expert

Hi Mark
Yeah, ping echo reply is unicast.
But the bigger issue is you mix up the use of static multicast “ip mroute” and normal static route in general.
Static multicast route is to fix RPF failure issue. It is not made to route multicast traffic! In most cases, you do not even need to have ip mroute (NOT “always perform on client attached router” as you mentioned if you do not have RPF issue)!
Cheers,
—–Original Message—– From: nobody@groupstudy.com [mailto:nobody@groupstudy.com] On Behalf Of Mark Stephanus Chandra Sent: Tuesday, 26 August 2008 11:19 AM To: ccielab@groupstudy.com Subject: Multicast Question
Guys,
I have a simple question about multicast. I’m wondering why ip multicast route static always perform on client attached router and no ip multicast route static to come back from the source ?
like these example of question :
Multicast Source ——– R4 ———–R3————–R1——-Multicast Client
Connection between R4 - R3 - R1 happen to be frame-relay, so it is a hub and spoke topology with R3 as the hub.
The solution is create tunnel between R4 and R1 using ip mroute to multcast source on R1 with Tunnel interface as the gateway and there is no ip multicast static route to go back to multicast client.
The Question is How R4 going back to R1 ? Using unicast routing table ?
If Yes then it’s not going back using the interface tunnel right ? so it is not a symectric routing solution.
Hope you guys know what I meant
Thanks a lot
— Mark Stephanus Chandra
Blogs and organic groups at http://www.ccie.net