<?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 Maintaining Wireless Services upon HiPath Controller loss in FAQs</title>
    <link>https://community.extremenetworks.com/t5/faqs/maintaining-wireless-services-upon-hipath-controller-loss/m-p/41211#M39</link>
    <description>Article ID: 13789 &lt;BR /&gt;
&lt;BR /&gt;
&lt;B&gt;Products&lt;/B&gt;&lt;BR /&gt;
C4110, C5110, C20, C20N, CRBT8110, CRBT82110, C2400&lt;BR /&gt;
AP3610, AP3620, AP3605, AP2605, RBT-4102(all variants), AP2610, AP2620 &lt;BR /&gt;
&lt;BR /&gt;
&lt;B&gt;Symptoms&lt;/B&gt;&lt;BR /&gt;
Clients drop service during a non-redundant controller outage.&lt;BR /&gt;
Access Point (AP) reboots during a controller outage and no available backup controller is available.&lt;BR /&gt;
Remote Access Points across a WAN link reboot when the connection to the controller is offline. &lt;BR /&gt;
&lt;BR /&gt;
&lt;B&gt;Solution/Workaround&lt;/B&gt;&lt;BR /&gt;
In order to maintain wireless services in the event the HiPath controller goes offline, it is important to understand that the ability to keep the Access Points' clients online with no reboot can only be achieved with a "Bridge at Access Point" topology. The "Bridge at Controller" and "Routed" topologies do not support this ability. &lt;BR /&gt;
&lt;BR /&gt;
Activation of the "Bridge at Access Point" function must be enabled per Access Point. Use the HiPath Wireless Assistant (Web GUI), found under &lt;DIV class="threadCode"&gt;&lt;B&gt;code:&lt;/B&gt;&lt;PRE spellcheck="false"&gt;Wireless APs&lt;/PRE&gt;&lt;/DIV&gt;, select an AP or use multi-edit, then select the "&lt;DIV class="threadCode"&gt;&lt;B&gt;code:&lt;/B&gt;&lt;PRE spellcheck="false"&gt;Advanced&lt;/PRE&gt;&lt;/DIV&gt;" tab in the AP Properties Window, and enable these features:&lt;BR /&gt;
&lt;DIV class="threadCode"&gt;&lt;B&gt;code:&lt;/B&gt;&lt;PRE spellcheck="false"&gt;- Maintain client sessions in event of poll failure&lt;/PRE&gt;&lt;/DIV&gt;&lt;BR /&gt;
&lt;DIV class="threadCode"&gt;&lt;B&gt;code:&lt;/B&gt;&lt;PRE spellcheck="false"&gt;- Restart service in the absence of controller&lt;/PRE&gt;&lt;/DIV&gt; &lt;BR /&gt;
&lt;BR /&gt;
&lt;U&gt;Supported Configuration Matrix:&lt;/U&gt; &lt;BR /&gt;
&lt;BR /&gt;
Note: In this matrix, 'B@AP' means "Bridge at Access Point", and 'B@HWC' means "Bridge at Controller".                                          The Access Point   Associated clients&lt;BR /&gt;
             VNS - NonAuth   VNS - Auth   accepts new client  still continue to&lt;BR /&gt;
 Encryption  Topo_Traffic   Topo_Traffic    associations.       pass traffic.&lt;BR /&gt;
 &lt;BR /&gt;
 WPA-PSK,       B@AP           B@AP             Yes                 Yes&lt;BR /&gt;
Static WEP&lt;BR /&gt;
             The Controller link going down has no impact on the clients'&lt;BR /&gt;
             ability to roam, associate, or pass traffic.&lt;BR /&gt;
 &lt;BR /&gt;
 WPA-PSK,      B@HWC           B@AP             No                  Yes&lt;BR /&gt;
Static WEP&lt;BR /&gt;
             The Controller link going down allows already connected clients to&lt;BR /&gt;
             continue to pass traffic; but any new clients coming on during the&lt;BR /&gt;
             outage will fail and any clients that roam from AP to AP will fail.&lt;BR /&gt;
 &lt;BR /&gt;
 MAC-Auth,      B@AP           B@AP             No                  Yes&lt;BR /&gt;
  802.1x,&lt;BR /&gt;
Web Portal&lt;BR /&gt;
             The Controller link going down allows already connected and&lt;BR /&gt;
             authenticated clients to continue to pass traffic; but any new&lt;BR /&gt;
             clients coming on during the outage will fail and any clients that&lt;BR /&gt;
             roam from AP to AP will fail.&lt;BR /&gt;
 &lt;BR /&gt;
 MAC-Auth,     B@HWC           B@AP             No                  Yes&lt;BR /&gt;
  802.1x,&lt;BR /&gt;
Web Portal&lt;BR /&gt;
             The Controller link going down allows already connected and&lt;BR /&gt;
             authenticated clients to continue to pass traffic; but any new&lt;BR /&gt;
             clients coming on during the outage will fail and any clients that&lt;BR /&gt;
             roam from AP to AP will fail.&lt;BR /&gt;
 &lt;BR /&gt;
Any Service  B@HWC/Routed   B@HWC/Routed        No                  No&lt;BR /&gt;
 &lt;BR /&gt;
             The Controller link going down provides no services at all; the&lt;BR /&gt;
             Access Point reboots.</description>
    <pubDate>Wed, 01 Jan 2014 01:52:00 GMT</pubDate>
    <dc:creator>FAQ_User</dc:creator>
    <dc:date>2014-01-01T01:52:00Z</dc:date>
    <item>
      <title>Maintaining Wireless Services upon HiPath Controller loss</title>
      <link>https://community.extremenetworks.com/t5/faqs/maintaining-wireless-services-upon-hipath-controller-loss/m-p/41211#M39</link>
      <description>Article ID: 13789 &lt;BR /&gt;
