Re: multicast: bidirectional pim issue

Oh the joys of dynamips : ) But hey man if not for dynamips you might
not have dug this deep into the protocols and learned the
troubleshooting as well ; )

On 3/8/12, ccie99999 <ccie99999_at_googlemail.com> wrote:
> Joe,
>
> with real equipment it works!
>
> thanks for your help, really appreciate it!
>
>
> On Thu, Mar 8, 2012 at 6:47 AM, Joe Astorino
> <joeastorino1982_at_gmail.com>wrote:
>
>> I would try it on some real equipment. With PIM bi-dir each segment
>> elects a DF which is basically the device closest to the RP. So, the
>> SW2 interface being DF was not an issue here. It seems to look good.
>>
>>
>>
>> On Thu, Mar 8, 2012 at 12:39 AM, ccie99999 <ccie99999_at_googlemail.com>
>> wrote:
>> > adding this info:
>> >
>> > I did a debug ip mpacket fastswitching 238.1.1.1 everywhere..:
>> R1,R2,R3,SW2
>> > and the I did ping the 238.1.1.1 from *SW2 and I see this:
>> > *
>> > SW2#ping 238.1.1.1
>> >
>> > Type escape sequence to abort.
>> > Sending 1, 100-byte ICMP Echos to 238.1.1.1, timeout is 2 seconds:
>> > .
>> >
>> > *on R3, the RP: *
>> >
>> > R3#
>> > *Mar 1 00:43:21.891: FS(0): Receive s=155.1.58.8 d=238.1.1.1 id=42
>> prot=1
>> > size=114(100) ttl=254 from FastEthernet0/0
>> > *Mar 1 00:43:21.895: FS(0): Forward s=155.1.58.8 d=238.1.1.1 id=42
>> prot=1
>> > size=104(100) ttl=254 to Serial0/0
>> >
>> > (entering from fa0/0, the one that goes to svi vlan58 on the switch and
>> > exiting on the serial, the one that goes to R1 and R2)
>> >
>> > *on R1 and R2: *
>> > simply nothing
>> >
>> > looks like the packet are reaching the BSR RP, they are able to exit and
>> > then they are lost.
>> >
>> > I've also tried to get away from the pim bidirection mode and I set up
>> the
>> > R3 as regular BSR RP:
>> >
>> > R3#conf t
>> > Enter configuration commands, one per line. End with CNTL/Z.
>> > R3(config)#no ip pim rp-candidate Loopback0 bidir
>> > R3(config)#ip pim rp-candidate Loopback0
>> > R3(config)#
>> >
>> > I did a clear ip mroute * everywhere and did a ping again from SW2 and
>> this
>> > time is working:
>> >
>> > *SW2#ping 238.1.1.1 *
>> >
>> > Type escape sequence to abort.
>> > Sending 1, 100-byte ICMP Echos to 238.1.1.1, timeout is 2 seconds:
>> >
>> > Reply to request 0 from 155.1.146.6, 320 ms
>> >
>> > *R3#*
>> > *Mar 1 00:51:26.071: FS(0): Receive s=155.1.58.8 d=238.1.1.1 id=47
>> prot=1
>> > size=114(100) ttl=254 from FastEthernet0/0 ... punt to create state
>> >
>> > *R1#*
>> > *Mar 1 00:51:16.371: FS(0): Receive s=155.1.58.8 d=238.1.1.1 id=47
>> prot=1
>> > size=104(100) ttl=253 from Serial0/0.1 ... punt to create state
>> >
>> > *R2#*
>> > *Mar 1 00:51:25.915: FS(0): Receive s=155.1.58.8 d=238.1.1.1 id=47
>> prot=1
>> > size=118(100) ttl=252 from FastEthernet0/0.146
>> >
>> > looks like an odd issue just on bidir pim on gns3?
>> >
>> > thanks
>> >
>> >
>> > Blogs and organic groups at http://www.ccie.net
>> >
>> > _______________________________________________________________________
>> > Subscription information may be found at:
>> > http://www.groupstudy.com/list/CCIELab.html
>> >
>> >
>> >
>> >
>> >
>> >
>> >
>>
>>
>>
>> --
>> Regards,
>>
>> Joe Astorino
>> CCIE #24347
>> http://astorinonetworks.com
>>
>> "He not busy being born is busy dying" - Dylan
>>
>
>
>
> --
> ccie99999
>
>
> Blogs and organic groups at http://www.ccie.net
>
> _______________________________________________________________________
> Subscription information may be found at:
> http://www.groupstudy.com/list/CCIELab.html
>
>
>
>
>
>
>
>

-- 
Sent from my mobile device
Regards,
Joe Astorino
CCIE #24347
http://astorinonetworks.com
"He not busy being born is busy dying" - Dylan
Blogs and organic groups at http://www.ccie.net