Description

 Getting the logs of bgp_listen_accept: Connection attempt from unconfigured neighbors from multiple ip addresses

Symptoms

Logs:

 

 

Dec 24 13:44:03.218 2023 INBOM1SWSDFA06B rpd[2179]: %DAEMON-4: bgp_listen_accept: Connection attempt from unconfigured neighbor: 192.168.1.1+45485

Dec 24 13:44:03.218 2023 INBOM1SWSDFA06B rpd[2179]: %DAEMON-4: bgp_listen_accept:6755: NOTIFICATION sent to 192.168.1.1+45485 (proto): code 6 (Cease) subcode 5 (Connection Rejected), Reason: Connection attempt from unconfigured neighbor: 192.168.1.1+45485

Dec 24 13:44:03.640 2023 INBOM1SWSDFA06B rpd[2179]: %DAEMON-4: bgp_listen_accept: Connection attempt from unconfigured neighbor: 192.168.1.1+46321

Solution

This log is seen when unknown BGP peer connects to EX to establish BGP. In the example above, BGP peers such 192.168.1.1 (some others as well) are not configured in the configuration, but the peers try to connect to our EX side, then this message is seen.

When someone tries to connect to the listening port of BGP(i.e. tcp port 179), device generates an RPD task to check and connect. 

If the request is from an unrecognized peer, the device aborts this request and report this kind of message log which is an informational and there is no service impact. 

This is not our side problem, If you don’t want this kind of log appear, You can block it with the help of below KB.

https://supportportal.juniper.net/s/article/Junos-Platform-Example-How-to-prevent-certain-syslog-messages-from-being-written-to-the-log-file?language=en_US

Modification History

2024-01-01 : Article Created
24-may-2024: changed used IP's to private IP's, added SRX devices to products.