> shared IP address. This will be useful so I won't have to do any > reconfiguration on where the heartbeats are sent. But, there could be a > loss of heartbeats received, and the system could *think* these are failing > when in reality they are not able to send their heartbeats because the have > the old MAC address in their ARP cache. So, gratuitous ARP was told to me > as the solution for this. And, with explanations on the list as well as > re-reading Stevens chapter on it I think this is a viable solution. If it > is NOT a system call or system API in the Linux Kernel, would it not be > easier just to issue a remote command to flush the ARP caches? i.e. 'rsh -d > <hostname>' so that node would be forced to re-issue the initial ARP? > TIA > -Brad Gratuitous arp is the common solution for this - and better than issuing an arp flush, which is rather drastic. Why zap everything on account of one bad entry? Check out the heartbeat utility that was just posted in the previous reply if at all possible.. thanks, Nivedita - : send the line "unsubscribe linux-net" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
