On Friday 20 January 2017 at 11:46:30, Joosten, Markus wrote:
> On 2017-01-20 11:33, Antony Stone wrote:
> > On Friday 20 January 2017 at 10:00:28, Joosten, Markus wrote:
> >> I have solved this issue by also having my satellite hosts in my
> >> master zone (with a reduced amount of services of course).
> >
> > Would you care to expand on that?
> >
> > How do you get one host to be in more than one zone (since I assume
> > your satellite hosts exist in their own satellite zone, hence your use of
> > "also" there)?
> >
> > I was under the impression that one EndPoint existed in only one Zone,
> > and (unless you have an HA setup) one Zone contains only one EndPoint;
> > further, each Host belongs to one Zone (although obviously one Zone can
> > contain multiple Hosts).
>
> Sorry if I wrote this easy to misunderstand, one host is only member of
> a single zone of course.
> Beside the host objects in the satellite zones (the satellites checking
> themselves) I also create similarly named hosts in my master zone (the
> master checks each satellite), e.g.:
>
> - host customer001-satellite in zone master
> - host customer001-satellite-local in zone customer001
Ah :)
So, you know it's the same machine twice, but Icinga doesn't :)
> Hope that helps clarifying what I meant :)
Indeed, thanks.
Antony.
--
Software development can be quick, high quality, or low cost.
The customer gets to pick any two out of three.
Please reply to the list;
please *don't* CC me.
_______________________________________________
icinga-users mailing list
icinga-users@lists.icinga.org
https://lists.icinga.org/mailman/listinfo/icinga-users
