[ednog] DNS server monitoring

Julian Y. Koh kohster at northwestern.edu
Tue Nov 29 08:53:23 EST 2005


-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

At 17:11 -0800 11/28/2005, Mark Boolootian wrote:
>The one caveat to this is that dedicated syslog servers that don't run
>any traffic-generating applications end up having their MAC address aged
>out of the forwarding tables of the L2 gear, and your syslog traffic ends
>up flooded to everyone in the same broadcast domain.

Yeah, we saw this as well.  The solution is to keep your L2 CAM tables in
sync with your L3 ARP tables as far as expire time is concerned.  Another
workaround is to regularly ping the receiving interface of the syslog server
from a monitoring station.


-----BEGIN PGP SIGNATURE-----
Version: PGP Desktop 9.0.3 (Build 2932)
Comment: <http://bt.ittns.northwestern.edu/julian/pgppubkey.html>

iQA/AwUBQ4xdUQ5UB5zJHgFjEQICzwCfZ6EnaFF2ZHnCWo/sXqimpAyXbKwAoIAK
fhD8qsqVDFlfKHhX03nv3NMx
=/n13
-----END PGP SIGNATURE-----

-- 
Julian Y. Koh                         <mailto:kohster at northwestern.edu>
Network Engineer                                   <phone:847-467-5780>
Telecommunications and Network Services         Northwestern University
PGP Public Key:<http://bt.ittns.northwestern.edu/julian/pgppubkey.html>


More information about the ednog mailing list