debug application confd-hamsg

Use this command to set the verbosity level and type of debug logs for HA synchronization.

Before you will be able to see any debug logs, you must first enable debug log output using the command diagnose debug (page 1).

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

Syntax

diagnose debug application confd-hamsg {0 | 1 | 2 | 3 | 4 | 5 | 6 | 7}

Variable Description Default

Variable	Description	Default
confd-hamsg {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 the process initialization failure message. 2—None. 3—Display MD5 checksums message of local host. 4—Display messages that the local host has received and need to be synchronized. 5—Display messages about member change and HA mode that the local host has received.. 6—Display detailed messages of information to be synchronized. 7—Display all messages. If you omit the number, the CLI displays the current verbosity level: `hasync debug level is 0`	0

confd-hamsg {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 the process initialization failure message.
2—None.
3—Display MD5 checksums message of local host.
4—Display messages that the local host has received and need to be synchronized.
5—Display messages about member change and HA mode that the local host has received..
6—Display detailed messages of information to be synchronized.
7—Display all messages.

If you omit the number, the CLI displays the current verbosity level:

hasync debug level is 0

Example

This example enables diagnostic debug logging in general, then specifically enables packet transmission logging of the HA synchronization daemon, confd-hamsg.

diagnose debug enable

diagnose debug application confd-hamsg 5

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

(./lib/confd_generate_md5.c : 103 ) request generate md5sum!

(./lib/confd_generate_md5.c : 149 ) generate md5sum done!

(./sync/confd_md5.c : 158 ) send md5sum request to FVVM020000176885, now:548 pending:0 timeout[60] sync_time:0

(./sync/confd_md5.c : 167 ) ---- <ha_check_confirm_members send by timeout> ----

(./sync/confd_md5.c : 168 ) ---- <local cli> 21E374585BFFBDD4A043951988FEDBE9 ----

(./sync/confd_md5.c : 169 ) ---- <member cli> 1335504BC818AC7702F0A8735DB290D0 ----

(./lib/confd_setup_rsc.c : 571 ) Received MD5SUM response from FVVM020000176885

(./lib/confd_setup_rsc.c : 254 ) get device's config file md5info, and compare them

(./lib/confd_setup_rsc.c : 336 ) the device FVVM020000176885 has fresh system config, don't need update

(./lib/confd_setup_rsc.c : 384 ) the device FVVM020000176885 has fresh cli config, don't need update

(./lib/confd_setup_rsc.c : 393 ) config file is same, send init_finished to slave device FVVM020000176885

(./lib/confd_setup_rsc.c : 118 ) member FVVM020000176885 update confirme time: 550654

(./lib/confd_msg.c : 39 ) send msg to ha, msg len: 72 msg type: 1 sn: FVVM020000176885 status: 0