When sync status change show in log

Hello,

Is it possible for F5 to show up "sync status change"in the log when the sync status changes?
I tried to change the sync status and found that the information is not shown in the log.

Any help is appreciate.

application delivery

Kai_Wilke
Nov 30, 2022
Hi Michael,

I'm uncertain if a more agressive MCPD log level may include some log messages for sync-status-changes? You may give it a try...

If everything fails you could simply produce your own log lines as needed via custom iCall scripts. The quickly coded iCall script executes every 120 seconds a "tmsh show cm sync-status" and then checks if the resulting text output contains the string "Color green", if the string is not present, it will simply create a log entry for you...

sys icall handler periodic check_config_sync { interval 120 script check_config_sync } sys icall script check_config_sync { app-service none definition { tmsh::log_dest file tmsh::log_level debug if { [tmsh::show /cm sync-status] contains "Color green" } then { # Everything is fine... } else { tmsh::log debug "Check Config Sync: [info hostname] displays a non-green sync-state." } } description none events none }

Cheers, Kai

Mohamed_Ahmed_Kansoh
MVP
Nov 30, 2022
Hi Michaelyang ,
F5 wouldn’t change its Syncronization status without Administative intervention , so that , you can see all changes by navigating F5 "/var/log/audit" logs , you can see the last insync status and what are the changes have been done since last insync status.
Follow this Article :
https://support.f5.com/csp/article/K09050750

Also this KB :
https://support.f5.com/csp/article/K15419
for monitoring F5 HA sync status

Regards
- Michaelyang
  Cirrostratus
  Nov 30, 2022
  Hi Mohamed_Ahmed_Kansoh,
  Thanks for your reply.
  Maybe my expression was not clear and made you misunderstand.
  I mean when the sync status changes, can I see the log with the status change on var/log/ltm?
  I tried to change the sync status and found that the information is not shown in var/log/ltm.
  - Mohamed_Ahmed_Kansoh
    MVP
    Nov 30, 2022
    hello ,
    you can see the " Sync " action in "/var/log/ltm" , you see a log related to mcpd process contains the commit id , time , ..etc , but this when you click sync button.
    
    I do not know if the status changed to " changes pending " shoud give you a log or not.
    let us see one of F5 experts here can provide you a good reply in this.
    
    But I want to ask you , why do you want to see this log , it wouldn’t be useful for anything , you can see the status cleared within cli or GUI as well.
    
    Regards
Kai_Wilke
MVP
Nov 30, 2022
Hi Michael,

I'm uncertain if a more agressive MCPD log level may include some log messages for sync-status-changes? You may give it a try...

If everything fails you could simply produce your own log lines as needed via custom iCall scripts. The quickly coded iCall script executes every 120 seconds a "tmsh show cm sync-status" and then checks if the resulting text output contains the string "Color green", if the string is not present, it will simply create a log entry for you...

sys icall handler periodic check_config_sync { interval 120 script check_config_sync } sys icall script check_config_sync { app-service none definition { tmsh::log_dest file tmsh::log_level debug if { [tmsh::show /cm sync-status] contains "Color green" } then { # Everything is fine... } else { tmsh::log debug "Check Config Sync: [info hostname] displays a non-green sync-state." } } description none events none }

Cheers, Kai
- Mohamed_Ahmed_Kansoh
  MVP
  Nov 30, 2022
  Hello Kai_Wilke ,
  I wonder if configsync.autodetect still supported.
  I think if he modified " db configsync.autodetect" value to be enabled , I think he will get an informative log message within /var/log/ltm.
  
  I tried to test it on my lab but i do not find this option.
  - Kai_Wilke
    MVP
    Nov 30, 2022
    Hi Mohamed,
    
    beginning with TMOS v11 the cluster management has completely changed.
    
    I highly doubt that any of those cluster related KB information written for previous TMOS versions still apply. It was a completely different world back then...
    
    Cheers, Kai