Hi StoRage,
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. So it seems that there is no other way than manually modifying MRTG configuration file to take the changes into account.
When asked how Data Fabric Manager can handle this, the answer was that since it relies on a database, DFM is clever enough to update the index to check.
I hope this will help. Kind regards,
Michel Geldenhuys Danone Belgium SA/NV +32 2 776 68 23 michel.geldenhuys@danone.com
Sto Rage© Net_Backer@hotmail.com Sent by: owner-toasters@mathworks.com 10/31/2003 03:42 AM
To: toasters@mathworks.com cc: Subject: SNMP values keeps changing after every reboot. any solution to fix this?
Every time the filer is rebooted. the snmp values for disk changes. This affects our mrtg monitoring. Is there a script that helps overcome this issue? How are others monitoring disk usage using mrtg? TIA
After last reboot:
NETWORK-APPLIANCE-MIB::dfFileSys.1 = STRING: "/vol/vol1/" NETWORK-APPLIANCE-MIB::dfFileSys.2 = STRING: "/vol/vol1/.snapshot" NETWORK-APPLIANCE-MIB::dfFileSys.3 = STRING: "/vol/vol7/" NETWORK-APPLIANCE-MIB::dfFileSys.4 = STRING: "/vol/vol7/.snapshot" NETWORK-APPLIANCE-MIB::dfFileSys.5 = STRING: "/vol/vol6/" NETWORK-APPLIANCE-MIB::dfFileSys.6 = STRING: "/vol/vol6/.snapshot" NETWORK-APPLIANCE-MIB::dfFileSys.7 = STRING: "/vol/vol2/" NETWORK-APPLIANCE-MIB::dfFileSys.8 = STRING: "/vol/vol2/.snapshot" NETWORK-APPLIANCE-MIB::dfFileSys.9 = STRING: "/vol/vol0/" NETWORK-APPLIANCE-MIB::dfFileSys.10 = STRING: "/vol/vol0/.snapshot" NETWORK-APPLIANCE-MIB::dfFileSys.11 = STRING: "/vol/vol5/" NETWORK-APPLIANCE-MIB::dfFileSys.12 = STRING: "/vol/vol5/.snapshot" NETWORK-APPLIANCE-MIB::dfFileSys.13 = STRING: "/vol/vol4/" NETWORK-APPLIANCE-MIB::dfFileSys.14 = STRING: "/vol/vol4/.snapshot" NETWORK-APPLIANCE-MIB::dfFileSys.15 = STRING: "/vol/vol3/" NETWORK-APPLIANCE-MIB::dfFileSys.16 = STRING: "/vol/vol3/.snapshot"
Before the reboot: #NETWORK-APPLIANCE-MIB::dfFileSys.1 = STRING: "/vol/vol2/" #NETWORK-APPLIANCE-MIB::dfFileSys.2 = STRING: "/vol/vol2/.snapshot" #NETWORK-APPLIANCE-MIB::dfFileSys.3 = STRING: "/vol/vol1/" #NETWORK-APPLIANCE-MIB::dfFileSys.4 = STRING: "/vol/vol1/.snapshot" #NETWORK-APPLIANCE-MIB::dfFileSys.5 = STRING: "/vol/vol4/" #NETWORK-APPLIANCE-MIB::dfFileSys.6 = STRING: "/vol/vol4/.snapshot" #NETWORK-APPLIANCE-MIB::dfFileSys.7 = STRING: "/vol/vol6/" #NETWORK-APPLIANCE-MIB::dfFileSys.8 = STRING: "/vol/vol6/.snapshot" #NETWORK-APPLIANCE-MIB::dfFileSys.9 = STRING: "/vol/vol0/" #NETWORK-APPLIANCE-MIB::dfFileSys.10 = STRING: "/vol/vol0/.snapshot" #NETWORK-APPLIANCE-MIB::dfFileSys.11 = STRING: "/vol/vol5/" #NETWORK-APPLIANCE-MIB::dfFileSys.12 = STRING: "/vol/vol5/.snapshot" #NETWORK-APPLIANCE-MIB::dfFileSys.13 = STRING: "/vol/vol3/" #NETWORK-APPLIANCE-MIB::dfFileSys.14 = STRING: "/vol/vol3/.snapshot" #NETWORK-APPLIANCE-MIB::dfFileSys.15 = STRING: "/vol/vol7/" #NETWORK-APPLIANCE-MIB::dfFileSys.16 = STRING: "/vol/vol7/.snapshot"
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
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