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

These release notes describe features and caveats in Cisco IOSRelease 12.2(5)DA1 for the Cisco 6015, Cisco 6160, and Cisco 6260 digital subscriber line access multiplexers (DSLAMs).

Note When you upgrade from Cisco IOS 12.1(5)DA1 or earlier images on the NI-2 card to Release 12.2(5)DA1, you must format the bootflash on the NI-2 card before loading the 12.2(5)DA1 dboot image. See the "Update the Image in Bootflash to the 12.2(5)DA1 dboot Image" section.

System Requirements

New and Changed Information

New Hardware Features in Release 12.2(5)DA1

New Software Features in Release 12.2(5)DA1

New Hardware Features in Release 12.2(5)DA

Cisco 6015 in an Outside Plant Environment

This release includes support for a Cisco 6015 that can be installed in an outside plant setting. The Cisco 6015 is an ATM-based DSLAM designed to support up to 48 subscribers per chassis in remote cabinets, smaller COs, and multiple dwelling unit (MDU) sites in a scalable fashion. Through subtending, multiple Cisco 6015 DSLAMs can be deployed to provide connectivity to more than 48 subscribers. The Cisco 6015 system is a smaller density companion to the Cisco 6160/Cisco 6260 product family.

Octal-Port DMT ATU-C Line Card on the Cisco 6015 DSLAM in an Outside Plant Environment

This release includes support for the octal-port DMT (8xDMT) ATU-C line card on the Cisco 6015 in an outside plant environment. This line card:

•

Converts ADSL modulation from the line card into digital data streams to and from the NI-2 card

•

Negotiates the line rate with the customer premises equipment (CPE) when it trains and bases the rate on line quality and distance

•

Interoperates with the Cisco 677, Cisco 678, Cisco 827, Cisco 1417 CPE, and with certain third-party CPE

For more detailed information, see the Octal-Port DMT ATU-C Line Card feature module at the following URL:

http://www.cisco.com/univercd/cc/td/doc/product/dsl_prod/ios_dsl/rel121/feature/8xdmtfm0.htm

Octal-Port DMT ATU-C Over ISDN Line Card

The octal-port DMT ATU-C over ISDN (8xDMT over ISDN) line card provides higher port density for the Cisco 6015 and Cisco 6260. This line card:

•

Provides G.dmt support (ITU G.922.1), Annex B/ETSI, through both the MIB and the CLI

•

Converts ADSL modulation from the line card into digital data streams to and from the NI-2 card

•

Negotiates the line rate with the CPE when it trains and bases the rate on line quality and distance

Note

Check with a Cisco customer representative to verify CPE compatibility with the 8xDMT over ISDN.

Note

A correct firmware version does not guarantee interoperation with third-party CPE. Some hardware variations can affect performance and error rates. Test the interoperation of CPE with the 8xDMT over ISDN line card in the targeted deployment model before provisioning service. "

For more detailed information, see the Octal-Port DMT ATU-C over ISDN feature module at the following URL:

http://www.cisco.com/univercd/cc/td/doc/product/dsl_prod/ios_dsl/rel121/feature/8dmtisdn.htm

New Software Features in Release 12.2(5)DA

Cisco Networking Services Agents

Cisco Networking Services (CNS) is a foundation technology for linking users to network services. CNS Software Developers Kit (SDK) accomplishes this linking by making applications network-aware and increasing the intelligence of the network elements. CNS SDK provides building blocks to market segments such as enterprises, service providers, independent software vendors, and system integrators.

The CNS Configuration Agent feature supports routing devices by providing the following:

The CNS Event Agent is part of the Cisco IOS infrastructure that allows Cisco IOS applications to publish and subscribe to events on an NS Event Bus. CNS Event Agent works in conjunction with the CNS Configuration Agent feature.

MIB Object Changes

This release contains changes to the following Management Information Base (MIB) objects:

•

In the CISCO-CONFIG-MAN-MIB, the maximum size of the ccmHistoryTable was increased from 10 to 256.

•

The SNMP Query of ceAssetFirmwareRevision, in the CISCO-ENTITY-ASSET-MIB now returns the FlexiCAP Firmware Revision.

•

The CISCO-SDSL-LINE-MIB now specifies a range for receiver gain of an SDSL or a G.SHDSL modem in the object cSdslStucCurrGainRev, instead of cSdslStucCurrGain, which has been deprecated.

Optional String Parameter in atm pvc Command

