|
|
September 2, 1998
These release notes discuss features, resolved problem reports, and unresolved problem reports for the Cisco 6100 advanced digital subscriber line access multiplexer (DSLAM) supported in Cisco 6100 Release 2.2.0.
For more detailed information about the features in these release notes, refer to the "Related Documentation" section. Information about electronic documentation can be found in the "Cisco Connection Online" section, and in the "Documentation CD-ROM" section.
These release notes discuss the following topics:
The Cisco 6100 Advanced DSL Access Multiplexer (Advanced DSLAM) is a Central Office (CO) grade multiplexer that offers cost effective high-speed services to the residential, telecommuter and business markets. The Cisco 6100 is part of Cisco's leadership architecture that breaks through the DSL service profitability barrier. The 6100 supports a broad range of users by allowing differing modem pooling rates and varying degrees of subtending in a fully NEBS Level 3 compliant package. Through Digital Off-Hook technology, each Cisco 6100 Advanced DSLAM can support up to 400 Asynchronous Digital Line Subscriber (ADSL) users through 64 ADSL modems. Operators can provision the Cisco 6100 Advanced DSLAM to support 1:1 modem configurations or oversubscribed pools of modems from 2:1 to 6.25:1. Basic telephone service splitters are not required at the premises with the Cisco EZ-DSL no-truck-roll technology.
The individual module software versions (and ROM versions as applicable) that comprise System Part Number 9000-001-12 (Release 2.2.0) are as follows:
System Controller S/W | 9651-001-20 |
Network Interface S/W | 9601-001-17 |
Subtending Host Module S/W | 9601-005-08 |
ATU-C S/W | 9101-001-11 |
LIM Controller S/W | 9651-002-10 |
RDF File | 9100-003-03 |
The module software versions are discoverable using ViewRunner.
The following new features are supported by the Cisco 6100 DSLAM in Cisco 6100 Release 2.2. Each feature is discussed in the subsections indicated in parentheses.
The inband management channel feature provides an additional channel (other than out-of-band Ethernet) on the network side of the 6100 to manage 6100. The inband management channel feature will be transparent to the network management system (NMS). Instead of conventional Ethernet physical media, it will use ATM as the physical layer for the management channel. To run IP over ATM, it uses RFC 1483 "Multi-protocol over AAL5" recommendation in NON-ISO-ROUTED-LLC encapsulation mode.
Previous versions of 6100 software send traps to only one recipient (default), which has the same IP address as the TFTP server. The multiple trap recipients feature will allow the user to configure the 6100 to send traps to a maximum of 10 recipients. The outbound traps can also be filtered based on the various programmable levels for each trap recipient.
A routing table has been added to support the inband management channel and multiple trap recipient features so the 6100 can select which interface to use (Ethernet or ATM) for out-bound IP packets. The inband management channel will not work without this feature.
The ADSL Layer 1 disconnect feature allows configuration of a timer on a per subscriber basis which can be used to disconnect a subscriber after a configured time. Two timers are supported, session and idle.
The 136K baud feature adds an additional set of selectable upstream/downstream training rates for ATU-Cs. It provides some immunity to AM radio interference and provides extended reach under low noise conditions.
With reliable dial, each time an ATU-C trains, it memorizes the upstream and downstream training rates so that the next training cycle can be held to around seven seconds. This is very useful in saving training time for the lines with longer loop lengths.
The adjustable training margin feature enables the user to adjust the margin (upstream and downstream) that the CAP physical layer will train to. This allows for optimizing performance dependent on the expected noise environment. The system defaults to 0dB downstream, 0dB upstream.
In 6100 software release 2.1.2, set the training margin to 0dB downstream and 3dB upstream to match the margin for subscribers provisioned under 6100 software release 1.0.1. In 6100 software release 2.2.0, set the training margin to 0dB downstream and 5dB upstream to match the margin for subscribers provisioned under 6100 software release 1.0.1.
For new subscribers being provisioned under 6100 software release 2.2.0, set the training margin to be 3dB downstream and 6dB upstream.
This enhancement allows an unlimited number of 6100 IP addresses/names to be selectable for management. In previous releases of ViewRunner for Windows, a maximum of 14 6100 IP addresses/names were supported.
With the addition of a feature compatibility matrix file (FCM), ViewRunner for Windows can now manage several 6100 software release levels. ViewRunner reads a release definition file (RDF) to determine what features are supported on a given 6100 system controller (regardless of its release level) and customizes the features presented to the user when connected to that 6100.
The FCM file included with ViewRunner for Windows Release 2.2.0 includes a feature description of all 6100 software releases up to and including Release 2.2.0. Newer 6100 releases may be managed by ViewRunner without updating this file. However, the user is warned each time a new 6100 IP address is discovered if that node's system controller (SC) software is not recognized. In these cases, ViewRunner will present the default SC 2.2.0 feature set to the user.
The most current versions of the FCM can be obtained through the Cisco Connection Online (CCO).
When a user chooses to upgrade the current 6100 software, a new software download wizard facilitates updating the images for that 6100 to match those specified in a given release definition file (RDF).
The most current versions of the RDF and 6100 software images can be obtained through the Cisco Connection Online (CCO).
The bugs listed in Table 1 are fixed in Cisco 6100 Release 2.2.0
| Bug Number | Description |
|---|---|
1689 | SC Ethernet port becomes non-functional. |
2044 | GFC multiplexing bit not getting cleared on SHM port 2 connections. |
2278 | DS3 NI dropped all cells for port 2 of SHM. |
2279 | Partial Packet discard not functioning on SHM. |
2335 | IPC congestion, packet loss between LCM and LIM. |
2328 | SMB address reset can cause a LCM to retry SMB message to LIM. |
2368 | NI reports HEC errors for valid cells from SHM port 2. |
1997 | Download server ASSERTs and CLEARs INFO event for DL underway. |
2001 | Loss Of Service alarm is not reported by NI DS3. |
2009,2030 | The downstream modem connections are limited to a 3.2 Mbs bandwidth. |
2035 | Five events for the Subtend ports have incorrect severity. |
1704 | Sometimes short DS3 loopback cables cause data transmission errors (Hardware fix - Ferrite added). |
1842 | During heavy management IP network congestion, software download if images from the management station to the SC can fail. |
The bugs listed in Table 2 are open problem reports as of Cisco 6100 Release 2.2.0.
| Bug Number | Description |
|---|---|
157 | The NI becomes active in the redundant position (Slot 11). |
561 | The SC and LIM controller become active in the redundant position (Slot 30 for SC and Slot 12 for LIM controller). |
684 | Occasionally, upon system start-up from reset, a disconnected NI fiber is not reported. |
1131 | During an NI reset, active OC3 cell flow may cause NI alarm and NI shut-down on power-up. |
1497 | Identical fault message text is provided when NI DS3 C-bit parity detection is asserted and cleared. |
1710, 1785 | Infrequently, ViewRunner shows ports Out of Service despite the subscribers, ports, and modules being unlocked. |
1722 | Direct connect ATU-C generated alarm when unlocked and reset. One time occurrence. |
1779 | Had a single instance of an ATU-C reset when the internal distribution of S/W images to modules was not allowed and the ATU-Cs did not contain a current image. |
1854 | Following an NI reset, the following non-fatal events are seen in the event window: FC_SUBTEND_PORT_UTOPIA_ERROR INFO FC_SUBTEND_PORT_INGRESS_ERROR INFO FC_SUBTEND_PORT_INGRESS_2_ERROR INFO FC_SUBTEND_PORT_EGRESS_PARITY INFO |
1901 | Infrequently, in a single LIM chassis system, replacing a LIM controller causes ViewRunner to display two LIM chassis. |
1912, 1913 | DS3 Subtending port does not block data flow upon port or module lock. Unimplemented feature at this time. |
1920 | Had a single instance of an ATU-C with solid Status and Active LEDs, but not discovered via ViewRunner. |
1956 | Had a single instance of being unable to transmit data after DS3 port on SHM was disconnected and reconnected. |
2002 | On the SHM module, the RAI and OCD alarms do not clear when the alarm condition is corrected. |
2017 | NI and SHM LEDs do not behave the same as other modules if there is an error in the download process. |
TBA | ADSL training for the 136 kbaud rates of 1024 and 896, margin could drop (as much as 3 dB) shortly after train for certain noise conditions. |
The bugs listed in Table 3 are open problem reports between Cisco Release 2.1.0 and 2.2.0.
| Bug Number | Description |
|---|---|
2354, 2060 | Restore does not always create a HardWare Revision table. |
2073 | Repeated power-up cycles on OC3 NIUs (6-8 times) can result in a Switch Failure. |
2080 | Date setting accepts the date outside the valid range of 1/1/1990 to 12/31/2089. |
2114 | LIMC does not reset on event 'Loss of communication'. |
2362, 2112 | The SC's IP information gets corrupted after save or after BOOTP completed. |
2176 | When locked, 6100 modules still give alarms when pulled from chassis. |
2336 | Incorrect image creation date. |
2352 | After resetting the SC through SNMP, the SC cannot be reset again when it comes up. |
2364 | Fabric Control will not configure transit VPCs. |
2390 | On one occasion the ATUC downloaded the code twice. |
2405 | If the tftp path (in ViewRunner) for software download is greater than 45 characters, SC may crash. |
2375, 2407 | The software download may fail during retries. |
2409 | Deleting transit subscriber with large number (>50) of transit PVCs, may cause SC to crash. |
Use these release notes in conjunction with the documents listed in this section.
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, description 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.
For the latest information on caveats and known problems, follow these steps to consult CCO:
Step 1 Connect to CCO as directed in the section above.
Step 2 On the CCO home page, click LOGIN, which appears in green in the menu bar at the top of the page, and log into CCO. (If you are not a registered CCO user, follow the instructions to register so that you can log in.)
Step 3 After you log in, click Software & Support on the CCO home page.
Step 4 On the Software & Support page, click Technical Tools.
Step 5 On the Technical Tools page, click Bug Toolkit II. (Bug Toolkit II is not visible on the Technical Tools page unless you log in to CCO as directed in Step 2.)
Step 6 Use one of the tools to get up-to-date bug information. For example, click Search for Bug by ID Number, then enter a bug ID, such as CSCdk09616, when prompted. For instructions on using the bug tools, go to the bottom of the Bug Toolkit II page and click Help—How to Use the Bug Toolkit.
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.
Posted: Mon Sep 16 16:27:12 PDT 2002
All contents are Copyright © 1992--2002 Cisco Systems, Inc. All rights reserved.
Important Notices and Privacy Statement.