hello,
R5#sh ip rpf 155.1.10.10
RPF information for ? (155.1.10.10)
  RPF interface: GigabitEthernet0/0
  RPF neighbor: ? (155.1.58.8)
  RPF route/mask: 155.1.10.0/24
  RPF type: unicast (eigrp 100)
  RPF recursion count: 0
  Doing distance-preferred lookups across tables
SW4#mtrace 155.1.10.10
Type escape sequence to abort.
Mtrace from 155.1.10.10 to 155.1.10.10 via RPF
From source (?) to destination (?)
Querying full reverse path...
 0  155.1.10.10
-1  155.1.10.10 PIM  [155.1.10.0/24]
-2  155.1.10.10
Here is the mtrace to the RP address:
SW4#mtrace 150.1.5.5
Type escape sequence to abort.
Mtrace from 150.1.5.5 to 155.1.108.10 via RPF
From source (?) to destination (?)
Querying full reverse path...
 0  155.1.108.10
-1  155.1.108.10 PIM  [150.1.5.0/24]
-2  155.1.108.8 PIM  [150.1.5.0/24]
-3  155.1.58.5 PIM  [150.1.5.0/24]
-4  150.1.5.5
On Wed, Jun 9, 2010 at 8:05 PM, Tyson Scott <tscott_at_ipexpert.com> wrote:
> what is the output of show ip rpf 155.1.10.10
> what is the result of mtrace 155.1.10.10 from SW4
>
> Regards,
>
> Tyson Scott - CCIE #13513 R&S, Security, and SP
> Managing Partner / Sr. Instructor - IPexpert, Inc.
> Mailto: tscott_at_ipexpert.com
>
>
>
> -----Original Message-----
> From: nobody_at_groupstudy.com [mailto:nobody_at_groupstudy.com] On Behalf Of
> Tom
> Kacprzynski
> Sent: Wednesday, June 09, 2010 7:16 PM
> To: Hector Gonzalez
> Cc: Joe Astorino; ccielab_at_groupstudy.com
> Subject: Re: PIM BiDir Problem
>
> Yes,
> This is what I have configured:
>
> interface Vlan10
>  ip address 155.1.10.10 255.255.255.0
>  ip pim sparse-mode
>  ip igmp join-group 238.1.1.1
>  ip igmp join-group 238.10.10.10
>  no ip mroute-cache
>
>
>
> On Wed, Jun 9, 2010 at 6:14 PM, Hector Gonzalez
> <hector.gonzalezf_at_gmail.com>wrote:
>
> > Do you have
> >
> > ip igmp join-group 238.10.10.10 and ip pim sparse-mode on the interface
> you
> >  are expecting to answer the ping
> >
> >
> > On Wed, Jun 9, 2010 at 6:03 PM, Tom Kacprzynski <tom.kac_at_gmail.com>
> wrote:
> >
> >> Joe,
> >> SW4 was the DR, changed it to SW2 but still no luck, pings are still
> >> timing
> >> out.
> >>
> >> SW4#sh ip pim int
> >>
> >> Address          Interface                Ver/   Nbr    Query  DR     DR
> >>                                          Mode   Count  Intvl  Prior
> >> 150.1.10.10      Loopback0                v2/S   0      30     1
> >> 150.1.10.10
> >> *155.1.108.10     Port-channel1            v2/S   1      30     1
> >> 155.1.108.8*
> >> 155.1.10.10      Vlan10                   v2/S   0      30     1
> >> 155.1.10.10
> >>
> >>
> >>
> >>
> >>
> >> On Wed, Jun 9, 2010 at 5:49 PM, Joe Astorino <joe_astorino_at_comcast.net
> >> >wrote:
> >>
> >> > Try making sure that SW4 is NOT the DR on the SW2/SW4 segment and try
> >> > again.  I have seen some interesting things happen that way.
> >> >
> >> > Regards,
> >> > Joe Astorino, CCIE #24347
> >> >
> >> > "He not busy being born is busy dying" -- Dylan
> >> >
> >> >
> >> > ----- Original Message -----
> >> > From: "Tom Kacprzynski" <tom.kac_at_gmail.com>
> >> > To: ccielab_at_groupstudy.com
> >> > Sent: Wednesday, June 9, 2010 6:43:15 PM GMT -05:00 US/Canada Eastern
> >> > Subject: PIM BiDir Problem
> >> >
> >> > Hello,
> >> > I'm working on a PIM bidirectional lab and looks like i'm stuck :( I
> >> hope
> >> > some here can help me out.
> >> >
> >> > The shared tree looks pretty good but no traffic response from pings.
> >> Here
> >> > are the details
> >> >
> >> > R5 (RP) (Source) ---> SW2 -------------> SW4 ---| (238.10.10.10
> >> receiver)
> >> >           Gi0/0  |----| Vlan58, Po1|-------|Po1 ,  Vlan10
> >> >
> >> >
> >> > The mroute tables:
> >> >
> >> > This is the RP and source
> >> > R5#sh ip mroute 238.10.10.10 | b \(
> >> > (*, 238.10.10.10), 00:06:45/00:02:30, RP *150.1.5.5*, flags: B
> >> >   Bidir-Upstream: Null, RPF nbr 0.0.0.0
> >> >   Outgoing interface list:
> >> >     *GigabitEthernet0/0*, Forward/Sparse, 00:05:59/00:02:30
> >> >
> >> > This is the intermediate router.
> >> > SW2#sh ip mroute 238.10.10.10 | b \(
> >> > (*, 238.10.10.10), 00:07:03/00:03:23, RP 150.1.5.5, flags: B
> >> >   Bidir-Upstream: Vlan58, RPF nbr 155.1.58.5
> >> >   Outgoing interface list:
> >> >     Port-channel1, Forward/Sparse, 00:07:03/00:03:23
> >> >     Vlan58, *Bidir-Upstream*/Sparse, 00:07:03/00:00:00
> >> >
> >> > The receiver.
> >> > SW4#sh ip mroute 238.10.10.10 | b \(
> >> > (*, 238.10.10.10), 00:07:03/00:02:51, RP 150.1.5.5, flags: BCL
> >> >   Bidir-Upstream: Port-channel1, RPF nbr 155.1.108.8
> >> >   Outgoing interface list:
> >> >     Vlan10, Forward/Sparse, 00:07:03/00:02:51
> >> >     Port-channel1,* Bidir-Upstream*/Sparse, 00:07:03/00:00:00
> >> >
> >> > *This is what I've tried so far:*
> >> > 1. Verified all devices have bootstrap mappings and the group is set
> for
> >> > bidirectional mode.
> >> > 2. "debug ip mpacket 238.10.10.10" on SW2 and SW4. RESULT: I see
> packets
> >> > destined to the correct group leaving R5 (the source) SW2 gets them.
> SW4
> >> on
> >> > the other hand never gets these packets in the debugs ( I disabled
> >> > mroute-cache on all interface just to be sure).
> >> > 3. check to make sure all of them are ip pim neighbors running
> >> > sparse/bidirectional mode.
> >> > 4. Reloaded all devices.
> >> >
> >> >
> >> > I'm really out of ideas, if anyone has any suggestions please help.
> >> >
> >> > Thank you.
> >> >
> >> >
> >> > Blogs and organic groups at http://www.ccie.net
> >> >
> >> >
> _______________________________________________________________________
> >> > Subscription information may be found at:
> >> > http://www.groupstudy.com/list/CCIELab.html
> >>
> >>
> >> Blogs and organic groups at http://www.ccie.net
> >>
> >> _______________________________________________________________________
> >> Subscription information may be found at:
> >> http://www.groupstudy.com/list/CCIELab.html
>
>
> Blogs and organic groups at http://www.ccie.net
>
> _______________________________________________________________________
> Subscription information may be found at:
> http://www.groupstudy.com/list/CCIELab.html
Blogs and organic groups at http://www.ccie.net
Received on Wed Jun 09 2010 - 20:29:53 ART
This archive was generated by hypermail 2.2.0 : Sun Aug 01 2010 - 09:11:37 ART