Sorry, It has no bearing on SNMP alerts. SNMP alerts are triggered via pre-defined MIB, which are defined @ 95 & 98 % for nearlyfull & full condition. Is it working for you and if yes, could you share the screenshots and SNMP alert viewer.
What you used to to with the 7 mode commands you provided. is to have ONTAP monitoring it's own SNMP OID, and triggers an SNMP trap when an "edge" hit's on the configured OID parameter.
The MIB was not involved in this process and don't provide (in Cdot and 7mode) individual volume threshold related OID. (it does have 2-3 global system OID indicating if any volume or aggr hit hardcoded 98/95% and that's indeed not seems configurable)
Thanks for the reply. I did figure out the event notification command for setting the trap destination and using filter but even though I am able to see the event in the history but did not trigger a trap to the traphost, not sure what to do next.
Are you able to test it on your lab and share the screenshot. Basically, I need to trigger a trap for a spcific set of volumes at customized values.
SNMP organises information about a system into a OID-addressed MIB. This MIB can be walked by SNMP software using the appropriate community string.
The user-defined SNMP traps in older versions of ONTAP would enable traps to be sent to a management host when certain conditions on data in that MIB were met, so as a push operation, vs the pull of a walk.
This functionality was not widely used in ONTAP, and in clustered ONTAP, it is not present, as management paragdims aim for simple appliances with external monitoring, using our free OnCommand Unified Manager software, or the software of your choice walking SNMP or using ZAPI to poll.
Thanks Alex for providing info around 'user-defined-traps', so as I understand, in cDOT it's the Management monitoring application such as OCUM/Nimsoft etc, pulling it at certain intervals rather then ONTAP pushing it when the thresholds are met. Does that mean, if the Pull is set every hour, and the vol reaches nearly-full threshold , it wiill not be sent out, instead it will be pulled when the polling is scheduled?
Further, I would get confirmation on if this is set up correctly.
Each volume by default is set 95 & 98 % for nearly & full condition. I have modified one volume to customized threhold.
Is it correct in understanding that - When the volume space full threshold settings are breached, there will be a TRAP on the monitoring software such as OCUM/Nimsoft etc and this will over-ride the gobal thresholds for the volume specifically configured for these values.
The "pull" of a walk is more commonly done every 5 minutes or so, not hourly, meaning the interval for finding an almost full volume is reduced significantly.
While the commands listed look correct, I do not have an environment where I can test them. While it sounds appealing for the array to notify you directly, I advise against it - as the commands are marked as deprecated, they are likely to be removed in future versions of ONTAP as they do not fit the management paragdim we are aiming for.
This has further confused me, you said - The commands are marked as deprecated, they are likely to be removed in future versions of ONTAP as they do not fit the management paragdim we are aiming for.
Which commands specifically you are talking about ? The 'event notification & event filter' commands are available on 9.2 version so thats pretty recent one.
What I want to achieve is - Instead of volumes being trapped at 95 % NF* & 98 % F* volume as per the Global MIB values,I would like the trap to be generated at lower threshold values for some of the KEY volumes we have.
Gidi has suggested to modify the values per volume basis for the thresholds, will that work automatically ? In a nutshell : If I modify a single volume's NF* & F *values, will the SNMP PULL pick it up or do I need to create a separte 'event notification and filter' as mentioned in my previous post.