Release Notes for Cisco netManager - IP Infrastructure 1.0

Cisco netManager is a data and IP communications network monitoring solution that provides standards-based monitoring of network devices, services, or applications on TCP/IP and Windows. You can use Cisco netManager to visualize, monitor, diagnose, and report the data status of your IP communications deployment.

Cisco netManager lets you initiate monitoring of devices in your network and execute actions based on device state changes, so you can identify network failures before they become catastrophic.

Note The ability to view and monitor IP communication devices depends upon the type of licensing you have. See the Quick Start Guide for Cisco netManager for licensing options.

Product Documentation

Note The documentation on the site from which you downloaded the product is the most up-to-date.

Documentation Errata

Table 1 Product Documentation
Document Title	Available Formats
Release Notes for Cisco netManager 1.0	PDF on Cisco.com.
Quick Start Guide for Cisco netManager 1.0	PDF on Cisco.com.
User Guide for Cisco netManager	PDF: •PDF on Cisco.com. •Accessible from online help—Refer to the PDF on the download site instead.
Context-sensitive online help	Available by clicking the Help link in the upper right-hand corner of the window.

The online help and PDF versions of User Guide for Cisco netManager installed with the software contain the following errors. The versions on Cisco.com contain the correct information.

Events generated by Cisco netManager are documented in Chapter 14, "Using Full Reports" of User Guide for Cisco netManager. The information in Table 14-4 is incomplete. The following tables list the missing information.

Note The ability to view certain events depends on the type of license you have purchased. See the Quick Start Guide for Cisco netManager to view the different licensing options available.

Table 2 List of Cisco Unity Express Events
Event	MIB
CUE Application Status Change	ciscoUnityExpressApplAlert
CUE Storage Issue	ciscoUnityExpressStorageAlert
CUE Security Issue	ciscoUnityExpressSecurityAlert
CUE CCM Connection Lost	ciscoUnityExpressCallMgrAlert
CUE Resource Exhausted	ciscoUnityExpressRescExhausted
CUE Backup Failed	ciscoUnityExpressBackupAlert
CUE NTP Issue	ciscoUnityExpressNTPAlert

Table 3 List of Cisco Unified Communications Manager Express Events
Event	MIB
CCME Ephone Deceased	ccmeEPhoneDeceased
CCME Ephone Login Failed	ccmeEphoneLoginFailed
CCME Ephone Registration Failed	ccmeEPhoneRegFailed
CCME Ephone Registrations Exceeded	ccmeEphoneUnRegThresholdExceed
CCME Key Ephone Registration Change	ccmeKeyEphoneRegChangeNotif
CCME Livefeed MOH Failed	ccmeLivefeedMohFailedNotif
CCME Maximum Conferences Exceeded	ccmeMaxConferenceNotif
CCME Night Service Change	ccmeNightServiceChangeNotif
CCME Status Change	ccmeStatusChangeNotif

Traps generated by Cisco netManager are documented in Appendix A, "Processed SNMP Traps and Corresponding Cisco netManager Events" of the User Guide for Cisco netManager. The "Processed CPQHLTH-MIB Traps" should be removed. These traps are not supported.

Third-Party Company Name in Cisco netManager Console

When you access the Cisco netManager console and online help, you will see the logo and product name of a third-party company (WhatsUp Gold by Ipswitch, Inc.).

Known Problems

Table 4 describes problems known to exist in this release. Problems that do not have associated bug IDs are described in Other Known Problems.

