From: vcappuccio@gmail.com
Date: Sun Feb 11 2007 - 23:38:24 ART
Hi,
I found this link
http://ftp.uth.gr/Mbone/guides/multicast_troubleshooting_guide.html#RPF%20FAILURE
very informative to understand some Multicast hidden Stuff
if you allow me to comment more about this, as a side note, if we are not able to modify the routing table using static routes, or within the lab wording we are not permitted to modify in some way the IGP Protocol Part (be aware of Routing Redistribution and all that), in order to modify the RPF information, then Static Mroutes should be allowed, else we are going to have this pretty output from the router when enabling the "debug ip mpacket". --> "not RPF interface" meaning that we have an RPF lookup failure, and probably we are going to fail those simple Multicast Point. Once you enter these debug command, you can observe one of the following outputs:
Functioning state:
Feb 11 03:19:35.295: IP(0): s=44.44.44.44 (Serial0/0) d=244.4.4.4
(Serial0/1) id=619, prot=1, len=100(100), mforward
Malfunctioning state:
Feb 11 04:14:51.251: IP(0): s=44.44.44.44 (Serial0/0) d=244.4.4.4
id=477, prot=1, len=104(100), not RPF interface
Remember that on the interfaces that is receiving the multicast traffic, to enter the following interface configuration command: no ip mroute-cache
Just My 2 Cents more to this thread
Victor.-
This archive was generated by hypermail 2.1.4 : Thu Mar 01 2007 - 07:38:46 ART