Hi Henning > * Pete Bristow <[EMAIL PROTECTED]> [2006-02-17 12:30]: > >>I've got OpenBGPD running on 3.7, currently whenever I bring up a >>session with another peer the session drops to Idle as soon as a set of >>routes are learnt. > > > that, of course, is not normal behaviour and nothing we ever observed... > > >>This behaviour has been observed when bringing sessions up against other >>routers too. Is there a way of getting bgpd to log more information as >>to why the session was torn down, rather than just logging state >>changes. I would speak to AS6871 about the problem but as yet I havn't >>worked out what's going wrong. > > > please show the logs. bgpd does log why a sessions drops back to IDLE. >
Feb 17 12:15:54 a bgpd[28123]: neighbor 217.112.a.b (BD01): state change Idle -> Connect, reason: Start Feb 17 12:15:54 a bgpd[28123]: neighbor 217.112.a.b (BD01): state change Connect -> OpenSent, reason: Connection opened Feb 17 12:15:54 a bgpd[28123]: neighbor 217.112.a.b (BD01): state change OpenSent -> OpenConfirm, reason: OPEN message received Feb 17 12:15:54 a bgpd[28123]: neighbor 217.112.a.b (BD01): state change OpenConfirm -> Established, reason: KEEPALIVE message received Feb 17 12:16:05 a bgpd[28123]: neighbor 217.112.a.b (BD01): state change Established -> Idle, reason: Connection closed Was all I got. Pete
