I found a small gotcha with the zenpack when I stared renaming some of our
devices to less cryptic names.
If the device doesn't resolve in DNS the command errors out and doesn't graph
anything or in some cases (we have multiple interfaces on most servers) you end
up graphing latency on the wrong net because your really monitoring the ip that
resolves not the ip configured in Zenoss
The quick fix is to modify the command from :
Code:
check_ping -H $devname -w 180,100% -c 300,100% | sed -e 's# - Packet
loss#|LOSS#;s#%,##;s#ms##;s# = #=#g'
to:
Code:
check_ping -H ${device/manageIp} -w 180,100% -c 300,100% | sed -e 's# - Packet
loss#|LOSS#;s#%,##;s#ms##;s# = #=#g'
This forces the command to use the management ip in Zenoss
-------------------- m2f --------------------
Read this topic online here:
http://forums.zenoss.com/viewtopic.php?p=25798#25798
-------------------- m2f --------------------
_______________________________________________
zenoss-users mailing list
[email protected]
http://lists.zenoss.org/mailman/listinfo/zenoss-users
