Upgrade Unity Connection from Single Server to Cluster

[DOUG DAVIDSON]

I am trying to implement a Unity Connection subscriber with an existing Unity Connection Publisher and am experiencing issues with getting the cluster established. I have been told by TAC that I need to re-install publisher and then install subscriber. Has anyone else had any issues creating a Connection cluster after the publisher has been running for a while?

Thanks,

Doug

[David Hailey]

What version is the existing CUC Publisher?

Hailey

[DOUG DAVIDSON]

8.5.1ES47.12900-47 (SU3)

[David Hailey]

That load is actually SU2 (not SU3). Couple other questions:

1. What is the hardware model of each server (Pub and Sub)?

2. Are you upgrading the Subscriber to the same version as the Pub prior to attempting to join the cluster?

3. Is there a specific error thrown when trying to join the cluster?

4. Did TAC reference any bugs specifically or find potential corruption of the database on the Publisher?

Hailey

[culittle]

What are the issues you are experiencing?

[DOUG DAVIDSON]

can't get serviceability or set manager to start. If I try to log on to anything other than OS admin I get db error.

Sent from Cisco Technical Support iPhone App

[Chris Deren]

You should be able to just configure the cluster on the Pub referencing the to be added Sub, and then build the SUB and add HA license.

Chris

[David Hailey]

I recall seeing a bug regarding CUC clustering setup when 8.5(1) was first released.  Should be resolved in SU2 but what I don't know is the install history of the existing Publisher (i.e., the initial version and the path to the current SU2 release).  The bug I'm referring to is:

  CSCtn61453 Bug Details

Applying 8.5.1 software as patch results in corrupted CUC installation.

Symptom:

After fresh installation of 8.5.1 software, we can notice several problem symptoms.

- Connection services and Connection DB does not start

- System cannot be accessed via web page

- Informix error messages for certain CLI commands

Example :- show cuc cluster status

com.informix.asf.IfxASFException: Attempt to connect to database server (ciscounity) failed.

Command failed

Conditions:

It is observed during fresh installation of Unity Connection product when installation was

started with earlier version of software and 8.5.1 software was applied as a patch during the setup process.

Workaround:

This issue will be resolved in 8.5(1)su2 and Unity Connection 8.6 and later. So applying those versions of software as a patch during setup process will not encounter this problem.

If you are installing affected version, first, perform a fresh installation of earlier version of software using the install media. Then after verifying the installation, proceed with the upgrade to 8.5.1su1 as a separate process.

The way I read the workaround above is that an inline upgrade (i.e., upgrade to SU1 during initial setup) may be problematic but again, this may not apply to your particular case.

Hailey

Please rate helpful posts!

[DOUG DAVIDSON]

That is the exact problem I am encountering. Publisher was installed as 8.5.1 and upgraded to SU2. I have a bootable SU2 CD, so evidently it is not fixed in SU2.

I also cannot find this bug referenced in the latest SU3 release notes. I am going to try and upgrade to SU 3 and see if it resolves the issue. Will let you know.

Thanks,

Doug

[DOUG DAVIDSON]

Well upgrading to SU3 did not fix the issue. When I run the "Utils Service list" command I see the following:

admin:utils service list

