Table of Contents

Release Notes for Cisco IOS Release 12.1(5)DA1 for Cisco DSLAMs with NI-2

Release Notes for Cisco IOS Release 12.1(5)DA1 for Cisco DSLAMs with NI-2

August 29, 2001

These release notes describe features and caveats in Cisco IOS Release 12.1(5)DA1 for the Cisco 6015, Cisco 6100, Cisco 6130, Cisco 6160, and Cisco 6260 digital subscriber line access multiplexers (DSLAMs).

Note   When you upgrade from Release 12.1(3)DA or earlier images on the NI-2 to Release 12.1(5)DA1, Cisco recommends that you upgrade the bootflash image on the NI-2 to the 12.1(5)DA1 dboot image. This is a result of a problem (CSCdr89374) in old bootflash images; this problem is fixed in Release 12.1(5)DA. This defect may cause the flash application image to fail to self-decompress successfully. See the "Upgrade the Bootflash Image on the NI-2 to the 12.1(5)DA1 dboot Image" section.

For pointers to more information about the Cisco 6015, Cisco 6130, Cisco 6160, Cisco 6260, and their software, refer to the "Related Documentation" section. To learn more about caveats, visit the Cisco web site—See the "Obtaining Documentation" section for details. Information about electronic documentation can be found in both the "Obtaining Documentation" section and in the "Documentation CD-ROM" section.

Contents

This document contains the following topics:

• System Requirements
  
  
• New and Changed Information
  
  
• Limitations and Restrictions
  
  
• Important Notes
  
  
• Caveats
  
  
• Related Documentation
  
  
• Obtaining Documentation
  
  
• Obtaining Technical Assistance
  
  

System Requirements

Cisco IOS Release 12.1(5)DA1 runs on these DSLAM systems:

• Cisco 6015
  
  
• Cisco 6100 with second-generation network interface (NI-2) module, Cisco 6100-specific system I/O card, and SC jumper card
  
  
• Cisco 6130 with second-generation network interface (NI-2) module and Cisco 6130-specific system I/O card
  
  
• Cisco 6160
  
  
• Cisco 6260
  
  

New and Changed Information

This section provides new and changed information for Cisco IOS releases.

New Features in Release 12.1(5)DA

This section describes new features in Cisco IOS Release 12.1(5)DA.

Fast Path Support for the Quad-Port Flexi ATU-C Line Cards

The fast path feature allows you to configure either the fast or the interleave DMT path via DSL profile configuration commands. Prior to Cisco IOS Release 12.1(5)DA, the operation of all supported DMT line cards was limited to use of the interleave path. Cisco IOS Release 12.1(5)DA supports the use of either the interleave or fast DMT paths with the 4xflexi-DMT line card provided that the CPE also supports fast path. The fast path provides improved latency characteristics for applications that cannot tolerate latency (for example, voice). Before migrating from interleave mode to fast path, you should determine whether the deployed CPEs offer support for the feature. The Cisco 600 series CPEs currently do not support fast path.

With fast path enabled, the 4xflexi-DMT line card now has downstream bit swapping enabled. This helps improve line quality on certain loops when running fast path.

New Flexi Line Card Support (DMT Line Encoding only) for the Cisco 6260

This release adds support for the quad-port flexi line card (ATUC-4-FLX-2) in the 6260 chassis when configured for DMT line encoding. The DMT features for the 4xflexi card in the Cisco 6260 are consistent with the feature set provided in the Cisco 6130 and Cisco 6160 products, and include autodetection of the CPE type and capabilities, compliance with 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. Please note that CAP line encoding is not supported on the Cisco 6260.

Proxy Element Supporting the Cisco DSL CPE Automated Configuration Solution

The Cisco DSL CPE automated configuration solution automates the configuration process for DSL customer premises equipment (CPEs). The proxy element is a name for the feature set embedded in IOS Release 12.1(5)DA to support the automated configuration solution on the Cisco 6000 series DSLAMs.

The Cisco DSL CPE automated configuration solution dramatically decreases the time and personnel resources required to bring service to a new DSL customer or to change or upgrade services. It allows the DSL provider to preprovision much of the CPE configuration. It eliminates the need for the DSL provider to visit the customer site. It provides a way to automatically deploy service changes or upgrades, and to automatically distribute new software and firmware images.

