Table Of Contents
Release Notes for Cisco Monitor Director 1.1
Obtaining Documentation, Obtaining Support, and Security Guidelines
Description
Product Documentation
Known Problems
Release Notes for Cisco Monitor Director 1.1
These release notes describe the caveats for Cisco Monitor Director 1.1. These release notes accompany the Quick Start Guide for Cisco Monitor Director 1.1 and the online help for Cisco Monitor Director.
Note 
For important licensing information, see the Quick Start Guide for Cisco Monitor Director 1.1.
These release notes contain the following sections:
•Obtaining Documentation, Obtaining Support, and Security Guidelines
•Description
•Product Documentation
•Known Problems
Obtaining Documentation, Obtaining Support, and Security Guidelines
For information on obtaining documentation, obtaining support, providing documentation feedback, security guidelines, and also recommended aliases and general Cisco documents, 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
Description
Cisco Monitor Director is a remote network monitoring and management application that works with one or more instances of Cisco Monitor Manager to provide seamless, centralized network management across multiple small-medium business (SMB) customer sites. Cisco Monitor Director stores network fault data received from associated Cisco Monitor Manager instances and uses this data (which can be selectively filtered) to create monthly reports that summarize a network's health. It also provides the capability to specify that only issues of a certain severity or type generate notification messages, ensuring that a network's administrator is notified of issues as quickly as possible.
The following list summarizes the features that Cisco Monitor Director provides:
•Central dashboard
•Secure communication between customers and resellers
•Syslog reporting
•Real-time alerts and notifications
•License monitoring and inventory alerts
•End of Life/End of Sales reports
•Scheduled monthly reports
Product 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 1 describes the product documentation that is available.
Known Problems
Table 2 describes problems known to exist in this release.
Table 2 Known Problems in Cisco Monitor Director
Bug ID
|
Summary
|
Explanation
|
CSCsg77188
CSCsi21336
|
Unable to view the desktop or user interface for a Windows 2000 server after connecting to it via RDP
|
After connecting to a Windows 2000 server via Remote Desktop Protocol (RDP), you will not be able to view its desktop.
Also, after you install Cisco Monitor on a system, restart the system, and log in to the system using Remote Desktop Protocol (RDP), if you launch the application from RDP, the user interface does not appear, even though the Cisco Monitor Director service has started.
There is no workaround for the first problem. To work around the second problem, first start Cisco Monitor Director on your system after system restart; also, do not use RDP to launch Cisco Monitor Director.
This release does not support use of Windows 2000 Server RDP.
|
CSCse42611
|
Cisco Monitor Director report topology does not display all the nodes
|
If the network topology map in Cisco Monitor Manager is collapsed, the same topology view is displayed in Cisco Monitor Director. In Cisco Monitor Director, the topology does not appear to contain all of the nodes.
To work around the problem, fully expand all nodes in the Cisco Monitor Manager network topology map; future reports sent from Cisco Monitor Manager to Cisco Monitor Director will include the complete topology.
|
CSCse53543
|
User-installed network printers are not visible in the Cisco Monitor Director interface printer list
|
The Print dialog box opens after you select the Print menu option from either the Cisco Monitor Director GUI or the web browser launched from the Monthly Report window. User-installed network printers do not show up in this dialog box.
|
CSCse53543
(continued)
|
User-installed network printers are not visible in the Cisco Monitor Director interface printer list
|
To work around the problem on systems running Windows XP or Windows 2003 Server, do the following:
1. Log onto the system as a user with administrative privileges (preferably as the same user who performed the Cisco Monitor Director installation).
2. If you have not added any printers to the system, add them using the Add Printer function of the operating system.
3. Verify that the printers are available by opening a web browser, selecting File > Print from the menu, and checking the list of printers.
4. Run the Install_Home\PrinterExport\
PrinterExport.bat script by double-clicking the script icon and then following the instructions. Install_Home is the root directory where Cisco Monitor Director is installed. By default, the installation home directory is C:\Program Files\Cisco Systems\CiscoSMB\
Cisco Monitor Director\.)
5. Verify that the printers are available in Cisco Monitor Director by opening the Print dialog box from the application.
To work around the problem on systems running Windows 2000, use the screen capture function and print from the application it uses.
|
CSCse87109
|
Installation/uninstallation of Cisco Monitor Manager and Cisco Monitor Director cannot proceed when antivirus software installed and is disabled
|
When antivirus software is installed and disabled, installing or uninstalling Cisco Monitor Manager and Cisco Monitor Director results in an error, and the installation or uninstallation cannot proceed.
To work around the problem, ensure that any installed antivirus software is running before installing or uninstalling Cisco Monitor Manager and Cisco Monitor Director.
|
CSCsf21496
|
Database backup causes delays in application operation
|
When the Cisco Monitor Director database is being backed up, performing application tasks can take a long time to complete.
To work around this problem, run a backup during nonpeak hours.
|
CSCsg74128
|
Uninstallation or reinstallation of Cisco Monitor Manager and/or Cisco Monitor Director may result in error conditions
|
To avoid this problem, do the following:
1. Ensure that Cisco Monitor Manager/Cisco Monitor Director is not running. For Cisco Monitor Director, also ensure that the Cisco Monitor Director service is stopped.
2. Ensure that there are no open folders containing the application installation directory or its subdirectories.
3. Ensure that the CLI command prompt is not pointing to the installation directory or its subdirectories.
If you receive an error during uninstallation or reinstallation, you can work around the problem by restarting the system when the error messages appears; then, proceed with the installation or uninstallation.
|
CSCsh85319
|
Cisco Monitor Manager and/or Cisco Monitor Director do not start and display errors
|
Cisco Monitor Manager and/or Cisco Monitor Director do not start after a successful installation or when they are launched from Remote Desktop Protocol (RDP), and the following error messages appear:
Couldn't create Java Virtual Machine
and
Error occurred during initialization
To work around the problem, modify the JVM_MAXIMUM_HEAP value in the startup.properties file; this file is located in the <Cisco Monitor Manager/Cisco Monitor Director installation directory>\startup directory.You must set a value that is less than 1024m; for example, you can enter 256m, 512m, or 786m as values.
If you continue to see these errors after modifying the value, continue to decrease the value until the application starts.
Note Decreasing the JVM_MAXIMUM_HEAP value may decrease the performance of the application.
|
CSCsi06269
|
Alert counts are not the same in the monthly report and in view-1
|
The total alert count value in the Customer Dashboard view-1 is not the same as the value in the monthly report.
To work around the problem, stop and restart the Cisco Monitor Director service.
|
CSCsi79855
|
Duplicate entries with null values are shown in the monthly report for a stack member that becomes stack master
|
When a stack member is changed to a stack master, the monthly report displays data for the old stack master device as Null and all data for the new stack master. The monthly report displays two entries for device availability for the old and new stack masters; the hostname of the old stack master device is displayed, but the other values for the device are displayed as Null.
To work around the problem, restart the application to remove the entry with the Null values from the monthly report.
|
CSCsi81570
|
E-mail cannot be sent when McAfee VirusScan Enterprise installed on the application server
|
After Cisco Monitor Manager is installed on a server that has McAfee VirusScan Enterprise installed, you cannot send e-mail from Cisco Monitor Manager and/or Cisco Monitor Director unless port 25 is released.
To work around the problem, release port 25 on the application server. Do the following
1. Launch the VirusScan Console window.
2. Right-click the Access Protection task; then, select Properties.
3. In the Port Blocking tab, uncheck the Prevent mass mailing worms from sending mail check box; then, click Apply.
4. Click OK.
|
This document is to be used in conjunction with the documents listed in the "Product Documentation" section.
Any Internet Protocol (IP) addresses used in this document are not intended to be actual addresses. Any examples, command display output, and figures included in the document are shown for illustrative purposes only. Any use of actual IP addresses in illustrative content is unintentional and coincidental.
© 2007 Cisco Systems, Inc. All rights reserved.
