<?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: Failover between two V2110 is not working in ExtremeWireless (Identifi)</title>
    <link>https://community.extremenetworks.com/t5/extremewireless-identifi/failover-between-two-v2110-is-not-working/m-p/29024#M152</link>
    <description>Upgrading to 10.31.07.0002 didn't solve the problem.&lt;BR /&gt;
&lt;BR /&gt;
The error message is still present, I am going to create GTAC case. &lt;BR /&gt;</description>
    <pubDate>Fri, 10 Nov 2017 20:40:00 GMT</pubDate>
    <dc:creator>Robert_Zdzieblo</dc:creator>
    <dc:date>2017-11-10T20:40:00Z</dc:date>
    <item>
      <title>Failover between two V2110 is not working</title>
      <link>https://community.extremenetworks.com/t5/extremewireless-identifi/failover-between-two-v2110-is-not-working/m-p/29020#M148</link>
      <description>Hello the Hub !&lt;BR /&gt;
&lt;BR /&gt;
I have two V2110 controllers running in availability pair mode.&lt;BR /&gt;
Today the primary V2110 suddenly stopped working - don't know why (probably it was the power issue).&lt;BR /&gt;
&lt;BR /&gt;
The bad thing is that AP's and clients didn't switched to secondary V2110.&lt;BR /&gt;
I have tested this configuration before and we had good failover behaviour.&lt;BR /&gt;
There was no change in configuration since then.&lt;BR /&gt;
 &lt;BR /&gt;
I have repeating log massege (major severity):&lt;BR /&gt;
&lt;BR /&gt;
Config Manager has experienced an error which has prevented it from   properly processing a request.  CM will continue running, however this   error may be an indicator of a larger system &lt;BR /&gt;
problem. Error   Details:Error updating table [/var/controller/data/db/phyport.bin] id   [2]&lt;BR /&gt;
&lt;BR /&gt;
- could it be related somehow to failover behaviour ?&lt;BR /&gt;
&lt;BR /&gt;
The software is 10.11.05.0005.&lt;BR /&gt;
&lt;BR /&gt;
Did anyone experience something like that ?&lt;BR /&gt;
&lt;BR /&gt;
REGARDS&lt;BR /&gt;
Robert&lt;BR /&gt;
&lt;BR /&gt;</description>
      <pubDate>Mon, 16 Oct 2017 17:37:00 GMT</pubDate>
      <guid>https://community.extremenetworks.com/t5/extremewireless-identifi/failover-between-two-v2110-is-not-working/m-p/29020#M148</guid>
      <dc:creator>Robert_Zdzieblo</dc:creator>
      <dc:date>2017-10-16T17:37:00Z</dc:date>
    </item>
    <item>
      <title>RE: Failover between two V2110 is not working</title>
      <link>https://community.extremenetworks.com/t5/extremewireless-identifi/failover-between-two-v2110-is-not-working/m-p/29021#M149</link>
      <description>Hi Robert,&lt;BR /&gt;
&lt;BR /&gt;
The reoccurring log message should cease if you are able to upgrade to a more recent version of firmware (10.41.x.x or 10.31.06.x). If there are issues with the failover behaviour on these versions of firmware then you should open a support case with GTAC and provide the logs for us to investigate. &lt;BR /&gt;
&lt;BR /&gt;
Best regards,&lt;BR /&gt;
Sam</description>
      <pubDate>Mon, 16 Oct 2017 18:11:00 GMT</pubDate>
      <guid>https://community.extremenetworks.com/t5/extremewireless-identifi/failover-between-two-v2110-is-not-working/m-p/29021#M149</guid>
      <dc:creator>Sam</dc:creator>
      <dc:date>2017-10-16T18:11:00Z</dc:date>
    </item>
    <item>
      <title>RE: Failover between two V2110 is not working</title>
      <link>https://community.extremenetworks.com/t5/extremewireless-identifi/failover-between-two-v2110-is-not-working/m-p/29022#M150</link>
      <description>Hello Robert&lt;BR /&gt;
