On Mon, Dec 15, 2008 at 9:14 AM, Jussi Peltola <pe...@pelzi.net> wrote:
> On Mon, Dec 15, 2008 at 03:43:43AM +0100, Felipe Alfaro Solana wrote: > > If the two machines that are part of the same CARP group are connected to > > the same switch, and you are experiencing packet loss, then something > really > > bad is going on. How many ports does your switch have? Perhaps the total > > aggregated switching capacity of the switch is not enough in your > > deployment. > > Who says the switch is losing the packets, if your router is overloaded > it's forwarding at 100% speed and you have no room for CARP > announcements. One solution would be to increase the time between > advertisements and hope for the best. What does "overloaded" mean? It's CPU overload? NIC overload? If it's CPU, it might be possible that CARP packets will get lost but who cares? Because if the router's CPU is at 100% you have a problem and need to scale up. If the NIC is overloaded, it means you have too much non-TCP traffic and are not using Ethernet flow control. Perhaps using Ethernet flow control might help. IME forwarded packets seem to somehow have a higher priority than > self-originated traffic in most OS's; don't know why this is, just a gut > feeling. Probably related to interrupts taking away CPU time from other > things; if the machine is so loaded the physical console is slow as > molasses, I doubt that CARP can work very well either. > > -- > Jussi Peltola > > -- http://www.felipe-alfaro.org/blog/disclaimer/
