Installation Guide for Cisco Unified Operations Manager 8.0
Installing, Migrating, and Uninstalling Cisco Unified Operations Manager
Downloads: This chapterpdf (PDF - 501.0KB) The complete bookPDF (PDF - 1.96MB) | Feedback

Installing, Migrating, and Uninstalling Cisco Unified Operations Manager

Table Of Contents

Installing, Migrating, and Uninstalling Cisco Unified Operations Manager

Preparing to Install Operations Manager

Preparing the Operations Manager Server

Server Preparation Checklist for New Installation and Migration

Preparing a Server Where Provisioning Manager Has Already Been Installed

Ensuring that Service Statistics Manager Uses the Correct HTTPS Port to Contact Operations Manager

Enabling the Full 4 GB of RAM

Preparing Devices for Addition to Operations Manager Inventory

Device-Specific Configurations

Actions to Take Before Adding Devices

Verifying TCP and UDP Ports that Operations Manager Uses

Gathering Information to Provide During Installation

Performing a New Installation

Installation Checklist

Installing Operations Manager—New

Installing Operations Manager in Silent Mode

Installing Mandatory Patches for Operations Manager and Service Monitor 8.0

Preparing to Migrate to Operations Manager 8.0

Migration Paths

Operations Manager Release Versions for Which Migration is Supported

Third-Party Tools and Software Changes

Supported Operating System Upgrades

Supported Order of Migration Tasks

Upgrading from Operations Manager Releases Earlier than 2.2 to Operations Manager 8.0

Performing Operations Manager Database Maintenance

Handling Sybase Database Issues Before Migration for Operations Manager

Fixing DB Fragmentation

Monitoring Operations Manager Process Health

Backing Up Operations Manager Data

Backing Up and Restoring Detailed Device View Configurations Using Operations Manager Utilities

Backing Up and Restoring Operations Manager and Common Services Databases and Files

Preparing Service Monitor for Data Migration

Planning for and Running Service Monitor Call Data Migration

Backing Up the Service Monitor Database Manually

Removing Cisco 1040 Configuration Files from TFTP Servers

Performing a Migration to Operations Manager 8.0

Completing the Migration to Operations Manager 8.0

Reintegrating Service Statistics Manager with Operations Manager 8.0

Reconfiguring Cisco 1040s After a Service Monitor Upgrade

Post-Installation Tasks

Firewall Updates to Avoid Denial of Service Attacks

Configuring Your System for SNMP Queries

NTP Configuration Notes

Manually Clearing Unified CM Obsolete Events

Troubleshooting the Installation

Increase Size of the Virtual Memory Paging File

InstallShield Engine Cannot Be Installed

Installation Exits with Unsupported Locale Error

Uninstalling Operations Manager

Reinstalling Operations Manager


Installing, Migrating, and Uninstalling Cisco Unified Operations Manager


This chapter describes installing, migrating, and uninstalling Cisco Unified Operations Manager (with Cisco Unified Service Monitor) on a Windows system.


Note Service Monitor is a separately licensed product. To use Service Monitor, you must install a Service Monitor license after the Operations Manager installation completes. See Licensing Process, page B-3.


This chapter includes the following:

Preparing to Install Operations Manager

Performing a New Installation

Preparing to Migrate to Operations Manager 8.0

Performing a Migration to Operations Manager 8.0

Post-Installation Tasks

Troubleshooting the Installation

Uninstalling Operations Manager

Reinstalling Operations Manager

Preparing to Install Operations Manager

The information in this section helps you to deploy Cisco Unified Operations Manager (Operations Manager) in your network. Do the following before you install Operations Manager:

Make sure that hardware and software requirements for the server are met. (See Server Requirements, page 1-1.)

Prepare the Operations Manager server for installation or migration. (See Preparing the Operations Manager Server.)

Configure devices so that they can be monitored by Operations Manager. (Preparing Devices for Addition to Operations Manager Inventory.)

Determine whether your existing applications are already using ports that Operations Manager or Cisco Unified Service Monitor (Service Monitor) use. (Existing applications should not use the ports that Operations Manager or Service Monitor use.) See Verifying TCP and UDP Ports that Operations Manager Uses.

Gather information that you might need to provide during the Operations Manager installation. (See Gathering Information to Provide During Installation.)

Preparing the Operations Manager Server

To prepare the server, see each of the following topics:

Server Preparation Checklist for New Installation and Migration

Preparing a Server Where Provisioning Manager Has Already Been Installed

Ensuring that Service Statistics Manager Uses the Correct HTTPS Port to Contact Operations Manager

Enabling the Full 4 GB of RAM

Server Preparation Checklist for New Installation and Migration


Note If you are migrating to Operations Manager 8.0 from an earlier version, see Preparing to Migrate to Operations Manager 8.0 first.


Before you install or mgirate to Operations Manager 8.0, do the following tasks:

Disable the virus scan software on your system. After the installation is complete, we recommend you exclude the NMSROOT directory from virus scanning. Problems can arise when Operations Manager files are locked because of virus scanning.

Disable Windows Data Execution Protection (DEP). DEP should remain off (that is, set to only protect critical Windows system files) as long as Operations Manager is installed on the server.

Set up the correct date and time on the system. Changing the date and time after installation can cause Operations Manager not to work, because it is perceived as a license violation. Also, the self-signed certificates generated during installation become invalid.

Set your system's IP address and hostname. It may be difficult to change them after you complete the installation.)

Verify that the fully qualified domain name of the system on which Operations Manager is installed is Domain Name System (DNS) resolvable. The IP address must be resolvable to the DNS, and the DNS must be resolvable to the IP address (forward and reverse lookup, in DNS terms).

To check name resolution on the Operations Manager server, in a command prompt, run the command NMSROOT\bin>smNameRes.exe.

NMSROOT is the directory where Operations Manager is installed on your system. If you selected the default directory during installation, it is C:\PROGRA~1\CSCOpx.

Verify that the drive that you choose to install Operations Manager on is an NTFS file system.


Note To install Operations Manager on VMware, ensure that you install it on a VMFS file system.


If you are using an IBM server with IBM Director installed, stop the IBM Director WMI CIM server and change the service to manual, or disable it. If you do not, the Service Level View in Operations Manager will not work.

Operations Manager uses ICMP ping to determine the reachability of all devices. Some security applications may detect a burst of ICMP pings as being caused by a malicious application. The security application may then block the ping requests. This can cause Operations Manager to generate a flood of false unreachable events.

To avoid this situation, you should configure security applications so they do not block bursts of ICMP pings from the Operations Manager server.

Clean the temp directory. You can open the temp directory by typing %temp% in a Windows Explorer window.

On Windows 2008, you must configure these PAGE FILE settings for Operations Manager to work:

In System Properties > Advanced > Performance Advanced > Virtual Memory change Page file from Automatically manage paging file size to specifically mention a fixed size. We recommend the Initial and Maximum size be set to the same value. For detailed steps, see Increasing the Paging File Size, page 1-6.

On 4-GB system, Microsoft Windows detects only 3.5 GB of RAM, although your system may have 4 GB installed. If you want to choose the medium or large installation when installing Operations Manager, you must first enable all 4 GB of RAM on the system. See Enabling the Full 4 GB of RAM.


Caution If system memory is less than the minimum required to deploy both Operations Manager and Service Monitor, a message appears, asking you to upgrade your memory for better performance. If system memory is less than the minimum required, an error appears and the installation cannot continue. You must upgrade system memory to at least 4 GB before you continue with the installation.

Verify that the Primary and Active regional settings are set to either US English or Japanese. Other options are not supported by Operations Manager.

You can set the Active regional settings in Control Panel > Regional and Language Options > Regional Options.

You can install Operations Manager on a system with Terminal Services enabled in Remote Administration mode. However, installing Operations Manager on a system with Terminal Services enabled in Application mode is not supported.

If you have enabled Terminal Server in Application mode, disable the Terminal Server, reboot the system, and start the installation again. See Terminal Server Support for Windows 2003 and 2008.

If Internet Information Services (IIS) is detected on your system and if you have continued the installation with IIS services, you cannot use port number 443 for HTTPS. Instead, you must use port numbers ranging from 1026 to 65535 for HTTPS to avoid this conflict.


Note Any time you change the HTTPS port that Operations Manager uses, see Ensuring that Service Statistics Manager Uses the Correct HTTPS Port to Contact Operations Manager.


Close all open or active programs. Do not run other programs during the installation process.

If you have the Cisco Security Agent installed on your system and it is running, shut it down. If you do not do so, you may receive a confirmation message during installation, requesting permission to continue. Click Yes and proceed.

To disable the Cisco Security Agent, right-click the Cisco Security Agent icon and select Security Level > Off.

