Installation Guide for Cisco Unified Operations Manager 2.3
Installing, Uninstalling, and Upgrading Cisco Unified Operations Manager
Downloads: This chapterpdf (PDF - 375.0KB) The complete bookPDF (PDF - 1.65MB) | Feedback

Installing, Uninstalling, and Upgrading Cisco Unified Operations Manager

Table Of Contents

Installing, Uninstalling, and Upgrading Cisco Unified Operations Manager

Preparing to Install Operations Manager

Preparing the Operations Manager Server

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

Upgrading to Cisco Unified Operations Manager 2.3

Upgrade Paths

Upgrading from Operations Manager Releases Prior to 2.1 to Operations Manager 2.3

Third-Party Tools and Software Changes

Backing Up Data Before the Upgrade or Reinstallation

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

Backing Up and Restoring Using CiscoWorks

Backing Up the Service Monitor Database Manually

Before You Start the Upgrade

(Optional) Planning for (and Running) Service Monitor Call Data Migration Before the Upgrade

Upgrading to Operations Manager 2.3

Restoring Detailed Device View Configuration Data to Operations Manager 2.3

Configuring Service Monitor After Upgrading

Reinstalling Operations Manager

Uninstalling Operations Manager

Configuring Your System for SNMP Queries

NTP Configuration Notes


Installing, Uninstalling, and Upgrading Cisco Unified Operations Manager


This chapter describes installing 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. A Service Monitor 2.0 license also supports Service Monitor 2.2. See Licensing Process, page B-3.


This chapter includes the following:

Preparing to Install Operations Manager

Performing a New Installation

Upgrading to Cisco Unified Operations Manager 2.3

Reinstalling Operations Manager

Uninstalling Operations Manager

Configuring Your System for SNMP Queries

NTP Configuration Notes

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-2.)

Prepare the Operations Manager server for installation. (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) uses. (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

Before installing or upgrading Operations Manager, do the following:

Before upgrading or reinstalling Operations Manager, you must back up Operations Manager. See Backing Up Data Before the Upgrade or Reinstallation. (The 2.3 upgrade and reinstallation procedures do not perform a backup due to time limitations.)

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's not simple 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.


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.


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 4-GB system, Microsoft Windows detects only 3.5 GB of RAM, even though 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, installation of 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 a Windows 2003 Server.

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.

We recommend that you disable the virus scan software on your system. You can restart it after all installations are completed.

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, reinstallation, or upgrade. 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, 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.


Ensuring that There Is No Conflict over OpenSSL Library Files


Step 1 In the Windows system directory—which might be C:\WINDOWS and is defined by the %WINDIR% system environment variable—look for these library files:

ssleay32.dll

libeay32.dll

If you find them, complete the steps remaining in this procedure.

Step 2 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 3, download it from this URL: http://www.slproweb.com/products/Win32OpenSSL.html.

Step 3 Install Win32 OpenSSL v0.9.8j Light:


Note If you receive an error message stating 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

Select The OpenSSL binaries(/bin) directory.

b. 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.


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


Step 4 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 2.3.

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 or upgrade—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 should not need to perform this procedure.


On a 4-GB system, Microsoft Windows detects only 3.5 GB of RAM even though 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

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 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).

For all 3.x and 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

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 ports that Operations Manager uses, see Table 2-1; for Service Monitor, see Table 2-2.

Operations Manager uses the following TCP and UDP ports.

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 Services1

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

Note 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

1 For a list of all ports that Common Services uses, see Installing and Getting Started With CiscoWorks LAN Management Solution 3.2.


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.

Note These ports must be free.


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-7.


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)


Note 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.


Note You can determine the status of your license from the Common Services Licensing Information page. From the Operations Manager home page, click CiscoWorks in the upper-right corner of the window. The CiscoWorks home page opens. Under Common Services, select Server > Admin > Licensing. An Operations Manager 2.0 license also supports Operations Manager 2.3. You are not required to get a new license.



