|
|
March 15, 2002
 |
Note You can find the most current Cisco IOS documentation, including release notes, on Cisco Connection Online (CCO). These electronic documents may contain updates and modifications made after the hard copy documents were printed. |
These release notes describe features and caveats in Cisco IOS Release 12.1(4)DA for the Cisco 6100, Cisco 6015, Cisco 6130, Cisco 6160, and Cisco 6260 digital subscriber line access multiplexers (DSLAMs).
For pointers to more information about the Cisco 6015, Cisco 6160, Cisco 6260, Cisco 6130, and their software, refer to the "Related Documentation" section. To learn more about caveats, visit the Cisco web site—See the "Obtaining Technical Assistance" section for details. Information about electronic documentation can be found in both the "Obtaining Technical Assistance" section and in the "Related Documentation" section.
This document contains the following topics:
Cisco IOS Releases 12.1(4)DA runs on these DSLAM systems:
This section provides new and changed information for Cisco IOS releases.
This section describes new features in Cisco IOS Release 12.1(4)DA.
The Cisco 6015 is an ATM-based DSL multiplexer designed to support from 4 to 48 subscribers per chassis in remote cabinets, smaller COs, and MDU sites in a scalable fashion. Through subtending, multiple 6015s can be deployed to provide connectivity to more than 48 subscribers. It is a smaller density companion to the Cisco 6100/6130/6160/6260 DSLAM product family.
|
Note The Cisco 6015 system support is available in this release; however, at the date of this release, the Cisco 6015 system is not shipping. The Cisco 6015 system is expected to ship within the next quarter. Please contact your sales representative for more information on the Cisco 6015 system availability. |
New components supported include:
The 6015 supports two configurations:
Both of these configurations are based on the DS3+8xT1/E1 IMA NI-2.
The DS3+8xT1/E1 IMA NI-2 supports two new features for Release 12.1(4)DA:
The DS3+8xT1/E1 IMA NI-2 supports two modes of operation:
The mode of operation is determined based on the type of I/O module (DS3/T1 or E1) that is detected at system startup.
The T1/E1 inverse multiplexing over ATM (IMA) feature uses IMA technology to aggregate multiple low-speed links (T1/E1) into one or more IMA groups at speeds between 1.5 Mbps to 16 Mbps. IMA breaks up the ATM cell stream and distributes the cells over the multiple physical links of an IMA group and then recombines the cells into a single stream at the other end of the connection. The ATM cells are distributed in a round-robin fashion over the physical links of the IMA group, demultiplexed at the receiving IMA group, and passed in their original form to the ATM layer. Using the multiple links of an IMA group increases the logical link bandwidth to approximately the sum of the individual link rates.
The eight links on the DS3+8xT1/E1 IMA NI-2 can be independent ATM links or can be configured into one or more IMA groups. There are four static IMA groups. Each IMA group can contain from zero to eight T1/E1 links. Any combination of independent T1/E1 links and IMA groups is allowed, up to eight T1/E1 links total.
Some examples of allowed combinations are
|
Note E1 IMA group bandwidth is limited to six links. Cell loss will occur if an IMA group has more than six links and more than 12 Mbps are sent through it. The loss only occurs on groups with greater than six E1 links. All eight links can be used in different groups, however (for example, six in group 0, two in group 1). This does not affect T1 operation (that is, all eight T1 links may be used in a group). This problem is described in DDTS report CSCdr45623. |
For detailed information, see the T1/E1 Inverse Multiplexing over ATM feature module.
The trunk selection feature allows you to configure any WAN interface (the DS3, any T1 link, any E1 link, or any IMA group) as the trunk. When you configure a T1/E1 link or an IMA group as the trunk, the DS3 port is disabled. When you select the DS3 port as the trunk, the T1/E1 links and IMA groups are all treated as subtended ports.
This release adds support for an E3 trunk with 2xE3 subtends on the Cisco 6260. E3 operation is provided with the new 6260 E3+2xE3 I/O module combined with the existing DS3/E3+2xDS3/E3 NI-2.
The MPLS VPN mapping of RFC 1483 routed sessions feature enables most Cisco DSLAMs with NI-2 controller cards and connected customer premises equipment (CPE) to participate in MPLS VPNs.
The following DSLAM platforms support MPLS VPN mapping of RFC 1483 routed sessions:
For detailed information on configuring MPLS VPN mapping of RFC 1483 routed sessions see the MPLS VPN Mapping of RFC 1483 Routed Sessions feature module.
This section provides information about the latest features in Cisco IOS Release 12.1(3)DA.
This release supports the quad port ATUC-1-4DMT-ISDN line card. This line card provides four ADSL/DMT ports per card. With this card, the Cisco 6260 supports operation over POTS and over both 4B3T and 2B1Q ISDN line coding.
This section provides information about the latest features in Cisco IOS Release 12.1(2)DA.
This release supports the 8-port IDSL ITU-C line card. With this 8-port card, the Cisco 6160 can support up to 256 IDSL subscribers. The IDSL line card uses 2B1Q line coding and offers configurable data rates of 56 kbps, 64 kbps, 128 kbps, and 144 kbps. The card also provides PPP (RFC 1549) to PPPoATM (RFC 2364) translation and FRF.8 Frame Relay to ATM service level interworking. In this release, the IDSL line card operates in the Cisco 6160 DSLAM only.
This section provides information about the latest features in Cisco IOS Release 12.1(1)DA1.
This software image implements limited support for interoperability with most CPE devices based on the Alcatel DSL chip set (no new hardware is required). Given current generation chipsets from our suppliers, the best possible performance is still achieved between like-to-like chipsets (ADI to ADI). Although this will improve over time, the current software image is interoperable with most CPE devices based on other chipset technology.
Although this image provides enough performance to support mixed chipset deployment of ADSL services in many actual field conditions, most CPE modems will not perform equally well. It is highly recommended that the customer test to ensure that the performance is acceptable before making a decision to deploy a mixed solution (that is, nonADI to ADI).
Specifically, the three following performance limitations exist when implemented with Alcatel-based CPE with the ATUC-1-4DMT (ADI-based) line card:
The ATUC-1-4DMT2 line card now supports the G.992.1 (G.DMT) and G.992.2 (G.lite) standards.
This section provides information about the latest features in Cisco IOS Release 12.1(1)DA.
The Cisco 6160 is a multiservice DSLAM designed for markets in North America. The Cisco 6160 is a NEBS-compliant platform that supports up to 128 subscribers per chassis, with plans to support 256 subscribers in a future release. Initially, subscriber lines can be ADSL with either carrierless amplitude modulation/phase modulation (CAP), discrete multitone (DMT) T1.413-1998, Issue 2-compliant, or SDSL. (IDSL will be available shortly.) Up to 13 Cisco 6160 chassis can be linked together through the use of advanced, fair-service subtending. OC-3c and DS3 trunk and subtending interfaces are available now; T1 IMA will be available in the future. Optional support for analog voice telephony (POTS, or plain old telephone service) is also available through a companion POTS splitter available from ADC. The Cisco 6160 runs the widely deployed Cisco IOS software.
The Cisco 6160 is designed for 23-inch deployments requiring NEBS compliance and compatibility with North American telephone network requirements. Cisco technical and customer service support teams ensure the highest level of customer care and service support available.
The Cisco 6160 internal design is based on a high-performance ATM switching architecture that includes more than 1 million cells of buffering, support for multiple ATM quality of service (QoS) levels, and a variety of ATM traffic management and shaping capabilities.
The Cisco 6160 supports subtending of up to 13 shelves (chassis) of user traffic all concentrated onto a single network WAN interface port. A variety of WAN and subtending interface port configurations are available, allowing for flexible service architecture design and optimized cost. The Cisco 6160 subtending architecture provides fair and prioritized access to network bandwidth for all subscriber traffic, ensuring sustained throughput and performance for all users.
The Cisco 6160 supports a quad-port flexi line card that can be configured for either CAP or DMT T1.413-1998 Issue 2-compliant line encoding, ANSI T1.413 issue 2 (ATM mode), G.992.1 Annex A, G.992.2 Annex A, and configurability between G.lite and G.dmt/T1.413.
Support for ITU and ATM Forum UNI 3.0, 3.1, and 4.0 switched virtual connections (SVCs) provides end-user applications with real-time access to bandwidth and QoS. Support for Private Network Node Interface (PNNI) call routing and Call Admission Control (CAC) is also included.
ATM signaling can be used for automated provisioning of ATM virtual circuits. This capability, also referred to as soft permanent virtual connections (soft PVCs), greatly reduces the time and cost of manual, node-by-node PVC provisioning.
Optional support for voice telephone service (POTS) is accomplished through use of POTS splitter equipment available from a third party, ADC Telecommunications. This POTS splitter solution is optimized for international copper access networks and is designed to ensure that basic telephone service is always available, a feature known as life-line POTS.
Splitters and cable kits are not OEM from Cisco and are available only through ADC. ADC offers several splitter solutions; contact ADC to get additional information:
Rodney McCrea
Rodney_McCrea@adc.com
(612) 403-8922
Two new quad-port line cards are introduced in this release for use with the Cisco 6160 and Cisco 6130:
With these line cards, the Cisco 6160 supports up to 128 ports per shelf. New eight-port line cards, available soon, will double the capacity of the system to 256 ports. Line card options that are planned for future releases include G.SHDSL.
This release supports 96 buckets of 15-minute interval, previous and current 1-day interval DMT performance statistics.
To enable migration from NI-1 to NI-2 without reconfiguring CPEs in the field, in this release the NI-2 DSLAMs support both VPI=1, VCI=1 and VPI=1, VCI=0 configurations on subscriber ports.
The following default values have changed:
| Profile Configuration Command | New Default | Old Default |
|---|---|---|
dmt margin | downstream 6 | downstream 3 |
dmt framing-mode | mode3 | mode1 |
dmt training-mode | quick | standard |
Cisco IOS Release 12.1(1)DA includes new DSP microcode for the ATUC-1-4DMT2 line card for Cisco 6260 and Cisco 6130 DSLAMs.
 |
