From: Marvin Greenlee (marvingreenlee@yahoo.com)
Date: Mon Oct 08 2007 - 01:36:02 ART
If it happened when you were adding a password to an
existing BGP peering, it is possible that one side
initated a new connection, and had a second session.
Clearing the TCB for the second session will stop the
error message.
"Show tcp brief" will show you TCP sessions. If you
have two sessions, you can clear the second session
with 'clear tcp tcb xxxx'.
Reloading the routers would also "magically" fix it,
as it would clear the TCP sessions.
Marvin Greenlee, CCIE #12237 (R&S, SP, Sec)
Senior Technical Instructor - IPexpert, Inc.
A Cisco Learning Partner - We Accept Learning Credits!
Telephone: +1.810.326.1444
Fax: +1.810.454.0130
Mailto: mgreenlee@ipexpert.com
--- Grace Simon <SimonG@pcsystems.gr> wrote:
> Yep, I aggree, seems that it needs a reload to solve
> it.
>
> Cheers,
>
> Simon
>
> -----Original Message-----
> From: Sadiq Yakasai [mailto:sadiqtanko@gmail.com]
> Sent: Sunday, October 07, 2007 6:21 PM
> To: Nicky
> Cc: Jason Guy (jguy); Grace Simon;
> ccielab@groupstudy.com
> Subject: Re: BGP MD5 Error Message
>
> Actually, when it happend to me yesterday, I did all
> that...
>
> It wasnt a space on the password string i had. I
> took off the
> password, and re-enabled it,....- all in vein!
>
> I reloaded me routers, all went fine! One of those
> things I would
> think...
>
>
This archive was generated by hypermail 2.1.4 : Fri Nov 16 2007 - 13:11:12 ART