[cisco-voip] CUCM Upgrade failure...
Jonathan Charles
jonvoip at gmail.com
Tue Nov 17 12:23:06 EST 2015
Watching the log... it does this a bunch of times:
2015-11-17 11:18:37,460 INFO [http-bio-443-exec-9] resources.Handler.start
- --- Start: com.cisco.ucmap.resources.ClusterHandler.getCluster ---
2015-11-17 11:18:37,461 INFO [http-bio-443-exec-9]
resources.ClusterHandler.getCluster - PathParam = 1616
2015-11-17 11:18:37,461 INFO [http-bio-443-exec-9]
custom.LogicBroker.executePreLogic - No pre DB custom logic for Cluster.read
2015-11-17 11:18:37,462 INFO [http-bio-443-exec-9]
custom.LogicBroker.executePreLogic - No pre DB custom logic for
DBEntity.read
2015-11-17 11:18:37,477 INFO [http-bio-443-exec-9]
custom.LogicBroker.executePostLogic - No post DB custom logic for
Cluster.read
2015-11-17 11:18:37,477 INFO [http-bio-443-exec-9]
custom.LogicBroker.executePostLogic - No post DB custom logic for
DBEntity.read
2015-11-17 11:18:37,477 INFO [http-bio-443-exec-9]
resources.Localization.loadResourceBundles - Loading properties for
language en
2015-11-17 11:18:37,477 INFO [http-bio-443-exec-9]
resources.Handler.localizeResponse - Localizing 0 messages
2015-11-17 11:18:37,477 INFO [http-bio-443-exec-9]
resources.Handler.localizeResponse - Localizing 1 entities
2015-11-17 11:18:37,478 INFO [http-bio-443-exec-9] resources.Handler.end -
--- End: com.cisco.ucmap.resources.ClusterHandler.getCluster ---
And then dies:
2015-11-17 11:19:08,654 INFO [http-bio-443-exec-9] resources.Handler.end -
--- End: com.cisco.ucmap.resources.ClusterHandler.getCluster ---
2015-11-17 11:19:18,509 INFO [DefaultQuartzScheduler_Worker-3]
inventory.Migration.installCop - installCop return cmdOutput
2015-11-17 11:19:18,509 INFO [DefaultQuartzScheduler_Worker-3]
inventory.Migration.installCop - installCop return cmdOutput CALLING
ucmapLib::upgrade { 10.0.126.10 ccmadministrator 10.0.126.21
ciscocm.ucmap_platformconfig.cop.sgn cop/ adminsftp 0}
CALLING ucmapLib::adminLogin 10.0.126.10 ccmadministrator
SUCCESS ucmapLib::adminLogin
CALLING ucmapLib::initiateUpgrade {exp3
ciscocm.ucmap_platformconfig.cop.sgn}
CALLING ucmapLib::setPagination {exp3 0}
2015-11-17 11:19:18,510 INFO [DefaultQuartzScheduler_Worker-3]
inventory.NatAddressHelper.getPublicIP - Application Node private IP
Address is : 10.0.126.10
2015-11-17 11:19:18,510 INFO [DefaultQuartzScheduler_Worker-3]
inventory.Migration.nodeDiscovery - Return nodeDiscovery result 103
2015-11-17 11:19:18,510 INFO [DefaultQuartzScheduler_Worker-3]
scheduler.CustomJob.acquireLock - T1876:TA1877:N1617 waiting for DB lock
2015-11-17 11:19:18,510 INFO [DefaultQuartzScheduler_Worker-3]
scheduler.CustomJob.acquireLock - T1876:TA1877:N1617 acquired lock
2015-11-17 11:19:18,515 INFO [DefaultQuartzScheduler_Worker-3]
db.EntityBroker.updateNodeInfo - Updated 1617 to v19
2015-11-17 11:19:18,515 INFO [DefaultQuartzScheduler_Worker-3]
scheduler.CustomJob.releaseLock - T1876:TA1877:N1617 releasing DB lock
options: q=quit, n=next, p=prev, b=begin, e=end (lines 1661 - 1680 of 1760)
:
2015-11-17 11:19:18,515 INFO [DefaultQuartzScheduler_Worker-3]
scheduler.DiscoveryJob.executeJob - discovery node 1617 failed with
errorcode 103
2015-11-17 11:19:18,515 INFO [DefaultQuartzScheduler_Worker-3]
scheduler.CustomJob.acquireLock - T1876:TA1877:N1617 waiting for DB lock
2015-11-17 11:19:18,515 INFO [DefaultQuartzScheduler_Worker-3]
scheduler.CustomJob.acquireLock - T1876:TA1877:N1617 acquired lock
2015-11-17 11:19:18,522 INFO [DefaultQuartzScheduler_Worker-3]
scheduler.Scheduler.addStatusMessage - Adding ERROR message
[migration_errorCode_103] to task action 1877
2015-11-17 11:19:18,528 INFO [DefaultQuartzScheduler_Worker-3]
db.EntityBroker.createStatusMessage - Created 1901
2015-11-17 11:19:18,530 INFO [DefaultQuartzScheduler_Worker-3]
db.EntityBroker.updateTaskAction - Updated 1877 to v9
2015-11-17 11:19:18,530 INFO [DefaultQuartzScheduler_Worker-3]
scheduler.CustomJob.releaseLock - T1876:TA1877:N1617 releasing DB lock
2015-11-17 11:19:18,530 INFO [DefaultQuartzScheduler_Worker-3]
scheduler.CustomJob.acquireLock - T1876:TA1877:N1617 waiting for DB lock
2015-11-17 11:19:18,530 INFO [DefaultQuartzScheduler_Worker-3]
scheduler.CustomJob.acquireLock - T1876:TA1877:N1617 acquired lock
2015-11-17 11:19:18,530 INFO [DefaultQuartzScheduler_Worker-3]
scheduler.Scheduler.isJobActive - Searching for job T1876:TA1877:N1617
2015-11-17 11:19:18,530 INFO [DefaultQuartzScheduler_Worker-3]
scheduler.Scheduler.isJobActive - Job T1876:TA1877:N1617 active = true
2015-11-17 11:19:18,530 INFO [DefaultQuartzScheduler_Worker-3]
scheduler.CustomJob.setNodeStatus - Updating node 1617's status to FAILED
2015-11-17 11:19:18,545 INFO [DefaultQuartzScheduler_Worker-3]
scheduler.CustomJob.findNodeStatus - Looking for s900pxiptcmp or 10.0.126.10
2015-11-17 11:19:18,545 INFO [DefaultQuartzScheduler_Worker-3]
scheduler.CustomJob.findNodeStatus - Comparing s900pxiptcmp
2015-11-17 11:19:18,546 INFO [DefaultQuartzScheduler_Worker-3]
db.EntityBroker.updateNodeStatus - Updated 1882 to v3
2015-11-17 11:19:18,553 INFO [DefaultQuartzScheduler_Worker-3]
scheduler.CustomJob.finishJob - Node 1617 successful = false
2015-11-17 11:19:18,555 INFO [DefaultQuartzScheduler_Worker-3]
scheduler.Scheduler.addStatusMessage - Adding ERROR message
[scheduler.node.fail] to task action 1877
2015-11-17 11:19:18,562 INFO [DefaultQuartzScheduler_Worker-3]
db.EntityBroker.createStatusMessage - Created 1904
2015-11-17 11:19:18,564 INFO [DefaultQuartzScheduler_Worker-3]
db.EntityBroker.updateTaskAction - Updated 1877 to v10
2015-11-17 11:19:18,564 INFO [DefaultQuartzScheduler_Worker-3]
scheduler.Scheduler.jobCompleted - Node 1617 in task action 1877 in task
1876 has finished
options: q=quit, n=next, p=prev, b=begin, e=end (lines 1681 - 1700 of 1760)
:
2015-11-17 11:19:18,599 INFO [DefaultQuartzScheduler_Worker-3]
scheduler.Scheduler.jobCompleted - The trigger for node 1617 was deleted
2015-11-17 11:19:18,599 INFO [DefaultQuartzScheduler_Worker-3]
scheduler.Scheduler.findNumberOfJobsRemaining - 0 remaining job(s) in task
action 1877
2015-11-17 11:19:18,599 INFO [DefaultQuartzScheduler_Worker-3]
scheduler.Scheduler.jobCompleted - There are no more remaining jobs in task
action 1877 in task 1876
2015-11-17 11:19:18,602 INFO [DefaultQuartzScheduler_Worker-3]
db.EntityBroker.createEndTime - Created 1908
2015-11-17 11:19:18,603 INFO [DefaultQuartzScheduler_Worker-3]
db.EntityBroker.updateTaskAction - Updated 1877 to v11
2015-11-17 11:19:18,604 INFO [DefaultQuartzScheduler_Worker-3]
db.EntityBroker.updateTaskAction - Updated 1877 to v12
2015-11-17 11:19:18,604 INFO [DefaultQuartzScheduler_Worker-3]
scheduler.Scheduler.addStatusMessage - Adding ERROR message
[scheduler.taskaction.failednodes] to task action 1877
2015-11-17 11:19:18,613 INFO [DefaultQuartzScheduler_Worker-3]
db.EntityBroker.createStatusMessage - Created 1909
2015-11-17 11:19:18,614 INFO [DefaultQuartzScheduler_Worker-3]
db.EntityBroker.updateTaskAction - Updated 1877 to v13
2015-11-17 11:19:18,614 INFO [DefaultQuartzScheduler_Worker-3]
scheduler.Scheduler.updateTaskActionStatus - task action 1877 set to FAILED
2015-11-17 11:19:18,631 INFO [DefaultQuartzScheduler_Worker-3]
scheduler.Scheduler.findNextTaskAction - Execute last failed task action =
false
2015-11-17 11:19:18,631 INFO [DefaultQuartzScheduler_Worker-3]
scheduler.Scheduler.findNextTaskAction - Looking for sequence number >= 1
2015-11-17 11:19:18,631 INFO [DefaultQuartzScheduler_Worker-3]
scheduler.Scheduler.findNextTaskAction - task action 1877 sequence number =
1
2015-11-17 11:19:18,631 INFO [DefaultQuartzScheduler_Worker-3]
scheduler.Scheduler.findNextTaskAction - task action 1877 status = FAILED
2015-11-17 11:19:18,632 INFO [DefaultQuartzScheduler_Worker-3]
scheduler.Scheduler.findNextTaskAction - There are no task actions waiting
to be scheduled
2015-11-17 11:19:18,633 INFO [DefaultQuartzScheduler_Worker-3]
db.EntityBroker.updateTask - Updated 1876 to v7
2015-11-17 11:19:18,634 INFO [DefaultQuartzScheduler_Worker-3]
db.EntityBroker.updateTask - Updated 1876 to v8
2015-11-17 11:19:18,634 INFO [DefaultQuartzScheduler_Worker-3]
scheduler.Scheduler.addStatusMessage - Adding ERROR message
[scheduler.task.pause] to task 1876
2015-11-17 11:19:18,637 INFO [DefaultQuartzScheduler_Worker-3]
db.EntityBroker.createStatusMessage - Created 1915
2015-11-17 11:19:18,638 INFO [DefaultQuartzScheduler_Worker-3]
db.EntityBroker.updateTask - Updated 1876 to v9
options: q=quit, n=next, p=prev, b=begin, e=end (lines 1701 - 1720 of 1760)
:
2015-11-17 11:19:18,639 INFO [DefaultQuartzScheduler_Worker-3]
scheduler.Scheduler.addStatusMessage - sendEmail = true
2015-11-17 11:19:18,639 INFO [DefaultQuartzScheduler_Worker-3]
resources.Localization.loadResourceBundles - the http headers object has
not been set
2015-11-17 11:19:18,639 INFO [DefaultQuartzScheduler_Worker-3]
db.EntityBroker.getNotifications - Query = SELECT entity FROM Notification
entity ORDER BY entity.pkId
2015-11-17 11:19:18,639 INFO [DefaultQuartzScheduler_Worker-3]
db.EntityBroker.getNotifications - Located 0 entities
2015-11-17 11:19:18,639 INFO [DefaultQuartzScheduler_Worker-3]
notification.EmailHandler.getNotificationLevel - Email notifications have
not been configured
2015-11-17 11:19:18,639 INFO [DefaultQuartzScheduler_Worker-3]
scheduler.Scheduler.updateTaskStatus - task 1876 set to PAUSE_ERROR
2015-11-17 11:19:18,639 INFO [DefaultQuartzScheduler_Worker-3]
scheduler.CustomJob.releaseLock - T1876:TA1877:N1617 releasing DB lock
2015-11-17 11:19:18,640 INFO [DefaultQuartzScheduler_Worker-3]
scheduler.CustomJob.execute - Job T1876:TA1877:N1617 has been cleaned = true
2015-11-17 11:19:18,640 INFO [DefaultQuartzScheduler_Worker-3]
scheduler.CustomJob.execute - Job T1876:TA1877:N1617 finished
2015-11-17 11:19:18,728 INFO [http-bio-443-exec-9] resources.Handler.start
- --- Start: com.cisco.ucmap.resources.ClusterHandler.getCluster ---
2015-11-17 11:19:18,729 INFO [http-bio-443-exec-9]
resources.ClusterHandler.getCluster - PathParam = 1616
2015-11-17 11:19:18,729 INFO [http-bio-443-exec-9]
custom.LogicBroker.executePreLogic - No pre DB custom logic for Cluster.read
2015-11-17 11:19:18,729 INFO [http-bio-443-exec-9]
custom.LogicBroker.executePreLogic - No pre DB custom logic for
DBEntity.read
2015-11-17 11:19:18,741 INFO [http-bio-443-exec-9]
custom.LogicBroker.executePostLogic - No post DB custom logic for
Cluster.read
2015-11-17 11:19:18,741 INFO [http-bio-443-exec-9]
custom.LogicBroker.executePostLogic - No post DB custom logic for
DBEntity.read
2015-11-17 11:19:18,741 INFO [http-bio-443-exec-9]
resources.Localization.loadResourceBundles - Loading properties for
language en
2015-11-17 11:19:18,742 INFO [http-bio-443-exec-9]
resources.Handler.localizeResponse - Localizing 0 messages
2015-11-17 11:19:18,742 INFO [http-bio-443-exec-9]
resources.Handler.localizeResponse - Localizing 1 entities
2015-11-17 11:19:18,742 INFO [http-bio-443-exec-9] resources.Handler.end -
--- End: com.cisco.ucmap.resources.ClusterHandler.getCluster ---
2015-11-17 11:19:18,853 INFO [http-bio-443-exec-9] resources.Handler.start
- --- Start: com.cisco.ucmap.resources.ClusterHandler.getClusters ---
options: q=quit, n=next, p=prev, b=begin, e=end (lines 1721 - 1740 of 1760)
:
2015-11-17 11:19:18,854 INFO [http-bio-443-exec-9]
custom.LogicBroker.executePreLogic - No pre DB custom logic for Cluster.read
2015-11-17 11:19:18,854 INFO [http-bio-443-exec-9]
custom.LogicBroker.executePreLogic - No pre DB custom logic for
DBEntity.read
2015-11-17 11:19:18,854 INFO [http-bio-443-exec-9]
db.EntityBroker.getClusters - Query = SELECT entity FROM Cluster entity
ORDER BY entity.pkId
2015-11-17 11:19:18,867 INFO [http-bio-443-exec-9]
db.EntityBroker.getClusters - Located 1 entities
2015-11-17 11:19:18,867 INFO [http-bio-443-exec-9]
custom.LogicBroker.executePostLogic - No post DB custom logic for
Cluster.read
2015-11-17 11:19:18,868 INFO [http-bio-443-exec-9]
custom.LogicBroker.executePostLogic - No post DB custom logic for
DBEntity.read
2015-11-17 11:19:18,868 INFO [http-bio-443-exec-9]
resources.Localization.loadResourceBundles - Loading properties for
language en
2015-11-17 11:19:18,868 INFO [http-bio-443-exec-9]
resources.Handler.localizeResponse - Localizing 0 messages
2015-11-17 11:19:18,868 INFO [http-bio-443-exec-9]
resources.Handler.localizeResponse - Localizing 1 entities
2015-11-17 11:19:18,869 INFO [http-bio-443-exec-9] resources.Handler.end -
--- End: com.cisco.ucmap.resources.ClusterHandler.getClusters ---
2015-11-17 11:20:15,393 INFO [http-bio-443-exec-9] resources.Handler.start
- --- Start: com.cisco.ucmap.resources.ClusterHandler.getCluster ---
2015-11-17 11:20:15,393 INFO [http-bio-443-exec-9]
resources.ClusterHandler.getCluster - PathParam = 1616
2015-11-17 11:20:15,394 INFO [http-bio-443-exec-9]
custom.LogicBroker.executePreLogic - No pre DB custom logic for Cluster.read
2015-11-17 11:20:15,394 INFO [http-bio-443-exec-9]
custom.LogicBroker.executePreLogic - No pre DB custom logic for
DBEntity.read
2015-11-17 11:20:15,409 INFO [http-bio-443-exec-9]
custom.LogicBroker.executePostLogic - No post DB custom logic for
Cluster.read
2015-11-17 11:20:15,409 INFO [http-bio-443-exec-9]
custom.LogicBroker.executePostLogic - No post DB custom logic for
DBEntity.read
2015-11-17 11:20:15,410 INFO [http-bio-443-exec-9]
resources.Localization.loadResourceBundles - Loading properties for
language en
2015-11-17 11:20:15,410 INFO [http-bio-443-exec-9]
resources.Handler.localizeResponse - Localizing 0 messages
2015-11-17 11:20:15,410 INFO [http-bio-443-exec-9]
resources.Handler.localizeResponse - Localizing 1 entities
2015-11-17 11:20:15,411 INFO [http-bio-443-exec-9] resources.Handler.end -
--- End: com.cisco.ucmap.resources.ClusterHandler.getCluster ---
On Tue, Nov 17, 2015 at 11:06 AM, Jonathan Charles <jonvoip at gmail.com>
wrote:
> Nope, not all good... new error... the upgrade failed so I deleted the
> cluster and re-added... it finds all of the subscribers, but it times out
> on the publisher....
>
> I have verified all services are running on the Pub and it looks clean...
>
>
>
> Jonathan
>
> On Mon, Nov 16, 2015 at 10:20 AM, Anthony Holloway <
> avholloway+cisco-voip at gmail.com> wrote:
>
>> Looks like you're all good now, but as a heads up to everyone else, don't
>> stop at checking NTP with "utils ntp status". You will fail to upgrade if
>> your NTP configuration has an FQHN for the NTP server which begins with a
>> digit.
>>
>> E.g., 0.pool.ntp.org
>>
>> You will not see the hostname in the output of "utils ntp status", as it
>> will only show you the resolved IP address. So, you will also need to
>> issue a "utils ntp config" to see what value was entered by the
>> administrator.
>>
>> This is the only defect reference I found, though my upgrade I hit it on
>> was an 8.6 to 10.5 Refresh Upgrade (RU) (Not PCD).
>>
>> https://tools.cisco.com/bugsearch/bug/CSCtj07817
>>
>> On Sun, Nov 15, 2015 at 10:43 PM, Jonathan Charles <jonvoip at gmail.com>
>> wrote:
>>
>>> OK, a reboot of CPCD got it passed that error...
>>>
>>>
>>> Jonathan
>>>
>>> On Sun, Nov 15, 2015 at 9:40 PM, Jonathan Charles <jonvoip at gmail.com>
>>> wrote:
>>>
>>>> Yeah, the error I am getting is:
>>>>
>>>> 1 nodes(s) in Export task action ID #1127... on the Publisher...
>>>>
>>>> I will try rebooting everything...
>>>>
>>>>
>>>>
>>>> Jonathan
>>>>
>>>> On Sun, Nov 15, 2015 at 9:35 PM, Ryan Huff <ryanhuff at outlook.com>
>>>> wrote:
>>>>
>>>>> Looks healthy ...
>>>>>
>>>>> I recall trying PCD once and I hit really strange issues too. For that
>>>>> upgrade, I ultimately abandoned PCD and built new VMs with the Answer File
>>>>> Generator then a DRS backup/restore.
>>>>>
>>>>> Not sure where you are in your timeline or if it is that important but
>>>>> it is definitely something I would consider. Sometimes you can spend more
>>>>> time trying to get the silly tools to work, than to just do the work
>>>>> yourself.
>>>>>
>>>>> Google is littered with PCD weirdness; great idea of an application,
>>>>> just not there yet IMO.
>>>>>
>>>>> -Ryan
>>>>>
>>>>>
>>>>>
>>>>> Sent from my iPad
>>>>> On Nov 15, 2015, at 10:19 PM, Jonathan Charles <jonvoip at gmail.com>
>>>>> wrote:
>>>>>
>>>>> Everything looks good....
>>>>>
>>>>>
>>>>> admin:utils ntp status
>>>>> ntpd (pid 19674) is running...
>>>>>
>>>>> remote refid st t when poll reach delay offset
>>>>> jitter
>>>>>
>>>>> ==============================================================================
>>>>> 127.127.1.0 .LOCL. 10 l 21 64 377 0.000 0.000
>>>>> 0.001
>>>>> 10.0.31.2 10.0.31.3 3 u 175 1024 377 0.635 -5.771
>>>>> 2.042
>>>>> *10.0.31.3 129.6.15.29 2 u 970 1024 377 0.510 -11.340
>>>>> 0.449
>>>>> 10.1.31.2 10.0.31.3 3 u 490 1024 377 0.850 -9.114
>>>>> 4.881
>>>>> +10.1.31.3 129.6.15.29 2 u 184 1024 377 0.817 -4.085
>>>>> 5.355
>>>>>
>>>>>
>>>>> synchronised to NTP server (10.0.31.3) at stratum 3
>>>>> time correct to within 68 ms
>>>>> polling server every 1024 s
>>>>>
>>>>> Current time in UTC is : Mon Nov 16 03:16:14 UTC 2015
>>>>> Current time in America/Chicago is : Sun Nov 15 21:16:14 CST 2015
>>>>> admin:
>>>>>
>>>>> admin:utils diagnose module validate_network
>>>>>
>>>>> Log file: platform/log/diag1.log
>>>>>
>>>>> Starting diagnostic test(s)
>>>>> ===========================
>>>>> test - validate_network : Passed
>>>>>
>>>>> Diagnostics Completed
>>>>>
>>>>> admin:#
>>>>>
>>>>> admin:utils dbreplication runtimestate
>>>>>
>>>>> DB and Replication Services: ALL RUNNING
>>>>>
>>>>> Cluster Replication State: Replication repair command started at:
>>>>> 2014-06-20-23-22
>>>>> Replication repair command COMPLETED 541 tables processed out of
>>>>> 541
>>>>> Errors or Mismatches Were Found:
>>>>>
>>>>> Use 'file view activelog
>>>>> cm/trace/dbl/sdi/ReplicationRepair.2014_06_20_23_22_51.out' to see the
>>>>> details
>>>>>
>>>>> DB Version: ccm8_6_2_20000_2
>>>>> Number of replicated tables: 541
>>>>>
>>>>> Cluster Detailed View from PUB (5 Servers):
>>>>>
>>>>> PING REPLICATION REPL.
>>>>> DBver& REPL. REPLICATION SETUP
>>>>> SERVER-NAME IP ADDRESS (msec) RPC? STATUS QUEUE
>>>>> TABLES LOOP? (RTMT) & details
>>>>> ----------- ------------ ------ ---- ----------- -----
>>>>> ------- ----- -----------------
>>>>> IPTCMS02 10.0.126.12 0.196 Yes Connected 0
>>>>> match Yes (2) Setup Completed
>>>>> IPTCMS01 10.0.126.11 0.151 Yes Connected 0
>>>>> match Yes (2) Setup Completed
>>>>> IPTCMP 10.0.126.10 0.065 Yes Connected 0
>>>>> match Yes (2) PUB Setup Completed
>>>>> IPTCMS03 10.1.126.13 0.545 Yes Connected 0
>>>>> match Yes (2) Setup Completed
>>>>> IPTCMS04 10.1.126.14 0.527 Yes Connected 0
>>>>> match Yes (2) Setup Completed
>>>>>
>>>>> admin:
>>>>>
>>>>> On Sun, Nov 15, 2015 at 9:14 PM, Ryan Huff <ryanhuff at outlook.com>
>>>>> wrote:
>>>>>
>>>>>> Also worth noting that if CCM NTP is synchronized to a Windows server
>>>>>> (even if it shows Stratum 3 or better); that is a problem you'll need to
>>>>>> correct as SNTP can play hell with UCOS and do some pretty weird stuff.
>>>>>>
>>>>>> Thanks,
>>>>>>
>>>>>> Ryan
>>>>>>
>>>>>> On Nov 15, 2015, at 10:06 PM, Ryan Huff <ryanhuff at outlook.com> wrote:
>>>>>>
>>>>>> If the FROM CCM version was unrestricted, it would say "
>>>>>> *Unrestricted*" after the version number on the "*Active Master
>>>>>> Version"* line. If it does not say "*Unrestricted*", then it is the
>>>>>> more common restricted version.
>>>>>>
>>>>>> As to your original issue, I would start with all the usual suspects.
>>>>>> Is the FROM CCM cluster healthy to start with; dns, ntp, replication ...
>>>>>> etc?
>>>>>>
>>>>>> From CCM:
>>>>>>
>>>>>> 1.) #utils diagnose module validate_network
>>>>>> (Should see *Passed*)
>>>>>>
>>>>>> 2.) #utils ntp status
>>>>>> (Pub should be synchronized and Strata 3 or better)
>>>>>>
>>>>>> 3.) #utils dbreplication runtimestate
>>>>>> (Should see *2 - Setup Completed* for all nodes)
>>>>>>
>>>>>> If PCD is moving the apps to a new platform/chassis, make sure the
>>>>>> *target* environment can reach all the same network assets as the
>>>>>> *from* environment.
>>>>>>
>>>>>> Thanks,
>>>>>>
>>>>>> Ryan
>>>>>>
>>>>>> On Nov 15, 2015, at 9:34 PM, Jonathan Charles <jonvoip at gmail.com>
>>>>>> wrote:
>>>>>>
>>>>>> It just says the version number...
>>>>>>
>>>>>> admin:show version active
>>>>>> Active Master Version: 8.6.2.20000-2
>>>>>> Active Version Installed Software Options:
>>>>>> cmterm-7942_7962-sccp.9-3-1ES27-rel.cop
>>>>>> cmterm-devicepack8.6.2.24118-1.cop
>>>>>> ciscocm.refresh_upgrade_v1.1.cop
>>>>>> ciscocm.ucmap_platformconfig.cop
>>>>>> ciscocm.migrate-export-v1.12.cop
>>>>>> admin:
>>>>>>
>>>>>>
>>>>>> Jonahan
>>>>>>
>>>>>> On Sun, Nov 15, 2015 at 7:26 PM, Ryan Huff <ryanhuff at outlook.com>
>>>>>> wrote:
>>>>>>
>>>>>>> Did you actually dump the logs to a serial interface (curious what
>>>>>>> it shows)?
>>>>>>>
>>>>>>> On the FROM CCM, goto the CLI of pub (or sub) and do a "show version
>>>>>>> active"; it will tell you if you have the UNREST.
>>>>>>>
>>>>>>> Thanks,
>>>>>>>
>>>>>>> Ryan
>>>>>>>
>>>>>>> > On Nov 15, 2015, at 7:55 PM, Jonathan Charles <jonvoip at gmail.com>
>>>>>>> wrote:
>>>>>>> >
>>>>>>> > Using PCD on CUCM 10.5.2.11901 got the following error:
>>>>>>> >
>>>>>>> > <image.png>
>>>>>>> >
>>>>>>> > It seems to imply I am not matching restricted vs. unrestricted...
>>>>>>> >
>>>>>>> > Any easy way to find out?
>>>>>>> >
>>>>>>> >
>>>>>>> >
>>>>>>> > Jonathan
>>>>>>> > _______________________________________________
>>>>>>> > 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
>>>>>>
>>>>>>
>>>>>
>>>>
>>>
>>> _______________________________________________
>>> cisco-voip mailing list
>>> cisco-voip at puck.nether.net
>>> https://puck.nether.net/mailman/listinfo/cisco-voip
>>>
>>>
>>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://puck.nether.net/pipermail/cisco-voip/attachments/20151117/5e364347/attachment.html>
More information about the cisco-voip
mailing list