Buy or Renew
Buy or Renew
Cisco + Splunk: It’s a new day for your data. Learn more.
 
cancel
Turn on suggestions
Auto-suggest helps you quickly narrow down your search results by suggesting possible matches as you type.
Showing results for 
Search instead for 
Did you mean: 
cancel
Start a conversation
1928
Views
0
Helpful
15
Replies

RTMT not working after changing hostname on subscriber (unity connection)

latintrpt
Level 1
Level 1

‎04-15-2012 04:49 PM - edited ‎03-16-2019 10:39 AM

Hello all,

Yesterday I moved my subscriber for Cisco Unity Connection to another data center.  I had it defined by hostname so I changed DNS to reflect the new IP.

Also changed the IP, name, and gateway under the OS administration.

The cluster was rebooted and replication is working just fine.

My only problem is that RTMT is reporting that the subscriber node "AMC service is down".  I have verified that the service is up on both the publisher and subscriber.  In RTMT the only node I'm seeing is the publisher.

Anyone have an idea as to what I'm doing wrong or missing?

I'm running version 7.1.3ES50.33039-50 on both nodes

Thanks

Labels:
0 Helpful
15 Replies 15

ronpatel
Level 8
Level 8

‎04-15-2012 06:50 PM

Hi

Is there a possibility to do following procedure

This might be due to enterprise replication being broken between the publisher and subscriber.

on sub:

utils dbreplication stop


on pub:

utils dbreplication stop

utils dbreplication reset all


This should rebuild the enterprise replication (OS level informix replication).


Confirm RTMT state is 2 on both pub and sub with:

utils dbreplication runtimestate

utils dbreplication status


Then make sure the UC application replication is good with:

show cuc cluster status

Regards

Ronak Patel

Rate helpful posts.

Regards Ronak Patel Rate all helpful post by clicking stars below the answer.
0 Helpful

latintrpt
Level 1
Level 1
In response to ronpatel

‎04-15-2012 08:24 PM

I think I have a replication issue

Publisher:

admin:utils dbreplication runtimestate

DB and Replication Services: ALL RUNNING

Cluster Replication State: Replication status command started at: 2012-04-15-21-59
There no active nodes in the replication network
DB Version: ccm7_1_3_33039_1
Number of replicated tables: 427

Cluster Detailed View from PUB (2 Servers):

                                PING            REPLICATION     REPL.   DBver&  REPL.   REPLICATION SETUP
SERVER-NAME     IP ADDRESS      (msec)  RPC?    STATUS          QUEUE   TABLES  LOOP?   (RTMT) & details
-----------     ------------    ------  ----    -----------     -----   ------- -----   -----------------
rudua-unity001  10.74.13.229    0.042   Yes     Off-Line        N/A     match   Yes     (2) PUB Setup Completed
rupua-unity001  10.74.213.229   0.226   Yes     Off-Line        N/A             N/A     () Not Setup
 

admin:show cuc cluster status

Server Name     Member ID  Server State  Internal State  Reason
--------------  ---------  ------------  --------------  ------
rudua-unity001  0          Primary       Pri Active      Normal
rupua-unity001  1          Secondary     Sec Active      Normal

SERVER                 ID STATE    STATUS     QUEUE  CONNECTION CHANGED
-----------------------------------------------------------------------
g_ciscounity_rudua_unity001  100 Active   Local           0               
g_ciscounity_rupua_unity001  101 Active   Connected       0 Apr 15 05:19:13


Subscriber:

admin:utils dbreplication runtimestate

Cisco Database Layer Monitor is not running 

admin:show cuc cluster status

Server Name     Member ID  Server State  Internal State  Reason
--------------  ---------  ------------  --------------  ------
rudua-unity001  0          Primary       Pri Active      Normal
rupua-unity001  1          Secondary     Sec Active      Normal

SERVER                 ID STATE    STATUS     QUEUE  CONNECTION CHANGED
-----------------------------------------------------------------------
g_ciscounity_rudua_unity001  100 Active   Connected       0 Apr 15 05:19:13
g_ciscounity_rupua_unity001  101 Active   Local           0               

Any idea on how to fix this and do I need to this on a down time?

Thank You

0 Helpful

anchoudh
Level 9
Level 9
In response to latintrpt

‎04-15-2012 08:39 PM

Hi,

You can use the command for forceing the replication on to subscriber

utils dbreplication forcedatasyncsub

Reference:

http://www.cisco.com/en/US/partner/docs/voice_ip_comm/cucm/cli_ref/7_1_2/cli_ref_712.html#wp69932

utils dbreplication forcedatasyncsub

This command forces a subscriber server to have its data restored from data on the publisher server.

Use this command only after you have run the utils dbreplication repair command several times, but the utils dbreplication status command still shows non-dynamic tables that are not in sync

Note Do  not run this command if only dynamic tables are out of sync; dynamic  tables can be out of sync during normal system operation.

You can only run this command from the publisher server. Use the all parameter to force sync on all subscriber servers in the cluster. If only one subscriber server is out of sync, use the hostname parameter.

After you run this command, you must restart the restored subscriber servers.

This command can take a significant  amount of time to execute and can affect the system-wide IOWAIT.

Hope it helps.

Anand

Pls rate helpful posts !!

0 Helpful

anchoudh
Level 9
Level 9

‎04-15-2012 07:40 PM

Hi,

Did you reinstall the RTMT after you made changes on subscriber?

