Solved, it was indeed high volume traffic from windows machine on inside 
network 
that generated 200+ mbit of UDP traffic, possible a member of bot network :)

Thanks guys :)



________________________________
From: Mindless Gr <[email protected]>
To: [email protected]
Sent: Fri, April 1, 2011 2:12:04 PM
Subject: OSPFD: No buffer space available

Hello List :)

i came through a problem and i need your opinion about it, i have noticed that 
some times i get this type of errors in my /var/log/daemon file and these times 
my ospf adjacency goes to loading and full again as you see on the logs a 
little 

research over the internet didnt came with any results, when this message 
appears on the logs, i have tried to do netstat -m and gave me 5032 Kbytes 
allocated to network (77% in use) which normaly is 6 - 15%, how can i increase 
this buffer? or this problem came from somewhere else?

if you need any additional information please ask :)

Apr  1 06:41:51 brdr0 ospfd[21953]: send_packet: error sending packet on 
interface em1: No buffer space available
Apr  1 06:43:01 brdr0 last message repeated 3 times
Apr  1 06:43:21 brdr0 ospfd[21953]: recv_db_description: seq num mismatch, bad 
flags
Apr  1 06:43:21 brdr0 ospfd[21953]: send_packet: error sending packet on 
interface em1: No buffer space available
Apr  1 06:43:27 brdr0 bgpd[22462]: nexthop 192.168.10.36 now valid: via 
192.168.10.21
Apr  1 06:43:27 brdr0 bgpd[22462]: nexthop 192.168.10.38 now valid: via 
192.168.10.21
Apr  1 06:43:27 brdr0 bgpd[22462]: nexthop 192.168.10.36 now valid: via 
192.168.10.21
Apr  1 06:43:27 brdr0 bgpd[22462]: nexthop 192.168.10.38 now valid: via 
192.168.10.21
Apr  1 06:43:31 brdr0 ospfd[21953]: send_packet: error sending packet on 
interface em1: No buffer space available
Apr  1 06:43:40 brdr0 ospfd[21953]: send_packet: error sending packet on 
interface em1: No buffer space available
Apr  1 06:55:34 brdr0 ospfd[21953]: send_packet: error sending packet on 
interface em0: No buffer space available
Apr  1 06:55:54 brdr0 ospfd[21953]: send_packet: error sending packet on 
interface em0: No buffer space available
Apr  1 06:56:04 brdr0 ospfd[21953]: recv_db_description: seq num mismatch, bad 
flags
Apr  1 06:56:04 brdr0 ospfd[21953]: send_packet: error sending packet on 
interface em0: No buffer space available
Apr  1 06:56:05 brdr0 bgpd[22462]: nexthop 192.168.10.36 now valid: via 
192.168.10.25
Apr  1 06:56:05 brdr0 bgpd[22462]: nexthop 192.168.10.38 now valid: via 
192.168.10.25
Apr  1 06:56:09 brdr0 ospfd[21953]: send_packet: error sending packet on 
interface em1: No buffer space available
Apr  1 06:56:10 brdr0 bgpd[22462]: nexthop 192.168.10.36 now valid: via 
192.168.10.25
Apr  1 06:56:10 brdr0 bgpd[22462]: nexthop 192.168.10.38 now valid: via 
192.168.10.25
Apr  1 06:56:10 brdr0 bgpd[22462]: nexthop 192.168.10.36 now valid: via 
192.168.10.25
Apr  1 06:56:10 brdr0 bgpd[22462]: nexthop 192.168.10.38 now valid: via 
192.168.10.25
Apr  1 06:56:11 brdr0 ospfd[21953]: send_packet: error sending packet on 
interface em1: No buffer space available
Apr  1 06:56:32 brdr0 last message repeated 6 times
Apr  1 06:56:44 brdr0 ospfd[21953]: send_packet: error sending packet on 
interface em0: No buffer space available
Apr  1 06:57:54 brdr0 ospfd[21953]: send_packet: error sending packet on 
interface em0: No buffer space available


brdr0:~# netstat -m
188 mbufs in use:
        180 mbufs allocated to data
        2 mbufs allocated to packet headers
        6 mbufs allocated to socket names and addresses
156/2146/6144 mbuf 2048 byte clusters in use (current/peak/max)
0/8/6144 mbuf 4096 byte clusters in use (current/peak/max)
0/8/6144 mbuf 8192 byte clusters in use (current/peak/max)
0/8/6144 mbuf 9216 byte clusters in use (current/peak/max)
0/8/6144 mbuf 12288 byte clusters in use (current/peak/max)
0/8/6144 mbuf 16384 byte clusters in use (current/peak/max)
0/8/6144 mbuf 65536 byte clusters in use (current/peak/max)
5032 Kbytes allocated to network (7% in use)
0 requests for memory denied
0 requests for memory delayed
0 calls to protocol drain routines

Thanks in advance

Reply via email to