"debug ip bgp" (no additional arguments) will give you the most information
about negotiation progress and errors. If you have access to the other
side and it's Cisco, "debug ip bgp updates" on that side will give some
clues about what what's going on at the time the error messages are
triggered on your side.
George
> From cisco-nsp-request@puck.nether.net Fri Oct 20 13:20:14 2000
> Resent-Date: Fri, 20 Oct 2000 13:16:49 -0400
> Received-Date: Fri, 20 Oct 2000 13:14:58 -0400
> Date: Fri, 20 Oct 2000 13:07:22 -0400
> From: Martin Picard <mpicard@sinc.ca>
> Subject: Re: Bad attribute
> To: cisco-nsp@puck.nether.net
> Resent-From: cisco-nsp@puck.nether.net
> X-Mailing-List: <cisco-nsp@puck.nether.net> archive/latest/4114
> X-Loop: cisco-nsp@puck.nether.net
> Precedence: list
> Resent-Sender: cisco-nsp-request@puck.nether.net
>
> 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
> >
> >
> >
>
>
This archive was generated by hypermail 2b29 : Sun Aug 04 2002 - 04:12:19 EDT