Charles,
We actually have private Ips but selection of them isn't available in
the UI. You can change the code in IpInterface.py at 384 and add
more to the regex. I added a ticket to expose this to the UI.
http://dev.zenoss.org/trac/ticket/961
You can run multiple zenmodeler processes on your external boxes.
You will need to point them to different parts of the device tree
using the -p flag. Of course the also need a connection back to the
central zeo database.
-EAD
On Feb 1, 2007, at 10:57 AM, Charles Tan wrote:
Zenoss,
It appears as though Zenoss will not allow for multiple devices
that have the same IP address assigned to an interface.
For example, say we have performance/status serverA monitoring
devices in siteA as well as the performance/status serverB
monitoring devices in siteB. Inside both siteA and siteB, there are
existing devices that use private IP address space that happens to
overlap between the two sites (physically separate networks, but
the same private IP space). Both serverA and serverB are configured
by a central Zenoss instance. Currently when trying to add a device
with an IP address that exists, Zenoss reports back with a "Ip
x.x.x.x exists on" critical message.
Would it be feasible to enable private address spaces in Zenoss to
allow for multiple devices with the same IP address (using
different performance/status montiors)?
I also noticed that when adding a device from the central Zenoss
controller and assigning either serverA or serverB as the status/
performance monitor, the central server still tries to collect the
information. Is this a bug? I assumed that the chosen performance
monitor would do the initial collection, since the device is only
accessible to Zenoss through the performance monitor.
Thanks,
Charles
_______________________________________________
zenoss-users mailing list
[email protected]
http://lists.zenoss.org/mailman/listinfo/zenoss-users
_______________________________________________
zenoss-users mailing list
[email protected]
http://lists.zenoss.org/mailman/listinfo/zenoss-users
