Hello
Expanding my use of Zenoss I find that several of the sites I monitor use the
same range of private IP addresses, for example 192.168.1.0/24. If I only
monitor, through the use of a single port-forward, the main server at each site
I end up with a picture like this:
Server1 at public ip address A1.B1.C1.D1 (which only has an interface
on 192.168.1.1)
Server2 at public ip address A2.B2.C2.D2 (which only has an interface
on 192.168.1.1)
And both servers have a default route to 192.168.1.254.
Add to that my own internal network which also happens to use 192.168.1.0/24,
replete with a router at 192.168.1.254 and once you have Zenoss draw the map
and it concludes all servers are connected to the same router! To avoid this
problem there has to be some way to indicate that there exist islands of
private address space. How do other management platforms handle this? How can
we enhance Zenoss to handle this?
PaulW
------------------------
Paul Winkeler
-------------------- m2f --------------------
Read this topic online here:
http://community.zenoss.com/forums/viewtopic.php?p=11962#11962
-------------------- m2f --------------------
_______________________________________________
zenoss-users mailing list
[email protected]
http://lists.zenoss.org/mailman/listinfo/zenoss-users