The DSL end user (the provider's customer) benefits by the shortened implementation time for DSL services, the plug and play style installation, and the automated distribution of new software images to CPE.

The Cisco DSL CPE automated configuration solution is one piece of a larger solution that represents Cisco's support of the OpenDSL initiative. The Cisco solution and the Open DSL initiative are based on the Simple Network Management Protocol (SNMP) and its information unit known as the management information base (MIB).

The proxy element performs the following functions in support of the automated configuration solution:

• Manages the configuration information base (CIB), which is a set of interrelated SNMP MIBs. The CIB stores all configuration information for all of the CPEs under the proxy element's control.
  
  
• Accepts input from the Cisco DSL CPE Manager (CDCM), which is a graphical user interface (GUI) tool for operators at the DSL provider site to add to and update information in the CIB.
  
  
• Handles requests from the CPEs for their configuration information. Every time a CPE in automated configuration mode reboots, it requests its configuration information.
  
  
• Downloads files to the CPEs. Examples of file types that can be accepted by CPEs are operating system software images, firmware images, and configuration files. The types of files that can be downloaded to a CPE depends on the CPE's model.
  
  
• Implements security and access control features in the SNMP version 3 (SNMPv3) to ensure that external users cannot modify the configuration information for a CPE.
  
  

New Features in Release 12.1(4)DA

This section describes new features in Cisco IOS Release 12.1(4)DA.

Cisco 6015 DSLAM

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   Cisco 6015 system support was available in Release 12.1(4)DA; however, at the date of Release 12.1(4)DA, the Cisco 6015 system was 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:

• 6015 chassis
  
  
• DS3+8xT1/E1 inverse multiplexing over ATM (IMA) NI-2
  
  
• DS3+8xT1 I/O module
  
  
• 8xE1 I/O module
  
  
• 6015 DC PEM
  
  
• 6015 Fan tray
  
  
• Up to six quad-port Flexi ATU-C line cards
  
  

The 6015 supports two configurations:

• DS3/T1 IMA
  
  
• E1 IMA
  
  

Both of these configurations are based on the DS3+8xT1/E1 IMA NI-2.

DS3+8xT1/E1 IMA NI-2

The DS3+8xT1/E1 IMA NI-2 supports two new features for Release 12.1(4)DA:

• T1/E1 IMA
  
  
• Trunk selection
  
  

The DS3+8xT1/E1 IMA NI-2 supports two modes of operation:

• DS3 trunk with 8xT1 IMA trunk/subtend
  
  
• 8xE1 IMA trunk/subtend
  
  

The mode of operation is determined based on the type of I/O module (DS3/T1 or E1) that is detected at system start-up.

T1/E1 Inverse Multiplexing over ATM

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

• Two links and one IMA group with six links
  
  
• Four IMA groups with two links in each
  
  
• Four links and two IMA groups with two links in each
  
  

  ---

  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.

Trunk Selection

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.

E3+2E3 I/O Module on the Cisco 6260

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.

MPLS VPN Mapping of RFC 1483 Routed Sessions

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:

• Cisco 6015 DSLAM with NI-2
  
  
• Cisco 6100 DSLAM with NI-2
  
  
• Cisco 6130 DSLAM with NI-2
  
  
• Cisco 6160 DSLAM with NI-2
  
  
• Cisco 6260 DSLAM with NI-2
  
  

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.

Quad-Port STU-C Line Card for the Cisco 6260

This release supports the quad-port symmetrical digital subscriber line (4xSDSL) transmission unit—central office (STU-C) line card on the Cisco 6260. The 4xSDSL conforms to 2B1Q line encoding. The line card is designed for use in a Direct Connect without a POTS splitter configuration. The Direct Connect without a POTS splitter configuration provisions one modem directly and is physically connected to one specific subscriber line through the main distribution frame (MDF) connections.

The 4xSDSL:

• Contains four SDSL modem connections.
  
  
• Transports ATM data at rates of up to 1168 kbps over a single twisted pair of copper wire.
  
  
• Converts SDSL modulation from the line into digital data streams to and from the network interface card.
  
  

The negotiated bit rate is the lower of the following rates:

• The provisioned bit rate set for the 4xSDSL in the management software
  
  
• The assigned bit rate at the customer premises equipment (CPE)
  
  

New Features in Release 12.1(3)DA

This section provides information about the latest features in Cisco IOS Release 12.1(3)DA.

ATUC-1-4DMT-ISDN Line Card

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.

New Features in Release 12.1(2)DA

This section provides information about the latest features in Cisco IOS Release 12.1(2)DA.

Eight-Port IDSL ITU-C Line Card

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.

New Features in Release 12.1(1)DA1

This section provides information about the latest features in Cisco IOS Release 12.1(1)DA1.

Software Supports Alcatel DSL Chip Set-Based CPE

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:

• Performance characterization between the ATUC-1-4DMT (ADI-based) line card and Alcatel-based CPE has been limited to the Alcatel 2.5.8 version of firmware. Other firmware revisions may perform differently.
  
  
• The ATUC-1-4DMT (ADI-based) line card performance might be limited when deployed on very short loops (less than 3 thousand feet). This affects most nonADI based CPEs including the Cisco 827.
  
  
• Upstream performance is limited when connecting the ATUC-1-4DMT (ADI-based) line card to Alcatel-based CPE.
  
  

Quad-Port DMT Card Supports G.lite and G.DMT

The ATUC-1-4DMT2 line card now supports the G.992.1 (G.DMT) and G.992.2 (G.lite) standards.

New Features in Release 12.1(1)DA

This section provides information about the latest features in Cisco IOS Release 12.1(1)DA.

Release 12.1(1)DA Supports the Cisco 6160 DSLAM

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.

Availability and Compliance

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.

Advanced Services ATM Architecture

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.

Scalability with Fair-Service Subtending

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.

Standards-Compliant ADSL Support

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.

Switched Virtual Connections

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.

Soft PVC Provisioning

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.

Life-line POTS Splitter Support

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

New Flexi and SDSL Line Cards

Two new quad-port line cards are introduced in this release for use with the Cisco 6160 and Cisco 6130:

• The flexi line card can be configured for either CAP or DMT line encoding. CAP features are consistent with NI-1 Release 3.0, with configurable line rates up to 7168 kbps downstream and 1088 kbps upstream. DMT features include autodetection of the CPE type and capabilities, compliance with 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.
  
  
• The symmetrical digital subscriber line (SDSL) line card supports configurable line rates up to 1168 kbps in both directions. The SDSL card uses 2B1Q line encoding.
  
  

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.

New DMT Performance MIB Support

This release supports 96 buckets of 15-minute interval, previous and current 1-day interval DMT performance statistics.

Support for New VPI/VCI Combinations

To enable migration from NI-1 to NI-2 without reconfiguring CPEs in the field, in Release 12.1(1)DA the NI-2 DSLAMs support both VPI=1, VCI=1 and VPI=1, VCI=0 configurations on subscriber ports.

Changes to Default Values in DSL Profiles

The following default values have changed:

New Microcode for ATUC-1-4DMT Line Card

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.

Limitations and Restrictions

This section describes the limitations and restrictions for Cisco IOS DSLAM releases.

Cisco IOS Release 12.1(5)DA

There are no restrictions that specifically apply just to IOS Release 12.1(5)DA. Other restrictions that apply to Release 12.1(5)DA are described in the "Cisco IOS Release 12.1(4)DA" section.

Cisco IOS Release 12.1(4)DA

This section describes the limitations and restrictions for Cisco IOS Release 12.1(4)DA.

Restrictions to MPLS VPN Mapping of RFC 1483 Routed Sessions

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.

Number of Configurable MPLS VPNs Limited to 50

Each DSLAM can support up to 50 MPLS VPNs.

Integrated Routing and Bridging Not Supported

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.

VPN Interfaces Restricted to Trunk Interfaces

Do not configure subtended interfaces for MPLS VPN services. Only trunk interfaces support MPLS VPN mapping of RFC 1483 routed sessions.

MPLS ATM-Label Switch Router Functionality Not Supported

DSLAMs are not meant for use as MPLS ATM-Label Switch Routers (ATM-LSRs). When designing your network, keep in mind that DSLAMs act only as Label Edge Routers (LER).

Performance Restrictions for MPLS VPN Traffic

MPLS VPN-enabled interfaces do not perform as well as switched VCs. Please take this into consideration when deploying MPLS VPNs in your networks.

Restricted Layer 3 Services

The following Layer 3 services are not supported in Cisco IOS Release 12.1(4)DA:

• IP Quality of Service
  
  
• IP Queueing
  
  
• IP Multicast
  
  

Restricted MPLS Features

The following are MPLS-related features that are not a part of the MPLS VPN mapping of RFC 1483 routed sessions feature:

• MPLS Traffic Engineering
  
  
• MPLS Multicast
  
  

DSL Interface Limitations

In IP DSL switches, each DSL interface can support multiple Permanent Virtual Circuits (PVCs), but only one routed MPLS VC.

Configuration of MPLS VPN Mapping of RFC 1483 Routed Sessions not Supported by Cisco DSL Manager (CDM)

CDM users can provision switched VCs, but CDM does not support configuring routed termination of RFC 1483 sessions.

MPLS VPN Mapping of RFC 1483 Routed Sessions not Supported on the Eight-Port IDSL ITU-C Line Card

Routed termination of IDSL connections is not supported in Cisco IOS Release 12.1(4)DA.

Cisco IOS Release 12.1(3)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.

Cisco IOS Release 12.1(2)DA

The following restrictions apply to Release 12.1(2)DA:

If you need to fall back to an earlier release, note the following restrictions:

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.

Cisco IOS Release 12.1(1)DA1

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.

Cisco IOS Release 12.1(1)DA

The following restrictions apply to this release:

If you need to fall back to an earlier release, note the following restrictions:

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.

Important Notes

This section provides important information about Cisco IOS DSLAM releases.

Caveat CSCds04747 and TCP Initial Sequence Numbers

Cisco IOS software contains a flaw that permits the successful prediction of transmission control protocol (TCP) initial sequence numbers.

This vulnerability is present in all released versions of Cisco IOS software running on Cisco routers and switches. It only affects the security of TCP connections that originate or terminate on the affected Cisco device itself; it does not apply to TCP traffic forwarded through the affected device in transit between two other hosts.

To remove the vulnerability, Cisco is offering free software upgrades for all affected platforms. The defect is described in DDTS record CSCds04747.

Workarounds are available that limit or deny successful exploitation of the vulnerability by filtering traffic containing forged IP source addresses at the perimeter of a network or directly on individual devices.

This notice will be posted at http://www.cisco.com/warp/public/707/ios-tcp-isn-random-pub.shtml.

CSCds32217, CSCdr61016, and Multiple SNMP Community String Vulnerabilities

Multiple Cisco IOS software and CatOS software releases contain several independent but related vulnerabilities involving the unexpected creation and exposure of SNMP community strings. These vulnerabilities can be exploited to permit the unauthorized viewing or modification of affected devices.

To remove the vulnerabilities, Cisco is offering free software upgrades for all affected platforms. The defects are documented in DDTS records CSCds32217, CSCds16384, CSCds19674, CSCdr59314, CSCdr61016, and CSCds49183.

In addition to specific workarounds for each vulnerability, affected systems can be protected by preventing SNMP access.

This notice will be posted at http://www.cisco.com/warp/public/707/ios-snmp-community-vulns-pub.shtml.

Upgrade the Bootflash Image on the NI-2 to the 12.1(5)DA1 dboot Image

When you upgrade from Release 12.1(3)DA or earlier images on the NI-2 to Release 12.1(5)DA1, Cisco recommends that you upgrade the bootflash image on the NI-2 to the 12.1(5)DA1 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:

DSLAM>enable

Password: <password>
DSLAM#

DSLAM# delete bootflash:[file name]

DSLAM# squeeze bootflash

DSLAM# copy tftp://[server name] 
/[directory]/ni2-dboot-mz.121-5.da1 
bootflash

DSLAM# show version

DSLAM# configure terminal

DSLAM(config)# config-register 0

DSLAM(config)# exit

DSLAM# copy running-config 
startup-config

DSLAM# reload

rommon> set

rommon > unset BOOTLDR

rommon > sync

rommon > b

DSLAM# configure terminal

DSLAM(config)# config-register value

DSLAM(config)# exit

IDSL Linecard Clocking Problem Fixed in Release 12.1(4)DA

The following problem is fixed in the IOS 12.1(4)DA release. Upgrade to 12.1(4)DA 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.

Soft PVC Address Changes Upon Upgrade to 12.1(3)DA or 12.1(4)DA

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:

• Reconfigure the soft PVCs associated with all interfaces.
  
  
• Assign a (nondefault) address to the interfaces.
  
  

Configuring Cisco Routers for Use with IDSL

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.

Upgrading from Cisco IOS 12.0(x)DA to 12.1(1)DA, 12.1(2)DA, or 12.1(3)DA

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 start-up 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 start-up 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 start-up 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]

