<?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 AP behavior when detecting radar on DFS channels in Wireless</title>
    <link>https://community.cisco.com/t5/wireless/ap-behavior-when-detecting-radar-on-dfs-channels/m-p/5259046#M280780</link>
    <description>&lt;P&gt;Hi all,&lt;/P&gt;&lt;P&gt;In the following process of DFS on Cisco Wireless Network (Either AireOS or IOS-XE WLC)&lt;/P&gt;&lt;P&gt;Could someone please confirm that I understand this correctly, particularly the 30-minute period of non-occupancy?&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;1.) DFS Non-Occupancy Period Rules&lt;BR /&gt;When an AP detects radar on a DFS channel (e.g., Channel 132), it must:&lt;/P&gt;&lt;P&gt;Immediately stop transmissions and vacate the channel within 1 second.&lt;BR /&gt;Avoid using the detected channel for at least 30 minutes (called the Non-Occupancy Period).&lt;BR /&gt;Select a new channel, either a non-DFS channel (preferred) or another DFS channel (which requires a Channel Availability Check).&lt;BR /&gt;Key Regulation (FCC, ETSI, etc.):&lt;/P&gt;&lt;P&gt;30-minute Non-Occupancy Period: The AP must not use the detected channel for at least 30 minutes after radar detection.&lt;/P&gt;&lt;P&gt;&lt;BR /&gt;2.) AP Behavior After Radar Detection&lt;BR /&gt;Case 1: Non-DFS Channel Available&lt;BR /&gt;&lt;span class="lia-unicode-emoji" title=":white_heavy_check_mark:"&gt;✅&lt;/span&gt;AP moves immediately to a non-DFS channel and resumes operation.&lt;/P&gt;&lt;P&gt;Case 2: Another DFS Channel is Selected&lt;BR /&gt;&lt;span class="lia-unicode-emoji" title=":white_heavy_check_mark:"&gt;✅&lt;/span&gt;AP moves to another DFS channel but must perform a Channel Availability Check (CAC):&lt;BR /&gt;60 seconds of listening for radar before accepting clients.&lt;/P&gt;&lt;P&gt;Case 3: No Other Channels Available&lt;BR /&gt;&lt;span class="lia-unicode-emoji" title=":hourglass_not_done:"&gt;⏳&lt;/span&gt;The AP remains offline until a valid channel is assigned.&lt;/P&gt;&lt;P&gt;3.) Can the AP Reuse Channel 132 Before 30 Minutes?&lt;BR /&gt;No, the AP must wait 30 minutes before reusing Channel 132.&lt;BR /&gt;Even if RRM selects Channel 132, the AP must reject it if it’s within the Non-Occupancy Period.&lt;/P&gt;</description>
    <pubDate>Tue, 11 Feb 2025 10:37:02 GMT</pubDate>
    <dc:creator>bakaholic39</dc:creator>
    <dc:date>2025-02-11T10:37:02Z</dc:date>
    <item>
      <title>AP behavior when detecting radar on DFS channels</title>
      <link>https://community.cisco.com/t5/wireless/ap-behavior-when-detecting-radar-on-dfs-channels/m-p/5259046#M280780</link>
      <description>&lt;P&gt;Hi all,&lt;/P&gt;&lt;P&gt;In the following process of DFS on Cisco Wireless Network (Either AireOS or IOS-XE WLC)&lt;/P&gt;&lt;P&gt;Could someone please confirm that I understand this correctly, particularly the 30-minute period of non-occupancy?&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;1.) DFS Non-Occupancy Period Rules&lt;BR /&gt;When an AP detects radar on a DFS channel (e.g., Channel 132), it must:&lt;/P&gt;&lt;P&gt;Immediately stop transmissions and vacate the channel within 1 second.&lt;BR /&gt;Avoid using the detected channel for at least 30 minutes (called the Non-Occupancy Period).&lt;BR /&gt;Select a new channel, either a non-DFS channel (preferred) or another DFS channel (which requires a Channel Availability Check).&lt;BR /&gt;Key Regulation (FCC, ETSI, etc.):&lt;/P&gt;&lt;P&gt;30-minute Non-Occupancy Period: The AP must not use the detected channel for at least 30 minutes after radar detection.&lt;/P&gt;&lt;P&gt;&lt;BR /&gt;2.) AP Behavior After Radar Detection&lt;BR /&gt;Case 1: Non-DFS Channel Available&lt;BR /&gt;&lt;span class="lia-unicode-emoji" title=":white_heavy_check_mark:"&gt;✅&lt;/span&gt;AP moves immediately to a non-DFS channel and resumes operation.&lt;/P&gt;&lt;P&gt;Case 2: Another DFS Channel is Selected&lt;BR /&gt;&lt;span class="lia-unicode-emoji" title=":white_heavy_check_mark:"&gt;✅&lt;/span&gt;AP moves to another DFS channel but must perform a Channel Availability Check (CAC):&lt;BR /&gt;60 seconds of listening for radar before accepting clients.&lt;/P&gt;&lt;P&gt;Case 3: No Other Channels Available&lt;BR /&gt;&lt;span class="lia-unicode-emoji" title=":hourglass_not_done:"&gt;⏳&lt;/span&gt;The AP remains offline until a valid channel is assigned.&lt;/P&gt;&lt;P&gt;3.) Can the AP Reuse Channel 132 Before 30 Minutes?&lt;BR /&gt;No, the AP must wait 30 minutes before reusing Channel 132.&lt;BR /&gt;Even if RRM selects Channel 132, the AP must reject it if it’s within the Non-Occupancy Period.&lt;/P&gt;</description>
      <pubDate>Tue, 11 Feb 2025 10:37:02 GMT</pubDate>
      <guid>https://community.cisco.com/t5/wireless/ap-behavior-when-detecting-radar-on-dfs-channels/m-p/5259046#M280780</guid>
      <dc:creator>bakaholic39</dc:creator>
      <dc:date>2025-02-11T10:37:02Z</dc:date>
    </item>
    <item>
      <title>Re: AP behabior when detecting radar on DFS channels</title>
      <link>https://community.cisco.com/t5/wireless/ap-behavior-when-detecting-radar-on-dfs-channels/m-p/5259056#M280781</link>
      <description>&lt;P&gt;&lt;a href="https://community.cisco.com/t5/user/viewprofilepage/user-id/1547404"&gt;@bakaholic39&lt;/a&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;The only information I think is not right is this "&lt;SPAN&gt;Even if RRM selects Channel 132, the AP must reject it if it’s within the Non-Occupancy Period."&lt;/SPAN&gt;&lt;/P&gt;
