Version:

Version:

Version:

Version:

Version:

Version:

Version:

Version:

Version:

Version:

Version:

Version:

Version:


Table of Contents

CLI Reference

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

To use this command, your administrator account’s access control profile requires only r permission in any profile area. For details, see Permissions.

Syntax

diagnose debug application hatalk {0 | 1 | 2 | 3 | 4 | 5 | 6 | 7}

Variable Description Default

{0 | 1 | 2 | 3 | 4 | 5 | 6 | 7}

Enter the number indicating the verbosity level and type of debugging messages to output to the CLI display after the command executes.

  • 0—Do not display messages.
  • 1—Display heartbeat process initialization messages.
  • 2—Display monitor port related messages.
  • 3—Display member change, external process communication related messages.
  • 4—None.
  • 5—Display member massages sent to Kernal.
  • 6—Display current status, and role messages.
  • 7—Display all messages.

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 6

The CLI displays output such as the following until the command is terminated:

FortiWeb # (ha_timer.c : 305) [87040]syncronized 2 nodes!

(ha_timer.c : 428) hamain[87040949] mode 2, role 1,1, phase 2, narps 0, skip 0

(ha_timer.c : 305) [87041]syncronized 2 nodes!

(ha_timer.c : 428) hamain[87041949] mode 2, role 1,1, phase 2, narps 0, skip 0

(ha_timer.c : 305) [87042]syncronized 2 nodes!

(ha_timer.c : 428) hamain[87042949] mode 2, role 1,1, phase 2, narps 0, skip 0

(ha_timer.c : 305) [87043]syncronized 2 nodes!

(ha_timer.c : 428) hamain[87043948] mode 2, role 1,1, phase 2, narps 0, skip 0

(ha_timer.c : 305) [87044]syncronized 2 nodes!

(ha_timer.c : 428) hamain[87044948] mode 2, role 1,1, phase 2, narps 0, skip 0

(ha_timer.c : 305) [87045]syncronized 2 nodes!

(ha_timer.c : 428) hamain[87045948] mode 2, role 1,1, phase 2, narps 0, skip 0

(ha_timer.c : 305) [87046]syncronized 2 nodes!

(ha_timer.c : 428) hamain[87046948] mode 2, role 1,1, phase 2, narps 0, skip 0

(ha_timer.c : 305) [87047]syncronized 2 nodes!

(ha_timer.c : 428) hamain[87047948] mode 2, role 1,1, phase 2, narps 0, skip 0

(ha_timer.c : 305) [87048]syncronized 2 nodes!

Related topics

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

To use this command, your administrator account’s access control profile requires only r permission in any profile area. For details, see Permissions.

Syntax

diagnose debug application hatalk {0 | 1 | 2 | 3 | 4 | 5 | 6 | 7}

Variable Description Default

{0 | 1 | 2 | 3 | 4 | 5 | 6 | 7}

Enter the number indicating the verbosity level and type of debugging messages to output to the CLI display after the command executes.

  • 0—Do not display messages.
  • 1—Display heartbeat process initialization messages.
  • 2—Display monitor port related messages.
  • 3—Display member change, external process communication related messages.
  • 4—None.
  • 5—Display member massages sent to Kernal.
  • 6—Display current status, and role messages.
  • 7—Display all messages.

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 6

The CLI displays output such as the following until the command is terminated:

FortiWeb # (ha_timer.c : 305) [87040]syncronized 2 nodes!

(ha_timer.c : 428) hamain[87040949] mode 2, role 1,1, phase 2, narps 0, skip 0

(ha_timer.c : 305) [87041]syncronized 2 nodes!

(ha_timer.c : 428) hamain[87041949] mode 2, role 1,1, phase 2, narps 0, skip 0

(ha_timer.c : 305) [87042]syncronized 2 nodes!

(ha_timer.c : 428) hamain[87042949] mode 2, role 1,1, phase 2, narps 0, skip 0

(ha_timer.c : 305) [87043]syncronized 2 nodes!

(ha_timer.c : 428) hamain[87043948] mode 2, role 1,1, phase 2, narps 0, skip 0

(ha_timer.c : 305) [87044]syncronized 2 nodes!

(ha_timer.c : 428) hamain[87044948] mode 2, role 1,1, phase 2, narps 0, skip 0

(ha_timer.c : 305) [87045]syncronized 2 nodes!

(ha_timer.c : 428) hamain[87045948] mode 2, role 1,1, phase 2, narps 0, skip 0

(ha_timer.c : 305) [87046]syncronized 2 nodes!

(ha_timer.c : 428) hamain[87046948] mode 2, role 1,1, phase 2, narps 0, skip 0

(ha_timer.c : 305) [87047]syncronized 2 nodes!

(ha_timer.c : 428) hamain[87047948] mode 2, role 1,1, phase 2, narps 0, skip 0

(ha_timer.c : 305) [87048]syncronized 2 nodes!

Related topics