Yes. The output of df matches the SNMP OID index.
Filesystem total used avail capacity Mounted on /vol/vol1/ 2049GB 1640GB 409GB 80% /vol/vol1/ /vol/vol1/.snapshot 0GB 263GB 0GB ---% /vol/vol1/.snapshot /vol/vol7/ 1863GB 1203GB 659GB 65% /vol/vol7/ /vol/vol7/.snapshot 0MB 123MB 0MB ---% /vol/vol7/.snapshot /vol/vol6/ 1863GB 1470GB 393GB 79% /vol/vol6/ /vol/vol6/.snapshot 0MB 29MB 0MB ---% /vol/vol6/.snapshot /vol/vol2/ 1863GB 981GB 881GB 53% /vol/vol2/ /vol/vol2/.snapshot 0GB 181GB 0GB ---% /vol/vol2/.snapshot /vol/vol0/ 149GB 4315MB 144GB 3% /vol/vol0/ /vol/vol0/.snapshot 37GB 10MB 37GB 0% /vol/vol0/.snapshot /vol/vol5/ 884GB 700GB 184GB 79% /vol/vol5/ /vol/vol5/.snapshot 46GB 229MB 46GB 0% /vol/vol5/.snapshot /vol/vol4/ 2049GB 1648GB 401GB 80% /vol/vol4/ /vol/vol4/.snapshot 0GB 348GB 0GB ---% /vol/vol4/.snapshot /vol/vol3/ 931GB 846GB 84GB 91% /vol/vol3/ /vol/vol3/.snapshot 0GB 511GB 0GB ---% /vol/vol3/.snapshot
----- Original Message ----- From: "Chris Thompson" cet1@cus.cam.ac.uk To: "Michel GELDENHUYS" michel.geldenhuys@danone.com Cc: toasters@mathworks.com Sent: Friday, October 31, 2003 10:18 AM Subject: Re: SNMP values keeps changing after every reboot. any solution to fix this?
michel.geldenhuys@danone.com (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.
Do you know whether this is the same order that "df" (without
arguments)
shows the volumes? I have noticed that this changes unpredictably
after
a reboot. [That's in 6.3.3: I am fairly sure that once upon a time
it
used to list them in order of Volume-Id (as in the NFS filehandle),
and
so was consistent over a reboot.]
Chris Thompson Email: cet1@cam.ac.uk