<?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: Extremecloudiq Update Issue in ExtremeCloud IQ</title>
    <link>https://community.extremenetworks.com/t5/extremecloud-iq/extremecloudiq-update-issue/m-p/89905#M2461</link>
    <description>&lt;P&gt;Could also be a latency issue (can confirm this if you run &lt;A href="https://extremeportal.force.com/ExtrArticleDetail?n=000046614&amp;amp;q=Capwap%20debug" target="_blank" rel="nofollow noreferrer noopener"&gt;capwap debugs&lt;/A&gt; and then search for “echos” in the buffered log of the tech data, if you see failed echo packets then it’s latency). If the APs don’t respond to XIQ fast enough then it’ll trigger that lost connection email even if the AP starts responding again in a few seconds. We ran in to this a lot, no real connection issues, all APs updated, but a bit of latency and we got flooded with emails.&lt;/P&gt;</description>
    <pubDate>Mon, 27 Apr 2020 23:27:04 GMT</pubDate>
    <dc:creator>Shannon_Abby</dc:creator>
    <dc:date>2020-04-27T23:27:04Z</dc:date>
    <item>
      <title>Extremecloudiq Update Issue</title>
      <link>https://community.extremenetworks.com/t5/extremecloud-iq/extremecloudiq-update-issue/m-p/89903#M2459</link>
      <description>&lt;P&gt;Has anyone had any issue with AP’s losing connection to the cloud and it sending emails (if you have that set) saying connection change because it lost the connection?&amp;nbsp; Since the update this past weekend I have received over 300 emails from various ap’s and when I look it shows them connected.&amp;nbsp; Any help would be greatly appreciated.&lt;/P&gt;</description>
      <pubDate>Tue, 21 Apr 2020 20:00:38 GMT</pubDate>
      <guid>https://community.extremenetworks.com/t5/extremecloud-iq/extremecloudiq-update-issue/m-p/89903#M2459</guid>
      <dc:creator>bobby_clowers</dc:creator>
      <dc:date>2020-04-21T20:00:38Z</dc:date>
    </item>
    <item>
      <title>Re: Extremecloudiq Update Issue</title>
      <link>https://community.extremenetworks.com/t5/extremecloud-iq/extremecloudiq-update-issue/m-p/89904#M2460</link>
      <description>&lt;P&gt;I would recommend pushing complete configurations to all your devices. You may also want to check the Firewall Configuration guide found by hovering over the admin icon/silhouette in the top right of the Cloud IQ, then click About ExtremeCloud IQ and follow the Firewall Configuration Guide link.&lt;/P&gt;</description>
      <pubDate>Sat, 25 Apr 2020 02:49:36 GMT</pubDate>
      <guid>https://community.extremenetworks.com/t5/extremecloud-iq/extremecloudiq-update-issue/m-p/89904#M2460</guid>
      <dc:creator>Nick_Moore</dc:creator>
      <dc:date>2020-04-25T02:49:36Z</dc:date>
    </item>
    <item>
      <title>Re: Extremecloudiq Update Issue</title>
      <link>https://community.extremenetworks.com/t5/extremecloud-iq/extremecloudiq-update-issue/m-p/89905#M2461</link>
      <description>&lt;P&gt;Could also be a latency issue (can confirm this if you run &lt;A href="https://extremeportal.force.com/ExtrArticleDetail?n=000046614&amp;amp;q=Capwap%20debug" target="_blank" rel="nofollow noreferrer noopener"&gt;capwap debugs&lt;/A&gt; and then search for “echos” in the buffered log of the tech data, if you see failed echo packets then it’s latency). If the APs don’t respond to XIQ fast enough then it’ll trigger that lost connection email even if the AP starts responding again in a few seconds. We ran in to this a lot, no real connection issues, all APs updated, but a bit of latency and we got flooded with emails.&lt;/P&gt;</description>
      <pubDate>Mon, 27 Apr 2020 23:27:04 GMT</pubDate>
      <guid>https://community.extremenetworks.com/t5/extremecloud-iq/extremecloudiq-update-issue/m-p/89905#M2461</guid>
      <dc:creator>Shannon_Abby</dc:creator>
      <dc:date>2020-04-27T23:27:04Z</dc:date>
    </item>
  </channel>
</rss>

