|
Table Of Contents
Installing Cisco Emergency Responder 1.3(1)
Hardware and Software Prerequisites
Installing Cisco Emergency Responder 1.3(1) on a New System
Installing the Cisco ER Publisher
Installing the Cisco ER Subscriber
Upgrading from Cisco Emergency Responder 1.2(x) to Cisco Emergency Responder 1.3(1)
Configuring the Cisco Emergency Responder Cluster
Installing Cisco Emergency Responder 1.3(1)
Cisco Emergency Responder (Cisco ER) consists of three components: the Cisco ER web interface for end users and administrators, the Cisco ER server and the phone tracking engine. Although some Cisco ER settings are configured during installation, most of the configuration must be done after installation using the Cisco ER administration interface.
You can install Cisco ER 1.3(1) as a new installation using an installation CD. Or you can upgrade to Cisco ER 1.3(1) by downloading cer-fmr.1-3-1.exe from the following URL:
http://www.cisco.com/cgi-bin/tablebuild.pl/cer
or you can upgrade to Cisco ER 1.3(1) from the following installed systems:
•Cisco ER 1.2(1)
•Cisco ER 1.2(2)
•Cisco ER 1.2(3a)
Note Data migration from Cisco ER 1.1(4) to Cisco ER 1.3(1) is not supported. To upgrade from Cisco ER 1.1(4), you must first upgrade to Cisco ER 1.2(3a). After you have upgraded to Cisco ER 1.2(3), you can follow the procedure in this guide to upgrade from 1.2(3a) to 1.3(1).
To upgrade from Cisco ER 1.1(4) to 1.2(3), see: Cisco Emergency Responder Administration Guide 1.2(3) at the following url:
http://www.cisco.com/univercd/cc/td/doc/product/voice/respond/res12/res123/index.htm.
Note If a Cisco ER service release (SR) is installed on the server, you must uninstall that SR before proceeding with the upgrade. The upgrade cannot be performed with the SR in place
These topics cover the hardware and software requirements and upgrade instructions for Cisco ER:
• Hardware and Software Prerequisites
• Before You Install or Upgrade
• "Installing Cisco Emergency Responder 1.3(1) on a New System" section
• Upgrading from Cisco Emergency Responder 1.2(x) to Cisco Emergency Responder 1.3(1)
• Configuring the Cisco Emergency Responder Cluster
Hardware and Software Prerequisites
Cisco Emergency Responder (Cisco ER) requires specific hardware and software to run properly. Review the following sections before you proceed with the installation or upgrade to Cisco ER 1.3(1):
•See the "Network Hardware and Software Requirements" section to verify that you have all the hardware and software, and in the supported versions, that you must install for Cisco ER.
•See Table 1-6 to check that your MCS platform provides the Cisco ER capabilities to meet your configuration needs. (You can also use equivalent Cisco-certified servers.)
•See Table 1-9 to make sure that you have all the required license keys available before you begin the installation process.
Before You Install or Upgrade
Cisco recommends that you perform the installation or upgrade during off-peak hours. The upgrade will stop Cisco Emergency Responder services, upgrade the required services and files, and restart the Cisco ER services when complete.
Review the following information before you upgrade your system to Cisco ER 1.3(1):
•Determine and list your Cisco ER Host Name and Passwords.
–Decide on a permanent hostname for the Cisco ER server before you install Cisco ER. Changing the hostname of a Cisco ER server after installation may cause problems.
–Cisco recommends that you add the publisher hostname and the IP address to the hosts file (usually at C:\\WINNT\system32\drivers\etc\hosts) on the subscriber before you begin the Cisco ER installation or upgrade.
–The hostname for the Cisco ER 1.3(1) publisher and subscriber must not contain the underscore character (_). If you have an existing Cisco ER server with an underscore in its hostname, change the hostname of the server prior to installing Cisco ER 1.3(1).
–The local Administrator password must be the same for the Cisco ER publisher server and subscriber server. If the passwords are different, there may be problems in setting up the subscriber database. If you encounter problems with the subscriber database setup, use the Admin Utility task "Point subscriber to new publisher" to fix the problem. For more information, see the "Using the Cisco ER Admin Utility" section on page 7-30.
•Cisco ER Versions:
–Different versions of Cisco ER cannot be deployed in the same Cisco ER group. The primary and the standby Cisco ER servers must be running the same version of Cisco ER. If you are upgrading to Cisco ER 1.3(1) make sure to upgrade both Cisco ER servers to version 1.3(1). Cisco ER 1.3 server groups cannot be placed in a Cisco ER cluster with Cisco ER 1.2(x) or Cisco ER 1.1(x) server groups.
–All Cisco ER servers must be upgraded to Cisco ER 1.3(1). In a Cisco ER cluster, Cisco ER 1.3(1) server will not operate with previous versions of Cisco ER servers.
•Use the Add/Remove Program in the windows control panel to uninstall all Service Packs, Service Patches and Antivirus Services; re-install them after the upgrade:
–Uninstall all Service Packs and Service Releases before the upgrade. This will not impact your Cisco ER configuration.
–Uninstall all antivirus services, such as the Cisco-approved McAfee virus service. You can enable all antivirus services after you complete the procedures.
–If you have Cisco IDS Host Sensor Agents installed on the server, you must uninstall the following services before the upgrade: entercept Agent; entercept Watchdog; entercept Notification Manager; entercept Server.
•Caveats:
–You cannot install Cisco ER on the same system as any other Cisco IP Telephony applications, such as Cisco CallManager, Cisco Customer Response Solutions (Cisco CRS), Cisco CallManager AutoAttendant, Cisco Personal Assistant, and so on.
–You cannot install Cisco ER on a Windows domain controller.
–You cannot install or upgrade to Cisco ER 1.3(1) using Terminal Services.
–Once you upgrade your system to Cisco ER 1.3(1), Cisco ER downgrades are not supported.
–Review the release notes for Cisco ER 1.3(1) before installation:
http://www.cisco.com/univercd/cc/td/doc/product/voice/respond/index.htm
•Install the components for Cisco ER 1.3(1) in the order shown in Table 2-1.
Table 2-1 Installation Tasks
Installation Task Where to Find DocumentationCisco CallManager operating system 2000.2.7
http://www.cisco.com/univercd/cc/td/doc/product/voice/iptel_os/install/index.htm.
Note Newer servers, such as the MCS-7835-H1-IPC1, require an operating system installation kit that contains DVD media. Use the operating system upgrade only to upgrade earlier versions of the operating system to the new level (service packs, hot fixes, configuration settings, BIOS, firmware, and drivers).
Cisco CallManager
http://www.cisco.com/univercd/cc/td/doc/product/voice/c_callmg/index.htm
Cisco CallManager Backup and Restore Utility Version 4.0(9)
http://www.cisco.com/univercd/cc/td/doc/product/voice/backup/bars40/index.htm
Cisco ER 1.3(1) as a new installation
Cisco ER 1.3(1) as an upgrade
Upgrading from Cisco Emergency Responder 1.2(x) to Cisco Emergency Responder 1.3(1).
Post Cisco ER 1.3(1) upgrade tasks
• Configuring the Cisco Emergency Responder Cluster
•Enable any services such as antivirus software that you disabled before the upgrade.
Installing Cisco Emergency Responder 1.3(1) on a New System
This procedure describes how to install Cisco Emergency Responder (Cisco ER) 1.3(1)) as a new installation.
With Cisco ER 1.3(1), the Cisco ER cluster information is determined at the time of installation. Cisco ER cluster information is based on the Cisco CallManager publisher where you point your initial configuration data to be stored. You enter Cisco ER group configuration through the web interface based on publisher (primary) and subscriber (secondary) server pairs:
• Installing the Cisco ER Publisher
• Installing the Cisco ER Subscriber
Installing the Cisco ER Publisher
To install Cisco ER 1.3(1), you install the publisher (primary) first, then you install the subscriber (backup) on a separate server. You must install Cisco ER on separate servers from Cisco CallManager or any Cisco AVVID applications.
To install the publisher, perform the following steps:
Procedure
Step 1 As a local administrator, log onto the computer where you are running the Cisco ER installation program.
Step 2 Insert the Installation CD and launch the Cisco ER installation program by clicking on the installation executable file:
cer-fmr.1-3-1.exe
Step 3 Click Next to continue the installation.
The End-User License Agreement window displays.
Step 4 Read the agreement, and click Yes to accept the terms and continue. (Or, click No to cancel the installation).
The Cisco Emergency Responder server window displays.
Step 5 On the Cisco Emergency Responder server page, select Publisher.
The Service Log On Account window displays.
Step 6 At the Password field, enter a password for the CERSQLAdmin account (the user account created and used by Cisco ER) and click Next.
The Cisco Emergency Number Configuration window displays.
Step 7 Change the Emergency Number default value of 911 to the emergency number for your location and click Next.
The Cisco CallManager Server Version window displays.
Step 8 Select the Cisco CallManager version that you are running and click Next.
The Ready to Install Cisco Emergency Responder window displays.
Step 9 Click Next.
The installation of the Cisco ER publisher will take an additional 10 to 15 minutes to complete.
Step 10 After installation, you must reboot the server.
Installing the Cisco ER Subscriber
Now you install the Cisco Emergency Responder (Cisco ER) subscriber. You must install the subscriber on a separate server from the Cisco ER publisher. The subscriber server must also be separate from Cisco CallManager or Cisco AVVID applications.
Caution Be sure that you have completely installed the publisher, including the reboot, before you start to install the subscriber.
Perform the following steps.
Procedure
Step 1 As a local administrator, log onto the computer where you are running the Cisco ER installation program.
Step 2 Insert the Installation CD and launch the Cisco ER installation program by clicking on the installation executable file:
cer-fmr.1-3-1.exe
Step 3 Click Next to continue the installation.
The End-User License Agreement window displays.
Step 4 Read the agreement, and click Yes to accept the terms and continue. (Or, click No to cancel the installation.)
The Cisco Emergency Responder server window displays.
Step 5 On the Cisco Emergency Responder server page, select Subscriber and enter the following data:
a. At the Publisher Hostname, enter the name of the Cisco ER publisher.
b. At the CERSQLAdmin password on Publisher, enter the CERSQLAdmin account password on the publisher.
Cisco ER displays the Publisher Details window.
The Cisco ER installation validates the publisher Cisco ER version; reads the Cisco CallManager cluster information and the Cisco CallManager version configuration; and displays the details.
Note If the installation cannot validate the publisher, see the "Cannot Validate Publisher" section on page 7-24 in the Troubleshooting chapter.
Step 6 Verify the publisher information.
•If the publisher information is correct, click Next.
•If the information is not correct, click the Back button and make sure that the correct Cisco ER publisher server is specified. Then, click Next.
The installation of the Cisco ER subscriber will take an additional 10 to 15 minutes to complete.
Step 7 After installation, you must reboot the server.
Tip Cisco ER creates multiple files in the directory C:\CERInstall. If you need to contact Cisco Technical Support concerning installation issues, zip and send all the files under this folder to your support contact.
Upgrading from Cisco Emergency Responder 1.2(x) to Cisco Emergency Responder 1.3(1)
This procedure describes how to upgrade from Cisco Emergency Responder (Cisco ER) 1.2(1), 1.2(2), or 1.2(3a) to Cisco ER 1.3(1).
Note Be sure to uninstall all Service Patches or Service Releases such as 1.2(3)sr2 before performing the upgrade. (Use the Add/Remove Programs in the windows control panel). And read the "Before You Install or Upgrade" section.
To upgrade from Cisco ER 1.2(x) to Cisco ER 1.3(1), perform the following steps:
Procedure
Step 1 As a local administrator, log onto the computer where you are running the Cisco ER installation program and download cer.fmr.1-3-1.exe to your server from the following URL:
http://www.cisco.com/cgi-bin/tablebuild.pl/cer
Step 2 Launch the Cisco ER upgrade program by double clicking the installation executable file:
cer-fmr.1-3-1.exe
The Welcome screen displays. Then the upgrade screen displays the Cisco ER version that will be upgraded.
Step 3 Click Next to continue the installation.
The End-User License Agreement window displays.
Step 4 Read the agreement, and click Yes to accept the terms and continue. (Or, click No to cancel the installation.)
The Cisco Emergency Responder password window displays.
Step 5 On the Cisco Emergency Responder password page, enter the CERSQLAdmin password that you used to install the previous version of Cisco ER.
Note The CERSQLAdmin password must match the CERSQLAdmin password of the previous version of Cisco ER exactly; if it does not match, you will receive an error message.
The installation of the Cisco ER subscriber will take an additional 10 to 15 minutes to complete.
Step 6 After installation, you must reboot the server.
Tip Cisco ER creates multiple files in the directory C:\CERInstall. If you need to contact Cisco Technical Support concerning installation issues, zip and send all the files under this folder to your support contact.
Configuring the Cisco Emergency Responder Cluster
After you install or upgrade to Cisco Emergency Responder 1.3(1), you must configure the Cisco Emergency Responder (Cisco ER) cluster. To configure the Cisco ER cluster, perform the following procedure.
Procedure
Step 1 Identify the following:
•all the Cisco ER groups participating in the Cisco ER cluster
•one of the Cisco ER publishers as "Cluster DB Host.
•a password that will be the same across the Cluster as "Cluster password."
Step 2 Use the AdminUtility task Updated Cisco ER Cluster DB host details and enter the values from Step 1.
Step 3 Repeat steps 1 and 2 for each Cisco ER server group in the cluster.
Step 4 Restart Cisco ER services.
Posted: Fri Mar 31 18:26:04 PST 2006
All contents are Copyright © 1992--2006 Cisco Systems, Inc. All rights reserved.
Important Notices and Privacy Statement.