1) NetApp makes a great product. The problem is that their initial MIB was created in the SNMP v1 days; when the concept of counters and gauges did not exist. Hence the use of integers in places were we would expect to see counters.

2) RRDTool, and by extension Cricket, is based upon SNMP v2; where the concept of Counters and Gauges were introduced.

3) Due to historic reasons, the SNMP community does not permit the modification of objects once they are cast in stone. [Made public] OID's can be depreciated, but cannot be modified or eliminated.

Note: This is were Network Appliance has fallen short. The INTEGER objects in the mib should have been declared historical long ago, and new objects created with a more appropriate object types.

4) The NetApp MIB is tightly tied to the OS release. Check the mib on the system being monitored. You may find that the SNMP v1 object you want to graph, may have been superseded by a SNMP v2 object.

I switched from 'miscNfsOps' to 'tnfsCalls' when I upgraded the OS on my filers earlier this year. (I'm running 5.3.4R3)

Benjamin Cooper wrote:

Wow, you people have been busy over the night. I didn't mean to turn this into such a huge thread.

Could someone send me a summary of what has been concluded? I have read all the messages, and as far as I can see this are what has been decided:

1. NetApp is stupid and really screwed up.
2. My graphs should work anyway.
3. Since they don't I have to resort to using the exec collector, and

munge the data myself.

Is that a valid summary? Can someone tell me exactly (technically) why it won't work the way I have it?

-- Benjamin Cooper UCSA I/S Group Hal Computer (408) 341-5135

---

cricket-users mailing list cricket-users@lists.sourceforge.net http://lists.sourceforge.net/mailman/listinfo/cricket-users

-- Matthew Lee Stier * Fujitsu Network Communications Unix Systems Administrator | Two Blue Hill Plaza Ph: 914-731-2097 Fx: 914-731-2011 | Sixth Floor Matthew.Stier@fnc.fujitsu.com * Pearl River, NY 10965