Description

EBGP session goes down to idle with log:

 

Connect event OpenFail new state Idle

Symptoms

Check if you see this error log:

 

bgp_connect_complete: error connecting to X.X.X.X (External AS XXXXX): Unknown error: -14336<<<<

 

Hint logs:

 

Jan 23 12:50:38.859112 task_set_option_internal: task BGP_65300_65150.172.16.0.110 socket 139 option TcpAggressiveTransmission(59) value 0

Jan 23 12:51:51.537647 task_process_events_internal: connect ready for BGP_65300_65150.172.16.0.110

Jan 23 12:51:51.537656 bgp_connect_complete: error connecting to 172.16.0.110 (External AS 65300): No error: 0

Jan 23 12:51:51.537659 BGP peer 172.16.0.110 (External AS 65300) CLOSE: close socket 139

Jan 23 12:51:51.537662 task_close: close socket 139 task BGP_65300_65150.172.16.0.110

Jan 23 12:51:51.537667 task_reset_socket: task BGP_65300_65150.172.16.0.110 socket 139

Jan 23 12:51:51.537688 bgp_event: peer 172.16.0.110 (External AS 65300) old state Connect event OpenFail new state Idle

Jan 23 12:51:51.537761 bgp_event: peer 172.16.0.110 (External AS 65300) old state Idle event Start new state Active

Jan 23 12:53:04.532081 bgp_connect_timeout: BGP_65300_65150.172.16.0.110_Connect

Jan 23 12:53:04.532096 bgp_connect_start: peer 172.16.0.110 (External AS 65300)

 

Here we can see that the session goes to connect and then fails and returns to idle:

Connect event OpenFail new state Idle

 

Before that we can see that the socket 139 gets closed and then this event happens.

 

This behavior repeats after a few seconds again:

 

bgp_connect_complete: error connecting to 172.16.0.110 (External AS 65300): No error: 0

Línea  35: Jan 23 12:54:19.541614 BGP peer 172.16.0.110 (External AS 65300) CLOSE: close socket 145

Línea  36: Jan 23 12:54:19.541616 task_close: close socket 145 task BGP_65300_65150.172.16.0.110

Línea  37: Jan 23 12:54:19.541618 task_reset_socket: task BGP_65300_65150.172.16.0.110 socket 145

Línea  38: Jan 23 12:54:19.541642 bgp_event: peer 172.16.0.110 (External AS 65300) old state Connect event OpenFail new state Idle

Línea  39: Jan 23 12:54:19.541716 bgp_event: peer 172.16.0.110 (External AS 65300) old state Idle event Start new state Active

Línea  40: Jan 23 12:55:32.532756 bgp_connect_timeout: BGP_65300_65150.172.16.0.110_Connect

Solution

If error log Unknown error: -14336 is seen, this can be caused for any password set incorrectly in between the peers. Check for a possible MD5 digest error in logs and delete or set correctly any password for BGP or peers and issue should clear.

Modification History

2024-01-24 : Article Created