Forum Discussion
3 Replies
Sort By
- What_Lies_Bene1Cirrostratus
Hey. The command to do the sync is:
. The command to display status istmsh run cm config-sync (to-group | from-group) 'device-group-name'
.tmsh show cm sync-status
I just deleted my previous response. It was simply wrong.
In case all your devices belong to a SYNC-FAILOVER device group (i.e. 'device-group-failover'), you can synchronize them from CLI with the following command:tmsh run cm config-sync to-group device-group device-group-failover
Perhaps your SYNC-FAILOVER device group got a different name. You can check it as follows:
tmsh list cm device-group one-line | grep 'sync-failover' | awk '{print $3}'
By putting the command above in backticks you can combine it with the sync command in a single line:
tmsh run cm config-sync to-group `tmsh list cm device-group one-line | grep 'sync-failover' | awk '{print $3}'`
Hi Mareeswaran, there is a good article on the subject on AskF5. Please see SOL7024 for details.
The concept of device clustering changed completely with the introduction of v11 to become more flexible and scalable. The previous deployment was limited to 2 units only. Always make sure your units are synched with NTP:watch -d "ntpq -p"
Sometimes a timestamp mismatch prevents a config sync. Failing SCCP communication may also impact the config sync operation on the previous H/W platforms, if I remember right.
Please keep in mind, that a "full_box_reboot" is required to restart the SCCP as well. Maybe some units (and SCCP) have a longer uptime than 497 days. Thanks, Stephan