<?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: Configure EMS events for all hardware/software related faults in ONTAP Discussions</title>
    <link>https://community.netapp.com/t5/ONTAP-Discussions/Configure-EMS-events-for-all-hardware-software-related-faults/m-p/150572#M33501</link>
    <description>&lt;P&gt;From the CLI, look at the command: &lt;FONT face="courier new,courier"&gt;event route show&lt;/FONT&gt;&lt;/P&gt;
&lt;P&gt;That will list out all the events that ONTAP could alert on.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;&lt;A title="EMS Configuration Express Guide" href="https://library.netapp.com/ecm/ecm_download_file/ECMLP2496248" target="_self"&gt;Check out the&amp;nbsp;&lt;SPAN&gt;EMS Configuration Express Guide&lt;/SPAN&gt;&lt;/A&gt;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
    <pubDate>Thu, 29 Aug 2019 12:36:30 GMT</pubDate>
    <dc:creator>TMACMD</dc:creator>
    <dc:date>2019-08-29T12:36:30Z</dc:date>
    <item>
      <title>Configure EMS events for all hardware/software related faults</title>
      <link>https://community.netapp.com/t5/ONTAP-Discussions/Configure-EMS-events-for-all-hardware-software-related-faults/m-p/150567#M33499</link>
      <description>&lt;P&gt;Is there a single EMS event available which will monitor all hardware and software fault ? if this is not possible, what are the list of ems events we should configure so that all the faults will be reported promptly. There is very less information available in the documentations.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;We are running Ontap 9.5P6, Active IQ Unified Manager 9.6.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Thanks for your help in advance&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Wed, 04 Jun 2025 12:17:25 GMT</pubDate>
      <guid>https://community.netapp.com/t5/ONTAP-Discussions/Configure-EMS-events-for-all-hardware-software-related-faults/m-p/150567#M33499</guid>
      <dc:creator>Faslu</dc:creator>
      <dc:date>2025-06-04T12:17:25Z</dc:date>
    </item>
    <item>
      <title>Re: Configure EMS events for all hardware/software related faults</title>
      <link>https://community.netapp.com/t5/ONTAP-Discussions/Configure-EMS-events-for-all-hardware-software-related-faults/m-p/150572#M33501</link>
      <description>&lt;P&gt;From the CLI, look at the command: &lt;FONT face="courier new,courier"&gt;event route show&lt;/FONT&gt;&lt;/P&gt;
&lt;P&gt;That will list out all the events that ONTAP could alert on.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;&lt;A title="EMS Configuration Express Guide" href="https://library.netapp.com/ecm/ecm_download_file/ECMLP2496248" target="_self"&gt;Check out the&amp;nbsp;&lt;SPAN&gt;EMS Configuration Express Guide&lt;/SPAN&gt;&lt;/A&gt;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Thu, 29 Aug 2019 12:36:30 GMT</pubDate>
      <guid>https://community.netapp.com/t5/ONTAP-Discussions/Configure-EMS-events-for-all-hardware-software-related-faults/m-p/150572#M33501</guid>
      <dc:creator>TMACMD</dc:creator>
      <dc:date>2019-08-29T12:36:30Z</dc:date>
    </item>
    <item>
      <title>Re: Configure EMS events for all hardware/software related faults</title>
      <link>https://community.netapp.com/t5/ONTAP-Discussions/Configure-EMS-events-for-all-hardware-software-related-faults/m-p/150574#M33502</link>
      <description>&lt;P&gt;Thanks for the reply, "&lt;FONT style="background-color: #ffffff;"&gt;&amp;nbsp;event route show&lt;/FONT&gt;" displays more than 500 events.&lt;/P&gt;
