Table Of Contents
Broadband Access: PPP and Routed Bridge Encapsulation Commands
ac name
atm route-bridge
bba-group pppoe
class-range
clear pppoe
clear vpdn tunnel pppoe
controller shdsl
dsl equipment-type
dsl linerate
dsl operating-mode
dsl operating-mode (ADSL over ISDN)
dsl operating-mode (G.SHDSL)
dsl power-cutback
ip tcp adjust-mss
max bandwidth
max vc
pppoe-client dial-pool-number
pppoe enable
pppoe limit max-sessions
pppoe limit per-mac
pppoe limit per-vc
pppoe limit per-vlan
pppoe max-sessions
protocol pppoe (ATM VC)
pvc-in-range
range pvc
rbe nasip
sessions max limit
sessions per-mac limit
sessions per-vc limit
sessions per-vlan limit
sessions throttle
show atm svc ppp
show controller shdsl
show dsl interface atm
show pppatm summary
show pppatm trace
shutdown (PVC-in-range)
shutdown (PVC range)
virtual-template (BBA group)
virtual-template pre-clone
vpn service
Broadband Access: PPP and Routed Bridge Encapsulation Commands
Use the commands described in this chapter to configure broadband access using PPP and routed bridge encapsulation.
For information about configuring broadband access using PPP and routed bridge encapsulation, refer to the chapter "Configuring Broadband Access: PPP and Routed Bridge Encapsulation" in the Cisco IOS Wide-Area Networking Configuration Guide.
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
name
|
Name of the access concentrator to be used in PADOs.
|
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
Release
|
Modification
|
12.2(15)T
|
This command was introduced.
|
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 "europa" as the access concentrator name to be used in PADOs:
Related Commands
Command
|
Description
|
bba-group pppoe
|
Creates a PPPoE profile.
|
atm route-bridge
To configure an interface to use the ATM routed bridge encapsulation, use the atm route-bridge interface configuration command.
atm route-bridge protocol
Syntax Description
protocol
|
Protocol to be route-bridged. IP is the only protocol that can be route-bridged using ATM routed bridge encapsulation.
|
Defaults
ATM routed bridge encapsulation is not configured.
Command Modes
Interface configuration
Command History
Release
|
Modification
|
12.0(5)DC
|
This command was introduced.
|
12.1(2)T
|
This command was integrated in Cisco IOS Release 12.1(2)T.
|
Examples
The following example configures ATM routed bridge encapsulation on an interface:
interface atm 4/0.100 point-to-point
ip address 172.16.5.9 255.255.255.0
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
group-name
|
Name of the PPPoE profile.
|
global
|
PPPoE profile that serves as the default profile for any PPPoE port (Ethernet interface, VLAN, or PVC) that has not been assigned a specific PPPoE profile.
|
Defaults
A PPPoE profile is not configured.
Command Modes
Global configuration
Command History
Release
|
Modification
|
12.2(15)T
|
This command was introduced.
|
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 VC class, or an ATM PVC range. PPPoE profiles can also be used with 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.
vc-class atm class-pppoe-global
interface ATM1/0.10 multipoint
range range-pppoe-1 pvc 100 109
protocol pppoe group vpn1
interface ATM1/0.20 multipoint
class-int class-pppoe-global
Related Commands
Command
|
Description
|
encapsulation aal5autoppp virtual-template
|
Enables PPPoA/PPPoE autosense.
|
pppoe enable
|
Enables PPPoE sessions on an Ethernet interface or subinterface.
|
protocol pppoe (ATM VC)
|
Enables PPPoE sessions to be established on PVCs.
|
sessions max limit
|
Configures a PPPoE global profile with the maximum number of PPPoE sessions permitted on a router and sets the PPPoE session-count threshold.
|
sessions per-mac limit
|
Sets the maximum number of PPPoE sessions allowed per MAC address in a PPPoE profile.
|
sessions per-vc limit
|
Sets the maximum number of PPPoE sessions to be established over a VC and sets the PPPoE session-count threshold.
|
sessions per-vlan limit
|
Sets the maximum number of PPPoE sessions per VLAN in a PPPoE profile.
|
class-range
To assign a virtual circuit (VC) class to an ATM permanent virtual circuit (PVC) range, use the class-range PVC range configuration command. To remove the VC class, use the no form of this command.
class-range class-name
no class-range class-name
Syntax Description
class-name
|
Name of the VC class.
|
Defaults
No VC class is assigned to the PVC range.
Command Modes
PVC range configuration
Command History
Release
|
Modification
|
12.1(5)T
|
This command was introduced.
|
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:
! The following commands apply classA to an ATM PVC range:
interface atm 6/0.110 multipoint
range range-pppoa-1 pvc 0/102 0/199
Related Commands
Command
|
Description
|
abr
|
Selects ABR QoS and configures the output peak cell rate and output minimum guaranteed cell rate for an ATM PVC.
|
broadcast
|
Configures broadcast packet duplication and transmission for an ATM PVC.
|
cbr
|
Configures the CBR for the ATM CES for an ATM PVC.
|
class-vc
|
Assigns a VC class to an ATM PVC.
|
encapsulation atm-dxi
|
Configures the AAL and encapsulation type for an ATM PVC.
|
ilmi manage
|
Enables ILMI management on an ATM PVC.
|
inarp
|
Configures the Inverse ARP time period for an ATM PVC.
|
oam-pvc
|
Enables end-to-end F5 OAM loopback cell generation and OAM management for an ATM PVC.
|
oam retry
|
Configures parameters related to OAM management for an ATM PVC.
|
protocol (ATM)
|
Configures a protocol for an ATM PVC. A PVC within a PVC range supports only the protocols that do not require static map configuration.
|
show pppatm summary
|
Deactivates an individual PVC within a PVC range.
|
shutdown (PVC range)
|
Deactivates an ATM PVC range.
|
ubr
|
Configures an UBR QoS and specifies the output PCR for an ATM PVC range.
|
ubr+
|
Configures an UBR QoS and specifies the output PCR and output minimum guaranteed cell rate for an ATM PVC range.
|
vbr-nrt
|
Configures the VBR-NRT QoS and specifies output PCR, output sustainable cell rate, and output maximum burst cell size for an ATM PVC range.
|
vbr-rt
|
Configures the real-time VBR for an ATM PVC range.
|
clear pppoe
To clear PPP over Ethernet (PPPoE) sessions, use the clear pppoe command in privileged EXEC mode.
clear pppoe {interface interface-type interface-number [vc {[vpi/]vci | virtual-circuit-name}] |
rmac mac-address [sid session-id] | all}
Syntax Description
interface interface-type interface-number
|
Interface keyword followed by the interface type and number.
|
vc [vpi/]vci virtual-circuit-name
|
(Optional) Virtual circuit (VC) keyword followed by a virtual path identifier (VPI), virtual channel identifier (VCI), and VC name. A slash (/) follows the VPI.
|
rmac mac-address
|
(Optional) Remote Media Access Control (MAC) address.
|
sid session-id
|
(Optional) Session identifier.
|
all
|
(Optional) Combines all keywords.
|
Command Modes
Privileged EXEC
Command History
Release
|
Modification
|
12.2(13)T
|
This command was introduced.
|
Examples
The following example clears all PPPoE sessions:
clear vpdn tunnel pppoe
To clear all PPP over Ethernet (PPPoE) sessions, use the clear vpdn tunnel pppoe command in privileged EXEC configuration mode.
clear vpdn tunnel pppoe
Syntax Description
This command has no arguments or keywords.
Command Modes
Privileged EXEC
Command History
Release
|
Modification
|
12.1(1)T
|
This command was introduced.
|
Usage Guidelines
Use this command to clear all PPPoE sessions on the device. To clear a specific PPPoE session or set of sessions, use the clear pppoe command.
Examples
The following example clears all PPPoE sessions on the device:
Router# clear vpdn tunnel pppoe
Related Commands
Command
|
Description
|
clear pppoe
|
Clears PPPoE sessions.
|
controller shdsl
To configure a controller for single-pair high-bit-rate digital subscriber line (SHDSL) mode, use the controller shdsl command in global configuration mode.
controller shdsl number
Syntax Description
number
|
Contoller number. The valid controller number is 0.
|
Defaults
Controller number: 0
Command Modes
Global configuration
Command History
Release
|
Modification
|
11.3(5)AAA
|
This command was introduced.
|
12.2(8)T
|
This command was implemented on Cisco IAD2420 series IADs.
|
Usage Guidelines
This command is used to configure the controller mode and the controller number.
Examples
The following example enters SHDSL controller mode on controller number 0 and configures ATM mode on a Cisco IAD2420 series IAD:
Router# controller shdsl 0
Related Commands
Command
|
Description
|
show controller shdsl
|
Displays the controller status and statistics.
|
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
co
|
Configures the DSL ATM interface to function as central office equipment.
|
cpe
|
Configures the DSL ATM interface to function as customer premises equipment.
|
ignore-error-duration seconds
|
Sets the number of seconds for which errors are ignored. The valid range is from 15 to 30. The default is 0.
|
Defaults
cpe
Seconds: 0
Command Modes
Interface configuration
Command History
Release
|
Modification
|
12.2(4)XL
|
This command was integrated into Cisco IOS Release 12.2(4)XL on the G.SHDSL WIC on the Cisco 2600 series routers.
|
12.2(8)T
|
This command was integrated into Cisco IOS Release 12.2(8)T on the G.SHDSL WIC on the Cisco 2600 series and Cisco 3600 series routers.
|
12.2(13)T
|
The ignore-error-duration keyword was added to interoperate with metalink chipset DSLAMs.
|
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 terminal
Enter configuration commands, one per line. End with CNTL/Z.
Router(config)# interface atm 1/1
Router(config-if)# dsl equipment-type co
Router# clear interface atm 0/1
Related Commands
Command
|
Description
|
dsl linerate
|
Specifies a line rate for the DSL ATM interface.
|
dsl operating-mode (G.SHDSL)
|
Specifies an operating mode of the DSL ATM interface.
|
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
kbps
|
Line rate, in kilobits per second, for the DSL ATM interface. Allowable entries are 72, 136, 200, 264, 392, 520, 776, 1032, 1160, 1544, 2056, and 2312.
|
auto
|
Configures the DSL ATM interface to automatically train for an optimal line rate by negotiating with the far-end digital subscriber line access multiplexer (DSLAM) or WAN interface card (WIC).
|
Defaults
The DSL ATM interface automatically synchronizes its line rate with the far-end DSLAM or WIC.
Command Modes
Interface configuration
Command History
Release
|
Modification
|
12.2(4)XL
|
This command was integrated into Cisco IOS Release 12.2(4)XL on the G.SHDSL WIC on the Cisco 2600 series routers.
|
12.2(8)T
|
This command was integrated into Cisco IOS Release 12.2(8)T on the G.SHDSL WIC on the Cisco 2600 series and Cisco 3600 series routers.
|
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 terminal
Enter configuration commands, one per line. End with CNTL/Z.
Router(config)# interface atm 0/1
Router(config-if)# dsl linerate 1040
Router# clear interface atm 0/1
Related Commands
Command
|
Description
|
dsl equipment-type
|
Configures the DSL ATM interface to function as CO equipment or CPE.
|
dsl operating-mode (G.SHDSL)
|
Specifies an operating mode of the DSL ATM interface.
|
dsl operating-mode
Caution 
This command is for testing or lab environments only. Using a configuration other than the default configuration for the digital subscriber line (DSL) operating mode can lead to unpredictable behavior on the asymmetric digital subscriber line (ADSL) line.
To modify the operating mode of the digital subscriber line for an ATM interface, use the dsl operating-mode command in interface configuration mode. To reset the operating mode to the default, use the no form of this command.
dsl operating-mode {auto | ansi-dmt | itu-dmt | splitterless}
no dsl operating-mode {auto | ansi-dmt | itu-dmt}
Syntax Description
auto
|
Configures the ADSL line after auto-negotiating with the DSL access multiplexer (DSLAM) located at the central office. This is the default operating mode.
|
ansi-dmt
|
Configures the ADSL line to use the ANSI T1.413 Issue 2 mode.
|
itu-dmt
|
Configures the ADSL line to use the G.992.1 mode.
|
splitterless
|
Configures the ADSL line to use the G.992.2 (G.lite) mode.
|
Defaults
DSL operating mode: auto
Command Modes
Interface configuration
Command History
Release
|
Modification
|
12.1(3)XJ
|
This command was introduced on Cisco 1700 series routers.
|
12.2(2)T
|
This command was integrated into Cisco IOS Release 12.2(2)T.
|
12.1(5)YB
|
Support for this command was added to Cisco 2600 series and Cisco 3600 series routers.
|
12.1(5)XR1
|
Support for this command was added to the Cisco IAD2420 series.
|
12.2(4)T
|
This command was integrated into Cisco IOS Release 12.2(4)T.
|
Usage Guidelines
This configuration command applies to a specific ATM interface. The interface to which it applies must be specified before using the command.
This command is supported only when the 1-Port ADSL WAN interface card is installed.
Caution 
This command is for testing or lab environments only. Using a configuration other than the default configuration for the DSL operating mode can lead to unpredictable behavior on the ADSL line.
Examples
In the following example, the ADSL line is configured to use the G.992.1 mode:
Router# configure terminal
Enter configuration commands, one per line. End with CNTL/Z.
Router(config)# interface atm 0
Router(config-if)# dsl operating-mode itu-dmt
Related Commands
Command
|
Description
|
show dsl interface atm
|
Displays the ADSL-specific information for a specified ATM interface.
|
dsl 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
annexb-ur2
|
Specifies the Deutsche Telekom U-R2 (interface) mode, which transmits and receives ADSL signals according to the ITU-T G.992.1 Annex B standard. This mode supports upstream bins (analog modems) numbered 33 to 53 and downstream bins numbered 64 to 255.
|
etsi
|
Specifies Alcatel proprietary ETSI mode, which supports upstream bins numbered 29 to 48 and downstream bins numbered 64 to 255.
|
auto
|
Configures a modem to switch between etsi mode and annexb-ur2 mode for connection, following the sequence described in the "Usage Guidelines" section.
|
Defaults
Mode: etsi
Command Modes
Interface configuration
Command History
Release
|
Modification
|
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 terminal
Enter configuration commands, one per line. End with CNTL/Z.
Router(config)# interface atm 0
Router(config-if)# dsl operating-mode etsi
Related Commands
Command
|
Description
|
show dsl interface atm
|
Displays information specific to the ADSL for a specified ATM interface.
|
dsl operating-mode (G.SHDSL)
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
gshdsl
|
Configures the DSL ATM interface to operate in multirate high-speed mode per ITU G.991.2.
|
symmetric
|
Configures the DSL ATM interface to operate in symmetrical mode per ITU G.991.2.
|
annex
|
Specifies the regional operating parameters.
|
A
|
Configures the regional operating parameters for North America. This value is the default.
|
B
|
Configures the regional operating parameters for Europe.
|
Defaults
Region: A
Command Modes
Interface configuration
Command History
Release
|
Modification
|
12.1(3)XJ
|
This command was introduced on the Cisco 1700 series routers.
|
12.2(2)T
|
This command was integrated into Cisco IOS Release 12.2(2)T for the Cisco 1700 series routers.
|
12.2(4)XL
|
This command was integrated into Cisco IOS Release 12.2(4)XL for the G.SHDSL WIC on the Cisco 2600 series routers.
|
12.2(8)T
|
This command was integrated into Cisco IOS Release 12.2(8)T on the G.SHDSL WIC on the Cisco 2600 series and Cisco 3600 series routers.
|
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 terminal
Enter configuration commands, one per line. End with CNTL/Z.
Router(config)# interface atm 0/0
Router(config-if)# dsl operating-mode gshdsl symmetric annex A
Router# clear interface atm 0/1
Related Commands
Command
|
Description
|
dsl equipment-type
|
Configures the DSL ATM interface to function as CO equipment or CPE.
|
dsl linerate
|
Specifies a line rate for the DSL ATM interface.
|
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
dB
|
Maximum noise margin in decibels. Range is 1 to 30.
|
Command Default
The maximum noise margin is 31.
Command Modes
Interface configuration
Command History
Release
|
Modification
|
12.2T
|
This command was introduced.
|
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:
ip tcp adjust-mss
To adjust the maximum segment size (MSS) value of TCP 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 max-segment-size
no ip tcp adjust-mss max-segment-size
Syntax Description
max-segment-size
|
Maximum segment size, in bytes. The range is from 500 to 1460.
|
Defaults
If the ip tcp adjust-mss command is not configured, the MSS is determined by the originating host.
Command Modes
Interface configuration
Command History
Release
|
Modification
|
12.2(4)T
|
This command was introduced.
|
12.2(8)T
|
This command was changed from ip adjust-mss to ip tcp adjust-mss.
|
12.2(27)SBA
|
This command was integrated into Cisco IOS Release 12.2(27)SBA.
|
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 a 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 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, it is recommended that you use the following commands and values:
•
ip tcp adjust-mss 1452
•
ip mtu 1492
Examples
The following example shows the configuration of a PPPoE client with the MSS value set to 1452:
ip address 192.168.100.1.255.255.255.0
pppoe client dial-pool-number 1
dsl operating-mode GSHDSL symmetric annex B
ppp authentication pap callin
ppp pap sent-username sohodyn password 7 141B1309000528
ip nat inside source list 101 Dialer1 overload
ip route 0.0.0.0.0.0.0.0 Dialer1
access-list permit ip 192.168.100.0.0.0.0.255 any
Related Commands
Command
|
Description
|
ip mtu
|
Sets the MTU size of IP packets sent on an interface.
|
max bandwidth
To specify the total amount of outgoing bandwidth available to SVCs in the current configuration, use the max bandwidth interface-ATM-VC configuration command. To remove the current bandwidth setting, use the no form of this command.
max bandwidth kbps
no max bandwidth kbps
Syntax Description
kbps
|
Total amount of outgoing bandwidth in kilobits per second available to all SVCs in the current configuration.
|
Defaults
No default behavior or values.
Command Modes
Interface-ATM-VC configuration
Command History
Release
|
Modification
|
12.1(3)T
|
This command was introduced.
|
Usage Guidelines
Only the guaranteed cell rate of an SVC is counted toward the maximum bandwidth.
Examples
In following example, an SVC called "anna" on ATM interface 2/0/0 is configured using the max bandwidth command to allow a maximum of 50 Mbps of bandwidth to be used by all of the SVCs in this configuration:
protocol ppp virtual-template 1
Related Commands
Command
|
Description
|
max vc
|
Specifies the maximum number of SVCs that can be established using the current configuration.
|
max vc
To specify the maximum number of switched virtual circuits (SVCs) that can be established using the current configuration, use the max vc command in interface-ATM-VC configuration mode. To restore the maximum number of SVCs to the default setting, use the no form of this command.
max vc number
no max vc number
Syntax Description
number
|
Maximum number of SVCs to be established using the current SVC configuration.
|
Defaults
4096 SVCs
Command Modes
Interface-ATM-VC configuration
Command History
Release
|
Modification
|
12.1(3)T
|
This command was introduced.
|
Examples
In following example, an SVC called "anna" on ATM interface 2/0/0 is configured using the max vc command to allow a maximum of 100 SVCs to be established using this configuration:
protocol ppp virtual-template 1
Related Commands
Command
|
Description
|
max bandwidth
|
Specifies the maximum amount of bandwidth available to all SVCs in the current configuration.
|
svc
|
Creates an ATM SVC.
|
pppoe-client dial-pool-number
To configure a PPP over Ethernet (PPPoE) client and to specify dial-on-demand routing (DDR) functionality, use the pppoe-client dial-pool-number command in either interface configuration mode or ATM virtual circuit configuration mode. To disable any configured functionality, use the no form of this command.
pppoe-client dial-pool-number number [dial-on-demand]
no pppoe-client dial-pool-number number [dial-on-demand]
Syntax Description
number
|
Unique number of a dial group configured with the dialer-group dialer interface command.
|
dial-on-demand
|
(Optional) Enables DDR functionality for the PPPoE connection.
|
Defaults
A PPPoE client is not configured, and DDR functionality is disabled.
Command Modes
Interface configuration
ATM virtual circuit configuration
Command History
Release
|
Modification
|
12.1(3)XG
|
This command was introduced.
|
12.2(2)T
|
This command was integrated into Cisco IOS Release 12.2(2)T.
|
12.2(13)T
|
The dial-on-demand keyword was added to allow the configuration of DDR interesting traffic control list functionality.
|
Usage Guidelines
One PVC will support only one PPPoE client. Multiple PPPoE clients can run concurrently on different permanent virtual circuits (PVCs), but each PPPoE client must use a separate dialer interface and a separate dialer pool.
Use this command to configure dial-on-demand routing (DDR) interesting traffic control list functionality of the dialer interface with a PPP over Ethernet (PPPoE) client. When the DDR functionality is configured for this command, the following DDR commands must also be configured: dialer-group, dialer hold-queue, dialer idle-timeout, and dialer-list.
Tips for Configuring the Dialer Interface
If you are configuring a hard-coded IP address under the dialer interface, you can configure a default IP route using the ip route command as follows:
ip route 0.0.0.0 0.0.0.0 dialer1
But if you are configuring a negotiated IP address using the ip address negotiated command under the dialer interface, you must configure a default IP route using the ip route command as follows:
ip route 0.0.0.0 0.0.0.0 dialer1 permanent
The reason is that the dialer interface will lose its IP address when a PPPoE session is brought down (even if the dialer does not go down), and hence the route removal routine will take effect and remove all IP routes pointed at the dialer interface, even the default IP route. Although the default IP route will be added back about one minute later by IP background processes, you may risk losing incoming packets during the interval.
Examples
PPPoE Client DDR Idle-Timer on an Ethernet Interface
The following example shows how to configure the PPPoE client DDR idle-timer on an Ethernet interface and includes the required DDR commands:
pppoe-client dial-pool-number 1 dial-on-demand
dialer idle-timeout 180 either
dialer-list 1 protocol ip permit
ip route 0.0.0.0 0.0.0.0 Dialer1
PPPoE client DDR Idle-Timer on an ATM PVC
The following example shows how to configure the PPPoE client DDR idle-timer on an ATM PVC interface and includes the required DDR commands:
pppoe-client dial-pool-number 1 dial-on-demand
dialer idle-timeout 180 either
dialer-list 1 protocol ip permit
ip route 0.0.0.0 0.0.0.0 Dialer1
Related Commands
Command
|
Description
|
debug vpdn pppoe-data
|
Displays PPPoE session data packets.
|
debug vpdn pppoe-errors
|
Displays PPPoE protocol errors that prevent a session from being established or errors that cause an established session to be terminated.
|
debug vpdn pppoe-events
|
Displays PPPoE protocol messages about events that are part of normal session establishment or shutdown.
|
debug vpdn pppoe-packets
|
Displays each PPPoE protocol packet exchanged.
|
dialer-group
|
Controls access by configuring a virtual access interface to belong to a specific dialing group.
|
dialer hold-queue
|
Allows interesting outgoing packets to be queued until a modem connection is established.
|
dialer idle-timeout
|
Specifies the idle time before the line is disconnected.
|
dialer-list
|
Defines a DDR dialer list to control dialing by protocol or by a combination of protocol and an access list.
|
pppoe enable
To enable PPP over Ethernet (PPPoE) sessions on an Ethernet interface or subinterface, use the pppoe enable command in interface configuration mode. To disable PPPoE, use the no form of this command.
pppoe enable [group group-name]
no pppoe enable
Syntax Description
group
|
(Optional) Specifies that a PPPoE profile will be used by PPPoE sessions on the interface.
|
group-name
|
(Optional) Name of the PPPoE profile to be used by PPPoE sessions on the interface.
|
Defaults
PPPoE is disabled by default.
Command Modes
Interface configuration
Command History
Release
|
Modification
|
12.1(2)T
|
This command was introduced.
|
12.1(5)T
|
This command was modified to enable PPPoE on IEEE 802.1Q encapsulated VLAN interfaces.
|
12.2(15)T
|
The group option was added.
|
Usage Guidelines
If a PPPoE profile is not specified by using the group option, PPPoE sessions will be established using values from the global PPPoE profile. PPPoE profiles must be configured using the bba-group pppoe command.
Examples
PPPoE on an Ethernet Interface Example
The following example enables PPPoE sessions on Ethernet interface 1/0. PPPoE sessions will be established using the PPPoE parameters in the global PPPoE profile.
PPPoE on an 802.1Q VLAN Subinterface Example
The following example shows how to enable PPPoE on an 802.1Q VLAN subinterface. PPPoE sessions will be established using the PPPoE parameters in PPPoE profile "vpn1".
Related Commands
Command
|
Description
|
bba-group pppoe
|
Creates a PPPoE profile.
|
debug pppoe
|
Displays debugging information for PPPoE sessions.
|
sessions max limit
|
Configures a PPPoE global profile with the maximum number of PPPoE sessions permitted on a router and sets the PPPoE session-count threshold.
|
sessions per-vlan limit
|
Specifies the maximum number of PPPoE sessions under each VLAN.
|
pppoe limit max-sessions
To specify the maximum number of PPP over Ethernet (PPPoE) sessions that will be permitted on a router, use the pppoe limit max-sessions command in VPDN group configuration mode. To remove this specification, use the no form of this command.
pppoe limit max-sessions number-of-sessions
no pppoe limit max-sessions
Syntax Description
number-of-sessions
|
Maximum number of PPPoE sessions that will be permitted on the router. The range is from 0 to the maximum number of interfaces on the router.
|
Defaults
Maximum number-of-sessions is not set.
Command Modes
VPDN group configuration
Command History
Release
|
Modification
|
12.2(1)DX
|
This command was introduced.
|
12.2(2)DD
|
This command was integrated into Cisco IOS Release 12.2(2)DD.
|
12.2(4)B
|
This command was integrated into Cisco IOS Release 12.2(4)B.
|
12.2(13)T
|
This command was integrated into Cisco IOS Release 12.2(13)T.
|
Usage Guidelines
PPPoE session limits configured using the pppoe limit per-vc, pppoe limit per-vlan, pppoe max-sessions, pppoe max-sessions (VC), and pppoe max-sessions (subinterface) commands take precedence over limits configured for the router using the pppoe limit max-sessions command.
Examples
The following example shows a limit of 100 PPPoE sessions configured for the router.
pppoe limit max-sessions 100
Related Commands
Command
|
Description
|
debug vpdn pppoe-errors
|
Displays PPPoE protocol errors that prevent a session from being established or errors that cause an established session to be closed.
|
pppoe limit per-mac
|
Specifies the maximum number of PPPoE sessions to be sourced from a MAC address.
|
pppoe limit per-vc
|
Specifies the maximum number of PPPoE sessions permitted on all VCs.
|
pppoe limit per-vlan
|
Specifies the maximum number of PPPoE sessions permitted on a VLAN.
|
pppoe max-sessions
|
Specifies the maximum number of PPPoE sessions permitted on an ATM PVC, PVC range, VC class, or Ethernet subinterface.
|
pppoe limit per-mac
To specify the maximum number of PPPoE sessions to be sourced from a MAC address, use the pppoe limit per-mac command in VPDN configuration mode.
pppoe limit per-mac number
Syntax Description
number
|
Maximum number of PPPoE sessions that can be sourced from a MAC address.
|
Defaults
100 sessions
Command Modes
VPDN configuration
Command History
Release
|
Modification
|
12.1(1)T
|
This command was introduced.
|
Examples
The following example sets a limit of 10 sessions to be sourced from a MAC address:
Related Commands
Command
|
Description
|
pppoe limit per-vc
|
Specifies the maximum number of PPPoE sessions to be established over a VC.
|
pppoe limit per-vlan
|
Specifies the maximum number of PPPoE sessions under each VLAN.
|
pppoe limit per-vc
To specify the maximum number of PPPoE sessions to be established over a VC, use the pppoe limit per-vc command in VPDN configuration mode.
pppoe limit per-vc number
Syntax Description
number
|
Maximum number of PPPoE sessions that can be established over an ATM PVC.
|
Defaults
100 sessions
Command Modes
VPDN configuration
Command History
Release
|
Modification
|
12.1(1)T
|
This command was introduced.
|
Examples
The following example sets a limit of 10 sessions to be established over a VC:
Related Commands
Command
|
Description
|
pppoe limit max-sessions
|
Specifies the maximum number of PPPoE sessions to be sourced from a MAC address.
|
pppoe limit per-vlan
|
Specifies the maximum number of PPPoE sessions under each VLAN.
|
pppoe limit per-vlan
To specify the maximum number of PPP over Ethernet (PPPoE) sessions permitted under each virtual LAN (VLAN), use the pppoe limit per-vlan VPDN configuration command. To remove this specification, use the no form of this command.
pppoe limit per-vlan number
no pppoe limit per-vlan
Syntax Description
number
|
Maximum number of PPP over Ethernet sessions permitted under each VLAN.
|
Defaults
100 PPPoE sessions per VLAN
Command Modes
VPDN configuration
Command History
Release
|
Modification
|
12.1(5)T
|
This command was introduced.
|
Usage Guidelines
If the pppoe max-session command is configured on a VLAN, that command will take precedence over the pppoe limit per-vlan command. The pppoe limit per-vlan command applies to all VLANs on which the pppoe max-session command has not been configured.
The pppoe limit per-vlan command must be configured after the accept dial-in VPDN group has been configured using the accept-dialin VPDN configuration command.
Examples
The following example shows a maximum of 200 PPPoE sessions configured for an 802.1Q VLAN subinterface:
interface FastEthernet0/0.10
Related Commands
Command
|
Description
|
accept dial-in
|
Creates an accept dial-in VPDN subgroup.
|
debug vpdn pppoe-data
|
Displays data packets of PPPoE sessions.
|
debug vpdn pppoe-error
|
Displays PPPoE protocol errors that prevent a session from being established or errors that cause an established session to be closed.
|
debug vpdn pppoe-events
|
Displays PPPoE protocol messages about events that are part of normal session establishment or shutdown.
|
debug vpdn pppoe-packet
|
Displays each PPPoE protocol packet exchanged.
|
pppoe enable
|
Enables PPPoE sessions on an Ethernet interface.
|
pppoe limit max-sessions
|
Specifies the maximum number of PPPoE sessions to be sourced from a MAC address.
|
pppoe limit per-vc
|
Specifies the maximum number of PPPoE sessions to be established over a VC.
|
pppoe max-sessions
|
Specifies the maximum number of PPPoE sessions permitted under a VLAN.
|
pppoe max-sessions
To specify the maximum number of PPP over Ethernet (PPPoE) sessions that will be permitted on an ATM permanent virtual circuit (PVC), PVC range, virtual circuit (VC) class, or Ethernet subinterface, use the pppoe max-sessions command in the appropriate mode. To remove this specification, use the no form of this command.
pppoe max-sessions number-of-sessions
no pppoe max-sessions
Syntax Description
number-of-sessions
|
Maximum number of PPPoE sessions that will be permitted.
Note The PPPoE session limit in the case of a PVC range applies to each PVC in the range. This limit is not cumulative on all PVCs belonging to the range.
|
Defaults
Maximum number of sessions is not set.
Command Modes
Ethernet subinterface configuration
Interface-ATM-VC configuration
VC-class configuration
ATM PVC range configuration
PVC-in-range configuration
Command History
Release
|
Modification
|
12.1(5)T
|
This command was introduced.
|
12.2(4)T
|
This command was modified to limit PPPoE sessions on ATM PVCs, PVC ranges, and VC classes.
|
Usage Guidelines
PPPoE sessions can be limited in the following ways:
•
The pppoe limit max-sessions command limits the total number of PPPoE sessions on the router, regardless of the type of medium the sessions are using.
•
The pppoe limit per-mac command limits the number of PPPoE sessions that can be sourced from a single MAC address. This limit also applies to all PPPoE sessions on the router.
•
The pppoe limit per-vc and pppoe limit per-vlan commands limit the number of PPPoE sessions on all PVCs or VLANs on the router. The pppoe max-sessions command limits the number of PPPoE sessions on a specific PVC or VLAN. Limits created for a specific PVC or VLAN using the pppoe max-session command take precedence over the global limits created with the pppoe limit per-vc and pppoe limit per-vlan commands.
PPPoE session limits created on an ATM PVC take precedence over limits created in a VC class or ATM PVC range.
PPPoE session limits created in an ATM PVC range take precedence over limits created in a VC class.
Examples
Ethernet Subinterface Example
The following example shows a limit of 200 PPPoE sessions configured for the subinterface:
interface FastEthernet 0/0.10
ATM PVC Example
The following example shows a limit of 10 PPPoE sessions configured for the PVC:
interface ATM1/0.102 multipoint
VC Class Example
The following example shows a limit of 20 PPPoE sessions that will be permitted per PVC in the VC class called "main":
ATM PVC Range Example
The following example shows a limit of 30 PPPoE sessions that will be permitted per PVC in the PVC range called "range-1":
interface atm 6/0.110 multipoint
range range-1 pvc 100 4/199
protocol ppp virtual-template 2
Individual PVC Within a PVC Range Example
The following example shows a limit of 10 PPPoE sessions configured for "pvc1", which is part of the ATM PVC range called "range1":
interface atm 6/0.110 multipoint
range range1 pvc 100 4/199
Related Commands
Command
|
Description
|
debug vpdn pppoe-errors
|
Displays PPPoE protocol errors that prevent a session from being established or errors that cause an established session to be closed.
|
pppoe limit max-sessions
|
Specifies the maximum number of PPPoE sessions that will be permitted on a router.
|
pppoe limit per-mac
|
Specifies the maximum number of PPPoE sessions to be sourced from a MAC address.
|
pppoe limit per-vc
|
Specifies the maximum number of PPPoE sessions permitted on all VCs.
|
pppoe limit per-vlan
|
Specifies the maximum number of PPPoE sessions permitted on a VLAN.
|
protocol pppoe (ATM VC)
To enable PPP over Ethernet (PPPoE) sessions to be established on permanent virtual circuits (PVCs), use the protocol pppoe command in the appropriate configuration mode. To disable PPPoE, use the no form of this command.
protocol pppoe [group group-name]
no protocol pppoe [group group-name]
Syntax Description
group
|
(Optional) Specifies a PPPoE profile to be used by PPPoE sessions on the interface.
|
group-name
|
(Optional) Name of the PPPoE profile to be used by PPPoE sessions on the interface.
|
Defaults
PPPoE is not enabled.
Command Modes
ATM VC configuration
ATM VC class configuration
ATM PVC range configuration
ATM PVC-in-range configuration
Command History
Release
|
Modification
|
12.2(15)T
|
This command was introduced.
|
Usage Guidelines
If a PPPoE profile is not specified by using the group option, PPPoE sessions will be established using values from the global PPPoE profile. PPPoE profiles must be configured using the bba-group pppoe command.
Examples
The following example shows PPPoE configured in virtual circuit (VC) class "class-pppoe-global" and on the range of PVCs from 100 to 109. PVCs that use VC class "class-pppoe-global" will establish PPPoE sessions using the parameters configured in the global PPPoE profile. PVCs in the PVC range will use PPPoE parameters defined in PPPoE profile "vpn1".
vc-class atm class-pppoe-global
interface ATM1/0.10 multipoint
range range-pppoe-1 pvc 100 109
protocol pppoe group vpn1
interface ATM1/0.20 multipoint
class-int class-pppoe-global
Related Commands
Command
|
Description
|
bba-group pppoe
|
Creates a PPPoE profile.
|
debug pppoe
|
Displays debugging information for PPPoE sessions.
|
sessions max limit
|
Configures a PPPoE global profile with the maximum number of PPPoE sessions permitted on a router and sets the PPPoE session-count threshold.
|
sessions per-mac limit
|
Sets the maximum number of PPPoE sessions allowed per MAC address in a PPPoE profile.
|
sessions per-vc limit
|
Sets the maximum number of PPPoE sessions to be established over a VC and sets the PPPoE session-count threshold.
|
pvc-in-range
To configure an individual permanent virtual circuit (PVC) within a PVC range, use the pvc-in-range PVC range configuration command. To delete the individual PVC configuration, use the no form of this command.
pvc-in-range [pvc-name] [vpi/vci]
no pvc-in-range [pvc-name] [vpi/vci]
Syntax Description
pvc-name
|
(Optional) Name given to the PVC. The PVC name can have a maximum of 15 characters.
|
vpi/
|
(Optional) ATM network virtual path identifier (VPI) for this PVC. In the absence of the "/" and a vpi value, the vpi value defaults to 0. The vpi value ranges from 0 to 255.
|
vci
|
(Optional) ATM network virtual channel identifier (VCI) for this PVC. The vci value ranges from 32 to 2047.
|
Defaults
No default behavior or values.
Command Modes
PVC range configuration
Command History
Release
|
Modification
|
12.1(5)T
|
This command was introduced.
|
Usage Guidelines
The pvc-in-range command defines an individual PVC within a PVC range and enables PVC-in-range configuration mode.
Examples
In the following example, a PVC called "pppoa" is deactivated. The PVC "pppoa" is an individual PVC within a configured PVC range.
Related Commands
Command
|
Description
|
range pvc
|
Defines a range of ATM PVCs.
|
range pvc
To define a range of ATM permanent virtual circuits (PVCs), use the range pvc subinterface configuration command. To delete the range of ATM PVCs, use the no form of this command.
range [range-name] pvc start-vpi/start-vci end-vpi/end-vci
no range [range-name] pvc
Syntax Description
range-name
|
(Optional) Name of the range. The range name can be a maximum of 15 characters.
|
start-vpi/
|
Beginning value for a range of virtual path identifiers (VPIs). In the absence of the "/" and a vpi value, the vpi value defaults to 0. The vpi value ranges from 0 to 255.
|
start-vci/
|
Beginning value for a range of virtual channel identifiers (VCIs). The vci value ranges from 32 to 65535.
|
end-vpi
|
End value for a range of virtual path identifiers (VPIs). In the absence of an end-vpi value, the end-vpi value defaults to the start-vpi value.The vpi value ranges from 0 to 255.
|
end-vci
|
End value for a range of virtual channel identifiers (VCIs). The vci value ranges from 32 to 65535.
|
Defaults
An ATM PVC range is not configured.
Command Modes
Subinterface configuration
Command History
Release
|
Modification
|
12.1(5)T
|
This command was introduced.
|
Usage Guidelines
The range pvc command defines a range of PVCs and enables PVC range configuration mode.
The number of PVCs in a range can be calculated using the following formula:
number of PVCs = (end-vpi - start-vpi + 1) x (end-vci - start-vci +1).
The start-vpi argument may be omitted if it is zero. The end_vpi argument may be omitted, but if it is omitted, it is assigned the value of start-vpi. The end-vpi and end-vci arguments are always greater than or equal to start-vpi and start-vci respectively.
When applied to multipoint subinterfaces, the range pvc command creates a range of ATM PVCs. When applied to point-to-point subinterfaces, the range pvc command creates range of PVCs and a corresponding range of point-to-point subinterfaces.
For point-to-point subinterfaces, subinterface numbering begins with the subinterface on which the PVC range is configured and increases sequentially through the range.
Examples
ATM PVC Range Example
In the following example, 100 PVCs with VCI values from 100 to 199 for each VPI value from 0 to 4 are created for a PVC range called "range-pppoa-1". This configuration creates a total of 500 PVCs in the range. PVC parameters are then configured for the range.
interface atm 6/0.110 multipoint
range range-pppoa-1 pvc 100 4/199
class-range class-pppoa-1
protocol ppp virtual-Template 2
Subinterface Grouping by PVC Range for Routed Bridge Encapsulation Example
In the following example, a PVC range called "range1" is created with a total of 100 PVCs in the range. A point-to-point subinterface will be created for each PVC in the range. ATM routed bridge encapsulation is also configured.
interface atm 6/0.200 point-to-point
range range1 pvc 1/200 1/299
Related Commands
Command
|
Description
|
pvc-in-range
|
Configures an individual PVC within a PVC range.
|
rbe nasip
To specify the IP address of an interface on the Dynamic Host Configuration Protocol (DHCP) relay agent that will be sent to the DHCP server via the agent remote ID option, use the rbe nasip command in global configuration mode. To remove this specification, use the no form of this command.
rbe nasip source-interface
no rbe nasip source-interface
Syntax Description
source-interface
|
The type and number of one of the interfaces on the router. The IP address for this interface will be forwarded in the agent remote ID option and can be used by the DHCP server to uniquely identify the DHCP relay agent.
|
Defaults
No IP address is specified.
Command Modes
Global configuration
Command History
Release
|
Modification
|
12.2(2)T
|
This command was introduced.
|
Usage Guidelines
The rbe nasip command is used to configure support for the DHCP relay agent information option (option 82) for ATM routed bridge encapsulation (RBE).
Support for the DHCP relay agent information option must be configured on the DHCP relay agent using the ip dhcp relay information option command in order for the rbe nasip command to be effective.
Examples
In the following example, support for DHCP option 82 is enabled on the DHCP relay agent by the use of the ip dhcp relay agent information option command. The rbe nasip command configures the router to forward the IP address for Loopback0 to the DHCP server. ATM routed bridge encapsulation is configured on ATM subinterface 4/0.1.
ip dhcp-server 170.16.1.2
ip dhcp relay information option
ip address 11.1.1.129 255.255.255.192
interface ATM4/0.1 point-to-point
ip helper-address 170.16.1.2
Related Commands
Command
|
Description
|
ip dhcp relay information option
|
Enables the system to insert the DHCP relay agent information option in forwarded BOOT REQUEST messages to a Cisco IOS DHCP server.
|
sessions max limit
To configure the PPP over Ethernet (PPPoE) global profile with the maximum number of PPPoE sessions that will be permitted on a router and to set the PPPoE session-count threshold at which a Simple Network Managment Protocol (SNMP) trap will be generated, use the sessions max limit command in BBA group configuration mode. To remove these settings, use the no form of this command.
sessions max limit number-of-sessions [threshold threshold-value]
no sessions max limit number-of-sessions [threshold threshold-value]
Syntax Description
number-of-sessions
|
Maximum number of PPPoE sessions that will be permitted on the router. The range is from 0 to the total number of interfaces on the router.
|
threshold
|
(Optional) Sets the PPPoE session-count threshold at which an SNMP trap will be generated.
|
threshold-value
|
(Optional) Number of PPPoE sessions that will cause an SNMP trap to be generated. The range is from 0 to the total number of interfaces on the router.
|
Defaults
There is no default number-of-sessions.
The default threshold-value is the configured number-of-sessions.
Command Modes
BBA group configuration
Command History
Release
|
Modification
|
12.2(15)T
|
This command was introduced.
|
Usage Guidelines
This command can be used only in a global PPPoE profile.
The snmp-server enable traps pppoe command must be configured in order for SNMP traps to be generated when the PPPoE session-count threshold is reached.
Examples
The following example shows the global PPPoE profile configured with a maximum PPPoE session limit of 8000 sessions. The PPPoE session-count threshold is set at 7000 sessions, so when the number of PPPoE sessions on the router reaches 7000, an SNMP trap will be generated.
sessions max limit 8000 threshold 7000
Related Commands
Command
|
Description
|
bba-group pppoe
|
Creates a PPPoE profile.
|
sessions per-mac limit
|
Sets the maximum number of PPPoE sessions allowed per MAC address in a PPPoE profile.
|
sessions per-vc limit
|
Sets the maximum number of PPPoE sessions permitted over a VC and sets the PPPoE session-count threshold.
|
sessions per-vlan limit
|
Sets the maximum number of PPPoE sessions per VLAN in a PPPoE profile.
|
snmp-server enable traps pppoe
|
Enables PPPoE session-count SNMP notifications.
|
sessions per-mac limit
To set the maximum number of PPP over Ethernet (PPPoE) sessions allowed per MAC address in a PPPoE profile, use the sessions per-mac limit command in BBA group configuration mode. To remove this setting, use the no form of this command.
sessions per-mac limit per-mac-limit
no sessions per-mac limit per-mac-limit
Syntax Description
per-mac-limit
|
Maximum number of PPPoE sessions that can be sourced from a MAC address. The default is 100 sessions.
|
Defaults
100 sessions
Command Modes
BBA group configuration
Command History
Release
|
Modification
|
12.2(15)T
|
This command was introduced.
|
Usage Guidelines
Use the sessions per-mac limit command to configure a PPPoE profile with the maximum number of PPPoE sessions that will be allowed per MAC address.
You cannot configure PPPoE session limits in PPPoE profiles and in VPDN groups simultaneously. You also cannot configure session limits in PPPoE profiles and directly on PPPoE ports (Ethernet interface, VLAN, or permanent virtual circuit (PVC)) simultaneously.
Examples
The following example show a limit of two PPPoE sessions per MAC address configured in the global PPPoE profile:
sessions max limit 8000 threshold-sessions 7000
Related Commands
Command
|
Description
|
bba-group pppoe
|
Creates a PPPoE profile.
|
sessions max limit
|
Configures a PPPoE global profile with the maximum number of PPPoE sessions that will be permitted on a router and sets the PPPoE session-count threshold.
|
sessions per-vc limit
|
Sets the maximum number of PPPoE sessions to be established over a VC in a PPPoE profile and sets the PPPoE session-count threshold.
|
sessions per-vlan limit
|
Sets the maximum number of PPPoE sessions per VLAN in a PPPoE profile.
|
sessions per-vc limit
To set the maximum number of PPP over Ethernet (PPPoE) sessions to be established over a virtual circuit (VC) in a PPPoE profile and to set the PPPoE session-count threshold at which a Simple Network Management Protocol (SNMP) trap will be generated, use the sessions per-vc limit command in BBA group configuration mode. To remove this specification, use the no form of this command.
sessions per-vc limit per-vc-limit [threshold threshold-value]
no sessions per-vc limit per-vc-limit [threshold threshold-value]
Syntax Description
per-vc-limit
|
Maximum number of PPPoE sessions that can be established over an ATM PVC. The default is 100.
|
threshold
|
(Optional) Sets the PPPoE session-count threshold at which an SNMP trap will be generated.
|
threshold-value
|
(Optional) Number of PPPoE sessions that will cause an SNMP trap to be generated.
|
Defaults
Sessions: 100
The default threshold-value is the per-vc-limit.
Command Modes
BBA group configuration
Command History
Release
|
Modification
|
12.2(15)T
|
This command was introduced.
|
Usage Guidelines
Use the sessions per-vc limit command to configure a PPPoE profile with the maximum number of PPPoE sessions that will be allowed per VC.
You cannot configure session limits in PPPoE profiles and directly on permanent virtual circuits (PVCs) simultaneously.
The snmp-server enable traps pppoe command must be configured in order for SNMP traps to be generated when the PPPoE session-count threshold is reached.
Examples
The following example shows a limit of eight PPPoE sessions per VC configured in the PPPoE profile "vpn1":
Related Commands
Command
|
Description
|
bba-group pppoe
|
Creates a PPPoE profile.
|
sessions max limit
|
Configures a PPPoE global profile with the maximum number of PPPoE sessions that will be permitted on a router and sets the PPPoE session-count threshold.
|
sessions per-mac limit
|
Sets the maximum number of PPPoE sessions allowed per MAC address in a PPPoE profile.
|
sessions per-vlan limit
|
Sets the maximum number of PPPoE sessions per VLAN in a PPPoE profile.
|
snmp-server enable traps pppoe
|
Enables PPPoE session-count SNMP notifications.
|
sessions per-vlan limit
To specify the maximum number of PPPoE sessions permitted per VLAN in a PPPoE profile, use the sessions per-vlan limit command in BBA group configuration mode. To remove this specification, use the no form of this command.
sessions per-vlan limit per-vlan-limit
no sessions per-vlan limit per-vlan-limit
Syntax Description
per-vlan-limit
|
Maximum number of PPPoE sessions permitted under each VLAN. The default is 100.
|
Defaults
Sessions: 100
Command Modes
BBA group configuration
Command History
Release
|
Modification
|
12.2(15)T
|
This command was introduced.
|
Usage Guidelines
Use the sessions per-vlan limit command to configure a PPPoE profile with the maximum number of PPPoE sessions that will be allowed per VLAN.
You cannot configure session limits in PPPoE profiles and directly on VLANs simultaneously.
Examples
The following example shows a limit of 200 PPPoE sessions per VLAN configured in the PPPoE profile "vpn1":
sessions per-vlan limit 200
Related Commands
Command
|
Description
|
bba-group pppoe
|
Creates a PPPoE profile.
|
sessions max limit
|
Configures a PPPoE global profile with the maximum number of PPPoE sessions that will be permitted on a router and sets the PPPoE session-count threshold.
|
sessions per-mac limit
|
Sets the maximum number of PPPoE sessions allowed per MAC address in a PPPoE profile.
|
sessions per-vc limit
|
Sets the maximum number of PPPoE sessions to be established over a VC in a PPPoE profile and sets the PPPoE session-count threshold.
|
sessions throttle
To configure PPP over Ethernet (PPPoE) connection throttling, which limits the number of PPPoE session requests that can be made from a virtual circuit (VC) or a MAC address within a specified period of time, use the sessions throttle command in BBA group configuration mode. To remove this limit, use the no version of this command.
sessions {per-mac | per-vc} throttle session-requests session-request-period blocking-period
no sessions {per-mac | per-vc} throttle session-requests session-request-period blocking-period
Syntax Description
per-mac
|
Limits the number of PPPoE session requests that can be made from a single MAC address.
|
per-vc
|
Limits the number of PPPoE session requests that can be made from a single VC.
|
session-requests
|
Number of PPPoE session requests that will be allowed within a specified period of time. Range is from 1 to 100000.
|
session-request-period
|
Period of time, in seconds, during which a specified number of PPPoE session requests will be allowed. Range is from 1 to 3600.
|
blocking-period
|
Period of time, in seconds, during which PPPoE session requests will be blocked. This period begins when the number of PPPoE session requests from a VC or MAC address exceeds the configured session-requests value within the configured session-request-period. Range is from 0 to 3600.
|
Defaults
The number of PPPoE session requests that can be made within a specific period of time is not limited.
There are no default values for the session-requests, session-request-period, and blocking-period arguments.
Command Modes
BBA group configuration
Command History
Release
|
Modification
|
12.2(15)T
|
This command was introduced.
|
Usage Guidelines
Continuous repeated requests to initiate PPPoE sessions can seriously affect the performance of a router and RADIUS server. Use the sessions throttle command to configure the PPPoE server to limit the number of requests for PPPoE sessions that can be made from a MAC address or VC during a configured period of time.
If a client exceeds the configured number of allowable session requests (session-requests) within the configured time limit (session-request-period), the PPPoE server accepts only the allowable number of session requests and blocks the MAC address or VC from making any more requests for a configured period of time (blocking-period).
After the blocking-period expires, the PPPoE server will again accept the configured number of session requests from the MAC address or VC within the configured session-request-period.
Examples
The following example shows the configuration of per-VC and per-MAC PPPoE connection throttling in PPPoE profile "grp1":
sessions per-mac throttle 10 60 300
sessions per-vc throttle 100 30 300
interface ATM2/0.1 multipoint
protocol pppoe group grp1
interface virtual-template1
no peer default ip address
Related Commands
Command
|
Description
|
bba-group pppoe
|
Creates a PPPoE profile.
|
sessions per-mac limit
|
Sets the maximum number of PPPoE sessions allowed per MAC address in a PPPoE profile.
|
sessions per-vc limit
|
Sets the maximum number of PPPoE sessions to be established over a VC in a PPPoE profile and sets the PPPoE session-count threshold.
|
show atm svc ppp
To display information about each switched virtual circuit (SVC) configured for PPP over ATM, use the show atm svc ppp command in privileged EXEC mode.
show atm svc ppp
Syntax Description
This command has no arguments or keywords.
Command Modes
Privileged EXEC
Command History
Release
|
Modification
|
12.1(3)T
|
This command was introduced.
|
Examples
The following is sample output for the show atm svc ppp command:
ATM Int. VCD/Name VPI VCI Type VCSt VA VASt
2/0.1 10 0 60 SVC UP 1 UP
Table 21 describes the fields shown in the display.
Table 21 show atm svc ppp Field Descriptions
Field
|
Description
|
ATM Int.
|
Interface on which the SVC is configured.
|
VCD/Name
|
Virtual circuit descriptor (VCD) or name associated with the SVC.
|
VPI
|
Virtual path identifier.
|
VCI
|
Virtual channel identifier.
|
Type
|
Type of virtual circuit.
|
VCSt
|
Virtual circuit state.
|
VA
|
Virtual access interface number.
|
VASt
|
Virtual access interface state.
|
show controller shdsl
To display the status of the controller configured for single-pair high-bit-rate digital subscriber line (SHDSL) mode, use the show controller shdsl command in privileged EXEC mode.
show controller shdsl number
Syntax Description
number
|
SHDSL controller number. The valid controller number for SHDSL mode is 0.
|
Defaults
Controller number: 0
Command Modes
privileged EXEC
Command History
Release
|
Modification
|
12.2(8)T
|
This command was introduced on Cisco IAD2420 series IADs.
|
Usage Guidelines
This command is used to display the controller mode and the controller number and to view the associated statistics.
Examples
The following example displays the status of the controller configured for SHDSL mode:
Router# show controller shdsl 0
SLOT 3: Globespan xDSL controller chipset
Configured Line rate: 1160Kbps
Line Re-activated 0 times after system bootup
CRC per second alarm: None
Related Commands
Command
|
Description
|
controller shdsl 0
|
Configures the controller status and the controller number.
|
show dsl interface atm
To display information specific to the the asymmetric digital subscriber line (ADSL) for a specified ATM interface, use the show dsl interface atm command in EXEC mode.
show dsl interface atm number
Syntax Description
number
|
ATM interface number.
|
Command Modes
EXEC
Command History
Release
|
Modification
|
12.1(3)XJ
|
The command was introduced on Cisco 1700 series routers.
|
12.2(2)T
|
This command was integrated into Cisco IOS Release 12.2(2)T.
|
12.1(5)YB
|
Support for this command was added to Cisco 2600 series and Cisco 3600 series routers.
|
12.1(5)XR1
|
Support for this command was added to the Cisco IAD2420 series.
|
12.2(4)T
|
This command was integrated into Cisco IOS Release 12.2(4)T.
|
Usage Guidelines
Use this command to view the status or results of a line test and to get information on port status, alarms, configured and actual transmission rates, and transmission errors.
The output from this command appears the same as the output from the show controller atm command on Cisco 1400 series routers.
Examples
The following sample output displays the ADSL-specific information for ATM interface 0:
Router# show dsl interface atm0
Alcatel 20150 chipset information
Modem Status: Showtime (DMTDSL_SHOWTIME)
DSL Mode: ITU G.992.1 (G.DMT)
Vendor Specific: 0x0000 0x0000
Vendor Country: 0x00 0x0F
Noise Margin: 13.5 dB 7.0 dB
Output Power: 9.5 dBm 12.0 dBm
Attenuation: 1.5 dB 3.5 dB
Interrupts: 5940 (0 spurious)
Interleave Fast Interleave Fast
Speed (kbps): 0 8128 0 864
00: 0 0 0 0 0 0 0 7 6 7 9 A B C C C
10: C C C C C C B B B B A 9 A 9 0 0
20: 0 0 0 0 0 0 2 2 3 4 4 5 6 6 7 7
30: 7 8 8 8 9 9 9 A A A A A A B B B
40: B B B B B B B B B B B A B B B B
50: B B B B B B B B B B B B 2 B B B
60: B B B B B B B B B B B B B B B B
70: B B B B B B B B B B B B B B B B
80: B B B B B B B B B B B B B B B B
90: B B B B B B B B B B B B B B B B
A0: B B B B B B B B B B B B B B B B
B0: B B B B B B B B B B B B A B A A
C0: A A A A A A A A A A A A A A A A
D0: A A A A A A A A A A A 9 9 9 9 9
E0: 9 9 9 9 9 9 9 9 9 9 9 9 8 8 8 8
F0: 8 8 8 8 8 8 7 7 7 7 6 6 5 5 4 4
Table 2 describes the significant fields shown in the display.
Table 22 show dsl interface atm Field Descriptions
Field
|
Description
|
Modem Status
|
Status of the modem. Possible states include the following:
DMTDSL_INVALID—Error state.
DMTDSL_STOP—Administrative down state.
DMTDSL_INIT—Restarting line.
DMTDSL_CHK_HW—Confirming that required HW exists.
DMTDSL_DLOAD_1—Downloading the init.bin file.
DMTDSL_DLOAD_2—Downloading operational firmware.
DMTDSL_MODE_CHK—Verifying that download was successful.
DMTDSL_DO_OPEN—Issue ADSL_OPEN command.
DMTDSL_RE_OPEN—Cycle the link. Retry open.
DMTDSL_ACTIVATING—Waiting for activation to succeed.
DMTDSL_LOOPBACK—Activation done.
DMTDSL_SHOWTIME—Activation succeeded.
|
DSL Mode
|
DSL operating mode.
|
ITU STD NUM
|
ITU standard number for the operating mode.
|
Vendor ID
|
Vendor identification code.
|
Vendor Specific
|
Indicates if this router is specified for a vendor.
|
Vendor Country
|
Code for the country where the vendor is located.
|
Capacity Used
|
Percentage of the capacity that is being used.
|
Noise Margin
|
Noise margin, in decibels.
|
Output Power
|
Power output, in decibels.
|
Attenuation
|
Attenuation of the signal, in decibels.
|
Defect Status
|
Status of defects.
|
Last Fail Code
|
Last failure code that was logged.
|
Selftest Result
|
Results of the self-test.
|
Subfunction
|
Code for the subfunction running.
|
Interrupts
|
Code for interrupts used.
|
PHY Access Err
|
Number of physical access errors.
|
Activations
|
Number of activations of the router.
|
SW Version
|
Software version number.
|
FW Version
|
Firmware version number.
|
Speed
|
The train speed for upstream and downstream. It shows both the interleave and the fast mode.
|
Reed-Solomon EC
|
Reed-Solomon error-correction statistics.
|
CRC Errors
|
Cyclic redundancy check statistics.
|
Header Errors
|
ATM header error reports.
|
Bit Errors
|
Total number of bit errors.
|
BER Valid sec
|
Bit error rate valid seconds.
|
BER Invalid sec
|
Bit error rate invalid seconds.
|
Related Commands
Command
|
Description
|
dsl operating-mode
|
Modifies the operating mode of the digital subscriber line for an ATM interface.
|
show pppatm summary
To display PPP over ATM (PPPoA) session counts, use the show pppatm summary command in EXEC mode.
show pppatm summary [interface atm interface-number[.subinterface-number]]
Syntax Description
interface atm interface-number.subinterface-number
|
(Optional) Specifies a particular ATM interface by interface number and possibly a subinterface number. A period (.) must precede the optional subinterface number.
|
Command Modes
EXEC
Command History
Release
|
Modification
|
12.2(13)T
|
This command was introduced.
|
Usage Guidelines
This command is useful for obtaining session counts, the state of the PPPoA sessions, and the interfaces they are running on.
This command gives a summary of the number of PPPoA sessions in each state and the session information of each individual session. If a subinterface number is given in the command, the output is a summary report of the PPPoA sessions in the subinterface. If a main interface number is given, the output will have the summary reports for each individual subinterface of that main interface as shown in the example that follows. If no interface is given, the output will contain the summary reports for each ATM interface on the router.
Examples
The following example displays PPPoA session counts and states for ATM interface 5/0:
Router# show pppatm summary interface atm 5/0
VPI VCI Conn ID PPPoA ID SSS ID PPP ID AAA ID VT VA/SID State
6 101 11 DA000009 BB000013 E5000017 C 1 1.1 PTA
Most of the messages displayed by the show pppatm summary command are self-explanatory. Table 23 describes the significant fields shown in the displays. Any data not described in Table 23 is used for internal debugging purposes.
Table 23 show pppatm summary Field Descriptions
Field
|
Description
|
VPI
|
Virtual path identifier of the permanent virtual circuit (PVC).
|
VCI
|
Virtual channel identifier of the PVC.
|
Conn ID
|
Unique connection identifier for the PPPoA session. This ID can be correlated with the unique ID in the show vpdn session command output for the forwarded sessions.
|
PPPoA ID
|
Internal identifier for the PPPoA session.
|
SSS ID
|
Internal identifier in the Subscriber Service Switch.
|
PPP ID
|
Internal identifier in PPP.
|
AAA ID
|
Authentication, authorization, and accounting (AAA) unique identifier for accounting records.
|
VT
|
Virtual template number used by the session.
|
VA/SID
|
PPPoA virtual access number for PPP Termination Aggregation (PTA) sessions, and switch identifier for forwarded sessions.
|
State
|
PPPoA state of the session.
|
Related Commands
Command
|
Description
|
clear pppatm interface atm
|
Clears PPP ATM sessions on an ATM interface.
|
debug pppatm
|
Enables reports for PPPoA events, errors, and states either globally or conditionally on an interface or VC.
|
show pppatm trace
|
Displays a sequence of PPPoA events, errors, and state changes when the debug pppatm command is enabled.
|
show pppatm trace
To display a sequence of PPP over ATM (PPPoA) events, errors, and state changes when the debug pppatm command is enabled, use the show pppatm trace command in privileged EXEC mode.
show pppatm trace [error | event | state] interface atm interface-number.[subinterface-number]
vc {[vpi/]vci | virtual-circuit-name}
Syntax Description
error
|
(Optional) PPPoA events.
|
event
|
(Optional) PPPoA errors.
|
state
|
(Optional) PPPoA state.
|
interface atm interface-number.subinterface-number
|
Specifies a particular ATM interface by interface number and possibly a subinterface number preceded by a period.
|
vc [vpi/]vci virtual-circuit-name
|
(Optional) Virtual circuit (VC) keyword followed by a virtual path identifier (VPI), virtual channel identifier (VCI), and VC name. A slash (/) must follow the VPI.
|
Command Modes
Privileged EXEC
Command History
Release
|
Modification
|
12.2(13)T
|
This command was introduced.
|
Usage Guidelines
When the debug pppatm command has been enabled, this command displays messages from the specified permanent virtual circuit (PVC). If only one debug pppatm command keyword is supplied in the command, the report will display only the sequence of events for that particular debug type.
Examples
The following example traces the debugging messages supplied by the debug pppatm command on PVC 101. The report is used by Cisco technical personnel for diagnosing system problems.
Router# debug pppatm trace interface atm 1/0.10 vc 101
Router# debug pppatm state interface atm 1/0.10 vc 101
Router# debug pppatm event interface atm 1/0.10 vc 101
Router# show pppatm trace interface atm 1/0.10 vc 101
Event = AAA gets dynamic attrs
Event = AAA gets dynamic attrs
Event = Access IE allocated
Event = AAA gets retrieved attrs
Event = AAA gets nas port details
Event = AAA gets dynamic attrs
Event = AAA gets dynamic attrs
Event = AAA unique id allocated
Event = No AAA method list set
State = NAS_PORT_POLICY_INQUIRY
Event = Access IE get nas port
Event = AAA gets dynamic attrs
Event = AAA gets dynamic attrs
Related Commands
Command
|
Description
|
clear pppatm interface atm
|
Clears PPP ATM sessions on an ATM interface.
|
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.
|
shutdown (PVC-in-range)
To deactivate an individual permanent virtual circuit (PVC) within a PVC range, use the shutdown PVC-in-range configuration command. To reactivate an individual PVC within PVC range, use the no form of this command.
shutdown
no shutdown
Syntax Description
This command has no arguments or keywords.
Defaults
The PVC is active.
Command Modes
PVC-in-range configuration
Command History
Release
|
Modification
|
12.1(5)T
|
This command was introduced.
|
Examples
In the following example, "pvc1" within the PVC range called "range1" is deactivated:
interface atm 6/0.110 multipoint
range range1 pvc 100 4/199
Related Commands
Command
|
Description
|
pvc-in-range
|
Configures an individual PVC within a PVC range.
|
shutdown (PVC range)
|
Deactivates a PVC range.
|
shutdown (PVC range)
To deactivate a PVC range, use the shutdown command in PVC range configuration mode. To reactivate a PVC range, use the no form of this command.
shutdown
no shutdown
Syntax Description
This command has no arguments or keywords.
Defaults
PVC range is active.
Command Modes
PVC range configuration
Command History
Release
|
Modification
|
12.1(5)T
|
This command was introduced.
|
Examples
In the following example, a PVC range called "range1" is deactivated:
interface atm 6/0.110 multipoint
range range1 pvc 100 4/199
Related Commands
Command
|
Description
|
range pvc
|
Defines a range of ATM PVCs.
|
show pppatm summary
|
Deactivates an individual PVC within a PVC range.
|
virtual-template (BBA group)
To configure a PPPoE profile with a virtual template to be used for cloning virtual access interfaces, use the virtual-template command in BBA group configuration mode. To remove the virtual template from a PPPoE profile, use the no form of this command.
virtual-template template-number
no virtual-template template-number
Syntax Description
template-number
|
Identifying number of the virtual template that will be used to clone virtual-access interfaces.
|
Defaults
A virtual template is not specified.
Command Modes
BBA group configuration
Command History
Release
|
Modification
|
12.2(15)T
|
This command was introduced.
|
Usage Guidelines
Each PPPoE profile can clone virtual-access interfaces using only one virtual template. If you enter a second virtual-template command in a PPPoE profile, it will replace the first virtual-template command.
You can configure different PPPoE profiles to use different virtual templates. You can also configure multiple PPPoE profiles to use the same virtual template.
Examples
The following example shows the configuration of two PPPoE profiles:
Related Commands
virtual-template pre-clone
To specify the number of virtual-access interfaces to be created and cloned from a specific virtual template, use the virtual-template pre-clone command in global configuration mode. To disable precloning, use the no form of this command.
virtual-template template-number pre-clone number
no virtual-template template-number pre-clone number
Syntax Description
template-number
|
The number of the virtual template interfaces from which the new virtual-access interfaces are created.
|
number
|
The number of virtual-access interfaces to be created.
|
Defaults
Precloning is disabled.
Command Modes
Global configuration
Command History
Release
|
Modification
|
12.0(3)DC
|
This command was introduced on the Cisco 6400 node route processor.
|
12.2(4)T
|
This command was integrated into Cisco IOS Release 12.2(4)T.
|
Usage Guidelines
The number of precloned virtual-access interfaces should be set to the number of expected PPPoA and PPPoE sessions.
The precloned virtual-access interfaces will be attached to the PVC upon receipt of the first PPP packet from the client on the PVC. The virtual-access interface will be detached from the PVC upon termination of the PPP session.
When a PPP session is terminated, the virtual-access interface will remain in the router and will be reused. When precloning is disabled, any virtual-access interfaces that were already precloned but have not yet been used will remain in the router for future use.
Examples
The following example shows how to create 1200 precloned virtual-access interfaces on virtual template 1:
virtual-template 1 pre-clone 1200
Related Commands
Command
|
Description
|
encapsulation (ATM)
|
Configures the ATM adaptation layer (AAL) and encapsulation type for an ATM virtual circuit (VC), VC class, VC, bundle, or PVC range.
|
show vtemplate
|
Displays a list of all configured virtual templates.
|
vpn service
To configure a static domain name, use the vpn service command in ATM VC or VC class configuration mode. To remove a static domain name, use the no form of this command.
vpn service domain-name
no vpn service domain-name
Syntax Description
domain-name
|
Static domain name.
|
Defaults
No default behavior or values.
Command Modes
ATM VC configuration
ATM VC class configuration
Command History
Release
|
Modification
|
12.1(1)DC1
|
This command was introduced on the Cisco 6400 NRP.
|
12.2(13)T
|
This command was integrated into Cisco IOS Release 12.2(13)T.
|
Usage Guidelines
Use the vpn service command in a permanent virtual circuit (PVC) or a PVC range configuration so that PPP over ATM (PPPoA) sessions in those PVCs will be forwarded according to the domain name supplied, without starting PPP.
Examples
In the following partial example, virtual private dialup network (VPDN) group 1 is selected for PPPoA session forwarding based on the domain name xyz.com:
initiate-to ip 1.1.1.1 priority 1
interface ATM1/0.1 multipoint
protocol ppp virtual-template 1