Table Of Contents
clear call admission statistics
clear ppp subscriber statistics
dsl operating-mode (ADSL over ISDN)
dsl-mode shdsl symmetric annex
Broadband and DSL Commands
ac name
To specify the name of the access concentrator to be used in PPPoE Active Discovery Offers (PADO), use the ac name command in BBA group configuration mode. To remove this specification, use the no form of this command.
ac name name
no ac name name
Syntax Description
Defaults
If the name of the access concentrator is not specified, the name of the router is used as the access concentrator name.
Command Modes
BBA group configuration
Command History
Usage Guidelines
The ac name command allows you to advertise a unique access concentrator name other than the router name to PPPoE clients.
Examples
The following example shows the configuration of the name "region1" as the access concentrator name to be used in PADOs:
bba-group pppoe globalvirtual-template 1ac name region1Related Commands
access-list template
To enable template access control list (ACL) processing (as defined by the Template ACL feature), use the access-list template command in global configuration mode. To disable template ACL processing, use the no form of this command.
access-list template [number-of-rules]
no access-list template [number-of-rules]
Syntax Description
Command Default
Template ACL processing is enabled.
Command Modes
Global configuration (config)
Command History
12.2(27)SBKA
This command was introduced on the Cisco 10000 series router.
Cisco IOS XE Release 2.4
This command was implemented on the Cisco ASR 1000 series routers.
Usage Guidelines
Reducing the number of rules for template ACL status can lower CPU utilization. Checking each ACL against other known ACLs in the system is easier if the matching task can be aborted earlier.
Note
Changes in CPU utilization occur only during session initialization. Steady-state CPU utilization is unaffected by these changes in ACL processing.
If template ACL processing is disabled, the system replaces all existing template ACL instances with ACLs. Therefore, before you disable the feature, you must ensure that the number of template ACLs does not exceed the system capabilities.
If template ACL processing is enabled, the system scans and evaluates all configured per-session ACLs, and then creates all required template ACLs.
Default Settings
If the number-of-rules argument is specified for the no version of the command, the default of 100 will be used, and only ACLs with 100 or fewer rules will be considered for template status.
Cisco 1000 Series Routers
On the Cisco 1000 series routers, if the number of rules is smaller than the largest similar Attribute 242 ACL, the processing of this new setting can use up substantial CPU resources because ACLs that previously would be considered as template ACL duplicates are instead compiled using TurboACL compilation without regard to other ACLs already in the router. If the ACLs have fewer than eight rules, the CPU increase will not be so noticeable, because ACLs will be compiled as MiniACLs.
If the number of rules is set larger than the largest similar Attribute 242 ACL, then increased CPU resources may be required to conduct the comparison task. This potential increase in CPU resources is offset by the elimination of TurboACL and MiniACL compilation.
Examples
The following example specifies that ACLs with 50 or fewer rules will be considered for template ACL status:
Router(config)# access-list template 50atm pppatm link reset
To configure the system to bring down PPP over ATM (PPPoA) sessions when the virtual circuit (VC) is deactivated, use the atm pppatm link reset command in subinterface configuration mode. To return to the default behavior (PPPoA sessions are not brought down), use the no form of this command.
atm pppatm link reset
no atm pppatm link reset
Syntax Description
This command has no arguments or keywords.
Defaults
PPPoA sessions are not brought down when the VC is deactivated.
Command Modes
Subinterface configuration
Command History
Usage Guidelines
Use the atm pppatm link reset command to configure the system to place PPPoA sessions in a non operational state when a VC is deactivated. This command is useful on customer premises equipment (CPE) that is not configured with Dialer. On L2TP access concentrators (LACs), issues of scalability make it useful to allow PPPoA sessions to remain up when a VC is deactivated.
Examples
In the following example, PPPoA sessions on permanent virtual circuit (PVC) 3/501 will be brought down when that PVC is deactivated:
interface ATM4/0atm pppatm link resetpvc 3/501encapsulation aal5snapprotocol ppp virtual-template 1!interface virtual-template 1no ip addressppp chap hostname bostonppp chap password 7 111F1111ppp multilinkppp multilink group 1interface multilink1ip unnumbered loopback 0ppp multilinkppp multilink group 1atm route-bridged
To configure an interface to use the ATM routed bridge encapsulation (RBE), use the atm route-bridged command in interface configuration mode.
atm route-bridged protocol
Syntax Description
protocol
Protocol to be route-bridged. IP and IPv6 are the only protocols that can be route-bridged using ATM RBE.
Command Default
ATM routed bridge encapsulation is not configured.
Command Modes
ATM subinterface configuration
Command History
Usage Guidelines
Use this command to configure RBE on an ATM interface. The atm route-bridged command can also be used to integrate RBE with quality of service (QoS) features on the Cisco 800 and 1700 series routers.
Routing of IPv6 and IP Packets
IP and IPv6 packets can be routed using RBE only over ATM point-to-point subinterfaces.
Routing of IP packets and IPv6 half-bridging, bridging, PPP over Ethernet (PPPoE), or other Ethernet 802.3-encapsulated protocols can be configured on the same subinterface.
Router Advertisements with IPv6
Router advertisements are suppressed by default. For stateless autoconfiguration, router advertisements must be allowed with the no ipv6 nd suppress-ra command. For static configuration, router advertisement is not required; however, the aggregator should either have the RBE interface on the same subnet as the client or have a static IPv6 route to that subnet through the RBE interface.
Examples
IP Encapsulation Example
The following example configures ATM routed bridge encapsulation on an interface:
interface atm 4/0.100 point-to-pointip address 172.16.5.9 255.255.255.0atm route-bridged ippvc 0/32IPv6 Encapsulation Example
The following example shows a typical configuration on an RBE interface to allow routing of IPv6 encapsulated Ethernet packets. IPv6 packets sent out of the subinterface are encapsulated over Ethernet over the RBE interface.
interface ATM1/0.1 point-to-pointipv6 enableipv6 address 3FEE:12E1:2AC1:EA32::/64no ipv6 nd suppress-raatm route-bridged ipv6pvc 1/101In this example, the ipv6 enable command allows the routing of IPv6 packets. The ipv6 address command specifies an IPv6 address for the interface and an IPv6 prefix to be advertised to a peer. The no ipv6 nd ra suppress command enables router advertisements on the interface.
IPv6 Routing and Bridging of Other Traffic Example
The following example shows a configuration in which IPv6 packets are routed and all other packets are bridged.
interface ATM1/0.1 point-to-pointipv6 enableipv6 address 3FEE:12E1:2AC1:EA32::/64atm route-bridged ipv6bridge-group 1pvc 1/101IP and IPv6 Routing with Bridging of Other Protocols Example
IP and IPv6 routing can be configured on the same interface as shown in this example. All other packets are bridged. PPPoE could also be configured on this same interface.
interface ATM1/0.1 point-to-pointipv6 enableipv6 address 3FEE:12E1:2AC1:EA32::/64ip address 10.0.0.1 255.255.255.0atm route-bridged ipv6atm route-bridged ipbridge-group 1pvc 1/101Static Configuration Example
The following example shows the IPv6 static route configured. Unlike IP, the IPv6 interface on an aggregator is always numbered and, minimally, has a link local IPv6 address.
Router# configure terminalRouter(config)# ipv6 route 3FEE:12E1:2AC1:EA32::/64 atm1/0.3Router(config)# endshow ipv6 interface Example
Notice in this show ipv6 interface output display that each RBE link has its own subnet prefix. Unlike proxy ARP in IPv4 RBE configurations, the aggregator does not require proxy ND in IPv6 RBE deployments.
Router# show ipv6 interface atm1/0.1ATM1/0.1 is up, line protocol is upIPv6 is enabled, link-local address is FE80::203:FDFF:FE3B:B400Global unicast address(es):3FEE:12E1:2AC1:EA32::, subnet is 3FEE:12E1:2AC1:EA32::/64Joined group address(es):FF02::1FF02::2FF02::1:FF00:0FF02::1:FF3B:B400MTU is 4470 bytesICMP error messages limited to one every 100 millisecondsICMP redirects are enabledND DAD is enabled, number of DAD attempts: 1ND reachable time is 30000 millisecondsND advertised reachable time is 0 millisecondsND advertised retransmit interval is 0 millisecondsND router advertisements are sent every 200 secondsND router advertisements live for 1800 secondsHosts use stateless autoconfig for addressesIntegrated Class-Based Weighted Fair Queueing and RBE on ATM Example
The following partial example configures a single PVC using AAL5SNAP encapsulation and class-based routing for traffic shaping on the interface where RBE is enabled. The following CBWFQ parameters are configured: access-list with different IP precedence, class map, policy map, and service policy. Different bandwidth classes are configured in the same policy.
RBE base configuration:
interface FastEthernet0ip address 172.22.1.1 255.255.0.0!interface ATM0.1 point-to-pointip address 10.1.1.5 255.255.255.252atm route-bridged ippvc 88/800encapsulation aal5snap!interface ATM0.1 point-to-pointip address 10.1.1.1 255.255.255.252atm route-bridged ippvc 99/900encapsulation aal5snap!interface ATM0.1 point-to-pointip address 172.18.0.1 255.0.0.0pvc 100/1000!router eigrp 100network 10.1.0.0network 172.18.0.0network 172.22.0.0...CBWFQ configuration:
class-map match-all voicematch access-group 105!policy-map voicedatapolicyclass voicebandwidth 200class class-defaultfair-queuerandom-detect!interface Ethernet0ip address 172.25.1.1 255.0.0.0hold-queue 600 inhold-queue 100 out!interface ATM0no ip addressno atm ilmi-keepalivedsl operating-mode auto!interface ATM0.1 point-to-pointip address 10.2.3.4 255.255.255.0atm route-bridged ippvc 1/42protocol ip 10.2.3.5 broadcastvbr-nrt 300 300encapsulation aal5snapservice-policy output voicedatapolicy...Related Commands
no ipv6 nd ra suppress
Suppresses IPv6 router advertisement transmissions on a LAN interface.
bba-group pppoe
To create a PPP over Ethernet (PPPoE) profile, use the bba-group pppoe command in global configuration mode. To delete a PPPoE profile, use the no form of this command.
bba-group pppoe {group-name | global}
no bba-group pppoe {group-name | global}
Syntax Description
Command Default
A PPPoE profile is not configured.
Command Modes
Global configuration (config)#
Command History
Usage Guidelines
PPPoE profiles contain the configuration for a group of PPPoE sessions. Once a profile has been defined, it can be assigned to a PPPoE port (Ethernet interface, VLAN, or PVC), a virtual circuit (VC) class, or an ATM PVC range. PPPoE profiles can also be used with PPP over ATM (PPPoA)/PPPoE autosense. Multiple PPPoE profiles can be created and assigned to different ports.
The global PPPoE profile serves as the default profile for any port that has not been assigned a specific PPPoE profile.
Examples
The following example shows the configuration of a global PPPoE profile and a profile called "vpn1". PPPoE sessions established on PVCs that use the VC class "class-pppoe-global" will use the global profile. PVCs in the range "range-pppoe-1" will use the "vpn1" profile.
Router(config)# bba-group pppoe globalRouter(config-bba-group)# virtual-template 1Router(config-bba-group)# sessions max limit 8000Router(config-bba-group)# sessions per-vc limit 8Router(config-bba-group)# sessions per-mac limit 2!Router(config-bba-group)# bba-group pppoe vpn1Router(config-bba-group)# virtual-template 1Router(config-bba-group)# sessions per-vc limit 2Router(config-bba-group)# sessions per-mac limit 1!Router(config-bba-group)# vc-class atm class-pppoe-globalRouter(config-bba-group)# protocol pppoe!Router(config-bba-group)# interface ATM1/0.10 multipointRouter(config-bba-group)# range range-pppoe-1 pvc 100 109Router(config-bba-group)# protocol pppoe group vpn1!Router(config-bba-group)# interface ATM1/0.20 multipointRouter(config-bba-group)# class-int class-pppoe-globalRouter(config-bba-group)# pvc 0/200Related Commands
call admission limit
To instruct Internet Key Exchange (IKE) to drop security association (SA) requests (that is, calls for Call Admission Control [CAC]) when a specified percentage of system resources is being consumed, use the call admission limit command in global configuration mode. To disable this feature, use the no form of this command.
call admission limit percent
no call admission limit percent
Syntax Description
percent
Percentage of the system resources that, when used, causes IKE to stop accepting new SA requests. Valid values are 1 to 100.
Defaults
No default behavior or values
Command Modes
Global configuration
Command History
Usage Guidelines
It is recommended that initially you specify a value of 90. You will have to alter the value depending on the network topology, the capabilities of the router, and the traffic patterns.
Examples
The following example causes IKE to drop calls when 90 percent of system resources are being used:
Router(config)# call admission limit 90Related Commands
show call admission statistics
Monitors the global CAC configuration parameters and the behavior of CAC.
call admission load
To configure a call admission control (CAC) metric for scaling WAN protocol session load, use the call admission load command in global configuration mode. To disable this feature, use the no form of this command.
call admission load multiplier metric-poll-rate
no call admission load multiplier metric-poll-rate
Syntax Description
Defaults
The default values are 100 for the multiplier and 1 for the poll rate. These values should not be changed without guidance from Cisco technical personnel.
Command Modes
Global configuration
Command History
Usage Guidelines
This command enables CAC to limit overconsumption of Cisco IOS CPU cycles. On hardware-forwarded router platforms, established sessions tend not to consume much of the router processor resources, but there is a need to reduce resource utilization during session establishment, especially, to determine when a call cannot be handled and then to determine when it can be handled again.
For the call admission load command, the router load is calculated when software routines average the current CPU utilization. The command is configured as a mathematical formula—call admission load multiplier metric-poll-rate—where CPU utilization is polled every metric-poll-rate seconds and multiplied by a multiplier, which is the scaling factor. This formula results in a metric value for the current router load determined by existing sessions. The value is compared to that set for the call admission limit command, and if it exceeds the value, the call is rejected; otherwise, the call is accepted.
Note
Examples
The following example shows recommended settings for the call admission load and call admission limit commands on the Cisco 10000 ESR:
Router(config)# call admission limit 90Router(config)# call admission load 100 1Related Commands
class-range
To assign a virtual circuit (VC) class to an ATM permanent virtual circuit (PVC) range, use the class-range command in PVC range configuration mode. To remove the VC class, use the no form of this command.
class-range class-name
no class-range class-name
Syntax Description
Defaults
No VC class is assigned to the PVC range.
Command Modes
PVC range configuration
Command History
12.1(5)T
This command was introduced.
12.2(28)SB
This command was integrated into Cisco IOS Release 12.2(28)SB.
Usage Guidelines
When you create a VC class for an ATM PVC range, you can use the following commands to define your parameters: abr, broadcast, cbr, encapsulation aal5, ilmi manage, inarp, oam-pvc, oam retry, protocol, ubr, ubr+, vbr-nrt, and vbr-rt.
Parameters that are configured for a PVC range through discrete commands entered in PVC range configuration mode supersede VC class parameters assigned to an ATM PVC range using the class-range command.
Examples
In the following example, a class called "classA" is created and then applied to an ATM PVC range called "range-pppoa-1":
! The following commands create the class classA:vc-class atm classAubr 10000encapsulation aal5snap! The following commands apply classA to an ATM PVC range:interface atm 6/0.110 multipointrange range-pppoa-1 pvc 0/102 0/199class-range classARelated Commands
shutdown (PVC-in-range)
Deactivates an individual PVC within a PVC range.
shutdown (PVC range)
Deactivates an ATM PVC range.
clear call admission statistics
To clear call admission control (CAC) statistics, use the clear call admission statistics command in privileged EXEC mode.
clear call admission statistics
Syntax Description
This command has no arguments or keywords.
Command Modes
Privileged EXEC
Command History
Usage Guidelines
Use the clear call admission statistics command to clear statistics associated with CAC.
Examples
The following example clears the CAC statistics shown in the show call admission statistics EXEC command report:
Router# show call admission statisticsTotal call admission charges: 0, limit 25Total calls rejected 150, accepted 51Router# clear call admission statisticsClear call admission statistics [confirm]yRelated Commands
clear ip http client cookie
To remove the HTTP client cookies, use the clear ip http client cookie command in privileged EXEC mode.
clear ip http client cookie [domain cookie-domain | name cookie-name | session session-name]
Syntax Description
Command Modes
Privileged EXEC (#)
Command History
Examples
The following example shows how to remove the HTTP client cookie named test:
Device# clear ip http client cookie name test
clear mpf interface
To clear Multi-Processor Forwarding (MPF) packet counts on all physical interfaces, use the clear mpf interface command in user EXEC or privileged EXEC mode.
clear mpf interface
Syntax Description
This command has no arguments or keywords.
Command Modes
User EXEC
Privileged EXECCommand History
Usage Guidelines
This command has no output. It resets the packet counters shown in the show mpf interface command output.
Examples
The following example uses the clear mpf interface command to reset the packet counters displayed in the output of the show mpf interface command:
Router# clear mpf interfaceRelated Commands
clear mpf punt
To clear Multi-Processor Forwarding (MPF) per-box punt reason and counts, use the clear mpf punt command in user EXEC or privileged EXEC mode.
clear mpf punt
Syntax Description
This command has no arguments or keywords.
Command Modes
User EXEC
Privileged EXECCommand History
Usage Guidelines
This command clears all punt counters and implicitly generates show mpf punt output. It resets for each box or router chassis the punt packet counters shown in the show mpf punt command output. Packets that are punted are directed for Cisco IOS processing and are not accelerated by MPF.
Examples
The following example clears the type of packets (Type), the reasons for the punt (Message), and the punt packet counts (Count) for the router chassis, then implicitly generates show mpf punt output.
Router# show mpf puntType Message Countl2tp unknown session errors 7l2tp L2TP control 6ipv4/verify adjacency punt 1ethernet unknown ethernet type 542ppp punts due to unknown protocol 333arp ARP request 6Router# clear mpf puntType Message Countarp ARP request 38ethernet unknown ethernet type 591l2tp unknown session errors 71790l2tp unsupported output feature 24000Table 8 describes the fields in the clear mpf punt output display.
Related Commands
clear ppp subscriber statistics
To clear PPP subscriber statistics and reset counters to zero, use the clear ppp subscriber statistics command in privileged EXEC mode.
clear ppp subscriber statistics
Syntax Description
This command has no arguments or keywords.
Command Modes
Privileged EXEC
Command History
Usage Guidelines
Use the clear ppp subscriber statistics command to clear all PPP subscriber statistics and reset counters to zero.
Examples
The following example clears all PPP subscriber statistics and resets counters to zero:
Router# clear ppp subscriber statisticsRelated Commands
clear pppatm interface atm
To clear PPP ATM sessions on an ATM interface, use the clear pppatm interface atm command in privileged EXEC mode.
clear pppatm interface atm interface-number[.subinterface-number] [vc {[vpi/]vci | virtual-circuit-name}]
Syntax Description
Command Modes
Privileged EXEC
Command History
12.2(13)T
This command was introduced.
12.2(28)SB
This command was integrated into Cisco IOS Release 12.2(28)SB.
Usage Guidelines
This command clears the PPP over ATM (PPPoA) sessions in an interface, or in a VC when the VC is specified.
When the clear pppatm interface atm command is used to clear sessions on an interface, PPP keepalives continue to work and can be used to detect a broken link.
Examples
The following example clears a PPP ATM session on ATM interface 1/0.10:
Router# clear pppatm interface atm 1/0.10Related Commands
debug pppatm
Enables reports for PPPoA events, errors, and states either globally or conditionally on an interface or VC.
show pppatm summary
Displays PPPoA session counts.
clear pppatm statistics
To clear PPP over ATM statistics and reset counters to zero, use the clear pppatm statistics command in privileged EXEC mode.
clear pppatm statistics
Syntax Description
This command has no arguments or keywords.
Command Modes
Privileged EXEC
Command History
Usage Guidelines
Use the clear pppatm statistics command to clear PPPoA statistics and reset counters to zero.
Examples
The following example clears PPPoA statistics and reset counters to zero:
Router# clear pppatm subscriber statisticsRelated Commands
clear pppoe
To clear PPP over Ethernet (PPPoE) sessions, use the clear pppoe command in privileged EXEC mode.
clear pppoe {interface type number [vc {[vpi/]vci | vc-name}] [vlan vlan-id] | rmac mac-address [sid session-id] | all}
Syntax Description
Command Modes
Privileged EXEC
Command History
12.2(13)T
This command was introduced.
12.3(2)T
The vlan vlan-id keyword and argument were added.
Usage Guidelines
Use the clear pppoe all command to clear all PPPoE sessions.
Use the interface keyword and arguments and the vlan keyword and argument to clear PPPoE sessions on a specific Ethernet 802.1Q VLAN.
Use the interface, vc, and vlan keywords and arguments to clear PPPoE over 802.1Q VLAN sessions on an ATM PVC.
Examples
The following example clears all PPPoE sessions:
Router# clear pppoe allclear pppoe derived
To clear the cached PPP over Ethernet (PPPoE) configuration of a PPPoE profile and force the PPPoE profile to reread the configuration from the assigned subscriber profile, use the clear pppoe derived command in privileged EXEC mode.
clear pppoe derived group group-name
Syntax Description
Command Modes
Privileged EXEC
Command History
12.2(15)T
This command was introduced.
12.2(28)SB
This command was integrated into Cisco IOS Release 12.2(28)SB.
Usage Guidelines
A subscriber profile can be configured locally on the router or remotely on an authentication, authorization, and accounting (AAA) server. The PPPoE configuration that is derived from a subscriber profile is cached locally under the PPPoE profile. Use the clear pppoe derived command to clear the cached PPPoE configuration of a specified PPPoE profile and force the PPPoE profile to reread the configuration from the assigned subscriber profile.
A subscriber profile contains a list of PPPoE service names. The PPPoE server will advertise the service names that are listed in the subscriber profile to each PPPoE client connection that uses the configured PPPoE profile. You can assign a subscriber profile to a PPPoE profile by using the service profile command in BBA group configuration mode.
Examples
The following example clears the cached PPPoE configuration for PPPoE profile "group1". The PPPoE profile will reread the configuration from the subscriber profile that is assigned to that PPPoE profile.
Router# clear pppoe derived group1Related Commands
clear pppoe relay context
To clear the PPP over Ethernet (PPPoE) relay context created for relaying PPPoE Active Discovery (PAD) messages, use the clear pppoe relay context command in privileged EXEC mode.
clear pppoe relay context {all | id session-id}
Syntax Description
all
Clears all relay contexts.
id session-id
Clears a specific relay context identified in the output of the show pppoe relay context all command.
Command Modes
Privileged EXEC
Command History
12.3(4)T
This command was introduced.
12.2(28)SB
This command was integrated into Cisco IOS Release 12.2(28)SB.
Usage Guidelines
Use this command to clear relay contexts created for relaying PAD messages.
Examples
The following example clears all PPPoE relay contexts created for relaying PAD messages:
Router# clear pppoe relay context allRelated Commands
show pppoe relay context all
Displays PPPoE relay contexts created for relaying PAD messages.
show pppoe session
Displays information about currently active PPPoE sessions.
clear pppoe statistics
To clear PPP over Ethernet (PPPoE) statistics and reset counters to zero, use the clear pppoe statistics command in privileged EXEC mode.
clear pppoe statistics
Syntax Description
This command has no arguments or keywords.
Command Modes
Privileged EXEC
Command History
Usage Guidelines
Use the clear pppoe statistics command to clear all PPPoE statistic and reset counters to zero.
Examples
The following example clears all PPPoE statistics and resets counters to zero:
Router# clear pppoe statisticsRelated Commands
connection request username
To specify the username used to authenticate an auto-configuration server (ACS) which makes a connection request to a customer premise equipment (CPE), use the connection request username command in TR-069 Agent configuration mode.
connection request username username
Syntax Description
Command Modes
TR-069 Agent configuration mode (config-cwmp)
Command History
Examples
The following example shows the connection request username command when specifying a username:
Device(config-cwmp)# connection request username cisco
connection request password
To specify the password used to authenticate an auto-configuration server (ACS) which makes a connection request to a customer premise equipment (CPE), use the connection request password command in TR-069 Agent configuration mode.
connection request password [encryption-type | cleartext-password] passwd
Syntax Description
Command Modes
TR-069 Agent configuration (config-cwmp)
Command History
Examples
The following example shows how to specify the password that is used in the authentication phase. In this example, the password is cisco and is not encrypted:
Device(config-cwmp)# connection request password 0 cisco
control-packets vlan cos
To set the 802.1P priority bits in 802.1Q frames containing PPP over Ethernet (PPPoE) control packets, use the control-packets vlan cos command in BBA group configuration mode. To remove the setting, use the no form of this command.
control-packets vlan cos priority
no control-packets vlan cos priority
Syntax Description
priority
Allows the configuration of VLAN priority bits, for PPPoE control packets. The priority value for PPPoE control packets in the VLAN header can be any number from 0 through 7.
Command Default
No marking is enabled.
Command Modes
BBA group configuration (config-bba-group)
Command History
12.2SRC
This command was introduced.
12.2(33)SB
This command was integrated.
Cisco IOS XE Release 2.1
This command was integrated.
Usage Guidelines
This command allows the setting of class of service (CoS) values on PPPoE control packets to valid priority value compatible with IEEE 802.1P particularly for PPPoEo802.1Q, and PPPoE over QinQ. Settings for PPPoE control packets can differ depending on the BBA group that they are associated with.
Examples
In the following examples, PPPoE control packets associated with BBA group global have a priority of 5, whereas PPPoE control packets associated with BBA group cisco have a priority of 2:
Router(config)# bba-group pppoe globalRouter(config-bba-group)# control-packets vlan cos 5Router(config)# bba-group pppoe ciscoRouter(config-bba-group)# control-packets vlan cos 2The following example shows the setting of 802.1P priority bits in 802.1Q frames containing PPPoE:
Router(config-bba-group)# control-packets vlan cos 5Related Commands
controller shdsl
To configure a controller for single-pair high-bit-rate digital subscriber line (SHDSL) mode, use the controller shdsl command in global or controller configuration mode.
Cisco HWIC-4SHDSL and HWIC-2SHDSL
controller shdsl slot-number/subslot-number/port-number
Cisco IAD2420 Series
controller shdsl number
Syntax Description
Defaults
Controller number: 0
Command Modes
Cisco HWIC-4SHDSL and HWIC-2SHDSL
Global configuration
Controller configuration
Cisco IAD2420 Series
Global configuration
Command History
Usage Guidelines
This command is used to configure the controller mode and the controller number.
Examples
Cisco HWIC-4SHDSL and HWIC-2SHDSL
The following example uses the controller shdsl command to configure a Cisco HWIC-4SHDSL installed in a Cisco access router, controller number 0, subslot 2, port number 0); the example enters controller configuration mode:
Router(config)# controller shdsl 0/2/0Router(config-controller)#Cisco IAD2420 Series
The following example uses the controller shdsl command to enter SHDSL controller mode on controller number 0; the example also configures ATM mode:
Router# controller shdsl 0Router# mode atmRelated Commands
cwmp agent
To enable the TR-069 Agent configuration mode, use the cwmp agent command in global configuration mode.
cwmp agent
Syntax Description
This command has no arguments or keywords.
Command Default
None
Command Modes
Global configuration (config)
Command History
Examples
The following example shows how to enter TR-069 Agent configuration mode:
Device(config)# cwmp agent
cwmp wan
To define the WAN interfaces on the customer premises equipment (CPE), use the cwmp wan command in interface configuration mode.
cwmp wan
Syntax Description
This command has no arguments or keywords.
Command Modes
Interface configuration (config-if)
Command History
Usage Guidelines
Any interface without this command is considered a LAN interface by TR-069 protocol. There can be multiple WAN and LAN interfaces configured on the CPE. By default, an ATM interface on the CPE will be considered a WAN interface by the TR-069 protocol.
Examples
The following example shows how to define the WAN interfaces on the CPE:
Device(config-if)# cwmp wan
Related Commands
cwmp wan default
To define the default WAN interfaces on the customer premises equipment (CPE), use the cwmp wan default command in interface configuration mode.
cwmp wan default
Syntax Description
This command has no arguments or keywords.
Command Modes
Interface configuration (config-if)
Command History
Usage Guidelines
Among the multiple WAN interfaces, there can be only one default WAN interface in which the TR-069 communication will happen. If you try to configure this command on multiple interfaces, only the latest configuration will be active and the previous default WAN interface will become a WAN interface, ensuring only one interface is the default at any point in time.
Examples
The following example shows how to define the default WAN interfaces on the CPE:
Device(config-if)# cwmp wan default
dsl enable-training-log
To enable the training log to record firmware debug messages, enter the dsl enable-training-log command in interface configuration mode.
dsl enable-training-log {delay [nseconds] | failure | ondemand | showtime}
Syntax Description
Command Default
By default, the training log is disabled.
Command Modes
Interface configuration
Command History
12.4(11)XJ
This command modification was integrated into the Cisco IOS
Release 12.4(11)XJ.
Usage Guidelines
The dsl enable-training log command is an optional command that enables the training log to record the firmware debug messages. This log can be retrieved from the asynchronous digital subscriber line (ADSL) chipset after the ADSL line goes into showtime or comes out of showtime, or whenever the user enters the show dsl interface atm command.
Caution
Examples
The following example shows: To enable the training log, enter the following command in interface configuration mode:dsl enable-training-log showtimeRelated Commands
dsl equipment-type
To configure the digital subscriber line (DSL) ATM interface to function as central office or customer premises equipment, use the dsl equipment-type command in interface configuration mode. To restore the default equipment type, use the no form of this command.
dsl equipment-type {co | cpe} ignore-error-duration seconds
no dsl equipment-type
Syntax Description
Defaults
cpe
Seconds: 0Command Modes
Interface configuration
Command History
Usage Guidelines
This configuration command applies to a specific ATM interface. You must specify the ATM interface before you enter this command.
The ATM interface must be in the shutdown state before you enter this command.
Examples
The following example shows how to configure DSL ATM interface 1/1 to function as central office equipment:
Router# configure terminalEnter configuration commands, one per line. End with CNTL/Z.Router(config)# interface atm 1/1Router(config-if)# dsl equipment-type co ignore-error-duration 18````Router(config-if)# endRouter# clear interface atm 0/1Related Commands
dsl linerate
Specifies a line rate for the DSL ATM interface.
dsl operating-mode gshdsl
Specifies an operating mode of the DSL ATM interface.
dsl gain-setting rx-offset
To add an offset to the receive (Rx) gain in a modem, use the dsl gain-setting rx-offset command in global configuration mode.
dsl gain-setting rx-offset decimal
Syntax Description
decimal
Offset (in dB) to the Rx gain. The valid range is from -5 dB to 3 dB, with a granularity of 0.5 dB.
Defaults
0 dB (no offset)
Command Modes
Global configuration
Command History
12.2(8)YN
This command was introduced.
12.3(2)T
This command was integrated into Cisco IOS Release 12.3(2)T.
Usage Guidelines
In most cases this command does not need to be used because the default value should be adequate. If the service provider improves the line rates, as often happens, using this and other DSL commands will not improve the DSL performance.
Examples
The following example shows how to add an offset of -2 to the receive (Rx) gain of the modem:
dsl gain-setting rx-offset -2Related Commands
dsl gain-setting tx-offset
To add an offset to the transmit gain in a modem, use the dsl gain-setting tx-offset command in global configuration mode.
dsl gain-setting tx-offset decimal
Syntax Description
decimal
Offset (in dB) to the transmit gain. The valid range is from -10 dB to 3 dB, with a granularity of 0.5 dB.
Defaults
0 dB (no offset)
Command Modes
Global configuration
Command History
12.2(8)YN
This command was introduced.
12.3(2)T
This command was integrated into Cisco IOS Release 12.3(2)T.
Usage Guidelines
In most cases this command does not need to be used because the default value should be adequate. If the service provider improves the line rates, as often happens, using this and other DSL commands will not improve the DSL performance.
Examples
The following example shows how to add an offset of .5 to the transmit (Tx) gain of the modem:
dsl gain-setting tx-offset .5Related Commands
dsl linerate
To specify a line rate for the digital subscriber line (DSL) ATM interface, use the dsl linerate command in interface configuration mode. To restore the default line rate, use the no form of this command.
dsl linerate {kbps | auto}
no dsl linerate
Syntax Description
Defaults
The DSL ATM interface automatically synchronizes its line rate with the far-end DSLAM or WIC.
Command Modes
Interface configuration
Command History
Usage Guidelines
This configuration command applies to a specific ATM interface. You must specify the ATM interface before you enter this command.
The ATM interface must be in the shutdown state before you enter this command.
Examples
The following example shows how to configure DSL ATM interface 0/1 to operate at a line rate of 1040 kbps.
Router# configure terminalEnter configuration commands, one per line. End with CNTL/Z.Router(config)# interface atm 0/1Router(config-if)# dsl linerate 1040Router(config-if)# endRouter# clear interface atm 0/1Related Commands
dsl equipment-type
Configures the DSL ATM interface to function as CO equipment or CPE.
dsl operating-mode gshdsl
Specifies an operating mode of the DSL ATM interface.
dsl lom
To enable LoM monitoring, use the dsl lom command in global configuration mode. To disable LOM monitoring, use the no form of this command.
dsl lom number
no dsl lom
Syntax Description
Defaults
This command is disabled by default. LoM monitoring is disabled.
Command Modes
Interface configuration
Command History
Examples
The following example shows how to enable LoM monitoring with retraining configured for 200 counts:
dsl lom 200Related Commands
show dsl interface atm
Displays the ADSL-specific information for a specified ATM interface.
dsl max-tone-bits
To set a limit on the number of bits that are loaded into each upstream tone, use the dsl max-tone-bits command in global configuration mode.
dsl max-tone-bits integer
Syntax Description
Defaults
14 bits per tone, which is the ADSL maximum standard
Command Modes
Global configuration
Command History
12.2(8)YN
This command was introduced.
12.3(2)T
This command was integrated into Cisco IOS Release 12.3(2)T.
Usage Guidelines
In most cases this command does not need to be used because the default value should be adequate. If the service provider improves the line rates, as often happens, using this and other DSL commands will not improve the DSL performance.
Examples
The following example sets 10 as the maximum number of bits to be loaded into each upstream tone:
dsl max-tone-bits 10Related Commands
dsl noise-margin
To add an offset to the receive (Rx) target noise margin of a modem, use the dsl noise-margin command in global configuration mode.
dsl noise-margin decimal
Syntax Description
decimal
Offset (in dB) to the Rx target noise margin. The valid range is from -3 dB to -3 dB, with a granularity of 0.5 dB.
Defaults
0 dB (no offset)
Command Modes
Global configuration
Command History
12.2(8)YN
This command was introduced.
12.3(2)T
This command was integrated into Cisco IOS Release 12.3(2)T.
Usage Guidelines
In most cases this command does not need to be used because the default value should be adequate. If the service provider improves the line rates, as often happens, using this and other digital subscriber line (DSL) commands will not improve the DSL performance.
Examples
The following example shows how to add an offset of -0.5 to the noise margin:
dsl noise-margin -.5Related Commands
dsl operating-mode
To configure the (DSL) operating mode, use the dsl operating-mode command in interface configuration mode on Annex A and Annex M interfaces.
dsl operating-mode {adsl2 [annex a | annex m] | adsl2+ [annex a | annex m] | ansi-dmt | auto | itu-dmt}
Syntax Description
Command Default
The default is auto mode.
Command Modes
Interface configuration
Command History
Usage Guidelines
In the default auto mode, a router first tries to connect using the configured ITU operating modes. If the connection fails, the router tries with ANSI/ETSI mode for the allowed number of seconds (2 seconds by default). This time can be modified with the dsl sync interval command. If this command fails, the router tries ITU mode again for the allotted number of seconds (2 seconds by default). The router can be forced to try connecting with ANSI mode first by using the dsl sync mode ansi command. If this also fails, the router tries ITU mode again for 3 seconds or the interval specified by dsl sync interval. If that fails, the router repeats the cycle mode, including any modes other than ansi mentioned above.
If the router is forced to connect in a mode other than auto, you must use DSL operating-mode with the attribute auto to set the router back to the default auto mode.
The router continues switching between modes, in sequence as described, until the router reaches the showtime state (which signifies that the connection attempt is successful) and connects, using one of the modes. This switching process is designed specifically for expediting DSL performance.
Examples
The following example shows how to configure Annex M operating mode, using the dsl operating-mode command and beginning in interface configuration mode:
Router(config-if)# dsl operating-mode adsl2+ annex mdsl operating-mode (ADSL over ISDN)
To specify the operating mode of the digital subscriber line (DSL) for an ATM interface, use the dsl operating-mode command in interface configuration mode. To restore the default operating mode, use the no form of this command.
dsl operating-mode {annexb-ur2 | etsi | auto}
no dsl operating-mode {annexb-ur2 | etsi | auto}
Syntax Description
Defaults
Mode: etsi
Command Modes
Interface configuration
Command History
12.2(4)YA
This command was introduced.
12.2(15)T
This command was implemented on the Cisco 820 series and the Cisco SOHO 70, 76, 77, and 77H platforms.
Usage Guidelines
In auto mode, a modem first tries to connect using etsi mode. If the connection fails, the modem retries a set number of times. If the modem fails to connect after several retries using etsi mode, the modem automatically switches to annexb-ur2 mode and tries several times to connect using annexb-ur2 mode. If the modem fails to connect after several retries using annexb-ur2 mode, the modem automatically switches back to etsi mode and tries to connect.
The modem continues switching between modes, in sequence as described, until the modem reaches the state SHOWTIME (which signifies that the connection attempt was successful) and connects using one of the modes. This switching process is designed specifically for expediting DSL modem performance.
Examples
The following example shows how to configure the DSL to operate in etsi mode:
Router# configure terminalEnter configuration commands, one per line. End with CNTL/Z.Router(config)# interface atm 0Router(config-if)# dsl operating-mode etsiRouter(config-if)# endRelated Commands
show dsl interface atm
Displays information specific to the ADSL for a specified ATM interface.
dsl operating-mode gshdsl
To specify the operating mode of the digital subscriber line (DSL) for an ATM interface, use the dsl operating-mode command in interface configuration mode. To restore the default operating mode, use the no form of this command.
dsl operating-mode gshdsl symmetric annex {A | B}
no dsl operating-mode
Syntax Description
Defaults
Region: A
Command Modes
Interface configuration
Command History
Usage Guidelines
This configuration command applies to a specific ATM interface. You must specify the ATM interface before you enter this command.
The ATM interface must be in the shutdown state before you enter this command.
Examples
The following example shows how to configure DSL ATM interface 0/0 to operate in G.SHDSL mode:
Router# configure terminalEnter configuration commands, one per line. End with CNTL/Z.Router(config)# interface atm 0/0Router(config-if)# dsl operating-mode gshdsl symmetric annex ARouter(config-if)# endRouter# clear interface atm 0/1Related Commands
dsl power-cutback
To set the maximum noise margin that can occur on a digital subscriber line (DSL) before a power cutback happens, use the dsl power-cutback command in interface configuration mode. To reset the maximum noise margin to the default value of 31, use the no form of this command.
dsl power-cutback dB
no dsl power-cutback
Syntax Description
Command Default
The maximum noise margin is 31.
Command Modes
Interface configuration
Command History
Usage Guidelines
This command is available on ATM interfaces.
Anytime the maximum noise margin is changed by entering the dsl power-cutback command, the line will retrain.
Examples
The following example specifies a maximum noise margin of 10 decibels on ATM interface 0:
interface ATM 0no ip addressno ip route-cacheno ip mroute-cacheload-interval 30no atm ilmi-keepalivedsl operating-mode autodsl power-cutback 10dsl-mode shdsl symmetric annex
To specify the operating mode of the digital subscriber line (DSL) controller, use the dsl-mode shdsl symmetric annex command in controller configuration mode. To return the DSL to the default Annex A, use the no form of this command.
dsl-mode shdsl symmetric annex mode
Syntax Description
Defaults
The annex defaults to A for North America.
Command Modes
Controller configuration
Command History
Usage Guidelines
This command is used to configure the DSL controller interface to operate in a specified DSL mode and to set regional operating parameters. The shdsl keyword is used to set the mode to SHDSL and configures multirate, high-speed DSL per ITU G.991.2. The symmetric keyword configures the controller to symmetric mode. The annex keyword configures the controller to use regional operating parameters. The regional operating parameters default to North America.
Examples
The following example displays the use of the controller dsl 0/0 command to configure the controller in the router configured on the central office (CO) side. Use the dsl-mode shdsl symmetric annex b command to configure the controller for multirate, high-speed DSL with symmetric mode for European operating parameters.
Router# configure terminalRouter(config)# controller dsl 0/0Router(config-controller)# line-term coRouter(config-controller)# dsl-mode shdsl symmetric annex bRouter(config-controller)# mode atmRouter(config-controller)#00:22:07: %CONTROLLER-5-UPDOWN: Controller DSL 0/0, changed state to downRouter(config-controller)# line-mode 4-wire00:23:25: %CONTROLLER-5-UPDOWN: Controller DSL 0/0, changed state to up00:23:31: %LINK-3-UPDOWN: Interface ATM0/0, changed state to up00:23:32: %LINEPROTO-5-UPDOWN: Line protocol on Interface ATM0/0, changed state to upRelated Commands
ip http digest algorithm
To configure the digest algorithm parameter, use the ip http digest algorithm command in global configuration mode.
ip http digest algorithm [digest-algorithm]
Syntax Description
digest-algorithm
(Optional) The digest algorithm method. The choices for the digest algorithm parameter are MD5 and MD5-sess. MD5 is the default.
Command Default
The digest algorithm parameter is set to MD5.
Command Modes
Global configuration (config)
Command History
Examples
The following example shows how to change the digest algorithm parameter from MD5 to MD5-sess:
Device(config)# ip http digest algorithm md5-sessip mpf
To enable Multi-Processor Forwarding (MPF) on the second CPU of a Cisco 7200 VXR and Cisco 7301 routers, use the ip mpf command in global configuration mode. To disable MPF, use the no form of this command.
ip mpf
no ip mpf
Syntax Description
This command has no arguments or keywords.
Command Default
MPF is enabled by default on the second CPU.
Command Modes
Global configuration
Command History
Usage Guidelines
This command allows you to disable and reenable MPF.
MPF is enabled by default on the second CPU (CPU1). The special MPF image is bundled together with the Cisco IOS image and must be purchased.
Note
Because MPF is enabled by default when the special MPF image is booted up, if CEF is not enabled, MPF is not enabled and boots up with an error message in the error log.
Examples
The following example disables MPF on the second CPU:
Router(config)# no ip mpfThe following configuration example shows a system where CEF is disabled and the resulting error message showing that MPF cannot be enabled:
00:00:13:%MPF-4-NOIPCEF:MPF disabled due to IP CEF disabled00:00:13:%MPF-6-MODULE:CPU 1 switching module is readyThe following configuration example shows that 1) CEF cannot be disabled until MPF is disabled first; and 2) MPF cannot be enabled until CEF is enabled first:
Router(config)# no ip cef%Cannot disable CEF on this platformRouter(config)# no ip mpfRouter(config)# no ip cefRouter(config)# ip mpf%Can not enable MPF when CEF is disabled.Router(config)# ip cefRouter(config)# ip mpfRelated Commands
ip tcp adjust-mss
To adjust the maximum segment size (MSS) value of TCP synchronize/start (SYN) packets going through a router, use the ip tcp adjust-mss command in interface configuration mode. To return the MSS value to the default setting, use the no form of this command.
ip tcp adjust-mss bytes
no ip tcp adjust-mss bytes
Syntax Description
Command Default
The MSS is determined by the originating host.
Command Modes
Interface configuration (config-if)
Command History
Usage Guidelines
When a host (usually a PC) initiates a TCP session with a server, it negotiates the IP segment size by using the MSS option field in the TCP SYN packet. The value of the MSS field is determined by the maximum transmission unit (MTU) configuration on the host. The default MSS value for a PC is 1500 bytes.
The PPP over Ethernet (PPPoE) standard supports an MTU of only 1492 bytes. The disparity between the host and PPPoE MTU size can cause the router in between the host and the server to drop 1500-byte packets and terminate TCP sessions over the PPPoE network. Even if the path MTU (which detects the correct MTU across the path) is enabled on the host, sessions may be dropped because system administrators sometimes disable the Internet Control Message Protocol (ICMP) error messages that must be relayed from the host in order for path MTU to work.
The ip tcp adjust-mss command helps prevent TCP sessions from being dropped by adjusting the MSS value of the TCP SYN packets.
The ip tcp adjust-mss command is effective only for TCP connections passing through the router.
In most cases, the optimum value for the max-segment-size argument is 1452 bytes. This value plus the 20-byte IP header, the 20-byte TCP header, and the 8-byte PPPoE header add up to a 1500-byte packet that matches the MTU size for the Ethernet link.
If you are configuring the ip mtu command on the same interface as the ip tcp adjust-mss command, we recommend that you use the following commands and values:
•
•
Examples
The following example shows the configuration of a PPPoE client with the MSS value set to 1452:
vpdn enableno vpdn logging!vpdn-group 1request-dialinprotocol pppoe!interface Ethernet0ip address 192.168.100.1.255.255.255.0ip tcp adjust-mss 1452ip nat inside!interface ATM0no ip addressno atm ilmi-keepalivepvc 8/35pppoe client dial-pool-number 1!dsl equipment-type CPEdsl operating-mode GSHDSL symmetric annex Bdsl linerate AUTO!interface Dialer1ip address negotiatedip mtu 1492ip nat outsideencapsulation pppdialer pool 1dialer-group 1ppp authentication pap callinppp pap sent-username sohodyn password 7 141B1309000528!ip nat inside source list 101 Dialer1 overloadip route 0.0.0.0.0.0.0.0 Dialer1access-list permit ip 192.168.100.0.0.0.0.255 anyRelated Commands
limit pado service-name
To limit the service-name provided in the PPP over Ethernet Active Discovery Offer (PADO) message to the service-name received in the PPP Protocol over Ethernet Active Discovery Initiation (PADI) message, use the limit pado service-name command in BBA group configuration mode. To disable this configuration, use the no form of this command.
limit pado service-name
no limit pado service-name
Syntax Description
This command has no arguments or keywords.
Command Default
All the configured local PPPoE service names are sent in a PADO message. The service-name sends only the requested service name from PADI in the PADO response.
Command Modes
BBA group configuration (config-bba-group)
Command History
Usage Guidelines
This command when enabled limits the service-name provided in the PADO message to the service name received in the PADI message, regardless of the number of service name configured for the BBA group. The
This command works in conjunction with the service name match command.
Examples
In the following example, the service name provided in the PADO message is limited to the service name received in the PADI message:
Router(config-bba-group)# limit pado service-nameRelated Commands
logging rate-limit
To limit the rate of messages logged per second, use the logging rate-limit command in global configuration mode. To disable the limit, use the no form of this command.
logging rate-limit {number | all number | console {number | all number}} [except severity]
no logging rate-limit
Syntax Description
Command Default
The default is 10 messages logged per second.
Command Modes
Global configuration
Command History
Usage Guidelines
The logging rate-limit command controls the output of messages from the system. Use this command to avoid a flood of output messages. You can select the severity of the output messages and the output rate by using the logging rate-limit command. You can issue the logging rate-limit command at any time. System performance is not negatively affected and may improve when severities and rates of output messages are specified.
You can use logging rate-limit command with or without the logging synchronous line configuration command. For example, if you want to see all severity 0, 1, and 2 messages, use the no logging synchronous command and specify logging rate-limit 10 except 2. By using the two commands together, you cause all messages of 0, 1, and 2 severity to print and limit the less severe ones (higher number than 2) to only 10 per second.
Table 9 shows the numeric severity level, equivalent meaning in text, and a description for error messages.
Cisco 10000 Series Router
To avoid CPU overload and router instability, use the logging rate-limit command to limit the rate at which the Cisco 10000 series router logs system messages. To increase the Point-to-Point Protocol call rate, you can turn off console logging completely using the no logging console command.
Examples
The following example shows how to limit message output to 200 per second:
Router(config)# logging rate-limit 200Related Commands