Assigning VPI Values to Shaped VP Tunnels

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.

Installing Multiple Cisco 6160 Chassis in an Equipment Rack

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.

Synchronizing the Management Database

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.

Console Logging

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.

Caveats

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.

Open Caveats—Release 12.1(5)DA

The caveats in this section apply only to IOS Release 12.1(5)DA. Other open caveats that apply to this Release 12.1(5)DA are described in the "Open CaveatsRelease 12.1(4)DA" section, the "Open CaveatsRelease 12.1(3)DA" section, the"Open CaveatsRelease 12.1(2)DA" section, "Open CaveatsRelease 12.1(1)DA1" section, and the "Open CaveatsRelease 12.1(1)DA" section.

Flexi Line Card Problems

FastPath Working on G.lite

With the 4x flexi-DMT line card configured, the line is able to train up in fast path when in G.lite mode. This was observed with CPEs capable of G.Lite and fast path.

Workaround: Do not enable fast path when in G.Lite operating mode. [CSCds52496]

Fastpath with Trellis off Reports Up Margin of -63 dB

With the 4xflexi-DTM line card configured, the DSLAM reports the upstream margin of -63 dB or 63 dB (depending on the DSP firmware version) when operating with Alcatel based CPEs (tested with Efficient 5260 and 5262).

