Hello Toasterites,

I've come across some odd behaviour in the SNMP reporting of OnTap. I have a script that uses Net-SNMP to check for failures on our Filers. This came about due to disks slipping offline silently rather than failing. The script does 3 checks: the failed count OID, the number of spares OID, and an overall comparison of total disks, spare disks, and active disks. Every saturday night (when the INFO report mail is sent out) I get a run of my script generating errors. To isolate the problem I put some debugging into the script and found that I get back the following numbers for one of my Filers: Active Disks: 50 Spare Disks: 2 Total Disks: 56

Some how 4 disks disappeared from the SNMP reporting for that run... and it's gotta be the parity disks. The Filers run great, no problems there, it's just a simple reporting issue.

So the question: why? It's not a big issue, but it'd be nice to not get paged every saturday night for no reason, and I'd rather not have to work around this too in my script (which was written to work around a previous reporting issue, etc, etc).

Oh, and I'm running OnTap 6.1R1, on several 760 and 840s.

Ben Rockwood UNIX Systems Admin Homestead.com