Had anybody encountered an issues with trucated data when using exec in the snmpd.conf to execute a command on a remote host. When running the command on the actual host all output lines get displayed and are complete. Here are the last three lines of the output...
data8 516287984 370097752 146190232 72% /data8
data4 413030384 258884720 154145664 63% /data4
root_fs_2 258128 14704 243424 6% /
Now, when executing a snmpwalk (from the monitoring server) with the custom OID the following is displayed. As you can see the truncation starts in the second to last line. In total the script on the remote host produces 16 lines of output, anybody aware of any exec character or line output limitations?
SNMPv2-SMI::enterprises.1139.999126.96.36.199 = STRING: "data8 516287984 370097752 146190232 72% /data8"
SNMPv2-SMI::enterprises.1139.999188.8.131.52 = STRING: "data4 413030384 258884720 1541"
SNMPv2-SMI::enterprises.1139.999184.108.40.206 = INTEGER: 0
SNMPv2-SMI::enterprises.1139.999220.127.116.11 = ""
This is the exec line in the snmpd.conf.
exec .18.104.22.168.4.1.1139.99999.1 server_df /bin/bash /nas/bin/server_df_wrapper
Thanks in advance for any input...
Thanks for all your helpful answers.
Technically this isn't a SNMP issue, however isn't Zenoss highly dependent on SNMP. This issue is directly related to the EMC Celerra FileSystem ZenPack, in order to get this ZenPack working you need to extend SNMP with the exec command, which isn't fully working due the truncation errors I mentioned on my earlier posts.
I understand that one of the installation steps of the ZenPack is extending SNMP functionality on the device. Zenoss is not "highly dependent" on SNMP. It supports monitoring via SNMP, which is one of many monitoring protocols which it supports. You are receiving truncated values when performing an SNMPWALK. It has absolutely nothing to do with Zenoss and everything to do with net-snmp. I don't personally know the answer and no one else seems to have chimed in which is why we suggested that you may get better support for this type of issue on a Linux forum.
Follow Us On Twitter »
||Latest from the Zenoss Blog »||Community||Products||Services||Customers||About Us|
Copyright © 2005-2011 Zenoss, Inc.