I'm confused about how zendisc uses info from the database, and how to use that to control how far out zendisc will look for routers, for example.
My next-hop router from the zenoss server has over 1500 OSPF routes in both 10/8 and 172.16/12. I want to learn only networks and routers under 172.16/12. My first run gave me 800 networks in my database, most of which I didn't want :) After deleting all of those, I set /Networks zAutoDiscover to false, and then created a 172.16.0.0/12 network with zAutoDiscover set to True. Unfortunately this caused all routes picked up by SNMP to show a destination of 172.16.0.0. I'm also not sure I understand the purpose of zRouteMapCollectOnlyIndirect. When would I want to add only non-connected routes to the collected table? (That's all for now ... I've got to go figure out how to fix what I broke by entering "^10." as a filter string in the /Networks view.) _______________________________________________ zenoss-users mailing list [email protected] http://lists.zenoss.org/mailman/listinfo/zenoss-users