The atm pvc and atm soft-vc Cisco IOS commands now allow you to include an optional name that associates a connection name to PVC and Soft PVC connections. The connection name is a unique identifier per DSLAM for a given connection. The length of the name can be up to 16 characters. See the Command Reference for Cisco DSLAMs with NI-2 for a description of the atm pvc and atm soft-vc commands.

Provisional Tagging Indication in ATM Signaling for SoftVCs

This feature allows you to enable the signaling of tagging and frame discard for SoftVCs based on SoftVC configuration parameters. The atm soft-vc command performs this function. You can configure whether you want forward or backward (or both) tagging sent if tagging is upc. The tagging is only signaled for VBR connections with CLP 0 SCR to reduce potential interoperability issues. See the Command Reference for Cisco DSLAMs with NI-2 for a description of the atm soft-vc command.

Show atm vc has Information about Softvc Connections

The show atm vc and show atm vp commands display more disconnect information about the SOFTvc's that are "NOT CONNECTED". The display gives a number corresponding to the disconnect reason. You can access the explanatory string for the disconnect with the following commands:

Installation Notes

Update the Image in Bootflash to the 12.2(5)DA1 dboot Image

When you upgrade from Cisco IOS Release 12.1(5)DA1 or earlier images on the NI-2 card to Release 12.2(5)DA1, you must reformat the bootflash on the NI-2 card.

Note If you are upgrading from Cisco IOS Release 12.1(6)DA, 12.1(6)DA2, 12.1(7)DA, 12.1(7)DA3, or 12.2(1b)DA1 you do not need to reformat the bootflash. You can skip this section and follow the DSLAM upgrade procedure at the following URL:
http://www.cisco.com/univercd/cc/td/doc/product/dsl_prod/ios_dsl/rel122/config/04conf09.htm.

Note We highly recommend that you have console access to the NI-2 card during the upgrade procedure. You can use the console connection to troubleshoot any unexpected events that occur during the upgrade.


	Command	Purpose
Step 1	DSLAM# dir bootflash:	Verify that the bootflash image is ni2-dboot-mz.121-5.da1 or ni2-dboot-mz.121-4.da. If it is neither, go to the "Upgrade the Bootflash Image on the NI-2 Card to the 12.1(5)DA1 dboot Image" section and perform the instructions there, and then return to this step. This is required because of a problem (CSCdr89374) in old bootflash images.
Step 2	DSLAM# dir flash:	Display the name of the Flash file that begins ni2- and use it as filename in Step 3.
Step 3	DSLAM# delete flash:filename	Delete the Flash file name found in Step 2. Repeat Step 2 and Step 3 until all files in the Flash file have been deleted.
Step 4	DSLAM# squeeze flash:	Recover available space in Flash memory.
Step 5	DSLAM# copy tftp://tftpserver:TFTPBOOT/ni2 -dsl-mz.122-5.da1 flash:	Copy the Cisco IOS image from a TFTP server to Flash.
Step 6	DSLAM# configure terminal DSLAM (config)# no boot system DSLAM (config)# boot system flash:ni2-dsl-mz.122-5.da1 DSLAM# end	Enter global configuration mode. Disable the boot from system. Specify the name of the system image to load at startup. End global configuration mode.
Step 7	DSLAM# copy running-config startup-config	Save your changes to the startup configuration.
Step 8	DSLAM# reload	Reload the system to upgrade the image.
Step 9	DSLAM# show version	Confirm that the running image is ni2-dsl-mz.122-5.da1. If it is not, go to Step 5.
Step 10	DSLAM# format bootflash:	Erase all information in bootflash memory. Answer y to all confirm questions. When the DSLAM returns you to the EXEC prompt, bootflash memory is successfully formatted and ready for use. Ensure that the bootflash is 3.8 MB total. If it is not, go to Step 5.
Step 11	DSLAM# copy tftp://tftpserver:TFTPBOOT/ni2 -dboot-mz.122-5.da1 bootflash:	Copy the boot image from a TFTP server to the bootflash.
Step 12	DSLAM# reload	Reload the system to upgrade the image.

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

When you upgrade from Release 12.1(3)DA or earlier images on the NI-2 card to Release 12.1(5)DA1, we recommend that you upgrade the bootflash image on the NI-2 card to the 12.1(5)DA1 dboot image.


	Command	Purpose