Operations Manager is installed in the default directory: SystemDrive:\Program Files\CSCOpx

Where SystemDrive is the drive on which the Windows operating system is installed.

If you select another directory during installation, the application is installed in that directory.

The destination folder should not contain any of the following special characters:

! @ # $ % ^ & * ( ) + | } { " [ ] ; ' / ? < > , . ` =

After you click the Install button, you can click Cancel at any time to end the installation or reinstallation. However, any changes to your system will not be undone.

For example, if any new files were installed or if any changes were made to the system files, you need to manually clean up the installation directories.


Note We recommend that you do not terminate the installation while it is running.


If Provisioning Manager is already installed on the server, to prevent conflicts that can cause the Operations Manager installation to fail, see Preparing a Server Where Provisioning Manager Has Already Been Installed.

Preparing a Server Where Provisioning Manager Has Already Been Installed

To install Operations Manager and Provisioning Manager on the same server, we recommend that you install Operations Manager first. However, if Provisioning Manager is already installed and running in Secure mode, to install Operations Manager you must prevent SSL-related conflicts. Ensure that:

Win32 OpenSSL v0.9.8j Light library files are installed correctly.

Operations Manager will not use port 443. (Provisioning Manager uses port 443 for SSL.)


Note Any time that you change the HTTPS port that Operations Manager uses, see Ensuring that Service Statistics Manager Uses the Correct HTTPS Port to Contact Operations Manager.


This section contains:

Ensuring that There Is No Conflict over OpenSSL Library Files

Preventing Conflict over Port 443

Ensuring that There Is No Conflict over OpenSSL Library Files

To ensure no conflict, look for these library files in the Windows system directory:

ssleay32.dll

libeay32.dll

The Windows system directory might be C:\WINDOWS and is defined by the %WINDIR% system environment variable. If the files are in the Windows system directory, perform the following procedure.


Step 1 Uninstall Win32 OpenSSL v0.9.8j Light.

You can use Add or Remove Programs from the Control Panel; you can find the program by looking for OpenSSL.

To install Win32 OpenSSL v0.9.8j Light using the instructions provided in Step 2, download it from this URL: http://www.slproweb.com/products/Win32OpenSSL.html.

Step 2 Install Win32 OpenSSL v0.9.8j Light:

If you receive an error message that Visual C++ 2008 Redistributables are missing, you must download and install the Visual C++ 2008 Redistributables before proceeding. It is available from this URL: (http://www.slproweb.com/products/Win32OpenSSL.html).

a. During the installation, the Copy OpenSSL DLLs to prompt appears and provides two options:

The Windows System directory

The OpenSSL binaries(/bin) directory

b. Select The OpenSSL binaries(/bin) directory.

c. After the installation, copy the ssleay32.dll and libeay32.dll files:

From the C:\OpenSSL\bin folder

To the C:\CUPM\httpd\bin folder

where C:\CUPM is the location where Provisioning Manager is installed and C:\OpenSSL is the location where OpenSSL is installed.

Installing Win32 OpenSSL v0.9.8j Light is only the first step to enable SSL on Provisioning Manager.

Step 3 Finish enabling SSL on Provisioning Manager by generating the security certificate and ensuring that the Apache server is correctly configured.

For more information, see Installation Guide for Cisco Unified Provisioning Manager.


Preventing Conflict over Port 443

When you install Operations Manager, select Custom Installation instead of Typical Installation. During the custom installation, enter an HTTPS port other than 443. If you use Service Statistics Manager, see Ensuring that Service Statistics Manager Uses the Correct HTTPS Port to Contact Operations Manager.

Ensuring that Service Statistics Manager Uses the Correct HTTPS Port to Contact Operations Manager


Note By default, the Operations Manager HTTPS port is 443. (The HTTPS port is also known as the web services port.)


Any time that you change the HTTPS port that Operations Manager uses, Service Statistics Manager integration with Operations Manager fails. To recover, you must reconfigure Service Statistics Manager and reintegrate it with Operations Manager.

For more information, see Configuring Service Statistics Manager to Connect with Operations Manager in User Guide for Cisco Unified Service Statistics Manager. For supported Service Statistics Manager product release version, see Supported Devices Table for Cisco Unified Operations Manager.

You might change the Operations Manager HTTPS port at these times:

Before you install Operations Manager—See Preparing a Server Where Provisioning Manager Has Already Been Installed.

During Operations Manager installation—If port 443 is in use, the installer can automatically assign 8443 as the HTTPS port or you might be prompted to enter a port.

During Operations Manager reinstallation—You might be prompted to enter a port.

Enabling the Full 4 GB of RAM


Note If your operating system is Windows 2003 Server Enterprise Edition, /PAE is enabled by default and, therefore, you might not need to perform this procedure.


On a 4-GB system, Microsoft Windows detects only 3.5 GB of RAM although your system has 4 GB installed. If you want to choose the medium or large installation when installing or upgrading Operations Manager, you must first enable all 4 GB of RAM on the system.


Step 1 On the Operations Manager system, in Microsoft Windows, right-click My Computer.

Step 2 Select Properties.

Step 3 Select the Advanced tab.

Step 4 Under Startup and Recovery, click Settings.

Step 5 Click Edit.

The boot.ini file opens.

Step 6 In the file, add /PAE to the line that starts with "multi(0)disk(0)rdisk(0)partition(1)\WINDOWS=..."

Step 7 Restart the system.


Preparing Devices for Addition to Operations Manager Inventory

This section describes actions you must perform before adding devices to Operations Manager device inventory.

Before adding devices to Operations Manager, do the following:

Configure devices so they can be added to Operations Manager correctly, and so Operations Manager can monitor the devices correctly. (See Device-Specific Configurations.)

Make sure all processes are running on the Operations Manager system. (See Actions to Take Before Adding Devices.)

Device-Specific Configurations

This section contains device-specific configurations for:

Cisco Unified Communications Manager

Cisco Unified Contact Center and Cisco Unity

IPSLA Devices

All Other Devices

Cisco Unified Communications Manager

Make sure that SNMP read access is configured on the Cisco Unified Communications Manager system.

Provide the HTTP username and password for AXL access. This is the same username and password that is used for the Cisco Unified Communications Manager Administration page.

If the Cisco Unified Communications Manager Administration page has HTTPS enabled, make sure HTTPS is enabled on all AXL directories.

For all supported 5.x (and greater) Cisco Unified Communications Managers, make sure that the SOAP-Performance Monitoring API is running on all nodes and that the AXL service is activated on the first node (Publisher).


Note For supported Cisco Unified Communications Managers release versions, see Supported Devices Table for Cisco Unified Operations Manager.


For all supported 4.x Cisco Unified Communications Managers, make sure that the IIS service is enabled.

Cisco Unified Contact Center and Cisco Unity

Make sure that SNMP read access is configured on the Cisco Unified Contact Center and Cisco Unity systems. You may need to download the Remote Serviceability Kit for certain versions of Cisco Unity (see www.ciscounitytools.com).

For Operations Manager to autodiscover Cisco Unified Contact Center devices, each Cisco Unified Contact Center device must be configured with the SNMP v1 read credential. (This may be in addition to the SNMP v2c read credentials).

IPSLA Devices

Make sure that SNMP read and write access is configured on the IPSLA device. The write community string is required to configure tests.

If the device is used as a target device for the jitter node-to-node test, make sure that the IPSLA responder is enabled.

All Other Devices

Make sure that SNMP read access is configured.

Actions to Take Before Adding Devices

Before adding devices to Operations Manager, do the following:

Run pdshow to make sure all processes are running except for the transient processes such as the purge tasks.

Run NMSROOT\objects\smarts\bin\brcontrol and make sure that you see the message stating that VHM and DFM servers are registered to the broker. If you do not see this message, you must start VHMServer or DFMServer manually.


Note NMSROOT is the directory where Operations Manager is installed on your system. If you selected the default directory during installation, it is C:\PROGRA~1\CSCOpx.


Verifying TCP and UDP Ports that Operations Manager Uses

Before installing Operations Manager, make sure that the ports that Operations Manager (and Service Monitor) uses are free. For the TCP and UDP ports that Operations Manager uses, see Table 2-1; for Service Monitor, see Table 2-2.

If you plan to install additional supported products (see Coresident Guidelines, page 1-3), make sure the ports they use are free. For ports used by:

Service Statistics Manager—See Table 2-3.

Provisioning Manager—See Installation Guide for Cisco Unified ProvisioningManager.

After installation, see Firewall Updates to Avoid Denial of Service Attacks.

Table 2-1 Ports that Operations Manager Uses 

Port Numbers
Service Name 
Application

80

Used to reach phones for XML-based data collection of serial numbers and load ID fetched through discovery.

Operations Manager

161

Simple Network Management Protocol (SNMP)

Common Services

162

Trap receiving (standard port)

Common Services

514

Syslog

Common Services

1024-4999

Ephemeral ports

Operations Manager

40000-41000

Used by Common Transport Mechanism for internal application messaging

Operations Manager

42344

Used by Synthetic Testing web service

Operations Manager

42350-42353

Used by messaging software

Operations Manager

43445

Used by Alert History database engine

Operations Manager

43446

Used by inventory service database engine

Operations Manager

43447

Used by event processing database engine

Operations Manager

43449

Used by IP Phone Information Facility database engine

Operations Manager

8080

Used to determine whether the Cisco Unified Communications Manager 5.0 web service is up

This port must be made available to Operations Manager.

Operations Manager

9000

Trap receiving CSListener (Operations Manager server if
port 162 is occupied)

Operations Manager

9002

DynamID authentication (Operations ManagerBroker)

Operations Manager

9009

Default port number used by the IP telephony server for receiving traps from the device fault server

Operations Manager


Table 2-2 Ports that Service Monitor Uses 

Port Numbers
Service Name

22

SFTP—Service Monitor uses SFTP to obtain data from Unified Communications Manager 5.x and later.

53

DNS.

67 and 68

DHCP.

2000

SCCP—Service Monitor uses SCCP to communicate with Cisco 1040s.

43459

QOVRdatabase.

5666

Syslog—Service Monitor receives syslog messages from Cisco 1040s.

5665-5680

Interprocess communication between user interface and back-end processes.

These ports must be free.


Table 2-3 Ports that Service Statistics Manager Uses 

Port Numbers
Service Name

8007

Apache JServ

8008

Tunnel Proxy

8009

Tomcat

8093

JMS Server

9149

JServer Event

48099

Remote Method Invocation

To configure Service Statistics Manager to use a port other than 48099, see the Quick Start for Service Statistics Manager.

48100

JBOSS

To configure Service Statistics Manager to use a port other than 48100, see the Quick Start for Cisco Unified Service Statistics Manager.

48101

HTTP—Web server

48102

Database

12123

Agent Controller Listener

12124

Used by SSM Agent to listen to messages from the SSM server

12125

Database access port that interacts between the agent controller and the database.

12126

Agent controller callback—This port is used by remote SSM agents to send data back to the Service Statistics Manager server.

12130

Checkpoint monitor (for receiving log messages)

12140

CLServer

12141

Log Server

18000

Rate

40402

Licensing

45000

Message server

48443

HTTPS—Secure web server


Gathering Information to Provide During Installation

You might need to supply the following information while you are installing Operations Manager:


Note For information on creating passwords, see Password Information, page A-6.


User Admin password

System Identity Account password

Casuser password (custom installation only)

Guest password (custom installation only)

Common Services database password (custom installation only)

Mail Settings (custom installation and when configuring an HTTPS port other than 443)

If IIS runs on your server, a dialog box will present you with the choice of whether to configure an HTTPS port other than 443 during the installation to avoid port conflict. If you select OK, you will need to enter mail settings.

License information—Location of the license file. If you have already obtained a license file, provide the path. If not, be sure to obtain one. You can do so before or after you install Cisco Unified Operations Manager; see Licensing Process, page B-3.

You can determine the status of your license from the Common Services Licensing Information page.

From the Operations Manager home page, click Administration > Server Administration > Administration > Licensing.

If you install Operations Manager for evaluation purposes, you need not provide a license file. For more information see:

Licensing Overview, page B-1

Licensing Reminders, page B-5


Performing a New Installation


Note If you are migrating to Operations Manager 8.0 from an earlier version, see Preparing to Migrate to Operations Manager 8.0 first.


Operations Manager allows you to choose the method in which to install your software:

Manual Install Mode—Performs a new installation that requires input. See Installing Operations Manager—New and User Input for Installation and Reinstallation, page A-1.

Silent Install Mode—Performs a new unattended installation using a user input file. See Installing Operations Manager in Silent Mode and User Input for a Silent Installation, page A-5 for details.

The installation process takes approximately 60 minutes to complete. Review the Installation Checklist before proceeding with your installation. After the installation, see Post-Installation Tasks for required steps to complete.

Installation Checklist

Follow these guidelines when installing Operations Manager:

Do not install Operations Manager 8.0 before taking a backup (if you are migrating from an earlier version).

Operations Manager requires a dedicated system; do not install it on a system with:

Third-party management software (such as HP OpenView or NetView).

Cisco Secure Access Control Server (ACS).

Any Cisco applications other than those that are documented to be able to coexist with Operations Manager.

The system where Operations Manager is to be installed must be configured for DNS.

Do not install Operations Manager on:

A Primary Domain Controller (PDC) or Backup Domain Controller (BDC)

A FAT file system.

A Windows Advanced Server with Terminal Services enabled in application server mode.

A system that does not have name lookup.

An encrypted directory. Operations Manager does not support directory encryption.

A voice application server or Cisco Unified Communications Manager server.

Do not install any Common Services service packs on Operations Manager.

Verify that the system date and time are set properly.

To speed up installation, disable all virus-scan software while installing. After installation is complete, we recommend you exclude the NMSROOT directory from future virus scanning. Problems can arise when Operation Manager files are locked because of virus scanning.

Your system's IP address and hostname should be set before installation.

If you plan to use Cisco Unified Service Monitor (which is installed when you install Operations Manager), the clocks on Service Monitor and Cisco Unified Communications Manager servers must be synchronized. See NTP Configuration Notes.

Moving your Operations Manager server from Windows Workgroup to Domain is not supported.

If you want to install Operations Manager on a machine with an unsupported locale, see Troubleshooting the Installation for details on steps to take to resolve the problem.


Note If you have configured Operations Manager in a master-slave server setup, install the master server before installing the slave server.


Installing Operations Manager—New

To perform a new installation of Operations Manager:


Step 1 Make sure your system meets these prerequisites:

Required (or desired) operating system upgrades have been performed.

Required service packs are installed.

For system requirements, see Server Requirements, page 1-1.

Step 2 Close all open or active programs. Do not run other programs during the installation process.

Step 3 Disable all anti-virus and Data Execution Protection (DEP) software.

Anti-virus can be re-enabled after installation, but you should EXCLUDE the NMSROOT directory as long as Operations Manager is installed on the server. DEP should remain off (that is, set to only protect critical Windows system files) as long as Operations Manager is installed on the server.

For details on installation tips, see https://supportforums.cisco.com/docs/DOC-9132.

Step 4 Download the zip file that contains the Cisco Unified Operations Manager 8.0 software package to your PC.

Step 5 Unzip the file to your local disk.

Step 6 As the local administrator, log in to the machine on which you will install the Operations Manager software, and double-click the Cisco Unified Operations Manager installer (setup.exe) on your local disk to start the installation program.

The Cisco Unified Operations Manager Setup Program window opens.

If you stopped the installation process to close programs or if Autostart is disabled, click Setup to restart the process.

Step 7 Read any messages and acknowledge them:

If Provisioning Manager is running in Secure mode on the system

Messages appear, prompting you to resolve conflicts and to use a port other than 443 for HTTPS. You will not be able to continue the installation; exit the installation and perform tasks in Preparing a Server Where Provisioning Manager Has Already Been Installed.

If WMI Services are running on the system

A message is displayed stating that, for the installation to proceed, the script will stop WMI Services, complete the installation, and restart WMI Services. To continue, click OK.

If IIS is detected (even if it is disabled)

A message is displayed. To avoid a port conflict with IIS, click Yes. In a later step, you will be prompted to select an HTTPS port other than 443.

The Welcome window appears.

Step 8 Click Next.

The Software License Agreement window appears.

Step 9 Select the I accept the terms of the license agreement radio button and click Next.

The Licensing Information window appears.

Step 10 Select one of the following, and then click Next:

License File Location—Browse to enter the location.

Evaluation Only—You can complete the migration and then register the license file later.

For instructions on obtaining a license file, see Licensing Process, page B-3.

The Setup Type window appears.

Step 11 Select Typical if you want the system to automatically provide the following information to the installation process:

Guest password

Common Services database password

Mail Settings (also appears if you need to configure an HTTPs port other than 443)

If you change the HTTPS port that Operations Manager uses, see Ensuring that Service Statistics Manager Uses the Correct HTTPS Port to Contact Operations Manager for details.

Self-signed certificate information

If you choose the Custom installation mode, you will be prompted to enter this information during the installation process.

Step 12 Click Next.

The Choose Destination Folder window appears.

Step 13 Do one of the following:

Click Next to accept the default installation directory.

Browse to the folder where you would like to install Operations Manager, and click Next.

The installation program checks dependencies and system requirements.

If you are installing on a virtual machine with a dynamic MAC address:

Another warning message will be displayed. Click Yes.

After the installation completes, you can run Operations Manager in Evaluation mode without problems. Outside of Evaluation mode, you must configure a static MAC address to run Operations Manager. For more information, see VMware Guidelines, page 1-5.)