&lt;P&gt;1. How do we know which ones important ones ?&lt;/P&gt;
&lt;P&gt;2. Configuring these many by one by one is huge task, does not make any sense. I read somewhere wilde cards(*) not accepted.&lt;/P&gt;
&lt;P&gt;3.&amp;nbsp; I have checked the express guide, the information provided in that is very little.It says to expecute the below command&lt;/P&gt;
&lt;P&gt;&lt;FONT style="background-color: #ffffff;"&gt;"event notification create -filter-name important-events -destinations storage_admins"&lt;BR /&gt;&lt;/FONT&gt;&lt;/P&gt;
&lt;P&gt;&lt;FONT style="background-color: #ffffff;"&gt;In the above command how do a user know what is being covered under '&lt;FONT style="background-color: #ffffff; box-sizing: border-box; color: #3e3e3e; font-family: &amp;amp;quot; source sans pro&amp;amp;quot;,&amp;amp;quot;lato&amp;amp;quot;,&amp;amp;quot;helvetica neue&amp;amp;quot;,&amp;amp;quot;helvetica&amp;amp;quot;,&amp;amp;quot;arial&amp;amp;quot;,&amp;amp;quot;sans-serif&amp;amp;quot;; font-size: 16px; font-style: normal; font-variant: normal; font-weight: 300; letter-spacing: normal; orphans: 2; text-align: left; text-decoration: none; text-indent: 0px; text-transform: none; -webkit-text-stroke-width: 0px; white-space: normal; word-spacing: 0px;"&gt;important-events &lt;/FONT&gt;' ?&lt;/FONT&gt;&lt;/P&gt;
&lt;P&gt;&lt;FONT style="background-color: #ffffff;"&gt;Thank you&lt;/FONT&gt;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Thu, 29 Aug 2019 13:08:01 GMT</pubDate>
      <guid>https://community.netapp.com/t5/ONTAP-Discussions/Configure-EMS-events-for-all-hardware-software-related-faults/m-p/150574#M33502</guid>
      <dc:creator>Faslu</dc:creator>
      <dc:date>2019-08-29T13:08:01Z</dc:date>
    </item>
    <item>
      <title>Re: Configure EMS events for all hardware/software related faults</title>
      <link>https://community.netapp.com/t5/ONTAP-Discussions/Configure-EMS-events-for-all-hardware-software-related-faults/m-p/150578#M33505</link>
      <description>&lt;P&gt;Actually, in ONTAP 9.6, there are ove 6800 event routes!&lt;/P&gt;
