Table Of Contents
Release Notes for Cisco Unified Operations Manager 2.2
Published: August, 2009 OL-19472-03Revised: April 19, 2010
This document contain the following topics:
Cisco Unified Operations Manager 2.2 includes the following new features:
Major new features include:
•Incremental support for Cisco Unified Communications family of products and other new devices.
•Support for 45,000 phones in a single instance of Operations Manager on a single server in a nonvirtual environment.
•Virtualization support for VMware ESX 3.5:
–Support for a single virtual instance of Operations Manager scaling up to 30,000 phones deployed on a single VMWare ESX server.
–Support for a single instance of each of these products:
Service Statistics Manager
each in a separate virtual machine, each supporting up to 10,000 phones.
–Support for three virtual instances of Operations Manager, each scaling up to 5,000 phones deployed on a single VMWare ESX server.
•The following new tools are provided:
–Health Monitoring—Monitors and provides status of Operations Manager processes.
–DB Reload Utility—Enables database defragmentation.
Note A Cisco Unified Operations Manager - Bandwidth Estimator tool is also newly available from the Tool Index page: www.cisco.com/en/US/products/prod_tools_index.html.
For more information, User Guide for Cisco Unified Operations Manager.
•Improved events with more intuitive descriptions, attribute enhancements, recommended actions, and detailed descriptions of each event.
Suppression of event has been added to enable a user to suppress specific events from specific components.
For a list of supported events, see Table E-1 in the "Events Processed" appendix of the User Guide for Cisco Unified Operations Manager. For a list of deprecated events that have been removed to improve Operations Manager performance, see Table E-2 in the "Events Processed" appendix of the User Guide for Cisco Unified Operations Manager.
•Additional documentation available on Cisco.com:
–Best practices for managing voice applications.
–Frequently Asked Questions.
–Best practices for managing various Unified Communication components including Communications Manager, Unity, Contact Center, Communications Manager Express, Unity Express, Gatekeeper, SRST-enabled routers, Voice Gateways, and other voice applications.
•Auto-discovery improvements that speed the discovery process by allowing various options such as:
–An Advanced Filters page expands the filter settings for more complex filtering.
•Service Level View enhancements and updates:
–Removal of the Service Impact report and user-defined map view. Service Level View cannot be enabled when creating groups.
–Manage Views no longer allows you the option to manage Service Level View.
–Display of port information is improved; a separate popup provides all information and is scrollable.
–Zooming functionality is improved.
–Font readability is improved
–Ability to hide or view the device name label by IP address or DNS.
–Removal of printer-friendly view to avoid performance issues.
•Improved phone and device count data. Phone test can now be selected from Diagnostics tab.
•Improved performance details on trunk utilization for individual trunk. Updates now display this information in Detailed Device View and performance graphing.
•Personalized report allows a maximum 5,000-record selection per user.
•Web Services API mechanism to remotely acknowledge or clear an alert or event from its database.
•Support for a coresident server with Operations Manager, Service Statistics Manager, and Service Monitor which scales to support 10,000 phones.
See Table 3 for problems that are resolved in this release.
System requirements are documented in the Installation Guide for Cisco Unified Operations Manager 2.2. For documentation updates after publication, see Documentation Updates.
Upgrade paths that were tested and are supported:
•Operations Manager, release 2.0.3 to 2.2
•Operations Manager, release 2.1 to 2.2
•Operations Manager, release 2.1 SP1 (2.1.1) to 2.2
There is no direct upgrade from Operations Manager releases prior to 2.0.3 to Operations Manager 2.2. If you are running:
•Operations Manager 2.0.2, first upgrade to Operations Manager 2.0.3.
•Operations Manager 2.0 or 2.0.1, first upgrade to Operations Manager 2.1.
The following paths for releases prior to 2.0 are recommended:
•Operations Manager, release 1.0 to 1.1, then to 2.0, 2.1, and 2.2.
•Operations Manager, release 1.1 to 2.0, then to 2.1 and 2.2
For complete details on installation and upgrade procedures, see the Installation Guide for Cisco Unified Operations Manager 2.2.
Note Some known problems in Service Monitor have been resolved. If you run Service Monitor on the server with Operations Manager, you should review the Resolved Problems section and the Release Notes for Cisco Unified Service Monitor 2.2 before you install Operations Manager.
This section includes the following important notes:
Known IBM Server Problem
For IBM servers, the temperature sensor value in the Detailed Device View (DDV) may display as -1. The -1 should be interpreted as follows:
•The SNMP Agent software has not been properly integrated, or
•The vendor has not implemented the object ID (OID).
There is no workaround.
Requirements for Operations Manager
The software that you already have on the server may affect Operations Manager. Be sure to check the server and client requirements; see the Installation Guide for Cisco Unified Operations Manager 2.2.
Memory Usage for Multiple Phone Reports
Depending on the number of records reports, the system can only handle a certain number of large reports kept open at the same time. When a report is closed, the window task manager may not show Tomcat memory usage decreasing right away, but it will free up memory for new report to be opened. We recommend you close phone reports after you are finished with them to ensure system performance is not degraded.
Table 1 describes the installation or upgrade, backup and restore, and other setup problems known to exist in this release.
Table 2 describes other known problems that exist in this release.
Table 1 Known Problems with Installation, Upgrade, Backup, Restore, and Setup in Operations Manager
Bug ID Summary Explanation
Product Security: VTP-VUL-SCAN
Immediately following installation, the TCP/IP stack should be hardened to avoid denial of service attacks. These type of attacks may occur when using Nessus (a vulnerability scan tool that performs network and system vulnerability assessments). Ensure the footnote steps listed in Table 1-1 of the Installation Guide for Cisco Unified Operations Manager are taken before you use Operations Manager.
Even after performing the hardening steps on the Operations Manager server, the following problems may still occur with these Nessus IDs:
•For port 1741: Nessus ID 10930: Has the following common vulnerabilities and exposures (CVE): CVE-2001-0386, CVE-2001-0493, CVE-2001-0391, CVE-2001-0558, CVE-2002-0200, CVE-2000-0168, CVE-2003-0016, and CVE-2001-0602 which may occasionally cause an Apache child process to halt abruptly, but the system recovers automatically without intervention when Apache starts a new child process.
•For port 139: Nessus ID 10204: Has the following CVE: CVE-1999-0980: An existing vulnerability on Windows NT 4.0 may cause the services.exe to halt abruptly. However, this was not seen during testing but may occur.
Every audit check done by Nessus is implemented as a plugin and is identified by a plugin ID. The list of Nessus plugin IDs can be viewed at http://www.nessus.org/plugins/index.php?view=all and can be searched for at http://www.nessus.org/plugins/index.php?view=search.
Associated with each plugin is a list of CVEs. CVEs are maintained in the National Vulnerability Database (http://cve.mitre.org/cve/) and can be searched for by their identifiers here (http://cve.mitre.org/cve/cve.html). For example, "Nessus ID 10930 CVE-2001-0386" indicates a plugin ID of 10930 with a CVE identifier of CVE-2001-0386.
Large performance:Backup user interface times out if the page is open for more than an hour.
Backup user interface times out if the page is open for more than one hour. This happens when the data to be backed up is huge.
Workaround: Even though the user interface times out, the backup process is actually running on the server. Check the backup directory and backup log to determine the status.
Table 2 Known Problems in Operations Manager
Bug ID Summary Explanation
Service quality events showing up in Alerts and Events View.
If the same device has both device and service quality events, then service quality events display in the Alerts and Events view.
Workaround: Check for service quality events in Service Quality Fault History for that device.
Further Problem Description: If a device receives device events followed by Service Quality events, the latest event category in Alerts and Events display displays as QOV. The Alert Detail view for that alert shows both Service Quality and device events. If a device receives Service quality events followed device events, the alert will not be visible in the Service Quality Alert Display.
Large deployment FHServer OutOfMemory error
OutOfMemory error appears in the FHServer logfile because the database grows large quickly and can become fragmented. Symptoms include slow Alert History queries or issues in restarting the FHDbEngine Server.
Workaround—If the database size grows due to some unknown reason, this utility can be used to unload and reload all Operations Manager databases:
1. Make sure the system uses the perl utility that is supplied with Operations Manage under this directory: <NMSROOT>\objects\perl5\bin
NMSROOT is the directory where you installed Operations Manager. If you used the default installation directory, NMSROOT is C:\Program Files\CSCOpx.
2. Delete any reload.sql files left from any previous reload activity from the database directories.
3. Run this perl script: <NMSROOT>/conf/itemDb/bin/dbreload.pl.
After you invoke the utility, command line options walk you through the steps. This utility reloads all Operations Manager databases given the password. If you do not know the database password, the utility prompts for a new database password, resets it on all the databases, and then executes the reload.
Note Consider running this utility as a preventive measure when the Alert History database size grows beyond 2 GB or when Alert History queries run slowly.
Nonpaged pool kernel memory is increasing
Workaround - Apply the Windows hot fix available at http://support.microsoft.com/kb/931311. Reboot the system. Nonpaged pool kernel memory should be stabilized.
Flash memory instability can occur in SLV client during burst events
The Service Level View client can become unresponsive and may start sending messages after triggering 700 to 2,000 device unresponsive burst events. This may be caused by a network connectivity issue to Operations Manager. Internet Explorer may crash in this situation.
When large number of devices become unresponsive at the same time, a multitude of events are generated and the changes are pushed to the SLV client. This causes memory instability in the Flash module in Internet Explorer and display the following error dialog: "A script in this movie is causing Adobe Flash player 9 to run slowly. If it continues to run your computer may become unresponsive. Do you want to abort the script?"
Workaround: Close all existing Service Level View clients and start a new client after the burst events have stopped. Any client which hangs should be closed and relaunched.
Fault History report contains invalid event ID.
Some event ID numbers may display incorrectly when the Alert and Event History Report is displayed in an Excel spreadsheet. This occurs if the event ID contains certain numbers. The wrong format is a result of an Excel limitation which displays numbers such as 00003E8 as 3.00E+08.
Workaround: Open the report in a text reader such as Notepad or Wordpad, which will show the right event ID.
RPC communication is still on between Operations Manager and Cisco Unity device even though the device is not managed.
RPC keep alive packets are exchanged between Unity devices and Operations Manager server even after the devices are deleted from the server. For example, the Unity server was managed byOperations Manager, then deleted later but RPC packet continue to be exchanged.
This happens when the Cisco Unity device status is initially marked Fully Managed in Operations Manager but later the device is deleted from Operations Manager.
Workaround: Restarting daemon manager resolves this issue.
1. Stop the CiscoWorks daemon manager by entering net stop crmdmgtd.
2. Wait 1 to 15 minutes for the daemon to stop.
3. Start the Ciscoworks daemon manager by entering: net start crmdmgtd.
Operations Manager cannot monitor Extension Mobility enabled phones.
Some of the Extension Mobility phones are missing in the Operations Manager Phone report. Extension mobility phones exist in the network.
Operations Manager currently doesn't support Extension Mobility Phones in Unified Communications Manager due to lack of MIB instrumentation in Unified Communications Manager.
IPIU Phone count reduced to 0.
Phone count in the system becomes 0 when phone major discoveries schedules are deleted and there is no major discovery scheduled for the entire day.
Workaround: Need to have at least one major discovery cycle of major discovery scheduled in a day. To avoid this issue, do not delete any of the default schedules.
Operations Manager does not support more than two page files on the system.
Inventory Collection is stuck at 10% and the brcontrol execution gets stuck with high CPU consumption. This is a limitation of the Operations Manager due to the SMART server.
This occurs when the system has more than two page files.
Workaround: Do not use more than two page files on the operating system.
SIP-based CME is not discovered as CME nor is it displayed as CME in the Service Level View.
This problem is related to CSCso92226; CCMEEnabled is not set to true for SIP Communications Manager Express.
Workaround: Create a dummy "telephony config" on the CME device and then discover it in Operations Manager. Use the "telephony-service" command in config mode to enable skinny- based CME on the gateway.
OM credential change disrupts Service Statistics Manager functioning
If Service Statistics Manager is installed in your network and uses the Operations Manager admin user password to perform discovery, changing the admin user password causes problems. Users can no longer log into Service Statistics Manager; Service Statistics Manager can no longer verify licensing.
Workaround: Change the Operations Manager password for the admin user to the original password that Service Statistics Manager used to discover Operations Manager. For more information, see Release Notes for Cisco Unified Service Statistics Manager 1.2.
ErrCode 10 displayed for NAM properties
This can happen when you drill down from a Service Quality Alerts Display to an Event ID page and click a NAM Call Details link If the event occurred longer than 3 days ago, ErrCode = 10 is displayed.
NAM call details are only available for 3 days.
Workaround: Close the error window.
Operations Manager does not recognize gateways as MGCp devices when dial control is not needed.
You cannot create performance graphs in Operations Manager for Media Gateway Control Protocol (MGCP) voice gateways. The performance graphing option does not appear in the right-click menu in the Service Level View for the device.
This occurs when the device is configured using the new MGCP configuration, for example with PRI Backhaul or SS7 Signaling where dial peers do not need to be configured.
Workaround: Upgrade the gateway to Cisco IOS version 12.4(17a) or higher, then rediscover the device in Operations Manager.
SRST operations link does not open.
The SRST page and the Service Level View may not open.
Restart the appropriate service:
•For the SRST page, restart the SRSTServer service.
•For the Service Level View, restart the Inventory Collector.
In the Detailed Device View for negative synthetic tests, the success criterion for end-to-end calls and phone registration always shows availability as 100 percent.
In the Detailed Device View for negative tests, the availability is displayed as 100 percent and failure as 0 percent. These two settings are not applicable to the negative synthetic tests. The Detailed Device View should display N/A for this field.
Detailed Device View for Cisco Unity devices displays incorrect information.
For Cisco Unity releases prior to 4.2, the Detailed Device View shows the following:
•Current Number Of Licensed Subscribers as Not Available.
•Maximum Number of Licensed Subscribers as Not Available.
•Current Number of Inbox Licenses as Not Available.
•Maximum Number of Inbox Licenses as Not Available.
•Even though Cisco Unity 4.0(4) is upgraded to 4.0(5), the version on all services is still shown as 4.0(4).
Workaround: Upgrade to Cisco Unity 4.2, then run RSK Configuration Wizard.
Note This workaround applies only to the Cisco Unity service version issue. The workaround does not fix the first four counter issues mentioned above. There is no workaround for those issues.
Unreachable devices are displayed in Operations Manager device management.
If the SNMP agent on a device is working intermittently, Operations Manager may discover the device, but may move it to the unreachable state during inventory collection.
This occurs because the device was responding to SNMP queries during automatic discovery, then did not respond to SNMP queries during inventory collection.
The Devices report may show a device's capability as UnknownMDFType.
The Devices report displays a device's capability as UnknownMDFType when the device is not supported by Operations Manager.
The DFMServer and VHMServer processes are not registering with the broker.
Devices that are added to Operations Manager when it is in this condition exhibit the following behavior:
•ALL devices become stuck in the Inventory Collection in Progress state.
•All devices move to the unreachable state.
After installing Operations Manager and rebooting the server, either the DFMServer, or the VHMServer, or both processes do not start. There is no sm_server.exe instance (or there are only two sm_server.exe instances) in the Windows task manager.
Workaround: Perform the following:
1. Run net stop crmdmgtd.
2. Wait 15 minutes.
3. Run net start crmdmgtd.
After the CPU cools down, check the Windows task manager. There should be four instances of sm_server.exe.
The output of the brcontrol command should show both DFM and VHM.
Broker is located at: IPCOM-daily:9002 Started: Jan 06 10:21:09 2006
Domain Host Name Port Proc ID State Last Chg Time
------ --------- ------ ------- ----- -------------
DFM IPCOM-daily.cisco.com 2163 14120 RUNNING Jan 06 16:18:03 2006
VHM IPCOM-daily.cisco.com 2206 8856 RUNNING Jan 06 16:18:04 2006
Next Discovery, in the Device Management: Summary page, displays the incorrect time.
The problem is due to a registry setting in Windows that appears for certain time zones for which Daylight Saving Time changes are applicable. If the check box for Daylight Saving Time is not checked, problems occur when converting valid date strings to a Date object. This registry key remains even if the time zone of the machine is switched to another time zone for which Daylight Saving Time is not applicable.
Following is the registry information:
DisableAutoDaylightTimeSet REG_DWORD 0x00000001(1)
Workaround: If the system is in a time zone that has Daylight Saving Time, check the Automatically adjust for Daylight Saving Time changes check box.
If the system is in a time zone for which Daylight Saving Time is not applicable, but the registry key is present and set to 1, do the following:
1. Change to a time zone for which Daylight Saving Time is applicable.
2. Check the Automatically adjust for Daylight Saving Time changes check box, and click Apply.
This will cause the registry key to disappear. Now switch the machine to its present time zone.
On the Alert Details page, once a tool is launched, you cannot relaunch it.
In the Alert Details page, once you select a tool from the Launch Tools menu you cannot launch the selected tool again until you choose another tool.
Workaround: After launching a tool, to launch the same tool again, you must either select a different tool or select the Launch Tools option in the menu.
After doing either of these actions, you can relaunch your original choice.
An error occurs when you launch a trending graph for a device when the time of the graph is configured for more than 48 minutes in the past.
The error states that there is not any data available for the last 48 minutes. This error occurs due to an incorrect system uptime in the device.
This error occurs in specific Cisco IOS versions. Refer to the Cisco IOS IP SLA bugs, CSCin66315 and CSCeb46870.
Workaround: Upgrade the Cisco IOS version, or reboot the source device. For details, see CSCin66315 and CSCeb46870.
Cluster name changes are not reflected in Operations Manager.
If you change the name of a cluster in Cisco Unified CallManager after the devices have been added to Operations Manager, the name change does not occur in Operations Manager. This is the case even after performing inventory collection.
Workaround: Delete the devices in the cluster from Operations Manager and then add the devices in again.
The following software problems were resolved in Operations Manager 2.2. For information on bugs that are not included below, see the Cisco Software Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/home.pl.
Note Service Monitor Build ID NT_SM2_2_20090925_1028 resolves known problems in Service Monitor and is included with Operations Manager Build ID NT_OM22CS32_20090930_1223. For more information, see Release Notes for Cisco Unified Service Monitor 2.2, and Finding the Build ID for an Installed Operations Manager or Service Monitor (New Topic) to determine if you must reinstall Operations Manager.
Table 3 describes problems that were fixed in this release.
Table 3 Problems Resolved in Operations Manager 2.2
Bug ID Summary
Operations Manager with BUILD ID NT_CUOM2_2_CS32_20090715_1306 was removed from Cisco.com and republished with software fixes.
If you have Operations Manager 2.2 installed with the BUILD ID above, the workaround is to download the latest version (Operations Manager with BUILD ID NT_OM22CS32_20090930_1223) from the Cisco.com software download center and reinstall. Perform a rediscovery of your devices after reinstallation. See the Installation Guide for Cisco Unified Operations Manager for the reinstall procedures. You should also review the documentation updates for Chapter 2, Installing, Uninstalling, and Upgrading Cisco Unified Operations Manager before proceeding.
UserCleared and Acknowledged updates don't show on the user interface immediately.
Dashboards hang during device rediscovery.
After manually clearing alert AAD shows old age for new event
Auto Discovery hangs, no transition to Inventory Collection.
Selecting Location in Performance no longer shows error.
Operations Manager no longer generates CTILinkDown active/clear event pair when CTI mgr is up.
ICTs, GWs and SIP applications are shown in the SLV Map irrespective of RL/RG config.
Out of Memory error and major discovery issue has been resolved.
The documentation included with the product was missing. Where possible these updates have been made in the documents on Cisco.com. Any omissions not included in the documentation are noted below.
The following omissions occurred in the Installation Guide:
•Chapter 2, Installing, Uninstalling, and Upgrading Cisco Unified Operations Manager (appears corrected on Cisco.com)
•Prerequisites Chapter, Table 1-1, Installation Server System Minimum Requirements for Operations Manager (only appears in this release note)
Chapter 2, Installing, Uninstalling, and Upgrading Cisco Unified Operations Manager
Addition to the Reinstalling Operations Manager Topic
Before you reinstall Operations Manager, you must stop the Health Monitor service.
Additional Note for Installing Operations Manager
If you are installing Operations Manager using a executable that you obtained through the Download Software page on Cisco.com:
1. To start the installation, re-installation, or upgrade, double-click the executable file.
2. Follow the online prompts. For more information, see Installation Guide for Cisco Unified Operations Manager 2.2 (Includes Service Monitor 2.2).
The following correction appears only in the 2.2 Release Notes.
Prerequisites Chapter, Table 1-1, Installation Server System Minimum Requirements for Operations Manager
Footnote #6 in the table has been updated as follows:
Immediately following installation, the TCP/IP stack should be hardened to avoid denial of service attacks. Ensure these steps are taken before product use.
•Apply Windows security patches. See Microsoft Security Updates for Denial of Service Attacks for details. The system that you use for your Operations Manager server should meet all the security guidelines that Microsoft recommends for Windows 2003 Server. See the NSA website for security guidance: http://www.nsa.gov/ia/guidance/security_configuration_guides/operating_systems.shtml#microsoft. (Specifically, the TCP/IP stack should be hardened to avoid denial of service attacks.) See "Security Consideration for Network Attacks", page 103 in "The Windows Server 2003 - Security Guide, v2.1" for download from this NSA URL.
•Apply Common Services patches. Common Services has released OpenSSL security patch for TLS/SSL renegotiation vulnerability (CSCtd01597) on Cisco.com. The patch can be downloaded from the following URL: http://tools.cisco.com/support/downloads/go/Redirect.x?mdfid=276698858.
•Perform a procedure on their Windows Server 2003 Standard/Enterprise Edition to block remote access to all TCP/UDP ports except for those ports used by Operations Manager required for external access. See Operations Manager Firewall Updates to Avoid Denial of Service Attacks.
For details about Nessus vulnerability scan issues that may occur even after performing these steps, see CSCsy83005.
Corrections have been made in these sections:
Appendix E, Events Processed
The suppressedevent.bat filename does not match the actual filename on the disk which is supressedevent.bat.
Chapter 20, Administering Operations Manager
Corrections to the Backup and Restore Information
This procedure backs up the databases for Common Services and Operations Manager. It does not back up:
•The state of components in the Detailed Device View (DDV)—You must back them up using Backing Up and Restoring Detailed Device View Configurations Using Operations Manager Utilities.
•The database for Service Monitor—You must back up the Service Monitor database manually; see User Guide for Cisco Unified Service Monitor.
Finding the Build ID for an Installed Operations Manager or Service Monitor (New Topic)
Occasionally for troubleshooting purposes, you might need to know which build of Operations Manager or Service Monitor is installed. You can find the build ID as follows:
1. Click CiscoWorks from the upper-right corner on the Operations Manager home page. A new window opens.
2. Select Software Center > Software Update under Common Services. A new window opens.
3. Click the appropriate link (Cisco Unified Operations Manager n.n or Cisco Unified Service Monitor n.n, where n.n is the software release number) under Products Installed. A new window opens.
4. See the value labeled "Build Id" at the top of the page; for example, Build Id: NT_OM22CS32_20090930_1223.
Note NT_OM22CS32_20090930_1223 is an example that illustrates the build ID format.
Note The originally published printed and electronic documentation is included with your product. Any changes after original publication are reflected on Cisco.com, where you will find the most up-to-date documentation. Table 4 describes the product documentation that is available.
Table 4 Product Documentation
Document Title Available Formats
Supported Devices Table for Cisco Unified Operations Manager 2.2
On Cisco.com at the following URL: http://www.cisco.com/en/US/products/ps6535/products_device_support_tables_list.html
Release Notes for Cisco Unified Operations Manager 2.2
•In PDF on the product CD-ROM
•On Cisco.com at the following URL: http://www.cisco.com/en/US/products/ps6535/prod_release_notes_list.html
Installation Guide for Cisco Unified Operations Manager 2.2
•In PDF on the product CD-ROM
•On Cisco.com at the following URL: http://www.cisco.com/en/US/products/ps6535/prod_installation_guides_list.html
User Guide for Cisco Unified Operations Manager 2.2
•In PDF on the product CD-ROM
•On Cisco.com at the following URL: http://www.cisco.com/en/US/products/ps6535/products_user_guide_list.html
Context-sensitive online help
•Select an option from the navigation tree, then click Help
•Click the Help button on the page
Note We sometimes update the printed and electronic documentation after original publication. Therefore, you should also review the documentation on Cisco.com for any updates.
Table 5 describes the additional documentation that is available.
Table 5 Related Documentation
Document Title Available Formats
Release Notes for Cisco Unified Service Monitor 2.2
•PDF on the product CD-ROM
•On Cisco.com at the following URL:
User Guide for Cisco Unified Service Monitor 2.2
•PDF on the product CD-ROM.
•On Cisco.com at the following URL: http://www.cisco.com/en/US/products/ps6536/
Release Notes for CiscoWorks Common Services 3.2
On Cisco.com at this URL:
User Guide for CiscoWorks Common Services 3.2
On Cisco.com at this URL:
Obtaining Documentation, Obtaining Support, and Security Guidelines
For information on obtaining documentation, submitting a service request, and gathering additional information, see the monthly What's New in Cisco Product Documentation, which also lists all new and revised Cisco technical documentation, at:
Subscribe to the What's New in Cisco Product Documentation as a Really Simple Syndication (RSS) feed and set content to be delivered directly to your desktop using a reader application. The RSS feeds are a free service and Cisco currently supports RSS version 2.0.
SUPPLEMENTAL LICENSE AGREEMENT
SUPPLEMENTAL LICENSE AGREEMENT FOR CISCO SYSTEMS NETWORK MANAGEMENT SOFTWARE: CISCO UNIFIED OPERATIONS MANAGER.
IMPORTANT-READ CAREFULLY: This Supplemental License Agreement ("SLA") contains additional limitations on the license to the Software provided to Customer under the End User License Agreement between Customer and Cisco. Capitalized terms used in this SLA and not otherwise defined herein shall have the meanings assigned to them in the End User License Agreement. To the extent that there is a conflict among any of these terms and conditions applicable to the Software, the terms and conditions in this SLA shall take precedence.
By installing, downloading, accessing or otherwise using the Software, Customer agrees to be bound by the terms of this SLA. If Customer does not agree to the terms of this SLA, Customer may not install, download or otherwise use the Software.
ADDITIONAL LICENSE RESTRICTIONS:
•Installation and Use. The Software components are provided to Customer solely to install, update, supplement, or replace existing functionality of the applicable Network Management Software product. Customer may install and use the following Software components:
–CiscoWorks Common Services: Contains shared resources used by other components in this bundle. In many cases, all components in this bundle can be installed on a single server.
–Cisco Unified Operations Manager: May be installed on a server in Customer's network management environment. Contains shared resources used by other components in this bundle. In many cases, all components in this bundle can be installed on a single server.
–Cisco Unified Service Monitor: May be installed on a server in Customer's network management environment.
For each Software license granted, Customers may install and run the software on a single server to manage the number of IP phones specified in the license file provided with the software, or as specified in the Software License Claim Certificate. Customers whose requirements exceed the IP phone limit must purchase upgrade licenses or additional copies of the software. The IP phone limit is enforced by license registration.
•Cisco Unified Operations Manager Standard Edition. Customer may install and run the Software on a single server. This version of Operations Manager limits the features available to the Customer. The following features are not accessible:
–Diagnostics (phone status tests, synthetic tests, batch tests, and node-to-node tests).
–Video phone reports.
Customers who require the use of these features must upgrade to the Premium Edition of the Software. Feature use restrictions are enforced by license registration.
•Cisco Unified Operations Manager Premium Edition. Customer may install and run the Software on a single server. Customer has access to all features of the product. Use of this product is enforced by license registration.
•Reproduction and Distribution. Customers may not reproduce nor distribute the Software.
DESCRIPTION OF OTHER RIGHTS AND LIMITATIONS.
Please refer to the Cisco Systems, Inc. End User License Agreement.
This document is to be used in conjunction with the documents listed in the "Product Documentation" section.
CCDE, CCENT, CCSI, Cisco Eos, Cisco Explorer, Cisco HealthPresence, Cisco IronPort, the Cisco logo, Cisco Nurse Connect, Cisco Pulse, Cisco SensorBase, Cisco StackPower, Cisco StadiumVision, Cisco TelePresence, Cisco TrustSec, Cisco Unified Computing System, Cisco WebEx, DCE, Flip Channels, Flip for Good, Flip Mino, Flipshare (Design), Flip Ultra, Flip Video, Flip Video (Design), Instant Broadband, and Welcome to the Human Network are trademarks; Changing the Way We Work, Live, Play, and Learn, Cisco Capital, Cisco Capital (Design), Cisco:Financed (Stylized), Cisco Store, Flip Gift Card, and One Million Acts of Green are service marks; and Access Registrar, Aironet, AllTouch, AsyncOS, Bringing the Meeting To You, Catalyst, CCDA, CCDP, CCIE, CCIP, CCNA, CCNP, CCSP, CCVP, Cisco, the Cisco Certified Internetwork Expert logo, Cisco IOS, Cisco Lumin, Cisco Nexus, Cisco Press, Cisco Systems, Cisco Systems Capital, the Cisco Systems logo, Cisco Unity, Collaboration Without Limitation, Continuum, EtherFast, EtherSwitch, Event Center, Explorer, Follow Me Browsing, GainMaker, iLYNX, IOS, iPhone, IronPort, the IronPort logo, Laser Link, LightStream, Linksys, MeetingPlace, MeetingPlace Chime Sound, MGX, Networkers, Networking Academy, PCNow, PIX, PowerKEY, PowerPanels, PowerTV, PowerTV (Design), PowerVu, Prisma, ProConnect, ROSA, SenderBase, SMARTnet, Spectrum Expert, StackWise, WebEx, and the WebEx logo are registered trademarks of Cisco and/or its affiliates in the United States and certain other countries.
All other trademarks mentioned in this document or website are the property of their respective owners. The use of the word partner does not imply a partnership relationship between Cisco and any other company. (1002R)
Any Internet Protocol (IP) addresses used in this document are not intended to be actual addresses. Any examples, command display output, and figures included in the document are shown for illustrative purposes only. Any use of actual IP addresses in illustrative content is unintentional and coincidental.
© 2009 Cisco Systems, Inc. All rights reserved.