The System Requirements window displays the results of the requirements check and prompts whether the installation can continue. One of the following might occur:

If there is not enough disk space for the installation, or if memory requirements are not met, the installation program displays an error message and stops. (See Server Requirements, page 1-1.)

If the minimum recommended requirements are not met, the installation program displays a warning message and continues installing.

Step 14 Click Next.

The Enter Admin Password window appears.

a. Enter a password (and confirm), and click Next.

Remember the password. You will need it to log in to Operations Manager until you have configured security and created users in addition to admin.

The Enter System Identity Account Password window appears.

If you selected the Custom installation mode, during this part of the installation you will be asked to enter all the information that is noted in Step 11.

b. Enter a System Identity Account password (and confirm), and click Next.

The Create Casuser dialog box appears.

c. Click Yes to continue with the installation.

If IIS is present on your server and you selected Yes (to avoid port conflict by reconfiguring the HTTPS port), the Mail Settings window appears. The range of ports that you can use for HTTPS is displayed. After entering data, click Next.

If you change the HTTPS port that Operations Manager uses, see Ensuring that Service Statistics Manager Uses the Correct HTTPS Port to Contact Operations Manager for details.

d. The Change casuser Password window appears. Do one of the following:

Click Next to automatically generate the password.

Enter a password and confirm it before clicking Next.

The Summary window appears, displaying the current settings.

Step 15 Click Install.

The installation proceeds.

Step 16 Click OK to confirm additional messages if they are displayed:


Caution Operations Manager requires only one NIC card and supports only one IP address. Operations Manager does not support two NIC cards with different IP addresses.

If Windows SNMP service is not installed on your system, a message appears indicating this.

If you did not supply a license file during the installation, a message about obtaining a license file is displayed.

After the installation is complete, the following message appears:

Before you reboot this system, configure automatic time synchronization on it using 
NTP. Configure this system to use the time server that is used by Cisco Unified 
Communications Managers in your network.


Caution This message may not appear in the foreground and may be minimized in the taskbar. You must click OK in this message or your installation time may be significantly impacted.

For more information, see NTP Configuration Notes.

A pop-up appears with the Yes, I want to restart my computer now radio button selected.

Step 17 Click Finish to reboot the machine.


Note If you are migrating to Operations Manager 8.0, perform the tasks in Completing the Migration to Operations Manager 8.0 instead of completing this procedure.


Wait 30 minutes after the system reboots before starting Operations Manager. This gives all of the Operations Manager processes time to initialize.

Step 18 After the installation completes:

a. Verify that Operations Manager was installed correctly by starting the application. From the Windows desktop, select Start > All Programs > Cisco Unified Operations Manager > Cisco Unified Operations Manager.

b. Install mandatory patches; see Installing Mandatory Patches for Operations Manager and Service Monitor 8.0.

c. See Post-Installation Tasks and Getting Started, page 3-1.


If errors occur during installation, do the following:

Check the installation log file in the root directory on the drive where the operating system is installed. Each installation creates a new log file like this: C:\Ciscoworks_install_YYYYMMDD_hhmmss.log, where YYYYMMDD denotes the year, month and date of installation and hhmmss denotes the hours, minutes and seconds of installation; for example: C:\Ciscoworks_install_20100721_182205.log.

See Troubleshooting the Installation.

Installing Operations Manager in Silent Mode

Silent installation or unattended installation is supported in the Operations Manager single installer. You can perform only a fresh installation of Operations Manager 8.0 in silent installation mode.

Silent install does not prompt for your inputs. It continues the installation based on your inputs provided in a file. You should save the installation inputs in a file and store the file in the system. See User Input for a Silent Installation, page A-5 for more information.


Caution To migrate from a previous version of Operations Manager, you must first back up data and uninstall Operations Manager before you can run a silent installation. See Preparing to Migrate to Operations Manager 8.0.

To perform a silent installation:


Step 1 Ensure you have created your installation response file with values to suit the desired configuration for your system. See User Input for a Silent Installation, page A-5 for details.

Step 2 Download the zip file that contains the Cisco Unified Operations Manager 8.0 software package to your PC.

Step 3 Unzip the file to your local disk.

Step 4 Navigate to the disk1 folder (among the unzipped files) and from the command line, enter this command:

setup.exe QUIET answerfile=C:\answer_file_name

where answer_file_name is the full path of the user input file stored on the system.

The silent installation fails if you do not specify a fully qualified path to the response file, unless the response file is located in the i386 directory and setup.exe is run from that directory. Operations Manager supports new installation and does not support migration, upgrades, uninstall or reinstall in silent mode.

The installation starts.

Step 5 Restart your system after the installation is complete.


Note After the installation completes, you must install mandatory patches; see Installing Mandatory Patches for Operations Manager and Service Monitor 8.0.



Installing Mandatory Patches for Operations Manager and Service Monitor 8.0

After installing Operations Manager 8.0, you must install mandatory patches for Operations Manager and Service Monitor as directed in Release Notes for Cisco Unified Operations Manager 8.0.

Preparing to Migrate to Operations Manager 8.0

Operations Manager does not support an automated software upgrade for version 8.0. See the following sections:

Migration Paths

Performing Operations Manager Database Maintenance

Backing Up Operations Manager Data

Preparing Service Monitor for Data Migration

Migration Paths

See the following sections:

Operations Manager Release Versions for Which Migration is Supported

Third-Party Tools and Software Changes

Supported Operating System Upgrades

Supported Order of Migration Tasks

Upgrading from Operations Manager Releases Earlier than 2.2 to Operations Manager 8.0

Operations Manager Release Versions for Which Migration is Supported

Operations Manager supports the migration paths listed in Table 2-4.

Table 2-4 Migration Paths to Operations Manager 8.0

From This License
To This License
Migration to Operations Manager 8.0 Is Supported from These Operations Manager Releases

Purchased

Purchased

2.3

2.2

2.2.1 (Managed Services Operations Manager)

Evaluation

Evaluation

None



Caution There is no direct upgrade from Operations Manager releases earlier than 2.2. See Upgrading from Operations Manager Releases Earlier than 2.2 to Operations Manager 8.0 for details on how to proceed.

When you migrate to Operations Manager 8.0 from 2.3:

Service Monitor upgrades to release 8.0.

Common Services upgrades to release 4.0. (For more information, see Third-Party Tools and Software Changes.)

Operations Manager, Common Services, and Service Monitor databases are upgraded to Sybase 10.x EBF patch.

If you plan to upgrade your operating system, see Supported Operating System Upgrades.

Third-Party Tools and Software Changes

The following component upgrade is performed in Common Services 4.0:

ActiveMQ - 5.2.0

Sybase ASA is upgraded to the latest version 10.x.

Java Runtime Environment (JRE) is upgraded to JRE 1.6.0_19; Java Plug-in 1.6.0_19 is provided.

Supported Operating System Upgrades

Operations Manager supports the operating system migration paths listed in Table 2-5.


Note If you are upgrading the operating system for the server on which Operations Manager resides to a new version, you must follow the sequence specified in Supported Order of Migration Tasks.


Table 2-5 Supported Operating System Upgrade Paths for Operations Manager 8.0 

From
To

Windows 2003

Either of these:

Windows 2008 Standard

Windows 2008 Enterprise

Windows 2008 Standard

Windows 2008 Enterprise


Supported Order of Migration Tasks


Note To upgrade the operating system on which your Operations Manager is installed, you must perform the upgrade when listed in Table 2-6 to ensure that the Operations Manager migration works properly.


Table 2-6 Operations Manager 8.0 Migration Tasks

Task Overview
Refer to:

1. Perform a complete backup of Operations Manager 2.2.x or 2.3.

Note This backup saves all license files, including those for Operations Manager and any for Service Monitor.

Backing Up Operations Manager Data

2. To save your Service Monitor data: It is optional to migrate call data (for reporting); It is mandatory to back up the Service Monitor database manually.

Note If you do not use Service Monitor, you do not need to perform this step.

Preparing Service Monitor for Data Migration

3. Uninstall Operations Manager 2.2.x or 2.3.

Uninstalling Operations Manager

4. (Optional) Upgrade your operating system.

Note If you plan to upgrade your operating system, you must do so now for the Operations Manager migration to succeed.

Follow the operating system product documentation

5. Perform a new installation of Operations Manager 8.0.

