From: ISolveSystems (support@isolvesystems.com)
Date: Tue Aug 07 2007 - 15:23:31 ART
Problem solved. It was the RPF failure on R1 to the mapping agent R3.
Thanks.
On 8/7/07, ISolveSystems <support@isolvesystems.com> wrote:
>
> Looks like there's RPF failure on R1. Am I right? How do I resolve?
>
>
> Rack1R1(config)#do sh ip mroute count
> IP Multicast Statistics
> 6 routes using 4320 bytes of memory
> 3 groups, 1.00 average sources per group
> Forwarding Counts: Pkt Count/Pkts per second/Avg Pkt Size/Kilobits per
> second
> Other counts: Total/RPF failed/Other drops(OIF-null, rate-limit etc)
>
> Group: 239.254.2.5, Source count: 0, Packets forwarded: 0, Packets
> received: 0
>
> Group: 224.0.1.39, Source count: 2, Packets forwarded: 0, Packets
> received: 2
> Source: 150.1.1.1/32, Forwarding: 0/0/0/0, Other: 0/0/0
> Source: 150.1.2.2/32, Forwarding: 0/0/0/0, Other: 2/2/0
>
> Group: 224.0.1.40, Source count: 1, Packets forwarded: 0, Packets
> received: 1
> Source: 150.1.3.3/32, Forwarding: 0/0/0/0, Other: 1/1/0
> Rack1R1(config)#do sh ip mroute
> IP Multicast Routing Table
> Flags: D - Dense, S - Sparse, B - Bidir Group, s - SSM Group, C -
> Connected,
> L - Local, P - Pruned, R - RP-bit set, F - Register flag,
> T - SPT-bit set, J - Join SPT, M - MSDP created entry,
> X - Proxy Join Timer Running, A - Candidate for MSDP Advertisement,
> U - URD, I - Received Source Specific Host Report,
> Z - Multicast Tunnel, z - MDT-data group sender,
> Y - Joined MDT-data group, y - Sending to MDT-data group
> Outgoing interface flags: H - Hardware switched, A - Assert winner
> Timers: Uptime/Expires
> Interface state: Interface, Next-Hop or VCD, State/Mode
>
> (*, 239.254.2.5), 02:45:35/stopped, RP 0.0.0.0, flags: DCL
> Incoming interface: Null, RPF nbr 0.0.0.0
> Outgoing interface list:
> Serial0/0/0, Forward/Sparse-Dense, 02:45:35/00:00:00
> Serial0/1/0, Forward/Sparse-Dense, 02:45:35/00:00:00
>
> (*, 224.0.1.39), 04:13:08/stopped, RP 0.0.0.0, flags: D
> Incoming interface: Null, RPF nbr 0.0.0.0
> Outgoing interface list:
> Serial0/0/0, Forward/Sparse-Dense, 03:31:21/00:00:00
> Serial0/1/0, Forward/Sparse-Dense, 04:13:09/00:00:00
>
> (150.1.1.1, 224.0.1.39), 03:47:43/00:02:39, flags: T
> Incoming interface: Loopback0, RPF nbr 0.0.0.0
> Outgoing interface list:
> Serial0/0/0, Prune/Sparse-Dense, 02:00:51/00:01:38
> Serial0/1/0, Forward/Sparse-Dense, 03:47:43/00:00:00
>
> (150.1.2.2, 224.0.1.39), 00:02:20/00:00:39, flags:
> Incoming interface: Null, RPF nbr 174.1.31.9
> Outgoing interface list:
> Serial0/1/0, Forward/Sparse-Dense, 00:02:20/00:00:00
> Serial0/0/0, Forward/Sparse-Dense, 00:02:20/00:00:00
>
> (*, 224.0.1.40), 04:25:49/stopped, RP 0.0.0.0, flags: DCL
> Incoming interface: Null, RPF nbr 0.0.0.0
> Outgoing interface list:
> Serial0/0/0, Forward/Sparse-Dense, 03:31:46/00:00:00
> Serial0/1/0, Forward/Sparse-Dense, 04:24:32/00:00:00
> FastEthernet0/0.1001, Forward/Sparse-Dense, 04:25:49/00:00:00
>
> (150.1.3.3, 224.0.1.40), 00:01:41/00:01:18, flags: L
> Incoming interface: Null, RPF nbr 174.1.31.9
> Outgoing interface list:
> FastEthernet0/0.1001, Forward/Sparse-Dense, 00:01:41/00:00:00
> Serial0/1/0, Forward/Sparse-Dense, 00:01:41/00:00:00
> Serial0/0/0, Forward/Sparse-Dense, 00:01:41/00:00:00
>
>
>
> On 8/7/07, ISolveSystems <support@isolvesystems.com> wrote:
> >
> > Below is the sh ip mroute and count output from R4. I dont' see any RPF
> > failed, do you?
> >
> >
> >
> > Rack1R4#sh ip mroute
> > IP Multicast Routing Table
> > Flags: D - Dense, S - Sparse, B - Bidir Group, s - SSM Group, C -
> > Connected,
> > L - Local, P - Pruned, R - RP-bit set, F - Register flag,
> > T - SPT-bit set, J - Join SPT, M - MSDP created entry,
> > X - Proxy Join Timer Running, A - Candidate for MSDP
> > Advertisement,
> > U - URD, I - Received Source Specific Host Report,
> > Z - Multicast Tunnel, z - MDT-data group sender,
> > Y - Joined MDT-data group, y - Sending to MDT-data group
> > Outgoing interface flags: H - Hardware switched, A - Assert winner
> > Timers: Uptime/Expires
> > Interface state: Interface, Next-Hop or VCD, State/Mode
> >
> > (*, 224.0.1.39), 01:18:29/stopped, RP 0.0.0.0, flags: D
> > Incoming interface: Null, RPF nbr 0.0.0.0
> > Outgoing interface list:
> > Serial0/0/0, Forward/Sparse-Dense, 01:18:29/00:00:00
> >
> > (150.1.1.1, 224.0.1.39 ), 00:02:05/00:00:54, flags: PT
> > Incoming interface: Serial0/0/0, RPF nbr 174.1.145.1
> > Outgoing interface list: Null
> >
> > (*, 224.0.1.40), 01:18:48/00:02:51, RP 0.0.0.0, flags: DCL
> > Incoming interface: Null, RPF nbr 0.0.0.0
> > Outgoing interface list:
> > Serial0/0/0, Forward/Sparse-Dense, 01:18:50/00:00:00
> > FastEthernet0/0, Forward/Sparse-Dense, 01:18:50/00:00:00
> >
> > Rack1R4#sh ip mroute count
> > IP Multicast Statistics
> > 3 routes using 1654 bytes of memory
> > 2 groups, 0.50 average sources per group
> > Forwarding Counts: Pkt Count/Pkts per second/Avg Pkt Size/Kilobits per
> > second
> > Other counts: Total/RPF failed/Other drops(OIF-null, rate-limit etc)
> >
> > Group: 224.0.1.39, Source count: 1, Packets forwarded: 0, Packets
> > received: 6
> > Source: 150.1.1.1/32, Forwarding: 0/0/0/0, Other: 6/0/6
> >
> > Group: 224.0.1.40, Source count: 0, Packets forwarded: 0, Packets
> > received: 0
> > Rack1R4#
> >
> >
> >
> > On 8/7/07, Mike Harrison <michael.h4@blueyonder.co.uk > wrote:
> > >
> > > Have you checked there isnt a RPF fail ???
> > >
> > > Just a thought
> > >
> > > Mike
> > >
> > > ----- Original Message -----
> > > From: "ISolveSystems" <support@isolvesystems.com>
> > > To: "Serhat Aslan" < serhatworks@gmail.com>
> > > Cc: "Salau, Yemi" < yemi.salau@siemens.com>; "Group study"
> > > <ccielab@groupstudy.com>
> > > Sent: Tuesday, August 07, 2007 6:18 PM
> > > Subject: Re: RP mapping info not received
> > >
> > >
> > > > Yes, I can ping from R4/R5 to Lo0 of R1 and R3.
> > > >
> > > > *R1*
> > > >
> > > > Rack1R1(config-pmap-c)#do sh run int s0/0/0
> > > > Building configuration...
> > > >
> > > > Current configuration : 583 bytes
> > > > !
> > > > interface Serial0/0/0
> > > > ip address 174.1.145.1 255.255.255.0
> > > > ip pim nbma-mode
> > > > ip pim sparse-dense-mode
> > > > encapsulation frame-relay
> > > > delay 10
> > > > ipv6 address 2001:CC1E:1:1515::1/64
> > > > ipv6 ospf neighbor FE80::215:FAFF:FED7:6B68
> > > > ipv6 ospf 1 area 0
> > > > no fair-queue
> > > > frame-relay class FRTS
> > > > frame-relay traffic-shaping
> > > > frame-relay map ip 174.1.145.4 104 broadcast
> > > > frame-relay map ip 174.1.145.5 105 broadcast
> > > > frame-relay map ipv6 FE80::215:FAFF:FED7:6B68 105 broadcast
> > > > frame-relay map ipv6 2001:CC1E:1:1515::5 105 broadcast
> > > > no frame-relay inverse-arp
> > > > frame-relay lmi-type cisco
> > > > end
> > > >
> > > > *R3*
> > > >
> > > > interface Serial0/2/0
> > > > ip address 174.1.13.3 255.255.255.0
> > > > ip pim sparse-dense-mode
> > > > service-policy output AUDIO
> > > > end
> > > >
> > > > *R4*
> > > > interface Serial0/0/0
> > > > bandwidth 100000
> > > > ip address 174.1.145.4 255.255.255.0
> > > > ip pim dr-priority 0
> > > > ip pim sparse-dense-mode
> > > > encapsulation frame-relay
> > > > delay 1
> > > > no fair-queue
> > > > frame-relay class FRTS
> > > > frame-relay traffic-shaping
> > > > frame-relay map ip 174.1.145.1 401 broadcast
> > > > frame-relay map ip 174.1.145.5 401
> > > > no frame-relay inverse-arp
> > > > frame-relay lmi-type cisco
> > > >
> > > > *R5*
> > > >
> > > > interface Serial0/0/0
> > > > bandwidth 1000000
> > > > ip address 174.1.145.5 255.255.255.0
> > > > ip pim dr-priority 0
> > > > ip pim sparse-dense-mode
> > > > encapsulation frame-relay
> > > > ipv6 address 2001:CC1E:1:1515::5/64
> > > > ipv6 ospf priority 0
> > > > ipv6 ospf 1 area 0
> > > > no fair-queue
> > > > frame-relay class FRTS
> > > > frame-relay traffic-shaping
> > > > frame-relay map ip 174.1.145.1 501 broadcast
> > > > frame-relay map ip 174.1.145.4 501
> > > > frame-relay map ipv6 FE80::217:EFF:FEAF:8738 501 broadcast
> > > > frame-relay map ipv6 2001:CC1E:1:1515::1 501 broadcast
> > > > no frame-relay inverse-arp
> > > > frame-relay lmi-type cisco
> > > > end
> > > >
> > > >
> > > > On 8/7/07, Serhat Aslan < serhatworks@gmail.com> wrote:
> > > >>
> > > >> Those are the not configs that I wanted, I mean
> > > the running-config. If
> > > >> you can ping ->from serial interface of R4-R5 to loopback of
> > > routers, and
> > > >> if
> > > >> there is no error the separation and mapping with access-lists on
> > > both
> > > >> RP(s) and agent configuration, the system must work. It is very
> > > straight
> > > >> forward configuration.
> > > >>
> > > >> Serhat Aslan
> > > >>
> > > >>
> > > >> On 8/7/07, ISolveSystems < support@isolvesystems.com > wrote:
> > > >> >
> > > >> > Below shows R4 R5 pim enabled interfaces and neighbours. What
> > > other
> > > >> > config do you want?
> > > >> >
> > > >> > *R4*
> > > >> >
> > > >> > Rack1R4#sh ip pim int
> > > >> >
> > > >> > Address Interface Ver/ Nbr Query DR
> > > >> > DR
> > > >> > Mode
> > > Count Intvl Prior
> > > >> > 174.1.4.4 FastEthernet0/0 v2/SD 0 30 1
> > > >> > 174.1.4.4
> > > >> > 174.1.145.4 Serial0/0/0 v2/SD 2 30
> > > 0
> > > >> > 174.1.145.1
> > > >> >
> > > >> > Rack1R4(config)#do sh ip pim nei
> > > >> > PIM Neighbor Table
> > > >> > Mode: B - Bidir Capable, DR - Designated Router, N - Default DR
> > > >> > Priority,
> > > >> > S - State Refresh Capable
> > > >> >
> > > Neighbor Interface Uptime/Expires Ver DR
> > > >> > Address
> > > >> > Prio/Mode
> > > >> > 174.1.145.1 Serial0/0/0 00:52:30/00:01:27
> > > v2 1 /
> > > >> > DR S
> > > >> > 174.1.145.5 Serial0/0/0 00:52:31/00:01:27
> > > v2 0 /
> > > >> > S
> > > >> >
> > > >> > *R5*
> > > >> >
> > > >> > Rack1R5#sh ip pim int
> > > >> >
> > > >> > Address Interface Ver/ Nbr Query DR
> > >
> > > >> > DR
> > > >> > Mode
> > > Count Intvl Prior
> > > >> > 174.1.145.5 Serial0/0/0 v2/SD 2 30 0
> > > >> > 174.1.145.1
> > > >> > 192.10.1.5 FastEthernet0/1.52 v2/SD 0 30 1
> > > >> > 192.10.1.5
> > > >> > Rack1R5#ping 150.1.1.1
> > > >> >
> > > >> >
> > > >> >
> > > >> >
> > > >> >
> > > >> > On 8/7/07, Serhat Aslan < serhatworks@gmail.com > wrote:
> > > >> > >
> > > >> > > Did you check the unicast reachability of rp/agent to clients
> > > and
> > > >> > > pim
> > > >> > > enable interfaces ? if you did can you send the config ?
> > > >> > >
> > > >> > >
> > > >> > > Serhat Aslan
> > > >> > >
> > > >> > >
> > > >> > > On 8/7/07, ISolveSystems < support@isolvesystems.com > wrote:
> > > >> > >
> > > >> > > > I have tried the nbmp mode with same result.
> > > >> > > >
> > > >> > > > I have the broadcase keyword...
> > > >> > > > frame-relay map ip 174.1.145.4 104 broadcast
> > > >> > > > frame-relay map ip 174.1.145.5 105 broadcast
> > > >> > > >
> > > >> > > >
> > > >> > > > On 8/7/07, Salau, Yemi < yemi.salau@siemens.com> wrote:
> > > >> > > > >
> > > >> > > > > 1. tried ip pim nbma-mode on R1's serial interface?
> > > >> > > > > 2. Sure the FR interfaces/dlcis are broadcast compatible?
> > > ie.
> > > >> > > > > Frame-relay map with broadcast keyword?
> > > >> > > > >
> > > >> > > > > -----Original Message-----
> > > >> > > > > From: nobody@groupstudy.com [mailto: nobody@groupstudy.com] On
> > > >> > > > Behalf Of
> > > >> > > > > ISolveSystems
> > > >> > > > > Sent: Tuesday, August 07, 2007 3:43 PM
> > > >> > > > > To: Group study
> > > >> > > > > Subject: RP mapping info not received
> > > >> > > > >
> > > >> > > > > Hello Expert,
> > > >> > > > > R1, R4, R5 are full meshed FR. R1 is the RP. R3 is the
> > > mapping
> > > >> > > > agent.
> > > >> > > > > All connected interfaces are configured with pim sparse
> > > dense
> > > >> > > > > mode
> > > >> > > > and
> > > >> > > > > are
> > > >> > > > > all neighbor up.
> > > >> > > > >
> > > >> > > > > For some reason R4 and R5 are not receiving rp mapping from
> > >
> > > >> > > > R3. Any
> > > >> > > > > idea?
> > > >> > > > >
> > > >> > > > > R4
> > > >> > > > > \
> > > >> > > > > \
> > > >> > > > > R1-----R3----R2
> > > >> > > > > /
> > > >> > > > > /
> > > >> > > > > R5
> > > >> > > > >
> > > >> > > > > Thanks.
> > > >> > > > >
> > > >> > > > >
> > > >> > > >
> > > _______________________________________________________________________
> > > >> > > > > Subscription information may be found at:
> > > >> > > > > http://www.groupstudy.com/list/CCIELab.html
> > > >> > > >
> > > >> > > >
> > > _______________________________________________________________________
> > > >> > > >
> > > >> > > > Subscription information may be found at:
> > > >> > > > http://www.groupstudy.com/list/CCIELab.html
> > > >
> > > >
> > > _______________________________________________________________________
> > > > Subscription information may be found at:
> > > > http://www.groupstudy.com/list/CCIELab.html
This archive was generated by hypermail 2.1.4 : Sat Sep 01 2007 - 11:32:09 ART