|
|
These release notes document caveats pertaining to the Cisco Digital Subscriber Line Manager (CDM), Release 3.0. This release supports the Cisco 6260, 6130, and 6160 DSLAMs with NI-2 card.
To learn more about caveats, visit the Cisco web site (see the "Cisco Connection Online" section for details). Information about electronic documentation can be found in both the "Cisco Connection Online" section and in the "Documentation CD-ROM" section.
Obtaining Technical Assistance
You can deploy CDM in a number of different configurations, from a single hardware system to a multisite distributed management system, using Sun Solaris/SPARC hardware with Solaris, Release 2.6. Machine specifications are detailed in the following sections.
For a small site, consider the following machine specifications:
At a minimum, the server machine must meet the following requirements:
Cisco recommends that the server machine meets the following requirements:
For a large site, consider the following machine specifications:
Minimally, the server for a large site must meet the following requirements:
Cisco recommends that the server machine meets the following requirements:
In large deployments with client-server configurations, the recommended hardware specifications for typical client deployments are as follows:
It is useful to install a Sun color card (for example, 24-bit color) if several graphically intensive applications are also run on this workstation.
To operate CDM Release 3.0, you must have following versions of Cisco IOS running on the Cisco DSLAM.
If you are using the CAP line card in a Cisco DSLAM, you must install Cisco IOS Release 12.1(2)DA.
This section describes unexpected behavior in the system. Please refer to the DDTS entry (tracking number) if you communicate with Cisco about any of these issues.
 |
