From: Mike Flanagan (mikenoc@mindspring.com)
Date: Wed Oct 13 2004 - 02:58:51 GMT-3
On R2 I am getting an olist null when I ping the address. From R3 I can
ping it fine. Did a debug ip mroute on R3 and on R5 and sure enough R5
Was getting the RPF failure. Did a show ip route for the source address and
The IGP route should have been the routers ethernet interface and it was
Received on the serial interface. Added an mroute for the /24 out the serial
interface and that did the trick. One question what is this olist null
statement ? And thanks again Brian you are the man :)
Mike F.
n=100(100), mroute olist null.
*Mar 3 04:28:43.886: IP(0): s=150.1.2.2 (Loopback0) d=226.26.26.26 id=21,
prot=1, len=100(100), mroute olist null.
*Mar 3 04:28:45.889: IP(0): s=150.1.2.2 (Loopback0) d=226.26.26.26 id=22,
prot=1, len=100(100), mroute olist null.
*Mar 3 04:28:47.893: IP(0): s=150.1.2.2 (Loopback0) d=226.26.26.26 id=23,
prot=1, len=100(100), mroute olist null.
Rack1R2#
R3 which is the RP can ping it fine
Rack1R3#ping 226.26.26.26
Type escape sequence to abort.
Sending 1, 100-byte ICMP Echos to 226.26.26.26, timeout is 2 seconds:
Reply to request 0 from 183.1.0.5, 60 ms
Rack1R3#
Debug IP mpacket on R3 whith R2 pinging the address shows the same
Olist noll command.
*Mar 3 04:22:07.757: IP(0): s=183.1.123.2 (Serial0/0) d=226.26.26.26 id=30,
prot=1, len=104(100), mroute olist null
Rack1R3#
*Mar 3 04:22:09.760: IP(0): s=183.1.123.2 (Serial0/0) d=226.26.26.26 id=31,
prot=1, len=104(100), mroute olist null
Rack1R3#
*Mar 3 04:22:11.763: IP(0): s=183.1.123.2 (Serial0/0) d=226.26.26.26 id=32,
prot=1, len=104(100), mroute olist null
Rack1R3#
** Debug IP Mpacket shows RPF failure and an olist null
*Mar 1 14:35:53.694: IP(0): s=183.1.123.2 (Serial0/0) d=224.0.1.40
id=35737, prot=17, len=52(48), not RPF interface
Rack1R5#
*Mar 1 14:36:33.170: IP(0): s=150.1.3.3 (Serial0/0) d=224.0.1.39 id=43851,
prot=17, len=52(48), mroute olist null
Rack1R5#
Rack1R5#sh ip route 183.1.123.2
Routing entry for 183.1.123.0/24
Known via "eigrp 100", distance 90, metric 2221312, type internal
Redistributing via eigrp 100, ospf 1
Advertised by ospf 1 subnets
Last update from 183.1.58.8 on Ethernet0/0, 14:36:59 ago
Routing Descriptor Blocks:
* 183.1.58.8, from 183.1.58.8, 14:36:59 ago, via Ethernet0/0
Route metric is 2221312, traffic share count is 1
Total delay is 22010 microseconds, minimum bandwidth is 1544 Kbit
Reliability 255/255, minimum MTU 1500 bytes
Loading 1/255, Hops 3
Rack1R5#
Rack1R5(config)#ip mroute 183.1.123.0 255.255.255.0 183.1.0.5
Rack1R5(config)#end
Rack1R5#
*Mar 1 14:39:38.266: %SYS-5-CONFIG_I: Configured from console by console
Rack1R5#
** After adding the mroute :)
Reply to request 2 from 183.1.0.5, 88 ms
Reply to request 2 from 183.1.0.5, 128 ms
Reply to request 4 from 183.1.0.5, 88 ms
Reply to request 4 from 183.1.0.5, 128 ms
Reply to request 5 from 183.1.0.5, 89 ms
Reply to request 5 from 183.1.0.5, 129 ms
Rack1R2#
On 10/12/04 3:00 PM, "Brian McGahan" <bmcgahan@internetworkexpert.com>
wrote:
> Did you check the RP assignments? Remember that the auto-rp
> groups 224.0.1.39 and 224.0.1.40 are also subject to the RPF check. To
> trace the packet on a hop by hop basis, issue the "debug ip mpacket"
> command. Then disable multicast fast switching by issuing the "no ip
> mroute-cache" command on the interfaces running PIM. You should see
> whether the packet is forwarded (mforward), dropped (olist null), or has
> rpf failure (not rpf interface).
>
>
> HTH,
>
> Brian McGahan, CCIE #8593
> bmcgahan@internetworkexpert.com
>
> Internetwork Expert, Inc.
> http://www.InternetworkExpert.com
> Toll Free: 877-224-8987 x 705
> Outside US: 775-826-4344 x 705
> 24/7 Support: http://forum.internetworkexpert.com
> Live Chat: http://www.internetworkexpert.com/chat/
>
>
>> -----Original Message-----
>> From: nobody@groupstudy.com [mailto:nobody@groupstudy.com] On Behalf
> Of
>> Mike Flanagan
>> Sent: Tuesday, October 12, 2004 1:14 PM
>> To: ccielab@groupstudy.com
>> Subject: IE Task 7.6 - 7.7 Multicast RPF not working
>>
>> I am having a problem getting this task working. When a traceroute
>> From R2 to R5 using the loopback and ethernet addresses it takes the
> path
>> from R2 -> R1 -> SW1 -> SW2 -> R5. When I traceroute from R5 to R2 I
> take
>> the path R5 -> SW2 -> SW1 -> R1 -> R2 so I am not seeing an RPF issue.
> I
>> still cannot ping from R2 to R5 using the address 226.26.26.26 and I
> even
>> Added the static mroute's on R2 with no luck. Can someone please look
> at
>> my
>> Config and tell me what I am missing ?
>>
>>
>> Thanks in advance,
>>
>> Mike F.
>>
>> R2
>>
>> !
>> interface Loopback0
>> ip address 150.1.2.2 255.255.255.0
>> ip pim sparse-dense-mode
>> !
>> interface Ethernet0/0
>> ip address 183.1.2.2 255.255.255.0
>> ip pim sparse-dense-mode
>> half-duplex
>>
>> !
>> ip pim send-rp-discovery scope 16
>>
>>
>>
>> R2
>>
>> Rack1R2#traceroute 183.1.58.5
>>
>> Type escape sequence to abort.
>> Tracing the route to 183.1.58.5
>>
>> 1 183.1.123.1 28 msec 28 msec 28 msec
>> 2 183.1.17.7 32 msec 28 msec 28 msec
>> 3 183.1.78.8 28 msec 28 msec 28 msec
>> 4 183.1.58.5 28 msec * 28 msec
>> Rack1R2#trace 150.1.5.5
>>
>> Type escape sequence to abort.
>> Tracing the route to 150.1.5.5
>>
>> 1 183.1.123.1 28 msec 28 msec 28 msec
>> 2 183.1.17.7 32 msec 28 msec 29 msec
>> 3 183.1.78.8 28 msec 28 msec 28 msec
>> 4 183.1.58.5 28 msec * 28 msec
>> Rack1R2#trace 226.26.26.26
>>
>> Type escape sequence to abort.
>> Tracing the route to 226.26.26.26
>>
>> 1 * * *
>> 2 * * *
>> 3 * * *
>>
>> Rack1R2#ping 226.26.26.26
>>
>> Type escape sequence to abort.
>> Sending 1, 100-byte ICMP Echos to 226.26.26.26, timeout is 2 seconds:
>> .
>> Rack1R2#ping 226.26.26.26 source 183.1.2.2
>>
>> Type escape sequence to abort.
>> Sending 1, 100-byte ICMP Echos to 226.26.26.26, timeout is 2 seconds:
>> Packet sent with a source address of 183.1.2.2
>> .
>> Rack1R2#
>>
>> R5
>>
>> interface Ethernet0/0
>> ip address 183.1.58.5 255.255.255.0
>> ip pim sparse-dense-mode
>> ip igmp join-group 226.26.26.26
>> half-duplex
>> !
>> interface Serial0/0
>> ip address 183.1.0.5 255.255.255.0
>> ip pim sparse-dense-mode
>> encapsulation frame-relay
>> ip ospf network broadcast
>> frame-relay map ip 183.1.0.3 513 broadcast
>> frame-relay map ip 183.1.0.4 504 broadcast
>> no frame-relay inverse-arp
>>
>>
>> !
>> ip mroute 183.1.2.0 255.255.255.0 183.1.0.3
>> ip mroute 150.1.2.2 255.255.255.255 183.1.0.3
>>
>> Rack1R5#trace 183.1.2.2
>>
>> Type escape sequence to abort.
>> Tracing the route to 183.1.2.2
>>
>> 1 183.1.58.8 0 msec 4 msec 4 msec
>> 2 183.1.78.7 0 msec 4 msec 0 msec
>> 3 183.1.17.1 0 msec 4 msec 4 msec
>> 4 183.1.123.2 28 msec * 28 msec
>> Rack1R5#trace 150.1.2.2
>>
>> Type escape sequence to abort.
>> Tracing the route to 150.1.2.2
>>
>> 1 183.1.58.8 4 msec 0 msec 0 msec
>> 2 183.1.78.7 4 msec 0 msec 4 msec
>> 3 183.1.17.1 4 msec 4 msec 4 msec
>> 4 183.1.123.2 28 msec * 28 msec
>> Rack1R5#
>>
>>
> _______________________________________________________________________
>> Subscription information may be found at:
>> http://www.groupstudy.com/list/CCIELab.html
This archive was generated by hypermail 2.1.4 : Sat Nov 06 2004 - 17:11:47 GMT-3