Neighbour table overflow Rumi, February 10, 2012 If you have a big network with the hundreds of hosts you can expect “Neighbour table overflow” error which occurs in large networks when there are two many ARP requests which the server is not able to reply. For example you’re using server as a DHCP server, cable modems provisioning, etc. Nov 10 03:18:17 myhost Neighbour table overflow. Nov 10 03:18:23 myhost printk: 12 messages suppressed. To check the present threshold level 1 cat /proc/sys/net/ipv4/neigh/default/gc_thresh1 It will give some value as 128 or 256 or 512. This can be increased to the next level.Like if the value is 128 then make the thresh1 value as 256 and thresh2 as 512 and thresh3 as 1024. Of curse, this can be fixed. The solution is to increase the threshhold values in /etc/sysctl.conf. Add following lines to /etc/sysctl.conf (RH based distros) net.ipv4.neigh.default.gc_thresh1 = 4096 net.ipv4.neigh.default.gc_thresh2 = 8192 net.ipv4.neigh.default.gc_thresh3 = 8192 net.ipv4.neigh.default.base_reachable_time = 86400 net.ipv4.neigh.default.gc_stale_time = 86400 Save sysctl.conf and exec sysctl -p. You can also reboot but it isn’t necessary. The default sysctl.conf file net.ipv4.ip_forward=0 kernel.shmmax=68719476736 kernel.msgmax=65536 kernel.msgmnb=65536 net.ipv4.conf.default.rp_filter=1 kernel.sysrq=0 net.ipv4.conf.default.accept_source_route=0 kernel.shmall=4294967296 kernel.core_uses_pid=1 net.ipv4.tcp_syncookies=1“ Tuned” systctl.conf net.ipv4.ip_forward=0 kernel.shmmax=4294967295 kernel.msgmax=65536 kernel.msgmnb=65536 net.ipv4.conf.default.rp_filter=1 kernel.sysrq=0 net.ipv4.conf.default.accept_source_route=0 kernel.shmall=268435456 kernel.core_uses_pid=1 net.ipv4.tcp_syncookies=1 net.ipv4.neigh.default.gc_thresh1 = 4096 net.ipv4.neigh.default.gc_thresh2 = 8192 net.ipv4.neigh.default.gc_thresh3 = 8192 net.ipv4.neigh.default.base_reachable_time = 86400 net.ipv4.neigh.default.gc_stale_time = 86400 Explanation… The neighbour table is generally known as ARP table and the default value for gc_thresh1 is 128 (Adjust where the gc will leave arp table alone) [root@myServer ~]# cat /proc/sys/net/ipv4/neigh/default/gc_thresh1 128which is not enough for large networks (more than 128 hosts). Thats why we need to tune this value. The gc_thresh2 is a soft limit (Tell the gc when to become aggressive with arp table cleaning.) and the gc_thresh3 is a hard limit (Don’t allow the arp table to become bigger than this). To enlarge the ARP cache table on the live system run: # sysctl -w net.ipv4.neigh.default.gc_thresh3=8192 # sysctl -w net.ipv4.neigh.default.gc_thresh2=8192 # sysctl -w net.ipv4.neigh.default.gc_thresh1=4096It is possible that after distro update your systctl.conf will be replaced with the default values. Check this file periodically.. Src: http://www.serveradminblog.com/2011/02/neighbour-table-overflow-sysctl-conf-tunning/ Some other reference: http://www.gnulinuxclub.org/index.php?option=com_content&task=view&id=333&Itemid=49 http://linuxman.wikispaces.com/Neighbour+table+overflow Related Administrations Configurations (Linux) PKI
Install Munin on SL 6 January 31, 2013 [root@master ~]# yum –enablerepo=epel -y install munin munin-node # install from EPEL [root@master ~]# vi /etc/munin/munin.conf # line 60: change to your hostname Related Read More
Enabling munin node plug-ins on Debian January 18, 2013January 18, 2013 Munin uses plug-ins to determine what data is gathered and reported. It includes several plug-ins for the types of data most people would be interested in, but not all of those plug-ins are enabled on a fresh installation. What are plug-ins? When a munin node gathers data about a slice… Read More
How to setup as DNS client / name server IP address August 26, 2008August 26, 2008 Many new Linux user finds it difficult to setup / modify new name server address (NS1 / NS2). Local name resolution is done via /etc/hosts file. If you have small network then use /etc/hosts file. DNS (domain name service is accountable for associating domain names with ip address, for example… Read More