Gavin
I fear you may have misunderstood the purpose of multihomed. It only suppresses a log message. It doesn't override access restrictions imposed by running xymond with "--status-senders".
On 26 Mar 2015 2:54 pm, "Gavin Stone-Tolcher" <g.stone-tolcher at its.uq.edu.au> wrote:
By default, Xymon will warn if it sees data for one host coming
from different
The man page you quoted says "warn" not "reject".
169 xmh_item_key[XMH_FLAG_MULTIHOMED] = "MULTIHOMED";
Is that looking for “MULTIHOMED” in CAPS, not “multihomed” lowercase?
Yes. But elsewhere is code that parses the hosts.cfg file to find multihomed and then set MULTIHOMED.
Also, should line 170 have "XMH_FLAG_MULTIHOMED" rather than "XMH_MULTIHOMED"
No because it's setting the item name not the item key.
Xymon will be using some forms of the name as internal variable names and environment variables and so they might not mean what you think they mean.
Doing a xymondborad query against a host with “multihome” produces no result for that field:
Is it "multihome" like you have here or is it "multihomed"?
xymon localhost "xymondboard host=pf-parkingguide.pf.uq.edu.au fields=XMH_FLAG_MULTIHOMED"
I think this should work. What do you get from "xymongrep multihomed"? What do you get from your xymondboard command if you don't specify "fields=..."?
This section in xymond.c from line 1520 seems to be the code doing a check that XMH_FLAG_MULTIHOMED is NULL:
Yep. And you'll notice that it all boils down to whether or not to run this line:
log_multisrc(log, sender);
Any ideas on this one? Currently I have to add multihomed hosts to “--status-senders” otherwise.
You could disable --statussenders. Or you could add dummy host entries with the alternate IP addresses.
J