Introduction
This document describes the steps to resolve renegotiation failure between Cisco Unity Connection Publisher and Subscriber.
Prerequisites
Requirements
Cisco recommends that you have knowledge of Linux.
Components Used
The information in this document is based on Cisco Unity Connection version 10.5.2
The information in this document was created from the devices in a specific lab environment. All of the devices used in this document started with a cleared (default) configuration. If your network is live, make sure that you understand the potential impact of any command.
Resolving the Renegotiation Failure on Cisco Unity Connection 10.5
Collect renegotiate logs from the Unity Connection Server.
- Renegotiate logs show snippet, which is something similar to this:
+ [[ -n '' ]]
+ [[ -z '' ]]
+ target_exec /opt/cisco/connection/bin/cuc_controlcenter.sh '"A' Cisco 'DB"' start
+ sudo -u cucluster ssh gaxgpvs96 ' sh -lc '\''source /usr/local/cm/db/informix/local/ids.env && /opt/cisco/connection/bin/cuc_controlcenter.sh' '"A' Cisco 'DB"' 'start'\'''
sh: /opt/cisco/connection/bin/cuc_controlcenter.sh: Permission denied
++ error
++ '[' 0 -eq 1 ']'
++ '[' 0 -eq 1 ']'
++ echo 'Cluster renegotiation failed.'
++ echo 'The cluster renegotiation log cuc-cluster-rejoin_2016-01-30_14.53.47.log can be found in the installation logging location through the CLI or RTMT.'
++ exit 1
- Need to focus on this line:
sh: /opt/cisco/connection/bin/cuc_controlcenter.sh: Permission denied
- To disable the SELinux mode on both, new publisher and the already available subscriber node use the command utils os secure permissive.
- After you disbale the SELinux, run the renegotiate command utils cuc cluster renegotiate.
This command creates a cluster relationship with the publsiher server in a conection cluster after the server is replaced or the connection was reinstalled on the publisher server. This command overwrites all the data on the publsiher server with data from the subscriber server and initializes the replication between the servers.
Note: Remember to enable the SELinux once the server cluster is setup and replication is good between the two nodes.
Reason of the Failure
The main reason of renegotiation failure on Cisco Unity Connection 10.5 is the SELinux, which prevents bash from getattr access on the file /opt/cisco/connection/bin/cuc_controlcenter.sh.
Feedback