<?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: AP310 config errors after updating in ExtremeWireless (WiNG)</title>
    <link>https://community.extremenetworks.com/t5/extremewireless-wing/ap310-config-errors-after-updating/m-p/87290#M8169</link>
    <description>&lt;P&gt;Good to hear that you found the culprit, Matheus.&lt;/P&gt;</description>
    <pubDate>Fri, 16 Jul 2021 22:34:22 GMT</pubDate>
    <dc:creator>ckelly</dc:creator>
    <dc:date>2021-07-16T22:34:22Z</dc:date>
    <item>
      <title>AP310 config errors after updating</title>
      <link>https://community.extremenetworks.com/t5/extremewireless-wing/ap310-config-errors-after-updating/m-p/87285#M8164</link>
      <description>&lt;P&gt;Hello,&lt;/P&gt;&lt;PRE&gt;I have a VX9000 with 7632 and 310 access points, today I includes new 3 310 APs on one site, The APs came with 7.5.1 Wing firmware, after updating these 3 controller APs (7.6.2.0), they came back with some configuration errors ("Last configuration update resulted in loss of connectivity to the controller, ignore this configuration update request) and they are not working properly.&lt;/PRE&gt;</description>
      <pubDate>Fri, 16 Jul 2021 20:16:48 GMT</pubDate>
      <guid>https://community.extremenetworks.com/t5/extremewireless-wing/ap310-config-errors-after-updating/m-p/87285#M8164</guid>
      <dc:creator>Matheus_Santana</dc:creator>
      <dc:date>2021-07-16T20:16:48Z</dc:date>
    </item>
    <item>
      <title>Re: AP310 config errors after updating</title>
      <link>https://community.extremenetworks.com/t5/extremewireless-wing/ap310-config-errors-after-updating/m-p/87286#M8165</link>
      <description>&lt;P&gt;Matheus,&lt;/P&gt;&lt;P&gt;The configuration error message is indicating that when it was pushed and loaded by the AP, it ended up causing the AP to lose its ability to adopt to the controller. In these cases, the AP will automatically revert to the previous working configuration so that it can at least re-adopt to the controller - preventing it from being stranded/orphaned.&lt;/P&gt;&lt;P&gt;Somewhere in the configuration that is being sent, there is something either included or missing that causes the AP to not be able to reach the controller.&lt;/P&gt;&lt;P&gt;Question: Is the AP Profile that is being pushed to the AP the same one that is being used by other APs that are successfully adopted to the controller…..or is this a new AP Profile that was created just for these new APs?&lt;/P&gt;</description>
      <pubDate>Fri, 16 Jul 2021 20:21:17 GMT</pubDate>
      <guid>https://community.extremenetworks.com/t5/extremewireless-wing/ap310-config-errors-after-updating/m-p/87286#M8165</guid>
      <dc:creator>ckelly</dc:creator>
      <dc:date>2021-07-16T20:21:17Z</dc:date>
    </item>
    <item>
      <title>Re: AP310 config errors after updating</title>
      <link>https://community.extremenetworks.com/t5/extremewireless-wing/ap310-config-errors-after-updating/m-p/87287#M8166</link>
      <description>&lt;P&gt;Hello Mr. Kelly,&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;When I check, the adoption mode of these APs after upgrade are not set, so I made it changing to “controller”, I believe that was the problem, but the error status continued.&lt;/P&gt;&lt;P&gt;The profile have the same configuration of others functional sites.&lt;/P&gt;</description>
      <pubDate>Fri, 16 Jul 2021 20:34:05 GMT</pubDate>
      <guid>https://community.extremenetworks.com/t5/extremewireless-wing/ap310-config-errors-after-updating/m-p/87287#M8166</guid>
      <dc:creator>Matheus_Santana</dc:creator>
      <dc:date>2021-07-16T20:34:05Z</dc:date>
    </item>
    <item>
      <title>Re: AP310 config errors after updating</title>
      <link>https://community.extremenetworks.com/t5/extremewireless-wing/ap310-config-errors-after-updating/m-p/87288#M8167</link>
      <description>&lt;P&gt;Matheus, I’m not certain what change you made when you say that you changed it to “controller”. Can you describe this change?&lt;/P&gt;&lt;P&gt;More than likely, the issue is related to a network configuration problem that is being created with the new configuration.&lt;/P&gt;&lt;P&gt;Also, are these new APs deployed at a site with other APs that are successfully adopted...or are these three new APs deployed at a NEW site that has no other APs?&lt;/P&gt;&lt;P&gt;Are all three new 310i’s having seeing this issue?&lt;/P&gt;</description>
      <pubDate>Fri, 16 Jul 2021 20:55:16 GMT</pubDate>
      <guid>https://community.extremenetworks.com/t5/extremewireless-wing/ap310-config-errors-after-updating/m-p/87288#M8167</guid>
      <dc:creator>ckelly</dc:creator>
      <dc:date>2021-07-16T20:55:16Z</dc:date>
    </item>
    <item>
      <title>Re: AP310 config errors after updating</title>
      <link>https://community.extremenetworks.com/t5/extremewireless-wing/ap310-config-errors-after-updating/m-p/87289#M8168</link>
      <description>&lt;P&gt;Chris, I found the problem and the APs worked after reload. The default gateway of these news APs are not set in the profile. Thank you for the help.&lt;/P&gt;</description>
      <pubDate>Fri, 16 Jul 2021 21:29:47 GMT</pubDate>
      <guid>https://community.extremenetworks.com/t5/extremewireless-wing/ap310-config-errors-after-updating/m-p/87289#M8168</guid>
      <dc:creator>Matheus_Santana</dc:creator>
      <dc:date>2021-07-16T21:29:47Z</dc:date>
    </item>
    <item>
      <title>Re: AP310 config errors after updating</title>
      <link>https://community.extremenetworks.com/t5/extremewireless-wing/ap310-config-errors-after-updating/m-p/87290#M8169</link>
      <description>&lt;P&gt;Good to hear that you found the culprit, Matheus.&lt;/P&gt;</description>
      <pubDate>Fri, 16 Jul 2021 22:34:22 GMT</pubDate>
      <guid>https://community.extremenetworks.com/t5/extremewireless-wing/ap310-config-errors-after-updating/m-p/87290#M8169</guid>
      <dc:creator>ckelly</dc:creator>
      <dc:date>2021-07-16T22:34:22Z</dc:date>
    </item>
  </channel>
</rss>

