<?xml version="1.0" encoding="UTF-8"?>
<rss xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/" version="2.0">
  <channel>
    <title>topic Re: Is NetApp DFM capable of alerting on “interface down” or “SAS channel down&amp;quot;? in Active IQ Unified Manager Discussions</title>
    <link>https://community.netapp.com/t5/Active-IQ-Unified-Manager-Discussions/Is-NetApp-DFM-capable-of-alerting-on-interface-down-or-SAS-channel-down-quot/m-p/80599#M16773</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Thanks Craig - I've asked the customer to try this and report back. I'll post an update when I get one.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Cheers annd thanks,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Tony&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Fri, 26 Apr 2013 16:11:13 GMT</pubDate>
    <dc:creator>tguntrip</dc:creator>
    <dc:date>2013-04-26T16:11:13Z</dc:date>
    <item>
      <title>Is NetApp DFM capable of alerting on “interface down” or “SAS channel down"?</title>
      <link>https://community.netapp.com/t5/Active-IQ-Unified-Manager-Discussions/Is-NetApp-DFM-capable-of-alerting-on-interface-down-or-SAS-channel-down-quot/m-p/80590#M16769</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;&lt;SPAN style="color: #000000;"&gt;Hi,&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN style="color: #000000; font-family: arial,helvetica,sans-serif;"&gt;Query from my customer; support haven't been able to assist.&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN style="color: #0000ff; font-family: arial,helvetica,sans-serif;"&gt;Is NetApp DFM capable of alerting on “interface down” or “SAS channel down”.&amp;nbsp; If it is – then we have an issue:&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P style="text-indent: 36pt;"&gt;&lt;SPAN style="color: #0000ff; font-family: arial,helvetica,sans-serif;"&gt;Specifically - Unplugging a network cable or SAS cable does not get recognised in DFM. We have waited a number of hours AND change the monitoring time to 1 minute.&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN style="color: #0000ff; font-family: arial,helvetica,sans-serif;"&gt;I have seen events (I think triggered on DFM start-up):&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN style="font-family: arial,helvetica,sans-serif; color: #0000ff;"&gt;&lt;EM&gt;An Error event at 30 Jan 16:57 GMT Standard Time on interface e0c on Active/Active Controller controller.local: &lt;/EM&gt;&lt;EM&gt;Interface Status Down.&lt;/EM&gt;&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN style="color: #0000ff; font-family: arial,helvetica,sans-serif;"&gt;DFM – 5.02.7873&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN style="font-family: arial,helvetica,sans-serif; color: #0000ff;"&gt;DOT - 8.0.2 7-Mode&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN style="color: #000000;"&gt;Anything else we can try?&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN style="color: #000000;"&gt;Thanks,&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN style="color: #000000;"&gt;Tony&lt;/SPAN&gt;&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Thu, 05 Jun 2025 06:04:12 GMT</pubDate>
      <guid>https://community.netapp.com/t5/Active-IQ-Unified-Manager-Discussions/Is-NetApp-DFM-capable-of-alerting-on-interface-down-or-SAS-channel-down-quot/m-p/80590#M16769</guid>
      <dc:creator>tguntrip</dc:creator>
      <dc:date>2025-06-05T06:04:12Z</dc:date>
    </item>
    <item>
      <title>Re: Is NetApp DFM capable of alerting on “interface down” or “SAS channel down"?</title>
      <link>https://community.netapp.com/t5/Active-IQ-Unified-Manager-Discussions/Is-NetApp-DFM-capable-of-alerting-on-interface-down-or-SAS-channel-down-quot/m-p/80595#M16771</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi Tony,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Hope you are well. &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Can you check if the filer(s) are set to send SNMP traps to the DFM server?&amp;nbsp; Check the output of the 'snmp' command on the filer(s).&amp;nbsp; Traphost should include the hostname or ip of the DFM server and 'init' should be set to '1'.&amp;nbsp; If not...&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;snmp traphost add &amp;lt;&lt;EM&gt;hostname &lt;/EM&gt;| &lt;EM&gt;IP address&lt;/EM&gt;&amp;gt;&lt;/P&gt;&lt;P&gt;snmp init 1&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;...should do the trick.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Regards,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Craig&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Fri, 26 Apr 2013 12:39:40 GMT</pubDate>
      <guid>https://community.netapp.com/t5/Active-IQ-Unified-Manager-Discussions/Is-NetApp-DFM-capable-of-alerting-on-interface-down-or-SAS-channel-down-quot/m-p/80595#M16771</guid>
      <dc:creator>GARDINEC_EBRD</dc:creator>
      <dc:date>2013-04-26T12:39:40Z</dc:date>
    </item>
    <item>
      <title>Re: Is NetApp DFM capable of alerting on “interface down” or “SAS channel down"?</title>
      <link>https://community.netapp.com/t5/Active-IQ-Unified-Manager-Discussions/Is-NetApp-DFM-capable-of-alerting-on-interface-down-or-SAS-channel-down-quot/m-p/80599#M16773</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Thanks Craig - I've asked the customer to try this and report back. I'll post an update when I get one.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Cheers annd thanks,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Tony&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Fri, 26 Apr 2013 16:11:13 GMT</pubDate>
      <guid>https://community.netapp.com/t5/Active-IQ-Unified-Manager-Discussions/Is-NetApp-DFM-capable-of-alerting-on-interface-down-or-SAS-channel-down-quot/m-p/80599#M16773</guid>
      <dc:creator>tguntrip</dc:creator>
      <dc:date>2013-04-26T16:11:13Z</dc:date>
    </item>
    <item>
      <title>Re: Is NetApp DFM capable of alerting on “interface down” or “SAS channel down"?</title>
      <link>https://community.netapp.com/t5/Active-IQ-Unified-Manager-Discussions/Is-NetApp-DFM-capable-of-alerting-on-interface-down-or-SAS-channel-down-quot/m-p/80603#M16775</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi Craig,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;That made no difference, I'm afraid. Does anyone else have any other ideas?&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Thanks all,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Tony&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Fri, 24 May 2013 12:49:27 GMT</pubDate>
      <guid>https://community.netapp.com/t5/Active-IQ-Unified-Manager-Discussions/Is-NetApp-DFM-capable-of-alerting-on-interface-down-or-SAS-channel-down-quot/m-p/80603#M16775</guid>
      <dc:creator>tguntrip</dc:creator>
      <dc:date>2013-05-24T12:49:27Z</dc:date>
    </item>
    <item>
      <title>Re: Is NetApp DFM capable of alerting on “interface down” or “SAS channel down"?</title>
      <link>https://community.netapp.com/t5/Active-IQ-Unified-Manager-Discussions/Is-NetApp-DFM-capable-of-alerting-on-interface-down-or-SAS-channel-down-quot/m-p/80609#M16777</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;DFM/UM cannot alert on a link break, although I am not sure that is causing your lack of alerts.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Check the&amp;nbsp; evevnttype list for any events that&amp;nbsp; might be useful in logging an event, which are mandatory for generating an alert/triggering an alarm. I do not recall any SAS specific events but do not have CLI access at the moment.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Fri, 24 May 2013 13:06:56 GMT</pubDate>
      <guid>https://community.netapp.com/t5/Active-IQ-Unified-Manager-Discussions/Is-NetApp-DFM-capable-of-alerting-on-interface-down-or-SAS-channel-down-quot/m-p/80609#M16777</guid>
      <dc:creator>kryan</dc:creator>
      <dc:date>2013-05-24T13:06:56Z</dc:date>
    </item>
    <item>
      <title>Re: Is NetApp DFM capable of alerting on “interface down” or “SAS channel down"?</title>
      <link>https://community.netapp.com/t5/Active-IQ-Unified-Manager-Discussions/Is-NetApp-DFM-capable-of-alerting-on-interface-down-or-SAS-channel-down-quot/m-p/80613#M16779</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi Tony,&lt;/P&gt;&lt;P&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; Can you check if there is TRAP defined for the same ? If so then Craigs suggestion of enabled DFM host as trap receiver should get you this event. &lt;/P&gt;&lt;P&gt;The only down side is that all event raised for traps are of the severity Information and they dont show up in the events report. &lt;/P&gt;&lt;P&gt;Pls use events-history report to view the same or change the trap severity to make it show up in the normal report.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN style="color: #002060;"&gt;The default event severity definition in OCUM for Traps is Information. But the same can be modified.&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN style="color: #002060;"&gt;Default Severity Definition for all trap events is Information :&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN style="color: #002060;"&gt;+++++++++++++++++++++++++++++++++++++++++++++++++&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN style="color: #002060;"&gt;C:\&amp;gt;dfm eventtype list | findstr /i trap-received&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN style="color: #002060;"&gt;alert-trap-received&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; Information&amp;nbsp; alert-trap-received&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN style="color: #002060;"&gt;critical-trap-received&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; Information&amp;nbsp; critical-trap-received&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN style="color: #002060;"&gt;emergency-trap-received&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; Information&amp;nbsp; emergency-trap-received&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN style="color: #002060;"&gt;error-trap-received&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; Information&amp;nbsp; error-trap-received&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN style="color: #002060;"&gt;information-trap-received&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; Information&amp;nbsp; information-trap-received&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN style="color: #002060;"&gt;notification-trap-received&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; Information&amp;nbsp; notification-trap-received&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN style="color: #002060;"&gt;warning-trap-received&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; Information&amp;nbsp; warning-trap-received&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN style="color: #002060;"&gt;C:\&amp;gt;&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN style="color: #002060;"&gt;Modify them as follows:&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN style="color: #002060;"&gt;++++++++++++++++++++&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN style="color: #002060;"&gt;C:\&amp;gt;dfm eventtype modify -v Warning alert-trap-received&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN style="color: #002060;"&gt;Modified event "alert-trap-received".&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN style="color: #002060;"&gt;C:\&amp;gt;dfm eventtype modify -v Critical critical-trap-received&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN style="color: #002060;"&gt;Modified event "critical-trap-received".&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN style="color: #002060;"&gt;C:\&amp;gt;dfm eventtype modify -v Emergency emergency-trap-received&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN style="color: #002060;"&gt;Modified event "emergency-trap-received".&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN style="color: #002060;"&gt;C:\&amp;gt;dfm eventtype modify -v Error error-trap-received&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN style="color: #002060;"&gt;Modified event "error-trap-received".&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN style="color: #002060;"&gt;C:\&amp;gt;dfm eventtype modify -v Warning warning-trap-received&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN style="color: #002060;"&gt;Modified event "warning-trap-received".&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN style="color: #002060;"&gt;C:\&amp;gt;&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN style="color: #002060;"&gt;Now you will receive the trap with appropriate severity:&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN style="color: #002060;"&gt;++++++++++++++++++++++++++++++++++++++++++++++++&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN style="color: #002060;"&gt;C:\&amp;gt;dfm eventtype list | findstr /i trap-received&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN style="color: #002060;"&gt;alert-trap-received&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; Warning&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; alert-trap-received&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN style="color: #002060;"&gt;critical-trap-received&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; Critical&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; critical-trap-received&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN style="color: #002060;"&gt;emergency-trap-received&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; Emergency&amp;nbsp;&amp;nbsp;&amp;nbsp; emergency-trap-received&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN style="color: #002060;"&gt;error-trap-received&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; Error&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; error-trap-received&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN style="color: #002060;"&gt;information-trap-received&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; Information&amp;nbsp; information-trap-received&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN style="color: #002060;"&gt;notification-trap-received&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; Information&amp;nbsp; notification-trap-received&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN style="color: #002060;"&gt;warning-trap-received&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; Warning&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; warning-trap-received&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN style="color: #002060;"&gt;The drawback or side effect:&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN style="color: #002060;"&gt;======================&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN style="color: #002060;"&gt;When a trap other than information severity is generated the object status of the filer changes from green to orange, yellow or red.&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN style="color: #002060;"&gt;And even when the condition is rectified the object status doesn’t return back to green as there is no neutralization event.&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN style="color: #002060;"&gt;Now to overcome and make the object status green resolve the event by clicking on the resolve now.&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Regards&lt;/P&gt;&lt;P&gt;adai&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Fri, 24 May 2013 13:17:20 GMT</pubDate>
      <guid>https://community.netapp.com/t5/Active-IQ-Unified-Manager-Discussions/Is-NetApp-DFM-capable-of-alerting-on-interface-down-or-SAS-channel-down-quot/m-p/80613#M16779</guid>
      <dc:creator>adaikkap</dc:creator>
      <dc:date>2013-05-24T13:17:20Z</dc:date>
    </item>
    <item>
      <title>Re: Is NetApp DFM capable of alerting on “interface down” or “SAS channel down"?</title>
      <link>https://community.netapp.com/t5/Active-IQ-Unified-Manager-Discussions/Is-NetApp-DFM-capable-of-alerting-on-interface-down-or-SAS-channel-down-quot/m-p/80618#M16781</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;This has bitten me before and I never found a solution in DFM either. I eventually wrote a Perl script run that scans the filer message log every 15 minutes and sends me an email if it sees (among other things):&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;netif.linkUp&lt;/P&gt;&lt;P&gt;netif.linkDown&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;So if a link goes down, I get an email that says something like this:&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Fri Mar 29 12:09:45 EDT [&amp;lt;filer name&amp;gt;: netif.linkDown:info]: Ethernet c0a: Link down, check cable.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Fri, 24 May 2013 13:18:01 GMT</pubDate>
      <guid>https://community.netapp.com/t5/Active-IQ-Unified-Manager-Discussions/Is-NetApp-DFM-capable-of-alerting-on-interface-down-or-SAS-channel-down-quot/m-p/80618#M16781</guid>
      <dc:creator>MROSENKRANZEBSCO</dc:creator>
      <dc:date>2013-05-24T13:18:01Z</dc:date>
    </item>
    <item>
      <title>Re: Is NetApp DFM capable of alerting on “interface down” or “SAS channel down"?</title>
      <link>https://community.netapp.com/t5/Active-IQ-Unified-Manager-Discussions/Is-NetApp-DFM-capable-of-alerting-on-interface-down-or-SAS-channel-down-quot/m-p/80623#M16782</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;I still guess there is no option to monitor a Nic Port going down. Can someone please let us know if there is any alarm to monitor the same. &lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Mon, 12 May 2014 18:59:04 GMT</pubDate>
      <guid>https://community.netapp.com/t5/Active-IQ-Unified-Manager-Discussions/Is-NetApp-DFM-capable-of-alerting-on-interface-down-or-SAS-channel-down-quot/m-p/80623#M16782</guid>
      <dc:creator>SATISH_WALMART</dc:creator>
      <dc:date>2014-05-12T18:59:04Z</dc:date>
    </item>
  </channel>
</rss>

