<?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: HA Configuration on C5210 in ExtremeWireless (Identifi)</title>
    <link>https://community.extremenetworks.com/t5/extremewireless-identifi/ha-configuration-on-c5210/m-p/51959#M5613</link>
    <description>We usually do yes to free the port to be used for other things, but your design is still valid, just not the norm....</description>
    <pubDate>Fri, 07 Apr 2017 00:51:00 GMT</pubDate>
    <dc:creator>Craig_Guilmette</dc:creator>
    <dc:date>2017-04-07T00:51:00Z</dc:date>
    <item>
      <title>HA Configuration on C5210</title>
      <link>https://community.extremenetworks.com/t5/extremewireless-identifi/ha-configuration-on-c5210/m-p/51956#M5610</link>
      <description>In one installation we have a pair of C5210 in HA mode with fast failover enabled.&lt;BR /&gt;
&lt;BR /&gt;
The network of registration of APs is 10.90.x.x in esa1 and the network HA is 1.1.1.x directly connected by esa3.&lt;BR /&gt;
&lt;BR /&gt;
&lt;P class="fancybox-image"&gt;&lt;span class="lia-inline-image-display-wrapper" image-alt="caf88a5629f94fcda47a7163f3cb2ec3_RackMultipart20170406-107092-1vsfe5u-HA-topologia2_inline.jpg"&gt;&lt;img src="https://community.extremenetworks.com/t5/image/serverpage/image-id/2904i2048F1A318E8AA8C/image-size/large?v=v2&amp;amp;px=999" role="button" title="caf88a5629f94fcda47a7163f3cb2ec3_RackMultipart20170406-107092-1vsfe5u-HA-topologia2_inline.jpg" alt="caf88a5629f94fcda47a7163f3cb2ec3_RackMultipart20170406-107092-1vsfe5u-HA-topologia2_inline.jpg" /&gt;&lt;/span&gt;&lt;/P&gt;&lt;BR /&gt;
&lt;BR /&gt;
We note that in the configuration of APs these four interfaces appear as failover addresses:&lt;BR /&gt;
&lt;BR /&gt;
&lt;P class="fancybox-image"&gt;&lt;span class="lia-inline-image-display-wrapper" image-alt="caf88a5629f94fcda47a7163f3cb2ec3_RackMultipart20170406-45618-bko9ts-HA-ap-cfg_inline.jpg"&gt;&lt;img src="https://community.extremenetworks.com/t5/image/serverpage/image-id/4873i273861AA77B34823/image-size/large?v=v2&amp;amp;px=999" role="button" title="caf88a5629f94fcda47a7163f3cb2ec3_RackMultipart20170406-45618-bko9ts-HA-ap-cfg_inline.jpg" alt="caf88a5629f94fcda47a7163f3cb2ec3_RackMultipart20170406-45618-bko9ts-HA-ap-cfg_inline.jpg" /&gt;&lt;/span&gt;&lt;/P&gt;&lt;BR /&gt;
&lt;BR /&gt;
And in the capture of the packets we noticed that there is an attempt to ping the four interfaces and, of course, without success in the interfaces of HA 1.1.1.x. And this occurs every 1 second.&lt;BR /&gt;
&lt;BR /&gt;
&lt;P class="fancybox-image"&gt;&lt;span class="lia-inline-image-display-wrapper" image-alt="caf88a5629f94fcda47a7163f3cb2ec3_RackMultipart20170406-81143-1dwsbrc-HA-dump-icmp_inline.jpg"&gt;&lt;img src="https://community.extremenetworks.com/t5/image/serverpage/image-id/1147i095A4FC9D9589525/image-size/large?v=v2&amp;amp;px=999" role="button" title="caf88a5629f94fcda47a7163f3cb2ec3_RackMultipart20170406-81143-1dwsbrc-HA-dump-icmp_inline.jpg" alt="caf88a5629f94fcda47a7163f3cb2ec3_RackMultipart20170406-81143-1dwsbrc-HA-dump-icmp_inline.jpg" /&gt;&lt;/span&gt;&lt;/P&gt;&lt;BR /&gt;
&lt;BR /&gt;
Here's the questions: would these network configurations be incompatible with HA FastFailover and why do APs test connectivity with esa3?&lt;BR /&gt;
&lt;BR /&gt;
Tks.</description>
      <pubDate>Fri, 07 Apr 2017 00:37:00 GMT</pubDate>
      <guid>https://community.extremenetworks.com/t5/extremewireless-identifi/ha-configuration-on-c5210/m-p/51956#M5610</guid>
      <dc:creator>Casimiro</dc:creator>
      <dc:date>2017-04-07T00:37:00Z</dc:date>
    </item>
    <item>
      <title>RE: HA Configuration on C5210</title>
      <link>https://community.extremenetworks.com/t5/extremewireless-identifi/ha-configuration-on-c5210/m-p/51957#M5611</link>
      <description>Hello&lt;BR /&gt;
