 Feedback
|
Table Of Contents
Release Notes for Cisco Unified Operations Manager 2.0.1
SUPPLEMENTAL LICENSE AGREEMENT
Circumstances that Can Affect Data
Obtaining Documentation, Obtaining Support, and Security Guidelines
Release Notes for Cisco Unified Operations Manager 2.0.1
These release notes are for use with Cisco Unified Operations Manager (Operations Manager).
These release notes provide:
•
SUPPLEMENTAL LICENSE AGREEMENT
•
•
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:
•
–
–
–
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.
•
–
–
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.
•
•
DESCRIPTION OF OTHER RIGHTS AND LIMITATIONS.
Please refer to the Cisco Systems, Inc. End User License Agreement.
New Features
Cisco Unified Operations Manager adds the following:
•
•
•
•
Note
•
•
–
–
•
–
–
Product Documentation
Note
Table 1 describes the product documentation that is available.
Table 1 Product Documentation
Supported Devices Table for Cisco Unified Operations Manager 2.0.1
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.0.1
•
•
Installation Guide for Cisco Unified Operations Manager (Includes Service Monitor) 2.0.1
•
•
User Guide for Cisco Unified Operations Manager 2.0.1
•
•
Context-sensitive online help
•
•
Related Documentation
Note
Table 2 describes the additional documentation that is available.
Table 2 Related Documentation
Release Notes for Cisco Unified Service Monitor 2.0.1
•
•
User Guide for Cisco Unified Service Monitor 2.0.1
•
•
Release Notes for CiscoWorks Common Services 3.0.5 (Includes CiscoView 6.1.5) on Windows
•
•
Installation and Setup Guide for Common Services 3.0.5 (Includes CiscoView) on Windows
•
•
User Guide for CiscoWorks Common Services 3.0.5
•
•
Circumstances that Can Affect Data
Table 3 documents problems you may encounter.
Known Problems
Table 4 describes problems known to exist in this release.
Table 4 Known Problems in Operations Manager
CSCsb60614
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 re-add the devices.
CSCsb63311
In the Service Quality Alerts display, filtering does not work when using multiple criteria.
Using multiple filtering options at one time to customize the Service Quality Alerts display does not work correctly.
Workaround:
Filter the Service Quality Alerts display based on a single criterion.
CSCsb66977
Voice application software (for example, Cisco Conference Connection, Cisco Unified CallManager, or Cisco Emergency Responder) goes to the Unsupported state.
On some servers that have voice application software installed, rebooting causes the server to go to the Unsupported state in Operations Manager.
The problem occurs on servers that have the Windows operating system version upgraded to 2000.2.7sr3 or 2000.4.1.
The problem is caused by incompatibility between the CDP driver installed by the voice application and Microsoft Security hotfix MS05-019. For more information regarding the hotfix, see the Microsoft website for more details.
Workaround:
Upgrade the CDP driver on the voice application server.
1.
C:\Program Files\Cisco\Bin> cdpinstaller -v -u CISCO_CDP2.
•
•
•
•
3.
C:\program files\Cisco\Bin> cdpinstaller -v -l "C:\Program Files\Cisco\Bin \cdp.inf" -c p -i CISCO_CDPCSCsb73004
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.
CSCsb83202
OperationallyDown events for voice ports are being cleared automatically, even though the port is still down in the router.
The operationallyDown event for voice ports in routers are being cleared even though the port continues to be down.
Operations Manager only sends an operationallyDown alarm if the operating status (the OperStatus for this router) is in one of the following states:
•
•
If, during a polling cycle, the ifOperStatus is Down (2), the alarm is generated. If, during the next polling cycle, the ifOperStatus is Dormant (5), the operationallyDown alarm is cleared because it is not Down (2) or Testing (3).
Related bug: CSCsb87389.
Workaround: None.
CSCsc07502
Some screens in Operations Manager are not sized correctly when opened.
Several popup screens open with the status bar covering the bottom of the screen. Some popups are not resizable, and the buttons located at the bottom right are covered by the status bar.
This occurs only with Windows XP Service Pack 2 using Microsoft Internet Explorer, and with certain security settings configured. The security settings are applied when the Operations Manager server is put in a security zone where the sizing of popups opened by scripts is disabled.
Workaround:
For detailed instructions, access this bug through Cisco Software Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/home.pl. (You will be prompted to log into Cisco.com.)
To fix the problem, the Allow script-initiated windows without size or position constraints option should be enabled for the security zone that the Operations Manager server is in.
Do one of the following:
•
•
Note
CSCsc10167
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.
CSCsc12967
Exchange services are displayed as stopped when Cisco Unity is configured for failover.
When Cisco Unity is configured for failover mode, Operations Manager shows Microsoft Exchange Services as being stopped.
Workaround: None.
CSCsc44538
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:
•
•
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.
2.
3.
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.
For example:
C:\Program Files\CSCOpx\objects\smarts\bin>brcontrol
Broker is located at: IPCOM-daily:9002 Started: Jan 06 10:21:09 2006Domain Host Name Port Proc ID State Last Chg Time------ --------- ------ ------- ----- -------------DFM IPCOM-daily.cisco.com 2163 14120 RUNNING Jan 06 16:18:03 2006VHM IPCOM-daily.cisco.com 2206 8856 RUNNING Jan 06 16:18:04 2006CSCsc61752
In the Service Level View, when Cisco IP Contact Center (IPCC) is part of a user-defined view, it only appears in the tree view (view pane).
User-defined views in the Service Level View do not show Cisco IP Contact Centers in the map display pane. They only appear in the view pane.
Workaround: None.
CSCsc87486
In the Personalized report, not all the graphs are shown for the node-to-node test violations.
In the Personalized report for node-to-node tests, 24-Hour History shows the graph for only the following metrics:
•
•
•
No other graphs are displayed.
Workaround: None.
CSCsc91915
When creating node-to-node tests, errors are displayed when the test limit is exceeded.
When creating more node-to-node tests than allowed (the limit is 250), the following errors are displayed:
•
•
Workaround: None.
You can ignore the error messages.
CSCsd21804
Learning appears in the Device Type column of the Alerts and Events display.
On the Alerts and Events display and the Alert Details page, you may see Learning in the Device Type column. Learning indicates that Operations Manager was discovering the device when the alert occurred. The following events can trigger an alert during discovery:
•
•
–
–
–
–
Workaround:
•
•
CSCsc26996
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:
HKEY_LOCAL_MACHINE\CurrentControlSet\Control\TimeZoneInformation
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.
2.
This will cause the registry key to disappear. Now switch the machine to its present time zone.
CSCsd22730
Automatic discovery does not discover Cisco Unity Express devices.
During automatic discovery, using either ping sweep or CDP, Cisco Unity Express devices are discovered. These devices go into the Unreachable state.
Workaround:
Manually add Cisco Unity Express devices into Operations Manager.
CSCsd58055
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.
Workaround: None.
CSCsd69455
The right-click menu in the Service Level View does not display some of the options for Cisco Unified CallManagers.
When you right-click on a Cisco Unified CallManager in the Service Level View, not all the menu items are available in the list. Also, in the Detailed Device View for a Cisco Unified CallManager's device capabilities, Media Server and Host are not displayed.
Workaround:
Rediscover the Cisco Unified CallManager.
CSCsd71626
The Service Level View does not display a Cisco Unified CallManager cloud that was previously displayed.
During initial discovery or when the Operations Manager server boots up, if the Cisco Unified CallManager Service is down on all members of the cluster, this cluster will not show up in the Service Level View.
Workaround:
Rediscover the device once the Cisco Unified CallManager is reachable and the Cisco Unified CallManager Service is running on the Cisco Unified CallManagers.
CSCse75607
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.
Workaround: None.
CSCse78310
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:
•
•
•
•
•
Workaround: Upgrade to Cisco Unity 4.2, then run RSK Configuration Wizard.
Note
CSCsf05654
Some PRI channels are showing as active, even though they are inactive.
For PRI channels, D channels are always shown as active. Therefore, the four T1 ports on the Cisco Unified CallManager record (record 100) appear active. As a result, four out of a total of 96 channels appear active.
This also applies to the MGCP gateway data record (record 101); two D channels are active on the two T1 ports.
D channels are always shown as active in the case of PRI channels.
Workaround: None.
CSCsf15041
The device MCS7825I (with the sysObjectID 1.3.6.1.4.1.9.1.746) is listed as UnKnownMDFType.
Operations Manager displays Cisco 7800 Series Media Convergence Server MCS7825I (with the sysObjectID 1.3.6.1.4.1.9.1.746) capabilities as UnknownMDFType.
The sysObjectID 1.3.6.1.4.1.9.1.746 is not supported. See bug ID CSCsf15027.
Workaround: None.
CSCsf18921
Threshold settings appear incorrectly in performance graphs.
Configured thresholds for route list and route group are displayed incorrectly in performance graphs. Only one threshold setting appears in the graph.
Workaround: None.
CSCsf19029
Message-Waiting Indicator synthetic tests on Cisco Unity and Cisco Unity Express fail periodically.
Message-Waiting Indicator synthetic tests created on Cisco Unity and Cisco Unity Express may fail.
Workaround: None.
CSCsf27034
Route group and route list calculation limitations for MGCP and H323 gateway.
For MGCP gateways, route group, and route list, utilization is calculated for all channels of the T1/E1 ports even though partial T1/E1 circuits are configured. Operations Manager gets the data from Cisco Unified CallManager, and the data does not contain the MGCP port configuration information.
For H323 gateways, all ports which are part of the device are included in the route group and route list calculation even though not all of the ports are configured for call routing. This limitation is also caused by Cisco Unified CallManager not having the required information.
Workaround: None.
CSCsf98008
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.
Workaround: None.
CSCsh07060
InsufficientFreeMemory is reported incorrectly for Cisco Unified CallManager 5.0 clusters.
Events for InsufficientFreeMemory are being generated for Cisco Unified CallManager clusters 5.0 and higher. Operations Manager is not determining the correct InsufficientFreeMemory.
Workaround: None
CSCsi78419
Cisco Unity Connection 2.x attributes are not displayed in the Detailed Device View.
Cisco Unity Connection 2.x attributes are shown as either N/A or 0 in the Detailed Device View. This only occurs on Cisco Unity Connection 2.x.
Workaround: None.
CSCsj20070
SRST operations link does not open.
The SRST page and the Service Level View may not open.
Workaround:
Restart the appropriate service:
•
•
CSCsj43765
Cisco Unified Communications Manager Express appears under the H323 gateway group in the Service Level View.
When an ICT is configured between a Cisco Unified Communications Manager Express and a Cisco Unified Communications Manager, the Cisco Unified Communications Manager Express appears under the H323 gateway group in the Service Level View.
Workaround: None.
CSCsk21367
When restarting the Daemon Manager, the brcontrol command may fail.
When starting the Daemon Manager, the brcontrol command may fail. Meaning the VHM and DFM processes do not register with the broker.
This causes the following to occur:
•
•
•
Workaround:
Run the following commands:
1.
2.
3.
4.
5.
6.
Resolved Problems
Table 5 describes problems that where fixed in this release.
Obtaining Documentation, Obtaining Support, and Security Guidelines
For information on obtaining documentation, obtaining support, providing documentation feedback, security guidelines, and also recommended aliases and general Cisco documents, see the monthly What's New in Cisco Product Documentation, which also lists all new and revised Cisco technical documentation, at:
http://www.cisco.com/en/US/docs/general/whatsnew/whatsnew.html
This document is to be used in conjunction with the documents listed in the "Product Documentation" section.
Copyright © 2007 Cisco Systems, Inc. All rights reserved.