Performing a New Installation

6. Complete the migration. Steps include restoring data—the order in which you restore data is documented and you must follow the steps in the order specified—installing upgrade licenses, installing mandatory patches, running rediscovery, etc.

Completing the Migration to Operations Manager 8.0


Upgrading from Operations Manager Releases Earlier than 2.2 to Operations Manager 8.0

You cannot upgrade directly from releases earlier than 2.2 to Operations Manager 8.0. This section gives instructions on upgrading from:

Operations Manager 2.0.x

Operations Manager 2.1

Operations Manager 2.0.x

To ensure safe migration of your Operations Manager 2.0.x data, you must perform these upgrades before you can install Operations Manager 8.0:


Step 1 Upgrade to Operations Manager 2.1. To download Operations Manager 2.1, go to http://www.cisco.com/cgi-bin/tablebuild.pl/cuom21.

Step 2 Perform the upgrade from Operations Manager 2.1 to 2.2 or 2.3.

Step 3 From Operations Manager 2.2 or 2.3, you can perform the upgrade to Operations Manager 8.0 by following the procedures in these sections:

a. Preparing to Migrate to Operations Manager 8.0.

b. Performing a Migration to Operations Manager 8.0.


Operations Manager 2.1

To ensure safe migration of your Operations Manager 2.1 data, you must perform these upgrades before you can install Operations Manager 8.0:


Step 1 Upgrade to Operations Manager 2.2 or 2.3. To download Operations Manager 2.2 or 2.3:

a. Go to http://www.cisco.com/en/US/partner/products/ps6535/index.html

b. Click Download Software.

c. Log into Cisco.com.

d. Follow the online instructions to select Cisco Unified Operations Manager 2.2. or Cisco Operations Manager 2.3 and download the software.

Step 2 Perform the upgrade from Operations Manager 2.1 to 2.2 or 2.3.

Step 3 From Operations Manager 2.2 or 2.3, you can perform the upgrade to Operations Manager 8.0 by following the procedures in these sections:

a. Preparing to Migrate to Operations Manager 8.0.

b. Performing a Migration to Operations Manager 8.0.


For upgrade instructions, see the appropriate installation guide for your release at http://www.cisco.com/en/US/products/ps6535/prod_installation_guides_list.html.

Performing Operations Manager Database Maintenance

You might need to perform some of these tasks before backing up your Operations Manager database. This section contains the following topics:

Handling Sybase Database Issues Before Migration for Operations Manager

Fixing DB Fragmentation

Monitoring Operations Manager Process Health

Handling Sybase Database Issues Before Migration for Operations Manager

If your Operations Manager database is over 10 GB, it may need to be unloaded and reloaded before the migration. A Sybase database failure problem can occur, wherein the database can become corrupt, fail to validate, or grow too large (to over 10 GB, causing the backup procedure to take a long time).

If your database shows any of the issues described, use the following procedure to unload and reload the database. You must know your database password to perform this procedure. If you do not know your database password, contact your customer support representative.


Caution Remember to manually stop the OMHealthMonitor Windows Service when you perform maintenance activities. Not doing so may result in processes being restarted that have been intentionally stopped. For details on OMHealthMonitor, see Monitoring Operations Manager Process Health.


Step 1 Stop the daemon manager:

% net stop crmdmgtd


Tip Ensure you wait until all database processes have stopped running. You can check for running dbeng9 or dbsrv9 processes using the process explorer tool.


Step 2 Unload the database:

% dbunload -c "uid=<username>;pwd=<pwd>;dbf=<db name>" <Directory to unload data>

For example:

%dbunload -c "uid=itemFhUser;pwd=<pwd>;dbf=itemFh.db" c:\unload

Step 3 Remove and save the itemFh.db to another directory.

Step 4 Initialize the new database:

% dbinit -p 4096 itemFh.db

Step 5 Reload the new database:

% dbisqlc -c "uid=<default username;pwd=<default passwd>;dbf=<db name>" reload.sql

For example:

%dbisqlc -c "uid=dba;pwd=sql;dbf=itemFh.db" reload.sql

Step 6 Delete the newly created *.DAT and *.SQL files, and restart the daemon manager.

%rm *.dat *.sql
net start crmdmgtd

Fixing DB Fragmentation

To clean up fragmentation (unwanted allocated space) in the Operations Manager FHDB database without losing data:


Step 1 Ensure you know the password of FH db.

Step 2 Create a backup of the file CSCOpx\databases\itemEpm\itemFh.db by copying it to another location.

If you cannot copy this file, stop the daemon manager and then try again.

Step 3 Stop the daemon manager:

net stop crmdmgtd

Step 4 Unload the database:

% dbunload -c "uid=<username>;pwd=<pwd>;dbf=<db name>" <Directory to unload data>

For example:

%dbunload -c "uid=itemFhUser;pwd=<pwd>;dbf=C:\Program 
Files\CSCOpx\databases\itemFh\itemFh.db" c:\unload

Step 5 Enter: perl dbRestoreOrig.pl dsn=itemfh dmprefix=FH

Step 6 Reload the database:

% dbisqlc -c "uid=itemFh;pwd=XXX;dbf=C:\Program Files\CSCOpx\databases\itemFh\itemFh.db" reload.sql

Step 7 Start daemon manager:

net start crmdmg

Step 8 At the command line, enter: NMSROOT/conf/itemDb/bin/dbreload.pl.

After you invoke the utility, command line options walk you through the steps. This utility reloads all Operations Manager databases given the password. If you do not know the database password, the utility prompts you for a new one, resets it on all the databases, and then executes the reload.


Monitoring Operations Manager Process Health

OMHealthMonitor is a Windows Service that monitors Operations Manager processes and restarts them if they have shutdown unexpectedly or are out of memory and are in an unstable state. If a process is out of memory, the logs are backed up and the process is restarted.

Administrators should routinely check the FH DB size and run the dbreload utility when it reaches a certain size. It is located in the CSCOpx\HealthMonitor directory.


Caution Whenever you have maintenance or debugging tasks to perform, you must stop the OMHealthMonitor Windows Service so that processes that are intentionally shut down are not inadvertently restarted. Run the following commands:

net stop OMHealthMonitor
net start OMHealthMonitor

OMHealthMonitor performs the following tasks:

Stores a backup of logs belonging to terminated processes before attempting to restart them.

Ignores all the processes configured by the user and only restarts the remaining processes if they are not running.

Monitors only Operations Manager and Common Services (CWCS) processes.

Logs debug information into a log file named HealthMonitor.log located in CSCOpx\HealthMonitor\log.

Logs audit information for all restarted processes into an audit log located in CSCOpx\HealthMonitor\audit.

Sends email to the administrator (if configured) when the Audit logs are updated.

For details on the where HealthMonitor stores data, see Table 2-7.

Table 2-7 Health Monitor Directories

Directory Name
Contents

Audit

Contains the audit file, HealthMonitor.audit.

Backup

Contains the backed up log files of restarted processes.

Conf

Contains the required configurations files.

Log

Contains the debug log file, HealthMonitor.log.

scripts

Contains the HealthMonitor.pl Perl script and modules.


For more information on how to edit the Health Monitor configuration files or view backed up process logs, see the online help or User Guide for the Cisco Unified Operations Manager.

Backing Up Operations Manager Data


Note Backup and restore is supported only from version 2.2 and 2.3 to 8.0. Backup and restore must be done on the same machine.


Before backing up Operations Manager database, you might need to perform some database maintenance. To determine whether this is the case, see Performing Operations Manager Database Maintenance.

To perform a complete backup of Operations Manager, do both of the following:

Backing Up and Restoring Detailed Device View Configurations Using Operations Manager Utilities

Backing Up and Restoring Operations Manager and Common Services Databases and Files


Caution If your database backup has a different admin password than the existing Operations Manager server, the admin password reverts to the restored admin password after the migration.

As an ongoing maintenance measure, scheduled backups should occur weekly or monthly; not daily. You must delete the old versions of the backed up files manually.

For details on known issues, see the release notes on Cisco.com.

Backing Up and Restoring Detailed Device View Configurations Using Operations Manager Utilities

The Operations Manager inventory backup utility backs up the states of all components of all types of monitored or partially monitored devices in the Detailed Device View (DDV). The inventory backup utility does not cover suspended devices. Inventory backup and restore is supported only from version 2.2 and 2.3 to 8.0. Backup and restore must be done on the same machine.


Note The inventory backup utility is separate from and must be used in addition to the database backup described in Backing Up and Restoring Operations Manager and Common Services Databases and Files.



Caution Ensure that the daemon processes for this system are up and running to allow for data backup.

The restore utility restores the managed states of non- suspended devices in the Detailed Device View.

