|
|
Table Of Contents
Release Notes for Cisco Cable Manager Release 2.0
Additions to the Cisco Cable Manager Users' Guide Release 2.0
Changing $CEMFROOT to CEMF_INSTALL_DIR
Performance Management [Polling and Reports]
Performance Management [Polling and Reports] Caveats
Configuration Management Caveats
Obtaining Technical Assistance
Release Notes for Cisco Cable Manager Release 2.0
Contents
•
Additions to the Cisco Cable Manager Users' Guide Release 2.0
•
•
•
•
•
•
Introduction
These release notes describe important information and caveats for the Cisco Cable Manager Release 2.0. Information in this document supplements information in the Cisco Cable Manager Users' Guide Release 2.0.
Warning
Additions to 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.
Changing $CEMFROOT to CEMF_INSTALL_DIR
Change all references to $CEMFROOT to CEMF_INSTALL_DIR in the Cisco Cable Manager Users' Guide Release 2.0.
Bundled Software
The following information relates to software which is bundled with Cisco Cable Manager 2.0.
Saving the CEMF License File When Uninstalling CEMF
The CEMF uninstallation script, bundled with CCM2.0, saves the CEMF license file in the /CCM2.0_licenses directory before removing CEMF.
Installing CiscoView
When installing CiscoView as part of the CCM2.0 installation, the following prompt appears even after you have completed the CiscoView installation:
The following packages are available:1 CSCOcv CiscoView 4.2(sparc) 4.2(1.0)Select package(s) you wish to process (or 'all' to process all packages). (default: all) [?,??,q]:
After the CiscoView installation has completed, please respond with a "q" to the above query.Database Backup and Restore
You can backup and restore the database used by Cable Manager 2.0.
Backing Up the Database
To backup the database, enter the following command:
$<CEMF_INSTALL_DIR>/bin/cemf backup
Running the above command will create a backup directory. For example, if <CEMF_INSTALL_DIR> is /opt/cemf, then the database will be backed up under /opt/Backup.
Restoring the Database
To restore the database, follow these steps:
Step 1
$<CEMF_INSTALL_DIR>/bin/cemf stop
Step 2
$<CEMF_INSTALL_DIR>/bin/cemf restore -t mm-dd-yyyy
where mm-dd-yyyy is the date when the database was backed up.
Step 3
$<CEMF_INSTALL_DIR>/bin/cemf start
For details, see the Cisco Element Management Framework Installation and Administration Guide 3.1, Chapter 11, Cisco EMF Database Backup and Restore Procedures.
Deployment
Understanding General Polling Behavior
uBR Periodic Discovery
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
Performance Management [Polling and Reports]
Stop Cable Modem Polling
Stopping performance polling simultaneously on a large number of cable modems can take some time to take effect. Table 0-1shows the elapsed time between the user action to stop polling and the actual stopping of the polling
Table 0-1
10K
8 minutes
20K
15 minutes
50K
50 minutes
80K
100 minutes
100K
210 minutes
Disabling Cable Modem Polling
Recommended Polling Configuration for 80K Modems
Table 0-2 shows the recommended polling configuration for up to 40 uBRs with 2000 modems per uBR.
Table 0-2 Recommended Polling Configuration
Automatic Polling of Newly Discovered Cable Modems
Once performance polling has been started on all modems for a uBR, any newly discovered modems are not polled automatically. This applies to all modems discovered through either trap-based discovery or the periodic re-discovery. The newly discovered modems can be polled by starting polling on the modem individually, or by stopping and re-starting polling on all cable modems attached to a particular uBR.
Customized Performance Reports
The Performance Manager application that is bundled with CEMF displays all the attributes that are monitored for all the managed object classes. To run a customized performance report, select the appropriate attribute for the managed object from the list of attributes that are presented.
Configuration Management
Utilities Required by Configuration Management
The device configuration and diagnostic requests will not function if the Expect and TCL utilities are not installed on your system. A cblCtrl core dump appears if these utilities are not loaded.
Check the CCM2.0 CD for 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 PROGRAMSupported Versions
Cisco Cable Manager 2.0 supports DOCSIS cable modems that support RFC2669. CCM 2.0 does not support those cable modems that support older versions of DOCS-CABLE-DEVICE-MIB under experimental (1.3.6.1.3.83) tree.
Impact of Multiple Requests
If multiple requests are launched simultaneously from the device configuration or diagnostic subsystems (upload/download uBR configuration, download templates, show snmp/flap-list/interface/upstream/downstream, ping cable modem, and so on), expect delays.
Note
Correcting Data Abstractor Timeout
A device configuration reequest can fail due to a data abstractor time out. The error message is "AV Data Abstractor Error." To correct the problem, increase the DaemonDataAbstractor timeout (default is 60 seconds):
Step 1
cd <CEMF_INSTALL_DIR>/bin/
Step 2
./cemf shell
./sysmgrClient -k cblCtrl
Step 3
Step 4
./sysmgrClient -x cblCtrl
Caveats
This section describes known Cisco Cable Manager v2.0 software caveats and the related behaviors.
Installation Caveats
DDTS: ATLuk21287
CCM2.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 CCM2.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
Sometimes, after a UNIX machine is rebooted CEMF may not start correctly.
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.
Edit the AutoDiscoveryConfig.spec file carefully to avoid introducing any non-printable characters.
Deployment Caveats
UBR Chassis Deployment
DDTS: CSCds65399
Discovery of SRP CardSymptom
Discovery of SRP Card: only a partial table is returned when you poll entPhysicalTable.
Problem Description
If you have an SRP card, you need image version 12.1(6)EC.
Workaround
Install the correct image to discover a uBR correctly.
DDTS: CSCdt50845 and CSCdt00346
Discovery of CardsSymptom
No child object in entPhysicalTable for POS MM port adapter.
Problem Description
After OIR of port adapters, SNMP MIB tables may not be correct.
Workaround
Reload your router to discover cards correctly.
Reparenting a Cable Modem
DDTS: CSCdt89886
Rehoming uBRsSymptom
Reparenting with LDAP did not move the modem to a rehome uBR.
Problem Description
With LDAP setup, when a cable modem is rehomed it does not get reparented in the map viewer. You will see the cable modem under the primary uBR instead of under the secondary uBR to which it was rehomed.
Workaround
None.
DDTS: CSCdt75932
Correct grouping of cable modems after rehomingSymptom
Cable modem does not move to unprovisioned group after rehoming/reparenting.
Problem Description
After successfully rehoming a cable modem to the secondary uBR, the modem is placed in the rehome group. When cable modem periodic discovery is triggered, the modem is supposed to be reparented to the unprovisioned group. Instead, the cable modem was changed to online_ip_unreachable in the rehome group.
Workaround
None.
Renaming Cable Modems
DDTS: CSCdu00872
Renaming of cable modem tagsSymptom
Rename the cable modem tags.
Problem Description
Cable Manager does not rename cable modems when receiving an online/offline trap for an existing cable modem. So if a cable modem was discovered in an offline state (xx.xx.xx.xx.xx.xx_offline), its name will remain the same until the next periodic discovery.
Workaround
Run a cable modem discovery to update the cable modem names.
uBR Deployment using Auto Discovery
DDTS: CSCds37663
SNMP as only discovery methodSymptom
Cable Mgr should prevent unsupported discovery methods.
Problem Description
From the Auto-Discovery window, select SNMP as the discovery method. The Cable Manager discovery module will not function properly if you choose other discovery methods.
Workaround
Use only SNMP as a discovery method.
Deleting uBRs from Cable Manager
DDTS: CSCds91195
Hourglass does not go away after deleting objectSymptom
Hourglass does not go away after deleting object.
Problem Description
Sometimes, after deleting one or more uBRs from the Tree View, the hourglass will not go away from the GUI window. The GUI doesn't refresh automatically.
Workaround
Close and reopen the Map Viewer.
Large Scale Deployment
DDTS: CSCdt93457 and CSCdu00623
High cpu usage during deploymentSymptom
High cpu usage during deployment.
Problem Description
The ObjectServerDB and localDB processes may consume large amounts of CPU time when creating large numbers of uBR/cable modem objects without using LDAP. This happens generally during the initial deployment phase when you try to deploy a large number of uBRs and CMs.
20k deployment : 76% CPU usage
50k deployment : 90% CPU usage
100k deployment : 99% CPU usage
Note
When a large scale deployment is in progress, it may impact the performance of other applications. With LDAP, CPU utilization can be high with even small deployments.
Workaround
If you are deploying large numbers of cable modems (greater than 20,000) at one time, do not enable any other application.
Other Deployment Caveats
DDTS: CSCdt78432
Unable to expand view after large deploymentsSymptom
If a large number of objects are deployed, for example, 50 UBRs with 2000 cable modems each, the 'plus' sign in the Tree View of each uBR disappears. You cannot expand the uBR view to see the line cards and cable modems attached to the uBR. This happens each time you open Map Viewer. Also, the names of the objects on the right side of the map appear as numbers.
Problem Description
To reproduce the problem, deploy a large number of ubrs and cable modems You can see the problem when you open Map Viewer again.
Workaround
Deploy large numbers of objects under one site (80K - 100K cable modem deployment). Then reparent the uBRs into multiple sites. It is recommended that you limit the number of uBRs per site to 10 units.
DDTS: CSCds56091
Object lists are slow to populateSymptom
Object lists are slow to populate.
Problem Description
If you launch certain dialog boxes from a site, expect a delay while the dialog lists all the objects which correspond to the list request. Expect to wait approximately two minutes if there are up to 25 uBRs in the site, and approximately five minutes if there are between 25 and 50 uBRs.
Workaround
None
Fault Management Caveats
DDTS: CSCdt96113
Linkdown trap alarm for PAs display on uBR object levelSymptom
Linkdown trap alarm for PAs display on uBR object level.
Problem Description
When a linkup or linkdown trap is generated from a uBR upon bringing a port adapter interface up or down, the alarm is not raised on that port adapter object in the Tree View, but under its parent uBR.
Workaround
Run the Event Browser from the uBR object to view the Link up/Down trap generated from Port Adapter (PA) interfaces ONLY.
DDTS: CSCdt59971
Threshold Manager does not work for CPU utilizationSymptom
Threshold Manager does not work for CPU utilization.
Problem Description
Thresholds on CPU utilization do not work correctly and may raise false alarms. This is because the index value is not set when you create a uBR object.
Workaround
To set the attribute LocalDB:CISCO-PROCESS-MIB.cpmCPUTotalIndex to 1:
Step 1
Step 2
Step 3
Step 4
Step 5
In the above example : replace objectname by Physical:/Site-1/1.8.7.2
DDTS: CSCds56861
ciscoFlash traps not recognizedSymptom
Traps for ciscoFlash are not recognized in Cable Manager.
Problem Description
Traps for ciscoFlashCopyCompletionTrap, ciscoFlashPartitioningCompletionTrap and ciscoFlashMiscOpCompletionTrap, and ciscoFlashDeviceChangeTrap are not recognized by Cable Manager.
Workaround
None.
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-4 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
To turn on cable modem polling at the same time for all modems under more than one uBR, or turn on cable modem polling for all cable modems for additional uBRs (incrementally):
Step 1
a.
b.
c.
Step 2
a.
b.
c.
Step 3
a.
b.
c.
DDTS: CSCdt90922
High CPU time for reportsSymptom
Java performance reports consuming approximately thirty-three percent of CPU time per report.
Problem Description
The pre-defined performance reports can consume up to thirty-three percent of CPU time per report. You may not be able to run several performance reports simultaneously and you may not be able to run any other CPU-intensive applications while running a performance report.
The root-cause of this performance bottleneck is in the CORBA calls that are being used for the performance data gathering from CEMF. The current version of Orbix (ORB) used by CEMF 3.1 is inefficient in the encoding of the performance data that is retrieved by the reporting application, and additionally, the number of CORBA calls that need to be made to retrieve the data increases linearly with the number of objects that are queried by the reporting application.
Workaround
None.
DDTS: CSCdt40476
Running historyAdmin exportSymptom
You cannot run the CEMF utility "historyAdmin export" at the same time that a performance report is being run.
Problem Description
Running a performance report at the same time as "historyAdmin export" causes a very heavy load on CEMF, and the performance reports will indicate a time-out for the data retrieval from the performance data repository.
Workaround
None.
Configuration Management Caveats
DDTS: CSCdu03194
Logging in through TerminalSymptom
You cannot login through "Terminal" if the router console port doesn't set the password.
Problem Description
If you choose "Terminal" as the Telnet access type, the managed router must request the console port password to login.
Workaround
Configure the managed router to ask for the console port password when Telneting through the terminal server.
Diagnostic Caveats
DDTS: CSCdt92266
Cable modem batch ping statusSymptom
Need progress status or hourglass while cable modem batch ping is processing.
Problem Description
After starting a batch ping of 60+ modems, it takes a while for the result dialog box to appear. During this period, you don't know if the operation has been completed or not. It is better to have an hourglass or status symbol displayed, so that the user knows the operation is still going on.
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, CCDA, CCDE, CCDP, CCIE, CCNA, CCNP, CCSI, CD-PAC, CiscoLink, the Cisco NetWorks logo, 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, Cisco, the Cisco Certified Internetwork Expert logo, Cisco IOS, the Cisco IOS logo, 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 brands, names, or 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. (0104R)
Copyright © 2001, Cisco Systems, Inc.
All rights reserved.
Posted: Thu May 27 07:00:06 PDT 2004
All contents are Copyright © 1992--2004 Cisco Systems, Inc. All rights reserved.
Important Notices and Privacy Statement.