Caution When you boot the DSLAM for the first time after installing Cisco IOS Release 12.1(1)DA, the DSLAM downloads new microcode to the 4DMT-2 line cards. The microcode download requires about 10 minutes. During the download period, the Active LED on each line card blinks and the DSLAM does not pass data. Until the download is complete, do not remove cards from the chassis. Do not reboot the chassis. If you interrupt the download, the line card's flash memory might be damaged, making it necessary to replace the card. When the download is complete, the Active LEDs on the line cards stop blinking and the lines train as usual. |
You can track the status of a microcode download through software using the command show dsl interface atm slot/port. In the resulting display, look at the Line Status field. If the Line Status field says DOWNLOADING MICROCODE, wait a few minutes and check again.
This section describes the limitations and restrictions for Cisco IOS DSLAM releases.
This section describes the limitations and restrictions for Cisco IOS Release 12.1(4)DA.
This section describes restrictions to Cisco MPLS VPN mapping of RFC 1483 routed sessions.
|
Note DSLAMs running MPLS VPN mapping of RFC 1483 sessions are referred to as IP DSL switches. |
Each IP DSL switch can support up to 50 MPLS VPNs.
MPLS VPN mapping of RFC 1483 routed sessions must not be confused with Integrated Routing and Bridging (IRB). IRB is not supported by MPLS VPN mapping of RFC 1483 routed sessions.
Do not configure subtended interfaces for MPLS VPN services. Only trunk interfaces support MPLS VPN mapping of RFC 1483 routed sessions.
IP DSL switches are not meant for use as MPLS ATM-Label Switch Routers (ATM-LSRs). When designing your network, keep in mind that IP DSL switches act only as Label Edge Routers (LER).
MPLS VPN-enabled interfaces do not perform as well as switched VCs. Please take this into consideration when deploying MPLS VPNs in your networks.
The following Layer 3 services are not supported in Cisco IOS Release 12.1(4)DA:
The following are MPLS-related features that are not a part of the MPLS VPN mapping of RFC 1483 routed sessions feature:
In IP DSL switches, each DSL interface can support multiple Permanent Virtual Circuits (PVCs), but only one routed MPLS VC.
CDM users can provision switched VCs, but CDM does not support configuring routed termination of RFC 1483 sessions.
Routed termination of IDSL connections is not supported in Cisco IOS Release 12.1(4)DA.
The limitations and restrictions for Cisco IOS Release 12.1(3)DA are the same as those listed for Cisco IOS Release 12.1(2)DA, below.
The following restrictions apply to this release:
1. If you are using Cisco DSL Manager (CDM) Version 1.0 or 1.1 software to manage your existing DSLAM network:
a. Do not upgrade the DSLAMs to this new release of Cisco IOS. CDM 1.0 and CDM 1.1 do not support this release of the Cisco IOS software.
b. Spare NI-2 cards are shipped with the most recent release of Cisco IOS software. Therefore, if you install a spare NI-2 in a network that uses CDM, you might need to install an older version of the Cisco IOS software on the spare NI-2. Cisco IOS Release 12.0(8)DA4 and earlier versions are compatible with CDM. Go to the Software Center on CCO to download back versions of Cisco IOS software.
c. When CDM Release 3.0 comes out, it will support the flexi and SDSL line cards only. CDM 3.0 will not allow you to configure or manage IDSL line cards. Configuration and management of IDSL line cards will be supported in a later release of CDM.
d. Refer to your CDM documentation for more information on compatibility between CDM versions and Cisco IOS releases.
2. Cisco IOS Release 12.0(8)DA2 or greater is required for Cisco 6260 and Cisco 6130 systems that contain new 4DMT-2 cards (revision 800-05262-03 or greater). Releases 12.0(8)DA2 and above are also compatible with earlier revisions of the 4DMT line card.
a. You can fall back only to Release 12.0(8)DA1 or greater. The DSLAMs cannot operate under releases prior to 12.0(8)DA1.
b. New 4DMT-2 cards (revision 800-05262-03 or greater) require Cisco IOS Release 12.0(8)DA2 or greater; the cards will not operate under prior releases of software.
3. Cisco IOS Release 12.0(8)DA4 runs only on this hardware:
a. Cisco 6260
b. Cisco 6130 with NI-2 and Cisco 6130-specific system I/O cards
4. The VP tunneling feature cannot be used in conjunction with VCs outside of VP tunnels.
The limitations and restrictions for Cisco IOS Release 12.1(1)DA1 are the same as those listed for Cisco IOS Release 12.1(1)DA, below.
The following restrictions apply to this release:
1. If you are using Cisco DSL Manager (CDM) software to manage your existing DSLAM network:
a. Do not upgrade the DSLAMs to this new release. No CDM version is available to work with this release of the DSLAM software.
b. Spare NI-2 cards are shipped with the most recent release of Cisco IOS software. Therefore, if you install a spare NI-2 in a network that uses CDM, you might need to install an older version of the Cisco IOS software on the spare NI-2. Cisco IOS Release 12.0(8)DA4 and earlier versions are compatible with CDM. Go to the Software Center on CCO to download back versions of Cisco IOS software.
2. Cisco IOS Release 12.0(8)DA2 or greater is required for Cisco 6260 and Cisco 6130 systems that contain new 4DMT-2 cards (revision 800-05262-03 or greater). Releases 12.0(8)DA2 and above are also compatible with earlier revisions of the 4DMT line card.
a. You can fall back only to Release 12.0(8)DA1 or greater. The DSLAMs cannot operate under releases prior to 12.0(8)DA1.
b. New 4DMT-2 cards (revision 800-05262-03 or greater) require Cisco IOS Release 12.0(8)DA2 or greater; the cards will not operate under prior releases of software.
3. Cisco IOS Release 12.0(8)DA4 runs only on this hardware:
a. Cisco 6260
b. Cisco 6130 with NI-2 and Cisco 6130-specific system I/O cards
4. The VP tunneling feature cannot be used in conjunction with VCs outside of VP tunnels.
This section provides important information about Cisco IOS DSLAM releases.
When you upgrade to the Release 12.1(4)DA images on the NI-2, Cisco recommends that you upgrade the bootflash image on the NI-2 to the 12.1(4)DA dboot image. This is a result of a problem (CSCdr89374) in old bootflash images. This defect may cause the flash application image to fail to self-decompress successfully.
To upgrade the dboot image in bootflash, perform the following steps:
Step 2 Erase the current bootflash image.
Step 3 Squeeze the bootflash.
Step 4 Copy ni2-dboot-mz.121-4.bin to bootflash.
Step 5 Delete any flash files and squeeze flash to free space for ni2-dsl-mz.121-4.bin.
Step 6 Copy ni2-dsl-mz.121-4.bin to flash.
Step 7 Record the current setting of the config-register.
Step 8 Set the config-register to 0x0000 so that the NI-2 will reboot in the rom monitor.
Step 9 Change the boot system command to:
boot system flash:ni2-dsl-mz.121-4.binStep 10 Save the running configuration.
Step 11 Reset the system. The NI-2 will come up in the rom monitor.
Step 12 From the rom monitor, enter the following commands to force the system to use ni2-dboot-mz.121-4.bin as the bootstrapper:
rommon > unset BOOTLDRWhen the NI-2 boots, it uses ni2-dboot-mz.121-4.bin as your bootstrapper and ni2-dsl-mz.121-4.bin as the application image.
Step 13 Set the config-register to the saved setting from Step 7.
The following problem is fixed in the IOS 12.1(4)DA release. Upgrade to this release to fix this IDSL problem. The ITUC-1-8IDSL line card is not forwarding traffic after reload/reboot because the ISDN chipset is initializing indefinitely due to network clock synchronization.
When you upgrade from a previous release to 12.1(3)DA or 12.1(4)DA, the default soft PVC addresses on all interfaces change. This only occurs when you upgrade to release 12.1(3)DA or 12.1(4)DA from a previous release. This will not happen when you upgrade to future releases from 12.1(4)DA.
Workarounds:
If you wish to use a Cisco router for an IDSL application and the router is running a Cisco IOS release prior to 12.1, you must configure the ISDN switch type. If you do not configure the ISDN switch type on the Cisco router, the router's BRI interface may not come back up after the IDSL line goes down and back up.
To prevent this problem from occurring, execute the isdn switch-type basic-ni command in global configuration mode on the router.
This problem does not occur if the Cisco router is running Cisco IOS Release 12.1 or later.
After you upgrade a DSLAM from Cisco IOS Release 12.0(x)DA to 12.1(1)DA, 12.1(2)DA, or 12.1(3)DA, you might experience a problem that results from a change in some of the DMT defaults in the DSL profiles. The changes, which are listed in the "Changes to Default Values in DSL Profiles" section, affect the training mode, overhead framing, and DMT margin parameters. This problem is fixed in Release 12.1(4)DA.
The problem is triggered when you edit your DSL configuration profiles after upgrading to Cisco IOS Release 12.1(x)DA.
The system checks its startup configuration file for a release number, and if it finds a number earlier than 12.1, it automatically adds the following commands to the profile whenever you edit the profile. These commands set the profile to use the old default values for training mode, overhead framing, and DMT margin.
dmt training-mode standard
dmt overhead-framing mode1
dmt margin downstream 3 upstream 3
The commands are added so that the changed defaults in Cisco IOS Release 12.1(x)DA will not affect your configuration. However, the system continues to add the commands to your configuration every time you edit profiles, unless your startup configuration file contains a 12.1 release stamp.
Workaround: Follow these steps. Start with Step 2 if you have already completed the upgrade.
Step 2 Issue the command copy running-config startup-config. Now the startup configuration file has a 12.1(x)DA stamp in it.
Step 3 Reboot the DSLAM again.
Now you can change the configuration without difficulty. [CSCdr66665]
This release supports the full range of VPI values: 0 to 255. However, if you configure VP tunnels with traffic shaping, you can use only 32 VPIs out of that range. If you have not yet assigned any VPIs, all values from 0 to 255 are available. Once you start assigning VPIs, however, the assigned VPIs limit the VPIs that remain. (You assign VPIs using the atm pvp or atm pvc commands.)
After a particular VPI value is assigned to a shaped VP tunnel, every 32nd VPI value above and below the first one is eliminated—that is, the original value modulo 32. For example, if you assign VPI 94 to a shaped VP tunnel, the following VPI values become unavailable for any purpose: 30, 62, 126, 158, 190, and 222.
To avoid problems, choose a block of 32 consecutive VPI values (for example, 0 to 31 or 101 to 132). The software rejects invalid VPI values.
You can install multiple Cisco 6160 chassis within a telco equipment rack. A standard seven-foot equipment rack can house four Cisco 6160 chassis, stacked one on top of another. This configuration maximizes the DSL density within a seven-foot rack. However, if space is available or if you are interested in using multiservice capabilities that the chassis will support in the future, Cisco recommends that you install no more than three Cisco 6160 chassis within a seven-foot rack. Leave a space of at least 2.5 rack units (4.375 inches, or 11.1 cm) beneath each chassis for future cable management use.
If you use both the Cisco DSL Manager (CDM) application and the command line interface (CLI) to configure and manage your DSLAMs, you must the synchronize the CDM to your management database on a regular basis. (If you use only the CDM or only the CLI, you need not synchronize your database.) Refer to the release notes for the Cisco DSL Manager 2.0 or later for more information.
Turn console logging off if you plan to reboot the DSLAM. Turn console logging back on after the system comes up. (Console logging is turned on by default.) Use the global configuration commands no logging console (to turn the feature off) and logging console (to turn it on).
If console logging is on when the system reboots, the large volume of console messages consumes CPU time. As a result, the system comes back up more slowly and line cards might reload repeatedly, causing further delays.
This section describes unexpected behavior in the system. A tracking number, if one exists, is provided in square brackets at the end of each description. Please refer to the tracking number if you communicate with Cisco Systems about any of these issues.
The caveats in this section apply only to IOS Release 12.1(4)DA. Other open caveats that apply to this Release 12.1(4)DA are described in the "Open CaveatsRelease 12.1(3)DA" section, "Open CaveatsRelease 12.1(2)DA" section, "Open CaveatsRelease 12.1(1)DA1" section, and "Open CaveatsRelease 12.1(1)DA" section.
The atm oam intercept end-to-end command is not supported. This means that the NI-2 cannot insert or remove end-to-end OAM cells if it is an intermediate node; that is, if the VC is not terminated to the SAR. The command is not supported on any releases.
Workaround: Terminate the VC to the SAR. [CSCds36465]
E1 IMA group bandwidth is limited to six links. Cell loss will occur if an IMA group has more than six links and more than 12 Mbps are sent through it.
The loss only occurs on groups with greater than six E1 links. All eight links can be used in different groups, however (for example, six in group 0, two in group 1). This does not affect T1 operation (that is, all eight T1 links may be used in a group).
Workaround: Do not configure an IMA group with more than six E1 links. [CSCdr45623]
Cell loss on the subscriber (DSL) ports may be seen if you select an IMA group and the trunk is down. The loss only happens if the trunk IMA group is down. [CSCds02810]
Workarounds:
The CLI incorrectly accepts configuration input on reserved VCIs 3 and 4 through the atm pvc command.
Example:
DSLAM#configure terminal
Enter configuration commands, one per line. End with CNTL/Z.
DSLAM(config)#interface atm1/3
DSLAM(config-if)#atm pvc 1 4 interface atm0/0 0 120
DSLAM(config-if)#
DSLAM#show running interface atm1/3
Building configuration...
Current configuration : 62 bytes
!
interface ATM1/3
no ip address
no atm ilmi-keepalive
end
VC-Table
ATM1/3 1 4 PVC ATM0/0 0 120 SNAP DOWN
If you attempt to create virtual channel connections (VCC) 1/3 or 1/4 using the pvc command an error message appears.
DSLAM(config)#interface atm1/3
DSLAM(config-if)#pvc 1/3
%ATM: Invalid VCI of 3 requested: (ATM1/3): Not creating vc:1:3
DSLAM(config-if)#pvc 1/4
%ATM: Invalid VCI of 4 requested: (ATM1/3): Not creating vc:1:4
DSLAM(config-if)#pvc 1/5
DSLAM(config-if-atm-vc)#
Workaround: Do not attempt to configure VCIs 3 and 4. [CSCdr99296]
If you swap a line card or change the line coding on a DSL interface, the show ip vrf command may display duplicate references to a VRF instance.
Workaround: Do not swap line cards with a different type. Do not change line coding on an active interface. [CSCds29146]
Configuring more than 32 PVP subinterfaces on the trunk interface of the NI-2 may cause a loss of connectivity to remote peer MPLS routers.
Workaround: Currently, there is no workaround. [CSCdr88865]
No fragmentation occurs at the IP layer.
Workaround: There is no workaround. The default MTU settings work fine for Layer 3 services on the IP DSL Switch. [CSCds15469]
ATM cell corruption could be detected on the Customer Premises Equipment (CPE) as a result of running the NI-2 Rev02 (B) SAR. To determine the NI-2 SAR version:
1. Load the IOS Release 12.1(4)DA software image.
2. Type show controller atm0/0.
The SAR revision number will be shown in the show controller atm0/0 output.
Workaround: Currently, there is no workaround. A different hardware revision of the NI-2 SAR (Rev03) must be installed. [CSCds05184]
Using the debug atm error command generates the following invalid error message:
"ATM(ATM0/1):point-to-point interface does not have a VCD"
The message appears when there is no PVC defined on the atm0/1 physical interface.
Workaround: This message can be ignored. Configuring a point-to-point PVC on the physical uplink interface is unnecessary for MPLS functionality. [CSCdr97541]
DSL interfaces reset when CPU usage approaches 100 percent for an extended period of time.
Workaround: Using the show proc cpu command, identify the CPU hogging interfaces. Move those interfaces to a less taxed IP DSL Switch. verify that the CPU usage exceeds 95 percent. Then, using the show interface accounting command, take successive samplings of packet counters to identify the interfaces with the highest traffic rates. Once these interfaces are identified, move them to an IP DSL switch with lower CPU usage rates. [CSCds23638]
Output from the atm debug command returns misleading error messages while configuring a point-to-point PVC or MPLS-switched interface.
The following erroneous message is logged:
c6100_atm_add_vc_to_swsb: Error adding VC to vc-list
Workaround: This message can be ignored. The VC creation has taken place. [CSCds15732]
Site-of-Origin tagging does not work when associated with the ip vrf sitemap on customer edge (CE) interfaces.
Workaround: Currently, there is no workaround. [CSCdr93090]
The ATM command syntax atm pvc vpi vci is not parsed correctly by the IP DSL Switch. [CSCds05174]Workaround: Use the following syntax:
atm pvc vpi vci interface atm [slot/port] vpi vci
The maximum number of Interior Gateway Protocol (IGP) routes on the IP DSL Switch is limited to 3500.
Workaround: Currently, there is no workaround. [CSCdr89959]
Outbound access- lists on uplink and CE interfaces are ignored.
Workaround: Currently, there is no workaround. [CSCds01820]
Aggregate throughput in NI-2s running Layer 3 services is poor when average packet sizes are less than 512 bytes.
Workaround: Currently, there is no workaround. [CSCdr92284]
With a large number of VPN routes within a single VPN domain, the CPU may approach 100 percent usage for too long. This causes system instability.
Workaround: It is unlikely that a single VPN would ever contain this many routes. If it does, however, segment the network into multiple VPNs. [CSCds27853]
Static routes are not applied to a DSL interface if you change its line coding.
Workaround: Remove all static IP routes using the no ip route and no ip route vrf commands before you change line coding. Recreate the static routes after the line coding is changed. [CSCds38810]
Disabling Cisco Express Forwarding (CEF) while MPLS traffic is being passed can destabilize the IP DSL Switch.
Workaround: CEF is a prerequisite to running MPLS. It should never be disabled while MPLS traffic is being passed. Leave CEF enabled. [CSCds29151]
If you attempt to remove a VP-tunnel interface on the atm0/1 you receive the following incorrect error message:
Example:
DSLAM(config)#interface atm0/1.60
DSLAM(config-subif)#no tag-switching atm vp-tunnel 60
%Invalid tag vpi range for selected VP-tunnel
Hardware does not support the specified VPI, 1
Workaround: None. This message can be ignored. [CSCdr89031]
When you create a VPN routing and forwarding instance (VRF) on systems with an older bootflash image, the following message may appear:
% Can't create VRF <VRF-ID>
This is message is generated because of an outdated bootflash image.
Workaround: The message can be ignored. It has no impact on MPLS VPN functionality. [CSCdr89698]
The caveats in this section apply only to IOS Release 12.1(3)DA. Other open caveats that apply to this Release 12.1(3)DA are described in the "Open CaveatsRelease 12.1(2)DA" section, "Open CaveatsRelease 12.1(1)DA1" section, and "Open CaveatsRelease 12.1(1)DA" section.
The line card operational mode reports G.DMT when the operational mode is actually T1.413. If the CO line card requests T1.413 mode, and the CPE is Alcatel based, the return value is decoded incorrectly by the Globespan chipset for Alcatel based CPE's.
Workaround: None. This is a reporting error only; the operation of the CPE is not affected. [CSCdr58384]
There is a performance issue when the line length is less than 8 K feet with LOW noise, and the downstream bit rate is less than 512 kbps.
Workaround: Provision the downstream bit rate to be 512 kbps or above. [CSCdr63938]
This section describes problems with the ATUC-1-4DMT-I line card.
Enabling DMT trellis line coding on the 4xDMT/ISDN ADI-based line card can decrease link reliability by causing problems passing data due to errored second events and data corruption in the downstream and upstream directions. ADI/Aware has a known problem where high errored seconds may result if trellis coding is turned on. This problem is not scheduled to be fixed in the 2.0 release, which is currently where the 4xDMT/ISDN code is branched.
On the 4xDMT/ISDN ADI-based line card, having trellis coding enabled will decrease link reliability by causing problems training or passing data. There is no way to accurately predict when it will be reliable. Therefore, trellis coding is disabled by default on the NI-2 to ensure that it is not accidentally enabled with the 4xDMT/ISDN line card.
Workaround: DMT trellis line coding is not enabled by default on the NI-2, because it is not supported on the 4xDMT/ISDN ADI-based line card. [CSCdr92590]
This problem occurs at long loop lengths (11500 feet and above) when using the quick training mode of the 4xDMT/ISDN ADI-based line card. It can decrease link reliability by causing problems passing data due to errored second events and data corruption in the downstream direction.
On the 4xDMT/ISDN ADI-based line card, using the quick training mode at long loop lengths (3600 m and above) will decrease link reliability. The link will train at a higher data rate, but at lower downstream margins (:for example, 1 or 2 dB) rather than training at a lower data rate and maintaining the requested downstream margin (:for example, 6 dB). This can decrease link reliability by causing errored second events and data corruption in the downstream direction due to the acquired lower downstream margins.
Workaround: Use the standard training mode to train up the link at long loop lengths (11500 feet and above). [CSCdr93540]
This problem is identical to the problem described in DDTS report CSCdm89068, which describes the same symptoms that appear when using the ATUC-1-4DMT line card.
In some situations, the reported (actual) margins may be higher than the configured values. Depending on the port configuration, there are effective minimum end-to-end margin values for combinations of parameters including:
Workaround: If you configure the margins for a port below these effective minimum margins, the system accepts the margin configuration, but the margin values that are actually used and reported are the effective minimum end-to-end values. The actual margins are essentially clipped at these effective minimum values. [CSCdr93546]
The effective minimum margins for the downstream and upstream directions are given in the following tables:
| Train Mode | Frame Mode | Intlv >0 | Trellis Coding | Ckbytes >0 | Downstream Bit-rate Range (kbps) | ||||
|---|---|---|---|---|---|---|---|---|---|
| 32-640 | 672-768 | 800-3040 | 3072-6112 | 6144-8032 | |||||
X | X | X | X | No | 0 | 0 | 0 | 0 | 0 |
Quick | 0,1 | No | Disabled | Yes | 0 | 5 | 5 | 4 | 5 |
Quick | 0,1 | No | Enabled | Yes | 0 | 6 | 6 | 5 | 6 |
Quick | 0,1 | Yes | Disabled | Yes | 0 | 6 | 6 | 5 | 6 |
Quick | 0,1 | Yes | Enabled | Yes | 0 | 7 | 7 | 6 | 7 |
Quick | 2,3 | No | Disabled | Yes | 0 | 0 | 5 | 4 | 5 |
Quick | 2,3 | No | Enabled | Yes | 0 | 0 | 6 | 5 | 6 |
Quick | 2,3 | Yes | Disabled | Yes | 0 | 0 | 6 | 5 | 6 |
Quick | 2,3 | Yes | Enabled | Yes | 0 | 0 | 7 | 6 | 7 |
Stnd. | 0,1 | No | Disabled | Yes | 2 | 2 | 2 | 1 | 2 |
Stnd. | 0,1 | No | Enabled | Yes | 3 | 3 | 3 | 2 | 3 |
Stnd. | 0,1 | Yes | Disabled | Yes | 3 | 3 | 3 | 2 | 3 |
Stnd. | 0,1 | Yes | Enabled | Yes | 4 | 4 | 4 | 3 | 4 |
Stnd. | 2,3 | No | Disabled | Yes | 2 | 2 | 2 | 1 | 2 |
Stnd. | 2,3 | No | Enabled | Yes | 3 | 3 | 3 | 2 | 3 |
Stnd. | 2,3 | Yes | Disabled | Yes | 3 | 3 | 3 | 2 | 3 |
Stnd. | 2,3 | Yes | Enabled | Yes | 4 | 4 | 4 | 3 | 4 |
| Train Mode | Frame Mode | Intlv >0 | Trellis Coding | Ckbytes >0 | Upstream Bit-rate Range (kbps) | ||
|---|---|---|---|---|---|---|---|
| 32-640 | 672-768 | 800-864 | |||||
X | X | X | X | No | 0 | 0 | 0 |
Quick | 0,1 | No | Disabled | Yes | 0 | 5 | 5 |
Quick | 0,1 | No | Enabled | Yes | 0 | 6 | 6 |
Quick | 0,1 | Yes | Disabled | Yes | 0 | 6 | 6 |
Quick | 0,1 | Yes | Enabled | Yes | 0 | 7 | 7 |
Quick | 2,3 | No | Disabled | Yes | 0 | 0 | 5 |
Quick | 2,3 | No | Enabled | Yes | 0 | 0 | 6 |
Quick | 2,3 | Yes | Disabled | Yes | 0 | 0 | 6 |
Quick | 2,3 | Yes | Enabled | Yes | 0 | 0 | 7 |
Stnd. | 0,1 | No | Disabled | Yes | 2 | 2 | 2 |
Stnd. | 0,1 | No | Enabled | Yes | 3 | 3 | 3 |
Stnd. | 0,1 | Yes | Disabled | Yes | 3 | 3 | 3 |
Stnd. | 0,1 | Yes | Enabled | Yes | 4 | 4 | 4 |
Stnd. | 2,3 | No | Disabled | Yes | 2 | 2 | 2 |
Stnd. | 2,3 | No | Enabled | Yes | 3 | 3 | 3 |
Stnd. | 2,3 | Yes | Disabled | Yes | 3 | 3 | 3 |
Stnd. | 2,3 | Yes | Enabled | Yes | 4 | 4 | 4 |
This section describes problems with the IDSL line card.
When you enter the show controllers idsl card/port command after a reload/reboot, an excessive number of network clock losses is reported. This is normal because the network interface module is being reinitialized and network clocking has yet to be established.[CSCdr91534]
Workaround: None.
Under certain conditions, if you issue the no frame-relay soft-vc dlci, another frame-relay soft-vc on that interface will improperly be deleted. This behavior only applies to IDSL interfaces.
The conditions under which this is known to occur are as follows:
Workaround: Ensure that a valid dlci is specified when you delete a frame-relay soft-vc. [CSCds06327]
The following are miscellaneous problems with this release.
The following are loopback and test problems with this release.
On the Cisco 6160 DSLAM equipped with IDSL line cards, ATM traffic shaping and policing might not function properly. Shaping is enabled on Frame- Relay and PPP PVCs and soft PVCs with the upc drop option of the frame-relay pvc, frame-relay soft-vc, ppp pvc, or ppp soft-vc commands. Policing without traffic shaping (that is, tagging of cells exceeding the ATM traffic descriptor parameters) is enabled with the upc tag option of the above four commands.
Specifically, the following problems are known to exist:
There are no workarounds to the above problems.[CSCdr70582]
When an NI-2 is shipped, the ATM address is blank. When that NI-2 is provisioned in a chassis, an ATM address is generated using the MAC address of the chassis. If that NI-2 is moved to another chassis and a new NI-2 is installed in the original chassis, the two NI-2s will have the same ATM address.
Workaround:
1. Issue the command show hardware chassis and note the MAC address from the IO card EEPROM field.
2. Issue the command show atm address and note the ATM address.
3. Issue the command configure terminal.
4. Issue the command atm addr <enter the first 7 bytes from the original address><enter MAC addr><enter MAC addr again>.00.'
5. Enter no atm address (original atm address).
6. And finally issue reload.
The caveats in this section apply only to IOS Release 12.1(2)DA. Other open caveats that apply to this Release 12.1(2)DA are described in the "Open CaveatsRelease 12.1(1)DA1" section, and "Open CaveatsRelease 12.1(1)DA" section.
On rare occasions, the results of the command show interface idsl slot/port indicate that an interface is up when it is in fact down. You can verify this failure mode by issuing the command show controllers idsl slot/port and confirming that the "C/I" state is not "0xF3".
Workaround: Issue the shutdown command followed by the no shutdown command on the IDSL interface. [CSCdr23602]
In a fully loaded chassis after hours of normal operation, one or more ports of a line card begins to have trickle CRC errors at medium to high data rates. The problem resolves itself upon retrain. [CSCdr46450]
We recommend that trellis coding be enabled in this release for the Flexi-DMT line card.
|
Note Note: We recommend that you disable trellis coding for ATUC-1-4DMT2 line cards. See the "Incorrect Margin Value Reported for Some Cisco 678 Connections" section. |
We recommend that the interleave configuration be set to 1000 microseconds or greater for optimal reach performance. [CSCdr27700]
When you change a flexi card type from DMT to CAP or CAP to DMT, the active alarms are not cleared.
Workaround: Before you change the line card provisioned mode, clear the existing alarms by issuing shutdown commands to all ports with active alarms. [CSCdr13611]
When the DSLAM connects to a Cisco 678 CPE running a software version older than CBOS Release 2.3.5, the downstream margin reported is half of the actual margin.
The caveats in this section apply only to IOS Release 12.1(1)DA1. Other open caveats that apply to this Release 12.1(1)DA1 are described in the "Open CaveatsRelease 12.1(1)DA" section.
When IP routing is enabled on an NI-2 DSLAM, the Ethernet port 0/0 does not come back up by itself after it experiences a problem. To reenable the port, enter the shut command in interface configuration mode, then enter the no shut command.
Workarounds: Do one of the following:
Xmodem, which resides in rommon on the NI-2 card, is not working. As a result, there is no way to recover if you delete the software image in bootflash and then try to reboot the system. In this case you must replace the NI-2.
Workaround: If you delete the image in bootflash, copy a new image into bootflash before shutting down or rebooting the system. [CSCdr22773]
When the DSLAM connects to a Cisco 678 CPE running a software version older than CBOS Release 2.3.5, the downstream margin reported is half of the actual margin.
The caveats in this section apply only to IOS Release 12.1(1)DA.
The software check for invalid VPI numbers on VP tunnels occurs only if the interface associated with the VP tunnel is up. If the interface is down, the system accepts invalid VPI values, but when the interfaces come back up, VPIs are assigned unpredictably. For more information on assigning VPI values, see the "Assigning VPI Values to Shaped VP Tunnels" section.
Workaround: Use a block of 32 consecutive VPI values (for example, 0 to 31 or 101 to 133). Or, if you require a complete range of VPI values, make sure not to configure the VPIs that become unavailable once a VPI is used for a shaped VP tunnel. [CSCdr19173]
When the DSLAM connects to a Cisco 678 CPE running a software version older than CBOS Release 2.3.5, the downstream margin reported is half of the actual margin.
When autoconfiguration is enabled on a subscriber port, the DSLAM might set the maximum VCI bits for that port to an incorrect value that exceeds the maximum allowed value of 8. This depends upon a negotiated value with the connecting port on the adjacent node.
Workaround: Use the command no atm auto-configuration to disable autoconfiguration for subscriber ports. (Autoconfiguration is enabled by default.) [CSCdr18239]
The input queue field in the output of the show interface atm slot#/port# command is not applicable in the NI-2 environment. Ignore this field. [CSCdp68075]
This applies to the ATUC-1-4DMT2 line card. If a port is configured for standard training mode and the number of FEC check bytes for the downstream direction is configured for 2, 6, 10, or 14, then the port may have trouble staying trained if the loop conditions (such as loop length and noise levels) are favorable for training at a high bitrate. In other words, if the port would otherwise train at or above certain threshold bitrates in the downstream direction, and the FEC check bytes per codeword is set for 2, 6, 10, or 14, then the port continually retrains.
This problem does not occur if any of the following are true:
The threshold bit rates at which this problem appears for each check byte per codeword setting are as follows:
| FEC Check Bytes per Codeword | Threshold Downstream Bit Rate |
|---|---|
0 | Problem does not occur |
2 | 8000 kbps |
4 | Problem does not occur |
6 | 7872 kbps |
8 | Problem does not occur |
10 | 7744 kbps |
12 | Problem does not occur |
14 | 7616 kbps |
16 | Problem does not occur |
Workarounds: Do one of the following:
When a hardware failure occurs on one or more of the ports on a 4DMT-2 line card, every other (otherwise healthy) port on the line card might be unable to train. Cisco strongly recommends that you replace or remove any line card with any defective ports. [CSCdp05249]
The extended version of the ATM ping command returns "Bad Interface Port" when it is executed on the NI-2. The system accepts the same command in line form, however.
For example, the NI-2 accepts this command:
DSLAM> ping atm interface atm 0/1 0 100 atm-prefix 47.00918100000000E01417DA01
If you use the extended command line, however, the same command is rejected:
ping
Protocol [ip]: atm
Interface [card/port]: 0/1
% Bad Interface Port #
Workaround: Use the line form of the ping atm command. [CSCdr27204]
When you change a flexi card type from DMT to CAP or CAP to DMT, the existing virtual channels (VCs) on the interfaces of that card are not deleted; instead they are kept in REMOVED state. Hence you cannot reuse these VCs for the new card type. However, if you change the card type back to the original type, these VCs become available.
Workarounds: Do one of the following:
These problems affect SNMP-based management systems, including the Cisco DSL Manager (CDM). You can avoid these problems by using the CLI.
The system incorrectly allows you to create VBR-RT and VBR-NRT tunnels. In fact the system can handle only CBR tunnels, and tunnels created as VBR-RT or VBR-NRT behave like CBR tunnels. [CSCdp21731]
We recommend that trellis coding not be enabled in this release. (Trellis coding is disabled by default.)
Although trellis coding works reliably on most loops and most trains, it does not always work reliably. For some trains on some loops, enabling trellis coding causes continuous errored seconds, as well as corrupted data in the upstream direction. It is not possible to predict the circumstances under which this happens. This problem will be fixed in a later release. [CSCdm73343]
Under certain combinations of upstream bit rate and overhead framing mode, no valid data flows upstream. When the line trains at these combinations, data going upstream is corrupted. Avoid these data rate and framing mode combinations:
| Upstream Bit Rate | Overhead Framing Mode |
|---|---|
32 kbps | Mode 1 |
64 kbps | Mode 2 |
96 kbps | Mode 3 |
Workaround: To avoid this data corruption problem, use these combinations of settings for the lower data rates:
| Upstream Bit Rate | Overhead Framing Mode |
|---|---|
32 kbps | Mode 3 |
64 kbps | Mode 1 |
96 kbps | Mode 1 |
[CSCdm66085]
When the DLSAM is connected to a Cisco 676 or any other CPE that is based on ADI's AD20MSP910 chipset (which was designed to support the older Issue 1 version of the T1.413 ADSL standard), you might experience higher than normal numbers of errored seconds, corrected superframes, and uncorrected superframes. This can occur when the interleaving delay is configured at values less than the maximum (16 msec). The errors can occur in both the upstream and downstream directions. This problem might be more apparent with short loop lengths (for example, those less than 4000 feet).
Workarounds: Do either of the following to eliminate the problem:
The value you configure for the check bytes parameter might not be properly reported by the system. An incorrect check bytes value equal to half of the configured value is reported when a port is set to use standard training mode and the downstream data rate is greater than 7 Mbps. Only the downstream path is affected. The actual ratio of user data to check bytes matches the configuration. [CSCdm90741]
When a line that is configured for quick training mode trains to a downstream bit rate of 8 Mbps or higher, the actual interleaving delay might be reported incorrectly. (The interleaving delay appears in the display for the command show dsl interface atm slot/port.) When this problem occurs, the reported interleaving delay is half of the value that is actually in effect. [CSCdp14712]
The dmt bitswap margin command has no effect in this release. Bit swapping is always disabled. [CSCdm80069]
Sometimes it is impossible to remove a configured PVP. When VP switching is configured from one subscriber port to another using the same VPI number on both the ports, the VP circuit is not set up correctly.
Workaround: Configure different VPI numbers on the subscriber ports at either end of the connection. [CSCdp44469]
If you create a PVC using network management, the system does not allow you to enable OAM RDI. Regardless of your selection for OAM RDI, the cross connect setting forces the OAM RDI to disable. This is related to the CDM issue CSCdp08324.
Workaround: In CDM, edit the PVC and enable OAM RDI. Or in the CLI, use the interface configuration version of the atm oam rdi command. [CSCdp74861]
The maximum size of input queue counter that can be supported by hardware is 255 cells. (You can configure this using the max-size argument of the atm input-queue command.) But software allows configuration of values beyond 255. Limiting input traffic will work only for queue sizes configured 255 cells or less. When you enter a value higher than 255, no input queue function is performed—all traffic is allowed through. [CSCdp25887]
The problems listed in Table 3 are fixed in Cisco IOS Release 12.1(4)DA.
| Caveat Number | Description |
|---|---|
CSCdp61780 | No matter what you set the configuration register or the bootvar to, rommon always boots up off bootflash. |
CSCdr58384 | The line card operational mode reports G.DMT when the operational mode is actually T1.413. |
CSCdr64678 | If you disable snmp-server traps alarms with the no snmp-server enable traps alarms command, you cannot reenable this feature with the snmp-server enable traps alarms command. |
CSCdr66665 | After you upgrade a DSLAM from Cisco IOS Release 12.0(x)DA to 12.1(x)DA, you might experience a problem that results from a change in some of the DMT defaults in the DSL profiles. The changes, which are listed in the "Changes to Default Values in DSL Profiles" section, affect the training mode, overhead framing, and DMT margin parameters. |
CSCdr91551 | The ITUC-1-8IDSL line card is not forwarding traffic after reload/reboot because the ISDN chipset is initializing indefinitely due to network clock synchronization. |
CSCdr91706 | Router hangs if the IOS HTTP service is enabled and you browse to an invalid URL. |
CSCdr94959 | NI-2/6160 allows the CPE to train with an incorrect mode. |
CSCds15858 | This unexpected behavior affects users who have a line card populated in slot 32. The soft VC addresses of ports atm32/1, atm32/2, and atm32/3 are identical to the ATM trunk ports atm0/1, atm0/2 and atm0/3 (in the case of an NI-2 with 2 subtend ports). This causes problems with the configuration information reporting in the wrong location, as well as errors with PNNI and possibly other protocols. The symptom occurs on the Cisco 6100, Cisco6130, Cisco 6160 and Cisco6260 running IOS Release 12.1(3)DA. |
The problems listed in Table 4 are fixed in Cisco IOS Release 12.1(3)DA.
| Caveat Number | Description |
|---|---|
CSCdm88409 | If you momentarily power down and then power up a CPE that is attached to a 4DMT-I line card, there is a small chance (roughly 1 in 100) that it will take an additional 45 seconds to complete training (as compared to typical training cycles). |
CSCdm64615 | If the 4DMT-I line card boot register is set for the card to reload application code, it reloads when the system reboots even if the load image is the same as the code already loaded on the card. (The reload takes about 2 minutes.) |
CSCdr66442 | A device that is connected to an ITUC-1-8IDSL IDSL interface and that requires a unified network clock might experience CRC errors, because the ITUC-1-8IDSL IDSL interface currently uses a local clock only. Support for using a network clock is planned for a future release. |
CSCdr04963 | The ITUC-1-8IDSL line card does not achieve theoretically possible downstream throughput for small frames (frames on the order of 64 bytes). The line card does achieve theoretically possible downstream rates for larger frames (frames on the order of 256 bytes and up). |
CSCdr67353 | The output of the show controllers command for a port that is configured for PPP encapsulation does not show the VPI/VCI that is configured between the NI-2 and the line card for that interface. Instead, it always shows VPI/VCI = 0/0, with all the SAR counters being 0. (The count for number of VCs configured is correct.) |
The problems listed in Table 5 are fixed in Cisco IOS Release 12.1(2)DA.
| Caveat Number | Description |
|---|---|
CSCdp05249 | When a hardware failure occurs on one or more of the ports on a 4DMT-2 line card, every other (otherwise healthy) port on the line card might be unable to train. Cisco strongly recommends that you replace or remove any line card with any defective ports. |
CSCdr56410 | When IP routing is enabled on an NI-2 DSLAM, the Ethernet port 0/0 does not come back up by itself after it experiences a problem. |
CSCdm89206 | Default ATM traffic descriptors cannot be deleted. When you attempt to delete them through the MIB, the MIB incorrectly indicates that the deletion is successful. |
The problems listed in Table 6 are fixed in Cisco IOS Release 12.1(1)DA1.
| Caveat Number | Description |
|---|---|
CSCdr43418 | Frames are delayed coming downstream from the NI-2. |
CSCdr53955 | ILMI does not come up between two subtended nodes. As a result, some traffic is dropped in error. |
The problems listed in Table 7 are fixed in Cisco IOS Release 12.1(1)DA.
| Caveat Number | Description |
|---|---|
CSCdp21747, CSCdp03335 | The CLI command for creating soft VPs, atm soft-vp, shows an invalid VPI range, and the MIB allows invalid values to be set. The full range of VPI values, 0 to 255, is now supported. |
CSCdp19413 | The dmtCodewordSize object does not allow a setting of automatic, as the CLI does. |
CSCdm92046 | The clear counter command does not consistently return all counter values to zero. This problem is not reproducible. |
CSCdp17666 | When you execute the shutdown command for a port, the port goes out of service, but Cisco IOS still lists the port's administrative status as UP. |
CSCdp00996 | Periodically, the system generates a serial management bus cyclic redundancy check (SMBCRC) error message such as this: %NI2-5-LC_NOTICE:Slot[15] SMBCRC (1 days, 3 hours, 37 minutes, 6
seconds)
These messages are informational only and do not affect performance. |
CSCdm66087 | DMT lines do not train to upstream bit rates that are multiples of 128 kbps. This applies to both standard training and quick training modes, but only in the upstream direction. If a line is configured with a maximum upstream bit rate that is a multiple of 128 kbps, the best upstream bit rate to which the line can train is 32 kbps less than the configured value. |
CSCdm91877 | When a port is set to use quick training mode, its symbols per codeword value is sometimes reported as "?" (a question mark). This value is displayed when you enter the show dsl interface atm command. |
CSCdp18533 | The MIB defines the ifAlias (subscriber ID) object as a 64-character field. SNMP truncates the field at 20 characters. This problem is not reproducible. |
CSCdp26405 | If the BITS plug is configured as the system's timing source, and the BITS clock source fails, an alarm is generated. (This behavior is correct.) However, the alarm is not cleared even after you remove the BITS plug from the valid list of clock sources. |
CSCdp63686 | The system does not allow you to remove VC/VP configuration parameters from the table, falsely claiming the parameters are in use by a connection. The command that fails is no atm connection-traffic-table-row. This problem is not reproducible. |
The software described in these release notes runs on several Cisco NI-2 DSLAM platforms, including the Cisco 6015, Cisco 6160, the Cisco 6260, and the Cisco 6130. The sections below list related documentation.
A complete list of all DSL hardware product related documentation is available on the World Wide Web at http://www.cisco.com/univercd/cc/td/doc/product/dsl_prod/index.htm.
These documents contain software information for all NI-2 DSLAMs:
In these Cisco ATM software manuals, look for information pertaining to the LightStream 1010, which uses the same software base as the NI-2 DSLAMs:
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, Are You Ready, ATM Director, Browse with Me, CCDA, CCDE, CCDP, CCIE, CCNA, CCNP, CCSI, CD-PAC, CiscoLink, the Cisco NetWorks logo, Cisco Powered Network logo, Cisco Systems Networking Academy, 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 Logo, iQ Readiness Scorecard, Kernel Proxy, MGX, Natural Network Viewer, Network Registrar, the Networkers logo, Packet, PIX, Point and Click Internetworking, Policy Builder, RateMUX, ReyMaster, ReyView, ScriptShare, Secure Script, Shop with Me, SlideCast, SMARTnet, SVX, TrafficDirector, TransPath, VlanDirector, Voice LAN, Wavelength Router, WebViewer, Workgroup Director, and Workgroup Stack are trademarks of Cisco Systems, Inc.; Changing the Way We Work, Live, Play, and Learn, 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 Press, Cisco Systems, Cisco Systems Capital, the Cisco Systems logo, Collision Free, Enterprise/Solver, EtherChannel, EtherSwitch, FastHub, FastLink, FastPAD, IOS, IP/TV, IPX, LightStream, LightSwitch, MICA, NetRanger, Post-Routing, Pre-Routing, Registrar, StrataView Plus, Stratm, SwitchProbe, TeleRouter, and VCO are registered trademarks of Cisco Systems, Inc. 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. (0010R)
Copyright © 2000, Cisco Systems, Inc.
All rights reserved.
Posted: Fri Mar 15 06:33:41 PST 2002
All contents are Copyright © 1992--2002 Cisco Systems, Inc. All rights reserved.
Important Notices and Privacy Statement.