Step 1	DSLAM> enable Password: <password> DSLAM#	Enter enable mode. Enter the password. You have entered enable mode when the prompt changes to DSLAM#.
Step 2	DSLAM# delete bootflash:filename	Make room in the bootflash by deleting the name of the current boot image.
Step 3	DSLAM# squeeze bootflash	Recover available space in bootflash using the squeeze bootflash command.
Step 4	DSLAM# copy tftp://[server name] /[directory]/ni2-dboot-mz.121-5.da1 bootflash:	Copy the boot image to the bootflash.
Step 5	DSLAM# show version	Record the current value of the config-register that appears on the last line of the show version display.
Step 6	DSLAM# configure terminal	Enter global configuration mode. You have entered global configuration mode when the prompt changes to DSLAM(config)#.
Step 7	DSLAM(config)# config-register 0	Set the config register to 0x0000 so that the NI-2 reboots in the ROM monitor.
Step 8	DSLAM(config)# exit	Exit global configuration mode.
Step 9	DSLAM# copy running-config startup-config	Save the running configuration.
Step 10	DSLAM# reload	Reset the system.
Step 11	rommon> set	If you see BOOTLDR after you enter this command, the image in bootflash is already being used as the bootstrap image; go to Step 15. Otherwise, go to Step 12 and enter the commands in Steps 12 through 14 to force the system to use ni2-dboot-mz.121-5.bin as the bootstrap image.
Step 12	rommon> unset BOOTLDR	Unset BOOTLDR to remove the variable.
Step 13	rommon> sync	Sync to save the state of rommon.
Step 14	rommon> b	When the NI-2 boots, it uses ni2-dboot-mz.121-5da.bin as the bootstrap image.
Step 15	DSLAM# configure terminal	Enter global configuration mode. You have entered global configuration mode when the prompt changes to DSLAM(config)#.
Step 16	DSLAM(config)# config-register value	Set the config-register to the value you recorded in Step 5.
Step 17	DSLAM(config)# exit	Return to enable mode. Go to the "Update the Image in Bootflash to the 12.2(5)DA1 dboot Image" section.

Limitations and Restrictions

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

Attainable Bit Rate Is Conservative on 4xflexi-DMT and 8xDMT

Limitations

Due to line condition variations between trains, the effect of trellis coding, interleave delay, FEC check bytes, and so forth, the attainable bit rate estimate is not always 100 percent accurate. A conservative approach was taken in making the estimate; therefore, in general, you can get a higher rate than what the estimate suggests. For a fast-path scenario, the results should track fairly closely for the downstream rate and err on the conservative side for the upstream rate. For an interleave path scenario, the results are highly dependent on configurations.

At a higher reach or where line conditions are not optimal, the effect of having trellis coding, interleave delay, and FEC check bytes can provide a much higher rate than was estimated (greater than 128 kbps).

Workaround

There is no workaround. The aggregate bit rate calculation is an estimate, which does not accurately model all of the line conditions that affect the true attainable bit rate for a given profile. The calculations for aggregate bit rate are performed as follows:

•

The downstream capacity is obtained from the number of Reed-Solomon payload bytes per frame exchanged during line training, that is, the K value. The per-second estimate is then calculated from this K value. An extrapolated margin value is derived from the per-second estimate to make sure that if the line is trained at the estimated rate, it will still have an adequate margin.

•

For upstream, unlike downstream, the Reed-Solomon payload bytes per frame is not readily available. Furthermore, unlike downstream, which requires a CPE EOC response to know the downstream margin, the upstream margin is readily available at the CO (upstream margin is measured at the CO end). Using this upstream margin and the number of bins utilized for upstream, an estimate of upstream attainable bit rate is made. (The associated DDTS numbers are CSCdv05351 and CSCdv05322.)

CPE Performance Issues with Overhead Framing Modes 0, 1 and 2

The customer premises equipment (CPE) does not train or perform reliably when the Discrete Multitone (DMT) profile is set to use overhead framing mode 0, 1, or 2.

Workaround

Overhead framing mode 3 is designed for use in Asynchronous Transfer Mode (ATM). While overhead framing mode 1, which is not currently supported, is designed for Synchronous Transport Module (STM) mode. Configure your profiles to use overhead framing mode 3. Overhead framing mode 3 uses only 32 bytes of administrative overhead. Compared with overhead framing mode 1, it allows more bandwidth to be allocated to user data.

Trellis Coding Enable Default Recommendations