Note If you are installing Operations Manager for evaluation purposes:

You do not need to supply a license file.

You might be interested in the following information:

Licensing Overview, page B-1

Licensing Reminders, page B-5


Performing a New Installation

The installation process takes approximately 60 minutes to complete.

Follow these guidelines when installing Operations Manager:

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 CiscoWorks Common Services 3.2 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.

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

If you are going 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.


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-2.

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

Step 3 As the local administrator, log in to the machine on which you will install the Operations Manager software, and insert the Cisco Unified Operations Manager CD-ROM into the CD-ROM drive. The Cisco Unified Operations Manager Setup Program window opens.


Note If the CD-ROM is already in the CD-ROM drive and you stopped the installation process to close programs or if Autostart is disabled, click Setup.exe to restart the process.


Step 4 Read any messages and acknowledge them:

If Provisioning Manager is running in Secure mode on the system—Messages are displayed telling 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 5 Click Next. The Software License Agreement window appears.

Step 6 Select the I accept the terms of the license agreement radio button and click Next. The Licensing Information window appears.

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

License File Location—Browse to enter the location.

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


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


The Setup Type window appears.

Step 8 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)


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.


Self-signed certificate information

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

Step 9 Click Next. The Choose Destination Folder window appears.

Step 10 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. To license and run Operations Manager, you must configure a static MAC address. For more information, see VMware Guidelines, page 1-6.)

The System Requirements window displays the results of the requirements check and advises 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-2.)

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

Step 11 Click Next. You will need to provide input as follows:

a. The Enter Admin Password window appears. Enter a password (and confirm), and click Next.


Note 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.


Note 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 8.


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

c. The Create Casuser dialog box appears; click Yes to continue with the installation.

d. 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.


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.


e. 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 12 Click Install. The installation proceeds.

Step 13 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 will inform you of this fact.

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

When 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.

Step 14 Eject the CD.


Note Store the CD in a secure, climate-controlled area for safekeeping.


Step 15 A window appears with the "Yes, I want to restart my computer now" radio button selected. Click Finish to reboot the machine.

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

Step 17 After the installation completes, 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.


NoteIf Enhanced Security is enabled on the Windows 2003 system, you must add the Operations Manager home page to the Internet Explorer Trusted Sites Zone. You will not be able to access the Cisco Unified Operations Manager home page until it is added to the trusted sites. See Adding the Operations Manager Home Page to the Internet Explorer Trusted Site Zone, page 3-19.

You should exclude the NMSROOT/databases directory from virus scanning. Problems can arise if database files are locked because of virus scanning.



If any errors occurred during installation, check the installation log in the root directory on the drive. (For example, the CiscoWorks Common Services installation might create C:\Ciscoworks_setup001.log, the Operations Manager installation might create C:\Ciscoworks_setup002.log, and so forth.) The Cisco Technical Assistance Center (TAC) might ask you to send them the installation log.

Upgrading to Cisco Unified Operations Manager 2.3

This section covers the following topics:

Upgrade Paths

Upgrading from Operations Manager Releases Prior to 2.1 to Operations Manager 2.3

Third-Party Tools and Software Changes

Backing Up Data Before the Upgrade or Reinstallation

Before You Start the Upgrade

(Optional) Planning for (and Running) Service Monitor Call Data Migration Before the Upgrade

Upgrading to Operations Manager 2.3

Restoring Detailed Device View Configuration Data to Operations Manager 2.3

Configuring Service Monitor After Upgrading

Upgrade Paths

Operations Manager supports the upgrade paths listed in Table 2-3.

Table 2-3 Upgrade Paths to Operations Manager 2.3

From This License
To This License
Upgrade to Operations Manager 2.3 Is Supported from These Operations Manager Releases

Purchased

Purchased

2.2

2.1 SP1 (2.1.1)

2.1

Evaluation

Evaluation

None



Caution There is no direct upgrade from releases prior to 2.1. See Upgrading from Operations Manager Releases Prior to 2.1 to Operations Manager 2.3 for details on how to proceed.


