The
Software Upgrade pages enable you to upgrade Emergency Responder software from
a DVD (local source) or from a network location (remote source) that the
Emergency Responder server can access. The Emergency Responder Publisher must
be upgraded first, followed by the Subscriber.
![](https://www.cisco.com/content/dam/en/us/td/i/templates/note.gif)
Note
|
Direct Refresh Upgrades from Pre-12.5.x source to Release 15 is not supported. You should first upgrade your source to Release
12.5.x or 14 and SUs and then upgrade your source to Release 15.
|
![](https://www.cisco.com/content/dam/en/us/td/i/templates/note.gif)
Note
|
Emergency Responder 15 does not support Install with Data Import.
|
![](https://www.cisco.com/content/dam/en/us/td/i/templates/note.gif)
Note
|
If your Emergency Responder publisher node is on Release 15 and the subscribers nodes are in Release 12.5.x or 14 and SUs,
the nodes in the cluster will not be authenticated. Only when the subscribers nodes are upgraded to Release 15, all the nodes
will be in the authenticated state.
|
With Emergency Responder 10.0 and later, you cannot install upgrade software on your server while the system continues to
operate. A Refresh Upgrade is required for all upgrades from Emergency Responder 10.0, 11.x, 12.0, or earlier to the most
recent version of Emergency Responder. A Refresh Upgrade is a fresh install on the inactive partition, with embedded data
migration. A Refresh Upgrade requires server downtime. This is less critical in a redundant system with both Emergency Responder
Publisher and Subscriber.
Before you begin the
upgrade, back up your system.
When you install the
upgrade software, there will be a temporary server outage while the Emergency
Responder software is installed. After you begin the upgrade, using either the
command line or graphical user interface, the data will be migrated, and the
system will automatically reboot, at which point the server outage begins. The
duration of this outage depends on your configuration and amount of data. A
notification email is sent at the start and end of Refresh Upgrade.
If an administrator makes changes during the upgrade process such as exporting data, then that data could be lost after the
upgrade.
The previous
software remains in the inactive partition until the next upgrade.
A manual switch back
can revert to the old version. If the upgrade fails, the system automatically
reverts to the previous version. Your configuration information migrates
automatically to the upgraded version in the active partition.
If for any
reason you decide to back out of the upgrade, you can restart the system to the
inactive partition that contains the older version of the software using the
switch-version option.
However, any configuration changes that you made since you upgraded the software will be lost, because the database on the
inactive partition does not get updated. If you make changes to the database after an upgrade, you must repeat those changes
after switching back to the inactive partition.
When you upgrade Emergency Responder from any older release versions to Release 14SU2 and if the Unified CM is running on
an older version lesser than Release 14SU2, use the following steps to prevent the CTI Route points from getting unregistered:
-
From the Cisco Unified CM Administration, navigate to User Management > User Setting > Application User CAPF Profile, and choose the application user for the CAPF operation.
-
Select the Instance Id registered for CAPF.
-
Select Install/Upgrade option from the Certificate Operation drop-down list. And, provide the Authentication String as configured under Phone Tracking > Cisco Unified Communications Manager > Secure Authentication String for Publisher in the Cisco Emergency Responder Administration Web Interface.
-
Ensure that the Operation Completes By field shouldn't have a past due date and save the changes.
-
Verify that all the route points (911/912/913) get registered.