Table Of Contents
Installing and Uninstalling IP Communications Operations Manager
Preparing to Install Operations Manager
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
Configuring Your System for SNMP Queries
Installing and Uninstalling IP Communications Operations Manager
This chapter describes installing IP Communications Operations Manager (with IP Communications Service Monitor) on a Windows system. It includes:
•
Preparing to Install Operations Manager
•Performing a New Installation
•Reinstalling Operations Manager
•Uninstalling Operations Manager
Preparing to Install Operations Manager
The information that follows helps you to perform the following tasks before you install IP Communications Operations Manager (Operations Manager):
•Ensure that hardware and software requirements for the server are met. (See Server Requirements.)
•Determine whether your existing applications are already using ports that Operations Manager or IP Communications Service Monitor (Service Monitor) uses. (Existing applications should not use the ports that Operations Manager or Service Monitor use.)
•Gather information that you might need to provide during the Operations Manager installation.
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
Protocol
|
Port Numbers
|
Service Name
|
Applications
|
UDP
|
161
|
Simple Network Management Protocol (SNMP)
|
Common Services
|
162
|
Trap receiving (standard port)
|
Common Services
|
9000
|
Trap receiving
CSListener (Operations Manager server if port 162 is occupied)
|
Operations Manager
|
TCP
|
9002
|
DynamID authentication
(Operations ManagerBroker)
|
Operations Manager
|
15000
|
Log server
|
Operations Manager
|
43445
|
itemFh
Fault History database
|
Operations Manager
|
43446
|
itemInv
Inventory service database
|
Operations Manager
|
43447
|
itemEpm
Event promulgation module database
|
Operations Manager
|
43500-43520
|
CSTM
|
Operations Manager
|
Table 2-2 Ports that Service Monitor Uses
Protocol
|
Port Numbers
|
Service Name
|
UDP
|
53
|
DNS
|
UDP
|
67 and 68
|
DHCP
|
UDP
|
69
|
TFTP—Service Monitor uses TFTP to find the configuration file for a given Cisco 1040
|
UDP
|
514
|
Syslog—Service Monitor receives syslog messages from Cisco 1040
|
TCP
|
2000
|
SCCP—Service Monitor uses SCCP to communicate with Cisco 1040s
|
TCP
|
43459
|
Database
|
Gathering Information to Provide During Installation
You might need to supply the following information while you are installing Operations Manager:
•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)
For more information on creating passwords, see the appendix "Password Information" in Installation and Setup Guide for Common Services (Includes CiscoView) on Windows.
•License information—The installation script prompts you to enter one of the following:
–Information that you will find printed on the software claim certificate—Product Authorization Key (PAK).
–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 IP Communications Operations Manager; see Obtaining and Installing Your License File.
Note You can determine the status of your license from the CiscoWorks home page, by selecting Common Services > Server > Admin > Licensing.
Note If you are installing Operations Manager for evaluation purposes:
•You do not need to supply a license file or a PAK.
•You might be interested in the following information:
–Upgrading Your Evaluation License
–Licensing Reminders
Performing a New Installation
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 CiscoWorks applications other than those that are documented to be able to coexist with Operations Manager 1.0.
•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.
•Verify the system date and time is set properly.
•To speed up installation, disable all virus scan software while installing.
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 IP Communications Operations Manager CD-ROM into the CD-ROM drive. The IPC Operations Manager 1.0 and Service Monitor 1.0 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 one of these radio buttons, enter any required information, and click Next.
•License File Location—For instructions on obtaining a license file, see Obtaining and Installing Your License File.
•Evaluation Only
Note Do not select the PAK and PIN radio button. A PIN is not provided for Operations Manager.
The Setup Type window appears.
Step 8 Select Typical to install the complete IP Communications Operations Manager package, which contains Operations Manager 1.0, Common Services 3.0 with Service Pack 1, and Service Monitor 1.0.
If you choose the Typical installation mode, the following information will be supplied for you:
•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 an error 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 To verify that the Operations Manager process is running, log in to the CiscoWorks home page as the administrator and select Common Services > Server > Admin > Processes.
Step 20 To use Operations Manager, from the Windows desktop select Start > All Programs > IPC Operations Manager 1.0 and Service Monitor 1.0 > IPC Operations Manager 1.0 and Service Monitor 1.0.
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 IP Communications 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 IP Communications Operations Manager software, and insert the IP Communications Operations Manager CD-ROM into the CD-ROM drive. The installer window appears, asking you if you want to reinstall IP Communications 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 protocal 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 IP Communications 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 > IPC Operations Manager 1.0 and Service Monitor 1.0 > IPC Operations Manager 1.0 and Service Monitor 1.0.
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 CiscoWorks 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 tests respective configuration page (see the IP Communications Operations Manager online help for information on deleting each test).
Step 1 As the local administrator, log in to the system on which IP Communications Operations Manager is installed.
Step 2 To start the uninstallation process, from the Windows desktop select Start > All Programs > IPC Operations Manager 1.0 and Service Monitor 1.0 > Uninstall IPC Operations Manager 1.0 and Service Monitor 1.0.
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.
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.
You can install Windows SNMP service before or after 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.
