Guest

Cisco Prime Unified Operations Manager

Release Notes for Cisco Prime Unified Operations Manager 8.7

  • Viewing Options

  • PDF (276.9 KB)
  • Feedback

Table Of Contents

Release Notes for Cisco Prime Unified Operations Manager 8.7

System Requirements

New and Changed Features

UC Opsview

Support for Adding New Syslogs

Support for New Events

Support for New Devices and Phones

Important Notes

Installation Notes

Memory Usage for Multiple Phone Reports

Known Problems

Resolved Problems

Product Documentation

Related Documentation

Obtaining Documentation, Obtaining Support, and Security Guidelines

SUPPLEMENTAL LICENSE AGREEMENT


Release Notes for Cisco Prime Unified Operations Manager 8.7


This document contains the following topics:

System Requirements

New and Changed Features

Important Notes

Known Problems

Resolved Problems

Product Documentation

Related Documentation

Obtaining Documentation, Obtaining Support, and Security Guidelines

SUPPLEMENTAL LICENSE AGREEMENT

System Requirements

System requirements are documented in the Installation Guide for Cisco Unified Operations Manager 8.7. For documentation updates after publication, see Cisco.com.

Compatibility information is documented in the Supported Devices and Interoperable Software Table for Cisco Prime Unified Operations Manager 8.7 and the Cisco Unified Service Monitor 8.7 Compatibility Matrix.

New and Changed Features

The following are the new features in this release:

UC Opsview

Support for Adding New Syslogs

Support for New Events

Support for New Devices and Phones

UC Opsview

UC Opsview provides:

An integrated view of UC endpoint and network infrastructure health

Quality of service

An interface that aids in navigation to fix operational issues before the end user notices them.

The following dashlets are available:

Phone Health Summary

Top 5 Call Failure Locations

Top 5 WAN Traffic Locations

UC Services Health Summary

Top 5 Poor Call Quality Locations

Top 5 Utilized Trunks

See the UC Opsview section in the User Guide for Cisco Prime Unified Operations Manager 8.7 for details.

Support for Adding New Syslogs

Operations Manager enables you to add unsupported syslogs. You can set the severity and the time by which the syslog must be cleared. See the Adding New Syslogs section in the User Guide for Cisco Prime Unified Operations Manager 8.7 for details.

Support for New Events

Cisco Prime Unified Operations Manager 8.7 supports the following new events:

AdjacencyDetached

MOSCQEReachedCriticalThreshold

MOSCQEReachedMinorThreshold

MOSCQEReachedMajorThreshold

MeetingPlaceMinorSwAlarm

ServiceStopped

MeetingPlaceSwAlarm has been renamed MeetingPlaceMajorSwAlarm.

See the Supported Events section in the User Guide for Cisco Prime Unified Operations Manager 8.7 for details.

Support for New Devices and Phones

Cisco Prime Unified Operations Manager 8.7 supports the following new devices and phones:

Cisco Unified Communications Manager Business Edition 8.6.2 (CCMBE 8.6.2)

Cisco Unified Communications Manager 8.6.2 (CCM 8.6.2)

Cisco Unity Connection 8.6.2 (CUC 8.6.2)

Cisco Unified Presence 8.6.2 (CUP 8.6.2)

Cisco Jabber for iPhone, Windows and Android

Important Notes

The following topics include important information:

Installation Notes

Memory Usage for Multiple Phone Reports

Installation Notes

See the Installation Guide for Cisco Unified Operations Manager 8.7 for details on installation, upgrade/migration, and getting started.

The upgrade paths that have been tested and are supported in Operations Manager are:

Release 8.5 to 8.7

Release 8.6 to 8.7

The following upgrade paths are not supported:

Upgrade from Operations Manager 8.6 MSP deployment to 8.7 enterprise deployment.

Upgrade from Operations Manager 8.6 MSP deployment to 8.7 MSP deployment.

Direct upgrade from Operations Manager releases before 8.5.

For more information see the following guides:

Installation Guide for Cisco Unified Operations Manager 8.0

Installation Guide for Cisco Unified Operations Manager 8.5

Installation Guide for Cisco Unified Operations Manager 8.6