Requesting service status, please wait...
System SSH [STARTED]
Cluster Manager [STARTED]
Service Manager is running
Getting list of all services
>> Return code = 0
A Cisco DB[STARTED]
A Cisco DB Replicator[STARTED]
Cisco AMC Service[STARTED]
Cisco Audit Event Service[STARTED]
Cisco CDP[STARTED]
Cisco CDP Agent[STARTED]
Cisco CallManager Serviceability[STARTED]
Cisco CallManager Serviceability RTMT[STARTED]
Cisco Certificate Change Notification[STARTED]
Cisco Certificate Expiry Monitor[STARTED]
Cisco DRF Local[STARTED]
Cisco DRF Master[STOPPED]  Commanded Out of Service
Cisco Database Layer Monitor[STARTED]
Cisco Log Partition Monitoring Tool[STARTED]
Cisco RIS Data Collector[STARTED]
Cisco RTMT Reporter Servlet[STARTED]
Cisco Syslog Agent[STARTED]
Cisco Tomcat[STARTED]
Cisco Tomcat Stats Servlet[STARTED]
Cisco Trace Collection Service[STARTED]
Cisco Trace Collection Servlet[STARTED]
Connection Administration[STARTING]
Connection DB[STARTING]
Connection DB Event Publisher[STARTED]
Connection Directory Feeder[STARTING]
Connection License Server[STARTING]
Connection SNMP Agent[STARTED]
Connection Server Role Manager[STARTING]
Connection Serviceability[STARTING]
Host Resources Agent[STARTED]
MIB2 Agent[STARTED]
SNMP Master Agent[STARTED]
SOAP -Log Collection APIs[STARTED]
SOAP -Performance Monitoring APIs[STARTED]
SOAP -Real-Time Service APIs[STARTED]
System Application Agent[STARTED]
Cisco DirSync[STOPPED]  Service Not Activated
Cisco Serviceability Reporter[STOPPED]  Service Not Activated
Connection Access Layer[STOPPED]  Service Not Activated
Connection CM Database Event Listener[STOPPED]  Service Not Activated
Connection Conversation Manager[STOPPED]  Service Not Activated
Connection Database Proxy[STOPPED]  Service Not Activated
Connection Diagnostic Portal Service[STOPPED]  Service Not Activated
Connection Digital Networking Replication Agent[STOPPED]  Service Not Activated
Connection Exchange Notification Web Service[STOPPED]  Service Not Activated
Connection File Syncer[STOPPED]  Service Not Activated
Connection Groupware Caching Service[STOPPED]  Service Not Activated
Connection IMAP Server[STOPPED]  Service Not Activated
Connection Inbox RSS Feed[STOPPED]  Service Not Activated
Connection Integrated Mailbox Configuration[STOPPED]  Service Not Activated
Connection Jetty[STOPPED]  Service Not Activated
Connection Mailbox Sync[STOPPED]  Service Not Activated
Connection Message Event Service[STOPPED]  Service Not Activated
Connection Message Transfer Agent[STOPPED]  Service Not Activated
Connection Mixer[STOPPED]  Service Not Activated
Connection Notifier[STOPPED]  Service Not Activated
Connection Personal Communication Assistant[STOPPED]  Service Not Activated
Connection REST Service[STOPPED]  Service Not Activated
Connection Realtime Monitoring APIs[STOPPED]  Service Not Activated
Connection Reports Data Harvester[STOPPED]  Service Not Activated
Connection SMTP Server[STOPPED]  Service Not Activated
Connection SpeechView Processor[STOPPED]  Service Not Activated
Connection System Agent[STOPPED]  Service Not Activated
Connection Voice Mail Web Service[STOPPED]  Service Not Activated
Connection Voice Recognition Transport[STOPPED]  Service Not Activated
Connection Voice Recognizer[STOPPED]  Service Not Activated
Primary Node =false

Also, I have noticed that about every 10 minutes core files for CuSrm and CuLicSrv are being generated.

This is not supposed to be that difficult. Of course, when the problem is found it will probably be something that i should have caught early on.

Thanks,

Doug

[David Hailey]

Unfortunately, this sounds as if it may be related to some form of DB corruption especially if it is related to the bug I noted earlier in the thread.  That probably forces you down the path of rebuilding the Publisher and then installing the Subscriber as part of the new build.  Obviously, that's not an ideal solution but may be what's required to resolve the problem.  If this is a production system, you may be able to leverage the COBRAS tool to export some data and then re-import after the new cluster is built.  This would, at least to some degree, potentially reduce the pain associated with the rebuild.  You can take a look at that more here:

http://www.ciscounitytools.com/Applications/General/COBRAS/COBRAS.html

Hailey

Please rate helpful posts!