&lt;P&gt;the "event route" commands have been depricated and replaced by a few others. Going to use it as an example though.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;You could start by looking at&amp;nbsp;&lt;/P&gt;
&lt;P style="padding-left: 30px;"&gt;&lt;FONT face="courier new,courier"&gt;event route show -destinations asup&lt;/FONT&gt;&lt;/P&gt;
&lt;P&gt;which indicates what is at least alerted to ASUP. You can decide what is important to you there. (ONTAP 9.6 = 271)&lt;/P&gt;
&lt;P&gt;Then look at all the EMERGENCY routes:&lt;/P&gt;
&lt;P style="padding-left: 30px;"&gt;&lt;FONT face="courier new,courier"&gt;event route show -severity EMERGENCY&lt;/FONT&gt;&lt;/P&gt;
&lt;P&gt;These are the most critical. Again, you can choose what to look at. (ONTAP 9.6 = 246)&lt;/P&gt;
&lt;P&gt;You could even look at the overlap of the two&lt;/P&gt;
&lt;P style="padding-left: 30px;"&gt;&lt;FONT face="courier new,courier"&gt;event route show -severity EMERGENCY -destinations asup&lt;/FONT&gt;&lt;/P&gt;
&lt;P&gt;You would see the list is much shorter (ONTAP 9.6 = 28).&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Bottom line is this: You need to decide which are important to you as an ADMIN and your company to monitor.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Following the guide to setup email:&lt;/P&gt;
&lt;P&gt;Configure for the SMTP server&lt;/P&gt;
&lt;P&gt;&lt;FONT face="courier new,courier" size="2"&gt;event config modify -mail-server mailhost.your_domain -mail-from cluster_admin@your_domain&lt;/FONT&gt;&lt;/P&gt;
&lt;P&gt;Create a destination (email address)&lt;/P&gt;
&lt;P&gt;&lt;FONT face="courier new,courier" size="2"&gt;event notification destination create -name storage-admins -email your_email@your_domain&lt;/FONT&gt;&lt;/P&gt;
&lt;P&gt;Add the destination to the "important-events" filter&lt;/P&gt;
&lt;P&gt;&lt;FONT face="courier new,courier" size="2"&gt;event notification create -filter-name important-events -destinations storage_admins&amp;nbsp;&lt;/FONT&gt;&lt;/P&gt;
&lt;P&gt;See which events will be alerted on&lt;/P&gt;
&lt;P&gt;&lt;FONT face="courier new,courier" size="2"&gt;event filter show -filter-name important-events&lt;/FONT&gt;&lt;/P&gt;
&lt;P&gt;&lt;FONT face="courier new,courier" size="2"&gt;cluster1::*&amp;gt; event filter show -filter-name important-events&lt;/FONT&gt;&lt;BR /&gt;&lt;FONT face="courier new,courier" size="2"&gt;Filter Name Rule&amp;nbsp; &amp;nbsp; &amp;nbsp;Rule&amp;nbsp; &amp;nbsp; &amp;nbsp; Message Name&amp;nbsp; SNMP Trap Type&amp;nbsp; Severity&lt;/FONT&gt;&lt;BR /&gt;&lt;FONT face="courier new,courier" size="2"&gt;&amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; Position Type&lt;/FONT&gt;&lt;BR /&gt;&lt;FONT face="courier new,courier" size="2"&gt;----------- -------- --------- ------------- --------------- --------&lt;/FONT&gt;&lt;BR /&gt;&lt;FONT face="courier new,courier" size="2"&gt;important-events&lt;/FONT&gt;&lt;BR /&gt;&lt;FONT face="courier new,courier" size="2"&gt;&amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; 1&amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; include&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, ALERT&lt;/FONT&gt;&lt;BR /&gt;&lt;FONT face="courier new,courier" size="2"&gt;&amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; 2&amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; include&amp;nbsp; &amp;nbsp;callhome.*&amp;nbsp; &amp;nbsp; *&amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp;ERROR&lt;/FONT&gt;&lt;BR /&gt;&lt;FONT face="courier new,courier" size="2"&gt;&amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; 3&amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; exclude&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;*&lt;/FONT&gt;&lt;/P&gt;
&lt;P&gt;&lt;FONT face="courier new,courier" size="2"&gt;3 entries were displayed.&lt;/FONT&gt;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;So, any routes/events that are &lt;FONT color="#FF0000"&gt;Severity &lt;STRONG&gt;&lt;FONT face="courier new,courier"&gt;EMERGENCY&lt;/FONT&gt; &lt;/STRONG&gt;or &lt;STRONG&gt;&lt;FONT face="courier new,courier"&gt;ALERT&lt;/FONT&gt; &lt;/STRONG&gt;(rule #1)&lt;/FONT&gt; or that are &lt;FONT color="#0000FF"&gt;&lt;STRONG&gt;&lt;FONT face="courier new,courier"&gt;ERROR&lt;/FONT&gt; &lt;EM&gt;AND&lt;/EM&gt;&lt;/STRONG&gt;&lt;EM&gt; the message name begins with&lt;/EM&gt; "&lt;STRONG&gt;&lt;FONT face="courier new,courier"&gt;callhome.*&lt;/FONT&gt;&lt;/STRONG&gt;" (rule #2)&lt;/FONT&gt; will be sent&lt;/P&gt;</description>
      <pubDate>Thu, 29 Aug 2019 14:14:26 GMT</pubDate>
      <guid>https://community.netapp.com/t5/ONTAP-Discussions/Configure-EMS-events-for-all-hardware-software-related-faults/m-p/150578#M33505</guid>
      <dc:creator>TMACMD</dc:creator>
      <dc:date>2019-08-29T14:14:26Z</dc:date>
    </item>
    <item>
      <title>Re: Configure EMS events for all hardware/software related faults</title>
      <link>https://community.netapp.com/t5/ONTAP-Discussions/Configure-EMS-events-for-all-hardware-software-related-faults/m-p/150585#M33507</link>
      <description>&lt;P&gt;Thanks for the reply.&lt;/P&gt;
&lt;P&gt;Does the 3rd rule in the output of the command "&lt;SPAN style="display: inline !important; float: none; background-color: #ffffff; color: #3e3e3e; font-family: courier new,courier; font-size: 13.33px; font-style: normal; font-variant: normal; font-weight: 300; letter-spacing: normal; orphans: 2; text-align: justify; text-decoration: none; text-indent: 0px; text-transform: none; -webkit-text-stroke-width: 0px; white-space: normal; word-spacing: 0px;"&gt;event filter show -filter-name important-events&lt;/SPAN&gt;" exclude all events of all types, which means no events will be sent out ?&lt;/P&gt;
&lt;P&gt;&lt;SPAN style="display: inline !important; float: none; background-color: #ffffff; color: #3e3e3e; font-family: courier new,courier; font-size: 13.33px; font-style: normal; font-variant: normal; font-weight: 300; letter-spacing: normal; orphans: 2; text-align: justify; text-decoration: none; text-indent: 0px; text-transform: none; -webkit-text-stroke-width: 0px; white-space: normal; word-spacing: 0px;"&gt; &amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; 3&amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; exclude&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;*&lt;/SPAN&gt;&lt;/P&gt;</description>
      <pubDate>Thu, 29 Aug 2019 15:50:56 GMT</pubDate>
      <guid>https://community.netapp.com/t5/ONTAP-Discussions/Configure-EMS-events-for-all-hardware-software-related-faults/m-p/150585#M33507</guid>
      <dc:creator>Faslu</dc:creator>
      <dc:date>2019-08-29T15:50:56Z</dc:date>
    </item>
    <item>
      <title>Re: Configure EMS events for all hardware/software related faults</title>
      <link>https://community.netapp.com/t5/ONTAP-Discussions/Configure-EMS-events-for-all-hardware-software-related-faults/m-p/150586#M33508</link>
      <description>&lt;P&gt;No, it will include all the EMERGENCY/ALERT messages AND it will include all ERROR messages that start with callhome and then exclude everything else.&lt;/P&gt;</description>
      <pubDate>Thu, 29 Aug 2019 15:58:17 GMT</pubDate>
      <guid>https://community.netapp.com/t5/ONTAP-Discussions/Configure-EMS-events-for-all-hardware-software-related-faults/m-p/150586#M33508</guid>
      <dc:creator>TMACMD</dc:creator>
      <dc:date>2019-08-29T15:58:17Z</dc:date>
    </item>
  </channel>
</rss>

