On Thu, 28 Jun 2007 08:11:53 +0000
"jsegura" <[EMAIL PROTECTED]> wrote:
>
> stldave wrote:
> > The easiest way I can think of accomplishing this is by setting up VPN
> > tunnels between your Zenoss server and the remote enetworks, then
> > monitoring things directly.
> >
> > Is this feasible for you?
>
>
> With this way I can monitor my subservers (see my first post) as if they were
> in the same local network as my master server. The problem comes (I think)
> when trying to monitor the nodes hanged on these subservers because all
> private networks have the same network adresses.[/i]
Hey Javier,
I'm interested in the setup you are planning - i haven't looked too deeply into
the capabilities of the multi-server setup.
I gather from the thread that the setup you have is something like this:
dyn_IP_A : ZenossSubA -> subnet 192.168.1.1
dyn_IP_B : ZenossSubB -> subnet 192.168.1.1
dyn_IP_C : ZenossSubC -> subnet 192.168.1.1
ZenosMain [somewhere else ]
right? Does ZenossMain have to talk directly to all the hosts in the various
192.168.1.1 , or shouldn't ZenossMain receive the info from each of
ZenossSubA, SubB and SubC? Each of the Sub* would know what their monitored
hosts IP and hostnames are - I would make sure the hostnames , or at least the
emails /alerts sent 'upwards' to ZenossMain include enough information to
discern host 192.168.1.10 from SubA and host 192.168.1.10 from SubB....
doest that make sense ? as I said, i haven't looked into this features yet,
but i'd imagine that's how it'd work...
B
_________________________
{Beto|Norberto|Numard} Meijome
"Great spirits have often encountered violent opposition from mediocre minds."
Albert Einstein
I speak for myself, not my employer. Contents may be hot. Slippery when wet.
Reading disclaimers makes you go blind. Writing them is worse. You have been
Warned.
_______________________________________________
zenoss-users mailing list
[email protected]
http://lists.zenoss.org/mailman/listinfo/zenoss-users
