Ahhh, that's a good point! That made me take a second look at the
configuration. This behavior can be caused if you use aggressive
timers and the remote end is rejecting the session as a result.
Try removing " neighbor 10.255.0.10 timers 3 9" and see what happens.
-- Marko Milivojevic - CCIE #18427 Senior Technical Instructor - IPexpert FREE CCIE training: http://bit.ly/vLecture Mailto: markom_at_ipexpert.com Telephone: +1.810.326.1444 Web: http://www.ipexpert.com/ On Fri, Aug 5, 2011 at 19:47, Kenneth Ratliff <lists_at_cluebat.net> wrote: > On 08/05/2011 10:03 PM, Dave Serra wrote: >> 10.255.0.10 6/0 (cease) > > That's the important part, the 6/0. That means the remote neighbor is sending an error code 6, which is Cease. However, it's not sending a sub-code. The Cease Notification subcodes are handled by RFC 4486, but unfortunately, they're not mandatory parts of the BGP spec. > > > B 1 B B B B Maximum Number of Prefixes Reached > B B B B B 2 B B B B Administrative Shutdown > B B B B B 3 B B B B Peer De-configured > B B B B B 4 B B B B Administrative Reset > B B B B B 5 B B B B Connection Rejected > B B B B B 6 B B B B Other Configuration Change > B B B B B 7 B B B B Connection Collision Resolution > B B B B B 8 B B B B Out of Resources > > > Those are the subcodes, so one of those is likely the problem. Depending on what it is, the problem may be in the remote configuration, not on your end. > > > Blogs and organic groups at http://www.ccie.net > > _______________________________________________________________________ > Subscription information may be found at: > http://www.groupstudy.com/list/CCIELab.html Blogs and organic groups at http://www.ccie.netReceived on Fri Aug 05 2011 - 20:25:22 ART
This archive was generated by hypermail 2.2.0 : Thu Sep 01 2011 - 06:05:56 ART