<?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: Is it Bug? It's about dfsmidbandblock on standalone AP. in Access Points - Indoor and Outdoor</title>
    <link>https://community.ruckuswireless.com/t5/Access-Points-Indoor-and-Outdoor/Is-it-Bug-It-s-about-dfsmidbandblock-on-standalone-AP/m-p/31373#M8770</link>
    <description>&lt;P&gt;Just reset dfschannel block.&lt;/P&gt;&lt;P&gt;With cli(get dfschannelmidbandblock wlanX), it was shown enabled fuction.&lt;/P&gt;&lt;P&gt;As a result, I thought it's bug.&lt;/P&gt;</description>
    <pubDate>Mon, 03 Aug 2015 15:21:19 GMT</pubDate>
    <dc:creator>hyosang_choi</dc:creator>
    <dc:date>2015-08-03T15:21:19Z</dc:date>
    <item>
      <title>Is it Bug? It's about dfsmidbandblock on standalone AP.</title>
      <link>https://community.ruckuswireless.com/t5/Access-Points-Indoor-and-Outdoor/Is-it-Bug-It-s-about-dfsmidbandblock-on-standalone-AP/m-p/31371#M8768</link>
      <description>&lt;P&gt;Hi.&lt;/P&gt;&lt;P&gt;I tested "dfsmidbandblock function" on standalone AP.&lt;/P&gt;&lt;P&gt;It's worked when set cli.&lt;/P&gt;&lt;P&gt;But, atfer Ap reboot, it's now worked.&lt;/P&gt;&lt;P&gt;Is it bug?&amp;nbsp;&amp;nbsp; I thought it's BUG.&lt;/P&gt;&lt;P&gt;Plz let me know about it.&lt;/P&gt;&lt;P&gt;It's tested on F/W version both 100.x.x.x&amp;nbsp; and&amp;nbsp;9.8.x, It's same. &lt;/P&gt;&lt;P&gt;AP is 7372.&lt;/P&gt;&lt;P&gt;The following is snapshot.&lt;/P&gt;&lt;P&gt;Regards.&lt;/P&gt;&lt;P&gt;1)&lt;/P&gt;&lt;P&gt;&lt;span class="lia-inline-image-display-wrapper" image-alt="Image_ images_messages_5f91c3e6135b77e2478d4413_b42cd44bbe7cfbecf1314e9529e3aa79_RackMultipart2015073174671lmad-f40b6515-6c22-45a0-8695-ff706b2c3fad-1106583192.png1438353091"&gt;&lt;img src="https://community.ruckuswireless.com/t5/image/serverpage/image-id/797iD8A5C2EC526FCEF4/image-size/large?v=v2&amp;amp;px=999" role="button" title="Image_ images_messages_5f91c3e6135b77e2478d4413_b42cd44bbe7cfbecf1314e9529e3aa79_RackMultipart2015073174671lmad-f40b6515-6c22-45a0-8695-ff706b2c3fad-1106583192.png1438353091" alt="Image_ images_messages_5f91c3e6135b77e2478d4413_b42cd44bbe7cfbecf1314e9529e3aa79_RackMultipart2015073174671lmad-f40b6515-6c22-45a0-8695-ff706b2c3fad-1106583192.png1438353091" /&gt;&lt;/span&gt;﻿&lt;/P&gt;&lt;P&gt;2)&lt;/P&gt;&lt;P&gt;&lt;span class="lia-inline-image-display-wrapper" image-alt="Image_ images_messages_5f91c3e6135b77e2478d4413_5263ebef99f4acabc9e88aa6cbe8b87d_RackMultipart2015073126142v0v3-0ba90f47-d5c6-40cc-ac40-446d452c47c0-216435898.png1438353162"&gt;&lt;img src="https://community.ruckuswireless.com/t5/image/serverpage/image-id/798i51D77E0E4B22270B/image-size/large?v=v2&amp;amp;px=999" role="button" title="Image_ images_messages_5f91c3e6135b77e2478d4413_5263ebef99f4acabc9e88aa6cbe8b87d_RackMultipart2015073126142v0v3-0ba90f47-d5c6-40cc-ac40-446d452c47c0-216435898.png1438353162" alt="Image_ images_messages_5f91c3e6135b77e2478d4413_5263ebef99f4acabc9e88aa6cbe8b87d_RackMultipart2015073126142v0v3-0ba90f47-d5c6-40cc-ac40-446d452c47c0-216435898.png1438353162" /&gt;&lt;/span&gt;&lt;/P&gt;</description>
      <pubDate>Fri, 31 Jul 2015 14:35:15 GMT</pubDate>
      <guid>https://community.ruckuswireless.com/t5/Access-Points-Indoor-and-Outdoor/Is-it-Bug-It-s-about-dfsmidbandblock-on-standalone-AP/m-p/31371#M8768</guid>
      <dc:creator>hyosang_choi</dc:creator>
      <dc:date>2015-07-31T14:35:15Z</dc:date>
    </item>
    <item>
      <title>Re: Is it Bug? It's about dfsmidbandblock on standalone AP.</title>
      <link>https://community.ruckuswireless.com/t5/Access-Points-Indoor-and-Outdoor/Is-it-Bug-It-s-about-dfsmidbandblock-on-standalone-AP/m-p/31372#M8769</link>
      <description>&lt;P&gt;Not all/many AP CLI configuration settings will persist after an AP reboot.&lt;/P&gt;

&lt;P&gt;Some WLAN settings, can be configured by the ZoneDirector (on ZD managed
APs) which will then be provisioned on all connected APs (even after reboots).



&lt;/P&gt;</description>
      <pubDate>Fri, 31 Jul 2015 17:17:07 GMT</pubDate>
      <guid>https://community.ruckuswireless.com/t5/Access-Points-Indoor-and-Outdoor/Is-it-Bug-It-s-about-dfsmidbandblock-on-standalone-AP/m-p/31372#M8769</guid>
      <dc:creator>joe_tassone</dc:creator>
      <dc:date>2015-07-31T17:17:07Z</dc:date>
    </item>
    <item>
      <title>Re: Is it Bug? It's about dfsmidbandblock on standalone AP.</title>
      <link>https://community.ruckuswireless.com/t5/Access-Points-Indoor-and-Outdoor/Is-it-Bug-It-s-about-dfsmidbandblock-on-standalone-AP/m-p/31373#M8770</link>
      <description>&lt;P&gt;Just reset dfschannel block.&lt;/P&gt;&lt;P&gt;With cli(get dfschannelmidbandblock wlanX), it was shown enabled fuction.&lt;/P&gt;&lt;P&gt;As a result, I thought it's bug.&lt;/P&gt;</description>
      <pubDate>Mon, 03 Aug 2015 15:21:19 GMT</pubDate>
      <guid>https://community.ruckuswireless.com/t5/Access-Points-Indoor-and-Outdoor/Is-it-Bug-It-s-about-dfsmidbandblock-on-standalone-AP/m-p/31373#M8770</guid>
      <dc:creator>hyosang_choi</dc:creator>
      <dc:date>2015-08-03T15:21:19Z</dc:date>
    </item>
  </channel>
</rss>

