-
Cisco IOS Wide-Area Networking Command Reference, Release 12.3 T
-
Introduction
-
Wide-Area Networking Commands: A through B
-
Wide-Area Networking Commands: C
-
Wide-Area Networking Commands: D through E
-
Wide-Area Networking Commands: frame-relay adaptive-shaping through frame-relay lmi-type
-
Wide-Area Networking Commands: frame-relay local-dlci through fr-atm connect dlci
-
Wide-Area Networking Commands: H through L
-
Wide-Area Networking Commands: M through R \r\n
-
Wide-Area Networking Commands: scrambling cell-payload through show dxi pvc
-
Wide-Area Networking Commands: show frame-relay through show vc-group
-
Wide-Area Networking Commands: show x25 through svc
-
Wide-Area Networking Commands: T through x25 nvc
-
Wide-Area Networking Commands: x25 ops through xot access-group
-
Table Of Contents
dscp (Frame Relay VC-bundle-member)
dsl operating-mode (ADSL over ISDN)
dsl-mode shdsl symmetric annex
encapsulation (Frame Relay VC-bundle)
dbs enable
To apply Dynamic Subscriber Bandwidth Selection (DBS) QoS parameters, use the dbs enable command in the appropriate configuration mode. To remove DBS QoS parameters, use the no form of this command.
dbs enable
no dbs enable
Syntax Description
This command has no arguments or keywords.
Defaults
DBS QoS parameters are not applied.
Command Modes
ATM VC class configuration
ATM VC configuration
ATM PVC range configuration
ATM PVC-in-range configurationCommand History
12.2(4)B
This command was introduced.
12.2(13)T
This command was integrated into Cisco IOS Release 12.2(13)T.
Usage Guidelines
The no dbs enable command configured in any configuration mode overrides the dbs enable command configured in any configuration mode. Both the dbs enable and no dbs enable commands are saved in the running configuration and appear, when configured, in the output of the show running-config command. The default dbs enable command does not appear in the output of the show running-config command when configured.
When you enter the dbs enable or no dbs enable command, existing sessions are not disconnected. If you have a session that has been configured for DBS and you configure the no dbs enable command on a VC, additional sessions that are configured will display DBS-configured QoS values until the first new session is up. After the first session is brought up, the VC has default and locally configured values. If you configure the dbs enable command after multiple sessions are already up on the VC, all sessions on that VC have DBS QoS parameters.
RADIUS QoS attributes are applied to PVCs when a new PPP over Ethernet (PPPoE) session has peak cell rate (PCR) and sustainable cell rate (SCR) values that are higher than existing PPPoE sessions. If a new PPPoE session with lower PCR and SCR values is added to a PVC, the RADIUS QoS attributes are not applied to the new session. If the user of the PPPoE session that has the higher PCR and SCR values logs out, the QoS attributes are set to those of the lower bandwidth user.
RADIUS QoS attributes override attributes on a PVC configured in ATM PVC-in-range or ATM PVC range configuration mode. If the RADIUS QoS attributes cannot be applied to a PVC, PPPoE and PPPoA sessions cannot be established.
When DBS is configured, normal ATM precedences apply. PVC configurations take precedence over VC class configurations. Thus, if DBS QoS parameters are applied on a VC class and disabled on one PVC in that VC class, DBS QoS parameters are not applied on the PVC. ATM PVC-in-range configurations take precedence over PVC range configurations.
When you configure DBS on a PVC, existing sessions on that PVC remain connected.
Examples
The following example configures DBS in ATM VC class configuration mode:
vc-class atm pppoedbs enableThe following example configures DBS in ATM VC configuration mode:
interface atm0/0/0.5 point-to-pointip address 10.0.0.0 255.255.255.0pvc 0/100dbs enableprotocol pppoeThe following example configures DBS in ATM PVC range configuration mode:
interface atm0/0/0.1 multipointip address 10.0.0.0 255.255.255.0range pvc 0/50 0/70dbs enableThe following example configures DBS in ATM PVC-in-range configuration mode:
interface atm0/0/0.1 multipointrange pvc 0/50 0/70pvc-in-range 60dbs enableRelated Commands
de-bit
To set Frame Relay discard-eligible (DE) bit mapping for FRF.5 and FRF.8 network interworking, use the de-bit command in FRF.5 connect configuration mode or FRF.8 connect configuration mode. To disable or reset Frame Relay DE bit mapping, use the no form of this command.
de-bit {0 | 1 | map-clp}
no de-bit {0 | 1 | map-clp}
Syntax Description
Defaults
map-clp
Command Modes
FRF.5 connect configuration
FRF.8 connect configurationCommand History
Usage Guidelines
In the default state, the DE bit in the Frame Relay header is set to 1 when one or more ATM cells that belong to a frame have their cell loss priority (CLP) field set to 1 or when the DE field of the Frame Relay service-specific convergence sublayer (FR-SSCS) protocol data unit (PDU) is set to 1.
When the no de-bit command and map-clp keyword are entered, the FR-SSCS PDU DE field is copied unchanged to the Q.922 core frame DE field, independently of CLP indications received at the ATM layer.
Examples
The following example creates a connection between the virtual circuit (VC) group named "friends" and ATM PVC 0/32 and configures FR DE field mapping to match the ATM CLP field:
Router(config)# vc-group friendsRouter(config-vc-group)# serial1/0 16 16Router(config-vc-group)# serial1/0 17 17Router(config-vc-group)# serial1/0 18 18Router(config-vc-group)# serial1/0 19 19Router(config)# interface atm3/0Router(config-if)# pvc 0/32Router(config-if-atm-vc)# encapsulation aal5mux frame-relayRouter (config-if-atm-vc)# exitRouter (config-if)# exitRouter(config)# connect vc-group friends atm3/0 0/32Router(config-frf5)# de-bit map-clpRelated Commands
de-bit map-clp
To set Frame Relay discard eligible (DE) bit mapping for FRF.5 network interworking, use the de-bit map-clp command in FRF.5 connect mode. To disable or reset Frame Relay DE bit mapping, use the no form of this command.
de-bit map-clp
no de-bit map-clp
Syntax Description
This command has no arguments or keywords.
Defaults
No default behavior or values
Command Modes
FRF.5 connect configuration
Command History
Usage Guidelines
In the default state, the DE bit in the Frame Relay header is set to 1 when one or more ATM cells belonging to a frame have their cell loss priority (CLP) field set to 1, or when the DE field of the Frame Relay service specific convergence sublayer (FR-SSCS) protocol data unit (PDU) is set to 1.
When the no de-bit map-clp command is entered, the FR-SSCS PDU DE field is copied unchanged to the Q.922 core frame DE field, independent of CLP indications received at the ATM layer.
Examples
The following example creates a connection that connects the virtual circuit (VC) group named friends to ATM PVC 0/32 and configures FR DE field mapping to match the ATM CLP field:
Router(config)# vc-group friendsRouter(config-vc-group)# serial0 16 16Router(config-vc-group)# serial0 17 17Router(config-vc-group)# serial0 18 18Router(config-vc-group)# serial0 19 19Router(config)# interface atm3/0Router(config-if)# pvc 0/32Router(config-if-atm-vc)# encapsulation aal5mux frame-relayRouter(config)# connect vc-group friends atm3/0 0/32Router(config-frf5)# de-bit map-clpRelated Commands
dscp (Frame Relay VC-bundle-member)
To configure the differentiated services code point (DSCP) levels for a Frame Relay permanent virtual circuit (PVC) bundle member, use the dscp command in Frame Relay VC-bundle-member configuration mode. To remove the DSCP level configuration from the PVC, use the no form of this command.
dscp {level | other}
no dscp level
Syntax Description
Defaults
DSCP levels are not configured.
Command Modes
Frame Relay VC-bundle-member configuration
Command History
Usage Guidelines
Assignment of DSCP levels to PVC bundle members allows you to create differentiated service because you can distribute the DSCP levels over the various PVC bundle members. You can map a single DSCP level or range of levels to each discrete PVC in the bundle, thereby enabling PVCs in the bundle to carry packets marked with different DSCP levels. Use the dscp other command to configure a PVC to carry traffic marked with DSCP levels not specifically configured on other PVCs. Only one PVC in the bundle can be configured with the dscp other command.
This command is available only when the match type for the PVC bundle is set to dscp using the match dscp command in Frame Relay VC-bundle configuration mode.
You can overwrite the DSCP level configuration on a PVC by reentering the dscp command with a new level value.
There is no default value for this command. When the PVC bundle is set to dscp using the match dscp command, all PVCs in the bundle are reset to remove any existing DSCP values. If one or more DSCP values are not specifically configured, the bundle will not come up.
Note, however, that a PVC may exist in a bundle but have no DSCP value associated with it. As long as all valid DSCP values are handled by one or more of the other PVCs in the bundle, the bundle can come up, but the PVC that has no DSCP value configured will not participate in it.
A DSCP level can be configured on one PVC-bundle member per bundle. If you configure the same DSCP level on more than one PVCs within a bundle, the following error warning appears on the console:
%Overlapping diff-serv code pointsExamples
The following example assigns DSCP levels 0 through 9 to PVC bundle member 300 in a Frame Relay PVC bundle called "MP-3-static":
interface serial 1/4frame-relay map ip 10.2.2.2 vc-bundle MP-3-staticframe-relay vc-bundle MP-3-staticpvc 300dscp 0-9The following example changes the DSCP levels in the above example from 0 through 9 to 0, 9, and 20 through 29:
interface serial 1/4frame-relay map ip 10.2.2.2 vc-bundle MP-3-staticframe-relay vc-bundle MP-3-staticpvc 300dscp 0,9,20-29Related Commands
dsl enable-training-log
To enable the retrieval of the digital subscriber line (DSL) training log, use the dsl enable-training-log command in interface configuration mode. To disable retrieval of the DSL training log, use the no form of this command.
dsl enable-training-log
no dsl enable-training-log
Syntax Description
This command has no arguments or keywords.
Defaults
Retrieval of the DSL training log is disabled.
Command Modes
Interface configuration
Command History
12.2(4)XM
This command was introduced.
12.3
This command was integrated into Cisco IOS Release 12.3
Usage Guidelines
The training log is a record of the events that occur when the router trains, or negotiates communication parameters, with the DSL access multiplexer (DSLAM) at the central office. Retrieving this log may add up to a few minutes to the training process, and retrieval is not always necessary after the router has successfully trained. Therefore, retrieval of the training log is disabled by default. To retrieve the log, enter the dsl enable-training-log command.
Examples
The following example enables the retrieval of the training log:
Router(config-if)# dsl enable-training-logdsl 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 (G.SHDSL)
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 (G.SHDSL)
Specifies an operating mode of the DSL 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 -.5 to the noise margin:
dsl noise-margin -.5Related Commands
dsl operating-mode
CautionThis 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).
To modify the operating mode of the digital subscriber line for an ATM interface, use the dsl operating-mode command in interface configuration mode.
The following syntax is used with the Cisco WIC-1ADSL:
dsl operating-mode {auto | ansi-dmt | itu-dmt | splitterless}
no dsl operating-mode {auto | ansi-dmt | itu-dmt | splitterless}
The following syntax is used with the Cisco WIC-1ADSL-I-DG:
dsl operating-mode {auto | etsi | itu-dmt} [tone low]
no dsl operating-mode {auto | etsi | itu-dmt} [tone low]
Syntax Description
Defaults
The default DSL operating mode is auto.
Command Modes
Interface configuration
Command History
Usage Guidelines
Caution
Examples
The following example shows how to configure the DSL operating mode for ATM interface 0:
Router# configure terminalEnter configuration commands, one per line. End with CNTL/Z.Router(config)# interface atm 0Router(config-if)# dsl operating-mode itu-dmtRouter(config-if)# endRouter#Related Commands
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
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-mode shdsl symmetric annex
To configure a DSL controller to operate in SHDSL multirate, high-speed symmetric mode, and to set regional operating parameters, use the dsl-mode shdsl symmetric annex command in controller configuration mode.
dsl-mode shdsl symmetric annex {A | B | A-B | A-B-ANFP | B-ANFP}
Syntax Description
Defaults
The default regional operating parameter is A for North America.
Command Modes
Controller configuration
Command History
Usage Guidelines
Use this command to configure the DSL controller interface to operate in SHDSL multirate, high-speed symmetric mode, and to set regional operating parameters to either North America or Europe, per ITU G.991.2.
Examples
The following example shows a typical configuration and (when messaging is enabled) the messages seen for a DSL controller on the CO side of the network. This example uses the dsl-mode shdsl symmetric annex a command to configure the controller for SHDSL North American multirate, high-speed symmetric mode.
Router# configure terminalEnter configuration commands, one per line. End with CNTL/Z.Router(config)# controller dsl 0/0Router(config-controller)# mode atmRouter(config-controller)# line-term coRouter(config-controller)# line-mode 4-wireRouter(config-controller)# dsl-mode shdsl symmetric annex aRouter(config-controller)# line-rate 460800:22:07: %CONTROLLER-5-UPDOWN: Controller DSL 0/0, changed state to down00: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
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 10dxi map
To map a protocol address to a given virtual path identifier (VPI) and virtual channel identifier (VCI), use the dxi map command in interface configuration mode. To remove the mapping for that protocol and protocol address, use the no form of this command.
dxi map protocol protocol-address vpi vci [broadcast]
no dxi map protocol protocol-address
Syntax Description
Defaults
No map definition is established.
Command Modes
Interface configuration
Command History
Usage Guidelines
This command is used in configurations where the router is intended to communicate with an ATM network through an ATM data service unit (ADSU). Given the circuit identifier parameters (VPI and VCI) for the ATM permanent virtual circuit (PVC), the router computes and uses the DXI frame address (DFA) that is used for communication between the router and the ADSU.
The dxi map command can be used only on a serial interface or HSSI configured for ATM-DXI encapsulation.
Examples
The following example converts all IP packets intended for the host with IP address 172.21.170.49 into ATM cells identified with a VPI of 2 (binary 0000 0010) and a VCI of 46 (binary 0000 0000 0010 1110) by the ADSU:
interface serial 0dxi map ip 172.21.170.49 2 46 broadcastUsing the mapping defined in Annex A of the ATM DXI Specification, the router uses the VPI and VCI information in this example to compute a DFA of 558 (binary 1000101110). The ADSU will use the DFA of the incoming frame to extract the VPI and VCI information when formulating ATM cells.
Related Commands
dxi pvc
Configures multiprotocol or single-protocol ATM-DXI encapsulation.
encapsulation atm-dxi
Enables ATM-DXI encapsulation.
dxi pvc
To configure multiprotocol or single protocol ATM-Data Exchange Interface (DXI) encapsulation, use the dxi pvc command in interface configuration mode. To disable multiprotocol ATM-DXI encapsulation, use the no form of this command.
dxi pvc vpi vci [snap | nlpid | mux]
no dxi pvc vpi vci [snap | nlpid | mux]
Syntax Description
Defaults
LLC/SNAP encapsulation
Command Modes
Interface configuration
Command History
Usage Guidelines
This command can be used only on a serial interface or HSSI that is configured with ATM-DXI encapsulation.
Select the nlpid option if you are using the default encapsulation for software releases earlier than Cisco IOS Release 10.3.
Examples
The following example configures ATM-DXI MUX encapsulation on serial interface 1. The PVC identified by a VPI of 10 and a VCI of 10 can carry a single protocol. Then the protocol to be carried on this PVC is defined by the dxi map command.
interface serial 1dxi pvc 10 10 muxdxi map ip 172.21.176.45 10 10 broadcastThe following example configures ATM-DXI NLPID encapsulation on serial interface 1. The PVC identified by a VPI of 11 and a VCI of 12 can carry multiprotocol traffic that is encapsulated with a header described in RFC 1294/1490.
interface serial 1dxi pvc 11 12 nlpidRelated Commands
class-int
Maps a protocol address to a given VPI and VCI.
encapsulation atm-dxi
Enables ATM-DXI encapsulation.
show dxi pvc
Displays the PVC statistics for a serial interface.
efci-bit
To set the explicit forward congestion indication (EFCI) bit field in the ATM cell header for FRF.8 service interworking, use the efci-bit command in FRF.8 connect mode. To disable or reset this bit, use the no form of this command.
efci-bit {0 | map-fecn}
no efci-bit {0 | map-fecn}
Syntax Description
Defaults
The default is 0.
Command Modes
FRF.8 connect configuration
Command History
Usage Guidelines
This command maps from Frame Relay to ATM.
Examples
The following example creates a connection that connects Frame Relay DLCI 100 to ATM PVC 0/32, and sets the EFCI field in the ATM cell header to 1 when the FECN field in the Frame Relay header is set:
Router(config)# interface atm1/0Router(config-if)# pvc 0/32Router(config-if)# encapsulation aal5mux fr-atm-srvRouter(config)# connect serial0 100 atm1/0 0/32 service-interworkingRouter(config-frf8)# efci-bit map-fecnRelated Commands
encapsulation (ATM)
To configure the ATM adaptation layer (AAL) and encapsulation type for an ATM virtual circuit (VC), VC class, VC, bundle, or permanent virtual circuit (PVC) range, use the encapsulation command in the appropriate mode. To remove an encapsulation type, use the no form of this command.
encapsulation {aal2 | aal5auto | aal5autoppp virtual-template number [group group-name] | aal5ciscoppp virtual-template number | aal5mux protocol | aal5nlpid | aal5snap}
no encapsulation {aal2 | aal5auto | aal5autoppp virtual-template number [group group-name] | aal5ciscoppp virtual-template number | aal5mux protocol | aal5nlpid | aal5snap}
Syntax Description
Defaults
The global default encapsulation option is aal5snap. See the "Usage Guidelines" section for other default characteristics.
Command Modes
ATM VC configuration (for an ATM PVC or SVC)
VC-class configuration (for a VC class)
Bundle configuration (for a VC bundle)
PVC range configuration (for an ATM PVC range)
PVC-in-range configuration (for an individual PVC within a PVC range)Command History
Usage Guidelines
Note
Use the aal5mux encapsulation option to dedicate the specified PVC to a single protocol; use the aal5snap encapsulation option to multiplex two or more protocols over the same PVC. Whether you select aal5mux or aal5snap encapsulation might depend on practical considerations, such as the type of network and the pricing offered by the network. If the pricing of the network depends on the number of PVCs set up, aal5snap might be the appropriate choice. If pricing depends on the number of bytes transmitted, aal5mux might be the appropriate choice because it has slightly less overhead.
Encapsulation for PPPoA
When configuring Cisco PPP over ATM, use the aal5ciscoppp keyword and specify the virtual template number.
It is possible to implicitly create a virtual template when configuring Cisco PPP over ATM. In other words, if the parameters of the virtual template are not explicitly defined before you configure the ATM PVC, the PPP interface will be brought up using default values from the virtual template identified. However, some parameters (such as an IP address) take effect only if they are specified before the PPP interface comes up. Therefore, we recommend that you explicitly create and configure the virtual template before configuring the ATM PVC to ensure that such parameters take effect.
If you specify virtual template parameters after the ATM PVC is configured, you should enter a shutdown command followed by a no shutdown command on the ATM subinterface to restart the interface, causing the newly configured parameters (such as an IP address) to take effect.
Configuring PPPoA/PPPoE Autosense
Use the encapsulation aal5autoppp virtual-template template-number command to configure PPPoA/PPPoE autosense. PPPoA/PPPoE autosense enables a router to distinguish between incoming PPPoA and PPPoE sessions and create virtual access for both PPP types based on demand.
If a PPPoE profile is not specified by using the group group-name option, PPPoE sessions will be established using parameters from the global PPPoE profile. PPPoE profiles must be configured using the bba-group pppoe command.
Note
Entering the no encapsulation aal5autoppp virtual-template command will terminate the PPPoA or PPPoE session and detach the virtual-access interface from the PVC.
Configuring Encapsulation for VC Bundles
Before using this command to configure a VC bundle, enter the bundle subinterface configuration command to create a new bundle or modify an existing one and to enter bundle configuration mode.
A VC bundle can have only one encapsulation configured for it: either aal5snap or aal5mux.
Encapsulation Rules of Precedence
If the encapsulation command is not explicitly configured on an ATM PVC, SVC, or VC bundle, the VC inherits the following default configuration (listed in order of precedence from lowest to highest):
•
•
•
•
Note
Configuring Encapsulation for a PVC Range
When a PVC range or an individual PVC within a PVC range is being configured, the following options are available:
•
•
•
Examples
MUX-Type Encapsulation on a VC Example
The following example configures an ATM PVC with VPI 0 and VCI 33 for a MUX-type encapsulation using IP:
interface atm 1/0pvc 0/33encapsulation aal5mux ipSNAP Encapsulation Example
The following example configures a bundle called "chicago" for aal5snap encapsulation:
bundle chicagoencapsulation aal5snapPPP over ATM SVCs Example
The following example configures an ATM SVC called "chicago" with the encapsulation type aal5auto. Encapsulation type aal5auto enables the SVC to use PPP and either aal5snap or aal5mux encapsulation.
interface ATM 2/0/0svc chicagoencapsulation aal5autoPPPoA/PPPoE Autosense Example
The following example enables PPPoA/PPPoE autosense on PVC 30/33. PPPoA sessions will use virtual template 1, and PPPoE sessions will use the global PPPoE profile.
interface ATM 0/0/0.33 multipointpvc 30/33encapsulation aal5autoppp virtual-template 1!bba-group pppoe globalvirtual-template 1sessions max limit 8000sessions per-vc limit 8sessions per-mac limit 2AAL2 Voice over ATM Example
The following example configures a PVC to support AAL2 encapsulation for Voice over ATM:
interface ATM0.2 point-to-pointpvc 2/200vbr-rt 760 760 100encapsulation aal2Related Commands
encapsulation (Frame Relay VC-bundle)
To override the encapsulation for a point-to-point subinterface and configure Frame Relay encapsulation for an individual Frame Relay permanent virtual circuit (PVC) bundle, use the encapsulation command in Frame Relay VC-bundle configuration mode. To disable the encapsulation for the individual PVC bundle and revert to the encapsulation for the point-to-point subinterface, use the no form of this command.
encapsulation [cisco | ietf]
no encapsulation [cisco | ietf]
Syntax Description
Defaults
Encapsulation type that is configured on the main interface
Command Modes
Frame Relay VC-bundle configuration
Command History
Usage Guidelines
Use this command to override the encapsulation at a point-to-point subinterface for an individual Frame Relay PVC bundle. This command is available for point-to-point subinterfaces only; it cannot be used on multipoint interfaces.
Examples
The following example configures RFC 1490 encapsulation for the Frame Relay PVC bundle named "P2P-5":
interface serial 1/4.2 point-to-pointip address 10.1.1.1 255.0.0.0frame-relay vc-bundle P2P-5encapsulation ietfRelated Commands
encapsulation (L2TP)
To specify the Layer 2 data encapsulation method to be used for tunneling IP traffic over a pseudowire, use the encapsulation (L2TP) command in pseudowire class configuration mode. To remove the specified Layer 2 encapsulation method, use the no form of this command.
encapsulation {l2tpv2 | l2tpv3 [manual] | mpls}
no encapsulation {l2tpv2 | l2tpv3 [manual] | mpls}
Syntax Description
Defaults
No encapsulation method is specified.
Command Modes
Pseudowire class configuration
Command History
12.0(23)S
This command was introduced.
12.3(2)T
The l2tpv2 keyword was added and this command was integrated into Cisco IOS Release 12.3(2)T.
Usage Guidelines
This command must be configured if the pseudowire class will be referenced from an xconnect or pseudowire configured to forward Layer 2 traffic.
Examples
The following example shows how to configure L2TPv3 as the data encapsulation method for the pseudowire class named "ether-pw":
Router(config)# pseudowire-class ether-pwRouter(config-pw)# encapsulation l2tpv3Related Commands
pseudowire-class
Specifies the name of an L2TP pseudowire class and enters pseudowire class configuration mode.
encapsulation atm-dxi
To enable ATM-Data Exchange Interface (DXI) encapsulation, use the encapsulation atm-dxi command in interface configuration mode. To disable ATM-DXI, use the no form of this command.
encapsulation atm-dxi
no encapsulation atm-dxi
Syntax Description
This command has no arguments or keywords.
Defaults
When ATM-DXI encapsulation is not configured, HDLC is the default encapsulation.
Command Modes
Interface configuration
Command History
Examples
The following example configures ATM-DXI encapsulation on serial interface 1:
interface serial 1encapsulation atm-dxiRelated Commands
encapsulation frame-relay
To enable Frame Relay encapsulation, use the encapsulation frame-relay command in interface configuration mode. To disable Frame Relay encapsulation, use the no form of this command.
encapsulation frame-relay [cisco | ietf]
no encapsulation frame-relay [ietf]
Syntax Description
Defaults
The default is cisco encapsulation.
Command Modes
Interface configuration
Command History
Usage Guidelines
Use this command with no keywords to restore the default Cisco encapsulation, which is a 4-byte header with 2 bytes for the DLCI and 2 bytes to identify the packet type.
You should shut down the interface prior to changing encapsulation types. Although this is not required, shutting down the interface ensures that the interface is reset for the new encapsulation.
Examples
The following example configures Cisco Frame Relay encapsulation on interface serial 1:
interface serial 1encapsulation frame-relayUse the ietf keyword if your router or access server is connected to another vendor's equipment across a Frame Relay network to conform with RFC 1490:
interface serial 1encapsulation frame-relay ietfencapsulation frame-relay mfr
To create a multilink Frame Relay bundle link and associate the link with a bundle, use the encapsulation frame-relay mfr command in interface configuration mode. To remove the bundle link from the bundle, use the no form of this command.
encapsulation frame-relay mfr number [name]
Syntax Description
Defaults
The default LID is the name of the physical interface.
Command Modes
Interface configuration
Command History
Usage Guidelines
Use the name argument to assign a LID name to a bundle link. This name will be used to identify the bundle link to peer devices and to enable the devices to determine which bundle links are associated with which bundles. The LID name can also be assigned or changed by using the frame-relay multilink lid command on the bundle link interface. If the LID name is not assigned, the default name is the name of the physical interface.
Tip
To remove a bundle link from a bundle, use the no encapsulation frame-relay mfr command or configure a new type of encapsulation on the interface by using the encapsulation command.
Examples
The following example shows serial interface 0 being associated as a bundle link with bundle interface "mfr0". The bundle link identification name is "BL1".
interface mfr0!interface serial 0encapsulation frame-relay mfr0 BL1Related Commands
encapsulation lapb
To exchange datagrams over a serial interface using Link Access Procedure, Balanced (LAPB) encapsulation, use the encapsulation lapb command in interface configuration mode.
encapsulation lapb [dte | dce] [multi | protocol]
Syntax Description
Defaults
The default serial encapsulation is High-Level Data Link Control (HDLC). You must explicitly configure a LAPB encapsulation method.
DTE operation is the default LAPB mode. IP is the default protocol.
Command Modes
Interface configuration
Command History
Usage Guidelines
LAPB encapsulations are appropriate only for private connections, where you have complete control over both ends of the link. Connections to X.25 networks should use an X.25 encapsulation configuration, which operates the X.25 Layer 3 protocol above a LAPB Layer 2.
One end of the link must be a logical DCE device, and the other end a logical DTE device. (This assignment is independent of the interface's hardware DTE or DCE identity.)
Both ends of the LAPB link must specify the same protocol encapsulation.
LAPB encapsulation is supported on serial lines configured for dial-on-demand routing (DDR). It can be configured on DDR synchronous serial and ISDN interfaces and on DDR dialer rotary groups. It is not supported on asynchronous dialer interfaces.
A single-protocol LAPB encapsulation exchanges datagrams of the given protocol, each in a separate LAPB information frame. You must configure the interface with the protocol-specific parameters needed—for example, a link that carries IP traffic will have an IP address defined for the interface.
A multiprotocol LAPB encapsulation can exchange any or all of the protocols allowed for a LAPB interface. It exchanges datagrams, each in a separate LAPB information frame. Two bytes of protocol identification data precede the protocol data. You need to configure the interface with all the protocol-specific parameters needed for each protocol carried.
Multiprotocol LAPB encapsulation supports transparent bridging. This feature requires use of the encapsulation lapb multi command followed by the bridge-group command, which identifies the bridge group associated with multiprotocol LAPB encapsulation. This feature does not support use of the encapsulation lapb protocol command with a bridge keyword.
LAPB encapsulation supports the priority and custom queueing features.
Examples
The following example sets the operating mode as DTE and specifies that AppleTalk protocol traffic will be carried on the LAPB line:
interface serial 1encapsulation lapb dte appletalkRelated Commands
encapsulation smds
To enable Switched Multimegabit Data Service (SMDS) on the desired interface, use the encapsulation smds interface configuration command.
encapsulation smds
Syntax Description
This command has no arguments or keywords.
Defaults
Disabled
Command Modes
Interface configuration
Command History
Usage Guidelines
The interface to which this command applies must be a serial interface. All subsequent SMDS configuration commands apply only to an interface with encapsulation SMDS.
Note
Caution
Examples
The following example shows how to configure the SMDS service on serial interface 0:
interface serial 0encapsulation smdsRelated Commands
encapsulation x25
To specify a serial interface's operation as an X.25 device, use the encapsulation x25 command in interface configuration mode. To remove the specification, use the no form of this command.
encapsulation x25 [dte | dce] [ddn | bfe | ietf]
no encapsulation x25 [dte | dce] [ddn | bfe | ietf]
Syntax Description
Defaults
The default serial encapsulation is High-Level Data Link Control (HDLC). You must explicitly configure an X.25 encapsulation method.
DTE operation is the default X.25 mode. Cisco's traditional X.25 encapsulation method is the default.
Command Modes
Interface configuration
Command History
10.0
This command was introduced.
10.3
The following keywords were added:
•
•
•
•
•
Usage Guidelines
One end of an X.25 link must be a logical DCE device and the other end a logical DTE device. (This assignment is independent of the interface's hardware DTE or DCE identity.) Typically, when connecting to a public data network (PDN), the customer equipment acts as the DTE device and the PDN attachment acts as the DCE.
Cisco has long supported the encapsulation of a number of datagram protocols, using a standard means when available and a proprietary means when necessary. The IETF adopted a standard, RFC 1356, for encapsulating most types of datagram traffic over X.25. X.25 interfaces use Cisco's traditional method unless explicitly configured for IETF operation; if the ietf keyword is specified, that standard is used unless Cisco's traditional method is explicitly configured. For details see the x25 map command.
You can configure a router attaching to the DDN or to a BFE device to use their respective algorithms to convert between IP and X.121 addresses by using the ddn or bfe option, respectively. An IP address must be assigned to the interface, from which the algorithm will generate the interface's X.121 address. For proper operation, this X.121 address must not be modified.
A router DDN attachment can operate as either a DTE or a DCE device. A BFE attachment can operate only as a DTE device. The ietf option is not available if either the ddn or bfe option is selected.
Examples
The following example configures the interface for connection to a BFE device:
interface serial 0encapsulation x25 bfeRelated Commands
exp
To configure Multiprotocol Label Switching (MPLS) experimental (EXP) levels for a Frame Relay permanent virtual circuit (PVC) bundle member, use the exp command in Frame Relay VC-bundle-member configuration mode. To remove the EXP level configuration from the PVC, use the no form of this command.
exp {level | other}
no exp
Syntax Description
Defaults
EXP levels are not configured.
Command Modes
Frame Relay VC-bundle-member configuration
Command History
Usage Guidelines
Assignment of MPLS EXP levels to Frame Relay PVC bundle members allows you to create differentiated service because you can distribute the levels over the various PVC bundle members. You can map a single level or a range of levels to each discrete PVC in the bundle, thereby enabling PVCs in the bundle to carry packets marked with different levels. Use the exp other command to indicate that a PVC can carry traffic marked with EXP levels not specifically configured for other PVCs. Only one PVC in the bundle can be configured using the exp other command.
All EXP levels must be accounted for in the PVC bundle configuration, or the bundle will not come up. Note, however, that a PVC may be a bundle member but have no EXP level associated with it. As long as all valid EXP levels are handled by other PVCs in the bundle, the bundle can come up, but the PVC that has no EXP level configured will not participate in it.
The exp command is available only when tag-switching is configured on the interface with the tag-switching ip command.
You can overwrite the EXP level configuration on a PVC by reentering the exp command with a new value.
The MPLS experimental bits are a bit-by-bit copy of the IP precedence bits. When Frame Relay PVC bundles are configured for IP precedence and tag-switching is enabled, the precedence command is replaced by the exp command. When tag-switching is disabled, the exp command is replaced by the precedence command.
Examples
The following example shows the configuration of four Frame Relay PVC bundle members in PVC bundle "bundle1" configured with MPLS EXP level support:
interface serial 0.1 point-to-pointencapsulation frame-relayip address 10.1.1.1tag-switching ipframe-relay vc-bundle bundle1pvc 100 ny-controlclass controlexp 7protect vcpvc 101 ny-premiumclass premiumexp 6-5protect groupno bump trafficbump explicit 7pvc 102 my-priorityclass priorityexp 4-2protect grouppvc 103 ny-basicclass basicexp otherprotect groupRelated Commands
