Michel Geldenhuys writes:

I discussed this few weeks ago with a NetApp engineer. Unfortunately, this is a "by-design" behaviour: MIB values are loaded during boot and in a random fashion so there is no way to forecast (or enforce) what MIB index will be for a particular volume.

The interesting thing about this is that the behaviour changed in ONTAP 6.3 and beyond. ONTAP 6.2 had the volumes sorted so they always appeared in the same order for both a "df" and for SNMP. Does anyone know _why_ they changed it?

+----------------------------------------------+-----------------------+ | Carl Richard Friend (UNIX Sysadmin) | Natick, Massachusetts | | Minicomputer Collector / Enthusiast | 01760-2098 | | mailto:carl_friend@mathworks.com +-----------------------+ | http://users.rcn.com/crfriend/museum | ICBM: 42:18N 71:21W | +----------------------------------------------+-----------------------+