Cisco Emergency Responder Administration Guide 8.5
Chapter 2: Installing Cisco Emergency Responder 8.5
Downloads: This chapterpdf (PDF - 494.0KB) The complete bookPDF (PDF - 12.58MB) | Feedback

Installing Cisco Emergency Responder 8.5

Table Of Contents

Installing Cisco Emergency Responder 8.5

Hardware and Software Prerequisites

Before You Install or Upgrade

Installing and Migrating to Cisco Emergency Responder on the Cisco UCS Server

System Requirements

Installing Cisco Emergency Responder on the Cisco UCS Server

Configuration Checklist for Installing and Configuring the Server

Preparing To Install

Configuring RAID

Installing vSphere Client

Aligning the Datastore Used for VMs

Creating Virtual Machines

Downloading Virtual Machine Templates (OVA Templates)

Installing Cisco Emergency Responder On a VM

Cisco Emergency Responder on the Cisco UCS Server Licensing

Customer Impact from New Licensing Procedures

Obtaining New Licenses

Supported Virtual Machine Configurations and Licensing

Migrating To Cisco Emergency Responder on the Cisco UCS Server

VMware Support

Performing Daily Operations on Cisco Emergency Responder on the Cisco UCS Server

Monitoring Hardware from the VM

Monitoring from CIMC

Monitoring from vSphere Client and vCenter

Related Documentation

Installing Cisco Emergency Responder 8.5 on a New System

Installing the Cisco Emergency Responder Publisher

Installing the Cisco Emergency Responder Subscriber

Upgrading to CER 8.5


Installing Cisco Emergency Responder 8.5


Cisco ER is distributed on an installation DVD that contains everything that is required to install Cisco ER 8.5, including the Cisco Unified Communications Operating System software.

You can upgrade to Cisco ER 8.5 from Cisco ER 7.1 or Cisco ER 8.0. You cannot directly upgrade to Cisco ER 8.5 from other versions of Cisco ER (i.e Cisco ER 1.x, Cisco ER 2.x and Cisco ER 7.0.)

These topics cover the hardware and software requirements and upgrade instructions for Cisco ER:

Hardware and Software Prerequisites

Installing and Migrating to Cisco Emergency Responder on the Cisco UCS Server

Installing Cisco Emergency Responder 8.5 on a New System

Upgrading to CER 8.5

Hardware and Software Prerequisites

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 8.5:

See the Release Notes for Cisco Emergency Responder 8.5 to verify that you have all the hardware and software, and in the supported versions, that you must install for Cisco ER and to check that your Cisco MCS Unified Communications Manager Appliance platform provides the Cisco ER capabilities to meet your configuration needs. (You can also use equivalent Cisco-certified servers.)

See the "Determining Your License Requirements" section to make sure that you have all the required license keys available before you begin the installation process.

Before You Install or Upgrade

The Cisco ER 8.5 installation process installs both the platform software and the Cisco ER 8.5 software. During the installation, you will be prompted to enter information needed by the system to complete the installation.


Note Cisco recommends that you perform the installation or upgrade during off-peak hours. The installation/upgrade procedure completely reformats the hard disk, so Cisco ER 8.5 will be unavailable for the duration of the installation or upgrade.


Review the following information before you install or upgrade your system to Cisco ER 8.5:

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 8.5, make sure to upgrade both Cisco ER servers to version 8.5.


Note Cisco ER 8.5 supports interoperability between two server groups in a cluster running different versions of Cisco ER. One server group in a cluster may be running Cisco ER 8.5 while another server group in the cluster is running Cisco ER 1.3, Cisco ER 2.0.x, Cisco ER 7.x and Cisco ER 8.0. However, Cisco ER 8.5 will not interoperate with versions earlier than Cisco ER 1.3.


Determine and list your Cisco ER hostname and passwords.

Decide on a permanent hostname, user interface administrator name and password for the
Cisco ER server before you install Cisco ER. Changing the hostname of a Cisco ER server after installation may cause problems.

The hostname for the Cisco ER 8.5 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 8.5.

Decide on a password for Cicso ER administrative user.


Note The Cisco ER administrative users password must be at least six characters long and can contain alphanumeric characters, hyphens, and underscores. It must start with an alphanumeric character.


Ethernet NIC speed and duplex mode:

Decide if you want to enable autonegotiation of Ethernet NIC speed and duplex

If yes, you don't need any additional information

If no, determine what Ethernet NIC speed and duplex mode you will use