If you are running Operations Manager 8.5 or 8.6, see the Installation Guide for Cisco Unified Operations Manager 8.7 for complete details on installation and upgrade procedures.


Note Some known problems in Service Monitor have been resolved. If you run Service Monitor on the server with Operations Manager, be sure to review Release Notes for Cisco Unified Service Monitor before you install Operations Manager.


Memory Usage for Multiple Phone Reports

Depending on the number of records reports, the system can handle only a certain number of large reports that are open at the same time. When a report is closed, the window task manager may not immediately show that the Tomcat memory usage is decreasing. However, it will free up memory for new reports to be opened.

We recommend that you close phone reports after you view them to ensure that system performance is not degraded.

Known Problems

Table 1 describes known problems that exist in this release.

For updates to the Installation Guide for Cisco Prime Unified Operations Manager or the User Guide for Cisco Prime Unified Operations Manager, see Product Documentation.

Table 1 Known Problems in Operations Manager 

Bug ID
Summary
Explanation

CSCuj29826

A blank page is displayed when you use the direct URL to launch the diagnostics page.

A blank page is displayed when you use the direct URL to launch the diagnostics page. This can occur if:

There are no evaluation or permanent license files in the /opt/CSCOpx/etc/licenses directory.

Permanent license files are hosted to the wrong MAC address. This can occur if there is a change in the MAC address of Operations Manager server interface.

For Single Enterprise installation of Operations Manager, the following URL will be displayed in the Address bar, but a blank page will be displayed: http://<om_server_ip_address>:1741/cwportal/user/admin/
cuom-dashboard

For Multiple End-customer installation of Operations Manager, the following URL will be displayed in the Address bar, but a blank page will be displayed: http://<om_server_ip_address>:1741/cwportal/user/admin/
cuom-alert

Workaround:

If there is a change in the MAC address, you must rehost the permanent license file to the correct MAC address. After rehosting, you must clear the browser cache and use the following URL to launch the application: http://<om_server_ip_address>:1741.

If there are no license files in the /opt/CSCOpx/etc/licenses directory, you must install an evaluation or permanent license.

Impacted devices do not show the poor calls.

The impacted devices do not show poor calls information when:

Wireless IP Phones are involved (because CUOM does not get access point information from wireless phones).

The IP Phone is unable to provide switch information.

The IP Phone wrongly provides 0.0.0.0 as switch information.

Workaround:

None.

CSCtw65476

WAN Dashlet shows two colors.

The WAN Dashlet shows two colors when the location used does not change for some time or remains the same for the entire time period shown in the graph.

Workaround:

None.

CSCtw65487

The top five poor call quality locations show negative values in the Y axis.

When the total calls are very low and the bubble size is large, negative values are shown on the Y axis for the top five poor call quality locations to accomodate the bubble on the graph.

Workaround:

None.

CSCtw85588

The Top N Location WAN Traffic dashlet shows multiple tooltips

Hovering your cursor over the Top N Locations WAN Traffic dashlet shows multiple tooltips with the same information.

Workaround:

None.

CSCtx27067

Mismatch in the number of failed calls in the Top 5 Call Failed Locations.

The Failed Calls count in the main dashlet does not match count shown in the trend chart in the Troubleshooting view.

This discrepancy occurs because the main dashlet shows the failed calls count one hour from the current launch, but the Troubleshooting view trend chart shows hourly breakup of the failed calls.

Workaround:

Check the count based on the time shown in the CDR table.

CSCtx27125

Mismatch in the number of poor calls in the Top 5 Poor Call Quality Locations.

The Poor Quality Calls count in the main dashlet does not match the count shown in the trend chart in the Troubleshooting view.

This discrepancy occurs because the main dashlet shows the call count one hour from the current launch, but the Troubleshooting view trend chart shows hourly breakup of the calls.

Workaround:

Check the count based on the time shown in the CDR table.

CSCtx56387

Syslog processor logs are not rotated properly and hence they take a large chunk of memory space.

Disk space becomes low when the syslogs are not rotated properly.

Workaround:

Stop the daemon manager and delete all very large log files; then restart the daemon manager:

1. Run the command net stop OMHealthMonitor

