To upgrade to Cisco Unified SIP Proxy Release 1.1.4 from an earlier release, follow these steps:

To upgrade to Cisco Unified SIP Proxy Release 1.1.4 from an earlier release, follow these steps:

+

1) Back up your CUSP config! This is important, because upgrading the code erases your configuration. Also, make sure you are in hostname(cusp)# when you copy the config out. The easiest way to back up the config is to use the following command:

1) Back up your CUSP config! This is important, because upgrading the code erases your configuration. Also, make sure you are in hostname(cusp)# when you copy the config out. The easiest way to back up the config is to use the following command:

Line 9:

Line 9:

This will allow you to specify the IP address of an FTP server to back your configuration up. We also highly recommend that you go to the FTP server and verify that your CUSP config did indeed get transfered and that you can view the file without any problems. You will be restoring from this file shortly.

This will allow you to specify the IP address of an FTP server to back your configuration up. We also highly recommend that you go to the FTP server and verify that your CUSP config did indeed get transfered and that you can view the file without any problems. You will be restoring from this file shortly.

+

2) Double check that you have performed step number 1.

2) Double check that you have performed step number 1.

+

3) There are three files you need to download from CCO for the upgrade to work. They are:

3) There are three files you need to download from CCO for the upgrade to work. They are:

-

+

* cusp-k9.nme.1.1.4.pkg

-

cusp-k9.nme.1.1.4.pkg

+

* cusp-full-k9-nme.1.1.4.prt1

-

cusp-full-k9-nme.1.1.4.prt1

+

* cusp-installer-k9.nme.1.1.4.prt1

-

cusp-installer-k9.nme.1.1.4.prt1

+

These need to be on an FTP server somewhere with an anonymous account (with any password accepted) setup. You DO NOT have the option to input a username and password when initiating the install on the CUSP CLI. When you are on the CLI of the NME and you start typing software install, you have a few different options. One of them is "upgrade". Unfortunately, "upgrade" is not a valid option for upgrading your CUSP software. The only option that is valid is "clean". The full syntax for the upgrade is "software install clean url ftp://10.0.0.1/cusp-k9.nme.1.1.4.pkg".

These need to be on an FTP server somewhere with an anonymous account (with any password accepted) setup. You DO NOT have the option to input a username and password when initiating the install on the CUSP CLI. When you are on the CLI of the NME and you start typing software install, you have a few different options. One of them is "upgrade". Unfortunately, "upgrade" is not a valid option for upgrading your CUSP software. The only option that is valid is "clean". The full syntax for the upgrade is "software install clean url ftp://10.0.0.1/cusp-k9.nme.1.1.4.pkg".

NOTE: A clean install ERASES your config. So be sure that you backed up your config before you do this.

NOTE: A clean install ERASES your config. So be sure that you backed up your config before you do this.

+

4) The NME reboots and begins the initialization wizard. Your NME config gets saved in flash, so you'll be prompted to restore that. Once it has reached the hostname> prompt, type "cusp" to go into CUSP EXEC mode, and then type in "copy ftp: config active". Here you'll specify the IP address of the FTP server used in step 1 to back your old configuration up. You'll also need to know the name of the file as it was saved to the FTP server. By default it is "<hostname>.cusp.cfg" (where <hostname? is whatever you named your CUSP NME). A reboot will take place once the file is transferred, and this completes the upgrade process.

4) The NME reboots and begins the initialization wizard. Your NME config gets saved in flash, so you'll be prompted to restore that. Once it has reached the hostname> prompt, type "cusp" to go into CUSP EXEC mode, and then type in "copy ftp: config active". Here you'll specify the IP address of the FTP server used in step 1 to back your old configuration up. You'll also need to know the name of the file as it was saved to the FTP server. By default it is "<hostname>.cusp.cfg" (where <hostname? is whatever you named your CUSP NME). A reboot will take place once the file is transferred, and this completes the upgrade process.

+

+

+

[[Category: Unified SIP Proxy]]

Revision as of 22:01, 14 October 2010

To upgrade to Cisco Unified SIP Proxy Release 1.1.4 from an earlier release, follow these steps:

1) Back up your CUSP config! This is important, because upgrading the code erases your configuration. Also, make sure you are in hostname(cusp)# when you copy the config out. The easiest way to back up the config is to use the following command:

hostname(cusp)#copy config active ftp:

This will allow you to specify the IP address of an FTP server to back your configuration up. We also highly recommend that you go to the FTP server and verify that your CUSP config did indeed get transfered and that you can view the file without any problems. You will be restoring from this file shortly.

2) Double check that you have performed step number 1.

3) There are three files you need to download from CCO for the upgrade to work. They are:

cusp-k9.nme.1.1.4.pkg

cusp-full-k9-nme.1.1.4.prt1

cusp-installer-k9.nme.1.1.4.prt1

These need to be on an FTP server somewhere with an anonymous account (with any password accepted) setup. You DO NOT have the option to input a username and password when initiating the install on the CUSP CLI. When you are on the CLI of the NME and you start typing software install, you have a few different options. One of them is "upgrade". Unfortunately, "upgrade" is not a valid option for upgrading your CUSP software. The only option that is valid is "clean". The full syntax for the upgrade is "software install clean url ftp://10.0.0.1/cusp-k9.nme.1.1.4.pkg".

NOTE: A clean install ERASES your config. So be sure that you backed up your config before you do this.

4) The NME reboots and begins the initialization wizard. Your NME config gets saved in flash, so you'll be prompted to restore that. Once it has reached the hostname> prompt, type "cusp" to go into CUSP EXEC mode, and then type in "copy ftp: config active". Here you'll specify the IP address of the FTP server used in step 1 to back your old configuration up. You'll also need to know the name of the file as it was saved to the FTP server. By default it is "<hostname>.cusp.cfg" (where <hostname? is whatever you named your CUSP NME). A reboot will take place once the file is transferred, and this completes the upgrade process.