DHCP Configuration

Decide if you want to use the Dynamic Host Configuration Protocol (DHCP) to allocate IP addresses

If yes, you don't need any additional information

If no, you will need to know the hostname, IP address, IP mask, and gateway address to enter for the Static Network Configuration

NTP Client information

The system will ask if you want to set up external Network Time Protocol (NTP) servers. Cisco recommends that you use external NTP servers to ensure that the system time is accurate.

If you decide to use external NTP servers, you will need to enter the IP address or hostname of the servers.

If you do not choose to use external NTP servers, you will need to enter the system date and time clock information manually.


Note Use of NTP server is mandatory when installing Cisco ER 8.5 on UCS servers.


Decide on a Database Access Security password

The system requires a database access security password to allow the nodes in a servergroup to communicate. The password is shared with all nodes in the servergroup.

The password must be at least six characters long and can contain alphanumeric characters, hyphens, and underscores. It must start with an alphanumeric character.

SMTP Host Configuration (optional)

Decide if you want to use an SMTP host.

If yes, determine the hostname or IP address of the SMTP host.

Caveats:

Review the release notes for Cisco ER 8.5 before installation:

http://www.cisco.com/en/US/products/sw/voicesw/ps842/prod_release_notes_list.html

Install the components for Cisco ER 8.5 in the order shown in Table 2-1.

Table 2-1 Installation Tasks 

Installation Task
For More Information

Install Cisco Unified Communications Manager

http://www.cisco.com/en/US/products/sw/voicesw/ps556/tsd_products_support_series_home.html

Install Cisco ER 8.5 as a new installation

Installing Cisco Emergency Responder 8.5 on a New System


Installing and Migrating to Cisco Emergency Responder on the Cisco UCS Server

This following sections describe the changes for installation, upgrade, and migration in Cisco Emergency Responde on the Cisco UCS Server:

System Requirements

Installing Cisco Emergency Responder on the Cisco UCS Server

Cisco Emergency Responder on the Cisco UCS Server Licensing

Migrating To Cisco Emergency Responder on the Cisco UCS Server

VMware Support

Performing Daily Operations on Cisco Emergency Responder on the Cisco UCS Server

System Requirements

To run Cisco Emergency Responder on the Cisco UCS Server, your system must meet the requirements listed in Table 2-2.

Table 2-2 System Requirements

System Parameter
System Parameter options

Supported Virtual Machine Configuration

Refer to the documentation at

http://www.cisco.com/go/uc-virtualized

IOPS per virtual machine (VM)

Refer to the documentation at

http://www.cisco.com/go/uc-virtualized

VMware version

ESXi 4.0 Update 1


Note Ensure that you use ESXi, rather than ESX, to run Cisco Emergency Responder on the Cisco UCS Server. However, the server can be part of a VMware vCenter that includes ESX hosts.


VMware—vMotion

No


Note Cisco does not support vMotion on a VM that is running. However, Cisco does support powering-down a VM, then rebooting the VM on a different rack server. This may be helpful if you want to put a rack server into maintenance mode.


VMware—Site Recovery Manager

Yes

VMware—High Availability

Yes

VMware—Data Recovery (VDR)

Yes

All other unlisted VMware features

Not supported


To operate Cisco Emergency Responder on the Cisco UCS Server successfully, you should have the experience and skills to manage a host server running VMware ESXi. If you do not have this experience and want to obtain the required information quickly, consider using VMware GO, a Web-based application that facilitates VMware.


Note Even if you use VMware GO, you still need to use the supported VMware configuration on Cisco Emergency Responder on the Cisco UCS Server, which are documented at both http://www.cisco.com/go/swonly and http://www.cisco.com/go/uc-virtualized.


Installing Cisco Emergency Responder on the Cisco UCS Server

This following sections describe how to perform a fresh installation of a Cisco Emergency Responder on the Cisco UCS server:

Configuration Checklist for Installing and Configuring the Server

Preparing To Install

Configuring RAID

Installing vSphere Client

Aligning the Datastore Used for VMs

Creating Virtual Machines

Downloading Virtual Machine Templates (OVA Templates)

Installing Cisco Emergency Responder On a VM

Configuration Checklist for Installing and Configuring the Server

Table 2-3provides a checklist of the major steps required to install and configure Cisco Emergency Responder on the Cisco UCS Server.

Table 2-3 Configuration Checklist for Installing and Configuring the Server

 
Configuration Step
Related Documentation

Step 1

