Hi, I have been using snmpd to monitor disk activity on my storage machine (Debian 8, running mdadm raid6), for this, I've been using the "DiskIODevice" and "hrStorage" trees. This has been working like a charm except for one issue: The disk device index appears to change every reboot. So every time the storage server needs to reboot I have to rewrite the monitoring configuration on the statistics collector to keep the data accurate.
The layout of the system is as follows: /dev/sda up until /dev/sdf are the raid disks, holding two sets: /dev/md0 and /dev/md1. /dev/sdg is the boot device (USB flashdisk). For some reason the order in which /dev/sda to /dev/sdf, /dev/md0 and /dev/md1 are indexed changes every boot. The only disk that consistently gets the same index number is /dev/sdg. Note: the physical device paths do not change, port 1 on the disk controller will always map to /dev/sda, port 2 to /dev/sdb, etc. This detection is consistent in the system. For the hrStorage, the solution seems to be to use the dskTable tree and manually configure each filesystem in the snmpd config. However, this only seems to work for actual filesytems, not for individual disks. Is there a way to get a persistent index (or manually configured indexing) on the "DiskIODevice" trees? Kind regards, Rudi Daemen ------------------------------------------------------------------------------ Site24x7 APM Insight: Get Deep Visibility into Application Performance APM + Mobile APM + RUM: Monitor 3 App instances at just $35/Month Monitor end-to-end web transactions and take corrective actions now Troubleshoot faster and improve end-user experience. Signup Now! http://pubads.g.doubleclick.net/gampad/clk?id=267308311&iu=/4140 _______________________________________________ Net-snmp-users mailing list Net-snmp-users@lists.sourceforge.net Please see the following page to unsubscribe or change other options: https://lists.sourceforge.net/lists/listinfo/net-snmp-users
