From: John (jgarrison1@austin.rr.com)
Date: Tue Oct 30 2007 - 14:09:57 ART
I have the following scenario.
S---R3----R1----R2---R4
| |
R5-------------
|
R6-----H
R4 connects to R5(my diagram isn't the best). I'm asked to enable PIM in
dense mode on all transit interfaces, except on the link between R1 and R5.
This causes a RPF failure in the link between R4 and R5. I use a static
mroute on R5 to override the RPF check. On R5 I get this for sh Mroute
224.1.1.1 before the mroute is installed
(*, 224.1.1.1), 00:02:00/stopped, RP 0.0.0.0, flags: D
Incoming interface: Null, RPF nbr 0.0.0.0
Outgoing interface list:
FastEthernet0/1, Forward/Dense, 00:02:00/00:00:00
Serial2/0.1, Forward/Dense, 00:02:00/00:00:00
(10.1.37.7, 224.1.1.1), 00:02:00/00:00:59, flags:
Incoming interface: Null, RPF nbr 150.1.15.1
Outgoing interface list:
Serial2/0.1, Forward/Dense, 00:02:00/00:00:00
FastEthernet0/1, Forward/Dense, 00:02:00/00:00:00
Why do I show my RPF neighbor for the (S,G) being 150.1.15.1 (R1's address).
How did it get there. Once the group is advertised doesn't it flow
downstream. That should mean that R5's incoming interface for the 224.1.1.1
entry should be connected to R4. Why is it picking up R1's address which does
not have PIM enabled on it and neither does the interface which connects to R1
from R5? I'm getting ready to read the RFC for PIM in dense mode, but if
anyone can shine a light on this feel free.
This archive was generated by hypermail 2.1.4 : Fri Nov 16 2007 - 13:11:19 ART