CUCM replication

Hi i want to replicate the subscriber across a wan link to create a redundant solution for my workplace can someone please indicate what is the minimum bandwidth required also is there a way to do replication only at night take inconsederation that it will only be a backup device incase the main pub and sub has failed or lost connection in the cloud currently we have ver 8.5 and is going to upgradeto vver 9.1 in about 2 to 3 months Thanx Benny Botha

Hi Guillaume,
Please check the following related post
https://supportforums.cisco.com/discussion/12166391/cucm-database-replication-status-mib
Looks like it is not possible.
HTH
Manish

Similar Messages

  • CUCM Replication after a restore

    Hi All,
    I have just completed a restore of a CUCM 9.1.1.20000-5 Publisher and Subscriber, all seems to be ok however replication is broken bewteen the two servers.
    When I run "utils dbreplication runtimestate" from the publisher, it fails with the following:
    admin:utils dbreplication runtimestate
    DB and Replication Services: ALL RUNNING
    DB CLI Status: No other dbreplication CLI is running...
    Cluster Replication State: BATCHING SYNC Requests from nodes at: 2013-12-06-14-59
         Sync Request Progress: Received 1 node requests for DB sync
         Sync Request Errors: NO ERRORS
    Traceback (most recent call last):
      File "/usr/local/cm/bin/DbReplRTstate.py", line 1143, in ?
        maxTime = getMaxDelay()
      File "/usr/local/cm/bin/DbReplRTstate.py", line 604, in getMaxDelay
        (rhostname, aliaslist, ipaddrlist) = socket.gethostbyaddr(temp[1])
    socket.herror: (2, 'Host name lookup failure')
    when i check the DB status from the reports, my pubnlisher is status = 3 (bad) and the publisher is status = 4 (initializing)
    I have tried to reset the replication etc but dont seem to be getting anywhere.
    Any help appreciated.
    Thanks
    Jason

    THanks Guys,
    No issues with the restore.
    Nothing changed in regrads to hostname, ip, etc.  All details were kept the same.
    The new hardwrae is a VMserver, we are testing the backup and restore process in the event of a DR failure.
    All looks to be working Ok, phones are registered and making calls updates made to DN and Users and being replicatied but the Replica state is still showing 3 - Bad.
    I have working through the doc that Ajay has mentioned, and replication foes through the steps and I can see it initalising but then after a while it go back to state 3.
    Thanks
    Jason

  • CUCM Replication SNMP

    Hi,
    i wondered how to check replication betweek publisher and subscriber via a request SNMP ...
    Thanks for your replies !
    Best regards,
    Guillaume

    Hi Guillaume,
    Please check the following related post
    https://supportforums.cisco.com/discussion/12166391/cucm-database-replication-status-mib
    Looks like it is not possible.
    HTH
    Manish

  • CUCM Replication status of 3

    Hi Everyone
    We had some work done on our CUCM cluster and when it was done the nodes all have a status of 3 except the publisher which is a 2.
    How serious is a 3 and will this cause any major issues with the performance of the system.
    Eric

    Replications state of 3 means that tables are suspect. This can happen because the other servers are unsure if  there is an  update to a user facing feature that has not been passed  from that sub  to the other device in the cluster.
    Steps to fix are given in the following link
    https://supportforums.cisco.com/docs/DOC-13672
    HTH
    Manish

  • Cucm replication status Off-Line

    Hello Everyone!!!
    I've faced to strange issue. I have 1 publisher and 6 subscribers. After reinstalling one of subscribers, database replication status of this
    subscriber shows 4.  Unified CM Database Status shows that files hosts, rhosts, sqlhosts are ok. 
    In Replication Server List (cdr list serv) reinstalled subscriber contain nothing. And it doesn't appear in another subscribers.
    All other subscribers including publisher have database replication status 2.
    Maybe anyone have idea how to solve this problem?

    If the standard dbreplication stop on subscribers, then publisher, then reset all from the publisher doesn't do the job (and by the way replication will take awhile before the subscriber status turns to 2, you can see progress under utils dbreplication runtimestate), then I would suggest using clusterreset on the publisher (use Cisco documentation to see how this is done). But this is only if you see that you can't get it working for you with the standard solution.
    I had similar problems not long ago after reinstalling a publisher, sometimes replication needs a bit of tough love :) After stopping replication on all subscribers, then publisher, then performing clusterreset on Publisher and tailing the log file to see when it's done (a few hours), I reset the replication and the cluster was good to go.

  • Three new CM 7.0(2) subscribers wont pass UTIM "Verify Servers" Test

    Hey all, installed 3 new subscibers to an existing, and I might add working, CM/Unity cluster.  But for the life of me I can't figure out why the 3 new servers fail the UTIM "Verify Servers" test.  The pub passes but not the three new subscribers.  The error states that the 3 new subs received a skinny reject message.
    Any clues?
    CM 7.1(5) and Unity 7.0(2) with 8.3(1) TSP

    I assume you are using the same Port for SCCP, and not trying to do anything different for the other nodes in the CUCM cluster when adding them as backups in UTIM.
    Are other devices, such as IP Phones, able to successfully register with the new CUCM nodes in the cluster?   Are all of the CUCM nodes on the same VLAN and location?   If other devices can't register to them either then you might have some kind of CUCM replication or change notification issue.
    Kind regards,
    Craig

  • Extension mobility not working

    Our users with extension mobility their user not displaying on the phone. However CM shows user logedin into the phone. Check all the services running. Need quick answer. It does not show ipcc extension.

    It took us 5 hours to figure the issue yesterday that Db replication was malfunctoning. We had a failover last week where some users were not able to login into the phones.but resolved on its own everything worked fine until yesterday. We saw some errors AQM server and restarted the services that took care of our CUCM replication issue. What AQM has to do with  it.

  • How to force database replication after CUCM upgrade

    Hello All, I will be doing an upgrade to version 10.5 from 8.5 of CUCM. I've done this before and as documented started with the publisher and then subscriber. When I have done this I always wait and check Database replication via RTMT and the CLI.
    I'm always nervous as this process seems to take a long time. Is this just a waiting game or is there a command that I can force replication to my subscribers? How long should this process really take? I never know....
    Thanks,
    Dan

    Dan,
    Use "utils dbreplication runtimestate" to check the replication status of your servers in the cluster. The servers should show connected to the publisher and a status of 2
    Or you can use unified reporting to generate report on db replication as follows.
    Check Database Replication:
    Access Publisher CUCM GUI
    Navigate to Cisco Unified Reporting
    Select System Reports
    Select Unified CM Database Status
    Generate New Report
    In the Unified CM Database Status section of the report, expand the View Details under the All servers have a good replication status and confirm a Replicate State for all servers of “2” as follows:

  • CUCM Database Replication Status MIB

    Hi Guys,
    Can you please help me whether we could monitor CCM database replication status through SNMP MIB or OID..
    Also please guide me in how to configure SNMP traps for the MIBS??
    Regards,
    Indrajith PC

    Hi,
    please take a look at the CUCM serviceability guide:
    http://www.cisco.com/c/en/us/td/docs/voice_ip_comm/cucm/service/9_0/admin/CUCM_BK_C136FE37_00_cisco-unified-serviceability-administration-90/CUCM_BK_C136FE37_00_cisco-unified-serviceability-administration-guide_preface_00.html
    I'm afraid there's no trap generated when DB replication issues occur, so you might want to do periodic polling.
    The above referenced document contains some basic information which MIB's may be interesting to you and how to get them.
    Personally, I would download and register them all, and then just walk the whole tree and cherrypick ;-)
    G.

  • CUCM - 8.6.2

    Hi All - Recently we have installed CUCM - 8.6.2 with PUB and SUB, After the installltion when we checked the DB Replication in CLI where it shows 2 for both PUB and SUB.
    When i check the GUI, It throws below Error.
    All necessary services are UP and Running.
    Connection to RTMT on cucm-sub could not be Established in PUB
    Connection to RTMT on cucm-PUB could not be Established in SUB
    Replication Status in PUB:
    PUB - 2 GOOD
    SUB - N/A
    Replication Status in SUB:
    SUB - 2 GOOD
    PUB - N/A
    Attached Screenshot for referrence.
    SIVANESAN R       

    Check this bug CSCua09290
    try this from cli and show us the result
    show perf queryclass "Number of Replicates Created and State of Replication"
    Regards
    Haitham

  • Unable to view 7841 Ip Phones on CUCM Subscriber

    We have a new CUCM BE 6000 ver 9.1.2 implementation, with a CUCM Publisher and a Subscriber servers
    As we have Cisco 7841 Ip Phones, we installed on both servers the recommneded device pack  (cmterm-devicepack9.1.2.11013-1.cop.sgn) as specified on link: "http://www.cisco.com/en/US/docs/voice_ip_comm/cucm/compat/devpack_comp_mtx.html"
    After we restarted CUCM cluster, we can add, view, modify 7841 Ip Phones on Publisher server ONLY , these Cisco 7841 are registered on CUCM Subscriber ,and they areworking good .
    But when we try to view/modify these Cisco Ip Phones 7841 on Subscriber server we got this error:
    "Unmapped Exception /usr/local/cm/db/xml/xml/Phone_7841_SIP_display_instance.xml (No such file or directory)"
    And we are unable to access them on Subscriber server.
    We also run "utils dbreplication status" on both servers and got :
    "No Errors or Mismatches found.
    Replication status is good on all available servers"
    ....when I viewed generated file.
    We also run "Unified CM Database status" report and got Replicate state= "2    Good " ob Subscriber server.
    But the situation is the same, Could any of you have an idea about this kind of problem??
    Thanks a lot in advanced.
    Enrique

    Hi ev1205,
    Re-install the cop file on the subscriber and restart the subscriber server. This should fix the problem.
    Errors like this indicate that the cop.sgn file was not installed correctly on the server.
    The fact that the phone is registered on the subscriber indicates that the model type is present in the tables, but maybe other details specific to this model were not installed correctly.
    Thanks
    Sreekanth

  • ** Ugrent --CUCM Upgrade 8.6 to 10.5 issue **

    Hello all,
    We have upgraded CUCM from 8.6 to 10.5 (direct upgrade).
    After upgrade we cant make changes into CUCM Publisher. While adding phones or device profile we are facing following error:
    Add failed. The Insert privilege is required for this operation.
    Also, our Cisco Unified Attendant Console Enterprise Addition sync with CUCM is not successful.
    CTI RoutePoint & CTI Ports are not registered gone into unknow state.
    Attached are Attendant console enterprise CUCM sync reports screen shot.
    DB Replication for whole cluster is good with value 2.
    Need urgent help - our system is in production now & we dont have cisco support agreement at the moment.
    Regards,

    Here are the install logs:
    admin:file view install system-history.log
    =======================================
    Product Name -    Cisco Unified Communications Manager
    Product Version - 10.5.1.10000-7
    Kernel Image -    2.6.32-431.3.1.el6.x86_64
    =======================================
    09/12/2014 22:16:31 | root: Install 10.5.1.10000-7 Start
    09/12/2014 15:45:21 | root: Boot 10.5.1.10000-7 Start
    09/13/2014 02:17:53 | root: Install 10.5.1.10000-7 Success
    09/13/2014 02:17:54 | root: Boot 10.5.1.10000-7 Start
    09/13/2014 02:41:59 | root: DRS Restore UCMVersion:10.5.1.10000-7 Start
    09/13/2014 02:55:15 | root: DRS Restore UCMVersion:10.5.1.10000-7 Error
    09/13/2014 03:06:55 | root: Boot 10.5.1.10000-7 Start
    09/13/2014 03:16:24 | root: DRS Restore UCMVersion:10.5.1.10000-7 Start
    09/13/2014 03:55:07 | root: DRS Restore UCMVersion:10.5.1.10000-7 Success
    09/13/2014 03:59:19 | root: Boot 10.5.1.10000-7 Start
    09/13/2014 06:16:40 | root: DRS Restore UCMVersion:10.5.1.10000-7 Start
    09/13/2014 06:21:33 | root: DRS Restore UCMVersion:10.5.1.10000-7 Error
    09/13/2014 09:31:10 | root: DRS Backup UCMVersion:10.5.1.10000-7 Start
    09/13/2014 10:09:25 | root: DRS Backup UCMVersion:10.5.1.10000-7 Success
    09/14/2014 12:38:48 | root: Restart 10.5.1.10000-7 Start
    options: q=quit, n=next, p=prev, b=begin, e=end (lines 1 - 20 of 21) :
    admin:
    admin:

  • CUCM 6.1(5) "jump" upgrade to 9.1(2)

    I am in the process of trying to upgrade a customers CUCM 6.1(5) environment to 9.1(2) using the jump upgrade method. The current system is on MCS servers and I have installed new 6.1(5) CUCM's on a UCS, applied th required cop file to disable licensing check and performed a restore. When I look at the DB replication status, it has failed. Has anyone attempted performing the upgrade using this method and if so, was it successful. Here is a link to a Voice of the Engineer session that covers this upgrade path
    https://communities.cisco.com/docs/DOC-7823
    Regards,
    Dave

    Did you recreate your whole cluster, just as it is in production, on UCS???
    I did the procedure from 6.1(5) and 7.1(5) and had no problems.
    HTH
    java
    if this helps, please rate
    www.cisco.com/go/pdihelpdesk

  • Call Manager will not activate in CUCM 7

    i have installed cucm 7 and can get to it with windows IE, but when i try to activate call manager in the cisco unified servicability it give me this error:
    Update Failed for the Service(s): Cisco CallManager Request unsuccessful to license manager(Please check the Licensing logs for further details)
    i can not add any phones or do anything.
    can someone help.

    Hello Sanil,
    You have to check your services on your publisher and subscriber , or you  can use ssh and login to your publisher and check if the replication   between your pubisher and subscriber is perfect or not. Most likely services not started yet.
    Br,
    Nadeem

  • CUCM Version 9.X generate alerts every day

    Hi To all
    I receive everyday alerts that two nodes from the cluster are down
    ServerDown occurred.
    Node 10.10.1.1 is unreachable.
     ServerDown occurred.
    Node 10.10.1.2 is unreachable.
    We have a cluster of four cucms
    First ucs server located to the building A and holding the below cucms
    10.10.0.1
    10.10.0.2
    Second ucs server located to the building B and holding the below cucms
    10.10.1.1
    10.10.1.2
    Building A connected with Building B with dark fiber
    Checked  the interface into the layer 3 devices on both sides  and are clear
    No errors no drop packets
    check the output from the replication status
    The ping msec is acceptable?
    admin:utils dbreplication runtimestate
    DB and Replication Services: ALL RUNNING
    DB CLI Status: No other dbreplication CLI is running...
    Cluster Replication State: Replication status command started at: 2014-03-20-09-56
         Replication status command COMPLETED 603 tables checked out of 603
         Errors or Mismatches Were Found!!!
         Use 'file view activelog cm/trace/dbl/sdi/ReplicationStatus.2014_03_20_09_56_34.out' to see the details
    DB Version: ccm9_1_1_10000_11
    Repltimeout set to: 300s
    PROCESS option set to: 1
    Cluster Detailed View from CM1 (4 Servers):
                                    PING            CDR Server      REPL.   DBver&  REPL.   REPLICATION SETUP
    SERVER-NAME     IP ADDRESS      (msec)  RPC?    (ID) & STATUS   QUEUE   TABLES  LOOP?   (RTMT) & details
    CM1     10.10.0.1      0.032   Yes     (2)  Connected   0      match   Yes     (2) PUB Setup Completed
    CM2     10.10.0.2      0.099   Yes     (3)  Connected   0      match   Yes     (2) Setup Completed
    CM3     10.10.1.1      1.378   Yes     (4)  Connected   140    match   Yes     (2) Setup Completed
    CM4     10.10.1.2      1.232   Yes     (5)  Connected   140    match   Yes     (2) Setup Completed
    Regrds
    cc

    Hi,
    Your cluster could be affected by the following bug
    https://tools.cisco.com/bugsearch/bug/CSCtl75789
    Symptom:
    The RTMT receives a false alarm that the Server is down.
    Conditions:
    Any error in the network that closes the TCP session on the ports 1090 and 1099 will cause the false alarm.
    Workaround:
    none.
    HTH
    Manish

Maybe you are looking for