<?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: How does XMC decide what interfaces to alert up/down in ExtremeCloud IQ- Site Engine Management Center</title>
    <link>https://community.extremenetworks.com/t5/extremecloud-iq-site-engine/how-does-xmc-decide-what-interfaces-to-alert-up-down/m-p/78989#M8854</link>
    <description>Thanks &lt;SPAN&gt;&lt;SPAN&gt;&lt;SPAN class="bio-bubble-link"&gt;&lt;A href="https://community.extremenetworks.com/network/members/profile?UserKey=04660f43-1aca-45a8-af81-2b37804d4b75" target="" class="author" aria-label="Adrian Orellana Press space to toggle pop up" aria-haspopup="dialog" aria-controls="bio-bubble-popup-04660f43-1aca-45a8-af81-2b37804d4b75-5"&gt;Adrian Orellana&lt;/A&gt;&lt;SPAN class="bootstrap-4"&gt;&lt;/SPAN&gt;&lt;/SPAN&gt;&lt;/SPAN&gt;&lt;/SPAN&gt;&lt;SPAN&gt; .&lt;BR /&gt;Sorry for the delay in replying.&amp;nbsp; We don't get many of these messages so it has taken a long time for one to come through.&lt;BR /&gt;We do normally configure our edge stacks so that only the uplink ports send up/down traps (as per your email, but for ERS switches- different syntax)&lt;BR /&gt;&lt;BR /&gt;What has happened is that when another switch has been added to a stack the ports for the added stack were not configured to stop link up/down.&lt;BR /&gt;&lt;BR /&gt;It turns out to be a good way of spotting badly configured added stack member!&lt;/SPAN&gt;</description>
    <pubDate>Wed, 26 Jan 2022 13:18:00 GMT</pubDate>
    <dc:creator>bar</dc:creator>
    <dc:date>2022-01-26T13:18:00Z</dc:date>
    <item>
      <title>How does XMC decide what interfaces to alert up/down</title>
      <link>https://community.extremenetworks.com/t5/extremecloud-iq-site-engine/how-does-xmc-decide-what-interfaces-to-alert-up-down/m-p/78987#M8852</link>
      <description>Can anyone tell me how XMC decides which ports to include in the "Alarms and Events" page?&lt;BR /&gt;&lt;BR /&gt;Our installation correctly notifies us of uplink port status changes and generally correctly&amp;nbsp;&lt;EM&gt;doesn't&lt;/EM&gt; inform us of user port changes.&amp;nbsp; However occasionally it seems to get it wrong and will report a user port going down.&lt;BR /&gt;&lt;BR /&gt;I cannot see anywhere that this is configured.&amp;nbsp; Can anyone help?&lt;BR /&gt;&lt;BR /&gt;thanks,</description>
      <pubDate>Wed, 15 Dec 2021 15:19:29 GMT</pubDate>
      <guid>https://community.extremenetworks.com/t5/extremecloud-iq-site-engine/how-does-xmc-decide-what-interfaces-to-alert-up-down/m-p/78987#M8852</guid>
      <dc:creator>bar</dc:creator>
      <dc:date>2021-12-15T15:19:29Z</dc:date>
    </item>
    <item>
      <title>Re: How does XMC decide what interfaces to alert up/down</title>
      <link>https://community.extremenetworks.com/t5/extremecloud-iq-site-engine/how-does-xmc-decide-what-interfaces-to-alert-up-down/m-p/78988#M8853</link>
      <description>The command to disable/enable traps when a port goes up/down is:&lt;BR /&gt;&lt;BR /&gt;
&lt;PRE class="language-python"&gt;&lt;CODE&gt;# enable snmp traps port-up-down ports &amp;lt;port_list&amp;gt;​
# disable snmp traps port-up-down ports &amp;lt;port_list&amp;gt;​&lt;/CODE&gt;&lt;/PRE&gt;</description>
      <pubDate>Thu, 16 Dec 2021 13:25:51 GMT</pubDate>
      <guid>https://community.extremenetworks.com/t5/extremecloud-iq-site-engine/how-does-xmc-decide-what-interfaces-to-alert-up-down/m-p/78988#M8853</guid>
      <dc:creator>AdrianO</dc:creator>
      <dc:date>2021-12-16T13:25:51Z</dc:date>
    </item>
    <item>
      <title>Re: How does XMC decide what interfaces to alert up/down</title>
      <link>https://community.extremenetworks.com/t5/extremecloud-iq-site-engine/how-does-xmc-decide-what-interfaces-to-alert-up-down/m-p/78989#M8854</link>
      <description>Thanks &lt;SPAN&gt;&lt;SPAN&gt;&lt;SPAN class="bio-bubble-link"&gt;&lt;A href="https://community.extremenetworks.com/network/members/profile?UserKey=04660f43-1aca-45a8-af81-2b37804d4b75" target="" class="author" aria-label="Adrian Orellana Press space to toggle pop up" aria-haspopup="dialog" aria-controls="bio-bubble-popup-04660f43-1aca-45a8-af81-2b37804d4b75-5"&gt;Adrian Orellana&lt;/A&gt;&lt;SPAN class="bootstrap-4"&gt;&lt;/SPAN&gt;&lt;/SPAN&gt;&lt;/SPAN&gt;&lt;/SPAN&gt;&lt;SPAN&gt; .&lt;BR /&gt;Sorry for the delay in replying.&amp;nbsp; We don't get many of these messages so it has taken a long time for one to come through.&lt;BR /&gt;We do normally configure our edge stacks so that only the uplink ports send up/down traps (as per your email, but for ERS switches- different syntax)&lt;BR /&gt;&lt;BR /&gt;What has happened is that when another switch has been added to a stack the ports for the added stack were not configured to stop link up/down.&lt;BR /&gt;&lt;BR /&gt;It turns out to be a good way of spotting badly configured added stack member!&lt;/SPAN&gt;</description>
      <pubDate>Wed, 26 Jan 2022 13:18:00 GMT</pubDate>
      <guid>https://community.extremenetworks.com/t5/extremecloud-iq-site-engine/how-does-xmc-decide-what-interfaces-to-alert-up-down/m-p/78989#M8854</guid>
      <dc:creator>bar</dc:creator>
      <dc:date>2022-01-26T13:18:00Z</dc:date>
    </item>
  </channel>
</rss>

