Guest

Cisco Prime Unified Operations Manager

Release Notes for Cisco Unified Operations Manager 8.0

  • Viewing Options

  • PDF (259.1 KB)
  • Feedback
Release Notes for Cisco Unified Operations Manager 8.0

Table Of Contents

Release Notes for Cisco Unified Operations Manager 8.0

System Requirements

New and Changed Features

Important Notes

Installation Notes

Memory Usage for Multiple Phone Reports

Known Problems

Resolved Problems

Documentation 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.0


Published: July 13, 2010 OL-21591-03

This document contains the following topics:

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

System Requirements

System requirements are documented in the Installation Guide for Cisco Unified Operations Manager 8.0. 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.0.

Note the following system requirements:

Internet Explorer 7.x is no longer recommended or supported

8 GB of RAM is now required for the Unified Service Statistics Manager interface and any network greater than 10,000 phones.

Client requirements have been increased. For details see the Installation Guide for Cisco Unified Operations Manager 8.0).

New and Changed Features

Cisco Unified Operations Manager includes the following updates:

Access to Service Level View from the Diagnostics view. See User Guide Updates for details.

New Fault Monitor and Diagnostics portals.

Device Pool Support.

New Registration Status—backup and unknown/rejected.

Support for Unified Computing System platform for Operations Manager and virtualized Cisco Unified Communications 8.0 and Unity Connection 8.0.

Additional Unified Communications 8.0 solution and application support details are located in the Supported and Interoperable Devices and Software for Cisco Unified Operations Manager.

Newly supported events. This includes AutoFailoverFailed, DeviceRestarted, EndPointLostContact, ExchangeLoginFailed, HardDiskError, LicenseExpirationWarning, LicenseExpired, NoConnectionToPeer, OutOfDiskSpace, ReplicationStopped, VoiceQualityThresholdCrossed, and PhoneUnregThresholdExceeded.

For a list of supported events, see Table E-1 in Appendix E, Events Processed, of the User Guide for Cisco Unified Operations Manager.

Additional documentation is available on Cisco.com. See:

Best practices guides for managing Cisco devices.

Deployment guide.

E-learning video tutorials available from the E-Learning link in the online help. 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

There are critical known software issues that are fixed in patches available locally in the Patches folder of CUOM8.0-with-CUSM8.0.zip file. A README available in each patch zip file contains the installation instructions.

After installing Operations Manager/Service Monitor 8.0, you must go to the Patches folder and install them before using Operations Manager:

CUOM8.0-win-CSCti51775-1.0.zip—In some scenarios on Windows 2008, Operations Manager SIRServer process CPU usage is at 40%.

CUOM8.0-win-CSCtj15812-1.0.zip—In a very large profile with multiple clients accessing Operations Manager, the Tomcat process experiences an Out Of Memory error.

CUOM8.0-win-CSCtj25145-1.0.zip—When ACS is integrated with Operations Manager, asynchronous notifications and event communication to Fault Monitor does not occur.

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


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

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

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

Conditions:

When CSA is installed on a Voice Portal server.

Workaround:

Disable CSA.

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 DB every few seconds because this would create a extra load on the system and impact performance negatively.

Therefore the inconsistency will add 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.

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

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

CSCtj25145

DWR Update does not occur in ACS mode.

A NullPointerException error appears when the DWR tries to validate a device for a username with ACS server.

Workaround:

Download and install the required patch available in the Patches folder of the CUOM8.0-with-CUSM8.0.zip file on the software download web site.

Review the patch README for installation instructions. See Installation Notes for more details.

CSCtj15812

Perf VL - Tomcat experiences Out of Memory error, all dependent process including Tomcat restarted.

In a very large profile with multiple clients accessing Operations Manager, the Tomcat process experiences an Out Of Memory error.

CSCtj08618

RTMT data collection does not start until AXL discovery has occurred.

Discrepancy in registration status of end points of a cluster in Operations Manager.

This happens when the syslogs are not configured on the cluster and 24 hours scheduled CDT AXL data collection has not happened since the addition of the cluster.

Workaround:

You must manually start a CDT Discovery by clicking Run Now on the CDT Discovery UI or rediscover the publisher of the cluster.

CSCtj08146

Audit records are not created for entities that do not have SEP prefix.

Audit records are not created for endpoints such as Unified Personal Communicator that do not have SEP prefixes. For example, MAC address is upcpuser1.

Workaround:

None.

CSCtj00724

Unreachable devices create event count inconsistencies in the tree node.

Event count is updated in all tree nodes that contain unreachable devices. But the unreachable device will not appear in device views or event views upon clicking the tree nodes, except unreachable device events will display only under All Devices and Unreachable Devices nodes.

Workaround:

None.

CSCti98776

Operations Manager documents need to state the use of port 80.

Operations Manager uses port 80, but it is not documented in the User Guide.

Workaround:</B>

Ensure port 80 is available for Operations Manager to reach the phones for XML-based data collection. The data collection could be serial numbers and load ID fetched through discovery.

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.

CSCti87747

CDT cannot handle phones with the same extension in two different partitions.

The IPIF Report displays the partition name incorrectly. This occurs when a phone has been configured with two lines with the same directory number but with different partitions.

Workaround:

None.

CSCti78394

IPIF should support to search extension with "\" symbol.

In the IPIF report filter page, when you search for a phone with extension "\" symbol, an invalid extension error occurs. This occurs when a phone has been configured with an extension number such as \+2000 in Unified CM. This is configured for international dialing support.

Workaround:

Instead of searching with the "\" symbol, search with "+" or with only the extension number.

CSCti65530

FHServer will be in Never started state.

After DM or system restart, FHServer remains in the Never started state for 30 minutes.

Workaround:

From the command prompt, run pdexec FHServer. Make sure the OMHealthMonitor service is running.

CSCti51775

SIRServer process CPU usage is at 40%.

In some scenarios on Windows 2008, Operations Manager SIRServer process CPU usage is at 40%.

Workaround:

Download and install the required patch available in the Patches folder of the CUOM8.0-with-CUSM8.0.zip file on the software download web site.

Review the patch README for installation instructions. See Installation Notes for more details.

CSCti46949

SQ event count is wrong in Device Pool portlet.

During heavy load conditions, the service quality count may display incorrectly in the Device Pool.

Workaround:

Restart the QoVMServer.

CSCti41795

Fault Monitor does not display automatically; requires multiple manual refreshes.

In the following scenarios, sometimes, the Fault Monitor page is not displayed even after you log in:

Operations Manager server has high CPU utilization because of ongoing intense operations such as a a major discovery.

In this case, Web server is not able to cater to some HTTP requests that block the Fault Monitor page from loading completely.

Sometimes, over a slow network or over VPN, the Fault Monitor page takes time to load or does not load at all.

As Fault Monitor has a rich set of UI controls, a significant number of HTTP requests are sent to WebServer the first time Fault Monitor is loaded.

This is because some of the HTTP requests get timed out and the Fault Monitor page is not displayed. Once the pages are cached after the first loading, this scenario rarely occurs.

Workaround:

Manually refresh the browser, using the F5 button for Internet Explorer and Firefox.

CSCti37663

DDV problems for 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, information is not displayed.

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

See CSCtc94859 for information on Cisco Unified MeetingPlace problem.

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) will not work properly.

Error and warning message 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.0.

CSCth52193

Extensions updated in IPIF throughout Audit table deleted.

Newly added phone extensions are deleted from phone reports within four hours. Extensions can also get deleted if the existing extension is changed.

Audio/Video Phone report shows the newly changed extension for the next four hours. After that, it reverts to displaying the old extension.

Conditions:

This occurs when a new extension is added to existing phone or an existing extension is changed in a phone and the phone is reset.

Workaround:

Manually start a CDT discovery using Administration > Auto Discovery Configuration.

After the discovery is complete, Phone Reports include the newly added extension or changed extension in its reports.

CSCth07566

Popup windows from mega menu are not properly sized.

All the popup screens are appearing as full screens. Proper sizing should be provided for these popup 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 extension, instead of showing 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. Then 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.

2. Restart the daemon manager to apply the changes.

3. 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, information is not displayed.

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

See CSCtc94859 for information on Cisco Unified MeetingPlace problem.

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

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.

CSCta64842

ErrCode 10 displayed for NAM properties.

This occurs when you navigate down from a Service Quality Alerts Display to an Event ID page and click a 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.

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.

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.

At times some of the system and environmental parameters of Unified Contact Center Express, appear as NA.

Workaround:

None.

CSCsw69457

Need the ability to deselect CUCM nodes from Notification Criteria.

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

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:

If you need to select the clusters, use the Cisco Unified Communication manager or Cluster OGS group or other groups such as the 78XX media servers to select CUCM.

You can then deselect the CUCM in those other groups.

CSCsv09130

Flash memory instability can occur in SLV client during burst events.

The Service Level View client can become unresponsive and may start sending messages after triggering 700 to 2,000 device unresponsive burst events.

This may be caused by a network connectivity 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 dialog:

A script in this movie is causing Adobe Flash player 9 to run slowly. If it continues to run your computer may become unresponsive. Do you want to abort the script?

Workaround:

Close all existing Service Level View clients and start a new client after the burst events have stopped. 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

Personalized Reports 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.

CSCsr19193

Unreachable devices are included in Unmanaged Device Report.

Discovery Devices with no SNMP credentials or no IP Connectivity are added to the Unmanaged Device report. These devices should be listed as Unreachable with an appropriate Reason Code.

This impacts the ability to verify the completed Discovery because the Unmanaged Report does not include Reason Codes.

Workaround:

None.

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.

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.

CSCsl41124

Launching past times T1 PRI Channel Status performance graph shows wrong graph.

This is caused by a limitation in the Fusion graphing tool and averaging calculation in TGU. This means that an accurate graph cannot be plotted.

Workaround:

This will be fixed in the next release.

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,

Personal Assistant is unable to launch Personal Assistant Administration 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).

CSCta37313

Event Monitor component of OM, logs the event details that are dropped because of flood conditions.

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

Sometimes, all dropped events are not logged in the associated log files EPMDroppedEvents.log or ClearedDroppedEvents.log.

Workaround:

None.


Resolved Problems

The following software problems were resolved in Operations Manager 8.0. For information on bugs that are not included below, see the Cisco Software Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/home.pl.

Table 2 describes problems that were fixed in this release.

Table 2 Problems Resolved in Operations Manager 8.0 

Bug ID
Summary

CSCtf42170

SSM login to OM WebServices works successfully

CSCte75121

Environment variables are shown for ASR

CSCtd93443

IBM MCS server support for monitoring hardware information works successfully

CSCtd42122

Voice Mails Ports status is updating dynamically

CSCsz42608

Environment variables for Cisco Unified Contact Center installed in 7845-I2 display correctly.

CSCso67158

Duplicate of CSCsw46556, Correct error messages appear if there is an auto-discovery failure.

CSCta64842

NAM properties display correctly.


Documentation Updates

After installation, review the Known Problems in Operations Manager and Installation Notes section for required critical patch information.

Go to the Patches folder of the CUOM8.0-with-CUSM8.0.zip file on your local server or to the Operations Manager software download web site. Review the patch READMEs for installation instructions.

User Guide Updates

The following updates were not included in the User Guide for Cisco Unified Operations Manager 8.0.

You can now access the Service Level View (SLV) map from the Diagnostics view. Access the SLV map by clicking on the Service Level View icon in the Cluster Summary view or from the Server Summary view portlet.

To use this new functionality, you must download the updated Operations Manager zip file (CUOM8.0-with-CUSM8.0.zip dated 12/3/10) on the Cisco.com software download site.

If you have previously downloaded the 8.0 zip file, you should backup the current 8.0 data, uninstall 8.0, then install the new image from the download site, and restore the previous backup. Instructions for migrating data to 8.0 are included in the Installation Guide for Cisco Unified Operations Manager 8.0.

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.

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 3 describes the product documentation that is available.


Table 3 Product Documentation 

Document Title
Available Formats

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

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

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

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

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

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 4 describes the additional documentation that is available.

Table 4 Related Documentation 

Document Title
Available Formats

Release Notes for Cisco Unified Service Monitor 4.0

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 4.0

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


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

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.