|
|
These release notes document caveats that pertain to the Cisco Digital Subscriber Line Manager (CDM) NI-1, Release 3.0.
For more details, see the "Cisco Connection Online" section. Information about electronic documentation can be found in both the "Cisco Connection Online" section and in the "Documentation CD-ROM" section.
This document contains the following sections:
You can deploy CDM in a number of different configurations, from a single hardware system to a multiworkstation distributed management system, using Sun Solaris/SPARC hardware with Solaris, Release 2.6. Machine specifications are detailed in the following sections.
To manage a small network, consider the computer specifications that are described in the following sections.
The server computer must meet the following minimum requirements:
Cisco recommends the following requirements for the server computer:
For a large site, consider the computer specifications that are described in the following sections.
The server computer for a large site must meet the following minimum requirements:
Cisco recommends the following requirements for the server computer:
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 you plan to run several graphically intensive applications on this workstation. |
A change to the CDM NI-1 graphical user interface (GUI) is in effect since the release of the Cisco Digital Subscriber Line Manager NI-1 User Guide for this release, and is described in the following sections.
In the "Using Map Hierarchy Views" section of "Chapter 1, Using CDM---An Overview," the information about the map hierarchy view should be replaced with the following information.
Figure 1-21 shows a top level CDM map hierarchy view to which a new map hierarchy has been added as the first view, and this view now includes the following top level map hierarchies:
The major difference in how you navigate through the map views is that to observe a view of the chassis and its associated line cards, you must click the "+" next to C61xxChassisView to find the Trap Management list, and continue clicking the "+" below this map to see the associated managed element and line cards.
In the following example, a chassis is named C6100v30ManagedElement with a trap management element named C6100v30TrapMgmt and contains four ATU-C modules. You would see the following hierarchical menu structure:
C61xxChassisView
6100v30TrapMgmt
The navigational actions based on this new hierarchy view are as follows:
|
Note To see the line card ports or subscribers, you must navigate through the Physical or C61200v30Mgr map hierarchy views, as described in the Cisco Digital Subscriber Line Manager NI-1 User Guide. |
You can no longer have the Map Viewer window display a chassis view by clicking from within the Physical map hierarchy view (Refer to Figure 1-33 in the Cisco Digital Subscriber Line Manager NI-1 User Guide). To have the Map Viewer window display a graphical representation of the chassis, you must click C61xxChassisView as described in the "Changes to the Map Hierarchy View" section. However, you can still access object menus from the objects that are listed below the Physical view, as described in the user guide.
To access object menus for specific managed objects, you can first display the chassis view that you see after you click the trap manager map hierarchy view from below C6100v30Mgr, then right-click over the icon of the line card or other module whose status or configuration window you want to open.
As described in the Cisco Digital Subscriber Line Manager NI-1 User Guide, you can access object menus by right-clicking over the name of the managed object from below the Physical view map on the left side of the Map Viewer window.
Alternatively, below the Physical view map, you can click the name of a managed object and the Map Viewer displays an icon for this object on the right side of the window. You can right-click the icon to open the object menu for this object.
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.
In the Downloading Software instructions in Chapter 4 of the Cisco Digital Subscriber Line Manager NI-1 User Guide, a step is missing from the instructions. If you complete Step 4 (Start the Software Download and click Yes in the confirmation dialog box), then immediately proceed to Step 5 (Open the System Commission/Decommission/ Config sync Dialog window) and Step 6 (invoke the Image Swap System command) before the Action Report window opens after Step 4 to inform you that the software has successfully downloaded, the download fails.
Impact: The software download fails.
Workaround: After performing Step 4 of the Downloading Software instructions in Chapter 4 of the Cisco Digital Subscriber Line Manager NI-1 User Guide, wait for and confirm in the Action Report window that the software has downloaded before you proceed to Step 5.
The ObjectServer process of the Cisco Element Manager Framework (EMF), which handles object creation/deletion for all Cisco EMF-based applications, appears to use excessive amounts of CPU time (40 to 50%) on ULTRA60 machines when excessive numbers of DSLAM chassis are commissioned. This CPU usages can decrease the performance time of all the Cisco EMF application windows and may cause server applications to terminate. The problem usually corrects itself over time, but this can take several hours. When the ObjectServer is behaving in such a manner, Cisco has noted different types of application server termination problems.
The following caveats are examples of known server termination problems:
Workaround/Prevention: The best workaround for this problem is prevention. Prevention means that you should commission a minimum number of DSLAM chassis; that is, less than four.
Occasionally, a server termination problem might occur but is transparent to you because the application restarts itself. It is possible that you will have to reopen the window that you were trying to access.
Another symptom might be that the ObjectGui process termination is more visible. You must restart the graphical user interface (GUI) application by restarting the Cisco EMF session.
Cisco is investigating this particular problem with the highest priority. In the meantime, if the ObjectServer process problem does not correct itself as described previously, stop Cisco EMF and restart Cisco EMF as well as the Cisco EMF session.
The caveats listed in Table 1 for CDM NI-1 are open as of Release 3.0.
| DDTS Entry | Description | ||
|---|---|---|---|
CSCdr02305 | The fan tray is not represented graphically on the chassis view or by an object in any of the hierarchical views. Impact: The operator cannot immediately discern, via graphical representation, whether there are any outstanding alarms against the fan tray. Workaround: The operator should be aware that alarms against the fan tray are shown and propagated through the MUX chassis object. | ||
CSCdr06477 | It is possible to create a subscriber on a LIM1 port that is not assigned to a logical pool. This situation applies to a DSLAM chassis in DOH2, or pooled, mode. Impact: A subscriber who is assigned to a LIM port that is not in a logical pool is unable to get service. Workaround: Always ensure that the LIM port is assigned to a logical pool before creating the subscriber. | ||
CSCdr21852 | The image date and checksum do not show correctly on the Image Info/Delete window. Impact: You cannot correctly identify the image date or checksum. Workaround: None. | ||
CSCdr23881 | In the Cisco Digital Subscriber Line Manager NI-1 User Guide, illustrations of the Navigation Menu include a choice that no longer appears, Open LIM Power Module Status/Configuration Dialog. Impact: CDM does not support a LIM power module; this menu item has been removed. Workaround: None. | ||
CSCdr23898 | The chassis Module Creation window supports the creation of an ATU-C3 module with a DMT4 line code. Impact: You can preprovision an ATU-C module with a DMT line code; this is not supported by Cisco. Workaround: Do not preprovision an ATU-C module with a DMT line code. | ||
CSCdr25956 | The software does not reset DSLAM chassis alarms when you change the connection mode from DOH to Direct Connect or vice versa. Impact: You cannot identify the outstanding alarms against a DSLAM chassis after changing the connection mode. Workaround: After you change a DSLAM connection mode, delete the DSLAM from the Cisco DSL Manager and redeploy it. This removes all outstanding alarms against the DSLAM. You can then identify any new outstanding alarms that are generated after the DSLAM deployment. | ||
CSCdr31253 | The graphical representation of the DSLAM chassis, and the window and menu selections all refer to a DSLAM 6100 chassis whether the managed element is a 6100 DSLAM chassis or a 6130 DSLAM chassis. Impact: You cannot determine whether the chassis is a 6100 or a 6130 based on the graphical representation of the DSLAM chassis or the window or menu chassis references. Workaround: To determine the proper chassis version, look at the chassis revision found in the chassis configuration window. If the chassis revision is 5 or earlier, the chassis is a 6100. If the chassis revision is later than 5, the chassis is a 6130. | ||
CSCdr33000 | The system does validate user input on the Subscriber Creation window. As a result, you can provision differing subscriber upstream and downstream rates. Impact: If you provision different upstream and downstream rates, the system can use either the upstream or downstream rate as the provisioned rate. Workaround: Provision the same rates for both upstream and downstream. | ||
CSCdr33074 | CDM provides only a single Subscriber Configuration/Status window to service all subscribers, regardless of the subscriber line type. As a result, the subscriber Status/Configuration window may contain unsupported configuration parameters for a subscriber, based on the type of line card an operator is configuring. Impact: The operator cannot determine which subscriber configuration parameters are supported by looking at the Subscriber Configuration/Status window. Workaround: Consult the appropriate user guide to determine which subscriber configuration parameters are supported for the type of line card. | ||
CSCdr36575 | In the Flex Module Status/Configuration/Delete Dialog window, Port/Slot tab, you cannot change the Flex Line Code field from cap to dmt. Impact: You cannot change the line code for the Flexi ATU-C to DMT. Workaround: None | ||
CSCdr42712 | The system does not validate the subscriber VCI5 before trying to add a new PVC6 to a subscriber. As a result, it is possible for an operator to enter a duplicate subscriber VCI, causing the add PVC operation to fail. Impact: If an operator tries to add a PVC that contains a subscriber VCI already in use, the operation fails and a failure message appears. The failure message does not specify why the operation failed. Workaround: Track the subscriber VCI usage and ensure that each subscriber PVC has a unique subscribe VCI. | ||
CSCdr43260 | The system does not validate the network VPI7/VCI pair before trying to add a new PVC to a subscriber. As a result, you can enter a duplicate network VPI/VCI, causing the add PVC operation to fail. Impact: If you try to add a PVC that contains a network VPI/VCI already in use, the operation fails and a failure message appears. The failure message does not specify why the operation failed. Workaround: Track the network VPI/VCI usage and ensure that each subscriber PVC has a unique network VPI/VCI. | ||
CSCdr53991 | When you create a new logical pool, CDM does not update the list box in the LPool Create/Delete/Info window. Impact: The operator is unable to see the newly added logical pool. Workaround: Close and reopen the LPool Create/Delete/Info dialog window. | ||
CSCdr57032 | The system does not properly set the read/write community strings to public and private for a NI-1 DSLAM chassis that the system has autodiscovered. Impact: If the system does not properly set the community strings for the NI-1 DSLAM chassis, you cannot manage the system. Workaround: In the Auto-Discovery window, remove the Public community string from the community list. Add Private to the community list. Proceed to autodiscover the DSLAM chassis as usual. Even though both of the read/write community strings are set to private, the node is still manageable under the Cisco DSL Manager. | ||
CSCdr57162 | The Routing Table Configuration Dialog window only displays the first five trap recipients in the list box, but the DSLAM chassis supports up to 10 trap recipients. Impact: The operator sees the first five trap recipients in the list box. Workaround: Limit the number of DSLAM trap recipients to five or fewer. | ||
CSCdr63664 | The system shows the DSLAM in an error state for a period of time after you reset the system controller in the DSLAM. Impact: Wait a brief period of time after you perform a system controller reset for the managed element to return to a normal state. Workaround: None. | ||
CSCdr63844 | Periodically, but infrequently, CDM may suspend the display of all traps against a particular node. When this happens, the system will no longer display any traps until corrective action is taken. Impact: The operator may not be aware of events and alarms against managed DSLAM chassis. Workaround: If operators suspect that CDM is not displaying events, they should check the trapAlarmMapper.log file that is located in the <CEMF8_ROOT_DIR>/logs directory. If operators notice entries in the log file with a description such as "No match found for object in cache," there may be a problem. In addition, if the C6100v30Ctrl.log file, which is also located in the <CEMF_ROOT_DIR>/logs directory, contains entries with a description such as "unable to retrieve children," there may be a problem. If operators see these kinds of messages in the log files, they should first kill the trapAlarmMapper and then the C6100v30Ctrl processes on the Cisco EMF server workstation by using the kill -9 command. Cisco EMF will automatically restart these processes. | ||
CSCdr64005 | The system does not correctly set the provisioned upstream and downstream rates when creating a new DMT-2 subscriber with G.Lite enabled. Impact: You must reconfigure the improperly provisioned upstream and downstream rates after you create the subscriber. Workaround: None. | ||
CSCdr65612 | All references to DSLAMS in the CDM windows and menus refer to a Cisco 6100 DSLAM chassis. Impact: The references to the Cisco 6100 chassis may not be correct because the system manages both Cisco 6100 and 6130 DSLAM chassis. You cannot distinguish between the chassis types using the chassis references in the windows and menus. Workaround: To verify the type of DSLAM chassis, check the chassis revision on the Chassis Configuration window. | ||
CSCdr65810 | On the Create Subscriber on CAP ADSL Modem Port window you cannot set the CPE Detect parameter when creating the subscriber. The parameter, however, does exist on the Subscriber Status/Configuration window. As a result, you can enable or disable the CPE Detect parameter after the subscriber is created. Impact: The user will not be able to set the CPE Detect parameter when creating the subscriber. Workaround: Enable or Disable the CPE Detect field after the subscriber is created. The parameter is available on the Subscriber Status/Configuration window. | ||
CSCdr70201 | CDM may incorrectly identify DSLAM elements during the autodiscovery process. Impact: As a result of autodiscovery, CDM may discover nonDSLAM elements and represent them as DSLAM chassis in the map view. The discovered elements are within the autodiscovered address range that is specified. Workaround: If nonDSLAM elements are represented as DSLAMS within the map view, delete the nonDSLAM chassis from CDM. | ||
CSCdr70274 | You can delete DSLAM objects, such as line cards, ports, subscribers, and so forth, by clicking on the object name in a hierarchy view (from the left side of the Map Viewer window), and selecting Deployment > Delete Objects from the object menu. Impact: After deleting the object, CDM removes the object from the hierarchical view but does not remove this object from the node. Workaround: If you remove an item by choosing Delete Objects from an object menu, click Synchronize on the System/Commission/Decommission/
| ||
CSCdr71215 | If you select Edit > Add Profile or Edit > Delete Profile from any window, the associated window disappears and creates a client GUI manager core file. Impact: Any unsaved operations that you performed on that window are lost. You can resume the session as normal after the window disappears. Workaround: Do not select the Edit > Add Profile or Edit > Delete Profile menu option. | ||
CSCdr71458 | CDM allows you to create an ATU-C subscriber PVC with a fast PVC path, even though only interleaved paths are supported for ATU-C subscribers. Impact: If an operator configures an ATU-C subscriber with a fast PVC path, CDM ignores the setting and treats the PVC as if it were configured to be an interleaved PVC path. The operator may be under the impression that they have configured a fast PVC. Workaround: Only configure ATU-C subscribers with the interleaved PVC path for ATU-C subscribers. | ||
CSCdr74943 | The DMT-2 Performance tab on the DMT-2 Modem Port Configuration Dialog window may show blank values for each of the fields. Impact: Temporarily, the operator may be unable to read the DMT-2 port performance information. Workaround: The operator should close and reopen the DMT-2 Port Configuration Dialog window. | ||
CSCdr84266 | You can edit the subtend port Admin status field on the Transit Subscriber dialog window. Impact: The operator may try to edit the subtend port Admin status field. Having this field be editable may confuse the operator because there is no way to save the modified subtend port Admin status. You can only change the subtend port Admin status from the Subtend Port Configuration dialog window. Workaround: Do not modify the subtend port Admin status on the Transit Subscriber dialog window. | ||
CSCdr84267 | You can edit the transit subscriber Admin status field on the Transit PVC dialog window. Impact: The operator may try to edit the transit subscriber Admin status field on the Transit PVC dialog window. It is not possible to change the Transit Subscriber Admin status from the Transit PVC dialog window. Workaround: The operator should not change the transit subscriber Admin status field on the Transit PVC dialog window. | ||
CSCdr84760 | In the Downloading Software instructions in Chapter 4 of the Cisco Digital Subscriber Line Manager NI-1 User Guide, a step is missing from the instructions. If you complete Step 4 (Start the Software Download and click Yes in the confirmation dialog box), then immediately proceed to Step 5 (Open the System Commission/Decommission/ Config sync Dialog window) and Step 6 (invoke the Image Swap System command) before the Action Report window opens after Step 4 to inform you that the software has successfully downloaded, the download fails. Impact: The software download fails. Workaround: After performing Step 4 of the Downloading Software instructions in Chapter 4 of the Cisco Digital Subscriber Line Manager NI-1 User Guide, wait for and confirm in the Action Report window that the software has downloaded before you proceed to Step 5. | ||
CSCdr87635 | If you click an empty slot on the graphical representation (chassis view) of a DOH chassis, the graphical representations of the line cards disappear. Impact: None. Workaround: Click another object in the hierarchy map on the left side of the Map Viewer window, and then reselect the object for which you want to choose an object menu item. |
Refer to the following publications for related information:
A complete list of all DSL product related documentation is available on the World Wide Web at
http://www.cisco.com/univercd/cc/td/doc/product/dsl_prod/index.htm
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 13:36:33 PDT 2000
Copyright 1989-2000©Cisco Systems Inc.