It is because you have ap Registration enabled on those 1.1.1.1 interfaces. The AP's are told of all interfaces with AP reg enabled and they try to reach them in case their primary interface fails. FYI we don't usually suggest using a separate interface for H/A.</description>
      <pubDate>Fri, 07 Apr 2017 00:51:00 GMT</pubDate>
      <guid>https://community.extremenetworks.com/t5/extremewireless-identifi/ha-configuration-on-c5210/m-p/51957#M5611</guid>
      <dc:creator>Craig_Guilmette</dc:creator>
      <dc:date>2017-04-07T00:51:00Z</dc:date>
    </item>
    <item>
      <title>RE: HA Configuration on C5210</title>
      <link>https://community.extremenetworks.com/t5/extremewireless-identifi/ha-configuration-on-c5210/m-p/51958#M5612</link>
      <description>Bingo, AP registration was enabled on the HA interfaces. I removed and corrected the information in the AP configuration:&lt;BR /&gt;
&lt;BR /&gt;
# cat /home/config/current.cfg | grep "failoverIpAddr"&lt;BR /&gt;
cset failoverIpAddr 1 10.90.0.1 Home&lt;BR /&gt;
cset failoverIpAddr 1 10.90.0.2 Foreign&lt;BR /&gt;
&lt;BR /&gt;
But then it is recommended to use the same AP registration interfaces as HA interfaces, in this case to esa1?&lt;BR /&gt;
&lt;BR /&gt;</description>
      <pubDate>Fri, 07 Apr 2017 00:51:00 GMT</pubDate>
      <guid>https://community.extremenetworks.com/t5/extremewireless-identifi/ha-configuration-on-c5210/m-p/51958#M5612</guid>
      <dc:creator>Casimiro</dc:creator>
      <dc:date>2017-04-07T00:51:00Z</dc:date>
    </item>
    <item>
      <title>RE: HA Configuration on C5210</title>
      <link>https://community.extremenetworks.com/t5/extremewireless-identifi/ha-configuration-on-c5210/m-p/51959#M5613</link>
      <description>We usually do yes to free the port to be used for other things, but your design is still valid, just not the norm....</description>
      <pubDate>Fri, 07 Apr 2017 00:51:00 GMT</pubDate>
      <guid>https://community.extremenetworks.com/t5/extremewireless-identifi/ha-configuration-on-c5210/m-p/51959#M5613</guid>
      <dc:creator>Craig_Guilmette</dc:creator>
      <dc:date>2017-04-07T00:51:00Z</dc:date>
    </item>
    <item>
      <title>RE: HA Configuration on C5210</title>
      <link>https://community.extremenetworks.com/t5/extremewireless-identifi/ha-configuration-on-c5210/m-p/51960#M5614</link>
      <description>Thanks, Craig.</description>
      <pubDate>Fri, 07 Apr 2017 00:51:00 GMT</pubDate>
      <guid>https://community.extremenetworks.com/t5/extremewireless-identifi/ha-configuration-on-c5210/m-p/51960#M5614</guid>
      <dc:creator>Casimiro</dc:creator>
      <dc:date>2017-04-07T00:51:00Z</dc:date>
    </item>
  </channel>
</rss>

