01-23-2018 01:33 PM - edited 03-14-2019 05:53 PM
Hello all,
I'm trying to upgrade my UCCX from version 10.6 SU2 to SU3. The software options I have installed are: ciscouccx.ReportFix.10.cop and ciscouccx.VMwareTools2016V2.cop.
I'm trying this in my lab and the ISO file has a status of "Name does not match any filter pattern."
The ISO file's MD5 hash matches the one from the download site.
I tried looking for a refresh package, but couldn't locate anything.
I've tried rebooting my UCCX servers and that didn't work.
I'm redownloading the ISO despite the hashes matching.
ESXi in my lab is 6.5
Is there something I'm missing?
Solved! Go to Solution.
01-24-2018 11:29 AM - edited 01-25-2018 06:10 AM
Can you make sure that the file in SFTP has the correct extension ? From the web GUI snippet, I can see the file ending is "sgn" when it should be "sgn.iso". I believe that is why the system is not able to recognize any valid upgrade files.
01-24-2018 09:25 AM - edited 01-25-2018 06:09 AM
Are you using the "10.6.1.11003-29" for upgrade ?
01-24-2018 09:31 AM
Thank you for the response.
Yes, I am.
The re-download didn't work.
Just to see if it was my lab environment, i tested to see if my production side recognizes the ISO, and it too doesn't like it.
01-24-2018 09:44 AM
01-24-2018 09:51 AM
I didn't see any cop files that needed to be installed. The readme and Install guides didn't mention one.
The only cop files installed before the upgrade are the ones listed in the body above.
The error is in the GUI, but when I try from CLI, it doesn't even list it as an option.
There are 2 nodes
01-24-2018 10:12 AM
01-24-2018 10:47 AM - edited 01-24-2018 10:48 AM
Thanks for the detailed steps. But I can't even get that far. The ISO I downloaded appears to not be a valid upgrade ISO.
I've attached pictures of what I get through CLI and the webpage.
I verified the MD5 hash on the original I downloaded and the re-downloaded file. The integrity is fine.
Not sure what's going on unless the ISO on the download page is corrupted.
01-24-2018 11:29 AM - edited 01-25-2018 06:10 AM
Can you make sure that the file in SFTP has the correct extension ? From the web GUI snippet, I can see the file ending is "sgn" when it should be "sgn.iso". I believe that is why the system is not able to recognize any valid upgrade files.
01-24-2018 11:42 AM
Thank you for being very prompt on your replies!
I was hoping it would be that easy, but it does have .iso on the end.
Not sure why it's not showing up in the GUI.
On my windows machine, I have it set to show file extensions, and it's there. I tried to change the file name by adding "test" in the middle.
The ISO I'm using isn't for fresh installs only is it? It said for upgrades and fresh installs.
01-24-2018 11:46 AM
WAIT! I looked at the file name again, and it ended with ".sgn (1).iso"
I changed the name and its now recognizing it!
Thank you so much for helping me out!
01-24-2018 11:50 AM - edited 01-25-2018 06:12 AM
Great. See sometimes it's the easier things that we tend to overlook.
Try the upgrade now and follow the procedure that I highlighted.
Do update me how it goes.
01-25-2018 09:28 AM
It's always the easy stuff!
I'm pleased to announce that the install in the lab went well! No issues at all. DB replication is working. All datastores are up and running. All services are running. I updated CUCM as well, so I needed to do a JTAPI resync, which completed successfully. I still need to test ACD, CAD, and Supervisor, but so far I'm pretty hopeful!
Thank you for all your help!
01-25-2018 09:50 AM
Discover and save your favorite ideas. Come back to expert answers, step-by-step guides, recent topics, and more.
New here? Get started with these tips. How to use Community New member guide