Workaround: Enable trellis encoding when operating with Alcatel based CPEs. [CSCds54602]

BERT Test Interrupts Upstream Traffic on the Other Card Ports

With the 4xflexi line card configured, other ports on the same line card are unable to pass upstream traffic when one of the ports on the line card is running a BERT test. Once the BERT test completes, the upstream traffic on other ports resumes.

Workaround: Do not initiate the BERT test if there is traffic running on other ports on the same line card. [CSCds73901]

Downstream Frame Loss When Check-bytes Less Than 6 with 5262/Interleave

With the 4xflexi-DMT line card configured for interleave path operation and an FEC value of less than 6, a number of Uncorrected Superframes and thus lost data frames (in the order of 1 in 10,000) in the downstream direction can occur on certain loops. This was observed with line card dsp image version K.29 while connected to an Efficient 5262 CPE.

Workaround: Set an FEC value of 6 or greater.[CSCds76533]

MIB Problems

adslAturCurrOutputPwr Returns Incorrect Value on CAP Cards

Setting adslAtuc/AturCurrOutputPwr in the ADSL-LINE-MIB returns an incorrect value for short loops ( < 2000 feet ). When Transmit Power reports a negative value, the SNMP query to these variables returns an incorrect value in the response.

Workaround: Use CLI. [CSCds48052]

adslAtucCurrStatus Returns Incorrect Value for CAP and DMT

Setting adslAtucCurrStatus returns an incorrect status for CAP and DMT.

Workaround: Use CLI. [CSCds80863]

adslAturCurrStatus Returns Incorrect Value for DMT

Setting adslAturCurrStatus returns an incorrect status for DMT line cards.

Workaround: Use CLI. [CSCds81122]

cAdslAtuc/AturCapCurrRxGain Returns Invalid Values

Setting cAdslAtuc/AturCapCurrRxGain in the CISCO-ADSL-CAP-LINE-MIB returns an incorrect value for short loops ( < 2000 feet). When Receiver Gain reports a negative value, the SNMP query to these variables returns an incorrect value in the response.

Workaround: Use CLI. [CSCds48063]

Cannot Get or Set Filter in CISCO-ATM-ACCESS-LIST-MIB

The ATM filter created from CLI does not show up in the MIB filter tables. An ATM filter cannot be created from MIB.

Workaround: Use CLI. [CSCds68212]

Creation of snmpNotifyFilterProfileTable Incorrect, Can Cause Reboot

The snmpNotifyFilterProfileTable in snmp-notification-mib cannot be properly created.

Workaround: None. [CSCds70225]

ifIndex in pnniIfTable Mapped to Wrong ATM Layer

Entries for the trunk and subtend ports in the pnniIfTable are mapped to the wrong layer.

Workaround: None. [CSCds80219]

Inconsistent ATM Perf Data Reporting Breaks CDM Feature

ATM performance data for DSL and SONET/DS3 interfaces is not consistently reported. ATM performance data for SONET/DS3 interfaces is reported in the physical layer.

Workaround: Query the physical layer of the SONET/DS3 interfaces to get ATM data.[CSCds59103]

Reboots When Setting ceAlarmHistTableSize CISCO-ENTITY-ALARM-MIB

Setting ceAlarmHistTableSize returns ERROR and reboots system. SNMP set for ceAlarmHistTableSize returns ERROR and when ceAlarmHistTableSize is reset from 0, the system reboots.

Workaround: None. [CSCds61302]

Removing Preprovisioned Slot with PVCs Causes Snmp Table Corruption

The VCCrossConnectTable in the ATM-MIB does not list all entries after a slot is deleted. This occurs when a slot has been preprovisioned via the slot command and then removed via the no slot command.

Workaround: Use CLI to view VC cross connections or reload the system and the table will be corrected.[CSCds74434]

SNMP Walk Loops in CISCO-ATM-SIG-DIAG-MIB

SNMP walk loops in csfRecordTable (CISCO-ATM-SIG-DIAG-MIB) conditions.