Prepare to install the server.

Preparing To Install

Step 2

Physically install and connect the server.

Step 3

Power on the server and Configure Cisco Integrated Management Controller (CIMC) for remote management.

Step 4

If you purchased the UCS server separately, configure the RAID settings to the following specification:

The first 2 drives are configured as a RAID 1 (mirrored) drive. This drive is for ESXi installation.

The next 4 drives are configured as a RAID 5 drive. This drive is for VMs.


Note Number of drives may be different in diferent version of UCS servers.


Configuring RAID

Step 5

If you purchased the UCS server separately, configure the BIOS to the following specification:

Disable Quiet Mode

Enable Enhanced SATA for CDROM access

Configure the following boot order:

SATA5:Optiarc DVD first

PCI Raid Adapter second

Step 6

Install and configure VMware EXSi 4.0.0 Update 1 on the smaller of the two available disks (approximately 130 GB).

VMware ESXi documentation

Step 7

Install vSphere Client.

Installing vSphere Client

vSphere Client documentation

Step 8

Align the datastores for the VMs.

Aligning the Datastore Used for VMs

Step 9

If you use 802.1q trunking, set the MTU size to 1472.

Step 10

Install and configure a virtual machine (VM).

Creating Virtual Machines

Downloading Virtual Machine Templates (OVA Templates)

Step 11

Install Cisco Emergency Responder on the VM.

Installing Cisco Emergency Responder On a VM


Preparing To Install

This section describes how to prepare to install a Cisco Emergency Responder on the Cisco UCS server in a standalone configuration, meaning that it is not in a datacenter.

You should allocate the following resources before installation:

Space in a rack to receive a 2 RU UCS server

Ethernet ports on a switch close to the UCS server:

One port for the CIMC

Two ports for the LAN on motherboard (LOM) NICs

An IP address for the CIMC management port

An IP address for the virtual host. This is the UCS server's IP address and is used by ESXi.

A hostname, and optionally configure DNS for the virtual host's hostname

IP addresses for the VMs

Configuring RAID

If you purchased the UCS server separately, configure the RAID settings to the following specifications:

The first 2 drives are configured as a RAID 1 (mirrored) drive. This drive is for ESXi installation.

The next 4 drives are configured as a RAID 5 drive. This drive is for VMs.


Note Number of drives may be different in diferent version of UCS servers.


Follow this procedure to perform this task:


Step 1 During server bootup, press Ctrl+Y to enter the preboot CLI.

Step 2 Enter the following commands to determine the current RAID configuration:

-ldinfo -l0 -a0

-ldinfo -l1 -a0

The required configuration is two drives in a RAID 1 array for logical drive 0, and four drives in a RAID

5 array for Logical drive 1. If the RAID configuration is wrong, continue with this procedure.


Note Do not continue with this procedure if RAID is configured correctly.


Step 3 Enter the command -cfgclr -a0 to clear the RAID configuration.


Caution Clearing the RAID configuration deletes all data on the hard drives.

Step 4 Enter the following commands to configure RAID:

-cfgldadd -r1 [252:0, 252:1] -a0

-cfgldadd -r5 [252:2, 252:3, 252:4, 252:5] -a0

If the hard drives did not have a RAID configuration previously, you are done configuring RAID. If the

hard drives had a RAID configuration before, continue with this procedure.

Step 5 Enter the following commands to initialize the logical volumes.

-ldinit -start -full -l0 -a0 (l0 is the letter l and the number 0, not the number 10)

-ldinit -start -full -l1 -a0 (l1 is the letter l and the number 1, not the number 11)

This clears data on the drives and initializes the new array.

Step 6 Allow these commands to finish running before exiting the Preboot CLI. Enter the following commands

to display the progress of the commands:

-ldinit -showprog -l0 -a0

-ldinit -showprog -l1 -a0

When both commands report that no initialization is running, it is safe to quit the Preboot CLI.

Step 7 After configuring the two logical volumes, you can exit the Preboot CLI by entering q.

Installing vSphere Client

When the virtual host is available on the network, you can browse to its IP address to bring up a web-based interface. The vSphere Client is Windows-based, so the download and install must be performed from a Windows PC.

Once the vSphere Client is installed, you can run it and log into the virtual host using the virtual host's name or IP address, the root login ID, and the password you configured.

You can join the host to a vCenter if you want to manage it through vCenter.

Aligning the Datastore Used for VMs

