30.08.2017 CUCM Cluster replication problem

Из-за сбоя оборудования упал Subscriber, причем заметили только через 8 дней.
После запуска сервера не смог зайти на страницу CUCM Administration - выдавал Database error.

Далее обнаружилась проблема с репликацией:

SERVER-NAME         IP ADDRESS        (msec)    DbMon?    QUEUE    Group ID       (RTMT) & Details
-----------         ----------        ------    -------   -----    -----------    ------------------
cucm01-tmn-igf1     10.19.65.11       0.026     Y/Y/Y     0        (g_2)          (3) Out Of Sync
cucm02-tmn-igf1     10.19.65.12       1.052     Y/Y/Y     2016794  (g_3)          (-) Setup Completed

Далее для решения проблемы:

1. Проверяем правильную настройку NTP:
   

   admin:utils ntp status
   ntpd (pid 12364) is running...
   
        remote           refid      st t when poll reach   delay   offset  jitter
   ==============================================================================
   *10.19.0.1       10.19.176.1      3 u  845 1024  377    0.674    1.930   0.665
   +10.19.0.2       10.19.176.1      3 u  574 1024  377    0.678    2.681   1.989
   
   
   synchronised to NTP server (10.19.0.1) at stratum 4 
      time correct to within 85 ms
      polling server every 1024 s
   
   Current time in UTC is : Wed Aug 30 13:15:07 UTC 2017
   Current time in Etc/GMT-5 is : Wed Aug 30 18:15:07 +05 2017

2. провести диагностику:
   

   admin:utils diagnose test
   
   Log file: platform/log/diag1.log
   
   Starting diagnostic test(s)
   ===========================
   test - disk_space          : Passed (available: 1569 MB, used: 12587 MB)
   skip - disk_files          : This module must be run directly and off hours
   test - service_manager     : Passed                      
   test - tomcat              : Passed                      
   test - tomcat_deadlocks    : Passed                      
   test - tomcat_keystore     : Passed                      
   test - tomcat_connectors   : Passed                      
   test - tomcat_threads      : Passed                      
   test - tomcat_memory       : Passed                      
   test - tomcat_sessions     : Passed                      
   skip - tomcat_heapdump     : This module must be run directly and off hours
   test - validate_network    : Passed                      
   test - raid                : Passed                      
   test - system_info         : Passed (Collected system information in diagnostic log)
   test - ntp_reachability    : Passed               
   test - ntp_clock_drift     : Passed               
   test - ntp_stratum         : Passed               
   skip - sdl_fragmentation   : This module must be run directly and off hours
   skip - sdi_fragmentation   : This module must be run directly and off hours

3. Сделать reset для DB replication
   1. Issue command “utils dbreplication stop” on all nodes starting from Subscribers and ending with Publisher one by one.
   2. Issue command “utils dbreplication dropadmindb” on all nodes starting from Publisher (one by one).
   3. Issue command “utils dbreplication reset all” on the Publisher