Wednesday, February 23, 2011

vrrp_send: send failed on interface eth2c0(172.16.1.1): No buffer space available

The most common solution is to issue a netstat -ni and look at the output corresponding to the interfaces mentioned in the error message. In a number of similar cases we've noticed a huge number of collisions on these interfaces.



ipso[admin]# netstat -ni

Name Mtu Network Address Ipkts Ierrs Opkts Oerrs Coll

loop0 0 0:0:0:0:0:0 0 0 0 0 0

pppoe0 1492 0:0:0:0:0:0 0 0 0 0 0

soverf0 1500 0:0:0:0:0:0 0 0 0 0 0

stof0 65535 0:0:0:0:0:0 0 0 0 0 0

tun0 0 0:0:0:0:0:0 0 0 0 0 0

eth1 1518 0:a0:8e:99:bc:93 185307 0 72412 0 0

eth2 1518 0:a0:8e:99:bc:94 4611410 0 3389113 76263 76263

eth3 1518 0:a0:8e:99:bc:95 20 0 0 0 0

eth4 1518 0:a0:8e:99:bc:96 3398470 0 4612687 93341 93341



Check the speed / duplex settings on these interfaces and the devices they connect to as there is most likely a mismatch.