Installation Guide for Cisco Unified Operations Manager 1.1
Installing, Uninstalling, and Upgrading Cisco Unified Operations Manager
Downloads: This chapterpdf (PDF - 311.0KB) The complete bookPDF (PDF - 1.08MB) | 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 Devices for Addition to Operations Manager Inventory

Device Specific Configurations

Actions to Take Before Adding Devices

Adding Devices Notes

Verifying TCP and UDP Ports that Operations Manager Uses

Gathering Information to Provide During Installation

Performing a New Installation

Reinstalling Operations Manager

Uninstalling Operations Manager

Upgrading IP Communications Operations Manager 1.0 to Cisco Unified Operations Manager 1.1

Moving from IP Telephony Monitor 2.0 to Cisco Unified Operations Manager 1.1

Configuring Your System for SNMP Queries


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. It includes:

Preparing to Install Operations Manager

Performing a New Installation

Reinstalling Operations Manager

Uninstalling Operations Manager

Upgrading IP Communications Operations Manager 1.0 to Cisco Unified Operations Manager 1.1

Preparing to Install Operations Manager

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

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

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 Operations Manager, do the following:

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.

The drive that you choose to installation Operations Manager on must be a NTFS file system.

If you are using an IBM server with IBM director installed, you must stop the ibm director wmi cim server and change the service to manual, or disabled it. If you do not, the Service Level View in Operations Manager will not work.

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

Preparing Devices for Addition to Operations Manager Inventory

This section describes actions you must perform before adding devices to Operations Manager's 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.)

Review the notes for adding devices. (See Adding Devices Notes.)

Device Specific Configurations

Cisco CallManager:

Make sure that SNMP read access is configured on the Cisco CallManager system.

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

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

Cisco IP Contact Center and Cisco Unity:

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

WMI credentials, which is the Windows username and password, must be entered in the primary credential portion of the DCR screen.

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

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 the 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:\Program Files\CSCOpx.


Adding Devices Notes

The filtering fields (IP Address, DNS Domain, and SysLocation) in the Discovery page, are optional. The most effective way to add devices to Operations Manager's inventory, is to not use these filtering options.

If you use a ping sweep to add devices, use smaller subnets. Do not use ping sweep on a Class A or Class B address.

Seed devices must be running CDP.

If there are many SNMP unreachable devices in your network and you have to supply multiple device credentials (causing discovery to have to try one or more credentials on each device until it finds the correct credentials for the device), device discovery can take a long time.

This can be caused by the SNMP timeout setting. To fix this situation, you can lower the SNMP timeout and retries setting (default is 3 seconds with 2 retries).

Do the following:

1. Enter the credentials on the Default Credentials page.

2. Open the IPCDiscovery-config.xml file from <NMSROOT>\conf\discovery.

3. Locate the Credentials section. In this section, for each credential that you entered, you will find a section similar to the following:

<SnmpCredential IPAddress="*.*.*.*"> <SNMPv2 Snmpretry="2" Snmptimeout="3000" Usertag="SNMPv2 Credentials in first line" ROCommunity="/qiJe7XyxpU=" RWCommunity="Byh+1ukjK3I="/> </SnmpCredential>

Snmptimeout="3000" indicates that the timeout is 3000 milliseconds or 3 seconds.

4. You can lower this value to 1000 milliseconds or 1 second. You can choose a value based on the SNMP responsiveness in your network.

5. Save the changes that you made to the file.

6. Start discovery.


Note If you make any further modifications to the credential list from the Default Credentials page, you will need to verify the SNMP timeout values in the configuration file. They may have been overwritten.


Verifying TCP and UDP Ports that Operations Manager Uses

Before installing Operations Manager, make sure that the ports Operations Manager (and Service Monitor) use will only be used by the applications listed in Table 2-1 and Table 2-2.


Note If an existing NMS uses port 162, see Configuring SNMP Trap Receiving and Forwarding, for more information.


Operations Manager uses the following TCP and UDP ports.

Table 2-1 Ports that Operations Manager Uses 

Port Numbers
Service Name 
Applications

161

Simple Network Management Protocol (SNMP)

Common Services

162

Trap receiving (standard port)

Common Services

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

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

53

DNS

67 and 68

DHCP

69

TFTP—Service Monitor uses TFTP to find the configuration file for a given Cisco 1040

514

Syslog—Service Monitor receives syslog messages from Cisco 1040

2000

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

5667

Interprocess communication

43459

Database


Gathering Information to Provide During Installation

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


