From: Paul Dardinski (pauld@marshallcomm.com)
Date: Fri Aug 04 2006 - 22:07:54 ART
Victor,
I don't have your exact topology re: ip addr, but assuming you have a
static join on loop0 to 224.1.1.1. If this is the case and R2/R5 are
directly connected, when pinging from R2, it will first attempt to use
sparse mode assuming it has an RP for the group. AFAIK, if it doesn't,
then it will fall back to dense. You can kill this behavior with "no ip
dm fallback". Try entering this commo on R2 and see if you can still
ping.
-----Original Message-----
From: nobody@groupstudy.com [mailto:nobody@groupstudy.com] On Behalf Of
Victor Cappuccio
Sent: Friday, August 04, 2006 11:32 AM
To: ccielab@groupstudy.com
Subject: ip pim rp-add
Morning Guys,
Could anyone please explain this behavior?
Lo0-R5 ------ frame-relay ------- R2, running ip pim sparse.
And:
R2(config)#do clear ip mroute *
R2(config)#no ip pim rp-add 155.1.5.5 <---- REMOVING THE RP-ADDRESS
R2(config)#do show ip pim rp map
PIM Group-to-RP Mappings
R2(config)#do clear ip mroute *
R2(config)#do ping 224.1.1.1
Type escape sequence to abort.
Sending 1, 100-byte ICMP Echos to 224.1.1.1, timeout is 2 seconds:
Reply to request 0 from 150.1.25.5, 124 ms <-----Works :S
R2(config)#
R2(config)#
R2(config)#
R2(config)#ip pim rp-add 155.1.5.5
R2(config)#do show ip pim rp map
PIM Group-to-RP Mappings
Group(s): 224.0.0.0/4, Static
RP: 155.1.5.5 (?)
R2(config)#do ping 224.1.1.1
Type escape sequence to abort.
Sending 1, 100-byte ICMP Echos to 224.1.1.1, timeout is 2 seconds:
Reply to request 0 from 150.1.25.5, 68 ms <--- Also Works :S :S
R2(config)#
Thanks
Victor.--
This archive was generated by hypermail 2.1.4 : Fri Sep 01 2006 - 15:41:56 ART