<?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: some APs dropping hostname after complete update. Still in config, requires a second update to correct in ExtremeCloud IQ</title>
    <link>https://community.extremenetworks.com/t5/extremecloud-iq/some-aps-dropping-hostname-after-complete-update-still-in-config/m-p/87718#M2271</link>
    <description>&lt;P&gt;The hostname reverting to the default name issue is a known issue that is still being worked out. The config audit mismatch would likely be a separate issue, and for that I’d recommend opening a case as they’ll have to look at some logs to try to identify what is tripping the audit mismatch notification.&amp;nbsp;&lt;/P&gt;</description>
    <pubDate>Sat, 19 Dec 2020 02:30:04 GMT</pubDate>
    <dc:creator>SamPirok</dc:creator>
    <dc:date>2020-12-19T02:30:04Z</dc:date>
    <item>
      <title>some APs dropping hostname after complete update. Still in config, requires a second update to correct</title>
      <link>https://community.extremenetworks.com/t5/extremecloud-iq/some-aps-dropping-hostname-after-complete-update-still-in-config/m-p/87715#M2268</link>
      <description>&lt;P&gt;I’ve noticed this problem on and off for a while but it seems sporadic.However, Last night I did complete updates to all of my APs, and this morning there are over 25 that are not showing their proper hostname (instead, are showing “AH-MAC###”). If I look in device 360 &amp;gt; configure &amp;gt; device configuration &amp;gt; hostname the proper hostname is still there, so pushing a delta will re-apply the hostname. Any idea why this would be happening, and how to prevent it from happening in the future?&lt;/P&gt;</description>
      <pubDate>Sat, 19 Dec 2020 00:05:17 GMT</pubDate>
      <guid>https://community.extremenetworks.com/t5/extremecloud-iq/some-aps-dropping-hostname-after-complete-update-still-in-config/m-p/87715#M2268</guid>
      <dc:creator>w1f1n00b</dc:creator>
      <dc:date>2020-12-19T00:05:17Z</dc:date>
    </item>
    <item>
      <title>Re: some APs dropping hostname after complete update. Still in config, requires a second update to correct</title>
      <link>https://community.extremenetworks.com/t5/extremecloud-iq/some-aps-dropping-hostname-after-complete-update-still-in-config/m-p/87716#M2269</link>
      <description>&lt;P&gt;Hi John,&lt;/P&gt;&lt;P&gt;If you click on the configuration audit &amp;gt; delta tab, after the delta push&amp;nbsp;to&amp;nbsp;the AP is this showing anything or is it empty? I’m wondering whether something in the APs config is causing it to roll back to an old configuration and losing the hostname etc.&lt;/P&gt;</description>
      <pubDate>Sat, 19 Dec 2020 00:08:38 GMT</pubDate>
      <guid>https://community.extremenetworks.com/t5/extremecloud-iq/some-aps-dropping-hostname-after-complete-update-still-in-config/m-p/87716#M2269</guid>
      <dc:creator>Ash_Finch</dc:creator>
      <dc:date>2020-12-19T00:08:38Z</dc:date>
    </item>
    <item>
      <title>Re: some APs dropping hostname after complete update. Still in config, requires a second update to correct</title>
      <link>https://community.extremenetworks.com/t5/extremecloud-iq/some-aps-dropping-hostname-after-complete-update-still-in-config/m-p/87717#M2270</link>
      <description>&lt;P&gt;I ended up pushing a complete config update to these devices this morning, and unfortunately didn’t document the specific devices.&lt;/P&gt;&lt;P&gt;&lt;BR /&gt;However now that I’m looking, I do have 250+ devices still with a config audit mismatch even though they are showing that they were successfully updated last night (and no config changes have been made since). Any idea if this could be a related or a separate issue?&lt;/P&gt;</description>
      <pubDate>Sat, 19 Dec 2020 00:54:37 GMT</pubDate>
      <guid>https://community.extremenetworks.com/t5/extremecloud-iq/some-aps-dropping-hostname-after-complete-update-still-in-config/m-p/87717#M2270</guid>
      <dc:creator>w1f1n00b</dc:creator>
      <dc:date>2020-12-19T00:54:37Z</dc:date>
    </item>
    <item>
      <title>Re: some APs dropping hostname after complete update. Still in config, requires a second update to correct</title>
      <link>https://community.extremenetworks.com/t5/extremecloud-iq/some-aps-dropping-hostname-after-complete-update-still-in-config/m-p/87718#M2271</link>
      <description>&lt;P&gt;The hostname reverting to the default name issue is a known issue that is still being worked out. The config audit mismatch would likely be a separate issue, and for that I’d recommend opening a case as they’ll have to look at some logs to try to identify what is tripping the audit mismatch notification.&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Sat, 19 Dec 2020 02:30:04 GMT</pubDate>
      <guid>https://community.extremenetworks.com/t5/extremecloud-iq/some-aps-dropping-hostname-after-complete-update-still-in-config/m-p/87718#M2271</guid>
      <dc:creator>SamPirok</dc:creator>
      <dc:date>2020-12-19T02:30:04Z</dc:date>
    </item>
    <item>
      <title>Re: some APs dropping hostname after complete update. Still in config, requires a second update to correct</title>
      <link>https://community.extremenetworks.com/t5/extremecloud-iq/some-aps-dropping-hostname-after-complete-update-still-in-config/m-p/87719#M2272</link>
      <description>&lt;P&gt;Is there a CFD for this yet? I haven’t seen it in the known issues list&lt;/P&gt;&lt;P&gt;&lt;A href="https://docs.aerohive.com/330000/docs/help/english/ng/Content/reference/known-and-addressed-issues.htm" target="_blank" rel="nofollow noreferrer noopener"&gt;https://docs.aerohive.com/330000/docs/help/english/ng/Content/reference/known-and-addressed-issues.htm&lt;/A&gt;&lt;/P&gt;</description>
      <pubDate>Sat, 19 Dec 2020 02:33:28 GMT</pubDate>
      <guid>https://community.extremenetworks.com/t5/extremecloud-iq/some-aps-dropping-hostname-after-complete-update-still-in-config/m-p/87719#M2272</guid>
      <dc:creator>w1f1n00b</dc:creator>
      <dc:date>2020-12-19T02:33:28Z</dc:date>
    </item>
    <item>
      <title>Re: some APs dropping hostname after complete update. Still in config, requires a second update to correct</title>
      <link>https://community.extremenetworks.com/t5/extremecloud-iq/some-aps-dropping-hostname-after-complete-update-still-in-config/m-p/87720#M2273</link>
      <description>&lt;P&gt;Yes, this is CFD-5718.&lt;/P&gt;</description>
      <pubDate>Tue, 22 Dec 2020 03:00:35 GMT</pubDate>
      <guid>https://community.extremenetworks.com/t5/extremecloud-iq/some-aps-dropping-hostname-after-complete-update-still-in-config/m-p/87720#M2273</guid>
      <dc:creator>SamPirok</dc:creator>
      <dc:date>2020-12-22T03:00:35Z</dc:date>
    </item>
  </channel>
</rss>

