Possible Communications Manager DB Replication Issue

[sean.demura]

Hello,

I was in the process of getting ready to change DNS settings on my
publisher (GTLIN21CCM) and my two subscribers (GTLIN22CCM, GTLIN23CCM) and wanted to check
the DB replication status as I've read from Cisco's support site that changing DNS
settings can break replication. (
http://www.cisco.com/en/US/products/sw/voicesw/ps556/products_configuration_
example09186a0080a9a0fe.shtml )

Upon running a Unified CM Database Status report, I received an interesting status report
that I am confused about.

Under the Unified CM Database Status section of the report results, from GTLIN221CCM
(Publisher) I get the messages
x - The gtlin221ccm server cannot be reached.
x - The gtlin23ccm server cannot be reached.
v - All servers have a replication count of 393
v - all servers have a good replication status
-View Details
     gtlin223ccm 393 2-good

Why does it not report the two publishers under View Details? Likewise if I run this from
the other call managers I get the same messages (with the respective host names flipped
around).

I went to the CLI and ran several tests

' show perf query class "Number of Replicates Created and State of Replication" '

{

admin:show perf query class "Number of Replicates Created and State of Replication"
==>query class :

- Perf class (Number of Replicates Created and State of Replication) has instances and
values:
    ReplicateCount  -> Number of Replicates Created   = 393
    ReplicateCount  -> Replicate_State                = 2

}

' utils dbreplication status '
( did not find any rows/columns out of sync )

and did not see anything out of the 'ordinary'

Currently running Unified Communications System version: 6.1.3.1000-16

Is there anything I should worry about, look for, adjust, change before I go ahead and do
a DNS configuration change on these boxes?

[Rob Huffman]

Hi Sean,

You may be seeing this CUCM 6.1 bug as i don't see your version as "fixed-in";

CSCsv21137 - Unified Reporting showing the Sub not reachable

Description

Symptom:

When running  Unified reporting tool in 6.1.2 and specifically the Database summary  report it reports one or more of the subs not reachable.

You can  confirm subs are indeed reachable with 'utils dbreplication status' and  seeing all the replicates.  'utils network connectivity' can also  confirm connectivity between nodes.

Conditions:

Subs  can ping by hostname and confimred all the tables are good and in sync.   Issue occurs with mismatch in case between hostname and database,  example: server1 vs. SERVER1.  This defect is triggered by CURT using  case sensitive search on hostname.

Workaround:

set database and platform servername to same case.

Details

First Found in:                          (3)

6.1,6.1(2.1000.13),7.0(1.1101.8)

Status:

Fixed

Last Modified:

Feb 27,2012

Fixed in:                          (7)

7.1(2.10000.16),7.1(1.39000.134),7.0(2.22900.2)

7.0(2.22031.1),6.1(4.1000.10),6.1(3.9999.1)

6.1(3.9901.120)

Less

Product:

Cisco Unified Communications Manager (CallManager)

Platform:

Dependent

Severity:

3 - moderate

Cheers!

Rob

"Show a little faith, there's magic in the night" - Springsteen