On Wed, Aug 01, 2007 at 08:00:26AM -0500, Jacob Yocom-Piatt wrote: > i was redoing some ethernet cabling in the office and made 2 connections > between 2 switches before i pulled one connection. shortly after > plugging in the second cable the pair of webservers that use carp sans > preemption got "confused", causing a failover to the backup machine. > > here is a quick clarification of the cabling > > switch 1--------A-------switch 2 > \--------------B----------/ > > > where making connection B caused the drama. switch 1 is a nice managed > switch and switch 2 is a random POS. > > is this the expected behavior with carp when a cabling topology like > this comes up sans trunking, etc? clues about what happened would be great. >
You created a loop in the L2 broadcast domain and because carp is using multicast for the hellos you had a nice network meltdown (maybe your managed switch was realizing that and blocked the traffic). -- :wq Claudio
