Zenoss 2.3.3 on SLES 10. I have an environment with networks with various different netmasks - /16, /24 and /28. Devices on the /16 network I have hand-added. The /28 networks I have told Zenoss to discover all devices in the network. The /24 networks, I have done a mixture of hand-add devices and network discovery.
Results are not always consistent, however... I usually find that my class B network (10.191.0.0) gets a load of class C subnetworks. although no device has an interface on a 10.191.x class C network (if you inspect the subnetmask either directly or with SNMP). Even weirder, if you drill down to the 10.191/16 network and then drill down into these spurious class C subnetworks, the class Cs all say that they have a subnetwork - the 10.191 class B !! The result is that the network topology isn't properly built so there are problems with the Network Map application. Further, event suppression from devices behind failed routers can't work because Zenoss is confused about the topology (netdata's tracepath.py utility is great to help diagnose what is going on here - see http://forums.zenoss.com/viewtopic.php?t=6761&highlight=tracepath ) The only way I have found to get consistency is: 1) Discover the devices you need - one way or another 2) Drill down the Networks hierarchy, into any spurious subnetworks, and delete any IP addresses that shouldn't be there. 3) Then delete the spurious subnetwork itself. 4) For all relevant devices (especially routers) check interfaces and netmasks - some interfaces may now not have IP addresses if you deleted them in (2) 5) Remodel these devices and check that all interfaces, IP addresses and netmasks are correct 6) Use tracepath.py to check Zenoss's internal network topolgy 7) If there are breakages, check the route tables, especially of routers (under Zenoss's OS tab for a device). Any indirect route must have not only an IP address for the next hop but also a Name - if you don't have the name then it is an indication that the internal topology is broken. Recheck networks, netmasks and remodel. 8) I have found that deleting a whole device (rather than deleting an interface) is likely to bring back the spurious subnetworks and interfaces on a class C network, rather than class B, so this is to be avoided. 9) Incidentally, I find the Network Map application a real CPU hog (I suspect because of flash). I have an old Firefox on this system (2.0.0.2) - does everyone see Network Map gobbling CPU or can anyone tell me it gets better if I up-level my Firefox??? Anyone else see this netmask / cyclical spurious subnets syndrome? Anyone got any better workarounds? Cheers, Jane -------------------- m2f -------------------- Read this topic online here: http://forums.zenoss.com/viewtopic.php?p=32594#32594 -------------------- m2f -------------------- _______________________________________________ zenoss-users mailing list [email protected] http://lists.zenoss.org/mailman/listinfo/zenoss-users