When you install VMWare ESXi, the second logical volume is automatically imported unaligned. VMs have better disk performance when all partitions (physical, ESXi and VM) start on the same boundary.

This prevents disk blocks being fragmented across the different boundaries.

To ensure that the ESXi partition used for VMs will be aligned, you should delete the unaligned datastore (the larger disk partition---407 GB), then recreate the datastore using vSphere client.

Creating Virtual Machines

Cisco provides a VM template for you to download and transfer to your Virtual Host. Use this template to create the VM for Cisco Emergency Responder on the Cisco UCS Server installation.

Before you deploy the template and create the VM, you should have a hostname and IP address allocated for the new VM.

Follow these steps to create a VM and prepare to install Cisco Emergency Responder on the Cisco UCS Server:


Step 1 Download the VM template for your application.

See the Downloading Virtual Machine Templates (OVA Templates) for more information.

Step 2 Upload the template to a datastore on the UCS server.

It is recommended to use the smaller datastore (with ESXi installed on it) for this.

Step 3 Make this template available to the UCS server.

Step 4 Deploy the template file using vSphere Client. Enter the following information for the new VM:

hostname

datastore---Select a datastore which have enough resource

Step 5 Complete creating the VM.

At this point a new VM has been created with the correct amount of RAM, number of CPUs, size and number of disks for the intended application.

Step 6 Install Cisco Emergency Responder on the Cisco UCS Server on the VM.

See the Installing Cisco Emergency Responder On a VM for more information.

Downloading Virtual Machine Templates (OVA Templates)

The configuration of a Cisco Emergency Responder, virtual machine must match a supported virtual machine template.

Perform the following procedure to obtain the virtual machine template for Cisco Emergency Responder on the Cisco UCS Server:


Step 1 Select this URL in your browser:

http://tools.cisco.com/support/downloads/go/Redirect.x?mdfid=278875240

Step 2 If your browser prompts you to do so, type your Cisco.com User Name: and Password: in the text boxes, then click the Log In button.

Step 3 Choose IP Telephony > Call Control > Cisco Unified Communications Manager (CallManager) > Cisco Unified Communications Manager Version 8.0.

Step 4 Click the Unified Communications Manager Virtual Machine Templates link.

Step 5 In the Latest Releases folder, click the 1.0(1) link.

Step 6 Click the Download Now button. Follow the prompts and provide the required information to download the software.

Step 7 When the Download Cart window displays, click the Readme link to view the virtual machine template's release information.

Installing Cisco Emergency Responder On a VM

Follow this procedure to install Cisco Emergency Responder on a new VM:


Step 1 In vSphere Client, edit the VM to force entry into BIOS setup the next time the VM reboots.

Step 2 Make the CER installation media available to the VM DVD-ROM drive.

Step 3 Power on the VM, then in BIOS setup, promote CD ROM to boot before the hard drive.

Step 4 Complete booting the VM.

The Cisco Emergency Responder installation program starts. For information about performing the installation, see the document Installing Cisco Emergency Responder.

Cisco Emergency Responder on the Cisco UCS Server Licensing

The following sections describe licensing for Cisco Emergency Responder on the Cisco UCS Server:

Customer Impact from New Licensing Procedures

Supported Virtual Machine Configurations and Licensing

Customer Impact from New Licensing Procedures

Cisco Emergency Responder on the Cisco UCS Server uses a different licensing model than Cisco Emergency Responder on an MCS server. The MAC address of the NIC card is no longer used to associate the license to the server.

Instead, the license gets associated to a license MAC, which is a 12 digit HEX value created by hashing

the following parameters that you configure on the server:

Time zone

NTP server 1 (or "none")

NIC speed (or "auto")

Hostname

IP Address (or "dhcp")

IP Mask (or "dhcp")

Gateway Address (or "dhcp")

Primary DNS (or "dhcp")

SMTP server (or "none")

Certificate Information (Organization, Unit, Location, State, Country)

The ways to obtain the license MAC are as follows:

After installation, navigate to Show > Network in Cisco Emergency Responder OS Administration web page

After installation, use the CLI command show status.

Obtaining New Licenses

The process to redeem a Product Activation Key (PAK) for licenses at https://tools.cisco.com/SWIFT/Licensing/PrivateRegistrationServlet is changed for a license MAC. When redeeming a PAK for a license MAC at this URL, you get prompted to select the type of license that you want to obtain:

A physical MAC address — this is used when Cisco Emergency Responder will be installed on an MCS server.

