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

[Ryan Ratliff]

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
-----Original Message-----
From: Wes Sisk [mailto:wsisk at cisco.com] 
Sent: Thursday, August 26, 2010 1:43 PM
To: Patrick Mowry
Cc: cisco-voip at puck.nether.net
Subject: Re: [cisco-voip] CUCM 6.1.1 replication - pub state is 3-bad

most likely hosts files ore cluster manager are blocking replication.  
6.1.1 serviceability is very lacking so not much is lacking.  TAC case
and remote account will be required for proper investigation.

if you have 'utils diagnose' at CLI you can start there and also use
Cisco Unified Reporting Tool (CURT) reports if available.

/Wes

Patrick Mowry wrote:
> Good day,
> 
> Short version: when a cluster reset and reinstalling a sub does not
fix replication, what do you do next?
> 
> A customer has a 6.1.1-3000-2 cluster of 6 servers that was installed
in an environment with power issues. An initial symptom was newly
created phone would show a dberror when registering to a subscriber, but
could register to the pub just fine. Replication  state of all servers
was 3. Powercycled the cluster, and then tried a clusterreset. The end
result of this was the pub was still 3 and all subscribers 4. 
> 
> Last night I reinstalled one subscriber and this returned it's state
to 3. Phones can register to this reinstalled server so I'm tempted to
reinstall the others as well. But I don't expect it to be a proper fix. 
> 
> Any suggestions are appreciated,
> 
> -Patrick
> 
> 
> _______________________________________________
> cisco-voip mailing list
> cisco-voip at puck.nether.net
> https://puck.nether.net/mailman/listinfo/cisco-voip
> 

_______________________________________________
cisco-voip mailing list
cisco-voip at puck.nether.net
https://puck.nether.net/mailman/listinfo/cisco-voip