Guest

Cisco Prime Unified Operations Manager

Release Notes for Cisco Unified Operations Manager 8.5

  • Viewing Options

  • PDF (282.4 KB)
  • Feedback
Release Notes for Cisco Unified Operations Manager 8.5

Table Of Contents

Release Notes for Cisco Unified Operations Manager 8.5

Changes to the Release Notes

System Requirements

New and Changed Features

Important Notes

Installation Notes

Memory Usage for Multiple Phone Reports

Known Problems

Resolved Problems

Documentation Updates

Installation Guide Updates

User Guide Updates

Product Documentation

Related Documentation

Obtaining Documentation, Obtaining Support, and Security Guidelines

SUPPLEMENTAL LICENSE AGREEMENT


Release Notes for Cisco Unified Operations Manager 8.5


Published: July 20, 2011 OL-24007-03

This document contains the following topics:

Changes to the Release Notes

System Requirements

New and Changed Features

Important Notes

Known Problems

Resolved Problems

Documentation Updates

Product Documentation

Related Documentation

Obtaining Documentation, Obtaining Support, and Security Guidelines

SUPPLEMENTAL LICENSE AGREEMENT

Changes to the Release Notes

This section documents supplemental changes that have been made since the initial release of the Release Notes for Cisco Unified Operations Manager 8.5.

Installation Guide Updates Added

Licensing updates to cover mandatory patch (CSCtq29209) for Operations Manager. For this and other minor updates, see the Installation Guide for Cisco Unified Operations Manager 8.5 for details.

User Guide Updates Added

For new entries about Service Level View and service quality event setting changes, see User Guide Updates.

System Requirements

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

Compatibility information is documented in the Supported Devices and Interoperable Software Table for Cisco Unified Operations Manager 8.5.

New and Changed Features

The following are the new features in this release:

Feature parity of Unified Communications 8.5 applications with functionality from UC 8.5. See the Supported Devices and Interoperable Software Table for Cisco Unified Operations Manager 8.5.

New phone models including 7925, 7925G, 7926G, and 7937G.

New device support, including:

Session Manager

Cisco Unified Border Element 1.4 and later:

o Support to monitor MTP and Transcoder Sessions usage

o SIP trunk utilization (call volume)

o Support for usage graphs

Energy Wise phone monitoring support

SIP Trunk and DSP failure monitoring

Usability enhancements—New performance dashboard, zoom/pan chart for back-in-time analysis

Call volume-based trunk utilization

Monitoring of Unified Communications on applications running on UCS:

Core applications include: Cisco Unified Communications Manager, Unity Connection, Cisco Unified Presence, Unified Contact Center Enterprise, and Cisco Voice Portal

Additional documentation is available on Cisco.com. See:

Best practices guides for managing Cisco devices.

Deployment guide.

E-learning video tutorials available from the user interface. You can also view these videos on Cisco.com at http://www.cisco.com/web/learning/le31/le46/nmtg_training/vods/om/om80/pointer.html.

See Table 2 for problems that are resolved in this release.

Important Notes

The following topics include important information:

Installation Notes

Memory Usage for Multiple Phone Reports

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

Installation Notes

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

The upgrade path that was tested and is supported is Operations Manager, release 8.0 to 8.5.

You can migrate your data from Operations Manager, release 2.3 to 8.5.

There is no direct upgrade from Operations Manager releases prior to 2.3.

If you are running any of these releases, for complete details on installation and migration procedures, see the Installation Guide for Cisco Unified Operations Manager for complete details on installation and migration procedures.


Note Some known problems in Service Monitor have been resolved. If you run Service Monitor on the server with Operations Manager, you should 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 show that the Tomcat memory usage is decreasing, right away. 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 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 Unified Operations Manager or the User Guide for Cisco Unified Operations Manager, see Documentation Updates.

Table 1 Known Problems in Operations Manager

Bug ID
Summary
Explanation

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.

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

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

CSV/XML file import may display a blank window.

In rare cases, after you import devices using a CSV/XML file, a blank window appears instead of a confirmation dialog box.

Workaround:

Ignore this window and close it. The devices are imported correctly into Operations Manager.

UserCleared events may require a manual refresh to get updated.

The time it takes to remove User Cleared events from the user interface of an already opened client, may differ from that of a newly launched client, by 30 minutes.

By design, the software does not check the EPM database every few seconds because this would create a extra load on the system and negatively impact performance.

Therefore this adds an additional 30 minutes to User Cleared events for clients that have been opened.

Workaround:

Manually refresh the page to reflect the updated values of UserCleared events.

Phone count problems when CUCM cluster name is in DNS.

If the CUCM Cluster name is DNS resolvable to an IP address, there may be phone count inconsistencies in the Diagnostics view.

Workaround:

If CDT Cluster/AXL discovery or RTMT polling does not work correctly, although the device may be active, check the device credentials.

1. Use Administration > Device Management > Device Configuration > Modify/Delete Devices to edit the device credentials.

If the device credentials are blank, enter the credentials and click Save.

2. Perform a rediscovery using Administration > Device Management > Inventory Collection > Cluster Device Discovery.

CSCtq29209

License CR CUOM 8.5 : Upgrade license

After upgrading from 2.3 to 8.x, licensing counts may not be represented correctly if the number of licensing files does not match. For example, if you have several 2.3 license files and upgrade with only one 8.x license file, Operations Manager does not recognize the multiple license files.

Workaround:

Install the mandatory CSCtq29209-8.5.0.zip patch from the Software Download on Cisco.com.

This patch corrects the behavior as follows:

1. If 8.x upgrade count in license file is less than the cumulative 2.x count:

A message displays that the server is eligible for an additional number of phone upgrades, as the current upgrade is less than the 2.x count

You can import another 8.x upgrade license, later for the missing count.

2. If 8.x upgrade count in license file is equal to cumulative 2.x count, no action is required.

3. If 8.x upgrade count in license file is greater than cumulative 2.x count:

A message displays that the server will manage only a specific number of phones, which is the number of phones licensed in 2.x.

If you want the server to manage more phones, you must purchase a standard 8.x license for additional phones.

CSCtn46270

Channel graph status issue.

Some problems exist in the Channel status graph including missing time in X-Axis of the channel status graph and chart not refreshing (which causes mismatched data between the utilization and channel status.

Workaround:

None.

CSCtn28373

Count Inconsistency between Portal and Fault Monitor.

Event totals between Diagnostics View and Fault Monitor do not match at times.

Workaround: None.

CSCtl99518

Intra-cluster phone move may cause the order of audits to be reversed.

The intra-cluster phone has different registration statuses in IPIF and CDT.

The cluster Device Registration Summary portlet shows the count for the phone, but the number of phones that are displayed in report do not match the count that was shown in the portlet.

This may happen when the phone undergoes an intra-cluster move (fallback scenario). If a phone moves from a primary Unified CM of a cluster to a backup node or vice versa, this problem may occur.

Workaround:

Start a CDT Discovery.

CSCtl84914

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

SIP trunk is not being shown in Service Level View. This occurs when multiple destinations have been configured on the SIP trunk.

Workaround:

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

CSCtl78837

IPIU reports do not reflect any changes when they are refreshed.

The IPIU reports do not display updated data after you refresh it.

Workaround:

Close the IPIU report and reopen it.

CSCtl76382

Service quality alerts > Tools > Node to Node test and Path Analysis does not work.

These tools do not work for service quality events that have phones as endpoints.

This problem occurs when a default gateway/switch to which the phone is connected, is not managed in Operations Manager.

Workaround:

None.

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, 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 CCM 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 the 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:

Uncomment 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>

CSCtk09169

Peak call failures appear in the Cluster Call Usage Summary following a CCM restart.

The Call Usage Summary Total, Hourly, and Peak 24- hour counters are incorrect when a CCM in a cluster is restarted.

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.

CSCti12760

ACS Fault Monitor needs to filter cluster events correctly

Cluster level events appear in Fault Monitor even after Unified CM is unauthorized in ACS mode.

Workaround:

None.

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

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

CUOM 2.3: 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.

CSCtc03348

DDV problems in Cisco Unified MeetingPlace 8.0.

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

Environmental parameters are not displayed.

If you select System > Processor, processor information is not displayed.

If you select System > RAM, free physical memory (%) is displayed as a negative.

Workaround:

None.

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 select Interfaces > Unity Ports > Port, the extensions are not displayed.

See CSCtc94843 for information on Unity problems.

Workaround:

None.

CSCtb75042

Environmental variables not shown for VG202 & VG204.

VG202 and VG204 environmental variables are not discovered and monitored. This is because some variables in the Cisco Environmental MIB are not supported on VG202 and VG204.

Because of this, Operations Manager cannot discover or monitor any environmental variables, such as Fan, VoltageSensor, and TempSensor.

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 Phone Access Switch MIB Display Problems.

CSCta64842

ErrCode 10 displayed for NAM properties.

This occurs when you navigate from a Service Quality Alerts Display to an Event ID page and click the NAM Call Details link.

If the event occurred earlier than three days ago, ErrCode = 10 is displayed. NAM call details are available only for three days.

Workaround:

Close the error window.

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.

CSCta37313

Event Monitor logs event details that are dropped because of flood conditions.

When an event flood occurs, Event Monitor logs the event details that are dropped (not processed) because of flood conditions.

In some instances, the dropped events are not logged in the associated log files, EPMDroppedEvents.log or ClearedDroppedEvents.log.

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.

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

Env. Variables Tab missing for IPCC installed in 7845-I2.

IPCC platform environment variables are not supported.

Workaround:

None.

CSCsz18490

Incorrect unresponsive event for Cisco Unity.

This only occurs on Cisco Unity version 4.0.5 (which has reached end of life).

Workaround:

Upgrade to a later version of software to fix the issue.

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.

CSCsx69872

Unified Contact Center Express issues.

Sometimes a few of the system and environmental parameters of Unified Contact Center Express appear as NA.

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.

CSCsv09130

Flash memory instability can occur in Service Level View 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 problem with Operations Manager. Internet Explorer may exit unexpectedly in this situation.

When a 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 displays the following error message:

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. Also close and relaunch any clients that may be hanging.

CSCsu73532

Operations Manager cannot monitor Extension Mobility enabled phones.

Some of the Extension Mobility phones are missing in the Operations Manager Phone report. However, Extension mobility phones exist in the network.

Workaround:

None.

Operations Manager currently does not support Extension Mobility Phones in Unified Communications Manager. This is because there is no MIB instrumentation in Unified Communications Manager.

CSCsu69477

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:

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.

CSCsq04884

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:

1. Create a dummy telephony config on the CME device and then discover it in Operations Manager.

2. Use the telephony-service command in config mode to enable skinny-based CME on the gateway.

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.

CSCsj20070

SRST operations link does not open.

The SRST page and the Service Level View may not open.

Workaround:

Restart the appropriate service as follows:

For the SRST page, restart the SRSTServer service.

For the Service Level View, restart the Inventory Collector.

CSCsj04891

Cannot launch the Personal Assistant Administration page from Cisco Personal Assistant,

You cannot launch the Personal Assistant Administration page from the Personal Assistant cross-launch.

Workaround:

None.

CSCsi80115

Associated Phone icon not represented with alert icon.

If a phone in a Unified CM cluster has an SQ alert, the Associated Phone icon is not represented with an alert icon.

Workaround:

None.

CSCsi77087

GB: Service Level View display 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.

CSCse78310

Detailed Device View for Cisco Unity devices displays incorrect information.

For Cisco Unity releases earlier than 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.

Although Cisco Unity 4.0(4) is upgraded to 4.0(5), the version on all services appears as 4.0(4).

Workaround:

Upgrade to Cisco Unity 4.2, then run RSK Configuration Wizard.

This workaround applies only to the Cisco Unity service version issue. It does not fix the first four counter problems mentioned above. There is no workaround for those problems.

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.

CSCsb60614

 

Cluster name changes are not reflected in Operations Manager.

If you change the name of a cluster in Cisco Unified Communications Manager, after the devices have been added to Operations Manager, the name change does not occur in Operations Manager.

This occurs even after you perform inventory collection.

Workaround:

1. Delete the devices in the cluster from Operations Manager.

2. Re-add the devices.

 

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


Resolved Problems

The following software problems were resolved in Operations Manager 8.5. 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.5 

Bug ID
Summary

CSCtl04036

Exported Phones Removed report works correctly

CSCtl00419

IP Phone Audit report now includes Audit Type for new phones added

CSCtk53815

Performance graphs work properly when multiple attributes are selected

CSCtk52876

GatewayReport Utilization displays all interfaces

CSCtk52733

UCM Cluster Route Pattern Summary now includes SIP Trunk and SIP Gateway associated Route Patterns

CSCtk46967

All event details display completely when Fault Monitor launches from Portal

CSCtk37285

IP phone status runs properly in Phone Status test

CSCtk18232

Internal pop up window launch in Portal works properly

CSCtj96908

Grouping of DS1s from 2 VGS works properly

CSCtj89834

Edit now works in Real-Time Transport Node-to-Node Test results

CSCtj03853

PhoneReachability Event now displays the ACS mode in AAD/Fault Monitor

CSCti37663

Service Level View launches successfully after daemon restart

CSCso62895

Operations Manager now lists all phones, including phones that have a Not Found status


Documentation Updates

Review the Known Problems and Installation Notes section for required critical information. This information is not available in the documentation that was included with the product image.

This section includes information on Installation Guide Updates and User Guide Updates.

Installation Guide Updates

For information on licensing updates to cover mandatory patch (CSCtq29209) for Operations Manager and other minor updates, see the Installation Guide for Cisco Unified Operations Manager 8.5 for details.

User Guide Updates

The following information was missing from the User Guide that was included in the product image:

When including NAT-enabled devices that are in MSP mode into a Node-to-Node Tests import file, ensure that the target router IP address is the private/local IP instead of public/global IP.

Use the following recommendations for optimal viewing of graphs in the Performance Dashboard:

Number of metrics selected in the Add Metrics dialog box for graphs to add to the dash board: 5

Number of graphs: 10

Number of metrics that can be merged: 10

Number of node-to-node tests that can be selected for launching a merged graph: 10

These recommendations are not an indication of limits for the performance graphing dashboard, but can be used as guidelines.

If you suspend a device, Operations Manager stops polling the device but may still receive device data such as CDR records.

For Service Level View, Unified CM Express (CME) devices do not display in Service Level View. To view CME data with Cisco Unity Express associations, see the Diagnostics view UI for UCM Express Summary portlets. For more information see the Using the Portal chapter in User Guide for Cisco Unified Operations Manager.

The procedure described in "Configuring Service Quality Events Settings" is no longer valid. This functionality was removed in Operations Manager 8.0 and is no longer available. MOS threshold setting can only be set at the codec level in Service Monitor. Operations Manager will no longer perform any checks on the traps MOS value and will generate the event as critical.

Detailed Device View Updates

The following information was missing from the User Guide that was included in the product image:

In the Detailed Device View, the Interface Code is applicable only for ISDN interfaces. All other interface types display N/A.

In the Detailed Device View, the Platform type for CUCM on UCS will display as VMware.

The Detailed Device View does not display the device model parameters listed in Table 3. This is due to SNMP MIB problems on the specified device model. There is no workaround.

Table 3 Phone Access Switch MIB Display Problems

Device Model
SNMP MIB Parameter not Displayed in DDV

2960(WS-C2960-24PC-L) and 3560 (WS-C3560-24PS)

1. Environment --> Device Temperature Sensor— Location not shown

2. Environment --> Power Supply—Description not shown

3. System --> Processor—Description not shown

4. Device Memory not shown

5. Interfaces --> Port—Admin status and Oper status shown as NA

3750 (WS-C3750G-24T)

1. Device Temperature Sensor not shown in Environment

2. Environment --> Power Supply—Description not shown

3. System --> Processor—Description not shown

4. Interfaces --> Port—Admin and Oper status shown as NA

C4507R-E and 4506E

1. MAC Address not shown

2. Environment --> Power Supply—Description not shown

3. System --> Processor—Description not shown

WS-C2960-24LT-L

1. Environment --> Power Supply—Description not shown

2. System --> Processor—Description not shown

3. System --> Memory information not shown

WS-3560E-48PD

1. Environment --> Power Supply—Description not shown

2. System --> Processor—Description not shown


Product Documentation


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 and Interoperable Software Table for Cisco Unified Operations Manager 8.5

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 8.5

In PDF on the product image

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 8.5

In PDF on the product image

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 8.5

In PDF on the product image

On Cisco.com at the following URL: http://www.cisco.com/en/US/products/ps6535/products_user_guide_list.html

Open Source Used In Cisco Unified Operations Manager 8.5

In PDF on the product image

On Cisco.com at the following URL: http://www.cisco.com

Context-sensitive online help

Select an option from the navigation tree, then click Help

Click the Help button on the page


Related Documentation


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 

PDF on the product image

On Cisco.com at the following URL:
http://www.cisco.com/en/US/products/
ps6536/prod_release_notes_list.html

User Guide for Cisco Unified Service Monitor

PDF on the product image.

On Cisco.com at the following URL: http://www.cisco.com/en/US/products/ps6536/
products_user_guide_list.html

White Papers including Deployment Guide and Best Practices Guides

PDF on the product image.

On Cisco.com at the following URL: http://www.cisco.com/en/US/products/ps6535/prod_white_papers_list.html


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

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.