Table 4 Known Problems in Cisco netManager
Bug ID	Summary	Explanation
CSCsi34066	Handle leak with particular virus detection software	Handle leaks for NMService increase when McAfee virus detection software is on the Cisco netManager system. Note This problem has not been observed with other virus detection software, such as Norton. Workaround: Remove McAfee virus detection software from the Cisco netManager system.
CSCsi48134	In workspace view Problem Areas 1, no values are displayed for portlets	There is no workaround for this problem.
CSCsi56457	Detailed Device View shows incorrect Unified Communications Manager version	For Unified Communications Manager 6.0, Detailed Device View shows version 5.0 instead. This is due to a known problem (CSCsk02405) in Unified Communications Manager. There is no workaround.
CSCsi63015	"Unable to determine default browser" error appears when Cisco netManager is launched.	This error appears if Cisco netManager is launched using a browser version that is not supported (for example, Firefox). Workaround: Set Internet Explorer 6.0 as the system's default browser.
CSCsi76739	Drilled-down view for selected phone removed after refresh cycle	In the Service Level View, the map display pane refreshes every 2 minutes. Any phone that was selected before the refresh is no longer selected afterward. Workaround: After a refresh, you must select the phone again from the Phone Search results.
CSCsi88785	JSON Parse Error	Rarely, a JSON Parse Error message appears. If this message appears, it might reappear in 6 to 7 hours. It is otherwise harmless. Workaround: Click OK to dismiss the message.
CSCsj07867	After uninstalling Cisco netManager, some files remain in the installation folders.	In some servers, Cisco netManager uninstallation does not remove all the files from the installation folders. This can also occur if the uninstallation process is cancelled before it completes. Workaround: Run the clean_system.exe script to remove the files: 1. Go to the Windows\System32\cleanup_tools folder. For example, if the operating system is installed on C:, then the folder will be C:\Windows\System32\cleanup_tools. 2. Locate and run clean_system.exe. 3. Follow the instructions provided by the script. Note If clean_system.exe is not available in the Windows\System32\cleanup_tools folder, you can run it from the cleanup_tools folder on the Cisco netManager product CD.
CSCsj22329	MSDE installation fails	Cisco netManager installation may fail to install Microsoft SQL Server Desktop Engine (MSDE) if file and print sharing are not enabled. Workaround: Enable file and print sharing: 1. In the Control Panel, double-click Network Connections. 2. From the Advanced menu, select Advanced Settings. 3. On the Adaptors and Bindings tab, ensure that File and Print Sharing for Microsoft Networks is selected. Note Also, see Other Known Problems.
CSCsj22425	Cisco netManager installation might fail if started from a remote desktop connection or any other software that uses sessions to communicate with the machine.	MSDE has known compatibility issues with Remote Desktop, a feature in Windows 2000 Server (and later versions). Do not use any remote control software that uses sessions to install Cisco netManager. Note Sessionless remote control software, such as VNC, should work.
CSCsl12370	From the Home Page workspace, the Device and Phone Summary portlet displays the error "Some error in query" when adding or discovering a device from the Cisco netManager console.	The Cisco Wireless LAN Controller Status performance monitor might be assigned to a device that is not a Cisco Wireless LAN Controller. Workaround: Delete the device and add it back to Cisco netManager. When prompted to select performance monitors for the device, confirm that the Cisco Wireless LAN Controller performance monitor is not selected.
CSCsj39426	Handle leaks due to multiple trap and syslog receivers	Handle leaks can occur when, in addition to Cisco netManager trap and syslog receivers, third-party trap and syslog receivers run on the server. Workaround: To disable or enable the Cisco netManager trap and syslog receivers, do the following: 1. Open a command prompt and go to <Installation Path>\Cisco netManager\conf; for example: `cd Program Files\Cisco netManager\conf` 2. Run the command TrapReg.vbs with one of these arguments: 0—Disables traps 1—Enables traps `TrapReg.vbs <0\|1>` 3. Run the command SyslogReg.vbs with one of these arguments: 0—Disable syslog receiver 1—Enable syslog receiver `SyslogReg.vbs <0\|1>` 4. Restart Cisco netManager Engine from the task tray.
CSCsj52269	Service Level View and Physical Connectivity View topologies do not appear initially	If Sun Microsystems Java Runtime Environment (JRE) version 6.0 is already installed, after the Cisco netManager installation completes, Service Level View and Physical Connectivity View topologies are blank. Workaround: Reboot the system after installation. The topologies should appear.
CSCsj54892	Memory utilization greater than 100% for Unified Communications Manager 5.0 and later	For Unified Communications Manager, the Detailed Device View page shows Percent Utilization of Physical RAM greater than 100%. This is a known problem in Unified Communications Manager 5.0.1.0 and later running on Linux (CSCsj47638). Workaround: Upgrade to the latest image of Unified Communications Manager. For more information about CSCsj47638 and where it has been fixed, see the Bug Toolkit at: http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl.
CSCsj56733	Event and semaphore handle leaks occur in Service Level View and Physical Connectivity View	A gradual handle leak may be observed from the browser window when viewing the Service Level View and Physical Connectivity View topologies. This occurs in the following cases: •MSXML filter is installed (with Office 2003 Installation). For more information on the symptom and workaround, visit http://support.microsoft.com/kb/841532. Note This website is Copyright � 2007, Microsoft Corporation. •Handle leak due to Flash Eventing mechanism. Workaround: If the Service Level View or Physical Connectivity View appears to be running slowly, close and reopen the browser window.
CSCsj78993	Inconsistent data between detailed device view and individual reports.	The Device Inventory workspace view information displayed in the Device Status workspace (from Device tab, right-click device and select Detailed Device View) may not have the same information presented in the full reports for Fan Status, Power Supply Status, and Processor (CPU) Status. This occurs because the information is collected from different MIBs. There is no workaround.
CSCsj88180	SQL error while installing Cisco netManager	SQL configuration fails during installation, displaying error messages. This happens when MSDE is not installed properly. Workaround: 1. Close the error messages. 2. Create a new registry key and string value: a. Click Start > Run. The Run dialog box opens. b. In the Open field, enter Regedit, then click OK. The Registry Editor opens. c. Create the following registry key: `HKEY_LOCAL_MACHINE\SOFTWARE\ Cisco Systems\Cisco netManager\1.0` d. Create a String Value key named NMSROOT and, for the value, enter the installation folder that you selected during installation. For example: C:\Progra~1\CiscoN~1 e. Close the Registry Editor. 3. From the command line, execute clean_system.exe in the <CD Drive>\cleanup_tools folder. 4. Restart the server. 5. Start the installation again.
CSCsj90477	Unreachable device shows interface status as Up.	If Cisco netManager is set up to collect the same data using Active Monitor polling and Performance Monitor polling for different workspace reports (portlets), the portlets may show different status for the same device. This occurs because the polling cycles are different and the same information being collected for both may lead to a discrepancy in the information reported. For example, if a device interface is in the process of going from Down to Up, Active Monitor polling may register it first as Down. Active Monitor polling will not recognize that the interface is Up until the next time it polls the device. Meanwhile, Performance Monitor may poll the interface and it finds the interface Up. Hence, portlets using Active Monitor polling will show the device interface Down and portlets using the Performance Monitor polling will show the device interface as Up. Workaround: Use only one type of monitor polling for a particular piece of information.
CSCsk06614	The installation wizard sometimes prompts user to reboot server.	After installation, a window may appear asking you to restart the machine. Restart the machine before using Cisco netManager.
CSCsk10117	Cisco netManager fails to start if IP Communicator is installed on the same machine.	IP Communicator and Cisco netManager are using the same port. The default port during installation for IP Communicator and Cisco netManager is port 80. Workaround: Change the port for one of the applications.
CSCsk43135	Cisco netManager discovers FWSM as a workstation	The Firewall Service Module is discovered as a workstation. There is no workaround.
CSCsk63532	The device count displayed in the "Device and Phone Summary" and "Total Devices By Type" workspace reports (portlets) is different.	When a device is rediscovered,the Device and Phone Summary portlet displays an incorrect device count by state (Monitored, suspended, and Unreachable). Workaround: Use the Total Devices By Type portlet to view the correct device count.
CSCsk62614	Launching the client from the Program menu shows cached information.	Starting the Cisco netManager web interface from the Start > Programs menu shows cached information from previous installations. Workaround: Modify the Internet Explorer settings (Tools > Internet Options > General >Settings) so that it checks for newer versions of stored pages.
CSCsk80731	Evaluation license file is not visible during Cisco netManager installation.	This occurs during Cisco netManager installation when there are multiple CD ROM drives and the product CD is inserted in one of the drives. Workaround: 1. When the installation prompts you for the license file, navigate to the CD ROM drive where the product CD is located. 2. From the CD directory, navigate to the license folder. 3. Select the evaluation.lic file. 4. Click Next to proceed with installation steps.
CSCsl12370	From the Home Page workspace, the Device and Phone Summary portlet displays the error "Some error in query" when adding or discovering a device from the Cisco netManager console.	The Cisco Wireless LAN Controller Status performance monitor might be assigned to a device that is not a Cisco Wireless LAN Controller. Workaround: Delete the device and add it back to Cisco netManager. When prompted to select performance monitors for the device, confirm that the Cisco Wireless LAN Controller performance monitor is not selected.

Table Of Contents