Rw-rw-r- 1 admin admin 13K Jan 12 -01-12-12-18-28CCMdrfComponent.xmlTask 2: Restore Cisco Unified Communications ManagerIn this task we will restore Cisco Unified Communications Manager from the previously created system backup. Activity ProcedureComplete these steps:. From Communications Manager Administration page, go to Navigation Disaster Recovery System page. You will need to login again. From the menu, select Restore Restore Wizard. Select the Device Name. Click Next button.
![Install Install](/uploads/1/2/4/2/124214535/561585779.jpeg)
For Step 2 of the Restore page, select the backup file (there should be one backup file from the previous task; if there is no backup file, repeat task 1). Click Next button. For Step 3 of the Restore page, on Select Features select UCM, and click Next.
For Step 4 Restore page, on Select the servers to be restored for each feature, select CCM, and click Restore. Wait until restore process is finished. A reboot of the server is needed which can be accomplished in two ways. The server can be restarted through the Cisco Unified OS Administration web interface or the command line via SSH. To restart the server through web interface, use the navigation pane and access the Cisco Unified OS Administration web page. You will need to login using your credentials. From the menu, select Settings Version.
Click Restart and the Ok. To restart the server through CLI, use the SSH client (PuTTy) and initiate SSH session to the Cisco Unified Communications Manager Server. Login using your credentials. Type this command: utils system restart.
Type yesto continue. Read the warning message and wait until message for shutdown displayed.
Supports a wide range of devices with Cisco Jabber for smartphones, tablets,. See Expressway on Virtual Machine Installation Guide on the Expressway Install. The PAK contains one or many Product Identifiers (PIDs) that translate into. Addresses between Expressway-E and Expressway-C. How Does it Work? Step 6 In the Warning box, verify that you selected the correct firmware and click Install. Step 7 Check that you received a Success message. Step 8 Restart the TFTP service. Step 9 Reset the device to upgrade the device to the new firmware load. This needs to be installed on all nodes in the CUCM cluster followed by restart of TFTP service.
Wait until the Communications Manager server is up and running (Try to ping 10.1.1.10 to see when the server will be reachable. The server will take 10 to 15 minutes to come back online where the web pages are accessible).
Log back into the Cisco Unified Communications Manager administration page, and select Call Routing Route plan Report and click Find to list all dial plan patterns. The translation pattern(s) created on the previous task will not be there anymore.Activity VerificationYou have completed this task when you attain these results:. Verify that the changes done in step one are gone and the previous configuration has been restored.
Manish is spot on. It is very key to understand that there is a difference between upgrading the firmware for an existing device type and adding a new device type. When upgrading the firmware of an existing device type, you only need to install the firmware cop file on the publisher node and the TFTP nodes. The former so things like Dev Defaults get updated. The latter because the TFTP nodes access their local file repository when serving files.You have to restart the TFTP service so that the server can refresh cache.
You DO NOT need to load firmware images on cluster nodes that are not running the TFTP service. In larger clusters, it is common to have nodes designated as TFTP only or as media only (or as TFTP + Media, if you walk that line).When installing a dev pack, you typically need to update the db schema and update various web (admin/user) files (while accounting for new locales, etc.).
Since the installer touches various file system locations, db tables, etc., Cisco opts to go for a UCM reload. Since you have to install dev packs on each server, that leads to the cluster reload scenario.-Bill. Manish is spot on. It is very key to understand that there is a difference between upgrading the firmware for an existing device type and adding a new device type. When upgrading the firmware of an existing device type, you only need to install the firmware cop file on the publisher node and the TFTP nodes. The former so things like Dev Defaults get updated. The latter because the TFTP nodes access their local file repository when serving files.You have to restart the TFTP service so that the server can refresh cache.
You DO NOT need to load firmware images on cluster nodes that are not running the TFTP service. In larger clusters, it is common to have nodes designated as TFTP only or as media only (or as TFTP + Media, if you walk that line).When installing a dev pack, you typically need to update the db schema and update various web (admin/user) files (while accounting for new locales, etc.). Since the installer touches various file system locations, db tables, etc., Cisco opts to go for a UCM reload. Since you have to install dev packs on each server, that leads to the cluster reload scenario.-Bill.