Workaround: None. [CSCds64436]

Sonetpath(50) Missing from ifTable

The ifType with a value sonetPath(50) is missing from the ifTable. The ifIndex of MIB variables in sonetPathCurrent and sonetPathInterval tables are mapped to the sonet(39) ifType. The ifIndex of these variables should map to a sonetPath(50) ifType, which is not present in the ifTable.

Workaround: None. [CSCds59504]

Miscellaneous Problems

F4 and F5 OAM Cells from CPEs are Dropped

The F4 and F5 OAM atm cells arriving on modem interfaces are ignored. The OAM related activities do not take place for modem interfaces because the F4 and F5 OAM cells are ignored.

Workaround: None. [CSCds77253]

SNMP set cmd w/ string param (IOS CLI) Causes System Failure

Executing an SNMP Set/Inform request with string or ip address parameter through IOS CLI causes an unexpected DSLAM reload. For example:

snmp set v3 ip xxx.xxx.xxx.xxx community pef context pef oid cdcpCibOwner.0 string pef
 

Other parameters, for example, integer work fine.

Workaround: Use other tools to set objects that require a string or ip address input. [CSCds81489]

MPLS Problems

NI-2 Reload under Destructive VPN Routes Update Test

Running a destructive test by sending more than 30,000 VPN routes across the MPLS network causes the NI-2 to reload.

Workaround: Configure the maximum routes for each VPN to prevent the CE devices or remote PE routers from sending the VPN routes more than it should. [CSCds51409]

Open Caveats—Release 12.1(4)DA

The caveats in this section apply only to IOS Release 12.1(4)DA. Other open caveats that apply to 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.

IMA Problems

E1 IMA Group Bandwidth is Limited to Six Links

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 May Occur on Subscriber Ports If Trunk is Down

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:

• Shutdown the trunk IMA group.
  
  
• Bring the trunk IMA group up (by troubleshooting).
  
  
• Reassign the trunk to another interface (changes network topology).
  
  

MPLS VPN Mapping of RFC 1483 Routed Sessions

Attempting to Create a Circuit on VCI 3 or 4 is Allowed by the CLI

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]

Changing Line Coding or Line Card Type Causes Duplicate VPN References in show ip vrf Output

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 a Large Number of Subinterfaces Causes Service Loss

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]

Configuring IP MTU or Physical MTU Size has no Effect on Fragmentation

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]

CRC Errors Appear on CPE DSL Modems if IP DSL Switch Is Running NI-2 Rev02 SAR

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:

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]

debug atm error Command Generates Invalid Error Messages

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 Interface Resets Under Heavy Stress

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 a DSLAM with lower CPU usage rates. [CSCds23638]

Erroneous debug atm Error Message When Creating a PVC or MPLS-Switched Interface

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]

Interface Site-of-Origin Tagging is Not Working

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]

IP DSL Switch Accepts Invalid ATM Syntax on DSL Interfaces

The ATM command syntax atm pvc vpi vci is not parsed correctly by the DSLAM. [CSCds05174]

Workaround: Use the following syntax:

atm pvc vpi vci interface atm [slot/port] vpi vci

Maximum Number of Interior Gateway Protocol (IGP) Routes Supported on the IP DSL Switch is Limited to 3500

The maximum number of Interior Gateway Protocol (IGP) routes on the DSLAM is limited to 3500.

Workaround: Currently, there is no workaround. [CSCdr89959]

Outbound Access Lists Do Not Work

Outbound access- lists on uplink and CE interfaces are ignored.

Workaround: Currently, there is no workaround. [CSCds01820]

Packet Sizes of Less Than 512 Bytes Result in Reduced Aggregate Throughput in the NI-2

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]

Sending More than 12,500 RIP Routes in a Single VPN Causes High CPU Usage

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 IP Routing Tables Break After Line Coding Change

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]

System Generates a MALLOCFAIL Error if You Disable Cisco Express Forwarding While Traffic is Running

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]

System Generates an Incorrect Error Message When Attempting to Remove VP-tunnel

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]

System Generates Unknown Protocol, VRF Error Message Reference During NI-2 Reload

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]

Open Caveats—Release 12.1(3)DA

The caveats in this section apply only to IOS Release 12.1(3)DA. Other open caveats that apply to 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.

ATUC-1-4DMT-I Line Card Problems

This section describes problems with the ATUC-1-4DMT-I line card.

With Trellis Enabled, Errored Seconds are High

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]

Some Trains in Quick Mode will have High Errored Seconds

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]

Reported Margins do not Match Selected Margins

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:

• Training mode
  
  
• Framing mode
  
  
• Interleaving delay
  
  
• Trellis coding
  
  
• Number of FEC checkbytes
  
  

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:

IDSL Line Card Problems

This section describes problems with the IDSL line card.

Clocking Problem

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.

Frame Relay Configuration Problems

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:

• A combination of four Frame- Relay PVCs and soft PVCs are configured on a given IDSL interface.
  
  
• At least one of the PVCs is a soft PVC.
  
  
• The dlci specified in the command no frame-relay soft-vc dlci is not configured.
  
  

Workaround: Ensure that a valid dlci is specified when you delete a frame-relay soft-vc. [CSCds06327]

Miscellaneous

The following are miscellaneous problems with this release.

• The IDSL-associated atm-p interface input counters are not being updated. The per-VC counters are updating properly, but interface-level counters are not.
  
  

Workaround: Use the following CLI commands that display counters:

• show interface idsl card/port
  
  
• show atm vc traffic interface atm-p card/port [CSCdr90732]
  
  

