<?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 IMC $SYSTEM auto recovers interface down alarms in IMC</title>
    <link>https://community.hpe.com/t5/imc/imc-system-auto-recovers-interface-down-alarms/m-p/7079541#M5730</link>
    <description>&lt;P&gt;Hello&lt;/P&gt;&lt;P&gt;We have strange problem with our IMC. When we get an link down alarm from trap (1.3.6.1.6.3.1.1.5.3), alarm gets recovered by $SYSTEM the same second it arrives.&lt;/P&gt;&lt;P&gt;We have configured recovery trap, but IMC doesn’t receive link UP during that time.&lt;/P&gt;&lt;P&gt;For example:&lt;/P&gt;&lt;P&gt;Name Link DOWN&lt;BR /&gt;Level Minor&lt;BR /&gt;OID 1.3.6.1.6.3.1.1.5.3&lt;BR /&gt;&lt;FONT color="#FF0000"&gt;Alarm at 2020-02-18 15:49:20&lt;/FONT&gt;&lt;BR /&gt;Alarm Source XXX&lt;BR /&gt;Type Trap&lt;BR /&gt;Alarm Category Interface/Link Status Alarm&lt;BR /&gt;Source Interface YYY&lt;BR /&gt;&lt;FONT color="#FF0000"&gt;Recovery Status $SYSTEM&lt;/FONT&gt;&lt;BR /&gt;&lt;FONT color="#FF0000"&gt;Recovered at 2020-02-18 15:49:20&lt;/FONT&gt;&lt;BR /&gt;Acknowledgement Status Unacknowledged&lt;BR /&gt;Description The interface Ten-GigabitEthernet2/0/7 is DOWN.&lt;/P&gt;&lt;P&gt;We have configurated custom&amp;nbsp;severity for some core devices. I’ve tried to remove this configuration, but nothing changed.&lt;/P&gt;&lt;P&gt;But we do get emails, as if alarm is not acknowledged.&lt;/P&gt;&lt;P&gt;Any idea how to fix this? Or this a known bug? Or something wrong with our configuration?&lt;/P&gt;&lt;P&gt;Our IMC version is 7.3 (E0703)&lt;/P&gt;&lt;P&gt;Thank you.&lt;/P&gt;</description>
    <pubDate>Tue, 18 Feb 2020 14:32:57 GMT</pubDate>
    <dc:creator>Edis_M</dc:creator>
    <dc:date>2020-02-18T14:32:57Z</dc:date>
    <item>
      <title>IMC $SYSTEM auto recovers interface down alarms</title>
      <link>https://community.hpe.com/t5/imc/imc-system-auto-recovers-interface-down-alarms/m-p/7079541#M5730</link>
      <description>&lt;P&gt;Hello&lt;/P&gt;&lt;P&gt;We have strange problem with our IMC. When we get an link down alarm from trap (1.3.6.1.6.3.1.1.5.3), alarm gets recovered by $SYSTEM the same second it arrives.&lt;/P&gt;&lt;P&gt;We have configured recovery trap, but IMC doesn’t receive link UP during that time.&lt;/P&gt;&lt;P&gt;For example:&lt;/P&gt;&lt;P&gt;Name Link DOWN&lt;BR /&gt;Level Minor&lt;BR /&gt;OID 1.3.6.1.6.3.1.1.5.3&lt;BR /&gt;&lt;FONT color="#FF0000"&gt;Alarm at 2020-02-18 15:49:20&lt;/FONT&gt;&lt;BR /&gt;Alarm Source XXX&lt;BR /&gt;Type Trap&lt;BR /&gt;Alarm Category Interface/Link Status Alarm&lt;BR /&gt;Source Interface YYY&lt;BR /&gt;&lt;FONT color="#FF0000"&gt;Recovery Status $SYSTEM&lt;/FONT&gt;&lt;BR /&gt;&lt;FONT color="#FF0000"&gt;Recovered at 2020-02-18 15:49:20&lt;/FONT&gt;&lt;BR /&gt;Acknowledgement Status Unacknowledged&lt;BR /&gt;Description The interface Ten-GigabitEthernet2/0/7 is DOWN.&lt;/P&gt;&lt;P&gt;We have configurated custom&amp;nbsp;severity for some core devices. I’ve tried to remove this configuration, but nothing changed.&lt;/P&gt;&lt;P&gt;But we do get emails, as if alarm is not acknowledged.&lt;/P&gt;&lt;P&gt;Any idea how to fix this? Or this a known bug? Or something wrong with our configuration?&lt;/P&gt;&lt;P&gt;Our IMC version is 7.3 (E0703)&lt;/P&gt;&lt;P&gt;Thank you.&lt;/P&gt;</description>
      <pubDate>Tue, 18 Feb 2020 14:32:57 GMT</pubDate>
      <guid>https://community.hpe.com/t5/imc/imc-system-auto-recovers-interface-down-alarms/m-p/7079541#M5730</guid>
      <dc:creator>Edis_M</dc:creator>
      <dc:date>2020-02-18T14:32:57Z</dc:date>
    </item>
    <item>
      <title>Re: IMC $SYSTEM auto recovers interface down alarms</title>
      <link>https://community.hpe.com/t5/imc/imc-system-auto-recovers-interface-down-alarms/m-p/7079987#M5737</link>
      <description>&lt;P&gt;Hello,&lt;/P&gt;&lt;P&gt;The "Link Down" and "Link Up" alarms are already be pre-configured in iMC so that an Up event for the same interface recovers the respective Down event. Are you sure that no Link Up trap was received immediately after the Link Down (check Trap Management &amp;gt; Trap Browse list)? Automatically recovered alarms will always show $SYSTEM under the Recovery Status.&lt;/P&gt;&lt;P&gt;Here is what the default Trap Management &amp;gt; Trap Definition of the Link UP Trap looks like in terms of parameters and automatically restoring the Link DOWN traps:&lt;/P&gt;&lt;P&gt;&lt;span class="lia-inline-image-display-wrapper lia-image-align-inline" image-alt="LinkUP-Config.png" style="width: 1582px;"&gt;&lt;img src="https://community.hpe.com/t5/image/serverpage/image-id/114089i5EFD80C9752E6B48/image-size/large?v=v2&amp;amp;px=2000" role="button" title="LinkUP-Config.png" alt="LinkUP-Config.png" /&gt;&lt;/span&gt;&lt;/P&gt;&lt;P&gt;Note that under the parameters, Interface Index should be set as the Key Parameter and Interface Index (configured like this by default). Otherwise you might see UP events from one interface recovering the DOWN status of a different interface.&lt;/P&gt;&lt;P&gt;Regarding receiving of e-mails - the moment any alarm is generated that matches the conditions in your mail notification rule, an e-mail will be sent. This is expected behavior, it will be sent regardless of whether the alarm gets automatically recovered a split-second later by receiving a Link UP event or not.&lt;/P&gt;</description>
      <pubDate>Fri, 21 Feb 2020 13:00:11 GMT</pubDate>
      <guid>https://community.hpe.com/t5/imc/imc-system-auto-recovers-interface-down-alarms/m-p/7079987#M5737</guid>
      <dc:creator>jguse</dc:creator>
      <dc:date>2020-02-21T13:00:11Z</dc:date>
    </item>
  </channel>
</rss>

