2011-05-12 12:09 PM
Maybe you can try the following.
Acknowledge the event when it first appears on the that filer, and then delete the event. This should remove the event and prevent it from further appearing.
I'm not sure if this is a clean way, but it does seem to work.
But if you don't want to see this event at all for some particular filer(s), not even for the first time, this is not possible I think.
Anyone has any other idea?
2011-05-13 02:43 AM
There is no way today in DFM to disable a particular event or monitor for a specific filer.
Though disabling complete monitoring of specific filer/vfiler can be done.(ie ignored.)
As suggested by kjag, changing the severity of the event is one way, but it affect globally on all filers and not just the one you like to.
As said by sinhaa, you will get this event only once, as we keep generating such events only when the state changes, from up to down or vice versa.Ack for the first time and forget.
Third, way is to delete the filer or vfiler from dfm using dfm filer delete or dfm vfiler delete cli.
But this will stop monitoring for the entire filer or vfiler, all events and even discovery of new volumes or qtrees on those filer or vfiler.
Hope now you know when to use what.
If you would like to ignore false alerts from a filer/vfiler which is scheduled for maintenance, then go with third approach.
Once maintenance is over re-add the filer/vfiler using dfm filer add or vfiler add.Untill its readded no events /discovery happens for that filer/vfiler.
2011-05-13 03:50 AM
For vfilers, this is possible without any of the of the above 3 ways.
If you setup your vfiler using Provisioning Mgr and select the allowed protocols ( NFS, CIFS or iSCSI) as you wish, then in this case you won't get any warning events due to the unallowed protocol/service down which you didn't select.