From: John Matus (jmatus@pacbell.net)
Date: Wed Aug 18 2004 - 21:46:47 GMT-3
what does it mean when you are getting rpf errors on connected interfaces??
the 13.3, 32.3, and 36.3 are all connected....i'm not quite sure how to
patch that up
*Mar 1 11:01:48.192: IP(0): s=172.16.13.3 (FastEthernet0/0.2) d=227.7.7.7
(FastEthernet0/1) id=175, prot=1, len=100(100), mforward
*Mar 1 11:01:48.196: IP(0): s=172.16.13.3 (FastEthernet0/1) d=227.7.7.7
id=175, prot=1, len=114(100), not RPF interface
*Mar 1 11:01:48.228: IP(0): s=172.16.32.3 (FastEthernet0/1) d=227.7.7.7
id=175, prot=1, len=114(100), not RPF interface
*Mar 1 11:01:48.248: IP(0): s=172.16.36.3 (FastEthernet0/1) d=227.7.7.7
id=175, prot=1, len=114(100), not RPF interface
John D. Matus
MCSE, CCNP
Office: 818-782-2061
Cell: 818-430-8372
jmatus@pacbell.net
----- Original Message -----
From: "John Matus" <jmatus@pacbell.net>
To: "John Matus" <jmatus@pacbell.net>; "lab" <ccielab@groupstudy.com>
Sent: Wednesday, August 18, 2004 5:37 PM
Subject: Re: rp trouble
> i added the static mroute for 172.16.120.1.....it should be routing
through
> e0/0 which is 172.16.23.2, but i'm getting the same darn error....
> (ip mroute 172.16.120.1 255.255.255.255 172.16.23.2)
>
>
> *Mar 1 02:11:27.475: IP(0): s=172.16.120.1 (Ethernet0/0) d=224.0.1.40
> id=3382, prot=17, len=62(48), mroute olist null
> *Mar 1 02:11:27.479: IP(0): s=172.16.120.1 (Ethernet0/0) d=224.0.1.40
> id=3383, prot=17, len=62(48), mroute olist null
> *Mar 1 02:11:27.495: IP(0): s=172.16.120.1 (Serial0/0.1) d=224.0.1.40
> id=3382, prot=17, len=52(48), not RPF interface
> *Mar 1 02:11:27.499: IP(0): s=172.16.120.1 (Serial0/0.1) d=224.0.1.40
> id=3383, prot=17, len=52(48), not RPF interface
>
>
>
>
> John D. Matus
> MCSE, CCNP
> Office: 818-782-2061
> Cell: 818-430-8372
> jmatus@pacbell.net
> ----- Original Message -----
> From: "John Matus" <jmatus@pacbell.net>
> To: "Richard Dumoulin" <richard.dumoulin@vanco.es>; "lab"
> <ccielab@groupstudy.com>
> Sent: Wednesday, August 18, 2004 5:24 PM
> Subject: Re: rp trouble
>
>
> > RE: rp troubleall set 'no ip mroute cache' and see what happens. debug
> does
> > not show rpf failures
> >
> >
> >
> > John D. Matus
> > MCSE, CCNP
> > Office: 818-782-2061
> > Cell: 818-430-8372
> > jmatus@pacbell.net
> > ----- Original Message -----
> > From: Richard Dumoulin
> > To: John Matus ; lab
> > Sent: Wednesday, August 18, 2004 5:21 PM
> > Subject: RE: rp trouble
> >
> >
> > Debug ip mpackets needs no ip moute-cache. Did you set this on the
> incoming
> > interfaces ?
> > I bet your 2 hops away routers are suffering from "rpf failures" when
> they
> > receive the discovery messages from the MA,
> >
> > --Richard
> >
> > -----Original Message-----
> > From: John Matus [mailto:jmatus@pacbell.net]
> > Sent: jueves, 19 de agosto de 2004 1:52
> > To: lab
> > Subject: rp trouble
> >
> >
> >
> > i'm trying to use auto-rp on this network. all addresses are
reachable,
> > however only the directly connected neighbors are regestering the
> rp....those
> > that are 2 hops away don't see it at all.. any ideas? debug ip mpacket
> shows
> > nothing. the rp is set with 'ip pim send-rp-ann lo0 scope 16' and ip
> > send-rp-disc lo0 scope 16
> >
> >
> >
> >
> >
> >
> > John D. Matus
> > MCSE, CCNP
> > Office: 818-782-2061
> > Cell: 818-430-8372
> > jmatus@pacbell.net
> >
> >
This archive was generated by hypermail 2.1.4 : Fri Sep 03 2004 - 07:02:45 GMT-3