Trellis coding is disabled by default on the NI-2 because it is not supported on the 4xDMT (ATUC-1-4DM) card. However, trellis coding is supported on the 4xFlexiDMT (ATUC-4FLEXIDMT) and 8xDMT (ATUC-1-DMT8) line cards. Additionally, trellis coding should be enabled for the 4xFlexiDMT and 8xDMT line cards.

For all 4xDMT (ATUC-1-4DMT) ports in the DSLAM, make sure that trellis coding is disabled in the dsl-profile for those ports. For all 4xFlexiDMT and 8xDMT ports in the DSLAM, make sure that trellis coding is enabled except with ADI chipset based CPE using ADI F/W prior to ADI 3.1. This includes all Cisco 677 and Cisco 627 CPEs.

See the documentation at the following location for details on the commands used to change trellis coding settings on the NI-2:

http://www.cisco.com/univercd/cc/td/doc/product/dsl_prod/ios_dsl/rel122/config/04conf04.htm#xtocid1734531

Restrictions on NI-2 IP Services

Restricted Layer 3 Services

Cisco IOS Release 12.2(5)DA1 does not support the following Layer 3 services (or else these services are limited, as noted):

•

The maximum number of MPLS/VPN for PPPoA terminations is 25 VPNs for PPPoA and 1 VPN for PPPoE.

•

We recommend use of a virtual template for PPPoX termination rather than a dialer interface.

•

Up to 32 subinterfaces can be used for IP termination under the trunk or subtend ports.

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 (LERs).

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 MPLS Features

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

DSL Interface Limitations

In DSLAMs, each DSL interface can support multiple permanent virtual circuits (PVCs), but we recommend that you use one routed MPLS VC if a dynamic routing protocol, such as RIP, is used between the CE and the PE.

MPLS VPN Mapping Not Supported on the Eight-Port IDSL ITU-C Line Card

Routed termination of IDSL connections is not supported since Cisco IOS Release 12.2(1b)DA1.

Frame Relay PVCs/Soft PVCs on an IDSL Interface

The number of Frame Relay PVCs/Soft PVCs on an IDSL interface is restricted to 1 if you use the default row in a frame-relay connection traffic table (FR-CTT).

When upgrading to Cisco IOS Release 12.2(5)DA1 from previous releases, you must first create a new row in the FR-CTT with the desired CIR value and use the resultant row number during PVC/Soft PVC creation. If you do not create a new row, the second FR PVC/Soft PVC command is not parsed and installed on the IDSL interface.

Use of a Ring Topology in a DSLAM Subtend Environment to Achieve ATM Trunk Redundancy

Ring topology is achieved when a node in the subtend tree is attached to the ATM access to provide a physically redundant loop. Thus, when the primary ATM access or one of the ATM trunks in the subtend tree fails, the soft permanent virtual circuits (SPVCs) can be dynamically rerouted through the use of Private Network-Network Interface (PNNI). See Figure 1.

This redundancy requires the use of SPVCs. If you use permanent virtual circuits (PVCs) or permanent virtual paths (PVPs), redundancy cannot be provided. The use of the SPVCs allows traffic to be rerouted around the failed access point, because SPVCs leverage this feature of PNNI. When the failure occurs, the SPVCs are disconnected and dynamically reconnected across the new path. See Figure 2.

Requirements

If you implement ring topology in a DSLAM subtend to achieve ATM trunk redundancy, the following requirements apply:

•

You must use SPVCs, PNNI, ATM signaling, and Interim Local Management Interface (ILMI) to enable rerouting. PNNI, ATM signaling, and ILMI are enabled by default. Permanent connections such as PVCs and shaped virtual paths (VPs) do not benefit from the redundant link.

•

You must make the redundant link's PNNI administrative weight higher than the PNNI weight of the primary trunk. Once you change the weight of the redundant link, the subtend tree uses this link only if a failure occurs.

Limitations

•

Increase in latency as well as an increase in cell delay variation (CDV) between the cells. Delay-sensitive traffic, such as voice and video, or traffic that is susceptible to jitter, such as constant bit rate (CBR) voice, might be compromised. This technique is best realized for unspecified bit rate (UBR) traffic, such as consumer internet access, where no strict quality of service (QoS) objectives are required.

Once the redundant link is active, the following occurrences are potential problems:

•

Greater possibility of increased congestion in the DSLAM ATM switch fabric, which might cause loss of data.

•