A license MAC address — this is used when Cisco Emergency Responder will be installed on the Cisco UCS Servers.

After you make this selection, the generation and installation of the license file follows the same process.

Obtaining Rehosted Licenses When You Change License MAC Parameters

When you change any of the parameters that create the license MAC, the license that you obtained with it becomes invalid. You must request a re-hosting of the license to obtain a valid license. The old license continues to work for a 30-day grace period.

To rehost your licenses, you must open a case with the licensing team. Contact the licensing team at licensing@cisco.com.

Supported Virtual Machine Configurations and Licensing

The virtual machine configuration for running Cisco Emergency Responder on the Cisco UCS Server, the Vmware server must match the specifications described in the System Requirements to get support from Cisco.

While Cisco Emergency Responder can be installed and licensed in other virtual machine configurations, Cisco does not support these configurations.

Migrating To Cisco Emergency Responder on the Cisco UCS Server

Migrating from a Media Convergence Server (MCS server) to a Cisco Emergency Responder on the Cisco UCS Server follows a procedure that is very similar to replacing server hardware.

Table 2-4 provides an overview of the migration process and references to other pertinent documentation.

Table 2-4 Migrating to Cisco Emergency Responder on Cisco UCS Server Process Overview

 
Configuration Steps
Related Procedure and Topics

Step 12

Upgrade the MCS server to Cisco Emergency Responder 8.5.

Refer to Cisco Emergency Responder Admin Guide Release 8.5.

Step 13

If the CER VM will use a different IP address or hostname than the MCS server, change the IP address and hostname of the MCS server to the values that the CER VM will use. This is required for DRS backup and restore to work.

Refer to Cisco Emergency Responder Admin Guide Release 8.5.

Step 14

Perform a DRS backup on the MCS server.

Refer to Cisco Emergency Responder Admin Guide Release 8.5.

Step 15

Create the virtual machine (VM) on the Cisco UCS server that will be used as the replacement for the MCS node.

Installing Cisco Emergency Responder on the Cisco UCS Server

Step 16

Install Cisco Emergency Responder 8.5 on the Cisco UCS server.

Installing Cisco Emergency Responder on the Cisco UCS Server.

Step 17

Perform a DRS restore to restore the data backed up from the MCS server to the Cisco UCS server.

Refer to Cisco Emergency Responder Admin Guide Release 8.5.

Step 18

Upload the new licenses to the Cisco Emergency Responder on the Cisco UCS server.

Refer to Cisco Emergency Responder Admin Guide Release 8.5.


VMware Support

Consider the following, when using Cisco Emergency Responder on the Cisco UCS Server:

Install, upgrade, and recovery procedures now use "soft media" such as ISO or FLP (virtual floppy) if the server does not have a DVD drive.

USB tape backup is not supported.

NIC teaming is configured at the VMware virtual switch.

Hardware SNMP and syslog move to VMware and UCS Manager.

Install logs are written only to the virtual serial port.

Unattended installs use virtual floppy instead of USB.

Basic UPS Integration is not supported.

Boot order is controlled by the BIOS of the VMware VM.

Hardware BIOS, firmware, and drivers must be the required level and configured for compatibility with Cisco Emergency Responder supported VMware product and version.

For more information on the UCS C series server, go to the following URL:

http://www.cisco.com/en/US/docs/unified_computing/ucs/c/sw/gui/config/guide/1.1.1/b_Cisco_UCS_C-Series_Servers_Integrated_Management_Controller_Configuration_Guide_1_1_1.html

To view the list of product installation and configuration guides for Cisco UCS C-Series Integrated Management Controller, go to the following URL:

http://www.cisco.com/en/US/products/ps10739/products_installation_and_configuration_guides_list.html

To view the list of product installation and configuration guides for Cisco UCS Manager, go to following URL:

http://www.cisco.com/en/US/products/ps10281/products_installation_and_configuration_guides_list.html

Performing Daily Operations on Cisco Emergency Responder on the Cisco UCS Server

Daily operations for Cisco Emergency Responder on the Cisco UCS Server software applications are identical to when the application is installed on an MCS server.

There are some differences in hardware management and monitoring, because Cisco Emergency Responder on the Cisco UCS Server operates in a virtual environment. The following sections describe how to perform these tasks:

Monitoring Hardware from the VM

Monitoring from CIMC

Monitoring from vSphere Client and vCenter

Monitoring Hardware from the VM

Applications running in a VM have no ability to monitor the physical hardware. Any hardware monitoring must be done from the CIMC, ESXi plugins, vCenter, or by physical inspection (for flashing LEDs, etc.).