2. Run the command net stop crmdmgtd.

3. Delete all very large log files.

4. Run the following commands:

command net start crmdmgtd

net start OMHealthMonitor

CSCty67192

Problem with loading the CDR records in Call Quality Troubleshooting view.

There is a problem with loading the CDR records in the Call Quality Troubleshooting view.

Workaround:

Reload the page.

CSCty67484

The scroll bar is missing from the Call Details table when it is launched in Internet Explorer.

CDR records cannot be viewed completely when the number of records is larger than seven, because the scroll bar is missing when Operations Manager is launched in Internet Explorer.

Workaround:

None.

CSCty67524

Impacted device call details are not filtered properly in the Call Quality Troubleshooting view.

CDR and CMR details are incorrect in the Troubleshooting view, because the call details are not filtered properly.

Workaround:

None.

CSCty67616

Discrepancy in the poor call count in the Call Quality Trend graph and Impacted Network Infrastructure Device graph.

There is a discrepency in Call Quality Trend graph and the Network Infrastructure Device graph in the Troubleshooting view.

Workaround:

None.

CSCty51136

There is a mismatch in the number of Call Quality and Failed Calls in the Troubleshooting view.

After Operations Manager and Service Monitor are installed and the Cisco Unified Communications Manager added, the user may find a mismatch number in the Call Quality and Failed Calls for the first hour.

This happens if Unified CM sends the CDRs late to Service Monitor. This will happen only once in the first hour after installation.

Workaround:

None.

CSCty48944

Bubble icon representing percentages in the Call Failure and Poor Call Quality dashlets is not shown for low percentages.

The bubble icon is not seen when the Call Failure and Poor Call Quality percentages are low.

Workaround:

None.

CSCty02664

The call detail data is sometimes jumbled in the Call Quality Troubleshooting view.

The CDR details are sometimes jumbled in the Call Quality Troubleshooting view.

Workaround:

Refresh the page.

CSCto03412

NAM reports loss of packets when calls are made to vmail using SIP trunk.

When calls made to vmail via SIP trunk DTMF tones are sent inband, the NAM and Cisco 1040 sensor both report packet loss statistics where none exists in the network.

Workaround:

None.

IBM Server MCS 7835/7845 I2 displays -1 in DDV.

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

Workaround:

None. This problem has not been observed on later Unified Communications Manager versions, for example, 7.1(2).

Operations Manager support for Cisco Voice Portal server with headless Cisco Security Agent installed.

While you are running headless Cisco Security Agent (CSA) on Cisco Voice Portal servers and managing these devices with Operations Manager, ping requests may be blocked by CSA.

This occurs when CSA is installed on a Voice Portal server.

Workaround:

1. Disable CSA.

2. Add Operations Manager as a trusted application in CSA.

UC App on UCS goes to SNMP Timeout - Unreachable state (Specifically MP and CUPS).

If any vendor MIBs (such as .1.3.6.1.4.1.77.1.2.3.1.1) do not respond within two seconds during Inventory Collection, UC App on UCS is marked Unreachable in CUOM.

Workaround:

1. Stop the Native Agent Adapter service on the device.

2. Delete and re-add the device in Operations Manager.

If the problem persists, delete the device from the Unreachable device list in Operations Manager.

3. Open the file \CSCOpx\objects\smarts\conf\discovery\discovery.conf and search for defaultSNMPAutoTimeout, and set the value to 10000.

4. Restart DfmServer (pdterm/pdexec).

5. Wait for several minutes before you re-add the device in OM.

CSCtr85775

Batch test result shows Partial or Failed state although it is passed.

In some instances, an error in the batch test results causes it to display a Partial or Failed status although the status should be Passed.

Workaround:

Disregard the batch test results.

CSCtr72012

50 cluster setup - Fault Monitor goes blank.

This problem occurs in multiple end-customer deployments that use Internet Explorer if:

There are 50 customers/clusters with a full load

and

A consistently even load of approximately 25 events per minute

In this case, Fault Monitor windows goes blank but recovers after a few minutes.

The problem is caused by the Internet Explorer Java Script Engine performance.

No problems exist in Firefox and Chrome.

Workaround:

If you are a multiple end-customer or an HCS user, use Firefox browser in full load conditions with 25 events per minute.

CSCtr71722

During upgrade a Locked files error occurs on rare occasions.

In rare cases, while upgrading, all the processes are not shutdown, which causes the lock to certain files. This problem causes an error message to appear stating that the files are locked.

Workaround:

Stop the install or upgrade and manually stop those processes from the Windows Task Manager. The install/upgrade runs properly after this step is taken.

CSCtr65253

Issues in Portal and IPIF reports for Super Admin and System Admin users.

In Multiple-End Customer deployments, if a user with Super Admin privileges logs into Operations Manager, they see inconsistencies in Fault Monitor and Diagnostics Portal's Customer View.

Workaround:

Super Admin is only supported in the Common Services framework. There is no support for those privileges in Operations Manager. We recommended you do not use this user role in Operations Manager.

CSCtr58368

50 Cluster VL Co-Residence setup - PTM Re-Configure takes close to nine hours.

This problem occurs if you add many devices (for example over 2,000). In this case, the PollingServer may experience polling delays of up to two hours.

Workaround:

Add devices in smaller increments.

CSCtr54265

PR event is seen for only one phone if two phones have same IP and extension.

In rare occasions in the multiple end-customer deployments, if two customer phones have the same IP and Extension and these two phones have a phone reachability test Failed event on them at same time, then only one event on one phone is raised.

Workaround:

None.

CSCtr52074

Return error indicates HTTPS is not supported on HCM add/delete device.

In HCM when you add or import a device using HTTPS as the protocol or use a port number, it causes devices to be placed in a Partially Monitored state. This is because the device expects HTTP protocol and no port.

Although OM/SM NBI exposes the interface to accept HTTPS as protocol and port for communication, these two attributes are place holders for future requirements. Do not use these fields in the NBI.

Workaround:

While adding a device or importing from HCM through xls, ensure you select HTTP as protocol and that you do not set the port field.

CSCtr45073

Unsupported version error in Internet Explorer 8.0 compatibility mode.

An "unsupported browser" error occurs in Internet Explorer (IE) 8.0 compatibility mode. IE 8.0 functions as IE 7.0 in compatibility mode, and IE 7.0 is not supported by Operations Manager.

Workaround:

Do not use IE 8.0 compatibility mode.

CSCtr31224

Device tree takes a long time to load when RBAC user device groups are configured or when system device groups are present.

When the device tree is expanded, it is very slow. /This occurs when a user is given a device-level authorization This does not occur when a user is given a task-level authorization. It also occurs when the CPU is high.

Workaround:

Retry opening the device tree later, after the CPU load is reduced.

CSCtr30213

Annotate does not work on DWR.

Whenever cluster level events are annotated in Fault Monitor by a user, the annotation status is not updated automatically.

Workaround:

Manually refresh the events updates the annotation status.

CSCtq96815

Perf-ENT NotsGroup creation-group selection takes more than 5 minutes

If you monitor more than 1,000 devices, it takes a long time to configure Notification groups (for example, selecting and editing device selection) in a large performance enterprise setup.

Workaround:

None.

CSCtq63688

Operations Manager 8.5 to 8.6 upgrade—None of the portlets load

None of the portlets load while you upgrade Operations Manager 8.5 to 8.6.

Workaround:

1. Remove the tomcat Work directory in the following location: C:\Program Files\CSCOpx\MDC\Tomcat\work,

2. Restart tomcat by typing the following on the command line: pdterm tomcat
pdexec tomcat

CSCtq56614

RBAC-Common Services screen is always viewed in read-only mode.

If a user is not provided access to any Common Services screens, the screens can still be launched, but only in read-only mode. This occurs in normal conditions, when a user is created without any access privileges to Common Services features.

Workaround:

This is the accepted product behavior. If no access privileges are provided, then screens are displayed in read-only mode.

CSCtq52863

Operations Manager uninstall does not remove the CSCOpx or the log directories.

In some cases, when you uninstall Operations Manager, the CSCOpx OM install folder has some files left in it. This may be caused by some processes that are open and have access to these files.

Workaround:

Always check these folders after installation and manually delete any files that remain in the folder.

CSCtq51627

Phone ReachahbilityTest events not generated.

Phone reachability events are not created when a phone becomes unreachable. This occurs when you configure a phone reachability test with the source device running IOS version 12.x.

Workaround:

Upgrade the IPSLA module IOS to 15.x.

CSCtq36919

Tree view is does not reflect the event count in Multiple end-customer mode

Sometimes Fault Monitor does not update the event severity counts properly for unidentified traps. This occurs when Operations Manager receives traps from devices that it does not manage and are classified as unidentified traps.

This is not common scenario because this occurs only when traps are being sent to Operations Manager, from devices not managed by Operations Manager.

Workaround:

None.

CSCto01090

Install intermittent error: could not find dbsrv10.exe error causes Fault Monitor not to load.

Fault Monitor fails to load. At the end of the installation logs, an error relating to the dbsrv10.exe not found appears. This is because the dbsrv10 is not found in a 32 bit machine.

Workaround:

To recover from this problem:

1. Uninstall the lms.

2. Local copy the lms image to a folder say for example c:\lms.

3. Go to local copy folder, installreloc, where you should see several zip files.

In one of the zip files, the crm.pm will be in the objects\\perl5\\lib structure. Usually it will be part1x.zip (where x is 1,2,3...) or part2x.zip (where x is 1,2,3,...).

4. Extract that file using a compression software such as winrar/winzip and open it in Notepad.

5. Change the following lines:

if ($ctr > 0 ) { 
$WIN_BIT = '64'; 
}
else { $WIN_BIT = '32'; 
} 
 
      

to

$WIN_BIT = '32';
 
      

6. Save and copy this file to replace the original crm.pm in the zip file.

7. Install using this local copy and issue should be resolved

CSCtn28373

Count Inconsistency between Portal and Fault Monitor.

Sometime event totals of Diagnostics View and Fault Monitor do not match.

Workaround:

None.

CSCtl84914

Service Level View does not show SIP trunk with multiple destinations.

SIP trunk does not display in Service Level View. This occurs when multiple destinations have been configured on the SIP trunk.

Workaround:

None. Service Level View displays only SIP trunks that have a single destination configured.

CSCtl56188

Perf VL Cluster Event Summary takes 30 seconds

In the Cluster Event Summary portlet, if the number of events at the cluster level is greater than 200, then the load time may vary between 30 to 90 seconds, depending on the number of events in the system.

Workaround:

None.

CSCtl03846

Client Memory and CPU usage for CUES graph

When ten graphs are open at the same time on a client machine, CPU and memory usage is high.

Workaround:

Reduce the number of simultaneous graphs, if the client performance is impacted.

CSCtk64429

Various failures with Firefox Zoom In or Zoom Out feature.

Several menu options cannot be displayed when the Zoom In or Zoom Out feature is enabled in Firefox.

These are:

Device and Credentials

Diagnostic Tests

Event History Reports

Notifications

Performance Graphs

Workaround:

If a menu option does not appear, revert to either Zoom In or Zoom Out. For example, use Zoom Out to see Event History reports or Zoom In to see Performance Graphs.

CSCtk46871

Registered MGCP interfaces are reported as Unknown.

Endpoint registration status is detected from a Unified CM node that belongs to a Unified CM group configured for an endpoint.

If an endpoint is registered to a Unified CM node that is outside the Unified CM group for which it was configured, its status is reported as Unknown.

This occurs although the endpoint appears as Registered in the Unified CM Administration UI.

Workaround:

Ensure the device pool and Unified CM group configurations are correct.

CSCtk35693

Unable to retrieve the contents from the Enumeration type response

Operations Manager cannot retrieve the Enumeration type response in the following situations:

When using Apache-Axis2 client for CUOM NBI:

Apache-Axis2 does not support the parsing enumeration data-type because Axis does not support the No-UPA [Unique Particle] option while compiling XSD.

Workaround:

For Apache-Axis2 client generation, use all files available under OM-Install-Folder\orion_nbi\wsdl-xsd.

When using Apache-Muse client with XMLBeans for bindings:

Apache-Muse with XMLBeans supports NO-UPA rules.

Workaround:

Remove thee comment tags for the following lines in WS-Enumeration-2004_09.xsd, available under OM-Install-Folder\orion_nbi\wsdl-xsd\:

Line number: 25-27

<xs:sequence>

<xs:any namespace="##other" processContents="lax" minOccurs="0" maxOccurs="unbounded"/>

</xs:sequence>

Line number: 48-52

<xs:sequence>

<xs:any namespace="##other" processContents="lax" minOccurs="0" maxOccurs="unbounded"/>

</xs:sequence>

Line number: 58-62

<xs:sequence maxOccurs="unbounded">

<xs:any namespace="##other" processContents="lax" minOccurs="0" maxOccurs="unbounded"/>

</xs:sequence>

CSCtj61784

Launching cross launches for IP Phones that is in NATTED environment fails.

HCS customers only.

If there is a NAT Gateway between the phones being monitored and Operations Manager and they are prevented from reaching these phones directly, then clicking on the IP Phone, Extension or MACAddress links in Phone reports display a Page Not Found error.

Workaround:

None.

CSCti88552

Cisco Unified Presence Server version appears incorrectly.

Presence Server version 8.x appears incorrectly in Operations Manager.

The version may appear as 8.0.1-1 in DDV and portal, but the actual CUPS version is 8.0.0.39051-32. This behavior is related to a defect on Presence Server SNMP.

Workaround:

None.

CSCti87909

User Defined Group Name change is not handled in Fault Monitor.

Fault Monitor tree node is not updated when there is a change to the User Defined Group Name.

Workaround:

Do not rename the User Defined Group. Instead, delete it and add it again with the new name. If it has been renamed, restart the Tomcat process. To do this:

1. Enter net stop Tomcat at the command prompt.

Tomcat stops.

2. Enter net start Tomcat.

CSCth72411

CPU Requirement in the System Requirement screen of install shield is incorrect.

System Requirement shows 2,000 MHz as required, but Operations Manager requires two CPUs of 2,000 MHz each (Dual core).

If you use the requirement documented in the install screen (Single core), the backup and restore process (upgrade) do not work properly.

Error and warning messages appear if you install in a single core CPU machine.

Workaround:

Ensure you have the required system requirements as documented in the Installation Guide for Cisco Unified Operations Manager 8.7.

CSCth49859

Rearranging portlets layout results in disturbed column width

The column width is altered when you reposition portlets.

Workaround:

Manually rearrange the portlets so that the column widths are more readable.

CSCth07566

Popup windows from mega menu are not properly sized.

All popup screens appear as full screens.

Workaround:

None

CSCtg65703

First directory number is considered as phone directory number.

For Service Quality events, Operations Manager cannot retrieve all extensions for phones with multiple extensions from Service Monitor.

Operations Manager displays only one of the extensions, instead of a blank display or IP address. This is because the extension information is easier to correlate to the phone.

Workaround:

None.

CSCtc59456

Service Level View does not auto update CM cluster name changes.

In Operations Manager, only DDV automatically updates the cluster names. Admin has to manually restart the SIRServer and the TopoServer, for SLV to update its cluster name display.

Workaround:

Delete the cluster and add it back into Operations Manager.

CSCtc57000

Operations Manager displays event discovery time zone incorrectly.

Various components in Operations Manager may display different time zones.

This is caused by the way in which JDK uses the Windows system time resources. This time zone error can occur on any application that uses JDK.

Workaround:

1. On your server, change the time zone to another time zone and click Apply.

2. Return the time zone back to its original setting and click Apply.

For example, change to ACT/PKST in the server time zone list, then back to CDT.

3. Restart the daemon manager to apply the changes.

4. To update all time zone displays in Operations Manager, run Discovery.

CSCtb87576

Environmental parameters not shown for Unity 8.0.

The following problems occur while adding and monitoring Cisco Unity 8.0 in Operations Manager:

Environmental parameters are not displayed.

If you choose Interfaces > Unity Ports > Port, the extensions are not displayed.

This is a hardware Unity issue.

Workaround:

None.

CSCtb52025

Detailed Device View issues for Phone Access Switches

The Detailed Device View does not display some phone access switch model parameters. This is caused by SNMP MIB problems on the specified device model.

Workaround:

None. For details, see the Supported Devices and Interoperable Software Table for Cisco Prime Unified Operations Manager 8.6.

CSCta42055

Icon overlap issue in Service Level View.

In rare cases in Service Level View, the Edge/Icon overlaps with the label.

Workaround:

Right-click on the white space of the map to hide or show the IP or DNS label.

CSCsz96802

Nonpaged pool kernel memory increases.

This problem occurs when there is a gradual increase in the non-paged memory pool of the kernel memory.

Eventually this memory grows to 256MB and creates problems with the system.

Workaround:

1. Apply the Windows hot fix available at http://support.microsoft.com/kb/931311.

2. Reboot the system.

Nonpaged pool kernel memory should be stabilized.

CSCsz91114

Part of the host name is not visible on Service Level View.

The topology is the layout pattern of interconnections of the various devices. The layout pattern (x,y) position is based on the prefuse layout algorithm. In some rare cases, the device label may be truncated.

Workaround:

Do either of the following:

Rest your cursor over the device and view the name in the tooltip.

Right-click the empty area to display the device name by IP/DNS.

CSCsz84687

Error message appears intermittently when you edit the notification group.

If you have created more than the recommended notification groups, an error message appears intermittently while you are editing a notification group.

Workaround:

Limit the number of notification groups. If you have more than the recommended limit, remove some notification groups.

See http://www.cisco.com/en/US/products/ps6535/products_user_guide_list.html for details about phone and other notification group limits.

CSCsz42608

Environment Variables Tab is missing for IPCC installed in 7845-I2.

IPCC platform environment variables are not supported.

Workaround:

None.

CSCsz15709

Voice Gateway is in an Unreachable state, but events are raised.

Although devices go into an Unreachable state, Operations Manager can still monitor the device faults if the device becomes reachable.

Workaround:

Rediscover the device to move it into a Monitored state.

CSCsy83638

SYS: default polling interval of 240s is not maintained for monitored switches.

Interface/port status and memory utilization status for monitored switches may not get polled at the specified polling interval.

For example, if the default polling interval is configured at 240 seconds, polling may occur between 240 to 600 seconds. This occurs only when OM monitors a large number of devices (over 1,000).

Workaround:

None.

CSCsw69457

Cannot deselect CUCM nodes from Notification Criteria.

If you deselect CUCM nodes from Notification Criteria, Notifications continue to appear for CUCM nodes. This occurs if you select Cisco Unified Communication Manager or Cluster OGS group in Operations Manager 2.1.

This causes Operations Manager to continue to receive cluster-level events, as well as CUCM events (since the CUCM are selected under the cluster).

Workaround:

None.

CSCsu69477

IPIU Phone count reduced to 0.

Phone count in the system becomes 0 when major phone discovery schedules are deleted and there is no major discovery scheduled for the entire day.

Workaround:

You must have at least one major discovery cycle of a major discovery scheduled in a day. To avoid that problem, do not delete any of the default schedules.

CSCsr73142

Phone reachability events not deleted if you delete all devices.

Phone reachability events are not deleted when all devices in the system are deleted.

Workaround:

None.

CSCsr20195

Operations Manager does not support more than two page files on the system.

Inventory Collection gets stuck at 10% and the brcontrol execution hangs because of high CPU consumption. This is a limitation of the Operations Manager caused by 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.

CSCq65045

Duplicate set of IP addresses in IP Address report.

When there are devices to be monitored in NAT, the IP Address report duplicates the set of device IPs.

This problem is caused when the information is pulled from the inventory engine, and the data replicates all IP address modelled there (which includes both NAT and local IP).

These are not duplicate entries, but depict the combinations for NAT and corresponding local IPs and vice versa.

Workaround:

None. This does not impact functionality.

CSCso54492

Phone Count issues across GSU, IPIF and SLV

For a brief period of time (around 15 minutes), the phone counts in phone reports may not match with counts displayed in the Detailed Device View.

This occurs because of the way the various pollers collect and process the phone data during any major phone status updates. Also because of the difference in frequency of polling.

