The security passphrase (the fourth item in the list) is retrieved from the site documentation. In this case, the IP address is 172.18.172.212, the host name is cucm911ccnapub, and there is no domain name configured for the publisher.
In order to retrieve the first three items in the list, enter the show network cluster command at the current subscriber node CLI: admin: show network clusterġ72.18.172.213 cucm911ccnasub1 Subscriber authenticatedġ72.18.172.212 cucm911ccnapub Publisher not authenticated - INITIATORġ72.18.172.214 cucm911ccnasub2 Subscriber authenticated using TCP since
MAC CUPS CLIENT HOLD FOR AUTHENTICATION FULL
In order to avoid these issues, keep a full cluster DRF backup. Since this process only recovers the CUCM DB configuration, other data, such as certificates, Music on Hold (MoH), and TFTP files, are not recovered.
MAC CUPS CLIENT HOLD FOR AUTHENTICATION HOW TO
This document describes how to take advantage of this feature in order to successfully restore a publisher DB from the subscriber.Ĭisco strongly recommends that you keep a full Disaster Recovery Framework (DRF) backup of the entire cluster. In CUCM Version 8.6(1), a new feature was introduced in order to restore a publisher DB from a subscriber database. Some customers did not keep proper backups, or had backups that were out-of-date, so the only option was to rebuild and reconfigure the publisher server node. Consequently, if a publisher node was lost due to a hardware failure or a file system corruption, the only way to recover it was to reinstall and restore the DB from a Disaster Recovery System (DRS) backup. In early versions of CUCM, the publisher node was regarded as the only authoritative source for the Structured Query Language (SQL) DB. This document describes how to restore the Cisco Unified Communications Manager (CUCM) publisher node from the subscriber database (DB) without prior backup or root access. Phones do not Register or are Unable to Access Services
0 kommentar(er)