Please add the hostname entries in the RTMT client box and select the new ip address once again to login.

Hope it helps.

Anand

Pls rate helpful posts !!

0 Helpful

latintrpt
Level 1
Level 1
In response to anchoudh

‎04-15-2012 08:42 PM

Whenever I start the Cisco Database Layer Monitor on the subscriber, it starts and then it stops.

Should I still do the above with forcing replication on the subscriber?

Thanks

0 Helpful

anchoudh
Level 9
Level 9
In response to latintrpt

‎04-15-2012 08:46 PM

Hi,

Could you please check the servicability page to verify if the services are running and stable?

Thanks,

Anand

0 Helpful

latintrpt
Level 1
Level 1
In response to anchoudh

‎04-15-2012 08:50 PM

All services are started except for: Cisco Database Layer Monitor, Cisco RIS Data Collector, and Cisco Log Partition Monitoring Tool.  I tried starting these services.  They do start up but then stop running.

This is only an issue on the subscriber.  Publisher services are all fine.

0 Helpful

ronpatel
Level 8
Level 8
In response to latintrpt

‎04-15-2012 08:53 PM

Hi

Please do above procedure which is mentioned in my previous post. It will help you.

regards

Ronak Patel

Rate helpful posts.

Regards Ronak Patel Rate all helpful post by clicking stars below the answer.
0 Helpful

latintrpt
Level 1
Level 1
In response to ronpatel

‎04-15-2012 08:54 PM

Ron, I have tried the above you listed, but i get the following:

Publisher:

admin:utils dbreplication runtimestate

DB and Replication Services: ALL RUNNING

Cluster Replication State: Replication status command started at: 2012-04-15-21-59
There no active nodes in the replication network
DB Version: ccm7_1_3_33039_1
Number of replicated tables: 427

Cluster Detailed View from PUB (2 Servers):

                                PING            REPLICATION     REPL.   DBver&  REPL.   REPLICATION SETUP
SERVER-NAME     IP ADDRESS      (msec)  RPC?    STATUS          QUEUE   TABLES  LOOP?   (RTMT) & details
-----------     ------------    ------  ----    -----------     -----   ------- -----   -----------------
rudua-unity001  10.74.13.229    0.042   Yes     Off-Line        N/A     match   Yes     (2) PUB Setup Completed
rupua-unity001  10.74.213.229   0.226   Yes     Off-Line        N/A             N/A     () Not Setup
 

admin:show cuc cluster status

Server Name     Member ID  Server State  Internal State  Reason
--------------  ---------  ------------  --------------  ------
rudua-unity001  0          Primary       Pri Active      Normal
rupua-unity001  1          Secondary     Sec Active      Normal

SERVER                 ID STATE    STATUS     QUEUE  CONNECTION CHANGED
-----------------------------------------------------------------------
g_ciscounity_rudua_unity001  100 Active   Local           0               
g_ciscounity_rupua_unity001  101 Active   Connected       0 Apr 15 05:19:13


Subscriber:

admin:utils dbreplication runtimestate

Cisco Database Layer Monitor is not running 

admin:show cuc cluster status

Server Name     Member ID  Server State  Internal State  Reason
--------------  ---------  ------------  --------------  ------
rudua-unity001  0          Primary       Pri Active      Normal
rupua-unity001  1          Secondary     Sec Active      Normal

SERVER                 ID STATE    STATUS     QUEUE  CONNECTION CHANGED
-----------------------------------------------------------------------
g_ciscounity_rudua_unity001  100 Active   Connected       0 Apr 15 05:19:13
g_ciscounity_rupua_unity001  101 Active   Local           0               

0 Helpful

latintrpt
Level 1
Level 1
In response to latintrpt

‎04-15-2012 09:03 PM

Any reason why the Cisco Database Layer Monitor keeps turning off on the subscriber?  I would think this would cause issues if I try to rebuild the database on the subscriber.

0 Helpful

ronpatel
Level 8
Level 8
In response to latintrpt

‎04-15-2012 09:07 PM

Hi

"utils cuc cluster overwritedb" in Sub will copies data from the publisher to the  subscriber.  See if this command helps, If not I would suggest you to raise the Cisco TAC case.

Regards

Ronak Patel

Regards Ronak Patel Rate all helpful post by clicking stars below the answer.
0 Helpful

Gajanan Pande
Cisco Employee
Cisco Employee
In response to latintrpt

‎04-15-2012 09:09 PM

Latin,

Do you see any error while booting the Sub ? Anything mentioning about using recovery CD to fix any issue as such ?

Due to malfunction or file corruption, Services will have similar issues & using recovery disk while booting fixes it.


GP.

0 Helpful

latintrpt
Level 1
Level 1
In response to Gajanan Pande

‎04-15-2012 09:14 PM

Date: Apr 15 05:20:02

Machine Name: rupua-unity001

Severity: Critical

Process:  Cisco Database Layer Monitor

Message: : SDIDBConfigData:Read failed. ProccessNodeIdException = Could not locate process node id


I saw this in RTMT

0 Helpful

Gajanan Pande
Cisco Employee
Cisco Employee
In response to latintrpt

‎04-15-2012 09:17 PM

No, I meant, did you see any message on server console ( not RTMT ) asking to use " Recovery Disk " while booting the server ?


GP.

0 Helpful
Getting Started

Find answers to your questions by entering keywords or phrases in the Search bar above. New here? Use these resources to familiarize yourself with the community:

Customers Also Viewed These Support Documents