When the main link is restored, there is downtime while the path is being rerouted. After the SPVCs are rerouted to the redundant ATM trunk and the original trunk is repaired or brought back into service, you must manually intervene. You must flap (shut/noshut) the subtend port. Because of retries on the current path, you must keep the trunk down until the maximum retry interval expires.

Cisco DSL Manager

If you are using versions of Cisco DSL Manager (CDM) before CDM Release 3.4—from CDM Release 1.0 to CDM Release 3.3(3)—do not upgrade the DSLAMs to this new Cisco IOS release.

If you use both the CDM network management application and the Cisco IOS command line interface to manage your Cisco DSLAMs, you should be aware of certain configuration and procedural implications. Please refer to the Release Notes for the Cisco DSL Manager, Release 3.4 for this information.

Important Notes

NI-2 IP Services

During system startup, the following protocol warning messages display. You can ignore these messages.

Soft PVC Address Changes upon Upgrade from Release 12.1(4)DA or Earlier

When you upgrade from Cisco IOS Release 12.1(4)DA or earlier to Release 12.2(5)DA1, the default soft PVC addresses on all interfaces change. This occurs only when you upgrade to Release 12.2(5)DA1 from Release 12.1(4)DA or earlier.

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 Release 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 might not come back up after the IDSL line goes down and comes 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.

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 command.)

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 in a telco equipment rack. A standard 7-foot equipment rack can house four Cisco 6160 chassis, stacked one on top of another. This configuration maximizes the DSL density within a 7-foot rack. However, if space is available or if you are interested in using multiservice capabilities that the chassis will support in the future, we recommend that you install no more than three Cisco 6160 chassis within a 7-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.

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

Caveats describe unexpected behavior in Cisco IOS software releases. Severity 1 caveats are the most serious caveats; severity 2 caveats are less serious. Severity 3 caveats are moderate caveats, and only select severity 3 caveats are included here.

This section contains only open, closed, and resolved caveats for the current Cisco IOS release.

Caveat numbers and brief descriptions are listed in Table 1, Table 2, Table 3, Table 4, Table 5, and Table 6. For details about a particular caveat and for information on caveats in previous Cisco IOS releases that also apply to this release, go to Bug Toolkit at:

To access this location, you must have an account on Cisco.com. If you have forgotten or lost your account information, e-mail the Contact Database Administration group at cdbadmin@cisco.com. If you do not have an account on Cisco.com, go to http://www.cisco.com/register and follow the directions to set up an account.

Note If you have an account with Cisco.com, you can use Bug Navigator II to find caveats of any severity for any release. To reach Bug Navigator II, go to Cisco.com and click Login. Then go to Software Center > Cisco IOS Software > Cisco Bugtool Navigator II . Alternatively, you can go to

http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl

This software release is based on Cisco IOS Release 12.2. For information on caveats in Cisco IOS Release 12.2, see Caveats for Cisco IOS Release 12.2, which lists severity 1 and 2 caveats and select severity 3 caveats for Cisco IOS Release 12.2. It is located on Cisco.com and the Documentation CD-ROM.

Open Caveats—Release 12.2(5)DA

All the caveats listed in Table 1 are open in Cisco IOS Release 12.2(5)DA. This table lists only severity 1 and 2 caveats and select severity 3 caveats.

Closed Caveats—Release 12.2(5)DA

Table 1 Open Caveats for Cisco IOS Release 12.2(5)DA
Caveat Number	Description
CSCdu48003	The Init event counter toggles between 0 and 4294967295 several times in a minute for 4xFlexiDMT.
CSCdv28281	File system synchronization does not work correctly when one NI-2 is running Cisco IOS Release 12.2(1b)DA or Release 12.2(5)DA and the other NI-2 in the chassis is running release Cisco IOS Release 12.1(7)DA3 or an earlier build. The files are copied correctly but a message is generated at the end of the operation indicating that the sync failed. Workaround: Manually copy the files between the NI-2s.
CSCdv32720	The 8xDMT over ISDN line card does not recognize the dying gasp messages from any CPE. The Far End LPR Events counter in the show dsl interface atm x/y command does not increment when dying gasp messages are sent from a CPE. Workaround: None

All the caveats listed in Table 2 are closed in Cisco IOS Release 12.2(5)DA. This table lists only severity 1 and 2 caveats and select severity 3 caveats.

Open Caveats—Release 12.2(1b)DA