Note For more information on creating passwords, see the appendix "Password Information" in Installation and Setup Guide for Common Services (Includes CiscoView) on Windows.


User Admin password

System Identity Account password

Casuser password (custom installation only)

Guest password (custom installation only)

Common Services database password (custom installation only)

Web server information (custom installation only)

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.


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-hand corner of the window. The CiscoWorks home page opens. Under Common Services, select Server > Admin > Licensing.



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

Licensing Reminders


Performing a New Installation

The installation process takes approximately sixty 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 1.1. Only Cisco Unified Service Monitor can reside on the same server as Operations Manager.

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

If you want to monitor Operations Manager using a third-party SNMP management tool, see Configuring Your System for SNMP Queries.

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 with Internet Information Services (IIS) enabled.

A system that does not have name lookup.

Do not select an encrypted directory. Operations Manager does not support directory encryption.

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

Do not install on any of your voice application servers or on a Cisco CallManager server.

Verify that the system date and time are set properly.

To speed up installation, disable all virus-scan software while installing.

Your systems IP address and hostname should be set before installation.


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.

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 1.1 and Service Monitor 1.1 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 Click Install. The Welcome window appears.

Step 5 Click Next. The Software License Agreement window appears.

Step 6 Click Accept. The Licensing Information window appears.

Step 7 Select a radio button:

If you have a license file for Operations Manager, select the first radio button and browse to the location of the license file. Click Next.

If you do not have a license for Operations Manager, select the Evaluation Only radio button, and click Next.


Note For instructions on obtaining a license file, see Licensing Process.


The Setup Type window appears.

Step 8 Select Typical to install the complete Cisco Unified Operations Manager package, which contains Operations Manager 1.1 and Service Monitor 1.1.

If you choose the Typical installation mode, the system automatically provides the following information to the installation process:

Guest password

Common Services database password

Web server information

Self-signed certificate information

Username and password for data transport protocol authentication

Location where the Service Monitor call metrics data will be stored

Location where the Service Monitor probe image and configuration files will be stored

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.

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, the installation program displays an error message and stops.

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

Step 11 Click Next.

Step 12 Enter a User Admin password (and confirm), and click Next.


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.


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

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

The Summary window appears, displaying the current settings.

Step 15 Click Next. The installation proceeds.

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

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

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

Step 17 Eject the CD-ROM.


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


Step 18 Click Finish to reboot the machine.

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

Step 20 You can verify that the Operations Manager process is running from the Common Services Process Management page. From the Operations Manager home page, click CiscoWorks in the upper right-hand corner of the window. The CiscoWorks home page opens. Under Common Services, select Server  >  Admin >  Processes.

Step 21 To use Operations Manager, from the Windows desktop select Start > All Programs > Cisco Unified Operations Manager 1.1 and Service Monitor 1.1 > Cisco Unified Operations Manager 1.1 and Service Monitor 1.1.


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



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.

Reinstalling Operations Manager


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

Step 2 As the local administrator, log in to the machine on which you will install the Cisco Unified Operations Manager software, and 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 3 Click Install. The Welcome window appears.

Step 4 Click Next. The Software License Agreement window appears.

Step 5 Click Accept. The Setup Type window appears.

Step 6 Select Typical or Custom.

Step 7 Click Next. The Backup Data window appears.

Step 8 Enter or browse to the location where you want the backup of your previous version of Operations Manager stored, and 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 Custom installation you will be asked to enter the following:

Casuser password

Username and password for data transport protocol authentication

Location where the Service Monitor call metrics data will be stored

Location where the Service Monitor probe image and configuration files will be stored

This step is not required for Typical installation. Click Next.

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-ROM from the drive.


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


Step 14 Click Finish to reboot the machine.

Step 15 To verify that the Operations Manager Server process is running, log in to the CiscoWorks home page as the administrator and select Common Services > Server  > Admin >  Processes.

Step 16 To use Operations Manager, from the Windows desktop select Start > Programs > Cisco Unified Operations Manager 1.1 and Service Monitor 1.1 > Cisco Unified Operations Manager 1.1 and Service Monitor 1.1.


If any errors occurred 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.


Note Before uninstalling, be sure to delete 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 each test's respective configuration page (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 To start the uninstallation process, from the Windows desktop select Start > All Programs > Cisco Unified Operations Manager 1.1 and Service Monitor 1.1 > Uninstall Cisco Unified Operations Manager 1.1 and Service Monitor 1.1.

Step 3 Select the components you want to uninstall.

