From: Brian McGahan (bmcgahan@internetworkexpert.com)
Date: Tue Oct 12 2004 - 16:00:44 GMT-3
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#
>
>
This archive was generated by hypermail 2.1.4 : Sat Nov 06 2004 - 17:11:46 GMT-3