Table 2 Closed Caveats for Cisco IOS Release 12.2(5)DA
Caveat Number	Description
CSCdt27044	Filesys space error is displayed when you perform the first write mem command following a reload.
CSCdt27246	CIB Save FAILED message is displayed during NI-2 boot.
CSCdv12425	As explained in the "More-info" enclosure, the IMA error message is printed and the system reboots - only at the point where there is no possible SW recovery. Workaround: None.
CSCdv38294	VPI/VCI values for provisioned PVC do not match the provisioned values. The problem occurs when a VCI value of 0 is selected for any nonterminating PVC, that is, a PVC not terminating at atm0/0. Workaround: Use non-zero VCI values for all PVCs.

All the caveats listed in Table 3 are open in Cisco IOS Release 12.2(1b)DA. This table lists only severity 1 and 2 caveats and select severity 3 caveats.

Table 3 Open Caveats for Cisco IOS Release 12.2(1b)DA
Caveat Number	Description
CSCdt81452	PPP negotiation does not occur if the ppp encapsulation command references a nonexistent virtual template. Workaround: Configure a complete virtual-template interface first, and then configure the PPP PVC.
CSCdu09877	The 8xDMT line card ignores interleave setting when trained to 677. Workaround: None.
CSCdu10692	If you configure no ip cef and ip cef in very quick succession, MPLS ceases operating and the show mpls forwarding command reports that tag switching is not operational. CEF or tag switching has not been enabled. Workaround: Configure no ip cef, wait 2 seconds, and then configure ip cef.
CSCdu35160	Packet loss occurs when you police with abr for MCR values greater than 18. Workaround: None.
CSCdu39970	A per-user route from a previous IPCP subnet negotiation might appear in the routing table after the PPP circuit has been added again with a no pvc X/Y command and then followed by the pvc X/Y command. Workaround: Use the no ip route command to remove the stale per-user route.
CSCdu46804	IP address negotiation via IPCP to an external DHCP server across an ATM link fails. Workaround: Use a local DHCP server connected on the Ethernet segment.
CSCdu74113	If you use NAS-PORT format D, the underscore delimiter is missing in the Acct-Session-Id attribute. Workaround: None.
CSCdu78386	The static VRF route applied on the PE does not take effect. There is no connectivity if you use static routing over MPLS/VPN. Workaround: Redistribute static or RIP route into BGP from the egress PE; the ingress PE will learn the egress PE VPN routes.
CSCdv05322	Attainable bit rate is conservative for 4xFLEXI-DMT. Workaround: None. The aggregate bit rate calculation is an estimate, which does not accurately model all of the line conditions that affect the true attainable bit rate for a given profile.

Resolved Caveats—Release 12.2(5)DA1

Resolved Caveats—Release 12.2(5)DA

Table 4 Caveats Resolved in Cisco IOS Release 12.2(5)DA1
Caveat Number	Description
CSCdw65903	An error can occur with management protocol processing. Please use the following URL for further information: http://www.cisco.com/cgi-bin/bugtool/onebug.pl?bugid=CSCdw65903

Table 5 Caveats Resolved in Cisco IOS Release 12.2(5)DA
Caveat Number	Description
CSCdt89256	Cisco 6160 DSLAM does not recognize the debug atm oam command.
CSCdt91908	When an IMA group and some of the links in the group are administratively shutdown, the IMA group cannot recover.
CSCdu06659	GETNEXT fails for all entries in cAdslAtucDmtChanTable.
CSCdu06678	GETNEXT fails for all entries in cAdslAturDmtChanTable.
CSCdu15630	Auto-sync of startup-config does not always work.
CSCdu17222	The port state that the show aps command displays for the subtend port on the standby card is not valid until the peer state indicated by the command show redundancy states is "STANDBY READY".
CSCdu18944	When both NI-2s in a redundant configuration reboot simultaneously, the standby card may reboot more than once if the configuration file is very large.
CSCdu24772	System shows secondary running config failed during RF progression.
CSCdu35414	Auto-sync of running config can cause write command to fail.
CSCdu44723	The show facility-alarm status command displays incorrect message.
CSCdu75769	When you issue an atm oam intercept end-to-end command, an error message appears.
CSCdu76334	SNMP query for the MIB objects adsl[Atuc/Atur]ChanCurrTxRate (ADSL-LINE-MIB) returned swapped values for CAP line card.
CSCdu80361	Failed to set overhead framing structure to structure0 in DMT.
CSCdu83833	CLI command snmp get/set is seen via CLI help.
CSCdv15430	Stur objects are not supported on SHDSL.
CSCdv23151	A DMT interface configured to use fast channel returns values on this interface's adslAtucChanIntervalTable and adslAturChanIntervalTable.
CSCdv32861	The mib object atmInterfaceMyNeighborIpAddress in the ATM mib can contain incorrect address.
CSCdv38540	Ping not responding but Telnet works.
CSCdv39307	Some ports of flexiCAP lock up as trained even when CPE is untrained.
CSCdv52839	When more than 150 PVPs are configured, the Cisco 6260 DSLAM cannot be booted after a power cycle or a reload. Workaround: Power-off the DSLAM, "break" into rommon, boot the DSLAM without parsing the configuration, and copy the startup to running-config.
CSCdv62132	Cisco 677 retrains on Cisco 6260 DSLAM with 8xDMT line cards.
CSCdv61164	cAdslAtucCapCurrRxSnr is reporting in dB, where as the MIB definition states that it should be reported in 1/10th dB.

