2018-06-01 07:40 AM
Can someone shed some light on this, what do you mean by that ?
User-defined traps are not supported in clustered Data ONTAP.
Unlike 7-mode, cDOT does not support user-defined traps. Does that mean, one cannot set SNMP trap for non-global threshold values ?
My intention is to - set the traps for Volume.full & volume.nearlyfull on per volume basis on cDOT filers and not follow global thresholds?
filer> snmp traps dfPerCentKBytesCapacity.edge-1 90
filer> snmp traps
active = off
OID = snmp.18.104.22.168.4.1.722.214.171.124.1.6.9
trigger = level-trigger
interval = 3600
edge-1 = 90 (up) <-- now we have a trigger at value of 90
current-value = 0
2018-06-01 07:34 PM
You can define custom thresholds on each volume. i assume SNMP following these settings.
2018-06-02 02:14 AM
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.
2018-06-05 08:20 AM - edited 2018-06-05 08:22 AM
in the following article it's says that ONTAP raises the EMS message with relation to the parameter i provided. and that you can set an SNMP trap for it
For setting the trap you will need to set the server in "event destination" and the relevant events touted to it in "event filter" and "event filter rule"
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)
2018-06-05 09:35 AM
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.
2018-06-05 10:16 AM
i don't think i have something ready to accept SNMP Traps in my environment.
What is your event settings looks like ? it can be very confusing with the 10 different objects and all the deprecated commands around "event".
also. is there a network connectivity from your node management lif to you snmp server ?
2018-06-05 11:27 AM
Even route destiantion and filter is set properly, and SNMP does have route to Node Mgmt LIF, I will do some investigation tomorrow and will update you on the result.
I am still eager to understand, what do you mena by - user-defined-traps ?
NetApp cDOT documentation states - user-defined-traps not supported, Is there an example of what are they ?
2018-06-05 08:37 PM
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.
I hope this clarifies what this feature was.
2018-06-06 07:19 AM
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.
nac01::*> event notification create -filter-name default-trap-events -destinations snmp-traphost
nac01::*> event filter rule add -filter-name default-trap-events -type include -message-name monitor.volume.nearlyFull -snmp-trap-type built-in -position 1 -severity INFORMATIONAL
nac01::*> volume show -vserver svm_cifs -volume NA01_CIFS -instance
Volume Nearly Full Threshold Percent: 95%
Volume Full Threshold Percent: 98%
nac01::*> volume modify -vserver svm_cifs -volume NA01_CIFS -space-full-threshold-percent 90 space-nearly-full-threshold-percent 85
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.
2018-06-06 03:19 PM
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.