Note The CDM 3.0 and Cisco IOS 12.1(2)DA software provide for the management of a DMT over ISDN line card for the Cisco 6260 DSLAM. However, the DMT over ISDN line card is not available as of the release of the CDM 3.0 and Cisco IOS Release 12.1(2)DA software and is not supported. |
Table 1 lists the open caveats as of Release 3.0.
| DDTS Entry | Description | ||
|---|---|---|---|
CSCdr24602 | The ATM Connection Manager Controller (ATMCMController) has occasionally failed when multiple DSLAMs are selected for uploading PVCs and QoS profiles. Impact: When failing, the controller core dumps and the Upload Management dialog closes abruptly. Workaround: When uploading PVCs and QoS Profiles, using the Upload Management dialog, select only one DSLAM at a time in the Chassis selection panel per upload. | ||
CSCdr51378 | The Generic Component Objects menu under the Deployment tab is inappropriate to the Cisco DSLAM. A user will not use the interfaces available under the menu. Impact: As described Workaround: None. Ignore these menu options. | ||
CSCdr51495 | The Cisco IOS image download fails if it is launched from the NI-2 card. Impact: As described Workaround: Launch the IOS image download from the site or chassis objects. | ||
CSCdr51543 | It is inappropriate for the Management Information choice to appear in the Module submenu. A user should not set this information at the module level. Impact: This information should be set the chassis level, not just the module. Workaround: Set this information at the chassis level. | ||
CSCdr51776 | If the Cisco IOS image download to a DSLAM fails due to the flash being full, subsequent downloads also fail. Impact: As described Workaround: Clear the error condition, Telnet to the DSLAM and issue the command no file prompt quiet. Then perform the download again. | ||
CSCdr52357 | Deployment wizards templates contain too many choices. Impact: You must search a list to view the deployment options. Workaround: None. | ||
CSCdr52395 | Image Download status only shows the status of the previous download. Impact: This attribute does not show status of a download in progress. Workaround: View the status of a download in progress in the IOS image download window. | ||
CSCdr52597 | If the config-register parameter in Cisco IOS is set to 0x0, and you choose "reset device using new image - yes," this does not result in a reset of the DSLAM with newly-downloaded Cisco IOS image. Impact: As described Workaround: Access the Cisco IOS prompt and set the config-register as follows: The reset device from CDM now works. | ||
CSCdr53113 | Line cards can be deployed in slots which are already occupied. Impact: The chassis configuration in CDM shows two icons in a slot in which there should only be one icon. Workaround: Delete the second line card and recommission the chassis. | ||
CSCdr53117 | When you download a Cisco IOS image to a DSLAM, the prompt "file prompt quiet" is issued by CDM. Impact: When you attempt to tftp images in IOS by issuing the command copy tftp: flash:, the command does not generate dialog prompts and whatever image was last downloaded is immediately downloaded again. Workaround: Telnet to the DSLAM and issue the command no file prompt quiet. | ||
CSCdr53332 | Initially all Interface Configuration windows show that a profile was applied, but the profile was not really applied. Impact: The Configuration window does not show blank information when it is initially deployed. A blank is appropriate when there is no information assigned to the interface. The information that appears is residual, arising from a previous selection or from a list of defaults. Workaround: None | ||
CSCdr53883 | Subrack discovery requires considerable time and processing to complete. The length of time depends on the interface population in the chassis. Impact: Overburdening subrack discovery will slow performance significantly. Workaround: Avoid attempts to commission more than three chassis at one time. Wait until the subrack discovery is complete before you begin operations on the chassis or perform additional subrack discoveries. | ||
CSCdr54860 | The ATM Interface Status window misleads you to believe that the Bit Rate Type information in this window applies to the current service category. Impact: The Bit Rate Type drop-down box is designed to allow user to examine status information of the ATM Interface for each type of service category. Workaround: None | ||
CSCdr54902 | No error message is displayed when a delete profile operation fails. Impact: The user will not know why the profile delete operation has failed. Workaround: None. | ||
CSCdr55774 | If you try to apply a profile and no profile is selected (such as an ADSL or DMT profile), the window stops responding and fails. Impact: As described Workaround: When you apply a profile, first make sure you have selected a profile to apply. | ||
CSCdr56646 | When you deploy an line card, the default name of that card <line_card_type>1 (for example, an SDSL line card defaults to S1). Impact: If you do not change the card name, the name of all cards defaults to <line_card_type>1. Workaround: Change the card name after you enter the slot number. | ||
CSCdr57494 | In the SDSL Module Inventory window, some fields that do not have values because those attributes do not have values set in the Cisco IOS software. Impact: None Workaround: None | ||
CSCdr60092 | In the Syslog Message window, when the Maximum Table Entries field is changed, the Syslog Message panel is not updated automatically when you press Save. Impact: As described Workaround: Close the Syslog Message window, and then reopen the Syslog Message window to view the changes. | ||
CSCdr60214 | The Maximum Table Entries field in the Event History Details panel does not update when user modifies the value. Impact: None. The attribute is a read-only attribute and the window must be updated to display changes. Workaround: N/A | ||
CSCdr60691 | If you attempt to delete a preprovisioned card using CDM, you cannot complete the task. A deletion using CDM should result in card being removed from CDM as well as from the DSLAM. CDM currently only removes the card from CDM. Impact: The deleted card is not removed from the DSLAM IOS configuration. The deleted card disappears from the CDM initially, but the card reappears when CDM performs subrack discovery (either by user request or through a trap-initiated discovery) on that DSLAM. Workaround: Delete the affected card from the DSLAM using CLI after you delete the card using CDM. | ||
CSCdr60873 | There is no Action Report or Upload Status window that allows you to view the number of profiles that were created or updated. Impact: As described Workaround: None | ||
CSCdr61045 | The Chassis Inventory window sometimes produces incorrect or null values, depending upon the type of chassis being used. Impact: You do not see values for fields such as Power Supply in Cisco 6130, or software or firmware id. Workaround: None | ||
CSCdr61147 | The SNMP Version field in the Deployment Wizard should not be editable. Impact: If the user changes the SNMP Version, then the deployment process could fail. Workaround: Do not edit the SNMP version field. | ||
CSCdr61148 | SNMP Community Strings that are entered in the Deployment Wizard appear in the SNMP V2 fields of the SNMP Management window, no matter which version of SNMP the user selected. Impact: As described Workaround: None | ||
CSCdr61284 | Duplicate object names are not allowed in the database. Impact: In the Deployment Wizard-Object Parameters windows, if you choose to keep the default prefix (CiscoDSLAMUnit) and default unit name (CiscoDSLAMUnit-6160Chassis-1), chassis deployment fails.
Workaround: Add more words to the default prefix for the unit name, such as CiscoDSLAMUnit-NMS-6160-B. | ||
CSCdr61855 | In the PVC/SPVC Deployment Wizard, you are prompted to choose the PVC Source and Destination ports. Both fields in which this selection takes place have labels which read Component Managed instead of Source Port and Destination port. Impact: As described Workaround: Ensure that the two managed components are unique and represent the source and destination. | ||
CSCdr62131 | The system allows you to create a profile with a null name. Impact: As described Workaround: You can delete or rename the profile. | ||
CSCdr63069 | The Interleave Channel Delay field accepts any whole number from 1 to 16 (milliseconds). In the Cisco IOS software, the same field can only be assigned the following values in microseconds: 1000, 2000, 4000, 8000, 16000. Impact: You can enter invalid values into the ADSL profile. Workaround: Edit the profile to contain supported values. | ||
CSCdr63123 | In the ADSL Profile window, the Interleave Maximum/Minimum Transmit Rates field accepts the following values:
According to a DMT card specification and Cisco IOS software, you can only enter the following discrete values in the Interleave Maximum/Minimum Transmit Rates field:
Impact: The ADSL profile could be created using incorrect values. Workaround: Edit the profile to contain supported values. | ||
CSCdr63322 | The ADSL Profile window contains two CLI fields that are not available from the SNMP MIBs. Therefore, these fields do not appear in the Profile window: 1. The Alarms Enabled field, which can be assigned a Yes or No value. 2. The Payload Scrambling field, which can be assigned an Enabled or Disabled value. Impact: You cannot configure these fields from CDM. Workaround: None | ||
CSCdr63585 | According to the DMT line card functional specification and the Cisco IOS software, the DMT line card supports two modes: Automatic and Splitterless. In the DMT Profile window of CDM, the Operating Mode list box contains additional choices (such as G.992.2, G.992.1, T1.413) other than the two choices that are required. Impact: You could mistakenly choose an incorrect mode. Workaround: Edit the profile to contain supported values. | ||
CSCdr64955 | The physical Cisco 4-port CAP/DMT Flexi card discovered by CDM shows a module status of discoverylostcomms. The 4Flexi card does not operate as a CAP or DMT card when initially inserted into the DSLAM. You must configure the Flexi card to operate as a CAP or DMT card after the card is discovered and shows Normal module status. However, due to a problem in the state machine, the status does not change to Normal module status, although the module status is indeed Normal. Impact: The discovered 4Flexi module status shows a discoverylostcomms status, even after the discovery process is complete. The card retains this status until you configure the card as CAP or DMT. Workaround: After the discovery process completes, configure the card as either CAP or DMT, even though status appears to be "discoverylostcomms." | ||
CSCdr65868 | Some OC-3 and DS3 alarm states supersede others and render them as unknown. CDM reports all alarm states as either present or absent, and suppressed alarms do not appear as suppressed. Impact: Be aware that although some alarm states may appear as good, the true states are suppressed or unknown. Workaround: None | ||
CSCdr66439 | Power entry module failure traps are not visible in the shelf or chassis event browsers. No status color change occurs to indicate an alarm. Impact: You do not know is the power entry module is in an error condition. Workaround: None | ||
CSCdr66472 | In the SNMP Management window, the diagram in the online help is out-of-date. Impact: As described Workaround: Ignore the diagram in the help page. | ||
CSCdr66924 | When trying to set OAM Information using CDM on a chassis running Cisco IOS version 12.1, nothing happens. Trying to set OAM Information using CDM on a chassis running Cisco IOS version 12.0, causes the PVC to become disconnected. Impact: As described. Workaround: Set OAM Information using the Cisco IOS command line interface (CLI). | ||
CSCdr68727 | Some ADSL line alarm states supersede others and render them as unknown. CDM reports all alarm states as either present or absent, and suppressed alarms do not appear as suppressed. Impact: Be aware that although some alarm states may appear as good, the true states are suppressed or unknown. Workaround: None | ||
CSCdr69516 | Dialog box content is fixed and can be adversely affected by video resolution settings. Impact: CDM and the CEMF do not support UNIX clone systems, machines, or non-common desktop environment (CDE) window managers. Workaround: Run CDM and CEMF on Sun UNIX systems using the CDE window manager. | ||
CSCdr72120 | In CDM, actions such as creating profiles and PVCs do not provide explicit error messages if the operation should fail. Impact: You may not know why a particular operation fails (such as creating a PVC). Workaround: Refer to the CDM documentation for information on valid entries and ranges for certain fields. | ||
CSCdr78016 | If you reset the CDM database after you upgrade a CDM installation, basic CDM functionality such as applying profiles and configuring PVCs may not work. Impact: As described Workaround: If you must reset the database in conjunction with a CDM upgrade, use the following procedure: 1. Reset the CDM database. 2. Remove the old CDM installation. 3. Install the new CDM installation. | ||
CSCdr78595 | When you first upload profiles from a chassis, duplicate profiles may be uploaded (such as profiles with the same values but different profile names). Impact: The CDM system could contain duplicate profiles. Workaround: You can delete duplicate profiles from CDM (if these profiles are not applied to an interface). | ||
CSCdr81466 | On the DMT interface or CAP interface, if you select Tools > Performance Manager, the following prompt appears: Impact: You cannot see performance attributes change at the appropriated time intervals. Workaround: None | ||
CSCdr82341 | When trying to apply a DMT profile that has an Operational Mode of "splitterless" on a chassis running Cisco IOS Version 12.0, an error message appears stating: "Profile Roll Down to Device Failed." Impact: You should be able to apply a splitterless DMT profile on a DMT card in a chassis running Cisco IOS Version 12.0 from CDM. Workaround: Apply splitterless DMT profiles using the Cisco IOS command line interface (CLI) on a chassis running Cisco IOS Version 12.0. | ||
CSCdr89038 | When a preprovisioned line card is deleted from IOS and not CDM, the line card object in CDM becomes an object which is "no longer in use." This state change is not reported as an event in the module event browser. Impact: You are not alerted to the state change using the event browser. Workaround: For this type of status change, you must rely on status color changes and object states listed in the object status field at the bottom of most dialog boxes. | ||
CSCdr90944 | Periodically, the content of the Edit menu on the CAP Interface Status and DMT Interface Status windows is not greyed out. Impact: When the Edit menu on the CAP Interface Status and DMT Interface Status windows is not greyed out, the operator may believe that the sub-menu items are valid. In fact, the Edit menu items should be greyed out and should not be used. Workaround: None | ||
CSCdr91628 | If a DSLAM is decommissioned, the PVCs are shown to be disconnected and decommissioned. In fact, when a DSLAM is decommissioned, the PVCs remain connected. When the DSLAM is recommissioned, the PVCs are not recommissioned. Impact: If a DSLAM is decommissioned and recommissioned, the active PVCs remain in a disconnected and decommissioned state after recommissioning. CDM should depict the active PVCs as connected and commissioned after recommissioning the DSLAM. Workaround: After you recommission a DSLAM, you must recommission each active PVC. You can recommission the PVC by selecting the PVC in the ATM Connection Management window and pressing the Commission button. |
Refer to the following publications for related information:
The following sections provide sources for obtaining documentation from Cisco Systems.
You can access the most current Cisco documentation on the World Wide Web at http://www.cisco.com, http://www-china.cisco.com, or http://www-europe.cisco.com.
Cisco documentation and additional literature are available in a CD-ROM package, which ships with your product. The Documentation CD-ROM is updated monthly. Therefore, it is probably more current than printed documentation. The CD-ROM package is available as a single unit or as an annual subscription.
Registered CCO users can order the Documentation CD-ROM and other Cisco Product documentation through our online Subscription Services at http://www.cisco.com/cgi-bin/subcat/kaojump.cgi.
Nonregistered CCO users can order documentation through a local account representative by calling Cisco's corporate headquarters (California, USA) at 408 526-4000 or, in North America, call 800 553-NETS (6387).
Cisco provides Cisco Connection Online (CCO) as a starting point for all technical assistance. Warranty or maintenance contract customers can use the Technical Assistance Center. All customers can submit technical feedback on Cisco documentation using the web, e-mail, a self-addressed stamped response card included in many printed docs, or by sending mail to Cisco.
Cisco continues to revolutionize how business is done on the Internet. Cisco Connection Online 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.
CCO's broad range of features and services helps customers and partners to streamline business processes and improve productivity. Through CCO, you will find information about Cisco and our networking solutions, services, and programs. In addition, you can resolve technical issues with online support services, 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 CCO to obtain additional personalized information and services. Registered users may order products, check on the status of an order and view benefits specific to their relationships with Cisco.
You can access CCO in the following ways:
You can e-mail questions about using CCO to cco-team@cisco.com.
The Cisco Technical Assistance Center (TAC) is available to warranty or maintenance contract customers who need technical assistance with a Cisco product that is under warranty or covered by a maintenance contract.
To display the TAC web site that includes links to technical support information and software upgrades and for requesting TAC support, use www.cisco.com/techsupport.
To contact by e-mail, use one of the following:
| Language | E-mail Address |
|---|---|
English | tac@cisco.com |
Hanzi (Chinese) | chinese-tac@cisco.com |
Kanji (Japanese) | japan-tac@cisco.com |
Hangul (Korean) | korea-tac@cisco.com |
Spanish | tac@cisco.com |
Thai | thai-tac@cisco.com |
In North America, TAC can be reached at 800 553-2447 or 408 526-7209. For other telephone numbers and TAC e-mail addresses worldwide, consult the following web site: http://www.cisco.com/warp/public/687/Directory/DirTAC.shtml.
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, for your convenience many documents contain a response card behind the front cover. Otherwise, you can mail your comments to the following address:
Cisco Systems, Inc.
Document Resource Connection
170 West Tasman Drive
San Jose, CA 95134-9883
We appreciate and value your comments.
This document is to be used in conjunction with the documents listed in the "Related Documentation" section.
Access Registrar, AccessPath, Any to Any, Are You Ready, AtmDirector, Browse with Me, CCDA, CCDE, CCDP, CCIE, CCNA, CCNP, CCSI, CD-PAC, the Cisco logo, Cisco Certified Internetwork Expert logo, CiscoLink, the Cisco Management Connection logo, the Cisco NetWorks logo, the Cisco Powered Network logo, Cisco Systems Capital, the Cisco Systems Capital logo, Cisco Systems Networking Academy, the Cisco Systems Networking Academy logo, the Cisco Technologies logo, Fast Step, FireRunner, Follow Me Browsing, FormShare, GigaStack, IGX, Intelligence in the Optical Core, Internet Quotient, IP/VC, IQ Breakthrough, IQ Expertise, IQ FastTrack, IQ Readiness Scorecard, The IQ Logo, Kernel Proxy, MGX, Natural Network Viewer, NetSonar, Network Registrar, the Networkers logo, Packet, PIX, Point and Click Internetworking, Policy Builder, Precept, RateMUX, ReyMaster, ReyView, ScriptShare, Secure Script, Shop with Me, SlideCast, SMARTnet, SVX, The Cell, TrafficDirector, TransPath, VlanDirector, Voice LAN, Wavelength Router, Workgroup Director, and Workgroup Stack are trademarks; Changing the Way We Work, Live, Play, and Learn, Empowering the Internet Generation, The Internet Economy, and The New Internet Economy are service marks; and Aironet, ASIST, BPX, Catalyst, Cisco, Cisco IOS, the Cisco IOS logo, Cisco Systems, the Cisco Systems logo, the Cisco Systems Cisco Press logo, CollisionFree, Enterprise/Solver, EtherChannel, EtherSwitch, FastHub, FastLink, FastPAD, FastSwitch, GeoTel, IOS, IP/TV, IPX, LightStream, LightSwitch, MICA, NetRanger, Post-Routing, Pre-Routing, Registrar, StrataView Plus, Stratm, TeleRouter, and VCO are registered trademarks of Cisco Systems, Inc. or its affiliates in the U.S. and certain other countries. All other trademarks mentioned in this document 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. (0005R)
Copyright © 2000, Cisco Systems, Inc.
All rights reserved.
Posted: Mon Jul 31 07:53:16 PDT 2000
Copyright 1989-2000©Cisco Systems Inc.