Monitoring from CIMC

The CIMC provides the following hardware monitoring:

An overview of CPU, memory and power supply health

An overview of hardware inventory, including CPUs, memory, power supplies and storage

Monitoring of sensors for power supplies, fans, temperature and voltage

A system event log that contains BIOS and sensor entries

Monitoring from vSphere Client and vCenter

The vSphere Client provides the following monitoring features:

When you are logged into vCenter, the vSphere Client displays hardware and system alarms defined on the Alarms tab.

VM resource usage displays on the Virtual Machines tab, and on the Performance tab for each VM.

Host performance and resource usage display on the Performance tab for the Host.

When ESXi is used standalone (without vCenter), hardware status and resource usage are available, but alarming is not possible.

Related Documentation

The UCS RAID Controller SMI-S Reference Guide, which describes Storage Management Initiative Specification (SMI-S) support in the Cisco UCS Servers, is available at the following URL:

http://www.cisco.com/en/US/docs/unified_computing/ucs/sw/utilities/raid/reference/guide/ucs_raid_smis_reference.html

Installing Cisco Emergency Responder 8.5 on a New System

This procedure describes how to install Cisco ER 8.5 as a new installation.

You enter Cisco ER group configuration through the Cisco ER Administration web interface based on Publisher (primary) and Subscriber (secondary) server pairs as described in the following topics:

Installing the Cisco Emergency Responder Publisher

Installing the Cisco Emergency Responder Subscriber

Installing the Cisco Emergency Responder Publisher

To install Cisco ER 8.5, 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 Unified Communications Manager or any Cisco Unified Communications applications.

Allow approximately 1 hour to perform a new installation.

To install the Publisher, follow these steps:

Procedure


Step 1 Insert the Cisco ER 8.5 Installation DVD.

If the system finds the DVD, you are asked if you want to perform a media check prior to installation to determine if there are any problems with the DVD. The system displays the checksum of the DVD and instructs you to verify this checksum on the Cisco ER 8.5 website.

At the bottom of the screen you will see instructions for moving between elements and for selecting elements, as follows:

Use the Tab key to advance to the next element

Use the Alt-Tab key combination to return to the previous element

Use the Space bar to select a highlighted element

If you choose to perform the media check, the system performs the media check and displays the results.

If the result of the media check is PASS, click OK. The system install begins the installation. Skip to Step 2.

If the result of the media check is FAIL, obtain a new installation DVD from Cisco Systems.

Step 2 The Cisco Unified Communications system installer starts. The Product Deployment Selection screen displays a message saying the Cisco Emergency Responder product suite will be installed. Click OK to continue.

Step 3 The Proceed with Install page displays the current software version on the hard drive (if any) and the software version on the installation DVD.

If you are performing a fresh installation, there will be no software on the hard drive and the system asks if you want to proceed with the installation. Click Yes to proceed.

If you are performing an upgrade, the system displays the current software version and asks it you want to overwrite the hard drive. Click Yes to proceed.

If you click Yes, the system continues with the installation and the Platform Configuration Wizard appears.

If you click No, the installation is terminated.

Step 4 On the Platform Configuration Wizard page, click Proceed to continue with the platform installation. The Import Windows Data page appears. Skip to Step 5.

If you click Skip, the system will install both the platform and Cisco ER software without prompting you to provide any information during the installation. Once the installation is completed and the system reboots, you will be prompted to enter the required configuration details.

Step 5 The Import Windows Data page prompts you to import data from a Windows version of Cisco ER. This page does not apply to fresh installations or to upgrades from earlier Linux-based versions of Cisco ER. Click No to proceed with the fresh installation. The Basic Install page appears.

Step 6 Click Continue to proceed. The Timezone Configuration page appears.

Step 7 Choose the correct timezone to use from the list provided.

Use the following keys to move between elements on the Timezone Configuration page:

Arrow Up or Arrow Down to select a timezone from the list

Tab to move to another field

After selecting the correct timezone, click OK. The Auto Negotiation Configuration page appears.

Step 8 Click Yes to enable autonegotiation of the Ethernet NIC speed and duplex mode. The DHCP Configuration page appears. If you click Yes, skip to Step 11.

If you click No, the NIC Speed and Duplex Configuration page appears.

Step 9 On the NIC Speed and Duplex Configuration page, do the following:

