On Mon, Jan 9, 2012 at 7:26 AM, Florian Lohoff <span dir="ltr"><<a href="mailto:f@zz.de">f@zz.de</a>></span> wrote:<br><div class="gmail_quote"><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<br>
Hi,<br>
<br>
i am thinking about the monitoring with dualstack targets/hosts. I'd expect<br>
all our hosts and services to be dual stacked or at least single stacked services<br>
to be the exception.<br>
<br>
So adding a v6 host for all v4 hosts seems so odd. I was thinking about adding<br>
some _v6address variable to all host definitions and defining v6 services using<br>
host HOSTADDRESS but _HOSTV6ADDRESS.<br>
<br>
In the end it would even be more natural to check_ping to check both address families<br>
if available and go to CRITICAL if one of them fails. In the end v6 should be a equivalent<br>
member of the family.<br>
<br>
Whats the preferred way people have chosen and what where the pitfalls?<br>
<br>
Flo<br>
<span class="HOEnZb"><font color="#888888">--<br>
Florian Lohoff <a href="mailto:f@zz.de">f@zz.de</a><br>
</font></span><br></blockquote><div><br></div><div>Hi Flo,</div><div><br></div><div>At work we have started to go dualstack with all of our servers. Currently our web servers are 100% dualstack so most of our monitoring dualstack experience is based off of these servers. We have noticed that IPv4 connectivity is more important than IPv6 since a client is more likely to have an IPv4 address than IPv6, also if a web client accesses a server over IPv6 and the server doesn't respond on IPv6 it will timeout and fall back to IPv4. I suggest that you monitor these ping check separately so that you'll be able to troubleshoot where the problem is on the IPv4 side of the IPv6 side. If you really want to monitor these together I would look into clustering these two ping checks and set a warning if one of these fails. Here is the info about <a href="http://nagiosplugins.org/man/check_cluster">check_cluster</a></div>
<div><br></div><div>--<div><b><font face="arial, helvetica, sans-serif">Robert V. Bolton</font></b></div><div><font face="arial, helvetica, sans-serif">Email: <a href="mailto:robert@robertvbolton.com" target="_blank">robert@robertvbolton.com</a></font></div>
<div>Web: <a href="http://robertvbolton.com" target="_blank">http://robertvbolton.com</a></div>
<br></div></div>