Resolved Caveats—Release 12.2(1b)DA

Table 6 Caveats Resolved in Cisco IOS Release 12.2(1b)DA
Caveat Number	Description
CSCdr38060	Add attainable bit rate on 4xflexi DMT.
CSCdr96185	When you are executing a show version command, SHDSL ports are shown as SDSL ports.
CSCds14884	No log event link-status command has no effect.
CSCds15469	IP MTU or Physical MTU setting has no effect on fragmentation.
CSCds80863	MIB adslAtucCurrStatus returns incorrect value for CAP and DMT.
CSCds81122	MIB adslAturCurrStatus returns incorrect value for DMT.
CSCdt11375	Performance interval counters are not correct for G.SHDSL.
CSCdt34090	Profile created from altered default has different parameters.
CSCdt71353	Minimum DMT bitrate setting is lost after upgrade.
CSCdt73955	The delay does not change when oamLoopbackPingDelay is changed.
CSCdt75675	Link down traps are not reliably sent for IDSL.
CSCdt76848	SDSL profile lists rates of 1552, 2064, and 2320 and allows their use.
CSCdt79352	MIB adslAturChanTransmittedBlks has a MIB value of 0 but CLI has non-0.
CSCdt79387	adslAturVendorID will return 0 from MIB, CLI has 57 (Globespan).
CSCdt79394	MIB adslAtucChanCrcBlockLength always has a value of 0.
CSCdt79405	MIB adslAturChanCrcBlockLength always has a value of 0.
CSCdt79412	MIB cIdslItucInvSerialNumber returns garbage instead of empty string.
CSCdt81887	IMA group collapses when differential delay changed on one line.
CSCdt88209	Some DSL statistics missing in Cisco IOS 12.1(5)DA for DMT cards.
CSCdt94063	OAM ping of IMA group depends on state of CPE connection.
CSCdu05779	MIB imaGroupLeastDelayLink is not supported in MIB.
CSCdu06348	SDSL attempts to report LOS events instead of LOSQ in the show dsl interface display.
CSCdu07798	PEM alarm does not clear after hot swap replacement.
CSCdu11030	MIB imaGroupTestProStatus does not match CLI.
CSCdu11335	MIB: All Prev1Day performance counters are always zero.
CSCdu11634	Line ports reset when CPU usage is high.
CSCdu12291	Issuing show run on the NI-2 results in SNMP query timeout.
CSCdu17619	Attainable aggregate bitrates do not apply to 8xDMT.
CSCdu20810	CPU utilization is degrading.
CSCdu26649	MIB SONET physical layer does not match logical layer.
CSCdu35353	Limitation to 32 VPI values even if the VP tunnels are not shaped.
CSCdu44511	8xDMT is unable to train at 1024 kbps upstream with Cisco 678.
CSCdu45628	IOS reloads with update_the_1day_counts on top of stack.
CSCdu47978	Init Event counters toggle between 0 and max int in 8xDMT cards.
CSCdu48059	Inconsistent counter operations exist for Atuc/Atur IntervalEntry fields.
CSCdu57284	ItucIntervalNumber is more than 96 while querying ItucIntervalTable.
CSCdu64006	Soft PVC address on the Cisco 6260 DSLAM is changed after upgrade.
CSCdu71803	When an F4 OAM atm seg cell, with a PT field set for end-to-end type, is received on nonprovisioned VP, the system reloads.

Table Of Contents