Note When you upgrade to Operations Manager 2.3 from 2.1, 2.0 or 1.1:

Service Monitor upgrades to release 2.2.

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

When you upgrade to Operations Manager 2.3 from 2.2, Service Monitor, Common Services, and third-party product versions do not change.


You can purchase two levels of functionality for Operations Manager 2.3: Premium Edition and Standard Edition. To get full Operations Manager functionality, you must upgrade to Operations Manager Premium Edition.

Full backup is not run as part of an upgrade or reinstallation, to allow for a short upgrade or reinstallation time. For instructions on how to run your backups, see Backing Up Data Before the Upgrade or Reinstallation before performing your upgrade or reinstallation.

Upgrading from Operations Manager Releases Prior to 2.1 to Operations Manager 2.3

You cannot upgrade directly from Operations Manager releases prior to 2.1 to Operations Manager 2.3. If you are running:

Operations Manager 2.0.x—First upgrade to Operations Manager 2.1. To download Operations Manager 2.1, go to http://www.cisco.com/cgi-bin/tablebuild.pl/cuom21.

Operations Manager 1.x—To ensure safe migration of your Operations Manager 1.x data, you must perform these upgrades before you can upgrade to Operations Manager 2.3:

1. Upgrade from Operations Manager 1.x to 2.0.3. To download Operations Manager 2.0.3, go to http://www.cisco.com/cgi-bin/tablebuild.pl/cuom203.

2. Perform the upgrade from Operations Manager 2.0.3 to 2.1, then to 2.3.

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

Third-Party Tools and Software Changes

The following third-party components are removed and replaced with open-source components in Common Services 3.2:

Visigenics, which was used for CORBA communication, is replaced with JACORB.

Tibco, which was used for event services, is replaced with ActiveMQ.

The following component upgrade is performed in Common Services 3.2:

Sybase ASA is upgraded to version 10.0.1 from 9.x.

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

Backing Up Data Before the Upgrade or Reinstallation

To ensure that you have a backup if corruption occurs, you should back up configuration and data files on the Operations Manager server. The following sections cover various backup scenarios for Operations Manager. Depending on your configuration, you might need to perform each of the following:

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

Backing Up and Restoring Using CiscoWorks

Backing Up the Service Monitor Database Manually

Because Operations Manager supports the Device Credentials Repository (DCR), you should be aware of the information in these topics in User Guide for CiscoWorks Common Services 3.2:

Effects of Backup-Restore on DCR at http://www.cisco.com/en/US/docs/net_mgmt/ciscoworks_common_services_software/3.2/user/
guide/admin.html#wp388174

Master-Slave Configuration Prerequisites and Restore Operations http://www.cisco.com/en/US/docs/net_mgmt/ciscoworks_common_services_software/3.2/user/
guide/admin.html#wp381835)

During the upgrade to Operations Manager 2.3, the following occurs on each component:

Operations Manager—Detailed Device View configuration is backed up.

Common Services—All data (such as server settings, usernames, and passwords) is migrated.

Service Monitor—If you are running Service Monitor on the server, configuration data (such as credentials and threshold settings) is migrated during the upgrade, but report data is not. To migrate report data, you must run the Call Migration Tool before you run the upgrade. See (Optional) Planning for (and Running) Service Monitor Call Data Migration Before the Upgrade.

Operations Manager, Common Services, and Service Monitor databases—All are upgraded to Sybase 10.

Database backup and restore is supported only on the same version of Operations Manager (which includes the database and user configuration data of all Operations Manager modules). The backed-up database should be stored on a different hard disk or a server other than Operations Manager.


Note Ensure that you schedule weekly or monthly backups, instead of daily backups. Also, you must manually delete older versions of the backed-up files.



Caution A warning message displays during the upgrade or reinstallation procedure. If you have not completed a backup, you should exit the installation to perform your backup.

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

