|
|
These release notes document caveats pertaining to the Cisco Digital Subscriber Line Manager (CDM), Release 1.1.
For pointers to more detailed information about the Cisco 6260, Cisco 6130, and the software that operates on those DSLAMs, refer to the "Related Documentation" section. To learn more about caveats, visit Cisco's 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.
Release 1.0 Caveats Fixed in Release 1.1
Release 1.0 Caveats in CDM 1.1
The CDM software can be deployed in a number of different configurations, from a single hardware system, to a multi-site distributed management system, using Sun Solaris/SPARC hardware with Solaris, Release 2.6.
Minimally, the server machine must meet the following requirements;
 |
Note The additional disk is required for performance improvements of the database, not for additional storage capacity. Although the Sun Ultra 30 workstation is sufficient to run CDM, the Ultra 60, because it can include an additional CPU, will support future enhancements to CDM. |
In larger deployments with client-server configurations the recommended hardware specifications for typical client deployments are as follows:
|
Note It is useful to have a Sun color card (for example, 24 bit color) if many graphically intensive applications are also run on this workstation. A typical Server installation requires 370MB of free disk space in a file system, for example, /opt. The system also requires an appropriate amount of free disk space for database files. |
For a small deployments (for example, trials), the typical Client and Server can run together on a single workstation. The minimum specification for this scenario is:
To operate CDM 1.1, you must have IOS release 12.0(8)DA or greater running on the DSLAM.
This following section describes how to install CDM 1.1 and SCM 1.2 on the same server.
Workaround instructions for getting CDM and SCM installed together:
To install CDM 1.1 and SCM 1.2 on the same server:
1. Install CEMF 2.1.4
2. Install AV_2.1.4-P4_1
3. Install SCM 1.2
4. Install CDM 1.1
After installing the CDM 1.1 and SCM 1.2 software, you must modify files in the <AVROOT>/config/mibControl directory on both the server and client according to the following instructions.
1. In the file x_c6260Manager.emLocalMibs, search for and locate all occurrences of the identified text and replace it with the specified text as follows:
2. In the file x_c6400Manager.emLocalMibs, search for and locate all occurrences of the identified text and replace it with the specified text as follows:
3. Change to the directory <AVROOT>/config/mib and issue the following command:
rm OLD-CISCO-SYSTEM-MIB.my
4. On the server, change to the directory <AVROOT>/bin directory and issue the following commands:
./av start ./av dataload ./avsession
./av start ./avsession
|
Note The command ./avsession starts a session of the CDM graphical user interface. |
When you have completed these operations, you should be able to run the CDM 1.1 and SCM 1.2 element managers on the same server.
To install CDM 1.1 and SCM 1.3 on the same server:
1. Install CEMF2.14
2. Install AV_2.1.4-P5_1
3. Install SCM1.3 (beta)
4. Install the latest CDM 1.1(EFT)
After installing the CDM 1.1 and SCM 1.3 software, you must modify files in the <AVROOT>/config/mibControl directory on the server and client according to the following instructions.
1. In the file x_c6260Manager.emLocalMibs, search and replace text as follows:
2. When you finish modifying the text, change to the <AVROOT>/bin directory on the server and run the following commands:
./av start ./av dataload ./avsession
./av start ./avsession
|
Note The command ./avsession starts a session of the CDM graphical user interface. |
The following caveats that existed in CDM Release 1.0 are fixed in CDM Release 1.1.
The following caveats identified in CDM Release 1.0 remain in CDM 1.1:
The IF-MIB.ifTable within the OC3Shelf Object Configuration Screen did not return the identical value for objects acquired using the command line interface as it does using CDM. In many cases, CDM shows a value of 0 (zero) for objects that do not exist.
[CSCdp01956]
When the Configure -> ADSL Line screen for a DMT card is invoked, the pull-down menu for Admin Status includes up, down, and testing. The "testing" option should be removed from the menu.
[CSCdp23780]
In a configuration in which the CDM server had two interfaces, the server and clients were associated with IP address 172.27.137.255. The Cisco 6260s were associated with the second interface on the server for which the IP address was 4.4.7.255.
A site object was created in the object manager and Auto Discovery was run on the new site object. The begin/end IP address was double clicked to change the class C network address 172.27.137 to a class A network address 4.4.7. Then, clicking on OK returned the error message:
"Invalid value in field of address"
There was no way to correct or change the subnet mask.
Deploy network objects with the correct network address and initiate auto-discovery from the new object.
[CSCdm49028]
The following caveats have been identified in CDM Release 1.1
DMT Profile Names are allowed to be from 1 to 32 characters in length. There is a logic problem within CDM that prevents CDM from creating or deleting DMT Profiles that are 25 to 32 characters in length. Because some ASCII-character decimal values are 2-digits in size, using "1 through 0, A through Z, and a through c" may increase the number of accepted characters.
DMT Profiles with names 25 to 32 characters in length cannot be created or deleted reliably.
Creation and deletion of long name DMT Profiles must be done using IOS CLI. Whenever possible, use DMT Profile names of 1 to 24 characters in length.
[CSCdm77055]
The PVC Configuration Manager dialog provides a table listing the PVCs connected to the selected interface. The content of this table sometimes needs to be reloaded.
Occasionally, the PVC Manager dialog PVC table is blank, filled with zeros, or does not list a recently created PVC.
Open the PVC Manager dialog and, if the table is not accurate, ensure the correct chassis, card, and interface are selected on the selection panels. If correct, click on the desired interface again to force the table to refresh.
[CSCdm85259, CSCdp19141]
The autodiscovery and manual deployment processes are significantly different. Autodiscovered DSLAMs are not identified for NI-2 type until the subrack discovery process during commissioning.
The user will not see Trunk or Subtend ports on an autodiscovered DSLAM until it is commissioned. As a result, the autodiscovered DSLAM cannot be used in a subtend tree until it has been commissioned.
Commission the DSLAM in the CDM so that subrack discovery can properly identify the NI-2 type and its trunk/subtend ports.
[CSCdm59278]
CDM status is predominantly trap driven and events that do not force SNMP traps typically are not visible in CDM.
If a line card is preprovisioned in IOS CLI, it will not be visible in the CDM model for the DSLAM.
Force CDM to perform a subrack discovery on the DSLAM by entering the NI-2 Status Manager dialog, perform a Decommission and Commission of the DSLAM.
[CSCdm85259, CSCdp64721]
There is no ability to set interleaving to automatic since the CISCO-ADSL-DMT-LINE-MIB does not support an automatic setting for the DMT Codeword Size.
There are no auto settings for DMT line rates or interleave delay through CDM; however, you can set DMT line rates and the interleave delay using the IOS CLI.
Use the IOS CLI to set lines to 'auto' and recognize codeword size of 'zero' in CDM to be this 'auto' setting.
[CSCd64074]
The IOS CLI units of measure displayed for DMT Profile values differ from the units of measure displayed through the MIB.
These values will be in different units -
Max Interleave Delay MIB/CDM -> milli-seconds
IOS CLI -> microseconds
Interleave Min Transmit Rate
Interleave Max Transmit Rate
MIB/CDM -> bps (bits per second)
IOS CLI -> kbps (kilobits per second)
Values are correct in both cases; but, they are represented with different units of measure.
[CSCdp22541]
The ifAdminStatus setting for 'testing (3)' is made available to the DMT Port Configuration Manager dialog even though DMT lines do not support the testing mode.
Testing is presented as an option when configuring a DMT port.
None. Do not use the testing option, it has no meaning for DMT ports.
[CSCdp06765]
When creating a PVC for the first time, and the OAM RDI Mode is set to 'enable', this mode is being reset to 'disable' during the cross-connect phase of creation.
Whenever OAM RDI Mode is set to 'enable' during initial creation, the mode changes to 'disable'.
Create the PVC and, once created, use the Edit tab in the PVC Configuration Manager dialog to change the OAM RDI Mode for this PVC to 'enable'.
[CSCdp08324, CSCdp74861]
The IOS CLI uses kbps (kbits per second) for the ATM Traffic Descriptor Peak Cell Rate value; CDM uses the MIB and cells/second.
The IOS CLI and CDM Peak Cell Rates display different numbers using different units of measure.
Values are correct in both cases; however, they use different units of measure. To compare the values, convert cells/second to kbits/second.
[CSCdp22524]
These documents contain information that might be useful to users of the Cisco Digital Subscriber Line Manager Release 1.1:
Cisco Connection Online (CCO) is Cisco Systems' primary, real-time support channel. Maintenance customers and partners can self-register on CCO to obtain additional information and services.
Available 24 hours a day, 7 days a week, CCO provides a wealth of standard and value-added services to Cisco's customers and business partners. CCO services include product information, product documentation, software updates, release notes, technical tips, the Bug Navigator, configuration notes, brochures, descriptions of service offerings, and download access to public and authorized files.
CCO serves a wide variety of users through two interfaces that are updated and enhanced simultaneously: a character-based version and a multimedia version that resides on the World Wide Web (WWW). The character-based CCO supports Zmodem, Kermit, Xmodem, FTP, and Internet e-mail, and it is excellent for quick access to information over lower bandwidths. The WWW version of CCO provides richly formatted documents with photographs, figures, graphics, and video, as well as hyperlinks to related information.
You can access CCO in the following ways:
For a copy of CCO's Frequently Asked Questions (FAQ), contact cco-help@cisco.com. For additional information, contact cco-team@cisco.com.
|
Note If you are a network administrator and need personal technical assistance with a Cisco product that is under warranty or covered by a maintenance contract, contact Cisco's Technical Assistance Center (TAC) at 800 553-2447, 408 526-7209, or tac@cisco.com. To obtain general information about Cisco Systems, Cisco products, or upgrades, contact 800 553-6387, 408 526-7208, or cs-rep@cisco.com. |
Cisco documentation and additional literature are available in a CD-ROM package, which ships with your product. The Documentation CD-ROM, a member of the Cisco Connection Family, is updated monthly. Therefore, it might be more current than printed documentation. To order additional copies of the Documentation CD-ROM, contact your local sales representative or call customer service. The CD-ROM package is available as a single package or as an annual subscription. You can also access Cisco documentation on the World Wide Web at http://www.cisco.com, http://www-china.cisco.com, or http://www-europe.cisco.com.
If you are reading Cisco product documentation on the World Wide Web, you can submit comments electronically. Click Feedback in the toolbar and select Documentation. After you complete the form, click Submit to send it to Cisco. We appreciate 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, 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, ConnectWay, Fast Step, FireRunner, Follow Me Browsing, FormShare, GigaStack, IGX, Intelligence in the Optical Core, Internet Quotient, IP/VC, Kernel Proxy, MGX, MultiPath Data, MultiPath Voice, Natural Network Viewer, NetSonar, Network Registrar, the Networkers logo, Packet, PIX, Point and Click Internetworking, Policy Builder, Precept, ScriptShare, Secure Script, ServiceWay, Shop with Me, SlideCast, SMARTnet, SVX, The Cell, TrafficDirector, TransPath, ViewRunner, Virtual Loop Carrier System, Virtual Service Node, Virtual Voice Line, VisionWay, VlanDirector, Voice LAN, WaRP, Wavelength Router, Wavelength Router Protocol, WebViewer, 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 ASIST, BPX, Catalyst, Cisco, Cisco IOS, the Cisco IOS logo, Cisco Systems, the Cisco Systems logo, the Cisco Systems Cisco Press logo, 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 of its resellers. (9912R)
Copyright © 2000, Cisco Systems, Inc.
All rights reserved.
Posted: Wed Feb 16 11:35:07 PST 2000
Copyright 1989 - 2000©Cisco Systems Inc.