[cisco-voip] CUCM 6.1.1 replication - pub state is 3-bad

[Patrick Mowry]

At this point it is only showing a connection for the one's I've
reinstalled.  I did not save a report from before I started:

10.132.244.2	

SERVER                 ID STATE    STATUS     QUEUE  CONNECTION CHANGED
-----------------------------------------------------------------------
g_rsd_ccm_moh_ccm      15 Active   Connected       0 Aug 25 16:42:12
g_rsd_ccm_pub_ccm       2 Active   Local           0                
g_rsd_ccm_sub3_ccm     11 Active   Connected       0 Aug 26 12:28:54
g_rsd_ccm_tftp_ccm     12 Active   Connected       0 Aug 26 12:02:42

The are similar for the other rebuilt servers and the lines for sub1 and
2 are blank except for the IP.  So I think once I get the last one
rebuilt I'll be good.  I have all my phones registered to sub3 and the
pub right now any so far the odd issues seem to have cleared up.  The
equipment has been moved to another building, so the ongoing power
issues for the past 2 years will not be an issue anymore.


Would you have any idea what the result 256 would be from the
validate_network script?  It's just curiosity, so please don't put any
time on it unless your curious too. 

-----Original Message-----
From: Ryan Ratliff [mailto:rratliff at cisco.com] 
Sent: Thursday, August 26, 2010 3:59 PM
To: Patrick Mowry
Cc: Wes Sisk; cisco-voip at puck.nether.net
Subject: Re: [cisco-voip] CUCM 6.1.1 replication - pub state is 3-bad

What does CURT show for the output of 'cdr lis serv'?  That's the
connection that is down and triggers state 3.

If you don't want to keep reinstalling open a TAC SR and get somebody
looking at it.  Otherwise get the cluster to a good state and upgrade.
There are many improvements since early 6.x related to dbreplication
serviceability.

-Ryan

On Aug 26, 2010, at 4:41 PM, Patrick Mowry wrote:

> Does 'file view activelog platform/log/diag2.log' not give you
anything?

On 2 of the servers no, but it does work on a 3rd one that was failing.
The end is:
08-19-2010 14:30:11 validate_network:     test script exists
08-19-2010 14:30:11 validate_network:     run network script via expect
[./diag_validate_network.exp > /dev/null]
08-19-2010 14:33:11 validate_network:     result: 256, message: Unknown
network error

The test reads passed after a reinstall.


> I'm not 100% sure for 6.1.1 but in later versions state 3 simply means

> that one of the servers in the cluster is down.

All members of the cluster are up, and I was using the Unified reporting
application to verify the host files and it showed all of them.  But a
reinstall is changing the state from 4 to 3, and fixing the problem
where newly created phones do not register to a subscriber.  Maybe once
I reinstall the last one and there are no more 4's the state will change
to 2.


-----Original Message-----
From: Ryan Ratliff [mailto:rratliff at cisco.com]
Sent: Thursday, August 26, 2010 2:51 PM
To: Patrick Mowry
Cc: Wes Sisk; cisco-voip at puck.nether.net
Subject: Re: [cisco-voip] CUCM 6.1.1 replication - pub state is 3-bad

I'm not 100% sure for 6.1.1 but in later versions state 3 simply means
that one of the servers in the cluster is down.  It is entirely possible
that replication is working for all other servers in the cluster.

You'd need to look at the CDR connections to find out which one is down
and this you can get via CURT or with root access.  

Does 'file view activelog platform/log/diag2.log' not give you anything?

-Ryan

On Aug 26, 2010, at 3:23 PM, Patrick Mowry wrote:

Thanks for the reply,

Host files are equivalent.

On the pub and the sub I reinstalled validate_network shows passed, but
on servers I have not reinstalled I get:
admin:utils diagnose module validate_network

Log file: /var/log/active/platform/log/diag2.log

Starting diagnostic test(s)
===========================
test - validate_network    : Unknown network error

Diagnostics Completed 

Not sure how to view the log. Files view activelog responds no file was
found

I've reinstalled 2 more servers and they pass validate_network and
phones register, but replication is still a 3.  I want to upgrade the
cluster, even if it's just to 6.1.5, but I'm reluctant to do so with
replication bad.


I'll keep at it.

Thanks again,

-Patrick