debug application hatalk
Use this command to set the verbosity level and type of debug logs for HA heartbeats.
Before you will be able to see any debug logs, you must first enable debug log output using the command
diagnose debug.
To use this command, your administrator account’s access control profile requires only r permission in any profile area.
Syntax
Variable | Description | Default |
[{-1 | 0 | 1 | 2}] | Optionally, type the number indicating the verbosity level and type of debugging messages to output to the CLI display after the command executes. • -1 — Display all messages. • 0 — Do not display messages. • 1 — Display application messages such as MD5 checksums for the configuration, and confirmation that the standby appliance received the synchronized data. • 2 — Display network transmission messages, such as ARP broadcasts and bridge down/up status changes. If you omit the number, the CLI displays the current verbosity level: hatalk debug level is 0 | 0 |
Example
This example enables diagnostic debug logging in general, then specifically enables complete debug logging of the HA heartbeat daemon, hatalkd.
diagnose debug enable
diagnose debug application hatalk -1
The CLI displays output such as the following until the command is terminated:
FortiWeb # (ha_hb.c : 176) : mem-table[0]:
(ha_hb.c : 61) : member name : wasp
(ha_hb.c : 62) : member pcnt : 0
(ha_hb.c : 63) : member pri : 5
(ha_hb.c : 64) : member sn : FV-1KC3R11700136
(ha_hb.c : 65) : member age : 11209
(ha_hb.c : 66) : member role : 1
(intf_check.c : 273) : clicfg->monitor_count : 1, count : 1
(ha_hb_send.c : 85) : sock : 26, sendlen : 264(head: 88, mem(2) 88)
(ha_hb_send.c : 104) : Send HB buf success.
(ha_hb.c : 83) : Enter Function : get_master_sn
(ha_hb.c : 756) : -------------------------
(ha_hb.c : 760) : ==> HB..., I'am (Master) master is : FV-1KC3R11700094
(ha_hb.c : 637) : update my status info : FV-1KC3R11700094
(ha_hb.c : 871) : Enter Fun : hb_packet_check
(ha_hb.c : 897) : mysn : FV-1KC3R11700094(0), comesn : FV-1KC3R11700136(1)
(ha_hb_recv.c : 446) : Got an valid HB packet(port3), len : 176
(ha_hb_recv.c : 451) : come from : FV-1KC3R11700136
(ha_hb_recv.c : 104) : fill ha member to local
(ha_hb_recv.c : 251) : slave (FV-1KC3R11700136) arrived ...
(ha_hb_recv.c : 342) : An exist slave device arrive...
(ha_hb_recv.c : 512) : sockfd1 : 200(UP), sockfd2 : 0(DOWN)
(ha_hb.c : 159) : Enter Function : print_member_tab
(ha_hb.c : 166) : total cnt : 2
(output truncated)
(main.c : 1005) : send short cli msg to :
FV-1KC3R11700136
(main.c : 1349) : switch MASTER -> SLAVE
(main.c : 1350) : block ARP
(main.c : 1219) : HA device into Slave mode
(main.c : 1220) : device block ARP
(main.c : 1121) : Get BrgInfo, my brgCnt = 0
The results indicate that the HA cluster is named wasp (group ID 0, HA link over port3). It is formed by the active appliance FV‑1KC3R11700094 (device priority 5) and the standby appliance FV-1KC3R11700136. The two appliances then switched rules — that is, a failover occurred.
Related topics