Someone may be sending you an invalid or unreachable next-hop
to cause this. I've seen cases where if you have a peer-group
configured (this was in 11.1CC), and the peer-group is for ebgp sessions
not out the same interface, some equipment will ignore the route
if it gets the next-hop of one of the other serial interfaces.
Check that they have next-hop-self and that you are not part of
an ebgp peer group that talks to multiple providers, that may be able to
get rid of the problem (if that's the issue).
- jared
On Fri, Oct 20, 2000 at 01:07:22PM -0400, Martin Picard wrote:
> One more try at this ???
>
> Even though the BGP session stays up and
> seems healthy, I keep getting these messages.
>
> Are they only really an indication of an error
> or just a cosmetic bug ???
>
> tx
> martin
>
> ----- Message d'origine -----
> De : "Martin Picard" <mpicard@sinc.ca>
> À : <cisco-nsp@puck.nether.net>
> Envoyé : 19 septembre, 2000 15:06
> Objet : BGP: Bad attribute
>
>
> > Can anybody indicate how I can find the culprit attribute
> > that causes these messages to be issued ?
> >
> > 3d05h: BGP: 10.247.144.2 Bad attributes
> > 4d02h: BGP: 10.247.144.2 Bad attributes
> >
> > tx
> > Martin
> >
> >
> >
-- Jared Mauch | pgp key available via finger from jared@puck.nether.net clue++; | http://puck.nether.net/~jared/ My statements are only mine. END OF LINE | Manager of IP networks built within my own home
This archive was generated by hypermail 2b29 : Sun Aug 04 2002 - 04:12:19 EDT