Morning all,

I received the following messages in routing.log today >>>


Aug 28 06:03:38 4slgbmernfw01 bgpd[18303]: neighbor 192.168.55.5 (AWS-DC MER 
Peer): sending notification: HoldTimer expired, unknown subcode 0

Aug 28 06:03:38 4slgbmernfw01 bgpd[18303]: neighbor 192.168.55.5 (AWS-DC MER 
Peer): state change Established -> Idle, reason: HoldTimer expired

Aug 28 06:04:08 4slgbmernfw01 bgpd[18303]: writev (6/80): No buffer space 
available

Aug 28 06:04:09 4slgbmernfw01 bgpd[18303]: writev (8/120): No buffer space 
available

Aug 28 06:04:09 4slgbmernfw01 bgpd[18303]: neighbor 192.168.55.5 (AWS-DC MER 
Peer): pfkey setup failed

Aug 28 06:04:10 4slgbmernfw01 bgpd[18303]: Connection attempt from neighbor 
192.168.55.5 (AWS-DC MER Peer) while session is in state Idle

Aug 28 06:04:46 4slgbmernfw01 bgpd[18303]: Connection attempt from neighbor 
192.168.55.5 (AWS-DC MER Peer) while session is in state Idle

Aug 28 06:05:18 4slgbmernfw01 bgpd[18303]: Connection attempt from neighbor 
192.168.55.5 (AWS-DC MER Peer) while session is in state Idle

Bgpd stopped routing.

I have restarted bgpd and everything is OK – but I would like to find out what 
happened or rather how to avoid it happening again – can anyone make any 
suggestions or point me in the right direction.  Was it because of the hold 
timer expiry ??

Many thanks,



Mark Relf
Principal Consultant

[cv_certified_engineer.gif]

4sl Group, 4 Snow Hill, London EC1A 2DJ
t: +44 (0) 203 307 1053
m: +44 (0) 7868 842548
w: www.4sl.com<http://www.4sl.com/>
e: mark.r...@4sl.com<mailto:mark.r...@4sl.com>

Planned away dates: None

[2013 Tech Track 100 logo - smaller]
Legal Disclaimer: The information in this email and any attachment is 
confidential and may also be privileged. If you have received this message in 
error please notify the sender and delete the message and attachments from your 
system immediately. You are not entitled to retain, copy or use this email for 
any purpose, nor disclose all or any part of its content to any other person.
_______________________________________________
List mailing list
List@lists.pfsense.org
https://lists.pfsense.org/mailman/listinfo/list

Reply via email to