|
|
Table Of Contents
Release Notes for Cisco Cable Manager Release 2.1
Installation and Uninstallation Related Changes
Answering EM Upgrade Questions
About Configuration Management
About Renaming Objects from MapViewer
About Starting Cisco Broadband Troubleshooter 2.0 from CCM 2.1
Registering CBT 2.0 with CCM 2.1
About Starting CiscoView Web 5.2 from CCM 2.1
Registering CVW 5.2 with CCM 2.1
Unregistering CVW 5.2 with CCM 2.1
About Understanding General Polling Behavior
Discovering Cards after a Card Is Inserted or Removed
Dynamically Starting Polling for Newly Added CMs
Performance Management [Polling and Reports] Caveats
Obtaining Technical Assistance
Release Notes for Cisco Cable Manager Release 2.1
Note
Cisco Cable Manager Release 2.1 requires Cisco Element Management Framework (CEMF) 3.1 patch 5.
Contents
•
•
•
•
•
•
•
•
•
Introduction
These release notes describe important information and caveats for the Cisco Cable Manager Release 2.1. Information in this document supplements information in the Cisco Cable Manager Users' Guide Release 2.0.
•
•
The following informational items will be added to the Cisco Cable Manager Users' Guide Release 2.0.with the next release of the document.
Installation and Uninstallation Related Changes
Note
Version Number Removed From Script Names
Note
The installation and uninstallation procedures remain the same. To install CCM as root, enter:
cd dir in which CCM package was extracted
./install_CCM
To uninstall CCM, enter:
cd dir in which CCM package was extracted
./uninstall_CCM
Upgrading CCM 1.0 to CCM 2.1
Note
Step 1
cd dir to which the CCM package was extracted
./uninstall_CCM1.0
Step 2
cd dir to which the CEMF 3.1 was extracted
./cemfinstall
Follow the procedure.
Step 3
cd dir to which the CEMF 3.1 patch 5 was extracted
./cemfinstall
Follow the procedure.
Step 4
cd dir to which the CCM package was extracted
./install_CCM
Upgrading CCM 2.0 to CCM 2.1
Do not use the archived performance polling data from CCM 2.0 to regenerate the Cable Modem Usage Report in CCM 2.1 since the related polling group internal data representation has been changed to improve the Usage Report performance.
Note
Step 1
If there is any possibility that you may want to back off CCM 2.1 and re-install CCM 2.0 in its place, you must do this step.
Step 2
cd dir to which the CEMF 3.1 patch 5 was extracted
./cemfinstall
Follow the procedure.
Step 3
a.
cd dir to which the CCM package was extracted
./uninstall_CCM
b.
cd dir to which the CCM package was extracted
./install_CCM
Step 4
To install CCM 2.1, run the install script
cd dir to which the CCM package was extracted
./install_CCM
The install_CCM script has been modified, so that if CCM 2.0 is already installed on this host, an element manager (EM) upgrade is performed automatically. The current database created with CCM 2.0 is read by CCM 2.1, and CCM 2.1-specific attributes are added so that the database is usable by CCM 2.1.
Note
Answering EM Upgrade Questions
During the upgrade, to reuse the CCM 2.0 database, enter y to the following questions:
The package cblMgrm is already installed on the system.Do you wish to upgrade this package? [y][y.n,?]Enter y.
Are you sure you wish to upgrade the package cblMgrm? [y][y.n,?]Enter y.
Are you sure you wish to install the package cblMgrm? [y][y.n,?]Enter y.
Ignoring EM Upgrade Errors
Two error messages appear as a result of the EM upgrade. These do not affect the CCM 2.1 installation. Ignore them. Sample messages are:
objectspec - Running "/opt/cemf/config/selfManagement/actions/p.objectspec"ObjectFileParser: create/delete failure. Object Name = 'ldapConfigObj' (Path error)ERROR: Action returned an error.viewspec - Running "/opt/cemf/config/selfManagement/actions/p.viewspec"ObjectFileParser: create/delete failure.ERROR: Action returned an error.About Configuration Management
Utilities Required by Configuration Management
The device configuration and diagnostic requests will not function if you don't have the Expect and TCL utilities installed on your system. A cblCtrl core dump appears if these utilities are missing.
Check the ccm2.1.tar.Z filefor the following Expect/TCL libraries:
expect.5.31.5_PkgOnSolaris2.6.tar.Z
tcl.8.3.0_PkgOnSolaris2.6.tar.ZTo load these packages, enter the following commands:
uncompress -d expect.5.31.5_PkgOnSolaris2.6.tar.Z
tar -xvf expect.5.31.5_PkgOnSolaris2.6.tar
pkgadd -d DIRECTORY THAT CONTAINS THE EXPECT PROGRAMuncompress -d tcl.8.3.0_PkgOnSolaris2.6.tar.Z
tar -xvf tcl.8.3.0_PkgOnSolaris2.6.tar
pkgadd -d DIRECTORY THAT CONTAINS THE TCL PROGRAMAbout Renaming Objects from MapViewer
CEMF provides the menu option View Manipulation > Rename Objects to rename objects (icons) shown in the MapViewer. Some internal caches in CCM are based on the ObjectName, such as the cable modem MAC Address, the group name under each cell-name, or an unprovisioned object in the Tree View (MapViewer). Renaming an object in MapViewer can corrupt these caches and cause Cable Manager not to function properly
Note
About Bundled Software
The following information describes software that is bundled with Cisco Cable Manager 2.1.
Netscape Navigator Bundled as Browser
Netscape Navigator is bundled with Cable Manager as of the 2.1 release. The Cisco Cable Manager (CCM) installation procedure will automatically install the browser, which starts CiscoView Web and Cisco Broadband Troubleshooter 2.0 if those packages have been purchased separately and if they have been registered with CCM (see Registering CBT 2.0 with CCM 2.1 and Registering CVW 5.2 with CCM 2.1). The browser will be installed automatically on both the CCM server and client machines.
Note
Netscape Navigator Installation
When installing Netscape Navigator, you are asked the following questions.
Note
Query 1
-------
Please specify the directory path under which the software will be installed. The default directory is auto-generated directory name, but you may install anywhere you wish (if you have permission to do so).
Location for Navigator software [auto-generated directory name]:
Query 2
-------
Existing 'auto-generated directory name' directory found.
The existing contents may be modified or replaced if you install in this directory. If you choose not to install in 'auto-generated directory name', you will be prompted for a different directory.
Do you wish to install in 'auto-generated directory name'? (y/n)[y]
CiscoView Classic
CiscoView Classic is bundled with CCM 2.1 and has been updated to include support for the Cisco uBR925, the uBR10012, the CVA122E, and the uBR7100 series.
Cisco Cable Troubleshooter 1.3
Cisco Cable Troubleshooter 1.3 is bundled with CCM 2.1 and has been updated to include support for the uBR7100 series and the uBR10012.
About Starting Cisco Broadband Troubleshooter 2.0 from CCM 2.1
A new set of scripts, install_cbt and uninstall_cbt, are bundled with Cisco Cable Manager (CCM) 2.1. Run these scripts manually. The scripts are not run automatically by the CCM master installation/uninstallation scripts.
Note
Registering CBT 2.0 with CCM 2.1
The install_cbt script will register the CBT server name and port number with CCM 2.1. After running install_cbt, only CBT 2.0 will be started when invoked from the CCM menus.
In order to register CBT 2.0 with CCM 2.1 as root, enter:
cd dir in which CCM package was extracted
./install_cbt
You must register CBT 2.0 on the CCM server as well as on the client machine. Install_cbt will auto-detect a CBT 2.0 installation on the CCM server machine.
Unregistering CBT 2.0
The uninstall_cbt script removes the CBT server and port number entries. After running uninstall_cbt, only CCT will be started when you invoke it from the CCM menus.
Note
About Starting CiscoView Web 5.2 from CCM 2.1
Note
A new set of scripts, install_ciscoview_web and uninstall_ciscoview_web, are bundled with CCM 2.1. Run these scripts manually. The scripts are not run automatically by the CCM master installation/uninstallation scripts.
Note
Registering CVW 5.2 with CCM 2.1
The install_ciscoview_web script registers the CiscoView Web (CVW) server name and port number with CCM 2.1.
When registering CVW with CCM 2.1, the JAVA plug-in and the identity database needed for starting CVW are installed automatically. These components are used to invoke CV 5.2. [To invoke CV 5.3 or other releases, different sets of components may be needed. It is up to the user to install them.]
After running install_ciscoview_web, only CiscoView Web is started when you invoke it from the CCM menus.
In order to register CiscoView Web with CCM 2.1 as root, enter:
cd dir in which CCM package was extracted
./install_ciscoview_web
Note
Unregistering CVW 5.2 with CCM 2.1
The uninstall_ciscoview_web script removes the JAVA plug-in and the identity database and removes the CVW server and port number entries. After running uninstall_ciscoview_web, only CiscoView Classic (CVC) is started when you invoke it from the CCM menus.
Note
Sequence of Registering CVW and CBT 2.0
If CiscoView Web is registered with CCM AFTER CBT 2.0 is registered, close any browser window opened for CBT 2.0 before starting CVW from the CCM menu.
About Understanding General Polling Behavior
The uBR object "ENTITY-MIB.entLastChangeTime" is polled every 15 minutes (default) to detect any changes (such as OIR). If a change is detected, rediscovery is initiated. Polling of ENTITY-MIB.entLastChangeTime is spread across a 15-minute interval to evenly distribute the load on the system. The spread poll interval depends on the number of uBRs to be polled and the poll interval. The spread poll interval is impacted when uBRs are added (deployed ) or removed (deleted). All subsequent polls occur at 15 minutes intervals.
Example:
Scenario 1:poll interval = 15 minutesnumber of UBRs successfully deployed = 3spread poll interval = 5 minutes ( poll interval / number of UBRs )Assuming deployment started around 10:00am.first poll cycle:ubr-1 is polled at 10:05 amubr-2 is polled at 10:10 amubr-3 is polled at 10:15 amsubsequent poll cycles:ubr-1 is polled at 10:20 amubr-2 is polled at 10:25 amubr-3 is polled at 10:30 amScenario 2:If a uBR is added (deployed) or removed (deleted), the process of calculating the spread poll interval is repeated.Assume 2 additional uBRs are deployed at 10:30 am.Poll interval = 15 minutesnumber of uBRs successfully deployed = 5spread poll interval = 3 minutes (poll interval / number of UBRs)next poll cycle:ubr-1 is polled at 10:33 amubr-2 is polled at 10:36 amubr-3 is polled at 10:39 amubr-4 is polled at 10:42 amubr-5 is polled at 10:45 amsubsequent poll cycles:ubr-1 is polled at 10:48 amubr-2 is polled at 10:51 amubr-3 is polled at 10:54 amubr-4 is polled at 10:57 amubr-5 is polled at 11:00 amCABLE MODEM PERIODIC DISCOVERYCable modem periodic rediscovery is initiated every 24 hours (default). The 24 hour interval starts from the time the uBR was first polled.ubr-1 CM rediscovery will start at 10:05am + 24 hrsubr-2 CM rediscovery will start at 10:10am + 24 hrsubr-3 CM rediscovery will start at 10:15am + 24 hrsubr-4 CM rediscovery will start at 10:42am + 24 hrsubr-5 CM rediscovery will start at 10:45am + 24 hrsDiscovering Cards after a Card Is Inserted or Removed
Cable Manager can detect if a card has been inserted or removed (OIR) from a uBR chassis in the following ways :
•
•
Step 1
This moves the uBR state from Idle to DecommissionStep 2
Step 3
Note
Rehoming/Reparenting
The secondary uBR IP address is not required to perform the rehoming/reparenting operation.
Rehoming/reparenting is not supported on the same uBR. You cannot rehome or reparent a cable modem from one card to another card within the same chassis.
Cable Modem Deletion
An out-of-service cable modem (a cable modem which is no longer registered on any uBR) is not automatically deleted from the map viewer. You must manually delete all cable modems that are no longer registered with any uBR.
About Performance Reports
The Cable Modem (CM) Usage and CPE reports have been redesigned to improve response time. The rest of the reports have been finetuned to improve response time.
The CPE Type column in the CM CPE report has been eliminated since the CPE Type is set to a constant value on the agent.
Spikes in Performance Reports Attribute Value
If you see a spike in a performance chart or an unusually large delta value in a tabular report, the uBR or cable modem has probably been rebooted. This is not an error.
In performance reports, when a delta value is calculated for Counter32-type polling of raw data, it takes counter-rollover into consideration. The delta value is adjusted by adding the Counter32 maximum value of 4294967295L. If the counter value decreased between two consecutive intervals due to counter-resets triggered by the uBR or to cable modem reboots, the performance report treats the event as a counter-rollover case.
Save/Load Function for All Performance Reports
The save/load function can now accept user-specified directories. However, the user-specified directory must have a subdirectory structure consistent with the structure in the default directory to ensure that all reports are categorized by report type. You must also set the directory permissions correctly and ensure that the files in each directory are of the proper report type.
The directory structure for performance reports is default dir or user specified dir/PerformanceReportLog/report type specific dir
The specific report type directory name can be one of the following:
•
•
•
•
•
•
•
•
•
Note
Dynamically Starting Polling for Newly Added CMs
The performance polling controller periodically checks for new cable modems (default time interval is 3600 seconds). If any new cable modems are discovered for a uBR in "AllCMsPerfPolling" state, polling is enabled automatically within 3600 seconds after the cable modems are added to the physical tree view.
To disable the feature or to reconfigure the discovery interval, restart the performance polling controller:
Step 1
cd $CEMF_ROOT/bin
cemf shell
./sysmgrClient -k perfPollCtrl
Step 2
periodicCheckingEnable = 1 ; 0 for disable, 1 for enable
periodicCheckingInterval = 3600 ; unit is seconds
Step 3
Step 4
./sysmgrClient -x perfPollCtrl
Step 5
Site object -> Performance Polling -> Start/Stop uBR/CM Polling
The Start/Stop UBR/CM Polling dialog appears. The current state in the Cable Modem Polling frame indicates whether all CMs under selected uBR are in polling state.
Note
Caveats
This section describes known Cisco Cable Manager Release 2.0 and Release 2.1 software caveats and their related behaviors.
Installation Caveats
DDTS: ATLuk21287
CCM 2.0 May Not Install ProperlySymptom
While installing CEMF 3.1, if you don't select the default Network Interface option, the Object Store database is not initialized correctly and CCM 2.0 may not be properly installed.
Problem Description
Unix machines with multiple networks interface cards.
Workaround
Choose default option "Network Interface" while installing CEMF.
See the following example of an installation of the CEMF 3.1 package:CEMF Manager InstallationThis machine is configured with multiple network interfaces.
Please choose the number that corresponds to the interface
you wish to use. Or hit return to enter the name by hand.1 cta-8.cisco.com/141.22.77.21
2 cta-8a.cisco.com/1.8.6.22
3 cta-8b.cisco.com/10.2.2.11Please choose a number (default: Other) [?,??,q]: <press RETURN KEY>Please enter the hostname of the server for this CEMF Manager system.
Hostname? [cta-8] [?] <press RETURN KEY>The hostname specified was "cta-8".
Is this correct? [y] [y,n,?] < press Y >CEMF Manager InstallationServer Hostname : cta-8
Server IP Address : 141.22.77.21Is this setup correct? [y] [y,n,?] <press Y >DDTS: CSCdt51258
CEMF May Not Start CorrectlySymptom
CEMF may not start correctly after a UNIX machine is rebooted.
Problem Description
If you store the transact.log file in the /tmp directory while installing CEMF 3.1, the file can be lost. There is no guarantee that any files will still be in the /tmp directory after a system reboot.
Also, editing the AutoDiscoveryConfig.spec file may introduce some non-printable characters. If this configuration file is not parsed correctly by the discovery module, Cisco Cable Manager processes are not initialized properly.
Workaround
Note
It is recommended that you store the transact.log file on a separate disk partition with a reasonable amount of disk space (recommended: 9 GB) because this file will be rather large with a large scale uBR/cable modem deployment.
Tips
DDTS: CSCdu44445
CEMF Client BugSymptom
If the client uses a different installation path than that used for the server, the thirdparty application will not start on that client.
Problem Description
Launch3rdPartyAppService appears to be broken if the client and server use different CEMF installation directories. Service invocation happens through the server, and the server uses its own service configuration to determine the COMMAND parameter for the third party application service. This is fine for CEMF native services since the server simply gives the client the app tag; sysmgr on the client then uses this and its local apps file in config/apps to determine the path to the binary. This doesn't happen for thirdparty applications.
Workaround
The client installation path has to be exactly the same as the server installation path to start thirdparty apps correctly, and these include all our bundled apps, including the reports.
Deployment Caveats
DDTS: CSCdt95650
DDTS: CSCdu01000
DDTS: CSCdu02253
Cable Modem GroupingSymptom
Group names are not in order. Extra group names are generated
Problem Description
A group is supposed to have 100 cable modems before another group is created during the discovery process. There are instances when additional empty groups are created, or multiple groups are created, each containing fewer than 100 cable modems. Alternatively, some groups contain more than 100 cable modems, which could affect perf report performance.
Also, group names are not created in numerical sequence.
Workaround
No workaround.
DDTS: CSCdv23986
Cable Modem Discovery Status not Refreshed in Manual Discovery DialogSymptom
The discovery status of the cable modem is not always updated in the Manual Discovery dialog box.
Problem Description
The current discovery state value for a uBR object is not always shown correctly in the Manual Discovery and Commission/Decommission dialog boxes. This is due to a refresh problem.
Workaround
To verify the status of the uBR, click refresh in the Manual Discovery and Commission/Decommission dialog boxes.
Performance Management [Polling and Reports] Caveats
DDTS: CSCdt57598
Cable Modem Polling Interval SkewedSymptom
Cable modem polling interval skewed with every cable modem polling start.
Problem Description
After starting cable modem polling on one or more uBRs, subsequently starting cable modem polling on any other uBR causes an adjustment in the poll sample time for the uBRs that had polling turned on initially. This is a result of the design of the poller: the poller spreads the load of polling over time to ensure that CPU usage is at a constant low level. When new objects are added to the object list maintained by the poller, it redistributes all the objects that need polling over the polling interval. This is a transient issue in that it only occurs when polling configuration parameters are changed. The poller will then return to a steady state and the times between subsequent cable modem polls will again become constant.
Workaround
None.
DDTS: CSCdt44418
Cable Modem Polling Takes Too LongSymptom
Cable modem polling takes too long to start for large-scale deployments.
Problem Description
The latency between the time that cable modem polling is started on a large number of modems and the first polled sample is received can be quite large, up to 2 times the configured polling interval. After the initial latency, the poller will reach steady state and the polling interval will be fairly constant between subsequent polls.
Workaround
None
DDDTS: CSCds46075
DDTS: CSCds91305
Polling Takes Place even after uBR Is DecommissionedSymptom
Polling takes place and alarms are received, even after uBR is decommissioned.
Problem Description
Polling takes place and alarms relating to that uBR are received, even after the uBR has been decommissioned (from the user's perspective). Theoretically, polling should suspend if a uBR is decommissioned and should resume if the uBR is recommissioned.
Workaround
None.
Obtaining Documentation
The following sections provide sources for obtaining documentation from Cisco Systems.
World Wide Web
You can access the most current Cisco documentation on the World Wide Web at the following sites:
•
•
•
Documentation CD-ROM
Cisco documentation and additional literature are available in a CD-ROM package, which ships with your product. The Documentation CD-ROM is updated monthly and may be more current than printed documentation. The CD-ROM package is available as a single unit or as an annual subscription.
Ordering Documentation
Cisco documentation is available in the following ways:
•
http://www.cisco.com/cgi-bin/order/order_root.pl
•
http://www.cisco.com/go/subscription
•
Documentation Feedback
If you are reading Cisco product documentation on the World Wide Web, you can submit technical comments electronically. Click Feedback in the toolbar and select Documentation. After you complete the form, click Submit to send it to Cisco.
You can e-mail your comments to bug-doc@cisco.com.
To submit your comments by mail, use the response card behind the front cover of your document, or write to the following address:
Attn Document Resource Connection
Cisco Systems, Inc.
170 West Tasman Drive
San Jose, CA 95134-9883We appreciate your comments.
Obtaining Technical Assistance
Cisco provides Cisco.com as a starting point for all technical assistance. Customers and partners can obtain documentation, troubleshooting tips, and sample configurations from online tools. For Cisco.com registered users, additional troubleshooting tools are available from the TAC website.
Cisco.com
Cisco.com is the foundation of a suite of interactive, networked services that provides immediate, open access to Cisco information and resources at anytime, from anywhere in the world. This highly integrated Internet application is a powerful, easy-to-use tool for doing business with Cisco.
Cisco.com provides a broad range of features and services to help customers and partners streamline business processes and improve productivity. Through Cisco.com, you can find information about Cisco and our networking solutions, services, and programs. In addition, you can resolve technical issues with online technical support, download and test software packages, and order Cisco learning materials and merchandise. Valuable online skill assessment, training, and certification programs are also available.
Customers and partners can self-register on Cisco.com to obtain additional personalized information and services. Registered users can order products, check on the status of an order, access technical support, and view benefits specific to their relationships with Cisco.
To access Cisco.com, go to the following website:
http://www.cisco.com
Technical Assistance Center
The Cisco TAC website is available to all customers who need technical assistance with a Cisco product or technology that is under warranty or covered by a maintenance contract.
Contacting TAC by Using the Cisco TAC Website
If you have a priority level 3 (P3) or priority level 4 (P4) problem, contact TAC by going to the TAC website:
http://www.cisco.com/tac
P3 and P4 level problems are defined as follows:
•
•
In each of the above cases, use the Cisco TAC website to quickly find answers to your questions.
To register for Cisco.com, go to the following website:
http://www.cisco.com/register/
If you cannot resolve your technical issue by using the TAC online resources, Cisco.com registered users can open a case online by using the TAC Case Open tool at the following website:
http://www.cisco.com/tac/caseopen
Contacting TAC by Telephone
If you have a priority level 1(P1) or priority level 2 (P2) problem, contact TAC by telephone and immediately open a case. To obtain a directory of toll-free numbers for your country, go to the following website:
http://www.cisco.com/warp/public/687/Directory/DirTAC.shtml
P1 and P2 level problems are defined as follows:
•
•
This document is to be used in conjunction with the Cisco Cable Manager Users' Guide publication.
AccessPath, AtmDirector, Browse with Me, CCIP, CCSI, CD-PAC, CiscoLink, the Cisco Powered Network logo, Cisco Systems Networking Academy, the Cisco Systems Networking Academy logo, Fast Step, Follow Me Browsing, FormShare, FrameShare, GigaStack, IGX, Internet Quotient, IP/VC, iQ Breakthrough, iQ Expertise, iQ FastTrack, the iQ Logo, iQ Net Readiness Scorecard, MGX, the Networkers logo, Packet, RateMUX, ScriptBuilder, ScriptShare, SlideCast, SMARTnet, TransPath, Unity, Voice LAN, Wavelength Router, and WebViewer are trademarks of Cisco Systems, Inc.; Changing the Way We Work, Live, Play, and Learn, Discover All That's Possible, and Empowering the Internet Generation, are service marks of Cisco Systems, Inc.; and Aironet, ASIST, BPX, Catalyst, CCDA, CCDP, CCIE, CCNA, CCNP, Cisco, the Cisco Certified Internetwork Expert logo, Cisco IOS, the Cisco IOS logo, Cisco Press, Cisco Systems, Cisco Systems Capital, the Cisco Systems logo, Enterprise/Solver, EtherChannel, EtherSwitch, FastHub, FastSwitch, IOS, IP/TV, LightStream, MICA, Network Registrar, PIX, Post-Routing, Pre-Routing, Registrar, StrataView Plus, Stratm, SwitchProbe, TeleRouter, and VCO are registered trademarks of Cisco Systems, Inc. and/or its affiliates in the U.S. and certain other countries.
All other trademarks mentioned in this document or Web site are the property of their respective owners. The use of the word partner does not imply a partnership relationship between Cisco and any other company. (0108R)
Copyright © 2001, Cisco Systems, Inc.
All rights reserved.
Posted: Thu May 27 06:58:32 PDT 2004
All contents are Copyright © 1992--2004 Cisco Systems, Inc. All rights reserved.
Important Notices and Privacy Statement.