To run the backup utility:


Step 1 Open a DOS prompt and enter:

% PROGRA~1\CSCOpx\objects\vhm\utilities\inventoryBackup default

Where default saves the managed states of all monitored and partially monitored devices to the inventoryBackup file. No user input is needed while the script is running.


Caution Backup on a network drive is not supported. Although the CLI is functional, we recommend you do not use it due to network connectivity issues. As a result, the mapped network drive on the server will not be available for selection in the user interface.

If you prefer to enter a specific filename or a list specific device IP addresses, enter:

% PROGRA~1\CSCOpx\objects\vhm\utilities\inventoryBackup

The script prompts you to enter the filename and device information.


Caution After you migrate to Operations Manager 8.0, you can run the inventoryRestore script only after rediscovering all devices from the Operations Manager Device Management interface. During device rediscovery, the system may be under a heavy load, resulting in the user interface becoming unresponsive.
The dashboards may not refresh during this time. We recommend that you wait to perform any user interface actions until device discovery is complete.

Step 2 To run the restore utility, open a DOS prompt and enter:

% PROGRA~1\CSCOpx\objects\vhm\utilities\inventoryRestore default

Where default restores the data saved in the inventoryBackup.xml file. No user input is needed while the script is running.

If you want to input your own filename enter:

% PROGRA~1\CSCOpx\objects\vhm\utilities\inventoryRestore

The script prompts you to enter the filename you previously created using the backup utility.


Backing Up and Restoring Operations Manager and Common Services Databases and Files

You must use the Common Services backup and restore features during your migration to Operations Manager 8.0.

The Common Services backup feature backs up the Operations Manager and Common Services databases, selected files, and all license files including those for Operations Manager and Service Monitor.

The Common Services backup feature does not back up the following: The state of components in the Detailed Device View (DDV); The database for Service Monitor; The call data from which reports are generated in Service Monitor. Therefore, additional procedures are provided to backup up each of them (elsewhere in this guide).

The backup and restore features are supported only from version 2.2.x and 2.3 to 8.0. Backup and restore must be done on the same machine.


Caution Backup on a network drive is not supported. Although the CLI is functional, we recommend that you do not use it due to network connectivity issues. As a result, the mapped network drive on the server will not be seen from the user interface for drive selection.

Because Operations Manager supports the Device Credentials Repository (DCR), you should refer to topics in Common Services online help:

Effects of Backup-Restore on DCR

Master-Slave Configuration Prerequisites and Restore Operations

To access Common Services online help, select Administration and then select a topic under any heading that includes (Common Services). When the new window opens, click Help in it.

To run back up and restore the database:


Step 1 From the Operations Manager home page, click the CiscoWorks link.

The CiscoWorks home page opens.

Step 2 Under Common Services, select Server > Admin > Backup.

The Backup Job page appears.

Step 3 Click the Help button and follow the instructions for backing up and restoring data.


Note Print the restore instructions from the Common Services help. When you restore, you will be prompted for whether you want to restore the license files; for the migration to succeed, you must respond yes.



Database files are stored using the backup directory structure described in Table 2-8.

Format—/generation_number/suite/directory/filename

Example—/1/itemFh/database/itemFh.db

Table 2-8 Operations Manager Backup Directory Structure 

Option
Description
Usage Notes

generationNumber

Backup number

For example, 1, 2, and 3, with 3 being the latest database backup.

suite

Application, function, or module

When you perform a backup, data for all suites is backed up. The Common Services server suite is cmf. The Operations Manager application suites are:

dfm—Data collection and analysis for devices in IP infrastructure

itemEpm—Event promulgation

itemFh—Alert history

itemInv—Device inventory

itemIPIU—Phone information

qovr—Service quality

vhm—Data collection and analysis for voice-enabled devices

wpu—Node-to-node tests.

(The Service Monitor suite is qovr.)

directory

What is being stored

Each application or suite listed. Directories include database and any suite applications.

filename

File that has been backed up

Files include database (.db), log (.log), version (DbVersion.txt), manifest (.txt), tar (.tar), and data files (datafiles.txt).


Preparing Service Monitor for Data Migration


Step 1 Change the database password of the Service Monitor 2.x system.

a. On the Service Monitor system, open a command prompt.

b. Stop all processes by entering:

net stop crmdmgtd 

c. Change to the Installation Directory by entering:

cd NMSROOT\bin 

(NMSROOT is the directory where Service Monitor is installed; its default location is C:\Program Files\CSCOpx.)

d. Run perl dbpasswd.pl dsn=qovr npwd=cisco. (Changes the password to cisco.)

e. Start all processes by entering:

net start crmdmgtd 

Step 2 In a backup folder, make a copy of the NMSROOT\qovr\config\ptm\creds file.

Step 3 If you want to migrate call data, see Planning for and Running Service Monitor Call Data Migration.

Step 4 Backup the Service Monitor database (see Backing Up the Service Monitor Database Manually).

Step 5 If you have Cisco 1040 sensors, do the tasks in Removing Cisco 1040 Configuration Files from TFTP Servers.


Planning for and Running Service Monitor Call Data Migration

Call data is the data from which Service Monitor generates reports. Migrating call data is optional. However, to keep the data, you must migrate it before you start the upgrade to Service Monitor 8.0. You can find the call migration tool in the zip file that contains the Service Monitor product on Cisco.com.


Note The README_QOVR_CMT.TXT. file that is included with the Call Migration Tool provides estimates of the time that data migration takes and the disk space it uses. It also explains the effect that running the tool has on Operations Manager and Service Statistics Manager, if they are installed in your network.



Step 1 Download the zip file (CUSM8_0.zip) that contains the Service Monitor product from Cisco.com. You can navigate to the file as follows:

a. Go to this URL: http://www.cisco.com/en/US/partner/products/ps6536/tsd_products_support_series_home.html.

b. If you have not already logged in to Cisco.com, log in.

c. Click the Download Software link.

d. Follow the online instructions to select Cisco Unified Service Monitor 8.0 and download the zip file.

Step 2 Extract the QOVR_CMT.zip file from the \install\CallMigrationTool folder in the CUSM8_0.zip file.

Step 3 Extract the README_QOVR_CMT.TXT file from the QOVR_CMT.zip file and use the information in it to plan for and execute the migration.


Backing Up the Service Monitor Database Manually

You must back up the Service Monitor database manually to nonlocal storage. (The Service Monitor database can potentially grow to greater than 10 GB.). To do this:


Step 1 Log into the system where Service Monitor is installed.

Step 2 Stop the daemon manager using this command:

net stop crmdmgtd

Step 3 From NMSROOT\databases\qovr, copy the files qovr.db and qovr.log to a tape, an external drive, or a network directory (not a local directory).

This ensures data integrity in case of hardware failure and ensures that backup data does not exhaust local disk space.

Step 4 Restart the daemon manager using the following command:

net start crmdmgtd

Removing Cisco 1040 Configuration Files from TFTP Servers

We recommend that you delete existing Cisco 1040 configuration files—one QOVDefault.CNF file and a QoVMACAddress.CNF file for each sensor—from your existing TFTP servers before you perform the migration.

Immediately after you complete the installation of Operations Manager (includes Service Monitor), Cisco 1040 sensors are unable register to Service Monitor until you perform post-migration configuration steps. For more information, see Reconfiguring Cisco 1040s After a Service Monitor Upgrade.

Performing a Migration to Operations Manager 8.0


NoteIf you have configured Operations Manager in a master-slave server setup, migrate the master server before migrating the slave server.

This procedure is supported only for the Operations Manager releases listed in Operations Manager Release Versions for Which Migration is Supported.



Step 1 Ensure that you have completed preparations:

Backed up all the data that you want to migrate: the DDV, the Operations Manager database, and—if you need Service Monitor data—the Service Monitor database and optionally call data for Service Monitor reports.

Copied the Service Monitor creds file (if using Service Monitor)

Printed the instructions for restoring using the Common Services restore feature; you will need them to restore the Operations Manager data.

Step 2 Uninstall Operations Manager:

a. Follow instructions in Uninstalling Operations Manager.

b. Delete the CSCOpx directory.

Step 3 If you are upgrading your opererating system, do so now.

Step 4 Ensure that the Operations Manager server is prepared for a fresh installation; see Preparing the Operations Manager Server.

Step 5 Install Operations Manager 8.0:

a. See Installation Checklist

b. See Installing Operations Manager—New

Step 6 Immediately after completing the installation and rebooting the system, perform the procedures in Completing the Migration to Operations Manager 8.0.


Completing the Migration to Operations Manager 8.0


Step 1 Log into the Operations Manager server as an Administrator and stop the daemon manager using this command:

net stop crmdmgtd

