<?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: Disable UNII-3 Channels Causing Config Update Failures in Aerohive Migrated Content</title>
    <link>https://community.extremenetworks.com/t5/aerohive-migrated-content/disable-unii-3-channels-causing-config-update-failures/m-p/64244#M2155</link>
    <description>&lt;P&gt;Hi Ashley, thanks for getting back to me. I imagine this solution would work but would not be ideal.  Do you know if Aerohive is planning to fix this at some time?&lt;/P&gt;</description>
    <pubDate>Wed, 24 Apr 2019 22:21:16 GMT</pubDate>
    <dc:creator>blw</dc:creator>
    <dc:date>2019-04-24T22:21:16Z</dc:date>
    <item>
      <title>Disable UNII-3 Channels Causing Config Update Failures</title>
      <link>https://community.extremenetworks.com/t5/aerohive-migrated-content/disable-unii-3-channels-causing-config-update-failures/m-p/64242#M2153</link>
      <description>&lt;P&gt;I have switched the &lt;B&gt;Disable UNII-3 Channels &lt;/B&gt;option on in a radio profile as some of my clients do not support these channels.  This causes delta config updates to fail for older devices (AP121 and AP330) with the error message "The CLI 'interface wifi1 radio channel exclude 149' execute failed, cause by: Unknown error".&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Manually running the CLI via SSH produces the following output : "Channel (149) is not in the available channel list.". The delta updates work fine on the newer models (AP130, AP230, AP250 etc).&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;The failing APs are on HiveOS 6.5r12 build-221611 (The latest available). Other HiveManager NG users have also seen the same behavior.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;I was going to use the feedback option but it has been removed  &lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Thanks in advance for any assistance&lt;/P&gt;</description>
      <pubDate>Tue, 23 Apr 2019 19:13:10 GMT</pubDate>
      <guid>https://community.extremenetworks.com/t5/aerohive-migrated-content/disable-unii-3-channels-causing-config-update-failures/m-p/64242#M2153</guid>
      <dc:creator>blw</dc:creator>
      <dc:date>2019-04-23T19:13:10Z</dc:date>
    </item>
    <item>
      <title>Re: Disable UNII-3 Channels Causing Config Update Failures</title>
      <link>https://community.extremenetworks.com/t5/aerohive-migrated-content/disable-unii-3-channels-causing-config-update-failures/m-p/64243#M2154</link>
      <description>&lt;P&gt;Hello,&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;I believe the issue is that these channels are not available on that version of firmware hence it's unable to apply the command to the AP. As a workaround it may be best to clone the 5GHz radio profiles - one with and one without that option.&lt;/P&gt;</description>
      <pubDate>Tue, 23 Apr 2019 21:07:06 GMT</pubDate>
      <guid>https://community.extremenetworks.com/t5/aerohive-migrated-content/disable-unii-3-channels-causing-config-update-failures/m-p/64243#M2154</guid>
      <dc:creator>ashley_finch</dc:creator>
      <dc:date>2019-04-23T21:07:06Z</dc:date>
    </item>
    <item>
      <title>Re: Disable UNII-3 Channels Causing Config Update Failures</title>
      <link>https://community.extremenetworks.com/t5/aerohive-migrated-content/disable-unii-3-channels-causing-config-update-failures/m-p/64244#M2155</link>
      <description>&lt;P&gt;Hi Ashley, thanks for getting back to me. I imagine this solution would work but would not be ideal.  Do you know if Aerohive is planning to fix this at some time?&lt;/P&gt;</description>
      <pubDate>Wed, 24 Apr 2019 22:21:16 GMT</pubDate>
      <guid>https://community.extremenetworks.com/t5/aerohive-migrated-content/disable-unii-3-channels-causing-config-update-failures/m-p/64244#M2155</guid>
      <dc:creator>blw</dc:creator>
      <dc:date>2019-04-24T22:21:16Z</dc:date>
    </item>
  </channel>
</rss>

