Menu
▾
▴
Re: [Devmon] Problem reading out SNMP values with Devmon; snmpwalk is working
|
From: Buchan M. <bg...@st...> - 2012-06-04 23:34:50
|
On Thursday, 31 May 2012 13:07:55 Becker Christian wrote: > Hello out there, > > I have a problem for which I neither have a solution nor an explanation why > this problem occurs. > > I have Devmon v0.3.1-beta1 running on a Xymon 4.3.7 server. The operating > system is Red Hat Enterprise Linux Server release 6.1 (Santiago). I have > installed templates from the sourceforge site; these templates are working > and my Xymon pages are being populated with values coming from the devices > having the DEVMON tag in the hosts.cfg file. > > Now that we have the Cisco Call Manager (aka Cisco Unified Communications) > up and running at our site, I was in the need to include these components > (which are Cisco proprietary linux virtual machines) into Xymon. After > reading around a bit I came to the solution, that the template > linux-netsnmp would do the things for us that we need. > > And here the problem starts. > > Looking into the file <path-to-devmon>/templates/linux-netsnmp/disk/oids I > can see the following: DiskName : > .1.3.6.1.2.1.25.2.3.1.3 : branch DiskBlocks > : .1.3.6.1.2.1.25.2.3.1.5 : branch DiskBlocksUsed : > .1.3.6.1.2.1.25.2.3.1.6 : branch DiskBlockSize : > .1.3.6.1.2.1.25.2.3.1.4 : branch > > Testing these snmp values with the "normal" snmpwalk command against my > Cisco target produces the following output: [root@xymon disk]# snmpwalk > -v2c -cpublic MY.CISCO.TARGET .1.3.6.1.2.1.25.2.3.1.3 > HOST-RESOURCES-MIB::hrStorageDescr.1 = STRING: Physical RAM > HOST-RESOURCES-MIB::hrStorageDescr.2 = STRING: Virtual Memory > HOST-RESOURCES-MIB::hrStorageDescr.3 = STRING: / > HOST-RESOURCES-MIB::hrStorageDescr.4 = STRING: /proc > HOST-RESOURCES-MIB::hrStorageDescr.5 = STRING: /sys > HOST-RESOURCES-MIB::hrStorageDescr.6 = STRING: /dev/pts > HOST-RESOURCES-MIB::hrStorageDescr.7 = STRING: /grub > HOST-RESOURCES-MIB::hrStorageDescr.8 = STRING: /partB > HOST-RESOURCES-MIB::hrStorageDescr.9 = STRING: /common > HOST-RESOURCES-MIB::hrStorageDescr.10 = STRING: /dev/shm > HOST-RESOURCES-MIB::hrStorageDescr.11 = STRING: /proc/sys/fs/binfmt_misc > HOST-RESOURCES-MIB::hrStorageDescr.12 = STRING: > /var/log/ramfs/cm/trace/ccm/sdi HOST-RESOURCES-MIB::hrStorageDescr.13 = > STRING: /var/log/ramfs/cm/trace/ccm/sdl > HOST-RESOURCES-MIB::hrStorageDescr.14 = STRING: > /var/log/ramfs/cm/trace/ccm/calllogs HOST-RESOURCES-MIB::hrStorageDescr.15 > = STRING: /var/log/ramfs/cm/trace/ccm/dntrace > HOST-RESOURCES-MIB::hrStorageDescr.16 = STRING: > /var/log/ramfs/cm/trace/cti/sdi HOST-RESOURCES-MIB::hrStorageDescr.17 = > STRING: /var/log/ramfs/cm/trace/cti/sdl [root@xymon disk]# > > [root@xymon disk]# snmpwalk -v2c -cpublic MY.CISCO.TARGET > .1.3.6.1.2.1.25.2.3.1.5 HOST-RESOURCES-MIB::hrStorageSize.1 = INTEGER: > 1004241 > HOST-RESOURCES-MIB::hrStorageSize.2 = INTEGER: 516070 > HOST-RESOURCES-MIB::hrStorageSize.3 = INTEGER: 3660764 > HOST-RESOURCES-MIB::hrStorageSize.4 = INTEGER: 0 > HOST-RESOURCES-MIB::hrStorageSize.5 = INTEGER: 0 > HOST-RESOURCES-MIB::hrStorageSize.6 = INTEGER: 0 > HOST-RESOURCES-MIB::hrStorageSize.7 = INTEGER: 253871 > HOST-RESOURCES-MIB::hrStorageSize.8 = INTEGER: 3660780 > HOST-RESOURCES-MIB::hrStorageSize.9 = INTEGER: 12544916 > HOST-RESOURCES-MIB::hrStorageSize.10 = INTEGER: 502120 > HOST-RESOURCES-MIB::hrStorageSize.11 = INTEGER: 0 > HOST-RESOURCES-MIB::hrStorageSize.12 = INTEGER: 32768 > HOST-RESOURCES-MIB::hrStorageSize.13 = INTEGER: 32768 > HOST-RESOURCES-MIB::hrStorageSize.14 = INTEGER: 32768 > HOST-RESOURCES-MIB::hrStorageSize.15 = INTEGER: 32768 > HOST-RESOURCES-MIB::hrStorageSize.16 = INTEGER: 32768 > HOST-RESOURCES-MIB::hrStorageSize.17 = INTEGER: 32768 > [root@xymon disk]# > > [root@xymon disk]# snmpwalk -v2c -cpublic MY.CISCO.TARGET > .1.3.6.1.2.1.25.2.3.1.6 HOST-RESOURCES-MIB::hrStorageUsed.1 = INTEGER: > 683687 > HOST-RESOURCES-MIB::hrStorageUsed.2 = INTEGER: 192 > HOST-RESOURCES-MIB::hrStorageUsed.3 = INTEGER: 3013226 > HOST-RESOURCES-MIB::hrStorageUsed.4 = INTEGER: 0 > HOST-RESOURCES-MIB::hrStorageUsed.5 = INTEGER: 0 > HOST-RESOURCES-MIB::hrStorageUsed.6 = INTEGER: 0 > HOST-RESOURCES-MIB::hrStorageUsed.7 = INTEGER: 10479 > HOST-RESOURCES-MIB::hrStorageUsed.8 = INTEGER: 2959094 > HOST-RESOURCES-MIB::hrStorageUsed.9 = INTEGER: 8579106 > HOST-RESOURCES-MIB::hrStorageUsed.10 = INTEGER: 19872 > HOST-RESOURCES-MIB::hrStorageUsed.11 = INTEGER: 0 > HOST-RESOURCES-MIB::hrStorageUsed.12 = INTEGER: 13 > HOST-RESOURCES-MIB::hrStorageUsed.13 = INTEGER: 329 > HOST-RESOURCES-MIB::hrStorageUsed.14 = INTEGER: 426 > HOST-RESOURCES-MIB::hrStorageUsed.15 = INTEGER: 0 > HOST-RESOURCES-MIB::hrStorageUsed.16 = INTEGER: 32 > HOST-RESOURCES-MIB::hrStorageUsed.17 = INTEGER: 480 > [root@xymon disk]# > > > [root@xymon disk]# snmpwalk -v2c -cpublic MY.CISCO.TARGET > .1.3.6.1.2.1.25.2.3.1.4 HOST-RESOURCES-MIB::hrStorageAllocationUnits.1 = > INTEGER: 4096 Bytes HOST-RESOURCES-MIB::hrStorageAllocationUnits.2 = > INTEGER: 4096 Bytes HOST-RESOURCES-MIB::hrStorageAllocationUnits.3 = > INTEGER: 4096 Bytes HOST-RESOURCES-MIB::hrStorageAllocationUnits.4 = > INTEGER: 4096 Bytes HOST-RESOURCES-MIB::hrStorageAllocationUnits.5 = > INTEGER: 4096 Bytes HOST-RESOURCES-MIB::hrStorageAllocationUnits.6 = > INTEGER: 4096 Bytes HOST-RESOURCES-MIB::hrStorageAllocationUnits.7 = > INTEGER: 1024 Bytes HOST-RESOURCES-MIB::hrStorageAllocationUnits.8 = > INTEGER: 4096 Bytes HOST-RESOURCES-MIB::hrStorageAllocationUnits.9 = > INTEGER: 4096 Bytes HOST-RESOURCES-MIB::hrStorageAllocationUnits.10 = > INTEGER: 4096 Bytes HOST-RESOURCES-MIB::hrStorageAllocationUnits.11 = > INTEGER: 4096 Bytes HOST-RESOURCES-MIB::hrStorageAllocationUnits.12 = > INTEGER: 4096 Bytes HOST-RESOURCES-MIB::hrStorageAllocationUnits.13 = > INTEGER: 4096 Bytes HOST-RESOURCES-MIB::hrStorageAllocationUnits.14 = > INTEGER: 4096 Bytes HOST-RESOURCES-MIB::hrStorageAllocationUnits.15 = > INTEGER: 4096 Bytes HOST-RESOURCES-MIB::hrStorageAllocationUnits.16 = > INTEGER: 4096 Bytes HOST-RESOURCES-MIB::hrStorageAllocationUnits.17 = > INTEGER: 4096 Bytes [root@xymon disk]# > > For me, this makes me think that the snmp mechanisms do what they should > do. > > But if I now start the devmon processes, I receive messages like this in > the devmon.log: No SNMP data found for DiskName on MY.CISCO.TARGET Note that, unless you are using the version in svn, this message could be due to other SNMP oids which could not be retrieved, and as such, Devmon gave up on polling the OID. I would suggest you enable on test at a time, or upgrade to the version from svn. (Yes, I really do need to try and find time to finalise any outstanding changes and do a new release). > > The Xymon page that contains my Cisco target displays the "disk" column. > That means that devmon could identify my Cisco target as linux-netsnmp. > But when clicking on the disk-column, I get also the message > > Missing repeater data for primary OID DiskName > and the test itself remains "clear" (=no data). > > This happens not only for the "disk" test, but also for the tests "diskio", > "processes" and "temp". The MIBs for diskio and temp are specific to net-snmp, I would recommend you disable these tests first (or, make a new template for CUCM, and leave these test out). processes is standard-based, but maybe the CUCM doesn't support the data for it. > For any reason I cannot understand the mechanism > does work for the "memory" test. > > The fact, that in the file > <path-to-devmon>/templates/linux-netsnmp/disk/oids the parameter is called > DiskName and not hrStorageDescr (or whatever for the other values) > shouldn't / doesn't matter, because these are only variables that are > filled with the values coming from the snmp values. If I simply change the > parameter DiskName in the oids file to hrStorageDescr, then I get the > message > > Missing repeater data for primary OID hrStorageDescr > in the devmon.log file. So this shouldn't be the reason. This template works fine for real linux servers running net-snmp, except possibly the temp test (if the net-snmp agent isn't built with lmsensors support). Regards, Buchan |
