|
Refer 1+1 fast failover configuration using the below link: FortiGate WiFi controller 1+1 fast failover example
FortiAP will show 'run' on primary FortiGate and 'run-standby' on Secondary FortiGate.
Commands to check on FortiAP:
FortiAP# cw_diag -c ha
Current AC: 192.168.20.1:5246 pri 1
WC fast failover AC mode : 2
WC fast failover peer cnt: 1
Discovered AC list:
ip=192.168.20.2 allow=1 pri=2 dtls=3 wtp=0/4096 sta=0/65535
ip=192.168.20.1 allow=1 pri=1 dtls=3 wtp=3/4096 sta=0/65535
FortiAP# cw_diag -c acs
ACS 0 info
wcha info : mode=2 max=10 wait=10 peer_cnt=1
acPri : 1
peer-00 : FG3K2D3Z1580xxxx ip=192.168.20.2:5246 pri=2 pstate=1
fsm-state : RUN 3584
ac-ip-addr : 192.168.20.1:5246,5247 BROADCAST
ac-name : FG1K5D3I1580xxxx
ACS 1 info
wcha info : mode=2 max=10 wait=10 peer_cnt=1
acPri : 2
peer-00 : FG1K5D3I1580xxxx ip=192.168.20.1:5246 pri=1 pstate=1
fsm-state : RUN_STANDBY 711
ac-ip-addr : 192.168.20.2:5246,5247 BROADCAST
ac-name : FG3K2D3Z1580xxxx
AC candidate info:
AC-00 192.168.20.2:5246 2 available 1 score 696310.00 dtlsPolicy clear allow 1 skip 0 until 0 curr 4438
AC-01 192.168.20.1:5246 1 available 1 score 656671.31 dtlsPolicy clear allow 1 skip 0 until 0 curr 4438
FortiAP# kinfo
Ctrl Sess: ac=192.168.20.1:5246 Mesh Ether Type: 0x2233
Data Sess: ac=192.168.20.1:5247 wtp=192.168.20.13:52744 ether_mode=Ether II sec=0 skip_cwol=0
After the failover, the control and data sessions should move to the secondary FortiGate, and the output of the command 'kinfo' should show 'ac=192.168.20.2'.
|
