HA Configuration on C5210


In one installation we have a pair of C5210 in HA mode with fast failover enabled.

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.



We note that in the configuration of APs these four interfaces appear as failover addresses:



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.



Here's the questions: would these network configurations be incompatible with HA FastFailover and why do APs test connectivity with esa3?

Tks.

4 replies

Userlevel 5
Hello
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.
Craig Guilmette wrote:

Hello
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.

Bingo, AP registration was enabled on the HA interfaces. I removed and corrected the information in the AP configuration:

# cat /home/config/current.cfg | grep "failoverIpAddr"
cset failoverIpAddr 1 10.90.0.1 Home
cset failoverIpAddr 1 10.90.0.2 Foreign

But then it is recommended to use the same AP registration interfaces as HA interfaces, in this case to esa1?
Userlevel 5
Craig Guilmette wrote:

Hello
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.

We usually do yes to free the port to be used for other things, but your design is still valid, just not the norm....
Craig Guilmette wrote:

Hello
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.

Thanks, Craig.

Reply