cucm10.5 upgrade to cucm 14

[gushuhua]

When I upgrade CUCM which version is 10.5.2  to CUCM 14 by  Fresh Install with Data Import, it get an error.

I have checked  the destination server IP and the SFTP directory  and it's correct.  How should I troubleshoot ?

[Nithin Eluvathingal]

Can you share the screenshot or the path you mention on cucm installation and

the path on SFTP

I believe it’s just matter of SFTP path. There is specific requirement 

and if you can share the folder screenshot it will be helpful

[gushuhua]

I   installed the freeFTP  as the sftp server on windows 10.   The home directory of the user  is cisco. I  exported the cucm 10 data to the sftp server and it created an folder named cluster-192.168.31.241 automaticlly under the home directory.

[dagnaget]

We recently ran into this same error; were you able to find a solution/workaround? TIA

[gushuhua]

Just move the sftp server to linux .

[Elliot Dierksen]

It is probably an issue with the ciphers or key exchange algorithms. I use the OpenSSH server on FreeBSD and Linux, and this works for me.

in sshd_config:

KexAlgorithms +diffie-hellman-group1-sha1
KexAlgorithms +diffie-hellman-group-exchange-sha1

Ciphers +aes128-cbc
# 3DES isn't supported on newer version of DRS or in
# newer versions of OpenSSH
Ciphers +3des-cbc

Newer Ubuntu needs this:
PubkeyAcceptedAlgorithms +ssh-rsa
HostkeyAlgorithms +ssh-rsa

[gushuhua]

Yes,When I  changed the sftp server from window to linunx and it worked.

[ahmedelrayess]

@gushuhua could you please tell which Linux server you use and sftp

[CUCM-GOD]

Good day all,

The fix for this issue / error is very simple.

#1 check to make sure the IP /address is 100 % correct.

#2 The SFTP path is root + cluster-your ip add address. eg below

/cluster_10.10.1.10 that is it.

#3 if you get that error after these steps. do the following.

#1 disable NIC card from new VM

#2 power on OLD VM with old ip address 

#3 ping from your SFTP TFTP or STP to cucm VM. make sure the solorwinds FTP is working and can talk to CUCM.

#4. on your MGMT VM or database or storage ... delete old cluster-IP.address

#5 start the export from OLD CUCM VM again, and WAIT  just wait it can take up to 1 hr or more depending what size CUCM you have 

#6 once you get a full complete, then you can shut down old VM  start new VM with new NIC ip address, or old address does not matter.

#7 and import with /cluster-10.10.1.10

that will solve this error.

not sure how the tor file get corrupted, but it happens..

Things to look out for. DO NOT OPEN cluster-10.10.1.10 FILE BEFORE ITS DONE.

make sure the file size once done is not small ... aka 40m with 10 phones mine was 1.4 GB

GL all