Table Of Contents
Release Notes for Cisco Multicast Manager Release 2.5.3
Installing the CMM R2.5.3 Patch
Downloading the CMM Patch—Solaris and Linux
Installing the CMM 2.5.3 Patch in Solaris and Linux
Obtaining Documentation, Obtaining Support, and Security Guidelines
Release Notes for Cisco Multicast Manager Release 2.5.3
Revised: August 11, 2008, OL-15311-01Contents
•
Obtaining Documentation, Obtaining Support, and Security Guidelines
Introduction
Cisco Multicast Manager is a web-based network management application that is designed to aid in the monitoring and troubleshooting of multicast networks. Enterprises running video delivery systems or financial market data applications can greatly benefit from deploying Cisco Multicast Manager. Service providers or cable operators also benefit from:
•
•
•
New Features
Cisco Multicast Manager provides the following patch functionalitys:
•
•
Changes to the Release Notes
This section documents supplemental changes that have been made since the initial release of the Release Notes for Cisco Multicast Manager Release 2.5.3.
Caveats and Sections Added
The following caveats and sections have been added to the release notes:
The section Installing the CMM R2.5.3 Patch was added to describe how to install the CMM R2.5.3 patch.
•
•
System Requirements
This section describes the system requirements for Cisco Multicast Manager 2.5.3.
Supported Hardware
Linux
On Linux systems, the following hardware is supported:
•
A 2.4 GHz 64 bit processor is recommended for a large enterprise network (more than 500 devices)
•
•
Sun Microsystems Servers
Cisco Multicast Manager supports the following hardware on Sun Microsystems servers:
•
•
Operating System Requirements
Linux
CMM 2.5.3 can run on the following Linux versions:
•
•
Sun Systems
CMM 2.5.3 can run on the following Sun Solaris versions:
•
•
•
Note
Memory Requirements
•
•
Supported Browsers
•
•
•
CMM R2.5.3 Patch
Bug Fixes
The CMM R2.5.3 patch fixes the following caveats:
Installing the CMM R2.5.3 Patch
•
Downloading the CMM Patch—Solaris and Linux
Step 1
Note
Step 2
Step 3
cd /<directory_name>gunzip -c CMM_Patch_release_2.5.3.tar.gz | tar xvf - (for Solaris)tar -xzvf CMM_Patch_release_2.5.3.tar.gz (for Linux)
Note
Installing the CMM 2.5.3 Patch in Solaris and Linux
The following steps describe how to apply the CMM 2.5.3 patch in Solaris or Linux..
Step 1
Note
Sample output of the installation script:
bash-3.00# ./install_patch.shInstalling Cisco Multicast Manager Version 2.5.3Copyright (c) 2008 Cisco Systems, Inc. All Rights Reserved.Installing CMM 2.5.3 for SunOSFound CMM 2.5 installed in this machineThe patch installs in /opt/RMSMMT. Do you wish to continue? [y/n]: yStopping CMM Processes ...Sun Microsystems Inc. SunOS 5.10 Generic January 2005You have new mail./opt/RMSMMT/httpd_perl/bin/apachectl stop: httpd stoppedStopping the Polling Daemon..Stopping CLI Proxy Daemon..Stopping SNMP Trap Receiver..Stopping SNMP Trap Agent..Clean up server access files--Backing up CMM 2.5 processes...Backup CompleteInstalling patch files...Installation Finished.Restarting CMM Processes ..Starting the application...
Caveats
The following IOS caveats affect the operation of CMM 2.5.
•
Symptom:
The current MVRF functionality is limited and it would be useful to include topology views for the MTI and MVRF interfaces.
Workaround:
None.
•
Symptom:
Expand RP status for RPs configured with the context of a VRF.
Workaround:
None.
•
Symptom:
Expand the MSDP status for MSDP peers configured with the context of a VRF.
Workaround:
None.
•
Symptom:
A configurable option should be added to display the device names in either lowercase or uppercase regardless of the actual character case in the SNMP strings or/and DNS.
Workaround:
None.
•
Symptom:
The historical graph does not updates the graph for newly selected SGs. The previous graph appears. This is problem occurs only with the IE 6 browser.
Workaround:
The user can either use a Mozilla browser or configure IE 6 users by following these steps:
1. From the browser menu, select Tools >Internet Options >Settings.
2. Select Every Visit to the page.
•
Symptom:
The user is unable to install CMM 2.5 to a custom file path.
Workaround:
None.
•
Symptom:
The home page of CMM 2.5 displays all of the events and trap details regardless of the domain that the user is currently viewing. The user can view traps that are not related to their domain in the home page.
Workaround:
None.
•
Symptom:
The interfaces list is not displayed for the Add Unicast router
Conditions:
Adding a unicast router through the route manger will not update the full router information on topo.db.
Workaround:
None.
•
Symptom:
When the multicast baselines are viewed, the list of baseline details is incomplete.
Conditions:
The Multicast Baseline Details table is missing some columns of information such as MIB object, Description, and Group Name Values.
Workaround:
None.
•
Symptom:
On Solaris
/opt/RMSMMT/httpd_perl/logs/Server_access_log.x file contains the user login/logout sessions.
On Linux:
/usr/local/netman/httpd_perl/Server_access_log.x file contains the user login/logout sessions.
The dates and times in these files are not properly synchronized.
Conditions:
This condition occurs when CMM 2.5 is installed on the supported OS platforms.
Workaround:
None. This bug will be fixed in the next release.
•
Symptom:
When CMM 2.5 is installed, a non-administrative user can click on the admin link. As a result, the user is logged out and the logs record a timeout entry.
Conditions:
A non-administrative user has the ability to click on the admin link.
Workaround:
None.
•
Symptom:
After logging in to the CMM server, there should be a lock icon displayed in the lower right hand corner of the web browser. In Internet Explorer 7, this lock icon is not displayed.
Conditions:
This condition occurs in CMM 2.5.
Workaround:
The observed symptoms are due to the following reasons:
•
•
For now, it may not be required to find a mechanism for these problems as the customer can
always install their own certificates.
•
Symptom:
The Top Talkers link on the Diagnostics page does not work if the network device supports the
IOSXR release.
Conditions:
The user is trying to execute the Top Talkers link on a device running IOSXR.
Workaround:
None.This feature was not supported for CMM 2.4. This requires a supporting command set for IOSXR. This feature will be available in CMM 3.0.
•
Symptom:
The user tries to execute commands, selected from a drop down list on the Diagnostics page. The user clicks on a device from the devices list located in the left margin.
Conditions:
This occurs in both CMM 2.4 and 2.5.
Workaround:
The use case is that the user wants to do some debugging and the user supplies credentials by manually executing the command. The user should select the command from the drop down menu instead of entering the command.
Further Problem Description:
1. Switch on tcache=1 in file <NMSROOT>/mmtsys/sys/<domain.mm.conf>
2. Restart the application.
3. Execute the command on the Diagnostics page by clicking on the device and entering the command.
The user can execute the commands from the drop down menu for this device.
•
Symptom:
The user fails to run commands on the IOSXR devices from the Diagnostics page.
Conditions:
The user tries to run commands on the devices supporting IOSXR from CMM 2.5.
Workaround:
The user should use SSH V1.
•
Symptom:
In Baseline route polling, a value of 0 or -1, indicates that the routing table should be queried without checking the CPU utilization.
Conditions:
The CPU threshold is taken as -1 when 0 is entered.
Workaround:
None.
•
Symptom:
When upgrading from CMM 2.4 to version 2.5 or reinstalling CMM 2.5, the TACACS configuration is overwritten.
Conditions:
This occurs while upgrading from CMM 2.4 to version 2.5 or while reinstalling CMM 2.5.
Workaround:
Repeat the TACACS configuration.
•
Symptom:
The IOS-XR does not support the CISCO-MVPN-MIB.
Conditions:
The XR PE information is not displayed in the MVPN page.
Workaround:
None.
•
Symptom:
Duplicate Routers are displayed in router column of the SG Polling by Branch page.
Conditions:
In the SG Polling by Branch page, when the filtered FHR and LHR are selected as the same and the routers are filtered, then the duplicate router names are displayed in the router column.
Workaround:
Select only one router from the duplicate routers.
•
Symptom:
The user should not start cliproxyd_sock, snmp, snmptrapd processes without verifying the validity of the license.
Conditions:
Cliproxyd_sock, snmp, and snmptrapd will run even if the license file is invalid.
Workaround:
None.
•
Symptom:
In the SG Polling by Branch page, in the Selective Source and Group Monitoring fields, after the branches are created, an error page is displayed when any of the branches are selected.
Workaround:
When the SG polling by Branch page is refreshed, the branch details for the selected branch will be displayed correctly.
•
Symptom:
Instead of just supporting 7600 router, a config file named (rmspollcli.conf), which can be located under the <NMSROOT>/mmtsys/sys folder, is provided. User can enter the chasis informationandthe IOS version in the config file for which they need CLI option..
Workaround:
Install the 2.5.3 patch.
•
Symptom:
In S,G Delta PPS polling, when the devices are polled through CLI, historical graph display the wrong PPS value.
Workaround:
Install the 2.5.3 patch.
•
Symptom:
The IOS version information continues to display for deleted devices.
Workaround:
None.
•
Symptom:
Users are not able to discover deleted unicast routers with the Unicast Discovery function.
Workaround:
None.
•
Symptom:
Layer 2 devices are added through the Unicast Router Discovery.
Workaround:
None.
•
Symptom:
L2 Polling: An error page is displayed when a device is selected to poll.
Workaround:
None.
•
Symptom:
SG PPS, BPS values are not populated in the Historical Graph - This bug has a workaround which is included in the bug details.
Workaround:
1. Remove the Email configuration, done in Global polling configuration, and in Domain Trap/Email if any.
2. Wait for the polling interval to be configured.
3. The S,G Threshold events will be generated for the configured S,Gs.
4. The Historical Graph will also display the correct and current SG PPS and BPS values.
•
Symptom:
When polling is restarted twice, continuously, the polling daemon exits.
Workaround:
1.
2.
Product Documentation
Table 1 describes the product documentation available for CMM.
Table 1 CMM Documentation
Release Notes for Cisco Multicast Manager, 2.5
•
•
http://www.cisco.com/en/US/products/ps6337/
prod_release_notes_list.htmlDocumentation Guide and Supplementary License Agreement for Cisco Multicast Manager, 2.5
•
•
http://www.cisco.com/en/US/products/ps6337/
products_documentation_roadmaps_list.htmlInstallation Guide for Cisco Multicast Manager, 2.5
•
•
http://www.cisco.com/en/US/products/ps6337/
prod_installation_guides_list.htmlUser Guide for Cisco Multicast Manager, 2.5
•
•
http://www.cisco.com/en/US/products/ps6337/products_user_guide_list.html
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
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.
© 2008 Cisco Systems, Inc. All rights reserved.
Printed in the USA on recycled paper containing 10% postconsumer waste.
Guest