Step 2 Restore the Operations Manager database; see Backing Up and Restoring Operations Manager and Common Services Databases and Files.


Note When prompted, you must agree to restore the license files; enter yes.


Step 3 If you backed up the Service Monitor database and files before starting the migration, do the following:

a. Change the Service Monitor database password to the same password you set in Service Monitor 2.x.

b. Restore the Service Monitor database that you backed up earlier (see Backing Up the Service Monitor Database Manually).

c. Copy the previously backed-up creds file to the new installation, in NMSROOT\qovr\config\ptm.

Step 4 Install the required patches. See Installing Mandatory Patches for Operations Manager and Service Monitor 8.0.

Step 5 Restart the daemon manager using the following command:

net start crmdmgtd

Step 6 Log into Operations Manager; see Starting Operations Manager, page 3-21. You will be running Operations Manager under an evaluation license until you apply your upgrade license or licenses.

Step 7 Apply the upgrade license or licenses, see Registering a License File with Operations Manager, page B-5.

Step 8 Start rediscovery and allow it to complete.

Step 9 After rediscovery completes, restore the DDV. See Backing Up and Restoring Detailed Device View Configurations Using Operations Manager Utilities.

Step 10 If Service Statistics Manager was reporting on data from Operations Manager before the migration and it is no longer doing so, see Reintegrating Service Statistics Manager with Operations Manager 8.0.

Step 11 If you have Cisco 1040 Sensors in your network, see Reconfiguring Cisco 1040s After a Service Monitor Upgrade.


Reintegrating Service Statistics Manager with Operations Manager 8.0

Service Statistics Manager stops collecting data from Operations Manager when you reinstall or migrate Operations Manager and change either of the following:

The password for the admin user.

The destination location (the directory in which Operations Manager is installed).

To re-enable data collection perform the procedures that are documented in Release Notes for Cisco Unified Service Statistics Manager 1.3.

Reconfiguring Cisco 1040s After a Service Monitor Upgrade

This section provides the minimum steps required to enable Cisco 1040 sensors to register with Service Monitor.

For complete configuration procedures, including how to add Unified Communications Managers and Network Analysis Modules (NAMs) to Service Monitor, see the configuration checklists in User Guide for Cisco Unified Service Monitor.


Step 1 Start Service Monitor.

Step 2 Configure the default configuration file:

a. Select Administration > Configuration > Cisco 1040 > Setup.

The Setup page appears.

b. Update the Default Configuration to TFTP Server fields:

Image Filename—Enter SvcMonAB2_102.img.

Primary Service Monitor—Enter an IP address or DNS name.

Secondary Service Monitor—(Optional) Enter an IP address or DNS name.


Note Occasionally, updated binary image files might be released. For the names of supported binary image files, see Cisco Unified Service Monitor 8.0 Compliance Matrix.


c. Click OK. Service Monitor stores the default configuration file locally and copies it to the TFTP servers that are configured in Service Monitor.

d. Copy the binary image file, SvcMonAB2_102.img, from NMSROOT\ImageDir on the Service Monitor server to the root location on the TFTP server. (NMSROOT is the directory where Service Monitor is installed; its default location is C:\Program Files\CSCOpx.)

e. Verify that the newly created QOVDefault.CNF file is on the TFTP server.

If it is not, upload it to the root location on the TFTP server from the Service Monitor image file directory, NMSROOT\ImageDir. For examples of the configuration files, see "Sample Sensor Configuration Files" in the Installation Guide for Cisco Unified Service Monitor on Cisco.com.

If you use Unified Communications Manager as a TFTP server, Service Monitor cannot copy configuration files to Unified Communications Manager due to security settings on the latter.

Manually upload the configuration file to the root location on the TFTP server from the Service Monitor image file directory, NMSROOT/ImageDir. After uploading the configuration file, reset the TFTP server on Unified Communications Manager.

For more information, see the Unified Communications Manager documentation.

Step 3 Wait a few minutes and verify that the sensors have registered to Service Monitor.

If they have not, reset the sensors by disconnecting them from the power source and connecting them again.


Warning Before disconnecting a sensor, read the regulatory compliance and safety information in Quick Start Guide for Cisco 1040 Sensor.



Post-Installation Tasks

You must complete the following post-installation tasks to ensure Operations Manager works properly.

Tasks
Refer to

Check the release notes for patches; install any required patches.

Installing Mandatory Patches for Operations Manager and Service Monitor 8.0

To install or verify Windows SNMP service (if you use a third-party SNMP management tool to make SNMP queries to Operations Manager)

Configuring Your System for SNMP Queries

To synchronize the clocks on Service Monitor and Cisco Unified Communications Manager servers

NTP Configuration Notes

If Enhanced Security is enabled on the Windows 2003 or Windows 2008 system, you must add the Operations Manager home page to the Internet Explorer Trusted Sites Zone.

You will not be able to access the Operations Manager home page until it is added to the trusted sites.

Adding the Operations Manager Home Page to the Internet Explorer Trusted Site Zone, page 3-21

Exclude the NMSROOT directory from future virus scanning.

Problems can arise when Operation Manager files are locked because of virus scanning.

See your virus scanning help for instructions.

Clear the Unified Communications Manager events that are no longer used in
Operations Manager.

To view the list of events, see Manually Clearing Unified CM Obsolete Events.


Firewall Updates to Avoid Denial of Service Attacks

If you have Windows Server 2003 Enterprise Edition, use the following procedure to block remote access to all TCP/UDP ports except for those required for external access by Operations Manager.

The list of ports required for Operations Manager external access is listed in the procedure below in Step 6. (CSCsy80792)


Step 1 Open Control Panel for Windows Firewall.

Step 2 Select On to block all outside sources from connecting to this computer. The exceptions to this rule are documented in steps below.

Step 3 Select the Exceptions tab and select any services you may want to open for remote access. For example, Remote Desktop or File and Print Sharing.

Step 4 Select the Advanced tab.

To add exemptions for an individual connection, select the network connection that is used for connecting external clients to this server and then click Settings.

Step 5 Click Add in the Advanced Settings dialog window to enter your port exceptions.

Step 6 In the Service Settings dialog box, enter each of the following TCP/UDP ports one at a time and click OK:

Name
Protocol
Port Number 1

CUOM Web Server

TCP

1741

CUOM HTTPS

TCP

443

CUSM SFTP Server

TCP

22

CUOM Trap Listener

UDP

161

CUOM Trap Listener

UDP

162

CUOM Syslog Receiver

UDP

514

CUSM Syslog Receiver

UDP

5666

1 Note that external and internal port numbers are the same for all the services that require external access.

Repeat Step 7 until all ports are entered.

Step 7 Click Apply and then OK in the Windows Firewall Settings window to close it.

Step 8 Restart the server for the firewall settings to take effect, if required.


Configuring Your System for SNMP Queries

Operations Manager implements the system application MIB. If you want to use a third-party SNMP management tool to make SNMP queries against the server where Operations Manager is installed, Windows SNMP service must be installed.


Note To improve security, the SNMP set operation is not allowed on any object ID (OID) in the system application MIB. After installing Operations Manager, you should modify the credentials for Windows SNMP service to not use a default or well-known community string.


To enable Operations Manager to manage itself, install and configure SNMP on a local server. We recommend that you install Windows SNMP service before you install Operations Manager.

Use this procedure to determine whether Windows SNMP service is installed.


Step 1 Verify that Windows SNMP service is installed on the server where you will install Operations Manager. To do so:

a. Open the Windows administrative tool Services window.

b. Verify the following:

SNMP Service is displayed on the Windows administrative tool Services window; if so, Windows SNMP service is installed.

SNMP service status is Started; if so, SNMP service is running.

Step 2 If Windows SNMP service is not installed, install it.


Note Windows online help provides instructions for adding and removing Windows components, such as Windows SNMP service. To locate the instructions, try selecting the Index tab in Windows online help and entering a keyword or phrase, such as install SNMP service.



NTP Configuration Notes

The clocks on Service Monitor and Cisco Unified Communications Manager servers must be synchronized for Service Monitor reports to include complete and up-to-date information and accurately reflect activity during a given time period. These notes offer a starting point and do not provide complete instructions for configuring NTP.

To get started:


Step 1 Discuss with your Cisco Unified Communications Manager administrators to determine the time server with which Service Monitor should synchronize.

For further details see Cisco IP Telephony Clock Synchronization: Best Practices, a white paper on Cisco.com, useful; read it at this URL: http://cisco.com/en/US/products/sw/voicesw/ps556/prod_white_papers_list.html.

Step 2 Use your system documentation to configure NTP on the Windows Server 2003 system where Service Monitor will be installed.