&lt;DIV class="lia-rating-metoo lia-component-me-too lia-component-message-view-widget-me-too"&gt;
&lt;DIV class="RatingDisplay lia-component-ratings-widget-rating-display"&gt;
&lt;DIV id="ratingenumerationdisplay" class="lia-rating-enumeration-system-forum_topic_metoo lia-rating-enumeration rating-enum-5259046-forum_topic_metoo"&gt;
&lt;DIV class="lia-button-group-left"&gt;&amp;nbsp;&lt;/DIV&gt;
&lt;/DIV&gt;
&lt;/DIV&gt;
&lt;/DIV&gt;
&lt;DIV id="labelsWithEvent" class="LabelsForArticle lia-component-labels lia-component-message-view-widget-labels-with-event"&gt;
&lt;DIV class="LabelsList"&gt;&amp;nbsp;If the AP is joined in a WLC and subjected to RRM I dont believe it can reject channel by itself.&amp;nbsp; If you read this in some documentation, please, share here.&amp;nbsp;&lt;/DIV&gt;
&lt;/DIV&gt;</description>
      <pubDate>Tue, 11 Feb 2025 10:31:50 GMT</pubDate>
      <guid>https://community.cisco.com/t5/wireless/ap-behavior-when-detecting-radar-on-dfs-channels/m-p/5259056#M280781</guid>
      <dc:creator>Flavio Miranda</dc:creator>
      <dc:date>2025-02-11T10:31:50Z</dc:date>
    </item>
    <item>
      <title>Re: AP behabior when detecting radar on DFS channels</title>
      <link>https://community.cisco.com/t5/wireless/ap-behavior-when-detecting-radar-on-dfs-channels/m-p/5259058#M280782</link>
      <description>&lt;P&gt;Hello Flavio,&lt;/P&gt;&lt;P&gt;Thanks for sharing, this is just my understading, may be I'm miss. But for the AP could not reuse the same DFS channel again after detecting a radar for 30 mins, is it right on a Cisco wireless?, if this behavior is a standard, this can apply to every vendors?&lt;/P&gt;</description>
      <pubDate>Tue, 11 Feb 2025 10:36:12 GMT</pubDate>
      <guid>https://community.cisco.com/t5/wireless/ap-behavior-when-detecting-radar-on-dfs-channels/m-p/5259058#M280782</guid>
      <dc:creator>bakaholic39</dc:creator>
      <dc:date>2025-02-11T10:36:12Z</dc:date>
    </item>
    <item>
      <title>Re: AP behavior when detecting radar on DFS channels</title>
      <link>https://community.cisco.com/t5/wireless/ap-behavior-when-detecting-radar-on-dfs-channels/m-p/5259068#M280783</link>
      <description>&lt;P&gt;To add more, in Cisco, if the Cisco AP is configured to use a wide channel (40-, 80-MHz wide) it will turn to 20-MHz channel in whatever new channel it would be, and even when it turns to use the previous DFS impacted channel (132 in your example). Bonding channels won't be available until next RRM calculation.&lt;/P&gt;</description>
      <pubDate>Tue, 11 Feb 2025 11:06:24 GMT</pubDate>
      <guid>https://community.cisco.com/t5/wireless/ap-behavior-when-detecting-radar-on-dfs-channels/m-p/5259068#M280783</guid>
      <dc:creator>JPavonM</dc:creator>
      <dc:date>2025-02-11T11:06:24Z</dc:date>
    </item>
    <item>
      <title>Re: AP behabior when detecting radar on DFS channels</title>
      <link>https://community.cisco.com/t5/wireless/ap-behavior-when-detecting-radar-on-dfs-channels/m-p/5259069#M280784</link>
      <description>&lt;P&gt;&lt;a href="https://community.cisco.com/t5/user/viewprofilepage/user-id/1547404"&gt;@bakaholic39&lt;/a&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Yes, this Will apply to all vendor because this is regulared for agencies around the world. What can vary is the Channels that Will be using.&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Tue, 11 Feb 2025 11:19:02 GMT</pubDate>
      <guid>https://community.cisco.com/t5/wireless/ap-behavior-when-detecting-radar-on-dfs-channels/m-p/5259069#M280784</guid>
      <dc:creator>Flavio Miranda</dc:creator>
      <dc:date>2025-02-11T11:19:02Z</dc:date>
    </item>
    <item>
      <title>Re: AP behabior when detecting radar on DFS channels</title>
      <link>https://community.cisco.com/t5/wireless/ap-behavior-when-detecting-radar-on-dfs-channels/m-p/5259071#M280785</link>
      <description>&lt;P&gt;This is my understanding as well - if&amp;nbsp;a radar signal is detected on a DFS channel, the AP and its clients must stop using it for 30 minutes and move to a different channel. This is standardised in 802.11h in order to avoid&lt;SPAN&gt; co-channel interference with systems that predated Wi-Fi like military or weather radars&lt;/SPAN&gt;.&lt;/P&gt;
&lt;P&gt;HTH&lt;/P&gt;</description>
      <pubDate>Tue, 11 Feb 2025 11:26:49 GMT</pubDate>
      <guid>https://community.cisco.com/t5/wireless/ap-behavior-when-detecting-radar-on-dfs-channels/m-p/5259071#M280785</guid>
      <dc:creator>liviu.gheorghe</dc:creator>
      <dc:date>2025-02-11T11:26:49Z</dc:date>
    </item>
  </channel>
</rss>

