Ok, I figured it out (without knowing Python). Toss out the shell script shown above as all it did was a different trace route.
The problem has nothing to do with the zenping.conf file. It was an issue with us (me) interpreting your (NetData's) suggestions for setting up. Most of confusion came from it echoing the source and destination names then failing. The Python script does a lookup of the device name in the database and resolves an actual device to a Zenoss device, not an normal trace route. The error 'invalid source' is caused by no object in Zenoss for the Zenoss server its self. I created a new object under Devices/Server/Linux/SLES to represent the actual Zenoss server I was using and all of a sudden I was getting invalid destination. Bingo! Now all I have to figure out is how to get into Zenoss all the WAN router devices and routing tables that our telco is providing and won't tell us anything about. -------------------- m2f -------------------- Read this topic online here: http://forums.zenoss.com/viewtopic.php?p=30004#30004 -------------------- m2f -------------------- _______________________________________________ zenoss-users mailing list [email protected] http://lists.zenoss.org/mailman/listinfo/zenoss-users
