![]() I did want to do exactly the what the upgrade guide stated, infact i had the same cop file as what you mentioned and no other cop files required due to the version 8.6.2 (1) Number of rows in a table do not match on all nodes. To determine if replication is suspect, look for the following: Suspect Replication Summary -įor table: ccmdbtemplate_cucmpub_ccm8_6_2_10000_14_1_517_pickupgrouplinemap SERVER ID STATE STATUS QUEUE CONNECTION CHANGED I cannot find the rebuild, maybe repair is the command ?Īdmin:file view activelog cm/trace/dbl/sdi/ReplicationStatus.2014_12_08_13_23_16.out He recommends to create a new VM using the new OVA and use the DRS and restore process for performing the upgrade. The 10.5 OVA, 7500 users requires 1 vCPU and 110GB for the vdisk.ĭoes anybody know if I have to run the ee_common_space_v1.1.cop.sgn to increase the space to 110GB on each vdisk (even if the total size is 160GB on 2 vdisks which is more then 110GB required on 10.5 OVA)?Ĭisco engineer said that this is not possible as well that I can not change the OS to RHEL 6 (64-bit) on the existing server/VM (ESXi 4.1 U3. The existing 8.6.2 OVA, 7500 users is using 2 vCPU and 80GB for each vdisk (total of 160GB). run the 10.5 ugrade file in following order: PUB, TFTP, SUB1, SUB2 ![]() changing the OS to RHEL 6 (64-bit) and the Network Adapter from "Flexible" to "VMXNET 3” for the VM (shut down the VM and perform the changes) I have to upgrade a virtualized CUCM cluster (PUB, SUB1, SUB2, TFTP) version 8.6.2 SU3 to version 10.5.Īs per documentation this should be a direct refresh upgrade and no need of PCD to do it.īased on the documentation the main steps of the upgrade are:
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |