From: John Matus (jmatus@pacbell.net)
Date: Wed Aug 18 2004 - 22:00:07 GMT-3
my understanding of rpf failure is that the interface the router is expecting
the multicast traffice in on is different than the unicast path... below, the
rpf failure is for 172.16.120.1, which should be reachable out interface e0/0
is pointing to s0/0.1. should the destination of my static mroute be the
next hop address towards that address or the connected interface pointing
towards the next hop. (i used the next hop address - ip mroute 172.16.120.1
255.255.255.255 172.16.23.20.......but i'm still getting the rpf failures
*Mar 1 02:30:21.603: IP(0): s=172.16.120.1 (Ethernet0/0) d=224.0.1.40
id=3860, prot=17, len=62(48), mroute olist null
*Mar 1 02:30:21.603: IP(0): s=172.16.120.1 (Ethernet0/0) d=224.0.1.40
id=3861, prot=17, len=62(48), mroute olist null
*Mar 1 02:30:21.619: IP(0): s=172.16.120.1 (Serial0/0.1) d=224.0.1.40
id=3860, prot=17, len=52(48), not RPF interface
*Mar 1 02:30:21.627: IP(0): s=172.16.120.1 (Serial0/0.1) d=224.0.1.40
id=3861, prot=17, len=52(48), not RPF interface
John D. Matus
MCSE, CCNP
Office: 818-782-2061
Cell: 818-430-8372
jmatus@pacbell.net
This archive was generated by hypermail 2.1.4 : Fri Sep 03 2004 - 07:02:45 GMT-3