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.
![caf88a5629f94fcda47a7163f3cb2ec3_RackMultipart20170406-107092-1vsfe5u-HA-topologia2_inline.jpg caf88a5629f94fcda47a7163f3cb2ec3_RackMultipart20170406-107092-1vsfe5u-HA-topologia2_inline.jpg](/t5/image/serverpage/image-id/2904i2048F1A318E8AA8C/image-size/large?v=v2&px=999)
We note that in the configuration of APs these four interfaces appear as failover addresses:
![caf88a5629f94fcda47a7163f3cb2ec3_RackMultipart20170406-45618-bko9ts-HA-ap-cfg_inline.jpg caf88a5629f94fcda47a7163f3cb2ec3_RackMultipart20170406-45618-bko9ts-HA-ap-cfg_inline.jpg](/t5/image/serverpage/image-id/4873i273861AA77B34823/image-size/large?v=v2&px=999)
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.
![caf88a5629f94fcda47a7163f3cb2ec3_RackMultipart20170406-81143-1dwsbrc-HA-dump-icmp_inline.jpg caf88a5629f94fcda47a7163f3cb2ec3_RackMultipart20170406-81143-1dwsbrc-HA-dump-icmp_inline.jpg](/t5/image/serverpage/image-id/1147i095A4FC9D9589525/image-size/large?v=v2&px=999)
Here's the questions: would these network configurations be incompatible with HA FastFailover and why do APs test connectivity with esa3?
Tks.