During an upgrade to Operations Manager 2.3 and during a reinstallation, the Detailed Device View (DDV) backup runs automatically. The DDV backup utility backs up the states of all components of all types of monitored or partially monitored devices (except for those mentioned in the note that follows) in the DDV. It does not cover suspended devices. You can also run this script at any time to save your device data if you are using Operations Manager 2.3.


Note Operations Manager does not restore DDV configurations on voice services, system processor, hard disk, virtual memory, or RAM components for Cisco Unified Communications Manager systems. Operations Manager uses Real-Time Monitoring Tool (RTMT) polling, not device MIB polling, to create these components and therefore does not display this data in the Operations Manager DDV in release 2.3.



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 nonsuspended devices in the Detailed Device View.


Step 1 If you ran the upgrade or reinstallation program, you do not have to perform this step. To run the backup utility, 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.

If you prefer to enter a specific filename or a list of 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 an Operations Manager 2.3 upgrade, you can run the inventoryRestore script only after rediscovering all devices from the Operations Manager Device Management interface.

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 Using CiscoWorks

This procedure backs up the databases for Common Services and Operations Manager. It does not back up:

The database for Service Monitor—You must back up the Service Monitor database manually. See Backing Up the Service Monitor Database Manually.

The state of components in the Detailed Device View (DDV)—You must back up the DDV component states using Backing Up and Restoring Detailed Device View Configurations Using Operations Manager Utilities.

Backup and restore (including database backup and user configuration data backup) is supported only on the same version of Operations Manager. The backed-up database should be stored on a different hard disk or on a server other than Operations Manager.


Note Ensure that you schedule weekly or monthly backups, instead of daily backups. Also, you must delete old backed-up files manually.



Step 1 From the Operations Manager home page, click CiscoWorks in the upper-right corner of the window. 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.


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

Format—/generation_number/suite/directory/filename

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

Table 2-4 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 CiscoWorks 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).


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.)


Step 1 Log in to 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 qovrx.log to a tape, an external drive, or a network directory (not a local directory). Doing so 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


Before You Start the Upgrade


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


Complete the steps in Preparing the Operations Manager Server.

Make sure your system meets the system requirements (see Server Requirements, page 1-2).

Note that Service Statistics Manager stops collecting data from Operations Manager when you reinstall or upgrade 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).

If you change the admin password or the destination location, you can enable data collection by performing procedures that are documented in Release Notes for Cisco Unified Service Statistics Manager 1.2.

If you use Service Monitor, you should be aware of the following:

To save existing report data, you should run the Call Migration Tool before you start the upgrade. See (Optional) Planning for (and Running) Service Monitor Call Data Migration Before the Upgrade.

It is recommended that you delete existing sensor configuration files—one QOVDefault.CNF file and a QoVMACAddress.CNF file for each sensor—from your existing TFTP servers before you perform the upgrade. Immediately after you upgrade to the Service Monitor 2.2 software, sensors are unable register to Service Monitor until you perform post-upgrade configuration steps; for more information, see Configuring Service Monitor After Upgrading.

To use Service Monitor to monitor MOS reported from Cisco Unified Communications Managers, you should configure the server to use NTP before you upgrade. For more information, see NTP Configuration Notes.

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

If you have Cisco Security Agent installed and running on your system, shut it down before upgrading Operations Manager. If you do not shut it down, you may receive a confirmation message during the upgrade, or the upgrade process may fail. (See the Release Notes for Cisco Unified Operations Manager on Cisco.com for more details.)

If an inventorybackup.xml file already exists in CSCOpx\objects\vhm\utilities directory before the Operations Manager 2.3 upgrade, rename the inventorybackup.xml file before you perform the upgrade.

To improve response times for the Fault History database, run disk defragmentation on the Operations Manager server machine before you install the release 2.3 software. The upgrade now allocates 2 GB of disk space to the database, and defragmenting the disk before the upgrade ensures faster response times.

(Optional) Planning for (and Running) Service Monitor Call Data Migration Before the Upgrade