a. Select the NIC Speed. The available options are 10 Megabit, 100 Megabit, or 1000 Megabit.

b. Select the NIC Duplex setting. The available options are Full or Half.

c. Click OK. The DHCP Configuration page appears.

Step 10 On the MTU Configuration page, you can set the maximum transmission unit (MTU) that can be sent in a network as follows:

Click Yes if you want to configure a a MTU value of less than 1500 bytes.

Click No to use the default MTU value of 1500 bytes.

Step 11 Click Yes if you want to use Dynamic Host Configuration Protocol (DHCP). The Administration Login Configuration page appears. Skip to Step 15.

If you click No, the Static Network Configuration page appears.

Step 12 If you chose not to use DHCP, enter the following information on the Static Network Configuration page:

Host Name

IP Address

IP Mask

Gateway (GW) Address

Click OK. The DNS Client Configuration page appears.

Step 13 On the DNS Client Configuration page, you are asked if you want to configure the Domain Name System (DNS) client.


Note Click the Help button for details on configuring DNS.


If you select Yes, a second DNS Client Configuration page appears.

If you select No, the Administration Login Configuration page appears. Skip to Step 15.

Step 14 On the second DNS Client Configuration page, you are prompted to enter the following information:

Primary

Secondary DNS (optional)

Domain

Click OK. The Administration Login Configuration page appears.

Step 15 On the Administration Login Configuration page, enter an ID and password for the Administrator account. This password is used to access the CLI and the Cisco Unified OS Administration and Disaster Recovery System (DRS) websites. Click Help to display guidelines for creating this password.

When you have finished, click OK. The Certificate Information page appears.

Step 16 Enter the following information on the Certificate Information page:

Organization

Unit

Location

State

Country (select from the scroll-down menu).

Click OK. The Publisher Configuration page appears.

Step 17 Based on the type of installation you are performing, do one of the following:

If the server you are configuring is the Publisher in the server group, click Yes. The Network Time Protocol Client Configuration page appears. Proceed to Step 18.

If the server you are installing is not the Publisher in the server group, you must first configure this server on the Publisher before you can proceed. Also, this server must have network access to the Publisher, which must be in service for the installation to complete successfully. Click No only if you are configuring the Subscriber. See the "Installing the Cisco Emergency Responder Subscriber" section for information on installing the Subscriber.

Step 18 On the Network Time Protocol Client Configuration page, you are asked if you want to set up external Network Time Protocol (NTP) servers.


Note Cisco strongly recommends that you use external NTP servers to ensure that the system time is kept accurate.



Caution For CER install on UCS servers, it is mandatory to configure NTP server.

If you click Yes, the system displays a second Network Time Protocol Client Configuration page. In the fields provided, enter the IP address or hostname of the external NTP servers, then click OK. The Database Access Security Configuration page displays. Skip to Step 19.

If you click No, the Hardware Clock Configuration page appears. Enter the following information:

Year [yyyy]

Month [mm]

Day [dd]

Hour [hh]

Minute [mm]

Second [ss]

When you have finished entering this information, click OK. The Database Access Security Configuration page appears.

Step 19 On the Database Access Security Configuration page, enter the security password and then confirm the password in the fields provided.


Note The security password must be at least six characters long and can contain alphanumeric characters, hyphens, and underscores. It must start with an alphanumeric character. The security password is used for secure communications between Cisco ER server groups when performing installation/upgrade, DRS backup or restore, and "Point to a new Publisher" operations.


Click Help to display guidelines. When you have finished, click OK. The SMTP Host Configuration page appears.

Step 20 You are asked if you want to configure a Simple Mail Transport Protocol (SMTP) host. This step is optional.

If you click Yes, a second SMTP Host Configuration page appears. Click Help for guidelines, then enter the SMTP hostname or IP address in the field provided. When you are finished, click OK. The Platform Configuration Confirmation page appears.

If you click No, the Platform Configuration Confirmation page appears.

Step 21 On the Platform Configuration Confirmation page, do one of the following:

Select OK to save the platform configuration information and continue with the installation. The Cisco Emergency Responder Configuration page appears.


Note Once you select OK, you will not be able to modify the platform configuration information.


Select Back if you want to return to the previous page to make modifications. Continue to select Back to scroll through each platform configuration page.

Select Cancel to cancel the installation.

Step 22 On the Cisco Emergency Responder Configuration page, do the following:

Enter the emergency number (for example, 911).

Select the Cisco Unified Communications Manager version. Use the Up or Down arrows to select the version number, the select OK.

