[Xymon] xymonnet testip And host.cfg Entry

[Thomas Eckert]

On both lines mentioning your glabal zone the hash (#) after the hostname is missing. Probably just a cut and paste error.

Having used conn checks for multihomed machines rarely but from the manpage the syntax seems to be:

10.###.###.12    <global zone> #  conn=best,10.###.###.12,172.###.###.78

Cheers
Thomas

On Aug 22, 2014 6:17 PM, "Rebman,Scott (HHSC Contractor)" <Scott.Rebman at hhsc.state.tx.us> wrote:
>
> Looking for assistance in recognizing (pinging) admin networks on Solaris 10/11 global zones and ldoms but keep using public IP’s for containers (zones)
>  
> Found the following on the xymonnet man page:
>  
> --dns=[ip|only|standard]
> Determines how xymonnet finds the IP adresses of the hosts to test. By default (the "standard"), xymonnet does a DNS lookup of the hostname to determine the IP address, unless the host has the "testip" tag, or the DNS lookup fails. 
> With "--dns=only" xymonnet will ONLY do the DNS lookup; if it fails, then all services on that host will be reported as being down. 
> With "--dns=ip" xymonnet will never do a DNS lookup; it will use the IP adresse specified in hosts.cfg for the tests. Thus, this setting is equivalent to having the "testip" tag on all hosts. Note that http tests will ignore this setting and still perform a DNS lookup for the hostname given in the URL; see the "xymonnet tags for HTTP tests" section in hosts.cfg(5)
>  
> But on the host.cfg man page:
>  
> testip
> By default, Xymon will perform a name lookup of the hostname to get the IP address it will use for network tests. This tag causes Xymon to use the IP listed in the hosts.cfg file.
>  
> But then it goes on to say later in the hosts.cfg page:
>  
> Testing sites by IP-address
> xymonnet ignores the "testip" tag normally used to force a test to use the IP-address from the hosts.cfg file instead of the hostname, when it performs http and https tests.
> The reason for this is that it interacts badly with virtual hosts, especially if these are IP-based as is common with https-websites.
> The xymon info page does list the admin network IP but the conn page continues to check the public IP address:
>  
> <Organization Name>
> <Global Zone> - Information
> Fri Aug 22 09:38:43 2014
>  
> 08/21/14 What happened to the iostat2 column on the Solaris boxes?
>
>
>  
> Hostname:
> <Global Zone>
> OS:
> SunOS <Global Zone> 5.11 11.1 sun4v sparc sun4v
> Client S/W:
> IP:
> 172.###.###.78
>  
> <Organization Name>
> <Global Zone> - conn
> Fri Aug 22 09:40:14 2014
>  
> 08/21/14 What happened to the iostat2 column on the Solaris boxes?
>
>
>  
> Top of Form
> Bottom of Form
> Fri Aug 22 09:38:41 2014 conn NOT ok
>  
> Service conn on <Global Zone> is not OK : Host does not respond to ping
>  
>  
> System unreachable for 1424 poll periods (258838 seconds)
>  
>   10.###.###.12 is unreachable
>  
>  
>  
>  
>  
> host.cfg file entry:
>  
> group
> 172.###.###.78   <global hostname> testip
> 10.###.###.41    <container hostname> #COMMENT:"<comment>"
> 10.###.###.42    <container hostname> #COMMENT:"<comment>"
> 10.###.###.43    <container hostname> #COMMENT:"<comment>"
> 10.###.###.44    <container hostname> #COMMENT:"<comment>"
> 10.###.###.45    <container hostname> #COMMENT:"<comment>"
> 10.###.###.46    <container hostname> #COMMENT:"<comment>"
> 10.###.###.47    <container hostname> #COMMENT:"<comment>"
> 10.###.###.48    <container hostname> #COMMENT:"<comment>"
> 10.###.###.49    <container hostname> #COMMENT:"<comment>"
> 10.###.###.79    <container hostname> #COMMENT:"<comment>"
> 10.###.###.81    <container hostname> #COMMENT:"<comment>"
> 10.###.###.166   <container hostname> #COMMENT:"<comment>"
> 10.###.###.53    <container hostname> #COMMENT:"<comment>"
> 10.###.###.170   <container hostname> #COMMENT:"<comment>"
> 10.###.###.55    <container hostname> #COMMENT:"<comment>"
> 10.###.###.56    <container hostname> #COMMENT:"<comment>"
> 10.###.###.57    <container hostname> #COMMENT:"<comment>"
> 10.###.###.58    <container hostname> #COMMENT:"<comment>"
> 10.###.###.73    <container hostname> #COMMENT:"<comment>"
> 10.###.###.168   <container hostname> #COMMENT:"<comment>"
>  
> I have also added the following entry to the hosts.cfg file with no luck getting the conn to go green:
>  
> 10.###.###.12    <global zone> conn={best}10.###.###.12,172.###.###.78
>  
> How do I correct this to have the conn also ping the admin IP address but yet allow the continued checks of DNS for the containers (zones)?
>  
> Scott Allen Rebman 
> Solaris System Administrator 
> Northrop Grumman
>  
>  
>  
>  
>