Migrating call data is optional. However, to keep the data, you must migrate it before you start the upgrade to Operations Manager (includes Service Monitor) 2.3.


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 tool (QOVR_CMT.zip) and the readme file from this URL:

http://www.cisco.com/cgi-bin/tablebuild.pl/servmon


Note You will need to log in to Cisco.com.


Step 2 Extract the README_QOVR_CMT.TXT file and use the information in it to plan for and execute the migration.



Note Running the Call Migration Tool migrates only the Service Monitor call data. Service Monitor configuration data migrates automatically during the upgrade to Operations Manager (includes Service Monitor) 2.3. After you run the Call Migration Tool, do not run Service Monitor until you complete the upgrade to Operations Manager.


Upgrading to Operations Manager 2.3

The upgrade procedure takes approximately 45 to 90 minutes (depending on your existing database).


Note Sometimes the upgrade seems to stall. This happens when files are locked by some processes. You can do either of the following:

Re-try and wait for processes to release locked files.

Stop the upgrade and:

a. Use the process explorer to find the processes that are holding file handles under CSCOpx (NMSROOT).

b. Remove those processes manually and restart the upgrade.



Step 1 As the local administrator, log in to the machine on which you will be upgrading the Operations Manager software:

a. Ensure that you have completed a backup. (See Backing Up Data Before the Upgrade or Reinstallation.)

b. If an inventorybackup.xml file already exists in CSCOpx\objects\vhm\utilities directory before the Operations Manager 2.3 upgrade, rename the inventorybackup.xml file before you perform the upgrade.

Step 2 Insert the Cisco Unified Operations Manager CD-ROM into the CD-ROM drive. The Cisco Unified Operations Manager Setup Program window opens.


Note If the CD-ROM is already in the CD-ROM drive and you stopped the installation process to close programs or if Autostart is disabled, click Setup.exe to restart the process.


Step 3 Read any messages and acknowledge them to continue:

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 port conflict with IIS, click Yes. In a later step, you will be prompted to select an HTTPS port other than 443.

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

The Welcome window appears.

Step 4 Click Next. An upgrade warning appears.

Step 5 To save any Service Monitor report data that you have—and, if you have not run the Call Migration Tool—click No, exit, and run the Call Migration Tool to completion before you run the upgrade. Otherwise, click Yes.

The Software License Agreement window appears.

Step 6 Select the I accept the terms of the license agreement radio button and click Next. The Setup Type window appears.

Step 7 Select Typical or Custom. (The changes you can make during a Custom installation are listed under Step 9.) Click Next.

Step 8 The System Requirements window displays the results of the requirements check and advises whether the upgrade can continue; click Next.


Note If memory requirements are not met, installation cannot proceed. See Server Requirements, page 1-2.


Step 9 If you chose Typical installation, skip this step and proceed to Step 10. If you chose Custom Installation, do any of the following in the windows that appear:

Change the user admin password and guest password

Change the system identity account password

Change the casuser password

Change the Common Services database password

Change the HTTPS port, administrator e-mail, or SMTP server settings

Create a self-signed certificate

Click Next.

Step 10 The Summary window appears, displaying the current settings. Click Install. The installation proceeds.

Step 11 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.

Before database upgrade, the following message is displayed:

Rebuilding the database. Please wait. At most, for a 25GB database, it can take up to 
an hour. 

The following message might appear:

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.

(For more information, see NTP Configuration Notes.)

This message is displayed:

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

If Windows SNMP service is not installed on your system, a message will inform you of this fact.

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


Step 12 Remove the Cisco Unified Operations Manager CD from the drive.


Note Store the CD in a secure, climate-controlled area for safekeeping.


Step 13 Click Finish to reboot the machine.

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

Step 15 Verify the upgrade by starting Operations Manager.

Step 16 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 Device > Device Management > Modify/Delete Devices.

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

c. Click Rediscover.

