Hi guys, Many thanks netdata for that script, it helped us improve our layer3 tology as it shown us strait we did it wrong.
To answer hummerboy, we had to build our topology "by hand" as our telco is proving us an MPLS cloud. To build the topology we did the following: - on the router collectors we removed the RouteMap collector to avoid seeing the telco could - we created a "dummy" network 192.168.105.0/24 - on each router we added a "dummy" interface "ethcloud" with ip 192.168.105.x and we locked the interface to avoid the modeler removing it. - on zenping.conf we set the root device as the router zenoss is using. - on that router we manually added routes to all remote networks though the dummy network. - on each router we added a route to the local network on the ethernet interface. Say we have a zenoss server is in paris (192.168.0.2/24) , it's router is 192.168.0.1, and we have a device in London (192.168.1.2/24) with a router 192.168.1.1. zenoss.paris eth0 (automatic) 192.168.0.2 default route (automatic) 0.0.0.0/0 => 192.168.0.1 router.paris eth0 (automatic) : 192.168.0.1 ethcloud (manual) : 192.168.105.1 route (manual) : 192.168.1.0/24 => 192.168.105.2 / ethcloud / local / indirect router.london eth0 (automatic) : 192.168.1.1 ethcloud (manual) : 192.168.105.2 route (manual) : 192.168.1.0/24 => none / eth0 / local / direct device.paris eth0 (automatic) : 192.168.1.2 Now zenping is able to build a path from zenoss to the device through the clould and so create dependencies. -- Florian Deckert SopraGroup - France -------------------- m2f -------------------- Read this topic online here: http://forums.zenoss.com/viewtopic.php?p=30006#30006 -------------------- m2f -------------------- _______________________________________________ zenoss-users mailing list [email protected] http://lists.zenoss.org/mailman/listinfo/zenoss-users
