06-10-2015 02:52 AM - edited 03-19-2019 09:41 AM
Hi,
One of my clients have a CUSP redundant pair deployed with version 8.5.2 . Due to the leap second adjustment bug, client wants to upgrade the version to 8.5.9 where the bug is fixed.
I am unable to find an upgrade path from 8.5.2 to 8.5.9
Will we have to do a fresh install on one side and then do it on the other side?
Please help with any upgrade path available or if there is a procedure to restore the config from 8.5.2 to 8.5.9 from a backup.
Thank you for your response!
Warm Regards
Chitrangad Pathak
Solved! Go to Solution.
06-10-2015 03:55 AM
Hi Chitrangad,
You will need to do a backup of config, do a normal clean install and then restore the config.
The upgrade keyword in the install command is not supported on CUSP. There is a doc bug opened to update the documentation and remove the software install
upgrade url command as a possible way of upgrading the module.
CUSP remove "software install upgrade url" command section from guides
CSCut23494
Symptom:
Software upgrade using the "software install upgrade url" command on a Cisco Unified SIP Proxy (CUSP) module will fail with error:
ERROR: Upgrade of subsystem [Cisco Unified SIP Proxy] from [8.5.2] to [8.5.4] not allowed.
(The 'from' and 'to' version can be any version number)
Conditions:
When the command "software install upgrade url" is used to initiate the upgrade.
Workaround:
This command needs to be removed from the CUSP guides as it was never supposed to work for software upgrades on any/all versions of CUSP.
The correct way to upgrade CUSP is to first do a backup of its configuration, then do a normal clean install and then finally restore the configuration.
HTH
Manish
06-10-2015 03:56 AM
Link to the bug
https://tools.cisco.com/bugsearch/bug/CSCut23494/?reffering_site=dumpcr
06-10-2015 03:55 AM
Hi Chitrangad,
You will need to do a backup of config, do a normal clean install and then restore the config.
The upgrade keyword in the install command is not supported on CUSP. There is a doc bug opened to update the documentation and remove the software install
upgrade url command as a possible way of upgrading the module.
CUSP remove "software install upgrade url" command section from guides
CSCut23494
Symptom:
Software upgrade using the "software install upgrade url" command on a Cisco Unified SIP Proxy (CUSP) module will fail with error:
ERROR: Upgrade of subsystem [Cisco Unified SIP Proxy] from [8.5.2] to [8.5.4] not allowed.
(The 'from' and 'to' version can be any version number)
Conditions:
When the command "software install upgrade url" is used to initiate the upgrade.
Workaround:
This command needs to be removed from the CUSP guides as it was never supposed to work for software upgrades on any/all versions of CUSP.
The correct way to upgrade CUSP is to first do a backup of its configuration, then do a normal clean install and then finally restore the configuration.
HTH
Manish
06-10-2015 03:56 AM
Link to the bug
https://tools.cisco.com/bugsearch/bug/CSCut23494/?reffering_site=dumpcr
06-10-2015 04:03 AM
Thanks Manish for the help. I was looking for some documentation of the sort you provided to go back to the client.
Warm Regards
06-10-2015 04:12 AM
Yes, supporting official documentation like a bug helps.
Manish
06-22-2015 07:19 AM
Hi Manish,
So, it looks like it will be same path for doing an upgrade from CUSP 8.5.5 to 8.5.9 as well. Correct?
1. Backup of configuration
2. Do clean install of 8.5.9
3. Restore the configuration.
I think quick fall-back option to 8.5.5 won't be available in case there is an issue.
Regards,
Amarjeet
06-22-2015 07:43 AM
That is correct Amar.
Manish
07-08-2015 09:47 AM
Hello Everyone,
We were able to upgrade from CUSP 8.5.5 to 8.5.9 with some hiccups.. Here's what worked for us. This is just to update everyone about the upgrade steps and the issues faced.
Note: This is based on personal experiences. So, this is not authenticated by Cisco. You can add or suggest any improvements to the procedure.
Step 1. Backup of configuration from CLI and GUI:
CLI:
CUSP2(cusp)# show configuration active verbose
GUI:
Take the backup of full data and configuration from GUI to destination backup device as well.
Step 2. You might want to stop all the incoming traffic to the current CUSP to avoid the production impact.
Shut down the respective dial-peer on each gateway which point to this CUSP . If there are multiple CUSP servers, you can edit dial-peer priority to route all the traffic to the other CUSP.
Note: In our case, we had redundancy option available. So, we were able to complete the upgrade without impacting any calls going to Contact centre.
Step 3: On the CUSP which is under maintenance, Start a clean install of 8.5.9 by calling .pkg file available on FTP server. It may take 15-20 minutes to complete the installation. Once complete, it gives you an option to "restore saved configuration". It restores the basic configuration for example the hostname, users etc. So, you can select this option. Then create an admin account.
Step 4. Restore the detailed configuration(server groups, triggers etc):
Now we have the basic configuration and the CUSP has been upgraded to latest version. The next question is to restore the detailed configuration. Two methods available:
CLI >> Little complex and prone to mistakes when we copy paste detailed configuration.
GUI >> easy way but this method runs into a known defect where the indexing gets overwritten due to upgrade and the CUSP is not able to find a backup files on destination folder(at FTP).
Once you are done through this, it's just a matter of seconds to fix the indexing and restore old configuration(8.5.5 in our case). So, GUI way still works.
Step 5. The restore process will ask for reload of CUSP module. Once its back, give it about 5 minutes and every thing should be back. Then do a commit and WR to make sure that you are saving the configuration.
Step 6. You can check the restore history and it should display "success" to your last restore.
Step7:. Then you can do basic and detailed config backup from CLI as done in step 1 and match it using any notepad compare software(a good one is "CompareIT". ).
Step 8: Don't forget to re-configure dial-peers to send the traffic to newly updated CUSP server. You can take some logs to make sure the traffic is routing correctly. Dashboard itself gives good indication of "calls routed" and "calls failed" etc.
Step 9. Repeat same steps for other CUSP server.
Note: The only drawback of CUSP upgrade is , that the upgrade command doesn't work and the quick fall-back option to old version(8.5.5) won't be available in case there is an issue.
Hope this helps,
Amarjeet
07-08-2015 11:39 PM
Hi Amarjeet,
This is very valuable information that you have shared. I have a question though. Did you guys need to re install the licenses as well or were they taken by CUSP from Backup? Ideally we should, but since you did not mention that here so got curios.
Also when you say that indexing needed to be fixed, what exactly do you mean?
Thanks for your response.
Regards
Chitrangad Pathak
07-09-2015 04:49 PM
Hello Chitrangad,
We did not need to restore the licenses because when we ordered CUSP module, the licenses were pre-installed in the flash memory. Re-installing the CUSP did not any harm to the licenses. Moreover, the configuration was restored and remained exactly same for 8.5.9.
As per below guide:
http://www.cisco.com/c/en/us/td/docs/voice_ip_comm/cusp/rel8_5/install/cusp_install/licensing.html#wpxref30903
You have two choices for installing and activating the Cisco Unified SIP Proxy software:
•If you ordered a new module with Cisco Unified SIP Proxy Release 8.5 included, it is shipped with the Cisco Unified SIP Proxy image and the corresponding licenses preinstalled for the packages and features that you specified. You do not need to activate or register the software prior to use. The module stores the software license file on the flash memory. You do not need to do anything.
Coming back to your question regarding indexing, below is mentioned on the defect:
Workaround:
If the customer has the previous backup file on the ftp server, they can restore by manipulating the file name on the FTP server.
Steps to work-around
clean install on cusp
run backup so backup id 1 exists in backup DB and FTP server
rename backup id 1 to old or something else
rename previous cusp backup to _1 on ftp server
restore previous config/data files to cusp
Hope that helps
Amarjeet
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