• Occasionally, an SNMP query of the cIdslIturPerfPrev1DayMoniSecs object in the CISCO-IDSL-LINE-MIB results in a negative value. This condition occurs when IDSL ports are operationally down for several hours before the physical link is connected and the port becomes operationally up. There is currently no workaround for this problem. [CSCdr92983]
  
  

Loopback and Test Problems

The following are loopback and test problems with this release.

• When you configure an interface for loopback diagnostic operation and this configuration becomes part of the startup-config, the interface might initialize in the down state after DSLAM reload/reboot.
  
  

Workaround: Enter the clear interface idsl card/port command to reinitialize the interface. [CSCds01533]

• On rare occasions, if you issue the remote loopback command, the interface goes down and remains down. You can verify this failure mode by issuing the show controllers IDSL slot/port command and confirming that the C/I state is not 0xF3.
  
  

Workaround: Remove and reissue the loopback remote command. [CSCdr62772]

• On rare occasions, an ITUC-1-8IDSL BERT test will report bit errors and multiple sync losses.
  
  

Workaround: Remove and reissue the loopback remote command. [CSCdr63116]

ATM Traffic Shaping and Policing not Functioning

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:

• Shaping and policing do not work if the ATM SCR is less than 3 kbps. The behavior is that all traffic is passed and no cells are dropped or tagged.
  
  
• Shaping and policing at higher rates does function, but the rate to which shaping and policing occurs might not match the configured rate.
  
  

There are no workarounds to the above problems.[CSCdr70582]

Two NI-2s have the same ATM Address

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. [CSCds26889]

Workaround:

Open Caveats—Release 12.1(2)DA

The caveats in this section apply only to IOS Release 12.1(2)DA. Other open caveats that apply to Release 12.1(2)DA are described in the "Open CaveatsRelease 12.1(1)DA1" section, and in the "Open CaveatsRelease 12.1(1)DA" section.

IDSL Line Card Problems

Frame Relay Configuration Problems

• The NI-2 cannot terminate IDSL FRF.8 service transparent PVCs. The system accepts commands of the form frame-relay pvc... service transparent interface ATM0/0... encap aal5mux ip, but the PVC is not properly terminated. Only service translation PVCs can be terminated by the NI-2 with an ATM encapsulation of aal5snap. Note that service transparent PVCs can be terminated via any physical ATM interface, however. [CSCdr16342]
  
  
• If you issue the shutdown command on a Cisco 6160 IDSL interface that is attached to a Motorola Vanguard 65, and Frame Relay encapsulation is configured on both devices, a subsequent no shutdown command might not bring the Motorola Vanguard 65 interface back up. This problem does not occur if PPP encapsulation is configured.
  
  

Workaround: Power cycle the Motorola Vanguard 65. [CSCdr32145]

• The default value for the optional efci-bit parameter of the IDSL interface configuration command frame-relay soft-vc... is incorrect. The default should be 0, not map-fecn.
  
  

Workaround: Explicitly specify the desired setting when you configure Frame Relay soft VCs. [CSCdr62008]

• IDL 144 kbps mode is currently disabled for IDSL interfaces. It will be enabled in a future release. At that time, the command dsl profile idsl bitrate 144 idl will be enabled. Note that 144 kbps non-IDL mode is supported. [CSCdp63832]
  
  
• If you configure Frame Relay encapsulation on an IDSL interface, the interface does not pass Appletalk traffic. There is no workaround. [CSCdp70130]
  
  

Interface State Problem

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]

Status Display Problems

• If you specify the UPC pass optional parameter in the frame-relay soft-vc... command, the parameter appears in the running configuration, even though this is the default. This is a cosmetic defect only, and does not affect operational behavior in any way. [CSCdr36372]
  
  
• The show dsl interface idsl slot/port command displays excessive HDLC layer performance statistics errors if the line interface cable to the CPE is pulled. This is an aspect of the implementation and does not indicate negative performance. [CSCdr43144]
  
  

Loopback and Testing Problems

• If you issue the no loopback command on an ITUC-1-8IDSL interface on which a loopback command has not previously been issued, the interface goes down and back up. This causes a momentary interruption of service for the affected interface. [CSCdr35443]
  
  
• A Cabletron Flowpoint 144F-16 IDSL router cannot be placed into remote loopback when it is operating in 144kbps mode when you issue the loopback remote command on the Cisco 6160. You can put the Cabletron Flowpoint 144-16 IDSL router into remote loopback if it is operating at 64kbps or 128kbps. There is no workaround. [CSCdr58260]
  
  
• On rare occasions, if you issue the loopback remote command and then issue the no loopback remote command, the interface goes down and remains down. You can verify this failure mode by issuing the show controllers idsl slot/port command and confirming that the "C/I" state is not "0xF3".
  
  

Workaround: Disable and re-enable the interface using the shutdown command followed by the no shutdown command. [CSCdr60773]

• Bit error rate testing (BERT) runs continuously if the Cisco 6160 is reloaded while BERT is in progress.
  
  

Workaround: To abort BERT before reloading the Cisco 6160, use the dsl test idsl slot/port abort command. [CSCdr62092]

• ITUC-1-8IDSL interfaces that are configured with Frame Relay encapsulation and LMI experience periodic interface state transitions if you issue the loopback remote command. This results in the periodic printing of LINK, LINEPROTO and possibly alarm transition messages to the console until you disable the loopback using the no loopback remote command. The interface transitions and the resulting console messages do not affect BERT tests and are completely benign. [CSCdr62656]
  
  
• On rare occasions, if you issue the loopback remote command, the interface goes down and remains down. You can verify this failure mode by issuing the show controllers idsl slot/port command and confirming that the "C/I" state is not "0xF3".
  
  

Workaround: Use the no loopback remote command to turn the remote loopback off, then use the loopback remote command to turn it on again. [CSCdr62772]

