![]() Internal CLI Error: Failed to connect to the database of node DC21-CUCCX1 ![]() Output is in file: uccx/cli/DbConfigIntegrity_1524829209977.txt Output is in file: uccx/cli/DbServerIntegrity_1524829028379.txt This operation may take a few minutes to complete. *Also, what is the impact of leaving CDS/HDS disabled ?Īdmin:utils uccx database dbserver intergrityĪdmin:utils uccx database dbserver integrity I restarted Cisco Unified CCX Cluster View Daemon service and issue came clear ![]() Ran the utils uccx database dbserver integrity on both nodes and didn't look goodĮrror on both nodes showed=Internal CLI Error: Failed to connect to the database of node DC21-CUCCX1 If the primary is down and the secondary is up and if you try to make a config change, it will fail always as the IDS need the primary to be up for the protocol and there is no workaround to this.īelow is how I have been able to temporarily fix mine but I need a perm fix If the secondary node goes down, then to make a config update, the Disable CDS/HDS can be carried out which will remove this protocol and the config changes will be successful from the primary. This will fail if the one of the nodes is down, DB on one of the nodes is down. The Config Datastore works on the Informix 2 phase commit protocol which means that for a transaction to be commited into the DB, both the primary and target node (Informix terminology) needs to participate in the transactions. See if it shows both the nodes and if the status is RUNNING. Then proceed to the Related Links for Datastores and check the Config Datastore. If it still fails, look out for the Replication Servers under the Cisco Unified CCX Serviceability - Tools - Datastore Control Center - Replication Servers.īoth nodes should show Connected and Active with the Reset replication button available. To verify the integrity can you run the following command on both the nodes (non-business impacting)Ĭheck the update post that. Can you check if the Cisco Unified CCX Database is IN SERVICE on both the nodes?
0 Comments
Leave a Reply. |