We've been having issues with this feature, which is supposed to be built into zenoss. We ran into a couple problems, one of which isn't resolved yet.
We have a point to point link between our two sites, with a Cisco ASA on each end. The first was a mismatch between the subnet masks on the inter-site link. Functionally, this didn't matter much, but it threw off the network map structure in zenoss. Once this config on the devices was corrected, we deleted all network objects in zenoss, and remodeled all devices, per support. This corrected the network map issue. The second issue is unresolved, and is related to traceroute. After support sent me a utility to identify breaks in the fault isolation dependency path, I started looking at how zenoss builds the internal network structure, apparently with traceroute. It turns out that Cisco ASAs do not decrement the TTL in traceroutes by default. I think this may have an adverse affect on the ability of zenoss to build the network path. I enabled the ttl decrement on our asa, however, the other is managed by a hosting provider, and they need time to test. It looks like you can add routes manually to the device models in zenoss, but that hasn't helped. Has anyone else had similar experiences? -------------------- m2f -------------------- Read this topic online here: http://forums.zenoss.com/viewtopic.php?p=25535#25535 -------------------- m2f -------------------- _______________________________________________ zenoss-users mailing list [email protected] http://lists.zenoss.org/mailman/listinfo/zenoss-users