• On rare occasions, an ITUC-1-8IDSL bit error rate test (BERT) reports bit errors and multiple sync losses.
  
  

Workaround: Use the no loopback remote command to turn the remote loopback off, then use the loopback remote command to turn it on again. [CSCdr63116]

SDSL Line Card Problem

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]

Flexi Line Card Problems

Trellis Coding Disabled Can Cause Errors with Flexi-DMT Cards

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.

Interleave Delay of Zero Can Cause Errors with Flexi-DMT Cards

We recommend that the interleave configuration be set to 1000 microseconds or greater for optimal reach performance. [CSCdr27700]

Line Card Alarms Not Cleared When a Flexi Card Changes Type

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]

Incorrect Margin Value Reported for Some Cisco 678 Connections

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.

Open Caveats—Release 12.1(1)DA1

The caveats in this section apply only to IOS Release 12.1(1)DA1. Other open caveats that apply to Release 12.1(1)DA1 are described in the "Open CaveatsRelease 12.1(1)DA" section.

Ethernet Port Cannot Recover Itself

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:

• Use IP host-routing to establish connectivity over the Ethernet interface.
  
  
• Turn off keep-alives on the Ethernet interface. If you do this, however, the system does not tell you when the Ethernet line goes down. [CSCdr56410]
  
  

NI-2 Cannot Recover if Bootflash Image Is Deleted

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]

Open Caveats—Release 12.1(1)DA

The caveats in this section apply only to IOS Release 12.1(1)DA.

Incorrect Margin Value Reported for Some Cisco 678 Connections

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.

Maximum VCI Bits Value on Subscriber Ports Can Exceed 8

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]

DMT Ports Do Not Train Under Some FEC Check Bytes Settings

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 port is configured for quick training mode
  
  
• FEC check bytes per codeword for the downstream direction is configured for 0, 4, 8, 12, or 16.
  
  
• The port trains below the threshold bit rate for the configured FEC check bytes per codeword (as listed in the table below).
  
  

The threshold bit rates at which this problem appears for each check byte per codeword setting are as follows:

Workarounds: Do one of the following:

• Use the dmt training-mode command to configure the port for quick training mode.
  
  
• Avoid setting the port to 2, 6, 10, or 14 check bytes per codeword in the downstream direction if it is possible that the line will train at or above 7616 Kbps. In this case, use settings of 0, 4, 8, 12, or 16 check bytes per codeword instead. Use the dmt check-bytes command to configure this parameter.
  
  
• Use the dmt bitrate command to configure the maximum downstream bit rate below the threshold bit rates listed above, depending on the configured number of check bytes per codeword. [CSCdr16409]
  
  

Failed Ports Bring Down Healthy Ports on Same Line Card

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]

VCs Are Not Released When a Flexi Card Changes Type

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:

• Delete the VCs on the interfaces either before or after you change the card type, and recreate the VCs after the card type is changed.
  
  
• Use new sets of VCs for new card types. [CSCdr06985]
  
  

Problems Affecting Management Systems

These problems affect SNMP-based management systems, including the Cisco DSL Manager (CDM). You can avoid these problems by using the CLI.

• You cannot set or change the subtend node ID using SNMP.
  
  

Workaround: Use the CLI command subtend-id node# to set or change the subtend ID. [CSCdm93577]

• 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. [CSCdm89206]
  
  

Problems Affecting the ATUC-1-4DMT2 Line Card

Training Problems

• DMT lines sometimes train at 8096 kbps (downstream), although the maximum configurable bit rate is 8032 kbps. This occurs with Cisco 676 CPEs and might also occur with other vendors' Issue 1 equipment. [CSCdm66998]
  
  
• DMT ports sometimes attempt to train (port LEDs blink) when no CPE is connected at the far end of the subscriber loop. This occurs when a neighboring port that is connected to CPE is training on a very short loop (less than 1000 feet). [CSCdm85326]
  
  
• There may be no benefit in lowering configured end-to-end signal-to-noise ratio (SNR) margins below certain effective minimum values. Although the system allows margins to be configured below these effective minimums, the resulting bit rates and actual end-to-end margins might be the same as those realized when the margins are configured at the effective minimum values.
  
  

The effective minimum values depend upon

• Training mode (standard or quick)
  
  
• Bit rates to which the line trains
  
  
• Whether interleaving is used
  
  

For the standard training mode, the effective minimum end-to-end margin is 1 to 3 dB. For the quick training mode, the effective minimum end-to-end margin is 4 to 6 dB. The effective margins might be better (that is, at the lower ends of the specified ranges) if interleaving is turned off and/or the bit rates fall between 6 Mbps and 3 Mbps. [CSCdm89068]

Trellis Coding Can Cause Errors

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]

Some Combinations of Framing Mode and Bit Rate Cause Data Corruption

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:

Workaround: To avoid this data corruption problem, use these combinations of settings for the lower data rates:

[CSCdm66085]

Decreasing Interleaving Delay Increases Errored Seconds

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:

• Use the dmt interleaving-delay command to increase the interleaving delay to 16 msec.
  
  
• Use the dmt bitrate command to lower the maximum bit rates (both upstream and downstream, if necessary) to a lower rate than the one at which the errors were observed. [CSCdm82076]
  
  

Check Bytes Are Not Reported Correctly

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]

Interleaving Delay Is Not Reported Correctly

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]

Bitswap Command Is Not Functional

The dmt bitswap margin command has no effect in this release. Bit swapping is always disabled. [CSCdm80069]

Virtual Path Deconfiguration Problem

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]

OAM RDI Cannot Be Enabled

