<?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: ASUP CASES FOR BROCADE in Active IQ and AutoSupport Discussions</title>
    <link>https://community.netapp.com/t5/Active-IQ-and-AutoSupport-Discussions/ASUP-CASES-FOR-BROCADE/m-p/131161#M1405</link>
    <description>&lt;P&gt;Hi, I beleive there are only a couple of&amp;nbsp;EMS event that Brocade could trigger for ONTAP to send an AutoSupport:&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&lt;STRONG&gt;callhome.clus.net.degraded&lt;/STRONG&gt;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&lt;EM&gt;This message occurs when the cluster network has experienced an issue that could potentially affect connectivity, reliability, redundancy, or performance, as observed from the local node. A degraded cluster network might cause a cluster-wide outage. If your system is configured to do so, it generates and transmits an AutoSupport (or 'call home') message to NetApp technical support and to the configured destinations. Successful delivery of an AutoSupport message significantly improves problem determination and resolution.&lt;/EM&gt;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&lt;STRONG&gt;callhome.fc.al.link&lt;/STRONG&gt;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&lt;EM&gt;This message occurs when a Fibre Channel arbitrated loop (FC-AL) has link failures. You need to resolve this issue promptly. If your system is configured to do so, it generates and transmits an AutoSupport (or 'call home') message to NetApp technical support and to the configured destinations. Successful delivery of an AutoSupport message significantly improves problem determination and resolution.&lt;/EM&gt;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&lt;STRONG&gt;callhome.fc.al.poor&lt;/STRONG&gt;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&lt;EM&gt;This message occurs when the system detects that a Fibre Channel arbitrated loop (FC-AL) is unreliable or is too poor in quality for data exchange. You need to resolve this issue promptly. The link errors are recoverable in the sense that the system is up and running. If your system is configured to do so, it generates and transmits an AutoSupport (or 'call home') message to NetApp technical support and to the configured destinations. Successful delivery of an AutoSupport message significantly improves problem determination and resolution.&lt;/EM&gt;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;For details please see page 74 onwards&amp;nbsp;of the ONTAP 9 EMS Event Catalog: &lt;A href="https://library.netapp.com/ecm/ecm_get_file/ECMLP2597302" target="_blank"&gt;https://library.netapp.com/ecm/ecm_get_file/ECMLP2597302&lt;/A&gt;. All EMS events that can trigger an ASUP are in the&amp;nbsp;"callhome" Event Group.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Hope you find the info useful.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
    <pubDate>Thu, 18 May 2017 13:24:16 GMT</pubDate>
    <dc:creator>sgrant</dc:creator>
    <dc:date>2017-05-18T13:24:16Z</dc:date>
    <item>
      <title>ASUP CASES FOR BROCADE</title>
      <link>https://community.netapp.com/t5/Active-IQ-and-AutoSupport-Discussions/ASUP-CASES-FOR-BROCADE/m-p/130928#M1404</link>
      <description>&lt;P&gt;Which event types will trigger an auto generated NetApp case for Brocade Switches?&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;List of alerts that will generate an ASUP call home. These events can be categorized into three sections&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;UL&gt;&lt;LI&gt;CONSRV Events&lt;/LI&gt;&lt;LI&gt;Thermal Events&lt;/LI&gt;&lt;LI&gt;Fabric Events&lt;/LI&gt;&lt;/UL&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Refer to page 1575 of the following document &lt;A href="https://www.brocade.com/content/dam/common/documents/content-types/user-guide/networkadvisor-1243-san-manual.pdf" target="_blank"&gt;https://www.brocade.com/content/dam/common/documents/content-types/user-guide/networkadvisor-1243-san-manual.pdf&lt;/A&gt;&lt;/P&gt;</description>
      <pubDate>Wed, 04 Jun 2025 15:06:17 GMT</pubDate>
      <guid>https://community.netapp.com/t5/Active-IQ-and-AutoSupport-Discussions/ASUP-CASES-FOR-BROCADE/m-p/130928#M1404</guid>
      <dc:creator>Debbrata</dc:creator>
      <dc:date>2025-06-04T15:06:17Z</dc:date>
    </item>
    <item>
      <title>Re: ASUP CASES FOR BROCADE</title>
      <link>https://community.netapp.com/t5/Active-IQ-and-AutoSupport-Discussions/ASUP-CASES-FOR-BROCADE/m-p/131161#M1405</link>
      <description>&lt;P&gt;Hi, I beleive there are only a couple of&amp;nbsp;EMS event that Brocade could trigger for ONTAP to send an AutoSupport:&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&lt;STRONG&gt;callhome.clus.net.degraded&lt;/STRONG&gt;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&lt;EM&gt;This message occurs when the cluster network has experienced an issue that could potentially affect connectivity, reliability, redundancy, or performance, as observed from the local node. A degraded cluster network might cause a cluster-wide outage. If your system is configured to do so, it generates and transmits an AutoSupport (or 'call home') message to NetApp technical support and to the configured destinations. Successful delivery of an AutoSupport message significantly improves problem determination and resolution.&lt;/EM&gt;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&lt;STRONG&gt;callhome.fc.al.link&lt;/STRONG&gt;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&lt;EM&gt;This message occurs when a Fibre Channel arbitrated loop (FC-AL) has link failures. You need to resolve this issue promptly. If your system is configured to do so, it generates and transmits an AutoSupport (or 'call home') message to NetApp technical support and to the configured destinations. Successful delivery of an AutoSupport message significantly improves problem determination and resolution.&lt;/EM&gt;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&lt;STRONG&gt;callhome.fc.al.poor&lt;/STRONG&gt;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&lt;EM&gt;This message occurs when the system detects that a Fibre Channel arbitrated loop (FC-AL) is unreliable or is too poor in quality for data exchange. You need to resolve this issue promptly. The link errors are recoverable in the sense that the system is up and running. If your system is configured to do so, it generates and transmits an AutoSupport (or 'call home') message to NetApp technical support and to the configured destinations. Successful delivery of an AutoSupport message significantly improves problem determination and resolution.&lt;/EM&gt;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;For details please see page 74 onwards&amp;nbsp;of the ONTAP 9 EMS Event Catalog: &lt;A href="https://library.netapp.com/ecm/ecm_get_file/ECMLP2597302" target="_blank"&gt;https://library.netapp.com/ecm/ecm_get_file/ECMLP2597302&lt;/A&gt;. All EMS events that can trigger an ASUP are in the&amp;nbsp;"callhome" Event Group.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Hope you find the info useful.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Thu, 18 May 2017 13:24:16 GMT</pubDate>
      <guid>https://community.netapp.com/t5/Active-IQ-and-AutoSupport-Discussions/ASUP-CASES-FOR-BROCADE/m-p/131161#M1405</guid>
      <dc:creator>sgrant</dc:creator>
      <dc:date>2017-05-18T13:24:16Z</dc:date>
    </item>
    <item>
      <title>Re: ASUP CASES FOR BROCADE</title>
      <link>https://community.netapp.com/t5/Active-IQ-and-AutoSupport-Discussions/ASUP-CASES-FOR-BROCADE/m-p/131187#M1406</link>
      <description>&lt;P&gt;These Events are not for Brocade.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&lt;STRONG&gt;&lt;SPAN&gt;&lt;FONT color="#000000"&gt;callhome.clus.net.degraded.&lt;/FONT&gt;&lt;/SPAN&gt;&lt;/STRONG&gt;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&lt;SPAN&gt;&lt;FONT color="#000000"&gt;This alert is trigerred for Data ONTAP Cluster connectivity.&lt;/FONT&gt;&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&lt;STRONG&gt;&lt;SPAN&gt;&lt;FONT color="#000000"&gt;callhome.fc.al.link&lt;/FONT&gt;&lt;/SPAN&gt;&lt;/STRONG&gt;&lt;/P&gt;&lt;P&gt;&lt;STRONG&gt;&lt;SPAN&gt;&lt;FONT color="#000000"&gt;callhome.fc.al.poor&lt;/FONT&gt;&lt;/SPAN&gt;&lt;/STRONG&gt;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&lt;SPAN&gt;&lt;FONT color="#000000"&gt;FCAL is used for connectivity to disk shelves , a Broacde switch is connetced as PTP.&lt;/FONT&gt;&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&lt;STRONG&gt;&lt;SPAN&gt;&lt;FONT color="#000000"&gt;ONTAP 9 EMS Event Catalog: &lt;A href="https://library.netapp.com/ecm/ecm_get_file/ECMLP2597302" target="_blank"&gt;&lt;U&gt;https://library.netapp.com/ecm/ecm_get_file/ECMLP2597302&lt;/U&gt;&lt;/A&gt;&lt;/FONT&gt;&lt;/SPAN&gt;&lt;/STRONG&gt;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&lt;SPAN&gt;&lt;FONT color="#000000"&gt;There is nothing specific for Brocade. The above catalog is very much specific to ONTAP Events.&lt;/FONT&gt;&lt;/SPAN&gt;&lt;/P&gt;</description>
      <pubDate>Fri, 19 May 2017 00:44:50 GMT</pubDate>
      <guid>https://community.netapp.com/t5/Active-IQ-and-AutoSupport-Discussions/ASUP-CASES-FOR-BROCADE/m-p/131187#M1406</guid>
      <dc:creator>Debbrata</dc:creator>
      <dc:date>2017-05-19T00:44:50Z</dc:date>
    </item>
    <item>
      <title>Re: ASUP CASES FOR BROCADE</title>
      <link>https://community.netapp.com/t5/Active-IQ-and-AutoSupport-Discussions/ASUP-CASES-FOR-BROCADE/m-p/131192#M1407</link>
      <description>&lt;P&gt;Correct, these are events that could be caused by the Brocade that would impact the NetApp so as to&amp;nbsp;trigger an AutoSupport.&amp;nbsp;If you are interested in being alerted on issues on the Brocade that could cuase an impact on the NetApp (as I had assumed!) then the&amp;nbsp;ones listed in the doc are what you need.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Brocades do not send AutoSupports to the MyAutoSupprot site.&lt;/P&gt;</description>
      <pubDate>Fri, 19 May 2017 07:40:31 GMT</pubDate>
      <guid>https://community.netapp.com/t5/Active-IQ-and-AutoSupport-Discussions/ASUP-CASES-FOR-BROCADE/m-p/131192#M1407</guid>
      <dc:creator>sgrant</dc:creator>
      <dc:date>2017-05-19T07:40:31Z</dc:date>
    </item>
  </channel>
</rss>