Step 23 On the Security End User Language Selection page, choose a language for the Cisco Emergency Responder web pages. The system defaults to the English language.

The Application User Password Configuration page appears.

Step 24 On the Application User Configuration page, enter the username and password. This username and password is associated with the default administrative account and is used to log in to the Cisco ER Administration webpage. Click Help for guidelines.

When you are finished, click OK. The Cisco Emergency Responder Configuration Confirmation page appears.

Step 25 On the Cisco Emergency Responder Configuration Confirmation page, do one of the following:

Select OK to save the Cisco Emergency Responder configuration information and continue with the installation. The system continues the installation process and then reboots.


Caution Once you select OK, you will not be able to modify the Cisco Emergency Responder configuration information.

Select Back if you want to return to the previous page to make modifications. Continue to select Back to scroll through each Cisco ER Application User Configuration page.

Select Cancel to cancel the installation.

Step 26 After the system reboots, it checks the status of various system components. If the system finds any problems, you will be prompted to correct the problem.

If the system does not find any problems, the installation process continues. The system will eject the installation DVD, reboot, and then finish the installation. When the installation is complete, a command-line interface prompt appears.


Note During this process, the system will display the MAC address of the Publisher. Write down the MAC address when it displays; you will use the MAC address later to acquire Cisco ER licenses. If you are not able to capture the MAC address during installation, you can look it up later. See the "Server Licenses" section for information on looking up the server MAC address.


Step 27 To bring up the Cisco ER 8.5 websites, go to any Windows system on the network, start a supported web browser, and enter the following URL:

http://your CER hostname/

or

http://your CER IP address/


Note Make sure that the CER is configured with DNS so that hostname is resolved to the IP address.



Installing the Cisco Emergency Responder Subscriber

After you install the Publisher, you must install the Cisco ER Subscriber. You must install the Subscriber on a separate server from the Cisco ER Publisher.


Caution You must complete the installation of the Publisher, which includes a system reboot, before you start to install the Subscriber.

To install the Cisco ER 8.5 Subscriber, follow these steps:

Procedure


Step 1 On the Publisher server, add the details about the Subscriber server by doing the following:

a. Log in the Publisher's Cisco ER 8.5 Administration website.

b. Select System > Add Subscriber. The Add Server page appears.

c. Enter the hostname of the new Subscriber and click Insert. The Add Subscriber appears again.

d. In the Configured Servers list, check that the hostname/IP address of the new Subscriber is listed.

Step 2 Follows Step 1 through Step 16 in the "Installing Cisco Emergency Responder 8.5 on a New System" section. After you complete Step 16, the Publisher Configuration page appears.

Step 3 On the Publisher Configuration page, select No to indicate that you are installing a Subscriber, not a Publisher. The system displays a warning saying that if this is not the Publisher, you must first configure this server using the Publisher's Administration web interface before you can proceed (see Step 1 of this procedure for more information). Also, this server being added must have network access to the Publisher, which must be in service for the installation to complete successfully.

Click OK to close the warning.

Step 4 The Network Connectivity Test Configuration page appears. The system attempts to verify system connectivity. Click No to continue the installation.

Step 5 The Publisher Access Configuration page appears. Enter the following:

Publisher's hostname

Publisher's IP address

Publisher's Database/Security password

Step 6 Verify the that Publisher information is correct and click OK.

Step 7 The SMTP Host Configuration page appears. Choose Yes if you want to configure the SMTP Host.

Step 8 The Platform Configuration Complete page appears. Select one of the following options:

If the Publisher information is correct, click OK.

If the information is not correct, click the Back button and make the needed corrections on the Publisher Access Configuration page. Then, click OK.

The installation of the Cisco ER Subscriber begins and will take an additional 20 to 30 minutes to complete.

Step 9 When the installation completes, go to the Cisco ER Administration website on the Subscriber to verify that the Subscriber was installed successfully. If the installation succeeded, a message saying "Primary Cisco Emergency Responder is active" will appear. This message indicates that the Subscriber was installed successfully.


Note If the Subscriber installation cannot validate the Publisher, see the "Cannot Validate Publisher" section in the Troubleshooting chapter.


Upgrading to CER 8.5

To upgrade from 7.1(1) or 8.0(1) to a later version of Cisco ER 8.5, use the Cisco Unified OS Administration web interface. See the "Performing Software Upgrades" section for information on upgrading from Cisco ER 7.1 to a later version of Cisco ER 8.5.