Step 4 Click Next to begin uninstalling the selected components.

A window appears, listing the components selected for uninstallation.

Step 5 Click Next.

Messages showing the progress of the uninstallation appear.

The following message appears:

Uninstallation is complete. Click OK to finish.

Step 6 Click OK.


Upgrading IP Communications Operations Manager 1.0 to Cisco Unified Operations Manager 1.1

Supported upgrade paths:

Upgrade from a licensed copy of IP Communications Operations Manager 1.0 to a licensed copy of Cisco Unified Operations Manager 1.1.

Upgrade from a licensed copy of IP Communications Operations Manager 1.0 to an evaluation copy of Cisco Unified Operations Manager 1.1


Note You cannot upgrade from an evaluation copy of IP Communications Operations Manager 1.0 to an evaluation copy of Cisco Unified Operations Manager 1.1.


If you want to upgrade from IP Telephony Monitor 2.0, see Moving from IP Telephony Monitor 2.0 to Cisco Unified Operations Manager 1.1.


Note Synthetic test settings are not migrated from IP Communications Operations Manager 1.0 to Cisco Unified Operations Manager 1.1. After upgrade, you will have to recreate any synthetic tests that you previously created in Operations Manager 1.0.


Before You Begin

Make sure your system meets the system requirements (see Server Requirements).

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

If Operations Manager 1.0 has been running for a long period of time and has accumulated a large amount of data (database over 1 GB), you should run an independent backup before upgrading. Also, during installation, do not run the backup data process. You can use Windows Explore to view the database size (Operations Manager's databases are located in the <NMSROOT>\databases folder).


Note NMSROOT is the folder where Operations Manager is installed on the server. If you selected the default directory during installation, it is C:\Program Files\CSCOpx.



Step 1 As the local administrator, log in to the machine on which you will be upgrading the Operations Manager software, and insert the Cisco Unified Operations Manager CD-ROM into the CD-ROM drive. The Cisco Unified Operations Manager 1.1 and Service Monitor 1.1 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 2 Click Install. The Welcome window appears.

Step 3 Click Next. The Software License Agreement window appears.

Step 4 Click Accept. The Licensing Information window appears.

Step 5 Select a radio button:

If you know the location of the license file for Operations Manager, select the first radio button and browse to the location of the license file. Click Next.

If you do not have a license for Operations Manager, select the Evaluation Only radio button, and click Next.


Note For instructions on obtaining a license file, see Licensing Process.


The Setup Type window appears.

Step 6 Select Typical or Custom.

Step 7 Click Next. The Backup Data window appears.

Step 8 Enter or browse to the location where you want the backup of your previous version of Operations Manager stored.

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

Step 10 If you chose Custom installation, you will be asked to enter the following:

casuser password

Username and password for data transport protocol authentication

Location where the Service Monitor call metrics data will be stored

Location where the Service Monitor probe image and configuration files will be stored

This step is not required for Typical installation. Click Next.

Step 11 An information dialog box appears, confirming upgrade; 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-ROM from the drive.


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


Step 14 Click Finish to reboot the machine.

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

Step 16 To verify that the Operations Manager Server process is running, log in to the CiscoWorks home page as the administrator and select Common Services > Server  > Admin >  Processes.

Step 17 To make sure all existing devices go to the monitored state, Operations Manager must perform rediscovery. Do the following:

a. In Operations Manager, select Device > Device Management > View/Rediscover/Delete.

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

c. Click Rediscover.


Note During upgrade, the Voice Utilization polling settings are carried over from IP Communications Operations Manager 1.0 to Cisco Unified Operations Manager 1.1.

If you encounter problems when launching performance graphs, do the following:

1. From a command prompt run the following command:

- pdshow InventoryCollector. 

This verifies that the Inventory Collector server is running.

2. If the server is not running, run the following command:

- pdexec InventoryCollector. 

3. In Operations Manager Polling and Thresholds, change any priority settings.

4. Click Apply Changes.


Step 18 Recreate any synthetic tests that you previously created in Operations Manager 1.0.


Note Synthetic test settings are not migrated from IP Communications Operations Manager 1.0 to Cisco Unified Operations Manager 1.1. After upgrade, you will have to recreate your synthetic tests.



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.

Moving from IP Telephony Monitor 2.0 to Cisco Unified Operations Manager 1.1

There is no upgrade from IP Telephony Monitor 2.0 to Cisco Unified Operations Manager 1.1. If you are moving from IP Telephony Monitor, you must first uninstall it before installing Operations Manager.

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.


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.