On Tue, Oct 10, 2006 at 05:50:50PM -0400, Brian A. Seklecki wrote:
> Certainly a way to log events (interfaces, etc.) and the resulting actions
> taken by the code would be useful in mission critical environments.
>
> Anything beats "tcpdump 'proto carp'" and making guesses from there.
Nothing new to 4.0, but a few of the things you can do besides using
tcpdump are:
route monitor
- see interface link state change
sysctl net.inet.carp.log=1
- generates primarily protocol error messages
netstat -sp carp
- display a number of relevant counters
If you want to do more complicated things, like run commands when carp
interfaces change state, you can have a look at ifstated.
-Ryan
