Making, drinking tea and reading an opus magnum from Tim:
> William Bloom <wbloom <at> eldocomp.com> writes:
>
> >
> > If I'd had this experience, I'd be tempted to use tcpdump on whichever
> physical
> > interface is carpdev for the suspect carp interface in order to verify that
> > multicast is enabled on your switch. With carp interfaces up, you should
> see
> > periodic multicast messages. If you don't see any, then you've found your
> > problem (and you need to revisit the switch configuration in order to fix
> it).
> > Bill
> >
>
> Thanks Bill. I'd suspect the switch too except that all 3 carp interfaces are
> on the same physical interface in this case, yet it's only carp0 that
> experiences this behavior. Nevertheless, I will haul out tcpdump and see
> what's
> going on. To answer your question, no, pf is not running on these boxes. I
> also have two 3.7 CARP/pfsync firewalls that have never exhibited this
> behavior
> and they are on the same switch.
dude
your carp0 is down. unless you "up" it -- nothing will happen.
i suggest you compare your hostname.carp* files to discover
what exactly you have missed in the hostname.carp0 .
cu
--
paranoic mickey (my employers have changed but, the name has remained)
