<?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-adoption convergence time in ExtremeWireless (WiNG)</title>
    <link>https://community.extremenetworks.com/t5/extremewireless-wing/re-adoption-convergence-time/m-p/75431#M6978</link>
    <description>&lt;P&gt;Hi!&lt;/P&gt;&lt;P&gt;maybe who knows, how to boost re-adoption time for APs, when 1 controller of cluster goes down (link or itself). I’ve tested. It tooks about 1 minute, when AP decided to re-adopt to another member of cluster. Mode bridging is tunnel. IT is a&amp;nbsp;business critical question)&lt;/P&gt;</description>
    <pubDate>Tue, 01 Sep 2020 18:41:41 GMT</pubDate>
    <dc:creator>karayafrog</dc:creator>
    <dc:date>2020-09-01T18:41:41Z</dc:date>
    <item>
      <title>re-adoption convergence time</title>
      <link>https://community.extremenetworks.com/t5/extremewireless-wing/re-adoption-convergence-time/m-p/75431#M6978</link>
      <description>&lt;P&gt;Hi!&lt;/P&gt;&lt;P&gt;maybe who knows, how to boost re-adoption time for APs, when 1 controller of cluster goes down (link or itself). I’ve tested. It tooks about 1 minute, when AP decided to re-adopt to another member of cluster. Mode bridging is tunnel. IT is a&amp;nbsp;business critical question)&lt;/P&gt;</description>
      <pubDate>Tue, 01 Sep 2020 18:41:41 GMT</pubDate>
      <guid>https://community.extremenetworks.com/t5/extremewireless-wing/re-adoption-convergence-time/m-p/75431#M6978</guid>
      <dc:creator>karayafrog</dc:creator>
      <dc:date>2020-09-01T18:41:41Z</dc:date>
    </item>
  </channel>
</rss>

