Enhanced Voice and QoS for ADSL and G.SHDSL on Cisco 1700 Series, Cisco 2600 Series, and Cisco 3600 Series Routers
Available Languages
Table Of Contents
Class-Based Packet Marking with Differentiated Services
Dial-Peer DSCP and IP Precedence Marking
Network-Based Application Recognition
Class-Based Weighted Fair Queueing
Class-Based Weighted Random Early Detection with DSCP (egress)
Weighted Random Early Detection
VC Shaping for Variable Bit Rate-Nonreal Time
cRTP over an ATM Link with PPP Encapsulation
Link Fragmentation and Interleaving
IP QoS Map to ATM Class of Service
Analog Voice Interface Support
F5 OAM CC Segment Functionality
H.323 and Media Gateway Control Protocol
Survivable Remote Site Telephony
Supported Standards, MIBs, and RFCs
Configuring ATM CLP Bit Marking
Configuring the Clock Rate for ADSL and G.SHDSL WICs
Verifying the Clock Setting for ADSL and G.SHDSL WICs
Troubleshooting the Clock Setting for ADSL and G.SHDSL WICs on Cisco 2600 Series and Cisco Series
Configuring cRTP over an ATM Link with ATM Encapsulation
Troubleshooting Tips for MLP Bundling
ATM CLP Bit Marking over G.SHDSL Example
Clock Rate for ADSL and G.SHDSL WICs Example
cRTP over an ATM Link with PPP Encapsulation Example
Tx Ring-Limit Tuning over ADSL Example
Enhanced Voice and QoS for ADSL and G.SHDSL on Cisco 1700 Series, Cisco 2600 Series, Cisco 3600 Series, and Cisco 3700 Series Routers
Feature History
This document describes enhancements to the voice and quality of service (QoS) features for asymmetric digital subscriber lines (ADSLs) and single-pair high-bit-rate digital subscriber lines (G.SHDSLs) on the Cisco 1700 series, Cisco 2600 series, Cisco 3600 series, and Cisco 3700 series. This document includes the following sections:
•
Supported Standards, MIBs, and RFCs
Feature Overview
Cisco 1700 series, Cisco 2600 series, Cisco 3600 series, and Cisco 3700 series routers with ADSL or G.SHDSL WAN interface cards (WICs) support the integration of voice and data over the same ADSL or G.SHDSL circuit using Voice over IP (VoIP). The Cisco 2600 series, Cisco 3600 series, and Cisco 3700 series routers with ADSL or G.SHDSL WICs also support the integration of voice and data over the same ADSL or G.SHDSL circuit using Voice over ATM (VoATM).
Note
–
–
–
–
–
–
QoS features make it possible to effectively combine voice and data traffic in the same WAN connection without sacrificing quality and reliability. Service providers can increase revenue by building differentiated service options based on premium, standard, or best-effort service classes.
The following voice and QoS features are supported on ADSL and G.SHDSL WICs. The new features introduced in Cisco IOS Release 12.2(8)YN are marked with an asterisk (*).
–
–
–
–
–
–
–
–
–
–
–
–
•
–
–
–
–
–
–
–
–
–
–
Table 1 lists the voice and QoS features for ADSL and G.SHDSL and the releases in which they are available. Table 2 provides some summary information regarding platform support for each release. Refer to Cisco IOS release notes at cisco.com for more details about platform support and memory requirements for each release.
Note
Table 2 lists the Cisco IOS releases in which voice and QoS Support for ADSL and G.SHDSL are available and the platforms supported on each release. A "yes" means that the Cisco platform listed in the header row is supported on the release listed in the "Release" column. An "x" means that the Cisco platform is not supported in the release listed in the "Release" column.
Classification and Marking
The following Cisco IOS classification and marking features are supported on ADSL WICs and G.SHDSL WICs:
•
•
•
ATM CLP Bit Marking
When congestion occurs in an ATM network, ATM cells are discarded. One way to control which cells are discarded is to use the cell loss priority (CLP) bit in the ATM header of each cell. The CLP bit may be set to either 1 or 0. Those cells that have the CLP bit set to 1 are always discarded before any of the cells that have the CLP bit set to 0.
The ATM CLP Bit Marking feature allows you to control the CLP setting on Cisco routers. The marking of the CLP bit is implemented on a per-packet basis so that the CLP bit of every ATM cell that belongs to a particular packet is set to either 0 or 1.
For an example of output in which ATM CLP Bit Marking has been enabled, see the section "ATM CLP Bit Marking over G.SHDSL Example."
For more information about ATM cell bit marking, refer to the following document:
•
Class-Based Packet Marking with Differentiated Services
For information about class-based packet marking with differentiated services, refer to the following document:
•
Committed Access Rate
For information about committed access rate (CAR), refer to the following document:
•
Dial-Peer DSCP and IP Precedence Marking
For information about dial-peer differentiated services code points (DSCPs) and IP precedence marking, refer to the following document:
•
Local Policy Routing
For information about local policy routing (LPR), refer to the following documents:
•
•
Network-Based Application Recognition
For information about network-based application recognition (NBAR), refer to the following documents:
•
•
•
Policy-Based Routing
For information about policy-based routing (PBR), refer to the following documents:
•
•
Queueing and Scheduling
The following Cisco IOS queueing and scheduling features are supported on ADSL WICs and G.SHDSL WICs:
•
Class-Based Weighted Fair Queueing
For information about class-based weighted fair queueing (CBWFQ), refer to the following document:
•
Low Latency Queueing
For information about low latency queueing (LLQ), refer to the following documents:
•
•
Note
Per-VC Queueing
Per-virtual circuit (per-VC) queueing is supported on ADSL and G.SHDSL interfaces at the driver level, similar to VC-queueing features on other ATM interfaces. This feature underlies many of the Cisco IOS QoS queueing features, such as LLQ.
For more information about per-VC queueing, refer to the following documents:
•
•
and 2600 RoutersCongestion Avoidance
The following Cisco IOS congestion avoidance features are supported on ADSL WICs and G.SHDSL WICs:
•
•
•
Class-Based Weighted Random Early Detection with DSCP (egress)
Class-Based Weighted Random Early Detection (WRED) is supported on ADSL and G.SHDSL WICs.
For more information about WRED, refer to the following documents:
•
•
•
Resource Reservation Protocol
For information about Resource Reservation Protocol (RSVP), refer to the following documents:
•
•
•
•
Weighted Random Early Detection
For information about Weighted Random Early Detection (WRED), refer to the following document:
•
Policing and Traffic Shaping
The following Cisco IOS policing and shaping features are supported on ADSL WICs and G.SHDSL WICs:
•
ATM Traffic Shaping
For information about ATM traffic shaping, refer to the following document:
•
•
Class-Based Policing
For information about traffic classes and traffic policies, refer to the following document:
•
Traffic Policing
For information about traffic policing, refer to the following documents:
•
•
VC Shaping for Variable Bit Rate-Nonreal Time
For information about VC shaping for variable bit rate-nonreal time (VBR-NRT), refer to the following document:
•
Link Efficiency
The following link latency features are supported on ADSL WICs and G.SHDSL WICs:
•
•
cRTP over an ATM Link with PPP Encapsulation
The Compressed Real-Time Protocol (cRTP) feature reduces bandwidth consumption on real-time applications such as voice. Thus, by using cRTP, you can further improve voice quality. Configuring cRTP can save troubleshooting time by isolating potential cRTP issues. Based on RFC 2508, the RTP header compression feature compresses the IP, User Data Protocol (UDP), and Real-Time Transport Protocol (RTP) header (IP/UDP/RTP header) from 40 bytes to 2 or 4 bytes, reducing unnecessary bandwidth consumption. It is a hop-by-hop compression scheme; therefore, cRTP must be configured on both ends of the link (unless the passive option is configured).
To configure cRTP, use the ip rtp header-compression command.
Because the compression process can be CPU intensive, RTP header compression was implemented in the fast-switching and Cisco Express Forwarding (CEF) switching paths in Cisco IOS Release 12.0.(7)T. Sometimes the cRTP implementations are broken, and if they are broken, the only way that cRTP will work is to use process switching. It is recommended that cRTP be used with links lower than 768 kbps unless the router is running at a low CPU utilization rate. Monitor the CPU utilization of the router, and disable cRTP if it is above 75 percent.
When you configure the ip rtp header-compression command, the router adds the ip tcp header-compression command to the configuration by default. This command is used to compress the TCP/IP packets of the headers. Header compression is particularly useful on networks that have a large percentage of small packets, such as those supporting many Telnet connections. The TCP header compression technique, described fully in RFC 1144, is supported on serial lines using High-Level Data Link Control (HDLC) or PPP encapsulation.
To compress the TCP headers without enabling cRTP, use the ip tcp header-compression command.
To enable cRTP over an ATM Link with PPP Encapsulation, see the "Configuring cRTP over an ATM Link with ATM Encapsulation" table.
Link Fragmentation and Interleaving
For information about the Link Fragmentation and Interleaving (LFI) feature, refer to the following document:
•
MLP Bundling
Multilink PPP (MLP), standardized in RFC 1990, is similar to load balancing techniques in that it sends packets across the individual links in a round-robin fashion. However, MLP adds three significant capabilities:
•
•
•
Additionally, when more bandwidth is needed, additional links can be added to the bundle by simply configuring them as members of the bundle. No reconfiguration at the network layer, such as new addressing, is needed. This is also a significant factor when considering the use of advanced router services. For example, a specific QoS can be configured once for the bundle as a whole rather than on each link in the bundle.
The trade-off for the increased functionality is that MLP requires greater CPU processing than load-balancing solutions. Packet reordering, fragment reassembly, and the MLP protocol itself increase the CPU load.
Note
•
•
To enable MLP bundling, see the section "Configuring MLP Bundling."
PPPoE MTU Adjustment
If a Cisco router terminates the PPP over Ethernet (PPPoE) traffic, a computer connected to the Ethernet interface may have a problem accessing websites. The solution is to manually reduce the maximum transmission unit (MTU) configured on the computer by constraining the TCP maximum segment size (MSS). To manually reduce the MTU configured on the computer, use the ip tcp adjust-mss command. The mss argument value must be 1452 or less.
For more information about adjusting the PPPoE MTU, refer to the following document:
•
Tunable Transmission Ring
The transmission (tx) ring is the FIFO buffer used to hold frames before transmission at the DSL driver level. The tx ring defines the maximum number of packets that can wait for transmission at Layer 2.
The tx ring complements the ability of LLQ to minimize jitter and latency of voice packets. For maximum voice quality, a low tx ring setting should be used. For maximum data throughput, a high tx ring setting should be used.
You can configure the size of the tx ring for each permanent virtual circuit (PVC). The default value is 60. However, the value of the setting can be 2 through 60 on Cisco 1700 series routers and 3 through 60 on Cisco 2600 and Cisco 3600 series routers. A low tx ring setting, such as 2 or 3, is required for latency-critical traffic. For example, when the tx ring limit is configured as 3 and LLQ is configured on the PVC, the worst case delay for a voice packet is the time required to transmit three data packets. When the buffering is reduced by configuring the tx ring limit, the delay experienced by voice packets is reduced by a combination of the tx ring and LLQ mechanism.
Note
VC Bundling
For infomation about virtual circuit (VC) bundling, refer to the following document:
•
Other (IP QoS)
The following IP QoS features are supported on ADSL WICs and G.SHDSL WICs:
•
Access Control Lists
For infomation about access control lists, refer to the following document:
•
IP QoS Map to ATM Class of Service
For information about IP QoS map to ATM class of service (CoS), refer to the following document:
•
Additional Supported Features
The following Cisco IOS features are supported on ADSL WICs and G.SHDSL WICs:
•
•
•
•
•
•
•
•
•
Analog Voice Interface Support
Note
For more information about analog voice interface support, refer to the following document:
•
Clock Rate for AAL5 and AAL2
The communication between DSL WICs and a host in a router occurs through a device called the Serial Communication Controller (SCC). If a host wants to forward data or send any control traffic to a DSL WIC, it uses SCCs. In the same way, if a DSL WIC wants to forward incoming data from a line to the host, it also uses SCCs. Each DSL WIC installed in the router uses two SCCs. One SCC (SCC-A) is used for AAL5 data traffic, and the other SCC (SCC-B) is used for AAL2 and control traffic. The speed at which the SCC transfers data between a host and a WIC depends on the clock rate with which it has been configured. You can configure this clock rate on the basis of the DSL line rate. Even though the DSL upstream and downstream line rate may vary, the clock rate between the SCC and the DSL WIC is the same for both the transmitting and receiving direction. That is, the communication between the SCC and the DSL WIC is synchronous. Therefore, you need to configure only one clock rate for an SCC that will be used for both transmitting and receiving between an SCC and a DSL WIC.
It is always recommended that you configure the SCC clock rate slightly higher than the DSL line rate to accommodate overhead between the SCC and the DSL WIC. For an asynchronous DSL WIC (for example, ADSL), the SCC clock rate depends on either the downstream or the upstream line rate, whichever is the maximum rate. For a synchronous DSL WIC (for example, G.SHDSL), the bandwidth for upstream and downstream is the same. Therefore, the SCC clock rate configuration can be based on either the upstream or the downstream line rate.
To configure the clock, use the clock rate command, which is shown in the section "Configuring the Clock Rate for ADSL and G.SHDSL WICs."
Maximum Clock Rate Limits and Defaults
Because the maximum line rate for G.SHDSL is 2.312 Mbps, the default SCC clock rate of 2.6 Mbps for AAL5 and 1 Mbps for AAL2 should be sufficient. However, for ADSL, the clock rate may need to be configured on the basis of the current line rate. If AAL2 is used for voice traffic, the AAL2 SCC must be configured to the appropriate clock rate: 1 Mbps for ADSL and 2.6 Mbps for G.SHDSL.
The maximum data rate between an SCC and a DSL WIC depends primarily on the maximum clock rate that the SCC can support. For example, on the Cisco 2600 series mainboard, which supports two DSL WICs, the total SCC clock rate that can be configured for both WICs is 8 Mbps. Therefore, if only one DSL WIC is present on the mainboard, AAL5 and AAL2 clock rates can be configured to 7 Mbps and 1 Mbps, respectively. If two DSL WICs are supported on the mainboard, the total of 8 Mbps should be distributed among the four SCCs.
Network module SCCs also pose similar limitations. That is, on the Cisco 2600 series, the total clock rate for all four SCCs is 8 Mbps. The maximum AAL5 clock rate that may be configured on a network module is 5.3 Mbps. On the Cisco 1700 series, the maximum configurable SCC clock rate for both AAL5 and AAL2 is 8 Mbps.
If the clock rate is unconfigured, the SCC is reset to the default values. See the clock rate (interface ATM) command for a more complete explanation of default values and maximum and minimum values.
Concurrent VoIP and VoATM
The Concurrent VoIP and VoATM feature allows you to make VoIP over ATM (aal5snap) and VoATM (aal5mux) calls concurrently over xDSL.
Note
F5 OAM CC Segment Functionality
For information about F5 Operation, Administration, and Maintenance Continuity Check (F5 OAM CC) segment functionality, refer to the following documents:
•
•
FRF.5 and FRF.8
To communicate over WANs, end-user stations and the network cloud typically must use the same type of transmission protocol. This limitation has prevented differing networks such as Frame Relay and ATM from being linked. The Frame Relay-to-ATM service interworking feature allows Frame Relay and ATM networks to exchange data despite differing network protocols. The functional requirements for linking Frame Relay and ATM networks are provided by the Frame Relay/ATM PVC Service Interworking Implementation Agreement specified in Frame Relay Forum (FRF) documents FRF.5 and FRF.8. The FRF.5 and FRF.8 interworking functions involve multiplexing PVCs between Frame Relay and ATM networks and mapping the control bits between Frame Relay frame headers and ATM cell headers. FRF.5 and FRF.8 are necessary for ATM-based features to interwork with Frame-Relay-based IP class of service features.
To configure FRF.5 and FRF.8, see the sections "Configuring FRF.5" and "Configuring FRF.8."
H.323 and Media Gateway Control Protocol
For information about H.323 and Media Gateway Control Protocol (MGCP) testing, refer to the following document:
•
ILMI
For information about Integrated Local Management Interface (ILMI) protocol implementation for Cisco digital subscriber loop access multiplexers (DSLAMs) with N1-2 cards, refer to the following document:
•
Multiple PVC Support
Note
For information about PVCs, refer to the following documents:
•
•
Refer to the following documents for caveat information for multiple PVCs on Cisco 1700 series, Cisco 2600 series, and Cisco 3600 series routers for Cisco IOS Release 12.2(2)XK:
•
•
•
Refer to the following documents for caveat information for multiple PVCs on Cisco 1700 series, Cisco 2600 series, and Cisco 3600 series routers for Cisco IOS Release 12.2(4)XL:
•
•
•
Refer to the following document for caveat information for multiple PVCs on Cisco 1700 series routers for Cisco IOS Release 12.2(8)YN:
•
OAM
For infomation about Operation, Administration, and Maintenance (OAM), refer to the following document:
•
PPPoE Client
For information about the Point-to-Point Protocol over Ethernet (PPPoE) Client feature, refer to the following document:
PPPoE over ATM
PPPoE over ATM enables PPP sessions to be transported via an Ethernet-connected PC over an ATM DSL link. For more information about the PPPoE over ATM feature, refer to the following document:
RFC 1483 Bridging
For information about RFC 1483 bridging, refer to the following documents:
•
RFC 1483 Routing
For information about ATM and ATM adaptation layers (AALs), refer to the following document:
•
Session Initiation Protocol
For information about Session Initiation Protocol (SIP), refer to the following document:
•
Survivable Remote Site Telephony
For information about Survivable Remote Site Telephony (SRST), refer to the following document:
•
VoATM over AAL2
For information about Voice over ATM over AAL2, refer to the following documents:
•
•
Note
VoATM over AAL5
For information about Voice over ATM over AAL5, refer to the following document:
•
Note
VoIP over AAL5
For information about Voice over IP over AAL5, refer to the following document:
•
Benefits
QoS provides improved and more predictable network service for ADSL and G.SHDSL by
•
•
•
•
•
•
Restrictions
•
•
Related Documents
See Table 3 for documents related to the Enhanced Voice and Qos for ADSL and G.SHDSL features on Cisco 1700 series, Cisco 2600 series, and Cisco 3600 series routers.
Table 3 Related Documents
AAL2
•
•
Access control lists
•
ADSL and G.SHDSL WAN interface cards
•
•
•
•
•
•
Analog voice interface support
•
ATM CLP bit marking
ATM, configuring
•
•
ATM traffic shaping
•
•
Class-based packet marking with DSCP
•
Class-based policing
•
Class-based weighted fair queueing
•
Class-based WRED with DSCP (egress)
•
•
Committed access rate (CAR)
•
Dial-peer DSCPs and IP precedence marking
•
F5 OAM CC segment functionality
•
•
H.323 and Media Gateway Control Protocol (MGCP)
•
ILMI
•
IP, configuring
•
•
IP QoS map to ATM CoS
•
Link fragmentation and interleaving (LFI)
•
Local policy routing (LPR)
•
Low latency queueing
•
•
MLP with LFI
•
Multiple PVC support
•
•
Network-based application recognition (NBAR)
•
•
•
OAM
•
Per-VC queueing
•
•
PPPoE client
PPPoE MTU adjustment (ip tcp adjust-mss command)
•
•
PPPoE over ATM
Policy-based routing
•
•
QoS, configuring
•
•
QoS features on Cisco 1700 series routers
Resource Reservation Protocol (RSVP)
•
•
•
•
RFC 1483 bridging
•
RFC 1483 Routing
For information about ATM and ATM adaptation layers:
•
For information about AAL5 Subnetwork Access Protocol (AAL5SNAP) encapsulations:
•
Session Initiation Protocol (SIP)
•
Survivable Remote Site Telephony (SRST)
•
Traffic policer
•
VC bundling
•
VC shaping for VBR-NRT
•
Voice configuration
•
•
Voice over AAL5
•
VoATM
•
WRED
.
Supported Platforms
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
Determining Platform Support Through Cisco Feature Navigator
Cisco IOS software is packaged in feature sets that are supported on specific platforms. To get updated information regarding platform support for this feature, access Cisco Feature Navigator. Cisco Feature Navigator dynamically updates the list of supported platforms as new platform support is added for the feature.
Cisco Feature Navigator is a web-based tool that enables you to determine which Cisco IOS software images support a specific set of features and which features are supported in a specific Cisco IOS image. You can search by feature or release. Under the release section, you can compare releases side by side to display both the features unique to each software release and the features in common.
To access Cisco Feature Navigator, you must have an account on Cisco.com. If you have forgotten or lost your account information, send a blank e-mail to cco-locksmith@cisco.com. An automatic check will verify that your e-mail address is registered with Cisco.com. If the check is successful, account details with a new random password will be e-mailed to you. Qualified users can establish an account on Cisco.com by following the directions found at this URL:
Cisco Feature Navigator is updated regularly when major Cisco IOS software releases and technology releases occur. For the most current information, go to the Cisco Feature Navigator home page at the following URL:
Availability of Cisco IOS Software Images
Platform support for particular Cisco IOS software releases is dependent on the availability of the software images for those platforms. Software images for some platforms may be deferred, delayed, or changed without prior notice. For updated information about platform support and availability of software images for each Cisco IOS software release, refer to the online release notes or, if supported, Cisco Feature Navigator.
Supported Standards, MIBs, and RFCs
Standards
No new or modified standards are supported by these features.
MIBs
The following MIBs are supported:
•
•
•
•
•
•
•
•
•
•
To locate and download MIBs for selected platforms, Cisco IOS releases, and feature sets, use Cisco MIB Locator found at the following URL:
http://tools.cisco.com/ITDIT/MIBS/servlet/index
If Cisco MIB Locator does not support the MIB information that you need, you can also obtain a list of supported MIBs and download MIBs from the Cisco MIBs page at the following URL:
http://www.cisco.com/public/sw-center/netmgmt/cmtk/mibs.shtml
To access Cisco MIB Locator, you must have an account on Cisco.com. If you have forgotten or lost your account information, send a blank e-mail to cco-locksmith@cisco.com. An automatic check will verify that your e-mail address is registered with Cisco.com. If the check is successful, account details with a new random password will be e-mailed to you. Qualified users can establish an account on Cisco.com by following the directions found at this URL:
RFCs
No new or modified RFCs are supported by these features.
Prerequisites
To configure the voice and QoS features, you must first install and configure the ADSL WIC or G.SHDSL WIC on your Cisco 1700 series, Cisco 2600 series, and Cisco 3600 series. For information about installing and configuring the ADSL and G.SHDSL WICs, see the "ADSL and G.SHDSL WAN interface cards" topic in the Related Documents section.
Configuration Tasks
See the following sections to configure the Enhanced Voice and QoS features for ADSL and G.SHDSL on Cisco routers. Each task in the list is identified as either required or optional.
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
Configuring ATM CLP Bit Marking
To configure ATM CLP bit marking, use the following commands beginning in global configuration mode.
Step 1
Enables Cisco Express Forwarding (CEF).
Step 2
Creates a class map to be used for matching packets to a specified class and enters class map configuration mode. The class-map-name argument is the name of the class for the class map. The class name is used for both the class map and to configure policy for the class in the policy map.
Step 3
Specifies the numbered access list against whose contents packets are checked to determine whether they belong to the class. Refer to the Cisco IOS Quality of Service Solutions Configuration Guide for other match options.
Step 4
Exits class map configuration mode.
Step 5
Creates or modifies a policy map that can be attached to one or more interfaces to specify a service policy and enters policy map configuration mode. The policy-map-name argument is the name of the policy map.
Step 6
Router (config-pmap)# class nameSpecifies the name of a traffic class to classify traffic for the policy traffic and enters policy-map class configuration mode. The name argument should be the same as the class-map name in Step 2 of this configuration.
Step 7
Controls the cell loss priority (CLP) bit setting on Cisco routers when a policy map is configured (changes the setting for all packets that match the specified class from 0 to 1).
Step 8
Exits policy-map class configuration mode.
Step 9
Exits policy-map configuration mode.
Step 10
Configures an interface type and enters subinterface configuration mode.
The arguments and keywords are as follows:
•
•
•
•
•
•
Step 11
Creates an ATM permanent virtual circuit (PVC) or assigns a name to an ATM PVC and enters ATM VC configuration mode.
The arguments are as follows:
•
•
Note
Step 12
Attaches a policy map to an interface to be used as the service policy for that interface.
The arguments and keywords are as follows:
•
•
Verifying ATM CLP Bit Marking
The following show atm pvc command output from a Cisco 1721 router displays detailed information about the PVC. In this example, five packets are sent, with the CLP set to 1.
Router# show atm pvc 0/33ATM0.1: VCD: 1, VPI: 0, VCI: 33UBR, PeakRate: 2304AAL5-LLC/SNAP, etype:0x0, Flags: 0x2000C20, VCmode: 0x0OAM frequency: 0 second(s), OAM retry frequency: 1 second(s)OAM up retry count: 3, OAM down retry count: 5OAM END CC Activate retry count: 3, OAM END CC Deactivate retry count: 3OAM END CC retry frequency: 30 second(s),OAM SEGMENT CC Activate retry count: 3, OAM SEGMENT CC Deactivate retry count: 3OAM SEGMENT CC retry frequency: 30 second(s),OAM Loopback status: OAM DisabledOAM VC state: Not ManagedILMI VC state: Not ManagedInARP frequency: 15 minutes(s)InPkts: 5, OutPkts: 5, InBytes: 560, OutBytes: 560InPRoc: 5, OutPRoc: 5InFast: 0, OutFast: 0, InAS: 0, OutAS: 0InPktDrops: 0, OutPktDrops: 0/0/0 (holdq/outputq/total)CrcErrors: 0, SarTimeOuts: 0, OverSizedSDUs: 0, LengthViolation: 0, CPIErrors: 0Out CLP=1 Pkts: 5OAM cells received: 0F5 InEndloop: 0, F5 InSegloop: 0,F5 InEndcc: 0, F5 InSegcc: 0, F5 InAIS: 0, F5 InRDI: 0F4 InEndloop: 0, F4 InSegloop: 0, F4 InAIS: 0, F4 InRDI: 0OAM cells sent: 0F5 OutEndloop: 0, F5 OutSegloop: 0,F5 OutEndcc: 0, F5 OutSegcc: 0, F5 OutRDI: 0F4 OutEndloop: 0, F4 OutSegloop: 0, F4 OutRDI: 0OAM cell drops: 0Status: UPConfiguring the Clock Rate for ADSL and G.SHDSL WICs
To configure the clock between a WIC and the hosts that are used by the WIC, use the following commands beginning in global configuration mode.
Step 1
Configures an ATM interface type and enters interface configuration mode.
Step 2
Configures the clock rate between a WIC and the SCCs that are used by the WIC.
The keywords and arguments are as follows:
•
•
•
–
For Cisco 2600 and 3600 series routers, the minimum value for ADSL and G.SHDSL is 1 Mbps. The maximum value is 7 Mbps for mainboard slots and 5.3 Mbps for network modules. The default value for ADSL and G.SHDSL is 2.6 Mbps for both mainboard slots and network modules.
To make full use of the 2.3 Mbps bandwidth for VoATM non-switched trunk calls on G.SHDSL, you can change the 1 Mbps default value on Cisco 2600 series and Cisco 3600 series routers and configure the AAL2 clock rate as 2.6 Mbps.
It is recommended, however, that you keep the ADSL SCC clock rate for AAL2 at the default value of 1 Mbps because the upstream of ADSL cannot exceed 1 Mbps.
Note
–
For Cisco 2600 and 3600 series routers, the minimum value for ADSL and G.SHDSL is 1 Mbps. The maximum value is 7 Mbps for mainboard slots and 5.3 Mbps for network modules. The default value for ADSL and G.SHDSL is 2.6 Mbps for both mainboard slots and network modules.
Note
Step 3
or
Router (config-if)# no clock rate aal2Disables the clock setting for AAL5 or AAL2, respectively, and changes the clock rate to the default setting.
The other method for changing the AAL5 or AAL2 clock rate into the default rate is to configure the clock rate to the actual default settings.
Verifying the Clock Setting for ADSL and G.SHDSL WICs
To verify the clock rate setting for an ADSL WIC or G.SHDSL WIC on a Cisco 1700, Cisco 2600, or Cisco 3600 series router, use the show running-config or the show controllers atm command in EXEC mode.
Cisco 1700 Series Router
Router# show running-config interface atm0/0interface ATM0/0ip address 1.0.0.1 255.255.255.0no ip route-cacheload-interval 30clock rate aal2 4000000no atm ilmi-keepalivepvc 0/33!dsl equipment-type CPEdsl operating-mode GSHDSL symmetric annex Adsl linerate AUTOCisco 1700 Series Router
Router# show controllers atm0/0Interface: ATM0/0, Hardware: DSLSAR (with Globespan G.SHDSL module), State:upIDB: 82201E98 Instance: 8220364C reg_dslsar:68030000 wic_regs:68030080PHY Inst:822251DC Ser0Inst: 821FC328 Ser1Inst: 821FF41C us_bwidth:192Slot: 0 Unit: 0 Subunit: 0 pkt Size: 4528VCperVP: 256 max_vp: 256 max_vc: 65536 total vc: 1rct_size:65536 vpivcibit:16 connTblVCI:8 vpi_bits: 8vpvc_sel:3 enabled: 0 throttled: 0 cell drops:0Parallel reads to TCQ:0 tx count reset = 0, periodic safe start = 0Serial idb(AAL5) output_qcount:0 max:40Serial idb(RAW) output_qcount:0, max:40Sar ctrl queue: max depth = 9, current queue depth = 0, drops = 0, uruncnt = 0,total cnt = 153Serial idb tx count: AAL5: 0, RAW: 0, Drop count:AAL5: 0, RAW: 0SCC Clockrates:SCC-A = 8000000SCC-B = 4000000In the above example, SCC-A represents the SCC clock rate for AAL5 and SCC-B represents the SCC clock rate for AAL2.
Cisco 2600 Series Chassis WIC Slots
The following show controllers atm example from a Cisco 2621 router shows verification of the SCC clock rates for ATM interface 0/0 on mainboard slot 0 and ATM interface 0/1 on mainboard slot 1:
Router# show controllers atm 0/0Interface: ATM0/0, Hardware: DSLSAR (with Globespan G.SHDSL module), State: upIDB: 8295D918 Instance: 8295F0CC reg_dslsar:67000000 wic_regs: 67000080PHY Inst:82981024 Ser0Inst: 8294C2B4 Ser1Inst: 82954DD8 us_bwidth:2304Slot: 0 Unit: 0 Subunit: 0 pkt Size: 4528VCperVP: 256 max_vp: 256 max_vc: 65536 total vc: 2rct_size:65536 vpivcibit:16 connTblVCI:8 vpi_bits: 8vpvc_sel:3 enabled: 0 throttled: 0 cell drops: 0Parallel reads to TCQ:2 tx count reset = 0, periodic safe start = 0Serial idb(AAL5) output_qcount:0 max:40Serial idb(RAW) output_qcount:0, max:40Sar ctrl queue: max depth = 10, current queue depth = 0, drops = 0, urun cnt = 0, total cnt = 105Serial idb tx count: AAL5: 90277249, RAW: 105, Drop count:AAL5: 0, RAW: 0SCC Clockrates:SCC0 = 2600000 (ATM0/0)SCC1 = 2600000 (ATM0/1)SCC2 = 1000000 (ATM0/1)SCC3 = 1000000 (ATM0/0)In the above example, the ADSL WIC in slot 0 uses SCC0 and SCC3. The AAL5 and AAL2 SCC clock rate of the WICs are 2 Mbps and 4 Mbps, respectively. The second WIC in slot 1 uses SCC1 and SCC2 for AAL5 and AAL2.
Cisco 2600 Series Network Router
The SCC assignment on a network module is different. The following show controllers atm example is from ATM interface 1/0, which is on network module slot 0. The example is from a Cisco 2650XM router.
Router# show controllers atm1/0Interface: ATM0/0, Hardware: DSLSAR (with Globespan G.SHDSL module), State: upIDB: 8295D918 Instance: 8295F0CC reg_dslsar:67000000 wic_regs: 67000080PHY Inst:82981024 Ser0Inst: 8294C2B4 Ser1Inst: 82954DD8 us_bwidth:2304Slot: 0 Unit: 0 Subunit: 0 pkt Size: 4528VCperVP: 256 max_vp: 256 max_vc: 65536 total vc: 2rct_size:65536 vpivcibit:16 connTblVCI:8 vpi_bits: 8vpvc_sel:3 enabled: 0 throttled: 0 cell drops: 0Parallel reads to TCQ:2 tx count reset = 0, periodic safe start = 0Serial idb(AAL5) output_qcount:0 max:40Serial idb(RAW) output_qcount:0, max:40Sar ctrl queue: max depth = 10, current queue depth = 0, drops = 0, urun cnt = 0, total cnt = 105Serial idb tx count: AAL5: 90277249, RAW: 105, Drop count:AAL5: 0, RAW: 0SCC Clockrates:SCC0 = 2600000 (ATM0/0)SCC1 = 2600000 (ATM0/1)SCC2 = 1000000 (ATM0/1)SCC3 = 1000000 (ATM0/0)Troubleshooting the Clock Setting for ADSL and G.SHDSL WICs on Cisco 2600 Series and Cisco Series
The system limitation for Cisco 2600 and Cisco 3600 series routers is that the total SCC clock rate that can be configured for one or more WICs is 8 Mbps. The following troubleshooting tips for Cisco 2600 and Cisco 3600 routers explain situations for which warning and error messages can be received because of the 8 Mbps limitation.
Step 1
Router (config)# interface atm 0/0Router (config-if)# clock rate aal5 7000000%error: insuffcient clockrates, available (including current clock rate) = 4000000 bps%Clockrate configuration failedStep 2
1d20h: %DSLSAR-1-NO_SCC_CLK_ERR: ATM1/0: Interface is DOWN because the sum of the clock rate values for both the WICs in slots 0 and 1 exceeded maximum capacity. Please configure clock rates using clock rate command in interface mode such that the sum of clock rate on both the WICs does not exceed 8000000 bps. For a DSL wic, please include aal5 and aal2 clock rate values while calculating the total.If you add a second WIC, make sure that you reduce the clock rate of the existing DSL so that the combined clock rates do not exceed the maximum.
Step 3
Configuring cRTP over an ATM Link with ATM Encapsulation
To configure cRTP over an ATM link with ATM encapsulation, use the following commands beginning in global configuration mode.
Verifying cRTP Statistics
To display cRTP statistics, use the show ip rtp header-compression command as is shown in the following example:
Router# show ip rtp header-compressionRTP/UDP/IP header compression statistics:Interface Virtual-Template1:Rcvd: 0 total, 0 compressed, 0 errors, 0 status msgs0 dropped, 0 buffer copies, 0 buffer failuresSent: 0 total, 0 compressed, 0 status msgs0 bytes saved, 0 bytes sentConnect: 3 rx slots, 3 tx slots,0 long searches, 0 misses 0 collisions, 0 negative cache hitsInterface Virtual-Access4:Rcvd: 0 total, 0 compressed, 0 errors, 0 status msgs0 dropped, 0 buffer copies, 0 buffer failuresSent: 0 total, 0 compressed, 0 status msgs0 bytes saved, 0 bytes sentConnect: 3 rx slots, 3 tx slots,0 long searches, 0 misses 0 collisions, 0 negative cache hitsInterface Virtual-Access5:Rcvd: 7264 total, 7244 compressed, 0 errors, 0 status msgs0 dropped, 0 buffer copies, 0 buffer failuresSent: 7414 total, 7392 compressed, 0 status msgs280706 bytes saved, 164178 bytes sent2.70 efficiency improvement factorConnect: 3 rx slots, 3 tx slots,0 long searches, 2 misses 1 collisions, 0 negative cache hits99% hit ratio, five minute miss rate 0 misses/sec, 0 maxTo display the cRTP gain and to monitor the traffic flow on the actual interface, use the show interface atm command.
Router# show interface atm 0/0ATM0/0 is up, line protocol is upHardware is DSLSAR (with Globespan G.SHDSL module)MTU 4470 bytes, sub MTU 4470, BW 2304 Kbit, DLY 880 usec,reliability 255/255, txload 1/255, rxload 1/255Encapsulation ATM, loopback not setEncapsulation(s): AAL5 , PVC mode23 maximum active VCs, 256 VCs per VP, 1 current VCCsVC Auto Creation Disabled.VC idle disconnect time: 300 secondsLast input 00:11:57, output 00:00:00, output hang neverLast clearing of "show interface" counters neverInput queue: 0/75/0/0 (size/max/drops/flushes); Total output drops: 0Queueing strategy: None30 second input rate 10000 bits/sec, 50 packets/sec30 second output rate 13000 bits/sec, 50 packets/sec54153 packets input, 2586202 bytes, 0 no bufferReceived 0 broadcasts, 0 runts, 0 giants, 0 throttles5 input errors, 0 CRC, 0 frame, 0 overrun, 0 ignored, 0 abort38013 packets output, 2133672 bytes, 0 underruns0 output errors, 0 collisions, 0 interface resets0 output buffer failures, 0 output buffers swapped outConfiguring FRF.5
To configure FRF.5 for a one-to-one connection between two Frame Relay end users over an intermediate ATM network, use the following commands beginning in global configuration mode.
To configure FRF.5 for a many-to-one connection between two Frame Relay end users over an intermediate ATM network, use the following commands beginning in global configuration mode.
Verifying FRF.5
The following show command output is from a Cisco 1721 router. Use the show connection all or show connection id commands to check the state of the connection. Use the show frame-relay pvc command to verify the state of the Frame Relay PVC, and use the show atm pvc command to verify the state of the ATM PVC.
Router# show connection allID Name Segment 1 Segment 2 State========================================================================1 frf5 Serial0 100 ATM0 0/33 UPRouter# show connection id 1FR/ATM Network Interworking Connection: frf5Status - UPSegment 1 - Serial0 DLCI 100Segment 2 - ATM0 VPI 0 VCI 33Interworking Parameters -fr-sscs-dlci 1022de-bit map-clpclp-bit map-deRouter# show frame-relay pvc 100PVC Statistics for interface Serial0 (Frame Relay DCE)DLCI = 100, DLCI USAGE = FRF.5, PVC STATUS = ACTIVE, INTERFACE = Serial0input pkts 5 output pkts 5 in bytes 520out bytes 520 dropped pkts 0 in pkts dropped 0out pkts dropped 0 out bytes dropped 0in FECN pkts 0 in BECN pkts 0 out FECN pkts 0out BECN pkts 0 in DE pkts 0 out DE pkts 0out bcast pkts 0 out bcast bytes 05 minute input rate 0 bits/sec, 0 packets/sec5 minute output rate 0 bits/sec, 0 packets/secswitched pkts 5Detailed packet drop counters:no out intf 0 out intf down 0 no out PVC 0in PVC down 0 out PVC down 0 pkt too big 0shaping Q full 0 pkt above DE 0 policing drop 0pvc create time 00:25:00, last time pvc status changed 00:05:16Router# show atm pvc 0/33ATM0.1: VCD: 1, VPI: 0, VCI: 33UBR, PeakRate: 2304AAL5-FRATM, etype:0x3, Flags: 0xC22, VCmode: 0x0OAM frequency: 0 second(s), OAM retry frequency: 1 second(s)OAM up retry count: 3, OAM down retry count: 5OAM END CC Activate retry count: 3, OAM END CC Deactivate retry count: 3OAM END CC retry frequency: 30 second(s),OAM SEGMENT CC Activate retry count: 3, OAM SEGMENT CC Deactivate retry count: 3OAM SEGMENT CC retry frequency: 30 second(s),OAM Loopback status: OAM DisabledOAM VC state: Not ManagedILMI VC state: Not ManagedInARP DISABLEDInPkts: 5, OutPkts: 5, InBytes: 540, OutBytes: 540InPRoc: 0, OutPRoc: 0InFast: 5, OutFast: 5, InAS: 0, OutAS: 0InPktDrops: 0, OutPktDrops: 0/0/0 (holdq/outputq/total)CrcErrors: 0, SarTimeOuts: 0, OverSizedSDUs: 0, LengthViolation: 0, CPIErrors: 0Out CLP=1 Pkts: 0OAM cells received: 0F5 InEndloop: 0, F5 InSegloop: 0,F5 InEndcc: 0, F5 InSegcc: 0, F5 InAIS: 0, F5 InRDI: 0F4 InEndloop: 0, F4 InSegloop: 0, F4 InAIS: 0, F4 InRDI: 0OAM cells sent: 0F5 OutEndloop: 0, F5 OutSegloop: 0,F5 OutEndcc: 0, F5 OutSegcc: 0, F5 OutRDI: 0F4 OutEndloop: 0, F4 OutSegloop: 0, F4 OutRDI: 0OAM cell drops: 0Status: UPConfiguring FRF.8
To configure FRF.8, use the following commands beginning in global configuration mode.
Verifying FRF.8
The following show command output is from a Cisco 1721 router. Use the show connection all or show connection id commands to check the state of the connection. Use show frame-relay pvc command to verify the state of the Frame Relay PVC and use show atm pvc command to verify the state of the ATM PVC.
Router# show connection allID Name Segment 1 Segment 2 State========================================================================2 frf8 Serial0 100 ATM0 0/33 UPRouter# show connection id 2FR/ATM Service Interworking Connection: frf8Status - UPSegment 1 - Serial0 DLCI 100Segment 2 - ATM0 VPI 0 VCI 33Interworking Parameters -service translationefci-bit 0de-bit map-clpclp-bit map-deRouter# show frame-relay pvcPVC Statistics for interface Serial0 (Frame Relay DCE)Active Inactive Deleted StaticLocal 0 0 0 0Switched 1 0 0 0Unused 0 0 0 0DLCI = 100, DLCI USAGE = FRF.8, PVC STATUS = ACTIVE, INTERFACE = Serial0input pkts 5 output pkts 5 in bytes 540out bytes 520 dropped pkts 0 in pkts dropped 0out pkts dropped 0 out bytes dropped 0in FECN pkts 0 in BECN pkts 0 out FECN pkts 0out BECN pkts 0 in DE pkts 0 out DE pkts 0out bcast pkts 0 out bcast bytes 05 minute input rate 0 bits/sec, 0 packets/sec5 minute output rate 0 bits/sec, 0 packets/secswitched pkts 5Detailed packet drop counters:no out intf 0 out intf down 0 no out PVC 0in PVC down 0 out PVC down 0 pkt too big 0shaping Q full 0 pkt above DE 0 policing drop 0pvc create time 00:08:57, last time pvc status changed 00:08:20Router# show atm pvc 0/33ATM0.1: VCD: 1, VPI: 0, VCI: 33UBR, PeakRate: 2304AAL5-FRATMSRV, etype:0x15, Flags: 0xC23, VCmode: 0x0OAM frequency: 0 second(s), OAM retry frequency: 1 second(s)OAM up retry count: 3, OAM down retry count: 5OAM END CC Activate retry count: 3, OAM END CC Deactivate retry count: 3OAM END CC retry frequency: 30 second(s),OAM SEGMENT CC Activate retry count: 3, OAM SEGMENT CC Deactivate retry count: 3OAM SEGMENT CC retry frequency: 30 second(s),OAM Loopback status: OAM DisabledOAM VC state: Not ManagedILMI VC state: Not ManagedInARP DISABLEDInPkts: 5, OutPkts: 5, InBytes: 560, OutBytes: 560InPRoc: 0, OutPRoc: 0InFast: 5, OutFast: 5, InAS: 0, OutAS: 0InPktDrops: 0, OutPktDrops: 0/0/0 (holdq/outputq/total)CrcErrors: 0, SarTimeOuts: 0, OverSizedSDUs: 0, LengthViolation: 0, CPIErrors: 0Out CLP=1 Pkts: 0OAM cells received: 0F5 InEndloop: 0, F5 InSegloop: 0,F5 InEndcc: 0, F5 InSegcc: 0, F5 InAIS: 0, F5 InRDI: 0F4 InEndloop: 0, F4 InSegloop: 0, F4 InAIS: 0, F4 InRDI: 0OAM cells sent: 0F5 OutEndloop: 0, F5 OutSegloop: 0,F5 OutEndcc: 0, F5 OutSegcc: 0, F5 OutRDI: 0F4 OutEndloop: 0, F4 OutSegloop: 0, F4 OutRDI: 0OAM cell drops: 0Status: UPConfiguring MLP Bundling
To configure MLP bundling using a multilink interface, use the following commands beginning in global configuration mode.
Verifying MLP Bundling
To verify your MLP bundling configuration, use the following show commands:
Router# show ppp multilinkMultilink1, bundle name is 3660Bundle up for 00:00:17E, 1/255 load, 2 receive classes, 2 transmit classesReceive Class 0:1 lost fragments, 1 reordered, 0 unassigned0 discarded, 0 lost received0x3 received sequenceReceive Class 1:0 lost fragments, 0 reordered, 0 unassigned0 discarded, 0 lost received0x0 received sequenceTransmit Class 0:0x2 sent sequenceTransmit Class 1:0x0 sent sequenceMember links: 2 active, 5 inactive (max not set, min not set)Vi8, since 00:00:17 480 weight, 472 frag sizeVi9, since 00:00:17 480 weight, 472 frag sizeRouter# show interfaces multilink 1Multilink1 is up, line protocol is upHardware is multilink group interfaceInterface is unnumbered. Using address of Loopback0 (2.2.2.2)MTU 1500 bytes, BW 1280 Kbit, DLY 100000 usec,reliability 255/255, txload 1/255, rxload 1/255Encapsulation PPP, LCP Open, multilink OpenOpen: IPCP, loopback not setDTR is pulsed for 2 seconds on resetLast input 02:57:52, output never, output hang neverLast clearing of "show interface" counters 02:58:45Input queue: 0/75/0/0 (size/max/drops/flushes); Total output drops: 0Queueing strategy: weighted fairOutput queue: 0/1000/64/0 (size/max total/threshold/drops)Conversations 0/1/256 (active/max active/max total)Reserved Conversations 0/0 (allocated/max allocated)Available Bandwidth 860 kilobits/sec30 second input rate 0 bits/sec, 0 packets/sec30 second output rate 0 bits/sec, 0 packets/sec2 packets input, 28 bytes, 0 no bufferReceived 0 broadcasts, 0 runts, 0 giants, 0 throttles0 input errors, 0 CRC, 0 frame, 0 overrun, 0 ignored, 0 abort2 packets output, 24 bytes, 0 underruns0 output errors, 0 collisions, 1 interface resets0 output buffer failures, 0 output buffers swapped out0 carrier transitionsRouter# show interfaces atm 0/0ATM0/0 is up, line protocol is upHardware is DSLSAR (with Alcatel ADSL Module)MTU 4470 bytes, sub MTU 4470, BW 800 Kbit, DLY 2560 usec,reliability 255/255, txload 1/255, rxload 1/255Encapsulation ATM, loopback not setEncapsulation(s): AAL5 AAL2, PVC mode23 maximum active VCs, 256 VCs per VP, 1 current VCCsVC Auto Creation Disabled.VC idle disconnect time: 300 secondsLast input never, output 00:00:01, output hang neverLast clearing of "show interface" counters neverInput queue: 0/75/0/0 (size/max/drops/flushes); Total output drops: 0Queueing strategy: None30 second input rate 0 bits/sec, 0 packets/sec30 second output rate 0 bits/sec, 0 packets/sec2188 packets input, 30640 bytes, 0 no bufferReceived 0 broadcasts, 0 runts, 0 giants, 0 throttles4 input errors, 0 CRC, 0 frame, 0 overrun, 0 ignored, 0 abort2194 packets output, 48368 bytes, 0 underruns0 output errors, 0 collisions, 0 interface resets0 output buffer failures, 0 output buffers swapped outRouter# show usersLine User Host(s) Idle Location* 0 con 0 idle 00:00:00Interface User Mode Idle Peer AddressVi4 3660 PPPoATM 00:09:25Vi5 3660 PPPoATM 00:09:23Mu1 3660 Sync PPP 00:09:25 2.2.2.2Router# show policy-map interface mul 1Multilink1Service-policy output: CISCOClass-map: VOICE (match-all)11117 packets, 234235 bytes30 second offered rate 25000 bps, drop rate 0 bpsMatch: access-group 100QueueingStrict PriorityOutput Queue: Conversation 264Bandwidth 100 (kbps) Burst 2500 (Bytes)(pkts matched/bytes matched) 17/748(total drops/bytes drops) 0/0Class-map: class-default (match-any)234453438 packets, 64564574574bytes30 second offered rate 645000 bps, drop rate 12000 bpsMatch: anyRouter# show dsl interface atm 0/0Alcatel 20150 chipset informationATU-R (DS) ATU-C (US)Modem Status: Showtime (DMTDSL_SHOWTIME)DSL Mode: ITU G.992.1 (G.DMT)ITU STD NUM: 0x01 0x1Vendor ID: 'ALCB' 'GSPN'Vendor Specific: 0x0000 0x0002Vendor Country: 0x00 0x00Capacity Used: 80% 90%Noise Margin: 11.5 dB 9.0 dBOutput Power: 8.0 dBm 12.0 dBmAttenuation: 0.0 dB 4.0 dBDefect Status: None NoneLast Fail Code: Handshake or init message invalid or had bad CRCSelftest Result: 0x00Subfunction: 0x15Interrupts: 1333 (0 spurious)PHY Access Err: 0Activations: 1Init FW: embeddedOperation FW: embeddedSW Version: 3.8129FW Version: 0x1A04Interleave Fast Interleave FastSpeed (kbps): 7616 0 800 0Reed-Solomon EC: 4 0 1326 0CRC Errors: 0 0 1 0Header Errors: 0 0 0 0Bit Errors: 0 0BER Valid sec: 0 0BER Invalid sec: 0 0DMT Bits Per Bin00: 0 0 0 0 0 0 0 6 7 8 9 9 B B C C10: B B C C B B A 9 9 9 9 8 8 9 0 020: 0 0 0 0 0 0 3 4 4 5 6 6 7 7 7 830: 8 8 9 9 9 9 A A A A A A A A 9 A40: 0 B B B B B B B B B B B B B B B50: B B B B B B B B B B B B B 8 B 260: B B B B B B B B B B B B B B B B70: B B B B B B 8 B B B B B 9 B B B80: B B B B B B B B B B B B B B B B90: B B B B B B B B B B B 9 B B B BA0: B B B B B B B B B B B B B B B BB0: B B B B B B A B B A 9 A A A A AC0: A A A A A A A A A A A A A A A AD0: A A A A A A A A A 9 A A A A A AE0: A A A A A A 9 A 9 9 8 8 7 5 5 5F0: 4 3 2 0 0 0 0 0 0 0 0 0 0 0 0 0DSL: Training log buffer capability is not enabledTroubleshooting Tips for MLP Bundling
To troubleshoot your MLP bundling configuration, do the following:
Step 1
•
•
Step 2
•
Step 3
Router# debug ppp negotiation1d05h: ppp11 LCP: State is Open1d05h: ppp11 PPP: Phase is FORWARDING, Attempting Forward1d05h: Vi7 PPP: Phase is DOWN, Setup1d05h: Vi7 PPP: Phase is DOWN, Setup1d05h: ppp11 LCP: I TERMREQ [Open] id 2 len 41d05h: ppp11 LCP: O TERMACK [Open] id 2 len 41d05h: ppp11 PPP: Phase is TERMINATING1d05h: ppp13 PPP: Treating connection as a dedicated line1d05h: ppp13 PPP: Phase is ESTABLISHING, Active Open1d05h: ppp13 LCP: O CONFREQ [Closed] id 1 len 291d05h: ppp13 LCP: MagicNumber 0x0FD2BAA3 (0x05060FD2BAA3)1d05h: ppp13 LCP: MRRU 1524 (0x110405F4)1d05h: ppp13 LCP: EndpointDisc 1 2600 (0x130B0132363531584D2D31)1d05h: ppp13 LCP: MultilinkHdrFmt seq long classes 2 (0x1B040202)1d05h: ppp14 PPP: Treating connection as a dedicated line1d05h: ppp14 PPP: Phase is ESTABLISHING, Active Open1d05h: ppp14 LCP: O CONFREQ [Closed] id 1 len 291d05h: ppp14 LCP: MagicNumber 0x0FD2BB2D (0x05060FD2BB2D)1d05h: ppp14 LCP: MRRU 1524 (0x110405F4)1d05h: ppp14 LCP: EndpointDisc 1 2600 (0x130B0132363531584D2D31)1d05h: ppp14 LCP: MultilinkHdrFmt seq long classes 2 (0x1B040202)1d05h: ppp13 LCP: TIMEout: State REQsent1d05h: ppp13 LCP: O CONFREQ [REQsent] id 2 len 291d05h: ppp13 LCP: MagicNumber 0x0FD2BAA3 (0x05060FD2BAA3)1d05h: ppp13 LCP: MRRU 1524 (0x110405F4)1d05h: ppp13 LCP: EndpointDisc 1 2600 (0x130B0132363531584D2D31)1d05h: ppp13 LCP: MultilinkHdrFmt seq long classes 2 (0x1B040202)1d05h: ppp14 LCP: TIMEout: State REQsent1d05h: ppp14 LCP: O CONFREQ [REQsent] id 2 len 291d05h: ppp14 LCP: MagicNumber 0x0FD2BB2D (0x05060FD2BB2D)1d05h: ppp14 LCP: MRRU 1524 (0x110405F4)1d05h: ppp14 LCP: EndpointDisc 1 2600 (0x130B0132363531584D2D31)1d05h: ppp14 LCP: MultilinkHdrFmt seq long classes 2 (0x1B040202)1d05h: ppp13 LCP: TIMEout: State REQsent1d05h: ppp13 LCP: O CONFREQ [REQsent] id 3 len 291d05h: ppp13 LCP: MagicNumber 0x0FD2BAA3 (0x05060FD2BAA3)1d05h: ppp13 LCP: MRRU 1524 (0x110405F4)1d05h: ppp13 LCP: EndpointDisc 1 2600 (0x130B0132363531584D2D31)1d05h: ppp13 LCP: MultilinkHdrFmt seq long classes 2 (0x1B040202)1d05h: ppp14 LCP: TIMEout: State REQsent1d05h: ppp14 LCP: O CONFREQ [REQsent] id 3 len 291d05h: ppp14 LCP: MagicNumber 0x0FD2BB2D (0x05060FD2BB2D)1d05h: ppp14 LCP: MRRU 1524 (0x110405F4)1d05h: ppp14 LCP: EndpointDisc 1 2600 (0x130B0132363531584D2D31)1d05h: ppp14 LCP: MultilinkHdrFmt seq long classes 2 (0x1B040202)1d05h: ppp13 LCP: TIMEout: State REQsent1d05h: ppp13 LCP: O CONFREQ [REQsent] id 4 len 291d05h: ppp13 LCP: MagicNumber 0x0FD2BAA3 (0x05060FD2BAA3)1d05h: ppp13 LCP: MRRU 1524 (0x110405F4)1d05h: ppp13 LCP: EndpointDisc 1 2600 (0x130B0132363531584D2D31)1d05h: ppp13 LCP: MultilinkHdrFmt seq long classes 2 (0x1B040202)1d05h: ppp14 LCP: TIMEout: State REQsent1d05h: ppp14 LCP: O CONFREQ [REQsent] id 4 len 291d05h: ppp14 LCP: MagicNumber 0x0FD2BB2D (0x05060FD2BB2D)1d05h: ppp14 LCP: MRRU 1524 (0x110405F4)1d05h: ppp14 LCP: EndpointDisc 1 2600 (0x130B0132363531584D2D31)1d05h: ppp14 LCP: MultilinkHdrFmt seq long classes 2 (0x1B040202)1d05h: ppp13 LCP: I CONFREQ [REQsent] id 1 len 291d05h: ppp13 LCP: MagicNumber 0x36EBFBB7 (0x050636EBFBB7)1d05h: ppp13 LCP: MRRU 1524 (0x110405F4)1d05h: ppp13 LCP: EndpointDisc 1 3660 (0x130B01333636302D746F70)1d05h: ppp13 LCP: MultilinkHdrFmt seq long classes 2 (0x1B040202)1d05h: ppp13 LCP: O CONFACK [REQsent] id 1 len 291d05h: ppp13 LCP: MagicNumber 0x36EBFBB7 (0x050636EBFBB7)1d05h: ppp13 LCP: MRRU 1524 (0x110405F4)1d05h: ppp13 LCP: EndpointDisc 1 3660 (0x130B01333636302D746F70)1d05h: ppp13 LCP: MultilinkHdrFmt seq long classes 2 (0x1B040202)1d05h: ppp14 LCP: I CONFREQ [REQsent] id 1 len 291d05h: ppp14 LCP: MagicNumber 0x36EBFBB8 (0x050636EBFBB8)1d05h: ppp14 LCP: MRRU 1524 (0x110405F4)1d05h: ppp14 LCP: EndpointDisc 1 3660 (0x130B01333636302D746F70)1d05h: ppp14 LCP: MultilinkHdrFmt seq long classes 2 (0x1B040202)1d05h: ppp14 LCP: O CONFACK [REQsent] id 1 len 291d05h: ppp14 LCP: MagicNumber 0x36EBFBB8 (0x050636EBFBB8)1d05h: ppp14 LCP: MRRU 1524 (0x110405F4)1d05h: ppp14 LCP: EndpointDisc 1 3660 (0x130B01333636302D746F70)1d05h: ppp14 LCP: MultilinkHdrFmt seq long classes 2 (0x1B040202)1d05h: ppp13 LCP: TIMEout: State ACKsent1d05h: ppp13 LCP: O CONFREQ [ACKsent] id 5 len 291d05h: ppp13 LCP: MagicNumber 0x0FD2BAA3 (0x05060FD2BAA3)1d05h: ppp13 LCP: MRRU 1524 (0x110405F4)1d05h: ppp13 LCP: EndpointDisc 1 2600 (0x130B0132363531584D2D31)1d05h: ppp13 LCP: MultilinkHdrFmt seq long classes 2 (0x1B040202)1d05h: ppp13 LCP: I CONFACK [ACKsent] id 5 len 291d05h: ppp13 LCP: MagicNumber 0x0FD2BAA3 (0x05060FD2BAA3)1d05h: ppp13 LCP: MRRU 1524 (0x110405F4)1d05h: ppp13 LCP: EndpointDisc 1 2600 (0x130B0132363531584D2D31)1d05h: ppp13 LCP: MultilinkHdrFmt seq long classes 2 (0x1B040202)1d05h: ppp13 LCP: State is Open1d05h: ppp13 PPP: Phase is FORWARDING, Attempting Forward1d05h: Vi8 PPP: Phase is DOWN, Setup1d05h: Vi8 PPP: Phase is DOWN, Setup1d05h: ppp13 PPP MLP: Queue packet code[192] id[0]1d05h: %LINK-3-UPDOWN: Interface Virtual-Access8, changed state to up1d05h: Vi8 PPP: Phase is ESTABLISHING, Finish LCP1d05h: Vi8 PPP: Phase is VIRTUALIZED1d05h: Mu1 MLP: Added first link Vi8 to bundle 36601d05h: Vi8 PPP: Process pending packets1d05h: Vi8 MLP: Redirect packet to MLP1d05h: %LINK-3-UPDOWN: Interface Multilink1, changed state to up1d05h: Mu1 PPP: Phase is UP1d05h: Mu1 IPCP: O CONFREQ [Closed] id 2 len 101d05h: Mu1 IPCP: Address 2.2.2.2 (0x030602020202)1d05h: Mu1 PPP: Process pending packets1d05h: Mu1 PPP: Process pending packets1d05h: Mu1 PPP: Treating connection as a dedicated line1d05h: Mu1 IPCP: I CONFACK [REQsent] id 2 len 101d05h: Mu1 IPCP: Address 2.2.2.2 (0x030602020202)1d05h: ppp14 LCP: TIMEout: State ACKsent1d05h: ppp14 LCP: O CONFREQ [ACKsent] id 5 len 291d05h: ppp14 LCP: MagicNumber 0x0FD2BB2D (0x05060FD2BB2D)1d05h: ppp14 LCP: MRRU 1524 (0x110405F4)1d05h: ppp14 LCP: EndpointDisc 1 2600 (0x130B0132363531584D2D31)1d05h: ppp14 LCP: MultilinkHdrFmt seq long classes 2 (0x1B040202)1d05h: ppp14 LCP: I CONFACK [ACKsent] id 5 len 291d05h: ppp14 LCP: MagicNumber 0x0FD2BB2D (0x05060FD2BB2D)1d05h: ppp14 LCP: MRRU 1524 (0x110405F4)1d05h: ppp14 LCP: EndpointDisc 1 2600 (0x130B0132363531584D2D31)1d05h: ppp14 LCP: MultilinkHdrFmt seq long classes 2 (0x1B040202)1d05h: ppp14 LCP: State is Open1d05h: ppp14 PPP: Phase is FORWARDING, Attempting Forward1d05h: Vi9 PPP: Phase is DOWN, Setup1d05h: Vi9 PPP: Phase is DOWN, Setup1d05h: %LINK-3-UPDOWN: Interface Virtual-Access9, changed state to up1d05h: Vi9 PPP: Phase is ESTABLISHING, Finish LCP1d05h: Vi9 PPP: Phase is VIRTUALIZED1d05h: Mu1 MLP: Added link Vi9 to bundle 36601d05h: Vi9 PPP: Process pending packets1d05h: %LINEPROTO-5-UPDOWN: Line protocol on Interface Virtual-Access8, changed state to up1d05h: %LINEPROTO-5-UPDOWN: Line protocol on Interface Multilink1, changed state to up1d05h: %LINEPROTO-5-UPDOWN: Line protocol on Interface Virtual-Access9, changed state to up1d05h: Mu1 IPCP: I CONFREQ [ACKrcvd] id 8 len 101d05h: Mu1 IPCP: Address 2.2.2.3 (0x030602020203)1d05h: Mu1 AAA/AUTHOR/IPCP: Start. Her address 2.2.2.3, we want 0.0.0.01d05h: Mu1 AAA/AUTHOR/IPCP: Reject 2.2.2.3, using 0.0.0.01d05h: Mu1 AAA/AUTHOR/IPCP: Done. Her address 2.2.2.3, we want 0.0.0.01d05h: Mu1 IPCP: O CONFACK [ACKrcvd] id 8 len 101d05h: Mu1 IPCP: Address 2.2.2.3 (0x030602020203)1d05h: Mu1 IPCP: State is Open1d05h: Mu1 IPCP: Install route to 2.2.2.31d05h: Mu1 IPCP: Add link info for cef entry 2.2.2.3Step 4
Router# debug ppp authentication1d06h: ppp295 PPP: Treating connection as a dedicated line1d06h: ppp295 PPP: Authorization required1d06h: ppp296 PPP: Treating connection as a dedicated line1d06h: ppp296 PPP: Authorization required1d06h: ppp295 CHAP: O CHALLENGE id 1 len 29 from "3660"1d06h: ppp295 CHAP: I CHALLENGE id 1 len 29 from "2600"1d06h: ppp295 CHAP: Using hostname from unknown source1d06h: ppp295 CHAP: Using password from AAA1d06h: ppp295 CHAP: O RESPONSE id 1 len 29 from "3660"1d06h: ppp295 CHAP: I RESPONSE id 1 len 29 from "2600"1d06h: ppp295 PPP: Sent CHAP LOGIN Request1d06h: ppp295 PPP: Received LOGIN Response PASS1d06h: %LINK-3-UPDOWN: Interface Virtual-Access4, changed state to up1d06h: Vi4 CHAP: O SUCCESS id 1 len 41d06h: Vi4 CHAP: I SUCCESS id 1 len 41d06h: %LINK-3-UPDOWN: Interface Multilink1, changed state to up1d06h: Mu1 PPP: Treating connection as a dedicated line1d06h: %LINEPROTO-5-UPDOWN: Line protocol on Interface Virtual-Access4, changed state to up1d06h: %LINEPROTO-5-UPDOWN: Line protocol on Interface Multilink1, changed state to up1d06h: ppp296 CHAP: O CHALLENGE id 1 len 29 from "3660" ç1d06h: ppp296 CHAP: I CHALLENGE id 1 len 29 from "2600" ç1d06h: ppp296 CHAP: Using hostname from unknown source1d06h: ppp296 CHAP: Using password from AAA1d06h: ppp296 CHAP: O RESPONSE id 1 len 29 from "3660"1d06h: ppp296 CHAP: I RESPONSE id 1 len 29 from "2600"1d06h: ppp296 PPP: Sent CHAP LOGIN Request1d06h: ppp296 PPP: Received LOGIN Response PASS ç1d06h: %LINK-3-UPDOWN: Interface Virtual-Access5, changed state to up1d06h: Vi5 CHAP: O SUCCESS id 1 len 41d06h: Vi5 CHAP: I SUCCESS id 1 len 41d06h: %LINEPROTO-5-UPDOWN: Line protocol on Interface Virtual-Access5, changed state to upStep 5
Router# debug ppp multilink events1d05h: %LINK-3-UPDOWN: Interface Virtual-Access8, changed state to up1d05h: %LINK-3-UPDOWN: Interface Virtual-Access9, changed state to up1d05h: Vi8 MLP: Request add link to bundle1d05h: Vi9 MLP: Request add link to bundle1d05h: Vi8 MLP: Adding link to bundle1d05h: Mu1 MLP: Added first link Vi8 to bundle 3660 1d05h: Vi9 MLP: Adding link to bundle1d05h: Mu1 MLP: Added link Vi9 to bundle 36601d05h: %LINK-3-UPDOWN: Interface Multilink1, changed state to up1d05h: %LINEPROTO-5-UPDOWN: Line protocol on Interface Virtual-Access8, changed state to up1d05h: %LINEPROTO-5-UPDOWN: Line protocol on Interface Virtual-Access9, changed state to up1d05h: %LINEPROTO-5-UPDOWN: Line protocol on Interface Multilink1, changed st
Configuring the Tx Ring Limit
To configure the tx ring limit, use the following commands beginning in global configuration mode.
Verifying the Tx Ring Limit
The following output example is for a tx ring limit over ADSL configuration:
Router# show running-configinterface ATM0/0no ip addressload-interval 30no atm ilmi-keepalivepvc 1/100vbr-rt 1500 1500tx-ring-limit 3protocol ppp Virtual-Template1!dsl equipment-type CPEdsl operating-mode GSHDSL symmetric annex Adsl linerate AUTOConfiguration Examples
This section provides the following configuration examples for ADSL and G.SHDSL:
•
•
•
•
ATM CLP Bit Marking over G.SHDSL Example
The following output is from a Cisco 1721 router. In this example, all output packets that have an IP precedence value of 0 are sent with the CLP set to 1.
Note
•
ip cef!class-map match-all PREC0match ip precedence 0!policy-map ATM_CLPclass PREC0set atm-clp!interface ATM0no ip addressno atm ilmi-keepalivedsl equipment-type CPEdsl operating-mode GSHDSL symmetric annex Adsl linerate AUTO!interface ATM0.1 point-to-pointip address 10.0.0.1 255.255.255.0pvc 0/33service-policy output ATM_CLPClock Rate for ADSL and G.SHDSL WICs Example
The following example from a Cisco 1760 router shows that the clock rate on the AAL5 channel is set to the minimum value of 4 Mbps on interface ATM 0/0:
interface atm 0/0clock rate aal5 4000000The following example from a Cisco 1760 router shows that the clock rate on the AAL2 channel is set to the value of 5.3 Mbps on interface ATM 1/0:
interface atm 1/0clock rate aal2 5300000The following example from a Cisco 2621 mainboard module shows that the clock rate on the AAL5 channel is set to the maximum value of 7 Mbps on interface ATM 0/0:
interface atm 0/0clock rate aal5 7000000The following example from a Cisco 2621 network module shows that the clock rate on the AAL5 channel is set to the maximum value of 5.3 Mbps on interface ATM 1/0:
interface atm 1/0clock rate aal5 5300000cRTP over an ATM Link with PPP Encapsulation Example
The following example shows that cRTP has been configured using Virtual Template over ATM:
ip cefclass-map match-all voice-trafficmatch access-group 102class-map match-all voice-signallingmatch access-group 103!policy-map VOICE-POLICYclass voice-trafficpriority 48class voice-signallingbandwidth 8class class-defaultfair-queue!interface Loopback0ip address 192.168.1.2 255.255.255.0!interface ATM0/0no ip addressload-interval 30no atm ilmi-keepalivepvc 1/100vbr-rt 1500 1500tx-ring-limit 3protocol ppp Virtual-Template1!dsl equipment-type CPEdsl operating-mode GSHDSL symmetric annex Adsl linerate AUTO!interface Virtual-Template1ip unnumbered Loopback0ip tcp header-compression iphc-formatservice-policy output VOICE-POLICYppp multilinkppp multilink fragment-delay 3ppp multilink interleaveip rtp header-compression iphc-formatip rtp compression-connections 3!access-list 102 permit udp any any range 16384 37276access-list 103 permit tcp any eq 1720 anyaccess-list 103 permit tcp any any eq 1720!voice-port 1/0/0!voice-port 1/0/1!dial-peer voice 1 potsdestination-pattern 7...port 1/0/0!dial-peer voice 2 voipdestination-pattern 8...session target ipv4:192.168.1.1dtmf-relay cisco-rtpip qos dscp cs5 mediaip qos dscp cs5 signalingno vadFRF.5 over G.SHDSL Example
The following output is from a Cisco 1721 router. This example shows how to create an FRF.5 one-to-one connection using the the connect command with the network-interworking keyword.
frame-relay switching!interface ATM0no ip addressno atm ilmi-keepalivedsl equipment-type CPEdsl operating-mode GSHDSL symmetric annex Adsl linerate AUTO!interface ATM0.1 point-to-pointpvc 0/33encapsulation aal5mux frame-relay!interface Serial0no ip addressencapsulation frame-relay IETFclockrate 2000000frame-relay interface-dlci 100 switchedframe-relay intf-type dce!connect frf5 Serial0 100 ATM0 0/33 network-interworking!The following example shows how to create an FRF.5 many-to-one connection.
vc-group groupASerial0 100 100Serial0 200 200Serial0 300 300Serial0 400 400!interface ATM0no ip addressno atm ilmi-keepalivepvc 0/33encapsulation aal5mux frame-relay!dsl equipment-type CPEdsl operating-mode GSHDSL symmetric annex Adsl linerate AUTO!connect frf5-v vc-group GroupA ATM0 0/33
Note
FRF.8 over G.SHDSL Example
The following output is from a Cisco 1721 router. This example shows how to create an FRF.8 connection using the the connect command with the service-interworking keyword.
frame-relay switching!interface ATM0no ip addressno atm ilmi-keepalivedsl equipment-type CPEdsl operating-mode GSHDSL symmetric annex Adsl linerate AUTO!interface ATM0.1 point-to-pointpvc 0/33encapsulation aal5mux fr-atm-srv!interface Serial0no ip addressencapsulation frame-relay IETFclockrate 2000000frame-relay interface-dlci 100 switchedframe-relay intf-type dce!ip classlessno ip http server!connect frf8 Serial0 100 ATM0 0/33 service-interworking
Note
MLP Bundling Example
The following output examples show how MLP DSL links can be bundled using a multilink interface. The configurations were created using devices in a specific laboratory environment. All of the devices started with a cleared (default) configuration. If you are working in a live network situation, make sure that you understand the potential impact of all commands before using them (refer to the command references for Cisco IOS Release 12.2).
Note
The following example was configured on a Cisco 2600 router equipped with two xDSL WICs.
ip subnet-zeroip cef!no ip domain lookup!class-map match-all VOICEmatch access-group 100!policy-map greenclass VOICEpriority 100!interface Loopback0ip address 10.2.2.2 255.255.255.0!interface Multilink1ip unnumbered Loopback0load-interval 30service-policy output greenip nat outsideno cdp enableppp multilinkppp multilink fragment-delay 6ppp multilink interleavemultilink-group 1!interface ATM0/0no ip addressload-interval 30no atm ilmi-keepalivedsl operating-mode auto!interface ATM0/0.1 point-to-pointpvc 203/202vbr-rt 640 640tx-ring-limit 3protocol ppp Virtual-Template1!interface FastEthernet0/0ip address 10.3.202.48 255.0.0.0load-interval 30duplex autospeed autono cdp enable!interface ATM0/1no ip addressload-interval 30no atm ilmi-keepalivedsl operating-mode auto!interface ATM0/1.1 point-to-pointpvc 5/201vbr-rt 640 640tx-ring-limit 3protocol ppp Virtual-Template1!interface FastEthernet0/1description ip address 10.6.6.6 255.0.0.0mac-address 0000.0000.0003ip address 10.1.1.30 255.255.255.0load-interval 30duplex autospeed autono cdp enable!interface Virtual-Template1no ip addressload-interval 30ppp authentication chap papppp multilinkppp multilink multiclassmultilink-group 1!ip classlessip route 10.1.1.0 255.255.255.0 2.2.2.3ip route 10.1.1.1 255.255.255.255 2.2.2.3ip route 192.168.254.254 255.255.255.255 1.3.0.1no ip http serverip pim bidir-enable!access-list 100 permit udp any any precedence criticalaccess-list 100 permit tcp any any eq 1720access-list 100 permit tcp any eq 1720 anyno cdp run!snmp-server managercall rsvp-sync!voice-port 1/1/0!voice-port 1/1/1!mgcp profile default!dial-peer cor custom!dial-peer voice 101 voipincoming called-number 10.....destination-pattern 200....session target ipv4:2.2.2.3ip qos dscp cs5 mediaip qos dscp cs5 signalingno vad!dial-peer voice 200 potsdestination-pattern 100....port 1/1/0prefix 200!alias exec c conf talias exec s sh run!line con 0exec-timeout 0 0privilege level 15line aux 0line vty 0 4loginline vty 5 15loginThe following example was configured on a Cisco 3660 or Cisco 7206 router:
ip subnet-zeroip cef!no ip domain lookup!class-map match-all VOICEmatch access-group 100!policy-map PURPLEclass VOICEpriority 100!voice call carrier capacity active!fax interface-type fax-mailmta receive maximum-recipients 0!interface Loopback0ip address 10.2.2.3 255.255.255.0!interface Multilink1ip unnumbered Loopback0load-interval 30service-policy output PURPLEno cdp enableppp multilinkppp multilink fragment-delay 6ppp multilink interleavemultilink-group 1!interface FastEthernet0/0mac-address 0000.0000.0004ip address 10.3.202.89 255.0.0.0load-interval 30duplex autospeed autono cdp enable!interface FastEthernet0/1mac-address 0000.0000.0004ip address 10.1.1.20 255.255.255.0load-interval 30no keepaliveduplex autospeed autono cdp enable!interface ATM2/0no ip addressload-interval 30atm clock INTERNALno atm ilmi-keepalive!interface ATM2/0.1 point-to-pointpvc 203/202vbr-rt 640 640tx-ring-limit 3protocol ppp Virtual-Template1!interface ATM2/0.2 point-to-pointpvc 5/201vbr-rt 640 640tx-ring-limit 3protocol ppp Virtual-Template1!interface Virtual-Template1no ip addressload-interval 30ppp authentication chap papppp multilinkppp multilink multiclassmultilink-group 1!ip classlessip route 10.1.1.0 255.255.255.0 2.2.2.2ip route 10.1.1.1 255.255.255.255 2.2.2.2ip route 192.168.254.254 255.255.255.255 1.3.0.1ip http serverip pim bidir-enable!access-list 100 permit udp any any precedence criticalaccess-list 100 permit tcp any any eq 1720access-list 100 permit tcp any eq 1720 anyno cdp run!call rsvp-sync!voice-port 4/1/0!voice-port 4/1/1!mgcp profile default!dial-peer cor customdial-peer voice 101 voipincoming called-number 200....destination-pattern 10.....session target ipv4:2.2.2.2ip qos dscp cs5 mediaip qos dscp cs5 signalingno vad!dial-peer voice 200 potsdestination-pattern 200....port 4/1/0prefix 200!alias exec c conf talias exec s sh run!line con 0exec-timeout 0 0privilege level 15line aux 0line vty 0 4password greenloginTx Ring-Limit Tuning over ADSL Example
The following output is from a Cisco 1751 router. The tx ring limit is configured on an ATM PVC interface.
class-map match-all VOIPmatch ip dscp 32class-map CRITICALmatch access-group 100!policy-map 1751_ADSLclass CRITICALpriority 48class VOIPbandwidth 64set ip precedence 6!interface Loopback1ip address 10.0.0.10 255.255.255.252!interface ATM0/0no ip addressno atm ilmi-keepalive!interface ATM0/0.1pvc 0/33vbr-rt 320 320 30tx-ring-limit 3protocol ppp Virtual-Template1!interface Virtual-Template1bandwidth 320ip unnumbered Loopback1ip mroute-cacheservice-policy output 1751_ADSLppp multilinkppp multilink fragment-delay 4ppp multilink interleaveThe following output is from a Cisco 2600 router that is configured for tx ring-limit tuning:
voice-card 1dspfarm!ip subnet-zero!ip cef!class-map match-all VOICE-CLASSmatch access-group 100!policy-map SERVICE-PACK-640class VOICE-CLASSpriority 160!controller T1 1/0framing esflinecode b8zsds0-group 0 timeslots 1-24 type e&m-wink-start!controller T1 1/1framing sflinecode ami!interface FastEthernet0/0ip address 10.3.214.50 255.255.0.0duplex autospeed auto!interface ATM0/1no ip addressload-interval 30atm vc-per-vp 256no atm ilmi-keepaliveatm voice aal2 aggregate-svc upspeed-number 0dsl equipment-type CPEdsl operating-mode GSHDSL symmetric annex Adsl linerate AUTO!interface ATM0/1.1 point-to-pointip address 192.168.1.2 255.255.255.0pvc 11/201protocol ip 192.168.1.1 broadcastvbr-nrt 640 640tx-ring-limit 3oam-pvc manageservice-policy output SERVICE-PACK-640!interface FastEthernet0/1ip address 10.10.11.1 255.255.255.0load-interval 30duplex autospeed auto!ip classlessip route 10.10.11.254 255.255.255.255 192.168.1.1ip route 192.168.254.254 255.255.255.255 1.3.0.1ip http serverip pim bidir-enable!ip director cache time 60access-list 100 permit udp any any precedence critical!snmp-server managercall rsvp-sync!voice-port 1/0:0!mgcp profile default!dial-peer cor custom!dial-peer voice 1 potsdestination-pattern 7...!dial-peer voice 2 voippattern 8...session target ipv4:192.168.1.1ip qos dscp cs5 mediaip qos dscp cs5 signalingno vad!alias exec s sh runalias exec c conf t!line con 0exec-timeout 0 0privilege level 15line aux 0line vty 0 4loginline vty 5 15loginCommand Reference
This section documents new and modified commands. All other commands used with this feature are documented in the Cisco IOS Release 12.2 command reference publications.
New
Modified
clock rate (interface ATM)
To configure the clock rate between a wide-area network interface card (WIC) and the serial communication controllers (SCCs) that are used by the WIC, use the clock rate command in interface ATM mode. To disable the clock rate setting, use the no form of this command.
clock rate [aal2 | aal5] clock-rate-value
no clock rate [aal2 | aal5] clock-rate-value
Syntax Description
aal2
(Optional) AAL2.
aal5
(Optional) ATM adaptation layer 5 (AAL5).
clock-rate-value
The clock rate value can be changed as follows:
•
For Cisco 2600 and 3600 series routers, the minimum value for ADSL and G.SHDSL is 1 Mbps. The maximum value is 7 Mbps for mainboard slots and 5.3 Mbps for network modules. The default value for ADSL and G.SHDSL is 2.6 Mbps for both mainboard slots and network modules.
To make full use of the 2.3 Mbps bandwidth for VoATM non-switched trunk calls on G.SHDSL, you can change the 1 Mbps default value on Cisco 2600 series and Cisco 3600 series routers and configure the AAL2 clock rate as 2.6 Mbps.
It is recommended, however, that you keep the ADSL SCC clock rate for AAL2 at the default value of 1 Mbps because the upstream of ADSL cannot exceed 1 Mbps.
Note
•
For Cisco 2600 and 3600 series routers, the minimum value for ADSL and G.SHDSL is 1 Mbps. The maximum value is 7 Mbps for mainboard slots and 5.3 Mbps for network modules. The default value for ADSL and G.SHDSL is 2.6 Mbps for both mainboard slots and network modules.
Note
Command Modes
Interface ATM configuration
Command History
12.2(8)YN
This command was introduced on the Cisco 1700, Cisco 2600, and Cisco 3600 series.
Usage Guidelines
The communication between DSL WICs and a host in a router occurs through a device called the SCC. If a host wants to forward data or send any control traffic to a DSL WIC, it uses SCCs. In the same way, if a DSL WIC wants to forward incoming data from a line to the host, it also uses SCCs. Each DSL WIC installed in the router uses two SCCs. One SCC (SCC-A) is used for AAL5 data traffic, and the other SCC (SCC-B) is used for AAL2 and control traffic. The speed at which the SCC transfers data between a host and a WIC depends on the clock rate with which it has been configured. You can configure this clock rate on the basis of the DSL line rate. Even though the DSL upstream and downstream line rate may vary, the clock rate between the SCC and the DSL WIC is the same for both the transmitting and receiving direction. That is, the communication between the SCC and the DSL WIC is synchronous. Therefore, you need to configure only one clock rate for an SCC that will be used for both transmitting and receiving between an SCC and a DSL WIC.
It is always recommended that you configure the SCC clock rate slightly higher than the DSL line rate to accommodate overhead between the SCC and DSL WIC. For an asynchronous DSL WIC (for example, ADSL), the SCC clock rate depends on either the downstream or the upstream line rate, whichever is the maximum rate. For a synchronous DSL WIC (for example, G.SHDSL), the bandwidth for upstream and downstream is the same. Therefore, the SCC clock rate configuration can be based on either the upstream or the downstream line rate.
Because the maximum line rate for G.SHDSL is 2.312 Mbps, the default SCC clock rate of 2.6 Mbps for AAL5 and 1 Mbps for AAL2 should be sufficient. However, for ADSL, the clock rate may need to be configured on the basis of the current line rate. If AAL2 is used for voice traffic, the AAL2 SCC must be configured to the appropriate clock rate: 1 Mbps for ADSL and 2.6 Mbps for G.SHDSL.
The maximum data rate between an SCC and a DSL WIC depends primarily on the maximum clock rate that the SCC can support. For example, on the Cisco 2600 mainboard, which supports two DSL WICs, the total SCC clock rate that can be configured for both WICs is 8 Mbps. Therefore, if only one DSL WIC is present on the mainboard, AAL5 and AAL2 clock rates can be configured to 7 Mbps and 1 Mbps, respectively. If two DSL WICs are supported on the mainboard, the total of 8 Mbps should be distributed among the four SCCs.
Network module SCCs also pose similar limitations. That is, on the Cisco 2600, the total clock rate for all four SCCs is 8 Mbps. The maximum AAL5 clock rate that may be configured on a network module is 5.3 Mbps. On the Cisco 1700, the maximum configurable SCC clock rate for both AAL5 and AAL2 is 8 Mbps.
If the clock rate is unconfigured, the SCC is reset to the default values.
The clock rate can be configured independently for each SCC. To verify the clock rate setting, use the show running-config command.
Examples
The following example for a Cisco 2600 series or Cisco 3600 series router shows that the clock rate is set to 2 Mbps for AAL5 and to 1.3 Mbps for AAL2:
Router (config)# interface atm1/0Router (config-if)# no ip addressRouter (config-if)# no atm ilmi-keepaliveRouter (config-if)# pvc 6/65Router (config-if)# clock rate aal5 2000000Router (config-if)# clock rate aal2 1300000Router (config-if)# vbr-nrt 640 640 128Router (config-if)# tx-ring-limit 3connect (FRF.5)
To configure an FRF.5 one-to-one or many-to-one connection between two Frame Relay end users over an intermediate ATM network, use the connect command in global configuration mode. To remove a connection, use the no form of this command.
connect connection-name {vc-group group-name | FR-interface FR-DLCI} ATM-interface ATM-VPI/VCI network-interworking
no connect connection-name {vc-group group-name | FR-interface FR-DLCI} ATM-interface ATM-VPI/VCI network-interworking
Syntax Description
Defaults
No default behavior or values
Command Modes
Global configuration
Command History
12.1(2)T
This command was introduced.
12.2(8)YN
This command was implemented on the Cisco 1700 series.
Usage Guidelines
Use the connect command to connect a group of Frame Relay DLCIs to an ATM PVC.
To connect to the Frame Relay DLCI that has been configured on the interface, the Frame Relay DLCI must be configured on the interface using the frame-relay interface-dlci switched command.
To disconnect the FRF.5 interworking connection, use the shutdown connect subcommand.
Examples
The following example shows how to create an FRF.5 one-to-one connection (not using the vc-group keyword):
Router(config)#interface serial0/0Router(config-if)# frame-relay interface-dlci 100 switchedRouter(config-if)# interface atm1/0Router(config-if)# pvc 0/32Router(config-if-atm-vc)# encapsulation aal5mux frame-relayRouter (config-if-atm-vc)# exitRouter (config-if)# exitRouter(config)#connect frf5 serial0/0 100 atm1/0 0/32 network-interworkingRouter(config-frf5)# clp-bit 1Router(config-frf5)# de-bit map-clpThe following example shows how to create an FRF.5 many-to-one connection (using the vc-group keyword):
Router(config)#interface serial1/0Router(config-if)# frame-relay interface-dlci 100 switchedRouter (config-if)# exitRouter(config)#vc-group friendsRouter(config-vc-group)#serial1/0 16 16Router(config-vc-group)#serial1/0 17 17Router(config-vc-group)#serial1/0 18 18Router(config-vc-group)#serial1/0 19 19Router (config-vc-group)# exitRouter(config)#interface atm1/0Router(config-if)# pvc 0/32Router(config-if-atm-vc)# encapsulation aal5mux frame-relayRouter (config-if-atm-vc)# exitRouter (config-if)# exitRouter(config)#connect frf5-v vc-group friends atm1/0 0/32Router(config-frf5)# de-bit map-clpRelated Commands
connect (FRF.8)
To configure an FRF.8 one-to-one mapping between a Frame Relay data-link connection identifier (DLCI) and an ATM permanent virtual circuit (PVC), use the connect command in global configuration mode. To remove a connection, use the no form of this command.
connect connection-name FR-interface FR-DLCI ATM-interface ATM-VPI/VCI service-interworking
no connect connection-name FR-interface FR-DLCI ATM-interface ATM-VPI/VCI service-interworking
Syntax Description
Defaults
No default behavior or values
Command Modes
Global configuration
Command History
12.1(2)T
This command was introduced.
12.2(8)YN
This command was implemented on the Cisco 1700 series.
Usage Guidelines
Use the connect command to connect a Frame Relay DLCI to an ATM PVC.
To disconnect the FRF.8 interworking connection, use the shutdown connect subcommand.
Examples
The following example shows how to create an FRF.8 connection:
Router(config)#interface serial0/0Router(config-if)# frame-relay interface-dlci 100 switchedRouter(config-if)# interface atm1/0Router(config-if)# pvc 0/32Router(config-if-atm-vc)# encapsulation aal5mux fr-atm-srvRouter (config-if-atm-vc)# exitRouter (config-if)# exitRouter(config)#connect service-1 Serial0/0 100 ATM1/0 0/32 service-interworkingRouter(config-frf8)# efci-bit map-fecnRelated Commands
de-bit
To set Frame Relay discard eligible (DE) bit mapping for FRF.5 and FRF.8 network interworking, use the de-bit command in FRF.5 connect or FRF.8 connect configuration mode. To disable or reset Frame Relay DE bit mapping, use the no form of this command.
de-bit {0 | 1 | map-clp}
no de-bit {0 | 1 | map-clp}
Syntax Description
Defaults
map-clp
Command Modes
FRF.5 connect submode
FRF.8 connect submodeCommand History
12.1(2)T
This command was introduced.
12.2(8)YN
This command was implemented on the Cisco 1700 series.
Usage Guidelines
In the default state, the DE bit in the Frame Relay header is set to 1 when one or more ATM cells that belong to a frame have their cell loss priority (CLP) field set to 1 or when the DE field of the Frame Relay service specific convergence sublayer (FR-SSCS) protocol data unit (PDU) is set to 1.
When the no de-bit command and map-clp keyword is entered, the FR-SSCS PDU DE field is copied unchanged to the Q.922 core frame DE field, independent of CLP indications received at the ATM layer.
Examples
The following example creates a connection that connects the virtual circuit (VC) group named "friends" to ATM PVC 0/32 and configures FR DE field mapping to match the ATM CLP field:
Router(config)#vc-group friendsRouter(config-vc-group)#serial1/0 16 16Router(config-vc-group)#serial1/0 17 17Router(config-vc-group)#serial1/0 18 18Router(config-vc-group)#serial1/0 19 19Router(config)#interface atm3/0Router(config-if)# pvc 0/32Router(config-if-atm-vc)# encapsulation aal5mux frame-relayRouter (config-if-atm-vc)# exitRouter (config-if)# exitRouter(config)#connect vc-group friends atm3/0 0/32Router(config-frf5)# de-bit map-clpRelated Commands
ppp multilink multiclass
To enable a multiclass multilink, use the ppp multilink multiclass command in interface configuration mode. To disable the multiclass multilink, use the no form of this command.
ppp multilink multiclass
no ppp multilink multiclass
Syntax Description
This command has no arguments or keywords.
Defaults
A multiclass multilink is not enabled.
Command Modes
Interface configuration
Command History
12.2(8)YN
This command was introduced on the Cisco 1700, Cisco 2600, and Cisco 3600 series.
Usage Guidelines
This command must be entered on member links, not on the bundle interface itself. In the case of Point-to-Point Protocol over ATM (PPPoA) or Point-to-Point Protocol over Frame Relay (PPPoFR), the command is entered on the virtual template.
If this command is configured (and assuming that the peer also supports and is configured for multiclass interleaving), interleaved packets are assigned sequence numbers so that they are kept in order at the receiving end. Without this command, interleaved packets are sent without multilink headers so that they are subject to reordering when sent over parallel links.
Examples
The following example shows that interleaving is configured on the bundle interface while multiclass is configured on the member links (in this case, any Virtual-Access interfaces that are cloned from the Virtual-Template):
Router (config)# interface Multilink1Router (config-if)# ip address 10.0.0.50 255.255.255.240Router (config-if)# fair-queueRouter (config-if)# ppp multilinkRouter (config-if)# ppp multilink fragment-delay 10Router (config-if)# ppp multilink interleaveRouter (config-if)# multilink-group 2!Router (config)# interface Virtual-Template1Router (config-if)# no ip addressRouter (config-if)# ppp multilinkRouter (config-if)# ppp multilink multiclassRouter (config-if)# multilink-group 2Related Commands
tx-ring-limit
To limit the number of packets that can be used on a transmission (tx) ring on a DSL wide-area network interface card (WIC), use the tx-ring-limit command in ATM VC configuration mode. To not limit the number of packets that can be used on a transmission ring on a DSL WIC, use the no form of this command.
tx-ring-limit ring-limit
no tx-ring-limit ring-limit
Syntax Description
Defaults
The default value of the ring-limit argument is 60.
Command Modes
ATM VC configuration
Command History
Examples
The following example configures the transmission ring limit to three packets on an ATM permanent virtual circuit (PVC) subinterface:
Router(config)# interface atm1/0.1 point-to-pointRouter(config-subif)#pvc 2/200Router(config-if-atm-vc)#tx-ring-limit 3Related Commands
Feedback