&lt;BR /&gt;
&lt;B&gt;Products&lt;/B&gt;&lt;BR /&gt;
C4110, C5110, C20, C20N, CRBT8110, CRBT82110, C2400&lt;BR /&gt;
AP3610, AP3620, AP3605, AP2605, RBT-4102(all variants), AP2610, AP2620 &lt;BR /&gt;
&lt;BR /&gt;
&lt;B&gt;Symptoms&lt;/B&gt;&lt;BR /&gt;
Clients drop service during a non-redundant controller outage.&lt;BR /&gt;
Access Point (AP) reboots during a controller outage and no available backup controller is available.&lt;BR /&gt;
Remote Access Points across a WAN link reboot when the connection to the controller is offline. &lt;BR /&gt;
&lt;BR /&gt;
&lt;B&gt;Solution/Workaround&lt;/B&gt;&lt;BR /&gt;
In order to maintain wireless services in the event the HiPath controller goes offline, it is important to understand that the ability to keep the Access Points' clients online with no reboot can only be achieved with a "Bridge at Access Point" topology. The "Bridge at Controller" and "Routed" topologies do not support this ability. &lt;BR /&gt;
&lt;BR /&gt;
Activation of the "Bridge at Access Point" function must be enabled per Access Point. Use the HiPath Wireless Assistant (Web GUI), found under &lt;DIV class="threadCode"&gt;&lt;B&gt;code:&lt;/B&gt;&lt;PRE spellcheck="false"&gt;Wireless APs&lt;/PRE&gt;&lt;/DIV&gt;, select an AP or use multi-edit, then select the "&lt;DIV class="threadCode"&gt;&lt;B&gt;code:&lt;/B&gt;&lt;PRE spellcheck="false"&gt;Advanced&lt;/PRE&gt;&lt;/DIV&gt;" tab in the AP Properties Window, and enable these features:&lt;BR /&gt;
&lt;DIV class="threadCode"&gt;&lt;B&gt;code:&lt;/B&gt;&lt;PRE spellcheck="false"&gt;- Maintain client sessions in event of poll failure&lt;/PRE&gt;&lt;/DIV&gt;&lt;BR /&gt;
&lt;DIV class="threadCode"&gt;&lt;B&gt;code:&lt;/B&gt;&lt;PRE spellcheck="false"&gt;- Restart service in the absence of controller&lt;/PRE&gt;&lt;/DIV&gt; &lt;BR /&gt;
&lt;BR /&gt;
&lt;U&gt;Supported Configuration Matrix:&lt;/U&gt; &lt;BR /&gt;
&lt;BR /&gt;
Note: In this matrix, 'B@AP' means "Bridge at Access Point", and 'B@HWC' means "Bridge at Controller".                                          The Access Point   Associated clients&lt;BR /&gt;
             VNS - NonAuth   VNS - Auth   accepts new client  still continue to&lt;BR /&gt;
 Encryption  Topo_Traffic   Topo_Traffic    associations.       pass traffic.&lt;BR /&gt;
 &lt;BR /&gt;
 WPA-PSK,       B@AP           B@AP             Yes                 Yes&lt;BR /&gt;
Static WEP&lt;BR /&gt;
             The Controller link going down has no impact on the clients'&lt;BR /&gt;
             ability to roam, associate, or pass traffic.&lt;BR /&gt;
 &lt;BR /&gt;
 WPA-PSK,      B@HWC           B@AP             No                  Yes&lt;BR /&gt;
Static WEP&lt;BR /&gt;
             The Controller link going down allows already connected clients to&lt;BR /&gt;
             continue to pass traffic; but any new clients coming on during the&lt;BR /&gt;
             outage will fail and any clients that roam from AP to AP will fail.&lt;BR /&gt;
 &lt;BR /&gt;
 MAC-Auth,      B@AP           B@AP             No                  Yes&lt;BR /&gt;
  802.1x,&lt;BR /&gt;
Web Portal&lt;BR /&gt;
             The Controller link going down allows already connected and&lt;BR /&gt;
             authenticated clients to continue to pass traffic; but any new&lt;BR /&gt;
             clients coming on during the outage will fail and any clients that&lt;BR /&gt;
             roam from AP to AP will fail.&lt;BR /&gt;
 &lt;BR /&gt;
 MAC-Auth,     B@HWC           B@AP             No                  Yes&lt;BR /&gt;
  802.1x,&lt;BR /&gt;
Web Portal&lt;BR /&gt;
             The Controller link going down allows already connected and&lt;BR /&gt;
             authenticated clients to continue to pass traffic; but any new&lt;BR /&gt;
             clients coming on during the outage will fail and any clients that&lt;BR /&gt;
             roam from AP to AP will fail.&lt;BR /&gt;
 &lt;BR /&gt;
Any Service  B@HWC/Routed   B@HWC/Routed        No                  No&lt;BR /&gt;
 &lt;BR /&gt;
             The Controller link going down provides no services at all; the&lt;BR /&gt;
             Access Point reboots.</description>
      <pubDate>Wed, 01 Jan 2014 01:52:00 GMT</pubDate>
      <guid>https://community.extremenetworks.com/t5/faqs/maintaining-wireless-services-upon-hipath-controller-loss/m-p/41211#M39</guid>
      <dc:creator>FAQ_User</dc:creator>
      <dc:date>2014-01-01T01:52:00Z</dc:date>
    </item>
  </channel>
</rss>

