Module: check_mk
Branch: master
Commit: 0cdf00ef3904792d078889542bdf280c0ee9e1e3
URL:
http://git.mathias-kettner.de/git/?p=check_mk.git;a=commit;h=0cdf00ef390479…
Author: Lars Michelsen <lm(a)mathias-kettner.de>
Date: Wed Oct 14 16:31:58 2015 +0200
Updated werk text
---
.werks/2674 | 7 ++++++-
1 file changed, 6 insertions(+), 1 deletion(-)
diff --git a/.werks/2674 b/.werks/2674
index 2ad124f..cb64aa5 100644
--- a/.werks/2674
+++ b/.werks/2674
@@ -31,11 +31,16 @@ the only check working vith IPv6 is <tt>check_http</tt>.
This is the default and recommended way for monitoring dual-stack hosts. You use one
address family for monitoring the whole system and the other one is just being pinged.
-Note: If you use the Check_MK Enterprise Edition togehter with the Micro Core,
+Note: If you use the Check_MK Enterprise Edition together with the Micro Core,
the Smart PING mechanism is not used for IPv6 hosts at the moment. This mechanism has
a slightly slower performance, but if you don't have too many IPv6 hosts, this
should
be OK for the beginning.
+If you use the xinetd for serving the Check_MK agent output, you need to configure
+xinetd to create an IPv6 socket. By default it only creates an IPv4 socket. If you
+use the Agent Bakery, the baked agents configure xinetd to use the primary IP address
+family of the hosts.
+
The basic implementation for IPv6 monitoring has been done. But there are several
components in the Check_MK environment left which need to be extended to be fully
compatible with IPv6. Some of them are: