Table 2 Known Problems in Operations Manager
Bug ID
|
Summary
|
Explanation
|
CSCsv33965
|
HOT14 - L and VL - IPIF Major Discovery Hang.
|
IP Phone Discovery hangs. When you select Device Management > Inventory Collection > IP Phone > Collection Status the phrase "Discovery in progress... display does not disappear" displays. This can happen when a device does not close its connections properly.
Workaround: Restart the device. You can open a command prompt on the Operations Manager server and run the netstat command to identify the device which has a high number of open HTTP connections.
|
CSCsv29289
|
Inconsistency in data collected by GSU.
|
The primary rate interface (PRI) utilization for Unified Communications Manager incorrectly considers D channels of the registered gateways for utilization calculation. There are PRI's registered to the CCMs. Workaround: None.
Operations Manager reports the utilization of the CCM PRI (from the registered gateways) based on the total channels including the D Channel.Therefore, the total channels considered while calculating utilization is one more per PRI, which will result in lesser utilization than actual.
|
CSCsv09130
|
Service Level view intermittent error messages diaplay due to event burst and Internet Explorer client crash.
|
The Service Level View client becomes unresponsive and starts sending intermittent error messages after receiving 700 to 2,000 unresponsive device events. This may be a result of network connectivity issues to Operations Manager. Internet Explorer may crash in this situation.
When a large number of devices become unresponsive at the same time, there are a large number of events generated. These changes are sent to the Service Level View which causes memory instability in the flash module in Internet Explorer.
Workaround: Close all existing Service Level View windows and open a new one after the event burst period is over.
|
CSCsu91758
|
Fault History report contains invalid event ID.
|
Some event ID numbers may display incorrectly when the Alert and Event History Report is displayed in an Excel spreadsheet. This occurs if the event ID contains certain numbers. The wrong format is a result of an Excel limitation which displays numbers such as 00003E8 as 3.00E+08.
Workaround: Open the report in a text reader such as Notepad or Wordpad, which will show the right event ID.
|
CSCsu73512
|
SIP application servers connected by SIP trunk do not show up in the Service Level View.
|
The SIP application is not shown on Service Level View. If the SIP application is configured as part of route list/route group, then it is shown in the Route List report in the Service Level View.
Workaround: None.
|
CSCsu74459
|
RPC communication is still on between Operations Manager and Cisco Unity device even though the device is not managed.
|
RPC keep alive packets are exchanged between Unity devices and Operations Manager server even after the devices are deleted from the server. For example, the Unity server was managed byOperations Manager, then deleted later but RPC packet continue to be exchanged.
This happens when the Cisco Unity device status is initially marked Fully Managed in Operations Manager but later the device is deleted from Operations Manager.
Workaround: Restarting daemon manager resolves this issue.
1.  Stop the CiscoWorks daemon manager by entering net stop crmdmgtd.
2. Wait 1 to 15 minutes for the daemon to stop.
3. Start the Ciscoworks daemon manager by entering: net start crmdmgtd.
|
CSCsu73548
|
Operations Manager counts phones with multiple extensions wrongly.
|
Operations Manager shows separate records for each phone line (extension number) in phone reports.
This happens randomly when there are multiline phones with same extension. The expected behavior is that only single row will be shown for multiline phones with same extension.
Workaround: None.
Operations Manager doesn't show multiline phones with same extension numbers as different records in the All Phones report. Operations Manager some times shows some of the multiline phones with same extension as two different records which is not expected behavior. The physical phone count will be not be affected because of this.
|
CSCsu73532
|
Operations Manager cannot monitor Extension Mobility enabled phones.
|
Some of the Extension Mobility phones are missing in the Operations Manager Phone report. Extension mobility phones exist in the network.
Workaround: None.
Operations Manager currently doesn't support Extension Mobility Phones in Unified Communications Manager due to lack of MIB instrumentation in Unified Communications Manager.
|
CSCsu69664
|
Phone unregistration status issue.
|
Phone status changes are not getting updated in the phone reports. This occurs when there are large numbers of phones in the system.
Workaround: To increase the value of ccmPhoneStatusUpdateStorePeriod to 3600, perform a SNMP set from the Device center view where the values are set as follows:
•Object ID: .1.3.6.1.4.1.9.9.156.1.9.5.0
•Object Type: Integer
•Value: 3600
For example, snmpset [-d] [-p port] [-r retry] [-t timeout] -v 2 host community ccmPhoneStatusUpdateStorePeriod Integer 3600
|
CSCsu69638
|
Phone Selection issue in PR.
|
An error displays in Personalized Reports when selecting more than 5,000 records in PR phone adding.
Workaround: To fix this problem:
1. Select Notification > Notification Criteria > ADD > Add Phone-Based Criterion, then select the phones.
2. Selected phones will appear in the text box. Copy the selected phones to Notepad.
3. Select Personalized Report > Configure Report.
4. Select phones and add the phones From Known list.
5. Paste previously selected phone records to the text box.
6. Click on Apply. Phones are added to the Personalized Report.
7. Click Save to save the Personalized Report.
|
CSCsu69504
|
Service Level View Adobe Flash Client Crash.
|
In some desktops, where DEP is enabled or improper Adobe Flash plug-in installation is present or IE crashes while visiting some of the Adobe Flash enabled sites, the Service Level View client may crash after few hours. This can happen often with Adobe Flash Player 9, and rarely with Adobe Flash Player 8.
Workaround: Relaunch the Service Level View client to continue using it.
|
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: Need to have at least one major discovery cycle of major discovery scheduled in a day. To avoid this issue, do not delete any of the default schedules.
|
CSCsu50989
|
Dashboards hang during device rediscovery.
|
While device discovery is occurring, some of the dashboards in Operations Manager respond very slowly and some time hang, get stuck and stop at a gray page, or displays a Page Not Found error. This happens through out the complete discovery cycle.
There is no work around. Dashboards will respond more quickly after the discovery is complete.
|
CSCsu35212
|
Managed Views enabling is not consistent.
|
When subgroups are added via OGS under a supergroup for which all views (Service Level View, Alerts and Events display, and so on) are already enabled, by default the sub-groups also have their views enabled when created. Though the managed views page shows as if the sub-groups also have the views enabled, they are not seen in Service Level View.
Workaround: After creating the subgroups, make sure that you deselect the check boxes which are automatically selected during subgroup creation and click on Apply. Then reselect the subgroups and click Apply. This should fix the issue and all subgroups should appear in Service Level View, Alert and Events display, and all displays.
|
CSCsu22879
|
Previous and Next buttons are disabled after Search option in Cisco Unified Communications Manager Express Report.
|
While doing a search on Service Level View reports (Cisco Unified Communications Manager Express Report, Unmanaged Report, Gateway Report, and so on, except for RLRG Report), the Next button is disabled no allowing you to go to the next result page. Clicking Clear again when the normal report is loaded clears the results off, but the Next button is still disabled.
Workaround: In search result mode, when the Next button is disabled, you can change the page size to include more entries in a single page. You can also refine the search to reduce the search results to one page. After clicking Clear, if the Next button is disabled, refresh the browser by clicking F5 resolves this issue.
|
CSCsu22811
|
UserCleared and Acknowledged updates don't show on the user interface immediately.
|
If the user selects certain events in the events display and then manually clears or acknowledges them then it may happen that the status does not change from Active to UserCleared or Acknowledged immediately for all the selected events. Some events can show the status as UserCleared/Acknowledged, where some will still show the status as Active.
The problem will be more prominent if the events to be cleared/acknowledged are greater in number as some time will be taken to process them.
Workaround: To update status, click the Refresh button on that page. There is no automatic refresh of events display.
|
CSCsr96863
|
Operations Manager generates CTILinkDown active/clear event pair when CTI mgr is up.
|
Operations Manager generates CTILinkDown active event followed by CTILinkDown clear event when Cisco CTIManager service status is changed.
This occurs when CCM is monitored by Operations Manager, if Cisco CTIManager service on CCM is stopped/deactivated, started/activated, Operations Manager may generate CTILinkDown active event then generate CTILinkDown clear event after couple of minutes.
Workaround: None.
|
CSCsr84351
|
Operations Manager 2.1 InventoryCollector shutting down in pdshow and UI.
|
InventoryCollector process is showing shutdown by pdshow command. But device addition and deletion are all going fine.
Workaround: Communication between CS registry and process start command has broken. Restarting process again resolves the issue.
|
CSCsr59911
|
Selecting Location in Performance shows error.
|
In a network that consists of a medium load (10,000 phones and 1,000 devices), when you click on the location for any Cisco Unified Communications Manager in a cluster with close to 500 locations it may not show all the locations configured in the system, but shows an error.
This happens only with IE version < 7 and when the number of locations configured on the CCM are more than 375.
Workaround: Manually enter the location name (instead of clicking on the popup), then launch the graph.
|
CSCsr48109
|
Polling leaves gaps in data collection.
|
On a medium/large Operations Manager machine the performance polling may miss some cycles and cause gaps in data collection. This occurs when voice utilization settings are enabled for multiple groups like Unified Communications Managers or gateways, and if the number of devices are more than 200. This can be observed in the data csv files in NMSROOT\data\gsu\_#GSUDATA#_ folder. The device-specific CSV file will have data with some timestamps missed. For example, for a default polling interval of 4 minutes, you may see data gaps in the range of 8 or 12 minutes or multiples of 4 minutes. Ideally the data should be spaced 4 minutes apart and no more. This effect will be reflected in the Detailed Device View and performance graphs where the timestamp gaps are indicated.
Workaround: On Operations Manager where many devices are getting polled (usually medium/large), we recommend you increase the number of collector threads. For devices in the range of 300 to 600, the number should be around 40 collector threads and for large machines with more than 600 devices, the number should be 60. This parameter is configurable in the file gpf.properties under NMSROOT\gpf\ folder. The parameter to be modified is "NumOfDCThread". The default value is 15.
The problem does not occur if the polling is not enabled for multiple groups. If the specific group where the polling settings are enabled (like call managers) have many devices the problem is seen. This problem has been reported in a performance setup and currently no customer has reported this issue.
|
CSCsr45509
|
DFM and Operations Manager hang with more than two page files on the system.
|
InventoryCollection stops processing at 10% and the brcontrol execution stops processing with high CPU consumption. This occurs when your system has more than two page files.
Workaround: Configure the system with two page files or less.
|
CSCsr23045
|
Auto Discovery hangs, no transition to Inventory Collection.
|
Auto-Discovery stops processing and doesn't proceed to inventory collection.
Workaround: Restart Auto Discovery by pressing the Cancel button in the Device Management user interface.
|
CSCsr20195
|
Operations Manager does not support more than two page files on the system.
|
Inventory Collection is stuck at 10% and the brcontrol execution gets stuck with high CPU consumption. This is a limitation of the Operations Manager due to the SMART server.
This occurs when the system has more than two page files.
Workaround: Do not use more than two page files on the operating system.
|
CSCsq21596
|
SIP Trunks between Unified Communications Manager clusters should display as an ICT cloud.
|
SIP trunks are displayed as endpoints in Service Level View, whereas H.323 intercluster trunks are shown as a cloud in the Service Level View. Clicking the ICT cloud displays the topology cluster of the remote Unified Communications Manager cluster.
This has been observed with Cisco Unified Operations Manager.
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: Create a dummy "telephony config" on the CME device and then discover it in Operations Manager. Use the "telephony-service" command in config mode to enable skinny- based CME on the gateway.
|
CSCsq00168
|
Alert Details page shows only first 1,000 events.
|
When over 1,000 events occur or exist for an alert, the Alert Details page for that alert displays only the first 1,000 events. The remaining events are not displayed.
Workaround: The remaining events can be seen in Fault History by launching the report for that alert ID.
|
CSCso67158
|
An error is displayed when the Operations Manager credential is changed in Cisco Unified Service Statistics Manager > Modify.
|
A confusing message displays when using the Cisco Unified Statistics Manager > Modify window: "Unable to validate CUSSM license information. Please check the OM licensing info..."
Workaround: Change the Operations Manager password to the original password that Service Statistics Manager used to discover Operations Manager.
|
CSCsm59818
|
Operations Manager does not recognize gateways as MGPC devices when dial control is not needed.
|
You cannot create performance graphs in Operations Manager for Media Gateway Control Protocol (MGCP) voice gateways. The performance graphing option does not appear in the right-click menu in the Service Level View for the device.
This occurs when the device is configured using the new MGCP configuration, for example with PRI Backhaul or SS7 Signaling where dial peers do not need to be configured.
Workaround: Upgrade the gateway to Cisco IOS version 12.4(17a) or higher, then rediscover the device in Operations Manager.
|
CSCsm54654
|
The MWIOnTImeExceeded event is not generated.
|
When an MWI Synthetic Test on a Cisco Unity or Cisco Unity Express is set up and you try to change the MWI On Time Threshold value (default value 5) in the Polling and Thresholds page, the changes do not take effect correctly.
For Cisco Unity Express, there is no change to the value. For Cisco Unity, the value is changed to 99999 and the MWIOnTImeExceeded event is not generated.
Workaround: None.
|
CSCsl88020
|
Cluster connectivity is not shown for Cisco Catalyst 6000 devices.
|
Cluster connectivity is not shown for MGCP gateways that are registered to Cisco Unified Communications Manager. This causes performance data not to be collected for this device.
If gateways are registered to Cisco Unified Communications Manager with the MGCP protocol, sometimes the VIC module does not create connectivity information for this device to Cisco Unified Communications Manager. Due to this issue, Operations Manager fails to do MGCP performance data collection for this gateway.
This issue can occur because of any of the following conditions:
1. A Cisco Unified Communications Manager SOAP-related defect. It is mostly noticed in Cisco Catalyst 6000 gateways and gateways registered with multiple IP addresses.
2. The gateway has two IP addresses and it is registered with Cisco Unified Communications Manager with one IP address and managed in Operations Manager with the other IP address.
3. The gateway was added before Cisco Unified Communications Manager in Operations Manager.
Workaround: The following numbered workarounds correspond to the numbered conditions above.
1. Make sure that Cisco Unified Communications Manager has the fix for CSCsm02537. It is available with the following Cisco Unified Communications Manager builds (and later):
– 005.001(003.1114.001)
– 005.001(003.9901.103)
– 006.000(001.2125.001)
– 006.001(001.9901.049)
– 007.000(000.39000.029)
– 007.000(000.9691.002)
2. Delete the gateway device from Operations Manager and add the IP address that is registered with Cisco Unified Communications Manager.
3. Rediscover the Cisco Unified Communications Manager in Operations Manager.
Note The Operations Manager performance collection module uses VIC cluster connectivity information to do the MGCP performance polling. If for any of the reasons listed, the VIC fails to create the cluster connectivity, the MGCP performance polling may not happen.
|
CSCsl50238
|
Service Level View scalability needs to be improved.
|
When there are large numbers of Cisco Unified Communications Manager Express (CME) clouds (greater than 150) or device nodes (greater than 150) in a single Cisco Unified Communications Manager (CCM) cluster, the Service Level View client takes a long time to load and eventually hangs. The map view becomes illegible and cluttered.
This occurs when there are more than 150 Cisco Unified Communications Manager Express clouds. It may also happen when there are 150 or more H323/MGCP/APPSERVER/SIPAPP/SRST devices in a single cluster. Only the gateways which are not configured under any RouteList-RouteGroup (RLRG) are shown in a cluster view contributing to this issue. Gateways under RLRG do not affect the performance of the Service Level View client. If the total number of devices (regardless of which cluster they are present in) exceeds 150 in the Service Level View, the web browser starts slowing down and hangs at the end.
Workaround: There is no workaround if you want to manage those 150+ Cisco Unified Communications Manager Express devices or hundreds of gateways outside of Route List/Route Group. In order to use the Service Level View, you should delete some of the from Operations Manager. Or, you can deploy another Operations Manager server to offload a portion of the managed devices from this server.
|
CSCsj43765
|
Cisco Unified Communications Manager Express appears under the H323 gateway group in the Service Level View.
|
When an ICT is configured between a Cisco Unified Communications Manager Express and a Cisco Unified Communications Manager, the Cisco Unified Communications Manager Express appears under the H323 gateway group in the Service Level View.
Workaround: None.
|
CSCsj20070
|
SRST operations link does not open.
|
The SRST page and the Service Level View may not open.
Workaround Restart the appropriate service:
•For the SRST page, restart the SRSTServer service.
•For the Service Level View, restart the Inventory Collector.
|
CSCsk85046
|
Operations Manager: A&E CTILinkDown present on non CTI based servers.
|
Operations Manager generates CTILinkdown failures in Alert and Events for servers which do not run CTI Manager services (Music On Hold Servers). Operations Manager reports this as a CTILinkDown instead of a CTIServicedown. There is also no provision to disable this message in the Detailed Device View, so there is no way to stop the false alarms.
Conditions This occurs when any Unified Communications Manager with CTI Services disabled.
Workaround: None.
|
CSCsi78419
|
Cisco Unity Connection 2.x attributes are not displayed in the Detailed Device View.
|
Cisco Unity Connection 2.x attributes are shown as either N/A or 0 in the Detailed Device View. This only occurs on Cisco Unity Connection 2.x.
Workaround: None.
|
CSCsi10168
|
Exporting reports to PDF format generates the filename as "export.pdf."
|
When exporting reports to PDF format, the filename is always "export.pdf," regardless of what type of report is being exported.
This problem only occurs when you are using Windows XP with Internet Explorer 7.0 and Acrobat Reader 6.x.
This problem does not occur with Acrobat Reader 7.x and later.
Workaround: When exporting reports to PDF format, make sure your system is using Acrobat Reader 7.x.
|
CSCsf98008
|
In the Detailed Device View for negative synthetic tests, the success criterion for end-to-end calls and phone registration always shows availability as 100 percent.
|
In the Detailed Device View for negative tests, the availability is displayed as 100 percent and failure as 0 percent. These two settings are not applicable to the negative synthetic tests. The Detailed Device View should display N/A for this field.
Workaround: None.
|
CSCse78310
|
Detailed Device View for Cisco Unity devices displays incorrect information.
|
For Cisco Unity releases prior to 4.2, the Detailed Device View shows the following:
•Current Number Of Licensed Subscribers as Not Available.
•Maximum Number of Licensed Subscribers as Not Available.
•Current Number of Inbox Licenses as Not Available.
•Maximum Number of Inbox Licenses as Not Available.
•Even though Cisco Unity 4.0(4) is upgraded to 4.0(5), the version on all services is still shown as 4.0(4).
Workaround: Upgrade to Cisco Unity 4.2, then run RSK Configuration Wizard.
Note This workaround applies only to the Cisco Unity service version issue. The workaround does not fix the first four counter issues mentioned above. There is no workaround for those issues.
|
CSCse75607
|
Unreachable devices are displayed in Operations Manager device management.
|
If the SNMP agent on a device is working intermittently, Operations Manager may discover the device, but may move it to the unreachable state during inventory collection.
This occurs because the device was responding to SNMP queries during automatic discovery, then did not respond to SNMP queries during inventory collection.
Workaround: None.
|
CSCsd58055
|
The Devices report may show a device's capability as UnknownMDFType.
|
The Devices report displays a device's capability as UnknownMDFType when the device is not supported by Operations Manager.
Workaround: None.
|
CSCsd22730
|
Automatic discovery does not discover Cisco Unity Express devices.
|
During automatic discovery, using either ping sweep or CDP, Cisco Unity Express devices are discovered. These devices go into the Unreachable state.
Workaround: Manually add Cisco Unity Express devices into Operations Manager.
|
CSCsd21804
|
Learning appears in the Device Type column of the Alerts and Events display.
|
On the Alerts and Events display and the Alert Details page, you may see Learning in the Device Type column. Learning indicates that Operations Manager was discovering the device when the alert occurred. The following events can trigger an alert during discovery:
•Duplicate IP (might be generated for any type of device)
•Events for media servers only:
–FanDown
–FanDegraded
–TemperatureSensorDown
–TemperatureSensorDegraded
Workaround:
•Simply wait; the actual device type is reflected in the Device Type column when new events occur.
•Look up the current state of a device from the Detailed Device View, which always displays the current state.
|
CSCsc87486
|
In the Personalized report, not all the graphs are shown for the node-to-node test violations.
|
In the Personalized report for node-to-node tests, 24-Hour History shows the graph for only the following metrics:
•Source-to-Destination Packet Jitter.
•Destination-to-Source Packet Jitter.
•Average Latency.
No other graphs are displayed. Workaround: None.
|
CSCsc61752
|
In the Service Level View, when Cisco IP Contact Center (IPCC) is part of a user-defined view, it only appears in the tree view (view pane).
|
User-defined views in the Service Level View do not show Cisco IP Contact Centers in the map display pane. They only appear in the view pane. Workaround: None.
|
CSCsc44538
CSCsk21367
|
The DFMServer and VHMServer processes are not registering with the broker.
Devices that are added to Operations Manager when it is in this condition exhibit the following behavior:
•ALL devices become stuck in the Inventory Collection in Progress state.
•All devices move to the unreachable state.
|
After installing Operations Manager and rebooting the server, either the DFMServer, or the VHMServer, or both processes do not start. There is no sm_server.exe instance (or there are only two sm_server.exe instances) in the Windows task manager.
Workaround: Perform the following:
1. Run net stop crmdmgtd.
2. Wait 15 minutes.
3. Run net start crmdmgtd.
After the CPU cools down, check the Windows task manager. There should be four instances of sm_server.exe.
The output of the brcontrol command should show both DFM and VHM.
For example:
C:\Program Files\CSCOpx\objects\smarts\bin>brcontrol
Broker is located at: IPCOM-daily:9002 Started: Jan 06
10:21:09 2006
Domain Host Name Port Proc ID State Last
Chg Time
------ --------- ------ ------- -----
-------------
DFM IPCOM-daily.cisco.com 2163 14120
RUNNING Jan 06 16:18:03 2006
VHM IPCOM-daily.cisco.com 2206 8856
RUNNING Jan 06 16:18:04 2006
|
CSCsc26996
|
Next Discovery, in the Device Management: Summary page, displays the incorrect time.
|
The problem is due to a registry setting in Windows that appears for certain time zones for which Daylight Saving Time changes are applicable. If the check box for Daylight Saving Time is not checked, problems occur when converting valid date strings to a Date object. This registry key remains even if the time zone of the machine is switched to another time zone for which Daylight Saving Time is not applicable.
Following is the registry information:
HKEY_LOCAL_MACHINE\CurrentControlSet\Control\TimeZoneInformation
DisableAutoDaylightTimeSet REG_DWORD 0x00000001(1)
Workaround: If the system is in a time zone that has Daylight Saving Time, check the Automatically adjust for Daylight Saving Time changes check box.
If the system is in a time zone for which Daylight Saving Time is not applicable, but the registry key is present and set to 1, do the following:
1. Change to a time zone for which Daylight Saving Time is applicable.
2. Check the Automatically adjust for Daylight Saving Time changes check box, and click Apply.
This will cause the registry key to disappear. Now switch the machine to its present time zone.
|
CSCsc12967
|
Exchange services are displayed as stopped when Cisco Unity is configured for failover.
|
When Cisco Unity is configured for failover mode, Operations Manager shows Microsoft Exchange Services as being stopped. Workaround: None.
|
CSCsc10167
|
On the Alert Details page, once a tool is launched, you cannot relaunch it.
|
In the Alert Details page, once you select a tool from the Launch Tools menu you cannot launch the selected tool again until you choose another tool.
Workaround: After launching a tool, to launch the same tool again, you must either select a different tool or select the Launch Tools option in the menu.
After doing either of these actions, you can relaunch your original choice.
|
CSCsb83202
|
OperationallyDown events for voice ports are being cleared automatically, even though the port is still down in the router.
|
The operationallyDown event for voice ports in routers are being cleared even though the port continues to be down.
Operations Manager only sends an operationallyDown alarm if the operating status (the OperStatus for this router) is in one of the following states:
•Down (2).
•Testing (3) (If not suppressing testing-related alarms).
If, during a polling cycle, the ifOperStatus is Down (2), the alarm is generated. If, during the next polling cycle, the ifOperStatus is Dormant (5), the operationallyDown alarm is cleared because it is not Down (2) or Testing (3).
Related bug: CSCsb87389.
Workaround: None.
|
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 states that there is not any data available for the last 48 minutes. This error occurs due to an incorrect system uptime in the device.
This error occurs in specific Cisco IOS versions. Refer to the Cisco IOS IP SLA bugs, CSCin66315 and CSCeb46870.
Workaround: Upgrade the Cisco IOS version, or reboot the source device. For details, see CSCin66315 and CSCeb46870.
|
CSCsb66977
|
Voice application software (for example, Cisco Conference Connection, Cisco Unified CallManager, or Cisco Emergency Responder) goes to the Unsupported state.
|
On some servers that have voice application software installed, rebooting causes the server to go to the Unsupported state in Operations Manager.
The problem occurs on servers that have the Windows operating system version upgraded to 2000.2.7sr3 or 2000.4.1.
The problem is caused by an incompatibility between the CDP driver installed by the voice application and Microsoft Security hotfix MS05-019. For more information regarding the hotfix, see the Microsoft website for more details.
Workaround: Upgrade the CDP driver on the voice application server.
1. Uninstall the CDP driver from the voice application server.
2. Run the following command:
C:\Program Files\Cisco\Bin> cdpinstaller -v -u
CISCO_CDP
3. Log on to any Cisco Unified CallManager 4.1 server and copy the following files to the voice application server:
•CDP.SYS (C:\Program Files\Cisco\Bin)
•CDPintf.dll (C:\WINNT\system32)
•CDPInstaller.exe
•CDP.inf
4. Install the new CDP driver by running the following command:
C:\program files\Cisco\Bin> cdpinstaller -v -l
"C:\Program Files\Cisco\Bin
\cdp.inf" -c p -i CISCO_CDP
|
CSCsb60614
|
Cluster name changes are not reflected in Operations Manager.
|
If you change the name of a cluster in Cisco Unified CallManager after the devices have been added to Operations Manager, the name change does not occur in Operations Manager. This is the case even after performing inventory collection.
Workaround: Delete the devices in the cluster from Operations Manager and then add the devices in again.
|
CSCeb62542
|
cdspCardsStatusTable is not populated.
|
No DSP records display for Voice Interface Cards (VICs) that are supported by the following network modules:
•NM-1V
•NM-2V
•NM-HDA
Affected record type: 109.
CISCO-DSP-MGMT-MIB is not supported on the listed network modules. This bug applies to all devices that support them.
|
CSCdm87395
|
No support for CISCO-POP-MGMT MIB on 2600 platform
|
The number of CAS ports is incorrect, and CAS channel status is missing for all supported network devices that run Cisco IOS except for Cisco Universal Gateways. Gateway Statistics Utility (GSU) always reports the number of CAS ports as follows:
•24 ports for each T1
•31 ports for each E1
For example, if a device has two T1 ports, Operations Manager reports the total number of T1 CAS ports as 48, no matter how many CAS ports are configured on the device.
Affected record types: 102, 112, 113.
Except for Cisco Universal Gateways, the network devices that run Cisco IOS do not support CISCO-POP-MGMT-MIB.
|
