William, You may like to try the "dfm eventtype" command from the command prompt. Check Appendix A of the the DFM manual for information on the event types. I am only looking at the 3.01 version so I don't see the CIFS event log full option, but I would say it is easily modified for 3.1

Basically, you can set and event to be reported as Informational, Warning, Error and in some cases Critical. The cmdref.pdf explains syntax as follows;

dfm eventtype modify [ -v event-severity ] event-name

My suggestions; 1) Choose the ones you are not so interested in and change them to Informational. Then when you check events, you can view only Warning or worse (for example). This won't necessarily keep your database size down. I have been running DFM for years and haven't seen my database get much larger than 400-500mb. I can see user quota monitoring making this blowout in a very large environment. Even then, I have never had a DFM database corrupt and have only heard about it once or twice. Check with NetApp, there is probably a way to groom old events from the database.

2) We use the "Alarms" to email the team when specific events are recorded by DFM. We can do this because we know exactly what we like to watch in our environment and want DFM to tell us about it rather than us having to go search for it. Because of this, we rarely go through the events list as an operational procedure. It is more used as a tool to help us identify a sequence of events that may have occurred leading up to another issue. i.e. A paper trail.

Hope this helps you out.

Regards, Aaron

-----Original Message----- From: Holland, William L [mailto:hollandwl@state.gov] Sent: Friday, 21 January 2005 6:09 AM To: 'toasters@mathworks.com' Subject: DFM 3.1 Events

Anyone found a way to stop DFM 3.1 from recording certain events? For instance, we have AutoSupport turned off due to security configuration policies. However, every few hours the filers dutifully report that AutoSupport is turned off and try to cajole me with all the benefits of turning it on. I know it's off, I purposefully turned it off, stop notifying me about it. I don't want to see this event in my DFM events. Another example is when CIFS event log is full and it creates another one - I get LOTS of these every day. I don't care about them. Only tell me if you couldn't create one. These two events alone spread across 3 filers, I have gathered approximately 1700 events in the week I've had DFM running. I don't want these events taking up space in my database, I don't want to filter through them every day looking to see if there is some event worth my paying attention to that I may not have yet established an alarm for. In short, by being inundated with informational events that I don't care about, the usefulness is being diluted.

************** IMPORTANT MESSAGE ************** This e-mail message is intended only for the addressee(s) and contains information which may be confidential. If you are not the intended recipient please advise the sender by return email, do not use or disclose the contents, and delete the message and any attachments from your system. Unless specifically indicated, this email does not constitute formal advice or commitment by the sender or the Commonwealth Bank of Australia (ABN 48 123 123 124) or its subsidiaries. We can be contacted through our web site: commbank.com.au. If you no longer wish to receive commercial electronic messages from us, please reply to this e-mail by typing Unsubscribe in the subject line. ***************************************************************