When you create a PVC for the first time, and the OAM RDI Mode is set to enable, this mode is reset to disable during the cross-connect phase of creation. This is related to the CDM issue CSCdp08324.

Workaround: Create the PVC, and, once created, use the Edit tab in the PVC Configuration Manager dialog to change the OAM RDI Mode for this PVC to enable. [CSCdp74861]

ATM Input Queue is Limited to 255 Cells

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]

Resolved Caveats—Release 12.1(5)DA

The problems listed in Table 4 are fixed in Cisco IOS Release 12.1(5)DA.

Resolved Caveats—Release 12.1(4)DA

The problems listed in Table 4 are fixed in Cisco IOS Release 12.1(4)DA.

Resolved Caveats—Release 12.1(3)DA

The problems listed in Table 5 are fixed in Cisco IOS Release 12.1(3)DA.

Resolved Caveats—Release 12.1(2)DA

The problems listed in Table 6 are fixed in Cisco IOS Release 12.1(2)DA.

Resolved Caveats—Release 12.1(1)DA1

The problems listed in Table 7 are fixed in Cisco IOS Release 12.1(1)DA1.

Resolved Caveats—Release 12.1(1)DA

The problems listed in Table 8 are fixed in Cisco IOS Release 12.1(1)DA.

%NI2-5-LC_NOTICE:Slot[15] SMBCRC (1 days, 3 hours, 37 minutes, 6 
seconds)
 

Related Documentation

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.

Hardware 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.

Software Documentation

These documents contain software information for all NI-2 DSLAMs:

• Configuration Guide for Cisco DSLAMs with NI-2
  
  
• Command Reference for Cisco DSLAMs with NI-2
  
  
• Release notes for Cisco IOS Release 12.1(5)DA1 or greater
  
  

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:

• ATM Switch Router Software Configuration Guide
  
  
• ATM Switch Router Command Reference Guide
  
  
• Guide to ATM Technology
  
  

See the following documents for information related to the Cisco DSL CPE automated configuration solution, the proxy element's role in this solution, and proxy element configuration and deployment information.

• Proxy Element Supporting the Cisco DSL CPE Automated Configuration Solution, a feature module in the Cisco IOS 12.1.5(DA) release train
  
  
• Cisco DSL CPE Automated Configuration Solution Guide
  
  
• Release Notes for Cisco DSL CPE Automated Configuration Solution
  
  
• Cisco DSL CPE Manager User Guide
  
  

Obtaining Documentation

The following sections provide sources for obtaining documentation from Cisco Systems.

World Wide Web

You can access the most current Cisco documentation on the World Wide Web at the following sites:

• http://www.cisco.com
  
  
• http://www-china.cisco.com
  
  
• http://www-europe.cisco.com
  
  

Documentation CD-ROM

Cisco documentation and additional literature are available in a CD-ROM package, which ships with your product. The Documentation CD-ROM is updated monthly and may be more current than printed documentation. The CD-ROM package is available as a single unit or as an annual subscription.

Ordering Documentation

Cisco documentation is available in the following ways:

• Registered Cisco Direct Customers can order Cisco Product documentation from the Networking Products MarketPlace:
  
  

http://www.cisco.com/public/ordsum.html

• Registered Cisco.com users can order the Documentation CD-ROM through the online Subscription Store:
  
  

http://www.cisco.com/go/subscription

• Nonregistered CCO users can order documentation through a local account representative by calling Cisco corporate headquarters (California, USA) at 408 526-7208 or, in North America, by calling 800 553-NETS(6387).
  
  

Documentation Feedback

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

Obtaining Technical Assistance

Cisco provides Cisco.com as a starting point for all technical assistance. Customers and partners can obtain documentation, troubleshooting tips, and sample configurations from online tools. For Cisco.com registered users, additional troubleshooting tools are available from the TAC website.

Cisco.com

Cisco.com 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.

Cisco.com provides a broad range of features and services to help customers and partners streamline business processes and improve productivity. Through Cisco.com, you can find information about Cisco and our networking solutions, services, and programs. In addition, you can resolve technical issues with online technical support, 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 Cisco.com to obtain additional personalized information and services. Registered users can order products, check on the status of an order, access technical support, and view benefits specific to their relationships with Cisco.

To access Cisco.com, go to the following website:

http://www.cisco.com

Technical Assistance Center

The Cisco TAC website is available to all customers who need technical assistance with a Cisco product or technology that is under warranty or covered by a maintenance contract.

Contacting TAC by Using the Cisco TAC Website

If you have a priority level 3 (P3) or priority level 4 (P4) problem, contact TAC by going to the TAC website:

http://www.cisco.com/tac

P3 and P4 level problems are defined as follows:

• P3—Your network performance is degraded. Network functionality is noticeably impaired, but most business operations continue.
  
  
• P4—You need information or assistance on Cisco product capabilities, product installation, or basic product configuration.
  
  

In each of the above cases, use the Cisco TAC website to quickly find answers to your questions.

To register for Cisco.com, go to the following website:

http://www.cisco.com/register/

If you cannot resolve your technical issue by using the TAC online resources, Cisco.com registered users can open a case online by using the TAC Case Open tool at the following website:

http://www.cisco.com/tac/caseopen

Contacting TAC by Telephone

If you have a priority level 1(P1) or priority level 2 (P2) problem, contact TAC by telephone and immediately open a case. To obtain a directory of toll-free numbers for your country, go to the following website:

http://www.cisco.com/warp/public/687/Directory/DirTAC.shtml

P1 and P2 level problems are defined as follows:

• P1—Your production network is down, causing a critical impact to business operations if service is not restored quickly. No workaround is available.
  
  
• P2—Your production network is severely degraded, affecting significant aspects of your business operations. No workaround is available.