The DDV (GSU) phone count is based on a single global variable, ccmTotalRegisteredPhoneCount. The phone report phone counts are collected from IPIU.

If there are phone status changes because of some outages in the network, Detailed Device View shows the counts, immediately. Other phone reports take some time to process and update the counts. This causes the mismatch.

Workaround:

None

CSCsm59818

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 later, then rediscover the device in Operations Manager.

CSCsl89529

In CER in Detailed Device View virtual memory is shown as 0.

Virtual Memory is displayed as 0 for CER when Operations Manager monitors CER 2.0.

Workaround:

None.

CSCsk41498

Cannot discover SIP Phone registered to CME.

When Operations Manager discovers a CME and voice register pool (SIP phones), it does not display any SIP Phones registered with that CME.

Workaround:

None.

CSCsi77087

GB: Service Level View displays the link status of private links for ICM nodes incorrectly.

The IPCC SLV shows the link state among various device subsystems, instead of among the ICM servers.

Workaround:

None

CSCsi77016

Service Level View ICM device IP addressing

In IPCC deployment, if ICM is configured with private and public addresses, the information displayed in Service Level View and Detailed Device View is not consistent.

Workaround:

None.

CSCsi73594

SLV-IPCC displays unnecessary cross links.

Under certain conditions Service Level View displays crossed links among devices where it is not necessary.

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 do not apply to the negative synthetic tests. The Detailed Device View should display N/A for this field.

Workaround:

None.

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 responded to SNMP queries during automatic discovery. However later, it did not respond to SNMP queries during inventory collection.

Workaround:

None.

CSCsd58055

The Devices report may show a device's capability as UnknownMDFType.

The Devices report displays a device's capability as UnknownMDFType, if the device is not supported by Operations Manager.

Workaround:

None.

CSCsc44538

CSCsk21367

The DFMServer and VHMServer processes do not register with the broker.

Devices that are added to Operations Manager while these processes are running, exhibit the following behavior:

All devices get stuck in the Inventory Collection in Progress state.

All devices move to the Unreachable state.

After you install Operations Manager and reboot 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:

1. Run net stop crmdmgtd.

2. Wait 15 minutes.

3. Run net start crmdmgtd.

4. After the CPU resets, 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 2009

Domain Host Name Port Proc ID State Last Chg Time

------ --------- ------ ------- ----- -------------

DFM IPCOM-daily.cisco.com 2163 14120 RUNNING Jan 06 16:18:03 2009

VHM IPCOM-daily.cisco.com 2206 8856 RUNNING Jan 06 16:18:04 2009

CSCsc26996

Next Discovery, in the Device Management: Summary page, displays the time incorrectly.

This problem is caused by a registry setting in Windows that appears for time zones for which Daylight Saving Time changes are applicable.

If the check box for Daylight Saving Time is not checked, problems occur while 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.

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

3. Switch the machine to its present time zone.

CSCsb73004

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 message states that there is no data available for the last 48 minutes. This error is caused by 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.


Resolved Problems

The following software problems were resolved in Operations Manager 8.7. For information on bugs that are not included below, see the Cisco Software Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/home.pl.

Table 2 describes problems that were fixed in this release.

Table 2 Problems Resolved in Operations Manager 8.7 

Bug ID
Summary

CSCtq36936

Customer name is incorrect in notification for duplicate phones.


Product Documentation

The following product documentation is available:


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.


Supported Devices and Interoperable Software Table for Cisco Unified Operations Manager 8.7

Installation Guide for Cisco Prime Unified Operations Manager 8.7

User Guide for Cisco Prime Unified Operations Manager 8.7

Open Source Used In Cisco Unified Operations Manager 8.7

Related Documentation

Following is the list of related documentation that is available:


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.


Release Notes for Cisco Unified Service Monitor

User Guide for Cisco Unified Service Monitor

Best Practices for Cisco Unified Communications Management Suite on Virtualization

White Papers for Cisco Unified Operations Manager

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:

http://www.cisco.com/en/US/docs/general/whatsnew/whatsnew.html

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 Prime Unified Operations Manager Standard Edition has been discontinued. All Operations Manager Standard Edition customers will now receive the Premium Edition features by installing Operations Manager 8.7.

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.