&lt;BR /&gt;
We shown similar log messages on wireless controller, but the issue was solved after upgrading firmware. &lt;BR /&gt;
&lt;BR /&gt;
&lt;A href="https://gtacknowledge.extremenetworks.com/articles/Solution/Wireless-Appliance-is-reporting-the-following-log-message-The-erroneous-encoded-configuration-item-is-0068000B" target="_blank" rel="nofollow noreferrer noopener"&gt;https://gtacknowledge.extremenetworks.com/articles/Solution/Wireless-Appliance-is-reporting-the-foll...&lt;/A&gt; &lt;BR /&gt;
&lt;BR /&gt;
Agree with Sam's suggestion. Could you update to the recent version firmware if it is possible.&lt;BR /&gt;
&lt;BR /&gt;
Best regards,&lt;BR /&gt;
&lt;BR /&gt;</description>
      <pubDate>Tue, 17 Oct 2017 03:28:00 GMT</pubDate>
      <guid>https://community.extremenetworks.com/t5/extremewireless-identifi/failover-between-two-v2110-is-not-working/m-p/29022#M150</guid>
      <dc:creator>Bin</dc:creator>
      <dc:date>2017-10-17T03:28:00Z</dc:date>
    </item>
    <item>
      <title>RE: Failover between two V2110 is not working</title>
      <link>https://community.extremenetworks.com/t5/extremewireless-identifi/failover-between-two-v2110-is-not-working/m-p/29023#M151</link>
      <description>Thank you guys,&lt;BR /&gt;
&lt;BR /&gt;
I'll put new version nad check.&lt;BR /&gt;
&lt;BR /&gt;
Regards, &lt;BR /&gt;
Robert</description>
      <pubDate>Tue, 17 Oct 2017 11:28:00 GMT</pubDate>
      <guid>https://community.extremenetworks.com/t5/extremewireless-identifi/failover-between-two-v2110-is-not-working/m-p/29023#M151</guid>
      <dc:creator>Robert_Zdzieblo</dc:creator>
      <dc:date>2017-10-17T11:28:00Z</dc:date>
    </item>
    <item>
      <title>RE: Failover between two V2110 is not working</title>
      <link>https://community.extremenetworks.com/t5/extremewireless-identifi/failover-between-two-v2110-is-not-working/m-p/29024#M152</link>
      <description>Upgrading to 10.31.07.0002 didn't solve the problem.&lt;BR /&gt;
&lt;BR /&gt;
The error message is still present, I am going to create GTAC case. &lt;BR /&gt;</description>
      <pubDate>Fri, 10 Nov 2017 20:40:00 GMT</pubDate>
      <guid>https://community.extremenetworks.com/t5/extremewireless-identifi/failover-between-two-v2110-is-not-working/m-p/29024#M152</guid>
      <dc:creator>Robert_Zdzieblo</dc:creator>
      <dc:date>2017-11-10T20:40:00Z</dc:date>
    </item>
    <item>
      <title>RE: Failover between two V2110 is not working</title>
      <link>https://community.extremenetworks.com/t5/extremewireless-identifi/failover-between-two-v2110-is-not-working/m-p/29025#M153</link>
      <description>Hi Robert - Just want to make sure the Virtual Server itself is OK?  Nothing wring with the ports there?&lt;BR /&gt;
&lt;BR /&gt;
Please also include the tech support files from both V2110s when you open the Case.</description>
      <pubDate>Fri, 10 Nov 2017 20:57:00 GMT</pubDate>
      <guid>https://community.extremenetworks.com/t5/extremewireless-identifi/failover-between-two-v2110-is-not-working/m-p/29025#M153</guid>
      <dc:creator>Scott_Whall</dc:creator>
      <dc:date>2017-11-10T20:57:00Z</dc:date>
    </item>
    <item>
      <title>RE: Failover between two V2110 is not working</title>
      <link>https://community.extremenetworks.com/t5/extremewireless-identifi/failover-between-two-v2110-is-not-working/m-p/29026#M154</link>
      <description>With remote support from GTAC, we tried repairing file system with FSCK in rescue mode, however same error showed up. We then redeployed a new V2110 and upgraded it to version 10.31.07.0002, rehosted the licenses, and got the configuration imported from the original controller.&lt;BR /&gt;
The new V2110 is now operating without the errors.&lt;BR /&gt;
&lt;BR /&gt;
Many thanks to Ryan Careno from GTAC team !</description>
      <pubDate>Wed, 22 Nov 2017 16:36:00 GMT</pubDate>
      <guid>https://community.extremenetworks.com/t5/extremewireless-identifi/failover-between-two-v2110-is-not-working/m-p/29026#M154</guid>
      <dc:creator>Robert_Zdzieblo</dc:creator>
      <dc:date>2017-11-22T16:36:00Z</dc:date>
    </item>
  </channel>
</rss>