Step 17 To restore the detailed device view configuration, run the restore utility after Step 16 completes. See Restoring Detailed Device View Configuration Data to Operations Manager 2.3. Be sure that discovery is complete before performing this step.


If any errors occur during installation, check the installation log in the root directory on the drive. (For example, the CiscoWorks Common Services installation might create C:\Ciscoworks_setup001.log, the Operations Manager installation might create C:\Ciscoworks_setup002.log, and so forth.) The Cisco Technical Assistance Center (TAC) might ask you to send them the installation log if you encounter problems.

Restoring Detailed Device View Configuration Data to Operations Manager 2.3

If you upgraded from a previous release of Operations Manager, you must restore the Detailed Device View data that you backed up before the upgrade or reinstallation using the restore utility.

The restore utility restores the managed states of nonsuspended devices in the Detailed Device View.

The utilities are located in CSCOpx\objects\vhm\utilities. To run the restore utility, open a DOS prompt and enter:

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

% CSCOpx\objects\vhm\utilities\inventoryRestore

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

For information on backing up your Detailed Device View after your upgrade and restore is complete, see the online help or User Guide for Cisco Unified Operations Manager 2.3.

Configuring Service Monitor After Upgrading

This section provides the minimum steps required to enable Cisco 1040 sensors to register with Service Monitor 2.2. 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 2.2.


Step 1 Start Service Monitor.

Step 2 Configure the default configuration file:

a. Select Configuration > Sensor > 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 To ensure that you use the most up-to-date image file, see Cisco Unified Service Monitor 2.2 Compatibility Matrix.


c. Click OK. Operations Manager 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 Quick Start Guide for Cisco Unified Service Monitor 2.2 on Cisco.com.


Note 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.



Reinstalling Operations Manager


Step 1 As the local administrator, log in to 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 Insert the Cisco Unified Operations Manager CD-ROM into the CD-ROM drive. The installer window appears, asking you if you want to reinstall Cisco Unified Operations Manager.


Note If the CD-ROM is already in the CD-ROM drive and you stopped the reinstallation process to close programs or if Autostart is disabled, click Setup.exe from the top directory of your CD-ROM to restart the process.


Step 5 Read any messages and acknowledge them to continue:

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.

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. Click Next.

Step 9 The System Requirements window displays the results of the requirements check and advises whether the reinstallation can continue; click Next.

Step 10 If you chose Typical installation, skip this step and proceed to Step 11. If you chose Custom installation, you will be asked to enter:

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

Security certificate information.

Data transport protocol.

Step 11 An information dialog box appears, confirming reinstallation; click OK.

The Summary window appears, displaying the current settings.

Step 12 Click Next. The installation proceeds.

Step 13 Remove the Cisco Unified Operations Manager CD from the drive.


Note Store the CD in a secure, climate-controlled area for safekeeping.


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.

Step 16 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 Device > Device Management > Modify/Delete Devices.

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

c. Click Rediscover.

Step 17 To restore the Detailed Device View configuration, run the restore utility after Step 16 completes. See Restoring Detailed Device View Configuration Data to Operations Manager 2.3. Be sure you have rediscovered your devices before completing this step.


If any errors occur during reinstallation, check the installation log in the root directory on the drive. (For example, the CiscoWorks Common Services installation might create C:\Ciscoworks_setup001.log, the Operations Manager installation might create C:\Ciscoworks_setup002.log, and so forth.) The Cisco Technical Assistance Center (TAC) might ask you to send them the installation log.

Uninstalling Operations Manager


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.

Step 3 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. 

You must click OK. (To cancel the uninstallation, you can click Cancel on the next window that appears.)

Step 4 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 5 Click Finish.


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. It is recommended 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:

1. Talk with your Cisco Unified Communications Manager administrators to determine the time server with which Service Monitor should synchronize. You might find 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.

2. Use your system documentation to configure NTP on the Windows Server 2003 system where Service Monitor will be installed. Configure NTP with the time server being used by Cisco Unified Communications Managers in your network. You might find 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 © 2009, Microsoft Corporation.