Step 3 Configure NTP with the time server being used by Cisco Unified Communications Managers in your network.

For further details see How to configure an authoritative time server in Windows Server 2003, useful; look for it at this URL: http://support.microsoft.com/kb/816042.


Note This website is Copyright © 2010, Microsoft Corporation.



Manually Clearing Unified CM Obsolete Events

The following Unified CM events are obsolete and should be manually cleared from the Fault Monitor after installation or migration.

cpuUtilizationExceeded

InsufficientFreeHardDisk

InsufficientFreeMemory

InsufficientFreeVirtualMemory

ServiceDown

IDS Replication Failure

Troubleshooting the Installation

Some issues may result during an installation. Use the following recommendations to resolve these installation issues:

Increase Size of the Virtual Memory Paging File

InstallShield Engine Cannot Be Installed

Installation Exits with Unsupported Locale Error

If errors occur during installation, check the installation log file in the root directory on the drive where the operating system is installed. Each installation creates a new log file like this: C:\Ciscoworks_install_YYYYMMDD_hhmmss.log, where YYYYMMDD denotes the year, month and date of installation and hhmmss denotes the hours, minutes and seconds of installation; for example: C:\Ciscoworks_install_20100721_182205.log.

Increase Size of the Virtual Memory Paging File

Symptom:

Windows Virtual Memory is too low. Event Viewer (System log) shows that the system is running out of virtual memory.

Message:

Application popup: Windows - Virtual Memory Minimum Too Low: Your system is low on virtual memory.

Cause:

Windows is increasing the size of your virtual memory paging file. During this process, memory requests for some applications may be denied.

Action:

To change the size of the virtual memory paging file on the Operations Manager server, perform the following steps.


Step 1 From the Windows Start menu, click Start > Control Panel > System.

Step 2 Select the Advanced tab and under Performance, click Settings.

Step 3 Select the Advanced tab and under Virtual memory, click Change.

Step 4 Under Paging file size for the selected drive, click Custom size and type a new paging file size in megabytes in the Initial size (MB) and Maximum size (MB) boxes, and then click Set.

The virtual memory must be 1.5 times of RAM.

The Initial and Maximum size should be set to the same value.


InstallShield Engine Cannot Be Installed

Symptom:

During Operations Manager installation, the following error message appears:

Message:

"The InstallShield Engine(iKernel.exe) could not be installed. Ikernel.exe could not be copied to C:\Program Files\Common Files\InstallShield\Engine\6 \Intel 32."

Cause:

Multiple instances of the Install Program are being run.


Note InstallShield (the install program for the Operations Manager) allows only one ikernel.exe running at a time.


Action:

Stop all install programs and run the Operations Manager installation program.

Installation Exits with Unsupported Locale Error

There are instances where the Operations Manager installation fails with the following error message (even if the regional language is set to English):

"You are trying to install Cisco Works on an unsupported locale. Cisco Works         \
supports only US English or Japanese languages. The setup program will exit when     \
you click OK. Please change the regional settings to either of these languages".

To configure the locale setting, and resolve this issue, do the following:


Step 1 Go to Control Panel > Regional and Language Option.

Step 2 From the Regional Option tab ensure the following are set:

In Standards and Formats, click Customize and select English (United States) or English (Japanese).

In Location, select United States or Japanese.

Step 3 From the Advanced tab in Language for non-Unicode Programs, select English (United States) or English (Japanese).

Step 4 Click Apply.

Check the registration entries and compare them with the values below. If the values are different from those shown below, change them to "00000409".

HKEY_USERS \\DEFAULT\\Control Panel\\International \\ locale \\00000409 \

HKEY_CURRENT_USER\\Control Panel\\International\\ locale \\00000409

Step 5 If the "International" key is missing, make sure you have the required permission to create a key at the super group; for example, Control Panel.

To create a key do either one of the following:

Export the same key from another machine to this machine. For example, export the HKEY_CURRENT_USER key to this machine.

Create this key and manually add all entries under this key.


Uninstalling Operations Manager


Note If you are migrating to Operations Manager 8.0 from an earlier version, you must back up your data before you uninstall Operations Manager; see Preparing to Migrate to Operations Manager 8.0,



Caution You must use the Operations Manager uninstallation program to remove Operations Manager from your system. If you try to remove the files and programs manually, you can seriously damage your system.

Before you uninstall Operations Manager, ensure that:

Remote desktop sessions are not connected to Operations Manager. Remote sessions can lock files; if Operations Manager processes are running, Operations Manager installation will stop.

You have deleted all the phone status, node-to-node, and SRST tests from the application. If you do not delete these tests, they will continue to run on the router.

To delete these tests, use the respective configuration page for each test (see the Cisco Unified Operations Manager online help for information on deleting each test).


Step 1 As the local administrator, log in to the system on which Cisco Unified Operations Manager is installed.

Step 2 Select Start > All Programs > Cisco Unified Operations Manager > Uninstall Cisco Unified Operations Manager.

If Windows Management Instrumentation (WMI) is running on the system, this message is displayed:

Windows Management Instrumentation (WMI) is running. This locks processes and impedes 
installation. To avoid WMI conflicts, this program will stop and immediately restart the 
WMI service.stating that WMI impedes the uninstallation and to prevent conflict, the 
script will stop WMI services and restart them. 

Step 3 Click OK.

To cancel the uninstallation, you can click Cancel on the next window that appears.

An Uninstallation window appears, listing the components to uninstall. To continue, click Next; otherwise click Cancel.

Messages showing the progress of the uninstallation appear.

The following message appears:

Uninstallation is complete. Before you install CW200 product, you must restart your 
computer and delete any residual files from C:\PROGRA~1\CSCOPX manually. 

The Yes, I want to restart my computer now radio button is selected by default. Alternatively, you can select the No, I will restart my computer later radio button.


Note You must restart your computer to finalize the uninstallation.


Step 4 Click Finish.


Reinstalling Operations Manager

To reinstall Operations Manager:


Step 1 As the local administrator, log into the machine on which you will install the Cisco Unified Operations Manager software.

Step 2 Close all open or active programs. Do not run other programs during the reinstallation process.

Step 3 From the command line, stop the OMHealthMonitor service by entering the following command:

net stop OMHealthMonitor

Step 4 Click the Cisco Unified Operations Manager executable file, Cisco_Unified_OperationsManager_with_ServiceMonitor_8.0.exe, that you obtained through e-delivery.

The installer window appears, prompting you to reinstall Cisco Unified Operations Manager.

Step 5 Read any messages and acknowledge them to continue:

If WMI Services are running on the system, a message appears that for the installation to proceed, the script will stop WMI Services, complete the installation, and restart WMI Services. To continue, click OK.

Acknowledge the message that a database backup will not be performed by clicking OK. (If you have not performed a backup, exit the reinstallation now and perform a backup.)

The Welcome window appears.

Step 6 Click Next.

The Software License Agreement window appears.

Step 7 Select the I accept the terms of the license agreement radio button and click Next.

The Setup Type window appears.

Step 8 Select Typical or Custom.

Step 9 Click Next.

Step 10 The System Requirements window displays the results of the requirements check and prompts you acknowledge whether the reinstallation can continue.

Step 11 Click Next.

If you chose Typical installation, proceed to .

If you chose Custom installation, you are prompted to enter:

Passwords—For admin, guest, system identity account, casuser, database. (In most cases, you can click Next to retain the existing password. The casuser password is generated for you if you click Next.

Security certificate information.

Data transport protocol.

An information dialog box appears, confirming reinstallation.

Step 12 Click OK.

The Summary window appears, displaying the current settings.

Step 13 Click Next.

The installation proceeds.

Step 14 Click Finish to reboot the machine.

Step 15 After the reinstallation completes, verify that Operations Manager was reinstalled correctly by starting the application. From the Windows desktop, select Start > All Programs > Cisco Unified Operations Manager > Cisco Unified Operations Manager.

To make sure all existing devices go to the Monitored state, you must configure Operations Manager to perform rediscovery after restart. Do the following:

a. In Operations Manager, select Administration > Device Management > Device Configuration > Modify/Delete Devices.

b. In the device selector, select the All Devices check box.

c. Click Rediscover.

To restore the Detailed Device View configuration, run the restore utility after rediscovery completes. Be sure you have rediscovered your devices before completing this step.


If errors occur during installation, do the following:

Check the installation log file in the root directory on the drive where the operating system is installed. Each installation creates a new log file like this: C:\Ciscoworks_install_YYYYMMDD_hhmmss.log, where YYYYMMDD denotes the year, month and date of installation and hhmmss denotes the hours, minutes and seconds of installation; for example: C:\Ciscoworks_install_20100721_182205.log.

See Troubleshooting the Installation.