The neighbor table overflow occurs. The reason is being found ....
The first statement:
Kernel-maintained ARP tables are too large and jitters.
Kernel ARP parameters:
======================================
Gc_stale_time
Determines the validity period of each adjacent layer record. When an adjacent layer record fails, it will be resolved again before sending data to it. The default value is 60 seconds.
Gc_thresh1
The minimum number of layers that exist in the ARP cache. If the number is smaller than this number, the garbage collector will not run. The default value is 128.
Gc_thresh2
Maximum number of records saved in the ARP cache. The garbage collector allows more than 5 seconds to record before starting collection. The default value is 512.
Gc_thresh3
The maximum number of records saved in the ARP cache. Once the number of records in the cache exceeds this limit, the garbage collector runs immediately. The default value is 1024.
======================================
For example, if the result of ARP-an | WC-L is about 300, you should increase the values of gc_thresh to prevent jitter:
Echo "net. ipv4.neigh. Default. gc_thresh1 = 512"> sysctl. conf
Echo "net. ipv4.neigh. Default. gc_thresh2 = 2048"> sysctl. conf
Echo "net. ipv4.neigh. Default. gc_thresh3 = 4096"> sysctl. conf
Second statement:
Subnet Mask setting error, check
Third statement:
Kernel compilation Error
Fourth statement:
Not seen yet