IP Phone still active even though its MAC address removed from CUCM

[herus]

Hello everyone,

I have a strange issue, where IP Phone (CP-7821) still active (able to make / receive a call) even though its MAC Address removed from call manager. Auto-registration is not activated. I have done reset from setting menu and factory reset by pressing #, but the Phone still active.

I also try to deleted another MAC Address CP-7821 from call manager to make sure, after remove it, the phone became not active / unprovisioned.

Does Anyone experience this issue before?, is this IP Phone issue or there is something wrong with call manager?

Note : CUCM Version is 11.5

Need your advice.

Thank you.

[Nithin Eluvathingal]

Check the DB  replications .Check  if all tables are synced properly.

2.12.0.0

[Ratheesh Kumar]

Hi there

When you say MAC address removed, does that mean you deleted the 7841 phone ?

If yes, then as Nithin suggested check the DB replication of the cluster. There are high chances that the device might got removed from CUCM PUB but still flagged in SUBs.

Check the replication, a repair of cluster or even a restart of entire cluster would be a best bet

Hope this Helps

Cheers
Rath!

***Please rate helpful posts and if applicable mark "Accept as a Solution"***

[herus]

Hello Nitehin & Rath,

Thank you for your reply.

Correct, I deleted CP 7821 from call manager.

I have checked db replication of call manager in good state but there is Errors or data mismatches were found in utils dbreplication status.

Below is the output

admin:utils dbreplication runtimestate

Server Time: Wed Mar 9 06:59:24 WIB 2022

Cluster Replication State: Errors or data mismatches were found in utils dbreplication status at: 2022-03-08-09-37
Use CLI to see detail: 'file view activelog cm/trace/dbl/sdi/ReplicationStatus.2022_03_08_09_30_04.out'

DB Version: ccm11_5_1_13900_52

Repltimeout set to: 1260s
PROCESS option set to: 1

Cluster Detailed View from pubcucm1 (5 Servers):

PING DB/RPC/ REPL. Replication REPLICATION SETUP
SERVER-NAME IP ADDRESS (msec) DbMon? QUEUE Group ID (RTMT) & Details
----------- ---------- ------ ------- ----- ----------- ------------------
subscucm1 14.x.x.x 0.147 Y/Y/Y 0 (g_10) (2) Setup Completed
subscucm1 14.x.x.x 1.341 Y/Y/Y 0 (g_12) (2) Setup Completed
substftp1 14.x.x.x 0.129 Y/Y/Y 0 (g_11) (2) Setup Completed
pubcucm1 14.x.x.x 0.011 Y/Y/Y 0 (g_2) (2) Setup Completed
substftp1 14.x.x.x 1.362 Y/Y/Y 0 (g_13) (2) Setup Completed

If I would like to repair db replication, what is best practice to db replication repair or sequence to perform db replication ?

Thank you.

Regards,

Herus

[Ratheesh Kumar]

DB replication looks good (Setup at 2). Why dont you try a Publisher restart

Hope this Helps

Cheers
Rath!

***Please rate helpful posts and if applicable mark "Accept as a Solution"***

[Nithin Eluvathingal]

There is mismatch on tables

Cluster Replication State: Errors or data mismatches were found in utils dbreplication status at: 2022-03-08-09-37

Stop db replication and start the replication to resync the tables

refer the below guide and follow the db reset steps 

[herus]

Hello Nithin,

I didn't find link you share, can you re-post again.

In addition, if I perform utils dbreplication repair all from publisher, is there impact to production?

Thank you.

Regards,

Herus

[Nithin Eluvathingal · Accepted solution]

https://www.cisco.com/c/en/us/support/docs/unified-communications/unified-communications-manager-callmanager/200396-Steps-to-Troubleshoot-Database-Replicati.html

I would prefer to do it during the maintenance window and make sure you have a backup. 

[Ratheesh Kumar · Accepted solution]

If all nodes are in Setup 2, you can just do "utils dbreplication repair all" on PUB and it will fix the tables.

If I were you, I will do the following

1. Restart the entire cluster starting with PUB followed by SUBs

Check the DB replication 

2. utils dbreplication repair all" on PUB

Check the DB replication 

3. Move into detailed recovery as per Nithin's link/ raise up with TAC

Hope this Helps

Cheers
Rath!

***Please rate helpful posts and if applicable mark "Accept as a Solution"***

[herus]

Hello Rath,

I plan to do your advice, and let you know the result.

Thank you.

Heru

[Nithin Eluvathingal]

The guide which I shared has all trouble shooting related to the db issues.

[herus]

Hi Rath & Nithin,

after perform utils db replication repair all on publisher, problem solved, all table are replicated properly.

admin:utils dbreplication runtimestate

Server Time: Fri Mar 11 07:21:01 WIB 2022

Cluster Replication State: Replication status command started at: 2022-03-11-07-16
Replication status command ENDED. Checked 706 tables out of 706
Last Completed Table: devicenumplanmapremdestmap
No Errors or Mismatches found.

Thank you for your help.

Regards,

Herus